A deployment method of an internet of things application function configuration

Abstract

The application relates to the technical field of Internet of Things, in particular to a deployment method of application function configuration of Internet of Things, which is characterized in that, on the premise that a distributed application architecture taking a service unit as a basic unit is adopted in an Internet of Things application system, a unified communication mechanism of an Internet of Things platform is used to realize the configuration and deployment of the distributed function of the Internet of Things; the communication of the configuration and deployment and the communication of application data of the Internet of Things use a unified Internet of Things device data convergence mechanism, so that the unified transmission, control and management of the distributed function and the sensing and executing information of the Internet of Things can be realized in the Internet of Things environment. According to the application, as long as the nodes of the sensing and executing terminals of the Internet of Things can be converged, the on-demand configuration or permanent configuration of the distributed function is supported, the flexibility of the deployment and use of the function of the Internet of Things is improved, and the development and management control of the system are simplified.

Description

TECHNICAL FIELD

[0001] The application belongs to the field of Internet of Things, and particularly relates to a deployment method of Internet of Things application function configuration. BACKGROUND

[0002] From the perspective of application, an Internet of Things application system is composed of a client, an Internet of Things platform, an Internet of Things gateway, and an Internet of Things terminal device. A perfect Internet of Things application should be able to realize the distribution of system processing functions on different nodes in a wide area according to different needs of application and system. For example, the processing functions can be distributed on the Internet of Things platform in the cloud or on the Internet of Things gateway at the edge.

[0003] The current processing technology means that when it is necessary to change the system processing function on an application node, code modification, recompilation, and other operations are specially performed on the program on the application node, which not only increases the amount of code modification, affects the stability of the system, but also reduces the response speed of customer demand.

[0004] In order to realize the flexible deployment of system processing functions, the Internet of Things system can adopt a distributed application architecture with Internet of Things service units as the basic unit (in patent application CN115208920A). The Internet of Things service units can be distributed on locations reachable in a wide area, and a node deploying an Internet of Things service unit is a convergence node, and all the convergence nodes form a tree structure or a mesh structure. The Internet of Things service unit has the functions of north-south communication, data exchange, and configurable application data processing functions provided according to system requirements. By using the above application framework, the application data processing functions can be deployed on any convergence node in the Internet of Things system according to different requirements, and the coupling degree of the application data processing functions with the cloud server and the convergence nodes such as the Internet of Things gateway is minimized.

[0005] However, due to the wide range of technologies and standards involved in the Internet of Things, diversified needs and extensive interconnection, the complexity of the Internet of Things environment is determined; in the Internet of Things application, how to flexibly and quickly deploy distributed application data processing functions is a problem that must be solved. SUMMARY

[0006] To solve the above technical problems, the application proposes a deployment method of Internet of Things application function configuration by using the unified communication mechanism of the Internet of Things platform under the premise of a distributed application architecture with Internet of Things service units as the basic unit. Compared with general network services and Internet of Things devices, the method can directly support distributed processing involving Internet of Things functions without additional interconnection and interoperability association. The method can introduce ordinary network services at any desired location and flexibly deploy on-site (edge) processing functions.

[0007] The application discloses a deployment method of an Internet of Things application function configuration.

[0008] Each convergence node in the Internet of Things system is deployed with an Internet of Things service unit, which can independently run and provide two groups of north-south communication interfaces and a data exchange module; one group of communication interfaces completes the interface of the convergence function of the Internet of Things terminal device, which is referred to as a convergence interface; the other group of communication interfaces completes the interface function of the use and provision of ordinary network services, which is referred to as a network service interface; the data exchange module realizes the data exchange between the convergence interfaces and between the convergence interfaces and the Profile;

[0009] The Profile is configured with specifications, and the defined initial configuration file and all Profile program files for downloading are stored in a reachable network node, which is used as a Profile file server and is located on the same hardware platform as the Internet of Things service unit or is borne by an independent hardware platform.

[0010] The convergence node with the distributed processing function of the Profile mechanism is deployed with a Profile agent function, which provides the Profile management and running service for the system or the application.

[0011] In the application, the convergence node deployed with the Internet of Things service unit is referred to as a service node.

[0012] Further, the Profile is a distributed processing function in the Internet of Things service unit, which has a data exchange relationship with the Internet of Things convergence southward and has an Internet of Things virtual device identifier; the function in the Internet of Things service unit only interacts with the ordinary network service, or only uses the convergence part southward data and does not have the virtual device identifier, and the function does not belong to the Profile.

[0013] Further, when the Profile is configured with specifications, the various specification attributes of the Profile are defined, and the preparation work for the Profile program downloading is completed; the downloading channel of all files uses a general file downloading mechanism, and the downloading control information of the Profile program file is realized through the convergence communication function.

[0014] Further, in the specification configuration process, the Profile agent realizes the configuration definition of three aspects and records in the service node to which the agent belongs: a. the list and start-stop configuration of all the Profiles and the instances thereof deployed in the service node; b. the configuration of all the Profile functions in the list; and c. the configuration of all the Profile function instances in the list.

[0015] Further, the Profile management service includes: Profile downloading, instantiation, upgrade, instance start-stop, recycling; the Profile running service includes: data exchange between the Profile instance and the data exchange module in the Internet of Things service unit, Profile instance identification analysis, Profile instance addressing.

[0016] Further, with the support of the Profile agent in the service unit, dynamic Profile management and running service can be deployed and implemented in the case of normal program running, i.e. the whole process from downloading to running and updating, and the steps are as follows:

[0017] Step 1-1. When the user of the Profile configuration service, i.e. the system function or application function, needs to deploy a new Profile on the service node, the corresponding program should be queried on the Profile file server; if available, the type identification is submitted to the Profile agent of the service node with the downloading service request;

[0018] Step 2-1. According to the identification carried by the downloading request, the service node Profile agent downloads and deploys the appropriate program version and initial configuration file according to the platform and operating system, and according to the request, performs instance configuration, allocates identification and addressing identification, and starts instance running;

[0019] Step 3-1. If the application needs to start a new instance, it sends an instance request to the Profile agent of the service node and provides instance configuration parameters, and the latter allocates identification and addressing identification for the new instance according to the request, performs instance configuration, and starts instance running;

[0020] Step 4-1. After the Profile is successfully deployed, the Profile agent receives the instance stop request sent by the system or application according to business requirements and system requirements, and deregisters the Profile instance;

[0021] Step 5-1. The Profile agent has an update agent function, which regularly checks the Profile file server according to the active Profile type identification in the configuration file, compares the version on the service node with the server version, and if a new version is found, performs conditional or unconditional upgrade.

[0022] Further, the Profile agent automatically completes the registration of the Profile instance after starting the Profile, and the specific steps of registration are as follows:

[0023] Step 1-2: When the Profile instance is started, a data packet or a heartbeat packet is sent to the Profile agent of the service node where the Profile instance is located, so as to register the Profile instance and indicate the addressing route of the instance;

[0024] Step 2-2: After receiving the request, the Profile agent establishes the southbound route of the Profile instance and registers the instance in the service node;

[0025] Step 3-2: While the southbound route is established, the Profile agent forwards the data packet or the heartbeat packet to the data exchange module of the service node, and the route of the Profile instance is established in the data exchange module, so that all applications or other entities that need to use the Profile function can perform one-way or two-way communication through the addressing identifier.

[0026] Further, after the Profile instance is stopped, the Profile agent automatically completes the de-registration of the Profile instance, and the specific steps are as follows:

[0027] The Profile agent sends a stop command to the corresponding running instance according to the identification or addressing identifier in the request, and in the Profile program, the command listening function is provided, and when the stop command is received, a response is sent and the running is exited; correspondingly, the Profile agent deletes the southbound route information and performs de-registration.

[0028] The beneficial effects of the application are as follows:

[0029] 1) On the premise of using the existing communication and convergence functions of the Internet of Things system, the existing program code does not need to be modified, only the configuration information deployed on the node of a certain system needs to be quickly changed, so that the automatic update and re-deployment of the Profile can be realized, the application deployment process in the Internet of Things environment is simplified, and the deployment efficiency and the running efficiency of the distributed processing function are improved;

[0030] 2) On the premise of the whole system, the Profile and the sensing processing terminal are uniformly associated, the Profile deployment cost is maximally reduced, and the development and management control of the system are greatly simplified;

[0031] 3) A unified communication mechanism is adopted, as long as the nodes of the Internet of Things sensing execution terminal can converge, the Profile can be loaded and the instance can be run, so that the flexibility of the distributed application deployment and service provision of the Internet of Things is greatly improved. BRIEF DESCRIPTION OF DRAWINGS

[0032] Figure 1 The Profile described in the application is shown in the schematic diagram of the association relationship in the Internet of Things system.

[0033] Figure 2 a flow of deploying a new Profile instance described in the present application;

[0034] Figure 3 a structural diagram of a data frame format used in the Profile deployment process. DETAILED DESCRIPTION

[0035] In order to make the content of the present application more easily and clearly understood, the present application is further described in detail below according to specific embodiments and in conjunction with the accompanying drawings.

[0036] The present application proposes a deployment method of Internet of Things application function configuration, which utilizes a uniform communication mechanism of an Internet of Things platform to implement deployment of a Profile under the premise of a distributed application architecture taking an Internet of Things service unit as a basic unit, and specifically includes a specification configuration stage and an instance running stage. The specification configuration stage mainly defines various specification attributes of the Profile and completes preparation work for Profile program downloading, and the instance running stage involves specific steps including Profile file downloading, Profile instance start-stop operation, Profile instance registration and deregistration. The Profile is a short name of an Internet of Things distributed application function in the present application, and is a distributed processing function in a service unit which has a data exchange relationship with an Internet of Things convergence object.

[0037] A prerequisite of the present application is to adopt a distributed application architecture taking an Internet of Things service unit as a basic unit, in which architecture, each convergence node in an Internet of Things system is deployed with an Internet of Things service unit; wherein, a convergence node deployed with the Internet of Things service unit is referred to as a service node; the Internet of Things service unit refers to a program which can be independently deployed and run, and is a functional entity which can include an Internet of Things convergence part and a general network service part; and a node refers to a device in a network or a machine with an IP address in the network.

[0038] Figure 1 is a schematic diagram of an association relationship of the Profile described in the present application in an Internet of Things system, which is associated with an Internet of Things system through exchange functions of the Internet of Things service node on the left side and accesses a convergence structure of the Internet of Things system; and is associated with a general network service system on the right side and accesses a general network service system, such as a service system composed of Tornado or Node.js.

[0039] In a convergence node in an Internet of Things application architecture, if only a function of interacting with a general network service, that is, Figure 1If the north-south interface on the left side does not exist and only the network service interface on the right side exists, the service unit provides a general distributed network service, at this time, the module providing the network service function does not belong to the definition of the Profile, that is, the service unit does not include the Profile. For example, the convergence node only providing the general RestFul service function does not include the Profile.

[0040] In the present application, the Profile can be a virtual Internet of Things device, and the input and processing result thereof can participate in the convergence process of the Internet of Things device data, and the interaction relationship is as shown on the left side of the dashed line. Figure 1 The input or processing result of the Profile can also not participate in the convergence process of the Internet of Things, but is obtained through a general network service or provided to the outside as a general network service, and the interaction relationship is as shown on the right side of the dashed line. Figure 1

[0041] In the service unit involved in the present application, if the distributed processing function of the Profile mechanism needs to be implemented, the Profile agent function must be set, and in operation, all the Profiles and instances thereof are connected with the service unit data exchange module in the system or application through the agent function to complete the data exchange of the Profile and the convergence interface. Figure 1

[0042] The Profile agent provides the Profile management and operation services for the system or application, wherein the management services include: downloading, instantiation, upgrading, instance start-stop, recycling, etc. of the Profile; the operation services include: data exchange, instance identification analysis, instance addressing, etc. functions, to complete the data exchange between the Profile instance and the data exchange module in the service unit.

[0043] One Profile agent can manage multiple Profile instances.

[0044] Before the Internet of Things system needs to deploy a new Profile or upgrade the Profile, the initial configuration file needs to be maintained. The configuration file includes various attributes related to the Profile program file, some of which are independent of the Profile type and some of which are related to the type. The type-independent attributes can include: Profile type identification (used to distinguish different Profile program files), Profile state (such as warehousing, upgrading, and exiting), Profile download attributes (such as version number, download address and port number, and software and hardware environment parameters corresponding to each version), etc.; the type-dependent attributes are related to the function of the Profile, for example, in the light control Profile instance, the corresponding relationship between the control switch and the controlled lighting lamp. ​​

[0045] All downloadable Profile program files, and the initial configuration file described above are stored on a certain accessible network node for service node to download and run; the network node (referring to the node that each convergence node in the Internet of Things system can access, with a specific IP address; this node can be a convergence node, or a dedicated ftp server) as the Profile file server, can be in the same hardware platform as the Internet of Things service unit, or can be undertaken by an independent hardware platform; the download channel of all files does not use the convergence communication function of the Internet of Things, but uses the general file download mechanism, such as supporting SSH, FTP and other protocols, but the download control information of the Profile program file is realized through the convergence communication function.

[0046] When deploying Profile for the first time, it is necessary to ensure that the information of the initial configuration file on the Profile file server has been configured, and to ensure that the Profile program file has been put into the warehouse.

[0047] Figure 2 After the above preparation work is completed, the process of deploying a new Profile instance. The user of the Profile configuration service, such as a system function or an application function, needs to deploy a new Profile on the service node, and should first query the corresponding program on the Profile file server whether it is available, if it is available, then submit its type identifier to the service node Profile agent with the download service request; the service node Profile agent downloads the initial configuration file from the Profile file server according to the type identifier carried by the download request, and then finds the appropriate program version number in the initial configuration file according to the platform and operating system of the service node where the Profile needs to be deployed, and then downloads the Profile program file corresponding to the version from the Profile file server, to complete the entire download work.

[0048] After downloading, the Profile agent maintains the local program configuration file on the service node according to the downloaded initial configuration file. The local program configuration file records the Profile program file that has been successfully downloaded, which can mark which Profile the Profile agent in the service unit can manage, to facilitate the subsequent instance startup and registration request of the Profile instance that needs to be started after the download is successful; at the same time, it can also record the current program version, to facilitate subsequent automatic update.

[0049] After the above work is completed, the Profile agent performs instance configuration, maintains the instance configuration file, and starts the instance.

[0050] The reason for maintaining the instance profile file is that the same Profile can be deployed on multiple different service nodes to form multiple Profile instances; on the same service node, the same Profile can also start multiple Profile instances. Since each Profile instance handles different object instances, the specific processing object instances of all Profile function instances need to be defined. For example, the light control Profile can be deployed on multiple edge convergence nodes in the system, and since the physical locations of different edge convergence nodes are different, the control switches and controlled lighting lamps are also different. At this time, the control switch identifier and the controlled lighting lamp identifier handled by the Profile instance on the different edge convergence nodes need to be configured accordingly to ensure the correctness of data processing.

[0051] The specific steps of instance configuration are as follows:

[0052] 1. Assign Profile identification and addressing identification; identification and addressing identification are different concepts. The identification is the globally unique device identification of the Profile instance in the Internet of Things system, while the addressing identification is the identification for accessing the Profile instance generated in each north-south communication interaction process. When assigning the identification, determine the number of instances generated according to the business request, and then determine the number of generated identification. For example, in an Internet of Things service node that needs to deploy a light control Profile instance, if all the control switches and controlled lighting lamps within the control range of the service node are controlled uniformly, only one Profile instance needs to be started subsequently, and only one identification needs to be assigned. If all the control switches and controlled lighting lamps within the control range of the service node are divided into several groups and controlled by different Profile instances, several identification signs need to be assigned to correspond to different Profile instances.

[0053] 2. Configure instance-related attributes, including functional parameters and instance status. Each Profile implements different functions and processes different objects. For example, a Profile can process both text information and information about specific sensors / actuators in the system. Therefore, service nodes need to configure the data processing objects and data processing rules for each Profile instance deployed on their respective nodes. For example, on the service node deploying the lighting control Profile, the control switch identifier and the controlled lighting fixture identifier corresponding to the runtime of each lighting control Profile instance should be recorded in the instance configuration file. After the above runtime parameters are configured, the Profile instance can control according to the rules during runtime. During the operation of the Profile instance, the Profile instance can be started and stopped through the Profile agent, so the instance status will be flexibly modified according to the actual situation, supporting states such as "Generated", "Running", "Suspended", and "Closed". In the current configuration stage, the Profile instance status is "Generated".

[0054] All of the above configuration information is dynamic and can be changed continuously according to the application's needs during system operation.

[0055] It is important to note that all Profile program files and their related functional configuration information in the entire IoT system are stored on a single reachable service node, while the configuration information of the Profile agent only applies to Profiles within the management scope of that Profile agent.

[0056] 3. Start the Profile instance; Upon request, the Profile agent starts the Profile program file and generates the corresponding Profile instance. After the Profile instance starts, it sends data packets or heartbeat packets to the Profile agent on the node where it resides. After receiving the request, the Profile agent establishes a southbound route for the Profile instance and changes the instance's status to "running" in the service node. While establishing the southbound route, the Profile agent forwards the data packets or heartbeat packets to the service node's data exchange module. The data exchange module then establishes a route for the Profile instance, allowing all applications or other entities that need to use this Profile function to communicate with it one-way or two-way through its address identifier.

[0057] Once the above steps are completed, the Profile instance has been successfully deployed. After successful registration, the Profile instance periodically sends heartbeat packets to the Profile agent. If the Profile agent does not receive a heartbeat packet for an extended period, it will assume that the Profile instance has stopped and will then reissue the command to start the Profile instance.

[0058] After successful deployment of the Profile, an instance stop command can be sent to a specific service node based on business and system requirements. The Profile agent will send the stop command to the corresponding running instance based on the identification or addressing identifier in the request. The Profile program has a command listening function; when it receives a stop command, it sends a response and exits operation. Correspondingly, the Profile agent will delete the southbound routing information and deregister.

[0059] The Profile agent has an automatic update function. It periodically checks the Profile file server based on the active Profile type identifier in the instance configuration file, compares the version on this service node with the server version, and can perform conditional or unconditional upgrades if a new version is found.

[0060] During the upgrade process, first download the latest version of the Profile program file, then change the status of the Profile instance in the instance configuration file to "suspended," then stop the old version of the Profile instance from running, and then start the new version of the Profile instance. After the update is complete, change the status of the Profile instance back to "running."

[0061] The processes of deploying new profiles, upgrading and updating profiles, and stopping profile operation all involve communication between the system or application and the profile agent. These information interactions are all related to the profile agent's management of the profile. After successful profile deployment and normal operation, the communication between the system or application and the profile agent becomes related to profile data processing, i.e., processing by the sensor execution terminal. The data frame format used in the communication at both levels mentioned above when configuring and downloading profile-related configuration files is consistent with the data frame format used after the sensor execution terminal connects to the IoT system; during transmission, data can be transmitted in JSON format or binary format.

[0062] The data structure used for control and management interactions during the Profile deployment process is completely consistent with the data structure used for sensor control data transmission, and the application layer protocol used for exchange is also consistent. The data structure includes basic fields such as: reference, function code, device ID, endpoint ID, size, and value. The profile management function is equivalent to a device, with a device ID, and can be addressed globally. In the deployment activities of Profile management function control such as download, upgrade, registration, and startup, all control and management interactions except for file transfer are implemented by the above data structure and application layer exchange protocol.

[0063] In an IoT system with distributed service units as the basic unit, multiple convergence nodes can form a tree or mesh structure, and these nodes can be cascaded. When a convergence node that needs to download a profile communicates with a reachable network node that stores the basic configuration information of the profile, the interaction described above can be achieved regardless of how many convergence nodes are cascaded in between.

[0064] In an IoT system, a Profile instance is equivalent to a sensor execution terminal. Generally speaking, a Profile instance can be deployed in the same way as a sensor execution terminal. The difference is that configuring a sensor execution terminal requires the installation and networking of the device, while configuring a Profile instance requires the corresponding Profile program to be present in the service node. Sensor execution terminals are used to collect data or perform actions, while Profile instances are used to process data. Sensor execution terminals require actual physical deployment, while Profile instances can be deployed remotely.

[0065] Profiles can be deployed in two ways: dynamic deployment and permanent deployment. If a convergence node needs to dynamically deploy a Profile, then the service units deployed on that node must permanently deploy a Profile that supports Profile-related configuration, download, information query, and other functions to ensure the dynamic deployment of Profiles in that convergence node.

[0066] Figure 3 It is a structure diagram of the data frame format used by the application function configuration structure.

[0067] The prerequisite for this invention to achieve flexible and automatic deployment is that the communication between IoT terminal devices and server-side application services adopts a unified data frame format, and the specific data structure includes the following:

[0068] 1) Connection reference REF, an 8-bit unsigned integer, with a value range of [0, 256);

[0069] 2) Function code FNC, an 8-bit unsigned integer;

[0070] 3) Device Identifier (TMA), a 32-bit unsigned integer;

[0071] 4) The endpoint identifier (EMA) of the first endpoint is a 16-bit unsigned integer;

[0072] 5) Number of endpoints in the data REG: 8-bit unsigned integer;

[0073] 6) Device Time (DTM): 64-bit integer;

[0074] 7) Data DAT: The data carried by the data structure. Its number of bytes is determined by the data type (included in the endpoint identifier) ​​and the number of endpoints, but the maximum is no more than 1000 bytes;

[0075] 8) A 2-byte CRC check field at the end of the entire structure.

[0076] The function code in this data structure differs depending on the specific operation request. This data structure supports the following types of operations:

[0077] 1) Exchange of sensing / execution data;

[0078] 2) Data exchange between calculation unit parameters and calculation results;

[0079] 3) Configuration for controlling the execution of commands;

[0080] 4) Profile configuration data exchange;

[0081] 5) Management and state data exchange of Profile and Profile Agent.

[0082] In this invention, different operations are identified by function code FNC, different profile instances are distinguished by device identifier, and different attributes of profile are distinguished by endpoint identifier; different profile attribute values ​​are read and processed accordingly by reading data DAT.

[0083] In summary, the method described in this invention can be deployed as needed during operation, and in an open environment, it can utilize network open functions or close a given range of resources to enable autonomous operation. Furthermore, under the premise of abstracting IoT application functions, this invention describes how the same application function can be flexibly deployed on a certain node and can also be flexibly canceled. At the same time, the transmission mechanism of control information during deployment is consistent with the transmission mechanism of IoT sensor information after the system is running normally, without the need to set up a separate mechanism for program deployment.

[0084] The above description is merely a preferred embodiment of the present invention and is not intended to further limit the present invention. All equivalent changes made based on the description and drawings of the present invention are within the protection scope of the present invention.

Claims

1. A deployment method of an application function configuration of an Internet of Things, based on an Internet of Things system employing a distributed application architecture with Internet of Things service units as a basic unit, characterized by, The method comprises the following steps: Each service node in the Internet of Things system is provided with an Internet of Things service unit, which can independently run and provide two sets of north-south communication interfaces and a data exchange module; one set of communication interfaces completes the interface of the convergence function of the Internet of Things terminal device, which is referred to as a convergence interface; the other set of communication interfaces completes the interface function of the use and provision of ordinary network services, which is referred to as a network service interface; the data exchange module realizes data exchange between the convergence interfaces and between the convergence interfaces and the Profile; The Profile is configured, and the defined initial configuration file and all Profile program files for downloading are stored on a certain reachable network node, which is used as a Profile file server and is on the same hardware platform as the Internet of Things service unit or is borne by an independent hardware platform; The service node with a distributed processing function requiring a Profile mechanism is provided with a Profile agent function, which provides Profile management and running services for the system or application. 2.The method of claim 1, wherein, The Profile is a distributed processing function in the Internet of Things service unit, which has a data exchange relationship with the Internet of Things convergence south and a virtual device identifier; the function in the Internet of Things service unit only interacts with ordinary network services or only uses the convergence part of the south data without a virtual device identifier. 3.The method of claim 1, wherein, In the Profile specification configuration, various specification attributes of the Profile are defined, and preparation work for Profile program downloading is completed; all file downloading channels use general file downloading mechanisms, including SSH protocols or FTP protocols; Profile program file downloading control information is realized through convergence communication functions.

4. The method of Claim 3, wherein, In the specification configuration process, the Profile agent realizes three aspects of configuration definition and records in the service node to which the agent belongs: a. a list of all Profiles and their instances deployed in the service node and start-stop configurations; b. configurations of all Profile functions in the list; c. configurations of all Profile function instances in the list.

5. The deployment method of an application function configuration of an Internet of Things according to claim 1, characterized in that, The Profile management service includes: Profile downloading, instantiation, upgrading, instance start-stop and recycling; the Profile running service includes: data exchange between the Profile instance and the data exchange module in the Internet of Things service unit, Profile instance identifier analysis and Profile instance addressing.

6. The method of claim 5, wherein, With the support of the Profile agent in the service unit, the steps of Profile management and running service are as follows: Step 1-1. When the user of the Profile configuration service, i.e., a system function or an application function, needs to deploy a new Profile on the service node, the corresponding program is queried on the Profile file server to determine whether it is available; if it is available, the type identifier is submitted to the Profile agent of the service node with a downloading service request; Step 2-1. The service node Profile agent downloads and deploys the appropriate program version and initial configuration file according to the platform and operating system, and performs instance configuration, assigns the identification and addressing identification, and starts the instance operation according to the request based on the identification carried by the download request. Step 3-1. If the application needs to start a new instance, send an instance request to the Profile agent of the service node and provide instance configuration parameters. The latter assigns the identification and addressing identification for the new instance, performs instance configuration, and starts the instance operation according to the request. Step 4-1. After the Profile is successfully deployed, the Profile agent receives the instance stop request sent by the system or application according to the business requirements and system requirements, and deregisters the Profile instance. Step 5-1. The Profile agent has an update agent function. According to the active Profile type identification in the configuration file, it regularly checks the Profile file server and compares the version difference between the local service node and the server version. If a new version is found, it performs conditional or unconditional upgrade.

7. The method of claim 5, wherein, After the Profile agent starts the Profile, it automatically completes the registration of the Profile instance. The specific steps are as follows: Step 1-2: When the Profile instance starts, send a data packet or heartbeat packet to the Profile agent of the service node to register the Profile instance and indicate the addressing route of the instance. Step 2-2: After receiving the request, the Profile agent establishes the southbound route of the Profile instance and registers the instance in the service node. Step 3-2: The Profile agent forwards the data packet or heartbeat packet to the data exchange module of the service node while establishing the southbound route. The data exchange module will establish the route of the Profile instance, and all applications or other entities that need to use the Profile function can communicate with it through its addressing identification for one-way or two-way communication.

8. The method of claim 5, wherein, After the Profile instance stops, the Profile agent will automatically complete the deregistration of the Profile instance. The specific steps are as follows: The Profile agent sends a stop command to the corresponding running instance according to the identification or addressing identification in the request. In the Profile program, there is a command listening function. When the stop command is received, a response is sent and the running is exited. Correspondingly, the Profile agent will delete the southbound route information and perform deregistration.

Images