Action planning and execution support device
US-2017147989-A1 · May 25, 2017 · US
US12003374B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12003374-B2 |
| Application number | US-202217674309-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 17, 2022 |
| Priority date | Sep 20, 2019 |
| Publication date | Jun 4, 2024 |
| Grant date | Jun 4, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
What is claimed is: 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. 2. 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. 3. 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. 4. 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. 5. 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. 6. 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. 7. 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. 8. 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. 9. 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. 10. 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. 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. 12. 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. 13. 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. 14. 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. 15. 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. 16. 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. 17. 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. 18. 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. 19. 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. 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
for vehicles, e.g. vehicle-to-pedestrians [V2P] · CPC title
Risk-dependent, e.g. selecting a security level depending on risk profiles · CPC title
using security domains · CPC title
using domain name system [DNS] · CPC title
Network utilisation, e.g. volume of load or congestion level · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.