CN116600352B - Space-earth integrated QoS consistency processing method, qoS convergent and QoS orchestrator - Google Patents

Abstract

The present disclosure relates to a method for processing QoS consistency, qoS convergent and QoS orchestrator. In at least one embodiment of the present disclosure, a QoS aggregator is added, after the QoS orchestrator receives a QoS identifier request, the QoS orchestrator sends a network capability request to the QoS aggregator, so that the QoS aggregator obtains node functions from network nodes of different network segments of an heaven-earth integrated network as network capabilities, and further the QoS orchestrator may obtain the network capabilities of the different network segments from the QoS aggregator, and based on a matching relationship between the QoS identifier and the network capabilities determined by the capabilities of the network segments, since the basis for calculating the QoS identifier is the network capabilities of the different network segments, the QoS identifier can meet QoS requirements of the different network segments, thereby avoiding QoS failure of a certain network segment in the network or failing to meet requirements of users.

Description

Space-earth integrated QoS consistency processing method, qoS convergent and QoS orchestrator

Technical Field

The embodiment of the disclosure relates to the technical field of satellite networks, in particular to a method for processing QoS consistency of an heaven-earth integration, a QoS convergent and a QoS orchestrator.

Background

In the field of communications, a complete telecommunication service network, different parts of the network (i.e. different network segments) are relatively independently evolving, different organizations defining different quality of service (Quality of Service, qoS) implementations for different network segments, e.g. 3GPP (3 rd Generation Partnership Project, third generation partnership project) standards defining QoS schemes for 5G (5 th Generation Mobile Communication Technology, fifth generation mobile communication technology) RANs (Radio Access Network, radio access networks); the IETF (The Internet Engineering Task Force, internet engineering task force) defines QoS schemes for F5G (The 5th Generation Fixed networks, fifth generation fixed network). Different QoS schemes defined by different organizations are followed in different parts of the network, so that in different network segments, the configuration of the network devices also follows the QoS schemes of the network segments to implement QoS functions.

However, due to the inconsistency of the negotiated protocols of the QoS levels of different network segments, the QoS schemes of the network segments cannot be effectively executed, so that the QoS schemes of the network segments are difficult to be compatible, and QoS of a certain network segment in the network may be invalid or the requirements of users cannot be met. In a 5G satellite network, a space network and a ground cable network are required to be considered, and meanwhile, a service level also needs to follow a 5G standard, so that implementation of a QoS scheme is more complex, and therefore, it is highly desirable to provide an heaven-earth integrated QoS consistency processing scheme for coordinating and considering different QoS schemes in the satellite network, so as to avoid QoS failure of a certain network segment in the network or incapacity of meeting requirements of users.

Disclosure of Invention

At least one embodiment of the present disclosure provides an heaven-earth integrated QoS consistency processing method, a QoS aggregator, and a QoS orchestrator.

In a first aspect, an embodiment of the present disclosure provides a method for processing QoS consistency of heaven and earth integration, where the method includes:

the QoS convergence device receives a network capacity request sent by the QoS orchestrator, wherein the network capacity request is a request generated after the QoS orchestrator receives a QoS identification request sent by a data source;

the QoS convergent device responds to the network capability request and acquires node functions from network nodes of different network segments of the heaven-earth integrated network as network capabilities;

after the QoS convergence device completes the capacity acquisition of each network segment in the heaven-earth integrated network, the QoS convergence device sends a network capacity confirmation message to the QoS arrangement device, wherein the network capacity confirmation message comprises the capacity of each network segment in the heaven-earth integrated network;

the QoS convergence device receives QoS identification matching sent by the QoS orchestrator, wherein the QoS identification matching is a matching relation between QoS identification and network capacity, which is determined by the QoS orchestrator based on the capacity of each network segment included in the network capacity confirmation message;

the QoS convergence device controls QoS of the heaven-earth integrated network based on the QoS identification.

In some embodiments, the QoS converger performs QoS control on the heaven-earth integrated network based on the QoS identification, including:

after the QoS convergence device detects that the network has no conflict, a confirmation message of QoS identification matching is sent to the QoS arrangement device;

the QoS convergence device receives the QoS strategy sent by the QoS orchestrator, wherein the QoS strategy is the strategy of the configuration space node and/or the ground node determined by the QoS orchestrator based on the QoS mark;

the QoS aggregator sends node configuration information to the network forwarding device based on the QoS policy to cause the network forwarding device to configure the space node and/or the ground node based on the node configuration information.

In some embodiments, the method for processing the world-wide integrated QoS consistency further comprises:

after the QoS convergence device sends node configuration information to the network forwarding device, a message for confirming implementation of QoS strategy is sent to the QoS arrangement device;

the QoS convergence device receives a space routing strategy sent by the QoS orchestrator, wherein the space routing strategy is a routing strategy of a space node and/or a ground node determined based on the QoS strategy after the QoS orchestrator receives a message confirming implementation of the QoS strategy;

the QoS aggregator sends node routing information to the network routing device based on the spatial routing policy to cause the network routing device to select spatial nodes and/or ground nodes for routing based on the node routing information.

In some embodiments, after acquiring the node function as the network capability from the network node of the different network segments of the heaven-earth integrated network, the heaven-earth integrated QoS uniformity processing method further comprises:

the QoS convergence device generates a capability matching table based on the acquired node capability, wherein the capability matching table comprises the following table items:

matching items, policy items, and capability items;

wherein the matching item is used for describing the capability type of the matching;

policy items are used to describe available policies that meet QoS requirements;

the capability item is used to describe the capabilities of the available policies.

In some embodiments, the capability type includes at least one of:

TCP/IP protocol layer capability, spatial routing capability, and hard pipe capability;

the capability items corresponding to the TCP/IP protocol layer capability comprise at least one of the following: whether to identify the original address and whether to identify the DSCP field;

the capability items corresponding to the space routing capability include at least one of the following: port bandwidth speed limit range, number of forwarding queues and number of supported propagation priorities;

the capability items corresponding to the hard pipe capability include at least one of the following: whether hard pipe, hard pipe bandwidth, and queue number are supported.

In a second aspect, an embodiment of the present disclosure further provides a method for processing QoS consistency of heaven and earth integration, where the method includes:

After receiving a QoS identification request sent by a data source, a QoS orchestrator generates a network capability request;

the QoS orchestrator sends the network capability request to the QoS convergent device, so that the QoS convergent device obtains node functions from network nodes of different network segments of the heaven-earth integrated network as network capabilities;

the QoS orchestrator receives a network capability confirmation message sent by the QoS aggregator, wherein the network capability confirmation message comprises the capability of each network segment in the heaven-earth integrated network;

the QoS orchestrator determines QoS identity matches based on capabilities of each network segment included in the network capability confirmation message;

the QoS orchestrator sends the QoS identification match to the QoS aggregator, so that the QoS aggregator performs QoS control on the heaven-earth integrated network based on the QoS identification.

In some embodiments, the method further comprises:

after receiving a QoS identification request sent by a data source, a QoS orchestrator analyzes QoS requirements of a data flow, wherein the QoS requirements comprise: the number of 5QI identifications, the priority PL of 5QI and the allocation reservation priority ARP requirement;

accordingly, the QoS orchestrator determines a QoS identity match based on the capabilities of the network segments included in the network capability confirmation message, comprising:

the QoS orchestrator determines that the QoS identities match based on the QoS requirements and the capabilities of the network segments included in the network capability confirmation message.

In some embodiments, the QoS orchestrator determines that the QoS identification matches based on the QoS requirements and capabilities of the network segments included in the network capability confirmation message, comprising:

judging whether the number of 5QI identifiers is smaller than or equal to the number of QoS levels indicated in the capacity of each network segment;

if the number of the 5QI identifiers is smaller than or equal to the number of QoS levels, matching Qn with Cn, wherein Qn is any 5QI identifier, cn is configuration information of a group of network nodes and a group of network nodes in the heaven-earth integrated network;

if the number of the 5QI identifiers is greater than the number of the QoS classes, matching Qn with Cn according to the priority PL of the 5QI identifiers, matching data streams capable of performing integer division operation on the number of the 5QI identifiers and the number of the QoS classes to specified QoS classes, and matching data streams capable of performing integer division operation on the number of the 5QI identifiers and the number of the QoS classes by 1 to unspecified QoS classes, wherein the specified QoS classes are QoS classes corresponding to values obtained by performing residual operation on the number of the QoS classes by the difference between the number of the QoS classes and the number of the 5QI identifiers;

after Qn and Cn are matched, sorting data streams based on ARP requirements;

traversing in ascending order:

if the GBR requirement exists and the network node is not a hard pipeline, judging whether the function of the network forwarding equipment meets the GBR requirement, if so, trying to match the QoS identifier based on the function of the network node, if the matching fails, trying to match the 5QI identifier based on the configuration information of the network node in TCP, and if the matching fails again, sending a matching failure notification; if the GBR requirement is not met, attempting to match the 5QI identifier based on the TCP configuration information, and if the matching fails, sending a matching failure notification;

If the network node is a hard pipeline or the rate per second reaches a rate threshold set by a user, hard pipeline matching is tried, and if matching fails, a matching failure notification is sent.

In a third aspect, embodiments of the present disclosure further provide a QoS converger, including:

a first receiving unit, configured to receive a network capability request sent by a QoS orchestrator, where the network capability request is a request generated after the QoS orchestrator receives a QoS identification request sent by a data source;

an acquiring unit, configured to acquire node functions as network capabilities from network nodes of different network segments of the heaven-earth integrated network in response to the network capability request;

the sending unit is used for sending a network capacity confirmation message to the QoS orchestrator after the obtaining unit completes the capacity obtaining of each network segment in the heaven-earth integrated network, wherein the network capacity confirmation message comprises the capacity of each network segment in the heaven-earth integrated network;

a second receiving unit, configured to receive QoS identifier matching sent by the QoS orchestrator, where the QoS identifier matching is a matching relationship between a QoS identifier determined by the QoS orchestrator based on capabilities of network segments included in the network capability confirmation message and network capabilities;

and the control unit is used for carrying out QoS control on the heaven-earth integrated network based on the QoS identification.

In a fourth aspect, embodiments of the present disclosure further provide a QoS orchestrator, including:

the first receiving unit is used for generating a network capability request after receiving the QoS identification request sent by the data source;

a first sending unit, configured to send a network capability request to the QoS converger, so that the QoS converger obtains node functions from network nodes of different network segments of the heaven-earth integrated network as network capabilities;

the second receiving unit is used for receiving the network capacity confirmation message sent by the QoS convergent, wherein the network capacity confirmation message comprises the capacity of each network segment in the heaven-earth integrated network;

a determining unit, configured to determine QoS identifier matching based on capabilities of each network segment included in the network capability confirmation message;

and the second sending unit is used for sending the QoS identification match to the QoS convergent device so that the QoS convergent device can carry out QoS control on the heaven-earth integrated network based on the QoS identification.

It can be seen that, in at least one embodiment of the present disclosure, a QoS aggregator is newly added, and after the QoS orchestrator receives the QoS identifier request, the QoS orchestrator sends a network capability request to the QoS aggregator, so that the QoS aggregator obtains node functions from network nodes of different network segments of the heaven-earth integrated network as network capabilities, and further, the QoS orchestrator may obtain the network capabilities of the different network segments from the QoS aggregator, and based on the matching relationship between the QoS identifier and the network capabilities determined by the capabilities of the network segments, since the basis for calculating the QoS identifier is the network capabilities of the different network segments, the QoS identifier can meet QoS requirements of the different network segments, thereby avoiding QoS failure of a certain network segment in the network or failing to meet requirements of users.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings used in the embodiments or the description of the prior art will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present disclosure, and other drawings may be obtained according to these drawings to those of ordinary skill in the art.

Fig. 1 is a flow chart of an heaven-earth integrated QoS consistency processing method according to an embodiment of the present disclosure;

fig. 2 is a flow chart of another method for processing QoS consistency integrated with the world provided in an embodiment of the present disclosure;

fig. 3 is an interactive flow diagram of an heaven-earth integrated QoS uniformity process according to an embodiment of the present disclosure;

fig. 4 is a schematic diagram of a QoS converger provided in an embodiment of the present disclosure;

fig. 5 is a schematic diagram of a QoS orchestrator according to an embodiment of the present disclosure.

Detailed Description

In order that the above-recited objects, features and advantages of the present disclosure may be more clearly understood, a more particular description of the disclosure will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. It is to be understood that the described embodiments are some, but not all, of the embodiments of the present disclosure. The specific embodiments described herein are to be considered in an illustrative rather than a restrictive sense. All other embodiments derived by a person of ordinary skill in the art based on the described embodiments of the present disclosure fall within the scope of the present disclosure.

It should be noted that in this document, relational terms such as "first" and "second" and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.

At present, because the relevance and the corresponding relation between different QoS schemes are not defined, the converged QoS identifier cannot simultaneously meet the different QoS schemes, so that the QoS of a certain network segment in the network fails or the requirement of a user cannot be met. For example, the converged QoS is identified as 5QI (5G QoS Identifier,5G network quality of service identifier), the 5QI defining scheduling priorities for different data flows, but when resources of a certain network segment in the network are limited, the aggregation and propagation module of the network may discard data flows with high priorities, which would result in the setting of scheduling priorities to be useless.

Therefore, the embodiment of the disclosure provides a method, a device, equipment and a storage medium for processing the world integrated QoS consistency, which realize the function of adaptively determining the QoS identification without depending on the QoS consistency scheme of a manufacturer, so that the determined QoS identification simultaneously meets different QoS schemes, and the condition that the QoS of a certain network segment in a network is invalid or the requirement of a user cannot be met is avoided.

Fig. 1 is a flow chart of an heaven and earth integrated QoS uniformity processing method according to an embodiment of the present disclosure, where a QoS convergence device is used as an execution body, and an interactive flow of QoS uniformity processing is described, as shown in fig. 1, the method may include, but is not limited to, steps 101 to 105:

in step 101, the QoS convergence device receives a network capability request sent by the QoS orchestrator, where the network capability request is a request generated by the QoS orchestrator after receiving a QoS identification request sent by a data source.

The data source is a user data plane, and is embodied as a network element in an heaven-earth integrated network, so as to send a QoS identification request, for example, a request of 5QI requirement. The data sources are, for example: UPF in 5G network (User Plane Function ).

The QoS convergence device is configured to aggregate a plurality of parameters affecting QoS into a single QoS identifier, and a specific process is described below. The QoS orchestrator is configured to determine, based on parameters affecting QoS, an action or behavior of a network node corresponding to the QoS identifier, where the network node is a node in the space-earth integrated network, and the network node may be a spatial node (e.g. a satellite) or a ground node.

In step 102, the QoS aggregator obtains node functions as network capabilities from network nodes of different network segments of the heaven-earth integrated network in response to the network capability request.

The node functions are functions that can be provided for implementation of QoS schemes, including hardware functions and software functions of each network node in the heaven-earth integrated network, for example: TCP/IP protocol layer capabilities, spatial routing capabilities, and hard pipe capabilities.

The capability items corresponding to the TCP/IP protocol layer capability comprise at least one of the following: whether to identify the original address and whether to identify the DSCP (Differentiated Services Code Point ) field;

the capability items corresponding to the space routing capability include at least one of the following: port bandwidth speed limit range, number of forwarding queues and number of supported propagation priorities;

the capability items corresponding to the hard pipe capability include at least one of the following: whether hard pipe, hard pipe bandwidth, and queue number are supported.

In this embodiment, the QoS converger refines the QoS index, including:

1. GBR (Guaranteed Bit Rate ): GFBR (Guaranteed Flow Bit Rate, guaranteed minimum bit rate), MFBR (Maximum Flow Bit Rate, maximum bit rate), MPLR (Maximum Packet Lose Rate, maximum data packet loss rate).

2. 5QI: PL (Priority Level), PBD (Packet Delay Budget, message delay).

3. ARP (AllocationRetention Priority), assigned reservation priority).

It is understood that GBR,5qi, arp are all identities in different QoS schemes.

In step 103, after completing the capability acquisition of each network segment in the heaven-earth integration network, the QoS convergence device sends a network capability confirmation message to the QoS orchestrator, where the network capability confirmation message includes the capability of each network segment in the heaven-earth integration network.

After the QoS convergence device obtains node functions from network nodes of different network segments of the heaven-earth integrated network as network capabilities, generating a capability matching table based on the obtained node capabilities, wherein the capability matching table comprises the following table items:

matching items (Mapping), policy items (Policy), and capability items (capability);

wherein the matching item is used for describing a capability type of the matching, and the capability type comprises at least one of the following: TCP/IP protocol layer capabilities, spatial routing capabilities, and hard pipe capabilities. It can be seen that by matching (Mapping) it is possible to determine what data flow characteristics can hit the capability type described by the matching, for example the capability type described by the matching is TCP/IP protocol layer capability, if the original address of the data flow is a certain IP, the data flow hits the matching, so that Policy items (policies) in the capability matching table can be applied to the data flow.

Policy items are used to describe the available policies that meet QoS requirements. It can be seen that the available policies that can be applied on the data stream can be determined by Policy terms (policies) which can follow the policies conventional in the art.

The capability item is used to describe the capabilities of the available policies. It can be seen that the capabilities of the available policies that can be applied can be determined by the capability item (capability). The QoS converger may obtain the capabilities of the network node, such as maximum transmission rate, support for transmission or reception, number of queues, queue capacity, etc., with the port ID of the network node as an index.

Capability matching codes for different capability types are as follows:

capability matching code corresponding to TCP/IP protocol layer capability:

capability matching codes corresponding to the spatial routing capabilities:

capability matching code corresponding to the hard pipe capability:

the QoS converger generates the capability matching table based on the capability matching code, and it should be noted that the capability matching code may be implemented in different programming languages, and the above capability matching code is merely illustrative, and the embodiment is not limited to a specific implementation of the capability matching code. After the QoS convergence device generates the capability matching table, a network capability confirmation message is sent to the QoS arrangement device, wherein the network capability confirmation message comprises the generated capability matching table.

In step 104, the QoS convergence device receives the QoS identification match sent by the QoS orchestrator, where the QoS identification match is a matching relationship between the QoS identification and the network capabilities determined by the QoS orchestrator based on the capabilities of the network segments included in the network capability acknowledgement message.

In this embodiment, the QoS orchestrator determines QoS identity matches based on a capability matching table (capability matching table represents capabilities of each network segment) included in the network capability confirmation message, and how this is determined is described below.

In step 105, the QoS converger performs QoS control on the heaven-earth integrated network based on the QoS identification.

In this embodiment, after detecting that the network has no conflict, the QoS convergence device confirms the QoS identifier matching, converges to a single QoS identifier, that is, selects one QoS identifier satisfying the QoS requirements of different network segments from the QoS identifier matching, and sends a confirmation message of the QoS identifier matching to the QoS orchestrator; further, the QoS convergence device receives the QoS policy sent by the QoS orchestrator, where the QoS policy is a policy of a configuration space node and/or a ground node determined by the QoS orchestrator based on the QoS identifier, and the QoS policy may follow a conventional policy in the art; thus, the QoS converger sends node configuration information to the network forwarding device based on the QoS policy, so that the network forwarding device configures the space node and/or the ground node based on the node configuration information, where the network forwarding device is configured to apply a processing action corresponding to the QoS identifier (including the policy of configuring the space node and/or the ground node) to the data flow.

It can be seen that, in the embodiment of the present disclosure, a QoS aggregator is newly added, after the QoS orchestrator receives a QoS identifier request, the QoS orchestrator sends a network capability request to the QoS aggregator, so that the QoS aggregator obtains node functions from network nodes of different network segments of the heaven-earth integrated network as network capabilities, and further, the QoS orchestrator may obtain the network capabilities of the different network segments from the QoS orchestrator, and based on the matching relationship between the QoS identifier and the network capabilities determined by the capabilities of the network segments, since the basis of calculating the QoS identifier is the network capabilities of the different network segments, the QoS identifier can meet the QoS requirements of the different network segments, thereby avoiding that the QoS of a certain network segment in the network fails or cannot meet the requirements of users, that is, the embodiment of the present disclosure can automatically and simultaneously meet different QoS standards of the different network segments, and complete the effective configuration of the heaven-earth integrated network 5QI standard, and simultaneously can automatically operate without manual intervention.

In some embodiments, the method for processing the world-wide integrated QoS consistency further comprises:

after the QoS convergence device sends node configuration information to the network forwarding device, a message for confirming implementation of QoS strategy is sent to the QoS arrangement device; further, the QoS convergence device receives a space routing strategy sent by the QoS orchestrator, wherein the space routing strategy is a routing strategy of a space node and/or a ground node determined based on the QoS strategy after the QoS orchestrator receives a message confirming implementation of the QoS strategy, and the routing strategy adopts a conventional strategy in the field; thus, the QoS aggregator sends node routing information to the network routing device based on the spatial routing policy to cause the network routing device to select spatial nodes and/or ground nodes for routing based on the node routing information.

In this embodiment, after the QoS convergence device sends node routing information to the network routing device, a message confirming implementation of the spatial routing policy is sent to the QoS orchestrator, so far, the whole configuration flow is completed, and when the user changes the QoS requirement or has a new requirement, the foregoing steps are repeatedly executed. It should be noted that if the hardware function and the software function of the network are not updated, the capability of each network node is not repeatedly collected.

Fig. 2 is a flow chart of another method for processing QoS consistency integrated with the world, which is provided in the embodiment of the present disclosure, and the embodiment uses QoS arrangement as an execution body, and describes an interaction flow of QoS consistency processing, as shown in fig. 2, and the method may include, but is not limited to, steps 201 to 205:

in step 201, the QoS orchestrator generates a network capability request after receiving a QoS identification request sent by a data source.

In this embodiment, the QoS identifier request may carry function requirement information and resource requirement information, and further, the QoS orchestrator may carry function requirement information and resource requirement information in the network capability request, where the function requirement information and the resource requirement information are requirement information set by a user.

In some embodiments, the QoS orchestrator parses QoS requirements of the data flow after receiving a QoS identification request sent by the data source, where the QoS requirements include: the number of 5QI identities, the priority PL of 5QI and the allocation reservation priority ARP requirement.

In step 202, the QoS orchestrator sends a network capability request to the QoS aggregator to cause the QoS aggregator to obtain node functions as network capabilities from network nodes of different network segments of the heaven-earth integrated network.

In step 203, the QoS orchestrator receives the network capability confirmation message sent by the QoS converger, where the network capability confirmation message includes the capabilities of each network segment in the heaven-earth integrated network.

In step 204, the QoS orchestrator determines a QoS identity match based on the capabilities of the network segments included in the network capability confirmation message.

In this embodiment, the QoS orchestrator determines a QoS identity match based on the QoS requirements and the capabilities of the network segments included in the network capability confirmation message, in particular how this is determined as described below.

In step 205, the QoS orchestrator sends the QoS identity matches to the QoS converger to cause the QoS converger to QoS control the world-wide integrated network based on the QoS identities.

The difference between the interactive flow of the QoS consistency process shown in fig. 1 and the interactive flow of the QoS consistency process in this embodiment is that the QoS orchestrator is used as an execution body in this embodiment, so details of this embodiment may refer to the related embodiment in fig. 1, and will not be described again.

In some embodiments, the QoS orchestrator determines a QoS identity match based on the QoS requirements and capabilities of the network segments included in the network capability confirmation message, in particular:

determining whether the number of 5QI identifiers (Nq) is less than or equal to the number of QoS classes (Nc) indicated in the capabilities of the respective network segment;

if the number of the 5QI identifiers is smaller than or equal to the number of QoS grades, namely Nq is smaller than or equal to Nc, matching Qn with Cn, wherein Qn is any 5QI identifier, cn is configuration information of a group of network nodes and a group of network nodes in the heaven-earth integrated network;

if the number of 5QI identifiers is greater than the number of QoS classes, namely Nq > Nc, matching Qn with Cn according to the priority PL of 5QI, matching the data flow capable of performing integer division operation on the number of 5QI identifiers and the number of QoS classes to a designated QoS class, and matching the data flow capable of performing integer division operation on the number of 5QI identifiers and the number of QoS classes by 1 to a non-designated QoS class, wherein the designated QoS class is the QoS class corresponding to the value obtained by taking the remainder operation on the number of QoS classes by the difference between the number of QoS classes and the number of 5QI identifiers; that is, the data flow of Np// Nc is matched to the QoS class of (Nc-Nq)% Nc; matching the data flow of Nq// (nc+1) to other QoS classes;

After Qn and Cn are matched, sorting data streams based on ARP requirements;

traversing in ascending order:

if the GBR requirement exists and the network node is not a hard pipeline, judging whether the function of the network forwarding equipment meets the GBR requirement, if so, trying to match the QoS identifier based on the function of the network node, if the matching fails, trying to match the 5QI identifier based on the configuration information of the network node in TCP, and if the matching fails again, sending a matching failure notification; if the GBR requirement is not met, attempting to match the 5QI identifier based on the TCP configuration information, and if the matching fails, sending a matching failure notification;

if the network node is a hard pipeline or the rate per second reaches a rate threshold set by a user, hard pipeline matching is tried, and if matching fails, a matching failure notification is sent.

Fig. 3 is an interactive flow chart of an heaven-earth integrated QoS uniformity process according to an embodiment of the present disclosure. Details of the interaction flow are referred to the foregoing embodiments, and will not be described in detail.

It should be noted that, for simplicity of description, the foregoing method embodiments are all expressed as a series of combinations of actions, but those skilled in the art can appreciate that the disclosed embodiments are not limited by the order of actions described, as some steps may occur in other orders or concurrently in accordance with the disclosed embodiments. In addition, those skilled in the art will appreciate that the embodiments described in the specification are all alternatives.

Fig. 4 is a QoS aggregator provided by an embodiment of the present disclosure, where the QoS aggregator may be implemented as software, hardware, or a combination of software and hardware. The QoS convergence device comprises: a first receiving unit 41, an acquiring unit 42, a transmitting unit 43, a second receiving unit 44 and a control unit 45. The units are described as follows:

a first receiving unit 41, configured to receive a network capability request sent by a QoS orchestrator, where the network capability request is a request generated after the QoS orchestrator receives a QoS identification request sent by a data source;

an obtaining unit 42, configured to obtain, in response to the network capability request, a node function from network nodes of different network segments of the heaven-earth integrated network as a network capability;

a sending unit 43, configured to send a network capability confirmation message to the QoS orchestrator after the acquiring unit 42 completes capability acquisition of each network segment in the heaven-earth integrated network, where the network capability confirmation message includes the capability of each network segment in the heaven-earth integrated network;

a second receiving unit 44, configured to receive QoS identifier matching sent by the QoS orchestrator, where the QoS identifier matching is a matching relationship between a QoS identifier determined by the QoS orchestrator based on capabilities of each network segment included in the network capability confirmation message and the network capability;

A control unit 45, configured to perform QoS control on the heaven-earth integrated network based on the QoS identifier.

In some embodiments, the control unit 45 is configured to:

after detecting that the network has no conflict, sending a confirmation message of QoS identification matching to a QoS orchestrator;

receiving a QoS strategy sent by a QoS orchestrator, wherein the QoS strategy is a strategy of a configuration space node and/or a ground node determined by the QoS orchestrator based on the QoS identification;

and sending node configuration information to the network forwarding equipment based on the QoS strategy, so that the network forwarding equipment configures space nodes and/or ground nodes based on the node configuration information.

In some embodiments, the QoS converger further comprises a routing unit to:

after the control unit 45 sends the node configuration information to the network forwarding device, a message confirming implementation of QoS policies is sent to the QoS orchestrator;

receiving a space routing strategy sent by a QoS orchestrator, wherein the space routing strategy is a routing strategy of a space node and/or a ground node determined based on the QoS strategy after the QoS orchestrator receives a message confirming implementation of the QoS strategy;

and transmitting node routing information to the network routing equipment based on the spatial routing strategy, so that the network routing equipment selects spatial nodes and/or ground nodes of the route based on the node routing information.

In some embodiments, the QoS converger further comprises a capability matching unit to:

after the acquiring unit 42 acquires the node function as the network capability from the network nodes of the different network segments of the heaven-earth integrated network, a capability matching table is generated based on the acquired node capability, the capability matching table including the following table entries:

matching items, policy items, and capability items;

wherein the matching item is used for describing the capability type of the matching;

policy items are used to describe available policies that meet QoS requirements;

the capability item is used to describe the capabilities of the available policies.

In some embodiments, the capability type includes at least one of:

TCP/IP protocol layer capability, spatial routing capability, and hard pipe capability;

the capability items corresponding to the TCP/IP protocol layer capability comprise at least one of the following: whether to identify the original address and whether to identify the DSCP field;

the capability items corresponding to the space routing capability include at least one of the following: port bandwidth speed limit range, number of forwarding queues and number of supported propagation priorities;

the capability items corresponding to the hard pipe capability include at least one of the following: whether hard pipe, hard pipe bandwidth, and queue number are supported.

Fig. 5 is a QoS orchestrator provided by an embodiment of the present disclosure, which may be implemented as software, hardware, or a combination of software and hardware components. The QoS orchestrator comprises: a first receiving unit 51, a first transmitting unit 52, a second receiving unit 53, a determining unit 54, and a second transmitting unit 55. The units are described as follows:

A first receiving unit 51, configured to generate a network capability request after receiving a QoS identifier request sent by a data source;

a first sending unit 52, configured to send a network capability request to the QoS converger, so that the QoS converger obtains node functions from network nodes of different network segments of the heaven-earth integrated network as network capabilities;

a second receiving unit 53, configured to receive a network capability confirmation message sent by the QoS converger, where the network capability confirmation message includes capabilities of each network segment in the heaven-earth integrated network;

a determining unit 54, configured to determine a QoS identifier match based on the capabilities of each network segment included in the network capability confirmation message;

a second sending unit 55, configured to send the QoS identifier match to the QoS converger, so that the QoS converger performs QoS control on the heaven-earth integrated network based on the QoS identifier.

In some embodiments, the QoS orchestrator further comprises a parsing unit for:

after the first receiving unit 51 receives the QoS identification request sent by the data source, the QoS requirement of the data flow is parsed, where the QoS requirement includes: the number of 5QI identifications, the priority PL of 5QI and the allocation reservation priority ARP requirement;

accordingly, the determining unit 54 is configured to determine that the QoS identifier matches based on the QoS requirement and the capabilities of each network segment included in the network capability confirmation message.

In some embodiments, the determining unit 54 is configured to:

judging whether the number of 5QI identifiers is smaller than or equal to the number of QoS levels indicated in the capacity of each network segment;

if the number of the 5QI identifiers is smaller than or equal to the number of QoS levels, matching Qn with Cn, wherein Qn is any 5QI identifier, cn is configuration information of a group of network nodes and a group of network nodes in the heaven-earth integrated network;

if the number of the 5QI identifiers is greater than the number of the QoS classes, matching Qn with Cn according to the priority PL of the 5QI identifiers, matching data streams capable of performing integer division operation on the number of the 5QI identifiers and the number of the QoS classes to specified QoS classes, and matching data streams capable of performing integer division operation on the number of the 5QI identifiers and the number of the QoS classes by 1 to unspecified QoS classes, wherein the specified QoS classes are QoS classes corresponding to values obtained by performing residual operation on the number of the QoS classes by the difference between the number of the QoS classes and the number of the 5QI identifiers;

after Qn and Cn are matched, sorting data streams based on ARP requirements;

traversing in ascending order:

if the GBR requirement exists and the network node is not a hard pipeline, judging whether the function of the network forwarding equipment meets the GBR requirement, if so, trying to match the QoS identifier based on the function of the network node, if the matching fails, trying to match the 5QI identifier based on the configuration information of the network node in TCP, and if the matching fails again, sending a matching failure notification; if the GBR requirement is not met, attempting to match the 5QI identifier based on the TCP configuration information, and if the matching fails, sending a matching failure notification;

If the network node is a hard pipeline or the rate per second reaches a rate threshold set by a user, hard pipeline matching is tried, and if matching fails, a matching failure notification is sent.

Details of related embodiments of the QoS converger shown in fig. 4 refer to related embodiments of the heaven-earth integrated QoS consistency processing method shown in fig. 1; details of the relevant embodiments of the QoS orchestrator shown in fig. 5 refer to the relevant embodiments of the heaven-earth integrated QoS consistency handling method shown in fig. 2, and are not described again.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

Those skilled in the art will appreciate that while some embodiments described herein include some features but not others included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the disclosure and form different embodiments.

Those skilled in the art will appreciate that the descriptions of the various embodiments are each focused on, and that portions of one embodiment that are not described in detail may be referred to as related descriptions of other embodiments.

Although embodiments of the present disclosure have been described with reference to the accompanying drawings, various modifications and variations may be made by those skilled in the art without departing from the spirit and scope of the disclosure, and such modifications and variations fall within the scope defined by the appended claims.

Claims (7)

1. A method of world-wide integrated QoS consistency handling, the method comprising:

the QoS convergence device receives a network capacity request sent by the QoS orchestrator, wherein the network capacity request is a request generated after the QoS orchestrator receives a QoS identification request sent by a data source;

the QoS convergent device responds to the network capability request and acquires node functions from network nodes of different network segments of the heaven-earth integrated network as network capabilities;

after the QoS convergence device completes the capacity acquisition of each network segment in the heaven-earth integrated network, the QoS convergence device sends a network capacity confirmation message to the QoS arrangement device, wherein the network capacity confirmation message comprises the capacity of each network segment in the heaven-earth integrated network;

The QoS convergence device receives QoS identification matching sent by the QoS orchestrator, wherein the QoS identification matching is a matching relation between QoS identification and network capacity, which is determined by the QoS orchestrator based on the capacity of each network segment included in the network capacity confirmation message;

the QoS converger performs QoS control on the heaven-earth integrated network based on the QoS identifier, including:

after the QoS convergence device detects that the network has no conflict, the QoS convergence device sends a confirmation message matched with the QoS identification to the QoS arrangement device;

the QoS convergent device receives a QoS strategy sent by the QoS orchestrator, wherein the QoS strategy is a strategy of a configuration space node and/or a ground node determined by the QoS orchestrator based on the QoS identification;

the QoS convergent sends node configuration information to a network forwarding device based on the QoS strategy, so that the network forwarding device configures space nodes and/or ground nodes based on the node configuration information.

2. The method of claim 1, wherein the method further comprises:

after the QoS convergence device sends node configuration information to the network forwarding device, the QoS convergence device sends a message for confirming implementation of QoS strategy to the QoS arrangement device;

The QoS convergence device receives a space routing strategy sent by the QoS orchestrator, wherein the space routing strategy is a routing strategy of a space node and/or a ground node determined based on the QoS strategy after the QoS orchestrator receives the message confirming to implement the QoS strategy;

the QoS aggregator sends node routing information to a network routing device based on the spatial routing policy to cause the network routing device to select spatial nodes and/or ground nodes of a route based on the node routing information.

3. The method of claim 1, wherein after the acquiring node functions from the network nodes of the different network segments of the heaven-earth integrated network as network capabilities, the method further comprises:

the QoS convergence device generates a capability matching table based on the acquired node capability, wherein the capability matching table comprises the following table items:

matching items, policy items, and capability items;

wherein the matching item is used for describing the capability type of matching;

the policy item is used for describing available policies meeting QoS requirements;

the capability item is used to describe the capabilities of the available policies.

4. A method according to claim 3, wherein the capability type comprises at least one of:

TCP/IP protocol layer capability, spatial routing capability, and hard pipe capability;

the capability items corresponding to the TCP/IP protocol layer capability comprise at least one of the following: whether to identify the original address and whether to identify the DSCP field;

the capability items corresponding to the space routing capability comprise at least one of the following: port bandwidth speed limit range, number of forwarding queues and number of supported propagation priorities;

the capability items corresponding to the hard pipeline capability comprise at least one of the following: whether hard pipe, hard pipe bandwidth, and queue number are supported.

5. A method of world-wide integrated QoS consistency handling, the method comprising:

after receiving a QoS identification request sent by a data source, a QoS orchestrator generates a network capability request;

the QoS orchestrator sends the network capability request to a QoS (quality of service) convergence device so that the QoS convergence device obtains node functions from network nodes of different network segments of the heaven-earth integrated network as network capabilities;

the QoS orchestrator receives a network capability confirmation message sent by the QoS convergence device, wherein the network capability confirmation message comprises the capability of each network segment in the heaven-earth integrated network;

the QoS orchestrator determines QoS identity matches based on capabilities of network segments included in the network capability confirmation message;

The QoS orchestrator sends the QoS identification match to the QoS convergent device so that the QoS convergent device performs QoS control on the heaven-earth integrated network based on the QoS identification;

after the QoS orchestrator receives a QoS identification request sent by a data source, analyzing QoS requirements of a data flow, wherein the QoS requirements comprise: the number of 5QI identifications, the priority PL of 5QI and the allocation reservation priority ARP requirement;

accordingly, the QoS orchestrator determines a QoS identification match based on the capabilities of the network segments included in the network capability confirmation message, including:

the QoS orchestrator determining that QoS identities match based on the QoS requirements and capabilities of network segments included in the network capability confirmation message;

the QoS orchestrator determining that QoS identities match based on the QoS requirements and capabilities of the network segments included in the network capability confirmation message, comprising:

judging whether the number of 5QI identifiers is smaller than or equal to the number of QoS levels indicated in the capacity of each network segment;

if the number of the 5QI identifiers is smaller than or equal to the number of the QoS classes, matching Qn with Cn, wherein Qn is any 5QI identifier, cn is configuration information of a group of network nodes in the heaven-earth integrated network and the group of network nodes;

If the number of the 5QI identifiers is greater than the number of the QoS classes, matching the Qn with the Cn according to the priority PL of the 5QI identifiers, matching data flows which can perform integer division operation on the number of the 5QI identifiers and the number of the QoS classes to appointed QoS classes, and matching data flows which can perform integer division operation on the number of the 5QI identifiers and the number of the QoS classes by 1 to unspecified QoS classes, wherein the appointed QoS classes are QoS classes corresponding to values obtained by taking the remainder operation on the number of the QoS classes according to the difference between the number of the QoS classes and the number of the 5QI identifiers;

after the Qn and Cn are matched, sorting data streams based on the ARP requirement;

traversing in ascending order:

if there is GBR demand and the network node is not a hard pipeline, judging whether the function of the network forwarding equipment meets the GBR demand, if so, trying to match QoS identification based on the function of the network node, if so, trying to match 5QI identification based on the TCP configuration information of the network node, if so, sending a matching failure notice; if the GBR requirement is not met, attempting to match the 5QI identifier based on TCP configuration information, and if the matching fails, sending a matching failure notification;

If the network node is a hard pipeline or the rate per second reaches a rate threshold set by a user, hard pipeline matching is tried, and if matching fails, a matching failure notification is sent.

6. A QoS converger, comprising:

a first receiving unit, configured to receive a network capability request sent by a QoS orchestrator, where the network capability request is a request generated after the QoS orchestrator receives a QoS identification request sent by a data source;

an obtaining unit, configured to obtain node functions from network nodes of different network segments of the heaven-earth integrated network as network capabilities in response to the network capability request;

a sending unit, configured to send a network capability confirmation message to the QoS orchestrator after the obtaining unit completes capability obtaining of each network segment in the heaven-earth integrated network, where the network capability confirmation message includes capabilities of each network segment in the heaven-earth integrated network;

a second receiving unit, configured to receive a QoS identifier match sent by the QoS orchestrator, where the QoS identifier match is a matching relationship between a QoS identifier determined by the QoS orchestrator based on capabilities of network segments included in the network capability confirmation message and a network capability;

A control unit, configured to perform QoS control on the heaven-earth integrated network based on the QoS identifier, including: after detecting that the network has no conflict, sending a confirmation message matched with the QoS identifier to the QoS composer; receiving a QoS strategy sent by the QoS orchestrator, wherein the QoS strategy is a strategy of a configuration space node and/or a ground node determined by the QoS orchestrator based on the QoS identification; and sending node configuration information to network forwarding equipment based on the QoS strategy, so that the network forwarding equipment configures space nodes and/or ground nodes based on the node configuration information.

7. A QoS orchestrator, comprising:

the first receiving unit is used for generating a network capability request after receiving the QoS identification request sent by the data source;

a first sending unit, configured to send the network capability request to a QoS converger, so that the QoS converger obtains node functions from network nodes of different network segments of the heaven-earth integrated network as network capabilities;

a second receiving unit, configured to receive a network capability confirmation message sent by the QoS converger, where the network capability confirmation message includes capabilities of each network segment in the heaven-earth integrated network;

A determining unit, configured to determine a QoS identifier match based on capabilities of each network segment included in the network capability confirmation message;

a second sending unit, configured to send the QoS identifier match to the QoS converger, so that the QoS converger performs QoS control on the heaven-earth integrated network based on the QoS identifier;

the QoS orchestrator further comprises a parsing unit for:

after the first receiving unit receives a QoS identification request sent by a data source, analyzing QoS requirements of the data flow, wherein the QoS requirements comprise: the number of 5QI identifications, the priority PL of 5QI and the allocation reservation priority ARP requirement;

accordingly, the determining unit is configured to determine that the QoS identifier matches, specifically, based on the QoS requirement and the capabilities of each network segment included in the network capability confirmation message:

judging whether the number of 5QI identifiers is smaller than or equal to the number of QoS levels indicated in the capacity of each network segment;

if the number of the 5QI identifiers is smaller than or equal to the number of the QoS classes, matching Qn with Cn, wherein Qn is any 5QI identifier, cn is configuration information of a group of network nodes in the heaven-earth integrated network and the group of network nodes;

If the number of the 5QI identifiers is greater than the number of the QoS classes, matching the Qn with the Cn according to the priority PL of the 5QI identifiers, matching data flows which can perform integer division operation on the number of the 5QI identifiers and the number of the QoS classes to appointed QoS classes, and matching data flows which can perform integer division operation on the number of the 5QI identifiers and the number of the QoS classes by 1 to unspecified QoS classes, wherein the appointed QoS classes are QoS classes corresponding to values obtained by taking the remainder operation on the number of the QoS classes according to the difference between the number of the QoS classes and the number of the 5QI identifiers;

after the Qn and Cn are matched, sorting data streams based on the ARP requirement;

traversing in ascending order:

if there is GBR demand and the network node is not a hard pipeline, judging whether the function of the network forwarding equipment meets the GBR demand, if so, trying to match QoS identification based on the function of the network node, if so, trying to match 5QI identification based on the TCP configuration information of the network node, if so, sending a matching failure notice; if the GBR requirement is not met, attempting to match the 5QI identifier based on TCP configuration information, and if the matching fails, sending a matching failure notification;

If the network node is a hard pipeline or the rate per second reaches a rate threshold set by a user, hard pipeline matching is tried, and if matching fails, a matching failure notification is sent.