[go: up one dir, main page]

WO2019160176A1 - Dispositif de communication v2x et procédé d'émission et de réception de message v2x au moyen de celui-ci - Google Patents

Dispositif de communication v2x et procédé d'émission et de réception de message v2x au moyen de celui-ci Download PDF

Info

Publication number
WO2019160176A1
WO2019160176A1 PCT/KR2018/001944 KR2018001944W WO2019160176A1 WO 2019160176 A1 WO2019160176 A1 WO 2019160176A1 KR 2018001944 W KR2018001944 W KR 2018001944W WO 2019160176 A1 WO2019160176 A1 WO 2019160176A1
Authority
WO
WIPO (PCT)
Prior art keywords
access technology
message
layer
data
ats
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2018/001944
Other languages
English (en)
Korean (ko)
Inventor
양승률
고우석
김진우
백서영
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Priority to PCT/KR2018/001944 priority Critical patent/WO2019160176A1/fr
Publication of WO2019160176A1 publication Critical patent/WO2019160176A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present invention relates to a V2X communication device and a method for transmitting and receiving V2X messages thereof, and more particularly, to a method for transmitting and receiving V2X messages using hybrid communication.
  • V2X Vehicle to Everything
  • V2X communication Various services can be provided through V2X communication.
  • V2X communication may be implemented using various access technologies. However, no clear description of the architecture and operating procedures of the V2X communication device for this hybrid communication is defined.
  • V2X communication device and a V2X communication method of the V2X communication device are disclosed.
  • V2X communication method of a vehicle to everything (V2X) communication apparatus comprises the steps of selecting a target access technology for transmission of V2X messages; Processing the input data into a plurality of message segments; And transmitting V2X messages including each message segment using the target access technology.
  • the step of selecting a target access technology comprises: an access technology selection (ATS) entity obtaining access technology related information from a management entity; And selecting, by the ATS, the target access technology based on the access technology related information, wherein the access technology related information may include available access technology information providing a list of available access technologies.
  • ATS access technology selection
  • the obtaining of the access technology related information may include: forwarding a request primitive to the management entity for which the ATS entity requests the access technology related information; And receiving, by the ATS entity, an acknowledgment primitive including the access technology related information from the management entity.
  • the access technology related information further includes at least one of bandwidth information providing a list of bandwidths associated with the available access technology or CBR information providing a list of channel busy ratios (CBRs) associated with the available access technology. can do.
  • bandwidth information providing a list of bandwidths associated with the available access technology
  • CBR information providing a list of channel busy ratios (CBRs) associated with the available access technology. can do.
  • the access technology related information further includes maximum packet size information providing a list of maximum packet sizes associated with the available access technology
  • processing into the plurality of message segments comprises: the ATS entity; Determining a size of the message segment using the maximum packet size information; And generating the plurality of message segments from the input data based on the determined size of the message segment.
  • the message segment includes a payload having a header and segmented data, wherein the header includes message ID information and segment ID information indicating an order of the message segment;
  • the message ID information of each message segment generated from the input data may be set to the same value.
  • the ATS entity can be an application layer entity, a facility layer entity or a networking and transport layer entity.
  • V2X communication apparatus includes a memory for storing data; A communication unit for transmitting and receiving wireless signals; And a processor controlling the communication unit, the processor selecting a target access technology for transmission of a V2X message; Process the input data into a plurality of message segments; And V2X messages including each message segment using the target access technology.
  • the selecting the target access technology comprises: the access technology selection (ATS) entity obtaining access technology related information from a management entity; And the ATS selecting the target access technology based on the access technology related information, wherein the access technology related information may include available access technology information providing a list of available access technologies.
  • ATS access technology selection
  • obtaining the access technology related information may include: forwarding a request primitive to the management entity for which the ATS entity requests the access technology related information; And the ATS entity receiving an acknowledgment primitive from the management entity that includes the access technology related information.
  • the access technology related information further includes at least one of bandwidth information providing a list of bandwidths associated with the available access technology or CBR information providing a list of channel busy ratios (CBRs) associated with the available access technology. can do.
  • bandwidth information providing a list of bandwidths associated with the available access technology
  • CBR information providing a list of channel busy ratios (CBRs) associated with the available access technology. can do.
  • the access technology related information further includes maximum packet size information providing a list of maximum packet sizes associated with the available access technology
  • processing into the plurality of message segments includes: Determining the size of the message segment using the maximum packet size information; And generating the plurality of message segments from the input data based on the determined size of the message segment.
  • the message segment includes a payload having a header and segmented data, wherein the header includes message ID information and segment ID information indicating an order of the message segment;
  • the message ID information of each message segment generated from the input data may be set to the same value.
  • the ATS entity can be an application layer entity, a facility layer entity or a networking and transport layer entity.
  • a V2X communication device can provide a hybrid communication service.
  • the V2X communication device can efficiently provide hybrid communication.
  • FIG 1 illustrates an intelligent transport system (ITS) according to an embodiment of the present invention.
  • FIG. 2 shows a V2X transmission and reception 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 for performing MCO (Multi-channel Operation) according to an embodiment of the present invention.
  • FIG. 8 illustrates a relationship between user priority of an EDCA and an access category (AC) according to an embodiment of the present invention.
  • FIG. 9 shows a physical layer configuration of a V2X transmission device according to an embodiment of the present invention.
  • FIG. 10 illustrates a network architecture using an 802.11p based access technology in accordance with an embodiment of the present invention.
  • FIG 11 illustrates a network architecture using a side link (LTE-SL) based access technology according to an embodiment of the present invention.
  • LTE-SL side link
  • FIG. 12 illustrates a network architecture using an LTE-UL / DL (Up Link / Down Link) based access technology according to an embodiment of the present invention.
  • FIG. 13 illustrates a network architecture using LTE-UL / DL (Up Link / Down Link) based access technology according to another embodiment of the present invention.
  • FIG. 14 illustrates a network architecture using hybrid access technology in accordance with an embodiment of the present invention.
  • Figure 15 illustrates a network architecture using a hybrid access technology in accordance with another embodiment of the present invention.
  • FIG. 16 illustrates a network architecture using a hybrid access technology in accordance with another embodiment of the present invention.
  • FIG. 17 illustrates a protocol stack of ITS-S for hybrid communication according to an embodiment of the present invention.
  • FIG. 18 illustrates a protocol stack of ITS-S for hybrid communication according to another embodiment of the present invention.
  • FIG. 19 illustrates a protocol stack of an ITS-S for performing an ATS procedure by an application layer according to an embodiment of the present invention.
  • FIG. 20 illustrates a message flow for an ATS procedure by an application layer according to an embodiment of the present invention.
  • 21 illustrates a protocol stack of an ITS-S for performing an ATS procedure by a facility layer according to an embodiment of the present invention.
  • FIG. 22 illustrates a message flow for an ATS procedure by a facility layer according to an embodiment of the present invention.
  • FIG. 23 illustrates a protocol stack of an ITS-S for performing an ATS procedure by a networking / transport layer according to an embodiment of the present invention.
  • FIG. 24 illustrates a message flow for an ATS procedure by a networking / transport layer according to an embodiment of the present invention.
  • 25 illustrates a protocol stack of an ITS-S for performing an ATS procedure by a networking / transport layer according to an embodiment of the present invention.
  • 26 illustrates a message flow for an ATS procedure by a networking / transport layer according to an embodiment of the present invention.
  • FIG. 27 illustrates a message segmentation procedure by an application layer according to an embodiment of the present invention.
  • FIG. 28 illustrates a first embodiment of a structure of a message segment when the message segmentation procedure of FIG. 27 is performed according to an embodiment of the present invention.
  • FIG. 29 illustrates a second embodiment of a structure of a message segment when the message segmentation procedure of FIG. 27 is performed according to an embodiment of the present invention.
  • FIG. 30 illustrates a message segmentation procedure by the facility layer according to an embodiment of the present invention.
  • FIG. 31 illustrates a first embodiment of a structure of a message segment when the message segmentation procedure of FIG. 30 is performed according to an embodiment of the present invention.
  • FIG. 32 illustrates a second embodiment of a structure of a message segment when the message segmentation procedure of FIG. 30 is performed according to an embodiment of the present invention.
  • FIG 33 illustrates a message segmentation procedure by the networking / transport layer according to an embodiment of the present invention.
  • FIG. 34 illustrates a first embodiment of a structure of a message segment when the message segmentation procedure of FIG. 33 is performed according to an embodiment of the present invention.
  • FIG. 35 illustrates a second embodiment of a structure of a message segment when the message segmentation procedure of FIG. 33 is performed according to an embodiment of the present invention.
  • FIG. 36 illustrates a message segmentation procedure by a networking / transport layer according to another embodiment of the present invention.
  • FIG. 37 illustrates a first embodiment of a structure of a message segment when the message segmentation procedure of FIG. 36 is performed according to an embodiment of the present invention.
  • FIG. 38 illustrates a second embodiment of a structure of a message segment when the message segmentation procedure of FIG. 36 is performed according to an embodiment of the present invention.
  • 39 illustrates operations of access technology selection and message segmentation performed at different layers according to an embodiment of the present invention.
  • FIG 40 illustrates operations of access technology selection, DCC, and message segmentation performed in the facility layer according to an embodiment of the present invention.
  • FIG. 41 illustrates operations of access technology selection, DCC, and message segmentation performed in a facility layer according to another embodiment of the present invention.
  • V2X communication device 42 shows a configuration of a V2X communication device according to an embodiment of the present invention.
  • FIG. 43 is a flowchart illustrating a V2X communication method of a V2X communication device according to an embodiment of the present invention.
  • the present invention relates to a V2X communication device, and the V2X communication device may be included in an intelligent transport system (ITS) system to perform all or some functions of the ITS system.
  • the V2X communication device 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 onboard unit (OBU) of the vehicle or may be included in the OBU.
  • OBU On Board Equipment
  • OBU On Board Equipment
  • the V2X device may correspond to a road side unit (RSU) of the infrastructure or may be included in the RSU.
  • the RSU may be referred to as RoadSide Equipment (RSE).
  • the V2X communication device may correspond to or be included in an ITS station. Any OBU, RSU, mobile equipment, etc. that perform V2X communication may all be referred to as ITS stations or V2X communication devices.
  • FIG 1 illustrates an intelligent transport system (ITS) according to an embodiment of the present invention.
  • Intelligent transportation system provides efficient and safe transportation services by applying information and communication technology such as electronic control and communication devices to transportation facilities such as cars, buses and trains, and traffic facilities installed around roads such as traffic lights and billboards. Means to provide a system.
  • Information and communication technology such as electronic control and communication devices
  • transportation facilities such as cars, buses and trains, and traffic facilities installed around roads such as traffic lights and billboards.
  • V2X Vehicle to everything
  • V2X communication technology refers to a communication technology between a vehicle and a vehicle or a vehicle and a peripheral device.
  • Vehicles supporting V2X communication are equipped with OBUs, which include dedicated short-range communication (DSRC) communication modems.
  • Infrastructure that includes a V2X module installed around a road, such as a traffic light, may be referred to as an RSU.
  • VRU Vehicleable Road Users
  • the VRU may be capable of V2X communication.
  • V2V Vehicle to Vehicle
  • V2I Vehicle to Infra-structure
  • V2O communication between the vehicle and the traffic weak
  • I2O communication between the infrastructure and the traffic weak
  • FIG. 2 shows a V2X transmission and reception system according to an embodiment of the present invention.
  • the V2X transmission and reception system is classified according to the role of transmitting and receiving data between the V2X transmitter 2100 and the V2X receiver 2200, and there is no configuration difference between the devices.
  • the V2X transmitter 2100 and the V2X receiver 2200 both 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, and an Application Electronic Control Unit (ECU).
  • GNSS Receiver Global Navigation Satellite System
  • DSRC Radio 2120 a DSRC Radio 2120
  • DSRC device processor 2130 a DSRC device processor 2130
  • ECU Application Electronic Control Unit
  • the ECU 2140 includes a sensor 2150 and a human interface 2160.
  • the DSRC radio 2120 may perform communication based on a wireless local area network (WLAN) -based IEEE 802.11 standard and / or the Wireless Access in Vehicular Environments (WAVE) standard of the Society of Automotive Engineers (SAE). have.
  • the DSRC radio 2120 may 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 decode the message to be transmitted.
  • the GNSS receiver 2110 processes the GNSS and may acquire 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 a service, and send and receive messages using a DSRC device processor.
  • the sensor 2150 may acquire vehicle state and ambient sensor information.
  • the human interface 2160 may receive a user input or display / provide a message through an interface such as an input button or a monitor.
  • the V2X receiver 2200 may include a Global Navigation Satellite System (GNSS Receiver) 2210, a DSRC Radio 2220, a DSRC device processor 2230, and an Application Electronic Control Unit (ECU). ECU 2240, Sensor 2250, and Human Interface 2260. The above description of the configuration of the V2X transmitter 2100 is applied to the configuration 2200 of the V2X receiver.
  • GNSS Receiver Global Navigation Satellite System
  • DSRC Radio 2220 a DSRC Radio 2220
  • ECU Application Electronic Control Unit
  • Sensor 2250 Sensor 2250
  • Human Interface 2260 Human Interface
  • the DSRC radio and the DSRC device processor correspond to one embodiment of a communication unit.
  • the communication unit may communicate based on cellular communication technology such as 3GPP, Long Term Evolution (LTE).
  • 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 as defined in ISO 21217 / EN302 665.
  • 3 shows an example of an ITS station in which the ITS station is based on a reference architecture.
  • 3 illustrates a hierarchical architecture for end-to-end communication.
  • the message is transmitted through each layer down one layer in the transmitting vehicle / ITS system, and the message is transmitted to the upper layer one layer up in the receiving vehicle / ITS system. Description of each layer is as follows.
  • the application layer may 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 end vehicles / users / infrastructures through lower layers.
  • the application can be defined / applied by use-case, or the use-case can be grouped as road-safety, traffic efficiency, local service, infotainment to define / apply It may be.
  • 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 are communicated and shared in both directions through the interface between management entity and application layer (MAMA) and the interface between security entity and ITS-S applications (SA) or Service Access Points (eg MA-SAP, SA-SAP). Can be.
  • MAMA management entity and application layer
  • SA security entity and ITS-S applications
  • SA-SAP Service Access Points
  • the request from the application layer to the facility layer or the transfer of information from the facility layer to the application layer may be performed through an interface between facilities layer and ITS-S applications (FA) (or
  • the facility layer can support the effective realization of the various uses defined in the application layer.
  • the facility layer may perform application support, information support, and session / communication support.
  • the facility layer may natively support the top three layers of the OSI model: session layer, presentation layer, and application layer.
  • the facility layer may additionally provide advanced facilities such as application support, information support, and session / communication support for the ITS system.
  • a facility refers to a component that provides functionality, information, and data.
  • the facility may be classified into a common facility and a domain facility.
  • Common facilities can provide the basic set of applications of ITS and the core services or functions required to operate the ITS station. For example, time management, position management, service management, and the like may be provided.
  • Domain facilities may provide special services or functions to a basic set of applications of one or more ITS.
  • the domain facility may provide decentralized notification messages (DENM) management for Road Hazard Warning applications (RHW).
  • DENM decentralized notification messages
  • RHW Road Hazard Warning applications
  • the network / transport layer can form a network for vehicle communication between homogeneous / heterogenous networks by using various transport protocols and network protocols.
  • the network / transport layer may provide Internet access and routing using Internet protocols such as TCP / UDP + IPv6.
  • the network / transport layer may configure a vehicle network using a geographical position based protocol such as BTP / GeoNetworking.
  • the transport layer corresponds to a connection layer between services provided by upper layers (session layer, presentation layer, application layer) and lower layers (network layer, data link layer, physical layer).
  • the transport layer manages the data sent by the user to arrive at the destination exactly.
  • the transport layer may serve to divide data into packets of a size suitable for transmission for efficient data transmission.
  • the transport layer may serve to reassemble the received packets into the original file.
  • the transport protocol may be TCP / UDP, and a transport protocol for ITS such as VTS may be used.
  • the network layer can assign logical addresses and determine packet forwarding paths.
  • the network layer may receive a packet generated at the transport layer and add a network header including a logical address of a destination.
  • packet path design unicast / broadcast between vehicles, between vehicles and fixed stations, and between fixed stations may be considered.
  • protocols such as geo-networking, with movility support IPv6 networking, IPv6 over geo-networking, and the like may be considered.
  • the access layer may transmit a message / data received from a higher layer through a physical channel.
  • the access layer may include 2G including an IEEE 802.11 and / or 802.11p standard based communication technology, ITS-G5 wireless communication technology based on the physical transmission technology of the IEEE 802.11 and / or 802.11p standard, and satellite / wideband wireless mobile communication. It can perform / support data communication based on / 3G / 4G (LTE) / 5G wireless cellular communication technology, broadband terrestrial digital broadcasting technology such as DVB-T / T2 / ATSC, GPS technology, IEEE 1609 WAVE technology.
  • LTE Long Term Evolution
  • 5G wireless cellular communication technology broadband terrestrial digital broadcasting technology
  • DVB-T / T2 / ATSC GPS technology
  • IEEE 1609 WAVE technology IEEE 1609 WAVE technology.
  • ITS systems for vehicle communication and networking can be organically designed in consideration of various connection technologies, network protocols, and communication interfaces to provide a variety of use-cases.
  • the role and function of each layer may be augmented or augmented.
  • FIG. 4 shows a packet structure of a network / transport layer according to an embodiment of the present invention.
  • the transport layer may generate a BTP packet, and the network layer may generate a geo-networking packet.
  • the geonetworking packet may correspond to data of a logical link control (LLC) packet and may be included in the LLC packet.
  • Geo-networking packets may be encapsulated into LLC packets.
  • the data includes a message set, which 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 type A BTP header may include a destination / destination port and a source port, which are required for transmission and reception for interactive packet transmission.
  • the B type header may include destination port and destination port information, which is required for transmission for non-interactive packet transmission. Descriptions of the fields / information included in the header are as follows.
  • the destination port identifies the facility entity corresponding to the destination of the data (BTP-PDU) included in the BTP packet.
  • Source Port A field generated in the case of a BTP-A type, indicating a port of a protocol entity of a facility layer in a source through which a corresponding packet is transmitted. This field may have a size of 16 bits.
  • This field is generated for the BTP-B type and may provide additional information when the destination port is the best known port. This field may have a size of 16 bits.
  • the geonetworking packet includes a basic header and a common header according to the protocol of the network layer, and optionally includes an extension header according to the geonetworking 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), an LT (LifeTime) field, and a Remaining Hop Limit (RHL) field.
  • the 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 geonetworking protocol.
  • NH Next Header
  • the NH (Next Header) field indicates the type of the next header / field. If the field value is 1, the common header is followed. If the field value is 2, the secured secure packet may be followed.
  • the LT (LifeTime) field indicates the maximum survival time of the packet.
  • RHL 8 bits: The Remaining Hop Limit (RHL) field indicates the remaining hop limit.
  • the RHL field value may be decremented by 1 each time it is forwarded by a GeoAdhoc router. If the RHL field value is 0, the packet is no longer forwarded.
  • the common header can be 64 bits (8 bytes).
  • Common headers include the following fields: NH (NextHeader) field, HT (HeaderType) field, HST (Header Sub-Type) field, TC (Traffic Class) field, Flags field, Payload Length field, PL (Maximum Hop Limit) field It may include at least one of. Description of each field is as follows.
  • the NH (Next Header) field indicates the type of the next header / field.
  • a field value of 0 may indicate an undefined "ANY" type, 1 indicates a BTP-A type packet, 2 indicates a BTP-B type packet, and 3 indicates an IPv6 IP diagram.
  • Geonetworking types include Beacon, GeoUnicast, GeoAnycast, GeoBroadcast, Topologically-Scoped Broadcast, and Location Service (LS).
  • HST (4-bit): The Header Subtype field indicates the detailed type along with the header type.
  • TSB When the HT type is set to TSB, when the HST value is '0', a single hop may be indicated, and when it is '1', a multi hop may be designated.
  • the traffic class field may include a Store-Carry-Forward (SCF), Channel Offload, and TC ID.
  • SCF Store-Carry-Forward
  • the SCF field indicates whether to store a packet when there is no neighbor to deliver the packet.
  • the channel offload field indicates that a packet can be delivered to another channel in case of a multichannel operation.
  • the TC ID field is a value assigned during packet transmission in the facility layer and may be used to set a contention window value in the physical layer.
  • the flag field indicates whether the ITS device is mobile or stationary, and may be the last 1 bit as an embodiment.
  • the Payload Length field indicates the data length following the geonetworking header in bytes.
  • the PL field may indicate the length of the BTP header and the CAM.
  • MHL 8-bit
  • MHL The Maximum Hop Limit (MHL) field may indicate the maximum number of hops.
  • the LLC header is added to the geonetworking packet to generate the LLC packet.
  • the LLC header provides the function of distinguishing IP data and geonetworking data. IP data and geonetworking data can be distinguished by the Ethertype of SNAP. As an embodiment, when IP data is transmitted, the Ethertype may be set to 0x86DD and included in the LLC header. As an embodiment, when geonetworking data is transmitted, the Ethertype may be set to 0x86DC and included in the LLC header.
  • the receiver may check the Ethertype field of the LLC packet header and forward and process the packet to the IP data path or the geonetworking 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 PHY technology and MAC technology of IEEE 802.11, and may further use the MAC technology of IEEE 1609.4.
  • the technology of the IEEE802.2 standard is applied to the LLC block, and the IEEE 1609.3 technology may be applied to the WAVE short message protocol (WSMP).
  • the facility layer can use message sets from SAE's J2735 standard, and the application layer can use applications defined for V2V, V2I, and V2O in the J2945 standard.
  • the application layer may perform a function by implementing a use-case.
  • 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 applications for V2V technology such as V2V safety communications.
  • FCW technology is a V2V safety communication technology that warns of a collision with a preceding vehicle. If a vehicle with a V2X communication device stops suddenly or stops in an accident, it can send an FCW safety message to prevent subsequent vehicle collisions. Subsequent vehicles may receive FCW messages and warn the driver or perform controls such as speed reduction or lane change. In particular, even when there is another vehicle between the stopped vehicle and the driving vehicle, there is an advantage that the state of the stopped vehicle through the FCW.
  • FCW safety messages may include vehicle location information (latitude, longitude, lane), vehicle information (vehicle type, length, direction, speed), event information (stop, sudden stop, slow motion), which may be 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 may generate a set of contextual messages to support the application.
  • the message set is defined in the J2735 standard and can be described / decrypted via ASN.1.
  • the message set may include BasicSafetyMessage message, MapData message, SPAT message, CommonSafetyRequest message, EmergencyVehicleAlert message, IntersectionCollision message, ProbeVehicleData message, RoadSideAlert message, PersonalSafetyMessag message.
  • the facility layer may generate a message set by collecting information to be transmitted from a higher layer.
  • the message set may be indicated in an Abstract Syntax Notation 1 (ASN.1) manner.
  • ASN.1 is a notation used to describe data structures. It can also specify encoding / decoding rules.
  • ASN.1 is not dependent on specific devices, data representations, programming languages, hardware platforms, etc.
  • ASN.1 is a language that describes data regardless of platform. It is a joint standard between the International Committee for Internationalization and Telephony (CITT) (X.208) and the International Organization for Standardization (ISO 8824).
  • a message set is a collection of messages related to V2X operations. There is a message set for the context of the parent application.
  • the message set is represented in the form of a data frame and may include at least one element. Each element may include a data frame or a data element.
  • the data frame represents two or more data sequences.
  • the data frame may be an enumeration structure of data elements or an enumeration structure of data frames.
  • the DV_vehicleData is a data frame structure representing information of a vehicle and may include a plurality of data elements (eg, height, bumbers, mass, trailerweight).
  • the data element defines a description of the data element.
  • an element called Height used in the data frame is defined in DE_VehicleHeight and may represent the height of the vehicle.
  • the height of the vehicle may be expressed from 0 to 127, and the LBS unit may be increased in units of 5 cm and may be expressed up to 6.35 meters.
  • a BasicSafetyMessage may be sent.
  • BasicSafetyMessage is the most basic and important message of the message set and is used to transmit basic information of the vehicle periodically.
  • the message may include coreData defined as BSMcoreData, and optional PartII and regional data.
  • coreData may include data elements such as msgCnt, id, lat, long, elev, speed, deading, break, size, and the like.
  • coreData uses data elements to display message count, ID, latitude, longitude, altitude, speed, direction, brake, vehicle size, and so on.
  • the BSM can generally transmit information corresponding to coreData in a cycle of 100 msec (10 times per second).
  • the network / transport layer may correspond to OSI layer 3 (network layer) and layer 4 (transport layer).
  • a WAVE short message protocol (WSMP) may be used to transmit a WAVE short message (WSM) delivered from an upper layer.
  • WSM WAVE short message
  • the IPv6 / TCP protocol may be used to process conventional IP signals.
  • the LLC block uses the IEEE802.2 standard and can distinguish an IP diagram from a WSM packet.
  • the access layer may correspond to OSI layer 1 (physical layer) and layer 2 (data link layer).
  • the access layer may use the IEEE 802.11 PHY technology and MAC technology, and in addition, the MAC technology of IEEE 1609.4 may be used to support vehicle communication.
  • the security entity and the management entity may be connected and operated in all sections.
  • FIG. 6 shows a WSMP packet configuration according to an embodiment of the present invention.
  • the network / transport layer of FIG. 5 may send a vehicle safety message, such as a BSM, via WSMP.
  • vehicle safety message such as a BSM
  • WSMP vehicle safety message
  • IPv6 and TCP / UDP can also be supported for transporting IP data.
  • the WSMP packet includes WSM data including a WSMP header and 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 an actual WSMP version of 4 bits and a reserved field of 4 bits.
  • the PSID field is a provider service identifier and may be allocated according to an application in a higher layer. The PSID field helps the receiver determine the appropriate higher layer.
  • the extension field is a field for extending the WSMP header and may include information such as a channel number, a data rate, and a transmit power used.
  • the WSMP WAVE Element ID field may specify the type of WAVE short message to be transmitted.
  • the length field may specify the length of the WSM data transmitted in octets transmitted through the 12-bit WSMLemgth field.
  • the LLC header provides the function of distinguishing and transmitting IP data and WSMP data.
  • IP data and WSMP data can be distinguished by Ethertype of SNAP.
  • the LLC header and the SNAP header structure may be defined in a document of IEEE 802.2.
  • the ether type may be set to 0x86DD and included in the LLC header.
  • the Ethertype may be set to 0x86DC and included in the LLC header.
  • the receiver may check the Ethertype field of the LLC packet header and forward and process the packet to the IP data path or WSMP path according to the value.
  • FIG. 7 illustrates a conceptual internal architecture of a MAC sublayer for performing MCO (Multi-channel Operation) according to an embodiment of the present invention.
  • 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 channel access is defined, channel routing defining overall operation of PHY-MAC layers and an operation process of a management frame, and an EDCA (Enhanced) which determines and defines a priority of a transmission frame. Dedicated Channel Access), and a data buffer (or queue) for storing a frame received from a higher layer.
  • the channel coordination block is not shown in FIG. 7, and channel coordination may be performed by the entire MAC sublayer of FIG. 5.
  • Channel Coordination In an embodiment, channel access to a control channel (CCH) and a service channel (SCH) may be controlled. Channel access coordination will be described later.
  • a WSM Wive Short Message
  • CCH control channel
  • SCH service channel
  • WSM Wive Short Message
  • the data buffer may store a data frame received from a higher layer according to a defined access category (AC).
  • AC access category
  • a data buffer may be provided for each AC.
  • the channel routing block can deliver data input from the upper layer to the data buffer.
  • the transmission operation parameters such as channel coordination and channel number, transmission power, and data rate for the frame transmission may be called for the transmission request of the upper layer.
  • EDCA In order to guarantee QoS in the existing IEEE 802.11e MAC layer, it is divided into four access categories (ACs) according to the type of traffic, giving differentiated priority to each category, and assigning different parameters by AC. It is a contention-based medium access method that gives more traffic for priority traffic. For data transmission including priority, the EDCA block can assign 8 priorities from 0-7 and map the data arriving at the MAC layer to 4 ACs according to the priorities.
  • FIG. 8 illustrates a relationship between user priority of an EDCA and an access category (AC) according to an embodiment of the present invention.
  • the relationship between the user priority of the EDCA and the AC is shown in FIG. 8.
  • the ranking has a higher priority as the AC number increases. Every AC has its own transmit queue and AC parameters, and the difference in priority between ACs is determined based on the AC parameter values set differently. Differently set AC parameter values are associated with back-off and have different channel access ranks.
  • the parameter values of the corresponding AC use AIFS [AC], CWmin [AC], and CWmax [AC], respectively, where AIFS (Arbitration Inter-Frame Space) checks whether the channel is idle before proceeding. Say the minimum time for. The smaller the value of AIFS [AC] and CWmin [AC], the higher the priority. Therefore, the shorter the channel access delay, the more bandwidth can be used in a given traffic environment.
  • the transmitter creates a new backoff counter.
  • Four AC-specific transmission queues defined in IEEE 802.11 MAC compete with each other individually for wireless media access within one station. Since each AC has independent backoff counters, virtual collisions can occur. If there is more than one AC that has completed backoff at the same time, the data of the highest priority AC is transmitted first, and the other ACs update the backoff counter again by increasing the CW value. This conflict resolution process is called a virtual conflict process.
  • EDCA also provides access to channels for data transmission through Transmission Opportunity (TXOP). If one frame is too long to transmit all during one TXOP, it may be divided into smaller frames and transmitted.
  • TXOP Transmission Opportunity
  • FIG. 9 shows a physical layer configuration of a V2X transmission device according to an embodiment of the present invention.
  • FIG. 9 shows a physical layer signal processing block diagram 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, a FEC encoder 9020, an interleaver 9030, a mapper 9040, a pilot insertion block 9050, and an IFFT block.
  • PLCP Physical Layer Convergence Protocol
  • PMD Physical Medimu Dependant
  • the scrambler 9010 may randomize the input bit stream by XORing with a pseudo random binary sequence (PRBS).
  • the FEC encoder 9020 may add redundancy to the transmission data so that an error on the transmission channel may be corrected at the receiving side.
  • the interleaver 9030 may interleave the input data / bit string based on the interleaving rule so as to correspond to a burst error. As an embodiment, when deep fading or erasure is applied to a QAM symbol, since interleaved bits are mapped to each QAM symbol, an error occurs in successive bits among all codeword bits. Can be prevented.
  • the mapper 9040 may allocate 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 channel distortion phenomena such as channel estimation, frequency offset, and timing offset.
  • the IFFT block 9060 may convert an input signal to improve transmission efficiency and flexibility in consideration of the characteristics of the transport channel and the system structure.
  • the IFFT block 9060 may convert a signal in the frequency domain into a time domain using an inverse FFT operation.
  • IFFT block 9060 may be unused or omitted for single carrier systems.
  • the guard insertion block 9070 may insert guard intervals between adjacent signal blocks to minimize the influence of the delay spread of the transmission channel.
  • the guard insertion block 9070 may insert a cyclic prefix in the guard interval period.
  • the preamble insertion block 9080 may insert a predetermined type of signal, that is, a preamble, into a transmission signal so that the receiver can detect the target signal quickly and efficiently.
  • the preamble insertion block 9080 may define a signal block / signal frame including a plurality of OFDM symbols and insert a preamble symbol at the beginning of the signal block / signal frame.
  • the wave shaping block 9090 may 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 baseline of out-of-band emission of the transmitted signal.
  • SRRC square-root-raised cosine
  • the waveform shaping block 9090 may be unused or omitted.
  • the I / Q modulator 9100 may perform in-phase and quadrature modulation.
  • the digital to analog converter (DAC) block may convert an input digital signal into an analog signal and output the analog signal. The output analog signal can be transmitted via an output antenna.
  • the V2X communication device may communicate based on the DSRC technique and the WAVE technique described with reference to FIGS. 7 to 9. However, the V2X communication device may perform communication based on other communication technologies including cellular technologies such as LTE, LTE-A, and 5G.
  • V2X communication can be implemented through various access technologies.
  • current V2X communication standards are defined taking into account only one access technology.
  • the access layer of ITS-S is implemented to support only 802.11p based access technology.
  • 802.11p based and LTE based access technologies have their respective advantages, a V2X communication standard for ITS-S that can support both access technologies needs to be considered.
  • FIG. 10 illustrates a network architecture using an 802.11p based access technology in accordance with an embodiment of the present invention.
  • an 802.11p based access technique is used for communication between each hop.
  • the ITS-S may deliver data to all ITS-Ss (ITS # B, #C, etc.) within one hop range through a single hop broadcast (SHB) method.
  • SHB single hop broadcast
  • data is passed from the source ITS-S (sander) to all destination ITS-Ss (destinations) within one hop range.
  • the ITS-S (#A) may transmit data to all ITS-Ss (#B, #C, etc.) within a specific number of hop ranges through a topologically-scoped broadcast (TSB) scheme.
  • TSB topologically-scoped broadcast
  • the TSB scheme is a broadcast scheme that adjusts the distance in which data is delivered by the number of hops. Since only the number of hops determines whether data is delivered, the location address of the destination or local information to which the data is delivered is not used. In this case, data is passed from the source ITS-S (sander) to all destination ITS-Ss (destinations) within a predetermined number of hop ranges.
  • the ITS-S may transfer data to a specific ITS-S (#B) through a GeoUnicast method.
  • Geounicasting is a method of delivering data from a specific source ITS-S to a destination ITS-S.
  • data may be delivered from the source ITS-S to the target ITS-S via multi-hop.
  • the source ITS-S must have information (eg, location information) about the destination ITS-S.
  • the ITS-S (#A) may transmit data to all ITS-Ss (#B, #C, etc.) in a specific region through a geobroadcast scheme.
  • Geobroadcasting is a method of broadcasting data to all ITS-Ss in a particular region. In this case, when the data delivered from the source ITS-S is delivered to a specific destination area (geographic area), the data (packet) is broadcasted within the defined area.
  • the ITS-S (#A) may transmit data to one ITS-S (#B) in a specific region through a GeoAnycast method.
  • the GeoAnycast method is a method of delivering data to one ITS-S that first receives a packet in a specific region. In this case, when data transferred from the source ITS-S is delivered to one ITS-S in a specific destination area (geographic area), it is no longer delivered.
  • LTE-SL side link
  • FIG. 11 illustrates a network architecture using a side link (LTE-SL) based access technology according to an embodiment of the present invention.
  • LTE-SL means an LTE side link using a PC5 interface.
  • FIG. 11 a description overlapping with FIG. 10 will be omitted.
  • the ITS-S may transfer data to all ITS-Ss (#B, #C, etc.) within one hop range through the SHB scheme.
  • the SHB scheme may be referred to as a SHB_LTE_SL scheme.
  • the ITS-S may transmit data to all ITS-Ss (#B, #C, etc.) within a specific number of hop ranges through the TSB scheme.
  • the TSB scheme may be referred to as a TSB_LTE_SL scheme.
  • the ITS-S (#A) may deliver data to a specific ITS-S (#B) through a geounicast scheme.
  • the GeoUnicast scheme may be referred to as a GeoUnicast_LTE_SL scheme.
  • the ITS-S (#A) may transmit data to all ITS-Ss (#B, #C, etc.) in a specific region through a geobroadcasting scheme.
  • the GeoBroadcast scheme may be referred to as a GeoBroadcast_LTE_SL scheme.
  • the ITS-S may deliver data to one ITS-S (ITS # B) in a specific region through a geoanycast scheme.
  • the GeoAnycast scheme may be referred to as a GeoAnycast_LTE_SL scheme.
  • LTE-UL / DL Up Link / Down Link
  • LTE-UL / DL Up Link / Down Link
  • a base station eNB
  • the eNB means an evolved node, and the eNB plays a role of connecting a user equipment (UE) and a mobile network.
  • the UE may be a mobile handset, for example.
  • the eNB is not ITS-S. That is, it is assumed that the RSU is a user equipment (UE) type.
  • the RSU may be a roadside ITS-S.
  • FIG. 12 descriptions duplicated with FIGS. 10 and 11 will be omitted.
  • the ITS-S may transmit data to all ITS-Ss within one hop range through the SHB scheme.
  • the ITS-S (#A) may deliver data to ITS-Ss (#B, #C, etc.) within one hop range via one eNB.
  • data transfer from the ITS-S (#A) to the eNB is performed using the LTE-UL access technology
  • data transfer from the eNB to the ITS-Ss (#B, #C, etc.) is performed using the LTE-DL access technology ( Broadcasting).
  • the SHB scheme may be referred to as a SHB_LTE scheme.
  • the ITS-S may deliver data to a specific ITS-S through a geounicast scheme.
  • the ITS-S (#A) may deliver data to a specific ITS-S (#B) via a plurality of eNBs.
  • data transfer from the eNB adjacent to the ITS-S (#A) to the eNB adjacent to the specific destination may be performed through forwarding through a relay of the backbone network or the eNB.
  • data delivery from eNB to ITS-S (#B) may be performed using LTE-DL access technology (unicasting).
  • the GeoUnicast scheme may be referred to as a GeoUnicast_LTE scheme.
  • the ITS-S may deliver data to all ITS-Ss in a specific region through a geobroadcasting scheme.
  • the ITS-S (#A) may deliver data to ITS-Ss (#B, #C, etc.) in a specific region via a plurality of eNBs.
  • data transfer from the eNB adjacent to the ITS-S (#A) to the eNB adjacent to the specific region may be performed through forwarding through a relay of the backbone network or the eNB.
  • data delivery from the eNB to the ITS-Ss (#B, #C, etc.) may be performed using LTE-DL access technology (broadcasting).
  • the GeoBroadcast scheme may be referred to as a GeoBroadcast_LTE scheme.
  • the ITS-S may deliver data to one ITS-S in a specific region through a geoanycast scheme.
  • the ITS-S (#A) may deliver data to one ITS-S (#B) in a specific region via a plurality of eNBs.
  • data transfer from the eNB adjacent to the ITS-S (#A) to the eNB adjacent to the specific region may be performed through forwarding through a relay of the backbone network or the eNB.
  • data delivery from eNB to ITS-S (#B) may be performed using LTE-DL access technology (unicasting).
  • the GeoAnycast scheme may be referred to as a GeoAnycast_LTE scheme.
  • the ITS-S may deliver data to all ITS-Ss within a specific number of hop ranges through the TSB scheme.
  • the ITS-S (#A) may deliver data to the ITS-S (#B) within a specific hop number range via a plurality of eNBs.
  • data transfer from the eNB adjacent to the ITS-S (#A) to the eNB adjacent to the ITS-S (#B) may be performed through broadcast forwarding through a relay of the backbone network or the eNB.
  • data delivery from the eNB to the ITS-S (#B) may be performed using LTE-DL access technology (broadcasting).
  • the TSB scheme may be referred to as a TSB_LTE scheme.
  • FIG. 13 illustrates a network architecture using LTE-UL / DL (Up Link / Down Link) based access technology according to another embodiment of the present invention.
  • LTE-UL / DL based access technology is used for communication between each hop.
  • a base station eNB
  • ITS-Ss ITS-Ss.
  • RSU roadside ITS-S
  • FIG. 13 descriptions duplicated with FIGS. 10 to 12 will be omitted.
  • the ITS-S may deliver data to all ITS-Ss within one hop range through the SHB scheme.
  • the ITS-S (#A) may deliver data to the ITS-S (eNB type RSU) within one hop range.
  • data transfer from the ITS-S (#A) to the eNB type RSU may be performed using an LTS-UL access technology (broadcasting).
  • the ITS-S (eNB type RSU) may pass data to ITS-Ss (#A, #B, etc.) within one hop range.
  • the SHB scheme may be referred to as a SHB_LTE scheme.
  • the ITS-S may deliver data to a specific ITS-S through a geounicast scheme.
  • the ITS-S (#A) may deliver data to a specific ITS-S (eNB type RSU) via an eNB type RSU.
  • the data transfer from the ITS-S (#A) to the adjacent eNB type RSU is performed using LTE-UL access technology, and the data transfer from the eNB type RSU to the ITS-S (eNB type RSU) is performed in the backbone network or the like. It may be performed through forwarding through the relay of the eNB.
  • the ITS-S may deliver data to a specific ITS-S (#A) via an eNB type RSU.
  • data transfer from the ITS-S (eNB type RSU) to the eNB type RSU adjacent to the ITS-S (#A) may be performed through forwarding through a relay of the backbone network or eNB, and the ITS-S in this eNB type RSU.
  • Data delivery to S (#A) may be performed using LTE-DL access technology (unicast).
  • the GeoUnicast scheme may be referred to as a GeoUnicast_LTE scheme.
  • the ITS-S may deliver data to all ITS-Ss within a specific number of hop ranges through a TSB scheme.
  • the ITS-S (#A) may deliver data to the ITS-S (eNB type RSU) within a specific hop number range via the eNB type RSU.
  • the data transfer from the ITS-S (#A) to the adjacent eNB type RSU is performed using LTE-UL access technology, and the data transfer from the eNB type RSU to the ITS-S (eNB type RSU) is performed in the backbone network or the like. It may be performed through broadcast forwarding through a relay of the eNB.
  • the ITS-S may deliver data to the ITS-S (#A) within a specific hop number range via the eNB type RSU.
  • data transfer from the ITS-S (eNB type RSU) to the eNB type RSU adjacent to the ITS-S (#A) may be performed through forwarding through a relay of the backbone network or eNB, and the ITS-S in this eNB type RSU.
  • Data delivery to S (#A) may be performed using LTE-DL access technology (broadcast).
  • the TSB scheme may be referred to as a TSB_LTE scheme.
  • the ITS-S may deliver data to all ITS-Ss in a specific region through a geobroadcasting scheme.
  • the ITS-S (#A) may deliver data to ITS-Ss (eNB type RSUs) in a specific region via an eNB type RSU.
  • data transfer from the eNB type RSU adjacent to the ITS-S (#A) to the ITS-Ss (eNB type RSUs) in a specific region may be performed through forwarding through a relay of the backbone network or the eNB.
  • the ITS-S may deliver data to the ITS-S (#B, #C, etc.) in a specific region via the eNB type RSU.
  • data transfer from the ITS-S (eNB type RSU) to the eNB type RSU adjacent to the ITS-S (#B, #C, etc.) may be performed through forwarding through a relay of the backbone network or eNB, and this eNB type Data delivery from the RSU to the ITS-S (#B, #C, etc.) may be performed using LTE-DL access technology (broadcast).
  • the GeoBroadcast scheme may be referred to as a GeoBroadcast_LTE scheme.
  • the ITS-S may deliver data to one ITS-S in a specific region through a geoanycast scheme.
  • the ITS-S (#A) may deliver data to one ITS-S (eNB type RSU) in a specific region via an eNB type RSU.
  • data transfer from the eNB type RSU adjacent to the ITS-S (#A) to the ITS-S (eNB type RSU) in a specific region may be performed through forwarding through a relay of the backbone network or the eNB.
  • the ITS-S (eNB type RSU) may deliver data to one ITS-S (#B) in a particular region via an eNB type RSU.
  • ITS-S eNB type RSU
  • eNB type RSU data transfer from the ITS-S (eNB type RSU) to the eNB type RSU adjacent to the ITS-S (#B)
  • data transfer from the ITS-S (eNB type RSU) to the eNB type RSU adjacent to the ITS-S (#B) may be performed through forwarding through a relay of the backbone network or eNB, and the ITS-S in this eNB type RSU.
  • Data delivery to S (#B) may be performed using LTE-DL access technology (unicast).
  • the GeoAnycast scheme may be referred to as a GeoAnycast_LTE scheme.
  • FIG. 14 illustrates a network architecture using hybrid access technology in accordance with an embodiment of the present invention.
  • 802.11p based access technology LTE-SL based access technology, and / or LTE-UL / DL based access technology are used for communication between each hop.
  • the data transfer method through each access technology has been described above with reference to FIGS. 10 to 14.
  • a base station eNB
  • ITS-Ss ITS-Ss
  • RSU user equipment
  • the ITS-S may deliver data to all ITS-Ss within a specific number of hop ranges through a TSB scheme.
  • the ITS-S (#A) may deliver data to the ITS-S (#B, #C, etc.) within a specific hop number range via the eNB.
  • the TSB scheme may be referred to as a TSB_Hybrid scheme.
  • the ITS-S may deliver data to a specific ITS-S through a geounicast scheme.
  • the ITS-S (#A) may deliver data to a specific ITS-S (#B) via the eNB.
  • the GeoUnicast scheme may be referred to as a GeoUnicast_Hybrid scheme.
  • the ITS-S may deliver data to all ITS-Ss in a specific region through a geobroadcasting scheme.
  • the ITS-S (#A) may deliver data to ITS-Ss (#B, #C, etc.) in a specific region via the eNB.
  • the GeoBroadcast scheme may be referred to as a GeoBroadcast_Hybrid scheme.
  • the ITS-S may deliver data to one ITS-S in a specific region through a geoanycast scheme.
  • the ITS-S (#A) may deliver data to one ITS-S (#B) in a specific region via the eNB.
  • the GeoAnycast scheme may be referred to as a GeoAnycast_Hybrid scheme.
  • Figure 15 illustrates a network architecture using a hybrid access technology in accordance with another embodiment of the present invention.
  • 802.11p based access technology LTE-SL based access technology, and / or LTE-UL / DL based access technology are used for communication between each hop.
  • the data transfer method through each access technology has been described above with reference to FIGS. 10 to 13.
  • a base station eNB
  • RSU roadside ITS-S
  • FIG. 15 descriptions duplicated with FIGS. 10 to 14 will be omitted.
  • the ITS-S may deliver data to all ITS-Ss within a specific number of hop ranges through a TSB scheme.
  • the ITS-S (#A) may deliver data to the ITS-S (#B, #C, etc.) within a specific hop number range via the eNB type RSU.
  • the TSB scheme may be referred to as a TSB_Hybrid scheme.
  • the ITS-S may deliver data to a specific ITS-S through a geounicast scheme.
  • the ITS-S (#A) may deliver data to a specific ITS-S (#B) via the eNB type RSU.
  • the GeoUnicast scheme may be referred to as a GeoUnicast_Hybrid scheme.
  • the ITS-S may deliver data to all ITS-Ss in a specific region through a geobroadcasting scheme.
  • the ITS-S (#A) may deliver data to ITS-Ss (#B, #C, etc.) in a specific region via the eNB type RSU.
  • the GeoBroadcast scheme may be referred to as a GeoBroadcast_Hybrid scheme.
  • the ITS-S may deliver data to one ITS-S in a specific region through a geoanycast scheme.
  • the ITS-S (#A) may deliver data to one ITS-S (#B) in a specific region via the eNB type RSU.
  • the GeoAnycast scheme may be referred to as a GeoAnycast_Hybrid scheme.
  • FIG. 16 illustrates a network architecture using a hybrid access technology in accordance with another embodiment of the present invention.
  • any available access technique is used for communication between each hop.
  • the ITS-S may transmit data to all ITS-Ss within one hop range through the SHB scheme.
  • the ITS-S (#A) may pass data to ITS-Ss (#B, #C, etc.) within one hop range.
  • the ITS-S may deliver data to all ITS-Ss within a specific number of hop ranges through the TSB scheme.
  • the ITS-S (#A) may deliver data to the ITS-S (#B, #C, etc.) within a specific hop number range.
  • the ITS-S may deliver data to a specific ITS-S through a geounicast scheme.
  • the ITS-S (#A) may deliver data to a specific ITS-S (#B).
  • the ITS-S may deliver data to all ITS-Ss in a specific region through a geobroadcast method.
  • the ITS-S (#A) may transfer data to ITS-Ss (#B, #C, etc.) in a specific region.
  • the ITS-S may deliver data to one ITS-S in a specific region through a geoanycast scheme.
  • the ITS-S (#A) may transfer data to one ITS-S (#B) in a specific region.
  • FIG. 17 illustrates a protocol stack of ITS-S for hybrid communication according to an embodiment of the present invention.
  • descriptions duplicated with those described above in FIG. 3 will be omitted.
  • the ITS protocol stack of FIG. 17 includes modifications to further use LTE access layer technology.
  • the ITS protocol stack has an adaptation layer for the networking / transport layer. Through this newly defined adaptation layer, ITS-S can select and perform the desired communication method of 802.11p based communication or LTE based communication at the networking / transport layer level.
  • the ITS protocol stack may add entities for LTE-based communication to the networking / transport layer, access layer, management layer, and the like.
  • the description of the newly added entity is as follows.
  • LTE PDCP Packet Data Convergence Protocol
  • LTE RLC Radio Link Control
  • An access layer entity which performs operations for segmentation / concatenation, RLC retransmission, and in-sequence delivery.
  • MAC Medium Access Control
  • LTE PHY Physical Layer: An access layer entity, which performs operations for coding, modulation, multi-antenna processing, and resource mapping.
  • LTE RRC Radio Resource Control
  • a management layer entity which performs operations for establishing and releasing connections, broadcasting system information, establishing, reconfiguring, and releasing radio bearers.
  • FIG. 18 illustrates a protocol stack of ITS-S for hybrid communication according to another embodiment of the present invention.
  • FIG. 18 descriptions duplicated with those described above with reference to FIGS. 3 and 17 will be omitted.
  • the ITS protocol stack of FIG. 18 has an adaptation layer for the access layer.
  • the ITS-S can select and perform a desired communication method of 802.11p based communication or LTE based communication at the access layer level.
  • the ITS protocol stack may add entities to the access layer for LTE-based communication. Each entity is as described above with reference to FIG. 17.
  • the originating ITS-S When using hybrid communication, the originating ITS-S must select the target access technology to be used to transfer data to the other ITS-S.
  • This procedure for selecting a target access technology (hereinafter, referred to as an access technology selection (ATS) procedure) may be performed at one of an application layer, a networking / transport layer, or a facility layer of the originating ITS-S.
  • the ATS procedure may be performed by an ATS module / entity included in one of an application layer, a networking / transport layer, or a facility layer.
  • the originating ITS-S must first check the available access technology.
  • the ATS module may obtain information about available access technologies (eg, a list of available access technologies) from the management layer through a service access point (SAP).
  • SAP service access point
  • the ATS module may request available access technology information from an Access Technology Manager (ATM) module / entity in the management layer and receive available access technology information from the ATM module.
  • ATM Access Technology Manager
  • the ATS module can then select one access technology using this available access technology information.
  • Information about the selected access technology may be delivered to the lower layer. Through this, data may be transmitted using the corresponding access technology.
  • ATM Access Technology Manager
  • FIG. 19 illustrates a protocol stack of an ITS-S for performing an ATS procedure by an application layer according to an embodiment of the present invention.
  • 20 illustrates a message flow for an ATS procedure by an application layer according to an embodiment of the present invention.
  • FIG. 19 a description overlapping with the description above with reference to FIGS. 3, 17, and 18 will be omitted.
  • an application layer of the ITS-S may include an ATS module / entity, and the management layer may further include an ATM module / entity. Description of each module is as follows.
  • Access Technology Selection (ATS) module A module for selecting an access technology.
  • Access Technology Manager (ATM) module A module that stores a list of currently available access technologies and the characteristics of each access technology, and provides this list and properties when requested by another layer or entity through SAP.
  • the application layer may include an ATS module.
  • the ATS module may be included in a hybrid application for hybrid communication.
  • the ATS module may request access technology related information from the ATM module of the management layer through the MA-SAP and receive this access technology related information from the ATM module through the MA-SAP.
  • the ATS module may request access technology related information from the ATM module through the extended MA (SAP) -SAP and receive the access technology related information from the ATM module through the extended MA-SAP.
  • Table 1 is an example of an extended MA-SAP for ATS.
  • the extension of the MA-SAP may include an ATM request primitive (ATM-REQUEST.request) and an ATM request confirmation primitive (ATM-REQUEST.confirm).
  • the ATM request primitive may include an ATM Request Number (ATM-Request.No) field.
  • the ATM request confirmation primitive may include an ATM request confirmation number (ATM-ReqConfirm.No) field and an ATM request confirmation value (ATM-ReqConfirm.Value) field.
  • ATM request primitive A primitive that requests the value of a specific ATM Request (ATS-REQUEST) field from the application layer to the management layer.
  • ATM request primitives may be used by an ATS entity to request access technology related information from an ATM entity. In this case, the access technology related information may be provided through an ATS request field.
  • an ATM request primitive may be abbreviated as a request primitive.
  • ATM Request Number field Contains a field number indicating the ATM request field being requested.
  • ATM request confirmation primitive A primitive that returns the value of the ATM request field requested from the management layer to the application layer.
  • the ATM request confirmation primitive may be used to convey / return the access technology related information requested by the ATM entity to the ATS entity.
  • an ATM request confirmation primitive may be abbreviated as an confirmation primitive.
  • ATM Request Confirmation Number field A field number indicating the ATM request field returned.
  • ATM Request Confirmation Value field Contains the value of the returned ATM request field.
  • ATM request field Contains the set of data returned by the request in the management layer.
  • the ATM request field can be used to provide access technology related information.
  • each data field in the ATM request field may be assigned a number (field number), a name (field name) and a description, for example.
  • Table 2 shows an example of an ATM request field.
  • the ATM request field may be an available access description field that provides a list of current available access technologies for the originating ITS-S.
  • the ATM request field may be a bandwidth field that provides a list of bandwidths associated with the available access technology.
  • the ATM request field may be a CBR field that provides a list of channel busyratios (CBRs) associated with the available access technology.
  • the ATS module can pass an ATM request primitive to the ATM module requesting access technology related information through the extended MA-SAP.
  • the ATM module may forward an ATM request confirmation primitive to the ATS module that includes access technology related information through the extended MA-SAP.
  • the access technology related information may include a list of currently available access technologies, a list of bandwidths associated with the available access technologies, and / or a list of CBRs associated with the available access technologies.
  • the ATM module may select / determine the access technology based on the access technology related information. For example, the ATM module may select one access technology from the list of currently available access technologies. At this point, the ATM module may select one access technology based on the bandwidth associated with the available access technology and / or the value of the CBR associated with the available access technology.
  • the ATS module may deliver information on the selected access technology to the facility layer through a facility application (FA) -SAP.
  • FA facility application
  • the ATS module may deliver information about the selected access technology along with data of the application layer to the ATM module through the extended FA-SAP.
  • Table 3 is an example of an extended FA-SAP for ATS.
  • the extension of the FA-SAP may include a facility data request primitive (FACILITIES-DATA.request).
  • the facility data request primitive may include an Access Technology Profile field, a Length field, and a Data field.
  • Facility data request primitive A primitive that requests data transfer from the application layer to the facility layer.
  • Access technology profile field The target access technology that you want data to be transferred to. That is, the access description profile field may indicate an access technology to which data or a message is to be transmitted. This may follow the definitions in Tables 4 and 5 below.
  • Length field Indicate the length of the following data field.
  • Data field Contains data requesting transmission from the application layer to the facility layer.
  • Tables 4 and 5 are examples of access description profile fields.
  • the access description profile field may have a string value directly indicating the access description.
  • the access technology profile field may indicate the access technology by a predetermined numeric value. Examples of access technologies may include 802.11p, 3G, 4G, 5G, legacy LTE and / or LTE-SL.
  • the facility layer may deliver information on the access technology selected as the networking / transport layer through the Network & Trasnport Facility (NF) -SAP.
  • the facility layer may convey information about the selected access technology along with the data of the facility layer to the networking / transport layer through the extended NF-SAP.
  • the facility layer conveys the information of the facility layer's data and the selected access technology to the BTP entity via the extended BTP-SAP, and the BTP entity's data and selected information to the geonetworking entity via the extended GN-SAP. It can convey information about access technologies.
  • the extension of the NF-SAP will be described.
  • Table 6 is an example of an extended BTP-SAP for ATS.
  • BTP-DATA.request ⁇ BTP type, Source port, Destination port Destination port info GN Packet transport type GN Destination address GN Communication profile GN Access Technology profile GN Security profile GN Maximum packet lifetime GN Repetition interval GN Maximum repetition time GN Maximum hop limit GN Traffic class Length, Data, ⁇
  • the extension of the FA-SAP may include a BTP data request primitive (BTP-DATA.request).
  • BTP-DATA.request a BTP data request primitive
  • the BTP data request primitive may include fields such as the GN Access Technology Profile field.
  • BTP data request primitive A primitive that requests data transfer from the facility layer to BTP.
  • BTP type indicates the type of BTP. For example, to distinguish between interactive (BTP-A) or non-interactive (BTP-B).
  • Source port Indicates the BTP port for sending data.
  • Destination port Indicate the BTP port for receiving data.
  • Destination port info Provides additional information when the destination port is a well-known port.
  • GN Packet transport type indicates the transport type of the GN packet. Used to distinguish the packet transport type.
  • the packet transmission type may include, for example, GeoUnicast, SHB, TSB, and the like.
  • GN Destination address Indicates the geonetworking address of the destination.
  • GN Communication profile used to distinguish whether it is ITS-G5.
  • GN Access Technology profile field to indicate the selected access technology. Has the same value as the Access Technology Profile field in FA-SAP.
  • GN Security profile Indicate the security service profile / level to apply.
  • Maximum packet lifetime Indicates the maximum time to keep a packet before reaching its destination.
  • GN Repetition interval indicates the repetition interval of the packet.
  • GN Maximum hop limit indicates the maximum allowed hop number of the packet.
  • GN Traffic class Indicate the traffic class of a packet.
  • Length indicates the size of the Data field.
  • Data A field containing data requesting transmission from the facility ray to the BTP.
  • Table 7 is an example of an extended GN-SAP for ATS.
  • GN-DATA.request ⁇ Upper protocol entity, Packet transport type, Destination address Communication profile Access Technology profile Security profile ITS-AID length ITS-AID Security permissions length Security permissions Security context information Security target ID list length Security target ID list Maximum packet lifetime Repetition interval Maximum repetition time Maximum hop limit Traffic class Length Data, ⁇
  • the extension of the GN-SAP may include a GN data request primitive (GN-DATA.request).
  • the GN data request primitive may include fields such as an Access Technology Profile field. Each will be described as follows.
  • Upper protocol entity indicates the upper protocol. Used to distinguish higher protocols. For example, distinguish whether the upper protocol is BTP or GN6ASL.
  • Packet transport type indicates the transport type of the GN packet. Used to distinguish the packet transport type.
  • the packet transmission type may include, for example, GeoUnicast, SHB, TSB, and the like.
  • Destination address indicates the geonetworking address of the destination.
  • Access Technology profile Field indicating the selected access technology. Has the same value as the Access Technology Profile field and the GN Access Technology Profile field of the FA-SAP.
  • Security profile Indicate the security service profile / level to apply.
  • ITS-AID length Indicates the length of the value of the ITS-AID field.
  • ITS-AID indicates the ID of the application to which data is ultimately delivered.
  • Security permissions length Indicates the length of the value of the Security permissions field.
  • SSPs Service Specific Permissions
  • Security context information Provides information for selecting security protocol properties.
  • Security target ID list length Indicates the length of the value of the Security target ID list field.
  • Security target ID list Provides a list of target IDs used by security entities.
  • Maximum packet lifetime Indicate the maximum time to keep a packet before reaching its destination.
  • Repetition interval indicates the repetition interval of the packet.
  • Maximumrepetition time Indicates the total time that the packet will be sent repeatedly.
  • Maximum hop limit Indicates the maximum number of hops allowed in the packet.
  • Traffic class Indicate the traffic class of the packet.
  • Length indicates the size of the Data field.
  • Data Data that requests transmission from the BTP to the geonetworking layer.
  • the networking / transport layer may pass data to the access layer for the selected access technology via IN-SAP.
  • the geonetworking layer can deliver data to access layer #B via NF-SAP.
  • FIGS. 21 and 22 illustrates a protocol stack of an ITS-S for performing an ATS procedure by a facility layer according to an embodiment of the present invention.
  • 22 illustrates a message flow for an ATS procedure by a facility layer according to an embodiment of the present invention.
  • FIGS. 21 and 22 descriptions duplicated with those described above with reference to FIGS. 3, 17, 18, 19, and 20 are omitted.
  • the facility layer of the ITS-S may include an ATS module / entity, and the management layer may further include an ATM module / entity. Description of each module is as described above.
  • the facility layer may include an ATS module.
  • the application layer may transfer data of the application layer to the facility layer through FA-SAP.
  • the hybrid application of the application layer may deliver data of the hybrid application to the ATS module of the facility layer through FA-SAP.
  • the ATS module may request access technology related information from the ATM module of the management layer through the MF-SAP and receive this access technology related information from the ATM module through the MF-SAP.
  • the ATS module may request access technology related information from the ATM module via the extended MF-SAP and receive this access technology related information from the ATM module through the extended MF-SAP.
  • the extended MF-SAP for ATS may include the same primitives and fields as the extended MA-SAP described above in Table 1.
  • the extension of the MF-SAP may include an ATM request primitive (ATM-REQUEST.request) and an ATM request confirmation primitive (ATM-REQUEST.confirm).
  • the ATM request primitive may include an ATM Request Number (ATM-Request.No) field.
  • the ATM request confirmation primitive may include an ATM request confirmation number (ATM-ReqConfirm.No) field and an ATM request confirmation value (ATM-ReqConfirm.Value) field. Description of each is as described above.
  • the exemplary ATS procedure using this extended MF-SAP is the same as the exemplary ATS procedure using the extended MA-SAP described above.
  • the ATS module may deliver information on the selected access technology to the networking / transport layer through NF (Network & Trasnport Facility) -SAP.
  • NF Network & Trasnport Facility
  • the ATS module may communicate information about the selected access technology with the facility layer's data to the networking / transport layer via the extended NF-SAP.
  • the facility layer conveys the information of the facility layer's data and the selected access technology to the BTP entity via the extended BTP-SAP, and the BTP entity's data and selected information to the geonetworking entity via the extended GN-SAP. It can convey information about access technologies.
  • the above is an extension of the NF-SAP and GN-SAP.
  • the extended BTP-SAP may include a BTP data request primitive (BTP-DATA.request), and the BTP data request primitive may include a GN Access Technology Profile field.
  • This GN access description profile field is a field indicating the selected access description, and follows the definitions of Tables 4 and 5 described above.
  • the extended GN-SAP may include a GN data request primitive (GN-DATA.request), and the GN data request primitive may include fields such as an access technology profile field.
  • This access description profile field is a field indicating a selected access description and has the same value as the GN access description profile field.
  • the networking / transport layer may pass data to the access layer for the selected access technology via IN-SAP.
  • the geonetworking layer can deliver data to access layer #B via NF-SAP.
  • 23 illustrates a protocol stack of an ITS-S for performing an ATS procedure by a networking / transport layer according to an embodiment of the present invention.
  • 24 illustrates a message flow for an ATS procedure by a networking / transport layer according to an embodiment of the present invention.
  • 23 and 24 assume that the ATS module is included in the BTP of the networking / transport layer. In FIGS. 23 and 24, descriptions duplicated with those described above with reference to FIGS. 3 and 17 through 22 will be omitted.
  • the BTP of the networking / transport layer of the ITS-S may include an ATS module / entity, and the management layer may further include an ATM module / entity. Description of each module is as described above.
  • the application layer may transfer data of the application layer to the facility layer through FA-SAP.
  • the hybrid application of the application layer may deliver data of the hybrid application to the ATS module of the facility layer through FA-SAP.
  • the facility layer may transfer the data of the facility layer to the networking / transport layer through the NF-SAP.
  • the facility layer may transfer data of the facility layer to the ATS module of the BTP through the NF-SAP (BTP-SAP).
  • the ATS module may request access technology related information from the ATM module of the management layer through the MN-SAP, and receive the access technology related information from the ATM module through the MN-SAP.
  • the ATS module may request access technology related information from the ATM module via the extended MN-SAP and receive this access technology related information from the ATM module through the extended MN-SAP.
  • the MN-SAP extended for ATS may include the same primitives and fields as the extended MA-SAP described above in Table 1.
  • the extension of the MF-SAP may include an ATM request primitive (ATM-REQUEST.request) and an ATM request confirmation primitive (ATM-REQUEST.confirm).
  • the ATM request primitive may include an ATM Request Number (ATM-Request.No) field.
  • the ATM request confirmation primitive may include an ATM request confirmation number (ATM-ReqConfirm.No) field and an ATM request confirmation value (ATM-ReqConfirm.Value) field. Description of each is as described above.
  • the exemplary ATS procedure using this extended MN-SAP is the same as the exemplary ATS procedure using the extended MA-SAP described above.
  • the ATS module can communicate the data of the BTP entity and the information about the selected access technology to the geonetworking entity through the extended GN-SAP.
  • the expansion of the GN-SAP is as described above.
  • the extended GN-SAP may include a GN data request primitive (GN-DATA.request), and the GN data request primitive may include fields such as an access technology profile field.
  • This access description profile field is a field indicating the selected access description, and follows the definitions of Tables 4 and 5 described above.
  • the networking / transport layer may pass data to the access layer for the selected access technology via IN-SAP.
  • the geonetworking layer can deliver data to access layer #B via NF-SAP.
  • 25 illustrates a protocol stack of an ITS-S for performing an ATS procedure by a networking / transport layer according to an embodiment of the present invention.
  • 26 illustrates a message flow for an ATS procedure by a networking / transport layer according to an embodiment of the present invention. 25 and 26 assume that the ATS module is included in the geonetworking entity / layer of the networking / transport layer. In FIGS. 25 and 26, descriptions duplicated with those described above with reference to FIGS. 3 and 17 through 24 will be omitted.
  • the geonetworking layer of the networking / transport layer of the ITS-S may include an ATS module / entity, and the management layer may further include an ATM module / entity. Description of each module is as described above.
  • the application layer may transfer data of the application layer to the facility layer through FA-SAP.
  • the hybrid application of the application layer may deliver data of the hybrid application to the ATS module of the facility layer through FA-SAP.
  • the facility layer may transfer the data of the facility layer to the networking / transport layer through the NF-SAP.
  • the facility layer may transfer data of the facility layer to the BTP through NF-SAP (BTP-SAP), and the BTP may transfer data of the BTP through NF-SAP (GN-SAP) to the ATS of the geonetworking layer. You can pass it to the module.
  • the ATS module may request access technology related information from the ATM module of the management layer through the MN-SAP, and receive the access technology related information from the ATM module through the MN-SAP.
  • the ATS module may request access technology related information from the ATM module via the extended MN-SAP and receive this access technology related information from the ATM module through the extended MN-SAP.
  • the MN-SAP extended for ATS may include the same primitives and fields as the extended MA-SAP described above in Table 1.
  • the extension of the MF-SAP may include an ATM request primitive (ATM-REQUEST.request) and an ATM request confirmation primitive (ATM-REQUEST.confirm).
  • the ATM request primitive may include an ATM Request Number (ATM-Request.No) field.
  • the ATM request confirmation primitive may include an ATM request confirmation number (ATM-ReqConfirm.No) field and an ATM request confirmation value (ATM-ReqConfirm.Value) field. Description of each is as described above.
  • the exemplary ATS procedure using this extended MN-SAP is the same as the exemplary ATS procedure using the extended MA-SAP described above.
  • the ATS module can deliver data to the access layer for the selected access technology through IN-SAP.
  • the geonetworking layer can deliver data to access layer #B via NF-SAP.
  • message segmentation may be performed along with the access technology selection.
  • various embodiments of the message segmentation procedure will be described.
  • FIG. 27 illustrates a message segmentation procedure by an application layer according to an embodiment of the present invention.
  • descriptions duplicated with those described above with reference to FIGS. 19 and 20 will be omitted.
  • the application layer may perform an ATS procedure.
  • the application layer may perform a message segmentation procedure along with an ATS procedure.
  • the ATS procedure and the message segmentation procedure may be performed by the ATS module of the application layer.
  • the ATS module can use the MA-SAP extension.
  • the extension of the MA-SAP may include an ATM request primitive (ATM-REQUEST.request) and an ATM request confirmation primitive (ATM-REQUEST.confirm).
  • the ATM request primitive may include an ATM Request Number (ATM-Request.No) field.
  • the ATM request confirmation primitive may include an ATM request confirmation number (ATM-ReqConfirm.No) field and an ATM request confirmation value (ATM-ReqConfirm.Value) field.
  • ATM-REQUEST.request ATM Request Number
  • ATM request confirmation primitive may include an ATM request confirmation number (ATM-ReqConfirm.No) field and an ATM request confirmation value (ATM-ReqConfirm.Value) field.
  • Table 8 shows another example of an ATM request field.
  • the ATM request field may further include a maximum packet size (MPS_acc) field.
  • the Maximum Packet Size field may provide a list of maximum packet sizes associated with available access technologies. As an embodiment, the field number of this maximum packet size field may be "4".
  • the ATM module may determine the size of the message segment transmitted from the application layer to the lower layer based on the information in the maximum packet size field as follows.
  • -MPS_app MPS_acc-Maximum access layer header size-Maximum GeoNetworking header size-Maximum BTP header size-Maximum facilities layer header size
  • MPS_app maximum packet size of the application layer
  • MPS_acc maximum packet size of access retrieved through MA-SAP
  • Each message segment thus generated can be delivered up to the access layer for the selected access technology. As described above with reference to FIG. 20, detailed description thereof will be omitted.
  • FIG. 28 illustrates a first embodiment of a structure of a message segment when the message segmentation procedure of FIG. 27 is performed according to an embodiment of the present invention.
  • FIG. 29 illustrates a second embodiment of a structure of a message segment when the message segmentation procedure of FIG. 27 is performed according to an embodiment of the present invention.
  • application data may be segmented into N message segments.
  • each message segment may include an application header and an application payload.
  • the application payload may comprise an application data segment.
  • the application header may include a message ID field, a segment ID field, and / or an application header part. Each field is described as follows.
  • Message ID field A field that identifies the message that belonged before the message segment was segmented.
  • the message ID field of message segments segmented from one message may be set to the same value.
  • the receiving ITS-S may use this message ID field to merge message segments having the same message ID.
  • Segment ID field A field that indicates the order of the message segment.
  • the receiving ITS-S may use this message ID field and the segment ID field to merge message segments having the same message ID in order.
  • Application header part A part containing the fields of the remaining application headers except for the message ID field and the segment ID field. In the embodiment of FIG. 28, all application header parts are included in each message segment. In the embodiment of FIG. 29, the application header part may be included only in the first message segment. This can reduce the size of the remaining message segments. In this case, the receiving ITS-S may restore the remaining message segments using the application header part included in the first message segment.
  • FIG. 30 illustrates a message segmentation procedure by the facility layer according to an embodiment of the present invention.
  • FIG. 30 descriptions overlapping with those described above with reference to FIGS. 21 and 22 will be omitted.
  • the facility layer may perform an ATS procedure.
  • the facility layer may perform a message segmentation procedure along with an ATS procedure.
  • the ATS procedure and the message segmentation procedure may be performed by the ATS module of the facility layer.
  • the ATS module can use the MF-SAP extension.
  • the extension of the MF-SAP may include the same primitives and fields as the above-described MA-SAP.
  • the ATM request field may be extended as shown in Table 8 for the message segmentation.
  • the ATM module may determine the size of the message segment transmitted from the application layer to the lower layer based on the information in the maximum packet size field as follows.
  • -MPS_fac MPS_acc-Maximum access layer header size-Maximum GeoNetworking header size-Maximum BTP header size
  • MPS_fac maximum packet size of the facility layer
  • MPS_acc maximum packet size of access retrieved through MF-SAP
  • Each message segment thus generated can be delivered up to the access layer for the selected access technology. As described above with reference to FIG. 22, detailed description thereof will be omitted.
  • FIG. 31 illustrates a first embodiment of a structure of a message segment when the message segmentation procedure of FIG. 30 is performed according to an embodiment of the present invention.
  • 32 illustrates a second embodiment of a structure of a message segment when the message segmentation procedure of FIG. 30 is performed according to an embodiment of the present invention.
  • the facility data may be segmented into N message segments.
  • each message segment may include a facility header and a facility payload.
  • the facility payload may comprise a facility data segment.
  • the facility header may include a message ID field, a segment ID field, and / or an application header part. Each field is as described above with reference to FIGS. 28 and 29.
  • FIG. 33 illustrates a message segmentation procedure by the networking / transport layer according to an embodiment of the present invention.
  • descriptions duplicated with those described above with reference to FIGS. 23 and 24 will be omitted.
  • the networking / transport layer may perform an ATS procedure.
  • the networking / transport layer may perform a message segmentation procedure along with an ATS procedure.
  • the ATS procedure and message segmentation procedure may be performed by an ATS module included in the BTP of the networking / transport layer.
  • the ATS module can use the MN-SAP extension.
  • the extension of the MN-SAP may include the same primitives and fields as the above-described MA-SAP.
  • the ATM request field may be extended as shown in Table 8 for the message segmentation.
  • the ATM module may determine the size of the message segment transmitted from the application layer to the lower layer based on the information in the maximum packet size field as follows.
  • MPS_btp maximum packet size of the BTP layer
  • MPS_acc maximum packet size of access retrieved through MF-SAP
  • Each message segment thus generated can be delivered up to the access layer for the selected access technology. As described above with reference to FIG. 24, detailed description thereof will be omitted.
  • FIG. 34 illustrates a first embodiment of a structure of a message segment when the message segmentation procedure of FIG. 33 is performed according to an embodiment of the present invention.
  • FIG. 35 illustrates a second embodiment of a structure of a message segment when the message segmentation procedure of FIG. 33 is performed according to an embodiment of the present invention.
  • BTP data may be segmented into N message segments.
  • each message segment may include a BTP header and a BTP payload.
  • the BTP payload may comprise a BTP data segment.
  • the BTP header may include a message ID field, a segment ID field, and / or an application header part. Each field is as described above with reference to FIGS. 28 and 29.
  • FIG. 36 illustrates a message segmentation procedure by a networking / transport layer according to another embodiment of the present invention.
  • FIG. 36 descriptions duplicated with those described above with reference to FIGS. 25 and 26 will be omitted.
  • the networking / transport layer may perform an ATS procedure.
  • the networking / transport layer may perform a message segmentation procedure along with an ATS procedure.
  • the ATS procedure and the message segmentation procedure may be performed by an ATS module included in the geonetworking layer of the networking / transport layer.
  • the ATS module can use the MN-SAP extension.
  • the extension of the MN-SAP may include the same primitives and fields as the above-described MA-SAP.
  • the ATM request field may be extended as shown in Table 8 for the message segmentation.
  • the ATM module may determine the size of the message segment transmitted from the application layer to the lower layer based on the information in the maximum packet size field as follows.
  • MPS_gn The maximum packet size of the geonetworking (GN) layer.
  • MPS_acc maximum packet size of access retrieved through MF-SAP
  • Each message segment thus generated can be delivered up to the access layer for the selected access technology. As described above with reference to FIG. 26, detailed description thereof will be omitted.
  • FIG. 37 illustrates a first embodiment of a structure of a message segment when the message segmentation procedure of FIG. 36 is performed according to an embodiment of the present invention.
  • FIG. 38 illustrates a second embodiment of a structure of a message segment when the message segmentation procedure of FIG. 36 is performed according to an embodiment of the present invention.
  • geonetworking data may be segmented into N message segments.
  • each message segment may include a geonetworking header and a geonetworking payload.
  • the geonetworking payload may comprise a geonetworking data segment.
  • the geonetworking header may include a Message ID field, a Segment ID field, and / or an application header part. Each field is as described above with reference to FIGS. 28 and 29.
  • the size of each segment can be determined in the following manner.
  • FIG. 39 illustrates operations of access technology selection and message segmentation performed at different layers according to an embodiment of the present invention.
  • a description overlapping with the above description will be omitted.
  • access technology selection and message segmentation are performed in one same layer.
  • access technology selection and message segmentation may be performed at different layers.
  • access technology selection may be performed at the facility layer and mesh segmentation may be performed at the geonetworking layer.
  • each of the facility layer and the geonetworking layer may include an ATS module for access technology selection and message segmentation.
  • the facility layer may include a module for selecting an access technology only
  • the geonetworking layer may include a module for only message segmentation.
  • the ITS-S may perform a distributed congestion control (DCC) function in consideration of channel congestion of the ITS system. Accordingly, the packet (message) size can be adjusted.
  • DCC distributed congestion control
  • FIG. 40 illustrates operations of access technology selection, DCC, and message segmentation performed in the facility layer according to an embodiment of the present invention.
  • FIG. 40 descriptions duplicated with those described above with reference to FIGS. 21, 22, and 30 will be omitted.
  • the facility layer of the ITS-S may include an ATS module and a DCC module
  • the management layer may include an ATM module.
  • the hybrid application of the application layer may deliver the hybrid application data to the ATS module of the facility layer through FA-SAP.
  • the ATS module can obtain information on the available access technology and the maximum packet size from the ATM module through the MF-SAP extension.
  • the MF-SAP extension may include the same primitives and fields as the above-described MA-SAP.
  • the MF-SAP extension may include an ATM request primitive and an ATM request confirmation primitive.
  • the ATM request field may be as shown in Table 8 above. This allows the ATS module to obtain a list of available access technologies and a list of maximum packet sizes (MPS_acc) associated with the available access technologies from the ATM module.
  • the ATS module may determine the maximum packet size (MPS_fac) of the target access technology and the facility layer based on the list of this available access technology and the list of the maximum packet size.
  • the DCC module may obtain congestion measurement information from the ATM module.
  • the DCC module may request congestion measurement information from the ATM module and receive congestion measurement information from the ATM module.
  • This congestion measurement information may provide information about channel congestion of the ITS system, for example, CBR information.
  • the DCC module may determine the congestion level based on the congestion measurement information. In addition, the DCC module may determine the maximum packet size (MPS_acc_dcc) associated with the DCC based on the congestion level.
  • MPS_acc_dcc maximum packet size associated with the DCC based on the congestion level.
  • Table 9 is an example of a table indicating MPS_acc_dcc according to the congestion level.
  • the value of MPS_acc_dcc may have a predetermined value according to the range of channel load (congestion degree) (option # 1). For example, if the channel load is ⁇ 30% (Relaxed), MPS_acc_dcc is 1500 octets; if the channel load is 30-39% (Active 1), MPS_acc_dcc is 1200 octets, and the channel load is 40-49%.
  • MPS_acc_dcc is 900 octets, if the channel load is 50-60% (Active 3 state), MPS_acc_dcc is 600 octets, and if the channel load is> 60% (Restricive state), MPS_acc_dcc is 300 octets. That is, MPS_acc_dcc may have a predetermined value according to each state regardless of MPS_acc.
  • the value of MPS_acc_dcc may have a value associated with a predetermined MPS_acc according to a range of channel load (congestion degree) (option # 2). For example, if the channel load is ⁇ 30% (Relaxed), MPS_acc_dcc is MPS_acc, if the channel load is 30-39% (Active 1 state), MPS_acc_dcc is MPS_acc * 0.8, and the channel load is 40-49%.
  • MPS_acc_dcc is MPS_acc * 0.6
  • channel load is 50 ⁇ 60%
  • MPS_acc_dcc is MPS_acc * 0.4
  • channel load is> 60%
  • MPS_acc_dcc is MPS_acc * 0.2. That is, MPS_acc_dcc may have a value associated with MPS_acc.
  • the ATS module and / or the DCC module may determine the size of the message segment transmitted from the facility layer to the lower layer by using MPS_acc and MPS_acc_dcc as follows.
  • the ATS module and / or the DCC module may perform message segmentation at the facility layer based on this message segment size.
  • the packet size (message segment size) decreases as the congestion increases, it may be helpful to solve the channel congestion.
  • the number of delivered messages (message segments) also increases.
  • the idle time of not transmitting a message according to the DCC mechanism also increases.
  • the increased number of messages does not directly affect congestion.
  • the packet size may be adjusted in consideration of channel congestion caused by the geonetworking scheme. That is, the size of the message may be adjusted in consideration of the congestion caused by the packet transmission type to be applied in the geonetworking layer.
  • FIG. 41 illustrates operations of access technology selection, DCC, and message segmentation performed in a facility layer according to another embodiment of the present invention.
  • FIG. 41 descriptions duplicated with those described above with reference to FIGS. 21, 22, 30, and 40 are omitted.
  • the facility layer of the ITS-S may include an ATS module, and the management layer may include an ATM module.
  • the hybrid application of the application layer may deliver the hybrid application data to the ATS module of the facility layer through FA-SAP.
  • the ATS module can obtain information on the available access technology and the maximum packet size from the ATM module through the MF-SAP extension.
  • the MF-SAP extension may include the same primitives and fields as the above-described MA-SAP.
  • the MF-SAP extension may include an ATM request primitive and an ATM request confirmation primitive.
  • the ATM request field may be as shown in Table 8 above. This allows the ATS module to obtain a list of available access technologies and a list of maximum packet sizes (MPS_acc) associated with the available access technologies from the ATM module.
  • the ATS module may determine the maximum packet size (MPS_fac) of the target access technology and the facility layer based on the list of this available access technology and the list of the maximum packet size.
  • the facility layer may determine the packet transmission type for geonetworking.
  • the facility layer may determine the maximum packet size (MPS_acc_gn) associated with geonetworking based on the packet transmission type.
  • MPS_acc_gn the maximum packet size associated with geonetworking based on the packet transmission type.
  • Table 10 is an example of a table indicating after MPS_acc_ according to a packet transmission type.
  • Packet Transport Type MPS_acc_gn Maximum access layer packet size (option # 1) Maximum access layer packet size (option # 2) SHB (Single Hop Broadcast) 1500 octets MPS_acc TSB (Topology Scoped Broadcast) 1 hop 1500 octets MPS_acc 2 to 5 hops 1200 octets MPS_acc x 0.8 6 to 10 hops 900 octets MPS_acc x 0.6 11 to 15 hops 600 octets MPS_acc x 0.4 > 15 hops 300 octets MPS_acc x 0.2 GeoUnicast / GeoBroadcast / GeoAnycast ⁇ 300 m 1500 octets MPS_acc 301-600 m 1200 octets MPS_acc x 0.8 601-900 m 900 octets MPS_acc x 0.6 901-1200 m 600 octets
  • the value of MPS_acc_gn may have a predetermined value according to a packet transmission type irrelevant to MPS_acc (option # 1).
  • MPS_acc_gn may have a value of 1500 octets.
  • MPS_acc_gn may have a value of 1500, 1200, 900, 600 or 300 octets according to the number of delivery hops.
  • the packet transmission type is geounicast, geobroadcast, or geoanicast
  • the packet transmission type may have a value of 1500, 1200, 900, 600, or 300 octets depending on the transmission distance. That is, MPS_acc_gn may have a predetermined value according to each packet transmission type irrespective of MPS_acc.
  • the value of MPS_acc_gn may have a value associated with MPS_acc predetermined according to the packet transmission type (option # 2). For example, if the packet transmission type is SHB, MPS_acc_gn may have a value of MPS_acc. Alternatively, if the packet transmission type is SHB, MPS_acc_gn may have a value of MPS_acc, MPS_acc * 0.8, MPS_acc * 0.6, MPS_acc * 0.4 or MPS_acc * 0.2 according to the number of delivery hops.
  • the packet transmission type may have a value of MPS_acc, MPS_acc * 0.8, MPS_acc * 0.6, MPS_acc * 0.4 or MPS_acc * 0.2 depending on the transmission distance. That is, MPS_acc_dcc may have a value associated with MPS_acc.
  • the ATS module may determine the size of the message segment transmitted from the facility layer to the lower layer by using MPS_acc and MPS_acc_gn as follows.
  • Message segment size of facilities layer ⁇ min ⁇ MPS_fac, MPS_fac_dcc, MPS_fac_gn ⁇
  • the ATS module may perform message segmentation at the facility layer based on this message segment size.
  • V2X communication device 42 shows a configuration of a V2X communication device according to an embodiment of the present invention.
  • the V2X communication device 42000 may include a communication unit 4210, a processor 4420, and a memory 4430.
  • the communication unit 4210 may be connected to the processor 4420 to transmit / receive a radio signal.
  • the communication unit 4210 may up-convert data received from the processor 4420 to a transmission / reception band to transmit a signal, or downconvert the received signal.
  • the communication unit 4210 may implement at least one of the physical layer and the access layer.
  • the communication unit 4210 may include a plurality of sub-RF units for communicating in accordance with a plurality of communication protocols.
  • the communication unit 4210 may include a dedicated short range communication (DSRC), an ITS-G5 wireless communication technology, a satellite based on the physical transmission technology of the IEEE 802.11 and / or 802.11p standard, the IEEE 802.11 and / or 802.11p standard.
  • Data communication based on 2G / 3G / 4G (LTE) / 5G wireless cellular communication technology including broadband wireless mobile communication, broadband terrestrial digital broadcasting technology such as DVB-T / T2 / ATSC, GPS technology, IEEE 1609 WAVE technology, etc. Can be done.
  • the communication unit 4210 may include a plurality of transceivers that implement each communication technology.
  • the communication unit 4210 includes a plurality of transceivers, where one transceiver can communicate on a CCH and another transceiver can communicate on a SCH.
  • the communication unit 4210 may perform multichannel operation using a plurality of transceivers.
  • the processor 4220 may be connected to the RF unit 4230 to implement operations of layers according to the ITS system or the WAVE system.
  • the processor 4220 may be configured to perform operations according to various embodiments of the present disclosure according to the above-described drawings and descriptions.
  • at least one of a module, data, a program, or software for implementing an operation of the V2X communication device 42000 according to various embodiments of the present disclosure described above may be stored in the memory 4210 and executed by the processor 4420. have.
  • the memory 4210 is connected to the processor 4420 and stores various information for driving the processor 4420.
  • the memory 4210 may be included in the processor 4420 or may be installed outside the processor 4420 to be connected to the processor 4420 by known means.
  • V2X communication device may be a V2X communication device of the vehicle.
  • the V2X communication device may select a target access technology for transmitting the V2X message (S43010).
  • selecting a target access technology includes access information related information obtained from a management entity (eg, an ATM entity) by an access technology selection (ATS) entity and the ATS based on the access technology related information. It may include selecting.
  • the ATS entity passes a request primitive (eg, ATM.REQUEST.request) requesting the access technology related information to the management entity, and includes a confirmation primitive (eg, the access technology related information).
  • a request primitive eg, ATM.REQUEST.request
  • confirmation primitive eg, the access technology related information
  • ATM.REQUEST.confirm may be received from the management entity.
  • the access technology related information may include available access technology information that provides a list of available access technologies.
  • the access technology related information may further include at least one of bandwidth information providing a list of bandwidths associated with an available access technology or CBR information providing a list of channel busy ratios (CBRs) associated with an available access technology.
  • bandwidth information providing a list of bandwidths associated with an available access technology
  • CBR information providing a list of channel busy ratios (CBRs) associated with an available access technology.
  • the V2X communication device may process the input data into a plurality of message segments (S43020).
  • the access technology related information may further include maximum packet size information providing a list of maximum packet sizes associated with the available access technology.
  • the ATS entity determines the size of the message segment using the maximum packet size information, and generates the plurality of message segments from the input data based on the determined size of the message segment, thereby processing the input data into the plurality of message segments. can do.
  • the input data is data of a layer on which message segmentation is performed, and may be referred to as an input packet or an input message.
  • each message segment may include a payload having a header and segmented data.
  • the header may include message ID information and segment ID information indicating the order of message segments, and the message ID information of each message segment generated from input data may be set to the same value.
  • This message ID information and segment ID information can be used to merge message segments generated from one input data (message) in the received ITS-S.
  • the V2X communication device may transmit V2X messages including each message segment using the target access technology (S43030).
  • each message segment may be sent via a separate V2X message.
  • the first V2X message may comprise a first message segment and the second V2X message may comprise a second message segment.
  • the AT entity may be an application layer entity, a facility layer entity or a networking and transport layer entity. That is, the above-described access technology selection and message segmentation may be performed in one of an application layer, a facility layer, or a networking / transport layer.
  • each component or feature is to be considered optional unless stated otherwise.
  • Each component or feature may be embodied in a form that is not combined with other components or features. It is also possible to combine some of the components and / or features to form an embodiment of the invention.
  • the order of the operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is obvious that the claims may be combined to form an embodiment by combining claims that do not have an explicit citation relationship in the claims or as new claims by post-application correction.
  • Embodiments according to 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), FPGAs ( 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
  • FPGAs field programmable gate arrays
  • processors controllers, microcontrollers, microprocessors, and the like.
  • an embodiment of the present invention may be implemented in the form of a module, procedure, function, etc. that performs the functions or operations described above.
  • the software code may be stored in memory and driven by the processor.
  • the memory may be located inside or outside the processor, and may exchange data with the processor by various known means.
  • the present invention is used in the field of vehicle communications.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé d'émission d'un message V2X au moyen d'un dispositif de communication V2X. Un procédé de communication V2X peut comporter les étapes consistant à: sélectionner une technologie d'accès cible pour l'émission d'un message V2X; traiter des données d'entrée pour obtenir une pluralité de segments de message; et émettre des messages V2X comportant chacun des segments de message respectifs au moyen de la technologie d'accès cible.
PCT/KR2018/001944 2018-02-14 2018-02-14 Dispositif de communication v2x et procédé d'émission et de réception de message v2x au moyen de celui-ci Ceased WO2019160176A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/KR2018/001944 WO2019160176A1 (fr) 2018-02-14 2018-02-14 Dispositif de communication v2x et procédé d'émission et de réception de message v2x au moyen de celui-ci

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/KR2018/001944 WO2019160176A1 (fr) 2018-02-14 2018-02-14 Dispositif de communication v2x et procédé d'émission et de réception de message v2x au moyen de celui-ci

Publications (1)

Publication Number Publication Date
WO2019160176A1 true WO2019160176A1 (fr) 2019-08-22

Family

ID=67619959

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2018/001944 Ceased WO2019160176A1 (fr) 2018-02-14 2018-02-14 Dispositif de communication v2x et procédé d'émission et de réception de message v2x au moyen de celui-ci

Country Status (1)

Country Link
WO (1) WO2019160176A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021089237A1 (fr) * 2019-11-04 2021-05-14 Robert Bosch Gmbh Procédé de transmission d'un message dans un réseau de communication pour la communication entre un usager de la route et au moins un autre usager de la route

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100062800A1 (en) * 2008-09-08 2010-03-11 Agere Systems Inc. Wireless communications using multiple radio access technologies simultaneously
US20130343408A1 (en) * 2012-06-21 2013-12-26 Brent Aaron Cook High-speed cld-based tcp segmentation offload
US9161281B2 (en) * 2012-06-08 2015-10-13 Blackberry Limited Method and apparatus for multi-rat transmission
KR20160091891A (ko) * 2013-11-29 2016-08-03 바이에리셰 모토렌 베르케 악티엔게젤샤프트 차량 통신 시스템 및 상기 시스템을 작동하기 위한 방법
WO2017189035A1 (fr) * 2016-04-29 2017-11-02 Intel IP Corporation Interopérabilité entre des technologies d'accès radio (rat) v2x (v2v (véhicule à véhicule), v2i (véhicule à infrastructure) et/ou v2p (véhicule à piéton))

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100062800A1 (en) * 2008-09-08 2010-03-11 Agere Systems Inc. Wireless communications using multiple radio access technologies simultaneously
US9161281B2 (en) * 2012-06-08 2015-10-13 Blackberry Limited Method and apparatus for multi-rat transmission
US20130343408A1 (en) * 2012-06-21 2013-12-26 Brent Aaron Cook High-speed cld-based tcp segmentation offload
KR20160091891A (ko) * 2013-11-29 2016-08-03 바이에리셰 모토렌 베르케 악티엔게젤샤프트 차량 통신 시스템 및 상기 시스템을 작동하기 위한 방법
WO2017189035A1 (fr) * 2016-04-29 2017-11-02 Intel IP Corporation Interopérabilité entre des technologies d'accès radio (rat) v2x (v2v (véhicule à véhicule), v2i (véhicule à infrastructure) et/ou v2p (véhicule à piéton))

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021089237A1 (fr) * 2019-11-04 2021-05-14 Robert Bosch Gmbh Procédé de transmission d'un message dans un réseau de communication pour la communication entre un usager de la route et au moins un autre usager de la route
CN114642022A (zh) * 2019-11-04 2022-06-17 罗伯特·博世有限公司 用于在用于交通参与者与至少一个另外的交通参与者之间通信的通信网络中传输消息的方法
US20220386169A1 (en) * 2019-11-04 2022-12-01 Robert Bosch Gmbh Method for transferring a message in a communications network for communication between a road user and at least one further road user
JP2023500881A (ja) * 2019-11-04 2023-01-11 ロベルト・ボッシュ・ゲゼルシャフト・ミト・ベシュレンクテル・ハフツング 交通参加者と少なくとも１人の他の交通参加者との間の通信のための通信ネットワークでメッセージを伝送するための方法
JP7326607B2 (ja) 2019-11-04 2023-08-15 ロベルト・ボッシュ・ゲゼルシャフト・ミト・ベシュレンクテル・ハフツング 交通参加者と少なくとも１人の他の交通参加者との間の通信のための通信ネットワークでメッセージを伝送するための方法
US12238576B2 (en) * 2019-11-04 2025-02-25 Robert Bosch Gmbh Method for transferring a message in a communications network for communication between a road user and at least one further road user

Similar Documents

Publication Publication Date Title
WO2019160177A1 (fr) Dispositif de communication v2x et procédé de transmission et de réception de messages v2x au moyen de celui-ci
WO2019066106A1 (fr) Dispositif de communication v2x et procédé d'émission/réception de contenu multimédia associé
WO2018174385A1 (fr) Dispositif de communication v2x et procédé associé d'émission et de réception d'un message v2x
WO2019156266A1 (fr) Dispositif de communication v2x et procédé de communication v2x d'un dispositif de communication v2x
WO2019132082A1 (fr) Dispositif de communication v2x et son procédé d'émission et de réception d'un message v2x
WO2021162397A1 (fr) Procédé et dispositif pour déterminer des ressources devant être détectées pour une communication de dispositif à dispositif dans un système de communication sans fil
WO2020032753A1 (fr) Procédé et dispositif de transmission et de réception d'un signal sans fil dans un système de communication sans fil
WO2022203299A1 (fr) Procédé de transmission/réception de psfch dans un système de communication sans fil, et dispositif associé
WO2018128205A1 (fr) Dispositif et procédé de communication v2x
WO2023287224A1 (fr) Procédé de transmission et de réception d'un canal physique partagé de liaison latérale dans un système de communication sans fil, et dispositif associé
WO2020096433A1 (fr) Appareil et procédé de sélection de technologie d'accès radio pour communication directe entre terminaux dans un système de communication sans fil
WO2020022526A1 (fr) Dispositif de communication v2x et procédé de transmission par géoroutage
WO2019199140A1 (fr) Procédé et dispositif d'attribution de ressources permettant de prendre en charge une communication de véhicule dans un système de communication mobile de prochaine génération
WO2020067816A1 (fr) Procédé et dispositif pour réalisation d'une opération harq pour système v2x nr
WO2020197310A1 (fr) Procédé de transmission de message de sécurité dans un système de communication sans fil prenant en charge les liaisons latérales et appareil associé
WO2019074242A1 (fr) Procédé et dispositif de communication pour un véhicule à vitesse ultra-élevée
WO2022220615A1 (fr) Procédé et dispositif pour transmettre ou recevoir un canal physique de rétroaction de liaison latérale dans un système de communication sans fil
WO2018182074A1 (fr) Dispositif et procédé de communication v2x
WO2018128206A1 (fr) Dispositif et procédé de communication v2x
WO2022235082A1 (fr) Procédé et appareil de détermination d'une ressource non préférée dans un système de communication sans fil
WO2021040144A1 (fr) Procédé de transmission et de réception de signal par un véhicule dans un système de communication sans fil et véhicule associé
WO2021100938A1 (fr) Procédé de transmission de signal entre un véhicule, un terminal et un réseau dans un système de communication sans fil, et véhicule, terminal et réseau correspondants
WO2023043283A1 (fr) Procédé de transmission et de réception d'informations de coordination inter-équipements utilisateurs dans un système de communication sans fil et appareil associé
WO2019117369A1 (fr) Dispositif de communication v2x et procédé de communication associé
WO2021045253A1 (fr) Procédé de communication avec un véhicule dans un système de communication sans fil et terminal utilisateur associé

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18905995

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18905995

Country of ref document: EP

Kind code of ref document: A1