Base station data model analysis method and system based on TR069 protocol

Abstract

The present invention discloses a base station data model analysis method and system based on the TR069 protocol, the method comprising: step 1: the network management platform defines key information based on the full amount of data model parameters, and constructs a corresponding database form according to the key information; step 2: the network management platform obtains the corresponding data model parameters from the base station, and updates the database form according to the obtained parameters; step 3: the network management platform analyzes the updated database form to obtain the corresponding score; step 4: the network management platform outputs a parameter adaptation report corresponding to the base station according to the score. The present invention directly scores the information on the parameter adaptation, so that the user can understand the situation of the base station adaptation network management at one time. The present invention enables the user to have a more comprehensive understanding of the situation of the base station adaptation network management; and displays whether each parameter adaptation situation is passed, so that the user can analyze the specific adaptation situation conveniently.

Description

Technical Field

[0001] The present invention relates to the field of communication technologies, and in particular to a base station data model analysis method and system based on the TR069 protocol. Background Art

[0002] TR069 is the communication protocol for communication between CPE (Customer Premises Equipment) and ACS (AutoConfiguration Server). Currently, 5G small cell network management systems (an ACS system, also referred to as network management platform, network management, or ACS) generally use the TR069 protocol to manage small cells (a type of CPE), using TR-181 as the data model. When adapting data model parameters (parameters) between small cells and network management systems, a significant amount of manpower is often required to repeatedly address issues such as parameter integrity, parameter readability, and parameter value ranges, resulting in low efficiency. Currently, there is no effective way to fully verify data model parameters on the device before adapting the base station to the network management platform. Summary of the Invention

[0003] The technical problem to be solved by the embodiments of the present invention is to provide a base station data model analysis method and system based on the TR069 protocol to solve the data model parameter verification and adaptation problem when the base station adapts to the network management platform.

[0004] In order to solve the above technical problems, an embodiment of the present invention proposes a base station data model analysis method based on the TR069 protocol, including:

[0005] Step 1: The network management platform defines key information based on the full set of data model parameters and constructs a corresponding database form based on the key information;

[0006] Step 2: The network management platform obtains the corresponding data model parameters from the base station and updates the database table according to the obtained parameters;

[0007] Step 3: The network management platform analyzes the updated database form and obtains the corresponding score;

[0008] Step 4: The network management platform outputs the parameter adaptation report corresponding to the base station based on the score, completing the final adaptation analysis.

[0009] Accordingly, an embodiment of the present invention further provides a base station data model analysis system based on the TR069 protocol, comprising:

[0010] Construction unit: defines key information based on the full set of data model parameters and constructs corresponding database forms according to the key information;

[0011] Acquisition unit: obtains corresponding data model parameters from the base station and updates the database table according to the acquired parameters;

[0012] Analysis unit: Analyze the updated database form and obtain the corresponding score;

[0013] Output unit: Outputs the parameter adaptation report corresponding to the base station based on the score to complete the final adaptation analysis.

[0014] The beneficial effects of the present invention are:

[0015] 1. Before the network management platform manages the equipment, the present invention directly scores the information on parameter adaptation through a pre-made database form scoring system, so that users can understand the adaptation of the base station to the network management at one time.

[0016] 2. The present invention classifies parameters and scores them, and displays the scores based on three different dimensions, so that users can have a more comprehensive understanding of the base station adaptation network management; and displays whether each parameter adaptation status has passed, which facilitates users to analyze the specific adaptation situation. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 It is a flow chart of a base station data model analysis method based on the TR069 protocol according to an embodiment of the present invention. DETAILED DESCRIPTION

[0018] It should be noted that, unless there is a conflict, the embodiments in this application and the features in the embodiments can be combined with each other. The present invention is further described in detail below with reference to the drawings and specific embodiments.

[0019] Please refer to Figure 1 The base station data model analysis method based on the TR069 protocol in an embodiment of the present invention is applied to a network management platform, including steps 1 to 4.

[0020] Step 1: The network management platform defines key information based on the full set of data model parameters and constructs a corresponding database form according to the key information.

[0021] The network management platform divides the key parameter indicator information set {KeyParInfo1, ...,KeyParInfo i , ...,KeyParInfo N}, where KeyParInfo iContains ParName (parameter name), ParImp (importance), ParRWPer (read and write permissions), ParType (data type), ActParRWPer (actual read and write permissions), ActParType (actual data type), and ActParValue (actual parameter value).

[0022] The ParName (parameter name) is a tree-structured string. The ParImp (importance) is divided into two categories, A and B. Category A is the key parameter, and category B is the general parameter. The ParRWPer (read and write permission) includes R (read permission), W (write permission) and RW (read and write permission). The ParType (data type) refers to the format and value range of the parameter value. The word "actual" indicates the actual parameter information reported by the base station after the network management platform interacts with the base station. The N is the maximum number of entries in the set, that is, the maximum number of data model parameters. The i is {KeyParInfo1, ...,KeyParInfo i , ...,KeyParInfo N}, 1≤i≤N. i Refers to {KeyParInfo1, ...,KeyParInfo i , ...,KeyParInfo N} any object in .

[0023] The network management platform creates a database table EvaluationRulesTable and sets {KeyParInfo1, ...,KeyParInfo i , ...,KeyParInfo N} is written into EvaluationRulesTable in sequence. The writing method is:

[0024] Traverse {KeyParInfo1, ...,KeyParInfo i , ..., KeyParInfo N}, each record in turn {KeyParInfo i. ParName, KeyParInfo i. ParImp, KeyParInfoi. ParRWPer,KeyParInfo i. ParType, KeyParInfo i. ActParRWPer, KeyParInfo i. ActParType, KeyParInfo i. ActParValue} is written into the database as a record. i. ActParRWPer、 KeyParInfo i. ActParType and KeyParInfo i. The value of ActParValue is NULL (empty value), and it needs to be filled with the corresponding value after actual interaction with the base station.

[0025] After the above operation is completed, the database table EvaluationRulesTable contains a collection of N records, marked as {DBRuleInfo1, ...,DBRuleInfo j , ...,DBRuleInfo N} set, where N is the maximum number of entries in the set. j is the subscript number of any object in EvaluationRulesTable, 1≤j≤N. j Refers to any object in EvaluationRulesTable. Each record DBRuleInfo j Contains ParName (parameter name), ParImp (importance), ParRWPer (read and write permissions), ParType (data type), ActParRWPer (actual read and write permissions), ActParType (actual data type), and ActParValue (actual parameter value).

[0026] Step 2: The network management platform obtains the corresponding data model parameters from the base station and updates the database table according to the obtained parameters.

[0027] As an implementation method, the network management platform sends a GetParameterNames RPC message to the base station, and the base station returns a GetParameterNamesResponse RPC message. The network management platform obtains the key information set {PropertInfo1, ...,PropertInfo k , ...,PropertInfo M},

[0028] The M is the maximum number of entries in the set.

[0029] The k is {PropertInfo1, ...,PropertInfo k , ...,PropertInfo M}, 1≤k≤M.

[0030] The PropertInfo K Refers to the set {PropertInfo1, ...,PropertInfo k , ...,PropertInfo M}, which contains Pro_ParName (parameter name) and Pro_ParRWPer (read and write permissions) in the data model parameters reported by the base station.

[0031] The network management platform sends the GetParameterValues ​​RPC message to the base station, and the base station returns the GetParameterValuesResponse RPC message. The network management platform obtains the key information set {SubParInfo1, ...,SubParInfo x , ...,SubParInfo S},

[0032] The S is the maximum number of entries in the set.

[0033] The x is {SubParInfo1, ...,SubParInfo x , ...,SubParInfo S}, 1≤x≤S.

[0034] The SubParInfo x Refers to the set {SubParInfo1, ...,SubParInfo x , ...,SubParInfo S}, which contains the SubPar_ParName (parameter name), SubPar_ParType (data type) and SubPar_ParValue (parameter value) in the base station reporting data model parameters.

[0035] The network management platform will collect {PropertInfo1, ...,PropertInfo k , ...,PropertInfo M} and the collection {SubParInfo1, ...,SubParInfo x , ...,SubParInfo S The data in} is written to the database form EvaluationRulesTable, and the writing method is:

[0036] (1) Traverse {PropertInfo1, ...,PropertInfo k , ...,PropertInfo M Each PropertInfo in k If PropertInfo k. Pro_ParName finds the corresponding record DBRuleInfo in EvaluationRulesTable j (ie DBRuleInfo j. ParName equals PropertInfo k. Pro_ParName), then DBRuleInfo j Update data and set DBRuleInfo j. ActParRWPer=PropertInfo k. Pro_ParRWPer.

[0037] (2) Traverse {SubParInfo1, ...,SubParInfo x , ...,SubParInfo S Each SubParInfo in x , if SubParInfo x.SubPar_ParName finds the corresponding record DBRuleInfo in EvaluationRulesTable j (ie DBRuleInfo j. ParName equals SubParInfo x. SubPar_ParName), then DBRuleInfo j Update data and set DBRuleInfo j. ActParType= SubParInfo x. SubPar_ParType, DBRuleInfo j. ActParValue= SubParInfo x. SubPar_ParValue.

[0038] Step 3: Analyze the updated database form and obtain the corresponding score.

[0039] Traverse the collection of database table EvaluationRulesTable {DBRuleInfo1, ...,DBRuleInfo j , ...,DBRuleInfo N};

[0040] If DBRuleInfo j. If ActParValue is equal to NULL, the record is judged as failed and feedback is given to the user.

[0041] If (DBRuleInfo j. ActParValue is not equal to NULL)&& (DBRuleInfo j. ParRWPer equals DBRuleInfo j. ActParRWPer)&& (DBRuleInfo j. ParType equals DBRuleInfo j. ActParType), namely DBRuleInfo j. The value of ActParValue is not null, and DBRuleInfo j. ParRWPer equals DBRuleInfo j. ActParRWPer, while DBRuleInfo j. ParType equals DBRuleInfoj. ActParType, the record is judged as passed.

[0042] After scoring each record, the corresponding scoring and judgment results are added to the ActParValue field of the record. A pass is marked as P, and a fail is marked as F.

[0043] As an implementation method, the scoring method is:

[0044] Traverse the database table EvaluationRulesTable collection {DBRuleInfo1, ...,DBRuleInfo j , ...,DBRuleInfo N}, according to DBRuleInfo j. ParImp = A or B is scored respectively, and the scoring is divided into three dimensions:

[0045] Dimension 1, DBRuleInfo j. ParImp = A's parameters are scored by converting DBRuleInfo j. ParImp = the number of parameters passed by A / DBRuleInfo j. ParImp = the total number of corresponding parameters in A * 100;

[0046] Dimension 2: DBRuleInfo j. ParImp = B's parameters are scored by converting DBRuleInfo j. ParImp = the number of parameters passed by B / DBRuleInfo j. ParImp = the total number of corresponding parameters in B * 100;

[0047] Dimension 3: Score the overall parameters by dividing the number of passed parameters by the total number of parameters * 100.

[0048] As an implementation method, in order to facilitate comparison of parameters, it is determined that DBRuleInfo j .ParName and SubParInfo x .SubPar_ParName, PropertyInfo k .Pro_ParName are equal, the present invention quickly compares the parameters DBRuleInfoj.ParName with SubParInfox.SubPar_ParName, PropertInfo according to the following stepsk .Pro_ParName is equal:

[0049] Step (1): Split the parameter name with “.” to get the word set {P1,...,P n}. Where n is the number of words segmented, and P represents the word objects in the set.

[0050] Step (2), for the word set {P1,...,P n}, calculate the character length Len and ASCII value of each word P in the set {P1,...,P n}, and then combine them with "-" to form MA = TotalLen-Len(P1).VAL(P1)-Len(P2).VAL(P2)...-Len(P n ).VAL(P n ). Wherein, the Len(P n ) represents the length of the nth word in the word set, and the VAL(P n ) represents the sum of the ASCII code values ​​of all characters in the nth word, and TotalLen = Len(P1) + ... + Len(P n ). VAL(P n ) = , the ASCII (C i ) represents the character C i The ASCII code value of ... indicates that the intermediate object description is omitted.

[0051] Step (3), when the two parameters are compared, if TotalLen is equal, then continue; if not equal, then the two parameters are not equal and the comparison ends.

[0052] Furthermore, continue to compare whether Len(P1) is equal. If they are equal, continue to compare whether VAL(P1) is equal. If they are not equal, the two parameters are inconsistent and the comparison ends.

[0053] Repeat the above comparisons in sequence, only Len(P n ).VAL(P n ) comparison is completed and they are equal, then the two arguments are exactly equal.

[0054] Furthermore, the above word set {P1,...,P n The object P in} does not contain a multi-instance value {i}.

[0055] Step 4: After the network management platform completes the scoring of the model parameters reported by the base station, it outputs the parameter adaptation report corresponding to the base station based on the score, completing the final adaptation analysis. The parameter adaptation report is preferably an Excel spreadsheet summarizing the pass rate.

[0056] The base station data model analysis system based on the TR069 protocol according to an embodiment of the present invention includes:

[0057] Construction unit: defines key information based on the full set of data model parameters and constructs corresponding database forms according to the key information;

[0058] Acquisition unit: obtains corresponding data model parameters from the base station and updates the database table according to the acquired parameters;

[0059] Analysis unit: Analyze the updated database form and obtain the corresponding score;

[0060] Output unit: Outputs the parameter adaptation report corresponding to the base station based on the score to complete the final adaptation analysis.

[0061] As an embodiment, the construction unit constructs the database form EvaluationRulesTable according to the following steps: As an embodiment, the construction unit constructs the database form EvaluationRulesTable according to the following steps: As an embodiment, the construction unit constructs the database form EvaluationRulesTable according to the following steps:

[0062] Based on the data model of TR-181 specification, the key parameter indicator information set {KeyParInfo1, ...,KeyParInfo i , ...,KeyParInfo N}, where KeyParInfo i Contains ParName (parameter name), ParImp (importance), ParRWPer (read and write permissions), ParType (data type), ActParRWPer (actual read and write permissions), ActParType (actual data type) and ActParValue (actual parameter value), N is the maximum number of entries in the set, i∈N;

[0063] Create a database table EvaluationRulesTable and set {KeyParInfo1, ...,KeyParInfo i , ...,KeyParInfoN} is written into EvaluationRulesTable, and the database form EvaluationRulesTable is created as a set of N records {DBRuleInfo1, ...,DBRuleInfo j , ...,DBRuleInfo N}. N is the maximum number of entries in the set, j∈N.

[0064] As an embodiment, the acquisition unit updates the database table according to the following steps:

[0065] Send the GetParameterNames RPC message to the base station, the base station returns the GetParameterNamesResponse RPC message, and obtain the key information set {PropertInfo1, ...,PropertInfo k , ...,PropertInfo M}, M is the maximum number of entries in the set, k∈M;

[0066] The network management platform sends the GetParameterValues ​​RPC message to the base station, and the base station returns the GetParameterValuesResponse RPC message. The network management platform obtains the key information set {SubParInfo1, ...,SubParInfo x , ...,SubParInfo S}, S is the maximum number of entries in the set, x∈S;

[0067] Set {PropertInfo1, ...,PropertInfo k , ...,PropertInfo M} and the collection {SubParInfo1, ...,SubParInfo x , ...,SubParInfo S} is written to the database form EvaluationRulesTable:

[0068] (1) Traverse {PropertInfo1, ...,PropertInfo k , ...,PropertInfo M Each PropertInfo in k If PropertInfo k. Pro_ParName finds the corresponding record DBRuleInfo in EvaluationRulesTable j , namely DBRuleInfo j. ParName equals PropertInfo k. Pro_ParName, then DBRuleInfo j Update data and set DBRuleInfo j. ActParRWPer=PropertInfo k. Pro_ParRWPer;

[0069] (2) Traverse {SubParInfo1, ...,SubParInfo x , ...,SubParInfo S Each SubParInfo in x If SubParInfo x .SubPar_ParName finds the corresponding record DBRuleInfo in EvaluationRulesTable j , namely DBRuleInfo j. ParName equals SubParInfo x. SubPar_ParName, then DBRuleInfo j Update data and set DBRuleInfo j. ActParType= SubParInfo x. SubPar_ParType, DBRuleInfo j. ActParValue= SubParInfo x. SubPar_ParValue.

[0070] As an embodiment, the analysis unit performs analysis according to the following steps:

[0071] Traverse the database table EvaluationRulesTable collection {DBRuleInfo1, ...,DBRuleInfo j , ...,DBRuleInfo N},

[0072] If DBRuleInfo j. If the value of ActParValue is null, the record is judged as failed;

[0073] If DBRuleInfo j. The value of ActParValue is not null, and DBRuleInfo j. ParRWPer equals DBRuleInfo j. ActParRWPer, while DBRuleInfo j. ParType equals DBRuleInfo j. ActParType, the record is judged as passed;

[0074] According to DBRuleInfo j. The types of ParImp were scored separately;

[0075] After scoring each record, the corresponding scoring result is added to the ActParValue field of the record, with P for passing and F for failing.

[0076] As an embodiment, the analysis unit performs scoring according to the following steps:

[0077] According to DBRuleInfo j. ParImp = A or B is scored according to the following three dimensions, where A is the key parameter and B is the general parameter;

[0078] Dimension 1: DBRuleInfo j. ParImp = A parameter to be scored: DBRuleInfo j. ParImp = the number of parameters passed by A divided by DBRuleInfo j. ParImp = the total number of parameters corresponding to A, multiplied by 100, the resulting value is the score;

[0079] Dimension 2: DBRuleInfo j. ParImp = B's parameters to be scored: DBRuleInfo j.ParImp = the number of parameters passed by B divided by DBRuleInfo j. ParImp = the total number of parameters in B, multiplied by 100, the resulting value is the score;

[0080] Dimension 3: Score the overall parameters: the number of all passed parameters / total number of parameters * 100.

[0081] As an implementation method, in order to facilitate comparison of parameters, it is determined that DBRuleInfo j .ParName and SubParInfo x .SubPar_ParName, PropertyInfo k .Pro_ParName are equal, the analysis unit quickly compares the parameters DBRuleInfoj.ParName with SubParInfox.SubPar_ParName and PropertInfo according to the following steps k .Pro_ParName is equal:

[0082] Step (1): Split the parameter name with “.” to get the word set {P1,...,P n}. Where n is the number of words segmented, and P represents the word objects in the set.

[0083] Step (2), for the word set {P1,...,P n}, calculate the character length Len and ASCII value of each word P in the set {P1,...,P n}, and then combine them with "-" to form MA = TotalLen-Len(P1).VAL(P1)-Len(P2).VAL(P2)...-Len(P n ).VAL(P n ). Wherein, the Len(P n ) represents the length of the nth word in the word set, and the VAL(P n ) represents the sum of the ASCII code values ​​of all characters in the nth word, and TotalLen = Len(P1) + ... + Len(P n ). VAL(P n ) = , the ASCII (C i ) represents the character C i The ASCII code value of ... indicates that the intermediate object description is omitted.

[0084] Step (3), when the two parameters are compared, if TotalLen is equal, then continue; if not equal, then the two parameters are not equal and the comparison ends.

[0085] In Example 1, a corresponding database table is constructed based on key information, that is, a database table named EvaluationRulesTable is added to the data, as shown in Table 1:

[0086]

[0087] The first line is the title bar of the database form. Id represents the serial number, ParName represents the parameter name, ParImp represents the importance, ParRWPer represents the read and write permissions, ParType represents the data type, ActParRWPer represents the actual read and write permissions, ActParType represents the actual data type, and ActParValue represents the actual parameter value. The second line onwards contains the specific data content in the database form.

[0088] For example, the data of ID = 1 and 2 is constructed based on the key information parameters in the TR-181 data model.

[0089] The row with ID=1 indicates that the parameter name is Device.SoftwareCtrl.SystemBackupVersion, its importance is A (critical parameter), its read and write permissions are R, and its data type is string(64).

[0090] The data row with ID = 2 indicates that the parameter name is Device.SoftwareCtrl.ActivateEnable, its importance is B (general parameter), the read and write permission is RW, and the data type is boolean.

[0091] The values ​​of ActParRWPer, ActParType, and ActParValue are all NULL. The network management system must interact with the base station and then write corresponding values ​​based on the corresponding parameter attributes in the message information actually reported by the base station. This example only uses partial data to display key information.

[0092] In embodiment 2, the network management platform obtains corresponding data model parameters from the base station:

[0093] 1. The network management platform sends a GetParameterNames RPC message to the base station. The interaction message is as follows:

[0094] <SOAP-ENV:Envelope

[0095] xmlns:SOAP-ENV="http: / / schemas.xmlsoap.org / soap / envelope / "

[0096] xmlns:SOAP-ENC="http: / / schemas.xmlsoap.org / soap / encoding / "

[0097] xmlns:cwmp="urn:dslforum-org:cwmp-1-0"

[0098] xmlns:xsd="http: / / www.w3.org / 2001 / XMLSchema"

[0099] xmlns:xsi="http: / / www.w3.org / 2001 / XMLSchema-instance">

[0100] <soap-env:header>

[0101] <cwmp:id soap-env:mustunderstand="1">b986282f972f41f4b18bbc95125000ea< / cwmp:id>

[0102] <cwmp:nomorerequests> 0< / cwmp:nomorerequests>

[0103] < / soap-env:header>

[0104] <soap-env:body>

[0105] <cwmp:getparameternames>

[0106] <parameterpath>Device.< / parameterpath>

[0107] <nextlevel> 0< / nextlevel>

[0108] < / cwmp:getparameternames>

[0109] < / soap-env:body>

[0110]

[0111] This message indicates that the network management platform obtains all parameter names from the base station. When the base station receives this message, it returns the corresponding parameter information to the network management platform via the GetParameterNamesResponse message. See below:

[0112] <?xml version="1.0" encoding="UTF-8" standalone="no"?>

[0113] <soap_env:Envelope xmlns:soap_env="http: / / schemas.xmlsoap.org / soap / envelope / " xmlns:soap_enc="http: / / schemas.xmlsoap.org / soap / encoding / " xmlns:xsd="http: / / www.w3.org / 2001 / XMLSchema" xmlns:xsi="http: / / www.w3.org / 2001 / XMLSchema-instance" xmlns:cwmp="urn:dslforum-org:cwmp-1-0">

[0114] <soap_env:Header>

[0115] <cwmp:id soap_env:mustunderstand="1">b986282f972f41f4b18bbc95125000ea< / cwmp:id>

[0116] < / soap_env:Header>

[0117] <soap_env:Body>

[0118] <cwmp:getparameternamesresponse>

[0119] <parameterlist soap_enc:arraytype="cwmp:ParameterInfoStruct

[8444] ">

[0120] <parameterinfostruct>

[0121] <name>Device.SoftwareCtrl.SystemBackupVersion< / name>

[0122] <writable> 0< / writable>

[0123] < / parameterinfostruct> ......

[0124] <parameterinfostruct>

[0125] <name>Device.SoftwareCtrl.ActivateEnable< / name>

[0126] <writable> 1< / writable>

[0127] < / parameterinfostruct>

[0128] < / parameterlist>

[0129] < / cwmp:getparameternamesresponse>

[0130] < / soap_env:Body>

[0131] < / soap_env:Envelope>

[0132] The read / write properties of the parameter Device.SoftwareCtrl.SystemBackupVersion are both 0, and the read / write properties of Device.SoftwareCtrl.ActivateEnable are both 1 (0 represents R, 1 represents W). After receiving this message, the network management platform writes it to the database table (the read / write properties in the above example need to be converted to the corresponding R / W for writing). In the above example, "..." indicates that other detailed parameters are omitted, and only some parameters are listed for clarification.

[0133] 2. The network management platform sends a GetParameterValues ​​RPC message to the base station. The interaction message is as follows:

[0134] <?xml version="1.0" encoding="UTF-8" standalone="no"?><soap_env:Envelope xmlns:soap_env="http: / / schemas.xmlsoap.org / soap / envelope / " xmlns:soap_enc="http: / / schemas.xmlsoap.org / soap / encoding / " xmlns:xsd="http: / / www.w3.org / 2001 / XMLSchema" xmlns:xsi="http: / / www.w3.org / 2001 / XMLSchema-instance" xmlns:cwmp="urn:dslforum-org:cwmp-1-0">

[0135] <soap_env:Header>

[0136] <cwmp:id soap_env:mustunderstand="1">Id:com.ctran.ums.acs.GetParameterValues.1743990712423.9J13N2< / cwmp:id>

[0137] < / soap_env:Header>

[0138] <soap_env:Body>

[0139] <cwmp:getparametervalues>

[0140] <parameternames soap_enc:arraytype="xsd:string[1]">

[0141] <string>Device.< / string>

[0142] < / parameternames>

[0143] < / cwmp:getparametervalues>

[0144] < / soap_env:Body>

[0145] < / soap_env:Envelope>

[0146] The network management platform obtains parameter information supported by the base station by carrying the parameter Device. in the message sent to the base station.

[0147] After receiving this message, the base station returns all the parameters supported by the base station to the network management platform through the GetParameterValuesResponse message. The interaction message is as follows:

[0148] <?xml version="1.0" encoding="UTF-8" standalone="no"?>

[0149] <soap_env:Envelope xmlns:soap_env="http: / / schemas.xmlsoap.org / soap / envelope / " xmlns:soap_enc="http: / / schemas.xmlsoap.org / soap / encoding / " xmlns:xsd="http: / / www.w3.org / 2001 / XMLSchema" xmlns:xsi="http: / / www.w3.org / 2001 / XMLSchema-instance" xmlns:cwmp="urn:dslforum-org:cwmp-1-0">

[0150] <soap_env:Header>

[0151] <cwmp:id soap_env:mustunderstand="1">Id:com.ctran.ums.acs.GetParameterValues.1743990712423.9J13N2< / cwmp:id>

[0152] < / soap_env:Header>

[0153] <soap_env:Body>

[0154] <cwmp:getparametervaluesresponse>

[0155] <parameterlist soap_enc:arraytype="cwmp:ParameterValueStruct

[6965] ">

[0156] <parametervaluestruct>

[0157] <name>Device.SoftwareCtrl.SystemBackupVersion< / name>

[0158] <value xsi:type="xsd:string（64）">v5.0.10.a< / value>

[0159] < / parametervaluestruct> ......

[0160] <parametervaluestruct>

[0161] <name>Device.SoftwareCtrl.ActivateEnable< / name>

[0162] <value xsi:type="xsd:boolean"> 0< / value>

[0163] < / parametervaluestruct>

[0164] < / parameterlist>

[0165]

[0166] < / soap_env:Body>

[0167] < / soap_env:Envelope>

[0168] In the above message, the value of the parameter Device.SoftwareCtrl.SystemBackupVersion is v5.0.10.a, of type string(64). The value of the parameter Device.SoftwareCtrl.ActivateEnable is 0 (0 represents false, 1 represents true), of type boolean. The "..." indicates that other parameters in the intermediate process are omitted. The above message only displays some key information.

[0169] After the above interaction, the corresponding database form is updated as shown in Table 2:

[0170] In Table 2, the parameter check items with Id = 1 and 2 pass the check if the value of their ActParValue is not empty && (ParRWPer == ActParRWPer) && (ParType == ActParType).

[0171] The results corresponding to the parameters in the update database form are shown in Table 3: Example 3: Parameter items that fail the network management platform database check:

[0172] In Table 4, the parameter items with IDs 3 and 4 fail the check. When ID = 3, the check fails because ActParValue is NULL (the base station device has not reported this parameter).

[0173] When Id = 4, the parameter corresponding to this Id also fails the check because ParType (value is string(64)) and ActParType (value is dateTime) are not equal.

[0174] Example 4: Analyze and score database forms:

[0175] Taking the table in Example 3 as an example, scoring is performed based on three dimensions.

[0176] Dimension 1: Score the parameters of ParImp = A by dividing the number of passed parameters of ParImp = A by the total number of corresponding parameters in ParImp = A by 100. In the table, the Class A parameters are the two parameters with Id = 1 and Id = 4. The parameter with Id = 1 passes the check, while the parameter with Id = 4 fails the check. Therefore, the score = 1 / 2 * 100 = 50 points.

[0177] Dimension 2: Score the parameters of ParImp = B by dividing the number of passed parameters of ParImp = B by the total number of corresponding parameters in ParImp = B * 100. The Class B parameters in the table are two parameters with Id = 2 and Id = 3. The parameter with Id = 2 passed the check, and the parameter with Id = 3 failed the check. Therefore, the score = 1 / 2 * 100 = 50 points.

[0178] Dimension 3: Score the overall parameters by dividing the number of passed parameters by the total number of parameters * 100. In the table, there are 2 passed parameters (Id = 1 and Id = 2), and the total number of parameters is 4, so the score = 2 / 4 * 100 = 50 points.

[0179] For the sake of convenience, the above examples do not include the full data model parameter samples.

[0180] Example 5, a summary table of parameter scores is shown in Table 5, which is an EXCEL table summarizing the pass rates.

[0181] The number specified in the data model is the number of parameters in the corresponding dimension, and the number of base station parameters actually conforming is the number of parameters that passed the corresponding dimension. The score indicates the passing evaluation. A higher score indicates better base station parameter adaptability, while a lower score indicates poorer adaptability. The result indicates whether the parameters in that dimension passed or failed. If a dimension fails, you can analyze the adaptation details, which are shown in Table 4.

[0182] Example 6, comparison of multiple instance parameters:

[0183] A normal parameter name is a tree-structured name consisting of word characters and "". A multi-instance parameter name is a parameter that contains two ".". followed by a number. For example:

[0184] ParName = Device.DeviceInfo.MU.{i}.ManufacturerOUI, where {i} represents the number of the multi-instance parameter, ranging from 1 to 65535. The calculation process of the quick identification code MA is as follows:

[0185] The character set separated by "." is {Device, DeviceInfo, MU, ManufacturerOUI}, where {i} represents a multi-instance number and is therefore not included in the calculation.

[0186] Calculate the sum of the corresponding character length Len and ASCII value in the character set, where

[0187] Len(Device) = 6, VAL(Device) = 68 + 101+118+105+99+101 = 592;

[0188] Len(DeviceInfo) = 10, VAL(DeviceInfo) = 592+73+110+102+111=988;

[0189] Len(MU) = 2, VAL(MU) = 77+85 = 162;

[0190] Len(ManufacturerOUI) = 15, VAL(ManufacturerOUI) = 77+97+110+117+102+97+99+116+117+114+101+114+79+85+73 = 1498;

[0191] TotalLen= Len(Device) + Len(DeviceInfo) + Len(MU) + Len(ManufacturerOUI) = 6+10+2+15 = 33;

[0192] Then the MA of ParName=Device.DeviceInfo.MU.{i}.ManufacturerOUI = 33-6.592-10.988-2.162-15.1498.

[0193] When the multi-instance parameter of SubPar_ParName = Device.DeviceInfo.MU.3.ManufacturerOUI is compared with ParName = Device.DeviceInfo.MU.{i}.ManufacturerOUI, the two are exactly equal through the above comparison process, without the multi-instance number involved in the comparison, as expected.

[0194] When Pro_ParName = Device.DeviceInfo.MU.2.ProductClass, the character set separated by "." is {Device, DeviceInfo, MU, ProductClass}, where

[0195] Len(Device) = 6, VAL(Device) = 68 + 101+118+105+99+101 = 592;

[0196] Len(DeviceInfo) = 10, VAL(DeviceInfo) = 592+73+110+102+111=988;

[0197] Len(MU) = 2, VAL(MU) = 77+85 = 162;

[0198] Len(ProductClass) = 12, VAL(ProductClass) = 80+114+111+100+117+99+116+67+108+97+115+115 = 1239;

[0199] TotalLen = Len(Device) + Len(DeviceInfo) + Len(MU) + Len(ProductClass) = 6+10+2+12 = 30;

[0200] The MA of Pro_ParName = Device.DeviceInfo.MU.2.ProductClass = 30-6.592-10.988-2.162-12.1239 is not equal to the MA of ParName = Device.DeviceInfo.MU.{i}.ManufacturerOUI = 33-6.592-10.988-2.162-15.1498 when comparing the first key information (33 and 30). Therefore, the two are directly inconsistent and the comparison ends.

[0201] Compared with the common parameter name equality judgment method, this method of the present invention not only eliminates the need to compare multiple instance numbers {i}, but also shortens the character comparison process. The total parameter length and the length of a single word are calculated to obtain the corresponding numerical value and ASCII code value, thereby improving comparison efficiency.

[0202] While embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions, and variations may be made to these embodiments without departing from the principles and spirit of the invention, and that the scope of the invention is defined by the appended claims and their equivalents.< / cwmp:getparametervaluesresponse>

Claims

1. A base station data model analysis method based on the TR069 protocol, characterized in that: include: Step 1: The network management platform defines key information based on the full set of data model parameters and constructs a corresponding database form based on the key information; Step 2: The network management platform obtains the corresponding data model parameters from the base station and updates the database table according to the obtained parameters; Step 3: The network management platform analyzes the updated database form and obtains the corresponding score; Step 4: The network management platform outputs a parameter adaptation report corresponding to the base station based on the score, completing the final adaptation analysis; In step 3, analysis is performed according to the following steps: Traverse the database table EvaluationRulesTable constructed by the network management platform in step 1, wherein the database table EvaluationRulesTable is a set {DBRuleInfo1, ..., DBRuleInfoj, ..., DBRuleInfoN} containing N records, where j∈N; If the value of DBRuleInfoj.ActParValue is null, the record is judged as failed; If the value of DBRuleInfoj.ActParValue is not null, and DBRuleInfoj.ParRWPer is equal to DBRuleInfoj.ActParRWPer, and DBRuleInfoj.ParType is equal to DBRuleInfoj.ActParType, then the record is judged to have passed; Score according to the type of DBRuleInfoj.ParImp; After scoring each record, the corresponding score result is added to the ActParValue field of the record, with P for passing and F for failing. In step 3, scoring is performed according to the following steps: According to DBRuleInfoj.ParImp = A or B, score is given according to the following three dimensions, where A is a key parameter and B is a general parameter; Dimension 1: Score the parameters of DBRuleInfoj.ParImp = A: Divide the number of passed parameters of DBRuleInfoj.ParImp = A by the total number of corresponding parameters in DBRuleInfoj.ParImp = A, and multiply by 100. The resulting value is the score; Dimension 2: Score the parameters of DBRuleInfoj.ParImp = B: Divide the number of passed parameters of DBRuleInfoj.ParImp = B by the total number of corresponding parameters in DBRuleInfoj.ParImp = B, and multiply by 100. The resulting value is the score; Dimension 3: Score the overall parameters: the number of all passed parameters / total number of parameters * 100.

2. The base station data model analysis method based on the TR069 protocol as claimed in claim 1, wherein In step 1, build the database table EvaluationRulesTable according to the following steps: Based on the data model of TR-181, the network management platform divides the key parameter indicator information set {KeyParInfo1,...,KeyParInfo i ,...,KeyParInfo N }, where KeyParInfo i Contains ParName parameter name, ParImp importance, ParRWPer read and write permissions, ParType data type, ActParRWPer actual read and write permissions, ActParType actual data type and ActParValue actual parameter value, N is the maximum number of entries in the key parameter indicator information set, i∈N; The network management platform creates a database table EvaluationRulesTable and sets {KeyParInfo1,...,KeyParInfo i ,...,KeyParInfo N } is written into EvaluationRulesTable, and the database form EvaluationRulesTable is created as a set of N records {DBRuleInfo1,...,DBRuleInfo j ,...,DBRuleInfo N }, j∈N.

3. The base station data model analysis method based on TR069 protocol as claimed in claim 2, wherein In step 2, update the database table according to the following steps: The network management platform sends the GetParameterNames RPC message to the base station, and the base station returns the GetParameterNamesResponse RPC message. The network management platform obtains the key information set {PropertInfo1,...,PropertInfo k ,...,PropertInfo M }, M is the maximum number of entries in the set, k∈M; The network management platform sends the GetParameterValues ​​RPC message to the base station, and the base station returns the GetParameterValuesResponse RPC message. The network management platform obtains the key information set {SubParInfo1,...,SubParInfo x ,...,SubParInfo S }, S is the maximum number of entries in the set, x∈S; Set {PropertInfo1,...,PropertInfo k ,...,PropertInfo M } and the set {SubParInfo1,...,SubParInfo x ,...,SubParInfo S } is written to the database form EvaluationRulesTable: (1) Traverse {PropertInfo1,...,PropertInfo k ,...,PropertInfo M Each PropertInfo in k If PropertInfo k. Pro_ParName finds the corresponding record DBRuleInfo in EvaluationRulesTable j , namely DBRuleInfo j. ParName equals PropertInfo k. Pro_ParName, then DBRuleInfo j Update data and set DBRuleInfo j. ActParRWPer=PropertInfo k. Pro_ParRWPer; (2) Traverse {SubParInfo1,...,SubParInfo x ,...,SubParInfo S Each SubParInfo in x If SubParInfo x .SubPar_ParName finds the corresponding record DBRuleInfo in EvaluationRulesTable j , namely DBRuleInfo j. ParName equals SubParInfo x. SubPar_ParName, then DBRuleInfo j Update data and set DBRuleInfo j. ActParType= SubParInfo x. SubPar_ParType, DBRuleInfo j. ActParValue= SubParInfo x. SubPar_ParValue.

4. A base station data model analysis system based on TR069 protocol, characterized in that: include: Construction unit: defines key information based on the full set of data model parameters and constructs corresponding database forms according to the key information; Acquisition unit: obtains corresponding data model parameters from the base station and updates the database table according to the acquired parameters; Analysis unit: Analyze the updated database form and obtain the corresponding score; Output unit: Outputs the parameter adaptation report corresponding to the base station according to the score and completes the final adaptation analysis; The analysis unit performs analysis according to the following steps: Traverse the database table EvaluationRulesTable constructed by the construction unit, the database table EvaluationRulesTable is a set of N records {DBRuleInfo1,...,DBRuleInfo j ,...,DBRuleInfo N }, j∈N; If the value of DBRuleInfoj.ActParValue is null, the record is judged as failed; If the value of DBRuleInfoj.ActParValue is not null, and DBRuleInfoj.ParRWPer is equal to DBRuleInfoj.ActParRWPer, and DBRuleInfoj.ParType is equal to DBRuleInfoj.ActParType, then the record is judged to have passed; Score according to the type of DBRuleInfoj.ParImp; After scoring each record, the corresponding score result is added to the ActParValue field of the record, with P for passing and F for failing. The analysis units are scored according to the following steps: According to DBRuleInfo j. ParImp = A or B is scored according to the following three dimensions, where A is the key parameter and B is the general parameter; Dimension 1: DBRuleInfo j. ParImp = A parameter to be scored: DBRuleInfo j. ParImp = the number of parameters passed by A divided by DBRuleInfo j. ParImp = the total number of parameters corresponding to A, multiplied by 100, the resulting value is the score; Dimension 2: DBRuleInfo j. ParImp = B's parameters to be scored: DBRuleInfo j. ParImp = the number of parameters passed by B divided by DBRuleInfo j. ParImp = the total number of parameters in B, multiplied by 100, the resulting value is the score; Dimension 3: Score the overall parameters: the number of all passed parameters / total number of parameters * 100.

5. The base station data model analysis system based on TR069 protocol as claimed in claim 4, characterized in that, The construction unit builds the database table EvaluationRulesTable according to the following steps: Based on the data model of TR-181, the key parameter indicator information set {KeyParInfo1,...,KeyParInfo i ,...,KeyParInfo N }, where KeyParInfo i Contains ParName parameter name, ParImp importance, ParRWPer read and write permissions, ParType data type, ActParRWPer actual read and write permissions, ActParType actual data type and ActParValue actual parameter value, N is the maximum number of entries in the key parameter indicator information set, i∈N; Create a database table EvaluationRulesTable and set {KeyParInfo1,...,KeyParInfo i ,...,KeyParInfo N } is written into EvaluationRulesTable, and the database form EvaluationRulesTable is created as a set of N records {DBRuleInfo1,...,DBRuleInfo j ,...,DBRuleInfo N }, j∈N.

6. The base station data model analysis system based on TR069 protocol as claimed in claim 5, characterized in that The acquisition unit updates the database table according to the following steps: The network management platform sends the GetParameterNames RPC message to the base station, and the base station returns the GetParameterNamesResponse RPC message. The key information set {PropertInfo1,...,PropertInfo k ,...,PropertInfo M }, M is the maximum number of entries in the set, k∈M; The network management platform sends the GetParameterValues ​​RPC message to the base station, and the base station returns the GetParameterValuesResponse RPC message. The network management platform obtains the key information set {SubParInfo1,...,SubParInfo x ,...,SubParInfo S }, S is the maximum number of entries in the set, x∈S; Set {PropertInfo1,...,PropertInfo k ,...,PropertInfo M } and the set {SubParInfo1,...,SubParInfo x ,...,SubParInfo S } is written to the database form EvaluationRulesTable: (1) Traverse {PropertInfo1,...,PropertInfo k ,...,PropertInfo M Each PropertInfo in k If PropertInfo k. Pro_ParName finds the corresponding record DBRuleInfo in EvaluationRulesTable j , namely DBRuleInfo j. ParName equals PropertInfo k. Pro_ParName, then DBRuleInfo j Update data and set DBRuleInfo j. ActParRWPer=PropertInfo k. Pro_ParRWPer; (2) Traverse {SubParInfo1,...,SubParInfo x ,...,SubParInfo S Each SubParInfo in x If SubParInfo x .SubPar_ParName finds the corresponding record DBRuleInfo in EvaluationRulesTable j , namely DBRuleInfo j. ParName equals SubParInfo x. SubPar_ParName, then DBRuleInfo j Update data and set DBRuleInfo j. ActParType= SubParInfo x. SubPar_ParType, DBRuleInfo j. ActParValue= SubParInfo x. SubPar_ParValue.

Images