Vehicle-to-everything messaging

Abstract

The user equipment and a transport entity, such as a transport vehicle or a transport server, perform information exchange for a transport service using device-to-device (D2D) communication, such as dedicated short-range communication (DSRC), cellular vehicle-to-everything (C‑V2X), or 5G New Radio (NR). For example, the information exchange relates to, for example, logistics and delivery of the transport service. For example, the user equipment may send a transport request message including information elements such as an identifier, the type of transport equipment requested, the number of users, the requested destination, etc. The transport entity may send a transport response message accepting or rejecting the request. Additional messages, such as status requests and transport status, and messages related to completing the transport service may be exchanged.

Description

[0001] Claiming priority under 35 USC § 119

[0002] This application claims the benefit of and priority under 35 U.S.C. §119 to U.S. Provisional Application No. 62 / 961,154, filed on January 14, 2020, and entitled “VEHICLE TO EVERYTHING APPLICATION MESSAGING,” and U.S. Non-Provisional Application No. 17 / 124,003, filed on December 16, 2020, and entitled “VEHICLE TO EVERYTHING APPLICATION MESSAGING,” both of which are assigned to the assignee of this application and are incorporated herein by reference in their entirety. Technical Field

[0003] The subject matter disclosed herein relates to wireless communication systems, and more particularly, to methods and apparatus for vehicle-to-everything (V2X) message exchange in wireless communication systems. Background Art

[0004] Vehicle communication systems are an area of ​​active interest in the communications industry, which are used to provide useful information in transportation. For example, vehicle communication systems include nodes such as roadside units (RSUs) and the vehicles themselves, which wirelessly transmit traffic-related information and are being developed as part of intelligent transportation systems (ITS). For example, vehicle communication systems include direct communication systems such as dedicated short-range communications (DSRC), cellular vehicle-to-everything (C-V2X) communications, and even 5G new radio (NR) communications.

[0005] Traffic-related information to be communicated in currently contemplated vehicle communication systems is related to safety applications. For example, currently contemplated message exchanges in vehicle communication systems are directed to aspects such as safety warnings, traffic congestion (eg, automated traffic control), and coordinated or automated vehicle maneuvers. Summary of the invention

[0006] The user equipment and a transport entity such as a transport vehicle or a transport server perform information exchange for a transport service using device-to-device (D2D) communication such as dedicated short range communication (DSRC), cellular vehicle-to-everything (C-V2X), or 5G New Radio (NR). For example, the information exchange relates to, for example, logistics and delivery of the transport service. For example, the user equipment may send a transport request message including information elements such as an identifier, the type of transport equipment requested, the number of users, the requested destination, etc. The transport entity may send a transport response message accepting or rejecting the request. Additional messages, such as status requests and transport status, and messages related to completing the transport service may be exchanged.

[0007] In one implementation, a method for information exchange performed by a user device for a transportation service includes: wirelessly sending a transportation request message to a transportation entity, the transportation request message including one or more message information elements including an identifier of the user device and a requested destination; wirelessly receiving a transportation response message from the transportation entity, the transportation response message including one or more message information elements including an acceptance or rejection of the transportation request message; and in response to an acceptance in the transportation response message, wirelessly sending a transportation confirmation message to the transportation entity, the transportation confirmation message including one or more message information elements including an identifier of the user device.

[0008] In one implementation, a user device configured to perform information exchange for a transportation service includes: a wireless transceiver configured to communicate wirelessly with a transportation entity; at least one memory; and at least one processor coupled to the wireless transceiver and the at least one memory, the at least one processor configured to: send a transportation request message to the transportation entity via the wireless transceiver, the transportation request message including one or more message information elements including an identifier of the user device and a requested destination; receive a transportation response message from the transportation entity via the wireless transceiver, the transportation response message including one or more message information elements including an acceptance or rejection of the transportation request message; and in response to an acceptance in the transportation response message, send a transportation confirmation message to the transportation entity via the wireless transceiver, the transportation confirmation message including one or more message information elements including an identifier of the user device.

[0009] In one implementation, a user device configured to perform information exchange for a transportation service includes: a component for wirelessly sending a transportation request message to a transportation entity, the transportation request message including one or more message information elements including an identifier of the user device and a requested destination; a component for wirelessly receiving a transportation response message from the transportation entity, the transportation response message including one or more message information elements including an acceptance or rejection of the transportation request message; and a component for wirelessly sending a transportation confirmation message to the transportation entity in response to an acceptance in the transportation response message, the transportation confirmation message including one or more message information elements including an identifier of the user device.

[0010] In one implementation, a non-transitory storage medium including program code stored thereon, the program code being operable to configure at least one processor in a user device to perform an information exchange for a transportation service, comprising: program code for wirelessly sending a transportation request message to a transportation entity, the transportation request message including one or more message information elements including an identifier of the user device and a requested destination; program code for wirelessly receiving a transportation response message from the transportation entity, the transportation response message including one or more message information elements including an acceptance or a rejection of the transportation request message; and program code for wirelessly sending a transportation confirmation message to the transportation entity in response to an acceptance in the transportation response message, the transportation confirmation message including one or more message information elements including an identifier of the user device.

[0011] In one implementation, a method for information exchange performed by a transport entity for a transport service includes: wirelessly receiving a transport request message from a user device, the transport request message including one or more message information elements including an identifier of the user device and a requested destination; wirelessly sending a transport response message to the user device, the transport response message including one or more message information elements including an acceptance or rejection of the transport request message; and wirelessly receiving a transport confirmation message from the user device in response to an acceptance in the transport response message, the transport confirmation message including one or more message information elements including an identifier of the user device.

[0012] In one implementation, a transportation entity configured to perform information exchange for a transportation service includes: a wireless transceiver configured to communicate wirelessly with a user device; at least one memory; and at least one processor coupled to the wireless transceiver and the at least one memory, the at least one processor configured to: receive a transportation request message from the user device via the wireless transceiver, the transportation request message including one or more message information elements including an identifier of the user device and a requested destination; send a transportation response message to the user device via the wireless transceiver, the transportation response message including one or more message information elements including an acceptance or rejection of the transportation request message; and in response to an acceptance in the transportation response message, receive a transportation confirmation message from the user device via the wireless transceiver, the transportation confirmation message including one or more message information elements including an identifier of the user device.

[0013] In one implementation, a transport entity configured to perform information exchange for a transport service includes: a component for wirelessly receiving a transport request message from a user device, the transport request message including one or more message information elements including an identifier of the user device and a requested destination; a component for wirelessly sending a transport response message to the user device, the transport response message including one or more message information elements including an acceptance or rejection of the transport request message; and a component for wirelessly receiving a transport confirmation message from the user device in response to an acceptance in the transport response message, the transport confirmation message including one or more message information elements including an identifier of the user device.

[0014] In one implementation, a non-transitory storage medium including program code stored thereon, the program code being operable to configure at least one processor in a transportation entity to perform information exchange for a transportation service, the non-transitory storage medium including: program code for wirelessly receiving a transportation request message from a user device, the transportation request message including one or more message information elements including an identifier of the user device and a requested destination; program code for wirelessly sending a transportation response message to the user device, the transportation response message including one or more message information elements including an acceptance or rejection of the transportation request message; and program code for wirelessly receiving a transportation confirmation message from the user device in response to an acceptance in the transportation response message, the transportation confirmation message including one or more message information elements including an identifier of the user device. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Non-limiting and non-exhaustive aspects are described with reference to the following figures, wherein like reference numerals refer to like parts throughout the various figures unless otherwise specified.

[0016] Figure 1 A wireless communication system in which a user equipment and a transport entity perform wireless communication is shown.

[0017] Figure 2 Another wireless communication system in which a user equipment and a transport entity perform wireless communication is shown.

[0018] Figure 3 is a signal flow illustrating an example of a message exchange between a user device and one or more transport entities such as a transport vehicle and / or a transport server for transport service operations.

[0019] Figure 4 is a signal flow illustrating another example of a message exchange between a user device and one or more transport entities such as a transport vehicle and / or a transport server for transport service operations.

[0020] Figure 5is a flow chart illustrating a method of information exchange for a transportation service performed by a user device.

[0021] Figure 6 is a flow chart illustrating a method of performing information exchange for transportation services by a transportation entity.

[0022] Figure 7 A schematic block diagram illustrating certain exemplary features of a user equipment configured to perform information exchange for a transportation service with a transportation entity is shown.

[0023] Figure 8 A schematic block diagram illustrating certain exemplary features of a transport entity configured to perform information exchange for a transport service with a user device is shown. DETAILED DESCRIPTION

[0024] Vehicle communication systems, such as vehicle-to-everything (V2X), can be used, for example, for safety-related applications, such as safety warnings, traffic congestion (e.g., automated traffic control), and coordinated or automated vehicle maneuvers. Various standards development organizations are defining application layer messages and information elements (IEs) that support safety-related applications. For example, the Society of Automotive Engineers (SAE) is preparing work items J3186 Mobility Sharing and Coordination Services and J2945 / 6 Performance Requirements for Collaborative Adaptive Cruise Control and Platooning. In China, Baidu has initiated work on Phase 3 message definition for collaborative driving. These messages are prerequisites for Intelligent Transportation Systems (ITS), for example, for coordinated or automated vehicle maneuvers and traffic control.

[0025] As discussed herein, the vehicle communication system may additionally be used for non-safety applications. Non-safety applications may address many use case issues, such as for transportation vehicles (e.g., trains, buses, carpooling, etc.) and user device interactions with transportation vehicles (e.g., logistics, delivery, etc.). The vehicle communication system (e.g., direct wireless communication between V2X entities) may be used to engage in (e.g., request, confirm, obtain status, etc.) transportation of a consumer or service. For example, a user (e.g., a consumer) may use the vehicle communication system to request or otherwise communicate with a transportation vehicle or transportation service to be used as transportation for the user. In another example, a user (e.g., an entity or service) may use the vehicle communication system to request or otherwise communicate with a transportation vehicle or transportation service to be used as delivery transportation for goods or services (such as freight, food delivery, etc.).

[0026] In one implementation, a set of application layer IEs depicts the interaction of a transport vehicle with a user device, such as transport request or registration, status, and transport completion or deregistration. The transport-related messages may be, for example, dedicated messages in a device-to-device (D2D) communication link such as dedicated short range communication (DSRC), cellular vehicle-to-everything (C-V2X) communication, 5G new radio (NR) communication such as 5G NR-based sidelink communication, or similar wireless communication systems.

[0027] Figure 1 A V2X wireless communication system 100 is shown in which V2X services operate using direct wireless communications between V2X entities. As shown, a user device 102 associated with a user 104 can wirelessly communicate directly with various other entities such as a transportation entity shown as a transportation vehicle 110 (shown as a bus) via a vehicle-to-pedestrian (V2P) communication link 111, or wirelessly communicate with a roadside unit (RSU) 120 via a vehicle-to-infrastructure (V2I) communication link 121. Figure 1 User 104 is shown as a person who may be a consumer of transportation, for example, user 104 may be transported by transportation vehicle 110. However, in some implementations, user 104 may be an entity such as a restaurant, store, etc., and transportation vehicle 110 may be used to transport goods or services provided or requested by user 104.

[0028] A roadside unit (RSU) is a fixed infrastructure entity that supports V2X applications and can exchange messages with other entities that support V2X applications. The user equipment 102 can communicate wirelessly with the transport vehicle 110 via the RSU 120, via a V2P communication link 121 and a V2I communication link 123. For example, the wireless communication can be performed over a proximity-based service (ProSe) directional communication (PC5) reference point defined, for example, by the 3rd Generation Partnership Project (3GPP) standard body (such as in Technical Specification (TS) 23.303), and can use IEEE 1609, Wireless Access in Vehicular Environments (WAVE), Intelligent Transport Systems (ITS), Dedicated Short Range Communications (DSRC), Cellular Vehicle to Everything (C-V2X), and wireless communications on the 5.9 GHz ITS band under IEEE 802.11p, or other wireless connections directly between entities. During direct communication with one or more entities in the V2X wireless communication system 100, each entity provides V2X information, such as an identifier of the V2X entity, and other information in messages such as Common Awareness Messages (CAM) and Decentralized Notification Messages (DENM) or Basic Safety Messages (BSM), which can be used, for example, for advanced driver assistance systems (ADAS) or safety use cases such as lane changes, speed changes, passing speeds, etc. As discussed herein, the user device 102 and the transport entity (e.g., the transport vehicle 110) can also exchange messages related to the transport vehicle and user device interaction, such as logistics, delivery, status, etc.

[0029] Figure 2 A vehicle-to-network (V2N) wireless communication system 200 is shown, in which the V2X service operates using a wireless network between entities, such as a wireless wide area network (WWAN). For example, the entities can communicate via a long-term evolution (LTE) network, where the radio interface between the user equipment (UE) and the eNodeB is referred to as LTE-Uu, or other appropriate wireless networks, such as "3G", "4G" or "5G" networks. As shown, the user equipment 102 can communicate wirelessly with a transport entity such as a transport vehicle 110 or a transport server 220 via a network infrastructure 210, which for example will be referred to as an LTE network, but can be a 5G NR network or other type of network. As shown, the user equipment 102 can communicate wirelessly with the network infrastructure 210 (e.g., a base station 202, referred to as an eNodeB in the LTE network infrastructure 210 (or a gNodeB in the 5G NR network infrastructure)) via a Uu interface 203. As shown, in some implementations, the user equipment 102 may communicate directly with the RSU 230 via a communication link 231 , which is connected to the base station 204 via a Uu interface 205 .

[0030] The base station 202 can communicate with other base stations (e.g., base station 212) via an IP layer 214 and a network 216 (such as an evolved multimedia broadcast multicast service (eMBMS) / single cell point-to-multipoint (SC-PTM) network). As shown, the transport server 220 can be part of or connected to the IP layer 214, or can be external to the IP layer 214 and the network infrastructure 210. The transport server 220 can receive and route information between the user equipment 102 and the transport vehicle 110, as well as receive other external inputs. The base station 212 can communicate wirelessly with the transport vehicle 110 directly or through other V2X entities (such as RSU 232) via Uu interfaces 213 or 215 and 233, respectively. V2N communications using the "Uu" interface can be used to exchange messages using, for example, C-V2X, 5GNR communications, etc. The information exchange can be similar to that discussed above, including messages related to the interaction between the transport vehicle and the user equipment, such as logistics, delivery, status, etc., but the distance of the information exchange is greater than Figure 1 The direct communication shown in is further.

[0031] Figure 3 300 is a signal flow illustrating an example of a message exchange between a user device 102 and one or more transport entities (e.g., a transport vehicle 110 and / or a transport server 220) for transport service operations, and the user device 102 can be used by an end user or other entities such as a restaurant, a store, a service, etc. For example, a transport service can be related to public transportation, such as a city bus, a trolley bus, a tram (or light rail) and a passenger train, a rapid transit (urban rail / subway / underground transportation, etc.), a ferry, an airplane, a coach, and an intercity railway. Transport services can also include paratransit systems, vehicle rentals (e.g., taxis, rickshaws, limousines, party buses, etc.), shared scooters, shared bicycles, etc. In addition, transport services can be used for delivery transportation, for example, for goods, food, merchandise, or services. For example, a transport service can be used by an entity that provides goods or services to an end user (e.g., at the request of an end user). For example, an entity such as a restaurant, a store, a delivery service, etc. can use a vehicle communication system to request a transport vehicle (delivery device) to deliver goods or services. The entity may not care about the delivery device, but instead may be concerned with cost and delivery time or other criteria specific to the requester. In some implementations, the request may be made by an end user and provided to an entity (e.g., a restaurant, a store, a delivery service), and the entity may request a transport vehicle (delivery device) using a vehicle communication system. The message may be a dedicated message or encapsulated in a data payload, for example, in a D2D communication link such as C-V2X, DSRC, and / or 5G NR communications such as 5G NR based sidelink communications.

[0032] exist Figure 3 At stage 1 of the present invention, the user device 102 may send a transportation registration message to a transportation entity (e.g., a transportation vehicle 110). For example, the transportation registration message may be sent directly to the transportation vehicle 110. In some implementations, as shown by the dotted line, the transportation registration may be sent to the transportation server 220. For example, the transportation registration message may include an identifier of the user device 102 and an identifier of the transportation vehicle. For example, the transportation registration message may include a payment method to be charged for transportation. The transportation registration message may be a request for or registration with a specific transportation or a specific original equipment manufacturer (OEM). For example, if a bus is registered or requested, the transportation registration message may indicate the type of bus requested, such as a city bus or an off-road bus. Similarly, if a train is registered or requested, the transportation registration message may indicate the type of train requested, such as a tram, a local train, or a national train. The transportation registration message may provide a registration server address for purchasing a ticket or validating a transportation pass (e.g., a bus pass). The transportation registration message may provide information such as ticket information or destination information. The transport registration message may include a request for specific seating or luggage arrangements (such as bicycle storage), or a request for assistance, such as assistance entering / exiting the transport vehicle, assistance with luggage, etc. The transport registration message may provide message specific information, such as a validation period for the transport registration message. If the transport is requested for the delivery of goods or services, the transport registration message may provide information related to the goods or services, such as identification, type, special requirements (e.g., temperature control), and other information such as destination, cost, and delivery time.

[0033] At stage 2, for example, if user device 102 sends a transportation registration message to transportation vehicle 110, transportation vehicle 110 may send a verification registration message to transportation server 220. The verification registration message may be used by transportation vehicle 110 to verify registration of user device 102 with transportation vehicle 110, for example, to confirm that user device 102 has purchased a ticket or has a valid account for a transportation request, or alternatively, to initiate registration of the user device with a transportation vehicle or service.

[0034] At stage 3 , for example, if the message from stage 1 is sent to transport server 220 , transport server 220 may send a confirmation of the transport registration message to transport vehicle 110 or user device 102 .

[0035] At stage 4 , transport vehicle 110 may send a confirmation of the transport registration message to user device 102 .

[0036] The confirmation message from stage 3 and / or stage 4, for example, may provide information such as an indication to the user device 102 of where available seats are or have been assigned, an indication of the estimated time to the user's particular stop and / or next stop, route information or certification information, etc., for example, so that encrypted information broadcast by the transport vehicle 110 can be decrypted by the user device 102.

[0037] At stage 5, the user device 102 and the transport vehicle 110 may exchange transport-specific information. The transport-specific information may be exchanged directly, for example, upon request, or may be broadcast or periodically broadcast, for example, upon request. In some implementations, the transport-specific information, whether sent directly to the user device 102 or broadcast, may be encrypted, and the user device 102 may decrypt the message using, for example, proof information received in a confirmation message from stage 3 and / or 4. The transport-specific information may be situation-specific, for example, for a bus or train, the transport-specific information may include route information, upcoming stops, or periodic indications of the current location. Other examples of transport-specific information may include available battery, available range, or potential parking areas within a specific area for an electric scooter or bicycle, or route, location, or parking information for a ride-sharing application. In the transport-specific information, the user may request updates (such as status updates), or updates to the trip (such as a change in destination), or pass renewals, etc.

[0038] At stage 6, user device 102 may send a cancel registration (complete) message to transportation vehicle 110 or, as indicated by the dashed line, to transportation server 220. For example, a cancel registration message may be used to indicate that the user wishes to depart at a particular stop or an upcoming stop. The cancel registration message may also be used to complete purchases at the destination, for example, by charging a payment method provided during registration for a ride based on the user device.

[0039] At stage 7 , for example, if the user device 102 sends a deregistration message to the transport vehicle 110 , the transport vehicle 110 may send a deregistration (complete) message to the transport server 220 .

[0040] At stages 8 and 9, a confirmation message of the deregistration message may be sent to transport vehicle 110 and / or user device 102. For example, transport vehicle 110 or transport server 220 may request user device 102 to provide a periodic signal to transport vehicle 110 as part of the deregistration process, with which transport vehicle 110 or transport server 220 may verify that user device 102 has left transport vehicle 110 at the appropriate station, for example based on changes in signal strength as user device 102 leaves transport vehicle 110 and as transport vehicle 110 moves away and the distance between user device 102 and transport vehicle 110 increases.

[0041] Figure 4 4 is a signal flow 400 illustrating another example of message exchange between user equipment 102 and a transport entity (which may be, for example, transport vehicle 110 and / or transport server 220). The exchanged messages may be dedicated messages or encapsulated (e.g., via radio resource control (RRC) messages or the like).

[0042] exist Figure 4 At stage 1 of the present invention, the user device 102 may send a transport request message to the transport entity 110 / 220. The transport request message may be sent by the user 104 (at Figure 1 and Figure 2 ) is issued by the user device 102 to request transportation. The transportation request message may include details of the transportation, such as a user device identifier (e.g., an octet random identifier used to identify the requester and ensure anonymity), the type of transportation requested (e.g., bus, train, subway, carpool, etc.), the destination (e.g., selected from a map or address), the number of users (e.g., the number of users on the party), the type of user (e.g., pedestrian, cyclist, scooter, wheelchair, stroller, other), the validity or timeliness of the transportation request (e.g., providing an indication of how long the user is willing to wait), the maximum amount the user is willing to pay, the identification of the goods or services to be transported, special requirements (e.g., temperature control), etc. Table 1 illustrates all or some of the data fields, data elements, and their contents that may be included in the transportation request message. In addition, Table 1 provides suggestions on which data fields or data elements in the transportation request message may be considered mandatory (M) or optional (O).

[0043]

[0044]

[0045]

[0046] Table 1

[0047] exist Figure 4At stage 2 of the transport entity 110 / 220, the transport entity 110 / 220 may send a transport response message to the user device 102. The transport response message may be sent from the transport vehicle 110 or from a central service, such as the transport server 220, to accept or reject the transport request message sent in stage 1. In some implementations, the transport response message may come from the transport server 220 and may be encapsulated (e.g., via an RRC message and provided to the transport vehicle 110 so that the transport vehicle 110 makes a determination to accept or reject the transport request). The transport response message may include information such as a transport response type (e.g., acceptance or rejection), a transport type, a transport identifier, a fare, a sharing, an estimated time of arrival (ETA) for the pickup, and an ETA to the destination. Table 2 illustrates all or some of the data fields, data elements, and their contents that may be included in the transport response message. In addition, Table 2 provides suggestions on which data fields or data elements in the transport response message may be considered mandatory (M) or optional (O).

[0048]

[0049]

[0050]

[0051] Table 2

[0052] exist Figure 4 At stage 3, the user device 102 may send a transport confirmation message to the transport entity 110 / 220. The transport confirmation message may be sent by the user 104 (at Figure 1 and Figure 2 ) is issued by the user device 102 to accept the offered transportation (such as a fare, etc.). Table 3 illustrates all or some of the data fields, data elements, and their contents that may be included in the transportation confirmation message. In addition, Table 3 provides suggestions on which data fields or data elements in the transportation confirmation message may be considered mandatory (M) or optional (O).

[0053]

[0054] Table 3

[0055] exist Figure 4 At stage 4, the transport entity 110 / 220 may send a transport confirmation confirmation message to the user device 102. The transport confirmation confirmation message may be used to confirm the transport confirmation and to, for example, confirm the pickup ETA, travel ETA, fare, etc.

[0056] exist Figure 4At stage 5 of the transport status request message, the user equipment 102 may send a transport status request message to the transport entity 110 / 220. The transport status request message may include a user equipment identifier and may request the status of a transport service, such as information related to the current location (such as the current site, the time to the next site, etc.), or information related to the estimated arrival of the requested destination, such as the ETA to the destination, the number of sites to the destination, etc. Table 4 illustrates all or some of the data fields, data elements, and their contents that may be included in the transport status request message. In addition, Table 4 provides suggestions on which data fields or data elements may be considered mandatory (M) or optional (O) in the transport status request message.

[0057]

[0058] Table 4

[0059] exist Figure 4 At stage 6 of the transport entity 110 / 220, in response to the transport status request message, the transport entity 110 / 220 may send a transport status message to the user device 102. For example, the transport status message may be used to indicate the status of the requested transport service, for example, information related to the current location, or information related to the arrival estimate of the requested destination, such as the ETA to the destination, the number of stops to the destination, etc. In some implementations, the user device 102 may determine the arrival estimate of the requested destination based on the information related to the current location provided in the status message. For example, the status message may provide the time between the current stop and the upcoming stop of the bus. The user device 102 may determine the time to the destination or the number of stops to the destination based on the requested destination and the known route and the status message. It should be understood that multiple transport status requests and transport status messages may be exchanged between the user device 102 and the transport entity 110 / 220. Table 5 illustrates all or some of the data fields, data elements, and their contents that may be included in the transport status message. In addition, Table 5 provides suggestions on which data fields or data elements in the transport status message may be considered mandatory (M) or optional (O).

[0060]

[0061] Table 5

[0062] exist Figure 4At stage 7 of the transport completion request message, the user equipment 102 may send a transport completion request message to the transport entity 110 / 220. The transport completion request message may request that the user equipment 102 be allowed to get off the transport vehicle 110, for example, at the next station, and the transport service terminates. Table 6 illustrates all or some of the data fields, data elements, and their contents that may be included in the transport completion request message. In addition, Table 6 provides suggestions on which data fields or data elements in the transport completion request message may be considered mandatory (M) or optional (O).

[0063]

[0064] Table 6

[0065] exist Figure 4 At stage 8, the transport entity 110 / 220 may send a transport completion request confirmation message to the user equipment 102 in response to the transport completion request message and to confirm the transport completion request message. Table 7 illustrates all or some of the data fields, data elements, and their contents that may be included in the transport completion request confirmation message. In addition, Table 7 provides suggestions on which data fields or data elements in the transport completion request confirmation message may be considered mandatory (M) or optional (O).

[0066]

[0067] Table 7

[0068] exist Figure 4 At stage 9, the transport entity 110 / 220 may send a transport completion response message to the user device 102 in response to the transport completion request message. For example, the transport completion response message may confirm the route taken, the fare collected, etc. Table 8 illustrates all or some of the data fields, data elements, and their contents that may be included in the transport completion response message. In addition, Table 8 provides suggestions on which data fields or data elements in the transport completion response message may be considered mandatory (M) or optional (O).

[0069]

[0070] Table 8

[0071] Figure 5 5 is a flow chart illustrating a method for information exchange for a transportation service performed by a user device, such as user device 102. As shown in block 502, the user device wirelessly sends a transportation request message to a transportation entity, the transportation request message including one or more message information elements including an identifier of the user device and a requested destination, such as in Figure 3 Stage 1 or Figure 4As discussed in stage 1 of . For example, the transport entity may be the transport vehicle 110, the transport server 220, or both. At block 504, a transport response message is wirelessly received from the transport entity, the transport response message including one or more message information elements including an acceptance or rejection of the transport request message, such as, for example, Figure 3 Stage 3 or Stage 4 or Figure 4 At block 506, in response to the acceptance in the transport response message, a transport confirmation message is wirelessly transmitted to the transport entity, the transport confirmation message including one or more message information elements including an identifier of the user device, such as, for example, Figure 4 as discussed in Phase 3 of .

[0072] In one implementation, the transport request message, the transport response message, and the transport confirmation message are dedicated messages in a device-to-device (D2D) communication link, which includes one or more of dedicated short range communication (DSRC), cellular vehicle-to-everything (C-V2X) communication, or 5G new radio (NR) communication.

[0073] In one implementation, the transport request message, the transport response message, and the transport confirmation message are encapsulated in a data payload in a device-to-device (D2D) communication link, which includes one or more of dedicated short range communication (DSRC), cellular vehicle-to-everything (C-V2X) communication, or 5G new radio (NR) communication.

[0074] In one implementation, the one or more message information elements in the transport request message further include at least one of the requested transport equipment type, the number of users, the validity period of the transport request message, the maximum travel time, or the required destination arrival time, or a combination thereof.

[0075] In one implementation, the one or more message information elements in the transportation request message further include at least one of a user type, willingness to share a transportation vehicle, a maximum fare, a requested departure time, a beacon proximity threshold, or a combination thereof.

[0076] In one implementation, the one or more message information elements in the transport response message also include at least one of a transport type, a transport identifier, a fare, an indication of whether the transport is shared or individual, an estimated time of arrival for the pickup, and an estimated time of arrival at the destination, or a combination thereof.

[0077] In one implementation, the one or more message information elements in the transportation confirmation message also include at least one of a requested destination and an estimated arrival time for the pickup, or a combination thereof.

[0078] In one implementation, the user equipment may also wirelessly send a transport status request message to the transport entity, the transport status request message including one or more message information elements containing a query for information related to the current location, such as Figure 3 Stage 5 or Figure 4 The user equipment may also wirelessly receive a transport status message from the transport entity, the transport status message including one or more message information elements containing information related to the current location, such as Figure 3 Stage 5 or Figure 4 The user equipment may be further configured to use information related to the current location to determine an arrival estimate for the requested destination.

[0079] In one implementation, the user equipment may also wirelessly send a transport status request message to the transport entity, the transport status request message including one or more message information elements including an identifier of the user equipment, a query for information related to an arrival estimate of the requested destination, e.g. Figure 3 Stage 5 or Figure 4 The user equipment may also wirelessly receive a transport status message from the transport entity, the transport status message including one or more message information elements containing an arrival estimate of the destination, such as in Figure 3 Stage 5 or Figure 4 As discussed at stage 6 of . For example, the arrival estimate of the destination includes one or more of an estimated arrival time to the destination and an estimated number of stops to the destination. In another example, one or more message information elements in the transport status message also include a destination of a transport vehicle closest to the requested destination.

[0080] In one implementation, the user device may wirelessly send a transport completion request message to the transport entity, the transport completion request message including one or more message information elements including an identifier of the user device and a drop-off request, such as in Figure 3 Stage 6 or Figure 4 The user device may also wirelessly receive a transport completion confirmation message from the transport entity, the transport completion confirmation message including one or more message information elements including an arrival estimate of the destination and a confirmation of the drop-off request, for example, as in Figure 3 Stage 8 or Stage 9 or Figure 4The user device may also wirelessly receive a transport completion response message from the transport entity, the transport completion response message including one or more message information elements including an identifier of the user device, an entry location, and an exit location. In one implementation, the transport completion response message also includes one or more message information elements including at least one of a fare and a request to provide a periodic signal to verify that the user device has left the transport vehicle.

[0081] Figure 6 6 is a flow chart illustrating a method for information exchange for transportation services performed by a transportation entity, wherein the transportation entity may include, for example, a transportation vehicle 110, a transportation server 220, or both. As shown in block 602, the transportation entity wirelessly receives a transportation request message from a user device, the transportation request message including one or more message information elements including an identifier of the user device and a requested destination, such as in Figure 3 Stage 1 or Figure 4 At block 604, a transport response message is wirelessly sent to the user device, the transport response message including one or more message information elements containing an acceptance or rejection of the transport request message, such as, for example, Figure 3 Stage 3 or Stage 4 or Figure 4 At block 606, in response to the acceptance in the transport response message, a transport confirmation message is wirelessly received from the user device, the transport confirmation message including one or more message information elements including an identifier of the user device, such as, for example, Figure 4 as discussed in Phase 3 of .

[0082] In one implementation, the transport request message, the transport response message, and the transport confirmation message are dedicated messages in a device-to-device (D2D) communication link, which includes one or more of dedicated short range communication (DSRC), cellular vehicle-to-everything (C-V2X) communication, or 5G new radio (NR) communication.

[0083] In one implementation, the transport request message, the transport response message, and the transport confirmation message are encapsulated in a data payload in a device-to-device (D2D) communication link, which includes one or more of dedicated short range communication (DSRC), cellular vehicle-to-everything (C-V2X) communication, or 5G new radio (NR) communication.

[0084] In one implementation, the one or more message information elements in the transport request message further include at least one of the requested transport equipment type, the number of users, the validity period of the transport request message, the maximum travel time, or the required destination arrival time, or a combination thereof.

[0085] In one implementation, the one or more message information elements in the transportation request message further include at least one of a user type, willingness to share a transportation vehicle, a maximum fare, a requested departure time, a beacon proximity threshold, or a combination thereof.

[0086] In one implementation, the one or more message information elements in the transport response message also include at least one of a transport type, a transport identifier, a fare, an indication of whether the transport is shared or individual, an estimated time of arrival for the pickup, and an estimated time of arrival at the destination, or a combination thereof.

[0087] In one implementation, the one or more message information elements in the transportation confirmation message also include at least one of a requested destination and an estimated arrival time for the pickup, or a combination thereof.

[0088] In one implementation, the transport entity may also wirelessly receive a transport status request message from the user device, the transport status request message including one or more message information elements containing a query for information related to the current location, such as in Figure 3 Stage 5 or Figure 4 The transport entity may also wirelessly send a transport status message to the user device, the transport status message including one or more message information elements containing information related to the current location, such as Figure 3 Stage 5 or Figure 4 as discussed in Stage 6 of

[0089] In one implementation, the transport entity may also wirelessly receive a transport status request message from the user device, the transport status request message including one or more message information elements including an identifier of the user device, query information related to the arrival estimate of the requested destination, such as Figure 3 Stage 5 or Figure 4 The transport entity may also wirelessly send a transport status message to the user equipment, the transport status message including one or more message information elements containing an arrival estimate of the destination, for example, as in Figure 3 Stage 5 or Figure 4 As discussed at stage 6 of . For example, the arrival estimate of the destination includes one or more of an estimated arrival time to the destination and an estimated number of stops to the destination. In another example, one or more message information elements in the transport status message also include a destination of a transport vehicle closest to the requested destination.

[0090] In one implementation, the transport entity may also wirelessly receive a transport completion request message from the user device, the transport completion request message including one or more message information elements including an identifier of the user device and a drop-off request, such as in Figure 3 Stage 6 or Figure 4 The transport entity may also wirelessly send a transport completion confirmation message to the user device, the transport completion confirmation message including one or more message information elements including an arrival estimate of the destination and a confirmation of the drop-off request, for example, as in Figure 3 Stage 8 or Stage 9 or Figure 4 The transport entity may also wirelessly send a transport completion response message to the user device, the transport completion response message including one or more message information elements including an identifier of the user device, an entry location, and an exit location, for example, as in Figure 3 Stage 8 or Stage 9 or Figure 4 In one implementation, the transport completion response message further includes one or more message information elements including at least one of a fare and a request to provide a periodic signal to verify that the user device has left the transport vehicle.

[0091] Figure 7 A schematic block diagram illustrating certain exemplary features of a user device 700 is shown, which may be, for example, Figure 1-Figure 3 The user device 102 shown is configured to perform information exchange for transportation services with a transportation entity, which can be a transportation vehicle 110, a transportation server 220, or both. The user device 700 can, for example, include one or more processors 702, a memory 704, a wireless wide area network (WWAN) transceiver 710, and a wireless local area network (WLAN) transceiver 740, which can be operatively coupled to a non-transitory computer-readable medium 720 and the memory 704 with one or more connectors 706 (e.g., a bus, line, optical fiber, link, etc.). The user device 700 can also include additional items (not shown), such as a user interface, which can include, for example, a display, a keyboard, or other input device (such as a virtual keyboard on a display), through which a user can connect to the user device or a satellite positioning system receiver. In certain example implementations, all or part of the user device 700 can take the form of a chipset or the like. The transceiver 710 can be, for example, a cellular transceiver, and can be configured to send and receive inter-vehicle communications, such as Figure 1 and Figure 2 As shown in . The transceiver 710 may include a transmitter 712 that can transmit one or more signals over one or more types of wireless communication links; and a receiver 714 to receive one or more signals transmitted over one or more types of wireless communication links. The transceiver 740 may be, for example, a short-range transceiver and may be configured to wirelessly transmit and receive inter-vehicle communications, such as Figure 1 and Figure 2. The transceiver 740 may include a transmitter 742 capable of transmitting one or more signals over one or more types of wireless communication links; and a receiver 744 capable of receiving one or more signals transmitted over one or more types of wireless communication links. The transceivers 710 and 740 enable the user equipment 700 to communicate with a transport entity using a D2D communication link such as DSRC, C-V2X, or 5G NR.

[0092] In some embodiments, the user equipment 700 may include an antenna 711, which may be internal or external. The antenna 711 may be used to transmit and / or receive signals processed by the transceiver 710 and / or the transceiver 740. In some embodiments, the user equipment antenna 711 may be coupled to the transceiver 710 and / or the transceiver 740. In some embodiments, measurements of signals received (transmitted) by the user equipment 700 may be performed at the connection point between the user equipment antenna 711 and the transceiver 710 and / or the transceiver 740. For example, the measurement reference point for the received (transmitted) RF signal measurement may be the input (output) end of the receiver 714, 744 (transmitter 712, 742) and the output (input) end of the user equipment antenna 711. In a user equipment 700 having multiple user equipment antennas 711 or an antenna array, the antenna connector may be regarded as a virtual point representing the total output (input) of the multiple user equipment antennas.

[0093] The one or more processors 702 may be implemented using a combination of hardware, firmware, and software. For example, the one or more processors 702 may be configured to perform the functions discussed herein by implementing one or more instructions or program codes 708 on a non-transitory computer-readable medium such as the medium 720 and / or the memory 704. In some embodiments, the one or more processors 702 may represent one or more circuits that may be configured to execute at least a portion of a data signal computing program or process associated with the operation of the user device 700.

[0094] The medium 720 and / or the memory 704 may store instructions or program code 708 containing executable code or software instructions that, when executed by the one or more processors 702, cause the one or more processors 702 to operate as a programmed special-purpose computer to perform the techniques disclosed herein. As shown in the user device 700, the medium 720 and / or the memory 704 may include one or more components or modules that may be implemented by the one or more processors 702 to perform the methods described herein. Although the components or modules are shown as software in the medium 720 executable by the one or more processors 702, it should be understood that the components or modules may be stored in the memory 704, or may be dedicated hardware in or outside the one or more processors 702.

[0095] A number of software modules and data tables may reside in the media 720 and / or memory 704 and be used by the one or more processors 702 to manage both the communications and functions described herein. It should be understood that the organization of the contents of the media 720 and / or memory 704 as shown in the user device 700 is merely exemplary, and therefore, the functionality of the modules and / or data structures may be combined, separated and / or structured in different ways depending on the implementation of the user device 700.

[0096] The medium 720 and / or the memory 704 may include a transportation request module 722, which, when implemented by the one or more processors 702, configures the one or more processors 702 to send a transportation request message to a transportation entity, for example, via the transceiver 710 or the transceiver 740. The transportation request message may include one or more message information elements including an identifier of the user device 700, the type of transportation vehicle requested, the number of users, and the requested destination, which may be selected by the user. The transportation request message may also include one or more of a validity period of the transportation request message, a maximum travel time or a required destination arrival time, a user type, a willingness to share a transportation vehicle, a maximum fare, a requested departure time, a beacon proximity threshold, or a combination thereof.

[0097] The medium 720 and / or the memory 704 may include a transportation response module 724, which, when implemented by the one or more processors 702, configures the one or more processors 702 to receive a transportation response message from a transportation entity, for example, via the transceiver 710 or the transceiver 740. The transportation response message may include one or more message information elements containing an acceptance or rejection of the transportation request message. The transportation response message may also include at least one of a transportation type, a transportation identifier, a fare, an indication of whether the transportation is shared or separate, an estimated arrival time of the pickup, and an estimated arrival time to the destination, or a combination thereof.

[0098] The medium 720 and / or the memory 704 may include a transport confirmation module 726, which, when implemented by the one or more processors 702, configures the one or more processors 702 to send a transport confirmation message to the transport entity, for example, via the transceiver 710 or the transceiver 740, in response to the acceptance in the transport response message. The transport confirmation message may include one or more message information elements including an identifier of the user device. The transport confirmation message may also include at least one of the requested destination and an estimated arrival time of the pickup, or a combination thereof.

[0099] The medium 720 and / or the memory 704 may include a status request module 728 that, when implemented by the one or more processors 702, configures the one or more processors 702 to send a status request message to a transportation entity, e.g., in response to a user input, e.g., via the transceiver 710 or the transceiver 740. The status request message may include one or more message information elements including a query for information related to a current location or identifier of the user device 700 and a query for information related to an arrival estimate for a requested destination.

[0100] The medium 720 and / or the memory 704 may include a status module 730, which, when implemented by the one or more processors 702, configures the one or more processors 702 to receive a status message from a transportation entity, such as via the transceiver 710 or the transceiver 740, in response to a status request message. The transportation status message may include one or more message information elements containing information related to the current location or the arrival estimate of the destination. The arrival estimate of the destination may be an estimated arrival time to the destination or an estimated number of stops to the destination. The transportation status message may include the destination of the transportation vehicle closest to the requested destination.

[0101] The medium 720 and / or the memory 704 may include an arrival estimation module 731, which, when implemented by the one or more processors 702, configures the one or more processors 702 to use information related to the current location to determine an arrival estimate for the requested destination. For example, based on the current location, an estimated arrival time to the destination or an estimated number of stops that may be available to the destination may be determined.

[0102] The medium 720 and / or the memory 704 may include a fulfillment request module 732, which, when implemented by the one or more processors 702, configures the one or more processors 702 to send a fulfillment request message to the transportation entity, e.g., in response to a user input, e.g., via the transceiver 710 or the transceiver 740. The fulfillment request message may include one or more message information elements including an identifier of the user device 700 and a drop-off request.

[0103] The medium 720 and / or the memory 704 may include a completion confirmation module 734 that, when implemented by the one or more processors 702, configures the one or more processors 702 to, for example, receive a completion confirmation message from a transportation entity in response to a completion request message, such as via the transceiver 710 or the transceiver 740. The completion confirmation message may include one or more message information elements including an arrival estimate of the destination and a confirmation of the drop-off request.

[0104] The medium 720 and / or the memory 704 may include a completion response module 736, which, when implemented by the one or more processors 702, configures the one or more processors 702 to, for example, respond to the completion request message, such as receiving a completion response message from the transportation entity via the transceiver 710 or the transceiver 740. The completion response message may include one or more message information elements including an identifier of the user device, an entry location, an exit location, and a fare. The completion response message may also include a request to provide a periodic signal to verify that the user device has left the transportation vehicle.

[0105] The methods described herein can be implemented by various components depending on the application. For example, these methods can be implemented in hardware, firmware, software, or any combination thereof. For hardware implementation, one or more processors 702 can be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or combinations thereof.

[0106] For firmware and / or software implementations, the methods can be implemented with modules (e.g., programs, functions, etc.) that perform the functions described herein. Any machine-readable medium that tangibly embodies instructions can be used to implement the methods described herein. For example, software code can be stored in a non-transitory computer-readable medium 720 or memory 704 connected to one or more processors 702 and executed by one or more processors 702. The memory can be implemented within one or more processors or external to one or more processors. As used herein, the term "memory" refers to any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type of memory or any number of memories, or the type of medium on which the memory is stored.

[0107] If implemented in firmware and / or software, the functionality may be stored as one or more instructions or program code 708 on a non-transitory computer-readable medium such as medium 720 and / or memory 704. Examples include computer-readable media encoded with data structures and computer-readable media encoded with computer programs 708. For example, a non-transitory computer-readable medium including program code 708 stored thereon may include program code 708 for supporting OTDOA measurements in a manner consistent with the disclosed embodiments. The non-transitory computer-readable medium 720 includes physical computer storage media. The storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such non-transitory computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the required program code 708 in the form of instructions or data structures and can be accessed by a computer; disks and optical disks as used herein include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, where disks typically reproduce data magnetically, while optical disks reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0108] In addition to being stored on the computer-readable medium 720, the instructions and / or data may be provided as signals on a transmission medium included in the communication device. For example, the communication device may include a transceiver 710 with signals indicating instructions and data. The instructions and data are configured to cause one or more processors to implement the functions outlined in the claims. That is, the communication device includes a transmission medium with signals indicating information for performing the disclosed functions.

[0109] The memory 704 may represent any data storage mechanism. The memory 704 may include, for example, a main memory and / or a secondary memory. The main memory may include, for example, a random access memory, a read-only memory, etc. Although shown in this example as being separate from the one or more processors 702, it should be understood that all or part of the main memory may be provided within the one or more processors 702, or otherwise co-located / coupled with the one or more processors 702. The secondary memory may include, for example, a memory of the same or similar type as the main memory and / or one or more data storage devices or systems, such as, for example, a disk drive, an optical drive, a tape drive, a solid-state memory drive, etc.

[0110] In some implementations, the secondary storage may be operable to receive, or otherwise be configurable to be coupled to, the non-transitory computer-readable medium 720. Thus, in some example implementations, the methods and / or apparatus presented herein may take the form of all or part of a computer-readable medium 720, which may include computer-implemented code 708 stored thereon, which, if executed by one or more processors 702, may be operable to enable it to perform all or part of the example operations as described herein. The computer-readable medium 720 may be part of the memory 704.

[0111] Thus, a user device such as user device 700 may include means for wirelessly sending a transport request message to a transport entity, the transport request message including one or more message information elements including an identifier of the user device and a requested destination, the means may be, for example, a wireless transceiver 710 or a wireless transceiver 740 and one or more processors 702 having dedicated hardware or executable code or software instructions in implementation medium 720 and / or memory 704, such as a transport request module 722. Means for wirelessly receiving a transport response message from a transport entity, the transport response message including one or more message information elements including an acceptance or rejection of the transport request message, the means may be, for example, a wireless transceiver 710 or a wireless transceiver 740 and one or more processors 702 having dedicated hardware or executable code or software instructions in implementation medium 720 and / or memory 704, such as a transport response module 724. A component for wirelessly sending a shipping confirmation message to a shipping entity in response to an acceptance in a shipping response message, the shipping confirmation message including one or more message information elements including an identifier of a user device, the component can be, for example, a wireless transceiver 710 or a wireless transceiver 740 and one or more processors 702 having dedicated hardware or implementation media 720 and / or executable code or software instructions (such as a shipping confirmation module 726) in a memory 704.

[0112] In one implementation, the user equipment may also include a component for wirelessly sending a transport status request message to a transport entity, the transport status request message including one or more message information elements containing a query for information related to the current location, which component may be, for example, a wireless transceiver 710 or a wireless transceiver 740 and one or more processors 702 having dedicated hardware or executable code or software instructions in the implementation medium 720 and / or memory 704 (such as a status request module 728). A component for wirelessly receiving a transport status message from a transport entity, the transport status message including one or more message information elements containing information related to the current location, which component may be, for example, a wireless transceiver 710 or a wireless transceiver 740 and one or more processors 702 having dedicated hardware or executable code or software instructions in the implementation medium 720 and / or memory 704 (such as a status module 730). The user device may also include a component for determining an arrival estimate for a requested destination using information related to the current location, which component may be, for example, one or more processors 702 having dedicated hardware or executable code or software instructions (such as an arrival estimation module 731) in the implementation medium 720 and / or memory 704.

[0113] In one implementation, the user device may also include means for wirelessly sending a transport status request message to a transport entity, the transport status request message including one or more message information elements including an identifier of the user device and a query for information related to an arrival estimate of the requested destination, the means may be, for example, a wireless transceiver 710 or a wireless transceiver 740 and one or more processors 702 having dedicated hardware or executable code or software instructions in implementation medium 720 and / or memory 704, such as a status request module 728. Means for wirelessly receiving a transport status message from a transport entity, the transport status message including one or more message information elements including an arrival estimate of the destination, the means may be, for example, a wireless transceiver 710 or a wireless transceiver 740 and one or more processors 702 having dedicated hardware or executable code or software instructions in implementation medium 720 and / or memory 704, such as a status module 730.

[0114] In one implementation, the user device may also include means for wirelessly sending a transport completion request message to the transport entity, the transport completion request message including one or more message information elements including an identifier of the user device and a drop-off request, which means may be, for example, a wireless transceiver 710 or a wireless transceiver 740 and one or more processors 702 with dedicated hardware or executable code or software instructions in implementation medium 720 and / or memory 704, such as a completion request module 732. Means for wirelessly receiving a transport completion confirmation message from the transport entity, the transport completion confirmation message including one or more message information elements including an arrival estimate of the destination and a confirmation of the drop-off request, which means may be, for example, a wireless transceiver 710 or a wireless transceiver 740 and one or more processors 702 with dedicated hardware or executable code or software instructions in implementation medium 720 and / or memory 704, such as a completion confirmation module 734. A component for wirelessly receiving a transport completion response message from a transport entity, the transport completion response message including one or more message information elements including an identifier of a user device, an entry location, and an exit location, the component can be, for example, a wireless transceiver 710 or a wireless transceiver 740 and one or more processors 702 having dedicated hardware or an implementation medium 720 and / or executable code or software instructions (such as a completion response module 736) in a memory 704.

[0115] Figure 8 A schematic block diagram illustrating certain exemplary features of a transport entity 800 is shown, which may be, for example, Figure 1-Figure 3 The transport vehicle 110 or transport server 220 shown is configured to perform information exchange for transport services with a user device (such as user device 102). In some embodiments, the transport entity 800 may include, for example, one or more processors 802, memory 804, transceiver 810 (e.g., wireless interface) and (if applicable) communication interface 806 (e.g., wired or wireless interface to other transport entities, such as to the transport vehicle 110 or transport server 220), which may be operatively coupled to the non-transitory computer-readable medium 820 and memory 804 with one or more connectors 806 (e.g., bus, line, optical fiber, link, etc.). In some example implementations, some portions of the transport entity 800 may take the form of a chipset or the like.

[0116] The transceiver 810 may, for example, include a transmitter 812 capable of transmitting one or more signals over one or more types of wireless communication links; and a receiver 814 to receive one or more signals transmitted over one or more types of wireless communication links. The transceiver 810 enables the transport entity 800 to communicate with a user device using a D2D communication link such as DSRC, C-V2X, or 5G NR. The transport entity 800 may include an antenna 811 to transmit and / or receive signals processed by the transceiver 810. The communication interface 840 may include various wired and wireless connections that support wired transmission and / or reception, and may additionally or alternatively support the transmission and reception of one or more signals over one or more types of wireless communication systems, if desired. The communication interface 806 may also include an interface for communicating with various other computers and peripheral devices. For example, in one embodiment, the communication interface 806 may include a network interface card, an input-output card, a chip, and / or an ASIC that implements one or more of the communication functions performed by the transport entity 800.

[0117] The one or more processors 802 may be implemented using a combination of hardware, firmware, and software. For example, the one or more processors 802 may be configured to perform the functions discussed herein by implementing one or more instructions or program codes 808 on a non-transitory computer-readable medium such as the medium 820 and / or the memory 804. In some embodiments, the one or more processors 802 may represent one or more circuits that may be configured to execute at least a portion of a data signal computing program or process associated with the operation of the transport entity 800.

[0118] The medium 820 and / or the memory 804 may store instructions or program code 808 containing executable code or software instructions that, when executed by one or more processors 802, cause the one or more processors 802 to operate as a programmed special-purpose computer to perform the techniques disclosed herein. As shown in the transport entity 800, the medium 820 and / or the memory 804 may include one or more components or modules that may be implemented by one or more processors 802 to perform the methods described herein. Although the components or modules are shown as software in the medium 820 executable by one or more processors 802, it should be understood that the components or modules may be stored in the memory 804, or may be dedicated hardware in or outside of the one or more processors 802.

[0119] A number of software modules and data tables may reside in the media 820 and / or memory 804 and be used by the one or more processors 802 to manage both the communications and functions described herein. It should be understood that the organization of the contents of the media 820 and / or memory 804 as shown in the mobile device 82 is merely exemplary, and therefore, the functionality of the modules and / or data structures may be combined, separated and / or structured in different ways depending on the implementation of the transport entity 800.

[0120] The medium 820 and / or the memory 804 may include a transportation request module 822, which, when implemented by the one or more processors 802, configures the one or more processors 802 to receive a transportation request message from the user device 102, for example, via the transceiver 810. The transportation request message may include one or more message information elements including an identifier of the user device, the type of transportation vehicle requested, the number of users, and the requested destination. The transportation request message may also include one or more of a validity period of the transportation request message, a maximum travel time or a required destination arrival time, a user type, a willingness to share a transportation vehicle, a maximum fare, a requested departure time, a beacon proximity threshold, or a combination thereof.

[0121] The medium 820 and / or the memory 804 may include a transportation response module 824, which, when implemented by the one or more processors 802, configures the one or more processors 802 to send a transportation response message to the user device 102, for example, via the transceiver 810. The transportation response message may include one or more message information elements including an acceptance or rejection of the transportation request message. The transportation response message may also include at least one of a transportation type, a transportation identifier, a fare, an indication of whether the transportation is shared or separate, an estimated arrival time of the pickup, and an estimated arrival time to the destination, or a combination thereof.

[0122] The medium 820 and / or the memory 804 may include a transport confirmation module 826 that, when implemented by the one or more processors 802, configures the one or more processors 802 to respond to the acceptance in the transport response message, such as receiving a transport confirmation message from the user device 102 via the transceiver 810. The transport confirmation message may include one or more message information elements including an identifier of the user device. The transport confirmation message may also include at least one of the requested destination and an estimated arrival time of the pickup, or a combination thereof.

[0123] The medium 820 and / or the memory 804 may include a status request module 828 that, when implemented by the one or more processors 802, configures the one or more processors 802 to receive a status request message from the user equipment 102, e.g., via the transceiver 810. The status request message may include one or more message information elements including a query for information related to a current location or identifier of the user equipment 800 and a query for information related to an arrival estimate for a requested destination.

[0124] The medium 820 and / or the memory 804 may include a status module 830, which, when implemented by the one or more processors 802, configures the one or more processors 802 to, for example, send a status message to the user device 102 via the transceiver 810 in response to the status request message. The transport status message may include one or more message information elements containing information related to the current location or the arrival estimate of the destination. The arrival estimate of the destination may be an estimated arrival time to the destination or an estimated number of stops to the destination. The transport status message may include the destination of the transport vehicle closest to the requested destination.

[0125] The medium 820 and / or memory 804 may include a completion request module 832, which, when implemented by the one or more processors 802, configures the one or more processors 802 to receive a completion request message from the user device 102, for example, via the transceiver 810. The completion request message may include one or more message information elements including an identifier of the user device 800 and a request to get off the vehicle.

[0126] The medium 820 and / or the memory 804 may include a completion confirmation module 834, which, when implemented by the one or more processors 802, configures the one or more processors 802 to, for example, send a completion confirmation message to the user device 102 via the transceiver 810 in response to the completion request message. The completion confirmation message may include one or more message information elements including an arrival estimate of the destination and a confirmation of the drop-off request.

[0127] The medium 820 and / or the memory 804 may include a completion response module 836, which, when implemented by the one or more processors 802, configures the one or more processors 802 to, for example, respond to the completion request message, for example, by sending a completion response message to the user device 102 via the transceiver 810. The completion response message may include one or more message information elements including an identifier of the user device, an entry location, an exit location, and a fare. The completion response message may also include a request to provide a periodic signal to verify that the user device has left the transportation vehicle.

[0128] The methods described herein can be implemented by various components depending on the application. For example, these methods can be implemented in hardware, firmware, software, or any combination thereof. For hardware implementation, one or more processors 802 can be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described herein, or combinations thereof.

[0129] For firmware and / or software implementations, the methods can be implemented with modules (e.g., programs, functions, etc.) that perform the functions described herein. Any machine-readable medium that tangibly embodies instructions can be used to implement the methods described herein. For example, software code can be stored in a non-transitory computer-readable medium 820 or memory 804 connected to one or more processors 702 and executed by one or more processors 802. The memory can be implemented within one or more processors or external to one or more processors. As used herein, the term "memory" refers to any type of long-term, short-term, volatile, non-volatile, or other memory, and is not limited to any particular type of memory or any number of memories, or the type of medium on which the memory is stored.

[0130] If implemented in firmware and / or software, the functionality may be stored as one or more instructions or program code 808 on a non-transitory computer-readable medium such as medium 820 and / or memory 804. Examples include computer-readable media encoded with data structures and computer-readable media encoded with computer programs 808. For example, a non-transitory computer-readable medium including program code 808 stored thereon may include program code 808 for supporting OTDOA measurements in a manner consistent with the disclosed embodiments. Non-transitory computer-readable media 820 include physical computer storage media. The storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, such non-transitory computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the required program code 808 in the form of instructions or data structures and can be accessed by a computer; disks and optical disks as used herein include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, where disks typically reproduce data magnetically, while optical disks reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0131] In addition to being stored on the computer-readable medium 820, the instructions and / or data may be provided as signals on a transmission medium included in the communication device. For example, the communication device may include a transceiver 810 with signals indicating instructions and data. The instructions and data are configured to cause one or more processors to implement the functions outlined in the claims. That is, the communication device includes a transmission medium with signals indicating information for performing the disclosed functions.

[0132] The memory 804 may represent any data storage mechanism. The memory 804 may include, for example, a main memory and / or a secondary memory. The main memory may include, for example, a random access memory, a read-only memory, etc. Although shown in this example as being separate from the one or more processors 802, it should be understood that all or part of the main memory may be provided within the one or more processors 802, or otherwise co-located / coupled with the one or more processors 802. The secondary memory may include, for example, a memory of the same or similar type as the main memory and / or one or more data storage devices or systems, such as, for example, a disk drive, an optical drive, a tape drive, a solid-state memory drive, etc.

[0133] In some implementations, the secondary storage may be operable to receive, or otherwise be configurable to be coupled to, the non-transitory computer-readable medium 820. Thus, in some example implementations, the methods and / or apparatus presented herein may take the form of all or part of a computer-readable medium 820, which may include computer-implemented code 808 stored thereon, which, if executed by one or more processors 802, may be operable to enable it to perform all or part of the example operations as described herein. The computer-readable medium 820 may be part of the memory 804.

[0134] Thus, a transport entity (e.g., transport entity 800) may include means for wirelessly receiving a transport request message from a user device, the transport request message including one or more message information elements including an identifier of the user device and a requested destination, such as a transceiver 810 and one or more processors 802 having dedicated hardware or executable code or software instructions in an implementation medium 820 and / or memory 804, such as a transport request module 822. Means for wirelessly sending a transport response message to the user device, the transport response message including one or more message information elements including an acceptance or rejection of the transport request message, such as a transceiver 810 and one or more processors 802 having dedicated hardware or executable code or software instructions in an implementation medium 820 and / or memory 804, such as a transport response module 824. A component for wirelessly receiving a shipping confirmation message from a user device in response to an acceptance in a shipping response message, the shipping confirmation message including one or more message information elements including an identifier of the user device, the component can be, for example, a transceiver 810 and one or more processors 802 having dedicated hardware or implementation media 820 and / or executable code or software instructions (such as a shipping confirmation module 826) in a memory 804.

[0135] In one implementation, the transport entity may include means for wirelessly receiving a transport status request message from a user device, the transport status request message including one or more message information elements containing a query for information related to the current location, which means may be, for example, a transceiver 810 and one or more processors 802 having dedicated hardware or implementation medium 820 and / or executable code or software instructions in memory 804, such as a status request module 828. Means for wirelessly sending a transport status message to a user device, the transport status message including one or more message information elements containing information related to the current location, which means may be, for example, a transceiver 810 and one or more processors 802 having dedicated hardware or implementation medium 820 and / or executable code or software instructions in memory 804, such as a status module 830.

[0136] In one implementation, the transport entity may include means for wirelessly receiving a transport status request message from a user device, the transport status request message including one or more message information elements including an identifier of the user device and a query for information related to an arrival estimate of the requested destination, the means may be, for example, a transceiver 810 and one or more processors 802 having dedicated hardware or executable code or software instructions in an implementation medium 820 and / or memory 804, such as a status request module 828. Means for wirelessly sending a transport status message to a user device, the transport status message including one or more message information elements including an arrival estimate of the destination, the means may be, for example, a transceiver 810 and one or more processors 802 having dedicated hardware or executable code or software instructions in an implementation medium 820 and / or memory 804, such as a status module 830.

[0137] In one implementation, the transport entity may include means for wirelessly receiving a transport completion request message from a user device, the transport completion request message including one or more message information elements including an identifier of the user device and a drop-off request, which means may be, for example, a transceiver 810 and one or more processors 802 having dedicated hardware or executable code or software instructions in implementation medium 820 and / or memory 804, such as a completion request module 832. Means for wirelessly sending a transport completion confirmation message to the user device, the transport completion confirmation message including one or more message information elements including an arrival estimate of the destination and a confirmation of the drop-off request, which means may be, for example, a transceiver 810 and one or more processors 802 having dedicated hardware or executable code or software instructions in implementation medium 820 and / or memory 804, such as a completion confirmation module 834. A component for wirelessly sending a transport completion response message to a user device, the transport completion response message including one or more message information elements including an identifier, an entry location, and an exit location of the user device, which component can be, for example, a transceiver 810 and one or more processors 802 having dedicated hardware or an implementation medium 820 and / or executable code or software instructions (such as a completion response module 836) in a memory 804.

[0138] In this specification, reference to "one example," "example," "some examples," or "exemplary implementations" means that a particular feature, structure, or characteristic described in conjunction with a feature and / or example may be included in at least one feature and / or example of the claimed subject matter. Thus, the appearance of the phrases "in one example," "example," "some examples," or "in some implementations," or other similar phrases in various places throughout the specification do not necessarily refer to the same features, examples, and / or limitations. Furthermore, particular features, structures, or characteristics may be combined in one or more examples and / or features.

[0139] Some parts of the detailed description included herein are presented according to algorithms or symbolic representations of operations on binary digital signals stored in the memory of a specific device or a dedicated computing device or platform. In the context of this particular specification, the term "specific device" etc. includes a general-purpose computer, once it is programmed to perform specific operations according to instructions from program software. Algorithmic description or symbolic representation is an example of a technique used by a person of ordinary skill in signal processing or related technical fields to convey the essence of their work to other technicians in the field. Algorithms are here and generally considered to be self-consistent sequences of operations or similar signal processing that obtain desired results. In this context, operations or processing involve physical operations of physical quantities. Generally, although not necessarily, such quantities can take the form of electrical or magnetic signals that can be stored, transmitted, combined, compared or otherwise manipulated. It has been proven that sometimes, mainly for general reasons, it is convenient to refer to such signals as bits, data, values, elements, symbols, characters, terms, quantities, numbers, etc. However, it should be understood that all of these or similar terms are associated with appropriate physical quantities and are merely convenient labels. Unless otherwise specifically stated, as will be apparent from the discussion herein, it should be understood that discussions in this specification using terms such as "processing," "computing," "calculating," "determining," etc. refer to actions or processes of a specific device, such as a special-purpose computer, a special-purpose computing device, or a similar special-purpose electronic computing device. Thus, in the context of this specification, a special-purpose computer or a similar special-purpose electronic computing device is capable of manipulating or transforming signals, which are typically represented as physical electronic or magnetic quantities in a memory, register, or other information storage device, transmission device, or display device of the special-purpose computer or a similar special-purpose electronic computing device.

[0140] In the foregoing detailed description, numerous specific details have been set forth to provide a thorough understanding of the claimed subject matter. However, it will be appreciated by those skilled in the art that the claimed subject matter may be practiced without these specific details. In other instances, methods and apparatuses known to those skilled in the art have not been described in detail so as not to obscure the claimed subject matter.

[0141] As used herein, the terms "and," "or," and "and / or" may include multiple meanings, which are also expected to depend at least in part on the context in which the terms are used. In general, "or," if used in connection with a list such as A, B, or C, is intended to mean A, B, and C (used herein in an inclusive sense), as well as A, B, or C (used herein in an exclusive sense). Additionally, as used herein, the term "one or more" may be used to describe any feature, structure, or characteristic in the singular, or may be used to describe a plurality of features, structures, or characteristics, or some other combination thereof. It should be noted, however, that this is merely an illustrative example, and that claimed subject matter is not limited to this example.

[0142] While there has been shown and described what are presently considered to be exemplary features, it will be understood by those skilled in the art that various other modifications may be made, and equivalents may be substituted, without departing from the claimed subject matter. Additionally, many modifications may be made to adapt a particular situation to the teachings of the claimed subject matter without departing from the central concept described herein.

[0143] Implementation examples are described in the following numbered clauses:

[0144] 1. A method for performing information exchange for a transportation service by a user device, the method comprising:

[0145] wirelessly sending a transport request message to a transport entity, the transport request message including one or more message information elements including an identifier of the user device and a requested destination;

[0146] wirelessly receiving a shipping response message from a shipping entity, the shipping response message including one or more message information elements including an acceptance or a rejection of the shipping request message; and

[0147] In response to acceptance in the transport response message, a transport confirmation message is wirelessly sent to the transport entity, the transport confirmation message including one or more message information elements including an identifier of the user device.

[0148] 2. A method according to clause 1, wherein the transport request message, the transport response message and the transport confirmation message are dedicated messages in a device-to-device (D2D) communication link, and the device-to-device (D2D) communication link includes one or more of dedicated short range communication (DSRC), cellular vehicle-to-everything (C-V2X) communication or 5G new radio (NR) communication.

[0149] 3. A method according to clause 1, wherein the transport request message, the transport response message, and the transport confirmation message are encapsulated in a data payload in a device-to-device (D2D) communication link, the device-to-device (D2D) communication link including one or more of dedicated short range communication (DSRC), cellular vehicle-to-everything (C-V2X) communication, or 5G new radio (NR) communication.

[0150] 4. A method according to any one of clauses 1 to 3, wherein one or more message information elements in the transport request message also include at least one of the requested transport equipment type, the number of users, the validity period of the transport request message, the maximum travel time, or the required destination arrival time, or a combination thereof.

[0151] 5. A method according to any one of clauses 1 to 4, wherein one or more message information elements in the transportation request message also include at least one of user type, willingness to share a transportation vehicle, maximum fare, requested departure time, beacon proximity threshold, or a combination thereof.

[0152] 6. A method according to any of clauses 1 to 5, wherein one or more message information elements in the transport response message also include at least one of the transport type, the transport identifier, the fare, an indication of whether the transport is shared or individual, the estimated arrival time for the pick-up and the estimated arrival time at the destination, or a combination thereof.

[0153] 7. A method according to any of clauses 1 to 6, wherein the one or more message information elements in the transportation confirmation message further include at least one of a requested destination and an estimated arrival time of the pick-up, or a combination thereof.

[0154] 8. The method according to any one of clauses 1 to 7, further comprising:

[0155] wirelessly sending a transport status request message to a transport entity, the transport status request message including one or more message information elements containing a query for information related to the current location; and

[0156] A transport status message is wirelessly received from a transport entity, the transport status message including one or more message information elements including information related to the current location.

[0157] 9. The method of clause 8, further comprising using information related to the current location to determine an arrival estimate for the requested destination.

[0158] 10. The method according to any one of clauses 1 to 9, further comprising:

[0159] wirelessly sending a transport status request message to a transport entity, the transport status request message comprising one or more message information elements including an identifier of the user equipment, a query for information related to an arrival estimate for the requested destination; and

[0160] A transport status message is wirelessly received from a transport entity, the transport status message including one or more message information elements including an arrival estimate for a destination.

[0161] 11. The method of clause 10, wherein the arrival estimate of the destination comprises one or more of an estimated arrival time to the destination and an estimated number of stops to the destination.

[0162] 12. The method of clause 10, wherein the one or more message information elements in the transport status message further include a destination of a transport vehicle that is closest to the requested destination.

[0163] 13. The method according to any one of clauses 1 to 12, further comprising:

[0164] wirelessly sending a transport completion request message to a transport entity, the transport completion request message including one or more message information elements including an identifier of the user device and a de-boarding request;

[0165] A transport completion confirmation message is wirelessly received from the transport entity, the transport completion confirmation message including one or more message information elements including an arrival estimate of the destination and a confirmation of the drop-off request.

[0166] 14. The method according to clause 13, further comprising:

[0167] A transport completion response message is wirelessly received from a transport entity, the transport completion response message including one or more message information elements including an identifier of the user equipment, an entry location, and an exit location.

[0168] 15. The method of clause 14, wherein the transport completion response message further comprises one or more message information elements including at least one of a fare and a request to provide a periodic signal to verify that the user device has left the transport vehicle.

[0169] 16. The method according to any one of clauses 1 to 15, wherein the transportation entity comprises a transportation vehicle, a transportation server, or both.

[0170] 17. A user device configured to perform information exchange for a transportation service, the user device comprising:

[0171] a wireless transceiver configured to communicate wirelessly with a transport entity;

[0172] at least one memory; and

[0173] at least one processor coupled to the wireless transceiver and to the at least one memory, the at least one processor being configured to:

[0174] sending, via the wireless transceiver, a transport request message to a transport entity, the transport request message comprising one or more message information elements including an identifier of the user device and a requested destination;

[0175] receiving, via the wireless transceiver, a shipping response message from a shipping entity, the shipping response message including one or more message information elements including an acceptance or a rejection of the shipping request message; and

[0176] In response to acceptance in the transport response message, a transport confirmation message is sent to the transport entity via the wireless transceiver, the transport confirmation message including one or more message information elements including an identifier of the user device.

[0177] 18. A user equipment according to clause 17, wherein the transport request message, the transport response message and the transport confirmation message are dedicated messages in a device-to-device (D2D) communication link, and the device-to-device (D2D) communication link includes one or more of dedicated short range communication (DSRC), cellular vehicle-to-everything (C-V2X) communication or 5G new radio (NR) communication.

[0178] 19. A user device according to clause 17, wherein the transport request message, the transport response message and the transport confirmation message are encapsulated in a data payload in a device-to-device (D2D) communication link, the device-to-device (D2D) communication link comprising one or more of dedicated short range communication (DSRC), cellular vehicle-to-everything (C-V2X) communication or 5G new radio (NR) communication.

[0179] 20. A user device according to any one of clauses 17 to 19, wherein one or more message information elements in the transport request message further include at least one of the requested transport equipment type, the number of users, the validity period of the transport request message, the maximum travel time or the required destination arrival time or a combination thereof.

[0180] 21. A user device according to any one of clauses 17 to 20, wherein one or more message information elements in the transport request message further include at least one of a user type, a willingness to share a transport vehicle, a maximum fare, a requested departure time, a beacon proximity threshold, or a combination thereof.

[0181] 22. A user device according to any of clauses 17 to 21, wherein one or more message information elements in the transport response message also include at least one of the transport type, the transport identifier, the fare, an indication of whether the transport is shared or individual, the estimated arrival time for the pick-up and the estimated arrival time at the destination, or a combination thereof.

[0182] 23. A user device according to any of clauses 17 to 22, wherein the one or more message information elements in the transport confirmation message further include at least one of a requested destination and an estimated arrival time of the pick-up, or a combination thereof.

[0183] 24. A user equipment according to any one of clauses 17 to 23, wherein at least one processor is further configured to:

[0184] sending, via the wireless transceiver, a transport status request message to a transport entity, the transport status request message including one or more message information elements containing a query for information related to the current location; and

[0185] A transport status message is received from a transport entity via a wireless transceiver, the transport status message including one or more message information elements containing information related to the current location.

[0186] 25. User equipment according to clause 24, wherein the at least one processor is further configured to use information related to the current location to determine an arrival estimate for the requested destination.

[0187] 26. A user equipment according to any one of clauses 17 to 25, wherein at least one processor is further configured to:

[0188] sending, via the wireless transceiver, a transport status request message to a transport entity, the transport status request message comprising one or more message information elements including an identifier of the user equipment, a query for information related to an arrival estimate for the requested destination; and

[0189] A transport status message is received from a transport entity via a wireless transceiver, the transport status message including one or more message information elements including an arrival estimate for a destination.

[0190] 27. User equipment according to clause 26, wherein the arrival estimate of the destination comprises one or more of an estimated arrival time to the destination and an estimated number of sites to the destination.

[0191] 28. User equipment according to clause 26, wherein the one or more message information elements in the transport status message further comprises a destination of a transport vehicle closest to the requested destination.

[0192] 29. A user equipment according to any one of clauses 17 to 28, wherein at least one processor is further configured to:

[0193] sending, via the wireless transceiver, a transport completion request message to a transport entity, the transport completion request message including one or more message information elements including an identifier of the user device and a request to get off the vehicle;

[0194] A transport completion confirmation message is received from the transport entity via the wireless transceiver, the transport completion confirmation message including one or more message information elements including an arrival estimate of the destination and a confirmation of the drop-off request.

[0195] 30. A user equipment according to clause 29, wherein at least one processor is further configured to:

[0196] A transport completion response message is received from the transport entity via the wireless transceiver, the transport completion response message including one or more message information elements including an identifier of the user equipment, an entry location, and an exit location.

[0197] 31. The user device of clause 30, wherein the transport completion response message further comprises one or more message information elements including at least one of a fare and a request to provide a periodic signal to verify that the user device has left the transport vehicle.

[0198] 32. The user equipment according to any one of clauses 17 to 31, wherein the transportation entity comprises a transportation vehicle, a transportation server, or both.

[0199] 33. A user device configured to perform information exchange for a transportation service, comprising:

[0200] means for wirelessly sending a transport request message to a transport entity, the transport entity comprising one or both of a transport vehicle and a transport server, the transport request message comprising one or more message information elements including an identifier of a user device and a requested destination;

[0201] means for wirelessly receiving a shipping response message from a shipping entity, the shipping response message comprising one or more message information elements containing an acceptance or a rejection of the shipping request message; and

[0202] Means for wirelessly sending a shipping confirmation message to a shipping entity in response to acceptance in the shipping response message, the shipping confirmation message including one or more message information elements including an identifier of the user equipment.

[0203] 34. A non-transitory storage medium comprising program code stored thereon, the program code being operable to configure at least one processor in a user device to perform information exchange for a transportation service, comprising:

[0204] program code for wirelessly transmitting a transportation request message to a transportation entity, the transportation entity comprising one or both of a transportation vehicle and a transportation server, the transportation request message comprising one or more message information elements including an identifier of a user device and a requested destination;

[0205] program code for wirelessly receiving a shipping response message from a shipping entity, the shipping response message including one or more message information elements containing an acceptance or a rejection of the shipping request message; and

[0206] Program code for wirelessly sending a shipping confirmation message to a shipping entity in response to acceptance in a shipping response message, the shipping confirmation message including one or more message information elements including an identifier of the user device.

[0207] 35. A method for performing information exchange for transportation services by a transportation entity, the method comprising:

[0208] wirelessly receiving a transport request message from a user device, the transport request message comprising one or more message information elements including an identifier of the user device and a requested destination;

[0209] wirelessly sending a transport response message to the user equipment, the transport response message including one or more message information elements containing an acceptance or a rejection of the transport request message; and

[0210] In response to acceptance in the shipping response message, a shipping confirmation message is wirelessly received from the user device, the shipping confirmation message including one or more message information elements including an identifier of the user device.

[0211] 36. A method according to clause 35, wherein the transport request message, the transport response message and the transport confirmation message are dedicated messages in a device-to-device (D2D) communication link, and the device-to-device (D2D) communication link includes one or more of dedicated short range communication (DSRC), cellular vehicle-to-everything (C-V2X) communication or 5G new radio (NR) communication.

[0212] 37. A method according to clause 35, wherein the transport request message, the transport response message, and the transport confirmation message are encapsulated in a data payload in a device-to-device (D2D) communication link, the device-to-device (D2D) communication link including one or more of dedicated short range communication (DSRC), cellular vehicle-to-everything (C-V2X) communication, or 5G new radio (NR) communication.

[0213] 38. A method according to any one of clauses 35 to 37, wherein one or more message information elements in the transport request message also include at least one of the requested transport equipment type, the number of users, the validity period of the transport request message, the maximum travel time, or the required destination arrival time, or a combination thereof.

[0214] 39. A method according to any one of clauses 35 to 38, wherein one or more message information elements in the transportation request message also include at least one of user type, willingness to share a transportation vehicle, maximum fare, requested departure time, beacon proximity threshold, or a combination thereof.

[0215] 40. A method according to any of clauses 35 to 39, wherein one or more message information elements in the transport response message also include at least one of the transport type, the transport identifier, the fare, an indication of whether the transport is shared or individual, the estimated arrival time for the pick-up and the estimated arrival time at the destination, or a combination thereof.

[0216] 41. A method according to any one of clauses 35 to 40, wherein the one or more message information elements in the transportation confirmation message further include at least one of a requested destination and an estimated arrival time of the pick-up, or a combination thereof.

[0217] 42. The method according to any one of clauses 35 to 41, further comprising:

[0218] wirelessly receiving a transport status request message from a user device, the transport status request message comprising one or more message information elements containing a query for information related to a current location; and

[0219] A transport status message is wirelessly transmitted to the user device, the transport status message including one or more message information elements containing information related to the current location.

[0220] 43. The method according to any one of clauses 35 to 42, further comprising:

[0221] wirelessly receiving a transport status request message from a user device, the transport status request message comprising one or more message information elements including an identifier of the user device, a query for information related to an arrival estimate for a requested destination; and

[0222] A transport status message is wirelessly transmitted to the user equipment, the transport status message including one or more message information elements including an arrival estimate of the destination.

[0223] 44. The method of clause 43, wherein the arrival estimate of the destination comprises one or more of an estimated arrival time at the destination and an estimated number of stops at the destination.

[0224] 45. The method of clause 43, wherein the one or more message information elements in the transport status message further include a destination of a transport vehicle that is closest to the requested destination.

[0225] 46. ​​The method according to any one of clauses 35 to 45, further comprising:

[0226] wirelessly receiving a transport completion request message from a user device, the transport completion request message comprising one or more message information elements including an identifier of the user device and a drop-off request;

[0227] A transport completion confirmation message is wirelessly transmitted to the user device, the transport completion confirmation message including one or more message information elements including an arrival estimate of the destination and a confirmation of the drop-off request.

[0228] 47. The method according to clause 46, further comprising:

[0229] A transport completion response message is wirelessly transmitted to the user equipment, the transport completion response message including one or more message information elements including an identifier of the user equipment, an entry location, and an exit location.

[0230] 48. The method of clause 47, wherein the transport completion response message further comprises one or more message information elements including at least one of a fare and a request to provide a periodic signal to verify that the user device has left the transport vehicle.

[0231] 49. The method according to any one of clauses 35 to 48, wherein the transportation entity comprises a transportation vehicle, a transportation server, or both.

[0232] 50. A transportation entity configured to perform information exchange for transportation services, the transportation entity comprising one of a transportation vehicle and a transportation server, the transportation entity comprising:

[0233] a wireless transceiver configured to communicate wirelessly with a user device;

[0234] at least one memory; and

[0235] at least one processor coupled to the wireless transceiver and to the at least one memory, the at least one processor being configured to:

[0236] receiving, via the wireless transceiver, a transport request message from a user device, the transport request message comprising one or more message information elements including an identifier of the user device and a requested destination;

[0237] sending, via the wireless transceiver, a transport response message to the user device, the transport response message including one or more message information elements containing an acceptance or a rejection of the transport request message; and

[0238] In response to the acceptance in the shipping response message, a shipping confirmation message is received from the user device via the wireless transceiver, the shipping confirmation message including one or more message information elements including an identifier of the user device.

[0239] 51. A transport entity according to clause 50, wherein the transport request message, the transport response message and the transport confirmation message are dedicated messages in a device-to-device (D2D) communication link, and the device-to-device (D2D) communication link includes one or more of dedicated short range communication (DSRC), cellular vehicle-to-everything (C-V2X) communication or 5G new radio (NR) communication.

[0240] 52. A transport entity according to clause 50, wherein the transport request message, the transport response message, and the transport confirmation message are encapsulated in a data payload in a device-to-device (D2D) communication link, the device-to-device (D2D) communication link comprising one or more of dedicated short range communication (DSRC), cellular vehicle-to-everything (C-V2X) communication, or 5G new radio (NR) communication.

[0241] 53. A transport entity according to any one of clauses 50 to 52, wherein one or more message information elements in the transport request message further include at least one of the requested type of transport equipment, the number of users, the validity period of the transport request message, the maximum travel time or the required destination arrival time or a combination thereof.

[0242] 54. A transportation entity according to any of clauses 50 to 53, wherein one or more message information elements in the transportation request message also include at least one of user type, willingness to share a transportation vehicle, maximum fare, requested departure time, beacon proximity threshold, or a combination thereof.

[0243] 55. A transportation entity according to any of clauses 50 to 54, wherein one or more message information elements in the transportation response message also include at least one of the transportation type, the transportation identifier, the fare, an indication of whether the transportation is shared or individual, the estimated arrival time for the pick-up and the estimated arrival time at the destination, or a combination thereof.

[0244] 56. A transport entity according to any one of clauses 50 to 55, wherein the one or more message information elements in the transport confirmation message further include at least one of a requested destination and an estimated arrival time of the pick-up, or a combination thereof.

[0245] 57. A transport entity according to any one of clauses 50 to 26, wherein at least one processor is further configured to:

[0246] receiving, via the wireless transceiver, a transport status request message from a user device, the transport status request message comprising one or more message information elements containing a query for information related to a current location; and

[0247] A transport status message is sent to the user device via the wireless transceiver, the transport status message including one or more message information elements containing information related to the current location.

[0248] 58. A transport entity according to any one of clauses 50 to 57, wherein at least one processor is further configured to:

[0249] receiving, via the wireless transceiver, a transport status request message from a user device, the transport status request message comprising one or more message information elements including an identifier of the user device, a query for information related to an arrival estimate for a requested destination; and

[0250] A transport status message is sent to the user equipment via the wireless transceiver, the transport status message including one or more message information elements including an arrival estimate for the destination.

[0251] 59. The transportation entity of clause 58, wherein the arrival estimate for the destination comprises one or more of an estimated arrival time at the destination and an estimated number of stops at the destination.

[0252] 60. A transport entity according to clause 58, wherein the one or more message information elements in the transport status message further include a destination of a transport vehicle that is closest to the requested destination.

[0253] 61. A transport entity according to any one of clauses 50 to 60, wherein at least one processor is further configured to:

[0254] receiving, via the wireless transceiver, a transport completion request message from a user device, the transport completion request message comprising one or more message information elements including an identifier of the user device and a drop-off request;

[0255] A transport completion confirmation message is sent to the user device via the wireless transceiver, the transport completion confirmation message including one or more message information elements including an arrival estimate of the destination and a confirmation of the drop-off request.

[0256] 62. The transport entity of clause 61, wherein the at least one processor is further configured to:

[0257] A transport completion response message is sent to the user equipment via the wireless transceiver, the transport completion response message including one or more message information elements including an identifier of the user equipment, an entry location, and an exit location.

[0258] 63. A transportation entity according to clause 62, wherein the transportation completion response message further comprises one or more message information elements including at least one of a fare and a request to provide a periodic signal to verify that the user device has left the transportation vehicle.

[0259] 64. A transportation entity according to any one of clauses 50 to 63, wherein the transportation entity comprises a transportation vehicle, a transportation server, or both.

[0260] 65. A transportation entity configured to perform information exchange for transportation services, the transportation entity comprising:

[0261] means for wirelessly receiving a transport request message from a user device, the transport request message comprising one or more message information elements including an identifier of the user device and a requested destination;

[0262] means for wirelessly transmitting a transport response message to a user device, the transport response message comprising one or more message information elements containing an acceptance or a rejection of the transport request message; and

[0263] Means for wirelessly receiving a shipping confirmation message from the user device in response to acceptance in the shipping response message, the shipping confirmation message including one or more message information elements including an identifier of the user device.

[0264] 66. A non-transitory storage medium comprising program code stored thereon, the program code being operable to configure at least one processor in a transportation entity to perform information exchange for a transportation service, the non-transitory storage medium comprising:

[0265] program code for wirelessly receiving a transport request message from a user device, the transport request message comprising one or more message information elements including an identifier of the user device and a requested destination;

[0266] program code for wirelessly transmitting a transport response message to a user device, the transport response message including one or more message information elements containing an acceptance or a rejection of the transport request message; and

[0267] Program code for wirelessly receiving a shipping confirmation message from a user device in response to an acceptance in a shipping response message, the shipping confirmation message including one or more message information elements including an identifier of the user device.

[0268] Therefore, it is intended that the claimed subject matter not be limited to the particular examples disclosed, but that such claimed subject matter may also include all aspects falling within the scope of the appended claims and their equivalents.

Claims

1. A method for performing information exchange for a transportation service by a user device, the method comprising: wirelessly sending a transport request message to a transport entity, the transport request message comprising one or more message information elements including an identifier of the user equipment and a requested destination; wirelessly receiving a transport response message from the transport entity, the transport response message including one or more message information elements including an acceptance or a rejection of the transport request message; in response to the acceptance in the transport response message, wirelessly sending a transport confirmation message to the transport entity, the transport confirmation message including one or more message information elements including an identifier of the user equipment; wirelessly sending a transport completion request message to the transport entity, wherein the transport completion request message includes one or more message information elements including an identifier of the user equipment and a drop-off request; and A transport completion response message is wirelessly received from the transport entity, wherein the transport completion response message includes one or more message information elements including a request to provide a periodic signal to verify that the user equipment has left a transport vehicle.

2. The method according to claim 1, wherein: The transport request message, the transport response message and the transport confirmation message are dedicated messages in a device-to-device (D2D) communication link, and the device-to-device (D2D) communication link includes one or more of dedicated short range communication (DSRC), cellular vehicle-to-everything (C-V2X) communication or 5G new radio (NR) communication.

3. The method according to claim 1, wherein: The transport request message, the transport response message, and the transport confirmation message are encapsulated in a data payload in a device-to-device (D2D) communication link, wherein the device-to-device (D2D) communication link includes one or more of dedicated short range communication (DSRC), cellular vehicle-to-everything (C-V2X) communication, or 5G new radio (NR) communication.

4. The method according to claim 1, wherein: The one or more message information elements in the transportation request message further include at least one of the requested transportation equipment type, the number of users, the validity period of the transportation request message, the maximum travel time, or the required destination arrival time, or a combination thereof.

5. The method according to claim 1, wherein: The one or more message information elements in the transportation request message further include at least one of a user type, willingness to share a transportation vehicle, a maximum fare, a requested departure time, a beacon proximity threshold, or a combination thereof.

6. The method according to claim 1, wherein: The one or more message information elements in the transportation response message also include at least one of a transportation type, a transportation identifier, a fare, an indication of whether the transportation is shared or individual, an estimated arrival time for pickup, and an estimated arrival time to the destination, or a combination thereof.

7. The method according to claim 1, wherein: The one or more message information elements in the transportation confirmation message also include at least one of the requested destination and an estimated arrival time of the pickup, or a combination thereof.

8. The method according to claim 1, further comprising: wirelessly sending a transport status request message to the transport entity, the transport status request message including one or more message information elements including a query for information related to a current location; as well as A transport status message is wirelessly received from the transport entity, the transport status message including one or more message information elements containing information related to the current location.

9. The method according to claim 8, further comprising: An arrival estimate for the requested destination is determined using information related to the current location.

10. The method according to claim 1, further comprising: wirelessly sending a transport status request message to the transport entity, the transport status request message comprising one or more message information elements including an identifier of the user equipment, a query for information related to an arrival estimate of the requested destination; as well as A transport status message is wirelessly received from the transport entity, the transport status message including one or more message information elements including an arrival estimate for the destination.

11. The method according to claim 10, wherein: The arrival estimate of the destination includes one or more of an estimated arrival time to the destination and an estimated number of stops to the destination.

12. The method according to claim 10, wherein: The one or more message information elements in the transport status message also include a destination of the transport vehicle that is closest to the requested destination.

13. The method according to claim 1, further comprising: A transport completion confirmation message is wirelessly received from the transport entity, the transport completion confirmation message including one or more message information elements including an arrival estimate of a destination and a confirmation of the drop-off request.

14. The method according to claim 13, wherein: The transport completion response message includes one or more message information elements including an identifier of the user device and at least one of an entry location, an exit location, and a fare.

15. The method according to claim 1, wherein: The transportation entity includes a transportation vehicle, a transportation server, or both.

16. A user device configured to perform information exchange for a transportation service, the user device comprising: a wireless transceiver configured to communicate wirelessly with a transport entity; at least one memory; as well as at least one processor coupled to the wireless transceiver and the at least one memory, the at least one processor being configured to: sending, via the wireless transceiver, a transport request message to the transport entity, the transport request message comprising one or more message information elements including an identifier of the user device and a requested destination; receiving, via the wireless transceiver, a transport response message from the transport entity, the transport response message comprising one or more message information elements including an acceptance or a rejection of the transport request message; in response to the acceptance in the transport response message, sending, via the wireless transceiver, a transport confirmation message to the transport entity, the transport confirmation message including one or more message information elements including an identifier of the user device; sending, via the wireless transceiver, a transport completion request message to the transport entity, wherein the transport completion request message includes one or more message information elements including an identifier of the user device and a drop-off request; and A transport completion response message is received from the transport entity via the wireless transceiver, wherein the transport completion response message includes one or more message information elements including a request to provide a periodic signal to verify that the user equipment has left a transport vehicle.

17. The user equipment according to claim 16, wherein: The transport request message, the transport response message and the transport confirmation message are dedicated messages in a device-to-device (D2D) communication link, and the device-to-device (D2D) communication link includes one or more of dedicated short range communication (DSRC), cellular vehicle-to-everything (C-V2X) communication or 5G new radio (NR) communication.

18. The user equipment according to claim 16, wherein: The transport request message, the transport response message, and the transport confirmation message are encapsulated in a data payload in a device-to-device (D2D) communication link, wherein the device-to-device (D2D) communication link includes one or more of dedicated short range communication (DSRC), cellular vehicle-to-everything (C-V2X) communication, or 5G new radio (NR) communication.

19. The user equipment according to claim 16, wherein: The one or more message information elements in the transportation request message further include at least one of the requested transportation equipment type, the number of users, the validity period of the transportation request message, the maximum travel time, or the required destination arrival time, or a combination thereof.

20. The user equipment according to claim 16, wherein: The one or more message information elements in the transportation request message further include at least one of a user type, willingness to share a transportation vehicle, a maximum fare, a requested departure time, a beacon proximity threshold, or a combination thereof.

21. The user equipment according to claim 16, wherein: The one or more message information elements in the transportation response message also include at least one of a transportation type, a transportation identifier, a fare, an indication of whether the transportation is shared or individual, an estimated arrival time for pickup, and an estimated arrival time to the destination, or a combination thereof.

22. The user equipment according to claim 16, wherein: The one or more message information elements in the transportation confirmation message also include at least one of the requested destination and an estimated arrival time of the pickup, or a combination thereof.

23. The user equipment according to claim 16, wherein: The at least one processor is further configured to: sending, via the wireless transceiver, a transport status request message to the transport entity, the transport status request message comprising one or more message information elements including a query for information related to a current location; as well as A transport status message is received from the transport entity via the wireless transceiver, the transport status message comprising one or more message information elements including information related to the current location.

24. The user equipment according to claim 23, wherein: The at least one processor is further configured to determine an arrival estimate for the requested destination using information related to the current location.

25. The user equipment according to claim 16, wherein: The at least one processor is further configured to: sending, via the wireless transceiver, a transport status request message to the transport entity, the transport status request message comprising one or more message information elements including an identifier of the user equipment, a query for information related to an arrival estimate of the requested destination; as well as A transport status message is received from the transport entity via the wireless transceiver, the transport status message comprising one or more message information elements including an arrival estimate for the destination.

26. The user equipment according to claim 25, wherein: The arrival estimate of the destination includes one or more of an estimated arrival time to the destination and an estimated number of stops to the destination.

27. The user equipment according to claim 25, wherein: The one or more message information elements in the transport status message also include a destination of the transport vehicle that is closest to the requested destination.

28. The user equipment according to claim 16, wherein: The at least one processor is further configured to: A transport completion confirmation message is received from the transport entity via the wireless transceiver, the transport completion confirmation message comprising one or more message information elements including an arrival estimate of a destination and a confirmation of the drop-off request.

29. The user equipment according to claim 28, wherein: The transport completion response message includes one or more message information elements including an identifier of the user device and at least one of an entry location, an exit location, and a fare.

30. The user equipment according to claim 16, wherein: The transportation entity includes a transportation vehicle, a transportation server, or both.

31. A user device configured to perform information exchange for a transportation service, comprising: means for wirelessly sending a transport request message to a transport entity, the transport request message comprising one or more message information elements including an identifier of the user equipment and a requested destination; means for wirelessly receiving a transport response message from the transport entity, the transport response message comprising one or more message information elements containing an acceptance or a rejection of the transport request message; means for wirelessly sending a transport confirmation message to the transport entity in response to the acceptance in the transport response message, the transport confirmation message including one or more message information elements including an identifier of the user equipment; means for wirelessly sending a transport completion request message to the transport entity, wherein the transport completion request message comprises one or more message information elements including an identifier of the user equipment and a drop-off request; and Means for wirelessly receiving a transport completion response message from the transport entity, wherein the transport completion response message includes one or more message information elements including a request to provide a periodic signal to verify that the user equipment has left a transport vehicle.

32. A non-transitory storage medium comprising program code stored thereon, the program code being operable to configure at least one processor in a user device to perform information exchange for a transportation service, comprising: program code for wirelessly sending a transport request message to a transport entity, the transport request message including one or more message information elements including an identifier of the user device and a requested destination; program code for wirelessly receiving a shipping response message from the shipping entity, the shipping response message including one or more message information elements containing an acceptance or a rejection of the shipping request message; program code for wirelessly transmitting a shipping confirmation message to the shipping entity in response to the acceptance in the shipping response message, the shipping confirmation message including one or more message information elements including an identifier of the user device; program code for wirelessly transmitting a transport completion request message to the transport entity, wherein the transport completion request message includes one or more message information elements including an identifier of the user device and a drop-off request; and Program code for wirelessly receiving a transport completion response message from the transport entity, wherein the transport completion response message includes one or more message information elements including a request to provide a periodic signal to verify that the user equipment has left a transport vehicle.

Images