CN114443261A - Terminal task shunting method and device - Google Patents

Terminal task shunting method and device Download PDF

Info

Publication number
CN114443261A
CN114443261A CN202011204900.XA CN202011204900A CN114443261A CN 114443261 A CN114443261 A CN 114443261A CN 202011204900 A CN202011204900 A CN 202011204900A CN 114443261 A CN114443261 A CN 114443261A
Authority
CN
China
Prior art keywords
task
terminal
executed
resource
parameter
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202011204900.XA
Other languages
Chinese (zh)
Inventor
肖晓丽
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China United Network Communications Group Co Ltd
Original Assignee
China United Network Communications Group Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China United Network Communications Group Co Ltd filed Critical China United Network Communications Group Co Ltd
Priority to CN202011204900.XA priority Critical patent/CN114443261A/en
Publication of CN114443261A publication Critical patent/CN114443261A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
    • G06F9/5016—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals the resource being the memory
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
    • H04W28/0236—Traffic management, e.g. flow control or congestion control based on communication conditions radio quality, e.g. interference, losses or delay

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The application provides a terminal task shunting method and device, relates to the technical field of communication, and can realize shunting of terminal tasks so that the terminal can better process the tasks. The method comprises the following steps: the terminal responds to the task execution instruction and determines a first parameter of the task to be executed. The first parameter comprises a first hardware resource, a first network resource and a task type of the task to be executed, wherein the first hardware resource and the first network resource are required by the task to be executed. Then, the terminal obtains a second parameter, wherein the second parameter comprises: a second network resource between the terminal and the base station, a second hardware resource of the terminal, wherein the base station is corresponding to the terminal. And finally, the terminal determines whether to execute the task to be executed locally on the terminal according to the first parameter and the second parameter.

Description

Terminal task shunting method and device
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for offloading a terminal task.
Background
With the development of mobile internet and the popularization of intelligent terminals, some complex applications, such as applications based on Augmented Reality (AR) technology or Virtual Reality (VR) technology, have appeared.
The advent of complex applications based on AR technology or VR technology, etc. has improved user experience. However, the computing power and resources of the terminal are limited, and other fixed applications are also running inside the terminal. This results in that when the terminal executes the tasks of the complex applications, the terminal cannot not only process the tasks of the complex applications well, but also affects the processing of the terminal on the tasks of other applications.
Disclosure of Invention
The application provides a terminal task shunting method and device, which can realize shunting of a terminal task and enable the terminal to better process the task.
In order to achieve the purpose, the technical scheme is as follows:
in a first aspect, the present application provides a method for splitting a task of a terminal, where the method may be applied to the terminal, and includes: the terminal responds to the task execution instruction and determines a first parameter of the task to be executed. The first parameter comprises a first hardware resource, a first network resource and a task type of the task to be executed, wherein the first hardware resource and the first network resource are required by the task to be executed. Then, the terminal obtains a second parameter, wherein the second parameter comprises: a second network resource between the terminal and the base station, a second hardware resource of the terminal, wherein the base station is corresponding to the terminal. And finally, the terminal determines whether to execute the task to be executed locally on the terminal according to the first parameter and the second parameter.
The first parameter of the task to be executed can be determined, and the first parameter comprises a first hardware resource and a first network resource required by executing the task to be executed. Therefore, the first parameter may reflect the resources consumed by executing the theory of the task to be performed. The second parameter acquired by the terminal can reflect the remaining amount of the local resource of the terminal. Therefore, whether to execute the task to be executed locally at the terminal can be determined by combining the first parameter and the second parameter. In addition, the first parameter also comprises the task type of the task to be executed, and certain specific tasks can be determined to be executed locally in the terminal.
In summary, the terminal task offloading method provided by the present application determines whether to execute the task to be executed locally at the terminal by analyzing the theoretical resource consumption situation of the task to be executed and the remaining situation of the local resource of the terminal, so as to implement offloading of the terminal task, and execute only a part of tasks at the terminal, so as to ensure that the terminal can better process the service.
Optionally, in a possible design, the "first hardware resource" may include a first CPU resource and a first memory resource, and the "second hardware resource" may include a second CPU resource and a second memory resource. Correspondingly, the "determining whether to execute the task to be executed on the terminal according to the first parameter and the second parameter" includes:
when the percentage of the first CPU resource in the second CPU resource is larger than or equal to a first threshold value, or the percentage of the first memory resource in the second memory resource is larger than or equal to a second threshold value, determining that a task to be executed is executed at the terminal; and when the percentage of the first CPU resource in the second CPU resource is smaller than a first threshold value and the percentage of the first memory resource in the second memory resource is smaller than a second threshold value, determining that the task to be executed is a target task.
Optionally, in a possible design, the "first network resource" may include a first latency and a first network bandwidth, and the "second network resource" may include a second latency and a second network bandwidth. Correspondingly, the "determining whether to execute the task to be executed at the terminal according to the first parameter and the second parameter" may include:
when the first time delay is less than or equal to the second time delay or the first network bandwidth is greater than or equal to the second network bandwidth, determining that a task to be executed is executed at the terminal; and when the first time delay is greater than the second time delay and the first network bandwidth is less than the second network bandwidth, determining that the task to be executed is the target task.
Optionally, in a possible design, the "first network resource" may further include a radio link quality parameter. Correspondingly, after the "task to be executed is determined to be the target task", the terminal task offloading method provided by the present application may further include: the terminal acquires a third hardware resource of the MEC server corresponding to the terminal; when the quality parameter of the wireless link meets a first preset condition, the third hardware resource meets a second preset condition and the task type is not a target type, the terminal determines to execute a task to be executed on the MEC server; and when the wireless link quality parameter does not meet the first preset condition, or the third hardware resource does not meet the second preset condition, or the task type is the target type, the terminal determines to execute the task to be executed locally on the terminal. The third hardware resource may include a third CPU resource and a third memory resource.
Optionally, in a possible design manner, after the "determining that the MEC server executes the task to be executed", the terminal task offloading method provided by the present application may further include: the method comprises the steps that a terminal obtains execution parameters of an MEC server for executing a task to be executed; and when the execution parameter meets a third preset condition, the terminal determines to execute the task to be executed again locally on the terminal.
In a second aspect, the present application provides a terminal task offloading device, including a determining module and an obtaining module. The determining module is used for responding to the task execution instruction and determining a first parameter of the task to be executed. The first parameter comprises a first hardware resource required for executing the task to be executed, a first network resource and a task type of the task to be executed. And the acquisition module is used for acquiring the second parameter. The second parameters include: a second network resource between the terminal and the base station, a second hardware resource of the terminal. The base station corresponds to the terminal. The determining module is further configured to determine whether to execute the task to be executed at the terminal according to the first parameter determined by the determining module and the second parameter acquired by the acquiring module.
In a third aspect, the present application provides a terminal task offloading device, including a processor, where the processor is configured to be coupled with a memory, read and execute an instruction in the memory, so as to implement the terminal task offloading method provided in the first aspect or the terminal task offloading method described in any possible design manner of the first aspect.
Optionally, the terminal task offloading device may further include a memory, and the memory is configured to store program instructions and data of the terminal task offloading device. Further optionally, the terminal task offloading device may further include a transceiver, and the transceiver is configured to perform a step of transceiving data, signaling, or information, for example, acquiring the second parameter, under the control of the processor of the terminal task offloading device.
Alternatively, the terminal task offloading device may be a terminal itself, or may be a device (such as a server) connected to the terminal for offloading a terminal task, or may be a part of the device or the terminal itself, for example, a chip system in the server or the terminal. The chip system is configured to support the terminal task offloading device to implement the functions related to the first aspect, for example, to receive, send, or process data and/or information related to the terminal task offloading method. The chip system includes a chip and may also include other discrete devices or circuit structures.
In a fourth aspect, the present application provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are executed by a computer, the method for splitting a terminal task provided in the first aspect or the method for splitting a terminal task described in any one of the possible design manners of the first aspect is implemented.
In a fifth aspect, the present application provides a computer program product, which includes computer instructions, when the computer instructions are executed on a computer, cause the computer to execute the terminal task offloading method according to the first aspect or the terminal task offloading method according to any possible design manner of the first aspect.
In a sixth aspect, the present application provides a terminal task offloading system, including a terminal and an MEC server as described in the first aspect.
It should be noted that all or part of the computer instructions may be stored on the computer readable storage medium. The computer-readable storage medium may be packaged together with the processor of the terminal task offloading device, or may be packaged separately from the processor of the terminal task offloading device, which is not limited in this application.
For the description of the second, third, fourth, fifth and sixth aspects in this application, reference may be made to the detailed description of the first aspect and its various implementations; moreover, for the beneficial effects of the second aspect, the third aspect, the fourth aspect, the fifth aspect and the sixth aspect, reference may be made to beneficial effect analysis in the first aspect and various implementation manners thereof, and details are not repeated here.
In this application, the names of the terminal task offloading devices mentioned above do not limit the devices or the functional modules themselves, and in practical implementations, the devices or the functional modules may appear by other names. Insofar as the functions of the respective devices or functional blocks are similar to those of the present invention, they are within the scope of the claims of the present application and their equivalents.
These and other aspects of the present application will be more readily apparent from the following description.
Drawings
Fig. 1 is a schematic structural diagram of a terminal task offloading system according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of another terminal task offloading system according to an embodiment of the present disclosure;
fig. 3 is a schematic flowchart of a terminal task offloading method according to an embodiment of the present application;
fig. 4 is a schematic flowchart of another method for splitting a terminal task according to an embodiment of the present application;
fig. 5 is a schematic flowchart of another method for offloading a terminal task according to an embodiment of the present application;
fig. 6 is a schematic flowchart of another method for offloading a terminal task according to an embodiment of the present application;
fig. 7 is a schematic flowchart of another method for offloading a terminal task according to an embodiment of the present application;
fig. 8 is a schematic flowchart of another method for offloading a terminal task according to an embodiment of the present application;
fig. 9 is a schematic flowchart of another method for offloading a terminal task according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of a terminal task offloading device according to an embodiment of the present application;
fig. 11 is a schematic structural diagram of another terminal task offloading device provided in an embodiment of the present application.
Detailed Description
The following describes in detail a terminal task offloading method and apparatus provided in an embodiment of the present application with reference to the accompanying drawings.
The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone.
The terms "first" and "second" and the like in the description and drawings of the present application are used for distinguishing different objects or for distinguishing different processes for the same object, and are not used for describing a specific order of the objects.
Furthermore, the terms "including" and "having," and any variations thereof, as referred to in the description of the present application, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may alternatively include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to mean serving as examples, illustrations or descriptions. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.
In the description of the present application, the meaning of "a plurality" means two or more unless otherwise specified.
With the development of mobile internet and the popularization of intelligent terminals, some complex applications, such as applications based on AR technology or VR technology, appear.
The advent of complex applications based on AR technology or VR technology, etc. has improved user experience. However, the computing power and resources of the terminal are limited, and other fixed applications are also running inside the terminal. This results in that when the terminal executes the tasks of the complex applications, the terminal cannot not only process the tasks of the complex applications well, but also affects the processing of the terminal on the tasks of other applications.
In view of the problems in the prior art, embodiments of the present application provide a terminal task offloading method, which determines whether to execute a task to be executed locally at a terminal by analyzing a theoretical resource consumption condition of the task to be executed and a remaining condition of local resources of the terminal, so as to implement offloading of a terminal task, and execute only a part of tasks at the terminal, so as to ensure that the terminal can better process a service.
The terminal task offloading method provided in the embodiment of the present application may be applied to a system architecture shown in fig. 1, where the system architecture includes a terminal 01 and a Mobile Edge Computing (MEC) server 02.
The terminal 01 may be a mobile phone, a tablet computer, a desktop computer, a laptop computer, a notebook computer, an ultra-mobile personal computer (UMPC), a handheld computer, a netbook, a Personal Digital Assistant (PDA), a wearable electronic device, a virtual reality device, and other different types of terminals connected to the MEC server 02.
And the terminal 01 is used for responding to the task execution instruction and determining a first parameter of the task to be executed. The terminal 01 is further configured to obtain a second parameter. Then, the terminal 01 determines whether to execute the task to be executed locally at the terminal 01 according to the first parameter and the second parameter.
And the MEC server 02 is used for executing the task to be executed according to the instruction of the terminal 01 when the terminal 01 determines that the task to be executed is executed in the MEC server 02.
In another possible implementation manner, the terminal task offloading method provided in this embodiment of the present application may be applied to a system architecture shown in fig. 2, where the system architecture includes a terminal 01, an MEC server 02, and a terminal task offloading device 03.
The terminal task shunting device 03 is connected with the terminal 01 and the MEC server 02 respectively.
The terminal task shunting device 03 is configured to determine, in response to the task execution instruction, a first parameter of the task to be executed. The terminal task shunting device 03 is further configured to acquire a second parameter, and then determine whether to execute the task to be executed locally at the terminal 01 according to the first parameter and the second parameter.
The terminal task offloading device 03 may be a physical machine (such as a server) or a Virtual Machine (VM) deployed on the physical machine.
And the terminal 01 is used for executing the task to be executed according to the instruction of the terminal task shunting device 03 when the terminal 01 determines that the task to be executed is executed by the terminal task shunting device 03.
The MEC server 02 is configured to execute the to-be-executed task according to the instruction of the terminal task offloading device 03 when the terminal task offloading device 03 determines that the to-be-executed task is executed in the MEC server 02.
It is to be understood that, in practical applications, the terminal task offloading system shown in fig. 1 or fig. 2 may further include other devices, for example, may also include a base station, and only devices that may be used in the embodiment of the present application are described herein, and do not form a specific limitation on the terminal task offloading system.
The following describes a terminal task offloading method provided in the embodiment of the present application with reference to the terminal task offloading system. In the following description of the embodiments of the present application, the terminal task shunting system shown in fig. 1 will be taken as an example for explanation.
Referring to fig. 3, a method for offloading a terminal task provided in an embodiment of the present application may include, by S101-S103:
s101, the terminal responds to the task execution instruction and determines a first parameter of a task to be executed.
In one possible implementation manner, the task execution instruction may be a trigger operation performed by a user on a user interface of the terminal. Illustratively, the task execution instruction may be a click operation or a slide operation of a user on an icon of an Application (APP) at a user interface of the terminal.
The first parameter comprises a first hardware resource, a first network resource and a task type of the task to be executed, wherein the first hardware resource and the first network resource are required by the task to be executed.
In a possible implementation manner, the first hardware resource required for executing the task to be executed may include a first Central Processing Unit (CPU) resource and a first memory resource.
In one possible implementation, the first network resources required to perform the task to be performed may include a first latency and a first network bandwidth.
In another possible implementation, the first network resources required to perform the task to be performed may also include radio link quality parameters. The radio link quality parameter is used for representing the index requirement of executing the task to be executed on the radio link quality.
In one possible implementation, the task types of the tasks to be performed may be divided into target types and non-target types. The target type is the type of a task which is required to be executed locally at the terminal, and the non-target type is the type of a task which is not required to be executed locally at the terminal.
It will be appreciated that in practical applications the first hardware resource may also comprise other resources. The first network resource may further include other resources, and the task type of the task to be executed may also be divided according to other manners, which is not limited in this embodiment of the present application.
S102, the terminal acquires a second parameter.
The second parameter includes a second network resource between the terminal and the base station and a second hardware resource of the terminal. The base station corresponds to a terminal.
In one possible implementation, the second network resource between the terminal and the base station may include a second time delay and a second network bandwidth.
In a possible implementation manner, the second hardware resource of the terminal may include a second CPU resource and a second memory resource.
It will be appreciated that in practical applications the second hardware resource may also comprise other resources. The second network resource may also include other resources, which is not limited in this embodiment of the present application.
S103, the terminal determines whether to execute the task to be executed on the terminal according to the first parameter and the second parameter.
After the terminal acquires the second parameter, it may be determined, in combination with the determined first parameter, that the task to be executed is executed locally at the terminal, or the task to be executed is executed at an MEC server corresponding to the terminal, so that the terminal service may be shunted.
In one possible implementation manner, the terminal may determine whether to execute the task to be executed locally on the terminal according to the sizes of the first CPU resource and the second CPU resource. For example, when the percentage of the first CPU resource to the second CPU resource is greater than or equal to the first threshold, the terminal may determine that the task to be executed is executed locally at the terminal. When the percentage of the first CPU resource in the second CPU resource is less than the first threshold, the terminal may determine that the task to be executed is the target task.
In a possible implementation manner, the terminal may determine whether to execute the task to be executed locally at the terminal according to the sizes of the first memory resource and the second memory resource. For example, when the percentage of the first memory resource in the second memory resource is greater than or equal to the second threshold, the terminal may determine to locally execute the task to be executed at the terminal. When the percentage of the first memory resource in the second memory resource is smaller than the second threshold, the terminal may determine that the task to be executed is the target task.
The first threshold and the second threshold are human parameters determined in advance, which are not limited in the embodiment of the present application.
In a possible implementation manner, the terminal may determine whether to execute the task to be executed locally at the terminal according to the sizes of the first delay and the second delay. For example, when the first time delay is less than or equal to the second time delay, the terminal may determine that the task to be performed is performed locally at the terminal. When the first time delay is greater than the second time delay, the terminal may determine that the task to be executed is the target task.
In one possible implementation manner, the terminal may determine whether to execute the task to be executed locally at the terminal according to the sizes of the first network bandwidth and the second network bandwidth. For example, when the first network bandwidth is greater than or equal to the second network bandwidth, the terminal may determine that the task to be performed is performed locally at the terminal. When the first network bandwidth is smaller than the second network bandwidth, the terminal may determine that the task to be executed is a target task.
It is to be understood that, in practical applications, the terminal may also determine whether to execute the task to be executed locally in the terminal in combination with the above-mentioned several implementations. Illustratively, when the percentage of the first CPU resource in the second CPU resource is greater than or equal to a first threshold, or when the percentage of the first memory resource in the second memory resource is greater than or equal to a second threshold, or when the first delay is less than or equal to a second delay, or when the first network bandwidth is greater than or equal to the second network bandwidth, the terminal may determine that the task to be executed is locally executed at the terminal, otherwise, the terminal may determine that the task to be executed is the target task.
Optionally, after the terminal determines that the task to be executed is the target task, it may be further determined whether to execute the task to be executed locally on the terminal in combination with other parameters.
In a possible implementation manner, the terminal may obtain a third hardware resource of the MEC server, and when the radio link quality parameter satisfies the first preset condition, the third hardware resource satisfies the second preset condition, and the task type is not the target type, the terminal may determine to execute the task to be executed at the MEC server. And when the wireless link quality parameter does not meet the first preset condition, or the third hardware resource does not meet the second preset condition, or the task type is the target type, the terminal determines to execute the task to be executed locally on the terminal.
The third hardware resource comprises a third CPU resource and a third memory resource, and the MEC server corresponds to the terminal.
Illustratively, the first preset condition may be that the radio link quality parameter falls within a preset range. The preset range may be an index range of the radio link quality determined in advance by human.
For example, the second preset condition may be that the percentage of the first CPU resource to the third CPU resource is less than or equal to a third threshold, and the percentage of the first memory resource to the third memory resource is less than or equal to a fourth threshold. The third threshold and the fourth threshold may be parameters determined in advance by a human, which is not limited in this application.
Optionally, after the terminal determines that the to-be-executed task is executed by the MEC server, the terminal may send a task execution request to the MEC server, where the task execution request carries the user registration information. The MEC server may include a receiving module, and the receiving module may intercept the task execution request sent by the terminal based on an Internet Protocol (IP) quintuple. After receiving the task execution request, the MEC server may determine whether the user is a registered user according to the user registration information, and when it is determined that the user corresponding to the user registration information is the registered user, the MEC server sends a task execution response to the terminal, where the task execution response is used to notify the terminal MEC server that the to-be-executed task is determined to be executed on the MEC server. After receiving the task execution response, the terminal sends the information of the specific task to the MEC server, and the MEC server may intercept the information of the specific task sent by the terminal based on the IP quintuple. The MEC server may further include a task allocation module, and the task allocation module may select a third CPU resource and a third memory resource of the MEC server to execute the task to be executed based on the information of the specific task sent by the terminal, and feed back an execution result to the terminal after execution.
Alternatively, the radio link quality may be degraded, the network bandwidth may be insufficient, etc. during the execution of the task to be executed by the MEC server. Therefore, optionally, during the period that the MEC server executes the task to be executed, the terminal may acquire an execution parameter of the MEC server executing the task to be executed, and when the execution parameter meets a third preset condition, the terminal determines to locally re-execute the task to be executed.
In a possible implementation manner, the execution parameter may include monitoring delay, monitoring network bandwidth, and monitoring radio link quality parameter, and the third preset condition may be that any one of the monitoring delay is within a preset delay range, the monitoring network bandwidth is within a preset network bandwidth range, and the monitoring radio link quality parameter is within a preset radio link quality parameter range is satisfied. The preset monitoring time delay, the preset monitoring network bandwidth and the preset monitoring wireless link quality parameter are all parameters determined in advance manually, and the embodiment of the application is not limited to the above.
According to the terminal task shunting method provided by the embodiment of the application, the first parameter of the task to be executed can be determined, and the first parameter comprises a first hardware resource and a first network resource which are required by the task to be executed. Therefore, the first parameter may reflect the resources consumed by executing the theory of the task to be performed. The second parameter acquired by the terminal can reflect the remaining amount of the local resource of the terminal. Therefore, whether to execute the task to be executed locally at the terminal can be determined by combining the first parameter and the second parameter. In addition, the first parameter also comprises the task type of the task to be executed, and certain specific tasks can be determined to be executed locally in the terminal. Therefore, the terminal task shunting method provided by the application determines whether the task to be executed is executed locally at the terminal or not by analyzing the theoretical resource consumption condition of the task to be executed and the residual condition of the local resource of the terminal, so that the shunting of the terminal task is realized, and only part of tasks are executed at the terminal, so that the terminal can better process services.
In summary of the above description, as shown in fig. 4, step S103 in fig. 3 may be replaced with S1031-S1032:
and S1031, when the terminal determines that the percentage of the first CPU resource in the second CPU resource is greater than or equal to a first threshold, or the percentage of the first memory resource in the second memory resource is greater than or equal to a second threshold, determining that the task to be executed is executed locally on the terminal.
S1032, when the terminal determines that the percentage of the first CPU resource in the second CPU resource is smaller than a first threshold value and the percentage of the first memory resource in the second memory resource is smaller than a second threshold value, determining that the task to be executed is a target task.
Optionally, as shown in fig. 5, after step S1032, the method further includes S1033-S1034:
s1033, the terminal acquires a third hardware resource of the MEC server.
S1034, when the terminal determines that the wireless link quality parameter meets a first preset condition, the third hardware resource meets a second preset condition and the task type is not the target type, determining to execute the task to be executed on the MEC server; otherwise, the terminal determines to execute the task to be executed locally on the terminal.
Alternatively, as shown in fig. 6, step S103 in fig. 3 may be replaced with S1035-S1036:
and S1035, when the terminal determines that the first time delay is less than or equal to the second time delay or the first network bandwidth is greater than or equal to the second network bandwidth, determining that the task to be executed is locally executed at the terminal.
And S1036, when the terminal determines that the first time delay is larger than the second time delay and the first network bandwidth is smaller than the second network bandwidth, determining that the task to be executed is the target task.
Optionally, as shown in fig. 7, after step S1036, the method further includes S1037-S1038:
s1037, the terminal acquires a third hardware resource of the MEC server.
S1038, when the terminal determines that the wireless link quality parameter meets a first preset condition, the third hardware resource meets a second preset condition and the task type is not the target type, determining to execute the task to be executed on the MEC server; otherwise, the terminal determines to execute the task to be executed at the terminal.
Optionally, as shown in fig. 8 or 9, after step S1034 or step S1038, the method further includes S104-S105:
and S104, the terminal acquires the execution parameters of the MEC server for executing the task to be executed.
And S105, when the terminal determines that the execution parameters meet the third preset condition, determining that the task to be executed is executed again in the local terminal.
As shown in fig. 10, an embodiment of the present application further provides a terminal task offloading device, where the terminal task offloading device may be a terminal in the terminal task offloading system shown in fig. 1, or may be a terminal task offloading device 03 in the terminal task offloading system shown in fig. 2. The terminal task shunting device comprises: a determination module 31 and an acquisition module 32.
The obtaining module 32 executes S102 in the above method embodiment, and the determining module 31 executes S101 and S103 in the above method embodiment.
Specifically, the determining module 31 is configured to determine, in response to the task execution instruction, a first parameter of the task to be executed. The first parameter comprises a first hardware resource, a first network resource and a task type of the task to be executed, wherein the first hardware resource and the first network resource are required by the task to be executed.
And an obtaining module 32, configured to obtain the second parameter. Wherein the second parameter comprises: a second network resource between the terminal and the base station, a second hardware resource of the terminal, and the base station corresponding to the terminal.
The determining module 31 is further configured to determine whether to execute the task to be executed at the terminal according to the first parameter determined by itself and the second parameter obtained by the obtaining module 32.
Optionally, the first hardware resource includes a first CPU resource and a first memory resource, and the second hardware resource includes a second CPU resource and a second memory resource.
The determining module 31 is specifically configured to: when the percentage of the first CPU resource in the second CPU resource is larger than or equal to a first threshold value, or the percentage of the first memory resource in the second memory resource is larger than or equal to a second threshold value, determining that a task to be executed is executed at the terminal; and when the percentage of the first CPU resource in the second CPU resource is smaller than a first threshold value and the percentage of the first memory resource in the second memory resource is smaller than a second threshold value, determining that the task to be executed is a target task.
Optionally, the first network resource comprises a first latency and a first network bandwidth, and the second network resource comprises a second latency and a second network bandwidth.
The determining module 31 is further specifically configured to: when the first time delay is less than or equal to the second time delay or the first network bandwidth is greater than or equal to the second network bandwidth, determining that a task to be executed is executed at the terminal; and when the first time delay is greater than the second time delay and the first network bandwidth is less than the second network bandwidth, determining the task to be executed as the target task.
Optionally, the first network resource further comprises a radio link quality parameter.
The obtaining module 32 is further configured to, when the determining module 31 determines that the task to be executed is the target task, obtain a third hardware resource of the MEC server; the third hardware resource comprises a third CPU resource and a third memory resource; the MEC server corresponds to the terminal.
The determining module 31 is further configured to determine to execute the task to be executed at the MEC server when the radio link quality parameter meets a first preset condition, the third hardware resource meets a second preset condition, and the task type is not the target type; and when the wireless link quality parameter does not meet the first preset condition, or the third hardware resource does not meet the second preset condition, or the task type is the target type, determining to execute the task to be executed at the terminal.
Optionally, the obtaining module 32 is further configured to obtain, after the MEC server executes the task to be executed, an execution parameter of the MEC server executing the task to be executed.
The determining module 31 is further configured to determine that the terminal re-executes the task to be executed when the execution parameter meets a third preset condition.
Optionally, the terminal task offloading device further includes a storage module. The storage module is used for storing program codes and the like of the terminal task shunting device.
As shown in fig. 11, an embodiment of the present application further provides a terminal task offloading device, which includes a memory 41, a processor 42, a bus 43, and a communication interface 44; the memory 41 is used for storing computer execution instructions, and the processor 42 is connected with the memory 41 through a bus 43; when the terminal task offloading device operates, the processor 42 executes the computer execution instructions stored in the memory 41 to make the terminal task offloading device execute the terminal task offloading method provided in the above embodiment.
In particular implementations, processor 42(42-1 and 42-2) may include one or more Central Processing Units (CPUs), such as CPU0 and CPU1 shown in FIG. 11, as one example. And as an example, the terminal task shunting device may include a plurality of processors 42, such as processor 42-1 and processor 42-2 shown in fig. 11. Each of the processors 42 may be a single-Core Processor (CPU) or a multi-Core Processor (CPU). Processor 42 may refer herein to one or more devices, circuits, and/or processing cores that process data (e.g., computer program instructions).
The memory 41 may be, but is not limited to, a read-only memory 41 (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 41 may be self-contained and coupled to the processor 42 via a bus 43. The memory 41 may also be integrated with the processor 42.
In a specific implementation, the memory 41 is used for storing data in the present application and computer-executable instructions corresponding to a software program for executing the present application. The processor 42 may perform various functions of the terminal task offloading device by running or executing software programs stored in the memory 41, and calling data stored in the memory 41.
The communication interface 44 may be any device, such as a transceiver, for communicating with other devices or communication networks, such as a control system, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), etc. The communication interface 44 may include a receiving unit implementing a receiving function and a transmitting unit implementing a transmitting function.
The bus 43 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an extended ISA (enhanced industry standard architecture) bus, or the like. The bus 43 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 11, but this is not intended to represent only one bus or type of bus.
As an example, in conjunction with fig. 10, the function implemented by the acquisition module in the terminal task offloading device is the same as the function implemented by the receiving unit in fig. 11, and the function implemented by the storage module in the terminal task offloading device is the same as the function implemented by the storage in fig. 11.
For the explanation of the related content in this embodiment, reference may be made to the above method embodiment, which is not described herein again.
Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions. For the specific working processes of the system, the apparatus and the unit described above, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.
The embodiment of the present application further provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the computer executes the instructions, the computer is enabled to execute the terminal task offloading method provided in the foregoing embodiment.
The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a RAM, a ROM, an erasable programmable read-only memory (EPROM), a register, a hard disk, an optical fiber, a CD-ROM, an optical storage device, a magnetic storage device, any suitable combination of the foregoing, or any other form of computer readable storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an Application Specific Integrated Circuit (ASIC). In embodiments of the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (12)

1. A terminal task shunting method is characterized by comprising the following steps:
responding to a task execution instruction, and determining a first parameter of a task to be executed; the first parameters comprise a first hardware resource, a first network resource and a task type of the task to be executed, wherein the first hardware resource and the first network resource are required by executing the task to be executed;
acquiring a second parameter; the second parameter includes: a second network resource between the terminal and the base station, a second hardware resource of the terminal; the base station corresponds to the terminal;
and determining whether to execute the task to be executed at the terminal according to the first parameter and the second parameter.
2. The method for splitting tasks of a terminal according to claim 1, wherein the first hardware resource includes a first CPU resource and a first memory resource, the second hardware resource includes a second CPU resource and a second memory resource, and the determining whether to execute the task to be executed at the terminal according to the first parameter and the second parameter includes:
when the percentage of the first CPU resource in the second CPU resource is greater than or equal to a first threshold value, or the percentage of the first memory resource in the second memory resource is greater than or equal to a second threshold value, determining to execute the task to be executed at the terminal;
and when the percentage of the first CPU resource in the second CPU resource is smaller than a first threshold value and the percentage of the first memory resource in the second memory resource is smaller than a second threshold value, determining that the task to be executed is a target task.
3. The method according to claim 2, wherein the first network resource includes a first latency and a first network bandwidth, the second network resource includes a second latency and a second network bandwidth, and the determining whether to execute the task to be executed at the terminal according to the first parameter and the second parameter includes:
when the first time delay is less than or equal to the second time delay or the first network bandwidth is greater than or equal to the second network bandwidth, determining that the task to be executed is executed at the terminal;
and when the first time delay is greater than the second time delay and the first network bandwidth is smaller than the second network bandwidth, determining that the task to be executed is a target task.
4. The method according to claim 2 or 3, wherein the first network resource further includes a radio link quality parameter, and after determining that the task to be executed is a target task, the method further includes:
acquiring a third hardware resource of the mobile edge computing MEC server; the third hardware resource comprises a third CPU resource and a third memory resource; the MEC server corresponds to the terminal;
when the radio link quality parameter meets a first preset condition, the third hardware resource meets a second preset condition and the task type is not a target type, determining to execute the task to be executed on the MEC server; and when the radio link quality parameter does not meet the first preset condition, or the third hardware resource does not meet the second preset condition, or the task type is the target type, determining to execute the task to be executed at the terminal.
5. The terminal task offloading method of claim 4, wherein the determining is performed after the MEC server executes the task to be executed, the method further comprising:
acquiring an execution parameter of the MEC server for executing the task to be executed;
and when the execution parameter meets a third preset condition, determining that the terminal re-executes the task to be executed.
6. A terminal task shunting device is characterized by comprising:
the determining module is used for responding to the task execution instruction and determining a first parameter of the task to be executed; the first parameters comprise a first hardware resource, a first network resource and a task type of the task to be executed, wherein the first hardware resource and the first network resource are required by executing the task to be executed;
the acquisition module is used for acquiring a second parameter; the second parameter includes: a second network resource between the terminal and the base station, a second hardware resource of the terminal; the base station corresponds to the terminal;
the determining module is further configured to determine whether to execute the task to be executed at the terminal according to the first parameter determined by the determining module and the second parameter acquired by the acquiring module.
7. The device according to claim 6, wherein the first hardware resource includes a first CPU resource and a first memory resource, the second hardware resource includes a second CPU resource and a second memory resource, and the determining module is specifically configured to:
when the percentage of the first CPU resource in the second CPU resource is greater than or equal to a first threshold value, or the percentage of the first memory resource in the second memory resource is greater than or equal to a second threshold value, determining to execute the task to be executed at the terminal;
and when the percentage of the first CPU resource in the second CPU resource is smaller than a first threshold value and the percentage of the first memory resource in the second memory resource is smaller than a second threshold value, determining that the task to be executed is a target task.
8. The apparatus of claim 7, wherein the first network resource comprises a first latency and a first network bandwidth, the second network resource comprises a second latency and a second network bandwidth, and the determining module is further specifically configured to:
when the first time delay is less than or equal to the second time delay or the first network bandwidth is greater than or equal to the second network bandwidth, determining that the task to be executed is executed at the terminal;
and when the first time delay is greater than the second time delay and the first network bandwidth is smaller than the second network bandwidth, determining that the task to be executed is a target task.
9. A terminal task offloading device according to claim 7 or 8, wherein the first network resource further comprises a radio link quality parameter,
the obtaining module is further configured to obtain a third hardware resource of the MEC server when the determining module determines that the task to be executed is the target task; the third hardware resource comprises a third CPU resource and a third memory resource; the MEC server corresponds to the terminal;
the determining module is further configured to determine to execute the task to be executed at the MEC server when the radio link quality parameter meets a first preset condition, the third hardware resource meets a second preset condition, and the task type is not a target type; and when the radio link quality parameter does not meet the first preset condition, or the third hardware resource does not meet the second preset condition, or the task type is the target type, determining to execute the task to be executed at the terminal.
10. A terminal task offloading device as recited in claim 9,
the acquiring module is further configured to acquire, after the MEC server executes the task to be executed, an execution parameter of the MEC server for executing the task to be executed;
the determining module is further configured to determine that the terminal re-executes the task to be executed when the execution parameter meets a third preset condition.
11. A terminal task shunting device is characterized by comprising a memory, a processor, a bus and a communication interface; the memory is used for storing computer execution instructions, and the processor is connected with the memory through the bus;
when the terminal task shunting device runs, the processor executes the computer-executable instructions stored in the memory to cause the terminal task shunting device to execute the terminal task shunting method according to any one of claims 1-5.
12. A computer-readable storage medium, wherein instructions are stored in the computer-readable storage medium, and when the instructions are executed by a computer, the computer is enabled to execute the terminal task offloading method according to any one of claims 1-5.
CN202011204900.XA 2020-11-02 2020-11-02 Terminal task shunting method and device Pending CN114443261A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011204900.XA CN114443261A (en) 2020-11-02 2020-11-02 Terminal task shunting method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011204900.XA CN114443261A (en) 2020-11-02 2020-11-02 Terminal task shunting method and device

Publications (1)

Publication Number Publication Date
CN114443261A true CN114443261A (en) 2022-05-06

Family

ID=81357575

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011204900.XA Pending CN114443261A (en) 2020-11-02 2020-11-02 Terminal task shunting method and device

Country Status (1)

Country Link
CN (1) CN114443261A (en)

Similar Documents

Publication Publication Date Title
CN109561141B (en) CDN node selection method and equipment
CN109547286B (en) CDN node selection method, device and storage medium
CN108628684B (en) DPDK-based message processing method and computer equipment
CN109451002B (en) CDN node selection method and equipment
US9161064B2 (en) Auto-scaling management of web content
CN111191777B (en) Neural network processor and control method thereof
US11853767B2 (en) Inter-core data processing method, system on chip and electronic device
CN112423351A (en) Network mode determination method and device
CN111741512B (en) Private network access method and device
CN111586716B (en) Network slice deployment method and device
CN115237589A (en) SR-IOV-based virtualization method, device and equipment
CN110597643B (en) Inter-core communication method, processor and electronic equipment
CN112068965A (en) Data processing method and device, electronic equipment and readable storage medium
CN114363414A (en) Method, device and system for scheduling calculation examples
CN114443261A (en) Terminal task shunting method and device
CN116244231A (en) Data transmission method, device and system, electronic equipment and storage medium
CN111475230A (en) Application function configuration method and device and electronic equipment
CN112215667B (en) User behavior prediction method and device
CN110869910A (en) Search resource recommendation method and related product
CN111708715B (en) Memory allocation method, memory allocation device and terminal equipment
CN114661762A (en) Query method and device for embedded database, storage medium and equipment
US20200192942A1 (en) Method for Processing Application Resources and Related Products
CN116610648A (en) Log storage method and device, electronic equipment and storage medium
CN111163533B (en) Network connection method and related product
CN113938992A (en) Threshold determination method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination