WO2019066106A1 - V2x 통신 장치 및 그의 멀티미디어 컨텐트 전송/수신 방법 - Google Patents
V2x 통신 장치 및 그의 멀티미디어 컨텐트 전송/수신 방법 Download PDFInfo
- Publication number
- WO2019066106A1 WO2019066106A1 PCT/KR2017/010954 KR2017010954W WO2019066106A1 WO 2019066106 A1 WO2019066106 A1 WO 2019066106A1 KR 2017010954 W KR2017010954 W KR 2017010954W WO 2019066106 A1 WO2019066106 A1 WO 2019066106A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- multimedia content
- information
- multimedia
- mcm
- message
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/20—Natural language analysis
- G06F40/263—Language identification
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
- H04B7/26—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile
- H04B7/2612—Arrangements for wireless medium access control, e.g. by allocating physical layer transmission capacity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/52—Network services specially adapted for the location of the user terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/30—Services specially adapted for particular environments, situations or purposes
- H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
Definitions
- the present invention relates to a V2X communication apparatus and a method for transmitting and receiving multimedia contents, and in particular, a method for receiving a multimedia content message including multimedia content and processing multimedia content based on information included in the message.
- V2X Vehicle to Everything
- the present invention proposes a message format and transmission / reception protocol for inter-vehicle multimedia content communication.
- a method of receiving a multimedia content message of a V2X (Vehicle to everything) communication device and a V2X communication device is disclosed.
- a method of receiving a multimedia content message includes: receiving a multimedia content message; Parsing the multimedia content message; And acquiring a multimedia content included in the multimedia message or a content segment that is a part of the multimedia content, wherein the multimedia content message includes a header including a protocol version and a message ID, a multimedia content message management A management container including information related to an MCD (Multimedia Content Dissemination) protocol, a status container including information describing an event, a location container including location information of the event, and the multimedia content Wherein the management container includes a number of multimedia data units (numberOfMultimediaUnit) indicating a number of multimedia data units included in the multimedia container, And a multimedia format type (multimediaFormatType) information about the multimedia content.
- MCD Multimedia Content Dissemination
- the management container may further include size information of at least one of the multimedia content or the segment of the multimedia content, Determining whether to store the multimedia content or the content segment based on size information and storage information of the V2X communication device.
- the management container may further include multimedia content identifier information
- the multimedia content message receiving method may include receiving the multimedia content message based on the multimedia content identifier information, Further comprising the step of determining whether the multimedia content or the content segment overlaps with the pre-received multimedia content.
- the management container may further include URL information
- the multimedia content message receiving method may include receiving the multimedia content by accessing a URL indicated by the URL information .
- the management container may further include language information indicating a language of the multimedia content
- the multimedia content message receiving method may further include: Further comprising determining whether the language of the multimedia content is an acceptable language.
- the management container may further include valid time information
- the multimedia content message receiving method may include receiving the multimedia content, And a step of determining whether or not it is possible.
- a V2X communication apparatus includes: a memory for storing data; A communication unit for transmitting and receiving a radio signal; And a processor for controlling the communication unit, wherein the V2X communication device receives the multimedia content message, parses the multimedia content message, and transmits the multimedia content or multimedia content included in the multi-
- the multimedia content message includes a header including a protocol version and a message ID, a management container including MCM (Multimedia Content Message) management and MCD (Multimedia Content Dissemination) protocol related information, information describing an event A location container including location information of the event, and a multimedia content container including the multimedia content
- the management container includes a multimedia container Number (numberOfMultimediaUnit) of the multimedia data unit indicating the number of multimedia data units included in the information, and a multimedia format type (multimediaFormatType) information about the multimedia content contained in the multimedia container.
- the MCD protocol of the present invention describes information about road safety, traffic management, POI (Point of Interest), national patrimony, commecial, personal, etc. as multimedia contents ) To enable V2X communication.
- the MCD protocol of the present invention separates multimedia contents into a plurality of segments and propagates them, and merges segments at a receiving end to recover multimedia contents.
- the receiver can determine whether to forward or ignore MCM delivering multimedia content / segments based on the storage state to the application. Therefore, unnecessary reception processing and storage waste can be prevented.
- the receiver determines whether the received content is a duplicated multimedia content, and determines whether to forward the content / segment to the application or ignore . Therefore, unnecessary reception processing and storage waste can be prevented.
- the multimedia content can be delivered based on another access layer or transport layer technology.
- the use of V2X communication frequency by multimedia content transmission can be minimized.
- the receiver can determine whether the multimedia content is acceptable to the user and determine whether to forward or ignore the content / segment to the application. Therefore, unnecessary reception processing and storage waste can be prevented.
- the receiver can determine the validity time of the multimedia content and determine whether to forward or ignore the content / segment to the application or forward. Thus, unnecessary transmission / reception processing, waste of storage, and utilization of ineffective information can be prevented.
- FIG 1 shows an Intelligent Transport System (ITS) according to an embodiment of the present invention.
- ITS Intelligent Transport System
- FIG. 2 shows a V2X transceiver system according to an embodiment of the present invention.
- FIG. 3 shows a configuration of a V2X system according to an embodiment of the present invention.
- FIG. 4 shows a packet structure of a network / transport layer according to an embodiment of the present invention.
- FIG. 5 shows a configuration of a V2X system according to another embodiment of the present invention.
- FIG. 6 shows a WSMP packet configuration according to an embodiment of the present invention.
- FIG. 7 illustrates a conceptual internal architecture of a MAC sublayer that performs an MCO (Multi-Channel Operation) according to an embodiment of the present invention.
- MCO Multi-Channel Operation
- FIG. 8 shows the relationship between the user priority of EDCA and AC (Access Category) according to the embodiment of the present invention.
- FIG. 9 shows a physical layer configuration of a V2X transmission apparatus according to an embodiment of the present invention.
- FIG 10 shows an MCM format according to an embodiment of the present invention.
- 11 is an ITS station architecture according to an embodiment of the present invention, in particular an architecture for message processing according to the MCD protocol.
- FIG. 12 shows a method of transmitting / receiving an MCM according to an embodiment of the present invention.
- FIG. 13 shows an MCM transmission / reception method according to an embodiment of the present invention.
- FIG. 14 shows an MCM transmission / reception method according to an embodiment of the present invention.
- FIG. 16 shows a configuration of a management container of an MCM according to an embodiment of the present invention.
- FIG. 17 shows an MCM transmission / reception method including size information according to an embodiment of the present invention.
- FIG. 19 shows an MCM transmission / reception method including size information according to an embodiment of the present invention.
- 21 shows a configuration of a management container of an MCM according to an embodiment of the present invention.
- FIG. 22 shows a method of transmitting / receiving an MCM according to an embodiment of the present invention.
- FIG. 24 shows a method of transmitting / receiving an MCM according to an embodiment of the present invention.
- 25 illustrates an MCD operation using multimedia content identifier information according to an embodiment of the present invention.
- 26 shows a configuration of a management container of an MCM according to an embodiment of the present invention.
- FIG. 27 shows a method of transmitting / receiving an MCM according to an embodiment of the present invention.
- 29 shows a configuration of a management container of an MCM according to an embodiment of the present invention.
- FIG. 30 shows a method of transmitting / receiving an MCM according to an embodiment of the present invention.
- FIG. 31 shows an MCM transmission / reception method according to an embodiment of the present invention.
- FIG 33 illustrates an MCD operation using multimedia language information according to an embodiment of the present invention.
- FIG. 34 illustrates a configuration of a management container of an MCM according to an embodiment of the present invention.
- 35 shows a management container and a geo-networking basic header of an MCM according to an embodiment of the present invention.
- FIG. 37 shows a V2X communication apparatus according to an embodiment of the present invention.
- FIG. 38 shows a method of receiving a multimedia content message of a V2X communication apparatus according to an embodiment of the present invention.
- the present invention relates to a V2X communication device, wherein the V2X communication device is included in an Intelligent Transport System (ITS) system to perform all or some of the functions of the ITS system.
- V2X communication devices can communicate with vehicles and vehicles, vehicles and infrastructure, vehicles and bicycles, and mobile devices.
- the V2X communication device may be abbreviated as a V2X device.
- the V2X device may correspond to an on-board unit (OBU) of a vehicle or may be included in an OBU.
- the OBU may also be referred to as OBE (On Board Equipment).
- the V2X device may correspond to an infrastructure's Road Side Unit (RSU) or may be included in an RSU.
- RSU may also be referred to as RSE (RoadSide Equipment).
- the V2X communication device may correspond to an ITS station or may be included in an ITS station. Any OBU, RSU, mobile device, etc. performing V2X communication may be referred to as an ITS station or a
- FIG 1 shows an Intelligent Transport System (ITS) according to an embodiment of the present invention.
- ITS Intelligent Transport System
- Intelligent transportation system applies information and communication technology such as electronic control and communication device to traffic facilities such as automobiles, buses, trains, traffic lights installed on roads, ≪ / RTI > To support ITS, a V2X (Vehicle to everything) technique may be used.
- V2X communication technology represents a communication technique between a vehicle and a vehicle or between a vehicle and a peripheral device.
- Vehicles supporting V2X communication are equipped with an OBU, and OBUs include a DSRC (Dedicated Short-Range Communication) communication modem.
- An infrastructure including a V2X module installed around the road, such as a traffic light, may be referred to as an RSU.
- VRU Vehicleable Road Users
- VRU Vehicleable Road Users
- pedestrians, bicycles, wheelchairs, etc. may correspond to VRUs.
- VRU can be V2X communication enabled.
- V2V Vehicle to Vehicle
- V2I Vehicle to Infra-structure
- V2O the communication between the vehicle and the traffic abbreviation
- I2O the communication between the infrastructure and the traffic abbreviation
- FIG. 2 shows a V2X transceiver system according to an embodiment of the present invention.
- V2X transmission / reception system is divided according to the roles of the V2X transmitter 2100 and the V2X receiver 2200 transmitter and receiver for transmitting and receiving data, and there is no difference in configuration of the apparatus.
- V2X transmitter 2100 and V2X receiver 2200 all correspond to V2X communication devices.
- the V2X transmitter 2100 includes a Global Navigation Satellite System (GNSS) receiver 2110, a DSRC radio 2120, a DSRC device processor 2130, an application ECU (Electronic Control Unit) An ECU 2140, a sensor 2150, and a human interface 2160.
- GNSS Global Navigation Satellite System
- the DSRC radio 2120 performs communications based on the IEEE 802.11 standard based on a WLAN (Wireless Local Area Network) and / or the Wireless Access in Vehicular Environments (WAVE) standard of the Society of Automotive Engineers (SAE) .
- the DSRC radio 2120 can perform operations of the physical layer and the MAC layer.
- the DSRC device processor 2130 may decode the message received by the DSRC radio 2120 or may decode the message to send.
- the GNSS receiver 2110 processes the GNSS and can obtain location information and time information.
- the GNSS receiver 2110 may be a Global Positioning System (GPS) device.
- GPS Global Positioning System
- the application ECU 2140 may be a microprocessor for providing a specific application service.
- the application ECU may generate an action / message based on sensor information and user input to provide the service, and may use the DSRC device processor to send and receive the message.
- the sensor 2150 can acquire vehicle status and ambient sensor information.
- the human interface 2160 can receive a user's input or display / provide a message through an interface such as an input button or a monitor.
- the V2X receiver 2200 includes a Global Navigation Satellite System (GNSS) receiver 2210, a DSRC radio 2220, a DSRC device processor 2230, an application ECU (Electronic Control Unit) ECU 2240, a sensor 2250 and a human interface 2260.
- GNSS Global Navigation Satellite System
- DSRC radio 2220 a Global Navigation Satellite System
- DSRC device processor 2230 an application ECU (Electronic Control Unit) ECU 2240, a sensor 2250 and a human interface 2260.
- ECU Electronic Control Unit
- the DSRC radio and DSRC device processor correspond to one embodiment of a communication unit.
- the communication unit may communicate based on a cellular communication technology such as 3GPP, Long Term Evolution (LTE).
- 3GPP Long Term Evolution
- LTE Long Term Evolution
- FIG. 3 shows a configuration of a V2X system according to an embodiment of the present invention.
- the V2X system of FIG. 3 may correspond to the ITS station reference architecture defined in ISO 21217 / EN 302 665.
- Figure 3 shows an example of an ITS station on which the ITS station is based on a reference architecture.
- Figure 3 shows a hierarchical architecture for end-to-end communication.
- the application layer can implement and support various use cases.
- the application may provide road safety, Efficient Traffic Information, and other application information.
- the application layer can classify and define ITS applications and provide services to the end vehicle / user / infrastructure via the lower layers.
- An application can be defined / applied on a use-case basis, or a use-case can be grouped as a road-safety, traffic efficiency, local service, infotainment, It is possible. As an example, application classification, use-case, etc. may be updated when new application scenarios occur.
- Layer management can manage and service information related to the operation and security of the application layer. Information and services can be delivered and shared bidirectionally via MAMA (interface between management entity and application layer) and SA (interface between security entity and ITS-S applications) or SAP (Service Access Point, eg MA-SAP, SA-SAP) .
- MAMA interface between management entity and application layer
- SA interface between security entity and ITS-S applications
- SAP Service Access Point, eg MA-SAP, SA-SAP
- the request from the application layer to the facility layer or from the facility layer to the application layer can be carried out via
- the facilities layer can support various applications defined at the application layer effectively.
- the facility layer can perform application support, information support, and session / communication support.
- the facility layer can support the top three layers of the OSI model, the session layer, the presentation layer, and the application layer, by default.
- the facility layer can additionally provide advanced facilities such as application support, information support, and session / communication support for the ITS system.
- Facility refers to a component that provides functionality, information, and data.
- the Facility can be classified into common facilities and domain facilities.
- the common facility can provide the basic set of applications of the ITS and core services or functions needed for ITS station operation. For example, time management, position management, service management, etc. may be provided.
- the domain capability can provide a special service or function to a basic application set of one or a plurality of ITSs.
- Domain Facilities can provide Decentralized Notification Messages (DENM) management for Road Hazard Warning applications (RHW). Domain facilities are optional and may not be used unless they are supported by the ITS station.
- DENM Decentralized Notification Messages
- RHW Road Hazard Warning applications
- the network / transport layer can configure a network for vehicle communication between homogenous and heterogenous networks by using various transport protocols and network protocols.
- the network / transport layer can provide Internet access and routing using Internet protocols such as TCP / UDP + IPv6.
- the network / transport layer may configure the vehicle network using a geographical position based protocol such as Basic Transport Protocol (BTP) / GeoNetworking.
- BTP Basic Transport Protocol
- the transport layer corresponds to a connection layer between services provided by the upper layer (session layer, presentation layer, application layer) and lower layers (network layer, data link layer, and physical layer).
- the transport layer manages the data sent by the user to arrive at the destination exactly.
- the transport layer can perform the function of dividing data into packets of a size suitable for transmission for efficient data transmission.
- the transport layer can serve to recombine the received packets into the original file.
- the transport protocol may be TCP / UDP, and the transport protocol for ITS such as VTS may be used.
- the network layer can assign a logical address and determine the packet delivery path.
- the network layer can receive the packet generated at the transport layer and add a network header including the logical address of the destination.
- a packet path design unicast / broadcast between vehicles, between a vehicle and a fixed station, and between fixed stations can be considered.
- protocols such as Geo-Networking, IPv6 with networking with mobility support, and IPv6 over geo-networking may be considered as network protocols for ITS.
- the access layer can transmit the message / data received from the upper layer through the physical channel.
- the access layer may be based on IEEE 802.11 and / or 802.11p standards based communication technology, ITS-G5 wireless communication technology based on the physical transmission technology of the IEEE 802.11 and / or 802.11p standards, 2G including satellite / Data communication can be carried out / supported based on broadband terrestrial digital broadcasting technology such as / 3G / 4G (LTE) / 5G wireless cellular communication technology, DVB-T / T2 / ATSC, GPS technology and IEEE 1609 WAVE technology.
- LTE 3G / 4G
- 5G wireless cellular communication technology DVB-T / T2 / ATSC
- GPS technology GPS technology
- IEEE 1609 WAVE technology IEEE 1609 WAVE technology.
- the ITS system for vehicle communication and networking can be organically designed considering various access technologies, network protocols, and communication interfaces to provide a variety of use-cases.
- the role and function of each layer may be enhanced or reinforced.
- FIG. 4 shows a packet structure of a network / transport layer according to an embodiment of the present invention.
- the geo-networking packet corresponds to the data of a logical link control (LLC) packet and can be included in the LLC packet.
- Geo-networking packets can be encapsulated in LLC packets.
- the data comprises a message set, and the message set may be a basic safety message.
- the BTP header is a protocol for transmitting messages such as CAM and DENM generated by the facility layer to the lower layer.
- the BTP header consists of A type and B type.
- the A-type BTP header may include a destination / destination port and a source port required for transmission / reception for interactive packet transmission.
- the B type header may include destination and destination port information required for transmission for non-interactive packet transmission.
- the fields / information included in the header are as follows.
- the destination port identifies a facility entity corresponding to the destination of the data (BTP-PDU) contained in the BTP packet.
- Source Port A field created in the case of the BTP-A type, indicating the port of the protocol entity of the facility layer at the source from which the packet is transmitted. This field may have a size of 16 bits.
- Destination Port Info This field is created for the BTP-B type. It can provide additional information if the destination port is the best known port. This field may have a size of 16 bits.
- a geonetworking packet includes a basic header and a common header according to a protocol of a network layer, and optionally includes an extension header according to a geo networking mode.
- the basic header can be 32 bits (4 bytes).
- the basic header may include at least one of a version field, an NH field (Next Header), a LT (LifeTime) field, and a Remaining Hop Limit (RHL) field. Fields included in the basic header are described below. The bit size constituting each field is only an embodiment and may be changed.
- Version (4-bit) The version field indicates the version of the geo-networking protocol.
- NH (4 bits): NH (Next Header) field indicates the type of the following header / field. If the field value is 1, a common header is followed. If the field value is 2, a secured packet can be followed.
- the LT (LifeTime) field indicates the maximum lifetime of the packet.
- RHL 8 bits: The Remaining Hop Limit (RHL) field indicates the residual hop limit.
- the RHL field value can be reduced by one for each forwarding on the GeoAdhoc router. When the RHL field value reaches 0, the packet is no longer forwarded.
- the common header can be 64 bits (8 bytes).
- the common header includes a Next Header (NH) field, an HT (HeaderType) field, a HST (Header Sub-Type) field, a TC (Traffic Class) field, a Flags field, a PayloadLength Or the like.
- NH Next Header
- HST Header Sub-Type
- TC Traffic Class
- NH (4 bits): NH (Next Header) field indicates the type of the following header / field. If the field value is 0, it indicates an undefined "ANY" type, 1 indicates a BTP-A type packet, 2 indicates a BTP-B type packet, and 3 indicates an IP diagram of IPv6.
- Geo-networking types include Beacon, GeoUnicast, GeoAnycast, GeoBroadcast, Topologically-Scoped Broadcast (TSB), and Location Service (LS).
- the header subtype field indicates the header type as well as the detailed type. As an example, when the HT type is set to TSB, a single hop is indicated when the HST value is '0', and a multi-hop can be designated when the HST value is '1'.
- the traffic class field may include Store-Carry-Forward (SCF), Channel Offload (Channel Offload), and TC ID.
- SCF Store-Carry-Forward
- Channel Offload Channel Offload
- TC ID TC ID
- the SCF field indicates whether to store the packet if there is no neighbor to which to transmit the packet.
- the channel offload field indicates that a packet can be delivered to another channel in the case of a multi-channel operation.
- the TC ID field is a value assigned at the time of packet forwarding in the facility layer and can be used to set the contention window value at the physical layer.
- the flag field indicates whether the ITS device is mobile or stationary, and may be the last one bit as an example.
- the payload length field indicates the length of data, in bytes, following the geo-networking header.
- the PL field may indicate the length of the BTP header and the CAM.
- MHL 8 bits
- the Maximum Hop Limit (MHL) field can indicate the maximum number of hops.
- An LLC header is added to the geo-networking packet to generate an LLC packet.
- the LLC header provides a function to distinguish and transmit IP data from geo-networking data.
- IP data and geo-networking data can be distinguished by SNAP's Ethertype.
- Ether type when IP data is transmitted, the Ether type may be set to 0x86DD and included in the LLC header.
- geo-networking data if geo-networking data is transmitted, the Ether type may be set to 0x86DC and included in the LLC header.
- the receiver can identify the Ethertype field of the LLC packet header and forward and process the packet to the IP data path or the geo networking path according to the value.
- FIG. 5 shows a configuration of a V2X system according to another embodiment of the present invention.
- the North American V2X system uses the IEEE 802.11 PHY technology and the MAC technology, and can further use the IEEE 1609.4 MAC technology.
- the IEEE802.2 standard is applied to the LLC block
- the IEEE 1609.3 technology is applied to the WAVE short message protocol (WSMP).
- the facility layer can use SAE's J2735 standard message set, and the application layer can use applications defined for V2V, V2I, V2O in the J2945 standard.
- the application layer can implement the support functions by implementing use cases.
- the application can optionally be used depending on the use case.
- the system requirements for each use-case can be defined in the J2945 standard.
- J2945 / 1 defines the application of V2V technology such as V2V safety communication.
- the J2945 / 1 document can be used for applications such as emergency electronic brake lights (EEBL), forward crash warning, blind spot warning, lane change warning, intersection movement assist (IMA) and control loss warning .
- the FCW technique is a V2V safety communication technology that warns of a collision with a preceding vehicle.
- a vehicle with a V2X communication device makes an emergency stop or crash, it may send an FCW safety message to prevent subsequent vehicle collisions.
- Subsequent vehicles can receive FCW messages and alert the driver or perform controls such as speed reduction or lane change.
- the FCW safety message may include vehicle location information (latitude, longitude, lane), vehicle information (vehicle type, length, direction, speed), event information (stop, It can be generated by request.
- the facility layer may correspond to OSI layer 5 (session layer), layer 6 (presentation layer), and layer 7 (application layer).
- the facility layer can create a contextual message set to support the application.
- the message set is defined in the J2735 standard and can be described / decoded via ASN.1.
- the message set may include BasicSafetyMessage, MapData, SPAT, CommonSafetyRequest, EmergencyVehicleAlert, IntersectionCollision, ProbeVehicleData, RoadSideAlert, and PersonalSafetyMessag messages.
- the facility layer can collect the information to be transmitted from the upper layer to generate a message set.
- the message set may be expressed in an ASN.1 (Abstract Syntax Notation 1) manner.
- ASN.1 is a notation used to describe the data structure, and can also set encoding / decoding rules. ASN.1 does not depend on specific devices, data representation, programming languages, hardware platforms, and so on.
- ASN.1 is a language for describing data on any platform, and is a joint standard between CCITT (Consultative Committee on International Circuity and Telephony, X.208) and ISO (International Organization for Standardization, ISO 8824).
- a message set is a collection of messages related to V2X operations, and there is a set of messages appropriate to the context of the parent application.
- a message set is represented in the form of a data frame, and may include at least one element. Each element may comprise a data frame or a data element.
- a data frame represents a sequence of two or more data.
- a data frame may be a data structure of a data element or a data structure of a data frame.
- DV_vehicleData is a data frame structure representing information of a car, and may include a plurality of data elements (e.g., Height, Bumbers, mass, trailerweight).
- a data element defines a description of a data element.
- an element called Height used in a data frame is defined in DE_VehicleHeight and can express the height of the vehicle. As an example, the height of the vehicle can be expressed from 0 to 127, and the LBS unit is increased by 5 cm and can be expressed up to 6.35 meters.
- a BasicSafetyMessage may be sent.
- BasicSafetyMessage is the most basic and important message in a set of messages, and is used to periodically transmit basic vehicle information.
- the message can include coreData defined in BSMcoreData and optional Part II and regional data.
- coreData may contain data elements such as msgCnt, id, lat, long, elev, speed, dead, break, coreData uses data elements to display message count, ID, latitude, longitude, altitude, speed, direction, break, vehicle size, and so on.
- the BSM can transmit information corresponding to the coreData in a period of generally 100 msec (10 times per second).
- the network / transport layer may correspond to OSI layer 3 (network layer), layer 4 (transport layer).
- WAVE short message protocol (WSMP) can be used to transmit a WAVE Short Message (WSM) transmitted from an upper layer.
- WSM WAVE Short Message
- IPv6 / TCP protocol can be used to process conventional IP signals.
- the LLC block uses the IEEE 802.2 standard to distinguish between IP diagrams and WSM packets.
- the access layer may correspond to OSI layer 1 (physical layer), layer 2 (data link layer).
- the access layer can use IEEE 802.11 PHY technology and MAC technology, and the MAC technology of IEEE 1609.4 can be used to further support vehicle communication.
- the security entity and the management entity may be connected and operated in all intervals.
- FIG. 6 shows a WSMP packet configuration according to an embodiment of the present invention.
- the network / transport layer of FIG. 5 may transmit a vehicle security message, such as BSM, via the WSMP.
- vehicle security message such as BSM
- the WSMP protocol is described in the IEEE 1609.3 document, and IPv6 and TCP / UDP can also be supported to transmit additional IP data.
- the WSMP is a protocol for transmitting a WAVE short message generated by the ASN.1 method in the facility layer to the lower layer.
- the WSMP packet includes a WSMP header and WSM data including a message.
- the WSMP header includes a version field, a PSID field, an extension field, a WSM WAVE element ID field, and a length field.
- the version field may be defined as a WsmpVersion field indicating the actual WSMP version of 4 bits and a reserved field of 4 bits.
- the PSID field is a provider service identifier, which can be assigned according to an application at an upper layer. The PSID field helps determine the appropriate upper layer at the receiver side.
- the extension field is a field for extending the WSMP header, and information such as a channel number, a data rate, and transmit power used may be inserted.
- the WSMP WAVE element ID field can specify the type of WAVE short message to be transmitted.
- the length field may specify the length of the WSM data transmitted in the WSMLemgth field of 12 bits in units of octets.
- the LLC header provides a function to transmit IP data and WSMP data separately.
- IP data and WSMP data can be distinguished by SNAP's Ethertype.
- LLC header and SNAP header structure can be defined in the document of IEEE 802.2.
- the Ether type may be set to 0x86DD and included in the LLC header.
- the Ether type may be set to 0x86DC and included in the LLC header.
- the receiver can identify the Ethertype field of the LLC packet header and forward and process the packet to the IP data path or the WSMP path according to the value.
- FIG. 7 illustrates a conceptual internal architecture of a MAC sublayer that performs an MCO (Multi-Channel Operation) according to an embodiment of the present invention.
- MCO Multi-Channel Operation
- the architecture of FIG. 7 may be included in the access layer of FIG. 5, or may be included in the MAC layer of the access layer.
- the MCO structure of FIG. 7 includes channel coordination in which a channel access is defined, overall data between PHY-MAC layers, channel routing that defines the operation of a management frame, EDCA (Enhanced Dedicated Channel Access), and a data buffer (or a queue) for storing frames received at an upper layer.
- the channel coordination block is not shown in FIG. 7, and the channel coordination may be performed by the entire MAC sublayer of FIG.
- Channel Coordination As an embodiment, channel access to Control Channel (CCH) and Service Channel (SCH) can be controlled. The channel access coordination will be described later.
- the CCH can be transmitted with a WSM (Wave Short Message) and the WSM and / or IP data can be transmitted with the SCH.
- WSM Wive Short Message
- the data buffer can store the data frame received from the upper layer according to the defined Access Category (AC).
- AC Access Category
- a data buffer may be provided for each AC.
- the channel routing block can forward the incoming data from the upper layer to the data buffer. It is possible to invoke transmission operation parameters such as the channel coordination and the channel number, transmission power, and data rate for the frame transmission described above with respect to the transmission request of the upper layer.
- EDCA It is a method for guaranteeing QoS in the existing IEEE 802.11e MAC layer. It is divided into four AC (Access Category) according to the type of traffic. Different priorities are assigned to each category, and differentiated parameters are assigned by AC It is a contention-based medium access scheme that gives more transmission opportunities to prioritized traffic. For data transmission with priority, the EDCA block can assign 8 priorities from 0 to 7 and map data arriving at the MAC layer to 4 ACs according to priority.
- FIG. 8 shows the relationship between the user priority of EDCA and AC (Access Category) according to the embodiment of the present invention.
- AIFS [AC], CWmin [AC], and CWmax [AC] are used as the parameter values of the corresponding AC, where the Arbitration Inter-Frame Space (AIFS) checks whether the channel is idle Is the minimum time for.
- AIFS Arbitration Inter-Frame Space
- the transmitter If a collision occurs between the stations during frame transmission, the transmitter generates a new backoff counter.
- the four per AC transmit queues defined in the IEEE 802.11 MAC compete with each other for wireless medium access within a station. Since each AC has an independent backoff counter, a virtual collision can occur. If there are more than two ACs that have been backed off at the same time, the data of the AC with the highest priority is transmitted first, and the other ACs update the backoff counter by increasing the CW value. This conflict resolution process is called a virtual conflict process.
- EDCA also allows access to the channel during data transmission via Transmission Opportunity (TXOP). If one frame is too long to be transmitted during one TXOP, it may be divided into small frames and transmitted.
- TXOP Transmission Opportunity
- FIG. 9 shows a physical layer configuration of a V2X transmission apparatus according to an embodiment of the present invention.
- FIG. 9 shows a block diagram of a physical layer signal processing of IEEE 802.11 or ITS-G5.
- FIG. 9 illustrates a physical layer configuration according to an embodiment of the present invention, and is not limited to the above-described transmission standard technology.
- the physical layer processor of FIG. 9 includes a scrambler 9010, an FEC encoder 9020, an interleaver 9030, a mapper 9040, a pilot insertion block 9050, an IFFT block A Physical Layer Convergence Protocol (PLCP) sublayer baseband signal processing portion including at least one of an IFFT 9060, a guard insertion block 9070, and a preamble insertion block 9080, and a wave shaping (Physical Medium Dependant) sub-layer RF band signal processing portion including at least one of a wave shaping 9090, an I / Q modulation block 9100, and a DAC 9110 .
- PLCP Physical Layer Convergence Protocol
- wave shaping Physical Medium Dependant
- the scrambler 9010 may XOR the input bit stream with PRBS (Pseudo Random Binary Sequence) to randomize the input bit stream.
- PRBS Physical Random Binary Sequence
- the FEC encoder 9020 may add redundancy to the transmission data so that the error on the transmission channel can be corrected on the receiving side.
- the interleaver 9030 can interleave the input data / bit stream based on the interleaving rule so as to respond to a burst error. As an embodiment, when deep fading or erasure is applied to a QAM symbol, since each interleaved bit is mapped to each QAM symbol, it is determined that an error occurs in consecutive bits among the entire code word bits Can be prevented.
- the mapper 9040 can assign the input bit word to one constellation.
- the pilot insertion block 9050 inserts a reference signal at a predetermined position of the signal block. By using such a reference signal, the receiver can estimate a channel distortion phenomenon such as channel estimation, frequency offset, and timing offset.
- the IFFT block 9060 that is, the inverse waveform transform block, can convert the input signal so as to improve the transmission efficiency and flexibility in consideration of the characteristics of the transmission channel and the system structure.
- the IFFT block 9060 may use the inverse FFT operation to transform the frequency domain signal into the time domain.
- IFFT block 9060 may not be used or may be omitted in the case of a single carrier system.
- the guard insertion block 9070 may insert a guard interval between adjacent signal blocks to minimize the influence of delay spread of the transmission channel.
- the guard insertion block 9070 may insert a cyclic prefix in a guard interval period.
- the preamble insertion block 9080 may insert a signal of a determined type, i.e., a preamble, into the transmission signal so that the receiver can quickly and efficiently detect the target signal.
- a preamble insertion block 9080 may define a signal block / signal frame including a plurality of OFDM symbols, and may insert a preamble symbol at the beginning of a signal block / signal frame.
- Wave shaping block 9090 can waveform process the input baseband signal based on channel transmission characteristics.
- the waveform shaping block 9090 may perform square-root-raised cosine (SRRC) filtering to obtain a base of out-of-band emission of the transmitted signal.
- SRRC square-root-raised cosine
- waveform shaping block 9090 may not be used or may be omitted.
- the I / Q modulator 9100 can perform in-phase and quadrature modulation.
- a digital to analog converter (DAC) block 9110 converts an input digital signal into an analog signal and outputs the analog signal. The output analog signal can be transmitted via the output antenna.
- DAC digital to analog converter
- each of the blocks shown and described in FIG. 9 may be omitted, or replaced by other blocks having similar or equivalent functionality.
- the blocks in Fig. 9 may be configured as a whole or in a combination as necessary.
- the V2X communication apparatus can communicate based on the DSRC technique and the WAVE technique described in Figs.
- the V2X communication device may perform communication based on another communication technology including cellular technology such as LTE, LTE-A, and 5G.
- the MCD (Multimedia Content Dissemination) service will be described below.
- the MCD Basic Service is a V2X that describes multimedia content as information about road safety, traffic management, point of interest (POI), national patrimony, commecial, personal, Technology.
- a vehicle ITS-S or a roadside ITS-S may transmit a multimedia content message (MCM) to another vehicle ITS station or a roadside ITS station.
- MCM multimedia content message
- An ITS station may transmit the MCM in a broadcast, geographical broadcast, multicast or peer-to-peer manner.
- the sequence of processes and rules for transmitting an MCM may be referred to as the MCD protocol.
- FIG 10 shows an MCM format according to an embodiment of the present invention.
- the MCM is a message for describing a specific event as multimedia content.
- the MCM includes an ITS PDU header, a Management Container, a Situation Container, a Location / Location Container, an Application Container (APPIL Container), and a Multimedia Content Container.
- the ITS PDU header includes at least one of protocol version information, message type information, and ITS station ID information.
- the management container contains information related to MCM management and MCD protocol.
- the Container Container contains information related to the triggering source of the MCD.
- the Container can provide information about the type of event and the type of event.
- the location container may provide information about where the event occurred.
- the application container can provide application-specific information of an application using the MCM.
- the multimedia content container may include or provide the multimedia content itself.
- the management container may include at least one of time information for transmitting the MCM, a message ID, an ID of a linkable specific denoted message (DEN) message, and file format information of the multimedia content.
- time information for transmitting the MCM a message ID, an ID of a linkable specific denoted message (DEN) message, and file format information of the multimedia content.
- DEN linkable specific denoted message
- the ITS station may not be able to receive or process the message due to insufficient storage space. If all the MCMs constituting one multimedia content are not received, the corresponding multimedia contents may not be rendered. In the current MCD protocol, the size of the content can not be known, so that the receiver may not receive all of the MCM due to insufficient storage space, or it may unnecessarily perform the reception.
- the ITS station has certain multimedia content, which can be transmitted by other ITS stations. Even in this case, the ITS station can not recognize that the multimedia content being transmitted and the multimedia content that is currently being transmitted are the same content, so that the ITS station can receive the same multimedia contents redundantly.
- the multimedia content may be more suitable for reception over a different path (e.g., broadband) than communication between ITS stations.
- a different path e.g., broadband
- the specific multimedia content is optimized for a specific language, or when the multimedia content is once received and rendered, it may be recognized that the content is an inappropriate language.
- 11 is an ITS station architecture according to an embodiment of the present invention, in particular an architecture for message processing according to the MCD protocol.
- An MCD application is an application that describes events by using multimedia for various purposes.
- Various purposes include, for example, road safety, traffic management, driver assistance, travel information provision, commercial information provision, and personal / community information provision.
- MCD Basic Service In the transport ITS-S, the facility layer receives multimedia content and other event descriptions / descriptions from the application layer and sends the received content and description to the receiving ITS- / Transport to the transport layer.
- the facility layer can deliver the received multimedia content and description in the form of an MCM.
- the facility layer may divide the multimedia content into multiple segments and deliver a plurality of MCMs to the network / transport layer.
- An entity operating according to this MCD protocol may also be referred to as an MCD basic service entity.
- the facility layer can receive and parse the MCM from the network / transport layer, and deliver the multimedia content and other event descriptions of the MCM to the application layer. If a plurality of MCMs include segments of multimedia content, the facility layer may merge the multimedia content into the multimedia content and deliver the merged multimedia content to the application layer. Alternatively, the facility layer may pass each parsed segment directly to the application layer. In this process, the multimedia content or segments may be stored in local storage.
- the facility layer can perform a storage status test and determine the state type and the operation of the corresponding receiver. In addition, the facility layer can perform operations such as duplicate checking / checking, language checking, and validity checking. When a URL is found from the MCM, the facility layer can deliver the URL to the appropriate lower layer and the lower layer can retrieve / retrieve the multimedia content or segment by connecting to the received URL.
- Each module shown in FIG. 11 may be provided as a separate module or may be a logical object implemented and operated by software.
- the modules provided for providing the MCM basic service of FIG. 11 will be described below.
- MCM Interfacing module with N / T layers for the network / transport layer:
- the MCM interfacing module transmits the multimedia contents received from the application layer and other event descriptions in the form of MCM / Transport layer.
- the MCM interfacing module can receive and parse the MCM from the network / transport layer and deliver the multimedia content and other descriptions of the MCM to the application layer.
- the MCM generating module of the transmitting ITS-S generates an MCM from at least one of multimedia content, segments and other event descriptions.
- the MCM interfacing module receives multimedia content and other event descriptions from the application layer and sends them to the network / transport layer Lt; / RTI > In the receiving ITS-S, the MCM interfacing module may communicate the multimedia content of the MCM received from the network / transport layer and other event descriptions to the application layer.
- the MCM segment module can divide multimedia content into a plurality of (multile) segments.
- the MCM merging module of the receiving ITS-S can merge a plurality of segments into the multimedia contents.
- the MCM parsing module of the receiving ITS-S can extract at least one of multimedia content, segments, or other event descriptions from the MCM.
- Multimedia content storage module can store multimedia content or segments in a storage space such as local storage.
- the storage status testing module can perform status testing of local storage. Testing of the Storage State Testing Module can be used to determine the storage state type and its behavior.
- Multimedia Content Duplication Checking Module A Multimedia Content Duplication Checking Module can perform duplicate checking of multimedia contents.
- the multimedia content language checking module can perform language checking on the content.
- the multimedia validation checking module can perform MCM validation (in time-wise) checking.
- FIG. 12 shows a method of transmitting / receiving an MCM according to an embodiment of the present invention.
- the information transmitted between the ITS-S 1000 and the receiver ITS-S 1000 may include an event description including multimedia content and metadata related to the multimedia content.
- the multimedia content and event description may be included and delivered in the MCM.
- the operation of the transmitting ITS station 1000 is as follows.
- the application passes the multimedia content and other event descriptions to the MCD basic service entity of the facility layer.
- the MCD basic service entity formats the multimedia content and the event description and delivers the MCM to the lower layers.
- Lower Layers send MCMs with headers for communication at lower layers.
- the lower layers may include at least one of a network / transport layer or an access layer.
- the operation of the receiving ITS station 2000 is as follows.
- the lower layers receive the MCM having a header for communication in the lower layers, and perform processing of the lower layers.
- the lower layers pass the MCM to the MCD basic service entity.
- the MCD basic service entity performs message parsing for the MCM.
- the MCD basic service entity delivers the parsed multimedia content and event description to the application.
- FIG. 13 shows an MCM transmission / reception method according to an embodiment of the present invention.
- the information transmitted between the ITS-S 1000 and the receiver ITS-S 1000 may include an event description including multimedia content and metadata related to the multimedia content.
- the multimedia content and event description may be included and delivered in the MCM.
- FIG. 13 shows an MCD operation when the multimedia contents are separated and transmitted to a plurality of MCMs.
- the operation of the transmitting ITS station 1000 is as follows.
- the application passes the multimedia content and other event descriptions to the MCD basic service entity of the facility layer.
- the MCD basic service entity may divide the multimedia content into a plurality of segments (segments # 1 to #n).
- the MCD basic service entity formats a plurality of content segments and delivers a plurality of MCMs (MCM # 1 to MCM # n) for each content segment to lower layers.
- the lower layers transmit a plurality of MCMs (MCM # 1 to MCM # n) having a header for communication in lower layers.
- the operation of the receiving ITS station 2000 is as follows.
- the lower layers receive a plurality of MCMs (MCM # 1 to MCM # n) having a header for communication in lower layers, and perform processing of lower layers.
- the lower layers communicate a plurality of MCMs (MCM # 1 to MCM # n) to the MCD basic service entity.
- the MCD basic service entity obtains the content segments by performing message parsing for a plurality of MCMs.
- the MCD basic service entity may cache or store the generated content segments.
- the MCD basic service entity performs content merging for a plurality of parsed contents.
- the MCD basic service entity delivers multimedia content and event descriptions to the application.
- FIG. 14 shows an MCM transmission / reception method according to an embodiment of the present invention.
- the information transmitted between the ITS-S 1000 and the receiver ITS-S 1000 may include an event description including multimedia content and metadata related to the multimedia content.
- the multimedia content and event description may be included and delivered in the MCM.
- FIG. 14 shows an embodiment in which an application performs content merging on the side of the receiving ITS station 2000 when the multimedia content is separated and transmitted to a plurality of MCMs.
- the same description as in Fig. 13 is not duplicated.
- the operation of the receiving ITS station 2000 is as follows.
- the lower layers receive a plurality of MCMs (MCM # 1 to MCM # n) having a header for communication in lower layers, and perform processing of lower layers.
- the lower layers communicate a plurality of MCMs (MCM # 1 to MCM # n) to the MCD basic service entity.
- the MCD basic service entity may obtain a plurality of content segments or a plurality of multimedia contents by performing message parsing for a plurality of MCMs.
- the plurality of multimedia contents may include a segment for one multimedia content.
- the MCD basic service entity may deliver a plurality of acquired content segments or a plurality of multimedia contents to an application.
- An application may cache or store a plurality of multimedia content or a plurality of content segments. The application can then perform content merge.
- the information transmitted between the ITS-S 1000 and the receiver ITS-S 1000 may include an event description including multimedia content and metadata related to the multimedia content.
- the multimedia content and event description may be included and delivered in the MCM.
- FIG. 15 shows an embodiment in which the multimedia contents are delivered to a plurality of MCMs in a separated manner, where the merging of contents at the receiving ITS station 2000 side is performed at the facility layer, while other event descriptions are directly transmitted to the application layer.
- the same description as in Fig. 13 is not duplicated.
- the operation of the receiving ITS station 2000 is as follows.
- the lower layers receive a plurality of MCMs (MCM # 1 to MCM # n) having a header for communication in lower layers, and perform processing of lower layers.
- the lower layers communicate a plurality of MCMs (MCM # 1 to MCM # n) to the MCD basic service entity.
- the MCD basic service entity may obtain a plurality of content segments and event descriptions by performing message parsing for a plurality of MCMs.
- the MCD basic service entity may deliver each of the event descriptions obtained from the plurality of parsed MSMs to the application.
- the MCD basic service entity may cache or store the generated content segments.
- the MCD basic service entity performs content merging for a plurality of parsed contents.
- the MCD basic service entity delivers the merged multimedia content to the application.
- FIG. 16 shows a configuration of a management container of an MCM according to an embodiment of the present invention.
- FIG. 16 shows the configuration of the management container included in the MCM shown in FIG. 10, and description of the field / data described in FIG. 10 is not duplicated.
- FIG. 16 (a) shows an MCM format including size information
- Fig. 16 (b) shows a management container format having size information.
- the information / fields included in the management container are as follows.
- the request field indicates whether the MCM message is a request / request message or a response / response message.
- the reference time field indicates the MCM generation time.
- actID field The action ID field identifies the message as a combination of orginatingStationID and sequenceNumber.
- linkedDenm The linked DENM field identifies the associated DENM.
- the number of multimedia data units field indicates the number of multimedia data units in the multimedia container.
- the total number of data units field indicates the number of segments in the multimedia content.
- the unit number field indicates the sequence number of the segment of the multimedia content.
- multimediaFormatType The multimedia format type field indicates the format of the multimedia content.
- the size field of the multimedia indicates the size of the multimedia content delivered by at least one MCM in bytes. At least one MCM may have the same action ID.
- sizeOfSegment Indicates the size, in bytes, of the segment of the multimedia content delivered to this MCM.
- Table 1 shows the definition of the sizeInByte data element.
- the multimedia size information and the segment size information are data elements of sizeInByte and can be included in the management container to define the data size.
- the sizeInByte data element can define the size of arbitrary content in bytes.
- the MCD basic service entity of the facsimile layer of the receiving ITS-S can perform a storage status test based on the multimedia size information, the segment size information, and the local storage information.
- the receiving ITS-S can determine the state type based on the storage state test. Based on the determined state type, the MCD basic service entity determines whether to forward the received MCM to the application, ii) whether to forward the MCM segment to be received in the future to the application layer, iii) You can decide whether to perform the test.
- the ITS-S can determine the condition and type to perform the storage state test, and can perform the operation according to the determined type.
- Table 2 shows conditions, status types and corresponding actions for the storage state test of ITS-S.
- FIG. 17 shows an MCM transmission / reception method including size information according to an embodiment of the present invention.
- the information transmitted between the ITS-S 1000 and the receiver ITS-S 1000 may include an event description including multimedia content and metadata related to the multimedia content.
- the multimedia content and event description may be included and delivered in the MCM.
- FIG. 17 shows an MCD operation in the case where the multimedia contents are separated into a plurality of MCMs, and in particular, an example in which size information is included in the MCM. 13 to 15 do not duplicate.
- the operation of the receiving ITS station 2000 is as follows.
- the lower layers receive a plurality of MCMs (MCM # 1 to MCM # n) having a header for communication in lower layers, and perform processing of lower layers.
- the lower layers communicate a plurality of processed MCMs to a facility MCD basic service entity.
- the MCD basic service entity parses the MCM and performs a status test.
- the state test can be performed as shown in Table 2 and the above description. That is, the MCD basic service entity obtains the multimedia size information and the segment size information from the MCM, and compares the available size and size information of the storage of the received ITS-S.
- the MCD basic service entity may determine whether the tested state of the received and parsed MCMs (MCM # 1 to # n-1) corresponds to # 2-b or # 3 prior to the parsed MCM #n. When the tested state of the preceding MCMs (MCM # 1 to # n-1) corresponds to # 2-b or # 3, the MCD basic service entity does not receive the MCM #n or can ignore it. That is, the MCD basic service entity may discard the parsed segment #n.
- the MCD basic service entity may notify the MCMs # 1 to # n-1 if the tested state of the received and parsed MCMs MCM # 1 to # n-1 does not correspond to # 2-b or # 3 prior to the parsed MCM # MCM # 1 to # n-1) corresponds to # 1. If the tested state of the preceding MCMs does not also correspond to # 1, the MCD basic service entity performs a state test on MCM #n. If the tested state of the preceding MCMs corresponds to # 1, the MCD basic service entity may cache or store the content segment #n.
- the MCD basic service entity may perform a status test on MCM #n, i.e., segment #n. If the tested state is # 2-b or # 3, the MCD basic service entity does not receive MCM #n or can ignore it. That is, the MCD basic service entity may discard the parsed segment #n. If the tested status is # 1 or # 2-a, the MCD basic service entity may cache or store the content segment #n.
- the MCD basic service entity may merge the content.
- the MCD basic service entity may perform content merging when all segments corresponding to one multimedia content are received.
- the MCD basic service entity may deliver the merged content and other event descriptions to the application.
- the information transmitted between the ITS-S 1000 and the receiver ITS-S 1000 may include an event description including multimedia content and metadata related to the multimedia content.
- the multimedia content and event description may be included and delivered in the MCM.
- FIG. 18 shows an MCD operation in the case where the multimedia contents are separated and transmitted to a plurality of MCMs.
- FIG. 18 shows an embodiment in which size information is included in the MCM.
- 18 shows an embodiment in which an application performs content merging on the receiving ITS station 2000 side. 13 to 15 and 17 do not overlap.
- the operation of the receiving ITS station 2000 is as follows.
- the receiving ITS-S performs a status test on the MCMs in the same manner as in FIG.
- the MCD basic service entity may transmit a plurality of acquired content segments or a plurality of multimedia contents to an application.
- An application may cache or store a plurality of multimedia content or a plurality of content segments. The application can then perform content merge. In an embodiment, an application may perform content merging when all segments corresponding to one multimedia content are received.
- FIG. 19 shows an MCM transmission / reception method including size information according to an embodiment of the present invention.
- the information transmitted between the ITS-S 1000 and the receiver ITS-S 1000 may include an event description including multimedia content and metadata related to the multimedia content.
- the multimedia content and event description may be included and delivered in the MCM.
- FIG. 19 shows an MCD operation in a case where the multimedia contents are separated and transmitted to a plurality of MCMs, and in particular, an embodiment in which size information is included in the MCM.
- FIG. 19 shows an embodiment in which content merging at the receiving ITS station 2000 side is performed at the facility layer, while other event descriptions are directly transferred to the application layer. The same description as in Fig. 13 is not duplicated. 13 to 15 and 17 to 18 do not overlap.
- the receiving ITS-S performs a status test on the MCMs in the same manner as in FIG.
- the MCD basic service entity can deliver each of the event descriptions obtained from the parsed MSM to the application.
- the MCD basic service entity may cache or store the generated content segments.
- the MCD basic service entity performs content merging for a plurality of parsed contents.
- the MCD service entity may perform content merging when all segments corresponding to one multimedia content are received.
- the MCD basic service entity delivers the merged multimedia content to the application.
- the RSU transmits a video file.
- the video corresponds to a video clip of 5 megabytes.
- the video clip is divided into 5 segments of 1 MB size and transmitted.
- the currently transmitted MCM # 1 includes video segment 1.
- the MCM may include multimedia content size information, segment number information, and segment size information.
- the content size information may indicate 5 megabytes
- the segment number information may indicate 5
- the video segment size information may indicate 1 megabyte, respectively.
- the size and decoding performance of the available storage space of the V2X device of each vehicle, i.e., ITS-S, are different from each other.
- the available storage capacity is 10 megabytes.
- the available storage capacity is 3 megabytes, and ITS-S is capable of partial content rendering.
- the available storage capacity is 0.5 megabytes and partial content rendering is possible.
- the available storage capacity is 4 megabytes, and partial content rendering is not possible.
- each vehicle performs a state test as described above.
- the tested state corresponds to state # 1. Therefore, the vehicle a receives all the content segments, and no additional status test is required.
- the tested state corresponds to state # 2-a. Therefore, the vehicle b receives the corresponding content segment, and an additional status test is required.
- the tested state corresponds to state # 2-b. Thus, the vehicle c does not receive the content segment, and no additional testing is required.
- the tested state corresponds to state # 3. Thus, the vehicle d does not receive the content segment, and no further testing is required.
- 21 shows a configuration of a management container of an MCM according to an embodiment of the present invention.
- FIG. 21 shows the configuration of the management container included in the MCM shown in FIG. 10, and description of the field / data is not duplicated.
- FIG. 21A shows an MCM format including file name information, URI information and MD5 information
- FIG. 21B shows a management including file name (fileName) information
- URI Uniform Resource Identifier
- multimedia content identifier information information identifying the multimedia content may be referred to as multimedia content identifier information or multimedia file identifier information.
- the MCM may include multimedia identifier information.
- the multimedia identifier information may include at least one of file name information, URI information, or MD5 information.
- Table 3 shows the definition of the file name data element.
- the file name information can define the file name of the multimedia content.
- Table 4 shows definitions of URI data elements.
- the URI information can define the URI of the multimedia content.
- Table 5 shows the definition of MD5 data elements.
- the MD5 information can define the MD5 value of the multimedia content.
- FIG. 22 shows a method of transmitting / receiving an MCM according to an embodiment of the present invention.
- the information transmitted between the ITS-S 1000 and the receiver ITS-S 1000 may include an event description including multimedia content and metadata related to the multimedia content.
- the multimedia content and event description may be included and delivered in the MCM.
- FIG. 22 shows an MCD operation in the case where multimedia contents are separated and transmitted to a plurality of MCMs.
- FIG. 22 shows an embodiment in which the MCM includes multimedia content identifier information. 13 to 15 do not duplicate.
- the receiving ITS station 2000 parses the MCM and performs a duplicate check.
- the MCD basic service entity can check whether the content delivered by the received message is content that has been received or processed based on the multimedia content identifier information obtained from the MCM. If the content of the receiving MCM is content that overlaps the preprocessed content, the receiving ITS station 2000 may not receive or ignore / discard MCMs having the same message ID as this MCM. If the content of the receiving MCM is not content that overlaps the preprocessed content, the receiving ITS station 2000 may process the MCM as described in FIG.
- the information transmitted between the ITS-S 1000 and the receiver ITS-S 1000 may include an event description including multimedia content and metadata related to the multimedia content.
- the multimedia content and event description may be included and delivered in the MCM.
- FIG. 23 shows an MCD operation when the multimedia contents are separated and transmitted to a plurality of MCMs.
- FIG. 23 shows an embodiment in which the MCM includes multimedia content identifier information. 13 to 15 do not duplicate.
- the receiving ITS station 2000 parses the MCM and performs a duplicate check.
- the MCD basic service entity can check whether the content delivered by the received message is content that has been received or processed based on the multimedia content identifier information obtained from the MCM. If the content of the receiving MCM is content that overlaps the preprocessed content, the receiving ITS station 2000 may not receive or ignore / discard MCMs having the same message ID as this MCM. If the content of the receiving MCM is not the content that overlaps the preprocessed content, the receiving ITS station 2000 may process the MCM as described in FIG.
- FIG. 24 shows a method of transmitting / receiving an MCM according to an embodiment of the present invention.
- the information transmitted between the ITS-S 1000 and the receiver ITS-S 1000 may include an event description including multimedia content and metadata related to the multimedia content.
- the multimedia content and event description may be included and delivered in the MCM.
- FIG. 24 shows an embodiment in which the multimedia contents are delivered to a plurality of MCMs in a separated manner, in which content merging at the receiving ITS station 2000 side is performed at the facility layer, while other event descriptions are directly transmitted to the application layer.
- FIG. 24 shows an embodiment in which the MCM includes multimedia content identifier information. 13 to 15 do not duplicate.
- the receiving ITS station 2000 parses the MCM and performs a duplicate check.
- the MCD basic service entity can check whether the content delivered by the received message is content that has been received or processed based on the multimedia content identifier information obtained from the MCM. If the content of the receiving MCM is content that overlaps the preprocessed content, the receiving ITS station 2000 may not receive or ignore / discard MCMs having the same message ID as this MCM. If the content of the receiving MCM is not content that overlaps the preprocessed content, the receiving ITS station 2000 may process the MCM as described in FIG.
- 25 illustrates an MCD operation using multimedia content identifier information according to an embodiment of the present invention.
- the RSU transmits a still image file.
- the file name of the image file is "Gas_Station_1234.jpg”.
- the MCM header including the image file includes the above-described multi-keyer content identifier information.
- the MCM header includes file name information, and the file name information may indicate " Gas_Station_1234.jpg ".
- the video corresponds to a video clip of 5 megabytes.
- the video clip is divided into 5 segments of 1 MB size and transmitted.
- the currently transmitted MCM # 1 includes video segment 1.
- the MCM may include multimedia content size information, segment number information, and segment size information.
- the content size information may indicate 5 megabytes
- the segment number information may indicate 5
- the video segment size information may indicate 1 megabyte, respectively.
- the state of the V2X device of each vehicle that is, the ITS-S, is different from each other.
- the file "Gas_Station_1234.jpg” is already stored.
- the file "Gas_Station_1234.jpg” is not stored.
- Each vehicle carries out a redundancy check as described above.
- duplicate files are already stored.
- the vehicle a may ignore the MCM and not deliver the MCM to the application layer. That is, the vehicle (a) may discard the MCM corresponding to the duplicate file.
- the receiving MCM delivers a new file.
- the vehicle b can receive and process the MCM and deliver the processed file / segment to the application layer.
- 26 shows a configuration of a management container of an MCM according to an embodiment of the present invention.
- FIG. 26 shows the configuration of the management container included in the MCM shown in FIG. 10, and description of the field / data is not duplicated.
- FIG. 26 (a) shows an MCM format including URL (Uniform Resource Locator) information
- FIG. 26 (b) shows a management container format having URL information.
- URL Uniform Resource Locator
- the URL information can define the URL of the resource. That is, the URL information may indicate a URL for downloading the multimedia content.
- FIG. 27 shows a method of transmitting / receiving an MCM according to an embodiment of the present invention.
- the information transmitted between the ITS-S 1000 and the receiver ITS-S 1000 may include an event description including multimedia content and metadata related to the multimedia content.
- the multimedia content and event description may be included and delivered in the MCM.
- the operation of the transmitting ITS station 1000 is as follows.
- the application passes the URL and other event description of the multimedia content to the MCD basic service entity of the facility layer.
- the MCD basic service entity creates an MCM for the content and delivers it to the lower layers.
- the generated MCM includes URL information.
- the lower layers transmit MCMs with headers for communication at the lower layers.
- the operation of the receiving ITS station 2000 is as follows.
- the lower layers receive the MCM having a header for communication in the lower layers, and perform processing of the lower layers.
- the lower layers pass the MCM to the MCD basic service entity.
- the MCD basic service entity parses the message and checks the URL information.
- the MCD basic service entity passes the URL information to the other lower layers.
- the receiving ITS station 2000 may obtain the content by accessing the URL.
- the receiving ITS station may use lower layers (at least one of a network layer, a transport layer, a MAC layer, and a physical layer) that operate based on a protocol capable of receiving a content based on a URL.
- the MCD basic service entity may provide multimedia content and other event descriptions to the application.
- the vehicle (a) can transmit the MCM including the URL information to the vehicle (b).
- the vehicle (b) can receive and parse the MCM to obtain URL information.
- the vehicle (b) can access the URL and download the multimedia content.
- the URL may be any Internet address that can be downloaded and downloaded multimedia content.
- 29 shows a configuration of a management container of an MCM according to an embodiment of the present invention.
- FIG. 29 shows the configuration of the management container included in the MCM shown in FIG. 10, and description of the field / data is not duplicated.
- FIG. 29A shows an MCM format including multimedia language information
- FIG. 29B shows a management container format including multimedia language information. Except for the multimedia language information, the description of the information / field included in the management container will be described with reference to FIG. 16 and the description above.
- the multimedia language information may define the language used by the multimedia content.
- the multimedia language information may indicate a standardized language code such as ISO 639-1.
- the multimedia language information may indicate a numeric value to which a character-valued language code is mapped to reduce the format size.
- the receiving ITS-S may perform a language check based on the multimedia language information included in the MCM.
- the language check can be performed in a different mode depending on the location of the language check entity.
- Language check mode A If the language check entity is an MCD basic service entity
- a facility layer entity of the MCD basic service may maintain or access a set of acceptable languages.
- the MCD basic service can check whether the language information of the received MCM matches the set of allowable languages.
- Mode B the facility layer entity of the MCD basic service does not maintain or access a set of allowable languages.
- the MCD basic service receives or acquires the language information
- the MCD basic service delivers the language information to the application.
- An application may maintain or access a set of acceptable languages. The application can check whether the language information of the received MCM matches the set of allowable languages.
- the facility layer entity of the MCD basic service does not maintain or access a set of allowable languages.
- the MCD basic service receives or obtains language information
- the ITS-S may ask the user / driver via the HIM if the language is acceptable.
- Mode D the facility layer entity of the MCD basic service does not maintain or access a set of allowable languages.
- the MCD basic service receives or acquires the language information
- the MCD basic service delivers the language information to the application.
- the application may ask the user / driver via the HIM and / or directly whether the language is acceptable.
- FIG. 30 shows a method of transmitting / receiving an MCM according to an embodiment of the present invention.
- the information transmitted between the ITS-S 1000 and the receiver ITS-S 1000 may include an event description including multimedia content and metadata related to the multimedia content.
- the multimedia content and event description may be included and delivered in the MCM.
- Figure 30 shows an MCD operation when the multimedia contents are separated and transmitted to a plurality of MCMs.
- Figure 30 illustrates an embodiment in which the MCM includes multimedia language information. 13 to 15 do not duplicate.
- FIG 30 shows the language check mode A described above. That is, the MCD basic service entity performs the language check.
- the receiving ITS station 2000 parses the MCM and performs a language check.
- the MCD basic service entity may use the multimedia language information obtained from the MCM to determine whether the language of the content is an acceptable language.
- the MCD basic service entity can determine whether the language of the content is an acceptable language based on the set of allowable languages. If the language of the content of the receiving MCM is not an acceptable language, the receiving ITS station 2000 may not receive or discard / discard MCMs having the same message ID as this MCM. If the language of the content of the receiving MCM is an acceptable language, the MCD basic service may cache / store the multimedia segment # 1 and receive the remaining MCMs.
- FIG. 31 shows an MCM transmission / reception method according to an embodiment of the present invention.
- the information transmitted between the ITS-S 1000 and the receiver ITS-S 1000 may include an event description including multimedia content and metadata related to the multimedia content.
- the multimedia content and event description may be included and delivered in the MCM.
- FIG. 31 shows an MCD operation in the case where multimedia contents are separated and transmitted to a plurality of MCMs.
- FIG. 31 shows an embodiment in which the MCM includes multimedia language information. 13 to 15 do not duplicate.
- 31 shows the language check mode B described above. That is, the application performs a language check.
- the receiving ITS station 2000 parses the MCM and delivers the obtained language information to the application.
- the application performs a duplicate check.
- the application can use the multimedia language information to determine whether the language of the content is an acceptable language.
- the application can determine whether the language of the content is an acceptable language based on the set of allowable languages.
- the application can pass the language check result to the MCD basic service entity. If the language of the content of the receiving MCM is not an acceptable language, the receiving ITS station 2000 may not receive or discard / discard MCMs having the same message ID as this MCM. If the language of the content of the receiving MCM is an acceptable language, the MCD basic service may cache / store the multimedia segment # 1 and receive the remaining MCMs.
- the information transmitted between the ITS-S 1000 and the receiver ITS-S 1000 may include an event description including multimedia content and metadata related to the multimedia content.
- the multimedia content and event description may be included and delivered in the MCM.
- FIG. 32 shows an MCD operation when the multimedia contents are separated and transmitted to a plurality of MCMs.
- FIG. 32 shows an embodiment in which the MCM includes multimedia language information. 13 to 15 do not duplicate.
- the receiving ITS station 2000 parses the MCM and delivers the obtained language information to the application.
- the MCD basic service entity delivers the language information to the application and then to the HIM (Human Machine Interface).
- the MCD Basic Service can request the user to check the language via the HMI.
- the application may request the user to check the language directly or via the HMI.
- the receiving ITS station 2000 may not receive or discard / discard MCMs having the same message ID as this MCM. If the language of the content of the receiving MCM is an acceptable language, the MCD basic service may cache / store the multimedia segment # 1 and receive the remaining MCMs.
- FIG 33 illustrates an MCD operation using multimedia language information according to an embodiment of the present invention.
- the RSU transmits an English audio file.
- Multimedia language information of MCM transmitting English audio file directs English.
- the state of the V2X device of each vehicle that is, the ITS-S, is different from each other.
- the driver may not understand English.
- the driver may understand the English language.
- Vehicle (a) may ignore the MCM and not deliver the MCM to the application layer. That is, the vehicle (a) may discard the MCM.
- Vehicle b may receive and process the MCM and deliver the processed file / segment to the application layer.
- FIG. 34 illustrates a configuration of a management container of an MCM according to an embodiment of the present invention.
- FIG. 34 shows the structure of the management container included in the MCM shown in FIG. 10, and description of the field / data is not duplicated.
- Fig. 34 (a) shows an MCM format including valid time (validTimeUntil) information
- Fig. 34 (b) shows a management container format including valid time (validTimeUntil) information. Except for the validity time (validTimeUntil) information, the description of the information / field included in the management container is described with reference to FIG. 16 and the above description.
- the valid time information may use a time stamp (TimestampsIts) as a data type.
- the receiving ITS-S may not provide the multimedia content received before the valid time if the effective time elapses, based on the valid time information of the received multimedia content. That is, after the expiration time, the MCD basic service entity does not deliver the corresponding multimedia content to the application. After the expiration time, the application does not use the corresponding multimedia content. After the expiration time, the MCD basic service entity or management entity may delete the corresponding multimedia content from the storage or cache.
- 35 shows a management container and a geo-networking basic header of an MCM according to an embodiment of the present invention.
- the basic header may include at least one of a version field, an NH field (Next Header), a LT (LifeTime) field, and a Remaining Hop Limit (RHL) field. Fields included in the basic header are described below. The bit size constituting each field is only an embodiment and may be changed.
- Version (4-bit) The version field indicates the version of the geo-networking protocol.
- NH (4 bits): NH (Next Header) field indicates the type of the following header / field. If the field value is 1, a common header is followed. If the field value is 2, a secured packet can be followed.
- the LT (LifeTime) field indicates the maximum lifetime of the packet.
- RHL 8 bits: The Remaining Hop Limit (RHL) field indicates the residual hop limit.
- the RHL field value can be reduced by one for each forwarding on the GeoAdhoc router. When the RHL field value reaches 0, the packet is no longer forwarded.
- Multimedia content can be multi-hop forwarded using a geo-networking protocol.
- the multimedia content may be set to be no longer forwarded after the expiration time to avoid over-occupying the channel. That is, if the time of the LT field has passed, the ITS-S can stop the forwarding of the packet.
- the forwarding ITS-S can perform forwarding without checking the information of the facility layer.
- the ITS station may perform the forwarding without checking the validity time. Accordingly, the ITS-S can transmit the value of the LT field of the basic header of the geo-networking PDU by setting it equal to or smaller than the value of the effective time field of the MCM field.
- LT represents the value of the LifeTime field in the Geo Networking Basic header.
- VT represents the value of the " validTimeUntil " field in the management container of the PDU from the MCD basic service entity
- CT represents the time at which the geo-networking PDU is generated
- LT represents the value obtained by subtracting CT from VTU (LT ⁇ VTU - CT) The value of LT must not exceed the difference between the valid time and the time at which the geo - networking PDU is generated.
- the RSU transmits MCM-xyz.
- the RSU geo-broadcasts the MCM. That is, the RSU sends a geo-networking message to broadcast the message at region "C".
- the time when the RSU transmits the MCM is t0, and the valid time (validTimeUntil) information indicates t5.
- the ITS-S may divide the multimedia content into a plurality of segments instead of transmitting the MCM to one MCM, and may transmit the segments as a plurality of MCMs.
- the maximum size of a message that can be transmitted at a time can be determined based on the access layer technology used for message transmission. Selection of the access layer technology used for transmission may be performed by at least one of an application layer, a facility layer, a network / transport layer, or a management entity.
- the maximum message size can be determined.
- PDU Protocol Data Unit
- layer A knows the maximum message size: Estimate the header size to be added in the lower layer, so that the message size to be transmitted over-the-air will not exceed the maximum PDU size of layer A .
- the layer A PDU is generated by segmenting the PDU to be smaller than the layer A maximum PDU size. Then, the generated layer A PDU is transferred to the lower layer.
- the received upper layer PDU may be a media content file when the layer A is an application layer.
- layer A does not know the maximum message size: PDUs of layer A are created without segmenting the upper layer PDU received from the upper layer. Then, the generated layer A PDU is transferred to the lower layer.
- the received upper layer PDU may be a media content file when the layer A is an application layer.
- FIG. 37 shows a V2X communication apparatus according to an embodiment of the present invention.
- the V2X communication device 37000 may include a memory 37010, a processor 37020, and a communication unit 37030.
- the V2X communication device may be an OBU (On Board Unit) or an RSU (Road Side Unit), or may be included in an OBU or an RSU.
- the V2X communication device may be included in the ITS station or may correspond to the ITS station.
- the communication unit 37030 may be connected to the processor 37020 to transmit / receive radio signals.
- the communication unit 37030 may upconvert the data received from the processor 37020 to the transmit and receive band and transmit the signal.
- the communication unit may implement the operation of the access layer.
- the communication unit may implement the operation of the physical layer included in the access layer, or may further implement the operation of the MAC layer.
- the communication unit may comprise a plurality of subcommunication units for communicating in accordance with a plurality of communication protocols.
- the processor 37020 may be coupled to the communication unit 37030 to implement the operation of the layers according to the ITS system or the WAVE system.
- the processor 37020 may be configured to perform operations in accordance with various embodiments of the present invention in accordance with the above figures and description. Also, at least one of the modules, data, programs, or software that implement the operation of the V2X communication device 37000 according to various embodiments of the invention described above may be stored in memory 37010 and executed by processor 37020 have.
- the memory 37010 is coupled to the processor 37020 to store various information for driving the processor 37020.
- Memory 37010 may be internal to processor 37020 or external to processor 37020 and coupled to processor 37020 by known means.
- the memory may include a secure / non-secure storage device, or may be included in a secure / non-secure storage device. Depending on the embodiment, the memory may be referred to as a secure / non-secure storage device.
- V2X communication device 37000 of FIG. 37 can be implemented such that the various embodiments of the present invention described above are applied independently or two or more embodiments are applied together.
- the GNSS receiver and DSRD radio may be included in the communication unit 37030 of FIG.
- the DSRC device processor may be included in the communication unit 37030 of Fig. 37 or may be included in the processor 37020.
- FIG. 38 shows a method of receiving a multimedia content message of a V2X communication apparatus according to an embodiment of the present invention.
- the V2X communication device may receive the multimedia content message (S38010).
- the V2X communication device can receive multimedia content messages based on various communication protocols.
- the V2X communication apparatus can parse the multimedia content message (S38020).
- the V2X communication device can parse the multimedia content message and obtain various information about the message.
- the V2X communication device may acquire multimedia content or a content segment.
- the V2X communication device can store / process the content or the content segment as described above and provide it to the user through the application.
- the V2X communication device may discard the content or the content segment without storing / processing based on the information on the message as described above.
- the multimedia content message includes a header including a protocol version and a message ID, a management container including information related to an MCM (Multimedia Content Message) management and an MCD (Multimedia Content Dissemination) protocol, A location container including location information of the event, and a multimedia content container including the multimedia content.
- MCM Multimedia Content Message
- MCD Multimedia Content Dissemination
- the management container includes at least one of a numberOfMultimediaUnit information indicating the number of multimedia data units included in the multimedia container and a multimedia format type information about a multimedia content included in the multimedia container.
- the description of the multimedia content message and the management container is as described above.
- the management container may further include size information for at least one of the segments of the multimedia content or multimedia content.
- the V2X communication apparatus can determine whether to store the multimedia content or the multimedia segment based on the size information and the storage information of the V2X communication apparatus.
- the management container may further include multimedia content identifier information.
- the V2X communication device may determine whether the multimedia content or the segment of the multimedia content message overlaps with the pre-received multimedia content based on the multimedia content identifier information.
- the management container may further include URL information.
- the V2X communication device can access the URL indicated by the URL information to receive the multimedia content.
- the management container may further include language information indicating the language of the multimedia content.
- the V2X communication device can determine whether the language of the multimedia content is an acceptable language based on the language information.
- the management container may further include valid time information.
- the V2X communication apparatus can determine whether to provide or forward the multimedia content based on the valid time information.
- Embodiments in accordance with the present invention may be implemented by various means, for example, hardware, firmware, software, or a combination thereof.
- an embodiment of the present invention may include 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, processors, controllers, microcontrollers, microprocessors, and the like.
- ASICs application specific integrated circuits
- DSPs digital signal processors
- DSPDs digital signal processing devices
- PLDs programmable logic devices
- an embodiment of the present invention may be implemented in the form of a module, a procedure, a function, or the like for performing the functions or operations described above.
- the software code can be stored in memory and driven by the processor.
- the memory is located inside or outside the processor and can exchange data with the processor by various means already known.
- the present invention is used in a range of vehicle communications.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Artificial Intelligence (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Multimedia (AREA)
- Mobile Radio Communication Systems (AREA)
- Computer And Data Communications (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
Abstract
Description
Descriptive Name | sizeInByte |
Identifier | DataType_xxx |
ASN.1 representation | sizeInByte ::= INTEGER(0..15000) |
Definition | This DE (Data Element) defines the size in byte of any content. |
Unit | N/A |
조건(Condition) | 상태 타입(Status Type) | 수신 ITS-S 동작(Receiver ITS-S Behavior) | |
가용 스토리지 양 >= 전체 컨텐트 사이즈(available storage amount >= overall content size) | Status #1 | 모든 컨텐트 세그먼트들 수신 및 추가 상태 테스트 불필요함(receiving all content segments AND no further status test needed) | |
가용 스토리지 양 < 전체 컨텐트 사이즈,및 부분 컨텐트 렌더링 가능(available storage amount < overall content size AND partial content rendering available) | Status #2 | ||
및(AND) | 가용 스토리지 양 >= 컨텐트 세그먼트 사이즈(available storage amount >= content segment size) | Status #2-a | 해당 컨텐트 세그먼트 수신 및 추가 상태 테스트 필요함(receiving this content segment AND further status test needed) |
및(AND) | 가용 스토리지 양 < 컨텐트 세그먼트 사이즈 | Status #2-b | 컨텐트 세그먼트 수신하지 않고, 추가 상태 테스트 불필요함(not receiving any content segment AND no further status test needed) |
가용 스토리지 양 < 전체 컨텐트 사이즈, 및 부분 컨텐트 렌더링 불가(available storage amount < overall content size AND partial content rendering not available) | Status #3 | 컨텐트 세그먼트 수신하지 않고, 추가 상태 테스트 불필요함(not receiving any content segment AND no further status test needed) |
Descriptive Name | fileName |
Identifier | DataType_xxx |
ASN.1 representation | fileName ::= PrintableString (SIZE(N)) |
Definition | This DE (Data Element) defines the file name of the multimedia content. |
Unit | N/A |
Descriptive Name | URI |
Identifier | DataType_xxx |
ASN.1 representation | URI ::= PrintableString (SIZE(N)) |
Definition | This DE (Data Element) defines the URI of the multimedia content. |
Unit | N/A |
Descriptive Name | MD5 |
Identifier | DataType_xxx |
ASN.1 representation | MD5 ::= PrintableString (SIZE(N)) |
Definition | This DE (Data Element) defines the MD5 value of the multimedia content. |
Unit | N/A |
Descriptive Name | URL |
Identifier | DataType_xxx |
ASN.1 representation | URL ::= PrintableString (SIZE(N)) |
Definition | This DE (Data Element) defines the URL of resource. |
Unit | N/A |
Descriptive Name | fileName |
Identifier | DataType_xxx |
ASN.1 representation | MultimediaLanguage ::= INTEGER {English(1), Korean(2), … } (1..1000)Or MultimediaLanguage ::= PrintableString (SIZE(2)) |
Definition | This DE (Data Element) defines the language used by the multimedia content. |
Unit | N/A |
Claims (12)
- V2X(Vehicle to everything) 통신 장치의 멀티미디어 컨텐트 메세지 수신 방법에 있어서,멀티미디어 컨텐트 메세지를 수신하는 단계;상기 멀티미디어 컨텐트 메세지를 파싱하는 단계; 및상기 멀티디미어 컨텐트 메세지에 포함된 멀티미디어 컨텐트 또는 멀티미디어 컨텐트의 일부인 컨텐트 세그먼트를 획득하는 단계를 포함하며,상기 멀티미디어 컨텐트 메세지는, 프로토콜 버전 및 메세지 ID를 포함하는 헤더, MCM(Multimedia Content Message) 매니지먼트 및 MCD(Multimedia Content Dissemination) 프로토콜 관련 정보를 포함하는 매니지먼트 컨테이너, 이벤트를 기술하는 정보를 포함하는 상황(situation) 컨테이너, 상기 이벤트의 위치 정보를 포함하는 위치(location) 컨테이너 및 상기 멀티미디어 컨텐트를 포함하는 멀티미디어 컨텐트 컨테이너를 포함하고,상기 매니지먼트 컨테이너는, 상기 멀티미디어 컨테이너에 포함된 멀티미디어 데이터 유닛의 수를 지시하는 멀티미디어 데이터 유닛의 수(numberOfMultimediaUnit) 정보, 상기 멀티미디어 컨테이너에 포함된 상기 멀티미디어 컨텐트에 대한 멀티미디어 포맷 타입(multimediaFormatType) 정보를 포함하는, 멀티미디어 컨텐트 메세지 수신 방법.
- 제 1 항에 있어서,상기 매니지먼트 컨테이너는, 상기 멀티미디어 컨텐트 또는 상기 멀티미디어 컨텐트의 세그먼트 중 적어도 하나에 대한 사이즈 정보를 더 포함하고,상기 멀티미디어 컨텐트 메세지 수신 방법은,상기 사이즈 정보 및 상기 V2X 통신 장치의 스토리지 정보에 기초하여 상기 멀티미디어 컨텐트 또는 컨텐트 세그먼트의 저장 여부를 결정하는 단계를 더 포함하는, 멀티미디어 컨텐트 메세지 수신 방법.
- 제 1 항에 있어서,상기 매니지먼트 컨테이너는, 멀티미디어 컨텐트 식별자 정보를 더 포함하고,상기 멀티미디어 컨텐트 메세지 수신 방법은,상기 멀티미디어 컨텐트 식별자 정보에 기초하여 상기 멀티미디어 컨텐트 메세지의 멀티미디어 컨텐트 또는 컨텐트 세그먼트가 기-수신한 멀티미디어 컨텐트와 중복되는지 여부를 결정하는 단계를 더 포함하는, 멀티미디어 컨텐트 메세지 수신 방법.
- 제 1 항에 있어서,상기 매니지먼트 컨테이너는, URL 정보를 더 포함하고,상기 멀티미디어 컨텐트 메세지 수신 방법은,상기 URL 정보가 지시하는 URL에 접속하여 상기 멀티미디어 컨텐트를 수신하는 단계를 더 포함하는, 멀티미디어 컨텐트 메세지 수신 방법.
- 제 1 항에 있어서,상기 매니지먼트 컨테이너는, 상기 멀티미디어 컨텐트의 언어를 지시하는 언어 정보를 더 포함하고,상기 멀티미디어 컨텐트 메세지 수신 방법은,상기 언어 정보에 기초하여 상기 멀티미디어 컨텐트의 상기 언어가 허용(acceptable) 언어인지 여부를 결정하는 단계를 더 포함하는, 멀티미디어 컨텐트 메세지 수신 방법.
- 제 1 항에 있어서,상기 매니지먼트 컨테이너는, 유효 시간 정보를 더 포함하고,상기 멀티미디어 컨텐트 메세지 수신 방법은,상기 유효 시간 정보에 기초하여 상기 멀티미디어 컨텐트의 제공 또는 포워딩 여부를 결정하는 단계를 더 포함하는, 멀티미디어 컨텐트 메세지 수신 방법.
- V2X 통신 장치에 있어서,데이터를 저장하는 메모리;무선 신호를 송수신하는 통신 유닛; 및상기 통신 유닛을 제어하는 프로세서를 포함하고,상기 V2X 통신 장치는,멀티미디어 컨텐트 메세지를 수신하고,상기 멀티미디어 컨텐트 메세지를 파싱하고, 및상기 멀티디미어 컨텐트 메세지에 포함된 멀티미디어 컨텐트 또는 멀티미디어 컨텐트의 일부인 컨텐트 세그먼트를 획득하며,상기 멀티미디어 컨텐트 메세지는, 프로토콜 버전 및 메세지 ID를 포함하는 헤더, MCM(Multimedia Content Message) 매니지먼트 및 MCD(Multimedia Content Dissemination) 프로토콜 관련 정보를 포함하는 매니지먼트 컨테이너, 이벤트를 기술하는 정보를 포함하는 상황(situation) 컨테이너, 상기 이벤트의 위치 정보를 포함하는 위치(location) 컨테이너 및 상기 멀티미디어 컨텐트를 포함하는 멀티미디어 컨텐트 컨테이너를 포함하고,상기 매니지먼트 컨테이너는, 상기 멀티미디어 컨테이너에 포함된 멀티미디어 데이터 유닛의 수를 지시하는 멀티미디어 데이터 유닛의 수(numberOfMultimediaUnit) 정보, 상기 멀티미디어 컨테이너에 포함된 상기 멀티미디어 컨텐트에 대한 멀티미디어 포맷 타입(multimediaFormatType) 정보를 포함하는, V2X 통신 장치.
- 제 7 항에 있어서,상기 매니지먼트 컨테이너는, 상기 멀티미디어 컨텐트 또는 상기 멀티미디어 컨텐트의 세그먼트 중 적어도 하나에 대한 사이즈 정보를 더 포함하고,상기 V2X 통신 장치는, 상기 사이즈 정보 및 상기 V2X 통신 장치의 스토리지 정보에 기초하여 상기 멀티미디어 컨텐트 또는 컨텐트 세그먼트의 저장 여부를 결정하는, V2X 통신 장치.
- 제 7 항에 있어서,상기 매니지먼트 컨테이너는, 멀티미디어 컨텐트 식별자 정보를 더 포함하고,상기 V2X 통신 장치는, 상기 멀티미디어 컨텐트 식별자 정보에 기초하여 상기 멀티미디어 컨텐트 메세지의 멀티미디어 컨텐트 또는 컨텐트 세그먼트가 기-수신한 멀티미디어 컨텐트와 중복되는지 여부를 결정하는, V2X 통신 장치.
- 제 7 항에 있어서,상기 매니지먼트 컨테이너는, URL 정보를 더 포함하고,상기 V2X 통신 장치는, 상기 URL 정보가 지시하는 URL에 접속하여 상기 멀티미디어 컨텐트를 수신하는, V2X 통신 장치.
- 제 7 항에 있어서,상기 매니지먼트 컨테이너는, 상기 멀티미디어 컨텐트의 언어를 지시하는 언어 정보를 더 포함하고,상기 V2X 통신 장치는, 상기 언어 정보에 기초하여 상기 멀티미디어 컨텐트의 상기 언어가 허용(acceptable) 언어인지 여부를 결정하는, V2X 통신 장치.
- 제 7 항에 있어서,상기 매니지먼트 컨테이너는, 유효 시간 정보를 더 포함하고,상기 V2X 통신 장치는, 상기 유효 시간 정보에 기초하여 상기 멀티미디어 컨텐트의 제공 또는 포워딩 여부를 결정하는, V2X 통신 장치.
Priority Applications (8)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201780089324.9A CN110476403B (zh) | 2017-09-29 | 2017-09-29 | V2x通信设备及由其发送/接收多媒体内容的方法 |
JP2019528883A JP6816281B2 (ja) | 2017-09-29 | 2017-09-29 | V2x通信装置及びそのマルチメディアコンテンツの送信/受信方法 |
KR1020197011388A KR102062298B1 (ko) | 2017-09-29 | 2017-09-29 | V2x 통신 장치 및 그의 멀티미디어 컨텐트 전송/수신 방법 |
KR1020197038656A KR102127436B1 (ko) | 2017-09-29 | 2017-09-29 | V2x 통신 장치 및 그의 멀티미디어 컨텐트 전송/수신 방법 |
EP17926340.5A EP3528467B1 (en) | 2017-09-29 | 2017-09-29 | V2x communication device and multimedia content transmitting/receiving method thereof |
PCT/KR2017/010954 WO2019066106A1 (ko) | 2017-09-29 | 2017-09-29 | V2x 통신 장치 및 그의 멀티미디어 컨텐트 전송/수신 방법 |
US16/407,953 US10686917B2 (en) | 2017-09-29 | 2019-05-09 | V2X communication apparatus and method for transmitting/receiving multimedia content thereby |
US16/871,872 US11012543B2 (en) | 2017-09-29 | 2020-05-11 | V2X communication apparatus and method for transmitting/receiving multimedia content thereby |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/KR2017/010954 WO2019066106A1 (ko) | 2017-09-29 | 2017-09-29 | V2x 통신 장치 및 그의 멀티미디어 컨텐트 전송/수신 방법 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/407,953 Continuation US10686917B2 (en) | 2017-09-29 | 2019-05-09 | V2X communication apparatus and method for transmitting/receiving multimedia content thereby |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019066106A1 true WO2019066106A1 (ko) | 2019-04-04 |
Family
ID=65903704
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2017/010954 WO2019066106A1 (ko) | 2017-09-29 | 2017-09-29 | V2x 통신 장치 및 그의 멀티미디어 컨텐트 전송/수신 방법 |
Country Status (6)
Country | Link |
---|---|
US (2) | US10686917B2 (ko) |
EP (1) | EP3528467B1 (ko) |
JP (1) | JP6816281B2 (ko) |
KR (2) | KR102127436B1 (ko) |
CN (1) | CN110476403B (ko) |
WO (1) | WO2019066106A1 (ko) |
Families Citing this family (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2019066106A1 (ko) * | 2017-09-29 | 2019-04-04 | 엘지전자(주) | V2x 통신 장치 및 그의 멀티미디어 컨텐트 전송/수신 방법 |
CN108182817A (zh) * | 2018-01-11 | 2018-06-19 | 北京图森未来科技有限公司 | 自动驾驶辅助系统、路侧端辅助系统和车载端辅助系统 |
JP6750646B2 (ja) * | 2018-06-07 | 2020-09-02 | トヨタ自動車株式会社 | 車載装置、情報処理方法、および、情報処理プログラム |
EP3594712B1 (en) | 2018-07-12 | 2023-11-22 | Cohda Wireless Pty Ltd. | A method and system for estimating range between and position of objects using a wireless communication system |
US11202273B2 (en) * | 2019-11-08 | 2021-12-14 | Blackberry Limited | Aggregating messages into a single transmission |
US11151879B2 (en) * | 2019-11-11 | 2021-10-19 | Continental Teves Ag & Co. Ohg | Communication device, method for execution by a communication device, and method for improving traffic safety of a road user |
CN113055846A (zh) * | 2019-12-26 | 2021-06-29 | 索尼公司 | 电子设备、无线通信方法和计算机可读存储介质 |
CN113055736B (zh) * | 2019-12-27 | 2023-02-21 | 中信科智联科技有限公司 | 一种视频接收、发送方法、终端设备及路侧设备 |
CN111016555A (zh) * | 2019-12-31 | 2020-04-17 | 深圳成谷科技有限公司 | 一种基于obu实现的牵引车和挂车胎压监测方法和装置 |
CN113327446B (zh) * | 2020-02-28 | 2022-06-10 | 大唐高鸿智联科技(重庆)有限公司 | 信息传输处理方法、装置、处理设备、车载单元及车辆 |
KR102328492B1 (ko) * | 2020-10-30 | 2021-11-18 | 주식회사 아이티텔레콤 | 멀티홉 방식의 v2x 데이터 송신 장치 및 수신 장치 |
CN116830536A (zh) * | 2021-01-05 | 2023-09-29 | 华为技术有限公司 | 高级驾驶辅助系统中的通信方法和装置 |
US11890997B2 (en) | 2021-03-22 | 2024-02-06 | GM Global Technology Operations LLC | Antimicrobial metallic touch surfaces and methods for making the same |
KR102543820B1 (ko) * | 2021-05-18 | 2023-06-19 | 주식회사 아이티텔레콤 | Ai v2x obu를 이용한 미끄럼 사고 예방 시스템 |
KR102541407B1 (ko) * | 2021-05-18 | 2023-06-12 | 주식회사 아이티텔레콤 | C-its mec 기반의 자율주행을 위한 실시간 교통정보제공시스템 |
WO2022271278A1 (en) * | 2021-06-25 | 2022-12-29 | Qualcomm Incorporated | Techniques to facilitate v2x identifier-based transport types of a geographical network layer protocol |
CN113381926B (zh) * | 2021-08-12 | 2022-01-18 | 深圳市城市交通规划设计研究中心股份有限公司 | 一种车路协同数据资源管理方法、装置及存储介质 |
GB2611540A (en) * | 2021-10-06 | 2023-04-12 | Canon Kk | Pre-crash DENM message within an intelligent transport system |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020078228A1 (en) * | 2000-12-20 | 2002-06-20 | Jussi Kuisma | Arrangement for implementing transmission of multimedia messages |
EP2667625A2 (en) * | 2011-01-19 | 2013-11-27 | Samsung Electronics Co., Ltd | Apparatus and method for transmitting multimedia data in a broadcast system |
KR101626686B1 (ko) * | 2011-10-13 | 2016-06-01 | 삼성전자주식회사 | 방송 시스템에서의 제어 메시지 구성 장치 및 방법 |
US20160285935A1 (en) * | 2015-03-27 | 2016-09-29 | Qualcomm Incorporated | Point-to-multipoint broadcast assisted vehicle-to-x broadcast |
Family Cites Families (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2845468B1 (fr) * | 2002-10-02 | 2005-01-14 | Telediffusion De France Tdf | Systeme d'affichage de contenus multimedia dans un vehicule |
KR20060122668A (ko) * | 2005-05-27 | 2006-11-30 | 엘지전자 주식회사 | 교통 정보 제공 방법 및 수신 장치 |
EP2036369B1 (en) * | 2006-06-08 | 2017-08-16 | LG Electronics Inc. | Method and apparatus for providng and using public transportation information |
EP2156582A4 (en) | 2007-04-09 | 2011-09-21 | Lg Electronics Inc | PROVISION AND USE OF INFORMATION ABOUT VIDEO WITH REGARD TO TRANSPORT SITUATIONS |
US20100057333A1 (en) | 2008-08-27 | 2010-03-04 | Hankuk University Of Foreign Studies Research And Industry-University Cooperation Foundation | Navigation system |
US8478209B2 (en) * | 2011-05-05 | 2013-07-02 | GM Global Technology Operations LLC | Method and apparatus for multimedia content promotion in vehicular wireless networks |
KR101279887B1 (ko) * | 2011-10-21 | 2013-06-28 | 주식회사 맥스포 | V2i 네트워크에서 브로드캐스팅 메시지 전송 방법 |
US9191133B2 (en) * | 2012-03-01 | 2015-11-17 | Htc Corporation | Multimedia data distribution system and operating method thereof |
KR101868628B1 (ko) * | 2014-04-30 | 2018-06-18 | 엘지전자 주식회사 | 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법 |
JP2018523322A (ja) * | 2015-06-24 | 2018-08-16 | インテル アイピー コーポレーション | Vehicle‐to‐anything(v2x)通信の拡張サポート |
WO2019066106A1 (ko) * | 2017-09-29 | 2019-04-04 | 엘지전자(주) | V2x 통신 장치 및 그의 멀티미디어 컨텐트 전송/수신 방법 |
-
2017
- 2017-09-29 WO PCT/KR2017/010954 patent/WO2019066106A1/ko unknown
- 2017-09-29 KR KR1020197038656A patent/KR102127436B1/ko active IP Right Grant
- 2017-09-29 EP EP17926340.5A patent/EP3528467B1/en active Active
- 2017-09-29 JP JP2019528883A patent/JP6816281B2/ja active Active
- 2017-09-29 CN CN201780089324.9A patent/CN110476403B/zh active Active
- 2017-09-29 KR KR1020197011388A patent/KR102062298B1/ko active IP Right Grant
-
2019
- 2019-05-09 US US16/407,953 patent/US10686917B2/en active Active
-
2020
- 2020-05-11 US US16/871,872 patent/US11012543B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020078228A1 (en) * | 2000-12-20 | 2002-06-20 | Jussi Kuisma | Arrangement for implementing transmission of multimedia messages |
EP2667625A2 (en) * | 2011-01-19 | 2013-11-27 | Samsung Electronics Co., Ltd | Apparatus and method for transmitting multimedia data in a broadcast system |
KR101626686B1 (ko) * | 2011-10-13 | 2016-06-01 | 삼성전자주식회사 | 방송 시스템에서의 제어 메시지 구성 장치 및 방법 |
US20160285935A1 (en) * | 2015-03-27 | 2016-09-29 | Qualcomm Incorporated | Point-to-multipoint broadcast assisted vehicle-to-x broadcast |
Non-Patent Citations (2)
Title |
---|
ITRI: "Discussion on the MBMS V2V Transmission and Reception", R2-162487, 3GPP TSG RAN2 WG2 MEETING #93BIS, 1 April 2016 (2016-04-01), Dubrovnik, Croatia, XP051082128 * |
See also references of EP3528467A4 * |
Also Published As
Publication number | Publication date |
---|---|
CN110476403A (zh) | 2019-11-19 |
US11012543B2 (en) | 2021-05-18 |
EP3528467A4 (en) | 2020-04-22 |
JP2020511015A (ja) | 2020-04-09 |
US20190268447A1 (en) | 2019-08-29 |
KR102062298B1 (ko) | 2020-02-11 |
CN110476403B (zh) | 2023-02-17 |
EP3528467B1 (en) | 2021-10-27 |
US20200274954A1 (en) | 2020-08-27 |
KR20200001621A (ko) | 2020-01-06 |
KR102127436B1 (ko) | 2020-06-26 |
EP3528467A1 (en) | 2019-08-21 |
US10686917B2 (en) | 2020-06-16 |
JP6816281B2 (ja) | 2021-01-20 |
KR20190052107A (ko) | 2019-05-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019066106A1 (ko) | V2x 통신 장치 및 그의 멀티미디어 컨텐트 전송/수신 방법 | |
WO2019156266A1 (ko) | V2x 통신 장치 및 v2x 통신 장치의 v2x 통신 방법 | |
WO2019132082A1 (ko) | V2x 통신 장치 및 그의 v2x 메시지의 송수신 방법 | |
WO2018174385A1 (ko) | V2x 통신 장치 및 그의 v2x 메시지의 송수신 방법 | |
WO2019160177A1 (ko) | V2x 통신 장치 및 그의 v2x 메시지의 송수신 방법 | |
WO2018128205A1 (ko) | V2x 통신을 위한 장치 및 방법 | |
WO2018182074A1 (ko) | V2x 통신을 위한 장치 및 방법 | |
WO2019240544A1 (en) | Method and apparatus for performing sidelink communication by ue in nr v2x | |
WO2018066876A1 (ko) | 무선 통신 시스템에서 v2x 통신 지원 방법 | |
WO2019240548A1 (en) | Method and apparatus for performing sidelink communication by ue in nr v2x | |
WO2019066108A1 (ko) | V2x 통신을 위한 장치 및 방법 | |
WO2020022526A1 (ko) | V2x 통신 장치 및 지오네트워킹 전송 방법 | |
WO2019240550A1 (en) | Method and apparatus for reporting cast type by ue in nr v2x | |
WO2016003174A1 (ko) | 무선 통신 시스템에서 그룹 메시징 송수신 방법 및 이를 위한 장치 | |
WO2018208062A1 (ko) | 무선 통신 시스템에서의 단말의 접속 식별자 보안 방법 및 이를 위한 장치 | |
WO2020197310A1 (ko) | 사이드링크를 지원하는 무선통신시스템에서 안전 메시지를 전송하는 방법 및 이를 위한 장치 | |
WO2021100938A1 (ko) | 무선 통신 시스템에서 차량, 단말 및 네트워크가 신호를 전송하는 방법 및 이를 위한 차량, 단말 및 네트워크 | |
WO2019004519A1 (ko) | V2x 통신 장치 및 지오네트워킹 전송 방법 | |
WO2019117369A1 (ko) | V2x 통신 장치 및 그의 통신 방법 | |
WO2021100935A1 (ko) | 무선 통신 시스템에서 취약한 도로 사용자의 단말이 신호를 전송하는 방법 | |
WO2019031625A1 (ko) | V2x 통신 장치 및 지오네트워킹 전송 방법 | |
WO2018124320A1 (ko) | V2x 통신을 위한 장치 및 데이터 통신 방법 | |
WO2019117367A1 (ko) | V2x 통신 장치 및 그의 통신 방법 | |
WO2022075769A1 (ko) | 무선 통신 시스템에서 제1 서버가 제2 메시지를 전송하는 방법 및 이를 위한 장치 | |
WO2018128206A1 (ko) | V2x 통신을 위한 장치 및 방법 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref document number: 20197011388 Country of ref document: KR Kind code of ref document: A |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17926340 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2017926340 Country of ref document: EP Effective date: 20190516 |
|
ENP | Entry into the national phase |
Ref document number: 2019528883 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |