WO2015180523A1 - 基于fpga射频拉远单元rru接口协议自适应的方法及装置 - Google Patents

基于fpga射频拉远单元rru接口协议自适应的方法及装置 Download PDF

Info

Publication number
WO2015180523A1
WO2015180523A1 PCT/CN2015/074214 CN2015074214W WO2015180523A1 WO 2015180523 A1 WO2015180523 A1 WO 2015180523A1 CN 2015074214 W CN2015074214 W CN 2015074214W WO 2015180523 A1 WO2015180523 A1 WO 2015180523A1
Authority
WO
WIPO (PCT)
Prior art keywords
rru
type
interface protocol
identifier
bbu
Prior art date
Application number
PCT/CN2015/074214
Other languages
English (en)
French (fr)
Inventor
郭峰
李谦
耿贵杰
杨笛
Original Assignee
大唐移动通信设备有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 大唐移动通信设备有限公司 filed Critical 大唐移动通信设备有限公司
Priority to EP15799047.4A priority Critical patent/EP3151607B1/en
Priority to US15/311,364 priority patent/US10298453B2/en
Publication of WO2015180523A1 publication Critical patent/WO2015180523A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • the present invention relates to the field of mobile communication technologies, and in particular, to a method for adapting a RRU interface protocol based on a field programmable gate array FPGA radio remote unit, and a RRU interface protocol based on a field programmable gate array FPGA radio remote unit Adaptive device.
  • RRU Radio Remote Unit
  • BBU Building Base Band Unit
  • the RRU accesses the BBU through the optical fiber according to a specific RRU interface protocol.
  • the RRU needs to support the smooth evolution from TD-SCDMA (Time Division-Synchronization Code Division Multiple Access) standard to TD-LTE.
  • TD-SCDMA Time Division-Synchronization Code Division Multiple Access
  • the standard requirements require that the types of RRU interface protocols supported by the RRU increase accordingly.
  • the RRU side needs to be able to access the RRU interface protocol corresponding to the BBU.
  • the RRU of the current TD-LTE is connected to the BBU of the TD-SCDMA through the optical fiber. Due to the difference in communication standards between the two, the interface protocol incompatibility between the RRU and the BBU is incompatible.
  • a method and a device for adapting an RRU interface protocol based on an FPGA radio remote unit are proposed, which are used for detecting and adjusting an interface protocol to ensure an interface protocol with a peer device.
  • Uniformity reduces the complexity of normal communication implementation, shortens the TD-SCDMA base station evolution to TD-LTE base station transformation time, and ensures normal communication of devices in the common network.
  • the technical problem to be solved by the present application is to provide a method for adapting the RRU interface protocol based on the FPGA radio remote unit, which is used for detecting and adjusting the interface protocol, ensuring and setting the interface.
  • the uniformity of the standby interface protocol reduces the complexity of normal communication implementation and ensures normal communication of devices in the common network.
  • the present application also provides an apparatus based on FPGA radio remote unit RRU interface protocol adaptation.
  • the present application discloses a method based on field programmable gate array FPGA radio remote unit RRU interface protocol adaptation, the FPGA includes a type register, and the method includes:
  • the RRU loads the FPGA; the FPGA includes one or more interface protocol types;
  • the RRU accesses the baseband processing unit BBU by using any of the interface protocol types;
  • the RRU detects a current interface protocol type of the BBU
  • the RRU records a corresponding type identifier in the type register for the current interface protocol type
  • the RRU is configured for an interface protocol type corresponding to the type identifier.
  • the step of detecting, by the RRU, the current interface protocol type of the BBU includes:
  • the RRU determines the interface protocol type according to the physical layer control word.
  • the step of determining, by the RRU, the interface protocol type according to the physical layer control word comprises:
  • the RRU determines that the interface protocol type is the first type.
  • the step of detecting, by the RRU, the current interface protocol type of the BBU includes:
  • the RRU determines that the interface protocol type is the second type.
  • the step of detecting, by the RRU, the current interface protocol type of the BBU includes:
  • the RRU determines that the interface protocol type is the third type.
  • the step of the RRU recording the corresponding type identifier in the type register for the current interface protocol type comprises:
  • the RRU records a first type identifier in the type register for the first type
  • the RRU records a second type identifier in the type register for the second type
  • the RRU records a third type of identification in the type register for the third type.
  • the first type is a general public radio interface CPRI protocol
  • the second type is an LTE-IR interface protocol
  • the third type is a TD-IR interface protocol.
  • the embodiment of the present application further discloses an apparatus for adapting based on a field programmable gate array FPGA radio remote unit RRU interface protocol, the FPGA includes a type register, and the apparatus includes:
  • a load module located at the RRU, configured to load an FPGA;
  • the FPGA includes one or more interface protocol types;
  • An access module located in the RRU configured to access the baseband processing unit BBU by using any of the interface protocol types;
  • a detection module located at the RRU, configured to detect a current interface protocol type of the BBU;
  • a recording module located at the RRU, configured to record a corresponding type identifier in the type register for the current interface protocol type
  • the configuration module of the RRU is configured to be configured for the interface protocol type corresponding to the type identifier.
  • the detecting module located in the RRU comprises:
  • a receiving module located at the RRU, configured to receive a physical layer control word sent by the BBU;
  • the judging module located at the RRU is configured to determine the interface protocol type according to the physical layer control word.
  • the determining module located in the RRU includes:
  • a first acquiring module located in the RRU, configured to acquire data of a first preset supergroup position in the physical layer control word
  • a first determining module located at the RRU configured to determine whether the first data is a preset value; if yes, calling a first determining module located in the RRU;
  • the first determining module located at the RRU is configured to determine that the interface protocol type is the first type.
  • the determining module located in the RRU includes:
  • a second acquiring module located in the RRU, configured to acquire an RRU identifier of a second preset supergroup position in the physical layer control word
  • a second determining module located in the RRU, configured to determine whether the RRU identifier is a preset RRU; if yes, invoking a second determining module located in the RRU;
  • a second determining module located at the RRU is configured to determine that the interface protocol type is the second type.
  • the determining module located in the RRU includes:
  • a third acquiring module located in the RRU, configured to acquire an RRU identifier of a third preset supergroup position in the physical layer control word;
  • a third determining module located in the RRU configured to determine that the RRU identifier is a preset RRU identifier; if yes, invoking a third determining module located in the RRU;
  • a third determining module located at the RRU is configured to determine that the interface protocol type is a third type.
  • the recording module located in the RRU includes:
  • a first recording module located at the RRU, configured to record a first type of identification in the type register for the first type
  • a second recording module located at the RRU, configured to send in the type for the second type Recording a second type identifier in the register;
  • a third recording module located at the RRU is configured to record a third type of identification in the type register for the third type.
  • the embodiment of the present application also discloses a computer readable recording medium on which a program for executing the above method is recorded.
  • the present application includes the following advantages:
  • the RRU uses the protocol type in the FPGA to access the BBU
  • the current interface protocol type of the BBU is detected, and the corresponding type identifier is recorded in the register according to the current interface protocol type, and the RRU corresponds to the interface protocol corresponding to the type identifier.
  • the configuration is performed to meet the requirements of the peer BBU, ensure the unification of the interface protocol with the peer device, reduce the complexity of normal communication, and ensure normal communication between devices in the common network.
  • the RBU after the RRU accesses the BBU, the RBU performs the detection according to the information sent by the BBU, and adjusts according to the detection result, so that the RRU can adapt to the current RRU interface protocol, and the interruption time of the user service is short, which does not affect normal use.
  • the user experience is good. It is not necessary to manually modify the type information of the interface protocol between the RRU and the BBU, which shortens the transformation time of the TD-SCDMA base station to the TD-LTE base station, and reduces labor cost and resource consumption.
  • the embodiment of the present application since the existing resources can be directly used, resource waste can be avoided, and the current interface protocol mode is determined according to the information sent by the BBU, thereby reducing the complexity of the normal communication implementation and reducing the complexity of the FPGA design.
  • it is not for a certain standard, and can support multiple communication specifications, support multiple interface protocols, is simple and easy to implement, and reduces the degree of restriction on its external devices. It should be noted that the embodiment of the present application can also support the detection and adjustment of the interface protocol when the BBU accesses the peer or the upper BBU.
  • FIG. 1 is a schematic diagram of a method for adjusting an RRU interface protocol in a TD-LTE base station
  • FIG. 2 is a flowchart of a configuration of replacing an RRU software package to perform an RRU interface protocol
  • FIG. 3 is a flow chart of steps of an embodiment of a method for adapting an RRU interface protocol based on an FPGA radio remote unit according to the present application;
  • FIG. 4 is a schematic diagram of an RRU interface protocol adaptation process of the present application.
  • FIG. 5 is a structural diagram of an internal module of a prior art FPGA fixed protocol type
  • FIG. 6 is a structural diagram of an internal module of an FPGA detection protocol type of the present application.
  • FIG. 7 is a schematic diagram of an internal interface protocol detection process of an FPGA in the present application.
  • FIG. 8 is a structural block diagram of an apparatus embodiment of an FPGA-based radio remote unit RRU interface protocol adaptation according to the present application.
  • the configuration of the interface protocol between the RRU and the BBU is mainly implemented in two ways:
  • FIG. 1 a schematic diagram of a method for adjusting an RRU interface protocol in a TD-LTE base station, an interface protocol of an FPGA (Field Programmable Gata Array) version generation in an RRU is determined, and is identified in In the corresponding register, the RRU software configures the software side message type by acquiring the type register in the FPGA, so that the RRU is accessed by a fixed interface protocol type.
  • the RRU-side FPGA needs to be modified to ensure that the BBU-side interface protocol is unified.
  • the RRU uses the original transmission protocol to access the BBU normally;
  • the RRU controls the LMT-B (the local maintenance management system of the base station) to download the software package of the upgraded version of the RRU through the original transmission protocol;
  • the RRU re-accesses the BBU, and triggers software version update on the BBU side;
  • the interface between the BBU and the RRU is fixed, that is, the interface protocol type of the RRU is fixed, the interface protocol used by the BBU must be clarified, and the specific protocol type on the RRU side is determined.
  • the dual-mode RRU can only support the TD-
  • the BBU docking of the LTE interface protocol cannot support the connection with the existing TD-SCDMA single-mode BBU, and the original TD-SCDMA single-mode RRU can only be connected with the TD-SCDMA single-mode BBU, and cannot be newly developed with the dual-mode.
  • the BBU is docked.
  • the second method is to replace the RRU software package to configure the RRU interface protocol.
  • the first method needs to consume a lot of labor costs, the BBU and the RRU need to be upgraded.
  • the base station's model reset operation This will cause the cell to fail to perform services for a long time, which will cause long-term interruption of user services and affect user usage.
  • one of the core concepts of the embodiment of the present application is that after the RRU uses the protocol type in the FPGA to access the BBU, the current interface protocol type of the BBU is detected, and the register is based on the current interface protocol type.
  • the corresponding type identifier is recorded in the middle, and the RRU configures the interface protocol type corresponding to the type identifier to meet the requirements of the peer BBU, shortens the transformation time of the TD-SCDMA base station to the TD-LTE base station, and ensures the interface protocol with the peer device. Uniformity reduces the complexity of normal communication implementation and ensures normal communication of devices in the common network.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the FPGA may include a type register, and the method may include the following steps:
  • Step 101 The RRU loads the FPGA; the FPGA includes one or more interface protocol types;
  • the FPGA stores information of multiple interface protocol types, which may include an interface protocol of TD-SCDMA and TD-LTE.
  • RRU soft when RRU starts The FPGA completes the loading of the FPGA, and the FPGA works under the default interface protocol type.
  • Step 102 the RRU uses any of the interface protocol types to access the baseband processing unit BBU;
  • an old interface protocol that can communicate with each other is installed in the RRU and the BBU, and is set as the default interface protocol in the PPGA.
  • the default interface protocol is used to access the BBU, and the normal communication between the RRU and the BBU is implemented to obtain the information about the interface protocol of the corresponding BBU. Ground adjustment.
  • Step 103 The RRU detects a current interface protocol type of the BBU.
  • the step 103 may include the following sub-steps:
  • Sub-step S11 the RRU receives a physical layer control word sent by the BBU;
  • Sub-step S12 the RRU determines the interface protocol type according to the physical layer control word.
  • the RRU receives the physical layer control word sent by the BBU, and the RRU FPGA automatically detects the physical layer control word, and determines the opposite BBU according to the detection result.
  • Interface protocol type
  • the sub-step S12 may include the following sub-steps:
  • Sub-step S12-11 the RRU acquires data of a first preset supergroup position in the physical layer control word
  • Sub-step S12-12 the RRU determines whether the first data is a preset value; if yes, performing sub-step S12-13;
  • Sub-step S12-13 the RRU determines that the interface protocol type is the first type.
  • the sub-step S12 may include the following sub-steps:
  • Sub-step S12-21 the RRU acquires an RRU identifier of a second preset supergroup position in the physical layer control word
  • Sub-step S12-22 the RRU determines whether the RRU identifier is a preset RRU; If yes, perform sub-step S12-23;
  • Sub-step S12-23 the RRU determines that the interface protocol type is the second type.
  • the sub-step S12 may include the following sub-steps:
  • Sub-step S12-31 the RRU acquires an RRU identifier of a third preset supergroup position in the physical layer control word
  • Sub-step S12-32 the RRU determines that the RRU identifier is a preset RRU identifier; if yes, performing sub-steps S12-33;
  • Sub-step S12-33 the RRU determines that the interface protocol type is the third type.
  • Step 104 The RRU records a corresponding type identifier in the type register for the current interface protocol type.
  • the step 104 may include the following sub-steps:
  • Sub-step S21 the RRU records a first type identifier in the type register for the first type
  • Sub-step S22 the RRU records a second type identifier in the type register for the second type
  • Sub-step S23 the RRU records a third type identifier in the type register for the third type.
  • Step 105 The RRU is configured for an interface protocol type corresponding to the type identifier.
  • the FPGA after normal communication between the RRU and the BBU, the FPGA automatically detects the BBU interface protocol type actually accessed, and identifies it in the register according to the interface protocol type.
  • the RRU software determines the interface protocol type of the currently connected BBU by reading the identifier in the register of the FPGA. Finally, the software completes all relevant configurations on the RRU side according to the interface protocol type.
  • a schematic diagram of an RRU interface protocol adaptation process of the present application includes an interface protocol type that allows normal communication between the RRU and the BBU in the FPGA. The specific steps are as follows:
  • Step 1 When the RRU starts, the software completes the loading of the FPGA, and the FPGA works under the default interface protocol type.
  • the FPGA default interface protocol adaptive register that is, the value of the type register is 0x0 (invalid protocol).
  • Step 2 The RRU FPGA receives the information sent by the BBU under the default interface protocol type, and automatically detects the actual access protocol type according to the information, and identifies it in the adaptive register.
  • the FPGA feeds back the current value of the protocol adaptive register to the RRU software.
  • the RSU software After receiving the RRU software, the RSU software reads the value of the adaptive register to determine whether the interface protocol type of the currently connected BBU is a valid interface protocol type. If yes, execute step 4, if not, Then go to step 3.
  • Step 3 The RRU software completes the configuration of the RRU side FPGA protocol register according to the interface protocol type.
  • Step 4 Repeat step 2 and the RRU software continues to query whether the register value is a valid protocol type.
  • the data DATA, RRU software of the peer device received by the SERDES (SERializer/DESerializer)
  • the interface protocol type register can only be configured according to the RRU interface protocol that has been pre-cure.
  • an interface protocol test module is added to the RRU to detect and adjust the RRU interface protocol according to the data received by the SERDES.
  • the RRU interface protocol real-time detection module PLT_TEST is added to the RRU_FPGA to implement real-time detection of the RRU interface protocol in the case of transmission rate matching.
  • the RRU software is used to notify the RRU software of the current RRU interface protocol, and the RRU software performs the RRU interface protocol mode for configuration.
  • PLT_TEST is divided into the following three modules, namely TD-IR protocol real-time parsing module, LTE protocol real-time parsing module and CPRI protocol real-time parsing module. Need to explain In TD-SCDMA, each time slot is composed of a plurality of Super-Groups of 25S duration, and each Super-Group includes 32 group groups. Each group consists of 24 words. Within a Super-Group, the first byte of the first group is used as the synchronization word k28.5, and the second byte is transmitted as SGN (Super-GroupNumber).
  • SGN Super-GroupNumber
  • an FPGA internal interface protocol detection flow diagram of the present application is shown.
  • the default protocol adaptive register value is 0x0 (invalid protocol).
  • the data is sent to the TD-IR protocol real-time parsing module, the LTE real-time parsing module, and the CPRI protocol real-time parsing module.
  • the three modules respectively detect the data.
  • the detection steps for the three modules are as follows:
  • the downlink received data is parsed according to the frame structure of the TD-IR protocol: the content of the physical layer control word is parsed from the supergroup number RRUID of 33, and the data is verified according to the TD-IR protocol after the parsing is completed.
  • the first bit position of the type register of the FPGA and RRU software is 1. For example, set the type register bit0 to 1, which is 0x1.
  • LTE-IR protocol real-time parsing module
  • the downlink received data is parsed according to the frame structure of the LTE-IR protocol: since the content of the physical layer control word is parsed from the super-group number RRUID of 80, the data is verified according to the LTE-IR protocol after the parsing is completed, and the verification is correct.
  • the second bit of the type register of the FPGA and RRU software will be set to 1. For example, set the type register bitl to 1, which is 0x2.
  • the downlink received data is parsed according to the frame structure of the CPRI protocol: if the adjacent 24-bit data of the K28.5 sync word is detected as 0x50c550, the protocol of the current link transmission is CPRI, and the type register of the FPGA and the RRU software is The third bit is set to 1. For example, set type register bit2 to 1, which is 0x3.
  • the FPGA starts to detect the state of the optical module, and then configures the SERDES rate of the FPGA, and waits for the delay. At this time, the FPGA starts to detect the current RRU interface protocol type in real time, and the received link data is simultaneously sent.
  • TD-IR agreement Real-time parsing module, real-time parsing module of LTE-IR protocol, real-time parsing module of CPRI protocol, these three modules are set to perform parallel real-time parsing of link data according to TD-IR protocol, LTE-IR protocol and CPRI protocol.
  • the RRU can also be adjusted according to other interface protocols, which is not limited in this embodiment of the present application.
  • the RRU real-time parsing three interface protocols is implemented, and the low-latency characteristic of the FPGA internal detection optical port receiving data is utilized.
  • the RRU software completes the optical port protocol configuration process according to the interface protocol type reported by the FPGA, and can support the process.
  • TD-SCDMA digital cellular mobile communication network distributed base station Ir interface technical requirements "TD-LTE cellular mobile communication network distributed base station Ir interface technical requirements” and CPRI interface three specifications of the protocol adaptive function.
  • the RRU can automatically complete the requirement of accessing the baseband unit BBU according to the current RRU interface protocol.
  • the RRU adopting this technology can meet the requirements of the service interruption time that the operator proposes to upgrade as small as possible, reduce the complexity of normal communication implementation, and reduce labor cost and resource consumption.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • an FPGA-based radio remote unit RRU interface of the present application is shown.
  • a block diagram of a device embodiment of a protocol adaptation the FPGA may include a type register, and the device may specifically include the following modules:
  • a loading module 201 located at the RRU, configured to load an FPGA;
  • the FPGA includes one or more interface protocol types;
  • the access module 202 located in the RRU is configured to access the baseband processing unit BBU by using any of the interface protocol types;
  • the detecting module 203 of the RRU is configured to detect a current interface protocol type of the BBU.
  • the detecting module 203 located in the RRU may include:
  • a receiving module located at the RRU, configured to receive a physical layer control word sent by the BBU;
  • the judging module located at the RRU is configured to determine the interface protocol type according to the physical layer control word.
  • the determining module located in the RRU may include:
  • a first acquiring module located in the RRU, configured to acquire data of a first preset supergroup position in the physical layer control word
  • a first determining module located at the RRU configured to determine whether the first data is a preset value; if yes, calling a first determining module located in the RRU;
  • the first determining module located at the RRU is configured to determine that the interface protocol type is the first type.
  • the determining module located in the RRU may include:
  • a second acquiring module located in the RRU, configured to acquire an RRU identifier of a second preset supergroup position in the physical layer control word
  • a second determining module located in the RRU, configured to determine whether the RRU identifier is a preset RRU; if yes, invoking a second determining module located in the RRU;
  • a second determining module located at the RRU is configured to determine that the interface protocol type is the second type.
  • the determining module located in the RRU may include:
  • a third acquiring module located in the RRU, configured to acquire an RRU identifier of a third preset supergroup position in the physical layer control word;
  • a third determining module located in the RRU configured to determine that the RRU identifier is a preset RRU identifier; if yes, invoking a third determining module located in the RRU;
  • a third determining module located at the RRU is configured to determine that the interface protocol type is a third type.
  • a recording module 204 located at the RRU, configured to record a corresponding type identifier in the type register for the current interface protocol type;
  • the recording module 204 located in the RRU may include:
  • a first recording module located at the RRU, configured to record a first type of identification in the type register for the first type
  • a second recording module located at the RRU, configured to record a second type of identification in the type register for the second type
  • a third recording module located at the RRU is configured to record a third type of identification in the type register for the third type.
  • the configuration module 205 located at the RRU is configured to configure the interface protocol type corresponding to the type identifier.
  • the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • the embodiment of the present application also discloses a computer readable recording medium on which a program for executing the above method is recorded.
  • the computer readable recording medium includes any mechanism for storing or transmitting information in a form readable by a computer (eg, a computer).
  • a machine readable medium includes a read only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, flash storage media, electrical, optical, acoustic or other forms of propagating signals (eg, carrier waves, infrared signals, digital signals, etc.).
  • embodiments of the present application can be provided as a method, apparatus, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce a computation
  • Machine-implemented processing such as instructions executed on a computer or other programmable device, provides steps for implementing the functions specified in a block or blocks of a flow or a flow and/or block diagram of a flowchart.

Landscapes

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

Abstract

一种基于FPGA射频拉远单元RRU接口协议自适应的方法及装置，所述现场可编程门阵列FPGA包括类型寄存器，所述方法包括：RRU加载FPGA；所述FPGA包括一个或多个接口协议类型；所述RRU采用任一所述接口协议类型接入基带处理单元BBU；所述RRU检测所述BBU的当前接口协议类型；所述RRU针对所述当前接口协议类型在所述类型寄存器中记录对应的类型标识；所述RRU针对所述类型标识对应的接口协议类型进行配置。本申请用以检测及调整接口协议，保证与对端设备接口协议的统一，降低正常通信实现的复杂度，缩短TD-SCDMA基站演进到TD-LTE基站改造时间，保证共同组网中的设备正常通信。

Description

基于FPGA射频拉远单元RRU接口协议自适应的方法及装置 技术领域
本申请涉及移动通信技术领域，特别是涉及一种基于现场可编程门阵列FPGA射频拉远单元RRU接口协议自适应的方法，以及，一种基于现场可编程门阵列FPGA射频拉远单元RRU接口协议自适应的装置。
背景技术
在TD-LTE(Time Division Long Term Evolution，时分长期演进)有中一种应用广泛的分布式结构，是由RRU(Radio Remote Unit，射频拉远单元)及BBU(Building Base band Unit，室内基带处理单元)构成的当前较为流行的基站系统架构。
目前，RRU通过光纤按照特定的RRU接口协议接入BBU过程中，RRU需要支持从TD-SCDMA(Time Division-Synchronization Code Division Multiple Access，时分同步的码分多址技术)标准平滑演进到TD-LTE标准的需求，使RRU支持的RRU接口协议种类也相应的增加，RRU侧需要能够使用与BBU对应的RRU接口协议正才能常接入。例如现在的TD-LTE的RRU通过光纤连接到TD-SCDMA的BBU上，由于两者的通信标准存在差异，导致了RRU及BBU出现接口协议不兼容的问题。
因此，本领域技术人员迫切需要解决的问题之一在于，提出了一种基于FPGA射频拉远单元RRU接口协议自适应的方法及装置，用以检测及调整接口协议，保证与对端设备接口协议的统一，降低正常通信实现的复杂度，缩短TD-SCDMA基站演进到TD-LTE基站改造时间，保证共同组网中的设备正常通信。
发明内容
本申请所要解决的技术问题是提供一种基于FPGA射频拉远单元RRU接口协议自适应的方法，用以检测及调整接口协议，保证与对端设 备接口协议的统一，降低正常通信实现的复杂度，保证共同组网中的设备正常通信。
相应的，本申请还提供了一种基于FPGA射频拉远单元RRU接口协议自适应的装置。
为了解决上述问题，本申请公开了一种基于现场可编程门阵列FPGA射频拉远单元RRU接口协议自适应的方法，所述FPGA包括类型寄存器，所述方法包括：
RRU加载FPGA；所述FPGA包括一个或多个接口协议类型；
所述RRU采用任一所述接口协议类型接入基带处理单元BBU；
所述RRU检测所述BBU的当前接口协议类型；
所述RRU针对所述当前接口协议类型在所述类型寄存器中记录对应的类型标识；
所述RRU针对所述类型标识对应的接口协议类型进行配置。
优选地，所述RRU检测所述BBU的当前接口协议类型的步骤包括：
所述RRU接收所述BBU发送的物理层控制字；
所述RRU依据所述物理层控制字判断所述接口协议类型。
优选地，所述RRU依据所述物理层控制字判断所述接口协议类型的步骤包括：
所述RRU获取所述物理层控制字中第一预置超组位置的数据；
所述RRU判断所述第一个数据是否为预置的数值；
若是，则所述RRU确定所述接口协议类型为第一类型。
优选地，所述RRU检测所述BBU的当前接口协议类型的步骤包括：
所述RRU获取所述物理层控制字中第二预置超组位置的RRU标识；
所述RRU判断所述RRU标识是否为预置的RRU；
若是，则所述RRU确定所述接口协议类型为第二类型。
优选地，所述RRU检测所述BBU的当前接口协议类型的步骤包括：
所述RRU获取所述物理层控制字中第三预置超组位置的RRU标识；
所述RRU判断所述RRU标识为预置的RRU标识；
若是，则所述RRU确定所述接口协议类型为第三类型。
优选地，所述RRU针对所述当前接口协议类型在所述类型寄存器中记录对应的类型标识的步骤包括：
所述RRU针对所述第一类型在所述类型寄存器中记录第一类型标识；
和/或，
所述RRU针对所述第二类型在所述类型寄存器中记录第二类型标识；
和/或，
所述RRU针对所述第三类型在所述类型寄存器中记录第三类型标识。
优选地，所述第一类型为通用公共无线电接口CPRI协议，所述第二类型为LTE-IR接口协议，所述第三类型为TD-IR接口协议。
本申请实施例还公开了一种基于现场可编程门阵列FPGA射频拉远单元RRU接口协议自适应的装置，所述FPGA包括类型寄存器，所述装置包括：
位于RRU的加载模块，设置为加载FPGA；所述FPGA包括一个或多个接口协议类型；
位于RRU的接入模块，设置为采用任一所述接口协议类型接入基带处理单元BBU；
位于RRU的检测模块，设置为检测所述BBU的当前接口协议类型；
位于RRU的记录模块，设置为针对所述当前接口协议类型在所述类型寄存器中记录对应的类型标识；
位于RRU的配置模块，设置为针对所述类型标识对应的接口协议类型进行配置。
优选地，所述位于RRU的检测模块包括：
位于RRU的接收模块，设置为接收所述BBU发送的物理层控制字；
位于RRU的判断模块，设置为依据所述物理层控制字判断所述接口协议类型。
优选地，所述位于RRU的判断模块包括：
位于RRU的第一获取模块，设置为获取所述物理层控制字中第一预置超组位置的数据；
位于RRU的第一判断模块，设置为判断所述第一个数据是否为预置的数值；若是，则调用位于RRU的第一确定模块；
位于RRU的第一确定模块，设置为确定所述接口协议类型为第一类型。
优选地，所述位于RRU的判断模块包括：
位于RRU的第二获取模块，设置为获取所述物理层控制字中第二预置超组位置的RRU标识；
位于RRU的第二判断模块，设置为判断所述RRU标识是否为预置的RRU；若是，则调用位于RRU的第二确定模块；
位于RRU的第二确定模块，设置为确定所述接口协议类型为第二类型。
优选地，所述位于RRU的判断模块包括：
位于RRU的第三获取模块，设置为获取所述物理层控制字中第三预置超组位置的RRU标识；
位于RRU的第三判断模块，设置为判断所述RRU标识为预置的RRU标识；若是，则调用位于RRU的第三确定模块；
位于RRU的第三确定模块，设置为确定所述接口协议类型为第三类型。
优选地，所述位于RRU的记录模块包括：
位于RRU的第一记录模块，设置为针对所述第一类型在所述类型寄存器中记录第一类型标识；
和/或，
位于RRU的第二记录模块，设置为针对所述第二类型在所述类型寄 存器中记录第二类型标识；
和/或，
位于RRU的第三记录模块，设置为针对所述第三类型在所述类型寄存器中记录第三类型标识。
本申请实施例还公开了一种在其上记录有用于执行上述方法的程序的计算机可读记录介质。
与现有技术相比，本申请包括以下优点：
在本申请实施例中，RRU采用FPGA中的协议类型接入BBU后，检测出BBU当前接口协议类型，根据当前接口协议类型在寄存器中记录对应的类型标识，RRU针对该类型标识对应的接口协议类型进行配置，以适应对端BBU的要求，保证与对端设备接口协议的统一，降低正常通信实现的复杂度，保证共同组网中的设备正常通信。
在本申请实施例中，RRU接入BBU后，根据BBU发送的信息进行检测，并根据检测结果进行调整，使RRU能够自适应当前RRU接口协议，用户业务的中断时间短，不影响正常使用，用户体验效果好，不需要人工在RRU及BBU之间修改接口协议的类型信息，缩短了TD-SCDMA基站演进到TD-LTE基站改造时间，减少了人力成本和资源消耗。
在本申请实施例中，由于可直接使用现有的资源，因此能避免资源浪费，采用依据BBU发送的信息确定当前的接口协议方式，降低正常通信实现的复杂度，降低FPGA设计的复杂度。另外，在本申请实施例中并非针对某一制式，可以支持多种通信规范，支持多种接口协议，简单易实现，降低了对其外部设备的制约度。需要说明的是，本申请实施例同时也可以支持BBU接入同级或者上级BBU时接口协议的检测及调整。
附图说明
图1是一种TD-LTE基站中调整RRU接口协议的方法示意图；
图2是一种更换RRU软件包进行RRU接口协议的配置流程图；
图3是本申请的一种基于FPGA射频拉远单元RRU接口协议自适应的方法实施例的步骤流程图；
图4是本申请的一种RRU接口协议自适应流程示意图；
图5是一种现有技术FPGA固定协议类型的内部模块结构图；
图6是本申请的一种FPGA检测协议类型的内部模块结构图；
图7是本申请的一种FPGA内部进行接口协议检测流程示意图；
图8是本申请的一种基于FPGA射频拉远单元RRU接口协议自适应的装置实施例的结构框图。
具体实施方式
为使本申请的上述目的之一、特征和优点能够更加明显易懂，下面结合附图和具体实施方式对本申请作进一步详细的说明。
目前主要采用两种方式进行RRU与BBU之间接口协议的配置：
1)BBU与RRU之间的接口协议固定。参照图1所示的一种TD-LTE基站中调整RRU接口协议的方法示意图，RRU中的FPGA(Field Programmable Gata Array，现场可编程门阵列)版本生成时接口协议已经是确定的，并标识在相应的寄存器中，RRU软件通过获取FPGA中的类型寄存器，配置其软件侧消息类型，使RRU以固定的接口协议类型接入。当BBU侧的接口类型变化时，RRU侧FPGA需要修改版本来保证了BBU侧接口协议统一。
2)更换RRU软件包进行RRU接口协议的配置。参照图2所示的一种更换RRU软件包进行RRU接口协议的配置流程图，通过RRU软件的远程更新进行传输协议的配置。使用该方法的步骤包括：
S1，RRU采用原有的传输协议正常接入BBU；
S2，RRU控制LMT-B(NodeB Local Maintenance Terminal，基站的本地维护管理系统)通过原有的传输协议下载升级版本的RRU的软件包；
S3，升级版本的RRU的软件包下载完成后，人工控制触发RRU的软件包进行更新；
S4，RRU重新接入BBU，并触发BBU侧的软件版本更新；
S5，待BBU侧软件版本更新后，RRU重启；
S6，待RRU和BBU都完成软件更新后，RRU再次接入时，观测到 RRU以期望的传输协议接入，重新激活小区提供服务。
由于第一种方式BBU与RRU接口协议固定，即RRU的接口协议类型是固定的，必须明确BBU使用的接口协议，进而确定RRU侧的具体协议类型，导致双模的RRU只能和支持TD-LTE接口协议的BBU对接，不能支持和现有的TD-SCDMA单模BBU对接，而原有的TD-SCDMA单模RRU也只能和TD-SCDMA单模BBU对接，不能和新开发的双模BBU对接。在进行TD-SCDMA标准向TD-LTE标准的演进过程中，增加了原有TD-SCDMA基站改造的人力成本和资源消耗。第二种方式更换RRU软件包进行RRU接口协议的配置，虽然解决了第一种方式需要消耗大量的人力成本的问题，但是需要对BBU和RRU进行版本升级，但由于基站的机型复位操作，会造成小区长时间不能正常进行服务，会造成用户业务的长时间中断，影响用户使用。
为了解决上述问题，本专利发明人创造性地提出本申请实施例的核心构思之一在于，RRU采用FPGA中的协议类型接入BBU后，检测出BBU当前接口协议类型，根据当前接口协议类型在寄存器中记录对应的类型标识，RRU再针对该类型标识对应的接口协议类型进行配置，以适应对端BBU的要求，缩短TD-SCDMA基站演进到TD-LTE基站改造时间，保证与对端设备接口协议的统一，降低正常通信实现的复杂度，保证共同组网中的设备正常通信。
实施例一：
参照图3，示出了本申请的一种基于FPGA射频拉远单元RRU接口协议自适应的方法实施例的步骤流程图，所述FPGA可以包括类型寄存器，所述方法包括具体可以包括如下步骤：
步骤101，RRU加载FPGA；所述FPGA包括一个或多个接口协议类型；
在具体实现中，所述FPGA中存储有多种接口协议类型的信息，其中可以包括TD-SCDMA及TD-LTE的接口协议。在RRU启动时RRU软 件完成FPGA的加载，FPGA工作在默认的接口协议类型下。
步骤102，所述RRU采用任一所述接口协议类型接入基带处理单元BBU；
在本申请的一种优选示例中，RRU与BBU中安装有可以互相通信的旧的接口协议，并在PPGA中设置为默认的接口协议。当RRU要接入BBU时，首先采用默认的接口协议接入BBU，实现RRU与BBU之间的正常通信，以获取对应的BBU的接口协议的相关信息，对RRU本地的接口协议进行实适应性地调整。
步骤103，所述RRU检测所述BBU的当前接口协议类型；
在本申请的一种优选实施例中，所述步骤103可以包括如下子步骤：
子步骤S11，所述RRU接收所述BBU发送的物理层控制字；
子步骤S12，所述RRU依据所述物理层控制字判断所述接口协议类型。
在实际应用中当RRU与BBU之间的采用默认的接口协议进行通信时，RRU接收到BBU发送的物理层控制字，RRU的FPGA自动检测该物理层控制字，并根据检测结果判断对端BBU的接口协议类型。
在本申请的一种优选实施例中，所述子步骤S12可以包括如下子步骤：
子步骤S12-11，所述RRU获取所述物理层控制字中第一预置超组位置的数据；
子步骤S12-12，所述RRU判断所述第一个数据是否为预置的数值；若是，则执行子步骤S12-13；
子步骤S12-13，所述RRU确定所述接口协议类型为第一类型。
在本申请的一种优选实施例中，所述子步骤S12可以包括如下子步骤：
子步骤S12-21，所述RRU获取所述物理层控制字中第二预置超组位置的RRU标识；
子步骤S12-22，所述RRU判断所述RRU标识是否为预置的RRU； 若是，则执行子步骤S12-23；
子步骤S12-23，所述RRU确定所述接口协议类型为第二类型。
在本申请的一种优选实施例中，所述子步骤S12可以包括如下子步骤：
子步骤S12-31，所述RRU获取所述物理层控制字中第三预置超组位置的RRU标识；
子步骤S12-32，所述RRU判断所述RRU标识为预置的RRU标识；若是，则执行子步骤S12-33；
子步骤S12-33，所述RRU确定所述接口协议类型为第三类型。
步骤104，所述RRU针对所述当前接口协议类型在所述类型寄存器中记录对应的类型标识；
在本申请的一种优选实施例中，所述步骤104可以包括如下子步骤：
子步骤S21，所述RRU针对所述第一类型在所述类型寄存器中记录第一类型标识；
和/或，
子步骤S22，所述RRU针对所述第二类型在所述类型寄存器中记录第二类型标识；
和/或，
子步骤S23，所述RRU针对所述第三类型在所述类型寄存器中记录第三类型标识。
步骤105，所述RRU针对所述类型标识对应的接口协议类型进行配置。
在具体实现中，RRU与BBU之间正常通信后，FPGA自动检测实际接入的BBU接口协议类型，并根据该接口协议类型在寄存器中标识。RRU软件通过读取FPGA的寄存器中的标识判断目前所接BBU的接口协议类型，最后，软件根据此接口协议类型完成RRU侧所有相关配置。
为了使本领域技术人员进一步了解本申请实施例，以下采用具体的示例来进行说明。
在本申请实施例中，利用FPGA对当前的RRU接口协议进行实时检测，实现RRU接口协议动态调整的功能。参照图4所示的本申请的一种RRU接口协议自适应流程示意图，在FPGA中包括有可以让RRU及BBU之间正常通信的接口协议类型，具体步骤如下所示：
步骤1，RRU启动时软件完成FPGA的加载，让FPGA工作在默认接口协议类型下。此时，FPGA默认接口协议自适应寄存器，即类型寄存器的值为0x0(无效协议)。
步骤2，RRU的FPGA接收在默认接口协议类型下BBU发送的信息，并根据该信息自动检测实际接入的协议类型，并在自适应寄存器中标识。FPGA向RRU软件反馈协议自适应寄存器当前值，RRU软件接收后读取自适应寄存器的值判断目前所接BBU的接口协议类型是否为有效的接口协议类型，若是，则执行步骤4，若否，则执行步骤3。
步骤3，RRU软件根据此接口协议类型完成RRU侧FPGA协议寄存器的相关配置。
步骤4，重复步骤2，RRU软件继续查询寄存器值是否为有效协议类型。
参照图5所示的一种现有技术FPGA固定协议类型的内部模块结构图，在RRU_FPGA中，SERDES(SERializer/DESerializer，串行器/解串器)接收的对端设备的数据DATA，RRU软件只能根据已经提前固化在RRU接口协议配置接口协议类型寄存器。
在本申请实施例中，在RRU中增加了接口协议测试模块，用以根据SERDES接收到的数据进行检测及调整RRU接口协议。参照图6所示的本申请的一种FPGA检测协议类型的内部模块结构图，在RRU_FPGA中增加了RRU接口协议实时检测模块PLT_TEST，用以实现传输速率匹配情况下的RRU接口协议的实时检测功能，通过与软件的接口通知RRU软件当前RRU接口协议，RRU软件再进行RRU接口协议模式进行配置。
具体而言，PLT_TEST分为以下三个模块，分别为TD-IR协议实时解析模块、LTE协议实时解析模块以及CPRI协议实时解析模块。需要说明 的是，在TD-SCDMA中，每个时隙由多个25S时长的超组Super-Group组成，每个Super-Group中包括32个组Group。每个Group由24个字组成，在一个Super-Group内，第一个Group的第一个字节作为同步字k28.5，第二个字节传送SGN(Super-GroupNumber，超组号)。
参照图7所示的本申请的一种FPGA内部进行接口协议检测流程示意图，在FPGA版本中默认协议自适应寄存器值为0x0(无效协议)。SERDES接收的数据后，将该数据分别发送至TD-IR协议实时解析模块、LTE协议实时解析模块以及CPRI协议实时解析模块，上述三个模块接收到SERDES的数据后，分别针对该数据进行检测，三个模块的检测步骤如下所示：
TD-IR协议实时解析模块：
根据TD-IR协议帧结构解析下行收到的数据：从超组号RRUID为33开始解析物理层控制字的内容，解析完成后根据TD-IR协议对数据进行校验，校验正确后会把FPGA与RRU软件的类型寄存器的第一比特位置1。例如，将类型寄存器bit0置为1，即0x1。
LTE-IR协议实时解析模块：
根据LTE-IR协议帧结构解析下行收到的数据：由于LTE从超组号RRUID为80开始解析物理层控制字的内容，解析完成后根据LTE-IR协议对数据进行校验，校验正确后会把FPGA与RRU软件的类型寄存器的第二比特位置1。例如，将类型寄存器bitl置为1，即0x2。
CPRI协议实时解析模块：
根据CPRI协议帧结构解析下行收到的数据：若检测到K28.5同步字相邻的24位数据为0x50c550，则当前链路传输的协议为CPRI，此时将FPGA与RRU软件的类型寄存器的第三比特位置1。例如，将类型寄存器bit2置为1，即0x3。
在实际应用中，RRU软件正常加载完成FPGA后，开始检测光模块状态，随后配置FPGA的SERDES速率，延时等待，此时FPGA开始实时检测当前RRU接口协议类型，接收到的链路数据同时送给TD-IR协议 实时解析模块、LTE-IR协议实时解析模块，CPRI协议实时解析模块，这三个模块设置为对链路数据按照TD-IR协议、LTE-IR协议、CPRI协议并行实时解析。当然，RRU也可以按照其他接口协议进行调整，本申请实施例对此不作限制。
在本申请实施例中，实现了RRU实时解析三种接口协议，并利用了FPGA内部检测光口接收数据的低延时特性。具体而言，通过采用实时解析物理层控制字中解析RRUID所在超组号，判断RRU当前工作的接口协议类型，RRU软件在根据FPGA上报的接口协议类型完成光口协议配置的流程，可以支持《TD-SCDMA数字蜂窝移动通信网分布式基站的Ir接口技术要求》，《TD-LTE蜂窝移动通信网分布式基站Ir接口技术要求》及CPRI接口三种规范的协议自适应功能。
综上所述，本申请实施例相对于现有技术具有如下优点：
1，自动实现RRU接口协议的检测及调整。
2，随着TD-SCDMA基站向TD-LTE基站的平滑演进升级，运营商不断要求升级演进带来的业务中断时间进一步缩短。以及TD-LTE基站与FDD-LTE基站融合组网的要求，RRU能够自动根据当前的RRU接口协议完成接入基带单元设备BBU的需求。采用这种技术的RRU可以满足运营商提出的升级演进过程尽量小的业务中断时间的要求，降低正常通信实现的复杂度，减少了人力成本和资源消耗。
3，可以支持BBU接入同级或者上级BBU时接口协议的检测及调整。
需要说明的是，对于方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本申请并不受所描述的动作顺序的限制，因为依据本申请，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作并不一定是本申请所必须的。
实施例二：
参照图8，示出了本申请的一种基于FPGA射频拉远单元RRU接口 协议自适应的装置实施例的结构框图，所述FPGA可以包括类型寄存器，所述装置具体可以包括如下模块：
位于RRU的加载模块201，设置为加载FPGA；所述FPGA包括一个或多个接口协议类型；
位于RRU的接入模块202，设置为采用任一所述接口协议类型接入基带处理单元BBU；
位于RRU的检测模块203，设置为检测所述BBU的当前接口协议类型；
在本申请的一种优选实施例中，所述位于RRU的检测模块203可以包括：
位于RRU的接收模块，设置为接收所述BBU发送的物理层控制字；
位于RRU的判断模块，设置为依据所述物理层控制字判断所述接口协议类型。
在本申请的一种优选实施例中，所述位于RRU的判断模块可以包括：
位于RRU的第一获取模块，设置为获取所述物理层控制字中第一预置超组位置的数据；
位于RRU的第一判断模块，设置为判断所述第一个数据是否为预置的数值；若是，则调用位于RRU的第一确定模块；
位于RRU的第一确定模块，设置为确定所述接口协议类型为第一类型。
在本申请的一种优选实施例中，所述位于RRU的判断模块可以包括：
位于RRU的第二获取模块，设置为获取所述物理层控制字中第二预置超组位置的RRU标识；
位于RRU的第二判断模块，设置为判断所述RRU标识是否为预置的RRU；若是，则调用位于RRU的第二确定模块；
位于RRU的第二确定模块，设置为确定所述接口协议类型为第二类型。
在本申请的一种优选实施例中，所述位于RRU的判断模块可以包括：
位于RRU的第三获取模块，设置为获取所述物理层控制字中第三预置超组位置的RRU标识；
位于RRU的第三判断模块，设置为判断所述RRU标识为预置的RRU标识；若是，则调用位于RRU的第三确定模块；
位于RRU的第三确定模块，设置为确定所述接口协议类型为第三类型。
位于RRU的记录模块204，设置为针对所述当前接口协议类型在所述类型寄存器中记录对应的类型标识；
在本申请的一种优选实施例中，所述位于RRU的记录模块204可以包括：
位于RRU的第一记录模块，设置为针对所述第一类型在所述类型寄存器中记录第一类型标识；
和/或，
位于RRU的第二记录模块，设置为针对所述第二类型在所述类型寄存器中记录第二类型标识；
和/或，
位于RRU的第三记录模块，设置为针对所述第三类型在所述类型寄存器中记录第三类型标识。
位于RRU的配置模块205，设置为针对所述类型标识对应的接口协议类型进行配置。
对于装置实施例而言，由于其与方法实施例基本相似，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
实施例三：
本申请实施例还公开了一种在其上记录有用于执行上述方法的程序的计算机可读记录介质。
所述计算机可读记录介质包括用于以计算机(例如计算机)可读的形式存储或传送信息的任何机制。例如，机器可读介质包括只读存储器 (ROM)、随机存取存储器(RAM)、磁盘存储介质、光存储介质、闪速存储介质、电、光、声或其他形式的传播信号(例如，载波、红外信号、数字信号等)等。
本说明书中的各个实施例均采用递进的方式描述，每个实施例重点说明的都是与其他实施例的不同之处，各个实施例之间相同相似的部分互相参见即可。
本领域内的技术人员应明白，本申请的实施例可提供为方法、装置、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算 机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例做出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
最后，还需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个......”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
以上对本申请所提供的一种基于FPGA射频拉远单元RRU接口协议自适应的方法，以及，一种基于FPGA射频拉远单元RRU接口协议自适应的装置，进行了详细介绍，本文中应用了具体个例对本申请的原理及实施方式进行了阐述，以上实施例的说明只是设置为帮助理解本申请的方法及其核心思想；同时，对于本领域的一般技术人员，依据本申请的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本申请的限制。

Claims (14)

  1. 一种基于现场可编程门阵列FPGA射频拉远单元RRU接口协议自适应的方法，其特征在于，所述现场可编程门阵列FPGA包括类型寄存器，所述方法包括：
    RRU加载FPGA；所述FPGA包括一个或多个接口协议类型；
    所述RRU采用任一所述接口协议类型接入基带处理单元BBU；
    所述RRU检测所述BBU的当前接口协议类型；
    所述RRU针对所述当前接口协议类型在所述类型寄存器中记录对应的类型标识；
    所述RRU针对所述类型标识对应的接口协议类型进行配置。
  2. 根据权利要求1所述的方法，其特征在于，所述RRU检测所述BBU的当前接口协议类型的步骤包括：
    所述RRU接收所述BBU发送的物理层控制字；
    所述RRU依据所述物理层控制字判断所述接口协议类型。
  3. 根据权利要求2所述的方法，其特征在于，所述RRU依据所述物理层控制字判断所述接口协议类型的步骤包括：
    所述RRU获取所述物理层控制字中第一预置超组位置的数据；
    所述RRU判断所述第一个数据是否为预置的数值；
    若是，则所述RRU确定所述接口协议类型为第一类型。
  4. 根据权利要求3所述的方法，其特征在于，所述RRU检测所述BBU的当前接口协议类型的步骤包括：
    所述RRU获取所述物理层控制字中第二预置超组位置的RRU标识；
    所述RRU判断所述RRU标识是否为预置的RRU；
    若是，则所述RRU确定所述接口协议类型为第二类型。
  5. 根据权利要求4所述的方法，其特征在于，所述RRU检测所述BBU的当前接口协议类型的步骤包括：
    所述RRU获取所述物理层控制字中第三预置超组位置的RRU标识；
    所述RRU判断所述RRU标识为预置的RRU标识；
    若是，则所述RRU确定所述接口协议类型为第三类型。
  6. 根据权利要求3或4或5所述的方法，其特征在于，所述RRU针对所述当前接口协议类型在所述类型寄存器中记录对应的类型标识的步骤包括：
    所述RRU针对所述第一类型在所述类型寄存器中记录第一类型标识；
    和/或，
    所述RRU针对所述第二类型在所述类型寄存器中记录第二类型标识；
    和/或，
    所述RRU针对所述第三类型在所述类型寄存器中记录第三类型标识。
  7. 根据权利要求6所述的方法，其特征在于，所述第一类型为通用公共无线电接口CPRI协议，所述第二类型为LTE-IR接口协议，所述第三类型为TD-IR接口协议。
  8. 一种基于现场可编程门阵列FPGA射频拉远单元RRU接口协议自适应的装置，其特征在于，所述现场可编程门阵列FPGA包括类型寄存器，所述装置包括：
    位于RRU的加载模块，设置为加载FPGA；所述FPGA包括一个或多个接口协议类型；
    位于RRU的接入模块，设置为采用任一所述接口协议类型接入基带处理单元BBU；
    位于RRU的检测模块，设置为检测所述BBU的当前接口协议类型；
    位于RRU的记录模块，设置为针对所述当前接口协议类型在所述类型寄存器中记录对应的类型标识；
    位于RRU的配置模块，设置为针对所述类型标识对应的接口协议类型进行配置。
  9. 根据权利要求8所述的装置，其特征在于，所述位于RRU的检 测模块包括：
    位于RRU的接收模块，设置为接收所述BBU发送的物理层控制字；
    位于RRU的判断模块，设置为依据所述物理层控制字判断所述接口协议类型。
  10. 根据权利要求9所述的装置，其特征在于，所述位于RRU的判断模块包括：
    位于RRU的第一获取模块，设置为获取所述物理层控制字中第一预置超组位置的数据；
    位于RRU的第一判断模块，设置为判断所述第一个数据是否为预置的数值；若是，则调用位于RRU的第一确定模块；
    位于RRU的第一确定模块，设置为确定所述接口协议类型为第一类型。
  11. 根据权利要求10所述的装置，其特征在于，所述位于RRU的判断模块包括：
    位于RRU的第二获取模块，设置为获取所述物理层控制字中第二预置超组位置的RRU标识；
    位于RRU的第二判断模块，设置为判断所述RRU标识是否为预置的RRU；若是，则调用位于RRU的第二确定模块；
    位于RRU的第二确定模块，设置为确定所述接口协议类型为第二类型。
  12. 根据权利要求11所述的装置，其特征在于，所述位于RRU的判断模块包括：
    位于RRU的第三获取模块，设置为获取所述物理层控制字中第三预置超组位置的RRU标识；
    位于RRU的第三判断模块，设置为判断所述RRU标识为预置的RRU标识；若是，则调用位于RRU的第三确定模块；
    位于RRU的第三确定模块，设置为确定所述接口协议类型为第三类型。
  13. 根据权利要求10或11或12所述的装置，其特征在于，所述位于RRU的记录模块包括：
    位于RRU的第一记录模块，设置为针对所述第一类型在所述类型寄存器中记录第一类型标识；
    和/或，
    位于RRU的第二记录模块，设置为针对所述第二类型在所述类型寄存器中记录第二类型标识；
    和/或，
    位于RRU的第三记录模块，设置为针对所述第三类型在所述类型寄存器中记录第三类型标识。
  14. 一种在其上记录有用于执行权利要求1所述方法的程序的计算机可读记录介质。
PCT/CN2015/074214 2014-05-29 2015-03-13 基于fpga射频拉远单元rru接口协议自适应的方法及装置 WO2015180523A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP15799047.4A EP3151607B1 (en) 2014-05-29 2015-03-13 Fpga-based self-adaption method and apparatus for remote radio unit (rru) interface protocol
US15/311,364 US10298453B2 (en) 2014-05-29 2015-03-13 Adaptive method and device based on FPGA RRU interface protocol

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410234496.9A CN104053174B (zh) 2014-05-29 2014-05-29 基于fpga基带单元设备rru接口协议自适应的方法及装置
CN201410234496.9 2014-05-29

Publications (1)

Publication Number Publication Date
WO2015180523A1 true WO2015180523A1 (zh) 2015-12-03

Family

ID=51505441

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/074214 WO2015180523A1 (zh) 2014-05-29 2015-03-13 基于fpga射频拉远单元rru接口协议自适应的方法及装置

Country Status (4)

Country Link
US (1) US10298453B2 (zh)
EP (1) EP3151607B1 (zh)
CN (1) CN104053174B (zh)
WO (1) WO2015180523A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112187722A (zh) * 2020-09-02 2021-01-05 博依特(广州)工业互联网有限公司 一种基于fpga的安全隔离系统

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104053174B (zh) * 2014-05-29 2018-03-27 大唐移动通信设备有限公司 基于fpga基带单元设备rru接口协议自适应的方法及装置
CN106330324B (zh) * 2015-07-09 2020-09-22 中兴通讯股份有限公司 一种控制方法及装置
CN106686636A (zh) * 2015-11-10 2017-05-17 中兴通讯股份有限公司 确定基站可用性的方法、装置及基站
CN106713314A (zh) 2016-12-22 2017-05-24 惠州Tcl移动通信有限公司 一种面向5g的协议栈多维度切分方法及其装置
CN108959134B (zh) * 2017-05-24 2022-02-15 微软技术许可有限责任公司 用于现场可编程门阵列设备的通信
CN109729530B (zh) * 2017-10-31 2021-03-09 大唐移动通信设备有限公司 一种小区的建立方法和装置
CN112787982B (zh) * 2019-11-08 2024-09-27 中兴通讯股份有限公司 协议切换方法及装置、电子设备、计算机可读介质
EP4210375A4 (en) * 2020-09-25 2023-11-01 Huawei Technologies Co., Ltd. COMMUNICATION METHOD, APPARATUS AND SYSTEM
CN114697988A (zh) * 2020-12-30 2022-07-01 大唐移动通信设备有限公司 一种rru测试方法、装置及介质
CN114697310B (zh) * 2020-12-30 2023-04-28 大唐移动通信设备有限公司 一种升级文件分配方法、调度服务器、装置及存储介质
CN116684993A (zh) * 2022-02-22 2023-09-01 华为技术有限公司 一种自适应建立链路的方法，基带单元和无线电单元
CN114885043B (zh) * 2022-05-23 2024-03-22 南京濠暻通讯科技有限公司 一种自适应前传协议的接口系统及方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102014463A (zh) * 2009-12-17 2011-04-13 大唐移动通信设备有限公司 一种进行接入的方法和装置
CN102300236A (zh) * 2010-06-28 2011-12-28 电信科学技术研究院 一种远程维护射频拉远设备的方法、装置及系统
CN102612166A (zh) * 2011-01-21 2012-07-25 华为技术有限公司 一种数据处理方法、基站系统以及相关设备
US20120250740A1 (en) * 2011-01-07 2012-10-04 Integrated Device Technology, Inc. Ofdm signal processing in a base transceiver system
CN104053174A (zh) * 2014-05-29 2014-09-17 大唐移动通信设备有限公司 基于fpga基带单元设备rru接口协议自适应的方法及装置

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6678751B1 (en) * 1999-10-15 2004-01-13 Micro Motion, Inc. System for setting frame and protocol for transmission in a UART device
CN101098328B (zh) * 2007-06-29 2010-06-02 中兴通讯股份有限公司 一种基带与射频系统同步和时延补偿方法
CN101193084A (zh) * 2007-11-21 2008-06-04 中兴通讯股份有限公司 一种基于srio协议的分布式基站系统及其基带和射频单元
CN101483459B (zh) * 2008-01-11 2012-05-23 鼎桥通信技术有限公司 一种智能天线的校准方法
CN101702826B (zh) * 2009-10-20 2011-09-28 武汉虹信通信技术有限责任公司 Td-scdma rru级联光纤时延补偿装置及方法
CN101695192A (zh) * 2009-10-22 2010-04-14 中兴通讯股份有限公司 实现基带处理单元与射频单元之间资源分配的方法及系统
CN102056184B (zh) * 2009-10-30 2014-04-23 中兴通讯股份有限公司 射频拉远单元链路自适应方法及装置
CN102594829B (zh) * 2012-02-29 2014-08-06 电信科学技术研究院 一种基带转接设备及其进行转接的方法
CN102665237B (zh) * 2012-04-24 2014-09-10 北京邮电大学 Ir接口协议一致性仿真测试装置及互联互通测试方法
US9191209B2 (en) * 2013-06-25 2015-11-17 Google Inc. Efficient communication for devices of a home network
CN103702374B (zh) * 2014-01-13 2017-03-29 武汉邮电科学研究院 一种支持lte网络拓扑的切换系统及方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102014463A (zh) * 2009-12-17 2011-04-13 大唐移动通信设备有限公司 一种进行接入的方法和装置
CN102300236A (zh) * 2010-06-28 2011-12-28 电信科学技术研究院 一种远程维护射频拉远设备的方法、装置及系统
US20120250740A1 (en) * 2011-01-07 2012-10-04 Integrated Device Technology, Inc. Ofdm signal processing in a base transceiver system
CN102612166A (zh) * 2011-01-21 2012-07-25 华为技术有限公司 一种数据处理方法、基站系统以及相关设备
CN104053174A (zh) * 2014-05-29 2014-09-17 大唐移动通信设备有限公司 基于fpga基带单元设备rru接口协议自适应的方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3151607A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112187722A (zh) * 2020-09-02 2021-01-05 博依特(广州)工业互联网有限公司 一种基于fpga的安全隔离系统

Also Published As

Publication number Publication date
CN104053174A (zh) 2014-09-17
EP3151607A4 (en) 2017-11-01
US10298453B2 (en) 2019-05-21
EP3151607B1 (en) 2018-12-12
EP3151607A1 (en) 2017-04-05
US20170118075A1 (en) 2017-04-27
CN104053174B (zh) 2018-03-27

Similar Documents

Publication Publication Date Title
WO2015180523A1 (zh) 基于fpga射频拉远单元rru接口协议自适应的方法及装置
US9445286B2 (en) Protocol version negotiation method, mobile terminal, base station and communications system
US11510275B2 (en) Configuration method for discontinuous reception parameters, terminal and network-side device
US9749377B2 (en) Method and system for network access control
JP6370908B2 (ja) デュアル接続アーキテクチャのための不連続受信（ｄｒｘ）整列技術
JP7182628B2 (ja) 無線通信方法、端末デバイス及びネットワークデバイス
TWI489818B (zh) 遠端升級伺服器及其適用之負載平衡方法
JP6254747B2 (ja) 情報提供方法、装置、プログラム及び記録媒体
RU2019127912A (ru) Радиотерминал, радиостанция, узел базовой сети и способ в них
JP7142710B2 (ja) 無線アクセス技術間ハンドオーバの方法
WO2021121001A1 (zh) 通信参数配置方法、装置、设备和存储介质
WO2016119218A1 (zh) 呼叫补充业务配置同步方法、装置及系统
US11630711B2 (en) Access control configurations for inter-processor communications
WO2014121471A1 (zh) 数据传输、获取方法、基站及用户设备
US10708870B2 (en) Systems and methods for adjusting power settings of a wireless device
WO2013114317A1 (en) Updating modem baseband firmware over-the-air
WO2016070756A1 (zh) 管理家庭网关的方法、装置和系统
US11690039B2 (en) Wireless communication method of dual-registered terminal device, terminal device, and network device
TWI609600B (zh) 減少傳呼作業之裝置與方法
TWI778614B (zh) 確定、指示接取參數的方法、終端、基地台及電腦可讀存儲介質
US8417220B2 (en) Method, apparatus and computer program product for security configuration coordination during a cell update procedure
WO2016180114A1 (zh) 终端热点休眠的方法和装置
US10880947B2 (en) Control plane latency reduction in a wireless communications network
US20160135215A1 (en) Long term evolution network system and data transmission scheduling method thereof
US9485670B2 (en) Method, apparatus and computer program product for security configuration coordination during a cell update procedure

Legal Events

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

Ref document number: 15799047

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15311364

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015799047

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015799047

Country of ref document: EP