Small base station management method and system

Abstract

The present application discloses a method and system for managing a small base station. The method is applied to a network system in which a small base station is simultaneously managed by multiple parallel OMC servers, wherein the small base station establishes a connection with each operator's OMC server via the TR069 protocol, and the small base station records parameter values ​​corresponding to each operator's OMC server, and the parameter values ​​corresponding to each operator's OMC server are associated with the operator attribute values ​​of the OMC server of the operator to which it belongs. The method comprises: receiving a management request for a target parameter initiated by the OMC server; determining the operator attribute value corresponding to the management request; and processing the target parameter associated with the operator attribute value to respond to the management request.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of network communications, and in particular to a management method and system for small base stations. Background Art

[0002] TR069 is a protocol for communication between CPE (Customer Premise Equipment) and ACS (Auto-Configuration Server). This protocol enables automatic provisioning and management of CPE. Small cells can also be considered a type of CPE providing wireless access within the network management context. Therefore, TR069 is the southbound network management protocol for small cells in the communications industry standards.

[0003] At present, all domestic operators have formulated southbound network management specifications for small base stations. In these southbound network management specifications, the network manager is the only device that manages small base stations (CPE), and there is a one-to-one correspondence, which means that a small base station can only be managed by one network manager. Figure 1 This is a schematic diagram of small base station network deployment, refer to Figure 1 As shown in the figure, operators generally deploy an OMC Server (Operation and Maintenance Center Server) as a network management server at the gathering place of small base stations in a city or province (also known as the core room), and manage multiple small base stations through multiple OMC Clients (Operation and Maintenance Center Clients). Each small base station is managed by a unique OMC Server. In other words, according to the southbound network management specifications, Figure 1 In the network deployment shown, a small base station can only be managed by one operator's OMC server. Alarm and performance data can be obtained from the small base station and configuration operations can be performed on the small base station. Although other operators also have OMC servers, they cannot manage the small base station.

[0004] With the advent of the 5G era, wireless access systems utilize higher frequencies to deploy networks. Therefore, deploying the same network requires significantly more 5G equipment than 4G equipment, significantly increasing network construction costs for operators. Therefore, co-construction and sharing are key approaches to reducing network deployment costs. Under this co-construction and sharing strategy, a single small base station can simultaneously serve two or more operators. Each operator has its own OMC server, making it increasingly urgent to more effectively manage a small base station across multiple operators' OMC servers. Summary of the Invention

[0005] In order to solve any of the above technical problems, the embodiments of the present application provide a small base station management method and system.

[0006] To achieve the purpose of the embodiments of the present application, the embodiments of the present application provide a small base station management method, which is applied to a network system in which the small base station is simultaneously managed by multiple parallel OMC servers, wherein the small base station establishes a connection with each operator's OMC server via the TR069 protocol, and the small base station records parameter values ​​corresponding to each operator's OMC server, and the parameter values ​​corresponding to each operator's OMC server are associated with operator attribute values ​​of the operator's OMC server. The method includes:

[0007] Receive the management request for target parameters initiated by the OMC Server;

[0008] Determining an operator attribute value corresponding to the management request;

[0009] The target parameter associated with the operator attribute value is processed to respond to the management request.

[0010] A small base station management system, comprising:

[0011] A small base station, used to implement the method described above;

[0012] Multiple operator OMC servers are set up in parallel, and the small base station is managed by multiple OMC servers at the same time.

[0013] One of the above technical solutions has the following advantages or beneficial effects:

[0014] By recording the parameter values ​​corresponding to each operator's OMC Server on the small base station, and associating the parameter values ​​corresponding to each operator's OMC Server with the operator attribute values ​​of the operator's OMC Server, the purpose of extending the TR069 protocol is achieved, so that the small base station can be managed by the OMC Servers of multiple operators, and multiple operators can set up their own OMC Servers to manage the jointly built and shared base stations.

[0015] Other features and advantages of the embodiments of the present application will be described in the following description, and in part will become apparent from the description or be understood by practicing the embodiments of the present application. The objectives and other advantages of the embodiments of the present application can be achieved and obtained through the structures particularly pointed out in the description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The accompanying drawings are used to provide a further understanding of the technical solutions of the embodiments of the present application and constitute a part of the specification. Together with the embodiments of the embodiments of the present application, they are used to explain the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions of the embodiments of the present application.

[0017] Figure 1 Schematic diagram of small cell network deployment;

[0018] Figure 2 A network deployment diagram of a small base station management system provided in an embodiment of the present application;

[0019] Figure 3 A flowchart of a small base station management method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0020] To make the purpose, technical solutions and advantages of the embodiments of the present application more clear, the embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that, unless there is a conflict, the embodiments and features in the embodiments of the present application can be combined with each other in any way.

[0021] In order to enable all shared operators to manage co-built and shared equipment, this application proposes a network management system for small base stations. In this small base station management system, each small base station can be managed by the OMC Servers of multiple operators at the same time, and all OMC Servers are set up in parallel, and there is no distinction between primary and secondary logical roles.

[0022] Figure 2 This is a network deployment diagram of the small base station management system provided in the embodiment of this application. Figure 2 As shown, in this network structure, for a more concise description, only two parallel operator OMC Servers are shown, namely: OMC Server A of operator A and OMC Server B of operator B; the small base station can be managed by OMC Server A of operator A and OMC Server B of operator B.

[0023] Figure 3 This is a flow chart of a small base station management method provided in an embodiment of the present application. Figure 3 As shown, the method is applied to a network system in which small cells are managed by multiple parallel OMC servers. Parallel configuration can be understood as the network system managing multiple OMC servers having equal management status over the small cells, with no hierarchy. The operator's OMC servers and small cells establish a connection via the TR069 protocol.

[0024] The parameter values ​​corresponding to each operator's OMC server are recorded on the small cell, and each parameter is associated with the operator attribute value corresponding to the operator's OMC server. Each parameter has a unique parameter meaning and corresponds to a unique data model.

[0025] Specifically, the association of the parameter value with the operator attribute value corresponding to the operator's OMC server indicates that the parameter can be managed by the OMC server corresponding to the operator attribute value. In other words, all parameters on the small cell that can be managed by a certain OMC server are associated with the operator attribute value corresponding to the OMC server. The operator attribute value can be the operator's PLMN (Public Land Mobile Network) value or a predetermined value.

[0026] Furthermore, all parameter values ​​can be recorded separately for each OMC Server on the small base station. In this case, the operator attribute value can be the PLMN value of the operator; or the unique parameter value can be recorded separately for each OMC Server. In this case, the operator attribute value of each parameter can be recorded as the PLMN value of each OMC Server; and for parameter values ​​shared by multiple OMC Servers, the corresponding shared OMC Servers record a copy together. In this case, the operator attribute value can be recorded as a predetermined value corresponding to the multiple shared OMC Servers, but the predetermined value needs to be associated with the operator attribute value of each shared OMC Server; wherein, the shared parameters can include: common parameters, and can also include non-common parameters with the same parameter values ​​for the same data model.

[0027] Furthermore, corresponding to the OMC servers of different operators, small cells can record parameters with the same or different parameter meanings respectively. Parameters with the same parameter meanings belonging to OMC servers of different operators have the same data model but can have different data model names and parameter names, thereby further distinguishing parameters of different operators.

[0028] Furthermore, a parameter meaning "network management online status" is added. Only when the data model parameter value corresponding to "network management online status" is marked as "online" can the small base station accept the operator's OMC server management;

[0029] In a specific implementation of the present application, the standard TR181 data model parameters for the small base station connection network management are still used, and are expanded on the basis of the parameters of the existing technology. For example, there are multiple parallel-set OMC Servers of operators in the small base station management system that manage them at the same time. Then, a set of parameters is stored for each OMC Server in the small base station. The data model name and the corresponding parameter name of each parameter in each set of parameters are distinguished according to the set rules (typically, a recognizable extension of the naming rules of the existing technology is sufficient), and parameters with the meaning of "network management online status" are added to the network management link class parameters.

[0030] The following is an example of some parameters when there are two operators' OMC Servers. Two sets of OMC Server parameters are stored on the small base station at the same time. The data model name in the parameters of OMC Server A is: Device...., the parameter name is: the parameter name in the existing technology, and the corresponding operator attribute values ​​are all set to PLMN A; correspondingly, the data model name in the parameters of OMCServer B is: Device.X_Vendor_..., the network management link class parameter name is: X_Vendor_+ parameter name in the existing technology, and the parameter names of the remaining parameters are: parameter names in the existing technology, and the corresponding operator attribute values ​​are all set to PLMN B; and a parameter that identifies the "network management online status" is added to the network management link class parameters, and its data model names are: Device.ManagementServer.managerStatus and Device.X_Vendor_ManagementServer.managerStatus respectively. Examples of some parameters stored on the small base station are as follows:

[0031] (1) Network management link class:

[0032] The original parameters in the prior art are shown in Table 1:

[0033] Data model name Parameter name Parameter meaning Device.ManagementServer.URL URL Network management server URL Device.ManagementServer.Username Username Connection Username Device.ManagementServer.Password Password Connection password Device.ManagementServer.PeriodicInformEnable PeriodicInformEnable Connect the enabling switch Device.ManagementServer.PeriodicInformTime PeriodicInformTime Reporting cycle Device.ManagementServer.PeriodicInformInterval PeriodicInformInterval Periodic reporting interval

[0034] Table 1

[0035] The extended parameters of the embodiment of this application are shown in Table 2:

[0036]

[0037]

[0038] Table 2(2) Log transmission class

[0039] The original parameters in the prior art are shown in Table 3:

[0040] Data model name Parameter name Parameter meaning Device.LogMgmt.PeriodicUploadEnable Enable Whether to enable log upload Device.LogMgmt.URL URL Upload URL Device.LogMgmt.Username Username username Device.LogMgmt.Password Password password Device.LogMgmt.PeriodicUploadInterval PeriodicUploadInterval Log upload cycle

[0041] Table 3 Extended parameters of the embodiment of this application are shown in Table 4:

[0042]

[0043]

[0044] Table 4 (3) Performance Statistics Upload Class The original parameters in the existing technology are shown in Table 5:

[0045] Data model name Parameter name Parameter meaning Device.FAP.PerfMgmt.Config.1.Enable Enable Whether to enable performance statistics Device.FAP.PerfMgmt.Config.1.Alias Alias Performance Task Friendly Name Device.FAP.PerfMgmt.Config.1.URL URL Upload URL Device.FAP.PerfMgmt.Config.1.Username Username username Device.FAP.PerfMgmt.Config.1.Password Password password Device.FAP.PerfMgmt.Config.1.PeriodicUploadInterval PeriodicUploadInterval Collection cycle Device.FAP.PerfMgmt.Config.1.PeriodicUploadTime PeriodicUploadTime Collection start time

[0046] Table 5 Extended parameters of the embodiment of this application are shown in Table 6:

[0047]

[0048]

[0049] Table 6 (4) MR (MesaureReport) Statistics Upload Class Original Parameters in the Existing Technology See Table 7:

[0050]

[0051]

[0052] Table 7 Extended parameters of the embodiment of this application are shown in Table 8:

[0053]

[0054]

[0055] Table 8

[0056] Here are some additional points:

[0057] (1) The functional classification of parameters can refer to the classification principles in the prior art and is not limited here. Furthermore, the functional classification of parameters is only for better explanation. The communication between the small base station and the OMC Server follows the existing standard southbound interface specification: using the TR069 protocol, so that the small base station can be managed by the OMC Server; the parameters involved in OMC management in the southbound interface specification are typically classified by function as shown in Table 9:

[0058]

[0059] Table 9

[0060] (2) Regarding parameters, in the above implementation, since the network management link parameters are small base stations corresponding to different OMC Servers, the data model names and parameter names are completely different for different OMC Servers. For other parameters, since they are for the small base stations themselves, the same parameter names can be used; of course, in other implementations, for different OMC Servers, the data model names and parameter names corresponding to parameters with the same parameter meaning can be different, as long as they can be distinguished according to the set rules.

[0061] (3) In the above implementation, the parameters recorded by the small base station include a parameter meaning "network management online status", but in other implementations, the small base station may not contain this parameter. In this case, it is assumed that the small base station is always managed by the operator's OMC Server.

[0062] (4) In the above implementation, the common parameters of the OMC Servers of multiple operators generally include: configuration parameters of small base station public resources, performance parameters and alarm parameters, etc., for example: resource parameters such as CPU usage, memory usage, transmission resources, and software version of the main control board; the unique parameters of each operator's OMC Server include: cell wireless resources of wireless services, physical resources carried by wireless resources, transmission resources and other abstract configuration management parameters, performance parameters and alarm parameters, etc.; however, the above unique parameter values ​​can be the same or different for the OMC Servers of different operators. If they are the same, they can be shared parameters.

[0063] In the above-mentioned small base station management system, the method includes:

[0064] Step S1: receiving a management request for target parameters initiated by the OMC Server;

[0065] Step S2: Determine the operator attribute value corresponding to the management request;

[0066] Step S3: Process the target parameter associated with the operator attribute value to respond to the management request.

[0067] The method provided in the embodiment of the present application achieves the purpose of extending the TR069 protocol by recording the parameter values ​​corresponding to the OMC Server of each operator on the small base station, and associating the parameter values ​​corresponding to the OMC Server of each operator with the operator attribute value of the OMC Server of the operator to which it belongs, so that the small base station can accept the management of the OMC Server of multiple operators, and multiple operators can set up their own OMC Server to manage the jointly built and shared base stations.

[0068] The establishment of a connection between the small base station and each operator's OMC Server through the TR069 protocol includes:

[0069] Step 1000: After each operator's OMC Server determines that it needs to manage the small cell, it sends an HTTP Get message with an empty message body to the small cell. The message carries the operator attribute value in the CWMP:ID field, indicating that it wishes to manage the small cell. The OMC Server instructs the small cell to associate the operator attribute value with the parameters managed by the corresponding operator's OMC Server.

[0070] In this step, the small cell is known as a managed object of the OMC Server during network planning. The small cell knows the addresses of all operators' OMC Servers that need to manage it and records them in the parameters of the local OMC Server data model, for example, the parameter value of the data model name Device.ManagementServer.URL of the OMC Server A parameter mentioned in the above specific implementation; and the parameter value of the data model name Device.X_Vendor_ManagementServer.URL of the OMC Server B parameter. When the small cell is activated, it automatically reports the local address to the OMC Server that needs to manage it according to the corresponding parameter values, so that the OMC Server records it as a managed object.

[0071] Step 1001: The small cell sends an HTTP Response message to each operator's OMC Server, where the status code is 200, indicating that the small cell is in normal status.

[0072] Step 1002: The small cell establishes a TCP connection to each operator's OMC server;

[0073] Step 1003: The small cell establishes a security mechanism with each operator's OMC Server via SSL;

[0074] Step 1004: The small cell sends an Inform message to each operator's OMC Server. The Eventcode field of the Inform message describes the reason for sending the Inform message. Here, it is "6CONNECTION REQUEST", indicating that the small cell requests to start establishing an HTTP connection.

[0075] Step 1005: If the operator's OMC Server passes the authentication of the small cell, it returns a response message (InformResponse, HTTP 200OK) to the small cell, indicating that the HTTP connection between the two is successfully established.

[0076] Step 1006: The small cell sends an HTTP Post message with an empty message body to each operator's OMC Server to meet the HTTP message request / response message interaction rules. The empty message body indicates that the small cell has no message to report to the OMC Server at this moment and only establishes a connection between the two.

[0077] Therefore, through the above method, multiple operators' OMC Servers can be set up in parallel in the small base station management system. Each operator's OMC Server can serve as the network management of the small base station, and there is no distinction between primary and secondary logical positions. Each operator's OMC Server can use the TR069 protocol to obtain parameter information recorded in the small base station, realizing information sharing on the small base station.

[0078] In an exemplary embodiment, the management request is a parameter value acquisition message.

[0079] When the small cell receives a parameter information acquisition command initiated by the operator's OMC server, it locally acquires the parameter value associated with the operator attribute value and that the OMC server wants to acquire based on the operator attribute value included therein, and returns the acquired parameter value to the OMC server;

[0080] In this step, when the small base station receives a parameter information acquisition command initiated by the operator's OMC Server, if the operator attribute value in the parameter information acquisition command is the operator attribute value associated with the parameter locally recorded by the small base station, it is considered that the OMC Server can manage the small base station. Otherwise, it does not fall within the scope of this application and is processed in accordance with the existing technology. Still taking the above specific implementation method of setting OMC Server A and OMC Server B in parallel to manage the small base station as an example, if the operator attribute value in the parameter information acquisition command received by the small base station is PLNM A, the operator attribute values ​​associated with the parameters locally recorded by the small base station include: PLNM A and PLNM B. Therefore, the operator attribute value in the parameter information acquisition command received by the small base station is the operator attribute value associated with the parameter locally recorded by the small base station, and the small base station can be managed by OMC Server A.

[0081] When the base station receives the parameter information acquisition command initiated by the operator's OMC server, it locally acquires the parameter value associated with the operator attribute value and that the OMC server wants to acquire based on the operator attribute value included therein, as follows:

[0082] When the small base station receives a parameter information acquisition command, it obtains the operator attribute value carried therein and the data model name corresponding to the parameter to be obtained, and searches the local record for the parameter value associated with the operator attribute value and corresponding to the data model name.

[0083] Furthermore, the parameter information acquisition command initiated by the operator's OMC Server is an HTTPGetParameterValues ​​message. At this time, when the small base station receives the parameter information acquisition command initiated by the operator's OMC Server, it locally obtains the parameter value associated with the operator attribute value and that the OMC Server wants to obtain based on the operator attribute value included therein, specifically including:

[0084] Step 100: The small cell receives an HTTP GetParameterValues ​​message sent by the OMC Server to the small cell, querying the parameters corresponding to GetParameterValues ​​in all parameter models on the small cell, and carries the operator attribute value in CWMP:ID, where the operator attribute value is the PLMN value of the OMC Server;

[0085] Step 101: The small cell locally determines and obtains the data model parameter value required in the HTTPGetParameterValues ​​message and associated with the operator attribute value according to the received operator attribute value included in the HTTPGetParameterValues ​​message, thereby completing a Get operation on the small cell.

[0086] One special note here: If all parameters of the OMC Servers corresponding to different operators are recorded separately on the small base station, the required data model parameter values ​​can be directly associated according to the operator attribute values; if the OMC Servers corresponding to different operators record a set of parameter values ​​shared by the OMC Servers, it is also necessary to determine whether the operator attribute values ​​included in the HTTPGetParameterValues ​​message are associated with the predetermined values ​​of multiple shared OMC Servers. If so, the required data model parameter values ​​can be associated according to the predetermined values.

[0087] Step 102: The small cell replies to the OMC Server with a GetParameterValues ​​Response message, where the GetParameterValues ​​Response message includes the acquired parameter values.

[0088] Of course, since the OMC Server and the small cell communicate via the TR069 protocol, after completing the above operations, the corresponding protocol-required operations will also be performed. I will not go into details here, but typically at least include:

[0089] The OMC Server sends an empty message (HTTP 204 No Content) to the small cell, indicating a request to end the session. After receiving the empty message, the small cell disconnects the HTTP and TCP connections, and the session officially ends.

[0090] In an exemplary embodiment, the management request is a parameter value setting message.

[0091] After a connection is established between the operator's OMC Server and the small base station through the TR069 protocol, when the operator needs to configure parameters for the small base station, the operator's OMC Server sends parameter configuration information to the small base station. The parameter configuration information includes the name of the data model to be configured and the parameter value to be set, and carries the operator attribute value.

[0092] When the small base station receives the parameter configuration information, it updates the corresponding parameter value of the data model name corresponding to the local operator attribute value with the parameter value corresponding to the data model name carried in the parameter configuration information.

[0093] Furthermore, the operator's OMC Server sends the parameter configuration information as a SetParameterValues ​​message. At this time, when the small base station receives the parameter configuration information, it updates the data model parameters corresponding to the local operator attribute values ​​with the data model parameter values ​​carried therein. Specifically, the following are included:

[0094] Step 200: The OMC Server sends a SetParameterValues ​​message to the small cell to configure parameters on the small cell. The field cwmp:SetParameterValues ​​in the SetParameterValues ​​message includes: the data model name (name) and the corresponding parameter value (value) to be set, and the operator attribute value is carried in the field CWMP:ID;

[0095] Step 201: After receiving the SetParameterValues ​​message, the small cell updates the parameters corresponding to the local operator attribute value with the data model name and parameter value carried therein; and replies with a SetParameterValues ​​Response message to the OMC Server.

[0096] One special note here: Since the multiple OMC Servers that manage the small base station are set in parallel, the parameters in the small base station are also set separately. Therefore, if the parameters set here are parameters maintained solely by the OMC Server, the Set operation is completed after the above step 201; whether the parameters are parameters maintained solely by the OMC Server can be determined based on the operator attribute value associated with the parameter. If the operator attribute value is associated with only one OMC Server, the parameter is exclusive to the OMC Server. If it is associated with multiple OMC Servers, the parameter is shared by multiple OMC Servers. Therefore, if the parameters that need to be configured received by the small base station are shared parameters of multiple OMC Servers, the following steps are continued:

[0097] Step 2011: Initiate a TR069 connection to other OMC servers that share the parameters with the OMC server that initiated the Set operation.

[0098] In this step, since the OMC server carries the operator attribute value when sending the SetParameterValues ​​message to the small base station, the small base station knows which OMC server initiated the Set operation; and through the operator attribute value associated with the parameter (because the operator attribute value corresponding to the parameter is associated with the respective operator attribute values ​​of the shared OMC Server), the small base station can determine the other OMC servers that need to share the parameter;

[0099] Step 2012: After establishing a TR069 connection with other OMC Servers, the small base station sends Inform messages to each of them. The Eventcode field of the Inform message describes the reason for sending the Inform message, which is "OMC SetChange" here, indicating that the small base station has received a modification of the parameter value of a shared parameter initiated by an OMC Server and needs to notify the other OMC Servers that share the parameter of the modified value. The OMC Server that receives the message determines whether to allow the parameter to be changed for this OMC Server as well.

[0100] Step 2013: If the small cell receives an Inform Response message from the OMC Server within the set time, it indicates that the OMC Server has received the Inform message and replies to the small cell whether the OMC Server allows the parameter value to be changed. Specifically, the parameter name and IfEnable field can be added to the InformResponse message. IfEnable is set to 0, it indicates that the change is not allowed; IfEnable is set to 1, it indicates that the change is allowed. The Inform Response message also carries the operator attribute value of the OMC Server.

[0101] Step 2014: If the small base station receives Inform Response messages sent by all other OMC Servers that share the parameter within the predetermined time, and all indicate that the parameter value is allowed to change, the parameter value of the shared parameter is updated, and there is no need to change the vendor attribute value associated with the parameter, and the Set operation ends; otherwise, if the parameter value of a universal parameter changes, the modification is not allowed, the original correspondence between the operator attribute value and the parameter value is maintained, and the Set operation ends; if the parameter value of a non-universal parameter changes, the operator attribute value of the OMC Server that is allowed to change the parameter is associated with the operator attribute value corresponding to the shared parameter, and the shared parameter value is updated; and further, an association relationship is established between the operator attribute value of the OMC Server that is not allowed to change the parameter and the parameter, so that the operator attribute value of the OMC Server that is not allowed to change the parameter is no longer associated with the operator attribute value corresponding to the shared parameter, and the parameter corresponding to the operator attribute value of the OMC Server that is not allowed to change the parameter maintains the original parameter value; and the Set operation ends. It is particularly noted that: if the operator attribute value corresponding to the shared parameter is associated with an operator attribute value of an OMC Server that allows the parameter to be changed, the association between the shared parameter and the corresponding operator attribute value can be directly cancelled, and the parameter can be kept corresponding to the operator attribute value of the allowed OMC Server.

[0102] It can be seen from this that through the above method, when an OMC Server initiates the configuration of parameter values ​​for a certain data model, if the parameter is a non-universal parameter but is shared, it will automatically initiate the judgment and corresponding configuration process of whether other OMC Servers are also allowed to modify it, which greatly expands the operability of the small base station system to receive multiple OMC Servers for parallel management.

[0103] The small base station management method also includes: after a connection is established between the OMC Server of each operator and the small base station via the TR069 protocol, the small base station sends reporting information to the OMC Server of a specific operator when an information reporting trigger condition is met; the OMC Server of the specific operator here is: the OMC Server corresponding to the information to be reported, which can be one or more according to the set conditions, and the reporting information is the data model parameters associated with the operator attribute value corresponding to the OMC Server and required to be reported according to the preset policy.

[0104] Specifically: The reporting information sent to the OMC Server of a specific operator includes:

[0105] Step 301: The small cell establishes a TCP connection with the OMC server of a specific operator;

[0106] Step 302: A security mechanism is established between the small cell and the OMC server of a specific operator through SSL;

[0107] Step 303: The small base station sends an Inform message to the OMC Server of a specific operator. The Inform message carries the operator attribute value and the Eventcode field describes the reason for sending the Inform message, which is "4valuechange" here, indicating that the small base station wants to report the changed parameters to the OMC Server; typically, the operator attribute value can be the PLMN value carried in the CWMP:ID.

[0108] Step 304: The OMC Server of a specific operator sends an Inform Response message to each small cell. The Inform Response message carries an operator attribute value to indicate which OMC Server receives the Inform message.

[0109] Step 305: The small cell sends a POST message with an empty message body to the OMC Server of the specific operator, requesting to end the session.

[0110] Step 306: The OMC Server of the specific operator sends an HTTP 204 message with an empty message body to the small cell, which carries the operator attribute value to indicate which OMC Server accepts the session end request.

[0111] Step 307: The base station disconnects the HTTP and TCP connections, and the session officially ends.

[0112] The triggering conditions for reporting information are: reaching the information reporting period or the occurrence of a preset external event;

[0113] The small base station management method also includes: after a connection is established between the OMC Server of each operator and the small base station via the TR069 protocol, the small base station sends a reporting file to the OMC Server of a specific operator when a file reporting trigger condition is met; the OMC Server of the specific operator here is: the OMC Server corresponding to the file to be reported, which can be one or more according to the set conditions, and the reporting file is a file associated with the operator attribute value corresponding to the OMC Server and required to be reported according to a preset policy.

[0114] Specifically: Sending a report file to a specific operator's OMC Server includes:

[0115] Step 401: The small cell establishes a TCP connection with the OMC server of a specific operator;

[0116] Step 402: A security mechanism is established between the small cell and the OMC server of a specific operator through SSL;

[0117] Step 403: The small cell sends an HTTP Put message for uploading a file to the OMC server of a specific operator. The HTTP Put message carries an operator attribute value.

[0118] Step 404: The OMC Server of the specific operator sends an HTTP 201 Created message to the small cell. The HTTP 201 Created message carries an operator attribute value to indicate which OMC Server receives the file content and completes the file creation.

[0119] Step 405: The small cell sends an HTTP POST message to the OMC Server of a specific operator, which carries the operator attribute value and the Eventcode field is M Upload, to notify the OMC Server of the operator that the file upload is initiated and the transmission is completed.

[0120] Step 406: The OMC Server of the specific operator sends an HTTP 200 InformResponse message to the small cell, which carries an operator attribute value, indicating which operator's OMC Server receives the file report.

[0121] Step 407: The small cell sends an AutonomoutTransfer Complete message to the OMC Server of the specific operator, notifying the OMC Server of the specific operator of the uploaded file name, upload result, etc.

[0122] Step 408: The OMC Server of the specific operator sends an HTTP 200 Autonomous Transfer Complete Response message to the small cell, which carries the operator attribute value, indicating which operator's OMC Server receives the automatic transfer complete message.

[0123] Step 409: The small cell sends a POST message with an empty message body to the OMC Server of the specific operator, requesting to end the session.

[0124] Step 410: The OMC Server of a specific operator sends an HTTP 204 message with an empty message body to the small cell, which carries an operator attribute value to indicate which OMC Server accepts the session end request.

[0125] The triggering conditions for reporting files are: reaching the file reporting period or the occurrence of a preset external event;

[0126] The reporting file includes: at least one of a performance statistics file, a log file and a measurement result file.

[0127] The method and system provided by the embodiment of the present application extend the TR069 protocol, so that small base stations can be managed by multiple management stations. In the case of co-construction and sharing, different operators can set up their own OMC servers to manage the co-construction and sharing base stations.

[0128] It will be appreciated by those skilled in the art that all or some of the steps, systems, and functional modules / units in the methods disclosed above may be implemented as software, firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all components may be implemented as software executed by a processor, such as a digital signal processor or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As is well known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable, and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those skilled in the art that communication media generally embodies computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

Claims

1. A small base station management method is applied to a network system in which a small base station is managed by multiple parallel OMC servers, wherein: The small base station establishes a connection with each operator's OMC Server via the TR069 protocol, and the small base station records parameter values ​​corresponding to each operator's OMC Server, and the parameter values ​​corresponding to each operator's OMC Server are associated with operator attribute values ​​of the operator's OMC Server. The method includes: Receive the management request for target parameters initiated by the OMC Server; Determining an operator attribute value corresponding to the management request; If the management request is a parameter value setting message, and the number of operator attribute values ​​associated with the target parameter is greater than one, processing the target parameter associated with the operator attribute value to respond to the management request includes: Initiating a notification message to all OMC servers sharing the target parameter except the OMC server that initiated the management request, wherein the notification message is used to confirm whether it is allowed to modify the value of the target parameter to the parameter value carried in the parameter setting message; Receive responses from other OMC Servers; After receiving the response from each of the other OMC servers, manage the value of the target parameter according to the received response; The managing of the value of the target parameter according to the received response includes: If all received responses indicate that parameter value changes are allowed, then the value of the target parameter is updated to the parameter value carried in the management request, and the operator attribute value associated with the target parameter remains unchanged; If the received responses do not all indicate that parameter value changes are allowed, and the target parameter is a universal parameter, then updating the parameter value of the target parameter is not allowed, and the operator attribute value associated with the target parameter remains unchanged; If the response does not all indicate that the parameter value is allowed to change, and the target parameter is a non-universal parameter, the operator attribute value of the OMC Server that is allowed to update the target parameter will be associated with the operator attribute value corresponding to the target parameter, and the parameter value of the target parameter will be updated; and an association relationship between the operator attribute value of the OMC Server that is not allowed to update the parameter value of the target parameter and the target parameter will be established, wherein the parameter corresponding to the operator attribute value that is not allowed to update the parameter value of the target parameter maintains the original parameter value unchanged.

2. The method according to claim 1, characterized in that The following methods are used to establish a connection between the small cell and each operator's OMC Server using the TR069 protocol, including: Receive an HTTP get message with an empty message body sent by each operator's OMC Server, wherein the HTTP get message carries the operator attribute value of the OMC Server; Send an HTTP response message to each operator's OMC Server, where the status code in the HTTP response message is 200, indicating that the small cell is in a normal state. Establish a TCP connection to each operator's OMC Server; Establish a security mechanism between each operator's OMC Server through SSL; Send an Inform message to each operator's OMC Server respectively, where the sending reason in the event type field of the Inform message carries instruction information requesting to establish an HTTP connection; If the operator's OMC Server passes the authentication of the small cell, an Inform response message carrying the content "OK" is received from the operator's OMC Server, indicating that the HTTP connection is successfully established. Send an HTTP Post message with an empty message body to each operator's OMC Server.

3. The method according to claim 2, characterized in that The network system management of small base stations managed by multiple parallel OMC servers is achieved through the following: After receiving an HTTP get message with an empty message body from each operator's OMC Server, for each received operator attribute value, establish an association relationship between the operator attribute value and the corresponding OMC Server parameter value; After the small base station is opened, the address of the small base station is reported to the OMC Server with small base station management authority, so that the OMC Server of each operator records the small base station as a managed object.

4. The method according to claim 1, wherein Record the parameter values ​​corresponding to each operator's OMC Server on the small cell in the following ways: Record all parameter values ​​of each OMC Server under its own data model; or, For parameters shared by multiple OMC Servers, one copy is recorded for the shared OMC Servers, wherein the operator attribute value corresponding to the shared parameter is the operator attribute value of the shared OMC Servers. The shared parameter includes a common parameter or a non-common parameter with the same parameter value under the same data model.

5. The method according to claim 4, characterized in that: The parameters of each operator's OMC Server have their own meanings; If OMC servers belonging to different operators have parameters with the same meaning and the same data model, different data model names and parameter names are used to distinguish the parameters of different operators.

6. The method according to claim 4, wherein: The parameters of each operator's OMC Server also include parameters that indicate the online status of the network management; Only when the parameter value is Online in the data model that indicates the online status of the network management, the operator's OMC server management is allowed.

7. The method according to claim 4, characterized in that The processing of the target parameter associated with the operator attribute value to respond to the management request includes: If the management request is a parameter value acquisition message, the value of the target parameter in the data model corresponding to the operator attribute value is returned to the OMC Server via a parameter value acquisition response message; If the management request is a set parameter value message, the value of the target parameter in the data model corresponding to the operator attribute value is updated with the parameter value carried in the set parameter value message, and the update result is returned to the OMC Server via a set parameter value response message.

8. The method according to claim 7, characterized in that The updating of the target parameter value in the data model corresponding to the operator attribute value using the parameter value carried in the parameter value setting message includes: When the number of operator attribute values ​​associated with the target parameter is 1, the parameter value carried in the parameter value setting message is used as the value of the target parameter in the data model corresponding to the operator attribute value.

9. The method according to claim 1, wherein: The notification message is an Inform message, in which a parameter name field and an event type field are set, wherein the parameter name field carries the parameter name of the target parameter, and the event type field carries the indication information that the OMC Server changes the parameter value; The reply response is an Inform reply message, which is provided with a parameter name field and a reply field, wherein the parameter name field carries the parameter name of the target parameter, and the reply field carries indication information of whether the parameter value is allowed to be changed.

10. The method according to claim 1, characterized in that The method further comprises: After a connection is established between each operator's OMC Server and the small base station through the TR069 protocol, when the information reporting trigger condition is met, reporting information is sent to one or more operators' OMC Servers; wherein, the reporting information is the data model and / or parameter value associated with the operator attribute value corresponding to the OMC Server and required to be reported according to the preset policy.

11. The method according to claim 10, characterized in that The sending of reporting information to the OMC Server of one or more operators includes: Establishing a TCP connection with the OMC Server of one or more operators; Establish a security mechanism with one or more OMC Servers through SSL; Sending an Inform message to the OMC Server of the one or more operators, wherein the Inform message carries an operator attribute value, and an event type field in the Inform message carries a reason for reporting information; Receive an Inform Response message sent by the OMC Server of the one or more operators, where the Inform Response message carries an operator attribute value, indicating that the OMC Server corresponding to the operator attribute value has received the Inform message; Sending a POST message with an empty message body to the OMC Server of the one or more operators to request to end the session; Receive an HTTP 204 message with an empty message body, which carries an operator attribute value and is sent by the OMC Server of the one or more operators, indicating that the OMC Serer corresponding to the operator attribute value accepts the session end request; The HTTP connection and the TCP connection with the OMC Server of the one or more operators are disconnected.

12. The method according to claim 1, characterized in that The method further comprises: After a connection is established between each operator's OMC Server and the small base station through the TR069 protocol, when the file reporting trigger condition is met, a reporting file is sent to one or more operators' OMC Servers; the reporting file is the file associated with the operator attribute value corresponding to the OMC Server and needs to be reported according to the preset policy.

13. The method according to claim 12, characterized in that The sending of the report file to the OMC Server of one or more operators includes: Establishing a TCP connection with the OMC Server of one or more operators; Establish a security mechanism with the OMC Server of one or more operators through SSL; Sending an HTTP Put message carrying file content to the OMC Server of the one or more operators, wherein the HTTP Put message carries an operator attribute value; Receive an HTTP 201 Created message sent by the OMC Server of the one or more operators, where the HTTP 201 Created message carries an operator attribute value, indicating that the OMC Server corresponding to the operator attribute value has received the file content and completed file creation; Send an HTTP POST message to the OMC Server of the one or more operators, which carries the operator attribute value and the content of the event type field is M Upload; Receive an HTTP 200 Inform response message sent by the OMC Server of the one or more operators, which carries the operator attribute value, indicating that the OMC Server corresponding to the operator attribute value has received the file report; Sending an automatic transmission completion message to the OMC Server of the one or more operators; Receive an HTTP 200 automatic transmission completion response message sent by the OMC Server of the one or more operators to the small base station, where the automatic transmission completion response message carries an operator attribute value, indicating that the OMC Serer of the operator corresponding to the operator attribute value has received the automatic transmission completion message; Sending a POST message with an empty message body to the OMC Server of the one or more operators to request the session to end; Send an HTTP 204 message with an empty message body to the small cell, which carries the operator attribute value, to the OMC Server of the one or more operators, indicating that the OMC Server corresponding to the operator attribute value accepts the session end request; The HTTP connection and the TCP connection with the OMC Server of the one or more operators are disconnected.

14. The method according to any one of claims 1 to 13, characterized in that: The operator attribute value is carried by the CWMP:ID field in the message sent by the OMC Server.

15. A small base station management system, comprising: A small base station, configured to implement the method according to any one of claims 1 to 14; Multiple operator OMC servers are set up in parallel, and the small base station is managed by multiple OMC servers at the same time.

Images