WO2025193134A1 - Nœuds de réseau et procédés de gestion de ressources de transport dans un réseau de communication sans fil - Google Patents

Nœuds de réseau et procédés de gestion de ressources de transport dans un réseau de communication sans fil

Info

Publication number
WO2025193134A1
WO2025193134A1 PCT/SE2024/050237 SE2024050237W WO2025193134A1 WO 2025193134 A1 WO2025193134 A1 WO 2025193134A1 SE 2024050237 W SE2024050237 W SE 2024050237W WO 2025193134 A1 WO2025193134 A1 WO 2025193134A1
Authority
WO
WIPO (PCT)
Prior art keywords
transport
ran
node
related information
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/SE2024/050237
Other languages
English (en)
Inventor
Linnea FAXEN
Paolo Debenedetti
Luca LUNARDI
Carin OMURCALI
Roberto Magri
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Priority to PCT/SE2024/050237 priority Critical patent/WO2025193134A1/fr
Publication of WO2025193134A1 publication Critical patent/WO2025193134A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/02—Resource partitioning among network components, e.g. reuse partitioning
    • H04W16/04—Traffic adaptive resource partitioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/27—Control channels or signalling for resource management between access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • Embodiments herein relate to network nodes and methods therein. In particular, they relate to handling transport resources for one or more radio access network nodes in a wireless communication network.
  • wireless devices also known as wireless communication devices, mobile stations, and/or user equipment (UE), communicate via a Radio Access Network (RAN) to one or more core networks (CN).
  • the RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be denoted, for example, a “NodeB” or “eNodeB” or “eNB” or “gNB”.
  • a service area or cell area is a geographical area where radio coverage is provided by the radio network node.
  • the radio network node communicates over an air interface operating on radio frequencies with the wireless communication device within a range of the radio network node.
  • a Universal Mobile Telecommunications System is a third generation (3G) telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM).
  • GSM Global System for Mobile Communications
  • EPS Evolved Packet System
  • 4G Fourth Generation
  • LTE Long Term Evolution
  • 3GPP 3rd Generation Partnership Project
  • a 5G transport network connects 5G RAN and core network.
  • the 5G transport network uses a new network architecture and key technologies.
  • a Transport Network consists of various network elements such as routers, switches, optical transmission equipment, and multiplexers/demultiplexers. These elements facilitate the transmission and routing of data packets or signals across the network.
  • the structure of a 5G Transport Network includes base stations for wireless connectivity, fronthaul and midhaul networks for high-speed data transport, optical fiber infrastructure for connectivity, core network for data routing and management, and packet switching technology for efficient data handling.
  • the main drivers for RAN optimization are:
  • 5G is designed to work in different frequency ranges. As the number of frequencies increases, so does the importance of placing UEs in the best cells. Combined with carrier aggregation (CA), this means CSPs must consider multiple cells, or sets of cells, when selecting the most adequate cell set for each UE.
  • CA carrier aggregation
  • 5G services will require massive capacity and throughput, while others will be more dependent on latency and low-energy consumption in the UE.
  • the UE may also be tailored to different types of use cases such as smartphones, simple sensors, augmented reality (AR) headsets, and fixed-wireless access (FWA) equipment, where different levels of feature support are required.
  • AR augmented reality
  • FWA fixed-wireless access
  • Carrier Aggregation was included in the first release of the 5G standard, making it possible to configure a PCell for UEs and then add one or more SCell(s) to increase their downlink (DL) or uplink (UL) throughput.
  • the total UE throughput with CA is realized by the combination of the PCell and the SCell(s), instead of individual cells.
  • the number of combinations of PCell and SCell(s) to be aggregated could be huge and varies for different UEs according to their capabilities. This brings complexity to finding the best UE configuration for each network deployment.
  • MBH Mobile Backhaul
  • Fronthaul Wireless Backhaul
  • MBH refers to the part of the network that connects the cell sites like base stations or small cells to the core network. It is responsible for transporting data traffic between the cell sites and the core network, enabling communication between mobile devices and the broader telecommunications infrastructure.
  • the fronthaul domain is RAN-near transport domain which refers to the portion of the transport network that is closely integrated with the RAN. This domain encompasses the transport network elements and functionalities that directly support the connectivity between the radio base stations e.g. gNodeBs or small cells and the core network.
  • the fronthaul domain includes a fronthaul network, which connects radio base stations gNodeBs or small cells to the central processing units (CUs) or distributed units (DUs) within the RAN.
  • Fronthaul connectivity is essential for transporting high-speed data traffic between the radio equipment and the processing units.
  • Figure 1 shows an example of a 5G transport network architecture 100.
  • a number of RAN nodes e.g. eMBB, mMTC, radio unit (RU), Centralized Unit (CU), Distributed Units (DU), a number of routers (R), a Data Center (DC), a core network (CN) etc.
  • a CU may control one or more DUs.
  • a RAN CU may be an implementation of a logical gNB-CU or gNB-CU-CP.
  • a gNB may consist of a gNB-CU and one or more gNB-DU(s).
  • a gNB-CU and a gNB-DU is connected via F1 interface.
  • gNBs can be interconnected through Xn interface.
  • MBH and Fronthaul are relevant to the Xn/X2/F1/E1 interfaces, using Internet Protocol (IP) transport networks to interconnect network nodes.
  • IP Internet Protocol
  • MBH and Fronthaul use the general concepts of Quality of Service (QoS) and network slicing for RAN service differentiation and traffic optimization.
  • QoS Quality of Service
  • IETF Internet Engineering Task Force
  • the Transport Network can differentiate the performances offered by each Transport network slice and therefore provide different bandwidth, latency, availability.
  • the main drivers for RAN Traffic changes are relevant to:
  • Figure 4 is a schematic block diagram illustrating a communication network in which new feature or function blocks may be implemented in existing network nodes according to embodiments herein;
  • the RTE function determines or obtains an indication that new or updated TNL resources are needed and requests the new or updated TNL resources to the Transport SDN Controller T-SDNc.
  • the T-SDNc determines new or updated TNL Offered Capacity or other TNL related configuration parameter(s).
  • the dynamic remapping of the RAN network slices over the Transport network slices is realized by setting the new or updated TNL Offered Capacity or other TNL related configuration parameter(s)) for one or more RAN Distributed Unit(s).
  • the setting can be performed indirectly, i.e. , the T-SDNc sends the new mapping to the RAN CU, which in turns sends the mapping to one or more RAN DUs, or directly, i.e., the T-SDNc sends the new mapping directly to one or more RAN DUs.
  • the RTE responsive to the detection of discrepancy among provisioned, offered and available transport capacity, initiates actions towards CU or T-SDNc including but not limited to:
  • RAN CU to modify the offered TNL capacity from/to one or more DU(s), responsive to a change in the Transport available capacity from/to the one or more DU(s).
  • T-SDNc to initiate a request to change one or more CU-DU transport link capacity.
  • RTE of RAN CU may decide to reduce the offered capacity or ask T-SDNc to increase or reduce the provisioned capacity.
  • the solution may use Transport network layer (TNL) information elements calculated and communicated over the standardized interfaces, such as the 3GPP F1 and/or Xn interfaces respectively according to TS 38.473 and TS 38.423, and/or defined as a proprietary extensions to the 3GPP standards.
  • TNL Transport network layer
  • new RTA and RTE features or functions may be proposed to implement in a RAN network node based on 3GPP standard TS 38.300 whereas a CU can control a multitude of DUs and whereas the RAN CU can be an implementation of a logical gNB-CU or gNB-CU-CP) as defined in 3GPP standard TS 38.300.
  • Figure 5 shows an example signal flow chart between the network nodes RAN CU, RAN DU1 , RAN DU2 and T-SDNc for handling transport resources in the communication network 400.
  • the signal flow comprises the following steps.
  • Step 510/511 The RTA/RTE of the RAN CU sends a request message to one or more RAN DUs to request the RTA of the one or more DUs, e.g. DU1, DU2, to provide TNL related information concerning the usage of certain TNL resources, e.g., TNL Available Capacity.
  • This step may be repeated for all the DUs served by the CU.
  • This step may be realized according to existing 3GPP standard, for instance by means of a RESOURCE STATUS REQUEST F1AP message.
  • Step 520/521 The RTA in the one or more DUs reports to the RTA of the CU the requested TNL related information.
  • This step may be realized according to existing 3GPP standard, for instance by means of a RESOURCE STATUS UPDATE F1AP message.
  • Step 530 The RTA of the CU may send to the RTE of the CU the TNL related information obtained from the RTA of the DUs, if the RTA and RTE are implemented as two separate function blocks in the CU. If the RTA and RTE are implemented as one function block in the CU, the RTE or RTA of the CU, based at least in part on the received TNL related information, determines itself or obtains from another entity/function within/outside the CU that new/updated TNL resources e.g., an updated value of TNL Offered Capacity are needed for one or more DUs.
  • new/updated TNL resources e.g., an updated value of TNL Offered Capacity are needed for one or more DUs.
  • Step 540 The RTE or RTA of the CU sends a message to the T-SDNc, the message comprising at least one of:
  • TNL Available Capacity pertaining to a certain DU is low or too low, or lower than a threshold.
  • TNL Available Capacity pertaining to a certain DU is high or higher than a threshold.
  • TNL resources pertaining to a certain DU e.g., a difference between TNL Offered Capacity and TNL Available Capacity, is too low, either in absolute values of in percentage.
  • Any of the above information can be requested or reported for a certain granularity or at different granularities, for instance, per Class of Service, or per cell etc.
  • the same message as in step 540, or a separate message, may be sent from the RTE of the CU to the T-SDNc to report TNL related information, as received from the RTA of the one or more DUs, or in some aggregated format e.g., the maximum, or the minimum, or the average of TNL Available Capacity over a certain time interval.
  • Step 550 the T-SDNc may send to the RTE/RTA of the CU the new/updated values of TNL related information e.g., the new values of TNL Offered capacity to be applied to the one or more DUs.
  • This step may in alternative be executed between the T-SDNc and the RTA of the one or more DUs, in which case the Steps 551 and 552 that follows are not executed.
  • Step 551/552 The RTA of the Central Unit sends to the RTA of the one or more DUs the new/updated values of TNL related information received from the T-SDNc in Step 550.
  • the T-SDNc may send the new/updated values of TNL related information e.g., the new values of TNL Offered capacity to be applied to the one or more DUs, to the respective DUs.
  • TNL related information e.g., the new values of TNL Offered capacity to be applied to the one or more DUs, to the respective DUs.
  • the first RAN node 410 sends a request to one or more second RAN nodes 421, 422 for requesting transport or TNL related information from the one or more second RAN nodes 421 , 422.
  • the transport/TNL related information comprises a set of transport network metrics related to their transport resource utilization (TRU).
  • a granularity of the transport related information requested or reported may be any one or a combination of the following: a) per network node, b) per Class of Service, c) per group of Class of Services: a group of Class of Services is a set of one or more Class of Services for which transport network reporting can be achieved, wherein the set is determined based on common characteristics of the individual Class of Services. Common characteristics can be one or more of: . a certain value e.g., a maximum or range of values for delay I packet loss I jitter that the traffic carried over the Class of Services in the group of Class of Services can tolerate;
  • a certain value e.g., a minimum guaranteed bit rate for the Class of Services in the group of Class of Services need
  • a set of services/communication type whose traffic is carried over transport resources associated to the Class of Services e.g. URLLC type of communication, or Time Sensitive Network type of communication.
  • GTP- U General Packet Radio Service Tunneling Protocol in User Plane
  • the values of the set of transport network metrics may be reported as any one or a combination of the following:
  • a percentage of the values collected for a transport network metric during a time period which are fulfilled a certain criterion, e.g. RTT, DL/UL packet error rate, DL/UL packet loss, DL/UL queuing delay are within/above/below a reference/threshold, or between a first reference/threshold and a second reference/threshold;
  • a percentage of users for which the values collected for a transport network metric during a time period are fulfilled a certain criterion e.g. RTT, DL/UL packet error rate, DL/UL packet loss, DL/UL queuing delay are within/above/below a reference/threshold, or between a first reference/threshold and a second reference/threshold.
  • a certain criterion e.g. RTT, DL/UL packet error rate, DL/UL packet loss, DL/UL queuing delay are within/above/below a reference/threshold, or between a first reference/threshold and a second reference/threshold.
  • the maximum/minimum/average value of experienced latency is reported for a certain network node e.g. a gNB-Dll or a certain cell, or a certain Class of Service.
  • a certain network node e.g. a gNB-Dll or a certain cell, or a certain Class of Service.
  • a distribution of values of experienced latency is reported for a certain network node e.g. a gNB-Dll or a certain cell, or a certain Class of Service.
  • the maximum/minimum/average value of experienced latency is reported for all the possible/requested/available Class of Services.
  • one or more latency values is/are indicated as difference or delta compared to a reference for a given Class of Service I network node I cell.
  • the latency per Class of Service I network node I cell is expressed as a percentage e.g., from 0 to 100, indicating the percentage of users whose packets are associated to a certain Class of Service I network node I cell and whose transmissions were delayed by a time lower than or equal to or alternatively above a reference.
  • the reference can be a value of Packet Delay Budget (PDB) associated with the Class of Service I network node I cell e.g., the value of the maximum PDB of the PDB values of all the users/services whose traffic is carried by TNL resources of a certain Class of Service I network node I cell.
  • PDB Packet Delay Budget
  • the latency is expressed as a percentage e.g., from 0 to 100, indicating the percentage of packets and experiencing a latency or delay higher than or lower than, or within a reference, where the reference may be a value as a PDB.
  • TNL related information concerning the latency may also apply for other types of TNL related information, such as Round-Trip- Time, Packet error rate in downlink and uplink, Packet Loss in downlink and uplink, queuing delay in downlink and uplink etc.
  • the TNL related information may comprise information related to QoS monitoring at different granularities, such as per QoS flow per UE, per UE, per GTP-U path.
  • TNL related information may be:
  • the first RAN node 410 may send the updated values of transport resources to the one or more second RAN nodes 421 , 422.
  • TNL related information e.g., average, maximum, minimum.
  • the method may further comprise the following actions, which may be performed before Action 610:
  • the first RAN node 410 may send one or more messages to the one or more second RAN nodes 421 , 422 to request one or more of the following information: a) capability of reporting transport related information; b) capability of reporting a specific transport related information; c) capability of reporting a specific transport related information with a certain granularity; d) capability of reporting certain aggregation level for the transport related information; e) indications of one or more transport related information that the second RAN node can offer or report.
  • the first RAN node 410 may receive one or messages from the one or more second RAN nodes 421, 422, wherein the one or more messages comprises one or more indications indicating the requested information listed above.
  • a method performed by a second RAN node 421, 422 in a wireless communication network 400 for handling transport resources will be described with reference to Figure 7.
  • the second RAN node 421, 422 is served by a first RAN node 410.
  • the method comprises the following actions which may be performed in any suitable order and some actions may be optional.
  • the second RAN node 421, 422 receives a request from the first RAN node 410 to report transport related information, wherein the transport related information comprises a set of transport network metrics related to transport resource utilization.
  • the second RAN node 421, 422 sends the requested transport related information to the first RAN node 410.
  • the second RAN node 421 , 422 may send the requested transport related information by any one of the following:
  • the second RAN node 421 , 422 receives updated values of transport resources from the first RAN node 410 or a third transport network node 420.
  • the second RAN node 421 , 422 may perform the following actions. Action 701
  • the second RAN node 421 , 422 may receive one or more messages from the first RAN node 410, the one or more messages may comprise requests for reporting one or more of the following information: a) capability of reporting transport related information; b) capability of reporting a specific transport related information; c) capability of reporting a specific transport related information with a certain granularity; d) capability of reporting certain aggregation level for the transport related information; e) indications of one or more transport related information that the second RAN node 421 , 422 can offer or report.
  • the second RAN node 421 , 422 may send one or more messages to the first RAN node 410, by pre-configuring or by one or more request received from the first RAN node 410.
  • the one or more messages may comprise one or more of the following: a) indication indicating capability of reporting transport related information; b) indication indicating its capability of reporting a specific transport related information; c) indication indicating its capability of reporting a specific transport related information with a certain granularity; d) indication indicating its capability of reporting the transport related information with certain aggregation level; e) indications of one or more transport related information it can offer or report.
  • a method performed by a third transport network node 430 in a wireless communication network 400 for handling transport resources will be described with reference to Figure 8.
  • the second RAN node 421, 422 is served by a first RAN node 410.
  • the method comprises the following actions which may be performed in any suitable order and some actions may be optional.
  • the third transport network node 430 may receive a message from the first RAN node 410.
  • the message comprises a request or indication for requesting or indicating whether updating transport resources is needed for one or more second RAN nodes 421, 422.
  • the third transport network node 430 determines whether updating transport resources is needed for the one or more second RAN nodes 421 , 422 based on the reported transport related information from the one or more second RAN nodes 421 , 422 and provisioned capacity
  • the third transport network node 430 takes actions to update transport resources for the one or more second RAN nodes 421 , 422 based on the message.
  • the third transport network node 430 may take one or more of the following actions to update transport network resources for the one or more second RAN nodes:
  • the third transport network node 430 sends updated values of the transport resources to the first RAN node 410 or to the respective one or more second RAN nodes 421 , 422.
  • FIG. 9 shows a possible cloud implementation according to embodiments herein.
  • the solutions in E-UTRAN or NG-RAN will typically be in the Radio Control Function (RCF) in an eNB, gNB or ng-eNB which may be implemented in the centralized environment, i.e. the cloud. So the new functions or features RTA/RTE for handling transport resources may be implemented in RCF, and the RTA may be implemented in one or more distributed Radio Node (RNs).
  • RCF Radio Control Function
  • RNs Radio Node
  • the physical location of RCF may be close to the RN or in a data center or in another hardware entity somewhere in-between.
  • the first RAN node 410 is configured to perform any one of the Actions 601-660 described above.
  • the first RAN node 410 is configured to, by means of e.g. the transmitting module 1020 being configured to, send a request to one or more second RAN nodes 421 , 422 for requesting transport related information from the one or more second RAN nodes 421 , 422, wherein the transport related information comprises a set of transport network metrics related to their transport resource utilization (TRU).
  • TRU transport resource utilization
  • the first RAN node 410 is further configured to, by means of e.g. the transmitting module 1020 being configured to, send a request to a third transport network node (430) for requesting transport related information from the third transport network node (430), wherein the transport related information comprises a set of transport network metrics related to transport resource capacity (TRC).
  • TRC transport resource capacity
  • the first RAN node 410 is further configured to, by means of e.g. the determining module 1030 or processing module 1040 being configured to, determining or obtaining indication whether the TRU of the one or more second RAN nodes 421, 422 and/or the TRC provisioned by the third transport network node 430 need to be adjusted based on the reported TRU and provisioned TRC.
  • the second RAN node 421 , 422 is configured to perform any one of the Actions 701-730 described above.
  • the second RAN node 421 , 422 is configured to, by means of e.g. the receiving module 1110 being configured to, receive a request from the first RAN node 410 to report transport related information, wherein the transport related information comprises a set of transport network metrics related to transport resource utilization.
  • the second RAN node 421 , 422 is further configured to, by means of e.g. the transmitting module 1120 being configured to, send the requested transport related information to the first RAN node (410).
  • the second RAN node 421 , 422 is further configured to, by means of e.g. the receiving module 1110 being configured to, receives updated values of transport resources from the first RAN node 410 or a third transport network node 430.
  • the third transport network node 430 comprises modules as shown in Figure 12.
  • the third transport network node 430 comprises a receiving module 1210, a transmitting module 1220, a determining module 1230, a processing module 1240, a memory 1250 etc.
  • the third transport network node 430 is configured to perform any one of the Actions 810-830 described above.
  • the third transport network node 430 is configured to, by means of e.g. the receiving module 1110 being configured to, receive a message from a first RAN node 410, wherein the message comprises a request or indication for requesting or indicating whether updating transport resources is needed for one or more second RAN nodes 421, 422.
  • the third transport network node 430 is further configured to, by means of e.g. the a processing module 1240 being configured to, take actions to update transport resources for the one or more second RAN nodes 421 , 422 based on the message.
  • the third transport network node 430 is further configured to, by means of e.g. transmitting module 1220 being configured to, send updated values of the transport resources to the first RAN node 410 or to the respective one or more second RAN nodes 421 , 422.
  • the methods according to embodiments herein may be implemented through one or more processors, such as the processor 1060/1160/1260 in the first/second/third network nodes 410/421 ,422/430 together with 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 computer readable medium or a data carrier 1080/1180/1280 carrying computer program code 1070/1170/1270, as shown in Figures 10/11/12, for performing the embodiments herein when being loaded into the first/second/third network nodes 410/421, 422/430.
  • 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 or a cloud and downloaded to the first/second/third network nodes 410/421 , 422/430.
  • RTA and RTE are implemented in a multiplicity of network nodes to handle transport resources.
  • the RTA function in a network node e.g. the second RAN node RAN DU 421, RAN DU 422, monitors transport resource usages, e.g. TNL QoS, TNL available transport capacity etc., and reports related metrics, e.g. TNL parameters and/or TNL performances to the RTA/RTE function hosted in an RAN CU, e.g. the first RAN node 410.
  • transport resource usages e.g. TNL QoS, TNL available transport capacity etc.
  • related metrics e.g. TNL parameters and/or TNL performances to the RTA/RTE function hosted in an RAN CU, e.g. the first RAN node 410.
  • the RTA/RTE function in the first RAN node 410 collects from the third transport network node 430, e.g. T-SDNc, the provisioned/offered capacity relevant to the links between the first and second RAN nodes and compares the offered capacity and available capacity reported by the RTA function in the respective second RAN nodes, i.e. RAN DU 421, RAN DU 422. Based on the received information concerning the TNL resource usage, the RTA/RTE function in the first RAN node 410 determines or obtains an indication from the third transport network node 430 or another network node or entity or function within or outside the first RAN node 410, that new or updated TNL resources are needed.
  • the third transport network node 430 e.g. T-SDNc

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des nœuds de réseau et un procédé de gestion de ressources de transport dans un réseau de communication sans fil (400). Un premier nœud RAN (410) dessert un ou plusieurs seconds nœuds RAN (421, 422). Le premier nœud RAN (410) envoie une requête à un ou plusieurs seconds nœuds RAN (421, 422) pour demander des informations relatives au transport à partir du ou des seconds nœuds RAN (421, 422), dans lequel les informations relatives au transport comprennent un ensemble de métriques de réseau de transport liées à leur utilisation des ressources de transport. Le premier nœud RAN (410) envoie une requête à un troisième nœud de réseau de transport (430) pour demander des informations relatives au transport au troisième nœud de réseau de transport (430), dans lequel les informations relatives au transport comprennent un ensemble de métriques de réseau de transport liées à la capacité des ressources de transport. Le premier nœud RAN (410) détermine ou obtient une indication indiquant si l'utilisation des ressources de transport d'un ou plusieurs seconds nœuds RAN (421, 422) et/ou la capacité des ressources de transport fournie par le troisième nœud de réseau de transport (430) doivent être ajustées sur la base de l'utilisation des ressources de transport signalée et de la capacité des ressources de transport fournie.
PCT/SE2024/050237 2024-03-15 2024-03-15 Nœuds de réseau et procédés de gestion de ressources de transport dans un réseau de communication sans fil Pending WO2025193134A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/SE2024/050237 WO2025193134A1 (fr) 2024-03-15 2024-03-15 Nœuds de réseau et procédés de gestion de ressources de transport dans un réseau de communication sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/SE2024/050237 WO2025193134A1 (fr) 2024-03-15 2024-03-15 Nœuds de réseau et procédés de gestion de ressources de transport dans un réseau de communication sans fil

Publications (1)

Publication Number Publication Date
WO2025193134A1 true WO2025193134A1 (fr) 2025-09-18

Family

ID=97064382

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2024/050237 Pending WO2025193134A1 (fr) 2024-03-15 2024-03-15 Nœuds de réseau et procédés de gestion de ressources de transport dans un réseau de communication sans fil

Country Status (1)

Country Link
WO (1) WO2025193134A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080070587A1 (en) * 2002-09-18 2008-03-20 Nokia Corporation Method for managing radio resources and radio system
US20170290049A1 (en) * 2016-04-05 2017-10-05 Arizona Board Of Regents On Behalf Of Arizona State University Systems and methods for a smart gateway sdn-based backhaul architecture for small cells
US20180206148A1 (en) * 2015-10-21 2018-07-19 T-Mobile Usa, Inc. Coordinated RAN and Transport Network Utilization
WO2020204779A1 (fr) * 2019-03-29 2020-10-08 Telefonaktiebolaget Lm Ericsson (Publ) Distribution d'informations d'état de réseau de transport pour amélioration de procédure ran
US20220329491A1 (en) * 2018-04-23 2022-10-13 Huawei Technologies Co., Ltd. System, Function and Interface for Interconnecting Multi-Domain Network Slice Control and Management
US20220394523A1 (en) * 2017-09-27 2022-12-08 Zte Corporation Load information interaction method and device, processor and storage medium

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080070587A1 (en) * 2002-09-18 2008-03-20 Nokia Corporation Method for managing radio resources and radio system
US20180206148A1 (en) * 2015-10-21 2018-07-19 T-Mobile Usa, Inc. Coordinated RAN and Transport Network Utilization
US20170290049A1 (en) * 2016-04-05 2017-10-05 Arizona Board Of Regents On Behalf Of Arizona State University Systems and methods for a smart gateway sdn-based backhaul architecture for small cells
US20220394523A1 (en) * 2017-09-27 2022-12-08 Zte Corporation Load information interaction method and device, processor and storage medium
US20220329491A1 (en) * 2018-04-23 2022-10-13 Huawei Technologies Co., Ltd. System, Function and Interface for Interconnecting Multi-Domain Network Slice Control and Management
WO2020204779A1 (fr) * 2019-03-29 2020-10-08 Telefonaktiebolaget Lm Ericsson (Publ) Distribution d'informations d'état de réseau de transport pour amélioration de procédure ran

Similar Documents

Publication Publication Date Title
US12177714B2 (en) Method and device for data rate control in network slice in wireless communication system
US20220369204A1 (en) Method and device for providing service to user device by using network slice in communication system
KR101617978B1 (ko) 기저대역 신호 처리 클러스터
CN114009096A (zh) 应用工作负载路由和网络定义的边缘路由的互通
US20230413103A1 (en) Quality of service implementations for separating user plane
US12081415B2 (en) Enabling data exchange between first and second communication networks having different data communication capabilities
US10735173B2 (en) Carrier aggregation inter eNB activation
US11601230B2 (en) Systems and methods for intelligent differentiated retransmissions
Zanzi et al. On guaranteeing end-to-end network slice latency constraints in 5G networks
WO2025137636A1 (fr) Activation basée sur le trafic d'agrégation de porteuses
EP2375803B1 (fr) Entité de contrôleur de réseau d'accès radio multi-mode avec reconfiguration dynamique pour soutenir au moins deux technologies d'acces radio différentes
US20240031926A1 (en) Network slice subnet instance configuration
WO2025193134A1 (fr) Nœuds de réseau et procédés de gestion de ressources de transport dans un réseau de communication sans fil
KR102792095B1 (ko) 무선 통신 시스템의 네트워크 슬라이스에서 데이터 속도 제어를 위한 방법 및 장치
US20260067707A1 (en) End-to-end (e2e) network capacity planning methodology in a cellular network
US20260012855A1 (en) Dynamic user plane function (upf) scaling
GB2529143A (en) Carrier aggregation mode selection
US20250344230A1 (en) Dynamic access and mobility management function (amf) scaling
US20250392519A1 (en) Method for determining repartition of user equipment handled by wireless communication system
WO2025109621A1 (fr) Systèmes et procédés pour la fourniture d'un équilibrage de charge
WO2026083802A1 (fr) Dispositif de commande de communication, système de commande de communication, procédé de commande de communication et programme
KR20210056210A (ko) 무선 통신 시스템의 네트워크 슬라이스에서 데이터 속도 제어를 위한 방법 및 장치

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24929913

Country of ref document: EP

Kind code of ref document: A1