Method for transmitting and receiving data in intelligent transport system, and apparatus for performing same

The method of collecting and transmitting sensing data about moving objects within ITS systems using V2X technology addresses the challenge of data accuracy and efficiency, enhancing real-time traffic management and safety by predicting and sharing object locations.

WO2024232653A1PCT designated stage expired Publication Date: 2024-11-14LG ELECTRONICS INC

Patent Information

Application Number
PCT/KR2024/006170
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-06-13
Filing Date
2024-05-08
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

Current Intelligent Transportation Systems (ITS) face challenges in accurately and efficiently transmitting and receiving data related to moving objects, particularly in real-time monitoring and processing of traffic conditions and vehicle movements.

Method used

A method involving a device that collects sensing data about a moving object, determines its movement path, and generates messages with N data sets related to the object's location at different time points, which can be past or future predictions, and transmits these messages to another device using wireless communication systems like V2X technology.

Benefits of technology

This approach enhances the accuracy and efficiency of data transmission and reception in ITS systems, improving traffic management and safety through real-time data sharing and prediction capabilities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024006170_14112024_PF_FP_ABST
    Figure KR2024006170_14112024_PF_FP_ABST
Patent Text Reader

Abstract

A method for transmitting information by a first device to a second device in an intelligent transport system (ITS) according to at least one of various embodiments may comprise: collecting sensing data about a moving object; obtaining information about a movement path of the object on the basis of the sensing data; generating a message for sharing the sensing data about the object; and transmitting the message to the second device, wherein the message includes N data sets configured on the basis of the information about the movement path of the object, and the N data sets are related to a location of the object at each of N different time points.
Need to check novelty before this filing date? Find Prior Art

Description

Method for transmitting and receiving data in an intelligent transportation system and device for performing the same

[0001] This specification relates to an intelligent transport system (ITS), and more specifically, to a method for transmitting and receiving data related to a moving object in an intelligent transport system and a device for performing the same.

[0002] A wireless communication system is a multiple access system that supports communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and multi-carrier frequency division multiple access (MC-FDMA).

[0003] Intelligent Transport Systems (ITS) utilize wireless communication technologies to manage transportation systems more efficiently and improve safety. ITS systems can monitor traffic conditions in real time and collect and process data using CCTV, sensor networks, GPS devices, and wireless communication systems. ITS systems can also support inter-vehicle communication, allowing vehicles to communicate with each other and share information about their surroundings to enhance autonomous driving and traffic safety.

[0004] The technical challenge to be achieved is to transmit and receive data related to moving objects more accurately and efficiently in intelligent transportation systems (ITS).

[0005] The technical challenges are not limited to those mentioned above, and other technical challenges not mentioned can be derived from the description below.

[0006] A method for transmitting information from a first device to a second device in an intelligent transportation system (ITS) according to one aspect comprises: collecting sensing data about a moving object; obtaining information about a movement path of the object based on the sensing data; generating a message for sharing the sensing data about the object; and transmitting the message to the second device, wherein the message includes N data sets set based on the information about the movement path of the object, and the N data sets can be related to a location of the object at each of N different points in time.

[0007] The position of the object at each of the N different points in time may be calculated by the first device based on information about the movement path of the object.

[0008] The movement path of the object is a path along which the object is predicted to move, and the N data sets may be related to the predicted location of the object for N future points in time.

[0009] The movement path of the above object is a path for the movement history of the object, and the N data sets can be related to the location of the object at N past points in time.

[0010] The sensing data for the above moving object may be obtained from vehicle-to-everything (V2X) messages received from other devices.

[0011] The above message may include information about a confidence level for the N data sets established based on the movement path of the object.

[0012] The above message may further include at least one data set set based on the sensing data in addition to the N data sets.

[0013] The above message may include information for distinguishing whether each data set is a data set established based on information about the movement path or a data set established based on the sensing data.

[0014] The sensing data may include first sensing data acquired within the sensing coverage of the first device and second sensing data acquired outside the sensing coverage of the first device.

[0015] The second sensing data may be received from another device having a sensing coverage different from the sensing coverage of the first device.

[0016] According to another aspect, a computer-readable recording medium having recorded thereon a program for performing the above-described method may be provided.

[0017] According to another aspect, a first device operating in an intelligent transportation system (ITS) includes a memory storing instructions; and a processor performing operations by executing the instructions, wherein the operations of the processor include collecting sensing data about a moving object; obtaining information about a movement path of the object based on the sensing data; generating a message for sharing the sensing data about the object; and transmitting the message to a second device, wherein the message includes N data sets set based on the information about the movement path of the object, and the N data sets can be related to a location of the object at each of N different points in time.

[0018] The first device may be a terminal, a vehicle, an RSU (road side unit), or a server.

[0019] According to one embodiment of the present disclosure, data transmission and reception for moving objects in an intelligent transportation system (ITS) can be performed more accurately and efficiently.

[0020] The effects that can be obtained in various embodiments are not limited to the effects mentioned above, and other effects not mentioned can be derived from the description below.

[0021] Figure 1 is a diagram for explaining V2X communication.

[0022] Figure 2 shows a radio protocol architecture for SL communication.

[0023] Figure 3 shows a terminal performing V2X or SL communication.

[0024] Figure 4 illustrates examples of various message transformations using the sensor data sharing message format.

[0025] Figure 5 illustrates an example of message alignment.

[0026] Figure 6 illustrates an example of selecting a V2X message including Path-history and Path-prediction information.

[0027] Figure 7 illustrates an example of selecting a V2X message that does not include Path-history or Path-prediction information.

[0028] Figure 8 illustrates an example of a CPM Path-history display.

[0029] Figure 9 illustrates an example of a CPM Path-Prediction representation.

[0030] Figure 10 illustrates an example of a CPM Path-history display.

[0031] Figure 11 is a diagram for explaining the data processing process for providing Path History / Prediction information.

[0032] Figure 12 illustrates an example of a method for utilizing detected objects and V2X received messages to improve / expand sensor area.

[0033] Figure 13 illustrates an example of message classification.

[0034] Figure 14 shows an example of a CPM display.

[0035] Figure 15 illustrates an example of a sensor data sharing message format input processing process.

[0036] FIG. 16 illustrates a flowchart of a method for transmitting data in an intelligent transportation system according to one embodiment.

[0037] Figure 17 illustrates a communication system applicable to the present disclosure.

[0038] Figure 18 illustrates a wireless device applicable to the present disclosure.

[0039] Figure 19 illustrates another example of a wireless device applicable to the present disclosure.

[0040] FIG. 20 illustrates a vehicle or autonomous vehicle applicable to the present disclosure.

[0041] Sidelink (SL) refers to a communication method that establishes a direct link between user equipment (UE), allowing voice or data to be exchanged directly between terminals without going through a base station (BS). SL is being considered as a solution to address the burden on base stations due to rapidly increasing data traffic.

[0042] V2X (vehicle-to-everything) refers to a communication technology that exchanges information with other vehicles, pedestrians, and infrastructure-based objects through wired / wireless communication. V2X can be divided into four types: V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), and V2P (vehicle-to-pedestrian). V2X communication can be provided through the PC5 interface and / or Uu interface.

[0043] Figure 1 is a diagram for comparing and explaining V2X communication based on RAT before NR and V2X communication based on NR.

[0044] In relation to V2X communication, in RATs prior to NR, methods for providing safety services based on V2X messages such as Basic Safety Message (BSM), Cooperative Awareness Message (CAM), and Decentralized Environmental Notification Message (DENM) were mainly discussed. V2X messages may include location information, dynamic information, attribute information, etc. For example, a terminal may transmit a CAM of a periodic message type and / or a DENM of an event triggered message type to another terminal.

[0045] For example, a CAM may include basic vehicle information such as dynamic vehicle status information, such as direction and speed, static vehicle data, such as dimensions, external lighting conditions, and route history. For example, a terminal may broadcast a CAM, and the latency of the CAM may be less than 100 ms. For example, in the event of an emergency, such as a vehicle breakdown or accident, a terminal may generate a DENM and transmit it to other terminals. For example, all vehicles within the transmission range of the terminal may receive the CAM and / or DENM. In this case, the DENM may have a higher priority than the CAM.

[0046] Since then, various V2X scenarios have been proposed in NR in relation to V2X communications. For example, various V2X scenarios may include vehicle platooning, advanced driving, extended sensors, and remote driving.

[0047] For example, based on vehicle platooning, vehicles can dynamically form groups and move together. For example, to perform platoon operations based on vehicle platooning, vehicles in the group can receive periodic data from the lead vehicle. For example, vehicles in the group can use this periodic data to narrow or widen the gap between vehicles.

[0048] For example, based on improved driving, vehicles can become semi-autonomous or fully automated. For example, each vehicle can adjust its trajectories or maneuvers based on data acquired from local sensors of nearby vehicles and / or nearby logical entities. Furthermore, for example, each vehicle can share driving intentions with nearby vehicles.

[0049] For example, based on extended sensors, raw data, processed data, or live video data acquired through local sensors can be exchanged between vehicles, logical entities, pedestrian terminals, and / or V2X application servers. Thus, for example, a vehicle can perceive its environment better than it can perceive using its own sensors.

[0050] For example, based on remote driving, a remote driver or V2X application can operate or control the remote vehicle for people who cannot drive or for remote vehicles located in hazardous environments. For example, in cases where the route is predictable, such as public transportation, cloud computing-based driving can be utilized to operate or control the remote vehicle. Additionally, access to a cloud-based back-end service platform, for example, can be considered for remote driving.

[0051] Meanwhile, a method to specify service requirements for various V2X scenarios, such as vehicle platooning, enhanced driving, expanded sensors, and remote driving, is being discussed in NR-based V2X communication.

[0052] Figure 2 illustrates a radio protocol architecture for SL communication. Specifically, Figure 2 (a) illustrates the user plane protocol stack of NR, and Figure 2 (b) illustrates the control plane protocol stack of NR.

[0053] Figure 3 shows a terminal performing V2X or SL communication.

[0054] Referring to FIG. 3, the term "terminal" in V2X or SL communications may primarily refer to a user's terminal. However, if a network device, such as a base station, transmits and receives signals according to a communication method between terminals, the base station may also be considered a type of terminal. For example, terminal 1 may be a first device (100), and terminal 2 may be a second device (200).

[0055] For example, terminal 1 can select a resource unit corresponding to a specific resource within a resource pool, which represents a set of resources. Then, terminal 1 can transmit an SL signal using the resource unit. For example, terminal 2, which is a receiving terminal, can be configured with a resource pool in which terminal 1 can transmit a signal, and can detect a signal from terminal 1 within the resource pool.

[0056] Here, if terminal 1 is within the connection range of the base station, the base station can inform terminal 1 of the resource pool. On the other hand, if terminal 1 is outside the connection range of the base station, another terminal can inform terminal 1 of the resource pool, or terminal 1 can use a pre-configured resource pool.

[0057] In general, a resource pool can be composed of multiple resource units, and each terminal can select one or multiple resource units to use for its SL signal transmission.

[0058] Meanwhile, the sensor data sharing service is a service that shares surrounding environment information captured by sensors installed in vehicles and RSUs using V2X communication.

[0059] Vehicles and RSUs can expand the detection area of ​​service users by sharing information about the current driving environment (road users, obstacles, etc. that do not support V2X communication) detected by their own sensors (Radar, LiDAR, infrared, Camera, Fusion Data, etc.) and can improve traffic safety by increasing the awareness of road conditions, including blind spots.

[0060] To support sensor data sharing services using V2X communication technology, SAE International defined SDSM (Sensor Data Sharing Message) in the J3224 standard document, and the European Telecommunications Standards Institute (ETSI) defined CPM (Collective Perception Message) in the TS 103 324 standard document.

[0061] The term sensor data sharing message format used in this specification may mean SDSM or CPM, but is not limited thereto.

[0062] Although there are differences in the types and scope of information that SDSM and CPM messages can include, they can commonly include information on one or more non-V2X road users (vehicles or VRUs without V2X functions) or road features (objects or obstacles) detected by a vehicle or RSU, as well as static information (size, type, etc.) and dynamic information (position, speed, direction, acceleration, etc.) of the detected objects (vehicles, VRUs, obstacles). In addition, based on the maximum object size information that can be included, SDSM can include up to 256 (DF_DetectedObjectList size) and CPM can include up to 128 (PerceivedObjectContainer size).

[0063] CPM can include information about the sensor used (sensor type, measurement range, etc.). When the SensorType field is set to itssaggregation, it can generate / transmit a Collective Perception Message by including / aggregating messages (e.g., CAM, BSM, PSM, VAM) received from multiple ITS Stations (ITS components of Vehicle, VRU, RSU, Center) as well as directly detected sensor data.

[0064] The approach to using these Aggregation messages is generally related to the infrastructure aspect and services provided by ITS central systems. Looking at various overseas ITS data linkage service / demo construction cases, we can see that internal C-ITS infrastructure data is linked based on Interchange nodes to be linked with external C-ITS clouds.

[0065] Interchange provides real-time data exchange and high scalability between different back-end systems and operates through multiple message brokers. Message brokers enable the collection, analysis, and processing of message data from various service providers. Interchanges can be implemented in both private and public settings. Each Interchange tracks all available data sets from connected service providers and stores metadata about that data, ensuring that all information about available data is shared across all Interchanges.

[0066] The method of processing / manufacturing message data collected from ITS central systems or interchanges can vary depending on various purposes and conditions, such as service purpose, standardization format, and channel capacity status. In order to preserve the original information contained in the message data, the collected message data can be retransmitted as is, but as in the example of the CPM standard requirements above, the received various messages can be analyzed / processed, aggregated, and sent in the sensor data sharing message (e.g. CPM) format. Since the sensor data sharing message format is structurally designed to comprehensively contain key information from messages between different heterogeneous types (e.g. Vehicle, VRU, Animal, Obstacle), its use can be considered when format integration is necessary. In addition to CPM, SDSM can also be used as a sensor data sharing message format.

[0067] Path-history / Path-prediction information sharing

[0068] Figure 4 illustrates examples of various message transformations using the sensor data sharing message format.

[0069] Path prediction / history information can be transmitted in the V2X message (e.g., BSM, CAM, PSM, VAM) format. However, since the sensor data sharing message format is designed to integrate messages between heterogeneous types (e.g., Vehicle, VRU, Animal, Obstacle) into a single format, it may be desirable to provide path prediction / history information in the sensor data sharing message format for the convenience of interoperability, such as format integration between service stake holders or operational issues related to each message version management.

[0070] CPM, one of the current sensor data sharing message formats, supports the aggregation and transmission of multiple messages. However, the current CPM standard does not define data fields for containing path history and path prediction information for V2X messages (e.g., BSM, CAM, PSM, VAM) transmitted by vehicles / VRUs.

[0071] The present disclosure relates to a method for sharing path-history and path-prediction information of vehicle-to-X messages (e.g., BSM, CAM, PSM, VAM) transmitted by a VRU for awareness purposes received from a server (or RSU / terminal) using a currently defined sensor data sharing message format.

[0072] The present disclosure also proposes a method for providing Path-history and Path-prediction information together when directly generating V2X messages for sharing sensor data, such as CPM, SDSM, and SBSM, as well as V2X messages for awareness purposes, such as BSM, CAM, PSM, and VAM, from a server (or RSU / terminal).

[0073] Another example of using a sensor data sharing message format is that SDSM can be used in addition to CPM.

[0074] The server (or RSU / terminal) classifies the messages by certain conditions through data parsing processing, and checks whether each Awareness message (e.g. BSM, CAM, PSM, VAM) sorted by certain criteria includes path-history and path-prediction information and whether it includes key field values ​​required for conversion to a sensor data sharing message format. Then, it can designate / decide the message to be converted.

[0075] When necessary, the server (or RSU / terminal) can directly generate sensor data sharing messages such as CPM, SDSM, and SBSM, and also specify / decide the target messages that need to be converted into the sensor data sharing V2X message format.

[0076] Once the target message(s) to be converted are specified, before being converted into a sensor data sharing message format, the server (or RSU / terminal) can notify the target Object of the target message information that its information is to be converted into a sensor data sharing message format generated by the server / RSU / terminal and transmitted to other V2X Objects.

[0077] The server (or RSU / terminal) parses the specified specific message(s) and sets the Mandatory Field using the sensor data sharing message format, and can display information (path prediction / history) for multiple points in time for a single terminal as multiple Object Lists. At this time, the data conversion / processing operations involved in displaying path prediction / history in the sensor data sharing message format can be performed differently depending on the message specification status.

[0078] When converting multiple designated messages containing path prediction / path history information, the path prediction / path history information contained in various pieces of information at a certain point in time can be referenced by the server (or RSU / terminal) and calculated / corrected using AI / ML, etc. This can be included in the sensor data sharing message format by applying improvements in accuracy compared to existing path history / prediction information, efficiency in the amount of data transmitted, etc.

[0079] When a single sensor data sharing message includes both object information detected by a sensor and information obtained from a message received by the ITS station that generates the sensor data sharing message, a method may be needed to distinguish between objects detected by a sensor and objects that must be obtained from a received message and have their data fields filled in, in terms of the V2X message exchange function.

[0080] (A) Sorting / classifying collected Awareness V2X messages

[0081] Path-history and path-prediction information may be about the past movement path and future predicted path of the object that transmitted the information (e.g., vehicle, VRU), respectively. This information is mainly included in various heterogeneous V2X messages (e.g., SAE - BSM, PSM, ETSI - CAM, VAM) for sharing awareness information of a moving object supporting V2X communication with its surroundings, and the corresponding information field or Container data frame including the field is mainly managed as an Optional attribute so that the corresponding information can be selectively included from the message transmission system.

[0082] Another characteristic of V2X messages with the Awareness attribute, which mainly includes Path-history and Path-prediction information, is that they are transmitted based on a specific time period, and therefore, when the server (or RSU / terminal) collects the information, multiple messages transmitted from the same object may be accumulated in chronological order.

[0083] To convert sensor data into a shared message format, the server sorts and categorizes these messages based on specific criteria. If the data is deemed to have low validity (e.g., real-time), it is deleted, freeing up server computing resources.

[0084] As an example of a sorting / classification condition for V2X messages for awareness purposes that may include path-history and path-prediction information, a method of 1) sorting in order of transmission objects, but for the same transmission object, 2) sorting in order of transmission time, may be considered.

[0085] Figure 5 illustrates an example of message alignment. In Figure 5, the information contained in each message and the transmission targets are identical objects. For example, the top-level BSM message contains information about Object A and was transmitted by Object A.

[0086] (B) Specifying the sorted / sorted conversion target message(s)

[0087] The criteria for determining a target message may vary, but if it contains path-history and path-prediction information, and essential basic information for creating a sensor data sharing message format exists within the message, it can be designated as a target message for conversion / restructuring. If this essential basic information data does not exist, it cannot be designated as a target message for conversion, or even if designated, proper conversion may not be possible.

[0088] The server (or RSU / terminal) determines whether each Awareness message (e.g. BSM, CAM, PSM, VAM) classified through parsing contains path-history and path-prediction information and whether it can be transmitted in a sensor data sharing message format, and then designates the message to be converted.

[0089] When necessary, the server (or RSU / terminal) directly generates sensor data sharing messages such as CPM, SDSM, and SBSM, and can also specify a designated target message that requires conversion into the sensor data sharing V2X message format.

[0090] Table 1 shows the required Awareness V2X message data information attributes and examples for the sensor data sharing message format that the server (or RSU / terminal) parses. In addition to the items listed in Table 1, all information data items of Awareness messages required to include data in the sensor data sharing message format can be included in the verification items.

[0091] 1. Data transmission Origination System information related fields and examples of main messages (1) PSMPersonalDeviceUserType (2) CAM, VAMStationType2. Object-related detailed information Related fields and main message examples (1) Positioning-related information i) BSM / PSMLatitude, Longitude, Elevation, PositionalAccuracy... / PathHistory / FullPositionVector ii) CAM, VAMreferencePosition (2) Information data generation time i) BSM / PSMDDateTime ii) CAM / VAMgenerationDeltaTime (3) Velocity and acceleration-related information Related fields and main message examples i) BSM / PSMSpeed, AccelerationSet4Way ii) CAM / VAMSpeed, longitudinalAcceleration (4) Direction-related information Related fields and main message examples i) BSM / PSM / CAM / VAMHeading, SteeringWheelAngle (5) Size-related fields and main message examples i) BSMVehicleSize ii) CAMVehicleLength, VehicleWidth (6) PathHistory-related fields and main message examples i) BSMBSMpartIIExtension / VehicleSafetyExtensions / PathHistory / PathHistoryPointList / ... ...ii) PSMPathHistory / PathHistoryPointListiii) CAMCoopAwareness / CamParameters / LowFrequencyContainer / BasicVehicleContainerLowFrequency / PathHistoryiv) VAMvruMotionPredictionContainer / pathHistory(7) PathPrediction information related fields and examples of main messagesi) BSMBSMpartIIExtension / VehicleSafetyExtensions / PathPrediction / RadiusOfCurvature / ... ...ii) PSMPathPrediction / RadiusOfCurvatureiii) CAM※ related information currently not availableiv) VAMvruMotionPredictionContainer / pathPrediction.

[0092] There are various criteria and conditions for specifying messages depending on various situations such as the type of service and whether specific information data is included in the collected message. However, for example, the messages to be converted can be specified as follows depending on the status of including key data.

[0093] (1) If, among the collected messages, both essential information data for the sensor data sharing message format and Path-history and Path-prediction information data are included, the most recent message containing the information data or N messages included in a specific point in time / section can be designated. Fig. 6 illustrates an example in which a message containing Path-history and Path-prediction information is designated as a conversion target message.

[0094] (2) Among the collected messages, for messages that do not include Path-history or Path-prediction information data but have essential information data for the sensor data sharing message format, multiple specific messages can be designated to sequentially or periodically select and aggregate these messages for the purpose of server (or RSU / terminal) judgment or implementation of Path-history or Path-prediction information utilization service requirements. Fig. 6 illustrates an example in which a message that does not include Path-history or Path-prediction information is designated as a conversion target message.

[0095] (3) In order to reduce the delay in analyzing and transmitting a received message, when a sensor data sharing message is directly generated from a server (or RSU / terminal), object information detected by the sensor and an ITS station reception message designated in a similar manner as above may be included together in the sensor data sharing message.

[0096] Once the target message(s) for conversion have been specified, and before being converted into a sensor data sharing message format, the server (or RSU / terminal) can notify the target Object of the target message information that its information will be converted into a sensor data sharing message format generated by the server / RSU / terminal and transmitted to other V2X Objects. The transmission of this information can be done in various ways, such as one-way transmission or requesting consent and then proceeding to the next step, depending on the purpose or operation method / policy of the service.

[0097] The above operation may be particularly necessary when the message generated by converting information into a sensor data sharing message format by the server / RSU / terminal is transmitted via broadcast / groupcast.

[0098] For example, when a server / RSU / terminal converts information into a sensor data sharing message format and transmits a message generated by the server / RSU / terminal to terminal A (located / driving in a specific area) (via network communication unicast), the server / RSU / terminal can generate and transmit a message so as not to include terminal A information as object information in the sensor data sharing message (generated by the server / RSU / terminal according to the method described above) sent to terminal A (for message size reduction purposes), so there may be no need for the server / RSU / terminal to separately notify whether the message generated by the server / RSU / terminal converts information into a sensor data sharing message format includes terminal A information.

[0099] For example, when a server / RSU / terminal converts information into a sensor data sharing message format and transmits a message generated by the server / RSU / terminal to terminal A (located / driving in a specific area) (unicast via network communication), if (only when) terminal A information is included as object information in the sensor data sharing message (generated by the server / RSU / terminal according to the method described above) sent to terminal A, the server / RSU / terminal can transmit a message to terminal A together with / separately from the sensor data sharing message notifying that the message includes terminal A information. In this case, an example of the content of the message notifying that the message includes terminal A information is described separately below.

[0100] For example, when a server / RSU / terminal converts information into a sensor data sharing message format and transmits (broadcast / groupcast) a message generated by the conversion to terminal A (located / driving in a specific area), information indicating that terminal A information is included in the sensor data sharing message can be included in the message (or transmitted as a separate message). An example of the content of the message indicating that terminal A information is included in the message is described separately below.

[0101] An example of information that can be included in a message to notify that the message generated by converting information into a sensor data sharing message format by the server / RSU / terminal includes terminal A information:

[0102] - ID(s) of the corresponding object(s) included in the message

[0103] - The ID that the object uses when sending messages it generates (e.g., the station ID included in the most recent message received by the server / RSU / terminal from the object).

[0104] - The ID of the message transmitted by the server / RSU / terminal that includes terminal A information as object information, and / or the station ID included in the message, and / or the time of message creation / transmission (e.g., message generation time), and / or the number of objects included in the message (e.g., the number of objects detected by the sensor, and / or the number of terminals that the server / RSU / terminal converted into object form based on the message it received, and / or the sum of the two)

[0105] Terminal A, which recognizes that its own information is included in a sensor data sharing message transmitted from a server / RSU / terminal, may not decode the sensor data sharing message or may omit / simplify reception-related operations. Alternatively, after decoding the message, it may accurately distinguish whether the object information in the message is itself or another terminal in its vicinity, thereby reducing the frequency / probability of false alarms and / or miss detections in use cases such as collision warning and VRU / vehicle awareness.

[0106] Meanwhile, even if the server / RSU / terminal does not separately inform the terminal that the message generated by converting information into the sensor data sharing message format includes information about a specific terminal (=terminal A), if the sensor data sharing message that the terminal A receives from the server / RSU / another terminal includes object information that matches the path history / prediction information included in the message that the terminal A previously transmitted (to the server / RSU / another terminal) to a certain level (and / or the number of path points related to the path history / prediction is a certain number), the terminal A may determine that the object is likely to be itself (or) and may omit the collision / risk assessment analysis / calculation operation between the object and itself (or) and may not display a collision warning with the object on the terminal (or) and may process it as a lower priority (especially in a situation where the collision / risk assessment analysis / calculation capability of the terminal is limited, compared to the collision / risk assessment analysis / calculation operation with other objects).

[0107] (C) Convert the data of the specified conversion target message(s) into the sensor data sharing message format.

[0108] The server (or RSU / terminal) parses the target message(s) and converts them into the contents of the Mandatory Field of the sensor data sharing message format and inputs them. Table 2 shows the main mandatory data information attributes and field examples for the sensor data sharing message format. In addition to Table 2, the Mandatory Field items that must be included in the sensor data sharing message format can be changed / added depending on the sensor data sharing message type.

[0109] The process of converting and entering the contents of the Mandatory Field of the sensor data sharing message format must determine and enter the value that can most closely match the contents of the mandatory information included in the message to be converted or within the same attribute information range.

[0110] 1. Data transmission Origination System information reference conversion example (1) Conversion target message → CPMCollectivePerceptionMessage / CpmParameters / CpmManagementContainer / StationType ::= INTEGER {unknown(0), pedestrian(1), cyclist(2), moped(3), motorcycle(4), passengerCar(5), bus(6), lightTruck(7), heavyTruck(8), trailer(9), specialVehicles(10), tram(11), roadSideUnit(15)} (0..255) - If the conversion target message is CAM, VAM, refer to the StationType information included in the message and input the same value among the selection values ​​above. - If the conversion target message is BSM, refer to the SupplementalVehicleExtensions / BasicVehicleClass information and input the most similar value among the selection values ​​above. If there is no BasicVehicleClass information, you can enter passengerCar (5). - If the message to be converted is PSM, refer to the PersonalDeviceUserType information and enter the most similar value among the selection values ​​above. (2) Message to be converted → SDSMEquipmentType = unknown (0), rsu (1), obu (2), vru (3) - If the message to be converted is CAM or VAM, refer to the StationType information included in the message and enter the most similar value to the selection value above. - If the message to be converted is BSM, refer to the SupplementalVehicleExtensions / BasicVehicleClass information and enter the most similar value to the selection value above. If there is no BasicVehicleClass information, you can enter vru (3).- If the message to be converted is PSM, refer to the PersonalDeviceUserType information and enter the value most similar to the selected value above. 2. Station Detailed Information Reference Conversion Example? Message generation time (1) Target message for conversion → CPMgenerationDeltaTime ::= INTEGER { oneMilliSec(1)} (0..65535) If the target message for conversion is CAM or VAM, enter the same value by referring to the generationDeltaTime information included in the message. If the target message for conversion is BSM / PSM, enter the same value by referring to the DSecond information included in the message. (2) Target message for conversion → SDSMMsgTimeStamp / DDay = INTEGER (0..31) -- units of daysMsgTimeStamp / DTime / DHour = INTEGER (0..31) -- units of hoursMsgTimeStamp / DTime / DMinute = INTEGER (0..60) -- units of minutesMsgTimeStamp / DTime / DSecond = INTEGER (0..65535) -- units of millisecondsRegardless of the type of message for conversion, the server (or Refer to the Log recording time information of the RSU / terminal and enter the value at the time the message was received. 3. Reference Position information reference conversion example (1) Conversion target message → CPMReferencePosition / Latitude, Longitude, positionConfidenceEllipse, altitude - If the conversion target message is CAM, VAM, refer to the referencePosition information included in the message and enter the same value among the selection values ​​above. - If the conversion target message is BSM, PSM, refer to the … / PathHistory / FullPositionVector information and enter the most similar value among the selection values ​​above.(2) Target message for conversion → SDSMPosition3D / Latitude, Longitude, Elevation(Optional), PositionalAccuracy - If the target message for conversion is CAM or VAM, refer to the referencePosition information included in the message and input the most similar value among the above selection values. - If the target message for conversion is BSM or PSM, refer to the … / PathHistory / FullPositionVector information and input the most similar value among the above selection values. 4. Example of conversion of Sensing Object list count information reference (1) Conversion target message → CPMCollectivePerceptionMessage / CpmParameters / NumberOfPerceivedObjects - If there is only one Object subject of Path-history and Prediction information to be included in one sensor data sharing message format regardless of the type of conversion target message, enter 1. - If the conversion target message is included in a sensor data sharing V2X message directly created by the server (or RSU / terminal), the object information detected by the sensor and the number of each object obtained from a designated ITS station reception message in a format similar to the example above can be entered.

[0111] The server (or RSU / terminal) parses the target message(s) and converts information (path prediction / history) from multiple points in time for a single terminal into multiple Object Lists and inputs them. The data conversion method may vary depending on the message specification status.

[0112] (1) Example of converting a single specified message containing path prediction or path history information.

[0113] For example, it is assumed that the message information to be converted includes Path prediction or Path history information, which is the most recent or specific point in time for a single terminal.

[0114] 1) Path history information

[0115] (i) Target message for conversion → CPM

[0116] PerceivedObjectContainer / PerceivedObject / objectID, TimeOfMeasurement, xDistance, yDistance

[0117] - If the message to be converted is BSM or PSM, enter the data element values ​​of PerceivedObject by referring to the information contained in the message … / PathHistory / PathHistoryPointList ::= SEQUENCE (SIZE(1..23)) OF PathHistoryPoint.

[0118] - If the message to be converted is CAM or VAM, enter the data element values ​​of PerceivedObject by referring to the PathHistory::= SEQUENCE (SIZE(0..40)) OF PathPoint information included in the message.

[0119] Fig. 8 illustrates an example of providing a path history by converting a target message into a CPM. Referring to Fig. 8, PerceivedObjectContainer provides information on the position, speed, size, etc. of the same Object A at multiple different (past) points in time T-01 to TN. StationDataContainer and FreeSpaceAddendumContainer are optional data containers provided when a target message is converted into a CPM defined in the ETSI standard, and may be omitted from the CPM depending on the embodiment. Meanwhile, a data container is a data bundle of a higher concept that groups detailed data with similar properties.

[0120] Meanwhile, StationDataContainer and FreeSpaceAddendumContainer (or their equivalent information) may be provided not only when the message to be converted is CPM as defined in the ETSI standard, but also when converted to SDSM as defined in the SAE standard.

[0121] (ii) Conversion target message → SDSM

[0122] DetectedObjectList / DetectedObjectData / DetectedObjectCommonData / ObjectType, ObjectID, MeasurementTimeOffset, PositionOffsetX, PositionOffsetY, Heading

[0123] - If the message to be converted is BSM or PSM, enter the data element values ​​of DetectedObjectData by referring to the information contained in the message … / PathHistory / PathHistoryPointList ::= SEQUENCE (SIZE(1..23)) OF PathHistoryPoint.

[0124] - If the message to be converted is CAM or VAM, enter the data element values ​​of DetectedObjectData by referring to the PathHistory::= SEQUENCE (SIZE(0..40)) OF PathPoint information included in the message.

[0125] (iii) Common requirements

[0126] By referring to the Path History related data frame PathHistoryPoint of the corresponding message or the Positioning information of the path point Points included in PathPoint, a single terminal object Object corresponding to the number of Point information and the path point Point Positioning information for each Object can be converted and included in the data frame related to each Sensing Object.

[0127] Data that should be displayed as an offset related to time and distance displays the difference value compared to the data frame referenced in the Reference Position information.

[0128] Basically, the same Object ID value can be used to indicate that the Object information is from multiple points in time for multiple identical Objects, but for the purpose of reducing the message size, it can be considered not to include things that do not change over time, such as the object ID or size, in all object information.

[0129] Confidence information refers to the confidence level of the path history / prediction. This information can be considered by referencing the confidence level and related information contained in the target message. If the server (or RSU / terminal) determines that the path history / prediction information contained in the target message is low in accuracy or does not exist, the server (or RSU / terminal) can directly improve the accuracy of the path history / prediction information. Furthermore, if the confidence level and related information are confirmed to have improved compared to the previous version, the improved confidence level value can be displayed.

[0130] 2) Path prediction information

[0131] (i) Target message for conversion → CPM

[0132] PerceivedObjectContainer / PerceivedObject / objectID, TimeOfMeasurement, xDistance, yDistance

[0133] - If the message to be converted is BSM or PSM, enter the data element values ​​of PerceivedObject by referring to the information contained in the message … / PathPrediction / RadiusOfCurvature ::= INTEGER (-32767..32767).

[0134] Since the information only means simple curvature information, the server (or RSU / terminal) must be able to predict the Positioning Point information of the future path for reference and generate Positioning Point information up to a certain Timing section point by analyzing information such as the speed, direction, and trajectory of the current Object. Based on this information and the number, it is converted into a data frame related to each Sensing Object of a single terminal object.

[0135] If the message to be converted is VAM, enter the data element values ​​of PerceivedObject by referring to the SequenceOfVruPathPoint / VruPathPoint / ReferencePosition and PathDeltaTime information included in the message.

[0136] - Referring to the positioning information of the path point points included in the future PathPoint-related data frame VRUPathPoint of the corresponding message, a single terminal object Object equal to the number of Point information and the path point Point Positioning information for each Object are converted and included in the data frame related to each Sensing Object.

[0137] Fig. 9 illustrates an example of providing path-prediction information by converting a conversion target message into a CPM. Referring to Fig. 9, PerceivedObjectContainer provides information on the position, velocity, size, etc. of the same Object A at multiple different (future) points in time T+01 to T+N. StationDataContainer and FreeSpaceAddendumContainer are optional data containers provided when a conversion target message is converted into a CPM defined in the ETSI standard, and may be omitted from the CPM depending on the embodiment. Meanwhile, a data container is a data bundle of a higher concept that groups detailed data with similar properties.

[0138] Meanwhile, StationDataContainer and FreeSpaceAddendumContainer (or their equivalent information) may be provided not only when the message to be converted is CPM as defined in the ETSI standard, but also when converted to SDSM as defined in the SAE standard.

[0139] (ii) Conversion target message → SDSM

[0140] DetectedObjectList / DetectedObjectData / DetectedObjectCommonData / ObjectType, ObjectID, MeasurementTimeOffset, PositionOffsetX, PositionOffsetY, Heading

[0141] - If the message to be converted is BSM or PSM, enter the data element values ​​of DetectedObjectData by referring to the information contained in the message … / PathPrediction / RadiusOfCurvature ::= INTEGER (-32767..32767).

[0142] Since the information only means simple curvature information, the server (or RSU / terminal) must be able to predict the Positioning Point information of the future path for reference and generate Positioning Point information up to a certain Timing section point by analyzing information such as the speed, direction, and trajectory of the current Object. Based on this information and the number, it is converted into a data frame related to each Sensing Object of a single terminal object.

[0143] - If the message to be converted is VAM, enter the data element values ​​of DetectedObjectData by referring to the SequenceOfVruPathPoint / VruPathPoint / ReferencePosition and PathDeltaTime information included in the message.

[0144] By referring to the positioning information of the path point points included in the future PathPoint-related data frame VRUPathPoint of the corresponding message, a single terminal object Object equal to the number of Point information and the path point Point Positioning information for each Object are converted and included in the data frame related to each Sensing Object.

[0145] (iii) Common requirements

[0146] Data that should be displayed as an offset related to time and distance displays the difference value compared to the data frame referenced in the Reference Position information.

[0147] Basically, the same Object ID value can be used to indicate that the Object information is from multiple points in time for multiple identical Objects, but for the purpose of reducing the message size, it can be considered not to include things that do not change over time, such as the object ID or size, in all object information.

[0148] Confidence information refers to the confidence level of the path history / prediction. This information can be considered by referencing the confidence level and related information contained in the target message. If the server (or RSU / terminal) determines that the path history / prediction information contained in the target message is low in accuracy or does not exist, the server (or RSU / terminal) can directly improve the accuracy of the path history / prediction information. Furthermore, if the confidence level and related information are confirmed to have improved compared to the previous version, the improved confidence level value can be displayed.

[0149] (2) Example of conversion of N designated messages containing path prediction or path history information

[0150] The target messages for conversion may contain path prediction or path history information of a single terminal for multiple sections / time points.

[0151] The way the server (or RSU / terminal) parses the messages to be converted and converts and displays information (path prediction / history) at multiple points in time for a single terminal into multiple Object Lists can be similar to the (1) single designated message conversion described above.

[0152] However, unlike (1) the example of converting a single designated message, (2) the example of converting N designated messages can reference the path prediction / path history information contained in various pieces of information at a certain point in time on the server (or RSU / terminal) and calculate / correct it using AI / ML, etc. Through this, accuracy can be improved compared to the existing path history / prediction information, the amount of data transmitted can be increased, etc., and included in the sensor data sharing message format.

[0153] For example, (1) in the example of converting one designated message, the number of PathPoint information must be equal to the number of Object Lists to be included in the sensor data sharing message format, but (2) in the example of converting N designated messages, the number of included Objects can be reduced as needed through the calculation / correction process of the server.

[0154] As another example, the server (or RSU / terminal) can detect errors in the location information included in the message information to be converted, correct them, and display the corrected values ​​in the path history and path prediction related fields.

[0155] (3) Example of conversion of multiple specified messages that do not include path prediction or path history information.

[0156] 1) Path history information

[0157] (i) Target message for conversion → CPM

[0158] PerceivedObjectContainer / PerceivedObject / objectID, TimeOfMeasurement, xDistance, yDistance

[0159] (ii) Conversion target message → SDSM

[0160] DetectedObjectList / DetectedObjectData / DetectedObjectCommonData / ObjectType, ObjectID, MeasurementTimeOffset, PositionOffsetX, PositionOffsetY, Heading

[0161] (iii) Common requirements

[0162] For the specified messages of that type, there is no PathHistory-related reference data field as shown below.

[0163] BSM, PSM: ... / PathHistory / PathHistoryPointList ::= SEQUENCE (SIZE(1..23)) OF PathHistoryPoint

[0164] CAM, VAM: PathHistory::= SEQUENCE (SIZE(0..40)) OF PathPoint

[0165] Therefore, instead of the number of points in the Path History path point Positioning information of the message, the number of single terminal objects corresponding to the specified number of messages and the Positioning information for each Object are converted and included in the data frame related to each Sensing Object.

[0166] Enter the data element values ​​of PerceivedObject and DetectedObjectData by referring to the Positioning, information data generation time, speed and acceleration, and direction-related information included in each corresponding message of the conversion target messages.

[0167] Since there is no PathHistory, the Reference Position information in the sensor data sharing message format inputs similar field values ​​by referencing the Positioning information of the first sequence message among the multiple conversion target messages.

[0168] Data that should be displayed as an offset related to time and distance displays the difference value compared to the data frame referenced in the Reference Position information.

[0169] Basically, the same Object ID value can be used to indicate that the Object information is from multiple points in time for multiple identical Objects, but for the purpose of reducing the message size, it can be considered not to include things that do not change over time, such as the object ID or size, in all object information.

[0170] Confidence information refers to the confidence level of the path history / prediction. This information can be considered by referencing the confidence level and related information contained in the target message. If the server (or RSU / terminal) determines that the path history / prediction information contained in the target message is low in accuracy or does not exist, the server (or RSU / terminal) can directly improve the accuracy of the path history / prediction information. Furthermore, if the confidence level and related information are confirmed to have improved compared to the previous version, the improved confidence level value can be displayed.

[0171] 2) Path prediction information

[0172] (i) Target message for conversion → CPM

[0173] PerceivedObjectContainer / PerceivedObject / objectID, TimeOfMeasurement, xDistance, yDistance

[0174] (ii) Conversion target message → SDSM

[0175] DetectedObjectList / DetectedObjectData / DetectedObjectCommonData / ObjectType, ObjectID, MeasurementTimeOffset, PositionOffsetX, PositionOffsetY, Heading

[0176] (iii) Common requirements

[0177] For the specified messages of that type, there is no PathPrediction-related reference data field as follows.

[0178] BSM, PSM → … / PathPrediction / RadiusOfCurvature ::= INTEGER (-32767..32767)

[0179] VAM → SequenceOfVruPathPoint / VruPathPoint / ReferencePosition, PathDeltaTime

[0180] Therefore, the server (or RSU / terminal) must be able to analyze the single terminal object Object for the specified number of messages and the positioning information, speed, and direction information for each Object to generate positioning point information up to a predicted certain timing interval. Based on this information and number, it is converted into a data frame related to each sensing object of the single terminal object.

[0181] For each message to be converted, the Positioning Point is reflected based on the server (or RSU / terminal) analysis results, and the data element values ​​of PerceivedObject and DetectedObjectData are entered by referring to the Positioning, information data generation time, speed and acceleration, and direction-related information contained in the corresponding message. For example, if the specified number of messages is 10, there may only be 3 Object Positioning Points up to the future point in time when this message is analyzed.

[0182] Data that should be displayed as an offset related to time and distance displays the difference value compared to the data frame referenced in the Reference Position information.

[0183] Basically, the same Object ID value can be used to indicate that the Object information is from multiple points in time for multiple identical Objects, but for the purpose of reducing the message size, it can be considered not to include things that do not change over time, such as the object ID or size, in all object information.

[0184] Confidence information refers to the confidence level of the path history / prediction. This information can be considered by referencing the confidence level and related information contained in the target message. If the server (or RSU / terminal) determines that the path history / prediction information contained in the target message is low in accuracy or does not exist, the server (or RSU / terminal) can directly improve the accuracy of the path history / prediction information. Furthermore, if the confidence level and related information are confirmed to have improved compared to the previous version, the improved confidence level value can be displayed.

[0185] (4) When a designated message(s) of a form similar to the example above is included together with sensor detection object information in a sensor data sharing message generated directly from the server (or RSU / terminal).

[0186] If it is necessary to reduce the latency required for a server (or RSU / terminal) to analyze a message it has received and then transmit it back to the terminals, it may be advantageous for the server (or RSU / terminal) to include sensor-detected object information and information obtained from the received message together when generating a single sensor data sharing message.

[0187] (4) A case may include (1) one designated message and (2) N designated message types as described above.

[0188] At this point, it may be necessary to distinguish between objects detected by sensors and objects acquired through received messages whose data fields must be filled in within the message. The reasons for distinguishing between objects detected by sensors and objects acquired through received messages whose data fields must be filled in within the message are roughly as follows.

[0189] - In the case of an object that must be acquired through a received message and fill in the data field, the receiving terminal may also need to recognize that the information contained in the sensor information data container is invalid.

[0190] - The confidence level definition of information related to the detected object and the confidence level definition of information related to the object that must be acquired through a received message and filled in the data field may be different.

[0191] Examples of key ways to distinguish this information include:

[0192] - A method can be considered to use the set of object IDs assigned to objects detected by sensors and the set of object IDs assignable to objects that must be acquired through received messages and fill in data fields without overlapping.

[0193] - In cases where a sensor data sharing message includes information on objects detected by the sensor and information obtained from a message received by the ITS station that generates the sensor data sharing message, such as NumberOfPerceivedObjects in CPM, it may be possible to include a data element that indicates the number of detected objects in the sensor data sharing message and a data element that indicates the number of objects obtained from the received message and filled in the data field in each message.

[0194] - The operation of a server / RSU of the type of the present disclosure fusing various types of messages to create a new type of information / type is considered as a new service that the server / RSU can provide, and when creating a sensor data sharing message, <message aggregation 구조로 생성되는 센서 데이터 공유 메시지> Although they use the same format, they may appear as different messages / services. In such cases, instead of including them in a single format, it may be possible to use different message IDs so that the receiving terminal can distinguish between the two formats by using the message ID.

[0195] Fig. 10 illustrates an example of a CPM Path-history representation. The CPM of Fig. 10 includes both a sensor detect object message and conversion target designation messages. Referring to Fig. 10, PerceivedObjectContainer provides information on the position, speed, size, etc. of the same Object A at multiple different (past) points in time T-01 to TN. In addition, SensorInformationContainer provides information (e.g., detection area, sensor type) directly sensed by the server (or RSU / terminal) for Object A (and / or other Objects). StationDataContainer and FreeSpaceAddendumContainer are optional data containers provided when a conversion target message is converted to a CPM defined in the ETSI standard, and may be omitted from the CPM depending on the embodiment. Meanwhile, a data container is a data bundle of a higher concept that groups detailed data with similar properties.

[0196] Meanwhile, StationDataContainer and FreeSpaceAddendumContainer (or their equivalent information) may be provided not only when the message to be converted is CPM as defined in the ETSI standard, but also when converted to SDSM as defined in the SAE standard.

[0197] For example, when ITS stations in various business domains exchange V2X messages with various messages for V2N2X-based ITS services, these entities are linked to the cloud server area, and message data is linked through the interchange function (or message, Information Broker).

[0198] In order to facilitate interoperability between entities and data maintainability during the data linkage process, when using a sensor data sharing message format that comprehensively covers various information, by applying the method proposed in this disclosure, a message can be created including Path History and Path Prediction information of a specific object that did not previously exist.

[0199] Additionally, a message may be created that includes both the converted message and the sensor detect object message.

[0200] Figure 11 is a diagram for explaining the data processing process for providing Path History / Prediction information.

[0201] Referring to FIG. 11, a device (e.g., server / RSU / terminal) can receive / collect V2X messages from other devices (A01). The device can classify / sort the received / collected V2X messages (A02). For example, V2X messages can be sorted by transmission object and / or transmission time order.

[0202] The device checks whether each V2X message includes essential data required for the sensor data sharing data format (A03), and V2X messages that do not include essential data can be excluded from conversion (A04).

[0203] The device can check whether each V2X message includes Path History / Prediction information (A05). If Path History / Prediction information is not included, the device designates N V2X messages as target messages for conversion (A06). If Path History / Prediction information is included, the device designates one or N V2X messages as target messages for conversion (A07).

[0204] The device can notify the target (owner) Object of the conversion target message that information from the target (owner) Object is about to be propagated (A08).

[0205] The device may determine whether to include sensor detection object information and conversion target messages together in the sensor data sharing data format (A09). If sensor detection object information and conversion target messages are included together in the sensor data sharing data format, the device may include information in the sensor data sharing data format that can distinguish whether the data is sensor detection object information or conversion target messages (A10).

[0206] If the conversion target message includes Path History / Prediction information, the device can generate a sensor data sharing data format based on the Path History / Prediction information of the conversion target message (A12).

[0207] If the conversion target message does not include Path History / Prediction information, the device can generate a sensor data sharing data format based on other information included in the conversion target message, such as positioning information, data generation time, speed, acceleration, and direction (A11).

[0208] Sharing Aggregation Information

[0209] Vehicles, RSUs, and servers equipped with their own sensors (Radar, LiDAR, Infrared, Camera, Fusion Data, etc.) for sensor data sharing services may fail to acquire sensor object information at a given location and time due to various and unexpected reasons, such as blind spots, interference, and sensor function problems within the sensor coverage area. Furthermore, sensor object information acquisition may fail due to the object location being outside the maximum range of the original sensor coverage area.

[0210] In this case, the quality of the service may be degraded because the information of sensor objects that are absolutely necessary for the purpose of a specific service cannot be included in the sensor data sharing message format, and if the requirements related to the sensor detection area range for a specific purpose service are expanded or changed, the system design to support the service may need to be modified.

[0211] Below, we propose a method to analyze objects detected and V2X messages received within the coverage area of ​​the server (or RSU / terminal)'s own sensor, and to display the detected object information and received V2X messages together in a sensor data sharing message to support a specific service. In addition, we propose a method to generate / transmit a sensor data sharing message that has the effect of expanding sensor coverage by identifying the existence / status of an object outside of sensor coverage based on the received message.

[0212] Through the method proposed in this disclosure, it is expected that the detection function can be improved by including V2X message information of objects that were not detected for unexpected reasons in the area coverage of the existing sensor, or the detection function area can be expanded by including V2X message information of objects located in the area coverage range of the newly expanded sensor.

[0213] Figure 12 illustrates an example of utilizing a detected object and a V2X received message to improve / expand the sensor area.

[0214] A server (or RSU / terminal) can obtain object information located inside / outside its sensing coverage through sensors installed / connected to the server (or RSU / terminal), but the server / RSU / terminal can also obtain it by receiving an awareness message (or proxy awareness message) and / or a message for (raw / processed) sensor data sharing from a neighboring server / RSU / terminal. Based on the analyzed result, the server (or RSU / terminal) determines the validity of the object information to be included in the sensor data sharing message format for a specific purpose. Criteria for determining validity may include whether the V2X message contains information sufficient to identify the object and the validity of the V2X service. In the process of determining the validity of the information by performing the function of parsing message information in the system, if the V2X message contains information that is not sufficient to identify the object, the information may be excluded from the candidates for inclusion.

[0215] Once the object information to be messaged is determined through validation, the server (or RSU / terminal) can notify the target Object of the message information to be converted that its information will be converted into a sensor data sharing message format generated by the server / RSU / terminal and transmitted to other V2X Objects.

[0216] From the perspective of benefit for expanding the sensing area, when generating a single sensor data sharing message directly from the server (or RSU / terminal), the requirements for including object information detected by the sensor and information acquired and processed from a designated ITS station reception message together in the sensor data sharing message format are organized, and for the expansion effect of collected V2X messages, the message format can be entered by considering Sensing coverage-In, out, In & out, etc. for the received messages.

[0217] Redundancy mitigation rules and / or object inclusion rules for objects to be included in messages (e.g. CPM, SDSM) defined in the sensor data sharing service standard can be processed in combination with the contents proposed in the present disclosure.

[0218] The information of objects to be included in the sensor data sharing message format can be numerical data of objects derived from sensor data, and can also be aggregated in the form of V2X messages. If both the sensor data and V2X message of the object in question are secured, the analyzed numerical data in the form of a fusion of the two can be input into the message format to improve data quality. The requirements for this input method may slightly vary depending on the sensor capability requirements of the server (or RSU / terminal) and the detection time of the object to be included in the sensor sharing message.

[0219] The server (or RSU / terminal) can arbitrarily designate an extended sensor coverage range and include object information detected by sensors within that range, as well as information obtained from messages received by the ITS station generating the sensor data sharing message, in the sensor data sharing message format. In this case, since the arbitrarily extended sensor coverage section is likely to include information received as V2X messages rather than object information detected by sensors, it must be possible to include numerical data information for the expanded sensor coverage in the message.

[0220] The server (or RSU / terminal) can use the extended / new data field to express which event the object information included in the message data format received by the receiving server (or RSU / terminal) of the sensor data sharing format message is related to. Alternatively, it can additionally express the detected source recognition information.

[0221] When a single sensor data sharing message format includes both object information detected by a sensor and information acquired or processed from a message received by an ITS station that generates the sensor data sharing message, a method may be needed to distinguish between objects detected by a sensor and objects that must be acquired from a received message and have their data fields filled in, in terms of the V2X message exchange function.

[0222] Classification of collected object information and data validity verification to determine whether to include / exclude collected object information data in sensor data sharing messages for expanding the sensing area.

[0223] The server (or RSU / terminal) can collect object information located inside / outside its sensing coverage to effectively support sensor data sharing services or other V2X services.

[0224] Such object information can be acquired through sensors (e.g., cameras, lidars, etc.) installed / connected to the server (or RSU / terminal), but the server (or RSU / terminal) can also acquire it by receiving an awareness message (e.g., CAM, VAM, BSM, PSM), a proxy awareness message (e.g., SBSM), and / or a message for (raw / processed) sensor data sharing (e.g., SDSM, CPM) from a surrounding server (or RSU / terminal). Therefore, the server (or RSU / terminal) capable of collecting the above information must be able to classify it based on specific conditions. Fig. 13 illustrates an example of message classification. For example, it can be classified within the system according to the inside / outside of the Sensing Coverage mentioned above and the information data acquisition method (e.g., Sensor, V2X Message).

[0225] Moving objects or V2X messages with the Awareness attribute are detected or transmitted based on a specific time cycle. Therefore, when the server (or RSU / terminal) collects these messages, multiple detection data and messages detected or transmitted from the same object may be accumulated in chronological order.

[0226] When collecting information data in this V2X message format, V2X messages must contain sufficient information to identify a single object, including detailed object information. The system must be able to verify whether this information is actually included in the message, thereby determining its validity. Examples of message fields containing object identification details for performing these system functions are shown in Table 3 below.

[0227] Object identification details related fields and examples of main messages (1) Positioning related information (i) BSM / PSMLatitude, Longitude, Elevation, PositionalAccuracy… / PathHistory / FullPositionVector (ii) CAM, VAMreferencePosition (2) Information data generation time (i) BSM / PSMDDateTime (ii) CAM / VAMgenerationDeltaTime (3) Velocity and acceleration related information related fields and examples of main messages (i) BSM / PSMSpeed, AccelerationSet4Way (ii) CAM / VAMSpeed, longitudinalAcceleration (4) Direction related information related fields and examples of main messages (i) BSM / PSM / CAM / VAMHeading, SteeringWheelAngle (5) Size related fields and examples of main messages (i) BSMVehicleSize (ii) CAMVehicleLength,VehicleWidth(6) PathHistory information related fields and main message examples (i) BSMBSMpartIIExtension / VehicleSafetyExtensions / PathHistory / PathHistoryPointList / … … (ii) PSMPathHistory / PathHistoryPointList(iii) CAMCoopAwareness / CamParameters / LowFrequencyContainer / BasicVehicleContainerLowFrequency / PathHistory(iv) VAMvruMotionPredictionContainer / pathHistory(7) PathPrediction information related fields and main message examples (i) BSMBSMpartIIExtension / VehicleSafetyExtensions / PathPrediction / RadiusOfCurvature / … … (ii) PSMPathPrediction / RadiusOfCurvature(iii) VAMvruMotionPredictionContainer / pathPrediction(iv) CAM,

[0228] When the system performs the function of parsing message information and determines the validity of information, if information contained in a V2X message is insufficient to identify an object, it may be excluded from the list of candidates for inclusion. For example, if the Confidence Level of a specific information data field falls below a certain required value, it may be considered low-confidence information and excluded. Examples of message fields containing such information are as follows.

[0229] CAM

[0230] BasicVehicleContainerHighFrequency / DF_Speed ​​ / SpeedConfidence / ::= INTEGER {equalOrWithinOneCentimeterPerSec(1), equalOrWithinOneMeterPerSec(100), outOfRange(126), unavailable(127)} (1..127) → If outOfRange(126)

[0231] The server (or RSU / terminal) can consider the validity of the V2X service as another criterion for collecting object information located inside / outside sensing coverage. In other words, rather than simply checking whether object identification information such as the above is included and collecting it, when collecting object information located inside / outside sensing coverage, if there are areas or objects that are irrelevant to a specific V2X service user, the server (or RSU / terminal) does not need to continue performing detection or include the received message.

[0232] For example, in basic safety-related use cases where awareness messages such as BSM and PSM can be received to recognize dangerous situations and warn users, there is no need to collect object information about objects that exist or events that occur outside of the safety-related scope of the user receiving the V2X message. Therefore, it may be more efficient to prioritize detection or collect V2X messages in areas that are relevant to the V2X user, i.e., within the valid reception range of the V2X service user.

[0233] In the case of collecting valid V2X service area / object information as a priority, by tracking movement and status information based on the location of the V2X receiving terminal, etc., priority detection areas / objects (e.g. areas / objects with high risk factors in the expected movement path and surrounding areas of the V2X terminal) and areas / objects to be detected later or areas / objects to be abandoned or omitted (e.g. areas where the V2X terminal has already passed, or areas with very low or no risk factors when considering the movement speed, direction, TTC (Time to collision), etc. among the expected movement path and surrounding areas of the V2X terminal) can be determined.

[0234] As examples of validating the above V2X service, the following two situations can be considered.

[0235] 1) Check the V2X service valid object / area judged from the perspective / viewpoint of the server (or RSU / terminal) that generates / transmits the message, and the sensor data message generated / transmitted may include valid object / area information that is unrelated to the receiving server (or RSU / terminal).

[0236] In these cases, it may be possible to set the message inclusion priority of objects expected to trigger an event higher than that of objects that are not. Examples of such events include obstacles, collisions, and risk situations. Objects associated with these events can be included in messages with a higher priority than other objects, thereby determining priority in the arrangement order of Object Data within the Data Frame, transmission order, etc.

[0237] In these cases, the receiving server (or RSU / terminal) may be able to use the extended / new data field to indicate in the message which event the object information contained in the received sensor data sharing data format is related to. For example, new event information data can be defined or input using existing ITIS Code information.

[0238] 2) The V2X service valid object / area judged from the perspective / viewpoint of the target server (or RSU / terminal) receiving the message is confirmed, and the sensor data message generated / transmitted can only include valid object / area information that is meaningful to the target server (or RSU / terminal) receiving the message.

[0239] In such cases, the server (or terminal / RSU) may be able to immediately send a direct event information message in addition to a sensor data sharing message when it detects a risk of accident or event.

[0240] Once the above validation is complete, the server (or RSU / terminal) can notify the target Object of the message information to be converted that its information will be converted into a sensor data sharing message format generated by the server / RSU / terminal and transmitted to other V2X Objects. Depending on the purpose or operating method / policy of the service, there may be various options for transmitting this information, such as one-way transmission or requesting consent and then proceeding to the next step.

[0241] Tracking information on objects located outside sensing coverage

[0242] When the existence of an object outside of its sensor coverage is recognized through the above validation, (a) the terminal transmitting the object information to itself requests that information including the object be continuously transmitted (for a specific time period), or (b) when a message including the object information is received but is not received (for a specific time period or longer), the server / RSU / terminal transmits a message to check whether the existence / status of the object has changed to the object, or to the server / RSU / terminal that detected the object and sent the sensor data sharing message, or to another ITS-station determined to be around the object, thereby performing an operation to track / identify the status / existence / location of the object.

[0243] Input the sensor data sharing message format of collected object information data for expanding the sensing area.

[0244] There may be several ways to input information designated to be transmitted in a sensor data sharing message format by checking the validity of information data about Sensing object information and V2X message information collected inside / outside the Sensing range as above.

[0245] From the perspective of benefit for expanding the sensing area, when generating a single sensor data sharing message directly from the server (or RSU / terminal), the requirements for including object information detected by the sensor and information acquired and processed from a designated ITS station reception message together in the sensor data sharing message format are organized, and for the expansion effect of collected V2X messages, the message format input for received messages can be considered in the following manner.

[0246] (1) Sensing coverage-In

[0247] (i) Information about objects that the server / RSU / terminal could not detect with its sensor can be included as a new object in a message for sensor data sharing generated by the server / RSU / terminal, and (ii) among the objects that the server / RSU / terminal detected with its sensor, if there is information (e.g., location, size, speed / acceleration / heading, path history / prediction) included in the message received by the server / RSU / terminal that has higher precision / reliability / accuracy than what the server / RSU / terminal judges / calculates with the information obtained by its sensor, the server / RSU / terminal can correct / modify and include the object information in the message for sensor data sharing generated by the server / RSU / terminal.

[0248] Redundancy mitigation rules and / or object inclusion schemes identical / similar to those mentioned in ETSI CPS TR / TS may be combined with methods (1) and (2) mentioned above to determine whether a message for sensor data sharing purposes generated / transmitted by a server / RSU / terminal is included or not.

[0249] (2) Sensing coverage-Out

[0250] It can be converted into object information format and included in a message for sensor data sharing generated by a server / RSU / terminal, or containers included in a received awareness (or proxy) message can be included in a message for sensor data sharing and sent, or the received (or proxy) awareness message can be forwarded to terminals around it.

[0251] When a server / RSU / terminal includes information about an ITS station located outside the coverage of its own sensor in a message for sensor data sharing (obtained from a message it has received), the sensor information of the sensor information container included in the message for sensor data sharing may include one or more of local aggregation, ITS-s aggregation, and fused object information. The fused object information may be a fusion of sensing information from multiple sensors installed in a single server / RSU / terminal, or a fusion of sensing information from sensors installed in different servers / RSUs / terminals by (a) server / RSU / terminal, or a fusion of sensing information acquired by the server / RSU / terminal itself (or by another server / RSU / terminal) and information acquired from a received V2X message.

[0252] (3) Sensing coverage-In & Out

[0253] When information on both objects included in sensing coverage and objects not included in sensing coverage is received, the message generated by the server / RSU / terminal may need to have new object information located inside / outside sensing coverage (not included in the previous message transmission) given a higher (or equal) priority than objects included in sensing coverage transmitted previously (or within a certain time period after the message transmission).

[0254] Additionally, the above operation may be applied only when the information of the ITS station obtained through the message received by the server / RSU / terminal has a precision / reliability / accuracy higher than a certain level (preliminarily set / promised).

[0255] (4) Distinction between sensor detect objects and objects recognized through message reception

[0256] When information on an object detected by a sensor and information data acquired or processed from a message received by an ITS station generating a sensor data sharing message are included in the same sensor data sharing message format, a method may be needed to distinguish whether the object is an object detected by a sensor or an object whose data field is set based on the received message.

[0257] How to display extended information in the sensing area of ​​the sensor data sharing message format

[0258] 1. Input conversion of ITS station information included in the message into object information.

[0259] The server (or RSU / terminal) parses the message(s) to be converted for validation and converts them into data to be included in the Data Frame related to the Sensing object information list in the sensor data sharing message format.

[0260] At this time, the object information entered in the Data Frame related to the Sensing object information list in the sensor data sharing message format is intended to expand the sensing area, so it is assumed that it is included together with the object information detected by the sensor.

[0261] The current standard contents of the Data Element field related to the Sensing object information list in the sensor data sharing message format include the Data Frame structures of "PerceivedObjectContainer" for CPM and "DetectedObjectList" for SDSM. Below are the main examples for filling out these Data Frame structures, but in addition to these examples, the field items that should be included in the Data Frame structures related to object information in the sensor data sharing message format can be changed / added depending on the type of sensor data sharing message, etc.

[0262] The process of converting and inputting the contents of the Data Frame in the sensor data sharing message format must determine and input the value that can most closely match the contents of the essential information included in the message to be converted or within the same attribute information range.

[0263] (1) Example of conversion of reference information related to sensor measurement time

[0264] (i) Target message for conversion → CPM

[0265] PerceivedObjectContainer / measurementDeltaTime DeltaTimeMilliSecondSigned

[0266] - If the message to be converted is CAM or VAM, enter the difference between the time the message was received by the server (or RSU / terminal) and the time the message was received by the server (or RSU / terminal) by referring to the generationDeltaTime information included in the message.

[0267] - If the message to be converted is BSM / PSM, enter the difference between the time the message was received by the server (or RSU / terminal) and the time the message was received by the server (or RSU / terminal) by referring to the DSecond information included in the message.

[0268] (ii) Conversion target message → SDSM

[0269] DetectedObjectData / DetectedObjectCommonData / MeasurementTimeOffset

[0270] - If the message to be converted is CAM or VAM, enter the difference between the time the message was received by the server (or RSU / terminal) and the time the message was received by the server (or RSU / terminal) by referring to the generationDeltaTime information included in the message.

[0271] - If the message to be converted is BSM / PSM, enter the difference between the time the message was received by the server (or RSU / terminal) and the time the message was received by the server (or RSU / terminal) by referring to the DSecond information included in the message.

[0272] (2) Example of conversion of sensor measurement relative position information reference

[0273] (i) Target message for conversion → CPM

[0274] PerceivedObjectContainer / position CartesianPosition3dWithConfidence(xCoordinate, yCoordinate, zCoordinate)

[0275] - If the conversion target message is CAM or VAM, the predicted relative position and accuracy information from the server (or RSU / terminal) mounted sensor position are entered into the DE information by referring to DF_Speed, DF_ReferencePosition, DF_Heading, DE_DriveDirection, etc.

[0276] - If the target message for conversion is BSM or PSM, the predicted values ​​of relative position and accuracy information from the server (or RSU / terminal) mounted sensor position are entered into the above DE information by referring to DE_Speed, DE_Latitude, DE_Longitude, DE_Elevation, DE_Heading, etc.

[0277] - The x, y, and z information displayed in the current CPM example represent East, North, and Vertical directions, respectively, and can also be displayed in other forms, such as Latitude, Longitude, and Elevation.

[0278] (ii) Conversion target message → SDSM

[0279] PositionOffsetXYZ / offsetX, offsetY, offsetZ ObjectDistance information

[0280] You can enter it using the same approach as the CPM example.

[0281] (3) Example of conversion of reference information related to the relative velocity of the sensor measurement object

[0282] (i) Target message for conversion → CPM

[0283] PerceivedObjectContainer / velocity Velocity3dWithConfidence

[0284] - If the message to be converted is CAM or VAM, the predicted values ​​of relative speed and accuracy information from the server (or RSU / terminal) mounted sensor location are entered into the DE information above by referring to DF_Speed, DF_ReferencePosition, DF_Heading, DE_DriveDirection, etc.

[0285] - If the target message for conversion is BSM or PSM, the predicted values ​​of relative speed and accuracy information from the server (or RSU / terminal) mounted sensor location are entered into the above DE information by referring to DE_Speed, DE_Latitude, DE_Longitude, DE_Elevation, DE_Heading, etc.

[0286] - The x, y, and z information displayed in the current CPM example represent East, North, and Vertical directions, respectively, and can also be displayed in other forms, such as Latitude, Longitude, and Elevation.

[0287] (ii) Conversion target message → SDSM

[0288] Speed, SpeedConfidence

[0289] - If the message to be converted is CAM or VAM, refer to DF_Speed ​​and enter the same or most similar value among the DE information above.

[0290] - If the target message for conversion is BSM or PSM, refer to DE_Speed ​​and input the same or most similar value among the above DE information. If there is no Confidence-related information to reference, you can also input the value determined by the server (or RSU / terminal).

[0291] (4) Example of conversion of reference information related to the relative acceleration of the sensor measurement object

[0292] (i) Target message for conversion → CPM

[0293] PerceivedObjectContainer / velocity Velocity3dWithConfidence

[0294] - If the message to be converted is CAM or VAM, refer to longitudinalAcceleration, lateralAcceleration, and verticalAcceleration and enter the same or most similar value among the above DE information.

[0295] - If the message to be converted is BSM or PSM, refer to DF_AccelerationSet4Way (long Acceleration, lat Acceleration, vert VerticalAcceleration, yaw YawRate) and input the same or most similar value among the above DE information.

[0296] (ii) Conversion target message → SDSM

[0297] AccelerationSet4Way / Acceleration, VerticalAcceleration, AccelerationConfidence, YawRate, YawRateConfidence

[0298] You can input data using the same approach as the CPM example. However, you can input data related to yawRate by referencing the yawRate-related Data Frame / Element included in each message.

[0299] (5) Example of conversion of reference information related to sensor measurement object type

[0300] (i) Target message for conversion → CPM

[0301] ObjectClassDescription / ClassConfidence, class CHOICE(VehicleSubclass or PersonSubclass or AnimalSubclass or AnimalSubclass)

[0302] - If the message to be converted is CAM or VAM, refer to the StationType information included in the message and enter the same value among the selection values ​​above.

[0303] - If the target message for conversion is BSM, refer to the SupplementalVehicleExtensions / BasicVehicleClass information and enter the most similar value among the above selection values. If there is no BasicVehicleClass information, you can enter passengerCar(5).

[0304] - If the message to be converted is PSM, refer to the PersonalDeviceUserType information and enter the most similar value among the above selection values.

[0305] (ii) Conversion target message → SDSM

[0306] DetectedObjectData / DetectedObjectCommonData / ObjectType, ClassificationConfidence

[0307] - If the message to be converted is CAM or VAM, refer to the StationType information included in the message and enter the value most similar to the selection value above.

[0308] - If the target message for conversion is BSM, refer to the SupplementalVehicleExtensions / BasicVehicleClass information and enter the value most similar to the selection value above. If there is no BasicVehicleClass information, you can enter vru (3).

[0309] - If the message to be converted is PSM, refer to the PersonalDeviceUserType information and enter the value most similar to the selection value above.

[0310] 2. Enter numerical data information to expand the coverage of sensor information.

[0311] The server (or RSU / terminal) can arbitrarily designate an extended sensor coverage range and include object information detected by sensors within the range and information data acquired or processed from messages received by the ITS station that generates the sensor data sharing message in the sensor data sharing message format. In this case, since the arbitrarily extended sensor coverage section is likely to include information received as a V2X message rather than object information detected by the sensor, numerical data information for the expanded sensor coverage should be included in the message so that the receiving system can recognize the expanded sensing results compared to the existing sensing area.

[0312] For a sensor data sharing message format with a Data Frame that can display data related to sensor information, it should be possible to display extended sensing area information using Sensor Type and Sensing (Detection) Area information, and, if necessary, to display various extended areas in numerical form by adding some information.

[0313] (1) Example of inputting information related to numerical data for expanding the coverage of sensor information

[0314] (i) CPM

[0315] SensorInformationContainer / SensorInformation

[0316] - Added new SensorInformation structure

[0317] SensorInformationContainer / SensorInformation / SensorType = itssaggregation(11)

[0318] - Enter the type related to the ITS Station receiving V2X message in the Sensor Type (itssaggregation)

[0319] DetectionArea / VehicleSensor or AreaRadial or AreaPolygon or AreaCircular ... etc.

[0320] - Input Sensing Area numerical data Input Data Frame information

[0321] (ii) SDSM

[0322] Currently, SDSM does not have a Data Frame that can display data related to Sensor information, but when a related Data Frame is added in the future, the same or most similar value among the above DF / DE information can be entered and displayed.

[0323] 3. Enter additional information as object information for ITS station information included in the message.

[0324] The server (or RSU / terminal) may be able to use the extended / new data field to indicate in the message which event the object information included in the message data format received by the receiving server (or RSU / terminal) of the sensor data sharing format message is related to. Alternatively, it may additionally indicate the detected source recognition information.

[0325] (1) Example of entering information related to event data

[0326] (i) CPM

[0327] PerceivedObjectContainer /

[0328] - Added new eventCase Data Frame structure

[0329] PerceivedObjectContainer / eventCase : : Select input among unknown(0), obstacle(1), collision(2), road_hazard_risk(3)...

[0330] (ii) SDSM

[0331] DetectedObjectData / DetectedObjectCommonData /

[0332] - Added a new eventCase Data Frame structure so that it can be entered using the same approach as the CPM example.

[0333] (2) Example of inputting information related to cognitive data

[0334] (i) CPM

[0335] PerceivedObjectContainer /

[0336] - Added new sourceData Data frame structure

[0337] PerceivedObjectContainer / sourceData / SourceType : : Select from Unknown(0), Sensor(1), ITS-S Message(2), Fusion(3)

[0338] PerceivedObjectContainer / sourceData / SensorID : : Select among Unknown(0), Lidar(1), Camera(2) ... ...

[0339] PerceivedObjectContainer / sourceData / MessageID : : Select among BSM(20), PSM(30), ...

[0340] ...

[0341] (ii) SDSM

[0342] DetectedObjectData / DetectedObjectCommonData /

[0343] - Added a new sourceData Data Frame structure so that it can be input using the same approach as the CPM example.

[0344] 4. Distinction between objects detected by the sensor and objects recognized through message reception

[0345] A distinction may be needed between objects detected by sensors and objects whose data fields are set based on received messages. The reasons for this distinction are as follows:

[0346] - For objects that must be acquired through a received message and fill in the data field, it may be necessary for the receiving terminal to recognize that the information contained in the sensor information data container is invalid.

[0347] - The confidence level definition of information related to the detected object and the confidence level definition of information related to the object that must be acquired through a received message and filled in the data field may be different.

[0348] Examples of key ways to distinguish this information include:

[0349] - A method can be considered to use the set of object IDs assigned to objects detected by sensors and the set of object IDs assignable to objects that must be acquired through received messages and fill in data fields without overlapping.

[0350] - In cases where a sensor data sharing message includes information on objects detected by the sensor and information obtained from a message received by the ITS station that generates the sensor data sharing message, such as NumberOfPerceivedObjects in CPM, it may be possible to include in the sensor data sharing message a data element that indicates the number of sensor detected objects and a data element that indicates the number of objects obtained from the received message and filled in the data field.

[0351] - The operation of a server / RSU of the type of the present disclosure fusing various types of messages to create a new type of information / type is considered as a new service that the server / RSU can provide, and when creating a sensor data sharing message, <message aggregation 구조로 생성되는 센서 데이터 공유 메시지> Although they use the same format, they may appear as different messages / services. In such cases, instead of including them in a single format, it may be possible to use different message IDs so that the receiving terminal can distinguish between the two formats using the message ID.

[0352] - It may be possible to add a small-sized Data Frame that can express the source recognition information detected for each Object Data included in the information Data Frame (e.g. PerceivedObjectContainer or DetectedObjectData) of sensor-detected objects included in the sensor data sharing message format, and include the source type (e.g. Unknown (0), Sensor (1), ITS-S Message (2), Fusion (3) ... ...), sensor ID, message ID (e.g. BSM (20), PSM (30), ... ), etc.

[0353] Fig. 14 illustrates an example of a CPM. In Fig. 14, Sensor detect object messages and ITS-S V2X messages are displayed together. Referring to Fig. 14, PerceivedObjectContainer includes a plurality of object information (e.g., location, speed, size, etc.). For example, Object A to Object D may be sensor detected object information directly detected by the ITS station, and Object E and Object F may be information acquired by the ITS station from a V2X message received from another ITS station. SensorInformationContainer may include first sensor information and second sensor information. The first sensor information may provide sensor information (e.g., sensor type, recognition area shape) for sensor detected object information directly detected by the ITS station, and the second sensor information may provide sensor information (e.g., sensor type, recognition area shape) acquired by the ITS station through a V2X message received from another ITS station.

[0354] StationDataContainer and FreeSpaceAddendumContainer are optional data containers provided when the target message is converted to CPM defined in the ETSI standard. Depending on the embodiment, they may be omitted from the CPM. Meanwhile, a data container is a data bundle of a higher concept that groups detailed data with similar properties.

[0355] Meanwhile, StationDataContainer and FreeSpaceAddendumContainer (or their equivalent information) may be provided not only when the message to be converted is CPM as defined in the ETSI standard, but also when converted to SDSM as defined in the SAE standard.

[0356] The ITS service operation layer standard is currently being standardized by dividing the service stages into Day-1 and Day-2 according to the technically feasible period, the degree of autonomous driving support, and whether basic safety support or additional convenience is provided. Day-2 services include platooning, VRU protection, sensor sharing service, and maneuver cooperation service that enhance traffic safety and improve driving and traffic convenience through autonomous driving support and additional convenience services.

[0357] The Sensor Sharing service is a service that shares information about the surrounding environment detected by the sensors installed in vehicles and RSUs through V2X communication. The main purpose is to expand the detectable area of ​​service users by sharing information about the current driving environment (Road Users not equipped with V2X, obstacles, etc.) detected by the vehicles and RSUs' own sensors (Radar, LiDAR, Camera, etc.) and to improve traffic safety by increasing the awareness of road conditions in blind spots.

[0358] Through the method proposed in this disclosure, the server / RSU / terminal can obtain ITS station information in an area that it could not detect with its own sensor by receiving a V2X message, and include and transmit the information in a message for the purpose of sensor data sharing, thereby improving sensing sensitivity or expanding coverage.

[0359] Figure 15 illustrates an example of a sensor data sharing message format input processing process.

[0360] Referring to FIG. 15, a device (e.g., server / RSU / terminal) can receive / collect V2X messages from other devices (B01). The device can classify / sort V2X messages based on whether they are inside / outside sensing coverage, data acquisition method, etc. (B02).

[0361] The device checks whether the V2X message contains detailed data related to object identification (B03), and can exclude V2X messages that do not contain detailed data from the conversion target (B04). Even if a priority is set for determining a valid V2X service area or a valid object (B05), the V2X message can also be excluded from the conversion target if it does not satisfy the priority (B04).

[0362] The device can notify the target (owner) object of the conversion target message that information from the target (owner) object is about to be propagated (B06).

[0363] The device can handle object detection related requirements by considering sensing coverage in / out / in&out (B07, B08, B09).

[0364] If the sensing coverage out object information is included, the device can enter numerical data for coverage extension into the sensor data sharing message format (B12).

[0365] The device may input additional information as described above within the sensor data sharing message format (B11).

[0366] Meanwhile, information for distinguishing between objects detected by a sensor and objects for which data fields are set based on received messages may be included in the sensor data sharing message format (B13).

[0367] Figure 16 illustrates a flowchart of a method for transmitting data by a first device in an intelligent transportation system according to one embodiment. The first device may include at least one of a terminal, a vehicle, a roadside unit (RSU), or a server.

[0368] Referring to FIG. 16, the first device can collect sensing data on a moving object (C05).

[0369] The first device can obtain information about the movement path of the object based on the sensing data (C10).

[0370] The first device can generate a message (e.g., CPM, SDSM) to share sensing data about the object (C15).

[0371] The first device can transmit the message to the second device (C20).

[0372] The above message includes N data sets established based on information about the movement path of the object, and the N data sets may be related to the position of the object at each of N different points in time.

[0373] The position of the object at each of the N different points in time may be calculated by the first device based on information about the movement path of the object.

[0374] The movement path of the object is a path along which the object is predicted to move, and the N data sets may be related to the predicted location of the object for N future points in time.

[0375] The movement path of the above object is a path for the movement history of the object, and the N data sets can be related to the location of the object at N past points in time.

[0376] The sensing data for the above moving object may be obtained from vehicle-to-everything (V2X) messages received from other devices.

[0377] The above message may include information about a confidence level for the N data sets established based on the movement path of the object.

[0378] The above message may further include at least one data set set based on the sensing data in addition to the N data sets.

[0379] The above message may include information for distinguishing whether each data set is a data set established based on information about the movement path or a data set established based on the sensing data.

[0380] The sensing data may include first sensing data acquired within the sensing coverage of the first device and second sensing data acquired outside the sensing coverage of the first device.

[0381] The second sensing data may be received from another device having a sensing coverage different from the sensing coverage of the first device.

[0382] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts of the present disclosure disclosed in this document may be applied to various fields requiring wireless communication / connectivity (e.g., 5G) between devices.

[0383] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.

[0384] Fig. 17 illustrates a communication system applicable to this embodiment.

[0385] Referring to FIG. 17, a communication system (1) applicable to the present embodiment includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and can be implemented in the form of HMD (Head-Mounted Device), HUD (Head-Up Display) installed in a vehicle, television, smartphone, computer, wearable device, home appliance, digital signage, vehicle, robot, etc. Mobile devices can include smartphone, smart pad, wearable device (e.g., smart watch, smart glass), computer (e.g., laptop, etc.), etc. Home appliances can include TV, refrigerator, washing machine, etc. IoT devices can include sensors, smart meters, etc. For example, base stations and networks can also be implemented as wireless devices, and a specific wireless device (200a) can act as a base station / network node to other wireless devices.

[0386] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, etc. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0387] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and base station-to-base station communication (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present disclosure.

[0388] Figure 18 illustrates a wireless device applicable to the present disclosure.

[0389] Referring to FIG. 18, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the base station (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 27.

[0390] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chipset designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In this specification, wireless device may also mean a communication modem / circuit / chipset.

[0391] Specifically, the UE may include a processor (102) and a memory (104) connected to the RF transceiver. The memory (104) may include at least one program capable of performing operations related to the embodiments described in FIGS. 17 to 27.

[0392] Alternatively, a chipset may be configured that includes a processor (102) and a memory (104). In this case, the chipset may include at least one processor and at least one memory operably connected to the at least one processor and, when executed, causing the at least one processor to perform operations.

[0393] The second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). Furthermore, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In this specification, a wireless device may also mean a communication modem / circuit / chip.

[0394] Hereinafter, the hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed herein, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0395] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0396] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0397] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0398] Figure 19 illustrates another example of a wireless device applicable to the present embodiment. The wireless device may be implemented in various forms depending on the use case / service (see Figure 27).

[0399] Referring to FIG. 19, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 18 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 19. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 18. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0400] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 17, 100a), a vehicle (Fig. 17, 100b-1, 100b-2), an XR device (Fig. 17, 100c), a portable device (Fig. 17, 100d), a home appliance (Fig. 17, 100e), an IoT device (Fig. 17, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 17, 400), a base station (Fig. 17, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0401] In FIG. 19, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and a first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of one or more processor sets. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0402] Figure 20 illustrates a vehicle or autonomous vehicle applicable to this embodiment. The vehicle or autonomous vehicle may be implemented as a mobile robot, car, train, manned / unmanned aerial vehicle (AV), ship, etc.

[0403] Referring to FIG. 20, a vehicle or autonomous vehicle (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a driving unit (140a), a power supply unit (140b), a sensor unit (140c), and an autonomous driving unit (140d). The antenna unit (108) may be configured as a part of the communication unit (110). Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 of FIG. 18, respectively.

[0404] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g., base stations, road side units, etc.), and servers. The control unit (120) can control elements of the vehicle or autonomous vehicle (100) to perform various operations. The control unit (120) can include an ECU (Electronic Control Unit). The drive unit (140a) can drive the vehicle or autonomous vehicle (100) on the ground. The drive unit (140a) can include an engine, a motor, a power train, wheels, brakes, a steering device, etc. The power supply unit (140b) supplies power to the vehicle or autonomous vehicle (100) and can include a wired / wireless charging circuit, a battery, etc. The sensor unit (140c) can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit (140c) may include an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an incline sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit (140d) may implement a technology for maintaining a driving lane, a technology for automatically controlling speed such as adaptive cruise control, a technology for automatically driving along a set path, a technology for automatically setting a path and driving when a destination is set, etc.

[0405] For example, the communication unit (110) can receive map data, traffic information data, etc. from an external server. The autonomous driving unit (140d) can generate an autonomous driving route and driving plan based on the acquired data. The control unit (120) can control the drive unit (140a) so that the vehicle or autonomous vehicle (100) moves along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit (110) can irregularly / periodically acquire the latest traffic information data from an external server and can acquire surrounding traffic information data from surrounding vehicles. In addition, during autonomous driving, the sensor unit (140c) can acquire vehicle status and surrounding environment information. The autonomous driving unit (140d) can update the autonomous driving route and driving plan based on newly acquired data / information. The communication unit (110) can transmit information regarding the vehicle location, autonomous driving route, driving plan, etc. to the external server. External servers can predict traffic information data in advance using AI technology or other technologies based on information collected from vehicles or autonomous vehicles, and provide the predicted traffic information data to the vehicles or autonomous vehicles.

[0406] Here, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PAN (personal area networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0407] The embodiments described above are combinations of components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments or incorporated as new claims through post-application amendments.

[0408] In this document, the embodiments of the present disclosure have been described primarily focusing on the signal transmission and reception relationship between a terminal and a base station. This transmission and reception relationship is equally / similarly extended to signal transmission and reception between a terminal and a relay or a base station and a relay. Certain operations described as being performed by a base station in this document may, in some cases, be performed by its upper node. That is, it is obvious that various operations performed for communication with a terminal in a network composed of multiple network nodes including a base station may be performed by the base station or other network nodes other than the base station. The base station may be replaced by terms such as a fixed station, a Node B, an eNode B (eNB), an access point, etc. The terminal may also be replaced by terms such as a User Equipment (UE), a Mobile Station (MS), or a Mobile Subscriber Station (MSS).

[0409] Embodiments according to the present disclosure may be implemented by various means, for example, hardware, firmware, software, or a combination thereof. In the case of hardware implementation, an embodiment of the present disclosure may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.

[0410] When implemented via firmware or software, one embodiment of the present disclosure may be implemented in the form of a module, procedure, function, or the like that performs the functions or operations described above. The software code may be stored in a memory unit and executed by a processor. The memory unit may be located within or outside the processor and may exchange data with the processor via various known means.

[0411] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the technical features described herein. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present invention should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present invention are intended to be included within the scope of the present invention.

[0412] The embodiments of the present disclosure as described above can be applied to various devices of an intelligent transportation system.

Claims

1. In a method for transmitting information from a first device to a second device in an intelligent transportation system (ITS), Collect sensing data about moving objects; Obtaining information about the movement path of the object based on the sensing data; Generate a message to share sensing data about the above object; and Including transmitting the message to the second device, The above message includes N data sets set based on information about the movement path of the object, A method wherein the N data sets are related to the location of the object at each of N different points in time.

2. In paragraph 1, A method wherein the position of the object at each of the N different points in time is calculated by the first device based on information about the movement path of the object.

3. In paragraph 1, The movement path of the above object is the path along which the object is predicted to move, A method wherein the N data sets are related to the predicted location of the object for N future points in time.

4. In paragraph 1, The movement path of the above object is a path for the movement history of the above object, A method wherein the N data sets are related to the location of the object at N past points in time.

5. In paragraph 1, A method wherein sensing data for the above moving object is obtained from V2X (vehicle-to-everything) messages received from other devices.

6. In paragraph 1, A method wherein the message includes information about a confidence level for the N data sets established based on the movement path of the object.

7. In paragraph 1, A method wherein the message further comprises at least one data set set based on the sensing data in addition to the N data sets.

8. In paragraph 7, A method wherein the message includes information for distinguishing whether each data set is a data set set based on information about the movement path or a data set set based on the sensing data.

9. In paragraph 1, A method wherein the sensing data includes first sensing data acquired within the sensing coverage of the first device and second sensing data acquired outside the sensing coverage of the first device.

10. In paragraph 9, A method wherein the second sensing data is received from another device having a sensing coverage different from the sensing coverage of the first device.

11. A computer-readable recording medium recording a program for performing the method described in paragraph 1.

12. In a first device operating in an intelligent transportation system (ITS), memory that stores commands; and A processor that performs operations by executing the above instructions, The operations of the above processor are: Collect sensing data about moving objects; Obtaining information about the movement path of the object based on the sensing data; Generate a message to share sensing data about the above object; and Including transmitting the above message to a second device, The above message includes N data sets set based on information about the movement path of the object, A first device, wherein the N data sets are related to the position of the object at each of N different points in time.

13. In paragraph 12, The first device is a terminal, a vehicle, an RSU (road side unit) or a server.

Citation Information

Patent Citations

  • Vehicle position calibration method using radar and v2v in GPS shielded area

    KR101837868B1

  • Control loss warning apparatus for vehicle using vehicle-to-vehicle communications and method thereof

    KR1020160013714A

  • Apparatus and mehtod for transmitting information for peripheral vehicle

    KR1020180062737A

  • V2V communication device and method for controlling thereof

    KR1020180118915A

  • Method for VRU to predict movement path in wireless communication system supporting sidelink, and device for same

    US20230087496A1

Cited By

  • Communication method and apparatus

    WO2026208803A1