Network nodes, intermediate node and methods for handling packets in a backhaul / midhaul transport network

Abstract

A method performed by a first network node is provided. The method is for handling packets of a packet stream in a wireless communications network. The packet stream is related to a transmission in a User Equipment, UE, data session from the first network node towards a second network node, via intermediate nodes in a transport network of the communications network. The transport network comprises any one or more out of: a backhaul network and midhaul network. The first network node obtains (402) a stream identifier identifying the packet stream based on characteristics of the packet stream. The first network node marks (403) the respective packet in the packet stream with the stream identifier. The first network node then transmits (405) the stream identifier marked packets of the packet stream towards the second network node. The stream identifier enables the respective first network node, second network node and intermediate nodes to: Identify the packet stream and obtain rules related to forwarding the packets of the identified packet stream towards the second network node, and based on the obtained rules, control traffic steering and / or distribution of the packets comprised in the identified packet stream, when forwarding the marked packets towards the second network node.

Description

[0001] NETWORK NODES, INTERMEDIATE NODE AND METHODS FOR HANDLING PACKETS IN A BACKHAUL / MIDHAUL TRANSPORT NETWORK

[0002] TECHNICAL FIELD

[0003] Embodiments herein relate to a first network node, a first intermediate node, a second network node and methods therein. In some aspects, they relate to handling packets of a packet stream in a communications network. The packet stream is related to a transmission in a User Equipment (UE) data session from the first network node towards a second network node, via intermediate nodes in a backhaul and / or midhaul transport network of the communications network.

[0004] BACKGROUND

[0005] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and / or User Equipment (UE), communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. The CN may also be referred to as “mobile core”, or “mobile core network” herein. 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 Wi-Fi access point, a Base Station (BS) or a radio base station (RBS), which in some networks may also be denoted, for example, a BS, a NodeB, eNodeB (eNB), or gNodeB (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 a radio frequency with the wireless devices within the range of the radio network node.

[0006] 3rd Generation Partnership Project (3GPP) is the standardization body for specifying the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet System (EPS) have been completed within the 3GPP. In 4G also called a Fourth Generation (4G) network, EPS is core network and E-UTRA is radio access network. In 5G, 5G Core (5GC) is core network, New Radio (NR) is radio access network. As a continued network evolution, the new release of 3GPP specifies a 5G network also referred to as 5G NR and 5GC.

[0007] Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz. FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.

[0008] Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. For a wireless connection between a single user, such as UE, and a base station, the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple- Output (MIMO) communication channel. This may be referred to as Single-User (SU)- MIMO. In the scenario where MIMO techniques is used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)- MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. The cell capacity can be increased linearly with respect to the number of antennas at the BS side. Due to that, more and more antennas are employed in BS. Such systems and / or related techniques are commonly referred to as massive MIMO.

[0009] A RAN has several external transport domains, e.g., relating to backhaul, fronthaul, midhaul, and sidehaul. Figure 1 depicts an example of such RAN network transport domains.

[0010] A backhaul domain is a network between a mobile core network and a base station. If there is a split into a Central Unit (CU) / virtual Central Unit (vCU) and Distributed Unit (DU) / virtual Distributed Unit (vDU), the backhaul domain ends at the CU / vCU. A fronthaul domain is a network between a DU / vDU and a Radio Unit (RU). A sidehaul domain is a network between DUs / vDUs. A midhaul domain is a network between a CU / vCU and a DU / vDU. If there is no split CU / vCU and DU / vDU then there is no midhaul domain and the backhaul domain ends at the combined node CD / DU, vCU / vDU.

[0011] A mobile backhaul packet transport network also referred to as mobile backhaul transport network is e.g., an Internet Protocol (IP) or Multi-Protocol Label Switching (MPLS) transport network between the mobile core network and the mobile backhaul termination point in a RAN Network. A RAN packet transport network, also referred to as RAN transport network, is often described as the Fronthaul, Sidehaul and Midhaul domains. In a mobile backhaul packet transport network and a RAN packet transport network, e.g., midhaul, there are often multiple simultaneous packet sessions ongoing between the IP endpoints. IP endpoints are e.g., related to physical or logical ports, and / or connections, between or within Dll / vDU, CU / vCll, Mobile Core. Each of those IP-sessions may comprise multiple transport networks such as e.g., mobile backhaul and / or midhaul, packet streams. The wording “mobile backhaul and / or mobile midhaul” is referred to as “backhaul / midhaul” herein. A mobile backhaul / midhaul packet stream when used herein e.g., means a stream of packets transmitted over a backhaul and / or midhaul network. The mobile backhaul / midhaul packet streams have various transport characteristics needs such as bitrate, delay, delay variation etc. The evolution of RAN Mobility services such as UltraReliable Low Latency Communications (URLLC) and Network Reliability, Availability and Redundancy (NRAR) drives for e.g., resilience and controlled packet stream steering in the mobile backhaul / midhaul transport networks. Therefore, mobile backhaul / midhaul packet transport networks are evolving towards more capable ring or meshed packet networks. Also new services like network slicing drives for evolution of packet transport handling in both mobile backhaul and / or midhaul networks.

[0012] SUMMARY

[0013] An object of embodiments herein is to improve the transmission of packet streams in backhaul and / or midhaul transport networks of a communications network.

[0014] According to an aspect of embodiments herein, the object is achieved by a method performed by a first network node. The method is for handling packets of a packet stream in a communications network. The packet stream is related to a transmission in a User Equipment (UE) data session from the first network node towards a second network node via intermediate nodes in a transport network of the communications network. The transport network comprises any one or more out of: a backhaul network and midhaul network. The first network node obtains a stream identifier. The stream identifier identifies the packet stream based on characteristics of the packet stream. The first network node marks the respective packet in the packet stream with the stream identifier. The first network node then transmits the stream identifier marked packets of the packet stream towards the second network node. The stream identifier enables the respective first network node, second network node and intermediate nodes to identify the packet stream and obtain rules related to forwarding the packets of the identified packet stream towards the second network node. Based on the obtained rules, the stream identifier enables the respective first network node, second network node and intermediate nodes to control traffic steering and / or distribution of the packets comprised in the identified packet stream, when forwarding the marked packets towards the second network node.

[0015] According to another aspect of embodiments herein, the object is achieved by a method performed by a first intermediate node. The method is for handling packets of a packet stream in a communications network. The packet stream is related to a transmission in a UE data session from a first network node towards a second network node via the first intermediate node and other intermediate nodes in a transport network of the communications network. The transport network comprises any one or more out of: a backhaul network and midhaul network. The first intermediate node receives packets of the packet stream. The respective packet of the packet stream is marked with a stream identifier identifying the packet stream. Based on the stream identifier, the first intermediate node obtains rules related to forwarding the packets of the identified packet stream towards the second network node. Based on the obtained rules, the first intermediate node controls any one or more out of: traffic steering and distribution, of the packets comprised in the identified packet stream, when forwarding the marked packets in the packet stream towards the second network node.

[0016] According to an aspect of embodiments herein, the object is achieved by a method performed by a second network node. The method is for handling packets of a packet stream in a communications network. The packet stream is related to a transmission in a UE data session from a first network node towards the second network node via intermediate nodes in a transport network of the communications network. The transport network comprises any one or more out of a backhaul network and a midhaul network. The second network node receives packets of the packet stream. The respective packet of the packet stream is marked with a stream identifier identifying the packet stream. Based on the identifier, the second network node obtains information about one or more Service Access Points (SAP)s and rules related to forward the packets of the packet stream to the one or more SAPs. Based on the obtained information and rules, the second network node forwards the packets in the identified packet stream to the one or more SAPs.

[0017] According to another aspect of embodiments herein, the object is achieved by a first network node. The first network node is configured to handle packets of a packet stream in a communications network. The packet stream is adapted to be related to a transmission in a UE data session from the first network node towards a second network node via intermediate nodes in a transport network of the communications network. The transport network is adapted to comprise any one or more out of: a backhaul network and midhaul network. The first network node is further configured to obtain a stream identifier identifying the packet stream based on characteristics of the packet stream. The first network node is further configured to mark the respective packet in the packet stream with the stream identifier. The first network node is further configured to transmit the stream identifier marked packets of the packet stream towards the second network node.

[0018] The stream identifier is adapted to enable the respective first network node, second network node and intermediate nodes to identify the packet stream and obtain rules related to forwarding the packets of the identified packet stream towards the second network node. The stream identifier is adapted to enable the respective first network node, second network node and intermediate nodes to, based on the obtained rules, control traffic steering and / or distribution of the packets comprised in the identified packet stream, when forwarding the marked packets towards the second network node.

[0019] According to an aspect of embodiments herein, the object is achieved by a first intermediate node. The first intermediate node is configured to handle packets of a packet stream in a communications network. The packet stream is adapted to be related to a transmission in a UE data session from a first network node towards a second network node via the first intermediate node and other intermediate nodes in a transport network of the communications network. The transport network is adapted to comprise any one or more out of a backhaul network and midhaul network. The first intermediate node is further configured to receive packets of the packet stream. The respective packet of the packet stream is adapted to be marked with a stream identifier identifying the packet stream. The first intermediate node is further configured to, based on the stream identifier, obtain rules related to forwarding the packets of the identified packet stream towards the second network node. The first intermediate node is further configured to, based on the obtained rules, control any one or more out of: traffic steering and distribution, of the packets comprised in the identified packet stream, when forwarding the marked packets in the packet stream towards the second network node.

[0020] According to an aspect of embodiments herein, the object is achieved by a second network node. The second network node is configured to handle packets of a packet stream in a communications network. The packet stream is adapted to be related to a transmission in a UE data session from a first network node towards the second network node via intermediate nodes in a transport network of the communications network. The transport network is adapted to comprise any one or more out of a backhaul network and a midhaul network. The second network node is further configured to receive packets of the packet stream. The respective packet of the packet stream is adapted to be marked with a stream identifier identifying the packet stream. The second network node is further configured to, based on the identifier, obtain information about one or more SAPs and rules related to forward the packets of the packet stream to the one or more SAPs. The second network node is further configured to, based on the obtained information and rules, forward the packets in the identified packet stream to the one or more SAPs.

[0021] Thanks to that the packet streams in the backhaul transport network and / or midhaul transport network are marked with the stream identifier, the first network node, the second network node and the intermediate nodes are enabled to obtain rules based on the characteristics of the packet streams, and based on the obtained rules, control traffic steering and / or distribution of the packets comprised in the identified packet stream, when transmitting or forwarding the packets in the packet stream towards the second network node. This will result in an improved transmission of packet streams in a communications network.

[0022] BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Examples of embodiments herein are described in more detail with reference to attached drawings in which:

[0024] Figure 1 is a schematic block diagram illustrating prior art.

[0025] Figure 2 is a schematic block diagram illustrating prior art.

[0026] Figure 3a is a schematic block diagram illustrating embodiments of a communications network.

[0027] Figure 3b is a schematic block diagram illustrating embodiments of a communications network. Figure 3c is a schematic block diagram illustrating embodiments of a communications network.

[0028] Figure 3d is a schematic block diagram illustrating embodiments of a communications network.

[0029] Figure 4 is a flowchart depicting an embodiment of a method in a first network node.

[0030] Figure 5 is a flowchart depicting an embodiment of a method in an intermediate node.

[0031] Figure 6 is a flowchart depicting an embodiment of a method in a second network node.

[0032] Figure 7 is a schematic block diagram illustrating an example embodiment herein.

[0033] Figure 8 is a schematic block diagram illustrating an example embodiment herein.

[0034] Figure 9 is a schematic block diagram illustrating an example embodiment herein.

[0035] Figure 10 is a schematic block diagram illustrating an example embodiment herein.

[0036] Figure 11 is a schematic block diagram illustrating an example embodiment herein.

[0037] Figure 12 is a schematic block diagram illustrating an example embodiment herein.

[0038] Figure 13 is a schematic block diagram illustrating an example embodiment herein.

[0039] Figure 14 is a schematic block diagram illustrating an example embodiment herein.

[0040] Figure 15 is a schematic block diagram illustrating an example embodiment herein.

[0041] Figure 16 is a schematic block diagram illustrating embodiments of a first network node.

[0042] Figure 17 is a schematic block diagram illustrating embodiments of an intermediate node.

[0043] Figure 18 is a schematic block diagram illustrating embodiments of a second network node.

[0044] Figure 19 schematically illustrates embodiments of a communication system.

[0045] Figure 20 is a generalized block diagram of embodiments of a UE.

[0046] Figure 21 is a generalized block diagram of embodiments of a network node.

[0047] Figure 22 is a generalized block diagram of embodiments of a host.

[0048] Figure 23 is a generalized block diagram of embodiments of a virtualization environment.

[0049] Figure 24 is a generalized block diagram of embodiments of a communication diagram of a host.

[0050] DETAILED DESCRIPTION

[0051] As part of developing embodiments herein, the inventors identified some problems that first will be described.

[0052] In mobile backhaul and / or midhaul transport networks today, a Tunnel Endpoint Identifier (TEID) parameter may be identified and / or parsed by a transport equipment such as e.g., mobile core, Switch / Router (SWR), Central Unit (CU) / virtual Central Unit (vCU), and Base Station. If there is a split into a Central Unit (CU) / virtual Central Unit (vCU) and Distributed Unit (DU) / virtual Distributed Unit (vDU)and hence the TEID parameter is used to perform some level of traffic handling. A problem is that when encryption is applied to the packet streams transmitted through a midhaul and / or backhaul transport networks, the TEID parameter is not visible to the transport network nodes and hence the TEID parameter cannot be used for traffic handling anymore. Furthermore, when network slicing is used, which also is becoming more and more common, the slicing information is not available in the data-plane packet streams transmitted over the user-plane but is exchanged separately in other control-plane signaling. A data-plane when used herein e.g., means the 3GPP S1- u or NG-u interface between mobile core and radio access network (RAN) network (backhaul), or the 3GPP F1-u interface between CU / vCU and DU / vDU (midhaul). A controlplane when used herein e.g., means the 3GPP S1-c or NG-c interface between the mobile core and the RAN network (backhaul), or the 3GPP F1-cinterface between CU / vCU and DU / vDU (midhaul). In both these cases, it is not possible to perform controlled and / or efficient distribution of packets in packet streams over multiple links and paths in the midhaul and backhaul transport networks. It is also not possible to perform steering of any individual UE packet streams. There exist proposals to make the slice identifier visible for the transport networks, but that is in no relation to service class or UE-PDU session. It is neither in relation to addressing the challenges with traffic steering, traffic distribution and traffic handling in the backhaul / midhaul transport networks. Packet streams transmitted through intermediate nodes in the backhaul / midhaul transport networks with network slicing do not have the required slicing information so they cannot control distribution of packets over multiple links or paths in these transport networks and cannot control traffic steering of the packets in the respective transport networks. When encryption is applied to the packet streams in the backhaul / midhaul transport networks, the TEID parameters is not visible and hence the intermediate nodes can neither control distribution of the packets in the packet streams over multiple links or paths nor control packet traffic steering in the respective transport networks.

[0053] Figure 2 shows an example of today’s technology using Multiple addresses IP and TEID for unencrypted, no slicing packet streams. The packet streams are sent between multiple IP endpoint addresses referred to as IP A, IP B and IP C at a Core Network (CN) endpoint and IP 1 , IP 2 and IP 3, at a RAN endpoint. In this example, TEID identifiers are used to identify the packet streams. The backhaul / midhaul transport network nodes cannot get multiple information input such as slices, their Quality of Service (QoS), individual UE sessions, any of the alternatives GPRS Tunnelling Protocol User Plane (GTP-U), TEID or Quick User data protocol Internet Connection (QUIC) Connection ID, to perform controlled distribution of packets over multiple links or paths and controlled packet traffic steering in the respective transport networks. GPRS is the abbreviation for General Packet Radio Service.

[0054] As mentioned above, an object of embodiments herein is to improve the transmission of packet streams in backhaul and / or midhaul transport networks of a communications network.

[0055] Embodiments herein, e.g., relate to a use of single, or few, source and / or destination network addresses for addressing between the backhaul and / or midhaul endpoint nodes. In some embodiments herein, the source endpoint node is referred to as a first network node, and the destination endpoint node is referred to as a second network node. As mentioned above, the wording “mobile backhaul and / or mobile midhaul” is referred to as “backhaul / midhaul” herein.

[0056] Embodiments herein may further relate to a first network node such as e.g., a RAN node and / or a CN node that marks respective packet of a packet stream with a stream identifier when transmitting the packet stream through a backhaul / midhaul transport network. The stream identifier identifies the packet stream associated with each packet.

[0057] Embodiments herein may further relate to nodes such as a first, and / or second network node e.g., a RAN node and / or a CN node and / or an intermediate node. These nodes are enabled to, use the stream identifier of the packets to identify the packet stream associated with the respective packet and to obtain rules to control traffic steering and / or distribution of the packets comprised in the identified packet stream.

[0058] Thus, stream identifier may then e.g., be used by any of the first network node, the intermediate nodes and / or the second network node for:

[0059] - Identifying individual backhaul / midhaul packet streams.

[0060] - Controlling distribution of packets of identified packet streams across multiple links between RAN / CN and backhaul / midhaul transport network nodes.

[0061] - Controlling distribution of packets of the identified packet streams across multiple links between backhaul / midhaul transport nodes. - Controlling traffic steering of packets of the identified packet streams in backhaul / midhaul transport networks across multiple network paths between RAN / CN endpoints.

[0062] - In the second network node, perform a first level of a backhaul / midhaul packet stream steering towards applicable processing element such as e.g., SAP, without performing decryption.

[0063] The stream identifier may be comprised in any one or more out of: an MPLS Label Segment Routing-Multi Protocol Label Switching (SR-MPLS) an IPv6 Segment Routing path, an IPv6 Flow label, an IPv6 extension header, and an IPv4 option header.

[0064] The stream identifier may be used by the first network node, the intermediate nodes and / or the second network node e.g., a RAN node, a CN and backhaul / midhaul transport network node.

[0065] Embodiments herein may provide one or more of the following advantages:

[0066] A packet marked with the stream identifier identifying the packet stream, is visible in the RAN, the backhaul / midhaul transport network and at the receiving RAN and / or CN endpoint node, both when encryption is not applied and when encryption is applied on a packet stream, such as e.g., a slicing packet stream. It should be noted that the words “encrypt” and “encode” have a similar meaning and may be used interchangeably herein. The stream identifier may be used to perform controlled explicit traffic steering and distribution of packet streams both in backhaul / midhaul transport and in RAN / Core endpoint nodes. The stream identifier is further used to achieve characteristics needs for the respective identified packet stream. This is advantageous in backhaul / midhaul transport networks for new services such as slicing and capabilities like NRAR. Embodiments provided herein realize a more efficient utilization of backhaul / midhaul transport network resources and improved service characteristics. This enables possibilities for lower Operating expenses or Expenditure (OPEX) in backhaul / midhaul packet transport networks.

[0067] Figure 3a is a schematic overview depicting a communications network 100 wherein embodiments herein may be implemented. The communications network 100 e.g., comprises one or more RANs 104, and one or more CNs 106.

[0068] The communications network 100 may use 5G NR but may further use a number of other different technologies, such as, 6G, Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

[0069] The communications network 100 comprises a transport network 102, comprising any one or more out of: a backhaul transport network and a midhaul transport network. A transport network may e.g., comprise transport equipment, such as intermediate nodes, that connects the RAN nodes, e.g., RAN node endpoints, a RAN node end point to a CN node endpoint, or a CN node endpoint to a RAN node endpoint. This may be referred to as connecting a first network node to a second network node. The transport equipment also referred to as intermediate nodes may comprise, switches, routers, optical equipment, and / or wireless transport equipment such as microwave, fibres, or other applicable transport technologies.

[0070] RAN nodes, such as e.g., a first RAN node 111 and a second RAN node 112, operate in the RAN 104 of the communications network 100. Each of the first and second RAN nodes 111 , 112 may be a transmission and reception point e.g. a base station, such as a NodeB, an evolved Node B (eNB, eNode B), an NR Node B (gNB), a base transceiver station, a CU / vCU and DU / vDU, a radio Remote Unit (RU), an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), an access controller, or any other network unit capable of communicating with UEs, such as a UE 121 , within a cell, served by the respective first and second RAN nodes 111 , 112. The respective first and second RAN nodes 111 , 112 may be referred to as a serving RAN node and may communicate with the UE 121 with Downlink (DL) transmissions to the UE 121 and Uplink (UL) transmissions from the UE 121.

[0071] Intermediate nodes, such as a first intermediate node 113, and other intermediate nodes, referred to as intermediate nodes 114, operate in the backhaul / midhaul transport network 102. The term first in the wording “first intermediate node” is just to give one intermediate node a specific name to differ it from the other intermediate nodes. It has nothing to do with any order of a node in a chain of intermediate nodes that is receiving and forwarding any packet. The first intermediate node 113 may be next to the first network node 131 as being a source node endpoint, between intermediate nodes 114 or next to the second network node 132 as being a target node endpoint. One or more UEs operate in the wireless communication network 100, such as e.g., the UE 121. The UE 121 may e.g., be a wireless device, an NR device, a mobile station, a wireless terminal, an NB-loT device, an MTC device, an eMTC device, a CAT-M device, a WiFi device, an LTE device and a non-access point (non-AP) STA, a STA. The UE may communicate via a RAN node such as e.g., the first RAN node 111 and / or the second RAN node 112, and one or more CN nodes in one or more CNs, with one or more SAPs, e.g. operating in one or more clouds 170. It should be understood by the skilled in the art that “UE” is a non-limiting term which means any terminal, client, mobile client, IMS client, wireless communication terminal, user equipment, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a car or any small base station communicating within a cell.

[0072] CN nodes, such as a CN node 130 operate in the CN 106 of the communications network 100.

[0073] Network nodes, such as a first network node 131 and a second network node 132, operate in the communications network 100. The first network node 131 and a second network node 132, may be endpoints in an example scenario that will be described below. The first network node 131 may be referred to as a source endpoint and the second network node 132 may be referred to as a destination endpoint.

[0074] The first network node 131 may be represented by any one out of: the first RAN node 111 , the second RAN node 112, or the CN node 130. Further, the second network node 132 may also be represented by any one out of: the first RAN node 111 , the second RAN node 112, or the CN node 130. These will be explained more in detail below.

[0075] Backhaul

[0076] In some embodiments the transport network 102 is represented by a backhaul network. The backhaul network is a transport network between the CN 106 and the RAN 104. The RAN 104 may be a split such that the first RAN node 111 and / or the second RAN node 112 are a split between a CU / virtual Central Unit (vCU) node and a Distributed Unit (DU) / virtual DU (vDU) node.

[0077] When the RAN 104 is not split, then the first RAN node 111 and / or the second RAN node 112 may be a combined and / or co-located vCU - vDU node or combined CU-DU node. In case data traffic of a packet stream is DL, the first network node 131 is a CN node such as the CN node 130 and the second network node 132 is a RAN node such as the first RAN node 111 or the second RAN node 112. The RAN node may thus be a vCU or a CU or, a Combined vCU and virtual Distributed Unit or a combined CU and Distributed Unit DU. Thus, when the transport network 102 is represented by the backhaul network, the first network node 131 may be represented by the CN node 130 in the CN 106 of the communications network 100, and the second network node 132 may be represented by a RAN node such as any of the first or second RAN 111 , 112 in the RAN 104 of the communications network 100. This is depicted in Figure 3b. Figure 3b depicts a DL backhaul transport network.

[0078] In case data traffic of a packet stream is UL, the first network node 131 is a RAN node such as the first RAN node 111 , and the second network node 132 is a CN node such as the CN node 130. In these embodiments, the RAN node may e.g., be a vCU or a CU, or a combined vCU and vDU or combined CU and DU.

[0079] Thus, when the transport network 102 is represented by a backhaul network, the first network node 131 may be represented by a RAN node such as any of the first or second RAN 111 , 112 in the RAN 104 of the communications network 100 and the second network node 132 may be represented by a CN node 130 in a CN 106 of the communications network 100. This is depicted in Figure 3c. Figure 3c depicts a UL backhaul transport network.

[0080] If there is no split CU / vCU and DU / vDU then there is no midhaul domain and the backhaul domain ends at the RAN comprising a RAN node using a combined RAN node such as a combined CD / DU, vCU / vDU. The first RAN node 111 may be represented by the combined CD / DU, vCU / vDU.

[0081] Midhaul

[0082] In some embodiments the transport network 102 is represented by a midhaul network. The midhaul transport network may exist when there is split of the RAN nodes 111 , 112 into vCU / CU and vDU / DU._The midhaul network may in these embodiments be the transport network 102 between a CU / vCU and a DU / vDU for example between the first RAN node 111 and the second RAN node 112. One of the RAN nodes is vCU or CU and the other of the RAN nodes is vDU or DU. In these embodiments, where the transport network 102 is represented by a midhaul network, the first network node 131 is represented by the first RAN node 111 in the RAN 104 of the communications network 100, and the second network node 132 is represented by the second RAN node 112 in the RAN 104 of the communications network 100. This is depicted in Figure 3d.

[0083] In DL, the first network node 131 is represented by the first RAN node 111 in these embodiments being a CU / vCll and the second network node 132 is represented by the second RAN node 112 in these embodiments being a Dll / vDU.

[0084] In UL, the first network node 131 is represented the second RAN node 112 in these embodiments being a Dll / vDU by and the second network node 132 is represented by the first RAN node 111 in these embodiments being a CU / vCll.

[0085] Methods according to embodiments herein are performed by the first network node 131 , the first intermediate node 113 and the second network node 132. These nodes may be Distributed Nodes (DN)s with functionality, e.g., comprised in the cloud 170 as shown in Figure 3a.

[0086] According to embodiments herein, a packet stream identifier is used for identifying, steering, and distributing packet streams in any one or more out of the backhaul and / or midhaul transport network 102, the RAN 104 and the CN 106.

[0087] A number of embodiments will now be described, some of which may be seen as alternatives, while some may be used in combination.

[0088] A method according to embodiments herein will be described in a general way as seen from the view of the first network node 131 together with Figure 4, from the view of the first intermediate node 113 together with Figure 5, and from the view of the second RAN node 132 together with Figure 6. This will be followed by a more detailed description with implementing examples of the method.

[0089] Figure 4 shows examples of embodiments of a method performed by the first network node 131. The method is for handling packets of a packet stream in a wireless communications network 100. The packet stream is related to a transmission in a UE 121 data session from the first network node 131 towards a second network node 132, via intermediate nodes 113, 114 in a transport network 102 of the communications network 100. The transport network 102 comprises any one or more out of: a backhaul network and midhaul network.

[0090] When the transport network 102 is represented by a backhaul network, then the first network node 131 may e.g., be represented by the CN node 130 in a CN 106 of the communications network 100, and the second network node 132 may e.g., be represented by a RAN node 111 , 112 in a RAN 104 of the communications network 100, or,

[0091] When the transport network 102 is represented by a backhaul network, then the first network node 131 may e.g., be represented by RAN node 111 , 112 in a RAN 104 of the communications network 100 and the second network node 132 may e.g., be represented by the CN node 130 in the CN 106 of the communications network 100, and,

[0092] When the transport network 102 is represented by a midhaul network, then the first network node 131 may e.g., be represented by a first RAN node 111 in a RAN 104 of the communications network 100, and the second network node 132 may e.g., be represented by a second RAN, node 112 in a RAN 104 of the communications network 100.

[0093] The method comprises the following actions, which actions may be taken in any suitable order. Optional actions are referred to as dashed boxes in Figure 4.

[0094] According to an example scenario, the first network node 131 receives packets of the packet stream, e.g., from an originating SAP, which packets are to be sent in the transport network 102 via one or more chains of nodes comprising the first network node 131 and one or more of the intermediate nodes 113, 114 towards the second network node 132. In order to make it possible for any nodes in the chain to control traffic steering and / or distribution of the packets when transmitting or forwarding them, a stream identifier will be used that is visible to the nodes in the chain even when the packet stream is encrypted or when it is related to network slicing.

[0095] Action 401 .

[0096] The first network node 131 may receive from an originating SAP, packets to be sent in the packet stream from the first network node 131 towards the second network node 132.

[0097] Action 402.

[0098] The first network node 131 obtains a stream identifier identifying the received packet stream based on characteristics of the packet stream. This may for example be performed by creating it based on principles for how to interpret and identify different characteristics requirements, steering and distribution of the packet stream. It may also be obtained by receiving it from a controller equipment, given characteristics requirements, steering and distribution of the packet stream as input to the controller. As a further alternative, it may be obtained by being configured by management equipment for related characteristics needs.

[0099] The stream identifier may also be referred to as a backhaul / midhaul packet stream identifier, a backhaul packet stream identifier, a midhaul packet stream identifier, or a mobile backhaul / midhaul packet stream identifier.

[0100] The stream identifier may e.g., be comprised in any one out of: an Internet Protocol version 6 (IPv6) flow-label, an IPv6 Extension header, IPv6 segment routing (SRv6) segment identifier (SID), Segment Routing-Multi Protocol Label Switching (SR-MPLS), label, segment identifier SID, Multi Protocol Label Switching (MPLS), label and an Internet Protocol version 4 (IPv4) option header. The stream identifier may e.g., indicate any one out of: a UE 121 data session Identifier (ID) of the packet stream, a backhaul tunnel ID related to the packet stream, a midhaul tunnel ID related to the packet stream, and a slice ID and / or slice service characteristics, when the data stream is related to network slicing. In some embodiments, the packet stream may comprise network slicing packets. The slicing packets may e.g., be related to connections for a specific organization or company, alternatively it can be a specific mobile network service with e.g., certain requirements. Another example may be a specific user service with e.g., specific requirements. In these embodiments, the stream identifier may comprise an ID of the slice and / or slice service characteristics. Slicing information as defined in 3GPP standardization, has a Slice Service Type (SST) parameter and a Service Differentiator (SD) parameter. The SST may define a slice and / or a service type and as such the characteristics for that slice / service type. The SD may be used to differentiate between multiple slices using the same SST. The stream identifier may utilize the SD to identify a specific slice, among multiple slices, utilizing the same SST.

[0101] The stream identifier may e.g., be used for the traffic steering in any one or more out of the transport network 102, the RAN 104, and the CN 106. In some embodiments, the characteristics may comprise any one or more out of: the bitrate, delay, delay-variation, inorder delivery, related to the packet stream. This e.g., means that these characteristics define which stream identifier to select among a number of selectable stream identifiers.

[0102] Action 403. The first network node 131 then marks the respective packet in the packet stream with the stream identifier. Different examples of how this is performed will be described more in detail below.

[0103] In some embodiments, the packets of the packet stream are not encrypted, e.g., in cases like when the network is considered to be secured by other means e.g., within physically secured perimeter or when the network comprises just a short cable. In some embodiments, a part of the packets of the identified packet stream may be encrypted. For example, when packet stream traverses a transport network that may be compromised in different ways and needs to be secured from one or many of the perspective’s confidentiality, integrity, and authentication. In some of these embodiments, the stream identifier may be located outside the encrypted part of the respective packet when marked. In this way the stream identifier is visible to the respective first network node 131 , intermediate nodes 113, 114 and second network node 132 without performing decryption of the packets.

[0104] Action 404.

[0105] The first network node 131 may obtain rules based on the stream identifier comprising the characteristics of the packet stream. These rules may e.g., relate to the forwarding of the packets in the transport network 102 towards the second network node 132 based on the stream identifier. This may for example be performed by using the stream identifier as input when looking up associated forwarding rules in a forwarding policy table.

[0106] Action 405.

[0107] The first network node 131 transmits the stream identifier marked packets of the packet stream towards the second network node 132. According to the example scenario, the stream identifier marked packets are transmitted to one or more next nodes in one or more chains of intermediate nodes 113, 114 towards the second network node 132. Each node in a chain will receive marked packets and by means of obtaining information from the stream identifier control and / or distribute forwarding of the packets to a next intermediate node in the chain or to the second network node if that node is the next node in the chain.

[0108] The stream identifier enables the respective first network node 131 , second network node 132 and intermediate nodes 113, 114 to identify the packet stream and obtain rules related to forwarding the packets of the identified packet stream towards the second network node 132. The stream identifier further enables the respective first network node 131 , second network node 132 and intermediate nodes 113, 114 to, based on the obtained rules, control traffic steering and / or distribution of the packets comprised in the identified packet stream, when forwarding the marked packets towards the second network node 132.

[0109] As mentioned above in Action 404, in some embodiments the first network node 131 has obtained rules related to transmitting the packets of the packet stream towards the second network node 132. In these embodiments, the first network node 131 may, based on the obtained rules, actually control traffic steering and / or distribution of the packets comprised in the identified packet stream, at the transmitting of the packets in the packet stream towards the second network node 132.

[0110] In some embodiments, rules may be assigned to characteristics to be fulfilled for forwarding the respective packet in the identified packet stream. A rule when used herein may e.g., mean a requirement to fulfil characteristics which are required for forwarding the respective packet in the identified packet stream. A rule may e.g., be steering the packet stream onto a path towards an end-point that fulfils one or more characteristics requirements. Another rule may e.g., be to allow or not allow a packet stream to be distributed over physical or logical link. Yet another rule may e.g., be to use the identifier when calculating the distribution of packet streams over physical or logical links. This may be performed with only the identifier or together with other transport information such as e.g., a source and / or a destination Medium Access Control (MAC) protocol or IP address, TCP or UDP port number, transport protocol e.g., GTP. The rules may relate to requirements on e.g., bitrate, delay, delay-variation, in-order delivery, related to the packet stream.

[0111] The rules when obtained to control traffic steering and / or distribution, may relate to which path to use and how to distribute the packets over different links along this path when transmitting and / or forwarding the packets of the packet stream towards the second network node 132.

[0112] The distribution of the packets may e.g., be performed across one or multiple links between any one or more out of RAN, CN, and transport network nodes 111 , 112, 113, 114, 130, 131 , 132.

[0113] The distribution of the packets may e.g., be further performed across one or multiple links between intermediate nodes 113, 114, in the transport network 102, and over different alternative paths.

[0114] Regarding the control of the traffic steering and / or distribution of the packet stream based on the obtained rules, the first network node 131 may e.g., select the path and / or different links using different technologies. For example, by using rules related to any one of segment routing, policy routing, policy switching, load-balancing mechanism for the path and / or different links, e.g., utilizing load-balancing mechanism based on “instantaneous” port utilisation.

[0115] In this way, by performing the above method, the stream identifier will be visible by the intermediate nodes 113, 114 in the transport network 102 and at the second network node 132, even when encryption is applied on the packet stream and when the data stream is related to network slicing. The stream identifier may then e.g., be used to perform explicit traffic steering and distribution of packet streams both in transport network and in mobile backhaul and / or midhaul endpoints such as the first and second network nodes 131 , 132, by achieving characteristics needs for the respective packet streams.

[0116] Figure 5 shows examples of embodiments of a method performed by a first intermediate node 113 for handling packets of a packet stream in a communications network 100. The packet stream is related to a transmission in a UE 121 data session from a first network node 131 towards a second network node 132, via the first intermediate node 113 and other intermediate nodes 114 in a transport network 102 of the communications network 100. The transport network 102 comprises any one or more out of a backhaul network and midhaul network.

[0117] When the transport network 102 is represented by a backhaul network, then the first network node 131 may e.g., be represented by the CN node 130 in the CN 106 of the communications network 100, and the second network node 132 may e.g., be represented by a RAN, node 111 , 112 in a RAN 104 of the communications network 100, or,

[0118] When the transport network 102 is represented by a backhaul network, then the first network node 131 may e.g., be represented by RAN node 111 , 112 in a RAN 104 of the communications network 100 and the second network node 132 may e.g., be represented by the CN node 130 in the CN 106 of the communications network 100, and,

[0119] When the transport network 102 is represented by a midhaul network, then the first network node 131 may e.g., be represented by a first RAN node 111 in a RAN 104 of the communications network 100, and the second network node 132 may e.g., be represented by a second RAN, node 112 in a RAN 104 of the communications network 100.

[0120] The method comprises the following actions, which actions may be taken in any suitable order. According to the example scenario, the first intermediate node 113 receives packets marked with the stream identifier from e.g., the first network node 131 or another of the intermediate nodes 114. The packets are to be sent in the transport network 102 via chain of nodes comprising the first network node 131 and the intermediate nodes 113, 114 towards the second network node 132. The first intermediate node 113 uses the stream identifier to obtain e.g., information related to the suitable path and / or link for steering and / or distribution of the packets. Based on the obtained information, the packets are then forwarded through the selected path and / or link to e.g., the next node in the chain such as the other intermediate node 114 or to the second network node 132.

[0121] Action 501.

[0122] The first intermediate node 113 receives packets of the packet stream. The respective packet of the packet stream is marked with a stream identifier identifying the packet stream.

[0123] The stream identifier may e.g., be comprised in any one out of: an IPv6 flow-label, an IPv6 Extension header, SRv6 SID, SR-MPLS label, SID, MPLS label and an IPv4 option header.

[0124] The stream identifier may e.g., indicate any one or more out of: a UE 121 data session ID of the packet stream, a backhaul tunnel ID related to the packet stream, a midhaul tunnel ID related to the packet stream, and a slice ID and / or slice service characteristics, when the data stream is related to network slicing.

[0125] In some embodiments, the packets of the packet stream are not encrypted. In some embodiments, a part of the packets of the identified packet stream may be encrypted. In some of these embodiments, the stream identifier is located outside the encrypted part of the respective packet when marked. In this way the stream identifier is visible to the first intermediate node 113 without performing decryption of the packets.

[0126] Action 502.

[0127] Based on the stream identifier, the first intermediate node 113 obtains rules related to forwarding the packets of the identified packet stream towards the second network node 132. This may for example be performed by receiving rules from controller equipment given the related identifier, or by being configured by management equipment for the related identifier.

[0128] The rules may be assigned to characteristics to be fulfilled for forwarding the respective packet in the identified packet stream. In some embodiments, the rules may be obtained based on the stream identifier comprising characteristics of the packet stream. In these embodiments, the characteristics comprise any one or more out of: the bitrate, delay, delay-variation, in-order delivery, of the RAN packet stream. In the same way as described above, this e.g., means that these characteristics define which stream identifier the first network node 131 has selected among a number of selectable stream identifiers. The chosen stream identifier marking the packets then e.g., defines which rules the first intermediate node 113 shall select for forwarding the packets further in the transport network 102.

[0129] The rule principles may be applied differently depending on where in the node chain the intermediate node 113 is placed, i.e., whether the intermediate node 113 is receiving the packets directly from the first network node 131 or one of the other intermediate nodes 114.

[0130] If the intermediate node 113 has received the packets directly from the first network node 131 , the obtained rules may define the use of transport technologies such as e.g., MPLS, policy routing, or segment routing, for the packet stream.

[0131] If the intermediate node 113 has received the packets directly from one of the other intermediate nodes 114 and is the last intermediate node before the receiving network node 132, the obtained rules may determine to terminate the used transport technology used in previous intermediate nodes.

[0132] Action 503.

[0133] Based on the obtained rules, the first intermediate node 113 controls any one or more out of: traffic steering and distribution, of the packets comprised in the identified packet stream, when forwarding the marked packets in the packet stream towards the second network node 132. As mentioned in Action 502, the first intermediate node 113 may have obtained from the stream identifier, the rules related to forwarding the packets of the packet stream towards the second network node 132. The first intermediate node 113 may then by means of the obtained information control and / or distribute the forwarding of the packets to a next intermediate node 114 in the transport network 102 chain or to the second network node 132 if that node is the next node in the chain.

[0134] This may be performed in different ways depending on where in the node chain the intermediate node 113 is placed, i.e., whether the intermediate node 113 shall forward the packets directly to one of the other intermediate nodes 114 or to the second network node 132.

[0135] If the intermediate node 113 shall forward the packets directly to one of the other intermediate nodes 114, the intermediate node 113 may apply different transport technologies defined in the obtained rules to perform traffic steering of packet stream onto applicable path and / or apply different load-balancing mechanisms to perform distribution of packet stream over physical or logical links.

[0136] If the intermediate node 113 shall forward the packets directly to the second network node 132, the intermediate node 113 may terminate the earlier intermediate nodes applied transport technology and if applicable apply load-balancing mechanisms defined by the obtained rules to perform distribution of packet stream over physical or logical links.

[0137] In some embodiments, the rules when obtained, to control traffic steering and / or distribution, relate to which path to use and how to distribute the packets over different links along this path, when forwarding the packets of the packet stream towards the second network node 132. The distribution of the packets may be performed according to any one or more out of:

[0138] -across one or multiple links between the first intermediate node 113 and a RAN node 111 , 112,131 , 132,

[0139] -across one or multiple links between the first intermediate node 113 and the CN node 130, 131 , 132, and

[0140] -across one or multiple links between the first intermediate node 113 and another intermediate node 114 in the transport network 102, and

[0141] -over different alternative paths.

[0142] In some embodiments, the identified packet stream may e.g., be directed to a selected alternative path and / or the packets may e.g., be divided over different links on that path.

[0143] Regarding the control of the traffic steering and / or distribution of the packet stream based on the obtained rules, the first intermediate node 113 may e.g., select the path and / or different links based on available bitrate, delay, etc. and / or the used technology. For example, by using any one of segment routing, policy routing, policy switching, loadbalancing mechanism for the path and / or different links, e.g. load balancing mechanism based on any of “instantaneous” port utilization, and / or rule obtained from identifier.

[0144] In this way, by performing the above method, the intermediate node 113 uses the visibility of the stream identifier to perform explicit traffic steering and distribution of packet streams in the transport network 102 e.g., to the next intermediate node 114 or to the second network node 132, by achieving characteristics needs for the respective RAN packet streams even when encryption is applied and when the data stream is related to network slicing. Figure 6 shows examples of embodiments of a method performed by a second network node 132 for handling packets of a packet stream in a communications network 100. The packet stream is related to a transmission in a UE 121 data session from the first network node 131 towards the second network node 132, via one or more of the intermediate nodes 113, 114 in the transport network 102 of the communications network 100. The transport network 102 comprises any one or more out of a backhaul network and a midhaul network.

[0145] When the transport network 102 is represented by a backhaul network, then the first network node 131 may e.g., be represented by the CN node 130 in the CN 106 of the communications network 100, and the second network node 132 may e.g., be represented by a RAN node 111 , 112 in the RAN 104 of the communications network 100, or,

[0146] When the transport network 102 is represented by a backhaul network, then the first network node 131 may e.g., be represented by a RAN node e.g., the first RAN node 111 in the RAN 104 of the communications network 100 and the second network node 132 may e.g., be represented by the CN node 130 in the CN 106 of the communications network 100, and,

[0147] When the transport network 102 is represented by a midhaul network, then the first network node 131 may e.g., be represented by a first RAN node 111 in a RAN 104 of the communications network 100, and the second network node 132 may e.g., be represented by a second RAN, node 112 in a RAN 104 of the communications network 100.

[0148] The method comprises the following actions, which actions may be taken in any suitable order.

[0149] According to the example scenario, the second network node 132 receives packets marked with the stream identifier from e.g., any of the intermediate nodes 113, 114. The marked packets have been sent in the transport network 102 via a chain of nodes comprising the first network node 131 and one or more of the intermediate nodes 113, 114 towards the second network node 132. The second network node 132 uses the stream identifier to obtain e.g., information related to the suitable path and / or link for steering and / or distribution of the packets. Based on the obtained information, the packets are then forwarded through the selected path and / or link to e.g., one or more SAPs.

[0150] Action 601.

[0151] The second network node 132 receives packets of the packet stream. The respective packet of the packet stream is marked with a stream identifier identifying the packet stream. The stream identifier may e.g., be comprised in any one out of: an IPv6 flow-label, an IPv6 Extension header, IPv6 SRv6 SID, SR-MPLS label segment identifier SID, MPLS label and an IPv4 option header.

[0152] The stream identifier may e.g., indicate any one or more out of: a UE 121 data session ID of the packet stream, a backhaul tunnel ID related to the packet stream, a midhaul tunnel ID related to the packet stream, and a slice identifier and / or slice service characteristics, when the data stream is related to network slicing.

[0153] The stream identifier may e.g., be used for the traffic steering in any one or more out of the RAN 104 of the communications network 100, and the CN 106 in the communications network 100.

[0154] In some embodiments, the packets of the packet stream are not encrypted. In some other embodiments, a part of the packets of the identified packet stream may be encrypted. In some of these embodiments, the stream identifier is located outside the encrypted part of the respective packet when marked. In this way, the stream identifier is visible to the second network node 132 without performing decryption of the packets.

[0155] Action 602.

[0156] Based on the identifier, the second network node 132 obtains information about one or more SAPs and rules related to forwarding the packets of the packet stream to the one or more SAPs. This may for example be performed by, based on the stream identifier, the second network node 132 that makes a look-up in a policy forwarding table to identify what rule the identifier relates to. The rules may be assigned to characteristics to be fulfilled for forwarding the respective packet in the identified packet stream. In some embodiments, the rules are obtained based on the stream identifier comprising characteristics of the packet stream. In these embodiments, the characteristics comprise any one or more out of: the bitrate, delay, delay-variation, in-order delivery, of the packet stream. This e.g., means that these characteristics define which stream identifier the first network node 131 has selected among a number of selectable stream identifiers. The selected stream identifier marking the packets then e.g., defines which rules the second network node 132 shall select for forwarding the packets further to one or more SAPs associated with the second network node 132.

[0157] Action 603.

[0158] Based on the obtained information and rules, the second network node 132 forwards the packets in the identified packet stream to the one or more SAPs. As mentioned in Action 602, the second network node 132 has obtained from the stream identifier the rules related to forwarding the packets of the packet stream to the one or more SAPs. The second network node 132 may then by means of the obtained information, control and / or distribute forwarding of the packets to the one or more SAPs.

[0159] In some embodiments, the rules when obtained, to control traffic steering and / or distribution, may relate to which path to use and how to distribute the packets over different links along this path, when forwarding the packets of the packet stream towards the SAPs. Regarding the control of the traffic steering and / or distribution of the packet stream based on the obtained rules, the second network node 132 may e.g., select the path and / or different links based on available bitrate, delay, etc. and / or the used technology. For example, by using any one of segment routing, policy routing, policy switching, loadbalancing mechanism for the path and / or different links between neighbouring nodes with e.g., load balancing mechanism based on any of “instantaneous” port utilization, and / or rule obtained from identifier.

[0160] The distribution of the packets may be performed across one or multiple links between the second network node 132 and the one or more SAPs.

[0161] In this way, by performing the above method, the second network node 132 uses the visibility of the stream identifier to perform explicit traffic steering and distribution of packet streams to the one or more SAPs, by achieving characteristics needs for the respective packet streams even when encryption is applied and when the data stream is related to network slicing.

[0162] Embodiments herein such as the embodiments mentioned above, will now be further described and exemplified. The text below is applicable to and may be combined with any suitable embodiment described above.

[0163] As also mentioned above, the stream identifier will be used to identify the packet streams. To come along with the evolution of backhaul and / or midhaul transport networks towards capabilities such as NRAR and Slicing but also cloud RAN architecture, the stream identifier according to some embodiments herein enables a way to enhance traffic handling capabilities to ensure required characteristics are fulfilled.

[0164] As mentioned above, some embodiments herein provide a backhaul / midhaul networking capability to perform packet stream distribution over multiple links between a chain of nodes such as any of CN and / or RAN and / or intermediate transport nodes, 111 , 112, 113, 114, 130, 131 , 132. Another capability is to perform steering of packet streams over alternative paths in any one or more out of the CN 106 and / or RAN 104 and / or transport networks 102.

[0165] The requirements on confidentiality and integrity may drive a use of encryption, and as has been described earlier. However, the stream identifier according to embodiments herein will be visible to the nodes in the chain even when the packet stream is encrypted or when it is related to network slicing.

[0166] An additional capability may be the possibility to perform a first level of packet stream steering within a CN and / or RAN node, 130, 111 , 112 towards one or more applicable CN / RAN processing element, such as e.g., SAP, without having to first perform decryption. A SAP may be a security processing entity in itself, which then may be identified and steered towards.

[0167] Identifying the packet stream.

[0168] To be able to perform the needed RAN / backhaul / midhaul / UE Packet Stream handling, there is need to identify the backhaul / midhaul packet streams. Some embodiments herein provide a way to define a new backhaul / midhaul packet stream identifier, referred to as the stream identifier, that will be used to identify packets streams in the transport network 102, such as the backhaul / midhaul packet streams. This is illustrated in Figure 7. Figure 7 depicts embodiments implemented in IPv6, with a Single IPv6 source address IPv6 A related to the first network node 131 , in this example represented by the CN node 130, and a Single IPv6 destination address IPv6 B related to the second network node 132, in this example represented by one of the first and / or second RAN node 111 , 112 such as a Baseband (BB) that can also be described as a combined CU / Dll or combined vCU / vDU, a CU / vCll and / or a Dll / vDU. The transmission of packet streams with packets marked with the stream identifier are referred to as dashed lines in the Figure 7.

[0169] The stream identifier addresses multiple challenges at the same time. As mentioned above, it will be visible outside any encryption, bring an identification of slicing packet streams and identification of any backhaul and / or midhaul UE Packet Stream, such as e.g., Tunnel Endpoint Identifier (TEID). Furthermore, a Quick User data protocol Internet Connection (QUIC) protocol is under discussion in standardization as an alternative to GTP, therefore the stream identifier may be implemented in the use of QUIC with its Connection ID (CID) parameter. The numeric-values of the stream identifiers are preferably unique per session, thus per source IP (S-IP) address to destination IP (D-IP) address. This gives good scaling of the identifier since they can be reused on other S-IP / D-IP sessions.

[0170] The stream identifier may also be used in combination with e.g., the ordinary IP header class of service Differentiated Services Code Point (DSCP) parameter, to determine the scheduling and forwarding decisions. DSCP is a means of classifying and managing network traffic and of providing Quality of Service (QoS) in Layer 3 IP networks. It uses the 6-bit Differentiated Services (DS) field in the IP header for the purpose of packet classification.

[0171] The stream identifier may provide an identification of RAN slicing packet streams. Figure 8 illustrates RAN slicing using Slicing-Single Network Slice Selection Assistance Information (S-NSSAI) format. The 8 bit Slice Service Type (SST) indicates the slice and / or service type and the 24 bit Slice Differentiator (SD) is an additional differentiator if multiple network slices carry the same SST value.

[0172] The stream identifier may further provide identification of a UE-PDU-Session TEID. The TEID parameter in GPRS Tunneling Protocol (GTP) version 1 (v1) header is depicted in Figure 9. In Figure 9 the stream identifier is represented by the TEID.

[0173] As mentioned above, the QIIIC protocol is under discussion in standardization as an alternative to GTP. An identification of the QIIIC CID parameter may be represented as different alternative compositions of the stream identifier according to some embodiments herein. The CID parameter length and encoding may be defined and / or negotiated within the QIIIC setup, the length of the CID may be negotiated to be 0, 8, 32 or 64 bit and the proposal is to use a 32-bit length to match the length of a TEID in GTP-ll. This is illustrated in Figure 10 depicting a simplified QIIIC header format.

[0174] Implementation examples of the stream identifier

[0175] Below follows five different implementation alternative embodiments of the stream identifier.

[0176] IPv6 64-bit Extension header. An example of a first alternative of the stream identifier is depicted in Figure 11 illustrating an IPv6 64-bit Extension header. It includes RAN Slicing NSSAI style of parameters SST and SD, but with scaled down numeric values to fit in the 64-bit extension header. This captures the individual slices and the service type. The stream identifier such as a packet stream ID parameter may be either the 32-bit TEID from GTP or a 32-bit CID from QIIIC, depending on what protocol is used and thus also captures the UE PDU session information.

[0177] IPv6 128-bit Extension header. An example of a second alternative of the stream identifier is depicted in Figure 12 illustrating an IPv6 128-bit Extension header. It comprises RAN Slicing NSSAI full size parameters SST and SD. This captures the full information of the NSSAI individual slices and service type. The stream parameter may be either the 32- bit TEID from GTP or a 32-bit CID from QIIIC, depending on what protocol is used and thus also captures the UE PDU session information.

[0178] IPv6 Flow Label header. An example of a third alternative of the stream identifier is depicted in Figure 13 illustrating a IPv6 Flow Label header. The stream identifier may comprise RAN Slicing NSSAI style of parameters SST and SD, but with scaled down numeric values. This is to fit in the 32-bit Flow Label header. This captures the individual Slices and service type but also brings additional entropy for packet stream steering through a 4-bit hash of the GTP-U TEID, and thus also captures the UE PDU session information.

[0179] IPv6 Flow Label header. An example of a fourth alternative of the stream identifier is depicted in Figure 14 also illustrating IPv6 Flow Label header. In this embodiment the stream identifier may comprise RAN Slicing NSSAI style of parameters SST and SD, but with scaled down numeric values to fit in the 20-bit Flow Label header. This captures the individual Slices and service type but also brings additional entropy for packet stream steering through a 4-bit hash of the QUIC CID, and thus also captures the UE PDU session information when QUIC is used instead of GTP-u.

[0180] IPv6 SRv6 SID list encoding. An example of a fifth alternative of the stream identifier is depicted in Figure 15 illustrating an IPv6 SRv6 SID list encoding of the stream identifier. The stream identifier comprises RAN Slicing NSSAI full size parameters SST and SD. It captures the full information of the NSSAI individual Slices and service type. The packet stream ID parameter may be either the 32-bit TEID from GTP-U or a 32-bit CID from QUIC, depending on what protocol is used and thus also captures the UE PDU session information. As in the earlier described alternatives, compressed versions of SST and SD may be applied to fit compressed version of Segment Routing headers. If IPsec tunnel mode is used, the stream identifier may be copied to an outer header flow label or extension header.

[0181] The stream identifier may e.g., be implemented in any one out of:

[0182] - a new IPv6 Extension header,

[0183] - a IPv6 Flow-label,

[0184] - an IPv6 Segment Routing SID,

[0185] - an MPLS Segment Routing SID,

[0186] - an MPLS Label, or

[0187] - a new IPv4 Option header.

[0188] To perform the method actions above, a first network node 131 is configured to handle packets of a packet stream in a communications network 100. The packet stream is adapted to be related to a transmission in a UE 121 data session from the first network node 131 towards the second network node 132, via intermediate nodes 113, 114 in a transport network 102 of the communications network 100. The transport network 102 is adapted to comprise any one or more out of: a backhaul network and midhaul network.

[0189] The first network node 131 may comprise an arrangement depicted in Figure 16. The first network node 131 may comprise an input and output interface 1600 configured to communicate in the communications network 100, e.g., with the intermediate nodes 113, 114, the second network node 132 and a SAP. The input and output interface 1600 may comprise a wireless receiver not shown, and a wireless transmitter not shown.

[0190] The first network node 131 is further configured to obtain a stream identifier identifying the packet stream based on characteristics of the packet stream.

[0191] The first network node 131 is further configured to mark the respective packet in the packet stream with the stream identifier.

[0192] The first network node 131 is further configured to transmit the stream identifier marked packets of the packet stream towards the second network node 132.

[0193] The stream identifier is adapted to enable the respective first network node 131 , second network node 132 and intermediate nodes 113, 114 to:

[0194] - identify the packet stream and obtain rules related to forwarding the packets of the identified packet stream towards the second network node 132, and - based on the obtained rules, control traffic steering and / or distribution of the packets comprised in the identified packet stream, when forwarding the marked packets towards the second network node 132.

[0195] In some embodiments, the stream identifier is adapted to indicate any one out of: a UE 121 data session ID of the packet stream, a backhaul tunnel ID related to the packet stream, a midhaul tunnel ID related to the packet stream, and a slice ID and / or slice service characteristics, when the data stream is related to network slicing.

[0196] In some embodiments, the stream identifier is adapted to be used for the traffic steering in any one or more out of:

[0197] - the transport network 102,

[0198] - a RAN 104 of the communications network 100, and

[0199] - a CN 106 communications network 100.

[0200] In some embodiments, the distribution of the packets is adapted to be performed according to any one or more out of:

[0201] - across one or multiple links between any one or more out of RAN, CN, and transport network nodes 111 , 112, 113, 114, 130, 131 , 132,

[0202] -across one or multiple links between intermediate nodes 113, 114, in the transport network 102, and

[0203] -over different alternative paths.

[0204] In some embodiments, the characteristics are adapted to comprise any one or more out of: the bitrate, delay, delay-variation, in-order delivery, related to the packet stream.

[0205] In some embodiments, the rules are adapted to be assigned to characteristics to be fulfilled for forwarding the respective packet in the identified packet stream.

[0206] The rules may be adapted to be obtained based on the stream identifier comprising the characteristics of the packet stream. The rules when obtained, to control traffic steering and / or distribution, are adapted to relate to which path to use and how to distribute the packets over different links along this path when forwarding the packets of the packet stream towards the second network node 132.

[0207] In some embodiments, the stream identifier is adapted to be comprised in any one out of: an IPv6 flow-label, an IPv6 Extension header, IPv6 SRv6 SID, SR-MPLS label, segment identifier SID, MPLS label and an IPv4 option header.

[0208] In some embodiments, a part of the packets of the identified packet stream is adapted to be encrypted. In these embodiments, the stream identifier is adapted to be located outside the encrypted part of the respective packet when marked. In this way, the stream identifier is visible to the respective first network node 131 , intermediate nodes 113, 114 and second network node 132 without performing decryption of the packets.

[0209] In some embodiments, when the transport network 102 is represented by a backhaul network, then the first network node 131 may e.g., be represented by a CN node 130 in the CN 106 of the communications network 100, and the second network node 132 may e.g., be represented by a RAN, node 111 in a RAN 104 of the communications network 100, or,

[0210] In some embodiments, when the transport network 102 is represented by a backhaul network, then the first network node 131 may e.g., be represented by RAN node 111 in a RAN 104 of the communications network 100 and the second network node 132 may e.g., be represented by the CN node 130 in the CN 106 of the communications network 100, and,

[0211] In some embodiments, when the transport network 102 is represented by a midhaul network, and the first network node 131 may e.g., be represented by a first RAN node 111 in a RAN 104 of the communications network 100, and the second network node 132 may e.g., be represented by a second RAN, node 112 in a RAN 104 of the communications network 100.

[0212] To perform the method actions above, the first intermediate node 113 is configured to handle packets of a packet stream in a communications network 100. The packet stream is adapted to be related to a transmission in a UE 121 data session from the first network node 131 towards the second network node 132, via the first intermediate node 113 and other intermediate nodes 114 in a transport network 102 of the communications network 100. The transport network 102 is adapted to comprise any one or more out of a backhaul network and midhaul network.

[0213] The first intermediate node 113 may comprise an arrangement depicted in Figure 17. The first intermediate node 113 may comprise an input and output interface 1700 configured to communicate in the communications network 100, e.g., with the first RAN node 111 , the second RAN node 112 and other intermediate nodes 114. The input and output interface 1700 may comprise a wireless receiver not shown, and a wireless transmitter not shown.

[0214] The first intermediate node 113 is further configured to receive packets of the packet stream. The respective packet of the packet stream is adapted to be marked with a stream identifier identifying the packet stream. The first intermediate node 113 is further configured to, based on the stream identifier, obtain rules related to forwarding the packets of the identified packet stream towards the second network node 132.

[0215] The first intermediate node 113 is further configured to, based on the obtained rules, control any one or more out of: traffic steering and distribution, of the packets comprised in the identified packet stream, when forwarding the marked packets in the packet stream towards the second network node 132.

[0216] In some embodiments, the stream identifier is adapted to indicate any one or more out of:

[0217] - a UE 121 data session ID of the packet stream,

[0218] - a backhaul tunnel ID related to the packet stream,

[0219] - a midhaul tunnel ID related to the packet stream, and

[0220] - a slice ID and / or slice service characteristics, when the data stream is related to network slicing.

[0221] In some embodiments, the distribution of the packets is adapted to be performed according to any one or more out of:

[0222] - across one or multiple links between the first intermediate node 113 and a RAN node 111 , 112,131 , 132,

[0223] - across one or multiple links between the first intermediate node 113 and a CN node 130, 131 , 132

[0224] - across one or multiple links between the first intermediate node 113 and another intermediate node 114 in the transport network 102, and

[0225] - over different alternative paths.

[0226] In some embodiments, the rules are adapted to be assigned to characteristics to be fulfilled for forwarding the respective packet in the identified packet stream. In some embodiments, the rules may be adapted to be obtained based on the stream identifier comprising characteristics of the packet stream. In these embodiments, the characteristics are adapted to comprise any one or more out of: the bitrate, delay, delay-variation, in-order delivery, of the RAN packet stream.

[0227] In some embodiments, the rules when obtained, to control traffic steering and / or distribution, are adapted to relate to which path to use and how to distribute the packets over different links along this path, when forwarding the packets of the RAN packet stream towards the second network node 132. In some embodiments, the stream identifier is adapted to be comprised in any one out of: an IPv6 flow-label, an IPv6 Extension header, IPv6 SRv6 SID, SR-MPLS label SID, MPLS label and an IPv4 option header.

[0228] In some embodiments, a part of the packets of the identified packet stream is adapted to be encrypted. In some of these embodiments, the stream identifier is adapted to be located outside the encrypted part of the respective packet when marked. In this way, the stream identifier is visible to the first intermediate node 113 without performing decryption of the packets.

[0229] In some embodiments, when the transport network 102 is represented by a backhaul network, then the first network node 131 may e.g., be represented by a CN node 130 in the CN 106 of the communications network 100, and the second network node 132 may e.g., be represented by a RAN, node 111 , 111 in a RAN 104 of the communications network 100, or,

[0230] In some embodiments, when the transport network 102 is represented by a backhaul network, then the first network node 131 may e.g., be represented by RAN node 111 , 112 in a RAN 104 of the communications network 100 and the second network node 132 may e.g., be represented by the CN node 130 in the CN 106 of the communications network 100, and,

[0231] In some embodiments, when the transport network 102 is represented by a midhaul network, and the first network node 131 may e.g., be represented by a first RAN node 111 in a RAN 104 of the communications network 100, and the second network node 132 may e.g., be represented by a second RAN, node 112 in a RAN 104 of the communications network 100.

[0232] To perform the method actions above, the second network node 132 is configured to handle packets of a packet stream in a communications network 100. The packet stream is adapted to be related to a transmission in a UE 121 data session from a first network node 131 towards the second network node 132, via intermediate nodes 113, 114 in a transport network 102 of the communications network 100. The transport network 102 is adapted to comprise any one or more out of a backhaul network and a midhaul network.

[0233] The second network node 132 may comprise an arrangement depicted in Figure 18. The second network node 132 may comprise an input and output interface 1800 configured to communicate in the communications network 100, e.g., with the intermediate nodes 113, 114 and a SAP. The input and output interface 1800 may comprise a wireless receiver not shown, and a wireless transmitter not shown. The second network node 132 is further configured to receive packets of the packet stream. The respective packet of the packet stream is adapted to be marked with a stream identifier identifying the packet stream.

[0234] The second network node 132 is further configured to, based on the identifier, obtain information about one or more SAPs and rules related to forward the packets of the packet stream to the one or more SAPs.

[0235] The second network node 132 is further configured to, based on the obtained information and rules, forward the packets in the identified packet stream to the one or more SAPs.

[0236] In some embodiments, the stream identifier is adapted to indicate any one or more out of:

[0237] - a UE 121 data session ID of the packet stream,

[0238] - a backhaul tunnel ID related to the packet stream,

[0239] - a midhaul tunnel ID related to the packet stream, and

[0240] - a slice identifier and / or slice service characteristics, when the data stream is related to network slicing.

[0241] In some embodiments, the stream identifier is adapted to be used for the traffic steering in any one or more out of:

[0242] - a RAN 104 of the communications network 100, and

[0243] - a CN 106 communications network 100.

[0244] In some embodiments, the distribution of the packets is adapted to be performed across one or multiple links between the second network node 132 and the one or more SAPs.

[0245] In some embodiments, the rules are adapted to be assigned to characteristics to be fulfilled for forwarding the respective packet in the identified packet stream.

[0246] In some embodiments, the rules are adapted to be obtained based on the stream identifier adapted to comprise characteristics of the packet stream. In these embodiments, characteristics comprise any one or more out of: the bitrate, delay, delay-variation, in-order delivery, of the packet stream.

[0247] In some embodiments, the rules when obtained, to control traffic steering and / or distribution, are adapted to relate to which path to use and how to distribute the packets over different links along this path, when forwarding the packets of the packet stream towards the SAPs. In some embodiments, the stream identifier is adapted to be comprised in any one out of: an IPv6 flow-label, an IPv6 Extension header, IPv6 segment routing, SRv6 SID, SR- MPLS label SID, MPLS label and an IPv4 option header.

[0248] In some embodiments, a part of the packets of the identified packet stream is adapted to be encrypted. In some of these embodiments, the stream identifier is adapted to be located outside the encrypted part of the respective packet when marked. In this way, the stream identifier is visible to the second network node 132 without performing decryption of the packets.

[0249] In some embodiments, when the transport network 102 is represented by a backhaul network, then the first network node 131 may e.g., be represented by a CN node 130 in the CN 106 of the communications network 100, and the second network node 132 may e.g., be represented by a RAN, node 111 , 112 in a RAN 104 of the communications network 100, or,

[0250] In some embodiments, when the transport network 102 is represented by a backhaul network, then the first network node 131 may e.g., be represented by RAN node 111 , 112 in a RAN 104 of the communications network 100 and the second network node 132 may e.g., be represented by the CN node 130 in the CN 106 of the communications network 100, and,

[0251] In some embodiments, when the transport network 102 is represented by a midhaul network, and the first network node 131 may e.g., be represented by a first RAN node 111 in a RAN 104 of the communications network 100, and the second network node 132 may e.g., be represented by a second RAN, node 112 in a RAN 104 of the communications network 100.

[0252] Embodiments herein may be implemented through a respective processor or one or more processors, such as the respective processor 1610 of a processing circuitry in the first network node 131 depicted in Figure 16, processor 1710 of a processing circuitry in the intermediate node 113 depicted in Figure 17, and processor 1810 of a processing circuitry in the second network node 132 depicted in Figure 18 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 respective first network node 131 , intermediate node 113 and second network node 132. 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 respective first network node 131 , intermediate node 113 and second network node 132.

[0253] The first network node 131 , intermediate node 113 and second network node 132 may further comprise a respective memory 1620, memory 1720 and memory 1820 comprising one or more memory units. The respective memory 1620, memory 1720 and memory 1820 comprises instructions executable by the processor in the respective first network node 131 , intermediate node 113 and second network node 132.

[0254] The respective memory 1620, memory 1720 and memory 1820 are arranged to be used to store e.g., media functions, indications, tags, information, data, configurations, communication data, and applications to perform the methods herein when being executed in the respective first network node 131 , intermediate node 113 and second network node 132.

[0255] In some embodiments, a respective computer program 1630, computer program 1730 and computer program 1830 comprises instructions, which when executed by the respective at least one processor 1610, processor 1710 and processor 1810, cause the at least one processor of respective first network node 131 , intermediate node 113 and second network node 132 to perform the actions above.

[0256] In some embodiments, a respective carrier 1640, carrier 1740 and carrier 1840 comprises the respective computer program 1630, computer program 1730 and computer program 1830, wherein the respective carrier 1640, carrier 1740 and carrier 1840 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.

[0257] Those skilled in the art will appreciate that units in the respective first network node 131 , intermediate node 113 and second network node 132 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 respective first network node 131 , intermediate node 113 and second network node 132, 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). ADDITIONAL EXPLANATION

[0258] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0259] Figure 19 shows an example of a communication system QQ100 in accordance with some embodiments.

[0260] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.

[0261] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O- CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1 , E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O- RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of user equipment, such as the UE 121 , QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

[0262] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0263] The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network QQ102.

[0264] In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (ALISF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0265] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0266] As a whole, the communication system QQ100 of Figure 19 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0267] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0268] In some examples, the UEs QQ112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e., being configured for multi-radio dual connectivity (MR- DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0269] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, fora UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0270] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and / or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node QQ110b. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0271] Figure 20 shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes such as e.g., first network node 131 , intermediate node 113 and second network node 132 and / or other UEs, such as e.g. UE 121. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB- loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0272] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0273] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 20. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0274] The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ202 may include multiple central processing units (CPUs).

[0275] In the example, the input / output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE QQ200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0276] In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied. The memory QQ210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[0277] The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.

[0278] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0279] In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11 , Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0280] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0281] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0282] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Figure 20.

[0283] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0284] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0285] Figure 21 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0286] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi- cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0287] The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300.

[0288] The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.

[0289] In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

[0290] The memory QQ304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

[0291] The communication interface QQ306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface QQ306 comprises port(s) / terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0292] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0293] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

[0294] The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0295] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0296] Embodiments of the network node QQ300 may include additional components beyond those shown in Figure 21 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.

[0297] Figure 22 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure 19, in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host QQ400 may provide one or more services to one or more UEs.

[0298] The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input / output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures QQ2 and QQ3, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

[0299] The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAG, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0300] Figure 23 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface. Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0301] Hardware QQ504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

[0302] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0303] In the context of NFV, a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[0304] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

[0305] Figure 24 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ112a of Figure 19 and / or UE QQ200 of Figure 20), network node (such as network node QQ110a of Figure 19 and / or network node QQ300 of Figure 21), and host (such as host QQ116 of Figure 19 and / or host QQ400 of Figure 22) discussed in the preceding paragraphs will now be described with reference to Figure 24.

[0306] Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650.

[0307] The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure 19) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0308] The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection QQ650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection QQ650.

[0309] The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0310] As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.

[0311] In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.

[0312] One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment. More precisely, the teachings of these embodiments may improve the latency and thereby provide benefits such as reduced user waiting time.

[0313] In an example scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0314] In some examples, 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 QQ650 between the host QQ602 and UE QQ606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and / or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 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 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.

[0315] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0316] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionalities may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0317] When using the word "comprise" or “comprising” it shall be interpreted as nonlimiting, i.e. , meaning "consist at least of".

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

Claims

CLAIMS1 . A method performed by a first network node (131) for handling packets of a packet stream in a communications network (100), which packet stream is related to a transmission in a User Equipment, UE, (121) data session from the first network node (131) towards a second network node (132), via intermediate nodes (113, 114) in a transport network (102) of the communications network (100), which transport network (102) comprises any one or more out of: a backhaul network and midhaul network, the method comprising: obtaining (402) a stream identifier identifying the packet stream based on characteristics of the packet stream, marking (403) the respective packet in the packet stream with the stream identifier, transmitting (405) the stream identifier marked packets of the packet stream towards the second network node (132), which stream identifier enables the respective first network node (131), second network node (132) and intermediate nodes (113, 114) to:- identify the packet stream and obtain rules related to forwarding the packets of the identified packet stream towards the second network node (132), and- based on the obtained rules, control traffic steering and / or distribution of the packets comprised in the identified packet stream, when forwarding the marked packets towards the second network node (132).

2. The method according to claim 1 , wherein the stream identifier indicates any one out of: a UE (121) data session Identifier, ID, of the packet stream, a backhaul tunnel ID related to the packet stream, a midhaul tunnel ID related to the packet stream, and a slice ID and / or slice service characteristics, when the data stream is related to network slicing.

3. The method according to any of the claims 1-2, wherein the stream identifier is used for the traffic steering in any one or more out of:- the transport network (102),- a Radio Access Network, RAN, (104) of the communications network (100), and- a Core Network, CN, (106) communications network (100).

4. The method according to any of the claims 1 -3, wherein the distribution of the packets is performed according to any one or more out of: across one or multiple links between any one or more out of Radio Access Network, RAN, Core Network, CN, and transport network nodes (111 , 112, 113, 114, 130, 131 , 132), across one or multiple links between intermediate nodes (113, 114,) in the transport network (102), and over different alternative paths.

5. The method according to any of the claims 1-4, wherein any one or more out of: the characteristics comprise any one or more out of: the bitrate, delay, delayvariation, in-order delivery, related to the packet stream, the rules are assigned to characteristics to be fulfilled for forwarding the respective packet in the identified packet stream, the rules are to be obtained based on the stream identifier comprising the characteristics of the packet stream, and when obtained, the rules to control traffic steering and / or distribution, relate to which path to use and how to distribute the packets over different links along this path when forwarding the packets of the packet stream towards the second network node (132), the stream identifier is comprised in any one out of: an Internet Protocol version 6, IPv6, flow-label, an IPv6 Extension header, Internet Protocol version 6, IPv6, segment routing, SRv6, segment identifier (SID), Segment Routing-Multi Protocol Label Switching, SR-MPLS, label, segment identifier (SID), Multi Protocol Label Switching, MPLS, label and an Internet Protocol version 4, IPv4, option header.

6. The method according to any of the claims 1-5, wherein a part of the packets of the identified packet stream is encrypted, and wherein the stream identifier is located outside the encrypted part of the respective packet when marked, to be visible to the respective first network node (131), intermediate nodes (113, 114) and second network node (132) without performing decryption of the packets.

7. The method according to any of the claims 1-6, wherein any one out of: the transport network (102) is represented by a backhaul network, and the first network node (131) is represented by a Core Network, CN, node (130) in a CN (106) of the communications network (100), and the second network node (132) is represented by a RAN, node (111 , 112) in a RAN (104) of the communications network (100), or, the transport network (102) is represented by a backhaul network, and the first network node (131) is represented by RAN node (111 , 112) in a RAN (104) of the communications network (100) and the second network node (132) is represented by a CN node (130) in a CN (106) of the communications network (100), and, the transport network (102) is represented by a midhaul network, and the first network node (131) is represented by a first RAN node (111) in a RAN (104) of the communications network (100), and the second network node (132) is represented by a second RAN node (112) in a RAN (104) of the communications network (100).

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

9. A carrier (1640) comprising the computer program (1630) of claim 8, wherein the carrier (1640) 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.

10. A method performed by a first intermediate node (113) for handling packets of a packet stream in a communications network (100), which packet stream is related to a transmission in a User Equipment, UE, (121) data session from a first network node (131) towards a second network node (132), via the first intermediate node (113) and other intermediate nodes (114) in a transport network (102) of the communications network (100), which transport network (102) comprises any one or more out of a backhaul network and midhaul network, the method comprising: receiving (501) packets of the packet stream, wherein the respective packet of the packet stream is marked with a stream identifier identifying the packet stream,based on the stream identifier, obtaining (502) rules related to forwarding the packets of the identified packet stream towards the second network node (132), and based on the obtained rules, controlling any one or more out of: traffic steering and distribution, of the packets comprised in the identified packet stream, when forwarding (503) the marked packets in the packet stream towards the second network node (132).

11. The method according to claim 10, wherein the stream identifier indicates any one or more out of: a UE (121) data session Identifier, ID, of the packet stream, a backhaul tunnel ID related to the packet stream, a midhaul tunnel ID related to the packet stream, and a slice ID and / or slice service characteristics, when the data stream is related to network slicing.

12. The method according to any of the claims 10-11 , wherein the distribution of the packets is performed according to any one or more out of: across one or multiple links between the first intermediate node (113) and a Radio Access Network, RAN, node (111 , 112,131 , 132), across one or multiple links between the first intermediate node (113) and a Core Network, CN, node (130, 131 , 132) across one or multiple links between the first intermediate node (113) and another intermediate node (114) in the transport network (102), and over different alternative paths.

13. The method according to any of the claims 10-12, wherein any one or more out of: the rules are assigned to characteristics to be fulfilled for forwarding the respective packet in the identified packet stream, the rules are obtained based on the stream identifier comprising characteristics of the packet stream, which characteristics comprises any one or more out of: the bitrate, delay, delay-variation, in-order delivery, of the RAN packet stream, and the rules when obtained, to control traffic steering and / or distribution, relate to which path to use and how to distribute the packets over different links along this path, when forwarding the packets of the RAN packet stream towards the second network node (132), andthe stream identifier is comprised in any one out of: an Internet Protocol version 6, IPv6, flow-label, an IPv6 Extension header, Internet Protocol version 6, IPv6, segment routing, SRv6, segment identifier (SID), Segment Routing-Multi Protocol Label Switching, SR-MPLS, label, segment identifier (SID), Multi Protocol Label Switching, MPLS, label and an Internet Protocol version 4, IPv4, option header.

14. The method according to any of the claims 10-13, wherein a part of the packets of the identified packet stream is encrypted, and wherein the stream identifier is located outside the encrypted part of the respective packet when marked, to be visible to the first intermediate node (113) without performing decryption of the packets.

15. The method according to any of the claims 10-14, wherein any one out of: the transport network (102) is represented by a backhaul network, and the first network node (131) is represented by a Core Network, CN, node (130) in a CN (106) of the communications network (100), and the second network node (132) is represented by a RAN, node (111 , 112) in a RAN (104) of the communications network (100), or, the transport network (102) is represented by a backhaul network, and the first network node (131) is represented by RAN node (111 , 112) in a RAN (104) of the communications network (100) and the second network node (132) is represented by a CN node (130) in a CN (106) of the communications network (100), and, the transport network (102) is represented by a midhaul network, and the first network node (131) is represented by a first RAN node (111) in a RAN (104) of the communications network (100), and the second network node (132) is represented by a second RAN, node (112) in a RAN (104) of the communications network (100).

16. A computer program (1730) comprising instructions, which when executed by a processor (1710), causes the processor (1710) to perform actions according to any of the claims 10-15.

17. A carrier (1740) comprising the computer program (1730) of claim 16, wherein the carrier (1740) 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.

18. A method performed by a second network node (132) for handling packets of a packet stream in a communications network (100), which packet stream is related to a transmission in a User Equipment, UE, (121) data session from a first network node(131) towards the second network node (132), via intermediate nodes (113, 114) in a transport network (102) of the communications network (100), which transport network (102) comprises any one or more out of a backhaul network and a midhaul network, the method comprising: receiving (601) packets of the packet stream, wherein the respective packet of the packet stream is marked with a stream identifier identifying the packet stream, based on the identifier, obtaining (602) information about one or more Service Access Points, SAPs, and rules related to forward the packets of the packet stream to the one or more SAPs, and based on the obtained information and rules, forwarding (603) the packets in the identified packet stream to the one or more SAPs.

19. The method according to claim 18, wherein the stream identifier indicates any one or more out of: a UE (121) data session Identifier, ID, of the packet stream, a backhaul tunnel ID related to the packet stream, a midhaul tunnel ID related to the packet stream, and a slice identifier and / or slice service characteristics when the data stream is related to network slicing.

20. The method according to any of the claims 18-19, wherein the stream identifier is used for the traffic steering in any one or more out of:- a Radio Access Network, RAN, (104) of the communications network (100), and- a Core Network, CN, (106) communications network (100).

21. The method according to any of the claims 18-20, wherein the distribution of the packets is performed across one or multiple links between the second network node(132) and the one or more SAPs.

22. The method according to any of the claims 18-21 , wherein any one or more out of:the rules are assigned to characteristics to be fulfilled for forwarding the respective packet in the identified packet stream, the rules are obtained based on the stream identifier comprising characteristics of the packet stream, which characteristics comprises any one or more out of: the bitrate, delay, delay-variation, in-order delivery, of the packet stream, and the rules when obtained, to control traffic steering and / or distribution, relate to which path to use and how to distribute the packets over different links along these paths, when forwarding the packets of the packet stream towards the SAPs, and the stream identifier is comprised in any one out of: an Internet Protocol version 6, IPv6, flow-label, an IPv6 Extension header, Internet Protocol version 6, IPv6, segment routing, SRv6, segment identifier (SID), Segment Routing-Multi Protocol Label Switching, SR-MPLS, label, segment identifier (SID), Multi Protocol Label Switching, MPLS, label and an Internet Protocol version 4, IPv4, option header.

23. The method according to any of the claims 18-22, wherein a part of the packets of the identified packet stream is encrypted, and wherein the stream identifier is located outside the encrypted part of the respective packet when marked, to be visible to the second network node (132) without performing decryption of the packets.

24. The method according to any of the claims 18-23, wherein any one out of: the transport network (102) is represented by a backhaul network, and the first network node (131) is represented by a Core Network, CN, node (130) in a CN (106) of the communications network (100), and the second network node (132) is represented by a RAN, node (111 , 112) in a RAN (104) of the communications network (100), or, the transport network (102) is represented by a backhaul network, and the first network node (131) is represented by RAN node (111 , 112) in a RAN (104) of the communications network (100) and the second network node (132) is represented by a CN node (130) in a CN (106) of the communications network (100), and, the transport network (102) is represented by a midhaul network, and the first network node (131) is represented by a first RAN node (111) in a RAN (104) of the communications network (100), and the second network node (132) is represented by a second RAN, node (112) in a RAN (104) of the communications network (100).

25. A computer program (1830) comprising instructions, which when executed by a processor (1810), causes the processor (1810) to perform actions according to any of the claims 18-24.

26. A carrier (1840) comprising the computer program (1830) of claim 28, wherein the carrier (1840) 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.

27. A first network node (131) configured to handle packets of a packet stream in a communications network (100), which packet stream is adapted to be related to a transmission in a User Equipment, UE, (121) data session from the first network node (131) towards a second network node (132), via intermediate nodes (113, 114) in a transport network (102) of the communications network (100), which transport network (102) is adapted to comprise any one or more out of: a backhaul network and midhaul network, the first network node (131) is further configured to: obtain a stream identifier identifying the packet stream based on characteristics of the packet stream, mark the respective packet in the packet stream with the stream identifier, transmit the stream identifier marked packets of the packet stream towards the second network node (132), which stream identifier is adapted to enable the respective first network node (131), second network node (132) and intermediate nodes (113, 114) to:- identify the packet stream and obtain rules related to forwarding the packets of the identified packet stream towards the second network node (132), and- based on the obtained rules, control traffic steering and / or distribution of the packets comprised in the identified packet stream, when forwarding the marked packets towards the second network node (132).

28. The first network node (131) according to claim 27, wherein the stream identifier is adapted to indicate any one out of: a UE (121) data session Identifier, ID, of the packet stream, a backhaul tunnel ID related to the packet stream, a midhaul tunnel ID related to the packet stream, anda slice ID and / or slice service characteristics, when the data stream is related to network slicing.

29. The first network node (131) according to any of the claims 27-28, wherein the stream identifier is adapted to be used for the traffic steering in any one or more out of:- the transport network (102),- a Radio Access Network, RAN, (104) of the communications network (100), and- a Core Network, CN, (106) communications network (100).

30. The first network node (131) according to any of the claims 27-29, wherein the distribution of the packets is adapted to be performed according to any one or more out of: across one or multiple links between any one or more out of Radio Access Network, RAN, Core Network, CN, and transport network nodes (111 , 112, 113, 114, 130, 131 , 132), across one or multiple links between intermediate nodes (113, 114,) in the transport network (102), and over different alternative paths.

31. The first network node (131) according to any of the claims 27-30, wherein any one or more out of: the characteristics are adapted to comprise any one or more out of: the bitrate, delay, delay-variation, in-order delivery, related to the packet stream, the rules are adapted to be assigned to characteristics to be fulfilled for forwarding the respective packet in the identified packet stream, the rules are adapted to be obtained based on the stream identifier comprising the characteristics of the packet stream, and when obtained, the rules to control traffic steering and / or distribution, are adapted to relate to which path to use and how to distribute the packets over different links along this path when forwarding the packets of the packet stream towards the second network node (132), the stream identifier is adapted to be comprised in any one out of: an Internet Protocol version 6, IPv6, flow-label, an IPv6 Extension header, Internet Protocol version 6, IPv6, segment routing, SRv6, segment identifier (SID), Segment Routing-Multi Protocol Label Switching, SR-MPLS, label, segment identifier (SID), Multi Protocol Label Switching, MPLS, label and an Internet Protocol version 4, IPv4, option header.

32. The first network node (131) according to any of the claims 27-31 , wherein a part of the packets of the identified packet stream is adapted to be encrypted, and wherein the stream identifier is adapted to be located outside the encrypted part of the respective packet when marked, to be visible to the respective first network node (131), intermediate nodes (113, 114) and second network node (132) without performing decryption of the packets.

33. The first network node (131) according to any of the claims 27-32, wherein any one out of: the transport network (102) is represented by a backhaul network, and the first network node (131) is represented by a Core Network, CN, node (130) in a CN (106) of the communications network (100), and the second network node (132) is represented by a RAN, node (111 , 112) in a RAN (104) of the communications network (100), or, the transport network (102) is represented by a backhaul network, and the first network node (131) is represented by RAN node (111 , 112) in a RAN (104) of the communications network (100) and the second network node (132) is represented by a CN node (130) in a CN (106) of the communications network (100), and, the transport network (102) is represented by a midhaul network, and the first network node (131) is represented by a first RAN node (111) in a RAN (104) of the communications network (100), and the second network node (132) is represented by a second RAN, node (112) in a RAN (104) of the communications network (100).

34. A first intermediate node (113) configured to handle packets of a packet stream in a communications network (100), which packet stream is adapted to be related to a transmission in a User Equipment, UE, (121) data session from a first network node (131) towards a second network node (132), via the first intermediate node (113) and other intermediate nodes (114) in a transport network (102) of the communications network (100), which transport network (102) is adapted to comprise any one or more out of a backhaul network and midhaul network, the first intermediate node (113) is further configured to:receive packets of the packet stream, wherein the respective packet of the packet stream is adapted to be marked with a stream identifier identifying the packet stream, based on the stream identifier, obtain rules related to forwarding the packets of the identified packet stream towards the second network node (132), and based on the obtained rules, control any one or more out of: traffic steering and distribution, of the packets comprised in the identified packet stream, when forwarding the marked packets in the packet stream towards the second network node (132).

35. The first intermediate node (113) according to claim 34, wherein the stream identifier is adapted to indicate any one or more out of: a UE (121) data session Identifier, ID, of the packet stream, a backhaul tunnel ID related to the packet stream, a midhaul tunnel ID related to the packet stream, and a slice ID and / or slice service characteristics, when the data stream is related to network slicing.

36. The first intermediate node (113) according to any of the claims 34-35, wherein the distribution of the packets is adapted to be performed according to any one or more out of: across one or multiple links between the first intermediate node (113) and a Radio Access Network, RAN, node (111 , 112,131 , 132), across one or multiple links between the first intermediate node (113) and a Core Network, CN, node (130, 131 , 132) across one or multiple links between the first intermediate node (113) and another intermediate node (114) in the transport network (102), and over different alternative paths.

37. The first intermediate node (113) according to any of the claims 34-36, wherein any one or more out of: the rules are adapted to be assigned to characteristics to be fulfilled for forwarding the respective packet in the identified packet stream, the rules are adapted to be obtained based on the stream identifier comprising characteristics of the packet stream, which characteristics is adapted to compriseany one or more out of: the bitrate, delay, delay-variation, in-order delivery, of the RAN packet stream, and the rules when obtained, to control traffic steering and / or distribution, is adapted to relate to which path to use and how to distribute the packets over different links along this path, when forwarding the packets of the RAN packet stream towards the second network node (132), and the stream identifier is adapted to be comprised in any one out of: an Internet Protocol version 6, IPv6, flow-label, an IPv6 Extension header, Internet Protocol version 6, IPv6, segment routing, SRv6, segment identifier (SID), Segment Routing- Multi Protocol Label Switching, SR-MPLS, label, segment identifier (SID), Multi Protocol Label Switching, MPLS, label and an Internet Protocol version 4, IPv4, option header.

38. The first intermediate node (113) according to any of the claims 34-37, wherein a part of the packets of the identified packet stream is adapted to be encrypted, and wherein the stream identifier is adapted to be located outside the encrypted part of the respective packet when marked, to be visible to the first intermediate node (113) without performing decryption of the packets.

39. The first intermediate node (113) according to any of the claims 34-38, wherein any one out of: the transport network (102) is represented by a backhaul network, and the first network node (131) is represented by a Core Network, CN, node (130) in a CN (106) of the communications network (100), and the second network node (132) is represented by a RAN, node (111 , 112) in a RAN (104) of the communications network (100), or, the transport network (102) is represented by a backhaul network, and the first network node (131) is represented by RAN node (111 , 112) in a RAN (104) of the communications network (100) and the second network node (132) is represented by a CN node (130) in a CN (106) of the communications network (100), and, the transport network (102) is represented by a midhaul network, and the first network node (131) is represented by a first RAN node (111) in a RAN (104) of the communications network (100), and the second network node (132) is represented by a second RAN, node (112) in a RAN (104) of the communications network (100).

40. A second network node (132) configured to handle packets of a packet stream in a communications network (100), which packet stream is adapted to be related to a transmission in a User Equipment, UE, (121) data session from a first network node (131) towards the second network node (132), via intermediate nodes (113, 114) in a transport network (102) of the communications network (100), which transport network (102) is adapted to comprise any one or more out of a backhaul network and a midhaul network, the second network node (132) is further configured to: receive packets of the packet stream, wherein the respective packet of the packet stream is adapted to be marked with a stream identifier identifying the packet stream, based on the identifier, obtain information about one or more Service Access Points, SAPs, and rules related to forward the packets of the packet stream to the one or more SAPs, and based on the obtained information and rules, forward the packets in the identified packet stream to the one or more SAPs.

41. The second network node (132) according to claim 40, wherein the stream identifier is adapted to indicate any one or more out of: a UE (121) data session Identifier, ID, of the packet stream, a backhaul tunnel ID related to the packet stream, a midhaul tunnel ID related to the packet stream, and a slice identifier and / or slice service characteristics, when the data stream is related to network slicing.

42. The second network node (132) according to any of the claims 40-41 , wherein the stream identifier is adapted to be used for the traffic steering in any one or more out of:- a Radio Access Network, RAN, (104) of the communications network (100), and- a Core Network, CN, (106) communications network (100).

43. The second network node (132) according to any of the claims 40-42, wherein the distribution of the packets is adapted to be performed across one or multiple links between the second network node (132) and the one or more SAPs.

44. The second network node (132) according to any of the claims 40-43, wherein any one or more out of: the rules are adapted to be assigned to characteristics to be fulfilled for forwarding the respective packet in the identified packet stream, the rules are adapted to be obtained based on the stream identifier adapted to comprise characteristics of the packet stream, which characteristics comprises any one or more out of: the bitrate, delay, delay-variation, in-order delivery, of the packet stream, and the rules when obtained, to control traffic steering and / or distribution, is adapted to relate to which path to use and how to distribute the packets over different links along this path, when forwarding the packets of the packet stream towards the SAPs, and the stream identifier is adapted to be comprised in any one out of: an Internet Protocol version 6, IPv6, flow-label, an IPv6 Extension header, Internet Protocol version 6, IPv6, segment routing, SRv6, segment identifier (SID), Segment Routing- Multi Protocol Label Switching, SR-MPLS, label, segment identifier (SID), Multi Protocol Label Switching, MPLS, label and an Internet Protocol version 4, IPv4, option header.

45. The second network node (132) according to any of the claims 40-44, wherein a part of the packets of the identified packet stream is adapted to be encrypted, and wherein the stream identifier is adapted to be located outside the encrypted part of the respective packet when marked, to be visible to the second network node (132) without performing decryption of the packets.

46. The second network node (132) according to any of the claims 40-45, wherein any one out of: the transport network (102) is represented by a backhaul network, and the first network node (131) is represented by a Core Network, CN, node (130) in a CN (106) of the communications network (100), and the second network node (132) is represented by a RAN, node (111 , 112) in a RAN (104) of the communications network (100), or, the transport network (102) is represented by a backhaul network, and the first network node (131) is represented by RAN node (111 , 112) in a RAN (104) of thecommunications network (100) and the second network node (132) is represented by a CN node (130) in a CN (106) of the communications network (100), and, the transport network (102) is represented by a midhaul network, and the first network node (131) is represented by a first RAN node (111) in a RAN (104) of the communications network (100), and the second network node (132) is represented by a second RAN, node (112) in a RAN (104) of the communications network (100).

Images