Method for transmitting message in wireless communication system, and device therefor

Abstract

A device according to various embodiments may receive a first message issued using first identification information related to a road section and issue a second message for delivering the first message, wherein on the basis that the first message is issued by a vulnerable road user (VRU) device, the second message may be issued using second identification information about a cell area converted to correspond to the road section.

Description

Method for transmitting a message in a wireless communication system and device therefor

[0001] A method for providing a message based on a message protocol in a wireless communication system and a device therefor are provided.

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

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

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

[0005] Meanwhile, as more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Accordingly, communication systems that consider services or terminals sensitive to reliability and latency are being discussed. Next-generation wireless access technologies that consider improved mobile broadband communication, massive machine type communication (MTC), and ultra-reliable and low latency communication (URLLC) can be called new radio access technology (RAT) or new radio (NR). NR can also support vehicle-to-everything (V2X) communication.

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

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

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

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

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

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

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

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

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

[0015] The technical challenge is to provide a more accurate and efficient way to transmit and receive data / messages.

[0016] The technical challenges are not limited to the technical challenges mentioned above, and other technical challenges not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the description below.

[0017] A method according to one aspect comprises the steps of: receiving, by a first device, a first message issued using first identification information associated with a road segment; and issuing, by the first device, a second message for transmitting the first message, wherein, based on the first message being issued by a Vulnerable Road User (VRU) device, the second message can be issued using second identification information for a cell area converted to correspond to the road segment.

[0018] Alternatively, the cell area may be a Quadtree-based cell area or a Geohash-based cell area.

[0019] Alternatively, the second identification information may be defined based on an index value of the quadtree-based cell area or a string of a geohash-based cell area.

[0020] Alternatively, the first identification information may be a topic (TOPIC) defined based on the road section, and the second identification information may be a topic (TOPIC) defined based on an index value for the quadtree-based cell area or a string for the geohash-based cell area.

[0021] Alternatively, the first identification information may include information about a first node and a second node associated with the road section.

[0022] Alternatively, the first device may determine a geographic area corresponding to the first identification information based on a curved section having a preset maximum curvature between the first node and the second node, and the second identification information may be determined based on an index value for at least one quadtree-based cell area overlapping the geographic area or a string for at least one geohash-based cell area.

[0023] Alternatively, the preset maximum curvature may be 60 degrees.

[0024] Alternatively, based on the first message being transmitted from a device associated with the vehicle, the second message may be issued using the first identification information.

[0025] In another aspect, at least one non-transitory computer-readable medium comprises instructions that, when executed by at least one processor, perform operations, the operations comprising: receiving a first message issued using first identification information associated with a road segment; and issuing a second message for transmitting the first message, wherein, based on the first message being issued by a Vulnerable Road User (VRU) device, the second message can be issued using second identification information for a cell area converted to correspond to the road segment.

[0026] According to another aspect, a first device includes: a Radio Frequency (RF) transceiver; a processor connected to the RF transceiver; and a memory including at least one program that performs operations when executed by the processor; wherein the operations include receiving a first message issued using first identification information related to a road section; and issuing a second message for transmitting the first message, wherein the second message can be issued using second identification information for a cell area converted to correspond to the road section based on the first message being issued by a Vulnerable Road User (VRU) device.

[0027] A processing device for controlling a first device performing the above-described method according to another aspect comprises: at least one processor; and at least one memory connected to the at least one processor and storing instructions that, when executed by the at least one processor, perform operations, wherein the operations include: receiving a first message issued by the first device using first identification information related to a road segment; and issuing a second message for transmitting the first message, wherein, based on the first message being issued by a Vulnerable Road User (VRU) device, the second message can be issued using second identification information for a cell area converted to correspond to the road segment.

[0028] According to another aspect, a method comprises the steps of: receiving, by a second device, from a first broker, a first message issued using first identification information related to a road segment; and issuing, by the second device, a second message for transmitting the first message, wherein, based on the second message being transmitted to a second broker that geo-casts the message based on a cell area, the second message can be issued to the first broker using second identification information for a cell area converted to correspond to the road segment.

[0029] In another aspect, at least one non-transitory computer-readable medium comprises instructions that, when executed by at least one processor, perform operations, the operations comprising: receiving a first message issued using first identification information associated with a road segment from a first broker; and issuing a second message for forwarding the first message, wherein the second message is forwarded to a second broker that geo-casts the message based on a cell area, and the second message can be issued to the first broker using second identification information for a cell area converted to correspond to the road segment.

[0030] According to another aspect, a second device comprises: a Radio Frequency (RF) transceiver; a processor connected to the RF transceiver; and a memory including at least one program that performs operations when executed by the processor, wherein the operations include receiving a first message issued using first identification information related to a road segment from a first broker; and issuing a second message for delivering the first message, wherein the second message can be issued to the first broker using second identification information for a cell area converted to correspond to the road segment based on the second message being delivered to a second broker that geo-casts the message based on a cell area.

[0031] A processing device for controlling a second device according to another aspect comprises at least one processor; and at least one memory connected to the at least one processor and storing instructions that, when executed by the at least one processor, perform operations, wherein the operations include: receiving, by the second device, a first message issued using first identification information related to a road segment from a first broker; and issuing, by the second device, a second message for delivering the first message, wherein, based on the second message being delivered to a second broker that geo-casts a message based on a cell area, the second message can be issued to the first broker using second identification information for a cell area converted to correspond to the road segment.

[0032] Various embodiments allow for more accurate and efficient data / message transmission and reception in wireless communication systems. For example, for messages issued from Vulnerable Road User (VRU) devices, a road segment-based geocasting method can be effectively switched to a cell area-based geocasting method suited to the VRU's mobility characteristics.

[0033] The effects that can be obtained in various embodiments are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the description below.

[0034] The drawings attached to this specification are intended to provide an understanding of the present invention, illustrate various embodiments of the present invention, and together with the description of the specification serve to explain the principles of the present invention.

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

[0036] Figure 2 shows the structure of the LTE system.

[0037] Figure 3 shows the structure of the NR system.

[0038] Figure 4 shows the structure of a radio frame of NR.

[0039] Figure 5 shows the slot structure of an NR frame.

[0040] FIG. 6 illustrates a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure.

[0041] FIG. 7 illustrates an electromagnetic spectrum according to one embodiment of the present disclosure.

[0042] FIG. 8 illustrates an example of a typical scenario of an NTN based on a transparent payload, according to one embodiment of the present disclosure.

[0043] FIG. 9 illustrates an example of a typical scenario of an NTN based on a regenerative payload, according to one embodiment of the present disclosure.

[0044] FIG. 10 illustrates an example of a sensing operation according to one embodiment of the present disclosure.

[0045] Figure 11 shows a radio protocol architecture for SL communication.

[0046] Figure 12 shows a terminal performing V2X or SL communication.

[0047] Figure 13 shows resource units for V2X or SL communication.

[0048] FIG. 14 illustrates an example of a BWP according to one embodiment of the present disclosure.

[0049] FIG. 15 illustrates a procedure for a terminal to perform V2X or SL communication according to a resource allocation mode, according to one embodiment of the present disclosure.

[0050] Figure 16 is a diagram for explaining the AMQP protocol for transmitting V2N messages.

[0051] Figure 17 is a diagram for explaining the MQTT protocol for transmitting V2N messages.

[0052] FIG. 18 and FIG. 19 are diagrams illustrating a method of dividing a geographic space into a plurality of cells or a plurality of geographic areas.

[0053] Figure 20 is a diagram illustrating a method for exchanging messages between heterogeneous service providers.

[0054] Figures 21 and 22 are diagrams illustrating a method for converting between topics based on a quadtree and topics based on a geohash.

[0055] Figure 23 is a diagram for explaining a method of conversion between identification information for a road section and identification information for a cell area.

[0056] Figure 24 is a drawing illustrating how the first device issues the second message.

[0057] Figure 25 is a diagram illustrating how a second device relays messages between two brokers.

[0058] Figure 26 illustrates a communication system applied to the present invention.

[0059] Figure 27 illustrates a wireless device applicable to the present invention.

[0060] Figure 28 illustrates another example of a wireless device applicable to the present invention. The wireless device may be implemented in various forms depending on the use case / service.

[0061] Figure 29 illustrates a vehicle or autonomous vehicle to which the present invention is applied.

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

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

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

[0065] Meanwhile, as more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Accordingly, communication systems that consider services or terminals sensitive to reliability and latency are being discussed. Next-generation wireless access technologies that consider improved mobile broadband communication, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) can be called new radio access technology (RAT) or new radio (NR). NR can also support V2X (vehicle-to-everything) communication.

[0066] The following technologies can be used in various wireless communication systems, such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved UTRA). IEEE 802.16m is an evolution of IEEE 802.16e, providing backward compatibility with systems based on IEEE 802.16e. UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long term evolution) is a part of E-UMTS (evolved UMTS) that uses E-UTRA (evolved-UMTS terrestrial radio access), employing OFDMA in the downlink and SC-FDMA in the uplink.LTE-A (advanced) is an evolution of 3GPP LTE.

[0067] 5G NR, the successor to LTE-A, is a new clean-slate mobile communications system featuring high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, from low-frequency bands below 1 GHz, mid-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz.

[0068] For clarity, the description will focus on LTE-A or 5G NR, but the technical ideas of the embodiment(s) are not limited thereto.

[0069] Figure 2 illustrates the architecture of an applicable LTE system. This may be referred to as an Evolved-UMTS Terrestrial Radio Access Network (E-UTRAN) or a Long Term Evolution (LTE) / LTE-A system.

[0070] Referring to FIG. 2, the E-UTRAN includes a base station (20; BS) that provides a control plane and a user plane to a terminal (10). The terminal (10) may be fixed or mobile, and may be referred to by other terms such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT), a wireless device, etc. The base station (20) refers to a fixed station that communicates with the terminal (10), and may be referred to by other terms such as an evolved-NodeB (eNB), a base transceiver system (BTS), an access point, etc.

[0071] Base stations (20) can be connected to each other via the X2 interface. The base station (20) is connected to an EPC (Evolved Packet Core, 30) via the S1 interface, more specifically, to an MME (Mobility Management Entity) via the S1-MME, and to an S-GW (Serving Gateway) via the S1-U.

[0072] The EPC (30) consists of an MME, an S-GW, and a P-GW (Packet Data Network-Gateway). The MME holds information about terminal access and capabilities, and this information is primarily used for terminal mobility management. The S-GW is a gateway with the E-UTRAN as its endpoint, and the P-GW is a gateway with the PDN as its endpoint.

[0073] The layers of the radio interface protocol between the terminal and the network can be divided into L1 (Layer 1), L2 (Layer 2), and L3 (Layer 3) based on the three lower layers of the Open System Interconnection (OSI) standard model, which is widely known in communication systems. Among these, the physical layer belonging to Layer 1 provides an information transfer service using a physical channel, and the RRC (Radio Resource Control) layer located in Layer 3 controls radio resources between the terminal and the network. To this end, the RRC layer exchanges RRC messages between the terminal and the base station.

[0074] Figure 3 shows the structure of the NR system.

[0075] Referring to FIG. 3, the NG-RAN may include a gNB and / or an eNB that provides user plane and control plane protocol termination to the UE. FIG. 7 illustrates a case where only a gNB is included. The gNB and eNB are connected to each other via an Xn interface. The gNB and eNB are connected to the 5th generation core network (5G Core Network: 5GC) via the NG interface. More specifically, the gNB is connected to the access and mobility management function (AMF) via the NG-C interface, and the gNB is connected to the user plane function (UPF) via the NG-U interface.

[0076] Figure 4 shows the structure of a radio frame of NR.

[0077] Referring to FIG. 4, radio frames can be used for uplink and downlink transmission in NR. A radio frame has a length of 10 ms and can be defined as two 5 ms half-frames (Half-Frames, HF). A half-frame can include five 1 ms sub-frames (Subframes, SF). A sub-frame can be divided into one or more slots, and the number of slots within a sub-frame can be determined by the Subcarrier Spacing (SCS). Each slot can include 12 or 14 OFDM (A) symbols depending on the cyclic prefix (CP).

[0078] When normal CP is used, each slot can contain 14 symbols. When extended CP is used, each slot can contain 12 symbols. Here, the symbols can include OFDM symbols (or CP-OFDM symbols), SC-FDMA (Single Carrier - FDMA) symbols (or DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) symbols).

[0079] Table 1 below shows the number of symbols per slot ((N)) depending on the SCS setting (u) when normal CP is used. slot symb ), number of slots per frame ((N frame,u slot ) and the number of slots per subframe ((N subframe,u slot ) is an example.

[0080] SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot 15KHz (u=0)1410130KHz (u=1)1420260KHz (u=2)14404120KHz (u=3)14808240KHz (u=4)1416016

[0081] Table 2 illustrates the number of symbols per slot, the number of slots per frame, and the number of slots per subframe according to SCS when extended CP is used.

[0082] SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot 60KHz (u=2)12404

[0083] In an NR system, OFDM(A) numerology (e.g., SCS, CP length, etc.) may be set differently between multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., subframe, slot, or TTI) (conveniently referred to as TU (Time Unit)) consisting of the same number of symbols may be set differently between the merged cells.

[0084] In NR, multiple numerologies, or SCSs, can be supported to support various 5G services. For example, a 15 kHz SCS can support wide areas in traditional cellular bands, while a 30 kHz / 60 kHz SCS can support dense urban areas, lower latency, and wider carrier bandwidth. A 60 kHz or higher SCS can support bandwidths greater than 24.25 GHz to overcome phase noise.

[0085] The NR frequency band can be defined by two types of frequency ranges. The two types of frequency ranges can be FR1 and FR2. The numerical values ​​of the frequency ranges can be changed, and for example, the two types of frequency ranges can be as shown in Table 3 below. Among the frequency ranges used in the NR system, FR1 can mean the "sub 6 GHz range", and FR2 can mean the "above 6 GHz range" and can be called millimeter wave (mmW).

[0086] Frequency Range designationCorresponding frequency rangeSubcarrier Spacing (SCS)FR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0087] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a band from 410 MHz to 7125 MHz, as shown in Table 4 below. That is, FR1 may include a frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, such as for vehicular communications (e.g., autonomous driving).

[0088] Frequency Range designationCorresponding frequency rangeSubcarrier Spacing (SCS)FR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0089] Figure 5 shows the slot structure of an NR frame.

[0090] Referring to Figure 5, a slot includes multiple symbols in the time domain. For example, in the case of a normal CP, one slot may include 14 symbols, but in the case of an extended CP, one slot may include 12 symbols. Alternatively, in the case of a normal CP, one slot may include 7 symbols, but in the case of an extended CP, one slot may include 6 symbols.

[0091] A carrier includes multiple subcarriers in the frequency domain. An RB (Resource Block) can be defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth Part) can be defined as multiple consecutive (P)RBs ((Physical) Resource Blocks) in the frequency domain, and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed through activated BWPs. Each element can be referred to as a Resource Element (RE) in the resource grid, and one complex symbol can be mapped to it.

[0092] Meanwhile, the wireless interface between terminals or between terminals and a network may be composed of an L1 layer, an L2 layer, and an L3 layer. In various embodiments of the present disclosure, the L1 layer may refer to a physical layer. Furthermore, for example, the L2 layer may refer to at least one of a MAC layer, an RLC layer, a PDCP layer, and an SDAP layer. Furthermore, for example, the L3 layer may refer to an RRC layer.

[0093] FIG. 6 illustrates a communication structure that can be provided in a 6G system according to an embodiment of the present disclosure. The embodiment of FIG. 6 can be combined with various embodiments of the present disclosure.

[0094] New network characteristics in 6G may include:

[0095] - Satellite integrated network

[0096] - Connected Intelligence: Unlike previous generations of wireless communication systems, 6G is revolutionary, upgrading the wireless evolution from "connected objects" to "connected intelligence." AI can be applied at every stage of the communication process (or at every signal processing step, as described below).

[0097] - Seamless integration of wireless information and energy transfer

[0098] - Ubiquitous super 3D connectivity: Access to networks and core network functions of drones and very low Earth orbit satellites will create super 3D connectivity in 6G ubiquitous.

[0099] Some general requirements for the new network characteristics of 6G, such as the above, may be as follows:

[0100] - small cell networks

[0101] - Ultra-dense heterogeneous network

[0102] - High-capacity backhaul

[0103] - Radar technology integrated with mobile technology: High-precision localization (or location-based services) through communications is a key feature of 6G wireless communication systems. Therefore, radar systems will be integrated with 6G networks.

[0104] - Softwarization and virtualization

[0105] Below, the core implementation technologies of the 6G system are described.

[0106] - Artificial Intelligence: Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. This means AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. Furthermore, AI can facilitate rapid communication in brain-computer interfaces (BCIs). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0107] - THz communication (terahertz communication): Data rates can be increased by increasing the bandwidth. This can be achieved by using sub-THz communication with wide bandwidths and applying advanced massive MIMO technology. THz waves, also known as sub-millimeter waves, typically refer to the frequency range between 0.1 THz and 10 THz, with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz to 300 GHz band (sub-THz band) is considered a key part of the THz spectrum for cellular communications. Adding the sub-THz band to the mmWave band will increase the capacity of 6G cellular communications. Among the defined THz bands, 300 GHz to 3 THz lies in the far infrared (IR) frequency band. While part of the optical band, the 300 GHz to 3 THz band lies at the boundary of the optical band, immediately following the RF band. Therefore, this 300 GHz to 3 THz band exhibits similarities to RF.

[0108] Figure 7 illustrates the electromagnetic spectrum according to one embodiment of the present disclosure. The embodiment of Figure 7 can be combined with various embodiments of the present disclosure. Key characteristics of THz communications include (i) a widely available bandwidth to support very high data rates, and (ii) high path loss at high frequencies (highly directional antennas are essential). The narrow beamwidth generated by the highly directional antenna reduces interference. The small wavelength of THz signals allows for a much larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array techniques to overcome range limitations.

[0109] - Large-scale MIMO technology

[0110] - Hologram beamforming (HBF)

[0111] - Optical wireless technology

[0112] - Free-space optical transmission backhaul network (FSO backhaul network)

[0113] - Quantum communication

[0114] - Cell-free communication

[0115] - Integration of wireless information and power transmission

[0116] - Integration of wireless communication and sensing

[0117] - Integrated access and backhaul network

[0118] - Big data analysis

[0119] - Reconfigurable intelligent surface

[0120] - metaverse

[0121] - Block chain

[0122] Unmanned aerial vehicles (UAVs): UAVs, or drones, will be a key element in 6G wireless communications. In most cases, high-speed data wireless connectivity can be provided using UAV technology. Base stations (BSs) can be installed on UAVs to provide cellular connectivity. UAVs may offer specific capabilities not found in fixed BS infrastructure, such as easy deployment, robust line-of-sight links, and controlled mobility. During emergencies such as natural disasters, deploying terrestrial communications infrastructure is not economically feasible and sometimes cannot provide services in volatile environments. UAVs can easily handle these situations. UAVs will become a new paradigm in wireless communications. This technology facilitates three fundamental requirements for wireless networks: enhanced mobile broadband (eMBB), URLLC, and mMTC. UAVs can also support various purposes, such as enhancing network connectivity, fire detection, disaster emergency services, security and surveillance, pollution monitoring, parking monitoring, and accident monitoring. Therefore, UAV technology is recognized as one of the most important technologies for 6G communications.

[0123] - Autonomous driving (self-driving): V2X (vehicle to everything), a key element in building autonomous driving infrastructure, can be a technology that allows cars to communicate and share with various elements on the road for autonomous driving, such as vehicle-to-vehicle (V2V) and vehicle-to-infrastructure (V2I) wireless communication. Fast transmission speeds and low-latency technologies are essential to maximize autonomous driving performance and ensure high safety. Furthermore, in the future, autonomous driving will go beyond simply providing warnings or guidance messages to drivers and may require active intervention in vehicle operation and direct control of the vehicle in dangerous situations. To this end, the amount of information that needs to be transmitted and received may become enormous, so 6G is expected to maximize autonomous driving with faster transmission speeds and lower latency than 5G.

[0124] - Non-terrestrial networks (NTN): NTN may refer to a network or network segment that uses radio frequency (RF) resources mounted on a satellite (or unmanned aerial system (UAS) platform). FIG. 8 illustrates an example of a typical NTN scenario based on a transparent payload according to an embodiment of the present disclosure. FIG. 9 illustrates an example of a typical NTN scenario based on a regenerative payload according to an embodiment of the present disclosure. The embodiments of FIG. 8 or FIG. 9 may be combined with various embodiments of the present disclosure. Referring to FIG. 8, a satellite (or UAS platform) may create a service link with a UE. The satellite (or UAS platform) may be connected to a gateway via a feeder link. The satellite may be connected to a data network via the gateway. A beam footprint may refer to an area where a signal transmitted by a satellite can be received. Referring to Figure 9, a satellite (or UAS platform) can establish a service link with a UE. A satellite (or UAS platform) connected to a UE can be connected to another satellite (or UAS platform) via an inter-satellite link (ISL). The other satellite (or UAS platform) can be connected to a gateway via a feeder link. Based on the replay payload, a satellite can be connected to a data network through another satellite and the gateway. If an ISL does not exist between a satellite and another satellite, a feeder link between the satellite and the gateway may be required. Figures 8 and 9 are merely examples of NTN scenarios, and NTN can be implemented based on various scenarios.For example, a satellite (or UAS platform) may implement a transparent or regenerative (with onboard processing) payload. For example, a satellite (or UAS platform) may generate multiple beams over a designated service area depending on the field of view of the satellite (or UAS platform). For example, the field of view of the satellite (or UAS platform) may vary depending on the onboard antenna diagram and minimum elevation angle. For example, a transparent payload may include radio frequency filtering, frequency conversion, and amplification. Therefore, the waveform signal repeated by the payload may not be altered. For example, a regenerative payload may include radio frequency filtering, frequency conversion and amplification, demodulation / decoding, switching and / or routing, and coding / modulation. For example, a regenerative payload may be substantially equivalent to equipping the satellite (or UAS platform) with all or part of the base station functionality.

[0125] - Integrated Sensing and Communication (ISAC): Wireless sensing is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, distance (range), etc. of an object, thereby obtaining information about the characteristics of the environment and / or objects within the environment. Because radio frequency sensing does not require a device to connect to the object through a network, it can provide a service for object positioning without a device. The ability to obtain range, velocity, and angle information from radio frequency signals can enable a wide range of new capabilities, such as various object detection, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to a variety of industries (e.g., drones, smart homes, V2X, factories, railways, public safety, etc.), enabling applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, wireless sensing can utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of a wireless sensing service, i.e., a sensing operation, may depend on the transmission, reflection, and scattering of wireless sensing signals. Therefore, wireless sensing may provide an opportunity to enhance existing communication systems from a communication network to a wireless communication and sensing network. FIG. 10 illustrates an example of a sensing operation according to an embodiment of the present disclosure. The embodiment of FIG. 10 may be combined with various embodiments of the present disclosure. Specifically, FIG. 10 (a) illustrates an example of sensing using a sensing receiver and a sensing transmitter located at the same location (e.g., monostatic sensing), and FIG. 10 (b) illustrates an example of sensing using a separated sensing receiver and a sensing transmitter (e.g., bistatic sensing).

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

[0127] Below, the SL synchronization signal (Sidelink Synchronization Signal, SLSS) and synchronization information are described.

[0128] SLSS is an SL-specific sequence and may include a Primary Sidelink Synchronization Signal (PSSS) and a Secondary Sidelink Synchronization Signal (SSSS). The PSSS may be referred to as a Sidelink Primary Synchronization Signal (S-PSS), and the SSSS may be referred to as a Sidelink Secondary Synchronization Signal (S-SSS). For example, length-127 M-sequences may be used for the S-PSS, and length-127 Gold sequences may be used for the S-SSS. For example, a terminal may detect an initial signal and acquire synchronization using the S-PSS. For example, a terminal may acquire detailed synchronization and detect a synchronization signal ID using the S-PSS and the S-SSS.

[0129] PSBCH (Physical Sidelink Broadcast Channel) may be a (broadcast) channel that transmits basic (system) information that a terminal must know first before transmitting or receiving an SL signal. For example, the basic information may be information related to SLSS, duplex mode (DM), TDD UL / DL (Time Division Duplex Uplink / Downlink) configuration, resource pool-related information, type of application related to SLSS, subframe offset, broadcast information, etc. For example, in NR V2X, for evaluating PSBCH performance, the payload size of PSBCH may be 56 bits, including a 24-bit CRC.

[0130] S-PSS, S-SSS and PSBCH may be included in a block format supporting periodic transmission (e.g., SL SS (Synchronization Signal) / PSBCH block, hereinafter referred to as S-SSB (Sidelink-Synchronization Signal Block)). The S-SSB may have the same numerology (i.e., SCS and CP length) as the PSCCH (Physical Sidelink Control Channel) / PSSCH (Physical Sidelink Shared Channel) in the carrier, and the transmission bandwidth may be within a (pre-)configured SL BWP (Sidelink BWP). For example, the bandwidth of the S-SSB may be 11 RBs (Resource Blocks). For example, the PSBCH may span 11 RBs. And, the frequency location of the S-SSB may be (pre-)configured. Therefore, the terminal does not need to perform hypothesis detection in the frequency to discover the S-SSB in the carrier.

[0131] Meanwhile, in the NR SL system, multiple numerologies having different SCS and / or CP lengths may be supported. In this case, as the SCS increases, the length of the time resource for a transmitting terminal to transmit an S-SSB may become shorter. Accordingly, the coverage of the S-SSB may decrease. Therefore, in order to ensure the coverage of the S-SSB, the transmitting terminal may transmit one or more S-SSBs to a receiving terminal within one S-SSB transmission period according to the SCS. For example, the number of S-SSBs that the transmitting terminal transmits to the receiving terminal within one S-SSB transmission period may be pre-configured or configured for the transmitting terminal. For example, the S-SSB transmission period may be 160 ms. For example, an S-SSB transmission period of 160 ms may be supported for all SCSs.

[0132] For example, when the SCS is 15 kHz at FR1, the transmitting terminal can transmit one or two S-SSBs to the receiving terminal within one S-SSB transmission period. For example, when the SCS is 30 kHz at FR1, the transmitting terminal can transmit one or two S-SSBs to the receiving terminal within one S-SSB transmission period. For example, when the SCS is 60 kHz at FR1, the transmitting terminal can transmit one, two, or four S-SSBs to the receiving terminal within one S-SSB transmission period.

[0133] For example, when the SCS is 60 kHz at FR2, the transmitting terminal can transmit 1, 2, 4, 8, 16, or 32 S-SSBs to the receiving terminal within one S-SSB transmission period. For example, when the SCS is 120 kHz at FR2, the transmitting terminal can transmit 1, 2, 4, 8, 16, 32, or 64 S-SSBs to the receiving terminal within one S-SSB transmission period.

[0134] Meanwhile, when the SCS is 60 kHz, two types of CP may be supported. In addition, the structure of the S-SSB transmitted by the transmitting terminal to the receiving terminal may be different depending on the CP type. For example, the CP type may be Normal CP (NCP) or Extended CP (ECP). Specifically, for example, when the CP type is NCP, the number of symbols to which the PSBCH is mapped within the S-SSB transmitted by the transmitting terminal may be 9 or 8. On the other hand, for example, when the CP type is ECP, the number of symbols to which the PSBCH is mapped within the S-SSB transmitted by the transmitting terminal may be 7 or 6. For example, the PSBCH may be mapped to the first symbol within the S-SSB transmitted by the transmitting terminal. For example, the receiving terminal receiving the S-SSB may perform an Automatic Gain Control (AGC) operation in the first symbol section of the S-SSB.

[0135] Figure 12 shows a terminal performing V2X or SL communication.

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

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

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

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

[0140] Figure 13 shows resource units for V2X or SL communication.

[0141] Referring to Figure 13, the entire frequency resources of the resource pool can be divided into NF units, and the entire time resources of the resource pool can be divided into NT units. Therefore, a total of NF * NT resource units can be defined within the resource pool. Figure 13 illustrates an example where the resource pool repeats with a cycle of NT subframes.

[0142] As illustrated in Figure 13, a single resource unit (e.g., Unit #0) may appear periodically and repeatedly. Alternatively, to achieve diversity effects in the time or frequency dimensions, the index of the physical resource unit to which a single logical resource unit is mapped may change in a predetermined pattern over time. In this resource unit structure, a resource pool may refer to a set of resource units that a terminal wishing to transmit an SL signal can use for transmission.

[0143] Resource pools can be subdivided into several categories. For example, based on the content of the SL signal transmitted from each resource pool, resource pools can be categorized as follows:

[0144] (1) Scheduling Assignment (SA) may be a signal that includes information such as the location of resources used by a transmitting terminal for transmission of an SL data channel, MCS (Modulation and Coding Scheme) or MIMO (Multiple Input Multiple Output) transmission method required for demodulation of other data channels, and TA (Timing Advance). SA may also be transmitted multiplexed with SL data on the same resource unit, in which case the SA resource pool may mean a resource pool in which SA is multiplexed with SL data and transmitted. SA may also be called an SL control channel.

[0145] (2) The SL data channel (Physical Sidelink Shared Channel, PSSCH) may be a resource pool used by a transmitting terminal to transmit user data. If SA is multiplexed and transmitted together with SL data on the same resource unit, only the SL data channel excluding SA information may be transmitted from the resource pool for the SL data channel. In other words, the REs (Resource Elements) that were used to transmit SA information on individual resource units within the SA resource pool may still be used to transmit SL data in the resource pool of the SL data channel. For example, the transmitting terminal may transmit the PSSCH by mapping it to consecutive PRBs.

[0146] (3) A discovery channel may be a resource pool for transmitting terminals to transmit information such as their IDs. Through this, transmitting terminals can enable neighboring terminals to discover them.

[0147] Even if the content of the SL signal described above is the same, different resource pools may be used depending on the transmission and reception properties of the SL signal. For example, even if it is the same SL data channel or discovery message, it may be again divided into different resource pools depending on the transmission timing determination method of the SL signal (for example, whether it is transmitted at the time of reception of a synchronization reference signal or whether it is transmitted by applying a certain timing advance at the time of reception), the resource allocation method (for example, whether the base station designates transmission resources for individual signals to individual transmitting terminals or whether individual transmitting terminals independently select individual signal transmission resources within the resource pool), the signal format (for example, the number of symbols each SL signal occupies in one subframe or the number of subframes used for transmission of one SL signal), the signal strength from the base station, the transmission power strength of the SL terminal, etc.

[0148] FIG. 14 illustrates an example of a BWP according to an embodiment of the present disclosure. The embodiment of FIG. 14 can be combined with various embodiments of the present disclosure. In the embodiment of FIG. 14, it is assumed that there are three BWPs.

[0149] Referring to Figure 14, a common resource block (CRB) may be a carrier resource block numbered from one end of a carrier band to the other. Furthermore, a PRB may be a numbered resource block within each BWP. Point A may indicate a common reference point for the resource block grid.

[0150] The BWP can be set by Point A, an offset from Point A (NstartBWP), and a bandwidth (NsizeBWP). For example, Point A can be an outer reference point of a PRB of a carrier where subcarrier 0 of all numerologies (e.g., all numerologies supported by the network on that carrier) are aligned. For example, the offset can be the PRB spacing between the lowest subcarrier in a given numerology and Point A. For example, the bandwidth can be the number of PRBs in a given numerology.

[0151] SLSS (Sidelink Synchronization Signal) is a SL (sidelink) specific sequence and may include PSSS (Primary Sidelink Synchronization Signal) and SSSS (Secondary Sidelink Synchronization Signal). The PSSS may be referred to as S-PSS (Sidelink Primary Synchronization Signal) and the SSSS may be referred to as S-SSS (Sidelink Secondary Synchronization Signal). For example, length-127 M-sequences may be used for S-PSS and length-127 Gold sequences may be used for S-SSS. For example, a terminal may detect an initial signal (signal detection) and obtain synchronization using S-PSS. For example, the terminal can obtain detailed synchronization using S-PSS and S-SSS and detect a synchronization signal ID.

[0152] PSBCH (Physical Sidelink Broadcast Channel) may be a (broadcast) channel that transmits basic (system) information that a terminal must know first before transmitting or receiving an SL signal. For example, the basic information may be information related to SLSS, duplex mode (DM), TDD UL / DL (Time Division Duplex Uplink / Downlink) configuration, resource pool-related information, type of application related to SLSS, subframe offset, broadcast information, etc. For example, in NR V2X, for evaluating PSBCH performance, the payload size of PSBCH may be 56 bits, including a 24-bit CRC (Cyclic Redundancy Check).

[0153] S-PSS, S-SSS and PSBCH may be included in a block format supporting periodic transmission (e.g., SL SS (Synchronization Signal) / PSBCH block, hereinafter referred to as S-SSB (Sidelink-Synchronization Signal Block)). The S-SSB may have the same numerology (i.e., SCS and CP length) as the PSCCH (Physical Sidelink Control Channel) / PSSCH (Physical Sidelink Shared Channel) in the carrier, and the transmission bandwidth may be within a (pre-)configured SL BWP (Sidelink BWP). For example, the bandwidth of the S-SSB may be 11 RBs (Resource Blocks). For example, the PSBCH may span 11 RBs. And, the frequency location of the S-SSB may be (pre-)configured. Therefore, the terminal does not need to perform hypothesis detection in the frequency to discover the S-SSB in the carrier.

[0154] FIG. 15 illustrates a procedure for a terminal to perform V2X or SL communication according to a resource allocation mode, according to one embodiment of the present disclosure. The embodiment of FIG. 15 may be combined with various embodiments of the present disclosure.

[0155] Referring to (a) of FIG. 15, in resource allocation mode 1, the base station may schedule SL resources to be used by the terminal for SL transmission. For example, in step S1500, the base station may transmit information related to SL resources and / or information related to UL resources to the first terminal. For example, the UL resources may include PUCCH resources and / or PUSCH resources. For example, the UL resources may be resources for reporting SL HARQ feedback to the base station.

[0156] For example, a first terminal may receive information related to a dynamic grant (DG) resource and / or information related to a configured grant (CG) resource from a base station. For example, a CG resource may include a CG type 1 resource or a CG type 2 resource. In this specification, a DG resource may be a resource that a base station configures / allocates to the first terminal via downlink control information (DCI). In this specification, a CG resource may be a (periodic) resource that a base station configures / allocates to the first terminal via DCI and / or an RRC message. For example, in the case of a CG type 1 resource, the base station may transmit an RRC message including information related to the CG resource to the first terminal. For example, in the case of a CG type 2 resource, the base station may transmit an RRC message including information related to the CG resource to the first terminal, and the base station may transmit a DCI related to activation or release of the CG resource to the first terminal.

[0157] In step S1510, the first terminal may transmit a PSCCH (e.g., Sidelink Control Information (SCI) or 1st-stage SCI) to the second terminal based on the resource scheduling. In step S1520, the first terminal may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal. In step S1530, the first terminal may receive a PSFCH related to the PSCCH / PSSCH from the second terminal. For example, HARQ feedback information (e.g., NACK information or ACK information) may be received from the second terminal via the PSFCH. In step S1540, the first terminal may transmit / report HARQ feedback information to the base station via a PUCCH or a PUSCH. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on the HARQ feedback information received from the second terminal. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on a rule set in advance. For example, the DCI may be DCI for scheduling SL.

[0158] Referring to (b) of FIG. 15, in resource allocation mode 2, a terminal can determine SL transmission resources within SL resources set by a base station / network or preset SL resources. For example, the set SL resources or preset SL resources may be a resource pool. For example, the terminal can autonomously select or schedule resources for SL transmission. For example, the terminal can perform SL communication by selecting resources by itself within the set resource pool. For example, the terminal can select resources by itself within a selection window by performing sensing and resource (re)selection procedures. For example, the sensing can be performed on a subchannel basis. For example, in step S1510, a first terminal that has selected resources by itself within a resource pool can transmit a PSCCH (e.g., Sidelink Control Information (SCI) or 1st-stage SCI) to a second terminal using the resources. In step S1520, the first terminal may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal. In step S1530, the first terminal may receive a PSFCH related to the PSCCH / PSSCH from the second terminal.

[0159] Referring to (a) or (b) of FIG. 15, for example, a first terminal may transmit an SCI to a second terminal on a PSCCH. Or, for example, the first terminal may transmit two consecutive SCIs (e.g., 2-stage SCIs) to the second terminal on the PSCCH and / or the PSSCH. In this case, the second terminal may decode the two consecutive SCIs (e.g., 2-stage SCIs) to receive the PSSCH from the first terminal. In this specification, an SCI transmitted on a PSCCH may be referred to as a 1st SCI, a 1st SCI, a 1st-stage SCI, or a 1st-stage SCI format, and an SCI transmitted on a PSSCH may be referred to as a 2nd SCI, a 2nd SCI, a 2nd-stage SCI, or a 2nd-stage SCI format.

[0160] Referring to (a) or (b) of FIG. 15, in step S1530, the first terminal may receive a PSFCH. For example, the first terminal and the second terminal may determine PSFCH resources, and the second terminal may use the PSFCH resources to transmit HARQ feedback to the first terminal.

[0161] Referring to (a) of FIG. 15, in step S1540, the first terminal may transmit SL HARQ feedback to the base station via PUCCH and / or PUSCH.

[0162] Meanwhile, the aforementioned sidelink can be defined as terminal-to-terminal communication or direct communication between terminals. In this case, the PSCCH can be defined as a physical control channel for terminal-to-terminal communication, the PSSCH as a physical data channel or physical shared channel for terminal-to-terminal communication, and the PSFCH as a physical feedback transmission channel between terminals.

[0163] Meanwhile, the SoftV2X service or SoftV2X system is a system in which a SoftV2X server receives a VRU message or a PSM (Personal Safety Message) from a VRU (Vulnerable Road User) or a V2X vehicle through a UU interface for V2X communication, and transmits information on surrounding VRUs or vehicles based on the VRU message or PSM message, or analyzes the road conditions on which surrounding VRUs or vehicles are moving, and transmits a message to notify surrounding VRUs or vehicles of a collision warning based on the analyzed information. Here, the VRU message or PSM message is a message transmitted to the SoftV2X server through the UU interface, and may include mobility information on the VRU, such as the location, moving direction, moving path, and speed of the VRU. In other words, the SoftV2X system receives mobility information on VRUs and / or vehicles related to V2X communication through the UU interface, and the softV2X server, such as a network, controls the driving path of the VRU, the VRU movement flow, etc. based on the received mobility information. Alternatively, the SoftV2X system can be configured in relation to V2N communications.

[0164] Below, we describe in detail how a network can provide V2X services based on a message protocol.

[0165] MQTT / AMQP protocol

[0166] Figure 16 is a diagram for explaining the AMQP protocol for transmitting V2N messages, and Figure 17 is a diagram for explaining the MQTT protocol for transmitting V2N messages.

[0167] Referring to Figure 16 (a), the AMQP protocol can be a message protocol that operates as a composition of a publisher, a broker, and a subscriber. The AMQP 1.0 protocol is an open standard protocol for asynchronous message transmission. This protocol standardizes communication between message-oriented middleware and clients, and can provide a high level of reliability, security, and interoperability. AMQP supports message orientation, queuing, routing (point-to-point, publish / subscribe), reliable, and secure transmission. It is widely used in various enterprise messaging applications. The AMQP 1.0 protocol message format is a binary protocol, enabling efficient message processing. The message structure consists of several parts, such as a header, properties, and a body, to support complex communication requirements.

[0168] Meanwhile, C-Road leverages AMQP 1.0 in the transportation and mobility fields to achieve reliable data exchange. They leverage AMQP's extensible and flexible framework for communication between various transportation management systems and devices. Referring to Figure 16 (b), the AMQP protocol format can consist of header, delivery-annotations, message-annotations, properties, application properties, application data, and footer fields. Here, C-Road's application properties can provide metadata describing the message content. Application properties contain information necessary for the receiver to interpret and appropriately process the message, thereby improving the efficiency and accuracy of communication. Furthermore, providing metadata through application properties can play a crucial role in ensuring that messages reach their intended destinations appropriately.

[0169] The MQTT protocol features lightweight network traffic and low bandwidth requirements, making it suitable for resource-constrained environments such as IoT devices and mobile applications. The MQTT protocol is based on a publish / subscribe model, enabling efficient message delivery and ensuring secure message delivery even in unstable network environments. The MQTT protocol is being adopted by various IoT platforms and V2N services due to its simple implementation and lightweight protocol structure, which facilitates widespread adoption.

[0170] Referring to Fig. 17 (a), the MQTT protocol may be a message protocol structured to operate with a publisher (or client), a broker, and a subscriber (or client). Here, subscription and publication of messages may be performed based on topics. For example, a subscriber may receive only messages corresponding to its requested topic from the broker, and a publisher may transmit a message to the broker with a topic set to specify the target to receive its message. For example, a broker may filter messages to be published to subscribers based on topics.

[0171] Referring to Fig. 17 (b), the MQTT protocol format can be composed of a fixed header, a variable header, and a payload. Referring to Fig. 17 (c), the fixed header of the MQTT protocol can always be included in all MQTT messages and contains message type and message length information. The variable header is optional and can contain different information depending on the message type. The payload contains the actual message data and can be defined according to the message type. The fixed header included in the MQTT control packet can define essential information including the packet type. This is because the 4th to 7th bits of the first byte of the packet define various MQTT states from CONNECT to DISCONNECT. Flags that provide additional information and functions can be set differently depending on the specific control packet type and can play a role in controlling the operation of the packet in detail. Remaining Length can tell you the total length of the control packet, including the variable header and payload.

[0172] The variable header includes a packet identifier and a property length, and the information allocated through these can play a significant role in the processing and routing of the message. In this regard, the MQTT 5.0 standard added a new section that allows user-defined properties (User Properties) to be included in the variable header. The User Properties can allow users to include additional information in the message. For example, a sender can define additional information for specific purposes or management from a service perspective. The User Properties are a way to exchange user-defined data between a client and a server, and can be defined multiple times for various information in a single message. The MQTT standard states that User Properties are not limited and are maintained universally, but can be extended as needed by users. Additionally, control packets of various states, such as CONNECT, CONNACK, PUBLISH, Will Properties, PUBACK, PUBREC, PUBREL, PUBCOMP, SUBSCRIBE, SUBACK, UNSUBSCRIBE, UNSUBACK, DISCONNECT, and AUTH, may contain user properties. These properties must be composed of UTF-8 (Unicode Transformation Format - 8-bit) character string pairs, and can be expressed in the form of Key and Value.

[0173] Below, we will explain in detail the data publication / subscription cycle principle of the server / client based on the MQTT protocol.

[0174] A scenario where all clients in a specific road area simultaneously publish (publish) and subscribe (subscribe) using the MQTT protocol can be implemented as follows. This scenario allows vehicles on the road within a given geographic area to exchange data and interact in real time.

[0175] (1) Preparation stage

[0176] 1) Client Registration and Authentication: Each vehicle must go through a proper authentication process before connecting to the MQTT broker. This ensures that the vehicle only allows data to be sent and received from trusted sources.

[0177] 2) Discovery Phase: This phase identifies the geographic region in which the client is located, based on geographic location information defined by the operator. The client can receive data corresponding to a specific road region. During the discovery phase, the broker or server can provide the client with topic information related to a message protocol (e.g., MQTT protocol).

[0178] 3) Topic Structure Design: Each vehicle or infrastructure can publish and subscribe to specific topics. Topics can be categorized as road / area1 / traffic, road / area2 / safety, etc. For example, MQTT clients in a specific region can simultaneously publish and subscribe to messages through topics specific to that region.

[0179] (2) Publishing / subscribing to messages

[0180] 1) Message Publication: A client (or client device or vehicle) can publish messages based on MQTT topics, periodically or when specific events occur, such as road conditions, its own status, or emergency messages. For example, a client can establish a session with the server or broker through authentication and discovery procedures. Using the established session, the client can publish messages based on a specific topic (or a topic selected / configured based on the client's location in the topic information).

[0181] 2) Message Reception: A client (or vehicle, V2N device) can subscribe to messages published by other vehicles / clients or infrastructure to receive real-time information updates. For example, a client can subscribe to messages based on a specific topic (or a topic selected / configured based on the client's location in the topic information).

[0182] 3) Data Processing: The received data can be processed on the screen of the app, the vehicle's HMI (Human Machine Interface), navigation system, safety system, or driver assistance system and delivered to the driver / user or appropriate feedback can be provided.

[0183] (3) Geocasting

[0184] Geocasting is a technology that transmits data based on a specific geographic area. Geocasting plays a crucial role in location-based services (LBS) and network communications, and can be used in a variety of applications. By transmitting data to devices or users within a specific geographic area, geocasting can provide more efficient and relevant information.

[0185] Geocasting is widely used in location-based services thanks to advancements in smartphones and GPS technology. This technology allows for more accurate and relevant services by transmitting data only to users within a specific geographic area.

[0186] A prime example is V2X (Vehicle-to-Everything) services, which may require communication between vehicles (V2V), vehicles and infrastructure (V2I), and vehicles and pedestrians (V2P). In these communications, it can be crucial to effectively manage and transmit events that occur only within a specific geographic area. Geocasting can be an ideal way to meet this need.

[0187] Geocasting can improve network efficiency by filtering data based on geographic criteria, rather than randomly transmitting data, thereby transmitting and receiving only data relevant to a specific geographic area. This can reduce network traffic, minimize data transmission delays, and utilize network resources more efficiently.

[0188] Quadtree and Geohash are two methods for dividing geographic space in V2X geocasting. These two methods can be used to efficiently divide and manage specific geographic areas, and are described in detail below.

[0189] How to segment space / section for geocasting

[0190] FIG. 18 and FIG. 19 are diagrams illustrating a method of dividing a geographic space into a plurality of cells or a plurality of geographic areas.

[0191] (1) Quadtree

[0192] Referring to Figures 18 (a) and (b), a Quadtree may be a tree data structure for dividing and exploring a two-dimensional space. A Quadtree may recursively divide the Earth into four equal rectangular regions, each parent node having four child nodes.

[0193] A quadtree cell (or quadtree-based cell region) can be structured in the following ways:

[0194] 1) Defining the entire space: The entire space is defined by latitude and longitude ranges, and each cell can be divided into four equal rectangular areas. This division process can be repeated until the desired level of geocasting is reached.

[0195] 2) Cell identifier: Each cell is identified by a binary string. For example, the string is divided into four cells of "0", "1", "2", and "3" at level 1, and can be further subdivided using more bits as the level increases. Typically, the most ideal range for geocasting when providing V2X services is 18 levels, from which the following location areas (cells) can be derived. For example, the identifier for a cell or cell area of ​​Yongsan Station in Yongsan-gu, Seoul can be calculated as follows.

[0196] - Latitude range: 180 degrees / 2^18 0.0006866455 degrees

[0197] - Longitude range: 360 degrees / 2^18 0.0013732910 degrees

[0198] - Cell ID (e.g., Yongsan Station cell identifier): 111010111001010110

[0199] (2) Geohash

[0200] Geohashing is a method for managing and retrieving spatial data by encoding geographic locations into unique strings.

[0201] Referring to Figure 19, a geohash can be expressed as a string by converting latitude and longitude values ​​to binary and then interleaving them, using Base32 encoding. This can be done by dividing the Earth into increasingly smaller cells, such as halving a range, and then converting the values ​​corresponding to each of these two ranges to binary. After converting the latitude and longitude for a specific location to binary, they can be interleaved and converted to binary alternately. Finally, these binary values ​​can be converted to a string using Base32 encoding.

[0202] For example, the Geohash of Gwanghwamun, Seoul can be calculated as follows.

[0203] - Latitude: 10110011101001001110 Longitude: 11101001010010001100

[0204] - Convert to Base 32 = wydhvn4r3k3j

[0205] Uu-based V2N services use MQTT to share current location information and exchange data with surrounding road users, aiming to provide safe driving services. At this time, communication zones can be identified using the quadtree or geohash methods described above, as criteria for defining specific areas. For example, communication between a V2N (Vehicle-to-Network) server and client terminals can utilize geocasting, which utilizes tile / cell area information.

[0206] In quadtree-based geocasting, each client or client device (hereinafter, “client”) can set the quadtree ID corresponding to its current location as an MQTT topic. For example, if the quadtree ID of a specific tile is “111010111001010110”, the client can subscribe to a topic defined as “v2n / 111010111001010110” and publish data. The client can subscribe to the topic of the tile it belongs to and publish messages containing current location and status information based on the topic. For example, if vehicle A and vehicle B are located in the same tile “111010111001010110”, the two vehicles can publish / subscribe to the topic defined as “v2n / 111010111001010110” to exchange each other’s location and status information in real time (via the network).

[0207] In geohash-based geocasting, a client can set the value of the geohash corresponding to its current location as an MQTT topic. For example, if the geohash of a specific location is "wx4g0b0", a client located at that specific location can subscribe to a topic defined in the format "v2n / wx4g0b0" and publish data / messages. A client can subscribe to the topic of the geohash cell it belongs to and publish messages containing its current location and status information using the topic. For example, if vehicle A and vehicle B are located in the same geohash cell "wx4g0b0", the two vehicles can subscribe to the topic defined as "v2n / wx4g0b0" to exchange each other's location and status information in real time (over the network).

[0208] (3) Node / link method

[0209] The node / link approach can be a method for simply representing and managing complex road structures through intersections (nodes) and road sections (links), which are the basic units that make up a road network. For example, the node / link approach can define road junctions and confluences as nodes, and the road sections between nodes as links. It can be designed to spatially organize the entire road network and efficiently manage traffic flow. For example, the node / link approach can represent and define a road section as a single link connecting two nodes, using information about the two nodes associated with the road section.

[0210] A unique identifier may be assigned / defined for at least one of the nodes and links described above, and such unique identifier can be used to accurately identify a specific point or section within a road network. For example, the unique identifier typically consists of a district number, serial number, extension, etc., and in some cases, may include a subdivision number for each lane / road. For example, the unique identifier for a node / link may be defined as shown in Table 5.

[0211] Area number Serial number (road) Extension Horizontal Longitudinal 110001010102

[0212] The node / link approach provides an intuitive representation of road networks, and it allows for the systematic management of intersections and road segments. However, in complex road environments, link and node management can be challenging, and in fragmented areas, the identifier system can become complex. Furthermore, when providing V2X services for traffic safety purposes, pedestrians do not use roads, so generating mobility information, etc., may be limited by the node / link or road segment-based approach compared to the cell area (or tile / cell)-based approach.

[0213] For example, when converting between node / link mode (or road segment period mode) and cell mode, the following issues may exist.

[0214] Because the node / link approach is designed to focus on road networks, it may not be suitable for including / representing mobility information outside of the road (e.g., pedestrian paths, crosswalks, sidewalks, etc.). For example, pedestrians do not walk on roads but primarily move on sidewalks or crosswalks, so the node / link approach described above may not adequately represent movement paths and other information.

[0215] Vulnerable Road Users (VRUs), such as pedestrians and bicycles, may move in different patterns than vehicles on the road. These user movement patterns are difficult to represent using node / link or road segment methods, and cell area / tile-based spatial representation methods (e.g., Geohash, Quadtree) may be more appropriate. Furthermore, while the node / link method is effective for communication between vehicles on the road, it may have limitations for V2X services, including interactions with users / pedestrians described above.

[0216] V2X services may be offered in a hybrid form, utilizing both tile / cell area-based topics and node / link (or road segment)-based topics for vehicle-pedestrian interaction. For example, a specific service provider may be configured to utilize both road segment-based topics (or node / link-based topics) and cell area-based topics for message publishing / subscription.

[0217] And / or, as will be described later, when the geocasting methods are different between different service providers, the V2X system / V2X service can be designed so that the data / messages that are geocasted can be shared between different service providers through the conversion method described later.

[0218] For example, when a specific road section based on nodes / links needs to be converted into a cell area (e.g., a cell area based on the geohash method or a cell area based on the quadtree method), the following issues may be considered.

[0219] - In the case of a straight section, cell areas including a single link (or, straight section) connecting two nodes can be converted into cell areas corresponding to the two nodes. In this case, messages / data related to the road section / straight section connecting the two nodes can be transmitted / published / geocasted to terminals / client devices that have / defined / set subscription topics for the cell areas. However, if an actual curved road section is defined / represented as a single link based on a node / link-based representation method, it may be difficult to recognize / identify whether the single link is a curve. For example, in a node / link-based representation method, only the locations of two nodes for the single link can be known, and it may be difficult to determine whether the road section of the single link is a curve. Therefore, a method needs to be proposed for converting such curved road sections into cell areas according to a quadtree or geohash method.

[0220] In the following, the method of converting between cell areas according to the quadtree method and cell areas according to the geohash method is explained first, and then the method of converting a road section / single link according to the node / link method into a cell area according to the quadtree method (or a quadtree-based cell area) or a cell area according to the geohash method (or a geohash-based cell area) is explained in detail.

[0221] Meanwhile, the conversion between cell areas described below, and / or the conversion between road sections (or single links) and cell areas according to the node / link method, can be applied not only between heterogeneous operators / service providers, but also between brokers serving the same operator / service provider. For example, cell areas can be defined in different ways even between brokers serving the same service provider, and in this case, the conversion between cell areas described below, and / or the conversion between road sections (or single links) and cell areas according to the node / link method, can naturally be applied.

[0222] Figure 20 is a diagram illustrating a method for exchanging messages between heterogeneous service providers.

[0223] Referring to FIG. 20, a first server (or first broker) of a first service provider (or first SP) and a second server (or second broker) of a second service provider (or second SP) are interconnected through an interchange and can exchange messages / data with each other. At this time, one of the first and second service providers can define a topic using a geohash method, and the other can define a topic using a quadtree method. For example, the first service provider (first SP) can use a topic defined using a quadtree method, and the second service provider (second SP) can use a topic defined using a geohash method.

[0224] Thus, when exchanging data between heterogeneous operators (heterogeneous service providers performing quadtree and geohash-based geocasting), the following problems may arise due to different topic definition methods for geocasting.

[0225] - Differences in cell structure: Quadtrees and geohashes differ in how they partition geographic space. Quadtrees recursively divide space into square cells, while geohashes may convert latitude and longitude into binary numbers and cross-concatenate them to create rectangular cells. This can lead to differences in cell sizes and boundaries between the two methods, even when representing the same location.

[0226] - Differences in topic definition methods: Quadtree-based geocasting uses quadtree cell IDs as topics. For example, topics in quadtree-based geocasting can be defined as a bit string, such as "v2n / 111010111001010110". In contrast, geohash-based geocasting can define / use topics based on geohash strings. For example, topics in geohash-based geocasting can be defined as a string, such as "v2n / wx4g0b0". As such, since the two methods define topics differently, direct mapping between them can be difficult.

[0227] - Data Exchange Failure: Since the boundaries of quadtree and geohash cells (or quadtree-based cell areas and geohash-based cell areas) do not match, data exchange may not occur due to subscriptions to different topics. For example, a terminal using a topic like "111010111001010110" based on the quadtree cell ID and a terminal using a topic like "wx4g0b0" based on the geohash method may have difficulty exchanging data / messages due to the different topics, even if they are located in the same area.

[0228] Unnecessary data transmission: Even if data is transmitted in relation to two regions, the different cell sizes may include unnecessary data ranges. This increases network load and reduces data processing efficiency. The process of converting cell boundaries between quadtrees and geohashes can make it difficult to accurately map cell areas, resulting in redundancy, where data is received that is not needed in each UI / UX.

[0229] Thus, data exchange issues between service providers (or operators) using quadtree and geohash-based geocasting stem from differences in cell area structures and topic definition formats. This can lead to terminals in the same geographic location subscribing to different topics, hindering smooth data exchange and potentially resulting in unnecessary data transfer and complex conversion logic. Below, we detail how to resolve these issues by using a common spatial indexing method at an intermediate conversion server (each server or interchange) or bridge to convert between topics defined in different ways.

[0230] Implementing real-time conversion and interoperability between road sections and cell areas, and between cell areas.

[0231] Figures 21 and 22 are diagrams illustrating a method for converting between topics based on a quadtree and topics based on a geohash.

[0232] Below, the method of converting between cell areas according to quadtree and cell areas according to geohash is described in detail by dividing into Method 1 and Method 2, and the method of converting a single link / road section according to the node / link method into a cell area is described in detail in Method 3.

[0233] 1. Method 1: Quadtree-to-Geohash Conversion Method

[0234] The latitude / longitude of the center point of the cell area corresponding to the quadtree or geohash can be used as a basis for conversion to the corresponding level of the cell area to be converted.

[0235] First, the latitude and longitude of the center point of the quadtree cell area can be calculated. Based on the quadtree, the cell area size and the corresponding number of characters in the geohash can be found according to the cell level. Information on the number of characters in the geohash can also be received during the discovery phase.

[0236] For example, referring to FIG. 21, the coordinates corresponding to the latitude and longitude of the center point of a quadtree cell area can be determined, and converted into a value corresponding to the number of characters for the geohash cell area to which the determined coordinates belong. The characters / string of the geohash cell area thus converted can be set as an MQTT topic, and can be published toward the broker / server of the business operator / service provider receiving the MQTT topic. This process can also be applied to a method of converting from a geohash-based topic to a quadtree-based topic. For example, the center point of a cell according to a geohash can be converted into a cell area according to a quadtree and processed in the same manner.

[0237] Method 1 is a method of converting between a quadtree cell area and a geohash cell area by calculating the latitude and longitude of the center point of the cell area and finding the relative cell area corresponding to the coordinates. For example, after calculating the latitude and longitude of the center point of the quadtree cell, it is converted into a geohash cell area corresponding to the latitude and longitude, and data / message is published using an MQTT topic defined based on the ID of the geohash cell area. Conversely, it is also possible to convert the center point of a geohash cell area into a quadtree cell area. For example, a server / broker of a service provider can specify a cell area ID of a quadtree corresponding to the publication topic of data / message published from a client device or data / message transmitted from a server / broker of another service provider, calculate the latitude and longitude of the center point of the cell area corresponding to the cell area ID of the quadtree, determine a cell area ID of a geohash corresponding to the calculated latitude / longitude, and determine a conversion topic defined by the geohash cell ID. In this case, the service provider's server / broker can publish the received / transmitted message / data using the above-mentioned conversion topic. Meanwhile, as described above, the quadtree / geohash-based cell area can also be defined as a quadtree / geohash-based cell.

[0238] As described above, Method 1 may be a method of converting between quadtree and geohash based on the center point of the cell area according to a specific method (e.g., the quadtree method or the geohash method used to define the publication topic of the received message / data). For example, in Method 1, the server / broker of the service provider may convert the cell area according to the quadtree method into the cell area according to the geohash method based on the center point of the cell area according to the quadtree method used to define the first publication topic of the received message / data, and may define a second publication topic for relaying the message / data based on the cell area according to the geohash method. For example, Method 1 may be a method of converting the first publication topic of the received message / data into the second publication topic for relaying the message / data through cell area conversion between the quadtree method or the geohash method. Method 1 may be performed through the following procedure. In the following, for convenience of explanation, it is assumed that the service provider's server / broker has received a message / data published to the first publication topic defined based on the quadtree cell.

[0239] (1) Calculation of the center point of the cell area based on the quadtree

[0240] The service provider's server / broker can calculate the center point (e.g., latitude and longitude values ​​of the quadtree cell area) of a given quadtree cell area (e.g., the quadtree cell area corresponding to the first published topic). Here, since the quadtree cell area is square, the service provider's server / broker can calculate the center point by calculating the midpoint between the south and north boundaries and the midpoint between the west and east boundaries of the quadtree cell area.

[0241] When the server / broker of the service provider converts the center point of the quadtree cell area into a geohash cell area, the server / broker of the service provider needs to select the number of characters / string length of the geohash cell area corresponding to the center point of the quadtree cell area. Generally, the number of characters / string length of an appropriate geohash cell area can be selected according to the level of the quadtree cell area. For example, as illustrated in FIG. 21, the quadtree cell area of ​​level 18 may be approximately 75m x 75m, the geohash cell area of ​​level 7 may be approximately 153m x 153m, and the geohash cell area of ​​level 8 may be approximately 39m x 39m. In this case, the server / broker of the service provider may select the number of characters / string length of the geohash cell area of ​​level 7 as the number of characters / string length of the geohash cell area corresponding to the quadtree cell area of ​​level 18.

[0242] (2) Set / convert the ID of the geohash cell to an MQTT topic

[0243] The service provider's server / broker can define / set up an MQTT topic based on the ID of the geohash cell area (e.g., "wx4g0b"), if the service provider's server / broker determines the ID of the geohash cell corresponding to the quadtree cell area ID (e.g., "wx4g0b"). Such an MQTT topic can be used to specify the location / geographic area where the service provider's server / broker will deliver data / message to the recipient.

[0244] (3) Publishing messages / data (or publishing to MQTT broker)

[0245] The service provider's server / broker can publish data / messages to recipients using an MQTT topic defined / configured with the ID of the converted geohash cell area. Conversely, converting the center point of a geohash cell area into a quadtree cell area can be handled in the same manner as described above.

[0246] (4) Example

[0247] As an example, a scenario can be considered in which a specific quadtree cell area in Yongsan-gu, Seoul is converted into a geohash cell area and data is issued.

[0248] 1) Quadtree cell area ID: 111010111001010110 (level 18), this cell area can represent a specific area within Yongsan-gu, Seoul.

[0249] 2) Calculating the center point of the quadtree cell area:

[0250] - Latitude range of cell area at quadtree level 18: 180 degrees / 2^18 0.0006866455 degrees

[0251] - Longitude range of cell area at quadtree level 18: 360 degrees / 2^18 0.0013732910 degrees

[0252] - Calculate the boundaries of the quadtree cell area and find its center point. The center point can be calculated as latitude 37.529945 degrees and longitude 126.964636 degrees.

[0253] 3) Convert to geohash cell area:

[0254] The quadtree cell area can be converted to a geohash cell area using the derived center point latitude (37.529945) and longitude (126.964636). When converted to geohash length / level 7 (approximately 153m x 153m), the geohash cell area ID corresponding to the derived center point latitude (37.529945) and longitude (126.964636) can be determined / specified as wx4g0b0. For example, the service provider's server / broker can convert the quadtree cell area ID of 111010111001010110 to the geohash cell area ID of wx4g0b0.

[0255] 4) Set / define the ID of the geohash cell area as an MQTT topic

[0256] The service provider's server / broker can define / configure an MQTT topic based on the geohash cell area ID, wx4g0b0. The service provider's server / broker can publish data / messages using the MQTT topic of wx4g0b0. For example, the MQTT topic can be defined as "v2n / wx4g0b0."

[0257] For example, a server / broker of a service provider may receive a first message / data published to a first topic defined based on a quadtree cell region ID of 111010111001010110 from its client. The server / broker of the service provider may forward / relay the first message / data to a server / broker of another service provider, where the topic is defined based on a geohash cell region. In this case, the server / broker of the service provider may convert the quadtree cell region ID of 111010111001010110 to the ID of the corresponding geohash cell of wx4g0b0, and relay / publish the first message / data to the server / broker of another service provider using the topic defined based on the ID of the geohash cell region of wx4g0b0.

[0258] Method 1 can be advantageous in situations where real-time processing and easy implementation are crucial. Method 1 can be particularly effective for real-time location-based services that require rapid response, as it can quickly and efficiently map geohash cell areas to quadtree cell areas through a single center-based transformation.

[0259] 2. Method 2

[0260] Method 2 may be a method of constructing a database through the range of cell areas between quadtree-geohash, and publishing data by converting the topic defined for each geocast into a topic of the cell area of ​​the overlapping area.

[0261] As a method for calculating overlapping areas, levels can be identified in advance during the topic or service discovery process. This narrows the scope, speeds up calculations, and simplifies the database. The specific method is as follows.

[0262] - Cell Area Boundary Calculation: The boundaries of each cell area of ​​a quadtree and geohash can be calculated. By defining the latitude and longitude ranges of each cell area, the boundary values ​​of the cell area can be calculated.

[0263] - Latitude overlap calculation: The latitude boundaries between cell areas of a quadtree and cell areas of a geohash can be compared. For example, the maximum value of the southern boundary and the minimum value of the northern boundary between the two cell areas can be compared. If there is an overlapping range between the maximum value of the southern boundary and the minimum value of the northern boundary between the two cell areas, the range can be considered a latitude overlap area.

[0264] - Longitude overlap calculation: The longitude boundaries of two cell areas (e.g., a cell area of ​​a quadtree and a cell area of ​​a geohash) can be compared. For example, the maximum value of the western boundary and the minimum value of the eastern boundary between the two cell areas can be compared. If there is an overlapping range between the maximum value of the western boundary and the minimum value of the eastern boundary between the two cell areas, the range can be considered a longitude overlap area.

[0265] - Overlapping area derivation: If both latitude overlapping area and longitude overlapping area exist between the cell area of ​​the quadtree and the cell area of ​​the geohash, the area can be defined as the area / cell area that overlaps between the cell area of ​​the quadtree and the cell area of ​​the geohash.

[0266] - Overlap ratio calculation: The overlap ratio between the cell regions of the quadtree and the cell regions of the geohash can be calculated by comparing the area of ​​the region between the cell regions of the quadtree and the cell regions of the geohash and the total area of ​​the two cell regions. This overlap ratio is a value indicating how much the two cell regions overlap, and can be stored in a look-up table, and the look-up table can be referenced in the conversion between the cell regions of the quadtree and the cell regions of the geohash. For example, the look-up table can be defined as in Table 6 below.

[0267] Quadtree Cell Area ID Geohash Cell Area ID Overlap Ratio 111010111001010110wx4g0b0.85 111010111001010110wx4g0c0.15

[0268] A lookup table that can be converted according to the size of the cell area of ​​each geocast can be configured to convert the topic value of the geocasting range to be converted. For example, the server / broker of the service provider can convert the topic between the quadtree and the geohash using a lookup table that pre-computes the adjacent cell area, overlapping area, and / or boundary when converting between the quadtree and the geohash. For example, the server / broker of the service provider can determine the cell area of ​​the geohash that is closest to / overlaps the cell area of ​​the quadtree based on the lookup table, and convert the topic defined corresponding to the cell area of ​​the quadtree to the topic defined corresponding to the cell area of ​​the determined geohash. For example, the server / broker of the service provider can publish a message / data to the server / broker of another service provider using a topic defined by the cell area ID of the geohash that overlaps the cell area ID of the quadtree. Alternatively, when a message / data published using a topic corresponding to a cell area ID of a quadtree is received, the service provider's server / broker can convert the topic into a topic defined by a cell area of ​​a geohash that overlaps the cell area ID of the quadtree and then relay / publish the message / data to clients.

[0269] When a service provider's server / broker uses a database-based lookup table (or mapping table), the service provider's server / broker can immediately look up / determine the overlapping opposite cell area ID for the cell area ID of the geohash or quadtree corresponding to the topic related to the incoming message / data in real time, and exchange the necessary data / messages using the topic defined based on the looked up / determined opposite cell area ID. This method can effectively map and exchange data using only the cell area ID even if the latitude and longitude values ​​of the client are not known. Meanwhile, the service provider's server / broker can also decide whether to convert a specific topic into one or more topics based on the overlapping ratio of the lookup table. For example, the service provider's server / broker can convert the publication topic of the message / data received from the client into a single topic corresponding to the geohash cell area ID that has the highest overlapping ratio with the quadtree cell area corresponding to the publication topic. Alternatively, the service provider's server / broker may, based on the lookup table, convert the published topic of the message / data received from the client into topics corresponding to all geohash cell area IDs that overlap with the quadtree cell area corresponding to the published topic. This conversion method may be selected based on the service provider's policy or determined based on the communication load / system load of the service provider's server / broker.

[0270] Method 2 described above is a method of performing conversion between quadtree and geohash using a pre-calculated lookup table. The range (i.e., boundary) of each geocasting cell area may be pre-calculated, and a lookup table capable of conversion may be configured based on this. The service provider's server / broker may determine / specify a relative cell area defined in another manner that is closest to the cell area defined in a specific manner to be converted (e.g., a quadtree cell area defined in a quadtree manner or a geohash cell area defined in a geohash manner) based on the lookup table, and may publish data / message using a topic defined based on the specified / determined relative cell area.

[0271] As described above, Method 2 can be a quadtree-to-geohash conversion method based on a lookup table. The boundaries and overlapping areas of each geocasting cell area are pre-calculated and stored in a database for reference during the conversion process.

[0272] (1) Calculating the boundaries of the quadtree cell area and the geohash cell area

[0273] Boundaries are calculated for each quadtree cell area and geohash cell area. Since quadtrees are composed of square cell areas, and geohashes are composed of rectangular cell areas, their boundaries may not perfectly match. For quadtree cell areas, the boundaries are calculated by dividing the latitude and longitude ranges by level. For geohash cell areas, the latitude and longitude ranges of the cell area are calculated based on the length of the corresponding geohash string.

[0274] (2) Calculation of overlapping area

[0275] The overlap area between each quadtree cell area and the geohash cell area is calculated. This step analyzes how the boundaries of the two cell areas intersect to find the overlapping area. To calculate the overlap area, the latitude and longitude boundary values ​​of the two cell areas are compared to determine the overlapping area. If there is an overlap, the percentage is calculated and the information is prepared to be stored in the lookup table.

[0276] (3) Create a lookup table

[0277] Based on the precomputed overlap area information, a lookup table is created to store mapping information between quadtree cell area IDs and geohash cell area IDs. This table is stored in the database for reference during conversion. The lookup table includes the quadtree cell area ID, geohash cell area ID (e.g., at least one geohash cell area ID that maps to a specific quadtree cell area ID), and an overlap ratio (optional).

[0278] (4) Data insertion and retrieval

[0279] The service provider's server / broker can store the generated lookup table in a database. This table is referenced when a real-time conversion request comes in, and the corresponding cell area ID can be looked up using the quadtree cell area ID or geohash cell area ID. The quadtree / geohash ID value can represent a topic string value. Based on the lookup table, the service provider's server / broker can query the cell area to determine which area the incoming data belongs to in real-time and publish the data to the corresponding cell area.

[0280] For example, referring to FIG. 22, there may be various overlapping possibilities between a quadtree cell area at level 18 and a geohash cell area with a string length of 7 characters. Various options may be considered for how data / messages are issued in each overlapping area.

[0281] For example, in the case of area A, data / message can be published using the topic corresponding to ID=10101010 as the maximum overlapping area. For example, the geohash cell area ID corresponding to area A is converted to the quadtree cell area ID of 10101010, and the message / data can be transmitted / published using the topic of V2N / 10101010 defined based on the quadtree cell area ID. The geohash cell area ID corresponding to area B can be converted to 10101011 and 10101000, and the message / data can be published / transmitted using both the 1-1 topic defined by 10101011 and the 1-2 topic defined by 10101000. The geohash cell area ID corresponding to area C can be converted to the quadtree cell area ID of 10101111, which is an inclusive relationship. The geohash cell area ID corresponding to the D area can be converted to the quadtree cell area ID of 10111100, which overlaps the most, or to all overlapping quadtree cell area IDs (10101111, 10101100, 10101000, and 10111100). In this case, the service provider's server / broker can configure / define an MQTT topic based on the converted quadtree cell area ID, and publish messages / data using the configured / defined MQTT topic.

[0282] Method 2, as described above, can be advantageous over Method 1 in situations requiring precise mapping and complex transformations. Method 2 can be particularly effective in situations where cell area transformations near cell area boundaries are critical, as it allows the service provider's server / broker to precisely calculate the overlap between cell areas using a lookup table, thereby improving data transmission accuracy.

[0283] 3. Method 3 - Conversion between road segments (or nodes / links) and cell areas

[0284] Figure 23 is a diagram for explaining a method of conversion between identification information for a road section and identification information for a cell area.

[0285] A straight section between nodes can be converted into a rectangular cell area, and information about the curvature range of the actual road section for the straight section can also be included. For example, a link can be separated at a point where the curvature of the road typically reaches 60-90 degrees. Therefore, a road / road section with a curvature of approximately 0-60 degrees can be defined as a single link. Taking this into account, a criterion / threshold of a certain / specific curvature can be set by reflecting the curvature between two nodes, and a rectangular area can be formed with a width calculated according to the criterion / threshold. In this case, a single link / road section between the two nodes can be converted into a cell area that includes or overlaps the rectangular area (e.g., a cell area according to a quadtree or geohash method). For example, a rectangular area can be set based on a road section with a curvature of 60 degrees for a link between two nodes, and the set rectangular area can be converted into a quadtree cell area or a geohash cell area (or, a quadtree cell or a geohash cell). For example, a link between two nodes can be converted into a quadtree cell area or a geohash cell area based on the rectangular area described above. Meanwhile, for the specificity of a rectangular area corresponding to a single link / road section between two nodes, the maximum curvature is exemplified as 60 degrees for convenience of explanation; however, it is not limited to 60 degrees and can be preset to various angles, such as 70 degrees, 10 degrees, or 20 degrees.

[0286] Specifically, while it is easy to convert straight paths / straight road segments into cell areas (Quadtree- or Geohash-based cell areas) in a node / link approach, converting curved paths / curved road segments into Quadtree- or Geohash-based cell areas can be complex. In particular, converting curved road segments into cell areas can present the following problems.

[0287] - When representing a curved road section as a single link (e.g., a link connecting two nodes), only information about the two nodes (A and B) can be provided, and it is not possible to determine whether the link between the two nodes is curved or straight. For example, in the node / link method, a single link is represented through two nodes (A and B), so it may be unclear whether the single link represents a curved road section or a straight road section between the two nodes.

[0288] - When a road segment / path is curved, it may be unclear how to define the cell area containing the road segment / path connecting two nodes.

[0289] To convert a curved road section between two nodes / links into a cell area, the following inference process may be required.

[0290] - In order to cover a road section with a curvature of up to 60 degrees, a deviation reflecting the curvature between points Node A and Node B can be calculated, and a bounding rectangular area sufficiently including the curved road section can be specified / determined based on the deviation. At least one cell area overlapping the rectangular area can be determined, and data / message can be transmitted based on the at least one cell area. For example, it can be assumed that the road can typically have a curvature of up to 60 degrees between points Node A and Node B. This can represent the maximum degree of curvature that the road deviates from a straight path between Node A and Node B. Meanwhile, the maximum curvature / maximum curvature angle can be preset differently for each business operator / service provider.

[0291] For example, a broker / server (or bridge) may receive a message / data including mobility information for a single link representing a curved road section in a node / link manner. The broker / server (or bridge) may, if the road section corresponding to the single link is a curved road section (if the message / data indicates that the road section is a curved road section or if the single link is assumed to be a curved road section), calculate a deviation between the single link and a curved road section (e.g., a curved road section having a preset maximum curvature) that may correspond to the single link based on a preset maximum curvature (e.g., 60 degrees) associated with the single link. The broker / server (or bridge) may, based on the deviation, specify / determine a rectangular area that may include (all) the curved road sections that may be associated with the single link. The broker / server (or bridge) may determine at least one geohash-based cell area or at least one quadtree-based cell area overlapping the rectangular area, and may geocast the received message / data using at least one topic (or publication topic) defined using identification information of the determined at least one geohash-based cell area or at least one quadtree-based cell area.

[0292] An example of this conversion method may be as follows. For convenience of explanation, the examples below assume that the road segment is represented by Node A and Node B according to the node / link method, and that the preset maximum curvature is 60 degrees.

[0293] - Deviation Calculation: The deviation for a single link (e.g., a link / straight road section connecting Node A and Node B) can be calculated based on the maximum curvature of 60 degrees. For example, as in the following mathematical expression 1, the deviation for the single link can be calculated using sin(60° / 2).

[0294] [Mathematical Formula 1]

[0295]

[0296] Here, d is the distance between nodes A and B, and the deviation may mean the maximum distance that a curved road section with a curvature angle of 60 deviates from a straight road path / link between nodes A and B.

[0297] - Determination / setting of rectangular area: A rectangle (bounding rectangular) can be set by reflecting the calculated deviation in the latitude direction based on a single link (or, straight road section) between nodes A and B. For example, the maximum latitude and minimum latitude according to the above-described deviation can be calculated based on the following mathematical expression 2. In addition, the horizontal length, vertical length, and / or area of ​​the rectangular area can be calculated based on the following mathematical expression 3. Here, latA may be the latitude of node A, lonA may be the longitude of node A, latB may be the latitude of node B, and lonB may be the longitude of node B.

[0298] [Equation 2]

[0299]

[0300] [Equation 3]

[0301]

[0302] In this way, a rectangular area corresponding to a single link between two nodes can be determined / set based on a preset maximum curvature.

[0303] For example, referring to FIG. 23, in order to cover a curved road section with a maximum curvature of 60 degrees, a deviation reflecting the curvature between Node A and Node B can be calculated, and the curved road section with the maximum curvature can be converted into a rectangular area based on the deviation. In this case, the broker / server can geocast V2X data / messages occurring in the road section (or single link) from Node A to Node B to cell / cell area 1, 2, 3, and 4 areas (quadtree-based cell areas corresponding to operator A) that overlap with the converted rectangular area sufficiently including the curved road section (with the maximum curvature). By the broker / server performing geocasting of V2X data / messages occurring in the road section (or single link) from Node A to Node B to the quadtree-based cell area, a smooth V2X interoperability service can be provided between the broker server and the broker / server of another operator / service provider using the node / link method.

[0304] As described above, the server / broker can perform / process the conversion task between the geohash-based cell area and the quadtree-based cell area in advance. For example, the server / broker can pre-configure a look-up table that maps the geohash-based cell area and the quadtree-based cell area corresponding to each of the node / link-based road segments / single links, and can determine / determine the geohash-based cell area and / or the quadtree-based cell area corresponding to the node / link-based road segment / single link without real-time conversion based on the look-up table. For example, when a client device requests the above-described conversion to the server / broker, the server / broker can immediately provide information on the geohash-based cell area and / or the quadtree-based cell area mapped to the road segment where the client device is located based on the look-up table (or the conversion information prepared in advance).

[0305] In this way, even if one system (service provider) uses different data representation methods, it can be represented in an appropriate data representation method depending on the device type. Or, even if two systems (or, heterogeneous service providers) use different data representation methods, the server / broker can act as a conversion pipeline in the middle to effectively support the exchange of data / messages between heterogeneous service providers / brokers that use different data representation methods. For example, when Company A or Service Provider A transmits data / message for a quadtree-based cell area to the server / broker, the server / broker can convert the quadtree-based cell area into a single link / road section of the node / link used by Company B / Service Provider B, thereby allowing the data / message to be transmitted to the client device of Company B / Service Provider B. The above-described method can also be applied when the server / broker provides messages / data of Company B / Service Provider B, which uses a single link / road section of the node / link, to the client device of Company A / Service Provider A. The above server / broker can effectively support the exchange / translation of data / messages between service providers / brokers using different geocasting methods, including a backend server or a specific module (bridge) connecting two servers (brokers).

[0306] Figure 24 is a drawing illustrating how the first device issues the second message.

[0307] The first device may be a first broker of a first service provider that relays messages between client devices based on the Message Queuing Telemetry Transport (MQTT) protocol or the Advanced Message Queuing Protocol (AMQP). The first service provider may provide a hybrid V2X service configured to support both publishing / subscribing messages using road segment-based topics (or node / link-based topics) and publishing / subscribing messages using cell area-based topics, as described above.

[0308] Specifically, referring to FIG. 24, a first device may receive a first message issued using first identification information related to a road section (S241). The first message may be a message (initially) issued from a vehicle-related device or a VRU device. The first identification information may include node / link-based identification information for specifying / identifying the road section. For example, the first identification information may include information about two nodes related to the road section, or may be a topic defined based on the two nodes.

[0309] Next, the first device can convert the road segment associated with the first identification information into a Quadtree-based cell area or a Geohash-based cell area (S243). As described in the section “Implementation of Real-Time Conversion and Interoperability Between Road Segments and Cell Areas and Between Cell Areas”, the first device can calculate a deviation between the road segment identified / specified by the first identification information and the curved road segment having the preset maximum curvature based on a preset maximum curvature, and can specify a geographic area corresponding to the road segment (e.g., a geographic area that can include the curved road segment having the maximum curvature) based on the calculated deviation, and can convert the road segment into at least one Quadtree-based cell area or at least one Geohash-based cell area overlapping the specified geographic area. In this case, the first device can define / determine second identification information corresponding to the first identification information based on the at least one Quadtree-based cell area or the at least one Geohash-based cell area. For example, the first device may define / determine an index value for the at least one quadtree-based cell area or a string for the at least one geohash-based cell area as the second identification information corresponding to the first identification information. Here, the first identification information may be a topic defined by the identification information of the road section according to the node / link method, and the second identification information may be a topic defined by an index value for the quadtree-based cell area or a string for the geohash-based cell area.

[0310] Meanwhile, whether or not to perform an operation of converting a road section related to the first identification information into the cell area may be determined based on the type of device that issued the first message. For example, if the first message is a message issued by a Vulnerable Road User (VRU) device such as a pedestrian or a bicycle, the first device may perform an operation of converting a road section related to the first identification information into the cell area and an operation of defining / determining second identification information based on the converted cell area. Conversely, if the first message is a message issued by a device related to a vehicle, the first device may not perform an operation of converting a road section related to the first identification information into the cell area and an operation of defining / determining second identification information based on the converted cell area.

[0311] Next, the first device can issue a second message to transmit the first message (S245). As described above, if the first message is a message issued by a Vulnerable Road User (VRU) device such as a pedestrian or a bicycle, the first device can issue the second message using the second identification information. In this case, the second message can be geocasted to client devices located in a cell area corresponding to the second identification information. Alternatively, if the first message is a message issued by a device related to a vehicle, the first device can issue the second message using the first identification information. In this case, the second message can be geocasted to client devices located in a road section corresponding to the second identification information.

[0312] Figure 25 is a diagram illustrating how a second device relays messages between two brokers.

[0313] The second device may be a device for connecting service providers or brokers. For example, as illustrated in FIG. 20, the first device may be a bridge connecting service providers or brokers, or an interchange including a bridge. For example, the first device may include a first client device connected to a first broker and a second client device connected to a second broker. In this case, the first device may publish messages subscribed / received from the first broker to the second broker via the second client device.

[0314] Meanwhile, as described above, different geocasting methods may be set between the first broker and the second broker. For example, the first broker may be a broker that receives a message issued through first identification information for a road section and performs geocasting of the message for the road section using the first identification information, and the second broker may be a broker that receives a message issued through second identification information for a cell area and performs geocasting of the message for the cell area using the second identification information.

[0315] Specifically, referring to FIG. 25, the second device may receive a first message issued from the first broker using first identification information related to a road section (S251). The first message may be a message for the first broker to relay a message (originally) issued by a device or VRU device related to a vehicle. The first identification information may include information for specifying / identifying the road section. For example, the first identification information may include information about two nodes related to the road section, or may be a topic defined based on the two nodes.

[0316] Next, the second device can forward the first message to a second broker that uses a different geocasting method than the first broker. In this case, the second device can convert the road segment associated with the first identification information into a Quadtree-based cell area or a Geohash-based cell area (S253). As described in the section "Implementation of Real-Time Conversion and Interoperability Between Road Segments and Cell Areas and Between Cell Areas", the second device can calculate a deviation between the road segment identified / specified by the first identification information and the curved road segment having the preset maximum curvature based on a preset maximum curvature, and specify a geographic area corresponding to the road segment (e.g., a geographic area that can include curved road segments having the preset maximum curvature) based on the calculated deviation, and convert the road segment into at least one Quadtree-based cell area or at least one Geohash-based cell area that overlaps the specified geographic area. In this case, the second device may define / determine second identification information corresponding to the first identification information based on the at least one quadtree-based cell area or the at least one geohash-based cell area. For example, the second device may define / determine an index value for the at least one quadtree-based cell area or a string for the at least one geohash-based cell area as the second identification information. Here, the first identification information may be a topic defined by the identification information of the road section according to the node / link method, and the second identification information may be a topic defined by an index value for the quadtree-based cell area or a string for the geohash-based cell area.

[0317] Next, the second device may issue a second message to transmit the first message (S255). As described above, when transmitting the first message to a second broker that geocasts messages in a different manner than the first broker, the second device may issue the second message to the second broker using second identification information defined to correspond to the first identification information.

[0318] In this way, the proposed invention can ensure conversion into second identification information for a cell area that can include all curved sections that can be considered by the first identification information by determining a geographic area corresponding to a road section by considering a preset maximum curvature. In addition, the proposed invention can effectively convert a road section-based geocasting method for messages issued from a Vulnerable Road User (VRU) device into a cell area-based geocasting method suitable for the movement characteristics of the VRU. Furthermore, the proposed invention can effectively improve the interaction between a vehicle driving on a road and a VRU based on the message by ensuring the delivery of the message issued from the VRU device through cell area-based geocasting.

[0319] Examples of communication systems to which the invention applies

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

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

[0322] Figure 26 illustrates a communication system applied to the present invention.

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

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

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

[0326] Examples of wireless devices to which the present invention is applied

[0327] Figure 27 illustrates a wireless device applicable to the present invention.

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

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

[0330] A first wireless device or first apparatus (100) may include a processor (102), a memory (104), and a transceiver (106). The memory (104) may include at least one program capable of performing operations related to the embodiments described in FIGS. 16 to 25. For example, the operations may include receiving a first message issued using first identification information associated with a road segment; and issuing a second message for transmitting the first message, wherein based on the first message being issued by a Vulnerable Road User (VRU) device, the second message may be issued using second identification information for a cell area converted to correspond to the road segment.

[0331] Alternatively, a processing device may be configured, comprising at least one processor (102) for controlling a first device and a memory (104). In this case, the processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions that perform operations when executed by the at least one processor. The operations include receiving a first message issued by the first device using first identification information associated with a road segment; and issuing a second message for transmitting the first message, wherein the second message may be issued using second identification information for a cell area converted to correspond to the road segment based on the first message being issued by a Vulnerable Road User (VRU) device. Alternatively, at least one non-transitory computer-readable medium comprising instructions for performing such operations may be configured.

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

[0333] A second wireless device or network (200) may include a transceiver (206), a processor (202), and a memory (204). The memory (204) may include at least one program capable of performing operations related to the embodiments described in FIGS. 16 to 25. For example, the operations may include: receiving, by the second device, a first message issued using first identification information associated with a road segment from a first broker; and issuing, by the second device, a second message for forwarding the first message, wherein the second message may be issued to the first broker using second identification information for a cell area converted to correspond to the road segment, based on which the second message is forwarded to a second broker that geocasts the message based on a cell area.

[0334] Alternatively, a processing device may be configured, including at least one processor (102) and a memory (104) for controlling a second device. In this case, the processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions that perform operations when executed by the at least one processor. The operations may include receiving a first message published using a first topic (TOPIC) defined for geocasting from a client device, publishing the first message to a third device of a heterogeneous service provider via the first device, wherein the first message is converted into a second message by the first device, and the second message may be published to the third device using a second topic defined based on the service provider of the second device. Alternatively, at least one non-transitory computer-readable medium including instructions for performing such operations may be configured.

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

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

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

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

[0339] Examples of wireless devices to which the present invention is applied

[0340] Figure 28 illustrates another example of a wireless device applicable to the present invention. The wireless device may be implemented in various forms depending on the use case / service (see Figure 26).

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

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

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

[0344] Examples of vehicles or autonomous vehicles to which the present invention is applied

[0345] Figure 29 illustrates a vehicle or autonomous vehicle applicable to the present invention. The vehicle or autonomous vehicle may be implemented as a mobile robot, a car, a train, a manned or unmanned aerial vehicle (AV), a ship, or the like.

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

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

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

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

[0350] The embodiments described above are combinations of components and features of the present invention in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form an embodiment of the present invention by combining some components and / or features. The order of 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 self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form an embodiment or may be incorporated as a new claim through a post-application amendment.

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

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

[0353] When implemented via firmware or software, an embodiment of the present invention may be implemented in the form of modules, procedures, functions, etc. that perform the functions or operations described above. The software code may be stored in a memory unit and executed by a processor. The memory unit may be located within or outside the processor and may exchange data with the processor via various known means.

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

[0355] The embodiments of the present invention as described above can be applied to various mobile communication systems.

Claims

1. In the method, A step in which a first device receives a first message issued using first identification information related to a road section; and The first device comprises a step of issuing a second message for transmitting the first message, A method wherein the second message is issued using second identification information for a cell area converted to correspond to the road section, based on the first message being issued by a Vulnerable Road User (VRU) device.

2. In paragraph 1, The above cell area is a quadtree-based cell area or a geohash-based cell area, the method.

3. In paragraph 2, A method wherein the second identification information is defined based on an index value of the quadtree-based cell area or a string of a geohash-based cell area.

4. In paragraph 1, The above first identification information is a topic (TOPIC) defined based on the road section, A method wherein the second identification information is a topic (TOPIC) defined based on an index value for the quadtree-based cell area or a string for the geohash-based cell area.

5. In paragraph 1, A method wherein the first identification information includes information about a first node and a second node associated with the road section.

6. In paragraph 1, The first device determines a geographic area corresponding to the first identification information based on a curved section having a preset maximum curvature between the first node and the second node, A method wherein the second identification information is determined based on an index value for at least one quadtree-based cell area overlapping the geographic area or a string for at least one geohash-based cell area.

7. In paragraph 6, A method wherein the preset maximum curvature is 60 degrees.

8. In paragraph 1, A method wherein the second message is issued using the first identification information based on the first message being transmitted from a device associated with the vehicle.

9. In at least one non-transitory computer-readable medium, Contains instructions that perform operations when executed by at least one processor, The above actions are, Receiving a first message issued using first identification information associated with a road segment; and Including issuing a second message for transmitting the first message, At least one non-transitory computer-readable medium recording medium, wherein the second message is issued using second identification information for a cell area converted to correspond to the road section, based on the first message being issued by a Vulnerable Road User (VRU) device.

10. In the first device, RF(Radio Frequency) transmitter and receiver; a processor connected to the RF transceiver; and a memory comprising at least one program that performs operations when executed by the processor; The above actions are, Receiving a first message issued using first identification information associated with a road segment; and Including issuing a second message for transmitting the first message, A first device, wherein the second message is issued using second identification information for a cell area converted to correspond to the road section, based on the first message being issued by a Vulnerable Road User (VRU) device.

11. In the processing device controlling the first device, at least one processor; and At least one memory connected to said at least one processor and storing instructions that perform operations when executed by said at least one processor, The above actions are, The first device receives a first message issued using first identification information related to a road section; and wherein the first device issues a second message for transmitting the first message; A processing device, wherein the second message is issued using second identification information for a cell area converted to correspond to the road section, based on the first message being issued by a Vulnerable Road User (VRU) device.

12. In the method, A step in which a second device receives a first message issued using first identification information related to a road section from a first broker; and The second device comprises a step of issuing a second message for transmitting the first message, A method wherein the second message is issued to the first broker using second identification information for a cell area converted to correspond to the road section, based on which the second message is delivered to the second broker for geo-casting the message based on the cell area.

13. In at least one non-transitory computer-readable medium, Contains instructions that perform operations when executed by at least one processor, The above actions are, Receive a first message issued using first identification information related to a road segment from a first broker; and Including issuing a second message for transmitting the first message, At least one non-transitory computer-readable medium recording medium, wherein the second message is issued to the first broker using second identification information for a cell area converted to correspond to the road section, based on which the second message is delivered to the second broker for geo-casting the message based on the cell area.

14. In the second device, RF(Radio Frequency) transmitter and receiver; a processor connected to the RF transceiver; and a memory comprising at least one program that performs operations when executed by the processor; The above actions are, Receive a first message issued using first identification information related to a road segment from a first broker; and Including issuing a second message for transmitting the first message, A second device, wherein the second message is issued to the first broker using second identification information for a cell area converted to correspond to the road section, based on which the second message is delivered to the second broker for geo-casting the message based on the cell area.

15. In a processing device that controls a second device, at least one processor; and At least one memory connected to said at least one processor and storing instructions that perform operations when executed by said at least one processor, The above actions are, The second device receives a first message issued using first identification information related to a road section from the first broker; and wherein the second device issues a second message for transmitting the first message; A processing device wherein the second message is issued to the first broker using second identification information for a cell area converted to correspond to the road section, based on which the second message is delivered to the second broker for geo-casting the message based on the cell area.

Images