Electronic device and method for delay measurement in wireless communication system
The method for precise delay measurement between DUs in wireless communication systems addresses the challenge of accurately assessing delay, optimizing communication interfaces and enhancing network performance in 5G and 6G networks.
Patent Information
- Application Number
- PCT/KR2024/004031
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-08
- Filing Date
- 2024-03-29
- Publication Date
- 2024-11-14
AI Technical Summary
Current wireless communication systems face challenges in accurately measuring delay between distributed units (DUs) in wireless communication systems, particularly in 5G and emerging 6G networks, which affects signal transmission efficiency and network performance.
A method and electronic device for a first distributed unit (DU) that transmits a measurement request message to a second DU, including global IDs and identification information, and receives a measurement response message with time information to calculate delay, enabling precise delay measurement and optimization of communication interfaces.
This approach allows for accurate delay measurement, improving signal transmission efficiency and network performance by optimizing communication interfaces between DUs, thereby enhancing overall system performance and reliability.
Smart Images

Figure KR2024004031_14112024_PF_FP_ABST
Abstract
Description
Electronic device and method for delay measurement in wireless communication systems
[0001] The present disclosure relates to a wireless communication system, and more particularly, to an electronic device and method for delay measurement in a wireless communication system.
[0002] 4G(4 th To meet the increasing demand for wireless data traffic since the commercialization of the 5G (5 generation) communication system, the improved 5G (5 th Efforts are being made to develop 5G communication systems or pre-5G communication systems. For this reason, 5G communication systems or pre-5G communication systems are also called Beyond 4G Network communication systems or Post-LTE systems.
[0003] To achieve high data rates, 5G communication systems are being considered for implementation in ultra-high frequency (mmWave) bands (e.g., the 60 GHz band). To mitigate radio path loss and increase the transmission range of radio waves in ultra-high frequency bands, beamforming, massive MIMO (massive MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antenna technologies are being discussed in 5G communication systems.
[0004] Additionally, to improve the network of the system, technologies such as evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device communication (D2D), wireless backhaul, moving networks, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation are being developed in 5G communication systems.
[0005] In addition, advanced coding modulation (ACM) methods such as Hybrid Frequency Shift Keying and Quadrature Amplitude Modulation (FQAM) and Sliding Window Superposition Coding (SWSC), as well as advanced access technologies such as Filter Bank Multi Carrier (FBMC), Non Orthogonal Multiple Access (NOMA), and Sparse Code Multiple Access (SCMA), are being developed in 5G systems.
[0006] In order to meet the demand for wireless data traffic, 5G system, NR (new radio or next radio) is commercialized, and it is expected that it will be able to provide users with high data transmission rate services through 5G system like 4G, and also provide wireless communication services for various purposes such as Internet of Things and services that require high reliability for specific purposes. In the current mixed system of 4th generation communication system, 5th generation system, etc., O-RAN (open radio access network) established by business operators and equipment providers defines E2AP (E2 application protocol) standard in the application protocol of E2 interface between E2 node and Near-RT (real time) RIC (RAN (radio access network) intelligent controller).
[0007] Looking back at the evolution of wireless communication over successive generations, technologies have primarily been developed for human-facing services such as voice, multimedia, and data. With the commercialization of the 5G (5th Generation) communication system, an explosive increase in connected devices is expected to be connected to communication networks. Examples of networked objects include vehicles, robots, drones, home appliances, displays, smart sensors installed in various infrastructures, construction equipment, and factory equipment. Mobile devices are also expected to evolve into diverse form factors, such as augmented reality glasses, virtual reality headsets, and holographic devices. In the 6G (6th Generation) era, efforts are being made to develop improved 6G communication systems to connect hundreds of billions of devices and objects and provide diverse services. For this reason, 6G communication systems are often referred to as "beyond 5G."
[0008] The 6G communication system, expected to be realized around 2030, will have a maximum transmission speed of terabytes (i.e., 1,000 gigabits) per second (bps) and a wireless latency of 100 microseconds (μsec). In other words, compared to 5G, the transmission speed in a 6G communication system will be 50 times faster and the wireless latency will be reduced to one-tenth.
[0009] To achieve these high data rates and ultra-low latency, 6G communication systems are being considered for implementation in the terahertz (THz) band (e.g., from 95 gigahertz (GHz) to 3 terahertz (THz)). Compared to the millimeter wave (mmWave) band introduced in 5G, the terahertz band is expected to have more severe path loss and atmospheric absorption, making it more important to develop technologies that can guarantee signal reach, or coverage. Key technologies to ensure coverage include Radio Frequency (RF) components, antennas, new waveforms that offer better coverage than Orthogonal Frequency Division Multiplexing (OFDM), beamforming, and multiple antenna transmission technologies such as massive Multiple-Input and Multiple-Output (MIMO), Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas. In addition, new technologies such as metamaterial-based lenses and antennas, high-dimensional spatial multiplexing using Orbital Angular Momentum (OAM), and Reconfigurable Intelligent Surface (RIS) are being discussed to improve the coverage of terahertz band signals.
[0010] In addition, in order to improve frequency efficiency and system network, 6G communication systems are developing full duplex technology that utilizes the same frequency resources at the same time for uplink and downlink; network technology that integrates satellites and HAPS (High-Altitude Platform Stations); network structure innovation technology that supports mobile base stations and enables optimization and automation of network operation; dynamic spectrum sharing technology through collision avoidance based on spectrum usage prediction; AI-based communication technology that utilizes artificial intelligence (AI) from the design stage and internalizes end-to-end AI support functions to realize system optimization; and next-generation distributed computing technology that realizes services with complexity that exceeds the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources (Mobile Edge Computing (MEC), cloud, etc.). In addition, efforts are being made to further strengthen connectivity between devices, further optimize networks, promote softwareization of network entities, and increase the openness of wireless communications through the design of new protocols to be used in 6G communication systems, the implementation of hardware-based security environments, the development of mechanisms for the safe use of data, and the development of technologies for maintaining privacy.
[0011] Research and development of these 6G communication systems are expected to enable a new level of hyper-connected experience through the hyper-connectivity of 6G communication systems, which encompass not only connections between things but also connections between people and things. Specifically, 6G communication systems are expected to enable services such as truly immersive eXtended Reality (XR), high-fidelity mobile holograms, and digital replicas. Furthermore, services such as remote surgery, industrial automation, and emergency response, which are provided through 6G communication systems through enhanced security and reliability, will be applied in diverse fields such as industry, medicine, automobiles, and home appliances.
[0012] In 6G communication systems, RAN functions are expected to be further refined, separating them into service subscribers and service providers. In service-based networks, subscription service confirmation procedures for service subscription status will be applied to various functions.
[0013] The above information may be provided as background art to aid in understanding the present disclosure. No claim or determination is made as to whether any of the above is applicable as prior art related to the present disclosure.
[0014] According to embodiments of the present disclosure, a method performed by a first distributed unit (DU) is provided. The method may include transmitting a measurement request message to a second DU via a communication interface between the first DU and the second DU. The method may include receiving a measurement response message from the second DU via the communication interface. The measurement request message may include a global ID for a base station of the first DU, first identification information of the first DU at the base station, and first time information indicating a first system time at which the measurement request message was transmitted from the first DU. The measurement response message may include a global ID for a base station of the second DU, second identification information of the second DU at the base station, and second time information. The second time information may be used to identify a difference between a second system time at which the measurement request message was received at the second DU and a third system time at which the measurement response message was transmitted from the second DU.
[0015] According to embodiments of the present disclosure, an electronic device for a first distributed unit (DU) is provided. The electronic device may include a memory storing one or more instructions. When the one or more instructions are executed, the one or more instructions may cause the first DU to transmit a measurement request message to a second DU through a communication interface between the first DU and the second DU. When the one or more instructions are executed, the one or more instructions may cause the first DU to receive a measurement response message from the second DU through the communication interface. The measurement request message may include a global ID for a base station of the first DU, first identification information of the first DU at the base station, and first time information indicating a first system time at which the measurement request message was transmitted from the first DU. The measurement response message may include a global ID for the base station of the second DU, second identification information of the second DU at the base station, and second time information. The second time information may be used to identify a difference between a second system time at which the measurement request message was received by the second DU and a third system time at which the measurement response message was transmitted by the second DU.
[0016] According to embodiments of the present disclosure, an electronic device of a first distributed unit (DU) is provided. The electronic device may include at least one transceiver, at least one processor, and a memory. The at least one processor may be operatively coupled to the memory and the at least one transceiver. The at least one processor may be configured to transmit a measurement request message to a second DU via a communication interface between the first DU and the second DU. The at least one processor may be configured to receive a measurement response message from the second DU via the communication interface. The measurement request message may include a global ID for a base station of the first DU, first identification information of the first DU at the base station, and first time information indicating a first system time at which the measurement request message was transmitted from the first DU. The measurement response message may include a global ID for the base station of the second DU, second identification information of the second DU at the base station, and second time information. The second time information may be used to identify a difference between a second system time at which the measurement request message was received by the second DU and a third system time at which the measurement response message was transmitted by the second DU.
[0017] The above and other aspects, features and advantages of specific embodiments of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings, in which:
[0018] Figures 1a and 1b illustrate examples of wireless communication systems.
[0019] Figures 2a to 2c illustrate examples of spectrum aggregation environments.
[0020] Figure 3 illustrates an example of a resource structure in the time domain and frequency domain.
[0021] Figure 4a illustrates an example of an architecture for an open RAN (radio access network).
[0022] Figure 4b illustrates an example of network entities according to distributed deployment in O-RAN.
[0023] Figure 5 illustrates examples of components of DU.
[0024] Figure 6 illustrates an example of a first type measurement procedure at an interface between DUs.
[0025] Figure 7 is a diagram for explaining signaling of parameters for delay measurement in an interface between DUs.
[0026] Figures 8a to 8c are diagrams showing signaling for delay measurement.
[0027] Figure 9a illustrates an example of a second type of measurement procedure at an interface between DUs.
[0028] FIG. 9b is a diagram for explaining signaling of parameters for delay measurement at the interface between DUs.
[0029] Figures 10a to 10c are diagrams showing signaling for delay measurement.
[0030] Figure 11 is a diagram showing signaling for delay measurement.
[0031] Figure 12 is a diagram showing signaling for delay measurement.
[0032] Figure 13 is a diagram showing signaling for delay measurement.
[0033] Figure 14 illustrates an example of delay measurement using a setup procedure at an interface between DUs.
[0034] Figure 15 illustrates an example of a liver removal procedure at the interface between DUs.
[0035] Figure 16 illustrates an example of an exemplary timestamp format.
[0036] The terms used in this disclosure are used only to describe specific embodiments and may not be intended to limit the scope of other embodiments. The singular expression may include plural expressions unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by those of ordinary skill in the art described in this disclosure. Terms defined in general dictionaries among the terms used in this disclosure may be interpreted as having the same or similar meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined in this disclosure. In some cases, even if a term is defined in this disclosure, it cannot be interpreted to exclude embodiments of the present disclosure.
[0037] The various embodiments of the present disclosure described below illustrate a hardware-based approach as an example. However, since the various embodiments of the present disclosure include techniques utilizing both hardware and software, the various embodiments of the present disclosure do not exclude a software-based approach.
[0038] In the following description, terms referring to signals (e.g., signal, information, message, signaling), terms referring to resources (e.g., symbol, slot, subframe, radio frame, subcarrier, resource element (RE), resource block (RB), bandwidth part (BWP), occasion), terms for operational states (e.g., step, operation, procedure), terms referring to data (e.g., packet, user stream, information, bit, symbol, codeword), terms referring to channels, terms referring to network entities, terms referring to components of devices, etc. are examples for convenience of description. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used. In addition, the terms '...bu', '...gi', '...mul', '...che', etc. used below may mean at least one shape structure or a unit that processes a function.
[0039] In addition, in the present disclosure, expressions such as "more than" or "less than" may be used to determine whether a specific condition is satisfied or fulfilled, but this is merely a description for expressing an example and does not exclude descriptions such as "more than" or "less than." A condition described as "more than" may be replaced with "more than," a condition described as "less than" may be replaced with "less than," and a condition described as "more than and less than" may be replaced with "more than and less than." In addition, hereinafter, "A" to "B" mean at least one of elements from A (including A) to B (including B). hereinafter, "C" and / or "D" mean at least one of "C" or "D," that is, including {"C", "D", "C" and "D"}.
[0040] Although the present disclosure describes various embodiments using terms used in some communication standards (e.g., 3rd Generation Partnership Project (3GPP), extensible radio access network (xRAN), open-radio access network (O-RAN), etc.), these are merely examples for explanation. The various embodiments of the present disclosure can be easily modified and applied to other communication systems.
[0041] In the present disclosure, the signal quality may be, for example, at least one of RSRP (reference signal received power), BRSRP (beam reference signal received power), RSRQ (reference signal received quality), RSSI (received signal strength indicator), SINR (signal to interference and noise ratio), CINR (carrier to interference and noise ratio), SNR (signal to noise ratio), EVM (error vector magnitude), BER (bit error rate), and BLER (block error rate). In addition to the examples described above, it goes without saying that other terms having equivalent technical meanings or other metrics indicating channel quality may be used. Hereinafter, in the present disclosure, high signal quality means a case where a signal quality value related to a signal size is large or a signal quality value related to an error rate is small. A higher signal quality may mean that a smooth wireless communication environment is guaranteed. In addition, an optimal beam may mean a beam with the highest signal quality among beams.
[0042] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.
[0043] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.
[0044] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).
[0045] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.
[0046] Hereinafter, 4G and / or 5G environments are described as examples, but this description does not limit the scope of the communication environments of the embodiments of the present disclosure. The technical principles according to the embodiments of the present disclosure can also be applied to 6G and post-6G communication technologies and network environments.
[0047] Figures 1a and 1b illustrate examples of wireless communication systems.
[0048] Referring to FIG. 1A, FIG. 1A illustrates a base station (110) and a terminal (120) as some of the nodes utilizing a wireless channel in a wireless communication system. Although FIG. 1A illustrates only one base station, the wireless communication system may further include other base stations identical or similar to the base station (110).
[0049] The base station (110) is a network infrastructure that provides wireless access to the terminal (120). The base station (110) has coverage defined based on the distance at which a signal can be transmitted. In addition to the base station, the base station (110) may be referred to as an 'access point (AP)', 'eNodeB (eNB)', '5th generation node', 'next generation nodeB (gNB)', 'wireless point', 'transmission / reception point (TRP)', or other terms having equivalent technical meanings.
[0050] The terminal (120) is a device used by a user and communicates with the base station (110) via a wireless channel. The link from the base station (110) to the terminal (120) is referred to as a downlink (DL), and the link from the terminal (120) to the base station (110) is referred to as an uplink (UL). In addition, although not shown in FIG. 1A, the terminal (120) and another terminal may communicate with each other via a wireless channel. In this case, the link between the terminal (120) and another terminal (device-to-device link, D2D) is referred to as a sidelink, and the sidelink may be used interchangeably with the PC5 interface. In some other embodiments, the terminal (120) may be operated without the involvement of a user. In one embodiment, the terminal (120) is a device that performs machine type communication (MTC) and may not be carried by the user. Additionally, according to one embodiment, the terminal (120) may be an NB (narrowband)-IoT (internet of things) device.
[0051] The terminal (120) may be referred to as a terminal, or other terms such as 'user equipment (UE),' 'customer premises equipment (CPE),' 'mobile station,' 'subscriber station,' 'remote terminal,' 'wireless terminal,' 'electronic device,' or 'user device,' or other terms having equivalent technical meanings.
[0052] The base station (110) and the terminal (120) can perform beamforming. The base station (110) and the terminal (120) can transmit and receive wireless signals in a relatively low frequency band (e.g., FR 1 (frequency range 1) of NR). In addition, the base station (110) and the terminal (120) can transmit and receive wireless signals in a relatively high frequency band (e.g., FR 2 (or, FR 2-1, FR 2-2, FR 2-3), FR 3 of NR), millimeter wave (mmWave) band (e.g., 28 GHz, 30 GHz, 38 GHz, 60 GHz)). To improve channel gain, the base station (110) and the terminal (120) can perform beamforming. Here, the beamforming can include transmission beamforming and reception beamforming. The base station (110) and the terminal (120) can impart directionality to the transmitted or received signal. To this end, the base station (110) and the terminal (120) can select serving beams through a beam search or beam management procedure. After the serving beams are selected, subsequent communication can be performed through resources that have a QCL relationship with the resource that transmitted the serving beams.
[0053] The terminal (120) may be configured with cells of the base station (110) and carrier aggregation (CA). CA technology is a technology that increases the frequency usage efficiency of the terminal (120) and the base station (110) by connecting the terminal to a group of homogeneous wireless communication cells having a common radio resource control entity, and simultaneously using frequency resources on component carriers of each cell located in different frequency bands for signal transmission and reception. The cells configured for CA may include one PCell (primary cell) and one or more SCells (secondary cells).
[0054] Referring to FIG. 1B, a terminal (120) may be configured in dual connectivity (DC) using a first base station (110-1) and a second base station (120). DC technology is a technology that increases frequency usage efficiency by simultaneously connecting a terminal to two independent heterogeneous or homogeneous wireless communication cell groups having separate radio resource control entities, and using frequency resources on component carriers of cells within each cell group located in different frequency bands for signal transmission and reception. The terminal (110) is connected to two different radio resource entities (e.g., a first base station (110-1), a second base station (110-2)) and is a technology for using radio resources allocated by each radio resource entity. In MR-DC, a UE (e.g., terminal 120) in a radio resource control (RRC) connected state (i.e., RRC_CONNCETED) can be configured to utilize radio resources provided by two independent schedulers. Each scheduler can be located in an NG-RAN node (e.g., a first base station (110-1) and a second base station (110-2)). Here, one node is a master node (MN) and the other node is a secondary node (SN). The MN and SN are connected via a network interface, and the MN can be connected to a core network. The SN may or may not be connected to the core network.
[0055] The MN may provide a master cell group (MCG). The MN, in addition to the MN, may be referred to as an M-NODE or an M-NG-RAN node. The MCG may include one or more cells. The MCG may include a PCell (primary cell). The MCG may include multiple aggregated cells. The MCG may include a PCell and one or more secondary cells (SCells). The SN may provide a secondary cell group (SCG). The SN, in addition to the SN, may be referred to as an S-NODE or an S-NG-RAN node. The SCG may include one or more cells. The SCG may include multiple aggregated cells. Like the MCG, the SCG may include a PCell and / or an SCell. A cell functioning as a PCell within the SCG may be referred to as a PSCell (primary secondary cell). The secondary cell group may include a PSCell and one or more SCells. Hereinafter, the term "SpCell" (special cell) may be used to encompass PCell and PSCell. "SpCell" refers to the primary cell of an MCG or SCG. In other words, an MCG SpCell refers to a PCell, and an SCG SpCell refers to an SCell.
[0056] The possible types of DC can be defined as follows:
[0057] 1) EN-DC: Dual connectivity in which the eNB is connected to the evolved packet core (EPC), and the UE is connected to the eNB acting as an MN and the gNB acting as an SN. Here, the gNB may be referred to as an en-gNB, and the en-gNB may or may not be connected to the EPC.
[0058] 2) NGEN-DC: Dual connectivity in which the eNB is connected to the 5GC (5G core), and the terminal is connected to the eNB operating as an MN and the gNB operating as an SN. Here, the eNB may be referred to as ng-eNB.
[0059] 3) NE-DC: Dual connectivity in which the gNB is connected to the 5GC, and the terminal is connected to the gNB operating as an MN and the eNB operating as an SN. Here, the eNB may be referred to as ng-eNB.
[0060] 4) NR-DC: Dual connectivity where gNBs are connected to 5GC, and the UE is connected to a gNB that acts as an MN and a gNB that acts as an SN. NR-DC can also be used when a UE is connected to a single gNB that acts as both an MN and SN and configures both an MCG and an SCG.
[0061] The terminal (120) can support MR (multi-radio)-DC. The terminal (120) can be connected to a first base station (110-1) and a second base station (110-2). The first base station (110-1) is an MN, and the second base station (110-2) is an SN, and can be connected to the terminal. With the CA (carrier aggregation) provided by each base station, the DC technology can provide higher data rates. The first base station (110-1) and the second base station (110-2), as MN and SN, respectively, can transmit downlink traffic to the terminal (120) or receive uplink traffic from the terminal (120).
[0062] Figures 2a to 2c illustrate examples of spectrum aggregation environments. Spectrum aggregation refers to a wireless communication technology that uses a certain frequency interval in the frequency domain and another frequency interval together with the frequency interval. Depending on the technology used, the frequency interval may correspond to at least one of a resource block (RB), a bandwidth part (BWP), a bandwidth, a cell, a cell group, a frequency band, and / or a frequency range. For example, spectrum aggregation may include CA. The bandwidth of a PCell (primary cell) and the bandwidth of a SCell (primary cell) may be used together for data communication. For example, spectrum aggregation may include DC. The frequency range occupied by the MCG cell of the MN and the frequency range occupied by the SCG cell of the SN may be used together for communication. For example, spectrum aggregation may include CoMP. Base stations with different frequency spectrums may be utilized for data communications. For example, spectrum aggregation may include multi-transmission reception points (M-TRPs). Resources allocated in different frequency bands may be utilized for data transmission.
[0063] A cell can refer to an area (or coverage) that can be covered by a single base station (e.g., gNB) (or a single DU). A cell can refer to not only a geographical area but also an area occupying a specific spectrum in the frequency domain. A DU can cover one cell or multiple cells. Here, multiple cells can be distinguished by the frequency they support and the area of the sector they cover. A serving cell is a cell that provides a terminal and upper layer signaling (e.g., radio resource control (RRC) signaling), and can refer to one cell or multiple cells. If the terminal (120) is not configured to support carrier aggregation (CA) and dual connectivity (DC), the serving cell can be a single cell corresponding to a PCell. When the terminal (120) is set to support CA or DC, the serving cell may be a set of cells including a PCell and one or more SCells.
[0064] Referring to Fig. 2a, a base station can be divided into a CU and a DU. For example, if the base station corresponds to a gNB, the CU is a logical node that hosts the RRC, SDAP (service data adaptation protocol), and PDCP (packet data convergence protocol) protocols of the base station. The CU and the DU can be connected via the F1 interface. The DU is a logical node that hosts the RLC (radio link control), MAC (medium access control), and PHY (physical) layers. A DU can support one or more cells, and a cell can be supported by only one DU. A first base station (110-1) can include CU #1 (205-1) and DU #1 (210-1). DU #1 (210-1) can provide one or more cells. A second base station (110-2) can include CU #2 (205-2) and DU #2 (210-2). DU #2 (210-2) may provide one or more cells. For example, for DC operation, MgNB-DU may represent the gNB-DU of the en-gNB or gNB acting as a master node (e.g., DU #1 (210-1)), and SgNB-DU may represent the gNB-DU of the en-gNB or gNB acting as a secondary node (e.g., DU #2 (210-2)).
[0065] Referring to FIG. 2B, a base station can be divided into a CU and a DU. Unlike multiple independent base stations (e.g., a first base station (110-1), a second base station (110-2)) that serve a terminal (120), one CU and multiple DUs can serve a terminal (120). For example, CU #1 (215) can be connected to DU #1 (231) and DU #2 (232). CU #1 (215) can be connected to each of DU #1 (231) and DU #2 (232) via an F1 interface. DU #1 (231) can provide one or more cells. DU #2 (232) can provide one or more cells. For example, for CA operation, DU #1 (231) can provide a cell corresponding to a PCell. DU #2 (232) can provide a cell corresponding to an SCell. Two cells can be configured for the terminal (120).
[0066] Referring to Fig. 2c, the base station can be divided into CU and DU. In addition to the distributed arrangement separated into CU and DU, a base station (242) for small cells can be additionally deployed. For example, CU #1 (215) can be connected to DU #1 (231) via the F1 interface. The base station (242) can communicate with CU #1 (215) as an independent base station. DU #1 (231) can provide one or more cells. The base station (242) can provide one or more small cells. For example, for CA operation, DU #1 (231) can provide a cell corresponding to PCell. DU #2 (232) can provide a cell corresponding to SCell. Two cells can be configured for the terminal (120).
[0067] The vendors of DUs (or DUs and base stations of small cells) may be different. Frequency bands used by multiple vendors may not be compatible with each other. For example, the vendors of the first DU and the second DU may purchase different frequency bands. The frequency range occupied by the cell provided by the first DU may be different from the frequency range occupied by the cell provided by the second DU. Since the second DU does not have accurate information about the cell of the first DU, it may be difficult to configure CA between the two cells. If CA is configured between the two cells, signaling via the CU or a higher-level entity is required because there is no interface between the first DU and the second DU. However, the increase in signaling causes delay, making effective resource management difficult.
[0068] Hereinafter, embodiments of the present disclosure describe a new interface and procedures and messages for configuring the interface for spectrum aggregation, such as the CA or DC described above. First, resources at the physical layer are described through FIG. 3.
[0069] Figure 3 illustrates an example of a resource structure in the time and frequency domains. Figure 3 illustrates the basic structure of the time-frequency domain, which is a radio resource domain in which data or control channels are transmitted in the downlink or uplink.
[0070] Referring to Figure 3, the horizontal axis represents the time domain and the vertical axis represents the frequency domain. The minimum transmission unit in the time domain is an OFDM (orthogonal frequency division multiplexing) symbol, N symbOFDM symbols (302) are grouped to form one slot (306). The length of a subframe is defined as 1.0 ms, and the length of a radio frame (314) is defined as 10 ms. The minimum transmission unit in the frequency domain is a subcarrier, and the carrier bandwidth constituting the resource grid is N BW It consists of a number of subcarriers (304).
[0071] The basic unit of resources in the time-frequency domain is a resource element (RE) (312), which can be represented by an OFDM symbol index and a subcarrier index. A resource block may include multiple resource elements. In the LTE system, a resource block (RB) (or physical resource block (PRB)) is N in the time domain. symb N consecutive OFDM symbols and frequency domain SC RB are defined as N consecutive subcarriers. In the NR system, a resource block (RB) (308) is defined as N in the frequency domain. SC RB can be defined as a series of consecutive subcarriers (310). One RB (308) is N in the frequency axis. SC RB It contains REs (312). In general, the minimum transmission unit of data is RB and the number of subcarriers is N. SC RB=12. The frequency domain may include common resource blocks (CRBs). Physical resource blocks (PRBs) may be defined in the bandwidth part (BWP) of the frequency domain. The CRB and PRB numbers may be determined based on the subcarrier spacing. The data rate may increase in proportion to the number of RBs scheduled to the terminal.
[0072] In the NR system, in the case of a frequency division duplex (FDD) system that operates the downlink and uplink by frequency division, the downlink transmission bandwidth and the uplink transmission bandwidth may be different. The channel bandwidth represents the radio frequency (RF) bandwidth corresponding to the system transmission bandwidth. [Table 1] shows part of the correspondence between the system transmission bandwidth, subcarrier spacing (SCS), and channel bandwidth defined in the NR system in a frequency band lower than x GHz (e.g., frequency range (FR) 1 (310 MHz to 7125 MHz)). And [Table 2] shows part of the correspondence between the transmission bandwidth, subcarrier spacing, and channel bandwidth defined in the NR system in a frequency band higher than y GHz (e.g., FR2 (24250 MHz - 52600 MHz) or FR2-2 (52600 MHz to 71000 MHz)). For example, an NR system with a 100 MHz channel bandwidth and a 30 kHz subcarrier spacing has a transmission bandwidth of 273 RBs. In [Table 1] and [Table 2], N / A may be a bandwidth-subcarrier combination not supported by the NR system.
[0073] Channel bandwidth [MHz] SCS 5 10 20 50 80 100 Transmission bandwidth configuration N RB15kHz2552106207N / AN / A30kHz11245113321727360kHzN / A112465107135
[0074] Channel bandwidth [MHz] SCS50100200400 Transmission bandwidth configuration N RB 60kHz66132264N / A120kHz3266132264
[0075] Figure 4a illustrates an example of an architecture for an open RAN (radio access network). 4th generation (4 th generation, 4G) / 5th generation (5 thAs 5G (5th generation) communication systems (e.g., new radio (NR)) become commercialized, differentiated service support for users in virtualized networks has become required. 3GPP is a joint research project among mobile communication-related organizations, and its goal is to create a globally applicable 3rd generation mobile communication system standard within the scope of the International Telecommunication Union (ITU) IMT-2000 project. Established in December 1998, 3GPP standards are based on the advanced GSM standards, and include radio, core network, and service architecture in the scope of standardization. Accordingly, O-RAN (open radio access network) newly defines the nodes that constitute the 3GPP NE (network entity) and base station, namely RU (radio unit), DU (digital unit), CU (central unit)-CP (control plane), and CU-UP (user plane), as O(O-RAN)-RU, O-DU, O-CU-CP, and O-CU-UP, respectively, and additionally standardizes the NRT (near-real-time) RIC (radio access network intelligent controller). Here, O-RU, O-DU, O-CU-CP, and O-CU-UP can be understood as objects that constitute the RAN that can operate according to the O-RAN standard, and can be referred to as E2 nodes. The interface between the objects that constitute the RAN that can operate according to the O-RAN standard between the RIC (e.g., Near-RT RIC) and E2 nodes uses E2AP (application protocol).
[0076] Referring to FIG. 4A, according to one embodiment, as a wireless communication system in an O-RAN, network entities according to the NSA mode (401) may be configured. In a deployment according to the NSA mode (401), an eNB is connected to an EPC via an S1-C / S1-U interface and to an O-CU-CP via an X2 interface. According to one embodiment, as a wireless communication system in an O-RAN, network entities according to the SA mode (402) may be configured. In a deployment according to the SA mode (402), an O-CU-CP may be connected to a 5GC (5G core) via an N2 / N3 interface.
[0077] A Near-RT (real time) RIC is a logical node that can collect information at a cell site where a terminal and an O-DU, O-CU-CP, or O-CU-UP transmit and receive information. A Near-RT RIC can be implemented as a server centrally located in one physical location. Connections can be established between an O-DU and a Near-RT RIC, between an O-CU-CP and a Near-RT RIC, and between an O-CU-UP and a Near-RT RIC via Ethernet. For this purpose, interface specifications for communication between an O-DU and a Near-RT RIC, between an O-CU-CP and a Near-RT RIC, and between an O-CU-UP and a Near-RT RIC are required, and message specifications such as E2-DU, E2-CU-CP, and E2-CU-UP and definition of procedures between an O-DU, O-CU-CP, O-CU-UP, and a Near-RT RIC are required. In particular, differentiated service support is required for users in virtualized networks, and by concentrating call processing messages / functions generated in O-RAN to Near-RT RIC, it is necessary to define the functions of E2-DU, E2-CU-CP, and E2-CU-UP messages to support services for wide cell coverage.
[0078] Near-RT RIC communicates with O-DU, O-CU-CP, and O-CU-UP using E2 interface, and can set event occurrence conditions by generating and sending subscription messages. For example, Near-RT RIC can set call processing event by generating E2 subscription request message and sending it to E2 node (e.g., O-CU-CP, O-CU-UP, O-DU). In addition, after setting event, E2 node sends subscription request response message to Near-RT RIC. E2 node can send current status to Near-RT RIC through E2 indication / report. Near-RT RIC can provide control for O-DU, O-CU-CP, and O-CU-UP using E2 control message.
[0079] Figure 4b illustrates an example of network entities according to distributed deployment in O-RAN.
[0080] Referring to FIG. 4b, the base station (110) may be distributed to multiple network entities defined in the O-RAN standard. For example, the base station (110) may include an O-CU-UP (410), an O-CU-CP (420), and / or an O-DU (430). A Near-RT RIC (440) is connected to the O-CU-CP (420), the O-CU-UP (410), and the O-DU (430). The Near-RT RIC (440) is a device for customizing RAN functionality for new services or regional resource optimization. The Near-RT RIC (440) can provide functions such as network intelligence (e.g., policy enforcement, handover optimization), resource assurance (e.g., radio-link management, advanced self-organized network (SON)), and resource control (e.g., load balancing, slicing policy). The Near-RT RIC (440) can communicate with the O-CU-CP (420), the O-CU-UP (410), and the O-DU (430). The Near-RT RIC (440) can be connected to each node through the E2-CP, E2-UP, and E2-DU interfaces. In addition, the interface between the O-CU-CP and the DU, and the interface between the O-CU-UP and the DU may be referred to as the F1 interface. In the following description, DU and O-DU, CU-CP and O-CU-CP, CU-UP and O-CU-UP may be used interchangeably.
[0081] While FIG. 4b illustrates a single Near-RT RIC (440), multiple RICs may exist in various embodiments. The multiple RICs may be implemented using multiple hardware located in the same physical location, or through virtualization using a single piece of hardware.
[0082] In a communication system with a relatively large base station cell radius, each base station is installed to include the functions of a digital processing unit (or DU (distributed unit)) and an RF (radio frequency) processing unit (or RU (radio unit)). 4G (4 th As higher frequency bands are used in the 5G generation and / or subsequent communication systems (e.g., 5G) and the cell coverage of base stations becomes smaller, the number of base stations to cover a specific area has increased. The installation cost burden on operators to install base stations has also increased. In order to minimize the installation cost of the base station, an arrangement may be assumed in which the DU (e.g., O-DU (430)) and RU (e.g., O-RU) of the base station (110) are separated and one or more RUs are connected to one DU via a wired network. In FIGS. 4A and 4B , the O-DU (430) is described as an entity that provides a cell to the terminal (120), but the O-DU (430) providing a cell may include one or more RUs that are connected to the O-DU (430) and are geographically distributed to cover multiple areas to provide coverage.
[0083] Figure 5 illustrates examples of components of DU.
[0084] Fig. 5 illustrates a configuration of a device according to embodiments of the present disclosure. The structure illustrated in Fig. 5 can be understood as a configuration of a device having at least one function among the Near-RT RIC, non-RT RIC, O-CU-CP, O-CU-UP, and O-DU described above. Terms such as "... unit" and "... device" used hereinafter mean a unit that processes at least one function or operation, and this can be implemented by hardware, software, or a combination of hardware and software.
[0085] Referring to FIG. 5, the device may include a transceiver (510), a memory (520), and a processor (530).
[0086] The transceiver (510) provides an interface for communicating with other devices within the network. That is, the transceiver (510) converts a bit string transmitted from a device to another device into a physical signal, and converts a physical signal received from another device into a bit string. That is, the transceiver (510) can transmit or receive signals. Accordingly, the transceiver (510) may be referred to as a modem, a communication unit, a transmit unit, a receive unit, or a transmit / receive unit. In this case, the transceiver (510) enables the device to communicate with other devices or systems via a backhaul connection (e.g., wired backhaul or wireless backhaul) or via a network. The transceiver (510) may include one or more transceivers.
[0087] The memory (520) stores data such as basic programs, application programs, and setting information for the operation of the device. The memory (520) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. In addition, the memory (520) provides stored data upon request from the processor (530). The memory (520) may be referred to as a storage unit.
[0088] The processor (530) controls the overall operations of the device. For example, the processor (530) transmits and receives signals via the transceiver (510). Additionally, the processor (530) writes and reads data to and from the memory (520). The processor (530) may be referred to as a control unit. For this purpose, the processor (530) may be composed of multiple processors or may include at least one sub-processor. According to various embodiments, the processor (530) may control the device to perform operations according to various embodiments described in the present disclosure.
[0089] The communication protocols defined in the O-RAN standard or 3GPP do not define interfaces between DUs and base stations or between DUs. As communication technology advances, the number of network entities increases, and communicating with external nodes (e.g., base stations, other DUs) through CUs causes delays. Therefore, interfaces between DUs or interfaces between DUs and base stations need to be defined. Hereinafter, a new interface and procedures and messages for configuring the interface are proposed for spectrum aggregation, such as the CA described above. Although procedures and messages related to the interface between DUs are described below, it should be understood that the descriptions can be applied in the same or similar manner to the interface between a DU and an independent base station (e.g., a base station of a small cell). In the present disclosure, when describing the interface between DUs, the DUs may be from the same vendor or different vendors. That is, information can be exchanged between DUs from different vendors through the interfaces and messages described below. Additionally, SFN synchronization between DUs can be achieved. For example, the global positioning system (GPS) or precision time protocol (PTP) can be used.
[0090] Fig. 6 illustrates an example of a first type of measurement procedure at an interface between DUs. The first type is a method of measuring latency at an interface between DUs through two-way signaling between DUs. The DUs are described in Figs. 2a to 2c and may include DUs (e.g., DU #1 (210-1), DU #2 (210-2), DU #1 (231), DU #2 (232)) that support an RLC layer protocol and a MAC layer protocol. For example, the DUs may include an O-DU (430) described in Figs. 4a to 4b.
[0091] Referring to FIG. 6, an F2 interface may be configured between DU #1 (610) and DU #2 (620). Meanwhile, the F2 interface is an inter-DU interface and may be referred to instead by other terms having the same technical meaning (e.g., M1, F3, MV, XD). Since the DU is responsible for the MAC layer, it can perform scheduling operations in the MAC layer. For the F2 interface, a protocol based on SCTP (streaming control transmission protocol) and UDP (user data protocol) (or GTP, L2, and / or IP) may be used between DUs. In a scenario where two DUs are distinguished (e.g., in the deployment scenario of FIG. 2a, FIG. 2b, or FIG. 2c), scheduling efficiency can be achieved by transmitting and / or receiving parameters for scheduling through the inter-DU interface.
[0092] In operation (601), DU #1 (610) may transmit an F2 measurement request message to DU #2 (620). The F2 measurement request message may be used to measure latency required in an F2 interface, for example, a communication interface between DU #1 (610) and DU #2 (620). According to one embodiment, the F2 measurement request message may include identification information related to DU #1 (610). For example, the F2 measurement request message may include base station information of DU #1 (610) (e.g., Global gNB ID) and identification information of DU #1 (610) (e.g., gNB-DU ID). According to one embodiment, the F2 measurement request message may additionally include identification information related to DU #2 (620). Identification information for DU #2 (620) can be obtained in advance through SCTP association of the interface. For example, the F2 measurement request message may include base station information of DU #2 (620) (e.g., Target Global gNB ID) and identification information of DU #2 (620) (e.g., gNB-DU ID). According to one embodiment, the F2 measurement request message may include system time information (e.g., gNB System Time). According to one embodiment, the F2 measurement request message may include information on a delay threshold (e.g., Delay threshold). The delay threshold may indicate an acceptable upper limit for communication to be possible on the F2 interface. For example, if the measured delay value exceeds the delay threshold, removal or release of the connection may be triggered, or the measurement request may be rejected. For example, the F2 measurement request message may have the following format.
[0093] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeMGlobal gNB IDMgNB-DU IDM or OUsed for CU-DU separated architecturegNB System TimeM or OX. Time Stamp(T1)Target Global gNB IDM or OTarget gNB-DU IDM or ODelay thresholdM or OAcceptable delay threshold for F2 link
[0094] The 'Message Type' IE indicates the type of the F2 measurement request message. The 'Message Type' IE may indicate a message code (e.g., one of the values 0 to 255 defined as 8 bits) and a message type. The message type may be one of 'initiation message', 'successful outcome', and 'unsuccessful outcome'. The 'Global gNB ID' IE may include the global ID of the gNB of DU #1 (610). The 'Global gNB ID' IE may be used to globally identify the gNB of DU #1 (610). The identification information indicated by the 'Global gNB ID' IE may consist of the PLMN ID and the gNB ID to which the gNB belongs. The MCC and the MNC may be the same as those included in the CGI. The CGI may consist of a mobile network code (MCC), a mobile country code (MNC), a local area code (LAC), and a cell identity (CI). The 'gNB-DU ID' IE may be identification information for uniquely identifying DU #1 (610) within the gNB. The 'Target Global gNB ID' IE may include the global ID of the gNB of DU #2 (620). The 'Target gNB-DU ID' IE may be identification information for uniquely identifying DU #2 (620) within the gNB. The 'gNB System Time' IE may indicate a system value (e.g., T1) of the time at which the F2 measurement request message was transmitted from DU #1 (610). The 'Delay Threshold' IE may include a delay threshold indicating an acceptable upper limit for enabling communication on the F2 interface.
[0095] 'M' represents a mandatory component for the message, and 'O' represents an optional component for the message. The 'M' and / or 'O' illustrated in the above table are exemplary, and a specific description is not to be construed as limiting a specific embodiment of the present disclosure.
[0096] In operation (603), DU #2 (620) may transmit an F2 measurement response message to DU #1 (610). The F2 measurement response message may be used to measure latency required in an F2 interface, for example, a communication interface between DU #1 (610) and DU #2 (620). According to one embodiment, the F2 measurement response message may include identification information related to DU #2 (620). For example, the F2 measurement response message may include base station information of DU #2 (620) (e.g., Global gNB ID) and identification information of DU #2 (620) (e.g., gNB-DU ID). According to one embodiment, the F2 measurement response message may additionally include identification information related to DU #1 (610). For example, the F2 measurement response message may include base station information of DU #1 (610) (e.g., Target Global gNB ID) and identification information of DU #1 (610) (e.g., gNB-DU ID). According to one embodiment, the F2 measurement response message may include system time information (e.g., gNB System Send Time, gNB System Received Time, gNB System Time). According to one embodiment, the F2 measurement response message may include information about a delay threshold (e.g., Delay threshold). The delay threshold may indicate an acceptable upper limit for communication to be possible on the F2 interface. For example, if the measured delay value exceeds the delay threshold, removal or release of the connection may be triggered. For example, the F2 measurement response message may have the following format.
[0097] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeMGlobal gNB IDMgNB-DU IDM or OgNB System Send TimeM or OX. Time StampT3gNB System Received TimeM or OX. Time StampT2Target Global gNB IDM or OTarget gNB-DU IDM or OTarget gNB System TimeM or OX. Time StampT1(If T1 is received before, it should be stored and returned to the target node)Delay thresholdM or OAcceptable delay threshold for F2 link
[0098] The 'Message Type' IE indicates the type of the F2 measurement response message. The 'Message Type' IE may indicate a message code (e.g., one of the values 0 to 255 defined as 8 bits) and a message type. The message type may be one of 'initiation message', 'successful outcome', and 'unsuccessful outcome'. The 'Global gNB ID' IE may include the global ID of the gNB of DU #2 (620). The 'Global gNB ID' IE may be used to globally identify the gNB of DU #2 (620). The identification information indicated by the 'Global gNB ID' IE may consist of a PLMN ID to which the gNB belongs and a gNB ID. The 'gNB-DU ID' IE may be identification information for uniquely identifying DU #2 (620) within the gNB. The 'Target Global gNB ID' IE may include the global ID of the gNB of DU #1 (610). The 'Target gNB-DU ID' IE may be identification information for uniquely identifying DU #1 (610) within the gNB. The 'gNB System Send Time' IE may indicate a system value of the time (e.g., T3) when the F2 measurement response message was transmitted from DU #2 (620). The 'gNB System Received Time' IE may indicate a system value of the time (e.g., T2) when the F2 measurement request message was received from DU #1 (610). The 'Target gNB System Time' IE may indicate a system value of the time (e.g., T1) when the F2 measurement request message was transmitted from DU #1 (610). The above system value can be obtained through information (e.g., 'gNB System Time' IE) received in operation (601).The 'Delay Threshold' IE may contain a delay threshold indicating an acceptable upper limit for communication to be possible over the F2 interface.
[0099] 'M' represents a mandatory component for the message, and 'O' represents an optional component for the message. The 'M' and / or 'O' illustrated in the above table are exemplary, and a specific description is not to be construed as limiting a specific embodiment of the present disclosure.
[0100] FIG. 7 is a diagram for explaining signaling of parameters for delay measurement at an interface between DUs. In FIG. 7, operations of DUs (e.g., DU #1 (610), DU #2 (620)) for measuring delay between DUs (the delay may be referred to as backhaul delay or midhaul delay) are described based on the F2 measurement request message and the F2 measurement response message described above with reference to FIG. 6. The DUs are described in FIGS. 2A to 2C and may include DUs (e.g., DU #1 (210-1), DU #2 (210-2), DU #1 (231), DU #2 (232)) that support a protocol of an RLC layer and a protocol of a MAC layer. For example, the DUs may include an O-DU (430) described in FIGS. 4A to 4B. For a description of each message in Fig. 7, reference may be made to the description of the messages in Fig. 6. In Fig. 7, the '*' symbol indicates an optional inclusion relationship.
[0101] Referring to FIG. 7, in operation (701), DU #1 (610) may transmit an F2 measurement request message to DU #2 (620). The F2 measurement request message may be transmitted from DU #1 (610) at a first system time (e.g., T1). Through propagation delay, the F2 measurement request message may reach DU #2 (620) at a second system time (e.g., T2).
[0102] In operation (703), DU #2 (620) may transmit an F2 measurement response message to DU #1 (610). DU #2 (620) may transmit the F2 measurement response message to DU #1 (610) after a certain time (e.g., Delta) from the second system time (e.g., T2) at which the F2 measurement request message is received. The F2 measurement response message may be transmitted from DU #2 (620) at a third system time (e.g., T3). The F2 measurement response message may reach DU #1 (610) at a fourth system time (e.g., T4).
[0103] DU #1 (610) can measure the link delay of the F2 interface between DU #1 (610) and DU #2 (620). DU #1 (610) can measure the link delay based on a first system time, a fourth system time, and difference information. The first system time indicates the time at which DU #1 (610) transmits an F2 measurement request message, and the fourth system time indicates the time at which DU #1 (610) receives an F2 measurement response message. The difference information may be the difference between the third system time and the second system time. For example, DU #1 (610) can measure the link delay based on the following mathematical equation.
[0104]
[0105] T4 represents the fourth system time, T1 represents the first system time, and Delta represents the difference information.
[0106] According to one embodiment, the difference information may be obtained from the second system time and the third system time included in the F2 measurement response message. For example, DU #1 (610) may obtain the 'gNB System Send Time' IE and the 'gNB System Received Time' IE from the F2 measurement response message having the format of Table 4. The 'gNB System Send Time' IE may indicate the third system time. The 'gNB System Received Time' IE may indicate the second system time. According to another embodiment, the difference information may be included in the F2 measurement response message. For example, DU #1 (610) may receive an F2 measurement response message including a value corresponding to a difference between the third system time and the second system time, unlike the format of Table 4. According to another embodiment, the difference information may be pre-configured.
[0107] DU #2 (620) can measure the link delay of the F2 interface between DU #1 (610) and DU #2 (620). DU #2 (620) can measure the link delay based on the difference between the first system time and the second system time. If both DU #1 (610) and DU #2 (620) are time-synchronized, and the link delay from DU #1 (610) to DU #2 (620) and the link delay from DU #2 (620) to DU #1 (610) are symmetric, the link delay can be obtained through a one-way measurement. For example, DU #2 (620) can measure the link delay based on the following mathematical equation.
[0108]
[0109] T2 represents the second system time, and T1 represents the first system time.
[0110] Although not shown in FIG. 7, delay condition analysis may be added to transmit the F2 measurement response message of operation (703). For example, DU #2 (620) may identify whether the measured link delay is greater than or equal to a delay threshold according to Equation 2. If the measured link delay is greater than or equal to the delay threshold, DU #2 (620) may transmit an F2 measurement failure message. If the measured link delay is less than or equal to the delay threshold, DU #2 (620) may transmit the F2 measurement response message according to operation (703).
[0111] In Fig. 7, DU #1 (610) can obtain link delay through bidirectional measurement, but DU #2 (620) can obtain link delay through unidirectional measurement. However, if the link delay from DU #1 (610) to DU #2 (620) and the link delay from DU #2 (620) to DU #1 (610) are not symmetrical, the link delay obtained through unidirectional measurement may be inaccurate. In order to obtain link delay through bidirectional measurement in DU #2 (620), the measurement procedure described in Figs. 6 and 7 may also be triggered in DU #2 (620).
[0112] Figures 8a to 8c are diagrams illustrating signaling for delay measurement. The DUs (e.g., DU #1 (610), DU #2 (620)) described in Figures 2a to 2c may include DUs (e.g., DU #1 (210-1), DU #2 (210-2), DU #1 (231), DU #2 (232)) that support the protocol of the RLC layer and the protocol of the MAC layer. For example, the DUs may include the O-DU (430) described in Figures 4a to 4b.
[0113] In FIG. 8a, the measurement procedures triggered in each of DU #1 (610) and DU #2 (620) are described.
[0114] Referring to FIG. 8A, in operation (801), DU #1 (610) may transmit an F2 SETUP REQUEST message to DU #2 (620). According to one embodiment, the F2 SETUP REQUEST message may include identification information of DU #1 (610) (e.g., 'Global gNB ID' IE, 'gNB-DU ID' IE). According to one embodiment, the F2 SETUP REQUEST message may transmit cell information of DU #1 (610). For example, the cell information may include cells that can be supported through DU #1 (610) and configuration information for each cell.
[0115] In operation (803), DU #2 (620) may transmit an F2 setup response (F2 SETUP RESPONSE) message to DU #1 (610). In one embodiment, the F2 setup response message may include identification information of DU #2 (620) (e.g., 'Global gNB ID' IE, 'gNB-DU ID' IE). In one embodiment, the F2 setup response message may transmit cell information of DU #2 (620). For example, the cell information may include cells that can be supported through DU #2 (620) and configuration information for each cell.
[0116] Through the above-described operations (801) and (803), after the F2 setup procedure is completed, the F2 measurement procedure can be initiated.
[0117] In operation (811), DU #1 (610) may transmit an F2 measurement request (F2 MEASUREMENT REQUEST) message to DU #2 (620). The descriptions of FIGS. 6 and 7 may be referenced for the F2 measurement request message. For example, the F2 measurement request message may include information about the time (e.g., T1) at which the F2 measurement request message was transmitted from DU #1 (610).
[0118] In operation (813), DU #2 (620) may transmit an F2 measurement response (F2 MEASUREMENT RESPONSE) message to DU #1 (610). The descriptions of FIGS. 6 and 7 may be referenced for the F2 measurement response message. For example, the F2 measurement response message may include information about the time (e.g., T2) at which the F2 measurement request message was received by DU #2 (620) and information about the time (e.g., T3) at which the F2 measurement response message was transmitted by DU #2 (620).
[0119] In operation (815), DU #1 (610) can analyze the delay condition. If the delay condition is not met, DU #1 (610) can maintain the connection on the F2 interface. For example, if the measured delay is lower than the delay threshold, DU #1 (610) can maintain the connection between DU #1 (610) and DU #2 (620). Although not shown in FIG. 8A, if the measured delay is lower than the delay threshold, DU #1 (610) can attempt to release the connection between DU #1 (610) and DU #2 (620).
[0120] In DU #1 (610), link delay can be measured through bidirectional measurement, but in DU #2 (620), link delay measurement through bidirectional measurement is difficult. As described above in Fig. 7, DU #2 (620) is only capable of unidirectional measurement, so DU #2 (620) can also initiate the measurement procedure in the same manner as DU #1 (610).
[0121] In operation (821), DU #2 (620) may transmit an F2 setup request message to DU #1 (610). In operation (823), DU #1 (610) may transmit an F2 setup response message to DU #2 (620). Meanwhile, if the F2 setup procedure between DU #1 (610) and DU #2 (620) is completed through operations (801) and (803), operations (821) and (823) may be omitted for simplification.
[0122] In operation (831), DU #2 (620) may transmit an F2 measurement request message to DU #1 (610). The descriptions of FIGS. 6 and 7 may be referenced for the F2 measurement request message. For example, the F2 measurement request message may include information about the time at which the F2 measurement request message of operation (831) was transmitted from DU #2 (620).
[0123] In operation (833), DU #1 (610) may transmit an F2 measurement response message to DU #2 (620). For the F2 measurement response message, the descriptions of FIGS. 6 and 7 may be referred to. For example, the F2 measurement response message may include information about the time at which the F2 measurement request message of operation (831) was received by DU #1 (610) and information about the time at which the F2 measurement response message of operation (833) was transmitted by DU #1 (610).
[0124] In operation (835), DU #2 (620) can analyze the delay condition. If the delay condition is not met, DU #2 (620) can maintain the connection on the F2 interface. For example, if the measured delay is lower than the delay threshold, DU #2 (620) can maintain the connection between DU #2 (620) and DU #1 (610). Although not shown in FIG. 8A, if the measured delay is lower than the delay threshold, DU #2 (620) can attempt to release the connection between DU #2 (620) and DU #1 (610).
[0125] In FIG. 8A, the measurement procedure of DU #2 (620) is described after the measurement procedure of DU #1 (610) is performed, but embodiments of the present disclosure are not limited thereto. Operations (801) to (815) may be performed in parallel with operations (823) to (835). For example, an operation (e.g., operation (815)) for determining whether to maintain a connection by analyzing a delay condition of DU #1 (610) may be performed independently from an operation (e.g., operation (835)) for determining whether to maintain a connection by analyzing a delay condition of DU #2 (620). According to one embodiment, if the connection between DU #1 (610) and DU #2 (620) is released based on the analysis result of operation (835), the measurement procedure of DU #1 (610) may be terminated. For example, in response to an F2 measurement request message from DU #1 (610), DU #2 (620) may transmit an F2 measurement failure message.
[0126] Referring to FIG. 8b, the measurement procedure and removal procedure triggered in DU #1 (610) are described.
[0127] In operation (841), DU #1 (610) may transmit an F2 SETUP REQUEST message to DU #2 (620). According to one embodiment, the F2 SETUP REQUEST message may include identification information of DU #1 (610) (e.g., 'Global gNB ID' IE, 'gNB-DU ID' IE). According to one embodiment, the F2 SETUP REQUEST message may transmit cell information of DU #1 (610). For example, the cell information may include cells that can be supported by DU #1 (610) and configuration information for each cell.
[0128] In operation (843), DU #2 (620) may transmit an F2 setup response (F2 SETUP RESPONSE) message to DU #1 (610). In one embodiment, the F2 setup response message may include identification information of DU #2 (620) (e.g., 'Global gNB ID' IE, 'gNB-DU ID' IE). In one embodiment, the F2 setup response message may transmit cell information of DU #2 (620). For example, the cell information may include cells that can be supported by DU #2 (620) and configuration information for each cell.
[0129] Through the above-described operations (841) and (843), after the F2 setup procedure is completed, the F2 measurement procedure can be initiated.
[0130] In operation (851), DU #1 (610) may transmit an F2 measurement request (F2 MEASUREMENT REQUEST) message to DU #2 (620). The descriptions of FIGS. 6 and 7 may be referenced for the F2 measurement request message. For example, the F2 measurement request message may include information about the time (e.g., T1) at which the F2 measurement request message was transmitted from DU #1 (610).
[0131] In operation (853), DU #2 (620) may transmit an F2 measurement response (F2 MEASUREMENT RESPONSE) message to DU #1 (610). The descriptions of FIGS. 6 and 7 may be referenced for the F2 measurement response message. For example, the F2 measurement response message may include information about the time (e.g., T2) at which the F2 measurement request message was received by DU #2 (620) and information about the time (e.g., T3) at which the F2 measurement response message was transmitted by DU #2 (620).
[0132] In operation (855), DU #1 (610) may analyze a delay condition. For example, if the measured delay is lower than a delay threshold, DU #1 (610) may attempt to disconnect the connection between DU #1 (610) and DU #2 (620).
[0133] In operation (860), DU #1 (610) may decide to remove F2. For example, DU #1 (610) may initiate an F2 removal request procedure to release the connection between DU #1 (610) and DU #2 (620).
[0134] In operation (861), DU #1 (610) may transmit an F2 removal request (F2 REMOVAL REQUEST) message to DU #2 (620). DU #1 (610) may initiate the procedure by sending the F2 removal request message to DU #2 (620). Upon receiving the F2 removal request message, DU #2 (620) may decide to remove all resources associated with the signaling connection. In one embodiment, DU #1 (610) may transmit identification information of DU #1 (610) to DU #2 (620) (e.g., gNB identification information, CU identification information, DU identification information). In one embodiment, DU #1 (610) may transmit cause information to DU #2 (620). For example, the F2 removal request message may have the following format.
[0135] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeMYESrejectGlobal gNB IDMgNB-DU IDM or OYESrejectTime to WaitM or OCauseM(TS38.473 9.3.1.2 Cause + additional Causes (ie, Long delay))YESignoreCriticality DiagnosticsO
[0136] The 'Message Type' IE indicates the type of the F2 removal request message. The 'Message Type' IE may indicate a message code (e.g., one of the values 0 to 255 defined as 8 bits) and a message type. The message type may be one of 'initiation message', 'successful outcome', and 'unsuccessful outcome'. The 'Global gNB ID' IE may include the global ID of the gNB. The 'gNB-DU ID' IE may be identification information for uniquely identifying DU #1 (610) within the gNB. The 'Time to Wait' IE may indicate the waiting time until the next setup procedure is initiated after the removal procedure is completed. The 'Cause' IE may indicate the cause for initiating the F2 removal procedure. The 'Cause' IE may indicate the reason for a particular event in the F2AP protocol. For example, the 'Cause' IE could point to a reason related to delays on the F2 interface (e.g. delays above a threshold).
[0137] In operation (863), DU #2 (620) may send an F2 REMOVAL RESPONSE message to DU #1 (610). For example, the F2 REMOVAL RESPONSE message may have the following format.
[0138] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeM YESrejectGlobal gNB IDM gNB-DU IDM or O YESrejectCriticality DiagnosticsM or O YESignore
[0139] The 'Message Type' IE indicates the type of the F2 removal response message. The 'Message Type' IE may indicate a message code (e.g., one of the values 0 to 255 defined as 8 bits) and a message type. The message type may be one of 'initial message', 'successful outcome', and 'unsuccessful outcome'. The 'Global gNB ID' IE may include the global ID of the gNB. The 'gNB-DU ID' IE may be identification information for uniquely identifying DU #2 (620) within the gNB (or within a common gNB-CU). The 'Criticality Diagnostics' IE may be transmitted when part of a received message is not understood or is missing, or when the message contains a logical error. The 'Criticality Diagnostics' IE may include information about the IEs that are not understood or are missing.
[0140] 'M' represents a mandatory component for the message, and 'O' represents an optional component for the message. The 'M' and / or 'O' illustrated in the above table are exemplary, and a specific description is not to be construed as limiting a specific embodiment of the present disclosure.
[0141] Referring to Fig. 8c, a delay measurement using the F2 setup procedure is described in DU #1 (610). In Figs. 8a and 8b, the F2 measurement procedure is described as being performed after the F2 setup procedure, but in Fig. 8c, the link delay of the F2 interface can be measured through messages of the F2 setup procedure.
[0142] In operation (871), DU #1 (610) may transmit an F2 setup request message to DU #2 (620). The F2 setup request message may include information for requesting delay measurement. For example, the F2 setup request message may include information for requesting delay measurement according to the first method. The first method represents a delay measurement method using bidirectional signaling, as described with reference to FIGS. 6 and 7. For example, the F2 setup request message may be configured as shown in the table below.
[0143] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeMGlobal gNB IDMgNB-DU IDM or ODelay Measurement RequestM or O(2-way delay measurement required,..)Delay thresholdM or OAcceptable delay threshold for F2 link
[0144] The 'Message Type' IE indicates the type of the F2 setup request message. The 'Global gNB ID' IE may include the global ID of the gNB. The 'gNB-DU ID' IE may be identification information to uniquely identify DU #1 (610) within the gNB. The 'Delay Measurement Request' IE may indicate that DU #1 (610) requests a measurement procedure to DU #2 (620). The 'Delay Threshold' IE may include a delay threshold indicating an acceptable upper limit for communication to be possible on the F2 interface.
[0145] In operation (873), DU #2 (620) may transmit an F2 setup response message to DU #1 (610). Through the F2 setup response message, a measurement procedure according to the first method of FIGS. 6 and 7 may be initiated. The F2 setup response message may include at least a portion of the IEs of the F2 measurement request message mentioned through FIGS. 6 and 7. For example, the F2 setup response message may include a system value of the time (e.g., T1) at which the F2 setup response message was transmitted from DU #2 (620). In addition, for example, the F2 setup response message may include information about a delay threshold (e.g., Delay threshold). The delay threshold may indicate an acceptable upper limit for enabling communication on the F2 interface. For example, the F2 setup response message may be configured as shown in the table below.
[0146] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeMGlobal gNB IDMgNB-DU IDM or OgNB System TimeM or OX. Time StampT1Delay thresholdM or OAcceptable delay threshold for F2 link
[0147] The 'Message Type' IE indicates the type of the F2 setup response message. The 'Global gNB ID' IE may include the global ID of the gNB. The 'gNB-DU ID' IE may be identification information for uniquely identifying DU #2 (620) within the gNB. The 'Delay Measurement Request' IE may indicate that DU #1 (610) requests a measurement procedure to DU #2 (620). The 'gNB System Time' IE may indicate a system value (e.g., T1) of the time at which DU #2 (620) transmitted the F2 setup response message. The 'Delay Threshold' IE may include a delay threshold indicating an acceptable upper limit for enabling communication on the F2 interface.
[0148] 'M' represents a mandatory component for the message, and 'O' represents an optional component for the message. The 'M' and / or 'O' illustrated in the above table are exemplary, and a specific description is not to be construed as limiting a specific embodiment of the present disclosure.
[0149] In operation (875), DU #1 (610) can perform delay condition analysis. DU #1 (610) can perform the delay condition analysis through one-way measurement. DU #1 (610) can record the time (e.g., T2) at which the F2 setup response message is received. DU #1 (610) can obtain the link delay through the difference between the recorded time and the time (e.g., T1) at which the F2 setup response message is transmitted. DU #1 (610) can identify whether the link delay value is greater than or equal to the delay threshold. If the link delay value is greater than or equal to the delay threshold, DU #1 (610) can trigger the release of the connection without performing an additional procedure. However, if the link delay value is less than the delay threshold, DU #1 (610) can continue the link delay measurement procedure through the operation described below. For example, DU #1 (610) can perform operation (881).
[0150] In operation (881), DU #2 (620) may transmit an F2 measurement response message. In one embodiment, the F2 measurement response message may include information (e.g., a system value) about a time (e.g., T2) at which the F2 setup response message was received and information (e.g., a system value) about a time (e.g., T3) at which the F2 measurement response message was transmitted. In another embodiment, the F2 measurement response message may include information about a difference between a time (e.g., T2) at which the F2 setup response message was received and a time (e.g., T3) at which the F2 measurement response message was transmitted. In another embodiment, if the difference between the time at which the F2 setup response message is received (e.g., T2) and the time at which the F2 measurement response message is transmitted (e.g., T3) is preset in DU #1 (610) and DU #2 (620), the F2 setup response message may include basic information (e.g., 'Message Type' IE, 'Global gNB ID' IE, 'gNB-DU ID' IE).
[0151] In FIG. 8C, an example of requesting delay measurement to DU #1 (610) via an F2 setup response message instead of an F2 measurement request message is described. However, embodiments of the present disclosure are not limited thereto. To trigger measurement according to the first method, an F2 setup request message may be used. For example, an F2 setup request message and an F2 setup response message may replace the F2 measurement request message and the F2 measurement response message, respectively. For example, the F2 setup request message may include information about a first system time (e.g., T1). The F2 setup response message may include information about a second system time (e.g., T2) and information about a third system time (e.g., T3).
[0152] In FIGS. 6 through 8c, a method for obtaining link delay through bidirectional measurement, which is the first method, is described for DU #1 (610). However, unless triggering occurs on both sides, unidirectional measurements will be present. For example, if the link delay from U #1 (610) to DU #2 (620) and the link delay from DU #2 (620) to DU #1 (610) are not symmetrical, the link delay obtained through unidirectional measurements may be inaccurate. Hereinafter, methods for obtaining link delay through 3-way measurements are described in the present disclosure.
[0153] Fig. 9a illustrates an example of a second method of a measurement procedure at an interface between DUs. The second method is a method of measuring latency at an interface between DUs through 3-way signaling between DUs. The DUs (e.g., DU #1 (610), DU #2 (620)) are described in Figs. 2a to 2c, and may include DUs (e.g., DU #1 (210-1), DU #2 (210-2), DU #1 (231), DU #2 (232)) that support an RLC layer protocol and a MAC layer protocol. For example, the DUs may include an O-DU (430) described in Figs. 4a to 4b.
[0154] Referring to FIG. 9A, in operation (901), DU #1 (610) may transmit an F2 Measurement Request message to DU #2 (620). The F2 Measurement Request message may be used to measure latency required in an F2 interface, for example, a communication interface between DU #1 (610) and DU #2 (620). According to one embodiment, the F2 Measurement Request message may include identification information related to DU #1 (610). For example, the F2 Measurement Request message may include base station information of DU #1 (610) (e.g., Global gNB ID) and identification information of DU #1 (610) (e.g., gNB-DU ID). According to one embodiment, the F2 Measurement Request message may additionally include identification information related to DU #2 (620). Identification information for DU #2 (620) can be obtained in advance through SCTP association of the interface. For example, the F2 measurement request message may include base station information of DU #2 (620) (e.g., Target Global gNB ID) and identification information of DU #2 (620) (e.g., gNB-DU ID). According to one embodiment, the F2 measurement request message may include system time information (e.g., gNB System Time). According to one embodiment, the F2 measurement request message may include information on a delay threshold (e.g., Delay threshold). The delay threshold may indicate an acceptable upper limit for communication to be possible on the F2 interface. For example, if the measured delay value exceeds the delay threshold, removal or release of the connection may be triggered. For example, the F2 measurement request message may have the following format.
[0155] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeMGlobal gNB IDMgNB-DU IDM or OUsed for CU-DU separated architecturegNB System TimeM or OX. Time Stamp(T1)Target Global gNB IDM or OTarget gNB-DU IDM or ODelay thresholdM or OAcceptable delay threshold for F2 link
[0156] The 'Message Type' IE indicates the type of the F2 measurement request message. The 'Message Type' IE may indicate a message code (e.g., one of the values 0 to 255 defined as 8 bits) and a message type. The message type may be one of 'initiation message', 'successful outcome', and 'unsuccessful outcome'. The 'Global gNB ID' IE may include the global ID of the gNB of DU #1 (610). The 'Global gNB ID' IE may be used to globally identify the gNB of DU #1 (610). The identification information indicated by the 'Global gNB ID' IE may consist of the PLMN ID and the gNB ID to which the gNB belongs. The MCC and the MNC may be the same as those included in the CGI. The CGI may consist of a mobile network code (MCC), a mobile country code (MNC), a local area code (LAC), and a cell identity (CI). The 'gNB-DU ID' IE may be identification information for uniquely identifying DU #1 (610) within the gNB. The 'Target Global gNB ID' IE may include the global ID of the gNB of DU #2 (620). The 'Target gNB-DU ID' IE may be identification information for uniquely identifying DU #2 (620) within the gNB. The 'gNB System Time' IE may indicate a system value (e.g., T1) of the time at which the F2 measurement request message was transmitted from DU #1 (610). The 'Delay Threshold' IE may include a delay threshold indicating an acceptable upper limit for enabling communication on the F2 interface.'M' represents a mandatory component for the message, and 'O' represents an optional component for the message. The 'M' and / or 'O' illustrated in the above table are exemplary, and a specific description is not to be construed as limiting a specific embodiment of the present disclosure.
[0157] In operation (903), DU #2 (620) may transmit an F2 Measurement Response message to DU #1 (610). The F2 Measurement Response message may be transmitted. The F2 Measurement Response message may be used to measure latency required in an F2 interface, for example, a communication interface between DU #1 (610) and DU #2 (620). According to one embodiment, the F2 Measurement Response message may include identification information related to DU #2 (620). For example, the F2 Measurement Response message may include base station information of DU #2 (620) (e.g., Global gNB ID) and identification information of DU #2 (620) (e.g., gNB-DU ID). According to one embodiment, the F2 Measurement Response message may additionally include identification information related to DU #1 (610). For example, the F2 measurement response message may include base station information of DU #1 (610) (e.g., Target Global gNB ID) and identification information of DU #1 (610) (e.g., gNB-DU ID). According to one embodiment, the F2 measurement response message may include system time information (e.g., gNB System Send Time, gNB System Received Time, gNB System Time). According to one embodiment, the F2 measurement response message may include information about a delay threshold (e.g., Delay threshold). The delay threshold may indicate an acceptable upper limit for communication to be possible on the F2 interface. For example, if the measured delay value exceeds the delay threshold, removal or release of the connection may be triggered. For example, the F2 measurement response message may have the following format.
[0158] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeMGlobal gNB IDMgNB-DU IDM or OgNB System Send TimeM or OX. Time StampT3gNB System Received TimeM or OX. Time StampT2Target Global gNB IDM or OTarget gNB-DU IDM or OTarget gNB System TimeM or OX. Time StampT1(If T1 is received before, it should be stored and returned to the target node)Delay thresholdM or OAcceptable delay threshold for F2 link
[0159] The 'Message Type' IE indicates the type of the F2 measurement response message. The 'Message Type' IE may indicate a message code (e.g., one of the values 0 to 255 defined as 8 bits) and a message type. The message type may be one of 'initiation message', 'successful outcome', and 'unsuccessful outcome'. The 'Global gNB ID' IE may include the global ID of the gNB of DU #2 (620). The 'Global gNB ID' IE may be used to globally identify the gNB of DU #2 (620). The identification information indicated by the 'Global gNB ID' IE may consist of a PLMN ID to which the gNB belongs and a gNB ID. The 'gNB-DU ID' IE may be identification information for uniquely identifying DU #2 (620) within the gNB. The 'Target Global gNB ID' IE may include the global ID of the gNB of DU #1 (610). The 'Target gNB-DU ID' IE may be identification information for uniquely identifying DU #1 (610) within the gNB. The 'gNB System Send Time' IE may indicate a system value of the time (e.g., T3) when the F2 measurement response message was transmitted from DU #2 (620). The 'gNB System Received Time' IE may indicate a system value of the time (e.g., T2) when the F2 measurement request message was received from DU #2 (620). The 'Target gNB System Time' IE may indicate a system value of the time (e.g., T1) when the F2 measurement request message was transmitted from DU #1 (610). The above system value can be obtained through information (e.g., 'gNB System Time' IE) received in operation (601).The 'Delay Threshold' IE may contain a delay threshold indicating an acceptable upper limit for communication to be possible over the F2 interface.
[0160] 'M' represents a mandatory component for the message, and 'O' represents an optional component for the message. The 'M' and / or 'O' illustrated in the above table are exemplary, and a specific description is not to be construed as limiting a specific embodiment of the present disclosure.
[0161] In operation (905), DU #1 (610) may transmit an F2 Measurement Complete message to DU #2 (620). For 3-way measurement, DU #1 (610) may transmit the F2 Measurement Complete message. DU #1 (610) may transmit the F2 Measurement Complete message to DU #2 (620) so that link delay can be obtained through bidirectional measurement.
[0162] According to one embodiment, the F2 measurement completion message may include identification information related to DU #1 (610). For example, the F2 measurement completion message may include base station information of DU #1 (610) (e.g., Global gNB ID) and identification information of DU #1 (610) (e.g., gNB-DU ID). According to one embodiment, the F2 measurement completion message may additionally include identification information related to DU #2 (620). For example, the F2 measurement completion message may include base station information of DU #2 (620) (e.g., Target Global gNB ID) and identification information of DU #2 (620) (e.g., gNB-DU ID). According to one embodiment, the F2 measurement completion message may include system time information (e.g., gNB System Send Time, gNB System Received Time, Target gNB System Time). According to one embodiment, the F2 measurement completion message may include information about a delay threshold (e.g., Delay threshold). For example, the F2 measurement completion message may have the following format:
[0163] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeMGlobal gNB IDMgNB-DU IDM or OgNB System Send TimeM or OX. Time StampT5gNB System Received TimeM or OX. Time StampT4Target Global gNB IDM or OTarget gNB-DU IDM or OTarget gNB System TimeM or OX. Time StampT3(If T3 is received before, it should be stored and returned to the target node)Delay thresholdM or OAcceptable delay threshold for F2 link
[0164] The 'Message Type' IE indicates the type of the F2 measurement completion message. The 'Message Type' IE may indicate a message code (e.g., one of the values 0 to 255 defined as 8 bits) and a message type. The 'Global gNB ID' IE may include the global ID of the gNB of DU #1 (610). The 'Global gNB ID' IE may be used to globally identify the gNB of DU #1 (610). The identification information indicated by the 'Global gNB ID' IE may consist of a PLMN ID and a gNB ID to which the gNB belongs. The 'gNB-DU ID' IE may be identification information for uniquely identifying DU #1 (610) within a gNB. The 'Target Global gNB ID' IE may include the global ID of the gNB of DU #2 (620). The 'Target gNB-DU ID' IE may be identification information for uniquely identifying DU #2 (620) within the gNB. The 'gNB System Send Time' IE may indicate a system value of the time (e.g., T5) at which the F2 measurement completion message is transmitted from DU #2 (620). The 'gNB System Received Time' IE may indicate a system value of the time (e.g., T4) at which the F2 measurement response message is received from DU #1 (610). The 'Target gNB System Time' IE may indicate a system value of the time (e.g., T3) at which the F2 measurement request message is transmitted from DU #2 (620). The system value may be obtained through information received in operation (903) (e.g., the 'gNB System Time' IE). The 'Delay Threshold' IE may include a delay threshold indicating an acceptable upper limit for enabling communication on the F2 interface.'M' represents a mandatory component for the message, and 'O' represents an optional component for the message. The 'M' and / or 'O' illustrated in the above table are exemplary, and a specific description is not to be construed as limiting a specific embodiment of the present disclosure.
[0165] FIG. 9B is a diagram for explaining signaling of parameters for delay measurement at an interface between DUs. In FIG. 9B, operations of DUs (e.g., DU #1 (610), DU #2 (620)) for measuring delay between DUs are described based on the F2 measurement request message, F2 measurement response message, and F2 measurement complete message described above through FIG. 9A. The DUs are described in FIGS. 2A to 2C and may include DUs (e.g., DU #1 (210-1), DU #2 (210-2), DU #1 (231), DU #2 (232)) that support the protocol of the RLC layer and the protocol of the MAC layer. For example, the DUs may include the O-DU (430) described in FIGS. 4A to 4B. For a description of each message in FIG. 9B, reference may be made to the description of the message in FIG. 9A. In Figure 9b, the '*' mark indicates an optional inclusion relationship.
[0166] Referring to FIG. 9B, in operation (951), DU #1 (610) may transmit an F2 Measurement Request message to DU #2 (620). The F2 Measurement Request message may be transmitted from DU #1 (610) at a first system time (e.g., T1). Due to propagation delay, the F2 Measurement Request message may reach DU #2 (620) at a second system time (e.g., T2).
[0167] In operation (953), DU #2 (620) may transmit an F2 Measurement Response message to DU #1 (610). DU #2 (620) may transmit the F2 Measurement Response message to DU #1 (610) after a certain time (e.g., Delta1) from the second system time (e.g., T2) at which the F2 Measurement Request message is received. The F2 Measurement Response message may be transmitted from DU #2 (620) at a third system time (e.g., T3). The F2 Measurement Response message may reach DU #1 (610) at a fourth system time (e.g., T4).
[0168] In operation (955), DU #1 (610) may transmit an F2 Measurement Complete message to DU #2 (620). DU #1 (610) may transmit the F2 Measurement Complete message to DU #2 (620) a predetermined time (e.g., Delta2) after the fourth system time (e.g., T4) at which the F2 Measurement Request message is received. The F2 Measurement Complete message may be transmitted from DU #1 (610) at a fifth system time (e.g., T5). The F2 Measurement Complete message may reach DU #2 (620) at a sixth system time (e.g., T6).
[0169] DU #1 (610) can measure the link delay of the F2 interface between DU #1 (610) and DU #2 (620). DU #1 (610) can measure the link delay based on a first system time, a fourth system time, and first difference information. The first system time indicates the time at which DU #1 (610) transmits an F2 measurement request message, and the fourth system time indicates the time at which DU #1 (610) receives an F2 measurement response message. The first difference information may be the difference between the third system time and the second system time. For example, DU #1 (610) can measure the link delay based on the following mathematical equation.
[0170]
[0171] T4 represents the fourth system time, T1 represents the first system time, and Delta1 represents the first difference information. The fourth system time and the first system time represent the system times recorded in DU #1 (610).
[0172] According to one embodiment, the first difference information may be obtained from the second system time and the third system time included in the F2 measurement response message. For example, DU #1 (610) may obtain the 'gNB System Send Time' IE and the 'gNB System Received Time' IE from the F2 measurement response message having the format of Table 10. The 'gNB System Send Time' IE may indicate the third system time. The 'gNB System Received Time' IE may indicate the second system time. According to another embodiment, the first difference information may be included in the F2 measurement response message. For example, DU #1 (610) may receive an F2 measurement response message including a value corresponding to a difference between the third system time and the second system time, unlike the format of Table 10. According to another embodiment, the first difference information may be pre-configured.
[0173] DU #2 (620) can measure the link delay of the F2 interface between DU #1 (610) and DU #2 (620). DU #2 (620) can measure the link delay based on the third system time, the sixth system time, and the second difference information. The third system time indicates the time at which DU #2 (620) transmits the F2 measurement response message, and the sixth system time indicates the time at which DU #2 (620) receives the F2 measurement completion message. The second difference information may be the difference between the fourth system time and the fifth system time. For example, DU #2 (620) can measure the link delay based on the following mathematical equation.
[0174]
[0175] T3 represents the third system time, T6 represents the sixth system time, and Delta2 represents the second difference information. The third system time and the sixth system time represent the system times recorded in DU #2 (620).
[0176] According to one embodiment, the second difference information may be obtained from the fourth system time and the fifth system time included in the F2 measurement response message. For example, DU #2 (620) may obtain the 'gNB System Send Time' IE and the 'gNB System Received Time' IE from the F2 measurement completion message having the format of Table 11. The 'gNB System Send Time' IE may indicate the fifth system time. The 'gNB System Received Time' IE may indicate the fourth system time. According to another embodiment, the second difference information may be included in the F2 measurement completion message. For example, DU #1 (610) may receive an F2 measurement completion message including a value corresponding to a difference between the fifth system time and the fourth system time, unlike the format of Table 10. According to another embodiment, the second difference information may be pre-configured.
[0177] Although not shown in FIG. 9B, delay condition analysis may be added to transmit the F2 measurement completion message of operation (953). For example, DU #1 (610) may identify whether the measured link delay is greater than or equal to the delay threshold according to Equation 3. If the measured link delay is greater than or equal to the delay threshold, DU #1 (610) may transmit an F2 measurement failure message instead of the F2 measurement completion message. If the measured link delay is less than the delay threshold, DU #1 (610) may transmit the F2 measurement completion message according to operation (953). In the same manner, DU #2 (620) may identify whether the measured link delay is greater than or equal to the delay threshold according to Equation 4. If the measured link delay is greater than or equal to the delay threshold, DU #2 (620) may trigger removal or release of the F2 connection. DU #2 (620) can maintain the F2 connection if the measured link delay is less than the delay threshold.
[0178] Figures 10a to 10c are diagrams illustrating signaling for delay measurement. The DUs (e.g., DU #1 (610), DU #2 (620)) described in Figures 2a to 2c may include DUs (e.g., DU #1 (210-1), DU #2 (210-2), DU #1 (231), DU #2 (232)) that support the protocol of the RLC layer and the protocol of the MAC layer. For example, the DUs may include the O-DU (430) described in Figures 4a to 4b.
[0179] Referring to FIG. 10A, in operation (1001), DU #1 (610) may transmit an F2 setup request message to DU #2 (620). According to one embodiment, the F2 setup request message may include identification information for DU #1 (610) (e.g., gNB-DU ID of DU #1 (610) and global ID of gNB of DU #1 (610)) and / or identification information for DU #2 (620) (e.g., gNB-DU ID of DU #2 (620) and global ID of gNB of DU #2 (620)) without additional fields for triggering measurement of link delay. DU #2 (620) may receive the F2 setup request message. DU #2 (620) can identify that the F2 measurement procedure is initiated after the F2 setup procedure is completed based on the F2 setup request message without the above additional field.
[0180] In operation (1003), DU #2 (620) may transmit an F2 setup response message to DU #1 (610). According to one embodiment, the F2 setup response message may include identification information for DU #1 (610) (e.g., gNB-DU ID of DU #1 (610) and global ID of gNB of DU #1 (610)) and / or identification information for DU #2 (620) (e.g., gNB-DU ID of DU #2 (620) and global ID of gNB of DU #2 (620)) without additional fields for triggering measurement of link delay. DU #1 (610) may receive the F2 setup response message. DU #1 (610) may identify that the F2 measurement procedure is initiated after the end of the F2 setup procedure based on the F2 setup response message without the additional fields.
[0181] In operation (1011), DU #1 (610) may transmit an F2 measurement request message to DU #2 (620). For the F2 measurement request message, the descriptions of FIGS. 9A and 9B may be referred to. For example, the F2 measurement request message may include a first system time (e.g., T1), which is information on the time at which the F2 measurement request message was transmitted from DU #1 (610).
[0182] In operation (1013), DU #2 (620) may transmit an F2 measurement response message to DU #1 (610). For the F2 measurement response message, the descriptions of FIGS. 9A and 9B may be referred to. For example, the F2 measurement response message may include a second system time (e.g., T2), which is information on the time point at which the F2 measurement request message was received by DU #2 (620), and a third system time (e.g., T3), which is information on the time point at which the F2 measurement response message was transmitted by DU #2 (620). As another example, the F2 measurement response message may include information on a difference between a second system time (e.g., T2) at which the F2 measurement request message was received by DU #2 (620) and a third system time (e.g., T3), which is information on the time point at which the F2 measurement response message was transmitted.
[0183] In operation (1015), DU #1 (610) may perform delay condition analysis. DU #1 (610) may measure link delay based on the time (e.g., T1) at which the F2 measurement request message is transmitted from DU #1 (610), the time (e.g., T4) at which the F2 measurement response message is received, and information (e.g., T2, T3, T3-T2) within the F2 measurement response message. DU #1 (610) may perform the delay condition analysis based on the value measured as the link delay. For example, DU #1 (610) may identify whether the link delay is greater than or equal to a delay threshold. If the link delay is greater than or equal to a delay threshold, DU #1 (610) may no longer perform the measurement procedure. DU #1 (610) may perform an F2 removal procedure to release the F2 connection. If the above link delay is less than the delay threshold, DU #1 (610) can perform the operation (1017) described below.
[0184] In operation (1017), DU #1 (610) may transmit an F2 measurement completion message to DU #2 (620). For the F2 measurement completion message, the descriptions of FIGS. 9A and 9B may be referred to. For example, the F2 measurement completion message may include a fourth system time (e.g., T4), which is information on a time point when the F2 measurement response message was received by DU #1 (610), and a fifth system time (e.g., T5), which is information on a time point when the F2 measurement completion message was transmitted by DU #1 (610). As another example, the F2 measurement response message may include information on a difference between a fourth system time (e.g., T4), which is information on a time point when the F2 measurement response message was received by DU #1 (610), and a fifth system time (e.g., T5), which is information on a time point when the F2 measurement completion message was transmitted.
[0185] In operation (1019), DU #2 (620) may perform delay condition analysis. DU #2 (620) may measure link delay based on the time at which the F2 measurement response message was transmitted (e.g., T3), the time at which the F2 measurement completion message was received (e.g., T6), and information within the F2 measurement response message (e.g., T4, T5, T5-T4). DU #2 (620) may perform the delay condition analysis based on the value measured as the link delay. For example, DU #2 (620) may identify whether the link delay is greater than or equal to a delay threshold. If the link delay is greater than or equal to a delay threshold, DU #2 (620) may no longer perform the measurement procedure. DU #2 (620) may perform an F2 removal procedure to release the F2 connection. If the above link delay is less than the delay threshold, DU #2 (620) can continue to communicate with DU #1 (610) via the F2 interface.
[0186] Referring to FIG. 10b, in operation (1031), DU #1 (610) may transmit an F2 setup request message to DU #2 (620). The F2 setup request message may include information for requesting delay measurement. For example, the F2 setup request message may include information for requesting delay measurement according to the second method. The second method represents a delay measurement method using bidirectional signaling, as described through FIGS. 9a and 9b. For example, the F2 setup request message may be configured as shown in the table below.
[0187] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeMGlobal gNB IDMgNB-DU IDM or ODelay Measurement RequestM or O(3-way delay measurement required,..)Delay thresholdM or OAcceptable delay threshold for F2 link
[0188] The 'Message Type' IE indicates the type of the F2 setup request message. The 'Global gNB ID' IE may include the global ID of the gNB. The 'gNB-DU ID' IE may be identification information to uniquely identify DU #1 (610) within the gNB. The 'Delay Measurement Request' IE may indicate that DU #1 (610) requests a measurement procedure to DU #2 (620). The 'Delay Threshold' IE may include a delay threshold indicating an acceptable upper limit for communication to be possible on the F2 interface.
[0189] 'M' represents a mandatory component for the message, and 'O' represents an optional component for the message. The 'M' and / or 'O' illustrated in the above table are exemplary, and a specific description is not to be construed as limiting a specific embodiment of the present disclosure.
[0190] In operation (1033), DU #2 (620) may transmit an F2 setup response message to DU #1 (610). The F2 setup response message may include trigger information in response to the F2 setup request message including the 'Delay Measurement Request' IE. The trigger information may be used to respond to the measurement request of DU #1 (610). In one embodiment, the trigger information may indicate that the measurement procedure is initiated by DU #2 (620). For example, DU #2 (620) may wait without transmitting the F2 setup request message until the overload is relieved or until a specified waiting time (e.g., the 'Time to Wait' IE of Table 5) expires. If DU #2 (620) receives an F2 setup request message including a measurement request from another DU (e.g., DU #1 (610)) before transmitting an F2 setup request message, DU #2 may determine whether to accept the measurement request. For example, if DU #2 (620) accepts the measurement request, it may generate the trigger information. DU #2 (620) may transmit an F2 setup response message including the generated trigger information to DU #1 (610). For another example, if DU #2 (620) does not accept the measurement request, it may transmit an F2 setup response message to DU #1 (610) without the trigger information or together with information requesting a trigger from DU #1 (610). Hereinafter, it is assumed that the F2 setup response message including the trigger information is transmitted.
[0191] In operation (1035), DU #1 (610) may wait for an F2 measurement request message. DU #1 (610) may identify the trigger information from the F2 setup response message. Based on the trigger information, DU #1 (610) may identify that DU #2 (620) will transmit an F2 measurement request message. DU #1 (610) may wait for the F2 measurement request message to be transmitted from DU #2 (620).
[0192] In operation (1041), DU #2 (620) may transmit an F2 measurement request message to DU #1 (610). For the F2 measurement request message, the descriptions of FIGS. 9A and 9B may be referred to. For example, the F2 measurement request message may include a first system time (e.g., T1), which is information on the time at which the F2 measurement request message was transmitted from DU #2 (620).
[0193] In operation (1043), DU #1 (610) may transmit an F2 measurement response message to DU #2 (620). For the F2 measurement response message, the descriptions of FIGS. 9A and 9B may be referred to. For example, the F2 measurement response message may include a second system time (e.g., T2), which is information on a time point when the F2 measurement request message was received by DU #1 (610), and a third system time (e.g., T3), which is information on a time point when the F2 measurement response message was transmitted by DU #1 (610). As another example, the F2 measurement response message may include information on a difference between a second system time (e.g., T2), which is information on a time point when the F2 measurement request message was received by DU #1 (610), and a third system time (e.g., T3), which is information on a time point when the F2 measurement response message was transmitted.
[0194] In operation (1045), DU #2 (620) may perform delay condition analysis. DU #2 (620) may measure link delay based on the time (e.g., T1) at which the F2 measurement request message is transmitted from DU #2 (620), the time (e.g., T4) at which the F2 measurement response message is received, and information (e.g., T2, T3, T3-T2) in the F2 measurement response message. DU #2 (620) may perform the delay condition analysis based on the value measured as the link delay. For example, DU #2 (620) may identify whether the link delay is greater than or equal to a delay threshold. If the link delay is greater than or equal to a delay threshold, DU #2 (620) may no longer perform the measurement procedure. DU #2 (620) may perform an F2 removal procedure to release the F2 connection. If the above link delay is less than the delay threshold, DU #2 (620) can perform the operation (1047) described below.
[0195] In operation (1047), DU #2 (620) may transmit an F2 measurement completion message to DU #1 (610). For the F2 measurement completion message, the descriptions of FIGS. 9A and 9B may be referred to. For example, the F2 measurement completion message may include a fourth system time (e.g., T4), which is information on a time point when the F2 measurement response message was received by DU #2 (620), and a fifth system time (e.g., T5), which is information on a time point when the F2 measurement completion message was transmitted by DU #2 (620). As another example, the F2 measurement response message may include information on a difference between a fourth system time (e.g., T4), which is information on a time point when the F2 measurement response message was received by DU #2 (620), and a fifth system time (e.g., T5), which is information on a time point when the F2 measurement completion message was transmitted.
[0196] In operation (1049), DU #1 (610) may perform delay condition analysis. DU #1 (610) may measure link delay based on the time at which the F2 measurement response message was transmitted (e.g., T3), the time at which the F2 measurement completion message was received (e.g., T6), and information within the F2 measurement response message (e.g., T4, T5, T5-T4). DU #1 (610) may perform the delay condition analysis based on the value measured as the link delay. For example, DU #1 (610) may identify whether the link delay is greater than or equal to a delay threshold. If the link delay is greater than or equal to a delay threshold, DU #1 (610) may no longer perform the measurement procedure. DU #1 (610) may perform an F2 removal procedure to release the F2 connection. If the above link delay is less than the delay threshold, DU #1 (610) can continue to communicate with DU #2 (620) via the F2 interface.
[0197] Referring to FIG. 10c, in operation (1061), DU #1 (610) may transmit an F2 setup request message to DU #2 (620). The F2 setup request message may include information for requesting delay measurement. For example, the F2 setup request message may include information for requesting delay measurement according to the second method. The second method represents a delay measurement method using bidirectional signaling, as described through FIGS. 9a and 9b. For example, the F2 setup request message may be configured as shown in Table 12.
[0198] In operation (1063), DU #2 (620) may transmit an F2 setup response message to DU #1 (610). The F2 setup response message may include trigger information in response to the F2 setup request message including the 'Delay Measurement Request' IE. The trigger information may be used to respond to a measurement request of DU #1 (610). If DU #2 (620) receives an F2 setup request message including a measurement request from another DU (e.g., DU #1 (610)) before transmitting the F2 setup request message, DU #2 may determine whether to accept the measurement request. For example, if DU #2 (620) does not accept the measurement request, DU #1 (610) may transmit an F2 setup response message including trigger information requesting a trigger to DU #1 (610).
[0199] In operation (1065), DU #2 (620) may wait for an F2 measurement request message. DU #1 (610) may determine to initiate an F2 measurement procedure based on the F2 setup response message. For example, DU #1 (610) may determine to initiate an F2 measurement procedure by transmitting an F2 measurement request message based on the trigger information. DU #2 (620) may wait for an F2 measurement request message to be transmitted from DU #1 (610) based on the F2 setup response message.
[0200] In operation (1071), DU #1 (610) may transmit an F2 measurement request message to DU #2 (620). For the F2 measurement request message, the descriptions of FIGS. 9A and 9B may be referred to. For example, the F2 measurement request message may include a first system time (e.g., T1), which is information on the time at which the F2 measurement request message was transmitted from DU #1 (610).
[0201] In operation (1073), DU #2 (620) may transmit an F2 measurement response message to DU #1 (610). For the F2 measurement response message, the descriptions of FIGS. 9A and 9B may be referred to. For example, the F2 measurement response message may include a second system time (e.g., T2), which is information on a time point when the F2 measurement request message was received by DU #2 (620), and a third system time (e.g., T3), which is information on a time point when the F2 measurement response message was transmitted by DU #2 (620). As another example, the F2 measurement response message may include information on a difference between a second system time (e.g., T2), which is information on a time point when the F2 measurement request message was received by DU #2 (620), and a third system time (e.g., T3), which is information on a time point when the F2 measurement response message was transmitted.
[0202] In operation (1075), DU #1 (610) may perform delay condition analysis. DU #1 (610) may measure link delay based on the time (e.g., T1) at which the F2 measurement request message is transmitted from DU #1 (610), the time (e.g., T4) at which the F2 measurement response message is received, and information (e.g., T2, T3, T3-T2) within the F2 measurement response message. DU #1 (610) may perform the delay condition analysis based on the value measured as the link delay. For example, DU #1 (610) may identify whether the link delay is greater than or equal to a delay threshold. If the link delay is greater than or equal to a delay threshold, DU #1 (610) may no longer perform the measurement procedure. DU #1 (610) may perform an F2 removal procedure to release the F2 connection. If the above link delay is less than the delay threshold, DU #1 (610) can perform the operation (1077) described below.
[0203] In operation (1077), DU #1 (610) may transmit an F2 measurement completion message to DU #2 (620). For the F2 measurement completion message, the descriptions of FIGS. 9A and 9B may be referred to. For example, the F2 measurement completion message may include a fourth system time (e.g., T4), which is information on a time point when the F2 measurement response message was received by DU #1 (610), and a fifth system time (e.g., T5), which is information on a time point when the F2 measurement completion message was transmitted by DU #1 (610). As another example, the F2 measurement response message may include information on a difference between a fourth system time (e.g., T4), which is information on a time point when the F2 measurement response message was received by DU #1 (610), and a fifth system time (e.g., T5), which is information on a time point when the F2 measurement completion message was transmitted.
[0204] In operation (1079), DU #2 (620) may perform delay condition analysis. DU #2 (620) may perform delay condition analysis. DU #2 (620) may measure link delay based on the time at which the F2 measurement response message was transmitted (e.g., T3), the time at which the F2 measurement completion message was received (e.g., T6), and information within the F2 measurement response message (e.g., T4, T5, T5-T4). DU #2 (620) may perform the delay condition analysis based on the value measured as the link delay. For example, DU #2 (620) may identify whether the link delay is greater than or equal to a delay threshold. If the link delay is greater than or equal to the delay threshold, DU #2 (620) may no longer perform the measurement procedure. DU #2 (620) may perform an F2 removal procedure to release the F2 connection. If the above link delay is less than the delay threshold, DU #2 (620) can continue to communicate with DU #1 (610) via the F2 interface.
[0205] Fig. 11 is a diagram illustrating signaling for delay measurement. Fig. 11 describes a situation in which an F2 setup procedure is initiated in each of the DUs. The DUs (e.g., DU #1 (610), DU #2 (620)) are described in Figs. 2a to 2c and may include DUs (e.g., DU #1 (210-1), DU #2 (210-2), DU #1 (231), DU #2 (232)) that support the protocol of the RLC layer and the protocol of the MAC layer. For example, the DUs may include the O-DU (430) described in Figs. 4a to 4b.
[0206] Referring to FIG. 11, in operation (1101), DU #1 (610) may transmit an F2 setup request message to DU #2 (620). The F2 setup request message may include information for requesting delay measurement. For example, the F2 setup request message may include information for requesting delay measurement according to the second method. The second method represents a delay measurement method using bidirectional signaling, as described through FIGS. 9A and 9B. For example, the F2 setup request message may be configured as shown in Table 12.
[0207] In operation (1103), DU #2 (620) may transmit an F2 setup request message to DU #1 (610). The F2 setup request message may include information for requesting delay measurement. For example, the F2 setup request message may include information for requesting delay measurement according to the second method. The second method represents a delay measurement method using bidirectional signaling, as described with reference to FIGS. 9A and 9B. For example, the F2 setup request message may be configured as shown in Table 12.
[0208] In operation (1105), DU #1 (610) may determine whether to accept the F2 setup request message of DU #2 (620). DU #1 (610) may wait for the F2 setup response message from DU #2 (620). However, DU #1 (610) may be configured to determine whether to accept the F2 setup request message of DU #2 (620) if it receives the F2 setup request message of DU #2 (620) while waiting for the F2 setup response message from DU #2 (620). This is because if both sides wait, the procedure may be delayed.
[0209] In operation (1107), DU #1 (610) may transmit an F2 measurement response message to DU #2 (620). The F2 measurement response message may include information indicating that DU #1 (610) will initiate measurement of link delay. For example, the F2 measurement response message may include '3-way Delay Measure OK'IE. Meanwhile, DU #2 (620) may also attempt to transmit the F2 measurement response message in the same manner as DU #1 (610). Here, if DU #2 (620) receives the F2 measurement response message from DU #1 (610) before transmitting the F2 measurement response message for operation (1101), DU #2 (620) may decide not to transmit the F2 measurement response message for operation (1101).
[0210] Fig. 12 is a diagram illustrating signaling for delay measurement. The DUs (e.g., DU #1 (610), DU #2 (620)) described in Figs. 2a to 2c may include DUs (e.g., DU #1 (210-1), DU #2 (210-2), DU #1 (231), DU #2 (232)) that support the protocol of the RLC layer and the protocol of the MAC layer. For example, the DUs may include the O-DU (430) described in Figs. 4a to 4b.
[0211] Referring to FIG. 12, an example is described in which the F2 setup request message and the F2 setup response message of the F2 setup procedure are used for measuring link delay. The F2 setup request message may include at least some of the parameters of the F2 measurement request message described in FIGS. 9A and 9B. The F2 setup response message may include at least some of the parameters of the F2 measurement response message described in FIGS. 9A and 9B.
[0212] In operation (1201), DU #1 (610) may transmit an F2 setup request message to DU #2 (620). According to one embodiment, the F2 setup request message may include a first system time (e.g., T1), which is information on the time at which the F2 setup request message was transmitted from DU #1 (610). In addition, the F2 setup request message may include information for indicating a delay threshold (hereinafter, referred to as a first delay threshold). For example, the F2 setup request message may have the following format.
[0213] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeGlobal gNB IDMgNB-DU IDM or ODelay Measurement RequestM or O(3-way delay measurement required,..)gNB System TimeM or OX.Time Stamp(T1)Delay thresholdM or OAcceptable delay threshold for F2 link
[0214] The 'Message Type' IE indicates the type of the F2 Setup Request message. The 'Global gNB ID' IE may include the global ID of the gNB. The 'gNB-DU ID' IE may be identification information to uniquely identify DU #1 (610) within the gNB. The 'Delay Measurement Request' IE may indicate that DU #1 (610) requests a measurement procedure to DU #2 (620). The 'gNB System Time' IE may indicate the time that DU #1 (610) transmitted the F2 Setup Request message to DU #2 (620). The 'Delay Threshold' IE may include a delay threshold indicating an acceptable upper limit for communication to be possible on the F2 interface. 'M' indicates a mandatory component for the message, and 'O' indicates an optional component for the message. The 'M' and / or 'O' illustrated in the above table are exemplary and should not be construed as limiting any particular embodiment of the present disclosure.
[0215] In operation (1203), DU #2 (620) may determine whether to accept the F2 setup request message of DU #1 (610). DU #2 (620) may obtain the first delay threshold based on the F2 setup request message. For example, DU #2 (620) may identify the first delay threshold from the F2 setup request message. DU #2 (620) may obtain information about the time at which the F2 setup request message was received. For example, DU #2 (620) may obtain the second system time (e.g., T2). DU #2 (620) may determine whether to accept the F2 setup request message based on the difference (e.g., Delta = T2-T1) between the second system time (e.g., T2) and the first system time (e.g., T1). For example, DU #2 (620) may decide to accept the F2 setup request message if the difference between the second system time and the first system time is greater than or equal to the first delay threshold. DU #2 (620) may decide to reject the F2 setup request message if the difference between the second system time and the first system time is less than the first delay threshold.
[0216] In the above-described embodiment, whether to accept the F2 setup request message is determined based on the first delay threshold value obtained through operation (1201), but embodiments of the present disclosure are not limited thereto. According to another embodiment, the determination of whether to accept the F2 setup request message may be determined based on an internal value stored in DU #2 (620). In this case, the first delay threshold value may not be included in the F2 setup request message.
[0217] If DU #2 (620) accepts the F2 setup request message of DU #1 (610), it can perform operation (1205). If DU #2 (620) does not accept the F2 setup request message of DU #1 (610), it can decide to terminate the measurement procedure. For example, DU #2 (620) can transmit an F2 setup failure message to DU #1 (610). An example of the F2 setup failure message is described in detail in FIG. 14. Meanwhile, although operation (1203) is illustrated in FIG. 12, the delay determination in operation (1203) is a procedure based on one-way measurement, which may result in an inaccurate determination. According to another embodiment, operation (1203) may be omitted. For example, if DU #2 (620) is configured not to utilize one-way delay, DU #2 (620) may perform action (1205) in response to the F2 setup request message.
[0218] In operation (1205), DU #2 (620) may transmit an F2 setup response message to DU #1 (610). DU #2 (620) may transmit the F2 setup response message so that DU #1 (610) may obtain the difference between the time of receiving the F2 setup request message and the time of transmitting the F2 setup response message. According to one embodiment, the F2 setup response message may include a second system time (e.g., T2), which is information on the time when the F2 setup request message was received by DU #2 (620), and a third system time (e.g., T3), which is information on the time when the F2 setup response message was transmitted by DU #2 (620). According to another embodiment, the F2 setup response message may include information on the difference between the second system time (e.g., T2) and the third system time (e.g., T3). According to another embodiment, the F2 setup response message may transmit an F2 setup response message including DU identification information (e.g., gNB-DU ID, Global gNB ID) without information about the system time. Here, the difference between the second system time (e.g., T2) and the third system time (e.g., T3) may be a pre-specified value. In addition, the F2 setup response message may include information for indicating a delay threshold (hereinafter, referred to as the second delay threshold). For example, the F2 setup response message may have the following format.
[0219] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeGlobal gNB IDMgNB-DU IDM or ODelay Measurement RequestM or O(3-way delay measurement required,..)gNB System TimeM or OX.Time Stamp(T1)gNB System Send TimeM or OX.Time StampT3gNB System Received TimeM or OX.Time StampT2Target Global gNB IDM or OTarget gNB-DU IDM or OTarget gNB System TimeM or OX.Time StampT1(If T1 is received before, it should be stored and returned to the target node)Delay thresholdM or OAcceptable delay threshold for F2 link
[0220] The 'Message Type' IE indicates the type of the F2 measurement response message. The 'Message Type' IE may indicate a message code (e.g., one of the values 0 to 255 defined as 8 bits) and a message type. The message type may be one of 'initiation message', 'successful outcome', and 'unsuccessful outcome'. The 'Global gNB ID' IE may include the global ID of the gNB of DU #2 (620). The 'Global gNB ID' IE may be used to globally identify the gNB of DU #2 (620). The identification information indicated by the 'Global gNB ID' IE may consist of a PLMN ID to which the gNB belongs and a gNB ID. The 'gNB-DU ID' IE may be identification information for uniquely identifying DU #2 (620) within the gNB. The 'Target Global gNB ID' IE may include the global ID of the gNB of DU #1 (610). The 'Target gNB-DU ID' IE may be identification information for uniquely identifying DU #1 (610) within the gNB. The 'gNB System Send Time' IE may indicate a system value of the time (e.g., T3) when the F2 measurement response message was transmitted from DU #2 (620). The 'gNB System Received Time' IE may indicate a system value of the time (e.g., T2) when the F2 measurement request message was received from DU #2 (620). The 'Target gNB System Time' IE may indicate a system value of the time (e.g., T1) when the F2 measurement request message was transmitted from DU #1 (610). The above system value can be obtained through information (e.g., 'gNB System Time' IE) received in operation (601).The 'Delay Threshold' IE may contain a delay threshold indicating an acceptable upper limit for communication to be possible over the F2 interface.
[0221] 'M' represents a mandatory component for the message, and 'O' represents an optional component for the message. The 'M' and / or 'O' illustrated in the above table are exemplary, and a specific description is not to be construed as limiting a specific embodiment of the present disclosure.
[0222] In operation (1207), DU #1 (610) may perform delay condition analysis. DU #1 (610) may measure link delay based on the time (e.g., T1) at which an F2 setup request message is transmitted from DU #1 (610), the time (e.g., T4) at which an F2 setup response message is received, and information (e.g., T2, T3, T3-T2) within the F2 setup response message. DU #1 (610) may perform the delay condition analysis based on the value measured as the link delay. For example, DU #1 (610) may identify whether the link delay is greater than or equal to a second delay threshold. If the link delay is greater than or equal to the second delay threshold, DU #1 (610) may no longer perform the measurement procedure. DU #1 (610) may perform an F2 removal procedure to release the F2 connection. If the link delay is less than the second delay threshold, DU #1 (610) may perform the operation (1209) described below. Meanwhile, according to another embodiment, the second delay threshold may be preset.
[0223] In operation (1209), DU #1 (610) may transmit an F2 measurement completion message to DU #2 (620). For the F2 measurement completion message, the descriptions of FIGS. 9A and 9B may be referred to. DU #1 (610) may transmit the F2 measurement completion message to DU #2 (620) so that DU #2 (620) may obtain the difference between the time of receiving the F2 setup response message and the time of transmitting the F2 measurement completion message. According to one embodiment, the F2 measurement completion message may include a fourth system time (e.g., T4), which is information on the time at which the F2 measurement response message was received by DU #1 (610), and a fifth system time (e.g., T5), which is information on the time at which the F2 measurement completion message was transmitted by DU #1 (610). According to another embodiment, the F2 measurement response message may include information about the difference between the fourth system time (e.g., T4), which is information about the time at which the F2 measurement response message was received in DU #1 (610), and the fifth system time (e.g., T5), which is information about the time at which the F2 measurement completion message was transmitted. According to another embodiment, the F2 measurement completion message may not include information about the system time. Here, the difference between the fourth system time (e.g., T4) and the fifth system time (e.g., T5) may be a pre-specified value.
[0224] In operation (1211), DU #2 (620) may perform delay condition analysis. DU #2 (620) may measure link delay based on the time at which the F2 measurement response message was transmitted (e.g., T3), the time at which the F2 measurement completion message was received (e.g., T6), and information within the F2 measurement response message (e.g., T4, T5, T5-T4). DU #2 (620) may perform the delay condition analysis based on the value measured as the link delay. For example, DU #2 (620) may identify whether the link delay is greater than or equal to a third delay threshold. If the link delay is greater than or equal to the third delay threshold, DU #2 (620) may no longer perform the measurement procedure. DU #2 (620) may perform an F2 removal procedure to release the F2 connection. If the link delay is less than the third delay threshold, DU #2 (620) can continuously communicate with DU #1 (610) via the F2 interface. Meanwhile, according to another embodiment, the third delay threshold may be preset.
[0225] Through the procedure illustrated in Fig. 12, since the parameters required for the F2 measurement procedure (e.g., system time, threshold value) are acquired in the F2 setup procedure, the F2 measurement request message and F2 measurement response message of the F2 measurement procedure are not required separately, so the measurement procedure can be simplified. By additionally performing only the transmission of the message of the measurement completion procedure of DU #1 (610), the link delay according to the 3-way method can be acquired in each of DU #1 (610) and DU #2 (620).
[0226] Fig. 13 is a diagram illustrating signaling for delay measurement. The DUs (e.g., DU #1 (610), DU #2 (620)) described in Figs. 2a to 2c may include DUs (e.g., DU #1 (210-1), DU #2 (210-2), DU #1 (231), DU #2 (232)) that support the protocol of the RLC layer and the protocol of the MAC layer. For example, the DUs may include the O-DU (430) described in Figs. 4a to 4b.
[0227] Referring to FIG. 13, in operation (1301), DU #1 (610) may transmit an F2 setup request message to DU #2 (620). The F2 setup request message may include information for requesting delay measurement. For example, the F2 setup request message may include information for requesting delay measurement according to the second method. The second method represents a delay measurement method using bidirectional signaling, as described with reference to FIGS. 9A and 9B. For example, the F2 setup request message may be configured as shown in the table below.
[0228] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeMGlobal gNB IDMgNB-DU IDM or ODelay Measurement RequestM or O(3-way delay measurement required,..)Delay thresholdM or OAcceptable delay threshold for F2 link
[0229] The 'Message Type' IE indicates the type of the F2 setup request message. The 'Global gNB ID' IE may include the global ID of the gNB. The 'gNB-DU ID' IE may be identification information to uniquely identify DU #1 (610) within the gNB. The 'Delay Measurement Request' IE may indicate that DU #1 (610) requests a measurement procedure to DU #2 (620). The 'Delay Threshold' IE may include a delay threshold indicating an acceptable upper limit for communication to be possible on the F2 interface.
[0230] 'M' represents a mandatory component for the message, and 'O' represents an optional component for the message. The 'M' and / or 'O' illustrated in the above table are exemplary, and a specific description is not to be construed as limiting a specific embodiment of the present disclosure.
[0231] In operation (1303), DU #2 (620) may transmit an F2 setup request message to DU #1 (610). The F2 setup response message may include trigger information in response to the F2 setup request message including the 'Delay Measurement Request' IE. The trigger information may be used to respond to a measurement request of DU #1 (610). According to one embodiment, the trigger information may indicate that a measurement procedure is initiated by DU #2 (620). To optimize the procedure, the F2 setup response message may include at least some of the parameters included in the F2 measurement request message of the measurement procedure. For example, the F2 measurement request message may include a first system time (e.g., T1), which is information on the time point at which the F2 setup response message was transmitted from DU #2 (620).
[0232] In operation (1305), DU #1 (610) may transmit an F2 measurement response message to DU #2 (620). For the F2 measurement response message, the descriptions of FIGS. 9A and 9B may be referred to. For example, the F2 measurement response message may include a second system time (e.g., T2), which is information on a time point when the F2 measurement request message was received by DU #1 (610), and a third system time (e.g., T3), which is information on a time point when the F2 measurement response message was transmitted by DU #1 (610). As another example, the F2 measurement response message may include information on a difference between a second system time (e.g., T2), which is information on a time point when the F2 measurement request message was received by DU #1 (610), and a third system time (e.g., T3), which is information on a time point when the F2 measurement response message was transmitted. Additionally, the F2 measurement response message may additionally include information about the first system time (e.g., T1).
[0233] In operation (1307), DU #2 (620) may perform delay condition analysis. DU #2 (620) may measure link delay based on the time (e.g., T1) at which the F2 measurement request message is transmitted from DU #2 (620), the time (e.g., T4) at which the F2 measurement response message is received, and information (e.g., T2, T3, T3-T2) in the F2 measurement response message. DU #2 (620) may perform the delay condition analysis based on the value measured as the link delay. For example, DU #2 (620) may identify whether the link delay is greater than or equal to a delay threshold. If the link delay is greater than or equal to a delay threshold, DU #2 (620) may no longer perform the measurement procedure. DU #2 (620) may perform an F2 removal procedure to release the F2 connection. If the above link delay is less than the delay threshold, DU #2 (620) can perform the operation (1309) described below.
[0234] In operation (1309), DU #2 (620) may transmit an F2 measurement completion message to DU #1 (610). For the F2 measurement completion message, the descriptions of FIGS. 9A and 9B may be referred to. For example, the F2 measurement completion message may include a fourth system time (e.g., T4), which is information on a time point when the F2 measurement response message was received by DU #2 (620), and a fifth system time (e.g., T5), which is information on a time point when the F2 measurement completion message was transmitted by DU #2 (620). As another example, the F2 measurement response message may include information on a difference between a fourth system time (e.g., T4), which is information on a time point when the F2 measurement response message was received by DU #2 (620), and a fifth system time (e.g., T5), which is information on a time point when the F2 measurement completion message was transmitted.
[0235] In operation (1311), DU #1 (610) may perform delay condition analysis. DU #1 (610) may perform delay condition analysis. Based on the time at which the F2 measurement response message is transmitted (e.g., T3), the time at which the F2 measurement completion message is received (e.g., T6), and information within the F2 measurement response message (e.g., T4, T5, T5-T4), DU #1 (610) may measure link delay. DU #1 (610) may perform the delay condition analysis based on the value measured as the link delay. For example, DU #1 (610) may identify whether the link delay is greater than or equal to a delay threshold. If the link delay is greater than or equal to a delay threshold, DU #1 (610) may no longer perform the measurement procedure. DU #1 (610) may perform an F2 removal procedure to release the F2 connection. If the above link delay is less than the delay threshold, DU #1 (610) can continue to communicate with DU #2 (620) via the F2 interface.
[0236] Fig. 14 illustrates an example of delay measurement using a setup procedure at an interface between DUs. In Fig. 14, a situation is described where the measurement procedure is terminated due to a long link delay during the setup procedure. The DUs (e.g., DU #1 (610), DU #2 (620)) are described in Figs. 2a to 2c, and may include DUs (e.g., DU #1 (210-1), DU #2 (210-2), DU #1 (231), DU #2 (232)) that support a protocol of the RLC layer and a protocol of the MAC layer. For example, the DUs may include an O-DU (430) described in Figs. 4a to 4b.
[0237] Referring to FIG. 14, in operation (1401), DU #1 (610) may transmit an F2 setup request message to DU #2 (620). According to one embodiment, the F2 setup request message may include a first system time (e.g., T1), which is information on the time at which the F2 setup request message was transmitted from DU #1 (610). In addition, the F2 setup request message may include information for indicating a delay threshold (hereinafter, referred to as a first delay threshold).
[0238] In operation (1403), DU #2 (620) may determine whether to accept the F2 setup request message of DU #1 (610). DU #2 (620) may obtain the first delay threshold based on the F2 setup request message. For example, DU #2 (620) may identify the first delay threshold from the F2 setup request message. DU #2 (620) may obtain information about the time at which the F2 setup request message was received. For example, DU #2 (620) may obtain the second system time (e.g., T2). DU #2 (620) may determine whether to accept the F2 setup request message based on the difference (e.g., Delta = T2-T1) between the second system time (e.g., T2) and the first system time (e.g., T1). For example, DU #2 (620) may decide to accept the F2 setup request message if the difference between the second system time and the first system time is greater than or equal to the first delay threshold. DU #2 (620) may decide to reject the F2 setup request message if the difference between the second system time and the first system time is less than the first delay threshold.
[0239] In the above-described embodiment, whether to accept the F2 setup request message is determined based on the first delay threshold value obtained through operation (1201), but embodiments of the present disclosure are not limited thereto. According to another embodiment, the determination of whether to accept the F2 setup request message may be determined based on an internal value stored in DU #2 (620). In this case, the first delay threshold value may not be included in the F2 setup request message.
[0240] If DU #2 (620) does not accept the F2 setup request message from DU #1 (610), it may decide to terminate the measurement procedure. To terminate the measurement procedure, DU #2 (620) may perform operation (1405).
[0241] In operation (1405), DU #2 (620) may transmit an F2 setup failure message to DU #1 (610). The F2 setup failure message may include cause information and / or wait time information. As an example, the following format may be referenced for the F2 setup failure message.
[0242] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCriticalityAssigned CriticalityMessage TypeMTransaction IDMCauseM or OY. Cause(long delay, ...)Time to WaitM or OCriticality DiagnosticsM or O
[0243] The 'Message Type' IE indicates the type of the F2 removal response message. The 'Message Type' IE may indicate a message code (e.g., one of the values from 0 to 255 defined as 8 bits) and the message type. The 'Transaction ID' may indicate an ID for distinguishing the transaction of this F2 setup failure message. The 'Cause' IE may indicate the cause of the failure of the F2 setup request. The 'Time to Wait' IE may indicate the waiting time until the next setup procedure is initiated (e.g., sending the F2 setup request message) after the F2 setup failure. The 'Criticality Diagnostics' IE may be sent when part of the received message is not understood or is missing, or when the message contains a logical error. The 'Criticality Diagnostics' IE may include information about the IE that is not understood or is missing. Although not shown in Table 16, the F2 setup failure message may further include a 'Global gNB ID' IE and / or a 'gNB-DU ID'. 'M' indicates a mandatory component for the message, and 'O' indicates an optional component for the message. The 'M' and / or 'O' illustrated in the above table are exemplary, and the specific description is not to be construed as limiting a specific embodiment of the present disclosure.
[0244] In one embodiment, the F2 setup failure message may include cause information. The cause information may indicate why the F2 setup failed. For example, the cause information may indicate a 'long delay.' As an example, the following format may be referenced for the cause information.
[0245] IE / Group NamePresenceRangeIE type and referenceSemantics descriptionCHOICE Cause GroupM> Radio Network Layer>> Radio Network Layer CauseMENUMERATED(Unspecified, ...lots of per UE-level inter-DU call processing error causes, ..., TBD (F2 inter-DU CA functional error causes)> Transport Layer>> Transport Layer CauseMENUMERATED(Unspecified, Transport Resource Unavailable, ... Long (Backhaul) Delay, ...)> Protocol>> Protocol CauseMENUMERATED(Transfer Syntax Error, Abstract Syntax Error (Reject),Abstract Syntax Error (Ignore and Notify),Message not Compatible with Receiver State,Semantic Error,Abstract Syntax Error (Falsely Constructed Message, Unspecified, ...)> Misc>> Miscellaneous CauseMENUMERATED(Control Processing Overload, Not enough User Plane Processing Resources, Hardware Failure, O&M Intervention, Unspecified, ...)
[0246] 'M' represents a mandatory component for the message, and 'O' represents an optional component for the message. The 'M' and / or 'O' illustrated in the above table are exemplary, and a specific description is not to be construed as limiting a specific embodiment of the present disclosure. According to one embodiment, the F2 setup failure message may include wait time information. The wait time information may indicate a wait time until the next setup procedure is initiated after the setup procedure is terminated. The setup procedure cannot be initiated before the wait time has elapsed. In other words, DU #1 (610) cannot transmit an F2 setup request message before the wait time expires after receiving the F2 setup failure message.
[0247] In operation (1407), DU #1 (610) may transmit an F2 setup request message to DU #2 (620). After the waiting time has elapsed from the time point at which DU #1 (610) receives the F2 setup failure message from DU #2 (620), DU #1 (610) may transmit an F2 setup request message to DU #2 (620). The F2 setup request message may be independent from the F2 setup request message of operation (1401). For example, the F2 setup request message may include a seventh system time (e.g., T1'), which is information on the time point at which the F2 setup request message was transmitted from DU #1 (610). In addition, the F2 setup request message may include information for indicating a delay threshold. The above delay threshold can be distinguished from the delay threshold of the F2 setup request message of operation (1401).
[0248] Although FIG. 14 describes a situation in which the measurement procedure is terminated when the link delay exceeds the delay threshold during the F2 setup procedure, embodiments of the present disclosure are not limited thereto. If DU #2 (620) identifies that the link delay between DU #1 (610) and DU #2 (620) is greater than or equal to the set threshold, DU #2 (620) may terminate the procedure regardless of the ongoing procedure. According to one embodiment, DU #2 (620) may notify DU #1 (610) of the termination of the measurement procedure by including the cause information and / or the waiting time information in the F2 setup request message.
[0249] Fig. 15 illustrates an example of a removal procedure at an interface between DUs. The DUs (e.g., DU #1 (610), DU #2 (620)) may include DUs (e.g., DU #1 (210-1), DU #2 (210-2), DU #1 (231), DU #2 (232)) that support the protocol of the RLC layer and the protocol of the MAC layer, as described in Figs. 2a to 2c. For example, the DUs may include the O-DU (430) described in Figs. 4a to 4b.
[0250] Referring to FIG. 15, in operation (1505), delay measurement can be performed through a delay measurement procedure between DU #1 (610) and DU #2 (620) (e.g., delay measurement according to the first method of FIGS. 6 to 8c and delay measurement according to the second method of FIGS. 9a to 13).
[0251] In operation (1511), DU #2 (620) may perform delay condition analysis. DU #2 (620) may obtain the link delay between DU #1 (610) and DU #2 (620). DU #2 (620) may identify whether the link delay is greater than or equal to a delay threshold. If the link delay is greater than or equal to a delay threshold, DU #2 (620) may no longer perform the measurement procedure. DU #2 (620) may perform operation (1513) to release the F2 connection.
[0252] At action (1513), DU #2 (620) may decide to initiate the F2 removal procedure.
[0253] In operation (1515), DU #2 (620) may transmit an F2 removal request message to DU #1 (610). DU #1 (610) may initiate the procedure by sending the F2 removal request message to DU #2 (620). Upon receiving the F2 removal request message, DU #2 (620) may decide to remove all resources associated with the signaling connection. In one embodiment, DU #1 (610) may transmit identification information of DU #1 (610) to DU #2 (620) (e.g., gNB identification information, CU identification information, DU identification information). In one embodiment, DU #1 (610) may transmit cause information to DU #2 (620). For example, the F2 removal request message may have the format of Table 5.
[0254] In operation (1517), DU #1 (610) may send an F2 removal response message to DU #2 (620). For example, the F2 removal response message may have the format of Table 6.
[0255] Although the disconnection through the F2 removal procedure is described in FIG. 15, embodiments of the present disclosure are not limited thereto. DU #1 (610) may disconnect the F2 interface connection by disconnecting the SCTP connection. In this case, an F2 setup request message may be transmitted to DU #2 (620), but DU #1 (610) may not respond, resulting in disconnection.
[0256] Although the gNB and the DU of the gNB (e.g., gNB-DU) are described as examples in the drawings and tables described above, embodiments of the present disclosure are not limited thereto. For example, the DU may be a network entity of the eNB. To identify the DU in the messages described above (e.g., F2 Setup Request Message, F2 Setup Response Message, F2 Measurement Request Message, F2 Measurement Response Message, F2 Removal Request Message, F2 Removal Response Message), the global eNB ID and / or the eNB-DU ID may be used.
[0257] In this disclosure, messages containing information about the system time are described to measure the delay of the interface between DUs. In the table described above, 'X. Time Stamp' is a 'Time Stamp' IE defined in Section X, and represents a type that represents the system time. The system time can be expressed in one of various ways.
[0258] In one embodiment, the system time of the 'Time Stamp' IE may be expressed as a time stamp based on the table below. A time stamp available in the F1AP (F1 application protocol) (e.g., TS 38.473 9.3.1.171) may be used for the F2 interface.
[0259] IE / Group NamePresenceRangeIE Type and ReferenceSemantics DescriptionCriticalityAssigned CriticalitySystem Frame NumberMINTEGER(0..1023)-CHOICESlot IndexM->SCS-15>>SCS-15MINTEGER(0..9)->SCS-30>>SCS-30MINTEGER(0..19)->SCS-60>>SCS-60MINTEGER (0..39)->SCS-120>>SCS-120MINTEGER(0..79)->SCS-480>>SCS-480MINTEGER(0..319)YESreject>SCS-960- >>SCS-960MINTEGER(0..639)YESrejectMeasurement TimeORelative Time 19009.3.1.183-
[0260] The 'System Frame Number' IE indicates an SFN, which has a value of one of 1024. The 'Slot Index' can indicate a slot number according to the numerology. As the subcarrier spacing (SCS) increases, the number of slots within the SFN can increase.
[0261] As the SCS increases, the range of slot numbers may increase. The 'Measurement Time' IE indicates the measured point in time, and its format indicates the initialization time (e.g., the cell's system frame number (SFN) initialization time, the requested time for action, etc.). The format in the table below can be referenced for the 'Measurement Time' IE.
[0262] IE / Group NamePresenceRangeIE Type and ReferenceSemantics DescriptionRelative Time 1900M BIT STRING (SIZE(64))Time in seconds relative to 00:00:00 on 1 January 1900 (calculated as continuous time without leap seconds and traceable to a common time reference) where binary encoding of the integer part is in the first 32 bits and binary encoding of the fraction part in the last 32 bits. The fraction part is expressed with a granularity of 1 / 2**32 second
[0263] In one embodiment, the arrangement and inclusion relationship of IEs may be changed to indicate the system time of the 'Time Stamp' IE. For example, [Table 18] may be changed as shown below.
[0264] IE / Group NamePresenceRangeIE Type and ReferenceSemantics DescriptionCriticalityAssigned CriticalityMeasurement TimeMRelative Time 19009.3.1.183-System Frame NumberOINTEGER(0..1023)-CHOICESlot IndexO ->SCS-15 >>SCS-15MINTEGER(0..9)->SCS-30 >>SCS-30MINTEGER(0..19)->SCS-60 >>SCS-60MINTEGER(0..39)->SCS-120 >>SCS-120MINTEGER(0..79)->SCS-480 >>SCS-480MINTEGER(0..319)YESreject>SCS-960 ->>SCS-960MINTEGER(0..639)YESreject
[0265] In one embodiment, the system time of the 'Time Stamp' IE may be expressed as a time stamp based on the table below. A time stamp available for PDU (protocol data unit) session control (e.g., TS 38.415) may be used for the F2 interface.
[0266] IE / Group NamePresenceRangeIE Type and ReferenceSemantics DescriptionTime StampMBIT STRING (SIZE(64))This field indicates the timestamp which is encoded in the same format as the 64-bit timestamp format as defined in Section 6 of IETF RFC 5905 [6].
[0267] In Section 6 of 'RFC 5905', time can be expressed in 32-bits for seconds and fractions, respectively. For example, the time can be expressed in the NTP (network time protocol) timestamp format (1600) of Fig. 16. The range of the 'Time Stamp' value is 0 to 2. 64 -It could be 1.
[0268] According to embodiments of the present disclosure, a method performed by a first distributed unit (DU) is provided. The method may include transmitting a measurement request message to a second DU via a communication interface between the first DU and the second DU. The method may include receiving a measurement response message from the second DU via the communication interface. The measurement request message may include a global ID for a base station of the first DU, first identification information of the first DU at the base station, and first time information indicating a first system time at which the measurement request message was transmitted from the first DU. The measurement response message may include a global ID for a base station of the second DU, second identification information of the second DU at the base station, and second time information. The second time information may be used to identify a difference between a second system time at which the measurement request message was received at the second DU and a third system time at which the measurement response message was transmitted from the second DU.
[0269] According to an exemplary embodiment, the second time information may include information about the second system time and information about the third system time.
[0270] According to an exemplary embodiment, the second time information may include first difference information indicating a difference between the second system time and the third system time.
[0271] According to an exemplary embodiment, the method may further include obtaining a link delay between the first DU and the second DU based on the first system time, the second system time, the third system time, and the fourth system time. The fourth system time may indicate a time at which the measurement response message is received at the first DU.
[0272] According to an exemplary embodiment, the link delay may be determined as a value obtained by dividing the difference between a first difference value and a second difference value by 2. The first difference value may represent a time interval from the first system time to the fourth system time. The second difference value may represent a time interval from the second system time to the third system time.
[0273] According to an exemplary embodiment, the measurement request message may further include information regarding a delay threshold. If the link delay between the first DU and the second DU is greater than or equal to the delay threshold, a disconnection between the first DU and the second DU may be triggered.
[0274] According to an exemplary embodiment, the method may further include transmitting a measurement complete message to the second DU via the communication interface. The measurement complete message may include a global ID for a base station of the first DU, the first identification information of the first DU at the base station, and third time information. The third time information may be used to identify a difference between a fourth system time at which the measurement response message was received from the first DU and a fifth system time at which the measurement complete message was transmitted from the first DU.
[0275] According to an exemplary embodiment, the method may include transmitting a removal request message to the second DU via the interface for releasing a connection between the first DU and the second DU. The method may include receiving a removal response message from the second DU via the interface. The removal request message may include information about a designated waiting time. The first DU may be configured not to initiate a setup procedure during the designated waiting time after the connection between the first DU and the second DU is released. For example, the removal request message may further include cause information. The cause information may indicate that a link delay in the communication interface is greater than or equal to a designated delay threshold.
[0276] According to an exemplary embodiment, the method may include transmitting a setup request message to the second DU through the interface. The method may further include receiving a setup response message from the second DU through the interface. The setup request message may include information indicating a request for delay measurement on the interface between the first DU and the second DU. The setup response message may include information indicating whether to accept or reject the request for delay measurement.
[0277] According to embodiments of the present disclosure, an electronic device for a first distributed unit (DU) is provided. The electronic device may include a memory storing one or more instructions. When the one or more instructions are executed, the one or more instructions may cause the first DU to transmit a measurement request message to a second DU through a communication interface between the first DU and the second DU. When the one or more instructions are executed, the one or more instructions may cause the first DU to receive a measurement response message from the second DU through the communication interface. The measurement request message may include a global ID for a base station of the first DU, first identification information of the first DU at the base station, and first time information indicating a first system time at which the measurement request message was transmitted from the first DU. The measurement response message may include a global ID for the base station of the second DU, second identification information of the second DU at the base station, and second time information. The second time information may be used to identify a difference between a second system time at which the measurement request message was received by the second DU and a third system time at which the measurement response message was transmitted by the second DU.
[0278] According to an exemplary embodiment, the second time information may include information about the second system time and information about the third system time.
[0279] According to an exemplary embodiment, the second time information may include first difference information indicating a difference between the second system time and the third system time.
[0280] According to an exemplary embodiment, when the one or more instructions are executed, the one or more instructions may cause the first DU to obtain a link delay between the first DU and the second DU based on the first system time, the second system time, the third system time, and a fourth system time. The fourth system time may indicate a time at which the measurement response message is received at the first DU.
[0281] According to an exemplary embodiment, the link delay may be determined as a value obtained by dividing the difference between a first difference value and a second difference value by 2. The first difference value may represent a time interval from the first system time to the fourth system time. The second difference value may represent a time interval from the second system time to the third system time.
[0282] According to an exemplary embodiment, the measurement request message may further include information regarding a delay threshold. If the link delay between the first DU and the second DU is greater than or equal to the delay threshold, a disconnection between the first DU and the second DU may be triggered.
[0283] In an exemplary embodiment, when the one or more instructions are executed, the one or more instructions may cause the first DU to transmit a measurement complete message to the second DU via the communication interface. The measurement complete message may include a global ID for a base station of the first DU, the first identification information of the first DU at the base station, and third time information. The third time information may be used to identify a difference between a fourth system time at which the measurement response message was received from the first DU and a fifth system time at which the measurement complete message was transmitted from the first DU.
[0284] In an exemplary embodiment, when the one or more instructions are executed, the one or more instructions may cause the first DU to transmit a removal request message to the second DU via the interface to disconnect the connection between the first DU and the second DU. When the one or more instructions are executed, the one or more instructions may cause the second DU to receive a removal response message via the interface. The removal request message may indicate information about a designated waiting time. The first DU may be configured not to initiate a setup procedure during the designated waiting time after the connection between the first DU and the second DU is disconnected.
[0285] According to an exemplary embodiment, the removal request message may further include cause information. The cause information may indicate that the link delay in the communication interface is greater than a specified delay threshold.
[0286] According to an exemplary embodiment, when the one or more instructions are executed, the one or more instructions may cause the first DU to transmit a setup request message to the second DU through the interface and to receive a setup response message from the second DU through the interface. The setup request message may include information indicating a request for delay measurement on the interface between the first DU and the second DU. The setup response message may include information indicating whether to accept or reject the request for delay measurement.
[0287] According to embodiments of the present disclosure, an electronic device of a first distributed unit (DU) is provided. The electronic device may include at least one transceiver, at least one processor, and a memory. The at least one processor may be operatively coupled to the memory and the at least one transceiver. The at least one processor may be configured to transmit a measurement request message to a second DU via a communication interface between the first DU and the second DU. The at least one processor may be configured to receive a measurement response message from the second DU via the communication interface. The measurement request message may include a global ID for a base station of the first DU, first identification information of the first DU at the base station, and first time information indicating a first system time at which the measurement request message was transmitted from the first DU. The measurement response message may include a global ID for the base station of the second DU, second identification information of the second DU at the base station, and second time information. The second time information may be used to identify a difference between a second system time at which the measurement request message was received by the second DU and a third system time at which the measurement response message was transmitted by the second DU.
[0288] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.
[0289] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors in an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specifications of the present disclosure. The one or more programs may be provided as included in a computer program product. The computer program product may be traded between sellers and buyers as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read only memory (CD-ROM)) or an application store (e.g., Play Store). ™ ) or directly between two user devices (e.g., smart phones), online distribution (e.g., downloading or uploading). In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or temporarily created in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.
[0290] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc-ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.
[0291] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.
[0292] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.
[0293] According to embodiments, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., modules or programs) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. According to embodiments, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.
[0294] Meanwhile, although the detailed description of the present disclosure has described specific embodiments, it is obvious that various modifications are possible within the scope of the present disclosure.
Claims
1. In a method performed by the first DU (distributed unit), Transmitting a measurement request message to the second DU through the communication interface between the first DU and the second DU, Including receiving a measurement response message from the second DU through the communication interface, The measurement request message includes a global ID for the base station of the first DU, first identification information of the first DU at the base station, and first time information indicating a first system time at which the measurement request message was transmitted from the first DU. The above measurement response message includes a global ID for the base station of the second DU, second identification information of the second DU at the base station, and second time information, The second time information is used to identify the difference between the second system time at which the measurement request message is received in the second DU and the third system time at which the measurement response message is transmitted in the second DU. method.
2. In claim 1, The second time information includes information about the second system time and information about the third system time. method.
3. In claim 1, The second time information includes first difference information indicating the difference between the second system time and the third system time. method.
4. In claim 1, Further comprising obtaining a link delay between the first DU and the second DU based on the first system time, the second system time, the third system time, and the fourth system time, The above fourth system time indicates the time at which the measurement response message is received in the first DU. method.
5. In claim 4, The above link delay is determined by dividing the difference between the first difference value and the second difference value by 2, The above first difference value represents the time interval from the first system time to the fourth system time, The second difference value represents the time interval from the second system time to the third system time. method.
6. In claim 4, The above measurement request message further includes information about the delay threshold, If the link delay between the first DU and the second DU is greater than or equal to the delay threshold, the release of the connection between the first DU and the second DU is triggered. method.
7. In claim 1, Further comprising transmitting a measurement complete message to the second DU through the communication interface, The above measurement completion message includes a global ID for the base station of the first DU, the first identification information of the first DU at the base station, and third time information, The third time information is used to identify the difference between the fourth system time at which the measurement response message was received in the first DU and the fifth system time at which the measurement completion message was transmitted in the first DU. method.
8. In claim 1, Transmitting a removal request message to the second DU through the interface to release the connection between the first DU and the second DU, Further comprising receiving a removal response message from the second DU through the interface, The above removal request message includes information about the specified waiting time, The first DU is configured not to initiate a setup procedure for the specified waiting time after the connection between the first DU and the second DU is released. method.
9. In claim 8, The above removal request message further includes cause information, The above cause information indicates that the link delay in the communication interface is greater than a specified delay threshold. method.
10. In claim 1, Transmit a setup request message to the above second DU through the above interface, Further comprising receiving a setup response message from the second DU through the interface, The above setup request message includes information indicating a request for delay measurement on the interface between the first DU and the second DU, The above setup response message includes information indicating whether to accept or reject the request for the delay measurement. method.
11. In an electronic device for the first DU (distributed unit), Contains memory that stores one or more instructions, When the one or more instructions above are executed, the one or more instructions, the first DU Transmitting a measurement request message to the second DU through the communication interface between the first DU and the second DU, Causing a measurement response message to be received from the second DU through the communication interface, The measurement request message includes a global ID for the base station of the first DU, first identification information of the first DU at the base station, and first time information indicating a first system time at which the measurement request message was transmitted from the first DU. The above measurement response message includes a global ID for the base station of the second DU, second identification information of the second DU at the base station, and second time information, The second time information is used to identify the difference between the second system time at which the measurement request message is received in the second DU and the third system time at which the measurement response message is transmitted in the second DU. device.
12. In claim 11, The second time information includes information about the second system time and information about the third system time. Electronic devices.
13. In claim 11, The second time information includes first difference information indicating the difference between the second system time and the third system time. Electronic devices.
14. In claim 11, When the one or more instructions are executed, the one or more instructions cause the first DU to obtain a link delay between the first DU and the second DU based on the first system time, the second system time, the third system time, and the fourth system time, The above fourth system time indicates the time at which the measurement response message is received in the first DU. Electronic devices.
15. In claim 14, The above link delay is determined by dividing the difference between the first difference value and the second difference value by 2, The above first difference value represents the time interval from the first system time to the fourth system time, The second difference value represents the time interval from the second system time to the third system time. Electronic devices.
Citation Information
Patent Citations
Time synchronization method and device
EP4132133A1
GPS location based user-customized augmented reality zoo viewing system and method
KR102603801B1
Measuring transmission delay
US11329926B2
Delay measurements between GNB-CU and GNB-du
WO2023018897A1
Cited By
Synchronization management in lower-layer split radio access networks
US20260040245A1
