Profiles

As mentioned earlier, Profiles refer to some built-in application scenarios of the terminal device, the purpose is to conveniently realize that when the terminal is in a specific scenario, the working mode can be automatically switched.

In different profiles, the terminal can have different behaviors. Here are some examples.

• When the terminal leaves the home network and enters the roaming network area, it will automatically switch to Profile 1 (Roaming), at this time, in order to save the data usage of the roaming network, the terminal may only generate reports but not send to the backend server, and then send these reports when the terminal leaves the roaming network area and returns to the local network area.

• When it is off duty, the terminal will automatically switch to Profile 3 (Off Duty), and in order to protect the privacy of the driver, the generated reports will not contain the actual location information, instead of fixed and false location information.

• When the ignition signal is detected, the terminal will automatically switch to Profile 6 (Ignition On), and a location report will be generated every 1 minute. When the flameout signal is detected, the terminal will switch to Profile 7 (Ignition Off), and automatically adjust to generate a location report every 60 minutes.

• When the power supply is sufficient, the terminal generates a location report every 30 minutes, and when it is in a low power state, in order to save power, it will switch to Profile 11 (Low Power) and automatically adjust to generate a location report every 6 hours.

• When the terminal receives the AT@RTO command with the subcommand 92, the terminal will automatically switch to Profile 63 (Emergency), and always tries to maintain a long connection with the backend server while shortening the interval for generating location reports so that the server can know the location of the terminal in real time.

These different behaviors of the terminal under different profiles can be realized through the multi-profile commands (containing the ‘Profile ID’ field). And the profile related commands supported by the terminal are listed below.

Note

Not all configuration commands support multiple profiles, that is, some commands are valid regardless of which profile the terminal is in, such as AT@CFG command.

In addition, the parameters of each profile are independent. Changing the parameters of one profile will not affect the parameters of other profiles.

By default, all parameters of all profiles supported by the terminal are the same, and the terminal only enables Profile 0 (Default) and Profile 63 (Emergency), and other profiles are disabled. The AT@PROFILE command can enable and disable profiles other than Profile 0 and Profile 63.

The terminal works in Profile 0 (Default) when it is started, and only when the trigger conditions of other profiles are met, the terminal will switch to other profiles. And when the conditions of other profiles disappear, the terminal will switch back to Profile 0 to work.

Priority

Sometimes the terminal may be in multiple profiles at the same time, for example, the terminal is in the area of the roaming network (Profile 1), and the power supply is low (Profile 11). The terminal supports configuring different priorities for different profiles to clarify the behavior of the terminal when it is in multiple profiles at the same time: The terminal will work according to the parameters of the higher priority profile.

By default, the lower the value of the profile ID, the lower the priority, that is, Profile 0 (Default) has the lowest priority and Profile 63 (Emergency) has the highest priority. And in particular, the priority of Profile 0 and Profile 63 cannot be changed, while the priority of other profiles can be changed through the AT@PPS command.

Note

The priority of each profile is different, that is, one profile corresponds to one priority. There will be no different profiles using the same priority.

Commands

The profile related commands supported by the terminal are as follows:

• AT@PROFILE

• AT@PPS

• Record 50H Settings

Supported Profiles

For GV500CNA, the supported profiles are as follows:

• Profile 0 (Default)

  When a terminal is first powered on, it always works in this profile. When the terminal restarts, it will work in the profile before the restart.

  The terminal will only switch to other profiles when it is satisfied to switch to other profiles, otherwise it will always work in this profile.

  Profile 0 (Default) is the lowest priority profile, and this is unchangeable.

• Profile 1 (Roaming)

  Since the terminal may be often used across regions, in order to reduce the data usage when using a roaming network, the terminal supports appropriately reducing the number of messages sent to the backend server when using a roaming network. This can be achieved by changing the configuration of the Profile 1.

  This profile is disabled by default, you can enable it through the AT@PROFILE command.

• Profile 3 (Off Duty)

  To protect the privacy of the driver and reduce unnecessary data usage, the terminal supports running with different configuration parameters during off duty. This can be achieved by changing the configuration of the Profile 3.

  Fixedly, the reports sent by the terminal during off duty always hide the location information, which means that in all reports, the fields Latitude, Longitude will be filled with 054C5638H, and the fields PLMN, LAC, Cell ID will be filled with 0.

  Note

  This feature of hiding location information during off duty is always effective, even if the terminal switches to other profile (except Profile 63).

  This profile is disabled by default, you can enable it through the AT@PROFILE command, and the working hours can be set in the AT@OWH command.

• Profile 6 (Ignition On)

  The terminal supports vehicle ignition detection. When the vehicle is being driven, the location can be updated more quickly. In order to more timely inform the backend server that the location of the terminal, it is necessary to speed up the transmission of location information when vehicle is ignition on. This can be achieved by changing the configuration of the Profile 6.

  This profile is disabled by default, you can enable it through the AT@PROFILE command.

• Profile 7 (Ignition Off)

  The terminal supports vehicle ignition detection. In order to save power, some reports need to be turned off or reduced when the vehicle is ignition off. This can be achieved by changing the configuration of the Profile 7.

  This profile is disabled by default, you can enable it through the AT@PROFILE command.

• Profile 11 (Low Power)

  When the external power supply of the terminal is connected and low, in order to extend the working time as much as possible, the terminal supports running with different configuration parameters at this time, which can be achieved by changing the configuration of Profile 11.

  This profile is disabled by default, you can enable it through the AT@PROFILE command, and the low power threshold can be set in the AT@EPS command.

• Profile 63 (Emergency)

  In order to allow the user to know the current location and other information of the terminal in a more real-time way when necessary, the terminal supports the Profile 63 (Emergency).

  This profile is also called emergency mode, and it contains these features:

  • When the terminal enters the emergency mode, the GNSS and cellular network are always on, and the terminal will always stay connected to the backend server.

  • When the terminal enters the emergency mode, the Outside Working Hours function (see AT@OWH command) will also be invalid, the real location of the terminal will be used to generate reports.

  • In emergency mode, the terminal always sends real-time reports first (equivalent to ‘Report Priority’ in the AT@RPS command is set to 1).

  • In emergency mode, the terminal may send some reports to the backend server more frequently. This can be achieved by changing the configuration of the Profile 63.

  Note

  The Profile 63 is always enabled and has the highest priority, which cannot be changed.

  How to Enter Profile 63

  When one of the following conditions is met, the terminal will switch to Profile 63 (Emergency).

  • When the terminal receives the AT@RTO command with the subcommand 92.

  How to Exit Profile 63

  When the terminal detects that the conditions for entering Profile 63 (Emergency) have disappeared, or the specified duration has elapsed, the terminal will exit Profile 63 and switch to other profiles. For example, the terminal receives a command to end the emergency state from the backend server.