High traffic density personalized transportation

Abstract

The present invention relates to personalized transportation with high traffic density. Methods, apparatuses, systems, and articles for personalized transportation with high traffic density are disclosed. An example system includes: a transfer carrier having a first mobility system, a first stacking coupler, a first magnetic coupler, a second magnetic coupler, and a first address; a transfer pod having a second mobility system, a second stacking coupler, and a second address, the second stacking coupler being configured to couple to the first stacking coupler; and a controller for: in response to obtaining a request to direct the transfer carrier to move from the first address to the second address, invoking the transfer pod to couple to the transfer carrier by directing the transfer pod to move to the top of the transfer carrier using the second mobility system; and when the transfer carrier is coupled to the transfer pod, invoking the transfer carrier to move the transfer pod to a third address using the first mobility system.

Description

Technical Field

[0001] The present disclosure generally relates to transportation, and more particularly, to systems, methods, and devices for personalized transportation in high traffic density areas. Background Art

[0002] In many countries, personalized travel takes precedence over public transportation, but the congestion on roads and highways increases traffic density at the expense of transportation efficiency. Existing public transportation systems are unable to keep up with the influx of large populations into cities. Increasing the capacity of existing public transportation systems, such as buses, railways, and ride-sharing systems, requires a large amount of infrastructure and incurs significant costs. Additionally, the ability to develop and reform existing public transportation systems is limited due to the lack of large tracts of land available for additional infrastructure. Summary of the Invention

[0003] An example system disclosed herein includes: a transfer carrier having a first mobile system, a first stacking coupler, a first magnetic coupler, and a second magnetic coupler, the transfer carrier having a first address; a transfer pod having a second mobile system, a second stacking coupler, and a second address, the second stacking coupler being configured to couple to the first stacking coupler; and a controller for: in response to obtaining a request to guide the transfer carrier from the first address to the second address, invoking the transfer pod to couple to the transfer carrier by guiding the transfer pod to move to the top of the transfer carrier using the second mobile system; and when the transfer carrier is coupled to the transfer pod, invoking the transfer carrier to move the transfer pod to a third address using the first mobile system.

[0004] A non-transitory computer-readable storage medium disclosed herein includes instructions that, when executed, cause at least one processor to perform: in response to obtaining a request to guide a transfer carrier having a first mobile system, a first magnetic coupler, a second magnetic coupler, and a first address to a second address of a transfer pod having a second mobile system, when the transfer carrier reaches the second address, invoking the transfer pod to move to the top of the transfer carrier using the mobile system; when the transfer pod moves to the top of the transfer carrier, guiding the transfer pod to couple to the transfer carrier by coupling the first stacking coupler of the transfer carrier to the second stacking coupler of the transfer pod; and in response to the transfer carrier being coupled to the transfer pod, instructing the transfer carrier to move the transfer pod to a third address using the first mobile system.

[0005] An example method disclosed herein includes the following steps: in response to obtaining a request to guide a transfer carrier having a first mobile system, a first magnetic coupler, a second magnetic coupler, and a first address to move to a second address of a transfer cabin having a second mobile system, when the transfer carrier reaches the second address, calling the transfer cabin to move to the top of the transfer carrier using the mobile system; when the transfer cabin moves to the top of the transfer carrier, guiding the transfer cabin to be coupled to the transfer cabin by coupling a first stacking coupler of the transfer carrier to a second stacking coupler of the transfer cabin; and in response to the transfer carrier being coupled to the transfer cabin, instructing the transfer carrier to use the first mobile system to move the transfer cabin to a third address. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figures 1A to 1B An isometric view depicting an example implementation of a transfer carrier for implementing the examples disclosed herein.

[0007] Figures 1C to 1E An isometric view depicting another example implementation of a transfer carrier for implementing the examples disclosed herein.

[0008] Figures 1F to 1G An isometric view depicting an example implementation of a passenger cabin for implementing the examples disclosed herein.

[0009] Figures 1H to 1I An isometric view depicting another example implementation of a passenger cabin for implementing the examples disclosed herein.

[0010] Figures 1J to 1K An isometric view depicting an example implementation of a parcel cabin for implementing the examples disclosed herein.

[0011] Figures 1L to 1M An isometric view depicting an example implementation of a parcel cabin for implementing the examples disclosed herein.

[0012] Figures 2A to 2B Depicts a Figures 1F to 1G passenger cabin coupled to Figures 1A to 1B form an example land vehicle

[0013] Figures 3A to 3B Depicts a Figures 1F to 1G passenger cabin coupled to Figure 2B form an example land vehicle Figures 1A to 1B of the transfer carrier's first isometric view.

[0014] Figures 4A to 4B Depicts a Figures 1F to 1G passenger cabin coupled to Figure 2B form an example land vehicleFigures 1A to 1B Third isometric view of the transfer carrier.

[0015] Figures 4C to 4D Depicts the Figures 1H to 1I passenger cabin connected to form an example land vehicle Figures 1C to 1E Isometric view of the transfer carrier.

[0016] Figures 5A to 5B Depicts the Figures 1J to 1K parcel cabin connected to form an example land vehicle Figures 1A to 1B Isometric view of the transfer carrier.

[0017] Figures 5C to 5D Depicts the Figures 1L to 1M parcel cabin connected to form an example land vehicle Figures 1C to 1E Isometric view of the transfer carrier.

[0018] Figures 6A to 6B Isometric view of four example land vehicles connected together.

[0019] Figure 6C Depicts the Figures 1C to 1E four transfer carriers in the

[0020] Figure 6D Depicts the Figures 1C to 1E four transfer carriers in the

[0021] Figure 6E Isometric view of four example land vehicles connected together.

[0022] Figure 6F Top view of four example land vehicles connected together.

[0023] Figure 7A Depicts the Figures 1C to 1E two transfer carriers in the

[0024] Figure 7B Depicts the Figures 1C to 1E transfer carrier connected to an example land vehicle.

[0025] Figure 7C Depicts the Figures 1C to 1E transfer carrier connected to an example land vehicle.

[0026] Figures 7D to 7E Depicts two example land vehicles connected together.

[0027] Figures 8A to 8BDepicts an example of an example land vehicle in the pre-connection stage.

[0028] Figures 8C to 8D Depicts an example land vehicle after the connection stage Figures 8A to 8B of.

[0029] Figures 8E to 8F Depicts an example land vehicle in the pre-connection stage Figures 8A to 8B of an example connection operation of the land vehicle.

[0030] Figures 9A to 9J Depicts an example connection operation for forming Figures 8A to 8B of an example land vehicle.

[0031] Figures 10A to 10B Depicts Figures 8A to 8B an example connection system of an example land vehicle.

[0032] Figures 11A to 11B Depicts an example air vehicle in the pre-connection stage.

[0033] Figures 11C to 11D Depicts an example air vehicle in the post-connection stage Figures 11A to 11B of.

[0034] Figures 11E to 11F Depicts an example air vehicle in the pre-connection stage Figures 11A to 11B of an example connection operation of the air vehicle.

[0035] Figures 12A to 12L Depicts an example connection operation for forming Figures 11A to 11B of an example air vehicle.

[0036] Figure 13 Is an example infrastructure for implementing the examples disclosed herein.

[0037] Figure 14 Is an example implementation of a transit controller.

[0038] Figure 15 Is an example implementation of a central server.

[0039] Figure 16A Depicts an example formation.

[0040] Figure 16B Depicts an example land vehicle interacting with Figure 16A the example formation.

[0041] Figure 16C Depicts another example land vehicle connecting to Figure 16A the example formation Figure 16BTop view of a first example implementation of an example land vehicle.

[0042] Figure 16D Depicts an Figure 16A example land vehicle of another example formation connected to an Figure 16B example land vehicle. Top view of a second example implementation of an

[0043] Figure 17 Depicts an example drone airport.

[0044] Figure 18A Depicts a Figure 5B drone interacting with an example land vehicle.

[0045] Figure 18B Depicts a Figure 5B and / or Figure 5D package operation associated with an example land vehicle.

[0046] Figures 19A to 19D Depicts an Figure 5B operation associated with an example land vehicle.

[0047] Figure 20 Depicts an example transportation hub for facilitating transportation operations of autonomous vehicles.

[0048] Figure 21 Depicts an example transportation station.

[0049] Figure 22 Depicts a stack of example transfer pods.

[0050] Figure 23 Is a flowchart of example machine-readable instructions that can be executed to implement a Figure 15 central server to transport example transfer pods.

[0051] Figure 24 Is a flowchart of example machine-readable instructions that can be executed to implement a Figure 15 central server to facilitate interaction with an example drone.

[0052] Figure 25 Is a flowchart of example machine-readable instructions that can be executed to implement a Figure 15 central server to instruct a Figures 1A to 1B and / or Figures 1C to 1E first of transfer carriers to connect with a Figures 1A to 1B and / or Figures 1C to 1E second of transfer carriers.

[0053] Figure 26 Is a flowchart of example machine-readable instructions that can be executed to implementFigure 15 Example central server for processing Figures 1J to 1M Flowchart of example machine-readable instructions for an example parcel compartment

[0054] Figure 27 Represents executable to implement Figure 15 Example central server for facilitating Figure 16A and / or Figure 16B Flowchart of example machine-readable instructions for operations of an example formation

[0055] Figure 28 Represents structured to execute Figures 23 to 27 Example machine-readable instructions to implement Figure 14 Block diagram of an example processor platform for an example transfer controller

[0056] Figure 29 Represents structured to execute Figures 23 to 27 Example machine-readable instructions to implement Figure 15 Block diagram of an example processing platform for an example central server

[0057] These figures are not necessarily to scale. Generally, the same reference numerals will be used throughout the drawings and the accompanying written description to represent the same or similar components. Connecting recitations (e.g., attached, coupled, connected, and joined) will be interpreted broadly and may include intermediate members between sets of elements and relative movement between elements, unless otherwise indicated. Thus, connecting recitations do not necessarily imply that two elements are directly connected and in a fixed relationship to each other.

[0058] When identifying multiple elements or components that may be separately referred to, the descriptors “first,” “second,” “third,” etc. are used herein. Unless otherwise specified or understood based on their usage context, these descriptors are not intended to ascribe any meaning of precedence, physical order or arrangement in a list, or temporal ordering, but are merely used as labels to separately denote multiple elements or components in order to understand the disclosed examples. In some examples, the descriptor “first” may be used to denote an element in a detailed description, while a different descriptor such as “second” or “third” may be used in the claims to denote the same element. In such instances, it should be understood that such descriptors are used merely for ease of denoting multiple elements or components. Detailed Description

[0059] In recent years, transportation infrastructure has become increasingly congested. The construction, management, and maintenance costs of public transportation systems are too high and time-consuming, and existing efficiency opportunities are not being utilized. Since citizens in many countries prefer personalized travel (such as operating their own cars), transportation efficiency has declined over time as congestion increases. Transportation operators (such as car drivers) are not synchronized with other car drivers, and the efficiency of the entire transportation infrastructure is lost. For example, the first car driver stopped at a traffic light must wait for the second car driver in front of the first car driver to move before moving forward. In such an example, due to the waiting time generated by unsynchronized transportation operations, fewer car drivers can pass through the traffic light, so transportation efficiency is lost.

[0060] Examples disclosed herein include example public transportation systems facilitated by autonomous transfer pods to achieve a personal transportation experience or, in some cases, the transport of goods, parcels, or other items. In some of the disclosed examples, the autonomous transfer pod can be a passenger pod (e.g., an autonomous passenger pod) that transports one or more individuals (e.g., passengers) or a parcel pod (e.g., an autonomous parcel pod) that transports goods, parcels, or other items. The autonomous transfer pod can be coupled to and decoupled from an autonomous transfer vehicle, which can be coupled to and decoupled from one or more other transfer vehicles using magnetic couplers to improve travel efficiency and throughput. Example types of autonomous transfer vehicles can be UAVs, road chassis, rail chassis, motorized hulls, etc. Advantageously, by coupling multiple autonomous transfer vehicles together for high-density transportation, the example public transportation systems can provide dynamically optimized traffic flow, power-saving efficiency, and enhanced traffic safety.

[0061] In some of the disclosed examples, magnetic couplers can be used to form formations and groups of autonomous vehicles including pods that mate with carriers to facilitate high-density transportation of goods and people. Example formations can include a group of autonomous transfer vehicles, passenger vehicles, and / or parcel vehicles coupled between powertrain vehicles. For example, a vehicle (e.g., an autonomous vehicle, an autonomous land vehicle, a land transfer assembly, etc.) can include a pod (e.g., a passenger pod, a parcel pod, etc.) coupled to and / or otherwise mating with a transfer vehicle. In some of the disclosed examples, the vehicle can be a passenger vehicle (e.g., an autonomous passenger vehicle, a land passenger vehicle, etc.) corresponding to a passenger pod coupled to a transfer vehicle. In some of the disclosed examples, the vehicle can be a parcel vehicle (e.g., an autonomous parcel vehicle, a land parcel vehicle, etc.) corresponding to a parcel pod coupled to a transfer vehicle. In some of the disclosed examples, a vehicle or an un-mated transfer vehicle can join or leave the formation at a speed that facilitates high-density transportation.

[0062] In some of the disclosed examples, an autonomous transfer vehicle transports an autonomous transfer pod to an example transport pod, such as an air-based transport pod, an orbit-based transport pod, a water-based transport pod, etc. For example, the autonomous transfer vehicle can transport the autonomous transfer pod to a drone (UAV) transport hub where one or more UAVs can be coupled to the autonomous transfer pod and fly the autonomous transfer pod to different addresses. In other examples, the autonomous transfer vehicle can transport the autonomous transfer pod to a platform of an orbital facility where the autonomous transfer pod can decouple from the autonomous transfer vehicle and be coupled to another autonomous transfer pod in a stacked configuration.

[0063] Figures 1A to 1B Depicts a transfer vehicle for transporting Figures 1F to 1M An isometric view of an example implementation of a transfer vehicle 100 for the example transfer pods 102, 104 depicted in. For example, the transfer vehicle 100 is a road or transfer chassis configured to transport Figures 1F to 1I the transfer pod 102 or Figures 1J to 1M the transfer pod 104 on a road-type surface. Alternatively, the transfer vehicle 100 may be referred to herein as a transfer pod carrier. In Figures 1A to 1B the transfer vehicle 100 is an autonomous vehicle (e.g., an autonomous transfer pod carrier, an autonomous road or transfer chassis, etc.).

[0064] Figure 1A is an isometric front view of the transfer vehicle 100, while Figure 1B is an isometric rear view of the transfer vehicle 100. The transfer vehicle 100 has a front surface 106, a rear surface 108 opposite the front surface 106, a first side surface 110 on a first side, and a second side surface 112 on a second side opposite the first side surface 110. The transfer vehicle 100 has four wheels 114A to 114D, which include a first wheel 114A and a second wheel 114B on a first side of the transfer vehicle 100 and a third wheel 114C and a fourth wheel 114D on a second side of the transfer vehicle 100.

[0065] In Figures 1A to 1B the illustrated example, the transfer vehicle 100 includes a first coupler 115 (e.g., a first stacking coupler 115) for coupling to Figures 1F to 1M the transfer pods 102, 104. In Figure 1A to FIG. 1B, the first coupler 115 is on the top surface 111 of the transfer vehicle 100. Figures 1A to 1B The first coupler 115 is a stacking coupler (e.g., a first stacking coupler). For example, the transfer vehicle 100 includes means for facilitating the transfer of Figures 1F to 1G the transfer pod 102 or Figures 1H to 1IThe first coupler 115 that stacks and / or places the transfer cabin 102 on top of the transfer carrier 100. In some examples, the first coupler 115 includes a lug-pin coupling system. For example, each of the first couplers 115 may correspond to a groove that leads to a socket that can receive a pin and latches to the pin when the pin is substantially received. Below, the first coupler 115 is described at least in conjunction with Figures 8A to 8F , Figures 9A to 9J and Figures 10A to 10B . In some examples, the first coupler 115 implements a first means for coupling. For example, the first means for coupling may include at least one of a groove or a lug. In other examples, the first means for coupling may include at least one of a groove or a socket configured to receive a pin, a plug, etc.

[0066] The transfer carrier 100 includes exemplary magnetic couplers 116, 118. The exemplary magnetic couplers 116, 118 include a first exemplary magnetic coupler 116 (e.g., 116A to 116D) on the front surface 106 as depicted in Figure 1A and a second exemplary magnetic coupler 118 (e.g., 118A to 118D) on the rear surface 108 as depicted in Figure 1B . The magnetic couplers 116, 118 are electro-permanent (EP) magnets controlled by an exemplary switch unit 120 and a transfer controller 122. In FIGS. 1A to Figure 1B , the magnetic couplers 116, 118 are depicted as circular or disc-shaped structures protruding from the transfer carrier 100. Alternatively, the magnetic couplers 116, 118 may have any other shape, size, and / or depth other than that depicted in Figures 1A to 1B .

[0067] In Figures 1A to 1B , the magnetic couplers 116, 118 have a substantially flat circular outer surface. Alternatively, the magnetic couplers 116, 118 may have a hemispherical concave outer surface protruding from the transfer carrier 100. In some examples, the outer surface of the magnetic couplers 116, 118 is metallic, while in other examples, the outer surface is covered with a material such as rubber or hardened plastic (e.g., a protective material). Alternatively, two or more of the magnetic couplers 116, 118 may be used on the front surface 106 and / or the rear surface 108. Additionally or alternatively, as depicted in Figures 1C to 1E , one or more magnetic couplers may be used on the first side surface 110 and / or the second side surface 112.

[0068] Figures 1A to 1BThe magnetic couplers 116, 118 may include two or more magnets. For example, the magnetic couplers 116, 118 may include: (1) a semi-hard reversible electromagnet including one or more coils; and (2) a hard magnetic permanent magnet. In such an example, the electromagnet may be an alnico (AlNiCo) magnet. In other examples, the permanent magnet may be a neodymium iron boron (NdFeB) magnet. Alternatively, any other electromagnet and / or permanent magnet may be used.

[0069] In Figures 1A to 1B it, the permanent magnets and electromagnets of the magnetic couplers 116, 118 are assembled in the following arrangement or configuration: the magnets are sandwiched, pressed, and / or otherwise disposed between soft magnetic materials (e.g., iron, soft (low-carbon) steel plates, etc.). The sandwich arrangement enables the magnetic field of the permanent magnet to be turned off (i.e., terminated) based on flux cancellation. Flux cancellation can occur by transmitting a relatively short-duration high-current electrical pulse through one or more coils of the electromagnet in a first direction. Once one or more coils of the electromagnet are energized, after the magnetic field of the permanent magnet is turned off, the semi-hard material of the electromagnet retains a new magnetic field (referred to as remanence). The magnetic field can be re-established by sending another high-current electrical pulse through one or more coils of the electromagnet in a second direction opposite to the first direction.

[0070] In Figures 1A to 1B it, the transfer carrier 100 includes a switching unit 120 for controlling the coupling ability and strength of the magnetic couplers 116, 118. For example, the switching unit 120 may be a power switching unit that changes the polarity of one or more coils of the electromagnet. In such an example, the switching unit 120 may be in electrical communication with the magnetic couplers 116, 118. In some examples, the switching unit 120 includes one or more switches (e.g., electromagnetic switches, solid-state switches, etc.) or relays (e.g., electromagnetic relays, solid-state relays, etc.) to facilitate the handling of high-current electrical pulses for energizing the electromagnetic coils. For example, the switching unit 120 may be in electrical communication with and / or otherwise electrically coupled to one or more switches or relays. In such an example, the one or more switches or relays may be in electrical communication with and / or otherwise electrically coupled to the magnetic couplers 116, 118.

[0071] In some examples, the switch unit 120 can increase the coupling strength by opening one or more switches or relays to increase the amount of electrical current provided to the electromagnetic coil (e.g., increase the attractive force of one or two magnetic couplers 116, 118). In some examples, the switch unit 120 can decrease the coupling ability by closing one or more switches or relays to decrease the amount of electrical current provided to the electromagnetic coil (e.g., decrease the attractive force of one or two magnetic couplers 116, 118). In some examples, the switch unit 120 includes hardware logic, one or more hardware-implemented state machines, one or more processor-based controllers, etc. and / or combinations thereof to obtain switch commands and control the magnetic couplers 116, 118 based on the switch commands, thereby performing processor-based controller operations.

[0072] Figures 1A to 1B The illustrated example of the transfer vehicle 100 includes an example powertrain 124 for facilitating the movement of the transfer vehicle 100. In Figures 1A to 1B this case, the powertrain 124 includes one or more engines (e.g., electric motors, internal combustion engine-based engines, etc. and / or combinations thereof to form a hybrid motor system), one or more transmissions, one or more drive shafts, one or more differentials, one or more axles, final drives, etc. for manipulating and / or otherwise controlling the wheels 114A to 114D to facilitate the movement of the transfer vehicle 100. For example, the powertrain 124 can be an electric powertrain including one or more electric motors. In other examples, the powertrain 124 can be an internal combustion engine-based powertrain including one or more internal combustion engines. In other examples, the powertrain 124 can be a hybrid powertrain including one or more electric motors and / or one or more internal combustion engines.

[0073] In Figures 1A to 1B the illustrated example, the powertrain 124 includes an example power source 126. For example, the power source 126 can be one or more batteries (e.g., lithium-ion batteries) that provide electrical power to the powertrain 124 to enable the movement ability of the transfer vehicle 100. In other examples, the power source 126 can be one or more fuel storage units, each fuel storage unit including a combustible fuel for an internal combustion engine (e.g., ethanol, gasoline, hydrogen, or other suitable combustible fuels). In other examples, the power source 126 can be a hybrid power source including one or more batteries and one or more fuel storage units.

[0074] In some examples, the power source 126 can provide electrical power to the switch unit 120 (e.g., the relay or switch of the switch unit 120) to change the polarity of the electromagnetic coil. In Figures 1A to 1BIn this case, the transfer carrier 100 includes a first exemplary mobile system 127, which may correspond to at least one of one or more of the wheels 114A to 114D, the power train 124, or the power source 126. In some examples, the first mobile system 127 implements a first device for moving the transfer carrier 100 or a first device for transporting the transfer carrier 100. For example, the first device for moving the transfer carrier 100 may include and / or otherwise correspond to one or more of the wheels 114A to 114D, the power train 124, the power source 126, one or more joints, an air cushion handling system, one or more tracks, one or more rollers (e.g., pallet handling rollers), etc. and / or a combination thereof. In other examples, the first device for transporting the transfer carrier 100 may include and / or otherwise correspond to one or more of the wheels 114A to 114D, the power train 124, the power source 126, one or more joints, an air cushion handling system, one or more tracks, one or more rollers (e.g., pallet handling rollers), etc. and / or a combination thereof.

[0075] The transfer carrier 100 includes a transfer controller 122 to obtain commands, instructions (e.g., machine-readable instructions), etc. from an external computing system (e.g., a central server, a transportation computing system, etc.), and translate the obtained commands, instructions, etc. into operations of the transfer carrier 100 (e.g., a moving operation, a transporting operation, etc.). In some examples, the transfer controller 122 obtains a command to move the transfer carrier 100 to a specified address using a Global Positioning System (GPS)-based navigation system. In some examples, the transfer controller 122 obtains an instruction to couple with another transfer carrier 100 by activating and / or otherwise enabling one or two magnetic couplers 116, 118.

[0076] Figures 1A to 1B The transfer controller 122 obtains data from the exemplary sensor systems 128, 130, 132, 134. In Figure 1A this case, the transfer carrier 100 includes a first exemplary sensor system 128 on a first side of the first magnetic coupler 116 and a second exemplary sensor system 130 on a second side of the first magnetic coupler 116, where the second side is opposite the first side. In Figure 1B this case, the transfer carrier 100 includes a third exemplary sensor system 132 on a first side of the second magnetic coupler 118 and a fourth exemplary sensor system 134 on a second side of the second magnetic coupler 118, where the second side is opposite the first side. Alternatively, in Figures 1A to 1BCompared with that depicted in, the transfer vehicle 100 may include fewer or more sensor systems 128, 130, 132, 134. For example, the transfer vehicle 100 may include one or more sensor systems 128, 130, 132, 134 on the first side surface 110 and / or the second side surface 112. Alternatively, the transfer vehicle 100 may have fewer or more sensor systems 128, 130, 132, 134 than those described on the front surface 106 and / or the rear surface 108. Alternatively, one or more of the sensor systems 128, 130, 132, 134 may be at a different address or location from that Figures 1A to 1B depicted in.

[0077] In some examples, one or more of the sensor systems 128, 130, 132, 134 are camera systems for capturing images of the surroundings or environment of the transfer vehicle 100. For example, the first sensor system 128 and the second sensor system 130 may correspond to a front camera system for capturing video of the environment in front of the transfer vehicle 100. In other examples, the third sensor system 132 and the fourth sensor system 134 may correspond to a rear camera system for capturing video of the environment behind the transfer vehicle 100. In some examples, the sensor systems 128, 130, 132, 134 include a single camera (e.g., a monocular camera) for generating a single image. Alternatively, the sensor systems 128, 130, 132, 134 may include two or more cameras for producing stereoscopic images and / or stereoscopic video.

[0078] In some examples, one or more of the sensor systems 128, 130, 132, 134 represent one or more instruments or sensors that monitor characteristics or parameters of the transfer vehicle 100 and / or the environment or surroundings of the transfer vehicle 100. For example, one or more of the sensor systems 128, 130, 132, 134 may include an accelerometer, a depth sensor, a humidity sensor, a light sensor, a light detection and ranging (LIDAR) system, a humidity sensor, a pressure sensor, a speed sensor (e.g., a motor encoder, a wheel speed sensor, etc.), a radio detection and ranging (RADAR) system (e.g., a Doppler radar, a pulsed Doppler system, etc.), a temperature sensor, an ultrasonic sensor, etc. or any other sensor and / or a combination thereof. For example, the transfer controller 122 may obtain sensor data or information including measurements from one or more of the sensor systems 128, 130, 132, 134. In some examples, the sensor systems 128, 130, 132, 134 include hardware logic for facilitating obtaining sensor information and / or translating the sensor information into a machine-readable format that can be processed by at least the transfer controller 122, one or more hardware-implemented state machines, one or more processor-based controllers, etc. and / or a combination thereof.

[0079] Figures 1C to 1E An isometric view of an example transfer vehicle 135 is depicted, and the transfer vehicle 135 is Figure 1A another example implementation of the transfer vehicle 100 of FIG. 1B. Unless otherwise specified, Figures 1C to 1E the operation and / or structure of the transfer vehicle 135 is the same as Figures 1A to 1B that of the transfer vehicle 100. For example, Figures 1C to 1E the transfer vehicle 135 is configured to transport Figures 1F to 1G the transfer cabin 102 or Figures 1H to 1I the transfer cabin 104 on a road-type surface, which is a road or transfer chassis.

[0080] Figure 1C is an isometric front view of the first side of the transfer vehicle 135. Figure 1D is an isometric rear view of the first side of the transfer vehicle 135. Figure 1E is an isometric front view of the second side of the transfer vehicle 135. Figures 1C to 1E The transfer vehicle 135 includes a third example magnetic coupler 119 on the first side surface 110 and a fourth example magnetic coupler 121 on the second side surface 112. The third magnetic coupler 119 and the fourth magnetic coupler 121 are EP magnets controlled by a switch unit 120 and the transfer controller 122. In Figures 1C to 1EIn [description], the third magnetic coupler 119 and the fourth magnetic coupler 121 are depicted as oval structures protruding from the transfer carrier 135. Alternatively, the third magnetic coupler 119 and the fourth magnetic coupler 121 can have any other shape, size, and / or depth other than those depicted in Figures 1C to 1E In some examples, the outer surfaces of the third magnetic coupler 119 and the fourth magnetic coupler 121 are metallic, while in other examples, materials such as rubber or hardened plastic (e.g., protective materials) are used to cover the outer surfaces. Alternatively, two or more of the third magnetic coupler 119 and the fourth magnetic coupler 121 can be used on the first side surface 110 and / or the second side surface 112.

[0081] Figures 1C to 1E The third magnetic coupler 119 and the fourth magnetic coupler 121 of [description] can include two or more magnets. For example, the third magnetic coupler 119 and the fourth magnetic coupler 121 can include: (1) a semi-hard reversible electromagnet including one or more coils; and (2) a hard magnetic permanent magnet. In such examples, the electromagnet can be an AlNiCo magnet. In other examples, the permanent magnet can be a NdFeB magnet. Alternatively, any other electromagnet and / or permanent magnet can be used.

[0082] In Figures 1C to 1E In [description], the permanent magnets and electromagnets of the third magnetic coupler 119 and the fourth magnetic coupler 121 are assembled in the following arrangement or configuration: the magnets are sandwiched, pressed, and / or otherwise disposed between soft magnetic materials (e.g., iron, soft (low-carbon) steel plates, etc.). For example, the third magnetic coupler 119 and the fourth magnetic coupler 121 can be controlled and / or otherwise operated in the same or substantially similar manner as the first magnetic coupler 116 and the second magnetic coupler 118 of Figures 1A to 1B In such examples, the switch unit 120 can control the third magnetic coupler 119 and the fourth magnetic coupler 121 in the same or substantially similar manner as the first magnetic coupler 116 and the second magnetic coupler 118.

[0083] Figures 1F to 1G An isometric front view of an example implementation of the transfer module 102 is depicted. Figure 1F It is an isometric front view of the first side of the transfer module 102. Figure 1G It is an isometric front view of the second side of the transfer module 102, where the second side is opposite to the first side. Figures 1F to 1G The transfer module 102 of [description] is an autonomous transfer module. Figures 1F to 1GThe transfer cabin 102 is referred to as the passenger cabin in this document and includes a passenger compartment, cockpit, or interior that can accommodate one or more persons. For example, the interior of the passenger cabin 102 can be substantially similar to a conventional automobile interior, which includes: one or more seats and seat belts, and includes an electronic screen and other controls (e.g., air conditioning and heating controls, entertainment (e.g., movies, music, Wi-Fi, etc.) controls), etc. Figures 1F to 1G The passenger cabin 102 of includes one or more windows 136.

[0084] In Figure 1F In the illustrated example of, the passenger cabin 102 has a front surface 138 on the front side, a rear surface 140 on the rear side opposite the front side, a first side surface 142 on the first side, a second side surface 144 on the second side opposite the first side, and a top surface (e.g., roof, roof surface, etc.) 146 on the top side. For example, metal materials (e.g., aluminum, steel, etc.), non-metal materials (e.g., carbon fiber, plastic, etc.), etc. and / or combinations thereof can be used to manufacture the frames, structures, etc. of the surfaces 138, 140, 142, 144, 146.

[0085] In Figure 1F In the illustrated example of, the passenger cabin 102 has a first magnetic coupler 148 (e.g., 148A to 148D) on the first side surface 142. In Figure 1G In, the passenger cabin 102 has a second magnetic coupler 150 (e.g., 150A to 150B) on the second side surface 142. The first magnetic coupler 148 and the second magnetic coupler 150 are the same as the first magnetic coupler 116 and the second magnetic coupler 118 of the transfer carrier 100 of Figures 1A to 1B Alternatively, one or both of the magnetic couplers 148, 150 can be different. Alternatively, the first side surface 142 and / or the second side surface 144 can have more than one of the magnetic couplers 148, 150. Alternatively, the magnetic couplers 148, 150 can be at different addresses and / or positions on the first side surface 142 and / or the second side surface 144 than those depicted in Figures 1F to 1G In.

[0086] In Figures 1F to 1G In the illustrated example of, the passenger cabin 102 includes first magnetic coupler 148 and second magnetic coupler 150 for facilitating connection (e.g., magnetic connection) with one or more different passenger cabins 102 and / or one or more of the transfer cabins 104 depicted in Figures 1J to 1M In. For example, the passenger cabin 102 can be connected to a first passenger cabin using the first magnetic coupler 148 and / or can be connected to a second passenger cabin using the second magnetic coupler 150. In Figures 1F to 1GIn this case, the passenger cabin 102 includes a first coupler 115 for facilitating connection to an aircraft (e.g., an unmanned aerial vehicle (UAV), an unpiloted aerial vehicle, a helicopter, a vertical takeoff and landing (VTOL) aircraft). Below, the passenger cabin 102 connected to an aircraft is described in conjunction with Figures 1A to 1B and Figures 11A to 11F and Figures 12A to 12L The passenger cabin 102 described in

[0087] Figures 1F to 1G includes one or more second example movement systems 152 for controlling the movement of the passenger cabin 102 when not connected to the transfer carrier 100 of Figures 1A to 1B or the transfer carrier 135 of Figures 1C to 1D . Below, the second movement system 152 is described in conjunction with Figures 8A to 8F and Figures 9A to 9J . For example, the second movement system 152 of the passenger cabin 102 may include and / or otherwise correspond to multiple wheels, one or more engines, one or more joints, one or more power sources (e.g., one or more batteries, one or more fuel storage units, etc.), and / or combinations thereof. In such an example, the second movement system 152 may guide the movement of the passenger cabin 102 and / or otherwise climb onto the tops of the transfer carriers 100, 135 to connect to the transfer carriers 100, 135, etc.

[0088] In some examples, the second movement system 152 implements a second device for moving the passenger cabin 102 or a second device for transporting the passenger cabin 102. For example, the second device for moving the passenger cabin 102 may include and / or otherwise correspond to multiple wheels, one or more electric motors, one or more joints, one or more power sources (e.g., one or more batteries), an air cushion handling system, one or more tracks, one or more rollers (e.g., pallet handling rollers), and / or combinations thereof. In other examples, the second device for transporting the passenger cabin 102 may include and / or otherwise correspond to multiple wheels, one or more electric motors, one or more joints, one or more power sources (e.g., one or more batteries), an air cushion handling system, one or more tracks, one or more rollers (e.g., pallet handling rollers), and / or combinations thereof.

[0089] Figures 1F to 1G The passenger cabin 102 of Figures 1A to 1E includes a transfer controller 122 for obtaining sensor measurements from example sensor systems 154, 156. The sensor systems 154, 156 may correspond to Figure 1AThe sensor systems 128, 130, 132, 134 up to FIG. 1E. The sensor systems 154, 156 of the passenger compartment 102 include a first exemplary sensor system 154 on the front surface 138 and a second exemplary sensor system 156 on the rear surface 140 (depicted in Figures 2A to 2B ). Alternatively, the passenger compartment 102 may include fewer or more sensor systems 154, 156. For example, the passenger compartment 102 may include one or more sensor systems 154, 156 on the front surface 138, rear surface 140, first side surface 142, second side surface 144, top surface 146, etc. Alternatively, one or both of the sensor systems 154, 156 may be at a different address or location than that depicted in Figures 1F to 1G or described in connection with Figure 1F up to FIG. 1G.

[0090] Figures 1F to 1G The passenger compartment 102 of includes a switch unit 120 and a transfer controller 122 for obtaining commands, instructions, etc. from an external computing system and translating the obtained commands, instructions, etc. into operations of the passenger compartment 102 (e.g., movement operations, transportation operations, etc.). Figures 1A to 1E In some examples, the transfer controller 122 obtains a command to move the passenger compartment 102 to a specified address using GPS. In some examples, the transfer controller 122 obtains an instruction coupled to the Figures 1A to 1B and / or Figures 1C to 1E transfer vehicle 100. In some examples, the transfer controller 122 obtains: (1) a command to couple the passenger compartment 102 to the aircraft by instructing the second movement system 152 to move to a position coupled to the aircraft; and / or (2) a command to couple the passenger compartment 102 to another passenger compartment 102 by instructing the switch unit 120 to activate and / or otherwise enable one or both of the first magnetic coupler 148 and the second magnetic coupler 150.

[0091] Figures 1H to 1I Depicts an isometric view of an exemplary passenger compartment 155 (e.g., 155A to 155D), the passenger compartment 155 being Figures 1F to 1G another exemplary implementation of the passenger compartment 102. Unless otherwise specified, the operation and / or structure of the transfer compartment 155 from FIGS. 1H to Figure 1I is the same as the operation and / or structure of the transfer compartment 102 of Figures 1F to 1G . Figure 1H Is an isometric front view of the first side of the transfer compartment 155. Figure 1I Is an isometric front view of the second side of the transfer compartment 155, where the second side is opposite the first side. Figures 1H to 1I The transfer compartment 155 of is an autonomous transfer compartment. Figures 1H to 1I The transfer compartment 155 of is referred to herein as a passenger compartment. Figures 1H to 1IThe passenger cabin 155 does not include Figures 1F to 1G the switch unit 120 and the magnetic couplers 148, 150.

[0092] Figures 1J to 1K An isometric front view depicting an example implementation of the transfer cabin 104. Figure 1J Is an isometric front view of the first side of the transfer cabin 104. Figure 1K Is an isometric front view of the second side of the transfer cabin 104, where the second side is opposite to the first side. Figures 1J to 1K The transfer cabin 104 of is an autonomous transfer cabin. Figures 1J to 1K The transfer cabin 104 of is referred to herein as a parcel cabin and can accommodate or load goods, merchandise, parcels, or other items. For example, the interior of the parcel cabin 104 can be substantially similar to a conventional automobile trunk, the parcel space of a delivery truck, etc. In some examples, the transfer cabin 104 can accommodate or load live animals (e.g., birds, cows, chickens, horses, pigs, etc.) for transportation. In some examples, the transfer cabin 104 can accommodate or load items that are not packaged but can be placed in the transfer cabin 104 for transportation. For example, the transfer cabin 104 can transport items such as art paintings or sculptures, automobiles, bicycles, building materials, furniture, etc. In some examples, the transfer cabin 104 can be a dedicated cabin equipped for transporting refrigerated items (e.g., meat products, agricultural products, etc.), heated items (e.g., cooked foods such as pizza, full meals, etc.), bulk items (e.g., grains, topsoil, lumber, firewood, etc.), heavy items (e.g., vending machines, pinball machines, etc.). In some examples, the transfer cabin 104 can store Figures 1F to 1G or Figures 1H to 1I different transfer cabins in the transfer cabin 102 or any other type of transfer cabin described herein.

[0093] In Figures 1J to 1K the illustrated example of, the parcel cabin 104 has a front surface 160, a rear surface 162 opposite to the front surface 160, a first side surface 164 on the first side, a second side surface 166 on the second side opposite to the first side, and a top surface (e.g., a vehicle roof, a roof surface, etc.) 168. For example, metal materials (e.g., aluminum, steel, etc.), non-metal materials (e.g., carbon fiber, plastic, etc.), etc. and / or combinations thereof can be used to manufacture the frames, structures, etc. of the surfaces 160, 162, 164, 166, 168.

[0094] In Figures 1J to 1K the illustrated example of, the parcel cabin 104 has a first example magnetic coupler 170 on the first side surface 164 and a second example magnetic coupler 172 on the second side surface 166. The first magnetic coupler 170 and the second magnetic coupler 172 are connected to Figures 1A to 1EThe first magnetic couplers 116 and 118 of the transfer carriers 100, 135 and / or Figures 1F to 1G The first magnetic couplers 148 and 150 of the passenger compartment 102 are the same. Alternatively, one or both of the first magnetic coupler 170 and the second magnetic coupler 172 may be different. Alternatively, the first side surface 164 and / or the second side surface 166 may have more than one of the magnetic couplers 170, 172. Alternatively, the magnetic couplers 170, 172 may be at different addresses and / or positions on the first side surface 164 and / or the second side surface 166 than those depicted in Figures 1J to 1K In the illustrated example of

[0095] In Figures 1J to 1K the illustrated example, the parcel compartment 104 includes first magnetic couplers 170 and 172 for facilitating connection (e.g., magnetic connection) with one or more different parcel compartments 104 and / or Figures 1F to 1G one or more in the passenger compartment 102 depicted in. For example, the parcel compartment 104 may be connected to the passenger compartment using the first magnetic coupler 170 and / or may be connected to a different parcel compartment 104 using the second magnetic coupler 172. In Figures 1J to 1K the parcel compartment 104 includes a first coupler 115 for facilitating connection to an aircraft (e.g., UAV, drone, helicopter, etc.). Below, in connection with Figures 1A to 1E and Figures 11A to 11F and Figure 12A to Figure 12L describe the parcel compartment 104 connected to the aircraft.

[0096] In Figures 1J to 1K the illustrated example, the parcel compartment 104 has an exemplary hatch 174. The hatch 174 is a slidable and movable surface (e.g., skylight, sliding top, etc.) for exposing the interior of the parcel compartment 104 to ambient air to facilitate interaction with another entity such as a UAV. For example, the transfer controller 122 of the parcel compartment 104 may open the hatch 174. In such an example, the parcel compartment 104 may include means for identifying the packages stored in the parcel compartment 104. For example, the means for identifying the packages may include a barcode scanner, a quick response (QR) code scanner, a computer vision system, etc. and / or a combination thereof. The parcel compartment 104 may include means for lifting and / or passing the packages through the hatch 174. For example, the means for lifting the packages may include a lift platform, a liftable surface, a hoist, etc. and / or a combination thereof. By opening the hatch 174, the transfer controller 122 of the parcel compartment 104 may facilitate the aircraft flying to the parcel compartment 104 and taking possession of the packages, as described below in connection with Figure 18A In

[0097] Figures 1J to 1K The parcel compartment 104 includes means for when not connected toFigures 1A to 1B Figures 1 to when controlling the movement of the transfer carrier 100 of the package compartment 104 Figure 1I of the second movement system 152. Next, in conjunction with Figure 8A to Figures 8F and Figures 9A to 9J Describe the second movement system 152. For example, the second movement system 152 can guide the movement of the package compartment 104 and / or otherwise climb onto the tops of the transfer carriers 100, 135 to be coupled to the transfer carriers 100, 135, etc.

[0098] Figures 1J to 1K The package compartment 104 of includes means for obtaining sensor measurements from the example sensor systems 176, 178 Figures 1A to 1E of the transfer controller 122. The sensor systems 176, 178 can correspond to Figure 1A the sensor systems 128, 130, 132, 134 of Figures 1E to Figures 1J to 1K The sensor systems 176, 178 of include a first example sensor system 176 on the front surface 160 and a second example sensor system 178 on the rear surface 162. Alternatively, the package compartment 104 can include fewer or more sensor systems 176, 178. For example, the package compartment 104 can include one or more sensor systems 176, 178 on the front surface 160, rear surface 162, first side surface 164, second side surface 166, top surface 168, etc. Alternatively, one or two sensor systems 176, 178 can be at Figures 1J to 1K depicted different addresses or locations.

[0099] Figures 1J to 1K The package compartment 104 of includes means for obtaining commands, instructions, etc. from an external computing system and translating the obtained commands, instructions, etc. into operations of the package compartment 104 (e.g., movement operations, transportation operations, etc.) Figures 1A to Figure 1E of the switch unit 120 and the transfer controller 122. In some examples, the transfer controller 122 obtains a command to move the package compartment 104 to a specified address using GPS. In some examples, the transfer controller 122 obtains an instruction to be coupled to Figures 1A to 1E the transfer carriers 100, 135. In some examples, the transfer controller 122 obtains: (1) a command to couple the package compartment 104 to the aircraft by instructing the second movement system 152 to move to a position coupled to the aircraft; and / or (2) a command to couple the package compartment 104 to another package compartment 104 and / or the passenger compartment 102 by instructing the switch unit 120 to activate and / or otherwise enable one or both of the first magnetic coupler 170 and the second magnetic coupler 172.

[0100] Figures 1L to 1MDepicts an isometric view of the transfer cabin 180 in the example, where the transfer cabin 180 is Figures 1J to 1K another example implementation of the transfer cabin 104 of Figures 1L to 1M . Unless otherwise specified, Figures 1J to 1K the operation and / or structure of the transfer cabin 180 is the same as that of Figure 1L the transfer cabin 104. Figure 1M Is an isometric front view of the first side of the transfer cabin 180. Figures 1L to 1M The transfer cabin 180 of Figures 1L to 1M is an autonomous transfer cabin. Figures 1L to 1M The transfer cabin 180 of Figures 1J to 1K does not include the switch unit 120 and

[0101] Figure 2A , Figure 3A and Figure 4A Depicts the Figures 1F to 1G transfer carrier 100 separated from the passenger cabin 102 of Figure 1A to Figure 1B in an isometric view. Figure 2A Is an isometric rear view, Figure 3A is an isometric bottom view, and Figure 4A is an isometric front view. Figure 2B , Figure 3B and Figure 4B Depicts an isometric view of the first example land vehicle 200, which includes Figures 1F to 1G the transfer carrier 100 connected to the passenger cabin 102 of Figure 1A to Figure 1B . Figure 2B Is an isometric rear view, Figure 3B is an isometric bottom view, and Figure 4B is an isometric front view.

[0102] In some examples, Figure 2ADepicts the transfer vehicle 100 after detaching from the passenger compartment 102 and moving away from the passenger compartment 102 after detachment. For example, the transfer controller 122 of the passenger compartment 102 may obtain a first request to detach from the transfer vehicle 100 (e.g., from an external computing system), and the transfer controller 122 of the transfer vehicle 100 may obtain a second request to move from the passenger compartment 102 to a different address after detachment. In such an example, the transfer controller 122 of the passenger compartment 102 may direct the second movement system 152 of the passenger compartment 102 to detach from the transfer vehicle 100 and move away from it. The transfer controller 122 of the transfer vehicle 100 may direct the power train 124 to engage the wheels 114A - 114D to move the transfer vehicle 100 to a different address.

[0103] In some examples, Figure 2A Depicts the transfer vehicle 100 moving towards the passenger compartment 102 to attach to the passenger compartment 102. For example, the transfer controller 122 of the transfer vehicle 100 may obtain a first request to move from a first address of the passenger compartment 102 to a second address (e.g., from an external computing system), and the transfer controller 122 of the passenger compartment 102 may obtain a second request to attach to the transfer vehicle 100 in response to the transfer vehicle 100 moving to the second address. In such an example, the transfer controller 122 of the passenger compartment 102 may direct the second movement system 152 of the passenger compartment 102 to move towards the transfer vehicle 100 and attach to the transfer vehicle 100. The transfer controller 122 of the transfer vehicle 100 may direct the power train 124 to engage the wheels 114A - 114D to move the transfer vehicle 100 towards the passenger compartment 102 to attach to the passenger compartment 102.

[0104] Figure 4C Depicts separated from Figures 1H to 1I the passenger compartment 155 Figures 1C to 1E an isometric view of the transfer vehicle 135. Figure 4D Depicts an isometric view of a second example land vehicle 400 that includes a transfer vehicle 135 attached to Figures 1H to 1I the passenger compartment 155 Figures 1C to 1E of.

[0105] Figure 5A Depicts separated from Figures 1J to 1K the package compartment 104 Figures 1A to 1B an isometric view of the transfer vehicle 100. Figure 5B Depicts an isometric view of a third example land vehicle 500 that includes a transfer vehicle 100 attached to Figures 1J to 1K the package compartment 104 Figures 1A to 1B of.

[0106] In some examples, Figure 5A depicts the transfer vehicle 100 after it has disengaged from the package pod 104 and moved away from the package pod 104 after disengagement. For example, the transfer controller 122 of the package pod 104 may obtain (e.g., from an external computing system) a first request to disengage the transfer vehicle 100, and the transfer controller 122 of the transfer vehicle 100 may obtain (e.g., from an external computing system) a second request to move from the package pod 104 to a different address after disengagement. In such an example, the transfer controller 122 of the package pod 104 may direct the second movement system 152 of the package pod 104 to disengage from the transfer vehicle 100 and move away from it. The transfer controller 122 of the transfer vehicle 100 may direct the powertrain 124 to engage the wheels 114A - 114D to move the transfer vehicle 100 to a different address.

[0107] In some examples, Figure 5A depicts the transfer vehicle 100 moving towards the package pod 104 to couple to the package pod 104. For example, the transfer controller 122 of the transfer vehicle 100 may obtain (e.g., from an external computing system) a first request to move from a first address of the package pod 104 to a second address, and the transfer controller 122 of the package pod 104 may obtain (e.g., from an external computing system) a second request to couple to the transfer vehicle 100 in response to the transfer vehicle 100 moving to the second address. In such an example, the transfer controller 122 of the package pod 104 may direct the second movement system 152 of the package pod 104 to move towards the transfer vehicle 100 and couple to the transfer vehicle 100. The transfer controller 122 of the transfer vehicle 100 may direct the powertrain 124 to engage the wheels 114A - 114D to move the transfer vehicle 100 towards the package pod 104 to couple to the package pod 104.

[0108] Figure 5C depicts the Figures 1L to 1M transfer vehicle 135 separated from the Figures 1C to 1E package pod 180 in an isometric view. Figure 5D depicts an isometric view of a fourth example land vehicle 510 that includes a Figures 1L to 1M transfer vehicle 135 coupled to the Figures 1C to 1E package pod 180.

[0109] Figure 6A depicts an isometric front view of four example vehicles (e.g., land vehicles) 200A - 200D that are coupled together. Figure 6B depicts an isometric top view of four land vehicles 200A - 200D. Each of the four land vehicles 200A - 200D may correspond to Figure 2B , Figure 3Band Figure 4B a first land vehicle 200. For example, each of land vehicles 200A to 200D may include Figures 1A to 1B a transfer carrier 100 and Figures 1F to 1G a passenger cabin 102. In Figures 6A to 6B , four land vehicles 200A, 200B, 200C, 200D include a first land vehicle 200A, a second land vehicle 200B, a third land vehicle 200C, and a fourth land vehicle 200D. For example, the first land vehicle 200A includes a first transfer carrier 100A coupled to a first passenger cabin 102A, the second land vehicle 200B includes a second transfer carrier 100B coupled to a second passenger cabin 102B, the third land vehicle 200C includes a third transfer carrier 100C coupled to a third passenger cabin 102C, and the fourth land vehicle 200D includes a fourth transfer carrier 100D coupled to a fourth passenger cabin 102D.

[0110] In Figures 6A to 6B the illustrated example, a linear connection (e.g., a straight-line connection) between the land vehicles among land vehicles 200A to 200D is depicted. For example, in Figures 6A to 6B , a second magnetic coupler 118 of the first transfer carrier 100A is coupled to a first magnetic coupler 116 of the second transfer carrier 100B. In FIGS. 6A to Figure 6B , a second magnetic coupler 118 of the third transfer carrier 100C is coupled to a first magnetic coupler 116 of the fourth transfer carrier 100D. Alternatively, Figures 6A to 6B one or more of the passenger cabins 102A to 102D of Figures 1J to 1K may be replaced by a parcel cabin 104 of

[0111] In Figures 6A to 6B the illustrated example, a side-by-side connection between the land vehicles among land vehicles 200A to 200D is depicted. For example, in Figures 6A to 6B , a second magnetic coupler 150A of the first passenger cabin 102A is coupled to a first magnetic coupler 148C of the third passenger cabin 102C. In Figures 6A to 6B , a second magnetic coupler 150B of the second passenger cabin 102B is coupled to a first magnetic coupler 148D of the fourth passenger cabin 102D.

[0112] Figure 6C An isometric view of four instances 135A to 135D of a transfer carrier 135 that are coupled together is depicted. Figures 1C to 1E An isometric view of four instances 135A to 135D of the transfer carrier 135 that are coupled together is depicted. In Figure 6D a top view of four instances 135A to 135D of the transfer carrier 135 that are coupled together is depicted. In Figures 6C to 6DAmong them, the four instances 135A to 135D include a first transfer carrier 135A, a second transfer carrier 135B, a third transfer carrier 135C, and a fourth transfer carrier 135D.

[0113] In Figures 6C to 6D the illustrated example of, a linear connection (e.g., a straight-line connection) between the transfer carriers among the transfer carriers 135A to 135D is depicted. For example, in Figure 6D the second magnetic coupler 118A of the first transfer carrier 135A is coupled to the first magnetic coupler 116B of the second transfer carrier 135B. In Figure 6D the second magnetic coupler 118C of the third transfer carrier 135C is coupled to the first magnetic coupler 116D of the fourth transfer carrier 135D.

[0114] In Figures 6C to 6D the illustrated example of, a side-by-side connection between the transfer carriers among the transfer carriers 135A to 135D is depicted. For example, in Figure 6D the fourth magnetic coupler 121A of the first transfer carrier 135A is coupled to the third magnetic coupler 119C of the third transfer carrier 135C. In Figure 6D the fourth magnetic coupler 121B of the second transfer carrier 135B is coupled to the third magnetic coupler 119D of the fourth transfer carrier 135D.

[0115] Figure 6E An isometric view of four instances 400A to 400D of the second land vehicle 400 that are coupled together is depicted. Figure 4D Figure 6F A top view of four instances 400A to 400D of the second land vehicle 400 that are coupled together is depicted. Figure 4D Figure 6E Each of the four land vehicles 400A to 400D depicted in Figure 4D may correspond to Figure 6E the second land vehicle 400. For example, Figures 1C to 1E each of the four land vehicles 400A to 400D may include Figures 1H to 1I the transfer carrier 135 of Figure 6EAmong them, the four land vehicles 400A, 400B, 400C, and 400D include the first land vehicle 400A, the second land vehicle 400B, the third land vehicle 400C, and the fourth land vehicle 400D. For example, the first land vehicle 400A includes a first transfer carrier 135A connected to the first passenger cabin 155A, the second land vehicle 400B includes a second transfer carrier 135B connected to the second passenger cabin 155B, the third land vehicle 400C includes a third transfer carrier 135C connected to the third passenger cabin 155C, and the fourth land vehicle 400D includes a fourth transfer carrier 135D connected to the fourth passenger cabin 155D.

[0116] In Figures 6E to 6F the illustrated example of, a linear connection (e.g., a straight-line connection) between the land vehicles among the land vehicles 400A to 400D is depicted. For example, in Figure 6F the second magnetic coupler 118A of the first transfer carrier 135A is connected to the first magnetic coupler 116B of the second transfer carrier 135B. In Figure 6F the second magnetic coupler 118C of the third transfer carrier 135C is connected to the first magnetic coupler 116D of the fourth transfer carrier 135D.

[0117] In Figures 6E to 6F the illustrated example of, a side-by-side connection between the land vehicles among the land vehicles 400A to 400D is depicted. For example, in Figure 6F the fourth magnetic coupler 121A of the first transfer carrier 135A is connected to the third magnetic coupler 119C of the third transfer carrier 135C. In Figure 6F the fourth magnetic coupler 121B of the second transfer carrier 135B is connected to the third magnetic coupler 119D of the fourth transfer carrier 135D.

[0118] Figure 7A Two instances 135A to 135B of the transfer carrier 135 that are connected together are depicted. In Figures 1C to 1E the two instances 135A to 135B include the first transfer carrier 135A and the second transfer carrier 135B. In Figure 7A the transfer carriers 135A to 135B are connected together because, as illustrated in Figure 7A the second magnetic coupler 118A of the first transfer carrier 135A is connected to the first magnetic coupler 116B of the second transfer carrier 135B, as illustrated in Figure 6D Among them.

[0119] Figure 7B Depicted is Figures 1C to 1E the transfer carrier 135 connected to Figure 4DThe second land vehicle 400. In Figure 7B the second land vehicle 400 is coupled to the transfer carrier 135 because, as Figure 6D illustrated in

[0120] Figure 7C the second magnetic coupler 118A of the first transfer carrier 135A (e.g., of the second land vehicle 400) is coupled to the first magnetic coupler 116B of the second transfer carrier 135B. Figure 5B depicts the transfer carrier 135 coupled to the Figures 1C to 1E third land vehicle 500. In Figure 7C the transfer carrier 135 is coupled to the third land vehicle 500 because, as Figure 6D illustrated in

[0121] Figure 7D depicts the transfer carrier 135 coupled to the Figure 5B third land vehicle 500 and Figure 2B the Figure 3B and Figure 4B first land vehicle 200. In Figure 7D the first land vehicle 200 is coupled to the third land vehicle 500 because the second magnetic coupler 118A of the first land vehicle 200 is coupled to the first magnetic coupler 116B of the third land vehicle 500.

[0122] Figure 7E depicts the transfer carrier 135 coupled to the Figure 5D fourth land vehicle 510 and Figure 4D the second land vehicle 400. In Figure 7E the second land vehicle 400 is coupled to the fourth land vehicle 510 because the second magnetic coupler 118A of the second land vehicle 400 is coupled to the first magnetic coupler 116B of the fourth land vehicle 510.

[0123] Figure 8A depicts a side view of an exemplary land vehicle 800 in a pre - coupling stage. Figure 8B depicts a rear view of the Figure 8A land vehicle 800 in a pre - coupling stage. When describing the exemplary coupling operations associated with the land vehicle 800, the land vehicle 800 is illustrated in a generalized manner for clarity. For example, the land vehicle 800 may correspond to Figure 2B the Figure 3B and Figure 4Bthe first land vehicle 200, Figure 4D the second land vehicle 400, Figure 5B the third land vehicle 500 or Figure 5D the fourth land vehicle 510. In such an example, any description (e.g., functional and / or structural description) associated with Figures 8A to 8F applies to Figure 2B , Figure 3B and Figure 4B the first land vehicle 200, Figure 4D the second land vehicle 400, Figure 5B the third land vehicle 500 or Figure 5D the fourth land vehicle 510.

[0124] In Figures 8A to 8B the illustrated example, the land vehicle 800 after connection includes Figure 1A to Figure 1B the transfer carrier 100 and the example transfer cabin 802. Alternatively, Figure 8A the land vehicle may include Figures 1C to 1E the transfer carrier 135. When describing the example connection operation associated with the transfer carrier 135, the transfer cabin 802 is illustrated in a general way for clarity. For example, the transfer cabin 802 may correspond to Figures 1F to 1G or Figures 1H to 1I the passenger cabin 102 or Figures 1J to 1K or Figures 1L to 1M the parcel cabin 104. In such an example, any description (e.g., functional and / or structural description) associated with Figures 8A to 8F applies to Figures 1F to 1G or Figures 1H to 1I the passenger cabin 102 or Figures 1J to 1K or Figures 1L to 1M the parcel cabin 104.

[0125] In Figures 8A to 8B the illustrated example, the land vehicle 800 is in the pre-connection stage. For example, the transfer cabin 802 and the transfer carrier 100 are in a pre-latching or pre-connection position where the transfer cabin 802 and the transfer carrier 100 are not connected. The transfer cabin 802 includes a Figures 1A to 1M first coupler 115 on the top surface of the transfer cabin 802. In Figures 8A to 8B , the first coupler 115 includes an example groove 804 and an example lug (e.g., pin lug) 806. For example, the lug 806 may be configured to receive and / or otherwise obtain a pin from a coupler associated with the UAV. Alternatively, the first coupler 115 may include a cavity and / or socket for receiving a plug or other coupler insertion structure associated with the UAV.

[0126] The transfer cabin 802 includesFigures 1F to 1I and / or Figures 1J to 1M a second mobile system 152. The transfer cabin 802 includes four instances of the second mobile system 152. Alternatively, the transfer cabin 802 may have fewer or more than four instances of the second mobile system 152. As used herein, the four instances of the second mobile system 152 may collectively be referred to as the transfer cabin mobile system. In Figures 8A to 8B some examples, the second mobile system 152 includes an example motor 810 and example wheels (e.g., mobile wheels) 812. In Figures 8A to 8B some examples, the motor 810 is a traction motor. Alternatively, any other type of motor such as a compressed air (or other gas) motor may be used. In Figure 8A to Figure 8B some examples, the mobile wheels 812 are in an extended or deployed position. For example, when the mobile wheels 812 are in the extended position, the transfer cabin 802 may travel at a non-zero speed.

[0127] In some examples, the second mobile system 152 corresponds to and / or otherwise includes a power train, a power source, and / or the mobile wheels 812. Alternatively, fewer or more than four mobile wheels 812 may be used. For example, the power train of the second mobile system 152 may include one or more electric motors, one or more transmissions, one or more drive shafts, one or more differentials, one or more axles, final drives, etc. for manipulating and / or otherwise controlling the four mobile wheels 812 to effect the movement of the transfer cabin 802.

[0128] In some examples, the power source of the second mobile system 152 includes one or more batteries (e.g., lithium-ion batteries) that supply power to one or more electric motors of the power train of the second mobile system 152 to effect the movement of the transfer cabin 802. Alternatively, the power source of the second mobile system 152 may be any other energy storage element or device (e.g., a capacitor bank, a chemical or liquid reservoir (e.g., a compressed air tank, a gasoline tank, a hydrogen tank, etc.). In some examples, the power source of the second mobile system 152 may supply power to the switch unit 120 of the passenger cabin 102 to change the polarity of the electromagnetic coils of one or more of the first magnetic coupler 148 and the second magnetic coupler 150 of the passenger cabin 102. In some examples, the power source of the second mobile system 152 may supply power to the switch unit 120 of the parcel cabin 102 to change the polarity of the electromagnetic coils of one or more of the first magnetic coupler 170 and the second magnetic coupler 172 of the parcel cabin 104.

[0129] In Figures 8A to 8B some examples, the mobile wheels 812 are coupled to an example joint (e.g., a pivot joint) 814. For example, the joint 814 may effect the movement of the mobile wheels 812 from Figure 8A and Figure 8BThe first position depicted (e.g., extended or deployed position) is moved to Figures 9E to 9H the second position depicted (e.g., intermediate position, transitional position, etc.) or Figures 8C to 8D the third position depicted (e.g., loading position). In some examples, the joint 814 implements a means for pivoting, which may include and / or otherwise correspond to an elbow, hinge, pivot, or any other type of movable, pivotable, and / or otherwise rotatable joint. Alternatively, the means for pivoting may include any other mechanical means or structure that facilitates the pivoting or rotation of the wheel 812 about an axis, such as a ball-and-socket or saddle joint.

[0130] In Figures 8A to 8B the transfer carrier 100 includes a first coupler 115 for coupling to a second coupler 816 of the transfer pod 802. In Figures 8A to 8B the second coupler 816 is on the top surface 803 of the transfer pod 802. For example, the top surface 803 of the transfer pod 802 may correspond to Figures 1F to 1G the top surface 146 of the passenger cabin 102 of Figures 1H to 1I and / or Figures 1J to 1K the top surface 168 of the parcel compartment 104 of Figures 1L to 1M and / or the parcel compartment 180. In other examples, the top surface 803 of the transfer pod 802 may correspond to

[0131] Figures 8A to 8B The second coupler 816 of Figures 1A to 1B is a stacking coupler (e.g., second stacking coupler). For example, the transfer pod 802 includes a second coupler 816 for facilitating the stacking and / or arrangement of the transfer pod 802 on top of the transfer carrier 100 of Figure 1C or the transfer carrier 135 of FIGS. 1E. The second coupler 816 includes an exemplary pin 818. For example, the pin 818 may be configured to couple, insert, and / or mate with a lug 806 of the first coupler 115 of the transfer carrier 100. In some examples, the second coupler 816 implements a second means for coupling. For example, the second means for coupling may include and / or otherwise be implemented by at least one of a base or a pin. In other examples, the second means for coupling may include at least one of a base or an elongate member (e.g., lug, plug, etc.) configured to be received by a socket. Below, the first coupler 116 and the second coupler 816 are further described in conjunction with Figures 8E to 8F and Figures 10A to 10B FIGS.

[0132] Figure 8C FIG. 8C depicts a side view of the land vehicle 800 of Figures 8A to 8B in a pre-coupling stage. FIG. 8D depicts a side view of the land vehicle 800 of Figures 8A to 8CRear view of the land vehicle 800. In Figure 8C to Figure 8D the transfer cabin 802 and the transfer carrier 100 are in the latched or connected position where the transfer cabin 802 is connected to the transfer carrier 100.

[0133] Figures 8E to 8F Depicts a view of an exemplary connection operation of Figures 8A to 8D the land vehicle 800 in the pre-connection stage. Figure 8E Depicts Figures 8A to 8D the first part of the transfer cabin 802 of Figures 8A to 8D and a side view B - B of the second part of the transfer carrier 100 of Figure 8E In, the first coupler 115 of the transfer carrier 100 is close to but not connected to the second coupler 816 of the transfer cabin 802. Figure 8F Depicts the rear view A - A also depicted in Figure 8A In. In Figure 8F the rear view A - A is the rear view of Figure 8E the first part and the second part of Figure 8F In, the first coupler 115 of the transfer carrier 100 is close to but not connected to the second coupler 816 of the transfer cabin 802.

[0134] Figures 9A to 9J Depicts Figures 8A to 8F the transfer cabin 802 of Figures 1A to 1B and the exemplary operations 910, 920, 930, 940, 950 of connecting the transfer carrier 100 of. The operations 910, 920, 930, 940, 950 include a first exemplary operation 910, a second exemplary operation 920, a third exemplary operation 930, a fourth exemplary operation 940, and a fifth exemplary operation 950.

[0135] Figure 9A Depicts a side view of the first operation 910, and Figure 9B Depicts a rear view of the first operation 910. The first operation 910 corresponds to an example where the transfer cabin 802 is moving towards the transfer carrier 100 onto an exemplary inclined platform or ramp 902. For example, the transfer controller 122 of the transfer cabin 802 can guide the second movement system 152 to move the moving wheels 812 to climb onto the top of the transfer carrier 100 and / or otherwise move onto the top of the transfer carrier 100.

[0136] Figure 9C Depicts a side view of the second operation 920, and Figure 9DDepicts a rear view of a first operation 920. The second operation 920 corresponds to an example where the transfer cabin 802 is on top of the transfer carrier 100. For example, the sensor system 904 of the transfer cabin 802 can determine that the transfer cabin 802 has traveled and / or otherwise moved to a first land connection position. The first land connection position can correspond to a position where the transfer controller 122 determines that the moving wheels 812 do not need to move further onto the transfer carrier 100 and can initiate the connection of the transfer cabin 802 to the transfer carrier 100. In some examples, the sensor system 904 corresponds to Figures 1F to 1I and Figures 2A to 2B one or both of the sensor systems 154, 156 of the passenger cabin 102. In some examples, the sensor system 904 corresponds to Figures 1J to 1M one or both of the sensor systems 176, 178 of the parcel cabin 104. For example, the transfer controller 122 can obtain the output from the LIDAR system of the transfer cabin 802 and determine that the transfer cabin 802 is in the first land connection position based on the LIDAR system output. Additionally or alternatively, a series of guides (e.g., mechanical guides, physical guides, etc.) and / or blocks (e.g., mechanical blocks, physical blocks, obstacles, etc.) can be used to maneuver the transfer cabin 802 onto the transfer chassis 100.

[0137] Figure 9E Depicts a side view of a third operation 930, and Figure 9F depicts a rear view of the third operation 930. The third operation 930 corresponds to an example where the transfer cabin 802 performs a kneeling operation on top of the transfer carrier 100 by reducing the height of the transfer cabin 802 from a first height to a second height. By rotating the moving wheels 812 clockwise to an intermediate position, the transfer cabin 802 can be lowered to align the second coupler 816 of the transfer cabin 802 with the first coupler 115 of the transfer carrier 100. For example, in response to the transfer controller 122 determining that the transfer cabin 802 is in the first land connection position, the transfer controller 122 can instruct the second movement system 152 to pivot the moving wheels 812 clockwise about the pivot to transfer the height of the transfer cabin 802 from a first height (e.g., deployed or extended height) to a second height (e.g., connection height, kneeling height, loading height, etc.), where the second height is lower than the first height. In such an example, the first height can correspond to the moving wheels 812 in the extended position to facilitate the transfer cabin 802 moving at a typical speed. In other examples, the second height can correspond to the moving wheels 812 in an intermediate position, transitional position, etc., to place and / or otherwise move the transfer cabin 802 to a second land connection position.

[0138] Figure 9G Depicts a side view of a fourth operation 940, and Figure 9HDepicts a rear view of a fourth operation 940. The fourth operation 940 corresponds to an example in which a second coupler 816 of the transfer pod 802 is interlocked, mated, and / or otherwise engaged with a first coupler 115 of the transfer carrier 100. For example, in response to the transfer controller 122 determining that the transfer pod 802 is in a second land connection position, the transfer controller 122 may instruct the second mobile system 152 to rotate the mobile wheels 812 to move the transfer pod 802 forward so that the second coupler 816 of the transfer pod 802 is coupled to the first coupler 115 of the transfer carrier 100. In response to the transfer controller 122 determining that the second coupler 816 is coupled to the first coupler 115, the transfer controller 122 instructs the second mobile system 152 to disengage the mobile wheels 812 to stop the movement of the transfer pod 802.

[0139] In some examples, the transfer controller 122 of the transfer pod 802 obtains a measurement that the second coupler 816 has been coupled to the first coupler 115 from a sensor (e.g., a pressure switch, a position sensor, etc.) of the sensor system 904 that monitors the second coupler 816. In other examples, the transfer controller 122 of the transfer carrier 100 may send wireless data (e.g., one or more wireless messages, one or more wireless data packets, etc.) to the transfer controller 122 of the transfer pod 802. For example, the wireless data may indicate that the result of the sensor associated with the sensor systems 128, 130, 132, 134 of the transfer carrier 100 monitoring the first coupler 115 is that the first coupler 115 has been coupled to the second coupler 816. In such examples, the sensors may be pressure sensors, position sensors, torque sensors, etc. In other examples, the pin 818 may have one or more conductive rings or contacts that generate an electrical signal to be obtained by the transfer controller 122 of the transfer pod 802 and / or the transfer chassis 100 when contacting one or more conductive rings or contacts of the lug 806. In such examples, the transfer controller 122 of the transfer pod 802 and / or the transfer chassis 100 may determine the position of the transfer pod 802 relative to the transfer chassis 100.

[0140] Figure 9I Depicts a side view of a fifth operation 950, and Figure 9JDepicts a rear view of a fifth operation 950. The fifth operation 950 corresponds to an example in which the second coupler 816 of the transfer pod 802 has been interlocked and / or otherwise engaged with the first coupler 115 of the transfer carrier 100. For example, in response to the transfer controller 122 of the transfer pod 802 determining that the second coupler 816 has been coupled to the first coupler 115, the transfer controller 122 of the transfer pod 802 instructs the second mobile system 152 to pivot the mobile wheels 812 from an intermediate position to a loading position. In response to moving the mobile wheels 812 to the loading position, the transfer controller 122 of the transfer pod 802 may wirelessly transmit data indicating that the transfer pod 802 is coupled to the transfer carrier 100 and ready for transportation to a different address to the transfer controller 122 of the transfer carrier 100. In response to receiving the wireless data from the transfer pod 802, the transfer controller 122 of the transfer carrier 100 may instruct the transfer carrier 100 to move the transfer carrier 100 and the transfer pod 802 to a different address.

[0141] Figure 10A Depicts the separation of the second part of the second coupler 816 from Figures 8A to 8F the first part of the first coupler 115 of FIGS. 8A through 8F. Figure 8A Depicts the first part of the first coupler 115 that is coupled, interlocked, and / or otherwise mated with the second part of the second coupler 816 of Figure 10B Depicts the coupling of the second part of the second coupler 816 with Figures 8A to 8F the first part of the first coupler 115 that is interlocked and / or otherwise engaged with Figures 8A to 8F the first part of the first coupler 115.

[0142] In Figure 10A the illustrated example, the second coupler 816 includes a pin 818 coupled to a first example base 1002 of FIGS. 8A through Figure 8F In Figure 10A , the pin 818 is a cylindrical pin or plug that includes an example notch 1004. Alternatively, the pin 818 may have any other shape. In Figure 10A , the notch 1004 may be used to key the first coupler 115 to the second coupler 816. In Figure 10A , the first base 1002 is a rectangular base. Alternatively, the first base 1002 may have any other shape. In some examples, the first base 1002 is coupled to Figure 8A the transfer pod 802 of FIGS. 8A through 8F.

[0143] In Figure 10A the illustrated example, the first coupler 115 includes Figures 8A to 8F a lug 806 of Figure 10AIn this case, the lug 806 is coupled to the second exemplary base 1008. In some examples, the second base 1008 is coupled to Figures 1A to 1B or Figure 1C to the transfer carrier 100 of FIG. 1E. In some examples, the second base 1008 is coupled to Figures 1F to 1G the passenger cabin 102 of Figures 1H to 1I or the passenger cabin 155 of Figure 1J to the parcel compartment 104 of FIG. 1K or Figures 1L to 1M the parcel compartment 180 of Figures 8A to 8F In some examples, the second base 1008 is coupled to the transfer compartment 802 of

[0144] Figure 11A FIG. 18 depicts an example of an exemplary aerial vehicle 1100 in a pre - coupling stage. Figure 11B FIG. 19 depicts a rear view of Figure 11A the aerial vehicle 1100 in a pre - coupling stage. The aerial vehicle 1100 after coupling includes Figures 8A to 8F the transfer compartment 802 of

[0145] and an exemplary UAV 1102. When describing the exemplary coupling operations associated with the aerial vehicle 1100, the aerial vehicle 1100 is illustrated in a generalized manner for clarity. Figures 11A to 11B In Figures 11A to 11B the UAV 1102 is a dual - rotor UAV (e.g., a dual - rotor drone) including a first exemplary rotor 1104 and a second exemplary rotor 1106. For example, the drone 1102 can be an unmanned aerial vehicle, a helicopter, etc. Alternatively, the drone 1102 can have fewer or more than two

[0146] In Figures 11A to 11B the two rotors 1104, 1106 depicted in. Alternatively, the UAV 1102 can be a helicopter or any other type of rotary - wing aircraft. When describing the exemplary coupling operations associated with the UAV 1102, the UAV 1102 is illustrated in a generalized manner for clarity. Figures 11A to 11BIn [the figure], the first exemplary power system 1108 is coupled to the first rotor 1104, and the second exemplary power system 1110 is coupled to the second rotor 1106. The power systems 1108, 1110 may include one or more pistons, one or more turbines, one or more (e.g., battery-powered) electric motors, one or more (e.g., gasoline-fueled) gasoline engines, etc. and / or combinations thereof. The UAV 1102 includes a transfer controller 122 for obtaining instructions from an external computing system and executing the instructions to facilitate transportation operations (e.g., UAV transportation operations including transporting the transfer pod 802, picking up the transfer pod 802, dropping off the transfer pod 802, etc.). Figures 1A to 1M of the transfer controller 122.

[0147] Figures 11A to 11B The UAV 1102 includes an exemplary sensor system 1111. In some examples, the sensor system 1111 corresponds to Figures 1F to 1I and Figures 2A to 2B one or both of the sensor systems 154, 156 of the passenger cabin 102. In some examples, the sensor system 1111 corresponds to Figures 1J to 1M one or both of the sensor systems 176, 178 of the package cabin 104. For example, the transfer controller 122 may obtain the outputs from the LIDAR system, GPS system, computer vision system, etc. of the UAV 1102, and determine that the UAV 1102 is at a desired location or address based on the LIDAR system output, GPS system output, computer vision system output, etc.

[0148] The transfer pod 802 includes a first coupler 115 on the top surface of the transfer pod 802 for facilitating interaction with the UAV 1102 Figure 1A to Figure 1M and Figures 8A to 8F of the UAV 1102. Above, the first coupler 115 on the top surface of the transfer pod 802 was described in connection with Figures 8A to 8F and Figures 10A to 10B . For example, Figures 8A to 8F and FIGS. 10A to Figure 10B the lugs 806 may be configured to receive and / or otherwise obtain Figures 8A to 8F and Figures 10A to 10B the pins 818 of the UAV 1102.

[0149] In Figures 11A to 11B , the UAV 1102 includes a second coupler 816 for coupling to the first coupler 115 on the top surface of the transfer pod 802. In Figures 11A to 11B , the second coupler 816 is on the bottom surface 1103 of the UAV 1102. In Figures 11A to 11BIn this case, the second connector 816 of the UAV 1102 may be referred to herein as a connector (e.g., a UAV connector), a cargo connector (e.g., a UAV cargo connector), a pickup connector (e.g., a UAV pickup connector, a transfer pod pickup connector, etc.), a transport connector (e.g., a UAV transport connector), a flight connector, etc. The UAV 1102 includes four instances of the second connector 816 configured to couple with corresponding connectors in the first connector 115 of the transfer pod 802. Alternatively, the UAV 1102 may have fewer or more instances of the second connector 816. Below, in conjunction with Figures 12A to 12L Describe operations associated with the second connector 816 of the UAV 1102 and the first connector 115 of the transfer pod 802.

[0150] The UAV 1102 includes a third example mobile system 1112. The UAV 1102 includes four instances of the third mobile system 1112. Alternatively, the UAV 1102 may have fewer than or more than four instances of the third mobile system 1112. As used herein, the four instances of the third mobile system 1112 may be collectively referred to herein as the UAV mobile system.

[0151] In Figures 11A to 11B this case, the third mobile system 1112 includes an example motor 1114 and example wheels (e.g., mobile wheels) 1116. In Figures 11A to 11B this case, the motor 1114 is a traction motor. Alternatively, any other type of motor may be used. In Figures 11A to 11B this case, the mobile wheels 1116 are used to move the UAV 1102 on top of the transfer pod 802 to align the second connector 816 of the UAV 1102 with the first connector 115 of the transfer pod 802. For example, when the mobile wheels 1116 are engaged for movement, the UAV 1102 may travel across the top of the transfer pod 802 at a non-zero speed (e.g., a non-zero horizontal or lateral speed). Alternatively, fewer or more than four mobile wheels 1116 may be used. For example, the powertrain of the third mobile system 1112 may include one or more electric motors, one or more transmissions, one or more drive shafts, one or more differentials, one or more axles, final drives, etc. for manipulating and / or otherwise controlling the four mobile wheels 812. Alternatively, one or both of the first powertrain 1108 and the second powertrain 1110 may be used to control the movement of the mobile wheels 1116.

[0152] In some examples, the third mobility system 1112 implements a second device for moving the UAV 1102 or a second device for transporting the UAV 1102. The second device for moving the UAV 1102 or the second device for transporting the UAV 1102 may correspond to and / or otherwise include a powertrain, a power source, and / or mobility wheels 1116, one or more joints, an air cushion handling system, one or more tracks, one or more rollers (e.g., pallet handling rollers), etc. and / or combinations thereof.

[0153] In some examples, the power source of the third mobility system 1112 includes one or more batteries (e.g., lithium-ion batteries) that supply power to one or more electric motors of the powertrain of the third mobility system 1112 to effect movement of the UAV 1102. Alternatively, the power source of the third mobility system 1112 can be any other energy storage element or device (e.g., a capacitor bank, a chemical or liquid reservoir (e.g., a gasoline tank, a hydrogen tank, etc.).

[0154] In Figures 11A to 11B the aerial vehicle 1100 is in a pre-coupling phase. For example, the transfer pod 802 and the UAV 1102 are in a pre-latched or pre-coupled position where the transfer pod 802 is on the ground surface 1118 and the UAV 1102 is not coupled to the transfer pod 802, or in some examples, in contact with the transfer pod 802. In Figures 11C to 11D the aerial vehicle 1100 is in a post-coupling phase. For example, the transfer pod 802 and the UAV 1102 are in a latched or coupled position where the transfer pod 802 is coupled to the transfer carrier 100.

[0155] Figures 11E to 11F depicts an example coupling operation of the Figures 11A to 11D aerial vehicle 1100 in the pre-coupling phase. Figure 11E depicts Figures 11A to 11D a first portion of the transfer pod 802 and Figures 11A to 11D a side view B-B of a second portion of the UAV 1102. In Figure 11E the first coupler 115 of the transfer pod 802 is close to but not coupled to the second coupler 816 of the UAV 1102. Figure 11F depicts a rear view A-A depicted in FIG. 11A. In Figure 11F the rear view A-A is a rear view of Figure 11E a first portion and a second portion. In Figure 11F the first coupler 115 of the transfer pod 802 is close to but not coupled to the second coupler 816 of the UAV 1102.

[0156] Figures 12A to 12L depicts Figures 11A to 11FThe transfer cabin 802 and Figures 11A to 11F Example operations 1210, 1220, 1230, 1240, 1250, 1260 of the connection of the UAV 1102 with Figures 11A to 11F . Operations 1210, 1220, 1230, 1240, 1250, 1260 include a first example operation 1210, a second example operation 1220, a third example operation 1230, a fourth example operation 1240, a fifth example operation 1250, and a sixth example operation 1260.

[0157] Figure 12A Depicts a side view of the first operation 1210, and Figure 12B Depicts a rear view of the first operation 1210. The first operation 1210 corresponds to an example where the UAV 1102 is moving towards the position of the transfer cabin 802 and / or otherwise approaching the position of the transfer cabin 802. For example, the transfer controller 122 of the UAV 1102 may instruct the power systems 1108, 1110 to control the rotors 1104, 1106 to move the UAV 1102 to a position close to the top surface of the transfer cabin 802.

[0158] Figure 12C Depicts a side view of the second operation 1220, and Figure 12D Depicts a rear view of the second operation 1220. The second operation 1220 corresponds to an example where the UAV 1102 is in a position generally above the transfer cabin 802. For example, the sensor system 1111 of the UAV 1102 may determine that the UAV 1102 has traveled and / or otherwise moved to a first aerial connection position. The first aerial connection position may correspond to a position where the transfer controller 122 of the UAV 1102 determines that the UAV 1102 can start to contact the transfer cabin 802 to start the connection.

[0159] Figure 12E Depicts a side view of the third operation 1230, and Figure 12F Depicts a rear view of the third operation 1230. The third operation 1230 corresponds to an example where the UAV 1102 contacts the transfer cabin 802 before being connected to the transfer cabin 802. For example, the sensor system 1111 of the UAV 1102 may determine that the UAV 1102 has traveled and / or otherwise moved to a second aerial connection position. At the second aerial connection position, the UAV 1102 has lowered the pin 818 of the second coupler 816 of the UAV 1102 into the groove 804 of the first coupler 115 of the transfer cabin 802.

[0160] Figure 12G Depicts a side view of the fourth operation 1240, and Figure 12HDepicts a rear view of a fourth operation 1240. The fourth operation 1240 corresponds to an example in which the UAV 1102 has been coupled to the transfer pod 802 at a third in-air coupling position. The third in-air coupling position may correspond to a position where the transfer controller 122 of the UAV 1102 determines that the mobile wheels 1116 do not need to be further moved onto the transfer pod 802 and the coupling of the transfer pod 802 to the UAV 1102 is complete. For example, in response to the UAV 1102 being in the second coupling position, the transfer controller 122 of the UAV 1102 may instruct the mobile wheels 1116 to move from the second coupling position to the third coupling position by guiding the mobile wheels 1116 to move across the top of the transfer pod 802.

[0161] By horizontally moving the mobile wheels 1116 across the top of the transfer pod 802, the UAV 1102 can be lowered into the recess 804 to align the second coupler 816 of the UAV 1102 with the first coupler 115 of the transfer pod 802. For example, in response to the transfer controller 122 determining that the UAV 1102 is in the second coupling position, the transfer controller 122 may instruct the third movement system 1112 to move the mobile wheels 1116 into the recess 804 to lower the height of the UAV 1102 from a first height to a second height, where the second height is lower than the first height. In such an example, the first height may correspond to the mobile wheels 1116 being above the recess 804 and / or otherwise not in the recess 804, and the second height may correspond to the mobile wheels 1116 being in the recess 804.

[0162] During the fourth operation 1240, the second connector 816 of the UAV 1102 interlocks, mates, and / or otherwise engages with the first connector 115 of the transfer pod 802. For example, in response to the transfer controller 122 of the UAV 1102 determining that the UAV 1102 is in the second connection position, the transfer controller 122 of the UAV 1102 may instruct the third movement system 1112 of the UAV 1102 to rotate the movement wheels 1116 so that the UAV 1102 moves horizontally across the transfer pod 802 to connect to the first connector 115 of the transfer pod 802. In response to the transfer controller 122 of the UAV 1102 determining that the second connector 816 is connected to the first connector 115, the transfer controller 122 instructs the third movement system 1112 to disengage from the movement wheels 1116 to stop the movement of the UAV 1102. For example, the transfer controller 122 of the UAV 1102 may obtain a measurement indicating that the second connector 816 has been connected to the first connector 115 from a sensor (such as a pressure switch, a position sensor, etc.) of the sensor system 1111 of the UAV 1102 that monitors the second connector 816. In other examples, the transfer controller 122 of the transfer pod 802 may send wireless data (such as one or more wireless messages, one or more wireless data packets, etc.) to the transfer controller 122 of the UAV 1102. For example, the wireless data may indicate that the result of the sensor associated with the sensor systems 154, 156 of the transfer pod 802 monitoring the first connector 115 is that the first connector 115 has been connected to the second connector 816 of the UAV 1102. In such examples, the sensors may be pressure sensors, position sensors, torque sensors, etc.

[0163] Figure 12I A side view of the fifth operation 1250 is depicted, and Figure 12J A rear view of the fifth operation 1250 is depicted. The fifth operation 1250 corresponds to an example in which the UAV 1102 lifts the transfer pod 802 to prepare for transportation. For example, in response to the transfer controller 122 of the UAV 1102 determining that the second connector 816 has been connected to the first connector 115 of the transfer pod 802, the transfer controller 122 of the UAV 1102 may instruct the power systems 1108, 1110 to control the rotors 1104, 1106 to generate a lift force sufficient to pick up the transfer pod 802.

[0164] Figure 12K A side view of the sixth operation 1260 is depicted, and Figure 12LA rear view of a sixth operation 1260 is depicted. The sixth operation 1260 corresponds to an example in which the transfer pod 802 pivots the travel wheels 812 from the extended position to the stowed position. In response to moving the travel wheels 812 to the stowed position, the transfer controller 122 of the transfer pod 802 may transmit wireless data to the transfer controller 122 of the UAV 1102 indicating that the transfer pod 802 is coupled to the UAV 1102 and is ready for transport to a different address. In response to obtaining the wireless data from the transfer pod 802, the transfer controller 122 of the UAV 1102 may instruct the UAV 1102 to fly the transfer pod 802 to the different address.

[0165] Figure 13 is an example infrastructure 1300 including an example central server 1302 that controls and / or otherwise manages a plurality of autonomous vehicles including Figures 1A to 1B Transfer carrier 100, Figures 1C to 1E Transfer carrier 135, Figures 1F to 1G Passenger compartment 102, Figure 1H to Figure 1I Passenger compartment 155, Figures 1J to 1K Package compartment 104, Figures 1L to 1M Package compartment 180 and / or Figures 11A to 11F UAV 1102. Figure 13 In the example, infrastructure 1300 is a public transportation system. Figure 13 In the example of FIG. 1 , the central server 1302 is a controller that can correspond to one or more computing devices (e.g., a system controller, a transportation system controller, etc.). The infrastructure 1300 includes an example network 1304 for communicating with the transfer vehicle 100, 135, the passenger cabin 102, 155, the package cabin 104, 180, and / or the UAV 1102. Figures 1A to 1M The relay controllers 122 communicate with corresponding relay controllers in order to facilitate the coordination and control of the autonomous vehicles.

[0166] Figure 13An example network 1304 of the illustrated examples is the Internet. However, network 1304 can be implemented using any suitable wired and / or wireless network or networks, including, for example, one or more data buses, one or more local area networks (LANs), one or more wireless LANs, one or more cellular networks, one or more private networks, one or more public networks, one or more satellite networks, etc. Network 1304 can be implemented via one or more direct wireless connections, including, for example, one or more radio frequency connections, one or more vehicle-to-everything (V2X) protocol connections, one or more Bluetooth connections, one or more Wi-Fi direct connections, one or more GPS connections, etc. Network 1304 enables central processor 1302 to communicate with one or more transfer controllers 122 or any other device or vehicle associated with infrastructure 1300.

[0167] Figure 13 Infrastructure 1300 includes example dwelling 1306. Figure 13 In this case, dwelling 1306 is a home associated with one or more individuals or users, the individuals or users being associated with one or more passenger compartments 102, 155, one or more parcel compartments 104, 180, etc. and / or combinations thereof. For example, a first dwelling in dwelling 1306 can include Figures 1F to 1G passenger compartment 102 of Figures 1H to 1I passenger compartment 155 of Figures 1J to 1K parcel compartment 104 of Figures 1L to 1M or parcel compartment 180 of Figures 1F to 1G at least one. In such an example, a user associated with Figures 1A to 1B passenger compartment 102 of Figure 1E can generate a request for transfer vehicle 100 or transfer vehicle 135 of FIG. 1C to

[0168] come to the first dwelling in dwelling 1306 via a software application (e.g., a software application executed on an Internet-enabled mobile phone, tablet, etc. and / or any other computing device). The user can send the request to central server 1302 via network 1304 using the application.

[0168] In some examples, in response to receiving the request, central server 1302 identifies available transfer vehicles 100, 135 that are moving on an example roadway (e.g., a road, highway, etc.) or stored in an example vehicle facility 1310. For example, vehicle facility 1310 can be for maintaining, renting, and / or storing Figures 1A to 1B one or more of transfer vehicles 100 of Figures 1C to 1Ea location for one or more of the transfer carriers 135. In response to identifying an available transfer carrier among transfer carriers 100, 135, the central server 1302 may dispatch the available transfer carrier among transfer carriers 100, 135 to the first residence among residences 1306. The example formation 1309 described below in conjunction with Figures 16A to 16B is further depicted on the roadway 1308. In other examples, a user associated with the first residence among residences 1306 may own (e.g., personally own) one or more of the transfer carriers 100, 135 for personal use.

[0169] The infrastructure 1300 includes an example pod facility 1312. In some examples, the pod facility 1312 is for maintenance (e.g., repair, charging, and / or refueling operations), rental, and / or storage Figures 1F to 1G of one or more of the passenger pods 102 Figures 1H to 1I of one or more of the passenger pods 155 Figures 1J to 1K of one or more of the parcel pods 104 and / or Figures 1L to 1M of one or more of the parcel pods 180. For example, a user who does not own the passenger pods 102, 155, parcel pods 104, 180, etc. may generate a request and send it to the central server 1302 to rent or temporarily use one or more of the passenger pods 102, 155, one or more of the parcel pods 104, 180, etc. In such an example, the central server 1302 may identify available passenger pods among the passenger pods 102, 155 at the pod facility 1312, available parcel pods among the parcel pods 104, 180, etc., and dispatch the available passenger pod among the passenger pods 102, 155, the available parcel pod among the parcel pods 104, 180, etc. to the user's address or an address specified by the user. In other examples, a user may own (e.g., personally own) one or more of the passenger pods 102, 155, one or more of the parcel pods 104, 180, etc. for personal use.

[0170] The infrastructure 1300 includes an example UAV facility 1313. In some examples, the UAV facility 1313 is for maintenance (e.g., repair, charging, and / or refueling operations), rental, and / or storage Figures 11A to 11F of one or more of the UAVs 1102. For example, a user may generate a request and send it to the central server 1302 to rent or temporarily use one or more of the UAVs 1102 to transport Figures 1G to 1H one of the passenger pods 102, 155 Figures 1J to 1MOne of the parcel compartments 104, 180, etc. In such an example, the central server 1302 can identify the available UAV in the UAV 1102 at the UAV facility 1313 and dispatch the available UAV in the UAV 1102 to the user's address or the address specified by the user (e.g., the address of the relevant passenger compartment 102, 155, the address of the relevant parcel compartment 104, 180, etc.). In Figure 13 In it, the UAV facility 1313 includes one or more instances of pads 1316 for facilitating the flight operations (e.g., landing, takeoff, etc.) of one or more of the UAVs 1102.

[0171] The infrastructure 1300 includes an example UAV airport 1314 for facilitating transportation operations (e.g., UAV transportation operations). In some examples, the passenger compartments 102, 155, the parcel compartments 104, 180, etc. can be picked up by one or more of the UAVs 1102 at the example pads 1316 (e.g., transportation pads, UAV pads, UAV transportation pads, etc.) and transported to the requested or desired second address. For example, the pad 1316 can be the takeoff / landing pad of the UAV 1102. Alternatively, the passenger compartments 102, 155, the parcel compartments 104, 180, etc. can be picked up by one or more of the UAVs 1102 at an address different from the pad 1316. For example, the passenger compartments 102, 155, the parcel compartments 104, 180, etc. can be picked up from the corresponding transfer carriers 100, 135 at the residence 1306. In some examples, the passenger compartments 102, 155, the parcel compartments 104, 180, etc. can be dropped off by one or more of the UAVs 1102 after being transported from different addresses to the UAV airport 1314. Below, in conjunction with Figure 17 Describe the operations associated with the UAV 1102 performed at the UAV airport 1314.

[0172] The infrastructure 1300 includes an example retail environment 1318. The retail environment 1318 includes an example retail store 1320 and an example parking lot 1322. In Figure 13 In it, the retail store 1320 is an enterprise or franchise that sells products or services to the public. In Figure 13 In it, the parking lot 1322 includes a plurality of transfer compartments 102, 104, 155, 180 and pads 1316. For example, the UAV 1102 can pick up or drop off the transfer compartments 102, 104, 155, 180 at the pad 1316. Below, in conjunction with Figures 19A to 19D Describe the operations associated with the transfer compartments 102, 104, 155, 180 related to the retail environment 1318.

[0173] The infrastructure 1300 includes an example airport 1326 and an example seaport 1328. In some examples, the transfer pods 102, 104, 155, 180 can be taken to the airport 1326 or the seaport 1328 for transportation to different airports or seaports. In some examples, the transfer pods 102, 104, 155, 180 can be taken to the airport 1326 or the seaport 1328 after being transported from different airports or seaports.

[0174] The infrastructure 1300 includes an example stacking facility 1330 and an example rail facility 1332. In Figure 13 this case, the infrastructure 1300 includes a stacking facility 1330 for facilitating stacking the transfer pods 102, 104, 155, 180 on different transfer pods 102, 104, 155, 180. For example, the stacking facility 1330 can include one or more ramps 1334, and the parcel pods 104, 180 can use the ramps 1334 to move onto another parcel pod 104, 180. In such an example, the stacked parcel pods 104, 180 can travel to the rail facility 1332 or another location within the infrastructure 1300 for further operations. Below, operations associated with the rail facility 1332 are described in conjunction with Figure 21 Operations associated with the stacking facility 1330 are described below in conjunction with FIG. 22.

[0175] The infrastructure 1300 includes an example building 1336. The building 1336 is a high-density building such as an apartment building, an office building, etc. The building 1336 includes a transport pad 1316 for facilitating UAV transportation operations associated with the building 1336. The building 1336 can include storage space for a plurality of transfer pods 102, 104, 155, 180 for use by personnel or users associated with the building 1336. In some examples, the building 1336 can include one or more ramps 1334 of the stacking facility 1330 to facilitate stacking of the transfer pods 102, 104, 155, 180, thereby increasing the density of the transfer pods stored in the transfer pods 102, 104, 155, 180.

[0176] The infrastructure 1300 includes an example warehouse 1338 for facilitating storage and / or transportation of goods, packages, or other items of the infrastructure 1300. The warehouse 1338 includes a transport pad 1316 for facilitating UAV transportation operations associated with the warehouse 1338. For example, the warehouse 1338 can be used to unload or load some of the parcel pods 104, 180, UAVs 1102, etc. and / or combinations thereof for transportation within the infrastructure 1300 or to different infrastructures.

[0177] Figure 14 is Figures 1A to 1M 、 Figures 11A to 11FExample implementations of the transfer controller 122, etc. The transfer controller 122 can be used to facilitate transfers with Figures 1A to 1B transfer vehicle 100, Figures 1C to 1E transfer vehicle 135, Figures 1F to 1G passenger cabin 102, Figures 1H to 1I passenger cabin 155, Figures 1J to 1K parcel compartment 104, Figures 1L to 1M parcel compartment 180 and / or Figures 11A to 11F users associated with UAV 1102, Figure 13 central server 1302, etc. In the Figure 14 illustrated example, the transfer controller 122 includes example network interface 1410, example sensor interface 1420, example override controller 1430, example command generator 1440, and example database 1450.

[0178] In Figure 14 the illustrated example, the transfer controller 122 includes a network interface 1410 for obtaining information from and / or sending information to Figure 13 network 1304. For example, the network interface 1410 can obtain data from and / or send data to different transfer controllers 122 (e.g., transfer controllers 122 associated with transfer vehicles 100, 135, transfer controllers 122 associated with passenger cabins 102, 155, transfer controllers 122 associated with parcel compartments 104, 180, transfer controllers 122 associated with UAV 1102, etc.), central server 1302, etc. via network 1304. In other examples, the network interface 1410 can obtain data (e.g., wireless data) from different transfer controllers 122 and / or send data to different transfer controllers 122 via a direct wireless connection (e.g., radio frequency connection, using formatted wireless messages and / or otherwise based on vehicle-to-everything (V2X) protocols, Bluetooth connection, Wi-Fi direct, etc.), where the wireless data does not pass through other intermediate devices such as cellular towers, gateways, routers, satellites, etc.

[0179] In some examples, the network interface 1410 implements a virtual server (e.g., a web server) that receives information from network 1304 and / or from different transfer controllers 122. For example, the information managed by the network interface 1410 can be formatted as one or more HTTP messages. However, any other message format and / or protocol such as (e.g.) File Transfer Protocol (FTP), Simple Mail Transfer Protocol (SMTP), HTTP Secure (HTTPS) protocol, etc. can be used additionally or alternatively.

[0180] In Figure 14In the illustrated example, the transfer controller 122 includes a sensor interface 1420 for obtaining measurements from one or more sensors and / or sensor systems. For example, the sensor interface 1420 can obtain sensor data from Figures 1A to 1B the transfer vehicle 100 and / or Figures 1C to 1E the sensor systems 128, 130, 132, 134 of the transfer vehicle 135, Figures 1F to 1G the passenger compartment 102 and / or Figures 1H to 1I the sensor systems 154, 156 of the passenger compartment 155, Figures 1J to 1K the parcel compartment 104 and / or Figures 1L to 1M the sensor systems 176, 178 of the parcel compartment 180, Figures 11A to 11F the sensor system 1111 of the UAV 1102, etc.

[0181] In some examples, the sensor interface 1420 configures one or more sensors and / or sensor systems. For example, the sensor interface 1420 can update the configuration of sensors associated with Figures 1A to 1B the transfer vehicle 100 and / or Figures 1C to 1E the sensor systems 128, 130, 132, 134 of the transfer vehicle 135, Figures 1F to 1G the passenger compartment 102 and / or Figures 1H to 1I the sensor systems 154, 156 of the passenger compartment 155, Figures 1J to 1K the parcel compartment 104 and / or Figures 1L to 1M the sensor systems 176, 178 of the parcel compartment 180, the sensor system 1111 of the UAV 1102, etc. (e.g., alarm settings, sensor input range, sensor output range, calibration factor, etc.).

[0182] In Figure 14 the illustrated example, the transfer controller 122 includes an override controller 1430 for controlling the transfer vehicles 100, 135, the passenger compartments 102, 155, the parcel compartments 104, 180, the UAV 1102, etc. in response to a command (e.g., a user command) or a command from the central server 1302 (e.g., an administrator sends a command via the central server 1302). In some examples, the override controller 1430 obtains a user command for adjusting the direction and / or speed of the transfer vehicles 100, 135, the passenger compartments 102, 155, the parcel compartments 104, 180, the UAV 1102, etc. For example, the user can manually control the passenger compartments 104, 155 via a joystick, a steering wheel, one or more pedals, or other control devices. In such an example, the override controller 1430 can control the powertrain 124 shown in FIGS. 1A to Figure 1E and Figures 1F to 1M the second mobile system 152 shown inFigures 11A to 11D The third mobile system 1112, etc. In some examples, the override controller 1430 translates user commands into commands to be executed by the command generator 1440.

[0183] In Figure 14 In the illustrated examples, the transfer controller 122 includes a command generator 1440 for generating commands, directions, instructions, calls, etc. for controlling the transfer carriers 100, 135, the passenger compartment 102, 155, the parcel compartment 104, 180, the UAV 1102, etc. In some examples, the command generator 1440 generates a command to move the transfer carriers 100, 135 from a first address to a second address and sends the command to the powertrains 124 of the transfer carriers 100, 135. In some examples, the command generator 1440 generates an instruction coupled to the transfer carriers 100, 135 and sends the instruction to the second mobile system 152 of the passenger compartment 102. In some examples, the command generator 1440 generates a command to climb onto the tops of different parcel compartments 104, 180 and be coupled to the parcel compartments 104, 180 via the first coupler 115 and the second coupler 816 and sends the command to the second mobile system 152 of the parcel compartments 104, 180. In some examples, the command generator 1440 generates a command to move the UAV 1102 from a first address to a second address and sends the command to the powertrains 1108, 1110 of the UAV 1102. In some examples, the command generator 1440 generates a command to control and / or otherwise affect the operation of different transfer controllers 122 and calls the network interface 1410 to send the command to different transfer controllers 122.

[0184] In Figure 14In the illustrated example, the transit controller 122 includes a database 1450 to record data (e.g., commands, configurations, GPS addresses, requests, sensor data, etc.). The database 1450 can be implemented by volatile memory (e.g., synchronous dynamic random access memory (SDRAM), dynamic random access memory (DRAM), RAMBUS dynamic random access memory (RDRAM), etc.) and / or non-volatile memory (e.g., flash memory). Additionally or alternatively, the database 1450 can be implemented by one or more double data rate (DDR) memories such as DDR, DDR2, DDR3, DDR4, mobile DDR (mDDR), etc. Additionally or alternatively, the database 1450 can be implemented by one or more mass storage devices such as hard disk drive (HDD), optical disc (CD) drive, digital versatile disc (DVD) drive, solid state disk (SDD) drive, etc. Although the database 1450 is illustrated as a single database in the illustrated example, the database 1450 can be implemented by any number and / or type of databases. Further, the data stored in the database 1450 can be in any data format such as (e.g.) binary data, comma-separated data, tab-separated data, structured query language (SQL) structures, etc.

[0185] Although in Figure 14 the implementation of Figures 1A to 1M , Figures 11A to 11D etc. of the transit controller 122 is illustrated, Figure 14 one or more of the elements, processes, and / or devices illustrated in Figures 1A to 1M can be combined, divided, rearranged, omitted, eliminated, and / or implemented in any other way. Additionally, Figures 1A to 1M , Figures 11A to 11DIn the examples such as, the transit controller 122 can be implemented by hardware, software, firmware, and / or any combination of hardware, software, and / or firmware. Thus, for example, any one of the example network interface 1410, the example sensor interface 1420, the example override controller 1430, the example command generator 1440, the example database 1450, and / or more generally the example transit controller 122 can be implemented by one or more analog or digital circuits, logic circuits, programmable processors, programmable controllers, graphics processing units (GPUs), digital signal processors (DSPs), application specific integrated circuits (ASICs), programmable logic devices (PLDs), and / or field programmable logic devices (FPLDs). When reading any of the apparatus or system claims of this patent to cover a pure software and / or firmware implementation, at least one of the example network interface 1410, the example sensor interface 1420, the example override controller 1430, the example command generator 1440, and / or the example database 1450 is hereby expressly defined to include a non-transitory computer-readable storage device or a storage disk such as a memory, DVD, CD, Blu-ray disc, etc. (including software and / or firmware). Additionally, Figures 1A to 1M , Figure 11A The example transit controller 122 up to FIGS. 1D etc. can include one or more elements, processes, and / or devices that supplement or replace the elements, processes, and / or devices illustrated in Figure 14 and / or can include more than one of any or all of the illustrated elements, processes, and devices. As used herein, the phrase "communicate" (including its variants) encompasses direct communication and / or indirect communication through one or more intermediate components, and does not require direct physical (e.g., wired) communication and / or constant communication, but additionally includes selective communication at regular intervals, scheduled intervals, aperiodic intervals, and / or one-time events.

[0186] Figure 15 is Figure 13 An example implementation of the central server 1302. The central server 1302 can be used to facilitate transportation operations associated with the Figure 13 infrastructure 1300. The transportation operations can correspond to any activities associated with land- or air-based autonomous vehicles in combination with one or more air (e.g., aircraft operations), land (e.g., autonomous vehicle operations, platoon operations, train operations, etc.), and / or sea-based operations (e.g., ferry operations, barge operations, etc.), including activities such as two or more autonomous vehicles being coupled together, autonomous vehicles being stacked on top of each other, one autonomous vehicle transporting another autonomous vehicle (e.g., picking up, dropping off, moving, etc.).

[0187] In some examples, the central server 1302 corresponds to one or more computer servers, one or more cloud computing environments, and / or more generally one or more computing systems that can be used to facilitate transportation operations associated with: Figures 1A to 1B one or more of the transfer carriers 100 in Figures 1C to 1E one or more of the transfer carriers 135 in Figures 1F to 1G one or more of the passenger cabins 102 in Figures 1H to 1I one or more of the passenger cabins 155 in Figures 1J to 1K one or more of the parcel compartments 104 in Figures 1L to 1M one or more of the parcel compartments 180 in Figures 11A to 11F one or more of the UAVs 1102 in Figure 13 one or more of the formations 1309, etc. and / or combinations thereof. In Figure 15 the illustrated example, the central server 1302 includes an example network interface 1510, an example autonomous vehicle tracker 1520, an example traffic analyzer 1530, an example infrastructure analyzer 1540, an example event scheduler 1550, an example command generator 1560, and an example database 1570.

[0188] In Figure 15 the illustrated example, the central server 1302 includes a network interface 1510 for obtaining information from and / or sending information to Figure 13 the network 1304. For example, the network interface 1510 can obtain data from and / or send data to one or more transfer controllers 122 (e.g., transfer controllers 122 associated with transfer carriers 100, 135, passenger cabins 102, 155, parcel compartments 104, 180, UAVs 1102, etc.), formations 1309, UAVs 1102, etc. and / or combinations thereof via the network 1304.

[0189] In some examples, the network interface 1510 implements a web server for receiving information from the network 1304. For example, the information managed by the network interface 1510 can be formatted as one or more HTTP messages. However, any other message format and / or protocol such as (e.g.) FTP, SMTP, HTTPS protocols, etc. can be used additionally or alternatively.

[0190] In Figure 15 the illustrated example, the central server 1302 includes an autonomous vehicle tracker 1520 for determining the address (e.g., GPS address) of one or more autonomous vehicles, where the autonomous vehicles include, for example, Figure 13 inside the infrastructure 1300 and / or otherwise associated with Figure 13The infrastructure 1300 associated with the transfer carrier 100, 135, the transfer cabin 102, 104, 155, 180, Figure 2B , Figure 3B , Figure 4B The first land transportation vehicle 200, Figure 4D The second land vehicle 400, Figure 5B 5D , a third land vehicle 500, a fourth land vehicle 510, Figure 13 Formation 1309, Figures 11A to 11F UAV 1102, formation 1309, etc.

[0191] In some examples, autonomous vehicle tracker 1520 receives Figures 16A to 16B The transfer controller 122 of one or both of the powered vehicles 1602, 1604 obtains the formation inventory information associated with the formation 1309. In such an example, the autonomous vehicle tracker 1520 may determine that the formation 1309 includes the powered vehicles 1602, 1604, the land vehicles 800A to 800D, etc., the connection order (e.g., the second land vehicle 800B is connected between the first land vehicle 800A and the fourth land vehicle 800D), etc. In some examples, the autonomous vehicle tracker 1520 identifies the location where the transfer pod joins the relevant formation based on the formation inventory information. For example, the autonomous vehicle tracker 1520 may determine that the second land vehicle 800B can join the formation 1309 at a location between the first land vehicle 800A and the fourth land vehicle 800D.

[0192] In some examples, the autonomous vehicle tracker 1520 determines the availability or status of one or more autonomous vehicles. For example, the autonomous vehicle tracker 1520 may determine whether one or more of the transfer vehicles 100, 135, the transfer pods 102, 104, 155, 180, the land vehicles 200, 400, 500, 510, the formation 1309, the UAV 1102, etc. are (1) not performing a transport operation and therefore available for dispatch or use, or (2) performing a transport operation and therefore not available for dispatch or use. In some examples, the autonomous vehicle tracker 1520 determines the position between the transfer vehicles 100, 135 of the formation 1309 so that the incoming transfer vehicles 100, 135 can join, as described below in conjunction with Figures 16A to 16B as described.

[0193] exist Figure 15In the illustrated example, the central server 1302 includes a traffic analyzer 1530 for determining existing traffic flow associated with the infrastructure 1300 and / or predicting future traffic flow. In some examples, the traffic analyzer 1530 determines the existing traffic flow on the roadway 1308 based on the number and / or type of autonomous vehicles on the roadway 1308. Figure 13 In some examples, the traffic analyzer 1530 predicts future traffic flow based on the existing traffic flow and one or more requests to perform or execute transportation operations (e.g., from users, transfer controllers 122 in transfer pods 102, 104, 155, 180, etc.). In some examples, the traffic analyzer 1530 determines the existing traffic flow or predicts future traffic flow based on traffic information obtained from traffic infrastructure, which includes, for example, traffic cameras, traffic lights, etc. that monitor and / or otherwise relate to the roadway 1308. In some examples, the traffic analyzer 1530 determines whether an autonomous vehicle is to join a formation such as Figure 13 the formation 1309 based on traffic analysis and / or determination. In such an example, the traffic analyzer 1530 may determine whether a request to join the relevant formation has been received from a transfer pod. For example, the event scheduler 1550 may receive a request to join the formation 1309 from the second land vehicle 800B.

[0194] In Figure 15 the illustrated example, the central server 1302 includes an infrastructure analyzer 1540 for determining existing infrastructure utilization associated with the infrastructure 1300 and / or predicting future infrastructure utilization. In some examples, the infrastructure analyzer 1540 determines Figure 13 the utilization of carrier facilities 1310, pod facilities 1312, UAV airports 1314, stacking facilities 1330, etc. For example, the infrastructure analyzer 1540 may determine whether one or more pads 1316 of the UAV airport 1314 are available for use by the UAV 1102. In other examples, the infrastructure analyzer 1540 may determine whether the carrier facilities 1310 and / or pod facilities 1312 have any storage and / or maintenance openings or availability. In other examples, the infrastructure analyzer 1540 may determine whether the stacking facility 1330 has available space on the ramp 1334 for stacking operations to be performed.

[0195] In Figure 15In the illustrated example, the central server 1302 includes an event scheduler 1550 for coordinating transportation operations. In some examples, the event scheduler 1550 determines the order of transportation operations. For example, in response to a request to move the passenger compartments 102, 155 from one of the residences 1306 to the UAV airport 1314, the event scheduler 1550 may determine the order of transportation operations. In such an example, the order of transportation operations may include: a first transportation operation that identifies available transfer carriers 100, 135 and dispatches them from the carrier facility 1310 to the requested residence in the residence 1306; a second transportation operation that couples the passenger compartments 102, 155 to the dispatched transfer carriers 100, 135 to form Figure 2B , Figure 3B and Figure 4B the first land vehicle 200; a third transportation operation that joins the first land vehicle 200 to Figure 13 the formation 1309; a fourth transportation operation that detaches the first land vehicle 200 from the formation 1309 when the formation 1309 approaches the exit near the roadway 1308 of the UAV airport 1314; a fifth transportation operation that moves the first land vehicle 200 to the available pad 1316 of the UAV airport 1314, and so on. In such an example, the event scheduler 1550 may generate and / or maintain a transportation operation queue (including the order of transportation operations) or update an existing transportation operation queue associated with the entire infrastructure 1300 to schedule and / or otherwise include the order of the above transportation operations.

[0196] In some examples, the event scheduler 1550 generates and / or determines formation travel path information. In some examples, the event scheduler 1550 may generate formation travel path information, including GPS data, turning directions, one or more stop points connecting multiple addresses to be traversed, etc. In such an example, the event scheduler 1550 may send the formation travel path information to Figure 13 one or more transfer compartments, autonomous vehicles, etc. of the formation 1309 to execute and / or otherwise implement. In other examples, the event scheduler 1550 may store the formation travel path information in the database 1570 for other purposes of the central server 1302. For example, the traffic analyzer 1530 may determine the existing traffic flow and / or predict the future traffic flow based on the formation travel path information stored in the database 1570.

[0197] In Figure 15 the illustrated example, the central server 1302 includes a command generator 1560 for generating to facilitate with Figure 13Commands for transportation operations associated with the assets of infrastructure 1300 and send the commands to autonomous vehicles communicatively coupled to network 1304 of FIG. 13. In some examples, command generator 1560 sends commands via network 1304 to one or more of transfer vehicles 100, 135, one or more of transfer pods 102, 104, 155, 180, one or more of land vehicles 200, 400, 500, 510, etc. For example, command generator 1560 may send commands to available transfer vehicles 100, 135 at vehicle facility 1310 to call the available transfer vehicles 100, 135 to move to different addresses to perform transportation operations.

[0198] In some examples, command generator 1560 controls formation 1309 traveling on road lane 1308. For example, command generator 1560 may generate and send commands that call formation 1309 to travel to different areas of infrastructure 1300 near and / or otherwise along road lane 1308 to formation 1309. In some examples, command generator 1560 performs air traffic control functions by coordinating and / or otherwise controlling the movement of UAVs 1102 so as not to conflict with the movement of different UAVs 1102.

[0199] In Figure 15 the illustrated example, central server 1302 includes database 1570 for recording data (e.g., commands, event schedules, GPS addresses, requests, infrastructure utilization, traffic information, etc.). Database 1570 may be implemented by volatile memory (e.g., SDRAM, DRAM, RDRAM, etc.) and / or non-volatile memory (e.g., flash memory). Additionally or alternatively, database 1570 may be implemented by one or more DDR memories such as DDR, DDR2, DDR3, DDR4, mDDR, etc. Additionally or alternatively, database 1570 may be implemented by one or more mass storage devices such as HDD, CD drive, DVD drive, SDD drive, etc. Although database 1570 is illustrated as a single database in the illustrated example, database 1570 may be implemented by any number and / or type of databases. Further, the data stored in database 1570 may be in any data format such as (e.g.) binary data, comma-separated data, tab-separated data, SQL structures, etc.

[0200] Although in Figure 15 an example manner of implementing Figure 13 central server 1302 is illustrated, Figure 15One or more of the elements, processes, and / or apparatus illustrated in [example] can be combined, divided, rearranged, omitted, eliminated, and / or implemented in any other way. Additionally, example network interface 1510, example autonomous vehicle tracker 1520, example traffic analyzer 1530, example infrastructure analyzer 1540, example event scheduler 1550, example command generator 1560, example database 1570, and / or more generally Figure 13 The example central server 1302 of [example] can be implemented by hardware, software, firmware, and / or any combination of hardware, software, and / or firmware. Thus, for example, the example network interface 1510, example autonomous vehicle tracker 1520, example traffic analyzer 1530, example infrastructure analyzer 1540, example event scheduler 1550, example command generator 1560, example database 1570, and / or more generally the example central server 1302 can be implemented by one or more analog or digital circuits, logic circuits, programmable processors, programmable controllers, GPUs, DSPs, ASICs, PLDs, and / or FPLDs. When reading any of the apparatus or system claims of this patent to cover a pure software and / or firmware implementation, at least one of the example network interface 1510, example autonomous vehicle tracker 1520, example traffic analyzer 1530, example infrastructure analyzer 1540, example event scheduler 1550, example command generator 1560, and / or example database 1570 is hereby expressly defined to include a non-transitory computer-readable storage device or a storage disk such as a memory, DVD, CD, Blu-ray disc, etc. (including software and / or firmware). Additionally, Figure 13 The example central server of [example] can include Figure 15 One or more elements, processes, and / or apparatus that supplement or replace the elements, processes, and / or apparatus illustrated in [example], and / or can include more than one of any one or all of the illustrated elements, processes, and apparatus.

[0201] Figure 16A depicts Figure 13 on the roadway 1308 of [example] Figure 13 The formation 1309 of [example]. The formation 1309 includes a plurality of autonomous vehicles coupled together using magnetic couplers to facilitate the operation of a high-traffic-density transportation path such as the roadway 1308. The autonomous vehicles are between a first example powertrain vehicle 1602 and a second example powertrain vehicle 1604. Alternatively, the formation 1309 may not include one or both of the powertrain vehicles 1602, 1604. For example, the formation 1309 may include only a plurality of autonomous vehicles, where one or more of the plurality of autonomous vehicles drive the formation 1309 (e.g., jointly drive the formation) using the respective powertrains of one or more of the plurality of autonomous vehicles.

[0202] exist Figure 16A In the illustrated example, the powertrain vehicles 1602, 1604 include Figures 1A to 1B The autonomous vehicles 1602 and 1604 may include a first transfer vehicle 100E and a second transfer vehicle 100F. Alternatively, one or both of the powered vehicles 1602 and 1604 may include a first transfer vehicle 100E and a second transfer vehicle 100F. Figures 1C to 1E The transfer vehicle 135 of the power system has a curved outer surface to reduce drag and improve the power efficiency of the formation 1309.

[0203] exist Figure 16A In the embodiment, the powertrain vehicles 1602, 1604 include a control system for controlling the operation of the powertrain vehicles 1602, 1604. Figures 1A to 1M For example, the relay controller 122 of the powertrain vehicle 1602, 1604 can be connected via Figure 13 Network 1304 and Figure 13 In such an example, the relay controllers 122 of the powered vehicles 1602, 1604 may send wireless data such as fleet inventory information (e.g., a list, inventory, or associated information of the autonomous vehicles in the fleet 1309) and / or fleet travel path information (e.g., GPS data, turn-by-turn directions, one or more stop points connecting multiple addresses to which the fleet 1309 will travel, etc.), and / or receive wireless data (e.g., commands, data requests, etc.) from the central server 1302.

[0204] exist Figure 16AIn this case, one or both of the powertrain vehicles 1602, 1604 may include a powertrain having one or more electric motors, one or more transmissions, one or more drive shafts, one or more differentials, one or more axles, a final drive, multiple wheels, etc. to manipulate and / or otherwise control the powertrain vehicles 1602, 1604 so as to facilitate the movement of the powertrain vehicles 1602, 1604. In some examples, one or both of the powertrain vehicles 1602, 1604 may include a power source that can provide fuel for the powertrain to burn and / or otherwise be used to enable the powertrain vehicles 1602, 1604 to have the ability to move. The power source includes one or more batteries (e.g., lithium-ion batteries), one or more chemical-based power sources (e.g., gasoline, hydrogen, etc.). In some examples, the power source of the powertrain vehicles 1602, 1604 may supply power to the switch unit 120 of the transfer carriers 100, 135 connected to the corresponding one of the powertrain vehicles 1602, 1604 to change Figures 1A to 1E the polarity of the electromagnetic coils of one or both of the magnetic couplers 116, 118.

[0205] In some examples, the power source of at least one of the first powertrain vehicle 1602 or the second powertrain vehicle 1604 charges the power source 126 of one or more of the transfer carriers 100, 135 included in the formation 1309. For example, the power source of the first powertrain vehicle 1602 may charge the power source 126 of the transfer carriers 100, 135 of the first land vehicle 800A, the power source associated with the transfer cabin 802 of the first land vehicle 800A, etc. In such an example, the power source of the first powertrain vehicle 1602 may charge the power source associated with the first land vehicle 800A via a daisy-chain electrical connection established through the magnetic couplers 116, 118 of the transfer carriers 100, 135 of the formation 1309. For example, the power source of the first powertrain vehicle 1602 may charge the power source associated with the first land vehicle 800A via the second magnetic coupler 118 of the transfer carrier 100E and the intermediate magnetic couplers 116, 118 between the transfer carrier 100E of the first powertrain vehicle 1602 and the transfer carrier 100A of the first land vehicle 800A. In such an example, the central server 1302 and / or the transfer controller 122 of the first powertrain vehicle 1602 may instruct the first powertrain vehicle 1602 to charge the power source associated with the first land vehicle 800A.

[0206] In Figure 16A the illustrated example of, the formation 1309 includes being associated with Figures 8A to 8DThe land vehicles 800A, 800B, 800C, and 800D corresponding to the land vehicle 800. The land vehicles 800A, 800B, 800C, and 800D include a first land vehicle 800A, a second land vehicle 800B, a third land vehicle 800C, and a fourth land vehicle 800D, where each land vehicle includes a corresponding transfer cabin 802A, 802B, 802C, 802D, 802E corresponding to the transfer cabin 802 of Figures 8A to 8D and corresponding transfer carriers 100A, 100B, 100C, 100D corresponding to the transfer carrier 100 of Figures 1A to 1B . Alternatively, the land vehicles 800A to 800D may include Figures 1C to 1E the transfer carrier 135 of Figure 16A . In Figure 22 , the third land vehicle 800C has a transfer cabin 802E stacked on top of the transfer cabin 802C of the third land vehicle 800C. The stacked transfer cabins in the transfer cabins 802C and 802E form an example stacked vehicle (e.g., a stacked land vehicle) 1606 described below in connection with

[0207] . In Figure 16A the illustrated example, the first land vehicle 800A is coupled (e.g., magnetically coupled) to the second land vehicle 800B. For example, the second magnetic coupler 118 of the first transfer carrier 100A may be coupled to the first magnetic coupler 116 of the second transfer carrier 100B.

[0208] Figure 16B depicts the second land vehicle 800B interacting with the formation 1309 of Figure 16A . In some examples, Figure 16B depicts the second land vehicle 800B joining the formation 1309. For example, the transfer controller 122 of the second land vehicle 800B (e.g., the transfer controller 122 of the transfer carrier 100B, the transfer controller 122 of the transfer cabin 802B, etc. and / or combinations thereof) may generate a request to move from a first address in the infrastructure 1300 of Figure 13 to a second address different from the first address in the infrastructure 1300, and send it to Figure 13Central server 1302. In response to the request, central server 1302 may instruct the second land vehicle 800B to join formation 1309. In some examples, central server 1302 identifies the position between powertrain vehicles 1602, 1604 for the second land vehicle 800B to join and / or otherwise occupy. In some examples, the transit controller 122 of one or both of powertrain vehicles 1602, 1604 determines the position.

[0209] In Figure 16B when the determined position is between the first transit vehicle 800A and the fourth land vehicle 800D, central server 1302 and / or the transit controller 122 of powertrain vehicles 1602, 1604 may instruct the first land vehicle 800A and the fourth land vehicle 800D to separate from each other. For example, central server 1302 may send a first command to the transit controller 122 of the first transit vehicle 100A and a second command to the transit controller 122 of the fourth transit vehicle 100D. In response to receiving the first command, the transit controller 122 of the first transit vehicle 100A may call the corresponding switch unit 120 to close the second magnetic coupler 118 of the first transit vehicle 100A. In response to receiving the second command, the transit controller 122 of the fourth transit vehicle 100D may call the corresponding switch unit 120 to close the first magnetic coupler 116 of the fourth transit vehicle 100D. In some examples, central server 1302 commands the fourth land vehicle 800D and all autonomous vehicles behind the fourth land vehicle 800D to adjust their speed from a first speed to a second speed, where the second speed is slower than the first speed. Advantageously, central server 1302 may synchronize the speed adjustment such that the fourth land vehicle 800D and all autonomous vehicles behind the fourth land vehicle 800D decelerate to the second speed substantially simultaneously.

[0210] In response to the separation of the first land vehicle 800A from the fourth land vehicle 800D, the second land vehicle 800B can be guided to join the opening formed by the separation in the platoon. For example, the central server 1302 can send a third command to the relay controller 122 of the second land vehicle 800B to join the opening in the formation. In such an example, the second land vehicle 800B can join the formation 1309 at a first speed, a second speed, or a different non-zero speed. In response to the second land vehicle 800B moving between the first land vehicle 800A and the fourth land vehicle 800D, the second land vehicle 800B can be coupled to the first land vehicle 800A and the fourth land vehicle 800D. For example, the central server 1302 can (1) send a fourth command to the first relay carrier 100A to enable the second magnetic coupler 118 of the first relay carrier 100A and (2) send a fifth command to the second relay carrier 100B to enable the first magnetic coupler 116 of the second relay carrier 100B to facilitate (3) the coupling of the first magnetic coupler 116 of the second relay carrier 100B with (4) the second magnetic coupler 118 of the first relay carrier 100A.

[0211] In response to the first land vehicle 800A being coupled to the second land vehicle 800B, the central server 1302 can send a command to the fourth land vehicle 800D and all autonomous vehicles behind the fourth land vehicle 800D to adjust from a second speed to a third speed that is faster than the second speed to keep up with the second land vehicle 800B. The fourth land vehicle 800D and all autonomous vehicles behind the fourth land vehicle 800D can be adjusted from the third speed to a first speed based on sensor measurements of one or more sensor systems (e.g., Figures 1F to 1I sensor systems 154, 156, FIGS. 1J to Figure 1M sensor systems 176, 178, etc.). For example, one or more sensor systems can indicate to the fourth land vehicle 800D that the second land vehicle 800B is in a proximity position for coupling, and the speed of the fourth land vehicle 800D will be reduced to avoid substantial contact or collision with the second land vehicle 800D.

[0212] In response to the fourth land vehicle 800D moving to a coupling position near the second land vehicle 800B, the central server 1302 may generate (1) a sixth command for enabling the second magnetic coupler 118 of the second transfer carrier 100B and (2) a seventh command for enabling the first magnetic coupler 116 of the fourth transfer carrier 100D to effect (3) the coupling of the first magnetic coupler 116 of the fourth transfer carrier 100D with (4) the second magnetic coupler 118 of the second transfer carrier 100B. A process corresponding to the second land vehicle 800B separating from the vehicle fleet 1309 is implemented substantially contrary to the process described above for the second land vehicle 800B joining the formation 1309.

[0213] In some examples, Figure 16B the second land vehicle 800B leaving the formation 1309 is depicted. For example, the transfer controller 122 of the second land vehicle 800B may generate a request to move from a first address in the infrastructure 1300 to an address different from the first address in the infrastructure 1300 and send it to the central server 1302 via Figure 13 the network 1304 of. In response to the request, the central server 1302 may instruct the second land vehicle 800B to leave the formation 1309 in response to the second land vehicle 800B and / or more generally the formation 1309, so as to move to a third address near the second address (e.g., an exit of the roadway 1308 proximate to and / or otherwise near the second address). Figure 13

[0214] To effect the second land vehicle 800B leaving the formation 1309, the central server 1302 may (1) send a first command to the transfer controller 122B of the second transfer carrier 100B to close the second magnetic coupler 118 of the second transfer carrier 100B, (2) send a second command to the transfer controller 122B of the fourth transfer carrier 100D to close the first magnetic coupler 116 of the fourth transfer carrier 100D, and (3) send a third command to the fourth transfer carrier 100D and all autonomous vehicles behind the fourth transfer carrier 100D to adjust from a first speed to a second speed slower than the first speed via the network 1304. Accordingly, the fourth transfer carrier 100D may disengage from the transfer carrier 100B, and the fourth transfer carrier 100D and all autonomous vehicles behind the fourth transfer carrier 100D may slow down to form a separation from the second transfer carrier 100B.

[0215] ​In response to creating a sufficient gap (e.g., 1 meter, 2 meters, 5 meters, etc.) (e.g., in response to the LIDAR system of one or more of the sensor systems 128, 130, 132, 134 of the second transfer vehicle 100B detecting the sufficient gap), the central server 1302 may send, via the network 1304(4), a fourth command to the transfer controller 122 of the first transfer vehicle 100A to close the second magnetic coupler 118 of the first transfer vehicle 100A, (5) a fifth command to the transfer controller 122 of the second transfer vehicle 100B to close the first magnetic coupler 116 of the second transfer vehicle 100B, and (6) a sixth command to the transfer controller 122 of the second transfer vehicle 100B to adjust from a first speed to a second speed or a third speed slower than the first speed. Accordingly, the second transfer vehicle 100B may detach from the first transfer vehicle 100A and may slow down to create a separation from the first transfer vehicle 100A. In response to creating a sufficient gap (e.g., in response to the LIDAR system of one or more of the sensor systems 128, 130, 132, 134 of the second transfer vehicle 100B detecting the sufficient gap), the central server 1302 may send a seventh command to the transfer controller 122 of the second transfer vehicle 100B to move to a second address.

[0216] Figure 16C Depicts a top view of a first example implementation of the first land vehicle 800A to Figures 16A to 16B the second land vehicle 800B that is coupled to Figure 16A FIGS. 16B. In Figure 16C this, the transfer vehicles 100A, 100B of the land vehicles 800A, 800B have a first example magnetic coupling system 1608 and a second example magnetic coupling system 1610. In Figure 16C this, the first example magnetic coupling system 1608 and the second example magnetic coupling system 1610 include Figures 1A to 1E a first example implementation of the magnetic couplers 116, 118. For example, the first implementation corresponds to magnetic couplers 116, 118 having a generally flat circular outer surface.

[0217] In Figure 16C this, the transfer vehicles 100A, 100B have a first magnetic coupling system 1608 that is coupled, attached, and / or otherwise affixed to the front surface 106 of the transfer vehicles 100A, 100B. The transfer vehicles 100A, 100B have a second magnetic coupling system 1610 that is coupled, attached, and / or otherwise affixed to the rear surface 108 of the transfer vehicles 100A, 100B. In Figure 16CThe second magnetic coupling system 1610 of the first transfer carrier 100A is depicted in an enlarged view 1612 as being coupled (e.g., magnetically coupled) to the first magnetic coupling system 1608 of the second transfer carrier 100B.

[0218] In Figure 16C the illustrated example, the first magnetic coupling system 1608 includes an exemplary base 1614 coupled to the front surface 106 of a respective one of the transfer carriers 100A, 100B. The first magnetic coupling system 1608 includes an exemplary elongated member (e.g., an arm, an elongated mechanical support, a lever, etc.) 1616 that is pivotally coupled to the base 1614 via an exemplary joint (e.g., a pivotable joint) 1618. For example, the joint 1618 can be a ball-and-socket joint, a hinge joint, etc. In some examples, the base 1614 is coupled to the front surface 106 using one or more springs, air cushions, shock absorbers, etc. and / or combinations thereof. The elongated member 1616 can pivot about the joint 1618 in response to a change in the direction of the second magnetic coupling system 1610. In Figure 16C it, the elongated member 1616 is pivotally coupled to a first magnetic coupler 116 of a respective one of the transfer carriers 100A, 100B via a ball seat including a ball 1620 and a pin 1622. The pin 1622 fixes and / or otherwise attaches the ball 1620 to the elongated member 1616. Alternatively, the ball 1620 can have any other shape. In Figure 16C it, the ball 1620 is coupled to the first magnetic coupler 116.

[0219] In Figure 16C the illustrated example, the second magnetic coupling system 1610 includes an exemplary base 1624 coupled to the rear surface 108 of a respective one of the transfer carriers 100A, 100B. In Figure 16C it, the base 1624 is pivotally coupled to the ball 1620 via a pin 1622. The ball 1620 of the second magnetic coupling system 1610 is coupled to a second magnetic coupler 118 of a respective one of the transfer carriers 100A, 100B. Advantageously, the first magnetic coupling system 1608 and the second magnetic coupling system 1610 facilitate a change in direction through one of the transfer carriers 100A, 100B. For example, in response to a change in the direction of the first transfer carrier 100A, the second transfer carrier 100B can remain magnetically coupled to the first transfer carrier 100A and adjust its direction accordingly.

[0220] Figure 16D Depicted is a top view of a second exemplary implementation of Figures 16A to 16B the first land vehicle 800A to Figure 16A the second land vehicle 800B coupled to FIG. 16B. In Figure 16DIn this case, the transfer carriers 100A and 100B of the land vehicles 800A and 800B have a third exemplary magnetic coupling system 1626A and a fourth exemplary magnetic coupling system 1626B. In Figure 16D this case, the third magnetic coupling system 1626A and the fourth magnetic coupling system 1626B include Figures 1A to 1E a second exemplary implementation of the magnetic couplers 116 and 118. For example, the second implementation corresponds to magnetic couplers 116 and 118 having a hemispherical concave outer surface that protrudes away from a respective one of the transfer carriers 100A to 100B. Advantageously, the concave outer surfaces of the magnetic couplers 116 and 118 eliminate the need for the movable components (e.g., the elongated members 1616, the joints 1618, etc.) described above in connection with Figure 16C this description.

[0221] In Figure 16D this case, the transfer carriers 100A and 100B have a third magnetic coupling system 1626A that is coupled, attached, and / or otherwise affixed to the front surface 106 of the transfer carriers 100A to 100B. The transfer carriers 100A and 100B have a fourth magnetic coupling system 1626B that is coupled, attached, and / or otherwise affixed to the rear surface 108 of the transfer carriers 100A to 100B. In Figure 16D an enlarged view 1628, the fourth magnetic coupling system 1626B of the first transfer carrier 100A is shown coupled (e.g., magnetically coupled) to the third magnetic coupling system 1626A of the second transfer carrier 100B.

[0222] In Figure 16D the illustrated example, the third magnetic coupling system 1626A and the fourth magnetic coupling system 1626B include respective exemplary bases 1630A to 1630B that are coupled to a respective one of the magnetic couplers 116 and 118. In Figure 16D this case, the base 1630A of the third magnetic coupling system 1626A is coupled to the front surface 106 of a respective one of the transfer carriers 100A to 100B. In Figure 16D this case, the base 1630B of the fourth magnetic coupling system 1626B is coupled to the rear surface 108 of a respective one of the transfer carriers 100A to 100B. Advantageously, the third magnetic coupling system 1626A and the fourth magnetic coupling system 1626B facilitate a change in direction through one of the transfer carriers 100A and 100B. For example, in response to a change in the direction of the first transfer carrier 100A, the second transfer carrier 100B can remain magnetically coupled to the first transfer carrier 100A and adjust its direction accordingly.

[0223] Figure 17 depicts Figure 13The UAV airport 1314. The UAV airport 1314 includes exemplary pads 1316A, 1316B, 1316C on the exemplary UAV platform 1702, and the pads include a first exemplary pad 1316A, a second exemplary pad 1316B, and a third exemplary pad 1316C. In Figure 17 it, the first pad 1316A has a first transfer cabin 802A corresponding to the transfer cabin 802 Figures 8A to 8F of. For example, the first transfer cabin 802A can be brought to the UAV platform 1702 by a first transfer carrier 100A corresponding to the transfer carrier 100 Figures 1A to 1B of. Alternatively, the first transfer cabin 802A can be brought to the UAV platform 1702 by the transfer carrier 135 Figure 1C from Fig. 1E to Fig. 1E. In response to leaving the first transfer cabin 802A at the first pad 1316A, the first UAV 1102A corresponding to the UAV 1102 Figures 11A to 11F of can travel to the UAV airport 1314 and pick up the first transfer cabin 802A via the UAV connection operation described above in conjunction with Figures 12A to 12L . Alternatively, the UAV 1102 can travel to any other address (e.g., current address, location, etc.) of the first transfer cabin 802A and pick up the first transfer cabin 802A via the UAV connection operation described above in conjunction with Figures 12A to 12L . For example, the UAV 1102 can pick up the first transfer cabin 802A at the high-density building 1336, the stacking facility 1330, etc. In such an example, the UAV 1102 can pick up the first transfer cabin 802A from the corresponding one of the transfer carriers 100 Figures 1A to 1B of or Figures 1C to 1E the transfer carrier 135 of.

[0224] In Figure 17 the illustrated example, the second pad 1316B has a second transfer cabin 802B corresponding to the transfer cabin 802 Figures 8A to 8F of, and the second transfer cabin 802B is connected to the second UAV 1102B corresponding to the UAV 1102 Figures 11A to 11F of. For example, the second UAV 1102B can be connected to the second transfer cabin 802B via the UAV connection operation described above in conjunction with Figures 12A to 12L .

[0225] In Figure 17 the illustrated example, the third pad 1316C is empty and thus available for use. For example, the central server 1302 can instruct the third UAV 1102C corresponding to the UAV 1102 Figures 11A to 11F of to drop the Figures 8A to 8FThe third transfer cabin 802C corresponding to the transfer cabin 802. In such an example, the third UAV 1102C can be lowered and detached from the third transfer cabin 802C via the UAV connection operation described above in conjunction with Figures 12A to 12L Upon transporting the third transfer cabin 802C to the third pad 1316C, the central server 1302 can instruct the second transfer cabin 100B corresponding to the transfer cabin 100 of Figures 1A to 1B to travel to the platform 1702 to pick up the third transfer cabin 802C. Alternatively, the central server 1302 can instruct the transfer vehicle 135 of Figures 1C to 1E to pick up the third transfer cabin 802C.

[0226] Figure 18A Illustrates an example UAV 1800 interacting with the third land vehicle 500 of Figure 5B Alternatively, the UAV 1800 can interact with the fourth land vehicle 510 of Figure 5D The UAV 1800 of Figure 18A is an unmanned aerial vehicle (e.g., transport unmanned aerial vehicle, transport UAV, etc.) for facilitating the transportation of goods, packages, and / or other items from land vehicles 500, 510 to different addresses such as one of the residences 1306 like Figure 13 , a high-density building 1336, a warehouse 1338, etc. and / or any other address within the infrastructure 1300 of Figure 13 . The UAV 1800 includes a transfer controller 122 of Figure 13 . For example, the central server 1302 can generate directions, commands, instructions, or any other calls to obtain the example package 1808 from the land vehicles 500, 510 and transport the package 180 to a different address, and send it to the UAV 1800. Advantageously, while the UAV 1800 is transporting the package 1808, the UAV 1800 enables the land vehicles 500, 510 to move from a first address (e.g., a first address in a residential area, an industrial park, etc.) to a second address (e.g., a second address in a residential area, an industrial park, etc.). Thus, the UAV 1800 can return (e.g., iteratively return) to the current address of the land vehicles 500, 510 to obtain relevant additional packages from the land vehicles 500, 510 for transportation while the land vehicles 500, 510 remain in motion.

[0227] Figure 18A The illustrated example of Figure 18A ​Among them, operations 1802, 1804, and 1806 include a first example operation 1802, a second example operation 1804, and a third example operation 1806. For example, the parcel compartment 104 of the third land vehicle 500 may be a transit compartment for transporting a plurality of items, parcels, and / or other items (including the package 1808 transported to Figure 13 the residence 1306, the high-density building 1336, etc.).

[0228] In Figure 18A the illustrated example, during the first operation 1802, the central server 1302 instructs the UAV 1800 (e.g., the transit controller 122 of the UAV 1800) to move to the first address of the third land vehicle 500 via Figure 13 the network 1304. In Figure 18A the second operation 1804, the central server 1302 instructs the UAV 1800 to move to the second address corresponding to the UAV 1800 and hover above the hatch 174 of the parcel compartment 104 and / or otherwise close to the hatch 174. During the second operation 1804, the lifting device of the parcel compartment 104 may lift the package 1808 upward and / or lift it through the hatch 174. In response to the package 1808 being lifted through the hatch 174, the UAV 1800 may take possession of the package 1808 via the example manipulator 1810.

[0229] In some examples, the manipulator 1810 may correspond to one or more arms, claws, grippers, etc. coupled to one or more actuators of the UAV 1102. For example, the UAV 1800 includes a manipulator 1810 for grasping the package 1808 during the second operation 1804. In some examples, the manipulator 1810 implements a device for manipulating the package 1808. For example, the device for manipulating the package 1808 may include one or more arms, claws, grippers, etc. coupled to one or more actuators of the UAV 1800 and / or otherwise implemented by them.

[0230] In response to the UAV 1800 obtaining the package 1808 from the parcel compartment 104, the central server 1302 may instruct the UAV 1800 to transport the package 1808 to the third address (e.g., Figure 13a residence 1306, a high-density building 1336, etc.). In response to transporting the package 1808 to a third address, the central server 1302 may instruct the UAV 1800 to return to a fourth address corresponding to the current address of the package compartment 104. For example, during the time the UAV 1800 transports the package 1808, the package compartment 104 moves from a second address to a fourth address. Thus, the UAV 1800 may iteratively obtain items from the package compartment 104, transport the items to an address different from the package compartment 104, and return to the current address of the package compartment 104, where the package compartment 104 may (constantly) maintain movement from one address to another.

[0231] Figure 18B depicts example package operations 1820, 1822, 1824 associated with Figure 5B a third land vehicle 500. Alternatively, the package operations 1820, 1822, 1824 may be associated with Figure 5D a fourth land vehicle 510. The third land vehicle 500 includes a package compartment 104 for facilitating the transportation of goods, packages, and / or other items from the package compartment 104 to different addresses such as one of a residence 1306, a high-density building 1336, a warehouse 1338, etc. and / or Figure 13 any other address within the infrastructure 1300. Figures 1J to 1K Alternatively, Figure 18B the package operations 1820, 1822, 1824 may be performed by Figures 1L to 1M a package compartment 180.

[0232] The package compartment 104 includes Figure 13 a transfer controller 122. For example, the central server 1302 may generate and send a direction, command, instruction, or any other call to transfer one or more packages to an address within the infrastructure 1300 to the package compartment 104. In some examples, the transfer controller 122 of the package compartment 104 may instruct the transfer controller 122 of one of the coupled transfer carriers 100, 135 to move the package compartment 104 to a relevant address within the infrastructure 1300. Alternatively, the central server 1302 may generate a command to move the package compartment 104 to a relevant address for a transportation operation and send it to one of the coupled transfer carriers 100, 135.

[0233] Advantageously, while the package compartment 104 can travel in and out of a distribution center (e.g., a warehouse 1338), the UAV 104 enables Figure 2A , Figure 3A and Figure 4AThe first land vehicle 200 can move from a first address (e.g., a first address in a residential area, an industrial park, etc.) to a second address (e.g., a second address in a residential area, an industrial park, etc.). Accordingly, different parcel compartments 104 can return (e.g., iteratively return) to the current address of the first land vehicle 200 to transport associated additional packages while the first land vehicle 200 remains in motion, to improve transportation efficiency.

[0234] Figure 18B The illustrated examples depict operations 1820, 1822, 1824 that facilitate the transportation of goods, packages, and / or other items. In Figure 18B this case, operations 1820, 1822, 1824 include a fourth example operation 1820, a fifth example operation 1822, and a sixth example operation 1824. In Figure 18B the illustrated example of this case, during the fourth operation 1820, the central server 1302 can, via Figure 13 the network 1304 of this case, instruct the third land vehicle 500 (e.g., the transfer controller 122 of the parcel compartment 104 and / or the transfer controller 122 of the corresponding transfer carrier 100) to move to the first address of the first land vehicle 200. For example, the central server 1302 can instruct the third land vehicle 500 to join and / or otherwise connect to the first land vehicle 200 that has not been connected to one of the third land vehicles 500. In such an example, the parcel compartment 104 can correspond to a full parcel compartment (e.g., the parcel compartment 104 has a complete inventory and / or is filled with items, packages, and / or other items), and the first land vehicle 200 assists the fully loaded parcel compartment to transport the loaded items.

[0235] In Figure 18B the illustrated example of this case, during the fifth operation 1822, the central server 1302 can instruct the third land vehicle 500 to connect to the first land vehicle 200. The central server 1302 can generate a transportation route, a transportation path, etc. for the first land vehicle 200 and the third land vehicle 500 to use to transport the items included in the parcel compartment 104. After the first land vehicle 200 is connected to the third land vehicle 500, the central server 1302 can instruct the first land vehicle 200 and the third land vehicle 500 to travel along the transportation route to facilitate the transportation of the loaded items.

[0236] In Figure 18BIn the illustrated example, during the sixth operation 1824, the parcel compartment 104 has been emptied corresponding to one or more of the previously stored items having been transported to their respective transport addresses. In response to the parcel compartment 104 being emptied or substantially emptied (e.g., because one or more items could not be successfully transported, so one or more items remain in the parcel compartment 104), the central server 1302 may instruct the third land vehicle 500 to detach from the first vehicle 200 and return to the distribution center or travel to a different address. In some examples, the third land vehicle 500 may return to the distribution center to be reloaded and then be instructed to join the first land vehicle 200 or a different one of the first land vehicles 200 to transport additional items, packages, and / or other items to the relevant addresses.

[0237] Figures 19A to 19D Depicts an example housing 1902, which may facilitate the transport of an example item 1904 via the third land vehicle 500 of FIG. 5B. Alternatively, the housing 1902 may facilitate the transport of the item 1904 via the fourth land vehicle 510 of FIG. 5D. The item 1904 may correspond to a package, parcel, etc. In Figure 19A this example, the housing 1902 is a platform or base structure to which the parcel compartment 180 of the third land vehicle 500 may be coupled. The housing 1902 has a front surface 1906, a rear surface 1908 opposite the front surface 1906, a first side surface 1910, a second side surface 1912 opposite the first side surface 1910, a top surface 1914, and a bottom surface 1916 opposite the top surface 1914. The housing 1902 includes an example hatch 1918 on the top surface 1914. The housing 1902 has an internal cavity within the surfaces 1906, 1908, 1910, 1912, 1914, 1916 for storing the item 1904. The hatch 1918 is a slidable and movable surface to expose the internal cavity of the housing 1902 to ambient air to facilitate interaction with another entity such as the third land vehicle 500.

[0238] Figure 19A The housing 1902 of this example includes an example magnetic coupler 1920 on the rear surface 1908. The magnetic coupler 1920 is the same as the first magnetic coupler 116 and the second magnetic coupler 118 of the transfer carriers 100, 135 of Figures 1A to 1E this example. Alternatively, the magnetic coupler 1920 may be different. Alternatively, the rear surface 1908 may have more than one magnetic coupler 1920. Alternatively, the magnetic coupler 1920 may be at a different address and / or location on the rear surface 1908 depicted in Figure 19A this example.

[0239] Figure 19B depicts a first example operation 1930 associated with the housing 1902 and Figure 5B a third land vehicle 500. In Figure 19B this example, the third land vehicle 500 includes an item 1904 within a Figures 1J to 1K package compartment 104. During the first operation 1930, the third land vehicle 500 moves to the address of the housing 1902 to couple with the housing 1902.

[0240] Figure 19C depicts a second example operation 1940 associated with the Figure 19A housing 1902 and Figure 5B a third land vehicle 500. During the second operation 1940, a first magnetic coupler 116 of the transfer carrier 100 is coupled to a magnetic coupler 1920 of the housing 1902. In response to this coupling, a first hatch 1918 is invoked to open. During the second operation 1940, the package compartment 104 detaches from the transfer carrier 100 and moves over the top of the housing 1902. For example, a second movement system 152 of the package compartment 104 can move the package compartment 104 onto the top surface 1914 of the housing 1902 as described above in connection with Figures 9A to 9J . During the second operation 1940, the package compartment 104 releases the item 1904 into the housing 1902 via the first hatch 1918. For example, the package compartment 104 can include a second hatch 1922 that is substantially the same as the Figures 1J to 1M hatch 174 to allow the item 1904 to move from the package compartment 104 into the housing 1902.

[0241] Figure 19D depicts a third example operation associated with the Figure 19A housing 1902 and Figure 5BA third example operation 1950 associated with a third land vehicle 500. During the third operation 1950, an item 1904 is placed in a housing 1902. During the third operation 1950, the third land vehicle 500 can move to the address of the housing 1902 and be coupled to the housing 1902. In response to this coupling, the parcel compartment 104 can be detached from the transfer carrier 100 and move from the top surface of the transfer carrier 100 to the top surface 1914 of the housing 1902. In response to the parcel compartment 104 moving to a position above the hatch 1918 of the housing 1902, an example elevator 1924 of the housing 1902 can lift the item 1904 from the interior of the housing 1902 through a second hatch 1922 to the interior of the parcel compartment 104. The elevator 1924 can correspond to a lift platform, a lift surface, a crane, etc. In some examples, the elevator 1924 implements a device for lifting, and the device for lifting corresponds to a lift platform, a lift surface, a crane, etc. In response to moving the item 1904 to the interior of the parcel compartment 104, the parcel compartment 104 can close the second hatch 1922. During the third operation 1950, the parcel compartment 104 can move back to the transfer carrier 100 and transport the item 1904 to a different address.

[0242] Figure 20 An example transportation hub 2000 for facilitating transportation operations of autonomous vehicles is depicted. The transportation hub 2000 includes an example transportation station 2010 and Figure 13 and / or Figure 17 a UAV airport 1314. Additionally or alternatively, the transportation hub 2000 can include Figure 13 a carrier facility 1310, a compartment facility 1312, an airport 1326, a seaport 1328, a stacking facility 1330, a rail facility 1332, and / or a warehouse 1338. For example, one or more of the autonomous vehicles in the formation 1309 can leave Figure 13 the formation 1309 when approaching and / or passing by the transportation hub 2000. In such an example, the autonomous vehicle can travel to the UAV airport 1314 for transportation by one of the UAVs 1102. For example, the UAV 1102 can transport one of the autonomous vehicles to an address different from the transportation hub 2000. In other examples, the UAV 1102 can pick up and land one of the autonomous vehicles on top of a different autonomous vehicle associated with an example autonomous vehicle chain 2020. Alternatively, the autonomous vehicle can travel to the transportation station 2010 for transportation by the autonomous vehicle chain 2020. In other examples, after being transported to the UAV airport 1314, the transportation station 2010, etc., the autonomous vehicle can leave the transportation hub 2000 and enter the roadway 1308 to join the formation 1309.

[0243] Figure 21 Depicted Figure 20 The transport station in 2010. Figure 21 Autonomous vehicles can help transport operations. For example, Figure 20 The autonomous vehicle chain 2020 moves on the example station road 2110. The autonomous vehicle chain 2020 includes stacked vehicles corresponding to the stacked vehicles 1606 of FIG. 16. In such an example, the stacked vehicles can be separated from the autonomous vehicle chain 2020 and moved to a corresponding one of the corresponding station roads 2110. For example, the central server 1302 via the network 1304 can instruct some of the stacked vehicles to detach or connect with the autonomous vehicle chain 2020. In such an example, the stacked vehicles Figures 8A to 8F The transfer pod 802 of the transfer carrier 100 can be detached from the corresponding transfer carrier 100 and moved to the top of the platform (e.g., a transport platform, a loading / unloading platform, an elevated platform, etc.) 2120. The transfer pod 802 can travel across the platform 2120 and move on the top of another transfer carrier 100 and connect to the transfer carrier 100. The transfer carrier 100 can transport the transfer pod 802 to a different address (e.g., can travel to Figure 13 The road 1308 joins Figure 13 Formation 1309, etc.).

[0244] Figure 22 Describes including Figures 8A to 8F For example, the central server 1302 may instruct the transfer cabin 802A in the first example and the transfer cabin 802B in the second example to stack the transfer cabins 802A and 802B in the example corresponding to the transfer cabin 802 in the first example. Figures 1A to 1B The first transfer carrier 100A corresponding to the transfer carrier 100 of the embodiment stacks the first transfer cabin 802A connected to the first transfer carrier 100A on top of the second transfer cabin 802B. Figures 1C to 1E The transfer carrier 135. Figure 22 In the process, the second transfer cabin 802B is connected to Figures 1A to 1B The second transfer carrier 100B corresponding to the transfer carrier 100. Figure 22 The second transfer cabin 802B is close to Figure 13 The first transfer carrier 100A may travel along the ramp 1334. In response to traveling to the edge 2220 of the top surface 2230 of the ramp 1334, the first transfer carrier 100A stops at the edge 2220.

[0245] exist Figure 22In the illustrated example, at edge 2220, the first transfer pod 802A detaches from the first transfer vehicle 100A. In response to this detachment, the first transfer pod 802 moves from the top of the first transfer vehicle 100A to the top of the second transfer pod 802B. In response to moving to the top of the second transfer pod 802B, the first transfer pod 802A couples to the second transfer pod 802B. For example, as described above in connection with Figures 8A to 8F and Figures 9A to 9J , the second coupler 816 of the first transfer pod 802A can couple to the first coupler 115 of the second transfer pod 802B to form the stacked vehicle 1606 of FIG. 16. In response to this coupling, the second transfer vehicle 100B can transport the first transfer pod 802A and the second transfer pod 802B to different addresses.

[0246] In Figures 23 to 27 is shown a flowchart representing example hardware logic, machine-readable instructions, hardware-implemented state machines, and / or any combination thereof for implementing Figure 14 the transfer controller 122 and / or Figure 15 the central server 1302. The machine-readable instructions can be one or more executable programs or portions of executable programs for execution by a computer processor such as the processor 2812 shown in the example processor platform 2800 discussed below in connection with Figure 28 and / or the processor 2912 shown in the example processor platform 2900 discussed below in connection with Figure 29 . The program can be implemented by software stored on a non-transitory computer-readable storage medium such as a CD-ROM, floppy disk, hard drive, DVD, Blu-ray disc, or memory associated with Figure 28 the processor 2812 and / or Figure 29 the processor 2912, but the entire program and / or portions thereof can alternatively be executed by a device other than Figure 28 the processor 2812 and / or Figure 29 the processor 2912 and / or implemented with firmware or special purpose software. Additionally, although the example program is described with reference to the flowchart illustrated in Figures 23 to 27 , many other methods for implementing the example transfer controller 122 and / or the example central server 1302 can alternatively be used. For example, the order of execution of the blocks can be changed, and / or some of the described blocks can be changed, eliminated, or combined. Additionally or alternatively, any or all of the blocks can be implemented by one or more hardware circuits (e.g., discrete and / or integrated analog and / or digital circuits, FPGA, ASIC, comparator, operational amplifier (op-amp), logic circuits, etc.) structured to perform the corresponding operations without executing software or firmware.

[0247] The machine-readable instructions described herein may be stored in one or more of a compressed format, an encrypted format, a segmented format, a compiled format, an executable format, a packaged format, etc. The machine-readable instructions described herein may be stored as data that can be used to create, manufacture, and / or generate machine-executable instructions (e.g., portions of instructions, code, representations of code, etc.). For example, the machine-readable instructions may be segmented and stored on one or more storage devices and / or computing devices (e.g., servers). The machine-readable instructions may need to be installed, modified, adapted, updated, combined, supplemented, configured, decrypted, decompressed, unpacked, distributed, reassigned, compiled, etc., in order for them to be directly readable, interpretable, and / or executable by a computing device and / or other machine. For example, the machine-readable instructions may be stored in multiple parts that are independently compressed, encrypted, and stored on separate computing devices, where the parts form an executable instruction set for implementing a program such as the programs described herein when they are decrypted, decompressed, and combined.

[0248] In another example, the machine-readable instructions may be stored in a state where they are computer-readable, but libraries (e.g., dynamic link libraries (DLLs)), software development kits (SDKs), application programming interfaces (APIs), etc., need to be added in order to execute the instructions on a particular computing device or other device. In another example, the machine-readable instructions may need to be configured (e.g., stored settings, data inputs, recorded network addresses, etc.) before the machine-readable instructions and / or corresponding programs can be executed in whole or in part. Accordingly, the disclosed machine-readable instructions and / or corresponding programs are intended to cover such machine-readable instructions and / or programs regardless of their particular format or state when they are stored or at rest or in transit.

[0249] The machine-readable instructions described herein may be represented in any past, present, or future instruction language, scripting language, programming language, etc. For example, the machine-readable instructions may be represented using any one of the following languages: C, C++, Java, C#, Perl, Python, JavaScript, Hypertext Markup Language (HTML), Structured Query Language (SQL), Swift, etc.

[0250] As described above, it can be implemented using executable instructions (e.g., computer and / or machine-readable instructions) stored on a non-transitory computer and / or machine-readable medium such as a hard disk drive, flash memory, read-only memory, CD, DVD, cache, random access memory, and / or any other storage device or storage disk that stores information for any duration (e.g., an extended period of time, permanently, a short instance, a temporary cache, and / or a cache of information). Figures 23 to 27Example process. As used herein, the term "non-transitory computer-readable medium" is expressly defined to include any type of computer-readable device and / or storage disk, and does not include propagated signals and does not include transmission media.

[0251] "Comprising" and "including" (and all forms and tenses thereof) are used herein as open-ended terms. Thus, whenever a claim employs any form of "comprising" or "including" (e.g., comprises, variations thereof, has, etc.) as a preamble or within any kind of claim recitation, it is to be understood that additional elements, items, etc. may exist without departing from the scope of the corresponding claim or recitation. As used herein, when the phrase "at least" is used as a transitional word in, for example, the preamble portion of a claim, it has the same open-endedness as the term "comprising" and its variations. When used in the form such as A, B, and / or C, the term "and / or" means any combination or subset of A, B, C, such as (1) only A, (2) only B, (3) only C, (4) A and B, (5) A and C, (6) B and C, and (7) A and B and C. As used herein, in the context of describing a structure, component, article, object, and / or thing, the phrase "at least one of A and B" is intended to mean an implementation that includes any one of the following: (1) at least one A, (2) at least one B, and (3) at least one A and at least one B. Similarly, as used herein, in the context of describing a structure, component, article, object, and / or thing, the phrase "at least one of A or B" is intended to mean an implementation that includes any one of the following: (1) at least one A, (2) at least one B, and (3) at least one A and at least one B. As used herein, in the context of describing the execution or performance of a process, instruction, action, activity, and / or step, the phrase "at least one of A and B" is intended to mean an implementation that includes any one of the following: (1) at least one A, (2) at least one B, and (3) at least one A and at least one B. Similarly, as used herein, in the context of describing the execution or performance of a process, instruction, action, activity, and / or step, the phrase "at least one of A or B" is intended to mean an implementation that includes any one of the following: (1) at least one A, (2) at least one B, and (3) at least one A and at least one B.

[0252] As used herein, singular references (e.g., "a," "an," "first," "second," etc.) do not exclude a plurality. As used herein, the term "a" or "an" entity refers to one or more of that entity. The terms "a," "one or more," and "at least one" may be used interchangeably herein. Further, although listed separately, a plurality of devices, elements, or method acts may be implemented by, for example, a single unit or processor. Additionally, although individual features may be included in different examples or claims, these features may be combinable, and inclusion in different examples or claims does not imply that a combination of features is infeasible and / or disadvantageous.

[0253] Figure 23 represents machine-readable instructions 2300 that may be executed to implement Figure 14 the transfer controller 122 and / or Figure 15 the central processor 1302 to transport autonomous transfer pods such as the passenger compartment 102 of FIG. 1 to Figure 1F the passenger compartment 102, Figures 1H to 1I the passenger compartment 155, Figures 1J to 1K the parcel compartment 104 and / or Figures 1L to 1M the parcel compartment 180, as shown in the flowchart of example machine-readable instructions 2300. Figure 23 The machine-readable instructions 2300 begin at block 2302, in which the central server 1302 obtains a request to move a mobile autonomous transfer pod. For example, the network interface 1510 ( Figure 15 ) may obtain the request via the network 1304 of FIG. 13 from a user (e.g., an application executing on a smartphone associated with the user, the transfer controller 122 associated with the user, etc.). In such an example, the request may correspond to moving the passenger compartments 102, 155, parcel compartments 104, 180, etc. from Figure 13 one of the residences 1306 to Figure 13 the UAV airport 1314.

[0254] In block 2304, the central server 1302 directs a transfer vehicle to the address of the transfer pod. For example, the autonomous vehicle tracker 1520 ( Figure 15 ) may identify available transfer vehicles 100, 135 at the vehicle facility 1310. In such an example, the command generator 1560 ( Figure 15 ) may generate a command to direct the available transfer vehicles 100, 135 to the requested residence in the residence 1306 and send the command to the transfer controller 122 of the available transfer vehicles 100, 135.

[0255] In block 2306, the central server 1302 invokes the transfer vehicle to connect to the transfer pod. For example, the command generator 1560 may generate, as described above in connection with Figures 9A to 9JOne or more commands that are described as being coupled together and sending the commands to Figures 8A to 8F the transfer controller 122 of the transfer module 802 and / or the transfer controller 122 of the transfer carriers 100, 135.

[0256] In block 2308, the central server 1302 instructs the transfer carrier to move the transfer module. For example, in response to the passenger cabins 102, 155 being coupled to the transfer carriers 100, 135, the command generator 1560 may send commands to the transfer controller 122 of the transfer carriers 100, 135 to move Figure 2B , Figure 3B , Figure 4B the first land vehicle 200, Figure 4D the second land vehicle 400, etc. to different addresses such as the UAV 1314.

[0257] In block 2310, the central server 1302 determines whether to facilitate interaction with another transfer carrier. For example, the traffic analyzer 1530 ( Figure 15 ) may determine Figure 13 that the traffic on the roadway 1308 is congested and may determine to move the first land vehicle 200, the second land vehicle 400, etc. to the UAV airport 1314 via Figure 13 the formation 1309. In such an example, the event scheduler 1550 ( Figure 15 ) may schedule one or more events in a queue to facilitate the first land vehicle 200, the second land vehicle 400, etc. joining the formation 1309. In response to scheduling one or more events, the command generator 1560 may send commands corresponding to the one or more events to facilitate the first land vehicle 200, the second land vehicle 400, etc. joining the formation 1309, as described above in connection with Figures 16A to 16B . In other examples, the central server 1302 may determine that the roadway 1308 is not congested and the first land vehicle 200, the second land vehicle 400, etc. may travel directly to the UAV airport 1314 without joining the formation 1309. In such an example, after the first land vehicle 200, the second land vehicle 400, etc. reach the UAV airport 1314, the central server 1302 may facilitate the connection of the UAV 1102 with the passenger cabin 102 of the first land vehicle 200, the passenger cabin 155 of the second land vehicle 400, etc.

[0258] If, in block 2310, the central server 1302 determines not to facilitate an interaction with another transfer vehicle, then in block 2312, the central server 1302 determines whether to facilitate an interaction with a UAV. For example, the traffic analyzer 1530 may determine that it is more efficient to move the passenger compartments 102, 155 from the requested residence in the residence 1306 to another address in the infrastructure 1300 via flight (e.g., one or more flight operations). In such an example, the event scheduler 1550 may schedule one or more events, including coordinating with Figures 11A to 11F the UAV 1102 to pick up the passenger compartments 102, 155 at the UAV airport 1314. Accordingly, the command generator 1560 may send a command to travel to the UAV airport 1314 for the flight transportation of the passenger compartments 102, 155 to the transfer controller 122 of the transfer vehicle 100, 135 carrying the passenger compartments 102, 155.

[0259] If, in block 2312, the central server 1302 determines not to facilitate an interaction with another transfer vehicle, then the machine-readable instructions 2300 of FIG. 23 end. For example, the command generator 1560 that sends commands to move the first land vehicle 200, the second land vehicle 400, etc. to different addresses to the transfer controller 122 of the transfer vehicle 100, 135, as described above in connection with block 2308, may end the actions to be performed by the central server 1302.

[0260] If, in block 2312, the central server 1302 determines to facilitate an interaction with a UAV, then in block 2314, the central server 1302 facilitates an interaction with the UAV. For example, the command generator 1560 may instruct the UAV 1102 to connect to the passenger compartments 102, 155 at the UAV airport 1314. Below, a Figure 24 sample process that may be used to implement block 2312 is described. In response to facilitating the interaction with the UAV in block 2314, Figure 23 the machine-readable instructions 2300 end.

[0261] If, in block 2310, the central server 1302 determines to facilitate an interaction with another transfer vehicle, then control proceeds to block 2316 to instruct the transfer vehicle to connect to another transfer vehicle. For example, the command generator 1560 may instruct Figure 13 the autonomous vehicles of the formation 1309 to facilitate the first land vehicle 200, the second land vehicle 400, etc. to join the formation 1309. Below, a Figure 25 sample process that may be used to implement block 2316 is described.

[0262] In response to indicating in block 2316 that a transfer vehicle is coupled to another transfer vehicle, in block 2318, central server 1302 directs the coupled transfer vehicle to move the transfer pod. For example, command generator 1560 may send commands to move first land vehicle 200, second land vehicle 400, etc. to formation 1309. In other examples, command generator 1560 may send one or more commands to move first land vehicle 200A after it is coupled to second land vehicle 200B, third land vehicle 200C, and fourth land vehicle 200D to Figures 6A to 6B transfer vehicles 100A - 100D.

[0263] In block 2320, central server 1302 determines whether the transfer pod is a parcel pod. For example, network interface 1510 may determine that the request is associated with Figures 1J to 1K parcel pod 104 or Figures 1L to 1M parcel pod 180. If in block 2320 central server 1302 determines that the transfer pod is not a parcel pod, then Figure 23 machine - readable instructions 2300 end. If in block 2320 central server 1302 determines that the transfer pod is a parcel pod, then in block 2322, central server 1302 processes the parcel pod. For example, event scheduler 1550 may schedule one or more events that facilitate the stacking of two parcel pods 104, 180 as described above in connection with FIG. 22. Below, an example process that may be used to implement block 2322 is described. In response to processing the parcel pod in block 2322, Figure 26 machine - readable instructions 2300 end. Figure 23 is a flowchart of example machine - readable instructions 2400 that may be executed to implement

[0264] Figure 24 transfer controller 122 and / or Figure 14 central processor 1302 of Figure 15 to transport transfer pods such as passenger cabin 102 of FIGS. 1 - Figures 11A to 11F UAV 1102 using Figure 1F passenger cabin 102, Figures 1H to 1I passenger cabin 155, Figures 1J to 1K parcel pod 104 or Figures 1L to 1M parcel pod 180. Figure 24 Machine - readable instructions 2400 of Figure 23 may be used to implement block 2314 of machine - readable instructions 2300. Figure 24 Machine - readable instructions 2400 of Figure 15 begin at block 2402, in which central server 1302 obtains a request to move a transfer pod using a UAV. For example, network interface 1510 ( Figure 13The network 1304 obtains a request from a user (e.g., an application executing on a smartphone associated with the user, a transit controller 122 associated with the user, etc.). In such an example, the request may correspond to moving a passenger cabin 102, 155, a parcel cabin 104, 180, etc. from Figure 13 one of the residences 1306 to Figure 13 the UAV airport 1314. The infrastructure analyzer 1540 ( Figure 15 ) may determine that the third pad 1316C is available for transportation and call the event scheduler 1550 to schedule an air transportation operation at the third pad 1316C.

[0265] In block 2404, the central server 1302 instructs the transit cabin to detach from the transit vehicle. For example, the command generator 1560 ( Figure 15 ) may send a command to detach the transit vehicle 100, 135 coupled to the passenger cabins 102, 155 to the transit controller 122 of the passenger cabins 102, 155. In such an example, the passenger cabins 102, 155 may call the mobile system 152 of the passenger cabins 102, 155 to detach the second coupler 816 of the passenger cabins 102, 155 from the first coupler 115 of the transit vehicle 100, 135.

[0266] In block 2406, the central server 1302 guides the UAV to the address of the transit cabin. For example, the command generator 1560 may send a command to move from a first address in the infrastructure 1300 to a second address corresponding to the third pad 1316C of the UAV airport 1314 to Figures 11A to 11F the UAV 1102.

[0267] In block 2408, the central server 1302 instructs the UAV to couple to the transit cabin. For example, the command generator 1560 may send one or more commands to call the coupling to the UAV 1102 and the respective transit controllers 122 of the passenger cabins 102, 155. In such an example, the command generator 1560 may guide the transit controller 122 of the UAV 1102 to couple the second coupler 816 of the UAV 1102 to the first coupler 115 of the passenger cabins 102, 155, as described above in connection with Figures 11A to 11F and Figures 12A to 12L .

[0268] In block 2410, the central server 1302 guides the UAV to move the transit cabin. For example, the traffic analyzer 1530 ( Figure 15 ) may be based on information from the UAV, associated with Figure 13Based on the existing or pending flight traffic of the aircraft and the like associated with the airport 1326, the flight path is determined. The command generator 1560 can send commands for transporting the passenger cabin 102, 155 to the relay controller 122 of the UAV 1102 based on the determined flight path. In response to the UAV moving the relay cabin in block 2410, Figure 24 The machine-readable instruction 2400 returns Figure 23 The machine-readable instruction 2300, end.

[0269] Figure 25 Is a flowchart showing an example machine-readable instruction 2500, and the machine-readable instruction 2500 can be executed to implement Figure 14 The relay controller 122 and / or Figure 15 The central server 1302 instructs the relay vehicle to connect to another relay vehicle. Figure 25 The machine-readable instruction 2500 can be used to implement Figure 23 Block 2316 of the machine-readable instruction 2300.

[0270] Figure 25 The machine-readable instruction 2500 starts at block 2502, where the central server 1302 identifies the formation to join at a non-zero speed. For example, the network interface 1510 ( Figure 15 ) can obtain via Figure 13 The network 1304 from the user (e.g., an application executed on a smartphone associated with the user, a relay controller 122 associated with the user, etc.) a request to move Figures 16A to 16B The second land vehicle 800B from the first address to the second address. In such an example, the request can correspond to moving the passenger cabin 102, 155, the package cabin 104, 180, etc. from Figure 13 One of the residences 1306 to Figure 13 The high-density building 1336. The traffic analyzer 1530 ( Figure 15 ) can determine Figure 13 The traffic on the roadway 1308 is congested, and in order to increase the transportation throughput and reduce the transportation time, the traffic analyzer 1530 can identify the Figure 13 Formation 1309 that the second land vehicle 800B is to join.

[0271] In block 2504, the central server 1302 determines the positions between the relay vehicles of the formation. For example, the autonomous vehicle tracker 1520 ( Figure 15 ) can determine that the second land vehicle 800B can join the formation 1309 at a position between the first land vehicle 800A and the fourth land vehicle 800D, as depicted in Figures 16A to 16B .

[0272] In block 2506, the central server 1302 directs the first transfer carrier to separate from the second transfer carrier. For example, the command generator 1560 may instruct the first transfer carrier 100A of the first land vehicle 800A to separate from the fourth transfer carrier 100D of the fourth land vehicle 800D, as described above in conjunction with Figures 16A to 16B Described in .

[0273] In block 2508, the central server 1302 directs the incoming relay carrier to connect to the first relay carrier. For example, the command generator 1560 may send a first command connected to the first relay carrier 100A to the relay controller 122 of the second relay carrier 100B, as described above in conjunction with Figures 16A to 16B Described in .

[0274] In block 2510, the central server 1302 directs the incoming relay carrier to connect to the second relay carrier. For example, the command generator 1560 may send a first command connected to the fourth relay carrier 100D to the relay controller 122 of the second relay carrier 100B, as described above in conjunction with Figures 16A to 16B Described in .

[0275] In response to directing the incoming transfer carrier to couple to a second transfer carrier, Figure 25 Machine readable instructions 2500 return Figure 23 Box 2318 of the machine-readable instructions 2300 to direct the connected transfer carrier to move the transfer cabin.

[0276] Figure 26 is a flow chart representing example machine readable instructions 2600 that may be executed to implement Figure 14 The relay controller 122 and / or Figure 15 The central server 1302 instructs the first package pod to be stacked on top of the second package pod. Figure 26 The machine readable instructions 2600 may be used to implement Figure 23 Box 2322 of machine readable instructions 2300.

[0277] Figure 26 The machine-readable instructions 2600 of 2600 begin at block 2602, in which the central server 1302 obtains a request to leave a package pod at a platform. For example, the network interface 1510 ( Figure 15 ) can be accessed through Figure 13 The network 1304 obtains the information from the user (e.g., an application executed on a smartphone associated with the user, a transit controller 122 associated with the user, etc.) Figures 1J to 1K Package compartment 104 or Figures 1L to 1M The request may indicate that the package pod 104, 180 is to be transported from a first address to a second address.Figure 17 platform 1702, Figure 13 and / or Figure 22 ramp 1334, Figures 19A to 19D housing 1902, etc. at a second address corresponding thereto.

[0278] In block 2604, the central server 1302 instructs the transfer carrier to connect to the platform. For example, the command generator 1560 may send a command to connect the first magnetic coupler 116 of the transfer carriers 100, 135 to the magnetic coupler 1920 of the housing 1902 to Figures 1A to 1B transfer carrier 100 or Figures 1C to 1E transfer carrier 135 to the transfer controller 122.

[0279] In block 2606, the central server 1302 instructs the transfer carrier to disconnect from the parcel compartment. For example, in response to connection to the housing 1902, the command generator 1560 may send a command to engage the movement system 152 to disconnect the transfer carriers 100, 135 to the transfer controller 122 of the parcel compartments 104, 180.

[0280] In block 2608, the central server 1302 instructs the parcel compartment to move onto the platform. For example, the command generator 1560 may send a command to move from the top of the transfer carriers 100, 135 to the top of the housing 1902 to the transfer controller 122 of the parcel compartments 104, 180.

[0281] In block 2610, the central server 1302 determines whether to facilitate interaction with another parcel compartment. For example, if the parcel compartments 104, 180 disconnect from the transfer carriers 100, 135 on Figure 13 and / or Figure 22 the top of ramp 1334, then the command generator 1560 may send a command to move onto the top of another parcel compartment 104, 180 to the transfer controller 122 of the parcel compartments 104, 180, as described above in connection with Figure 22 described.

[0282] If in block 2610, the central server 1302 determines not to facilitate interaction with another parcel compartment, then Figure 26 the machine-readable instructions 2600 return to Figure 23 the machine-readable instructions 2300, ending. For example, other operations such as Figures 19B to 19D operations 1930, 1940, 1950 may be performed by the transfer controller 122 of the parcel compartments 104, 180.

[0283] If, in block 2610, the central server 1302 determines to facilitate an interaction with another parcel pod, then in block 2612, the central server 1302 instructs the parcel pod to move on top of another parcel pod. For example, Figure 22 the first transfer pod 802A of Figure 22 may travel from the top of the first transfer vehicle 100A to the top surface of the second transfer pod 802B, as described above in connection with

[0284] In block 2614, the central server 1302 instructs the transfer vehicle stacking the parcel pods to move. For example, in response to the stacking of transfer pods 802A, 802B as depicted in Figure 22 , the command generator 1560 may send a command to move transfer pods 802A, 802B to a different address to the second transfer vehicle 100B of the stacking vehicle 1606. In response to instructing the transfer vehicle stacking the parcel pods to move in block 2614, Figure 26 the machine-readable instructions 2600 of Figure 23 return to the machine-readable instructions 2300 of

[0285] Figure 27 is a flowchart of example machine-readable instructions 2700 that may be executed to implement the operation of example formation 1309 in which the central server 1302 of Figure 15 facilitates Figure 13 , Figure 16A and / or Figure 16B . The machine-readable instructions begin at block 2702, in which the central server 1302 obtains formation inventory information for the formation. For example, the autonomous vehicle tracker 1520 ( Figure 15 ) may obtain formation inventory information associated with one or more formations including formation 1309 from the transfer controller 122 of one or both of the powertrain vehicles 1602, 1604 of Figures 16A to 16B . In such an example, the autonomous vehicle tracker 1520 may determine that formation 1309 includes powertrain vehicles 1602, 1604, land vehicles 800A - 800D, etc., a connection order (e.g., the second land vehicle 800B is connected between the first land vehicle 800A and the fourth land vehicle 800D), etc.

[0286] In block 2704, the central server 1302 obtains formation travel path information for the formation. For example, the event scheduler 1550 ( Figure 15 ) may obtain formation travel path information associated with one or more formations including formation 1309, where the formation travel path information may include information from Figures 16A to 16BGPS data, turning direction, one or more stop points connecting multiple addresses to be traversed, etc., of one or both of the powertrain vehicles 1602, 1604. In other examples, the event scheduler 1550 can obtain formation travel path information from the database 1570( Figure 15 )

[0287] In block 2706, the central server 1302 controls the formation to facilitate the execution of the formation travel path. For example, the command generator 1560( Figure 15 ) can control Figures 16A to 16B One or more of the powertrain vehicles 1602, 1604, transfer vehicles 800A to 800D, etc., and / or more commonly the formation 1309 to travel from the first address to multiple different addresses in the infrastructure 1300 along the formation travel path.

[0288] In block 2708, the central server 1302 determines whether a request for a transfer pod to join a relevant formation has been received. For example, the traffic analyzer 150( Figure 15 ) can obtain a request from the second land vehicle 800B to join the formation 1309.

[0289] If in block 2708, the central server 1302 determines that no request has been received, control returns to block 2702 to obtain the formation inventory information of the formation (e.g., updated formation inventory information). If in block 2708, the central server 1302 determines a request for a transfer pod to join a relevant formation, then in block 2710, the central server 1302 identifies the location where the transfer pod joins the relevant formation. For example, the autonomous vehicle tracker 1520 can determine that the second land vehicle 800B can join the formation 1309 at a position between the first land vehicle 800A and the fourth land vehicle 800D.

[0290] In block 2712, the central server 1302 instructs the formation to separate to form an opening for the transfer pod to join. For example, the command generator 1560 can instruct the first land vehicle 800A to break away from the fourth land vehicle 800D. In some examples, the command generator 1560 can direct the first land vehicle 800A and all land vehicles in front of or ahead of the first land vehicle 800A to increase their speed from a first speed to a second speed greater than the first speed. Additionally or alternatively, the central server 1560 can direct the fourth land vehicle 800D and all land vehicles behind the fourth land vehicle 800D to decrease their speed from the first speed to a third speed less than the first speed.

[0291] In block 2714, the central server 1302 commands the joined transfer pod to move to the opening. For example, the command generator 1560 may call the second land vehicle 800B to move into the opening formed by the separation of the first land vehicle 800A and the fourth land vehicle 800D.

[0292] In block 2716, the central server 1302 instructs the formation to connect to the transfer pod by closing the opening. For example, the command generator 1560 may instruct the first land vehicle 800A to connect to the second land vehicle 800B by reducing the speed from a second speed to a first speed. Additionally or alternatively, after connection, the fourth land vehicle 800D may connect to the second land vehicle 800B by increasing the speed from a third speed to a first speed. Thus, the formation 1309 may continue along the travel path with the second land vehicle 800B added to the formation. In response to instructing the formation to connect to the transfer pod by closing the opening in block 2716, Figure 27 the machine-readable instructions 2700 end.

[0293] Figure 28 is structured to execute Figures 23 to 27 the instructions to implement Figure 14 a block diagram of an example processor platform 2800 of the transfer controller 122 that is structured to execute TM the instructions to implement. The processor platform 2800 may be, for example, an electronic control unit (ECU), a server, a personal computer, a workstation, a self-learning machine (e.g., a neural network), a mobile device (e.g., a cell phone, a smart phone, a tablet such as an iPad

[0294] such tablet), a personal digital assistant (PDA), or any other type of computing device. Figure 14 the example sensor interface 1420, the example override controller 1430, and the example command generator 1440. In Figure 28 the example, the example sensor interface 1420 is represented as "sensor interface", the example override controller 1430 is represented as "override controller", and the example command generator 1440 is represented as "command generator".

[0295] The processor 2812 of the illustrated example includes a local memory 2813 (e.g., cache). The processor 2812 of the illustrated example communicates with a main memory including a volatile memory 2814 and a non-volatile memory 2816 via a bus 2818. The volatile memory 2814 can be implemented by synchronous dynamic random access memory (SDRAM), dynamic random access memory (DRAM), dynamic random access memory and / or any other type of random access storage device. The non-volatile memory 2816 can be implemented by flash memory and / or any other desired type of storage device. Access to the main memories 2814, 2816 is controlled by a memory controller.

[0296] The processor platform 2800 of the illustrated example further includes an interface circuit 2820. The interface circuit 2820 can be implemented by any type of interface standard such as an Ethernet interface, a universal serial bus (USB), interface, a near field communication (NFC) interface, and / or a PCI Express interface. In this example, the interface circuit 2820 implements the Figure 28 example network interface 1410 that is represented as a "network interface" in Figure 14 .

[0297] In the illustrated example, one or more input devices 2822 are connected to the interface circuit 2820. The input devices 2822 permit a user to input data and / or commands into the processor 2812. The input devices 2822 can be implemented by, for example, audio sensors, microphones, cameras (still or video), keyboards, buttons, mice, touchscreens, touchpads, trackballs, pointing devices, and / or voice recognition systems.

[0298] One or more output devices 2824 are also connected to the interface circuit 2820 of the illustrated example. The output devices 2824 can be implemented by, for example, display devices (e.g., light emitting diodes (LEDs), organic light emitting diodes (OLEDs), liquid crystal displays (LCDs), cathode ray tube (CRT) displays, in-plane switching (IPS) displays, touchscreens, etc.), haptic output devices, printers, and / or speakers. Thus, the interface circuit 2820 of the illustrated example generally includes a graphics driver card, a graphics driver chip, and / or a graphics driver processor.

[0299] The interface circuit 2820 of the illustrated example also includes communication devices such as transmitters, receivers, transceivers, modems, residential gateways, wireless access points, and / or network interfaces for facilitating the exchange of data with an external machine (e.g., any type of computing device) via network 2826. The communication can be via, for example, an Ethernet connection, a Digital Subscriber Line (DSL) connection, a telephone line connection, a coaxial cable system, a satellite system, a line-of-sight wireless system, a cellular phone system, etc.

[0300] The processor platform 2800 of the illustrated example also includes one or more mass storage devices 2828 for storing software and / or data. Examples of such mass storage devices 2828 include floppy disk drives, hard disk drives, CD drives, Blu-ray disc drives, Redundant Array of Independent Disks (RAID) systems, and DVD drives. In this example, one or more mass storage devices 2828 implement Figure 28 the example database 1450.

[0301] Figures 23 to 27 The machine-executable instructions 2832 can be stored in the mass storage device 2828, the volatile memory 2814, the non-volatile memory 2816, and / or on a removable non-transitory computer-readable storage medium such as a CD or DVD. In Figure 28 it, the machine-executable instructions 2832 are referred to as "encoded instructions" and "instructions".

[0302] Figure 29 is structured to execute Figures 23 to 27 the instructions to implement the block diagram of the example processor platform 2900 of the central server 1302 of FIG. 1. The processor platform 2900 can be, for example, a server, a personal computer, a workstation, a self-learning machine (e.g., a neural network), a mobile device (e.g., a cell phone, a smart phone, a tablet such as an iPad TM tablet), a PDA, or any other type of computing device.

[0303] The processor platform 2900 of the illustrated example includes a processor 2912. The processor 2912 of the illustrated example is hardware. For example, the processor 2912 can be implemented by one or more integrated circuits, logic circuits, microprocessors, GPUs, DSPs, or controllers of any desired family or manufacturer. The hardware processor can be a semiconductor-based (e.g., silicon-based) device. In this example, the processor 2912 implements Figure 15 the example autonomous vehicle tracker 1520, the example traffic analyzer 1530, the example infrastructure analyzer 1540, the example event scheduler 1550, and the example command generator 1560. In Figure 29In it, the example autonomous vehicle tracker 1520 is represented as "tracker", the example infrastructure analyzer 1540 is represented as "infrastructure analyzer", and the example command generator 1560 is represented as "command generator".

[0304] The processor 2912 of the illustrated example includes a local memory 2913 (e.g., cache). The processor 2912 of the illustrated example communicates with a main memory including a volatile memory 2914 and a non-volatile memory 2916 via a bus 2918. The volatile memory 2914 can be implemented by SDRAM, DRAM, and / or any other type of random access storage device. The non-volatile memory 2916 can be implemented by flash memory and / or any other desired type of storage device. Access to the main memories 2914, 2916 is controlled by a storage controller.

[0305] The processor platform 2900 of the illustrated example further includes an interface circuit 2920. The interface circuit 2920 can be implemented by any type of interface standard such as an Ethernet interface, USB, interface, NFC interface, and / or PCI Express interface. In this example, the interface circuit 2920 implements Figure 15 the example network interface 1510. In Figure 29 it, the example network interface 1510 is represented as "network interface".

[0306] In the illustrated example, one or more input devices 2922 are connected to the interface circuit 2920. The input devices 2922 permit a user to input data and / or commands into the processor 2912. The input devices 2922 can be implemented by, for example, audio sensors, microphones, cameras (still or video), keyboards, buttons, mice, touchscreens, touchpads, trackballs, fiducial devices, and / or voice recognition systems.

[0307] One or more output devices 2924 are also connected to the interface circuit 2920 of the illustrated example. The output devices 2924 can be implemented by, for example, display devices (e.g., LED, OLED, LCD, CRT monitors, IPS monitors, touchscreens, etc.), haptic output devices, printers, and / or speakers. Thus, the interface circuit 2920 of the illustrated example generally includes a graphics driver card, a graphics driver chip, and / or a graphics driver processor.

[0308] The interface circuit 2920 of the illustrated example also includes communication devices such as transmitters, receivers, transceivers, modems, residential gateways, wireless access points, and / or network interfaces for facilitating the exchange of data with an external machine (e.g., any type of computing device) via the network 2926. The communication can be via, for example, an Ethernet connection, a DSL connection, a telephone line connection, a coaxial cable system, a satellite system, a line-of-sight wireless system, a cellular phone system, etc.

[0309] The processor platform 2900 of the illustrated example also includes one or more mass storage devices 2928 for storing software and / or data. Examples of such mass storage devices 2928 include floppy disk drives, hard disk drives, CD drives, Blu-ray disk drives, RAID systems, and DVD drives. In this example, one or more mass storage devices 2928 implement Figure 15 the example database 1570.

[0310] Figures 23 to 27 Machine-executable instructions 2932 can be stored in the mass storage device 2928, the volatile memory 2914, the non-volatile memory 2916, and / or on a removable non-transitory computer-readable storage medium such as a CD or DVD. In Figure 29 it, the machine-executable instructions 2932 are represented as "encoded instructions" and "instructions".

[0311] In view of the foregoing, it will be appreciated that example systems, methods, devices, and articles of manufacture have been disclosed for implementing an example public transportation system with high traffic density (e.g., high traffic density personalized transportation, high traffic density air transportation, high traffic density transportation routes, etc. and / or combinations thereof). Compared with traditional transportation systems, the disclosed systems, methods, devices, and articles of manufacture improve travel efficiency and throughput. The example public transportation system disclosed herein can facilitate the use of lightweight mobile pods to transport people or packages, which are temporarily installed on autonomous carriers traveling on the road, provide high-density transportation, and provide optimized traffic flow, battery power saving efficiency, and traffic safety. The example public transportation system facilitates a fast and efficient transition from one form of transportation (e.g., land) to another form of transportation (e.g., air) to achieve faster point-to-point transfer of people and / or packages.

[0312] In addition, this disclosure includes examples according to the following clauses:

[0313] Clause 1. A system, the system comprising: a transfer carrier having a first movement system, a first stacking coupler, a first magnetic coupler, and a second magnetic coupler, the transfer carrier having a first address; a transfer pod having a second movement system, a second stacking coupler, and a second address, the second stacking coupler being configured to couple to the first stacking coupler; and a controller for: in response to obtaining a request to guide the transfer carrier to move from the first address to the second address, invoking the transfer pod to couple to the transfer carrier by guiding the transfer pod to move to the top of the transfer carrier using the second movement system; and when the transfer carrier is coupled to the transfer pod, invoking the transfer carrier to move the transfer pod to a third address using the first movement system.

[0314] Clause 2. The system according to Clause 1, wherein the transfer pod is a passenger pod for transporting one or more passengers or a parcel pod for transporting goods, and the second movement system includes one or more wheels, an engine, and a joint for facilitating a first wheel of the one or more wheels to pivot from a first position to a second position.

[0315] Clause 3. The system according to any one of Clauses 1-2, wherein the transfer pod is a parcel pod and the request is a first request, and the system further comprises: a housing having a first surface and a second surface opposite the first surface, the housing having a third magnetic coupler on the second surface; and the controller for, in response to obtaining a second request to transport the parcel pod to the third address: instructing the transfer carrier to couple the first magnetic coupler to the third magnetic coupler; instructing the parcel pod to detach from the transfer carrier; instructing the parcel pod to move onto the housing; and after the parcel pod has moved onto the housing, instructing the transfer carrier to move to a fourth address.

[0316] Clause 4. The system according to any one of Clauses 1 to 3, wherein the transfer cabin is a first transfer cabin and the transfer carrier is a first transfer carrier, the first transfer cabin has a front surface, a first rear surface, a first side surface and a second side surface, the first side surface is opposite to the second side surface, and the first transfer cabin has a third magnetic coupler on the first side surface and a fourth magnetic coupler on the second side surface, and the first transfer carrier has a second magnetic coupler on the rear surface of the first transfer carrier, and the system further includes: a second transfer cabin connected to a second transfer carrier, the second transfer carrier having a fifth magnetic coupler on the front surface of the second transfer carrier; a third transfer cabin connected to a third transfer carrier, the third transfer carrier having a sixth magnetic coupler on the third side surface of the third transfer carrier; and the controller is configured to: instruct the first transfer carrier to be connected to the second transfer carrier by connecting the second magnetic coupler to the fifth magnetic coupler; instruct the first transfer cabin to be connected to the third transfer cabin by connecting the fourth magnetic coupler to the sixth magnetic coupler; and after the connection, instruct the first transfer carrier, the second transfer carrier and the third transfer carrier to move together at the same speed.

[0317] Clause 5. The system according to any one of Clauses 1 to 4, wherein the transfer cabin is a first transfer cabin and the transfer carrier is a first transfer carrier, the first transfer carrier has a first front surface, a first rear surface, a first side surface, a second side surface, the first magnetic coupler on the first front surface, the second magnetic coupler on the first rear surface, a third magnetic coupler on the first side surface and a fourth magnetic coupler on the second side surface, and the system further includes: a second transfer cabin connected to a second transfer carrier, the second transfer carrier having a fifth magnetic coupler on the second front surface of the second transfer carrier and a sixth magnetic coupler on the third front surface of the second transfer carrier; a third transfer cabin connected to a third transfer carrier, the third transfer carrier having a seventh magnetic coupler on the fourth front surface of the third transfer carrier; and the controller, which is configured to: instruct the first transfer to be connected to the second transfer carrier by connecting the second magnetic coupler to the fifth magnetic coupler; instruct the first transfer cabin to be connected to the third transfer carrier by connecting the fourth magnetic coupler to the seventh magnetic coupler; and after the connection, instruct the first transfer carrier, the second transfer carrier and the third transfer carrier to move together at the same speed.

[0318] Clause 6. The system according to any one of Clauses 1 to 5, wherein the transfer cabin is a passenger cabin and the transfer carrier is a first transfer carrier having a first front surface and a first rear surface opposite to the first front surface, the first rear surface having the second magnetic coupler, and the system further comprises: a parcel cabin having a second stacking coupler; and a second transfer carrier having a second front surface, a second rear surface opposite to the second front surface, a third stacking coupler, and a third magnetic coupler on the second front surface, the third stacking coupler being coupled to the second stacking coupler, and the third magnetic coupler being coupled to the second magnetic coupler.

[0319] Clause 7. The system according to Clause 6, wherein the request is a first request, and the controller is configured to call the parcel cabin to be coupled to the second transfer carrier by the following steps: in response to obtaining a second request for guiding the second transfer carrier having a fourth address to move to a fifth address of the parcel cabin, calling the parcel cabin to move to the top of the second transfer carrier to be coupled to the parcel cabin using the second stacking coupler and the third stacking coupler; when the parcel cabin is coupled to the second transfer carrier, calling the second transfer carrier to move to the second address; when the second transfer carrier reaches the second address, instructing the second transfer carrier to be coupled to the first transfer carrier by coupling the second magnetic coupler to the third magnetic coupler; and when the first transfer carrier is coupled to the second transfer carrier, instructing at least one of the first transfer carrier or the second transfer carrier to move to the third address.

[0320] Clause 8. The system according to any one of Clauses 1 to 7, wherein the system further comprises: a non-transitory computer-readable storage medium in communication with the controller, the storage medium including instructions that, when executed, cause at least one processor in the controller to perform controller operations.

[0321] Clause 9. A non-transitory computer-readable storage medium, the non-transitory computer-readable storage medium including instructions that, when executed, cause at least one processor to at least perform: in response to obtaining a request to guide a transfer carrier having a first mobile system, a first magnetic coupler, a second magnetic coupler, and a first address to move to a second address of a transfer cabin having a second mobile system, when the transfer carrier reaches the second address, invoking the transfer cabin to move to the top of the transfer carrier using the mobile system; when the transfer cabin moves to the top of the transfer carrier, guiding the transfer cabin to be coupled to the transfer cabin by coupling a first stacking coupler of the transfer carrier to a second stacking coupler of the transfer cabin; and in response to the transfer carrier being coupled to the transfer cabin, instructing the transfer carrier to use the first mobile system to move the transfer cabin to a third address.

[0322] Clause 10. The non-transitory computer-readable storage medium according to Clause 9, wherein the transfer cabin is a passenger cabin for transporting one or more passengers or a parcel cabin for transporting goods, and the second mobile system includes one or more wheels, an engine, and a joint for causing a first wheel of the one or more wheels to pivot from a first position to a second position, and the instructions, when executed, cause the at least one processor to instruct a controller of the passenger cabin or the parcel cabin to move the one or more wheels from the first position to the second position by pivoting the one or more wheels using the joint.

[0323] Clause 11. The non-transitory computer-readable storage medium according to any one of Clauses 9 to 10, wherein the transfer cabin is a parcel cabin and the request is a first request, and the instructions, when executed, cause the at least one processor to: in response to obtaining a second request to transport the parcel cabin to the third address, instruct the transfer carrier to couple the first magnetic coupler to a third magnetic coupler of a housing at the third address, the housing having a first surface and a second surface opposite the first surface, the third magnetic coupler being on the second surface; instruct the parcel cabin to detach from the transfer carrier; instruct the parcel cabin to move to the housing; and after the parcel cabin has moved to the housing, instruct the transfer carrier to move to a fourth address.

[0324] Clause 12. The non-transitory computer-readable storage medium according to any one of Clauses 9 to 11, wherein the transfer cabin is a first transfer cabin and the transfer carrier is a first transfer carrier, the first transfer cabin has a front surface, a first rear surface, a first side surface, and a second side surface, the first side surface is opposite to the second side surface, and the first transfer cabin has a third magnetic coupler on the first side surface and a fourth magnetic coupler on the second side surface, and the first transfer carrier has a second magnetic coupler on the rear surface of the first transfer carrier, and the instructions, when executed, cause the at least one processor to: instruct the first transfer carrier to be coupled to the second transfer carrier by coupling the second magnetic coupler to a fifth magnetic coupler on the front surface of the second transfer carrier; instruct the first transfer cabin to be coupled to a third transfer cabin by coupling the fourth magnetic coupler to a sixth magnetic coupler on the third side surface of the third transfer cabin; and after the coupling, instruct the first transfer carrier, the second transfer carrier, and the third transfer carrier to move together at the same speed.

[0325] Clause 13. The non-transitory computer-readable storage medium according to any one of Clauses 9 to 12, wherein the transfer cabin is a first transfer cabin, and the transfer carrier is a first transfer carrier, the first transfer carrier has a first front surface, a first rear surface, a first side surface, a second side surface, the first magnetic coupler on the first front surface, the second magnetic coupler on the first rear surface, a third magnetic coupler on the first side surface, and a fourth magnetic coupler on the second side surface, and the instructions, when executed, cause the at least one processor to: instruct the first transfer carrier to be coupled to the second transfer carrier by coupling the second magnetic coupler to a fifth magnetic coupler on the second front surface of the second transfer carrier, the second transfer carrier having a sixth magnetic coupler on the third side surface of the second transfer carrier; instruct the first transfer carrier to be coupled to the third transfer carrier by coupling the fourth magnetic coupler to a seventh magnetic coupler on the fourth side surface of the third transfer carrier; and after the coupling, instruct the first transfer carrier, the second transfer carrier, and the third transfer carrier to move together at the same speed.

[0326] Clause 14. The non-transitory computer-readable storage medium according to any one of Clauses 9 to 13, wherein the transfer cabin is a passenger cabin and the transfer carrier is a first transfer carrier having a first front surface and a first rear surface opposite to the first front surface, the first rear surface having the second magnetic coupler, and the instructions, when executed, cause the at least one processor to: instruct the parcel cabin having the second stacking coupler to be coupled to the second transfer carrier by coupling the second stacking coupler to a third stacking coupler of the second transfer carrier, the second transfer carrier having a second front surface, a second rear surface opposite to the second front surface, and a third magnetic coupler on the second front surface; and instruct the first transfer carrier to be coupled to the second transfer carrier by coupling the second magnetic coupler to the third magnetic coupler.

[0327] Clause 15. The non-transitory computer-readable storage medium according to Clause 14, wherein the request is a first request, and the instructions, when executed, cause the at least one processor to call for the parcel cabin to be coupled to the second transfer carrier by the following steps: in response to obtaining a second request that guides the second transfer carrier having a fourth address to move to a fifth address of the parcel cabin, call for the parcel cabin to move to the top of the second transfer carrier to be coupled to the parcel cabin using the second stacking coupler and the third stacking coupler; when the parcel cabin is coupled to the second transfer carrier, call for the second transfer carrier to move to the second address; when the second transfer carrier reaches the second address, instruct the second transfer carrier to be coupled to the first transfer carrier by coupling the second magnetic coupler to the third magnetic coupler; and when the first transfer carrier is coupled to the second transfer carrier, instruct at least one of the first transfer carrier or the second transfer carrier to move to the third address.

[0328] Clause 16. A method, the method comprising the steps of: in response to obtaining a request that guides a transfer carrier having a first mobile system, a first magnetic coupler, a second magnetic coupler, and a first address to move to a second address of a transfer cabin having a second mobile system, when the transfer carrier reaches the second address, call for the transfer cabin to move to the top of the transfer carrier using the mobile system; when the transfer cabin moves to the top of the transfer carrier, guide the transfer cabin to be coupled to the transfer cabin by coupling a first stacking coupler of the transfer carrier to a second stacking coupler of the transfer cabin; and in response to the transfer carrier being coupled to the transfer cabin, instruct the transfer carrier to move the transfer cabin to a third address using the first mobile system.

[0329] Clause 17. The method according to Clause 16, wherein the transfer cabin is a passenger cabin for transporting one or more passengers or a parcel cabin for transporting goods, and the second moving system includes one or more wheels, an engine, and a joint for causing a first wheel of the one or more wheels to pivot from a first position to a second position, and the method further includes instructing a controller of the passenger cabin or the parcel cabin to move the one or more wheels from the first position to the second position by pivoting the one or more wheels using the joint.

[0330] Clause 18. The method according to any one of Clauses 16 to 17, wherein the transfer cabin is a parcel cabin and the request is a first request, and the method further includes the steps of: in response to obtaining a second request to transport the parcel cabin to a third address, instructing the transfer carrier to couple the first magnetic coupler to a third magnetic coupler of a housing at the third address, the housing having a first surface and a second surface opposite the first surface, the third magnetic coupler being on the second surface; instructing the parcel cabin to disengage from the transfer carrier; instructing the parcel cabin to move onto the housing; and after the parcel cabin has moved onto the housing, instructing the transfer carrier to move to a fourth address.

[0331] Clause 19. The method according to any one of Clauses 16 to 18, wherein the transfer cabin is a first transfer cabin and the transfer carrier is a first transfer carrier, the first transfer cabin having a front surface, a first rear surface, a first side surface, and a second side surface, the first side surface being opposite the second side surface, and the first transfer cabin having a third magnetic coupler on the first side surface and a fourth magnetic coupler on the second side surface, and the first transfer carrier having a second magnetic coupler on the rear surface of the first transfer carrier, and the method further includes the steps of: instructing the first transfer carrier to couple to a second transfer carrier by coupling the second magnetic coupler to a fifth magnetic coupler on the front surface of the second transfer carrier; instructing the first transfer cabin to couple to a third transfer cabin by coupling the fourth magnetic coupler to a sixth magnetic coupler on a third side surface of the third transfer cabin; and after the coupling, instructing the first transfer carrier, the second transfer carrier, and the third transfer carrier to move together at the same speed.

[0332] Clause 20. The method according to any one of Clauses 16 to 19, wherein the transfer cabin is a first transfer cabin, and the transfer carrier is a first transfer carrier, the first transfer carrier having a first front surface, a first rear surface, a first side surface, a second side surface, the first magnetic coupler on the first front surface, the second magnetic coupler on the first rear surface, a third magnetic coupler on the first side surface, and a fourth magnetic coupler on the second side surface, and the method further comprising the steps of: instructing the first transfer carrier to be coupled to the second transfer carrier by coupling the second magnetic coupler to a fifth magnetic coupler on a second front surface of the second transfer carrier, the second transfer carrier having a sixth magnetic coupler on a third side surface of the second transfer carrier; instructing the first transfer carrier to be coupled to the third transfer carrier by coupling the fourth magnetic coupler to a seventh magnetic coupler on a fourth side surface of the third transfer carrier; and after the coupling, instructing the first transfer carrier, the second transfer carrier, and the third transfer carrier to move together at the same speed.

[0333] Clause 21. The method according to any one of Clauses 16 to 20, wherein the transfer cabin is a passenger cabin and the transfer carrier is a first transfer carrier having a first front surface and a first rear surface opposite the first front surface, the first rear surface having the second magnetic coupler, and the method further comprising the steps of: instructing a parcel cabin having a second stacking coupler to be coupled to the second transfer carrier by coupling the second stacking coupler to a third stacking coupler of the second transfer carrier, the second transfer carrier having a second front surface, a second rear surface opposite the second front surface, and a third magnetic coupler on the second front surface; and instructing the first transfer carrier to be coupled to the second transfer carrier by coupling the second magnetic coupler to the third magnetic coupler.

[0334] Clause 22. The method according to Clause 21, wherein the request is a first request, and invoking the parcel cabin to be coupled to the second transfer carrier comprises the steps of: in response to obtaining a second request for guiding the second transfer carrier having a fourth address to move to a fifth address of the parcel cabin, invoking the parcel cabin to move to the top of the second transfer carrier to be coupled to the parcel cabin using the second stacking coupler and the third stacking coupler; when the parcel cabin is coupled to the second transfer carrier, invoking the second transfer carrier to move to the second address; when the second transfer carrier reaches the second address, instructing the second transfer carrier to be coupled to the first transfer carrier by coupling the second magnetic coupler to the third magnetic coupler; and when the first transfer carrier is coupled to the second transfer carrier, instructing at least one of the first transfer carrier or the second transfer carrier to move to the third address.

[0335] Although certain example systems, methods, devices, and articles have been disclosed herein, the scope of this patent is not limited thereto. Instead, this patent covers all systems, methods, devices, and articles that fall entirely within the scope of the claims of this patent.

[0336] The appended claims are hereby incorporated by reference into the detailed description, where each claim stands on its own as a separate embodiment of this disclosure.

Claims

1. A system for personalized transportation with high traffic density, the system comprising: A transfer carrier having a first address, the transfer carrier including a first mobile system, a first stacking coupler, a first magnetic coupler on a first side of the transfer carrier, a second magnetic coupler on a second side of the transfer carrier opposite the first side, and a first sensor and a second sensor on opposite lateral sides of the first magnetic coupler; A transfer pod having a second mobile system, a second stacking coupler, and a second address, the second stacking coupler being configured to couple to the first stacking coupler; And A controller for: In response to obtaining a request to guide the transfer carrier to move from the first address to the second address, invoking the transfer pod to couple to the transfer carrier by guiding the transfer pod to move to the top of the transfer carrier using the second mobile system based on the outputs of the first sensor and the second sensor; And When the transfer carrier is coupled to the transfer pod, invoking the transfer carrier to move the transfer pod to a third address using the first mobile system.

2. The system according to claim 1, wherein The transfer pod is a passenger pod for transporting one or more passengers or a parcel pod for transporting goods, and the second mobile system includes one or more wheels, an engine, and a joint for causing a first wheel of the one or more wheels to pivot from a first position to a second position.

3. The system according to any one of claims 1 to 2, wherein, The transfer pod is a parcel pod, and the request is a first request, and the system further includes: A housing having a first surface and a second surface opposite the first surface, the housing having a third magnetic coupler on the second surface; and The controller is configured to, in response to obtaining a second request to transport the parcel pod to the third address: Instruct the transfer carrier to couple the first magnetic coupler to the third magnetic coupler; Instruct the parcel pod to detach from the transfer carrier; Instruct the parcel pod to move onto the housing; and After the parcel pod has moved onto the housing, instruct the transfer carrier to move to a fourth address.

4. The system according to any one of claims 1 to 2, wherein, The transfer pod is a first transfer pod and the transfer carrier is a first transfer carrier, the first transfer pod having a front surface, a first rear surface, a first side surface, and a second side surface opposite the first side surface, and the first transfer pod having a third magnetic coupler on the first side surface and a fourth magnetic coupler on the second side surface, and the first transfer carrier having the second magnetic coupler on a rear surface of the first transfer carrier, and the system further includes: A second transfer pod coupled to a second transfer carrier, the second transfer carrier having a fifth magnetic coupler on a front surface of the second transfer carrier; A third transfer pod coupled to a third transfer carrier, the third transfer carrier having a sixth magnetic coupler on a third side surface of the third transfer carrier; and The controller for: Instruct the first intermediate carrier to be coupled to the second intermediate carrier by coupling the second magnetic coupler to the fifth magnetic coupler; Instruct the first intermediate cabin to be coupled to the third intermediate cabin by coupling the fourth magnetic coupler to the sixth magnetic coupler; and After the coupling, instruct the first intermediate carrier, the second intermediate carrier, and the third intermediate carrier to move together at the same speed.

5. The system according to any one of claims 1 to 2, wherein The intermediate cabin is the first intermediate cabin, and the intermediate carrier is the first intermediate carrier. The first intermediate carrier has a first front surface, a first rear surface, a first side surface, a second side surface, the first magnetic coupler on the first front surface, the second magnetic coupler on the first rear surface, the third magnetic coupler on the first side surface, and the fourth magnetic coupler on the second side surface. And the system further includes: A second intermediate cabin coupled to a second intermediate carrier, the second intermediate carrier having a fifth magnetic coupler on a second front surface of the second intermediate carrier and a sixth magnetic coupler on a third side surface of the second intermediate carrier; A third intermediate cabin coupled to a third intermediate carrier, the third intermediate carrier having a seventh magnetic coupler on a fourth side surface of the third intermediate carrier; and The controller is configured to: Instruct the first intermediate carrier to be coupled to the second intermediate carrier by coupling the second magnetic coupler to the fifth magnetic coupler; Instruct the first intermediate carrier to be coupled to the third intermediate carrier by coupling the fourth magnetic coupler to the seventh magnetic coupler; and After the coupling, instruct the first intermediate carrier, the second intermediate carrier, and the third intermediate carrier to move together at the same speed.

6. The system according to any one of claims 1 to 2, wherein The intermediate cabin is a passenger cabin and the intermediate carrier is the first intermediate carrier having a first front surface and a first rear surface opposite to the first front surface, the first rear surface having the second magnetic coupler. And the system further includes: A package cabin having a second stacking coupler; and A second intermediate carrier having a second front surface, a second rear surface opposite to the second front surface, a third stacking coupler, and a third magnetic coupler on the second front surface, the third stacking coupler being coupled to the second stacking coupler, and the third magnetic coupler being coupled to the second magnetic coupler.

7. The system according to claim 6, wherein, The request is the first request, and the controller is configured to call the package cabin to be coupled to the second intermediate carrier by the following steps: In response to obtaining a second request for guiding the second intermediate carrier with a fourth address to move to a fifth address of the package cabin, call the package cabin to move to the top of the second intermediate carrier to be coupled to the package cabin using the second stacking coupler and the third stacking coupler; When the package cabin is coupled to the second intermediate carrier, call the second intermediate carrier to move to the second address; When the second intermediate carrier reaches the second address, instruct the second intermediate carrier to be coupled to the first intermediate carrier by coupling the second magnetic coupler to the third magnetic coupler; And When the first transfer carrier is coupled to the second transfer carrier, indicating that at least one of the first transfer carrier or the second transfer carrier moves to the third address.

8. The system according to any one of claims 1 to 2, the system further comprising: A non-transitory computer-readable storage medium in communication with the controller, the storage medium including instructions that, when executed, cause at least one processor in the controller to perform controller operations.

9. A method for personalized transportation with high traffic density, the method comprising the following steps: In response to obtaining a request to guide a transfer carrier having a first mobile system, a first magnetic coupler, a second magnetic coupler, a first sensor and a second sensor on opposite lateral sides of the first magnetic coupler, and a first address to move to a second address of a transfer cabin having a second mobile system, when the transfer carrier reaches the second address, calling the transfer cabin to move to the top of the transfer carrier based on the outputs of the first sensor and the second sensor and using the second mobile system, the first magnetic coupler being on a first side of the transfer carrier, the second magnetic coupler being on a second side of the transfer carrier, the second side being opposite to the first side; When the transfer cabin moves to the top of the transfer carrier, guiding the transfer cabin to be coupled to the transfer cabin by coupling a first stacking coupler of the transfer carrier to a second stacking coupler of the transfer cabin; And In response to the transfer carrier being coupled to the transfer cabin, indicating that the transfer carrier uses the first mobile system to move the transfer cabin to a third address.

10. The method according to claim 9, wherein, The transfer cabin is a passenger cabin for transporting one or more passengers or a parcel cabin for transporting goods, and the second mobile system includes one or more wheels, an engine, and a joint for causing a first wheel of the one or more wheels to pivot from a first position to a second position, and the method further includes instructing a controller of the passenger cabin or the parcel cabin to move the one or more wheels from the first position to the second position by pivoting the one or more wheels using the joint.

11. The method according to any one of claims 9 to 10, wherein, The transfer cabin is a parcel cabin, and the request is a first request, and the method further includes the following steps: In response to obtaining a second request to transport the parcel cabin to the third address, indicating that the transfer carrier couples the first magnetic coupler to a third magnetic coupler of a housing at the third address, the housing having a first surface and a second surface opposite to the first surface, the third magnetic coupler being on the second surface; Instructing the parcel cabin to detach from the transfer carrier; Instructing the parcel cabin to move to the housing; and After the parcel cabin has moved to the housing, indicating that the transfer carrier moves to a fourth address.

12. The method according to any one of claims 9 to 10, wherein The transfer cabin is the first transfer cabin and the transfer carrier is the first transfer carrier. The first transfer cabin has a front surface, a first rear surface, a first side surface, and a second side surface. The first side surface is opposite to the second side surface, and the first transfer cabin has a third magnetic coupler on the first side surface and a fourth magnetic coupler on the second side surface. The first transfer carrier has the second magnetic coupler on the rear surface of the first transfer carrier. The method further comprises the following steps: Instructing the first transfer carrier to be coupled to the second transfer carrier by coupling the second magnetic coupler to a fifth magnetic coupler on the front surface of the second transfer carrier; Instructing the first transfer cabin to be coupled to the third transfer cabin by coupling the fourth magnetic coupler to a sixth magnetic coupler on the third side surface of the third transfer cabin; and After the coupling, instructing the first transfer carrier, the second transfer carrier, and the third transfer carrier to move together at the same speed.

13. The method according to any one of claims 9 to 10, wherein The transfer cabin is the first transfer cabin, and the transfer carrier is the first transfer carrier. The first transfer carrier has a first front surface, a first rear surface, a first side surface, a second side surface, the first magnetic coupler on the first front surface, the second magnetic coupler on the first rear surface, a third magnetic coupler on the first side surface, and a fourth magnetic coupler on the second side surface. The method further comprises the following steps: Instructing the first transfer carrier to be coupled to the second transfer carrier by coupling the second magnetic coupler to a fifth magnetic coupler on the second front surface of the second transfer carrier. The second transfer carrier has a sixth magnetic coupler on the third side surface of the second transfer carrier; Instructing the first transfer carrier to be coupled to the third transfer carrier by coupling the fourth magnetic coupler to a seventh magnetic coupler on the fourth side surface of the third transfer carrier; and After the coupling, instructing the first transfer carrier, the second transfer carrier, and the third transfer carrier to move together at the same speed.

14. The method according to any one of claims 9 to 10, wherein The transfer cabin is a passenger cabin and the transfer carrier is the first transfer carrier having a first front surface and a first rear surface opposite to the first front surface. The first rear surface has the second magnetic coupler. The method further comprises the following steps: Instructing a parcel cabin having a second stacking coupler to be coupled to the second transfer carrier by coupling the second stacking coupler to a third stacking coupler of the second transfer carrier. The second transfer carrier has a second front surface, a second rear surface opposite to the second front surface, and a third magnetic coupler on the second front surface; and Instructing the first transfer carrier to be coupled to the second transfer carrier by coupling the second magnetic coupler to the third magnetic coupler.

15. The method according to claim 14, wherein, The request is the first request, and the step of invoking the parcel cabin to be coupled to the second transfer carrier comprises the following steps: In response to obtaining a second request to guide the second transfer carrier having a fourth address to move to a fifth address of the package compartment, call the package compartment to move to the top of the second transfer carrier and be coupled to the package compartment using the second stacking coupler and the third stacking coupler; When the package compartment is coupled to the second transfer carrier, call the second transfer carrier to move to the second address; When the second transfer carrier reaches the second address, instruct the second transfer carrier to be coupled to the first transfer carrier by coupling the second magnetic coupler to the third magnetic coupler; And When the first transfer carrier is coupled to the second transfer carrier, instruct at least one of the first transfer carrier or the second transfer carrier to move to the third address.

Images