Method for transmitting message in wireless communication system and apparatus therefor

Abstract

Disclosed, according to various embodiments, are a method by which a first network transmits an MQTT-based message to a second network in a wireless communication system and an apparatus therefor. Disclosed are: a method comprising a step of receiving a first MQTT-based message published from a client through a first broker of the first network, and a step of transferring the first MQTT-based message to the second network; and an apparatus therefor.

Description

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

[0001] A method for transmitting MQTT (Message Queueing Telemetry Transport)-based messages between networks in a wireless communication system and a device therefor are disclosed.

[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 problem to be solved by the present invention is to provide a method for transmitting and receiving messages between networks more accurately and efficiently.

[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] In a wireless communication system according to one aspect, a method for a first network to transmit an MQTT (Message Queueing Telemetry Transport)-based message to a second network comprises the steps of: receiving a first MQTT-based message published from a client through a first broker of the first network; and transmitting the first MQTT-based message to the second network, wherein the first MQTT-based message can be transmitted through a bridge including a first client that has formed a first session with the first broker and a second client that has formed a second session with a second broker of the second network.

[0018] Alternatively, the first client is characterized in that it provides the second client with a second MQTT-based message in which the MQTT protocol layer is removed from the first MQTT-based message.

[0019] Alternatively, the second client is characterized in that it converts the second MQTT-based message into a third MQTT-based message including an MQTT protocol layer related to the second network, and publishes the third MQTT-based message to the second broker.

[0020] Alternatively, the second session is characterized in that it is formed only by the initial connection procedure of the second client, based on the first network providing a service related to the MQTT-based message through a WVL (wavelength) zone that is not connected to a public IP (Internet Protocol).

[0021] Alternatively, the initial connection procedure is characterized in that it is performed using the IP and port of the second broker.

[0022] Alternatively, the second client is characterized in that it is connected to the second broker based on TCP (Transmission Control Protocol) or UDP (User Datagram Protocol).

[0023] Alternatively, the MQTT-based message is characterized as a message for providing a V2X (Vehicle to Everything) service through a network.

[0024] Alternatively, the second network is characterized by being a different MEC (Multi-Access Edge Computing) platform from the first network or an application server for a different service entity from the first network.

[0025] According to another aspect, a first network may be provided that performs the method of transmitting the above-described MQTT (Message Queueing Telemetry Transport) based message to a second network.

[0026] According to another aspect, a processing device may be provided for controlling a first network to forward the above-described MQTT (Message Queueing Telemetry Transport) based messages to a second network.

[0027] According to another aspect, a method for a second network to receive an MQTT (Message Queueing Telemetry Transport)-based message in a wireless communication system includes: receiving a first MQTT-based message from a first network using a second broker of the second network; and publishing the first MQTT-based message to a plurality of clients that subscribe to a topic related to the first MQTT-based message using the second broker, wherein the first MQTT-based message can be received from a bridge of the first network, the bridge including a first client that has formed a first session with a first broker of the first network and a second client that has formed a second session with the second broker.

[0028] According to another aspect, a non-transitory computer-readable storage medium having recorded thereon instructions for performing the method of receiving an MQTT-based message as described above may be provided.

[0029] According to another aspect, a second network may be provided that performs the method for receiving MQTT-based messages described above.

[0030] According to another aspect, a processing device may be provided for controlling a second network that performs the method for receiving MQTT-based messages described above.

[0031] According to various embodiments, messages can be transmitted and received between networks 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 drawing for explaining the architecture of the V2N interface.

[0050] Figure 17 is a diagram for explaining the connection structure between two servers providing SoftV2X service.

[0051] Figure 18 is a drawing for explaining interfaces related to the connection structure between two servers providing SoftV2X services.

[0052] Figure 19 is a drawing for explaining the type of bridge connecting two servers.

[0053] Figure 20 is a diagram illustrating how MECs for different carriers are connected through a bridge.

[0054] Figures 21 and 22 are drawings for explaining data processing of the bridge.

[0055] Figure 23 is a diagram for explaining a structure connected between different MECs and servers through an inter-MEC bridge and an inter-Service bridge.

[0056] Figure 24 is a diagram illustrating how a first network transmits an MQTT-based message to a second network.

[0057] Figure 25 is a diagram illustrating how a second network receives an MQTT-based message from a first network.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0095] - Satellite integrated network

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

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

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

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

[0100] - small cell networks

[0101] - Ultra-dense heterogeneous network

[0102] - High-capacity backhaul

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

[0104] - Softwarization and virtualization

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

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

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

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

[0109] - Large-scale MIMO technology

[0110] - Hologram beamforming (HBF)

[0111] - Optical wireless technology

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

[0113] - Quantum communication

[0114] - Cell-free communication

[0115] - Integration of wireless information and power transmission

[0116] - Integration of wireless communication and sensing

[0117] - Integrated access and backhaul network

[0118] - Big data analysis

[0119] - Reconfigurable intelligent surface

[0120] - metaverse

[0121] - Blockchain

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0152] PSBCH (Physical Sidelink Broadcast Channel) may be a (broadcast) channel that transmits basic (system) information that a terminal must know first before transmitting or receiving an SL signal. For example, the basic information may be information related to SLSS, duplex mode (DM), TDD UL / DL (Time Division Duplex Uplink / Downlink) configuration, resource pool-related information, type of application related to SLSS, subframe offset, broadcast information, etc. For example, in 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).

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

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

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

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

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

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

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

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

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

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

[0163] Meanwhile, the SoftV2X service or SoftV2X system is a system in which a SoftV2X server receives a VRU message or a PSM (Personal Safety Message) from a VRU (Vulnerable Road User) or a V2X vehicle through a UU interface for V2X communication, and transmits information on surrounding VRUs or vehicles based on the VRU message or PSM message, or analyzes the road conditions on which surrounding VRUs or vehicles are moving, and transmits a message to notify surrounding VRUs or vehicles of a collision warning based on the analyzed information. Here, the VRU message or PSM message is a message transmitted to the SoftV2X server through the UU interface, and may include mobility information on the VRU, such as the location, moving direction, moving path, and speed of the VRU. In other words, the SoftV2X system receives mobility information on VRUs and / or vehicles related to V2X communication through the UU interface, and 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.

[0164] Below, a method for providing V2X services through a network based on the above-described contents is described in detail.

[0165] Network-to-network interface structure using messaging protocols in V2N services

[0166] V2X services play a significant role in ensuring safety, including collision prevention, and efficiently controlling traffic flow by allowing road users (vehicles, RSUs, pedestrians, etc.) to communicate with surrounding road users about their status information (location, speed, size, etc.) or environmental information (maps, signal information, etc.). Currently, various V2X services using various communication methods (short-range communication, long-range communication) exist, and service level requirements (SLREs) have been defined to ensure the organic operation of V2X services involving multiple ITS stations.

[0167] These V2X messages can be generated by vehicles and infrastructure to convey information about the surrounding environment, road conditions, situations, and events. V2X messages can be used for various purposes, such as vehicle-to-vehicle interaction, vehicle-to-infrastructure communication, object detection, and warning systems. V2X messages can be generated by vehicles or infrastructure and can contain information about the surrounding environment, situations, and events. Furthermore, V2X messages can include information collected through the vehicle's sensors, GPS information, and communication devices, and can be structured in a standardized format. These standardized V2X messages can include various data, such as location, speed, acceleration, lane change information, and traffic light status. Alternatively, V2X messages can be transmitted in one direction or two directions, and the information contained in the V2X messages can be updated and processed in real time. In V2X environments that require low-latency communication, rapid message transmission is essential, and a delay time of several milliseconds or less can be very important for rapid situational responses, such as accident prevention or collision warning. Furthermore, because V2X message-based communication relies on real-time interaction between vehicles and infrastructure, message delivery speed and reliability can play a critical role in ensuring timely driver alerts and vehicle response to situations. Therefore, V2X message communication requires minimizing message delivery speed and delay, and must be designed based on network technologies and protocols suitable for real-time communication, including appropriate buffering models and transmission methods for rapid data exchange.

[0168] In addition, V2X services can be provided (i.e., provision of SoftV2X services) not only through direct communication between devices but also through connections via a network (V2N) as described above. Here, a messaging protocol for V2N communication via a network (or server) can play an important role in improving the ease of communication. In particular, among the message protocols, MQTT (Message Queueing Telemetry Transport) can include the components of a client, a server, and a broker as its core components. Such a message protocol can be connected to multiple clients through a broker that performs a relay role based on the IP protocol. The client can publish messages and subscribe to topics using the MQTT protocol. A server, network, or MEC (hereinafter, “server”) can accept connections from clients, manage connections, and route and relay messages. The server is generally referred to as an MQTT broker or can include an MQTT broker. An MQTT broker (or broker) can be a central server that relays and coordinates communications between MQTT clients (clients), forwarding messages published by clients to other clients subscribed to topics corresponding to those messages. This V2N communication can provide enhanced services that handle diverse information by interconnecting information from different operators, countries, and regional infrastructures.

[0169] The connectivity architecture for providing such V2X services is being considered as a V2N2X (or V2N or SoftV2X) architecture that extends to network scope. This architecture can be schematically designed at a high level, depending on the requirements of vehicles, infrastructure, service providers, and information sharing instances to satisfy specific use cases. Below, the V2N architecture is described in detail.

[0170] Figure 16 is a drawing for explaining the architecture of the V2N interface.

[0171] Referring to Fig. 16, the architecture of the V2N interface (or SoftV2X interface) may be composed of an Infrastructure Owner Operator (IOO) AS (Autonomous System), a V2N Original Equipment Manufacturer (OEM) AS, a V2N OEM App, a V2N Service Provider (SP) AS (V2XAS), and an Information Sharing instance. The specific definitions of each component are as follows.

[0172] Infrastructure Owner Operator (IOO) AS: A local actor providing services related to the automotive and transportation domain, often based on its own sensors and infrastructure such as roads and parking. Examples include cities, road authorities, road operators, municipalities, or parking providers.

[0173] - V2N OEM AS: An OEM backend component (e.g., control) that manages the V2N OEM App in the vehicle OEM domain can allow vehicle connectivity. The OEM AS acts as a proxy and filter for information transmitted and received from the vehicle OEM App.

[0174] - V2N OEM App: An in-vehicle component that implements service functions for service users in the vehicle OEM domain. For the service to function, the app must receive data from other system components. Depending on the situation, it can implement functions that alert the human driver or support the vehicle's ADAS / AD functions.

[0175] - V2N Service Provider (SP) AS (V2XAS): In the service provider domain, V2N Service Provider Application Server (V2N SPAS) is a general term for an actor that provides services related to the automotive domain, such as VRU protection service, MAP service, traffic information service, and fleet operator service.

[0176] - Information Sharing Instance: An entity that connects each AS, enabling information across national or regional boundaries to be linked. For example, it can act as a rendezvous server, hosting servers seeking connections and acting as an intermediary to establish connections. Furthermore, it can also perform appropriate translation functions when relaying messages from non-standard entities, as needed.

[0177] Meanwhile, to provide the aforementioned V2N-based V2X service, the server-to-server interface is defined only at a high-level or conceptual level, without defining the fundamental requirements for connection. Therefore, a structure that considers the actual implementation of server-to-server connections for actual V2N requires clearly defining the following requirements.

[0178] (1) Structure compatible with message exchange protocol

[0179] For example, if it is built with the message exchange protocol structure of the existing MQTT (Message Queuing Telemetry Transport) / AMQP (Advanced Message Queuing Protocol), the interface must be built through the client-broker-client structure. In addition, an interface that satisfies the bidirectional publish / subscribe must be built according to the transmission direction of each data / message. Here, MQTT is a lightweight messaging protocol designed for low power, low bandwidth, and reliable communication. It can be mainly used in IoT devices with limited resources. The client can be configured as a publish / subscribe model that publishes messages to a topic or subscribes to a specific topic to receive messages, and a broker that receives the published messages and publishes the delivered messages to clients that have subscribed to them.

[0180] (2) Maintain compatibility with standard message formats

[0181] To maintain protocol compatibility or message standard compatibility, appropriate translation or filtering functions may be required. Interfaces (those connecting two operating systems or two networks) may need to include such translation or filtering functions and may require a structure for publishing to external servers in a pre-client / post-client format. Conversely, data / messages received through message subscriptions from external servers may require translation or filtering functions to suit a specific company's operations. In this case, the interface may require a client that republishes the translated data / messages to suit the operation of the receiving network.

[0182] (3) Message relay function and additional logic within the bridge

[0183] The data / messages re-issued by each client need to be relayed through appropriate message handling or processed according to additional logic.

[0184] Meanwhile, the connection structure according to the aforementioned additional requirements requires consideration of the "interchange" process in messaging protocols. "Interchange" generally refers to a process or tool for exchanging and converting messages between different messaging protocols or data formats. Interchange can be a configuration that ensures interoperability / compatibility between different servers / brokers (or different messaging systems) and supports the process of collecting and exchanging messages / data (hereinafter, "messages") from various servers.

[0185] However, in the connection between two networks related to the MQTT protocol, the following additional problems "(1)" and "(2)" may occur.

[0186] (1) Direct connection between MQTT broker and other MQTT brokers is not possible.

[0187] An MQTT broker typically acts as an intermediary, connecting to at least one client. Direct communication between the two brokers is impossible. Therefore, the bridge described above may require the introduction of a bridge configuration, as it serves as a bridge between two MQTT brokers.

[0188] Specifically, the bridge may be configured to connect between an internal broker belonging to its corresponding system / operating server and an external broker belonging to another system / operating server. In this case, since direct connection between two brokers based on the MQTT message protocol is impossible, the bridge may be configured to include a paired client for each broker, and the two brokers may be connected using the paired client for each broker. For example, the bridge may be configured to include two symmetrically arranged clients (or two virtual clients). Here, the two clients may include an internal client connected to the internal broker and an external client connected to the external broker, and may be configured to exchange data / messages with each other through internal communication.

[0189] Meanwhile, Multi-Access Edge Computing (MEC) is a computing paradigm that brings computational resources and services closer together in multi-access edge computing environments, such as 5G servers. MEC performs data processing and computation at the edge node, saving server bandwidth, minimizing latency, and supporting a variety of real-time and ultra-low-latency applications. Meanwhile, telecommunications companies can provide and manage MEC environments to offer customers a variety of edge computing services, enabling them to run their own services and applications or utilize MEC-based services. Implementing messaging protocols in these MEC environments can be a complex process requiring various technical and management considerations. Therefore, a new deployment model needs to be defined and designed to address the aforementioned challenges.

[0190] (2) In the connection between brokers, the source of all subscription messages is unknown.

[0191] In order to support interoperability based on message exchange protocols in a V2N environment (or V2N2X environment), it may be necessary to identify issues by defining the source of subscribed data / messages, and respond to the discovered issues. When establishing / forming a connection based on the MQTT protocol, the broker's IP / port and topic identification information can typically be used. However, in a V2N environment (or V2N2X environment), clients connected to the broker receive messages from multiple sources, not just one, making it difficult to identify the source or origin of the message through the broker's IP. In this way, if the source of the message is not confirmed, it may be difficult for the external server that ultimately receives the message to determine which server / client the message was delivered from and whether it was properly received. The MQTT standard, which is a protocol that supports message exchange within the current standard (5G Automotive Association; 5GAA) or typical distribution model, does not define a data identifier for the Facility layer. Additionally, V2X messages in the Facility layer do not define the information on the entity transmitting the message. As such, the source of the message's transmission entity is unclear in the current MQTT standard, so an extension to the configuration that can identify the source may be necessary. Furthermore, a broker connected to an interchange (or information sharing instance) receives data / messages from a collection of multiple clients, making it impossible to determine which company / server the message originated from.

[0192] Below, specific solutions to the above-described problems that may arise in the connection structure between two servers (or servers / MECs / networks of different operators) for providing SoftV2X services are described in detail.

[0193] Figure 17 is a diagram for explaining the connection structure between two servers providing SoftV2X service.

[0194] Referring to FIG. 17, application servers (120, 220) may be established in MECs (100, 200) of each telecommunications company's area. For example, the MEC (100) of Company A (e.g., telecommunications company, MEC operator) may include a first server (120) and a bridge (110) for SoftV2X service, and the MEC (200) of Company B may include a second server (220) that provides SoftV2X service. A messaging protocol connection between the MEC (100) of Company A and the MEC (200) of Company B may be established through the bridge (110).

[0195] The flow of data / message in the messaging protocol connection between the MEC (100) of Company A and the MEC (200) of Company B is as follows.

[0196] - ① Data / message of an application (e.g., an application for SoftV2X) of a device (or, issuing client) equipped with a SIM (Subscriber Identification Module) card of Company A can be transmitted to a first server (or, App server; 120) in A's MEC (100) via a base station. The first server (120) can transmit / issue the data / message issued from the device to a subscribing client (or, subscribing client) and a bridge (110).

[0197] - ② The bridge (or, Inter MEC Bridge; 120) can subscribe to / receive data / messages from the first server through a client (e.g., an internal client or an internal bridge) that is subscribing to data / messages from the first server.

[0198] - ③ The internal client (111) can transmit data / message issued from the first server (120) to the external client (or, External bridge; 113). Meanwhile, for convenience of explanation, in the following description, socket communication is performed between the internal client (111) and the external client (113), but the present invention is not limited thereto and messages / data can be exchanged with each other through various communication methods (e.g., memory sharing, etc.).

[0199] - ④ The external client (113) can issue / relay data / message received from the internal client (111) to the broker of Company B's MEC (200) (i.e., the broker of the second server; 221).

[0200] - ⑤ The broker (221) of the second server (220) can publish data / messages issued from the external client (113) to clients (and / or servers) that are subscribed (i.e., subscribed to a related topic).

[0201] - ⑥ The application of the device equipped with the SIM card of the above Company B can ultimately receive the data / message issued by the broker (221) of the second server.

[0202] Figure 18 is a drawing for explaining interfaces related to the connection structure between two servers providing SoftV2X services.

[0203] Referring to FIG. 18, one MEC or V2X system (100) includes a UE (or, RSU, server; 140) that transmits and receives V2X messages, a first server (120) that provides SoftV2X services, and a bridge (110), and can exchange data / messages with external brokers (221) using the bridge (100).

[0204] Such a connection structure can be connected based on at least one interface among interface 1 (①) to interface 5 (⑤). The connection structure and operation method for each interface can be defined as follows. Meanwhile, at least one of the interfaces below can be an interface using a messaging protocol based on MQTT, and for the convenience of explanation, an MQTT-based client / MQTT-based broker is defined as a client / broker and explained.

[0205] (1) Interface 1 (①)

[0206] Interface 1 (①) may be an interface connected between UEs (140) that generate and transmit V2X messages and the first server. The UE (or RSU, server, etc.) may be a message publisher or a client that subscribes to the message.

[0207] (2) Interface 2 (②)

[0208] Interface 2 (②) may be an interface connecting a broker (121) of the first server (120) and a bridge (client (-message relay module) - client) that connects a messaging protocol to the outside. Interface 2 (②) may exchange data / messages that are compatible with a standard format based on MQTT (a message format defined in the standard of 5GAA), or may exchange data / messages using a standard-incompatible message or protocol format that the first server (120) itself operates.

[0209] (3) Interface 3 (③)

[0210] Interface 3 (③) may be an interface connecting an internal client (111) and an external client (113) included in a bridge (110). Alternatively, interface 3 (③) may be an interface connecting an internal client (111), a message relay module (115), and an external client (113). Meanwhile, at least one of the two clients in interface 3 (③) may directly perform a function corresponding to the function of the message relay module (115), and in this case, the message relay module (115) may be omitted.

[0211] Specifically, interface 3 (③) may be an interface that relays a message payload decoded by the MQTT protocol stack in the internal client (111) to the external client (113). The data / message relayed by the internal client (111) through interface 3 (③) may have a different message format from the data / message received through interface 2 (②). For example, the data / message received through interface 2 (②) may be a message in which additional fields / data are defined for the V2X system or the first server (120) to provide data / message for its own operation and / or V2X service to the user more quickly and efficiently, but the message relayed through interface 3 (③) may be a pure standard message according to a standard format (see 5GAA TR-239129).

[0212] For example, the internal client (111) can remove the MQTT protocol stack (layer) from data / message received through interface 2 (②) and transmit the message in a pure standard format with the MQTT protocol stack removed to the external client (113). Alternatively, the internal client (111) can convert data / message received through interface 2 (②) into a message corresponding to the message protocol of the external server.

[0213] (4) Interface 4 (④) and / or Interface 5 (⑤)

[0214] Interface 4 (④) may be an interface connecting an external client (113) and an external broker (221). Here, interface 4 (④) may be an interface for exchanging data via a TCP session connection. In this case, the external client (113) and the external broker (221) may initialize / set each other's transmission / reception IP / Port / Topic and configuration information in advance. Alternatively, the external client (113) may convert data / message with the MQTT protocol stack removed transmitted from the internal client (111) into data / message with the MQTT protocol stack associated with the external broker, and may publish / transmit the converted data / message to the external broker (221).

[0215] Interface 5 (⑤) may be an interface connecting an external client (113) and an external broker (221) via a UDP session connection. The UDP-based external client may transmit messages / data transmitted from interface 3 (③) to the broker (or interchange(s)) of a second server in a unidirectional manner.

[0216] Below, we will describe in more detail the bridge that connects the two servers / networks.

[0217] Figure 19 is a drawing for explaining the type of bridge connecting two servers.

[0218] Referring to FIG. 19, the bridge (110) may include an Inter-MEC bridge for connecting different MEC platforms and an Inter-service bridge for connecting app servers of different service entities. The specific details are as follows.

[0219] - Inter-MEC Bridge: An Inter-MEC Bridge can be a bridge connecting various MEC platforms. For example, an Inter-MEC Bridge can be a bridge connecting various MEC platforms hosting app servers of the same service provider. It can comply with MQTT protocol interaction. An Inter-MEC Bridge can connect MQTT brokers of different MEC platforms through symmetric MQTT clients. An Inter-MEC Bridge can establish TCP sessions between MQTT brokers to exchange real-time data and perform 'publish and subscribe' operations for MEC interoperability.

[0220] - Inter-service bridge: An inter-service bridge can be a bridge that connects app servers of different service entities through mutual exchange. It can comply with MQTT protocol interactions. An inter-service bridge can also connect MQTT brokers on different MEC platforms through symmetric MQTT clients. An inter-service bridge can be designed to establish TCP sessions between MQTT brokers to perform "publish and subscribe" operations for real-time data exchange and service interoperability.

[0221] That is, the two types of bridges (110) may include an internal client (111) connected to the broker (121) of the first server and an external client (113) connected to the broker (221) of the second server to connect two brokers (121, 221) that cannot be directly connected to each other in relation to inter-service or inter-MECs.

[0222] Figure 20 is a diagram illustrating how MECs for different carriers are connected through a bridge.

[0223] Referring to Figure 20, Company A's MEC (cloud-based Wavelength Zone; 100) and Company B's MEC (local zone; 200) are connected via a bridge.

[0224] Meanwhile, Company A's MEC (100) can provide SoftV2X service through Wavelength Zone (WVL). In this case, since WVL is not a shared resource, unlike a local zone (LZ) that is freely accessible via the Internet, it cannot be accessed via the Internet and can only be accessed using a SIM card related to Company A. For example, Company A's MEC (100) can only be accessed through a mobile communication network based on Company A's SIM card. In this case, an issue such as "TCP / UDP-initiation from LZ (local zone) to MEC (Wavelength Zone) is not allowed via IGW (Internet Gateway)" may occur. That is, Company B's MEC (200) or the broker (221, 311) of the second server cannot directly establish a session for the WVL of Company A's MEC (100).

[0225] In relation to the above-described issue, since a client using the first server (110) of Company A's MEC (100) can connect to Company B's MEC (200) via the Internet (via a public IP), a connection in the opposite direction (i.e., from Company A's WVL to Company B's MEC) may be possible. In general, a messaging protocol can operate through a connection between a client and a broker. When a session is connected between a client and a broker, the client and the broker can continuously exchange data / messages. The client can connect the session with an external broker (221, 331) via the broker IP and port. At this time, the external broker (221, 331) cannot request a session connection to the client using the first server (110) of Company A's MEC (100). Therefore, the external client (113, 133) first needs to establish a session with the external broker (221, 331) via the IP / port of the external broker (221, 331).

[0226] Specifically, the bridge (110) may attempt to establish a session connection with the broker (121) of the first server (120) using the internal client (111) and exchange data / messages with the broker (121) through the session connection. In addition, the bridge (110) may first attempt to establish a session connection with the external broker (221) using the external client (113) and exchange data / messages with the broker (221) through the session connection. Ultimately, the bridge (110) needs to first establish a connection and session with the broker (121) of the first server in a client-broker relationship using the internal client (111) and first establish a connection and session with the broker (221) of the second server in a client-broker relationship using the external client (113). Additionally, to perform such a connection procedure, the bridge (110) must be included in the first MEC (100) related to the WVL among the first MEC (100) and the second MEC (200). For example, the bridge (110) may be configured to be included in the first MEC (100) that provides service as a wavelength zone among the first MEC (100) and the second MEC (200).

[0227] Meanwhile, the internal client (111) and the external client (113) can exchange / share data in real time through an internal interface. Here, the internal interface can be applied with various interfaces capable of exchanging data in addition to the interface for transmitting MQTT-based messages described above. Alternatively, the internal client (111) and the external client (113) can also exchange data / messages through memory copying at the socket level.

[0228] That is, the proposed bridge (110) can solve two issues that may arise in connection with the connection structure between different MEC platforms or service providers (Company A or Company B). First, the bridge (110) can solve the problem of not being able to directly connect between MQTT-based brokers by configuring it to include two symmetrical clients. Second, the bridge (110) can solve the problem of "TCP / UDP-initiation from LZ (local zone) to MEC (Wavelength Zone) is not allowed via IGW (Internet Gateway)" by configuring the two clients to first request a session connection to the corresponding broker.

[0229] In this way, the bridge can connect brokers for different servers using the internal client and the external client without the occurrence of the issues / problems described above. The internal client and the external client can relay / forward data / messages transmitted by the broker of the first server to the broker of the second server through the internal interface.

[0230] Furthermore, the above-described bridge can relay messages / data between two servers based on improved functions and logic, and the improved functions and logic of the bridge are described in detail below.

[0231] Bridge Advanced Features and Logic

[0232] Figures 21 and 22 are drawings for explaining data processing of the bridge.

[0233] Data / messages related to typical V2X services are transmitted from V2X entities or V2X systems (app, infra (e.g., RSU), server) to a corresponding MQTT-based broker based on appropriate filtering information (e.g., geographical information), and can be transmitted to a V2X application server through a session pre-connected with the broker. At this time, data / messages of V2X services of V2X entities may need to move to another external server (or, MEC, server, network, AS). For this purpose, the V2X application server can be connected to the external server using the above-described bridge. As described above, the bridge may include a symmetric TCP-based internal client and external client in order to maintain the receive / subscribe structure of the existing TCP-based client in the connection between two servers applying the message protocol.

[0234] Referring to Figure 21, the internal client can forward messages delivered by the first brokers to the external client after data processing according to additional logic.

[0235] Each configuration illustrated in Figure 21 can operate as follows. For convenience of explanation, the following description assumes that data / messages are issued from the first brokers, but the same can be applied to the direction in which data / messages are issued from the second brokers of an external server (only the sender / receiver entity is different).

[0236] (1) Sender

[0237] Entities that generate and transmit data (app, infrastructure (e.g. RSU), server) can packetize and transmit data according to a transmission protocol (e.g. MQTT protocol) through connected (or to be connected) brokers (broker A, broker B, broker C, ..., broker N).

[0238] (2) Recipient

[0239] The receiver can receive and process data transmitted from the sender and the network. The receiver (reception-side) accepts data transmitted from the sender and the network, decrypts packets, and reconstructs them into the intended message. Data for additional functions beyond the pure message data can support filtering for external transmission. For example, the receiver may be the external client described above.

[0240] (3) Data processing

[0241] Data processing involves classifying data / messages from the sender through appropriate data processing and connecting them to the appropriate data interfaces to facilitate appropriate data exchange. Data processing can be performed by function as described below. Alternatively, the data processing can be performed on an application server or internal client.

[0242] 1) Data receiver

[0243] A data receiver (or internal client) can receive data / message from a sender and perform decoding according to a transmission protocol and encoding stream method. The data receiver can verify the occurrence time of the message obtained during the decoding process (e.g., verified through XML (Extensible Markup Language) data of the message). The data receiver can transmit information about the occurrence time of the verified data / message to a database tree so that the data / message can be databased according to the occurrence time of the verified data / message. In this case, the occurrence time of the message can be set as a default parameter.

[0244] 2) Database tree

[0245] The database tree may be configured as a tree-type database (e.g., a Red Black tree) that classifies received data / messages in a relational database format based on the time of message generation. The database tree may be linked to an algorithm of a data processing manager to configure a database that classifies received data / messages based on the degree of correlation between additional information (geographical, direction, speed, velocity, etc.) based on the time of message generation. Alternatively, the internal client may configure the database to have the above-described data tree.

[0246] 3) Data Processing Manager

[0247] The data processing manager may include an algorithm capable of creating a tree structure within the database and a Tx buffer balancer. The algorithm may be an Application Programming Interface (API) for constructing a tree within the database based on parameters of data / messages. The buffer balancer may perform appropriate buffering and queuing of data / messages contained in the database, and may manage how to encapsulate the queued data / messages. Alternatively, the internal client may include a data processing manager.

[0248] 4) Network interface

[0249] The network interface can encapsulate the queued data using the necessary stack in the network domain and prepare to transmit a message containing the encapsulated data.

[0250] The functional units of the bridge (110) can adaptively turn on / off the data processing function to adjust / control buffering according to the insertion situation of packets based on the size or priority of the database.

[0251] Below, embodiments for establishing a connection with an external server (or external network) in a message (e.g. BSM) / data exchange via the Uu interface are described in detail.

[0252] Referring to Fig. 22, a transmission entity or V2X entity (Application, Infrastructure (RSU), server) can create / publish a message for a topic subscribed to by a client. The message can include a specific topic and a BSM payload. The message can be encapsulated according to the network stack, and if based on MQTT, it can be transmitted to the client through a broker. At this time, if the message is required to be exchanged with an external entity or external server, the necessary data can be deleted only from the corresponding server in the message, or the data processing process in Fig. 21 can be performed.

[0253] For example, the internal client can remove / filter specific extension fields / bit strings, use of additional fields of the message, optional fields (or MQTT protocol layer) that are difficult to be compatible with other applications, from a message subscribed / received (e.g., BSM) through interface 2 (② of FIG. 18), and transmit the filtered message to the external client through interface 3 (③ of FIG. 18). The external client is a client that can convert data / messages that are compatible with the protocol of an external server (or an external network), and can relay the filtered message from the internal client to the external server through interface 4 or interface 5 (④ or ⑤ of FIG. 18) while maintaining the structure of MQTT subscription and publication. When connecting data of an external server, the above-described connection structure that enables internal service operation based on the structure of subscription and publication may be required.

[0254] A transport entity or V2X entity (Application, Infrastructure (RSU), server) can publish (or transmit) data / messages (BSM) encoded with a transport network stack to a broker for clients registered for subscription. The broker can check the connection information of the subscribed clients and transmit the data / messages to the clients. Among the clients, an internal client included in the bridge can decode / parse the transmitted data / messages to create a database.

[0255] For example, referring to FIG. 22, the internal client can check information such as @TemploraryID, @Dsecond of the data / message (or BSM), and configure / determine the classification / priority to construct a tree in the database based on the confirmed information. Here, the occurrence time of the message (@Dsecond) is reference information for detecting the risk of collision as quickly as possible and issuing a warning within an appropriate time, and the V2X service must guarantee transmission / delivery of the message from the message occurrence time to the validity time before providing the safety message to the user. However, data / messages received from multiple entities may not be transmitted sequentially to correspond to the occurrence time. Therefore, the bridge or internal client can construct a database tree based on the information of @TemploraryID, @Dsecond of the data / message, and schedule data / message to be queued first based on the database tree. Specifically, the bridge or internal client can construct a database tree using the similarity of mobility information based on the occurrence time (or, effective time) of the data / message, analyze the fields of the data / messages received from various entities using the above-described algorithm, and periodically perform additional sorting of the arrays. The database tree constructed in this way can determine the output size (or, queuing size) of an appropriate message to be delivered / relayed through a queuing indication of a Tx buffer balancer. The message to be delivered / relayed can be encapsulated based on the network stack and transmitted / relayed to defined clients (e.g., external clients) through a delivery manager.At this time, there may be at least one external client, and the internal client may additionally include a client ID mapped according to the transmission type of UDP / TCP to transmit / relay the message to the external client. For example, client_id = 0 may be defined as a client that supports TCP transmission, and client_id = 1 may be defined as a client that supports UDP transmission. As described above, data / message with Client_id = 0 may be transmitted / delivered to a TCP-based connected external client (or interchange or broker). Data / message with Client_id = 1 may be transmitted / delivered to an external client (or interchange or broker) that supports UDP transmission.

[0256] Meanwhile, if there are multiple clients subscribing to the broker on the second server, or if the broker is an MQTT or AMQP broker acting as an interchange, an additional issue may arise where the source of data / messages transmitted through the bridge cannot be clearly identified. The following details solutions to this issue.

[0257] Figure 23 is a diagram for explaining a structure connected between different MECs and servers through an inter-MEC bridge and an inter-Service bridge.

[0258] Referring to FIG. 23, a first network (or, first MEC; 100) is connected to a broker (220) of an interchange (210) of a second network (or, second MEC; 200) via an Inter-MEC bridge (110), and is connected to a broker (260) of an app server (CMS App server; 250) of the second network (200) via an inter-Service bridge (130). The interchange (210) may be connected to first clients (221, 223, 225), and the broker (260) of the app server (250) may be connected to second clients (231, 233, 235).

[0259] At least one of the first clients (221, 223, 225) and the second clients (231, 233, 235) can transmit data / message to the SoftV2X server (210) via the broker (220, 260). In this case, each of the interchange (210) and the app server (250) can transmit data / message issued from at least one client to the Inter-MEC bridge / Inter service bridge (110, 130) subscribing to the internal MQTT broker (220, 251). The Inter-MEC bridge / Inter service bridge (110, 130) can receive data / message via the external client (or, External Bridge; 113, 133) and forward the received data / message to the internal client (or, internal Bridge; 111, 131). At this time, the external client (113, 133) can decapsulate all protocol layers from the received data / message and transmit pure data / message (data / message composed only of standard format) to the internal client (111, 131). The internal client (111, 131) can publish / transmit the data / message transmitted from the external client (113, 133) to the subscribing SoftV2X broker (121).

[0260] At this time, the internal client (111, 131) and the external client (113, 133) are connected to the corresponding brokers (121, 220, 251) symmetrically through the broker information (IP, Port), so the message received from the external client (113, 133) and the message issued from the internal client (111, 131) may be recognized as messages for different domains. Therefore, the source of the data / message issued to the SoftV2X MQTT broker (121) may not be clear. In this case, a problem may occur in which it is impossible to confirm whether the message / data is properly received. Because there is no 1:1 relationship between the broker IP and the source, the source cannot be matched solely based on the broker IP. Consequently, the front-end UI (User Interface) and UX (User Experience) cannot determine where (or through which broker) data / message was not received if reception is not confirmed. Therefore, expanding source-related information may be necessary, as described below.

[0261] - The issuing source (RSU, infra, operator, client, etc.) can be identified in the V2X message ASN.1 (Abstract Syntax Notation One) or MQTT header as shown in Table 5.

[0262] ElementTyperemark@applicationProviderID@applicationProviderName@deviceTypeRSU, Infra, traffic signal, etc.@applicationTypeType of data@regulatorFlagPublic, private data@cloudProviderType of MEC and cloud

[0263] - Alternatively, the sources issuing the message can be categorized and defined through the message topic. For example, the message topic can be expanded to provide various source information, such as MQTT / SoftV2X / AWSPublic / Commsignia / RSU / SDSM or MQTT / SoftV2X / VerizonMEC / Interchange / #, unlike before.

[0264] In this way, the above-described proposed invention can be expected to have the following technical effects ① to ③.

[0265] ① Providing messaging protocol compatibility: When connecting the messaging protocols of two parties, each connection operates its own messaging protocol, requiring a mediator to facilitate the connection. The proposed server-to-server interface can be implemented through a connection structure (e.g., the proposed deployment model) that maintains protocol compatibility through a messaging exchange structure (e.g., MQTT - AMQP).

[0266] - ② Maintaining the operating service solution system: Each application server's message format may be used by additionally allocating or modifying message data for specific purposes or for its own services. If the message format is changed to connect to an external server, a comprehensive change to the message operation system may be required. However, when adding an interface connecting to the outside world, the existing operation system can be maintained and changes can be minimized through the proposed separate bridge module. In other words, the existing operation of client-broker-server can be maintained without modification, and a connection to an external server can be established by building an additional bridge module.

[0267] ③ Maintaining standards compatibility for outgoing messages: Each server's connection messages follow their own operational message format, requiring some modifications to be converted to purely standards-based messages. If the bridge module's function performs message processing for standards compatibility (e.g., processes messages so they conform to the standard's default message format), outgoing messages can be interpreted without issue.

[0268] Figure 24 is a diagram illustrating how a first network transmits an MQTT-based message to a second network.

[0269] The first network may be an MEC, server, or cloud for providing the above-described SoftV2X service. The first network may transmit and receive messages related to the SoftV2X service based on MQTT. As described above, the MQTT may issue / relay messages related to the SoftV2X service to a plurality of clients through a client-broker-client connection structure. For example, the first network may receive / subscribe to an MQTT-based message issued from the above-described V2X entity (UE, RSU, V2X server, etc.) through a first broker, and may issue / relay the MQTT-based message to a plurality of clients that subscribe to a topic included in the MQTT-based message. Here, the topic may be information about a geographical area, etc., and the first network may issue / relay the MQTT-based message to a plurality of clients that subscribe to the topic (i.e., a plurality of clients located in a geographical area corresponding to the topic).

[0270] Specifically, referring to FIG. 24, the first network can receive a first MQTT-based message published from a client using the first broker of the first network (S241). The client can be a device included in a V2X entity, such as a UE or RSU included in a vehicle running in a predetermined geographical area as described above. The first MQTT-based message includes information about a topic, and the first MQTT-based message can be delivered to a plurality of clients that have subscribed to the topic.

[0271] Next, the first network can publish the first MQTT-based message to multiple clients that have subscribed to the topic corresponding to the first MQTT-based message (S243). Specifically, as described above, the first broker of the first network can verify the topic included in the first MQTT-based message and publish / transmit the verified topic to multiple clients that have subscribed to the topic.

[0272] Next, the first network can transmit the first MQTT-based message to the second network using a bridge (S245). Here, the second network may be a server, network, and / or MEC platform of another operator for providing the SoftV2X service as described above. That is, the second network may be a different MEC (Multi-Access Edge Computing) platform from the first network or an application server for a different service entity from the first network. Meanwhile, due to the characteristics of the MQTT protocol, the first network needs to use the bridge described above in order to transmit the MQTT-based message to the second broker of the second network.

[0273] Specifically, the first network may include a bridge for connecting to the second network in relation to MQTT-based messages. The bridge may include a first client and a second client that are symmetrically arranged in consideration of the characteristics of the MQTT protocol as described above. The first client may form a first session based on MQTT with a first broker of the first network, and the second client may form a second session based on MQTT with a second broker of the second network. In addition, the first client and the second client may exchange messages / data through an internal interface. For example, the first client may subscribe to / receive a first MQTT-based message from the first broker, and may provide a second MQTT-based message, which is obtained by removing the MQTT protocol layer from the first MQTT-based message, to the second client. As described above, the second MQTT-based message may be a pure standard format message composed only of a format corresponding to a standard format (a message format defined in 5GAA). The second client can convert the second MQTT-based message into a third MQTT-based message including an MQTT protocol layer associated with the second network, and publish the third MQTT-based message to the second broker.

[0274] Alternatively, the first network may provide the SoftV2X service related to the MQTT-based message through a WVL (wavelength) zone that is not connected to a public IP (Internet Protocol). In this case, the broker or client of the second network (i.e., a device that does not use a SIM card related to the first network) cannot directly access the WVL zone of the first network. Therefore, the second client needs to directly request an initial connection procedure with the second broker to form a second session with the second broker in advance. For example, the second client can connect to the second broker through a public IP using the IP and port of the second broker and form the second session. In other words, when the first network provides the service related to the MQTT-based message through a WVL (wavelength) zone that is not connected to a public IP, the second session can be formed only by the initial connection procedure of the second client. Alternatively, the second client may be connected to the second broker based on Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).

[0275] Figure 25 is a diagram illustrating how a second network receives an MQTT-based message from a first network.

[0276] Referring to FIG. 25, a second network can receive a first MQTT-based message from the first network using a second broker of the second network (S251). The first MQTT-based message includes information about a topic, and the first MQTT-based message can be delivered to multiple clients that have subscribed to the topic.

[0277] Next, the second network can issue the first MQTT-based message to a plurality of clients that subscribe to a topic related to the first MQTT-based message using the second broker (S253). Here, the second network may be a server, network, and / or MEC platform of another operator for providing the SoftV2X service as described above. That is, the second network may be a different MEC (Multi-Access Edge Computing) platform from the first network or an application server for a different service entity from the first network.

[0278] Meanwhile, due to the characteristics of the MQTT protocol, the second broker of the second network cannot be directly connected to the first broker of the first network, and can receive the MQTT-based message through the bridge of the first network. That is, the first MQTT-based message can be received from the bridge of the first network, which includes a first client that has formed a first session with the first broker of the first network, and a second client that has formed a second session with the second broker.

[0279] As described above, the bridge may include a first client and a second client in consideration of the characteristics of the MQTT protocol. The first client may form a first MQTT-based session with a first broker of the first network, and the second client may form a second MQTT-based session with a second broker of the second network. In addition, the first client and the second client may exchange messages / data through an internal interface. For example, the first client may subscribe to / receive a first MQTT-based message from the first broker, and provide a second MQTT-based message, which removes the MQTT protocol layer from the first MQTT-based message, to the second client. As described above, the second MQTT-based message may be a pure standard message composed only of a format corresponding to a standard format (a message format defined in 5GAA). The second client can convert the second MQTT-based message into a third MQTT-based message including an MQTT protocol layer associated with the second network, and publish the third MQTT-based message to the second broker.

[0280] Alternatively, the first network may provide a service related to the MQTT-based message through a WVL (wavelength) zone that is not connected to a public IP (Internet Protocol). In this case, a broker or client of the second network (i.e., a device that does not use a SIM card related to the first network) can directly access the WVL zone of the first network. Accordingly, the second client can directly request an initial connection procedure with the second broker to establish a second session with the second broker in advance. For example, the second client can establish a connection with the second broker through a public IP using the IP and port of the second broker and establish the second session. In other words, when the first network provides a service related to the MQTT-based message through a WVL (wavelength) zone that is not connected to a public IP, the second session may not be established by the second broker, but only by the initial connection procedure of the second client. Alternatively, the second client may be connected to the second broker based on Transmission Control Protocol (TCP) or User Datagram Protocol (UDP).

[0281] In this way, the proposed invention can effectively connect different networks while maximizing message protocol compatibility through the configuration of a bridge. Alternatively, the proposed invention can minimize changes in message formats when connecting different networks through the configuration of a bridge. Furthermore, the proposed invention can effectively ensure connectivity to networks that do not allow TCP / UDP initialization through the IGW via the bridge.

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

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

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

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

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

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

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

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

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

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

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

[0293] Specifically, the first wireless device or first network (100) may include a first broker (not shown), a bridge (not shown), and a memory (104). The memory (104) may include at least one program capable of performing operations related to the embodiments described in FIGS. 16 to 25.

[0294] The processor (102) can control the first broker to receive a first MQTT-based message published from a client and transmit the first MQTT-based message to the second network. Here, the first MQTT-based message can be transmitted through a bridge including a first client that has formed a first session with the first broker and a second client that has formed a second session with a second broker of the second network.

[0295] Alternatively, a processing device may be configured, comprising at least one processor (102) and a memory (104) for controlling a first network to transmit an MQTT-based message to a second network. In this case, the processing device may include at least one processor; and at least one memory coupled to the at least one processor and storing instructions, wherein the instructions, based on being executed by the at least one processor, cause the first network to: receive a first MQTT-based message published from a client using a first broker of the first network, and transmit the first MQTT-based message to the second network. Here, the first MQTT-based message may be transmitted through a bridge including a first client that has formed a first session with the first broker and a second client that has formed a second session with a second broker of the second network.

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

[0297] Specifically, the second wireless device or second network (200) may include a transceiver or RF transceiver (206), a second broker (not shown), 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.

[0298] The processor (202) can control the second broker to receive a first MQTT-based message from the first network and publish the first MQTT-based message to a plurality of clients that subscribe to a topic related to the first MQTT-based message. Here, the first MQTT-based message can be received from a bridge of the first network, which includes a first client that has formed a first session with the first broker of the first network and a second client that has formed a second session with the second broker.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. In a wireless communication system, a method for transmitting an MQTT (Message Queueing Telemetry Transport)-based message from a first network to a second network, A step of receiving a first MQTT-based message published from a client using a first broker of the first network; and comprising a step of transmitting the first MQTT-based message to the second network; A method wherein the first MQTT-based message is transmitted through a bridge including a first client that has formed a first session with the first broker and a second client that has formed a second session with a second broker of the second network.

2. In paragraph 1, A method characterized in that the first client provides the second client with a second MQTT-based message in which the MQTT protocol layer is removed from the first MQTT-based message.

3. In paragraph 2, A method characterized in that the second client converts the second MQTT-based message into a third MQTT-based message including an MQTT protocol layer related to the second network, and publishes the third MQTT-based message to the second broker.

4. In paragraph 1, A method characterized in that the second session is formed only by the initial connection procedure of the second client, based on the first network providing a service related to the MQTT-based message through a WVL (wavelength) zone that is not connected to a public IP (Internet Protocol).

5. In paragraph 4, A method characterized in that the above initial connection procedure is performed using the IP and port of the second broker.

6. In paragraph 1, A method, characterized in that the second client is connected to the second broker based on TCP (Transmission Control Protocol) or UDP (User Datagram Protocol).

7. In paragraph 1, A method, characterized in that the above MQTT-based message is a message for providing a V2X (Vehicle to Everything) service through a network.

8. In paragraph 1, A method, characterized in that the second network is a different MEC (Multi-Access Edge Computing) platform from the first network or an application server for a different service entity from the first network.

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

10. In a first network that transmits an MQTT (Message Queueing Telemetry Transport)-based message to a second network in a wireless communication system, A first broker that relays MQTT-based messages; A bridge for connection with the second network; and including a processor controlling the first broker; The processor controls the first broker to receive a first MQTT-based message published from a client and transmit the first MQTT-based message to the second network, A first network, wherein the first MQTT-based message is transmitted through the bridge, the first network including a first client that has formed a first session with the first broker and a second client that has formed a second session with the second broker of the second network.

11. In a processing device that controls a first network that transmits an MQTT (Message Queueing Telemetry Transport)-based message to a second network in a wireless communication system, at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said first network causes: Receive a first MQTT-based message published from a client using the first broker of the first network, and transmit the first MQTT-based message to the second network, A processing device wherein the first MQTT-based message is transmitted through a bridge of the first network, the bridge including a first client that has formed a first session with the first broker and a second client that has formed a second session with a second broker of the second network.

12. In a wireless communication system, a method for a second network to receive a message based on MQTT (Message Queueing Telemetry Transport), A step of receiving a first MQTT-based message from the first network using a second broker of the second network; and A step of publishing the first MQTT-based message to a plurality of clients that subscribe to a topic related to the first MQTT-based message using the second broker, A method wherein the first MQTT-based message is received from a bridge of the first network, the bridge including a first client that has formed a first session with a first broker of the first network and a second client that has formed a second session with the second broker.

13. A computer-readable recording medium recording a program for performing the method described in Article 12.

14. In a second network that receives MQTT (Message Queueing Telemetry Transport) based messages in a wireless communication system, A first broker that publishes MQTT-based messages to multiple clients; and including a processor controlling the second broker; The processor controls the second broker to receive a first MQTT-based message from the first network and to publish the first MQTT-based message to a plurality of clients that subscribe to a topic related to the first MQTT-based message. A second network, wherein the first MQTT-based message is received from a bridge of the first network, the second network including a first client that has formed a first session with the first broker of the first network and a second client that has formed a second session with the second broker.

15. In a processing device for controlling a second network that receives a message based on MQTT (Message Queueing Telemetry Transport) in a wireless communication system, at least one processor; and At least one memory connected to said at least one processor and storing instructions, said instructions being executed by said at least one processor, wherein said second network causes: Receive a first MQTT-based message from the first network using a second broker of the second network, and publish the first MQTT-based message to a plurality of clients that subscribe to a topic related to the first MQTT-based message using the second broker, A processing device, wherein the first MQTT-based message is received from a bridge of the first network, the bridge including a first client that has formed a first session with the first broker of the first network and a second client that has formed a second session with the second broker.

Images