# US 12,003,374 B2 · System, method, and apparatus for extra vehicle communications control > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,003,374 B2 - Document ID: US12003374B2 - Status: Granted - Kind: B2 - Application number: 17/674,309 - Filed: 2022-02-17 - Published: 2022-06-02 - Granted: 2024-06-04 - Earliest claimed: 2019-09-20 - Assignees: Sonatus, Inc. - Applicants: Sonatus, Inc. - Inventors: Yu Fang; Xuanran Zong; Jan Cardenas - Web page: https://patentgrep.com/patent/US12003374B2 ## CPC - H04W 12/37: Managing security policies for mobile devices or for controlling mobile applications - G07C 5/008: {communicating information to a remotely located station (transmission systems for measured values G08C)} - H04L 12/66: Arrangements for connecting between networks having differing types of switching systems, e.g. gateways - H04L 41/082: the condition being updates or upgrades of network functionality - H04L 41/0894: Policy-based network configuration management - H04L 41/28: Restricting access to network management systems or functions, e.g. using authorisation function to access network configuration - H04L 43/0876: Network utilisation, e.g. volume of load or congestion level - H04L 47/20: Traffic policing - H04L 61/3025: {Domain name generation or assignment} - H04L 61/4511: using domain name system [DNS] - H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL} - H04W 4/40: for vehicles, e.g. vehicle-to-pedestrians [V2P] - H04W 12/088: using filters or firewalls - H04L 41/0843: {based on generic templates} - H04L 2012/40215: {Controller Area Network CAN} - H04L 2012/40273: {the transportation system being a vehicle} - H04W 12/086: using security domains - H04W 12/67: Risk-dependent, e.g. selecting a security level depending on risk profiles - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - G07C: TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract An example system includes a mobile system having a first network zone and a second network zone of a different type than the first network zone; a policy manager circuit structured to interpret a policy comprising an external data routing description, wherein the external data routing description comprises a local domain name server (DNS) comprising a plurality of local address values for end points of the second network zone; a gatekeeper interface circuit interposed between the first network zone and a transceiver selectively couplable to an external device; and a configuration circuit structured to configure the gatekeeper interface circuit in response to the external data routing description; wherein the gatekeeper interface circuit is structured to regulate communications between end points of the first network zone and the transceiver, and to regulate communications between end points of the second network zone and the transceiver. ## Claims ### Claim 1 A system, comprising: a mobile system having a first network zone and a second network zone of a different type than the first network zone, and wherein the second network zone utilizes an IP addressing protocol; a policy manager circuit structured to interpret a policy comprising an external data routing description, wherein the external data routing description comprises: a plurality of external address values for external network access locations, each of the plurality of external address values corresponding to an end point of a plurality of end points of the second network zone; and a local domain name server (DNS) comprising a plurality of local address values for end points of the plurality of end points of the second network zone, each of the local address values corresponding to at least one non-local address value for an end point of the plurality of end points of the second network zone; a gatekeeper interface circuit interposed between the first network zone and a transceiver selectively couplable to an external device, and further interposed between the second network zone and the transceiver; and a configuration circuit structured to configure the gatekeeper interface circuit in response to the external data routing description; wherein the gatekeeper interface circuit is structured to: regulate communications between end points of the first network zone and the transceiver; regulate communications between end points of the second network zone and the transceive; and access an off-mobile system external DNS in response to a request by the end point of the plurality of end points of the second network zone to communicate with an external address value, wherein the external address value is not found on the local DNS. ### Claim 2 (depends on 1) The system of claim 1, wherein the policy manager circuit is further structured to update the local DNS in response to determining a second network zone end point address change. ### Claim 3 (depends on 1) The system of claim 1, wherein a first external address value of the plurality of external address values comprises both a corresponding IPv4 external address and a corresponding IPv6 address. ### Claim 4 (depends on 1) The system of claim 1, wherein the gatekeeper interface circuit is further configured to update the local DNS in response to the accessing the off-mobile system external DNS. ### Claim 5 (depends on 1) The system of claim 1, wherein the external data routing description comprises a local DNS comprising a plurality of local address values each corresponding to one of the end points of the second network zone, each corresponding to at least one non-local address value for the end point of the plurality of end points of the second network zone. ### Claim 6 (depends on 5) The system of claim 5, wherein at least a portion of the at least one non-local address values comprise both a corresponding IPv4 non-local address and a corresponding IPv6 non-local address. ### Claim 7 (depends on 6) The system of claim 6, wherein at least a portion of the plurality of local address values comprise a corresponding non-local address value that matches the corresponding local address value. ### Claim 8 (depends on 5) The system of claim 5, wherein the first network zone does not utilize an IP addressing protocol, and wherein the local DNS further comprises at least one local address value corresponding to one of the end points of the first network zone, and a corresponding at least one non-local address value for the at least one local address value. ### Claim 9 (depends on 8) The system of claim 8, wherein the corresponding at least one non-local address value for the at least one local address value corresponding to the one of the end points of the first network zone comprises an IP addressing protocol. ### Claim 10 (depends on 9) The system of claim 9, wherein the corresponding at least one non-local address value for the at least one local address value corresponding to the one of the end points of the first network zone comprises both a corresponding IPv4 non-local address and a corresponding IPv6 non-local address. ### Claim 11 A method comprising: interpreting, via a policy manager circuit for a vehicle having a first network zone and a second network zone, a policy comprising an external data routing description, wherein the second network zone is of a different type than the first network zone, the second network zone utilizes an IP addressing protocol, and the external data routing description comprises a local domain name server (DNS) comprising a plurality of local address values for end points of the second network zone, each corresponding to at least one non-local address value for the end points of the second network zone; responsive to the external data routing description, configuring, via a configuration circuit, a gatekeeper interface circuit; regulating, via the gatekeeper interface circuit, communications between end points of a first network zone of a vehicle and a transceiver; and regulating, via the gatekeeper interface circuit, communications between end points of a second network zone of the vehicle and the transceiver; wherein the gatekeeper interface circuit is interposed between the first network zone and the transceiver, and further interposed between the second network zone and the transceiver. ### Claim 12 (depends on 11) The method of claim 11 further comprising: determining, via the policy manager circuit, an address change of an end point of the second network zone; and updating, via the policy manager circuit, the local DNS in response to the address change. ### Claim 13 (depends on 11) The method of claim 11, wherein the external data routing description comprises an external DNS comprising a plurality of external address values for external network access locations, each corresponding to an external resource. ### Claim 14 (depends on 11) The method of claim 11, wherein the external data routing description comprises an external DNS comprising a plurality of external address values for external network access locations, each corresponding to an end point of the second network zone. ### Claim 15 (depends on 13) The method of claim 13, wherein at least a portion of the plurality of external address values comprise both a corresponding IPv4 external address and a corresponding IPv6 address. ### Claim 16 (depends on 13) The method of claim 13 further comprising: accessing, via the gatekeeper interface circuit, an off-vehicle external DNS in response to a request by an end point of the second network zone to communicate with an external address value, wherein the external address value is not found on the external DNS. ### Claim 17 (depends on 16) The method of claim 16, wherein the external data routing description comprises a local DNS comprising a plurality of local address values each corresponding to one of the end points of the second network zone, each corresponding to at least one non-local address value for the one of the end points of the second network zone. ### Claim 18 (depends on 17) The method of claim 17, wherein at least a portion of the at least one non-local address values comprise both a corresponding IPv4 non-local address and a corresponding IPv6 non-local address. ### Claim 19 (depends on 18) The method of claim 18, wherein at least a portion of the plurality of local address values comprise a corresponding non-local address value that matches the corresponding local address value. ### Claim 20 A system, comprising: a mobile system having a first network zone and a second network zone of a different type than the first network zone, and wherein the second network zone utilizes an IP addressing protocol; a policy manager circuit structured to interpret a policy comprising an external data routing description, wherein the external data routing description comprises a local domain name server (DNS) comprising a plurality of local address values for end points of the second network zone, each corresponding to at least one non-local address value for the end points of the second network zone; a gatekeeper interface circuit interposed between the first network zone and a transceiver selectively couplable to an external device, and further interposed between the second network zone and the transceiver; and a configuration circuit structured to configure the gatekeeper interface circuit in response to the external data routing description; wherein: the gatekeeper interface circuit is structured to regulate communications between end points of the first network zone and the transceiver, and to regulate communications between end points of the second network zone and the transceiver; and the external data routing description comprises a local domain name server (DNS) comprising a plurality of local address values each corresponding to one of the end points of the second network zone, each corresponding to at least one non-local address value for the one of the end points of the second network zone. ### Claim 21 (depends on 20) The system of claim 20, wherein at least a portion of the at least one non-local address values comprise both a corresponding IPv4 non-local address and a corresponding IPv6 non-local address. ### Claim 22 (depends on 21) The system of claim 21, wherein at least a portion of the plurality of local address values comprise a corresponding non-local address value that matches the corresponding local address value. ### Claim 23 (depends on 20) The system of claim 20, wherein the first network zone does not utilize an IP addressing protocol, and wherein the local DNS further comprises at least one local address value corresponding to one of the end points of the first network zone, and a corresponding at least one non-local address value for the at least one local address value. ### Claim 24 (depends on 23) The system of claim 23, wherein the corresponding at least one non-local address value for the at least one local address value corresponding to the one of the end points of the first network zone comprises an IP addressing protocol. ### Claim 25 (depends on 24) The system of claim 24, wherein the corresponding at least one non-local address value for the at least one local address value corresponding to the one of the end points of the first network zone comprises both a corresponding IPv4 non-local address and a corresponding IPv6 non-local address.