Method and node for delay management in a communication system
The method addresses delay management in 5G networks by dynamically adjusting delay profiles based on beamforming methods, enhancing communication efficiency and reducing failures and resource consumption.
Patent Information
- Application Number
- CN202410115536.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-06-06
- Filing Date
- 2024-01-26
- Publication Date
- 2024-12-06
AI Technical Summary
Current communication systems, particularly in 5G networks, face challenges in managing delays due to the use of multiple beamforming methods in O-RAN environments, leading to communication failures, throughput degradation, and increased resource consumption without considering the dynamic nature of beamforming methods.
A method for delay management in communication systems that involves reporting and configuring delay parameters based on beamforming methods, allowing for dynamic adjustment of delay profiles and configurations through management and control planes, ensuring synchronization and optimal resource utilization.
This approach enhances communication efficiency by adapting delay settings to current conditions, reducing communication failures, and optimizing resource usage by considering multiple beamforming methods, thereby improving system performance.
Smart Images

Figure CN119095154A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of communications, and more particularly, to a method and node for delay management in a communication system (for example, but not limited to, a communication system based on an Open Radio Access Network (O-RAN)). Background Art
[0002] The core network of communication systems (e.g., 5G (5th-Generation) systems) is undergoing a transformation. Since wireless access networks (e.g., 5G wireless access networks) have the characteristics of multiple services, large bandwidth, and high frequency bands, they may cause single-site coverage to become smaller, equipment complexity to increase, and network construction to increase, resulting in huge network costs and increased investment return risks. Considering the characteristics and requirements of wireless access networks, it is necessary to introduce new IT (Information Technology), CT (Communication Technology), and DT (Data Technology) integration research and development and design ideas in wireless access networks, which is in line with the macro evolution trend of the communications industry.
[0003] Based on this, operators are leading the creation of the O-RAN (open radio access network) industry alliance, proposing the two core visions of "open" and "intelligent", which is in line with the development trend of the communications industry and is another major network transformation led by operators. The O-RAN Alliance hopes to use big data, machine learning (ML) and artificial intelligence (AI) technologies to build an open and intelligent wireless network, while combining open standards, white box hardware and open source software to reduce wireless network costs. Summary of the invention
[0004] According to at least one embodiment of the present disclosure, a method executed by a first node in a communication system is provided, comprising: reporting a first delay parameter to a second node, wherein the first delay parameter is related to a beamforming method supported by the first node; receiving first configuration information related to delay management from the second node; and performing delay management based on the first configuration information.
[0005] In one implementation, the method further includes: receiving third configuration information related to delay management from the second node; and performing delay management based on the third configuration information.
[0006] In at least one embodiment of the present disclosure, the first delay parameter includes at least one delay parameter set, wherein each delay parameter set corresponds to one or more beamforming methods among the beamforming methods supported by the first node.
[0007] The method provided according to at least one embodiment of the present disclosure further includes: reporting at least one second delay parameter, where the at least one second delay parameter corresponds to all beamforming methods supported by the first node.
[0008] In at least one embodiment of the present disclosure, the first configuration information is determined based on the first delay parameter.
[0009] In at least one embodiment of the present disclosure, the first configuration information includes information related to a beamforming method.
[0010] The method provided according to at least one embodiment of the present disclosure further includes: sending second configuration information related to a delay parameter used by the first node to the second node, wherein the second configuration information includes information related to a beamforming method updated based on the first configuration information.
[0011] In at least one embodiment of the present disclosure, the first configuration information is configured by at least one of a user plane configuration file, a beamforming management configuration file, and a delay management configuration file of a management plane.
[0012] In at least one embodiment of the present disclosure, the second configuration information includes information related to a preset beamforming method or a non-updated beamforming method of the first node.
[0013] The method provided according to at least one embodiment of the present disclosure further includes: sending indication information to the second node indicating that the first node supports dynamic configuration of delay parameters based on time units.
[0014] In at least one embodiment of the present disclosure, the first node is an open radio access network O-RAN radio unit O-RU, and the second node is an O-RAN distribution unit O-DU.
[0015] According to at least one embodiment of the present disclosure, a method executed by a second node in a communication system is provided, comprising: receiving a first delay parameter from a first node, wherein the first delay parameter is related to a beamforming method supported by the first node; and sending first configuration information related to delay management to the first node.
[0016] In at least one embodiment of the present disclosure, the first delay parameter includes at least one delay parameter set, wherein each delay parameter set corresponds to one or more beamforming methods among the beamforming methods supported by the first node.
[0017] The method provided according to at least one embodiment of the present disclosure further includes: receiving at least one second delay parameter from the first node, where the at least one second delay parameter corresponds to all beamforming methods supported by the first node.
[0018] In at least one embodiment of the present disclosure, the first configuration information is determined by the second node based on the first delay parameter.
[0019] In at least one embodiment of the present disclosure, the first configuration information includes information related to a beamforming method.
[0020] The method provided according to at least one embodiment of the present disclosure further includes: receiving second configuration information related to a delay parameter used by the first node from the first node, wherein the second configuration information includes information related to a beamforming method updated by the first node based on the first configuration information.
[0021] In at least one embodiment of the present disclosure, the first configuration information is configured by at least one of a user plane configuration file, a beamforming management configuration file, and a delay management configuration file of a management plane.
[0022] In at least one embodiment of the present disclosure, the second configuration information includes information related to a default beamforming method or a non-updated beamforming method of the first node.
[0023] The method provided according to at least one embodiment of the present disclosure further includes: receiving indication information from the first node indicating that the first node supports dynamic configuration of delay parameters based on time units.
[0024] In at least one embodiment of the present disclosure, performing delay management based on the second configuration information includes: according to the indication information, indicating a delay parameter corresponding to the time unit to the first node based on the time unit through a control plane message.
[0025] In at least one embodiment of the present disclosure, the first node is an O-RU, and the second node is an O-DU.
[0026] According to at least one embodiment of the present disclosure, a method executed by a first node in a communication system is provided, comprising: reporting a third delay parameter to a second node, wherein the third delay parameter corresponds to all beamforming methods supported by the first node; and performing delay management using the third delay parameter.
[0027] According to at least one embodiment of the present disclosure, a method performed by a second node in a communication system is provided, comprising: receiving a third delay parameter from a first node, wherein the third delay parameter corresponds to all beamforming methods supported by the first node; and performing delay management using the third delay parameter.
[0028] According to at least one embodiment of the present disclosure, a method executed by a first node in a communication system is provided, comprising: reporting a first delay parameter to a second node, wherein the first delay parameter is related to a beamforming method supported by the first node; receiving first configuration information related to delay management from the second node; and performing delay management based on the first configuration information.
[0029] In one implementation, the first delay parameter includes information of at least one delay profile, wherein each delay profile corresponds to one or more of the beamforming methods or non-beamforming methods supported by the first node, or the delay profile information includes relevant information of the beamforming method corresponding to the delay profile or relevant information indicating that the delay profile does not correspond to the beamforming method.
[0030] In one implementation, the first delay parameter includes information of a delay profile supported by at least one endpoint of the first node, wherein the delay profile supported by the endpoint is associated with one or more beamforming methods or non-beamforming methods supported by the endpoint.
[0031] In one implementation, the information of the delay profile includes a delay profile identification ID.
[0032] In one implementation, the first delay parameter includes information of a delay profile obtained based on delay parameters of multiple beamforming methods corresponding to the first node.
[0033] In one implementation, the first configuration information includes information of a delay profile of at least one endpoint of the first node.
[0034] In one implementation, the information of the delay profile of at least one endpoint of the first node includes a delay profile ID corresponding to the at least one endpoint.
[0035] In an implementation manner, if the first configuration information does not include information about a delay profile, the first node performs delay management according to a preset delay profile.
[0036] In one implementation, the method further includes: sending information related to the beamforming method to the second node, the information including at least one of the following: computing resource consumption of the first node, channel quality, and a maximum number of data streams of the first node.
[0037] In one implementation, the method further includes: receiving a first message related to a delay profile update from a second node, the first message including sending time slot information, interval time information, and delay profile information of the first message; determining a time for switching the delay profile based on the sending time slot information and the interval time information; and when the determined time for switching the delay profile is reached, updating the delay profile of the corresponding endpoint based on the delay profile information.
[0038] In one implementation, the receiving window of the first node becomes smaller after the delay profile is updated or the data processing delay of the first node changes after the delay profile is updated.
[0039] In one implementation, the first message is a control plane message.
[0040] In one implementation, the method further includes: the first node sending maximum delay profile switching time information to the second node.
[0041] The interval time information is determined based on the maximum delay profile switching time.
[0042] In one implementation, the information of the delay profile includes a delay profile ID of a corresponding endpoint or a delay parameter corresponding to the delay profile of the corresponding endpoint.
[0043] In one implementation, the method further includes: before updating the delay profile of the corresponding endpoint, sending a message to the second node indicating that the delay profile update is ready to be processed.
[0044] In one implementation, the method further includes: receiving a second message related to delay profile update from a second node, the second message including information of an updated delay profile of at least one endpoint; and updating the delay profile of the corresponding endpoint based on the second message.
[0045] In one implementation, the receiving window of the first node becomes larger after the delay profile is updated.
[0046] In one implementation, the second message is a management plane message.
[0047] In one implementation, the first node is an open radio access network O-RAN radio unit O-RU, and the second node is an O-RAN distribution unit O-DU.
[0048] According to at least one embodiment of the present disclosure, a method executed by a second node in a communication system is provided, comprising: receiving a first delay parameter from a first node, wherein the first delay parameter is related to a beamforming method supported by the first node; and sending first configuration information related to delay management to the first node.
[0049] In one implementation, the first delay parameter includes information of at least one delay profile, wherein each delay profile corresponds to one or more of the beamforming methods or non-beamforming methods supported by the first node, or the information of the delay profile includes relevant information of the beamforming method corresponding to the delay profile or relevant information indicating that the delay profile does not correspond to the beamforming method.
[0050] In one implementation, the first delay parameter includes information of a delay profile supported by at least one endpoint of the first node, wherein the delay profile supported by the endpoint is associated with one or more beamforming methods or non-beamforming methods supported by the endpoint.
[0051] In one implementation, the information of the delay profile includes a delay profile identification ID.
[0052] In one implementation, the first delay parameter includes information of a delay profile obtained based on delay parameters of multiple beamforming methods corresponding to the first node.
[0053] In one implementation, the first configuration information includes information of a delay profile of at least one endpoint of the first node.
[0054] In one implementation, the information of the delay profile of at least one endpoint of the first node includes a delay profile ID corresponding to the at least one endpoint.
[0055] In one implementation, the method further includes: receiving information related to the beamforming method from the first node, the information including at least one of the following: computing resource consumption of the first node, channel quality, and a maximum number of data streams of the first node.
[0056] In one implementation, the method further includes: sending a first message related to delay profile update to the first node, wherein the first message includes sending time slot information, interval time information and delay profile information of the first message.
[0057] In one implementation, before sending a first message related to a delay profile update to the first node, it also includes: determining that a receiving window of the first node becomes smaller after the delay profile is updated or a data processing delay of the first node changes after the delay profile is updated.
[0058] In one implementation, the first message is a control plane message.
[0059] In one implementation, the method further includes: receiving maximum delay profile switching time information from the first node, and determining the interval time information based on the maximum delay profile switching time.
[0060] In one implementation, the information of the delay profile includes a delay profile ID of a corresponding endpoint or a delay parameter corresponding to the delay profile of the corresponding endpoint.
[0061] In one implementation, the method further includes receiving a message from the first node indicating that the delay profile update is ready to be processed.
[0062] In one implementation, the method further includes: sending a second message related to delay profile update to the first node, the second message including information of an updated delay profile of at least one endpoint.
[0063] In one implementation, before sending the second message related to the delay profile update to the first node, the method further includes: determining that the receiving window of the first node becomes larger after the delay profile is updated.
[0064] In one implementation, the second message is a management plane message.
[0065] In one implementation, the first node is an open radio access network O-RAN radio unit O-RU, and the second node is an O-RAN distribution unit O-DU.
[0066] According to at least one embodiment of the present disclosure, a first node in a communication system is provided, comprising: a transceiver configured to send and / or receive signals; and a controller configured to control the first node to execute the method described in at least one embodiment of the present disclosure.
[0067] According to at least one embodiment of the present disclosure, a second node in a communication system is provided, comprising: a transceiver configured to send and / or receive signals; and a controller configured to control the second node to execute the method described in at least one embodiment of the present disclosure.
[0068] According to at least one embodiment of the present disclosure, there is provided a storage medium on which instructions are stored. When the instructions are executed by a processor, the processor executes the method according to any one of the preceding claims. BRIEF DESCRIPTION OF THE DRAWINGS
[0069] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings of the embodiments of the present disclosure are briefly introduced below. Obviously, the drawings described below only relate to some embodiments of the present disclosure, and are not intended to limit the present disclosure. In the drawings:
[0070] Figure 1 The overall architecture of an O-RAN-based communication system according to some embodiments of the present disclosure is shown;
[0071] Figure 2 A schematic diagram showing an example of a delay management process (based on newly added parameters) according to some embodiments of the present disclosure;
[0072] Figure 3A schematic diagram showing an example of a management process for dynamic delay management update (a management process for dynamic management based on a delay profile) according to some embodiments of the present disclosure;
[0073] Figure 4 A schematic diagram showing an example of a management process of delay management according to some embodiments of the present disclosure;
[0074] Figure 5 A schematic diagram showing a simplified hardware structure of a first node according to an embodiment of the present disclosure;
[0075] Figure 6 A schematic diagram showing a simplified hardware structure of a second node according to an embodiment of the present disclosure;
[0076] Figure 7 A schematic diagram showing the calculation of the sending window and receiving window between the O-DU and the O-RU is shown;
[0077] Figure 8 A schematic diagram showing the O-RAN delay management process;
[0078] Fig. 9 A schematic diagram showing the delay configuration of the O-RU reporting different beamforming methods supported by each endpoint;
[0079] Fig.10 A schematic diagram showing an O-DU configuring a single delay profile used by each endpoint to an O-RU;
[0080] Fig.11 A schematic diagram showing a reconfiguration method of an O-DU to reconfigure a delay profile to an O-RU;
[0081] Fig.12 A schematic diagram showing another reconfiguration method for reconfiguring a delay profile from an O-DU to an O-RU. DETAILED DESCRIPTION
[0082] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution of the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings of the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the described embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.
[0083] Before carrying out the description of the following specific embodiments, it may be advantageous to elaborate on the definitions of certain words and phrases used throughout this patent document.The term "coupling" and its derivatives refer to any direct or indirect communication between two or more elements, regardless of whether these elements are in physical contact with each other.The terms "send", "receive" and "communication" and their derivatives cover direct and indirect communication.The terms "include" and "comprise" and their derivatives mean including but not limited to.The term "or" is inclusive, meaning and / or.The phrase "associated with..." and its derivatives mean including, included in, connected to, interconnected with, included in, connected to or connected with, coupled to or coupled with, can communicate with, collaborate with, interweave, juxtapose, approach, bind to or bind with, have, have... attributes, have... relationships or have relationships with, etc.The term "controller" means any device, system or part thereof that controls at least one operation.Such a controller can be implemented in hardware, or implemented in a combination of hardware and software and / or firmware.The functions associated with any particular controller can be centralized or distributed locally or remotely. The phrase "at least one of" when used with a list of items means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C. For example, "at least one of A, B, or C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.
[0084] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or parts thereof suitable for implementation in a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disc (CD), a digital video disc (DVD) or any other type of memory. "Non-transitory" computer-readable media excludes wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store and rewrite data later, such as rewritable optical discs or erasable memory devices.
[0085] The terms used to describe the embodiments of the present invention are not intended to limit and / or define the scope of the present invention. For example, unless otherwise defined, the technical terms or scientific terms used in this disclosure should be the common meanings understood by people with ordinary skills in the field to which the present invention belongs.
[0086] It should be understood that the words "first", "second" and the like used in the present disclosure do not indicate any order, quantity or importance, but are only used to distinguish different components. Unless the context clearly indicates otherwise, the singular forms "a", "an" or "the" and the like do not indicate quantity limitation, but indicate the presence of at least one.
[0087] As used herein, any reference to "one example" or "example", "one embodiment" or "embodiment" means that a particular element, feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment. The phrases "in one embodiment" or "in an example" appearing in different places in the specification do not necessarily all refer to the same embodiment.
[0088] As used herein, "a portion" of something means "at least some" of that thing, and thus may mean less than all of that thing or all of that thing. Thus, "a portion" of a thing includes the entire thing as a special case, i.e., the entire thing is an example of a portion of a thing.
[0089] As used herein, the term "set" means one or more. Thus, a set of items may be a single item or a set of two or more items.
[0090] In the present disclosure, in order to determine whether a specific condition is satisfied, expressions such as "greater than" or "less than" are used as examples, and expressions such as "greater than or equal to" or "less than or equal to" are also applicable and are not excluded. For example, a condition defined with "greater than or equal to" can be replaced with "greater than" (or vice versa), a condition defined with "less than or equal to" can be replaced with "less than" (or vice versa), and so on.
[0091] It will be further understood that the terms "include" or "comprises" and similar words mean that the elements or objects appearing before the word include the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connected" or "connected" and similar words are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "Up", "down", "left", "right", etc. are only used to indicate relative position relationships. When the absolute position of the object being described changes, the relative position relationship may also change accordingly.
[0092] The various embodiments discussed below for describing the principles of the present disclosure in this patent document are for illustration only and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any appropriately arranged wireless communication system.
[0093] Herein, depending on the type of network, the term "base station" or "BS" may refer to any component (or set of components) configured to provide wireless access to a network, such as a transmission point (TP), a transmission-reception point (TRP), an enhanced base station (eNodeB or eNB), a 5G base station (gNB), a macro cell, a femto cell, a WiFi access point (AP), or other wirelessly enabled devices. The base station may provide wireless access according to one or more wireless communication technologies, for example, 5G3GPP New Radio Interface / Access (NR), Long Term Evolution (LTE), Advanced LTE (LTE-A), High Speed Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. A person skilled in the art may understand that the "terminal" and "terminal device" used herein include both a device of a wireless signal receiver, which only has a wireless signal receiver without transmission capability, and a hardware device for receiving and transmitting, which has a hardware device capable of receiving and transmitting bidirectional communication on a bidirectional communication link. Such devices may include: cellular or other communication devices with single-line displays or multi-line displays or cellular or other communication devices without multi-line displays; PCS (Personal Communication System), which may combine voice, data processing, fax and / or data communication capabilities; PDA (Personal Digital Assistant), which may include a radio frequency receiver, pager, Internet / Intranet access, web browser, notepad, calendar and / or GPS (Global Positioning System) receiver; conventional laptop and / or palmtop computers or other devices, which have and / or include radio frequency receivers. "Terminal", "terminal device" as used herein may be portable, transportable, installed in a vehicle (air, sea and / or land), or adapted and / or configured to operate locally, and / or in a distributed form, operating at any other location on the earth and / or space. The "terminal" and "terminal device" used here can also be a communication terminal, an Internet terminal, a music / video playback terminal, for example, a PDA, a MID (mobile Internet device) and / or a mobile phone with music / video playback function, or a smart TV, a set-top box and other devices.
[0094] In the present disclosure, various embodiments will be described using terms adopted in some communication technologies (e.g., the Third Generation Partnership Project (3GPP) and the Open Radio Access Network (O-RAN)), but these embodiments are for illustrative purposes only. By modification, the embodiments of the present disclosure can also be easily applied to other communication systems.
[0095] Herein, unless otherwise specified, the terms "user", "user equipment (UE)" and "terminal" may be used interchangeably. In addition, unless otherwise specified, the terms "base station" and "cell" may be used interchangeably.
[0096] In this article, the E2 node can be one of a next-generation Node B (gNB), a distributed unit (DU), an evolved Node B (eNB), a gNB control unit (gNB-CU), an en-gNB, and an ng-eNB.
[0097] Some aspects of the present disclosure relate to delay configuration management of a communication node (e.g., O-RU). The following description will be given using O-RU as an example of a communication node that performs dynamic management of delay configuration. It will be understood that the principles of the technical solutions described in the present disclosure may also be applied to other types of communication nodes that perform delay configuration management. In the description of the present disclosure, operations performed between a first node and a second node for delay management are mainly described, wherein the first node is, for example, an O-RU and the second node is, for example, an O-DU.
[0098] Some or all of the delay parameters related to the O-RU operation may be referred to as an O-RU delay profile. Since the delay characteristics of the O-RU may vary depending on the air interface properties and the beamforming method, multiple groups of delay parameters are provided according to different combinations of one or more of the subcarrier spacing (SCS), channel bandwidth, and beamforming method, and some or all of the delay parameters in each group of delay parameters may be referred to as a delay profile.
[0099] In the description of the present disclosure, for the convenience of description, descriptions such as "delay parameters", "delay profiles", and "delay parameter sets" are used. It can be understood that they are merely examples of names for parameters used for delay management, to indicate parameters, profiles, or configuration information related to delay management. Therefore, it can be understood that other names may be used to indicate such parameters, profiles, or configuration information. For example, descriptions such as "delay configuration", "delay file", "delay configuration parameters", "delay configuration parameter sets", "delay configuration information", "delay profile", "delay distribution", and "delay spectrum" may also be used, all of which are used to indicate parameters related to the principles of the present disclosure and used for delay management.
[0100] Delay management is a key process in the open fronthaul interface (between O-DU and O-RU) in the ORAN architecture. The data flow between O-DU and O-RU includes user plane, control plane and synchronization plane message flow. In order to ensure the correct sending and receiving of these messages, the appropriate sending window and receiving window need to be correctly calculated using the delay parameters, as defined in Figure 7 As shown:
[0101] Correct send / receive window calculation Ttransmit_recv_win = f(T12, T2a, Ta3, T34)
[0102] Delay management process such as Figure 8 As shown, the following steps are included:
[0103] Step 1: The O-RU reports the delay parameters to the O-DU via the management plane. When requested, all O-RUs shall send a table of static “predefined” values of the delay parameters for different supported combinations of subcarriers and channel bandwidths via the management plane interface.
[0104] Step 2: Transmit and receive window determination in O-DU,When calculating the O-DU transmit and receive windows in the timing domain, the O-DU shall use the delay configuration parameters applicable to each O-RU based on the air interface properties used by the O-RU in the specific network configuration.
[0105] For example, the delay parameters (or interface parameters) reported by the O-RU are as follows:
[0106]
[0107] Current delay management does not take into account the multiple beamforming methods supported by the O-RU, which can lead to communication delays (e.g., failure of URLLC scenarios), system performance degradation (e.g., throughput degradation), and even system and communication failures.
[0108] Currently, ORAN supports four beamforming (BF) methods, and different beamforming methods correspond to different BF weight calculation processes. For example, depending on whether the weight calculation is performed on the O-DU side or the O-RU side, there can be different BF weight calculation processes. If the weight calculation is performed in the O-RU, the T2a (O-RU data processing delay) related parameters will be increased, further affecting the O-RU receiving window. The current O-RAN technology only supports reporting a set of delay parameters, but endpoints can support different BF methods, which may result in larger or smaller Ttrasmit_recv_win. Because a larger O-RU receiving window means that more buffers are required, occupying more computing resources, resulting in a decrease in system performance such as throughput, while a smaller O-RU receiving window may cause packet loss and retransmission, resulting in longer communication delays or even communication failures.
[0109] CU plane applications need to be uniquely associated with a specific data flow. This association is achieved by defining an O-RU "processing element", which can then be associated with a specific control plane / user plane (C / U plane) endpoint address (where each O-RU can have multiple endpoints).
[0110]
[0111]
[0112] As shown in the table, if the O-RU reports a set of BF2-related delay configuration parameters, but endpoint 1 works under BF1, this will result in a smaller O-RU receiving window (820-609=211us replacing 669-259=410us) If the O-RU reports a set of BF1-related delay configuration parameters, but endpoint 2 works under BF2, this will result in a larger O-RU receiving window (669-259=410us replacing 820-609=211us). Therefore, if the O-RU is required to support multiple BF methods at the same time, reporting one delay distribution without considering multiple BF methods will degrade performance.
[0113] According to at least one embodiment of the present disclosure, a method and apparatus for performing delay management by a fronthaul interface in a communication system according to multiple beamforming methods is provided. The method includes: obtaining information related to delay management of an O-RU under different beamforming methods; selecting different beamforming methods for the O-RU in the O-DU; and the O-RU feeding back the result of the O-DU beamforming method setting.
[0114] The method according to at least one embodiment of the present disclosure may consider delay management under multiple beamforming methods supported by the O-RU. Since the delay profile of the O-RU may vary depending on the beamforming method adopted by the O-RU, when requested, the O-RU may send a parameter value table of the corresponding delay profile for different supported beamforming methods through the management plane interface. Based on different beamforming methods, the O-RU can be configured to use a delay profile corresponding to the beamforming method, thereby solving the problem that the O-RU cannot support the use of different O-RU delay parameters under multiple beamforming methods, and further achieving the effect of optimizing the O-RU cache and improving the utilization of O-DU resources.
[0115] According to one aspect of the present disclosure, a method for performing O-RU delay management in an O-RAN-based communication system may include: a network function (e.g., an O-DU node) obtains information related to delay management based on different beamforming methods supported by the O-RU through a functional interface between the network function (e.g., the O-DU node) and the O-RU, for example, the O-DU may receive reporting information, for example, information reported by the O-RU; and the O-DU sends policy information through a corresponding interface. Information reporting may include reporting of information related to O-RU delay management. The policy information may indicate a change in the beamforming method.
[0116] According to one aspect of the present disclosure, different delay management strategies may include one of the following:
[0117] A method for delay management based on newly added management plane parameters.
[0118] A method for dynamically managing delay based on time slots based on control plane configuration beamforming method.
[0119] ·Delay management method based on unchanged interface.
[0120] According to one aspect of the present disclosure, the received reporting information may include at least one of the following: a delay parameter (or delay profile) of the O-RU, for example, a delay parameter of the O-RU corresponding to different beamforming methods; a beamforming method selected by the O-RU for use and / or a delay parameter corresponding to the beamforming method. For example, throughout the text, a delay parameter or delay profile reported by the O-RU to the O-DU may be referred to as a first delay parameter.
[0121] According to one aspect of the present disclosure, the O-RU performs configuration including selecting a beamforming method to be used. The configured beamforming method may be one or multiple beamforming methods may be supported simultaneously. Configuring the beamforming method includes at least one of the following: updating the configuration based on a new beamforming method parameter added to the management plane; updating the configuration based on a new remote call interface model added to the management plane; dynamically updating the configuration based on the control plane beamforming method;
[0122] According to one aspect of the present disclosure, different beamforming methods may include at least one of the following: a beamforming method of a predefined beam; a dynamic beamforming method based on beam weights; a dynamic beamforming method based on beam characteristics; and a beamforming method based on channel state information.
[0123] The embodiments of the present disclosure include at least the following:
[0124] 1. The O-RU supports reporting of multiple separate delay configuration parameters corresponding to different supported beamforming methods. Each set of delay configuration parameters can be associated with one or more beamforming methods, or with a no beamforming method (No BF).
[0125] - Use a delay profile identifier (e.g., delay-profile-id) to identify delay configuration parameter combinations with the same value. Each delay-profile-id can be associated with one or more beamforming methods or no beamforming method.
[0126] The mapping relationship between profile-id and beamforming method may be fixed. In addition, multiple beamforming methods may have the same delay configuration parameters.
[0127] - The ability to report the delay configuration parameters for each endpoint. The current beamforming method may be endpoint-based, and different endpoints may support different beamforming methods.
[0128] 2. The O-DU can select a set of delay configuration parameters and notify the O-RU
[0129] - An endpoint can support multiple beamforming methods, but each endpoint can use only one delay configuration parameter. Otherwise, it is difficult for the O-RU to dynamically determine the delay configuration parameter to be applied because the entire control plane message needs to be parsed to know the beamforming method used.
[0130] 3. O-DU can dynamically update the beamforming method and reconfigure the corresponding delay profile
[0131] - The beamforming method may change for reasons such as energy saving. The O-DU can use different beamforming methods dynamically.
[0132] 4. O-DU can configure the switching time for O-RU to ensure switching synchronization without deactivating all carriers
[0133] -Currently reconfiguration of the delay profile requires disabling all carriers of the O-RU.
[0134] In this case, frequent dynamic updates have a serious impact on O-RU services.
[0135] Throughout the text, the delay configuration parameters notified or sent by the O-DU to the O-RU may be referred to as delay management related first configuration information, for example.
[0136] Here are some examples of solutions:
[0137] 1. The O-RU reports the delay configurations of different beamforming methods supported by each endpoint, for example, the first delay parameter includes information about the delay profiles supported by at least one endpoint of the first node, such as Fig. 9 For example, the O-RU may report a corresponding delay profile identifier (id) for each endpoint.
[0138] 2. The O-DU configures the O-RU with a single delay profile for each endpoint, e.g. Fig.10 shown.
[0139] For each endpoint, when the supported beamforming method is updated, the O-DU reconfigures the delay profile to the O-RU according to the updated beamforming method of the endpoint. When reconfiguring the delay parameters:
[0140] - Option 1: Deactivate the carrier or related endpoints to set the new delay configuration to the O-RU endpoint for synchronization.
[0141] - Option 2: Set a new delay configuration without deactivating the carrier, and keep the synchronization between O-RU and O-DU through the transmission delay time and the maximum delay switching time.
[0142] According to the method of the embodiment of the present disclosure, the second node (e.g., O-DU) can perform delay management on the first node according to the beamforming method supported by the first node (e.g., O-RU), so that the delay setting between the first node and the second node can be better adapted to the current communication environment or communication status, thereby improving the communication efficiency. In addition, according to the method provided by the embodiment of the present disclosure, the second node can use simple signaling to configure the first node with appropriate (e.g., optimal) delay configuration parameters according to the actual situation of the first node, and dynamically configure the updated delay configuration parameters for the first node when the actual situation changes (e.g., when the situation related to the use of the beamforming method changes). In addition, according to the method of the embodiment of the present disclosure, the first node and the second node can be synchronized to update the delay configuration parameters. In addition, according to the embodiment of the present disclosure, the second node can also use a synchronous or asynchronous method to update the delay configuration parameters according to the actual situation of the delay configuration parameter update for the first node.
[0143] The following further describes example embodiments of the present disclosure in conjunction with the accompanying drawings.
[0144] Figure 1 The overall architecture of an O-RAN based communication system according to some embodiments of the present disclosure is shown.
[0145] The overall architecture of the O-RAN-based communication system is based on the centralized unit (CU) / distributed unit (DU) architecture and functional virtualization of the radio access network (e.g., base station), introduces reference designs for open interfaces and open hardware, and uses artificial intelligence to optimize wireless control processes.
[0146] The base station reference architecture in O-RAN is as follows Figure 1As shown, the base station in the figure can be a gNB (next generation NodeB, NR base station) supporting 5G NR (New Radio) or an eNB (evolved NodeB, LTE base station) supporting 4G LTE (Long Term Evolution). The reference architectures of gNB and eNB are slightly different, but have no impact on the content of this disclosure, so gNB and eNB are not distinguished. This disclosure also does not involve other functional entities outside the base station in O-RAN and their interfaces with the base station, so they are not shown in the figure. The following will briefly introduce Figure 1 Some components of the base station reference architecture in O-RAN are shown:
[0147] O-CU (O-RAN Central Unit) 101: A logical node including O-CU-CP (O-RAN Central Unit Control Plane) and O-CU-UP (O-RAN Central Unit User Plane), wherein O-CU-CP is a logical node including RRC (Radio Resource Control) and PDCP (Packet Data Convergence Protocol) control planes, and O-CU-UP is a logical node including PDCP user plane and SDAP (Service Data Adaptation Protocol).
[0148] O-DU (O-RAN Distributed Unit) 102: includes RLC (Radio Link Control), MAC (Media Access Control), High-PHY (High Physical layer) and logical nodes with specific functions in O-RAN.
[0149] MAC 102-1: 3GPP functional layer, responsible for multiplexing MAC SDU (Service Data Unit) from one or more different logical channels into TB (Transport Block), and sending the TB to the physical layer through the transport channel; and demultiplexing the TB delivered from the physical layer from the transport channel into MAC SDU of one or more different logical channels; and other functions such as error correction through HARQ (Hybrid Automatic Repeat reQuest). It is also a logical functional entity on the gNB / eNB, called a scheduler, which dynamically allocates time and frequency resources for the uplink and downlink air interfaces.
[0150] High-PHY 102-2: After the 3GPP functional layer physical layer is split, the function processed in the O-DU is responsible for encoding / decoding, channel estimation, modulation / demodulation, scrambling / descrambling, etc.
[0151] O-DU CUS-Plane Application (O-DU Control, User, Synchronization PlaneApplication, control plane / user plane / synchronization plane application in O-DU, referred to as O-DU application in this disclosure) 102-3: O-DU logical function, responsible for creating and sending C-Plane (Control-Plane), U-Plane (User-Plane) and S-Plane (Synchronization-Plane) messages to O-RU (O-RAN Radio Unit) on the fronthaul interface, or receiving and processing C-Plane (Control-Plane), U-Plane (User-Plane) and S-Plane (Synchronization-Plane) messages from O-RU. Among them, the control plane message carries the relevant information for controlling the user plane message (such as scheduling and beamforming indication), the user plane message carries the time-frequency domain I / Q (In-phase / Quadrature) data, and the synchronization plane message is used to achieve time-frequency synchronization between O-DU and O-RU.
[0152] O-DU M-Plane (O-DU Management Plane) 102-4: O-DU logical function, based on NETCONF / YANG (Network Configuration / Yet Another Next Generation, network configuration protocol / YANG data modeling language) to initialize O-RU, perform software management, configuration management, performance management, fault management, file management, etc.
[0153] OFH I / F (O-RAN Open Fronthaul interface) 103: includes CUS-Plane and M-Plane interfaces, which can be based on eCPRI (enhanced Common Public Radio Interface) or IEEE (Institute of Electrical and Electronics Engineers) 1914.3 interfaces, and the content transmitted on the interface complies with O-RAN CUS-Plane and M-Plane.
[0154] O-RU (O-RAN Radio Unit) 104: gNB / eNB physical node in O-RAN, including Low-PHY (Low Physical layer) and RF Chain.
[0155] O-RU CUS-Plane Application (O-RU Control, User, Synchronization PlaneApplication, control plane / user plane / synchronization plane application in O-RU, referred to as O-RU application in this disclosure) 104-1: O-RU logical function, responsible for creating and sending C-Plane, U-Plane and S-Plane messages to O-DU or receiving and processing C-Plane, U-Plane and S-Plane messages from O-DU on the fronthaul interface.
[0156] Low-PHY 104-2: The function that is processed in the O-RU after the 3GPP functional layer physical layer is split, and is responsible for FFT / iFFT (Fast Fourier Transformation / Invert Fast Fourier Transformation), analog beamforming, digital beamforming, digital-to-analog / analog-to-digital conversion, etc.
[0157] O-RU M-Plane (O-RU Management Plane) 104-3 is an O-RU logical function, which is managed by O-DU M-Plane and reports capabilities to O-DU in the initialization phase to inform O-DU which optional capabilities the O-RU supports.
[0158] Currently, secure, synchronous, and low-energy O-RU deployments are being considered. In the current case, O-RU only supports one delay configuration in terms of latency. Since the delay parameter between O-DU and O-RU is an important parameter for defining the send and / or receive buffer window and the optimization of the buffer operation at the receiving end.
[0159] O-RAN delay management supports only one set of delay configurations for each O-RU with different BF methods. The delay management steps are as follows:
[0160] 1. O-RU reports delay configuration to O-DU through management
[0161] 2. The O-DU determines the send and receive windows. When calculating the O-DU send and receive windows, the delay profile applicable to each O-RU is used.
[0162] In this way, the O-RU only supports one delay configuration, and the O-RU cannot select different delay configurations according to different beamforming methods. Based on the current intuitive solution, when the O-RU supports multiple BF methods and the BF methods can be changed frequently, the O-RU reports a delay configuration based on the worst case considering multiple BF methods.
[0163] For example, the O-RU supports BF1 and BF2, where endpoint 1 supports BF1 and endpoint 2 supports BF2. The worst-case delay configuration is reported for transmission and reception window calculation. For endpoint 1: The O-RU reception window is calculated based on the worst-case of the two BFs, and the O-RU reception window length = T2a_max_cp_dl-T2a_min_cp_dl. That is, the O-RU reception window length replaces the 820–609 = 211u required when only BF1 is supported with the worst-case 1035-609 = 426us. This makes the set O-RU reception window larger than the actual requirement, thereby requiring more buffers and more computing resources, which will result in more buffers being required, system performance degradation, and network devices (e.g., O-RU) caching windows that are too long, resulting in waste of O-RU buffers, and increasing the processing load of the O-DU due to delay requirements, resulting in the O-DU being unable to effectively schedule resources, thereby reducing the performance of the communication system. For example, the delay parameter tcp-adv-dl (value 475us) in the beamforming method based on channel state information is generally larger than the tcp-adv-dl (value 125us) in the beamforming method based on real-time information. Therefore, the O-DU needs to send the control plane message for the beamforming based on channel state information earlier, so the O-DU also needs to generate the control plane message earlier to meet the downlink tcp-adv-dl requirement, which will hinder the efficient resource scheduling of the O-DU and cause the system performance to degrade, such as the throughput to degrade.
[0164] In order to at least solve the above problems, some aspects of the present disclosure provide improved methods for determining O-RU delay management. For example,
[0165] 1. The O-RU of the present disclosure can report its ability to support multiple delay profiles based on the BF method when supporting multiple BF methods, such as reporting a first delay parameter to the first node. Since the BF method is based on multiple endpoints inside the O-RU, the delay configuration parameters can be managed by endpoint. Multiple BF methods can have the same delay parameters. Each set of delay parameters (also referred to as each delay profile) can be associated with one or more BF methods, and can also be associated with not supporting the BF method (No BF);
[0166] 2. The O-DU of some aspects of the present disclosure can comprehensively analyze the optimal beamforming method that the communication system should currently use, thereby notifying the O-RU to use the information related to delay management (e.g., delay profile) corresponding to the optimal beamforming method, such as the second node sending the first configuration information related to delay management to the first node.
[0167] Compared with the method in which the O-RU has only one delay profile, some embodiments of the present disclosure can make full use of the ability of the O-RU to support different beamforming methods, and accordingly perform delay management with full coverage of delay configuration, thereby achieving performance improvement of the O-RU and O-DU. Figure 2 A diagram depicting an example of a management flow (based on the management plane) for determining O-RU delay management.
[0168] 3. In order to dynamically change the BF method used during operation, the O-DU can update the selected delay configuration accordingly. The O-DU can dynamically update the BF method and reconfigure the corresponding delay configuration. For example, the beamforming method may change for reasons such as energy saving. The O-DU can dynamically use different BF methods. And the O-DU can configure the switching time (e.g., delay profile switching time or BF method switching time) for the O-RU to ensure switching synchronization without affecting the O-RU's currently ongoing business.
[0169] Figure 2 A schematic diagram showing an example of a delay management process (based on newly added parameters) according to some embodiments of the present disclosure. Figure 2 The described methods are only examples, and some steps may be omitted or some new steps may be added.
[0170] like Figure 2As shown in (a), in step S201, the O-RU reports the first information (including delay parameters) related to delay management. For example, the first information may also be referred to as the first delay parameter. For example, the O-RU may support one beamforming method or multiple different beamforming methods, and may report delay profiles corresponding to different beamforming methods, and the delay profile may include at least one delay parameter supported by the O-RU corresponding to the beamforming method. For example, the O-RU transmits the first information related to delay management via the uplink transmission of the management plane O-FH interface between the O-RU and the O-DU. For example, the first information includes: supported beamforming methods, such as one or more of a beamforming method based on channel state information, a beamforming method of a predefined beam, a dynamic beamforming method based on beam weights, a dynamic beamforming method based on beam characteristics, and the like. In one implementation, the information may also include an O-RU delay profile corresponding to the beamforming method.
[0171] In addition, if Figure 2 As shown in (b), the delay management between the O-RU and the O-DU may include steps S201-1, S201-2, S201-3, S202-1, S203-1, and S204-1. For example, through steps S201-1 to S201-3, the O-RU reports the delay parameters based on the BF method to the O-DU through a management plane message. In step S201-3, the message sent by the O-RU to the O-DU may include the maximum window switching time (or maximum profile switching time) supported by the O-RU.
[0172] - If the O-RU supports multiple beamforming methods, the O-RU can use delay-profile-
[0173] id is used to send the corresponding values of the parameters corresponding to the delay profile for different supported beamforming methods.
[0174] - Each delay-profile-id associates one or more BF methods or no-BF method with a delay parameter set (or delay profile), and the mapping relationship between delay-profile-id and beamforming method may be fixed.
[0175] - During the initial startup phase, the O-RU may inform each static endpoint of the supported delay profiles in the endpoint type (using the delay profile ID) in the capability report.
[0176] In step S202-1, the O-DU may perform some operations related to the configuration of the sending and receiving windows, such as Figure 2In step S203-1, the O-DU may notify the O-RU of the configured delay configuration. In step S204-1, the O-RU may reply to the O-DU. For example, the reported delay profile includes but is not limited to at least one of the following delay parameters: t2a-min-up, t2a-max-up, t2a-min-cp-dl, t2a-max-cp-dl, tcp-adv-dl, ta3-min, ta3-max, t2a-min-cp-ul, t2a-max-cp-ul.
[0177] When considering the downlink data direction, these parameters include:
[0178] - T2a_min: corresponds to the minimum O-RU data processing delay between receiving the last data sample over the fronthaul interface and sending the first IQ sample at the antenna.
[0179] - T2a_max: corresponds to the earliest allowed time that a data packet is received before the first IQ sample corresponding to the antenna transmission.
[0180] - Using the above parameters, (T2a_max–T2a_min): The difference between these two parameters corresponds to the O-RU reception window range.
[0181] - T2a_min_cp_dl: corresponds to the minimum O-RU data processing delay between receiving a downlink real-time control plane message over the fronthaul interface and sending the corresponding first IQ sample at the antenna.
[0182] - T2a_max_cp_dl: corresponds to the earliest allowed time for receiving a downlink real-time control message before the first IQ sample corresponding to the antenna is transmitted.
[0183] -Tcp_adv_dl: corresponds to the time difference (advance) between the receiving window of the downlink real-time control message and the receiving window of the corresponding IQ data message.
[0184] -Tda: corresponds to the time difference between the DL signal output from the O-RU antenna connector and the transmission over the air.
[0185] The latency parameters related to O-RU operation in the uplink data direction include:
[0186] - Ta3_min: corresponds to the minimum O-RU data processing delay between reception of IQ samples at the antenna and transmission of the first data sample over the fronthaul interface.
[0187] - Ta3_max: corresponds to the maximum O-RU data processing delay between reception of an IQ sample at the antenna and transmission of the last data sample over the fronthaul interface.
[0188] - Using the above parameters, (Ta3_max–Ta3_min): The difference between these two parameters corresponds to the O-RU transmission window range.
[0189] - T2a_min_cp_ul: Minimum O-RU data processing delay between receiving a real-time uplink control plane message over the fronthaul interface and receiving the first IQ sample at the antenna.
[0190] - T2a_max_cp_ul: Earliest allowed time for receiving a real-time uplink control message before the first IQ sample corresponding to the antenna is received.
[0191] - Tau: corresponds to the time difference between over-the-air reception and the input UL signal at the antenna connector of the O-RU.
[0192] The method for the O-RU to report the first information related to delay management may include at least one of the following:
[0193] Method 1: The delay profile can be reported in the o-ran-delay-management.yang file through the management plane. By defining new parameters, multiple groups of delay profiles can be reported according to the supported beamforming methods.
[0194] Delay-profile-id is used to identify delay configuration combinations (or delay profiles) with the same value, and each delay profile can be associated with one or more BF methods. For example, the delay parameter values of each (e.g., each BF method) can be reported according to different BF methods. In order to report the respective values according to different BF methods, a new parameter (e.g., "delay-profile-id") can be introduced to report the delay profile of each BF method. Since each delay-profile-id can be associated with one or more BF methods or no BF method, the O-RU can report multiple delay profiles identified using "delay-profile-id". For example, the mapping relationship between delay-profile-id and BF method can be fixed. If the O-RU wants to use multiple BF methods at the same time, and their corresponding delay configurations are different, the O-RU can generate a delay configuration that can indicate the simultaneous use of multiple BF methods.
[0195] To maintain backward compatibility, the BF method is an optional parameter. Not explicitly declaring support for any BF method can be assumed to support all existing BF methods.
[0196]
[0197] For example, each O-RU has multiple endpoints, and different endpoints may support different BF methods. The O-RU can report 4 different delay profiles, as shown below:
[0198] delay-profile-id=0 indicates no explicit association with any BF method;
[0199] delay-profile-id=1 or 2 indicates the corresponding value of a BF method;
[0200] delay-profile-id=3 indicates that both BF1 and BF2 are used.
[0201] The O-RU may report the delay profiles supported by each endpoint, for example: endpoints 1-4: delay-profile-id = 0 and 1; endpoints 5-8: delay-profile-id = 0, 1, 2, 3; the O-DU may select only the delay profile of each endpoint.
[0202]
[0203] The new delay profile can be defined as ru-delay-profile-per-bfmethod of list type but is not limited to this. The parameter beamforming-method is added to the new delay profile to indicate the beamforming method corresponding to the current delay profile. The parameter beamforming-method type can be a list list. If the delay profiles corresponding to multiple beamforming methods are the same, only one set of delay parameters (i.e., one delay parameter set or one delay profile) can be reported for these beamforming methods. When the delay parameters supported by all beamforming methods are the same or the ORU does not support beamforming, the parameter beamforming-method can be optional.
[0204]
[0205] In one implementation, the O-RU may report a delay profile corresponding to each beamforming method supported by the O-RU. The node beamforming-method may be an enumeration type, and each beamforming method corresponds to a delay profile (which includes a set of delay parameters). An example is as follows:
[0206]
[0207] In one implementation, considering that the delay characteristics of the O-RU may vary according to different combinations of one or more of the subcarrier spacing (SCS), channel bandwidth, and beamforming method, a delay parameter table may be provided according to different combinations of one or more of the subcarrier spacing (SCS), channel bandwidth, and beamforming method. The O-RU may send a delay profile value table for different combinations of one or more of the supported subcarrier spacing, channel bandwidth, and beamforming method through a management plane interface, and a new parameter bandwidth-scs-bf-delay-state is added. The parameter beamforming-method (beamforming method) is used as one of the type "key" statements in bandwidth-scs-bf-delay-state, and the subcarrier spacing (SCS) and / or channel bandwidth are used as the combined value of the specified "key" to represent the new parameter.
[0208]
[0209] Method 2: Delay parameters can be reported in groups according to their characteristics. For example, in one implementation, some delay parameters remain unchanged under different beamforming methods, while other delay parameters vary according to different beamforming methods. Delay parameters that remain unchanged under different beamforming methods, such as t2a-min-up and t2a-max-up, which remain unchanged under the beamforming method based on channel state information and the dynamic beamforming method based on beam weights, can be defined as a new group " ru-delay-profile ", which is reported only once. On the other hand, the delay parameter groups that change according to different beamforming methods can be defined as a new "list" ru-delay-profile-per-bfmethod To declare, and add "key" to the parameter to instantiate the delay parameters under multiple different beamforming methods. The example is as follows:
[0210]
[0211] In step S202, the O-DU may select a beamforming method for delay management based on the reported delay profile and weight accuracy or O-RU capability, such as a beamforming method to be configured for the O-RU. The selection process is internally implemented. For example, the O-DU may change the beamforming method and the delay profile under the method based on the channel feedback information, such as at least one delay parameter corresponding to the beamforming method. In one implementation, the O-DU selects a beamforming method based on the delay profile reported by the O-RU in step S201.
[0212] In step S203, after the O-DU obtains the first information related to delay management including multiple beamforming methods supported by the O-RU, the O-DU can select the optimal beamforming method through a certain strategy, and configure the selected one or more beamforming methods to the O-RU. The O-DU can configure the changed beamforming method to the O-RU through the O-FH interface.
[0213] Regarding the delay management between O-RU and O-DU:
[0214] 1. When the O-RU indicates that it supports multiple delay profiles based on different beamforming methods, the O-DU can select a delay profile ID based on different use cases. Add a new configuration parameter in the management plane interface, and the O-DU configures the delay-profile-id based on the beamforming method it supports. Each endpoint can only be configured with one delay-profile-id.
[0215] 2. When delay-profile-id is configured, O-RU shall use the delay parameter values corresponding to delay-profile-id. If O-DU does not configure any selected configuration ID to O-RU,
[0216] The O-RU will run with the default latency profile value.
[0217] For example, each O-RU has multiple endpoints, and different endpoints may support different BF methods. Based on the process of steps S201-1 to S201-3, the O-RU reports 4 different delay configuration parameters, such as:
[0218] delay-profile-id=0:No BF
[0219] delay-profile-id=1:BF 1
[0220] delay-profile-id=2:BF 2
[0221] delay-profile-id=3:BF1,BF2
[0222] Where delay-profile-id=0 indicates no explicit association with any BF method;
[0223] delay-profile-id=1 or 2 indicates the corresponding value of a BF method;
[0224] delay-profile-id=3 indicates the corresponding delay profile when BF1 and BF2 are used at the same time. The O-RU can report the delay profiles supported by each endpoint, for example: endpoints 1-4: delay-profile-id=0 and 1; endpoints 5-8: delay-profile-id=0,1,2,3;
[0225] At this time, O-DU can be configured as follows according to different requirements:
[0226] 1. The O-DU wants the O-RU to use a set of delay configurations:
[0227] -DU does not configure any delay profile id. In this case, O-RU uses the default value, for example
[0228] delay-profile-id=3;
[0229] 2. Only one BF method (BF 1) is used during O-DU operation.
[0230] - O-DU configures each endpoint of O-RU with delay-profile-id = 1. Each endpoint will use the delay parameters corresponding to delay-profile-id = 1;
[0231] 3. Both BF methods can be used during O-DU operation:
[0232] -O-DU configures two types of endpoints, and O-DU sets delay for four of them.
[0233] profile-id 1: Messages using beamforming 1 are transmitted to these four endpoints.
[0234] -O-DU sets delay-profile-id 2 for the remaining 4 endpoints: messages related to beamforming 2 are transmitted to these 4 endpoints.
[0235] -O-DU configures all endpoints to support delay-profile-id=3;
[0236] In an implementation manner, the configuration content of configuring the beamforming method includes one or more selected beamforming methods.
[0237] For example, in at least one embodiment of the present disclosure, the beamforming method configuration is configured to the O-RU through a management plane model.
[0238] The O-DU can configure the beamforming method by at least one of the following methods:
[0239] Method 1: Add new configuration parameters in o-ran-uplane-conf.yang, and the O-DU configures the delay-profile-id according to the beamforming method it supports. Each endpoint can only be configured with one delay-profile-id. The example is as follows:
[0240]
[0241] Method 2: You can add a new beamforming type parameter beamforming-method-configuration to the existing parameter "low-level-tx / rx-endpoints" in the o-ran-uplane-conf.yang file for configuration. The beamforming-method-configuration parameter is the beamforming method selected by the O-DU. The type can be defined as a list. The parameter in the list contains one or more beamforming-methods. The example is as follows:
[0242]
[0243] Method 3: You can configure a new remote procedure call (rpc) model in the beamforming configuration file o-ran-beamforming.yang. Configure it by inputting the parameter beamforming-method. The O-DU configures the beamforming-method to the O-RU. The example is as follows:
[0244]
[0245] Method 4: You can configure the selected beamforming-method to the O-RU through the new read-write parameter beamforming-method-configuration in the o-ran-delay-management.yang file. The example is as follows:
[0246]
[0247] In step S204, the O-RU may feedback through the O-FH whether the O-RU successfully adopts or fails to modify the beamforming method. The O-RU optimizes and selects the O-RU delay profile corresponding to the beamforming in the sending and / or receiving buffer window definition and the receiving end buffer operation according to the updated beamforming method (for example, determined according to the information received in step S203) (for example, it may be all or partly the same as the content reported in step S201).
[0248] In an optional implementation, the O-RU may also report second information related to delay management in step 204, for example, the second information is related to a delay profile adopted by the O-RU.
[0249] In one example, the second information related to delay management reported in step 204 includes but is not limited to the beamforming method adopted by the O-RU. The O-RU may report the second information related to delay management by at least one of the following methods, so that the O-DU may obtain information related to the beamforming method of the O-RU:
[0250] Method 1: The O-RU can add a beamforming type parameter beamforming-method-configuration in the list "low-level-tx / rx-endpoints" in the o-ran-uplane-conf.yang file to report the status to implement the second information related to delay management. The example is as follows:
[0251]
[0252]
[0253] Method 2: If the O-DU configures the beamforming method to the O-RU by configuring a new remote call model in the beamforming configuration file o-ran-beamforming.yang, then the O-RU reporting the second information related to delay management in step S204 can be implemented by adding a read-only parameter beamforming-method in the notification in o-ran-beamforming.yang. The example is as follows:
[0254]
[0255] Method 3: Reporting the second information related to delay management can be done by reporting the beamforming method parameters used in the o-ran-delay-management.yang file on the management plane. An example is as follows:
[0256]
[0257] Exception handling: If the O-RU fails to update the delay parameters, that is, the O-RU fails to successfully use or configure the delay profile related to the beamforming method configured by the O-DU in step 203, the O-RU also carries the last saved or default beamforming method when providing feedback through the O-FH (for example, sending a beamforming method configuration response).
[0258] According to the update of the O-RU feedback, the O-DU adopts the delay parameters corresponding to the beamforming method fed back by the O-RU for delay management, such as calculating the corresponding delay and transmitting and / or receiving based on the calculated delay.
[0259] In step 205, the O-DU updates the O-DU delay parameter according to the feedback from the O-RU. The O-DU calculates the receiving / transmitting delay of the O-DU according to the delay profile updated by the O-RU, thereby updating the receiving / transmitting buffer window of the O-DU and improving the performance of the O-DU scheduling resources.
[0260] Figure 3 A schematic diagram of an example of a management process for dynamic delay management update (a management process based on dynamic management of delay profile) according to some embodiments of the present disclosure is shown; if the O-DU delay profile is allowed to be dynamically changeable, dynamic configuration updates can be performed during operation, and this dynamic change can be real-time and based on time units, for example, based on time slot levels. This dynamic change can also be reconfigured through the management plane configuration file, and the endpoint level reconfiguration is performed without affecting the services in other endpoints in the O-RU. Combined with Figure 3 The described methods are only examples, and some steps may be omitted or some new steps may be added.
[0261] like Figure 3 As shown, the management process of dynamic delay management according to some embodiments of the present disclosure includes:
[0262] In step S301, the O-RU reports the third information related to delay management. The O-RU transmits the third information including the supported delay profiles through the O-FH interface uplink. For example, the third information may include: supported beamforming methods, such as at least one of a beamforming method based on channel information, a beamforming method of a predefined beam, a dynamic beamforming method based on beam weights, and a dynamic beamforming method based on beam characteristics, and an O-RU delay profile corresponding to the beamforming method. For another example, the third information may include variable channel conditions that can affect the change of the beamforming method. The beamforming method applied by each endpoint can be changed by variable channel conditions. When the currently used O-RU delay profile cannot be used for the changed beamforming method, the changed beamforming method may cause the O-RU delay profile to be reconfigured. Variable channel conditions include but are not limited to the current O-RU maximum number of data streams (O-RU capability), the current channel quality (UE level), and the current computing resource consumption of the O-RU and O-DU;
[0263] The reported delay profile includes at least one delay parameter, including but not limited to t2a-min-up, t2a-max-up, t2a-min-cp-dl, t2a-max-cp-dl, tcp-adv-dl, ta3-min, ta3-max, t2a-min-cp-ul, t2a-max-cp-ul, etc.
[0264] In one implementation, the third information related to delay management reported includes reporting the ability to support dynamic configuration of delay parameters. The dynamic configuration of delay parameters can be indicated as a "feature" parameter, feature: dynamic-deley-per-beamforming-type. When the O-RU supports dynamic configuration of delay parameters based on time slots, this indication information can be reported.
[0265] In step S302, the O-DU selects a beamforming method according to the algorithm. The selection process is internally implemented, for example, the O-DU changes the beamforming method and the delay configuration parameters corresponding to the changed beamforming method according to the channel feedback information. In one implementation, the O-DU selects the beamforming method according to the delay configuration file reported by the O-RU in step S301.
[0266] In one implementation, the O-DU selects the beamforming method according to the channel condition in step S301 due to changes in one or more factors as shown below. These three factors are listed in order of priority as follows: the current maximum number of data streams of the O-RU (O-RU capability), the current channel quality (UE level), and the current computing resource consumption of the O-RU and O-DU; in addition, the priority order between these factors can also be other orders.
[0267] For example:
[0268] 1) When the maximum number of data flows of the current O-RU is less than the defined threshold (e.g., the transmit and receive transmission channels are turned off for energy saving), the only beamforming mode that can be applied is the predefined beamforming mode regardless of the current channel quality and node computing resource consumption.
[0269] 2) If the current maximum number of data streams of the O-RU is greater than the threshold (e.g. the transmit and receive transmission channels are awakened from the energy-saving state), the O-DU's beamforming method will be updated by further considering the channel quality and node computing resource consumption. If the current channel quality (UE level) is greater than the defined threshold and the O-DU / O-RU computing resources are available for beamforming weights, the beamforming mode can be updated. Otherwise, if the current channel quality (UE level) is greater than the defined threshold, the O-DU / O-RU computing resources are available for beamforming weights.
[0270] If the channel quality is lower than the defined threshold, only the predefined beamforming mode can be applied. When the channel quality is low, the beamforming weight calculation is meaningless.
[0271]
[0272] In step S303, the O-DU notifies the O-RU of the dynamic configuration of the delay parameters or the change of the beamforming method. The O-DU notifies the O-RU of the changed delay parameters or beamforming method through the O-FH interface. In the dynamic configuration of the delay parameters or the dynamic beamforming method, multiple beamforming methods can be configured to the O-RU at the same time through the management plane. Since the dynamic beamforming of each RU can be different based on different endpoints, new delay parameters are configured for each endpoint through a configuration of a smaller granularity (for example, the endpoint is a smaller granularity than the entire O-RU).
[0273] After each endpoint updates the BF mode, there are two types of O-DU reconfiguration message contents, depending on whether the O-DU knows the transmission delay between the O-DU and the O-RU (transmission delay measurement is optional for the O-RU).
[0274] If the O-DU is not aware of the transmission delay: The O-DU reconfigures the O-RU delay profile by the delay-profiles-id reported at startup.
[0275] If the O-DU knows the transmission delay: the O-DU reconfigures the O-RU delay profile by a proposed O-RU delay profile which is optimized by the O-DU considering the transmission delay parameter.
[0276] Regarding the reconfiguration method of the O-DU to reconfigure the delay profile to the O-RU, the optional reconfiguration process scheme is as follows Fig.11 As shown, where:
[0277] Step 1103: Use the interval time to synchronize the configuration changes, use the control plane to configure the changes, for example, the second node (O-DU) sends a first message related to the delayed configuration file update to the first node (O-RU), and increases the interval time parameter ΔT and the current time slot number in the step to achieve synchronous configuration changes.
[0278] ΔT (interval time) is specified by the time parameter in the control plane reconfiguration message (eg, the first message) and is counted in number of time slots greater than zero, the duration of the time slot being indicated in the control plane common part type header.
[0279] ΔT>Control plane message transmission delay time between O-RU and O-DU+maximum profile switching time (indicating the maximum processing time of the O-RU using a new sending or receiving window). For example, the maximum profile switching time may be reported by the O-RU together with information related to the delay profile when reporting its ability to support multiple delay profiles based on the BF method to the O-DU.
[0280] The O-RU calculates the time slot for changing the delay profile based on the current time slot number and ΔT. Then the O-
[0281] DU and O-RU will be updated simultaneously in the same time slot.
[0282] The O-RU may send a “Ready” message to the O-DU containing a specific “Ready” bit indicating that the O-RU is ready to process the deferred profile update.
[0283] Optional reconfiguration scheme 2 Fig.12 As shown:
[0284] Update the delay profile of each endpoint using a process similar to the current management plane configuration. To ensure synchronization of the O-DU and O-RU delay configurations, since the management plane commands will be executed in unknown time slots, the window timing of the O-DU and O-RU is not guaranteed to be consistent. Fig.12 As shown, in step 1203: O-DU sends configuration information including information about endpoints that need to deactivate carriers and make delay profile changes to O-RU. For example, the second node (O-DU) sends a second message related to the delay profile update to the first node (O-RU). For example, O-DU can send a deactivation command and an update command (for example, including an updated delay profile), and O-RU performs deactivation of the corresponding carrier (for example, a portion of the carriers in the endpoints that need to make delay configuration changes) according to the deactivation command and updates the delay profile on the corresponding endpoint. For example, this can be achieved by enhancing RPC to include the specific deactivated endpoint for which the delay profile is updated. Allowing delay profile updates to be performed on each endpoint. In step 1204: O-DU configures the new delay profile to the endpoint of O-RU. O-RU can use the new delay profile for each endpoint to determine the sending or receiving window. In step 305: O-RU then activates the above-mentioned endpoints that were deactivated and the delay profile was changed.
[0285] Considering the impact of the window, for example, when the optimization parameters are T2a_min_up and T2a_max_up, the expansion of the O-RU receiving window and the widening of the receiving window will not cause some messages to be discarded. At this time, there is no need for O-DU and O-RU to delay configuration synchronization, and the management plane command can be used to directly reconfigure and update, that is, directly use step 1204.
[0286] Return to reference Figure 3 In step S304, the O-RU feeds back the update information. This step is similar to step 204 and will not be described in detail here.
[0287] In step S305, the O-DU dynamically determines the beamforming method configured for the O-RU based on a time unit (eg, a time slot).
[0288] In step S306, the O-DU notifies the O-RU of the delay profile (including one or more delay parameters) used in each time slot through a control plane message in different time slots. This can be implemented, for example, as follows: in a control plane or user plane message, the O-RU is notified of the beamforming method used in the current message through different message types or indications. The O-RU selects a delay profile related to the beamforming method according to the indication of the message, or when multiple groups of beamforming methods are supported at the same time, the O-RU can also calculate the best delay profile currently used through a certain algorithm through at least one group of delay profiles corresponding to the multiple groups of beamforming methods.
[0289] Through the above method, dynamic delay management based on time units can be implemented, so that delay management can be better adapted to the current communication environment.
[0290] Figure 4 A schematic diagram showing an example of a management flow of delay management according to some embodiments of the present disclosure.
[0291] like Figure 4 As shown, the management process includes:
[0292] In step S401, the O-RU reports the fourth information related to delay management. The O-RU transmits the fourth information including the delay profile (including at least one delay parameter) via the O-FH interface uplink. For example, the O-RU supports a set of O-RU delay parameters under all beamforming methods, and only reports a set of O-RU delay parameters when the O-RU supports multiple beamforming methods at the same time. In one implementation, the determination of such delay parameters may take into account all beamforming methods supported by the O-RU, and cover all beamforming methods in a way of setting the worst delay parameter. For example, for each of the delay parameters to be reported, the worst one of the delay parameters corresponding to all beamforming methods supported by the O-RU may be reported. For example, if the O-RU supports beamforming methods bf1, bf2, and bf3, the delay parameters to be reported are delay0 and delay1. If delay0 corresponding to bf1 is the worst and delay1 corresponding to bf3 is the worst, the O-RU can report delay0 corresponding to bf1 and delay1 corresponding to bf3.
[0293] In step S402, the O-RU continues to use the worst delay parameter to configure the delay of the O-RU.
[0294] Through the above method, the delay parameter can be made applicable to all beamforming methods supported by the O-RU without modifying the existing settings.
[0295] Figure 5 A simplified block diagram showing the hardware structure of the first node 500 according to an embodiment of the present disclosure. Figure 5 The illustrated first node 500 may be used to implement any method performed by an O-RU according to the principles of the present disclosure.
[0296] refer to Figure 5 According to an embodiment of the present disclosure, the first node 500 includes a transceiver 501 and a controller 502. Optionally, the first node 500 may also include a memory (not shown). The transceiver 501 may send a signal or data, or receive a signal or data. The controller 502 may be coupled to the transceiver 501 and the memory, and control the operation of the transceiver 501 and the memory. The memory stores computer executable instructions, and when the instructions are executed by the controller 502, at least one method corresponding to the above embodiments of the present disclosure is executed.
[0297] Figure 6 A simplified block diagram showing the hardware structure of the second node 600 according to an embodiment of the present disclosure. Figure 6 The illustrated second node 600 may be used to implement any method performed by an O-DU according to the principles of the present disclosure.
[0298] refer to Figure 6 According to an embodiment of the present disclosure, the second node 600 includes a transceiver 601 and a controller 602. Optionally, the second node 600 may also include a memory (not shown). The transceiver 601 may send a signal or data, or receive a signal or data. The controller 602 may be coupled to the transceiver 601 and the memory, and control the operation of the transceiver 601 and the memory. The memory stores computer executable instructions, and when the instructions are executed by the controller 602, at least one method corresponding to the above embodiments of the present disclosure is executed.
[0299] The above description is only an exemplary embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.
[0300] It will be appreciated by those skilled in the art that the present application may include devices for performing one or more of the operations described in the present application. These devices may be specially designed and manufactured for the desired purpose, or may include known devices in general-purpose computers. These devices have computer programs stored therein, which are selectively activated or reconstructed. Such computer programs may be stored in a device (e.g., computer) readable medium or in any type of medium suitable for storing electronic instructions and coupled to a bus, respectively, the computer readable medium including but not limited to any type of disk (including floppy disk, hard disk, optical disk, CD-ROM, and magneto-optical disk), ROM (Read-Only Memory), RAM (Random Access Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory, magnetic card or optical card. That is, the readable medium includes any medium that stores or transmits information in a readable form by a device (e.g., computer).
[0301] Those skilled in the art will appreciate that each block in these structure diagrams and / or block diagrams and / or flow charts and combinations of blocks in these structure diagrams and / or block diagrams and / or flow charts can be implemented using computer program instructions. Those skilled in the art will appreciate that these computer program instructions can be provided to a general-purpose computer, a professional computer, or a processor of other programmable data processing methods to implement, thereby executing the scheme specified in the block or multiple blocks of the structure diagram and / or block diagram and / or flow chart disclosed in the present invention through the processor of the computer or other programmable data processing method.
[0302] Those skilled in the art will appreciate that the various operations, methods, steps, measures, and schemes discussed in the present invention may be alternated, modified, combined, or deleted. Further, other steps, measures, and schemes in the various operations, methods, and schemes discussed in the present invention may also be alternated, modified, rearranged, decomposed, combined, or deleted. Further, the steps, measures, and schemes in the prior art that are similar to those disclosed in the present invention may also be alternated, modified, rearranged, decomposed, combined, or deleted.
[0303] The above descriptions are only some embodiments of the present disclosure. It should be pointed out that, for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as within the scope of protection of the present invention.
Claims
1. A method performed by a first node in a communication system, include: Reporting a first delay parameter to the second node, where the first delay parameter is related to a beamforming method supported by the first node; receiving first configuration information related to delay management from the second node; Delay management is performed based on the first configuration information.
2. The method according to claim 1, wherein the first delay parameter includes information of at least one delay profile, wherein each delay profile corresponds to one or more of the beamforming methods or non-beamforming methods supported by the first node, or the information of the delay profile includes relevant information of the beamforming method corresponding to the delay profile or relevant information indicating that the delay profile does not correspond to the beamforming method.
3. The method according to claim 1, in, The first delay parameter includes information of a delay profile supported by at least one endpoint of the first node, wherein the delay profile supported by the endpoint is associated with one or more beamforming methods or non-beamforming methods supported by the endpoint.
4. The method according to claim 2 or 3, in, The information of the delay profile includes a delay profile identification ID.
5. The method according to claim 1, in, The first delay parameter includes information of a delay profile obtained based on delay parameters of multiple beamforming methods corresponding to the first node.
6. The method according to any one of claims 1 to 5, in, The first configuration information includes information of a delay profile of at least one endpoint of the first node.
7. The method according to claim 6, in, The information of the delay profile of at least one endpoint of the first node includes a delay profile ID corresponding to the at least one endpoint.
8. The method according to any one of claims 1 to 5, in, If the first configuration information does not include information about the delay profile, the first node performs delay management according to a preset delay profile.
9. The method according to any one of claims 1 to 5, further comprising: include: Information related to the beamforming method is sent to the second node, where the information includes at least one of the following items: computing resource consumption of the first node, channel quality, and a maximum number of data streams of the first node.
10. The method according to any one of claims 1 to 9, further comprising: include: receiving a first message related to delay profile update from a second node, wherein the first message includes transmission time slot information, interval time information and delay profile information of the first message; determining a time for switching a delay profile based on the transmission time slot information and the interval time information; When the determined time for switching the delay profile is reached, the delay profile of the corresponding endpoint is updated based on the information of the delay profile.
11. The method according to claim 10, further comprising: include: The first node sends maximum delay profile switching time information to the second node. The interval time information is determined based on the maximum delay profile switching time.
12. A method performed by a second node in a communication system, include: receiving a first delay parameter from a first node, the first delay parameter being related to a beamforming method supported by the first node; Sending first configuration information related to delay management to the first node.
13. The method according to claim 12, further comprising: include: A first message related to delay profile update is sent to the first node, wherein the first message includes sending time slot information, interval time information and delay profile information of the first message.
14. The method according to claim 13, in, Before sending a first message related to delaying the configuration file update to the first node, the method further includes: It is determined that a receiving window of the first node becomes smaller after the delay profile is updated or a data processing delay of the first node changes after the delay profile is updated.
15. The method according to claim 13, further comprising: include: receiving maximum delay profile switching time information from the first node, The interval time information is determined based on the maximum delay profile switching time.
16. The method according to claim 12, further comprising: include: A second message related to delay profile update is sent to the first node, the second message including information of an updated delay profile of at least one endpoint.
17. The method according to claim 16, in, Before sending a second message related to delaying the configuration file update to the first node, the method further includes: It is determined that the receiving window of the first node becomes larger after the delay profile is updated.
18. A first node in a communication system, include: a transceiver configured to transmit and / or receive signals; A controller is configured to control the first node to execute the method according to any one of claims 1-11.
19. A second node in a communication system, include: a transceiver configured to transmit and / or receive signals; A controller is configured to control the second node to execute the method according to any one of claims 12-17.
20. A storage medium having instructions stored thereon, which when executed by a processor cause the processor to perform the method according to any one of the preceding claims.
