Methods, apparatus and computer readable media for device communication management in a communication system

Abstract

Aspects of the present description generally refer to one or more systems, methods and / or devices for secure communication between devices, such as devices within a vehicle. for example, some vehicles have built-in mobile computing platforms that allow communication with an extended productivity device. however, communication between the mobile computing platform and the extended productivity device may not be secure enough. as such, the present disclosure provides secure communication between the mobile computing platform and the extended productivity device, verifying, for example, an identity of the extended productivity device.

Description

1 / 33 “METHODS, APPARATUS AND COMPUTER-READABLE MEANS FOR MANAGING DEVICE COMMUNICATION IN A COMMUNICATION SYSTEM” PRIORITY CLAIM

[001] This Patent Application claims priority to Non-Provisional Application No. 14 / 994,381 entitled DEVICE COMMUNICATION MANAGEMENT IN A COMMUNICATION SYSTEM filed on January 13, 2016, which is assigned to the assignee hereof and is hereby expressly incorporated by reference herein for all purposes. BACKGROUND OF THE INVENTION

[002] The aspects of this description generally refer to communication systems and, more particularly, to the management of communication between devices within a vehicle.

[003] Communication systems are widely implemented to provide various communication services, such as telephony, video, data, messaging, broadcasts, and so on. These systems can be deployed in a vehicle to provide enhanced logistical capabilities. For example, some delivery vehicles include integrated communication systems in the form of an electronic system that allows the driver to transmit information and receive information from a remote host device. Such information may include, for example, route information, which assists the driver in reaching a delivery point by displaying route information on a screen. Some vehicle communication systems can also communicate wirelessly with devices inside the vehicle. There may be a lack of security in some vehicle communication systems, however, as some communication systems can be easily accessed by any device seeking Petition 870260000329, dated 05 / 01 / 2026, page 9 / 48 2 / 33 access. For example, if a vehicle communication system includes, for example, a Bluetooth and / or WIFI-Direct communication interface, then in some cases, any other device with a similar Bluetooth and / or WIFI-Direct communication interface may be able to monitor the vehicle communication system's communications and / or communicate with the vehicle communication system. As such, it may be desirable to provide secure communication between devices within a vehicle. BRIEF DESCRIPTION OF THE INVENTION

[004] The following is a simplified summary of one or more aspects of the present description in order to provide a basic understanding of such aspects. This summary is not a comprehensive overview of all aspects contemplated, and does not purport to identify key or critical elements of all aspects, nor to delineate the scope of any or all aspects. Its sole purpose is to introduce some concepts of one or more aspects of the present description in a simplified form as a prelude to the more detailed description that is presented later.

[005] In some respects, a present method relates to secure communication between devices. The aspects described include detecting, on an electronic device, that a first device is within the communication range of the electronic device according to one or more communication protocols. The aspects described further include establishing a restricted communication session with the first device based on the detection that the first device is within the communication range of the electronic device. The aspects described further include receiving, through a first communication channel associated with one or more communication protocols, an authentication request including a first device identifier of the first device in response to the establishment of the initial communication session with the first device.The aspects described also include determining whether a device identifier whitelist includes the first device identifier in response to receiving the authentication request, where the whitelist of... Petition 870260000329, dated 05 / 01 / 2026, page 10 / 48 3 / 33 Device identifiers allow a device with an associated device identifier to communicate with the electronic device. The aspects described also include, according to a determination that the device identifier allowlist includes the first device identifier, allowing an unrestricted communication session with the first device. The aspects described also include, according to a determination that the device identifier allowlist does not include the first identifier, terminating the restricted communication session with the first device.

[006] In another aspect, a non-transient computer-readable means present comprises code for secure communication between devices. The described aspects detect that a first device is within a communication range of the electronic device according to one or more communication protocols. The described aspects further include establishing a restricted communication session with the first device based on the detection that the first device is within the communication range of the electronic device. The described aspects further include receiving, through a first communication channel associated with one or more communication protocols, an authentication request including a first device identifier of the first device in response to the establishment of the initial communication session with the first device.The aspects described further include determining whether a device identifier allowlist includes the first device identifier in response to receiving the authentication request, where the device identifier allowlist allows a device with an associated device identifier to communicate with the electronic device. The aspects described also include, according to a determination that the device identifier allowlist includes the first device identifier, allowing an unrestricted communication session with the first device. The aspects described also include, according to a determination that the device identifier allowlist does not include the first identifier, terminating the restricted communication session with the first device. Petition 870260000329, dated 05 / 01 / 2026, p. 11 / 48 4 / 33

[007] In another aspect, a present apparatus refers to secure communication between devices. The aspects described include a processor and a memory coupled to the processor, wherein the memory includes instructions executable by the processor to detect that a first device is within a communication range of the electronic device according to one or more communication protocols. The aspects described further establish a restricted communication session with the first device based on the detection that the first device is within the communication range of the electronic device. The aspects described also receive, through a first communication channel associated with one or more communication protocols, an authentication request including a first device identifier of the first device in response to the establishment of the initial communication session with the first device.The aspects described further determine whether a device identifier allowlist includes the first device identifier in response to receiving the authentication request, wherein the device identifier allowlist allows a device with an associated device identifier to communicate with the electronic device. The aspects described also allow an unrestricted communication session with the first device, according to a determination that the device identifier allowlist includes the first device identifier. The aspects described further terminate the restricted communication session with the first device according to a determination that the device identifier allowlist does not include the first identifier.

[008] For the accomplishment of the foregoing and related purposes, one or more aspects of the present description comprise the features described below in full and particularly pointed out in the claims. The following description and the accompanying drawings present in detail certain illustrative features of one or more aspects of the present description. These features are indicative, however, of only some of the various ways in which the principles of various aspects of the present description may be employed, and this description is intended to include all such aspects and their equivalents. Petition 870260000329, dated 05 / 01 / 2026, p. 12 / 48 5 / 33 BRIEF DESCRIPTION OF THE DRAWINGS

[009] The disclosed aspects of this description will be described below in conjunction with the accompanying drawings, provided for illustrative purposes only and not to limit the disclosed aspects, where similar designations denote similar elements, where a dashed line may indicate an optional element or action, and where:

[010] FIG. 1 is a functional block diagram of example elements of an aspect of a system, including a mobile computing platform configured to enable secure communication between devices;

[011] FIG. 2 is a block diagram of example elements of an additional aspect of a system, including a mobile computing platform configured to enable secure communication between devices;

[012] FIGS. 3-5 are flowcharts of one aspect of a secure communication method between devices according to some aspects of the present description;

[013] FIG. 6 is a conceptual diagram of a secure communication scheme between various entities within a communication system according to some aspects of the present description;

[014] FIG. 7 is a conceptual diagram of a secure communication scheme between several entities, namely a mobile computing platform and an extended productivity device, within a communication system according to some aspects of the present description;

[015] FIG. 8 is a block diagram of an example of an aspect of a mobile computing platform (MCP) according to some aspects of the present description; and Petition 870260000329, dated 05 / 01 / 2026, page 13 / 48 6 / 33

[016] FIG. 9 is a block diagram of an example of an aspect of a network management center (NMC) according to some aspects of the present description. DETAILED DESCRIPTION

[017] Several aspects of the systems, apparatus, and methods are described in more detail below with reference to the attached figures. This description can, however, be incorporated in many different ways and should not be interpreted as limited to any specific structure or function presented throughout this description. On the contrary, these aspects are provided so that this description is exhaustive and complete, and will fully convey the scope of the description to those skilled in the art. Based on the teachings presented here, a person skilled in the art should understand that the scope of the description is intended to cover any aspect of the systems, apparatus, and methods disclosed here, whether implemented independently of, or combined with, any other aspect described herein. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein.Furthermore, the scope of these aspects is intended to cover such an apparatus or method that is practiced using another structure, functionality, or structure and functionality in addition to or beyond the various aspects set forth herein. It should be understood that any aspect disclosed herein may be incorporated by one or more elements of a claim.

[018] Although particular aspects are described herein, many variations and exchanges of these aspects are within the scope of the description. While some benefits and advantages of the aspects are mentioned, the scope of the description is not intended to be limited to specific benefits, uses, or objectives. Rather, the aspects of the description are intended to be broadly applicable to different communication technologies, system configurations, networks, and transmission protocols, some of which are illustrated by way of example in the figures and description of the aspects that follow. The detailed description and figures are merely illustrative of the description rather than Petition 870260000329, dated 05 / 01 / 2026, page 14 / 48 7 / 33 limiting, the scope of the description being defined by the appended claims and their equivalents.

[019] The aspects presented generally refer to secure communication between devices. Specifically, some vehicles (e.g., trucks) may include onboard management systems that provide various functionalities to a vehicle driver and / or a centralized management center. For example, at a macro level, onboard management systems may allow a centralized management center to track and manage a fleet of vehicles. However, at a micro level, these onboard management systems may interact directly with the driver through an extended productivity (EP) device (e.g., smartphone).For example, an onboard management system can provide various types of information to the driver through the extended productivity device, including information such as, but not limited to, messages from the centralized management center, workflow data, and / or specific driver training.

[020] However, in some respects, the information received from the centralized management center may be considered sensitive and / or confidential, and intended only for a specific recipient (e.g., driver). However, some onboard management systems may allow easy access to the centralized management center and, in turn, to the data residing in the centralized management center. This easy access may result in unauthorized retrieval or manipulation of information in the centralized management center. For example, because some onboard management systems include no, or at most minimal, security measures to prevent unauthorized access, any other extended productivity device may connect to the centralized management center via the integrated management system and access its data.However, secure communication may be desirable because there may be applications running for specific entities that exchange confidential information. Petition 870260000329, dated 05 / 01 / 2026, page 15 / 48 8 / 33

[021] Thus, the present aspects provide one or more solutions to ensure that extended productivity devices intended to communicate with the on-board management system of vehicles are authorized extended productivity devices (e.g., part of a customer's devices or vehicle fleet). As such, authentication of an extended productivity device by the on-board management system, or vice versa, would allow secure communication between systems and devices and prevent unauthorized devices from participating in these communications. As a result, the data exchanged between an authorized extended productivity device and the integrated management system would be considered secure.

[022] Several aspects will now be described with reference to the drawings. In the following description, for explanatory purposes, numerous specific details are set forth in order to provide a complete understanding of one or more aspects. It should be understood, however, that such aspect(s) may be practiced without these specific details.

[023] Referring now to FIG. 1, in one aspect, a communication system 100 includes one or more components and / or modules to implement secure communication between devices in conjunction with the operation of one or more vehicles. As used herein, the term component and / or module may be one of the parts that make up a device, may be hardware or software or firmware, and may be divided into other modules and / or distributed through one or more processors.

[024] In one aspect, the communication system 100 may include one or more mobile computing platforms (MCPs) 144a and 144b, which may be configured to facilitate secure communication with one or more devices, such as an extended productivity device (EP) 146 (e.g., a smartphone, tablet, etc.). Furthermore, the communication system 100 may include the network management center (NMC) 112 configured to communicate with one or more vehicles 104a and 104b via MCPs 144a and 144b, which may be located in each vehicle 104a and 104b, or associated with other vehicles. Petition 870260000329, dated 05 / 01 / 2026, page 16 / 48 9 / 33 to each driver of each vehicle 104a and 104b. In one aspect, MCP 144a and MCP 144b may be coupled to a respective vehicle, such as, but not limited to, vehicle 104a and vehicle 104b.

[025] The communication system 100 may include one or more fleets of vehicles 104a and 104b, each fleet having at least one vehicle. In some respects, a fleet may include tens, hundreds, or thousands of vehicles. An example of a fleet is illustrated as having two vehicles, for example, vehicle 104a and vehicle 104b. Additional fleets (not shown) are contemplated but not shown. In implementations, each MCP 144a and 144b may be configured to collect and transmit data associated with the operation of each respective vehicle 104a and 104b to the NMC 112.

[026] In one aspect, MCP 144a and 144b, and their corresponding components and / or modules, may be implemented as a software application defined by code or instructions stored on a computer-readable medium and executed by a processor, and / or as hardware (e.g., a specially programmed processor module) and / or as firmware. According to the present aspects, one of the components of MCP 144a (or, similarly, MCP 144b) may include the determination component 109 which may be configured to allow secure communications with another device, such as the EP 146 device.

[027] Specifically, for example, the MCP 144a can facilitate secure communication with the EP 146 device by operating the determination component 109 to verify the authenticity of the EP 146 device using its device identifier. For example, after receiving, via communication component 160, a first set of device identifiers from the NMC 112, the MCP 144a can be configured to detect that a first device, such as, but not limited to, the EP 146 device, is within a communication range of the MCP 144a according to one or more communication protocols. In some respects, the communication protocols may correspond to Bluetooth and / or Wi-Fi. Furthermore, upon detecting that the EP 146 device is within a communication range (e.g., via Bluetooth within the vehicle 104a), the MCP Petition 870260000329, dated 05 / 01 / 2026, page 17 / 48 10 / 33 114a can establish a restricted communication session with the EP 146 device. In some respects, the restricted communication session may correspond to a pairing session associated with a respective communication protocol.

[028] After the initial communication session is established (e.g., the pairing session) between the MCP 144a and the EP 146 device, the MCP 144a may receive, via a communication channel associated with one or more communication protocols, an authentication request including a first device identifier 148 of the EP 146 device. In some respects, the authentication request may include a version identifier of an application running on the EP 146 device. For example, the application may be a secure communication application residing on the EP 146 device.

[029] In one aspect, MCP 144a may include determination component 109, which may be configured to determine whether a device identifier allowlist 121 includes the first device identifier 148 within the device identifier allowlist 121 to facilitate secure communication with the EP device 148. In some aspects, the device identifier allowlist 121 may be preconfigured in MCP 144a and / or determination component 109. Furthermore, in other aspects, the device identifier allowlist 121 may be received by MCP 144a and / or determination component 109 via satellite 108, communication channel 113 and / or base station 110 of NMC 112.For example, MCP 144a can receive the set of device identifiers that define the device identifier 121 whitelist according to an over-the-air communication protocol, such as a wide area network protocol or a terrestrial protocol. Alternatively, one or more communication protocols may include a Bluetooth or wireless local area network (WLAN) protocol.

[030] In one aspect, for example, MCP 144a and / or determination component 109 can be configured to receive via a second communication channel (for example, between NMC 112 and MCP 144a) different from the first communication channel, a Petition 870260000329, dated 05 / 01 / 2026, page 18 / 48 11 / 33 set of device identifiers associated with EP devices that may be authorized to communicate with MCP 144a. Specifically, for example, MCP 144a and / or determination component 109 may be configured to receive a first set of device identifiers including the first device identifier 148 associated with EP device 146 from a host entity, such as, but not limited to, NMC 112. In addition, MCP 144a and / or determination component 109 may generate or construct the device identifier allowlist 121 including one or more device identifiers from the first set of device identifiers within the device identifier allowlist 121 in response to receiving the first set of device identifiers from the host device (e.g., NMC 112).In some respects, the host device or entity (e.g., NMC 112) may directly provide the device identifier whitelist 121, including the set of device identifiers to MCP 144a.

[031] As such, in some respects, MCP 144a may initially be provisioned by receiving one of a device identifier whitelist 121 from NMC 112 or a first set of device identifiers for subsequent formation of device identifier whitelist 121 from NMC 112. For example, MCP 144a may receive a configuration message including the first set of device identifiers from NMC 112 via the first communication channel (e.g., via base station 110 and / or Internet 113). In some respects, the EP 146 device may also receive a provisioning message including one or more specific identifiers to identify the EP 146 device from a host entity (e.g., other than NMC 112) via a second communication channel (e.g., via base station 110 and / or Internet 113).

[032] In addition, to maintain an up-to-date device identifier allowlist 121, MCP 144a and / or determination component 109 may adjust or update the device identifier allowlist 121 based on one or both subsequent allowlists received from a host entity (e.g., NMC 112) or a second set of device identifiers. Petition 870260000329, dated 05 / 01 / 2026, page 19 / 48 12 / 33 Specifically, for example, MCP 144a and / or determination component 109 can be configured to receive a second set of identifiers including a second device identifier associated with a second host entity device (e.g., NMC 112) and different from the first set of identifiers. MCP 144a and / or determination component 109 can determine whether one or more device identifiers, including the first device identifier 148 from the first set of device identifiers, are missing from the second set of identifiers and adjust (e.g., add or remove) the device identifier 121 allowlist based on the determination that one or more device identifiers, including the first device identifier 148 from the first set of device identifiers, are missing from the second set of identifiers.In this respect, each of the first sets of device identifiers including the first device identifier 148 and the second set of device identifiers including the second device identifier may be either a mobile directory number (e.g., phone number) or a device identifier generated by a host entity.

[033] As such, MCP 144a and / or determination component 109 can be configured to allow an unrestricted communication session with EP device 146 based on the determination that the device identifier allowlist 121 includes the first device identifier 148 (e.g., mobile directory number). In some respects, MCP 144a and / or determination component 109 can allow an unrestricted communication session with EP device 146 through a token and, optionally, one or more other items can be used to authenticate the EP device and allow secure communications. Specifically, a communication token that allows secure communication between the electronic device and the EP device 146 can be generated in MCP 144a and sent to the EP device 146 based on the determination that the device identifier allowlist 121 includes the first device identifier 148.In addition, one or more MCP 144a addresses (e.g., MCP 144a electronic (IP) address), an indication of driver identifier scanning activation, or a message from... Petition 870260000329, dated 05 / 01 / 2026, page 20 / 48 13 / 33 Workflow task indicating one or more workflows for a user of the EP 146 device can be sent to the EP 146 device. In one aspect, for example, the communication token and, optionally, one or more MCP 144a addresses, driver identifier activation indication or workflow task message, allows either data synchronization between the MCP 144a and the EP 146 device, or a state retrieval of one or more messages or files from the EP 146 device.

[034] Furthermore, in one aspect, as part of determining whether to grant access to the EP 148 device, and in addition to determining whether the device identifier of the EP 148 device is included in the list of device identifiers 121, MCP 144a and / or the determination component 109 may determine whether the version identifier of the application running on the EP 146 device satisfies a compatible version identifier in MCP 144a. Consequently, MCP 144a and / or the determination component 109 may allow communication with the EP 148 device, also based on determining that the version identifier of the application running on the EP 146 device satisfies the compatible version identifier in MCP 144a.

[035] However, in order to prevent unauthorized access to protect information in MCP 144a, or NMC 112 via MCP 144a, MCP 144a and / or determination component 109 can be configured to terminate the restricted communication session with EP device 146 and, as such, prevent the establishment of a secure communication session with EP device 146 based on the determination that the device identifier whitelist 121 does not include the first identifier 148. Furthermore, in some respects, the restricted communication session can also be terminated based on the determination that the version identifier of the application running on EP device 146 does not match the compatible version identifier in MCP 144a.

[036] In some respects, MCP 144a may also include an 805 processor configured to execute computer-readable code and / or instructions, and / or a Petition 870260000329, dated 05 / 01 / 2026, page 21 / 48 14 / 33 memory 810 configured to store computer-readable code, where processor 805 and / or memory 810 may define all or part of component determination 109 and may also store data associated with components and / or MCP 144a. The MCP 144a may also include a user interface or monitor, a mobile application server, and a communications module (e.g., including one or more transceivers and one or more terrestrial and Wi-Fi modems, one or more antennas, a GPS module, and a satellite communications module). For example, in one aspect, the MCP 144a may include, but is not limited to, an MCP200 platform sold by OMNITRACS LLC of Dallas, Texas.

[037] As an example only, each vehicle 104 may be in bidirectional communication with NMC 112 on at least one communication channel. In the example shown in FIG. 1, each vehicle 104 is in bidirectional communication with NMC 112 on at least one satellite-based communication system 108 or a terrestrial system 110 (e.g., a wireless communication system using a communication protocol / technology such as, but not limited to, GSM, CDMA, TDMA, WCDMA, EDGE, OFDM, GPRS, EV-DO, LTE, Wi-Fi, Bluetooth, or, when the vehicle is stationary, via a wired connection 113 over the Internet). Depending on many factors, data may be exchanged with vehicles 104 using one or both of the satellite communication systems 108 and the terrestrial communication system 110.

[038] In one aspect, many different types of data are collected and transferred from vehicles 104 to NMC 112. Examples of such data include, but are not limited to, vehicle performance data, driver performance data, critical events, messages and position data, location delivery data, and many other types of data. All information that is communicated to and from vehicles 104 can be processed through NMC 112. NMC 112 can be considered as a data clearinghouse that receives all data that is transmitted to and received from vehicles 104. Furthermore, in one aspect, NMC 112 may include one or more back-end servers. Thus, in some aspects, the collected information (e.g., device identifiers) may periodically (e.g., every x minutes, where x is an integer or a Petition 870260000329, dated 05 / 01 / 2026, page 22 / 48 15 / 33 times per day, or as a wired or wireless connection becomes available) to be transmitted from MCP 144a to NMC 112 for analysis and record keeping.

[039] The communication system 100 also includes a data center 112, which may be part of or in communication with the NMC 112. The data center 112 illustrates a possible implementation of a central repository for all data received from each of the vehicles 104. As an example, as mentioned above, many different types of data are transmitted from the vehicles 104 to the NMC 112. In the case where the data center 112 is in communication with the NMC 112, the data may be transmitted via connection 211 to the data center 112. Connection 111 may comprise any dedicated wired or wireless link, a broadband link, or any other communication channel configured to carry the data. Furthermore, in one aspect, the data center 112 may include one or more backend servers that analyze one or more parameters transmitted from one or more MCP(s) 144a.Additionally or alternatively, data can also be exchanged between multiple MCP(s) 144a using, for example, peer-to-peer (P2P) communication without the involvement of NMC 112.

[040] In one aspect, the data center 112 may include the communication component 120, which may be configured to receive the sets of device identifiers from one or more host entities (e.g., clients) and form or generate the device identifier allowlist 121 for subsequent forwarding to the EP device 148, or forward the sets of device identifiers directly to the EP device 148. Furthermore, the communication component 120 may be configured to adjust the device identifier allowlist 121 by adding and / or removing device identifiers as they are received from one or more host entities. The communication component 120 may then forward or provide, via a communication channel, the adjusted device identifier allowlist 121 to the MCP 144a. Petition 870260000329, dated 05 / 01 / 2026, page 23 / 48 16 / 33

[041] In one aspect, for example, data center 112 may include any number of application servers and data stores, where each may be associated with a separate fleet and / or driver management or performance data. In one aspect, each application server and data store may include a processor, memory including volatile and non-volatile memory, specially programmed operating software, a communication bus, an input / output mechanism and other operating systems.

[042] For example, an application server might be a service portal (SP) server that receives, for example, message and positioning (M / P) data from each of the 104 vehicles. Another application server, for example, might include one or more servers related to safety and compliance, such as a QDC (Rapid Deployment Center) server that receives, for example, critical event (CE) data from each of the 104 vehicles. Furthermore, for example, another application server might be vehicle and driver performance data related to fuel consumption and / or cost for each of the 104 vehicles. Additionally, for example, another application server might be related to asset management, such as a Vehicle Maintenance Report and Vehicle Inspection server that receives, for example, maintenance and / or inspection data for each of the 104 vehicles.It should be understood that the above list of server examples is for illustrative purposes only, and the 212 data center may include additional and / or different application servers.

[043] In some respects, the EP 146 device may include, be implemented as, or be known as an access terminal (AT), a subscriber station, a subscriber unit, a mobile station, a remote station, a remote terminal, a user terminal, a user agent, a user device, user equipment, or some other terminology. In some implementations, an access terminal may include a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless-capable handheld device, or some other suitable processing device connected to a wireless modem. Thus, Petition 870260000329, dated 05 / 01 / 2026, page 24 / 48 17 / 33 One or more aspects disclosed herein may be incorporated into a telephone (e.g., a mobile phone or smartphone), a computer (e.g., a laptop), a portable communication device, a headset, a portable computing device (e.g., a data assistant), a global positioning system device, or any other suitable device that is configured to communicate via a wireless medium.

[044] FIG. 2 illustrates a block diagram of example elements of an aspect of the communication system 200 including the MCP 216 configured to allow secure communication with the EP device 218. For example, the host entity 212 may initially, through an interface, enter or provide one or more device identifiers (e.g., mobile directory number and / or unique device identifier generated by the host). In some aspects, the host entity 212 may be a fleet manager that owns a package (one or more) of EP devices 146 or may possess identification information of authorized or approved EP devices, including some that may already be in the possession of drivers. The identifiers may be sent to one or both NMC 112 via the mobile provisioning portal 214 or the EP device 146.The NMC 112 can, via BSS 208 and / or Concentrator 206, upon receiving one or more identifiers, enable and / or disable communication with one or more EP devices associated with one or more identifiers, and generate a whitelist 121 including one or more identifiers.

[045] NMC 112 can then send, via Concentrator 206, one or more identifiers and / or the allowlist 121 to MCP 144a through communication channel 220. Specifically, NMC 112 can send a configuration definition including allowlist 121 to MCP 144a (e.g., via over-the-air). In some respects, the EP 146 device can be provisioned with software associated with one or more applications, which in some respects can be used to verify (e.g., using its version identifier) ​​that the EP 146 device is authorized for secure communication with one or more MCPs 144. Furthermore, as part of the provisioning, the EP 146 device can be provided with or associated with a Petition 870260000329, dated 05 / 01 / 2026, page 25 / 48 18 / 33 device identifier, which can also be used to verify whether the EP 146 device is authorized for secure communication with one or more MCPs 144. Provisioning information (e.g., one or more of the mobile directory numbers, the respective device identifier and / or software application version) can be sent via a 222 communication channel (e.g., via Wi-Fi or terrestrial connection). The EP 146 device can then provide the supplied information to MCP 144a to authenticate the EP 146 device for secure communication with MCP 144a.

[046] As such, in a non-limiting use case example, when the EP 146 device attempts to connect to the MCP 144a, the EP 146 device initially sends its device ID to the MCP 144a. The MCP 144a then determines whether the EP 146 device's device ID matches an identifier in the allowlist 121. If the MCP 144a determines that the device ID is part of or included in the allowlist 121, the MCP 144a can generate a communication token and allow a secure connection with the EP 146 device. However, if the MCP 144a determines that the device ID is not part of or included in the allowlist 121, then the MCP 144a can prevent the EP 146 device from establishing a connection and exchanging information with the MCP 144a. Therefore, device EP 146, via MCP 144a and based on provisioning by host 204, can communicate with host entity 210 after successful authentication by MCP 144a.For example, a driver can use an EP device to connect to MCP 144a and communicate with NMC 112, in particular to access delivery information (e.g., addresses), obtain route information (e.g., for deliveries), and / or provide delivery confirmations.

[047] FIGS. 3-5 are flow diagrams of method 300 to facilitate secure communication between devices within, for example, a fleet vehicle according to some aspects of the present description. In some aspects, method 300 can be performed in MCP 144a (FIGS. 1 and 2). Some operations in method 300 can be combined, the order of some operations can be changed, and some operations can be omitted. Petition 870260000329, dated 05 / 01 / 2026, page 26 / 48 19 / 33

[048] In block 302, method 300 may optionally receive, through a second communication channel different from a first communication channel, a first set of device identifiers including the first device identifier associated with the first device of a host entity. For example, the MCP 144a (FIGS. 1 and 2) may implement one or more components and / or modules (e.g., communication component 160, FIG. 1) to receive, via a second communication channel 220 (FIG. 2) between a host entity (e.g., NMC 112, FIGS. 1 and 2) and the electronic device (e.g., MCP 144a, FIGS. 1 and 2) and different from a first communication channel 224 (FIG. 2), a first set of device identifiers (e.g., mobile directory number or unique identifiers generated by the host) including the first device identifier 148 (FIG. 1) associated with the first device (EP device 146, FIGS. 1 and 2).1 and 2) of a host entity (e.g., NMC 112, FIGS. 1 and 2).

[049] In some respects, as part of receiving the first set of device identifiers, a configuration message including the first set of device identifiers may be received from the host entity (e.g., NMC 112, FIGS. 1 and 2) via the first communication channel 224 (FIG. 2) or a provisioning message including the first set of identifiers from a second host entity (e.g., mobile provisioning portal 214, FIG. 1) via a third communication channel 222 (FIG. 2), respectively different from the first host entity (e.g., NMC 112, FIGS. 1 and 2) and the first communication channel 224 (figure 2).

[050] In addition, in block 304, method 300 may optionally generate the device identifier whitelist, including the first set of device identifiers. For example, MCP 144a (FIGS. 1 and 2) may execute one or more components and / or modules (e.g., determination component 109) to generate the device identifier whitelist 121 (FIG. 1) including the first set of device identifiers in response to receiving the first set of device identifiers from the host device (e.g., NMC 112, FIGS. 1 and 2). Petition 870260000329, dated 05 / 01 / 2026, p. 27 / 48 20 / 33

[051] In block 306, method 300 can detect that a first device is within a communication range of the electronic device according to one or more communication protocols. For example, MCP 144a (FIGS. 1 and 2) can run one or more components and / or modules (e.g., communication component 109 and communication component 160, FIG. 1) to detect that a first device (e.g., EP device, FIGS. 1 and 2) is within a communication range of the electronic device (e.g., MCP 144a, FIGS. 1 and 2) according to one or more communication protocols.

[052] Additionally, in block 308, method 300 can establish a restricted communication session with the first device. For example, MCP 144a (FIGS. 1 and 2) can execute one or more components and / or modules (e.g., communication component 160, FIG. 1) to establish a restricted communication session (e.g., pairing session) with the first device (e.g., device EP 146, FIGS. 1 and 2) based on the detection that the first device is within the communication range of the electronic device (e.g., MCP 144a, FIGS. 1 and 2).

[053] Furthermore, in block 310, method 300 may receive, through a first communication channel associated with one or more communication protocols, an authentication request including a first device identifier of the first device. For example, MCP 144a (FIGS. 1 and 2) may execute one or more components and / or modules (e.g., communication component 160, FIG. 1) to receive, through a first communication channel 224 (FIG. 2) associated with one or more communication protocols (e.g., Bluetooth or Wi-Fi), an authentication request including a first device identifier 148 (FIG. 1) of the first device (e.g., EP device 146, FIGS. 1 and 2) in response to establishing the initial communication session (e.g., pairing session) with the first device.

[054] In block 314, method 300 can determine if a whitelist of Petition 870260000329, dated 05 / 01 / 2026, p. 28 / 48 21 / 33 device identifiers include the first device identifier in response to receiving the authentication request. For example, MCP 144a (FIGS. 1 and 2) may run one or more components and / or modules (e.g., determination component 109, FIG. 1) to determine whether a device identifier allowlist 121 (FIG. 1) includes the first device identifier 148 (FIG. 1) in response to receiving the authentication request. In some respects, the device identifier allowlist 121 allows a device (e.g., EP device 146, FIGS. 1 and 2) to have an associated device identifier (e.g., first device identifier 148, FIG. 1) within the device identifier allowlist 121 (FIG. 1) to communicate with the electronic device (e.g., MCP 144a).

[055] Method 300 may proceed to block 316 based on the determination that the device identifier whitelist includes the first device identifier. Specifically, in block 316, method 300 may allow an unrestricted communication session with the first device. For example, MCP 144a (FIGS. 1 and 2) may run one or more components and / or modules (e.g., communication component 160, FIG. 1) to allow an unrestricted communication session using, for example, a communication token with the first device (e.g., EP device 146, FIGS. 1 and 2).

[056] In some respects, allowing an unrestricted communication session with the first device includes generating a communication token that enables secure communication between the MCP 144a electronic device (FIGS. 1 and 2) and the first device (e.g., EP 146 device, FIGS. 1 and 2). For example, the communication token allows one or both data synchronizations between the MCP 144a (FIGS. 1 and 2) and the first device (e.g., EP 146 device, FIGS. 1 and 2) or a status retrieval of one or more messages or files from the first device (e.g., EP 146 device, FIGS. 1 and 2).

[057] In some respects, the authentication request includes an identifier of Petition 870260000329, dated 05 / 01 / 2026, p. 29 / 48 22 / 33 version of an application running on the first device. Furthermore, as part of or in addition to the determination in block 310, method 300 may optionally determine whether the version identifier of the application running on the first device (e.g., device EP 146, FIGS. 1 and 2) satisfies a compatible version identifier on the MCP 144a electronic device (FIGS. 1 and 2). Additionally, as part of or in addition to allowing unrestricted communication in block 316, method 300 may optionally allow communication based on a determination that the version identifier of the application running on the first device satisfies the compatible version identifier on the electronic device.

[058] Otherwise, in block 318, method 300 can terminate the restricted communication session with the first device. For example, MCP 144a (FIGS. 1 and 2) can execute one or more components and / or modules (e.g., communication component 160, FIG. 1) to terminate the restricted communication session with the first device (e.g., EP device 146, FIGS. 1 and 2).

[059] Furthermore, in block 324, method 300 may receive a second set of identifiers, including a second device identifier associated with a second device of the host entity and different from the first set of identifiers. For example, MCP 144a (FIGS. 1 and 2) may implement one or more components and / or modules (e.g., communication component 160, FIG. 1) to receive a second set of identifiers including a second device identifier associated with a second device of the host entity (e.g., NMC 112, FIGS. 1 and 2) and different from the first set of identifiers.

[060] In some respects, each of the first sets of device identifiers including the first device identifier 148 (FIG. 1) and the second set of device identifiers including the second device identifier is either a mobile directory number (e.g., phone number) or a device identifier generated by a host entity (e.g., NMC 112, FIG. 1). Petition 870260000329, dated 05 / 01 / 2026, page 30 / 48 23 / 33

[061] In block 326, method 300 can determine whether one or more device identifiers, including the first identifier of the first set of device identifiers, are missing from the second set of identifiers. For example, MCP 144a (FIGS. 1 and 2) can run one or more components and / or modules (e.g., determination component 109, FIG. 1) to determine whether one or more device identifiers, including the first identifier 148 (FIG. 1) of the first set of device identifiers, are missing from the second set of identifiers.

[062] In block 328, method 300 can adjust the device identifier allowlist based on the determination that one or more device identifiers, including the first device identifier from the first set of device identifiers, are missing from the second set of identifiers. For example, MCP 144a (FIGS. 1 and 2) can execute one or more components and / or modules (e.g., communication component 109, FIG. 1) to adjust the device identifier allowlist 121 (FIG. 1) based on the determination that one or more device identifiers, including the first device identifier 148 (FIG. 1) from the first set of device identifiers, are missing from the second set of identifiers. In some respects, adjusting the allowlist for device identifier 121 (FIG. 1) includes removing one or more device identifiers, including the first identifier 148 (FIG. 1).1) from the device identifier's whitelist.

[063] With reference to FIG. 6, in operation, a secure communication scheme (e.g., a signaling diagram) 400 illustrates a non-limiting example of signaling that can be associated with method 300 to enable secure communication between devices, for example, between a client 420, host 422, 424 and 426, the concentrator 428, and a mobile device in the cabin 430 and 432. In some respects, the client 420 may be the same or similar to the host entity 212 (FIG. 2). Furthermore, in some respects, the host 422, 424 and 426 may be the same or similar to the NMC 112 (FIGS. 1 and 2). In some respects, the mobile device in the cabin 430 and 432 may be the same or similar to the MCP 144a (FIGS. 1 and 2). Petition 870260000329, dated 05 / 01 / 2026, p. 31 / 48 24 / 33

[064] In one aspect, in 402, a 420 client can enable / disable an EP device operation (such as EP device 146, FIG. 1) on a mobile device in the cabin (e.g., MCP 144a) by adding / removing operator profiles, and / or can add unique device identifiers (e.g., device identifiers), such as mobile directory numbers or host-generated IDs associated with authorized devices. Additionally, in 404, the host 422 BSS client portal can transmit a signal to the NMC 428 concentrator (e.g., NMC 112, FIG. 1) to configure CDEF to enable / disable the EP device and CDEF for listed allowed devices.

[065] In one aspect, in 406, the NMC concentrator 428 (e.g., NMC 112, FIG. 1) can transmit a signal to propagate enable / disable and allowed listed devices for message processing from the mobile device 430 in the cabin (e.g., MCP 144a). That is, the device identifiers of the allowed authorized / listed devices must be propagated or sent for message processing from the mobile device in the cabin 430 (e.g., MCP 144a). As a result, in 408, the mobile device in the cabin (e.g., MCP 144a) can enable / disable the EP device (e.g., EP device 148, FIG. 1) and update the allow list. In 410, the mobile device 430 message processing in the booth can transmit acknowledgment CDEFs (ACKs) to the NMC concentrator (e.g., NMC 112, FIG. 1) which, in turn, in 412, can transmit the ACK CDEFs to the QDC EP host scanning and workflow component.Additionally, in version 414, the in-cab mobile computing device message processing may display that the connection management component is active for the extended productivity device connection in the in-cab mobile device user interface (UI) (e.g., MCP 144a).

[066] With reference to FIG. 7, in operation, a secure communication scheme (e.g., signaling diagram) 500 illustrates the signaling to enable secure communication between devices, for example, between device EP 146 (FIG. 1) and a mobile device in the cabin (e.g., MCP 144a inside vehicle 104a, FIG. 1). In one aspect, in 502, a UI 546 of device EP 146 (FIG. 1) can Petition 870260000329, dated 05 / 01 / 2026, page 32 / 48 25 / 33 establish logic to use its mobile directory number, if available, or a device ID entered by the user after a software (SW) download that provisions the EP device. In 504, the message processing component 544 of the EP 146 device (FIG. 1) can transmit a signal corresponding to a Bluetooth pair or Wi-Fi direct connection message to the message processing component 544 of the mobile device in the cabin. In response, in 506, the message processing component 542 of the mobile device in the cabin can determine if the device identifier (ID) is on the whitelist and / or if the SW version of an application running on the EP 146 device (FIG. 1) is compatible.

[067] If the mobile device in the cabin determines that the device ID is on the whitelist and / or that the SW version of the application running on the EP 146 device (FIG. 1) is compatible, then it can generate a token and, in 508, transmit a signal corresponding to an acceptance of the Bluetooth pair / Wi-Fi direct connection to the EP mobile device. Furthermore, in 510, the EP mobile device's message processing can display a UI 540 to enter an identifier, and in 512, a user can enter a unique device ID generated by the host when prompted if the mobile directory number (MDN) is not available.As a result, in 514, the EP mobile device UI can transmit user input to the EP mobile device's message processing, which in turn, in 516, can transmit a signal to the mobile device's message processing in the booth corresponding to an authentication request with the phone device ID (e.g., generated MDN or host) and the SW version.

[068] In 518, the mobile device message processing 542 in the booth can transmit to the UI to display a successful connection if the device ID is included in the whitelist 121 of device IDs or an unsuccessful connection if the device ID is not included. In 520, the mobile computing device message processing in the booth can transmit a signal to the EP device message processing component 146 (FIG. 1) corresponding to either an acceptance of establishing a secure connection or can remove the pairing if authentication was unsuccessful. As part of the Petition 870260000329, dated 05 / 01 / 2026, page 33 / 48 26 / 33 successful acceptance or authentication, the signal in 520 may include a token, unified device address within the cabin, driver ID scanning enablement, and workflow task details, if applicable.

[069] In 522, the message processing component 544 of the EP 146 device (FIG. 1) can transmit to the UI for either successful or unsuccessful display. In 524, the user can enter scans and / or complete tasks for a workflow, and in 526 the UI can transmit the task completion message to the message processing component of the EP 146 device (FIG. 1). In 528, the message processing component 544 of the EP 146 device (FIG. 1) can transmit a signal including or using the token for mobile device message processing in the booth to synchronize files for scanning and / or workflow between the EP 146 device (FIG. 1) and the mobile device in the booth. In 530, the message processing component 542 of the mobile device in the booth can transmit a signal to the UI 540 to display the updated tasks and files available.Additionally, in 532, message processing 542 can transmit a signal including or using the message processing token from device EP 146 (FIG. 1) to retrieve one or more messages and / or file states. In 534, device EP 146 (FIG. 1) can establish that messages are persistent for 72 hours if there is no connection, and the messages should be discarded. Furthermore, in 536, the mobile device in the cabin can determine if the last Bluetooth transmission was 72 hours or more ago and, if so, remove the Bluetooth pair.

[070] With reference to FIG. 8, in an example that should not be interpreted as limiting, the MCP 206 may include additional components that operate in conjunction with vehicle management module(s) 207, which may be implemented in specially programmed computer-readable instructions or code, firmware, hardware, or some combination thereof.

[071]

[0071] In one aspect, the characteristics described here in relation to the functions of the vehicle management module(s) 144a can be implemented or Petition 870260000329, dated 05 / 01 / 2026, pp. 34 / 48 27 / 33 executed using one or any combination of processor 805, memory 810, communications module 815, and data storage 820. For example, the determination component 109 can be defined or otherwise programmed as one or more processor modules of processor 805. Furthermore, for example, the determination component 109 can be defined as a computer-readable medium (e.g., a non-transient computer-readable medium) stored in memory 810 and / or data storage 820 and executed by processor 805.

[072] In addition, for example, inputs and outputs relating to operations of the determination component 109 may be provided or supported by the communications module 815, which may provide a bus between the computer device modules or an interface for communication with external devices or modules. In some respects, and as discussed above, the determination component 109 may include the device identifier whitelist 121 and, optionally, the first device identifier 148. The processor 805 may include a single or multiple set of processors or multi-core processors. In addition, the processor 805 may be implemented as an integrated processing system and / or a distributed processing system.

[073] Memory 810 may operate to enable the storage and retrieval of data used herein and / or local versions of applications and / or software and / or instructions or code being executed by processor 805, such as to perform the respective functions of the determination component 109 described herein. Memory 810 may include any type of memory usable by a computer, such as random access memory (RAM), read-only memory (ROM), tapes, magnetic disks, optical disks, volatile memory, non-volatile memory, and any combination thereof.

[074] The 815 communications module is operable to establish and maintain communications with one or more internal components / modules or devices. Petition 870260000329, dated 05 / 01 / 2026, pp. 35 / 48 28 / 33 external using hardware, software, and services as described herein. The communications component 815 can carry communications between modules in the MCP 144a, as well as between users and external devices, such as devices located across a communications network and / or devices serially or locally connected to the MCP 144a. For example, the communications component 815 may include one or more buses, and may further include transmit chain modules and receive chain modules associated with a transmitter and receiver, respectively, or an operable transceiver for interfacing with external devices.

[075] In addition, the 580 data store, which may be any suitable combination of hardware and / or software, provides for mass storage of information, databases and programs used in connection with the aspects described in this document. For example, the 820 data store may be a data store for applications that are not currently being run by the 805 processor.

[076] MCP 144a may additionally include an operable user interface module 825 to receive input from a user, and further operable to generate output for presentation to the user. The user interface module 825 may include one or more input devices, including but not limited to a keyboard, a numeric keypad, a mouse, a touch-sensitive display, a navigation key, a function key, a microphone, a voice recognition module, another mechanism capable of receiving input from a user, or any combination thereof. In addition, the user interface module 825 may include one or more output devices, including but not limited to a monitor, a loudspeaker, a haptic feedback mechanism, a printer, any other mechanism capable of presenting output to a user, or any combination thereof.

[077] With reference to FIG. 9, in an example that should not be interpreted as limiting, the NMC 112 may include additional components to implement secure communication through the communication component 120, which may be Petition 870260000329, dated 05 / 01 / 2026, pp. 36 / 48 29 / 33 implemented in specially programmed computer-readable instructions or code, firmware, hardware, or some combination thereof.

[078] In one aspect, the features of communication component 120 described herein can be implemented or executed using one or any combination of processor 932, memory 934, and data storage 920. For example, communication component 120 can be defined or otherwise programmed as one or more processor modules of processor 932. Furthermore, for example, the advanced warning module 920 and the vehicle control module 924 can be defined as a computer-readable medium (e.g., a non-transient computer-readable medium) stored in memory 934 and / or data storage 910 and executed by processor 932. Additionally, for example, inputs and outputs related to operations of communication component 120, which can provide a bus between the components / modules of NMC 112 or an interface for communication with external devices or components / modules.

[079] The 932 processor may include a single or multiple set of processors or multi-core processors. In addition, the 932 processor may be implemented as an integrated processing system and / or a distributed processing system.

[080] Memory 934 may be operable for storing and retrieving data used herein and / or local versions of applications and / or software and / or instructions or code being executed by processor 932, as well as for performing the respective functions of the respective entities described herein. Memory 934 may include any type of memory usable by a computer, such as random access memory (RAM), read-only memory (ROM), tapes, magnetic disks, optical disks, volatile memory, non-volatile memory, and any combination thereof.

[081] The communications component 120 may be operable to establish and maintain communications with one or more internal components / modules and / or Petition 870260000329, dated 05 / 01 / 2026, pages 37 / 48 30 / 33 external devices using hardware, software, and services as described herein. The communications component 120 can carry communications between modules in the NMC 112, as well as between the user and external devices, such as devices located across a communications network and / or devices serially or locally connected to the NMC 112. For example, the communications component 120 may include one or more buses, and may further include transmit chain modules and receive chain modules associated with a transmitter and receiver, respectively, or a transceiver, operable to interface with external devices.

[082] In addition, data storage 920, which may be any suitable combination of hardware and / or software, provides for mass storage of information, databases and programs used in connection with the aspects described in this document. For example, data repository 920 may be a data repository for applications that are not currently being run by processor 932.

[083] The NMC 112 may additionally include an operable user interface module 925 to receive input from a user and also operable to generate output for presentation to the user. The user interface module 925 may include one or more input devices, including but not limited to a keyboard, number pad, mouse, touch screen, navigation key, function key, microphone, a voice recognition module, any other mechanism capable of receiving input from a user, or any combination thereof. In addition, the user interface module 926 may include one or more output devices, including but not limited to a monitor, a loudspeaker, a haptic feedback mechanism, a printer, any other mechanism capable of presenting output to a user, or any combination thereof.

[084] In view of the above description, a programming specialist is able to write computer code or identify appropriate hardware and / or circuits. Petition 870260000329, dated 05 / 01 / 2026, pages 38 / 48 31 / 33 to implement the disclosed invention without difficulty based on the flowcharts and description associated in this descriptive report, for example. Therefore, the description of a particular set of program code instructions or detailed hardware devices is not considered necessary for a proper understanding of how to make and use the invention. The inventive functionality of the claimed computer-implemented processes is explained in more detail in the description above and in conjunction with FIGS. 3-5, which may illustrate various process flows.

[085] In the description above, the term software product may include files with executable content, such as: object code, scripts, bytecode, markup language files, and patches. In addition, a “software product” mentioned here may also include files that are not executable in nature, such as documents that may need to be opened or other data files that need to be accessed.

[086] The term software update may also include files with executable content, such as: object code, scripts, bytecode, markup language files, and patches. In addition, the “software update” referred to here may also include files that are not executable in nature, such as documents that may need to be opened or other data files that need to be accessed.

[087] As used in this description, the terms “module,” “database,” “module,” “system,” and the like shall refer to a computer-related entity, whether hardware, firmware, a combination of hardware and software, software, or running software. For example, a module may be, but is not limited to, a process running on a processor, a processor, an object, an executable, an execution thread, a program, and / or a computer. By way of illustration, both an application running on a computing device and the computing device itself may be a module. One or more modules may reside within a process and / or execution thread, and a module may be located on a computer and / or distributed among two or more computers. Furthermore, Petition 870260000329, dated 05 / 01 / 2026, pages 39 / 48 32 / 33 These modules can be executed from various computer-readable media, having various data structures stored in them. The modules can communicate through local and / or remote processes, such as according to a signal containing one or more data packets (for example, data from one module interacting with another module in a local system, distributed system and / or through a network, such as the Internet with other systems through the signal).

[088] In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored or transmitted as one or more instructions or code in a computer-readable medium. A computer-readable medium includes computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. A storage medium may be any available medium that can be accessed by a computer.By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other media that can be used to transport or store the desired program code in the form of instructions or data structures and that can be accessed by a computer.

[089] Furthermore, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a site, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (“DSL”), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of media.

[090] Magnetic disk and disk, as used herein, include compact disc (“CD”), Petition 870260000329, dated 05 / 01 / 2026, pages 40 / 48 33 / 33 Laser disc, optical disc, digital versatile disc (“DVD”), floppy disk, and Blu-ray disc, where magnetic discs generally reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[091] Although selected aspects have been illustrated and described in detail, it will be understood that various substitutions and alterations may be made without departing from the spirit and scope of the present invention, as defined by the following claims. Petition 870260000329, dated 05 / 01 / 2026, pages 41 / 48

Claims

1 / 6 CLAIMS 1. A secure communication method in an electronic device (144) characterized in that it comprises: receiving, in an electronic device (144) and through a second communication between the electronic device (144) and a host entity (112), a first set of device identifiers (148) from a host entity (112); generating a device identifier whitelist (121), including the first set of device identifiers (148) in response to receiving the first set of device identifiers (148) from the host entity (112), wherein the device identifier whitelist (121) allows any device with a device identifier associated with the device identifier whitelist (121) to communicate securely with the electronic device (144);detect in the electronic device (144) that a first device (144a) is within a communication range of the electronic device (144) according to one or more communication protocols, wherein the first device (144a) is distant from the electronic device (144) and the host entity (112); establish a restricted communication session with the first device (144a) based on the detection that the first device (144a) is within the communication range of the electronic device (144), wherein the restricted communication session comprises a pairing session;receive, through a first communication channel (110) between the electronic device (144) and the first device (144a), wherein the first communication channel (110) is associated with one or more communication protocols, a Petition 870260051647, dated 05 / 29 / 2026, page 9 / 14 2 / 6 for authentication including a first device identifier (148) of the first device (144a) in response to establishing the restricted communication session with the first device (144a); determine whether the device identifier whitelist (121) includes the first device identifier (148) in response to receiving the authentication request;in accordance with a determination that the device identifier allowlist (121) includes the first device identifier (148), allowing an unrestricted communication session with the first device (144a) wherein the unrestricted communication session comprises secure communication that allows one or both data synchronizations between the electronic device (144) and the first device (144a) or a status recovery of one or more messages or files from the first device (144a); and in accordance with a determination that the device identifier allowlist does not include the first identifier, terminating the restricted communication session with the first device.

2. A method according to claim 1, characterized in that it allows an unrestricted communication session with the first device (144a), includes: sending one or more addresses of the electronic device (144), an indication of driver identifier verification activation, or a workflow task message to the first device (144a).

3. Method according to claim 1, characterized in that it further comprises: receiving, on the electronic device (144), a second set of identifiers of Petition 870260051647, dated 05 / 29 / 2026, page 10 / 14 3 / 6 a host entity (112), the second set of identifiers including a second device identifier (148) associated with a second device; determining whether one or more device identifiers, including the first identifier of the first set of device identifiers (148), are missing from the second set of identifiers; and adjusting the device identifier whitelist (121) based on the determination that one or more device identifiers, including the first identifier of the first set of device identifiers (148), are missing from the second set of identifiers.

4. Method according to claim 3, characterized in that the adjustment of the device identifier allowlist (121) includes the removal of one or more device identifiers missing from the second set of device identifiers, including the first identifier from the device identifier allowlist (121).

5. Method according to claim 3, characterized in that each device identifier of the first set of device identifiers (148) including the first device identifier (148) and the second set of device identifiers including the second device identifier (148) is either a mobile directory number or a device identifier generated by the host entity (112).

6. Method according to claim 1, characterized in that receiving the first set of device identifiers (148) includes receiving a configuration message including the first set of device identifiers (148) from the host entity (112) through the first communication channel (110) or a provisioning message including the first set of identifiers from a second host entity (112) through the second communication channel, Petition 870260051647, dated 05 / 29 / 2026, p. 11 / 14 4 / 6 respectively, different from the first host entity and the first communication channel (110).

7. Method according to claim 1, characterized in that the authentication request includes a version identifier of an application running on the first device (144a), and in that determining whether the device identifier whitelist (121) includes the first device identifier (148) includes determining whether the version identifier of the application running on the first device (144a) satisfies a compatible version identifier on the electronic device (144).

8. Method according to claim 7, characterized in that allowing unrestricted communication session with the first device (144a) includes allowing communication according to a determination that the version identifier of the application running on the first device (144a) satisfies the compatible version identifier on the electronic device (144).

9. Method according to claim 1, characterized in that receiving the set of device identifiers (148) includes receiving in accordance with an over-the-air communication protocol, and wherein the over-the-air communication protocol includes a wide local area network protocol or a terrestrial protocol.

10. Method according to claim 1 characterized in that one or more communication protocols include a Bluetooth protocol or a wide local area network protocol, and wherein the electronic device (144) is coupled to a vehicle.

11. Apparatus for secure communication between devices, characterized in that it comprises: a processor (805); a memory (810) coupled to the processor (805), wherein the memory (810) includes instructions executable by the processor (805) to: receive, through a second communication channel between the electronic device (144) and a host entity (112), a first set of device identifiers (148) from a host entity (112);generate a device identifier allowlist (121), including one or more device identifiers from the first set of device identifiers (148) in response to receiving the first set of device identifiers from the host entity, wherein the device identifier allowlist (121) allows any device with a device identifier associated with the device identifier allowlist (121) to securely communicate with the electronic device (144); detect that a first device (144a) is within communication range of the electronic device (144) according to one or more communication protocols, wherein the first device (144a) is distant from the electronic device (144) and the host entity (112);establish a restricted communication session with the first device (144a) based on the detection that the first device (144a) is within the communication range of the electronic device (144), wherein the restricted communication session comprises a pairing session; receive, through the first communication channel (110) between the electronic device (144) and the first device (144a), wherein the first communication channel (110) is associated with one or more communication protocols, an authentication request including a first device identifier (148) of the first device (144a) in response to the establishment of the restricted communication session with the first device (144a); Petition 870260051647, dated 05 / 29 / 2026, p. 13 / 14 6 / 6 determine whether a device identifier whitelist (121) includes the first device identifier (148) in response to receiving the authentication request;in accordance with a determination that the device identifier allowlist (121) includes the first device identifier (148), allowing an unrestricted communication session with the first device (144a), wherein the unrestricted communication session comprises a secure connection that allows one or both data synchronizations between the electronic device (144) and the first device (144a) or a status recovery of one or more messages or files from the first device (144a); and in accordance with a determination that the device identifier allowlist (121) does not include the first identifier, terminate the restricted communication session with the first device (144a).

12. Device according to claim 11, characterized in that to allow an unrestricted communication session with the first device (144a), the memory (810) also includes instructions executable by the processor (805) to: send one or more addresses of the electronic device (144), an indication of activation of driver identifier verification or a workflow task message to the first device (144a).

13. Computer-readable medium for secure communication between devices, characterized in that the computer-readable medium comprises instructions that, when executed by a computer, cause the computer to execute the method as defined by any one of claims 1 to 10. Petition 870260051647, dated 05 / 29 / 2026, p. 14 / 14

Images