Base station data model analysis method and system based on TR069 protocol
By building a database form and obtaining base station parameters for scoring, the parameter adaptation problem when the base station adapts to the network management platform is solved, and efficient parameter adaptation evaluation and analysis is achieved.
Patent Information
- Application Number
- CN202510773392.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-11
- Publication Date
- 2025-07-11
- Estimated Expiration
- 2045-06-11
AI Technical Summary
When base stations adapt to network management platforms, the existing technology requires a lot of manpower to deal with problems such as parameter integrity, parameter read and writeability, and parameter value range, resulting in inefficiency and lack of effective means to conduct one-time inspections.
Through the network management platform, we build a database form based on the parameters of the full data model, obtain base station parameters, update and analyze the database form, output parameter adaptation reports, and realize the scoring and analysis of parameter adaptation.
It realizes that the base station adaptation status is understood at one time before the network management platform is managed, and the adaptation status is displayed through classified scoring, which facilitates users to comprehensively analyze the parameter adaptation status of the base station and the network management platform.
Smart Images

Figure CN120302309A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of communication technologies, and in particular, to a method and system for analyzing a base station data model based on the TR069 protocol. Background Art
[0002] TR069 is a communication protocol for communication between a CPE (Customer Premises Equipment) and an ACS (AutoConfiguration Server). Currently, 5G small base station network management systems (an ACS system, abbreviated as: network management platform, network management, or ACS) generally use the TR069 protocol to manage small base stations (a type of CPE), and the data model uses TR-181. When the data model parameters (abbreviated as parameters) of a small base station are adapted to the network management, a large amount of manpower is often spent repeatedly processing problems such as parameter integrity, parameter read / write ability, and parameter value range, resulting in low efficiency; currently, before the base station is adapted to the network management platform, there is no effective means to check the data model parameters on the device side at one time. Summary of the Invention
[0003] The technical problem to be solved by the embodiments of the present invention is to provide a method and system for analyzing a base station data model based on the TR069 protocol to solve the problem of data model parameter verification and adaptation when the base station is adapted to the network management platform.
[0004] To solve the above technical problem, an embodiment of the present invention provides a method for analyzing a base station data model based on the TR069 protocol, including: 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; 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 a corresponding score; Step 4: The network management platform outputs a parameter adaptation situation report corresponding to the base station according to the score to complete the final adaptation analysis.
[0005] Correspondingly, an embodiment of the present invention further provides a system for analyzing a base station data model based on the TR069 protocol, including: A construction unit: defines key information based on the full set of data model parameters and constructs a corresponding database form according to the key information; An acquisition unit: obtains the corresponding data model parameters from the base station and updates the database form according to the obtained parameters; An analysis unit: analyzes the updated database form to obtain a corresponding score; Output unit: According to the score, output the parameter adaptation situation report corresponding to the base station to complete the final adaptation analysis.
[0006] The beneficial effects of the present invention are as follows: 1. Before the network management platform manages the device, through the prefabricated database form scoring system, directly score the information of the parameter adaptation situation, so that the user can understand the situation of the base station adapting to the network management at one time.
[0007] 2. The present invention classifies the parameters for scoring and displays the scoring situation based on three different dimensions, so that the user can more comprehensively understand the situation of the base station adapting to the network management; and display whether each parameter adaptation situation passes, which is convenient for the user to analyze the specific adaptation situation. Description of the Drawings
[0008] Figure 1 It is a schematic flowchart of the base station data model analysis method based on the TR069 protocol in an embodiment of the present invention. Specific Embodiments
[0009] It should be noted that, without conflict, the embodiments in the present application and the features in the embodiments can be combined with each other. The present invention will be further described in detail below with reference to the drawings and specific embodiments.
[0010] Please refer to Figure 1 , the base station data model analysis method based on the TR069 protocol in the embodiment of the present invention is applied to the network management platform, including steps 1 to 4.
[0011] 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.
[0012] The network management platform divides the key parameter index information set {KeyParInfo1, ..., KeyParInfo i , ..., KeyParInfo N} based on the data model of the TR-181 specification, where KeyParInfo i includes ParName (parameter name), ParImp (importance), ParRWPer (read / write permission), ParType (data type), ActParRWPer (actual read / write permission), ActParType (actual data type), and ActParValue (actual parameter value).
[0013] The ParName (parameter name) is a string in a tree-like structure. The ParImp (importance) is divided into two categories, A and B. Category A are critical parameters, and Category B are general parameters. The ParRWPer (read / write permission) includes R (read permission), W (write permission), and RW (read / write permission). The ParType (data type) refers to the format and value range of the parameter value. The term "actual" means the actual parameter information reported by the base station after the network management platform interacts with the base station. N is the maximum number of entries in this set, that is, the maximum number of data model parameters. i is the subscript number of any object in {KeyParInfo1, ...,KeyParInfo i , ...,KeyParInfo N}, where 1 ≤ i ≤ N. The KeyParInfo i refers to any object in {KeyParInfo1, ...,KeyParInfo i , ...,KeyParInfo N}.
[0014] The network management platform creates a database form EvaluationRulesTable and writes the information of {KeyParInfo1, ...,KeyParInfo i , ...,KeyParInfo N} into EvaluationRulesTable in sequence. The writing method is as follows: Traverse each record in {KeyParInfo1, ...,KeyParInfo i , ..., KeyParInfo N}, and write each {KeyParInfo i. ParName, KeyParInfo i. ParImp, KeyParInfo i. ParRWPer, KeyParInfo i. ParType, KeyParInfo i. ActParRWPer, KeyParInfo i. ActParType, KeyParInfo i.The information of {ActParValue} is written into the database as a record. Among them, KeyParInfo i. ActParRWPer, KeyParInfo i. ActParType and KeyParInfo i. The value of ActParValue is NULL (null value), and the corresponding value needs to be filled in after actual interaction with the base station.
[0015] After the above operations are completed, the database form EvaluationRulesTable contains a set of N records, identified as {DBRuleInfo1, ..., DBRuleInfo j , ..., DBRuleInfo N} set, where N is the maximum number of entries in this set. The j is the subscript number of any object in EvaluationRulesTable, 1 ≤ j ≤ N. The DBRuleInfo j refers to any object in EvaluationRulesTable. Among them, each record DBRuleInfo j contains ParName (parameter name), ParImp (importance), ParRWPer (read / write permission), ParType (data type), ActParRWPer (actual read / write permission), ActParType (actual data type), and ActParValue (actual parameter value).
[0016] 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.
[0017] As an implementation, the network management platform sends an RPC message of GetParameterNames to the base station, and the base station returns an RPC message of GetParameterNamesResponse. The network management platform obtains the key information set {PropertInfo1, ..., PropertInfo k , ..., PropertInfo M} from the RPC message returned by the base station, where M is the maximum number of entries in this set.
[0018] The k is {PropertInfo1, ..., PropertInfo k , ..., PropertInfo M The subscript number of any object in}, where 1 ≤ k ≤ M.
[0019] The said PropertInfo K Refers to any object in the set {PropertInfo1, ..., PropertInfo k , ..., PropertInfo M}, which contains Pro_ParName (parameter name) and Pro_ParRWPer (read / write permission) in the base station reported data model parameters.
[0020] The network management platform sends an RPC message of GetParameterValues to the base station, and the base station returns an RPC message of GetParameterValuesResponse. The network management platform obtains the key information set {SubParInfo1, ..., SubParInfo x , ..., SubParInfo S} from the RPC message returned by the base station. The said S is the maximum number of entries in this set.
[0021] The said x is the subscript number of any object in {SubParInfo1, ..., SubParInfo x , ..., SubParInfo S}, where 1 ≤ x ≤ S.
[0022] The said SubParInfo x Refers to any object in the set {SubParInfo1, ..., SubParInfo x , ..., SubParInfo S}, which contains SubPar_ParName (parameter name), SubPar_ParType (data type), and SubPar_ParValue (parameter value) in the base station reported data model parameters.
[0023] The network management platform will set {PropertInfo1, ..., PropertInfo k , ...,PropertInfo M}, and the data in the set {SubParInfo1, ...,SubParInfo x , ...,SubParInfo S} are written into the database form EvaluationRulesTable. The writing method is as follows: (1) Traverse each PropertInfo in {PropertInfo1, ...,PropertInfo k , ...,PropertInfo M}. If the corresponding record DBRuleInfo k is found for PropertInfo k. Pro_ParName in EvaluationRulesTable j (that is, DBRuleInfo j. ParName is equal to PropertInfo k. Pro_ParName), then update the data of DBRuleInfo j , and set DBRuleInfo j. ActParRWPer = PropertInfo k. Pro_ParRWPer.
[0024] (2) Traverse each SubParInfo in {SubParInfo1, ...,SubParInfo x , ...,SubParInfo S}. If the corresponding record DBRuleInfo x is found for SubParInfo x .SubPar_ParName in EvaluationRulesTable j (that is, DBRuleInfo j. ParName is equal to SubParInfo x. SubPar_ParName), then update the data of DBRuleInfo j , and set DBRuleInfo j. ActParType = SubParInfo x.SubPar_ParType, DBRuleInfo j. ActParValue = SubParInfo x. SubPar_ParValue.
[0025] Step 3: Analyze the updated database form to obtain the corresponding score.
[0026] Traverse the set of the database form EvaluationRulesTable {DBRuleInfo1, ..., DBRuleInfo j , ..., DBRuleInfo N}; If DBRuleInfo j. ActParValue is equal to NULL, then this record is judged as not passed and feedback to the user.
[0027] If (DBRuleInfo j. ActParValue is not equal to NULL) && (DBRuleInfo j. ParRWPer is equal to DBRuleInfo j. ActParRWPer) && (DBRuleInfo j. ParType is equal to DBRuleInfo j. ActParType), that is, the value of DBRuleInfo j. ActParValue is not a null value, and DBRuleInfo j. ParRWPer is equal to DBRuleInfo j. ActParRWPer, and at the same time DBRuleInfo j. ParType is equal to DBRuleInfo j. ActParType, then this record is judged as passed.
[0028] After scoring each record, add the corresponding score result and judgment result after the ActParValue field of this record. Pass is P, not passed is F.
[0029] As an implementation manner, the scoring method is: Traverse the set of the database form EvaluationRulesTable {DBRuleInfo1, ..., DBRuleInfo j, ..., DBRuleInfo N}, according to DBRuleInfo j. ParImp = A or B is scored separately, and the scoring is divided into 3 dimensions: Dimension 1, score the parameters of DBRuleInfo j. where ParImp = A, the method is to divide the number of passed parameters of DBRuleInfo j. where ParImp = A by the total number of corresponding parameters in DBRuleInfo j. where ParImp = A * 100; Dimension 2, score the parameters of DBRuleInfo j. where ParImp = B, the method is to divide the number of passed parameters of DBRuleInfo j. where ParImp = B by the total number of corresponding parameters in DBRuleInfo j. where ParImp = B * 100; Dimension 3, score the overall parameters, the method is to divide the number of all passed parameters by the total number of parameters * 100.
[0030] As an implementation, to facilitate parameter comparison and determine whether DBRuleInfo j .ParName and SubParInfo x .SubPar_ParName, PropertInfo k .Pro_ParName are equal, the present invention quickly compares the parameters DBRuleInfoj.ParName with SubParInfox.SubPar_ParName, PropertInfo k .Pro_ParName as follows: Step (1), split the parameter names by "." to obtain a word set {P1,..., P n}. Where n is the number of split words, and P represents a word object in the set.
[0031] Step (2), calculate the character length Len and ASCII value for each word P in the word set {P1,..., P n}, and calculate the total character length TotalLen of the set {P1,..., P n}, then combine them with "-" to form MA = TotalLen - Len(P1).VAL(P1) - Len(P2).VAL(P2)... - Len(Pn ).VAL(P n ). Among them, 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. The TotalLen = Len(P1) +... + Len(P n ). VAL(P n ) = , and the ASCII(C i ) represents the ASCII code value of the character C i . The... represents the omission of the description of intermediate objects.
[0032] Step (3), when comparing two parameters, if TotalLen is equal, continue; if not, the two parameters are not equal and the comparison ends.
[0033] Furthermore, continue to compare whether Len(P1) is equal. If equal, continue to compare whether VAL(P1) is equal; if not, the two parameters are inconsistent and the comparison ends.
[0034] Repeat the above comparison in sequence. Only when the comparison of Len(P n ).VAL(P n ) is completed and equal, the two parameters are exactly equal.
[0035] Furthermore, the object P in the above word set {P1,..., P n} does not contain multi-instance values {i}.
[0036] Step 4: After the network management platform completes the parameter scoring of the base station reported data model, it outputs a parameter adaptation situation report corresponding to the base station according to the score, and completes the final adaptation analysis. The parameter adaptation situation report is preferably a summary pass rate EXCEL table.
[0037] The base station data model analysis system based on the TR069 protocol in the embodiment of the present invention includes: Construction unit: Define key information based on the full amount of data model parameters, and construct a corresponding database form according to the key information; Acquisition unit: Obtain the corresponding data model parameters from the base station, and update the database form according to the obtained parameters; Analysis unit: Analyze the updated database form to obtain the corresponding score; Output unit: Output a parameter adaptation situation report corresponding to the base station according to the score, and complete the final adaptation analysis.
[0038] As an implementation, the construction unit constructs the database form EvaluationRulesTable according to the following steps: As an implementation, the construction unit constructs the database form EvaluationRulesTable according to the following steps: As an implementation, the construction unit constructs the database form EvaluationRulesTable according to the following steps: Based on the data model of the TR-181 specification, divide the key parameter index information set {KeyParInfo1, ...,KeyParInfo i , ...,KeyParInfo N}, where KeyParInfo i includes ParName (parameter name), ParImp (importance), ParRWPer (read-write permission), ParType (data type), ActParRWPer (actual read-write permission), ActParType (actual data type), and ActParValue (actual parameter value), N is the maximum number of entries in this set, and i ∈ N; Create the database form EvaluationRulesTable, and write the information of {KeyParInfo1, ...,KeyParInfo i , ...,KeyParInfo N} into EvaluationRulesTable, and record the created database form EvaluationRulesTable as a set {DBRuleInfo1, ...,DBRuleInfo j , ...,DBRuleInfo N} containing N records. The said N is the maximum number of entries in this set, and j ∈ N.
[0039] As an implementation, the acquisition unit updates the database form according to the following steps: Send an RPC message of GetParameterNames to the base station, the base station returns an RPC message of GetParameterNamesResponse, and obtain the key information set {PropertInfo1, ...,PropertInfo k , ...,PropertInfo M}, where M is the maximum number of entries in the set, k∈M; The network management platform sends a GetParameterValues RPC message to the base station, and the base station returns a 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 collection {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 , ...,SubParInfoS Each SubParInfo in x , if SubParInfo x .SubPar_ParName finds the corresponding record DBRuleInfo in the EvaluationRulesTable j , that is, DBRuleInfo j. ParName is equal to SubParInfo x. SubPar_ParName, then update the data for DBRuleInfo j , and set DBRuleInfo j. ActParType = SubParInfo x. SubPar_ParType, DBRuleInfo j. ActParValue = SubParInfo x. SubPar_ParValue.
[0040] As an implementation, the analysis unit performs analysis according to the following steps: Traverse the set {DBRuleInfo1, ..., DBRuleInfo j , ..., DBRuleInfo N} of the database form EvaluationRulesTable, If the value of DBRuleInfo j. ActParValue is a null value, then this record is judged as not passing; If the value of DBRuleInfo j. ActParValue is not a null value, and DBRuleInfo j. ParRWPer is equal to DBRuleInfo j. ActParRWPer, and at the same time DBRuleInfo j. ParType is equal to DBRuleInfo j. ActParType, then this record is judged as passing; Score according to the type of DBRuleInfo j. ParImp respectively; After scoring each record, add the corresponding scoring result after the ActParValue field of this record, passing is P, not passing is F.
[0041] As an implementation manner, the analysis unit scores according to the following steps: According to DBRuleInfo j. ParImp = A or B is scored separately in the following three dimensions, where A is a key parameter and B is a general parameter; Dimension 1: Score the parameter of DBRuleInfo j. ParImp = A: Divide the number of passed parameters of DBRuleInfo j. ParImp = A by the total number of corresponding parameters in DBRuleInfo j. ParImp = A, and then multiply by 100. The obtained value is the score; Dimension 2: Score the parameter of DBRuleInfo j. ParImp = B: Divide the number of passed parameters of DBRuleInfo j. ParImp = B by the total number of corresponding parameters in DBRuleInfo j. ParImp = B, and then multiply by 100. The obtained value is the score; Dimension 3: Score the overall parameters: Divide the number of all passed parameters by the total number of parameters * 100.
[0042] As an implementation manner, in order to facilitate the comparison of parameters and determine whether DBRuleInfo j .ParName and SubParInfo x .SubPar_ParName, PropertInfo k .Pro_ParName are equal, the analysis unit quickly compares whether the parameter DBRuleInfoj.ParName is equal to SubParInfox.SubPar_ParName and PropertInfo k .Pro_ParName according to the following steps: Step (1), split the parameter name by "." to obtain a word set {P1,..., P n}. Where n is the number of split words, and P represents a word object in the set.
[0043] Step (2), calculate the character length Len and ASCII value for each word P in the word set {P1,..., P n}, and calculate the set {P1,..., P n}(TotalLen of all characters), and then combine them through "-" to form MA = TotalLen - Len(P1).VAL(P1) - Len(P2).VAL(P2)... - Len(P n ).VAL(P n ). Among them, 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. The TotalLen = Len(P1) +... + Len(P n ). VAL(P n ) = , and the ASCII(C i ) represents the ASCII code value of the character C i . The... represents the omission of the description of intermediate objects.
[0044] Step (3), when comparing two parameters, if TotalLen is equal, continue; if not, the two parameters are not equal and the comparison ends.
[0045] Example 1, construct a corresponding database form based on key information, that is, add a database table named EvaluationRulesTable to the data, as shown in Table 1:
[0046] Among them, the first row 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 / write permission, ParType represents the data type, ActParRWPer represents the actual read / write permission, ActParType represents the actual data type, and ActParValue represents the actual parameter value. The specific data content in the database form starts from the second row.
[0047] For example: The data with Id = 1 and 2 is a database form constructed based on the key information parameters in the TR-181 data model. Among them, The data in the row with Id = 1 indicates that the parameter name is Device.SoftwareCtrl.SystemBackupVersion, its importance is A (critical parameter), the read / write permission is R, and the data type is string(64); The data in the row with Id = 2 indicates that the parameter name is Device.SoftwareCtrl.ActivateEnable, its importance is B (general parameter), the read / write permission is RW, and the data type is boolean.
[0048] Among them, the values of ActParRWPer, ActParType, and ActParValue are all NULL. After the network management interacts with the base station, the corresponding values need to be written according to the parameter attributes in the message actually reported by the base station. This example only uses partial data to display key information.
[0049] Example 2, the network management platform obtains the corresponding data model parameters from the base station: 1. The network management platform sends an RPC message of GetParameterNames to the base station, and the interaction message is as follows: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http: / / schemas.xmlsoap.org / soap / envelope / " xmlns:SOAP-ENC="http: / / schemas.xmlsoap.org / soap / encoding / " xmlns:cwmp="urn:dslforum-org:cwmp-1-0" xmlns:xsd="http: / / www.w3.org / 2001 / XMLSchema" xmlns:xsi="http: / / www.w3.org / 2001 / XMLSchema-instance"> <soap-env:header> <cwmp:id soap-env:mustunderstand="1">b986282f972f41f4b18bbc95125000ea< / cwmp:id> <cwmp:nomorerequests> 0< / cwmp:nomorerequests> < / soap-env:header> <soap-env:body> <cwmp:getparameternames> <parameterpath>Device.< / parameterpath> <nextlevel> 0< / nextlevel> < / cwmp:getparameternames> < / soap-env:body> 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 through the GetParameterNamesResponse message. See below: <?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"> <soap_env:Header> <cwmp:id soap_env:mustunderstand="1">b986282f972f41f4b18bbc95125000ea< / cwmp:id> < / soap_env:Header> <soap_env:Body> <cwmp:getparameternamesresponse> <parameterlist soap_enc:arraytype="cwmp:ParameterInfoStruct
[8444] "> <parameterinfostruct> <name>Device.SoftwareCtrl.SystemBackupVersion< / name> <writable> 0< / writable> < / parameterinfostruct> ...... <parameterinfostruct> <name>Device.SoftwareCtrl.ActivateEnable< / name> <writable> 1< / writable> < / parameterinfostruct> < / parameterlist> < / cwmp:getparameternamesresponse> < / soap_env:Body> < / soap_env:Envelope> Among them, the read / write property of the parameter Device.SoftwareCtrl.SystemBackupVersion is 0, and the read / write property of Device.SoftwareCtrl.ActivateEnable is 1 (0 represents R, 1 represents W). After the network management platform receives this message, it writes it into the database form (in the above example, the read / write property needs 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 illustration.
[0050] 2. The network management platform sends an RPC message of GetParameterValues to the base station, and the interaction message is as follows: <?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"> <soap_env:Header> <cwmp:id soap_env:mustunderstand="1">Id:com.ctran.ums.acs.GetParameterValues.1743990712423.9J13N2< / cwmp:id> < / soap_env:Header> <soap_env:Body> <cwmp:getparametervalues> <parameternames soap_enc:arraytype="xsd:string[1]"> <string>Device.< / string> < / parameternames> < / cwmp:getparametervalues> < / soap_env:Body> < / soap_env:Envelope> In the message sent by the network management platform to the base station, the parameter information supported by the base station is obtained by carrying the parameter Device.
[0051] 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: <?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"> <soap_env:Header> <cwmp:id soap_env:mustunderstand="1">Id:com.ctran.ums.acs.GetParameterValues.1743990712423.9J13N2< / cwmp:id> < / soap_env:Header> <soap_env:Body> <cwmp:getparametervaluesresponse> <parameterlist soap_enc:arraytype="cwmp:ParameterValueStruct
[6965] "> <parametervaluestruct> <name>Device.SoftwareCtrl.SystemBackupVersion< / name> <value xsi:type="xsd:string(64)">v5.0.10.a< / value> < / parametervaluestruct> ...... <parametervaluestruct> <name>Device.SoftwareCtrl.ActivateEnable< / name> <value xsi:type="xsd:boolean"> 0< / value> < / parametervaluestruct> < / parameterlist> < / soap_env:Body> < / soap_env:Envelope> In the above message, the value of the parameter Device.SoftwareCtrl.SystemBackupVersion is v5.0.10.a, the data type is string(64), the value of the parameter Device.SoftwareCtrl.ActivateEnable is 0 (0 means false, 1 means true), and the parameter type is boolean. Among them,...... represents the omission of other parameter information in the intermediate process. The above message only shows some key information.
[0052] After the above interaction, the corresponding database form is updated as shown in Table 2: In Table 2, for the parameter check items with Id = 1 and 2, if the value of ActParValue is not empty && (ParRWPer == ActParRWPer) && (ParType == ActParType), then it passes the check.
[0053] The results corresponding to the parameters in the updated database form are shown in Table 3: Example 3, parameter items that fail the network management platform database check: In Table 4, the parameter items with Id = 3 and 4 fail the check. When Id = 3, since ActParValue is equal to NULL, it fails (the base station device has not reported this parameter); When Id = 4, since ParType (value is string(64)) and ActParType (value is dateTime) are not equal, the parameter corresponding to this Id also fails the check.
[0054] Example 4, analyze and score the database form: Taking the table in Example 3 as an example, score it in 3 dimensions.
[0055] Dimension 1: Score the parameters with ParImp = A by dividing the number of passed parameters with ParImp = A by the total number of corresponding parameters with ParImp = A and then multiplying by 100. In the table, the type-A parameters are the two parameters with Id = 1 and Id = 4. Among them, the parameter with Id = 1 passed the inspection, and the parameter with Id = 4 failed the inspection. So the score = 1 / 2 * 100 = 50 points.
[0056] Dimension 2: Score the parameters with ParImp = B by dividing the number of passed parameters with ParImp = B by the total number of corresponding parameters with ParImp = B and then multiplying by 100. In the table, the type-B parameters are the two parameters with Id = 2 and Id = 3. Among them, the parameter with Id = 2 passed the inspection, and the parameter with Id = 3 failed the inspection. So the score = 1 / 2 * 100 = 50 points.
[0057] Dimension 3: Score the overall parameters by dividing the number of all passed parameters by the total number of parameters and then multiplying by 100. In the table, the number of all passed parameters is 2 (Id = 1 and Id = 2), and the total number of parameters = 4. So the score = 2 / 4 * 100 = 50 points.
[0058] For the convenience of explanation in the above example, the quantity does not take the full amount of the data model parameter sample.
[0059] Example 5, The summary table of parameter scoring is shown in Table 5. Table 5 is an EXCEL table of the summary pass rate.
[0060] Among them, the specified quantity of the data model is the parameter quantity of the corresponding dimension, and the actual compliance quantity of the base station parameters is the quantity of the passed parameters of the corresponding dimension. The score value represents the passed evaluation. The higher the score value, the better the adaptability of the base station parameters, and the lower the score value, the worse the adaptability. The result indicates whether the parameters of this dimension pass. When the result of a certain dimension is not passed, it can be analyzed through the adaptation details, and the content is shown in Table 4.
[0061] Example 6, Comparison of multi-instance parameters: The ordinary parameter name is a tree structure name composed of word characters and ".", while the multi-instance parameter name is a parameter with numbers between two ".". For example: ParName = Device.DeviceInfo.MU.{i}.ManufacturerOUI, where {i} represents the number of the multi-instance parameter, and the range is between 1 and 65535. The calculation process of its quick identification code MA is as follows: The character set split by ". " is {Device, DeviceInfo, MU, ManufacturerOUI}, where {i} represents the multi-instance number and thus does not participate in the calculation.
[0062] Calculate the sum of the corresponding character lengths Len and ASCII values in the character set respectively. Among them, Len(Device) = 6, VAL(Device) = 68 + 101+118+105+99+101 = 592; Len(DeviceInfo) = 10, VAL(DeviceInfo) = 592+73+110+102+111=988; Len(MU) = 2, VAL(MU) = 77+85 = 162; Len(ManufacturerOUI) = 15, VAL(ManufacturerOUI) = 77+97+110+117+102+97+99+116+117+114+101+114+79+85+73 = 1498; TotalLen= Len(Device) + Len(DeviceInfo) + Len(MU) + Len(ManufacturerOUI) = 6+10+2+15 = 33; Then the MA of ParName = Device.DeviceInfo.MU.{i}.ManufacturerOUI is 33 - 6.592 - 10.988 - 2.162 - 15.1498.
[0063] When comparing the multi-instance parameter of SubPar_ParName = Device.DeviceInfo.MU.3.ManufacturerOUI with ParName = Device.DeviceInfo.MU.{i}.ManufacturerOUI, through the above process of comparison, the multi-instance number does not participate in the comparison, so the two are exactly equal, meeting the expectation.
[0064] When Pro_ParName = Device.DeviceInfo.MU.2.ProductClass, the character set split by ". " is {Device, DeviceInfo, MU, ProductClass}, where Len(Device) = 6, VAL(Device) = 68 + 101+118+105+99+101 = 592; Len(DeviceInfo) = 10, VAL(DeviceInfo) = 592+73+110+102+111=988; Len(MU) = 2, VAL(MU) = 77+85 = 162; Len(ProductClass) = 12,VAL(ProductClass) = 80+114+111+100+117+99+116+67+108+97+115+115 = 1239; TotalLen = Len(Device) + Len(DeviceInfo) + Len(MU) + Len(ProductClass) = 6+10+2+12 = 30; Then Pro_ParName = MA of Device.DeviceInfo.MU.2.ProductClass = 30 - 6.592 - 10.988 - 2.162 - 12.1239, and its MA compared with ParName = MA of Device.DeviceInfo.MU.{i}.ManufacturerOUI = 33 - 6.592 - 10.988 - 2.162 - 15.1498 is not equal when comparing the first key information (33 and 30), so they are directly inconsistent and the comparison ends.
[0065] Compared with the ordinary method for judging the equality of parameter names, this method of the present invention not only omits the comparison of multiple instance numbers {i}, but also shortens the process of character comparison. It calculates the corresponding numerical values and ASCII code values for both the total parameter length and the length of a single word, thus improving the comparison efficiency.
[0066] Although the embodiments of the present invention have been shown and described, those of ordinary skill in the art can understand that various changes, modifications, substitutions, and variations can be made to these embodiments without departing from the principles and spirit of the present invention. The scope of the present invention is defined by the appended claims and their equivalent scope.< / cwmp:getparametervaluesresponse>
Claims
1. A method for analyzing a base station data model based on the TR069 protocol, characterized in that, Including: 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; 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 situation report corresponding to the base station according to the score, and completes the final adaptation analysis.
2. The method for analyzing the base station data model based on the TR069 protocol according to claim 1, wherein In Step 1, construct the database form EvaluationRulesTable according to the following steps: The network management platform divides out the key parameter index information set {KeyParInfo1,...,KeyParInfo i ,...,KeyParInfo N} based on the data model of the TR-181 specification, where KeyParInfo i includes the parameter name ParName, importance ParImp, read / write permission ParRWPer, data type ParType, actual read / write permission ActParRWPer, actual data type ActParType, and actual parameter value ActParValue. N is the maximum number of entries in this set, and i ∈ N; The network management platform creates a database form EvaluationRulesTable and writes the information of {KeyParInfo1,...,KeyParInfo i ,...,KeyParInfo N} into EvaluationRulesTable, and records the creation of the database form EvaluationRulesTable as a set {DBRuleInfo1,...,DBRuleInfo j ,...,DBRuleInfo N} containing N records, where j ∈ N.
3. The method for analyzing the base station data model based on the TR069 protocol according to claim 2, wherein In Step 2, update the database form according to the following steps: The network management platform sends an RPC message of GetParameterNames to the base station, and the base station returns an RPC message of GetParameterNamesResponse. The network management platform obtains a key information set {PropertInfo1,..., PropertInfo k ,..., PropertInfo M} from the RPC message returned by the base station, where M is the maximum number of entries in the set, and k ∈ M; The network management platform sends an RPC message of GetParameterValues to the base station, and the base station returns an RPC message of GetParameterValuesResponse. The network management platform obtains a key information set {SubParInfo1,..., SubParInfo x ,..., SubParInfo S} from the RPC message returned by the base station, where S is the maximum number of entries in this set, and x ∈ S; Write the data in the sets {PropertInfo1,...,PropertInfo k ,...,PropertInfo M} and {SubParInfo1,...,SubParInfo x ,...,SubParInfo S} into 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}, and for each SubParInfo x in it, if a corresponding record DBRuleInfo x is found in the EvaluationRulesTable for SubParInfo j .SubPar_ParName, that is, DBRuleInfo j. ParName is equal to SubParInfo x. SubPar_ParName, then update the data for DBRuleInfo j , and set DBRuleInfo j. ActParType = SubParInfo x. SubPar_ParType, DBRuleInfo j. ActParValue = SubParInfo x. SubPar_ParValue.
4. The method for analyzing the base station data model based on the TR069 protocol according to claim 3, wherein In Step 3, perform analysis according to the following steps: Traverse the set {DBRuleInfo1,..., DBRuleInfoj,..., DBRuleInfoN} of the database form EvaluationRulesTable, If DBRuleInfo j. The value of ActParValue is null, then this record is judged as failed; If DBRuleInfo j. the value of ActParValue is not null, and DBRuleInfo j. ParRWPer is equal to DBRuleInfo j. ActParRWPer, and at the same time DBRuleInfo j. ParType is equal to DBRuleInfo j. ActParType, then this record is judged to pass; According to DBRuleInfo j. Score according to the types of ParImp respectively; After scoring each record, add the corresponding scoring result after the ActParValue field of the record, passing is marked as P, and failing is marked as F.
5. The method for analyzing the base station data model based on the TR069 protocol according to claim 4, wherein In Step 3, perform scoring according to the following steps: According to DBRuleInfo j. ParImp = A or B is scored separately according to the following three dimensions, where A is a key parameter and B is a general parameter; Dimension 1: For DBRuleInfo j. Score the parameter of ParImp = A: Divide the number of passed parameters of DBRuleInfo j. ParImp = A by the total number of corresponding parameters in DBRuleInfo j. Multiply the result by 100. The obtained value is the score; Dimension 2: For DBRuleInfo j. Score the parameter of ParImp = B: Divide the number of passed parameters of DBRuleInfo j. ParImp = B by the total number of corresponding parameters in DBRuleInfo j. ParImp = B, then multiply by 100. The resulting value is the score; Dimension 3: Score the overall parameters: (the number of all passed parameters / the total number of parameters) * 100.
6. A base station data model analysis system based on the TR069 protocol, characterized in that Including: Construction unit: Define key information based on the full set of data model parameters, and construct a corresponding database form according to the key information; Obtaining unit: Obtain the corresponding data model parameters from the base station, and update the database form according to the obtained parameters; Analysis unit: Analyze the updated database form to obtain the corresponding score; Output unit: Output a parameter adaptation situation report corresponding to the base station according to the score, and complete the final adaptation analysis.
7. The base station data model analysis system based on the TR069 protocol according to claim 6, characterized in that, The construction unit constructs the database form EvaluationRulesTable according to the following steps: Based on the data model of the TR-181 specification, the key parameter index information set {KeyParInfo1,...,KeyParInfo i ,...,KeyParInfo N} is divided, where KeyParInfo i includes the parameter name ParName, importance ParImp, read-write permission ParRWPer, data type ParType, actual read-write permission ActParRWPer, actual data type ActParType, and actual parameter value ActParValue. N is the maximum number of entries in this set, and i ∈ N; Create a database form EvaluationRulesTable and write the information of {KeyParInfo1,...,KeyParInfo i ,...,KeyParInfo N} into EvaluationRulesTable. Denote the created database form EvaluationRulesTable as a set {DBRuleInfo1,...,DBRuleInfo j ,...,DBRuleInfo N} containing N records, where j ∈ N.
8. The base station data model analysis system based on the TR069 protocol according to claim 7, characterized in that, The obtaining unit updates the database form according to the following steps: The network management platform sends an RPC message of GetParameterNames to the base station, and the base station returns an RPC message of GetParameterNamesResponse. The key information set {PropertInfo1,...,PropertInfo k ,...,PropertInfo M} is obtained from the RPC message returned by the base station. M is the maximum number of entries in this set, and k ∈ M; The network management platform sends an RPC message of GetParameterValues to the base station, and the base station returns an RPC message of GetParameterValuesResponse. The network management platform obtains a set of key information {SubParInfo1,..., SubParInfo x ,..., SubParInfo S} from the RPC message returned by the base station. S is the maximum number of entries in this set, and x ∈ S; Write the data in the sets {PropertInfo1,...,PropertInfo k ,...,PropertInfo M} and {SubParInfo1,...,SubParInfo x ,...,SubParInfo S} into the database form EvaluationRulesTable: (1)Traverse each PropertInfo in {PropertInfo1,...,PropertInfo k ,...,PropertInfo M} k . If the corresponding record DBRuleInfo of PropertInfo k. Pro_ParName is found in the EvaluationRulesTable j , that is, DBRuleInfo j. ParName is equal to PropertInfo k. Pro_ParName, then update the data of DBRuleInfo j , and set DBRuleInfo j. ActParRWPer = PropertInfo k. Pro_ParRWPer; (2) Traverse each SubParInfo in {SubParInfo1,..., SubParInfo x ,..., SubParInfo S}, if the corresponding record DBRuleInfo x is found in the EvaluationRulesTable for SubParInfo x .SubPar_ParName, that is, DBRuleInfo j ParName is equal to SubParInfo j. SubPar_ParName, then update the data for DBRuleInfo x. , set DBRuleInfo j ActParType = SubParInfo j. SubPar_ParType, DBRuleInfo x. ActParValue = SubParInfo j. SubPar_ParValue. x. 9. The base station data model analysis system based on the TR069 protocol according to claim 8, characterized in that The analysis unit analyzes according to the following steps: Traverse the set of the database form EvaluationRulesTable {DBRuleInfo1,..., DBRuleInfo j ,..., DBRuleInfo N}, If DBRuleInfo j. The value of ActParValue is a null value, then this record is judged as not passing; If DBRuleInfo j. the value of ActParValue is not null, and DBRuleInfo j. ParRWPer is equal to DBRuleInfo j. ActParRWPer, and at the same time DBRuleInfo j. ParType is equal to DBRuleInfo j. ActParType, then this record is judged to pass; According to DBRuleInfo j. Score according to the types of ParImp respectively; After scoring each record, add the corresponding scoring result after the ActParValue field of the record, passing is marked as P, and failing is marked as F.
10. The base station data model analysis system based on the TR069 protocol according to claim 9, characterized in that, The analysis unit scores according to the following steps: According to DBRuleInfo j. ParImp = A or B is scored separately according to the following three dimensions. Among them, A is a key parameter and B is a general parameter; Dimension 1: For DBRuleInfo j. Score the parameter of ParImp = A: Divide the number of passed parameters of DBRuleInfo j. ParImp = A by the total number of corresponding parameters in DBRuleInfo j. Multiply the result by 100, and the obtained value is the score; Dimension 2: For DBRuleInfo j. Score the parameter of ParImp = B: Divide the number of passed parameters of DBRuleInfo j. ParImp = B by the total number of corresponding parameters in DBRuleInfo j. Multiply the result by 100, and the obtained value is the score; Dimension 3: Score the overall parameters: (the number of all passed parameters / the total number of parameters) * 100.
Citation Information
Patent Citations
Method for screening core key indexes of system through parameter tuning
CN112015619A
Base station network management multi-version adaptation method and system thereof
CN113194495A
Base station opening method and system based on TR069 protocol
CN115243297A
Base station message parameter updating and storing method based on TR069 protocol
CN117097821A
Network management adaptation system and method of dual-mode base station
CN117580074A