Method for operating a first network device, first network device and method for operating a communication network

Abstract

A method for operating a first network device, a first network device and a method for operating a communication network are disclosed. A method for operating a first network device of a communication network, wherein the method comprises: determining or receiving (102), by means of an ingress interface, an ingress data stream comprising payload data to be transmitted towards a second network device; determining or receiving (104), by means of an association observer, at least one association value for a plurality of communication paths between the first network device and the second network device, wherein each of the plurality of communication paths comprises a different physical channel of a plurality of physical channels; determining (106), by means of a multi-connectivity controller, a plurality of egress data streams depending on the at least one association value and depending on the ingress data stream; and transmitting (108) via a respective egress queue of a plurality of egress queues, wherein each egress data stream is associated with a different path of a plurality of paths.

Description

Technical Field

[0001] The present invention relates to a method for operating a first network device, the first network device, and a method for operating a communication network. Background Technology

[0002] For example, known multi-connectivity systems in 3GPP only use packet replication to increase transmission reliability. Examples of existing multi-connectivity schemes are multipath TCP or dual-connectivity in 3GPP. Schemes have been proposed in the literature to make path selection in multi-connectivity scenarios based on the association between paths and to use unassociated paths for redundant scheduling [0]. However, current multi-connectivity schemes do not take into account path association for scheduling decisions. Summary of the Invention

[0003] The problems of the prior art are solved by the method for operating the first network device, by the first network device, and by the method for operating the communication network.

[0004] A first aspect of this description relates to a method for operating a first network device in a communication network, the method comprising: determining or receiving an ingress data stream comprising payload data to be transmitted toward a second network device by means of an ingress queue; determining or receiving at least one association value for a plurality of communication paths between the first network device and the second network device by means of an association observer, wherein each of the plurality of communication paths comprises a different physical wireless channel among a plurality of physical wireless channels; determining a plurality of egress data streams by means of a multi-connectivity controller, depending on the at least one association value and depending on the ingress data stream; and transmitting via a corresponding egress queue among the plurality of egress queues, wherein each egress data stream is associated with a different path among the plurality of paths.

[0005] Advantageously, using correlation values ​​for multi-connectivity scheduling decisions improves overall performance in terms of reliability, latency, and efficient resource utilization. It enhances the performance of wireless communication systems in terms of combined latency and reliability metrics, while increasing the efficiency of radio resource utilization. Therefore, information relating to the correlations between utilized links via the physical wireless channel is employed. This information is used to select different multi-connectivity scheduling schemes to improve overall performance and increase resource utilization efficiency.

[0006] Advantageous example features include determining multiple egress data streams by means of a multi-connectivity controller to select whether to partition or replicate the payload data, wherein partitioning includes determining mutually distinct segments of the payload data, wherein the mutually distinct segments are distributed among the multiple egress streams, and wherein replication includes determining replicated segments of the payload data, wherein the replicated segments are fed into each of the multiple egress data streams.

[0007] Dividing the payload data into segments offers the advantage of lower transmission latency, while copying the payload data into replicated segments increases transmission reliability.

[0008] Advantageously, the combination of scheduling and rate adaptation improves overall performance in terms of reliability and latency.

[0009] A favorable example feature is that determining multiple outgoing data streams includes: selecting a partition of the payload data if the association value indicates that multiple communication paths are associated.

[0010] By selecting a partitioning scheme, the mean and tail delays were improved. A robust multi-connectivity transmission scheme was established.

[0011] A favorable example feature is that determining multiple outgoing data streams includes selecting a copy of the payload data if the association value indicates that multiple communication paths are not associated.

[0012] By selecting a replication scheme, mean and tail latency were improved. Furthermore, reliability was increased.

[0013] Advantageous examples are characterized by the method including: receiving or determining QoS requirements for payload data; and determining multiple egress data streams based on the QoS requirements.

[0014] Therefore, applications can indicate their communication requirements via QoS requirements.

[0015] An advantageous example is that at least one association indicator is determined based on delay measurements for multiple physical wireless channels.

[0016] The applicant's research reveals that latency has a strong impact on the performance of different multi-connectivity schemes, such as data partitioning or replication.

[0017] Advantageous examples are characterized in that the method includes: receiving or determining QoS requirements for payload data; and determining and applying at least one configuration parameter for each communication path, depending on the QoS requirements and depending on the associated value, by means of a multi-connectivity controller.

[0018] Advantageously, communication paths are adapted to QoS requirements by merging correlation values ​​from observations of multiple paths. Thus, path adaptation (specifically, individual components of a path) is achieved to meet QoS requirements.

[0019] An advantageous example is that the method includes determining a QoS satisfaction indicator based on QoS requirements and on an associated value, wherein the QoS satisfaction indicator indicates whether the available communication path can satisfy the QoS requirements.

[0020] Advantageously, QoS satisfaction indicators provide applications with a means to decide whether to transmit the payload.

[0021] A further aspect of this description relates to a first network device in a communication network, wherein the first network device is configured to: determine or receive an ingress data stream comprising payload data to be transmitted toward a second network device by means of an ingress queue; determine at least one association value for a plurality of communication paths between the first network device and the second network device by means of an association observer, wherein each of the plurality of communication paths comprises a different physical wireless channel among a plurality of physical wireless channels; determine a plurality of egress data streams by means of a multi-connectivity controller, depending on the at least one association value and depending on the ingress data stream; and transmit the plurality of egress data streams via corresponding egress queues among a plurality of egress queues, wherein each egress data stream is associated with a different path among the plurality of paths.

[0022] The third aspect of this description relates to a method for operating a communication network, the communication network including a first network device and a second network device according to the second aspect. Attached Figure Description

[0023] In the attached diagram:

[0024] Figure 1 A schematic depiction of the sequence diagram;

[0025] Figure 2 and Figure 3 Each schematically depicts a communication network;

[0026] Figure 4 A schematic depiction of a multi-connectivity controller; and

[0027] Figures 5 to 7 Each schematic depicts a scheduling scheme. Detailed Implementation

[0028] Figure 1 A schematic sequence diagram of a first network device for operating a communication network is depicted. According to step 102, an ingress data stream is received or determined, wherein the ingress data stream includes payload data to be transmitted toward the second network device.

[0029] According to step 104, at least one association value for a plurality of communication paths between the first network device 100 and the second network device 200 is received or determined, wherein each of the plurality of communication paths includes a different physical wireless channel among a plurality of physical wireless channels. For example, if the same frequency is used to provide multi-connectivity, different physical channels are provided on the same channel frequency but with spatial diversity.

[0030] In step 106, multiple outgoing data streams are determined based on at least one associated value and based on the ingoing data stream.

[0031] According to step 108, multiple outgoing data streams are transmitted, wherein each outgoing data stream is associated with a different path among multiple paths.

[0032] Figure 2 An example of a communication network 300 is schematically depicted.

[0033] Using the ingress interface ii, an ingress data stream isA, including payload data to be transmitted toward the second network device 200, is received or identified. The first network device 100 may identify the ingress data stream isA itself, or act as a scheduler for the transmission of payload data by receiving the ingress data stream isA.

[0034] The association observer CO receives or determines at least one association value CC for multiple communication paths P1, P2 between the first network device 100 and the second network device 200. Each of the multiple communication paths P1, P2 includes a different physical wireless channel among multiple physical wireless channels pCH1, pCH2. The association observer CO may be housed in the MCC of the first network device or in a remote network device.

[0035] For example, at least one correlation indicator CC is determined based on delay measurements for multiple physical wireless channels pCH1, pCH2. The history of delay measurements is analyzed to determine the correlation indicator CC. A further example of determining the correlation indicator CC is based on measurements of the round-trip time of test packets between a first network device 100 and a second network device 200. The correlation indicator CC is, for example, the Pearson correlation coefficient.

[0036] In another example, at least one association indicator CC is determined based on loss or other metrics. It is even possible to construct a combined association indicator CC from multiple further association indicators.

[0037] Physical wireless channels pCH1 and pCH2 differ, for example, at least in transmission technologies such as Wi-Fi and LTE. According to a further example, physical wireless channels pCH1 and pCH2 differ at least in their transmitting and / or receiving antennas. In another example, physical wireless channels pCH1 and pCH2 differ at least in their frequencies.

[0038] With the help of the multi-connectivity controller MCC, multiple outgoing data streams es1 and es2 are determined based on at least one associated value CC and the ingoing data stream isA.

[0039] The Multi-Connectivity Controller (MCC) selects whether to partition or replicate the payload data. If the association value CC indicates that multiple communication paths P1 and P2 are associated, the MCC selects to partition the payload data. If the association value CC indicates that multiple communication paths P1 and P2 are not associated, the MCC selects to replicate the payload data.

[0040] In other words, based on the path association level provided by the association observer CO, the multi-connectivity controller MCC selects an appropriate packet scheduling scheme, which can be one of the following strategies: packet duplication (PD): duplicating packets and sending copies of them on each path; or packet splitting (PS): breaking packets into smaller pieces (fragments) and sending each fragment on one path.

[0041] The partitioning involves identifying mutually distinct segments of the net load data, which are distributed across multiple outflow flows eq1 and eq2.

[0042] The replication process involves determining replication segments of the payload data, which are then fed into each of the multiple egress data streams eq1 and eq2.

[0043] The Multi-Connectivity Controller (MCC) determines the QoS requirements (QoS) for payload data or receives QoS requirements (QoS) from the application (APP). The MCC determines multiple egress data streams (es1, es2) based on the QoS requirements (QoS). The QoS requirements (QoS) indicate requirements for payload data transmission related to at least one of the following: latency, data transmission rate, etc.

[0044] The QoS requirement for payload data is received from the application (APP) or determined by the multi-connectivity controller (MCC) itself. The MCC determines at least one configuration parameter cP1, cP2 for each communication path P1, P2 based on the QoS requirement and the associated value CC, and applies it to each communication path P1, P2.

[0045] For example, configuration parameters cP1 and cP2 include the transmission data rate for each path P1 and P2, which is achieved by configuring egress queues eq1 and eq2 and egress interfaces EI1 and EI2. In alternative or additional examples, configuration parameters cP1 and cP2 include modulation and coding schemes, sub-channels, transmission power, or other configurable parameters of the egress interfaces EI1 and EI2 of the first network device 100 and the ingress interfaces II1 and II2 of the second network device 200.

[0046] The Multi-Connectivity Controller (MCC) determines the QoS Satisfaction Indicator (QoSi) based on the QoS requirement (QoSi) and the associated value (CC). The QoS Satisfaction Indicator (QoSi) indicates whether the available communication paths P1 and P2 can satisfy the QoS requirement (QoS).

[0047] Multiple exit data streams es1 and es2 are transmitted via the corresponding exit queues in multiple exit queues eq1 and eq2, where each of the exit data streams es1 and es2 is associated with a different path in multiple paths P1 and P2.

[0048] The egress interfaces EI1 and EI2 obtain egress packets em1 and em2 from the corresponding egress queues eq1 and eq2, and transmit the egress packets em1 and em2 to the second network device 200 via physical wireless channels pCH1 and pCH2.

[0049] At the second network device 200 performing reception, the corresponding ingress interfaces II1 and II2 receive ingress packets is1 and is2 corresponding to the egress packets em1 and em2. Ingress queues iq1 and iq2 receive the relevant ingress packets from ingress packets is1 and is2.

[0050] The further multi-connectivity manager MCC2 determines the egress data stream esB based on the received ingress packets is1 and is2. Ingress packets is1 and is2 include reconfiguration indicators that define how the multi-connectivity manager MCC2 constructs a single packet for the egress data stream esB. Therefore, the reconfiguration indicators are inserted by the first network device 100's multi-connectivity manager MCC, depending on the selected scheduling scheme, into the single egress packets em1 and em2 for the egress data streams es1 and es2. The second network device 200 provides the egress data stream esB representing the ingress data stream isA of the first network device 100.

[0051] In the example, communication paths P1 and P2 include outgoing queues eq1 and eq2, outgoing interfaces EI1 and EI2, physical wireless channels pCH1 and pCH2, incoming interfaces II1 and II2, and incoming queues iq1 and iq2. Of course, further queues, channels, and interfaces can be parts of the corresponding paths P1 or P2. Figure 2 Only simple examples of network devices 100 and 200 are shown, which include interfaces EI1, EI2, II1, and II2 to participate in physical wireless channels pCH1 and pCH2. Other examples of network devices 100 and 200 may include interfaces for wired channels to other devices with radio interfaces, thus extending paths P1 and P2, as shown.

[0052] Figure 3An example of a communication network 300 is schematically depicted. In this example, the mobile user is a user equipment (UE), which includes two radio interfaces, Wi-Fi and LTE, based on different radio technologies and / or standards. A multi-connectivity network function (MCNF) is connected via a switch (SW) to a Wi-Fi-capable access point (AP) and an LTE-capable network (LN).

[0053] Therefore, different physical radio channels pCH1 and pCH2 are available on the communication path between the user equipment (UE) and the multi-connectivity network function (MCNF).

[0054] To measure the delay along the communication path, a logical time synchronization channel tsCH is established between the user equipment (UE) and the multi-connectivity network function (MCNF).

[0055] In another example, not shown, the communication network comprises two distinct physical wireless channels along corresponding paths. Two Wi-Fi access points (APs) operate on different frequencies and are connected to a second network device with two Wi-Fi network interface cards (NICs). The APs are connected to a central multi-connectivity controller, and the UE / client has a local multi-connectivity controller. In downlink (DL) operation, the central multi-connectivity controller applies scheduling decisions. The client-side multi-connectivity controller receives and processes data from different paths, making the multi-connectivity scheme transparent to the application. More specifically, in the case of PD, the client selects a copy of the packet, and in the case of PS, the client assembles packet fragments. Flags / indicators in the packet header specify information about one of the application scheduling schemes. Therefore, the client-side multi-connectivity controller knows which operation to perform on the packet to provide the egress data stream.

[0056] In another example not shown, the communication network includes two network devices that together form an adhoc network via at least two wireless physical channels without using an access point.

[0057] Figure 4 The Multi-Connectivity Controller (MCC) is schematically depicted. Decision block 402 selects either Packet Replication (PD) or Packet Segmentation (PS) as the scheduling scheme. The decision is based on the correlation value (CC) and the corresponding threshold, such as 0.5. If there is low correlation between communication paths, Packet Replication (PD) is used, while if there is high correlation between paths, Packet Splitting (PS) or Packet Segmentation is selected.

[0058] According to the example, if the resource indicator indicates that a multi-connectivity scheduling scheme will not be resource efficient, the decision block chooses not to use the multi-connectivity scheduling scheme.

[0059] Based on the selected scheduling scheme ss, packet inspector 404 applies the selected scheduling scheme ss to the packets being inspected. The inspected packets are either inserted into the corresponding egress queue or segmented into new packets, with the new packets being inserted into the corresponding egress queue.

[0060] Based on the selected scheduling scheme ss, the configurator 406 selects the corresponding path configuration, such as the transmission rate of the corresponding path.

[0061] According to transport block 408, the packets in the egress queue are transmitted toward the second network device.

[0062] For example, the application's QoS requirements are used as additional input. The Multi-Connectivity Controller (MCC) stores the history of previous packets, including receive and / or transmit times. Based on this history, the MCC determines latency-reliability curves for different communication paths. The MCC selects a scheduling scheme that meets the application's latency requirements (QoS requirements) and provides increased reliability.

[0063] Multi-connectivity at the physical layer can be implemented in different ways. One alternative is by transmitting application information to the client from multiple independent antennas in the downlink. For example, even if two access points or antennas send information to the client on the same physical resources, the paths are considered different. When handling multi-connectivity at the PHY layer, if the paths are correlated, such as CC > 0.5, the multi-connectivity controller (MCC) decides to apply PD. This decision is made because it is impossible to distinguish between different packets at the PHY layer when the correlation between communication paths is high. On the other hand, if the correlation between communication paths is low, such as CC < 0.5, the multi-connectivity controller (MCC) has the freedom to decide whether to use PS or PD. For the final decision, additional information about the application's QoS requirements is used. If reliability is relevant, PD is used at the cost of lower throughput. If a high data rate is required, PS is chosen as the scheduling scheme.

[0064] Figures 5 to 7 Each of the diagrams schematically depicts a different scheduling scheme. Figure 5 This illustrates a load balancing scheme where the ingress data stream comprises packets that are alternately directed to different paths. Figure 6 This illustrates a packet replication scheme where each path receives a replicated packet from the ingress data stream. Figure 7 The diagram illustrates a packet splitting scheme where each packet in the ingress flow is split into a first part and a second part. The first and second parts are then routed to different paths. When the multi-connectivity controller chooses to split the payload data, it selects... Figure 5 or Figure 7The scheduling scheme. When the multi-connectivity controller chooses to replicate payload data, it then selects... Figure 6 The scheduling scheme.

Claims

1. A method for operating a first network device in a communication network, the method comprising: The ingress data stream, including the payload data to be transmitted toward the second network device, is determined by using the ingress interface. At least one correlation value is determined by means of a correlation observer for multiple communication paths between a first network device and a second network device, each of the multiple communication paths including different physical channels among multiple physical channels, and the at least one correlation value is determined based on a loss metric of the multiple physical channels; With the aid of a multi-connectivity controller, multiple outgoing data streams are determined based on the at least one association value and based on the ingoing data streams, wherein determining the multiple outgoing data streams includes selecting, with the aid of the multi-connectivity controller, whether to partition or replicate the payload data, wherein partitioning the payload data is selected when the association value indicates that the multiple communication paths are associated, and wherein replication of the payload data is selected when the association value indicates that the multiple communication paths are not associated. as well as The multiple outgoing data streams are transmitted via corresponding outgoing queues in a plurality of outgoing queues, wherein each outgoing data stream is associated with a different path in the plurality of communication paths.

2. The method according to claim 1, The partitioning process includes identifying distinct segments of the payload data, which are distributed across the multiple outgoing data streams. The replication process includes determining replication segments of the payload data, wherein the replication segments are fed into each of the plurality of exit data streams.

3. The method according to claim 1, wherein, The method includes: Determine the QoS requirements for payload data; and The multiple egress data streams are determined based on QoS requirements.

4. The method according to claim 1, wherein, At least one association indicator is determined based on delay measurements for the plurality of physical channels.

5. The method according to claim 1, wherein, The method includes: Determine the QoS requirements for payload data; and With the help of a multi-connectivity controller, at least one configuration parameter is determined and applied for each communication path, depending on QoS requirements and the associated value.

6. The method according to claim 1, wherein, The method includes: The QoS satisfaction indicator is determined based on the QoS requirements and the associated value. The QoS satisfaction indicator indicates whether the available communication path can meet the QoS requirements.

7. A first network device for a communication network, wherein, The first network device includes: The ingress interface is configured to use an ingress queue to determine the ingress data stream, which includes payload data to be transmitted toward the second network device. An association observer is configured to determine at least one association value for a plurality of communication paths between a first network device and a second network device, wherein each of the plurality of communication paths includes a different physical channel among a plurality of physical channels, and wherein the at least one association value is determined based on a loss metric of the plurality of physical channels. A multi-connectivity controller is configured to determine multiple outgoing data streams based on the at least one association value and on the ingoing data streams, wherein determining the multiple outgoing data streams includes selecting, by means of the multi-connectivity controller, whether to partition or replicate the payload data, wherein partitioning the payload data is selected when the association value indicates that the multiple communication paths are associated, and wherein replication of the payload data is selected when the association value indicates that the multiple communication paths are not associated; and An egress interface is configured to transmit the plurality of egress data streams via corresponding egress queues in a plurality of egress queues, wherein each egress data stream is associated with a different path in the plurality of communication paths.

Images