Method by which device performs communication and device therefor in wireless communication system

Abstract

A device according to various embodiments may receive information about a first message generation rule of a second device. A first device may: receive a first message from the second device; on the basis of supporting a second message generation rule different from the first message generation rule, convert the first message into a second message according to the second message generation rule; and transmit the second message to client devices.

Description

A method for a device to perform communication in a wireless communication system and a device for the same

[0001] This relates to a method for a device to transmit and receive messages in a wireless communication system and a device for doing so.

[0002] 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 CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), SC-FDMA (single carrier frequency division multiple access), and MC-FDMA (multi carrier frequency division multiple access) systems.

[0003] Sidelink (SL) refers to a communication method in which User Equipment (UE) establishes a direct link to directly exchange voice or data between terminals without passing through a Base Station (BS). SL is being considered as a solution to address the burden on base stations caused by rapidly increasing data traffic.

[0004] V2X (vehicle-to-everything) refers to a communication technology that exchanges information with other vehicles, pedestrians, and infrastructure-equipped objects through wired or wireless communication. V2X can be classified 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 PC5 interfaces and / or Uu interfaces.

[0005] Meanwhile, as more communication devices require larger communication capacities, the need for improved mobile broadband communication compared to existing Radio Access Technology (RAT) is emerging. Accordingly, communication systems considering services or terminals sensitive to reliability and latency are being discussed; next-generation radio access technology that incorporates improved mobile broadband communication, Massive Machine Type Communication (MTC), and Ultra-Reliable and Low Latency Communication (URLC) can be referred to as new radio access technology (new RAT) or new radio (NR). Vehicle-to-everything (V2X) communication can also be supported in NR.

[0006] Figure 1 is a diagram illustrating a comparison between V2X communication based on RAT prior to NR and V2X communication based on NR.

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

[0008] For example, the CAM may include basic vehicle information such as dynamic state information of the vehicle, such as direction and speed, static data of the vehicle, such as dimensions, external lighting conditions, and route history. For example, a terminal may broadcast the CAM, and the latency of the CAM may be less than 100ms. For example, in the event of an unexpected situation such as a vehicle breakdown or accident, the 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, regarding V2X communication, various V2X scenarios have been presented in NR. For example, various V2X scenarios may include vehicle platooning, advanced driving, extended sensors, remote driving, etc.

[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 belonging to said group can receive periodic data from the lead vehicle. For example, vehicles belonging to said group can use said periodic data to reduce or increase the distance between vehicles.

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

[0012] For example, based on extended sensors, raw data or 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 an environment that is enhanced compared to the environment it can detect using its own sensors.

[0013] For example, based on remote driving, a remote driver or V2X application can operate or control a remote vehicle for a person unable to drive or for a remote vehicle located in a dangerous environment. For example, in cases where the route is predictable, such as in public transportation, cloud computing-based driving can be used for the operation or control of the remote vehicle. Additionally, access to a cloud-based back-end service platform, for example, can be considered for remote driving.

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

[0015] The technical problem that the present invention aims to solve is to provide a method for efficiently transmitting and receiving messages in a wireless communication system and an apparatus for doing so.

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

[0017] A method according to one aspect may include: a first device receiving information about a first message generation rule of a second device; a first device receiving a first message from the second device; a first device converting the first message into a second message according to the second message generation rule based on supporting a second message generation rule different from the first message generation rule; and transmitting the second message to client devices.

[0018] Alternatively, the information regarding the first message generation rule may include instruction information for the generation of a non-periodic message, trigger conditions for message transmission, and information regarding the maximum allowable time interval for message generation.

[0019] Alternatively, the information regarding the first message generation rule may include instruction information for the generation of aperiodic messages based on terminal location prediction, information on a list of maximum allowable errors between the terminal location and the terminal predicted location, and information on the maximum allowable time interval for message generation.

[0020] Alternatively, the information regarding the first message generation rule may include information regarding instructions for the generation of periodic messages, the minimum allowable time interval for message transmission, and the maximum allowable time interval for message transmission.

[0021] Alternatively, information regarding the first message generation rule and the first message may be received through an information sharing entity.

[0022] Alternatively, information regarding the generation rule of the first message can be obtained from the header of the message queuing protocol included in the first message.

[0023] Alternatively, the information regarding the first message generation rule may include information regarding event trigger conditions related to the first message generation rule, and the first message may include information indicating a specific trigger condition related to the first message among the event trigger conditions.

[0024] Alternatively, the first device and the second device may be networks that provide V2X (Vehicle to Everything) services based on different message generation rules.

[0025] According to another aspect, at least one non-transient computer-readable medium comprises instructions for performing operations when executed by at least one processor, said operations may include receiving information about a first message generation rule of a second device; receiving a first message from the second device; converting the first message into a second message corresponding to the second message generation rule based on supporting a second message generation rule different from the first message generation rule; and transmitting the second message to client devices.

[0026] A first device according to another aspect comprises: a Radio Frequency (RF) transceiver; a processor connected to the RF transceiver; and a memory including at least one program that performs operations when executed by the processor, wherein the operations may include receiving information about a first message generation rule of a second device; receiving a first message from the second device; converting the first message into a second message corresponding to the second message generation rule based on supporting a second message generation rule different from the first message generation rule; and transmitting the second message to client devices.

[0027] A processing device controlling a first device according to another aspect comprises at least one processor; and at least one memory connected to the at least one processor and storing instructions that perform operations when executed by the at least one processor, wherein the operations may include the first device receiving information about a first message generation rule of a second device; the first device receiving a first message from the second device; the first device converting the first message into a second message according to the second message generation rule based on supporting a second message generation rule different from the first message generation rule; and the first device transmitting the second message to client devices.

[0028] A method according to another aspect comprises the steps of: a second device receiving a first message generated from a client device based on a first message generation rule; and the second device transmitting the first message to a first device, wherein, based on the first device supporting a second message generation rule different from the first message generation rule, the second device may provide information regarding the first message generation rule to the first device in advance so that the first message is converted into a second message corresponding to the second message generation rule at the first device.

[0029] According to another aspect, at least one non-transient computer-readable medium comprises instructions for performing operations when executed by at least one processor, said operations include receiving a first message generated from a client device based on a first message generation rule; and transmitting said first message to a first device, and based on the first device supporting a second message generation rule different from the first message generation rule, information about said first message generation rule may be provided to said first device in advance so that said first message is converted into a second message corresponding to said second message generation rule at said first device.

[0030] According to another aspect, the second device comprises: a Radio Frequency (RF) transceiver; a processor connected to the RF transceiver; and a memory comprising at least one program that performs operations when executed by the processor, wherein the operations include receiving a first message generated from a client device based on a first message generation rule; and transmitting the first message to the first device, and wherein, based on the first device supporting a second message generation rule different from the first message generation rule, information regarding the first message generation rule may be provided to the first device in advance so that the first message is converted into a second message corresponding to the second message generation rule at the first device.

[0031] According to another aspect, a processing device controlling a second device comprises at least one processor; and at least one memory connected to the at least one processor and storing instructions that perform operations when executed by the at least one processor, wherein the operations include the second device receiving a first message generated from a client device based on a first message generation rule; and the second device transmitting the first message to a first device, and based on the first device supporting a second message generation rule different from the first message generation rule, information regarding the first message generation rule may be provided to the first device in advance so that the first message is converted into a second message corresponding to the second message generation rule at the first device.

[0032] According to various embodiments, a device in a wireless communication system can efficiently perform the transmission and reception of messages. According to one example, by exchanging information regarding message generation rules between heterogeneous service providers in advance, mutual compatibility of message exchange between service providers with different message generation rules can be effectively ensured.

[0033] The effects obtainable from various embodiments are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art from the description below.

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

[0035] Figure 1 is a diagram illustrating a comparison between V2X communication based on RAT prior to NR and V2X communication based on NR.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0050] Figure 16 is a diagram illustrating a method for predicting collision / accident risk based on the location of a terminal.

[0051] FIGS. 17 to 19 are diagrams illustrating a method of exchanging messages between service provider 1 and service provider 2.

[0052] FIG. 20 is a diagram illustrating a method for a first device to convert a first message of a second device into a second message.

[0053] FIG. 21 is a diagram illustrating a method for a second device to transmit a first message to a first device.

[0054] FIG. 22 illustrates a communication system to which the present invention is applied.

[0055] FIG. 23 illustrates a wireless device that can be applied to the present invention.

[0056] FIG. 24 shows another example of a wireless device to which the present invention is applied.

[0057] FIG. 25 illustrates a vehicle or autonomous vehicle to which the present invention is applied.

[0058] 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 CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), SC-FDMA (single carrier frequency division multiple access), and MC-FDMA (multi carrier frequency division multiple access) systems.

[0059] Sidelink refers to a communication method in which User Equipment (UE) establishes a direct link to directly exchange voice or data between terminals without passing through a Base Station (BS). Sidelink is being considered as a solution to address the burden on base stations caused by rapidly increasing data traffic.

[0060] V2X (vehicle-to-everything) refers to a communication technology that exchanges information with other vehicles, pedestrians, and infrastructure-equipped objects through wired or wireless communication. V2X can be classified 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 PC5 interfaces and / or Uu interfaces.

[0061] Meanwhile, as more communication devices require larger communication capacities, the need for improved mobile broadband communication compared to existing Radio Access Technology (RAT) is emerging. Accordingly, communication systems considering services or terminals sensitive to reliability and latency are being discussed; next-generation radio access technology that incorporates improved mobile broadband communication, Massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) can be referred to as new radio access technology (new RAT) or new radio (NR). Vehicle-to-everything (V2X) communication can also be supported in NR.

[0062] 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 using wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented using wireless technologies such as GSM (global system for mobile communications), GPRS (general packet radio service), and EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented using 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 and provides 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 part of E-UMTS (evolved UMTS) which 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.

[0063] 5G NR is a successor technology to LTE-A and is a new clean-slate type mobile communication system with characteristics such as high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, ranging from low frequency bands below 1 GHz to mid-frequency bands from 1 GHz to 10 GHz, and high frequency (millimeter wave) bands above 24 GHz.

[0064] For clarity of explanation, the description focuses on LTE-A or 5G NR, but the technical concept of the embodiment(s) is not limited thereto.

[0065] Figure 2 shows the structure of an applicable LTE system. This can be called an E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network), or an LTE (Long Term Evolution) / LTE-A system.

[0066] Referring to FIG. 2, the E-UTRAN includes a base station (20; Base Station, 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 MS (Mobile Station), UT (User Terminal), SS (Subscriber Station), MT (Mobile Terminal), or Wireless Device. 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 eNB (evolved-NodeB), BTS (Base Transceiver System), or Access Point.

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

[0068] The EPC (30) consists of an MME, an S-GW, and a P-GW (Packet Data Network-Gateway). The MME holds information regarding the terminal's connection information or capabilities, and this information is primarily used for managing the terminal's mobility. The S-GW is a gateway with an E-UTRAN as its endpoint, and the P-GW is a gateway with a PDN as its endpoint.

[0069] The layers of the Radio Interface Protocol between a terminal and a network can be classified into L1 (Layer 1), L2 (Layer 2), and L3 (Layer 3) based on the lower three layers of the Open System Interconnection (OSI) model, which is widely known in communication systems. Among these, the Physical Layer, belonging to Layer 1, provides Information Transfer Services using a physical channel, while the Radio Resource Control (RRC) layer, located at Layer 3, performs the role of controlling radio resources between the terminal and the network. To this end, the RRC layer exchanges RRC messages between the terminal and the base station.

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

[0071] Referring to FIG. 3, the NG-RAN may include gNBs and / or eNBs that provide user plane and control plane protocol termination to terminals. FIG. 7 illustrates a case where only gNBs are included. The gNBs and eNBs are connected to each other via Xn interfaces. The gNBs and eNBs are connected to the 5G Core Network (5GC) via NG interfaces. More specifically, they are connected to the access and mobility management function (AMF) via NG-C interfaces and to the user plane function (UPF) via NG-U interfaces.

[0072] Figure 4 shows the structure of a wireless frame of NR.

[0073] Referring to FIG. 4, radio frames can be used for uplink and downlink transmission in NR. The radio frame has a length of 10 ms and can be defined as two 5 ms half-frames (HF). A half-frame may contain five 1 ms subframes (SF). A subframe may be divided into one or more slots, and the number of slots within a subframe may be determined by the subcarrier spacing (SCS). Each slot may contain 12 or 14 OFDM(A) symbols according to the cyclic prefix (CP).

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

[0075] Table 1 below shows the number of symbols per slot ((N) according to 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 ) exemplifies.

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

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

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

[0079] In an NR system, the OFDM(A) numerology (e.g., SCS, CP length, etc.) can be configured differently among multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., subframe, slot, or TTI) (collectively referred to as TU (Time Unit) for convenience) composed of the same number of symbols can be configured differently among the merged cells.

[0080] In NR, multiple numerologies or SCSs may be supported to support various 5G services. For example, if the SCS is 15 kHz, a wide area in traditional cellular bands may be supported, and if the SCS is 30 kHz / 60 kHz, dense-urban, lower latency, and wider carrier bandwidth may be supported. If the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz may be supported to overcome phase noise.

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

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

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

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

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

[0086] Referring to FIG. 5, a slot contains multiple symbols in the time domain. For example, in the case of a normal CP, one slot may contain 14 symbols, but in the case of an extended CP, one slot may contain 12 symbols. Alternatively, in the case of a normal CP, one slot may contain 7 symbols, but in the case of an extended CP, one slot may contain 6 symbols.

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

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

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

[0090] New network characteristics in 6G may be as follows.

[0091] - Satellite Integrated Network

[0092] - Connected Intelligence: Unlike previous generations of wireless communication systems, 6G is innovative and will update wireless evolution from "connected things" to "connected intelligence." AI can be applied at each stage of the communication process (or at each step of the signal processing described below).

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

[0094] - Ubiquitous Super 3D Connectivity: Connectivity to the network and core network functions of drones and very low Earth orbit satellites will create Super 3D connectivity in 6G ubiquitous.

[0095] Some general requirements regarding the new network characteristics of 6G mentioned above may be as follows.

[0096] - Small cell networks

[0097] - Ultra-dense heterogeneous network

[0098] - High-capacity backhaul

[0099] - Radar technology integrated with mobile technology: High-precision localization (or location-based services) through communication is one of the functions of 6G wireless communication systems. Therefore, radar systems will be integrated with 6G networks.

[0100] - Softwarization and virtualization

[0101] The core implementation technologies of the 6G system are described below.

[0102] - Artificial Intelligence: Introducing AI into communications can streamline and enhance real-time data transmission. AI can determine how complex target tasks are performed using numerous analyses. In other words, AI can increase efficiency and reduce processing latency. Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly using AI. AI can also play a significant role in M2M, machine-to-human, and human-to-machine communication. Furthermore, AI can enable rapid communication in Brain-Computer Interfaces (BCI). 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.

[0103] - THz Communication: Data transmission rates can be increased by expanding bandwidth. This can be achieved by using sub-THz communication with wide bandwidth and applying advanced large-scale MIMO technology. THz waves, also known as sub-millimeter radiation, generally refer to a frequency band between 0.1 THz and 10 THz with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz-300 GHz band range (Sub-THz band) is considered the primary portion of the THz band for cellular communication. Adding the Sub-THz band to the mmWave band increases 6G cellular communication capacity. Among the defined THz bands, the 300 GHz-3 THz band is located in the far-infrared (IR) frequency band. Although the 300 GHz-3 THz band is part of the optical band, it lies at the boundary of the optical band and immediately following the RF band. Therefore, this 300 GHz-3 THz band exhibits similarities to RF.

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

[0105] - Large-scale MIMO technology

[0106] - Hologram beamforming (HBF)

[0107] - Optical wireless technology

[0108] - Free Space Optical Transmission Backhaul Network (FSO backhaul network)

[0109] - Quantum communication

[0110] - Cell-free communication

[0111] - Integration of wireless information and power transmission

[0112] - Integration of wireless communication and sensing

[0113] - Integrated access and backhaul network

[0114] - Big data analysis

[0115] - Reconfigurable intelligent metasurface

[0116] - Metaverse

[0117] - blockchain

[0118] - Unmanned Aerial Vehicle (UAV): UAVs or drones will be a critical element in 6G wireless communication. In most cases, high-speed data wireless connectivity can be provided using UAV technology. Base station (BS) entities can be installed on UAVs to provide cellular connectivity. UAVs can possess specific features not found in fixed BS infrastructure, such as easy deployment, robust line-of-sight links, and controlled degrees of freedom for mobility. During emergencies, such as natural disasters, the deployment of ground communication infrastructure is not economically feasible, and sometimes services cannot be provided in volatile environments. UAVs can easily handle these situations. UAVs will become a new paradigm in the field of wireless communication. This technology facilitates the three fundamental requirements of wireless networks: 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 critical technologies for 6G communication.

[0119] - Autonomous Driving (Self-Driving): V2X (Vehicle to Everything), a core element in building autonomous driving infrastructure, refers to technologies that enable vehicles to communicate and share with various elements on the road for autonomous driving, such as wireless communication between vehicles (Vehicle to Vehicle, V2V) and between vehicles and infrastructure (Vehicle to Infrastructure, V2I). Fast transmission speeds and low-latency technologies are essential to maximize autonomous driving performance and ensure high safety. Furthermore, future autonomous driving may go beyond merely delivering warning or guidance messages to the driver to actively intervene in vehicle operation and directly control the vehicle in dangerous situations. Since the amount of information to be transmitted and received may become massive for this purpose, it is expected that 6G will be able to maximize autonomous driving through faster transmission speeds and lower latency compared to 5G.

[0120] - Non-terrestrial networks (NTN): An NTN may represent 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 one embodiment of the present disclosure. FIG. 9 illustrates an example of a typical NTN scenario based on a regenerative payload according to one embodiment of the present disclosure. The embodiment of FIG. 8 or FIG. 9 may be combined with various embodiments of the present disclosure. Referring to FIG. 8, the satellite (or UAS platform) may establish 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 signals transmitted by the satellite can be received. Referring to FIG. 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 inter-satellite links (ISL). Another satellite (or UAS platform) can be connected to a gateway via a feeder link. Based on a replay payload, the satellite can be connected to a data network via another satellite and a gateway. If no ISL exists between the satellite and another satellite, a feeder link between the satellite and the gateway may be required. FIG. 8 and FIG. 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 on-board processing) payload. For example, a satellite (or UAS platform) may generate multiple beams across a designated service area depending on the satellite's (or UAS platform's) field of view. For example, the satellite's (or UAS platform's) field of view may vary depending on the on-board antenna diagram and the minimum elevation angle. For example, a transparent payload may include radio frequency filtering, frequency conversion, and amplification. Thus, 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 carrying all or part of the base station functions on the satellite (or UAS platform).

[0121] - Integrated Sensing and Communication (ISAC): Radio sensing is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, and distance (range) of an object, thereby obtaining information about the characteristics of the environment and / or objects within the environment. Since radio frequency sensing capabilities do not require connecting to objects via devices within a network, they can provide services for object location determination without the need for devices. The ability to obtain range, velocity, and angle information from radio frequency signals can provide a wide range of new functions, such as various object detection, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision localization, tracking, and activity recognition. Radio sensing services can provide information to various industries (e.g., unmanned aerial vehicles, smart homes, V2X, factories, railways, public safety, etc.) that enable applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, radio sensing may 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., the sensing operation, may depend on the transmission, reflection, and scattering processing of wireless sensing signals. Thus, wireless sensing can provide an opportunity to enhance existing communication systems from communication networks to wireless communication and sensing networks. FIG. 10 illustrates an example of a sensing operation according to one embodiment of the present disclosure. The embodiment of FIG. 10 may be combined with various embodiments of the present disclosure. Specifically, FIG. 10 (a) illustrates an example of sensing using a sensing receiver and a sensing transmitter located at the same position (e.g., monostatic sensing), and FIG. 10 (b) illustrates an example of sensing using a separated sensing receiver and a sensing transmitter (e.g., bistatic sensing).

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

[0123] The Sidelink Synchronization Signal (SLSS) and synchronization information are described below.

[0124] SLSS is an SL-specific sequence that 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 use S-PSS to detect a primary signal and obtain synchronization. For example, a terminal may use S-PSS and S-SSSS to obtain detailed synchronization and detect a synchronization signal ID.

[0125] PSBCH (Physical Sidelink Broadcast Channel) may be a (broadcast) channel through which basic (system) information that a terminal must know first is transmitted before transmitting or receiving SL signals. For example, the basic information may include information related to SLSS, Duplex Mode (DM), TDD UL / DL (Time Division Duplex Uplink / Downlink) configuration, information related to resource pools, types of applications related to SLSS, subframe offsets, broadcast information, etc. For example, to evaluate PSBCH performance, in NR V2X, the payload size of PSBCH may be 56 bits, including a 24-bit CRC.

[0126] S-PSS, S-SSS, and PSBCH may be included in a block format that supports periodic transmission (e.g., SL SS (Synchronization Signal) / PSBCH block, hereinafter S-SSB (Sidelink-Synchronization Signal Block)). The S-SSB may have the same numerology (i.e., SCS and CP lengths) as the PSCCH (Physical Sidelink Control Channel) / PSSCH (Physical Sidelink Shared Channel) within the carrier, and the transmission bandwidth may be within a (pre-)set SL BWP (Sidelink BWP). For example, the bandwidth of the S-SSB may be 11 RB (Resource Block). For example, the PSBCH may span 11 RB. Additionally, the frequency position of the S-SSB may be (pre-)set. Therefore, the terminal does not need to perform hypothesis detection at the frequency to discover the S-SSB in the carrier.

[0127] Meanwhile, in an 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 the transmitting terminal to transmit S-SSBs may decrease. Consequently, the coverage of S-SSBs may decrease. Therefore, to ensure S-SSB coverage, the transmitting terminal may transmit one or more S-SSBs to the receiving terminal within a single S-SSB transmission cycle according to the SCS. For example, the number of S-SSBs transmitted by the transmitting terminal to the receiving terminal within a single S-SSB transmission cycle may be pre-configured or configured for the transmitting terminal. For example, the S-SSB transmission cycle may be 160ms. For example, an S-SSB transmission cycle of 160ms may be supported for all SCSs.

[0128] For example, if the SCS is 15 kHz at FR1, the transmitting terminal may transmit one or two S-SSBs to the receiving terminal within one S-SSB transmission cycle. For example, if the SCS is 30 kHz at FR1, the transmitting terminal may transmit one or two S-SSBs to the receiving terminal within one S-SSB transmission cycle. For example, if the SCS is 60 kHz at FR1, the transmitting terminal may transmit one, two, or four S-SSBs to the receiving terminal within one S-SSB transmission cycle.

[0129] For example, if 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 cycle. For example, if 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 cycle.

[0130] Meanwhile, when the SCS is 60 kHz, two types of CP may be supported. Additionally, depending on the CP type, the structure of the S-SSB transmitted by the transmitting terminal to the receiving terminal may differ. For example, the CP type may be Normal CP (NCP) or Extended CP (ECP). Specifically, for example, if the CP type is NCP, the number of symbols mapping PSBCH within the S-SSB transmitted by the transmitting terminal may be 9 or 8. On the other hand, for example, if the CP type is ECP, the number of symbols mapping PSBCH within the S-SSB transmitted by the transmitting terminal may be 7 or 6. For example, 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 Automatic Gain Control (AGC) operation during the first symbol interval of the S-SSB.

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

[0132] Referring to FIG. 12, in V2X or SL communication, the term terminal may primarily refer to a user's terminal. However, if network equipment such as a base station transmits and receives signals according to the 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).

[0133] 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 said 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 terminal 1's signal within said resource pool.

[0134] Here, if terminal 1 is within the connection range of the base station, the base station may 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 may inform terminal 1 of the resource pool, or terminal 1 may use a pre-configured resource pool.

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

[0136] Figure 13 shows a resource unit for V2X or SL communication.

[0137] Referring to FIG. 13, the total frequency resources of the resource pool can be divided into NF units, and the total time resources of the resource pool can be divided into NT units. Thus, a total of NF * NT resource units can be defined within the resource pool. FIG. 13 illustrates an example where the resource pool is repeated in a period of NT subframes.

[0138] As shown in FIG. 13, a single resource unit (e.g., Unit #0) may appear repeatedly over time. Alternatively, to obtain diversity effects in the time or frequency dimension, 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 structure of resource units, a resource pool may refer to a set of resource units that a terminal intending to transmit an SL signal can use for transmission.

[0139] Resource pools can be subdivided into several types. For example, depending on the content of the SL signals transmitted from each resource pool, resource pools can be classified as follows.

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

[0141] (2) A 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 along with SL data on the same resource unit, only the form of the SL data channel excluding SA information can be transmitted from the resource pool for the SL data channel. In other words, REs (Resource Elements) that were used to transmit SA information on individual resource units within the SA resource pool can still be used to transmit SL data in the resource pool of the SL data channel. For example, the transmitting terminal can transmit by mapping the PSSCH to a succession of PRBs.

[0142] (3) The discovery channel may be a resource pool for a transmitting terminal to transmit information such as its ID. Through this, the transmitting terminal can enable adjacent terminals to discover it.

[0143] 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 attributes of the SL signal. For example, even if the same SL data channel or discovery message is used, it may be divided into different resource pools depending on the method of determining the transmission timing of the SL signal (e.g., whether it is transmitted at the time of reception of the synchronization reference signal or whether it is transmitted by applying a certain timing advance at the time of reception), the method of resource allocation (e.g., whether the base station assigns the transmission resource of an individual signal to the individual transmission terminal or whether the individual transmission terminal selects the individual signal transmission resource itself from within the resource pool), the signal format (e.g., the number of symbols occupied by each SL signal in one subframe, or the number of subframes used for the transmission of one SL signal), the signal strength from the base station, the transmission power strength of the SL terminal, etc.

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

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

[0146] A BWP can be configured by point A, an offset from point A (NstartBWP), and a bandwidth (NsizeBWP). For example, point A may be an external reference point of the PRB of a carrier where the subcarrier 0 of all numerologies (e.g., all numerologies supported by the network on that carrier) is aligned. For example, the offset may be the PRB interval between the lowest subcarrier in a given numerology and point A. For example, the bandwidth may be the number of PRBs in a given numerology.

[0147] SLSS (Sidelink Synchronization Signal) is a 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 use S-PSS to detect the initial signal and obtain synchronization. For example, a terminal may use S-PSS and S-SSSS to obtain detailed synchronization and detect the synchronization signal ID.

[0148] The PSBCH (Physical Sidelink Broadcast Channel) may be a (broadcast) channel through which basic (system) information that the terminal must know first is transmitted before transmitting or receiving SL signals. For example, the basic information may include information related to SLSS, Duplex Mode (DM), TDD UL / DL (Time Division Duplex Uplink / Downlink) configuration, information related to resource pools, types of applications related to SLSS, subframe offsets, broadcast information, etc. For example, to evaluate PSBCH performance, in NR V2X, the payload size of the PSBCH may be 56 bits, including a 24-bit CRC (Cyclic Redundancy Check).

[0149] S-PSS, S-SSS, and PSBCH may be included in a block format that supports periodic transmission (e.g., SL SS (Synchronization Signal) / PSBCH block, hereinafter S-SSB (Sidelink-Synchronization Signal Block)). The S-SSB may have the same numerology (i.e., SCS and CP lengths) as the PSCCH (Physical Sidelink Control Channel) / PSSCH (Physical Sidelink Shared Channel) within the carrier, and the transmission bandwidth may be within a (pre-)set SL BWP (Sidelink BWP). For example, the bandwidth of the S-SSB may be 11 RB (Resource Block). For example, the PSBCH may span 11 RB. Additionally, the frequency position of the S-SSB may be (pre-)set. Therefore, the terminal does not need to perform hypothesis detection at the frequency to discover the S-SSB in the carrier.

[0150] FIG. 15 illustrates a procedure in which a terminal performs 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.

[0151] Referring to FIG. 15(a), 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.

[0152] For example, the first terminal may receive information related to a dynamic grant (DG) resource and / or information related to a configured grant (CG) resource from the base station. For example, the CG resource may include a CG type 1 resource or a CG type 2 resource. In this specification, the DG resource may be a resource that the base station sets / assigns to the first terminal via downlink control information (DCI). In this specification, the CG resource may be a (periodic) resource that the base station sets / assigns to the first terminal via DCI and / or RRC messages. For example, in the case of a CG type 1 resource, the base station may transmit an RRC message containing 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 containing information related to the CG resource to the first terminal, and the base station may transmit DCI related to the activation or release of the CG resource to the first terminal.

[0153] In step S1510, the first terminal may transmit a PSCCH (e.g., Sidelink Control Information 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.) associated with the PSCCH to the second terminal. In step S1530, the first terminal may receive a PSFCH associated with 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 the HARQ feedback information to the base station via a PUCCH or PUSCH. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on 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 pre-set rule. For example, the DCI may be a DCI for scheduling SL.

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

[0155] Referring to FIG. 15 (a) or (b), for example, the first terminal may transmit an SCI to the second terminal over the PSCCH. Or, for example, the first terminal may transmit two consecutive SCIs (e.g., 2-stage SCIs) to the second terminal over the PSCCH and / or 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 over the PSCCH may be referred to as the 1st SCI, the 1st SCI, the 1st-stage SCI, or the 1st-stage SCI format, and an SCI transmitted over the PSSCH may be referred to as the 2nd SCI, the 2nd SCI, the 2nd-stage SCI, or the 2nd-stage SCI format.

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

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

[0158] Meanwhile, the aforementioned sidelink may be defined as communication between terminals or direct communication between terminals. In this case, PSCCH may be defined as a physical control channel for communication between terminals, PSSCH as a physical data channel or physical sharing channel for communication between terminals, and PSFCH as a physical feedback transmission channel between terminals.

[0159] Method for exchanging information related to Uu V2X message generation rules between heterogeneous service providers

[0160] The method of transmitting messages under a given scenario (e.g., Intelligent Transportation System (ITS) standard) is as follows.

[0161] Messages defined in ITS standards may be classified into periodic transmission and / or non-periodic transmission (e.g., event-triggered-based transmission) depending on the type of message. In this case, “periodic transmission” basically means that a message is generated / transmitted according to a (pre-defined / set) message transmission period, and means a message transmission method in which message generation / transmission is allowed at a specific point in time within the said defined / set period when the (pre-defined / set) triggering condition for message generation / transmission is satisfied. For example, a message defined for periodic transmission may mean that message generation / transmission must be performed in accordance with the (pre-defined / set) period even if an event corresponding to the (pre-defined / set) triggering condition for message generation / transmission does not occur. This may mean that, regardless of whether an event corresponding to the triggering condition for message creation / transmission occurs, the time interval between the previous message transmission (e.g., the Nth message transmission) and the next message transmission (e.g., the (N+1)th message transmission) cannot be longer than a (pre-defined) / set time interval (e.g., the message creation / transmission cycle).

[0162] Meanwhile, the proposals related to a given scenario (e.g., a contribution by Ericsson published at the 5GAA in 2017; A-170134) include the following:

[0163] - In a given scenario, only the broadcast transmission of CAM messages is considered, and the message (e.g., CAM) can be transmitted periodically (even without a special event).

[0164] - When a terminal transmits a CAM message using a Uu link, the CAM message may not be transmitted periodically. In this case, the terminal (or server / cloud) may predict the location of the terminal, but it may be efficient for the terminal to transmit the message to the server / cloud via a UL signal only when the terminal's location exceeds a specific threshold (pre-set) (or for the server to transmit the message about the terminal to the receiving terminal via a DL signal (e.g., forwarding). In this case, there may be an effect of reducing UL and / or DL ​​traffic.

[0165] - For example, when interpreted from the perspective of changing the spec related to the above-mentioned scenario, the maximum transmission period of the CAM (e.g., 1 second) defined as the message generation triggering condition in the above-mentioned scenario may be removed, and a new trigger condition may be added: "when the location of the terminal predicted by the terminal (or server / cloud) differs from the current actual terminal location by more than a specific threshold value (pre-set)."

[0166] The following describes in detail how to exchange information related to Uu V2X message generation rules, taking into account interoperability between heterogeneous service providers.

[0167] FIG. 16 is a diagram illustrating a method for predicting collision / accident risk based on the location of a terminal, and FIGS. 17 to 19 are diagrams illustrating a method for exchanging messages between service provider 1 and service provider 2.

[0168] As illustrated in FIG. 16 (a), the server / cloud can predict the location of the transmitting terminal (and / or receiving terminal) and / or the collision / accident risk of said terminal. Alternatively, as illustrated in FIG. 16 (b), the terminal can directly predict its own location and / or collision / accident risk.

[0169] As described above, in connection-based Uu V2X, non-periodic message generation rules (e.g., CAM / VAM generation based on terminal location prediction) may be applied to achieve traffic reduction effects. For instance, even if a message is defined for periodic transmission in current ITS standards designed considering only broadcast-based direct communication methods, the Uu V2X system may transmit the message according to non-periodic message generation rules based on terminal location prediction. Based on this, different message generation rules, parameters related to message generation rules, and configuration sets (or message generation rule information) within the (Uu) V2X system may be used or applied among service providers. Through this, each service provider may be granted a degree of freedom in the implementation of the (Uu) V2X system.

[0170] For example, referring to FIG. 17 (a), Uu V2X systems of two different service providers (Service Provider 1 (SP1), Service Provider 2 (SP2)) can be interconnected. In this case, each Uu V2X system can perform message transmission and reception operations (e.g., message transmission and reception operations between a server and a client device) based on different message generation rules, message generation rule related parameters and / or a set of settings (or message generation rule information). However, in this case, it may be difficult to ensure interoperability in the exchange of information / messages between V2X systems of two service providers (SP1 and SP2) where different message generation rules are defined / configured (e.g., SP1 server-to-SP2 server, UE of SP1-to-UE of SP2). For example, a server, cloud, RSU, or terminal of another SP that receives information / messages generated by a specific SP's V2X system may face difficulties in determining the cause of the information / messages' generation and the (maximum) time interval until the reception of the next message. Therefore, it may be necessary to develop a solution to ensure interoperability between different SPs.

[0171] Below, methods for ensuring interoperability between different SPs or between Uu V2X systems of different SPs are described in detail.

[0172] When exchanging information between V2X systems of different service providers (SPs) or service-providing devices / servers, the application (app) server (and / or user) of each service provider may notify the application server of a heterogeneous service provider, an information sharing entity (e.g., interchange), or a user / client connected to the application server of the heterogeneous service provider of the message generation rules used in the V2X system of the said SP (and / or individual users connected to / registered in the said V2X system and / or services supported through the V2X system of the said SP) and the associated configuration set and / or parameter values. For example, the first SP may provide information regarding the message generation rules applied / used in the first SP (or the V2X service provided by the first SP) to the linked second SP, an information sharing entity (e.g., interchange), and / or the client device of the second SP.

[0173] 1. Examples of message generation rules and associated parameter sets

[0174] Specifically, the message generation rule information (e.g., message generation rules, message generation rule-related parameters and / or sets of parameters) exchanged / provided between heterogeneous service providers may include the following information / parameters.

[0175] - Whether periodic message generation rules (according to direct communication-based ITS standards) are used or instructions regarding this

[0176] - If periodic message generation rules (according to direct communication-based ITS standards) are not used, the type of message generation rule, information on message generation triggering conditions, and / or a list of conditions

[0177] - Minimum / maximum allowed time interval between the previous message generation and the next message generation (e.g., T_GenVamMin, T_GenVamMax, T_CheckVamGen)

[0178] - Minimum / maximum change values ​​related to terminal driving characteristics used in message generation rules (e.g., minReferencePointPositionChangeThreshold, minGroundSpeedChangeThreshold, minGroundVelocityOrientationChangeThreshold, minTrajectoryInterceptionProbChangeThreshold, MSLaD, MSLoD, MSVD)

[0179] - (Location) Maximum error level applied to prediction-based message generation rules, minimum / maximum period for terminal location prediction, terminal location and maximum error for location prediction

[0180] - Predicted / planned message generation cycle / frequency / timeframe, or maximum / average / minimum value / range of the predicted / planned message generation cycle / frequency / timeframe

[0181] Meanwhile, even within a V2X system of a single SP, different message generation rules may be used depending on the service, terminal, and regional / context characteristics. Alternatively, even if the message generation rules are identical within a V2X system of a single SP, operations based on different parameters may be configured depending on the service, terminal, and regional / context characteristics.

[0182] For example, SP1 (e.g., SP1 application server, cloud, and / or user) may provide message creation rule information regarding a set of settings that includes the type of message creation rule used and two or more parameter values ​​that can be used for said message creation rule to a user / client connected to an application server / cloud of another SP, an information sharing entity, and / or an application server of a heterogeneous service provider. And, when a single SP (e.g., SP1 application server, cloud, and / or user) transmits a message / information to an application server / cloud of another SP (or an information sharing entity, or a user / client connected to an application server of a heterogeneous service provider), said SP1 (e.g., SP1 application server, cloud, and / or user) may additionally provide information to said application server / cloud of the other SP indicating which parameter among the parameters included in said set of settings was used in the creation of said message / information (and / or which configuration is used in the message creation rule for each service / user).

[0183] For example, referring to FIG. 17 (b), terminals within the V2X system of SP1 can predict their own location (transmitter) according to a terminal location prediction-based message generation rule, and generate / transmit a message only when the difference between their predicted location and the actual location at the predicted time exceeds an allowable location error level. For example, a terminal can trigger the transmission of a message when the difference between the predicted location for a specific time included in the most recently transmitted message and the actual location at said specific time exceeds a threshold error (or an allowable location error level). Here, the allowable location error level may be set differently for each service and each terminal. When messages / information generated from terminals within SP1’s V2X system performing such operations are transmitted / exchanged with another SP’s V2X system (e.g., the application server of a second service provider), the SP1 application server / cloud (and / or user) may inform the SP2 application server / cloud (or, user / client within SP2’s V2X system) of indication information that the message generation rule used is a “terminal location prediction-based message generation rule” and information regarding a “set of settings for lists of tolerance levels that can be used under said message generation rule” (e.g., message rule information). Furthermore, when the SP1 application server / cloud (and / or user) transmits a message to the SP2 application server / cloud (or, user / client within SP2’s V2X system), the SP1 application server / cloud (and / or user) may also indicate which of the parameters included in said set of settings the tolerance level used in generating said message is.

[0184] Below, a method for exchanging message generation rule information between heterogeneous servers / service providers, etc., that use different message generation rules as described above will be explained in detail.

[0185] 2. Examples of Information Exchange Operations by Heterogeneous Service Provider Linkage Implementation Methods

[0186] The exchange of message generation rule information based on the implementation method of linking heterogeneous service providers can be performed through a direct interface between heterogeneous servers, as shown in Example 1 described below; through an information sharing entity, as shown in Example 2; or by a client device directly connecting to a heterogeneous server, as shown in Example 3. Each case will be explained in detail below.

[0187] (1) Example 1: Information exchange between servers via a direct interface

[0188] Referring to Fig. 18 (a), the servers of SP1 and SP2 can exchange message creation rule information (e.g., message creation rules, parameters related to message creation rules and / or sets of parameters) through a direct interface.

[0189] 1) Alt 1

[0190] Message generation rule information regarding the message generation rules used by each V2X system, their associated parameter values, and setting sets can be exchanged between the SP1 server (or SP1 AS) and the SP2 server (or SP2 AS) (via the direct interface mentioned above). In this case, each server can transmit messages / information acquired / received from heterogeneous servers to its client devices / terminals after interpreting / processing them in accordance with the message generation rules used by its own V2X system.

[0191] For example, it can be assumed that the V2X system of SP1 uses periodic message generation rules based on direct communication-based ITS standards, and the V2X system of SP2 uses terminal location prediction-based message generation rules. In this case, SP1 may provide / transmit to SP2 indicators / information to inform it that periodic message generation rules (based on direct communication-based ITS standards) are being used, and / or information regarding the minimum / maximum allowable time intervals (e.g., T_GenVamMin, T_GenVamMax, T_CheckVamGen) between the generation of the previous message and the generation of the next message (e.g., message generation rule information). SP2 may provide / transmit to SP1 indicators / information to indicate that prediction-based message generation rules are used, the maximum tolerance level applied to the prediction-based message generation rules, the minimum / maximum period for terminal location prediction, the terminal location and maximum tolerance for location prediction, and / or information (e.g., message generation rule information) regarding the minimum / maximum allowable time interval between the previous message generation and the next message generation (e.g., T_GenVamMin, T_GenVamMax, T_CheckVamGen).

[0192] - Alt 1-1) SP2, having received the message generation rule information from SP1, can convert / generate the SP1 client-related information / messages received from SP1 according to its own message generation rules and transmit them to terminals / clients within the SP2 V2X system. In this case, the clients of SP2 may not need to take any separate action to receive the message.

[0193] - Alt 1-2) SP2, upon receiving the above information (e.g., message generation rule information), may add information related to the message generation rules of the SP1 V2X system (e.g., message generation rule information necessary for receiving / interpreting the message in the received message) transmitted from the SP1 server (or app server) to the message / information from the SP1 server (or app server) (generated / transmitted according to different message generation rules), and transmit the message / information of SP1 to which the message generation rule information of SP1 has been added to terminal / client devices within the SP2 V2X system. In this case, the SP2 client devices may normally receive / interpret the message / information based on the message generation rule information of SP1. For example, the SP2 server may add SP1's message creation rule information to the header of the message queuing protocol (e.g., MQTT (Message Queuing Telemetry Transport) message header, AMQP (Advanced Message Queuing Protocol) message header, etc.) and / or the (extended) data field of the message received from the SP1 server and transmit it to its client devices.

[0194] 2) Alt 2

[0195] If the message generation rules (and / or the set of related parameter settings) used in the V2X system of SP1 and the V2X system of SP2 are different, the terminal that (initially) generated the message / information may transmit the message / information to which it has directly added the message generation rule information it used for messages / information to be exchanged between heterogeneous servers / service providers / V2X systems. For example, when transmitting messages / information to be exchanged / transmitted between heterogeneous systems (or between the V2X system of SP1 and the V2X system of SP2), a terminal / client device may directly add the message generation rule information it used to the message / information and transmit the message / information to the heterogeneous system / server / service provider to which the message generation rule information has been added. The heterogeneous service provider and / or the client device / terminal of the heterogeneous service provider that receives the message / information may decode / interpret the message / information based on the message generation rule information included in the message.

[0196] (2) Example 2: Information exchange between heterogeneous servers through information sharing entities

[0197] Referring to Fig. 18 (b), information related to the message generation rule can be exchanged through an information sharing entity (e.g., Interchange) connecting the server of SP1 and the server of SP2.

[0198] 1) Alt 1: Message generation rule information used by each V2X system (e.g., message generation rules and related parameter values / sets of settings) may be reported to an information sharing entity. Based on message generation rule information obtained from heterogeneous servers / service providers, the information sharing entity may interpret / process received messages / information in accordance with the message generation rules of each server and then provide them to each service provider. For example, the information sharing entity may receive first message generation rule information (e.g., message generation rules, related parameters and / or sets of parameters) applied to the first service provider's server, etc. from the first service provider, and may receive second message generation rule information applied to the second service provider's server, etc. from the second service provider. Subsequently, when the first message is received from the first service provider, the information sharing entity may provide / transmit / transmit a second message, which is the result of interpreting / processing the first message in accordance with the second message generation rule information, to the second service provider / the client device of the second service provider.

[0199] 2) Alt 2: Information on message creation rules used by each V2X system (e.g., message creation rules, related parameters and / or sets of parameters) may be reported to an information sharing entity. When the information sharing entity transmits a message / information received / acquired from one server (e.g., SP1 app server) to another heterogeneous server (e.g., SP2 app server), it may provide / transmit / transmit the message / information to the other heterogeneous server along with information on message creation rules provided by the said server (e.g., SP1 app server). The other heterogeneous server (e.g., SP2 app server) that receives / transmits the message / information may perform the same operation as “(1) Alt 1 of Example 1” described above.

[0200] 3) Alt 3: The same operation as “(1) Alt 2 of Example 1” described above may be possible. For example, when a terminal / client device, which is the initial message / information generating device, transmits a message to a heterogeneous server / heterogeneous service provider, the terminal / client device may transmit a message / information to the heterogeneous server / heterogeneous service provider through the information sharing entity, by directly adding message generation rule information applied / used to its own server / heterogeneous service provider’s server.

[0201] (3) Example 3: A case where a client device of one service provider directly connects to the app server of another service provider to transmit and receive information based on an agreement between (heterogeneous) service providers.

[0202] 1) Alt 1: The same operation as “(1) Alt 2 of Example 1” may be possible. For example, referring to FIG. 19, when a terminal / client device, which is the initial message / information generating device, transmits a message to a heterogeneous server / heterogeneous service provider, the terminal / client device may directly connect to the app server of the heterogeneous server / heterogeneous service provider and transmit a message / information to the directly connected heterogeneous server / heterogeneous service provider's app server with message generation rule information applied / used to its own server / heterogeneous service provider's server.

[0203] 2) Alt 2: Operations similar to “(1) Alt 1-2 of Example 1” may be possible. When service providers agree, SP1 may provide SP2 with the connection authority (and related information) of SP2 clients, along with information on message generation rules used in SP1’s V2X system. When SP2’s clients connect to SP1, they may perform message / information transmission operations according to the message generation rules of SP1’s V2X system. Alternatively, as in “(1) Alt 1-2 of Example 1” (e.g., generate / transmit messages according to the message generation rules used by the SP2 V2X system), they may generate / transmit by adding the message generation rules and related parameters (and / or a set of settings) used by the client, so that terminals within the SP1 V2X system can interpret the information / messages transmitted by the client. The above additional information (e.g., message creation rule information) may be efficiently added to the header of the message queuing protocol (e.g., MQTT message header, AMQP message header, etc.) and / or (extended) data field.

[0204] For convenience of explanation, the above proposal was described under the premise that ITS messages / V2X messages are transmitted via Uu link; however, the proposal is not limited to this and can be applied in the same or similar manner to cases where messages are transmitted via direct communication using communication technologies such as LTE-V2X, NR-V2X, IEEE 11p, and ITS-G5. Here, (ITS / V2X) messages may be messages defined in current ITS standards (e.g., BSM, CAM, DENM, PSM, VAM, SDSM, CPM), but may also include messages that will be newly defined in future ITS standards or non-standard messages for supporting V2X services (not defined in standards).

[0205] FIG. 20 is a diagram illustrating a method for a first device to convert a first message of a second device into a second message.

[0206] The first device may be a server / network / broker of a first service provider, and the second device may be a server / network / broker of a second service provider. For example, the first device and the second device may be V2N devices / networks that provide V2X services by receiving messages from client devices / terminals through a Uu interface and relaying / transmitting the received messages to client devices / terminals through the Uu interface. For example, the first device may receive a message from a client device / terminal that includes a V2X message (e.g., CAM, DENM, BSM, VAM, etc., ITS message) regarding the status information / recognition information (e.g., movement speed, location, device type, etc.) of the client device / terminal, and may transmit / delivere a message containing the V2X message to surrounding client devices / terminals associated with the client device / terminal based on the received message. Additionally, the first device may transmit the message to the second device, and the second device may transmit a message to its own client devices to convey the message.

[0207] Meanwhile, the first service provider and the second service provider may use / apply different message generation rules. For example, as described above, the first service provider may use a second message generation rule that periodically generates / transmits messages based on a predetermined scenario (ITS standard), and the second service provider may use a first message generation rule that generates / transmits messages using an event-based trigger method. For example, the first message generation rule may include a terminal location prediction-based message generation rule in which the transmission of a new message is triggered when the difference between the location predicted by a client device / terminal included in a recently transmitted message (e.g., a message containing predicted locations for multiple future points in time) and the actual location exceeds a specific threshold.

[0208] Below, we will explain in detail how to exchange messages between devices, servers, and networks of heterogeneous service providers with different message generation rules.

[0209] Referring to FIG. 20, the first device may receive information regarding a first message generation rule of the second device (S201). The first message generation rule may include information indicating whether the V2X system associated with the second device uses a periodic message generation rule or a non-periodic message generation rule. Additionally, the information regarding the first message generation rule may include information regarding a set of parameters as described in "1. Example of a message generation rule and a set of parameters associated therewith."

[0210] For example, the information regarding the first message generation rule may include instruction information for the generation of a non-periodic message, trigger conditions for message transmission, and information regarding the maximum allowable time interval for message generation. Alternatively, the information regarding the first message generation rule may include instruction information for the generation of a non-periodic message based on terminal location prediction, information on a list of maximum allowable errors between the terminal location and the terminal predicted location, and information regarding the maximum allowable time interval for message generation. Alternatively, the information regarding the first message generation rule may include instruction information for the generation of a periodic message, information regarding the minimum allowable time interval for message transmission, and information regarding the maximum allowable time interval for message transmission.

[0211] Meanwhile, the first device may also provide / transmit information regarding the second message generation rule applied / used in its V2X system to the second device. For example, the first device may transmit information regarding the second message generation rule to the second device, including information about at least one of the sets of parameters / parameters as described in "1. Example of a message generation rule and a set of parameters / parameters associated therewith." Here, the first device may exchange information regarding the message generation rule through a direct interface between the first device and the second device as described in "2. (1) Example 1," or exchange information regarding the message generation rule through an information sharing entity (e.g., an interchange, a bridge) as described in "2. (2) Example 2."

[0212] Alternatively, information regarding the first message generation rule may be transmitted through a message from a client device connected to the V2X system of the second device, as described in “2. (1) Alt 2 of Example 1”. For example, the first device may obtain information regarding the first message generation rule related to the second device from the header of the message queuing protocol (e.g., MQTT message header, AMQP message header, etc.) of the first message from the client device connected to the V2X system of the second device.

[0213] Next, the first device may receive a first message based on the first message generation rule from the second device (S203). Here, the first message may be a message (initially) generated according to the first message generation rule by a client device / terminal connected to the V2X system of the second device as described above. For example, the first message may include a V2X message regarding status information / cognition information, etc., of the client device / terminal connected to the V2X system of the second device. Alternatively, the first message may further include instruction information indicating a specific trigger condition, at least one parameter, or a specific parameter set applied to the first message among a plurality of trigger conditions, parameters, and / or parameter sets included in the information regarding the first message generation rule.

[0214] Next, the first device can convert the first message into a second message according to the second message generation rule (S205). For example, based on the first device supporting a second message generation rule different from the first message generation rule, the first device can convert the first message into the second message based on the first message generation rule and / or the second message generation rule.

[0215] For example, the first message generation rule may be an event-trigger-based non-periodic message generation rule, and the second message generation rule may be a periodic message generation rule. In this case, the first device may convert the first message into at least one second message that is periodically generated in response to the first message based on the predicted locations of the client device / terminal included in the first message. Alternatively, the first message generation rule may be a periodic message generation rule, and the second message generation rule may be a terminal location prediction-based non-periodic message generation rule. In this case, the first device may predict the future locations of the client device / terminal that transmitted the first message based on location / mobility information included in the first message, and convert the first message into a second message that includes the predicted future locations. Subsequently, the first device may convert the first message into the second message only when the difference between the location included in the first message received periodically and the predicted location included in the second message is greater than or equal to the maximum allowable error (or a specific threshold) (on the other hand, if the first message containing a location less than the maximum allowable error is received, the first device may not only not convert the first message into the second message but also not deliver it to its client devices).

[0216] Next, the first device can transmit the second message to client devices associated with the first device (S207). Here, the client devices to which the second message is transmitted may be devices that receive V2X services from the first device. In this case, since the first message associated with the first device is converted into the second message and provided to the client devices, the client devices can effectively obtain information corresponding to the first message through the second message even without knowing information about the message generation rules of the first message.

[0217] Alternatively, if the first message generation rule and the second message generation rule are identical, the first device may transmit the first message itself to client devices / terminals of its V2X system without converting the first message into the second message.

[0218] FIG. 21 is a diagram illustrating a method for a second device to transmit a first message to a first device.

[0219] Referring to FIG. 21, a second device may receive a first message generated from a client device based on a first message generation rule (S211). The client device is a device that receives V2X services from the second device, and the first message may be a message generated / transmitted according to a first message generation rule applied to the V2X service of the second device.

[0220] Next, the second device may transmit information regarding the first message generation rule to the first device (S213). For example, the second device may receive information regarding the second message generation rule from the first device, and the second message generation rule may be different from the first message generation rule. In this case, the second device may provide information regarding the first message generation rule to the first device in advance so that the first message generated within its V2X system by the first device is converted into a second message corresponding to the second message generation rule. For example, the first message generation rule and / or the second message generation rule may include information regarding the parameter set and indication information as described in FIG. 20 and / or “1. Example of a message generation rule and a set of parameters associated therewith,” indicating whether the message generation rule is periodic or event-trigger-based non-periodic.

[0221] Next, the second device can transmit the first message to the first device (S215). For example, the second device can transmit the first message not only to client devices / terminals receiving its V2X service (e.g., client devices / terminals located near the client device of the first message), but also to the first device connected for interoperability. Meanwhile, the second device can geo-cast to client devices / terminals that have set a subscription topic corresponding to the publication topic of the first message based on a topic defined according to a geographical area as described above.

[0222] In this way, the proposed invention effectively ensures interoperability in message exchange between service providers with different message generation rules by exchanging information regarding message generation rules between heterogeneous service providers in advance. Furthermore, by supporting interoperability between heterogeneous service providers, the proposed invention can guarantee the maximum degree of freedom in the operation methods, such as message generation rules, of each service provider's system.

[0223] Example of a communication system to which the invention is applied

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

[0225] Examples are provided in more detail below with reference to the drawings. In the following drawings and descriptions, the same reference numerals may represent the same or corresponding hardware blocks, software blocks, or function blocks unless otherwise described.

[0226] FIG. 22 illustrates a communication system to which the present invention is applied.

[0227] Referring to FIG. 22, the communication system (1) to which the present invention applies includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using 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 Thing) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with wireless communication functions, an autonomous vehicle, a vehicle capable of performing inter-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 HMDs (Head-Mounted Devices), HUDs (Head-Up Displays) equipped in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Portable devices may include smartphones, smartpads, wearable devices (e.g., smartwatches, smart glasses), computers (e.g., laptops, etc.). Home appliances may include TVs, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, base stations and networks may be implemented as wireless devices, and a specific wireless device (200a) may operate as a base station / network node to other wireless devices.

[0228] Wireless devices (100a to 100f) can be connected to a network (300) through a base station (200). Artificial Intelligence (AI) technology may be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) through the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices (100a to 100f) may communicate with each other through the base station (200) / network (300), but they may 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). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0229] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base station (200) and base station (200) / base station (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 inter-base station communication (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 / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on various proposals of the present invention, at least some of the following may be performed: 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.), resource allocation processes, etc.

[0230] Example of a wireless device to which the present invention is applied

[0231] FIG. 23 illustrates a wireless device that can be applied to the present invention.

[0232] Referring to FIG. 23, 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)} may correspond to {wireless device (100x), base station (200)} and / or {wireless device (100x), wireless device (100x)} of FIG. 22.

[0233] The first wireless device (100) includes one or more processors (102) and one or more memories (104), and may additionally include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memory (104) and / or transceivers (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts of operation disclosed in this document. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (106). Additionally, the processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and then store information obtained from the 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 store software code containing instructions for performing some or all of the processes controlled by the processor (102) or for performing the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams 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 through one or more antennas (108). The transceiver (106) may include a transmitter and / or receiver. The transceiver (106) may be combined with an RF (Radio Frequency) unit. In the present invention, the wireless device may refer to a communication modem / circuit / chipset.

[0234] The first wireless device or the first device (100) may include at least one processor (102) connected to a transceiver (106) and at least one memory (104). The at least one memory (104) may include at least one program that enables the at least one processor (102) to perform operations related to the embodiments described in FIGS. 16 through 21. The operations may include receiving information about a first message generation rule of the second device, receiving a first message from the second device, converting the first message into a second message corresponding to the second message generation rule based on supporting a second message generation rule different from the first message generation rule, and transmitting the second message to client devices.

[0235] Alternatively, at least one non-transient computer-readable medium may have at least one program written thereon that enables the above operations to be performed. Alternatively, the processing device may include at least one processor (102) and at least one memory (104) connected to at least one processor (102) and storing at least one program that enables the above operations to be performed when executed by at least one processor.

[0236] The second wireless device (200) includes one or more processors (202) and one or more memories (204), and may additionally include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memory (204) and / or transceivers (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or operation sequences disclosed in this document. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and then transmit a wireless signal containing the third information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and then store information obtained from the signal processing of the fourth information / signal 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 store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the descriptions, functions, procedures, proposals, methods, and / or operation sequences 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 through one or more antennas (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeable with an RF unit. In the present invention, the wireless device may refer to a communication modem / circuit / chip.

[0237] A second wireless device or a second device (200) may include at least one processor (202) connected to a transceiver (206) and at least one memory (204). The at least one memory (204) may include at least one program that enables the at least one processor (202) to perform operations related to the embodiments described in FIGS. 16 through 21. The operations include receiving a first message generated based on a first message generation rule from a client device and transmitting the first message to a first device, and based on the first device supporting a second message generation rule different from the first message generation rule, information regarding the first message generation rule may be provided to the first device in advance so that the first message is converted into a second message corresponding to the second message generation rule at the first device.

[0238] Alternatively, at least one non-transient computer-readable medium may have at least one program written thereon that enables the above operations to be performed. Alternatively, the processing device may include at least one processor (202) and at least one memory (204) connected to at least one processor (202) and storing at least one program that enables the above operations to be performed when executed by at least one processor.

[0239] Hereinafter, 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 Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation 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 flowcharts of operation disclosed in this document. One or more processors (102, 202) may generate a signal (e.g., baseband signal) containing a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document.

[0240] One or more processors (102, 202) may be referred to as a controller, microcontroller, microprocessor, or 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 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. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be contained in one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.

[0241] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0242] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc., of this document to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc., disclosed in this document from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may 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 connected 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, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document through 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 the received wireless signal / channel, etc. from an RF band signal to a baseband signal in order to process the received user data, control information, wireless signal / channel, etc. using one or more processors (102, 202).One or more transceivers (106, 206) can convert user data, control information, wireless signals / channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters.

[0243] Examples of wireless device applications to which the present invention is applied

[0244] FIG. 24 illustrates another example of a wireless device to which the present invention applies. The wireless device may be implemented in various forms depending on the use-example / service (see FIG. 22).

[0245] Referring to FIG. 24, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 23 and may be composed of various elements, components, units / parts, 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 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. 24. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 23. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and additional elements (140) and controls the general operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on a program / code / command / information stored in the memory unit (130). Additionally, the control unit (120) may transmit information stored in the memory unit (130) to an external (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external (e.g., another communication device) via a wireless / wired interface through the communication unit (110) in the memory unit (130).

[0246] The additional element (140) can be configured in various ways depending on the type of 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. 22, 100a), a vehicle (Fig. 22, 100b-1, 100b-2), an XR device (Fig. 22, 100c), a portable device (Fig. 22, 100d), a home appliance (Fig. 22, 100e), an IoT device (Fig. 22, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or financial device), a security device, a climate / environment device, an AI server / device (Fig. 22, 400), a base station (Fig. 22, 200), a network node, etc. Wireless devices can be used in a movable or fixed location depending on the use—e.g., service.

[0247] In FIG. 24, 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 partially 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 connected via a wire, and the control unit (120) and the first unit (e.g., 130, 140) may be connected wirelessly via the communication unit (110). Additionally, each element, component, unit / part, and / or module within the wireless device (100, 200) may include one or more additional elements. For example, the control unit (120) may be composed of one or more sets of 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.

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

[0249] FIG. 25 illustrates a vehicle or autonomous vehicle to which the present invention applies. The vehicle or autonomous vehicle may be implemented as a mobile robot, a vehicle, a train, an aerial vehicle (AV), a ship, etc.

[0250] Referring to FIG. 25, 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 part of the communication unit (110). Blocks 110 / 130 / 140a to 140d each correspond to blocks 110 / 130 / 140 of FIG. 24.

[0251] 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, roadside base stations (Roadside units), etc.), and servers. The control unit (120) can perform various operations by controlling elements of the vehicle or autonomous vehicle (100). The control unit (120) may include an Electronic Control Unit (ECU). The driving unit (140a) can drive the vehicle or autonomous vehicle (100) on the ground. The driving unit (140a) may include an engine, motor, power train, wheels, brakes, steering device, etc. The power supply unit (140b) supplies power to the vehicle or autonomous vehicle (100) and may include wired / wireless charging circuits, batteries, 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 inclination sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / reverse 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 technologies such as maintaining the driving lane, technologies for automatically adjusting speed such as adaptive cruise control, technologies for automatically driving along a predetermined path, and technologies for automatically setting a path and driving when a destination is set.

[0252] 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 path and a driving plan based on the acquired data. The control unit (120) can control the drive unit (140a) so that the vehicle or the autonomous vehicle (100) moves along the autonomous driving path according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit (110) can acquire the latest traffic information data from an external server non-periodically and can acquire surrounding traffic information data from surrounding vehicles. Additionally, 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 path and the driving plan based on the newly acquired data / information. The communication unit (110) can transmit information regarding the vehicle location, autonomous driving path, driving plan, etc. to an external server. An external server can predict traffic information data in advance using AI technology, etc., based on information collected from vehicles or autonomous vehicles, and can provide the predicted traffic information data to vehicles or autonomous vehicles.

[0253] Here, 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 according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, 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 referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in 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 names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless device (XXX, YYY) of this specification may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) with consideration for low-power communication, and is not limited to the names mentioned above. As an example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0254] The embodiments described above are combinations of the components and features of the present invention in a specific form. Each component or feature should be considered optional unless otherwise explicitly stated. Each component or feature may be implemented in a form not combined with other components or features. Additionally, it is possible to construct embodiments 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 obvious that embodiments may be constructed by combining claims that do not have an explicit citation relationship in the claims, or that new claims may be included by amendment after filing.

[0255] In this document, embodiments of the present invention are described primarily with a focus on the signal transmission and reception relationship between a terminal and a base station. This transmission and reception relationship is extended in the same or similar manner to signal transmission and reception between a terminal and a relay or between a base station and a relay. Specific operations described in this document as being performed by a base station may, in some cases, be performed by an upper node. That is, it is self-evident that various operations performed for communication with a terminal in a network consisting 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. Additionally, the terminal may be replaced by terms such as User Equipment (UE), Mobile Station (MS), and Mobile Subscriber Station (MSS).

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

[0257] In the case of implementation by firmware or software, an embodiment of the present invention may be implemented in the form of a module, procedure, function, etc., that performs the functions or operations described above. Software code may be stored in a memory unit and executed by a processor. The memory unit may be located inside or outside the processor and may exchange data with the processor by various means already known.

[0258] It is obvious to those skilled in the art that the present invention may be embodied in other specific forms without departing from the features of the invention. Accordingly, the foregoing detailed description should not be interpreted restrictively in all respects but should be considered exemplary. The scope of the invention shall be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the invention are included within the scope of the invention.

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

Claims

1. Regarding the method, A step in which the first device receives information about the first message generation rule of the second device; The step of the first device receiving a first message from the second device; Based on supporting a second message generation rule different from the first message generation rule, the first device converts the first message into a second message according to the second message generation rule; and A method comprising the step of the first device transmitting the second message to client devices.

2. In Paragraph 1, A method comprising information regarding the first message generation rule, including instruction information for the generation of a non-periodic message, a trigger condition for message transmission, and information regarding the maximum allowable time interval for message generation.

3. In Paragraph 1, A method comprising information regarding the first message generation rule, including instruction information for the generation of aperiodic messages based on terminal location prediction, information on a list of maximum allowable errors between the terminal location and the terminal predicted location, and information on the maximum allowable time interval for message generation.

4. In Paragraph 1, A method comprising information regarding the first message generation rule, including instruction information for the generation of periodic messages, a minimum allowable time interval for message transmission, and a maximum allowable time interval for message transmission.

5. In Paragraph 1, A method in which information regarding the first message generation rule and the first message are received through an information sharing entity.

6. In Paragraph 1, A method for obtaining information about the generation rule of the first message from the header of a message queuing protocol included in the first message.

7. In Paragraph 1, The information regarding the first message generation rule includes information regarding event trigger conditions related to the first message generation rule, and A method in which the first message includes information indicating a specific trigger condition associated with the first message among the event trigger conditions.

8. In Paragraph 1, A method in which the first device and the second device are a network providing V2X (Vehicle to Everything) services based on different message generation rules.

9. In at least one non-transient computer-readable medium, Includes instructions that perform operations when executed by at least one processor, The above operations are, Receiving information about the first message generation rule of the second device; Receiving a first message from the second device; Based on supporting a second message generation rule different from the first message generation rule, converting the first message into a second message corresponding to the second message generation rule; and At least one non-transient computer-readable medium comprising transmitting the above-mentioned second message to client devices.

10. In the first device, RF (Radio Frequency) transceiver; A processor connected to the above RF transceiver; and A memory comprising at least one program that performs operations when executed by the above processor; and The above operations are, Receiving information about the first message generation rule of the second device; Receiving a first message from the second device; Based on supporting a second message generation rule different from the first message generation rule, converting the first message into a second message corresponding to the second message generation rule; and A first device comprising transmitting the above second message to client devices.

11. In a processing device that controls the first device, At least one processor; and It includes at least one memory that stores instructions connected to the above at least one processor and performing operations when executed by the at least one processor, The above operations are, The first device receives information regarding the first message generation rule of the second device; The first device receives a first message from the second device; Based on supporting a second message generation rule different from the first message generation rule, the first device converts the first message into a second message according to the second message generation rule; and A processing device comprising the first device transmitting the second message to client devices.

12. Regarding the method, The second device receives a first message generated from a client device based on a first message generation rule; and The above second device includes the step of transmitting the first message to the first device, and A method in which, based on the first device supporting a second message generation rule different from the first message generation rule, the second device provides information about the first message generation rule to the first device in advance so that the first message in the first device is converted into a second message corresponding to the second message generation rule.

13. In at least one non-transient computer-readable medium, Includes instructions that perform operations when executed by at least one processor, The above operations are, Receiving a first message generated from a client device based on a first message generation rule; and It includes transmitting the above-mentioned first message to a first device, and At least one non-transient computer-readable medium, wherein, based on the first device supporting a second message generation rule different from the first message generation rule, information regarding the first message generation rule is provided in advance to the first device so that the first message is converted into a second message corresponding to the second message generation rule at the first device.

14. In the second device, RF (Radio Frequency) transceiver; A processor connected to the above RF transceiver; and A memory comprising at least one program that performs operations when executed by the above processor; and The above operations are, Receiving a first message generated from a client device based on a first message generation rule; and It includes transmitting the above-mentioned first message to a first device, and A second device, wherein, based on the first device supporting a second message generation rule different from the first message generation rule, information regarding the first message generation rule is provided in advance to the first device so that the first message is converted into a second message corresponding to the second message generation rule at the first device.

15. In a processing device that controls a second device, At least one processor; and It includes at least one memory that stores instructions connected to the above at least one processor and performing operations when executed by the at least one processor, The above operations are, A second device receives a first message generated from a client device based on a first message generation rule; and The above second device transmits the first message to the first device, and A processing device based on the fact that the first device supports a second message generation rule different from the first message generation rule, wherein information regarding the first message generation rule is provided in advance to the first device so that the first message is converted into a second message corresponding to the second message generation rule at the first device.

Images