Method and system for checking connection between distributed unit and radio unit using detection of synchronization signal block

Abstract

A method for a system including a DU and an RU according to one embodiment to verify the normality of a connection between a DU and an RU using SSB detection may include: an operation in which the DU transmits a downlink signal to the RU; an operation in which the RU receives the downlink signal, detects an SSB, and extracts a Cell ID from the SSB; an operation in which the RU determines the normality of the downlink connection by checking whether the Cell ID is within a preset range; and an operation in which the RU transmits information regarding the normality of the downlink connection to an EMS server.

Description

Technology Field

[0001] The present invention relates to a method and system for verifying the normality of a connection between a DU and an RU by detecting an element that can verify whether the connection between a DU and an RU is normal in a downlink signal or an uplink signal. Background Technology

[0002] As the wireless communication environment has evolved, the number of wireless stations required to cover the entire country has increased exponentially. While the number of base stations required for nationwide coverage to provide 3G services in the past was approximately 8,000 to 10,000, in the current LTE and 5G wireless environments, each wireless operator must install and operate at least 200,000 wireless stations through cell division subdivided into DU (Distributed Unit) and RU (Radio Unit) structures. Furthermore, if optical repeaters, including outdoor or indoor repeaters, are included, the number of wireless stations to be operated reaches approximately 300,000.

[0003] Consequently, there is a severe shortage of personnel to conduct inspections of radio stations. In response, a sample inspection system for radio stations was introduced to facilitate rapid inspections, but despite this, the number of radio stations failing inspections continues to increase rapidly every year.

[0004] This phenomenon is placing an increasing burden on mobile telecommunications operators due to the growing workload and costs associated with wireless station equipment. Consequently, there is an urgent need for low-cost, high-efficiency solutions that can reduce the time, cost, and required personnel for wireless station inspections. Prior art literature

[0005] Republic of Korea Registered Patent Publication No. 10-1747231 The problem to be solved

[0006] Figure 1 is an example diagram showing inspection personnel checking whether the connection between the DU and the RU is normal at the physical location of the RU in a wireless communication system including a DU and an RU.

[0007] Referring to Figure 1, in the past, to verify whether the DU and RU of a wireless communication system were properly connected, inspection personnel directly checked the connection between the DU and RU through an inspection terminal at the physical location of the RU. However, this method has the problem that, in order to perform wireless station inspections, inspection personnel must directly reach the physical location of the RU, and thus, a huge amount of cost and time is required to inspect numerous RUs one by one.

[0008] Accordingly, the problem that the present invention aims to solve is to provide a technology that allows the DU or RU to directly detect an element capable of verifying whether the connection between the DU and RU is normal in a downlink signal or an uplink signal, thereby verifying the normality of the connection between the DU and RU without requiring inspection personnel to reach the physical location of the DU or RU.

[0009] Meanwhile, the technical problems of the present invention are not limited to those mentioned above, and other unmentioned technical problems will be clearly understood by a person skilled in the art from the description below. means of solving the problem

[0010] A method for verifying the normality of a connection between a DU and a RU using SSB detection in a system including a DU and a RU according to one embodiment may include: an operation in which the DU transmits a downlink signal to the RU; an operation in which the RU receives the downlink signal, detects an SSB, and extracts a Cell ID from the SSB; an operation in which the RU determines the normality of the downlink connection by checking whether the Cell ID is within a preset range; and an operation in which the RU transmits information regarding the normality of the downlink connection to an EMS server.

[0011] In addition, the above SSB may include PSS, SSS, and PBCH.

[0012] Additionally, the operation of extracting the Cell ID may include extracting NID2 from the PSS, extracting NID1 from the SSS, and extracting the SSB Index from the PBCH, and identifying the Cell ID based on the NID2, NID1, and SSB Index.

[0013] In addition, the SSB of the extraction operation is extracted from the User Plane, and the determination operation may further include an operation in which the RU additionally extracts the Cell ID of the SSB received in the M plane and compares whether it matches the Cell ID extracted from the User Plane.

[0014] Additionally, the above method may include the operation of the RU transmitting an uplink signal to the DU; the operation of the DU receiving the uplink signal, detecting a PRACH signal, and extracting pattern information from the PRACH signal; the operation of the DU checking whether the pattern information matches pre-established information to verify the normality of the uplink connection; and the operation of the DU transmitting information regarding the normality of the uplink connection to an EMS server.

[0015] In a system for verifying the normality of a connection between a DU and an RU using SSB detection according to one embodiment, the system includes an RU and a DU, and the operation of the RU is

[0016] The method may include: receiving a downlink signal transmitted by the DU; detecting an SSB from the downlink signal and extracting a Cell ID from the SSB; determining the normality of the downlink connection by checking whether the Cell ID is within a preset range; and transmitting information regarding the normality of the downlink connection to an EMS server.

[0017] In addition, the above SSB may include PSS, SSS, and PBCH.

[0018] Additionally, the operation of extracting the Cell ID may include extracting NID2 from the PSS, extracting NID1 from the SSS, and extracting the SSB Index from the PBCH, and searching for the Cell ID based on the NID2, NID1, and SSB Index.

[0019] In addition, the SSB of the extraction operation is extracted from the U Plane, and the determination operation may further include an operation to additionally extract the Cell ID of the SSB received by the RU in the M Plane and compare it with the Cell ID extracted from the U Plane.

[0020] Additionally, the operation of the DU may include: receiving an uplink signal transmitted by the RU; detecting a PRACH signal from the uplink signal and extracting pattern information from the PRACH signal; verifying the normality of the uplink connection by checking whether the pattern information matches pre-set information; and transmitting information regarding the normality of the uplink connection to an EMS server. Effects of the invention

[0021] The present invention can determine the normality of a downlink connection through the Cell ID of a Synchronization Signal Block (SSB) that occurs periodically in a downlink signal and transmit information regarding the normality of the connection to an EMS server. In addition, the present invention can determine the normality of an uplink connection through pattern information of a Physical Random Access Channel (PRACH) signal that occurs periodically in an uplink signal and transmit information regarding the normality of the connection to an EMS server.

[0022] Through this, the present invention enables inspection personnel to verify the normality of the connection between the DU and the RU without needing to reach the physical location of the DU or RU.

[0023] Meanwhile, the effects of the present invention are not limited to those mentioned above, and other unmentioned technical effects will be clearly understood by a person skilled in the art from the description below. Brief explanation of the drawing

[0024] Figure 1 is an example diagram showing inspection personnel checking whether the connection between the DU and the RU is normal at the physical location of the RU in a wireless communication system including a DU and an RU. FIG. 2 is a configuration diagram of a system for verifying the normality of a connection between a DU and a RU using SSB detection according to one embodiment. FIG. 3 is a configuration diagram of a DU or RU according to one embodiment. FIG. 4 is a flowchart of an operation in which a system according to one embodiment checks connection normality through the SSB of a downlink signal. FIG. 5 is an example of an SSB periodically included in a downlink signal according to one embodiment. FIG. 6 is an example diagram of an operation to extract a Cell ID from an SSB according to one embodiment. FIG. 7 is a flowchart of an operation in which a system according to one embodiment checks connection normality through PRACH of an uplink signal. Specific details for implementing the invention

[0025] Detailed information regarding the purpose, technical configuration, and resulting effects of the present invention will be more clearly understood through the following detailed description based on the drawings attached to the specification of the present invention. An embodiment according to the present invention will be described in detail with reference to the attached drawings.

[0026] The embodiments disclosed herein should not be interpreted or used to limit the scope of the invention. It is obvious to those skilled in the art that the description including the embodiments herein has various applications. Accordingly, any embodiments described in the detailed description of the invention are illustrative for better explaining the invention and are not intended to limit the scope of the invention to the embodiments.

[0027] The functional blocks shown in the drawings and described below are merely examples of possible implementations. In other implementations, other functional blocks may be used without departing from the spirit and scope of the detailed description. Additionally, while one or more functional blocks of the present invention are shown as individual blocks, one or more of the functional blocks of the present invention may be a combination of various hardware and software configurations that perform the same function.

[0028] Furthermore, the expression that it includes certain components is an “open-ended” expression that merely refers to the existence of such components and should not be understood as excluding additional components.

[0029] Furthermore, when it is stated that one component is “connected” or “joined” to another component, it should be understood that while it may be directly connected or joined to that other component, there may also be other components present in between.

[0030] Hereinafter, various embodiments of the present invention are described with reference to the accompanying drawings. However, this is not intended to limit the present invention to specific embodiments and should be understood to include various modifications, equivalents, and / or alternatives of the embodiments of the present invention.

[0031] FIG. 2 is a configuration diagram of a system (10) (hereinafter referred to as 'system (10)') that checks the normality of a connection between a DU and a RU using SSB detection according to one embodiment.

[0032] Referring to FIG. 2, a system (10) according to one embodiment is a system that includes a configuration for operating a wireless communication network. For example, the system (10) may include wireless communication systems such as a 5G mobile communication network, LTE (long term evolution), GSM (global system for mobile communication), CDMA (code division multiple access), and WCDMA (wideband code division multiple access).

[0033] A system (10) of one embodiment may include a DU (100), an RU (200), an FHM (300), and an EMS server (400).

[0034] DU (100) is a Distributed Unit that receives uplink signals from the system (10) and transmits downlink signals.

[0035] RU (200) is a Radio Unit that receives downlink signals from the system (10) and transmits uplink signals.

[0036] FHM (300) is a Fronthaul Multiplexer that relays signals transmitted and received between DU (100) and RU (200). The application protocol of FHM (300) may include a control plane (C-plane), a user plane (U-plane), a synchronization plane (S-plane), and a management plane (M-plane). The USER Plane may include user downlink data (IQ data, SSB (synchronization signal block), RS), uplink data (IQ data, SRS / RS), and PRACH (physical random access channel) data. The M Plane may include an SSB separately from the USER Plane.

[0037] The EMS (Enterprise Management System) server (400) is a device that manages the network status of the system (10), the operation status of each device, etc.

[0038] The DU (100), RU (200), FHM (300), and EMS server (400) can be connected to operate via a communication network to transmit and receive information. For example, the communication network may include wired or wireless communication networks such as a LAN (local area network), WAN (wide area network), virtual network, and remote communication.

[0039] FIG. 3 is a configuration diagram of a DU (100) or RU (200) according to one embodiment.

[0040] Referring to FIG. 3, a DU (100) or RU (200) according to one embodiment may each include a memory (110, 210), a processor (120, 220), an input / output interface (130, 230), and a communication interface (140, 240).

[0041] The memory (110, 210) can store data obtained from an external device or data generated by itself. The memory (110, 210) can store instructions that can perform operations of the processor (120, 220).

[0042] The processor (120, 220) is an arithmetic unit that controls overall operation. The processor (120, 220) can execute instructions stored in memory (110, 210). The operation of the DU (100) or RU (200) according to the embodiment of the present document can be understood as an operation performed by the processor (120, 220).

[0043] The input / output interface (130, 230) may include a hardware interface or a software interface for inputting or outputting information.

[0044] The communication interface (140, 240) enables the transmission and reception of information through a communication network. To this end, the communication interface (140, 240) may include a wireless communication module or a wired communication module.

[0045] The DU (100) or RU (200) can be implemented as various types of devices capable of performing operations through a processor (120, 220) and transmitting and receiving information through a network. For example, it can be implemented in the form of a server, computer device, portable communication device, smartphone, portable multimedia device, laptop, tablet PC, etc., but is not limited to these examples.

[0046] FIG. 4 is a flowchart of an operation in which a system (10) according to one embodiment checks the normality of the connection through the SSB of a downlink signal.

[0047] The operation of the system (10) according to the embodiment of FIG. 4 can be understood as an operation performed by the DU (100) or RU (200). Each step disclosed in FIG. 4 is merely a preferred embodiment for achieving the purpose of the present invention, and some steps may be added or deleted as needed, and any one step may be included in another step. The order of each operation disclosed in FIG. 4 is arranged only for convenience of understanding, and such order is not limited to a chronological order, and the order may be changed differently depending on the designer's choice.

[0048] Referring to FIG. 4, in step S1010, the DU (100) can transmit a downlink signal to the RU (200). The downlink signal may periodically include a Synchronization Signal Block (SSB).

[0049] FIG. 5 is an example of an SSB periodically included in a downlink signal according to one embodiment.

[0050] Referring to FIG. 5, the SSB is a block periodically included in the downlink signal and may include a synchronization signal (PSS (Primary Synchronization Signal), SSS (Secondary Synchronization Signal)) for time synchronization and frequency synchronization between devices included in the system (10) and a PBCH (Physical Broadcast Channel) for quality measurement.

[0051] In step S1020, the RU (200) receives a downlink signal to detect the SSB and can extract the Cell ID from the SSB.

[0052] FIG. 6 is an example diagram of an operation to extract a Cell ID from an SSB according to one embodiment.

[0053] Referring to FIG. 6, the RU (200) can detect an SSB in the User Plane and obtain a PSS (Primary Synchronization Signal), a SSS (Secondary Synchronization Signal), and a PBCH (Physical Broadcast Channel) from the SSB. Accordingly, the RU (200) can extract NID2 from the PSS, extract NID1 from the SSS, and extract an SSB Index from the PBCH, and determine a Cell ID based on NID2, NID1, and the SSB Index.

[0054] In step S1030, the RU (200) can determine the normality of the downlink connection by checking whether the specified Cell ID is within a preset range (e.g., 0 to 1024). For example, based on NID2, NID1, and SSB Index, the RU (200) can determine that the Cell ID is normally connected to the DU (100) if it is within the range of 0 to 1024, and can determine that the Cell ID is not properly connected to the DU (100) if it is within the range of 1024.

[0055] Additionally, in step S1030, the RU (200) can additionally extract an SSB from the M plane to detect the Cell ID of the SSB extracted from the M plane. The RU (200) can additionally perform an operation to compare whether the Cell ID extracted from the User Plane matches the Cell ID of the SSB extracted from the M plane, thereby secondarily verifying the normality of the downlink connection. If the Cell ID extracted from the User Plane matches the Cell ID of the SSB extracted from the M plane, the RU (200) can determine that it is connected to the DU (100) normally, and if the Cell ID extracted from the User Plane matches the Cell ID of the SSB extracted from the M plane, it can determine that the connection to the DU (100) is not properly performed.

[0056] FIG. 7 is a flowchart of an operation in which a system (10) according to one embodiment checks connection normality through PRACH of an uplink signal.

[0057] The operation of the system (10) according to the embodiment of FIG. 7 can be understood as an operation performed by the DU (100) or RU (200). Each step disclosed in FIG. 7 is merely a preferred embodiment for achieving the purpose of the present invention, and some steps may be added or deleted as needed, and any one step may be included in another step. The order of each operation disclosed in FIG. 4 is arranged only for convenience of understanding, and such order is not limited to a chronological order, and the order may be changed and operated differently according to the designer's choice.

[0058] Referring to FIG. 7, in step S2010, the RU (200) can transmit an uplink signal to the DU (100). The uplink signal may include a PRACH (Physical Random Access Channel) signal.

[0059] In step S2020, the DU (100) receives an uplink signal to detect a PRACH signal and can extract pattern information from the PRACH signal. For example, the pattern information of the PRACH signal may include A1, A2, A3, B1, B2, B3, B4, C0, C2, etc. as a pre-established form.

[0060] In step S2030, the DU (100) can verify the normality of the uplink connection by checking whether the extracted pattern information matches a pre-established pattern (e.g., one of A1, A2, A3, B1, B2, B3, B4, C0, C2). For example, if the pre-established pattern information in the uplink signal between the DU (100) and the RU (200) is A0, the DU (100) can determine that the connection with the RU (200) is not properly performed if the pattern information extracted from the PRACH signal is not A0.

[0061] According to the above-described embodiment, the present invention can determine the normality of a downlink connection through the Cell ID of a Synchronization Signal Block (SSB) that occurs periodically in a downlink signal and transmit information regarding the normality of the connection to an EMS server. In addition, the present invention can determine the normality of an uplink connection through pattern information of a Physical Random Access Channel (PRACH) signal that occurs periodically in an uplink signal and transmit information regarding the normality of the connection to an EMS server.

[0062] Through this, the present invention enables inspection personnel to verify the normality of the connection between the DU and the RU without needing to reach the physical location of the DU or RU.

[0063] The various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of said embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more items unless the relevant context clearly indicates otherwise.

[0064] In this document, each of the phrases such as “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B or C,” “at least one of A, B and C,” and “at least one of A, B, or C” may include all possible combinations of items listed together in the corresponding phrase. Terms such as “1,” “2,” or “first” or “second” may be used simply to distinguish a component from another component and do not limit the components in any other aspect (e.g., importance or order). Where any (e.g., 1st) component is referred to as “coupled” or “connected” to another (e.g., 2nd) component, with or without the terms “functionally” or “communicationly,” it means that the component may be connected to the other component directly (e.g., wired), wirelessly, or through a third component.

[0065] As used in this document, the term "module" may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit. A module may be a component formed integrally, or a minimum unit of a component or part thereof that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0066] Various embodiments of this document may be implemented as software (e.g., a program) comprising one or more instructions stored in a storage medium (e.g., memory) that can be read by a device (e.g., an electronic device). The storage medium may include random access memory (RAM), a memory buffer, a hard drive, a database, erasable programmable read-only memory (EPROM), electrically erasable read-only memory (EEPROM), read-only memory (ROM), and / or the like.

[0067] Additionally, the processor of the embodiments of this document may call at least one instruction among one or more instructions stored from a storage medium and execute it. This enables the device to operate to perform at least one function according to at least one called instruction. Such one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. The processor may be a general-purpose processor, a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), and / or the like.

[0068] A device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' simply means that the storage medium is a tangible device and does not contain signals (e.g., electromagnetic waves), and this term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily.

[0069] Methods according to the various embodiments disclosed in this document may be provided as part of a computer program product. The computer program product may be traded between a seller and a buyer 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 distributed online (e.g., download or upload) through an application store (e.g., Play Store) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created on a device-readable storage medium, such as a manufacturer's server, an application store's server, or the server's memory.

[0070] According to various embodiments, each component (e.g., module or program) of the described components may include a singular or multiple entities. According to various 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. Generally or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the components of the multiple components in the same or similar manner as they were performed by the corresponding component among the multiple components prior to integration. According to various embodiments, operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically; one or more of the operations may be executed in a different order; omitted; or one or more other operations may be added. Explanation of the symbols

[0071] 10: System 100: DU 200: RU 300: FHM 400: EMS Server 110, 210: Memory 120, 220: Processors 130, 230: Input / Output Interface 140, 240: Communication interface

Claims

Claim 1 A method for a system including a DU and an RU to verify the normality of a connection between a DU and an RU using SSB detection, comprising: an operation in which the DU transmits a downlink signal to the RU; an operation in which the RU receives the downlink signal, detects an SSB, and extracts a Cell ID from the SSB; an operation in which the RU determines the normality of the downlink connection by checking whether the Cell ID is within a preset range; and an operation in which the RU transmits information regarding the normality of the downlink connection to an EMS server. Claim 2 In claim 1, the method wherein the SSB comprises PSS, SSS, and PBCH. Claim 3 A method according to claim 2, wherein the operation of extracting the Cell ID includes extracting NID2 from the PSS, extracting NID1 from the SSS, and extracting the SSB Index from the PBCH, and determining the Cell ID based on the NID2, NID1, and SSB Index. Claim 4 A method according to claim 1, wherein the SSB of the extraction operation is extracted from the User Plane, and the determining operation further includes the operation of additionally extracting the Cell ID of the SSB received by the RU in the M Plane and comparing whether it matches the Cell ID extracted from the User Plane. Claim 5 The method of claim 1 comprises: the operation of the RU transmitting an uplink signal to the DU; the operation of the DU receiving the uplink signal, detecting a PRACH signal, and extracting pattern information from the PRACH signal; the operation of the DU verifying whether the pattern information matches pre-agreed information to verify the normality of the uplink connection; and the operation of the DU transmitting information regarding the normality of the uplink connection to an EMS server. Claim 6 A system for verifying the normality of a connection between a DU and an RU using SSB detection, wherein the system comprises an RU and a DU, and the operation of the RU comprises: receiving a downlink signal transmitted by the DU; detecting an SSB from the downlink signal and extracting a Cell ID from the SSB; determining the normality of the downlink connection by checking whether the Cell ID is within a preset range; and transmitting information regarding the normality of the downlink connection to an EMS server. Claim 7 In paragraph 6, the above SSB is a system including PSS, SSS, and PBCH. Claim 8 In claim 7, the operation of extracting the Cell ID includes extracting NID2 from the PSS, extracting NID1 from the SSS, and extracting the SSB Index from the PBCH, and the operation of searching for the Cell ID based on the NID2, NID1, and SSB Index. Claim 9 A system according to claim 6, wherein the SSB of the extraction operation is extracted from the U Plane, and the determining operation further includes the operation of additionally extracting the Cell ID of the SSB received by the RU in the M Plane and comparing it to the Cell ID extracted from the U Plane. Claim 10 In claim 6, the operation of the DU comprises: receiving an uplink signal transmitted by the RU; detecting a PRACH signal from the uplink signal and extracting pattern information from the PRACH signal; verifying the normality of the uplink connection by checking whether the pattern information matches pre-set information; and transmitting information regarding the normality of the uplink connection to an EMS server.

Images