Radio acess network nodes, intermediate node and methods for handling packet streams in a ran transport network

Abstract

A method performed by a first Radio Access Network, RAN, node is provided. The method is for handling packets of a RAN packet stream from the first RAN node towards a second RAN node in a communications network. The RAN packet stream is to be transmitted in a data session via intermediate nodes in a RAN transport network of the communications network. The first RAN node obtains (402) a RAN identifier. The RAN identifier identifies the RAN packet stream based on characteristics of the RAN packet stream. The first RAN node marks (403) the packets of the RAN packet stream with the RAN identifier. The first RAN node then transmits (405) the RAN identifier marked RAN packets of the RAN packet stream towards the second RAN node. The RAN identifier enables the respective first RAN node and intermediate nodes to: Identify the RAN packet stream and obtain rules related to forwarding the packets of the RAN packet stream towards the second RAN node, and based on the obtained rules, control traffic steering and / or distribution of the packets comprised in the identified RAN packet stream, when forwarding the packets towards the second RAN node.

Description

[0001] RADIO ACESS NETWORK NODES, INTERMEDIATE NODE AND METHODS FOR HANDLING PACKET STREAMS IN A RAN TRANSPORT NETWORK

[0002] TECHNICAL FIELD

[0003] Embodiments herein relate to a first Radio Access Network (RAN) node, a first intermediate node, a second RAN node and methods therein. In some aspects, they relate to handling packets of a RAN packet stream from the first RAN node towards the second RAN node in a communications network, which RAN packet stream is to be transmitted in a data session via intermediate nodes in a RAN 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 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 Base Station, 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. A RAN Packet Transport network, also referred to as RAN transport network, is often described as the Fronthaul, Sidehaul and Midhaul domains. In a RAN Packet Transport network, there is often multiple simultaneous packet sessions ongoing between Medium Access Control (MAC) or Internet Protocol (IP) endpoints. MAC endpoints are e.g., related to ports and connections between or within RU, DU / vDU, CU / vCU IP endpoints. Most of those sessions comprise multiple RAN Packet Streams. A RAN Packet Stream when used herein e.g., means a stream of RAN packets. The RAN Packet Streams have various transport characteristics needs such as bitrate, delay, delay variation etc. The evolution of RAN Mobility services such as e.g., Ultra-Reliable Low Latency Communications (URLLC) and Network Reliability, Availability and Redundancy (NRAR) drives for e.g., resilience and low latency in the RAN Transport network. Therefore, RAN Packet Transport networks are evolving from simple direct links to more capable ring or meshed packet networks. Also new services like network slicing and evolved traffic principles like UE-Centric packet stream data drives for evolution of RAN Packet Transport handling.

[0011] In fronthaul, midhaul and sidehaul transport networks at the L2 data layer (ethernet) and L3 network layer (IP network), it is complicated for an intermediate node, such as a Switch / Router (SWR) to identify RAN Packet Streams. This results in a poor packet steering which in turn results in that some links or one or more paths may get overloaded while others may get underutilized. The problem will be described more in detail below.

[0012] SUMMARY

[0013] An object of embodiments herein is to improve the transmission of RAN packet streams in a communications network.

[0014] According to an aspect of embodiments herein, the object is achieved by a method performed by a first Radio Access Network (RAN) node. The method is for handling packets of a RAN packet stream from the first RAN node towards a second RAN node in a communications network. The RAN packet stream is to be transmitted in a data session via intermediate nodes in a RAN transport network of the communications network. The first RAN node obtains a RAN identifier. The RAN identifier identifies the RAN packet stream based on characteristics of the RAN packet stream. The first RAN node marks the packets of the RAN packet stream with the RAN identifier. The first RAN node then transmits the RAN identifier marked RAN packets of the RAN packet stream towards the second RAN node. The RAN identifier enables the respective first RAN node and intermediate nodes to: Identify the RAN packet stream and obtain rules related to forwarding the packets of the RAN packet stream towards the second RAN node, and based on the obtained rules, control traffic steering and / or distribution of the packets comprised in the identified RAN packet stream, when forwarding the packets towards the second RAN 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 a RAN packet stream from a first RAN node towards a second RAN node in a communications network. The RAN packet stream is to be transmitted in a data session via intermediate nodes comprising the first intermediate node in a RAN transport network of the communications network. The first intermediate node receives packets of a RAN packet stream. The respective packet of the RAN packet stream is marked with a RAN identifier identifying the RAN packet stream. Based on the RAN identifier, the first intermediate node obtains rules related to forwarding the packets of the RAN packet stream towards the second RAN node. Based on the obtained rules, the first intermediate node then controls any one or more out of traffic steering and distribution, of the packets comprised in the identified RAN packet stream, when forwarding the packets in the RAN packet stream towards the second RAN node.

[0016] According to an aspect of embodiments herein, the object is achieved by a method performed by a second RAN node. The method is for handling packets of a RAN packet stream from a first RAN node towards the second RAN node in a communications network. The RAN packet stream is transmitted in a data session via intermediate nodes in a RAN transport network of the communications network. The second RAN node receives packets of a RAN packet stream. The respective packet of the RAN packet stream is marked with a RAN identifier identifying the RAN packet stream. Based on the RAN identifier, the second RAN node obtains information about one or more Service Access Points, SAPs, and also rules related to forwarding the packets of the RAN packet stream to the one or more SAPs. Based on the obtained information and rules, the first intermediate node then forwards the packets in the RAN packet stream to the one or more SAPs. According to another aspect of embodiments herein, the object is achieved by a first RAN node. The first RAN node is configured to handle packets of a RAN packet stream from the first RAN node towards a second RAN node in a communications network. The RAN packet stream is adapted to be transmitted in a data session via intermediate nodes in a RAN transport network of the communications network. The first RAN node is further configured to obtain a RAN identifier identifying the RAN packet stream based on characteristics of the RAN packet stream. The first RAN node is configured to mark the packets of the RAN packet stream with the RAN identifier. The first RAN node is configured to transmit the RAN identifier marked RAN packets of the RAN packet stream towards the second RAN node. The RAN identifier is adapted to enable the respective first RAN node and intermediate nodes to: identify the RAN packet stream and obtain rules related to forwarding the packets of the RAN packet stream towards the second RAN node, and based on the obtained rules, control traffic steering and / or distribution of the packets comprised in the identified RAN packet stream, when forwarding the packets towards the second RAN node.

[0017] According to an aspect of embodiments herein, the object is achieved by a first intermediate node. The first intermediate node is configured to handle a RAN packet stream from a first RAN node towards a second RAN node in a communications network. The RAN packet stream is adapted to be transmitted in a data session via intermediate nodes comprising the first intermediate node in a RAN transport network of the communications network. The first intermediate node is further configured to receive packets of a RAN packet stream. The respective packet of the RAN packet stream is adapted to be marked with a RAN identifier identifying the RAN packet stream. The first intermediate node is configured to, based on the RAN identifier, obtain rules related to forwarding the packets of the RAN packet stream towards the second RAN node. The first intermediate node is 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 RAN packet stream, when forwarding the packets in the RAN packet stream towards the second RAN node. According to an aspect of embodiments herein, the object is achieved by a second RAN node. The second RAN node is configured to handle packets of a RAN packet stream from a first RAN node towards the second RAN node in a communications network. The RAN packet stream is adapted to be transmitted in a data session via intermediate nodes in a RAN transport network of the communications network. The second RAN node is further configured to receive packets of a RAN packet stream. The respective packet of the RAN packet stream is marked with a RAN identifier identifying the RAN packet stream. The second RAN node is configured to, based on the RAN identifier, obtain information about one or more SAPs and rules related to forwarding the packets of the RAN packet stream to the one or more SAPs. The second RAN node is configured to, based on the obtained information and rules, forward the packets in the RAN packet stream to the one or more SAPs.

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

[0019] BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0039] Figure 17 is a schematic block diagram illustrating embodiments of a first RAN node.

[0040] Figure 18 is a schematic block diagram illustrating embodiments of an intermediate node.

[0041] Figure 19 is a schematic block diagram illustrating embodiments of a second RAN node.

[0042] Figure 20 schematically illustrates embodiments of a communication system.

[0043] Figure 21 is a generalized block diagram of embodiments of a UE.

[0044] Figure 22 is a generalized block diagram of embodiments of a network node.

[0045] Figure 23 is a generalized block diagram of embodiments of a host.

[0046] Figure 24 is a generalized block diagram of embodiments of a virtualization environment.

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

[0048] DETAILED DESCRIPTION

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

[0050] In fronthaul, midhaul and sidehaul transport networks at L2 and L3, it is complicated for an intermediate node such as Switch / Router (SWR) to identify RAN packet streams due to reasons such as e.g., that RAN headers are located deep in or at different locations in the RAN packets making it difficult for the SWR to parse the headers and / or e.g., that the RAN header and data may be encrypted complicating the identification of RAN Packet Streams by the SWRs. In an Ethernet RAN Packet Transport with a single Link Aggregation Group (LAG) Source and Destination MAC (SMAC and DMAC) endpoint address or with just a few SMAC and DMAC endpoint addresses, there are too few known parameters such as e.g., MAC addresses for the RAN Packet Transport network to be able to control the distribution of RAN Packet Streams over different links between the SWRs. Similarly, in an IP RAN Packet Transport with a single LAG Source and Destination IP (S-IP and D-IP) endpoint address or just a few S-IP and D-IP endpoint addresses, there are too few known parameters such as IP addresses, Transmission Control Protocol (TCP) / User Datagram Protocol (UDP) ports for the RAN Packet Transport network to be able to control the distribution of RAN Packet Streams over different links between the SWRs. The existing technology to achieve RAN packet distribution within the RAN Packet Transport network is to calculate a hash on the RAN packet headers and use it to distribute the Packet Streams. However, with too few parameters to hash on, the distribution gets non optimal leading to e.g., elephant flows. The term elephant flow used herein means that some links or paths may get overloaded while others may get underutilized. Furthermore, the current technology does not allow for a controlled steering and distribution of RAN Packet Streams. Sometimes a Virtual LAN (VLAN) parameter is used as an identifier, but a VLAN is standardized as a logical interface and does not fit a use to identify individual packet streams. For instance, a VLAN identifier is a global parameter for a given area which means that it does not scale for many of the packet streams.

[0051] In an Ethernet RAN Packet Transport with a single SMAC and DMAC endpoint address or an IP RAN Packet Transport with a single S-IP and D-IP endpoint address, an SWR cannot perform traffic engineering and / or traffic distribution of the RAN Packet Streams due to complications in identification of the RAN Packet Streams as mentioned above. Traffic engineering also known as traffic steering when used herein, e.g., means steering packets and packet streams to a certain outgoing physical port / path, VLAN, VPNs such as e.g., IP -VPN, MPLS, and Segment Routing. Traffic distribution when used herein, e.g., means distribution of single or multiple packet streams over multiple links or paths. The non-optimal traffic handling of the RAN Packet Streams by the SWR results in non- optimal usage of links, paths, and network resources such as e.g., SWR equipment, links and paths. When end to end encryption is applied on the RAN packet streams, the RAN headers are not visible at ingress to RAN nodes and not at all to RAN Packet Transport networks equipment and thus they cannot identify the RAN Packet Streams and / or act on them. Therefore, the RAN nodes cannot do a first level of RAN Packet Stream steering internally towards RAN processing elements e.g., Multiple Service Access Points (SAP) without first performing decryption.

[0052] Figure 2 shows an example of today’s technology where identifiers (not shown) are used for identifying RAN Packet Streams in an Ethernet fronthaul, midhaul and sidehaul transport network. It depicts the use of multiple MAC endpoint addresses referred to as MAC A, MAC B and MAC C at one MAC endpoint and MAC 1, MAC 2 and MAC3, at the other MAC endpoint. In this example, VLAN identifiers are used to identify RAN packet streams. The limited number of MAC endpoint addresses available in the Ethernet RAN Packet Transport network also limits the identification of the RAN Packet Streams forcing the usage of multiple MAC endpoint addresses and VLAN identifiers, the VLAN identifiers have limited scalability in the RAN packet transport network. Similar technology and identifiers are used for identifying RAN Packets Streams in an IP fronthaul, midhaul and sidehaul transport networks with problems that are similar to the problems with Ethernet RAN Packet Transport as mentioned above.

[0053] Embodiments herein, e.g., relate to radio access network (RAN) controlled packet marking with a RAN Identifier, e.g., used for identifying individual RAN Packet Streams, and controlling distribution of RAN Packet Streams across multiple nodes and links between RAN nodes and intermediate nodes, e.g., transport entities. The RAN identifier is also referred to as a RAN identifier, a RAN packet stream identifier and an identifier.

[0054] Embodiments herein, e.g., provide any one or more out of:

[0055] - a controlled distribution of RAN Packet Streams across multiple links and nodes between first and second RAN node endpoints and intermediate nodes, also referred to as RAN Transport entities;

[0056] - a controlled traffic steering in the RAN transport network across multiple network paths between first and second RAN node endpoints;

[0057] - at a RAN node, perform a first level of RAN Packet Stream steering towards applicable processing element such as SAP without performing decryption; - a common format of RAN Packet Stream Identifier between L2 and L3 that enables mapping of the RAN identifier between L2 and L3 e.g., at UL / DL networking;

[0058] - identification of any of Multiprotocol Label Switching (MPLS), Label stack Segment routing with MPLS data plane (SR MPLS) and MPLS Label Switched Path (MPLS LSP)

[0059] - identification of an IPv6 Segment Routing path;

[0060] - a RAN Identifier identifying a RAN packet stream that may be used by nodes in RANs and RAN transport networks, in Fronthaul, Sidehaul, and / or Midhaul.

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

[0062] The RAN identifier will be visible in the nodes in the RAN transport network and at the second RAN node endpoint, even when encryption is applied on the RAN Packet Stream. The RAN identifier may e.g., be used to perform explicit traffic steering and distribution of packet streams both in RAN Transport and in RAN endpoints such as the first and second RAN nodes, by achieving characteristics needs for the respective RAN packet streams. This is an advantageous part in the RAN packet transport networks for new RAN capabilities and services such as Network Reliability, Availability and Resiliency (NRAR), slicing and also evolved RAN connection principles like a user equipment (UE)-Centric packet stream. Embodiments herein provide a more efficient utilization of the RAN transport network resources and lower an Operational Expenditure (OPEX) for the RAN packet transport network. OPEX when used herein refers to operation expenses for managing the RAN transport network but also includes the expenses for over dimensioning of the RAN transport network due to inefficient utilization of these resources.

[0063] Figure 3 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, and one or more CNs. The communications network 100 further comprises a RAN transport network 102, also referred to as a RAN packet transport network. A RAN transport network may e.g., comprise transport equipment, such as nodes, that connects the RAN equipment such as RAN nodes, e.g., RAN node endpoints. The transport equipment may comprise nodes, switches, routers, optical equipment, and / or wireless transport equipment such as microwave, fibres, or other applicable transport technologies. The communications network 100 may use 5G New Radio (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.

[0064] RAN nodes, such as a first RAN node 111 and a second RAN node 112, operate in the RAN in the communications network 100. The first RAN node 111 and the second RAN node 112, may be endpoints in an example scenario that will be described below. The first RAN node 111 may be referred to as a source endpoint and the second RAN node 112 may be referred to as a destination endpoint. The RAN nodes 111, 112, may each be a transmission and reception point e.g. a radio access network node such as a base station, e.g. a radio 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 RAN nodes 111, 112. The respective RAN nodes 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.

[0065] Intermediate nodes, such as a first intermediate node 113, and other intermediate nodes, referred to as intermediate nodes 114, operate in the RAN 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 RAN node 111 as being a source RAN node endpoint, between intermediate nodes 114 or next to the second RAN node 112 as being a target RAN 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-IoT 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 core network (CN) nodes in one or more CNs, with one or more SAPs, e.g., operating in a cloud 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.

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

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

[0068] A method according to embodiments herein will be described in a general way as seen from the view of the first RAN node 111 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 112 together with Figure 6. This will be followed by a more detailed description with implementing examples of the method.

[0069] Figure 4 shows examples of embodiments of a method performed by the first RAN node 111. The method is for handling packets of a RAN packet stream from the first RAN node 111 towards the second RAN node 112 in the communications network 100.

[0070] The RAN packet stream is to be transmitted in a data session via the intermediate nodes 113, 114 in the RAN transport network 102 of the communications network 100.

[0071] The RAN packet stream may e.g., be related to any one out of an Ethernet domain, an Internet Protocol (IP) version 4 (IPv4) domain and an IP version 6 (IPv6) domain or any similar domain. This e.g., means that the packets may be sent over a plain Ethernet network, an Ethernet network utilizing VLANs, a Multi Protocol Label Switching (MPLS) network, an IPv4 network, an IPv4 network utilizing L3VPN, an IPv6 network, an IPv6 network utilizing L3VPN, an MPLS segment routing network, and a IPv6 Segment routing network.

[0072] 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.

[0073] In an example scenario, the first RAN node 111 receives packets, e.g., from an originating SAP, which are to be sent in the RAN transport network 102 via chain of nodes comprising the first RAN node 111 and the intermediate nodes 113, 114 towards the second RAN node 122. 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 RAN identifier will be used that is visible to the nodes in the chain.

[0074] Action 401.

[0075] The first RAN node 111 may receive from an originating SAP, packets to be sent in the RAN packet stream from the first RAN node 111 towards the second RAN node 112.

[0076] Action 402.

[0077] The first RAN node 111 obtains a RAN identifier identifying the RAN packet stream based on characteristics of the RAN 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.

[0078] In some embodiments, the characteristics of the RAN stream may comprise any one or more out of: the bitrate, delay, delay-variation, in-order delivery, related to the RAN packet stream. This e.g., means that these characteristics define which RAN identifier to select among a number of selectable RAN identifiers. The RAN identifier may e.g., be represented by any one out of: an Ethernet tag, an IPv6 flow-label, an IPv6 Extension header, an IPv4 option header, an UDP port, or a specific part of an Antenna-Carrier (eAxC)-Identity (ID) field.

[0079] The RAN identifier may comprise information on one or more of

[0080] - RAN packet flow type;

[0081] - one or more network slicing parameters;

[0082] - telemetry parameter.

[0083] In case of fronthaul transport domain, the information on the RAN packet flow type may comprise information on evolved Common Public Radio Interface (eCPRI) traffic flows and / or information on RAN eAxC-ID flows. Examples of information on eCPRI traffic flows are packet / flow direction, e.g., uplink or downlink, delay measurements, priority of scheduling allocation carried within these packets, type of air interface channel, power measurements, network services (such as Ultra-Reliable Low Latency Communications (URLLC)), and packet / flow type. Examples of packet / flow types are control plane, user plane, synchronization plane, and management plane. The information on eCPRI traffic flows may allow to identify, classify, steer and / or distribute (e.g., ORAN) eCPRI Fronthaul traffic flows. For example, the traffic flows may be classified based on packet / flow type, network slicing, direction (UL / DL), band, class-of-service (CoS), and / or Quality of Service (QoS).

[0084] The information on RAN eAxC-ID flows may comprise ORAN eAxC-id fields, such as Component Carrier (CC ID), BandSector lD, RU-port-ID, and / or DU-port-ID.

[0085] The information on one or more network slicing parameters may comprise service type, service differentiator, e.g., S-NSSAI, and / or UE flow in a network slice.

[0086] The information on the telemetry parameter comprises an indication to enable or to not enable telemetry on the related RAN flow. If the telemetry is enabled in e.g., the first RAN node 111, then nodes on the path (e.g., first RAN node 111, intermediate nodes 113, 114, and / or second RAN node 112) will record telemetry information, such as packet drop rate, burst bitrate, average bitrate, delay measurement, and (periodically) send the telemetry information to Operation and Maintenance (O&M) systems for example for maintenance purposes. In case of sidehaul transport domain, the information on the RAN packet flow type may comprise information on packet / flow type. Examples of packet / flow types are

[0087] - control plane, i.e., control plane traffic between control processes;

[0088] - data plane, i.e., actual data sent between RAN entities;

[0089] - management plane, i.e., signaling for configuration and maintenance of the RAN entities;

[0090] - delay measurement, i.e., delay measurement of flows between RAN entities.

[0091] The information on one or more network slicing parameters may comprise service type, service differentiator, e.g., S-NSSAI, and / or UE flow in a network slice.

[0092] The information on the telemetry parameter comprises an indication to enable or to not enable telemetry on the related RAN flow. If the telemetry is enabled in e.g., the first RAN node 111, then nodes on the path (e.g., first RAN node 111, intermediate nodes 113, 114, and / or second RAN node 112) will record telemetry information, such as packet drop rate, burst bitrate, average bitrate, delay measurement, and (periodically) send the telemetry information to O&M systems for example for maintenance purposes.

[0093] The parameters comprised in the RAN identifier are set by RAN equipment and may be configured statically or dynamically (manual / automated / intent-based configuration).

[0094] The RAN identifier may allow for:

[0095] - flexible configuration of partitioning and size of the different fields in the flow label, compatible with the Fronthaul or Sidehaul network. The configuration may be performed / negotiated over ORAN management plane between the endpoints (open distributed unit (O-DU) and open radio unit (O-RU)) and / or over any transport protocol that offers Flow Aware Transport (FAT):

[0096] - masking of delay measurement indicator and telemetry indicator from QoS and load balancing decision, such that they are only used by intermediate routers and switches;

[0097] - traffic identification without decoding the complete eCPRI message or before decryption is done.

[0098] Action 403.

[0099] The first RAN node 111 marks the packets of the RAN packet stream with the RAN identifier. Different examples will be described more in detail below. In some embodiments, the packets of the RAN 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 other embodiments, a part of the respective packet of the RAN packet stream is 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 perspectives confidentiality, integrity, and authentication. In some of these embodiments, the RAN identifier is located outside the encrypted part of the respective packet when marked. In this way the RAN identifier is visible to the respective first RAN node 111, intermediate nodes 113, 114 and second RAN node 112 without performing decryption of the packets.

[0100] Action 404.

[0101] The first RAN node 111 may in some embodiments obtain rules related to forwarding the packets of the RAN packet stream towards the second RAN node 112 based on the RAN identifier. This may for example be performed by using the RAN identifier as input when looking up associated forwarding rules in a forwarding policy table.

[0102] Action 405.

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

[0104] The RAN packet stream from the first RAN node 111 towards a second RAN node 112 may be transmitted from a source endpoint of the first RAN node 111 towards one or more destination endpoints of the second RAN node 112.

[0105] The RAN identifier enables the respective first RAN node 111 and intermediate nodes

[0106] 113, 114 to: - identify the RAN packet stream and obtain rules related to forwarding the packets of the RAN packet stream towards the second RAN node 112, and

[0107] - based on the obtained rules, control traffic steering and / or distribution of the packets comprised in the identified RAN packet stream, when forwarding the packets towards the second RAN node 112.

[0108] As mentioned above in Action 404, in some embodiments the first RAN node 111 has obtained rules related to transmitting the packets of the RAN packet stream towards the second RAN node 112. In these embodiments, the first RAN node 111 may control traffic steering and / or distribution of the packets comprised in the identified RAN packet stream, when transmitting the packets in the RAN packet stream towards the second RAN node 112.

[0109] The rules may be assigned to characteristics required to achieve for forwarding the respective packet in the identified packet stream. A rule when used herein may 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 one or more physical or logical links. 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 done with only the identifier or together with other transport information such as MAC-address, VLAN, IP- header. The rules may relate to requirements, e.g. a required characteristic, on e.g., bitrate, delay, delay-variation, in-order delivery, related to the RAN packet stream. E.g. a required bitrate.

[0110] In some embodiments, the RAN identifier comprises information about the characteristics. In these embodiments, the rules are to be obtained based on the RAN identifier comprising the characteristics of the RAN 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 RAN packet stream towards the second RAN node 112.

[0112] The distribution of the packets comprised in the identified RAN packet stream when forwarding the packets towards the second RAN node 112 may e.g., be performed over different alternative paths. Regarding the control of the traffic steering and / or distribution of the RAN packet stream based on the obtained rules, the RAN node 111 may e.g., select the path and / or different links using different technology. 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 utilization.

[0113] In this way, by performing the above method, with the RAN identifier visible by the intermediate nodes 113, 114 in the RAN transport network 102 and at the second RAN node 112, even when encryption is applied on the RAN Packet Stream. The RAN identifier may e.g., be used to perform explicit traffic steering and distribution of packet streams both in RAN transport network and in RAN endpoints such as the first and second RAN nodes 111, 112, by achieving characteristics needs for the respective RAN packet streams.

[0114] Figure 5 shows examples of embodiments of a method performed by the first intermediate node 113 for handling a RAN packet stream from the first RAN node 111 towards the second RAN node 112 in the communications network 100. The RAN packet stream is to be transmitted in a data session via intermediate nodes 113, 114 comprising the first intermediate node 113, in the RAN transport network 102 of the communications network 100. In some embodiments, the RAN packet stream may e.g., be related to any one out of: an Ethernet domain, an IPv4 domain, and an IPv6 domain, or any similar domain.

[0115] 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 5.

[0116] According to the example scenario, the first intermediate node 113 receives packets marked with the RAN identifier from e.g., the first RAN node 111 or another of the intermediate nodes 114. The packets are to be sent in the RAN transport network 102 via chain of nodes comprising the first RAN node 111 and the intermediate nodes 113, 114 towards the second RAN node 112. The first intermediate node 113 uses the RAN 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 RAN node 112. Action 501.

[0117] The first intermediate node 113 receives packets of a RAN packet stream e.g., from the first RAN node 111 or another of the intermediate nodes 114. The respective packet of the RAN packet stream is marked with a RAN identifier identifying the RAN packet stream. The RAN identifier may e.g., be represented by any one out of an Ethernet tag, an IPv6 flowlabel, an IPv6 Extension header, an IPv4 option header, a UDP port, or a specific part of an eAxC-ID field, or an MPLS label.

[0118] The RAN identifier may e.g., be represented by any one out of an Ethernet tag, an IPv6 flow-label, an IPv6 Extension header, an IPv4 option header, an UDP port, or a specific part of an eAxC-ID field.

[0119] The RAN identifier may comprise information on one or more of

[0120] - RAN packet flow type;

[0121] - one or more network slicing parameters;

[0122] - telemetry parameter.

[0123] In case of fronthaul transport domain, the information on the RAN packet flow type may comprise information on eCPRI traffic flows and / or information on RAN eAxC-ID flows. Examples of information on eCPRI traffic flows are packet / flow direction, e.g., uplink or downlink, delay measurements, priority of scheduling allocation carried within these packets, type of air interface channel, power measurements, network services (such as URLLC), and packet / flow type. Examples of packet / flow types are control plane, user plane, synchronization plane, and management plane. The information on eCPRI traffic flows may allow to identify, classify, steer and / or distribute (e.g., ORAN) eCPRI Fronthaul traffic flows. For example, the traffic flows may be classified based on packet / flow type, network slicing, direction (UL / DL), band, CoS, and / or QoS.

[0124] The information on RAN eAxC-ID flows may comprise ORAN eAxC-id fields, such as CC ID, BandSector lD, RU-port-ID, and / or DU-port-ID.

[0125] The information on one or more network slicing parameters may comprise service type, service differentiator, e.g., S-NSSAI, and / or UE flow in a network slice. The information on the telemetry parameter comprises an indication to enable or to not enable telemetry on the related RAN flow. If the telemetry is enabled in e.g., the first RAN node 111, then nodes on the path (e.g., first RAN node 111, intermediate nodes 113, 114, and / or second RAN node 112) will record telemetry information, such as packet drop rate, burst bitrate, average bitrate, delay measurement, and (periodically) send the telemetry information to O&M systems for example for maintenance purposes.

[0126] In case of sidehaul transport domain, the information on the RAN packet flow type may comprise information on packet / flow type. Examples of packet / flow types are

[0127] - control plane, i.e., control plane traffic between control processes;

[0128] - data plane, i.e., actual data sent between RAN entities;

[0129] - management plane, i.e., signaling for configuration and maintenance of the RAN entities;

[0130] - delay measurement, i.e., delay measurement of flows between RAN entities.

[0131] The information on one or more network slicing parameters may comprise service type, service differentiator, e.g., S-NSSAI, and / or UE flow in a network slice.

[0132] The information on the telemetry parameter comprises an indication to enable or to not enable telemetry on the related RAN flow. If the telemetry is enabled in e.g., the first RAN node 111, then nodes on the path (e.g., first RAN node 111, intermediate nodes 113, 114, and / or second RAN node 112) will record telemetry information, such as packet drop rate, burst bitrate, average bitrate, delay measurement, and (periodically) send the telemetry information to O&M systems for example for maintenance purposes.

[0133] The parameters comprised in the RAN identifier are set by RAN equipment and may be configured statically or dynamically (manual / automated / intent-based configuration).

[0134] The RAN identifier may allow for:

[0135] - flexible configuration of partitioning and size of the different fields in the flow label, compatible with the Fronthaul or Sidehaul network. The configuration may be performed / negotiated over ORAN management plane between the endpoints (O-DU and O- RU) and / or over any transport protocol that offers FAT:

[0136] - masking of delay measurement indicator and telemetry indicator from QoS and load balancing decision, such that they are only used by intermediate routers and switches; - traffic identification without decoding the complete eCPRI message or before decryption is done.

[0137] In some embodiments, the packets of the RAN packet stream are not encrypted. In some other embodiments, a part of the respective packet of the RAN packet stream are encrypted. In some of these embodiments, the RAN identifier is located outside the encrypted part of the respective packet when marked. In this way, the RAN identifier is visible to the respective intermediate nodes 113, 114 and second RAN node 112 without performing decryption of the packets.

[0138] Action 502.

[0139] Based on the RAN identifier, the first intermediate node 113 obtains rules related to forwarding the packets of the RAN packet stream towards the second RAN node 112. 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. The rules may be assigned to characteristics required to achieve for forwarding the respective packet in the identified packet stream. In some embodiments, the rules are obtained based on the RAN identifier comprising characteristics of the RAN packet stream. In these embodiments, the characteristics may e.g., 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 RAN identifier the first RAN node 111 has selected among a number of selectable RAN identifiers. The chosen RAN identifier marking the packets then e.g., defines which rules the first intermediate node 113 shall select for forwarding the packets further in the RAN transport network 102.

[0140] 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 RAN node 111 or one of the other intermediate nodes 114.

[0141] If the intermediate node 113 has received the packets directly from the first RAN node 111 or directly from one of the other intermediate nodes 114 and is not the last intermediate node before the receiving RAN node 112, the obtained rules may define the use of transport technologies e.g., VLAN, MPLS, Policy Routing, Segment Routing, for the packet stream. 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 RAN node 112, the obtained rules may determine to terminate the used transport technology used in previous intermediate nodes.

[0142] Action 503.

[0143] 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 RAN packet stream, when forwarding the packets in the RAN packet stream towards the second RAN node 112. As mentioned in Action 502, the first intermediate node 113 has obtained from the RAN identifier, the rules related to forwarding the packets of the RAN packet stream towards the second RAN node 112. The first intermediate node 113 then by means of the obtained information controls and / or distributes the forwarding of the RAN packets to a next intermediate node 114 in the RAN transport network 102 chain or to the second RAN node 112 if that node is the next node in the chain.

[0144] 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 RAN node 112.

[0145] 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.

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

[0147] 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 RAN packet stream towards the second RAN node 112. The distribution of the packets comprised in the identified RAN packet stream, when forwarding the packets towards the second RAN node 112 may e.g., be performed over different alternative paths. In some embodiments, the identified RAN 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.

[0148] Regarding the control of the traffic steering and / or distribution of the RAN 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.

[0149] In this way, by performing the above method, the intermediate node 113 uses the visibility of the RAN identifier to perform explicit traffic steering and distribution of packet streams in the RAN transport network 102 e.g., to the next intermediate node 114 or to the second RAN node 112, by achieving characteristics needs for the respective RAN packet streams even when encryption is applied.

[0150] Figure 6 shows examples of embodiments of a method performed by the second RAN node 112 for handling packets of a RAN packet stream from the first RAN node 111 towards the second RAN node 112 in the communications network 100. The RAN packet stream is transmitted in a data session via intermediate nodes 113, 114 in the RAN transport network 102 of the communications network 100. In some embodiments, the RAN packet stream may e.g., be related to any one out of an Ethernet domain, an IPv4 domain and IPv6 domain, or any similar domain.

[0151] 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 6.

[0152] According to the example scenario, the second RAN node 112 receives packets marked with the RAN identifier from e.g., any of the intermediate nodes 113, 114. The marked packets have been sent in the RAN transport network 102 via a chain of nodes comprising the first RAN node 111 and the intermediate nodes 113, 114 towards the second RAN node 112. The second RAN node 112 uses the RAN 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. Action 601.

[0153] The second RAN node 112 receives packets of a RAN packet stream. The respective packet of the RAN packet stream is marked with a RAN identifier identifying the RAN packet stream. The RAN identifier may e.g., be represented by any one out of: an Ethernet tag, an IPv6 flow-label, an IPv6 Extension header, an IPv4 option header, a UDP port, or a specific part of an eAxC-ID field.

[0154] The RAN identifier may e.g., be represented by any one out of: an Ethernet tag, an IPv6 flow-label, an IPv6 Extension header, an IPv4 option header, an UDP port, or a specific part of an eAxC-ID field.

[0155] The RAN identifier may comprise information on one or more of

[0156] - RAN packet flow type;

[0157] - one or more network slicing parameters;

[0158] - telemetry parameter.

[0159] In case of fronthaul transport domain, the information on the RAN packet flow type may comprise information on eCPRI traffic flows and / or information on RAN eAxC-ID flows. Examples of information on eCPRI traffic flows are packet / flow direction, e.g., uplink or downlink, delay measurements, priority of scheduling allocation carried within these packets, type of air interface channel, power measurements, network services (such as URLLC), and packet / flow type. Examples of packet / flow types are control plane, user plane, synchronization plane, and management plane. The information on eCPRI traffic flows may allow to identify, classify, steer and / or distribute (e.g., ORAN) eCPRI Fronthaul traffic flows. For example, the traffic flows may be classified based on packet / flow type, network slicing, direction (UL / DL), band, CoS, and / or QoS.

[0160] The information on RAN eAxC-ID flows may comprise ORAN eAxC-id fields, such as CC ID, BandSector lD, RU-port-ID, and / or DU-port-ID.

[0161] The information on one or more network slicing parameters may comprise service type, service differentiator, e.g., S-NSSAI, and / or UE flow in a network slice.

[0162] The information on the telemetry parameter comprises an indication to enable or to not enable telemetry on the related RAN flow. If the telemetry is enabled in e.g., the first RAN node 111, then nodes on the path (e.g., first RAN node 111, intermediate nodes 113, 114, and / or second RAN node 112) will record telemetry information, such as packet drop rate, burst bitrate, average bitrate, delay measurement, and (periodically) send the telemetry information to O&M systems for example for maintenance purposes.

[0163] In case of sidehaul transport domain, the information on the RAN packet flow type may comprise information on packet / flow type. Examples of packet / flow types are

[0164] - control plane, i.e., control plane traffic between control processes;

[0165] - data plane, i.e., actual data sent between RAN entities;

[0166] - management plane, i.e., signaling for configuration and maintenance of the RAN entities;

[0167] - delay measurement, i.e., delay measurement of flows between RAN entities.

[0168] The information on one or more network slicing parameters may comprise service type, service differentiator, e.g., S-NSSAI, and / or UE flow in a network slice.

[0169] The information on the telemetry parameter comprises an indication to enable or to not enable telemetry on the related RAN flow. If the telemetry is enabled in e.g., the first RAN node 111, then nodes on the path (e.g., first RAN node 111, intermediate nodes 113, 114, and / or second RAN node 112) will record telemetry information, such as packet drop rate, burst bitrate, average bitrate, delay measurement, and (periodically) send the telemetry information to O&M systems for example for maintenance purposes.

[0170] The parameters comprised in the RAN identifier are set by RAN equipment and may be configured statically or dynamically (manual / automated / intent-based configuration).

[0171] The RAN identifier may allow for:

[0172] - flexible configuration of partitioning and size of the different fields in the flow label, compatible with the Fronthaul or Sidehaul network. The configuration may be performed / negotiated over ORAN management plane between the endpoints (O-DU and O- RU) and / or over any transport protocol that offers FAT:

[0173] - masking of delay measurement indicator and telemetry indicator from QoS and load balancing decision, such that they are only used by intermediate routers and switches;

[0174] - traffic identification without decoding the complete eCPRI message or before decryption is done. In some embodiments, the packets of the RAN packet stream are not encrypted. In some other embodiments, a part of the respective packet of the RAN packet stream are encrypted. In some of these embodiments, the RAN identifier is located outside the encrypted part of the respective packet when marked. This is to be visible to the second RAN node 112 without performing decryption of the packets.

[0175] Action 602.

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

[0177] Action 603.

[0178] The second RAN node 112, based on the obtained information and rules, forwards the packets in the RAN packet stream to the one or more SAPs. As mentioned in Action 602, the second RAN node 112 has obtained from the RAN identifier the rules related to forwarding the packets of the RAN packet stream to the one or more SAPs. The second RAN node 112 then by means of the obtained information control and / or distribute forwarding of the RAN packets to the one or more SAPs. 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 RAN packet stream to the one or more SAPs. Regarding the control of the traffic steering and / or distribution of the RAN packet stream based on the obtained rules, the second RAN node 112 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, load-balancing 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.

[0179] The RAN packet stream from the first RAN node 111 towards a second RAN node 112 may be transmitted from the source endpoint of the first RAN node 111 towards one or more destination endpoints of the second RAN node 112. In some embodiments, the RAN packet stream may be transmitted from an originating SAP in the first RAN node 111 towards a destination SAP in the second RAN node 112.

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

[0181] 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.

[0182] As mentioned above, the RAN identifier is used between RAN entities such as the intermediate nodes 113, 114 between the first and second RAN nodes 111, 112, to identify individual RAN packet streams. The RAN packet stream identifier is visible to both the intermediate nodes 113, 114 and the first and second RAN nodes 111, 112, even when encryption is applied. The RAN identifier is used for handling the identified RAN packet streams in the intermediate nodes 113, 114 in the RAN transport network 102 as well as within first and second RAN nodes 111, 112.

[0183] As also mentioned above, the RAN identifier will be used to identify the RAN packet streams. The RAN packet streams to be identified may be related to multiple or single endpoint addresses. To come along with the evolution of RAN Packet Networks, such as e.g., fronthaul, midhaul, and sidehaul networks, towards more advanced transport topologies, the RAN identifier according to some embodiments herein enables a way to simplify and / or scale RAN endpoints by deploying single transport endpoint addresses. This may be possible since by creating a single transport endpoint address, even when multiple physical ports are used on RAN nodes, it may, behind the single transport address, encompass multiple RAN SAP endpoint addresses, and use the identifier to identify a rule that in turn identify a SAP endpoint address.

[0184] As mentioned above, a RAN transport network has several external transport domains. The RAN transport network according to embodiments herein may e.g., relate to any one or more out of a fronthaul domain, a midhaul domain, a sidehaul domain and a backhaul domain.

[0185] Identifying a RAN packet stream related to Ethernet

[0186] Deploying a single endpoint transport address, may e.g., be performed by e.g., using a Link Aggregation (LAG) MAC address covering all the physical ports, that encompass multiple RAN SAP end-point addresses. This is shown in Figure 7 depicting an example of the embodiments implemented in Ethernet, to be compared with Figure 2 depicting prior art. The difference provided by the embodiment in Figure 7 compared to prior art in Figure 2 is that they use single transport end-point addresses for the transmission of the RAN packet streams, a single LAG MAC X address in the first RAN node 111 and a single LAG MAC Y address in the second RAN node 112. Figure 7 illustrates the transport of packets of the RAN packet streams from the first RAN node 111 towards the second RAN node 112 via the RAN transport network 102. The RAN identifier is used to identify these RAN packet streams.

[0187] As mentioned above, besides the provided scaling to single end-point addresses in some embodiments, a controlled and explicit RAN Packet Stream steering onto path between first RAN node 111 and second RAN node 112 and / or distribution over multiple links between the RAN node 111 and an intermediate node 113, 114. Also multiple links between intermediate nodes in the RAN transport network is provided by some embodiments herein. E.g., to perform explicit steering of the RAN Packet Streams over alternative paths in the RAN transport network 102 and / or distribute them over multiple links between neighbouring nodes in the RAN transport network 102. The RAN Identifier is used to identify the RAN Packet Streams to be steered and / or distributed. This may be performed by reading the identifier in the received packet of the RAN packet stream, then based on the identifier obtaining rule for identification of the RAN packet stream and handling of the RAN packet stream.

[0188] Implementing the RAN identifier in a header of an Ethernet frame

[0189] As mentioned above, a RAN identifier according to embodiments herein, will be used to identify RAN Packet Streams to be enabled to perform the RAN Packet Stream handling needed for coming along with the evolution of RAN Packet Networks, such as e.g., fronthaul, midhaul, and sidehaul networks, towards more advanced transport topologies.

[0190] For embodiments related to Ethernet, the RAN identifier may be represented by, also referred to as implemented as, a specific tag in an Ethernet header of an Ethernet frame. The specific tag may be assigned with a new EtherType. An EtherType is a two-octet field in an Ethernet frame. It is used to indicate which protocol is encapsulated in the payload of the frame. A new EtherType value related to the RAN identifier may be assigned by the Electrical and Electronics Engineers (IEEE) registration authority. The indicated value of the RAN identifier i.e., the tag may preferably be unique only per session, the session may be the pair of a Source MAC and a Destination MAC address of the RAN end points such as the first and second RAN nodes 111, 112. Alternatively, if VLANs are used the session may be the Source MAC and a Destination MAC address of the RAN end points, such as the first and second RAN nodes 111, 112, within the specific VLAN. Thus, RAN packet streams in sessions within Ethernet Networks will be associated with the RAN identifier for identifying the RAN packet stream. This gives a good scaling of the RAN Packet Stream Identifier value.

[0191] By means of the RAN identifier it may be possible to perform a first level of RAN Packet Stream steering within the second RAN node 112, towards applicable one or more SAPs in or associated with the second RAN node 112, without first having to perform decryption. A SAP may also be a security processing entity in itself, which then may be identified and steered towards. For L3, an additional possibility is to use a source UDP to identify the stream per Source IP & Dest IP / UDP.

[0192] An example of the RAN identifier when represented by a specific tag in an Ethernet header, is referred to as Stream Identifier when depicted in Figure 8. The RAN identifier may also be referred to as a RAN Packet Stream Identifier TAG and may be a related new EtherType in a general Ethernet frame. This new RAN Packet Stream Identifier TAG is marked by the first RAN node 111, as being a RAN endpoint and may then be identified by the intermediate nodes 113, 114 in the RAN transport network 102 and the second RAN node 112 as being a receiving RAN endpoint. This will be different compared to the existing prior art Flow (F)- tag used in 3GPP standard specification 802. laq Shortest Path Bridging (SPB), that limits the use of the F-tag to be only within an SPB-domain and that the F-tag needs to be set by one of the intermediate nodes 113, 114 such as a switch of one of the intermediate nodes 113, 114 in the RAN transport network 102 at an edge of the SPB domain. The RAN identifier according to embodiments herein, implemented as an Ethernet TAG may be set by any entity or node and identified by all entities or nodes within a full Ethernet domain.

[0193] The 48 bit RAN Packet Stream Identifier Tag in the example of Figure 8 comprises a 16 bit Type field, a 12 bit Reserved field and a 20 bit Stream identifier field. The 16 bit Type field is for the Ethertype value. The 12 bit Reserved field is for future use. The 20 bit Stream Identifier field is for the value of the RAN identifier. The value may e.g., be a single value identifying multiple items or the identifier is built up of multiple parts identifying separate items. The single value identifier or the different parts of the identifier may then indicate separate items such as the RAN packet stream, bitrate category, delay category, type of packet stream, allow / not allow distribution over multiple paths etc.

[0194] As mentioned, the RAN identifier when represented by a specific tag in an Ethernet frame and referred to as Stream Identifier, may have a 20-bit value field. This is to match with a IPv6 Flow-Label parameter that also has a 20-bit value. It is an advantage to have the same size for Ethernet Stream Identifier and IPv6 flow label as this simplifies implementation, and a simultaneous use of IP and Ethernet RAN packet stream identification in fronthaul. This means that the same size and definition of a RAN packet stream identification may be used for both Ethernet and IP network. The principles here outlined for Fronthaul may be applied also for Sidehaul and Midhaul.

[0195] Between two endpoints, IP or Ethernet addresses, there may be multiple RAN flows and / or streams, that are identified with the RAN identifier. An alternative example for implementing the RAN identifier as a 4-byte header of an Ethernet frame is depicted in Figure 9. The tag in the example of Figure 9 comprises a 16 bit Type field and a 16 bit Stream Identifier field. The 16 bit Type field may be similar to Figure 8. The 16 bit Stream Identifier is for the value of the RAN identifier and this value may be similar to as mentioned above in Figure 8. This 4-byte format of the RAN Packet Stream Identifier Tag is to match with a VLAN Tag size of 32-bit. The advantage to have same appearance and properties as a IEEE 802. IQ defined VLAN tag for RAN packet stream identification is the possible reuse of existing hardware deployed in RAN or Transport nodes.

[0196] An example of the placement of a 48 bit RAN Packet Stream Identifier Tag in an unencrypted Ethernet frame is depicted in Figure 10. The tag comprising the RAN identifier is referred to as Stream Identifier Tag (SIT) in Figure 10. The unencrypted Ethernet frame comprises a 6-byte Destination MAC (DMAC) address field related to the second RAN node 112, a 6-byte Source MAC (SMAC) address field related to the first RAN node 111, and a 4-byte VLAN tag for identifying any Virtual LAN(VLAN) parameter used. Further, a 6- byte SIT field for the RAN identifier described in Figure 8, a 2-byte EtherType field identifying the payload, the payload itself and a 4-byte Frame Check Sequence (FCS) field. The SIT may be placed behind the VLAN tag to indicate streams within the VLAN, this will enhance the scalability of the identifier as described earlier. The SIT is placed before the Payload EtherType Tag as this Ethertype identifies the type of payload. A similar format may be used for the placement of the 32-bit alternative of the RAN Packet Stream Identifier Tag as represented in Figure 9.

[0197] Figure 11 depicts the placement of a 48 bit RAN Packet Stream Identifier Tag, referred to as SIT, within an encrypted Ethernet frame according to IEEE 802.1AE. An encrypted Ethernet frame is similar to an unencrypted Ethernet frame as in Figure 10 but comprises an additional 16 byte Security Tag (SecTag) and an 8 or 16 byte Integrity Check Value (ICV) field. When MAC Security (MACsec) is used for packet integrity and confidentiality, the VLAN and SIT may or may not be encrypted depending on use case depicted as the two alternatives in Figure 11. In Figure 11, EDE-M means an Ethernet Data Encryption device for a VLAN-unaware MAC Bridge, EDE-CS means an Ethernet Data Encryption device for a Provider Edge Bridge, CC means an Ethernet Data Encryption device for each of the two C-VLAN components and SS means an Ethernet Data Encryption device for each of the two S-VLAN components. For the use case when a packet traverses a RAN transport network 102 from a first RAN node 111 towards a second RAN node 112 through intermediate nodes 113, 114, the VLAN and SIT information need to be set in clear, e.g., by placing before the SecTag and the encrypted payload as shown in the lower part of Figure 11. This may be used in cases relating to EDE-CS / CC / SS encryption. This ensures that the RAN identifier within the SIT is visible to all the nodes 111, 112, 113, 114 in the RAN transport network 102 enabling packet distribution and steering as disclosed in the embodiments herein. The upper part of Figure 11 shows a use case such as relating to EDE-M encryption, where the VLAN and SIT information is set by placing it after the SecTag and encrypted along with the payload.

[0198] Identifying a RAN packet stream related to an IPv6 network

[0199] In some example embodiments, an IPv6 Flow-label is representing the RAN packet stream identifier, e.g., when the RAN transport network 102 is related to an IP transport network. An example of this is shown in Figure 12. All principles described for the Ethernet embodiments above, also applies for IPv6.

[0200] In this example, single transport end-point addresses are used, a single IPv6 A address in the first RAN node 111 and a single IPv6 B address in the second RAN node 112. The RAN identifier is used to identify the RAN packet streams. Figure 12 illustrates the transport of packets from the first RAN node 111 towards the second RAN node 112 via the RAN transport network 102. For use of single RAN endpoint transport IP addresses for simplification / better scaling, and for steering of RAN packet stream onto path between first RAN node 111 and second RAN node 112, the first RAN node 111 marks the packets in the RAN Packet Stream with the RAN identifier in IPv6 Flow-label.

[0201] The RAN identifier may then further be used for distribution of RAN Packet Streams over multiple links between neighbouring nodes, e.g. load-balancing mechanism based on “instantaneous” port utilisation in the RAN Transport network 102, and further also used for RAN Packet Stream steering and / or distribution within the second RAN node 112 towards applicable RAN processing elements such as SAPs, and if encrypted, without having to first perform decryption.

[0202] Implementing the RAN identifier in a header of an IPv6 RAN packet

[0203] Figure 13 illustrates how the first RAN node 111 may mark an IPv6 RAN packet with the RAN identifier when IPsec Encapsulating Security Protocol (ESP) Tunnel mode is applied to the IPv6 RAN packet. It further illustrates how the RAN identifier in the Flow label is copied out to the visible, non-encrypted part of the outer IP header. This is to enable the identification and use of the RAN identifier to enable distribution and steering of RAN Packet Streams in both RAN Transport network 102 and the first level of RAN Packet Stream steering within the second RAN node 112, towards applicable RAN processing element such as SAP without having to first perform decryption. The copying out to make the RAN identifier visible when encrypted, may be performed by the first RAN node 111 e.g., by an IP Security (IPsec) function in the first RAN node 111, e.g., based on being configured to do that.

[0204] Figure 14 illustrates how the first RAN node 111 may mark an IPv6 RAN packet with the RAN identifier when IPsec ESP Transport mode is applied to the IPv6 RAN packet. In this embodiment the original IP header is kept, and the RAN identifier is visible outside the encrypted payload. The usage of RAN identifier is the same as described for Figure 13 above.

[0205] The RAN identifier embedded in the Flow label may be partitioned in two parts, as shown in Figure 14a, wherein:

[0206] - a first part 1400 (5 bits) comprising information on RAN packet flow type, and

[0207] - a second part 1404 (15 bit) comprising information on one or more RAN parameters.

[0208] The information on RAN packet flow type 1400 (embedded in the 5 bits) may comprise one or more of:

[0209] - eCPRI packet flow direction 1041, e.g., uplink or downlink. This information 1041 may be embedded in 1 bit. For example, the bit set to 0 may indicate downlink and the bit set to 1 may indicate uplink, or vice versa;

[0210] - eCPRI delay measurement indicator 1402. This information 1402 may be embedded in 1 bit. For example, the bit set to 1 may indicate that the delay measurement (between DU / vDU and RU) is enabled and that the packets should follow a same path and not be distributed, the bit set to 0 may indicate that the delay measurement is not enabled;

[0211] - eCPRI packet or flow type 1403. This information 1403 may be embedded in 3 bits.

[0212] Examples of the first part comprising information on packet or flow type (5 bits) is shown in Table I.

[0213] Table I: Example of the 5bit RAN packet flow type partition of the 20bit Flow label, wherein LLS-U stands for low layer split user plane, LLS-C for LLS control plane, LLS-M for LLS management plane, BFW for beamforming weights, TX for transmit, RX for receive, SRS for sounding reference signal, RU for Radio Unit, BB for baseband unit. The information on one or more RAN parameters (embedded in the 15 bits) may comprise:

[0214] - one or more eAxC-ID parameters from an eCPRI header, such as CC ID 1405, layer / RU port ID 1406, BandSector ID 1407, and / or

[0215] - RAN specific parameters, such as network slicing service type 1408 and network slicing service differentiator 1409.

[0216] A first example of the 15 bits comprising information on one or more RAN parameters is shown in Figure 14b, wherein the 15 bits may be split in the following way:

[0217] - 4 bits: CC ID 1405;

[0218] - 4 bits: Layer / RU_port_ID 1406;

[0219] - 1 bit: BandSector lD 1407 (each band has up to 16 Component Carriers and 16 layers);

[0220] - 1 bit: Telemetry indicator 1408 (0 = disabled Telemetry, 1 = enabled Telemetry);

[0221] - 3 bits: Network Slicing Service type 1409;

[0222] - 2 bits: Network slicing Service differentiator 1410.

[0223] A second example of the 15 bits comprising information on one or more RAN parameters is shown in Figure 14c, wherein the 15 bits may be split in the following way:

[0224] - 4 bits: CC ID 1405;

[0225] - 4 bits: Layer / RU_port_ID 1406;

[0226] - 1 bit: BandSector lD 1407 (each band has up to 16 Component Carriers, 16 layers);

[0227] - 1 bit: Telemetry indicator 1408 (0 = disabled Telemetry, 1 = enabled Telemetry);

[0228] - 2 bit: Network Slicing Service type 1409;

[0229] - 2 bit: Network slicing Service differentiator 1410;

[0230] - 1 bit: ecpriConcatenation 1411.

[0231] The ecpriConcatenation bit makes it possible for RAN node to do early RAN traffic identification without decoding the complete eCPRI message or before decryption.

[0232] Figure 15 illustrates how the first RAN node 111 may mark an IPv6 RAN packet, by using a specific Ipv6 Extension Header according to embodiments herein, for the RAN identifier. The usage of RAN Packet Stream Identifier is the same as described for Figure 13 above. If Ipsec Tunnel mode is used, it may not be needed to encrypt the Extension header. If Ipsec on extension header Stream ID is applied, the RAN identifier needs to be copied to an outer header Flow-label.

[0233] Figure 16 illustrates one possible detailed implementation of an Ipv6 Extension Header for the RAN Identifier (referred to as Packet Stream identifier in Figure 16). The usage of RAN Packet Stream Identifier may be similar as described for Figure 13 above.

[0234] The RAN identifier embedded in the Ipv6 Extension Header may be partitioned in two parts:

[0235] - a first part (5 bits) comprising information on RAN packet flow type, and

[0236] - a second part (43 bits) comprising information on one or more RAN parameters.

[0237] The information on RAN packet flow type (embedded in the 5 bits) may comprise one or more of the information as described for Figure 14a above.

[0238] The information on one or more RAN parameters (embedded in the 48 bit) may comprise

[0239] - one or more eAxC-ID parameters from an eCPRI header, such as CC ID, layer / RU port ID, BandSector ID and / or

[0240] - RAN specific parameters, such as network slicing service type and network slicing service differentiator.

[0241] An example of the 43 bits comprising information on one or more RAN parameters is shown in Figure 14d, wherein the 43 bit may be split in the following way:

[0242] - 3 bits: eCPRI header reserved 1412;

[0243] - 1 bit: ecpriConcatenation 1411;

[0244] - 16 bits: eCPRI eAxC ID (ecpriRtcid / ecpriPcid) 1413;

[0245] - 1 bit: Telemetry indicator 1408;

[0246] - 4bit: Network Slicing Service type 1409;

[0247] - 8bit: Network slicing Service differentiator 1410;

[0248] - 8 bits: UE flow in Component Carrier (CC), service type, service differentiator 1414;

[0249] - 2 bits: Reserved 1415.

[0250] Further information on RAN parameters can be found in O-RAN.WG4.CUS.0-R003-

[0251] V13.00. To perform the method actions above, the first RAN node I l l is configured to handle packets of a RAN packet stream from the first RAN node 111 towards the second RAN node 112 in a communications network 100. The RAN packet stream is adapted to be transmitted in a data session via the intermediate nodes 113, 114 in the RAN transport network 102 of the communications network 100.

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

[0253] The first RAN node I l l is further configured to obtain a RAN identifier identifying the RAN packet stream based on characteristics of the RAN packet stream.

[0254] The first RAN node I l l is further configured to mark the packets of the RAN packet stream with the RAN identifier.

[0255] The first RAN node I l l is further configured to transmit the RAN identifier marked RAN packets of the RAN packet stream towards the second RAN node 112.

[0256] The RAN identifier is adapted to enable the respective first RAN node 111 and intermediate nodes 113, 114 to:

[0257] - identify the RAN packet stream and obtain rules related to forwarding the packets of the RAN packet stream towards the second RAN node 112, and

[0258] - based on the obtained rules, control traffic steering and / or distribution of the packets comprised in the identified RAN packet stream, when forwarding the packets towards the second RAN node 112.

[0259] 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 RAN packet stream.

[0260] In some embodiments, the rules are adapted to be assigned to characteristics required to achieve for forwarding the respective packet in the identified packet stream^

[0261] The rules may be adapted to be obtained based on the RAN identifier comprising the characteristics of the RAN packet stream.

[0262] The rules when obtained, to control traffic steering and / or distribution, may be 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 RAN node 112.

[0263] In some embodiments, the RAN identifier is adapted to be represented by any one out of: an Ethernet tag, an IPv6 flow-label, an IPv6 Extension header, an IPv4 option header, a UDP port, or a specific part of an eAxC- ID, field.

[0264] The RAN packet stream may be adapted to be related to e.g., any one out of: an Ethernet domain, an Internet Protocol, IP, version 4, IPv4, domain and an IP version 6, IPv6, domain.

[0265] The RAN identifier comprises information on one or more of

[0266] - RAN packet flow type;

[0267] - one or more network slicing parameters;

[0268] - telemetry parameter.

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

[0270] In some embodiments, the distribution of the packets comprised in the identified RAN packet stream when forwarding the packets towards the second RAN node 112 is adapted to be performed over different alternative paths.

[0271] The RAN packet stream from the first RAN node 111 towards a second RAN node 112 may be adapted to be transmitted from a source endpoint of the first RAN node 111 towards one or more destination endpoints of the second RAN node 112.

[0272] To perform the method actions above, the first intermediate node 113 is configured to handle a RAN packet stream from the first RAN node 111 towards the second RAN node 112 in a communications network 100. The RAN packet stream is adapted to be transmitted in a data session via intermediate nodes 113, 114 comprising the first intermediate node 113, in a RAN transport network 102 of the communications network 100.

[0273] The first intermediate node 113 may comprise an arrangement depicted in Figure 18. The first intermediate node 113 may comprise an input and output interface 1800 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 1800 may comprise a wireless receiver not shown, and a wireless transmitter not shown.

[0274] The first intermediate node 113 is further configured to receive packets of a RAN packet stream. The respective packet of the RAN packet stream is adapted to be marked with a RAN identifier identifying the RAN packet stream,

[0275] The first intermediate node 113 is further configured to obtain rules related to forwarding the packets of the RAN packet stream towards the second RAN node 112 based on the RAN identifier.

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

[0277] In some embodiments, the rules are adapted to be assigned to characteristics required to achieve for forwarding the respective packet in the identified packet stream^

[0278] The rules may be adapted to be obtained based on the RAN identifier comprising characteristics of the RAN packet stream. The characteristics may e.g., comprise any one or more out of: the bitrate, delay, delay-variation, in-order delivery, of the RAN packet stream.

[0279] The rules when obtained, to control traffic steering and / or distribution, may be 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 RAN node 112.

[0280] In some embodiments, the RAN identifier is adapted to be represented by e.g., any one out of: an Ethernet tag, an IPv6 flow-label, an IPv6 Extension header, an IPv4 option header, a UDP port or a specific part of an eAxC ID field.

[0281] In some embodiments, the RAN identifier comprises information on one or more of

[0282] - RAN packet flow type;

[0283] - one or more network slicing parameters;

[0284] - telemetry parameter.

[0285] In some embodiments, the RAN packet stream is adapted to be related to e.g., any one out of: an Ethernet domain, an IPv4 domain and an IPv6 domain.

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

[0287] The distribution of the packets comprised in the identified RAN packet stream, when forwarding the packets towards the second RAN node 112 may be adapted to be performed over different alternative paths.

[0288] To perform the method actions above, the second RAN node 112 is configured to handle packets of a RAN packet stream from the first RAN node 111 towards the second RAN node 112 in a communications network 100. The RAN packet stream is adapted to be transmitted in a data session via intermediate nodes 113, 114 in a RAN transport network 102 of the communications network 100.

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

[0290] The second RAN node 112 is further configured to receive packets of a RAN packet stream. The respective packet of the RAN packet stream is marked with a RAN identifier identifying the RAN packet stream.

[0291] The second RAN node 112 is further configured to obtain information, based on the RAN identifier, about one or more Service Access Points SAPs and rules related to forward the packets of the RAN packet stream to the one or more SAPs.

[0292] The second RAN node 112 is further configured to forward the packets in the RAN packet stream to the one or more SAPs based on the obtained information and rules.

[0293] In some embodiments, the rules are adapted to be assigned to characteristics required to achieve for forwarding the respective packet in the identified packet stream^

[0294] In some embodiments, the rules are adapted to be obtained based on the RAN identifier comprising characteristics of the RAN packet stream. In these embodiments, the characteristics e.g., comprises, also referred to as be related to, any one or more out of: the bitrate, delay, delay-variation, in-order delivery, of the RAN packet stream. The rules when obtained, to control traffic steering and / or distribution, may be 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 to the one or more SAPs.

[0295] The RAN identifier may be adapted to be represented by e.g., any one out of: an Ethernet tag, an IPv6 flow-label, an IPv6 Extension header, an IPv4 option header, a UDP port or a specific part of an eAxC-ID field.

[0296] In some embodiments, the RAN identifier comprises information on one or more of

[0297] - RAN packet flow type;

[0298] - one or more network slicing parameters;

[0299] - telemetry parameter.

[0300] In some embodiments, the RAN packet stream is adapted to be related to e.g.., any one out of: an Ethernet domain, an IPv4 domain and an IPv6 domain.

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

[0302] The RAN packet stream from the first RAN node 111 towards a second RAN node 112 may be adapted to be transmitted from a source endpoint of the first RAN node 111 towards one or more destination endpoints of the second RAN node 112.

[0303] Embodiments herein may be implemented through a respective processor or one or more processors, such as the respective processor 1710 of a processing circuitry in the first RAN node 111 depicted in Figure 17, processor 1810 of a processing circuitry in the intermediate node 113 depicted in Figure 18, and processor 1910 of a processing circuitry in the second RAN node 112 depicted in Figure 19 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 RAN node 111, intermediate node 113 and second RAN node 112. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the respective first RAN node 111, intermediate node 113 and second RAN node 112.

[0304] The first RAN node 111, intermediate node 113 and second RAN node 112 may further comprise a respective memory 1720, memory 1820 and memory 1920 comprising one or more memory units. The respective memory 1720, memory 1820 and memory 1920 comprises instructions executable by the processor in the respective first RAN node 111, intermediate node 113 and second RAN node 112.

[0305] The respective memory 1720, memory 1820 and memory 1920 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 RAN node 111, intermediate node 113 and second RAN node 112.

[0306] In some embodiments, a respective computer program 1730, computer program 1830 and computer program 1930 comprises instructions, which when executed by the respective at least one processor 1710, processor 1810 and processor 1910, cause the at least one processor of respective first RAN node 111, intermediate node 113 and second RAN node 112 to perform the actions above.

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

[0308] 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.

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

[0310] 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.

[0311] 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 Al, Fl, Wl, El, 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 (UE), such as the UE 121, QQ112a, QQ112b, QQ1 12c, 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.

[0312] 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.

[0313] 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.

[0314] 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 (AUSF), 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).

[0315] 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.

[0316] As a whole, the communication system QQ100 of Figure 20 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. 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.

[0317] 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 WiFi, 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).

[0318] 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 QQl lOb). 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, for a 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.

[0319] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQl lOb. 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.

[0320] Figure 21 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 RAN node 111, intermediate node 113 and second RAN node 112 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 customerpremise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3 GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP 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).

[0321] 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 21. 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.

[0322] 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).

[0323] 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.

[0324] 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.

[0325] 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.

[0326] 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 (eUICC), 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.

[0327] 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.

[0328] 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 / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0329] 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).

[0330] 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.

[0331] 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 21.

[0332] 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-IoT 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.

[0333] 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.

[0334] Figure 22 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)), 0-RAN nodes or components of an 0-RAN node (e.g., O-RU, O-DU, O-CU).

[0335] 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).

[0336] 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), 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).

[0337] 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.

[0338] 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.

[0339] 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.

[0340] 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.

[0341] 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.

[0342] 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).

[0343] 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.

[0344] 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.

[0345] 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.

[0346] Embodiments of the network node QQ300 may include additional components beyond those shown in Figure 22 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.

[0347] Figure 23 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure 20, 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.

[0348] 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.

[0349] 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 (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, 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.

[0350] Figure 24 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.

[0351] 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.

[0352] 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.

[0353] 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.

[0354] 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.

[0355] 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.

[0356] Figure 25 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 20 and / or UE QQ200 of Figure 21), network node (such as network node QQ110a of Figure 20 and / or network node QQ300 of Figure 22), and host (such as host QQ116 of Figure 20 and / or host QQ400 of Figure 23) discussed in the preceding paragraphs will now be described with reference to Figure 25.

[0357] 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. 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 20) 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.

[0358] 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.

[0359] 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.

[0360] 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.

[0361] 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.

[0362] 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.

[0363] 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.

[0364] 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.

[0365] 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.

[0366] 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.

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

[0368] 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 Radio Access Network, RAN, node (111) for handling packets of a RAN packet stream from the first RAN node (111) towards a second RAN node (112) in a communications network (100), which RAN packet stream is to be transmitted in a data session via intermediate nodes (113, 114) in a RAN transport network (102) of the communications network (100), the method comprising: obtaining (402) a RAN identifier identifying the RAN packet stream based on characteristics of the RAN packet stream, marking (403) the packets of the RAN packet stream with the RAN identifier, transmitting (405) the RAN identifier marked RAN packets of the RAN packet stream towards the second RAN node (112), which RAN identifier enables the respective first RAN node (111) and intermediate nodes (113, 114) to:- identify the RAN packet stream and obtain rules related to forwarding the packets of the RAN packet stream towards the second RAN node (112), and- based on the obtained rules, control traffic steering and / or distribution of the packets comprised in the identified RAN packet stream, when forwarding the packets towards the second RAN node (112).

2. The method according to claim 1, 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 RAN packet stream, the rules are assigned to characteristics required to achieve for forwarding the respective packet in the identified packet stream, the rules are to be obtained based on the RAN identifier comprising the characteristics 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 RAN node (112).

3. The method according to any of the claims 1-2, wherein the RAN identifier is represented by any one out of: an Ethernet tag, an Internet Protocol version 6, IPv6, flow-label an IPv6 Extension header, an Internet Protocol version 4, IPv4, option header a User Datagram Protocol, UDP, port, or a specific part of an Antenna-Carrier, eAxC, -Identity, ID, field.

4. The method according to any of the claims 1-3, wherein the RAN identifier comprises information on one or more ofRAN packet flow type; one or more network slicing parameters; telemetry parameter.

5. The method according to any of the claims 1-4, wherein the RAN packet stream is related to any one out of: an Ethernet domain, an Internet Protocol, IP, version 4, IPv4, domain and an IP version 6, IPv6, domain.

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

7. The method according to any of the claims 1-6, wherein the distribution of the packets comprised in the identified RAN packet stream when forwarding the packets towards the second RAN node (112) is performed over different alternative paths.

8. The method according to any of the claims 1-7, wherein the RAN packet stream from the first RAN node (111) towards a second RAN node (112) is to be transmitted from a sourceendpoint of the first RAN node (111) towards one or more destination endpoints of the second RAN node (112).

9. 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 1-8.

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

11. A method performed by a first intermediate node (113) for handling a RAN packet stream from a first Radio Access Network, RAN, node (111) towards a second RAN node(112) in a communications network (100), which RAN packet stream is to be transmitted in a data session via intermediate nodes (113, 114) comprising the first intermediate node(113), in a RAN transport network (102) of the communications network (100), the method comprising: receiving (501) packets of a RAN packet stream, wherein the respective packet of the RAN packet stream is marked with a RAN identifier identifying the RAN packet stream, based on the RAN identifier, obtaining (502) rules related to forwarding the packets of the RAN packet stream towards the second RAN node (112), and based on the obtained rules, controlling any one or more out of: traffic steering and distribution, of the packets comprised in the identified RAN packet stream, when forwarding (503) the packets in the RAN packet stream towards the second RAN node (112).

12. The method according to claim 11, wherein any one or more out of: the rules are assigned to characteristics required to achieve for forwarding the respective packet in the identified packet stream, andthe rules are obtained based on the RAN identifier comprising characteristics of the RAN packet stream, which characteristics comprise 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 RAN node (112).

13. The method according to any of the claims 11-12, wherein the RAN identifier is represented by any one out of an Ethernet tag, an Internet Protocol version 6, IPv6, flow-label an IPv6 Extension header, an Internet Protocol version 4, IPv4, option header a User Datagram Protocol, UDP, port, or a specific part of an Antenna-Carrier, eAxC, -Identity, ID, field.

14. The method according to any of the claims 11-13, wherein the RAN identifier comprises information on one or more ofRAN packet flow type; one or more network slicing parameters; telemetry parameter.

15. The method according to any of the claims 11-14, wherein the RAN packet stream is related to any one out of an Ethernet domain, an Internet Protocol, IP, version 4, IPv4, domain and an IP version 6, IPv6, domain.

16. The method according to any of the claims 11-15, wherein a part of the respective packet of the RAN packet stream is encrypted, and wherein the RAN identifier is located outside the encrypted part of the respective packet when marked, to be visible to the respective intermediate nodes (113, 114) and second RAN node (112) without performing decryption of the packets.

17. The method according to any of the claims 11-16, wherein the distribution of the packets comprised in the identified RAN packet stream, when forwarding (503) the packets towards the second RAN node (112) is performed over different alternative paths.

18. 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 11-17.

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

20. A method performed by a second Radio Access Network, RAN, node (112) for handling packets of a RAN packet stream from a first RAN node (111) towards the second RAN node (112) in a communications network (100), which RAN packet stream is transmitted in a data session via intermediate nodes (113, 114) in a RAN transport network (102) of the communications network (100), the method comprising: receiving (601) packets of a RAN packet stream, wherein the respective packet of the RAN packet stream is marked with a RAN identifier identifying the RAN packet stream, based on the RAN identifier, obtaining (602) information about one or more Service Access Points (SAP)s and rules related to forward the packets of the RAN packet stream to the one or more SAPs, and based on the obtained information and rules, forwarding (603) the packets in the RAN packet stream to the one or more SAPs.

21. The method according to claim 20, wherein any one or more out of: the rules are assigned to characteristics required to achieve for forwarding the respective packet in the identified packet stream, andthe rules are obtained based on the RAN identifier comprising characteristics of the RAN packet stream, which characteristics comprise any one or more out of the bitrate, delay, delay-variation, in-order delivery, of the RAN packet stream, and wherein 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 to the one or more SAPs.

22. The method according to any of the claims 20-21, wherein the RAN identifier is represented by any one out of an Ethernet tag, an Internet Protocol version 6, IPv6, flow-label an IPv6 Extension header, an Internet Protocol version 4, IPv4, option headerA User Datagram Protocol, UDP, port, or a specific part of an Antenna-Carrier, eAxC, -Identity, ID, field.

23. The method according to any of the claims 20-22, wherein the RAN identifier comprises information on one or more ofRAN packet flow type; one or more network slicing parameters; telemetry parameter.

24. The method according to any of the claims 20-23, wherein the RAN packet stream is related to any one out of an Ethernet domain, an Internet Protocol, IP, version 4, IPv4, domain and an Internet Protocol, IP, version 6, IPv6, domain.

25. The method according to any of the claims 20-24, wherein a part of the respective packet of the RAN packet stream is encrypted, and wherein the RAN identifier is located outside the encrypted part of the respective packet when marked to be visible to the second RAN node (112) without performing decryption of the packets.

26. The method according to any of the claims 20-25, wherein the RAN packet stream from the first RAN node (111) towards a second RAN node (112) is to be transmitted from a source endpoint of the first RAN node (111) towards one or more destination endpoints of the second RAN node (112).

27. A computer program (1930) comprising instructions, which when executed by a processor (1910), causes the processor (1910) to perform actions according to any of the claims 20-26.

28. A carrier (1940) comprising the computer program (1930) of claim 27, wherein the carrier (1940) 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.

29. A first Radio Access Network, RAN, node (111) configured to handle packets of a RAN packet stream from the first RAN node (111) towards a second RAN node (112) in a communications network (100), which RAN packet stream is adapted to be transmitted in a data session via intermediate nodes (113, 114) in a RAN transport network (102) of the communications network (100), the first RAN node (111) is further configured to: obtain a RAN identifier identifying the RAN packet stream based on characteristics of the RAN packet stream, mark the packets of the RAN packet stream with the RAN identifier, transmit the RAN identifier marked RAN packets of the RAN packet stream towards the second RAN node (112), which RAN identifier is adapted to enable the respective first RAN node (111) and intermediate nodes (113, 114) to:- identify the RAN packet stream and obtain rules related to forwarding the packets of the RAN packet stream towards the second RAN node (112), and- based on the obtained rules, control traffic steering and / or distribution of the packets comprised in the identified RAN packet stream, when forwarding the packets towards the second RAN node (112).

30. The first RAN node (111) according to claim 29, 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 RAN packet stream, the rules are adapted to be assigned to characteristics required to achieve for forwarding the respective packet in the identified packet stream, the rules are adapted to be obtained based on the RAN identifier comprising the characteristics of the RAN packet stream, and 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 RAN node (112).

31. The first RAN node (111) according to any of the claims 29-30, wherein the RAN identifier is adapted to be represented by any one out of an Ethernet tag, an Internet Protocol version 6, IPv6, flow-label an IPv6 Extension header, an Internet Protocol version 4, IPv4, option header a User Datagram Protocol, UDP, port, or a specific part of an Antenna-Carrier, eAxC, -Identity, ID, field.

32. The first RAN node (111) according to any of the claims 29-31, wherein the RAN identifier comprises information on one or more ofRAN packet flow type; one or more network slicing parameters; telemetry parameter.

33. The first RAN node (111) according to any of the claims 29-32, wherein the RAN packet stream is adapted to be related to any one out of an Ethernet domain, an Internet Protocol, IP, version 4, IPv4, domain and an IP version 6, IPv6, domain.

34. The first RAN node (111) according to any of the claims 29-33, wherein a part of the respective packet of the RAN packet stream is adapted to be encrypted, and wherein the RAN identifier is adapted to be located outside the encrypted part of the respective packet when marked, to be visible to the respective first RAN node (111), intermediate nodes (113, 114) and second RAN node (112) without performing decryption of the packets.

35. The first RAN node (111) according to any of the claims 29-34, wherein the distribution of the packets comprised in the identified RAN packet stream when forwarding the packets towards the second RAN node (112) is adapted to be performed over different alternative paths.

36. The first RAN node (111) according to any of the claims 29-35, wherein the RAN packet stream from the first RAN node (111) towards a second RAN node (112) is adapted to be transmitted from a source endpoint of the first RAN node (111) towards one or more destination endpoints of the second RAN node (112).

37. A first intermediate node (113) configured to handle a RAN packet stream from a first Radio Access Network, RAN, node (111) towards a second RAN node (112) in a communications network (100), which RAN packet stream is adapted to be transmitted in a data session via intermediate nodes (113, 114) comprising the first intermediate node (113), in a RAN transport network (102) of the communications network (100), the first intermediate node (113) is further configured to: receive packets of a RAN packet stream, wherein the respective packet of the RAN packet stream is adapted to be marked with a RAN identifier identifying the RAN packet stream, based on the RAN identifier, obtain rules related to forwarding the packets of the RAN packet stream towards the second RAN node (112), and based on the obtained rules, control any one or more out of traffic steering and distribution, of the packets comprised in the identified RAN packet stream, when forwarding the packets in the RAN packet stream towards the second RAN node (H2).

38. The first intermediate node (113) according to claim 37, wherein any one or more out of: the rules are adapted to be assigned to characteristics required to achieve for forwarding the respective packet in the identified packet stream, and the rules are adapted to be obtained based on the RAN identifier comprising characteristics of the RAN packet stream, which characteristics comprise 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, 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 RAN node (112).

39. The first intermediate node (113) according to any of the claims 37-38, wherein the RAN identifier is adapted to be represented by any one out of an Ethernet tag, an Internet Protocol version 6, IPv6, flow-label an IPv6 Extension header, an Internet Protocol version 4, IPv4, option header a User Datagram Protocol, UDP, port, or a specific part of an Antenna-Carrier, eAxC, -Identity, ID, field.

40. The first intermediate node (113) according to any of the claims 37-39, wherein the RAN identifier comprises information on one or more ofRAN packet flow type; one or more network slicing parameters; telemetry parameter.

41. The first intermediate node (113) according to any of the claims 37-40, wherein the RAN packet stream is adapted to be related to any one out of an Ethernet domain, an Internet Protocol, IP, version 4, IPv4, domain and an IP version 6, IPv6, domain.

42. The first intermediate node (113) according to any of the claims 37-41, wherein a part of the respective packet of the RAN packet stream is adapted to be encrypted, and wherein the RAN identifier is adapted to be located outside the encrypted part of the respective packet when marked, to be visible to the respective intermediate nodes (113, 114) and second RAN node (112) without performing decryption of the packets.

43. The first intermediate node (113) according to any of the claims 37-42, wherein the distribution of the packets comprised in the identified RAN packet stream, when forwarding the packets towards the second RAN node (112) is adapted to be performed over different alternative paths.

44. A second Radio Access Network, RAN, node (112) configured to handle packets of a RAN packet stream from a first RAN node (111) towards the second RAN node (112) in a communications network (100), which RAN packet stream is adapted to be transmitted in a data session via intermediate nodes (113, 114) in a RAN transport network (102) of the communications network (100), the second RAN node (112) is further configured to: receive packets of a RAN packet stream, wherein the respective packet of the RAN packet stream is marked with a RAN identifier identifying the RAN packet stream, based on the RAN identifier, obtain information about one or more Service Access Points (SAP)s and rules related to forward the packets of the RAN packet stream to the one or more SAPs, and based on the obtained information and rules, forward the packets in the RAN packet stream to the one or more SAPs.

45. The second RAN node (112) according to claim 44, wherein any one or more out of the rules are adapted to be assigned to characteristics required to achieve for forwarding the respective packet in the identified packet stream, and the rules are adapted to be obtained based on the RAN identifier comprising characteristics of the RAN packet stream, which characteristics comprise any one or more out of the bitrate, delay, delay -variation, in-order delivery, of the RAN packet stream, andwherein 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 to the one or more SAPs.

46. The second RAN node (112) according to any of the claims 44-45, wherein the RAN identifier is adapted to be represented by any one out of: an Ethernet tag, an Internet Protocol version 6, IPv6, flow-label an IPv6 Extension header, an Internet Protocol version 4, IPv4, option headerA User Datagram Protocol, UDP, port, or a specific part of an Antenna-Carrier, eAxC, -Identity, ID, field.

47. The second RAN node (112) according to any of the claims 44-46, wherein the RAN identifier comprises information on one or more ofRAN packet flow type; one or more network slicing parameters; telemetry parameter.

48. The second RAN node (112) according to any of the claims 44-46, wherein the RAN packet stream is adapted to be related to any one out of: an Ethernet domain, an Internet Protocol, IP, version 4, IPv4, domain and an Internet Protocol, IP, version 6, IPv6, domain.

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

50. The second RAN node (112) according to any of the claims 44-49, wherein the RAN packet stream from the first RAN node (111) towards a second RAN node (112) is adaptedto be transmitted from a source endpoint of the first RAN node (111) towards one or more destination endpoints of the second RAN node (112).

Images