Apparatus, method, medium and computer program product for assisting vehicle valve
Patent Information
- Application Number
- CN202380029311.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-30
- Filing Date
- 2023-03-27
- Publication Date
- 2024-11-12
AI Technical Summary
The transportation system of the ferry terminal cannot realize the interconnection between vehicles and shore-side equipment, resulting in low efficiency of security inspection, toll collection and other services, and the inability to provide automated dynamic loading services, resulting in long waiting times for vehicles and poor utilization of in-cabin parking space.
Through message interaction between server equipment, shore-side equipment and ferry-side equipment, vehicle ferry auxiliary information is obtained and generated, and provided to vehicles and related equipment, realizing real-time acquisition and processing of vehicle information and optimizing the ferry service process.
It improves the service efficiency and quality of vehicle ferries, reduces vehicle waiting time, improves terminal operation efficiency and revenue, and enhances the utilization of parking space.
Smart Images

Figure CN118947147A_ABST
Abstract
Description
Apparatus, method, medium and computer program product for assisting vehicle ferries
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to Chinese Patent Application No. 202210327097.1 filed on March 30, 2022, the entirety of which is incorporated herein by reference. Technical Field
[0003] The present disclosure relates to the field of vehicle ferries, and more particularly, to apparatus and methods for assisting vehicle ferries. Background Art
[0004] Vehicle ferries include inland river ferries and cross-sea ferries. Ferry types range from small ferries with a single parking deck to large, multi-deck passenger and vehicle ferries. Compared to bridges and tunnels, small ferries have shorter construction periods and lower construction costs, allowing for rapid deployment of transport capacity, making them an important mode of cross-river transportation. Large passenger and vehicle ferries are dual-purpose vessels connecting islands with the mainland, primarily used to transport trucks, cars, container trailers, and tourists, and provide onboard accommodation and entertainment services.
[0005] Vehicle ferry terminals include small ferry terminals and large passenger and cargo roll-on / roll-off terminals. A roll-on / roll-off terminal is a large ferry terminal with functional areas encompassing waterways, turning areas, and other water areas; land areas such as the security inspection hall, pre- and post-inspection parking lots, vehicle waiting areas, and passenger embarkation and disembarkation areas at the terminal; as well as the port gate and passenger terminal. It serves both inbound and outbound vehicles and passengers. A roll-on / roll-off terminal is a complex and dynamic logistics and road traffic system. Limited by functional area layout and traffic organization, it may face issues such as ferry safety, long wait times, and low traffic efficiency due to crowded crowds, vehicle congestion, and the carrying of dangerous goods.
[0006] Summary of the Invention
[0007] A brief overview of the present disclosure is provided below to provide a basic understanding of some aspects of the present disclosure. However, it should be understood that this overview is not an exhaustive overview of the present disclosure. It is not intended to identify key or important parts of the present disclosure, nor is it intended to limit the scope of the present disclosure. Its purpose is simply to present certain concepts of the present disclosure in a simplified form as a prelude to the more detailed description that will be given later.
[0008] The ferry terminal transportation system known to the inventors of this application is a closed internal system that lacks interoperability with ferry vehicles, and therefore cannot provide these vehicles with improved security, toll collection, parking, and other services. Furthermore, the ferry terminal transportation system cannot obtain vehicle information in a timely manner to provide automated dynamic loading services for ferries. Manual loading results in a large workload, low efficiency, and long waiting times for vehicles, while also failing to achieve optimal utilization of onboard parking space.
[0009] In view of one or more of the above problems, the present disclosure provides a mechanism for assisting vehicle ferries, so that ferry vehicles can interact with ferry-related equipment such as shore-side equipment set up at the ferry terminal and ferry-side equipment set up on the ferry, thereby improving the service efficiency and service quality of vehicle ferries.
[0010] According to one aspect of the present disclosure, a server-side electronic device is provided. The electronic device may include a processing circuit configured to: obtain vehicle information of a first vehicle performing a ferry; obtain ferry-related information from a ferry-related device; generate vehicle ferry auxiliary information based on the vehicle information of the first vehicle and the ferry-related information; and provide the vehicle ferry auxiliary information to at least one of the first vehicle and the ferry-related device.
[0011] According to another aspect of the present disclosure, a shore-side device disposed at a ferry terminal is provided. The shore-side device may include a processing circuit configured to: obtain vehicle information of a vehicle undergoing a ferry; obtain shore-side information related to the ferry terminal; generate vehicle ferry auxiliary information based on the vehicle information and the shore-side information; and provide the vehicle ferry auxiliary information to the vehicle.
[0012] According to another aspect of the present disclosure, a ferry-side device provided on a ferry is provided. The ferry-side device may include a processing circuit configured to: obtain vehicle information of a first vehicle boarding the ferry; obtain ferry information related to the ferry; generate vehicle ferry auxiliary information based on the vehicle information of the first vehicle and the ferry information; and provide the vehicle ferry auxiliary information to the first vehicle.
[0013] According to another aspect of the present disclosure, an electronic device for a vehicle is provided. The electronic device may include a processing circuit configured to: in response to control information from a server device or a ferry-related device, provide the vehicle-linked specified vehicle information to the server device so that the server device or the ferry-related device generates vehicle ferry assistance information; and obtain the vehicle ferry assistance information from the server device or the ferry-related device to assist the vehicle in ferrying.
[0014] According to another aspect of the present disclosure, a communication method for a server device is provided. The method may include: obtaining vehicle information of a vehicle performing a ferry; obtaining ferry-related information from a ferry-related device; generating vehicle ferry auxiliary information based on the vehicle information of the vehicle and the ferry-related information; and providing the vehicle ferry auxiliary information to at least one of the vehicle and the ferry-related device.
[0015] According to another aspect of the present disclosure, a communication method for shore-side equipment provided at a ferry terminal is provided. The method may include: obtaining vehicle information of a vehicle undergoing a ferry; obtaining shore-side information related to the ferry terminal; generating vehicle ferry auxiliary information based on the vehicle information and the shore-side information; and providing the vehicle ferry auxiliary information to the vehicle.
[0016] According to another aspect of the present disclosure, a communication method for a ferry-side device provided on a ferry is provided. The method may include: obtaining vehicle information of a vehicle boarding the ferry; obtaining ferry information related to the ferry; generating vehicle ferry auxiliary information based on the vehicle information and the ferry information; and providing the vehicle ferry auxiliary information to the vehicle.
[0017] According to another aspect of the present disclosure, a communication method for a vehicle is provided. The method may include: providing vehicle information of the vehicle to the server device in response to control information from a server device or a ferry-related device, so that the server device or the ferry-related device generates vehicle ferry assistance information; and obtaining the vehicle ferry assistance information from the server device or the ferry-related device to assist the vehicle in ferrying.
[0018] According to another aspect of the present disclosure, a computer-readable storage medium is provided, comprising executable instructions. When the executable instructions are executed by an information processing device, the information processing device is caused to perform the communication method according to the present disclosure.
[0019] According to another aspect of the present disclosure, a computer program product is provided, comprising a computer program, wherein when the computer program is executed by a processor, the processor is caused to perform the communication method according to the present disclosure.
[0020] According to one or more embodiments of the present disclosure, a mechanism for assisting vehicle ferries is provided, which enables ferry vehicles to exchange messages with ferry-related equipment such as shore-side equipment set up at the ferry terminal and ferry-side equipment set up on the ferry, thereby improving the service efficiency and service quality of the vehicle ferry. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.
[0022] The present disclosure may be more clearly understood from the following detailed description with reference to the accompanying drawings, in which:
[0023] FIG1 is a schematic diagram illustrating a vehicle ferry scenario;
[0024] 2 is a block diagram illustrating an exemplary configuration of an electronic device for a server device side according to an embodiment of the present disclosure;
[0025] FIG3 is an exemplary flow chart illustrating a communication method for a server device side according to an embodiment of the present disclosure;
[0026] FIG4 is a schematic diagram illustrating message interaction in a vehicle ferry scenario 1 according to an embodiment of the present disclosure;
[0027] FIG5 is a schematic diagram illustrating message interaction in a vehicle ferry scenario 2 according to an embodiment of the present disclosure;
[0028] FIG6 is an exemplary flow chart illustrating vehicle-ferry collision warning according to an embodiment of the present disclosure;
[0029] FIG7 is a schematic diagram illustrating message interaction in a vehicle ferry scenario three according to an embodiment of the present disclosure;
[0030] FIG8 is an exemplary flowchart illustrating ferry vehicle loading and parking guidance according to an embodiment of the present disclosure;
[0031] FIG9 is a schematic diagram illustrating safe distances between different vehicles in ferry parking spaces according to an embodiment of the present disclosure;
[0032] FIG10 is an example showing parking of different types of vehicles based on fixed lanes and fixed parking spaces;
[0033] FIG11 is a schematic diagram illustrating a dynamically planned parking space distribution according to an embodiment of the present disclosure;
[0034] FIG12 is a schematic diagram showing the distribution of parking spaces after dynamic loading according to an embodiment of the present disclosure;
[0035] 13 is a block diagram showing an exemplary configuration of an electronic device for shore-side equipment provided at a ferry terminal according to an embodiment of the present disclosure;
[0036] FIG14 is an exemplary flow chart illustrating a communication method for shore-side equipment according to an embodiment of the present disclosure;
[0037] FIG15 is a schematic diagram illustrating message interaction in a vehicle ferry scenario 1 according to an embodiment of the present disclosure;
[0038] 16 is a block diagram showing an exemplary configuration of an electronic device for a ferry-side device provided on a ferry according to an embodiment of the present disclosure;
[0039] FIG17 is an exemplary flow chart illustrating a communication method for a ferry-side device according to an embodiment of the present disclosure;
[0040] FIG18 is a schematic diagram illustrating message interactions between vehicle ferry scenarios 2 and 3 according to an embodiment of the present disclosure;
[0041] FIG19 is a block diagram showing an exemplary configuration of an electronic device for a vehicle side according to an embodiment of the present disclosure;
[0042] FIG20 is an exemplary flowchart illustrating a communication method for a vehicle according to an embodiment of the present disclosure; and
[0043] FIG21 is a block diagram showing a first example of a schematic configuration of an RSU according to an embodiment of the present disclosure;
[0044] FIG22 is a block diagram showing a second example of a schematic configuration of an RSU according to an embodiment of the present disclosure;
[0045] FIG23 is a block diagram illustrating an example of a schematic configuration of a smartphone according to an embodiment of the present disclosure; and
[0046] FIG. 24 is a block diagram showing an example of a schematic configuration of a car navigation device according to an embodiment of the present disclosure. DETAILED DESCRIPTION
[0047] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that unless otherwise specifically stated, the relative arrangement of components and steps, numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present disclosure.
[0048] At the same time, it should be understood that for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.
[0049] The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the present disclosure, its application, or uses.
[0050] Technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the technologies, methods, and equipment should be considered part of the specification.
[0051] In all examples shown and discussed herein, any specific values should be interpreted as merely exemplary and not limiting. Therefore, other examples of the exemplary embodiments may have different values.
[0052] It should be noted that like reference numerals and letters refer to like items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.
[0053] Figure 1 shows three example scenarios for a vehicle ferry.
[0054] Scenario 1 corresponds to the scenario before the vehicle boards the ship, including, for example, vehicle ferry reservation, vehicle security inspection, weighing and charging, parking at the ferry waiting area, etc. As shown in FIG1 , the server device 100 can communicate with the vehicle 110 and / or the shore-side device 120 set up at the ferry terminal, thereby providing the vehicle 110 and / or the shore-side device 120 with corresponding vehicle ferry auxiliary information, such as the ferry reservation result of the vehicle 110, the security inspection result, weighing and charging information, and ferry waiting area guidance information, etc. The shore-side device 120 in Scenario 1 is, for example, set up in the security inspection hall, pre-inspection and post-inspection parking lots, vehicle waiting area, passenger boarding and disembarking area at the front of the terminal, and other land areas of the ferry terminal. Details of Scenario 1 will be described in detail with reference to FIG4 described later.
[0055] Furthermore, although FIG1 depicts a vehicle at a ferry terminal, in some embodiments, scenario 1 may also occur before vehicle 110 arrives at the ferry terminal. For example, in a scenario where the vehicle is making a ferry reservation, vehicle 110 may communicate with server device 100 in advance before traveling to the ferry terminal to make a ferry reservation.
[0056] Scenario 2 corresponds to the scenario where a vehicle embarks or disembarks from a ferry. As shown in FIG1 , when a vehicle embarks from a ferry 140, the server device 100 can communicate with the vehicle 110, the shore-side device 120 provided at the ferry terminal, and / or the ferry-side device 130 provided on the ferry, thereby providing the vehicle 110, the shore-side device 120 and / or the ferry-side device 130 with corresponding vehicle ferry auxiliary information, such as the risk of collision between the vehicle 110 and the ferry 140 (e.g., the ferry's gangway, guardrail, hatch, etc.), the risk of collision between the vehicle 110 and other vehicles, etc. The shore-side device 120 in scenario 2 is, for example, provided at a vehicle embarkation port, a vehicle disembarkation port, etc. Details of scenario 2 will be described in detail with reference to FIG5 described later.
[0057] Scenario 3 corresponds to the scenario after the vehicle has boarded the ferry. As shown in Figure 1, after the vehicle has boarded the ferry, the server device 100 can communicate with the vehicle 110 and / or the ferry-side device 130 located on the ferry, thereby providing the vehicle 110 and / or the ferry-side device 130 with corresponding vehicle ferry assistance information, such as parking guidance information for guiding the vehicle 110 to park within the cabin. In addition, although Scenario 3 is a scenario after the vehicle has boarded the ferry, the server device 100 and the vehicle 110 can also communicate with the shore-side device 120 located at the ferry terminal as needed to obtain or provide necessary information. Details of Scenario 3 will be described in detail with reference to Figure 7 below.
[0058] It should be understood that the installation positions and quantities of the shore-side equipment 120 and the ferry-side equipment 130 shown in FIG1 are merely examples, and any number of shore-side equipment 120 and ferry-side equipment 130 may be set according to actual needs.
[0059] In some embodiments, the server device 100 may be, for example, an Internet of Vehicles server device (e.g., an Internet of Vehicles central subsystem) that supports the Internet of Vehicles protocol. The vehicle 110 may be equipped with a communication unit, such as an on-board unit (OBU) based on the Internet of Vehicles communication protocol and / or a mobile smart terminal that carries the Internet of Vehicles communication protocol. In addition, the shore-side device 120 and the ferry-side device 130 may include a road-side device (RSU: Road Side Unit) based on the Internet of Vehicles protocol. Thus, the server device 100, the vehicle 110, the shore-side device 120, and the ferry-side device 130 may perform message interaction based on the Internet of Vehicles communication protocol (e.g., C-V2X (Cellular-Vehicle to everything)).
[0060] It should be understood that the above-mentioned message interaction based on the Internet of Vehicles communication protocol is only an example of the message interaction between the server device 100, vehicle 110, shore-side device 120 and ferry-side device 130 disclosed in the present invention. Those skilled in the art may also adopt other communication methods according to actual needs, as long as the message interaction between the above-mentioned devices can be realized.
[0061] In some embodiments, the vehicle 110, the shore-side equipment 120, and the ferry-side equipment 130 may each be provided with one or more sensors for sensing vehicle information, shore-side information related to the ferry terminal, and ferry information related to the ferry 140. Sensors may include, but are not limited to, radars (e.g., ultrasonic radars, millimeter-wave radars, lidars, etc.), cameras (e.g., still cameras, stereo cameras, high-definition cameras, etc.), vibration sensors, liquid / gas detection sensors, X-ray security scanners, weighbridges, etc. In addition, those skilled in the art may configure other types of sensors to sense the required information based on actual needs. In some embodiments, the required vehicle information, shore-side information, and ferry information may be obtained through multi-source heterogeneous sensor fusion perception.
[0062] In some embodiments, one or more of the server device 100, the shore-side device 120, and the ferry-side device 130 may include a computing device, such as a mobile edge computing (MEC) device, to provide computing capabilities.
[0063] 2 is a block diagram showing an exemplary configuration of an electronic device 200 for a server device according to an embodiment of the present disclosure. The server device may correspond to the server device 100 shown in FIG1 , for example.
[0064] In some embodiments, the electronic device 200 may include a processing circuit 210. The processing circuit 210 of the electronic device 200 provides various functions of the electronic device 200. In some embodiments, the processing circuit 210 of the electronic device 200 may be configured to execute a communication method for a server device.
[0065] Processing circuitry 210 may refer to various implementations of digital circuitry, analog circuitry, or mixed-signal (a combination of analog and digital) circuitry that perform functions in a computing system. Processing circuitry may include, for example, circuits such as integrated circuits (ICs), application-specific integrated circuits (ASICs), portions or circuits of a separate processor core, an entire processor core, a separate processor, a programmable hardware device such as a field programmable gate array (FPGA), and / or a system including multiple processors.
[0066] In some embodiments, the processing circuit 210 may include a vehicle information acquisition unit 220, a ferry-related information acquisition unit 230, a vehicle ferry auxiliary information generation unit 240, and a vehicle ferry auxiliary information providing unit 250, which are respectively configured to execute steps S310 to 340 in the communication method 300 for the server device shown in Figure 3 described later.
[0067] In some embodiments, the electronic device 200 may further include a memory (not shown). The memory of the electronic device 200 may store information generated by the processing circuit 210 and programs and data for the operation of the electronic device 210. The memory may be a volatile memory and / or a non-volatile memory. For example, the memory may include, but is not limited to, a random access memory (RAM), a dynamic random access memory (DRAM), a static random access memory (SRAM), a read-only memory (ROM), and a flash memory. In addition, the electronic device 200 may be implemented at the chip level, or may be implemented at the device level by including other external components.
[0068] Fig. 3 shows an exemplary flow chart of a communication method 300 for a server device according to an embodiment of the present disclosure. This communication method can be used, for example, in the electronic device 200 shown in Fig. 2 .
[0069] As shown in FIG3 , in step S310 , the vehicle information acquiring unit 220 acquires vehicle information of a first vehicle that is performing a ferry crossing. The first vehicle may correspond to the vehicle 110 in FIG1 , for example.
[0070] The vehicle information may include any vehicle information related to the ferry vehicle (e.g., vehicle 110). Table 1 below shows an exemplary vehicle information table, including a timestamp, basic vehicle information, extended vehicle information, and other information. The timestamp includes, for example, time information (e.g., the current time). Basic vehicle information may include, for example, vehicle position (e.g., latitude and longitude, altitude), vehicle orientation (e.g., vehicle head direction angle), vehicle body dimensions (e.g., length, width, and height), vehicle weight, vehicle type, and vehicle speed. Extended vehicle information may include, for example, chassis height information (e.g., chassis ground clearance), vehicle center of gravity information (e.g., center of gravity height, center of gravity distance from the front of the vehicle). Other information may include, for example, vehicle reservation information, vehicle license plate number, and other vehicle-related information. The vehicle information of the first vehicle obtained in step S310 may include, for example, one or more of the items in Table 1 below. It should be understood that the above-mentioned vehicle information is merely an example, and the vehicle information according to an embodiment of the present disclosure may also include other information about the vehicle.
[0071] Table 1: Vehicle information table
[0072] In step S320, the ferry-related information acquisition unit 230 acquires ferry-related information from the ferry-related equipment. The ferry-related equipment may correspond to, for example, the shore-side equipment 120 and / or the ferry-side equipment 130 in FIG. 1 , or other ferry-related equipment of the vehicle 110 .
[0073] In some embodiments, when the equipment related to the ferry includes shore-side equipment (e.g., shore-side equipment 120), the information related to the ferry may include, for example, shore-side information related to the ferry terminal. Table 2 below shows an exemplary shore-side information table, including timestamp, RSU identification information, and shore-side basic information. The timestamp includes, for example, time information (e.g., the current time). When the shore-side equipment includes an RSU, the RSU identification information is used to identify the RSU, and may include, for example, an RSU ID. The shore-side basic information may include, for example, ferry schedule information, security check information (e.g., security checkpoint number), weighing and charging information (e.g., weighing and charging point number), and waiting-for-ferry information.
[0074] Table 2: Shore side information table
[0075] In some embodiments, when the ferry-related equipment includes ferry-side equipment (e.g., ferry-side equipment 130), the ferry-related information may, for example, include ferry information related to the ferry (e.g., ferry 140). Table 3 below shows an exemplary ferry information table, including a timestamp, RSU identification information, basic ferry information, ferry embarkation and disembarkation ramp information, ferry parking environment information, ferry hydrological environment information, and ferry loading information. The timestamp may, for example, include time information (e.g., the current time). When the ferry-side equipment includes an RSU, the RSU identification information is used to identify the RSU and may, for example, include an RSU ID. Basic ferry information may, for example, include the ferry ID, ship tonnage, and boarding gate number. Embarkation and disembarkation ramp information may, for example, include ramp number, ramp width, ramp inclination angle, and ramp friction coefficient. Parking environment information may, for example, include parking deck number, parking deck size, parking deck friction coefficient, parking lane width, and parking safety distance. Hydrological environment information may include, for example, water surface visibility at the boarding gate, wind speed, wind force level, wind direction, wave height, horizontal sway amplitude of the ferry, and vertical sway amplitude of the ferry. Ferry loading information may include, for example, other ferry loading information besides the loading of vehicles on the ferry.
[0076] Table 3: Ferry Information
[0077] The ferry-related information acquired in step S320 may include, for example, one or more items in Table 2 and Table 3. It should be understood that the above ferry-related information is merely an example, and the ferry-related information according to an embodiment of the present disclosure may also include other ferry-related information.
[0078] The information acquired in steps S310 and S320 is also referred to herein as perception information. For example, the information may be acquired through perception by one or more sensors installed in the first vehicle or ferry-related equipment. Furthermore, the order of steps 310 and S320 is not particularly limited; S320 may be performed first and then S310, or they may be performed in parallel.
[0079] Next, in step S330, the vehicle ferry auxiliary information generation unit 240 generates vehicle ferry auxiliary information based on the vehicle information of the first vehicle acquired in step S310 and the ferry-related information acquired in step S320. The vehicle ferry auxiliary information is also referred to herein as service-related information and is used to assist vehicle ferrying.
[0080] In some embodiments, vehicle ferry auxiliary information may include shore-side service information. Table 4 below shows an exemplary shore-side service information table, including a timestamp, ferry reservation results, security check information, weighing and charging information, and ferry terminal guidance information. The timestamp may include, for example, time information (e.g., the current time). The ferry reservation results may include, for example, the scheduled ferry schedule and the vehicle license plate number. The security check results may include, for example, the vehicle security check results. The weighing and charging information may include, for example, the actual vehicle weight and the ferry fee. The ferry terminal guidance information may include, for example, the ferry terminal number, lane number, and parking space number.
[0081] Table 4: Shore-side service information table
[0082] In some embodiments, the vehicle ferry auxiliary information may include ferry-side service information. Table 5 below shows an exemplary ferry-side service information table, including timestamp, collision warning information, parking guidance information, and parking loading information. The timestamp includes, for example, time information (e.g., current time). The collision warning information includes, for example, vehicle vertical collision risk warning information (e.g., vertical plane collision risk warning information between the vehicle and the boarding and disembarking ramp, etc.), vehicle horizontal collision risk warning information (e.g., horizontal plane collision risk warning information between the vehicle and the guardrail / cabin, etc.), vehicle lateral drift risk warning information, and vehicle rollover risk warning information. The parking guidance information includes, for example, cabin information (e.g., cabin entry sequence number), boarding gate information (e.g., boarding gate number), deck information (e.g., deck number), lane information (e.g., lane number), parking space information (e.g., parking space number), parking space size, parking safety distance, vehicle roll amplitude, and lashing and fastening information (e.g., whether lashing and fastening are required). Parking loading information includes, for example, deck information (such as deck number), lane information (such as lane number, lane number, distance between lane centerline and ship centerline, lane safety width, lane length, number of lane parking spaces), parking space information (such as number of parking spaces), and vehicle license plate number.
[0083] Table 5: Ferry side service information table
[0084] The vehicle ferry assistance information generated in step S330 may include, for example, one or more items in Table 4 and Table 5. It should be understood that the above vehicle ferry assistance information is merely an example, and the vehicle ferry assistance information according to an embodiment of the present disclosure may also include other information for assisting vehicle ferries.
[0085] Next, in step S340 , the vehicle ferry auxiliary information providing unit 250 provides the vehicle ferry auxiliary information generated in step S330 to at least one of the first vehicle and the ferry-related device.
[0086] Therefore, through message interaction between the ferry vehicle and ferry-related equipment such as shore-side equipment installed at the ferry terminal and ferry-side equipment installed on the ferry, the ferry vehicle and ferry-related equipment can obtain vehicle ferry auxiliary information to assist the vehicle ferry, thereby improving the service efficiency and service quality of the vehicle ferry.
[0087] Next, an example of message interaction in vehicle ferry scenario 1 according to an embodiment of the present disclosure will be described with reference to FIG4 . Vehicle ferry scenario 1 corresponds to scenario 1 shown in FIG1 , and is a scenario before a vehicle embarks on board the ferry, including, for example, vehicle ferry reservation, vehicle security inspection, weighing and charging, and parking at the ferry terminal.
[0088] In this disclosure, the information link from the vehicle to the server device and the information link from the shore-side equipment / ferry-side equipment to the server device are referred to as "uplink," and the information link from the server device to the vehicle and the shore-side equipment / ferry-side equipment are referred to as "downlink." Furthermore, the information link from the shore-side equipment / ferry-side equipment to the vehicle is referred to as "downlink."
[0089] As shown in Figure 4 , server device 400 (corresponding to server device 100 in Figure 1 ) obtains vehicle information from the host vehicle (HV) (corresponding to vehicle 110 in Figure 1 ). Vehicle information may include, for example, at least one of the following: vehicle reservation information, vehicle location information, vehicle dimensions, and vehicle weight information shown in Table 1. It should be understood that HV 420 and HV 430 shown in Figure 4 correspond to two implementations of the same HV and are used to illustrate two message interaction modes for HVs later in this article.
[0090] In addition, the server device 400 obtains shore information from the shore device 410 (corresponding to the shore device 120 in FIG1 ). The shore information may include, for example, at least one of the ferry terminal's ferry schedule information, security information, weighing and charging information, and waiting area information shown in Table 2.
[0091] The server device 400 generates at least one of the HV's ferry reservation results, security inspection results, weighing and charging information, and ferry terminal guidance information based on the acquired vehicle information and shore information as vehicle ferry auxiliary information, and provides the vehicle ferry auxiliary information to at least one of the HV and the shore device 410.
[0092] Figure 4 provides two message interaction modes between the server device 400, the shore-side device 410 and the HV. In the first message interaction mode, HV corresponds to HV420, a mobile intelligent terminal that carries the Internet of Vehicles communication protocol. HV420 can provide vehicle information to the server device 400 via the Internet of Vehicles communication link, and obtain vehicle ferry auxiliary information from the server device 400 via the Internet of Vehicles communication link. In the second message interaction mode, HV corresponds to HV430, which includes an on-board OBU based on the Internet of Vehicles communication protocol. HV430 can provide vehicle information to the server device 400 via the Internet of Vehicles communication link. In addition, when the shore-side device 410 is equipped with an RSU based on the Internet of Vehicles communication protocol, the shore-side device 410 and HV430 can communicate directly based on the Internet of Vehicles communication link (such as a PC5 link). In this case, the server device 400 can send the vehicle ferry auxiliary information to the shore-side device 410, and the shore-side device 410 further sends the vehicle ferry auxiliary information to HV430. The above two message interaction modes can coexist, or one message interaction mode can be adopted as needed.
[0093] Next, taking the vehicle ferry security inspection scenario as an example, a specific example of message interaction in the vehicle ferry scenario 1 shown in FIG4 is described.
[0094] In this scenario, HV420 and / or HV430 provide vehicle information to the server device 400, such as vehicle location and vehicle type. In some embodiments, HV420 / 430 can determine the vehicle location (e.g., longitude and latitude) by, for example, GPS (Global Position System) and report it to the server device 400. In addition, HV420 / 430 can obtain and report vehicle type information, and vehicle types can include, for example, oversized transport trucks, ordinary large trucks, large passenger buses, small trucks, cars, etc. In addition, in some embodiments, the shore-side device 410 can also sense vehicle information and report the vehicle information to the server device 400. For example, the shore-side device 410 can include a high-definition camera for acquiring an image of the HV, determining the vehicle type based on the acquired image, and reporting it to the server device 400. In addition, the shore-side device 410 can also directly report the acquired image of the HV to the server device 400, and the server device determines the vehicle type based on the acquired image.
[0095] Shore-side equipment 410 provides shore-side information, such as security inspection information, to server equipment 400. In some embodiments, shore-side equipment 410 can utilize sensors for detecting flammable and explosive liquids and gases, X-ray security scanners, and high-definition cameras, among other hazardous materials, to provide security inspection information related to vehicle security inspections, such as intelligent identification of hazardous materials, through multi-source heterogeneous sensor fusion perception. This security inspection information can then be provided to the server equipment as shore-side information. In other embodiments, shore-side equipment 410 can also provide sensor-derived metadata (e.g., detection results from liquid and gas detection sensors, X-ray security scanners, and high-definition cameras) to server equipment 400, with server equipment 400 determining security inspection information based on the sensor metadata.
[0096] Based on the vehicle information and security inspection information, the server device 400 generates a security inspection result (e.g., whether the security inspection is passed) and provides it to the HV 420 and the shore-side device 410 as vehicle ferry auxiliary information, or provides it to the HV 430 via the shore-side device 410. This allows the HV to conveniently obtain the security inspection result, and the shore-side device 410 can determine whether to allow the HV to pass based on the security inspection result.
[0097] In this disclosure, the message interaction mechanism for the vehicle ferry scenario 1 shown in Figure 4 can be used to implement functions such as ferry reservations, intelligent identification of hazardous materials, vehicle weighing, automatic toll collection without stopping, and parking guidance at ferry terminals. This improves the efficiency of vehicle reservations, security checks, weighing, toll collection, and ferry waiting at ferry terminals, reduces waiting times, and enhances customer satisfaction. Furthermore, it can improve ferry turnover efficiency at ferry terminals, reduce operating costs, and increase revenue.
[0098] Next, an example of message exchange in vehicle ferry scenario 2 according to an embodiment of the present disclosure will be described with reference to FIG5 . Vehicle ferry scenario 2 corresponds to scenario 2 shown in FIG1 , for example, and involves vehicles boarding or disembarking a ferry. In FIG5 , components identical or similar to those in FIG4 are denoted by the same reference numerals, and duplicate descriptions thereof will be omitted.
[0099] 5 , the server device 400 obtains vehicle information from the HV 420 / 430. The vehicle information may include at least one of the vehicle position information, vehicle orientation information, vehicle size information, vehicle chassis height information, vehicle weight information, and vehicle speed information shown in Table 1.
[0100] In addition, the server device 400 obtains ferry information from the ferry-side device 500 (corresponding to the ferry-side device 130 in FIG. 1 ). The ferry information may include, for example, at least one of the information on the ferry's boarding and disembarking ramps, the information on the ferry's hydrological environment, and the information on the parking environment on the ferry, as shown in Table 3.
[0101] The server device 400 determines the collision risk between the HV and the ferry based on the acquired vehicle information and ferry information. In some embodiments, the server device 400 may also acquire vehicle information of other vehicles RV (Remote Vehicle) on the ferry, and determine the collision risk between the HV and the RV based on the vehicle information of the HV, the vehicle information of the RV, and the ferry information. In addition, in some embodiments, when the collision risk exceeds a pre-set collision risk threshold, the server device 400 may generate collision warning information and provide it to one or more of the HV, RV, and ferry-side devices 500 as vehicle ferry auxiliary information.
[0102] Figure 5 provides two message interaction modes between the server device 400, the ferry-side device 500, and the HV. In the first message interaction mode, the HV corresponds to the HV420, a mobile smart terminal that carries the vehicle networking communication protocol. The HV420 can provide vehicle information to the server device 400 via the vehicle networking communication link and obtain vehicle ferry auxiliary information from the server device 400 via the vehicle networking communication link. In the second message interaction mode, the HV corresponds to the HV430, which includes an on-board OBU based on the vehicle networking communication protocol. The HV430 can provide vehicle information to the server device 400 via the vehicle networking communication link. In addition, when the ferry-side device 500 is equipped with an RSU based on the vehicle networking communication protocol, the ferry-side device 500 and the HV430 can communicate directly based on the vehicle networking communication link (e.g., PC5 link). In this case, the server device 400 can send the vehicle ferry auxiliary information to the ferry-side device 500, and the ferry-side device 500 will further send the vehicle ferry auxiliary information to the HV430. The above two message interaction modes can coexist, or one message interaction mode can be adopted as needed.
[0103] Next, a specific example of a vehicle ferry collision warning (VFCW) will be described with reference to Figure 6. VFCW includes collision warnings when an HV is getting on or off a ferry and collision warnings when an HV is parked inside a cabin.
[0104] As shown in Figure 6, in step S600, the HV reports vehicle information such as vehicle position, chassis ground clearance, and vehicle weight to the server device. In some embodiments, the HV may report vehicle information to the server device periodically or in response to a control signal from the server device.
[0105] In step S610, the server performs scenario-based calculations based on the ferry information reported by the ferry-side device. Collision warnings can include, for example, collision warnings for HVs boarding or disembarking from a ferry and for HVs parking within a ship's cabin. Based on the vehicle position information reported by the HV, the server determines whether the HV is currently boarding or disembarking from a ferry or parking within a ship's cabin, and determines the collision risk accordingly.
[0106] Steps S620 - S640 correspond to the HV boarding and disembarking ferry scenario.
[0107] In step S620, the server device calculates the vertical plane collision risk between the HV and the ferry gangway. As shown in Figure 1, in scenario two, the HV is located on the ferry boarding gangway 150, and the gangway is generally tilted to the shore at an angle of 35° to 45°. When the HV boards the ship (the situation of disembarking is similar), due to the influence of sea waves, etc., there may be a vertical plane collision risk with the gangway (for example, the collision 160 between the HV chassis and the ferry gangway shown in Figure 1). In some embodiments, the server device can calculate the vertical plane collision risk between the HV and the ferry gangway in real time based on the vertical plane (Z-axis) sway amplitude of the ferry, the inclination angle of the ferry gangway, the height of the vehicle chassis from the ground, the vehicle speed, etc. Among them, the vertical plane (Z-axis) sway amplitude of the ferry, the inclination angle of the ferry gangway, and the height of the vehicle chassis from the ground are included in the ferry information reported by the ferry side device, and the vehicle speed is included in the vehicle information.
[0108] In step S630, server device calculates the horizontal plane collision risk of HV and ferry. In some cases, due to the influence of sea waves etc., when HV embarks or disembarks, HV may produce the collision risk and the risk of falling into the water on the horizontal plane with the entrance hatch, cabin, guardrail etc. of ferry (such as HV deviates from the gangway center line too much and may cause falling into the water). Server device can, for example, calculate the offset risk and the offset distance of vehicle and ferry gangway / door center line in real time according to ferry horizontal plane (XY axis) sway amplitude, gangway width, gangway friction coefficient, water surface wind speed, vehicle weight / size / direction angle / speed etc., and then calculate the horizontal plane collision risk and the risk of falling into the water of HV and ferry in real time. Wherein, ferry horizontal plane (XY axis) sway amplitude, gangway width, gangway friction coefficient, water surface wind speed are included in the ferry information reported on the ferry side, and vehicle weight / size / direction angle / speed are included in the vehicle information.
[0109] While the above description describes vehicle information being reported by the HV, it should be understood that in some embodiments, vehicle information can also be sensed by ferry-side equipment or shore-side equipment and reported to the server. For example, a radar installed on the shore can be used to sense vehicle size and speed, while a weighbridge installed on the shore can be used to measure vehicle weight.
[0110] In step S640, if the vertical or horizontal collision risk / overboard risk exceeds a pre-set collision risk threshold, a collision warning message may be generated and provided to the HV, thereby issuing a collision warning and / or overboard warning to the HV driver, prompting the driver to take timely measures such as reducing speed and adjusting the vehicle's direction and angle of travel. In some embodiments, the timing of the warning may be appropriately set to ensure that the HV driver has sufficient time to take measures after receiving the warning to avoid collision with the ferry gangway, guardrail, etc.
[0111] Steps S650-S670 correspond to the scenario of parking an HV inside a ferry cabin. In this scenario, the HV and RV are parked on the deck inside the ferry cabin. In some cases, due to the influence of sea waves and other factors, the HV may move forward and backward and drift sideways when parked inside the cabin, creating the risk of collision with other vehicles (e.g., collision 170 shown in Figure 1).
[0112] In step S650, the server device calculates the risk of the HV moving forward and backward and drifting sideways. For example, the server device may calculate the risk of the HV moving forward and backward and drifting sideways based on the ferry's horizontal (XY axis) and vertical (Z axis) sway amplitude, the parking deck friction coefficient, the vehicle's weight / size, and the safe parking distance.
[0113] In step S660, the server device calculates the collision risk between the HV and the RV (e.g., other vehicles located in front, behind, or on the left and right of the HV). For example, the server device may obtain the HV's vehicle drift distance, as sensed and reported by the ferry device, and the RV's vehicle information (e.g., location information), to calculate the collision risk between the HV and the RV. The RV's vehicle information may be obtained and reported by the RV, or it may be sensed and reported by the ferry-side device.
[0114] In step S670, if the collision risk exceeds a pre-set collision risk threshold, a collision warning message may be generated and provided to the HV, thereby alerting the HV driver to a collision warning and prompting the driver to adjust the vehicle's position. In some embodiments, the timing of the warning may be appropriately set to ensure that the HV driver has sufficient time to take action to avoid a collision with the HV after receiving the warning.
[0115] According to an embodiment of the present disclosure, when an HV is boarding or disembarking a ferry or parking in a cabin, the ferry-side equipment can sense the shore environment, cabin environment, and vehicles parked around the cabin when the HV is boarding the ship. When the ferry is shaken by wind and waves, or there is a risk of collision between the HV and the ferry gangplank, guardrails, cabin, or vehicles around the cabin, the HV driver can be warned. This can assist the HV driver in avoiding or reducing the risk of accidents such as the vehicle sliding down the slope and falling into the water, the vehicle colliding with the guardrail, or the vehicle chassis hitting the gangplank when the vehicle is boarding or disembarking the ferry, thereby improving the safety of the vehicle boarding or disembarking. In addition, it can reduce the occurrence of collisions between vehicles due to shaking by wind and waves when the vehicles are densely parked in the cabin, thereby improving the safety of parking vehicles during ferry crossings.
[0116] In some embodiments, the collision warning information disclosed herein can be used to prompt at least one of the following: the type of collision risk, the relative position of the collision risk target and the HV, the relative distance between the collision risk target and the HV, the collision risk level, and the type of collision risk target. The collision risk type, for example, indicates the type of risk / information alert, such as the risk of a vertical collision with a ferry ramp, the risk of a horizontal collision between a vehicle and a guardrail / ship cabin, or the risk of a vehicle moving forward or backward or drifting sideways. The relative position of the collision risk target and the HV includes, for example, obstacles such as the ferry ramp and guardrail, and the position of the risk vehicle relative to the HV, including one or more of the following: front, rear, left, right, left front, right front, left rear, or right rear. The relative distance of the collision risk target and the HV includes, for example, obstacles such as the ferry ramp and guardrail, and the distance of nearby parked vehicles relative to the HV, such as the vertical distance between the HV chassis and the ferry ramp, the horizontal distance between the HV and obstacles such as guardrails, and the horizontal distance between the HV and nearby parked vehicles. The collision risk level, for example, is used to assess the level of collision risk, and different alerts can be given to users based on the risk level, such as high, medium, and low. Examples of collision risk targets include obstacles such as ferry ramps, guardrails, and nearby parked vehicles.
[0117] Next, an example of message exchange in vehicle ferry scenario three according to an embodiment of the present disclosure will be described with reference to FIG7 . Vehicle ferry scenario three corresponds to scenario three shown in FIG1 , and is a scenario after vehicles have boarded the ferry. Message exchange in vehicle ferry scenario three is used to provide parking guidance for multiple vehicles after they have boarded the ferry.
[0118] As shown in FIG7 , the server device 400 obtains vehicle information of multiple vehicles (e.g., multiple vehicles 110) from multiple different HVs 420 and / or 430 (FIG. 7 illustrates only the acquisition of vehicle information from one vehicle). The vehicle information of each vehicle may include, for example, at least one of the vehicle position information, vehicle size information, vehicle weight information, vehicle type information, and vehicle center of gravity information shown in Table 1.
[0119] In addition, the server device 400 obtains ferry information from the ferry-side device 500 (corresponding to the ferry-side device 130 in FIG. 1 ). The ferry information may include, for example, at least one of the ferry's loading information shown in Table 3, information about the parking environment on the ferry, and information about the hydrological environment in which the ferry is located.
[0120] The server device 400 generates parking guidance information for guiding the multiple vehicles to park on the parking deck based on the acquired vehicle information and ferry information of the multiple vehicles, and provides it to the multiple vehicles and / or ferry-side devices as vehicle ferry assistance information.
[0121] The message interaction of the vehicle ferry scenario three shown in Figure 7 is similar to the message interaction of the vehicle ferry scenario two shown in Figure 5. The difference is that the server device 400 obtains vehicle information of multiple vehicles and generates parking guidance information based on the vehicle information and ferry information. Other message interaction details are similar to the message interaction of the vehicle ferry scenario two shown in Figure 5 (for example, also including the first message interaction mode and the second message interaction mode), which will not be repeated here.
[0122] Next, an example of Vehicle Ferry Stowage and Parking Guidance (VFSPG) according to an embodiment of the present disclosure will be described with reference to FIG. 8 .
[0123] As shown in Figure 8, in step S8000, the ferry-side device senses ferry information and reports it to the server. This ferry information may include, for example, hydrological information such as the surrounding wind force level, wind direction, and wave height, parking environment information such as the friction coefficient of the parking deck, and basic ferry information such as the ship's tonnage.
[0124] In step S8100, the server calculates the ferry's sway amplitude (e.g., horizontal and vertical sway amplitudes) based on ferry information reported by the ferry's equipment (e.g., ship tonnage, wind force level, wind direction, and wave height). Furthermore, the server may feed the ferry's sway amplitude back to the ferry as vessel stability information.
[0125] In step S8200, multiple vehicles report their respective vehicle information to the server device, or the shore-side device / ferry-side device senses the vehicle information of multiple vehicles and reports it to the server device. The vehicle information includes, for example, vehicle weight, vehicle center of gravity information, etc.
[0126] In step S8300, the server device dynamically determines parking safety information based on the vehicle information of multiple vehicles and the ferry information. In some embodiments, the parking safety information may include, for example, the parking space size of each vehicle, the parking safety distance, the vehicle roll amplitude, and whether tie-down and fastening are required. The vehicle roll amplitude can be calculated, for example, based on the ferry swing amplitude calculated in step S8100 and the vehicle center of gravity in the vehicle information. The parking safety distance and parking space size can be calculated, for example, based on the ferry swing amplitude calculated in step S8100 and the vehicle weight, vehicle size, vehicle type, etc. in the vehicle information. In addition, whether tie-down and fastening are required can be comprehensively determined based on the parking space size, parking safety distance, and vehicle roll amplitude of each vehicle. In some embodiments, the parking safety information can be provided to the corresponding vehicles and ferries as vehicle ferry auxiliary information for safety warnings.
[0127] Figure 9 shows a schematic diagram of safe parking spacing for different vehicles on a ferry. As shown in Figure 9, on the deck of ferry 9000, there are parked an oversized transport truck 9100, a standard large truck 9200, and three cars 9300. Because different types of vehicles parked closely together can easily lead to collisions and other safety accidents, it is necessary to flexibly calculate the safe parking spacing for different vehicles based on the vehicle's rolling amplitude and size to ensure parking safety within the cabin under certain sea wave conditions. The safe parking spacing can be calculated, for example, in step S8300 shown in Figure 8. The dashed boxes outside the vehicles in Figure 9 depict the safe parking spacing for the corresponding vehicles. The safe parking spacing for oversized transport truck 9100 is greater than that for standard large truck 9200, and the safe parking spacing for standard large truck 9200 is greater than that for cars 9300.
[0128] Table 6 below illustrates the safe parking distances for different types of vehicles on a 10,000-ton ro-ro passenger ferry under different sea surface wind speeds, wave heights, and other conditions.
[0129] Table 6: Parking safety information for 10,000-ton ro-ro passenger ships
[0130] According to Table 6 above, the following information can be obtained:
[0131] (1) In an environment where the wind force is less than level 5 and the wave height is 0 to 2.5 meters (less than level 4 medium waves), the vehicles of different types
[0132] The safe parking distance is 0.5 to 1.0 meters, and no tying or fastening is required;
[0133] (2) In an environment with wind force 6 to 7 and wave height 2.5 to 4.0 meters (level 5 wave), parking safety requirements for different types of vehicles
[0134] The overall spacing is 0.8 to 1.5 meters, and only oversized and large trucks need to be tied down;
[0135] (3) In an environment with wind force 8-9 and wave height 4.0-6.0 meters (level 6 wave), parking safety requirements for different types of vehicles
[0136] The full spacing is 1.0 to 2.0 meters, and all vehicles need to be tied down;
[0137] (4) When the wind speed on the sea surface exceeds level 9 and the wave height exceeds 6 meters, it is recommended that ships stop sailing.
[0138] Continuing with FIG8 , in step S8400, the server device dynamically plans parking space distribution information based on vehicle information of multiple vehicles and ferry information. For example, based on parking environment information such as parking deck dimensions and parking lane widths, the server device can calculate the safe lane widths on the parking deck, plan the optimal number of lanes, lane widths / lengths, and calculate the distance between each lane's centerline and the ferry's centerline.
[0139] FIG10 shows an example diagram of parking for different types of vehicles based on fixed lanes and fixed parking spaces, and FIG11 shows a schematic diagram of a dynamically planned parking space distribution according to an embodiment of the present disclosure.
[0140] The top portion of Figure 10 shows four fixed lanes 1 through 4, each with a fixed parking area. When a large truck is parked, as shown in the bottom portion of Figure 10 , it needs to occupy two fixed lanes. In this case, fixed lanes 1 and 2 are merged into lane 1', potentially wasting parking space.
[0141] In contrast, as shown in Figure 11, in the present disclosure, lane safety widths are calculated based on the safe parking spacing for different vehicles, and dynamic lanes 1, 2-1, 2-2, 2-3, and 3 are then set. Dynamic lane 1 still has large trucks parked on it, but its width is reduced compared to lane 1' in Figure 10 (for example, it occupies one semi-fixed lane, while lane 1' in Figure 10 occupies two fixed lanes). This dynamic planning frees up space for more vehicles. For example, compared to Figure 10, Figure 11 shows two additional parking spaces.
[0142] Referring back to Figure 8 , in step S8500 , the server device dynamically allocates the loads of the ferry and multiple vehicles to generate parking guidance information after dynamic allocation. For example, the server device may allocate the loads to the cabin based on the ship's center of gravity balance ratio to adjust the parking space distribution dynamically planned in step S8400 .
[0143] Figure 12 shows a schematic diagram of the parking space distribution after dynamic loading. As shown in Figure 12, considering the balance ratio of the horizontal center of gravity of the ship, the vehicle loading is carried out so that light-weight small cars are parked in the middle lane (for example, parking spaces 5 to 9 suitable for parking small cars are set in the middle lane), and heavy trucks are parked in the lanes on both sides of the ship (for example, parking spaces 1, 10, and 11 suitable for parking large vehicles are set in the lanes on both sides). In addition, according to dynamic loading, the positions of other parking spaces 2-4 and 12-15 are reasonably set (wherein parking spaces 14 and 15 correspond to the newly added parking spaces in Figure 11). In addition, 1 to 15 in Figure 12 represent the order in which vehicles enter the warehouse, and this order can also be determined after dynamic loading.
[0144] In step S8600, the server device provides parking space distribution information to the ferry so that the ferry can display the parking space distribution (such as parking lanes, parking spaces, license plate numbers of vehicles to be parked, etc.) on a parking deck (such as a smart deck with display function), thereby facilitating the guidance of vehicles to park in the order of entry.
[0145] In step S8700, the server device provides each of the multiple vehicles with information about the corresponding parking space, such as the deck level, lane, and parking space where the vehicle is parked, and gives the order in which the vehicles enter the cabin, thereby facilitating the guidance of vehicle parking.
[0146] The VFSPG disclosed in this disclosure improves the ferry's center of gravity distribution balance and wind and wave resistance, reduces ship rolling, and enhances passenger comfort. Furthermore, while ensuring the safety of vehicles on board, it can flexibly arrange the number of vehicles on board, maximizing the number of vehicles carried and improving parking space utilization within the cabin.
[0147] The message interaction mechanism for assisting vehicle ferries according to an embodiment of the present disclosure has been described above with reference to Figures 2 to 11 , wherein a server device obtains vehicle information and ferry-related information and generates vehicle ferry assistance information based on this information. In some embodiments, an MEC device can be arranged near the server device to calculate and generate the vehicle ferry assistance information. In addition, the server device described in this disclosure can also be configured to include an MEC device.
[0148] In other embodiments, differently from the message mechanism described with reference to Figures 2 to 11, vehicle information and ferry-related information can also be obtained by ferry-related equipment (such as shore-side equipment, ferry-side equipment), and vehicle ferry auxiliary information can be generated based on this information. In this case, the MEC device can be arranged near the ferry-related equipment (such as near the shore-side equipment, near the ferry-side equipment) to calculate and generate vehicle ferry auxiliary information. In addition, the ferry-related equipment described in the present disclosure can also be configured to include MEC equipment. Next, the shore-side equipment and ferry-side equipment under the above-mentioned message mechanism will be described in detail in conjunction with Figures 13 to 18, wherein Figures 13 to 15 correspond to an embodiment in which vehicle ferry auxiliary information is generated by the shore-side equipment, and Figures 16 to 18 correspond to an embodiment in which vehicle ferry auxiliary information is generated by the ferry-side equipment.
[0149] Fig. 13 shows an exemplary block diagram of an electronic device 1300 for shore-side equipment provided at a ferry terminal according to an embodiment of the present disclosure. The shore-side equipment may correspond to the shore-side equipment 120 shown in Fig. 1 , for example.
[0150] In some embodiments, the electronic device 1300 may include a processing circuit 1310. The processing circuit 1310 of the electronic device 1300 provides various functions of the electronic device 1300. In some embodiments, the processing circuit 1310 of the electronic device 1300 may be configured to execute a communication method for a shore-side device.
[0151] Processing circuitry 1310 may refer to various implementations of digital circuitry, analog circuitry, or mixed-signal (a combination of analog and digital) circuitry that performs functions in a computing system. Processing circuitry may include, for example, circuits such as integrated circuits (ICs), application-specific integrated circuits (ASICs), portions or circuits of a separate processor core, an entire processor core, a separate processor, a programmable hardware device such as a field programmable gate array (FPGA), and / or a system including multiple processors.
[0152] In some embodiments, the processing circuit 1310 may include a vehicle information acquisition unit 1320, a shore information acquisition unit 1330, a vehicle ferry auxiliary information generation unit 1340, and a vehicle ferry auxiliary information providing unit 1350, which are respectively configured to execute steps S1410 to 1440 in the communication method 1400 using the shore device shown in Figure 14 described later.
[0153] In some embodiments, the electronic device 1300 may further include a memory (not shown). The memory of the electronic device 1300 may store information generated by the processing circuit 1310 and programs and data for the operation of the electronic device 1310. The memory may be a volatile memory and / or a non-volatile memory. For example, the memory may include, but is not limited to, a random access memory (RAM), a dynamic random access memory (DRAM), a static random access memory (SRAM), a read-only memory (ROM), and a flash memory. In addition, the electronic device 1300 may be implemented at the chip level, or may be implemented at the device level by including other external components.
[0154] FIG14 illustrates an exemplary flow chart of a communication method 1400 for a shore-side device according to an embodiment of the present disclosure. This communication method can be used, for example, with the electronic device 1300 shown in FIG13 . The shore-side device communication method 1400 shown in FIG14 can be used, for example, for message exchange in vehicle ferry scenario 1 (corresponding to scenario 1 in FIG1 ). FIG15 illustrates an example of message exchange in vehicle ferry scenario 1, in which a shore-side device 1510 executes the shore-side device communication method 1400 shown in FIG14 .
[0155] Next, the message interaction of the vehicle ferry scenario 1 according to an embodiment of the present disclosure will be described in detail with reference to FIG. 14 and FIG. 15 .
[0156] As shown in Figure 15, the shore-side device 1510 obtains the vehicle information of the HV performing the ferry (corresponding to step S1410 of Figure 14). In some embodiments, the shore-side device 1510 obtains the vehicle information of the HV from the server device 1500 via the Internet of Vehicles communication link. Similar to the two message interaction modes described above with reference to Figure 4, the vehicle information can be provided to the server device 1500 via the Internet of Vehicles communication link by the HV1520 of the mobile intelligent terminal carrying the Internet of Vehicles communication protocol, or by the HV430 including the vehicle-mounted OBU based on the Internet of Vehicles communication protocol, via the Internet of Vehicles communication link. In some embodiments, the shore-side device 1510 may include one or more sensors, which can sense the vehicle information of the HV via the sensor.
[0157] In addition, the shore-side device 1510 obtains shore-side information related to the ferry terminal (corresponding to step S1420 of FIG. 14 ). In some embodiments, the shore-side information can be sensed by using one or more sensors included in the shore-side device 1510 .
[0158] The shore-side device 1510 generates vehicle ferry assistance information based on the acquired vehicle information and shore-side information (corresponding to step S1430 of FIG. 14 ).
[0159] In addition, the shore-side device 1510 provides the vehicle ferry auxiliary information to the HV (corresponding to step S1440 of Figure 14). In some embodiments, as shown in Figure 15, the shore-side device 1510 (for example, including RSU) can directly communicate with the HV1530 via a vehicle network communication link (for example, a PC5 link) to provide the vehicle ferry auxiliary information to the HV1530. In other embodiments, as shown in Figure 15, the shore-side device 1510 can provide the vehicle ferry auxiliary information (for example, via a vehicle network communication link) to the server device 1500, and the server device 1500 (for example, via a vehicle network communication link) provides the vehicle ferry auxiliary information to the HV1520. The above two message interaction modes can coexist, or one message interaction mode can be adopted as needed.
[0160] In some embodiments, the shore-side device 1510 also provides shore-side information to the server device 1500 for storage and management of the shore-side information by the server device 1500. In addition, the server device 1500 can also obtain and store vehicle information from HVs and other RVs, thereby enabling comprehensive management and control of ferry-related information.
[0161] In the embodiments described above with reference to Figures 13 to 15, the specific contents of the vehicle information, shore information and vehicle ferry auxiliary information are the same as those in the embodiments described with reference to Figures 2 to 12, and are not repeated here.
[0162] 16 is a block diagram showing an exemplary configuration of an electronic device 1600 for use in a ferry-side device provided on a ferry according to an embodiment of the present disclosure. The ferry-side device may correspond to the ferry-side device 130 shown in FIG1 , for example.
[0163] In some embodiments, the electronic device 1600 may include a processing circuit 1610. The processing circuit 1610 of the electronic device 1600 provides various functions of the electronic device 1600. In some embodiments, the processing circuit 1610 of the electronic device 1600 may be configured to execute a communication method for a ferry-side device.
[0164] Processing circuitry 1610 may refer to various implementations of digital circuitry, analog circuitry, or mixed-signal (a combination of analog and digital) circuitry that performs functions in a computing system. Processing circuitry may include, for example, circuits such as integrated circuits (ICs), application-specific integrated circuits (ASICs), portions or circuits of a separate processor core, an entire processor core, a separate processor, a programmable hardware device such as a field programmable gate array (FPGA), and / or a system including multiple processors.
[0165] In some embodiments, the processing circuit 1610 may include a vehicle information acquisition unit 1620, a ferry information acquisition unit 1630, a vehicle ferry auxiliary information generation unit 1640, and a vehicle ferry auxiliary information providing unit 1650, which are respectively configured to execute steps S1710 to 1740 in the communication method 1700 using the ferry side device shown in Figure 17 described later.
[0166] In some embodiments, the electronic device 1600 may further include a memory (not shown). The memory of the electronic device 1600 may store information generated by the processing circuit 1610 and programs and data for the operation of the electronic device 1610. The memory may be a volatile memory and / or a non-volatile memory. For example, the memory may include, but is not limited to, a random access memory (RAM), a dynamic random access memory (DRAM), a static random access memory (SRAM), a read-only memory (ROM), and a flash memory. In addition, the electronic device 1600 may be implemented at the chip level, or may be implemented at the device level by including other external components.
[0167] FIG17 illustrates an exemplary flow chart of a communication method 1700 for a ferry-side device according to an embodiment of the present disclosure. This communication method can be used, for example, with the electronic device 1600 shown in FIG16 . The communication method 1700 for a shore-side device shown in FIG17 can be used, for example, to perform message exchanges for vehicle ferry scenarios 2 and 3 (corresponding to scenarios 2 and 3 in FIG1 ). FIG18 illustrates an example of message exchanges for vehicle ferry scenarios 2 and 3, wherein a ferry-side device 1810 executes the communication method 1700 for a ferry-side device described in FIG17 .
[0168] Next, the message exchange in Scenario 2 and Scenario 3 according to an embodiment of the present disclosure will be described in detail with reference to Figures 17 and 18. It should be understood that the message exchange patterns in Scenario 2 and Scenario 3 are identical, differing only in the specific content of the vehicle ferry auxiliary information. In Scenario 2, the vehicle ferry auxiliary information may include collision warning information, while in Scenario 3, the vehicle ferry auxiliary information may include parking guidance information. The following description will not distinguish between Scenario 2 and Scenario 3, but will provide a general description.
[0169] As shown in Figure 18, the ferry-side device 1810 obtains the vehicle information of the HV on the ferry (corresponding to step S1710 of Figure 17). In some embodiments, the ferry-side device 1810 obtains the vehicle information of the HV from the server device 1800 via the Internet of Vehicles communication link. Similar to the two message interaction modes described above with reference to Figure 4, the vehicle information can be provided to the server device 1800 via the Internet of Vehicles communication link by the HV1820 of the mobile smart terminal carrying the Internet of Vehicles communication protocol, or by the HV1830 including the vehicle-mounted OBU based on the Internet of Vehicles communication protocol, via the Internet of Vehicles communication link, to provide the vehicle information to the server device 1800. In some embodiments, the ferry-side device 1810 may include one or more sensors, which can sense the vehicle information of the HV via the sensor.
[0170] In addition, the ferry-side device 1810 obtains ferry information related to the ferry (corresponding to step S1720 of FIG. 17 ). In some embodiments, the ferry information can be sensed using one or more sensors included in the ferry-side device 1810.
[0171] The ferry-side device 1810 generates vehicle ferry auxiliary information based on the acquired vehicle information of the HV and ferry information (corresponding to step S1730 of FIG. 17 ).
[0172] In addition, the ferry-side device 1810 provides the vehicle ferry auxiliary information to the HV (corresponding to step S1740 of Figure 17). In some embodiments, as shown in Figure 18, the ferry-side device 1810 (for example, including an RSU) can directly communicate with the HV1830 via a vehicle networking communication link (for example, a PC5 link) to provide the vehicle ferry auxiliary information to the HV1830. In other embodiments, as shown in Figure 18, the ferry-side device 1810 can provide the vehicle ferry auxiliary information (for example, via a vehicle networking communication link) to the server device 1800, and the server device 1800 (for example, via a vehicle networking communication link) provides the vehicle ferry auxiliary information to the HV1820. The above two message interaction modes can coexist, or one message interaction mode can be adopted as needed.
[0173] In some embodiments, the ferry-side device 1810 also provides ferry information to the server device 1800 for storage and management of the ferry information by the server device 1800. In addition, the server device 1800 also acquires and stores vehicle information from HVs and other RVs, thereby enabling comprehensive management and control of ferry-related information.
[0174] In the embodiments described above with reference to Figures 16 to 18, the specific contents of the vehicle information, ferry information and vehicle ferry auxiliary information are the same as those in the embodiments described with reference to Figures 2 to 12, and are not repeated here.
[0175] Next, a vehicle according to an embodiment of the present disclosure will be described with reference to FIG. 19 and FIG. 20 .
[0176] FIG19 is a block diagram showing an exemplary configuration of an electronic device 1900 for a vehicle according to an embodiment of the present disclosure. The vehicle may correspond to the vehicle 110 shown in FIG1 , for example.
[0177] In some embodiments, the electronic device 1900 may include a processing circuit 1910. The processing circuit 1910 of the electronic device 1900 provides various functions of the electronic device 1900. In some embodiments, the processing circuit 1910 of the electronic device 1900 may be configured to execute a communication method for a vehicle.
[0178] Processing circuitry 1910 may refer to various implementations of digital circuitry, analog circuitry, or mixed-signal (a combination of analog and digital) circuitry that performs functions in a computing system. Processing circuitry may include, for example, circuits such as integrated circuits (ICs), application-specific integrated circuits (ASICs), portions or circuits of a separate processor core, an entire processor core, a separate processor, a programmable hardware device such as a field programmable gate array (FPGA), and / or a system including multiple processors.
[0179] In some embodiments, the processing circuit 1910 may include a vehicle information providing unit 1920 and a vehicle ferry auxiliary information acquiring unit 1930 , which are respectively configured to execute steps S2010 and S2020 in the vehicle communication method 2000 shown in FIG. 20 described later.
[0180] In some embodiments, the electronic device 1900 may further include a memory (not shown). The memory of the electronic device 1900 may store information generated by the processing circuit 1910 and programs and data for the operation of the electronic device 1910. The memory may be a volatile memory and / or a non-volatile memory. For example, the memory may include, but is not limited to, a random access memory (RAM), a dynamic random access memory (DRAM), a static random access memory (SRAM), a read-only memory (ROM), and a flash memory. In addition, the electronic device 1900 may be implemented at the chip level, or may be implemented at the device level by including other external components.
[0181] FIG20 shows an exemplary flow chart of a communication method 2000 for a vehicle according to an embodiment of the present disclosure. The communication method can be used, for example, in the electronic device 1900 shown in FIG19 .
[0182] As shown in Figure 20, in step S2010, the vehicle information providing unit 1920 provides vehicle information of the vehicle in response to the control information for generating vehicle ferry auxiliary information. In some embodiments, the control information may be sent by a server device to the vehicle, and the vehicle provides the vehicle information to the server device in response to the control information. In other embodiments, the control information may be sent by a device related to the ferry (such as a shore-side device, a ferry-side device), and the vehicle provides the vehicle information to the server device in response to the control information, and provides it to the ferry-related device via the server device. In some embodiments, the ferry-related device may periodically broadcast the control information, and the vehicle receives the control information when it enters the control range of the ferry-related device and performs corresponding operations in response to the control information.
[0183] In some embodiments, the vehicle may include one or more sensors that, in response to control information, sense vehicle information via the one or more sensors. In some embodiments, the control information may include instructing the vehicle which vehicle information to provide. The vehicle then provides the vehicle information accordingly based on the instructing information, for example, by causing corresponding sensors of the vehicle to sense the vehicle information. Thus, a server device or ferry-related device may generate vehicle ferry assistance information based on the vehicle information provided by the vehicle.
[0184] In step S2020 , the vehicle ferry assistance information acquiring unit 1930 acquires vehicle ferry assistance information from a server device or a device related to ferrying, so as to assist the vehicle in ferrying.
[0185] In some embodiments, a vehicle may include an on-board unit (OBU) based on a vehicle-to-vehicle communication protocol and configured to obtain vehicle ferry auxiliary information from a ferry-related device via a vehicle-to-vehicle communication link. The ferry-related device may include a RSU based on a vehicle-to-vehicle communication protocol, capable of directly communicating with the OBU via a vehicle-to-vehicle communication link (e.g., a PC5 link) to provide the OBU with the vehicle ferry auxiliary information.
[0186] In some embodiments, a vehicle may include a mobile smart terminal that supports the IoV communication protocol and is configured to obtain vehicle ferry assistance information from a server device via an IoV communication link. The mobile smart terminal may be, for example, a mobile phone, tablet computer, smartwatch, or other smart terminal. By loading the IoV protocol (e.g., installing an application that supports the IoV protocol), it can support application-layer IoV communication.
[0187] In the embodiments described above with reference to Figures 19 and 20, the specific contents of the vehicle information and the vehicle ferry auxiliary information are the same as those in the embodiments described with reference to Figures 2 to 12, and are not repeated here.
[0188] Application examples according to the present disclosure will be described below.
[0189] The technology of the present disclosure can be applied to various products.
[0190] The shore-side equipment and / or ferry-side equipment disclosed herein can be implemented, for example, using a road-side unit (RSU) in the Internet of Vehicles.
[0191] The electronic device on the vehicle side of the present disclosure can be implemented using a terminal device, for example.
[0192] For example, the terminal device can be implemented as a mobile terminal (such as a smart phone, a tablet personal computer (PC), a notebook PC, a portable game terminal, a portable / dongle-type mobile router, and a digital camera) or an in-vehicle terminal (such as a car navigation device). The terminal device can also be implemented as a terminal that performs machine-to-machine (M2M) communication (also known as a machine type communication (MTC) terminal). In addition, the terminal device can be a wireless communication module (such as an integrated circuit module including a single chip) installed on each of the above-mentioned terminals.
[0193] [Application examples of RSU]
[0194] (First application example)
[0195] 21 is a block diagram showing a first example of a schematic configuration of an RSU to which the technology of the present disclosure can be applied. The RSU 800 includes one or more antennas 810 and a roadside device 820. The roadside device 820 and each antenna 810 can be connected to each other via an RF cable.
[0196] Each antenna 810 includes a single or multiple antenna elements (such as the multiple antenna elements included in a multiple-input, multiple-output (MIMO) antenna) and is used for transmitting and receiving wireless signals by the roadside equipment 820. As shown in FIG21 , the RSU 800 may include multiple antennas 810. For example, the multiple antennas 810 may be compatible with multiple frequency bands used by the RSU 800. The roadside equipment 820 includes a controller 821, a memory 822, a network interface 823, and a wireless communication interface 825.
[0197] The controller 821 may be, for example, a CPU or a DSP, and operates various functions of the higher layers of the roadside device 820. For example, the controller 821 generates data packets based on data in the signal processed by the wireless communication interface 825, and transmits the generated packets via the network interface 823. The controller 821 may bundle data from a plurality of baseband processors to generate bundled packets, and transmit the generated bundled packets. The controller 821 may have logic functions for performing controls such as radio resource control, radio bearer control, mobility management, admission control, and scheduling. The control may be performed in conjunction with a nearby RSU or core network node (e.g., an access and mobility management function AMF (Access and Mobility Management Function)). The memory 822 includes RAM and ROM, and stores programs executed by the controller 821 and various types of control data (such as a terminal list, transmission power data, and scheduling data).
[0198] The network interface 823 is a communication interface for connecting the roadside device 820 to the core network 824. The controller 821 can communicate with the core network node or another RSU via the network interface 823. In this case, the RSU 800 and the core network node or other RSU can be connected to each other through a logical interface (such as a C-V2X uu interface or a C-V2X PC5). The network interface 823 can also be a wired communication interface or a wireless communication interface for a wireless backhaul line. If the network interface 823 is a wireless communication interface, the network interface 823 can use a higher frequency band for wireless communication than the frequency band used by the wireless communication interface 825.
[0199] The wireless communication interface 825 supports any cellular communication scheme and provides wireless connectivity to terminals located in the cell of the RSU 800 via the antenna 810. The wireless communication interface 825 may typically include, for example, a baseband (BB) processor 826 and an RF circuit 827. The BB processor 826 may perform various types of signal processing, such as encoding / decoding, modulation / demodulation, and multiplexing / demultiplexing, and may perform various types of signal processing for layers such as L1, medium access control (MAC), radio link control (RLC), and packet data convergence protocol (PDCP). In place of the controller 821, the BB processor 826 may have some or all of the aforementioned logical functions. The BB processor 826 may be a memory that stores communication control programs, or a module that includes a processor configured to execute programs and associated circuitry. Updating the program may modify the functionality of the BB processor 826. The module may be a card or blade inserted into a slot of the roadside equipment 820. Alternatively, the module may be a chip mounted on the card or blade. Meanwhile, the RF circuit 827 may include, for example, a mixer, a filter, and an amplifier, and transmit and receive wireless signals via the antenna 810 .
[0200] As shown in FIG21 , the wireless communication interface 825 may include multiple BB processors 826. For example, multiple BB processors 826 may be compatible with multiple frequency bands used by the RSU 800. As shown in FIG21 , the wireless communication interface 825 may include multiple RF circuits 827. For example, multiple RF circuits 827 may be compatible with multiple antenna elements. Although FIG21 illustrates an example in which the wireless communication interface 825 includes multiple BB processors 826 and multiple RF circuits 827, the wireless communication interface 825 may also include a single BB processor 826 or a single RF circuit 827.
[0201] (Second application example)
[0202] FIG22 is a block diagram illustrating a second example of a schematic configuration of an RSU to which the techniques of the present disclosure may be applied. The RSU includes one or more antennas 840, a roadside device 850, and an RRH 860. The RRH 860 and each antenna 840 may be connected to each other via an RF cable. The roadside device 850 and the RRH 860 may be connected to each other via a high-speed line such as an optical fiber cable.
[0203] Each of the antennas 840 includes a single or multiple antenna elements (such as multiple antenna elements included in a MIMO antenna) and is used for the RRH 860 to transmit and receive wireless signals. As shown in FIG22, the RSU 830 may include multiple antennas 840. For example, the multiple antennas 840 may be compatible with multiple frequency bands used by the RSU 830. The roadside equipment 850 includes a controller 851, a memory 852, a network interface 853, a wireless communication interface 855, and a connection interface 857. The controller 851, the memory 852, and the network interface 853 are the same as the controller 821, the memory 822, and the network interface 823 described with reference to FIG21.
[0204] The wireless communication interface 855 supports any cellular communication scheme and provides wireless communication to terminals located in the sector corresponding to the RRH 860 via the RRH 860 and the antenna 840. The wireless communication interface 855 may generally include, for example, a BB processor 856. Except that the BB processor 856 is connected to the RF circuit 864 of the RRH 860 via the connection interface 857, the BB processor 856 is the same as the BB processor 826 described with reference to FIG. 21. As shown in FIG. 22, the wireless communication interface 855 may include multiple BB processors 856. For example, multiple BB processors 856 may be compatible with multiple frequency bands used by the RSU 830. Although FIG. 22 shows an example in which the wireless communication interface 855 includes multiple BB processors 856, the wireless communication interface 855 may also include a single BB processor 856.
[0205] The connection interface 857 is an interface for connecting the roadside device 850 (wireless communication interface 855) to the RRH 860. The connection interface 857 may also be a communication module for connecting the roadside device 850 (wireless communication interface 855) to the RRH 860 for communication in the high-speed line.
[0206] The RRH 860 includes a connection interface 861 and a wireless communication interface 863 .
[0207] The connection interface 861 is an interface for connecting the RRH 860 (wireless communication interface 863) to the roadside apparatus 850. The connection interface 861 may also be a communication module for communication in the above-mentioned high-speed line.
[0208] The wireless communication interface 863 transmits and receives wireless signals via the antenna 840. The wireless communication interface 863 may generally include, for example, an RF circuit 864. The RF circuit 864 may include, for example, a mixer, a filter, and an amplifier, and transmits and receives wireless signals via the antenna 840. As shown in FIG22 , the wireless communication interface 863 may include multiple RF circuits 864. For example, multiple RF circuits 864 may support multiple antenna elements. Although FIG22 shows an example in which the wireless communication interface 863 includes multiple RF circuits 864, the wireless communication interface 863 may also include a single RF circuit 864.
[0209] In the RSU 800 and RSU 830 shown in Figures 21 and 22, one or more components included in the processing circuit 1310 described with reference to Figure 13 and the processing circuit 1610 described with reference to Figure 16 may be implemented in the wireless communication interface 912. Alternatively, at least part of these components may also be implemented by the controller 821 and the controller 851.
[0210] [Application examples for terminal devices]
[0211] (First application example)
[0212] 23 is a block diagram showing an example of a schematic configuration of a smartphone 900 to which the technology of the present disclosure can be applied. The smartphone 900 includes a processor 901, a memory 902, a storage device 903, an external connection interface 904, a camera 906, a sensor 907, a microphone 908, an input device 909, a display device 910, a speaker 911, a wireless communication interface 912, one or more antenna switches 915, one or more antennas 916, a bus 917, a battery 918, and an auxiliary controller 919.
[0213] The processor 901 may be, for example, a CPU or a system on a chip (SoC), and controls the functions of the application layer and other layers of the smartphone 900. The memory 902 includes RAM and ROM, and stores data and programs executed by the processor 901. The storage device 903 may include storage media such as semiconductor memories and hard disks. The external connection interface 904 is an interface for connecting external devices (such as memory cards and universal serial bus (USB) devices) to the smartphone 900.
[0214] The camera 906 includes an image sensor such as a charge coupled device (CCD) and a complementary metal oxide semiconductor (CMOS) and generates a captured image. The sensor 907 may include a group of sensors such as a measurement sensor, a gyroscope sensor, a geomagnetic sensor, and an acceleration sensor. The microphone 908 converts the sound input to the smartphone 900 into an audio signal. The input device 909 includes, for example, a touch sensor, a keypad, a keyboard, a button, or a switch configured to detect a touch on the screen of the display device 910, and receives an operation or information input from the user. The display device 910 includes a screen such as a liquid crystal display (LCD) and an organic light emitting diode (OLED) display and displays an output image of the smartphone 900. The speaker 911 converts the audio signal output from the smartphone 900 into sound.
[0215] The wireless communication interface 912 supports any cellular communication scheme (such as LTE and LTE-Advanced) and performs wireless communication. The wireless communication interface 912 may generally include, for example, a BB processor 913 and an RF circuit 914. The BB processor 913 may perform, for example, encoding / decoding, modulation / demodulation, and multiplexing / demultiplexing, and perform various types of signal processing for wireless communication. Meanwhile, the RF circuit 914 may include, for example, a mixer, a filter, and an amplifier, and transmit and receive wireless signals via an antenna 916. The wireless communication interface 912 may be a chip module on which the BB processor 913 and the RF circuit 914 are integrated. As shown in FIG23 , the wireless communication interface 912 may include multiple BB processors 913 and multiple RF circuits 914. Although FIG23 shows an example in which the wireless communication interface 912 includes multiple BB processors 913 and multiple RF circuits 914, the wireless communication interface 912 may also include a single BB processor 913 or a single RF circuit 914.
[0216] In addition, in addition to the cellular communication scheme, the wireless communication interface 912 can support other types of wireless communication schemes, such as a short-range wireless communication scheme, a near-field communication scheme, and a wireless local area network (LAN) scheme. In this case, the wireless communication interface 912 may include a BB processor 913 and an RF circuit 914 for each wireless communication scheme.
[0217] Each of the antenna switches 915 switches a connection destination of the antenna 916 between a plurality of circuits (eg, circuits for different wireless communication schemes) included in the wireless communication interface 912 .
[0218] Each of the antennas 916 includes a single or multiple antenna elements (such as multiple antenna elements included in a MIMO antenna) and is used for transmitting and receiving wireless signals via the wireless communication interface 912. As shown in FIG23, the smartphone 900 may include multiple antennas 916. Although FIG23 shows an example in which the smartphone 900 includes multiple antennas 916, the smartphone 900 may also include a single antenna 916.
[0219] In addition, the smartphone 900 may include an antenna 916 for each wireless communication scheme. In this case, the antenna switch 915 may be omitted from the configuration of the smartphone 900.
[0220] The bus 917 connects the processor 901, the memory 902, the storage device 903, the external connection interface 904, the camera 906, the sensor 907, the microphone 908, the input device 909, the display device 910, the speaker 911, the wireless communication interface 912, and the auxiliary controller 919. The battery 918 supplies power to the various blocks of the smartphone 900 shown in FIG. 23 via feeders, which are partially shown as dashed lines in the figure. The auxiliary controller 919 operates the minimum necessary functions of the smartphone 900, for example, in sleep mode.
[0221] In the smartphone 900 shown in FIG23 , one or more components included in the processing circuit 1310 described with reference to FIG13 and the processing circuit 1610 described with reference to FIG16 may be implemented in the wireless communication interface 912. Alternatively, at least a portion of these components may also be implemented by the processor 901 or the auxiliary controller 919.
[0222] (Second application example)
[0223] 24 is a block diagram showing an example of a schematic configuration of a car navigation device 920 to which the technology of the present disclosure can be applied. The car navigation device 920 includes a processor 921, a memory 922, a global positioning system (GPS) module 924, a sensor 925, a data interface 926, a content player 927, a storage medium interface 928, an input device 929, a display device 930, a speaker 931, a wireless communication interface 933, one or more antenna switches 936, one or more antennas 937, and a battery 938.
[0224] The processor 921 may be, for example, a CPU or an SoC, and controls a navigation function and other functions of the car navigation apparatus 920. The memory 922 includes a RAM and a ROM, and stores data and programs executed by the processor 921.
[0225] The GPS module 924 measures the position (such as latitude, longitude, and altitude) of the car navigation device 920 using GPS signals received from GPS satellites. The sensor 925 may include a group of sensors such as a gyroscope sensor, a geomagnetic sensor, and an air pressure sensor. The data interface 926 is connected to, for example, the in-vehicle network 941 via an unillustrated terminal and acquires data generated by the vehicle (such as vehicle speed data).
[0226] The content player 927 reproduces content stored in a storage medium (such as a CD or DVD) inserted into the storage medium interface 928. The input device 929 includes, for example, a touch sensor, button, or switch configured to detect a touch on the screen of the display device 930, and receives an operation or information input from the user. The display device 930 includes a screen such as an LCD or OLED display and displays an image of a navigation function or reproduced content. The speaker 931 outputs the sound of the navigation function or the reproduced content.
[0227] The wireless communication interface 933 supports any cellular communication scheme (such as LTE and LTE-Advanced) and performs wireless communication. The wireless communication interface 933 may generally include, for example, a BB processor 934 and an RF circuit 935. The BB processor 934 may perform, for example, encoding / decoding, modulation / demodulation, and multiplexing / demultiplexing, and perform various types of signal processing for wireless communication. Meanwhile, the RF circuit 935 may include, for example, a mixer, a filter, and an amplifier, and transmit and receive wireless signals via an antenna 937. The wireless communication interface 933 may also be a chip module on which the BB processor 934 and the RF circuit 935 are integrated. As shown in Figure 24, the wireless communication interface 933 may include multiple BB processors 934 and multiple RF circuits 935. Although Figure 24 shows an example in which the wireless communication interface 933 includes multiple BB processors 934 and multiple RF circuits 935, the wireless communication interface 933 may also include a single BB processor 934 or a single RF circuit 935.
[0228] In addition, in addition to the cellular communication scheme, the wireless communication interface 933 can support other types of wireless communication schemes, such as a short-range wireless communication scheme, a near field communication scheme, and a wireless LAN scheme. In this case, for each wireless communication scheme, the wireless communication interface 933 can include a BB processor 934 and an RF circuit 935.
[0229] Each of the antenna switches 936 switches a connection destination of the antenna 937 between a plurality of circuits included in the wireless communication interface 933 , such as circuits for different wireless communication schemes.
[0230] Each of the antennas 937 includes a single or multiple antenna elements (such as multiple antenna elements included in a MIMO antenna) and is used for transmitting and receiving wireless signals via the wireless communication interface 933. As shown in FIG24, the car navigation device 920 may include multiple antennas 937. Although FIG24 shows an example in which the car navigation device 920 includes multiple antennas 937, the car navigation device 920 may also include a single antenna 937.
[0231] Furthermore, the car navigation device 920 may include an antenna 937 for each wireless communication scheme. In this case, the antenna switch 936 may be omitted from the configuration of the car navigation device 920.
[0232] The battery 938 supplies power to the respective blocks of the car navigation device 920 shown in Fig. 24 via a feeder line, which is partially shown as a dotted line in the figure. The battery 938 accumulates the power supplied from the vehicle.
[0233] 24 , one or more components included in the processing circuit 1910 described with reference to FIG19 may be implemented in the wireless communication interface 912. Alternatively, at least a portion of these components may also be implemented by the processor 921.
[0234] The technology of the present disclosure can also be implemented as an in-vehicle system (or vehicle) 940 including a car navigation device 920, an in-vehicle network 941, and one or more blocks of a vehicle module 942. The vehicle module 942 generates vehicle data (such as vehicle speed, engine speed, and fault information) and outputs the generated data to the in-vehicle network 941.
[0235] It should be understood that references to "an embodiment" or similar expressions throughout this specification mean that the specific features, structures, or characteristics described in connection with that embodiment are included in at least one specific embodiment of the present disclosure. Therefore, the appearance of phrases such as "in an embodiment of the present disclosure" or similar expressions throughout this specification does not necessarily refer to the same embodiment.
[0236] Those skilled in the art will appreciate that the present disclosure is implemented as a system, apparatus, method, or computer-readable storage medium (e.g., a non-transitory storage medium) as a computer program product. Thus, the present disclosure may be implemented in various forms, such as a complete hardware embodiment, a complete software embodiment (including firmware, resident software, microprogram code, etc.), or a combination of software and hardware, hereinafter referred to as a "circuit," "module," or "system." Furthermore, the present disclosure may also be implemented as a computer program product in any tangible media form having computer-usable program code stored thereon.
[0237] The relevant description of the present disclosure is described with reference to the flowcharts and / or block diagrams of the systems, devices, methods and computer program products according to specific embodiments of the present disclosure. It is understood that each block in each flowchart and / or block diagram, as well as any combination of blocks in the flowchart and / or block diagram, can be implemented using computer program instructions. These computer program instructions can be executed by a machine composed of a processor of a general-purpose computer or a special computer or other programmable data processing device, and the instructions are processed by the computer or other programmable data processing device to implement the functions or operations described in the flowchart and / or block diagram.
[0238] The accompanying drawings show flowcharts and block diagrams of the architecture, functions and operations that can be implemented by the systems, devices, methods and computer program products according to various embodiments of the present disclosure. Therefore, each block in the flowchart or block diagram can represent a module, segment, or portion of program code, which includes one or more executable instructions to implement the specified logical function. It should also be noted that in certain other embodiments, the functions described by the blocks may not be performed in the order shown in the figures. For example, two blocks connected in the figures can actually be executed simultaneously, or in some cases can be executed in the opposite order of the icons depending on the functions involved. It should also be noted that each block of the block diagram and / or flowchart, and the combination of blocks in the block diagram and / or flowchart, can be implemented by a system based on dedicated hardware, or by a combination of dedicated hardware and computer instructions to perform specific functions or operations.
[0239] While various embodiments of the present disclosure have been described above, the foregoing description is intended to be illustrative, non-exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is selected to best explain the principles of the embodiments, their practical applications, or technical improvements to marketed technologies, or to enable others skilled in the art to understand the embodiments disclosed herein.
[0240] Note that the technology disclosed in this specification can have the following configurations.
[0241] (1) An electronic device on a server device side, the electronic device comprising:
[0242] a processing circuit, the processing circuit being configured to:
[0243] Obtaining vehicle information of a first vehicle performing ferrying;
[0244] obtaining ferry-related information from ferry-related equipment;
[0245] generating vehicle ferry auxiliary information based on the vehicle information of the first vehicle and the ferry-related information; and
[0246] The vehicle ferry assistance information is provided to at least one of the first vehicle and the ferry-related equipment.
[0247] (2) The electronic device according to (1), wherein
[0248] The vehicle information includes at least one of the following information: vehicle reservation information, vehicle location information, vehicle size information, and vehicle weight information.
[0249] The ferry-related equipment includes shore-side equipment installed at the ferry terminal, the ferry-related information includes shore-side information related to the ferry terminal, and the shore-side information includes at least one of ferry schedule information, security inspection information, weighing and charging information, and waiting area information of the ferry terminal.
[0250] The processing circuit is configured to generate at least one of a ferry reservation result, a security inspection result, weighing and charging information, and ferry terminal guidance information of the first vehicle as the vehicle ferry auxiliary information based on the vehicle information and the shore information.
[0251] (3) The electronic device according to (1), wherein
[0252] The vehicle information includes at least one of the following information: vehicle position information, vehicle orientation information, vehicle body size information, vehicle chassis height information, vehicle weight information, and vehicle speed information.
[0253] The ferry-related equipment includes ferry-side equipment installed on the ferry boarded by the first vehicle, the ferry-related information includes ferry information related to the ferry, and the ferry information includes at least one of information about the ferry's boarding and disembarking ramp, information about the hydrological environment of the ferry, and information about the parking environment on the ferry.
[0254] The processing circuit is configured to determine a collision risk between the first vehicle and the ferry based on the vehicle information and the ferry information.
[0255] (4) The electronic device according to (3), wherein
[0256] The processing circuit is configured to:
[0257] Obtaining vehicle information of a second vehicle performing the ferrying;
[0258] The collision risk between the first vehicle and the second vehicle is determined based on the vehicle information of the first vehicle and the second vehicle and the ferry information.
[0259] (5) The electronic device according to (3) or (4), wherein
[0260] The processing circuit is configured to: generate collision warning information when the collision risk exceeds a preset collision risk threshold, and provide the information as the vehicle ferry assistance information to at least one of the first vehicle and the ferry.
[0261] (6) The electronic device according to (5), wherein
[0262] The collision warning information is used to prompt at least one of the following information: type of collision risk, relative position of the collision risk target and the first vehicle, relative distance between the collision risk target and the first vehicle, collision risk level, and type of collision risk target.
[0263] (7) The electronic device according to (1), wherein
[0264] The vehicle information includes at least one of the following information: vehicle position information, vehicle size information, vehicle weight information, vehicle type information, and vehicle center of gravity information.
[0265] The ferry-related equipment includes ferry-side equipment installed on the ferry boarded by the first vehicle, the ferry-related information includes ferry information related to the ferry, and the ferry information includes at least one of loading information of the ferry, information about the parking environment on the ferry, and information about the hydrological environment in which the ferry is located.
[0266] The processing circuit is configured to:
[0267] obtaining vehicle information of a plurality of first vehicles;
[0268] Parking guidance information for guiding the plurality of first vehicles to park on a parking deck is generated as the vehicle ferry assistance information based on the vehicle information of the plurality of first vehicles and the ferry information.
[0269] (8) The electronic device according to (7), wherein
[0270] The parking guidance information includes parking safety information dynamically determined based on the vehicle information of the plurality of first vehicles and the ferry information, wherein the parking safety information includes at least one of a parking space size, a parking safety distance, a vehicle rolling amplitude, and whether lashing is required.
[0271] (9) The electronic device according to (7), wherein
[0272] The parking guidance information includes parking space distribution information dynamically planned according to the vehicle information of the plurality of first vehicles and the ferry information,
[0273] The processing circuit is configured to:
[0274] providing the parking space distribution information to the ferry as the vehicle ferry auxiliary information, so that the ferry can display the parking space distribution on a parking deck; and / or
[0275] Information on a corresponding parking space of each first vehicle is provided to each first vehicle of the plurality of first vehicles.
[0276] (10) The electronic device according to (7), wherein
[0277] The parking guidance information is generated by dynamically allocating loads to the ferry and the plurality of first vehicles.
[0278] (11) The electronic device according to (1), wherein
[0279] The processing circuit is configured to:
[0280] acquiring vehicle information of the first vehicle from the first vehicle; and / or
[0281] Vehicle information of the first vehicle sensed by the ferry-related device is acquired.
[0282] (12) The electronic device according to (1), wherein
[0283] The processing circuit is configured to:
[0284] The vehicle information and the ferry-related information are obtained via a vehicle-to-vehicle communication link.
[0285] (13) A shore-side device provided at a ferry terminal, comprising:
[0286] a processing circuit, the processing circuit being configured to:
[0287] Get vehicle information of the vehicle making the ferry;
[0288] Obtaining shore-side information related to the ferry terminal;
[0289] generating vehicle ferry auxiliary information based on the vehicle information of the vehicle and the shore-side information; and
[0290] The vehicle ferry assistance information is provided to the vehicle.
[0291] (14) The shore-side equipment according to (13), wherein
[0292] The vehicle information includes at least one of the following information: vehicle reservation information, vehicle location information, vehicle size information, and vehicle weight information.
[0293] The shore-side information includes at least one of the ferry schedule information, security information, weighing and charging information, and waiting area information of the ferry terminal.
[0294] The processing circuit is configured to generate at least one of the vehicle's ferry reservation result, security inspection result, weighing and charging information, and ferry terminal guidance information based on the vehicle information and the shore information as the vehicle ferry auxiliary information.
[0295] (15) The shore-side equipment according to (13), wherein:
[0296] The shore-side equipment further comprises one or more sensors,
[0297] The processing circuit is configured to sense the vehicle information of the vehicle and the shore-side information via the one or more sensors.
[0298] (16) The shore-side equipment according to (13), wherein:
[0299] The processing circuit is configured to obtain vehicle information of the vehicle from a vehicle networking server device in communication with the vehicle via a vehicle networking communication link.
[0300] (17) The shore-side equipment according to (13), wherein:
[0301] The processing circuit is configured to provide the vehicle ferry assistance information to an onboard unit disposed in the vehicle via a vehicle-to-vehicle communication link.
[0302] (18) The shore-side equipment according to (13), wherein:
[0303] The processing circuit is configured to provide the vehicle ferry auxiliary information to a vehicle networking server device via a vehicle networking communication link, so that the vehicle networking server device provides the vehicle ferry auxiliary information to a mobile intelligent terminal carried by the vehicle and carrying the vehicle networking communication protocol via the vehicle networking communication link.
[0304] (19) A ferry-side device provided on a ferry, comprising:
[0305] a processing circuit, the processing circuit being configured to:
[0306] obtaining vehicle information of a first vehicle boarding the ferry;
[0307] obtaining ferry information related to the ferry;
[0308] generating vehicle ferry auxiliary information based on the vehicle information of the first vehicle and the ferry information; and
[0309] The vehicle ferry assistance information is provided to the first vehicle.
[0310] (20) The ferry-side equipment according to (19), wherein:
[0311] The vehicle information includes at least one of the following information: vehicle position information, vehicle orientation information, vehicle body size information, vehicle chassis height information, vehicle weight information, and vehicle speed information.
[0312] The ferry information includes at least one of information about the boarding and disembarking ramp of the ferry, information about the hydrological environment of the ferry, and information about the parking environment on the ferry.
[0313] The processing circuit is configured to determine a collision risk between the first vehicle and the ferry based on the vehicle information and the ferry information.
[0314] (21) The ferry-side equipment according to (20), wherein
[0315] The processing circuit is configured to:
[0316] obtaining vehicle information of a second vehicle boarding the ferry;
[0317] The collision risk between the first vehicle and the second vehicle is determined based on the vehicle information of the first vehicle and the second vehicle and the ferry information.
[0318] (22) The ferry-side equipment according to (20) or (21), wherein:
[0319] The processing circuit is configured to: generate collision warning information when the collision risk exceeds a preset collision risk threshold, and provide the information as the vehicle ferry assistance information to the first vehicle.
[0320] (23) The ferry-side equipment according to (22), wherein:
[0321] The collision warning information is used to prompt at least one of the following information: type of collision risk, relative position of the collision risk target and the first vehicle, relative distance between the collision risk target and the first vehicle, collision risk level, and type of collision risk target.
[0322] (24) The ferry-side equipment according to (19), wherein:
[0323] The vehicle information includes at least one of the following information: vehicle position information, vehicle size information, vehicle weight information, vehicle type information, and vehicle center of gravity information.
[0324] The ferry information includes at least one of the ferry's loading information, the ferry's parking environment information, and the ferry's hydrological environment information.
[0325] The processing circuit is configured to:
[0326] obtaining vehicle information of a plurality of first vehicles;
[0327] Parking guidance information for guiding the plurality of first vehicles to park on a parking deck is generated as the vehicle ferry assistance information based on the vehicle information of the plurality of first vehicles and the ferry information.
[0328] (25) The ferry-side equipment according to (24), wherein:
[0329] The parking guidance information includes parking safety information dynamically determined based on the vehicle information of the plurality of first vehicles and the ferry information, wherein the parking safety information includes at least one of a parking space size, a parking safety distance, a vehicle rolling amplitude, and whether lashing is required.
[0330] (26) The ferry-side equipment according to (24), wherein:
[0331] The parking guidance information includes parking space distribution information dynamically planned according to the vehicle information of the plurality of first vehicles and the ferry information,
[0332] The processing circuit is configured to:
[0333] displaying the parking space distribution on the parking deck of the ferry according to the parking space distribution information; and / or
[0334] Information on a corresponding parking space of each first vehicle is provided to each first vehicle of the plurality of first vehicles.
[0335] (27) The ferry-side equipment according to (24), wherein:
[0336] The parking guidance information is generated by dynamically allocating loads to the ferry and the plurality of first vehicles.
[0337] (28) The ferry-side equipment according to (19), wherein:
[0338] The ferry side equipment also includes one or more sensors,
[0339] The processing circuit is configured to sense vehicle information of the first vehicle and the ferry information via the one or more sensors.
[0340] (29) The ferry-side equipment according to (19), wherein:
[0341] The processing circuit is configured to obtain vehicle information of the first vehicle from a vehicle networking server device in communication with the first vehicle via a vehicle networking communication link.
[0342] (30) The ferry-side equipment according to (19), wherein:
[0343] The processing circuit is configured to provide the vehicle ferry assistance information to an onboard unit disposed in the first vehicle via a vehicle-to-vehicle communication link.
[0344] (31) The ferry-side equipment according to (19), wherein:
[0345] The processing circuit is configured to provide the vehicle ferry auxiliary information to a vehicle networking server device via a vehicle networking communication link, so that the vehicle networking server device provides the vehicle ferry auxiliary information to a mobile intelligent terminal carried by the first vehicle and carrying the vehicle networking communication protocol via the vehicle networking communication link.
[0346] (32) An electronic device for a vehicle, the electronic device comprising:
[0347] a processing circuit, the processing circuit being configured to:
[0348] In response to control information from a server device or a ferry-related device, providing vehicle information of the vehicle to the server device for the server device or the ferry-related device to generate vehicle ferry auxiliary information; and
[0349] The vehicle ferry assistance information is obtained from the server device or the ferry-related device to assist the vehicle in ferrying.
[0350] (33) The electronic device on the vehicle side according to (32), wherein
[0351] The electronic device includes an on-board unit based on the Internet of Vehicles communication protocol,
[0352] The processing circuit is configured to obtain the vehicle ferry auxiliary information from a ferry-related device via a vehicle-to-vehicle communication link.
[0353] (34) The electronic device on the vehicle side according to (32), wherein
[0354] The electronic device includes a mobile smart terminal that carries the Internet of Vehicles communication protocol,
[0355] The processing circuit is configured to obtain the vehicle ferry assistance information from a server device via a vehicle network communication link.
[0356] (35) The electronic device on the vehicle side according to (32), wherein:
[0357] The electronic device further comprises one or more sensors,
[0358] The processing circuit is configured to sense the vehicle information via the one or more sensors in response to the control information.
[0359] (36) A communication method for a server device, comprising:
[0360] Get vehicle information of the vehicle making the ferry;
[0361] obtaining ferry-related information from ferry-related equipment;
[0362] generating vehicle ferry auxiliary information based on the vehicle information of the vehicle and the ferry-related information; and
[0363] The vehicle ferry assistance information is provided to at least one of the vehicle and the ferry-related equipment.
[0364] (37) A communication method for shore-side equipment provided at a ferry terminal, comprising:
[0365] Get vehicle information of the vehicle making the ferry;
[0366] Obtaining shore-side information related to the ferry terminal;
[0367] generating vehicle ferry auxiliary information based on the vehicle information of the vehicle and the shore-side information; and
[0368] The vehicle ferry assistance information is provided to the vehicle.
[0369] (38) A communication method for a ferry-side device provided on a ferry, comprising:
[0370] obtaining vehicle information of vehicles boarding the ferry;
[0371] obtaining ferry information related to the ferry;
[0372] generating vehicle ferry auxiliary information based on the vehicle information of the vehicle and the ferry information; and
[0373] The vehicle ferry assistance information is provided to the vehicle.
[0374] (39) A communication method for a vehicle, comprising:
[0375] In response to control information from a server device or a ferry-related device, providing vehicle information of the vehicle to the server device for the server device or the ferry-related device to generate vehicle ferry auxiliary information; and
[0376] The vehicle ferry assistance information is obtained from the server device or the ferry-related device to assist the vehicle in ferrying.
[0377] (40) A computer-readable storage medium comprising executable instructions, which, when executed by an information processing device, causes the information processing device to execute the communication method described in any one of (36) to (39).
[0378] (41) A computer program product comprising a computer program, wherein when the computer program is executed by a processor, the processor is caused to execute the communication method described in any one of (36) to (39).
Claims
1. An electronic device on a server device side, the electronic device comprising: a processing circuit, the processing circuit being configured to: Obtaining vehicle information of a first vehicle performing ferrying; obtaining ferry-related information from ferry-related equipment; generating vehicle ferry auxiliary information based on the vehicle information of the first vehicle and the ferry-related information; as well as The vehicle ferry assistance information is provided to at least one of the first vehicle and the ferry-related equipment.
2. The electronic device according to claim 1, wherein The vehicle information includes at least one of the following information: vehicle reservation information, vehicle location information, vehicle size information, and vehicle weight information. The ferry-related equipment includes shore-side equipment installed at the ferry terminal, the ferry-related information includes shore-side information related to the ferry terminal, and the shore-side information includes at least one of ferry schedule information, security inspection information, weighing and charging information, and waiting area information of the ferry terminal. The processing circuit is configured to generate at least one of a ferry reservation result, a security inspection result, weighing and charging information, and ferry terminal guidance information of the first vehicle as the vehicle ferry auxiliary information based on the vehicle information and the shore information.
3. The electronic device according to claim 1, wherein The vehicle information includes at least one of the following information: vehicle position information, vehicle orientation information, vehicle body size information, vehicle chassis height information, vehicle weight information, and vehicle speed information. The ferry-related equipment includes ferry-side equipment installed on the ferry boarded by the first vehicle, the ferry-related information includes ferry information related to the ferry, and the ferry information includes at least one of information about the ferry's boarding and disembarking ramp, information about the hydrological environment of the ferry, and information about the parking environment on the ferry. The processing circuit is configured to: determine the first vehicle and the ferry information according to the vehicle information and the ferry information Collision risk of said ferry.
4. The electronic device according to claim 3, wherein The processing circuit is configured to: Obtaining vehicle information of a second vehicle performing the ferrying; The collision risk between the first vehicle and the second vehicle is determined based on the vehicle information of the first vehicle and the second vehicle and the ferry information.
5. The electronic device according to claim 3 or 4, wherein: The processing circuit is configured to: generate collision warning information when the collision risk exceeds a preset collision risk threshold, and provide the information as the vehicle ferry assistance information to at least one of the first vehicle and the ferry. The electronic device according to claim 5 , wherein: The collision warning information is used to prompt at least one of the following information: type of collision risk, relative position of the collision risk target and the first vehicle, relative distance between the collision risk target and the first vehicle, collision risk level, and type of collision risk target.
7. The electronic device according to claim 1, wherein The vehicle information includes at least one of the following information: vehicle position information, vehicle size information, vehicle weight information, vehicle type information, and vehicle center of gravity information. The ferry-related equipment includes ferry-side equipment installed on the ferry boarded by the first vehicle, the ferry-related information includes ferry information related to the ferry, and the ferry information includes at least one of loading information of the ferry, information about the parking environment on the ferry, and information about the hydrological environment in which the ferry is located. The processing circuit is configured to: obtaining vehicle information of a plurality of first vehicles; Parking guidance information for guiding the plurality of first vehicles to park on a parking deck is generated as the vehicle ferry assistance information based on the vehicle information of the plurality of first vehicles and the ferry information.
8. The electronic device according to claim 7, wherein: The parking guidance information includes parking safety information dynamically determined based on the vehicle information of the plurality of first vehicles and the ferry information, wherein the parking safety information includes at least one of a parking space size, a parking safety distance, a vehicle rolling amplitude, and whether lashing is required.
9. The electronic device according to claim 7, wherein: The parking guidance information includes parking space distribution information dynamically planned according to the vehicle information of the plurality of first vehicles and the ferry information, The processing circuit is configured to: providing the parking space distribution information to the ferry as the vehicle ferry auxiliary information, so that the ferry can display the parking space distribution on a parking deck; and / or Information on a corresponding parking space of each first vehicle is provided to each first vehicle of the plurality of first vehicles.
10. The electronic device according to claim 7, wherein The parking guidance information is generated by dynamically allocating loads to the ferry and the plurality of first vehicles.
11. The electronic device according to claim 1, wherein The processing circuit is configured to: acquiring vehicle information of the first vehicle from the first vehicle; and / or Vehicle information of the first vehicle sensed by the ferry-related device is acquired.
12. The electronic device according to claim 1, wherein The processing circuit is configured to: The vehicle information and the ferry-related information are obtained via a vehicle-to-vehicle communication link.
13. A shore-side device provided at a ferry terminal, comprising: a processing circuit, the processing circuit being configured to: Get vehicle information of the vehicle making the ferry; Obtaining shore-side information related to the ferry terminal; generating vehicle ferry auxiliary information according to the vehicle information of the vehicle and the shore-side information; as well as The vehicle ferry assistance information is provided to the vehicle.
14. The shore-side equipment according to claim 13, wherein: The vehicle information includes at least one of the following information: vehicle reservation information, vehicle location information, vehicle size information, and vehicle weight information. The shore-side information includes at least one of the ferry schedule information, security information, weighing and charging information, and waiting area information of the ferry terminal. The processing circuit is configured to generate at least one of the vehicle's ferry reservation result, security inspection result, weighing and charging information, and ferry terminal guidance information based on the vehicle information and the shore information as the vehicle ferry auxiliary information.
15. The shore-side equipment according to claim 13, wherein: The shore-side equipment further comprises one or more sensors, The processing circuit is configured to sense the vehicle information of the vehicle and the shore-side information via the one or more sensors.
16. The shore-side equipment according to claim 13, wherein: The processing circuit is configured to obtain vehicle information of the vehicle from a vehicle networking server device in communication with the vehicle via a vehicle networking communication link.
17. The shore-side equipment according to claim 13, wherein: The processing circuit is configured to provide the vehicle ferry assistance information to an onboard unit disposed in the vehicle via a vehicle-to-vehicle communication link.
18. The shore-side equipment according to claim 13, wherein: The processing circuit is configured to: provide the vehicle ferry assistance information to the vehicle network communication link via the vehicle network communication link The vehicle network server device is configured to provide the vehicle ferry auxiliary information to a mobile intelligent terminal carrying the vehicle network communication protocol and mounted on the vehicle via the vehicle network communication link.
19. A ferry-side device provided on a ferry, comprising: a processing circuit, the processing circuit being configured to: obtaining vehicle information of a first vehicle boarding the ferry; obtaining ferry information related to the ferry; generating vehicle ferry auxiliary information based on the vehicle information of the first vehicle and the ferry information; as well as The vehicle ferry assistance information is provided to the first vehicle.
20. The ferry-side device according to claim 19, wherein: The vehicle information includes at least one of the following information: vehicle position information, vehicle orientation information, vehicle body size information, vehicle chassis height information, vehicle weight information, and vehicle speed information. The ferry information includes at least one of information about the boarding and disembarking ramp of the ferry, information about the hydrological environment of the ferry, and information about the parking environment on the ferry. The processing circuit is configured to determine a collision risk between the first vehicle and the ferry based on the vehicle information and the ferry information.
21. The ferry-side device according to claim 20, wherein: The processing circuit is configured to: obtaining vehicle information of a second vehicle boarding the ferry; The collision risk between the first vehicle and the second vehicle is determined based on the vehicle information of the first vehicle and the second vehicle and the ferry information.
22. The ferry-side device according to claim 20 or 21, wherein: The processing circuit is configured to: generate collision warning information when the collision risk exceeds a preset collision risk threshold, and provide the information as the vehicle ferry assistance information to the first vehicle.
23. The ferry-side device according to claim 22, wherein: The collision warning information is used to prompt at least one of the following information: type of collision risk, relative position of the collision risk target and the first vehicle, relative distance between the collision risk target and the first vehicle, collision risk level, and type of collision risk target.
24. The ferry-side device according to claim 19, wherein: The vehicle information includes at least one of the following information: vehicle position information, vehicle size information, vehicle weight information, vehicle type information, and vehicle center of gravity information. The ferry information includes at least one of the ferry's loading information, the ferry's parking environment information, and the ferry's hydrological environment information. The processing circuit is configured to: obtaining vehicle information of a plurality of first vehicles; Parking guidance information for guiding the plurality of first vehicles to park on a parking deck is generated as the vehicle ferry assistance information based on the vehicle information of the plurality of first vehicles and the ferry information.
25. The ferry-side device according to claim 24, wherein: The parking guidance information includes parking safety information dynamically determined based on the vehicle information of the plurality of first vehicles and the ferry information, wherein the parking safety information includes at least one of a parking space size, a parking safety distance, a vehicle rolling amplitude, and whether lashing is required.
26. The ferry-side device according to claim 24, wherein: The parking guidance information includes parking space distribution information dynamically planned according to the vehicle information of the plurality of first vehicles and the ferry information, The processing circuit is configured to: displaying the parking space distribution on the parking deck of the ferry according to the parking space distribution information; and / or Information on a corresponding parking space of each first vehicle is provided to each first vehicle of the plurality of first vehicles.
27. The ferry-side device according to claim 24, wherein: The parking guidance information is generated by dynamically allocating loads to the ferry and the plurality of first vehicles.
28. The ferry-side device according to claim 19, wherein: The ferry side equipment also includes one or more sensors, The processing circuit is configured to sense vehicle information of the first vehicle and the ferry information via the one or more sensors.
29. The ferry-side device according to claim 19, wherein: The processing circuit is configured to obtain vehicle information of the first vehicle from a vehicle networking server device in communication with the first vehicle via a vehicle networking communication link.
30. The ferry-side device according to claim 19, wherein: The processing circuit is configured to provide the vehicle ferry assistance information to an onboard unit disposed in the first vehicle via a vehicle-to-vehicle communication link.
31. The ferry-side device according to claim 19, wherein: The processing circuit is configured to provide the vehicle ferry auxiliary information to a vehicle networking server device via a vehicle networking communication link, so that the vehicle networking server device provides the vehicle ferry auxiliary information to a mobile intelligent terminal carried by the first vehicle and carrying the vehicle networking communication protocol via the vehicle networking communication link.
32. An electronic device for a vehicle, the electronic device comprising: a processing circuit, the processing circuit being configured to: In response to control information from a server device or a device related to a ferry, providing vehicle information of the vehicle to the server device for the server device or the device related to the ferry to generate vehicle ferry auxiliary information; as well as The vehicle ferry assistance information is obtained from the server device or the ferry-related device to assist the vehicle in ferrying.
33. The vehicle-side electronic device according to claim 32, wherein: The electronic device includes an on-board unit based on the Internet of Vehicles communication protocol, The processing circuit is configured to obtain the vehicle ferry auxiliary information from a ferry-related device via a vehicle-to-vehicle communication link.
34. The vehicle-side electronic device according to claim 32, wherein: The electronic device includes a mobile smart terminal that carries the Internet of Vehicles communication protocol, The processing circuit is configured to obtain the vehicle ferry assistance information from a server device via a vehicle network communication link.
35. The vehicle-side electronic device according to claim 32, wherein: The electronic device further comprises one or more sensors, The processing circuit is configured to sense the vehicle information via the one or more sensors in response to the control information.
36. A communication method for a server device, comprising: Get vehicle information of the vehicle making the ferry; obtaining ferry-related information from ferry-related equipment; generating vehicle ferry auxiliary information based on the vehicle information of the vehicle and the ferry-related information; as well as The vehicle ferry assistance information is provided to at least one of the vehicle and the ferry-related equipment.
37. A communication method for shore-side equipment provided at a ferry terminal, comprising: Get vehicle information of the vehicle making the ferry; Obtaining shore-side information related to the ferry terminal; generating vehicle ferry auxiliary information according to the vehicle information of the vehicle and the shore-side information; as well as The vehicle ferry assistance information is provided to the vehicle.
38. A communication method for a ferry-side device provided on a ferry, comprising: obtaining vehicle information of vehicles boarding the ferry; obtaining ferry information related to the ferry; generating vehicle ferry auxiliary information according to the vehicle information of the vehicle and the ferry information; as well as The vehicle ferry assistance information is provided to the vehicle.
39. A communication method for a vehicle, comprising: In response to control information from a server device or a device related to a ferry, providing vehicle information of the vehicle to the server device for the server device or the device related to the ferry to generate vehicle ferry auxiliary information; as well as The vehicle ferry assistance information is obtained from the server device or the ferry-related device to assist the vehicle in ferrying.
40. A computer-readable storage medium comprising executable instructions, which, when executed by an information processing device, causes the information processing device to execute the communication method according to any one of claims 36 to 39.
41. A computer program product comprising a computer program, wherein when the computer program is executed by a processor, the processor is caused to perform the communication method according to any one of claims 36 to 39.
