CN112469000A - System and method for vehicle network service on 5G network - Google Patents

Abstract

In a vehicle-to-infrastructure (V2I) communication, vehicle-oriented broadcast data must efficiently utilize network resources, while unicast data must reliably arrive with ultra-low latency. Furthermore, when the vehicle is moving quickly, the connection must remain network connected. A system/method is described by which a vehicle has a particular communication module and an internal computer. May be connected to one or more 5G Vehicle Network Slices (VNs) via multiple radio access technologies (multi-RATs) for efficient communication with local or remote traffic information databases and applications, road safety and emergency infrastructure. The infrastructure of the present invention uses the network slicing function of a 5G mobile network to segment vehicle data and control airplanes, providing vehicle services exclusively.

Description

System and method for vehicle network service on 5G network

Technical Field

The present invention relates generally to radio technology, and more particularly to 5G, for providing an efficient network infrastructure specifically designed to support intelligent transportation and connected vehicles using network slices.

Background

The automotive industry is striving to realize the dream of networking automobiles. With the functionality and speed provided by 5G mobile networks, highly intelligent traffic will be possible. So-called "networked vehicles" are expected to communicate with other vehicles (vehicle-to-vehicle-V2V) and one or more traffic information centers (also referred to as "infrastructure" (vehicle-to-infrastructure-V2I)) in the next decade. These centers can quickly estimate traffic density, direct vehicles to different congested routes, provide vehicle software updates, change the schedules of mass transit vehicles, and receive accident reports immediately (even if the driver has no conditions to make a call). Instead, the car will transmit important analytical data, GPS, camera and sensor data, ambient traffic information, etc., or receive data from other vehicles and the public internet. In addition, unmanned vehicles will soon emerge, utilizing the traffic information infrastructure of the network and its own intelligent road monitoring and assessment capabilities.

Vehicle-to-vehicle (V2V) communications using wireless networks such as VANET have been widely explored in the prior art, particularly in the academic world. In addition, it is a popular research topic to estimate a steering angle and a vehicle speed by autonomous (unmanned) driving, image processing, and a deep learning technique (based on a neural network) using a camera mounted on an automobile. However, vehicle-to-infrastructure (V2I) communications have not been widely explored until recently due to the lack of wireless communication infrastructure to support such fast moving objects, and the large amount of information exchange between moving objects and the network. Obviously, the vehicle must act as a special radio access endpoint to wirelessly access the functionality provided by the traffic information infrastructure on the public internet. With the advent of global positioning systems, accurate positioning of vehicles and analysis of entire road traffic is now even possible. In addition, cameras and sensors mounted on the vehicle can provide useful information about the surrounding vehicle.

Compared with users of other mobile devices such as smart phones, the network usage characteristics of vehicles are different:

(1) the vehicle is moving rapidly.

(2) They transmit (send and receive) data periodically. In the special case of unmanned driving, some level of data interaction may be required.

(3) The traffic information sought does not vary much. On a macroscopic level, the speed and density of network traffic is usually predictable.

(4) The vehicle searches for information of both unicast and broadcast types. The unicast information is vehicle specific. The broadcast type of information is traffic specific.

(5) Part or most of the transportation information (such as new routes, orders or accident reports) must be delivered with ultra low delay and high reliability.

(6) Most traffic information is localized.

Network slices are the basis of 5G networks. Using Software Defined Networking (SDN) concepts, the 5G infrastructure can be intelligently partitioned into virtual control and data plane network functions (including RAN). Each slice can work independently of the rest of the network, like a virtual network with dedicated resources. This can meet the requirements of different traffic types and services. Each individual network function in a slice is conceived as a Virtual Network Function (VNF) that can be widely distributed in the network, instantiated as and when needed, and capacity adjusted as and when needed. The grouping of these network functions forms a slice, follows different policies, and provides a particular quality of service. Any User Equipment (UE) may use a special field in the registration request message to signal the network with the required network slice during the connection.

With these concepts, one or more Vehicle Network Slices (VNs) may provide vehicle services. Multiple VNCs may be required due to different requirements for different modes of transportation. In view of the above-mentioned features of vehicle data traffic, the following are two embodiments of implementing the VNS: in one embodiment, it is envisaged that the vehicle network slice consists of (1) an "edge" network function geographically located at the roadside and dedicated solely to vehicle communication, and (2) an "interior" network function geographically remote from the roadside, overlaid on the 5G core network. In another embodiment, the network functions of the vehicle service are not dedicated, but are a superposition of the 5G core network, in which case the network functions of the core must be widely distributed, including those "edges" near the roadside. Thus, certain core network functions located at the edge may be split to provide vehicular services. The slicing concept substantially eliminates the need for vehicle network functions only for vehicle services.

The above-mentioned dedicated edge components must be inexpensive because they will be deployed in a large, versatile and efficient manner to eliminate most of the data traffic burden from the core network and the internet.

The vehicle transportation information infrastructure may include a 5G network of one or more mobile operators, each operator providing a VNSS with the same definition, but managed by the municipality. In another embodiment, it may be a pay-for-subscription service of a single operator. When multiple operators provide vehicle services, each vehicle must be able to connect to the multiple operators' networks.

Term(s) for

AP Access Point

AMF Access and mobility management functionality

CN core network

CP control plane

DL-Downlink

eBBF for enhancing mobile broadband function

gNB:5g-NodeB

GPS-global positioning system

NAI network access identity

NF network function

NSSF network slice selection function

NSSAI network slice selection assistance information

PCF policy control function

PEI permanent device ID

QoS-quality of service

(R) AN radio access network

RSAU road side passing device

SBA service-based architecture

SDN software defined network

SMF session management function

S-NSSAI Single-network-chip selection assistance information

SSC service and session continuity

SST image/service type

SUPI subscription permanent identifier

UL: upstream paths

UL CL uplink classifier

UPF user plane function

UDR unified data repository

V2V vehicle-to-vehicle

V2I vehicle-to-infrastructure

VID vehicle ID

VIR vehicle identification registry

VIM vehicle identification module

VNF virtual network function

VTNF virtual traffic network functionality

Vs. and vehicle slices

VSM vehicle slice manager

Embodiments of the present invention are an improvement over prior art systems and methods.

Disclosure of Invention

In one embodiment, the invention provides a method implemented in a mobile network communication infrastructure enabling communications in a vehicle having wireless network access capability and capable of connecting to a plurality of operators, the mobile network communication infrastructure comprising at least one first and second operator, the first operator having a first default slice associated with its core network, the second operator having a second default slice associated with its core network, the first and second operators further having third and fourth slices, respectively, wherein each of the third and fourth slices: (1) having the same attributes between the first and second operators; (2) contain partitioned network capabilities specific to providing vehicle services, and (3) include network functions that are physically separate from the first default slice and the second default slice, or network functions whose resources are shared with the same or different functions of the first default slice and the second default slice; the method comprises the following steps: (a) sending the registration request message and the attached vehicle to a first Access and Move Function (AMF) associated with a first default slice of a first operator in accordance with the registration request message, wherein the registration request message includes an indicator indicating that attachment to the fourth slice is desired; (b) a first AMF that verifies an identity of the vehicle from the registration request message; (c) after successful verification in (b), the first AMF redirecting the registration request message to a second AMF of a second default slice associated with a second operator; (d) the second AMF querying the vehicle ID registry database for the vehicle identification and authorizing the vehicle; (e) the second AMF then queries the policy control function to obtain a vehicle policy directive and instructs the vehicle to use the fourth piece of network functionality in accordance with the vehicle policy directive.

In another embodiment, the invention provides an article of manufacture comprising a non-transitory computer storage medium storing computer readable program code which, when executed by a processor, implements a method implemented in a mobile network communication infrastructure enabling a vehicle having wireless network access capability to communicate and to connect to a plurality of operators, the mobile network communication infrastructure comprising at least one first and second operator, the first operator having a first default slice associated with its core network, the second operator having a second default slice associated with its core network, the first and second operators further having third and fourth slices, respectively, wherein each of the third and fourth slices: (1) having the same attributes between the first and second operators; (2) including zoning network capabilities specific to providing vehicle services; (3) including network functions that are physically separated from the first default patch and the second default patch, or network functions whose resources are shared with the same or different functions of the first default patch and the second default patch; the computer storage medium includes: (a) computer readable program code in the vehicle for sending a registration request message and appending the registration request message to a first Access and Mobility Function (AMF) associated with a first default slice of a first operator in accordance with the registration request message, wherein the registration request message includes an indicator indicating that it is desired to append to the fourth slice; (b) computer readable program code in the first AMF for verifying the identity of the vehicle from the registration request message; (c) after successful verification in (b), computer readable program code in the first AMF redirects the registration request message to a second AMF associated with a second slice of a second operator; (d) computer readable program code in the second AMF for querying the vehicle ID registration database for the identity of the vehicle and authorizing the vehicle; (e) computer readable program code in the second AMF then queries the policy control function to obtain a vehicle policy directive and directs the vehicle to use the fourth piece of network functionality in accordance with the vehicle policy directive.

In a further embodiment, the present invention provides a method implemented in a mobile network communications infrastructure enabling communications for vehicles having radio access capability and capable of connecting to a plurality of operators, the mobile network communications infrastructure of each of a plurality of operators consisting of a first default slice and a set of slices associated with its core network, wherein: (1) using each slice in a set of slices of a different set of virtual data plane network functions, such that each slice has a different partitioned network function specific to providing an aspect of vehicular service, (2) a set of slices consisting of network functions that are physically separate from the first slice or network functions that share resources the same or different from the first slice, the method comprising: (a) the vehicle sends a registration request message and appends it to a first Access and Mobility Function (AMF) associated with a first default slice in accordance with the registration request message, wherein the registration request message includes an indicator indicating a desire to use a service of one or more slices of the set of slices; (b) a first AMF in communication with a Network Slice Selection Function (NSSF), and identifying a second AMF associated with a second slice of the set of slices closest to the vehicle to trigger a redirect action of the registration request message for each particular service type in the indicator; (c) the first AMF redirects the registration request message to the second AMF; (d) the second AMF querying the vehicle ID registry database for vehicle identification and authorizing vehicles in the second slice identified in (b); (e) the second AMF then queries the policy control function to obtain a vehicle policy directive and instructs the vehicle to use the second piece of network functionality identified in (b) in accordance with the vehicle policy directive.

Drawings

The present invention, in accordance with one or more various examples, is described in detail with reference to the following figures. The drawings are provided for illustration only and merely depict disclosed examples. These drawings are provided to facilitate the reader's understanding of the disclosure and should not be taken as limiting the breadth, scope, or applicability of the disclosure. It should be noted that for clarity and ease of illustration, the drawings are not necessarily drawn to scale.

FIG. 1 is a high level block diagram of a mobile network with vehicular services in accordance with the present invention.

Fig. 2 shows a block diagram of an RSAU according to the invention.

Fig. 3 and 4 illustrate two additional physical embodiments of the RSAU.

FIG. 5 illustrates a high-level block diagram of an in-vehicle communication and processing module (IVCU) in accordance with the present invention.

Fig. 6 illustrates an exemplary messaging sequence.

Detailed Description

While the invention has been illustrated and described in its preferred embodiments, the invention can be produced in a number of different configurations. A preferred embodiment of the present invention is illustrated in the accompanying drawings and will be described herein in detail as an example of the principles of the invention and its associated functional specifications. The invention is not intended to be limited to the embodiments shown. Those skilled in the art will envision many other possible variations that are within the scope of the invention.

Note that in this specification, reference to "one embodiment" or "an embodiment" means that the feature being referred to is included in at least one embodiment of the invention. Furthermore, separate references to "one embodiment" in this specification do not necessarily refer to the same embodiment; however, unless so stated and as would be readily understood by one of ordinary skill in the art, neither embodiment is mutually exclusive. Thus, the invention may include any combination or integration of the embodiments described herein.

An electronic device (e.g., a base station, agent, or controller) uses a machine-readable medium to store and transmit (either internally or over a network with other electronic devices) code (comprised of software instructions) and data, such as a non-transitory machine-readable medium (e.g., a machine-readable storage medium such as a magnetic disk; an optical disk; a read-only memory; a flash memory device; a phase-change memory) and a transitory machine-readable transmission medium (e.g., an electrical, optical, acoustical or other form of transmitted signal, such as a carrier wave, an infrared signal). Further, such electronic devices include hardware, e.g., a set of one or more processors coupled to one or more other components, e.g., one or more non-transitory machine-readable storage media (storing code or data) and network connections (transmitting code or data using propagated signals); and user input/output devices (e.g., keyboard, touch screen, or display). The coupling of a set of processors and other components is typically achieved through one or more interconnects within the electronic device (e.g., a bus and possibly a bridge). Thus, a non-transitory machine-readable medium of a given electronic device typically stores instructions that are executed on one or more processors of the electronic device. One or more portions of embodiments of the invention may be implemented using different combinations of software, firmware, or hardware. As used herein, a network device is a portion of a network device that includes hardware and software that communicatively interconnects with other devices on the network (e.g., other network devices, end systems). A network device is typically identified by its Media Access (MAC) address, Internet Protocol (IP) address/subnet, network socket/port, or upper OSI layer identifier.

A Radio Access Network (RAN) is typically comprised of one or more base stations. The base station provides cellular connectivity for User Equipment (UE) to the mobile operator core network. The base station is connected to an antenna (or multiple antennas) that receives and transmits signals in a cellular network to cellular telephones and other cellular devices. The RAN is connected to the Core Network (CN) of the mobile operator for end-to-end data transfer.

The network function is typically a software function implemented on a computer. One or more network functions may be hosted on the same computer. Network functions may be instantiated, terminated or capacitively, remotely or locally.

Fig. 1 shows a possible block diagram for implementing vehicle network services to a vehicle network slice using core network functionality. These core network functions are included in the architecture to provide more sophisticated management of the RAN, authentication of the VIR 152, different charging and billing means, and connectivity to various operator base stations. As shown, when the vehicle 100 attempts to receive vehicle services, it must first connect to the RAN 110, including the RSAU 111, and optionally the macro 3GPP operator base station 112, the non-3 GPP access point 113, and even the macro 5G base station (not shown), for various possible wireless connection options. RSAU 111 may contain a resident VTNF, but standby radio access units 112 and 113 do not necessarily contain any resident VTNF.

Fig. 1 illustrates a default (home) operator core network element 140, as well as network elements of vehicle slices in the vehicle control plane 130 and the vehicle data plane 120. Note that only a subset of the core network functions for routing control traffic to the vehicle control plane 130 are illustrated in 140. The core network also has many other core network functions for serving other types of users, but are not illustrated in 140 because they do not involve redirecting traffic to the vehicular network slices. For all SIM card based authentication with SUPI or IMSI identity, the operator's Unified Data Management (UDM) 144 is used. Operator access and mobility management function (AMF) 143 and Session Management Function (SMF) 141 entities provide services to all operator users, while they also assist in routing and redirection of vehicle service operations.

The Network Slice Selection Function (NSSF) 142 is an important function provided by 5G, indicating slice (service type) specific configuration to the AMF 143 during UE registration request with a newly defined field called slice type (sst) in the network slice selection assistance information field (NSSAI) of the message. Using different SST values, the vehicle can specify the need to attach to different types of network slices. There are standard or service specific SST values. For example, broadcast data, ultra-reliable, low latency, and large-scale internet of things are a few examples of standard slices. Further, the UE may specify a desire to attach to multiple virtual network slices in one registration request to the AMF 143.

The connection module of the vehicle first attempts to connect to the network by contacting the AMF 143 of the operator. The AMF 143 then checks the SST field of the NSSAI and sends an additional request to the AMF133 of the vehicle controlling aircraft 130 according to the redirection recommendation of the NSSF 142. If multiple such AMFs are deployed, AMF133 is most likely to be selected as the AMF closest to the slice of the vehicle. For example, the location of the vehicle can be easily determined from the location of the base station that sent the request.

The vehicle control aircraft 130 may include its dedicated AMF133 to provide flexible and quick service to the vehicle in one embodiment. The AMF133 performs user attachment procedures by validating the UDM 144, retrieves applicable vehicle access policies from the sliced Policy Control Function (PCF) 132, and performs vehicle subscription control for the VIR 152. Device access control based on VIR 152 may be handled using 5G device identification register (5G-EIR) network functions, as described in 5G. The Session Management Function (SMF) 131 handles data sessions for vehicle traffic using only gateways provided in the vehicle data plane 120. Traffic routes towards data plane functions are known in the art.

The vehicle data plane 120 is capable of routing data traffic between the vehicle and the Virtual Transport Network Function (VTNF) 153 and between the Vehicle Application Plane (VAP) 150 or VNTFs present in the public internet 160, depending on the use of the gateway 121 (referred to as UPF in 5 g). The regional broadcast data is routed to the vehicles through a broadcast gateway 122 (LTE called MBMS, 5G called EMBF). In addition, the operator assisted non-3 GPP access point 113 can extend the coverage of vehicular services by using a non-3 GPP gateway 123 (referred to as N3IWF for 5G).

The vehicle application plane 150 is comprised of a Vehicle Slice Manager (VSM) 151, a VIR 152, and a VTNF153 (VTNF). The VSM 151 is the brain of all vehicle slices, which, depending on their service type, assists the AMF133 and PCF 132 in obtaining access profiles for the vehicle (e.g., what they can request and receive). In an additional process, the vehicle user has the responsibility to indicate the type of service/slice needed by displaying the slice type using the SST field. Each vehicle user may be simultaneously connected to multiple vehicle slices, each slice providing a different QoS. PCF 132 provides different access control policies based on slice type (i), (ii) AMF133 assigns different frequency priorities/unit reselection parameters to vehicles by sending this information to RSAU 111. The VIR 152 uses the IMEI/PEI related access and service changes to authenticate the vehicle.

Depending on the particular vehicle slice implementation, there may be one or more VDPs 120. If desired, the operator's AMF 143 can easily point to different AMFs 133 for different slice types indicated in the SST field. VTNFs configured with RSAU may also be provided in the operator's shared core network to minimize delay and improve reliability. One of the remote VTNFs may provide the service if the RSAU is unable to reach its local VTNF.

There are various implementations of the RSAU 111, VDP 120, VCP 130, and VAP 150. A simple "unitary" embodiment of the RSAU330 is depicted in fig. 2. The RSAU330 includes radio access capabilities as well as all private vehicle data plane and application plane functions. It consists of (i) a multi-mouse access 111, sensor and camera 303, a system management console 301 in subcomponent 310 and (ii) VDP 120, VCP 130 and VAP 150 and a local caching application 308 in subcomponent 312. Data connection 176B extends to operator core network 140 and remote VTNF 190. The data connection 176C extends to the public Internet 160 and Internet applications 191. Control connection 175A handles control traffic.

Fig. 3 and 4 compare two other useful implementations with an "all-in-one" RSAU. In fig. 3, the RSAU 310B consists of only the multi-mouse access 111, sensors, and camera 303, and the system management console 301 is actually a subcomponent 310 of fig. 2. Sub-component 312, however, is deployed on another computer, serving both RSAUs 310A and 310B. In fig. 4, in addition to the VAP, a subcomponent 312 is deployed as an overlay to the core network 140. For example, AMF133 runs on AMF 143, SMF 131 runs on SMF 141, PCF 132 runs on a PCF function of the operator's core network, and so on. The dedicated vehicle application plane 150 with the VIR, VSM and VTNF is distributed over the network near the edge or may be maintained in the application function and network function repository of the operator 5G core network 140. The architecture does not require any dedicated resources to implement the virtual network functions of the core network.

Since the RSAU is a special access unit designated for the vehicle, the conventional mobile subscriber accesses the mobile network by connecting to the nearest gNB or ENB. In more economical cases, the GNBS may also be directly connected to the vehicle without the need of a RSAU, as shown in fig. 1.

A complete vehicle service infrastructure starts with the vehicle, which must simply have the in-vehicle communication and processing unit 200 of the Multi-RAT communication interface module 201 and a computer as shown in fig. 5. Although not all of the system components have been described, some key elements are included for a better understanding of the remainder of the invention. Subassembly 201 provides V2V and V2I wireless connections through modules 212 and 211, respectively. These radio connections may use different technologies. For V2I communication, each vehicle must identify itself over the network and register with a permanent vehicle ID contained in its Vehicle Identification Module (VIM). In one embodiment, the location of the VIM may be completely obscured within the vehicle and therefore cannot be removed. For example, if the VIM is removed, the vehicle's computer may stop functioning. In another embodiment, the VIM information may be fully embedded in the computer. VIM allows lost, stolen (even government vehicles) easy tracking of routes.

The vehicle may also contain a traffic control unit 202 that includes various components for relative or absolute position reporting, such as sensors and cameras 231 and GPS 235. The traffic data processing unit 237 processes information from other vehicles and infrastructure. The traffic application 239 is a set of applications that rely on real-time traffic information to determine various requests, such as traffic information on alternate routes, other routes, etc. The vehicle control application 233 provides control feedback to the mechanical steering and braking system based on the processed traffic data. The vehicle system may optionally contain non-transportation applications 203 such as audio/video entertainment 221, finders (gas stations, post offices, restaurants, etc.) 222, and weather 224. Although the V2V and V2I communication interfaces are shown separately, in another embodiment they may be the same interface. It may also contain an audiovisual driver interface 205 and a vehicle control interface 204 towards the car brake and steering system.

The Vehicle Identification Module (VIM) may have a MAC address and another user permanent id (supi) for mobile communications. For a 5G core, the VIM may be implemented as a 5G-EIR or/and Unified Data Repository (UDR), or may be implemented as a separate network function. In one embodiment, the SUPI may be a special address type assigned only to the vehicle. At vehicle registration, vehicle SUPI is assigned to each vehicle's VIM card. In one embodiment, the allocation of vehicle SUPI is independent of the home mobile operator. The municipality (or appropriate road traffic organization) may perform this task when providing vehicle license plates.

The identification of each connected vehicle, referred to as "vehicle id (vid)", is a special data record. The VID enters an electronic database called a Vehicle ID Register (VIR). An exemplary VID is as follows:

vehicle IMEI/PEI;

a vehicle permanent identification number;

a vehicle license plate;

vehicle make and model;

unmanned or conventional vehicles;

the name of the vehicle owner;

a vehicle owner registration phone;

other optional fields

The VIR is a repository that all mobile operators can access to verify and authenticate vehicles. There may be a national virus associated with viruses in other countries. When the vehicle attempts to connect to the RSAU in the 5G network, the control plane function may send a special identity request to the vehicle in response to the VID (or portion thereof) sent by the vehicle. If the VID is a valid record in the VIR, the user is authenticated. This function is specific to the vehicle slice. All operators must always have access to the VID. The VIR may be a database managed by the municipality because new vehicles are added to the road, license plates are replaced, etc., and may be globally synchronized with other similar databases.

Fig. 6 illustrates exemplary additional routines through the vehicle data and control planes 120 and 130, respectively. When the communication module of the vehicle 100 attempts to connect to any of the operational units in block 110 of fig. 1, its registration request is most likely sent to the nearest operator AMF 143. The request includes a slice selection by the vehicle user. These slice selections may include one or more of the following service types:

(1) V2V and V2I delay sensitive traffic: such traffic may be initiated or managed by the distributed VTNF. Autonomous vehicles and emergency situations require such QoS.

(2) Regional broadcast traffic information: the vehicle service network provides traffic information to all vehicles in the area through a broadcast channel according to the connected base station.

(3) Passive GPS positioning acquisition: as a vehicle Internet of things service, the position of each vehicle can be regularly collected for safety.

(4) And (3) internet connection: the vehicle communication module acts like a mobile internet gateway to provide connectivity for vehicle applications and vehicle occupants.

Each service type is represented by the vehicle communication module as S-NSSAI in the registration request. When the AMF 143 receives the additional request, it queries the NSSF 142 to obtain slice-specific information. The slice query includes all NSSAI slices requested by the vehicle user. The NSSF 142 retains slice-specific AMF, SMF, UPF, local area network (LADN) identities. Accordingly, the NSSF responds to the vehicle slice query with the identity of the vehicle AMF133, and then forwards additional requests from the AMF 143 to the vehicle AMF 133. If the vehicle is capable of connecting to multiple operators, the AMF 143 may belong to one operator while the AMF133 belongs to another operator. This may be true if multiple operators support vehicle services. Each slice of vehicular service implemented by multiple operators must have the same (or similar) slice attributes. However, typically, AMFs 143 and 133 belong to the same operator. When the vehicle AMF133 receives the request, it executes additional procedures through the vehicle PCF 132 and the operator's UDM 144. It also queries the VIR 151 database using the permanent address of the vehicle communication module (IMEI/PEI number) for further access and service control. This additional authentication may allow for service changes related to the device type.

In-vehicle AMF133 performs policy queries on PCF 132. In this way, the AMF133 acquires service tracking area information, which can be used for access control between different base station layers. That is, depending on the slice type, in the attach procedure, the vehicle may be forced to attach only to the macro base station or only to the RSAU by transmitting a corresponding Tracking Area (TA) code to the user. The user may receive a set of allowed and disallowed service (tracking) areas.

As can be seen from fig. 6, if a vehicle requests only area broadcast traffic information slices, it may be forced to connect only to tracking area 1 (TA 1) by the macro base station 112 of fig. 1 to reduce cell reselection/handover. However, if the vehicle requests fragmented delay sensitive traffic, it is more advantageous to connect to tracking area 2 (TA 2) through RSAU 111 to reach localized VTNF and locally routed v2v traffic.

Finally, the AMF133 may also provide user-specific cell reselection and frequency priority to the operating base stations. By using these additional parameters, the mobility of the user may be further enhanced for each type of slice. For example, using the PCF 132, a vehicle user may request initiation of a Mobile only initiated connection (MICO) mode. This mode allows the user to send and receive data only when a connection is attempted, so that the user does not need to maintain the connection. The MICO mode prevents the communication module from unnecessarily listening to paging messages and tracking cell reselection simultaneously if the user only wants to send his GPS data and does not expect any downlink traffic.

Many of the features and applications described above can be implemented as software processes that are specified as a set of instructions recorded on a computer readable storage medium (also referred to as computer readable medium). When executed by one or more processing units (e.g., one or more processors, processor cores, or other processing units), these instructions cause the processing unit to perform the operations indicated in the instructions. Embodiments within the scope of the present invention may also include tangible or non-transitory computer-readable storage media for carrying or having computer-executable instructions or data structures stored thereon. Such non-transitory computer-readable storage media can be any available media that can be accessed by a general purpose or special purpose computer, including the functional design of any special purpose processor. By way of example, and not limitation, such non-transitory computer-readable media can comprise flash memory, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of computer-executable instructions, data structures, or a processor chip design. Computer-readable media do not include carrier waves and electronic signals through a wireless or wired connection.

Computer-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Computer-executable instructions also include program modules that are executed by computers in stand-alone or network environments. Generally, program modules include routines, programs, components, data structures, objects, and functions inherent in the design of special-purpose processors, etc. that perform particular tasks or implement particular abstract data types. Computer-executable instructions, associated data structures, and program modules represent examples of the program code means for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps.

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and the processors of any one or more digital computers. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor that executes or carries out instructions, and one or more memories that store instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such a device. Moreover, a computer may be embedded in another device, e.g., a mobile telephone, a Personal Digital Assistant (PDA), a mobile audio or video player, a game player, a Global Positioning System (GPS) receiver, or a portable storage device (e.g., a Universal Serial Bus (USB) flash drive), to name a few.

In this specification, the term "software" is meant to include firmware located in read-only memory, or applications stored in magnetic or flash memory, such as a solid state drive, which may be read into memory for processing by a processor. Further, in some implementations, multiple software techniques may be implemented as sub-parts of a larger program, while preserving the different software techniques. In some implementations, multiple software techniques may also be implemented as a single program. Finally, any individual program or programs that combine to implement the software techniques described herein are within the scope of the subject technology. In some implementations, one or more specific machine implementations are defined that perform the operations of the software program when the software program is installed for execution on one or more electronic systems.

A computer program (also known as a program, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. The computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

The above-described functions may be implemented in digital electronic circuitry, computer software, firmware, or hardware. The techniques may be implemented using one or more computer program products. The programmable processor and computer may be included in or packaged as a mobile device. The processes and logic flows can be performed by one or more programmable processors and one or more programmable logic circuits. General purpose and special purpose computing devices and storage devices may be interconnected by a communication network.

Some implementations include electronic components, such as microprocessors, memory, and storage, that store computer program instructions in a machine-readable or computer-readable medium (alternatively referred to as a computer-readable storage medium or machine-readable storage medium).

Some examples of such computer-readable media include RAM, ROM, compact disk read-only (CD-ROM), compact disk recordable (CD-R), compact disk rewritable (CD-RW), digital versatile disk read-only (e.g., DVD-ROM, dual-layer DVD-ROM), various DVD recordable/rewritable (e.g., DVD-RAM, DVD-RW, DVD + RW, etc.), flash memory (e.g., SD cards, mini-SD cards, micro-SD cards, etc.), magnetic or solid-state hard disks, Blu-ray disks both read-only and recordable, ultra-density optical disks, any other optical or magnetic media, and floppy disks. The computer-readable medium may store a computer program that is executable by at least one processing unit and includes sets of instructions for performing various operations. Examples of computer programs or computer code include, for example, machine code (e.g., generated by a compiler) and files (including higher level code that are executed by a computer, electronic components, or microprocessor using an interpreter).

Although the above discussion has primarily referred to microprocessor or multi-core processors executing software, some implementations are performed by one or more integrated circuits, such as Application Specific Integrated Circuits (ASICs) or Field Programmable Gate Arrays (FPGAs). In some implementations, such integrated circuits execute instructions stored on the circuit itself.

As used in this specification and any claims of this application, the terms "computer-readable medium" and "computer-readable medium" are entirely limited to tangible physical objects that store information in a form readable by a computer.

These terms do not include any wireless signals, wired download signals, and any other transitory signals.

Claims (10)

1. A system and method of vehicle network services over a 5G network enabling a vehicle with wireless network access capability to communicate and to connect to a plurality of operators, a mobile network communication infrastructure comprising at least one first and second operator, the first operator having a first default slice associated with its core network, the second operator having a second default slice associated with its core network, the first and second operators further having third and fourth slices, respectively, wherein each of the third and fourth slices: (1) having the same attributes between the first and second operators; (2) contain partitioned network capabilities specific to providing vehicle services, and (3) include network functions that are physically separate from the first default slice and the second default slice, or network functions whose resources are shared with the same or different functions of the first default slice and the second default slice; the method comprises the following steps: (a) the vehicle sending a registration request message and attaching to a first Access and Mobility Function (AMF) associated with the first default slice of the first operator based on the registration request message; wherein the registration request message includes an indicator indicating that attachment to the fourth tile is desired; (b) a first AMF that verifies an identity of the vehicle from the registration request message; (c) after successful verification in (b), the first AMF redirecting the registration request message to a second AMF of a second default slice associated with a second operator; (d) the second AMF querying the vehicle ID registry database for the vehicle identification and authorizing the vehicle; (e) the second AMF then queries the policy control function to obtain a vehicle policy directive and instructs the vehicle to use the fourth piece of network functionality in accordance with the vehicle policy directive.

2. The method of claim 1, wherein the network function comprises a dedicated virtual network traffic function including traffic-related data and logic, wherein the dedicated virtual network traffic function is distributed within a core network but is for vehicles only.

3. The method of claim 1, wherein the vehicle first connects to a distributed Radio Access Network (RAN) through a multi-radio access technology distributed to a highway edge, the RAN further comprising 5G, 4G, 3G, and WiFi radio access capabilities.

4. The method of claim 3, wherein each distributed operation employs multiple radio access technologies, further comprising positioning and dedicated slice network functions.

5. The method of claim 3, wherein the plurality of distributed RANs with multiple radio access technologies are served by an independent system consisting of dedicated slicing network functions.

6. The method of claim 3, wherein a plurality of distributed RANs with multiple radio access technologies are further connected to a core network, wherein the slice network function is one overlay.

7. The method of claim 1, wherein the vehicle ID registrar is a database containing data relating to each vehicle, said data comprising a vehicle permanent ID selected from the following: IMEI, PEI and MAC address, where the permanent ID is assigned to each vehicle and stored in the vehicle at the time of manufacture.

8. The method of claim 1, wherein the vehicle ID registrar is a database implemented as any one of: 5G-EIR, 5G-UDR or a separate network function.

9. The method of claim 1, wherein the vehicle ID registrar is a database further comprising non-permanent data selected from any of: IP address, license plate number, and owner information.

10. The method of claim 1, wherein the steps of the method are implemented in a computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to perform the method performed by all of the above network functions.

Images