EP3620030A1 - Dispositif nomade multi-accès configuré pour être porté par un véhicule et pour obtenir des mises à jour de services, d'applications ou de données d'après l'emplacement du véhicule. - Google Patents

Dispositif nomade multi-accès configuré pour être porté par un véhicule et pour obtenir des mises à jour de services, d'applications ou de données d'après l'emplacement du véhicule.

Info

Publication number
EP3620030A1
EP3620030A1 EP17908262.3A EP17908262A EP3620030A1 EP 3620030 A1 EP3620030 A1 EP 3620030A1 EP 17908262 A EP17908262 A EP 17908262A EP 3620030 A1 EP3620030 A1 EP 3620030A1
Authority
EP
European Patent Office
Prior art keywords
applications
services
route
vehicle
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP17908262.3A
Other languages
German (de)
English (en)
Other versions
EP3620030A4 (fr
Inventor
John RASANEN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Technologies Oy
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Publication of EP3620030A1 publication Critical patent/EP3620030A1/fr
Publication of EP3620030A4 publication Critical patent/EP3620030A4/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/222—Monitoring or handling of messages using geographical location information, e.g. messages transmitted or received in proximity of a certain spot or area
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/005—Moving wireless networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user

Definitions

  • An example embodiment relates generally to multi-access edge computing ("MEC") and, more particularly, to obtaining and updating services, applications, and/or data by a MEC device on a vehicle traveling along a route.
  • MEC multi-access edge computing
  • GSM-R Global System for Mobile Communications - Railway
  • ETSI European telecommunications standards institute
  • ISG industry specification group
  • FIG. la a conventional GSM-R system is illustrated.
  • This example GSM-R system includes one or more mobile devices 10 disposed on a train in communication with a core network 40 via a radio base station 20 and a radio network controller 30.
  • the current GSM-R system shown in FIG. la may have radio base stations 20 located along the train's route in communication with a core network 40 to facilitate direct communication of the mobile devices 10 with a core network 40.
  • conventional GSM- R systems may utilize a Wi-Fi or wireless local area network (“WLAN”) hosted by the train.
  • the mobile devices 50 may connect to a satellite or mobile radio network 90 via connection with a WLAN 60 hosted by the train.
  • WLAN wireless local area network
  • a wireless access point (“WAP") 70 and radio terminal 80 may facilitate this connection.
  • WAP wireless access point
  • these conventional networks illustrated in FIGS, la and lb fail to meet the requirements set forth by forthcoming broadband traffic as defined by the ETSI.
  • a passenger traveling in a train car utilizing conventional communication networks, as seen in FIGS, la and lb may be connected to a local Wi-Fi network hosted by the train.
  • the passenger may receive varying levels of service along the route, and may experience disruptions in service caused by weak or nonexistent radio or satellite coverage when the train passes through a tunnel or is blocked by elevated terrain.
  • An apparatus, method, and computer program product are provided according to an example embodiment in order to provide services, applications, or data to mobile devices on a vehicle traveling along a route.
  • An example of the disclosure may provide an apparatus embodied by a nomadic multi-access edge computing device configured to be disposed on and carried by a vehicle along a route.
  • the apparatus includes at least one processor and at least one memory including computer program code with the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to obtain services, applications, or data from a terrestrial networking entity prior to travel along the route.
  • the apparatus is also caused to report a location of the vehicle during travel along the route. In response to the location of the vehicle, the apparatus is caused to receive an update to the services, applications, or data during travel along the route, and is caused to provide access to one or more passengers of the vehicle to the services, applications, or data during travel along the route.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to obtain the services, applications, or data from the terrestrial networking entity via a wireless local area network prior to travel along the route.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to receive the update to the services, applications, or data during travel along the route via a satellite network or mobile radio network.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to obtain services, applications, or data from the terrestrial networking entity by causing a request for the services, applications, or data to be transmitted by a terrestrial MEC device with an indication of an identity of the vehicle and the route to a multi-access edge orchestrator defined by the terrestrial networking entity.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to obtain services, applications, or data from the terrestrial networking entity by causing a request for the services, applications, or data to be transmitted with an indication of an identity of the vehicle and the route to a core network gateway for forwarding to a multi-access edge orchestrator defined by the terrestrial networking entity.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to request an update to the services, applications, or data during travel along the route based on a request by the one or more passengers of the vehicle.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to provide advertising material to the one or more passengers of the vehicle based upon passenger data or the location of the vehicle along the route.
  • the apparatus of any of the above embodiments may, with the at least one memory and the computer program code, be further configured to, with the at least one processor, cause the apparatus to maintain a connection between the apparatus and a satellite network, a mobile radio network, and a wireless local area network, and provide an option to the one or more passengers of the vehicle to select which connection to utilize.
  • a method in conjunction with a nomadic multi-access edge computing device configured to be disposed on and carried by a vehicle along a route, a method is provided in accordance with another embodiment with the method including obtaining services, applications, or data from a terrestrial networking entity prior to travel along the route.
  • the method includes causing a location of the vehicle to be reported during travel along the route.
  • the method includes receiving an update to the services, applications, or data during travel along the route, and providing access to one or more passengers of the vehicle to the services, applications, or data during travel along the route.
  • the method includes obtaining services, applications or data comprising obtaining the services, applications, or data from the terrestrial networking entity via a wireless local area network prior to travel along the route.
  • the method includes receiving an updated comprises receiving the update to the services, applications, or data during travel along the route via a satellite network or mobile radio network.
  • obtaining the services, applications, or data from the terrestrial networking entity includes requesting the services, applications, or data to be transmitted by a terrestrial MEC device with an indication of an identity of the vehicle and the route to a multi-access edge orchestrator defined by the terrestrial networking entity.
  • obtaining the services, applications, or data from the terrestrial networking entity includes requesting the services, applications, or data to be transmitted with an indication of an identity of the vehicle and the route to a core network gateway for forwarding to a multi-access edge orchestrator defined by the terrestrial networking entity.
  • requesting an update to the services, applications, or data during travel along the route includes requesting an update based on a request by the one or more passengers of the vehicle.
  • the method includes providing advertising material to the one or more passengers of the vehicle based upon passenger data or the location of the vehicle along the route.
  • the method of any of the above embodiments may include maintaining a connection between the nomadic multi-access computing device and a satellite network, a mobile radio network, and a wireless local area network, and providing an option to the one or more passengers of the vehicle to select which connection to utilize.
  • a computer program product may be embodied by or otherwise utilized in conjunction with a nomadic multi-access edge computing device configured to be disposed on and carried by a vehicle along a route.
  • the computer program product comprises at least one non-transitory computer-readable storage medium having computer-executable program code stored therein with the computer-executable program code comprising program code instructions configured to obtain services, applications, or data from a terrestrial networking entity prior to travel along the route.
  • the computer executable program code portions also include program code configured to cause a location of the vehicle to be reported during travel along the route.
  • the computer executable program code portions also include program code configured to receive an update to the services, applications, or data during travel along the route, and provide access to one or more passengers of the vehicle to the services, applications, or data during travel along the route.
  • the program code instructions are configured to obtain the services, applications, or data from the terrestrial networking entity comprise program code instructions configured to obtain the services, applications or data via a wireless local area network prior to travel along the route.
  • the program code instructions are configured to cause the apparatus to receive the update to the services, applications, or data during travel along the route comprise the program code instructions configured to receive the updated via a satellite network or mobile radio network.
  • the program code instructions are configured to obtain services, applications, or data from the terrestrial networking entity comprise program code instructions configured to cause a request for the services, applications, or data to be transmitted by a terrestrial MEC device with an indication of an identity of the vehicle and the route to a multiaccess edge orchestrator defined by the terrestrial networking entity.
  • the program code instructions are configured to obtain services, applications, or data from the terrestrial networking entity comprise program code instructions configured to cause a request for the services, applications, or data to be transmitted with an indication of an identity of the vehicle and the route to a core network gateway for forwarding to a multi-access edge orchestrator defined by the terrestrial networking entity.
  • the program code instructions are configured to request an update to the services, applications, or data during travel along the route comprise program code instructions configured to request the update based on a request by the one or more passengers of the vehicle.
  • the computer-executable program code further comprise program code instructions configured to provide advertising material to the one or more passengers of the vehicle based upon passenger data or the location of the vehicle along the route.
  • the computer program product of any of the above embodiment may comprise program code instructions configured to maintain a connection between the apparatus and a satellite network, a mobile radio network, and a wireless local area network, and provide an option to the one or more passengers of the vehicle to select which connection to utilize.
  • an apparatus may be embodied by or otherwise utilized in conjunction with a nomadic multi-access edge computing device configured to be disposed on and carried by a vehicle along a route.
  • the apparatus includes means for obtaining services, applications, or data from a terrestrial networking entity prior to travel along the route.
  • the apparatus also includes means for causing a location of the vehicle to be reported during travel along the route.
  • the apparatus further includes means for, in response to the location of the vehicle, receiving an update to the services, applications, or data during travel along the route, and means for providing access to one or more passengers of the vehicle to the services, applications, or data during travel along the route.
  • the apparatus of an example embodiment further includes means for obtaining the services, applications, or data from the terrestrial networking entity comprise means for obtaining the services, applications or data via a wireless local area network prior to travel along the route.
  • the means for receiving the update to the services, applications, or data during travel along the route includes means for receiving the update via a satellite network or mobile radio network.
  • the means for obtaining services, applications, or data from the terrestrial networking entity includes means for causing a request for the services, applications, or data to be transmitted by a terrestrial MEC device with an indication of an identity of the vehicle and the route to a multi-access edge orchestrator defined by the terrestrial networking entity.
  • the means for obtaining services, applications, or data from the terrestrial networking entity includes means for causing a request for the services, applications, or data to be transmitted with an indication of an identity of the vehicle and the route to a core network gateway for forwarding to a multi-access edge orchestrator defined by the terrestrial networking entity.
  • the means for requesting an update to the services, applications, or data during travel along the route includes means for requesting the updated based on a request by the one or more passengers of the vehicle.
  • the apparatus of an example embodiment further includes means for providing advertising material to the one or more passengers of the vehicle based upon passenger data or the location of the vehicle along the route.
  • the apparatus of any of the above described embodiments may further include means for maintaining a connection between the apparatus and a satellite network, a mobile radio network, and a wireless local area network, and providing an option to the one or more passengers of the vehicle to select which connection to utilize.
  • FIG. la shows an example block diagram of a GSM-R system
  • FIG. lb shows an example block diagram of a Wi-Fi train communication system
  • FIG. lc shows an example block diagram of a nomadic network that may be specifically configured, according to an example embodiment of the present disclosure
  • FIG. 2 shows an example block diagram of a terrestrial network, according to an example embodiment of the present disclosure
  • FIG. 3 shows a block diagram of an apparatus that may be specifically configured in accordance with an example embodiment of the present disclosure
  • FIG. 4 shows a flowchart illustrating operations performed, such as by the apparatus of FIGS, lc and/or 2, in accordance with an example embodiment of the present disclosure
  • FIG. 5 shows a flowchart illustrating operations performed, such as by the apparatus of FIGS, lc and/or 2, in accordance with an example embodiment of the present disclosure
  • FIG. 6 shows a flowchart illustrating operations performed, such as by the apparatus of FIGS, lc and/or 2, in accordance with an example embodiment of the present disclosure.
  • data As used herein, the terms “data,” “content,” “services,” “information,” and similar terms may be used interchangeably to refer to information capable of being transmitted, received, and/or stored in accordance with embodiments of the present invention. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention.
  • a computing device/server is described herein to receive data from another computing device/server, it will be appreciated that the data may be received directly from the another computing device, or may be received indirectly via one or more intermediary computing devices, such as, for example, one or more servers, relays, routers, network access points, base stations, hosts, and/or the like, sometimes referred to herein as a "network.”
  • intermediary computing devices such as, for example, one or more servers, relays, routers, network access points, base stations, hosts, and/or the like, sometimes referred to herein as a "network.”
  • the data may be sent directly to the another computing device or may be sent indirectly via one or more intermediary computing devices, such as, for example, one or more servers, relays, routers, network access points, base stations, hosts, and/or the like.
  • Example software applications refer to computer-executable application software programmed to or capable of running on a processing unit of a server, computing device mobile device, or the like.
  • Example software applications may include word processors, email, calendars, shared workspaces, issue tracking, software development tools, enterprise wiki collaboration, project management, code hosting, service desks, status monitoring pages, internet browsers, collaborative spaces, text/voice/video chat, sign on identity, bug reporting, and the like.
  • the term "user profile,” “passenger profile,” and “profile” refer to a collection of preferences, settings, configurations, mobile device identifiers, data, and information associated with a specific passenger or mobile device.
  • a passenger profile refers therefore to the explicit digital representation of a passenger's identity and other data or information associated with the passenger.
  • a passenger profile configured in accordance with the present disclosure is accessible by one or more of the software applications that are supported by the mobile device or server, and, thus, may include application-specific preferences, settings, configurations, data, and information.
  • a passenger profile can be used to store a description of characteristics of the passenger and/or of the mobile device, as well as credentials and preferences of the passenger.
  • mobile computing device and “mobile device” (which may be used interchangeably) refer to computer hardware and/or software that is configured to access a service made available by a server and, among various other functions, is configured to communicate or otherwise request data from the server.
  • Example mobile devices may include a smartphone, a tablet computer, a laptop computer, a wearable device, and the like.
  • a mobile device may include a "smart device” that is equipped with chip of other electronic device that is configured to communicate with the server via Bluetooth, near field communication (NFC), Wi-Fi, third generation (3G), fourth generation (4G), fifth generation (5G), radio frequency identification (RFID) protocols, and the like.
  • a mobile device may include an object that is equipped with a Wi-Fi radio that is configured to communicate with a Wi-Fi access point that is communicably connected with a server.
  • circuitry refers to (a) hardware-only circuit implementations (e.g., implementations in analog circuitry and/or digital circuitry); (b) combinations of circuits and computer program product(s) comprising software and/or firmware instructions stored on one or more computer readable memories that work together to cause an apparatus to perform one or more functions described herein; and (c) circuits, such as, for example, a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation even if the software or firmware is not physically present.
  • This definition of 'circuitry' applies to all uses of this term herein, including in any claims.
  • the term 'circuitry' also includes an implementation comprising one or more processors and/or portion(s) thereof and accompanying software and/or firmware.
  • the term 'circuitry' as used herein also includes, for example, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, other network device, and/or other computing device.
  • a nomadic multi-access edge computing device, method and computer program product are provided to apply a multi-access or mobile edge computing to a moving object.
  • MEC multi-access edge computing
  • MEC provides for content to be rapidly processed at the edge of a mobile network.
  • application developers, content providers and others can enjoy cloud-computing capabilities with ultra-low latency and high bandwidth as well as real time access to radio network information that may be leveraged by various MEC applications.
  • MEC may be utilized by a variety of applications including video analytic applications, location service applications, Internet of Things (IoT) applications, augmented reality applications, optimized local content distribution applications and data caching applications.
  • IoT Internet of Things
  • a nomadic MEC device may provide lower latency, dynamic service/application offering, and higher performance to a nomadic environment. Additionally, the utilization of a nomadic MEC device may provide a reduced need for data transmission during a vehicle's travel along a route by downloading services, applications, and/or data prior to the commencement of the vehicle's route. Further, at least certain embodiments described herein may be configured for use with the next generation of Global System for Mobile Communications - Railway (“GSM-R").
  • GSM-R Global System for Mobile Communications - Railway
  • the nomadic network 100 may comprise a nomadic multi-access edge computing (“MEC") device 102, such as a MEC server as shown in FIG. lc, one or more mobile devices 104, a local network 106, a wireless access point ("WAP") 108, and a radio terminal 1 12.
  • the nomadic MEC device 102 may, in some embodiments, comprise a forwarding plane 110, one or more applications (“Appl”) 120, and a multi-access edge (“ME”) platform 118.
  • the example nomadic network 100 may be disposed on and carried by a vehicle (e.g., railway system, train, or the like) associated with a route such that the MEC server is nomadic.
  • a vehicle e.g., railway system, train, or the like
  • the nomadic MEC device 102 may include circuitry, networked processors, or the like (e.g., as seen in FIG. 3) configured to perform some or all of processes described herein, and may be any suitable network server and/or other type of processing device. In some
  • nomadic MEC device 102 may function as a "cloud" with respect to the nomadic network 100. In that sense, the nomadic MEC device 102 may include several servers performing interconnected and/or distributed functions. To avoid unnecessarily overcomplicating the disclosure, the nomadic MEC device 102 is shown and described herein as a single server. In some embodiments, the nomadic MEC device 102 may further define one or more applications 120 and a ME platform 118 hosted and/or stored by the nomadic MEC device 102. As described below in detail, the one or more applications 120 and the ME platform 118 may correspond to services, applications, and/or data requested by one or more mobile devices 104 communicably connected with the nomadic MEC device 102. Although described herein as a "server," the present disclosure contemplates that the nomadic MEC device 102 may be broadly encompassed by any computing device.
  • the nomadic network 100 may be configured in some embodiments, as seen in FIG. lc, such that the one or more mobile devices 104 disposed on the vehicle may be communicably connected with the nomadic MEC device 102 via a local network 106 and a WAP 108.
  • the local network 106 may include one or more wired and/or wireless communication networks including, for example, a wired or wireless local area network (LAN), personal area network (PAN), metropolitan area network (MAN), wide area network (WAN), or the like, as well as any hardware, software and/or firmware for implementing the one or more networks (e.g., network routers, switches, hubs, etc.).
  • the local network 106 may include a cellular telephone, mobile broadband, long term evolution (LTE), a global system for mobile
  • the local network 106 may include a public network, such as the Internet, a private network, such as an intranet, or combinations thereof, and may utilize a variety of networking protocols now available or later developed including, but not limited to transmission control protocol (TCP)/internet protocol (IP) based networking protocols.
  • TCP transmission control protocol
  • IP Internet protocol
  • the present disclosure contemplates that various network beacons may be disposed on a vehicle.
  • a train car may have a plurality of Wi-Fi access beacons located throughout the train car to facilitate connection to a Wi-Fi network hosted by the train car.
  • the WAP 108 may be configured to receive wireless signals transmitted by the one or more mobile devices 104 via the local network 106 and convert the wireless signals to electrical signals for transmitting and/or processing by the nomadic MEC device 102.
  • a mobile device traveling in a train car may connect to a Wi-Fi network hosted by the train (e.g., by the nomadic network 100) such that the mobile device may request services, applications, and/or data from an external network (e.g., terrestrial network 200 and core network 214 in FIG. 2).
  • the one or more mobile devices 104 may also be directly communicably connected with an access network such as access network 114.
  • a mobile device 104 may be a cellular device connected to a cellular network and may receive services, applications, and/or data directly from the cellular network as well as from the nomadic network 102.
  • the mobile device may be provided options (e.g., in the form of a menu or the like).
  • a passenger may select to either utilize the nomadic network described herein or to use a conventional access network (e.g., a mobile cellular network, satellite network, or the like).
  • the provided options may include conditions associated with each option (e.g., estimated download time, costs/charges, or the like).
  • the WAP 108 may be configured to maintain a connection between the nomadic MEC device 102 and a satellite network, a mobile radio network, and a wireless local area network, and provide an option to the one or more passengers of the vehicle to select which connection to utilize.
  • each mobile device 104 may be associated with a passenger and/or passenger profile. Although described in reference to a single mobile device 104, the present disclosure contemplates that any number of mobile devices may be associated with various other passengers and/or passenger profiles. Additionally, the present disclosure contemplates that the nomadic MEC device 102 may be communicably connected to any number of mobile devices 104 located within or proximate the vehicle.
  • the nomadic network 100 may utilize a radio terminal 112 for connecting the nomadic network 100 to a terrestrial network 200, via an access network 114.
  • the radio terminal 112 may be configured to convert signals received from the nomadic MEC device 102 to appropriate signals for transmission to the access network 114.
  • the access network used by the nomadic network 100, via the radio terminal 1 12 may depend upon the location of the vehicle (e.g., prior to travel along the route or during travel along the route).
  • the nomadic network 100 may utilize a WLAN, mobile radio network, or satellite network access network for connecting with the terrestrial network 200.
  • the radio terminal 112 may utilize an alternative access network.
  • the train may utilize a Wi-Fi access network to request or otherwise receive services, applications, or data via a WLAN offered by the station.
  • the train may utilize a satellite access network or mobile radio network such that the nomadic network may connect to a terrestrial network.
  • various types of access networks such as 3GPP and non-3GPP access technologies, including an evolved UMTS, terrestrial radio access network (E-UTRAN), evolved node B (eNB), a HSPA network, a GSM/EDGE radio access network (GERAN), a wireless local area network (WLAN) or a WiMAX network, may be utilized to access the terrestrial network 200.
  • E-UTRAN terrestrial radio access network
  • eNB evolved node B
  • HSPA High Speed Packet Access
  • GERAN GSM/EDGE radio access network
  • WLAN wireless local area network
  • WiMAX WiMAX
  • the nomadic network 100 may, at various points in time, be in communication with one or more of a plurality of access networks associated with various stations located along the route associated with the vehicle.
  • the route of a railway system may include various terminals or stops along the route where passengers may enter or exit the train car.
  • each of these stations may offer various access networks 114.
  • the nomadic MEC device 102 may include a forwarding plane 110.
  • the forwarding plane 1 10 may be communicably connected with the wireless access point 108 and the radio terminal 112.
  • the forwarding plane 110 may be configured to monitor a data flow transmitted between the wireless access point 108 and the radio terminal 1 12.
  • the forwarding plane 110 may receive data (e.g., a request for services, applications, and/or data) from the one or more mobile devices 104 and may determine that the nomadic MEC device 102 cannot serve or otherwise fulfil the request.
  • the forwarding plane 100 may receive data requested by the nomadic network 100 from a terrestrial network (e.g., terrestrial network 200 in FIG. 2), and may similarly determine that the nomadic MEC device may not serve the data, applications, and/or data.
  • a terrestrial network e.g., terrestrial network 200 in FIG. 2
  • the terrestrial network 200 may comprise a terrestrial MEC device 202, such as a MEC server, an access network 114, a core network gateway 210, and a multi-access edge orchestrator ("MEO") 212.
  • the terrestrial MEC device 202 similar to the nomadic MEC device 102 in FIG. lc, may, in some embodiments, comprise a forwarding plane 204, one or more applications 206, and a multi-access edge (“ME”) platform 208.
  • the terrestrial MEC device 202 may include circuitry, networked processors, or the like (e.g., as seen in FIG. 3) configured to perform some or all of processes described herein, and may be any suitable network server and/or other type of processing device. In some
  • terrestrial MEC device 202 may function as a "cloud" with respect to the terrestrial network 200.
  • the terrestrial MEC device 202 may include several servers performing interconnected and/or distributed functions.
  • the terrestrial MEC device 202 is shown and described herein as a single server.
  • the terrestrial MEC device 202 may further define one or more applications 206 and a ME platform 208 hosted and/or stored by the terrestrial MEC device 202.
  • the one or more applications 206 and the ME platform 208 may correspond to services, applications, and/or data requested by one or more mobile devices (e.g., mobile devices 104 in FIG. lc) communicably connected with the terrestrial MEC device 202 via the nomadic network 100.
  • the terrestrial network 200 may also comprise a core network gateway 210 communicably connected with the terrestrial MEC device 202, the core network 214, and the MEO 212.
  • the core network gateway 210 may be configured to communicably connect the terrestrial network 200 with a core network 214.
  • a core network 214 may comprise the highly functional communication facilities that interconnect primary nodes of access networks.
  • the core network may further be configured to route or exchange data among various sub-networks.
  • the core network 214 may be any suitable core network structure such as an evolved packet core (EPC) network, a general packet radio system (GPRS) core network, or the like.
  • the core network gateway 210 may further be configured to receive a request for services, applications, and/or data from the terrestrial MEC device 202 and route the request to the core network 214 or the MEO 212.
  • the terrestrial network 200 may also comprise a MEO 212 (e.g., a network management entity).
  • the MEO 212 may be communicably connected to a core network 214 via a core network gateway 210 and may also be communicably connected with the terrestrial MEC device 202.
  • the MEO 212 may operate to manage and control requests for services, applications, and/or data by the terrestrial MEC device 202, and, by the connection between the nomadic network 100 and the terrestrial network 200, further manage and control requests for services, applications, and/or data by the nomadic MEC device 102 in FIG. lc.
  • the MEO 212 may receive services, applications, and/or data from a core network 214 via the core network gateway 210, and may manage the routing and distribution of said services, applications, and/or data to the terrestrial network 200 and the nomadic network 100.
  • the terrestrial MEC device 202 may detect a request from the nomadic network 100 in FIG. lc and may forward the request to the MEO 212.
  • the MEO 212 may route a response from the terrestrial network 200 to the nomadic multi-access edge computing device 102 via the terrestrial multi-access edge computing device 202.
  • the terrestrial MEC device 202 may detect a request from the nomadic network 100, and may route the request to the MEO 212 via the core network gateway 210 such that the terrestrial MEC device 202 operates to pass the request transparently therethrough.
  • the terrestrial MEC device 202 may include a forwarding plane 204.
  • the forwarding plane 204 may be communicably connected with the access network 114 and the core network gateway 210.
  • the forwarding plane 204 may be configured to monitor a data flow transmitted between the access network 114 and the core network gateway 210.
  • the forwarding plane 110 may receive data (e.g. , a request for services, applications, and/or data) from the access network 114 (e.g., via a request made by the nomadic network 100 in communication with the terrestrial network 200 by the access network 114) and may determine that the terrestrial MEC device 202 cannot serve or otherwise fulfil the request.
  • the nomadic MEC device 102 and/or terrestrial MEC device 202 may include or be associated with an apparatus 300 as shown in FIG. 3.
  • the apparatus 300 may include or otherwise be in communication with a processor 302, a memory device 304, a communication interface 306, and/or a user interface 308.
  • the processor 302 (and/or co-processors or any other processing circuitry assisting or otherwise associated with the processor) may be in
  • the memory device may include, for example, one or more volatile and/or non-volatile memories.
  • the memory device may be an electronic storage device (e.g., a computer readable storage medium) comprising gates configured to store data (e.g., bits) that may be retrievable by a machine (e.g., a computing device like the processor).
  • the memory device 304 may be configured to store information, data, content, applications, instructions, or the like for enabling the apparatus 300 to carry out various functions in accordance with an example embodiment of the present invention.
  • the memory device 304 may store the applications 120, 206 in FIGs. lc and 2.
  • the memory device 304 could be configured to buffer input data for processing by the processor 302.
  • the memory device 304 could be configured to store instructions for execution by the processor 302.
  • the apparatus 300 may be embodied by a nomadic MEC device 102 configured to be utilized in an example embodiment of the present invention.
  • the apparatus may be embodied as a chip or chip set.
  • the apparatus 300 may comprise one or more physical packages (e.g., chips) including materials, components and/or wires on a structural assembly (e.g., a baseboard).
  • the structural assembly may provide physical strength, conservation of size, and/or limitation of electrical interaction for component circuitry included thereon.
  • the apparatus 300 may therefore, in some cases, be configured to implement an embodiment of the present invention on a single chip or as a single "system on a chip.”
  • a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.
  • the processor 302 may be embodied in a number of different ways.
  • the processor 302 may be embodied as one or more of various hardware processing means such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without an accompanying DSP, or various other processing circuitry including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like.
  • the processor 302 may include one or more processing cores configured to perform independently.
  • a multi-core processor may enable multiprocessing within a single physical package.
  • the processor 302 may include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and/or multithreading.
  • the processor 302 may be configured to execute instructions stored in the memory device 304 or otherwise accessible to the processor 302. Alternatively or additionally, the processor 302 may be configured to execute hard coded functionality. As such, whether configured by hardware or software methods, or by a combination thereof, the processor 302 may represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to an embodiment of the present invention while configured accordingly. Thus, for example, when the processor 302 is embodied as an ASIC, FPGA or the like, the processor 302 may be specifically configured hardware for conducting the operations described herein.
  • the processor 302 when the processor 302 is embodied as an executor of software instructions, the instructions may specifically configure the processor 302 to perform the algorithms and/or operations described herein when the instructions are executed.
  • the processor 302 may be a processor 302 of a specific device (e.g., a nomadic MEC device, such as the ME platform 118, 208 and/or the forwarding plane 110, 204 as shown in FIGs. lc and 2) configured to be employed by an embodiment of the present invention by further configuration of the processor 302 by instructions for performing the algorithms and/or operations described herein.
  • the processor 302 may include, among other things, a clock, an arithmetic logic unit (ALU) and logic gates configured to support operation of the processor.
  • ALU arithmetic logic unit
  • the communication interface 306 may be any means such as a device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and/or transmit data between computing devices and/or servers (e.g., the nomadic MEC device 102 in FIG. lc and the terrestrial MEC device 202 in FIG. 2 and, more particularly, the forwarding plane 110, 204).
  • the communication interface 306 may include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling communications wirelessly. Additionally or alternatively, the communication interface may include the circuitry for interacting with the antenna(s) to cause transmission of signals via the antenna(s) or to handle receipt of signals received via the antenna(s).
  • the communication interface 306 may be configured to communicate wirelessly with the one or more mobile devices, such as via Wi-Fi, Bluetooth or other wireless communications techniques.
  • the communication interface may alternatively or also support wired communication.
  • the communication interface 306 may include a communication modem and/or other hardware/software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms.
  • the communication interface 306 may be configured to communicate via wired communication with other components of the computing device or sever.
  • the apparatus 300 may optionally include a user interface 308 in communication with the processor 302, such as by the user interface circuitry, to receive an indication of a user input and/or to provide an audible, visual, mechanical, or other output to a user.
  • the user interface 308 may include, for example, a keyboard, a mouse, a joystick, a display, a touch screen display, a microphone, a speaker, and/or other input/output
  • the user interface may also be in communication with the memory 304 and/or the communication interface 306, such as via a bus.
  • FIG. 4 a flowchart is provided that illustrates a method for a nomadic MEC network 400 for use with some embodiments, described herein.
  • the method for a nomadic MEC network 400 may include obtaining services, applications, or data by a nomadic multi-access edge computing device disposed on and carried by a vehicle along a route, prior to travel along the route at Block 402.
  • the apparatus 300 e.g., nomadic MEC device 102 in FIG.
  • the request at Block 402 may occur when a train is located at a terminal prior to beginning a route.
  • the nomadic MEC device 102 onboard the train may identify one or more mobile devices located proximate the train (e.g., in a train car), and may determine a basic set of services, applications, and/or data associated with the one or more mobile devices for which a request is transmitted.
  • the one or more mobile devices e.g., mobile device(s) 104 in FIG.
  • the method 400 at Block 402 may consider data associated with a passenger profile.
  • the passenger profile may be associated with a mobile device and may include biographic data (e.g., gender, age, ethnicity, employment, home address, user liked and/or disliked services, or the like), destination information (e.g., stops along the vehicle's route), and services and/or applications subscribed to or otherwise ordered by the passenger (e.g., via their mobile device or the like).
  • the request at Block 402 may include services, applications and/or data that are determined, such as by processor 302, based upon the passenger profile and in which there is a reasonable likelihood that the passenger will utilize or otherwise have interest.
  • the nomadic network 100 may receive passenger profiles or other associated passenger data from ticket purchasing.
  • a passenger on a railway system may purchase a ticket with a particular destination and a request for Wi-Fi access. The request for these services,
  • applications, and/or data may be included in the obtaining services, applications, or data by a nomadic multi-access edge computing device disposed on and carried by a vehicle along a route, prior to travel along the route at Block 402. Additionally, the present disclosure contemplates that the nomadic MEC device 102 may request all basic services, applications, and/or data at Block 402 prior to commencing its route, or may request any subset of these services, applications, and/or data.
  • the apparatus 300 may include means, such as the processor 302, the communications interface 306 or the like, for reporting a location of the vehicle during travel along the route to a terrestrial network 200 by a nomadic network 100 disposed on a vehicle at Block 404.
  • the nomadic network 100 may receive a request for services, applications, and/or data from one or more mobile devices 104 proximate the vehicle as described above, or the nomadic MEC device 102 may determine that services, applications, and/or data are necessary for the nomadic network 100, and may report a location of the vehicle to the radio terminal 1 12 for further transmission, via an access network 114, to a terrestrial network 200 at Block 404.
  • the apparatus 300 may include means such as the processor 302, the communications interface 306 or the like, for determining if the vehicle is located within a coverage region defined by a station or stop along the route at Block 406.
  • the nomadic network 100 via the nomadic MEC device 102, may periodically transmit the location of the vehicle along route to the terrestrial network 200 via an access network 1 14.
  • the access network selected by the nomadic network 100 may be determined by the location of the vehicle relative to stations along the route (e.g., a proximity to a terminal or stop along the route).
  • the nomadic MEC device 102 may determine that the vehicle, and the associated nomadic network 100, is located within a coverage region defined by a station by determining the availability of access networks associated with the terrestrial network 200.
  • a train traveling along a route outside of a coverage region e.g., between stations
  • may not receive access to a Wi-Fi network e.g., access network
  • the nomadic MEC device 102 may determine that the train is located within a coverage region due to the availability of the Wi-Fi network.
  • the apparatus 300 may include means such as the processor 302, the communications interface 306 or the like, for connecting the nomadic MEC device 102 with the terrestrial network 200 via a first set of access networks at Block 408.
  • the first set of access networks may include wireless local area networks, fixed networks, mobile/cellular radio networks, satellite networks, and the like. The present disclosure contemplates that when the vehicle is located within a coverage region defined by a station, any and all access networks may be utilized to connect the nomadic network 100 with the terrestrial network 200.
  • the nomadic network 100 may connect with the terrestrial network 200 via a Wi-Fi network (e.g., only available within the coverage region) or via a satellite network (e.g., available both within and outside of the coverage region).
  • a Wi-Fi network e.g., only available within the coverage region
  • a satellite network e.g., available both within and outside of the coverage region.
  • the apparatus 300 e.g., nomadic MEC device 102 and radio terminal 112 in FIG. lc
  • the apparatus 300 may include means, such as the processor 302, the communications interface 306 or the like, for connecting the nomadic MEC device 102 with the terrestrial network 200 via a second set of access networks at Block 410.
  • the second set of access networks may include
  • the first and second sets of access networks may include some of the same access networks, the access networks utilized when outside of a coverage region defined by a station are different in one embodiment than the access network utilized while within the coverage region of the station.
  • the present disclosure contemplates that when the vehicle is located outside of a coverage region defined by a station, access networks which are only available to the nomadic network 100 may be utilized to connect the nomadic network 100 with the terrestrial network 200.
  • the nomadic network 100 may connect with the terrestrial network 200 via a satellite network or mobile/cellular radio network.
  • the nomadic network 100 may connect with the terrestrial network 200 via any access network (e.g., second set of access networks) configured to connect a nomadic computing device/server to a terrestrial network or core network.
  • the apparatus 300 may include means, such as the processor 302, the communications interface 306 or the like, for receiving an update to the services, applications, or data during travel along the route at Block 412.
  • the terrestrial network 200 may receive a request for services, applications, and/or data from the nomadic network 100 via an access network 114.
  • the terrestrial network may determine the appropriate services, applications, and/or data required to satisfy the request of the nomadic network 100 at Block 412.
  • the terrestrial network 200 via the terrestrial MEC device 202 in conjunction with the MEO 212, may determine whether to activate possible service and/or application update operations at Block 412. Additionally, the
  • determination may consider the location of the vehicle along the route, the proximity of the vehicle with a station located along the route, the size of the services, applications, and/or data requested, the available bitrate or bandwidth offered by the terrestrial network, the velocity of the vehicle, and any potential network coverage issues (e.g., tunnels, mountains, or the like).
  • the apparatus 300 may include means, such as the processor 302, the communications interface 306 or the like, for providing access to one or more passengers of the vehicle to the services, applications, or data during travel along the route at Block 414.
  • the nomadic network 100 communicably connected with the terrestrial network 200 may download the services, applications, and/or data transmitted by the terrestrial network 200 via the access network 1 14.
  • the nomadic network 100 may, via the nomadic MEC device 102, enable an access to or route the downloaded services, applications, and/or data to the one or more mobile devices proximate the vehicle via the local network 106.
  • the nomadic MEC device 102 such as the processor 302, the communication interface 306 or the like, may be configured to maintain a connection to and between a satellite network, a mobile radio network, and a wireless local area network, and provide an option to the one or more passengers (e.g., mobile devices 104) of the vehicle to select which connection to utilize.
  • the nomadic MEC device of an example embodiment therefore facilitates the efficient and timely provision of services, applications or data to passengers in a vehicle that moves along a route.
  • the nomadic MEC device is configured to communicate with networks offboard the vehicle to obtain the services, applications or data and the networks with which the nomadic MEC device communicates may change during the time span from prior to the vehicle traveling along its route, while the vehicle is traveling along its route and upon completion of the route.
  • the nomadic MEC device may, in some embodiments, identify the services, applications or data to be obtained based on information provided by or associated with the passenger(s), such as via passenger profile.
  • the passenger experience may be enhanced, while the network utilization is correspondingly improved.
  • the apparatus 300 may include means, such as the processor 302 or the like, for determining a basic set of services, applications, and/or data dependent upon the route and/or destination of the vehicle by the nomadic MEC device 102 at Block 502.
  • the nomadic MEC device 102 such as the processor 302 may consider various characteristics associated with the vehicle and the vehicle's associated route in order to determine services, applications, and/or data to request from the terrestrial network 200.
  • the determination may consider the length of the vehicle's route, the number and location of stations located along the route, the size of the services, applications, and/or data requested, the number of mobile devices communicably connected with the nomadic MEC device, the velocity of the vehicle, and any potential network coverage issues (e.g., tunnels, mountains, or the like) along the route.
  • this determination and request of a basic set of services, applications, and/or data dependent upon the route and/or destination of the vehicle at Block 502 may be made without receiving a request for services, applications, or data from one or more mobile devices.
  • the nomadic MEC device 102 may request a basic set of services, applications, and/or data based only upon the route of the vehicle, without considering requests from one or more mobile devices.
  • the apparatus 300 may include means, such as the processor 302, the communications interface 306 or the like, for receiving a request for services, applications, and/or data from one or more mobile devices 104 located proximate the vehicle by the nomadic MEC device 102 via a local network 106 at Block 504.
  • one or more mobile devices 104 located proximate the vehicle may request, prior to the vehicle traveling along its route, particular services, applications, and/or data to be supplied by the nomadic network 100.
  • the nomadic MEC device may also receive the requests from the one or more mobile devices 104 via a local network 106 and WAP 108.
  • one or more mobile devices 104 may request particular services, applications, or data in addition to the basic set of services, applications, or data determined at Block 502.
  • the apparatus 300 Upon receiving a request for services, applications, and/or data from one or more mobile devices 104 located proximate the vehicle by the nomadic MEC device 102 via a local network 106 at Block 504, the apparatus 300 (e.g., nomadic MEC device 102 in FIG. lc) may include means, such as the processor 302, the communications interface 306 or the like, for determining by the forwarding plane if the requested services, applications, and/or data may be served by the nomadic MEC device 102 at Block 506. As discussed above with reference to FIG. lc, the forwarding plane 110 may be configured to monitor a data flow transmitted between the wireless access point 108 and the radio terminal 112.
  • the forwarding plane 110 may receive data (e.g., a request for services, applications, and/or data) from the one or more mobile devices 104 and may determine that the nomadic MEC device 102 cannot serve or otherwise fulfil the request (e.g., due to low bandwidth, memory storage concerns, or the like).
  • data e.g., a request for services, applications, and/or data
  • the nomadic MEC device 102 may not serve or otherwise fulfil the request (e.g., due to low bandwidth, memory storage concerns, or the like).
  • the apparatus 300 Upon determining by the forwarding plane 1 10 that the requested services, applications, and/or data may be served by the nomadic MEC device at Block 506, the apparatus 300 (e.g., nomadic MEC device 102 in FIG. lc) may include means, such as the processor 302, the communications interface 306 or the like, for passing the request for services, applications, and/or data through the forwarding plane 1 10 to the radio terminal 112 for transmission to an access network 114 in communication with the terrestrial network 200 at Block 508. As described above with reference to the architecture of the nomadic network 100, the forwarding plane 110 may operate to pass a request from the nomadic MEC device 102 to the terrestrial network 200 via an access network 1 14.
  • the apparatus 300 may include means, such as the processor 302, the communications interface 306 or the like, for receiving a request for services, applications, and/or data from the nomadic network 100 via the radio terminal 1 12 in communication with an access network 114 at Block 602.
  • the nomadic network 100 may report its location to the terrestrial network 200 via an access network 114.
  • the nomadic network 100 may connect with the access network 1 14 via a set of access networks dependent upon the access networks available to the nomadic network 100. Similarly, upon receiving a request for services, applications, and/or data from the nomadic network 100 via the radio terminal 112 in
  • the apparatus 300 may include means, such as the processor 302, the communications interface 306 or the like, for detecting the request for services, applications, and/or data by a terrestrial MEC device 202 at Block 604.
  • the communication method for routing a request through a terrestrial network 600 may receive the request for services, applications, and/or data at the terrestrial MEC device 202 and may route (e.g., forward) the request to the MEO 212 at Block 606.
  • the terrestrial MEC device 202 may function similar to the nomadic MEC device 102 described above, where the forwarding plane 204 may be configured to monitor a data flow transmitted between the access network 114 and the core network gateway 210.
  • the processor 302 and/or communication interface 306, such as may embody the forwarding plane 204, may receive data (e.g., a request for services, applications, and/or data) from the access network 114, and may determine that the terrestrial MEC device 202 cannot serve or otherwise fulfil the request (e.g., due to low bandwidth, memory storage concerns, or the like).
  • data e.g., a request for services, applications, and/or data
  • the processor 302 and/or communication interface 306 may receive data (e.g., a request for services, applications, and/or data) from the access network 114, and may determine that the terrestrial MEC device 202 cannot serve or otherwise fulfil the request (e.g., due to low bandwidth, memory storage concerns, or the like).
  • the communication method for routing a request through a terrestrial network 600 may receive the request for services, applications, and/or data at the terrestrial MEC device 202 and may route (e.g., forward) the request to the MEO 212 via a core network gateway 210 at Block 608.
  • the terrestrial MEC device such as the processor 302, the communication interface 306 or the like, may operate to route the request for services, applications, and/or data transparently through the terrestrial MEC device 202.
  • the terrestrial MEC device 202 may allow the received request to pass to the core network gateway 210 without modification by the terrestrial MEC device 202. Further the core network may function to fulfil the request by transmitting the requested services, applications, and/or data to the MEO 212. The MEO 212 may then operate to determine an appropriate set of services, applications, and/or data for transmitting to the nomadic network 100.
  • the apparatus 300 may include means such as the processor 302, the communications interface 306 or the like, for determining by the MEO 212 an appropriate set of services, applications, and/or data for transmitting to the nomadic network 100 at Block 610.
  • the terrestrial network 200 via the MEO 212, may determine whether to activate possible service and/or application update operations.
  • the determination at the MEO 212 may consider the location of the vehicle along the route, the proximity of the vehicle to a station located along the route, the size of the services, applications, and/or data requested, the available bitrate or bandwidth offered by the terrestrial network, the velocity of the vehicle, and any potential network coverage issues (e.g., tunnels, mountains, or the like).
  • the communication method for routing a request through a terrestrial network 600 may further include means, such as the processor 302 or the like, for considering by the MEO 212 passenger profiles and data associated with the one or more mobile devices 104 located proximate the vehicle at Block 612.
  • the one or more mobile devices 104 communicably connected to the terrestrial network 200 via the nomadic network 100 may be associated with one or more passenger profiles.
  • each passenger profile may be associated with a mobile device and may include biographic data (e.g., gender, age, ethnicity, employment, home address, user liked and/or disliked services, or the like), destination information (e.g., stop along vehicle route), and services and/or applications subscribed to or otherwise ordered by the passenger (e.g., via their mobile device or the like).
  • biographic data e.g., gender, age, ethnicity, employment, home address, user liked and/or disliked services, or the like
  • destination information e.g., stop along vehicle route
  • services and/or applications subscribed to or otherwise ordered by the passenger e.g., via their mobile device or the like.
  • the nomadic network 100 may receive passenger profiles or other associated passenger data from ticket purchasing.
  • the MEO 212 may apply a categorization or classification to a passenger profile based upon the destination of the passenger, the current location of the vehicle, the remaining duration to the destination of the passenger, ticketing information, and/or information provided by the passenger in order to determine the application, services or other data to be downloaded and provided or otherwise made available to a passenger, such as by downloading services and/or applications to which a passenger subscribes or has ordered and/or downloading services and/or applications in which the processor 302 determines the passenger may have interest based upon the passenger profile, the passenger's historical download or access patterns or the like.
  • the MEO 212 may utilize the passenger related categorization or passenger profile data for advertising directly to current passengers, or for future advertising campaigns, thereby providing more targeted advertising based upon the passenger profile data.
  • the MEO 212 may identify a passenger and associated mobile device belonging to a certain category or classification or passenger profile, communicably connected with a local network hosted by the vehicle (e.g. , local network 106 in FIG. lc) by identifying an access code or password given to the passenger and subsequently utilized by the passenger when connecting to the local network.
  • the access code or password may be related or otherwise tied to a ticket purchased by the passenger.
  • the access code or password in some embodiments, may correspond to a ticket number or code listed on the ticket.
  • the apparatus 300 may include means, such as the processor 302, the communications interface 306 or the like, for the transmitting via the terrestrial MEC 202 and the access network 1 14 the appropriate set of services, applications, and/or data from the terrestrial network 200 to the nomadic network 100 at Block 616.
  • the terrestrial network 200 may be communicably connected with the nomadic network 100 such that the appropriate set of services, applications, and/or data may transmitted by the terrestrial network 200 via the access network 114.
  • Figures 4-6 illustrate flowcharts of an apparatus 300, method, and computer program product according to example embodiments of the disclosure. It will be understood that each block of the flowcharts, and combinations of blocks in the flowcharts, may be implemented by various means, such as hardware, firmware, processor, circuitry, and/or other devices associated with execution of software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by a memory 304 of an apparatus 300 employing an embodiment of the present invention and executed by a processor 302 of the apparatus.
  • any such computer program instructions may be loaded onto a computer or other programmable apparatus (e.g., hardware) to produce a machine, such that the resulting computer or other programmable apparatus implements the functions specified in the flowchart blocks.
  • These computer program instructions may also be stored in a computer-readable memory that may direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture the execution of which implements the function specified in the flowchart blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart blocks.
  • blocks of the flowcharts support combinations of means for performing the specified functions and combinations of operations for performing the specified functions for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions.
  • certain ones of the operations above may be modified or further amplified. Furthermore, in some embodiments, additional optional operations may be included. Modifications, additions, or amplifications to the operations above may be performed in any order and in any combination.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un appareil, un procédé, et des produits de programmes informatiques en référence à un dispositif informatique périphérique nomade multi-accès configuré pour être disposé sur et porté par un véhicule le long d'un itinéraire. L'appareil peut obtenir des services, des applications ou des données à partir d'une entité terrestre de mise en réseau avant le déplacement le long de l'itinéraire. L'appareil peut faire en sorte qu'un emplacement du véhicule soit signalé pendant le déplacement le long de l'itinéraire, et en réaction à l'emplacement du véhicule, peut recevoir une mise à jour des services, des applications ou des données pendant le déplacement le long de l'itinéraire. L'appareil peut en outre fournir à un ou plusieurs passagers du véhicule un accès aux services, applications ou données pendant le déplacement le long de l'itinéraire.
EP17908262.3A 2017-05-02 2017-05-02 Dispositif nomade multi-accès configuré pour être porté par un véhicule et pour obtenir des mises à jour de services, d'applications ou de données d'après l'emplacement du véhicule. Withdrawn EP3620030A4 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2017/052541 WO2018203106A1 (fr) 2017-05-02 2017-05-02 Dispositif nomade multi-accès configuré pour être porté par un véhicule et pour obtenir des mises à jour de services, d'applications ou de données d'après l'emplacement du véhicule.

Publications (2)

Publication Number Publication Date
EP3620030A1 true EP3620030A1 (fr) 2020-03-11
EP3620030A4 EP3620030A4 (fr) 2020-11-18

Family

ID=64016935

Family Applications (1)

Application Number Title Priority Date Filing Date
EP17908262.3A Withdrawn EP3620030A4 (fr) 2017-05-02 2017-05-02 Dispositif nomade multi-accès configuré pour être porté par un véhicule et pour obtenir des mises à jour de services, d'applications ou de données d'après l'emplacement du véhicule.

Country Status (2)

Country Link
EP (1) EP3620030A4 (fr)
WO (1) WO2018203106A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220268593A1 (en) * 2021-02-19 2022-08-25 International Business Machines Corporation Joint optimization of vehicle mobility, communication networks, and computing resources

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2371711B (en) * 2000-11-27 2004-07-07 Nokia Mobile Phones Ltd A Server
JP2005092732A (ja) * 2003-09-19 2005-04-07 Nec Corp 旅客移動体内におけるサービス提供方法およびサービス提供システム
DE102006023319A1 (de) * 2006-05-18 2007-12-13 Deutsche Telekom Ag System für den Informationszugriff und die Kommunikation in einem Fahrzeug mit mehreren gekoppelten Einheiten
US20090024742A1 (en) * 2007-07-16 2009-01-22 Sony Ericsson Mobile Communications Ab Distribution of Multimedia Files Using a Roving File Server
US8353006B2 (en) * 2008-05-07 2013-01-08 Livetv, Llc Aircraft communications system using whitelists to control access and associated methods
US20110117890A1 (en) * 2009-11-18 2011-05-19 Sony Ericsson Mobile Communications Ab Top list generated from user context based information
US8797953B2 (en) * 2010-08-11 2014-08-05 Vit University In-vehicle networking based services

Also Published As

Publication number Publication date
EP3620030A4 (fr) 2020-11-18
WO2018203106A1 (fr) 2018-11-08

Similar Documents

Publication Publication Date Title
CN115175130B (zh) 用于移动用户设备的多址边缘计算服务的方法和装置
CN109729125B (zh) 会话建立方法、设备及系统
US11252638B2 (en) Vehicle-based mobile node fleet for network service deployment
EP3707881B1 (fr) Architecture informatique périphérique multi-accès et cadre de mobilité
US10740149B2 (en) Serverless computing architecture
CN114556888B (zh) 强制门户弹窗抑制
US10158966B2 (en) Connected car data links aggregator
US9714840B2 (en) Route determination based on user ranking of wireless internet quality of service metrics
US9769742B2 (en) Devices, methods, and computer readable storage devices for providing application services
US9185556B2 (en) Method and system for forming a common network using shared private wireless networks
CN110831074A (zh) 一种直连通信的方法、amf、接入网功能实体及计算机存储介质
WO2022125296A1 (fr) Mécanismes pour permettre des services informatiques en réseau
US11140541B2 (en) Method for management of movable edge computing servers
WO2018215816A1 (fr) Transfert au niveau d'un bord de réseau
WO2024011193A1 (fr) Améliorations de la resélection de cellules pour des réseaux non terrestres
US12418832B2 (en) Migration of network traffic between licensed and unlicensed spectrum
WO2024091970A1 (fr) Évaluation de performances pour inférence d'intelligence artificielle/apprentissage automatique
EP3620030A1 (fr) Dispositif nomade multi-accès configuré pour être porté par un véhicule et pour obtenir des mises à jour de services, d'applications ou de données d'après l'emplacement du véhicule.
JP2017228909A (ja) ネットワーク負荷低減システムおよびネットワーク負荷低減方法
US11005952B2 (en) Data distribution system, mobile station, distribution device, data distribution method, and computer readable medium
US20160119817A1 (en) Mobile terminal, communications control processor, communications system, and communications method
Slamnik-Kriještorac et al. An optimized application-context relocation approach for Connected and Automated Mobility (CAM)
US11863344B2 (en) Enabling global quality of service for real-time selection of best data communications channels in autonomous driving vehicles
TW202023313A (zh) 基於Ｗｉ－Ｆｉ探測的資訊推薦與通知系統及其實施方法
Slamnik-KrijeĹĄtorac et al. An optimized application-context relocation approach for Connected and Automated Mobility (CAM)

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20191202

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
A4 Supplementary search report drawn up and despatched

Effective date: 20201020

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 12/16 20060101ALI20201014BHEP

Ipc: H04W 4/44 20180101AFI20201014BHEP

Ipc: H04W 88/04 20090101ALI20201014BHEP

Ipc: H04L 12/58 20060101ALI20201014BHEP

Ipc: H04W 4/02 20180101ALI20201014BHEP

Ipc: H04W 24/02 20090101ALI20201014BHEP

Ipc: H04W 84/00 20090101ALI20201014BHEP

Ipc: H04L 29/06 20060101ALI20201014BHEP

Ipc: H04L 29/08 20060101ALI20201014BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20211013

INTG Intention to grant announced

Effective date: 20211027

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20220308