Management method and apparatus

Abstract

The present application provides a management method and apparatus. According to the management method, an interaction command is sent to a terminal device by means of a mobile network having capabilities such as long connection and control plane signaling, so that the function of the terminal device can be programmed and undergo other management operations by means of a corresponding command line in the interaction command, and thus the terminal device can realize flexible function changes and upgrades.

Description

Management method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on December 22, 2023, with application number 202311787495.2, and priority to the Chinese patent application with the invention name “Management Method and Device”, all contents of which are incorporated by reference into this application. Technical Field

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

[0003] The Third Generation Partnership Project (3 rd The 5G system, defined by the 3GPP (3rd Generation Partnership Project) and implemented and deployed by the industry, is essentially a wireless communication pipeline for most applications. Besides establishing communication channels and transmitting data with terminal devices through the air interface and the non-access stratum (NAS), network equipment has very limited control over the service application functions on terminal devices, such as IP multimedia subsystem (IMS) services. While network equipment can control these service application functions on terminal devices, it cannot manage and control the terminal device operating system and other application layer capabilities, preventing it from providing richer service applications.

[0004] In future mobile communication systems, beyond communication pipelines, network equipment and terminal devices may establish a higher level of collaboration. Therefore, remote and flexible functional changes and complex terminal software management for terminal devices of different types, uses, and operating systems are urgent challenges. Summary of the Invention

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

[0006] In a first aspect, a management method is provided, which is applied to a first management network element and includes: obtaining an interaction command, where the interaction command is used to perform a management operation on a terminal device; and sending the interaction command to the terminal device.

[0007] It should be understood that the first management network element is a network element that includes a terminal remote management function. The first management network element can be an independent newly added network element, or the first management network element can also be an existing network element that has newly added a terminal remote management function, for example, by assigning the terminal remote management function to an access management function network element, a session management function network element, a policy control function network element, etc.

[0008] In this technical solution, interactive commands are sent to terminal devices via a mobile network equipped with persistent connections and control plane signaling capabilities. These commands allow terminal device functions to be programmed and managed through corresponding command lines, enabling flexible functional changes and upgrades. Furthermore, terminal devices can be orchestrated with the network and cloud based on end-to-end service needs, more accurately and efficiently serving customer business goals. Ultimately, this reduces the complexity of installing, deploying, operating, maintaining, and managing terminal software, components, and tools, improving personnel efficiency and accelerating service rollout.

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

[0010] In combination with the first aspect, in some implementations 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 perform management functions.

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

[0012] In conjunction with the first aspect, in certain implementations of the first aspect, the method further includes: obtaining first indication information, the first indication information being used to indicate that the terminal device is configured with permission information for executing the interactive command. Obtaining the interactive command includes: obtaining the interactive command according to the first indication information.

[0013] In this way, the network side configures the terminal device with permission information for executing the interaction command to obtain the interaction command, thereby improving the flexibility of the first management network element on the network side in managing the terminal side.

[0014] In combination with the first aspect, in some implementations of the first aspect, the first indication information is obtained based on the second indication information, and the second indication information is used to indicate that the terminal device has enabled the execution permission of the interactive command.

[0015] In this way, obtaining the first indication information through the execution authority of the interactive command set on the terminal device side can improve the user's autonomy in performing subsequent management operations on the terminal device, thereby improving the user experience.

[0016] In conjunction with the first aspect, in certain 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 the 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.

[0017] In this way, an independent functional network element is set up on the network side for the process of obtaining interactive commands and managing terminal devices, which can be clearly distinguished from other current functional network elements, which is conducive to the subsequent management, functional expansion and continuous evolution of the independent functional network element.

[0018] In conjunction with the first aspect, in certain implementations of the first aspect, the method further includes: obtaining second indication information, the second indication information being used to indicate that the terminal device has enabled execution permission for the interactive command. Obtaining the interactive command includes: obtaining the interactive command according to the second indication information.

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

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

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

[0022] In this way, the complicated and diverse steps in the terminal device management operation are realized in the form of interactive commands in the interactive command set, so as to realize the interaction between the first management network element and the terminal device, thereby freeing up manpower, improving efficiency and supporting massive operations at the same time.

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

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

[0025] With reference to the first aspect, in certain implementations of the first aspect, obtaining the interaction command includes: obtaining the interaction command from a network open function network element.

[0026] Among them, the network open function network element includes the application program interface.

[0027] In this way, interactive commands are directly obtained through the application program interface of the network open function network element, and interaction with the terminal device is carried out, so that third-party manufacturers can directly perform real-time remote management and debugging of the terminal device, thereby realizing customized management of the terminal device.

[0028] In conjunction with the first aspect, in certain implementations of the first aspect, obtaining the interaction command includes: obtaining an interaction script from a script library, the interaction script including the interaction command. Sending the interaction command to the terminal device includes: sending the interaction script to the terminal device.

[0029] In this way, the complicated and diverse steps in the terminal device management operation are implemented in the form of interactive scripts to realize the interaction between the first management network element and the terminal device, thereby freeing up manpower, improving efficiency and supporting massive operations at the same time.

[0030] In some implementations, the interaction script is obtained and stored by the script library from a network open function network element, and the network open function network element includes an application program interface.

[0031] In this way, by configuring interactive scripts through the application program interface of the network open functional network element, third-party manufacturers (for example, terminal manufacturers, application manufacturers, etc.) can more conveniently customize and adapt specific terminal environments (for example, specific operating systems and / or terminal software components) and terminal management operations that need to be performed more reasonably, and can also be flexibly expanded, upgraded and changed according to subsequent industry developments.

[0032] In conjunction with the first aspect, in certain implementations of the first aspect, the method further includes: receiving an execution result of the interactive command from a terminal device; obtaining identification information of a resource repository from a resource repository based on the execution result, wherein 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; and sending third indication information to the terminal device, the third indication information including the identification information.

[0033] In this way, sending the resource warehouse's identification information to a terminal device can help subsequent terminal devices more conveniently and directly obtain the resource information needed for specific management operations from the resource warehouse. Furthermore, mobile networks feature a transmission pipeline that is always open once established. The resource warehouse within the network can prevent issues such as terminal devices being unable to properly address external networks or communicate properly with external servers, resulting in inefficient resource acquisition (slow transmission speeds), and vulnerability to attacks.

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

[0035] It should be understood that the management method of the second aspect corresponds to the management method of the first aspect, and the relevant beneficial effects can be referred to the first aspect, which will not be elaborated here.

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

[0037] In combination with the second aspect, in some implementations of the second aspect, the operating system command includes a command for managing the operating system of the terminal device, and a management tool command, which is a command for calling management tool software to perform management functions.

[0038] In combination with the second aspect, in some implementations of the second aspect, receiving the interaction command from the first management network element includes: receiving the interaction command from the first management network element through non-access layer signaling or user plane signaling.

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

[0040] In combination with the second aspect, in some implementations of the second aspect, sending the second indication information to the second management network element includes: when the switch state of the debugging switch is on, sending the second indication information to the second management network element.

[0041] In this way, the terminal device sends the second indication information through the state of the debugging switch, which can make the execution authority of the terminal device for the interactive command more intuitive, thereby improving the user experience.

[0042] In conjunction with the second aspect, in certain 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 an execution result corresponding to the interaction script.

[0043] In conjunction with the second aspect, in certain implementations of the second aspect, the method further includes: sending an execution result to the first management network element; and receiving third indication information from the first management network element, the third indication information including identification information of a resource repository determined based on the 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.

[0044] In conjunction with the second aspect, in certain implementations of the second aspect, the method further includes: acquiring information in a resource warehouse according to the identification information, and executing corresponding management tasks according to the information in the resource warehouse.

[0045] 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, the first indication information being used to indicate that the unified data management network element has configured permission information for executing an interactive command for a terminal device, the interactive command being used to perform a management operation on the terminal device; and outputting the first indication information to the first management network element.

[0046] In conjunction with the third aspect, in certain implementations of the third aspect, before determining the first indication information, the method further includes: receiving second indication information from the terminal device, the second indication information being used to indicate that the terminal device has enabled execution permission for interactive commands. Based on the second indication information, obtaining software management permission information from a unified data management network element, the software management permission information being used to indicate whether the unified data management network element has configured execution permission for interactive commands for the terminal device.

[0047] In combination with the third aspect, in certain 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 interactive command for the terminal device, then determining the first indication information.

[0048] In a fourth aspect, a management method is provided, which is applied to a second management network element, the method comprising: receiving second indication information from a terminal device, the second indication information being used to indicate that the terminal device has enabled execution permission for an interactive command, and outputting the second indication information to a first management network element.

[0049] In a fifth aspect, a management device is provided, the device being located in a first management network element and comprising a transceiver unit configured to: obtain an interactive command for performing management operations on a terminal device; and send the interactive command to the terminal device.

[0050] It should be understood that the management device of the fifth aspect corresponds to the management method of the first aspect, and the relevant beneficial effects can be referred to the first aspect, which will not be elaborated here.

[0051] In combination with the fifth aspect, in certain implementations of the fifth aspect, the interactive command includes an operating system command and / or a management tool command.

[0052] In combination with the fifth aspect, in certain implementations 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 management tool software to perform management functions.

[0053] In combination with the fifth aspect, in certain implementations of the fifth aspect, the transceiver unit is specifically used to send an interaction command to the terminal device through non-access layer signaling or user plane signaling.

[0054] In conjunction with the fifth aspect, in certain implementations 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 interactive command. The transceiver unit is specifically configured to obtain the interactive command based on the first indication information.

[0055] In combination with the fifth aspect, in certain implementations of the fifth aspect, the first indication information is obtained based on the second indication information, and the second indication information is used to indicate that the terminal device has opened the execution permission of the interactive command.

[0056] In conjunction with the fifth aspect, in certain implementations 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 the 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.

[0057] In conjunction with the fifth aspect, in certain implementations of the fifth aspect, the transceiver unit is further configured to obtain second indication information, where the second indication information is configured to indicate that the terminal device has enabled execution permission for the interactive command. The transceiver unit is specifically configured to obtain the interactive command based on the second indication information.

[0058] In some implementations, the transceiver unit is specifically configured to receive 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.

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

[0060] 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 open function network element.

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

[0062] In conjunction with the fifth aspect, in certain implementations of the fifth aspect, the transceiver unit is further configured to, based on the execution result, obtain 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; and transmit third indication information to the terminal device, where the third indication information includes the identification information.

[0063] In a sixth 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.

[0064] It should be understood that the management device of the sixth aspect corresponds to the management method of the second aspect, and the relevant beneficial effects can be referred to the second aspect, which will not be elaborated here.

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

[0066] In combination with the sixth aspect, in certain implementations of the sixth aspect, the operating system commands include commands for managing the operating system of the terminal device, and management tool commands, which are commands for calling management tool software to perform management functions.

[0067] In conjunction with the sixth aspect, in certain 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 the first management network element via 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 transmit it to an operating system of the terminal device.

[0068] In this way, the communication functional unit in the terminal device is further divided into a transceiver unit and an interaction proxy unit. The transceiver unit has the same function as the current terminal device's communication baseband and is responsible for information transmission. The interaction proxy unit is responsible for interaction between the terminal's operating system and the first functional network element. This division facilitates future functional evolution, upgrades, and changes to the two functional modules.

[0069] In conjunction with the sixth aspect, in certain implementations of the sixth aspect, the interaction proxy unit is further configured to send second indication information to the transceiver unit, where the second indication information is configured to indicate that the terminal device has enabled execution permission for the interaction command. The transceiver unit is further configured to send the second indication information to the second management network element.

[0070] In combination with the sixth aspect, in certain implementations of the sixth aspect, the interaction agent unit is specifically configured to receive second indication information from the operating system of the terminal device when the debugging switch is in the on state.

[0071] In conjunction with the sixth aspect, in certain 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 interaction commands from the first management network element one by one. The interaction proxy unit is specifically configured to obtain the interaction commands from the transceiver unit and transmit them to an 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.

[0072] In conjunction with the sixth aspect, in certain 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 script from the first management network element, where the interaction script includes an 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 an execution result of the interaction script.

[0073] In conjunction with the sixth aspect, in certain implementations 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 identification information of a resource repository determined based on 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. The interaction agent unit is specifically configured to obtain the third indication information from the transceiver unit and send it to an operating system of the terminal device.

[0074] In conjunction with the sixth aspect, in certain implementations of the sixth aspect, the transceiver unit is further configured to obtain information from the resource repository based on the identification information. The interaction agent unit is further configured to obtain the information from the resource repository from the transceiver unit and transmit it to the operating system of the terminal device. The processing unit is further configured to execute corresponding management tasks based on the information in the resource repository.

[0075] In a seventh aspect, a management device is provided, the device being located in a second management network element and comprising a transceiver unit and a processing unit. The processing unit is configured to determine first indication information, the first indication information being configured to indicate that the unified data management network element has configured permission information for executing an interactive command for a terminal device, the interactive command being 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.

[0076] In conjunction 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, the second indication information being used to indicate that the terminal device has enabled execution permission for interactive commands. Based on the second indication information, software management permission information is obtained from the unified data management network element, the software management permission information being used to indicate whether the unified data management network element has configured execution permission for interactive commands for the terminal device.

[0077] In combination with the seventh aspect, in certain implementations of the seventh aspect, the processing unit is specifically used 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 interactive command for the terminal device.

[0078] In an eighth aspect, a management device is provided, the device being located in a second management network element and comprising a transceiver unit. The method includes: the transceiver unit being configured to receive second indication information from a terminal device, the second indication information being configured to indicate that the terminal device has enabled execution permission for an interactive command; and outputting the second indication information to the first management network element.

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

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

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

[0082] In the tenth aspect, the present application provides a processor for executing the method provided by any one of the implementation methods of the first to fourth aspects above. In the process of executing these methods, the process of sending the above information and obtaining / receiving the above information in the above method can be understood as the process of the processor outputting the above information, and the process of the processor receiving the input above information. When outputting the above information, the processor outputs the above information to the interface and transmits it through the interface. After being output by the processor, the above information may also need to undergo other processing before reaching the interface. Similarly, when the processor receives the input above information, the interface obtains / receives the above information and inputs it into the processor. Furthermore, after the interface receives the above information, the above information may need to undergo other processing before being input into the processor.

[0083] For the operations involved, such as transmission, sending, and acquisition / reception, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be understood as output and reception, input and other operations, and can also be understood as transmission, sending and receiving operations performed by radio frequency circuits and antennas. This application does not limit this.

[0084] During implementation, the processor may be a processor specifically configured to execute the methods, or may be a processor that executes computer program code or instructions in a memory to execute the methods, such as a general-purpose processor. The memory may be a non-transitory memory, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or may be disposed on separate chips. The embodiments of the present application do not limit the type of memory or the configuration of the memory and the processor.

[0085] In the eleventh aspect, a computer-readable storage medium is provided, which stores program code or instructions for execution by a device, and the program code or instructions include a method for executing any one of the implementation methods of the first to fourth aspects above.

[0086] In a twelfth aspect, a computer program product comprising instructions is provided, which, when run on a computer, enables the computer to execute the method provided in any one of the implementations of the first to fourth aspects above.

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

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

[0089] In the fourteenth aspect, a management system is provided, comprising a first management network element, a second management network element and at least one of a terminal device, the first management network element being used to execute the method provided by any one of the implementation modes of the first aspect, and the terminal device being used to execute the method provided by any one of the implementation modes of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0090] FIG1 is a schematic diagram of a 3GPP system architecture of a 5G system provided in an embodiment of the present application;

[0091] FIG2 is a schematic diagram of a network architecture provided in an embodiment of the present application;

[0092] FIG3 is a schematic diagram of the architecture of a terminal device provided in an embodiment of the present application;

[0093] FIG4 is a flow chart of a management method provided in an embodiment of the present application;

[0094] FIG5 is a flow chart of another management method provided in an embodiment of the present application;

[0095] FIG6 is a flow chart of another management method provided in an embodiment of the present application;

[0096] FIG7 is a flow chart of another management method provided in an embodiment of the present application;

[0097] FIG8 is a flow chart of another management method provided in an embodiment of the present application;

[0098] FIG9 is a flow chart of another management method provided in an embodiment of the present application;

[0099] FIG10 is a flow chart of another management method provided in an embodiment of the present application;

[0100] FIG11 is a flow chart of another management method provided in an embodiment of the present application;

[0101] FIG12 is a schematic diagram of a management device provided in an embodiment of the present application;

[0102] FIG13 is a schematic structural diagram of a management device provided in an embodiment of the present application;

[0103] FIG14 is a schematic diagram of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0104] The technical solution in this application will be described below with reference to the accompanying drawings.

[0105] To facilitate understanding of the embodiments of the present application, the following points are explained:

[0106] First, in this application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments based on their internal logical relationships.

[0107] Second, in this application, "at least one" means one or more, and "more" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the text description of this application, the character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c. Wherein a, b and c can be single or multiple, respectively.

[0108] Third, in this application, the terms "first," "second," and various numerical references (e.g., #1, #2, etc.) are used to distinguish between different management network elements for ease of description and are not intended to limit the scope of the embodiments of this application. For example, they are used to distinguish between different management network elements, rather than to describe a specific order or precedence. It should be understood that the terms described in this manner are interchangeable where appropriate to describe solutions beyond the embodiments of this application.

[0109] Fourth, in this application, expressions such as "when," "under the circumstances of," and "if" all imply that a corresponding action will be taken under certain objective circumstances. They do not limit the timeframe, do not require a judgment action to be taken when the action is taken, and do not imply any other limitations. Furthermore, the judgment action following these conditional conjunctions does not imply that the judgment action following the conditional conjunctions is the only condition for achieving the result; additional conditions may also be included to achieve the result.

[0110] Fifth, in this application, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or are inherent to these processes, methods, products or apparatuses.

[0111] Sixth, in this application, "used to indicate" can include being used for direct indication and being used for indirect indication. When describing that a certain indication information is used to indicate A, it can include that the indication information directly indicates A or indirectly indicates A, and it does not mean that the indication information must carry A.

[0112] The indication methods involved in the embodiments of this application should be understood to encompass various methods that enable the party to be indicated to obtain information to be indicated. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. The transmission period and / or timing of these sub-information can be the same or different. This application does not limit the specific transmission method.

[0113] In the embodiments of the present application, the "indication information" may be an explicit indication, i.e., a direct indication via signaling, or may be obtained based on parameters indicated by the signaling, in combination with other rules, other parameters, or by deduction. It may also be an implicit indication, i.e., based on a rule or relationship, or based on other parameters, or by deduction. This application does not impose specific limitations on this.

[0114] Seventh, in this application, "protocol" may refer to a standard protocol in the field of communications, such as a 5G protocol, a new radio (NR) protocol, and related protocols used in future communication systems, and this application does not limit this. "Predefined" may include pre-definition. For example, protocol definition. "Preconfiguration" can be implemented by pre-saving corresponding codes, tables, or other methods that can be used to indicate relevant information in the device, and this application does not limit its specific implementation method.

[0115] Eighth, in this application, "storage" may refer to storage in one or more memories. The one or more memories may be provided separately or integrated into an encoder or decoder, a processor, or a communication device. The one or more memories may also be partially provided separately and partially integrated into a decoder, a processor, or a communication device. The type of memory may be any form of storage medium and is not limited in this application.

[0116] Figure 1 is a schematic diagram of the 3GPP system architecture of a 5G system provided in an embodiment of the present application. As shown in Figure 1, the network functions and entities currently included in the 3GPP architecture primarily include: user equipment (UE), (radio) access network (R)AN) equipment, data network (DN), and core network. The following describes each component involved in this communication system.

[0117] 1. User Equipment: A user equipment may also be called a terminal, an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user device. The terminal in the embodiments of the present application can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, an extended reality (XR) terminal (for example, a head-mounted display (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 a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a 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 device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal in a 5G network or a terminal in a future evolution network, etc.

[0118] Wearable devices, also known as wearable smart devices, are a general term for wearable devices that use wearable technology to intelligently design and develop wearable devices for daily wear, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include those that are fully functional, large in size, and can achieve full or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0119] 2. Access Network Equipment: Access network equipment, also known as access equipment, is a radio access network (R)AN. The (R)AN manages radio resources, provides access services to user devices, and forwards user device data between the user device and the core network. The (R)AN can also be understood as a base station in the network.

[0120] (R)AN can be a 3GPP-related cellular system, such as a 4G or 5G mobile communication system, or a future-oriented evolution system (for example, a 6G mobile communication system). (R)AN can also be an open access network (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 is a fusion of two or more of the above systems. (R)AN can also be called an (R)AN node, or other expressions, such as access network equipment. Unless otherwise specified in this application, access network equipment will be used for expression.

[0121] Exemplarily, the access network device in the embodiment of the present application may be any communication device with wireless transceiver functions for communicating with user equipment. The access network equipment includes, but is not limited to, evolved Node B (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 wireless fidelity (WiFi) system, wireless relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc. It can also be a next generation NodeB (gNB) or transmission point (TRP or TP) in 5G, such as NR system, one or a group of antenna panels (including multiple antenna panels) of a base station in 5G system, or a network node constituting a gNB or a transmission point, such as a baseband unit (BBU) or a distributed unit (DPU). unit, DU), etc. It can also be the next generation base station in the sixth generation mobile communication system, the base station in the future mobile communication system, etc. Optionally, the access network device can also be a wearable device, a vehicle or a vehicle-mounted device, etc. For example, the access network device in the vehicle to everything (V2X) technology can be a road side unit (RSU). It can be understood that all or part of the functions of the access network device in this application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform). The method performed by the access network device in this application can 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.

[0122] In some deployments, multiple access network devices collaborate to assist user equipment in achieving wireless access, with different access network devices implementing portions of the base station's functionality. For example, an access network device can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be separate devices or included in the same network element, such as a baseband unit (BBU). The radio unit RU can be included in a radio frequency device or radio unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). The CU implements portions of the access network device's functionality, while the DU implements portions of the access network device's functionality. For example, the CU is responsible for processing non-real-time protocols and services and implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, and realizing 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 eventually be encapsulated by the PHY layer of the DU to become PHY layer information, or converted from PHY layer information. Therefore, under this architecture, high-level signaling such as RRC layer signaling can also be considered to be sent by the DU, or by the DU+AAU. It can be understood that the access network device can be a device including one or more of the CU node, DU node, and AAU node. In addition, the CU can be divided into an access network device in the access network RAN, or the CU can be divided into an access network device in the core network (CN), and this application does not limit this.

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

[0124] 3. Data network DN: This is the operator network that provides data services to UEs, such as the Internet, third-party service networks, and IMS networks.

[0125] 4. Core Network: This refers to the equipment within the core network that provides service support for terminals. The core network performs three major functions: registration, connection, and session management. Currently, some examples of core network equipment include application network elements, network exposure network elements, policy control network elements, session management network elements, access management network elements, and user plane network elements. These network elements within the core network are described in detail below.

[0126] Application network element: In the 5G communication system, the 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.

[0127] Network open network element: In the long-term evolution (LTE) communication system, this network open network element can be a service capability exposure function (SCEF) network element. In the 5G communication system, this network open 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 the quality of application services. The 3GPP network can also securely obtain relevant data from third parties to enhance the network's intelligent decision-making. At the same time, this network function supports the recovery of structured data from a unified database or the storage of structured data in a unified database.

[0128] Session management network element: It is mainly used for session management, allocation and management of Internet protocol (IP) addresses for user equipment, selection of endpoints for manageable user plane functions, policy control and charging function interfaces, and downlink data notification. In LTE communication systems, the 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 that combines SGW-C and PGW-C. In 5G communication systems, the session management network element can be a session management function (SMF) network element, which completes terminal IP address allocation, UPF selection, and billing and QoS policy control.

[0129] 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) in addition to session management, such as legal monitoring and access authorization / authentication. In the LTE communication system, the access management network element may be an MME network element. In the 5G communication system, the access management network element may be an access and mobility management function (AMF), which mainly performs mobility management, access authentication / authorization and other functions. 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.

[0130] Policy control network element: This includes user subscription data management functions, policy control functions, charging policy control functions, and quality of service (QoS) control. It is used to guide the unified policy framework of network behavior and provide policy rule information to control plane function network elements (such as AMF and SMF network elements). In LTE communication systems, this policy control network element can be the policy control and charging function (PCRF). In 5G communication systems, this policy control network element can be the PCF network element.

[0131] User plane network element: Serves as the interface with the data network, performing functions such as user plane data forwarding, session / flow-level billing and statistics, and bandwidth limiting. This includes packet routing and forwarding, as well as quality of service (QoS) processing for user plane data. In LTE communication systems, this user plane network element can be the serving gateway user plane (SGW-U), the packet data network gateway user plane (PGW-U), or a combination of the SGW-U and PGW-U. In 5G communication systems, this user plane network element can be the user plane function (UPF) network element.

[0132] Authentication server function (AUSF) network element: Its main functions include user authentication and authorization.

[0133] Network slice selection function (NSSF) network element: Its main functions include the set of network slice instances serving the UE.

[0134] Unified data management (UDM) network element: Mainly used for UE subscription data management, including storage and management of UE identification, UE access authorization, etc.

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

[0136] It is understood that Figure 1 is only an example and does not limit the scope of protection of this application. The data transmission method provided in the embodiment of the present application may also involve network elements not shown in Figure 1. Of course, the data transmission method provided in the embodiment of the present application may also include only some of the network elements shown in Figure 1.

[0137] In addition, as shown in Figure 1, the figure shows the interaction relationship between network functional entities and the corresponding interfaces. For example, the UE and AMF can interact through the N1 interface (NAS). The interactions between other network functional entities are similar and will not be repeated here. Some interfaces can be implemented as service-oriented interfaces.

[0138] It should be understood that the UE, (R)AN, UPF, and DN in Figure 1 are generally referred to as user-layer network function entities. User data traffic can be transmitted through the protocol data unit session (PDU session) established between the UE and DN. The data transmission process passes through the (R)AN and UPF network entities. Other network entities can be referred to as control-layer network functions and entities, which are primarily responsible for functions such as authentication and authorization, registration management, session management, mobility management, and policy control, thereby ensuring reliable and stable transmission of user-layer traffic.

[0139] For most applications, the 5G system, implemented and deployed by the industry as defined by 3GPP, and the 5G-A system currently being defined by 3GPP, are essentially wireless communication pipes. Besides interacting with terminal devices through the air interface and NAS to establish communication pipes for data transmission, network equipment has very limited control over the service application functions on terminal devices, such as IP Multimedia Subsystem (IMS) service applications. While network equipment can control these service application functions on terminal devices, it cannot manage and control the terminal device operating system and other application layer capabilities, preventing it from providing richer service applications.

[0140] Other applications on the terminal device are installed by a third party on the terminal device and communicate with systems outside the network through wireless communication channels to realize business functions.

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

[0142] 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 to easily schedule and orchestrate containers. Containers are a lightweight, operating system-level virtualization technology that allows applications and their dependencies to run in resource isolation. All necessary components required to run an application are packaged as a single, reusable image. When the image runs, it runs in an isolated environment and does not share the host operating system's memory, central processing unit (CPU), or disk with other applications. This ensures that processes within the container do not affect any processes outside the container. Popular container technologies include Docker, Isula, etc.

[0143] 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. The complete installation and deployment of these containers and platforms, as well as other required software components (such as EdgeMesh, Istio, and Mosquitto), on specific operating systems may require different software tools, such as kubeadm, keadm, apt-get, apt, dpkg, yum, rpm, snap, and Python, which represent software packages, libraries, modules, and configuration files. These tools, combined with corresponding operating system commands or management tool commands, enable the installation, update, removal, and management of software image instances (containers) and other software packages and files. Table 1 provides examples of software images, software components, management tools, operating system commands, and management tool commands.

[0144] Table 1

[0145] Currently, third parties install software on terminal devices and communicate with external systems via wireless communication channels. This on-site deployment of edge devices is complex, demanding, time-consuming, and unable to meet the needs of massive applications. It suffers from the following shortcomings: First, containers, container clusters, cloud-native system architectures, edge-cloud collaborative system architectures, and tools involve numerous software systems, resulting in rapid technology and software version iterations and frequent updates. Second, the edge deployment environment is closely related to the terminal hardware devices, with varying configurations and numerous variables to consider. Third, most edge devices lack a user interface (UI) and require a separate connection to a host computer for configuration, resulting in numerous steps and a long on-site deployment process. Fourth, the current process relies primarily on manual operations (installation, configuration updates, and operation and maintenance), requiring extensive information technology (IT) knowledge, high requirements, and a long time. As the demand for edge deployment grows, manual operation is no longer sufficient for massive device deployment. Fifth, current IT system automation tools require manual personnel to establish network communication between the edge device and the central configuration server, and manual installation and boot software must be pre-deployed on the edge device. Due to the involvement of numerous software and hardware systems, a unified ecosystem cannot be formed. Only some steps can be completed automatically, and a large amount of manual real-time operations are still required.

[0146] Currently, in addition to third-party software installation on terminal devices, over-the-air (OTA) technology can also be used to achieve software upgrades and version updates at the edge of the device. OTA technology is primarily used for software upgrades and updates in smartphones and smart car systems. The essence of current OTA technology is that the cloud triggers the terminal device to download the software package, and the terminal device performs the software upgrade and update. 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's the aforementioned software management methods involving third-party software installation on terminal devices or over-the-air (OTA) technology for fixed operations like end-to-end software installation, authentication, and activation, these approaches often lack automation and are unable to implement complex software management. Currently, mobile communication networks, despite their vast topology and agile communication status awareness, essentially serve only as data transmission channels. This underutilizes the advantages of mobile communication networks, such as computing infrastructure, which can provide users with a better service experience and lower-cost, more efficient business applications.

[0148] Therefore, to address the above issues, the present application provides a management method and apparatus for terminal devices of different types, uses, and operating systems, which can remotely and flexibly perform function changes and complex terminal software management. This will be described in detail below with reference to Figures 2 to 14.

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

[0150] Figure 2 is a schematic diagram of a network architecture provided by an embodiment of the present application. As shown in Figure 2, 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. Not all functional network elements on the network device side are shown in Figure 2. For the specific functions of these functional network elements, please refer to the relevant description in Figure 1. In addition, the network device side of the embodiment of the present application may also include new functional network elements: terminal remote management function (TRMF) network element, template library, script library and resource repository.

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

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

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

[0155] It should be understood that the template library, script library and resource warehouse can also be independent network entities, and any one of the template library, script library and resource warehouse can also be combined with the current functional network element. The embodiments of this application do not limit the specific existence form of the template library, script library and resource warehouse.

[0156] The terminal device side includes an application layer and an operating system (OS) layer, wherein the application layer includes basic software, which may include container technology (Docker, containerd, iSula, etc.) installed on the terminal, platform or system (Kubernetes, KubeEdge, etc.) class, tool (kubeadm, keadm, apt, rpm, etc.) class, component (EdgeMesh, Istio, Mosquitto, etc.) class software and configuration. The operating system layer can also be called the terminal OS. The terminal device side also includes a communication function unit, which includes a transceiver unit and an interaction agent unit. The transceiver unit has a terminal communication protocol stack such as 3GPP, including a control plane and a user plane protocol stack. The interaction agent unit is used to proxy the interaction commands between the terminal OS in the network device side and the terminal device side, that is, the interaction agent unit can perform command line calls of the terminal OS, for example, input interaction command execution and obtain interaction command output. The terminal OS can run the interaction commands obtained from the interaction agent unit.

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

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

[0159] As shown in Figure 3(a), the functional unit of the interaction agent can be located in the terminal OS and can also be referred to as the OS interaction agent unit. The interaction command is transmitted to the OS interaction agent unit in the terminal OS via the transceiver unit in the communication functional unit, allowing the terminal OS to execute the interaction command and perform management operations on the terminal device. Accordingly, the results of the terminal OS's execution of the interaction command can be returned to the network device side via the OS interaction agent unit and the transceiver unit.

[0160] As shown in Figure 3(b), the functional unit of the interaction proxy can be located in the application layer and can also be referred to as an application layer interaction proxy unit. The interaction command is transmitted to the application layer interaction proxy unit in the application layer via the transceiver unit in the communication functional unit. The application layer interaction proxy unit communicates with the terminal OS to implement command line calls of the terminal OS, allowing the terminal OS to execute the interaction command and perform management operations on the terminal device. Accordingly, the results of the terminal OS's execution of the interaction command can be returned to the network device side via the application layer interaction proxy unit and the transceiver unit.

[0161] Figure 4 is a flow chart of a management method provided by an embodiment of the present application. It can be understood that the present application uses the terminal device and the network device as an example to illustrate the corresponding method as the execution subject of the interaction diagram, but the present application does not limit the execution subject of the interaction diagram. 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, please refer to Figure 3. The network device may include one or more 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 a terminal remote management function. The first management network element may be a newly added management function 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. In this case, 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 the existing functional network element, that is, the terminal remote management function TRMF is assigned to the existing functional network element. For example, the terminal remote management function TRMF is assigned to one of the functional network elements such as AMF, SMF, UDM, NEF or PCF. Specifically, if the second management network element is an AMF network element, the terminal remote management function TRMF is assigned 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, the terminal remote management function TRMF is assigned 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 assigned to one of the access management network element and the mobility management network element. The embodiment of the present application does not limit the specific form of the network element with the terminal remote management function in the future network.

[0164] S401: A first management network element obtains an interaction command, where the obtained interaction command is used for performing management operations on a terminal device.

[0165] It should be understood that the acquired interactive commands may belong to an interactive command set or an interactive script, wherein an interactive command set includes multiple interactive commands, and there is a corresponding execution order between the multiple interactive commands. An interactive script also includes multiple interactive commands and is a script, that is, a set of interactive commands in the form of a file or a complete message.

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

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

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

[0169] For example, in a Linux system, an interactive command set may include su-, sudo+command, and a series of operating system commands and / or management tool commands with specific management operations. The interactive command set may also include processing logic corresponding to the execution results fed back by the terminal device. The interactive command set may also include a first interaction type identifier. The first interaction type identifier is used to indicate that the interactive command set is used to interact with the terminal device. The first interaction type identifier may also include the effect of the interactive command set on the terminal device, such as installation, update, configuration, deletion, and other operations.

[0170] For example, in a Linux system, an interactive script may include interactive command sets such as su- and sudo+command, which include operating system commands and / or management tool commands. An interactive script is essentially an interactive command set in the form of a file or a whole message. An interactive script may also include a second interaction type identifier. This second interaction type identifier indicates that interaction with a terminal device is performed using an interactive script. The second interaction type identifier may also include the effect of the interactive script on the terminal device, such as installation, update, configuration, or deletion operations.

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

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

[0173] A specific pre-configuration method may be to configure the interactive command set to the template library through the application programming interface (API) of the network open function NEF network element by a third-party manufacturer (e.g., a terminal manufacturer), and the template library stores the interactive command set. Alternatively, the template library may be configured through other network elements, which is not limited in this application.

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

[0175] As a possible implementation manner, the first management network element directly obtains real-time interaction commands from the 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 via non-access layer signaling or user plane signaling.

[0178] It should be understood that the first management network element can send interaction commands directly to the terminal device, and can also send interaction commands to the terminal device through an intermediate functional network element. This application does not impose any restrictions on this.

[0179] It should be understood that the manner of sending the interaction command through the non-access layer signaling will be described in detail later in conjunction with Figures 5 to 7, and the manner of sending the interaction command through the user plane signaling will be described in detail in conjunction with Figures 8 to 10.

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

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

[0182] S403: The terminal device executes the interactive command to obtain an execution result corresponding to the management operation.

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

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

[0185] It should be understood that the specific unit modules of the terminal device in Figure 4 can refer to Figure 3. The specific unit modules in the terminal device are not described in detail here, and the subsequent detailed execution process will be described in detail in Figure 5.

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

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

[0188] Exemplarily, the description of the steps of sending interactive commands one by one, executing interactive 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 interactive command to the terminal device, the terminal device executes the first interactive command, obtains a first execution result corresponding to the first interactive command, and sends the first execution result to the first management network element. Subsequently, the first management network element sends a second interactive command to the terminal device, wherein the second interactive command can be determined according to the first execution result (for example, if the first interactive command is an uncertain command, the first execution result indicates an execution result of the first interactive command, then the second interactive command can be a subsequent interactive command corresponding to the first interactive result). The terminal device executes the second interactive command, obtains a second execution result corresponding to the second interactive command, and sends the second execution result to the first management network element. And so on, until the terminal device executes to the end position of the interactive command set.

[0189] Exemplarily, the description of the steps of sending multiple interactive commands at a time, executing multiple interactive commands at a time, and returning the execution results at a time in S402 to S404 can be that the first management network element sends multiple third interactive commands to the terminal device, the terminal device executes the multiple third interactive commands at a time, obtains the third execution results corresponding to the multiple third interactive commands, and then sends the third execution results to the first management network element. The subsequent steps are similar to the above-mentioned sending one by one and are not repeated here. It should be understood that the method of sending multiple interactive commands at a time so that the terminal device executes the multiple interactive commands may also require some auxiliary information. The embodiment of the present application does not limit the first management network element from sending additional auxiliary information.

[0190] In this technical solution, interactive commands are sent to terminal devices via a mobile network equipped with persistent connections and control plane signaling capabilities. These commands allow terminal device functions to be programmed and managed through corresponding command lines, enabling flexible functional changes and upgrades. Furthermore, terminal devices can be orchestrated with the network and cloud based on end-to-end user service needs to more accurately and efficiently serve user service goals. Ultimately, this reduces the complexity of installing, deploying, operating, maintaining, and managing terminal software, components, and tools, improving personnel efficiency and accelerating service rollout.

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

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

[0193] 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, but is not limited to, at least one of the terminal hardware model and version, operating system name and version, terminal hardware resources and status, DeepEdgePaaS resource settings reserved for the terminal side edge, and terminal identification.

[0194] As a possible implementation, the unified data management (UDM) network element configures permission information for executing interactive commands for the terminal device. The permission information for executing interactive commands may also be referred to as management operation permission information.

[0195] Specifically, the first management network element directly queries the UDM network element to determine whether the UDM network element has configured a permission for executing the interactive command for the terminal device, and then obtains the first indication information from the UDM network element.

[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 interactive commands.

[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, where the second indication information is used to indicate that the terminal device has enabled execution permission for the interactive 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 the interaction command.

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

[0202] In some implementations, the UDM network element configures permission information for executing interactive commands for all terminal devices. In this case, the first management network element does not need to obtain the first indication information and can directly obtain the interactive command according to the second indication information.

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

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

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

[0206] Optionally, in S409, the second management network element obtains 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 executing the interactive command for the terminal device, the second management network element sends first indication information to the first management network element.

[0209] If the unified data management (UDM) network element does not configure permission information for executing the interactive command for the terminal device, the second management network element sends instruction information to the first management network element not to execute the management operation on the terminal device.

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

[0211] 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] For example, management tools may include at least one of the following: software packages, libraries, modules, and configuration files such as kubeadm, keadm, apt-get, apt, dpkg, yum, rpm, snap, and Python, to enable installation, updating, deletion, and management of software image instances (containers) and other software packages and files. Component software packages may include other software that needs to be installed and deployed. Auxiliary tools may include transfer software packages or certification authority (CA) certificates.

[0213] Specifically, the first management network element performs a specific management task according to the execution result, for example, the management task may include system initialization, software installation, update, deletion, configuration, control, and acquisition of resources on the terminal.

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

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

[0216] Specifically, if the first management network element is a network element with an 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, the third indication information may be sent to the terminal device through non-access layer signaling. Alternatively, the third indication information may be sent to the terminal device through user plane signaling.

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

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

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

[0220] It should be understood that the detailed process from S410 to S413 will be described in detail in FIG. 11 .

[0221] The following, in conjunction with Figures 5 to 7 , details how a TRMF network element with a terminal remote management function sends a remote interaction command to a terminal device via non-access layer signaling, causing the terminal device to perform the management operation corresponding to the interaction command. To clearly illustrate the TRMF terminal remote management function, Figures 5 to 7 illustrate the first management network element as an independent TRMF network element.

[0222] Figure 5 is a flow chart of another management method provided by an embodiment of the present application. It can be understood that the present application uses the terminal device and the network device as an example to illustrate the corresponding method as the execution subject of the interaction diagram, but the present application does not limit the execution subject of the interaction diagram. 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, please refer to Figure 3. The network device may include functional network elements, for example, the AMF, TRMF, UDM, NEF and template library shown in Figure 5.

[0223] It should be understood that the AMF may be the second management network element in Figure 4, and the TRMF may be the first management network element in Figure 4. Alternatively, the functions of the TRMF may be implemented on the AMF, that is, the first management network element and the second management network element may be the same network element. In addition, the corresponding operations of the terminal device are described in detail using specific units in the terminal device in Figure 5.

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

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

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

[0227] Specifically, UDM obtains the terminal information of the terminal device from AMF, and 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 operation implemented on the terminal device.

[0229] It should be understood that UDM is the terminal device configuration management operation permission information, which can also be called the UDM contract information for configuring terminal management operations for the terminal device. For example, the contract information is used to indicate that the terminal device has a contract that can be controlled by remote interactive commands, or the contract information is used to indicate that the terminal device has a contract that can be installed and deployed by remote interactive commands, or the contract information is used to indicate that the terminal device can be contracted to run software services by remote interactive commands after the software is installed and deployed. This application does not limit the management operation type corresponding to the management operation permission information and the specific contract type indicated by the contract information.

[0230] S501c: The template library stores an interactive command set, where the interactive command set includes at least one interactive command.

[0231] It should be understood that a detailed explanation of the interactive command can be found in S401 and will not be repeated here.

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

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

[0234] Among them, NEF has an API interface, and terminal manufacturers can configure the interactive command set to the template library through the NEF API interface.

[0235] It should be understood that S501a, S501b, S501c, and S501d can all be referred to as the first pre-process, and these pre-processes are all optional steps. For example, the UDM can configure management operation permission information for all terminal devices, eliminating the need to configure it separately for each terminal device. In another example, the interaction command set can be pre-configured in the template library through other means. In another example, 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 state information of the debug switch, wherein the state information of the debug switch may indicate whether the debug switch is on or off.

[0237] Specifically, the terminal operating system of the terminal device receives a first operation instruction and determines the state information of the debug switch, where the first operation instruction may be to turn the debug switch on or off. Alternatively, the terminal operating system of the terminal device determines the state information of the debug switch by obtaining an initial state of the debug switch, where the initial state of the debug switch may be on or off.

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

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

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

[0241] S502c: The communication function unit sends 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, AMF requests the UDM for management operation permission information of the terminal device 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 permission information for executing interactive commands for the terminal device, 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 permission information for executing interactive commands for the terminal device, S503b is executed, and the AMF sends a first indication information to the TRMF, where the first indication information is used to indicate that the terminal device has configured permission information for executing interactive commands.

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

[0247] S504a: TRMF requests an interactive command set from the template library according to the first instruction information.

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

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

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

[0251] Specifically, the template library sends an interactive 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 interactive command set can be referred to S401, which will not be described in detail here. In addition, S504a and S504b are the first method for obtaining the interactive command.

[0253] S505a: If the NEF has an API interface, the TRMF requests an interactive command from the NEF according to the first instruction information.

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

[0255] Specifically, the NEF requests an interactive command from the third-party manufacturer through an API interface according to the first instruction 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 interactive command may be an interactive command corresponding to the type information of the management operation.

[0258] It should be understood that S505a and S505b are the second method for obtaining the interactive command. The embodiment of the present application does not limit whether the interactive command is obtained through the first or second method.

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

[0260] Exemplarily, the TRMF sends the 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 agent unit.

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

[0262] Exemplarily, the interaction agent unit sends a first interaction command to the terminal OS, the terminal OS receives the first interaction command from the interaction agent 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 interactive command to the communication function unit, and the communication function unit sends the execution result to the TRMF via 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 through NAS signaling.

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

[0266] Optionally, if the interactive command is obtained through interactive command acquisition method 2, S506d is executed, and the TRMF sends the first execution result to the third-party vendor via the NEF API. The third-party vendor then sends a second interactive command to the TRMF based on the first execution result. The TRMF continues to exchange commands with the terminal device through S506a to S506c. The third-party vendor continues to interact with the terminal device through the NEF API and TRMF until the third-party vendor indicates that the management operation is complete, that is, until the terminal device executes the last interactive command corresponding to the management operation.

[0267] FIG6 is a flowchart of another management method provided by an embodiment of the present application. It can be understood that the execution body of the flowchart of FIG6 is similar to that of FIG5. For detailed description, please refer to the relevant parts of FIG5 and will not be repeated here. For the logical module of the terminal device, please refer to FIG3. The network device may include functional network elements, for example, the AMF, TRMF, UDM, NEF and script library shown in FIG6.

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

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

[0270] It should be understood that S601a is similar to S501a, and S601b is similar to S501b, and detailed description thereof will be omitted here.

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

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

[0273] It should be understood that S601a, S601b, S601c and S601d can all be referred to as the second pre-process, and the pre-processes are also optional steps.

[0274] Steps S602a to S602c are similar to steps S502a to S502c. Please refer to the above description for details and will not be repeated here.

[0275] Steps S603a to S603b are similar to steps S503a to S503c. Please refer to the above description for details and will not be repeated here.

[0276] S604a: TRMF requests an interactive script from the script library according to the first instruction information.

[0277] S604b: The script library sends the interactive script to the TRMF, and the TRMF obtains the interactive script from the script library.

[0278] It should be understood that the detailed explanation of the interactive script can be referred to S401, which is not repeated here. The steps of S604a and S604b are similar to the steps of S504a and S504b, and the detailed explanation is not repeated here. In addition, S604a and S604b are the third method for obtaining the interactive command.

[0279] S605a: If the NEF has an API interface, the TRMF requests the NEF for an interactive script according to the first instruction information.

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

[0281] It should be understood that S605a and S605b are the fourth method for obtaining the interactive command. The present embodiment does not limit whether the interactive script is obtained through the third or fourth method. The steps of S605a and S605b are similar to the steps of S505a and S505b, and the detailed explanation is not repeated here.

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

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

[0284] S606b: The terminal device communication function unit executes the interactive script and sends the obtained interactive command to the terminal OS.

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

[0286] S606c: The terminal OS executes the interactive command, obtains an execution result, and sends the execution result to the communication function unit.

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

[0288] It should be understood that steps S606b and S606c may be that the interactive agent unit runs the interactive script and calls the interactive command line in the terminal OS, thereby realizing the interaction between the interactive agent unit and the terminal OS, and then obtaining the execution result of the interactive script.

[0289] Specifically, the interaction agent unit in the communication function unit determines the second interaction command based on the processing logic in the interaction script and continues to interact with the terminal OS through S606b and S606c to implement the command interaction. The interaction agent unit continues to interact 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 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 interactive script to the TRMF via NAS signaling.

[0291] Exemplarily, the interaction proxy 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 NAS signaling.

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

[0293] In one implementation, the implementation of Figure 5 can be used to perform management operations on some management tasks on the terminal device, and the implementation of Figure 6 can be used to perform management operations on other management tasks on the terminal device. Detailed description will be given in conjunction with Figure 7.

[0294] FIG7 is a flowchart of another management method provided by an embodiment of the present application. It can be understood that the execution body of the flowchart of FIG7 is similar to that of FIG5 . For detailed description, please refer to the relevant parts of FIG5 , which will not be repeated here. For the logical modules of the terminal device, please refer to FIG3 . The network device may include functional network elements, such as the AMF, TRMF, UDM, NEF, template library, and script library shown in FIG7 .

[0295] S701a, implement the first pre-process between the terminal device, AMF, UDM, template library and NEF.

[0296] It should be understood that the specific steps included in the first pre-process and the corresponding explanations can be found in FIG5 , which will not be described in detail here.

[0297] S701b, implement the second pre-process between the terminal device, AMF, UDM, script library and NEF.

[0298] It should be understood that the specific steps and corresponding explanations included in the second pre-process can be referred to Figure 6 and will not be repeated here. The repeated steps in the first pre-process and the second pre-process do not need to be repeated, and the steps in the first pre-process and the second pre-process terminals are optional steps.

[0299] S702, implement the step of obtaining the first indication information between the terminal device, AMF, TRMF and UDM.

[0300] It should be understood that the detailed steps of S702 can refer to steps S502a to S502c and steps S503a to S503b, and are not described in detail here.

[0301] S703a: Acquisition of interactive command sets is implemented between the TRMF and the template library.

[0302] Optionally, at S703b, a first interaction command is obtained between the TRMF and the NEF.

[0303] It should be understood that the specific steps included in S703a can refer to the steps included in the first acquisition method shown in FIG5 , and the specific steps included in S703b can refer to the steps included in the second acquisition method shown in FIG5 .

[0304] S704: The interactive process of interactive commands and execution results is implemented between the terminal device, TRMF and NEF through NAS signaling.

[0305] It should be understood that the specific steps included in S704 can refer to the specific steps S506a to S506d shown in Figure 5, and will not be repeated here. It should also be understood that if the interactive command set is obtained through interactive command acquisition method 1, S704 only needs to be implemented between the terminal device and the TRMF.

[0306] S705a: If the first execution result corresponding to the first interactive command indicates a determined management operation, the TRMF requests the NEF or the script library for a first interactive script corresponding to the determined management operation.

[0307] S705b: NEF or the script library sends the first interactive script to TRMF.

[0308] It should be understood that the first interaction command may be directly obtained from a third-party manufacturer through the NEF API interface in S704, or the first interaction command may be an interaction command in the interaction command set obtained from the template library in S704. The first interaction command is uncertain, for example, the first interaction command may be an interaction command with uncertainty, such as determining a command line or selecting a command line.

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

[0310] It should be understood that the embodiment of the present application does not limit the method for obtaining the first interaction script corresponding to the determined management operation. The first interaction script can be directly obtained from a script library (for specific steps, see SS604a and S604b in Figure 6). Alternatively, the first interaction script can be obtained from a third-party vendor through the NEF API interface (for specific steps, see SS605a and S605b in Figure 6).

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

[0312] It should be understood that the specific steps included in S706 can refer to the specific steps S606a to S606e shown in Figure 6, and will not be repeated here. It should also be understood that if the interactive script is obtained through the third interactive command acquisition method, S706 only needs to be implemented between the terminal device and the TRMF.

[0313] In the above technical solution, for management operations corresponding to uncertain interactive commands, the terminal OS can determine the subsequent execution branch after executing the interactive command. If the execution branch corresponding to the subsequent management operation is clear, the terminal device can be managed through the interactive script. This combines the high real-time feedback of interactive commands with the low interactive signaling of interactive scripts to reduce the latency of terminal device management.

[0314] The following, in conjunction with Figures 8 to 10, details how a network element with a terminal remote management function sends a remote interaction command to a terminal device via user plane signaling, causing the terminal device to execute the management operation corresponding to the interaction command. To clearly illustrate the terminal remote management function, Figures 8 to 10 also illustrate the first management network element as an independent TRMF network element.

[0315] FIG8 is a flowchart of another management method provided by an embodiment of the present application. It can be understood that the execution subject of the flowchart of FIG8 is similar to that of FIG5. For detailed description, please refer to the relevant parts of FIG5 and will not be repeated here. For the logical modules of the terminal device, please refer to FIG3. The network device may include functional network elements, such as the AMF, TRMF, UDM, NEF, SMF, UPF, and template library shown in FIG8.

[0316] S801, implement the first pre-process between the terminal device, AMF, UDM, template library and NEF.

[0317] It should be understood that the specific steps included in the first pre-process and the corresponding explanations can be found in FIG5 , which will not be described in detail here.

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

[0319] It should be understood that the detailed steps of S802 may refer to steps S502a to S502c and steps S503a to S503b, and are not described in detail here.

[0320] S803a: Acquisition of interactive command sets is implemented between TRMF and the template library.

[0321] Optionally, at S803b, obtaining a first interaction command is implemented between the TRMF and the NEF.

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

[0323] S804a, through NAS signaling, the TRMF sends fourth indication information to the communication function unit of the terminal device, where the fourth indication information is used to instruct the terminal device to establish a user plane connection with the TRMF.

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

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

[0326] 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 the network device side may include multiple TRMF network elements, and the current TRMF that performs the step of sending the fourth indication information to the AMF in S801 to S803a / S803b and S804a may be the same entity as the target TRMF or different entities. The current TRMF and the target TRMF shown in Figure 9 are the same entity.

[0328] S804b, the communication function unit of the terminal device establishes a user plane channel through the SMF and 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 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 physical IP address of the target TRMF by performing an address query (such as a domain name system (DNS) query) through 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-acquire the interaction command set in the network. For example, if the target TRMF that establishes a connection with the terminal does not query the interaction command set of the terminal device stored locally, then the target TRMF obtains the interaction command set of the terminal device by querying the terminal information within the network and obtaining the TRMF entity that stores the interaction command set of the terminal device. For another example, if the target TRMF that establishes a connection with the terminal does not query the interaction command set of the terminal device stored locally, then the target TRMF re-acquires the interaction command set or interaction command from the template library or NEF based on the type information of the management operation and / or the terminal information. The embodiment of the present application does not limit the manner in which the target TRMF re-acquires the interaction command.

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

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

[0336] S805c: The terminal OS outputs the execution result of the interactive command to the communication function unit, and the communication function unit sends the execution result to the TRMF through user plane signaling.

[0337] It should be understood that steps S805a to S805c are similar to steps S506a to S506c. The difference is that in steps S506a to S506c in FIG5 , the terminal device and the TRMF interact via NAS signaling, while in steps S805a to S805c in FIG8 , the terminal device and the TRMF interact via user plane signaling. Therefore, a detailed description of steps S805a to S805c is omitted here.

[0338] Optionally, if an interaction command is obtained through S803b, S805d is executed, and the TRMF sends a first execution result to the third-party vendor via the NEF API. The third-party vendor then sends a second interaction command to the TRMF based on the first execution result. The TRMF continues to exchange commands with the terminal device through S805a to S805c. The third-party vendor continues to interact with the terminal device through the NEF API and the TRMF until the third-party vendor indicates that the management operation is complete, that is, until the terminal device executes the last interaction command corresponding to the management operation.

[0339] FIG9 is a flowchart of another management method provided by an embodiment of the present application. It can be understood that the execution subject of the flowchart of FIG9 is similar to that of FIG5. For detailed description, please refer to the relevant parts of FIG5 and will not be repeated here. For the logical modules of the terminal device, please refer to FIG3. The network device may include functional network elements, such as the AMF, TRMF, UDM, NEF, SMF, UPF and script library shown in FIG9.

[0340] S901, implement the second pre-process between 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 found in FIG6 , which will not be described in detail here.

[0342] S902, implement the step of obtaining the first indication information between the terminal device, AMF, TRMF and UDM.

[0343] It should be understood that the detailed steps of S902 may refer to steps S502a to S502c and steps S503a to S503b, and are not described in detail here.

[0344] S903a: Acquisition of interactive scripts is implemented between TRMF and the script library.

[0345] Optionally, at S903b, obtaining an interaction script is implemented between the TRMF and the NEF.

[0346] It should be understood that the specific steps included in S903a can refer to the steps included in the third acquisition method shown in Figure 6, and the specific steps included in S903b can refer to the steps included in the fourth acquisition method shown in Figure 6.

[0347] Steps S904a to S904c are similar to steps S804a to S804c and are not described in detail here.

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

[0349] S905b, the terminal device communication function unit executes the interactive script and sends the obtained interactive command to the terminal OS.

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

[0351] S905d: The communication function unit sends the execution result of the interactive script to the TRMF through user plane signaling.

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

[0353] It should be understood that steps S905a to S905e are similar to steps S606a to S606e. The difference is that in steps S606a to S606e in Figure 6, the terminal device and the TRMF interact via NAS signaling, while in steps S905a to S905e in Figure 9, the terminal device and the TRMF interact via user plane signaling. Therefore, a detailed description of steps S905a to S905e is omitted here.

[0354] Similarly, similar to the information transmission via NAS signaling in Figures 5 to 7 , in one implementation, the implementation of Figure 8 can be used to perform management operations on a terminal device for some management tasks, and the implementation of Figure 9 can be used to perform management operations on a terminal device for other management tasks. This will be described in detail in conjunction with Figure 10 .

[0355] Figure 10 is a flowchart of another management method provided by an embodiment of the present application. It can be understood that the execution body of the flowchart of Figure 10 is similar to that of Figure 5. For detailed description, please refer to the relevant parts of Figure 5 and will not be repeated here. For the logical modules of the terminal device, please refer to Figure 3. The network device may include functional network elements, such as the AMF, TRMF, UDM, NEF, SMF, UPF, template library, and script library shown in Figure 10.

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

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

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

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

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

[0361] S1003a: Acquisition of interactive command sets is implemented between TRMF and the template library.

[0362] Optionally, at S1003b, obtaining a first interaction command is implemented between the TRMF and the NEF.

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

[0364] S1004: Establish a 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 may refer to steps S804a to S804c in FIG. 8 .

[0366] S1005: The interactive process of interactive commands and execution results is implemented between the terminal device, TRMF and NEF through user plane signaling.

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

[0368] S1006a: If the first execution result corresponding to the first interactive command indicates a determined management operation, the TRMF requests the NEF or the script library for a first interactive script corresponding to the determined management operation.

[0369] S1006b: NEF or the script library sends the first interactive script to TRMF.

[0370] It should be understood that the detailed processes of S1006a and S1006b can be referred to S705a and S705b, and will not be described in detail here.

[0371] S1007: The interactive script and execution result interaction process is implemented between the terminal device, TRMF and NEF through user plane signaling.

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

[0373] In the execution process of the interactive commands in Figures 5 to 10 above, if, in a specific management operation, the terminal device needs to obtain resource information from the network device side before completing the 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 is installed.

[0374] Figure 11 is a flow chart of another management method provided by an embodiment of the present application. It can be understood that the execution body of the flow chart of Figure 11 is similar to that of Figure 5. For detailed description, please refer to the relevant parts of Figure 5, which will not be repeated here. For the logical modules of the terminal device, please refer to Figure 3. The network device may include functional network elements, for example, the AMF, TRMF, UDM, NEF, SMF, UPF, template library, resource warehouse and script library shown in Figure 10.

[0375] It should be understood that for the resource information that may be included in the resource warehouse, reference may be made to the above description of the resource warehouse, which will not be elaborated here.

[0376] For S1101a and S1101b, reference may be made to the first configuration process in FIG5 and the second configuration process in FIG6 , which are not described in detail here.

[0377] S1101c, NEF configures resource information to the resource warehouse. S1101d, the resource warehouse stores the resource information.

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

[0379] It should be understood that S1101c and S1101d may also be optional steps, and resource information may also be configured in the resource warehouse in other ways, which is not limited in this embodiment of the present application.

[0380] For the specific steps of S1102, S1103a and S1103b, reference may be made to the relevant steps of FIG5 to FIG10, which will not be described in detail here.

[0381] For the relevant steps of S1104a, reference may be made to the relevant steps of FIG. 5 and FIG. 6 , and for the relevant steps of S1104b, reference may be made to the relevant steps of FIG. 8 and FIG. 9 , which will not be described in detail here.

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

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

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

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

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

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

[0388] Alternatively, TRMF can directly encapsulate the third indication information in NAS signaling, TRMF sends the NAS signaling to AMF, and 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 warehouses, and different resource warehouses may include different resource information.

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

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

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

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

[0394] S1106b: The target resource warehouse sends resource information to the terminal OS of the terminal device.

[0395] S1106c: The terminal OS continues to interact with the functional units of the terminal software domain and executes corresponding management tasks according to the resource information.

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

[0397] The management method provided by the embodiment of the present application is described in detail above with reference to Figures 4 to 11. It is understandable that, in order to implement the above functions, it includes hardware structures and / or software modules corresponding to the execution of each function.

[0398] Those skilled in the art should be aware that, in combination with the units and algorithm steps of each example 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 function is performed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for specific applications, but such implementation should not be considered to be beyond the scope of this application.

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

[0400] Figure 12 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, which is used to perform data processing. The device 1200 may also include a transceiver unit 1210, which may implement corresponding communication functions. 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 the operations such as sending and receiving involved in this application, if there is no special explanation, or if it does not conflict with its actual function or internal logic in the relevant description, it can be more generally understood as operations such as output and input, rather than sending and receiving operations directly performed by the radio frequency circuit and antenna.

[0401] Optionally, the device 1200 may further include a storage unit, which may be used to store 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 aforementioned method embodiment.

[0402] The device 1200 can be used to execute the actions performed by the first management network element in the above method embodiment. In this case, the device 1200 can be a communication device or a component that can be configured on a communication device. The transceiver unit 1210 is used to execute the transceiver-related operations on the communication device side in the above method embodiment, and the processing unit 1220 is used to execute the processing-related operations of the first management network element in the above method embodiment.

[0403] As a design, the apparatus 1200 is configured to execute the actions performed by the first management network element in the method embodiments shown in Figures 4 to 11 above. The execution entity may be a chip, chip system, or processor that supports the first management network element in implementing the corresponding method, or 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 configured to obtain an interaction command, where the interaction command is used to perform management operations on the terminal device, and send the interaction command to the terminal device.

[0405] For details not described in detail, please refer to the above method embodiment.

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

[0407] It should be understood that if the management device 1200 is used to execute the actions executed by the terminal device, the management device 1200 may also 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, please refer to the above method embodiment.

[0410] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0411] The processing unit 1220 in the above embodiment 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] FIG13 is a schematic structural diagram of a management device provided in an embodiment of the present application.

[0413] As shown in Figure 13, an embodiment of the present application further provides a management device 1300. Device 1300 includes a processor 1313. Optionally, the device also includes a memory 1320. Processor 1313 is coupled to memory 1320. Memory 1320 is configured to store computer program code, instructions, and / or data. Processor 1313 is configured to execute the computer program code, instructions, and / or data stored in memory 1320, thereby executing the method described in the above method embodiment.

[0414] Optionally, the device 1300 includes one or more processors 1313.

[0415] Optionally, as shown in FIG13 , 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 provided separately.

[0418] Optionally, as shown in Figure 13, the apparatus 1300 may further include a transceiver 1330, which is configured to receive and / or transmit signals. For example, the processor 1313 is configured to control the transceiver 1330 to receive and / or transmit signals.

[0419] As a solution, the apparatus 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 embodiment.

[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 embodiment, and the transceiver 1330 is used to implement the sending and receiving-related operations performed by the first management network element, the second management network element or the terminal device in the above method embodiment.

[0421] FIG14 is a schematic diagram of a chip system 1400 provided in an embodiment of the present application, as shown in FIG14 . The chip system 1400 (or it 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 couple with the input interface and transmit data parameters through the input / output interface to execute the method in the above method embodiment. The device in which the chip system 1400 is installed can implement the method and function of the embodiment of the present application. For example, the logic circuit 1410 can be a processing circuit in the chip system 1400, which controls the device in which the chip system 1400 is installed. It can also be coupled to a storage unit and call instructions in the storage unit so that the device can implement the method and function of the embodiment of the present application. The input / output interface 1420 can be an input / output circuit in the chip system 1400, which outputs information processed by the chip system 1400, or inputs 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 embodiment.

[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 embodiment, and the input / output interface 1420 is used to implement the sending and receiving-related operations performed by the first management network element, the second management network element or the terminal device in the above method embodiment.

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

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

[0426] For example, when the computer program is executed by a computer, the computer can implement the method 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 embodiment.

[0427] An embodiment of the present application also provides a computer program product comprising instructions, which, when executed by a computer, enables the computer to implement the method performed by the management device (first management network element, second management network element or terminal device) in the above method embodiment.

[0428] An embodiment of the present application also provides a management system, which includes at least one of a first management network element, a second management network element, and a terminal device.

[0429] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.

[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 be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

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

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

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

[0434] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0435] Those skilled in the art will 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 aforementioned method embodiments and will not be repeated here.

[0436] In the 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 schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as 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 mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

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

[0439] If the functions are implemented in the form of software functional 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 the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory ROM, a random access memory RAM, a magnetic disk, or an optical disk.

[0440] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A management method, characterized in that: The method is applied to a first management network element, comprising: Obtaining an interactive command, where the interactive command is used to perform management operations on the terminal device; The interactive command is sent to the terminal device.

2. The method according to claim 1, characterized in that The interactive commands include operating system commands and / or management tool commands.

3. The method according to claim 2, 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 calling management tool software to execute management functions.

4. The method according to any one of claims 1 to 3, characterized in that The sending the interactive command to the terminal device includes: The interaction command is sent to the terminal device via non-access layer signaling or user plane signaling.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: Acquire first indication information, where the first indication information is used to indicate that the terminal device is configured with permission information for executing the interactive command; The obtaining of the interactive command comprises: The interaction command is acquired according to the first indication information.

6. The method according to claim 5, characterized in that The first indication information is obtained based on the second indication information, and the second indication information is used to indicate that the terminal device has enabled the execution permission of the interactive command.

7. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: Acquire second indication information, where the second indication information is used to indicate that the terminal device has enabled the execution permission of the interactive command; The obtaining of the interactive command comprises: The interaction command is acquired according to the second indication information.

8. The method according to claim 5 or 6, characterized in that: The obtaining of the first indication information comprises: receiving the first 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.

9. The method according to any one of claims 1 to 8, characterized in that: The method further comprises: An interaction command set is acquired from a template library, wherein 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 of the interactive command comprises: The interaction command is obtained from a network open function network element.

11. The method according to any one of claims 1 to 10, characterized in that: The obtaining of the interactive command comprises: Acquire an interactive script from a script library, wherein the interactive script includes the interactive command; The sending the interactive command to the terminal device includes: The interactive script is sent to the terminal device.

12. The method according to any one of claims 1 to 11, characterized in that: The method further comprises: Receiving an execution result of the interactive command from the terminal device; According to the execution result, obtaining identification information of the resource warehouse from the resource warehouse, wherein the resource warehouse 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.

13. A management method, characterized in that: The method is applied to a terminal device, comprising: receiving an interaction command from the first management network element; Execute the interactive command to obtain an execution result corresponding to the management operation.

14. The method according to claim 13, characterized in that The interactive commands include operating system commands and / or management tool commands.

15. The method according to claim 14, characterized in that The operating system commands include commands for managing the operating system of the terminal device, and the management tool commands are commands for calling management tool software to execute management functions.

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

17. The method according to any one of claims 13 to 16, characterized in that The method further comprises: Sending second indication information to the second management network element, where the second indication information is used to indicate that the terminal device has opened the execution permission of the interactive command.

18. The method according to claim 17, characterized in that The sending the second indication information to the second management network element includes: When the state information of the debugging switch is on, the second indication information is sent 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 the first management network element includes: receiving an interaction script from the first management network element, wherein the interaction script includes the interaction command; The executing the interactive command to obtain the execution result includes: Execute the interactive script to obtain an execution result corresponding to the interactive script.

20. The method according to any one of claims 13 to 19, characterized in that The method further comprises: Sending the execution result to the first management network element; Receive third indication information from the first management network element, the third indication information including identification information of a resource warehouse determined according to the execution result, the resource warehouse including 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, characterized in that The method further comprises: According to the identification information, obtaining information in the resource warehouse; Execute corresponding management tasks according to the information in the resource warehouse.

22. A management device, characterized in that: The device is located in a first management network element, and includes a transceiver unit, and the transceiver unit is used to: Obtaining an interactive command, where the interactive command is used to perform management operations on the terminal device; The interactive command is sent to the terminal device.

23. The device according to claim 22, characterized in that The interactive commands include operating system commands and / or management tool commands.

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 calling management tool software to execute management functions.

25. The device according to any one of claims 22 to 24, characterized in that The transceiver unit is specifically used for: The interaction command is sent to the terminal device via non-access layer signaling or user plane signaling.

26. The device according to any one of claims 22 to 25, characterized in that The transceiver unit is also used for: Acquire first indication information, where the first indication information is used to indicate that the terminal device is configured with permission information for executing the interactive command; The transceiver unit is specifically used for: The interaction command is acquired according to the first indication information.

27. The device according to claim 26, characterized in that The first indication information is obtained based on the second indication information, and the second indication information is used to indicate that the terminal device has enabled the execution permission of the interactive command.

28. The device according to any one of claims 22 to 25, characterized in that The transceiver unit is also used for: Acquire second indication information, where the second indication information is used to indicate that the terminal device has enabled the execution permission of the interactive command; The transceiver unit is specifically used for: The interaction command is acquired according to the second indication information.

29. The device according to claim 26 or 27, characterized in that The transceiver unit is specifically configured to receive the first 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.

30. The device according to any one of claims 22 to 29, characterized in that The transceiver unit is also used for: An interaction command set is acquired from a template library, wherein the interaction command set includes the interaction command.

31. The device according to any one of claims 22 to 29, characterized in that The transceiver unit is specifically used for: The interaction command is obtained from a network open function network element.

32. The device according to any one of claims 22 to 31, characterized in that The transceiver unit is specifically used for: Acquire an interactive script from a script library, wherein the interactive script includes the interactive command; The interactive script is sent to the terminal device.

33. The device according to any one of claims 22 to 32, characterized in that The transceiver unit is also used for: According to the execution result, obtaining identification information of the resource warehouse from the resource warehouse, wherein the resource warehouse 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.

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

35. The device according to claim 34, characterized in that The interactive commands include operating system commands and / or management tool commands.

36. The device according to claim 35, characterized in that The operating system commands include commands for managing the operating system of the terminal device, and the management tool commands are commands for calling management tool software to execute management functions.

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 agent unit. The transceiver unit is specifically configured to receive the interaction command from the first management network element through non-access layer signaling or user plane signaling; The interaction proxy unit is specifically configured to obtain the interaction command from the transceiver unit and send the command to the operating system of the terminal device.

38. The device according to claim 37, characterized in that The interaction proxy unit is further used 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 used to send the second indication information to the second management network element.

39. The device according to claim 38, characterized in that The interaction agent unit is specifically used for: When the state information of the debugging switch is on, the second indication information is received from the operating system of the terminal device.

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 agent 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 used 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 used for: The interactive command is executed 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 agent 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 used 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 used for: The interactive command is executed in the operating system of the terminal device to obtain the execution result of the interactive 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 agent unit. The transceiver unit is specifically used to receive third indication information from the first management network element, where the third indication information is used to indicate identification information of a resource warehouse determined according to the execution result, where the resource warehouse 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 used to obtain the third indication information from the transceiver unit and send the third indication information to the operating system of the terminal device.

43. The device according to claim 42, characterized in that The transceiver unit is further specifically configured to obtain information in the resource warehouse according to the identification information; The interaction agent unit is specifically used to obtain the information in the resource warehouse from the transceiver unit and send it to the operating system of the terminal device; The processing unit is also used to execute corresponding management tasks according to the information in the resource warehouse.

44. A management device, characterized in that: The device comprises a processor coupled to a memory, the memory being used to store computer program codes or instructions, the processor being used to execute the computer program codes or instructions in the memory, so that the device performs the method as claimed in any one of claims 1 to 12, or the device is a unit of the method as claimed in any one of claims 13 to 21.

45. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer program code or instructions, which, when executed on a computer, enable the computer to execute the method as claimed in any one of claims 1 to 12, or enable the computer to execute the method as claimed in any one of claims 13 to 21.

46. ​​A chip, characterized in that: The chip is coupled to a memory and is used to read and execute program instructions stored in the memory to implement the method as claimed in any one of claims 1 to 12, or to implement the method as claimed 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, wherein the first management network element is used to execute the method as described in any one of claims 1 to 12, and the terminal device is used to execute the method as described in any one of claims 13 to 21.

Images