Method for a communication system
The RAN Dataflow Coordinator dynamically maps RAN dataflows to fronthaul transport resources, addressing service interruptions and optimizing resource usage in Open RAN fronthaul systems.
Patent Information
- Application Number
- PCT/EP2025/063365
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-15
- Publication Date
- 2026-11-19
AI Technical Summary
Conventional Open RAN fronthaul solutions require fixed and locked configurations between RAN Dataflows and Transport sessions, leading to service interruptions when configuration changes are necessary, prohibiting transport load-balancing and protection switching.
Introduce a RAN Dataflow Coordinator (RDFC) to dynamically map RAN dataflows to fronthaul transport resources, enabling flexible configuration changes without impacting RAN services, allowing load-balancing and protection switching.
Enables configuration changes without service disruptions, optimizes fronthaul transport resource usage, and simplifies RAN operation by separating the fixed relation between RAN data flows and fronthaul transport configuration.
Smart Images

Figure EP2025063365_19112026_PF_FP_ABST
Abstract
Description
[0001] METHOD FOR A COMMUNICATION SYSTEM
[0002] TECHNICAL FIELD
[0003] The present invention relates to Open RAN Fronthaul, RAN Lower Layer Split, LLS.
[0004] BACKGROUND
[0005] The Open RAN (O-RAN) alliance publishes specifications on Open RAN fronthaul, RAN Lower Layer Split (LLS). Specifications details communication between Baseband (O-DU) and Radio (O-RU). The fronthaul transport between O-DU and O-RU is a packet fronthaul, native Ethernet based or native IP based. The RAN data flows, specific RAN data exchanged between O-DU / O-RU RAN applications, are transported between O-DU and O-RU over the packet fronthaul. Every RAN data flow is, within O-DU / O-RU, mapped to a specific transport session, single or multiple RAN data flows can be mapped to a single transport session. RAN data flows are denoted extended Antenna Carrier Identifier (eAxC-ID) and they are built up of one or several evolved Common Public Radio Interface (eCPRI) messages. The fronthaul transport session is denoted Processing Element (PE) Transport endpoint(s), the transport session includes both source and destination address of the O-DU and O-RU respectively.
[0006] All configuration of RAN Dataflows and fixed mapping to transport sessions is performed during initial setup steps and performed by the O-RAN Management Plane (M-Plane) procedures, see e.g., 0-RAN.WG4.MP.0-R004-v17.01. After all configuration is done, the system goes into Operation with all configurations locked.
[0007] A problem with conventional solutions is that the fixed and locked configuration between the RAN Dataflow (eAxC-ID) and Transport session (PE transport endpoints) means that it’s not possible to perform any transport configuration changes without tearing down all related RAN configurations and re-configure the setup, thus creating a complete service interrupt.
[0008] Thus, there is a need for improved fronthaul functionality.
[0009] SUMMARY OF THE INVENTION
[0010] An objective of embodiments of the present invention is to provide a solution which mitigates or solves the drawbacks described above.The above and further objectives are achieved by the subject matter described herein. Further advantageous implementation forms of the invention are described herein. The invention is set out in the appended claims. The scope of the invention is defined by the claims which are incorporated into this section by reference.
[0011] According to a first aspect of the invention the object of the invention is achieved by a method for mapping Radio Access Network, RAN, dataflows to fronthaul transport resources performed by a RAN Dataflow Coordinator, RDFC, for Open Radio Access Network, O-RAN, fronthaul interfaces between O-RAN distributed units, O- DU, and O-RAN radio units, O-RU, the method comprising: obtaining first information indicative of one or more RAN dataflows, the first information comprising RAN dataflow endpoints and associated RAN dataflow transport characteristics requirements, obtaining second information indicating fronthaul transport resources, the fronthaul transport resources comprising at least pairs of processing element transport endpoints and enhanced low level links for the one or more RAN dataflows, obtaining third information indicating performance data and configuration data of the fronthaul transport resources, receiving data from the one or more RAN dataflows, selecting a subset of the fronthaul transport resources using the received data, the first information, the second information and the third information, initiating forwarding of the received data using the selected subset of fronthaul transport resources.
[0012] In one embodiment, selecting the subset of the fronthaul transport resources is performed by selecting a subset of the pairs of processing element transport endpoints that fulfills criteria of the first information, criteria of the second information and criteria of the third information. In one embodiment, the selected subset of the fronthaul transport resources is indicative of performing protection switching.
[0013] In one embodiment, the obtained first and / or third information comprises fronthaul transport load-balancing configurations, and the selected subset of the fronthaul transport resources is indicative of performing fronthaul transport load balancing.
[0014] In one embodiment, wherein the fronthaul transport load-balancing configuration is indicative of in-order-delivery of data from the one or more RAN dataflows, wherein the obtained second information is further indicative of forwarding functions associated with the pairs of processing element transport endpoints and available physical ports of a load balancing group, wherein the fronthaul transport load balancing is performed by the forwarding functions by distributing the one or more RAN dataflows over the available physical ports.In one embodiment, the fronthaul transport load-balancing configuration is indicative of out-of-order-delivery of data from the one or more RAN dataflows, wherein the obtained second information is further indicative of forwarding functions associated with the pairs of processing element transport endpoints and available physical ports of a load balancing group, wherein the fronthaul transport load balancing is performed by the forwarding functions by distributing the received data over the available physical ports.
[0015] In one embodiment, the distribution of the forwarding functions is based on physical port utilization indicated by the third information, wherein the physical port utilization is defined by a lest physical port usage and / or length of physical port queues.
[0016] In one embodiment, the selected subset of the fronthaul transport resources is indicative of performing delay management for the RAN dataflows.
[0017] In one embodiment, the selected transport resources comprises pairs of processing element transport endpoints, wherein the pairs of processing element transport endpoints comprise a respective O-DU PE transport endpoint and a respective O-RU PE transport endpoint.
[0018] In one embodiment, the RAN dataflow endpoints are identified by extended antenna-carrier identifiers eAxC-ID.
[0019] In one embodiment, the configuration data of the fronthaul transport resources is indicative of a selection of any of destination address, maximum fronthaul transport delay, transmission window size for fronthaul transport, pacing up to Max allowed delay, in-order-delivery, allowing out-of-order-delivery, Class of service, drop eligibility.
[0020] In one embodiment, the configuration data of the fronthaul transport resources is indicative of information about the local fronthaul physical ports, available source addresses, logical interface types, fronthaul transport load-balancing configuration, delay characteristics, bitrate of physical ports.
[0021] In one embodiment, the RDFC comprising multiple instances, one instance for each fronthaul interface for which data is exchanged
[0022] In one embodiment, the RDFC is implemented as multiple instances, one instance for each network slice, wherein each network slice comprises a selection of the one or more RAN dataflows.
[0023] In one embodiment, the RDFC is implemented as multiple instances, one instance for each logical transport interface.According to a second aspect of the invention the object of the invention is achieved by an Open Radio Access Network, O-RAN, radio unit, O-RU, for mapping RAN dataflows to fronthaul transport resources, the O-RU comprising: processing circuitry comprising a processor and a memory and wherein said memory is containing instructions executable by said processor, wherein the processing circuitry comprising is operative to perform the method according to the first aspect.
[0024] According to a third aspect of the invention the object of the invention is achieved by an Open Radio Access Network, O-RAN distributed unit, O- DU, for mapping RAN dataflows to fronthaul transport resources, the O-RU comprising: processing circuitry comprising a processor and a memory and wherein said memory is containing instructions executable by said processor, wherein the processing circuitry comprising is operative to perform the method according to the first aspect.
[0025] According to a fourth aspect of the invention the object of the invention is achieved by a computer program, comprising instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method according to the first aspect.
[0026] According to a fifth aspect of the invention the object of the invention is achieved by a carrier containing the computer program of the previous claim, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer-readable medium.
[0027] According to a sixth aspect of the invention the object of the invention is achieved by a computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method according to the first aspect. According to a sixth aspect of the invention the object of the invention is achieved by a computer program product, comprising instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method according to the first aspect. Reference will be made to the appended sheets of drawings that will first be described briefly.
[0028] BRIEF DESCRIPTION OF THE DRAWINGS
[0029] Fig. 1 shows a schematic view of pairs of processing element transport endpoints.
[0030] Fig.2 shows a conventional solution with RAN Dataflows fixedly mapped to transport sessions.
[0031] Fig. 3 schematically shows dynamic mapping of RAN Dataflows according to one or more embodiments of the present disclosure.Fig. 4A and Fig. 4B illustrates a forwarding functions according to one or more embodiments of the present disclosure.
[0032] Fig. 5 illustrates an example of egress from O-RU towards O-DU according to one or more embodiments of the present disclosure.
[0033] Fig. 6 illustrates an example of egress from O-DU towards O-RU according to one or more embodiments of the present disclosure.
[0034] Fig. 7 shows a method according to one or more embodiments of the present disclosure. Fig. 8A and Fig. 8B illustrates multiple instances of the RDF.
[0035] A more complete understanding of embodiments of the invention will be afforded to those skilled in the art, as well as a realization of additional advantages thereof, by a consideration of the following detailed description of one or more embodiments. It should be appreciated that like reference numerals are used to identify like elements illustrated in one or more of the figures.
[0036] DETAILED DESCRIPTION
[0037] As mentioned in the background section, the present disclosure relates to Open RAN fronthaul, RAN Lower Layer Split, LLS.
[0038] Details on this can be found in documents 0-RAN.WG4.CUS.0-R004-v17.01, O-RAN.WG4.MP.0-R004-V17.01, 0-RAN.WG4.MP-YANGS-R004-V17.01.
[0039] A problem with conventional solutions is that the fixed and locked configuration between the RAN Dataflow (eAxC-ID) and Transport session (PE transport endpoints) prohibits any type of transport load-balancing at the O-DU or O-RU transport ports. It also prohibits any type of transport protection switching at the O-DU or O-RU transport ports. It’s not possible to perform any transport configuration changes without tearing down all related RAN configurations and re-configure the setup, thus creating a complete service interrupt.
[0040] The present disclosure solves this problem by separating the “hard-locked” relation and configuration between RAN data flows (eAxC-IDs) and fronthaul transport configuration. This is achieved by introducing a RAN Dataflow Coordinator (RDFC).
[0041] The advantages of this disclosure are at least:
[0042] Enabling O-DU / O-RU fronthaul transport configuration changes without impact on RAN data flow configuration, thus no RAN service interrupt and that brings good value for the operatorEnabling O-DU / O-RU fronthaul transport protection switching without impact on RAN data flow configuration, with no RAN service disturbance. It’s great value for the operatorthat restoration of transport doesn’t affect RAN service or configuration
[0043] Enabling O-DU / O-RU to perform fronthaul transport load-balancing over the transport ports, resulting in optimal use of the scarce and expensive fronthaul transport resources. For the operator this gives maximum value out of the purchased and installed fronthaul transport resources, also sometimes enables activating RAN services or functions that otherwise would not be possible
[0044] The disclosure dynamically and flexibly selects O-DU / O-RU outgoing fronthaul transport for each RAN dataflow based on the dataflow transport characteristics requirements. This releases RAN applications from having to understand / measuring transport characteristics to adapt RAN services.
[0045] The disclosure enables adding or changing RAN data flow configuration without impact on fronthaul transport configuration. Simplifies RAN operation teams work, by not having to also plan and perform fronthaul transport re-configuration
[0046] The disclosure can perform (continuous) delay measurement on fronthaul transport paths between O-RU and O-DU, to be used when selecting fronthaul transport for RAN dataflows, delay information can also be provided to RAN control for decision on RAN applications In the present disclosure, the term “Radio Access Network” or “RAN” is used interchangeably and denotes a network as defined in the documents cited above.
[0047] In the present disclosure, the term “RAN dataflow” defines a flow of data between RAN dataflow endpoints.
[0048] In the present disclosure, the term “Open Radio Access Network” or “O-RAN” is used interchangeably.
[0049] In the present disclosure, the term “Processing Element” or “PE” is used interchangeably and denotes PEs as defined in the documents cited above.
[0050] In the present disclosure, the term “processing element transport endpoints” or “PE transport endpoints” denotes endpoints between PEs. In other words, the PE transport endpoints can be seen as two ends of a transport tunnel.
[0051] In the present disclosure, the term “O- DU” denotes O-RAN distributed units.
[0052] In the present disclosure, the term “O-RU” denotes O-RAN radio units.
[0053] Fig. 1 shows a schematic view of pairs of processing element transport endpoints.The O-RAN alliance publishes specifications, e.g., the ones cited above, on Open RAN fronthaul, RAN Lower Layer Split (LLS). Specifications details communication between Baseband (O-DU) and Radio (O-RU). The fronthaul transport between O-DU 110 and O-RU 130 is a packet fronthaul, native Ethernet based or native IP based. The RAN data flows, specific RAN data exchanged between O-DU / O-RU RAN applications, are transported between O-DU and O-RU over the packet fronthaul. Every RAN data flow is, within O-DU / O-RU, mapped to a specific transport session 120, single or multiple RAN data flows can be mapped to a single transport session. RAN data flows are denoted or identified by extended Antenna Carrier Identifier (eAxC-ID) and they convey data, e.g., built up of one or several evolved Common Public Radio Interface (eCPRI) messages.
[0054] The fronthaul transport session 120 is defined by a Processing Element (PE) 110 at the O-DU and a Processing Element (PE) 130 at the O-RU, or rather by Processing Element Transport endpoint(s) 111, 131. The transport session 120 includes both source and destination address of the O-DU and O-RU respectively.
[0055] Presently, all configuration of RAN Dataflows and fixed mapping to transport sessions is performed during initial setup steps and performed by the O-RAN Management Plane (M-Plane) procedures, see e.g., technical specification 0-RAN.WG4.MP.0-R004-v16.00.
[0056] In the current standardized solution, after all configuration is done, the system goes into operation with all configurations locked.
[0057] The Below the cited M-Plane specification describes in section 15.2.4 configuration relations of the O-RU RAN Dataflows and mapping to Transport sessions.
[0058] A simplified variant of a M-Plane configuration model, showing parts of the full model, is shown in Fig. 2.
[0059] Fig.2 shows a conventional solution with RAN Dataflows fixedly mapped to transport sessions. Fig. 2 illustrates an example of RAN Dataflows fixedly mapped to transport sessions in an O-RU.
[0060] The figure shows how physical ports (Phy port) are fixedly mapped to processing element transport endpoints (PE).
[0061] The figure further shows fixed mapping of low level tx links (lltxl), tx array carriers (txac), on the TX side.
[0062] The figure further shows fixed mapping of low level rx links (llrxl), rx array carriers (rxac), on the RX side.The figure further illustrates respective mapping to RAN dataflow endpoints eAxC-ID1, eAxC-ID3, eAxC-ID10, eAxC-ID11.
[0063] The figure further illustrates respective mapping to static low level tx endpoints and tx arrays. The figure further illustrates respective mapping to static low level rx endpoints and rx arrays.
[0064] Fig. 3 schematically shows dynamic mapping of RAN Dataflows according to the present disclosure.
[0065] In the present disclosure, a RAN Dataflow Coordinator, RDFC, 330 is introduced and is configured to map Radio Access Network, RAN, dataflows to fronthaul transport resources. The RDFC 330 obtains information indicative of one or more RAN dataflows defined by RAN dataflow endpoints 381-384 and / or associated RAN dataflow transport characteristics requirements associated to the RAN dataflows.
[0066] The RDFC 330 further obtains information indicating fronthaul transport resources. The fronthaul transport resources comprising at least pairs of processing element transport endpoints, as further described in relation to Fig. 1. The indicated fronthaul transport resources further comprising a novel improved low level links denoted enhanced low level links.
[0067] The RDFC 330 further obtains information indicating performance data and configuration data of the fronthaul transport resources.
[0068] The pairs of processing element transport endpoints as well as the enhanced low level links are then used by the RDFC 330 to map Radio Access Network, RAN, dataflows to fronthaul transport resources.
[0069] The RDFC 330 further obtains information of performance data and configuration data of the fronthaul transport resources, e.g., utilization of physical ports 311-313.
[0070] When the RDFC 330 receives data over the one or more RAN dataflows, the RDFC 330 then dynamically maps Radio Access Network, RAN, dataflows to fronthaul transport resources by selecting a subset of the fronthaul transport resources using all of the obtained information. An example of the received data may e.g., be eCPRI messages comprised in or distributed over one or more packets.
[0071] The RDFC 330 then initiates forwarding of the received data using the selected subset of fronthaul transport resources.An example of initiating the forwarding of the received data may be to transfer a packet to a physical port or to transfer the received data to a forwarding function associated with one or more physical ports.
[0072] In one embodiment, the RAN dataflow transport characteristics requirements is indicative of a RAN dataflow requiring protection switching.
[0073] In one example, a RAN dataflow have associated RAN dataflow transport characteristics that indicates that protection switching is required or desired. The RDFC 330 may then analyze the obtained performance data for available and functional physical ports and / or forwarding functions and select a subset of the fronthaul transport resources amongst those available and functional physical ports.
[0074] In one embodiment, the RAN dataflow transport characteristics requirements and / or the configuration data of the fronthaul transport resources comprises a fronthaul transport loadbalancing configurations. The RDFC 330 may then select a subset of the fronthaul transport resources indicative of performing fronthaul transport load balancing.
[0075] In one embodiment, the fronthaul transport load-balancing configuration is indicative of in-order-delivery of data over the one or more RAN dataflows, wherein the obtained second information is further indicative of forwarding functions associated with the pairs of processing element transport endpoints and available physical ports of a load balancing group, wherein the fronthaul transport load balancing is performed by the forwarding functions by distributing the one or more RAN dataflows over the available physical ports.
[0076] In one example, the RDFC 330 may then select a subset of the fronthaul transport resources for which the performance data of the fronthaul transport resources indicates a low load, e.g., initially selecting a first port 311 for a RAN dataflow having less utilization than a second port 312.
[0077] In one further example, the obtained information indicating fronthaul transport resources is further indicative of forwarding functions associated with the pairs of processing element transport endpoints and available physical ports of a load balancing group. The fronthaul transport load balancing is performed by the forwarding functions by distributing the received data over the available physical ports. In other words, distributing each RAN dataflow over the available physical ports.
[0078] In one further example, the RDFC 330 may obtain information indicating a forwarding function associated with available physical ports of a load balancing group. The RDFC 330 may then select a subset of the fronthaul transport resources for which the performance data of thefronthaul transport resources indicates a relatively low level of utilization, e.g., selecting a first port 311 having less utilization than a second port 312. The level of utilization may be indicated as physical port usage and / or length of physical port queues.
[0079] When applying in-order-delivery, all packets of a RAN dataflow must be sent in-order to assure that they arrive in the same order at the receiving end.
[0080] In one embodiment, the fronthaul transport load-balancing configuration is indicative of allowing out-of-order-delivery of data over the one or more RAN dataflows. The obtained information indicating fronthaul transport resources is further indicative of forwarding functions associated with the pairs of processing element transport endpoints and available physical ports of a load balancing group. The fronthaul transport load balancing is performed by the forwarding functions by distributing the received data over the available physical ports. In other words, distributing each received packet over the available physical ports.
[0081] In one example, the RDFC 330 may obtain information indicating a forwarding function associated with available physical ports of a load balancing group. The RDFC 330 may then select a subset of the fronthaul transport resources for which the performance data of the fronthaul transport resources indicates a relatively low level of utilization, e.g., selecting a first port 311 having less utilization than a second port 312. The level of utilization may be indicated as physical port usage and / or length of physical port queues.
[0082] When applying out-of-order-delivery, all packets of a RAN dataflow must not necessarily be sent in-order and may arrive in a different order at the receiving end.
[0083] In one embodiment, the selected subset of the fronthaul transport resources is indicative of performing delay management for the RAN dataflows.
[0084] In one example, the RDFC 330 may then select a subset of the fronthaul transport resources for which the performance data of the fronthaul transport resources indicates the lowest delay, e.g., select pairs of processing element transport endpoints for which the performance data has the lowest delay.
[0085] Fig 4A illustrates an example of fronthaul transport load balancing according to one or more embodiments of the present disclosure.
[0086] The figure illustrates RAN dataflows 421-423. RAN dataflow 421 and RAN dataflow 423 are associated with fronthaul transport load-balancing configurations that are indicative of in-order-delivery of data. RAN dataflow 422 is associated with fronthaul transport load-balancing configurations that is indicative of allowing out-of-order-delivery of data.RAN dataflow 421 is shown with a dotted line, RAN dataflow 422 is shown as a dashed line and RAN dataflow 423 is shown as a dash-dotted line.
[0087] Fig. 4A further illustrates an optional forwarding function 410 associated with available physical ports 411-412 of a load balancing group.
[0088] The RAN dataflow 421 and RAN dataflow 423 require in-order-delivery, and are therefore sent to a respective dedicated physical port 411 and 412. In other words, all packets of a RAN dataflow are sent in order to the dedicated physical port to ensure in-order delivery at the receiving side. It is understood that in some embodiments multiple ports may be used as dedicated ports without departing from the present disclosure.
[0089] In one example, when the first packet of RAN dataflow 421 initially arrives, a dedicated port will be assigned using performance data of the fronthaul transport resources and thereafter all packet of RAN dataflow 421 will use the dedicated port.
[0090] The performance data of the fronthaul transport resources indicates load of the physical ports, and the forwarding function 410 may then distribute the received data of RAN dataflow 422 over the available physical ports 411, 412, e.g., using the performance data.
[0091] In one example, each time a packet of RAN dataflow 422 arrives, a physical port will be assigned using performance data of the fronthaul transport resources.
[0092] In a more detailed example, the RAN dataflows 421-423 are set up with a bit rate of 60 Gb / s. The physical ports have a capacity of 100 Gb / s. RAN dataflow 422 will then not “fit into” any of the single physical ports 411, 412 as they only have 40 Gbps bitrate of available bandwidth left each. RAN dataflow 422 is therefore distributed over ports 411, 412 using out-of-order delivery of packets over both the available physical ports 411 , 412 of a load balancing group.
[0093] Fig 4B illustrates an example of fronthaul transport load balancing according to one or more embodiments of the present disclosure. The figure illustrates RAN dataflows 421-423.
[0094] In this example, RAN dataflows 421-423 are associated with fronthaul transport load-balancing configurations that is indicative of allowing out-of-order-delivery of data.
[0095] Fig. 4B further illustrates an optional forwarding function 410 associated with available physical ports 411-412 of a load balancing group.
[0096] The performance data of the fronthaul transport resources indicates at least loads of the physical ports 411-412, and the forwarding function 410 may then distribute the received data of RAN dataflows 421-423 over the available physical ports 411, 412, e.g., using the performance data.In one example, each time a packet of any of RAN dataflows 421-423 arrives, a physical port will be selected using performance data of the fronthaul transport resources, e.g. port use or que length.
[0097] In the example shown in Fig 4B, Packets relating to RAN dataflow 421 are illustrated by “A1, B1 C1”, packets relating to RAN dataflow 422 are illustrated by “A2, B2, C2” and Packets relating to RAN dataflow 423 are illustrated by “A3, B3, C3”.
[0098] Fig. 5 illustrates an example of egress from O-RU towards O-DU according to one or more embodiments of the present disclosure.
[0099] The top half of Fig. 5 illustrates the O-RU.
[0100] Fig. 5 illustrates a plurality of RAN dataflow endpoints 580. Fig. 5 further illustrates a plurality of enhanced low-level links 550. Fig. 5 further illustrates an instance of the RDFC 330 of the O-RU. Fig. 5 further illustrates processing element transport endpoints 321-323 of the O-RU. Fig. 5 further illustrates ports 311, 312 of the O-RU. Fig. 5 further illustrates an optional forwarding function 510 associated with a selection of the ports 311, 312 of the O-RU.
[0101] The bottom half of Fig. 5 illustrates the O-DU.
[0102] Fig. 5 illustrates a plurality of RAN dataflow endpoints 581 in the O-DU. Fig. 5 further illustrates a conventional traffic steering module 530 of the O-DU. Fig. 5 further illustrates processing element transport endpoints 521-524 of the O-DU. Fig. 5 further illustrates ports 511-513 of the O-DU.
[0103] In one example, whenever the instance of the RDFC 330 of the O-RU receives data from the plurality of enhanced low level links 550, the RDFC 330 selects a subset of available fronthaul transport resources and initiates forwarding to the O-DU.
[0104] Fig. 6 illustrates an example of egress from O-DU towards O-RU.
[0105] The top half of Fig. 6 illustrates the O-RU.
[0106] Fig. 6 illustrates a plurality of RAN dataflow endpoints 680. Fig. 6 further illustrates processing element transport endpoints 321-323 of the O-RU. Fig. 6 further illustrates ports 311, 312 of the O-RU. Fig. 6 further illustrates a conventional traffic steering module 630 of the O-RU. The bottom half of Fig. 6 illustrates the O-DU.
[0107] Fig. 6 illustrates a plurality of RAN dataflow endpoints 681 in the O-DU. Fig. 6 further illustrates an instance of the RDFC 330 of the O-DU. Fig. 5 further illustrates an optional forwarding function 610 associated with a selection of the ports 511-513 of the O-DU. Fig. 6 furtherillustrates processing element transport endpoints 521-524 of the O-DU. Fig. 6 further illustrates ports 511-513 of the O-DU.
[0108] In one example, whenever the instance of the RDFC 330 of the O-DU receives data from the RAN dataflow endpoints 681 in the O-DU, the RDFC 530 selects a subset of available fronthaul transport resources and initiates forwarding to the O-RU.
[0109] Fig. 7 shows a method according to one or more embodiments of the present disclosure. The method 700 is configured for mapping Radio Access Network, RAN, dataflows to fronthaul transport resources and is performed by a RAN Dataflow Coordinator, RDFC, for Open Radio Access Network, O-RAN, fronthaul interfaces between O-RAN distributed units, O- DU, and O-RAN radio units, O-RU. The method comprises:
[0110] Step 710: obtaining first information indicative of one or more RAN dataflows, the first information comprising RAN dataflow endpoints and associated RAN dataflow transport characteristics requirements.
[0111] In one example, the RAN data flows, identified by eAxC-IDs, are defined in the ORAN specification and is used in all the RAN communication between O-DU and O-RU.
[0112] In one embodiment, the RAN dataflow endpoints are identified by extended antenna-carrier identifiers eAxC-ID.
[0113] Step 720: obtaining second information indicating fronthaul transport resources, the fronthaul transport resources comprising at least pairs of processing element transport endpoints and enhanced low level links for the one or more RAN dataflows.
[0114] The pairs of processing element transport endpoints are further described in relation to Fig. 1. In one embodiment, the enhanced low level links comprises information selected from a destination address for a RAN dataflow, a maximum allowed fronthaul transport delay, a transmission window size for fronthaul transport, information on if pacing allowed up to a maximum allowed delay, information on if in-order-delivery of data packets is required, information on if out-of-order-delivery of data packets is allowed, information on desired class of service (QoS), information on data packet drop eligibility.
[0115] Step 730: obtaining third information indicating performance data and configuration data of the fronthaul transport resources.
[0116] In one example, the performance data includes utilization of physical ports defined as (lest) physical port usage and / or length of physical port queues.In one embodiment, the configuration data of the fronthaul transport resources is indicative of a selection of any of destination address, maximum fronthaul transport delay, transmission window size for fronthaul transport, pacing up to Max allowed delay, in-order-delivery, out-of-order-delivery Class of service, drop eligibility.
[0117] In one embodiment, the configuration data of the fronthaul transport resources is indicative of information about the local fronthaul physical ports, available source addresses, logical interface types, fronthaul transport load-balancing configuration, delay characteristics, bitrate on physical ports.
[0118] Step 740: receiving data from the one or more RAN dataflows.
[0119] The data is typically received as a data packet. The data packet may comprise a whole eCPRI message or part of the eCPRI message. The received data further may further comprise data of the enhanced low level links providing transport needs / details for the respective RAN data flows and / or packets.
[0120] Step 750: selecting a subset of the fronthaul transport resources using the received data, the first information, the second information and the third information.
[0121] In one example, selecting the subset of the fronthaul transport resources may comprise selecting pairs of processing element transport endpoints.
[0122] In one embodiment, selecting the subset of the fronthaul transport resources is performed by selecting a subset of the pairs of processing element transport endpoints that fulfills criteria of the first information, criteria of the second information and criteria of the third information. In one example, a fronthaul transport delay of a selected pairs of processing element transport endpoints meets what is defined in a RAN dataflow transport characteristics requirements of a respective RAN dataflow.
[0123] In one embodiment, the selected subset of the fronthaul transport resources is indicative of performing protection switching.
[0124] In one example, this involves automatically changing transport resources when errors or not fulfilled transport characteristics is identified.
[0125] In one embodiment, the selected subset of the fronthaul transport resources is indicative of performing delay management for the RAN dataflows.
[0126] In one example, this may involve to select fronthaul transport resources that meet RAN dataflow delay requirements of the first information.In one embodiment, the selected transport resources comprises pairs of processing element transport endpoints, wherein the pairs of processing element transport endpoints comprise a respective O-DU PE transport endpoint and a respective O-RU PE transport endpoint.
[0127] Step 760: initiating forwarding of the received data using the selected subset of fronthaul transport resources.
[0128] In one example, initiating forwarding of the received data comprises transferring the received data to a physical port and / or to a forwarding function.
[0129] In embodiments, the disclosure further comprises fronthaul transport load-balancing, as further described in relation to Fig. 4A and Fig. 4B.
[0130] In one embodiment, the obtained first and / or third information comprises fronthaul transport load-balancing configurations, and the selected subset of the fronthaul transport resources is indicative of performing fronthaul transport load balancing.
[0131] Additionally, or alternatively, the fronthaul transport load-balancing configuration is indicative of in-order-delivery of data overthe one or more RAN dataflows. In otherwords, the data and / or data packets of a RAN dataflow must be delivered in the same order that they are sent. In one embodiment, the obtained second information is further indicative of forwarding functions associated with the pairs of processing element transport endpoints and available physical ports of a load balancing group, wherein the fronthaul transport load balancing is performed by the forwarding functions by distributing the received data over the available physical ports. In one example, when a first packet of a RAN dataflow initially arrives, a port will be assigned to the RAN dataflow using performance data of the fronthaul transport resources, and thereafter all packet of the RAN dataflow will use the assigned port.
[0132] This is illustrated by the RAN data flows 421 and 423 of Fig. 4A. The data or data packets are transferred to a physical port, e.g., to a physical address of a physical port.
[0133] Additionally, or alternatively, the fronthaul transport load-balancing configuration is indicative of allowing out-of-order-delivery of data over the one or more RAN dataflows, wherein the obtained second information is further indicative of forwarding functions associated with the pairs of processing element transport endpoints and available physical ports of a load balancing group, wherein the fronthaul transport load balancing is performed by the forwarding functions by distributing the received data over the available physical ports.
[0134] In other words, the data or data packets are transferred to a forwarding function, e.g., to a logical group address.Additionally, or alternatively, the distribution of the forwarding functions is based on physical port utilization indicated by the third information, wherein the physical port utilization is defined by lest physical port usage and / or length of physical port queues.
[0135] In one example, if port 411 if Fig. 4A is occupied with transmission, forwarding function distributes the next data packet to port 412.
[0136] In some embodiments, the RDFC comprises one or more instances at a O-RU and / or at a O-DU.
[0137] In some embodiments, the RDFC comprises multiple instances.
[0138] Fig 8A illustrates multiple instances of the RDFC at a O-RU.
[0139] Fig 8B illustrates multiple instances of the RDFC at a O-DU.
[0140] In one embodiment, the RDFC comprises multiple instances, one instance for each fronthaul interface for which data is exchanged.
[0141] In one example, this includes a scenario where the O-RU has an instance of the RDFC for each O-DU that it is communicating with.
[0142] In one embodiment, the RDFC is implemented as multiple instances, one instance for each network slice, wherein each network slice comprises a selection of the one or more RAN dataflows. The selection may be made using any suitable criteria.
[0143] One example can be dividing RAN dataflows into different Radio access technologies such as 4G (LTE) or5G (NR).
[0144] In one embodiment, the RDFC is implemented as multiple instances, one instance for each logical transport interface.
[0145] In one example, an instance of the RDFC may be created for all different VPNs for transport for, e.g., dividing traffic to different operators (i.e., a multi-operator scenario).
[0146] Fig. 9 shows a computer 900 according to one or more embodiments of the present disclosure. The computer may e.g., be in the form of an Electronic Control Unit, a server, an on-board computer or a control arrangement. The computer may comprise a processor or processing means 912 communicatively coupled to a transceiver 904 configured for wired or wireless communication. Further, the computer may further comprise at least one optional antenna (not shown in figure). The antenna may be coupled to the transceiver 904 and is configured to transmit and / or emit and / or receive wireless signals in a wireless communication system, e.g., wireless signals comprising diagnostic actions or diagnostic data. In one example, the processor 912 may be any of a selection of processing circuitry and / or a central processingunit and / or processor modules and / or multiple processors configured to cooperate with each-other. Further, the computer may further comprise a memory 915. The memory 915 may contain instructions executable by the processor to perform any of the methods described herein. The memory and / or computer-readable storage medium referred to herein may comprise of essentially any memory, such as a ROM (Read-Only Memory), a PROM (Programmable Read-Only Memory), an EPROM (Erasable PROM), a Flash memory, an EEPROM (Electrically Erasable PROM), or a hard disk drive.
[0147] In a further embodiment, the computer may further comprise and / or be coupled to one or more sensors (not shown) configured to e.g., receive and / or obtain and / or measure physical properties pertaining to the vehicle 100 and / or transmission unit 130 and / or battery system 200 and send one or more control signals or sensor signals indicative of the physical properties to the processing means 912.
[0148] In one or more embodiments the computer may further comprise an input device 917, configured to receive input or indications from a user and send a user-input signal indicative of the user input or indications to the processor or processing means 912.
[0149] In one or more embodiments the computer may further comprise a display 918 configured to receive a display signal indicative of rendered objects, such as text or graphical user input objects, from the processor or processing means 912 and to display the received signal as objects, such as text or graphical user input objects.
[0150] In one embodiment the display 918 is integrated with the user input device 917 and is configured to receive a display signal indicative of rendered objects, such as text or graphical user input objects, from the processing means 912 and to display the received signal as objects, such as text or graphical user input objects, and / or configured to receive input or indications from a user and send a user-input signal indicative of the user input or indications to the processing means 912.
[0151] In embodiments, the processing means 912 is communicatively coupled to a selection of any of the memory 915 and / or the communications interface and / or transceiver and / or the input device 917 and / or the display 918 and / or the one or more sensors. In embodiments, the transceiver 904 communicates using wired and / or wireless communication techniques. The wired or wireless communication techniques may comprise any of Bluetooth, Wi-Fi, GSM, UMTS, LTE or LTE advanced communications network or any other wired or wireless communication network known in the art.
[0152] In one embodiment, a computer is provided, the control arrangement comprising:a processor, and a memory, said memory containing instructions executable by said processor, whereby said computer is operative to perform any of the methods described herein.
[0153] In one embodiment, a computer program (product) is provided and comprises instructions which, when the program is executed by a computer, cause the computer to carry out any of the methods described herein.
[0154] In one embodiment, a computer-readable medium is provided and comprises instructions which, when executed by a computer, cause the computer to carry out any of the methods described herein.
[0155] The term “computer” may be defined as any hardware or hardware / firmware device implemented using processing circuity such as, but not limited to, a processor, Central Processing Unit (CPU), a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a System-on-Chip (SoC), a programmable logic unit, a microprocessor, an application-specific integrated circuit, or any other device capable of electronically performing operations in a defined manner.
[0156] In some embodiments, the computer-readable medium may be a non-transitory computer-readable medium, such as a tangible electronic, magnetic, optical, infrared, electromagnetic, and / or semiconductor system, apparatus, and / or device.
[0157] In one embodiment, the computer program product may be a computer readable medium, and the computer program may be stored in the computer readable medium described herein. In embodiments, the communications network herein communicate using wired or wireless communication techniques that may include at least one of a Local Area Network (LAN), Metropolitan Area Network (MAN), Global System for Mobile Network (GSM), Enhanced Data GSM Environment (EDGE), Universal Mobile Telecommunications System, Long term evolution, High Speed Downlink Packet Access (HSDPA), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth®, Zigbee®, Wi-Fi, Voice over Internet Protocol (VoIP), LTE Advanced, IEEE802.16m, Wireless MAN-Advanced, Evolved High-Speed Packet Access (HSPA+), 3GPP Long Term Evolution (LTE), Mobile WiMAX (IEEE 802.16e), Ultra Mobile Broadband (UMB) (formerly Evolution-Data Optimized (EV-DO) Rev. C), Fast Low-latency Access with Seamless Handoff Orthogonal Frequency Division Multiplexing (Flash-OFDM), High Capacity Spatial Division Multiple Access (iBurst®) and Mobile Broadband Wireless Access (MBWA) (IEEE 802.20) systems, High Performance Radio Metropolitan Area Network (HIPERMAN),Beam-Division Multiple Access (BDMA), World Interoperability for Microwave Access (WiMAX) and ultrasonic communication, etc., but is not limited thereto.
[0158] Moreover, it is realized by the skilled person that the system and / or devices may comprise the necessary communication capabilities in the form of e.g., functions, means, units, elements, etc., for performing the present solution. Examples of other such means, units, elements and functions are: processors, memory, buffers, control logic, , multipliers, decision units, selecting units, switches, modulators, demodulators, inputs, outputs, antennas, amplifiers, receiver units, transmitter units, DSPs, MSDs, encoder, decoder, power supply units, power feeders, communication interfaces, communication protocols, etc. which are suitably arranged together for performing the present solution.
[0159] Especially, the processor and / or processing means of the present invention may comprise one or more instances of processing circuitry, processor modules and multiple processors configured to cooperate with each-other, Central Processing Unit (CPU), a processing unit, a processing circuit, a processor, an Application Specific Integrated Circuit (ASIC), a microprocessor, a Field-Programmable Gate Array (FPGA) or other processing logic that may interpret and execute instructions. The expression “processor” and / or “processing means” may thus represent a processing circuitry comprising a plurality of processing circuits, such as, e.g., any, some, or all of the ones mentioned above. The processing means may further perform data processing functions for inputting, outputting, and processing of data comprising data buffering and device control functions, such as call processing control, user interface control, or the like.
[0160] Finally, it should be understood that the invention is not limited to the embodiments described above, but also relates to and incorporates all embodiments within the scope of the appended independent claims.
Claims
CLAIMS1. A method for mapping Radio Access Network, RAN, dataflows to fronthaul transport resources performed by a RAN Dataflow Coordinator, RDFC, for Open Radio Access Network, O-RAN, fronthaul interfaces between O-RAN distributed units, O- DU, and O-RAN radio units, O-RU, the method comprising:obtaining first information indicative of one or more RAN dataflows, the first information comprising RAN dataflow endpoints and associated RAN dataflow transport characteristics requirements,obtaining second information indicating fronthaul transport resources, the fronthaul transport resources comprising at least pairs of processing element transport endpoints and enhanced low level links for the one or more RAN dataflows,obtaining third information indicating performance data and configuration data of the fronthaul transport resources,receiving data from the one or more RAN dataflows,selecting a subset of the fronthaul transport resources using the received data, the first information, the second information and the third information, initiating forwarding of the received data using the selected subset of fronthaul transport resources.
2. The method according to any of the preceding claims, wherein selecting the subset of the fronthaul transport resources is performed by selecting a subset of the pairs of processing element transport endpoints that fulfills criteria of the first information, criteria of the second information and criteria of the third information.
3. The method according to any of the preceding claims, wherein the selected subset of the fronthaul transport resources is indicative of performing protection switching.
4. The method according to any of the preceding claims, wherein the obtained first and / or third information comprises fronthaul transport load-balancing configurations, and the selected subset of the fronthaul transport resources is indicative of performing fronthaul transport load balancing.
5. The method according to claim 4, wherein the fronthaul transport load-balancing configuration is indicative of in-order-delivery of data from the one or more RAN dataflows, wherein the obtained second information is further indicative of forwarding functions associated with the pairs of processing element transport endpoints and available physical ports of a load balancing group, wherein the fronthaul transport load balancing is performed by the forwarding functions by distributing the one or more RAN dataflows over the available physical ports.
6. The method according to claim 4, wherein the fronthaul transport load-balancing configuration is indicative of out-of-order-delivery of data from the one or more RAN dataflows, wherein the obtained second information is further indicative of forwarding functions associated with the pairs of processing element transport endpoints and available physical ports of a load balancing group, wherein the fronthaul transport load balancing is performed by the forwarding functions by distributing the received data over the available physical ports.
7. The method according to claim 6, wherein the distribution of the forwarding functions is based on physical port utilization indicated by the third information, wherein the physical port utilization is defined by a lest physical port usage and / or length of physical port queues.
8. The method according to any of the preceding claims, wherein the selected subset of the fronthaul transport resources is indicative of performing delay management for the RAN dataflows.
9. The method according to any of the preceding claims, wherein the selected transport resources comprises pairs of processing element transport endpoints, wherein the pairs of processing element transport endpoints comprise a respective O- DU PE transport endpoint and a respective O-RU PE transport endpoint.
10. The method according to claim 9, wherein the RAN dataflow endpoints are identified by extended antenna-carrier identifiers, eAxC-ID.
11. The method according to any of the preceding claims, wherein the configuration data of the fronthaul transport resources is indicative of a selection of any of destination address, maximum fronthaul transport delay, transmission window size for fronthaul transport, pacing up to Max allowed delay, in-order-delivery, allowing out-of-order-delivery, Class of service, drop eligibility.
12. The method according to any of the preceding claims, wherein the configuration data of the fronthaul transport resources is indicative of information about the local fronthaul physical ports, available source addresses, logical interface types, fronthaul transport load-balancing configuration, delay characteristics, bitrate of physical ports.
13. The method according to any of the preceding claims, the RDFC comprising multiple instances, one instance for each fronthaul interface for which data is exchanged14. The method according to any of the preceding claims wherein the RDFC is implemented as multiple instances, one instance for each network slice, wherein each network slice comprises a selection of the one or more RAN dataflows.
15. The method according to any of the preceding claims , wherein the RDFC is implemented as multiple instances, one instance for each logical transport interface.
16. An Open Radio Access Network, O-RAN, radio unit, O-RU, for mapping RAN dataflows to fronthaul transport resources, the O-RU comprising: processing circuitry comprising a processor and a memory and wherein said memory contains instructions executable by said processor,wherein the processing circuitry comprising is operative to perform the method according to any of claims 1-15.
17. An Open Radio Access Network, O-RAN distributed unit, O- DU, for mapping RAN dataflows to fronthaul transport resources, the O-RU comprising: processing circuitry comprising a processor and a memory and wherein said memory contains instructions executable by said processor,wherein the processing circuitry comprising is operative to perform the method according to any of claims 1-15.
18. A computer program, comprising instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method according to any of claims 1 to 15.
19. A carrier containing the computer program of the previous claim, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer-readable medium.
19. A computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method according to any of claims 1 to 15.
20. A computer program product, comprising instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method according to any one of claims 1 to 15.
