CN107466050B

CN107466050B - Management method and device for RRS (remote radio system)

Info

Publication number: CN107466050B
Application number: CN201610390417.2A
Authority: CN
Inventors: 段然; 黄金日; 孔令斌; 孙军帅
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2016-06-02
Filing date: 2016-06-02
Publication date: 2020-11-06
Anticipated expiration: 2036-06-02
Also published as: CN107466050A

Abstract

The invention discloses a management method and a device of a remote radio system RRS. The method comprises the following steps: the method comprises the steps that a wireless cloud center (RCC) receives a discovery message sent by an RRS, wherein the discovery message carries an identification of the RRS; if the RCC sends a registration invitation message to the RRS according to the identification of the RRS carried in the discovery message; the RCC receives a registration request message sent by the RRS, wherein the registration request message carries an identifier of the RCC to which the RRS belongs; and if the RCC judges that the attributive RCC of the RRS is the RCC according to the identification of the attributive RCC of the RRS carried in the registration request message, the RCC registers the RRS. The invention can realize automatic and flexible networking between the RCC and the RRS.

Description

Management method and device for RRS (remote radio system)

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for managing a remote radio system RRS.

Background

In recent years, C-RAN (Centralized, Cooperative, Cloud-Radio Access Network, Centralized, Cooperative, Cloud-architecture, and green Radio Access Network) Network deployment of a Centralized BBU (Base Band Unit) and a Remote RRU (Radio Remote Unit) is increasingly widely applied in many countries and regions around the world, and BBU Centralized deployment proposed by C-RAN has significant advantages of accelerating Network deployment, reducing operation and maintenance and investment costs, effectively supporting key technologies such as cooperation and carrier aggregation, and improving Network performance.

However, the conventional front end transmission Interface CPRI (Common Public Radio Interface) has the disadvantages of low transmission efficiency, poor expandability, poor flexibility and the like due to the limitations of a point-to-point transmission mode, fixed rate transmission characteristics and the like of the CPRI and the influence of high bandwidth requirements of the existing BBU/RRU Interface, and is not suitable for a future wireless network architecture. The C-RAN deployment limits the large-scale deployment if the CPRI is used for front-end transmission networking. Taking LTE (Long term evolution ) as an example, the CPRI interface requires high bandwidth and low time delay, and although the forward transmission problem can be solved based on active or passive wavelength division transmission technology at present, additional transmission equipment is introduced, which causes cost increase. In addition, the requirement of dual-route protection after the C-RAN centralization also requires the realization of flexible routing between the BBU baseband pool and the RRU. Therefore, the traditional CPRI interface is difficult to support the networking requirements of the future wireless network centralized deployment.

In order to better improve the utilization efficiency of network resources, better support the evolution of wireless network to 5G system, and better support the centralized deployment of BBU, the NGFI (Next Generation front end transmission Interface) is in the process of being developed. In the wireless network architecture based on the NGFI, on one hand, part of BBU processing functions are moved to the RRU, which causes the change of the form of the BBU and the RRU, and after reconstruction, the BBU processing functions are redefined to be an RCC (Radio Cloud Center) and an RRS (Radio Remote System) respectively, and on the other hand, the front-end transmission is redefined to be a multipoint-to-multipoint front-end transmission network from a point-to-point interface based on a packet switching protocol.

For a wireless network based on NGFI, in which front-end transmission is defined as multipoint-to-multipoint, how to realize automatic and flexible networking between RCC and RRS is a problem to be solved in the industry.

Disclosure of Invention

The embodiment of the invention provides a management method and a management device of RRS (remote radio resource control), which are used for realizing automatic and flexible networking between RCC (remote control center) and RRS.

An embodiment of the present invention provides a method for managing an RRS, including:

a wireless cloud center (RCC) receives a discovery message sent by an RRS, wherein the discovery message carries an identifier of the RRS;

the RCC sends a registration invitation message to the RRS according to the identification of the RRS carried in the discovery message;

the RCC receives a registration request message sent by the RRS, wherein the registration request message carries an identifier of a home RCC of the RRS;

and if the RCC judges that the attributive RCC of the RRS is the RCC according to the identifier of the attributive RCC of the RRS carried in the registration request message, the RCC registers the RRS.

Specifically, the RCC sends a registration invitation message to the RRS according to the identifier of the RRS carried in the discovery message, including:

if the RCC judges that the RRS is not registered on the RCC according to the identification of the RRS carried in the discovery message, the RCC sends a registration invitation message to the RRS; or

And if the RCC judges that the RRS is not registered on the RCC according to the identification of the RRS carried in the discovery message and judges that the RCC can be used as a home RCC of the RRS, the RCC sends a registration invitation message to the RRS.

Further, the RCC determining, according to the identifier of the RRS carried in the discovery message, whether the RRS is registered on the RCC, including:

the RCC inquires the identification of the RRS marked as registered or pre-registered on the RCC in the RCC according to the identification of the RRS carried in the discovery message;

if the RCC does not inquire the identification of the RRS in the identifications of the RRS marked as registered and pre-registered to the RCC, the RCC judges that the RRS is not registered to the RCC;

after the RCC sends the registration invitation message to the RRS, the method further includes:

and the RCC saves the identification of the RRS carried in the discovery message and marks the RRS as pre-registered to the RCC.

Specifically, the determining, by the RCC, whether the RCC can serve as the home RCC of the RRS includes:

if the RCC determines that the RCC is matched with the RRS according to the configuration information of the RRS carried in the discovery message, the RCC judges that the RCC can be used as a home RCC of the RRS; or

If the RCC judges that the RRS can be accepted according to the processing capacity of the RCC, the RCC judges that the RCC can be used as a home RCC of the RRS; or

If the RCC determines that the RCC is matched with the RRS according to the configuration information of the RRS carried in the discovery message and the RCC can accept the RRS according to the processing capacity judgment of the RCC, the RCC judges that the RCC can be used as the home RCC of the RRS.

Specifically, the RCC registers the RRS, including: the RCC saves the configuration information of the RRS, establishes a link with the RRS and marks the RRS as being registered on the RCC.

Specifically, if the RCC determines that the home RCC of the RRS is not the RCC according to the identifier of the home RCC of the RRS carried in the registration request message, the method further includes:

and the RCC deletes the mark pre-registered by the RRS on the RCC and saves the attribution relationship between the identification of the RRS and the identification of the attribution RCC of the RRS.

Wherein, the registration request message is a broadcast message.

Specifically, if the RCC determines that the RRS is registered on the RCC according to the identifier of the RRS carried in the discovery message, the method further includes:

the RCC sends a keep-alive acknowledgement message to the RRS, the keep-alive acknowledgement message being used to inform the RRS that the RRS is registered on the RCC.

Wherein, the registration invitation message carries one or more of the following information: geographical location information of the RCC, communication bandwidth information between the RCC and the RRS, and communication delay information between the RCC and the RRS.

An embodiment of the present invention provides an RRS management apparatus for an application and an RCC, including:

a receiving module, configured to receive a discovery message sent by an RRS, where the discovery message carries an identifier of the RRS; and the registration request message is used for receiving the registration request message sent by the RRS, and the registration request message carries the identifier of the home RCC of the RRS;

a sending module, configured to send a registration invitation message to the RRS according to the identifier of the RRS carried in the discovery message received by the receiving module;

a determining module, configured to determine whether the RRS belongs to the RCC according to the identifier of the RRS belonging to the RCC, which is carried in the registration request message received by the receiving module;

and the registration module is used for registering the RRS when the judging module judges that the attributive RCC of the RRS is the RCC.

The sending module is specifically configured to:

if the RRS is judged not to be registered on the RCC according to the identification of the RRS carried in the discovery message, a registration invitation message is sent to the RRS; or

And if the RRS is judged not to be registered on the RCC according to the identification of the RRS carried in the discovery message and the RCC can be used as the home RCC of the RRS, sending a registration invitation message to the RRS.

Further, the sending module is specifically configured to:

inquiring the identification of the RRS marked as registered or pre-registered on the RCC in the RCC according to the identification of the RRS carried in the discovery message;

if the identification of the RRS is not inquired in the identifications of the RRS marked as registered and pre-registered to the RCC, judging that the RRS is not registered to the RCC;

some embodiments of the present invention provide an application and RRS management apparatus on an RCC, further including:

a storing module, configured to store the identifier of the RRS carried in the discovery message after the sending module sends a registration invitation message to the RRS, and mark the RRS as pre-registered on the RCC.

The sending module is specifically configured to:

if the RCC is determined to be matched with the RRS according to the configuration information of the RRS carried in the discovery message, judging that the RCC can be used as a home RCC of the RRS; or

If the RRS can be accepted according to the processing capacity of the RCC, judging that the RCC can be used as the home RCC of the RRS; or

And if the RCC is determined to be matched with the RRS according to the configuration information of the RRS carried in the discovery message and the RRS can be accepted according to the processing capability of the RCC, judging that the RCC can be used as the home RCC of the RRS.

The registration module is specifically configured to: and when the judging module judges that the home RCC of the RRS is the RCC according to the identifier of the home RCC of the RRS carried in the registration request message, storing the configuration information of the RRS, establishing a link with the RRS, and marking the RRS as being registered on the RCC.

Further, some embodiments of the present invention provide an application and RRS management apparatus on an RCC, further including: and the maintenance module is configured to delete the mark preregistered by the RRS on the RCC when the determination module determines that the home RCC of the RRS is not the RCC according to the identifier of the home RCC of the RRS carried in the registration request message, and store the home relationship between the identifier of the RRS and the identifier of the home RCC of the RRS.

Wherein, the registration request message is a broadcast message.

Further, the sending module is further configured to: and if the RRS is judged to be registered on the RCC according to the identification of the RRS carried in the discovery message, sending a keep-alive confirmation message to the RRS, wherein the keep-alive confirmation message is used for informing that the RRS is registered on the RCC.

In the management method of the RRS provided in the foregoing embodiment of the present invention, the RCC may send a registration invitation message to the RRS according to the received discovery message, and may further receive a registration request message sent by the RRS, thereby determining whether to register the RRS. It can be seen that, in the above embodiment of the present invention, the RCC can discover the RRS in the network, send the registration invitation message to the RRS in the network, and further determine whether to register the RRS according to the registration request message fed back by the RRS, so that the RCC in the network can flexibly perform networking with the RRS in the network, thereby implementing automatic and flexible networking between the RCC and the RRS.

the RRS sends a discovery message to the RCC, wherein the discovery message carries the identification of the RRS;

the RRS receives registration invitation messages sent by one or more RCCs, wherein the registration invitation message sent by one RCC is sent to the RRS by the RCC according to the identification of the RRS carried in the discovery message;

the RRS determines the home RCC of the RRS according to the received registration invitation message;

and the RRS sends a registration request message, wherein the registration request message carries the identifier of the attributive RCC determined by the RRS.

Specifically, the determining, by the RRS, the home RCC of the RRS according to the received registration invitation message includes: the RRS determines that one RCC is taken as the home RCC of the RRS according to one or more of the following information carried in the received registration invitation message sent by one or more RCCs: geographical location information of the RCC, communication bandwidth information between the RCC and the RRS, and communication delay information between the RCC and the RRS.

Further, after the registration of the RRS with the RCC to which the RRS belongs is completed, the method further includes:

the RRS sends a discovery message again;

the RRS receives a keep-alive confirmation message sent by the home RCC of the RRS and receives registration invitation messages sent by N other RCCs, wherein N is an integer greater than or equal to 1;

the RRS obtains one or more of the following information of the home RCC and the other RCCs of the RRS according to the received keep-alive confirmation message and the N registration invitation messages: geographical location information of the RCC, communication bandwidth information between the RCC and the RRS, and communication delay information between the RCC and the RRS.

Wherein, the registration request message is a broadcast message.

An embodiment of the present invention provides an application and RRS management apparatus on an RRS, including:

a sending module, configured to send a discovery message to an RCC, where the discovery message carries an identifier of the RRS; and the system is used for sending a registration request message, wherein the registration request message carries the identifier of the attributive RCC determined by the RRS;

a receiving module, configured to receive a registration invitation message sent by one or more RCCs, where the registration invitation message sent by one RCC is sent to the RRS by the RCC according to the identifier of the RRS carried in the discovery message;

a determining module, configured to determine, according to the registration invitation message received by the receiving module and sent by one or more RCCs, a home RCC of the RRS.

Wherein the determining module is specifically configured to: determining an RCC as an RCC to which the RRS belongs according to one or more of the following information carried in a registration invitation message sent by one or more RCCs received by the receiving module: geographical location information of the RCC, communication bandwidth information between the RCC and the RRS, and communication delay information between the RCC and the RRS.

Further, the sending module is further configured to: after the RRS completes the registration to the RCC to which the RRS belongs, the discovery message is sent again;

the receiving module is further configured to: receiving a keep-alive confirmation message sent by a home RCC of the RRS, and receiving registration invitation messages sent by N other RCCs, wherein N is an integer greater than or equal to 1;

some embodiments of the present invention provide an application and an RRS management apparatus on an RRS, further comprising:

an obtaining module, configured to obtain, according to the keep-alive confirm message and the N registration invitation messages received by the receiving module, one or more of the following information of the RCC to which the RRS belongs and the other RCCs: geographical location information of the RCC, communication bandwidth information between the RCC and the RRS, and communication delay information between the RCC and the RRS.

Wherein, the registration request message is a broadcast message.

In the management method of the RRS provided in the foregoing embodiment of the present invention, the RRS can obtain the registration invitation message sent by one or more RCCs in the network by sending the discovery message, and then initiate registration after determining the RCC to which the rrc belongs according to the received registration invitation message. It can be seen that, in the above embodiment of the present invention, the RRS may not receive the registration invitation message of a single RCC point to point, but may receive the registration invitation message sent by one or more RCCs, so that any RRS in the network may automatically and flexibly select an RCC in the network to register, thereby implementing automatic and flexible networking between the RCC and the RRS.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

FIG. 1 is a schematic diagram of an NGFI-based C-RAN wireless network architecture;

fig. 2 is a schematic flow chart of a management method of an RRS on an RCC side according to an embodiment of the present invention;

fig. 3 is a schematic flow diagram of a management method of an RRS on an RRS side according to an embodiment of the present invention;

fig. 4 is a schematic diagram of a specific implementation structure of the RRS management method in an NGFI-based network architecture according to an embodiment of the present invention;

fig. 5 is a schematic diagram of a flow of the management method of the RRS in an RCC side in a specific application according to an embodiment of the present invention;

fig. 6 is a schematic diagram of a flow of an RRS side in a specific application of a management method of an RRS according to an embodiment of the present invention;

fig. 7 is a schematic flowchart of a message interaction between an RRS and an RCC in a specific application of the management method for an RRS according to an embodiment of the present invention;

fig. 8 is a schematic structural diagram of an application and an RRS management apparatus on an RCC according to an embodiment of the present invention;

fig. 9 is a schematic structural diagram of an application and an RRS management apparatus on an RRS according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Fig. 1 shows a schematic diagram of a C-RAN wireless network architecture based on a next generation front-end transport interface NGFI. As shown in fig. 1, the network architecture includes: a remote radio frequency system RRS101, a wireless cloud center RCC102, a next generation front end transmission interface NGFI103, and a back end transmission network 104.

The remote Radio frequency system RRS101 includes an antenna, an RRU105, and a Radio Aggregation Unit (Radio Aggregation Unit) 106(Radio Aggregation Unit) that is a part of a conventional BBU. As with the network architecture shown in fig. 1, RRS101 may be one or more. Corresponding to the deployment of the current network, the remote function should be deployed at the position of the current wireless station site, and the active area of the corresponding function is the coverage area of the current macro station and the coverage areas of the micro RRUs and the macro RRUs which are remotely deployed by taking the macro station as the center. In the figure, the RAU is a logic unit, the actual device form is related to the specific implementation scheme, and the RAU may be integrated with the original RRU to form a new RRU entity (for example, the integrated RRS shown in fig. 1) or may be independently designed as a hardware entity.

The wireless cloud center RCC102 includes the remaining functions of the traditional BBU except the RAU, the high-level management function, and the like, and since the functions of multiple carriers and multiple cells under multiple sites are centralized, a function pool is formed, and the active area of the centralized function unit includes the sum of areas covered by multiple remote function units under all the centralized function units. As shown in the network architecture of fig. 1, there may be one or more RCCs 102, multiple RCCs 102 may be deployed at a single physical site, and one or more RRSs 101 may be connected to the centralized functional unit. For example, in a traffic-intensive area, the RCC may be centrally placed in a macro station room, and the RRS is used for remote coverage, so as to provide capacity guarantee, the RCC and the RRS are directly driven by optical fiber or connected by using an existing access network pipeline, and the RRS may further save cable resources by cascading. Compared with a flat LTE network design, the baseband centralized unit is introduced, a high-level network element is not introduced, the form reconstruction between the BBU/RRU is carried out only on the basis of considering the introduction of the higher-level collaborative requirement in the future, and the flat network structure of the LTE is not influenced.

As shown in fig. 1, RRS101 and RCC102 are connected through NGFI103, which constitutes a front-end transport network portion of an NGFI-based C-RAN wireless network. The NGFI realizes the function of connecting the RRS and the RCC, that is, the NGFI can also be understood as an interface between the BBU and the RRU after the repartitioning is completed. The NGFI may further support a future 5G air interface technology in addition to the existing 4G LTE technology, and may also be an evolvable interface considering the evolution process to the Cloud RAN and the trend of the transmission network to evolve to a higher bandwidth and a lower transmission delay. The load of the forward data can be transmitted by adopting the Ethernet, thereby not only fully utilizing the existing rich Ethernet basic network to improve the network deployment speed, but also utilizing the characteristics of statistical multiplexing, flexible routing and the like of packet transmission to improve the transmission efficiency and flexibly network.

For the wireless network architecture based on the NGFI, the interface design index definition of the NGFI needs to consider the new requirements of BBU/RRU function reconstruction on bandwidth, transmission delay, synchronization and the like. In the wireless network architecture based on the NGFI, a point-to-point front end transmission network defined by a traditional CPRI interface is redefined as a multipoint-to-multipoint front end transmission network based on the NGFI based on a packet switching protocol. The interface management functions of the CPRI between the original BBU and the RRU, such as RRU version management in the interface management of the original CPRI, delay measurement and configuration in the interface management of the original CPRI, RRU parameter query in the interface management of the original CPRI, and the like, need to be redefined and managed in the NGFI-based wireless network.

Compared with the traditional CPRI interface, the NGFI can greatly reduce the bandwidth of the transmission interface of the RCC and the RRS, is beneficial to the realization of a multi-antenna technology on the basis of keeping the RCC/RRS separation structure, and is easy for RCC centralized deployment and realization of a wireless network cooperative function. In the forward end transmission defined as a multipoint-to-multipoint wireless network based on the NGFI, one-to-many and many-to-one flexible networking between the RRS and the BCC is very important for meeting the development requirements of the future wireless network architecture, and realizing the network reliability, the flexibility of installation and construction, operation and maintenance management, and the like. In order to realize automatic and flexible networking between the RCC and the RRS, the embodiment of the invention provides a technical scheme for RRS management. The technical scheme of the management of the RRS provided by the embodiment of the invention can be applied to the NGFI-based network architecture shown in figure 1, and can be specifically realized in the interaction process between the RCC and the RRS.

In order to more clearly describe the interaction process between the RCC and the RRS implemented by the technical solution for managing the RRS provided by the embodiment of the present invention, the flow of the interaction process between the RCC and the RRS implemented by the technical solution for managing the RRS provided by the embodiment of the present invention on the RCC side and the flow on the RRS side will be described below respectively.

Embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

Fig. 2 is a schematic flowchart of a method for managing a remote radio frequency system RRS at an RCC side according to an embodiment of the present invention, where the flowchart may be applied to the RCC102 in the network architecture shown in fig. 1 to implement management of any one RRS101 in the network architecture shown in fig. 1, and the flowchart may be specifically executed by software or a combination of software and hardware integrated on the RCC 102.

For convenience of description, the following will describe a flow of the management method of the RRS implemented on the RCC side provided by the embodiment of the present invention by taking one RCC as an example. It should be understood that the management flow of RRS implemented on the RCC side described below is applicable to any one RCC in the NGFI-based network architecture as shown in fig. 1.

As shown in fig. 2, the process includes the following steps:

step 201: and the RCC receives a discovery message sent by the RRS, wherein the discovery message carries the identification of the RRS.

Step 202: and the RCC sends a registration invitation message to the RRS according to the identification of the RRS carried in the discovery message.

Step 203: and the RCC receives a registration request message sent by the RRS, wherein the registration request message carries the identifier of the RCC to which the RRS belongs.

Step 204: and if the RCC judges that the attributive RCC of the RRS is the RCC according to the attributive RCC identification of the RRS carried in the registration request message, the RCC registers the RRS.

The discovery message sent by the RRS and received by the RCC in step 201 may be a broadcast message sent by the RRS.

Specifically, the discovery message may be a broadcast message sent by the RRS to each RCC in the network when the RRS initially accesses the network, so as to notify the RCCs in the network area where the RRS is located of the RRS; or, the discovery message may also be a broadcast message sent by the RRS that has established a normal communication link with the RCC to each RCC in the network according to a set period, so as to confirm that the link between the RRS and the RCC is normal; or, the discovery message may also be a broadcast message sent by the RRS that has established a normal communication link with the RCC to each RCC in the network when the RRS needs to re-measure the relationship between the RRS and each RCC in the network, so as to obtain the measurement information between the RRS and the RCC in the network; alternatively, the discovery message may be a broadcast message sent by the RRS that loses normal communication service with the RCC (e.g., the RCC that established a communication link with the RRS exits service due to a failure, etc.) to each RCC in the network for re-registration with a new RCC, etc.

The discovery message sent by the RRS may carry the identifier of the RRS, and may further carry basic configuration information such as the configuration capability of the RRS. Specifically, the identification of an RRS may be an ID number of the RRS (for example, the identification may be a MAC (Media Access Control) address of the RRS or other numbers uniquely identifying the RRS).

Further, the RCC sends a registration invitation message to the RRS according to the identification of the RRS carried in the discovery message sent by the RRS received in step 201, specifically, the registration invitation message may be sent to the RRS corresponding to each discovery message for each received discovery message, or the registration invitation message may be sent to the corresponding RRS according to a result of judgment or selection after judging or selecting the received discovery message according to a preset criterion.

In some preferred embodiments of the present invention, after receiving the discovery message in step 201, the RCC may determine, according to the identifier of the RRS carried in the received discovery message, whether the RRS corresponding to the discovery message is registered on the RCC, and if it is determined that the RRS is not registered on the RCC, send a registration invitation message to the RRS.

In some embodiments of the present invention, the RCC may query, according to the identifier of the RRS carried in the received discovery message, the identifier of an RRS marked as registered or pre-registered to the RCC in the RCC, and if the identifier of an RRS carried in the discovery message is not queried in the identifiers of the RRS marked as registered and pre-registered to the RCC, the RCC determines that the RRS indicated by the identifier of the RRS is not registered in the RCC.

Further, if the RCC determines that the RRS is not registered on the RCC, the RCC may store the identification of the RRS carried in the discovery message after sending the registration invitation message to the RRS, and mark the RRS as pre-registered on the RCC.

The RCC may store the identifier of the RRS marked as registered or pre-registered to the RCC, and may correspondingly store and manage the marked registration state of each RRS for the stored identifier of each RRS. Furthermore, the RCC may further store the configuration information, such as the configuration capability of each RRS, corresponding to the identifier of each RRS, which is not limited in this invention.

Specifically, the marked registration status of an RRS may include a registered status marking that the RRS is registered to the RCC and a pre-registered status marking that the RRS is pre-registered to the RCC, where the registered status indicates that the RCC has registered the RRS, and the RCC is responsible for providing services and management to the RRS, and the pre-registered status indicates that the RCC needs to further confirm whether to register the RRS.

For example, in some preferred embodiments of the present invention, the RCC may store, in a list manner, the identification of the RRS carried in the received discovery message and the registration status marked by the RRS corresponding to the identification of each RRS in a local database of the RCC, and perform corresponding update or add/delete operations on the stored list each time a new discovery message is received or when one RRS is marked as pre-registered or registered on the RCC, thereby implementing management of the identification of the RRS and the registration status of the RRS stored on the RCC. For example, for an RRS of an initial access network, the RCC may add, after receiving a discovery message sent by the RRS, an identification of the RRS and a record of a pre-registration status marked for the RRS in a list; for another example, after receiving the discovery message sent by the RRS, the identifier of the RRS and the record of the pre-registration status marked by the RRS are queried in the list, the RCC may determine that the RRS is registered on the RCC, and after the RCC registers the RRS, the pre-registration status marked by the RRS recorded in the list may be changed to the registered status.

In some preferred embodiments of the present invention, the RCC may determine whether the RRS is registered on the RCC by querying a local database for a list of identifications of RRS marked as registered or pre-registered on the RCC according to the identification of the RRS carried in the received discovery message. If the RCC does not inquire the identification of the RRS carried in the discovery message in the list, the RCC may determine that the RRS is not registered on the RCC, and if the identification of the RRS carried in the discovery message is inquired and the RRS corresponding to the identification is marked as registered on the RCC, the RCC may determine that the RRS is registered on the RCC.

Further, in some embodiments of the present invention, if the RCC determines that the RRS is registered on the RCC according to the identifier of the RRS carried in the discovery message, the RCC may send a keep-alive acknowledgement message to the RRS, where the keep-alive acknowledgement message is used to notify that the RRS is registered on the RCC.

For example, in the case that the discovery message sent by the RRS received by the RCC is not the discovery message sent by the first broadcast when the RRS initially accesses the network, the RCC may determine that the RRS is registered on the RCC, for example, the discovery message sent by the rrc may be broadcast according to a set period by the RRS registered on the RCC in order to confirm that the communication link between the rrc and the RCC is normal, or the discovery message received by the RCC may also be the discovery message sent by the RRS broadcast due to event trigger, for example, the RRS is triggered by the condition that it needs to re-measure the relationship between the RRS and each RCC in the network or the RRS does not receive the keep-alive confirmation message of the RCC within a set time length.

Wherein the keep-alive acknowledgement message sent by the RCC to the RRS is mainly used to inform the RRS that it is registered on the RCC, and further inform the RRS that a communication link exists between the RRS and the RCC. Specifically, the keep-alive acknowledgement message may carry some basic keep-alive information, such as some basic measurement information of the determined communication link between the RRS and the RCC, so as to notify the RRS that the link between the RRS and the RCC is not broken, and the like.

Further, in some preferred embodiments of the present invention, after receiving the discovery message in step 201, the RCC may determine whether the RRS is registered on the RCC according to the identifier of the RRS carried in the discovery message, determine whether the RCC can serve as a home RCC of the RRS, and send a registration invitation message to the RRS if it is determined that the RRS is not registered on the RCC and the RCC can serve as a home RCC of the RRS.

Wherein an RRS of an access network should be registered with (i.e. belong to) an RCC at any time, the home RCC of an RRS can be understood as the access master serving RCC of the RRS. Specifically, the access primary service RCC of an RRS should be able to perform operations such as processing of baseband signals associated with the RRS, establishing an NGFI-based data communication link with the RRS, and managing, maintaining configuration, or automated searching of the RRS. As for the RCC, whether an RCC can be a home RCC of an RRS can be understood as whether the RCC can be an access primary service RCC of the RRS, that is, whether the RCC can complete processing of baseband signals related to the RRS, establish a data communication link based on NGFI with the RRS, and perform operations such as management, maintenance configuration, or automatic search on the RRS.

Specifically, the RCC may determine whether the RCC can serve as the home RCC of the RRS by any one of the following manners, and it should be noted that, in the management method of the RRS provided in the embodiment of the present invention, a specific algorithm for determining whether the RCC can serve as the home RCC of the RRS is not limited to the following manners:

in the method 1, if the RCC determines that the RCC can be matched with the RRS according to the configuration information of the RRS carried in the discovery message received in step 201, the RCC determines that the RCC can be used as a home RCC of the RRS. The matching of the RCC and the RRS may mean that the RCC and the RRS use the same communication protocol.

In the method 2, if the RCC determines that the RRS can be accepted according to the processing capability of the RCC, the RCC determines that the RCC can be a home RCC of the RRS. The processing capability of the RCC may include the number of RRSs that the RCC can support, the communication bandwidth, and the like.

Mode 3, if the RCC determines that the RCC can match the RRS according to the configuration information of the RRS carried in the discovery message received in step 201, and determines that the RRS can be accepted according to the processing capability of the RCC, the RCC determines that the RCC can serve as the home RCC of the RRS.

For example, in some preferred embodiments of the present invention, the RCC may specifically determine, by combining the configuration information of the RRS carried in the discovery message and the remaining processing capability of the RCC itself, whether to accept the RRS for processing, and if it is determined that the RRS can be accepted, determine that the RCC can serve as a home RCC of the RRS, so as to send a registration invitation message to the RRS. The RCC may determine whether to accept an RRS according to its processing capability, or determine whether the RCC has the capability of accessing the primary service RCC as the RRS according to its processing capability.

Specifically, the RCC may carry an identifier of the RCC, such as an ID number of the RCC, in the registration invitation message sent by the RCC to the RRS in step 202; the registration invitation message may further carry the geographical location information of the RCC. Preferably, the registration invitation message may further carry some basic information or link measurement information of data communication between the RCC and the RRS, such as communication bandwidth information between the RCC and the RRS, communication delay information between the RCC and the RRS, and the like, so that the RRS receiving the registration invitation message can further determine its own home RCC according to the one or more information carried in the registration invitation message.

In some embodiments of the present invention, after sending the registration invite message to the RRS, the RCC may further receive a registration request message sent by the RRS, where the registration request message carries an identifier of a home RCC of the RRS. Furthermore, when the RCC determines that the RRS's home RCC is the RCC according to the identifier of the RRS' home RCC carried in the registration request message, the RCC may register the RRS.

For an RRS, after receiving a registration invitation message sent by one or more RCCs, a home RCC of the RRS, that is, an access primary serving RCC of the RRS, may be determined according to the received registration invitation message. Specifically, after receiving the registration invitation message of one or more RCCs, the RRS determines, according to the relevant information of the RCCs carried in the received registration invitation message, one RCC as its own home RCC according to a preset criterion.

Specifically, after receiving the registration request message sent by the RRS, the RCC may determine whether the home RCC of the RRS is the RCC according to the identifier of the home RCC of the RRS carried in the registration request message. For example, in some embodiments of the present invention, the RCC may compare the identifier of the home RCC of the RRS carried in the registration request message with the identifier of the RCC itself, and if the identifier of the home RCC of the RRS is the same as the identifier of the RCC, it is determined that the home RCC of the RRS is the RCC, and if the identifier of the home RCC of the RRS is different from the identifier of the RCC, it is determined that the home RCC of the RRS is not the RCC.

Further, in some embodiments of the present invention, if the RCC determines that the home RCC of the RRS is the RCC, the registration of the RRS by the RCC may include storing configuration information of the RRS, establishing a link with the RRS, marking the RRS as being registered on the RCC, and further returning a registration confirmation message to the RRS, so that the RRS is served as the home RCC of the RRS to provide subsequent data communication services to the RRS, that is, the RRS may uniquely send data (air interface wireless data) to the RCC for processing, and implement related management and maintenance of the RRS.

In some embodiments of the present invention, if the RCC determines that the home RCC of the RRS is not the RCC, the RCC may delete the flag that the RRS pre-registered to the RCC and save the affiliation between the identity of the RRS and the identity of the home RCC of the RRS.

Specifically, the registration request message sent by the RRS may be a broadcast message, so that the RCCs in the network can receive the registration request message. For the home RCC of the RRS, the RRS can be registered according to the registration request message, so as to provide subsequent data communication services for the RRS, and for other RCCs in the network that are not the home RCC of the RRS, the registration relationship between the RRS and the home RCC thereof can be saved, so that for the entire network area, the complete home relationship between each RRS in the area and the home RCC thereof can be established, and the home relationship between the RRS and the RCC in the area can be automatically updated and maintained.

For example, for an RRS initially accessing a network, after receiving a registration invitation message sent by one or more RCCs, determining a home RCC of the RRS, that is, after the RRS accesses a primary serving RCC, broadcasting a registration request message of an identifier of the home RCC of the RRS; for the RRS that has performed registration, after receiving a registration invitation message sent by one or more RCCs, the RRS re-determines the RCC to which the RRS belongs after receiving a registration request message carrying an identifier of the RCC to which the RRS re-determines, where the registration request message is broadcast, where the registration request message is sent after the RRS fails to receive a keep-alive confirmation message sent by its RCC to the RRS within a set time period after a broadcast message sent by the RRS according to a set period, or may be when the RRS re-measures a relationship between the RRS and each RCC in a network, or may be when the RCC to which the RRS originally belongs cannot provide a service to the RRS.

In summary, in the management method for an RRS according to the embodiments of the present invention, the RCC may send a registration invitation message to the RRS according to the received discovery message, and may further receive a registration request message sent by the RRS, so as to determine whether to register the RRS. It can be seen that, in the embodiment of the present invention, the RCC does not send the registration invitation message to a single RRS point to point, but can automatically discover one or more RRSs in the network, flexibly send the registration invitation message to one or more RRSs in the network, and further determine whether to register the RRS according to the registration request message fed back by the RRS, so that any RCC in the network can flexibly establish an affiliation with one or more RRSs in the network, thereby implementing automatic and flexible networking between the RCC and the RRS.

Through the above process, although the RRS is only affiliated to one RCC at any time, that is, only registered to one RCC, compared with the conventional CPRI point-to-point management scheme, in the management method of the RRS provided in the embodiments of the present invention, in the network discovery process, the RRS notifies the existence of the RCC in the area through a broadcast method, and in the registration process, the RRS also sends a registration request message through a broadcast method, so that each RCC in the network can automatically discover the RRS and receive the registration request message of the RRS, and thus, through the above automatic network discovery and flexible registration method, the affiliation relationship between the RCC and the RRS can be flexibly established and maintained in a multipoint-to-multipoint manner, thereby realizing automatic and flexible networking between the RCC and the RRS.

It can be seen that, in the management method of the RRS provided in the embodiment of the present invention, the affiliation relationship between the RCC and the RRS is a relatively flexible relationship, that is, for any RCC in the network, all discovery messages sent by RRS broadcast in the network and registration request messages broadcast by the RRS can be received, so as to implement establishment or migration of the affiliation relationship between the RCC and the RRS, and any RCC in the network can also store the relationship between the RRS that does not affiliate and is not processed by the RCC and the corresponding affiliation RCC, so as to establish and maintain the complete affiliation relationship between the RRS and the RCC in the entire network area. For any RRS in the network, correspondingly, the discovery message is broadcast and sent to all the RCCs in the network, the registration invitation message returned by one or more RCCs is obtained, and then one RCC is determined as the current home RCC, and the registration request message is broadcast and sent to all the RCCs in the network, so that the establishment or migration of the home relationship between the RCCs and the RRS is realized, and the RCC can establish and maintain the home relationship between the RRS and the RCC in the whole network area.

The RRS management method provided by the embodiment of the invention can realize automatic and flexible establishment or migration of the affiliation relationship between the RCC and the RRS, thereby better realizing load balance when the network traffic is larger, further centralizing processing when the network traffic is lower, reducing equipment power consumption and better realizing statistical multiplexing of processing resources on the RCC in the network. For the case that any RCC in the network fails, the management method of the RRS provided by the embodiment of the present invention can also enable the RRS belonging to the RCC to re-register to other RCCs in the network through the above procedure to keep working, that is, the RRS belonging to the RCC can be distributed and migrated to other RCCs for management, thereby avoiding the influence on the whole network work due to the single point failure of the RCC, and improving the network reliability. In addition, through the flexible establishment or migration of the affiliation between the CC and the RRS, the RCC and the RRS can be flexibly and conveniently connected and networked based on the Ethernet, and the automatic registration and installation of the RRS in the networking process can be facilitated.

Based on the same technical concept, fig. 3 shows a schematic flow diagram of the management method of the RRS on the RRS side according to the embodiment of the present invention, where the flow may be applied to any one of the RRSs 101 in the network architecture shown in fig. 1, and the flow may be specifically executed by software or a combination of software and hardware integrated on the RRS 101.

For convenience of description, the following will describe a flow of the management method of the RRS implemented on the RRS side according to an embodiment of the present invention by taking one RRS as an example. It should be understood that the management flow of RRS implemented on the RRS side described below applies to any one RRS in the NGFI-based network architecture as shown in fig. 1.

As shown in fig. 3, the process includes the following steps:

step 301: and the RRS sends a discovery message to the RCC, wherein the discovery message carries the identification of the RRS.

Step 302: and the RRS receives registration invitation messages sent by one or more RCCs, wherein the registration invitation message sent by one RCC is sent to the RRS by the RCC according to the identification of the RRS carried in the discovery message.

Step 303: and the RRS determines the home RCC of the RRS according to the received registration invitation message.

Step 304: and the RRS sends a registration request message, wherein the registration request message carries the identifier of the attributive RCC determined by the RRS.

Specifically, the discovery message sent by the RRS may further include configuration information of the RRS.

For the case that the RRS sends the discovery message and the specific process that the RCC side receives the discovery message sent by the RRS and sends the registration invitation message according to the received discovery message, reference may be made to the specific process that the RCC side sends the registration invitation message and the description in the registration invitation message sent by the RCC, which are not described herein again.

Specifically, for the RRS, a set time length for waiting for a registration invitation message sent by the RCC may be preset, so that timing may be started after the RRS sends a discovery message, and then the registration invitation message sent by the RCC in the network within the set time length may be received and cached, and if a valid registration invitation message is not received within the set time length, for example, the registration invitation message is not received or a registration invitation message carrying an RCC identifier is not received, the RRS may be triggered to re-broadcast and send the discovery message.

Specifically, a registration invitation message sent by an RCC to the RRS may carry one or more of the following information: geographical location information of the RCC, communication bandwidth information between the RCC and the RRS, and communication delay information between the RCC and the RRS. Furthermore, after the RRS receives the registration invitation message sent by the one or more RCCs, the RRS may determine, according to one or more of the following information carried in the registration invitation message sent by the one or more RCCs, that an RCC is the home RCC of the RRS: geographical location information of the RCC, communication bandwidth information between the RCC and the RRS, and communication delay information between the RCC and the RRS.

It should be noted that, in the management method of the RRS provided in the embodiment of the present invention, a specific algorithm for the RRS to determine the home RCC of the RRS (i.e., determine the access RCC of the RRS) is not specifically limited.

Specifically, the registration request message sent by the RRS may be a broadcast message, so that the RCCs in the network can receive the registration request message. Corresponding to the management method of the RRS implemented on the RCC side provided in the foregoing embodiment, for the home RCC of the RRS, the RRS can be registered on the RCC according to the registration request message, and then an access service is provided for the RRS, and for other RCCs in the network that are not the home RCC of the RRS, the registration relationship between the RRS and the home RCC of the RRS can be saved, so that for the entire network area, a complete home relationship between each RRS in the area and the home RCC thereof can be established, and the home relationship between the RRS and the RCC in the area can be automatically updated and maintained.

Further, after the RRS sends the registration request message, it may also receive a registration confirmation message sent by the home RCC of the RRS after receiving the registration request message.

Specifically, a set time length for waiting for a registration confirmation message may also be preset on the RRS, if a registration confirmation message sent by the home RCC of the RRS after receiving the registration request message is received within the set time length, the RRS ends the registration process and enters a normal communication state, and if a registration confirmation message sent by the home RCC of the RRS after receiving the registration request message is not received within the set time length, the RRS may reinitiate registration, that is, may send a discovery message to the RCC in the network again, and perform the registration process again.

Further, after the RRS completes registration with the RCC to which the RRS belongs, the RRS may send the discovery message again, specifically, for example, the discovery message may be sent according to a set period, so that the RRS that completes registration may receive a keep-alive confirmation message sent by the RCC to which the RRS belongs and receive registration invitation messages sent by N other RCCs in the network, where N is an integer greater than or equal to 1; the RRS can obtain one or more of the following information of the home RCC of the RRS and other RCCs in the network according to the received keep-alive confirm message and the N registration invite messages: geographical location information of the RCC, communication bandwidth information between the RCC and the RRS, and communication delay information between the RCC and the RRS. Further, the RRS may determine whether to re-establish a relationship between the RRS and each RCC in the network, whether to re-select an RCC for access, and the like according to the obtained information.

In summary, in the management method of the RRS implemented at the RRS side according to the foregoing embodiment of the present invention, the RRS sends the discovery message in a broadcast manner, so that the registration invitation message sent by one or more RCCs in the network can be acquired, and then the registration can be initiated after determining the RCC to which the rrc belongs according to the received registration invitation message. It can be seen that, in the above embodiment of the present invention, the RRS does not receive the registration invitation message of a single RCC point to point, but can receive the registration invitation messages sent by one or more RCCs, and can flexibly determine one RCC from the RCCs sending the registration invitation message to register, so that any RRS in the network can automatically and flexibly determine one RCC from multiple RCCs in the network to register, thereby implementing automatic and flexible networking between the RCCs and the RRS.

Through the above description, it can be seen that the management method of the RRS provided by the embodiment of the present invention can be used in defining the interaction process of the RCC to the RRS in the NGFI-based network architecture, so as to implement automatic discovery and flexible management between the RCC and the RRS. It should be understood that the above-described method embodiment of the RCC side and the method embodiment of the RRS side both correspond to an interaction process between the RCC and the RRS to which the technical solution of management of the RRS provided by the embodiment of the present invention is applied, and the foregoing method embodiments are different only in terms of execution subject, that is, in terms of a flow of a method for describing management of the RRS provided by the embodiment of the present invention.

It should be further understood that the management method of the RRS provided by the embodiment of the present invention is not specifically limited to the messages interacted during the interaction between the RRS and the RCC, nor is it specifically limited to the specific algorithm for the RCC to determine whether the rrc can serve as the home RCC of the RRS (i.e., whether to accept the RRS) and the RRS to determine the RCC to which the RRS belongs (i.e., determine the RCC to which the RRS accesses).

The management method of the RRS provided in the embodiment of the present invention is based on network discovery and remote management, the RRS is defined as an IP-based functional entity, and when the management method is specifically implemented, a corresponding network management module may be designed in the RCC to perform management control on the RRS through a network, and a corresponding controlled module may be further designed in the RRS to receive management.

It can be seen that the core idea of the management method of the RRS provided in the embodiment of the present invention is to define two key management modules or devices, namely, a network management module in the RCC and a controlled module in the RRS based on network connection, and implement an automatic and flexible home (registration) relationship between the RCC and the RRS by a method of network automatic discovery and registration.

Fig. 4 shows an example of a specific implementation of the RRS management method in an NGFI-based network architecture according to an embodiment of the present invention.

As shown in fig. 4, in the RCC401, a protocol stack high layer function 402, a user level signal processing (physical layer) 403 and a network management module 404 are included, and in the RRS405, a controlled module 406, a front end processing function 407 and an RRU408 are included, and the RRS management method provided by the embodiment of the present invention can be implemented by the network management module 404 in the RCC401, the controlled module 406 in the RRS405 and an ethernet-based data switching network 409.

The network management module 404 in the RCC401 may perform the specific process of the foregoing embodiment of the RCC side method, the controlled module 406 in the RRS405 may perform the specific process of the foregoing embodiment of the RRS side method, and the network management module 404 in the RCC401 and the controlled module 406 in the RRS405 interact with each other through the data exchange network 409 of the ethernet.

For example, the specific interaction process may include: the RRS405 sends a broadcast discovery message through the controlled module 406 to notify the network management module 404 in the RCC401 in the network of its existence, so as to indicate that a new RRS joins the network or that the RRS loses the service of the original home RCC, and needs to establish a new home relationship with one RCC401 in the network; each RCC401 in the network receives the discovery message and determines whether the RRS405 can be managed by itself, and if the determination capability is allowable, the network management module 404 broadcasts registration invitation information to the controlled module 406 corresponding to the RRS 405; the controlled module 406 of the RRS405 determines to select the RCC to which the target belongs according to the received multiple pieces of registration invitation information, and broadcasts and sends registration request information; after receiving the broadcast registration information, the network management module 404 of the RCC401 serving as the home RCC establishes a home relationship with the RRS405, and returns registration confirmation information; the other RCCs 401 in the network do not respond to the registration request message of the RRS405, and may wait for the RRS405 to initiate a new round of broadcast messages before responding.

It should be noted that in the technical solution of management of RRS provided in the embodiment of the present invention, the network management module on the RCC for implementing management of RRS may include, but is not limited to, a network discovery function and a network function such as a multi-dependency relationship.

In order to more clearly illustrate the management method of the RRS provided by the embodiment of the present invention, a case where the management method of the RRS provided by the embodiment of the present invention is applied in a specific application will be described as an example.

Embodiment 1, the management method of the RRS provided by the embodiment of the present invention, in a specific application, includes an RRS automatic discovery process at the RCC side and an RRS registration process at the RRS side.

Fig. 5 shows an example of an RRS automatic discovery process of the RCC side in a specific application of the management method of the RRS provided by the embodiment of the present invention.

As shown in fig. 5, the RCC may first read data through the network port (step 501); further buffering the RRS signaling data (step 502); judging whether the message is an RRS broadcast message (namely a discovery message), if not, re-reading the data (namely returning to the step 501); if yes, reading the RRS broadcast message in the cache, and further reading the ID identification list of the RRS and the registration state of the RRS stored in the local database (step 503 and step 504); and then judging whether the ID identification of the RRS in the RRS broadcast message exists in a list stored in a local database.

If the ID of the RRS in the RRS broadcast message is not in the list stored in the local database, further determining whether the RCC can be used as the home RCC of the RRS, i.e. accessing the RCC, if not, re-reading the data (i.e. returning to step 501), if so, storing the ID of the RRS and marking the ID as a pre-registration state (step 505), and further sending a registration invitation message carrying the ID of the RCC to the RRS (step 506).

If the ID of the RRS in the RRS broadcast message is determined to be in the list stored in the local database, further determining whether the RRS is marked in a pre-registration state, and determining whether the broadcast message is a registration request message, if the RRS is determined to be marked in a registered state or the broadcast message is not a registration request message, the RCC may send a keep-alive confirm message to the RRS (step 507), if the RRS is determined to be marked in a pre-registration state and the broadcast message is a registration request message, further determining whether the ID of the home RCC carried in the registration request message is equal to the ID of the local RCC, i.e., is the RCC, if so, updating the registration state of the RRS to a registered state (step 508), establishing a communication link with the RRS, and sending a registration confirm message for successful registration to the RRS (step 509), the RRS can uniquely send data (air interface wireless data) to the RCC for processing in subsequent data communications. If not, deleting the pre-registration information corresponding to the ID identification of the RRS stored locally, and maintaining the RRS attribution relation table of the adjacent RCC (step 510).

Accordingly, fig. 6 shows an example of an RRS registration flow on the RRS side in a specific application of the management method for an RRS provided by the embodiment of the present invention.

As shown in fig. 6, after accessing the ethernet, the RRS first sends an RRS broadcast message (step 601); further, a timer is started to time (step 602), and before the timer expires, the registration invitation messages sent by each RCC in the network are received and buffered (step 603); after the timer expires, determining whether a valid registration invitation message is received; if not, resending the RRS broadcast message (i.e. returning to step 601); if yes, determining an RCC as a home RCC from the received registration invitation message, i.e. an access RCC, and determining an ID of the RCC (step 604); further, a registration request message may be sent in a broadcast manner, where the registration request message carries an ID identifier of the RCC (step 605); further starting a timer to wait for the registration confirmation message of successful registration fed back by the RCC (step 606); judging whether a valid registration confirmation message is received or not when the timer stops; if not, resending the RRS broadcast message (i.e. returning to step 601); if yes, the registration process is ended, and the RRS enters a normal communication state.

It can be seen that the above-mentioned registration process example of the RRS shown in fig. 6 corresponds to the discovery process example of the RRS on the RCC side shown in fig. 5, and in order to more clearly express the automatic discovery and registration of the RRS implemented in a specific application by the management method of the RRS provided by the embodiment of the present invention, fig. 7 shows an example of a message interaction process between the RRS and the RCC.

As shown in fig. 7, the message interaction process between the RRS and the RCC includes: RRS broadcasts and sends a discovery message to RCC (step 701); the RCC determines whether it can act as a home RCC for the RRS (step 702); after determining that the RCC can be the home RCC of the RRS, the RCC returns a registration invite message to the RRS (step 703); the RRS arbitrates to select the RCC as the home RCC (step 704); RRS broadcasts and sends a registration request message (step 705); after establishing a data link with the RRS, the RCC returns a registration confirmation message of successful registration to the RRS (step 706); and the RRS can perform subsequent normal data communication procedures with the RCC.

The discovery process of the RRS implemented on the RCC side may be implemented by the network management module 404 in the RCC401 shown in fig. 4, and the registration process of the RRS implemented on the RRS side may be implemented by the controlled module 406 in the RRS405 shown in fig. 4.

Embodiment 2 and the automatic fault protection process of the RRS in the specific application of the management method of the RRS provided by the embodiment of the present invention.

Specifically, for automatic fault protection of the RRS in a specific application, the automatic fault protection may be implemented by a procedure of reinitiating registration from the RRS to the RCC when the RRS and the RCC lose normal communication messages or the RCC needs to perform fault protection on the RRS and the RCC due to a fault, and the procedure of reinitiating registration from the RRS to the RCC may be the same as the procedure of automatic discovery and registration of the RRS in embodiment 1.

Therefore, except for the situation that the RRS is triggered to send the discovery message, the automatic fault protection for the RRS may be specifically implemented by re-executing the automatic discovery and registration process of the RRS as described in the foregoing embodiment 1, that is, implemented by the processing flow of the management method of the RRS provided by the embodiment of the present invention shown in fig. 5 on the RCC side in a specific application, the processing flow of the management method of the RRS provided by the embodiment of the present invention shown in fig. 6 on the RRS side in a specific application, and the normal message interaction flow between the RCC and the RRS in the management method of the RRS provided by the embodiment of the present invention shown in fig. 7, so as to ensure that the RCC in the network does not generate a fatal risk to the network-wide system after a single point of fault occurs.

For example, after losing the keep-alive confirm message of the RCC, that is, the RRS does not receive the keep-alive confirm message sent by the RCC within the set duration, the RRS may initiate registration with the RCC in the network again, and re-establish a new affiliation relationship through the flows shown in fig. 5, fig. 6, and fig. 7, so that the other RCCs in the network implement the function of the RCC to which the RRS originally belongs.

Based on the same technical concept, the embodiment of the present invention further provides an RRS management apparatus applied to an RCC, which may execute the foregoing management method embodiment of an RRS described in the RCC side, and the apparatus may be implemented by software integrated on the RCC or a combination of software and hardware, such as the network management module 404 in the RCC401 shown in fig. 4.

Fig. 8 illustrates an RRS management apparatus on an application and RCC according to an embodiment of the present invention, and as shown in fig. 8, the apparatus includes:

a receiving module 801, configured to receive a discovery message sent by an RRS, where the discovery message carries an identifier of the RRS; and the registration request message is used for receiving the registration request message sent by the RRS, and the registration request message carries the identifier of the home RCC of the RRS;

a sending module 802, configured to send a registration invitation message to the RRS according to the identifier of the RRS carried in the discovery message received by the receiving module 801;

a determining module 803, configured to determine whether the RRS belongs to the RCC according to the identifier of the RRS belonging to the RCC carried in the registration request message received by the receiving module 801;

a registering module 804, configured to register the RRS when the determining module 803 determines that the RCC to which the RRS belongs is the RCC.

The sending module 802 may be specifically configured to:

if the RRS is judged not to be registered on the RCC according to the identification of the RRS carried in the discovery message received by the receiving module 801, a registration invitation message is sent to the RRS; or

If the RRS is determined not to be registered to the RCC and the RCC can be determined to be the home RCC of the RRS according to the identifier of the RRS carried in the discovery message received by the receiving module 801, a registration invitation message is sent to the RRS.

Further, the sending module 802 may be specifically configured to: inquiring the identification of the RRS marked as registered or pre-registered on the RCC in the RCC according to the identification of the RRS carried in the discovery message; if the identification of the RRS is not inquired in the identifications of the RRS marked as registered and pre-registered to the RCC, judging that the RRS is not registered to the RCC.

Some embodiments of the present invention provide an application and RRS management apparatus on RCC, further including: a saving module 805, configured to, after the sending module 802 sends a registration invitation message to an RRS, save the identifier of the RRS carried in the discovery message, and mark the RRS as pre-registered on the RCC.

Further, the sending module 802 may be specifically configured to: if the RCC is determined to be matched with the RRS according to the configuration information of the RRS carried in the discovery message, judging that the RCC can be used as a home RCC of the RRS; or if the RRS can be accepted according to the processing capacity of the RCC, judging that the RCC can be used as the home RCC of the RRS; or if it is determined that the RCC is matched with the RRS according to the configuration information of the RRS carried in the discovery message and it is determined that the RRS can be accepted according to the processing capability of the RCC, determining that the RCC can be used as the home RCC of the RRS.

The registration module 804 is specifically configured to: when the determining module 803 determines that the RRS's home RCC is the RCC according to the identifier of the RRS' home RCC carried in the registration request message, the configuration information of the RRS is saved, a link with the RRS is established, and the RRS is marked as being registered on the RCC.

Further, in the application and RRS management apparatus on the RCC provided in some embodiments of the present invention, a maintaining module 806 is further included, configured to delete the flag pre-registered by the RRS on the RCC when the determining module 803 determines that the home RCC of the RRS is not the RCC, and save an affiliation relationship between the identifier of the RRS and the identifier of the home RCC of the RRS.

Wherein, the registration request message is a broadcast message.

Specifically, the sending module 802 is further configured to: when the determining module 803 determines that the RRS is registered on the RCC, a keep-alive confirm message is sent to the RRS, where the keep-alive confirm message is used to notify that the RRS is registered on the RCC.

Further, as for the specific functions of each module in the application and RRS management device on the RCC and the related process of message processing provided in the embodiment of the present invention as shown in fig. 8, reference may be made to the foregoing management method embodiment of the RRS described on the RCC side, which will not be described again here.

Based on the same technical concept, the embodiment of the present invention further provides an RRS management apparatus applied to an RRS, which may perform the aforementioned management method embodiment of the RRS described in the RRS side, and the apparatus may be implemented by software integrated on the RRS or a combination of software and hardware, such as the controlled module 406 in the RRS405 shown in fig. 4.

Fig. 9 illustrates an RRS management apparatus on an application and an RRS according to an embodiment of the present invention, and as shown in fig. 9, the apparatus includes:

a sending module 901, configured to send a discovery message to an RCC, where the discovery message carries an identifier of the RRS; and the system is used for sending a registration request message, wherein the registration request message carries the identifier of the attributive RCC determined by the RRS;

a receiving module 902, configured to receive a registration invitation message sent by one or more RCCs, where a registration invitation message sent by an RCC is sent to an RRS by the RCC according to an identifier of the RRS carried in the discovery message;

a determining module 903, configured to determine, after the receiving module 902 receives the registration invitation message sent by the one or more RCCs, a home RCC of the RRS according to the received registration invitation message.

Wherein, the registration request message is a broadcast message.

The determining module 903 is specifically configured to: determining an RCC as a home RCC of the RRS according to one or more of the following information carried in a registration invitation message sent by one or more RCCs received by the receiving module 902: geographical location information of the RCC, communication bandwidth information between the RCC and the RRS, and communication delay information between the RCC and the RRS.

Further, the sending module 901 is further configured to send the discovery message again after the RRS completes registration with the RCC to which the RRS belongs;

further, the receiving module 902 is further configured to: receiving a keep-alive confirmation message sent by a home RCC of the RRS, and receiving registration invitation messages sent by N other RCCs, wherein N is an integer greater than or equal to 1.

Some preferred embodiments of the present invention provide an application and RRS management apparatus on an RRS, further comprising: an obtaining module, configured to obtain, according to the keep-alive confirm message and the N registration invitation messages received by the receiving module 902, one or more of the following information of the RCC to which the RRS belongs and the other RCCs: geographical location information of the RCC, communication bandwidth information between the RCC and the RRS, and communication delay information between the RCC and the RRS.

Further, as for the specific functions of each module in the application and RRS management device on the RRS and the related process of message processing provided in the embodiment of the present invention shown in fig. 9, reference may be made to the foregoing management method embodiment of the RRS described on the RRS side, which will not be described again here.

It should be appreciated that for a software implementation, the techniques may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The software codes may be stored in memory units and executed by processors. The memory unit may be implemented within the processor or external to the processor.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims

1. A method for managing a remote radio system RRS, the method comprising:

if the RCC judges that the RRS is not registered on the RCC according to the identification of the RRS carried in the discovery message and judges that the RCC can be used as a home RCC of the RRS, the RCC sends a registration invitation message to the RRS;

2. The method of claim 1, wherein if the RCC does not query the identity of the RRS among the identities of RRSs marked as registered and pre-registered to the RCC according to the identity of the RRS carried in the discovery message, the RCC determines that the RRS is not registered to the RCC;

3. The method of claim 1, wherein if the RCC determines that the RCC matches the RRS according to the configuration information of the RRS carried in the discovery message, the RCC determines that the RCC can serve as a home RCC for the RRS; or

4. The method of claim 1, wherein the RCC registering the RRS comprises:

the RCC saves the configuration information of the RRS, establishes a link with the RRS and marks the RRS as being registered on the RCC.

5. The method of claim 1, wherein if the RCC determines that the home RCC of the RRS is not the RCC according to the identifier of the home RCC of the RRS carried in the registration request message, further comprising:

6. The method according to any of claims 1 to 5, wherein the registration request message is a broadcast message.

7. The method according to any one of claims 1 to 5, wherein if the RCC determines that the RRS is registered on the RCC according to the identifier of the RRS carried in the discovery message, further comprising:

8. The method according to any one of claims 1 to 5, wherein the registration invitation message carries one or more of the following information: geographical location information of the RCC, communication bandwidth information between the RCC and the RRS, and communication delay information between the RCC and the RRS.

9. A management method of RRS is characterized in that the method comprises the following steps:

the RRS receives registration invitation messages sent by one or more RCCs, wherein the registration invitation message sent by one RCC is sent to the RRS when the RCC judges that the RRS is not registered on the RCC and judges that the RCC can be used as a home RCC of the RRS according to the identification of the RRS carried in the discovery message;

10. The method of claim 9, wherein the RRS determining the home RCC of the RRS according to the received registration invitation message comprises:

the RRS determines that one RCC is taken as the home RCC of the RRS according to one or more of the following information carried in the received registration invitation message sent by one or more RCCs: geographical location information of the RCC, communication bandwidth information between the RCC and the RRS, and communication delay information between the RCC and the RRS.

11. The method of claim 9 or 10, wherein after the registration of the RRS with the RCC to which the RRS belongs is completed, further comprising:

the RRS sends a discovery message again;

12. The method of claim 9 or 10, wherein the registration request message is a broadcast message.

13. An apparatus for RRS management on an application and RCC, the apparatus comprising:

a receiving module, configured to receive a discovery message sent by an RRS, where the discovery message carries an identifier of the RRS; and the RRS is used for sending a registration invitation message to the RRS if the RRS is judged not to be registered on the RCC according to the identification of the RRS carried in the discovery message and the RCC can be used as the home RCC of the RRS;

14. The apparatus of claim 13, wherein the sending module is specifically configured to:

the RRS management apparatus further includes:

15. The apparatus of claim 13, wherein the sending module is specifically configured to:

16. The apparatus of claim 13, wherein the registration module is specifically configured to:

and when the judging module judges that the home RCC of the RRS is the RCC according to the identifier of the home RCC of the RRS carried in the registration request message, storing the configuration information of the RRS, establishing a link with the RRS, and marking the RRS as being registered on the RCC.

17. The apparatus of claim 13, further comprising:

and the maintenance module is configured to delete the mark preregistered by the RRS on the RCC when the determination module determines that the home RCC of the RRS is not the RCC according to the identifier of the home RCC of the RRS carried in the registration request message, and store the home relationship between the identifier of the RRS and the identifier of the home RCC of the RRS.

18. The apparatus according to any of claims 13 to 17, wherein the registration request message is a broadcast message.

19. The apparatus of any of claims 13-17, wherein the sending module is further configured to:

and if the RRS is judged to be registered on the RCC according to the identification of the RRS carried in the discovery message, sending a keep-alive confirmation message to the RRS, wherein the keep-alive confirmation message is used for informing that the RRS is registered on the RCC.

20. The apparatus according to any one of claims 13 to 17, wherein the registration invitation message carries one or more of the following information: geographical location information of the RCC, communication bandwidth information between the RCC and the RRS, and communication delay information between the RCC and the RRS.

21. An apparatus for RRS management on an application and RRS, the apparatus comprising:

a receiving module, configured to receive registration invitation messages sent by one or more RCCs, where a registration invitation message sent by an RCC is sent to the RRS when the RCC determines, according to an identifier of an RRS carried in the discovery message, that the RRS is not registered on the RCC and determines that the RCC can serve as a home RCC of the RRS;

22. The apparatus of claim 21, wherein the determination module is specifically configured to:

determining an RCC as an RCC to which the RRS belongs according to one or more of the following information carried in a registration invitation message sent by one or more RCCs received by the receiving module: geographical location information of the RCC, communication bandwidth information between the RCC and the RRS, and communication delay information between the RCC and the RRS.

23. The apparatus of claim 21 or 22, wherein the sending module is further configured to: after the RRS completes the registration to the RCC to which the RRS belongs, the discovery message is sent again;

the receiving module is further configured to:

receiving a keep-alive confirmation message sent by a home RCC of the RRS, and receiving registration invitation messages sent by N other RCCs, wherein N is an integer greater than or equal to 1;

the device, still include:

24. The apparatus of claim 21 or 22, wherein the registration request message is a broadcast message.