CN116233748A - Terminal equipment management and control method and device, storage medium and electronic equipment - Google Patents

Abstract

The application relates to the technical field of computers, and provides a terminal equipment management and control method and device, a storage medium and electronic equipment. The terminal equipment management and control method is applied to the terminal equipment and comprises the following steps: acquiring a control strategy set for terminal equipment in an electronic fence; the policing policy is executed before the terminal device reaches the entry device of the electronic fence. In the method, the terminal equipment executes the control strategy before reaching the entrance equipment of the electronic fence, which is equivalent to enabling the terminal equipment to be in a state of entering the electronic fence in advance, so that when a user holding the terminal equipment enters the electronic fence, the terminal equipment does not need to execute the control strategy again, the waiting time of the user at the entrance equipment can be shortened, and the congestion phenomenon at the entrance of the electronic fence is obviously improved.

Description

Terminal equipment management and control method and device, storage medium and electronic equipment

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a method and apparatus for controlling a terminal device, a storage medium, and an electronic device.

Background

An electronic fence is understood to be a geographical area of some significance delimited by specific entrance and exit devices. For example, a factory area defined by a gate for card punching on the business trip belongs to an electronic fence. In some occasions with higher requirements on security and confidentiality, when a user enters the electronic fence with a terminal device (such as a mobile phone), the user needs to execute some management and control strategies (such as disabling the functions of shooting and recording) on the terminal device by matching with the entrance device of the electronic fence and a background server. However, the current management and control policy implementation process is complex, so that a long time is required to complete the policy validation, before that, a user has to wait at the entrance of the electronic fence, and if more users need to enter the electronic fence at the same time (for example, when a factory is working), a congestion phenomenon is easily generated at the entrance of the electronic fence.

Disclosure of Invention

An objective of the embodiments of the present application is to provide a terminal device management and control method and apparatus, a storage medium, and an electronic device, so as to improve the above technical problems.

In order to achieve the above purpose, the present application provides the following technical solutions:

in a first aspect, an embodiment of the present application provides a terminal device management and control method, which is applied to a terminal device, where the method includes: acquiring a control strategy set for the terminal equipment in the electronic fence; and executing the control strategy before the terminal equipment reaches the entrance equipment of the electronic fence.

In the method, the terminal equipment executes the control strategy before reaching the entrance equipment of the electronic fence, which is equivalent to enabling the terminal equipment to be in a state of entering the electronic fence in advance, so that when a user holding the terminal equipment enters the electronic fence, the terminal equipment does not need to execute the control strategy again, the waiting time of the user at the entrance equipment can be shortened, and the congestion phenomenon at the entrance of the electronic fence is obviously improved.

Note that although the above method does not completely exclude the case where the terminal device executes the policing policy but does not succeed in validating the policy, the probability of this is low, so that it is a necessary effect to save the waiting time of the user at the portal device from a statistical sense.

In an implementation manner of the first aspect, the obtaining a management and control policy set for the terminal device in the electronic fence includes: before the terminal equipment reaches the entrance equipment, a request for acquiring the control strategy is sent to a server, and the control strategy corresponding to the request returned by the server is received; the executing the control strategy comprises the following steps: in response to receiving the policing policy from the server, the policing policy is executed.

In the implementation manner, before the terminal device reaches the inlet device, the terminal device requests the management and control strategy from the server and executes the management and control strategy immediately after receiving the management and control strategy, namely, the acquisition and execution operations of the management and control strategy are bound together, so that the operation logic is simplified, and the acquired management and control strategy can be ensured to be newer.

In an implementation manner of the first aspect, before the terminal device reaches the entrance device of the electronic fence, executing the management and control policy includes: and before the terminal equipment reaches the entrance equipment of the electronic fence, responding to the triggering operation on the terminal equipment, and executing the control strategy.

In the implementation manner, the execution of the management and control strategy on the terminal device is triggered through the triggering operation made by the user, so that whether the execution of the management and control strategy is completely under the control of the user, namely, the degree of freedom is higher.

In an implementation manner of the first aspect, the executing the management and control policy in response to a triggering operation on the terminal device includes: and when the condition that the permission triggering condition is met is detected, responding to the triggering operation on the terminal equipment, and executing the control strategy.

In the above implementation manner, the terminal device conditionally responds to the trigger operation, so that the situation that the user performs the trigger operation by mistake can be improved.

In an implementation manner of the first aspect, the allowed trigger condition includes at least one of the following conditions: the distance between the terminal equipment and the entrance equipment is smaller than a first distance threshold value; the difference between the current time and the target time for the terminal device to reach the entry device is less than a first time threshold.

In the implementation manner, the distance between the terminal device and the entrance device is smaller than the first distance threshold, which indicates that the user is about to enter the electronic fence, so that the triggering operation can be responded. The target time when the terminal device arrives at the entrance device may be, for example, a time limit of the user going to work (exceeding the time limit belongs to late arrival), and if the difference between the current time and the target time is smaller than the first time threshold, the user will enter the electronic fence with a high probability, so that the triggering operation may be responded.

In an implementation manner of the first aspect, before the terminal device reaches the entrance device of the electronic fence, executing the management and control policy includes: and executing the effective operation of the control strategy when the terminal equipment detects that the automatic triggering condition is met before reaching the entrance equipment of the electronic fence.

In the implementation manner, the terminal equipment automatically detects the specific condition to trigger the execution of the management and control strategy on the terminal equipment, so that the operation burden of a user can be reduced, and the situations that the user forgets to execute the triggering operation, wrongly executes the triggering operation and the like are improved.

In one implementation of the first aspect, the automatic triggering condition includes at least one of the following conditions: the distance between the terminal equipment and the entrance equipment is smaller than a second distance threshold value; the difference between the current time and the target time for the terminal device to reach the entry device is less than a second time threshold.

In the implementation manner, the distance between the terminal device and the entrance device is smaller than the second distance threshold, which indicates that the user is about to enter the electronic fence, so that automatic triggering can be performed. The target time for the terminal device to reach the entrance device may be, for example, a time limit of the user going to work (exceeding the time limit belongs to late arrival), and if the difference between the current time and the target time is smaller than a time threshold, the user will enter the electronic fence with a high probability, so that automatic triggering may be performed.

In one implementation manner of the first aspect, the method further includes: generating first scanning information for the portal equipment to scan, wherein the first scanning information comprises equipment identification of the terminal equipment; or after the terminal equipment arrives at the entrance equipment, the equipment identification is sent to the entrance equipment.

In the implementation manner, when the user enters the electronic fence, the terminal equipment only needs to provide the equipment identifier for the entrance equipment, and the processing flow is quite simple.

In an implementation manner of the first aspect, after the executing the management policy, the method further includes: acquiring a first strategy effective state of the management and control strategy; the first scan information further includes the first policy validation state; or after the terminal device reaches the entrance device, the first policy validation state is further sent to the entrance device; or sending the device identification and the first policy validation state to a server.

In the above implementation, when the user enters the electronic fence, the terminal device needs to provide the device identifier and the first policy validation state to the portal device (the first policy validation state may be sent to the server in advance). The first policy validation state may be used to identify whether the terminal device validates the management and control policy normally, so that the relevant parties can decide whether to allow the user to enter the electronic fence based on the first policy validation state, or take corresponding measures (such as later attempt to validate the management and control policy again), which is beneficial to implementing more strict management and control on the user entering the fence.

In an implementation manner of the first aspect, the first policy validation state is used for outputting on the portal device, or is used as a basis for allowing or rejecting, by the portal device, the user to enter the electronic fence.

In the above implementation, the first policy validation state may be output (e.g., a voice prompt is displayed or played) on the portal device, and a worker at the portal device may control the portal device according to the output content, so as to allow or reject the user to enter the electronic fence, which may implement strict control over the user entering the electronic fence. Alternatively, the electronic fence can automatically allow or reject the user to enter the electronic fence based on the first policy validation state, so that the labor cost for controlling the electronic fence is reduced.

In an implementation manner of the first aspect, the first policy validation state is not validated normally, and the method further includes: receiving a policy execution instruction sent by a server, wherein the policy execution instruction is used for indicating the terminal equipment to execute the management and control policy; operating the strategy execution instruction to obtain a second strategy effective state of the management and control strategy; generating second scanning information for the portal device to scan, wherein the second scanning information comprises the device identification and the second policy validation state; or sending the device identification and the second policy validation state to the portal device; or sending the device identification and the second policy validation to the server.

In the above implementation manner, if the first policy validation state is not validated normally, the server may send a policy execution instruction to the terminal device, so that the terminal device tries to execute the management and control policy again, thereby improving the problem that the management and control policy is not validated normally due to accidental factors, and enabling the user to enter the electronic fence normally. In addition, the implementation mode can also be compatible with the situation that the terminal equipment does not execute the management and control strategy in advance.

In a second aspect, an embodiment of the present application provides a terminal device management and control method, which is applied to a server, where the method includes: after a terminal device reaches an entrance device of an electronic fence, receiving a device identifier of the terminal device sent by the entrance device, and a first policy validation state of a management and control policy set for the terminal device in the electronic fence; the first policy validation state is a validation state of the management and control policy obtained by the terminal equipment executing the management and control policy; and storing the equipment identifier and the corresponding first policy validation state.

In the method, the terminal equipment executes the control strategy before reaching the entrance equipment of the electronic fence, so that when a user enters the electronic fence, the terminal equipment does not need to execute the control strategy again, and only the equipment identifier and the effective state of the first strategy are provided for the server through the entrance equipment, so that the equipment interaction flow required to be executed when the user enters the electronic fence can be reduced, the waiting time of the user at the entrance equipment is shortened, and the congestion phenomenon at the entrance of the electronic fence is obviously improved.

In a third aspect, an embodiment of the present application provides a terminal device management and control method, which is applied to a server, where the method includes: before a terminal device reaches an entrance device of an electronic fence, receiving a device identifier of the terminal device sent by the terminal device, and a first policy validation state of a management and control policy set for the terminal device in the electronic fence; the first policy validation state is a validation state of the management and control policy obtained by the terminal equipment executing the management and control policy; storing the equipment identifier and the corresponding first policy validation state thereof; after the terminal equipment arrives at the entrance equipment, receiving the equipment identification sent by the entrance equipment; determining the first policy validation state corresponding to the terminal equipment according to the equipment identifier and the corresponding relation between the pre-stored equipment identifier and the first policy validation state; sending the first policy validation state to the portal device, or an admission instruction generated based on the first policy validation state; the access instruction is used for indicating the entrance equipment to allow or reject the user to enter the electronic fence.

In the method, the terminal equipment executes the management and control strategy before reaching the entrance equipment of the electronic fence and sends the effective state of the first strategy to the server, so that when a user enters the electronic fence, the terminal equipment does not need to execute the management and control strategy again and only needs to provide the equipment identifier for the server through the entrance equipment, the equipment interaction flow required to be executed when the user enters the electronic fence can be reduced, the waiting time of the user at the entrance equipment is shortened, and the congestion phenomenon at the entrance of the electronic fence is obviously improved.

In a fourth aspect, an embodiment of the present application provides a terminal device management and control method, which is applied to a server, where the method includes: before a terminal device reaches an entrance device of an electronic fence, receiving a device identifier of the terminal device sent by the terminal device, and a first policy validation state of a management and control policy set for the terminal device in the electronic fence; the first policy validation state is a validation state of the management and control policy obtained by the terminal equipment executing the management and control policy; storing the equipment identifier and the corresponding first policy validation state thereof; after the terminal equipment reaches the entrance equipment, receiving physiological characteristic information of a user sent by the entrance equipment; determining the first policy validation state corresponding to the terminal equipment according to the physiological characteristic information, the pre-stored corresponding relation between the physiological characteristic information and the equipment identifier and the pre-stored corresponding relation between the equipment identifier and the first policy validation state; sending the first policy validation state to the portal device, or an admission instruction generated based on the first policy validation state; the access instruction is used for indicating the entrance equipment to allow or reject the user to enter the electronic fence.

In the method, the terminal equipment executes the management and control strategy before reaching the entrance equipment of the electronic fence and sends the effective state of the first strategy to the server, so that when a user enters the electronic fence, the terminal equipment does not need to execute the management and control strategy again, and the user only needs to provide own physiological characteristic information for the server through the entrance equipment, so that the equipment interaction flow which is required to be executed when the user enters the electronic fence can be reduced, the waiting time of the user at the entrance equipment is shortened, and the congestion phenomenon at the entrance of the electronic fence is obviously improved.

In a fifth aspect, an embodiment of the present application provides a terminal device management and control apparatus configured in a terminal device, where the apparatus includes: the strategy acquisition module is used for acquiring a control strategy set for the terminal equipment in the electronic fence; and the policy execution module is used for executing the control policy before the terminal equipment reaches the entrance equipment of the electronic fence.

In a sixth aspect, an embodiment of the present application provides a terminal device management and control apparatus configured in a server, where the apparatus includes: the electronic fence comprises a first data receiving module, a second data receiving module and a first strategy validation state, wherein the first data receiving module is used for receiving equipment identification of the terminal equipment sent by the entrance equipment after the terminal equipment reaches the entrance equipment of the electronic fence, and the first strategy validation state of a management and control strategy set for the terminal equipment in the electronic fence; the first policy validation state is a validation state of the management and control policy obtained by the terminal equipment executing the management and control policy; and the first data storage module is used for storing the equipment identifier and the corresponding first policy effective state.

In a seventh aspect, an embodiment of the present application provides a terminal device management and control apparatus configured in a server, where the apparatus includes: the second data receiving module is used for receiving the equipment identifier of the terminal equipment sent by the terminal equipment before the terminal equipment reaches the entrance equipment of the electronic fence, and a first strategy validation state of a management and control strategy set for the terminal equipment in the electronic fence; the first policy validation state is a validation state of the management and control policy obtained by the terminal equipment executing the management and control policy; the second data storage module is used for storing the equipment identifier and the corresponding first policy validation state; a third data receiving module, configured to receive, after the terminal device arrives at the ingress device, the device identifier sent by the ingress device; the first data query module is used for determining the first policy effective state corresponding to the terminal equipment according to the equipment identifier and the corresponding relation between the pre-stored equipment identifier and the first policy effective state; the first data sending module is used for sending the first policy validation state to the entrance equipment or generating an admission instruction based on the first policy validation state; the access instruction is used for indicating the entrance equipment to allow or reject the user to enter the electronic fence.

In an eighth aspect, an embodiment of the present application provides a terminal device management and control apparatus configured in a server, where the apparatus includes: a fourth data receiving module, configured to receive, before a terminal device reaches an entry device of an electronic fence, a device identifier of the terminal device sent by the terminal device, and a first policy validation state of a management and control policy set in the electronic fence for the terminal device; the first policy validation state is a validation state of the management and control policy obtained by the terminal equipment executing the management and control policy; the third data storage module is used for storing the equipment identifier and the corresponding first policy effective state; a fifth data receiving module, configured to receive physiological characteristic information of a user sent by the entry device after the terminal device reaches the entry device; the second data query module is used for determining the first policy effective state corresponding to the terminal equipment according to the physiological characteristic information, the pre-stored corresponding relation between the physiological characteristic information and the equipment identifier and the pre-stored corresponding relation between the equipment identifier and the first policy effective state; the second data sending module is used for sending the first policy validation state to the entrance equipment or generating an admission instruction based on the first policy validation state; the access instruction is used for indicating the entrance equipment to allow or reject the user to enter the electronic fence.

In a ninth aspect, embodiments of the present application provide a computer program product comprising computer program instructions which, when read and executed by a processor, perform the method provided by the first aspect, the second aspect, the third aspect, the fourth aspect or any one of the possible implementations of the fourth aspect.

In a tenth aspect, embodiments of the present application provide a computer readable storage medium having stored thereon computer program instructions which, when read and executed by a processor, perform the method provided by the first aspect, the second aspect, the third aspect, the fourth aspect, or any one of the possible implementations of the fourth aspect.

In an eleventh aspect, embodiments of the present application provide an electronic device, including: a memory and a processor, the memory having stored therein computer program instructions which, when read and executed by the processor, perform the method of the first aspect, the second aspect, the third aspect, the fourth aspect or any one of the possible implementations of the fourth aspect.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 to 8 are flowcharts of a terminal device management and control method provided in an embodiment of the present application;

fig. 9 is a block diagram of an electronic device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures.

The terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The terms "first," "second," and the like, are used merely to distinguish one entity or action from another entity or action, and are not to be construed as indicating or implying any actual such relationship or order between such entities or actions.

Before describing the terminal device management and control method provided in the embodiments of the present application, four main bodies may be referred to in the method in brief description, and referring to fig. 1 to 8, the terminal device 100, the user 110, the portal device 120, and the server 130 are respectively (note that not every figure includes these four main bodies).

The terminal device 100 may be held by the user 110, for example, the terminal device 100 may be a mobile phone, a tablet computer, a notebook computer, a wearable device, or the like carried by the user 110.

It should be noted that, in the embodiments of the present application, the user 110 may be considered to refer to a specific person, and in some cases involving the operation of the user 110 to trigger the terminal device 100, since the robot simulation user operation may be preset to replace the actual operation of the user, it is understood that the operation of the user 110 is not limited to the actual operation of the user, and the related behavior achieved by the robot simulation operation is equivalent to the behavior of the user 110, and it is understood that in the following embodiments, the point related to the user 110 may be included in the behavior category of the user 110, where similar effects can be achieved by intelligent means (such as the robot simulation operation, the application program, etc.).

The entrance device 120 is simply referred to as an entrance device of the electronic fence, where the entrance device 120 and an exit device of the electronic fence (may be simply referred to as an exit device) together define a geographic range of the electronic fence, and the entrance device 120 has at least two states, namely, a person-passable state and a person-non-passable state, so that a function of allowing or rejecting the user 110 to enter the electronic fence, referred to as a release function, can be implemented by using the entrance device 120. For example, the access device 120 may be a gate, an automatic door, or the like.

There are at least two implementations of the pass-through function of the entry device 120. One is manual, i.e., it is desirable to have a worker located near the portal device 120 (or can also remotely monitor the location of the portal device 120), the portal device 120 has a module, such as a display, speaker, etc., that can output a prompt, and the worker can manipulate the portal device 120 to allow or deny access to the electronic fence by the user 110 based on the prompt. One is automatic, i.e. the portal device 120 does not require staff coordination, and can itself allow or deny access to the electronic fence by the user 110 or the terminal device 100 based on information provided by the user 110 or based on control instructions issued by the server 130. In comparison, manual inspection of the user 110 entering the electronic fence is more strict, while automatic inspection is more beneficial to saving labor cost.

In addition, since the user 110 must access the inside of the electronic fence through the access device 120, in some implementations, the access device 120 may also be used as an attendance checking device, and the server 130 may be used to implement a function of checking cards in the office, where the user 110 may be an employee in the office.

The portal device 120 has some information gathering capability that behaves differently in different implementations of the portal device 120. For example, the portal device 120 may have a camera that can capture facial images of the user 110; as another example, the portal device 120 may have a fingerprint module that can capture a fingerprint of the user 110; for another example, the portal device 120 may have a two-dimensional code scanning module, which may scan the two-dimensional code on the terminal device 100; as another example, the portal device 120 may have a module (e.g., bluetooth, wiFi) that communicates with the terminal device 100, may receive information sent by the terminal device 100, and so on.

The server 130 is configured to cooperate with the entrance device 120 and the exit device to regulate and control the user 110 (including the terminal device 100 held by the user) entering and exiting the electronic fence, and its specific function will be described later. Server 130 may be in communication with portal device 120 and in some implementations server 130 may also be in communication with terminal device 100.

It should be understood that the server 130 is defined from a functional level, and refers to a device that can provide some specific services to the outside, but it is not limited to whether it is a dedicated server, and the server 130 may be a dedicated server or a device such as a PC that serves as a server.

The scene suitable for the terminal equipment management and control method provided by the embodiment of the application is mainly a scene that the user 110 enters the electronic fence through the entrance equipment 120; the object under control is a terminal device 100 held by a user 110; the aim to be achieved is that when the user 110 enters the electronic fence, on the terminal device 100, the control strategy set in the electronic fence for the user should be in an effective state; the problem to be solved is mainly that when the user 110 enters the electronic fence, the user 110 has to wait for the result that the policy takes effect at the entrance of the electronic fence because the flow of executing the control policy is complex, so that when more users 110 need to enter the electronic fence (for example, factory working) at the same time, the problem of congestion is easy to occur at the entrance device 120; the proposed solution mainly performs the validation operation of the management and control policy on the terminal device 100 in advance, so as to avoid the problems of long time consumption and easy congestion caused by the validation of the management and control policy at the inlet device 120.

The management and control policy may include one or more policies of disabling a camera function of the terminal device 100, disabling a recording function of the terminal device 100, disabling networking of the terminal device 100, and the like, and is mainly used to limit functions of the terminal device 100. For example, these strategies may be applicable to some situations where security and confidentiality are required, such as in factories where high-tech technologies are involved and where compromising activity is very sensitive.

Fig. 1 is a flowchart of a first terminal device management and control method provided in an embodiment of the present application. Referring to fig. 1, the method includes:

step S20: the terminal equipment 100 acquires a control strategy set for the terminal equipment in the electronic fence; before the terminal device 100 reaches the portal device 120, the terminal device 100 executes a policing policy.

Step S20 may be divided into two sub-steps, one sub-step is that the terminal device 100 acquires the policing policy, and the other sub-step is that the terminal device 100 executes the policing policy.

The terminal device 100 executes the management policy to enable the management policy to be successfully validated, but executing the management policy is not always equivalent to that the management policy must be successfully validated (for example, the management policy is to disable the camera, but the camera is occupied by other application programs, so that the camera cannot be disabled). However, in the method of fig. 1, the policing policy must be successfully validated after default execution of the policing policy.

The terminal device 100 may obtain the policing policy in a number of ways. For example, one possible implementation manner is that, before the terminal device 100 executes the management policy, a request for obtaining the management policy (one or more items of content including information of the device and information of the management policy) is sent to the server 130, and after the server 130 receives the request, the management policy corresponding to the request is returned to the terminal device 100. As another possible implementation manner, for example, the management and control policy is preset in an application program on the terminal device 100, for example, the management and control policy is executed by a certain APP installed on the terminal device 100, and the APP is configured with the management and control policy in advance, so that after the terminal device 100 installs the APP, the management and control policy can be read from the local naturally, and so on. The terminal device 100 should execute the policing policy before itself reaches the portal device 120, which condition is equivalent to before the user 110 reaches the portal device 120 or before the terminal device 100 (or the user 110) enters the electronic fence if the terminal device 100 is carried by the user 110. Note that the user 110 may pass through the entrance device 120 when leaving the electronic fence, but the exit device is to be reached by the user 110 at this time, and thus is not considered as the case when the user 110 reaches the entrance device 120.

Triggering the terminal device 100 to execute the management and control policy has at least the following two implementations:

(1) Manual triggering

Before reaching the portal device 120, the user 110 makes a trigger operation on the terminal device 100 (for example, the user may manually or by a robot program simulate clicking a button on an interface, clicking a physical button, issuing a voice command, etc.), and the terminal device 100 executes a control policy, such as disabling its camera function, recording function, networking function, etc., in response to the user 110 trigger operation.

In the manual triggering mode, whether the control strategy is executed or not is completely under the control of the user 110, and the degree of freedom is higher without forcing.

Alternatively, the terminal device 100 may not respond to the trigger operation in any case, and the control policy may be executed only when the trigger operation on the terminal device 100 is detected that the allowable trigger condition is satisfied.

The permission trigger condition may be configured on the terminal device 100 by the user 110 in advance, or may be a default configuration on the terminal device 100, or the like. For example, the allow trigger condition may characterize the user 110 as about to enter the electronic fence. Optionally, the allowed trigger condition includes at least one of the following conditions:

A. The terminal device 100 is at a distance from the entry device 120 less than the first distance threshold

The terminal device 100 is less than a first distance threshold (e.g., 100 meters, 500 meters) from the portal device 120, indicating that the user 110 is relatively close to the portal device 120, indicating that the user 110 is about to enter an electronic fence.

Further, the distance between the terminal device 100 and the entrance device 120 is smaller than the first distance threshold, which is not necessarily that the user 110 is about to enter the electronic fence, but is also possible that the user 110 is about to leave the electronic fence. It is thus also possible to strengthen the condition a, for example to one of the following conditions:

A1. the distance of the terminal device 100 from the portal device 120 is less than the first distance threshold and the distance is continually shrinking (indicating that the user 110 is moving in a direction towards the portal device 120).

A2. The terminal device 100 is less than the first distance threshold from the entry device 120 and the current time is within a period of time that the user 110 is ready to enter the electronic fence (e.g., a period of time that the user 110 should be on duty).

The terminal device 100 may acquire its own location information by means of satellite positioning, cellular network positioning, etc., and the location of the portal device 120 may be configured in advance, so that the terminal device 100 may calculate its distance from the portal device 120.

B. The difference between the current time and the target time for the terminal device 100 to reach the entry device 120 is less than a first time threshold

For example, the target time for the terminal device 100 to reach the entry device 120 may be a time limit (exceeding this time limit belongs to late arrival) for the user 110 holding the terminal device 100 to get on duty, and if the difference between the current time and the target time is smaller than a first time threshold (e.g., 30 minutes, 1 hour) the user 110 may be estimated to be about to get into the electronic fence. Of course, the target time may have other meanings, and is not exemplified.

Obviously, the terminal device 100 may obtain the current time through a network or a local timer, and the target time may be configured in advance, so that the terminal device 100 may calculate the difference between the current time and the target time.

Conditions a and B may also be combined with each other or with other conditions or the allowed trigger condition may also employ conditions other than a and B.

By setting the permission trigger condition so that the terminal device 100 conditionally responds to the trigger operation, it is possible to improve the case where the user 110 erroneously performs the trigger operation. For example, if the user 110 inadvertently triggers execution of the management policy manually at home (at a location far outside the electronic fence), resulting in that certain functions of the terminal device 100 are not used normally, the user 110 may have to contact a system administrator to solve the problem, and if the trigger permission condition is set reasonably so that the condition is not always satisfied at home of the user 110, the problem may be avoided.

(2) Automatic triggering

The terminal device 100 executes the management and control policy when it detects that the automatic trigger condition is satisfied.

The automatic triggering condition may be configured on the terminal device 100 by the user 110 in advance, or may be a default configuration on the terminal device 100, or the like. For example, the automatic trigger condition may characterize that user 110 is about to enter an electronic fence. Optionally, the automatic triggering condition includes at least one of the following conditions:

C. the terminal device 100 is at a distance from the entry device 120 less than the second distance threshold

D. The difference between the current time and the target time for the user 110 to reach the entry device 120 is less than the second time threshold

The implementation of conditions C and D may refer to conditions a and B, respectively, and will not be repeated. It should be noted that the second distance threshold in condition C may be the same as the first distance threshold in condition a, may be different from the first distance threshold in condition a, and the second time threshold in condition D may be the same as the first time threshold in condition B, or may be different from the first time threshold in condition B. Conditions C and D may also be combined with each other or with other conditions, or the auto-triggering condition may also employ conditions other than C and D.

In the automatic triggering mode, the terminal device 100 detects a specific condition by itself to trigger the execution of the management and control policy on the terminal device 100, so that the operation burden of the user 110 can be reduced, and the situations that the user 110 forgets to execute the triggering operation, erroneously executes the triggering operation, and the like can be improved.

For example, if the user 110 inadvertently triggers the validation operation of the management and control policy at home (at a location far outside the electronic fence) by using the manual triggering method, some functions of the terminal device 100 may not be used normally, and the user 110 may have to contact the system administrator to solve the problem, and if the automatic triggering method is used and the automatic triggering condition is set reasonably, so that the condition is not always satisfied at home of the user 110, the problem may be avoided. Of course, a solution supporting both the manual triggering mode and the automatic triggering mode is not excluded.

The terminal device 100 may acquire the control policy before the terminal device 100 executes the control policy, but the terminal device 100 may execute the control policy immediately after acquiring the control policy, or may not execute the control policy immediately after acquiring the control policy, but wait for the terminal device 100 to execute the control policy at a time before reaching the inlet device 120 next time. For example, before the terminal device 100 reaches the portal device 120, a request for acquiring a management policy is transmitted to the server 130 in response to a manual or automatic trigger operation, and the management policy corresponding to the request is received back from the server 130, and then immediately executed. As another example, the day 1 terminal device 100 acquires the policing policy from the server in response to an operation of the user 110 or automatically, and is triggered (manually or automatically) to execute the policing policy until the day 2 terminal device 100 reaches the portal device 120.

Optionally, after the terminal device 100 executes the management policy, the terminal device 100 may further send a state that the terminal device 100 enters the electronic fence to the server 130, where the state indicates that the terminal device 100 executes the management policy, and the server 130 may save the state for later use (how to use the examples described below). It should be noted, however, that at this point the user 110 is not actually entering the electronic fence, and that this state is also not equivalent to the policy validation state of the administration policy. However, if the validation operation of executing the management policy by default must succeed, the state may be equivalent to that the management policy is normally validated, in other words, if the server 130 receives the state of entering the electronic fence sent by the terminal device 100, it may be confirmed that the management policy on the terminal device 100 is normally validated, otherwise, it may be confirmed that the management policy on the terminal device 100 is not validated (the validation operation is not executed).

Step S21: the user 110 provides his own physiological characteristic information to the access device 120.

The physiological characteristic information of the user 110 may include one or more of the face, fingerprint, voiceprint, iris, etc. of the user 110 that may be collected by the portal device 120 for the user 110.

Step S22: the portal device 120 sends physiological characteristic information to the server 130.

After the portal device 120 obtains the physiological characteristic information of the user 110, the information may be forwarded to the server 130, without excluding that in some implementations the portal device 120 may perform certain processing, such as format conversion, on the physiological characteristic information.

Step S23: the server 130 queries the device identifier of the terminal device 100 held by the user 110 according to the physiological characteristic information, and stores the device identifier.

The device identification of the terminal device 100 may be a unique identification of the terminal device 100, such as a device serial number, a hash value generated based on the device serial number, or the like. The correspondence between the physiological characteristic information of the legitimate user (the user qualified to enter the electronic fence) and the device identifier of the terminal device 100 held by the legitimate user is pre-stored on the server 130, so that if the user 110 is legitimate, the server 130 can query the device identifier of the terminal device 100 held by the user 110 according to the physiological characteristic information of the user 110. For example, the server 130 stores the fingerprint and identity information entered by the legal user and the serial number of the terminal device held by the legal user, so that after the server 130 receives the fingerprint of the user 110 collected by the entry device 120, the serial number of the terminal device 100 held by the user 110 can be determined by comparing the fingerprints.

After querying the device identifier of the terminal device 100, the server 130 may save the device identifier as a record of the user 110 entering the electronic fence (if the device identifier is not queried, saving a record is not excluded). Optionally, the record may further include other information, for example, one or more items of information such as the current time (which may be acquired by the server 130 or may be sent by the portal device 120), identity information of the user 110, physiological characteristic information acquired by the user 110 this time, a state that the terminal device 100 enters the electronic fence (sent by the terminal device 100, see step S20), and so on.

S24: the server 130 sends an admission prompt to the portal device 120.

The admittance prompt information includes the inquiry result of the equipment identifier in the step S23, only legal users can inquire the equipment identifier registered in advance, and illegal users (users not allowed to enter the electronic fence) cannot inquire the equipment identifier.

Of course, the admission prompt information may further include more information, such as the queried device identifier, the identity information of the user 110, whether the terminal device 100 has sent the server 130 a status of entering the electronic fence (this status may represent whether the management policy is successfully validated in fig. 1, see step S20), and so on.

S25: the portal device 120 outputs admission prompt information.

After receiving the admission prompt information, the portal device 120 may output all or part of the admission prompt information, where the output mode may be one or more modes of display, voice broadcast, lighting, and the like. After receiving the entry prompt information output by the entry device 120, a worker located at the entry device 120 may control the entry device 120 to allow or deny the user 110 to enter the electronic fence according to the information content.

If the admission prompt indicates that the identity of user 110 is legitimate, user 110 is allowed to enter the interior of the electronic fence. Note that in some implementations it is not necessary at this point to verify again whether the policing policies on the terminal device 100 are valid properly. For example, the execution of the management policy is automatically triggered, and only the terminal device 100 of the legitimate user has the triggering function (for example, the function can be started only after the user 110 logs in the APP installed on the terminal device 100), and since the default validation operation in fig. 1 is necessarily successfully executed, the management policy in the terminal device 100 of the legitimate user 110 must be validated when the legitimate user reaches the entry device 120, and the query result of the device identifier contained in the admission information by the illegitimate user 110 can be excluded.

It is not excluded that in some implementations, the management policy on the terminal device 100 will be verified whether it is normally validated, for example, if the server 130 finds that the user 110 is legal when querying the device identifier of the terminal device 100, but the terminal device 100 held by the server 130 has not previously sent the terminal device 100 to enter the electronic fence, that is, the management policy has not been executed, the information (the state that the terminal device 100 has not sent the terminal device 100 to the server 130 to enter the electronic fence) may be included in the admission prompt information, and after the staff at the entrance device 120 knows the information, the user 110 will not be allowed to enter the electronic fence. At this point, user 110 may attempt to manually trigger terminal device 100 to execute the administration strategy (if terminal device 100 supports manual triggering) in order to enter the electronic fence.

If the entry hint information indicates that the identity of the user 110 is not legitimate, the user 110 may attempt to swipe the face again, fingerprint, etc. at the entry device 120 in order to enter the electronic fence.

There are different implementations of steps S24 to S25, for example, instead of sending the admission prompt information to the portal device 120, the server 130 may send an admission instruction to the portal device 120, where the admission instruction is used to instruct the portal device 120 to allow or deny the user 110 to enter the electronic fence, and the portal device 120 may implement a function of allowing or denying the user 110 to enter the electronic fence by running the instruction after receiving the admission instruction. It should be appreciated that the admission instructions and admission prompts are consistent in the outcome of allowing or denying the user 110 to the electronic fence, except that the admission instructions are provided to the machine (portal device 120) and the admission prompts are provided to the staff, so that they differ in form and therefore are not explained again as to how the admission instructions are generated.

In contrast, if the implementation of steps S24-S25 is adopted, the user 110 is more tightly controlled because the process of entering the electronic fence by the user 110 is manually confirmed. With the alternative implementation described above, no personnel may be deployed at the access device 120, thereby reducing the labor cost of managing the electronic enclosure.

In the method of fig. 1, since the terminal device 100 executes the control policy before the user 110 reaches the entrance device 120 of the electronic fence, which is equivalent to making the terminal device 100 in a state of entering the electronic fence in advance, when the user 110 holding the terminal device 100 enters the electronic fence, the terminal device 100 does not need to execute the control policy again, only the user 110 needs to provide the physiological characteristic information to the server 130 through the entrance device 120, so that the device interaction flow (the server 130 does not need to interact directly with the terminal device 100) required to be executed when the user 110 enters the electronic fence can be reduced, the waiting time of the user 110 at the entrance device 120 is shortened, and the congestion phenomenon at the entrance of the electronic fence is significantly improved.

Note that although the default in setting forth the method of fig. 1 is that the terminal device 100 will perform the policing policy will necessarily be successfully validated, even if this limitation is removed, since the probability of the terminal device 100 performing the policing policy but not being successfully validated is low, even if it takes a little longer to handle these abnormal situations, it is still a necessary effect in a statistical sense to save the waiting time of the user 110 at the portal device 120, and reference is made to the following examples.

Fig. 2 is a flowchart of a second method for controlling a terminal device 100 according to an embodiment of the present application.

Referring to fig. 2, the method includes:

step S30: the terminal equipment 100 acquires a control strategy set for the terminal equipment in the electronic fence; before the terminal device 100 reaches the portal device 120, the terminal device 100 executes a policing policy.

Reference is made to step S20, and the description is not repeated.

Step S31: the terminal device 100 provides its own device identification to the portal device 120.

There are various ways in which the terminal device 100 provides the device identification. For example, the terminal device 100 may generate first scan information for the portal device 120 to scan, the first scan information including a device identification of the terminal device 100. For example, the first scan information may be a two-dimensional code, where the generation timing of the two-dimensional code may be generated when the terminal device 100 arrives at the entry device 120 (when the user 110 presents the two-dimensional code), or may be generated before the terminal device 100 arrives at the entry device 120, or may be generated even before the step S30 is performed (if the two-dimensional code includes only the device identifier, it is obvious that whether the step S30 is performed does not affect the generation of the two-dimensional code).

For another example, the terminal device 100 may send a device identification to the portal device 120 after reaching the portal device 120 itself. Of course, before this, the terminal device 100 needs to first establish a communication connection (e.g. a bluetooth connection, a WiFi connection) with the portal device 120, and may also perform a certain interaction with the portal device 120. For example, the terminal device 100 may send a device identification to the portal device 120 upon request.

Step S32: the portal device 120 sends the device identification to the server 130.

After the portal device 120 obtains the device identification of the terminal device 100, the device identification may be forwarded to the server 130, without excluding that in some implementations the portal device 120 may perform certain processing on the device identification, such as format conversion, etc.

Step S33: the server 130 compares and saves the device identification.

The server 130 stores in advance some registered device identifiers of the terminal devices 100, and the user 110 holding the terminal devices 100 is a legal user (a user qualified to enter an electronic fence), and the server 130 may store identity information of the legal user. The server 130 compares the newly obtained device identifier with the device identifiers stored in advance to determine whether the terminal device 100 held by the user 110 is a registered device, which is equivalent to determining whether the user 110 is a legal user.

If, during the comparison, the device identifier received by the server 130 from the portal device 120 matches a registered device identifier, the server 130 may save the device identifier as a record of the user 110 entering the electronic fence (if the device identifier does not match, it is not excluded to save a record). Optionally, the record may further include other information, for example, one or more of current time, identity information of the user 110, a status of the terminal device 100 entering the electronic fence, and the like.

Step S34: the server 130 sends an admission prompt to the portal device 120.

The admission prompt information includes the comparison result of the device identifier in step S33, and only the devices held by the legal users can be successfully compared, and the devices held by the illegal users (users who do not qualify for entering the electronic fence) can be failed to be compared.

Of course, the admission prompt information may also include more information, such as a matched device identifier, identity information of the user 110, whether the terminal device 100 has sent to the server 130 a status of entering an electronic fence, and so on.

Step S35: the portal device 120 outputs admission prompt information.

This step can be referred to as step S25 and will not be repeated. There are also different implementations of steps S35-S36, for example, instead of sending an admission prompt to the portal device 120, the server 130 may send an admission instruction to the portal device 120, where the admission instruction is used to instruct the portal device 120 to allow or deny the user 110 to enter the electronic fence.

In the method of fig. 2, since the terminal device 100 executes the management and control policy before the user 110 reaches the entrance device 120 of the electronic fence, the terminal device 100 is in a state of entering the electronic fence in advance, so that when the user 110 enters the electronic fence, the terminal device 100 does not need to execute the management and control policy again, only needs to provide the device identifier of the terminal device to the server 130 through the entrance device 120, thus reducing the device interaction flow (the server 130 does not need to interact directly with the terminal device 100) required to be executed when the user 110 enters the electronic fence, shortening the waiting time of the user 110 at the entrance device 120, and significantly improving the congestion phenomenon at the entrance of the electronic fence.

Note that although the default in setting forth the method of fig. 2 is that the terminal device 100 will perform the policing policy will necessarily be successfully validated, even if this limitation is removed, since the probability of the terminal device 100 performing the policing policy but not being successfully validated is low, even if it takes a little longer to handle these abnormal situations, it is still a necessary effect in a statistical sense to save the waiting time of the user 110 at the portal device 120, and reference is made to the following examples.

Compared with the method in fig. 1, the method in fig. 2 replaces the physiological characteristic information of the user 110 with the device identifier, which is beneficial to protecting the privacy of the user 110, and does not need to deploy an identity recognition algorithm (e.g. face recognition, fingerprint recognition algorithm) on the server 130, so that the processing efficiency is higher. But the advantage of using physiological characteristic information is that it is safer to ensure that indeed the user 110 himself (and not the other person carrying the terminal device 100 of the user 110) enters the electronic fence. In some implementations, the methods of fig. 1 and 2 may also be combined, i.e. both physiological characteristic information of the user 110 and the device identification of the terminal device 100 are provided to the portal device 120.

Fig. 3 is a flowchart of a third method for controlling a terminal device 100 according to an embodiment of the present application.

Referring to fig. 3, the method includes:

step S40: the terminal equipment 100 acquires a control strategy set for the terminal equipment in the electronic fence; before the terminal device 100 reaches the portal device 120, the terminal device 100 performs an validating operation of the management policy, and obtains a first policy validating state.

The first policy validation state at least comprises two states, one is that the policy is validated normally, namely that the management and control policy is validated successfully, and the other is that the policy is not validated normally, namely that all or part of the management and control policies are not validated successfully. This step may refer to step S30, except that in the method of fig. 2, since the default management and control policy must be successfully validated, the validation state of the management and control policy is not intentionally obtained in step S30.

Optionally, if the first policy validation state is not normally validated, the terminal device 100 may attempt to repeatedly execute the validation operation of the management and control policy locally, where the first policy validation state obtained in step S40 may also be understood as the policy validation state obtained in the last retry.

Step S41: the terminal device 100 provides the portal device 120 with its own device identification and the first policy validation state.

This step may refer to step S31, and there are various ways in which the terminal device 100 provides the device identification and the first policy validation state. For example, the terminal device 100 may generate first scan information for the portal device 120 to scan, the first scan information including a device identification of the terminal device 100 and a first policy validation state. For another example, the terminal device 100 may send the device identification and the first policy validation state to the portal device 120 after the user 110 arrives at the portal device 120.

Step S42: the portal device 120 outputs a first policy validation state.

The portal device 120 may output the first policy validation status in one or more manners such as display, voice broadcast, lighting, etc., which does not exclude the portal device 120 from outputting other information, such as device identification, etc. After receiving the first policy validation state output by the portal device 120, the staff member located at the portal device 120 may operate the portal device 120 to allow or deny the user 110 to enter the electronic fence according to the first policy validation state: for example, if the first policy validation state is in a normal validation state, the portal device 120 is controlled to allow the user 110 to enter the electronic fence, if the first policy validation state is not in a normal validation state, the portal device 120 is controlled to reject the user 110 from entering the electronic fence (if the portal device 120 is in a personnel non-passable state, the operation of the personnel may be omitted).

In an alternative, the portal device 120 can automatically allow or deny the user 110 access to the electronic fence based on the first policy validation state.

As can be seen from comparing fig. 2, since the device identification is not transmitted to the server 130 at this time, it is not possible to determine whether the device identification corresponds to a legitimate user through the server 130, but in this case, it is still a viable solution to allow the user 110 to enter the electronic fence. For example, the user 110 must log in to a certain APP installed on the terminal device 100 to generate a two-dimensional code (first scan information) identifiable by the portal device 120, and obviously, an illegal user cannot log in to the APP, or cannot provide the two-dimensional code, or the two-dimensional code provided by the APP is not identifiable by the portal device 120, by which the validity of the user 110 can be ensured.

According to the above analysis, in an alternative manner of the method in fig. 2, steps S34 to S35 may be omitted, and after obtaining the device identifier provided by the terminal device 100, the portal device 120 directly releases the user 110 (by manual or automatic manner), and the capability of providing the device identifier itself is utilized to ensure the validity of the user 110, where in step S33, it is not necessary to perform the comparison of the device identifier.

Of course, conversely, the device identifier comparison in step S33, step S34, and step S35 may be combined into the method of fig. 3, and the server 130 may ensure the validity of the user 110, where the first policy valid state may still be output in step S42, but the user 110 may not be directly released, or step S42 may be omitted, and the first policy valid state may be output in the admission prompt information when step S35 is executed.

Step S43: the portal device 120 sends the device identification and the first policy validation state to the server 130.

After obtaining the device identifier and the first policy validation state of the terminal device 100, the portal device 120 may forward the device identifier and the first policy validation state to the server 130, without excluding that in some implementations, the portal device 120 may perform certain processing, such as format conversion, on the device identifier and the first policy validation state.

Step S44: the server 130 maintains the device identification and the first policy validation state.

Server 130 may save the received device identification and the first policy validation state as a record of the entry of user 110 into the electronic fence. Optionally, the record may further include other information, for example, one or more of current time, identity information of the user 110, a status of the terminal device 100 entering the electronic fence, and the like.

In the method of fig. 3, since the terminal device 100 executes the management and control policy before the user 110 reaches the entrance device 120 of the electronic fence, the terminal device 100 is in a state of entering the electronic fence in advance, so that when the user 110 enters the electronic fence, the terminal device 100 does not need to execute the management and control policy again, and only needs to provide the device identifier of the terminal device and the effective state of the first policy to the server 130 through the entrance device 120, so that the device interaction flow required to be executed when the user 110 enters the electronic fence can be reduced, the waiting time of the user 110 at the entrance device 120 is shortened, and the congestion phenomenon at the entrance of the electronic fence is significantly improved.

The data transmission flow in fig. 3 is simply analyzed, and the flow is unidirectional (from the terminal device 100 to the portal device 120 to the server 130), so that the processing efficiency is high. In contrast, if the terminal device 100 does not execute the management and control policy first, but executes the management and control policy under the instruction of the server 130 after the user 110 reaches the portal device 120, the server 130 needs to issue a control instruction for executing the management and control policy to the terminal device 100, and after obtaining the policy validation state of the management and control policy, the terminal device 100 needs to return the policy validation state to the server 130, and the server 130 returns the state to the portal device 120, so that the portal device 120 or a staff at the portal device 120 can allow or prohibit the user 110 from entering the electronic fence, and the data processing flow is lengthy and the processing efficiency is low.

Fig. 4 is a flowchart of a fourth method for controlling the terminal device 100 according to the embodiment of the present application.

Referring to fig. 4, the method includes:

step S50: the terminal equipment 100 acquires a control strategy set for the terminal equipment in the electronic fence; before the terminal device 100 reaches the portal device 120, the terminal device 100 performs an validating operation of the management policy, and obtains a first policy validating state.

This step is referred to step S40 and will not be repeated.

Step S51: the terminal device 100 transmits its device identification and the first policy validation state to the server 130.

Note that step S51 is performed immediately after step S50, and so may also be considered to be performed before the terminal device 100 reaches the entry device 120.

Step S52: the server 130 maintains the device identification and the first policy validation state.

Note that this step is not necessarily identical in implementation to step S44, because the purpose of saving the device identifier and the first policy validation state in step S44 is mainly to record the behavior of the user 110 entering the electronic fence, and the purpose of saving the device identifier and the first policy validation state in step S52 is mainly to store the correspondence therebetween, so that the query in step S55 is facilitated. Moreover, the timing of execution of step S52 and step S44 is also different, so that the data to be saved is not necessarily the same (refer to data other than the device identification and the first policy validation state, such as the current time).

Step S53: the terminal device 100 provides its own device identification to the portal device 120.

Step S54: the portal device 120 sends the device identification to the server 130.

The above two steps can be referred to steps S31 to S32, and will not be repeated.

Step S55: the server 130 queries the first policy validation state corresponding to the terminal device 100 held by the user 110 according to the device identifier.

The server 130 may query the first policy validation state corresponding to the terminal device 100 held by the user 110 according to the device identifier received from the portal device 120 and the correspondence between the device identifier and the first policy validation state stored in step S52. After step S55 is performed, the server 130 may generate a record (if the first policy validation state is not queried, and the record is not saved) that the user 110 enters the electronic fence, where the record may be a new record, or the content saved in step S52 may be used, but necessary information may be added or updated in the record, such as the current time, etc.

Step S56: the server 130 sends a first policy validation state to the portal device 120.

Step S57: the portal device 120 outputs a first policy validation state.

The above two steps can refer to steps S34 to S35, only the admission prompt information is replaced by the first policy validation state, or the first policy validation state itself can be regarded as an admission prompt information (if the first policy validation state is in normal validation, the user 110 is allowed to enter the electronic fence, if the first policy validation state is not in normal validation, the user 110 is refused to enter the electronic fence), and the rest of details are not repeated.

There are also different implementations of steps S56-S57, for example, instead of sending the first policy validation state to the portal device 120, the server 130 may send an admission instruction to the portal device 120, which is generated based on the first policy validation state, for instructing the portal device 120 to allow or deny the user 110 to enter the electronic fence. It should be appreciated that the admission instructions and the first policy validation state are consistent in the outcome of allowing or denying the user 110 to enter the electronic fence, except that the admission instructions are provided to the machine (the portal device 120) and the first policy validation state is provided to the staff, so that the forms differ.

Further, in addition to the first policy validation state, the server 130 may also send other information to the portal device 120, such as a device identifier matched to the server 130 (if the server 130 is to perform device identifier comparison), identity information of the user 110, whether the terminal device 100 has sent a state of entering an electronic fence to the server 130, and so on.

In the method of fig. 4, since the terminal device 100 executes the management and control policy before the user 110 reaches the entrance device 120 of the electronic fence, which is equivalent to making the terminal device 100 in a state of entering the electronic fence in advance, when the user 110 enters the electronic fence, the terminal device 100 does not need to execute the management and control policy again, but only needs to provide the device identifier of the terminal device 100 to the server 130 through the entrance device 120 (the first policy effective state is sent to the server 130 by the terminal device 100 in advance), so that the device interaction flow required to be executed when the user 110 enters the electronic fence can be reduced, the waiting time of the user 110 at the entrance device 120 is shortened, and the congestion phenomenon at the entrance of the electronic fence is significantly improved.

Although the data transmission flow in fig. 4 is more complicated than that in fig. 3, it should be noted that, because the first policy validation state is sent to the server 130 by the terminal device 100 in advance, rather than the terminal device 100 executing the control policy under the instruction of the server 130 after the user 110 arrives at the portal device 120, the policy validation state is sent to the server 130, that is, after the user 110 arrives at the portal device 120, no direct interaction is required between the server 130 and the terminal device 100, and the data processing efficiency is still relatively high.

Fig. 5 is a flowchart of a fifth method for controlling a terminal device 100 according to an embodiment of the present application.

Referring to fig. 5, the method includes:

step S60: the terminal equipment 100 acquires a control strategy set for the terminal equipment in the electronic fence; before the terminal device 100 reaches the portal device 120, the terminal device 100 performs an validating operation of the management policy, and obtains a first policy validating state.

Step S61: the terminal device 100 transmits its device identification and the first policy validation state to the server 130.

Step S62: the server 130 maintains the device identification and the first policy validation state.

The above three steps can be referred to steps S50 to S52, and will not be repeated.

Step S63: the user 110 provides his own physiological characteristic information to the access device 120.

Step S64: the portal device 120 sends physiological characteristic information to the server 130.

The above two steps can be referred to steps S21 to S22, and will not be repeated.

Step S65: the server 130 queries the first policy validation state corresponding to the terminal device 100 held by the user 110 according to the physiological characteristic information.

The server 130 may query the first policy validation state corresponding to the terminal device 100 held by the user 110 according to the physiological characteristic information received from the portal device 120, the correspondence between the pre-stored physiological characteristic information and the device identifier, and the correspondence between the device identifier and the first policy validation state stored in step S52. The known correspondence between the physiological characteristic information and the device identifier, and the correspondence between the device identifier and the first policy validation state are equivalent to the known correspondence between the physiological characteristic information and the first policy validation state, so that the query can be performed based on the physiological characteristic information of the user 110 provided by the access device 120, and this step can refer to step S23 and step S55.

After step S65 is performed, the server 130 may generate a record (if the first policy validation state is not queried, a record is not excluded from being saved) that the user 110 enters the electronic fence, where the record may be a new record, or the content saved in step S62 may be used, but necessary information may be added or updated therein, such as physiological characteristic information of the user 110, current time, and so on.

Step S66: the server 130 sends a first policy validation state to the portal device 120.

Step S67: the portal device 120 outputs a first policy validation state.

The above two steps can be referred to steps S56 to S57, and will not be repeated. There are also different implementations of steps S66-S67, for example, instead of sending the first policy validation state to the portal device 120, the server 130 may send an admission instruction to the portal device 120, which is generated based on the first policy validation state, for instructing the portal device 120 to allow or deny the user 110 to enter the electronic fence.

In the method of fig. 5, since the terminal device 100 executes the management and control policy before the user 110 reaches the entrance device 120 of the electronic fence, which is equivalent to making the terminal device 100 in a state of entering the electronic fence in advance, when the user 110 enters the electronic fence, the terminal device 100 does not need to execute the management and control policy again, and the user 110 only needs to provide own physiological characteristic information to the server 130 through the entrance device 120 (the first policy effective state is sent to the server 130 by the terminal device 100 in advance), so that the device interaction flow required to be executed by the user 110 when entering the electronic fence can be reduced, the waiting time of the user 110 at the entrance device 120 is shortened, and the congestion phenomenon at the entrance of the electronic fence is significantly improved.

Although the data transmission flow in fig. 5 is more complicated than that in fig. 3, it should be noted that, because the first policy validation state is sent to the server 130 by the terminal device 100 in advance, rather than the terminal device 100 executing the control policy under the instruction of the server 130 after the user 110 arrives at the portal device 120, the policy validation state is sent to the server 130, that is, after the user 110 arrives at the portal device 120, no direct interaction is required between the server 130 and the terminal device 100, and the data processing efficiency is still relatively high.

The methods of fig. 4 and 5 may also be combined, i.e. both the physiological characteristic information of the user 110 and the device identification of the terminal device 100 are provided to the portal device 120.

The method in fig. 3-5 is mainly to add a first policy validation state in the process flow compared to the method in fig. 1-2, where the first policy validation state can be used to identify whether the terminal device 100 validates the management policy normally, so that relevant parties can decide whether to allow the user 110 to enter the electronic fence based on the first policy validation state, or take corresponding measures (e.g. try to validate the management policy again later), which is beneficial to implement more strict management control on the user 110 entering the fence.

In some implementations, for the methods in fig. 3 to 5, if the first policy validation state is not validated normally, the server 130 may instruct the terminal device 100 to attempt to validate the management and control policy again, so as to improve the problem that the management and control policy is not validated normally due to accidental factors, so that the user 110 can enter the electronic fence normally. Correspondingly, the methods in fig. 6 to 8 can be derived.

Fig. 6 is a flowchart of a sixth method for managing and controlling a terminal device 100 according to an embodiment of the present application. The method of fig. 6 may be combined with the method of fig. 3, after step S43 of the method of fig. 3, but it is not excluded that the method of fig. 6 and the method of fig. 4 are combined, after step S55 of the method of fig. 4, or that the method of fig. 6 and the method of fig. 5 are combined, after step S65 of the method of fig. 5. Referring to fig. 6, the method includes:

step S70: if the server 130 determines that the first policy validation state is not validated normally, a policy execution instruction is sent to the terminal device 100.

The policy execution instruction is used to instruct the terminal device 100 to execute the management policy, and does not exclude that the policy execution instruction includes the management policy itself that needs to be validated.

Step S71: the terminal device 100 runs the policy execution instruction to obtain a second policy validation state of the management and control policy.

This step may refer to step S40, except that step S40 is that the terminal device 100 actively executes the policing policy and is executed before the terminal device 100 reaches the portal device 120, step S71 is that the terminal device 100 executes the policing policy under the direction of the server 130, and step S71 is executed after the terminal device 100 reaches the portal device 120. Similar to the first policy validation state, the second policy validation state includes at least two states, one being normally validated and one not being normally validated.

Step S72: the terminal device 100 provides its own device identification and a second policy validation state to the portal device 120.

Step S73: the portal device 120 outputs a second policy validation state.

Step S74: the portal device 120 sends the device identification and the second policy validation state to the server 130.

Step S75: the server 130 maintains the device identification and the second policy validation state.

The above four steps can be referred to steps S41 to S44, and will not be repeated. It is noted that if the device identification and the first policy validation state have been saved in step 44, then only the first policy validation state may be updated to the second policy validation state in step S75.

Fig. 7 is a flowchart of a seventh method for managing and controlling a terminal device 100 according to an embodiment of the present application. The method of fig. 7 may be combined with the method of fig. 4, after step S55 of the method of fig. 4, but it is not excluded that the method of fig. 7 and the method of fig. 3 are combined, after step S43 of the method of fig. 3, or that the method of fig. 7 and the method of fig. 5 are combined, after step S65 of the method of fig. 5. Referring to fig. 7, the method includes:

step S80: if the server 130 determines that the first policy validation state is not validated normally, a policy execution instruction is sent to the terminal device 100. The policy execution instruction is used to instruct the terminal device 100 to execute the management policy.

Step S81: the terminal device 100 runs the policy execution instruction to obtain the second policy validation state.

Step S82: the terminal device 100 transmits its own device identification and the second policy validation state to the server 130.

Step S83: the server 130 maintains the device identification and the second policy validation state.

Step S84: the terminal device 100 provides its own device identification to the portal device 120.

Step S85: the portal device 120 sends the device identification to the server 130.

Step S86: the server 130 queries the second policy validation state corresponding to the terminal device 100 held by the user 110 according to the device identifier and the correspondence between the pre-stored device identifier and the second policy validation state. Wherein, the correspondence between the device identifier and the second policy validation state is saved in step S83.

Step S87: the server 130 sends a second policy validation state to the portal device 120.

Step S88: the portal device 120 outputs a second policy validation state.

Steps S81 to S88 can refer to steps S50 to S57, and will not be repeated. There are also different implementations of steps S87-S88, for example, instead of sending the second policy validation state to the portal device 120, the server 130 may send an admission instruction to the portal device 120, which is generated based on the second policy validation state, for instructing the portal device 120 to allow or deny the user 110 to enter the electronic fence.

Fig. 8 is a flowchart of an eighth method for managing and controlling the terminal device 100 according to an embodiment of the present application. The method of fig. 8 may be combined with the method of fig. 5, after step S65 of the method of fig. 5, but it is not excluded that the method of fig. 8 and the method of fig. 3 are combined, after step S43 of the method of fig. 3, or that the method of fig. 8 and the method of fig. 4 are combined, after step S55 of the method of fig. 4. Referring to fig. 8, the method includes:

step S90: if the server 130 determines that the first policy validation state is not validated normally, a policy execution instruction is sent to the terminal device 100. The policy execution instruction is used to instruct the terminal device 100 to execute the management policy.

Step S91: the terminal device 100 runs the policy execution instruction to obtain the second policy validation state.

Step S92: the terminal device 100 transmits its own device identification and the second policy validation state to the server 130.

Step S93: the server 130 maintains the device identification and the second policy validation state.

Step S94: the user 110 provides his own physiological characteristic information to the access device 120.

Step S95: the portal device 120 sends physiological characteristic information to the server 130.

Step S96: the server 130 queries the second policy validation state corresponding to the terminal device 100 held by the user 110 according to the physiological characteristic information, the pre-stored correspondence between the physiological characteristic information and the device identifier, and the pre-stored correspondence between the device identifier and the second policy validation state. Wherein, the correspondence between the device identifier and the second policy validation state is saved in step S93.

Step S97: the server 130 sends a second policy validation state to the portal device 120.

Step S98: the portal device 120 outputs a second policy validation state.

Steps S91 to S98 may refer to steps S60 to S67, and will not be repeated. There are also different implementations of steps S97-S98, for example, instead of sending the second policy validation state to the portal device 120, the server 130 may send an admission instruction to the portal device 120, which is generated based on the second policy validation state, for instructing the portal device 120 to allow or deny the user 110 to enter the electronic fence.

In addition to the foregoing, the methods in fig. 6 to 8 can improve the problem that the management and control policy is not normally effective due to accidental factors, and also can be compatible with the situation that the terminal device 100 does not execute the management and control policy in advance. For example, if the execution of the management policy is manually triggered, but the user 110 does not trigger before reaching the portal device 120, taking fig. 3 as an example, step S40 is not executed, but the first policy validation state may still be sent and the value thereof is set to be not normally validated when step S41 is executed, so that after step S43 is executed, the execution of the management policy is triggered in step 70, and finally the execution of the management policy on the terminal device 100 is triggered (step S71). Similar analysis is possible for the cases of fig. 4 and 5.

In addition, the method in fig. 6 to 8 is retried by policy validation, so that the efficiency of the user 110 passing through the electronic fence is necessarily reduced to a certain extent, but research shows that the probability that the first policy validation state is not validated normally is extremely low, so that the method in fig. 6 to 8 is rarely executed, and the overall efficiency of a large number of users 110 passing through the electronic fence is very limited in a statistical sense.

Further, the method in fig. 6 to 8 only shows a case of one retry, and if multiple retries are performed, similar analysis is possible, and description will not be repeated.

The method embodiments in fig. 1 to 8 can be referred to each other, and details not mentioned in the latter embodiments can be referred to similar steps in the former embodiments.

The embodiment of the application also provides a terminal equipment management and control device, which is configured in the terminal equipment and comprises:

the strategy acquisition module is used for acquiring a control strategy set for the terminal equipment in the electronic fence;

and the policy execution module is used for executing the control policy before the terminal equipment reaches the entrance equipment of the electronic fence.

In an implementation manner of the terminal device management and control apparatus, the policy obtaining module obtains a management and control policy set for the terminal device in the electronic fence, including: before the terminal equipment reaches the entrance equipment, a request for acquiring the control strategy is sent to a server, and the control strategy corresponding to the request returned by the server is received; the policy enforcement module enforces the management and control policy, including: in response to receiving the policing policy from the server, the policing policy is executed.

In one implementation manner of the terminal device management and control apparatus, the policy execution module executes the management and control policy before the terminal device reaches the entrance device of the electronic fence, where the policy execution module includes: and before the terminal equipment reaches the entrance equipment of the electronic fence, responding to the triggering operation on the terminal equipment, and executing the control strategy.

In one implementation manner of the terminal device management and control apparatus, the policy execution module executes the management and control policy in response to a trigger operation on the terminal device, and includes: and when the condition that the permission triggering condition is met is detected, responding to the triggering operation on the terminal equipment, and executing the control strategy.

In one implementation manner of the terminal device management and control apparatus, the allowed triggering condition includes at least one of the following conditions: the distance between the terminal equipment and the entrance equipment is smaller than a first distance threshold value; the difference between the current time and the target time for the terminal device to reach the entry device is less than a first time threshold.

In one implementation manner of the terminal device management and control apparatus, the policy execution module executes the management and control policy before the terminal device reaches the entrance device of the electronic fence, where the policy execution module includes: and executing the effective operation of the control strategy when the terminal equipment detects that the automatic triggering condition is met before reaching the entrance equipment of the electronic fence.

In one implementation manner of the terminal device management and control apparatus, the automatic triggering condition includes at least one of the following conditions: the distance between the terminal equipment and the entrance equipment is smaller than a second distance threshold value; the difference between the current time and the target time for the user to reach the entry device is less than a second time threshold.

In one implementation manner of the terminal device management and control apparatus, the policy validation module is further configured to perform the following operations: generating first scanning information for the portal equipment to scan, wherein the first scanning information comprises equipment identification of the terminal equipment; or after the terminal equipment arrives at the entrance equipment, the equipment identification is sent to the entrance equipment.

In one implementation manner of the terminal device management and control apparatus, the policy execution module is further configured to, after executing the management and control policy, perform the following operations: acquiring a first strategy effective state of the management and control strategy; the first scan information further includes the first policy validation state; or after the terminal device reaches the entrance device, the first policy validation state is further sent to the entrance device; or sending the device identification and the first policy validation state to a server.

In one implementation manner of the terminal device management and control apparatus, the first policy validation state is used for outputting on the portal device, or is used as a basis for allowing or rejecting the portal device to allow the user to enter the electronic fence.

In one implementation manner of the terminal device management and control apparatus, the first policy validation state is not validated normally, and the policy validation module is further configured to perform the following operations: receiving a policy execution instruction sent by a server, wherein the policy execution instruction is used for indicating the terminal equipment to execute the management and control policy; operating the strategy execution instruction to obtain a second strategy effective state of the management and control strategy; generating second scanning information for the portal device to scan, wherein the second scanning information comprises the device identification and the second policy validation state; or sending the device identification and the second policy validation state to the portal device; or sending the device identification and the second policy validation to the server.

The foregoing implementation principles and the technical effects of the terminal device management and control device provided in the embodiments of the present application have been described in the foregoing method embodiments, and for the sake of brevity, reference may be made to corresponding contents in the method embodiments where the device embodiment portion is not mentioned.

The embodiment of the application also provides a terminal equipment management and control device configured on a server, the device comprises:

the electronic fence comprises a first data receiving module, a second data receiving module and a first strategy validation state, wherein the first data receiving module is used for receiving equipment identification of the terminal equipment sent by the entrance equipment after the terminal equipment reaches the entrance equipment of the electronic fence, and the first strategy validation state of a management and control strategy set for the terminal equipment in the electronic fence; the first policy validation state is a validation state of the management and control policy obtained by the terminal equipment executing the management and control policy;

and the first data storage module is used for storing the equipment identifier and the corresponding first policy effective state.

In one implementation manner of the terminal device management and control apparatus, the apparatus further includes: the first instruction issuing module is used for sending a policy execution instruction to the terminal equipment when the first policy effective state is not in normal effect, wherein the policy execution instruction is used for indicating the terminal equipment to execute the management and control policy; the first data receiving module is further configured to receive the device identifier and a second policy validation state sent by the ingress device; the second policy validation state is a validation state of the management and control policy obtained by the terminal equipment running the policy execution instruction; the first data storage module is further configured to store the device identifier and the corresponding first policy validation state.

The foregoing implementation principles and the technical effects of the terminal device management and control device provided in the embodiments of the present application have been described in the foregoing method embodiments, and for the sake of brevity, reference may be made to corresponding contents in the method embodiments where the device embodiment portion is not mentioned.

The embodiment of the application also provides a terminal equipment management and control device configured on a server, the device comprises:

the second data receiving module is used for receiving the equipment identifier of the terminal equipment sent by the terminal equipment before the terminal equipment reaches the entrance equipment of the electronic fence, and a first strategy validation state of a management and control strategy set for the terminal equipment in the electronic fence; the first policy validation state is a validation state of the management and control policy obtained by the terminal equipment executing the management and control policy;

the second data storage module is used for storing the equipment identifier and the corresponding first policy validation state;

a third data receiving module, configured to receive, after the terminal device arrives at the ingress device, the device identifier sent by the ingress device;

the first data query module is used for determining the first policy effective state corresponding to the terminal equipment according to the equipment identifier and the corresponding relation between the pre-stored equipment identifier and the first policy effective state;

The first data sending module is used for sending the first policy validation state to the entrance equipment or generating an admission instruction based on the first policy validation state; the access instruction is used for indicating the entrance equipment to allow or reject the user to enter the electronic fence.

In one implementation manner of the terminal device management and control apparatus, the apparatus further includes: the second instruction issuing module is used for sending a policy execution instruction to the terminal equipment when the first policy validation state is not normally validated, wherein the policy execution instruction is used for indicating the terminal equipment to execute the validation operation of the management and control policy; the second data receiving module is further configured to receive the device identifier and a second policy validation state sent by the terminal device; the second policy validation state is a validation state of the management and control policy obtained by the terminal equipment running the policy execution instruction; the second data storage module is further configured to store the device identifier and the corresponding second policy validation state; the first data sending module is further configured to send the second policy validation state to the ingress device, or an admission instruction generated based on the second policy validation state; the access instruction is used for indicating the entrance equipment to allow or reject the user to enter the electronic fence.

The foregoing implementation principles and the technical effects of the terminal device management and control device provided in the embodiments of the present application have been described in the foregoing method embodiments, and for the sake of brevity, reference may be made to corresponding contents in the method embodiments where the device embodiment portion is not mentioned.

The embodiment of the application also provides a terminal equipment management and control device configured on a server, the device comprises:

a fourth data receiving module, configured to receive, before a terminal device reaches an entry device of an electronic fence, a device identifier of the terminal device sent by the terminal device, and a first policy validation state of a management and control policy set in the electronic fence for the terminal device; the first policy validation state is a validation state of the management and control policy obtained by the terminal equipment executing the management and control policy;

the third data storage module is used for storing the equipment identifier and the corresponding first policy effective state;

a fifth data receiving module, configured to receive physiological characteristic information of a user sent by the entry device after the terminal device reaches the entry device;

the second data query module is used for determining the first policy effective state corresponding to the terminal equipment according to the physiological characteristic information, the pre-stored corresponding relation between the physiological characteristic information and the equipment identifier and the pre-stored corresponding relation between the equipment identifier and the first policy effective state;

The second data sending module is used for sending the first policy validation state to the entrance equipment or generating an admission instruction based on the first policy validation state; the access instruction is used for indicating the entrance equipment to allow or reject the user to enter the electronic fence.

In one implementation manner of the terminal device management and control apparatus, the apparatus further includes: the third instruction issuing module is used for sending a policy execution instruction to the terminal equipment when the first policy validation state is not normally validated, wherein the policy execution instruction is used for indicating the terminal equipment to execute the validation operation of the management and control policy; the fourth data receiving module is further configured to receive the device identifier and the second policy validation state sent by the terminal device; the second policy validation state is a validation state of the management and control policy obtained by the terminal equipment running the policy execution instruction; the third data storage module is used for storing the equipment identifier and the corresponding second policy effective state; the second data sending module is further configured to send the second policy validation state to the ingress device, or an admission instruction generated based on the second policy validation state; the access instruction is used for indicating the entrance equipment to allow or reject the user to enter the electronic fence.

The foregoing implementation principles and the technical effects of the terminal device management and control device provided in the embodiments of the present application have been described in the foregoing method embodiments, and for the sake of brevity, reference may be made to corresponding contents in the method embodiments where the device embodiment portion is not mentioned.

The embodiment of the application also provides a terminal equipment management and control system, which comprises terminal equipment and a server, wherein the terminal equipment is used for executing the step executed by the terminal equipment in the terminal equipment management and control method provided by the embodiment of the application, and the server is used for executing the step executed by the server in the terminal equipment management and control method provided by the embodiment of the application, and specific reference can be made to corresponding contents in the method embodiment.

The embodiment of the application further provides a terminal device management and control system, which comprises a terminal device, an entrance device of an electronic fence and a server, wherein the terminal device is used for executing steps executed by the terminal device in the terminal device management and control method provided by the embodiment of the application, the entrance device is used for executing steps executed by the entrance device in the terminal device management and control method provided by the embodiment of the application, and the server is used for executing steps executed by the server in the terminal device management and control method provided by the embodiment of the application, and specific reference can be made to corresponding contents in the embodiment of the method.

Fig. 9 shows a possible structure of the electronic device 200 provided in the embodiment of the present application. Referring to fig. 9, the electronic apparatus 200 includes: processor 210, memory 220, and communication interface 230, which are interconnected and communicate with each other by a communication bus 240 and/or other forms of connection mechanisms (not shown).

Wherein the processor 210 includes one or more (only one shown), which may be an integrated circuit chip, having signal processing capabilities. The processor 210 may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a micro control unit (Micro Controller Unit, MCU), a network processor (Network Processor, NP), or other conventional processor; but may also be a special purpose processor including a Neural Network Processor (NPU), a graphics processor (Graphics Processing Unit GPU), a digital signal processor (Digital Signal Processor DSP), an application specific integrated circuit (Application Specific Integrated Circuits ASIC), a field programmable gate array (Field Programmable Gate Array FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. Also, when the processor 210 is plural, some of them may be general-purpose processors, and another may be special-purpose processors.

The Memory 220 includes one or more (Only one shown in the drawings), which may be, but is not limited to, a random access Memory (Random Access Memory, RAM), a Read Only Memory (ROM), a programmable Read Only Memory (Programmable Read-Only Memory, PROM), an erasable programmable Read Only Memory (Erasable Programmable Read-Only Memory, EPROM), an electrically erasable programmable Read Only Memory (Electric Erasable Programmable Read-Only Memory, EEPROM), and the like. Processor 210, as well as other possible components, may access memory 220, read and/or write data therein.

In particular, one or more computer program instructions may be stored in the memory 220, which may be read and executed by the processor 210 to implement the terminal device management method provided in the embodiments of the present application.

The communication interface 230 includes one or more (only one shown) that may be used to communicate directly or indirectly with other devices for data interaction. Communication interface 230 may include an interface for wired and/or wireless communication.

It is to be understood that the configuration shown in fig. 9 is merely illustrative, and that the electronic device 200 may also include more or fewer components than those shown in fig. 9, or have a different configuration than that shown in fig. 9. The components shown in fig. 9 may be implemented in hardware, software, or a combination thereof. The electronic device 200 may be a physical device such as a PC, a notebook, a tablet, a cell phone, a server, a wearable device, a gate, etc., or may be a virtual device such as a virtual machine, a virtualized container, etc. The electronic device 200 is not limited to a single device, and may be a combination of a plurality of devices or a cluster of a large number of devices.

For example, the terminal device, the entrance device of the electronic fence, and the server mentioned in the embodiments of the present application may all be implemented by using the structure in fig. 9.

The embodiment of the application also provides a computer program product, which comprises computer program instructions, and when the computer program instructions are read and run by a processor of a computer, the terminal equipment management and control method provided by the embodiment of the application is executed.

The embodiment of the application also provides a computer readable storage medium, and the computer readable storage medium stores computer program instructions which, when read and run by a processor of a computer, execute the terminal equipment management and control method provided by the embodiment of the application. For example, the computer readable storage medium may be implemented as memory 220 in electronic device 200 in FIG. 9.

The foregoing is merely exemplary embodiments of the present application and is not intended to limit the scope of the present application, and various modifications and variations may be suggested to one skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims (14)

1. A method for controlling a terminal device, which is applied to a terminal device, the method comprising:

acquiring a control strategy set for the terminal equipment in the electronic fence;

and executing the control strategy before the terminal equipment reaches the entrance equipment of the electronic fence.

2. The terminal device management and control method according to claim 1, wherein the obtaining a management and control policy set for the terminal device in the electronic fence includes:

before the terminal equipment reaches the entrance equipment, a request for acquiring the control strategy is sent to a server, and the control strategy corresponding to the request returned by the server is received;

the executing the control strategy comprises the following steps:

in response to receiving the policing policy from the server, the policing policy is executed.

3. The terminal device management method according to claim 1, wherein the executing the management policy before the terminal device reaches the entrance device of the electronic fence comprises:

and before the terminal equipment reaches the entrance equipment of the electronic fence, responding to the triggering operation on the terminal equipment, and executing the control strategy.

4. A terminal device management method according to claim 3, wherein said executing said management policy in response to a trigger operation on said terminal device comprises:

and when the condition that the permission triggering condition is met is detected, responding to the triggering operation on the terminal equipment, and executing the control strategy.

5. The terminal device management method according to claim 4, wherein the allowed trigger condition includes at least one of:

the distance between the terminal equipment and the entrance equipment is smaller than a first distance threshold value;

the difference between the current time and the target time for the terminal device to reach the entry device is less than a first time threshold.

6. The terminal device management method according to claim 1, wherein the executing the management policy before the terminal device reaches the entrance device of the electronic fence comprises:

and executing the effective operation of the control strategy when the terminal equipment detects that the automatic triggering condition is met before reaching the entrance equipment of the electronic fence.

7. The terminal device management method according to claim 6, wherein the automatic triggering condition includes at least one of:

The distance between the terminal equipment and the entrance equipment is smaller than a second distance threshold value;

the difference between the current time and the target time for the terminal device to reach the entry device is less than a second time threshold.

8. The terminal device management method according to any one of claims 1 to 7, characterized in that the method further comprises:

generating first scanning information for the portal equipment to scan, wherein the first scanning information comprises equipment identification of the terminal equipment; or alternatively, the process may be performed,

and after the terminal equipment arrives at the entrance equipment, the equipment identification is sent to the entrance equipment.

9. The terminal device policing method of claim 8, further comprising, after said executing said policing policy:

acquiring a first strategy effective state of the management and control strategy;

the first scan information further includes the first policy validation state; or alternatively, the process may be performed,

after the terminal equipment reaches the entrance equipment, the first policy validation state is further sent to the entrance equipment; or alternatively, the process may be performed,

and sending the equipment identification and the first policy validation state to a server.

10. The method according to claim 9, wherein the first policy validation state is used for outputting on the portal device or is used as a basis for allowing or rejecting the portal device to enter the electronic fence by the user.

11. The terminal device management and control method according to claim 9, wherein the first policy validation state is not validated normally, the method further comprising:

receiving a policy execution instruction sent by a server, wherein the policy execution instruction is used for indicating the terminal equipment to execute the management and control policy;

operating the strategy execution instruction to obtain a second strategy effective state of the management and control strategy;

generating second scanning information for the portal device to scan, wherein the second scanning information comprises the device identification and the second policy validation state; or alternatively, the process may be performed,

transmitting the device identification and the second policy validation state to the portal device; or alternatively, the process may be performed,

and sending the equipment identification and the second policy validation state to the server.

12. A terminal device management and control apparatus, configured to a terminal device, the apparatus comprising:

the strategy acquisition module is used for acquiring a control strategy set for the terminal equipment in the electronic fence;

and the policy execution module is used for executing the control policy before the terminal equipment reaches the entrance equipment of the electronic fence.

13. A computer readable storage medium, having stored thereon computer program instructions which, when read and executed by a processor, perform the method of any of claims 1-11.

14. An electronic device comprising a memory and a processor, the memory having stored therein computer program instructions that, when read and executed by the processor, perform the method of any of claims 1-11.

Images