Model extension method, electronic equipment and storage medium

Abstract

The invention discloses a model extension method, electronic equipment and a storage medium, and belongs to the technical field of computers. The method comprises the following steps: based on the type of a target service, configuring an index field for a TR181 extension model file of the target service; based on the description parameters of the target service, at least one description field is configured for a TR181 extension model file of the target service, and one description field is used for expressing features of the description parameters; and setting the length of each description field based on the globalized fitness and global specification of the target service so as to realize the extension of the TR181 extension model file.

Description

Technical Field

[0001] 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

[0002] As a network management protocol for terminal devices, TR069 is increasingly being used in wireless coverage solutions, and related products are used in ground-to-air interconnection, factories and mines, enterprise parks, ports and docks, dense office buildings, and home broadband. Compared with the early Simple Network Management Protocol (SNMP), TR069 has made significant improvements in security, transmission protocols, and deployment methods. However, in actual applications, the TR181 model still cannot fully match the network management requirements, and there are problems with simple or incomplete descriptions of network management and operation information. Summary of the invention

[0003] The embodiments of the present application provide a model expansion method, an electronic device, and a storage medium, which can solve the problem of incomplete operation and maintenance information when the TR181 model is applied to a network management system.

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

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

[0006] In a second aspect, a model extension method is provided, which is applied to a terminal device, comprising: obtaining 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 languages ​​to the target field in the at least one description field based on the global adaptability of the target service, the TR181 extension 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; uploading the TR181 extension model file to a network management device.

[0007] In a third aspect, an electronic device is provided, comprising a processor and a memory, wherein the memory stores at least one computer program, and the at least one computer program is loaded and executed by the processor to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

[0008] In a fourth aspect, a storage medium is provided, wherein at least one computer program is stored in the storage medium, 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.

[0009] In a fifth aspect, a computer program product is provided, the computer program product comprising at least one computer program, the computer program being 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.

[0010] 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, and 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, and not only makes the length of the description field meet the needs of the target service, but also improves the flexibility and availability of the TR181 extended model.

[0011] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] 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.

[0013] Figure 1 A flow chart showing a method for expanding a model provided by an exemplary embodiment of the present application is shown;

[0014] Figure 2 Another flow chart of a method for extending a model provided by an exemplary embodiment of the present application is shown;

[0015] Figure 3 Another flow chart of a method for extending a model provided by an exemplary embodiment of the present application is shown;

[0016] Figure 4 A schematic diagram of the structure of an expansion system of a model provided by an exemplary embodiment of the present application is shown;

[0017] Figure 5 A structural block diagram of an electronic device provided by an exemplary embodiment of the present application is shown. DETAILED DESCRIPTION

[0018] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

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

[0020] With the rapid development of the fifth generation mobile communication technology (5G) communication network, high bandwidth, low latency, and high reliability are the basic characteristics and capabilities. More and more wireless coverage solutions are being applied to ground-to-air interconnection, factories and mines, enterprise parks, ports and docks, intensive office buildings, and home broadband, such as:

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

[0022] 2. With the increasing number of civil aviation passengers, in-flight networking has become an increasingly urgent basic demand of the civil aviation system. ATG (Air To Ground) uses mature ground mobile communication technology to build a ground-to-air broadband coverage network. ATG Customer Premise Equipment (CPE) can provide passengers with entertainment, office and black box data return services.

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

[0024] In summary, traditional network management based on the Simple Network Management Protocol (SNMP) is increasingly difficult to manage complex and numerous terminal devices. TR069, as a family of network management protocols for terminal devices, came into being. This protocol defines a new network management architecture, including the TR181 management node model, interactive interface and basic management parameters, so that different types and different manufacturers of equipment can be managed uniformly through the network, greatly improving the efficiency of terminal management and the universality of access to the Auto-Configuration Server (ACS) network management. Among them, the CPE WAN Management Protocol (CWMP), numbered TR-069, also known as the TR-069 protocol, includes a system specification of TR069, TR181, etc. This specification provides a new general framework for the management of network terminal devices, message specification definitions, and parameter node models. Among them, TR069 mainly defines the communication protocol specification and interaction process definition, and the TR181 specification defines the management node model.

[0025] Compared with the SNMP protocol, the TR069 protocol has made significant improvements in security, transmission protocol, and deployment methods, but it still has the following problems:

[0026] 1) Network management and operation information is simple, and the character length is too short, such as underlining simple English words without a complete description. This makes it difficult to locate problems on site, increasing costs and reducing efficiency.

[0027] 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). It can be seen that the character length specification is too small, which may lead to the inability to carry detailed alarm information, and cannot meet the effective guidance of on-site operation and maintenance. In addition, during on-site operation and maintenance, it is necessary to contact the network management or terminal manufacturer for further support and positioning.

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

[0029] For example, in the TR069 protocol, key fields for alarm services are not defined, such as alarm handling suggestions and alarm code names, which play an important role in guiding the rapid resolution of alarm events on site and are also the data basis for wizard-based alarms in To Business (ToB) network management. However, due to the missing TR069 protocol fields, the corresponding network management functions are not available.

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

[0031] Specifically, the specification does not define the international description of parameter values ​​of the String type. This means that no matter what language or languages ​​the network management supports, only one language is supported in the services corresponding to the terminal. 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.

[0032] In addition, TR069 defines that the communication protocol stack between ACS and CPE is based on the SOAP message body for RPC method calls. The number of fields and character length will increase the size of the SOAP message body. At present, there are a large number of repeated tags in conventional SOAP messages. Adding fields or detailed descriptions and international content will increase the size of the SOAP message body. Moreover, message transmission requires higher network bandwidth, large messages take a long time to transmit, and are more likely to be affected by network fluctuations, which places higher requirements on upper-layer application retry.

[0033] In view of this, the present application proposes a model expansion method, electronic device and storage medium, which have solved the above-mentioned problems, reduced the operation and maintenance costs of terminal equipment, and improved customer response speed and product competitiveness.

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

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

[0036] It is understandable that, since different types of services have different TR181 extension model files, the network management device can configure an index field for the TR181 extension model file of the target service according to the type of the target service corresponding to the terminal. In other words, the TR181 extension 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.

[0037] 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.

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

[0039] It is understandable 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 according to 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 alarm cause, the alarm handling suggestion, the alarm type, 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 metrics. 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 relevant service events are not generated during the operation period.

[0040] S130: Based on the global adaptability and global specifications of the target service, the length of each description field is set to extend the TR181 extended model file.

[0041] It is understandable that in order to ensure the consistency and operability of the data, 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 setting of the field length can be reasonably set according to the global adaptability and global standards of the target business. Too long or too short field length may affect the storage and transmission efficiency of the data. For example, for the alarm type field, all alarm types can be enumerated to obtain the longest alarm type value, thereby determining the length of the alarm type field.

[0042] 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, and 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, and not only makes the length of the description field meet the needs of the target service, but also improves the flexibility and availability of the TR181 extended model.

[0043] 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 according to the extended TR181 extended model file, and the association relationship includes: an association relationship between the value of the index field and the value of each description field, so that the network management device can obtain the value 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.

[0044] In one implementation, the setting of the length of each of the description fields based on the global adaptability and global specifications of the target business may include: adding internationalized fields described in at least two languages ​​to the target field in the at least one description field based on the global adaptability of the target business; and setting the length of each of the description fields and the internationalized fields based on the standardized expression of each of the description fields and the standardized expression of each of the internationalized 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 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 user group and market requirements. In addition, in order for the description field to carry detailed information, it is necessary to set the length of each description field and the internationalized field based on the global specifications of each description field and the internationalized field.

[0045] In the above implementation of the present application, in order to make the length of each description field and internationalization field 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 referring to different alarm types by different numbers. For another example, for the alarm reason field, the length of the alarm reason field can be determined according to the standard expression of the alarm reason, for example, the expression of who does what, and then according to the length of all possible expressions of "who" and the length of all possible expressions of "what to do". For another example, for the alarm code name English field, the length corresponding to the longest expression can be determined as the length of the alarm code name English field by enumerating all English expressions of the alarm code names.

[0046] In one implementation, after setting the length of each of the description fields based on the global adaptability and global specifications of the target service, the method further includes: adding filling rules for each field of the TR181 extension model file based on the semantics and length of each description field. Exemplarily, as shown in Table 1, a TR181 extension model designed by a network management device for a terminal device according to the characteristics of the target service.

[0047] Table 1.

[0048]

[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 processing suggestion, English name of processing suggestion, alarm type, alarm level, code value type, where 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, and the manufacturer corresponding to the terminal device can only fill in the number corresponding to the alarm level when filling in 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, which helps to ensure the accuracy, consistency and integrity of data and improve the quality and availability of data.

[0050] In one implementation, after the length of each of the description fields is set 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 can be understood that after the length of each of the description fields is set 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 the target time.

[0051] Among them, 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; determining that the connection state with the terminal device has changed. That is, if the current version of the terminal device lacks the corresponding business model file or the model terminal device is connected to the network management device for the first time or the connection state between the network management device and the terminal device has changed, a file upload command is sent to the terminal device.

[0052] In one implementation, the sending of the file upload command to the 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 through a remote procedure call RPC interface defined in the TR069 specification. It is understandable that TR069 defines communication protocol specifications and interaction processes, and can perform unified remote management and configuration on 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 a data carrier transmitted in the SOAP protocol, and is usually expressed 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, and management efficiency, security, and data transmission reliability can be improved. Sending the first SOAP message body through a remote procedure call protocol (RPC) interface can achieve remote calls across networks, which can not only support cross-language communication, but also improve 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 through the RPC interface defined in the TR069 specification; parsing the TR181 extended model file to obtain the TR181 extended model file uploaded by the terminal device. It is understandable 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, and 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 also include receiving a second SOAP message body uploaded by the terminal device through the RPC interface defined in the TR069 specification, and learning 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 content of 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 is understandable that in order to ensure the integrity of the TR181 extended model, it is necessary to configure attributes such as file packaging format, file target structure, file name, character encoding, and TR069 file type definition for the TR181 extended model. As shown in Table 2, a rule corresponding to each file upload attribute.

[0056] Table 2.

[0057]

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

[0059] In one implementation, after receiving the TR181 extended model file uploaded by the terminal device, the method further includes: receiving a target key value of an index field corresponding to the service data sent by the terminal device during service operation; and 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.

[0060] Figure 2 Another flow chart of the method for extending the model in the embodiment of the present application is shown, and the method 200 can be executed by a terminal device. Figure 2 As shown, the method may include the following steps.

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

[0062] 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 languages ​​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.

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

[0064] By uploading the TR181 extended model file to the network management device, the network management device can perform model extension according to the TR181 extended model file. In addition, during service operation, the terminal device only needs to send the value of the corresponding index field to the network management device, and the network management device can obtain the value of each description field corresponding to the value of the index field according to the value, thereby enabling the network management device to obtain relatively rich information, which is convenient for the network management device to manage.

[0065] 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 sent by the network management device. The file upload command may be an RPC file upload command, and the RPC file upload is a basic interface channel for communication between the ACS and the terminal. The channel can be reused by newly defining a FileType, and the terminal device can upload the TR181 extended model file after receiving the FileType.

[0066] 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.

[0067] Optionally, after uploading the TR181 extended model file, the terminal device may also 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.

[0068] Optionally, due to the complexity of the terminal device functions themselves, one model file is usually unable to fully describe the functions of the terminal device. 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.

[0069] Table 3.

[0070]

[0071] Table 4.

[0072]

[0073]

[0074] Table 5.

[0075]

[0076] 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 acquired TR181 extension model to meet the target service requirements of the terminal device, but also improves the flexibility and availability of the TR181 extension model.

[0077] 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 the file upload attribute, wherein the file upload attribute includes at least one of the following: file packaging format, file target structure, file name, character encoding, and TR069 file type definition. Figure 1 The relevant description in the illustrated embodiment will not be repeated here.

[0078] In one implementation, after uploading the updated TR181 extension model file to the network management device, the method further includes: during the operation of the target service, determining the target key value of the index field corresponding to the 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, the terminal needs to report the service data of the target service during operation, and the network management device can associate the TR181 extension model with the service data during operation according to the index field, thereby improving the flexibility and availability of the TR181 extension model.

[0079] Below through Figure 3 For the above Figure 1 to Figure 2 The illustrated embodiment is described in detail.

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

[0081] S320: Issue a file upload command.

[0082] The network management equipment formulates a unified extension model according to different business characteristics, and each terminal manufacturer can adapt it. For example, for the alarm service, the network management equipment 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 from the new management of the terminal device, the change of the link state, or the scheduled scanning model missing situation. 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.

[0083] S330: Parse the file upload command.

[0084] S340: Upload the business model file.

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

[0086] S350: Parse the business model file.

[0087] 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.

[0088] S360: Upload business data.

[0089] The terminal device will report the service data generated during operation to the network management system in the form of inform messages according to the TR069 specification.

[0090] S370: Associating the business data with the business model.

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

[0092] S380: Commercial presentation.

[0093] like Figure 4 As shown, 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. Among them, the network management device 410 includes the following components:

[0094] 1. The front-end UI module is used to provide the interface presentation of the network management feature functions and support user observation and operation interaction. A possible alternative is that the business data model is not uploaded to the network management through the terminal device, but is preset by the network management. When the terminal is not connected to the network management or has been connected to the network management but there is no alarm event, the front-end UI module can present detailed information of the specific alarm, such as alarm description, cause, alarm level, alarm type, and disposal method; when the terminal is connected to the network management and an alarm is generated, the network management TR069 protocol adaptation layer is used to capture packets and check the message fields of the TR181 specification in the alarm report SOAP body, which correspond to the individual fields of the alarm finally presented by the network management, but the information in the SOAP is obviously simple; when the terminal is connected to the network management and an alarm or performance statistics is generated, the network management is used to capture packets and check that the reported TR181 INFORM message body has only one language, while the front-end UI module can switch to different language environments, and the final alarm and performance data are displayed according to different language environments.

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

[0096] 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.

[0097] 4. Protocol adapter module: Depending on the type of managed equipment, there are usually multiple protocol adapters, such as TR069 protocol adapter, NETCONF protocol adapter, etc. TR069 protocol adapter mainly includes:

[0098] a. Support the identity authentication mechanisms specified in the protocol, such as basic authentication, summary authentication, and certificate authentication.

[0099] b. Support the RPC method specified in the protocol and communicate and interact with the terminal;

[0100] c. Support message interaction based on the SOAP message body and request header specified by the protocol.

[0101] d. Support terminal message reporting and perform preliminary analysis. After analysis, it is encapsulated according to the network management structure and broadcast to related modules, such as alarm event reporting and performance statistical periodic reporting.

[0102] e. Support triggering operations through the network management and sending them to the terminal for execution, such as: upgrade, restart, configuration activation.

[0103] The terminal device 420 includes various terminals supporting the TR069 protocol in ground-to-air interconnection, factories and mines, enterprise parks, ports and docks, office buildings, and home broadband, for example:

[0104] 1. Ground-to-air interconnection airborne station CPE. Based on the data backhaul function of 5G NR, it is installed in the equipment cabin and connected to the ground 5G NR base station to perform wireless backhaul for the onboard WiFi AP system;

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

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

[0107] 4. Mine edge computing gateway terminal assists in transmitting operation videos on site.

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

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

[0110] The traditional TR069 device network management only parses the terminal runtime data through the TR069 protocol adaptation layer and directly presents it 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 according to 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 completely through the https protocol.

[0111] 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, and the terminal can report passively or actively, import it in the network management, and preset it 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, which can quickly replicate this capability in multiple terminal manufacturers and in multiple business modules. From the perspective of product competitiveness, terminal manufacturers that support model expansion 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 cost.

[0112] Optional, such as Figure 5 As shown, the embodiment of the present application also provides an electronic device 500, including a processor 501 and a memory 502, the memory 502 stores a program or instruction that can be run on the processor 501, and the program or instruction is executed by the processor 501 to implement the above Figures 1 to 4 The various steps of the illustrated embodiments can achieve the same technical effect, and will not be described again here to avoid repetition.

[0113] The 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 above Figures 1 to 4 The various processes of the illustrated embodiments can achieve the same technical effect, and will not be described again here to avoid repetition.

[0114] 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-transient readable storage medium.

[0115] The present application also 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 a program or instruction to implement the above Figures 1 to 4 The various processes of the illustrated embodiments can achieve the same technical effect, and will not be described again here to avoid repetition.

[0116] 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.

[0117] The present application embodiment further provides a computer program / program product, wherein the computer program / program product is stored in a storage medium, and the computer program / program product is executed by at least one processor to implement the above Figures 1 to 4 The various processes of the illustrated embodiments can achieve the same technical effect, and will not be described again here to avoid repetition.

[0118] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including 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 one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment 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 reverse 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.

[0119] Through the description of the above implementation methods, 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 hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable a terminal or a network-side device to execute the methods described in each embodiment of the present application.

[0120] 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 the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.

Claims

1. A model expansion method, applied to a network management device, characterized in that: The method comprises: 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, characterized in that 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, characterized in that 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, characterized in that: 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that After receiving the TR181 extended model file uploaded by the terminal device, the method further includes: Receiving a target key value of an index field corresponding to service data sent by the terminal device during service operation; 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, characterized in that The target timing includes 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, characterized in that: The method comprises: 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 the value of the index field, the value of the description field, and the 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, characterized in that 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, characterized in that The uploading of the TR181 extended model file to the network management device includes: The TR181 extended model file is uploaded to the network management device according to the file upload attribute, wherein the file upload attribute includes at least one of the following: file packaging format, file target structure, file name, character encoding, and TR069 file type definition.

13. The method according to any one of claims 10 to 12, characterized in that: 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, characterized in that: The method comprises 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 according to any one of claims 1 to 13 are implemented.

15. A storage medium, characterized in that: The storage medium stores programs or instructions, and when the programs or instructions are executed by the processor, the steps of the model expansion method as described in any one of claims 1 to 13 are implemented.

Images