WO2022005346A1

WO2022005346A1 - Method for scheduling multiple replicated data flows over a number of wireless transmission paths

Info

Publication number: WO2022005346A1
Application number: PCT/SE2020/050680
Authority: WO
Inventors: Ying Sun; Torbjörn WIGREN
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2020-06-29
Filing date: 2020-06-29
Publication date: 2022-01-06

Abstract

A method performed by first network node for determining a number of paths in a communication between a second network node and a Wireless Device (WD) in a wireless communications network is provided. The first network node obtains (401) 5service requirements on a communication service provided to the WD. The service requirements comprise a latency requirement and error rate requirement. The first network node determines (402) the number of paths for the communication based on the obtained service requirements. Each path out of the number of paths, is to be scheduled for a respective replicated data transmission. The first network node determines (403) 10path specific operation target parameters for each respective replicated data transmission. The determination is based on the determined number of paths and the service requirements. The respective path specific operation target parameter comprises at least a (BLER) target and a maximum latency. The first network node sends (404) a request to the second network node. The request requests transmission of replicated data 15of each path of the number of paths, according to the path specific operation target parameters.20Publ.

Description

METHOD FOR SCHEDULING MULTIPLE REPLICATED DATA FLOWS OVER A NUMBER OF WIRELESS TRANSMISSION PATHS

TECHNICAL FIELD

Embodiments herein relate to a first network node, a second network node and methods therein. In some aspects, they relate to determining a number of paths to be used by a Wireless Device (WD) in a communication via the second network node in a wireless communications network.

BACKGROUND

In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and/or User Equipments (UE), communicate via a Local Area Network such as a W-Fi network or a Radio Access Network (RAN) to one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a W-Fi access point or a radio base station (RBS), which in some networks may also be denoted, for example, a NodeB, eNodeB (eNB), or gNB as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on radio frequencies with the wireless device within range of the radio network node.

Specifications for the Evolved Packet System (EPS), also called a Fourth Generation (4G) network, have been completed within the 3rd Generation Partnership Project (3GPP) and this work continues in the coming 3GPP releases, for example to specify a 5G network also referred to as 5G New Radio (NR). The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E-UTRAN/LTE is a variant of a 3GPP radio access network wherein the radio network nodes are directly connected to the EPC core network rather than to RNCs used in 3G networks. In general, in E- UTRAN/LTE the functions of a 3G RNC are distributed between the radio network nodes, e.g. eNodeBs in LTE, and the core network. As such, the RAN of an EPS has an essentially “flat” architecture comprising radio network nodes connected directly to one or more core networks, i.e. they are not connected to RNCs. To compensate for that, the E- UTRAN specification defines a direct interface between the radio network nodes, this interface being denoted the X2 interface.

URRLC

The NR standard in 3GPP is being designed to provide service for multiple diverse use cases such as Enhanced Mobile Broadband (eMBB), Ultra Reliable and Low Latency Communication (URLLC), and Machine Type Communication (MTC). These services may have vastly different technical requirements. In a distinguishing example, a general requirement for eMBB may comprise of very high data rate with moderate latency and moderate coverage, while URLLC services may require very low latency and very high reliability transmission but instead may only require moderate data rates as exemplified in Table 1 below.

The performance requirements in URLLC are enhanced from requirements of 4G mobile broadband capacity and spectral efficiency, to further include more stringent requirements on low latency and high reliability. E.g. the latency requirements may be lower than one millisecond (ms) and the reliability requirements may involve packet loss fi A probabilities as low as 10 to 10 . In order to achieve these requirements, significant re design, of previous mobile broadband systems e.g. 4G is thus necessary. Some concerns regarding reliability and latency in these types of emerging technologies and use cases will be discussed below.

Example use cases for URLLC appear in the area of Critical Machine Type Communications (C-MTC), e.g. automotive safety such as platooning or automatic braking, factory automation using wireless feedback loops for achieving manufacturing flexibility, Augmented Reality (AR) and Virtual Reality (VR) for remote sensing or tactile feedback transmitted using NR. Some of these and more use cases are exemplified in R. H. Middleton, T. Wigren, L. Bostrom, R. A. Delgado, K. Lau, R. Karlsson, L. Brus and E. Corbett, "Feedback control applications in new radio - exploring delay control and alignment", IEEE Vehicular Technology Magazine, vol. 14, no. 2, pp. 70-77, June, 2019. DOI: 10.1109/MVT.2019.2892495.

Reliability Mobile broadband transmission systems are optimized for operation at a Block-Error

2

Rate (BLER) of 1-10%. As such, without re-transmission, error rates as low as 10 may be achievable in these systems. Today, there is no realizable way to improve these error rates as to have a BLER e.g. as low as 10 would require data collection over an immense number of Transmission Time Intervals (TTIs) which adds up to three hours for data which is clearly infeasible as compared to the radio channel variation rate collection. TTI of 1 ms is exemplified for motion control in the below Table 1.

Table 1: 3GPP delay and reliability requirement examples.

Above applications all share requirements to meet both the delay and jitter requirements and at the same time the reliability requirement in terms of lost packets e.g. as seen in Table 1 are met.

A packet loss may be defined as either a lost packet or a packet received at the application layer with longer delay than a required delay budget required by the target application. In this case, e.g. C-MTC applications, may require real time feedback in control loops. In these cases, a packet loss may therefore be caused due to a late control or feedback signal. This is since feedback control needs to be based on the current system state which may not be available or may not able to respond in time. Delayed actions or measurements when performing feedback control thus provides past information which may already be expired or not relevant. Furthermore, delay in feedback control systems may easily lead to instability of the system.

Latency

Low latency data transmission as needed by e.g. URLLC services may be achieved by shortening the transmission time intervals. A way of achieving this, may be to utilize data transmissions of mini slots as depicted in Figure 1. A mini-slot transmission available in NR may comprise only one, but up to 14 Orthogonal Frequency-Division Multiplexing (OFDM) symbols or resource elements wherein a standard slot comprises 14 OFDM symbols. In addition to this, NR further includes high band carrier frequencies, including numerologies that offer up to 16 times wider subcarrier frequencies, together with up to 16 times finer time granularity for data transmission.

The latter property makes Millimetre Wave (mmW) technology, i.e. very high frequency e.g. gigahertz (GHz) bands, particularly useful for technologies such as URLLC. E.g. when using a Sub-Carrier Spacing (SCS) equal to 120 kilohertz (kHz), if a TTI length equal to a slot length which is 0.125ms, the transmission time over the air is four times lower compared to midband network with a subcarrier spacing equal to 30kHz.

Brief overview of 5G NR Physical layer design

3GPP is defining technical specifications for NR, e.g., 5G. In Release 15 NR, a user equipment (UE) may be configured with up to four carrier Bandwidth Parts (BWP) in the downlink with a single downlink carrier bandwidth part being active at a given time. A UE may be configured with up to four carrier BWPs in the uplink with a single uplink carrier BWP being active at a given time. If a UE is configured with a supplementary uplink, the UE may additionally be configured with up to four carrier BWPs in the supplementary uplink with a single supplementary uplink carrier bandwidth part being active at a given time.

For a carrier bandwidth part with a given numerology |Jj, a contiguous set of

Physical Resource Blocks (PRBs) are defined and numbered from

, where i is the index of the carrier bandwidth part. A resource block (RB) is defined as 12 consecutive subcarriers in the frequency domain. Numerologies

Multiple OFDM numerologies, m, may be supported in NR as given by Table 2 below, where the SCS, Af kHz, and the cyclic prefix for a carrier bandwidth part are configured by different higher layer parameters for Downlink (DL) and Uplink (UL), respectively.

Table 2: Supported transmission numerologies. Physical Channels

A downlink physical channel corresponds to a set of resource elements carrying information originating from higher layers. Following downlink physical channels are defined: Physical Downlink Shared Channel (PDSCH), Physical Broadcast Channel (PBCH), and Physical Downlink Control Channel (PDCCH). PDSCH is the main physical channel used for unicast downlink data transmission, but also for transmission of Random Access Response (RAR), certain system information blocks, and paging information.

PBCH carries the basic system information, required by the UE to access the network. PDCCH is used for transmitting Downlink Control Information (DCI), mainly scheduling decisions, required for reception of PDSCH, and for uplink scheduling grants enabling transmission on PUSCH.

An uplink physical channel corresponds to a set of resource elements carrying information originating from higher layers. The following uplink physical channels are defined: Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), and Physical Random Access Channel (PRACH).

PUSCH is the uplink counterpart to the PDSCH.

PUCCH is used by UEs to transmit uplink control information, e.g. Hybrid Automatic Repeat Request (HARQ) acknowledgements and channel state information reports. PRACH is used for random access preamble transmission. An example contents of a DL DCI is further explained in 3GPP TS 38.214 version 16.0.0 is shown below.

DCI format 1_0 with Cyclic Redundancy Check (CRC) scrambled by Radio Network Temporary Identifier (RNTI), e.g. Cell RNTI (C-RNTI) or Configured Scheduled (CS-RNTI) may comprise the following features:

Frequency domain resource assignments using

is the size of the active DL bandwidth part in case DCI format

1_0 is monitored in the UE specific search space and satisfying:

- the total number of different DCI sizes configured to monitor is no more than 4 for the cell, and

- the total number of different DCI sizes with C-RNTI configured to monitor is no more than 3 for the cell

- otherwise, the size of CORESET 0.

-Time domain resource assignment using 4 bits as defined in Subclause 5.1.2.1 of [6, TS 38.214]

VRB-to-PRB mapping - 1 bit according to T able 7.3.1.1.2-33 Modulation and coding scheme - 5 bits as defined in Subclause 5.1.3 of [6,

TS 38.214]

New data indicator - 1 bit

Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2 HARQ process number - 4 bits

Downlink assignment index - 2 bits as defined in Subclause 9.1.3 of [5, TS

38.213], as counter DAI

TPC command for scheduled PUCCH - 2 bits as defined in Subclause 7.2.1 of [5, TS 38.213]

PUCCH resource indicator - 3 bits as defined in Subclause 9.2.3 of [5, TS

38.213]

PDSCH-to-HARQ_feedback timing indicator - 3 bits as defined in Subclause 9.2.3 of [5, TS38.213]

Multi-connectivity In order to achieve the reliability e.g. as required by some URLLC services, this requires multiple transmissions over the wireless interfaces. These transmissions may be performed as depicted in Figure 2a, where data may be split at the Packet Data Convergence Protocol (PDCP) layer. In this way, URLLC data is replicated at the PDCP layer and two Radio Link Control (RLC) entities in different cell groups carries replicated packets and transmits via different band and air interfaces independently.

Alternatively, multi-connectivity may be achieves as depicted in Figure 2b, where URRLC packets at PDCP layer may be replicated using a carrier aggregation approach.

In this way, incoming data flow may be replicated data streams, to be transmitted over two RLC entities at different carriers in different band.

Both of these alternatives provide packet replication at higher layer and transmission independently at different air interface paths in different frequency. However, in these cases, the PDCP replication above is solely aimed to ensure that the network fulfills URLLC availability requirements.

A problem arises when adopting URLLC services with both extremely low latency and ultra high reliability requirements. These extreme cases as described in 3GPP is to support an end to end latency of 1ms or less with a high reliability with errors or packet loss of at most 10⁵ where some use cases have been mentioned above.

With a latency less than 1ms, retransmission in time domain by utilizing different protocol layers may however not be possible e.g. due to time constraints.

SUMMARY

As a part of developing embodiments herein a problem was identified by the inventors and will first be discussed.

A way to partly solve the above mentioned problem, is to apply a robust link adaptation to support BLER at the physical layer equal to the reliability requirement at application layer, e.g. BLER=PER=10⁵, in this way, retransmissions are not necessary since the reliability requirement is met by the physical layer. To support such low BLER requires extremely robust link adaptation with low coded rate and Modulation Coding Scheme (MCS), which may be obtained by performing link adaptation via large Signal to Noise Ratio (SI NR) backoff. This solution however may cause a high waste of SI NR, which indicates a poor spectrum efficiency and unpredictable inaccuracy of channel estimation and link adaptation. In order to alleviate full potential of mobile communications systems in order to meet the requirements of URLLC services demanding extremely low latency and ultra high reliability, it is necessary to optimize the use of each available resource efficiently.

Contrary to this insight, in prior art, there has been no way to schedule URLLC traffic so that packets are replicated using multipath for replicated transmissions in order to improve reliability via repetitions or replications of simultaneous transmission.

In particular there is no scheduling functionality known in prior art that handles:

Scheduling of multiple data flows (or users), over a predetermined number of wireless transmission paths, where said data flows consist of replicated data, at least one replicated data item to be sent over any of said transmission paths,

Scheduling of URLLC data of users, where the replicated data is subject to simultaneous reliability and latency constraints, and

Scheduling of URLLC data of users, where the replicated data is subject to either replication over frequency or repetition over time.

Furthermore, the scheduling achieves better control of the performance, selection and target of multiple paths.

Hence, in order to achieve a high reliability, e.g. of 10⁶ or less errors or packet loss, without any path being able to deliver this high reliability e.g. due to too high BLER, it may become necessary to split up the reliability over many different paths and achieve the reliability by aggregation of many less reliable paths. In this way, it may be possible to use multiple paths of lower reliability, as long as transmissions are precisely scheduled which will be further explained. Hence, this poses a problem of how to schedule replicated multipath transmissions precisely to achieve an overall service requirements of maximum latency and reliability when delegating part of the reliability into e.g. less reliable multiple paths.

An object of embodiments herein is to provide a mechanism for improving the performance of a communications network using multipath data transmissions.

According to an aspect of embodiments herein, the object is achieved by a method performed by a first network node for determining a number of paths in a communication between a second network node and a Wireless Device, WD, in a wireless communications network. The first network node obtains service requirements on a communication service provided to the WD. The service requirements comprises a latency requirement and error rate requirement. The first network node determines the number of paths for the communication based on the obtained service requirements.

Each path out of the number of paths, is to be scheduled for a respective replicated data transmission. The first network node determines path specific operation target parameters for each respective replicated data transmission. The determination is based on the determined number of paths and the service requirements. The respective path specific operation target parameter comprises at least a Block Error Rate, BLER, target and a maximum latency. The first network node sends a request to the second network node. The request requests transmission of replicated data of each path of the number of paths, according to the path specific operation target parameters.

According to another aspect of embodiments herein, the object is achieved by a method performed by a second network node for handling a number of paths between the second network node and a Wireless Device, WD, in a wireless communications network. The second network node receives a request from a first network node. The request requests transmission of replicated data according to an operation target parameter specific for each path of the number of paths. The path specific operation target parameter comprises, at least a Block Error Rate, BLER, target and a maximum latency. For each respective replicated data transmission of each path, the second network node schedules radio resources. The second network node performs individual link adaptation based on the respective path specific operation target parameter in the request.

According to another aspect of embodiments herein, the object is achieved by a first network node configured to determine a number of paths in a communication between a second network node and a Wreless Device, WD, in a wireless communications network. The first network node is further configured to:

- obtain service requirements on a communication service provided to the WD, wherein the service requirements are adapted to comprises a latency requirement and error rate requirement,

- determine the number of paths for the communication based on the obtained service requirements, where each path out of the number of paths, is adapted to be scheduled for a respective replicated data transmission,

- determine path specific operation target parameters for each respective replicated data transmission, based on the determined number of paths and the service requirements, which respective path specific operation target parameter is adapted to comprise at least a Block Error Rate, BLER, target and a maximum latency, and

- send a request to the second network node, the request being adapted to request a transmission of replicated data of each path of the number of paths, according to the path specific operation target parameters.

According to another aspect of embodiments herein, the object is achieved by a second network node configured to handle a number of paths between the second network node and a Wireless Device, WD, in a wireless communications network. The second network node is further configured to:

- receive a request from a first network node, the request being adapted to request transmission of replicated data according to an operation target parameter specific for each path of the number of paths, which path specific operation target parameter is adapted to comprise, at least a Block Error Rate, BLER, target and a maximum latency, and

- for each respective replicated data transmission of each path, schedule radio resources and perform individual link adaptation based on the respective path specific operation target parameter in the request.

Since the first network node determines the number of paths to be scheduled for a respective replicated data transmission, further determines a path specific operation target parameter based on the number of paths and the service requirement, and requests the second network node to communicate replicated data of each of the number of paths according to the path specific operation target parameters, the second node is enabled to handle communication with the WD according to the path specific operation target parameters, and thus, scheduling radio resources, performing link adaptation and communicating replicated data of each path individually, based on the service requirements and the determined number of nodes.

This results in an efficient way to schedule replicated multipath transmissions precisely to achieve overall service requirements and thus provides a mechanism for improving the performance of a communications network using multipath data transmissions.

BRIEF DESCRIPTION OF THE DRAWINGS Examples of embodiments herein are described in more detail with reference to attached drawings in which:

Figure 1 is a schematic block diagram illustrating prior art. Figure 2a is a schematic block diagram illustrating prior art. Figure 2b is a schematic block diagram illustrating prior art. Figure 3 is a schematic block diagram illustrating embodiments of a wireless communications network.

Figure 4 is a flowchart depicting embodiments of a method in a first network node Figure 5 is a flowchart depicting embodiments of a method in a second network node Figure 6 is a schematic block diagram depicting embodiments herein Figure 7 is a schematic block diagram of embodiments herein Figures 8 a and b are schematic block diagrams illustrating embodiments of a first network node. Figures 9 a and b are schematic block diagrams illustrating embodiments of a second network node.

Figure 10 schematically illustrates a telecommunication network connected via an intermediate network to a host computer.

Figure 11 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection.

Figures 12-15 are flowcharts illustrating methods implemented in a communication system including a host computer, a base station and a user equipment.

DETAILED DESCRIPTION

Examples of embodiments herein relate to URLLC multi-path transmissions with relaxed link adaptation.

Examples of embodiments herein provide simultaneous scheduling of multiple replicated data over multiple independent air interfaces with independent link adaptation. These may further operate using more relaxed HARQ operating point than the application layer reliability requirement, e.g. the packet error rate.

In some embodiments the HARQ operating point of each replicated transmissions e.g. being a function of the number of transmission paths and the reliability requirement of the service. In some embodiments each replicated transmission path may e.g. use PDCP replication with dual connectivity or carrier aggregation at different frequency.

In some embodiments each replicated transmission paths may e.g. use a different transmission point, such as distributed antenna ports at different spatial resources.

In some embodiments replicated transmissions may be communicated at different time instances.

Embodiments herein enables a systematic scheduling of URLLC traffic taking into consideration a plurality of URLLC related parameters, replicated over multiple data paths. By using simultaneous or multiple transmissions of replicated packets at varying time differences, the strict reliability requirement in a small delay budget when a data or packet should be communicated is met. This is since simultaneous independent replicated transmissions increase the reliability.

By replicating transmissions at multiple paths, each path transmission link may be adapted using wide range radio conditions independently, e.g. based on the carefully designed HARQ operating points of each independent path. This is since in some embodiments herein, when using the service requirements such as e.g. a Quality of Service (QoS) reliability requirement or e.g. a Packet Error Rate (PER) in the application layer, it is possible to reach an aggregated reliability achieved after the combination of different transmissions paths. By carefully scheduling each path and adapting the link of each path individually, no large SINR margin is needed, and thus, a higher spectrum may be achieved.

Furthermore, some embodiments herein allow e.g. repetition over time, frequency or spatial, to be optimally combined, thereby ensuring a high capacity for an URLLC scheduler.

Embodiments herein relate to wireless communication networks in general. Figure 3 is a schematic overview depicting a wireless communications network 100. The wireless communications network 100 comprises one or more RANs and one or more CNs. The wireless communications network 100 may use a number of different technologies, such as Wi-Fi, LTE, LTE-Advanced, 5G, NR, Wdeband Code Division Multiple Access (WCDMA), Global System for Mobile communications/enhanced Data rate for GSM Evolution (GSM/EDGE), Worldwide Interoperability for Microwave Access (WMAX), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations. Embodiments herein relate to recent technology trends that are of particular interest in a 5G context, however, embodiments are also applicable in further development of the existing wireless communication systems such as e.g. WCDMA and LTE.

A number of network nodes operate in the wireless communications network 100 such as e g. a first network node 111, and a second network node 112 for e g. handling or controlling a communication between the second network node 112 and a wireless device, WD 120.

The second network node 112 may provide radio coverage e.g. in a number of cells which may also be referred to as a beam or a beam group of beams, provided by the second network node 112 for communication with a wireless device, WD 120.

The first network node 111, may be located in RAN, Core or both. The second network node 112, may be located in RAN In some embodiments the network nodes 111,

112 are collocated. In this way, the functionality of the first network node 111 and the second network node 112 may be performed in different software processes executing independently to each other.

The first network node 111, may be part of a base station e.g. an eNB, a gNB or may be part of the core network, e.g. a control unit or control node. The first network node 111 may be in communication with the second network node 112, e.g. for controlling a communication between the second network node 112 and the WD 120.

The second network node 112 may be any of a NG-RAN node, a transmission and reception point e.g. a base station, a radio access network node such as a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, a base station, e.g. a radio base station such as a NodeB, an evolved Node B (eNB, eNodeB), a gNB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit capable of communicating with a wireless device within the service area served by the second network node 112 depending e.g. on the first radio access technology and terminology used. The second network node 112 may be referred to as a serving radio network node and communicates with the WD 120 with DL transmissions to the WD 120 and UL transmissions from the WD 120. The second network node 112 may further be able to communicate with the first network node 111 using e.g. X2 interface. The multipath transmission may be within one logical cell. In some embodiments the multipath transmission may be distributed in different cells. One or more WDs operate in the wireless communication network 100, such as e.g. the WD 120. The WD 120 may also referred to as a device, an loT device, a mobile station, a non-access point (non-AP) STA, a STA, a UE and/or a wireless terminal, communicate via one or more Access Networks (AN), e.g. RAN, to one or more core networks (CN). It should be understood by the skilled in the art that “wireless device” is a non-limiting term which means any terminal, wireless communication terminal, user equipment, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station communicating within a cell.

Methods herein may be performed by the first and second network nodes 111, 112. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in a cloud 130 as shown in Figure 3, may be used for performing or partly performing the methods herein.

The above described problem is addressed in a number of embodiments, some of which may be seen as alternatives, while some may be used in combination.

Figure 4 shows example embodiments of a method performed by the first network node 111 for determining a number of paths in a communication between the second network node 112 and the WD 120 in a wireless communications network 100. The method comprises the following actions, which actions may be taken in any suitable order. The term communicate data or communicating data when used herein means to receive or transmit data.

Action 401

According to an example scenario, the first network node 111 will determine a number of paths to be used for a communication between the WD 120 and the second network node 112. In order to be able to decide the number of paths to be used, the first network node may need to be informed about the service requirements of the communication and the status of the communication network e.g. available paths, used paths, second network node, WD, previous communications, and radio conditions.

Hence, the first network node 111 obtains service requirements on a communication service provided to the WD 120, wherein the service requirements comprise a latency requirement and error rate requirement. The obtaining of service requirements may in some embodiments be an initial service requirement, part a received feedback, or both.

In some embodiments the service requirements on the communication service provided to the WD 120, further may comprise any one or more out of:

- URRLC QoS requirements e.g. relating to latency and reliability requirements,

- a Packet Error Rate, PER, e.g. relating to a current PER or a maximum PER requirement,

- a Packet Delay Budget (PDB), e.g. relating to an end to end latency requirement,

- a packet size, e.g. size of the data to be communicated,

- a jitter requirement, e.g. relating to the time variation to be allowed for the communication or each transmission, and a network configuration, e.g. relating to how the network nodes 111, 112 and the WD 120 are configured and set up individually or how they are connected.

Furthermore, in some embodiments the service requirements may also comprise any one or more out of: reliability requirement, latency requirement, and QoS requirement

In this way, the first network node 111 may be informed of e.g. which limitations or constraints that the communication need to adhere to. Using this information, the first network node 111 is now enabled to e.g. determine the how many paths are necessary to meet provide communication according to the service requirements.

Action 402

The first network node 111 determines the number of paths for the communication based on the obtained service requirements, where each path out of the number of paths, is to be scheduled for a respective replicated data transmission.

The wording replicated data transmissions when used herein may be a replicated packet in another protocol layer, e.g. a replicated PDCP packet or e.g. a replicated RLC SDU. Replicated data transmission may e.g. mean duplicated or copied data transmissions, into more than one identical or similar data transmissions. In some embodiments replicated data transmission may refer to at least one additional data stream identical to e.g. incoming data, such that the identical data may be communicated over a different set of frequencies in frequency band or over different frequency bands from the incoming data.

A transmission path may be defined based on any one or more out of different time, frequency, spatial resource that are used to communicate the replicated data. The transmission path may be different frequency bands, carriers, cells, Transmission Reception Points (TRP) belonging to one or multiple cells, antenna ports, BWP within the same carrier, PRBs, or different time instance. The number of paths may be determined based on that a plurality of paths may achieve a greater reliability aggregated than each individual path reliability capability, e.g. BLER.

In some embodiments the number of paths may be determined based on the channel quality of each individual path that may fulfil the reliability requirement of one or more individual paths.

In some embodiments the number of paths may be based on the network configuration, e.g. in which the multiple Transmission and Reception Points (TRP) may be configured.

In some embodiments, the number of paths may be obtained e.g. by a network event. E.g. during a handover event, one or more new transmission paths from a target cell may added.

Therefore, in some embodiments the determining the number of paths may be based on achieving a low aggregated reliability target, e.g. BLER target for each path by distributing the required error rate multiplicatively between uncorrelated or independent paths for replicated data transmission. In this way, three independent data paths operating with e.g. BLER 10² may thus result in an aggregated error rate of 10⁶ =

(1 O ²)³ since all transmissions would need to fail to result in an aggregated.

In some embodiments the determination may further or instead be based on using a minimal number of paths by targeting paths with specific reliability capability e.g. a channel quality, e.g. a SINR, is above certain threshold. In this way, the number of paths may be determined by determining a number of paths for which aggregated error rate corresponds to the reliability of the service requirement.

In some embodiments, the determining of number of paths may further also be based on the latency requirement, e.g. in a PDB or URLLC QoS of the service requirements. In this way, the number of paths may further be determined based on that the determined number of paths meet the service requirement with regards to their aggregated latency and reliability capabilities.

This determination may further take into account that each of the paths have individual capabilities, e.g. differing latency and differing reliability compared to other paths. In this way, it is possible to determine the number of paths using the capabilities of each path individually with regards to the service requirement using some arithmetic or optimization function. In some embodiments the first network node 111 may decide individual path capability by checking if the BLER of each individual paths has met the individual residual BLER target after allowed number of retransmissions within the time budget, e.g. the PDB.

In some embodiments the first network node 111 may decide individual path capability by determining if the channel quality is above or below a threshold.

Action 403

The network node 111 determines path specific operation target parameters for each respective replicated data transmission, based on the determined number of paths and the service requirements. The respective path specific operation target parameter comprises at least a Block Error Rate (BLER) target and a maximum latency. This may be in order to further establish the target for what each path may need to perform with regards to a maximum latency and reliability constraints e.g. such that all of the paths aggregated meet the service requirement.

In this way, each path is now enabled to schedule and perform link adaptation with regards to individual target specific operation parameters. Thus all the paths together may be able to meet the service requirement by each path only considering its individual path specific operation target parameter.

In some embodiments, the BLER target may be a residual BLER target after the maximum number of time domain retransmission that is allowed by a time budget e.g.

PDB or maximum latency.

In some embodiments, the path specific operation target parameters further comprises, for each respective replicated data transmission path, information related to a HARQ, operating point, and a maximum number of time domain retransmissions.

In this way, each path is enabled to guarantee the required service quality requirement of each individual path, and are thus also enabled to perform replicated data transmission consistent with the momentary capability of the radio channel.

Action 404

The first network node 111 sends a request to the second network node 112 requesting transmission of replicated data of each path of the number of paths, according to the path specific operation target parameters. Accordingly, the second network node 112 is thus informed of which paths are chosen for replicated data transmission, and their associated path specific operation target parameters. Action 405

In some embodiments, the first network node 111 may further receive feedback from the second network node 112. The feedback is related to estimations in relation to the service requirements of the transmission of each of the replicated data of each path of the number of paths when communicated according to the determined path specific operation target parameters.

The estimations may relate to an actual service quality, e.g. BLER or SINR of each individual path. The estimations may further or instead relate to how difficult it is to meet the path specific operation target parameters and may be a generalized measure based on the path specific, free traffic capacity, and signal quality, wherein the measure may be generalized over several specific parameters and over time.

Thus, the first network node 111 may thus be enabled to evaluate each path in relation to a previous transmission request.

In some embodiments the feedback further comprises indications indicating for each of the path of the number of paths the feasibility of providing the communication according to the service requirements. This provides a way to indicate which paths are better to use for transmission and may include a determination whether or not the BLER of the individual path may meet the BLER target designed for the path. In some embodiments, a BLER not meeting the target, may indicate the respective path is associated with lower channel quality and may thus have harder to meet e.g. the service requirement.

In some embodiments the feedback further comprises a SINR or channel quality information for each available transmission paths in the second network node 112. In this way, the first network node 111 may more efficiently select which paths to be comprised within the determined number of paths Furthermore, the SINR or channel quality information may be used for selecting which path to use for data path capability and replicated data transmission capacity assessment.

The received feedback may further relate to current or previous communication of data over one or more transmissions of e.g. replicated data. The feedback may also relate to available transmission paths or unused network resources.

The feedback may further comprise the resource utilization of each individual path for the services belonging to e.g. the same QoS classes or interference statistics of each PRB of the individual transmission path. The interference statistics may be a wideband average value of interference of all PRBs and may be filtered over time. In some embodiments, the feedback may further comprise SINR, interference and noise estimates, obtained by signal processing on e.g. Demodulation Reference Signals (DMRS).

Action 406

When receiving the feedback, the first network node 111, may evaluate the paths. The reliability associated with each path may be determined and furthermore, one or more preferred or high performance paths may be determined. The feedback may also relate to the service requirements by indicating whether or not the number of paths are meeting the service requirements by e.g. comparing the estimated WD 120 service PER with a PER target.

In some embodiments the estimated WD 120 service PER is obtained by combining statistics of BLER measurements of individual transmission paths.

In some embodiments the number of paths may be restricted not only by capability of the selected paths to meet the overall service requirement, and by an estimated capability of a candidate path to improve on the overall service requirement but also the WD 120 may have a limitation in the number of paths used for communication, or in capacity for communicating over certain frequency carriers and bandwidth parts.

Based on the feedback, first network node 111, may adjust the number of paths for the communication, where each path out of the number of paths, is to be scheduled for a second respective replicated data transmission.

In this way, the feedback sent from the second network node 112 e.g. at least partly determines how the first network node 111 determines the number of paths to use for further communication between the second network node 112 and the WD 120.

In some embodiments, the first network node 111 adjusts the number of paths for the communication based on the indications for all of the path of the number of paths, based on an aggregated feasibility of providing the communication according to the service requirement with the adjusted number of paths. This enables a way to determine whether or not a number of paths e.g. comprising a specific set of paths is expected to meet the service requirements with regards to their individual path capabilities. Furthermore, the adjusting of the number of paths may be performed by excluding or including some paths in the adjusting number of paths by, based on channel quality measurement of each path, feedback or both.

In some embodiments, adjusting the number of paths may be performed by defining an optimization problem, using e.g. the Shannon formula for writing the aggregated capacity as a function of the SI NR, the number of replicated data transmission paths, the number of repetitions for each data path, and the frequency resources available for scheduling. In this way, the optimization problem may be subject to maximum delay constraints.

In some embodiments the first network node 111 may select e.g. a first transmission path with the strongest channel quality or larger than a certain threshold. In some embodiments one or more paths are selected if their channel quality measurement is within an interval of the channel quality measurement of the first path’s channel quality.

In some embodiments the first network node 111 may select a transmission path based on an independent channel quality measurement e.g. based on network configuration or a network event such as e.g. a handover, wherein a transmission path of a target cell is added when a handover is about to happen

Action 407

To further continue a communication on an adjusted set of number of paths for replicating data, each of the adjusted number of paths need a new path specific operation target with regards to the service requirements. Therefore the first network node 111 determines second path specific operation target parameters for each respective replicated data transmission, based on the adjusted number of paths and the service requirements. The respective second path specific operation target parameter comprises at least a second BLER target, and a second maximum latency.

Action 408

The first network node 111 may then send a second request to the second network node 112 requesting a second transmission of the replicated data of each path of the number of paths, according to the second path specific operation target parameters. This enables the second network node 112 to e.g. perform a second transmission according to the second path specific operation target parameters. In some embodiments, the request may order or trigger the second network node 112 to perform the second transmission.

The second request may further be based on the feedback from the second network node 112, triggered by the first request. In this way, the second request e.g. enables way to iteratively adapt the number of nodes to be a number of nodes that meets the service requirements of the communication even if service requirements or network conditions change over time. Figure 5 shows example embodiments of a method performed by the second network node 112 for handling a number of paths between the second network node 112 and the Wireless Device, WD, 120 in the wireless communications network 100. The method comprises the following actions, which actions may be taken in any suitable order. The term communicate data or communicating data when used herein means to receive or transmit data.

Action 501

The number of paths is determined by the first network node 111, and the second network node 112 receiving a request from the first network node 111, requesting transmission of replicated data according to an operation target parameter specific for each path of the number of paths. The path specific operation target parameter comprises, at least a BLER target and a maximum latency.

In this way, the second network node 112 is informed about which paths are to be used for communicating replicated data. Furthermore, the second network node 112 is informed about a path specific target parameter for each path comprising at least a BLER target and a maximum latency. In this way, each path need to handle its replicated data transmission in according to its respective path specific target parameter.

In some embodiments, the path specific operation target parameters further comprises, for each respective replicated data transmission path, information related to a HARQ operating point, and a maximum number of time domain retransmissions.

In this way, each path specific link adaptor and scheduler are enabled to select parameters for adapting the link and for scheduling the data transmissions.

Action 502

For each respective replicated data transmission of each path, the second network node 112 schedules radio resources based on the respective path specific operation target parameter in the request. The scheduling may then involve a decision on the number of parallel replicas of data, selection of frequency for the replicas within the bandwidth available for the path, and selection of the number of replicated data transmission over time. For some service requirements with less stringent latency requirements scheduling may also involve HARQ repetitions.

Action 503 For each respective replicated data transmission of each path, the second network node 112 performs individual link adaptation based on the respective path specific operation target parameter in the request.

In some embodiments, the second network node 112 may further perform individual link adaptation based on the quality of the channel such as channel state information reported by the WD 120 or determined based on the UL channel.

Action 504

The second network node 112 may then communicate each of the respective replicated data of respective scheduled and link adapted path according to the determined path specific operation target parameters.

This enables a way to perform the communication based on the path specific operation target parameters, and thus enables the second network node 112 to e.g. achieve a communication according to the service parameters based on meeting the path specific operation target parameters for each path.

In some embodiments, e.g. in order to meet the service parameters or path specific operation target parameters or, the communication may comprise communicating in different Transport Blocks, TB, multiplexed replicated data of respective scheduled and link adapted path relating to any one or more out of: communicating using a time resource differing from another time resource used by another path, communicating using distributed radio resources or Transmission and Reception points, TRP, communicating using an antenna ports separation different from another antenna ports used by another path, communicating using a frequency resource differing from a frequency resource used by another path, and communicating using a code separation different from another code separation used by another path.

In some embodiments the Transmission and Reception points, TRP may be within one cell, or different cell, and the frequency resource may be different PRB, BWP or carriers, bands

In this way the communication may e.g. achieve flexibility for performing communication and allow for an opportunistic routing of the replicated data transmission to resources that may be particularly efficient for said transmission, thereby improving the spectrum efficiency.

Action 505

The second network node 112 may provide feedback to the first network node 111, which feedback is related to estimations in relation to the service requirements of each of the respective replicated data transmission when communicated according to the determined path specific operation target parameters,

In this way, the first network node 111 is e.g. informed about each path, estimated capacity, channel quality, SI NR or estimated interference in relation to the service requirements.

The estimations may relate to measurements or approximations e.g. performed on pilot signals in a base station or WD 120, or performed as disclosed in previous actions.

In some embodiments the estimations may relate to the channel quality in terms of signal strength, interference, the capacity of the path in terms of bandwidth e.g. available for the service, or the number of times replicas may be communicated.

In some embodiments, specific measures and estimations may further be combined into a common measure and sent to the first network node 111.

In some embodiments the feedback further comprises an indication indicating the feasibility of providing the communication according to the service requirements for each of the path of the number of paths.

The feedback may further comprise a SINR or channel quality information for each available transmission paths in the second network node 112.

Furthermore, the feedback may in some embodiments trigger or order the first network node 111 to: based on the feedback adjust the number of paths for the communication, determine second path specific operation target parameters, and send a second request to the second network node 112 requesting a second transmission according to the second path specific operation target parameters.

Action 506

The first network node 111 may adjust the number of paths based on the provided feedback. The second network node 112 may receive a second request from the first network node 111 requesting a second transmission of the replicated data according to second operation target parameters specific for each path of an adjusted number of paths based on the provided feedback. The second path specific operation target parameters comprise, at least a second BLER target and a second maximum latency.

In this way, the second network node 112 is enabled to e.g. further communicate replicated data based on the provided feedback and adjusted accordingly such that the second path specific operation target parameters and the adjusted number of paths achieves the service requirements.

In some embodiments the path specific operation target parameters further comprises, for each respective replicated data transmission path, information related to a HARQ operating point, and a maximum number of time domain retransmissions.

Action 507

Similar to action 502, the second network node 112 may schedule for a respective replicated second data transmission of each path of the adjusted number of paths for the communication, based on the respective second path specific operation target parameters in the second request.

Action 508

Similar to action 503, the second network node 112 may perform second individual link adaptation for a respective replicated second data transmission of each path of the adjusted number of paths for the communication, based on the respective second path specific operation target parameters in the second request.

Action 509

Similar to action 504, the network node 112 may then communicate each of the respective replicated second data of each path of the adjusted number of paths using the scheduled and link adapted second radio resources according to the second path specific operation target parameters.

In this way, the replicated data is communicated based on an adjustment of path specific operation target parameters and an adjusted number of paths and based on provided feedback, thus achieving the aggregated service requirement maintained.

The communicating may in some embodiments further comprise different TB in similar way as in action 504.

The above embodiments will now be further explained and exemplified below. Relation of service requirement and path specific operation target parameters

The service requirements such as e.g. the PER requirement at the application layer may relate the path specific operation target parameters such as e.g. the BLER target a, after Na_me's retransmissions or repetitions at e.g. each simultaneous and independent total number of replication transmissions, N_Sim, such as e.g. each path of the number of paths or adjusted number of paths. This is e.g. shown in the equation a^Nsim=PER which assumes negligible packet error or packet loss in the CN or the Transport Network, (TN). In some aspects of the above relation in the equation is exemplified below.

The service requirements such as e.g. PER may be the error rate specified in e.g. QoS or service requirements of a specific service or application. The path specific operation target parameters such as e.g. the BLER target a may be the residual BLER after N_time ‘s retransmissions or repetitions in a time domain.

The paths such as e.g. N may be the total number of independent replication transmissions that are supported by the service requirements such as e.g. PDB, QoS of the application or service which may include the number of paths such as e.g. simultaneous replicated transmissions Nsim.

Packet Delay Budget

Some embodiments may be exemplified as shown in Figure 6, where the service requirements such as e.g. the packet delay budget, PDB only supports one transmission in time domain. In this way, there may be only one spatial or frequency domain transmission, and as such the link adaptation may need to select a physical layer TB size according to the path specific operation target parameters such as e.g. the BLER corresponding to an application layer PER, e.g. BLER target = PER=10⁶ e.g. in order to meet the service requirements.

In some example scenarios, the number of paths such as e.g. multiple simultaneous path transmissions, either in spatial domain, frequency domain, or both, with e.g. 3 multipath transmissions, and the path specific operation target parameters such as e.g. the individual BLER target of the link adaptation of each path equals to 10². In this example, e.g. the combined or aggregated service requirements such as e.g. PER at higher layer may equal to (BLER)^Nsim = 10 ®. In this way the link adaptation of each path may e.g. be more relaxed and may be able to provide a more effective handling of inaccuracy of channel estimations. Relaxed when used herein means e.g. that less backoff for SI NR may be needed or that a higher BLER target may be used. Function 1 - Determining number of paths

In this section, the detailed scenarios are depicted in Figure 7. Function 1 may be performed by the first network node 111.

At setup of the service requirements such as e.g. QoS, PDB, PER, PS, the service requirements may be associated by a 5G NR Standardized QoS Identifier (5QI). Based on the service requirements, the number of paths, e.g. the replicated transmission paths are determined.

The service requirement may e.g. comprise other input information such as network configuration, the available number of paths e.g. the number of multiple path supported.

In some embodiments the service requirement may comprise feedback details e.g. resource monitor parameters which may comprise details of feasibility, communicating using each specific path, relating to e.g. estimated radio channel quality or a resource utilization indicator.

In some embodiments the feedback may indicate feasibility e.g. how difficult or easy it is to provide the requested service requirements for each of the paths. This feedback may relate to an estimation or measurement of how loaded a specific carrier may be. In some embodiments, if a signal quality such as e.g. strength or interference is poor, thus the first network node 111 may select to give up on one path and put stricter path specific operation target parameters on another path based on e.g. the feasibility of the feedback.

In some embodiments it may be possible to decide whether or not Ntime time domain transmissions may be supported given a service requirement such as e.g. PDB as below.

The service requirements such as e.g. the PDB may thus be used to determine the maximum number of time domain transmission replications by determining the number based on any of:

T RTT.HARQ e.g. the HARQ round trip time e.g. applicable when using on demand retransmission which may in some embodiments be known by the network depending on e.g. system architecture. TRU.HARQ may in some embodiments be part of the service requirements,

TRLC e.g. time spent or communicating using the RLC layer, which in some embodiments may e.g. be negligible or zero,

TOTHER e.g. time spent or communicated using other protocol layer retransmissions, NOTHER e.g. be the number of transmissions including retransmissions,

NRLC e.g. be the number of transmissions including retransmissions communicating using the RLC layer.

TCN e.g. the time spent using the core network which may in some embodiments be known by the network depending on e.g. system architecture. TCN may in some embodiments be part of the service requirements, and TTN e.g. the time spent using the transport network which may in some embodiments be known by the network depending on e.g. system architecture. TTN may in some embodiments be part of the service requirements.

- In some embodiments, the maximum number of time domain transmission replications are determined based on the service requirement such as e.g. the PDB being based on all of TRTT,HARQ,TRLC,TOTHER, NOTHER, NRLC, TCN, TTN such that PDB ³Nother(NRLc(N|HARQTRTT,HARQ +TRLC) + TQTHER) + TCN+TTN. In some embodiments regarding above equation, e.g. the network nodes 111, 112 may communicate using RLC Unacknowledged Mode (UM) and hence requiring no retransmissions on the application layer, hence, NRLC=1 , Nother =1 , and thus resulting in PDB ³ NHARQT RTT.HARQ + TCN+TTN.

In some embodiments, as disclosed above, TRTT.HARQ , TCN, TTN are known, and as such in an example scenario with RLC UM the number of time domain transmission supported, Ntime.max, for e.g. PDB relation in Frequency-Division Duplex (FDD) lowband with 15 SCS as below:

PDB=1ms, Ntime_,max= NHARQ=1 , retransmission is not possible,

PDB=5ms, Ntime_,max= NHARQ=2, one retransmission is possible, PDB=50ms, Ntime_,max= NHARQ=4, three retransmissions are possible.

In some embodiments determining the number of paths e.g. number of simultaneous paths, Nsim, may be based on radio condition of each path, e.g. long term average, SINRi_avg, estimate of each path. In some embodiments the determining of number of paths may include a SINR threshold, SINRthreshold, and may be based on the path specific operation target parameters such as e.g. the channel quality such that e.g. SINRi_a vg>SINRthreshold. In some embodiments the path specific operation target parameters such as e.g. the residual BLER target of each path after time domain retransmissions are based on a = log(PER/Nsim).

In some other embodiments the determination of number of paths e.g. Nsim may be determined and the path specific operation target parameters such as e.g. the residual BLER target of each path, a is based on an optimization function to minimize the resource usage while fulfilling the service requirement such as e.g. the QoS requirement as below: arg min

aEB,N_sim EK

Where The link adaptation such as e.g. LA( ) may be a simplified link adaptation function to e.g. select the number of PRBs needed to transmit a packet size of size D with an operating point at BLER target = a,

The path specific operation target parameters such as e.g. the a e B, the path specific operation target parameters such as e.g. the residual BLER target, and the service requirement e.g. PER is packet error rate at application layer such that B={1 O ¹, 10-²,1 O ³,... , PER},

The determining the number of paths may be

may be the maximum number of simultaneous transmission paths e.g. supported by the service requirements such as e.g. the network configuration.

The service requirements such as e.g. SINRi may comprise a SINR channel quality estimation for each number of path e.g. i^th transmission.

The service requirements such as e.g. a packet size D, may include overhead of different communication layers.

In some embodiments e.g. the first network node 111, sends the request or second request and may comprise the number of paths e.g. Nsim , the path specific operation target parameters such as e.g. the output parameters, including residual BLER target, a , and the number of maximum supported time domain transmissions Ntime, to the scheduler and link adaptation function of each independent path. Some embodiments may involve deciding whether or not the service requirements such as e.g. the PDB may support a one shot transmission, Ntime=1 if there is only a single path supported by the network, such that the path specific operation target parameters such as e.g. correspond to the service requirements such as e.g. Packet Error Rate, PER, such that e.g. a=PER.

Some embodiments may involve deciding whether or not to use a single independent transmission path if the WD 120 e.g. a UE has a feasibility e.g. extremely good estimated radio channel quality to support service requirements such as e.g. required packet size and PER in relation to the path specific operation target parameters such as e.g. the BLER target.

Some embodiments may involve determining the number of paths such that e.g. selecting the number of replicated transmission paths based on the service requirements such as e.g. PDB and channel condition estimation of each individual paths.

Some embodiments may involve deciding whether or not to use a single independent transmission path if the service requirements such as e.g. PDB is long enough to support the path specific operation target parameters such as e.g. multiple retransmissions or repetitions in time and the service requirements such as e.g. PER requirement may be reached after retransmissions or repetition. In some embodiments this relates to a the path specific operation target parameters such as e.g. a HARQ operating point BLER target may be based on a=f(10^lg(pER/Nsim)).

In some embodiments the service requirements such as e.g. PER is not reached within the service requirements such as e.g. PDB, and the number of paths e.g. minimum simultaneous transmission paths may be increased.

In some embodiments the number of paths, e.g. the selected replicated transmission paths, including the number of replicated transmission paths, the path specific operation target parameters such as e.g. the correspondent HARQ operating point BLER target, and the maximum number of time domain retransmissions or repetitions are sent to e.g. the scheduler of each individual paths in the second network node 112.

In some embodiments, for the same service requirements, the number of replicated data packets and transmission paths may differ depending on the frequency band that the paths operate on. E.g. high bands may use higher numerologies and may host more repetitions of the same packet since the PDB allows more retransmissions.

Function 2 In this section, the detailed scenarios are depicted in figure 7. Function 2 may be performed by the second network node 112.

In an example scenario, in function 2, the second network node 112 such as its scheduler and link adaptation may select radio resource including MCS, TB size, frequency resource and time resource for each individual replication transmission path so that the HARQ operating point of individual paths may be maintained.

Furthermore, in some embodiments, the second network node 112 may monitor and send, e.g. as feedback, the resource utilization indicators such as e.g. time domain resource utilization and frequency resource utilization, of each individual path to the first network node 111 e.g. a hierarchical supervisor. In some embodiments the frequency resource utilization indicates the available Physical Resource Blocks, PRB resources that may be used for URLLC applications or services.

The feedback may also, in some embodiments, be an overall error rate e.g. PER or BLER after combination of all transmission paths, or an individual error rate, e.g. BLER of each individual path.

In some embodiments, the second network node 112 may, e.g. by a transmitter related to each path, transmit different TB multiplexed at different time, and using different frequency and spatial resource e.g. as scheduled by the scheduler.

In some embodiments the WD 120, e.g. the receiver receives transmissions and decodes the earliest correctly decoded replicated packets e.g. replicated data and ignores the other replicated packets that are received later.

In some embodiments the multipath may be PDCP replications with DC.

In some embodiments the multipath may be PDCP replications with carrier aggregation.

In some embodiments the multipath transmissions are transmitting from different transmission and reception points, e.g. multiple Transmission Reception Points (multi- TRP), or may use different antenna ports within the same carrier.

In some embodiments the multipath transmissions may be communicating from different part of frequency PRB or BWP at same or different time.

In some embodiments, the second network node 112 may convert service requirements e.g. received from the first network node into the path specific operation target parameters for the link adaptation and scheduling.

Schedulers The scheduling performed in e.g. the second network node 112 may in some embodiments be performed based on one or more shared schedulers of the second network node 112. In some embodiments each path may comprise an individual scheduler for each respective path. In some further embodiments, the schedulers may also schedule separate scheduling processes, scheduling data relating to other entities, wireless devices or UEs. In some embodiments the schedulers of individual paths comprise scheduling processes that allocate different air interface resources for e.g. different replicated data from the same UE.

Communication

In some or all embodiments herein, the use of the term communication of data, communicate data, communicating data, or any related term may refer to either receiving or transmitting of data. In some embodiments all communication may be applicable for either of or both uplink and downlink transmissions.

In some embodiments, replicas, replicated data or replicated packets may be equivalent and may be a packet or a group of packets.

In embodiments when the communication is an uplink communication, the second network node 112 may combine each replicated data e.g. into one packet or Protocol Data Unit (PDU). In embodiments when the communication is a downlink communication, the second network node 112 may instead generate replicated data as e.g. packets, and distribute them to the number of paths.

Path selection

Selecting, and re-selecting paths for communication with the WD 120 may in some scenarios be complex. This may be since each link adaptor and scheduler may work on just one carrier and balances the requirements of many WDs competing for limited resources. These limited resources may be distributed by each scheduler and link adaptor among the WDs such as e.g. WD 120. In these scenarios, many parameters may therefore be involved in the scheduling of a carrier. Furthermore, coordination of scheduling and link adaptation of several communication paths and communication with the WD 120 may therefore be too complex to be assigned to traditional link adaptors and schedulers.

Hence, in some embodiments, determining or adjusting a number of paths may further involve a selection of which paths to use of the determined or adjusted number of paths. In some embodiments, this selection may thus be handled by the first network node 111, such that, it receives e.g. from the second network node 112, a generalized measure of the performance of each path, and adapts each of the paths specific operation target parameters based on an evaluation of the performance of all paths, and selects and reselects paths based on the evaluation. In some embodiments the selection or reselection may select the path or paths with best evaluated performance.

In some embodiments, the selection or reselection of paths may be based on any parameter of embodiments herein.

To perform the method actions, the first network node 111 may comprise an arrangement depicted in Figures 8a and b. The first network node 111 is configured to determine a number of paths in a communication between a second network node 112 and a WD 120 in the wireless communications network 100.

The first network node 111 may comprise an input and output interface 800 configured to communicate with network nodes such as the second network node 112. The input and output interface 800 may comprise a wireless receiver (not shown) and a wireless transmitter (not shown).

The first network node 111 is further configured to, e.g. by means of an obtaining unit 810 in the first network node 111, obtain service requirements on a communication service provided to the WD 120. The service requirements are adapted to comprise a latency requirement and error rate requirement.

The service requirements on the communication service provided to the WD 120, may be adapted to further comprise any one or more out of: URRLC QoS requirements, PER, PDB, packet size, jitter requirement, and network configuration.

The first network node 111 is further configured to, e.g. by means of a determining unit 820 in the first network node 111, determine the number of paths for the communication based on the obtained service requirements. Each path out of the number of paths is adapted to be scheduled for a respective replicated data transmission.

The first network node 111 is further configured to, e.g. by means of the determining unit 820 in the first network node 111, determine path specific operation target parameters for each respective replicated data transmission. The parameters are based on the determined number of paths and the service requirements. The respective path specific operation target parameter is adapted to comprise at least a Block Error Rate, BLER, target and a maximum latency.

The first network node 111 may further be configured to, e.g. by means of the determining unit 820 in the first network node 111, determine second path specific operation target parameters for each respective replicated data transmission. The parameters are based on the adjusted number of paths and the service requirements. The respective second path specific operation target parameter is adapted to comprise at least a second BLER target, and a second maximum latency,

The any of the path specific operation target parameters may be adapted to further comprise, for each respective replicated data transmission path, information related to a HARQ operating point, and a maximum number of time domain retransmissions.

The first network node 111 is further configured to, e.g. by means of a sending unit 830 in the first network node 111, send a request to the second network node 112. The request is adapted to request a transmission of replicated data of each path of the number of paths, according to the path specific operation target parameters.

The first network node 111 may further be configured to, e.g. by means of the sending unit 830 in the first network node 111, send a second request to the second network node 112. The second request requests a second transmission of the replicated data of each path of the number of paths, according to the second path specific operation target parameters.

The first network node 111 may further be configured to, e.g. by means of a receiving unit 840 in the first network node 111, receive feedback from the second network node 112. The feedback is adapted to be related to estimations in relation to the service requirements of the transmission of each of the replicated data of each path out of the number of paths when communicated according to the determined path specific operation target parameters.

The feedback may be adapted to further comprise indications adapted to indicate, for each of the path of the number of paths, the feasibility of providing the communication according to the service requirements.

The feedback may further be adapted to comprise a SINR or channel quality information for each available transmission paths in the second network node 112. The first network node 111 may further be configured to, e.g. by means of an adjusting unit 850 in the first network node 111, based on the feedback, adjust the number of paths for the communication. Each path out of the number of paths is adapted to be scheduled for a second respective replicated data transmission.

The first network node 111 may further be configured to, e.g. by means of the adjusting unit 850 in the first network node 111, adjust the number of paths for the communication further based on aggregated feasibility of providing the communication according to the service requirement with the adjusted number of paths.

The embodiments herein may be implemented through a respective processor or one or more processors, such as the processor 860 of a processing circuitry in the first network node 111 depicted in Figure 8a, together with respective computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the first network node 111. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the first network node 111.

The first network node 111 may further comprise a memory 870 comprising one or more memory units. The memory 870 comprises instructions executable by the processor 860 in first network node 111. The memory 870 is arranged to be used to store e.g. requests, feedback, parameters, paths, targets, latency, indications, data, configurations, and applications to perform the methods herein when being executed in the first network node 111.

In some embodiments, a computer program 880 comprises instructions, which when executed by the respective at least one processor 860, cause the at least one processor 860 of first network node 111 to perform the actions above.

In some embodiments, a respective carrier 890 comprises the respective computer program 880, wherein the carrier 890 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium. Those skilled in the art will appreciate that the units in the first network node 111 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in the first network node 111, that when executed by the respective one or more processors such as the processors described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a- chip (SoC).

To perform the method actions, the second network node 112 may comprise an arrangement depicted in Figures 9a and b. The second network node 112 is configured to handle a number of paths between the second network node 112 and a WD 120 in a wireless communications network 100.

The second network node 112 may comprise an input and output interface 900 configured to communicate with network nodes such as the first network node 111 and the WD 120. The input and output interface 900 may comprise a wireless receiver (not shown) and a wireless transmitter (not shown).

The second network node 112 is further configured to, e.g. by means of a receiving unit 910 in the second network node 112, receive a request from a first network node 111. The request is adapted to request transmission of replicated data according to an operation target parameter specific for each path of the number of paths. The path specific operation target parameter is adapted to comprise, at least a BLER target and a maximum latency.

The second network node 112 may further be configured to, e.g. by means of the receiving unit 910 in the second network node 112, receive a second request from the first network node 112. The second request is adapted to request a second transmission of the replicated data according to second operation target parameters specific for each path of an adjusted number of paths based on the provided feedback. The second path specific operation target parameters is adapted to comprise, at least a second BLER target and a second maximum latency. The any of the path specific operation target parameters may be adapted to further comprise, for each respective replicated data transmission path, information related to a HARQ operating point, and a maximum number of time domain retransmissions.

The second network node 112 is further configured to, e.g. by means of a scheduling unit 920 in the second network node 112, schedule radio resources for each respective replicated data transmission of each path.

The second network node 112 may further be configured to, e.g. by means of the scheduling unit 920 in the second network node 112, schedule second radio resources.

The second network node 112 is further configured to, e.g. by means of a performing unit 930 in the second network node 112, perform individual link adaptation based on the respective path specific operation target parameter in the request.

The second network node 112 may further be configured to, e.g. by means of the performing unit 930 in the second network node 112, perform second individual link adaptation for a respective replicated second data transmission of each path of the adjusted number of paths for the communication based on the respective second path specific operation target parameters in the second request.

The second network node 112 may further be configured to, e.g. by means of a communicating unit 940 in the second network node 112, communicate each of the respective replicated data of respective scheduled and link adapted path according to the determined path specific operation target parameters.

The second network node 112 may further be configured to, e.g. by means of the communicating unit 940 in the second network node 112, communicate each of the respective replicated second data of each path of the adjusted number of paths adapted to use the scheduled and link adapted second radio resources according to the second path specific operation target parameters.

The second network node 112 may further be configured to, e.g. by means of a providing unit 950 in the second network node 112, provide feedback to the first network node 111. The feedback is adapted to be related to estimations in relation to the service requirements of each of the respective replicated data transmission when communicated according to the determined path specific operation target parameters. The feedback may be adapted to further comprise an indication. The indication is adapted to indicate the feasibility of providing the communication according to the service requirements for each of the path of the number of paths.

The feedback may be adapted to further comprise a SI NR or channel quality information for each available transmission paths in the second network node 112.

The second network node 112 may further be configured to, e.g. by means of the communicating unit 940 in the second network node 112, communicate in different TB multiplexed replicated data of respective scheduled and link adapted path adapted to relate to any one or more out of: communicate by using a time resource adapted to differ from another time resource used by another path, communicate by using distributed radio resources or Transmission and Reception points, TRP, communicate by using a frequency resource adapted to differ from a frequency resource used by another path, communicate by using a code separation adapted to differ from another code separation used by another path, and communicating using an antenna port separation different from another antenna port separation used by another path.

The embodiments herein may be implemented through a respective processor or one or more processors, such as the processor 960 of a processing circuitry in the second network node 112 depicted in Figure 9a, together with respective computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the second network node 112. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the second network node 112.

The second network node 112 may further comprise a memory 970 comprising one or more memory units. The memory 970 comprises instructions executable by the processor 960 in second network node 112. The memory 970 is arranged to be used to store e.g. requests, feedback, paths, parameters, targets, latency, indications, data, configurations, and applications to perform the methods herein when being executed in the second network node 112.

In some embodiments, a computer program 980 comprises instructions, which when executed by the respective at least one processor 960, cause the at least one processor 960 of the second network node 112 to perform the actions above.

In some embodiments, a respective carrier 990 comprises the respective computer program 980, wherein the carrier 990 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

Those skilled in the art will appreciate that the units in the second network node 112 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g. stored in the second network node 112, that when executed by the respective one or more processors such as the processors described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system- on-a-chip (SoC).

With reference to Figure 10, in accordance with an embodiment, a communication system includes a telecommunication network 3210, such as a 3GPP-type cellular network, which comprises an access network 3211, such as a radio access network, and a core network 3214. The access network 3211 comprises a plurality of base stations 3212a, 3212b, 3212c, such as AP STAs NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c is connectable to the core network 3214 over a wired or wireless connection 3215. A first user equipment (UE) such as a Non-AP STA 3291 located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c. A second UE 3292 such as a Non-AP STA in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. While a plurality of UEs 3291, 3292 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 3212.

The telecommunication network 3210 is itself connected to a host computer 3230, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 3221, 3222 between the telecommunication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may go via an optional intermediate network 3220. The intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 3220, if any, may be a backbone network or the Internet; in particular, the intermediate network 3220 may comprise two or more sub networks (not shown).

The communication system of Figure 10 as a whole enables connectivity between one of the connected UEs 3291, 3292 and the host computer 3230. The connectivity may be described as an over-the-top (OTT) connection 3250. The host computer 3230 and the connected UEs 3291, 3292 are configured to communicate data and/or signaling via the OTT connection 3250, using the access network 3211, the core network 3214, any intermediate network 3220 and possible further infrastructure (not shown) as intermediaries. The OTT connection 3250 may be transparent in the sense that the participating communication devices through which the OTT connection 3250 passes are unaware of routing of uplink and downlink communications. For example, a base station 3212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 3230 to be forwarded (e.g., handed over) to a connected UE 3291. Similarly, the base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 3291 towards the host computer 3230.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 11. In a communication system 3300, a host computer 3310 comprises hardware 3315 including a communication interface 3316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 3300. The host computer 3310 further comprises processing circuitry 3318, which may have storage and/or processing capabilities. In particular, the processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The host computer 3310 further comprises software 3311 , which is stored in or accessible by the host computer 3310 and executable by the processing circuitry 3318. The software 3311 includes a host application 3312. The host application 3312 may be operable to provide a service to a remote user, such as a UE 3330 connecting via an OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the remote user, the host application 3312 may provide user data which is transmitted using the OTT connection 3350.

The communication system 3300 further includes a base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with the host computer 3310 and with the UE 3330. The hardware 3325 may include a communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 3300, as well as a radio interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown in Figure 11) served by the base station 3320. The communication interface 3326 may be configured to facilitate a connection 3360 to the host computer 3310. The connection 3360 may be direct or it may pass through a core network (not shown in Figure 11) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, the hardware 3325 of the base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The base station 3320 further has software 3321 stored internally or accessible via an external connection.

The communication system 3300 further includes the UE 3330 already referred to. Its hardware 3335 may include a radio interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving a coverage area in which the UE 3330 is currently located. The hardware 3335 of the UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, application- specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The UE 3330 further comprises software 3331, which is stored in or accessible by the UE 3330 and executable by the processing circuitry 3338. The software 3331 includes a client application 3332. The client application 3332 may be operable to provide a service to a human or non-human user via the UE 3330, with the support of the host computer 3310. In the host computer 3310, an executing host application 3312 may communicate with the executing client application 3332 via the OTT connection 3350 terminating at the UE 3330 and the host computer 3310. In providing the service to the user, the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data. The OTT connection 3350 may transfer both the request data and the user data. The client application 3332 may interact with the user to generate the user data that it provides.

It is noted that the host computer 3310, base station 3320 and UE 3330 illustrated in Figure 11 may be identical to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291, 3292 of Figure 10, respectively. This is to say, the inner workings of these entities may be as shown in Figure 11 and independently, the surrounding network topology may be that of Figure 10.

In Figure 11, the OTT connection 3350 has been drawn abstractly to illustrate the communication between the host computer 3310 and the use equipment 3330 via the base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the UE 3330 or from the service provider operating the host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

The wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 3330 using the OTT connection 3350, in which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may improve the [select the applicable RAN effect: data rate, latency, power consumption] and thereby provide benefits such as [select the applicable corresponding effect on the OTT service: reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime]

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 3350 between the host computer 3310 and UE 3330, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 3311, 3331 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 3320, and it may be unknown or imperceptible to the base station 3320. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating the host computer’s 3310 measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that the software 3311, 3331 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 3350 while it monitors propagation times, errors etc.

FIGURE 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station such as a AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 10 and Figure 11. For simplicity of the present disclosure, only drawing references to Figure 12 will be included in this section. In a first step 3410 of the method, the host computer provides user data. In an optional substep 3411 of the first step 3410, the host computer provides the user data by executing a host application. In a second step 3420, the host computer initiates a transmission carrying the user data to the UE. In an optional third step 3430, the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional fourth step 3440, the UE executes a client application associated with the host application executed by the host computer.

FIGURE 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station such as a AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 10 and Figure 11. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section. In a first step 3510 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In a second step 3520, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.

In an optional third step 3530, the UE receives the user data carried in the transmission.

FIGURE 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station such as a AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 10 and Figure 11. For simplicity of the present disclosure, only drawing references to Figure 14 will be included in this section. In an optional first step 3610 of the method, the UE receives input data provided by the host computer. Additionally or alternatively, in an optional second step 3620, the UE provides user data. In an optional substep 3621 of the second step 3620, the UE provides the user data by executing a client application. In a further optional substep 3611 of the first step 3610, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in an optional third substep 3630, transmission of the user data to the host computer. In a fourth step 3640 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

FIGURE 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station such as a AP STA, and a UE such as a Non-AP STA which may be those described with reference to Figure 10 and Figure 11. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section. In an optional first step 3710 of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In an optional second step 3720, the base station initiates transmission of the received user data to the host computer. In a third step 3730, the host computer receives the user data carried in the transmission initiated by the base station. When using the word "comprise" or “comprising” it shall be interpreted as non limiting, i.e. meaning "consist at least of".

The embodiments herein are not limited to the above described preferred embodiments. Various alternatives, modifications and equivalents may be used.

Claims

1. A method performed by a first network node (111) for determining a number of paths in a communication between a second network node (112) and a Wireless Device, WD, (120) in a wireless communications network (100), the method comprising: obtaining (401) service requirements on a communication service provided to the WD (120), wherein the service requirements comprises a latency requirement and error rate requirement, determining (402) the number of paths for the communication based on the obtained service requirements, where each path out of the number of paths, is to be scheduled for a respective replicated data transmission, determining (403) path specific operation target parameters for each respective replicated data transmission, based on the determined number of paths and the service requirements, which respective path specific operation target parameter comprises at least a Block Error Rate, BLER, target and a maximum latency, and sending (404) a request to the second network node (112) requesting transmission of replicated data of each path of the number of paths, according to the path specific operation target parameters.

2. The method according to claim 1 , the method further comprising: receiving (405) feedback from the second network node (112), which feedback is related to estimations in relation to the service requirements of the transmission of each of the replicated data of each path out of the number of paths when communicated according to the determined path specific operation target parameters, based on the feedback, adjusting (406) the number of paths for the communication, where each path out of the number of paths, is to be scheduled for a second respective replicated data transmission, determining (407) second path specific operation target parameters for each respective replicated data transmission, based on the adjusted number of paths and the service requirements, which respective second path specific operation target parameter comprises at least a second BLER target, and a second maximum latency, and sending (405) a second request to the second network node (112) requesting a second transmission of the replicated data of each path of the number of paths, according to the second path specific operation target parameters.

3. The method according to any of the claim 2, wherein the feedback further comprises indications indicating for each of the path of the number of paths the feasibility of providing the communication according to the service requirements, and wherein the adjusting (406) of the number of paths for the communication based on the indications for all of the path of the number of paths, is based on an aggregated feasibility of providing the communication according to the service requirement with the adjusted number of paths.

4. The method according to any of the claims 1-3, wherein any of the path specific operation target parameters further comprises, for each respective replicated data transmission path, information related to a Hybrid Automatic Repeat Request,

HARQ, operating point, and a maximum number of time domain retransmissions.

5. The method according to any of the claims 2-4, wherein the feedback further comprises a Signal to Noise Ratio, SINR, or channel quality information for each available transmission paths in the second network node (112).

6. The method according to any of the claims 1-5, wherein service requirements on the communication service provided to the WD (120), further comprises any one or more out of:

Ultra-Reliable Low-Latency Communication, URRLC, Quality of Service, QoS requirements,

Packet Error Rate, PER,

Packet Delay Budget, PDB, packet size, jitter requirement, [YSI]

7. A computer program (880) comprising instructions, which when executed by a processor (860), causes the processor (860) to perform actions according to any of the claims 1-6.

8. A carrier (890) comprising the computer program (880) of claim 7, wherein the carrier (890) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

9. A method performed by a second network node (112) for handling a number of paths between the second network node (112) and a Wireless Device, WD, (120) in a wireless communications network (100), the method comprising: receiving (501) a request from a first network node (111), requesting transmission of replicated data according to an operation target parameter specific for each path of the number of paths, which path specific operation target parameter comprises, at least a Block Error Rate, BLER, target and a maximum latency, and for each respective replicated data transmission of each path, scheduling (502) radio resources and performing (503) individual link adaptation based on the respective path specific operation target parameter in the request.

10. The method according to claim 9, the method further comprising: communicating (504) each of the respective replicated data of respective scheduled and link adapted path according to the determined path specific operation target parameters, providing (505) feedback to the first network node (111), which feedback is related to estimations in relation to the service requirements of each of the respective replicated data transmission when communicated according to the determined path specific operation target parameters, receiving (506) a second request from the first network node (111) requesting a second transmission of the replicated data [YS2]according to second operation target parameters specific for each path of an adjusted number of paths based on the provided feedback, which second path specific operation target parameters comprise, at least a second BLER target and a second maximum latency, scheduling (507) second radio resources and performing (508) second individual link adaptation for a respective replicated second data transmission of each path of the adjusted number of paths for the communication, based on the respective second path specific operation target parameters in the second request, and communicating (509) each of the respective replicated second data of each path of the adjusted number of paths using the scheduled and link adapted second radio resources according to the second path specific operation target parameters.

11. The method according to claim 10, wherein the feedback further comprises an indication indicating the feasibility of providing the communication according to the service requirements for each of the path of the number of paths.

12. The method according to any of the claims 9-11, wherein any of the path specific operation target parameters further comprises, for each respective replicated data transmission path, information related to a Hybrid Automatic Repeat Request,

HARQ, operating point, and a maximum number of time domain retransmissions.

13. The method according to any of the claims 10-12, wherein the feedback further comprises a Signal to Noise Ratio, SINR, or channel quality information for each available transmission paths in the second network node (112).

14. The method according to claim 9 to 13, further comprising: communicating (504) in different Transport Blocks, TB, multiplexed replicated data of respective scheduled and link adapted path relating to any one or more out of: communicating using a time resource differing from another time resource used by another path, communicating using distributed radio resources or Transmission and Reception points, TRP, communicating using a frequency resource differing from a frequency resource used by another path, communicating using a code separation different from another code separation used by another path, and communicating using an antenna port separation different from another antenna port separation used by another path.

15. A computer program (980) comprising instructions, which when executed by a processor (960), causes the processor (960) to perform actions according to any of the claims 9-14.

16. A carrier (990) comprising the computer program (980) of claim 15, wherein the carrier (990) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

17. A first network node (111) configured to determine a number of paths in a communication between a second network node (112) and a Wireless Device, WD, (120) in a wireless communications network (100), the first network node (111) further being configured to: obtain service requirements on a communication service provided to the WD (120), wherein the service requirements are adapted to comprises a latency requirement and error rate requirement, determine the number of paths for the communication based on the obtained service requirements, where each path out of the number of paths is adapted to be scheduled for a respective replicated data transmission, determine path specific operation target parameters for each respective replicated data transmission, based on the determined number of paths and the service requirements, which respective path specific operation target parameter is adapted to comprise at least a Block Error Rate, BLER, target and a maximum latency, and send a request to the second network node (112), the request being adapted to request a transmission of replicated data of each path of the number of paths, according to the path specific operation target parameters.

18. The first network node (111) according to claim 17, further being configured to: receive feedback from the second network node (112), which feedback is adapted to be related to estimations in relation to the service requirements of the transmission of each of the replicated data of each path out of the number of paths when communicated according to the determined path specific operation target parameters, based on the feedback, adjust the number of paths for the communication, where each path out of the number of paths is adapted to be scheduled for a second respective replicated data transmission, determine second path specific operation target parameters for each respective replicated data transmission based on the adjusted number of paths and the service requirements, which respective second path specific operation target parameter is adapted to comprise at least a second BLER target, and a second maximum latency, and send a second request to the second network node (112) requesting a second transmission of the replicated data of each path of the number of paths, according to the second path specific operation target parameters.

19. The first network node (111) according to claim 18, wherein the feedback is adapted to further comprise indications adapted to indicate, for each of the path of the number of paths, the feasibility of providing the communication according to the service requirements, and wherein the first network node (111) is further configured to adjust the number of paths for the communication further based an aggregated feasibility of providing the communication according to the service requirement with the adjusted number of paths.

20. The first network node (111) according to any of the claims 17-19, wherein any of the path specific operation target parameters is adapted to further comprise, for each respective replicated data transmission path, information related to a Hybrid Automatic Repeat Request, HARQ, operating point, and a maximum number of time domain retransmissions.

21. The first network node (111) according to any of the claims 18-20, wherein the feedback further is adapted to comprise a Signal to Noise Ratio, SINR, or channel quality information for each available transmission paths in the second network node (112).

22. The first network node (111) according to any of the claims 17-21, wherein the service requirements on the communication service provided to the WD (120), is adapted to further comprise any one or more out of: Ultra-Reliable Low-Latency Communication, URRLC, Quality of Service, QoS requirements,

Packet Error Rate, PER,

Packet Delay Budget, PDB, packet size, jitter requirement, and network configuration.

23. A second network node (112) configured to handle a number of paths between the second network node (112) and a Wireless Device, WD, (120) in a wireless communications network (100), the second network node (112) further being configured to: receive a request from a first network node (111), the request being adapted to request transmission of replicated data according to an operation target parameter specific for each path of the number of paths, which path specific operation target parameter is adapted to comprise, at least a Block Error Rate, BLER, target and a maximum latency, and for each respective replicated data transmission of each path, schedule radio resources and perform individual link adaptation based on the respective path specific operation target parameter in the request.

24. The second network node (112) according to claim 23, further being configured to: communicate each of the respective replicated data of respective scheduled and link adapted path according to the determined path specific operation target parameters, provide feedback to the first network node (111), which feedback is adapted to be related to estimations in relation to the service requirements of each of the respective replicated data transmission when communicated according to the determined path specific operation target parameters, receive a second request from the first network node (111), the second request being adapted to request a second transmission of the replicated data according to second operation target parameters specific for each path of an adjusted number of paths based on the provided feedback, which second path specific operation target parameters is adapted to comprise, at least a second BLER target and a second maximum latency, schedule and perform second individual link adaptation for a respective replicated second data transmission of each path of the adjusted number of paths for the communication based on the respective second path specific operation target parameters in the second request, and communicate each of the respective replicated second data of each path of the adjusted number of paths adapted to use the scheduled and link adapted second radio resources according to the second path specific operation target parameters.

25. The second network node (112) according to claim 24, wherein the feedback is adapted to further comprise an indication adapted to indicate the feasibility of providing the communication according to the service requirements for each of the path of the number of paths.

26. The method according to any of the claims 23-25, wherein any of the path specific operation target parameters are adapted to further comprise, for each respective replicated data transmission path, information related to a Hybrid Automatic Repeat Request, HARQ, operating point, and a maximum number of time domain retransmissions.

27. The second network node (112) according to any of the claims 24-26, wherein the feedback is adapted to further comprise a Signal to Noise Ratio, SINR, or channel quality information for each available transmission paths in the second network node (112).

28. The second network node (112) according to claim 23 to 27, further being configured to: communicate in different Transport Blocks, TB, multiplexed replicated data of respective scheduled and link adapted path adapted to relate to any one or more out of: communicate by using a time resource adapted to differ from another time resource used by another path, communicate by using distributed radio resources or Transmission and Reception points, TRP, communicate by using a frequency resource adapted to differ from a frequency resource used by another path, communicate by using a code separation adapted to differ from another code separation used by another path, and communicating using an antenna port separation different from another antenna port separation used by another path.