Management method and device

Abstract

The invention provides a management method and device. According to the management method, the interaction command is sent to the terminal equipment through the mobile network with the capabilities of long connection, control plane signaling and the like, so that the functions of the terminal equipment can be managed through programming and the like of a corresponding command line in the interaction command, and the terminal equipment can realize flexible function change and upgrade.

Description

Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a management method and device. Background Art

[0002] The Third Generation Partnership Project (3 rd The 5G system defined by the 3rd Generation Partnership Project (3GPP), implemented and deployed by the industry, is essentially a wireless communication pipeline for most applications. In addition to establishing communication pipelines and transmitting data through air interfaces and non-access stratum (NAS) with terminal devices, network devices have very limited control over the service application functions on terminal devices, such as IP multimedia subsystem (IMS) service applications. Network devices can control such service application functions on terminal devices, but cannot manage and control the operating system and other application layer capabilities of terminal devices, and cannot provide richer service applications.

[0003] In the future mobile communication system, in addition to communication channels, network devices may establish a higher level of collaboration with terminal devices. Therefore, for terminal devices of different types, uses and operating systems, how to remotely and flexibly change the functions of terminal devices and manage complex terminal software is an urgent problem to be solved. Summary of the invention

[0004] The present application provides a management method and device, which can enable more flexible and complex software management of terminal devices of different types, uses or different operating systems.

[0005] In a first aspect, a management method is provided, the method being applied to a first management network element, comprising: obtaining an interaction command, the interaction command being used to perform a management operation on a terminal device, and sending the interaction command to the terminal device.

[0006] It should be understood that the first management network element is a network element including a terminal remote management function. The first management network element may be an independent newly added network element, or the first management network element may also be an existing network element to which a terminal remote management function is newly added, for example, the terminal remote management function is assigned to an access management function network element, a session management function network element, a policy control function network element, etc.

[0007] In the above technical solution, an interaction command is sent to a terminal device through a mobile network with capabilities such as long connection and control plane signaling, so that the functions of the terminal device can be managed through programming and other operations corresponding to the command lines in the interaction command, enabling the terminal device to achieve flexible function changes and upgrades. In addition, the terminal device can jointly orchestrate with the network and the cloud according to the client's end-to-end service requirements to serve the client's business goals more accurately and efficiently. Ultimately, it is realized to reduce the installation, deployment, operation, maintenance, and management difficulties of terminal software, components, and tools, improve personnel efficiency, and accelerate business go-live.

[0008] In combination with the first aspect, in some implementation manners of the first aspect, the interaction command includes an operating system command and / or a management tool command.

[0009] In combination with the first aspect, in some implementation manners of the first aspect, the operating system command includes a command for managing the operating system of the terminal device, and the management tool command is a command for calling management tool software to execute management functions.

[0010] In combination with the first aspect, in some implementation manners of the first aspect, sending the interaction command to the terminal device includes: sending the interaction command to the terminal device through non-access stratum signaling or user plane signaling.

[0011] In combination with the first aspect, in some implementation manners of the first aspect, the method further includes: obtaining first indication information, where the first indication information is used to indicate that the terminal device is configured with permission information for executing the interaction command. Obtaining the interaction command includes: obtaining the interaction command according to the first indication information.

[0012] In this way, the interaction command is obtained by configuring the permission information for executing the interaction command for the terminal device on the network side, thereby improving the flexibility of the first management network element on the network side to manage the terminal side.

[0013] In combination with the first aspect, in some implementation manners of the first aspect, the first indication information is obtained according to second indication information, and the second indication information is used to indicate that the terminal device has opened the execution permission of the interaction command.

[0014] In this way, obtaining the first indication information through the execution permission of the interaction command set on the terminal device side can improve the autonomy of the user to perform subsequent management operations on the terminal device, thereby improving the user experience.

[0015] In combination with the first aspect, in some implementations of the first aspect, obtaining the first indication information includes: receiving the first indication information from a second management network element. Alternatively, obtaining the second indication information includes: receiving the second indication information from a second management network element. Wherein, the second management network element includes one of an access and mobility management function network element, a session management function network element, or a policy control function network element, and the first management network element includes a terminal remote management function.

[0016] In this way, setting up an independent function network element for the process of obtaining interaction commands and managing terminal devices on the network side can be clearly separated from other current function network elements, which helps with subsequent management, function expansion, and continuous evolution of this independent function network element.

[0017] In combination with the first aspect, in some implementations of the first aspect, the method further includes: obtaining second indication information, where the second indication information is used to indicate that the terminal device has enabled the execution permission for interaction commands. Obtaining the interaction command includes: obtaining the interaction command according to the second indication information.

[0018] In this way, the interaction command is obtained through the indication information on the execution permission of the interaction command on the terminal device side, so that the first management network element on the network side can more reasonably manage the terminal device.

[0019] In some implementations, obtaining the second indication information includes: receiving the second indication information from a second management network element. Wherein, the second management network element includes one of an access and mobility management function network element, a session management function network element, or a policy control function network element, and the first management network element includes a terminal remote management function.

[0020] In combination with the first aspect, in some implementations of the first aspect, the method further includes: obtaining an interaction command set from a template library, where the interaction command set includes interaction commands.

[0021] In this way, the complex and diverse steps in the terminal device management operation are implemented in the form of interaction commands in the interaction command set to realize the interaction between the first management network element and the terminal device, thus liberating human resources, improving efficiency, and supporting massive operations simultaneously.

[0022] In some implementations, the interaction command set is obtained and stored by the template library from a network open function network element, and the network open function network element includes an application programming interface.

[0023] In this way, by configuring the interaction command set through the application programming interface of the network open function network element, third-party manufacturers (such as terminal manufacturers, application manufacturers, etc.) can more conveniently customize and adapt to specific terminal environments (such as specific operating systems and / or terminal software components) and terminal management operations that need to be performed, and can also be flexibly expanded, upgraded, and changed according to subsequent industry developments.

[0024] In combination with the first aspect, in some implementations of the first aspect, obtaining an interaction command includes: obtaining an interaction command from a network exposure function network element.

[0025] Among them, the network exposure function network element includes an application programming interface.

[0026] In this way, directly obtain the interaction command through the application programming interface of the network exposure function network element and interact with the terminal device, enabling third-party manufacturers to directly perform real-time remote management and debugging on the terminal device, thereby realizing customization of the management of the terminal device.

[0027] In combination with the first aspect, in some implementations of the first aspect, obtaining an interaction command includes: obtaining an interaction script from a script library, where the interaction script includes an interaction command. Sending an interaction command to the terminal device includes: sending the interaction script to the terminal device.

[0028] In this way, the complex and diverse steps in the terminal device management operation are implemented in the form of an interaction script to realize the interaction between the first management network element and the terminal device, thereby liberating manpower, improving efficiency, and supporting massive operations simultaneously.

[0029] In some implementations, the interaction script is obtained and stored by the script library from the network exposure function network element, and the network exposure function network element includes an application programming interface.

[0030] In this way, configuring the interaction script through the application programming interface of the network exposure function network element can enable third-party manufacturers (such as terminal manufacturers, application manufacturers, etc.) to more conveniently customize and adapt to a specific terminal environment (such as a specific operating system and / or terminal software component) and terminal management operations that need to be performed more reasonably, and can also be flexibly extended, upgraded, and changed according to the subsequent development of the industry.

[0031] In combination with the first aspect, in some implementations of the first aspect, the method further includes: receiving an execution result of the interaction command from the terminal device. According to the execution result, obtaining identification information of a resource repository from the resource repository, where the resource repository includes at least one of a software image, a management tool, a component software package, an auxiliary tool, and a license file. Sending third indication information to the terminal device, where the third indication information includes the identification information.

[0032] In this way, sending the identification information of the resource repository to the terminal device can help the subsequent terminal device obtain the resource information required for specific management operations more conveniently from the resource repository. In addition, the mobile network has the characteristic of a transmission pipeline that is established and connected once. The resource repository set in the network can avoid problems such as the terminal device being unable to obtain resource information properly, having low efficiency in obtaining resources (slow transmission speed), and being easily attacked due to incorrect addressing in the external network or inability to communicate normally with the external server.

[0033] In a second aspect, a management method is provided. The method is applied to a terminal device and includes: receiving an interaction command from a first management network element. Executing the interaction command to obtain an execution result corresponding to the management operation.

[0034] It should be understood that the management method in the second aspect corresponds to the management method in the first aspect. The relevant beneficial effects can be referred to the first aspect and will not be elaborated here.

[0035] In combination with the second aspect, in some implementation manners of the second aspect, the interaction command includes an operating system command and / or a management tool command.

[0036] In combination with the second aspect, in some implementation manners of the second aspect, the operating system command includes a command for managing the operating system of the terminal device, and the management tool command is a command for invoking a management tool software to execute a management function.

[0037] In combination with the second aspect, in some implementation manners of the second aspect, receiving an interaction command from a first management network element includes: receiving an interaction command from a first management network element through non-access stratum signaling or user plane signaling.

[0038] In combination with the second aspect, in some implementation manners of the second aspect, the method further includes: sending second indication information to a second management network element, where the second indication information is used to indicate that the terminal device has opened the execution permission of the interaction command.

[0039] In combination with the second aspect, in some implementation manners of the second aspect, sending second indication information to a second management network element includes: when the switch state of the debug switch is on, sending second indication information to the second management network element.

[0040] In this way, the terminal device sends the second indication information based on the state of the debug switch, which can make the execution permission of the interaction command more intuitive for the terminal device, thereby improving the user experience.

[0041] In combination with the second aspect, in some implementations of the second aspect, receiving an interaction command from a first management network element includes: receiving an interaction script from the first management network element, where the interaction script includes the interaction command. Executing the interaction command to obtain an execution result includes: executing the interaction script to obtain the execution result corresponding to the interaction script.

[0042] In combination with the second aspect, in some implementations of the second aspect, the method further includes: sending the execution result to the first management network element. Receiving third indication information from the first management network element, where the third indication information includes identification information of a resource repository determined according to the execution result, and the resource repository includes at least one of a software image, a management tool, a component software package, an auxiliary tool, and a license file.

[0043] In combination with the second aspect, in some implementations of the second aspect, the method further includes: obtaining information in the resource repository according to the identification information. Performing corresponding management tasks according to the information in the resource repository.

[0044] In a third aspect, a management method is provided. The method is applied to a second management network element and includes: determining first indication information for indicating that a unified data management network element has configured permission information for the terminal device to execute an interaction command, where the interaction command is used to perform a management operation on the terminal device. Outputting the first indication information to the first management network element.

[0045] In combination with the third aspect, in some implementations of the third aspect, before determining the first indication information, the method further includes: receiving second indication information from the terminal device, where the second indication information is used to indicate that the terminal device has opened the execution permission of the interaction command. According to the second indication information, obtaining software management permission information from the unified data management network element, where the software management permission information is used to indicate whether the unified data management network element has configured the execution permission of the interaction command for the terminal device.

[0046] In combination with the third aspect, in some implementations of the third aspect, determining the first indication information includes: if the management task permission information is used to indicate that the unified data management network element has configured the execution permission of the interaction command for the terminal device, then determining the first indication information.

[0047] In a fourth aspect, a management method is provided. The method is applied to a second management network element and includes: receiving second indication information from the terminal device, where the second indication information is used to indicate that the terminal device has opened the execution permission of the interaction command. Outputting the second indication information to the first management network element.

[0048] In a fifth aspect, a management device is provided. The device is located in the first management network element and includes a transceiver unit for: obtaining an interaction command for performing a management operation on a terminal device. Sending the interaction command to the terminal device.

[0049] It should be understood that the management device in the fifth aspect corresponds to the management method in the first aspect. For the related beneficial effects, reference can be made to the first aspect and will not be elaborated here.

[0050] In combination with the fifth aspect, in some implementation manners of the fifth aspect, the interaction command includes an operating system command and / or a management tool command.

[0051] In combination with the fifth aspect, in some implementation manners of the fifth aspect, the operating system command includes a command for managing the operating system of the terminal device, and the management tool command is a command for calling the management tool software to execute a management function.

[0052] In combination with the fifth aspect, in some implementation manners of the fifth aspect, the transceiver unit is specifically configured to send the interaction command to the terminal device through non-access stratum signaling or user plane signaling.

[0053] In combination with the fifth aspect, in some implementation manners of the fifth aspect, the transceiver unit is further configured to obtain first indication information, where the first indication information is used to indicate that the terminal device is configured with permission information for executing the interaction command. The transceiver unit is specifically configured to obtain the interaction command according to the first indication information.

[0054] In combination with the fifth aspect, in some implementation manners of the fifth aspect, the first indication information is obtained according to second indication information, where the second indication information is used to indicate that the terminal device has opened the execution permission of the interaction command.

[0055] In combination with the fifth aspect, in some implementation manners of the fifth aspect, the transceiver unit is specifically configured to receive the first indication information from a second management network element. Alternatively, the transceiver unit is specifically configured to receive the second indication information from a second management network element. The second management network element includes one of an access and mobility management function network element, a session management function network element, or a policy control function network element, and the first management network element includes a terminal remote management function.

[0056] In combination with the fifth aspect, in some implementation manners of the fifth aspect, the transceiver unit is further configured to obtain second indication information, where the second indication information is used to indicate that the terminal device has opened the execution permission of the interaction command. The transceiver unit is specifically configured to obtain the interaction command according to the second indication information.

[0057] In some implementation manners, the transceiver unit is specifically configured to receive the second indication information from a second management network element. The second management network element includes one of an access and mobility management function network element, a session management function network element, or a policy control function network element, and the first management network element includes a terminal remote management function.

[0058] In combination with the fifth aspect, in some implementations of the fifth aspect, the transceiver unit is further configured to obtain an interaction command set from a template library, where the interaction command set includes interaction commands.

[0059] In combination with the fifth aspect, in some implementations of the fifth aspect, the transceiver unit is specifically configured to obtain an interaction command from a network openness function network element.

[0060] In combination with the fifth aspect, in some implementations of the fifth aspect, the transceiver unit is specifically configured to obtain an interaction script from a script library, where the interaction script includes interaction commands; and send the interaction script to a terminal device.

[0061] In combination with the fifth aspect, in some implementations of the fifth aspect, the transceiver unit is further configured to obtain identification information of a resource repository from the resource repository according to an execution result, where the resource repository includes at least one of a software image, a management tool, a component software package, an auxiliary tool, and a license file. Send third indication information to the terminal device, where the third indication information includes the identification information.

[0062] In a fifth aspect, a management device is provided. The device is located in a terminal device and includes a communication function unit and a processing unit. The communication function unit is configured to receive an interaction command from a first management network element, where the interaction command is used to perform a management operation on the terminal device. The processing unit is configured to execute the interaction command to obtain an execution result corresponding to the management operation. The communication function unit is further configured to send the execution result to the first management network element.

[0063] It should be understood that the management device in the sixth aspect corresponds to the management method in the second aspect. The related beneficial effects can be referred to in the second aspect and will not be elaborated here.

[0064] In combination with the sixth aspect, in some implementations of the sixth aspect, the interaction command includes an operating system command and / or a management tool command.

[0065] In combination with the sixth aspect, in some implementations of the sixth aspect, the operating system command includes a command for managing the operating system of the terminal device, and the management tool command is a command for invoking a management tool software to execute a management function.

[0066] In combination with the sixth aspect, in some implementations of the sixth aspect, the communication function unit specifically includes a transceiver unit and an interaction proxy unit. The transceiver unit is specifically configured to receive an interaction command from a first management network element through non-access stratum signaling or user plane signaling. The interaction proxy unit is specifically configured to obtain the interaction command from the transceiver unit and send it to the operating system of the terminal device.

[0067] In this way, the communication function unit in the terminal device is further divided into a transceiver unit and an interaction agent unit. The transceiver unit is consistent with the communication baseband function of the current terminal device and is responsible for information transmission. The interaction agent unit is responsible for the interaction between the operating system of the terminal and the first functional network element. Such a division can help with the future functional evolution, upgrade, and change of the two functional modules separately.

[0068] In combination with the sixth aspect, in some implementation manners of the sixth aspect, the interaction agent unit is further configured to send second indication information to the transceiver unit, where the second indication information is used to indicate that the terminal device has enabled the execution permission of the interaction command. The transceiver unit is further configured to send the second indication information to the second management network element.

[0069] In combination with the sixth aspect, in some implementation manners of the sixth aspect, the interaction agent unit is specifically configured to receive the second indication information from the operating system of the terminal device when the switch state of the debug switch is on.

[0070] In combination with the sixth aspect, in some implementation manners of the sixth aspect, the communication function unit specifically includes a transceiver unit and an interaction agent unit. The transceiver unit is specifically configured to receive interaction commands from the first management network element one by one. The interaction agent unit is specifically configured to obtain the interaction commands from the transceiver unit and send them to the operating system of the terminal device. The processing unit is specifically configured to execute the interaction commands in the operating system of the terminal device to obtain an execution result.

[0071] In combination with the sixth aspect, in some implementation manners of the sixth aspect, the communication function unit specifically includes a transceiver unit and an interaction agent unit. The transceiver unit is specifically configured to receive an interaction script from the first management network element, where the interaction script includes interaction commands. The interaction agent unit is specifically configured to obtain the interaction script from the transceiver unit, execute the interaction script, and send the interaction commands to the operating system of the terminal device. The processing unit is specifically configured to execute the interaction commands in the operating system of the terminal device to obtain an execution result of the interaction script.

[0072] In combination with the sixth aspect, in some implementation manners of the sixth aspect, the communication function unit specifically includes a transceiver unit and an interaction agent unit. The transceiver unit is specifically configured to receive third indication information from the first management network element, where the third indication information is used to indicate the identification information of a resource repository determined according to the execution result, and the resource repository includes at least one of a software image, a management tool, a component software package, an auxiliary tool, and a license file. The interaction agent unit is specifically configured to obtain the third indication information from the transceiver unit and send it to the operating system of the terminal device.

[0073] In combination with the sixth aspect, in certain implementations of the sixth aspect, the transceiver unit is further specifically configured to obtain information in the resource repository according to the identification information. The interaction agent unit is specifically configured to obtain the information in the resource repository from the transceiver unit and send it to the operating system of the terminal system. The processing unit is further configured to perform corresponding management tasks according to the information in the resource repository.

[0074] In a seventh aspect, a management device is provided. The device is located in the second management network element and includes a transceiver unit and a processing unit. The processing unit is configured to determine first indication information, where the first indication information is used to indicate that the unified data management network element has configured permission information for the terminal device to execute an interaction command, and the interaction command is used to perform a management operation on the terminal device. The transceiver unit is configured to output the first indication information to the first management network element.

[0075] In combination with the seventh aspect, in certain implementations of the seventh aspect, before determining the first indication information, the transceiver unit is further configured to receive second indication information from the terminal device, where the second indication information is used to indicate that the terminal device has enabled the execution permission of the interaction command. According to the second indication information, obtain software management permission information from the unified data management network element, where the software management permission information is used to indicate whether the unified data management network element has configured the execution permission of the interaction command for the terminal device.

[0076] In combination with the seventh aspect, in certain implementations of the seventh aspect, the processing unit is specifically configured to determine the first indication information if the management task permission information is used to indicate that the unified data management network element has configured the execution permission of the interaction command for the terminal device.

[0077] In an eighth aspect, a management device is provided. The device is located in the second management network element and includes a transceiver unit. The method includes: The transceiver unit is configured to receive second indication information from the terminal device, where the second indication information is used to indicate that the terminal device has enabled the execution permission of the interaction command. Output the second indication information to the first management network element.

[0078] In a ninth aspect, a management device is provided, which includes: a memory for storing a program; a processor for executing the computer program code or instructions stored in the memory. When the computer program code or instructions stored in the memory are executed, the processor is used to execute the method provided in any implementation of the first aspect or the second aspect above.

[0079] In one implementation, the device is the first management network element, the second management network element, or the terminal device in the management method.

[0080] In another implementation, the device is a chip, a chip system, or a circuit in the first management network element, the second management network element, or the terminal device in the management method.

[0081] In a tenth aspect, the present application provides a processor for executing the method provided by any one of the first to fourth aspects above. During the execution of these methods, the processes of sending the above information and obtaining / receiving the above information in the above methods can be understood as the process of the processor outputting the above information and the process of the processor receiving the input of the above information. When outputting the above information, the processor outputs the above information to an interface for transmission through the interface. After the above information is output by the processor, other processing may be required before it reaches the interface. Similarly, when the processor receives the input of the above information, the interface obtains / receives the above information and inputs it into the processor. Further, after the interface receives the above information, the above information may need to be processed otherwise before being input into the processor.

[0082] For operations such as transmission, sending, and obtaining / receiving involved, if there is no special description, or if it does not conflict with its actual role or internal logic in the relevant description, it can be understood as operations such as output, reception, and input, and can also be understood as the transmission, sending, and receiving operations performed by the radio frequency circuit and the antenna. The present application does not make any limitations in this regard.

[0083] During implementation, the above processor can be a processor specifically dedicated to executing these methods, or a processor that executes the computer program code or instructions in the memory to execute these methods, such as a general-purpose processor. The above memory can be a non-transitory memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip or can be separately provided on different chips. The embodiments of the present application do not make any limitations on the type of the memory and the setting manner of the memory and the processor.

[0084] In an eleventh aspect, a computer-readable storage medium is provided. The computer-readable medium stores program code or instructions for a device to execute, and the program code or instructions include the method provided by any one of the first to fourth aspects above.

[0085] In a twelfth aspect, a computer program product containing instructions is provided. When the computer program product runs on a computer, it causes the computer to execute the method provided by any one of the first to fourth aspects above.

[0086] In a thirteenth aspect, a chip is provided. The chip includes a processor and a communication interface. The processor reads the instructions stored on the memory through the communication interface and executes the method provided by any one of the first to fourth aspects above.

[0087] Optionally, as an implementation, the chip may further include a memory, in which computer program code or instructions are stored, and the processor is configured to execute the computer program code or instructions stored on the memory. When the computer program code or instructions are executed, the processor is configured to execute the method provided by any one of the first to fourth aspects above.

[0088] In a fourteenth aspect, a management system is provided, including at least one of a first management network element, a second management network element, and a terminal device. The first management network element is configured to execute the method provided by any one of the implementations of the first aspect, and the terminal device is configured to execute the method provided by any one of the implementations of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0089] Figure 1 is a schematic diagram of the 3GPP system architecture of a 5G system provided by an embodiment of the present application;

[0090] Figure 2 is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0091] Figure 3 is a schematic diagram of the architecture of a terminal device provided by an embodiment of the present application;

[0092] Figure 4 is a schematic flowchart of a management method provided by an embodiment of the present application;

[0093] Figure 5 is a schematic flowchart of another management method provided by an embodiment of the present application;

[0094] Figure 6 is a schematic flowchart of yet another management method provided by an embodiment of the present application;

[0095] Figure 7 is a schematic flowchart of still another management method provided by an embodiment of the present application;

[0096] Figure 8 is a schematic flowchart of still another management method provided by an embodiment of the present application;

[0097] Figure 9 is a schematic flowchart of still another management method provided by an embodiment of the present application;

[0098] Figure 10 is a schematic flowchart of still another management method provided by an embodiment of the present application;

[0099] Figure 11 is a schematic flowchart of still another management method provided by an embodiment of the present application;

[0100] Figure 12It is a schematic diagram of a management device provided by an embodiment of the present application;

[0101] Figure 13 It is a schematic structural diagram of a management device provided by an embodiment of the present application;

[0102] Figure 14 It is a schematic diagram of a chip system provided by an embodiment of the present application. Detailed implementation manners

[0103] Next, the technical solutions in the present application will be described with reference to the accompanying drawings.

[0104] For the convenience of understanding the embodiments of the present application, the following points are explained:

[0105] First, in the present application, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be mutually referred to, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0106] Second, in the present application, "at least one" means one or more, and "a plurality" means two or more. "And / or" describes the association relationship of associated objects and indicates that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. In the text description of the present application, the character " / " generally represents an "or" relationship between the associated objects before and after. "At least one (item)" or its similar expression refers to any combination of these items, including any combination of single item (item) or plural items (items). For example, at least one (item) of a, b, and c can represent: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b, and c. Where a, b, and c can be single or multiple respectively.

[0107] Third, in the present application, "first", "second", and various numerical numbers (for example, #1, #2, etc.) are used for distinction for the convenience of description and do not limit the scope of the embodiments of the present application. For example, to distinguish different management network elements, etc., rather than for describing a specific order or sequence. It should be understood that the objects described in this way can be interchanged under appropriate circumstances so as to be able to describe the solutions other than the embodiments of the present application.

[0108] Fourth, in the present application, descriptions such as "when...", "in the case of...", and "if" all refer to corresponding processing being performed under certain objective circumstances, rather than limiting time. Moreover, it is not required that there must be a judgment action during implementation, nor does it mean that there are other limitations. Additionally, it does not mean that the judgment action after these conditional conjunctions is the only condition for achieving the result. Other additional conditions may also be included to achieve the result.

[0109] Fifth, in the present application, the terms "comprise" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that comprises a series of steps or units need not be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products, or devices.

[0110] Sixth, in the present application, "for indicating" may include direct indication and indirect indication. When describing that a certain indication information is for indicating A, it may include the indication information directly indicating A or indirectly indicating A, and does not mean that A must be carried in the indication information.

[0111] The indication methods involved in the embodiments of the present application should be understood to cover various methods that can enable the party to be indicated to obtain the indication information. The indication information may be sent as a whole or divided into multiple sub-information and sent separately. Moreover, the sending periods and / or sending timings of these sub-information may be the same or different. The present application does not limit the specific sending method.

[0112] The "indication information" in the embodiments of the present application may be explicit indication, that is, directly indicated by a signaling, or obtained by combining other rules or other parameters or through derivation according to the parameters indicated by the signaling. It may also be implicit indication, that is, obtained according to rules or relationships, or according to other parameters, or through derivation. The present application does not make specific limitations on this.

[0113] Seventh, in the present application, "protocol" may refer to standard protocols in the communication field. For example, it may include 5G protocols, new radio (NR) protocols, and related protocols applied to future communication systems. The present application does not limit this. "Pre-defined" may include pre-definition. For example, protocol definition. "Pre-configuration" may be achieved by pre-saving corresponding codes, tables, or other means that can be used to indicate relevant information in a device. The present application does not limit its specific implementation manner.

[0114] Eighth, in this application, "storage" may refer to being stored in one or more memories. The one or more memories may be separately provided, or may be integrated in an encoder or decoder, a processor, or a communication device. The one or more memories may also be partly separately provided and partly integrated in a decoder, a processor, or a communication device. The type of the memory may be any form of storage medium, and this application does not limit this.

[0115] Figure 1 It is a schematic diagram of the 3GPP system architecture of a 5G system provided by an embodiment of this application. As Figure 1 shown, the network functions and entities currently included in the 3GPP architecture mainly include: user equipment (UE), (radio) access network ((R)AN) equipment, data network (DN), and core network. Each part involved in this communication system will be described separately below.

[0116] 1. User Equipment: User equipment can also be referred to as a terminal, access terminal, user unit, user station, mobile station, mobile device, remote station, remote terminal, mobile equipment, user terminal, wireless communication device, user agent, or user device. The terminal in the embodiments of the present application can be a mobile phone, a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, an extended reality (XR) terminal (e.g., a head-mounted XR glasses), a holographic projector, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device, or other processing devices connected to a wireless modem, in-vehicle equipment, wearable devices, a terminal in a 5G network, or a terminal in a future evolved network, etc.

[0117] Among them, wearable devices can also be called wearable intelligent devices, which is a general term for devices developed by applying wearable technology to intelligent design of daily wear, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a kind of hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable intelligent devices include those with complete functions and large sizes that can achieve complete or partial functions without relying on a smart phone, such as smart watches or smart glasses, etc., and those that only focus on a certain type of application function and need to cooperate with other devices such as smart phones, such as various smart bracelets and smart jewelry for physical sign monitoring.

[0118] 2. Access network device: The access network device can also be called an access device, that is, a (wireless) access network (radio access network, (R)AN). The (R)AN can manage radio resources, provide access services for user equipment, and forward the data of user equipment between the user equipment and the core network. The (R)AN can also be understood as a base station in the network.

[0119] (R)AN can be a 3GPP-related cellular system. For example, 4G, 5G mobile communication systems, or future evolution systems (such as 6G mobile communication systems). (R)AN can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. (R)AN can also be a communication system that integrates two or more of the above systems. (R)AN can also be called an (R)AN node, or other expressions, such as an access network device. In the following of this application, if there is no special explanation, the access network device will be used for expression.

[0120] Exemplarily, the access network device in the embodiments of the present application may be any communication device with wireless transceiver function for communicating with user equipment. The access network device includes but is not limited to: evolved NodeB (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home evolved NodeB (HeNB, or home Node B, HNB), baseBand unit (BBU), access point (AP) in a wireless fidelity (WiFi) system, wireless relay node, wireless backhaul node, transmission point (TP), or transmission and reception point (TRP), etc. It may also be a 5G device, such as the next generation NodeB (gNB) in an NR system, or a transmission point (TRP or TP), one or a group (including multiple antenna panels) of antenna panels of a base station in a 5G system, or, it may also be a network node constituting a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU), etc. It may also be the next generation base station in a sixth generation mobile communication system, a base station in a future mobile communication system, etc. Optionally, the access network device may also be a wearable device, a vehicle or an in-vehicle device, etc. For example, the access network device in vehicle to everything (V2X) technology may be a road side unit (RSU). It can be understood that all or part of the functions of the access network device in the present application may also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform (such as a cloud platform). The method executed by the access network device in the present application may also be implemented by a logical node, a logical module or software that can implement all or part of the functions of the access network device.

[0121] In some deployments, multiple access network devices cooperate to assist a user equipment in achieving wireless access, and different access network devices respectively implement some functions of a base station. For example, the access network device may be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. The CU and the DU may be separately provided, or may also be included in the same network element, for example, in a baseband unit BBU. The radio unit RU may be included in a radio frequency device or a radio frequency unit, for example, included in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). The CU implements some functions of the access network device, and the DU implements some functions of the access network device. For example, the CU is responsible for processing non-real-time protocols and services, implementing radio resource control (RRC), and the functions of the packet data convergence protocol (PDCP) layer. The DU is responsible for processing physical layer protocols and real-time services, implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer, and the physical (PHY) layer. The AAU implements some physical layer processing functions, radio frequency processing, and related functions of active antennas. The information of the RRC layer is generated by the CU and will ultimately be encapsulated into PHY layer information through the PHY layer of the DU, or transformed from the PHY layer information. Therefore, in this architecture, high-layer signaling such as RRC layer signaling can also be considered to be sent by the DU, or sent by the DU + AAU. It can be understood that the access network device may be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU may be classified as an access network device in the radio access network (RAN), or may be classified as an access network device in the core network (CN), and this application does not make any limitations in this regard.

[0122] It should be understood that the embodiments of the present application can also be applied to fixed networks, such as fixed access networks and transmission networks.

[0123] 3. Data network DN: The operator network mainly used to provide data services for the UE. For example, the Internet, a third-party service network, an IMS network, etc.

[0124] 4. Core Network: It refers to the devices in the core network that provide service support for terminals. The core network is used to complete three major functions: registration, connection, and session management. Currently, some examples of core network devices are: application network elements, network exposure network elements, policy control network elements, session management network elements, access management network elements, and user plane network elements, etc. These network elements in the core network will be described in detail below.

[0125] Application Network Element: In a 5G communication system, this application network element can be an Application Function (AF) network element, which mainly supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing some third-party services to the network side.

[0126] Network Exposure Network Element: In a Long-Term Evolution (LTE) communication system, this network exposure network element can be a Service Capability Exposure Function (SCEF) network element. In a 5G communication system, this network exposure network element can be a Network Exposure Function (NEF) network element, which mainly supports the secure interaction between the 3GPP network and third-party applications. The NEF can securely expose network capabilities and events to third parties to enhance or improve application service quality. The 3GPP network can also securely obtain relevant data from third parties to enhance network intelligent decision-making. At the same time, this network function supports restoring structured data from a unified database or storing structured data in a unified database.

[0127] Session Management Network Element: It is mainly used for session management, allocation and management of the Internet Protocol (IP) address of user equipment, selection of manageable user plane functions, termination of policy control and charging function interfaces, and downlink data notification, etc. In an LTE communication system, this session management network element can be a Serving Gateway Control Plane (SGW-C) or a Packet Data Network Gateway Control Plane (PGW-C) or a network element where SGW-C and PGW-C are co-located. In a 5G communication system, this session management network element can be a Session Management Function (SMF) network element, which completes terminal IP address allocation, UPF selection, and charging and QoS policy control, etc.

[0128] Access management network element: mainly used for mobility management and access management, etc., and can be used to implement other functions of the mobility management entity (MME) function except session management. For example, functions such as legal monitoring and access authorization / authentication. In the LTE communication system, this access management network element can be an MME network element. In the 5G communication system, this access management network element can be the access and mobility management function (AMF), which mainly performs functions such as mobility management and access authentication / authorization. In addition, it is also responsible for transmitting user policies between the terminal and the policy control function (PCF) network element. It should be understood that the access and mobility management network element can also be divided into an access management network element and a mobility management network element.

[0129] Policy control network element: includes functions such as user subscription data management, policy control function, charging policy control function, quality of service (QoS) control, etc., and is a unified policy framework for guiding network behavior, providing policy rule information, etc. for control plane function network elements (such as AMF, SMF network elements, etc.). In the LTE communication system, this policy control network element can be the policy control and charging function (PCRF). In the 5G communication system, this policy control network element can be the PCF network element.

[0130] User plane network element: as an interface to the data network, it completes functions such as user plane data forwarding, session / flow-level charging statistics, bandwidth limitation, etc. That is, packet routing and forwarding and quality of service (QoS) processing of user plane data, etc. In the LTE communication system, this user plane network element can be the serving gateway user plane (SGW-U) or the packet data network gateway user plane (PGW-U) or a network element that combines SGW-U and PGW-U. In the 5G communication system, this user plane network element can be the user plane function (UPF) network element.

[0131] Authentication server function (AUSF) network element: its main functions include user authentication and authorization, etc.

[0132] Network Slice Selection Function (NSSF) network element: Its main functions include the set of network slice examples serving the UE, etc.

[0133] Unified Data Management (UDM) network element: It is mainly used for the subscription data management of the UE, including the storage and management of UE identifiers, access authorization of the UE, etc.

[0134] In future communication systems, such as 6G communication systems, the above-mentioned network elements or devices can still use their names in 4G or 5G communication systems, or they can also have other names, which are not limited in the embodiments of this application. The functions of the above-mentioned network elements or devices can be completed by an independent network element or by several network elements together. In actual deployment, the network elements in the core network can be deployed on the same or different physical devices. For example, as a possible deployment, the AMF and the SMF can be deployed on the same physical device. Another example is that the network elements of the 5G core network can be deployed on the same physical device as the network elements of the 4G core network. This is not limited in the embodiments of this application.

[0135] It can be understood that Figure 1 This is just an example and does not constitute any limitation to the protection scope of this application. The data transmission method provided by the embodiments of this application may also involve Figure 1 network elements not shown in the figure. Of course, the data transmission method provided by the embodiments of this application may also only include Figure 1 some of the network elements shown in the figure.

[0136] In addition, as Figure 1 shown in the figure, the interaction relationships between network function entities and the corresponding interfaces are shown. For example, the UE and the AMF can interact through the N1 interface (NAS), and the interactions between other network function entities are similar and will not be elaborated here; some interfaces can be implemented in the form of service-based interfaces.

[0137] It should be understood that Figure 1 the UE, (R)AN, UPF, and DN in the figure are generally referred to as user layer network function entities, and the data traffic of users can be transmitted through the protocol data unit session (PDU session) established between the UE and the DN. The data transmission process will pass through these two network entities, namely (R)AN and UPF. Other network entities can be called control layer network functions and entities, which are mainly responsible for functions such as authentication and authorization, registration management, session management, mobility management, and policy control, so as to achieve reliable and stable transmission of user layer traffic.

[0138] The 5G system implemented and deployed by the industry as defined by 3GPP, as well as the 5G-A system being defined by 3GPP, for most applications, the 5G system or the 5G-A system is essentially a wireless communication pipeline. In addition to interacting with the terminal device through the air interface and NAS to establish a communication pipeline for data transmission, the network device has very limited control over the service application functions on the terminal device. For example, for the IP Multimedia Subsystem (IMS) service application. The network device can control such service application functions on the terminal device, but cannot manage and control the terminal device operating system and other application layer capabilities, and cannot provide richer service applications.

[0139] Other applications on the terminal device are installed by a third party on the terminal device with software and communicate with systems outside the network through the wireless communication pipeline to implement service functions.

[0140] Currently, KubeEdge is the first open intelligent edge platform based on the extension of Kubernetes that provides cloud-edge collaboration capabilities. Among various solutions, software components similar to those included in the Edge part of KubeEdge can be deployed on small computing platforms (for example, used to directly connect devices such as machines, tools, instruments, etc., such as gateways, industrial control computers, personal computers, servers, etc.), or directly deployed on various intelligent devices (such as cameras, robots, consumer terminal devices, etc.) to achieve data collection and control of the devices. In the embodiments of this application, the edge part deployed on such computing platforms or devices is referred to as the end-side edge (deepedge) to distinguish it from another edge form that is deployed at a higher position and has more computing and storage resources and communication capabilities.

[0141] Kubernetes (also known as "k8s") is a mainstream open-source container cluster orchestration platform that can be used to deploy and manage containerized application software systems on a large scale and easily schedule and orchestrate containers. A container is a lightweight, operating system-level virtualization technology that allows an application and its dependencies to run with resource isolation. All necessary components required to run the application are packaged into a single image, and this image can be reused. When the image runs, it runs in an independent environment and does not share the host operating system's memory, central processing unit (CPU), or disk with other applications. This ensures that the processes inside the container do not affect any processes outside the container. Popular container technologies include Docker, Isula, etc.

[0142] Containers, Kubernetes, and KubeEdge can be installed and deployed on devices running Ubuntu, CentOS, and other Linux operating systems. After adaptation, they can also be deployed on operating systems such as the robot operating system (ROS), Windows, HarmonyOS, OpenHarmony, iOS, and Android. For these containers and platforms, as well as other software components that need to be installed and deployed (such as EdgeMesh, Istio, Mosquitto, etc.), different software tools may be required to complete the full installation and deployment on a specific operating system. These tools include management tools in the form of software packages, libraries, modules, and configuration files, such as kubeadm, keadm, apt-get, apt, dpkg, yum, rpm, snap, and python. By combining the corresponding operating system commands or management tool commands, the installation, update, deletion, and management of software image instances (containers) and other software packages and files can be completed. Table 1 provides examples of software images, software components, management tools, operating system commands, and management tool commands.

[0143] Table 1

[0144]

[0145] Currently, third parties install software on terminal devices and communicate with systems outside the network through wireless communication channels. The on-site deployment of the edge environment at the terminal side is complex, demanding, time-consuming, and unable to meet the needs of a large number of applications. There are the following disadvantages: First, there are many software systems involved in containers, container clusters, cloud-native system architectures, edge-cloud collaboration system architectures, tools, etc., and the technology and software versions are updated rapidly and frequently. Second, the edge deployment environment at the terminal side is strongly related to the terminal hardware device, with different configurations and many variables to consider. Third, most terminal edge devices do not have a user interface (UI), and an additional upper computer needs to be connected for configuration, resulting in many processes and a long on-site deployment time. Fourth, currently, manual operations (installation and deployment, configuration update, operation and maintenance) are mainly relied on, which requires a lot of information technology (IT) knowledge, high requirements, and a long time. With the increasing demand for edge deployment at the terminal side, manual operation of a large number of devices can no longer meet the needs. Fifth, the current automation tools for IT systems require manual intervention to establish network communication between the terminal edge and the central configuration server first, and manual pre-deployment and installation of the boot software at the terminal edge. Due to the large number of software and hardware systems involved, a unified ecosystem cannot be formed, and only some steps can be automated, still requiring a large amount of real-time manual operation.

[0146] Currently, in addition to third parties installing software on terminal devices, software upgrades, version updates, etc. at the edge of the terminal can also be achieved through over-the-air (OTA) technology. OTA technology is mainly used for software upgrades and updates of smartphones and intelligent vehicle systems. Currently, the essence of OTA technology is that the cloud triggers the terminal device to download a software package, and the software upgrade and update are executed on the terminal device side. The OTA upgrade process includes fixed operations such as installation, verification, and activation. These fixed operations have clear purposes and cannot achieve flexible terminal functional changes and complex terminal software management.

[0147] Whether it is the above-mentioned third party installing software on the terminal device or the software management method of realizing fixed operations such as software installation, verification, and activation at the terminal side through OTA technology, the degree of automation is relatively low, and complex software management cannot be achieved. Currently, as a mobile communication network with a vast topology and agile communication status perception capabilities, it essentially only serves as a data transmission channel, which actually does not fully utilize the advantages of the mobile communication network. For example, a mobile communication network with computing infrastructure can provide users with a better service experience, lower costs, and higher efficiency business applications.

[0148] Therefore, in view of the above problems, embodiments of the present application provide a management method and device for different types, uses, and terminal devices with different operating systems, which can flexibly perform function changes and complex terminal software management remotely. The following will be combined with Figures 2 to 14 be described in detail.

[0149] It should be understood that the management method provided by the embodiments of the present application can cooperate with the cloud platform or the edge platform in the form of an edge platform at the terminal side to form a cloud-terminal, edge-terminal, or cloud-edge-terminal solution to complete complex services.

[0150] Figure 2 is a schematic diagram of a network architecture provided by an embodiment of the present application. As Figure 2 shown, the network architecture provided by the present application includes a network device side and a terminal device side.

[0151] The functional network elements or entities on the network device side may include AMF, SMF, UDM, NEF, PCF, (R)AN, and UPF in the current network architecture, etc. Not all functional network elements on the network device side are shown in Figure 2 and the specific functions of these functional network elements can be referred to Figure 1The relevant descriptions in [reference]. In addition, the network device side of the embodiments of the present application may further include new functional network elements: a terminal remote management function (TRMF) network element, a template library, a script library, and a resource repository.

[0152] The terminal remote management function manages and controls the interaction of the software on the terminal device side through non-access stratum signaling or user plane signaling. The TRMF network element can be an independent functional network element, and the TRMF can be combined with the current functional network elements. For example, the TRMF can be combined with Figure 2 one or more of the network elements such as AMF, SMF, UDM, NEF, or PCF in [reference].

[0153] The template library may include an interactive command set, and the interactive command set includes at least one interactive command. The script library includes interactive scripts, and the interactive scripts include multiple interactive commands. The interactive commands may include operating system commands and / or management tool commands, as well as encapsulation, interpretation, and translation of the operating system commands and / or management tool commands. For example, the operating system commands may include, but are not limited to, the commands shown in Table 1, and the management tool commands may include, but are not limited to, the commands shown in Table 1.

[0154] The resource repository is used to store resource information corresponding to management tasks. The resource information includes some or all of software images, management tools, component components, auxiliary tools, license files, etc. For example, the management tools may include software packages, libraries, modules, and configuration files such as kubeadm, keadm, apt-get, apt, dpkg, yum, rpm, snap, python, etc., to complete the installation, update, deletion, and management of software image instances (containers) and other software packages and files. The software components are other software that needs to be installed and deployed, including but not limited to the software shown in Table 1. The auxiliary tools include transmission software packages, CA certificates, etc. The software images include but are not limited to the software images shown in Table 1.

[0155] It should be understood that the template library, the script library, and the resource repository may also be independent network entities, and any one of the template library, the script library, and the resource repository may also be combined with the current functional network elements. The embodiments of the present application do not limit the specific existence forms of the template library, the script library, and the resource repository.

[0156] The terminal device side includes an application layer and an operating system (OS) layer. The application layer includes basic software, which can include software and configurations of types such as container technologies (Docker, containerd, iSula, etc.), platforms or systems (Kubernetes, KubeEdge, etc.), tools (kubeadm, keadm, apt, rpm, etc.), and components (EdgeMesh, Istio, Mosquitto, etc.) installed on the terminal. The operating system layer can also be referred to as the terminal OS. The terminal device side also includes a communication function unit, which includes a transceiver unit and an interaction proxy unit. The transceiver unit has a terminal communication protocol stack such as 3GPP, including protocol stacks for the control plane and the user plane. The interaction proxy unit is used to proxy interaction commands between the network device side and the terminal OS in the terminal device side, that is, the interaction proxy unit can perform command-line calls of the terminal OS. For example, input interaction commands are executed and output of interaction commands is obtained. The terminal OS can run the interaction commands obtained from the interaction proxy unit.

[0157] It should be understood that in addition to applying the terminal remote management in the form of interaction commands provided by the embodiments of the present application, the terminal device side also applies artificial intelligence interaction, prompt word interaction, etc.

[0158] It should be understood that the interaction proxy unit can be located in the operating system layer of the terminal device side or in the application layer. Figure 3 It is a schematic diagram of the architecture of a terminal device provided by the embodiments of the present application.

[0159] As Figure 3 As shown in (a) of

[0160] As Figure 3 As shown in (b) of

[0161] Figure 4It is a schematic flowchart of a management method provided by an embodiment of the present application. It can be understood that the present application takes a terminal device and a network device as the execution entities of the interaction schematic to illustrate the corresponding method, but the present application does not limit the execution entities of the interaction schematic. For example, the method implemented by the terminal device can also be implemented by a module of the terminal device (such as a chip, a chip system, or a processor), and can also be implemented by a logical node, a logical module, or software that can implement all or part of the functions of the terminal device. For the logical module of the terminal device, reference can be made to Figure 3 . The network device may include one or more of functional network elements such as a first management network element, a second management network element, a unified data management UDM network element, and a network open function network element.

[0162] It should be understood that the first management network element is a network element with terminal remote management function. The first management network element may be a newly added management functional network element. For example, the first management network element may be a newly added terminal remote management function TRMF network element, and the second management network element may be an AMF network element. At this time, the first management network element and the second management network element are independent of each other.

[0163] Alternatively, the second functional network element may be an enhanced function on an existing functional network element, that is, the terminal remote management function TRMF is given to an existing functional network element. For example, the terminal remote management function TRMF is given to one of functional network elements such as AMF, SMF, UDM, NEF, or PCF. Specifically, if the second management network element is an AMF network element and the terminal remote management function TRMF is given to the AMF network element, at this time, the first management network element may also be an AMF network element, and the first management network element and the second management network element are the same network element. If the second management network element is an AMF network element and the terminal remote management function TRMF is given to the SMF network element, at this time, the first management network element may also be an SMF network element. If the AMF network element is divided into an access management network element and a mobility management network element, the terminal remote management function TRMF may be given to one of the access management network element and the mobility management network element. The embodiments of the present application do not limit the specific form of the network element with terminal remote management function in the future network.

[0164] S401, the first management network element obtains an interaction command, and the obtained interaction command is used for the terminal device to perform a management operation.

[0165] It should be understood that the obtained interaction command may belong to an interaction command set or an interaction script. Among them, the interaction command set includes multiple interaction commands, and there is a corresponding execution order between the multiple interaction commands. The interaction script also includes multiple interaction commands. The interaction script is a kind of script, that is, an interaction command set existing in the form of a file or an overall message.

[0166] As a possible implementation manner, the obtained interaction command may include an operating system command and / or a management tool command.

[0167] Among them, the operating system commands include commands for managing the operating system of the terminal device, and the management tool commands are commands for calling the management tool software to execute management functions.

[0168] It should be understood that the specific operating system commands may include, but are not limited to, the operating system commands shown in Table 1. The specific management tool commands may include, but are not limited to, the management tool commands shown in Table 1.

[0169] For example, in the Linux system, the interactive command set may include su-, sudo+command, etc., which is a set of operating system commands and / or management tool commands with specific management operations. The interactive command set may also include the processing logic corresponding to the execution result fed back by the terminal device. The interactive command set may also carry a first interaction type identifier. The first interaction type identifier is used to indicate the manner of interacting with the terminal device using the interactive command set, and the first interaction type identifier may also include the effects of the interactive command set on the terminal device, such as installation, update, configuration, deletion, etc.

[0170] Another example is that in the Linux system, an interactive script may include an interactive command set such as su-, sudo+command, which includes operating system commands and / or management tool commands. The interactive script is essentially an interactive command set existing in the form of a file or an overall message. The interactive script may also carry a second interaction type identifier. The second interaction type identifier is used to indicate the manner of interacting with the terminal device using the interactive script, and the second interaction type identifier may also include the effects of the interactive script on the terminal device, such as installation, update, configuration, deletion, etc.

[0171] As a possible implementation, the first management network element obtains the interactive commands from the interactive command library. The interactive command library may include a template library or a script library. The template library includes an interactive command set, and the script library includes an interactive script.

[0172] In some implementations, the first management network element obtains the interactive command set from the template library. Among them, the interactive command set may be pre-configured in the template library.

[0173] The specific pre-configuration method may be through a third-party manufacturer (such as a terminal manufacturer), through the application programming interface (API) interface of the network exposure function (NEF) network element, to configure the interactive command set to the template library, and the template library stores the interactive command set. Or, it may also be configured to the template library through other network network elements, and this application does not limit this.

[0174] In some implementations, the first management network element obtains an interaction script from a script library. Among them, the interaction script can be pre-configured in the script library. The specific pre-configuration method can refer to the above method and will not be elaborated here.

[0175] As a possible implementation, the first management network element directly obtains real-time interaction commands from a third-party manufacturer through the API interface of the network open function network element.

[0176] S402, the first management network element sends an interaction command to the terminal device.

[0177] In a possible implementation, the first management network element sends an interaction command to the terminal device through non-access stratum signaling or user plane signaling.

[0178] It should be understood that the first management network element can directly send an interaction command to the terminal device, or can also send an interaction command to the terminal device through an intermediate function network element, and this application does not limit this.

[0179] It should be understood that subsequently, the method of sending an interaction command through non-access stratum signaling will be described in detail, and the method of sending an interaction command through user plane signaling will be described in detail in combination with Figures 5 to 7 It should be understood that subsequently, the method of sending an interaction command through non-access stratum signaling will be described in detail, and the method of sending an interaction command through user plane signaling will be described in detail in combination with Figures 8 to 10 the method of sending an interaction command through user plane signaling will be described in detail.

[0180] As a possible implementation, if the interaction command obtained in S401 belongs to an interaction command set, the first management network element can send the interaction commands in the interaction command set to the terminal device one by one. Alternatively, the first management network element can also send multiple interaction commands in the interaction command set to the terminal device at one time. This embodiment of the application does not limit this.

[0181] As a possible implementation, if the interaction command obtained in S401 belongs to an interaction script, the first management network element can send the interaction script to the terminal device.

[0182] S403, the terminal device executes the interaction command to obtain the execution result corresponding to the management operation.

[0183] As a possible implementation, if in S402 the first management network element sends the interaction commands in the interaction command set to the terminal device one by one, the terminal device executes the interaction commands in the received interaction command set one by one to obtain the execution result corresponding to the management operation. If in S402 the first management network element sends multiple interaction commands in the interaction command set to the terminal device at one time, the terminal device executes the multiple interaction commands in the received interaction command set to obtain the execution result corresponding to the management operation.

[0184] As a possible implementation, if the first management network element in S402 sends an interaction script to the terminal device, the terminal device executes the received interaction script to obtain an execution result corresponding to the received interaction script.

[0185] It should be understood that Figure 4 the specific unit modules of the terminal device in Figure 3 can be referred to, and no detailed description is given here from the specific unit modules in the terminal device. The subsequent detailed execution process will be specifically described in Figure 5 below.

[0186] Optionally, in S404, the terminal device sends the execution result to the first management network element.

[0187] As a possible implementation, if the terminal device in S403 executes the interaction commands in the received interaction command set one by one, the terminal device can send the execution results to the first management network element one by one.

[0188] Exemplarily, the sequential step descriptions of sending interaction commands one by one, executing interaction commands one by one, and returning execution results one by one in S402 to S404 can be that the first management network element sends a first interaction command to the terminal device, the terminal device executes the first interaction command to obtain a first execution result corresponding to the first interaction command, and sends the first execution result to the first management network element. Subsequently, the first management network element sends a second interaction command to the terminal device, where the second interaction command can be determined according to the first execution result (for example, if the first interaction command is an uncertain command and the first execution result indicates an execution result of the first interaction command, the second interaction command can be a subsequent interaction command corresponding to the first interaction result). The terminal device executes the second interaction command to obtain a second execution result corresponding to the second interaction command, and sends the second execution result to the first management network element. And so on, until the terminal device reaches the end position of the interaction command set.

[0189] Exemplarily, the sequential step descriptions of sending multiple interaction commands at once, executing multiple interaction commands at once, and returning execution results at once in S402 to S404 can be that the first management network element sends multiple third interaction commands to the terminal device, the terminal device executes multiple third interaction commands at once to obtain third execution results corresponding to the multiple third interaction commands, and then sends the third execution results to the first management network element. The subsequent steps are similar to those of sending one by one above and will not be elaborated here. It should be understood that the manner of enabling the terminal device to execute the multiple interaction commands by sending multiple interaction commands at once may also require some auxiliary information, and the embodiments of the present application do not limit the first management network element to send additional auxiliary information.

[0190] In the above technical solution, an interaction command is sent to a terminal device through a mobile network with capabilities such as long connection and control plane signaling, so that the functions of the terminal device can be managed through corresponding command lines in the interaction command, such as programming, enabling the terminal device to achieve flexible function changes and upgrades. In addition, the terminal device can perform joint orchestration with the network and the cloud according to the user's end-to-end service requirements, serving the user's service goals more accurately and efficiently. Ultimately, it is achieved to reduce the installation, deployment, operation, and management difficulties of terminal software, components, and tools, improve personnel efficiency, and accelerate business go-live.

[0191] Optionally, the method for triggering the first management network element to obtain the interaction command in S401 may include the following steps S405 or S406.

[0192] Optionally, in S405, the first management network element obtains first indication information, and the first indication information is used to indicate that the terminal device is configured with permission information for executing the interaction command.

[0193] Among them, the first indication information may include type information of the management operation of the terminal device and / or terminal information. The terminal information may include at least one of, but is not limited to, the terminal hardware model and version, the operating system name and version, the terminal hardware resources and status, the DeepEdgePaaS resource settings reserved by the terminal for the edge on the terminal side, and the terminal identifier.

[0194] As a possible implementation manner, the Unified Data Management (UDM) network element configures permission information for the terminal device to execute the interaction command. The permission information for executing the interaction command may also be referred to as management operation permission information.

[0195] Specifically, the first management network element directly queries the UDM network element from the UDM network element whether the UDM network element has configured permission information for the terminal device to execute the interaction command, and then obtains the first indication information from the UDM network element. The detailed method will be Figure 5 specifically described in

[0196] It should be understood that the first management network element learns through the first indication information that the terminal device can be remotely managed by the interaction command.

[0197] Optionally, the first management network element obtains the interaction command according to the first indication information.

[0198] As a possible implementation manner, if the first management network element is an independently added TRMF network element, the first management network element may receive the first indication information from the second management network element, and the second management network element may obtain the first indication information from the Unified Data Management (UDM) network element.

[0199] Optionally, in S406, the first management network element obtains second indication information from the second management network element, and the second indication information is used to indicate that the terminal device has opened the execution permission of the interaction command.

[0200] It should be understood that if the first management network element obtains the second indication information, the second indication information may trigger the first management network element to obtain an interaction command.

[0201] Optionally, the first management network element obtains an interaction command according to the second indication information.

[0202] In some implementation manners, the UDM network element configures permission information for executing an interaction command for all terminal devices. At this time, the first management network element does not need to obtain the first indication information and can directly obtain an interaction command according to the second indication information.

[0203] Optionally, in S407, the terminal device determines the status information of the debugging switch. The debugging switch may be a physical switch of the terminal device or may also be a switch control or selection control of the user interaction interface with a screen of the terminal device.

[0204] Optionally, in S408, the terminal device sends the second indication information to the second management network element. The second indication information may include the status information that the debugging switch is turned on, or the second indication information may also include the type information of the management operation and / or the terminal information.

[0205] As a possible implementation manner, when the status information of the debugging switch is turned on, the terminal device sends the second indication information to the second management network element.

[0206] Optionally, in S409, the second management network element obtains the management operation permission information of the terminal device from the unified data management UDM network element according to the second indication information.

[0207] As a possible implementation manner, the first indication information in S405 may also be obtained by the first management network element according to the second indication information.

[0208] If the unified data management UDM network element configures permission information for the terminal device to execute an interaction command, the second management network element sends the first indication information to the first management network element.

[0209] If the unified data management UDM network element does not configure permission information for the terminal device to execute an interaction command, the second management network element sends indication information not to perform a management operation on the terminal device to the first management network element.

[0210] Optionally, after S404, in S410, the first management network element obtains the identification information of the resource repository according to the execution result.

[0211] Among them, the resource repository includes at least one of a software image, a management tool, a component software package, an auxiliary tool, and a license file.

[0212] Exemplarily, the management tool may include at least one of the following information: software packages, libraries, modules, configuration files such as kubeadm, keadm, apt-get, apt, dpkg, yum, rpm, snap, python, etc., to complete the installation, update, deletion, and management of software image instances (containers) and other software packages and files. The component software packages may include other software that needs to be installed and deployed. The auxiliary tool may include a transmission software package or a certificate authority (CA) certificate, etc.

[0213] Specifically, the first management network element performs specific management tasks indicated by the execution result. For example, the management tasks may include system initialization, software installation, update, deletion, configuration, control, obtaining resources on the terminal, etc.

[0214] Optionally, in S411, the first management network element sends third indication information to the terminal device, and the third indication information includes the identification information of the resource repository.

[0215] Exemplarily, the identification information may include the data network name (DNN) of the resource repository and / or the identification of the resource repository.

[0216] Specifically, if the first management network element is a network element with independent TRMF and the second management network element is an AMF network element, the first management network element may send the third indication information to the terminal device through the second management network element. For example, send the third indication information to the terminal device through non-access stratum signaling. Or, send the third indication information to the terminal device through user plane signaling.

[0217] If the first management network element is an AMF network element and has the terminal remote management function TRMF, the first management network element may directly send the third indication information to the terminal.

[0218] Optionally, in S412, the terminal device may obtain the information in the resource repository from the resource repository according to the identification information of the resource repository.

[0219] Optionally, in S413, the terminal device performs corresponding management tasks according to the information in the resource repository.

[0220] It should be understood that the detailed processes of S410 to S413 will be described in detail in Figure 11 in.

[0221] The following will be combined with Figures 5 to 7The detailed description is as follows: The TRMF network element with the terminal remote management function sends remote interaction commands to the terminal device through non-access stratum signaling, so that the terminal device performs the management operations corresponding to the interaction commands. To clearly illustrate the terminal remote management function TRMF, in Figures 5 to 7 the first management network element is taken as an independent TRMF network element as an example for description.

[0222] Figure 5 is a schematic flowchart of another management method provided by an embodiment of the present application. It can be understood that the present application takes the terminal device and the network device as the execution entities of the interaction schematic to illustrate the corresponding method, but the present application does not limit the execution entities of the interaction schematic. For example, the method implemented by the terminal device can also be implemented by a module of the terminal device (such as a chip, a chip system or a processor), and can also be implemented by a logical node, a logical module or software that can implement all or part of the functions of the terminal device. For the logical module of the terminal device, reference can be made to Figure 3 . The network device may include functional network elements. For example, Figure 5 the AMF, TRMF, UDM, NEF and template library shown.

[0223] It should be understood that the AMF may be Figure 4 the second management network element in Figure 4 , and the TRMF may be Figure 5 the first management network element in

[0224] S501a, the terminal device sends terminal information to the AMF.

[0225] Specifically, the communication function unit of the terminal device sends terminal information to the AMF. For example, as shown in Figure 3 , the transceiver unit of the terminal device sends terminal information to the AMF. Another example is that, as shown in Figure 3 , the interaction proxy unit (OS interaction proxy unit or application layer interaction proxy unit) of the terminal device outputs terminal information to the transceiver unit, and the transceiver unit then sends the terminal information to the AMF.

[0226] S501b, the UDM configures management operation permission information for the terminal device, and the management operation permission information is used to indicate that the terminal device is allowed to perform management operations through interaction commands.

[0227] Specifically, the UDM obtains the terminal information of the terminal device from the AMF, and the UDM configures management operation permission information according to the terminal information of the terminal device.

[0228] Optionally, the management operation permission information may further include type information of the management operations implemented on the terminal device.

[0229] It should be understood that the UDM configuring the management operation permission information for the terminal device may also be referred to as the UDM configuring the subscription information of the terminal management operation for the terminal device. For example, the subscription information is used to indicate that the terminal device has a subscription that can be controlled by remote interaction commands, or the subscription information is used to indicate that the terminal device has a subscription that can be installed and deployed with software by remote interaction commands, or the subscription information is used to indicate that the terminal device can run software services by remote interaction commands after the software is installed and deployed. This application does not limit the type of management operation corresponding to the management operation permission information and the specific subscription type indicated by the subscription information.

[0230] S501c, the template library stores an interaction command set, and the interaction command set includes at least one interaction command.

[0231] It should be understood that for a detailed explanation of the interaction command, reference can be made to S401, which will not be elaborated here.

[0232] As a possible implementation, the interaction command set can be pre-configured in the template library through high-layer signaling.

[0233] As a possible implementation, S501d, the NEF configures an interaction command set for the terminal device in the template library.

[0234] Among them, the NEF has an API interface, and the terminal manufacturer can configure the interaction command set in the template library through the API interface of the NEF.

[0235] It should be understood that S501a, S501b, S501c, and S501d can all be referred to as the first preprocessing process, and this preprocessing process is an optional step. For example, the UDM can configure the management operation permission information for all terminal devices. In this case, there is no need to configure it separately for this terminal device. Another example is that the interaction command set can be pre-configured in the template library by other means. Another example is that the terminal information does not need to be sent to the AMF in advance.

[0236] S502a, the terminal operating system (OS) of the terminal device determines the status information of the debug switch. Among them, the status information of the debug switch can indicate that the debug switch is in the on or off state.

[0237] Specifically, the terminal operating system of the terminal device receives a first operation instruction and determines the status information of the debug switch. Among them, the first operation instruction can be to turn on or off the debug switch. Or, the terminal operating system of the terminal device determines the status information of the debug switch by obtaining the initial state of the debug switch, and the initial state of the debug switch can be in the on or off state.

[0238] S502b. The terminal OS of the terminal device transmits second indication information to the communication function unit. The second indication information is used to indicate that the terminal device has enabled the execution permission for the interaction command.

[0239] It should be understood that the specific content that the second indication information may include can refer to S408 and will not be elaborated here.

[0240] Specifically, the communication function unit includes a transceiver unit and an interaction proxy unit. The second indication information may be transmitted by the terminal OS to the interaction proxy unit and then transmitted to the transceiver unit through the transmission proxy unit.

[0241] S502c. The communication function unit sends the second indication information to the AMF. The AMF receives the second indication information from the communication function unit.

[0242] Specifically, the transceiver unit of the terminal device sends the second indication information to the AMF.

[0243] S503a. The AMF requests the management operation permission information of the terminal device from the UDM according to the second indication information and obtains the management operation permission information from the UDM.

[0244] Specifically, if the management operation permission information indicates that the UDM has not configured the permission information for the terminal device to execute the interaction command, the network-side functional network element will not perform remote management operations on the terminal device.

[0245] If the management operation permission information indicates that the UDM has configured the permission information for the terminal device to execute the interaction command, then S503b is executed. The AMF sends the first indication information to the TRMF. The first indication information is used to indicate that the terminal device has configured the permission information for the interaction command.

[0246] It should be understood that the specific content that the first indication information may include can refer to S405 and will not be elaborated here.

[0247] S504a. The TRMF requests the interaction command set from the template library according to the first indication information.

[0248] It should be understood that when the TRMF requests the interaction command set from the template library, the request may include the type information of the management operation and / or the terminal information.

[0249] Specifically, the TRMF determines to perform a management operation on the terminal device according to the first indication information to request the interaction command set corresponding to the type of the management operation from the template library.

[0250] S504b. The template library sends the interaction command set to the TRMF, and the TRMF obtains the interaction command set from the template library.

[0251] Specifically, the template library sends an interaction command set to the TRMF according to the type information of the management operation and / or the terminal information.

[0252] It should be understood that the detailed explanation of the interaction command set can be referred to in S401 and will not be elaborated here. In addition, S504a and S504b are the first ways to obtain the interaction commands.

[0253] S505a, if the NEF has an API interface, the TRMF requests an interaction command from the NEF according to the first indication information.

[0254] It should be understood that when the TRMF requests an interaction command from the NEF, the request may include the type information of the management operation and / or the terminal information.

[0255] Specifically, the NEF requests an interaction command from a third-party manufacturer through the API interface according to the first indication information.

[0256] S505b, the NEF sends a first interaction command to the TRMF, and the TRMF obtains the first interaction command from the NEF.

[0257] It should be understood that the first interaction command may be an interaction command corresponding to the type information of the management operation.

[0258] It should be understood that S505a and S505b are the second ways to obtain the interaction commands. The embodiments of the present application do not limit whether the interaction commands are obtained through the first way or the second way.

[0259] S506a, the TRMF sends interaction commands to the communication function unit of the terminal device one by one through NAS signaling.

[0260] Exemplarily, the TRMF sends a first interaction command to the transceiver unit of the terminal device through NAS signaling, and the transceiver unit sends the first interaction command to the interaction proxy unit.

[0261] S506b, the communication function unit of the terminal device sends interaction commands to the terminal OS one by one, and the terminal OS executes the interaction commands one by one to obtain an execution result.

[0262] Exemplarily, the interaction proxy unit sends a first interaction command to the terminal OS, the terminal OS receives the first interaction command from the interaction proxy unit, and the terminal OS executes the first interaction command to obtain a first execution result corresponding to the first interaction command.

[0263] S506c, the terminal OS outputs the execution result of the interaction command to the communication function unit, and the communication function unit sends the execution result to the TRMF through NAS signaling.

[0264] Exemplarily, the terminal OS outputs the first execution result to the interaction agent unit, the interaction agent unit outputs the first execution result to the transceiver unit, and the transceiver unit sends the first execution result to the TRMF via NAS signaling.

[0265] It should be understood that if the interaction command set is obtained through the interaction command acquisition method 1, the TRMF determines the second interaction command according to the first execution result and the processing logic in the interaction command set, and continues to implement the command interaction with the terminal device in the manner of S506a to S506c. The TRMF continuously interacts with the terminal device until the management operation of the interaction command set is completed, that is, until the terminal device executes to the end position of the interaction command set.

[0266] Optionally, if the interaction command is obtained through the interaction command acquisition method 2, S506d is executed. The TRMF sends the first execution result to the third-party vendor through the API interface of the NEF. Subsequently, the third-party vendor sends the second interaction command to the TRMF according to the first execution result. The TRMF continues to implement the command interaction with the terminal device in the manner of S506a to S506c, and the third-party vendor and the TRMF continuously interact with the terminal device through the API interface of the NEF until the third-party vendor indicates that the management operation is completed, that is, until the terminal device executes to the last interaction command corresponding to the management operation.

[0267] Figure 6 The flowchart of another management method provided by the embodiments of this application. It can be understood that Figure 6 the execution subject of the flowchart and Figure 5 are similar, and the detailed description can refer to Figure 5 the relevant part, which will not be elaborated here. Regarding the logical modules of the terminal device, reference can be made to Figure 3 . The network device may include functional network elements, for example, Figure 6 the AMF, TRMF, UDM, NEF, and script library shown.

[0268] S601a, the terminal device sends terminal information to the AMF.

[0269] S601b, the UDM configures management operation permission information for the terminal device, and the management operation permission information is used to indicate that the terminal device is allowed to execute management operations through interaction commands.

[0270] It should be understood that S601a is similar to S501a, and S601b is similar to S501b, which will not be elaborated here.

[0271] S601c, the script library stores interaction scripts, and the interaction scripts include multiple interaction commands.

[0272] It should be understood that the method of pre-configuring the interaction script in the script library can refer to the method of pre-configuring the interaction command set in the template library in S501c, which will not be elaborated here.

[0273] It should be understood that S601a, S601b, S601c, and S601d can all be referred to as the second preprocessing process, and this preprocessing process is also an optional step.

[0274] The steps of S602a to S602c are similar to the steps of S502a to S502c. For specific reference, please refer to the above description, which will not be elaborated here.

[0275] The steps of S603a to S603b are similar to the steps of S503a to S503c. For specific reference, please refer to the above description, which will not be elaborated here.

[0276] S604a, according to the first indication information, the TRMF requests an interaction script from the script library.

[0277] S604b, the script library sends the interaction script to the TRMF, and the TRMF obtains the interaction script from the script library.

[0278] It should be understood that the detailed explanation of the interaction script can refer to S401, which will not be elaborated here. The steps of S604a and S604b are similar to the steps of S504a and S504b, and the detailed explanation will not be elaborated here. In addition, S604a and S604b are the third method for obtaining interaction commands.

[0279] S605a, if the NEF has an API interface, according to the first indication information, the TRMF requests an interaction script from the NEF.

[0280] S605b, the NEF sends the interaction script to the TRMF, and the TRMF obtains the interaction script from the NEF.

[0281] It should be understood that S605a and S605b are the fourth method for obtaining interaction commands. The embodiments of the present application do not limit whether the interaction script is obtained through the third method or the fourth method. The steps of S605a and S605b are similar to the steps of S505a and S505b, and the detailed explanation will not be elaborated here.

[0282] S606a, the TRMF sends the interaction script to the communication function unit of the terminal device through the NAS signaling.

[0283] Exemplarily, the TRMF sends the first interaction script to the transceiver unit of the terminal device through the NAS signaling, and the transceiver unit sends the first interaction script to the interaction proxy unit.

[0284] S606b, the communication function unit of the terminal device executes the interaction script and sends the obtained interaction command to the terminal OS.

[0285] Exemplarily, the interaction agent unit executes a first interaction script to obtain a first interaction command, and realizes the interaction with the terminal OS through the command line call of the first interaction command of the first interaction script.

[0286] S606c, the terminal OS executes the interaction command to obtain an execution result, and sends the execution result to the communication function unit.

[0287] Exemplarily, the terminal OS executes the first interaction command of the first interaction script to obtain the first execution result of the first interaction command, and outputs the first execution result of the first interaction command to the interaction agent unit.

[0288] It should be understood that the steps of S606b and S606c may be that the interaction agent unit realizes the call of the interaction command line in the terminal OS by running the interaction script, thereby realizing the interaction between the interaction agent unit and the terminal OS, and further obtaining the execution result of the interaction script.

[0289] Specifically, the interaction agent unit in the communication function unit determines a second interaction command according to the processing logic in the interaction script, and continues to realize the command interaction with the terminal OS in the manner of S606b and S606c. The interaction agent unit continuously interacts with the terminal OS until the management operation of the first interaction script is completed, that is, until the terminal OS executes to the end position of the first interaction script. Finally, the execution result of the first interaction script is obtained.

[0290] S606d, the communication function unit sends the execution result of the interaction script to the TRMF through the NAS signaling.

[0291] Exemplarily, the interaction agent unit outputs the execution result corresponding to the first interaction script to the transceiver unit, and the transceiver unit sends the execution result of the first interaction script to the TRMF through the NAS signaling.

[0292] Optionally, if the interaction script is obtained through the fourth interaction command acquisition method, then S606e is executed, and the TRMF sends the execution result of the interaction script to the third-party manufacturer through the API interface of the NEF.

[0293] In one implementation, part of the management tasks of the terminal device can be managed through Figure 5 the implementation method, and other management tasks of the terminal device can also be managed through Figure 6 the implementation method. Specifically, it will be described in detail in combination with Figure 7 this.

[0294] Figure 7 is a schematic flowchart of another management method provided by the embodiments of the present application. It can be understood Figure 7The execution entity of the process schematic diagram and Figure 5 is similar. For detailed descriptions, reference can be made to Figure 5 the relevant parts, which will not be elaborated here. Regarding the logic modules of the terminal device, reference can be made to Figure 3 . The network device may include functional network elements. For example, Figure 7 the AMF, TRMF, UDM, NEF, template library, and script library shown in

[0295] S701a: Implement the first pre - process among the terminal device, AMF, UDM, template library, and NEF.

[0296] It should be understood that for the specific steps included in the first pre - process and the corresponding explanations, reference can be made to Figure 5 , which will not be elaborated here.

[0297] S701b: Implement the second pre - process among the terminal device, AMF, UDM, script library, and NEF.

[0298] It should be understood that for the specific steps included in the second pre - process and the corresponding explanations, reference can be made to Figure 6 . The repeated steps in the first pre - process and the second pre - process do not need to be implemented repeatedly, and the steps in the terminal of the first pre - process and the second pre - process are optional steps.

[0299] S702: Implement the step of obtaining the first indication information among the terminal device, AMF, TRMF, and UDM.

[0300] It should be understood that for the detailed steps of S702, reference can be made to the steps of S502a to S502c and the steps of S503a to S503b, which will not be elaborated here.

[0301] S703a: Implement the acquisition of the interactive command set between the TRMF and the template library.

[0302] Optionally, S703b: Implement the acquisition of the first interactive command between the TRMF and the NEF.

[0303] It should be understood that for the specific steps included in S703a, reference can be made to Figure 5 the steps included in the first acquisition method shown in Figure 5 and for the specific steps included in S703b, reference can be made to

[0304] S704: Implement the interaction process of the interactive command and the execution result among the terminal device, TRMF, and NEF through NAS signaling.

[0305] It should be understood that for the specific steps included in S704, reference can be made to Figure 5The specific steps of S506a to S506d shown are not elaborated here. It should also be understood that if the interaction command set is obtained through the first method of obtaining interaction commands, only S704 needs to be implemented between the terminal device and the TRMF.

[0306] S705a, if the first execution result corresponding to the first interaction command indicates a determined management operation, the TRMF requests the first interaction script corresponding to the determined management operation from the NEF or the script library.

[0307] S705b, the NEF or the script library sends the first interaction script to the TRMF.

[0308] It should be understood that the first interaction command can be directly obtained from a third-party manufacturer through the API interface of the NEF in S704, or the first interaction command can be an interaction command in the interaction command set obtained from the template library in S704. Among them, the first interaction command is uncertain. For example, the first interaction command can be an interaction command with uncertainty such as a judgment command line or a selection command line.

[0309] In other words, the first execution result indicates a certain judgment branch or a certain selection branch in the first interaction command, and the interaction command corresponding to the subsequent management operation of the judgment branch or the selection branch is certain.

[0310] It should be understood that the embodiments of the present application do not limit the acquisition method of the first interaction script corresponding to the determined management operation. The first interaction script can be directly obtained from the script library (the specific steps refer to Figure 6 SS604a and S604b in). Or the first interaction script can also be obtained from a third-party manufacturer through the API interface of the NEF (the specific steps can refer to Figure 6 SS605a and S605b in).

[0311] S706, between the terminal device, the TRMF, and the NEF, the interaction process of the interaction script and the execution result is implemented through the NAS signaling.

[0312] It should be understood that the specific steps included in S706 can refer to Figure 6 the specific steps of S606a to S606e shown, which are not elaborated here. It should also be understood that if the interaction script is obtained through the third method of obtaining interaction commands, only S706 needs to be implemented between the terminal device and the TRMF.

[0313] In the above technical solution, for the management operations corresponding to the interactive commands with uncertainties, after the terminal OS executes the interactive commands, the subsequent execution branches can be determined. If the execution branches corresponding to the subsequent management operations are clear, the subsequent management of the terminal device can be implemented through the interactive script. In this way, by combining the advantages of high real-time performance of the real-time feedback interactive commands and few interactive signaling of the interactive script, the delay of managing the terminal device can be reduced.

[0314] The following will combine Figures 8 to 10 to detail how a network element with the terminal remote management function sends remote interactive commands to the terminal device through the user plane signaling, enabling the terminal device to execute the management operations corresponding to the interactive commands. To clearly illustrate the terminal remote management function, similarly, in Figures 8 to 10 the first management network element is taken as an independent TRMF network element for illustration.

[0315] Figure 8 is a schematic flowchart of another management method provided by an embodiment of the present application. It can be understood that Figure 8 the execution subject of the schematic flowchart is the same as that of Figure 5 For detailed description, reference can be made to Figure 5 the relevant part of Figure 3 . Regarding the logical modules of the terminal device, reference can be made to Figure 8 . The network device may include functional network elements, for example,

[0316] S801, implement the first preprocessing process among the terminal device, AMF, UDM, template library, and NEF.

[0317] It should be understood that the specific steps included in the first preprocessing process and the corresponding explanations can be referred to Figure 5 , which will not be elaborated here.

[0318] S802, implement the step of obtaining the first indication information among the terminal device, AMF, TRMF, and UDM.

[0319] It should be understood that the detailed steps of S802 can be referred to the steps of S502a to S502c and the steps of S503a to S503b, which will not be elaborated here.

[0320] S803a, implement obtaining the interactive command set between the TRMF and the template library.

[0321] Optionally, S803b, implement obtaining the first interactive command between the TRMF and the NEF.

[0322] It should be understood that the specific steps included in S803a can be referred to Figure 5The steps included in the first acquisition method shown, and the specific steps included in S803b can be referred to Figure 5 the steps included in the second acquisition method shown.

[0323] S804a: Through NAS signaling, the TRMF sends the fourth indication information to the communication function unit of the terminal device, and the fourth indication information is used to indicate that the terminal device and the TRMF establish a user plane connection.

[0324] Specifically, the TRMF may send the fourth indication information to the AMF, the AMF encapsulates the fourth indication information in the NAS signaling, and the AMF sends the fourth indication information to the communication function unit of the terminal device through the NAS signaling.

[0325] Alternatively, the TRMF may directly encapsulate the fourth indication information in the NAS signaling, the TRMF sends the NAS signaling to the AMF, and the AMF forwards the NAS signaling to the communication function unit of the terminal device.

[0326] Wherein, the fourth indication information may include a data network name DNN for identifying the target TRMF to be connected and / or an identifier of the target TRMF.

[0327] It should be understood that there may be multiple TRMF network elements on the network device side, and the current TRMF that executes S801 to S803a / S803b and the step of sending the fourth indication information to the AMF in S804a may be the same entity or a different entity from the target TRMF. Figure 9 The current TRMF and the target TRMF shown in are the same entity.

[0328] S804b: The communication function unit of the terminal device establishes a user plane channel through the SMF and the UPF according to the DNN of the target TRMF.

[0329] In other words, the transceiver unit of the communication function unit of the terminal device establishes a protocol data unit session (PDU session) through the SMF and the UPF according to the DNN of the target TRMF.

[0330] S804c: The communication function unit of the terminal device establishes a user plane connection with the target TRMF according to the identifier of the target TRMF.

[0331] Specifically, the transceiver unit in the communication function unit of the terminal device obtains the entity IP address of the target TRMF through methods such as address query (such as domain name system (DNS) query) using the identifier of the target TRMF, and establishes user plane application layer communication with the target TRMF.

[0332] Optionally, when establishing a user plane connection, the terminal device sends the type information of the management operation and / or the terminal information to the target TRMF.

[0333] It should be understood that when the current TRMF and the target TRMF are different entities, the target TRMF can re-obtain the interaction command set in the network. For example, if the target TRMF that establishes a connection with the terminal does not query that the interaction command set of the terminal device is stored locally, then through querying according to the terminal information in the network, the TRMF entity that stores the interaction command set of the terminal device is obtained, and the interaction command set of the terminal device is obtained. Another example, if the target TRMF that establishes a connection with the terminal does not query that the interaction command set of the terminal device is stored locally, then according to the type information of the management operation and / or the terminal information, the interaction command set or interaction command is re-obtained from the template library or the NEF. The embodiments of the present application do not limit the manner in which the target TRMF re-obtains the interaction command.

[0334] S805a, the target TRMF sends the interaction commands to the communication function unit of the terminal device one by one through the user plane signaling.

[0335] S805b, the communication function unit of the terminal device sends the interaction commands to the terminal OS one by one, and the terminal OS executes the interaction commands one by one to obtain the execution results.

[0336] S805c, the terminal OS outputs the execution results of the interaction commands to the communication function unit, and the communication function unit sends the execution results to the TRMF through the user plane signaling.

[0337] It should be understood that the steps of S805a to S805c are similar to the steps of S506a to S506c. The difference is that Figure 5 in the steps of S506a to S506c, the terminal device and the TRMF interact through the NAS signaling, Figure 8 in the steps of S805a to S805c, the terminal device and the TRMF interact through the user plane signaling. Therefore, the detailed description of the steps of S805a to S805c will not be repeated here.

[0338] Optionally, if the interaction commands are obtained through S803b, then S805d is executed. The TRMF sends the first execution result to the third-party manufacturer through the API interface of the NEF. Subsequently, the third-party manufacturer sends the second interaction command to the TRMF according to the first execution result. The TRMF continues to interact with the terminal device through the manner of S805a to S805c, and the third-party manufacturer continuously interacts with the terminal device through the API interface of the NEF and the TRMF until the third-party manufacturer indicates that the management operation is completed, that is, until the terminal device executes the last interaction command corresponding to the management operation.

[0339] Figure 9 It is a schematic flowchart of another management method provided by an embodiment of this application. It can be understood that Figure 9 the execution subject of the schematic flowchart of the process and Figure 5 are similar. For detailed descriptions, reference can be made to Figure 5 the relevant parts of Figure 3 . The network device may include functional network elements. For example, Figure 9 the AMF, TRMF, UDM, NEF, SMF, UPF, and script library shown in

[0340] S901: Implement a second pre - process among the terminal device, AMF, UDM, script library, and NEF.

[0341] It should be understood that the specific steps included in the second pre - process and the corresponding explanations can be referred to Figure 6 , and details are not elaborated here.

[0342] S902: Implement the step of obtaining the first indication information among the terminal device, AMF, TRMF, and UDM.

[0343] It should be understood that the detailed steps of S902 can be referred to the steps of S502a to S502c and the steps of S503a to S503b, and details are not elaborated here.

[0344] S903a: Implement obtaining an interaction script between the TRMF and the script library.

[0345] Optionally, S903b: Implement obtaining an interaction script between the TRMF and the NEF.

[0346] It should be understood that the specific steps included in S903a can be referred to Figure 6 the steps included in obtaining method three shown in Figure 6 the steps included in obtaining method four shown in

[0347] The steps of S904a to S904c are similar to the steps of S804a to S804c, and details are not elaborated here.

[0348] S905a: The TRMF sends the interaction script to the communication function unit of the terminal device through user - plane signaling.

[0349] S905b: The communication function unit of the terminal device executes the interaction script and sends the obtained interaction command to the terminal OS.

[0350] S905c: The terminal OS executes the interaction command, obtains the execution result, and sends the execution result to the communication function unit.

[0351] For S905d, the communication function unit sends the execution result of the interaction script to the TRMF via user plane signaling.

[0352] Optionally, if the interaction script is obtained through S903b, then S905e is executed, and the TRMF sends the execution result of the interaction script to the third-party vendor via the API interface of the NEF.

[0353] It should be understood that the steps of S905a to S905e are similar to the steps of S606a to S606e, with the difference being that Figure 6 in the steps of S606a to S606e, the terminal device and the TRMF interact via NAS signaling, Figure 9 and in the steps of S905a to S905e, the terminal device and the TRMF interact via user plane signaling. Therefore, the detailed description of the steps of S905a to S905e will not be elaborated here.

[0354] Similarly, similar to Figures 5 to 7 information transmission via NAS signaling, in one implementation, management operations for some management tasks of the terminal device can be performed through Figure 8 the implementation method, and management operations for other management tasks of the terminal device can also be performed through Figure 9 the implementation method. Specific details will be described in combination with Figure 10 for detailed explanation.

[0355] Figure 10 is a schematic flowchart of another management method provided by an embodiment of the present application. It can be understood that Figure 10 the execution entity of the flowchart and Figure 5 are similar, and the detailed description can refer to Figure 5 the relevant part, which will not be elaborated here. Regarding the logical modules of the terminal device, reference can be made to Figure 3 . The network device may include functional network elements, for example, Figure 10 the AMF, TRMF, UDM, NEF, SMF, UPF, template library, and script library shown in

[0356] S1001a, implement the first pre - process among the terminal device, AMF, UDM, template library, and NEF.

[0357] S1001b, implement the second pre - process among the terminal device, AMF, UDM, script library, and NEF.

[0358] It should be understood that the specific steps included in the first pre - process and the corresponding explanations can be referred to Figure 5 , and the specific steps included in the second pre - process and the corresponding explanations can be referred to Figure 6, which will not be elaborated here. It should be understood that the repeated steps in the first pre - process and the second pre - process do not need to be implemented repeatedly.

[0359] S1002. Implement the step of obtaining the first indication information among the terminal device, AMF, TRMF, and UDM.

[0360] It should be understood that the detailed steps of S1002 can refer to the steps of S502a to S502c and the steps of S503a to S503b, which will not be elaborated here.

[0361] S1003a. Implement obtaining the interaction command set between the TRMF and the template library.

[0362] Optionally, S1003b. Implement obtaining the first interaction command between the TRMF and the NEF.

[0363] It should be understood that the specific steps included in S1003a can refer to Figure 5 the steps included in the acquisition method one shown, and the specific steps included in S1003b can refer to Figure 5 the steps included in the acquisition method two shown.

[0364] S1004. Implement the establishment of the user plane between the terminal device and the TRMF among the terminal device, SMF, UPF, and TRMF.

[0365] It should be understood that the specific steps included in S1004 can refer to Figure 8 the steps S804a to S804c in

[0366] S1005. Implement the interaction process of the interaction command and the execution result between the terminal device, the TRMF, and the NEF through the user plane signaling.

[0367] It should be understood that the specific steps included in S1005 can refer to Figure 8 the specific steps of S805a to S804e shown, which will not be elaborated here. It should also be understood that if S1003a obtains the interaction command set, only S1005 needs to be implemented between the terminal device and the TRMF.

[0368] S1006a. If the first execution result indication corresponding to the first interaction command determines a management operation, the TRMF requests the first interaction script corresponding to the determined management operation from the NEF or the script library.

[0369] S1006b. The NEF or the script library sends the first interaction script to the TRMF.

[0370] It should be understood that the detailed processes of S1006a and S1006b can refer to S705a and S705b, which will not be elaborated here.

[0371] S1007. Implement the interaction process of the interaction script and the execution result between the terminal device, the TRMF, and the NEF through user plane signaling.

[0372] It should be understood that the specific steps included in S1007 can refer to Figure 6 the specific steps of S606a to S606e shown, which will not be elaborated here. It should also be understood that if the interaction script is obtained through the third method of obtaining the interaction command, only S1007 needs to be implemented between the terminal device and the TRMF.

[0373] In the above Figures 5 to 10 execution process of the interaction command, if in a specific management operation, the terminal device needs to obtain resource information from the network device side before it can complete a specific management task. For example, when installing software on the terminal device side, it is necessary to obtain the software image in advance before the software installation.

[0374] Figure 11 is a schematic flowchart of another management method provided by an embodiment of the present application. It can be understood that Figure 11 the execution entity of the schematic flowchart and Figure 5 is similar, and the detailed description can refer to Figure 5 the relevant part, which will not be elaborated here. Regarding the logical modules of the terminal device, reference can be made to Figure 3 . The network device may include functional network elements. For example, Figure 10 the AMF, TRMF, UDM, NEF, SMF, UPF, template library, resource repository, and script library shown.

[0375] It should be understood that the resource information that can be included in the resource repository can refer to the above description of the resource repository, which will not be elaborated here.

[0376] S1101a and S1101b can refer to Figure 5 the first configuration process in Figure 6 and the second configuration process in

[0377] S1101c. The NEF configures resource information in the resource repository. S1101d. The resource repository stores the resource information.

[0378] Among them, the NEF may include an API interface, and a third-party manufacturer sends resource information to the NEF through the API interface of the NEF.

[0379] It should be understood that S1101c and S1101d can also be optional steps, and the resource information can also be configured in the resource repository by other means. The embodiments of the present application do not limit this.

[0380] The specific steps of S1102, S1103a, and S1103b can refer to Figures 5 to 10 the relevant steps, which will not be elaborated here.

[0381] The relevant steps of S1104a can refer to Figure 5 and Figure 6 the relevant steps. The relevant steps of S1104b can refer to Figure 8 and Figure 9 the relevant steps, which will not be elaborated here.

[0382] S1105a, based on the execution result, the TRMF determines that the terminal device needs to obtain resource information from the resource repository.

[0383] Exemplarily, if the execution result is used to indicate that software needs to be installed on the terminal device, it is determined that the terminal device needs to obtain the software image corresponding to the software from the resource repository.

[0384] Specifically, the TRMF obtains the identification information of the target resource repository according to the execution result.

[0385] S1105b, the TRMF sends the third indication information to the communication function unit of the terminal device. The third indication information is used to indicate that the terminal device and the resource repository establish a user plane connection.

[0386] Among them, the third indication information includes the identification information of the target resource repository. For example, the identification information may include the data network name (DNN) of the resource repository and / or the identifier of the resource repository.

[0387] Specifically, the TRMF may send the third indication information to the AMF. The AMF encapsulates the third indication information in the NAS signaling, and the AMF sends the third indication information to the communication function unit of the terminal device through the NAS signaling.

[0388] Alternatively, the TRMF may directly encapsulate the third indication information in the NAS signaling, the TRMF sends the NAS signaling to the AMF, and the AMF forwards the NAS signaling to the communication function unit of the terminal device.

[0389] It should be understood that there may be multiple resource repositories, and different resource repositories may include different resource information.

[0390] Optionally, before S1105b, the TRMF determines the identification information of the target resource repository, and the identification information of the target resource repository may be determined according to the information indicated by the execution result.

[0391] S1105c, the communication function unit of the terminal device establishes a user plane channel with the resource repository through the SMF and the UPF according to the DNN of the target resource repository.

[0392] In other words, the transceiver unit of the communication function unit of the terminal device establishes a PDU session with the resource repository through the SMF and the UPF according to the DNN of the target resource repository.

[0393] S1106a, the terminal OS of the terminal device establishes a connection with the target repository through the identifier of the target resource repository and requests resource information from the target repository.

[0394] S1106b, the target resource repository sends resource information to the terminal OS of the terminal device.

[0395] S1106c, the terminal OS continues to interact with the functional units in the terminal software domain and performs corresponding management tasks according to the resource information.

[0396] It should be understood that the management tasks may include: system initialization, software installation, update, deletion, configuration, control, and obtaining resources on the terminal.

[0397] Above, in combination with Figures 4 to 11 The management method provided by the embodiments of the present application has been described in detail. It can be understood that, in order to implement the above functions, it includes the corresponding hardware structure and / or software module for executing each function.

[0398] Those skilled in the art should be able to realize that, in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for a specific application, but such implementation should not be considered to exceed the scope of the present application.

[0399] Next, in combination with Figures 12 to 14 The management device provided by the embodiments of the present application will be described in detail. It should be understood that the description of the device embodiments corresponds to the description of the method embodiments. Therefore, for the content not described in detail, reference can be made to the above method embodiments. For the sake of brevity, some content will not be repeated.

[0400] Figure 12It is a schematic diagram of a management device provided by an embodiment of the present application. The device 1200 may include a processing unit 1220, and the processing unit 1220 is used for data processing. The device 1200 may further include a transceiver unit 1210. The transceiver unit 1210 may implement corresponding communication functions, and the transceiver unit 1210 may also be referred to as a communication interface or a communication unit or an interface unit. It should be understood that for operations such as sending and receiving involved in the present application, if there is no special description, or if it does not conflict with its actual role or internal logic in the relevant description, it can be more generally understood as operations such as output and input, rather than the sending and receiving operations directly performed by the radio frequency circuit and the antenna.

[0401] Optionally, the device 1200 may further include a storage unit, and the storage unit may be used for storing instructions and / or data. The processing unit 1220 may read the instructions and / or data in the storage unit so that the device implements the foregoing method embodiments.

[0402] The device 1200 may be used to perform the actions executed by the first management network element in the foregoing method embodiments. At this time, the device 1200 may be a communication device or a component configurable in a communication device. The transceiver unit 1210 is used to perform the transceiver-related operations on the communication device side in the foregoing method embodiments, and the processing unit 1220 is used to perform the processing-related operations of the first management network element in the foregoing method embodiments.

[0403] As a design, the device 1200 is used to perform the actions executed by the first management network element in the foregoing Figures 4 to 11 method embodiments shown. The execution entity may be a chip, a chip system or a processor that supports the first management network element to implement the corresponding method, or may also be a logic module or software that can implement all or part of the functions of the first management network element.

[0404] Specifically, the transceiver unit 1210 is used to obtain an interaction command, and the interaction command is used for managing the terminal device. Send the interaction command to the terminal device.

[0405] For details not described in detail, reference may be made to the foregoing method embodiments.

[0406] As a design, the management device 1200 is used to perform the actions executed by the terminal device in the foregoing Figures 4 to 11 method embodiments shown. The execution entity may be a chip, a chip system or a processor that supports the terminal device to implement the corresponding method, or may also be a logic module or software that can implement all or part of the functions of the terminal device.

[0407] It should be understood that if the management device 1200 is used to execute the actions performed by the terminal device, the management device 1200 may further include an interaction agent unit 1230, and the communication function unit includes a transceiver unit and an interaction agent unit.

[0408] Specifically, the communication function unit is configured to receive an interaction command from the first management network element. The processing unit 1220 is configured to execute the interaction command to obtain an execution result corresponding to the management operation.

[0409] For details not described in detail, reference may be made to the above method embodiments.

[0410] It should be understood that the specific processes for each unit to execute the above corresponding steps have been described in detail in the above method embodiments. For the sake of brevity, they will not be elaborated here.

[0411] In the above embodiments, the processing unit 1220 may be implemented by at least one processor or processor-related circuits. The transceiver unit 1210 may be implemented by a transceiver or transceiver-related circuits. The storage unit may be implemented by at least one memory.

[0412] Figure 13 It is a schematic structural diagram of a management device provided by an embodiment of the present application.

[0413] As Figure 13 shown, an embodiment of the present application further provides a management device 1300. The device 1300 includes a processor 1313. Optionally, the device further includes a memory 1320. The processor 1313 is coupled to the memory 1320. The memory 1320 is used to store computer program code or instructions and / or data. The processor 1313 is used to execute the computer program code or instructions and / or data stored in the memory 1320, so that the method in the above method embodiments is executed.

[0414] Optionally, the processor 1313 included in the device 1300 is one or more.

[0415] Optionally, as Figure 13 shown, the device 1300 may further include a memory 1320.

[0416] Optionally, the memory 1320 included in the device 1300 may be one or more.

[0417] Optionally, the memory 1320 may be integrated with the processor 1313 or separately provided.

[0418] Optionally, as Figure 13As shown, the device 1300 may further include a transceiver 1330 for receiving and / or transmitting signals. For example, the processor 1313 is used to control the transceiver 1330 to receive and / or transmit signals.

[0419] As a solution, the device 1300 is used to implement the operations performed by the first management network element, the second management network element, or the terminal device in the above method embodiments.

[0420] For example, the processor 1313 is used to implement the processing-related operations performed by the first management network element, the second management network element, or the terminal device in the above method embodiments, and the transceiver 1330 is used to implement the transceiver-related operations performed by the first management network element, the second management network element, or the terminal device in the above method embodiments.

[0421] Figure 14 is a schematic diagram of a chip system 1400 provided by an embodiment of the present application, as Figure 14 shown. The chip system 1400 (or may also be referred to as a processing system) includes a logic circuit 1410 and an input / output interface 1420. The logic circuit is used to be coupled to the input interface and transmit data parameters through the input / output interface to execute the method in the above method embodiments. The device installed with the chip system 1400 can implement the method and functions of the embodiments of the present application. For example, the logic circuit 1410 may be a processing circuit in the chip system 1400 to implement the control of the device installed with the chip system 1400, and may also be coupled to a storage unit to call instructions in the storage unit, so that the device can implement the method and functions of the embodiments of the present application. The input / output interface 1420 may be an input / output circuit in the chip system 1400 to output the information processed by the chip system 1400, or input the data or signaling information to be processed into the chip system 1400 for processing.

[0422] As a solution, the chip system 1400 is used to implement the operations performed by the management device (such as the first management network element, the second management network element, or the terminal device) in the above method embodiments.

[0423] For example, the logic circuit 1410 is used to implement the processing-related operations performed by the first management network element, the second management network element, or the terminal device in the above method embodiments, and the input / output interface 1420 is used to implement the transceiver-related operations performed by the first management network element, the second management network element, or the terminal device in the above method embodiments.

[0424] An embodiment of the present application further provides a communication system, which includes the first management network element, the second management network element, or the terminal device that implements the management method in the above method embodiments.

[0425] The embodiments of the present application further provide a computer-readable storage medium, on which computer instructions or program codes are stored for implementing the methods executed by the management device (such as the first management network element, the second management network element or the terminal device) in the above method embodiments.

[0426] For example, when the computer program is executed by a computer, the computer can implement the methods executed by the management device (such as the first management network element, the second management network element or the terminal device) in the above method embodiments.

[0427] The embodiments of the present application further provide a computer program product containing instructions, which when executed by a computer cause the computer to implement the methods executed by the management device (the first management network element, the second management network element or the terminal device) in the above method embodiments.

[0428] The embodiments of the present application further provide a management system, which includes at least one of a first management network element, a second management network element and a terminal device.

[0429] For the explanations and beneficial effects of the relevant content in any of the above provided devices, reference can be made to the corresponding method embodiments provided above, and details are not described herein again.

[0430] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0431] It should also be understood that the memories mentioned in the embodiments of the present application may be volatile memories and / or non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, the RAM can be used as an external cache. By way of example and not limitation, the RAM may include the following various forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0432] It should be noted that when the processor is a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, the memory (storage module) can be integrated in the processor.

[0433] It should also be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0434] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or by a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed the scope of the present application.

[0435] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and will not be elaborated herein.

[0436] In several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces. The indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.

[0437] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0438] In addition, in each embodiment of this application, the functional units can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit.

[0439] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in each embodiment of this application. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory ROM, random access memory RAM, magnetic disks, or optical discs that can store program codes.

[0440] As described above, the above is only the specific implementation manner of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed in this application can easily think of changes or substitutions, which should all be covered within the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

1. A management method, characterized in that, The method is applied to a first management network element and includes: Obtaining an interaction command for performing a management operation on a terminal device; Sending the interaction command to the terminal device.

2. The method according to claim 1, wherein The interaction command includes an operating system command and / or a management tool command.

3. The method according to claim 2, wherein The operating system command includes a command for managing the operating system of the terminal device, and the management tool command is a command for invoking a management tool software to execute a management function.

4. The method according to any one of claims 1 to 3, characterized in that The sending the interaction command to the terminal device includes: Sending the interaction command to the terminal device through non-access stratum signaling or user plane signaling.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Obtaining first indication information for indicating that the terminal device is configured with permission information for executing the interaction command; The obtaining the interaction command includes: Obtaining the interaction command according to the first indication information.

6. The method according to claim 5, characterized in that The first indication information is obtained according to second indication information for indicating that the terminal device has opened the execution permission of the interaction command.

7. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Obtaining second indication information for indicating that the terminal device has opened the execution permission of the interaction command; The obtaining the interaction command includes: Obtaining the interaction command according to the second indication information.

8. The method according to claim 5 or 6, characterized in that, The obtaining the first indication information includes receiving the first indication information from a second management network element; wherein the second management network element includes one of an access and mobility management function network element, a session management function network element, or a policy control function network element, and the first management network element includes a terminal remote management function.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: Obtaining an interaction command set from a template library, where the interaction command set includes the interaction command.

10. The method according to any one of claims 1 to 8, characterized in that, The obtaining the interaction command includes: Obtaining the interaction command from a network exposure function network element.

11. The method according to any one of claims 1 to 10, characterized in that, The obtaining the interaction command includes: Obtaining an interaction script from a script library, where the interaction script includes the interaction command; The sending the interaction command to the terminal device includes: Sending the interaction script to the terminal device.

12. The method according to any one of claims 1 to 11, characterized in that, The method further includes: Receiving an execution result of the terminal device for the interaction command; According to the execution result, obtaining identification information of a resource repository from the resource repository, where the resource repository includes at least one of a software image, a management tool, a component software package, an auxiliary tool, and a license file; Sending third indication information including the identification information to the terminal device.

13. A management method, characterized in that, The method is applied to a terminal device and includes: Receiving an interaction command from a first management network element; Executing the interaction command to obtain an execution result corresponding to the management operation.

14. The method according to claim 13, wherein The interaction command includes an operating system command and / or a management tool command.

15. The method according to claim 14, characterized in that, The operating system command includes a command for managing the operating system of the terminal device, and the management tool command is a command for invoking a management tool software to execute a management function.

16. The method according to any one of claims 13 to 15, characterized in that, The receiving the interaction command from a first management network element includes: Receiving the interaction command from the first management network element through non-access stratum signaling or user plane signaling.

17. The method according to any one of claims 13 to 16, characterized in that The method further includes: Send second indication information to a second management network element, where the second indication information is used to indicate that the terminal device has enabled the execution permission for the interaction command.

18. The method according to claim 17, wherein The sending the second indication information to the second management network element includes: When the status information of the debug switch is enabled, send the second indication information to the second management network element.

19. The method according to any one of claims 13 to 18, characterized in that, The receiving the interaction command from a first management network element includes: Receive an interaction script from the first management network element, where the interaction script includes the interaction command. The executing the interaction command to obtain an execution result includes: Execute the interaction script to obtain an execution result corresponding to the interaction script.

20. The method according to any one of claims 13 to 19, characterized in that, The method further includes: Send the execution result to the first management network element. Receive third indication information from the first management network element, where the third indication information includes identification information of a resource repository determined according to the execution result, and the resource repository includes at least one of a software image, a management tool, a component software package, an auxiliary tool, and a license file.

21. The method according to claim 20, wherein The method further includes: Obtain information in the resource repository according to the identification information. Execute corresponding management tasks according to the information in the resource repository.

22. A management device, characterized in that, The apparatus is located in a first management network element, and the apparatus includes a transceiver unit, where the transceiver unit is configured to: Obtain an interaction command, where the interaction command is used to perform a management operation on a terminal device. Send the interaction command to the terminal device.

23. The device according to claim 22, wherein The interaction command includes an operating system command and / or a management tool command.

24. The device according to claim 23, characterized in that, The operating system command includes a command for managing the operating system of the terminal device, and the management tool command is a command for invoking a management tool software to execute a management function.

25. The device according to any one of claims 22 to 24, characterized in that Specifically, the transceiver unit is configured to: Send the interaction command to the terminal device through non-access stratum signaling or user plane signaling.

26. The device according to any one of claims 22 to 25, characterized in that, The transceiver unit is further configured to: Obtain first indication information, where the first indication information is used to indicate that the terminal device is configured with permission information for executing the interaction command. Specifically, the transceiver unit is configured to: Obtain the interaction command according to the first indication information.

27. The device according to claim 26, characterized in that, The first indication information is obtained according to second indication information, where the second indication information is used to indicate that the terminal device has enabled the execution permission for the interaction command.

28. The device according to any one of claims 22 to 25, characterized in that The transceiver unit is further configured to: Obtain second indication information, where the second indication information is used to indicate that the terminal device has enabled the execution permission for the interaction command. Specifically, the transceiver unit is configured to: Obtain the interaction command according to the second indication information.

29. The device according to claim 26 or 27, characterized in that, Specifically, the transceiver unit is configured to receive the first indication information from a second management network element. Wherein, the second management network element includes one of an access and mobility management function network element, a session management function network element, or a policy control function network element, and the first management network element includes a terminal remote management function.

30. The device according to any one of claims 22 to 29, characterized in that The transceiver unit is further configured to: Obtain an interaction command set from a template library, where the interaction command set includes the interaction command.

31. The device according to any one of claims 22 to 29, characterized in that, Specifically, the transceiver unit is configured to: Obtain the interaction command from a network exposure function network element.

32. The device according to any one of claims 22 to 31, characterized in that, Specifically, the transceiver unit is configured to: Obtain an interaction script from a script library, where the interaction script includes the interaction command. Send the interaction script to the terminal device.

33. The device according to any one of claims 22 to 32, characterized in that, The transceiver unit is further configured to Obtain the identification information of the resource repository from the resource repository according to the execution result, where the resource repository includes at least one of software images, management tools, component software packages, auxiliary tools, and license files; Send third indication information to the terminal device, where the third indication information includes the identification information.

34. A management device, characterized in that, The device is located in the terminal device, and the device includes a communication function unit and a processing unit. The communication function unit is configured to receive an interaction command from a first management network element, where the interaction command is used to perform a management operation on the terminal device; The processing unit is configured to execute the interaction command to obtain an execution result corresponding to the management operation; The communication function unit is further configured to send the execution result to the first management network element.

35. The device according to claim 34, characterized in that, The interaction command includes an operating system command and / or a management tool command.

36. The device according to claim 35, characterized in that, The operating system command includes a command for managing the operating system of the terminal device, and the management tool command is a command for invoking a management tool software to execute a management function.

37. The device according to any one of claims 34 to 36, characterized in that, The communication function unit specifically includes a transceiver unit and an interaction proxy unit. The transceiver unit is specifically configured to receive the interaction command from the first management network element through non-access stratum signaling or user plane signaling; The interaction proxy unit is specifically configured to obtain the interaction command from the transceiver unit and send it to the operating system of the terminal device.

38. The device according to claim 37, wherein The interaction proxy unit is further configured to send second indication information to the transceiver unit, where the second indication information is used to indicate that the terminal device has opened the execution permission of the interaction command; The transceiver unit is further configured to send the second indication information to a second management network element.

39. The device according to claim 38, wherein The interaction proxy unit is specifically configured to Receive the second indication information from the operating system of the terminal device when the status information of the debugging switch is on.

40. The device according to any one of claims 34 to 39, characterized in that, The communication function unit specifically includes a transceiver unit and an interaction proxy unit. The transceiver unit is specifically configured to receive the interaction commands from the first management network element one by one; The interaction proxy unit is specifically configured to obtain the interaction command from the transceiver unit and send it to the operating system of the terminal device; The processing unit is specifically configured to: Execute the interaction command in the operating system of the terminal device to obtain the execution result.

41. The device according to any one of claims 34 to 39, characterized in that, The communication function unit specifically includes a transceiver unit and an interaction proxy unit. The transceiver unit is specifically configured to receive an interaction script from the first management network element, where the interaction script includes the interaction command; The interaction proxy unit is specifically configured to obtain the interaction script from the transceiver unit, execute the interaction script, and send the interaction command to the operating system of the terminal device; The processing unit is specifically configured to: Execute the interaction command in the operating system of the terminal device to obtain the execution result of the interaction script.

42. The device according to any one of claims 34 to 41, characterized in that, The communication function unit specifically includes a transceiver unit and an interaction proxy unit. The transceiver unit is specifically configured to receive third indication information from a first management network element, where the third indication information is used to indicate identification information of a resource repository determined according to the execution result, and the resource repository includes at least one of a software image, a management tool, a component software package, an auxiliary tool, and a license file; The interaction agent unit is specifically configured to obtain the third indication information from the transceiver unit and send it to the operating system of the terminal device.

43. The apparatus according to claim 42, wherein The transceiver unit is further specifically configured to obtain information in the resource repository according to the identification information; The interaction agent unit is specifically configured to obtain information in the resource repository from the transceiver unit and send it to the operating system of the terminal system; The processing unit is further configured to perform corresponding management tasks according to the information in the resource repository.

44. A management device, characterized in that, It includes a processor, the processor is coupled with a memory, the memory is used to store computer program code or instructions, and the processor is used to execute the computer program code or instructions in the memory, so that the apparatus executes the method described in any one of claims 1 to 12, or so that the apparatus is a unit of the method described in any one of claims 13 to 21.

45. A computer-readable storage medium, characterized in that, Computer program code or instructions are stored on the computer-readable storage medium, and when the computer program code or instructions run on a computer, the computer is caused to execute the method described in any one of claims 1 to 12, or the computer is caused to execute the method described in any one of claims 13 to 21.

46. A chip, characterized in that, The chip is coupled with the memory and is used to read and execute program instructions stored in the memory to implement the method described in any one of claims 1 to 12, or to implement the method described in any one of claims 13 to 21.

47. A management system, characterized in that, It includes at least one of a first management network element and a terminal device, the first management network element is used to execute the method described in any one of claims 1 to 12, and the terminal device is used to execute the method described in any one of claims 13 to 21.

Images