CN113765957A

CN113765957A - Model updating method and device

Info

Publication number: CN113765957A
Application number: CN202010500882.3A
Authority: CN
Inventors: 黄谢田; 秦东润; 曹龙雨; 于益俊
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-06-04
Filing date: 2020-06-04
Publication date: 2021-12-07
Anticipated expiration: 2040-06-04
Also published as: WO2021244377A1; CN113765957B

Abstract

The embodiment of the application provides a model updating method and device, relates to the field of communication, and can reduce resource waste caused by model updating. The method comprises the following steps: the first device receives a first message from the second device, and acquires the model file according to the first message. The first message includes identification information of the model file and path information of the model file, or the first message includes the model file and the identification information of the model file. The first device may also receive a second message from the second device, the target model being activated in dependence on the second message and the model file, the second message comprising identification information of the model file and identification information of the target model.

Description

Model updating method and device

Technical Field

The embodiment of the application relates to the field of communication, in particular to a model updating method and device.

Background

5G (5th-Generation, fifth Generation mobile communication technology) networks bring operators richer traffic types, while also requiring more efficient resource management schemes and more flexible network architectures to facilitate business innovations. Radio access networks are evolving towards more open and intelligent directions.

The intelligent wireless network architecture includes functional modules, such as an operation, administration and maintenance (OAM) module, a Radio Access Network (RAN), a first wireless controller and a second wireless controller. The first wireless controller is mainly used for providing the function of a control plane of a wireless network, and the second wireless controller and the OAM are mainly used for providing the function of a management plane. The first wireless controller and the second wireless controller may implement the functional service by deploying different service function modules, wherein a class of service function modules (hereinafter, referred to as ML-based service function modules) using a Machine Learning (ML) model exists in the first wireless controller. The ML-based service function module can realize service functions by utilizing an ML model, and the performance of the RAN network is improved.

The ML model used by the ML-based service function module can be updated by updating the mirror software package. The mirror image software package also comprises software such as a basic operating system and a third-party plug-in besides the relevant model files, and the size is usually very large (hundred MB level or even GB level), so that a large amount of redundant information needs to be transmitted on relevant interfaces when the ML model is updated, a large amount of interface bandwidth is occupied, and resource waste is caused.

Disclosure of Invention

The embodiment of the application provides a model updating method and device, which can reduce resource waste caused by model updating.

In a first aspect, a model updating method is provided, including: the first device receives a first message from the second device, and acquires the model file according to the first message. The first message includes identification information of the model file and path information of the model file, or the first message includes the model file and the identification information of the model file. The first device may also receive a second message from the second device, the second message including identification information of the target model and identification information of the model file, and activate the target model based on the second message and the model file.

In the method provided by the embodiment of the application, model management can be performed based on the model file. For example, when a model is updated, the model file or information of the model file is transmitted through the relevant interface, so that only the model file can be updated and replaced. The model can be updated without transmitting a mirror image software package, thereby avoiding occupying a large amount of interface bandwidth to transmit information which is not needed by the model updating and reducing resource waste and time delay brought by the model updating.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the identification information of the model file includes at least one of: file identification information, identification information of a device using the target model, model identification information, or version information of the model file; the identification information of the target model includes at least one of: identification information of a device using the target model, model identification information. The model identification information is used to indicate a model, for example, the model identification information in the identification information of the model file may indicate a model using the model file, that is, the target model described in the embodiment of the present application.

The embodiment of the application also provides several possibilities of model file identification, and the corresponding model can be indexed according to the identification of the model file so as to update the model based on the model file.

With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the obtaining, by the first device, the model file according to the first message includes: the first equipment acquires the model file according to the path information, wherein the path information is used for indicating the storage path of the model file; or the first equipment analyzes the first message to obtain the model file.

The embodiment of the application also provides two possibilities of obtaining the model file. When the first message is a file downloading message, the first message includes path information of the model file, and the first device can acquire the model file at a storage path indicated by the path information; when the first message is a file transfer message, the first message includes a model file, and the first device analyzes the first message after receiving the first message to obtain the model file.

With reference to the first aspect or the first or second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, the activating, by the first device, the target model according to the second message and the model file includes: and the first equipment updates the model file of the target model according to the model file and operates the target model.

The embodiment of the application also provides a specific implementation mode for activating the model according to the obtained model file, the obtained new model file can be used for replacing the currently used model file of the target model, and the model can be updated based on the model file.

With reference to the first aspect or any one of the first to third possible implementation manners of the first aspect, in a third possible implementation manner of the first aspect, the second message further includes a model list; the model list includes at least one model identification.

The method provided by the embodiment of the application is suitable for a scene in which a plurality of models use the same model file, and in the scene, different model files are distinguished by using file identifiers. The model list comprises at least one model identification, and the at least one model identification corresponds to the file identification, namely, the model corresponding to the at least one model identification uses the model file corresponding to the file identification. The list of models is indicated by the second message so that multiple models are updated using the same model file.

With reference to the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the activating, by the device, the target model according to the second message and the model file includes: and the first equipment updates the model file of the at least one target model corresponding to the at least one model identification according to the model file and runs the at least one target model.

According to the method provided by the embodiment of the application, the plurality of models can be determined according to the model list, and the plurality of models are updated by using the new model file, so that the repeated transmission of the model files for the plurality of models is avoided, and transmission resources are saved.

With reference to the first aspect or the first to fifth possible implementations of the first aspect, in a sixth possible implementation of the first aspect, the second message further includes activation information of the target model; the activation information comprises an activation type of the target model and/or an activation time of the target model; wherein the activation type includes immediate activation, delayed activation, timed activation or periodic activation.

In the method provided by the embodiment of the application, the timed activation of the model can be realized by combining the activation type and the activation information.

With reference to the first aspect or the first to sixth possible implementation manners of the first aspect, in a seventh possible implementation manner of the first aspect, the first message further includes a file type; the file type includes a model file type and/or a sub-model file type.

In the method provided by the embodiment of the application, the file can also be indicated as a model file type, so that the first device can determine that the newly acquired file is the model file, and update the model based on the model file. In addition, model updating can be realized based on the sub-model file, and more detailed model management can be realized.

In a second aspect, a model updating method is provided, including: and the second equipment sends a first message to the first equipment to instruct the first equipment to acquire the model file. The first message includes identification information of the model file and path information of the model file, or the first message includes the model file and the identification information of the model file. The second device may also send a second message to the first device instructing the first device to activate the target file using the model file. Wherein the second message comprises identification information of the target model and identification information of the model file.

With reference to the second aspect, in a first possible implementation manner of the second aspect, the identification information of the model file includes at least one of the following: file identification information, identification information of a device using the target model, model identification information, or version information of the model file; the identification information of the object model includes identification information of a device using the object model, and/or model identification information.

With reference to the second aspect or the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the second message further includes a model list; the model list includes at least one model identification.

With reference to the second aspect or the first or second possible implementation manner of the second aspect, in a third possible implementation manner of the second aspect, the second message further includes activation information of the target model; the activation information comprises an activation type of the target model and/or an activation time of the target model; wherein the activation type includes immediate activation, delayed activation, timed activation or periodic activation.

With reference to the second aspect or any one of the first to third possible implementation manners of the second aspect, in a fourth possible implementation manner of the second aspect, the first message further includes a file type; the file type includes a model file type and/or a sub-model file type.

In a third aspect, a model updating method is provided, including: the first device receives a first message from the second device, the first message including a first parameter; the first parameter is used for describing the storage position of a model file of the target model; the first equipment acquires a model file according to the first parameter; the first device receives a second message from the second device, wherein the second message comprises a second parameter, and the second parameter is used for describing the state of the target model; the first device activates the target model according to the second parameters in the second message and the model file.

In the method provided by the embodiment of the application, the MOC may be defined for the model, and the attribute parameters of the model may describe characteristics such as a storage location of the model file and a state of the model. The first device is further instructed to acquire a new model file by modifying the attribute parameters of the model and to activate the model according to the new model file. The information which is not needed by the transmission model updating is prevented from occupying a large amount of bandwidth resources, and the model updating can be realized based on the model file.

With reference to the third aspect, in a first possible implementation manner of the third aspect, the first message further includes an identifier of the model file; the identification information of the model file includes at least one of: identification information of a device using the target model, model identification information, and version information of the model file.

With reference to the third aspect or the first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, the second message further includes identification information of the target model, and the identification information of the target model may be identification information of a device that uses the target model, and/or model identification information.

In the method provided by the embodiment of the application, the identification information of the model can be further indicated when the model is activated, so that the first device identifies the model to be updated and updates the model based on the newly acquired model file.

With reference to the first possible implementation manner of the third aspect, in a third possible implementation manner of the third aspect, the first device may further modify a value of a third parameter of the target model according to the version information of the model file; the third parameter is used to describe the version of the model file currently used by the target model.

In the method provided by the embodiment of the present application, the MOC of the model may include attribute parameters describing a version of the model, so as to record an updated version of the model.

With reference to the third aspect or the first to third possible implementation manners of the third aspect, in a fourth possible implementation manner of the third aspect, before the first device activates the target model according to the second parameter in the second message and the model file, the method further includes: the first device receiving a third message from the second device; the third message includes a second parameter; the first device deactivates the target model according to the second parameter in the third message.

In the embodiment of the application, before the model is updated, the model can be deactivated by a method of modifying the MOC attribute parameters of the model, so that sudden interruption of model service caused by direct updating of the model file is avoided.

With reference to the third aspect or the first to fourth possible implementation manners of the third aspect, in a fifth possible implementation manner of the third aspect, the activating, by the first device, the target model according to the second parameter in the second message and the model file includes: and if the value of the second parameter indicates that the state of the target model is activated, the first device updates the model file of the target model according to the model file and operates the target model.

In a fourth aspect, a model updating method is provided, including: the second equipment sends a first message to the first equipment, wherein the first message comprises a first parameter; the first parameter is used to describe a storage location of a model file of the target model. The second device may also send a second message to the first device, the second message including second parameters describing a state of the target model.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the first message further includes an identifier of the model file; the identification information of the model file includes at least one of: identification information of a device using the target model, model identification information, and version information of the model file.

With reference to the fourth aspect or the first possible implementation manner of the fourth aspect, in a second possible implementation manner of the fourth aspect, the second message further includes identification information of the target model, and the identification information of the target model may be identification information of a device using the target model, and/or model identification information.

In a fifth aspect, there is provided an apparatus, which may be the first device, or a component in the first device, according to embodiments of the present application. The device comprises: a communication unit for receiving a first message from a second device; the first message comprises identification information of the model file and path information of the model file, or the first message comprises the model file and the identification information of the model file; the processing unit is used for acquiring the model file according to the first message; the communication unit is further configured to receive a second message from the second device, the second message including identification information of the target model and identification information of the model file; the processing unit is further configured to activate the target model based on the second message and the model file.

The device provided by the embodiment of the application can be used for carrying out model management based on the model file. For example, when a model is updated, the model file or information of the model file is transmitted through the relevant interface, so that only the model file can be updated and replaced. The model can be updated without transmitting a mirror image software package, thereby avoiding occupying a large amount of interface bandwidth to transmit information which is not needed by the model updating and reducing resource waste and time delay brought by the model updating.

With reference to the fifth aspect, in a first possible implementation manner of the fifth aspect, the identification information of the model file includes at least one of: file identification information, identification information of a device using the target model, model identification information, or version information of the model file; the identification information of the target model includes model identification information and/or identification information of a device using the target model.

With reference to the fifth aspect or the first possible implementation manner of the fifth aspect, in a second possible implementation manner of the fifth aspect, the processing unit is specifically configured to obtain the model file according to path information, where the path information is used to indicate a storage path of the model file; or analyzing the first message to obtain the model file.

With reference to the fifth aspect or the first or second possible implementation manner of the fifth aspect, in a third possible implementation manner of the fifth aspect, the processing unit is specifically configured to update a model file of the object model according to the model file, and run the object model.

With reference to the fifth aspect or the first to third possible implementations of the fifth aspect, in a fourth possible implementation of the fifth aspect, the second message further includes a model list; the model list includes at least one model identification.

With reference to the fourth possible implementation manner of the fifth aspect, in a fifth possible implementation manner of the fifth aspect, the processing unit is specifically configured to update, according to the model file, a model file of the at least one object model corresponding to the at least one model identifier, and run the at least one object model.

With reference to the fifth aspect or any one of the first to fifth possible implementation manners of the fifth aspect, in a sixth possible implementation manner of the fifth aspect, the second message further includes activation information of the target model; the activation information comprises an activation type of the target model and/or an activation time of the target model; wherein the activation type includes immediate activation, delayed activation, timed activation or periodic activation.

With reference to the fifth aspect or any one of the first to sixth possible implementation manners of the fifth aspect, in a seventh possible implementation manner of the fifth aspect, the first message further includes a file type; the file type includes a model file type and/or a sub-model file type.

In a sixth aspect, there is provided an apparatus comprising: a communication unit for receiving a first message from a second device, the first message including a first parameter; the first parameter is used for describing the storage position of a model file of the target model; the processing unit is used for acquiring a model file according to the first parameter; the communication unit is further configured to receive a second message from the second device, the second message including a second parameter, the second parameter being used to describe a state of the target model; the processing unit is further configured to activate the target model based on the second parameter in the second message and the model file.

With reference to the sixth aspect, in a first possible implementation manner of the sixth aspect, the first message further includes an identifier of the model file; the identification information of the model file includes at least one of: identification information of a device using the target model, model identification information, and version information of the model file.

With reference to the sixth aspect or the first possible implementation manner of the sixth aspect, in a second possible implementation manner of the sixth aspect, the second message further includes identification information of the target model, and the identification information of the target model may be identification information of a device using the target model, and/or model identification information.

With reference to the sixth aspect or the first possible implementation manner of the sixth aspect, in a third possible implementation manner of the sixth aspect, the processing unit is further configured to modify a value of a third parameter of the target model according to version information of the model file; the third parameter is used to describe the version of the model file currently used by the target model.

With reference to the sixth aspect or any one of the first to third possible implementation manners of the sixth aspect, in a fourth possible implementation manner of the sixth aspect, the communication unit is further configured to receive, before the processing unit activates the target model according to the second parameter in the second message and the model file, a third message from the second device; the third message includes a second parameter; the processing unit is further configured to deactivate the target model according to the second parameter in the third message.

With reference to the sixth aspect or any one of the first to fourth possible implementation manners of the sixth aspect, in a fifth possible implementation manner of the sixth aspect, the processing unit is specifically configured to, if the value of the second parameter indicates that the state of the target model is active, update, by the first device, a model file of the target model according to the model file, and run the target model.

In a seventh aspect, a communications apparatus is provided that includes at least one processor and a memory, the at least one processor coupled with the memory; the memory for storing a computer program;

the at least one processor is configured to execute the computer program stored in the memory to cause the apparatus to perform the method according to any one of the implementations of the first aspect and the first aspect, or the method according to any one of the implementations of the third aspect and the second aspect.

In an eighth aspect, a communications apparatus is provided that includes at least one processor and a memory, the at least one processor coupled with the memory; the memory for storing a computer program;

the at least one processor is configured to execute the computer program stored in the memory to cause the apparatus to perform the method according to any one of the second aspect and the second implementation manner described above, or the method according to any one of the fourth aspect and the fourth implementation manner described above.

In a ninth aspect, there is provided a computer-readable storage medium comprising: the computer readable storage medium has instructions stored therein; when the computer readable storage medium is run on the communication apparatus according to any one of the above-mentioned fifth aspect and fifth aspect, the communication apparatus is caused to perform the communication method according to any one of the above-mentioned first aspect and first aspect.

In a tenth aspect, there is provided a computer-readable storage medium comprising: the computer readable storage medium has instructions stored therein; when the computer readable storage medium is run on the communication apparatus according to any one of the above-mentioned implementations of the sixth aspect, the communication apparatus is caused to perform the communication method according to any one of the above-mentioned implementations of the third aspect.

In an eleventh aspect, a wireless communication device is provided, which includes a processor, and is applied to a communication device, for example, a chip system, to implement the method according to the first aspect and any one implementation manner of the first aspect. In a possible implementation, the chip system further comprises a memory for storing program instructions and data necessary for implementing the functions of the method according to the first aspect.

A twelfth aspect provides a wireless communication device, which includes a processor, and is applied to a communication device, for example, a chip system, to implement the functions or methods according to any one of the implementation manners of the third aspect and the third aspect. In a possible implementation, the chip system further comprises a memory for storing program instructions and data necessary for implementing the functions of the method according to the third aspect.

The system-on-chip in the above aspect may be a system-on-chip (SOC), a baseband chip, and the like, where the baseband chip may include a processor, a channel encoder, a digital signal processor, a modem, an interface module, and the like.

Drawings

FIG. 1 is a diagram of a system architecture provided by an embodiment of the present application;

FIG. 2 is a block diagram of an apparatus according to an embodiment of the present disclosure;

fig. 3 to 14 are schematic flow charts of a model updating method according to an embodiment of the present application;

fig. 15 to 18 are block diagrams of another structure of the apparatus according to the embodiment of the present application.

Detailed Description

The method provided by the embodiment of the application is suitable for the system architecture shown in fig. 1. Referring to fig. 1, the system includes a RAN, an OAM, a first radio controller, a second radio controller, and the like. The OAM is responsible for operation and maintenance management, such as fault management, performance management, configuration management, etc.;

the first radio controller is mainly used for providing functions of a radio network control plane, for example, performing near real-time control and optimization on functional network elements and resources in the system. The first wireless controller includes a business function module that implements a business of the first wireless controller using a model (e.g., a machine learning model). For example, the ML model is used to process network data acquired by the first wireless controller, and data such as user report amount and resource utilization rate is input to the ML model to output prediction indexes such as throughput. The service can be adjusted and optimized according to the prediction indexes, for example, the user is instructed to perform cell switching and the like;

the second radio controller is mainly used for providing functions of a management plane, for example, performing non-real-time control and optimization on functional network elements and resources in the system.

It should be noted that a service function module may be considered as a function module for implementing a certain service, or a component for implementing a certain service, for example, may be an Application (APP).

Referring to fig. 1, the second wireless controller may include a model management unit and a model storage unit. The Model management unit can be called a Model Manager and is responsible for managing the life cycle of the Model, and the life cycle comprises the processes of triggering Model deployment, Model training, Model updating, Model monitoring and the like; the model storage unit can be called Training Catalog and is used for storing the model files stored after Training.

The first wireless controller may include a Model management client, which may be referred to as a Model MnS (management Service) Agent, for performing lifecycle management on the Model according to the instruction of the Model Manager, such as Model activation, Model update, or Model deactivation, and a Service function module based on the ML Model. The service management module based on the ML model is a functional module for realizing the service by using the ML model.

It should be noted that the model management unit, the model storage unit, and the model management client are modules that are functionally divided, and may be combined with an existing network element or serve as an independent network element, which is not limited in this embodiment of the present application.

First, terms related to embodiments of the present application are explained:

(1) ML model

The ML model, i.e., the machine learning model, can be considered as an algorithm that implements computer automatic "learning". In this embodiment of the application, the service function module in the first wireless controller may use the ML model to perform automatic learning by using the collected data, so as to implement a specific service function and improve network performance. For example: the performance of the UE in the cell, for example, the throughput of the UE, is predicted according to indexes such as Reference Signal Receiving Power (RSRP), Reference Signal Receiving Quality (RSRQ), or signal to interference plus noise ratio (SINR) reported by the UE in the existing network and the resource utilization of the cell, and a cell with the best performance is selected (or switched) according to the prediction result.

(2) Model files

The model file is used to record information of the model, for example, structural information of the model or parameters of the model. The structure information of the model may indicate input or output of the model, and may also indicate a network structure adopted by the model, for example: convolutional neural networks, fully connected networks, etc. The parameters of the model may be weights, biases, gradient values, etc. of the network.

(3) File type

The file type is used to describe a specific type of file. For example, the file type may be a model file type, which means that the file is a model file, i.e. the file is used to record information of a certain model.

In one possible implementation, a model may be divided into a plurality of functional blocks, which provide different algorithms, which may be referred to as submodels. The model may contain a plurality of sub-models. In this scenario, the file type may be a sub-model file type, which means that the file is a model file of a sub-model, that is, the file is used to record information of a certain sub-model.

In the embodiment of the present application, the parameter "file type" is used to describe a file type. The value of the "file type" can be "model file", which represents that the file type is a model file type, and the file is a model file; the value of "file type" may also be that "sub model file" represents that the file type is a sub model file type, and the file is a model file of the sub model.

It should be noted that the parameter "file type" may also take other values, representing other file types. For example, the image file represents an image software package, and the license file represents a license file.

The embodiment of the application provides a model updating method, wherein a first device (for example, a first wireless controller) receives a first message from a second device (for example, a second wireless controller), and acquires a model file according to the first message. Wherein the first message includes identification information of the model file and path information of the model file, or the first message includes identification information of the model file and the model file; and the first device receives a second message from the second device, and activates a target model according to the second message and the model file, wherein the second message comprises identification information of the model file and/or identification information of the target model.

The method provided by the embodiment of the present application is applicable to the apparatus 20 shown in fig. 2, where the apparatus may be the first device or the second device described in the embodiment of the present application, for example, the apparatus may be a network element integrating a first wireless controller, or a network element integrating a second wireless controller. Fig. 2 is a schematic diagram of the hardware structure of the apparatus 20. The apparatus 20 may be deployed on a computing device, or may be the computing device described in this application. Referring to fig. 2, the apparatus 20 includes a processor 201, a memory 202, and at least one network interface (which is illustrated in fig. 2 by way of example only as including the network interface 203). The processor 201, the memory 202 and the network interface 203 are connected to each other.

The processor 201 may be a general processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more ics for controlling the execution of programs in accordance with the present invention.

The network interface 203 is an interface of the apparatus 20, and is used for communicating with other devices or communication networks, such as ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), and the like.

The memory 202 may be, but is not limited to, a read-only memory (ROM) or other type of static data center that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic data center that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), a magnetic disk storage medium or other magnetic data center, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory may be separate and coupled to the processor via communication line 202. The memory may also be integral to the processor.

The memory 202 is used for storing computer-executable instructions for executing the scheme of the application, and is controlled by the processor 201 to execute. The processor 201 is used to execute the computer-executable instructions stored in the memory 202, thereby implementing the intent processing methods provided by the embodiments described below in the present application.

Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.

In particular implementations, processor 201 may include one or more CPUs such as CPU0 and CPU1 in fig. 2, for example, as one embodiment.

In particular implementations, apparatus 20 may include multiple processors, such as processor 201 and processor 204 in fig. 2, for example, as an embodiment. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

The apparatus 20 may be a general-purpose device or a special-purpose device. In particular implementations, the apparatus 20 may be a desktop, network appliance, embedded device, or other device having a similar structure as in FIG. 2. The embodiment of the present application does not limit the type of the device 20.

An embodiment of the present application provides a model updating method, as shown in fig. 3, the method includes the following steps:

301. the second device sends a first message to the first device, wherein the first message comprises the identification information of the model file and the path information of the model file, or the first message comprises the model file and the identification information of the model file.

The first device includes a plurality of service function modules, and the service function modules in the first device may implement services using an ML model, for example, network traffic prediction or throughput prediction. The second device may manage the model used in the first device, including but not limited to triggering processes such as model deployment, model training, model updating, and model monitoring.

In a possible implementation manner, the second device may send a first message to the first device, and the first device acquires the file according to the first message.

In this embodiment of the application, the first message may be a file download (file download) message, and may include identification information of the model file and path information of the model file. Wherein the identification information of the model file comprises at least one of: file identification information, identification information of a device using the target model, model identification information, or version information of the model file. Wherein the target model is a model using the model file, and the path information of the model file is used to indicate a storage path of the model file.

It should be noted that the file identification information may be understood as an identification of the file itself, for example, the file identification information may be an ID of the file, and different files may be distinguished by different IDs. The object model is a model using the model file, i.e. the first device may run the object model by loading the model file. The identification information of the device may be a name (name) of the device or other identity information of the device, and is used to uniquely identify the device, and different devices may be distinguished by the identification information of the device. For example, the identification information of the device may include a device name and a service function module name. The identification information of the model can be a model name or other identity information of the model, and is used for uniquely identifying the model, and different models in the same equipment can be distinguished through the identification information of the model. The version information of the model file is used to indicate a version (version) of the model file, for example, version 1.0, version 2.0, and the like.

Furthermore, the model identification information may be understood as an identification of the model itself, for example, the model identification information may be an ID of the model, and different models may be distinguished by different IDs. Alternatively, the model identification information may be the name of the model, with different models having different names. Still alternatively, the model identification information may be a number of the model, and different models may be distinguished by different numbers. The model identification information in the identification information of the model file is used for indicating a model using the model file, for example, a target model described in the embodiment of the present application.

Optionally, the first message may also be a file transfer message, which may include identification information of the model file and the model file. The specific implementation of the identification information of the model file refers to the foregoing description, and is not described herein again.

302. The first equipment receives a first message from the second equipment, and acquires the model file according to the first message.

In a specific implementation, if the first message is a file download message, the first device downloads the file in the specified path after receiving the first message. For example, the first device obtains the model file according to the path information in the first message.

If the first message is a file transfer message, the first device receives the first message, and the model file can be obtained by analyzing the first message.

It can be understood that the identification information of the model file in the first message is bound to the model file (or the path information of the model file), and after the first device acquires the model file according to the first message, the first device may further store the corresponding relationship between the model file and the identification information of the model file, and subsequently may further index the model file according to the identification information of the model file.

303. And the second device sends a second message to the first device, wherein the second message comprises the identification information of the target model and the identification of the model file.

The second message is used to indicate the first device to activate the target model, for example, the second message is a model activation (model activation) message.

In this embodiment of the application, the second message includes identification information of the target model and identification information of the model file, and instructs the first device to determine the model file and the target model according to the identification information in the second message, and load the model file to activate the target model.

In one possible implementation, the identification information of the model includes at least one of: identification information of a device using the model, model identification information.

Taking the target model described in the embodiment of the present application as an example, the identification information of the target model includes at least one of the following items: identification information of a device using the target model, model identification information of the target model.

In one possible implementation, the identification information of the model file may intersect with the identification information of the target model, for example, the identification information of the model file includes identification information of a device using the target model, model identification information, and version information of the model file. The identification information of the target model includes identification information of a device using the target model, model identification information.

The identification information of the model file and the identification information of the target model may not have an intersection, for example, the identification information of the model file is file identification information (e.g., file ID). The identification information of the target model includes identification information of a device using the target model, model identification information.

304. The first device receives a second message from the second device, and activates a target model according to the second message and the model file.

In a specific implementation, after receiving the second message, the first device determines a model file and a target model according to the identification information in the second message, and updates the model file of the target model according to the model file, that is, replaces the current model file of the target model with the model file obtained in step 302. The first device may also run the target model, completing model activation.

In one possible implementation, multiple different models may use the same model file. In this scenario, the model file may also be indexed by file identification information (file ID), and multiple models using the same model file may also be indicated by a model list (model list).

In this embodiment, the second message may further include a model list. The model list includes at least one model identification indicating a number of models for which a model file needs to be replaced (or updated).

After receiving the second message, the first device may determine, according to the model list in the second message, a plurality of models that need to replace the model file, for example, determine at least one target model corresponding to at least one model identifier in the model list. It should be noted that the model identifiers correspond to the target models one to one, that is, one model identifier corresponds to one model.

Further, the first device may also update the model file of the at least one target model corresponding to the at least one model identifier according to the model file, that is, the current model file of the at least one target model is replaced with the model file acquired in step 302. The first device may also run the at least one target model, completing model activation.

Optionally, the second message further includes activation information of the target model; the activation information includes an activation type (activation type) of the target model and/or an activation time (activation time) of the target model.

Wherein the activation type comprises immediate activation, delayed activation, timed activation or periodic activation. Immediately activating the target model after indicating that the first equipment receives the second message; after the first equipment is indicated to receive the second message through delayed activation, the target model is activated after a period of time delay; the timed activation instructs the first device to initiate activation at a specified point in time; periodic activation indicates that the first device periodically activates the target model, e.g., 1 activation target model per month.

In a specific implementation, the value of the activate type parameter may be immedate, delay, or timing, which respectively represents immediate activation, delayed activation, and timed activation.

In one possible implementation, when the activate type parameter indicates delayed activation or timed activation, the second message may further include an activation time. The activate time parameter may indicate a time duration, or may indicate a specific time point. The first device determines the point in time to activate the target model jointly from the activation type and the activation time, e.g. the first device may activate the target model for a first time period (e.g. 5min) after receiving the second message. Alternatively, the first device may activate the target model after a first duration after receiving the first message. Or the first device starts a timer after receiving the second message, the duration of the timer is set according to the activation time, and the target model is activated when the timer is overtime.

It should be noted that the first device may implement model activation according to the activation type, may also implement model activation according to the activation time, and may also implement model activation according to the activation type and the activation time.

Optionally, the first message further includes a file type; the file type refers to the type of the model file in the steps 301-304, and the file type comprises a model file type and/or a sub-model file type. For example, the second device indicates that the file acquired by the first device is the model file through the file type in the first message, so that model update is realized based on the model file, and the complexity of model update is reduced.

In a possible implementation manner, the first device may further store a file according to a file type, for example, store the model file obtained in step 302 in the target storage space. The target storage space is used for storing files of the model file type, i.e. is dedicated for storing model files.

An embodiment of the present application provides a model updating method, as shown in fig. 4, the method includes the following steps:

401. the method comprises the steps that a second device sends a first message to a first device, wherein the first message comprises a first parameter; the first parameter is used for describing the storage position of a model file of the target model.

In this embodiment of the present application, a model may be used as a management object, a Management Object Class (MOC) of the model is defined, and relevant information of the model, such as a model name, a model file version, a model file storage location, a device name to which the model belongs, an operating state of the model, and a business function component name to which the model belongs, is recorded through the MOC. Specifically, the MOC of the model includes a plurality of different attribute parameters, the attribute parameters are used to describe relevant information of the model, and the attribute parameters may have different values.

For example, the MOC of the model includes a first parameter, and the first parameter is used to describe a storage location of the model file (the model file after the model is updated or the model file of a new version). The value of the first parameter may be path information of the model file indicating a storage location of the model file. For the target model, the first parameter of the MOC may describe a storage location of a model file of the target model.

In one possible implementation, the first message may be a Model Object Instance (MOI) modification message (modify MOI message) for modifying a value of a first parameter of the target model, i.e., modifying a storage location of the model file. For example, the first message may include a first parameter, and a value of the first parameter in the first message may indicate a storage location of the new model file. The second device instructs the first device to modify the value of the first parameter through the first message, so that the storage position of the model file is updated, the first device is triggered to acquire the model file to be updated, the model update is realized based on the new model file, the model update realized by updating the mirror image software package is avoided, and the resource overhead brought by the model update is reduced.

402. And the first equipment receives a first message from the second equipment and acquires the model file according to the first parameter.

In a specific implementation, the first device receives the first message, and analyzes the first message to obtain a value of the first parameter. The value of the first parameter indicates a storage location of the model file, and the first device can access the storage location to obtain the model file.

403. And the second device sends a second message to the first device, wherein the second message comprises a second parameter, and the second parameter is used for describing the state of the target model.

It should be noted that the MOC of the model may further include a second parameter, where the second parameter is used to describe an operation state of the model, and the operation state of the model may be activated or deactivated. The value of the second parameter may be active or passive, indicating that the model is active or inactive. For the target model, the second parameter of the MOC may describe an operating state of the target model.

In this embodiment of the application, the second device may indicate, in step 401, a storage address of the new model file through the first message, and in step 403, the second device may indicate, through the second message, the first device to load the new model file, and activate the target model. For example, the first device may be instructed by the second message to modify the value of the second parameter, and the value of the second parameter in the second message may be "active" instructing the second device to activate the target model.

404. And the first device receives a second message from the second device, and activates the target model according to a second parameter in the second message and the model file.

In a specific implementation, after receiving the second message, the first device determines the state of the target model according to the second parameter in the second message. For example, the value of the second parameter in the second message is "active", indicating that the state of the target model is active.

The first device may update the model file of the target model according to the model file, that is, replace the current model file of the target model with the model file acquired in step 402. The first device may also run the target model, completing model activation.

Optionally, the first message further includes identification information of the model file; the identification information of the model file includes at least one of: identification information of a device using the target model, model identification information, and version information of the model file.

The file identification information may be an identification of the file itself, for example, the file identification information may be an ID of the file, and different files may be distinguished by different IDs. The object model is a model using the model file, i.e. the first device may run the object model by loading the model file. The identification information of the device may be a name (name) of the device or other identity information of the device, and is used to uniquely identify the device, and different devices may be distinguished by the identification information of the device.

Illustratively, the identification information of the device includes a device name and a name of the business function module. The identification information of the model can be a model name or other identity information of the model, and is used for uniquely identifying the model, and different models in the same equipment can be distinguished through the identification information of the model. The version information of the model file is used to indicate a version (version) of the model file, for example, version 1.0, version 2.0, and the like. Optionally, the second message further includes identification information of the target model, and the identification information of the target model may be identification information of a device using the target model, and/or model identification information.

Wherein, the model identification information can be the name of the target model; the identification information of the device using the target model may be a name of the device using the target model, for example, a name of the first wireless controller network element using the target model.

Optionally, the method shown in fig. 4 further includes: the first device deactivates the target model before updating the model file of the target model. For example, the first device receives a third message from the second device; the third message includes the second parameter. The value of the second parameter in the third message may be "passive" indicating that the first device deactivated the target model. The first device may deactivate the target model in dependence on the value of the second parameter in the third message.

It should be noted that the MOC of the model may further include a third parameter, and the third parameter is used to describe a version (version) of a model file used by the model. The value of the third parameter may be a version of the model file used by the model, e.g., 1.0, 2.0, etc.

Optionally, the method shown in fig. 4 further includes: the first device may further modify a value of a third parameter in the MOI corresponding to the target model, where the modified value of the third parameter indicates a version of the updated model file.

Specifically, if the first message carries version information of the model file, the first device may further modify a value of the third parameter of the target model according to the version information of the model file. For example, the version information carried in the first message is "2.0", and the version of the model file currently used by the target model is 1.0. The value of the third parameter in the MOI corresponding to the target model is "1.0", and the first device may modify "1.0" to "2.0".

In a possible implementation manner, the service function module may also be used as a management object, the MOC of the service function module is defined, and the related information of the service function module, including the related information of the model using the service function module, is recorded by the MOC. The relevant information of the model can be a model name, a model file version, a model file storage location and the like. In this implementation manner, the method shown in fig. 4 is still applicable, and the detailed flow and the message refer to the foregoing description and are not described herein again.

The model updating method provided by the embodiment of the present application is described below with reference to specific examples. The first wireless controller may be the first device described in this embodiment, and the second wireless controller may be the second device described in this embodiment. The second wireless controller comprises a Model Manager and a Training Catalog, wherein the trained Model file is stored in the Training Catalog. The first wireless controller comprises a Model MnS Agent and a service function module based on an ML Model. The Model MnS Agent can temporarily store the Model file, and the ML-based service function module can run the Model file. The model updating process is divided into two steps: a model file transfer process and a model activation process. The model file transmission process can be that the second wireless controller transmits the model file and the information of the model file to the first wireless controller; the Model activation process is triggered by the Model Manager, the Model file in the ML-based service function module is updated (replaced), and the Model is operated so that the Model can use the updated Model file to provide services for the outside.

In the method shown in fig. 5, a scenario in which a service function module implements a service using multiple models is considered, and each model is managed, and each model may further include multiple sub-models. The submodels included in the same model can be managed as a whole, a unique model name (model name) is assigned, and all the submodels included in the model can be indexed according to the model name. Of course, a sub model name (sub model name) can be assigned to each sub model, and the sub model name is used for indexing different sub models, so that the model can be finely managed.

The method shown in fig. 5 includes two processes, one is to trigger the model file downloading process through a file download (file download) command, and the other is to trigger the update of the model file through a model activation (model activation) message, so as to complete the model activation. Referring to fig. 5, the method includes the steps of:

501: the Model Manager sends a Path query message (file Path Inventory) to the Training Catalog to query the Path information of the Model file.

Specifically, the file path inventory message includes identification information of the model file. The identification information of the model file comprises a controller name, a function name, a model name and a model file version. The model name is a name of a model (hereinafter, referred to as an object model) using the model file, the function name is a name of a business function module using the object model, the controller name is a name of a device (for example, a name of a first wireless controller) to which the business function module belongs, and the model file version is a version of the model file. The Controller name and the function name may be regarded as identification information of the device using the target model according to the embodiment of the present application.

502: the Training Catalog query obtains the path information (file path) of the model file.

Specifically, the Training Catalog may store a correspondence between the path information of the model file and the identification information of the model file, and may determine the path information of the model file according to the identification information of the model file in the file path inventoryy message.

503: the tracking Catalog returns an Acknowledgement (ACK) message to the Model Manager, containing the path information of the Model file.

504: the Model Manager sends a file download (file download) message to the Model MnS Agent to trigger the Model file download.

The file download message includes path information of a file, a file type (file type), a name of an object model using the model file, a name of a business function module providing a business using the object model, and a version of the model file.

The parameter "file Type" in the file download message indicates the Type of the model file, and the file Type may include a model Type and/or a sub-model Type. The parameter file type value is a model file, the indication file type is a model type, the parameter file type value is a sub model file, and the indication file type is a sub model type. When the value of the file type parameter is model file, indicating that the file to be downloaded is a model file, and the file download message may further include the following parameters in addition to the file path: function name, model name, and model file version. Other types of files may require different parameters, which the present embodiment does not limit.

It should be noted that if the content of the file download message is incorrect, for example, the file path information is incorrect, a Negative Acknowledgement (NACK) is returned to the Model Manager. Optionally, an error reason may also be included.

505: the Model MnS Agent sends a file download request to the tracking Catalog.

506: the Training Catalog returns the Model file to the Model MnS Agent.

507: and after receiving the Model file, the Model MnS Agent stores the Model file to a specific path of the Model file according to the file type.

Wherein the specific path is dedicated to storing a model type file, e.g., "/model file".

The Model MnS Agent may maintain a Model file information table, and record information of the downloaded Model file. After the Model MnS Agent stores the Model file, the related information of the Model file is added to the Model file information table, for example, the name of the target Model, the name of the service function module using the target Model, the version of the Model file, and the path information of the Model file.

508: the Model MnS Agent sends a notification message of successful download to the Model Manager.

509: the Model Manager sends a message to the Model MnS Agent to inquire whether the Model file exists.

The message may include the file type, the name of the business function module using the target model, the name of the target model, and the version of the model file.

510: the Model MnS Agent queries whether a Model file exists.

511: and the Model MnS Agent returns a query result to the Model Manager.

If the corresponding model file is inquired, returning ACK; if the corresponding model file is not queried, a NACK is returned.

It should be noted that steps 509 to 511 are optional steps, and step 512 may be skipped to be executed directly.

512: the Model Manager sends a Model activate message to the Model MnS Agent.

Wherein the model activation message may trigger model activation, and the model activation message may include a service function module name using the target model, a target model name, a model file version, an activation type (activation time), and an activation time (activation time). The activation type and the activation time are optional parameters, and are defined as follows:

the activate type indicates an activation type, the selectable value is immedate, delay or timing, and the corresponding activation types are immediate activation, delayed activation and timed activation respectively; the activate time indicates the activation time, and when the activation type is delay or timing, the model activation message may carry the activate time.

It should be noted that if the message content is incorrect (e.g., the model indicated by the model activation message does not exist), a NACK is returned.

513: the Model MnS Agent returns an ACK to the Model Manager indicating that the Model activation message is received.

514: the Model MnS Agent adds the activate type and the activate time of the Model file to the Model file information table.

515: and the Model MnS Agent sets a corresponding timer according to the activate type and the activate time of the Model file.

Specifically, if the timer is over, the model activation is started, and the current model file of the target model is replaced with the model file acquired in step 506.

It should be noted that, in the embodiment shown in fig. 5, the active mode is Timing as an example, when other active modes are adopted, the timer may not be set, and step 516 and the following flow steps are directly executed by skipping step 515.

516: the Model MnS Agent queries the state of the target Model.

The Model MnS Agent maintains the running state (Model status) of each Model in the service function module, and has two states of activation (active) and deactivation (passive).

If the target model is in the activated state, executing 517-519 to deactivate the target model; otherwise, executing 520-525.

517: the Model MnS Agent sends a Model deactivation message to the service function module.

The target model is instructed to stop running by a model deactivation message, which may include the name of the intended target model.

518: and the service function module returns ACK to the Model MnS Agent to indicate that the target Model stops running.

519: the Model MnS Agent updates the Model state to be deactivated.

Specifically, the model status parameter may be set to passive.

520: the Model MnS Agent sends a Model replace (Model replace) message to the service function module.

And indicating the service function module to complete the replacement of the model file of the target model through the model replacement message. The model replacement message may include the model file (the model file obtained in step 506) and the name of the target model.

It should be noted that the Model MnS Agent may find the location where the Model file is stored from the Model file information table, and then obtain the corresponding Model file and send the Model file to the service function module.

521: and the business function module completes the replacement of the model file.

It should be noted that, after receiving the model replacement message, the service function module needs to verify whether the current operating environment meets the operating requirement of the model file to be updated. If yes, directly carrying out file replacement; if not (e.g., the current operating environment does not match the version of the model file), then environment-dependent configuration is performed (e.g., a version upgrade is performed) before replacement of the model file is performed.

522: and the service function module returns ACK to the Model MnS Agent to indicate that the Model file replacement is completed.

523: the Model MnS Agent sends a Model activation (Model activate) message to the service function module.

The business function module is instructed to run the target model by a model activation message, which may include the name of the target model.

524: and the service function module returns ACK to the Model MnS Agent to indicate that the target Model starts to operate.

525: and updating the state of the target Model to be an activated state by the Model MnS Agent.

For example, the model status parameter is set to active, and the version of the model file currently used by the model may also be updated, specifically, the version of the model file acquired in step 507 may be used.

526: and the Model MnS Agent returns a notification of successful activation to the Model Manager, which indicates that the Model updating is completed.

It should be noted that steps 501 to 508 in this embodiment are model file downloading processes, and steps 512 to 526 are model activation processes. A complete model update process requires the model file download process and the model activation process to be completed, but the model file download process and the model activation process are not necessarily completed continuously in time. That is, model activation does not necessarily occur immediately after model file download. Therefore, the query process of steps 509 to 511 is an optional step, and if the model file is immediately activated after being downloaded, steps 509 to 511 do not need to be performed. Steps 509-511 may be performed to query before sending the model activation message.

The method shown in fig. 5 may implement model-based management and updating. Only the model file is required to be transmitted on the interface during model updating, the mirror image software package is not required to be transmitted, the transmitted data volume is greatly reduced, and the interface bandwidth and the transmission resource are saved. And each model can be subjected to refined management, the updating of part models in a multi-model scene can be realized, the operation of other models in the service function module cannot be influenced in the updating process of a single model, and the flexibility of model management is improved. In addition, activation time parameters can be configured to realize the activation of the model at the specified time, and the management flexibility is further improved.

The embodiment of the application further provides a Model updating method, which is different from the method shown in fig. 5 in that the Model Manager does not send the path information of the Model file to the Model MnS Agent any more, and the Model file is triggered and downloaded. The Model Manager can send the Model file to the Model MnS Agent without information interaction between the Model MnS Agent and the Training Catalog. As shown in fig. 6, the method comprises the steps of:

601: the Model Manager sends a Model file request (Model file request) message to the tracking Catalog.

Wherein the model file request message includes identification information of the model file. The identification information of the model file comprises a controller name, a function name, a model name and a model file version. The model name is a name of a model (hereinafter referred to as an object model) using the model file, the function name is a name of a business function module using the object model, the controller name is a name of a device (for example, a first wireless controller) to which the business function module belongs, and the model file version is a version of the model file. The controller name and the function name may be regarded as "identification information of a device using a target model" described in the embodiment of the present application.

602: the Training Catalog returns the requested Model file to the Model Manager.

603: the Model Manager sends a file transfer message to the Model MnS Agent.

The transmission of the model file may be implemented by a file transfer message, and the file transfer message may include the model file, a file type (file type), a name of the target model (a model using the model file), a name of a business function module using the target model, and a version of the model file.

604: and after receiving the Model file, the Model MnS Agent stores the Model file to a specific path according to the file type.

Wherein a particular storage path is dedicated to storing model type files.

605: the Model MnS Agent sends a notification message that the file transmission is successful to the Model Manager;

606 to 623: 509-526 as previously described.

In the method shown in FIG. 6, the Model Manager directly obtains the Model file from the Training Catalog, and then sends the Model file to the Model MnS Agent. The Model MnS Agent does not need to request the Training Catalog for downloading the Model file, thereby reducing the message interaction between the first wireless controller and the second wireless controller and saving the signaling overhead.

The embodiment of the application further provides a model updating method, which is different from the method shown in fig. 5 in that model file replacement is triggered through Software activation information managed by Software, so that model activation is completed. As shown in fig. 7, the method comprises the steps of:

701-711: similar to the steps 501-511 described above, further description is omitted here.

712: the Model Manager sends a software activation (software activate) message to the Model MnS Agent.

The software activation message may trigger model activation, and the software activation message may include a file type to be activated, a name of a target model (using the model file), a name of a business function module using the target model, a model file version, an activation type, and an activation time. The definition of each parameter refers to the related description of the method shown in fig. 5, and is not described herein again.

It should be noted that step 712 is different from a general software activation operation, and if the file type in the software activation message is "model file", a series of operations such as replacement of the model file may be triggered.

713 to 726: similar to the above steps 513 to 526, further description is omitted here.

In the method shown in fig. 7, the Model Manager sends a software activated interface message software activate to the Model MnS Agent, triggering Model file replacement without defining a new interface. The target model may be triggered to load a new model file and run the target model.

The embodiment of the present application further provides a model updating method, which is different from the method shown in fig. 5 in that a model file is sent through a file transfer message, and model file replacement is triggered through a software activation message managed by software, so that model activation is completed. As shown in fig. 8, the method comprises the steps of:

801: the Model Manager sends a Model file request (Model file request) to the tracking Catalog.

Wherein the model file request message includes identification information of the model file. The identification information of the model file comprises a controller name, a function name, a model name and a model file version. The model name is a name of a model (hereinafter referred to as an object model) using the model file, the function name is a name of a service function module using the object model, the controller name is a name of a device to which the service function module belongs, and the model file version is a version of the model file. The controller name and the function name may be regarded as identification information of a device using the target model according to the embodiment of the present application.

802: the Training Catalog returns the requested Model file to the Model Manager.

803: the Model Manager sends a file transfer message to the Model MnS Agent.

The file transfer message may implement the transfer of the model file, and for example, the file transfer message may include the model file, a file type (file type), a name of the object model (a model using the model file), a name of a business function module using the object model, and a version of the model file.

804: and after receiving the Model file, the Model MnS Agent stores the Model file to a specific path according to the file type.

805: and the Model MnS Agent sends a notification message that the file transmission is successful to the Model Manager.

806-808: the details of the above 509-511 are omitted here.

809: the Model Manager sends a software activation (software activate) message to the Model MnS Agent.

Wherein the software activation message may trigger model activation, and the software activation message may include a file type, a name of the target model (using the model file), a name of a business function module using the target model, a model file version, an activation type, and an activation time. The definition of each parameter refers to the related description of the method shown in fig. 5, and is not described herein again.

810-823: as described in steps 513-526 above.

In the method shown in FIG. 8, the Model Manager directly obtains the Model file from the Training Catalog, and then sends the Model file to the Model MnS Agent. The Model MnS Agent does not need to request the Training Catalog for downloading the Model file, and the message interaction between the first wireless controller and the second wireless controller is reduced. Meanwhile, the Model Manager sends a software activation message to the Model MnS Agent, and the Model Manager can trigger the replacement of the Model file by using a software activation interface managed by software without defining a new interface.

The embodiment of the present application further provides a model updating method, which is different from the methods shown in fig. 5 to 8, in which the method shown in fig. 9 models the service function module and defines the MOC of the service function module. Model related information can also be added as attribute parameters of the service function module MOC. Specifically, modification of MOC attribute parameters can be triggered through an MOI modification command, so that downloading of a model file and activation of a model are triggered.

In one possible implementation, the Model MnS Agent is responsible for creating and managing the MOI of the service function module. Specifically, the service function module MOC includes (but is not limited to) the following attribute parameters:

-function name: a name representing a business function module;

- - -controller name: a name representing a device to which the service function module belongs, for example, a name of a first wireless controller to which the service function module belongs;

-function type: representing types of service function modules, such as: ML-based, which represents a business function module using a machine learning model.

-inference model list: is a list of models. Wherein the inference model list comprises the following attribute parameters: model name, model file version, model file location, and running state. The model name represents the model name, the model file version represents the model file version, the model file location represents the model file storage position, and the running state represents whether the model is running or not, and comprises two states of activation (active) and deactivation (passive).

As shown in fig. 9, the method comprises the steps of:

901: the Model Manager sends an MOI read message (read MOI message) to the Model MnS Agent, and queries the running state of the target Model.

Wherein the target model is the model to be updated. The MOI read message may include a name of a business function module using the target model and a name of the target model.

902: and the Model MnS Agent returns an ACK message to the Model Manager, and the ACK message comprises the running state of the target Model.

903: the Model Manager sends a MOI modification message (Modify MOI message) to the Model MnS Agent, and modifies the attribute parameter running state to passive.

Specifically, the operation state of the target model is indicated as deactivated (passive) by the MOI modification message.

904: and the Model MnS Agent sends a Model deactivation message (Model deactivation message) to the service function module to indicate that the target Model stops running.

Wherein the model deactivation message may include the name of the target model.

905: and the service function module returns ACK to the Model MnS Agent to indicate that the target Model stops running.

906: and modifying the MOI attribute parameter corresponding to the target Model by the Model MnS Agent, and modifying the running state attribute to passive.

907: the Model MnS Agent returns a notification message to the Model Manager indicating that the MOI attribute parameters have changed.

908: the Model Manager sends an MOI modification message to the Model MnS Agent to modify the attribute parameter "Model file location".

The MOI modification message includes a value of an attribute parameter "model file location", which may indicate a storage location of a new version of the model file. In addition, the MOI modify message may also indicate a modify attribute parameter "model file version".

909: the Model MnS Agent modifies the attribute parameter "Model file location" and the attribute parameter "Model file version".

The modified value of the attribute parameter "model file location" indicates the storage location of the model file of the new version, and the modified value of the attribute parameter "model file version" indicates the version of the new model file.

910: the Model MnS Agent sends a file download request to the tracking Catalog.

911: the Training Catalog returns the requested Model file to the Model MnS Agent.

912: and after receiving the Model file, the Model MnS Agent stores the Model file to a specific path of the Model file according to the file type.

913: the Model MnS Agent returns a notification message to the Model Manager indicating that the MOI attribute has changed.

914: and the Model Manager sends an MOI modification message to the Model MnS Agent, and modifies the attribute parameter running state into active.

Specifically, the MOI modification message indicates that the running state of the target model is active.

915: the Model MnS Agent sends a Model replace (Model replace) message to the service function module.

And indicating the service function module to complete the replacement of the model file of the target model through the model replacement message. The model replacement message may include the name of the model file and the name of the target model.

916: and the business function module completes the replacement of the model file.

917: and the service function module returns ACK to the Model MnS Agent to indicate that the Model replacement is completed.

918: the Model MnS Agent sends a Model activation (Model activate) message to the service function module.

919: and the service function module returns ACK to the Model MnS Agent to indicate that the target Model starts to operate.

920: the Model MnS Agent modifies the attribute parameter running state of the MOI to active.

921: the Model MnS Agent returns a notification message to the Model Manager indicating that the MOI attribute has changed.

In the method shown in FIG. 9, the running State of the model is indicated by an attribute parameter running State in the MOI, and 901-907 modify the MOI attribute through the MOI to execute the deactivation of the model. 901-907 are optional steps, but have no precedence relation with 908-913, and 908-913 can be executed to download the model files first, and then 901-907 are executed to deactivate the model. In another alternative, a deactivation method in the method shown in fig. 5 is adopted, a Model Mns Agent maintains the running state of the Model, and the deactivation operation of the Model is executed after the Model activation message is received, that is, 516 to 519 described above, without executing 901 to 907.

In the method shown in fig. 9, a business function module is modeled, and related information of the model is maintained through attribute parameters of the MOI. The object instance of the service function module is modified through the existing interface, the downloading of the model file and the activation of the model are triggered, the updating of the model is realized, and the parameter information transmitted on the interface is reduced. In a possible implementation manner, the model can be modeled, and relevant information of the MOC recording model is defined. In this implementation, the method shown in fig. 9 is still applicable, and the detailed flow and message refer to the foregoing description and are not described herein again.

The embodiment of the present application further provides a model updating method, which is different from the method shown in the foregoing, and model downloading and model activation are triggered in one step. Specifically, adding a parameter in the file download message triggers model download and activation. As shown in fig. 10, the method comprises the steps of:

1001 to 1003: as with 501-503, the description is omitted.

1004: the Model Manager sends a file download message (file download message) to the Model MnS Agent.

The File download message includes path information of a File, a File type (File type), a name of an object model using a model File, a name of a service function module providing a service using the object model, a version of the model File, an activation type (activation type), and an activation time (activation time). The definition of each parameter refers to the above description, and is not repeated herein.

1005 to 1007: the details of 505-507 are not repeated here.

1008: the Model MnS Agent sends an ACK to the Model Manager indicating that the file has been successfully downloaded.

1009-1020: the details of the above-mentioned steps 514-525 are omitted.

1021: the Model MnS Agent sends a notification message to the Model Manager indicating that the file download command has been successfully executed.

Specifically, after the Model MnS Agent Model is updated, the notification message is sent after the Model file replacement and the Model activation are completed.

In the method shown in fig. 10, model file downloading and model activation are triggered simultaneously by the file download message, and an activation command does not need to be sent again, thereby saving signaling overhead.

The embodiment of the application further provides a model updating method, which is different from the method shown in fig. 10 in that parameters are added to a File Transfer message, and model File transmission and model activation are triggered without sending an activation instruction. As shown in fig. 11, the method comprises the steps of:

1101: the Model Manager sends a Model file request (Model file request) to the Training Catalog, requesting a Model file.

1102: the Training Catalog returns the requested Model file to the Model Manager.

1103: the Model Manager sends a file transfer message to the Model MnS Agent to trigger the Model file download.

The file transfer message includes path information of the file, a file Type (file Type), a name of an object model using the model file, a name of a service function module providing a service using the object model, a version of the model file, an activation Type (activated Type), and an activation time (activated time). The definition of each parameter refers to the above description, and is not repeated herein.

1104: and after receiving the Model file, the Model MnS Agent stores the Model file to a specific path according to the file type.

Where the particular path may be a "/model file", dedicated to storing files of the model type.

1105: and the Model MnS Agent sends ACK to the Model Manager to indicate that the Model file is successfully transmitted.

1106 to 1117: the details of the above-mentioned steps 514-525 are omitted.

1118: the Model MnS Agent sends a notification message to the Model Manager indicating that the file download command has been successfully executed.

In the method shown in fig. 11, the File transfer message is used to trigger the model File downloading and the model activation at the same time, and the activation command does not need to be sent again, thereby saving signaling overhead.

The embodiment of the present application further provides a model updating method, which is different from the method shown in fig. 9, and indicates model activation information, for example, an activation type or an activation time, while modifying the MOI attribute parameter. Model file download and model activation may be triggered by a message, as shown in fig. 12, the method comprising the steps of:

1201-1207: the details of the steps are not repeated here, as described in the above 501-507.

1208: and the Model Manager sends an MOI modification message to the Model MnS Agent to modify the MOI attribute parameters.

The MOI modification message may include information of a model to be updated, including a name of a target model using a model file, a name of a service function module providing a service using the target model, a version of the model file, an activation type (activation type), an activation time (activation time), and a storage location of the model file. The definition of each parameter refers to the above description, and is not repeated herein.

The MOI modification message may instruct the Model MnS Agent to modify an attribute parameter "Model file location", which has updated the storage location of the Model file of the target Model, so that the Model MnS Agent acquires the updated Model file.

1209: and modifying corresponding MOI attribute parameters including the version of the Model file, the position of the Model file and the activation time by the Model MnS Agent.

1210-1212: as described above 910-912.

1213: the Model MnS Agent sends an ACK to the Model Manager indicating receipt of the MOI modification message.

1214 to 1220: the details of the methods are not repeated here, as described in the above 915-921.

In the method shown in fig. 12, by defining the relevant information of the MOC maintenance model, parameters in the MOI modification message indicate modification activation information or file storage location, and simultaneously trigger model file downloading and activation, multiple MOI modification messages do not need to be sent, thereby reducing the messages to be transmitted on the interface.

The embodiment of the application also provides a model updating method, which is suitable for a scene in which a plurality of models use the same model file. In this scenario, the methods shown in fig. 3-12 are still applicable, but the same file needs to be transmitted multiple times. In order to reduce unnecessary information transmission, the model file can be indexed through file identification information (file ID), a parameter model list is added to indicate that the model of the model file needs to be replaced, and the model files of a plurality of models can be updated simultaneously. As shown in fig. 13, the method includes the steps of:

1301-1311: as previously described 501-511.

The difference is that the model file is indexed by the file ID, i.e. the parameters control name, function name, model name, model file version are replaced by the file ID.

1312: the Model Manager sends a Model activate message to the Model MnS Agent to trigger the Model activation.

The model activate message may include the file ID, the list of models that need to be activated (model list), the activation type, and the activation time. The model list indicates a plurality of models which need to replace the model file, including a model name (model name) and a business function module name using the model.

Optionally, the activation type and the activation time may be added to the model list to meet the activation time requirements of different models.

1313: and searching all the service function modules and models of which the model files need to be updated according to the model list.

1314: and respectively executing the same file replacement and model activation operations on the searched business function modules and models, and referring to the above 514-526 for the operation of each business function module.

The method shown in fig. 13 is directed to a scenario in which multiple models use the same model file, and simultaneous updating of multiple models in the scenario may also be achieved by using the model updating method described above, where parameters of an index model file in a message may be changed to file ID, and parameters of an index model may be changed to model list, and a flow of these schemes is not listed in detail here.

In the method shown in fig. 13, the method is applicable to a scenario in which multiple models use the same model file, the model file is indexed by the file ID, the parameter model list is added to indicate that the model file needs to be replaced, and the model files of multiple models can be updated simultaneously. For the same model file, repeated downloading is not needed, repeated sending of downloading and activating commands is not needed, and the information interaction amount is greatly reduced.

The embodiment of the application also provides a model updating method, which is suitable for scenes in which a plurality of sets of model files are matched for use and need to be periodically activated. For example: use version a on monday through friday, use version B on saturday through sunday, and so on. The model updating method shown in the foregoing in this scenario is still applicable, but since the model file needs to be periodically activated for use, the model file is updated by sending the activation instruction again every fixed time. As in the above example, the model activation messages are sent every monday and every saturday, which results in a large number of repeated interface message transmissions and is inefficient. In the method shown in fig. 14, a parameter indicating periodic activation is added to the Model activation message, and the Model Mns Agent performs corresponding operations according to the parameter after receiving the message. As shown in fig. 14, the method includes the steps of:

1401 to 1411: as before 501-511.

1412: the Model Manager sends a Model activate message to the Model MnS Agent to trigger the Model activation.

It should be noted that, unlike step 512, the parameter periodicInfo added to the model activate message of step 1412 indicates the relevant information of periodic activation.

Wherein, periodicInfo is an optional parameter, and the optional values include: periodic, nonPeriodic, or stop. Respectively indicating that periodic activation is required, periodic activation is not required and periodic activation is stopped. If the period info field is empty, the default is no period, and the method shown in fig. 5 is adopted to update the model.

The activation instruction of the step can also adopt a Software activation message, and the parameter periodicInfo is added in the Software activation message.

1413: the Model MnS Agent returns an ACK to the Model Manager indicating that the activation message has been received.

1414: and the Model MnS Agent determines the activation time of the Model file according to the activate type, the activate time and the periodicInfo, and sets a corresponding timer.

In specific implementation, the following three cases may be included:

4a, if the period info is 'period', indicating that the model file needs to be periodically activated, and setting a periodic timer;

4b, if the period info is 'nonPeriodic', it indicates that the model file needs to be periodically activated, and a single-time timer is set, like 515 described above;

4c, if the periodicInfo is 'stop', it indicates that the periodic activation is set before the model file, and in step 1314, the periodic activation needs to be stopped, and the original periodic timer is cancelled.

1415: the Model MnS Agent sends an activation exception notification to the Model Manager.

It should be noted that 1415 is an optional step for exception handling. If the Model MnS Agent finds that the activation time of the currently available Model file is abnormal (for example, two Model file versions needing to be activated exist at the same time), an activation abnormal notification is sent to the Model Manager, and the Model Manager performs relevant processing, for example, specifies the currently activated Model file version.

1416: model MnS Agent arrives at the specified time to start the Model activation.

1417 to 1427: the descriptions of 516-526 are omitted here.

In the method shown in fig. 14, the Model Manager only needs to send an activation instruction to the Model Mns Agent, so that the Model can be periodically activated, and the Model updating efficiency in the scene of periodic activation is improved.

Fig. 15 shows a schematic diagram of a possible structure of the communication device according to the above-described embodiment, in a case where each functional module is divided according to each function. The communication apparatus shown in fig. 15 may be the first device described in the embodiment of the present application, may also be a component of the first device that implements the method described above, or may also be a chip applied to the first device. The Chip may be a System-On-a-Chip (SOC) or a baseband Chip with a communication function. As shown in fig. 15, the communication apparatus includes a processing unit 1501 and a communication unit 1502. The processing unit may be one or more processors and the communication unit may be a transceiver or a communication interface.

The processing unit 1501, for example, may be configured to support the first device to perform internal processing such as message generation or message parsing, for example, to support the first device to perform

steps

302 and 304, or steps 402, 404, and/or other processes for the techniques described herein.

A communication unit 1502 for enabling communication between the first device and other communication apparatuses, e.g., enabling interaction between the first device and a second device, enabling the first device to perform step 505, step 605, etc., and/or other processes for the techniques described herein.

It should be noted that all relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

As shown in fig. 16, the communication device may further include a storage unit 1503 for storing program codes and/or data of the communication device.

The processing unit 1501 may include at least one processor, the communication unit 1502 may be a transceiver or a communication interface, and the storage unit 1503 may include a memory.

In the above embodiments of the communication device, each unit may be referred to as a module, a component, a circuit, or the like.

Fig. 17 is a schematic diagram showing a possible configuration of the communication device according to the above embodiment, in a case where each functional module is divided in correspondence with each function. The communication apparatus shown in fig. 17 may be the second device described in the embodiment of the present application, may also be a component of the second device that implements the method described above, or may also be a chip applied to the second device. The Chip may be a System-On-a-Chip (SOC) or a baseband Chip with a communication function. As shown in fig. 17, the communication apparatus includes a processing unit 1601 and a communication unit 1602. The processing unit may be one or more processors and the communication unit may be a transceiver or a communication interface.

Processing unit 1601, for example, may be used to support the second device in performing internal processing such as message generation or message parsing, e.g., to support the second device in performing step 502, and/or other processes for the techniques described herein.

A communication unit 1602 for supporting communication between the second device and other communication apparatuses, e.g. for supporting interaction between the second device and the second device, for supporting the second device to perform steps 401, 403, 301, 303, etc., and/or other processes for the techniques described herein.

As shown in fig. 18, the communication apparatus may further include a storage unit 1603, the storage unit 1603 being used for storing program codes and/or data of the communication apparatus.

The processing unit 1601 may comprise at least one processor, the communication unit 1602 may be a transceiver or a communication interface, and the storage unit 1603 may comprise a memory.

The embodiment of the application provides a computer-readable storage medium, wherein instructions are stored in the computer-readable storage medium; the instructions are used to perform the methods shown in fig. 3-14.

Embodiments of the present application provide a computer program product comprising instructions, which when run on a communication apparatus, cause the communication apparatus to perform the method as shown in fig. 3 to 14.

An embodiment of the present application provides a wireless communication apparatus, including: instructions are stored in the wireless communication device; when the wireless communication device is operating on the communication device shown in fig. 2, 15, 16, the communication device is caused to perform the method as shown in fig. 3-14. The wireless communication device may be a chip.

It is clear to those skilled in the art from the foregoing description of the embodiments that, for convenience and simplicity of description, the above-mentioned division of the functional modules is merely used as an example, and in practical applications, the above-mentioned function distribution may be completed by different functional modules according to needs, that is, the internal structure of the communication device may be divided into different functional modules to complete all or part of the above-mentioned functions.

The processor in the embodiment of the present application may include, but is not limited to, at least one of the following: various computing devices that run software, such as a Central Processing Unit (CPU), a microprocessor, a Digital Signal Processor (DSP), a Microcontroller (MCU), or an artificial intelligence processor, may each include one or more cores for executing software instructions to perform operations or processing. The processor may be a single semiconductor chip or integrated with other circuits to form a semiconductor chip, for example, an SoC (system on chip) with other circuits (such as a codec circuit, a hardware acceleration circuit, or various buses and interface circuits), or may be integrated in the ASIC as a built-in processor of the ASIC, which may be packaged separately or together with other circuits. The processor may further include necessary hardware accelerators such as Field Programmable Gate Arrays (FPGAs), PLDs (programmable logic devices), or logic circuits implementing dedicated logic operations, in addition to cores for executing software instructions to perform operations or processes.

The memory in the embodiment of the present application may include at least one of the following types: read-only memory (ROM) or other types of static memory devices that may store static information and instructions, Random Access Memory (RAM) or other types of dynamic memory devices that may store information and instructions, and may also be electrically erasable programmable read-only memory (EEPROM). In some scenarios, the memory may also be, but is not limited to, a compact disk-read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

In the present application, "at least one" means one or more. "plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple. In addition, in order to facilitate clear description of technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish the same items or similar items having substantially the same functions and actions. Those skilled in the art will appreciate that the terms "first," "second," etc. do not denote any order or quantity, nor do the terms "first," "second," etc. denote any order or importance.

In the several embodiments provided in the present application, it should be understood that the disclosed database access apparatus and method may be implemented in other ways. For example, the above-described database access device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, multiple units or components may be combined or integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed coupling or direct coupling or communication connection between each other may be an indirect coupling or communication connection through some interfaces, database access devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, that is, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or partially contributed to by the prior art, or all or part of the technical solutions may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip microcomputer, a chip, or the like) or a processor to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A model update method, comprising:

the method comprises the steps that first equipment receives a first message from second equipment, and a model file is obtained according to the first message; the first message comprises identification information of the model file and path information of the model file, or the first message comprises the model file and the identification information of the model file;

and the first device receives a second message from the second device, and activates a target model according to the second message and the model file, wherein the second message comprises identification information of the target model and identification information of the model file.

2. The method of claim 1, wherein the identification information of the model file comprises at least one of: file identification information, identification information of a device using the target model, model identification information, and version information of the model file;

the identification information of the target model includes at least one of: identification information of a device using the target model and the model identification information.

3. The method according to claim 1 or 2, wherein the first device obtains the model file according to the first message, including:

the first equipment acquires the model file according to the path information, wherein the path information is used for indicating a storage path of the model file;

or the like, or, alternatively,

and the first equipment analyzes the first message to obtain the model file.

4. The method of any of claims 1-3, wherein the first device activates a target model based on the second message and the model file, comprising:

and the first equipment updates the model file of the target model according to the model file and operates the target model.

5. The method of any of claims 1-3, wherein the second message further comprises a list of models; the model list includes at least one model identification.

6. The method of claim 5, wherein the first device activates a target model based on the second message and the model file, comprising:

and the first equipment updates the model file of at least one target model corresponding to the at least one model identification according to the model file and runs the at least one target model.

7. The method according to any of claims 1-6, wherein the second message further comprises activation information of the target model; the activation information comprises an activation type of the target model and/or an activation time of the target model;

wherein the activation type comprises immediate activation, delayed activation, timed activation or periodic activation.

8. The method of any of claims 1-7, wherein the first message further comprises a file type; the file type includes a model file type and/or a sub-model file type.

9. A model update method, comprising:

a first device receiving a first message from a second device, the first message comprising a first parameter; the first parameter is used for describing the storage position of a model file of the target model;

the first equipment acquires the model file according to the first parameter;

the first device receiving a second message from the second device, the second message including a second parameter describing a state of the target model;

the first device activates the target model according to the second parameter in the second message and the model file.

10. The method of claim 9, wherein the first message further comprises an identification of the model file; the identification information of the model file includes at least one of:

identification information of a device using the target model, model identification information, and version information of the model file.

11. The method according to claim 9 or 10, wherein the second message further comprises identification information of the target model, the identification information of the target model comprising at least one of: identification information of a device using the target model and model identification information.

12. The method of claim 10, further comprising:

modifying the value of a third parameter of the target model according to the version information of the model file; the third parameter is used for describing the version of the model file currently used by the target model.

13. The method according to any of claims 9-12, wherein before the first device activates the target model according to the second parameter in the second message and the model file, the method further comprises:

the first device receiving a third message from the second device; the third message comprises the second parameters;

the first device deactivates the target model according to the second parameter in the third message.

14. The method according to any of claims 9-13, wherein the first device activates the target model according to the second parameter in the second message and the model file, comprising:

and if the value of the second parameter indicates that the state of the target model is activated, the first device updates the model file of the target model according to the model file and runs the target model.

15. An apparatus, comprising:

a communication unit for receiving a first message from a second device; the first message comprises identification information of a model file and path information of the model file, or the first message comprises the model file and the identification information of the model file;

the processing unit is used for acquiring the model file according to the first message;

the communication unit is further configured to receive a second message from the second device, the second message including identification information of a target model and identification information of the model file;

the processing unit is further configured to activate the target model based on the second message and the model file.

16. The apparatus of claim 15, wherein the identification information of the model file comprises at least one of: file identification information, identification information of a device using the target model, model identification information, and version information of the model file;

17. The apparatus according to claim 15 or 16, wherein the processing unit is specifically configured to obtain the model file according to the path information, where the path information is used to indicate a storage path of the model file;

or analyzing the first message to obtain the model file.

18. The apparatus according to any of claims 15 to 17, wherein the processing unit is specifically configured to update a model file of the object model based on the model file and run the object model.

19. The apparatus of any of claims 15-17, wherein the second message further comprises a list of models; the model list includes at least one model identification.

20. The apparatus according to claim 19, wherein the processing unit is specifically configured to update a model file of the at least one object model corresponding to the at least one model identifier according to the model file, and run the at least one object model.

21. The apparatus according to any of claims 15-20, wherein the second message further comprises activation information of the target model; the activation information comprises an activation type of the target model and/or an activation time of the target model;

22. The apparatus of any of claims 15-21, wherein the first message further comprises a file type; the file type includes a model file type and/or a sub-model file type.

23. An apparatus, comprising:

a communication unit configured to receive a first message from a second device, the first message including a first parameter; the first parameter is used for describing the storage position of a model file of the target model;

the processing unit is used for acquiring the model file according to the first parameter;

the communication unit is further configured to receive a second message from the second device, the second message including a second parameter describing a state of the target model;

the processing unit is further configured to activate the target model according to the second parameter in the second message and the model file.

24. The apparatus of claim 23, wherein the first message further comprises an identification of the model file; the identification information of the model file includes at least one of:

25. The apparatus according to claim 23 or 24, wherein the second message further comprises identification information of the target model, the identification information of the target model comprising at least one of: identification information of a device using the target model and model identification information.

26. The apparatus according to claim 24, wherein the processing unit is further configured to modify a value of a third parameter of the target model according to version information of the model file; the third parameter is used for describing the version of the model file currently used by the target model.

27. The apparatus according to any of claims 23-26, wherein the communication unit is further configured to receive a third message from the second device before the processing unit activates the target model according to the second parameter in the second message and the model file; the third message comprises the second parameters;

the processing unit is further configured to deactivate the target model according to a second parameter in the third message.

28. The apparatus according to any of claims 23 to 27, wherein the processing unit is configured to, if the value of the second parameter indicates that the state of the object model is active, update a model file of the object model according to the model file, and run the object model.

29. An apparatus comprising a processor, the processor coupled with a memory;

a memory for storing a computer program;

a processor for executing a computer program stored in the memory to cause the apparatus to perform the model updating method of any one of claims 1 to 14.

30. A computer-readable storage medium comprising a program or instructions which, when executed by a processor, causes the model updating method of any one of claims 1 to 14 to be performed.