# US 12,118,879 B2 · C-V2X mobile edge computing interface for mobile services > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,118,879 B2 - Document ID: US12118879B2 - Status: Granted - Kind: B2 - Application number: 17/965,179 - Filed: 2022-10-13 - Published: 2024-04-11 - Granted: 2024-10-15 - Earliest claimed: 2022-10-07 - Assignees: T-Mobile USA, Inc. - Applicants: T-Mobile USA, Inc. - Inventors: Ming Shan Kwok; Wafik Abdel Shahid - Web page: https://patentgrep.com/patent/US12118879B2 ## CPC - G08G 1/0112: {from the vehicle, e.g. floating car data [FCD]} - G06N 3/08: Learning methods - G06N 20/00: Machine learning - G08G 1/164: {Centralised systems, e.g. external to vehicles} - G08G 1/166: {for active traffic, e.g. moving vehicles, pedestrians, bikes} - G08G: TRAFFIC CONTROL SYSTEMS (guiding railway traffic, ensuring the safety of railway traffic B61L; arrangement of road signs or traffic signals E01F9/00; radar or analogous systems, sonar systems, lidar systems specially adapted for traffic control G01S13/91, G01S15/88, G01S17/88; {radar or analogous systems, sonar systems, lidar systems specially adapted for anti-collision purposes G01S13/93, G01S15/93, G01S17/93}) - G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS ## Abstract A computer server receives messages from a computer device located in proximity to the computer server. The messages are generated by at least one vehicle and translated into IP packets using an N2 control plane interface and an N3 user plane interface implemented in the computer device. A message can include a direction of operation of a vehicle. From a mobile device, information is received describing motion of a user of the mobile device. The information includes a trajectory of the user. The mobile device and the vehicle are located at less than a threshold distance from the computer device. A potential collision is determined between the vehicle and the user based on the direction of operation of the vehicle and the trajectory of the user. An alert is sent to the mobile device indicating the potential collision. ## Claims ### Claim 1 A system comprising: at least one hardware processor; and at least one non-transitory memory storing instructions, which, when executed by the at least one hardware processor, cause the system to: receive, by a local mobile edge computer (MEC) server, at least one Internet Protocol (IP) packet describing at least one basic safety message (BSM) from a roadside unit (RSU), the at least one BSM generated by at least one on-board unit (OBU) of at least one vehicle and sent by the at least one OBU to the RSU over a direct communications (PC5) interface, wherein the at least one BSM includes a direction of operation of the at least one vehicle, wherein the RSU is located in proximity to the local MEC server, and wherein the at least one BSM is translated into the at least one IP packet using a control plane interface (N2) and a user plane interface (N3) implemented in the RSU; receive, from a mobile device, information describing motion of a user of the mobile device, wherein the information includes a trajectory of the user of the mobile device, wherein the mobile device is located at less than a threshold distance from the RSU, and wherein the at least one vehicle is operating at less than the threshold distance from the RSU; determine a potential collision between the at least one vehicle and the user of the mobile device based on the direction of operation of the at least one vehicle and the trajectory of the user of the mobile device; and send an alert to the mobile device indicating the potential collision, wherein the local MEC server implements an access and mobility management function (AMF) of a 5G core network for sending the alert to the mobile device indicating the potential collision, and wherein the local MEC server implements a unified data management (UDM) function for managing the at least one IP packet and the information describing motion of the user of the mobile device. ### Claim 2 (depends on 1) The system of claim 1, wherein the at least one IP packet is received by the local MEC server using a non-3GPP inter-working function (N3IWF) implemented in the RSU. ### Claim 3 (depends on 1) The system of claim 1, wherein the RSU, the local MEC server, and the mobile device are connected by a local area network (LAN). ### Claim 4 (depends on 1) The system of claim 1, wherein the alert is a first alert, and wherein the instructions cause the system to: send a second alert to the at least one OBU of the at least one vehicle indicating the potential collision. ### Claim 5 (depends on 1) The system of claim 1: wherein the local MEC server is connected to an Ethernet port of the RSU over an optical fiber network, and wherein the local MEC server is connected to a cloud server over a 5G Uu interface. ### Claim 6 At least one non-transitory computer-readable storage medium storing instructions, which, when executed by at least one data processor of a system, cause the system to: receive, by a local mobile edge computer (MEC) server, at least one Internet Protocol (IP) packet describing at least one basic safety message (BSM) from a roadside unit (RSU), the at least one BSM generated by at least one on-board unit (OBU) of at least one vehicle and sent by the at least one OBU to the RSU over a direct communications (PC5) interface, wherein the at least one BSM includes a direction of operation of the at least one vehicle, wherein the RSU is located in proximity to the local MEC server, and wherein the at least one BSM is translated into the at least one IP packet using a control plane interface (N2) and a user plane interface (N3) implemented in the RSU; receive, from a mobile device, information describing motion of a user of the mobile device, wherein the information includes a trajectory of the user of the mobile device, wherein the mobile device is located at less than a threshold distance from the RSU, and wherein the at least one vehicle is operating at less than the threshold distance from the RSU; determine a potential collision between the at least one vehicle and the user of the mobile device based on the direction of operation of the at least one vehicle and the trajectory of the user of the mobile device; and send an alert to the mobile device indicating the potential collision, wherein the local MEC server implements an access and mobility management function (AMF) of a 5G core network for sending the alert to the mobile device indicating the potential collision, and wherein the local MEC server implements a unified data management (UDM) function for managing the at least one IP packet and the information describing motion of the user of the mobile device. ### Claim 7 (depends on 6) The at least one non-transitory computer-readable storage medium of claim 6, wherein the at least one IP packet is received by the local MEC server using a non-3GPP inter-working function (N3IWF) implemented in the RSU. ### Claim 8 (depends on 6) The at least one non-transitory computer-readable storage medium of claim 6, wherein the RSU, the local MEC server, and the mobile device are connected by a local area network (LAN). ### Claim 9 (depends on 6) The at least one non-transitory computer-readable storage medium of claim 6, wherein the alert is a first alert, and wherein the instructions cause the system to: send a second alert to the at least one OBU of the at least one vehicle indicating the potential collision. ### Claim 10 (depends on 6) The at least one non-transitory computer-readable storage medium of claim 6: wherein the local MEC server is connected to an Ethernet port of the RSU over an optical fiber network, and wherein the local MEC server is connected to a cloud server over a 5G Uu interface. ### Claim 11 A method comprising: receiving, by a local mobile edge computer (MEC) server, at least one Internet Protocol (IP) packet describing at least one basic safety message (BSM) from a roadside unit (RSU), the at least one BSM generated by at least one on-board unit (OBU) of at least one vehicle and sent by the at least one OBU to the RSU over a direct communications (PC5) interface, wherein the at least one BSM includes a direction of operation of the at least one vehicle, wherein the RSU is located in proximity to the local MEC server, and wherein the at least one BSM is translated into the at least one IP packet using a control plane interface N2 and a user plane interface N3 implemented in the RSU; receiving, from a mobile device, information describing motion of a user of the mobile device, wherein the information includes a trajectory of the user of the mobile device, wherein the mobile device is located at less than a threshold distance from the RSU, and wherein the at least one vehicle is operating at less than the threshold distance from the RSU; determining a potential collision between the at least one vehicle and the user of the mobile device based on the direction of operation of the at least one vehicle and the trajectory of the user of the mobile device; and sending an alert to the mobile device indicating the potential collision, wherein the local MEC server implements an access and mobility management function (AMF) of a 5G core network for sending the alert to the mobile device indicating the potential collision, and wherein the local MEC server implements a unified data management (UDM) function for managing the at least one IP packet and the information describing motion of the user of the mobile device. ### Claim 12 (depends on 11) The method of claim 11, wherein the at least one IP packet is received by the local MEC server using a non-3GPP inter-working function (N3IWF) implemented in the RSU. ### Claim 13 (depends on 11) The method of claim 11, wherein the RSU, the local MEC server, and the mobile device are connected by a local area network (LAN). ### Claim 14 (depends on 11) The method of claim 11, wherein the alert is a first alert, and wherein the method comprises: sending a second alert to the at least one OBU of the at least one vehicle indicating the potential collision. ### Claim 15 (depends on 11) The method of claim 11: wherein the local MEC server is connected to an Ethernet port of the RSU over an optical fiber network, and wherein the local MEC server is connected to a cloud server over a 5G Uu interface.