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

Abstract

A device for performing communication in a wireless communication system according to various embodiments is provided. The device may establish a connection with a first broker among a plurality of brokers related to a message protocol based on publishing and subscribing, publish metadata to the first broker by using a meta topic, and publish a first message to the first broker by using a publication topic.

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 of the present invention comprises: forming a connection with a first broker among a plurality of brokers associated with a message protocol based on publish and subscribe; publishing metadata to the first broker using a meta topic; and publishing a first message to the first broker using a publish topic; wherein the metadata may include coverage information for specifying at least one broker among the plurality of brokers to relay the first message.

[0018] Alternatively, the coverage information is characterized by including information about a coverage type and information about at least one location for defining coverage of the coverage type.

[0019] Alternatively, each of the plurality of brokers provides a relay service of a message related to the message protocol for one of the plurality of zones divided into a preset geographic area, wherein the at least one broker is characterized based on at least one zone covering the specific type of coverage among the plurality of brokers.

[0020] Alternatively, the coverage type is characterized in that it is determined based on the surrounding environment of the device among a circle type, a polygon type, and a line segment type.

[0021] Alternatively, the scope of coverage of the coverage type is characterized in that it is determined based on whether an event related to the first device occurs.

[0022] Alternatively, based on the detection of an occurrence of an event related to the first device, the first device is characterized in that it additionally issues the metadata to extend the scope of coverage of the coverage type.

[0023] Alternatively, the first message is characterized in that it further includes information on the relay validity time of the first message.

[0024] Alternatively, the message protocol is characterized as being MQTT (Message Queuing Telemetry Transport) or AMQP (Advanced Message Queuing Protocol).

[0025] According to another aspect, a non-transitory computer-readable storage medium having recorded thereon instructions for performing the above-described method may be provided.

[0026] According to another aspect, a first device performing the above-described method may be provided.

[0027] According to another aspect, a processing device may be provided for controlling a first device performing the method described above.

[0028] A method by a network according to another aspect comprises the steps of: forming a connection with a first device to provide a service related to a publish-and-subscribe based message protocol; subscribing to metadata from the first device based on a meta topic; and receiving a first message published using the published topic from the first device, wherein the metadata may include coverage information for specifying at least one broker among a plurality of brokers providing a service related to the publish-and-subscribe based message protocol to relay the first message.

[0029] According to another aspect, a network performing the method described above may be provided.

[0030] According to another aspect, a processing device may be provided for controlling a network performing the method described above.

[0031] According to various embodiments, data / messages can be transmitted and received more accurately and efficiently in a wireless communication system.

[0032] 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.

[0033] 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.

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

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

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

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

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

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

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

[0041] 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.

[0042] 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.

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

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

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

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

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

[0048] 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.

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

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

[0051] Figure 18 is a diagram illustrating a method for changing the publication cycle and / or subscription cycle using metadata.

[0052] Figure 19 is a diagram for explaining a method of transmitting metadata based on the packet format of MQTT.

[0053] FIG. 20 is a diagram illustrating a method for coordinating the publication cycle of messages / data through metadata based on metadata topics between a server and multiple clients.

[0054] FIG. 21 and FIG. 22 are drawings for explaining the architecture of a map tile-based V2N2X system.

[0055] FIGS. 23 and 24 are drawings illustrating a method for issuing metadata related to a map tile or a tile setting.

[0056] Figure 25 is a diagram for explaining a method of defining / setting the validity time of a message in the V2N2X layer.

[0057] Figure 26 is a drawing for explaining how the first device issues a message based on a message protocol.

[0058] Figure 27 is a diagram illustrating how a network relays a first message from a first device.

[0059] Figure 28 illustrates a communication system applied to the present invention.

[0060] Figure 29 illustrates a wireless device applicable to the present invention.

[0061] Figure 30 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.

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

[0063] 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).

[0064] 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.

[0065] 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.

[0066] 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.

[0067] 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.

[0068] 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.

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

[0070] 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.

[0071] 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.

[0072] 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.

[0073] 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.

[0074] 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.

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

[0076] 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.

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

[0078] 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).

[0079] 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).

[0080] 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.

[0081] 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

[0082] 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.

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

[0084] 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.

[0085] 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.

[0086] 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).

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

[0088] 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).

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

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

[0091] 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.

[0092] 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.

[0093] 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.

[0094] 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.

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

[0096] - Satellite integrated network

[0097] - 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).

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

[0099] - 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.

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

[0101] - small cell networks

[0102] - Ultra-dense heterogeneous network

[0103] - High-capacity backhaul

[0104] - 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.

[0105] - Softwarization and virtualization

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

[0107] - 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.

[0108] - 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.

[0109] 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.

[0110] - Large-scale MIMO technology

[0111] - Hologram beamforming (HBF)

[0112] - Optical wireless technology

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

[0114] - Quantum communication

[0115] - Cell-free communication

[0116] - Integration of wireless information and power transmission

[0117] - Integration of wireless communication and sensing

[0118] - Integrated access and backhaul network

[0119] - Big data analysis

[0120] - Reconfigurable intelligent surface

[0121] - metaverse

[0122] - Block chain

[0123] 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.

[0124] - 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.

[0125] - 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.

[0126] - 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).

[0127] 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.

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

[0129] 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.

[0130] 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.

[0131] 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.

[0132] 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.

[0133] 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.

[0134] 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.

[0135] 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.

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

[0137] 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).

[0138] 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.

[0139] 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.

[0140] 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.

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

[0142] 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.

[0143] 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.

[0144] 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:

[0145] (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.

[0146] (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.

[0147] (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.

[0148] 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.

[0149] 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.

[0150] 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.

[0151] 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.

[0152] 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.

[0153] 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 order to evaluate PSBCH performance, in NR V2X, the payload size of PSBCH may be 56 bits, including a 24-bit CRC (Cyclic Redundancy Check).

[0154] 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.

[0155] 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.

[0156] 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.

[0157] 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.

[0158] 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.

[0159] 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 within the set resource pool. For example, the terminal can select resources 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 within the 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.

[0160] 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.

[0161] 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.

[0162] 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.

[0163] 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.

[0164] 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 a 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.

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

[0166] MQTT / AMQP protocol

[0167] Figure 16 is a diagram for explaining AMQP (Advanced Message Queuing Protocol) for transmitting V2N messages, and Figure 17 is a diagram for explaining MQTT (Message Queuing Telemetry Transport) protocol for transmitting V2N messages.

[0168] 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.

[0169] 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.

[0170] 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.

[0171] Referring to Fig. 17 (a), the MQTT protocol may be a message protocol having a structure that operates as a composition of a publisher (or client), a broker, and a subscriber (or client or client device). 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 a subscriber based on topics.

[0172] 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.

[0173] 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.

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

[0175] 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.

[0176] (1) Preparation stage

[0177] 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.

[0178] 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).

[0179] 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.

[0180] (2) Publishing / subscribing to messages

[0181] 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).

[0182] 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).

[0183] 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.

[0184] (3) PC5-based V2X message transmission principle

[0185] 1) The PC5 interface can be mainly used for vehicle-to-vehicle (V2V) or vehicle-to-infrastructure (V2I) communication, and the vehicle's location, speed, and other safety-related information can be exchanged in real time through the PC5 interface.

[0186] 2) The PC5 interface can also be used primarily for direct vehicle-to-vehicle (D2D) communication and is primarily suited for short-range communications. For example, the PC5 interface can be used to quickly transmit safety-related messages, such as traffic accident information and road condition information, to nearby vehicles.

[0187] (4) Map tile method

[0188] The MAP Tile method divides the Earth into small square tiles to manage geographic information and display geographic data. Using the MAP Tile method, the geographic data can be hierarchized, and the map type can be finely divided for each zoom level. For example, zoom level 0 displays the entire Earth as a single tile, zoom level 1 divides the Earth into 2x2 tiles, and zoom level 2 divides the Earth into 4x4 tiles. The number of tiles at each zoom level is 2. zoomlevel X 2 zoomlevel This could be it.

[0189] The coordinate matrix according to the zoom level can be identified as (x, y). The pixels for each zoom level can be expressed as 256x256. For example, if I plot the location of my car in Seoul as a map tile, Seoul is 2 at zoom level 10. 10 X 2 10 Among the map tiles of the dog, some map tiles (or the coordinates of some map tiles) can be expressed. As the zoom level increases, tiles can be composed for a narrower geographic area, and the pixel resolution can also be finer.

[0190] (5) Quadtree method

[0191] The quadtree method is a space partitioning technique that defines geographic information as a hierarchical structure of patent-child structures, and a unique identifier, a quadkey, can be set for each space / tile. For example, a quadtree can have a hierarchical structure that repeatedly divides each tile into four child tiles. The length of the quadkey can increase as the zoom level increases, and the quadkey of each child tile can be defined based on the quadkey of the parent tile. In addition, as the zoom level increases, the tile size can decrease, and each tile can contain more detailed information. As the zoom level increases, the quadkey becomes longer, and the quadkey of the child tile can start with the high bit of the quadkey of the parent tile.

[0192] Meanwhile, when transmitting a V2X message or V2N message using the above-described message protocol, there may be problems as described below.

[0193] Specifically, in the AMQP protocol, when a sender creates a message, control information can be added in a key-value class structure through the Application-property section. This data (e.g., the control information) is not specifically defined by the AMQP standard and is application-dependent, so it can be used in various ways. The main role of the Application-property is to provide the AMQP broker with information essential for properly routing or filtering messages. For example, the AMQP broker can forward a message to a specific destination queue based on a specific value of the Application-property, or the subscriber can perform actions such as processing or ignoring a subscribed message based on a specific value of the Application-property. In addition, the Application-property can be used to convey additional metadata, such as the priority, expiration date, type, and location reference of the message, between applications. At the C-road stage, metadata for transmitting ITS messages such as Decentralized Environmental Notification Message (DENM) and Infrastructure to Vehicle Information Message (IVIM) can be defined through application properties to provide services such as road guidance, hazard warning, and GLOSA.

[0194] This type of transmission method (e.g., defining / providing metadata through application-properties) has a problem in that the header size tends to increase because the application-properties of AMQP / C-Road define required and optional information in a single template. This can lead to problems that can increase network latency. In applications that require large-scale data transfer and fast processing, the delay caused by this increase in header size can affect the performance of the entire system. If all metadata of C-road's application-properties were included without distinction between required and optional, approximately 70 to 80 bytes of metadata could be included in each transmission packet.

[0195] Meanwhile, the MQTT protocol may require information extension for efficient transmission of the V2N2X layer, as it does not define initialization information for filtering and service layers such as AMQP / C-road. Starting with the MQTT 5.0 standard, a user properties section with a Key=Value format of UTF-8 string pairs has been added to the Variable Header, which allows users to specify the context and processing of the message. If a terminal cannot read the Key, the corresponding part (e.g., the user properties section) may be ignored and the binary area corresponding to the corresponding part may not be accessed.

[0196] In the MQTT protocol, MQTT topics can be used to filter messages. However, filtering based on MQTT topics can be applied before receiving messages. For example, message filtering based on MQTT topics can be performed during the broker's message publishing phase. This can mean that the receiver cannot pre-filter all data. MQTT topic-based message filtering may not be suitable for sophisticated filtering operations that selectively process necessary information or allow the client to select specific information. Furthermore, defining MQTT topics for all filtering information can result in excessively long topic strings. This increases topic management complexity and reduces system efficiency. Therefore, extending message filtering through methods other than MQTT topics can be advantageous from a server perspective, enabling sophisticated and efficient data exchange and data curation with clients. For example, utilizing other curation information, rather than topics, can enable sophisticated and efficient data exchange and data curation between the server and the client. Therefore, by separately defining necessary information using user properties within the V2N2X layer, the length of the topic string can be optimized, thereby improving system efficiency.

[0197] Regarding the publishing and subscription of messages / data, designing and optimizing the principles of the publish (or, pub) and subscribe (or, sub) cycles in the MQTT protocol can play a crucial role in the efficiency and responsiveness of a communication system. These subscription / publish cycles can be influenced by the following factors:

[0198] - Publish interval: The publication interval determines how often specific data / message is transmitted to the MQTT broker. For example, the publication interval should be set short to convey emergency road conditions or accident information. On the other hand, when the vehicle is stationary, the publication interval can be set / determined to a relatively longer period.

[0199] - Subscription cycle or subscription interval: The subscription cycle refers to how often a client receives data / messages from the server. Typically, most systems based on the MQTT protocol can receive data based on the cycle of the client that published the message / data (e.g., the publication cycle) or by automatically routing the data to the client whenever the server has a new message. For example, the subscription cycle can be determined based on the publication cycle of the message publisher or the cycle at which the server routes the received message to other clients.

[0200] Setting such publish / subscribe cycles can be crucial for optimizing the overall performance and efficiency of a system, and can be dynamically adjusted to suit specific circumstances. However, prior art lacks a specific method or system for adaptively adjusting the publish / subscribe cycle. Consequently, the publish / subscribe cycle is determined solely by the publisher's judgment. This can lead to the following problems:

[0201] - ① If the issuance cycle is determined by the limited recognition scope of the issuing entity, inefficient or incorrect (transmission cycle) message / data transmission may occur.

[0202] ② Synchronization, stable / consistent message queuing: If each issuer adjusts / determines message transmission cycles based on their own judgment, maintaining message synchronization and consistency across the system can become difficult. Furthermore, duplicate message issuance, message omission, or delays in message publishing / subscription can occur. This can undermine the reliability of road safety systems, which must provide accurate, real-time information.

[0203] - ③ Absence of change notification (e.g., lack of means to notify changes in the publication / subscription cycle): If the server / broker does not properly notify changes in the routing / publication cycle, subscribers (e.g., subscribing devices or subscribing client devices) may misunderstand the frequency or timing of the messages / data they receive, or set the wrong subscription cycle. For example, if messages are published at too slow a cycle, it may be difficult to generate feedback for timely and safe driving actions.

[0204] - ④ Existing V2X communication systems have a fixed data transmission cycle, so they cannot respond flexibly even when road conditions change rapidly, which limits their ability to actively respond to emergency situations.

[0205] - ⑤ The MQTT protocol can provide efficient lightweight messaging, but it does not include a mechanism to dynamically adjust the transmission frequency of data / message, which may limit the optimization of server traffic and / or energy consumption.

[0206] - ⑥ The transmission cycle of static data / messages may not reflect the diversity and volatility of road usage conditions, and may cause unnecessary network load due to data transmission at an unnecessarily high frequency.

[0207] To address these issues, methods and systems that can recognize current road conditions while reducing client load may be needed. For example, a collaborative system approach between the client and server may be necessary. To achieve this, the server may additionally include artificial neural networks (AI), algorithmic analyzers (e.g., digital twins), and V2X managers.

[0208] Additionally, with regard to the validity time of the message, the following issues may be considered.

[0209] The protocol of the conventional PC5 interface is a push-type transmission of V2X messages, and apps that receive the V2X messages can decode (ANS.1) all data elements and display them on the UI upon receipt of the V2X messages. In this case, it is difficult to determine the validity of the received V2X messages in real time, and unnecessary decoding of invalid messages may be performed, resulting in inefficient work of displaying them on the UI (User Interface). In addition, a lot of resources may be wasted for decoding and processing unnecessary messages. Hereinafter, the definition of the message validity time of the V2N2X layer can quickly and efficiently check the validity of the message before transmission / relaying the message by defining the validity time of the message in advance in the V2N2X layer.

[0210] Furthermore, with respect to the propagation area of ​​the message, the following issues may be considered.

[0211] - Range limitations: The PC5 interface is effective only over relatively short distances, making it unsuitable for data transmission over wide areas. This may make it unsuitable for communications in urban areas or in wider areas outside of coverage.

[0212] Infrastructure Dependency: The PC5 interface may have limited communication capabilities in the absence of specific infrastructure. This can be particularly problematic in areas with limited infrastructure. The PC5 interface's fixed communication range and limited use in specific situations can hinder its flexibility in various scenarios / situations.

[0213] Meanwhile, the following requirements can be considered in the proposed method.

[0214] - Enhanced factors can be defined in the description of the application properties of existing AMQP / C-Road.

[0215] - It can be extended to an advanced MQTT-based V2N2X layer beyond application properties. In addition, it must be compatible with existing MQTT receivers.

[0216] - A method can be proposed to minimize inefficient header delivery redundancy in the V2N2X layer compared to AMQP / C-Road.

[0217] - A layer needs to be supported that can filter ITS messages and provide processing guidance, as defined by the V2N2X layer.

[0218] The proposed invention based on the above-described requirements can be applied in the following ways.

[0219] - As a method for extending the V2N2X layer based on MQTT 5.0, V2N2X metadata can be defined by utilizing user properties in the MQTT variable header.

[0220] - By defining it as a UTF-8 key-value pair, as in the definition of MQTT user properties, existing MQTT clients can ignore keys that they cannot read even if they receive them. In this case, it can be extended to be compatible with existing MQTT receivers.

[0221] - V2N2X metadata can be transmitted separately as two TOPIC tracks by defining the Required attribute and the Additional attribute. Required data / message can be defined for all packets, and the Additional attribute (e.g., an attribute that does not need to be transmitted for every packet, not an optional attribute) can be defined as a TOPIC for another transmission track, and the metadata can be published / subscribed through the Additional attribute. This can reduce redundancy because not all packets need to be received through the message / packet / data every time, and can enable flexible metadata transmission and reception through the Additional Topic (e.g., Additional attribute). For example, the TOPIC string of the metadata defined for the Additional attribute for the metadata can obtain the TOPIC string included in the required data at the time of the publication packet connecting the initial session, and subscribe to (or publish) the metadata using the obtained TOPIC string. The metadata can have a period independent of the ITS message period, and the period can be changed depending on the attribute (or Additional attribute).

[0222] Below, the above-described requirements and proposed methods are described in more detail.

[0223] Figure 18 is a diagram illustrating a method for changing the publication cycle and / or subscription cycle using metadata.

[0224] Before going into a specific description of the proposed method, the following prerequisites and requirements may be required for the application of the proposed method.

[0225] - ① All clients can subscribe to metadata containing information such as '@client ID' and '@interval'. Such metadata can be obtained through MQTT user properties, data elements preceding the payload, and / or separate topics.

[0226] - ② The app server may additionally include an MQTT Temporal client with the same properties as the clients of road users. The Temporal client of the app server has the function of issuing messages / metadata to clients under the management of the app server.

[0227] - ③ The app server can configure a digital twin of the area (or geographical area) it is managing, configure metadata according to appropriate purpose and judgment, and transmit / issue the configured metadata to clients under its management through the Temporal client.

[0228] - ④ The above-described solutions / requirements can be managed based on "@Client ID", and can support the function of provisioning metadata (e.g., metadata for managing individual clients and supporting efficient transmission) rather than relaying data / messages in a publication manner. For example, referring to Fig. 18, meta / C0, meta / C1, meta / C2, and meta / C3 can be topics defined for transmission of metadata provided to individual clients. The app server can use each of meta / C0, meta / C1, meta / C2, and meta / C3 to publish or provision metadata corresponding to each client (via a temporary client).

[0229] - ⑤ The proposed system can be based on protocols such as MQTT / AMQP, can utilize a subscription / publish model for data / message exchange among all vehicles and road users, and the app server must be able to manage and provide traffic data and metadata in real time.

[0230] - ⑥ The app server can analyze various variables such as road conditions, weather conditions, and traffic volume in real time, and based on the analysis results, determine the optimal message / data publication / subscription cycle for clients that are subscribed or under management, and dynamically create and manage metadata for controlling / adjusting such publication / subscription cycle.

[0231] - ⑦ Clients can select the data / message publication cycle / interval that best suits their circumstances based on metadata provided by the app server or broker. Alternatively, clients should be able to change the topics they subscribe to as needed.

[0232] Below, specific methods for dynamically controlling the transmission cycle of messages / data based on the above-described proposed method and requirements are described in detail.

[0233] Figure 19 is a diagram for explaining a method of transmitting metadata based on the packet format of MQTT.

[0234] Referring to Fig. 19 (a), a conventional MQTT packet may include a fixed header of 2 bytes in length and a variable header. The fixed header may include information / sub-fields regarding packet type, flags, and remaining length. The variable header may include values ​​according to the packet type and flags, and may be used to convey detailed information about the message.

[0235] Based on the above-described suggestions, the packet structure for receiving metadata through MQTT extension headers and additional topics for the V2N2X layer may be as shown in Fig. 19 (b). In order to efficiently manage metadata in the V2N2X system, a method may be considered in which metadata is defined as required properties and additional properties, and the metadata of required properties and the metadata of additional properties are transmitted through two separate topic paths (or two meta topics), respectively. For example, required data or metadata of required properties must be included in all packets, and additional data or metadata of additional properties do not need to be transmitted repeatedly and can be transmitted through a separately defined topic. This method can reduce redundant data transmission and effectively support the flexibility of metadata transmission.

[0236] The above-described method may require preparatory actions to receive additional metadata via a string of mandatory topics included / defined in the publish packet when connecting the initial session related to MQTT. For example, a topic for metadata (or a metadata topic or meta topic) may be provided during the setup phase of the mandatory topic defined for transmission of the publish packet for connecting the initial session. A metadata topic defined in this way can support sending and receiving metadata at a frequency changed according to the needs depending on the attribute, independently of the transmission frequency of the ITS message.

[0237] The behavior of the client (or broker, server, or receiver) in this regard may be as follows.

[0238] - The client can perform initialization and filtering roles by parsing V2N2X layer extension data with information from MQTT's User property.

[0239] - The client can receive a string of 'metaTopic' for transmitting required information and metadata in the V2N2X layer extension data.

[0240] - The client can manage TOPICs for message reception and TOPICs for metadata reception separately. For example, metadata related to V2N2X layer data received as TOPIC "ITS / V2N / Tileinfo / meta" can be received through a separately defined topic (e.g., ITS / V2N / Tileinfo / meta). In this system, only essential initialization data is included, and additional metadata can be received through additionally defined topics.

[0241] Below, specific embodiments of the proposed method described above are described.

[0242] Client A connected to an application related to V2N or V2N service can start moving / driving in a region called “Seocho-gu”. Client A can initialize the application to receive ITS messages. Client A can send a connection request (CONNECT) to the MQTT broker, and the MQTT broker can send a connection acknowledgment (CONNACK) to establish / configure a connection with Client A. Client A can obtain information about regional topic creation rules related to “Seocho-gu” to receive information / messages provided by the ITS service. The operator can provide a corresponding topic according to the location information of Client A, and various topic creation rules can be defined according to the provision method of the operator. Client A can send a SUBSCRIBE request for a topic of V2N / tile to the broker (here, tile can mean a receiving section for filtering according to the location information of Client A, for example, a topic for receiving only V2N packets for the location of the tile). The broker can send a SUBACK response to the SUBSCRIBE request of the client A to the client A.

[0243] Meanwhile, Client B can PUBLISH a V2X or ITS message transmitted / published from another server to the broker. At this time, Client B may be located within the area / geographical region of a potential event adjacent to Client A, and the topic string (Topic String) can be PUBLISHed as a V2N packet, etc. as a V2N / tile (e.g., the same topic as Client A's V2N / tile), and the PUBLISHed packet may include V2N2X metadata in the User property part. The User property of this PUBLISHed packet may include a key (= metatopic) for which additional metadata is provided. In addition, V2N2X additional metadata may be PUBLISHed as a topic of V2N / tile / metatopic.

[0244] When client B initiates a PUBLISH of a packet (e.g., an MQTT packet) to a topic of V2N / tile, client A can receive packets (e.g., MQTT packets) subscribed to the topic of V2N / tile. Client A can identify a key (=metatopic) that provides additional metadata obtained by parsing the user property part in the MQTT packet and request a SUBSCRIBE to the broker for a topic with the string V2N / tile / metatopic. In this case, the broker can send a SUBACK response to the SUBSCRIBE request of client A, through which client A can establish a subscription to the topic with the string V2N / tile / metatopic. Client A can store the additional metadata received through such a subscription as a configuration. An application (App) can obtain consent from the user to apply certain settings (e.g., low power mode based on message interval adjustment) within additional metadata. With such consent, Client A can perform the algorithms and operations provided through the additional metadata and receive corresponding enhanced services through the application (App).

[0245] 1. Solution: Adjusting the publish / subscribe cycle through individual metadata.

[0246] Below, we describe in detail how to dynamically adjust the transmission cycle / publication cycle of messages / data based on the publish / subscribe method of metadata / additional metadata through the additional topics described above.

[0247] In a scenario where all clients share data through publish / subscribe based on the same TOPIC (=A), a method can be considered where the app server adjusts the publication / subscription cycle of data / messages at the discretion of the Digital Twin (e.g., the composition of messages / data can be performed with the same Topic A, and when the publication cycle is adjusted, the subscription cycle can also be automatically adjusted).

[0248] Each client can publish messages / data based on a topic corresponding to its location / region. Additionally, if necessary, each client can subscribe to messages / data that can obtain local road condition information through the topic. Furthermore, each client can subscribe to metadata through an additional TOPIC (or metadata TOPIC, metatopic) for metadata acquisition.

[0249] Each client can be identified by a unique client ID. In this case, the server can create a metadata TOPIC (e.g., client212 / Meta) corresponding to each client ID. Each client can obtain its corresponding metadata TOPIC in advance through the service discovery procedure, and can periodically receive updates on the publication cycle of messages / data based on the metadata TOPIC. The string of the metadata topic can be defined in the user properties or defined / received according to the policy defined by the business / operator. The metadata can include information about each client's current publication / transmission cycle, network status, traffic conditions, expected changes, etc. The metadata is transmitted in JSON / XML format, and each field of the metadata can include information necessary to adjust the client's transmission cycle.

[0250] For example, the metadata described above can be defined as in Table 5.

[0251] {"metadataId": "SoftV2X_meta1","metaVersion": "1.0",“clientId: “212”,"communicationDetails": {"recommendedTransmissionRange": {"minInterval": "0.1 seconds","maxInterval": "3 seconds"} -> option 1"originalTransmissionInterval": "0.1 seconds""recommendedTransmissionInterval": "3 seconds" -> option 2"adjustmentWindow": "600""trafficCondition": {"level": "low","description": "Light traffic"},"vehicleData": {"speed": "30 km / h","location": "123.42314 N, 118.23123 W"},"networkStatus": {"bandwidth": "10 Mbps","latency": "90 ms"},"environmentalFactors": {"weather": "clear","visibility": "good"},},"updateTimestamp": "2024-04-18T12:30:00Z"}

[0252] Here, metadataId is a unique identifier of metadata, clientId is a unique identifier of the client, originalTransmissionInterval is the current client's message / data issuance / transmission cycle, recommendedTransmissionInterval is a new message / data issuance / transmission cycle recommended based on data analyzed by the server, recommendedTransmissionRange contains the Min and Max values ​​of the new message / data issuance cycle recommended based on data analyzed by the server, trafficCondition contains information about the current traffic conditions around the client, vehicleData contains information about the current speed and location of the client's vehicle, networkStatus contains information about the bandwidth and latency of the network to which the client is connected, environmentalFactors contains information about environmental factors such as current weather and visibility conditions, and updateTimestamp may contain information about the last updated time of metadata information.

[0253] While the proposed methods describe topic-based metadata acquisition, HTTP (HyperText Transfer Protocol)-based metadata acquisition may also be possible. For example, access to HTTP's Rest API (Representational State Transfer Application Programming Interface) can be defined in the user properties mentioned above or acquired through a discovery process, and the metadata can be acquired through the acquired HTTP Rest API. Alternatively, metadata can be acquired through a pre-known access address via a contract.

[0254] Data can be input from various data sources, not just road clients. This data may include information on road traffic conditions, traffic accidents, weather conditions, network conditions, etc. For example, this data may include RSU camera image information, weather conditions, bandwidth, etc. This data can be transmitted to the server in real time, and the server can continuously monitor and analyze the received data to dynamically adjust the message / data generation / transmission cycle for each client.

[0255] When the Digital Twin of the app server determines that the message / data issuing / transmitting cycle needs to be changed from "@issue_interval = 0.1" to "@issue_interval = 1" for "@client_Id=212" depending on road conditions, the Temporal Client of the app server can publish / provision metadata containing information about the change in the issuing cycle to the topic "client212 / Meta" corresponding to "@client_Id=212". The client with Client ID = 212 can receive the metadata through the subscription topic for the metadata, client212 / Meta, and adjust / control the message / data transmission / issuing cycle according to "@issue_interval = 1" included in the metadata.

[0256] The specific process of adjusting the transmission / publication cycle of messages / data using metadata can be as follows.

[0257] (1) Data analysis and metadata creation

[0258] The server can analyze (environmental) information (e.g., traffic conditions, vehicle data, network conditions, environmental factors, etc.) collected from various data sources in real time. Based on the analysis results, the server can generate metadata (SoftV2X_meta1) for a specific client (e.g., client 212). Here, the metadata can include information about communication details such as transmission cycles and traffic conditions.

[0259] (2) Metadata issuance / provisioning

[0260] The server can publish / provision the generated metadata to the client in JSON (JavaScript Object Notation) format. The metadata can include information about the client's identification information, current and recommended publication / transmission cycles, traffic conditions, etc. The metadata can be delivered via a TOPIC (e.g., client212 / Meta) to which the corresponding client is subscribed. For example, the server can generate the metadata, publish / provision the generated metadata as a temporary client, and deliver it to the client.

[0261] (3) Subscribe to / receive metadata

[0262] The client (212) can subscribe to / receive metadata through the subscribed TOPIC (e.g., a metadata topic pre-configured / obtained for transmission of metadata). Here, the metadata may optionally include information about the above-described "@recommendedTransmissionRange" or "@recommendedTransmissionInterval". If the metadata includes "recommendedTransmissionRange", the client (212) can select / set its own appropriate transmission cycle within the publication / transmission cycle defined in recommendedTransmissionRange. In this case, a flexible publication / transmission cycle can be set for the client (212), but the complexity of the system may increase. In contrast, indicating / setting the transmission / publication cycle of messages / data through "recommendedTransmissionInterval" can be clearer and simpler to develop than the "recommendedTransmissionRange" approach. Considering these pros and cons, the two methods can be used in a hybrid manner. For example, the setting of the issue / transmission cycle based on "recommendedTransmissionInterval" is performed with priority, but in a situation where dynamic adjustment of the issue / transmission cycle is required (e.g., when the user requires battery management or the user setting is applied), the flexibility to dynamically adjust the issue / transmission cycle within the range defined in "recommendedTransmissionRange" can also be provided. In this case, the metadata can include information about "@recommendedTransmissionRange" and "@recommendedTransmissionInterval". The maintenance time of the issue / transmission cycle according to the metadata can be set through "adjustmentWindow" included in the metadata.For example, if the adjustmentWindow of the metadata contains a value corresponding to 600 (seconds), the occurrence / transmission cycle according to the metadata may be continued / maintained for 10 minutes.

[0263] (4) Feedback mechanism

[0264] The client (212) can monitor the effectiveness of the publication / transmission cycle adjusted by the metadata. If necessary, the client (212) can transmit / publish metadata containing feedback information for further adjustment of the publication / transmission cycle to the server. In this case, the server can update the publication / transmission cycle based on the feedback information and publish / provision metadata containing information about the updated publication / transmission cycle. For example, the metadata can be published aperiodically as needed.

[0265] For example, in the following cases, the method of adjusting the issuance / transmission cycle of messages / data through the metadata described above can be performed.

[0266] - If the speed of a vehicle associated with a client (e.g., a vehicle equipped / included with the client) is stable (within ±5 km / h), the frequency of issuing messages / data from the client may be reduced to 0.1 Hz via metadata. Alternatively, even during stable driving, weather conditions may be given priority. For example, sudden deterioration of weather conditions, such as rain / snow, thick fog, or road conditions that indicate sinkholes or ice, may be detected. In this case, the server may increase the frequency of issuing messages / data from the client via metadata even if the speed of the vehicle associated with the client is stable.

[0267] - When a large vehicle (e.g., a large vehicle equipped with / containing a client) changes lanes abruptly, or when an emergency vehicle (e.g., an emergency vehicle equipped with / containing a client) requires rapid movement, the server may increase the frequency of issuing messages / data from the client via metadata.

[0268] - If a change in speed of a vehicle associated with a client (e.g., a vehicle equipped / included with the client) exceeds 5 km / h, the server may increase the frequency at which messages / data are issued from the client (e.g., to 1 Hz). Alternatively, if a sudden change of 10 km / h or more is detected, BSM / CAM data or messages may be transmitted immediately and the frequency at which messages / data are issued from the client may be reset to 1 Hz.

[0269] - When the battery level of a device related to a vehicle (e.g., a client terminal mounted / included in a vehicle) is below a certain threshold (e.g., 33%) and is not charged, the server may reduce the frequency of issuing messages / data of the client (e.g., increase the issuing cycle) to save power of the client.

[0270] - If a pedestrian associated with a client is not in a traffic-intensive environment or is moving in a safe environment (e.g., a pedestrian is walking in a park or using a safe, car-free walkway), the server may use metadata to decrease the frequency of the client's message / data transmission. Conversely, if a pedestrian associated with a client is on a busy road, close to a road, or entering an intersection, the server may use metadata to increase the frequency of the client's message / data transmission (e.g., decrease the transmission cycle).

[0271] - If a bicycle associated with a client is riding on a bicycle-only road with no cars, the server can reduce the frequency of issuing messages / data from said client (e.g., increase the issuing cycle) via metadata.

[0272] The method of changing the transmission cycle related to the conditions described above can be considered by considering parameters as shown in Table 6 below.

[0273] Parameters (quantifying each variable) - Time of day (T): Traffic volume by time of day, rush hour, night, etc. - Road type (S): Traffic flow according to each characteristic such as highway, urban road, rural road, etc. - Weather condition (W): Reflecting weather conditions such as rain, snow, fog, clear weather, etc. - Traffic volume (C): Number of vehicles on a road or at a specific time of day - Events and special circumstances (E): Sports events, performances, festivals, etc. - Road hazards (R): Road work, temporary road closures, sinkholes, icy roads, etc.* is the weight interval adjustment value for each variable = if (interval / cycle control value < threshold 1) -> low interval (or, relatively short message / data issuance period) else if (threshold 1 ≤ traffic condition score < threshold 2) -> medium interval else -> high interval (or, relatively long message / data issuance period)

[0274] The examples described above enable efficient data exchange between clients and servers, and can improve the overall performance and efficiency of the network by adopting customized data transmission strategies tailored to each client's circumstances.

[0275] 2. Solution 2: Adjusting the subscription cycle through subscription topics

[0276] FIG. 20 is a diagram illustrating a method for coordinating the publication cycle of messages / data through metadata based on metadata topics between a server and multiple clients.

[0277] Referring to FIG. 20, the server can provide multiple subscription topics as a single metadata for multiple clients, including information related to subscription cycles. Unlike the previously described method, the server provides clients with information about multiple subscription topics related to setting / determining subscription cycles. Each client can select a subscription topic appropriate to its situation from among the multiple subscription topics and subscribe to messages / data based on the selected subscription topic.

[0278] (1) Structure design of metadata topics

[0279] Each client can obtain information about published and subscribed topics during the service discovery process (or initial setup process) and establish a connection with the server. For example, if a client receives data / messages in the Yangjae-dong area, the published topic may be set to Yangjae-dong / A, and the subscribed topic may also be set to Yangjae-dong / A. Meanwhile, the subscription topic may be changed to Yangjae-dong / A / 0.5, as described below, to adjust the subscription cycle / interval of messages / data.

[0280] The V2X manager can manage and publish / generate metadata that reflects real-time traffic conditions in each area. The metadata may include information about the transmission / publishing cycles of V2X messages that reflect the current conditions of a certain road area, and may include information defining additional subscription topic strings related to the transmission / publishing cycles.

[0281] (2) Server data analysis and digital twinning, metadata provisioning logic

[0282] The server can collect object recognition data, real-time traffic data, weather information, and road condition information from various sources, including road users, pedestrians, and cameras. In this case, the server can build and monitor a digital twin that aligns spatiotemporally with the actual road using the collected data. The server can then publish appropriate V2X messages and metadata to subscribed clients regarding events occurring within the digital twin.

[0283] (3) Method for obtaining metadata of subscription clients

[0284] A subscription client can adaptively adjust the reception cycle / interval of its data / messages by analyzing the received metadata. For example, the subscription client can determine / select the final subscription cycle based on information about current road conditions, expected traffic volume, and special events. In this case, the client can efficiently adjust the subscription cycle of its messages / data based on the latest traffic information. For example, the metadata may include information about multiple subscription topics related to the subscription client. In this case, the subscription client can select a subscription topic appropriate to its situation from among the multiple subscription topics based on the collected / obtained traffic environment information, and determine / set the subscription cycle associated with the selected subscription topic as its message / data subscription cycle.

[0285] Metadata related to Solution 2 can be defined as shown in Table 7 below.

[0286] {"metadataId": "SoftV2X_meta1","metaVersion": "1.0","clientId: "212""communicationDetails": {"recommendedTransmission": {"baseInterval": "0.1 seconds","alternativeIntervals": [{"trafficCondition": "normal","recommendedInterval": "0.5 seconds"},{"trafficCondition": "light traffic","recommendedInterval": "2.0 seconds"}]}"networkStatus": {"bandwidth": "10 Mbps","latency": "90 ms"},"environmentalFactors": {"weather": "clear","visibility": "good"},},"publishTimestamp": "2024-04-18T12:30:00Z"}

[0287] Here, metadataId is a unique identifier for the metadata, clientId is a unique identifier for the client, baseInterval is the client's default subscription / transmission cycle, alternativeIntervals is a new subscription / transmission cycle recommended based on data analyzed by the server, and recommendedInterval is a new subscription / transmission cycle value recommended based on data analyzed by the server. trafficCondition contains information about the current traffic conditions around the client, networkStatus contains information about the bandwidth and latency of the network to which the client is connected, environmentalFactors contains information about environmental factors such as current weather and visibility conditions, and publishTimestamp can contain information about the last update of the information contained in the metadata.

[0288] For example, a server can collect real-time traffic data, weather information, and local events for the Yangjae-dong area, and build a digital twin on the server based on the received information. The digital twin can reflect a traffic condition score that considers various factors, and the server can define a default cycle of '0.1 seconds', an alternative cycle of '0.5 seconds', or '2.0 seconds' based on the traffic condition score. The cycle defined in this way is included in the metadata, and the server can publish the metadata to clients through the topic of Yangjae-dong / meta. Such metadata can be published periodically. A subscribed client can change the current subscription topic to a subscription topic corresponding to a '2.0 second' cycle when traffic conditions are light and weather conditions are good (e.g., subscription topic = Yangjae-dong / A / 1.0 changed to Yangjae-dong / A / 2.0).

[0289] Alternatively, if a sudden rain shower occurs, the server can regenerate and publish metadata. The metadata may define only baseInterval and not alternativeIntervals. A client subscribed to such metadata can change the subscription topic based on the subscribed metadata (e.g., the subscription topic changes from Yangjae-dong / A / 2.0 to Yangjae-dong / A / 1.0). Later, if the weather improves again and traffic flow improves, the server can publish metadata containing alternativeIntervals with a base period of `0.1 seconds`, alternative periods of `1.0 seconds`, and `3.0 seconds`. In this case, the client can change the subscription period based on the judgment condition. For example, a client subscribed to the metadata can change the subscription topic from Yangjae-dong / A / 1.0 to Yangjae-dong / A / 3.0.

[0290] The above-described proposed method can be expected to have the following technical effects.

[0291] First, in a scenario where all clients subscribe to / publish to the same TOPIC (=A) and share data, the app server can adjust / adapt the subscription / publishing cycle / interval (e.g., client message / data subscription / publishing) as a digital twin. In this case, a personalized approach allows for individual data transmission cycle adjustments for each client, maximizing communication efficiency and optimizing network resources. Furthermore, road condition monitoring via digital twins enables accurate and timely real-time data provision tailored to each client's location and situation, enabling each client to gain accurate situational awareness. Furthermore, the server can continuously analyze data and dynamically adjust the subscription / publishing cycle in response to rapidly changing road conditions. Furthermore, by allowing clients to adjust their transmission cycles, a more personalized communication strategy can be adopted based on each client's conditions and needs.

[0292] Furthermore, a system that allows for adjustment of subscription / publishing cycles via metadata allows for dynamic adjustment of data / message transmission cycles based on real-time changing road conditions, thereby improving the efficiency of traffic information for road users. Furthermore, dynamic adjustment of data / message transmission cycles / intervals can optimize network load, and subscribing clients can effectively explore personalized communication strategies and data / message retrieval methods based on their status within the server's provisioned interval range (or transmission cycle range).

[0293] 3. Solution 3: Defining the message propagation area using the V2N2X layer

[0294] FIG. 21 and FIG. 22 are drawings for explaining the architecture of a map tile-based V2N2X system.

[0295] V2N2X may be a method of performing V2X communication by utilizing cellular networks (e.g., Uu interfaces). Communications based on V2N2X can support communication between vehicles and networks over wide areas, beyond the limited geographical range of the PC5 interface.

[0296] (1) System architecture

[0297] 1) MQTT Broker: An MQTT broker can be deployed for each map tile area (or zone). The MQTT broker can relay the exchange of messages / data between road users in its corresponding map tile area.

[0298] 2) Client app (or client device): Road users' apps can connect to MQTT brokers and publish and subscribe to data / messages in real time. The app can connect to the appropriate MQTT broker based on the user's location. The app can connect to the nearest MQTT broker based on the user's current GPS location. As the user moves, the app can automatically attempt to connect to the appropriate MQTT broker based on the user's location change, or update the broker with the appropriate MQTT broker.

[0299] 3) Map tile-based UI: The app's UI is based on map tiles and can display the user's current location and movement path in real time.

[0300] (2) Broker placement (map tile-based broker placement and management)

[0301] 1) Broker Placement: The entire map can be divided into multiple map tiles. One MQTT broker can be placed for each map tile. In this case, all road users within each map tile can be connected to the broker placed for the corresponding map tile. For example, if a map tile is 10 km x 10 km in size, all road users within a single map tile can be connected to the same broker.

[0302] 2) The V2N2X service range is composed / divided into multiple geographically divided tiles (or multiple map tiles, multiple zones), and the service provision range can be determined for each tile. For example, as illustrated in Fig. 21, a server (or MQTT broker) can be deployed for each map tile, and messages / data can be shared between servers through interfacing (e.g., message bridge).

[0303] For example, referring to FIG. 21, MQTT brokers may be deployed for each predetermined map tile area. For example, corresponding MQTT brokers may be predefined / configured for each predefined map tile area. In addition, server #1 may include a bridge for exchanging messages with the MQTT broker and another broker (or another server #2). Here, the bridge may be composed of a local client and a neighboring client. The local client may forward messages published from the broker to the neighboring client, and the neighboring client may publish the messages to the MQTT broker of another server. Alternatively, the neighboring client may subscribe to the messages from the MQTT broker of another server, and the local client may receive messages from the neighboring client and publish the forwarded messages to the MQTT server of the server to which it belongs.

[0304] Alternatively, referring to FIG. 22, a V2N2X reference architecture configured for information sharing by stakeholders of a Service Provider (SP), an Infrastructure Owner Operator (IOO), and an Original Equipment Manufacturer (OEM) is illustrated. Each domain can be interconnected via an interface. Furthermore, the reference architecture can provide scalability, such as data exchange over a wider range through information sharing instances, in addition to direct connection between each domain. Such a structure can support data exchange over a wider range in the V2N2X ecosystem. For example, as described above, V2N2X can support communication between vehicles and the network over a wide geographic range beyond the limited geographic range of the PC5 interface by performing V2X communication using a cellular network (Uu interface).

[0305] Below, we detail how to configure, or (additionally) select / specify, at least one broker corresponding to a client by providing map tiles or tile-related information via metadata.

[0306] FIGS. 23 and 24 are drawings illustrating a method for issuing metadata related to a map tile or a tile setting.

[0307] The map type or coverage type can be defined as a Rectangle type, a Radius type, a Line Segment type, a Polygon type, etc. For example, referring to Fig. 23, the Rectangle type can be defined / set through parameters (or attributes) of the lower left and upper right latitude / longitude (lowerLeft, upperRight). Such a Rectangle type may be a type suitable for covering major urban areas. The Radius type can be defined / set through parameters for the center point and radius. The Radius type may be suitable for covering a geographic area within a certain radius centered on a specific point. The Line type or Line type can be defined / set through parameters for the latitude and longitude for each of a plurality of nodes (or a list of nodes). The Line Segment type may be a type suitable for covering a geographic area corresponding to a road section connecting major intersections (e.g., a highway, an expressway). Polygon types can be defined and configured via parameters for multiple latitude / coordinate pairs. Polygon types can be suitable for covering complex geographic areas connected by multiple points.

[0308] For example, referring to Figure 24, a schematic geographic area corresponding to each type is illustrated. The area for each type can be set / defined in the following manner.

[0309] (1) Square area type

[0310] 1) The publishing app or client device can generate metadata including parameters for setting / defining a rectangular area type. For example, the publishing app or client can determine its location and parameters for defining a rectangular area (latitude / longitude at the bottom left and top right), generate metadata including the client's location and the parameters, and publish the generated metadata to an MQTT broker. In this case, the metadata can be published to the MQTT broker through a metadata topic that is predefined / set in relation to publishing / subscribing to the metadata.

[0311] 2) The MQTT broker can determine / select a broker belonging to a corresponding geographical area based on the type of metadata (or V2X message / data) published by the publishing app or client and the properties (e.g., the parameters described above) for coverage. For example, referring to FIG. 24, the MQTT broker can determine MQTT broker 3 and MQTT broker 6 as MQTT brokers to relay the V2X message / data published by the publishing app or client based on the metadata. In this case, the V2X message published by the publishing app or client can be published to multiple subscribing apps or subscribing clients (e.g., subscribing apps or subscribing clients that subscribe to topics covered by MQTT broker 3 and MQTT broker 6) through MQTT broker 3 and MQTT broker 6. Alternatively, the metadata can be shared with apps or subscribing clients that are subscribed to the geographical area covered by MQTT broker 3 and MQTT broker 6.

[0312] 3) Subscription apps / subscription clients (e.g., subscription apps / subscription clients that subscribe to topics corresponding to geographic area 3 or geographic area 6 covered by MQTT broker 3 or MQTT broker 6) can subscribe to V2X messages / data published by the publishing app or client, and can display (Presentation) the subscribed V2X messages / data on the UI through rendering.

[0313] (2) Circle area type

[0314] 1) The publishing app or client can generate metadata including parameters for setting / defining a circle area corresponding to a circle area type. For example, the publishing app or client can determine parameters (center point, radius) for defining a circle area along with its location. The publishing app or client can generate metadata including the client's location and the parameters, and publish the generated metadata to an MQTT broker. In this case, the metadata can be published to the MQTT broker through a metadata topic that is predefined / set in relation to publishing / subscribing to the metadata.

[0315] 2) The MQTT broker can determine / select a broker belonging to a corresponding geographical area based on the type of metadata (or V2X message / data) published by the publishing app or client and the properties (e.g., the parameters described above) for coverage. For example, referring to FIG. 24, the server or MQTT broker can determine MQTT brokers to relay the V2X message / data published by the publishing app or client as MQTT broker 1, MQTT broker 2, MQTT broker 4, and MQTT broker 5 based on the metadata. In this case, the V2X message published by the publishing app or client can be published to multiple subscribing apps or subscribing clients (e.g., subscribing apps or subscribing clients that subscribe to topics covered by MQTT broker 1, MQTT broker 2, MQTT broker 4, and MQTT broker 5) through MQTT broker 1, MQTT broker 2, MQTT broker 4, and MQTT broker 5. Alternatively, the metadata may be shared with subscribing apps or subscribing clients for the geographic areas covered by MQTT Broker 1, MQTT Broker 2, MQTT Broker 4, and MQTT Broker 5.

[0316] 3) Subscribing apps / subscribing clients (e.g., subscribing apps / subscribing clients that subscribe to topics corresponding to geographic areas 1, 2, 4, or 5 covered by MQTT broker 1, MQTT broker 2, MQTT broker 4, and MQTT broker 5) can subscribe to V2X messages / data published by the publishing apps or clients, and can present the subscribed V2X messages / data on the UI through rendering.

[0317] (3) Line segment area type

[0318] 1) The publishing app or client can generate metadata including parameters for setting / defining a segment area of ​​a segment area type. For example, the publishing app or client can determine parameters (a list of latitudes / longitudes corresponding to multiple nodes) for defining a road line for delivering its message / data to road users who need it along with its location, generate metadata including the client's location and the parameters (e.g., coverage information), and publish the generated metadata to an MQTT broker. In this case, the metadata can be published to the MQTT broker through a metadata topic that is predefined / set in relation to publishing / subscribing to the metadata.

[0319] 2) The MQTT broker may determine / select a broker belonging to a corresponding geographical area based on the type of metadata (or V2X message / data) published by the publishing app or client and the properties (e.g., the parameters described above) for coverage. For example, referring to FIG. 24, the MQTT broker may determine MQTT broker 5, MQTT broker 8, and MQTT broker 9 as MQTT brokers to relay the V2X message / data published by the publishing app or client based on the metadata. In this case, the V2X message published by the publishing app or client may be published to multiple subscribing apps or subscribing clients (e.g., subscribing apps or subscribing clients that subscribe to topics covered by MQTT broker 5, MQTT broker 8, and MQTT broker 9) via MQTT broker 5, MQTT broker 8, and MQTT broker 9. Alternatively, the metadata may be shared with subscribing apps or subscribing clients for the geographic area covered by MQTT Broker 5, MQTT Broker 8, and MQTT Broker 9.

[0320] 3) Subscribing apps / subscribing clients (e.g., subscribing apps / subscribing clients that subscribe to topics corresponding to geographic areas 5, 8, or 9 covered by MQTT broker 5, MQTT broker 8, and MQTT broker 9) can subscribe to V2X messages / data published by the publishing apps or clients, and can present the subscribed V2X messages / data on the UI through rendering.

[0321] The technical effects of this method are as follows.

[0322] - Wide coverage: While PC5 is primarily limited to short-range infrastructure-based communications, V2N2X can cover a much wider area by leveraging cellular networks. This allows for selective transmission of information across a wide geographical area through server-to-server communication. For use cases such as road works or SAE's TIM and RSA messages, V2N2X can significantly improve road safety by quickly disseminating events over a wide area. By disseminating V2X messages over a wide area, drivers in a wide area can be quickly notified of an event. In particular, important safety information (road events such as road construction, accidents, and sinkholes) can be effectively transmitted to a wider range of vehicles, thereby improving road safety. In addition, while existing PC5-based propagation is a protocol stack that broadcasts V2X messages within a range or transmits them within the infrastructure, the new V2N2X layer can support efficient message transmission.

[0323] - Flexible geographic area definition: Various geographic areas such as rectangles, radii, line segments, and polygons can be defined in the V2N2X layer, allowing for optimized information to be provided according to the situation.

[0324] - Real-time information provision: The receiver subscribes to the metadata issued by the transmitter in real time, allowing it to immediately utilize the latest information appropriate to its current location.

[0325] - Effective message propagation: Network efficiency can be improved by reducing unnecessary data transmission and providing necessary information in a timely manner through optional metadata transmission.

[0326] 4. Solution 4: Defining the message validity period at the V2N2X layer

[0327] Figure 25 is a diagram for explaining a method of defining / setting the validity time of a message in the V2N2X layer.

[0328] Referring to FIG. 25, messageExpirationDuration, transmissionStartTime, and transmissionEndTime can be defined to set the message expiration time. Here, messageExpirationDuration can indicate the message expiration time. For example, if the value of messageExpirationDuration is "1", it can mean that the message is valid for 1 second after being published. transmissionStartTime can indicate the time when message transmission starts. transmissionStartTime can be useful when scheduling a message to be transmitted only at a specific time. transmissionEndTime can indicate the time when message transmission ends. transmissionStartTime can be used / defined when a message is not to be transmitted after a specific time.

[0329] For messageExpirationDuration, the publishing application or publishing app can include the @messageExpirationDuration property in the V2N2X layer to set the expiration time when publishing a message (e.g., BSM). The publishing app can set the expiration time of the message so that the message is valid only for a certain period of time after being published. For example, if @messageExpirationDuration=1000, the message can be valid only for 1000ms = 1 second after being published, and can be ignored after 1 second has passed. In this case, the broker and server can check the createdAt and messageExpirationDuration of the received message, and not deliver the message to the subscriber or subscribed device when the expiration time has passed.

[0330] For transmissionStartTime, the publishing app can set a message transmission start time to publish messages only at a specific time. This can be useful when scheduling is required based on the importance or urgency of the message. The publishing app can set the transmissionStartTime when publishing a message. When the time corresponding to the set transmissionStartTime arrives, the publishing app can transmit the message to the MQTT broker. For example, the publishing app can schedule a message to notify of road condition changes 60 minutes before road construction begins. Furthermore, the setting of transmissionEndTime is optional, and the setting / definition of transmissionEndTime may be omitted. In this case, the broker and server can check the transmissionStartTime of the received message and not deliver the message to the subscriber until the set time has arrived. The broker and server deliver the message to the subscriber or subscribing device (or subscribing client) only if the current time is after transmissionStartTime. The receiving app (or subscribing device) can be guaranteed that the message received from the broker is received after the preset transmissionStartTime. Because the broker and server perform pre-filtering, the receiving app may not notice that the message was sent after the transmission start time set for the message.

[0331] For transmissionEndTime, the publishing app (or publishing device) can set a message transmission end time, preventing the message from being published or relayed by the broker after a certain time. The publishing app (or publishing device) can publish a message with the transmissionEndTime set. The publishing app (or publishing device) can stop publishing the message after the set time has elapsed. The broker checks the transmissionEndTime of the received message and does not deliver the message to the subscriber or subscribing device after the set time has elapsed.

[0332] In this way, the proposed invention can guarantee cost-effective operation while reducing the burden of message transmission by introducing parameters related to the message's validity period. Furthermore, from a network perspective, it can effectively reduce network traffic.

[0333] Figure 26 is a drawing for explaining how the first device issues a message based on a message protocol.

[0334] As described above, the first device may be a client device that subscribes to and publishes messages based on the message protocol of MQTT or AMQP. The first device may establish a session with a network or a broker of the network related to the message protocol, and then publish or receive (or subscribe to) messages based on the session. Here, the publishing and receiving of the messages may be performed based on topic information related to a geographical area, etc. For example, the first device may define a publishing topic / subscription topic related to its location during an initial setup procedure with the network, and then request the network to subscribe to the defined subscription topic. Thereafter, the first device may receive / subscribe to messages from the network or the first broker based on the subscription topic. In addition, as described above, the first device may also obtain topic information (e.g., a meta topic) for subscribing or publishing metadata including coverage information for specifying / configuring brokers to which its messages will be relayed through the initial setup procedure or discovery procedure with the network. Meanwhile, the first device may be defined as a client, client device, or terminal, as a device that issues a message to a network or a first broker based on a message protocol, or receives a message from a network or a first broker.

[0335] Below, the operation on the side of the first device or client device is described in more detail based on the proposed invention described in FIGS. 16 to 25.

[0336] Referring to FIG. 26, a first device may establish a connection with a first broker among a plurality of brokers associated with a message protocol based on publication and subscription (S261). As described above, the first device may obtain information for accessing the first broker associated with itself through the initial setup procedure of the network or the first broker of the network, and may connect to the first broker based on the information. Here, the first broker among the plurality of brokers may be a broker that provides a service for relaying messages associated with the message protocol in a zone (or geographical area) associated with the location of the first device. For example, a plurality of zones may be pre-divided / separated for a preset geographical area, and a corresponding broker may be mapped to each zone. In this case, the first device may establish a connection / session for publishing / subscribing the message with the first broker, which is a broker corresponding to the zone to which the location of the first device belongs, among the plurality of brokers.

[0337] Next, the first device can publish metadata to the first broker using a meta topic (S263). As described above, the meta topic can be set / obtained for publishing or subscribing to the metadata during the initial setup procedure (or discovery procedure) with the network. Here, the metadata can include coverage information used to specify at least one broker to relay the message published by the first device as described above. For example, the metadata can include information about a coverage type as the coverage information and information about at least one location for defining the coverage of the coverage type. The coverage type can be defined as a circle area type, a square area type, a line type, or a polygonal type, as described with reference to FIG. 24. The coverage type can be set by the first broker or determined by the first device based on the surrounding environment. For example, when the first device is driving at a high speed in a certain direction, such as on a highway, the first device may determine the coverage type as a line type in consideration of the characteristics of the highway. In this case, the metadata may include information about the line type and / or information about a plurality of locations for defining a line of the line type. Alternatively, when the first device is driving in a city center where a plurality of intersections exist (i.e., movement in various directions is possible), the first device may determine the coverage type as a circular area type. In this case, the metadata may include information about the circular area type and information about the location and radius of the center point for defining the circular area. Alternatively, the scope of the coverage may be determined based on whether an event related to the first device has occurred.Here, the event may be a situation that may cause a road safety issue, such as a road accident, road construction, or the movement of an emergency vehicle, as described above. For example, if an event related to the first device does not occur / detect, the first device may determine / set the coverage range to a default range predefined for each type. Conversely, if an event related to the first device occurs / detects, the first device may determine / set the coverage range to a range wider than the default range predefined for each type.

[0338] Next, the first device can publish the first message to the first broker using the publication topic (S265). The first message can also be delivered to at least one broker specified / determined based on the metadata, and can be delivered / published by the at least one broker to a plurality of devices located in at least one zone corresponding to the at least one broker. For example, the first device can expand the brokers that relay the first message by publishing metadata including the coverage information to the first broker. In this way, by providing additional coverage information through the metadata, the first device can expand the brokers that relay the message, and by expanding the brokers, can provide client devices located in a wider geographic area with an opportunity to subscribe to the first message.

[0339] Alternatively, if a new event related to the first device occurs / detected, the first device may additionally issue metadata to extend the coverage range defined through the metadata.

[0340] Figure 27 is a diagram illustrating how a network relays a first message from a first device. Here, the network can also be defined as a server, an MQTT broker, or a broker.

[0341] Referring to FIG. 27, a network may establish a connection with a first device to provide a service related to a message protocol based on publication and subscription (S271). For example, the network may provide a message relay service, which is a service related to the message protocol, using a first broker. Furthermore, the network may be a server including the first broker, and the first broker may be a broker corresponding to a zone to which the first device is located among multiple brokers. As illustrated in FIGS. 21 and 24, a predefined geographic area may be divided into multiple zones, and a corresponding broker may be mapped to each zone.

[0342] Next, the network can subscribe to metadata from the first device based on the meta topic (S273). As described above, the metadata may include coverage information for additionally specifying at least one broker to relay the message of the first device among a plurality of brokers that relay messages related to the message protocol in the predefined geographic area. For example, the network may determine / specify at least one broker to additionally relay the message of the first device based on the coverage information included in the metadata. For example, as illustrated in FIG. 24, the network may determine a circular area, a rectangular area, a line area, or a polygonal area based on the coverage information, determine zones that can cover the circular area, the rectangular area, the line area, or the polygonal area, and determine at least one broker that provides services in the zones. In this case, the network may determine the at least one broker as a broker to additionally relay the message of the first device.

[0343] Next, the network can receive the first message published using the publication topic from the first device (S275). For example, the network can subscribe to / receive the first message using the first broker, and publish / relay the received first message to client devices located in a zone associated with the first broker. Furthermore, as described above, the network can also relay the first message to client devices located in other zones through other brokers. For example, the network can also forward the first message to at least one broker specified based on the metadata, so that the first message is also relayed to client devices located in at least one zone where the at least one broker provides a service.

[0344] Specifically, the network may determine at least one zone among the plurality of zones that covers the coverage determined based on the coverage information, and specify at least one broker that provides a service for the at least one zone. In this case, the network may also provide the message of the first device to the at least one broker using the first broker. For example, as illustrated in FIG. 21, the network may use the first broker to deliver the first message to the at least one broker through a message bridge of a server / network to which the at least one broker belongs. Specifically, the server / network may include a message bridge composed of a local client and a neighboring client (or a local client device and a neighboring client device). The message bridge may be composed of the neighboring client and the local client to connect brokers between different servers / networks. The neighboring client may subscribe to or publish messages from brokers of other servers / networks, and the local client may publish messages delivered from the neighboring client to an internal broker, or provide messages subscribed to from the internal broker to the neighboring client. For example, when a first broker of the network forwards the first message to a second broker of network 2, the first broker can publish / forward the first message to a neighboring client of the message bridge of network 2. In this case, the neighboring client of the message bridge of network 2 subscribes to the first message, forwards the subscribed first message to a local client of the message bridge of network 2, and the local client can publish the first message to the second broker. In this way, the network can effectively forward the first message to at least one broker specified based on the coverage information of the metadata.

[0345] In this way, the proposed invention can effectively provide V2X-related information through wider coverage by utilizing cellular networks. Alternatively, the proposed invention can effectively expand or reduce the scope of message issuance based on a message protocol by effectively coordinating brokers that relay device messages through metadata. Alternatively, the proposed invention can effectively expand or reduce the scope of message issuance based on a message protocol, thereby preventing messages from being unnecessarily transmitted to a wide range of devices or ensuring that information critical to road safety is transmitted to a wide range of devices.

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

[0347] 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.

[0348] 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.

[0349] Figure 28 illustrates a communication system applied to the present invention.

[0350] Referring to FIG. 28, 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.

[0351] 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).

[0352] 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.

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

[0354] Figure 29 illustrates a wireless device applicable to the present invention.

[0355] Referring to FIG. 29, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals via 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. 28.

[0356] 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.

[0357] 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.

[0358] Specifically, the processor (102) controls the transceiver (106) based on the at least one program to form a connection with a first broker among a plurality of brokers related to a message protocol based on publish and subscribe, publish metadata to the first broker using a meta topic, and publish a first message to the first broker using the publish topic. Here, the metadata may include coverage information for specifying at least one broker among the plurality of brokers to relay the first message.

[0359] Alternatively, a processing device may be configured, including at least one processor (102) and a memory (104) for controlling a first device. In this case, the processing device may include at least one processor; and at least one memory connected to the at least one processor and storing instructions that perform operations when executed by the at least one processor. The operations may include forming a connection with a first broker among a plurality of brokers related to a publish-and-subscribe based message protocol, publishing metadata to the first broker using a meta topic, and publishing a first message to the first broker using a publication topic. Here, the metadata may include coverage information for specifying at least one broker among the plurality of brokers to relay the first message.

[0360] 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.

[0361] 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.

[0362] Specifically, the processor (202) controls the transceiver (206) based on the at least one program to form a connection with a first device to provide a service related to a message protocol based on publication and subscription, subscribe to metadata from the first device based on a meta topic, and receive a first message published using the published topic from the first device. Here, the metadata may include coverage information for specifying at least one broker to relay the first message among a plurality of brokers that provide a service related to the message protocol based on publication and subscription.

[0363] 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.

[0364] 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.

[0365] 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.

[0366] 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.

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

[0368] Figure 30 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 28).

[0369] Referring to FIG. 30, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 29 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 30. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 29. 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).

[0370] 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. 28, 100a), a vehicle (Fig. 28, 100b-1, 100b-2), an XR device (Fig. 28, 100c), a portable device (Fig. 28, 100d), a home appliance (Fig. 28, 100e), an IoT device (Fig. 28, 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. 28, 400), a base station (Fig. 28, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0371] In FIG. 30, 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 a set of one or more processors. 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.

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

[0373] Figure 31 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.

[0374] Referring to FIG. 31, 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. 30, respectively.

[0375] 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.

[0376] 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.

[0377] 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.

[0378] 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.

[0379] 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).

[0380] 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.

[0381] 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.

[0382] 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.

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

Claims

1. In the method using the first device, A step of forming a connection with a first broker among a plurality of brokers related to a message protocol based on publish and subscribe; A step of issuing metadata to the first broker using a meta topic; and A step of publishing a first message to the first broker using a publishing topic; A method wherein the metadata includes coverage information for specifying at least one broker among the plurality of brokers to relay the first message.

2. In paragraph 1, A method, characterized in that the coverage information includes information about a coverage type and information about at least one location for defining coverage of the coverage type.

3. In paragraph 2, Each of the above plurality of brokers provides a relay service of messages related to the message protocol for one of the plurality of zones divided into preset geographic areas, A method, characterized in that said at least one broker is specified based on at least one zone covering said specific type of coverage among said plurality of brokers.

4. In paragraph 2, A method characterized in that the above coverage type is determined based on the surrounding environment of the device among a circle type, a polygon type, and a line segment type.

5. In paragraph 2, A method characterized in that the range of coverage of the above coverage type is determined based on whether an event related to the first device occurs.

6. In paragraph 2, A method characterized in that, based on the detection of an occurrence of an event related to the first device, the first device additionally issues the metadata to extend the scope of coverage of the coverage type.

7. In paragraph 1, A method, characterized in that the first message further includes information about the relay validity time of the first message.

8. In paragraph 1, A method, characterized in that the above message protocol is MQTT (Message Queuing Telemetry Transport) or AMQP (Advanced Message Queuing Protocol).

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, Forming a connection with a first broker among multiple brokers involved in a publish-and-subscribe based message protocol; Publishing metadata to the first broker using meta topics; and including publishing a first message to the first broker using a publishing topic, At least one non-transitory computer-readable medium recording medium, wherein the metadata includes coverage information for specifying at least one broker among the plurality of brokers to relay the first message.

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 processor controls the RF transceiver based on the at least one program to form a connection with a first broker among a plurality of brokers related to a message protocol based on publish and subscribe, publishes metadata to the first broker using a meta topic, and publishes a first message to the first broker using a publish topic. A first device, wherein the metadata includes coverage information for specifying at least one broker among the plurality of brokers to relay the first message.

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, Forming a connection with a first broker among multiple brokers involved in a publish-and-subscribe based message protocol; Publishing metadata to the first broker using meta topics; and including publishing a first message to the first broker using a publishing topic, A processing device, wherein the metadata includes coverage information for specifying at least one broker among the plurality of brokers to relay the first message.

12. In the method by network, A step of forming a connection with a first device to provide a service related to a message protocol based on publish and subscribe; A step of subscribing metadata from the first device based on a meta topic; and A step of receiving a first message published using a published topic from the first device, A method wherein the metadata includes coverage information for specifying at least one broker among a plurality of brokers that provide services related to the message protocol based on the publication and subscription to relay the first message.

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, Establishing a connection with a first device to provide services related to a publish-and-subscribe based messaging protocol; Subscribe to metadata from the first device based on the meta topic; and comprising receiving a first message published using a published topic from the first device; At least one non-transitory computer-readable medium recording medium, wherein the metadata includes coverage information for specifying at least one broker among a plurality of brokers that provide services related to the message protocol based on the publication and subscription to relay the first message.

14. In the network, 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 processor controls the RF transceiver based on the at least one program to form a connection with a first device to provide a service related to a message protocol based on publication and subscription, subscribes to metadata from the first device based on a meta topic, and receives a first message published using a publication topic from the first device. A network in which the metadata includes coverage information for specifying at least one broker among a plurality of brokers that provide services related to the message protocol based on the publication and subscription to relay the first message.

15. In a processing device that controls a network, 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, Establishing a connection with a first device to provide services related to a publish-and-subscribe based messaging protocol; Subscribe to metadata from the first device based on the meta topic; and comprising receiving a first message published using a published topic from the first device; A processing device, wherein the metadata includes coverage information for specifying at least one broker among a plurality of brokers that provide services related to the message protocol based on the publication and subscription to relay the first message.

Images