Model extension method, electronic device and storage medium

Abstract

The present application belongs to the technical field of computers. Disclosed are a model extension method, an electronic device and a storage medium. The method comprises: on the basis of the type of a target service, configuring a TR181 extended model file of the target service with an index field; on the basis of description parameters of the target service, configuring the TR181 extended model file of the target service with at least one description field, wherein the description field is used for expressing features of the description parameters; and setting the length of each description field on the basis of the degree of adaptability of the target service in terms of globalization and a global specification, so as to extend the TR181 extended model file.

Description

Model expansion method, electronic device and storage medium

[0001] Cross-references

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on June 28, 2023, with application number 202310778141.5 and invention name “Model expansion method, electronic device and storage medium”. The entire contents of the application are incorporated by reference into this application. Technical Field

[0003] The embodiments of the present application relate to the field of computer technology, and in particular to a model expansion method, electronic device, and storage medium. Background Art

[0004] TR069, a network management protocol for terminal devices, is increasingly being adopted in wireless coverage solutions. Related products are found in ground-to-air interconnection, factories and mines, enterprise campuses, ports and terminals, densely populated office buildings, and home broadband. Compared to the earlier Simple Network Management Protocol (SNMP), TR069 offers significant improvements in security, transmission protocols, and deployment methods. However, in practical applications, the TR181 model still fails to fully meet network management requirements, resulting in simplistic or incomplete descriptions of network management and operation information.

[0005] Summary of the Invention

[0006] Embodiments of the present application provide a model expansion method, electronic device, and storage medium.

[0007] In order to solve the above technical problems, this application is implemented as follows.

[0008] In a first aspect, a model extension method is provided, which is applied to a network management device, including: configuring an index field for the TR181 extended model file of the target business based on the type of the target business; configuring at least one description field for the TR181 extended model file of the target business based on the description parameters of the target business, wherein one description field is used to express the characteristics of the description parameters; and setting the length of each description field based on the global adaptability and global specifications of the target business to achieve the extension of the TR181 extended model file.

[0009] In a second aspect, a model extension method is provided, which is applied to a terminal device, including: obtaining a TR181 extended model file of a preset target service, wherein the TR181 extended model file includes: an index field configured based on the type of the target service, at least one description field configured based on the description parameters of the target service, and an internationalization field that adds at least two language descriptions to the target field in the at least one description field based on the global adaptability of the target service, and the TR181 extended model file records at least one association relationship, and the association relationship includes: an association relationship between 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.

[0010] In a third aspect, an electronic device is provided, comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0011] In a fourth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect or the steps of the method described in the second aspect are implemented.

[0012] In a fifth aspect, a computer program product is provided, which includes at least one computer program, and the computer program is loaded and executed by a processor to implement the steps of the method described in the first aspect above, or to implement the steps of the method described in the second aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0014] FIG1 shows a flow chart of a method for expanding a model provided by an exemplary embodiment of the present application;

[0015] FIG2 shows another flow chart of a model expansion method provided by an exemplary embodiment of the present application;

[0016] FIG3 shows another flow chart of a model expansion method provided by an exemplary embodiment of the present application;

[0017] FIG4 shows a schematic structural diagram of a model expansion system provided by an exemplary embodiment of the present application;

[0018] FIG5 shows a structural block diagram of an electronic device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0019] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0020] In order to better understand the technical solution provided by this application, the technology involved in this application is first introduced.

[0021] With the rapid development of 5G (5th Generation Mobile Communication Technology) networks, high bandwidth, low latency, and high reliability are the fundamental features. More and more wireless coverage solutions are being applied to ground-to-air interconnection, factories and mines, enterprise parks, ports and terminals, densely populated office buildings, and home broadband. For example:

[0022] 1. In response to the high reliability requirements of the production field, the 5G industrial gateway serves as the video backhaul synthesis core in the industrial control field, ensuring highly reliable, low-latency and stable transmission of unmanned vehicle control data in factories, mines, industrial parks, and ports.

[0023] 2. With the growing number of civil aviation passengers, in-flight connectivity has become an increasingly pressing and fundamental requirement for the civil aviation system. ATG (Air To Ground) leverages mature ground mobile communication technologies to build a ground-to-air broadband network. ATG customer premises equipment (CPE) provides passengers with entertainment, office work, and black box data transmission services.

[0024] 3. With the popularization of broadband access in homes and the rapid development of Voice over Internet Protocol (VoIP) and Interactive Personality TV (IPTV) services, more and more IP terminals are being introduced into home networks.

[0025] In summary, traditional network management based on the Simple Network Management Protocol (SNMP) is increasingly struggling to manage complex services and a large number of terminal devices. TR069, a family of network management protocols for terminal devices, emerged as a result. This protocol defines a new network management architecture, including the TR181 management node model, interaction interfaces, and basic management parameters. This allows for unified management of devices of different types and manufacturers over the network, significantly improving terminal management efficiency and the universality of network management via Auto-Configuration Servers (ACS). Among them, the CPE WAN Management Protocol (CWMP), numbered TR-069, also known as the TR-069 protocol, encompasses a system of specifications, including TR069 and TR181. This specification provides a new type of network terminal device management with a common framework, message specification definitions, and parameter node models. TR069 primarily defines the communication protocol and interaction process, while TR181 defines the management node model.

[0026] The TR069 protocol has significant improvements over the SNMP protocol in terms of security, transmission protocol, and deployment methods. However, it still has the following issues:

[0027] 1) Network management and operation and maintenance information is simple, with character length specifications being too short. For example, simple English words are underlined without complete descriptions. This makes it difficult to locate problems on-site, increasing costs and reducing efficiency.

[0028] For example, in the TR069 protocol, the alarm service corresponds to the alarm cause ProbableCause, and the specification defines the field length as Sting(64), which is only 64 bytes (32 characters in Chinese), and the alarm description SpecificProblem Sting(128), which is only 128 bytes (64 characters in Chinese). This shows that the character length specification is too small, which may result in the inability to carry detailed alarm information, unable to effectively guide on-site operation and maintenance, and requiring contact with the network management or terminal manufacturer for further support and positioning during on-site operation and maintenance.

[0029] 2) The basic information of the terminal is missing, resulting in incomplete network management functions and lack of support for general capabilities.

[0030] For example, the TR069 protocol lacks key fields for alarm services, such as alarm handling suggestions and alarm code names. These fields are crucial for quickly resolving alarm events on-site and form the data foundation for guided alarms in To-Business (ToB) network management. However, due to the missing TR069 protocol fields, the corresponding network management functions are currently unavailable.

[0031] 3) The terminal only supports one language, which cannot meet the information presentation requirements of the network management product in a multi-language environment, and the product's globalization journey is still a long way to go.

[0032] Specifically, the specification does not define international descriptions for String type parameter values. This means that no matter what language or languages ​​the network management supports, only one language is supported in the terminal's corresponding services. Moreover, when the terminal reports service data, each key field is usually a simple combination of several English words, or English word abbreviations mixed with underscores.

[0033] In addition, TR069 defines the communication protocol stack between the ACS and CPE as Remote Procedure Call (RPC) method calls based on Simple Object Access Protocol (SOAP) messages. The number of fields and character length will increase the size of the SOAP message body. Conventional SOAP messages currently contain numerous repeated tags, so adding fields, detailed descriptions, or internationalized content will also increase the size of the SOAP message body. Furthermore, message transmission requires higher network bandwidth, and large messages take longer to transmit, are more susceptible to network fluctuations, and place higher retry requirements on upper-layer applications.

[0034] In view of this, the present application proposes 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.

[0035] Figure 1 shows a flow chart of a method for extending a model in an embodiment of the present application. The method 100 can be executed by a network management device or other devices. As shown in Figure 1 , the method can include the following steps.

[0036] S110: Based on the type of the target service, configure an index field for the TR181 extended model file of the target service.

[0037] It is understood that since different types of services have different TR181 extended model files, the network management device can configure an index field for the TR181 extended model file of the target service based on the type of the target service corresponding to the terminal. In other words, the TR181 extended model file corresponding to the target service can be determined through the index field. The index field includes, but is not limited to, a unique identifier.

[0038] S120: Based on the description parameters of the target service, configure at least one description field for the TR181 extended model file of the target service.

[0039] Among them, one of the description fields is used to express the characteristics of the description parameter.

[0040] It can be understood that the description parameter refers to the service data of the target service of the terminal device, and the network management device configures at least one description field for the TR181 extended model file of the target service based on the service data. For example, if the target service is an alarm service, the description field corresponding to the alarm service may include fields such as a detailed description of the alarm corresponding to the alarm code name, the cause of the alarm, suggestions for alarm handling, the type of alarm, and the alarm level. If the target service is a performance indicator statistics service, the description field corresponding to the performance indicator statistics service may include fields such as network accessibility, network health, network energy consumption, network interference, and other manufacturer-designed measurement indicators. It should be noted that at least one description field is determined by the network management device. For example, during the operation of the terminal, even if there is no alarm service running, the description field corresponding to the alarm service is also determined. In other words, these description fields are uploaded to the network management device by the terminal only when no relevant service events are generated during the operation period.

[0041] S130: Based on the global adaptability and global standards of the target service, set the length of each description field to achieve extension of the TR181 extended model file.

[0042] It is understandable that in order to ensure data consistency and operability, it is necessary to set each description field to ensure that the data can be correctly transmitted and parsed between various systems and applications, thereby improving the readability and maintainability of the data and making the data easier to interact and share between different systems. It should be noted that the field length should be reasonably set according to the global adaptability and global standards of the target business. Field lengths that are too long or too short may affect data storage and transmission efficiency. For example, for the alarm type field, the length of the alarm type field can be determined by enumerating all alarm types and obtaining the longest alarm type value.

[0043] In an embodiment of the present application, an index field is configured for the TR181 extended model file of the target service based on the type of the target service through a network management device, and at least one description field is configured for the TR181 extended model file of the target service based on the description parameters of the target service. Then, based on the global adaptability and global specifications of the target service, the length of each description field is set to achieve the extension of the TR181 extended model file, so that the target service data of the terminal device and TR181 can be associated with each other through the index field, and the corresponding TR181 extended model can be extended according to the description parameters of the target service of the terminal device, which solves the problems of missing some basic information and simple operation and maintenance information content without complete description. Not only does the length of the description field meet the needs of the target service, but also the flexibility and availability of the TR181 extended model are improved.

[0044] In an embodiment of the present application, the network management device extends the TR181 extended model file so that the terminal device can record at least one association relationship based on the extended TR181 extended model file, and the association relationship includes: the association relationship between the value of the index field and the value of each of the description fields, so that the network management device can obtain the values ​​of each description field corresponding to the target value of the index field sent by the terminal device according to the association relationship during business operation, thereby obtaining relevant information of the current business and realizing corresponding management functions.

[0045] In one implementation, setting the length of each of the description fields based on the global adaptability and global specifications of the target business may include: adding internationalization fields described in at least two languages ​​to the target field in at least one description field based on the global adaptability of the target business; setting the length of each of the description fields and each of the internationalization fields based on the standard expression of each of the description fields and the standard expression of each of the internationalization fields. It is understandable that in the traditional TR181 model, since the runtime data of the terminal device only supports one language, the audience range of the TR181 model corresponding to the target business becomes smaller, resulting in a poor user experience. Therefore, it is necessary to take into account the diversity of target users and the market demand of the target business, and provide multi-language support as much as possible to meet the needs of a wider range of user groups and market requirements. In addition, in order for the description field to carry detailed information, it is necessary to set the length of each of the description fields and the internationalization fields based on the global specifications of each of the description fields and the internationalization fields.

[0046] In the above-described implementation of the present application, in order to ensure that the length of each description field and internationalization field is appropriate, for example, to fully express each description field and internationalization field without redundancy, the length of each description field and each internationalization field is set according to the standard expression of each description field and the standard expression of each internationalization field. For example, for the alarm type field, the length of the alarm type field can be determined by enumerating the standard expressions of all alarm types and using different numbers to refer to different alarm types. For another example, for the alarm cause field, the length of the alarm cause field can be determined based on the standard expression of the alarm cause, such as the expression of who does what, and then based on the length of all possible expressions of "who" and the length of all possible expressions of "what". For another example, for the English expression of the alarm code name field, the length of the English expression of the alarm code name can be determined by enumerating all English expressions of the alarm code name and determining the length corresponding to the longest expression as the length of the English expression of the alarm code name.

[0047] In one implementation, after setting the length of each description field based on the global adaptability and global standards of the target service, the method further includes: adding entry rules for each field of the TR181 extended model file based on the semantics and length of each description field. For example, as shown in Table 1, a TR181 extended model designed by a network management device for a terminal device based on the characteristics of the target service is shown.

[0048] Table 1.

[0049] The fields of the TR181 extended model include: alarm code name, Chinese name of alarm code, English name of alarm code, alarm reason code, Chinese name of alarm reason, Chinese name of handling suggestion, English name of handling suggestion, alarm type, alarm level, and code value type. Each field has a corresponding filling rule. For example, the alarm level includes 5 levels: 0: Undefined; 1: Severe; 2: Major; 3: Minor; 4: Warning. When filling in the alarm level, the manufacturer of the terminal device can only fill in the number corresponding to the alarm level. In this implementation, adding filling rules to each field of the TR181 extended model file solves the problems of no international language, missing fields, and insufficient length, helps to ensure the accuracy, consistency, and integrity of the data, and improves the quality and availability of the data.

[0050] In one implementation, after setting the length of each of the description fields based on the global adaptability and global specifications of the target business, the method further includes: issuing a file upload command to the terminal device at a target time, wherein the file upload command is used to instruct uploading the TR181 extended model file corresponding to the terminal device; receiving the TR181 extended model file uploaded by the terminal device, wherein at least one association relationship is recorded in the uploaded TR181 extended model file, and the association relationship includes: an association relationship between the value of the index field, the value of the description field, and the value of the internationalization field. It is understandable that after setting the length of each of the description fields based on the global adaptability and global specifications of the target business, the network management device needs to receive the TR181 extended model file uploaded by the terminal device, and therefore, the network device needs to issue a file upload command to the terminal device at a target time.

[0051] In another implementation, the target timing includes one of the following: determining that the current version of the terminal device lacks the corresponding business model file; determining that the terminal device is connected to the network management device for the first time; or determining that the connection status with the terminal device has changed. In other words, if the current version of the terminal device lacks the corresponding business model file, or the terminal device of the model is connected to the network management device for the first time, or the connection status between the network management device and the terminal device has changed, a file upload command is issued to the terminal device.

[0052] In one implementation, issuing a file upload command to a terminal device may include: converting the file upload command into a first Simple Object Access Protocol (SOAP) message body for file upload in accordance with the TR069 specification; and sending the first SOAP message body to the terminal device via a Remote Procedure Call (RPC) interface defined in the TR069 specification. It is understood that TR069 defines communication protocol specifications and interaction processes, enabling unified remote management and configuration of terminal devices supporting the protocol. The first Simple Object Access Protocol (SOAP) is an XML-based protocol used for communication between applications on a network. The SOAP message body is the data carrier transmitted in the SOAP protocol and is typically represented in XML format. By converting the file upload command into a SOAP message body for file upload in accordance with the TR069 specification, remote management and configuration of the device can be achieved, improving management efficiency, security, and data transmission reliability. Sending the first SOAP message body via the Remote Procedure Call (RPC) interface enables remote calls across networks, not only supporting cross-language communication but also improving efficiency and performance.

[0053] In one implementation, the receiving of the TR181 extended model file uploaded by the terminal device includes: receiving the TR181 extended model file uploaded by the terminal device via the RPC interface defined in the TR069 specification; and parsing the TR181 extended model file to obtain the TR181 extended model file uploaded by the terminal device. It is understood that after receiving the file upload instruction sent by the network management device, the terminal device can send the TR181 extended model file to the network management device according to the file upload instruction. After receiving the TR181 extended model file, the network management device can obtain the TR181 extended model file uploaded by the terminal device by parsing the TR181 extended model file.

[0054] In one implementation, the terminal may also upload a SOAP message body to notify the network management device that the TR181 extended model file has been uploaded. Therefore, in this implementation, the method may further include receiving a second SOAP message body uploaded by the terminal device via the RPC interface defined in the TR069 specification, and obtaining information that the TR181 extended model file has been uploaded by parsing the second SOAP message body.

[0055] In one implementation, the method further includes: formulating an extended model specification, wherein the extended model specification includes at least one of the following file upload attributes of the TR181 extended model: file packaging format, file directory structure, file name, character encoding, and TR069 file type definition. It will be appreciated that to ensure the integrity of the TR181 extended model, attributes such as file packaging format, file target structure, file name, character encoding, and TR069 file type definition need to be configured for the TR181 extended model. Table 2 shows a rule corresponding to each file upload attribute.

[0056] Table 2.

[0057] The file format is CSV, which does not have a large number of repeated fields compared to the SOAP message body.

[0058] In one implementation, after receiving the TR181 extended model file uploaded by the terminal device, the method further includes: receiving the target key value of the index field corresponding to the service data sent by the terminal device during service operation; obtaining the value of the description field and the value of the internationalization field associated with the target key value from the uploaded TR181 extended model file. It is understandable that the network management device receives the service data sent by the terminal device during service operation, and can extract the target key value of the index field corresponding to the service data; and can obtain the value of the description field and the value of the internationalization field associated with the target key value based on the target key value. Through the above-mentioned association relationship, the TR181 extended model information of the target service data during operation can be obtained, such as extended fields, Chinese and English internationalization, and detailed information description.

[0059] Fig. 2 shows another flow chart of the method for extending a model in an embodiment of the present application, and the method 200 can be executed by a terminal device. As shown in Fig. 2 , the method can include the following steps.

[0060] S210: Acquire a preset TR181 extension model file of the target service.

[0061] Among them, the TR181 extended model file includes: an index field configured based on the type of the target business, at least one description field configured based on the description parameters of the target business, and an internationalization field that adds at least two language descriptions to the target field in the at least one description field based on the global adaptability of the target business. The TR181 extended model file records at least one association relationship, and the association relationship includes: the association relationship between the value of the index field, the value of the description field and the value of the internationalization field.

[0062] S220: Upload the TR181 extended model file to the network management device.

[0063] By uploading the TR181 extended model file to the network management device, the network management device can perform model extension based on the TR181 extended model file. Furthermore, during service operation, the terminal device only needs to send the value of the corresponding index field to the network management device. Based on this value, the network management device can obtain the values ​​of each description field corresponding to the value of the index field, thereby enabling the network management device to obtain relatively rich information, facilitating management by the network management device.

[0064] In one implementation, before uploading the TR181 extended model file to the network management device, the method may further include: receiving a file upload command from the network management device. The file upload command may be an RPC file upload command. RPC file upload is a basic interface channel for communication between the ACS and the terminal. By defining a new FileType, the channel can be reused. After receiving the FileType, the terminal device can upload the TR181 extended model file.

[0065] It is understandable that the terminal device may actively upload the TR181 extended model file to the network management device after accessing the network management device or at other appropriate times, or may upload the file after receiving a file upload command sent by the network management device.

[0066] Optionally, after uploading the TR181 extended model file, the terminal device may further send a message to the network management device to notify the network management device that the setting model file has been uploaded, for example, by notifying through a SOAP message body.

[0067] Optionally, due to the complexity of the terminal device functions themselves, one model file is usually unable to fully describe the terminal device functions. A functional service can contain multiple TR181 extended model files, so they can be compressed and packaged when uploading to achieve one-time upload. For example, for performance services, as shown in Table 2, one performance service corresponds to three TR181 extended model files: group.csv, KPI.csv, and mot.csv. When uploading files, the terminal can package them according to the packaging format described in Table 2, and name the packaged files according to the file packaging naming method in Table 2 and upload them at one time. The following examples are given for the above three TR181 extended model files. As shown in Table 3, it is an example of the content of KPI.csv; as shown in Table 4, it is an example of the content of mot.csv; as shown in Table 5, it is an example of the content of group.csv.

[0068] Table 3.

[0069] Table 4.

[0070] Table 5.

[0071] In an embodiment of the present application, the matching TR181 extension model file is uploaded to the network management device through the terminal device, which not only enables the obtained TR181 extension model to meet the target business requirements of the terminal device, but also improves the flexibility and availability of the TR181 extension model.

[0072] In one implementation, uploading the updated TR181 extended model file to the network management device includes uploading the updated TR181 extended model file to the network management device according to file upload attributes, wherein the file upload attributes include at least one of the following: file packaging format, file target structure, file name, character encoding, and TR069 file type definition. For details about the content of the file attributes, reference may be made to the relevant description in the embodiment shown in FIG1 and will not be repeated here.

[0073] In one implementation, after uploading the updated TR181 extended model file to the network management device, the method further includes: determining, during the operation of the target service, a target key value for an index field corresponding to service data that needs to be sent to the network management device; and sending the target key value to the network management device. In other words, when a terminal needs to report service data of the target service during operation, the network management device can associate the TR181 extended model with the service data during operation based on the index field, thereby improving the flexibility and usability of the TR181 extended model.

[0074] The embodiment shown in FIG. 1 to FIG. 2 will be described in detail below with reference to FIG. 3 .

[0075] S310: Monitoring that the terminal device is online.

[0076] S320: Issue a file upload command.

[0077] The network management device formulates a unified extension model based on different business characteristics, which can be adapted by all terminal manufacturers. For example, for alarm services, the network management device can extend the TR181 extension model file as shown in Table 1 above. The network management defines the header and the second line of the description example, and the terminal manufacturer fills in the third line. Therefore, the network management device needs to issue a business model file upload command at an appropriate time, where the upload method can be the RPC file upload method defined in the TR069 specification. The timing of the issuance can be selected when the terminal device is newly managed, the link status changes, or the scheduled scanning model is missing. Usually, the same model and the same version only include one set of business models, and there is no need to issue this command for each device.

[0078] S330: Parse the file upload command.

[0079] S340: Upload the business model file.

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

[0081] S350: Parse the business model file.

[0082] The network management device parses the business model uploaded by the terminal device and stores the business static fields in the database according to the unified platform model rules of the network management.

[0083] S360: Upload business data.

[0084] The terminal device generates service data during operation and reports the inform message to the network management according to the TR069 specification.

[0085] S370: Associating business data with business models.

[0086] The network management system parses runtime data and associates it with the service static model. Complete information is displayed on the front end. In the SOAP message body format of the inform message reported by the terminal, for alarm services, Device.FaultMgmt.ExpeditedEvent.{i}.ProbableCause can be associated with the static model in SOAP; for performance indicator statistics services, Device.PeriodicStatistics.SampleSet.{i}.Alias ​​can be associated with the static model.

[0087] S380: Commercial presentation.

[0088] As shown in Figure 4, it is a structural diagram of a commercial model expansion system, and the expansion system 400 of the model includes a network management device 410 and a terminal device 420. The network management device 410 includes the following components.

[0089] 1. The front-end UI module provides an interface for presenting network management features and functions, supporting user observation and operational interaction. A possible alternative solution is to pre-set the service data model by the network management system rather than uploading it to the network management system via the terminal device. When the terminal is not connected to the network management system, or is connected to the network management system but has no alarm events, the front-end UI module can present detailed information about the specific alarm, such as the alarm description, cause, alarm severity, alarm type, and handling method. When the terminal is connected to the network management system and an alarm is generated, packet capture is performed at the network management system's TR069 protocol adaptation layer to verify that the message fields in the alarm report SOAP body conform to the TR181 specification. These fields correspond to the individual fields of the alarm displayed by the network management system, but the information in the SOAP is significantly simplified. When the terminal is connected to the network management system and an alarm or performance statistics are generated, packet capture is performed at the network management system to verify that the TR181 INFORM message body reported is only in one language. However, the front-end UI module can switch to different locales, and the final alarm and performance data is displayed according to the different locales.

[0090] 2. Application service module, used to provide service responses supporting the front-end UI and obtain the data required by the front-end for feedback.

[0091] 3. Unified platform module, usually the underlying storage structure designed according to ITU-T telecommunications specifications, is used to provide unified warehousing and storage of application data.

[0092] 4. Protocol adapter module. Depending on the type of device being managed, there are typically multiple protocol adapters, such as TR069 protocol adapter and NETCONF protocol adapter. TR069 protocol adapter primarily includes: a. Support for protocol-specified identity authentication mechanisms, such as basic authentication, digest authentication, and certificate authentication; b. Support for protocol-specified RPC methods for communication and interaction with terminals; c. Support for message interaction using SOAP message bodies and request headers as specified in the protocol; d. Support for terminal message reporting and preliminary parsing. After parsing, the messages are encapsulated according to the network management structure and broadcast to relevant modules, such as alarm event reporting and performance statistics periodic reporting; e. Support for triggering operations through the network management system and sending them to terminals for execution, such as upgrades, restarts, and configuration activations.

[0093] Terminal devices 420 include various TR069-capable terminals in ground-to-air interconnection, factories and mines, enterprise parks, ports and terminals, office buildings, and home broadband. For example:

[0094] 1. Ground-to-air interconnection airborne CPE. Based on the 5G NR data backhaul function, it is installed in the equipment compartment and connects to the ground 5G NR base station to provide wireless backhaul for the onboard WiFi AP system.

[0095] 2. Industrial gateways help automate the on-site operations of unmanned vehicles, such as key equipment for on-site operations in the steel industry.

[0096] 3. Port industrial control application business terminals open up engineering control operation channels.

[0097] 4. Mine edge computing gateway terminal to assist in on-site operation video transmission.

[0098] 5. Production automation industrial parks use automated guided vehicles (AGVs) to automate logistics turnover.

[0099] 6. Home device terminals and personal wearable terminals.

[0100] The traditional TR069 device network management only parses the terminal runtime data through the TR069 protocol adaptation layer and presents it directly on the front end. There are problems such as the terminal runtime data only supports one language, some basic information is missing, and the information content is simple and has no complete description. In this application, the application service module can detect whether the TR069 extended model exists based on the terminal product version managed by the network management. If it does not exist, it will send an extended model upload command to the terminal device; parse and use the extended model uploaded by the terminal; the protocol adaptation module can receive the extended model upload message issued by the application layer, convert it into a SOAP message body for TR069 file upload, and send it to the terminal device through the RPC interface; receive the extended model uploaded by the terminal; the terminal device can respond to the extended model upload command and upload the model file in full through the https protocol.

[0101] In this embodiment, from the perspective of problem-solving flexibility, the terminal static model and business statistics are separated. The terminal business statistics focus on the collection and reporting of operation data, and the static model focuses on the understanding and abstraction of remote operation and maintenance of the network management. The loading method of the model is flexible. It can be reported passively or actively by the terminal, imported into the network management, and preset in the network management. From the perspective of applicability, the network management only formulates a static model that expands the TR069 specification, and the terminal manufacturer provides model adaptation. This capability can be quickly replicated in multiple terminal manufacturers and in multiple business modules. From the perspective of product competitiveness, terminal manufacturers that support model extension have higher operation and maintenance efficiency and lower costs. The network management manufacturer that formulates the extended model has a more user-friendly interface and richer information. It is stationed in high-end operators and enterprises as a basic capability, providing a guarantee for the product's operation and maintenance efficiency and operation and maintenance costs.

[0102] Optionally, as shown in Figure 5, an embodiment of the present application also provides an electronic device 500, including a processor 501 and a memory 502, and the memory 502 stores a program or instruction that can be run on the processor 501. When the program or instruction is executed by the processor 501, the various steps of the embodiments shown in Figures 1 to 4 above are implemented, and the same technical effect can be achieved. To avoid repetition, they are not repeated here.

[0103] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the embodiments shown in Figures 1 to 4 above are implemented, and the same technical effects can be achieved. To avoid repetition, they will not be repeated here.

[0104] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0105] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the embodiments shown in Figures 1 to 4 above, and can achieve the same technical effects. To avoid repetition, they will not be repeated here.

[0106] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0107] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium and is executed by at least one processor to implement the various processes of the embodiments shown in Figures 1 to 4 above, and can achieve the same technical effects. To avoid repetition, they are not described here.

[0108] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0109] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0110] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A model expansion method, applied to a network management device, comprising: Based on the type of the target service, configure an index field for the TR181 extended model file of the target service; Based on the description parameters of the target service, configuring at least one description field for the TR181 extended model file of the target service, wherein one description field is used to express a feature of the description parameter; Based on the global adaptability and global specifications of the target service, the length of each description field is set to achieve the extension of the TR181 extended model file.

2. The method according to claim 1, wherein: The setting of the length of each of the description fields based on the global adaptability and global specifications of the target business includes: Based on the global adaptability of the target business, adding an internationalized field described in at least two languages ​​to the target field in the at least one description field; The length of each of the description fields and each of the internationalization fields is set based on the standard expression of each of the description fields and the standard expression of each of the internationalization fields.

3. The method according to claim 1, wherein: After setting the length of each of the description fields based on the global adaptability and global specifications of the target business, the method further includes: Based on the semantics and length of each description field, filling rules are added to each field of the TR181 extended model file.

4. The method according to any one of claims 1 to 3, wherein: After setting the length of each of the description fields based on the global adaptability and global specifications of the target business, the method further includes: Sending a file upload command to the terminal device at a target time, wherein the file upload command is used to instruct uploading the TR181 extended model file corresponding to the terminal device; A TR181 extended model file uploaded by the terminal device is received, wherein the uploaded TR181 extended model file records at least one association relationship, and the association relationship includes: an association relationship between the value of the index field, the value of the description field and the value of the internationalization field.

5. The method according to claim 4, wherein: The sending of the file upload command to the terminal device includes: Convert the file upload command into a first Simple Object Access Protocol SOAP message body for TR069 standard file upload; The first SOAP message body is sent to the terminal device through the remote procedure call RPC interface defined by the TR069 specification.

6. The method according to claim 4, wherein: After receiving the TR181 extended model file uploaded by the terminal device, the method further includes: A second SOAP message body uploaded by the terminal device through the RPC interface defined in the TR069 specification is received, and by parsing the second SOAP message body, it is learned that the TR181 extended model file is uploaded successfully.

7. The method according to claim 4, wherein: The method further includes: formulating an extended model specification, wherein the content of the extended model specification includes: at least one of the following file upload attributes of the TR181 extended model file: file packaging format, file target structure, file name, character encoding, and TR069 file type definition.

8. The method according to claim 3, wherein: After receiving the TR181 extended model file uploaded by the terminal device, the method further includes: Receive the index field corresponding to the service data sent by the terminal device during the service operation Mark key values; The value of the description field and the value of the internationalization field associated with the target key value are obtained from the uploaded TR181 extended model file.

9. The method according to claim 4, wherein: The target timing includes one of the following: Determining that the current version of the terminal device lacks the corresponding business model file; Determining that the terminal device accesses the network management device for the first time; It is determined that a connection state with the terminal device changes.

10. A model expansion method, applied to a terminal device, the method comprising: Obtain a TR181 extension model file of a preset target service, wherein the TR181 extension model file includes: an index field configured based on the type of the target service, at least one description field configured based on the description parameters of the target service, and an internationalization field adding at least two language descriptions to a target field in the at least one description field based on the global adaptability of the target service, and the TR181 extension model file records at least one association relationship, wherein the association relationship includes: an association relationship between a value of the index field, a value of the description field, and a value of the internationalization field; The TR181 extended model file is uploaded to a network management device, so that the network management device performs model extension according to the TR181 extended model file.

11. The method according to claim 10, wherein: Before uploading the TR181 extended model file to the network management device, the method further includes: Receive a file upload command sent by the network management device.

12. The method according to claim 10, wherein: The uploading of the TR181 extended model file to the network management device includes: According to the file upload attribute, the TR181 extended model file is uploaded to the network management device. In the example, the file upload attribute includes at least one of the following: a file packaging format, a file target structure, a file name, a character encoding, and a TR069 file type definition.

13. The method according to any one of claims 10 to 12, wherein: After uploading the TR181 extended model file to the network management device, the method further includes: During the operation of the target service, a target key value of the index field corresponding to the service data is sent to the network management device.

14. An electronic device comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the model expansion method as described in any one of claims 1 to 13 are implemented.

15. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the model expansion method according to any one of claims 1 to 13.

Images