Model extension methods, electronic devices and storage media

Abstract

This application discloses a method for extending a model, electronic equipment, and a storage medium, which belong to the art of computers. The method includes the steps of: setting an index field in a TR181 extended model file for target traffic based on the type of target traffic; setting at least one description field in the TR181 extended model file for target traffic based on the description parameters of the target traffic, wherein one of the description fields is for expressing the characteristics of the description parameters; and setting the length of each of the description fields based on the globalization adaptability and global standards of the target traffic, thereby realizing the extension of the TR181 extended model file.

Description

Technical Field

[0001] (Cross-reference to Related Applications) This application claims the priority of a Chinese patent application with the application number 202310778141.5 and the invention title "Model Expansion Method, Electronic Device and Storage Medium", which was filed with the Chinese Patent Office on June 28, 2023, and the entire content of that application is incorporated herein by reference.

[0002] The embodiments of this application relate to the technical field of computers, and particularly to a model expansion method, an electronic device and a storage medium.

Background Art

[0003] As a network management protocol for terminal devices, TR069 is increasingly applied to wireless badge solutions, and related products are deployed in a wide range of fields such as air-land connection, factories and mines, industrial parks, port terminals, high-density office buildings, and home broadband. Compared with the conventional Simple Network Management Protocol (SNMP), TR069 has seen significant improvements in security, transmission protocol, and setting methods. However, in actual applications, the TR181 model still cannot fully meet the management requirements of network management, and there remains the problem that the operation and maintenance information of network management is not described simply or completely.

Summary of the Invention

Problems to be Solved by the Invention

[0004] The embodiments of this application provide a model expansion method, an electronic device and a storage medium.

Means for Solving the Problems

[0005] To solve the above technical problems, the present invention is realized as follows.

[0006] In the first aspect, a method for extending a model applied to a network management device is provided, comprising the steps of: setting an index field in the TR181 extended model file for the target traffic based on the type of target traffic; setting at least one description field in the TR181 extended model file for the target traffic based on the description parameters of the target traffic, wherein the description field is for expressing the characteristics of the description parameters; and setting the length of each of the description fields based on the globalization adaptability and global standards of the target traffic, thereby realizing the extension of the TR181 extended model file.

[0007] A second embodiment provides a method for extending a model applied to a terminal device, comprising the steps of obtaining a TR181 extended model file for a pre-configured target traffic, wherein the TR181 extended model file includes an index field configured based on the type of the target traffic, at least one description field configured based on the description parameters of the target traffic, and an internationalization field described in at least two languages ​​added to the target field in the at least one description field based on the adaptability of the globalization of the target traffic, the TR181 extended model file records at least one association relationship, the association relationship includes the value of the index field, the value of the description field and the value of the internationalization field, and uploading the TR181 extended model file to a network management device.

[0008] In a third embodiment, the present invention provides an electronic device including a processor and memory, wherein the memory stores a program or command executable by the processor, and when the program or command is executed by the processor, the electronic device implements the steps of the method described in the first embodiment or the steps of the method described in the second embodiment.

[0009] In a fourth aspect, a readable storage medium is provided which stores a program or command, and which, when the program or command is executed by a processor, realizes a step of the method described in the first aspect or a step of the method described in the second aspect.

[0010] The fifth aspect provides a computer program product comprising at least one computer program, wherein the computer program is loaded and executed by a processor to realize a step according to the method described in the first aspect, or a step according to the method described in the second aspect. [Brief explanation of the drawing]

[0011] The drawings presented herein are incorporated into the specification and constitute part of the specification, illustrating embodiments of the present application and serving to explain the principles of the present application together with the specification. [Figure 1] A flowchart illustrating a method for extending the model according to the exemplary embodiment of this application is shown. [Figure 2] Another flowchart illustrating a method for extending the model according to the exemplary embodiment of this application is shown. [Figure 3] Another flowchart illustrating a method for extending the model relating to the exemplary embodiment of this application is shown. [Figure 4] This diagram shows a schematic structure of an extended system of the model according to an exemplary embodiment of the present invention. [Figure 5] A structural block diagram of an exemplary embodiment of the present invention is shown. [Modes for carrying out the invention]

[0012] The following describes exemplary embodiments in detail, which are illustrated in the drawings. In the following description, when referring to the drawings, unless otherwise specified, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments are not representative of all embodiments consistent with the present application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the present application detailed in the appended claims.

[0013] To better understand the technical solutions related to this application, we will first explain the technologies related to this application.

[0014] With the rapid development of 5th Generation Mobile Communication Technology (5G) communication networks, high bandwidth, low latency, and high reliability have become fundamental characteristics and capabilities, and an increasing number of wireless barrage solutions are being applied to air and land connectivity, factories and mines, industrial parks, port terminals, high-density office buildings, and home broadband.

[0015] for example, 1. To meet the high reliability requirements of the production sector, the 5G industrial gateway, as the core of video backhaul in the industrial automation control sector, guarantees highly reliable, low-latency, and stable transmission of automated guided vehicle (AGV) control data in factories, mines, industrial parks, and ports.

[0016] 2. As the number of passengers on commercial aircraft continues to increase, airborne internet connectivity is becoming an increasingly urgent and fundamental requirement for commercial aviation systems. ATG (Air To Ground) utilizes mature ground mobile communication technologies to build a ground-to-air broadband coverage network, and ATG Customer Premise Equipment (CPE) can provide services such as entertainment, office work, and black-box data backhaul to passengers on board.

[0017] 3. With the spread of broadband access to homes, the rapid development of IP voice (Voice over Internet Protocol, VoIP), and network television (Interactive Personality TV, IPTV) traffic, more and more IP devices are being introduced into home networks.

[0018] As described above, traditional network management based on SNMP (Simple Network Management Protocol) is becoming increasingly difficult to manage due to the complexity and sheer number of terminal devices involved. TR069 was introduced as a suite of network management protocols for terminal devices, defining a completely new network management architecture that includes the TR181 management node model, interaction interfaces, and basic management parameters. This enables unified management of devices of different types and manufacturers across the network, significantly improving the efficiency of terminal management and the universality of access to Auto-Configuration Server (ACS) network management.

[0019] Here, the CPE Wide Area Network Management Protocol (CWMP), with the designation TR-069 and also known as the TR-069 protocol, includes a series of standards such as TR069 and TR181, which provide a new general-purpose framework for network terminal device management, message standard definitions, and a parameter node model. Here, TR069 mainly defines the communication protocol standard and interaction process, while the TR181 standard defines the management node model.

[0020] While the TR069 protocol shows clear improvements over the SNMP protocol in terms of security, transmission protocol, and configuration method, the following problems still exist.

[0021] 1) Network management operation and maintenance information are simple, the character length standard definition is relatively short, for example, it is a combination of simple English words and underlines, and there is no complete description. This makes it difficult to position on-site, increases costs, and reduces efficiency.

[0022] For example, in the TR069 protocol, the alarm cause ProbableCause can be obtained in response to alarm traffic, the standard definition field length is String(64), which is only 64 bytes (32 Chinese characters), and the alarm description SpecificProblem is String(128), which is only 128 bytes (64 Chinese characters). As can be seen from this, when the character length standard definition is relatively short, detailed alarm information cannot be fully transmitted, and on-site operation and maintenance cannot be effectively guided. Also, during on-site operation and maintenance, it is necessary to contact the network management or terminal manufacturer to obtain further positioning support.

[0023] 2) Due to the lack of terminal basic information, some functions of network management are incomplete, and general-purpose capabilities are not supported.

[0024] For example, in the TR069 protocol, key fields of alarm traffic, such as suggestions for alarm handling and alarm code names, are not defined. These play an important role in quickly resolving alarm events on-site and are also the data basis for wizard-type alarms in business-oriented (To Business, ToB) network management. However, due to the current lack of TR069 protocol fields, the corresponding network management functions cannot be utilized.

[0025] 3) Since the terminal only supports a single language, it cannot support information display in a multilingual environment of network management products, and the path to product globalization is far.

[0026] Specifically, the standard does not define an internationalization description for String type parameter values. Therefore, regardless of which languages ​​or multiple languages ​​the network management supports, only single-language display is supported for traffic corresponding to the terminal. Furthermore, when the terminal reports traffic data, each key field is typically a combination of simple English words or an abbreviation of English words mixed with underscores.

[0027] Furthermore, TR069 defines the communication protocol stack between ACS and CPE as making Remote Procedure Call Protocol (RPC) method calls based on a Simple Object Access Protocol (SOAP) message body. The number and length of fields contribute to an increase in the size of the SOAP message body. Currently, typical SOAP messages contain a large number of repeating tags, and the addition of fields, detailed descriptions, and internationalization content will increase the size of the SOAP message body. This requires higher network bandwidth for message transmission, longer transmission times for large messages, increased susceptibility to network fluctuations, and stricter requirements for upper-layer application retries.

[0028] In view of this, the present invention provides a model expansion method, electronic device, and storage medium to solve the above problems, reduce the operation and maintenance costs of terminal equipment, and improve customer response speed and product competitiveness.

[0029] Figure 1 shows a flowchart of a method for extending the model in an embodiment of the present invention. Method 100 may be performed by a network management device or by other devices. As shown in Figure 1, the method may include the following S110 to S130.

[0030] S110: Based on the type of target traffic, set an index field in the TR181 extended model file for the target traffic.

[0031] To make it clear, different types of traffic have different TR181 extension model files. Therefore, network management equipment sets an index field in the TR181 extension model file for the target traffic based on the type of target traffic corresponding to the terminal. In other words, the TR181 extension model file corresponding to the target traffic can be determined through this index field. The index field includes, but is not limited to, a unique identifier.

[0032] S120: Based on the description parameters of the target traffic, set at least one description field in the TR181 extended model file for the target traffic.

[0033] Here, one of the description fields is for representing the characteristics of the description parameter.

[0034] To make it clear, the description parameter refers to the traffic data of the target traffic of the terminal device, and the network management device sets at least one description field in the TR181 extended model file of the target traffic based on that traffic data. For example, if the target traffic is alarm traffic, the description field corresponding to the alarm traffic may include fields such as an alarm detail description corresponding to the alarm code name, alarm cause, alarm action suggestion, alarm type, and alarm level.

[0035] If the target traffic is performance metric statistics traffic, the description fields corresponding to the performance metric statistics traffic may include fields such as network accessibility, network health, network consumption, and network interference, which are measurement metrics designed by the manufacturer. At least one description field is determined by the network management device, and for example, even if no traffic is running during the terminal execution period, the description field corresponding to the alarm traffic is determined. In other words, these description fields are not uploaded from the terminal to the network management device only when a traffic event related to the execution period occurs.

[0036] S130: Based on the adaptability of the target traffic to globalization and global standards, the length of each description field is set, thereby enabling the extension of the TR181 extended model file.

[0037] To ensure data consistency and usability, each descriptive field must be configured so that data is correctly transmitted and parsed across various systems and applications. This improves data readability and maintainability, and facilitates interaction and sharing of data between different systems. The field length can be reasonably set based on the adaptability of the target traffic to globalization and global standards. Field lengths that are too long or too short can both affect data storage and transmission efficiency. For example, the length of the alarm type field can be determined by enumerating all alarm types and obtaining the longest alarm type value.

[0038] In embodiments of the present invention, the network management device sets an index field in the TR181 extended model file of the target traffic based on the type of target traffic, sets at least one description field in the TR181 extended model file of the target traffic based on the description parameters of the target traffic, and further sets the length of each description field based on the globalization adaptability and global standards of the target traffic, thereby extending the TR181 extended model file.

[0039] This allows target traffic data from terminal devices and TR181 to be correlated via an index field, enabling the extension of the corresponding TR181 extension model based on the description parameters of the target traffic from the terminal devices. This solves the problem of some basic information being missing and the content of operation and maintenance information being simple and not fully described, and not only ensures that the length of the description field meets the requirements of the target traffic, but also improves the flexibility and availability of the TR181 extension model.

[0040] In embodiments of the present invention, the network management device extends the TR181 extended model file so that terminal devices can record at least one association relationship based on the extended TR181 extended model file. The association relationship includes an association between the value of the index field and the value of each of the description fields, so that during traffic execution, the network management device can obtain the value of each description field corresponding to the target value of the index field transmitted from the terminal device based on the association relationship, obtain information about the current traffic, and implement the corresponding management function.

[0041] In one implementation, the step of setting the length of each description field based on the adaptability of the target traffic to globalization and global standards may include the step of adding an internationalization field described in at least two languages ​​to the target field in at least one description field based on the adaptability of the target traffic to globalization, and the step of setting the length of each description field and each internationalization field based on the regular expression scheme of each description field and each internationalization field.

[0042] To understand this, the conventional TR181 model only supports one language for terminal device execution time data, which narrows the user base of the TR181 model that corresponds to the target traffic and leads to a degraded user experience. Therefore, considering the diversity of target users and the market needs of target traffic, it is necessary to provide multilingual support as much as possible to meet a wider user base and market demands. In addition, in order for the description fields to convey detailed information, the length of each description field and internationalization field should be set based on the global standards for each description field and internationalization field.

[0043] In the above-described embodiment of the present invention, in order to make the length of each description field and each internationalization field appropriate, for example, the length of each description field and each internationalization field is set based on the regular expression scheme of each description field and each internationalization field so that each description field and each internationalization field can be expressed sufficiently without redundancy. For example, for the alarm type field, the length of the alarm type field can be determined by enumerating the regular expression schemes of all alarm types and using different numbers to refer to different alarm types.

[0044] Furthermore, for example, the length of the alarm cause field can be determined based on the regular expression scheme of the alarm cause, for example, the expression "who does what," and further based on the lengths of all possible expressions for "who" and all possible expressions for "what does." Also, for example, the length of the English field for the alarm code name can be determined by listing all possible English expressions for the alarm code name and using the length of the longest expression among them as the length of the English field for the alarm code name.

[0045] In one implementation, after setting the length of each description field based on the adaptability of the target traffic to globalization and global standards, the method further includes the step of adding entry rules to each field of the TR181 extension model file based on the meaning and length of each description field. Exemplarily, Table 1 shows a TR181 extension model configured by a network management device for terminal devices based on the characteristics of the target traffic.

[0046] [Table 1] TIFF2026522895000003.tif193170

[0047] The fields in the TR181 extended model include alarm code name, alarm code Chinese name, alarm code English name, alarm cause code, alarm cause Chinese name, suggested action Chinese name, suggested action English name, alarm type, alarm level, and code value type. Each field has corresponding entry rules. For example, the alarm level includes five levels: 0: undefined, 1: critical, 2: major, 3: minor, and 4: alarm. When the manufacturer of the terminal equipment enters the alarm level, they should only enter the number corresponding to the alarm level.

[0048] In this implementation, by adding entry rules to each field of the TR181 extended model file, the problems of lack of internationalization language, missing fields, and insufficient length are resolved, contributing to ensuring data accuracy, consistency, and completeness, and improving data quality and usability.

[0049] In one implementation, after setting the length of each of the description fields based on the adaptability of the target traffic to globalization and global standards, the method further includes the steps of: delivering a file upload command to a terminal device at a target opportunity, the file upload command being for instructing the terminal device to upload the TR181 extension model file corresponding to the terminal device; and receiving the TR181 extension model file uploaded from the terminal device, wherein the uploaded TR181 extension model file has at least one association recorded, the association including the value of the index field, the association between the value of the description field and the value of the internationalization field. To understand that after setting the length of each of the description fields based on the adaptability of the target traffic to globalization and global standards, the network management device needs to receive the TR181 extension model file uploaded from the terminal device, and therefore the network device delivers a file upload command to the terminal device at a target opportunity.

[0050] In another implementation, the target opportunity includes one of the following steps: determining that the current version of the terminal device is missing a corresponding traffic model file; determining that the terminal device has connected to the network management device for the first time; or determining that a change has occurred in the connection state between the terminal device and the network management device. In other words, when the current version of the terminal device is missing a corresponding traffic model file, or when the model number terminal device accesses the network management device for the first time, or when a change occurs in the connection state between the network management device and the terminal device, a file upload command is delivered to the terminal device.

[0051] In one implementation, the step of delivering a file upload command to a terminal device may include the steps of converting the file upload command into a TR069 standard file upload first Simple Object Access Protocol SOAP message body, and transmitting the first SOAP message body to the terminal device via the Remote Procedure Call (RPC) interface defined in the TR069 standard.

[0052] To make it clear, TR069 defines a communication protocol standard and interaction process, enabling unified remote management and configuration of terminal devices that support this protocol.

[0053] The Simple Object Access Protocol (SOAP) is an XML-based protocol used for communication between application programs over a network. The SOAP message body is the data carrier transmitted within the SOAP protocol and is typically expressed in XML format. By converting file upload commands into the SOAP message body of the TR069 standard file upload, remote management and configuration of devices can be achieved, improving management efficiency, security, and data transmission reliability.

[0054] By sending the first SOAP message body via the Remote Procedure Call Protocol (RPC) interface, remote calls across networks can be enabled, supporting cross-language communication and improving efficiency and performance.

[0055] In one implementation, the step of receiving a TR181 extended model file uploaded from the terminal device includes the steps of receiving a TR181 extended model file uploaded by the terminal device via the RPC interface defined in the TR069 standard, and analyzing the TR181 extended model file to obtain the TR181 extended model file uploaded from the terminal device.

[0056] To understand this, a terminal device can, after receiving a file upload command sent from a network management device, send a TR181 extended model file to the network management device based on that file upload command. The network management device can, after receiving the TR181 extended model file, parse the TR181 extended model file to obtain the TR181 extended model file uploaded from the terminal device.

[0057] In one implementation, the terminal can further upload a SOAP message body to notify the network management device that the upload of the TR181 extended model file is complete. Accordingly, in this implementation, the method receives the second SOAP message body uploaded by the terminal device via the RPC interface defined in the TR069 standard, and parses the second SOAP message body to determine that the upload of the TR181 extended model file is complete.

[0058] In one implementation, the method further includes the step of creating an extended model standard, the contents of which include at least one file upload attribute of the TR181 extended model, such as the file packaging method, file directory structure, file name, character encoding, and TR069 file type definition. To ensure the integrity of the TR181 extended model, it is necessary to set attributes such as the file packaging method, file target structure, file name, character encoding, and TR069 file type definition for the TR181 extended model. These are the rules corresponding to each file upload attribute, as shown in Table 2.

[0059] [Table 2]

[0060] Here, the file format is CSV, and compared to the SOAP message body, it does not contain a large number of duplicate fields.

[0061] In one implementation, after receiving a TR181 extension model file uploaded from a terminal device, the method further includes the steps of receiving a target key value of an index field corresponding to traffic data transmitted by the terminal device during a traffic execution period, and obtaining the values ​​of the description field and the internationalization field associated with the target key value from the uploaded TR181 extension model file. To understand this, a network management device can receive traffic data transmitted by the terminal device during a traffic execution period, thereby extracting a target key value of an index field corresponding to the traffic data, and obtaining the values ​​of the description field and the internationalization field associated with the target key value based on the target key value.

[0062] Based on the above relationships, it is possible to obtain TR181 extended model information of the data during the execution period of the target traffic, such as extended fields, Chinese / English internationalization, and detailed information descriptions.

[0063] Figure 2 shows another flowchart of a method for extending the model in an embodiment of the present invention, and this method 200 may be performed by a terminal device. As shown in Figure 2, this method may include the following S210-S220.

[0064] S210: Retrieves the TR181 extension model file for the pre-configured target traffic.

[0065] Here, the TR181 extended model file includes an index field set based on the type of target traffic, at least one description field set based on the description parameters of the target traffic, and an internationalization field described in at least two languages ​​added to the target field in the at least one description field based on the adaptability of the globalization of the target traffic, the TR181 extended model file records at least one association relationship, the association relationship includes the value of the index field, the value of the description field and the value of the internationalization field.

[0066] S220: Upload the TR181 extension model file to the network management device.

[0067] By uploading the TR181 extended model file to the network management device, the network management device can perform model extensions based on the TR181 extended model file. Then, during traffic execution, terminal devices only need to send the values ​​of the corresponding index fields to the network management device, and the network management device can obtain the values ​​of each description field corresponding to the index field values ​​based on those values. As a result, the network management device can obtain richer information, making it easier to manage the network management device.

[0068] In one implementation, before uploading the TR181 extension model file to the network management device, the method may further include the step of receiving a file upload command sent from the network management device. Here, the file upload command may be an RPC file upload command, which is the basic interface channel for communication between the ACS and the terminal, and this channel can be reused by defining a new FileType, after which the terminal device can upload the TR181 extension model file after receiving the FileType.

[0069] To make it clear, terminal equipment may proactively upload the TR181 extension model file to the network management equipment after accessing it or at another appropriate opportunity, or it may upload it after receiving a file upload command sent from the network management equipment.

[0070] Selectively, after uploading the TR181 extension model file, the terminal device can send a message to the network management device to notify it whether the model file has already been uploaded, for example, via a SOAP message body.

[0071] Selectively, because the terminal device functions themselves are complex, it is not possible to describe the functions of a terminal device in a single model file. A single function traffic may contain multiple TR181 extension model files, and therefore, they can be compressed into a package and uploaded in a batch during the upload process. For example, for performance traffic, as shown in Table 2, one performance traffic corresponds to three TR181 extension model files: group.csv, KPI.csv, and mot.csv. When a terminal uploads files, it packages them according to the packaging method described in Table 2, names the package files according to the file package naming convention in Table 2, and then uploads them in a batch. The following provides examples of the three TR181 extension model files mentioned above, with Table 3 showing an example of the contents of KPI.csv, Table 4 showing an example of the contents of mot.csv, and Table 5 showing an example of the contents of group.csv.

[0072] [Table 3]

[0073] [Table 4]

[0074] [Table 5]

[0075] In the embodiments of this invention, by uploading the corresponding TR181 extension model file to the network management device via a terminal device, the acquired TR181 extension model not only meets the target traffic requirements of the terminal device, but also improves the flexibility and availability of the TR181 extension model.

[0076] In one implementation, the step of uploading the updated TR181 extended model file to the network management device includes the step of uploading the updated TR181 extended model file to the network management device according to file upload attributes, where the file upload attributes include at least one of the file package scheme, file target structure, file name, character encoding, and TR069 file type definition. The details regarding the file attributes can be found in the relevant descriptions in the embodiment shown in Figure 1 and will not be repeated here.

[0077] In one implementation, after uploading the updated TR181 extension model file to the network management device, the method further includes the steps of determining a target key value for an index field corresponding to the traffic data that needs to be sent to the network management device during the execution period of the target traffic, and sending the target key value to the network management device. In other words, the terminal needs to report the traffic data of the target traffic for the execution period, and the network management device can associate the TR181 extension model with the traffic data for the execution period based on the index field, thereby improving the flexibility and availability of the TR181 extension model.

[0078] The embodiments shown in Figures 1 and 2 above will be specifically described below with reference to Figure 3.

[0079] S310: Detects that the terminal device is online.

[0080] S320: Distributes a file upload command.

[0081] Network management equipment creates unified extension models according to different traffic characteristics, enabling each terminal manufacturer to adapt. For example, for alarm traffic, the network management equipment extends the TR181 extension model file shown in Table 1 above. Network management defines the table header and the explanatory example in the second row, while the terminal manufacturer fills in the third row onwards. Therefore, the network management equipment needs to distribute traffic model file upload commands at appropriate times. The upload method may be the RPC file upload method defined in the TR069 standard. Distribution opportunities can be selected from when terminal equipment is newly installed, when the connection status changes, or during periodic model missing scans. Typically, since the same model number and version contain only one set of traffic models, it is not necessary to distribute the command to each device.

[0082] S330: Analyze the file upload command.

[0083] S340: Upload the traffic model file.

[0084] After receiving an RPC file upload command from network management, the terminal device uploads the traffic static model to the specified directory.

[0085] S350: Analyze the traffic model file.

[0086] Network management devices analyze traffic models uploaded from terminal devices and register traffic static fields in a database based on unified platform model rules for network management.

[0087] S360: Upload traffic data.

[0088] Terminal devices report the traffic data generated during the execution period to network management via inform messages in accordance with the TR069 standard definition.

[0089] S370: Associates traffic data with traffic models.

[0090] Network management analyzes execution period data and associates it with a static traffic model. The complete information is displayed on the frontend. Here, in the SOAP message body format of the inform messages reported from the terminal, for alarm traffic, Device.FaultMgmt.ExpeditedEvent.{i}.ProbableCause in SOAP can be associated with the static model, and for performance metric statistics traffic, Device.PeriodicStatistics.SampleSet.{i}.Alias ​​can be associated with the static model.

[0091] S380: To materialize as a business.

[0092] As shown in Figure 4, this is a structural diagram of an extended system of a model that will be realized as a business, and the extended system 400 of this model includes a network management device 410 and terminal devices 420. Here, the network management device 410 includes the following components.

[0093] 1. Front-end UI module: This module provides an interface for displaying network management characteristics and supports user observation and operation interaction.

[0094] As a possible alternative, the traffic data model is pre-configured in network management rather than being uploaded to network management from the terminal device. If the terminal does not have access to network management or has access to network management but there are no alarm events, the frontend UI module can display specific alarm details such as alarm description, cause, alarm level, alarm type, and response method. If the terminal has access to network management and one alarm occurs, packet capture is performed at the TR069 protocol adaptation layer of network management, and the TR181 standard message fields in the alarm report SOAP body are checked, which correspond to the individual fields of the alarm that network management will ultimately display, although the information in SOAP is clearly simpler. If the terminal has access to network management and an alarm or performance statistics occurs, packet capture is performed in network management, and while the reported TR181 INFORM message body is only in a single language, the frontend UI module can switch between different language environments, and the final alarm and performance data will be displayed adapted according to the different language environment.

[0095] 2. App Service Module: Provides service responses corresponding to the frontend UI, and retrieves and feeds back the data required by the frontend.

[0096] 3. Unified Platform Module: Typically, this is an underlying memory structure designed based on ITU-T telecommunications standards, intended to provide unified database registration and storage of application data.

[0097] 4. Protocol Adapter Modules: Depending on the type of device being managed, there are typically multiple protocol adapters, such as the TR069 protocol adapter and the NETCONF protocol adapter. The TR069 protocol adapter primarily supports: a. Identity authentication mechanisms defined by the protocol, such as basic authentication, digest authentication, and certificate authentication; b. RPC methods defined by the protocol, and communication and interaction with terminals; c. Message interaction between SOAP message bodies and request headers defined by the protocol; d. Reporting terminal messages, performing basic analysis, packaging them according to the network management structure after analysis, and broadcasting them to relevant modules, such as alarm event reporting and performance statistics periodic reporting; and e. Triggering operations via network management, distributing them to terminals, and executing them, such as upgrades, reboots, and configuration activation.

[0098] Terminal equipment 420 includes various terminals that support the TR069 protocol in air and land connections, factories and mines, industrial parks, port terminals, office buildings and home broadband, and exemplifies, 1. Air-Ground Connectivity Aircraft Platform Equipment (CPE): Based on 5G NR data backhaul functionality, it is installed in the equipment compartment and accesses ground 5G NR base stations to perform wireless backhaul to the in-flight WiFi AP system. 2. Industrial Gateways: These support the automation of on-site operations of automated guided vehicles and are key equipment in on-site work, such as in the steel industry. 3. Port industrial automation control application traffic terminal: Establish a construction control operation channel. 4. Mine edge computing gateway terminal: Supports backhauling operation videos at the site. 5. Automated Guided Vehicles (AGVs) used in industrial parks for production automation: Enable automated logistics and turnaround. 6. Home appliances and personal wearable devices.

[0099] Conventional TR069 device network management analyzes terminal execution time data only through the TR069 protocol adaptation layer and displays it directly on the front end. As a result, terminal execution time data only supports a single language, some basic information is missing, and the information is simplified and not fully described.

[0100] In this invention, the application service module detects the existence of a TR069 extension model based on the version of the terminal product managed by network management. If it does not exist, it delivers an extension model upload command to the terminal device, parses and uses the extension model uploaded from the terminal, and the protocol adapter module receives the extension model upload message sent from the application layer, converts it into a SOAP message body for TR069 file upload, and sends it to the terminal device via the RPC interface. The terminal receives the extension model, and the terminal device responds to the upload command uploaded from the extension model, and can fully upload the model file via the HTTPS protocol.

[0101] In this embodiment, from the standpoint of flexibility in problem solving, the terminal static model and traffic statistics are separated. Terminal traffic statistics focus on collecting and reporting execution data, while the static model focuses on understanding and abstracting network management remote operation and maintenance. The method of loading the model is flexible; terminals may report passively, actively, be deployed by network management, or pre-configured by network management.

[0102] From an applicability standpoint, network management can create only static models that extend the TR069 standard, while terminal manufacturers can provide model adaptations, enabling rapid replication of these capabilities across multiple terminal manufacturers and even across multiple traffic modules. From a product competitiveness standpoint, terminal manufacturers supporting model extensions will have higher operational and maintenance efficiency and lower costs. Network management manufacturers creating extended models will have more user-friendly and informative user interfaces, enabling them to enter the market as advanced telecommunications operators and enterprises, and providing guaranteed operational and maintenance efficiency and cost-effectiveness.

[0103] Selectively, as shown in Figure 5, embodiments of the present application further include an electronic device 500, which includes a processor 501 and a memory 502, the memory 502 storing a program or command executable by the processor 501, and when the program or command is executed by the processor 501, each step of the embodiments shown in Figures 1 to 4 above is realized, achieving the same technical effect, and in order to avoid duplication, a detailed explanation is omitted here.

[0104] The embodiments of the present application further provide a readable storage medium in which a program or command is stored, and when the program or command is executed by a processor, each process shown in Figures 1 to 4 above is realized, achieving the same technical effect. To avoid duplication, a detailed explanation is omitted here.

[0105] Here, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes, for example, a computer-readable storage medium such as a computer's read-only memory ROM, random access memory RAM, magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-temporary readable storage medium.

[0106] Embodiments of the present invention further provide a chip which includes a processor and a communication interface, the communication interface and the processor being coupled, the processor being for executing a program or command, and which can realize each process of the embodiments shown in Figures 1 to 4 above and achieve the same technical effects, and a detailed explanation is omitted here to avoid duplication.

[0107] To ensure clarity, the chip relating to the embodiment of this application may be called a system-level chip, system chip, chip system, or system-on-a-chip, etc.

[0108] The embodiments of the present application further provide a computer program / program product which is stored in a storage medium and executed by at least one processor to realize each process of the embodiments shown in Figures 1 to 4 above, achieving the same technical effects. To avoid duplication, a detailed explanation is omitted here.

[0109] In this specification, terms such as “includes,” “inclusive,” or any other variation thereof are intended to cover non-exclusive inclusion, thereby including not only those elements but also other elements not expressly listed, or elements specific to such process, method, article, or apparatus.

[0110] Unless there are further restrictions, an element limited by the phrase "including one..." does not preclude the presence of another identical element in a process, method, article, or apparatus that includes that element. Furthermore, the scope of methods and apparatus in embodiments of this application is not limited to performing functions in the order shown or discussed, but also includes performing functions essentially simultaneously or in reverse order depending on the function; for example, the described method may be performed in an order different from the described order, and various steps may be added, omitted, or combined. Also, features described with reference to some examples may be combined in other examples.

[0111] Through the above description of the embodiments, those skilled in the art will clearly understand that the methods of the embodiments can be implemented by adding the necessary general-purpose hardware platform to a computer software product, and of course, can also be implemented by hardware alone. The computer software product is stored in a storage medium (e.g., ROM, RAM, magnetic disk, optical disk, etc.) and includes several commands that cause a terminal or network-side device to execute the methods of each embodiment of the present application.

[0112] Although embodiments of the present application have been described above with reference to the drawings, the present application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not limiting. A person skilled in the art can, based on the teachings of the present application, make many types of embodiments without departing from the spirit of the present application and the scope protected by the claims, and all such embodiments fall within the scope of the protection of the present application.

Claims

1. A method for extending a model applicable to network management equipment, The steps include setting an index field in the TR181 extended model file of the target traffic based on the type of target traffic, A step of setting at least one description field in the TR181 extended model file of the target traffic based on the description parameters of the target traffic, wherein one of the description fields is for representing the characteristics of the description parameters, A method comprising the steps of setting the length of each of the description fields based on the adaptability of the target traffic to globalization and global standards, thereby realizing the extension of the TR181 extension model file.

2. The step of setting the length of each description field based on the adaptability of the target traffic to globalization and global standards is: Based on the adaptability of the target traffic to globalization, the step of adding an internationalization field described in at least two languages ​​to the target field in the at least one description field, The method according to claim 1, comprising the step of setting the length of each description field and each internationalization field based on the regular expression scheme of each description field and each internationalization field.

3. After setting the length of each description field based on the adaptability of the target traffic to globalization and global standards, the method: The method according to claim 1, further comprising the step of adding entry rules to each field of the TR181 extended model file based on the meaning and length of each description field.

4. After setting the length of each description field based on the adaptability of the target traffic to globalization and global standards, the method: A step of delivering a file upload command to a terminal device at a target opportunity, wherein the file upload command is for instructing the terminal device to upload the TR181 extended model file corresponding to the terminal device, The method according to any one of claims 1 to 3, further comprising the step of receiving a TR181 extended model file uploaded from the terminal device, wherein the uploaded TR181 extended model file has at least one association recorded, and the association includes an association between the value of the index field, the value of the description field and the value of the internationalization field.

5. The step of distributing a file upload command to the aforementioned terminal device is: The steps include converting the aforementioned file upload command into a first simple object access protocol SOAP message body for TR069 standard file uploads, The method according to claim 4, comprising the step of transmitting the first SOAP message body to a terminal device via a remote procedure call (RPC) interface as defined in the TR069 standard.

6. After receiving the TR181 extended model file uploaded from the aforementioned terminal device, The method according to claim 4, further comprising the step of receiving a second SOAP message body uploaded by the terminal device via the RPC interface defined in the TR069 standard, and determining the completion of the TR181 extended model file upload by analyzing the second SOAP message body.

7. The method according to claim 4, further comprising the step of creating an extended model standard, wherein the contents of the extended model standard include at least one file upload attribute of the TR181 extended model file, a file package method, a file target structure, a file name, a character encoding, and a TR069 file type definition.

8. After receiving the TR181 extended model file uploaded from the terminal device, the method proceeds as follows: The steps include receiving the target key value of the index field corresponding to the traffic data transmitted by the terminal device during the traffic execution period, The method according to claim 3, further comprising the step of obtaining the value of the description field and the value of the internationalization field related to the target key value from the uploaded TR181 extended model file.

9. The aforementioned target opportunities are Determine that the corresponding traffic model file is missing in the current version of the terminal device. The terminal device determines that it has connected to the network management device for the first time. The method according to claim 4, further comprising the step of determining that a change has occurred in the connection state with the terminal device.

10. A method for extending a model applicable to terminal devices, A step of obtaining a TR181 extended model file for a pre-configured target traffic, wherein the TR181 extended model file includes an index field configured based on the type of the target traffic, at least one description field configured based on the description parameters of the target traffic, and an internationalization field described in at least two languages ​​added to the target field in the at least one description field based on the adaptability of the globalization of the target traffic, the TR181 extended model file records at least one association, the association includes the value of the index field, the value of the description field and the value of the internationalization field, A method comprising the steps of uploading the TR181 extended model file to a network management device, thereby causing the network management device to perform model extension according to the TR181 extended model file.

11. Before uploading the TR181 extended model file to the network management device, the method is as follows: The method according to claim 10, further comprising the step of receiving a file upload command transmitted from the network management device.

12. The step of uploading the TR181 extended model file to the network management device is: The method according to claim 10, comprising the step of uploading the TR181 extended model file to the network management device according to file upload attributes, wherein the file upload attributes include at least one of a file package method, a file target structure, a file name, a character encoding, and a TR069 file type definition.

13. After uploading the TR181 extended model file to the network management device, the method proceeds as follows: The method according to any one of claims 10 to 12, further comprising the step of sending a target key value of an index field corresponding to traffic data to a network management device during the execution period of the target traffic.

14. Electronic device including a processor and memory, wherein the memory stores a program or command executable by the processor, and when the program or command is executed by the processor, the electronic device implements a step of an extension method of any of the models of claims 1 to 13.

15. A readable storage medium in which a program or command is stored, wherein when the program or command is executed by a processor, a step of an extension method of any of the models of claims 1 to 13 is realized.

Images