Method for transmitting message in wireless communication system and apparatus therefor

Abstract

According to various embodiments, disclosed are a method for issuing an MQTT message by a first network in a wireless communication system, and an apparatus therefor. Disclosed are a method and a device therefor, the method comprising the steps of: subscribing to a first MQTT message based on MQTT from a second network by a first network; and issuing a second MQTT message to a plurality of clients connected to the first network on the basis of the first MQTT message.

Description

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

[0001] A method for a first network to issue an MQTT message in a wireless communication system and a device therefor.

[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 achieved by the present invention is to provide a method for transmitting and receiving data / messages 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] A method for issuing an MQTT message by a first network in a wireless communication system according to one aspect comprises the steps of: the first network subscribing to a first MQTT message based on MQTT (Message Queueing Telemetry Transport) from a second network; and issuing a second MQTT message to a plurality of clients connected to the first network based on the first MQTT message, wherein the second MQTT message may be issued with a second routing identifier associated with the first network that is different from a first routing identifier set in the first MQTT message.

[0018] Alternatively, the first network is characterized by including a first broker subscribing to the first MQTT message, an interchange issuing the second MQTT message, and a bridge connecting the interchange and the first broker.

[0019] Alternatively, the bridge is characterized by including an internal client connected to the first broker and an external client connected to the interchange.

[0020] Alternatively, the second routing identifier includes routing identifier information for a server name of the first network, and the first routing identifier includes routing identifier information for a server name of the second network.

[0021] Alternatively, the first routing identifier and the second routing identifier are characterized in that they further include routing identifier information related to a service type of the same MQTT message.

[0022] Alternatively, the first MQTT message is characterized in that it is subscribed to through the first broker of the first network connected to the bridge of the second network.

[0023] Alternatively, the second routing identifier is characterized in that it further includes routing identifier information for a service provider for the interchange.

[0024] Alternatively, the first MQTT message further includes information about a validity time associated with re-issuance, and the second MQTT message is characterized in that whether to issue to the plurality of clients is determined based on the validity time.

[0025] According to another aspect, a first device may be provided that performs the method of issuing an MQTT message as described above.

[0026] According to another aspect, a processing device for controlling a first network may be provided for issuing the MQTT message described above.

[0027] According to another aspect, a method for a second network to publish an MQTT message in a wireless communication system includes the steps of: the second network subscribing a first MQTT message based on MQTT (Message Queueing Telemetry Transport) from a client through a second broker; and publishing the first MQTT message subscribed to the second broker to a first broker of the first network using a bridge, wherein the bridge includes an internal client connected to the second broker and an external client connected to the first broker, and the external client may be configured to have routing identifier information for a network name in which a subscription routing identifier for subscribing to an MQTT message is different from a publication routing identifier for publishing an MQTT message.

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

[0029] According to another aspect, a second network may be provided that performs the method of publishing MQTT messages described above.

[0030] According to another aspect, a processing device may be provided for controlling a second network to issue the MQTT message described above.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0048] Figure 16 is a diagram illustrating a backend architecture in which multiple MQTT brokers are connected.

[0049] Figure 17 is a drawing for explaining a structure for linking V2N services based on Inter-MEC.

[0050] Figure 18 is a drawing for explaining the structure of an interchange.

[0051] Figure 19 is a diagram illustrating how a bridge prevents an infinite loop of data / messages using MQTT topics.

[0052] Figures 20 and 21 are diagrams for explaining a topic setting method to prevent an infinite loop of data / message.

[0053] Figure 22 is a diagram illustrating how a first network re-publishes an MQTT message received from a second network.

[0054] Figure 23 is a diagram illustrating how a second network issues a subscribed MQTT message to a first network.

[0055] Figure 24 illustrates a communication system applied to the present invention.

[0056] Figure 25 illustrates a wireless device applicable to the present invention.

[0057] Figure 26 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0092] - Satellite integrated network

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

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

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

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

[0097] - small cell networks

[0098] - Ultra-dense heterogeneous network

[0099] - High-capacity backhaul

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

[0101] - Softwarization and virtualization

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

[0103] - 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 key 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.

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

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

[0106] - Large-scale MIMO technology

[0107] - Hologram beamforming (HBF)

[0108] - Optical wireless technology

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

[0110] - Quantum communication

[0111] - Cell-free communication

[0112] - Integration of wireless information and power transmission

[0113] - Integration of wireless communication and sensing

[0114] - Integrated access and backhaul network

[0115] - Big data analysis

[0116] - Reconfigurable intelligent surface

[0117] - metaverse

[0118] - Blockchain

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

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

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

[0122] - 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, (a) of FIG. 10 illustrates an example of sensing using a sensing receiver and a sensing transmitter located at the same location (e.g., monostatic sensing), and (b) of FIG. 10 illustrates an example of sensing using a separated sensing receiver and a sensing transmitter (e.g., bistatic sensing).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0162] How to avoid duplicate reception in network connections related to V2N services

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

[0164] 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. Additionally, because V2X message-based communication relies on real-time interaction between vehicles and infrastructure, the speed and reliability of message delivery can play a critical role in ensuring that drivers are warned in a timely manner and vehicles can react to situations in a timely manner.

[0165] 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 message protocols, MQTT (Message Queueing Telemetry Transport) can include the components of a client, a server, and a broker as 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 using the MQTT protocol and subscribe based on routing identifiers such as topics. 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 that have subscribed to the corresponding topic or routing identifier. This V2N communication can provide enhanced services that handle diverse information by interconnecting information from different operators, countries, and regional infrastructures.

[0166] Specifically, a key aspect of the MQTT protocol may be the connection between an MQTT broker and MQTT clients. An MQTT broker is a centralized message broker that stores messages received from MQTT clients and coordinates communication with MQTT clients connected to it (or subscribed to it). An MQTT broker can publish / configure messages to various topics or TOPICS using routing identifiers, and perform routing to clients subscribed to specific topics / topics using routing identifiers. Meanwhile, an MQTT client can publish messages to a connected MQTT broker and subscribe to messages from the MQTT broker. In other words, in the MQTT protocol, message publishing and message subscription can be performed by an MQTT client. An MQTT broker can mediate / relay communication between MQTT clients and play a central role in routing messages. An MQTT client and an MQTT broker can exchange data through the following process. Meanwhile, as described above, a topic / topic is an identifier for routing used to relay messages in MQTT-based communication. For the convenience of explanation, the proposed invention is described below by defining an identifier for routing or a routing identifier as a topic / subject. However, the proposed invention can naturally be applied to various identifiers that a network sets to relay messages to appropriate clients, and is not limited to the term topic / subject. In addition, for the convenience of explanation, the following description is based on the MQTT protocol as a communication protocol between a network and a client. However, the MQTT protocol is only an example, and it is obvious that the proposed invention can be applied to various types of communication protocols.

[0167] 1. The MQTT client initiates an action to connect to the MQTT broker.

[0168] 2. The MQTT client associates its client ID with the IP address of the broker it wants to connect to.

[0169] 3. The MQTT broker authenticates the MQTT client, establishes a connection, and establishes a session.

[0170] 4. The MQTT client notifies the broker of the topic to publish and / or subscribe to.

[0171] 5. The MQTT client publishes a message to a given topic / subject and initiates a subscription to the message (at this time, the MQTT broker appropriately routes the message according to the topic / topic of the delivered message).

[0172] 6. The MQTT client can send and receive necessary messages while maintaining a connection with the MQTT broker.

[0173] At this point, the MQTT client can have or be assigned a client instance ID, which is used to uniquely identify the MQTT client. Additionally, a topic (TOPIC) related to publishing and subscribing to messages can be defined, as follows:

[0174] MQTT topics are separated by slashes (" / ") and can form a hierarchical structure. For example, "seoul / songpa / moonjungdong" can be defined as a hierarchical topic with "seoul" as the subtopic, and "songpa" as the subtopic, and "moonjungdong" as the subtopic. Meanwhile, MQTT topics can support the following two types of wildcards.

[0175] - The "+" wildcard: Can match a single-level topic. For example, "seoul / + / moonjungdong" can match any subtopic between "seoul" and "moonjungdong."

[0176] - The "#" wildcard can match multiple levels of topics. For example, "seoul / #:" matches all subtopics under "seoul."

[0177] By setting up publishing / subscribing messages using topics and wildcards for MQTT in this way, MQTT clients can effectively manage and process messages published to specific topics or messages according to specific topic hierarchy.

[0178] Meanwhile, in the MQTT protocol, "interchange" generally refers to a process or tool for exchanging and converting messages between different messaging protocols or data formats in a messaging system. Interchange can support the collection and exchange of data from multiple servers while ensuring interoperability between different messaging systems or networks. Below, the operations and functions related to interchange are described in detail.

[0179] Figure 16 is a diagram illustrating a backend architecture in which multiple MQTT brokers are connected.

[0180] As described above, V2N message / data exchange can be performed through a subscription / publish relationship based on IP connections between MQTT brokers and MQTT clients. However, in a single-architecture MQTT, message subscription and publishing based on connections between multiple brokers can lead to the following problems.

[0181] Referring to Fig. 16, three MQTT brokers (121, 221, 331) can be connected to each other through multiple bridges (110, 210, 310). At this time, it can be assumed that all clients (11, 12, 13) connected to the three MQTT brokers (121, 221, 331) are publishing / subscribing to a topic called “Ace”. In this case, duplicate data / message publishing / subscription may occur in the data flow clustered through the three MQTT brokers (121, 221, 331).

[0182] For example, if the client (13) on the lower left as above publishes a message with the topic “ACE” set, it can be relayed to the clients (111, 113, 131, 133) within the interchange and / or bridge connected on both sides starting from “①” through ② based on the MQTT brokers (121, 221, 331). The clients (113, 133) within the interchange and / or bridge can transmit / share data / messages to the MQTT brokers (221, 331) connected to different VPCs (Virtual Private Clouds) through ③. At this time, the VPCs connected to the local zone of the connected company B are connected in a broker-client relationship and can exchange data received from “③” through “⑤”. The data exchanged through “⑤” can be received redundantly by the client (13) on the lower left through “⑥”, “⑦”, and “⑧”. Additionally, the message / data issued by client (13) may be received redundantly not only by the client (13) at the lower left, but also by all clients in the clustering relationship (e.g., 11, 12, 111, 113, 211, 213). In this case, the clients may face a problem of having to directly process the duplicated messages.

[0183] To solve this problem, the following solutions may be considered.

[0184] - Solution 1 could be to define the maximum number of hops for data published in the extension header of the transport protocol, perform a hop count reduction operation every time the broker relays, and stop relaying when the hop count becomes 0.

[0185] - Solution 2 can define the maximum geographical distance of the published data in the extension header of the transport protocol and limit the number of brokers to be relayed within the maximum distance.

[0186] - Solution 3 may be a method in which the broker identifies whether the client that issued the message / data is a UE or an MQTT client of the bridge and filters the instance ID of the message / data so that it is not transmitted to (another) broker repeatedly.

[0187] - Solution 4 may be a way to determine the validity of a message / data by defining a message validity time in the MQTT extension header.

[0188] - Solution 5: Solution 5 may utilize the bridge's internal memory or database, which generates interchanges over a period of time, taking into account the cycle time. For example, clients within the bridge can additionally define a unique ID for each client instance within each data / message issued. In this case, clients within the bridge can filter out duplicate data / messages if the data / message is received repeatedly due to cycles.

[0189] - Solution 6: Solution 6 allows clients to include uniquely defined information within messages / data when publishing messages / data. In this case, clients within the bridge can pre-store / cache the unique information within the messages / data and circulate it, thereby filtering out duplicate messages / data.

[0190] Solution 7: Solution 7 stores a unique set of information by combining information from messages / data, and can filter out duplicate messages / data by cycling through this unique set of information. Alternatively, Solution 7 stores a unique set of information by combining information from Msg, cycling through it, and filtering out the information through comparison when it returns.

[0191] - Solution 8: Solution 8 stores information of messages / data through a HASH function, and can filter out duplicate messages / data received by circulation based on the HASH function.

[0192] - Solution 9: Solution 9 is an information sharing entity that relays or hosts multiple brokers, such as an interchange / bridge, and can perform the relaying role through a combination of different topics.

[0193] The above-described Solutions 1 to 9 can solve the problem of receiving duplicate messages from the above-described clients. That is, Solutions 1 to 9 can prevent the reception of duplicate messages / data by clients and / or the transmission of duplicate messages / data by brokers in an environment where multiple brokers and clients are connected. Meanwhile, the above-described Solutions 1 to 9 can be used / applied alone or through a combination of at least one solution (or, definition of an algorithm according to the combination).

[0194] Below, we describe in detail a specific method for preventing duplicate transmission / reception of messages based on the above-described solution.

[0195] Fig. 17 is a drawing for explaining a structure for linking V2N services based on Inter-MEC, Fig. 18 is a drawing for explaining an interchange structure, and Fig. 19 is a drawing for explaining a method for a bridge to prevent an infinite loop of data / message using an MQTT topic.

[0196] Referring to Figure 17, an application server is established in the MEC of each telecommunications company's territory, and brokers or messaging protocols can be connected through the bridge function. The data / message flow here is as follows.

[0197] - ① The issuance of messages / data in the application of a device equipped with a SIM card of A Telecommunication Company (hereinafter, Company A) can be transmitted to the application server (120) (or MQTT broker of the application server) within the MEC of Company A via the base station. The application server (120) (or MQTT broker of the application server) can issue the data / message to the client subscribing to the data / message and / or the connected bridge (Inter MEC Bridge; 110).

[0198] - ② The bridge (110) can receive the data / message through the operation of an internal client (111) that subscribes to the message / data internally.

[0199] - ③ The internal client (111) of the bridge (110) can transmit the data / message to the external client (113) in order to reissue the data to the external server (220). Meanwhile, in the following, the method by which the internal client (111) transmits the message / data to the external client (113) is assumed to be server-client socket communication, but the internal client (111) is not limited thereto and can transmit the message / data to the external client (113) through various methods.

[0200] - ④ The external client (113) can receive data / message from the internal client (111) and relay / issue the data / message to the broker (221) of the connected B company's MEC (200).

[0201] - ⑤ The broker (221) within Company B's MEC (200) can publish the above relayed / published message / data to a client or server that subscribes to it.

[0202] - ⑥ The application of the device equipped with Company B’s SIM card can ultimately receive data / messages issued by Company A’s client.

[0203] Referring to Figure 18, since direct connection between brokers is not possible as described above, brokers can be connected via a bridge that includes internal clients and external clients. That is, the bridge includes clients that can subscribe to messages / data, and can relay messages / data received to an external broker through the transmission of internal data / messages between clients.

[0204] Solution 1 and Solution 2 can extend the following information to prevent infinite loops by using extension headers in the MQTT layer as defined in Table 5.

[0205] Element Type (Type)remarkmsgTypeUnsigned Int or string@maxHopCountUnsigned Int@maxDistanceDouble or float@deliveryPoint@latitudeDouble or float@longitudeDouble or float@radiusDouble or float@polygon@ADouble or float@BDouble or float@CDouble or float@msgPublishTimestring@msgExpirationTimestring

[0206] For example, if @maxHopCount for a message / data issued by MEC of Company A as shown in FIG. 16 is set to 1, the value of @maxHopCount for a message / data delivered to a broker (221, 331) of Company B may be 0. In this case, Company B's broker (221, 331) and / or Company B's interchange / bridge (210, 330) may no longer relay the message / data. Alternatively, @maxDistance may be used to set a restriction so as not to leave a specific area. For example, if @maxDistance is set to 10km, the remaining distance excluding the physical distance between brokers for a message / data delivered to Company B's broker (221, 331) may be set. In this case, since the remaining distance may be set to be smaller than the physical distance, Company B's broker (221, 331) and / or Company B's interchange / bridge (210) may no longer relay the message / data. The two pieces of information described above may be used independently or in combination.

[0207] Meanwhile, the physical distance may be defined as a radius based on the @Deliverpoint, or may be a distance based on @Polygon. For example, the examples of Solution 1 and / or Solution 2 described above may be implemented in JSON format as shown in Table 6 below.

[0208] {"centerCoordinate": {"latitude": 37.4224764,"longitude": -122.0842499},"radius": 500,"polygon": [[37.4224764, -122.0842499],[37.4222112, -122.0852131],[37.4212782, -122.0842301]]}

[0209] Solution 4 can define the validity time or issuance time of the issued message / data. For example, the validity time or issuance time may be defined as in Table 7 below. In this case, the entity receiving the message / data (e.g., a bridge, broker, or client that can check the validity time / issuance time) may filter the message / data based on the validity time / issuance time. For example, the entities receiving the message / data can check whether the time between the issuance time of the message / data and the current time is within a preset specific time length, and if the time length exceeds the preset time length, the message / data can be filtered.

[0210] {"publishTime": "2023-09-26T14:00:00Z","expirationTime": "2023-09-26T15:00:00Z"}

[0211] All of the above-described solutions can be methods that adaptively respond according to the characteristics of the message by checking the identifier / identification information of the message / data.

[0212] For example, referring to FIG. 19, if the above-described solutions are not applied, it can be confirmed that the message / data published by UE-A is received in an infinite loop among UE-A, UE-B, and UE-C (UEs subscribing / publishing to the same topic) in the direction of the arrows shown. In order to resolve this problem, if solution 3 among the above-described solutions is based on, the broker can identify whether the client connected to it is a UE or an MQTT client of the bridge. For example, the client (UE-A, UE-B, or UE-C) can perform an authentication process (e.g., log in) to connect to the broker (MB-A, MB-B, or MB-C), and the broker (MB-A, MB-B, or MB-C) can identify whether the client is a UE through this authentication process. In this case, the broker can identify whether the client publishing / subscribing to the message / data is a UE or an MQTT client of the bridge to prevent the instance ID of the message / data from being published duplicately. For example, data / message of Hello issued by UE-A may be issued back to MB-A via MB-A, Bridge-A, MB-B, Bridge-B, MB-C, and Bridge-C. In this case, MB-A may filter the message / data from being issued to Bridge-A and / or UE-A by identifying that the message / data was issued by a client of Bridge-C.

[0213] Alternatively, for the above-described solutions 5 to 8, it may be a method of separately defining identification information within a message relayed through a bridge in an exchange environment of mobile data linked to a topic of a specific region. Here, through the identification information, it is possible to filter out messages / data that are received / issued in duplicate in the cyclical escalation of clustered data / messages. Specifically, solutions 5 to 8 can filter out messages / data that are received / issued in duplicate through the expansion of the following information within the V2X message ANS.1 as defined in Table 8.

[0214] Element type (Type) remark@bridgeClientInstanceIDInt / Char 4 bytes or more 2 24 Dog allocated @publishedMsgIDInt / Char4 bytes or more 2 24 Dog assignment

[0215] The above extension can be used to define a new field in ANS.1 or to replace an unused field in an existing field. In addition, some bits can be inserted as the above information in an existing bit string and used as the identification information / identifier. The method of preventing duplicate reception through the extension of ANS.1 of a message in this way makes it difficult to utilize MQTT information within a bridge that transmits pure messages / data without encapsulating data / messages according to the MQTT protocol. Therefore, it can be used as an identifier by defining data within the message. The identifier can be used by extending ASN.1 to be compatible with existing data transmission. The identifier / identification information can use an existing data field or be used as a prefix or suffix code of the data. In addition, the identifier / identification information according to the above-described extension method can be set as a criterion for determining the validity of data issuance, such as a timestamp, within the ASN.1 of V2X message data. Such identifier / identification information can be applied to all of the above-described solutions.

[0216] Solution 6 can define @publishedMsgID as the identification / extension information to be described when data / message is generated on the client side. In this case, if the identification / extension information is relayed through the bridge, the identification / extension information can be cached in the bridge's internal memory or stored in an internal database. In this case, the bridge may not re-distribute the data / message based on the identification / extension information even if it is re-delivered (via an external broker).

[0217] Solution 7 caches combinations of unique information of the message / data in the internal memory of the bridge or stores them in the internal DB when the message / data is relayed through the bridge, and based on the combinations of unique information, the data / message may not be re-issued for the message / data that has been re-delivered (through an external broker).

[0218] Solution 8 performs a HASH process on the message / data and stores the processed information (i.e., hashed hash information) in the internal DB of the bridge so that when the same data / message is re-delivered, the data / message can avoid re-issuing the re-delivered message / data (via an external broker) based on the hash information.

[0219] For Solution 9, the Interchange hosts regional and national service entities and can share V2N service-related information with other entities by publishing (or redirecting) data / messages to entities that require such information. Furthermore, even when data is logically shared, the Interchange can also bridge (via a bridge) the data between different entities or brokers of different entities. Therefore, the Interchange needs to publish data / messages appropriately for each data destination. However, the Interchange can prevent infinite data / messages from looping by utilizing MQTT topics, as detailed below.

[0220] Figures 20 and 21 are diagrams for explaining a topic setting method to prevent an infinite loop of data / message.

[0221] Specifically, referring to FIG. 20, a broker (121) of an application server (120; hereinafter, app server) connected to an interchange (330) via a bridge (130), or an interchange (330), can subscribe to / publish messages / data using a topic defined as follows.

[0222] - Company A's LGE app server: Subscription topic = V2N / LG1, Publication topic = V2N / +

[0223] - Company B's LGE app server: Subscription topic = V2N / LG2, Publication topic = V2N / +

[0224] - Company B's Interchange / Broker: Subscription Topic = V2N / Inter, Publication Topic = V2N / LG1 and / or V2N / LG2

[0225] When using the topic defined as described above, data / message issued from LGE app server (120) of A MEC can be received by clients connected to companies A and B via company B's LGE app server (220) and company B's interchange (330) and / or bridge (210). However, when the interchange (330) issues a message / data received from an MQTT blocker (220) via the bridge (210), the interchange (330) can issue the message / data via a topic different from the topic set in the subscribed MQTT message. For example, the interchange (330) can change the received message / data to the topic of V2N / LG 2 after setting the topic of V2N / + and then relay / issue the message / data. In other words, the proposed method can transmit messages that receive messages / data to both Company A and Company B by using topics defined with wildcards in the remaining app servers excluding interchanges. However, in the case of interchanges or bridges, only topics of specific app servers, not wildcards, are defined, so a limited data flow can be configured for specific app servers. In other words, the proposed method can guarantee the reception of messages / data by using topics defined with wildcards in the remaining app servers excluding interchanges, while forming an accurate data flow by setting limited publishing topics in interchanges. Meanwhile, in a structure with multiple interchanges / bridges, an infinite loop of data / messages between app servers / MECs can be prevented by using the number of publishing topics and the hierarchical expansion of " / ".

[0226] Below, we detail how to prevent infinite loops using topics, as in Solution 9.

[0227] MQTT topics are a core element of message routing and can be configured to enable the transmission and reception of messages between publishers and subscribers. Topics also enable data filtering and selective message / data transmission. Published packets are transmitted with a specific topic included in the MQTT variable header. The broker can then receive these published packets and forward them to clients subscribed to the specific topic.

[0228] A system for V2X services must be a system that can receive messages containing object information by all V2X users within a specific area (e.g., a specific area related to data publication and subscription scope) and recognize the objects included in the received messages. In a V2N environment, servers (brokers) of individual services must deliver as many messages / data related to objects as possible to road users, and an information sharing instance (Interchange) must seamlessly connect the data flow between heterogeneous servers. However, if the same topic is designed to interconnect entities or if a topic is designed by assigning a proprietary topic of an individual operator, a data looping issue may occur. Therefore, in a V2N2X environment, the topic of an interoperable V2N2X entity needs to be defined through the following general formula.

[0229] - TOPIC = Level 0 / Level 1 / Level 2 / Level 3 / optional

[0230] - V2N2X TOPIC = {Geolocation} / {serviceName} / {networkName} / {serviceProvider} / {msgType}

[0231] Example 1 for preventing data looping issues through the above-described rules is as follows. Meanwhile, Example 1 assumes that {Geolocation} is the same area, defines topics from Level 1, and defines topics for the flow of data / messages between entities illustrated in FIG. 16 or FIG. 20 described above.

[0232] (1) Company A's SoftV2X client (13, 111, 113, 131, 133)

[0233] - Issue TOPIC = V2N / A / LGE

[0234] - Subscription TOPIC = V2N / #, V2N / + / LGE, or V2N / A / LGE

[0235] - Clients (including internal clients) connected to the SoftV2X broker (121) installed on Company A's MEC resources can publish to V2N / A / LGE and subscribe to / receive all data below level 1 based on topics containing wildcards.

[0236] (2) Company B's SoftV2X client (12, 211, 213)

[0237] - Issue TOPIC = V2N / B / LGE

[0238] - Subscription TOPIC = V2N / # or V2N / + / LGE or V2N / B / LGE

[0239] - Clients (including internal clients and external clients) connected to the SoftV2X broker installed on Company B's resources can publish to V2N / B / LGE and subscribe / receive all data below level 1 based on topics containing wildcards.

[0240] (3) Interchange (330)

[0241] 1) Publication topics of external clients (113, 133, 213) within bridge (110, 130, 210)

[0242] - Company A's external client (131, 113) = V2N / A / INTER

[0243] - External client of Company B (213) = V2N / B / INTER

[0244] - Subscription topics for external clients (113, 133, 213) within the bridge (110, 130, 210)

[0245] - Company A's external client (131, 113) = V2N / A / INTER

[0246] - External client of Company B (213) = V2N / B / INTER

[0247] For example, in the case of "⑤ TMUS cloud zone Interchange direction" in Fig. 16, the publication topic may be V2N / B / INTER, and in the case of "⑥" direction, the subscription topic of the external client of Company A's cloud zone may be V2N / A / INTER. In this case, since the subscription topic of Company A's external client and the publication topic in the "⑤" direction are different, Company B's external client does not receive the message / data for which the publication topic in the "⑤" direction is set. Alternatively, the publication topic in the "③" direction (e.g., VZ cloud zone interchange direction) may be V2N / A / INTER, and the subscription topic of the external client of Company B's cloud zone in the "⑤" direction may be V2N / B / INTER. In this case, since the publication topic in the "③" direction and the subscription topic in the "⑤" direction are different or do not correspond, the external client of Company B's cloud zone does not subscribe to the message / data set to the publication topic in the "③" direction. In this way, by staggering the subscription topic and publication topic of the external client, data / messages can be prevented from being published to the next bridge.

[0248] Alternatively, referring to FIG. 21, Embodiment 2 may be proposed as a method for preventing data looping. In Embodiment 2, all clients can define a topic in common, and external clients within the bridge can convert it into a proprietary topic of each operator (e.g., Company A, Company B, LGE of FIG. 21).

[0249] (1) LGE client at Company A

[0250] - Issue TOPIC = V2N / A / LGE

[0251] - Subscription TOPIC = V2N / # or V2N / + / LGE or V2N / A / LGE

[0252] - Clients (including internal clients) connected to the LGE broker installed on Company A's MEC resources can publish to V2N / A / LGE and subscribe / receive all data below level 1 based on topics containing wildcards.

[0253] (2) CMS (or Commsignia) client from Company A

[0254] - Issue TOPIC = V2N / A / CMS

[0255] - Subscription TOPIC = V2N / # or V2N / + / CMS or V2N / A / CMS

[0256] - Clients (including internal clients) connected to the CMS broker installed on Company A's MEC resources can publish to V2N / A / CMS and subscribe / receive all data below level 1 based on topics containing wildcards.

[0257] (3) Clients at Company B

[0258] - Issue TOPIC = V2N / B / B

[0259] - Subscription TOPIC = V2N / # or V2N / + / B or V2N / B / B

[0260] - Clients (including internal clients) connected to Company B's broker installed on Company B's MEC resources can subscribe to / receive all data below level 1 based on topics that publish to V2N / B / B and include wildcards.

[0261] (4) LGE client at Company B

[0262] - Issue TOPIC = V2N / B / LGE

[0263] - Subscription TOPIC = V2N / # or V2N / + / LGE or V2N / B / LGE

[0264] - Clients (including internal clients) connected to the LGE broker installed on Company B's MEC resources can publish to V2N / B / LGE and subscribe / receive all data below level 1 based on topics containing wildcards.

[0265] (5) Interchange

[0266] - Issue TOPIC = V2N / A / INTER

[0267] - Subscription TOPIC = V2N / # or V2N / + / INTER or V2N / A / INTER

[0268] - Clients (including external clients) connected to the LGE broker installed on Company A's MEC resources can publish to V2N / A / INTER and subscribe / receive all data below level 1 based on topics containing wildcards.

[0269] As described above, the above-mentioned topic (TOPIC) can be defined as an identifier for routing required for the network to relay the client's message.

[0270] Figure 22 is a diagram illustrating how a first network re-publishes an MQTT message received from a second network.

[0271] Referring to FIG. 22, a first network can subscribe to a first MQTT message based on MQTT (Message Queueing Telemetry Transport) from a second network (S221). Here, the first MQTT message may be a message issued by a client of the second network and transmitted to a first broker of the first network via a bridge of the second network. Here, as described above, the bridge may include an internal client connected to a second broker of the second network and an external client connected to a first broker of the first network. The first MQTT message may be set with a first routing identifier for a network name associated with the first network. Alternatively, the first MQTT message may be changed / set from the first routing identifier to a second routing identifier by the external client. Meanwhile, as described above, the first routing identifier and the second routing identifier are identifiers related to routing used by the first network and the second network to relay the client's message, and may also be defined as topics / subjects.

[0272] Next, the first network can issue a second MQTT message to a plurality of clients connected to the first network based on the first MQTT message (S223). For example, the first network can forward the first MQTT message to the first broker and / or an interchange connected to the first broker via a bridge, and the first broker and / or the interchange can issue a second MQTT message relaying the first MQTT message to a plurality of clients connected thereto. Alternatively, the first broker can re-issue the first MQTT message to the clients while maintaining the first routing identifier set in the first MQTT message as is, and the interchange can issue the second MQTT message to the clients in which the first routing identifier set in the first MQTT message is changed to a second routing identifier.

[0273] Here, the second MQTT message may be set with a second routing identifier that is different from the first routing identifier set in the first MQTT message. For example, the first MQTT message may be set with a first routing identifier that includes routing identifier information related to the name / name of the second network, and the second MQTT message may be set with a second routing identifier that includes routing identifier information related to the name / name of the first network. The external client of the interchange or the bridge may issue a second MQTT message in which the first routing identifier in the first MQTT message is changed to the second routing identifier. Here, the first routing identifier and the second routing identifier may further include routing identifier information related to the service type of the same MQTT message. That is, the first routing identifier and the second routing identifier may include routing identifier information that is different from each other only in the network name.

[0274] Alternatively, to prevent an infinite loop of data / messages, a first MQTT message and / or a second MQTT message may be issued, wherein at least one of the solutions 1 to 8 described above is further considered. For example, the first MQTT message may further include information regarding a validity time and / or a validity distance associated with re-issuance. In this case, the interchange and / or broker may determine whether to relay the first MQTT message to the plurality of clients based on the validity time and / or the validity distance.

[0275] Alternatively, the bridge of the first network may include an internal client connected to the first broker and an external client connected to the interchange as described above. Here, the external client of the bridge of the first network may have routing identifiers for subscription and routing identifiers for publication set to be different from each other.

[0276] Alternatively, the external client included in the bridge of the second network may also have a subscription routing identifier for subscribing to MQTT messages and a publishing routing identifier for publishing MQTT messages set to be different from each other. For example, the external client included in the bridge of the second network may issue a message / data with a routing identifier including routing identifier information related to the first network to the interchange of the first network, and may subscribe to only messages / data including routing identifier information related to the second network from the interchange. In this case, since the second MQTT message issued by the interchange has a second routing identifier related to the first network set, the external client included in the bridge of the second network may not subscribe to the second MQTT.

[0277] Alternatively, as will be described later, the first MQTT message subscribed from the second network may be pre-configured by an external client of the bridge of the second network to change the first routing identifier to the second routing identifier.

[0278] Figure 23 is a diagram illustrating how a second network issues a subscribed MQTT message to a first network.

[0279] Referring to FIG. 23, the second network can subscribe to a first MQTT message issued by a client through a second broker (231). For example, as described above, the second network can receive an MQTT message issued by at least one client among a plurality of clients through a second broker connected to the plurality of clients, and relay the received MQTT message to the remaining clients. At this time, the received MQTT message can also be relayed to an internal client of the bridge of the second network, as described above.

[0280] Next, the second network can issue the first MQTT message relayed from the second broker to the first broker or interchange of the first network using the bridge (S233). Here, the bridge can include a first bridge including an internal client connected to the second broker and an external client connected to the first broker as described above, and a second bridge connected to an internal client connected to the second broker and an interchange of the first network.

[0281] Meanwhile, the external client may set a subscription routing identifier for subscribing to an MQTT message and a publication routing identifier for issuing an MQTT message to be different from each other. For example, in the case of the first bridge, the routing identifier that the external client issues to the second broker may include routing identifier information related to the first network, and the routing identifier for the external client to subscribe to messages / data from the second broker may include routing identifier information related to the second network. In addition, when the external client of the first bridge issues an MQTT message transmitted from an internal client to the first broker of the first network, the publication routing identifier of the MQTT message may be changed to a routing identifier including routing identifier information related to the second network and issued. Alternatively, in the case of the second bridge, the routing identifier that the external client issues to the interchange of the first network may include routing identifier information related to the first network, and the routing identifier for the external client to subscribe to messages / data from the interchange may include routing identifier information related to the second network. In this case, since the network names of the issued routing identifier and the subscribed routing identifier are different in the external client of the first bridge and / or the external client of the second bridge, the first MQTT message may be prevented from being re-subscribed to the second network.

[0282] In this way, the proposed invention can prevent MQTT messages of a client from being infinitely looped by staggering the network names between the subscription routing identifier and the publication routing identifier in the external client and / or interchange of the bridge.

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

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

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

[0286] Figure 24 illustrates a communication system applied to the present invention.

[0287] Referring to FIG. 24, 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.

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

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

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

[0291] Figure 25 illustrates a wireless device applicable to the present invention.

[0292] Referring to FIG. 25, 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. 24.

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

[0294] A first wireless device or first network (100) may include a processor (102), a memory (104), and a transceiver (106). The memory (104) may include at least one program capable of performing operations related to the embodiments described in FIGS. 16 to 23.

[0295] Specifically, the processor (102) can control the transceiver (106) to subscribe to a first MQTT message based on MQTT (Message Queueing Telemetry Transport) from a second network, and issue a second MQTT message to a plurality of clients connected to the first network based on the first MQTT message. Here, the second MQTT message can be issued with a second topic related to the first network set that is different from the first topic set in the first MQTT message.

[0296] Alternatively, a processing device may be configured, including at least one processor (102) and a memory (104) for controlling a first network for transmitting a message including object information. In this case, at least one processor; and at least one memory connected 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: subscribe to a first MQTT message based on MQTT (Message Queueing Telemetry Transport) from a second network, and issue a second MQTT message to a plurality of clients connected to the first network based on the first MQTT message. The second MQTT message may be issued with a second topic related to the first network set to be different from a first topic set in the first MQTT message.

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

[0298] A second wireless device or second network (200) may include a transceiver (206), a processor (202), and a memory (204). The memory (204) may include at least one program capable of performing operations related to the embodiments described in FIGS. 16 to 23.

[0299] Specifically, the processor (202) controls the transceiver (206) to subscribe to a first MQTT message based on MQTT (Message Queueing Telemetry Transport) from a client through a second broker of a second network, and to publish the first MQTT message subscribed to the second broker to the first broker of the first network using a bridge. Here, the bridge includes an internal client connected to the second broker and an external client connected to the first broker, and the external client may have topic information for different network names set between a subscription topic for subscribing to an MQTT message and a publication topic for publishing an MQTT message.

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

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

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

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

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

[0305] Figure 26 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 24).

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

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

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

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

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

[0311] Referring to FIG. 27, 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. 26, respectively.

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

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

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

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

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

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

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

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

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

Claims

1. A step in which a first network subscribes to a first MQTT message based on MQTT (Message Queueing Telemetry Transport) from a second network; and A step of issuing a second MQTT message to a plurality of clients connected to the first network based on the first MQTT message, A method in which the second MQTT message is issued with a second routing identifier associated with the first network that is different from the first routing identifier set in the first MQTT message.

2. In paragraph 1, A method, characterized in that the first network includes a first broker subscribing to the first MQTT message, an interchange issuing the second MQTT message, and a bridge connecting the interchange and the first broker.

3. In paragraph 2, A method, characterized in that the bridge includes an internal client connected to the first broker and an external client connected to the interchange.

4. In paragraph 1, A method, characterized in that the second routing identifier includes routing identifier information for a network name of the first network, and the first routing identifier includes routing identifier information for a network name of the second network.

5. In paragraph 1, A method, characterized in that the first routing identifier and the second routing identifier further include routing identifier information related to a service type of the same MQTT message.

6. In paragraph 1, A method, characterized in that the first MQTT message is subscribed to through a first broker of the first network connected to a bridge of the second network.

7. In paragraph 2, A method, characterized in that the second routing identifier further includes routing identifier information for a service provider for the interchange.

8. In paragraph 1, The first MQTT message further includes information about the validity time associated with the re-issuance, A method characterized in that whether or not the second MQTT message is issued to the plurality of clients is determined based on the validity time.

9. A computer-readable recording medium recording a program for performing the method described in paragraph 1. 10.RF(Radio Frequency) transmitter and receiver; and A processor connected to the RF transceiver, The processor controls the RF transceiver to subscribe to a first MQTT message based on MQTT (Message Queueing Telemetry Transport) from a second network, and issues a second MQTT message to a plurality of clients connected to the first network based on the first MQTT message. The second MQTT message is issued with a second routing identifier associated with the first network that is different from the first routing identifier set in the first MQTT message.

11. In a processing device controlling the first network, 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: Subscribe to a first MQTT message based on MQTT (Message Queueing Telemetry Transport) from a second network, and publish a second MQTT message to a plurality of clients connected to the first network based on the first MQTT message, A processing device in which the second MQTT message is issued with a second routing identifier associated with the first network that is different from the first routing identifier set in the first MQTT message.

12. A step in which a second network subscribes to a first MQTT message based on MQTT (Message Queueing Telemetry Transport) from a client through a second broker; and A step of publishing a first MQTT message subscribed to the second broker to the first broker of the first network using a bridge, The bridge includes an internal client connected to the second broker and an external client connected to the first broker, The above external client is a method in which routing identifier information for different network names is set between a subscription routing identifier for subscribing to MQTT messages and a publication routing identifier for publishing MQTT messages.

13. A computer-readable recording medium recording a program for performing the method described in Article 12. 14.RF(Radio Frequency) transmitter and receiver; and A processor connected to the RF transceiver, The processor controls the RF transceiver to subscribe to a first MQTT message based on MQTT (Message Queueing Telemetry Transport) from a client through a second broker of a second network, and to publish the first MQTT message subscribed to the second broker to the first broker of the first network using a bridge. The bridge includes an internal client connected to the second broker and an external client connected to the first broker, The above external client is a second network in which routing identifier information for different network names is set between a subscription routing identifier for subscribing to MQTT messages and a publication routing identifier for publishing MQTT messages.

15. In a processing device controlling a second network, 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: Subscribe to a first MQTT message based on MQTT (Message Queueing Telemetry Transport) from a client through a second broker of a second network, and publish the first MQTT message subscribed to the second broker to the first broker of the first network using a bridge. The bridge includes an internal client connected to the second broker and an external client connected to the first broker, The above external client is a processing device in which routing identifier information for different network names is set between a subscription routing identifier for subscribing to MQTT messages and a publication routing identifier for publishing MQTT messages.

Images