Method for transmitting security message in wireless communication system and apparatus therefor

Abstract

A method for a first device to transmit a security message in a wireless communication system according to various embodiments and a device therefor are disclosed. Disclosed are a method and an apparatus therefor, the method comprising the steps of: periodically transmitting a security message queued in a message queue to a plurality of terminals over a network; receiving a response message from at least one terminal among the plurality of terminals through the network, the response message including delay time information on the security message; and determining, based on the delay time information, whether to transmit the security message in segments by changing a size of the message queue based on a data element characteristic of the security message.

Description

Technical Field

[0001] This disclosure relates to a method and apparatus for sending secure messages based on message queues in a wireless communication system. Background Technology

[0002] Wireless communication systems are being widely deployed to provide various types of communication services such as voice and data. Typically, a wireless communication system is a multiple access system capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of multiple access systems include Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-Carrier Frequency Division Multiple Access (SC-FDMA), and Multi-Carrier Frequency Division Multiple Access (MC-FDMA).

[0003] Sidelink (SL) refers to a communication method that establishes a direct link between user equipment (UE) and allows UEs to exchange voice or data directly without going through a base station (BS). SL is considered a solution to alleviate the burden on base stations (BS) caused by the rapid growth of data services.

[0004] Vehicle-to-Everything (V2X) is a communication technology that allows vehicles to exchange information with other vehicles, pedestrians, and infrastructure via wired / wireless communication. V2X can be categorized into four types: Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure (V2I), Vehicle-to-Network (V2N), and Vehicle-to-Pedestrian (V2P). V2X communication can be provided via PC5 and / or Uu interfaces.

[0005] As more and more communication devices require greater communication capacity when sending and receiving signals, there is a need for mobile broadband communications that are improved compared to traditional radio access technologies. Therefore, communication systems for services / UEs that are sensitive to reliability and latency are being discussed. Next-generation radio access technologies that incorporate enhanced mobile broadband communications, massive machine-type communications (MTC), and ultra-reliable and low-latency communications (URLLC) can be referred to as new radio access technologies (RAT) or new radio (NR). Even within NR, vehicle-to-everything (V2X) communications can be supported.

[0006] Figure 1 This is a diagram comparing RAT-based V2X communication before NR with NR-based V2X communication.

[0007] Regarding V2X communication, the RAT prior to NR primarily discussed schemes for providing security services based on V2X messages (such as Basic Security Messages (BSM), Cooperation Aware Messages (CAM), and Distributed Environment Notification Messages (DENM)). V2X messages can include location information, dynamic information, and attribute information. For example, a UE can send periodic message type CAM and / or event-triggered message type DENM to another UE.

[0008] For example, a CAM can include dynamic state information about the vehicle (such as direction and speed), static vehicle data (such as dimensions), and basic vehicle information (such as external lighting conditions and route details). For example, a UE can broadcast a CAM, and the CAM latency can be less than 100 ms. For example, in the event of an unexpected situation such as a vehicle malfunction or accident, a UE can generate a DENM and send it to another UE. For example, all vehicles within the UE's transmission range can receive the CAM and / or DENM. In this case, the DENM can have a higher priority than the CAM.

[0009] Regarding V2X communication, various V2X scenarios were subsequently introduced in NR. For example, various V2X scenarios can include vehicle queuing, advanced driving, extended sensors, and remote driving.

[0010] For example, based on vehicle queuing, vehicles can dynamically form groups and move together. For example, to perform queuing operations based on vehicle queuing, vehicles belonging to the group can receive periodic data from the lead vehicle. For example, vehicles belonging to the group can decrease or increase the distance between vehicles based on periodic data.

[0011] For example, based on advanced driving, vehicles can be semi-autonomous or fully autonomous. For instance, each vehicle can adjust its trajectory or maneuver based on data acquired from local sensors of nearby vehicles and / or nearby logical entities. Furthermore, for example, each vehicle can share driving intentions with nearby vehicles.

[0012] For example, based on extended sensors, vehicles, logical entities, pedestrian UEs, and / or V2X application servers can exchange raw or processed data acquired through local sensors, or live video data. Thus, for example, a vehicle can identify an improved environment relative to the environment it could detect using its own sensors.

[0013] For example, for remote vehicles operated by unlicensed individuals or in hazardous environments, remote drivers or V2X applications can operate or control remote vehicles based on remote driving. For instance, when routes are predictable, such as in the case of public transportation, cloud-based driving can be used to operate or control remote vehicles. For example, access to a cloud-based backend service platform can be considered for remote driving.

[0014] In the field of NR-based V2X communications, a method for specifying service requirements for various V2X scenarios, such as vehicle queuing, advanced driving, extended sensors, and remote driving, is discussed. Summary of the Invention

[0015] Technical issues

[0016] The purpose of this disclosure is to provide a more accurate and efficient method for sending and receiving data and messages.

[0017] Those skilled in the art will understand that the objectives that can be achieved by various embodiments of this disclosure are not limited to those specifically described above, and that the above and other objectives that can be achieved by various embodiments of this disclosure will become clearer from the following detailed description.

[0018] Technical solution

[0019] In one aspect of this disclosure, a method is provided for transmitting a security message by a first device in a wireless communication system. The method includes: periodically transmitting security messages queued in a message queue to a plurality of user equipments (UEs) via a network; receiving, via the network, a response message including delay time information for the message from at least one of the plurality of UEs; and determining whether to perform segmented transmission of the security message based on the delay time information and by changing the size of the message queue based on characteristics of data elements of the security message.

[0020] Alternatively, based on the reception of delay time information including a value equal to or greater than a first threshold time, the size of the message queue is changed to a first size corresponding to the size of the mandatory data element among the mandatory and optional data elements constituting the security message. Based on the queuing of mandatory data elements in the message queue having the first size, the first device sends a first segmented security message as part of the security message.

[0021] Alternatively, the first segmented security message may also include indication information for segmented transmission of the security message.

[0022] Alternatively, based on the transmission of the first segmented security message, the size of the message queue is changed to a second size based on the size of the optional data elements. Based on the second size of the queue of optional data elements in the message queue, the first device sends a second segmented security message as part of the security message.

[0023] Alternatively, based on the fact that the traffic of at least one session through which the security message is sent is equal to or greater than a certain threshold, the first device sends only a first segment of the security message for the security message.

[0024] Alternatively, based on the reception of delay time information including a value equal to or greater than a first threshold time, the first device changes the size of the message queue based on the size of the dynamic data elements constituting the security message.

[0025] Alternatively, the security message may be a message based on Message Queuing Telemetry Transport (MQTT).

[0026] Alternatively, the security message may include a basic security message (BSM), a personal security message (PSM), or a collaboration-aware message (CAM).

[0027] In another aspect of this disclosure, a non-transitory computer-readable storage medium is provided, which records instructions for performing the method of sending security messages described above.

[0028] In another aspect of this disclosure, a first apparatus configured to perform the method of sending security messages described above is provided.

[0029] In another aspect of this disclosure, a processing device configured to control the transmission of the aforementioned security message is provided.

[0030] In another aspect of this disclosure, a method for forwarding security messages over a network in a wireless communication system is provided. The method includes: receiving a security message from a first device; sending a forwarding message to a plurality of user equipments (UEs) for forwarding the security message; receiving a response message from at least one of the plurality of UEs including delay time information for the security message; and determining whether to perform segmented transmission of the forwarding message based on the delay time information by changing the size of a message queue for the forwarding message. The size of the message queue can be changed based on the characteristics of the data elements of the forwarded security message.

[0031] In another aspect of this disclosure, a non-transitory computer-readable storage medium is provided, which records instructions for performing the method of forwarding security messages as described above.

[0032] In another aspect of this disclosure, a network configured to forward the aforementioned security messages is provided.

[0033] In another aspect of this disclosure, a processing device configured to control the forwarding of the aforementioned security messages is provided.

[0034] Beneficial effects

[0035] According to various implementation methods, data and messages can be sent and received more accurately and efficiently in wireless communication systems.

[0036] The effects to be achieved by the implementation method are not limited to those specifically described above, and those skilled in the art to which the implementation method pertains will gain a clearer understanding of other effects not mentioned herein based on the following detailed description. Attached Figure Description

[0037] The accompanying drawings, which are included to provide a further understanding of this disclosure and are incorporated into and constitute a part of this application, illustrate embodiments of this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0038] Figure 1 This is a diagram used to explain the difference between RAT-based V2X communication prior to NR and NR-based V2X communication.

[0039] Figure 2 The structure of an LTE system with applicable implementation methods is illustrated.

[0040] Figure 3 The structure of an NR system according to an applicable implementation is illustrated.

[0041] Figure 4 The structure of an NR radio frame applicable to the implementation method is illustrated.

[0042] Figure 5 The time slot structure of an NR frame applicable to this implementation is illustrated.

[0043] Figure 6 A communication architecture available in a 6G system based on an embodiment of the present disclosure is shown.

[0044] Figure 7 The electromagnetic spectrum based on embodiments of this disclosure is shown.

[0045] Figure 8 An example of a typical NTN scenario based on a transparent payload, based on an embodiment of this disclosure, is shown.

[0046] Figure 9 An example of a typical NTN scenario based on a regenerable payload, based on an embodiment of this disclosure, is shown.

[0047] Figure 10 An example of sensing operation based on an embodiment of this disclosure is shown.

[0048] Figure 11 An example of a radio protocol architecture for SL communication is given.

[0049] Figure 12 An example of a UE performing V2X or SL communication is shown.

[0050] Figure 13Examples of resource units for V2X or SL communication are shown.

[0051] Figure 14 An example of a BWP based on an embodiment of this disclosure is shown.

[0052] Figure 15 The process of a UE performing V2X or SL communication based on a resource allocation mode, according to an embodiment of this disclosure, is illustrated.

[0053] Figure 16 This is a diagram used to explain the architecture of the V2N interface.

[0054] Figure 17 It is a diagram used to explain the interface related to the connection structure between two servers providing SoftV2X services.

[0055] Figure 18 This is a diagram used to explain the data processing of a bridge.

[0056] Figure 19 This is a diagram used to explain the buffer model used for V2X communication.

[0057] Figures 20 to 22 This is a diagram used to explain how to send messages by applying a message queue scheme.

[0058] Figure 23 and Figure 24 This is a diagram used to explain the method of sending messages to a BSM based on a message queue scheme.

[0059] Figure 25 This is a diagram used to explain the method by which the first device sends a security message.

[0060] Figure 26 This is a diagram used to explain the method of forwarding security messages received from a first device over a network.

[0061] Figure 27 An example of a communication system applied to this disclosure is shown.

[0062] Figure 28 Wireless devices applicable to this disclosure are illustrated.

[0063] Figure 29 Another example of a wireless device that applies the present disclosure is illustrated.

[0064] Figure 30 Examples of vehicles or autonomous vehicles applicable to this disclosure are shown. Detailed Implementation

[0065] Wireless communication systems are multiple access systems that support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems, and so on.

[0066] Sidelinks refer to communication schemes that establish direct links between user equipment (UEs) to enable direct exchange of voice or data between UEs without assistance from a base station (BS). Sidelinks are considered a way to address the burden on the BS caused by rapidly increasing data traffic.

[0067] Vehicle-to-everything (V2X) refers to a communication technology that allows vehicles to exchange information with other vehicles, pedestrians, and infrastructure entities via wired / wireless communication. V2X can be categorized into four types: vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and vehicle-to-pedestrian (V2P). V2X communication can be provided through PC5 interfaces and / or Uu interfaces.

[0068] As more and more communication devices require greater communication capacity when sending and receiving signals, there is a need for improved mobile broadband communications compared to traditional radio access technologies. Therefore, communication systems considering service / UE sensitivity to reliability and latency are being discussed. Next-generation radio access technologies that incorporate enhanced mobile broadband communications, massive MTC, and ultra-reliable and low-latency communications (URLLC) can be referred to as new radio access technologies (RAT) or new radio (NR). Even within NR, V2X communication can be supported.

[0069] The technologies described in this article can be used in various radio access systems such as Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), and Single Carrier Frequency Division Multiple Access (SC-FDMA). CDMA can be implemented as radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented as radio technologies such as Global System for Mobile Communications (GSM), Universal Packet Radio Service (GPRS), and Enhanced Data Rate for GSM Evolution (EDGE). OFDMA can be implemented as radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of Evolved UMTS (E-UMTS) that uses Evolved UTRA (E-UTRA). 3GPP LTE uses OFDMA for downlink and SC-FDMA for uplink. LTE-A is an evolution of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolution of 3GPP LTE / LTE-A / LTE-A pro.

[0070] 5G NR is the successor to LTE-A and is a new type of clean-state mobile communication system characterized by high performance, low latency, and high availability. 5G NR can use all available spectrum resources, including low-frequency bands below 1 GHz, mid-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter-wave) bands of 24 GHz and above.

[0071] For clarity, the description primarily focuses on LTE-A or 5G NR, but the technical spirit of the implementation is not limited thereto.

[0072] Figure 2 An example of the structure of an LTE system applicable to this disclosure is illustrated. This may also be referred to as an evolved UMTS terrestrial radio access network (E-UTRAN) or an LTE / LTE-A system.

[0073] Reference Figure 2E-UTRAN includes an evolved Node B (eNB) 20 that provides the control plane and user plane to UE 10. UE 10 can be fixed or mobile and can also be referred to as a mobile station (MS), user terminal (UT), subscriber station (SS), mobile terminal (MT), or radio device. eNB 20 is a fixed station that communicates with UE 10 and can also be referred to as a base station (BS), base transceiver system (BTS), or access point.

[0074] The eNB 20 can connect to each other via the X2 interface. The eNB 20 connects to the evolved packet core (EPC) 39 via the S1 interface. More specifically, the eNB 20 connects to the mobility management entity (MME) via the S1-MME interface and to the serving gateway (S-GW) via the S1-U interface.

[0075] EPC 30 includes an MME, an S-GW, and a Packet Data Network Gateway (P-GW). The MME contains access or capability information about the UE and is primarily used for UE mobility management. The S-GW is a gateway with E-UTRAN as its endpoint, and the P-GW is a gateway with Packet Data Network (PDN) as its endpoint.

[0076] Based on the lowest three layers of the Open Systems Interconnection (OSI) reference model known in communication systems, the radio protocol stack between the UE and the network can be divided into Layer 1 (L1), Layer 2 (L2), and Layer 3 (L3). These layers are defined in pairs between the UE and the evolved UTRAN (E-UTRAN) for data transmission via the Uu interface. The Physical (PHY) layer at L1 provides information delivery services on the physical channel. The Radio Resource Control (RRC) layer at L3 is used to control radio resources between the UE and the network. For this purpose, the RRC layer exchanges RRC messages between the UE and the eNB.

[0077] Figure 3 The structure of an NR system applicable to this disclosure is illustrated.

[0078] Reference Figure 3 Next-generation radio access networks (NG-RAN) can include next-generation Node Bs (gNBs) and / or eNBs that provide user plane and control plane protocols to UEs. Figure 3 In this example, NG-RAN is shown as consisting only of gNBs. gNBs and eNBs are connected to each other via the Xn interface. gNBs and eNBs are connected to the 5G core network (5GC) via the NG interface. More specifically, gNBs and eNBs are connected to the Access and Mobility Management Function (AMF) via the NG-C interface and to the User Plane Function (UPF) via the NG-U interface.

[0079] Figure 4 The structure of an NR radio frame applicable to this disclosure is illustrated.

[0080] Reference Figure 4 Radio frames can be used for UL and DL transmissions in NR. A radio frame is 10 ms long and can be defined by two 5 ms half-frames. HF can include five 1 ms subframes. Subframes can be divided into one or more time slots, and the number of time slots in SF can be determined based on the subcarrier spacing (SCS). Each time slot can include 12 or 14 OFDM(A) symbols depending on the cyclic prefix (CP).

[0081] In the normal CP (NCP) scenario, each time slot can include 14 symbols, while in the extended CP (ECP) scenario, each time slot can include 12 symbols. In this paper, symbols can be OFDM symbols (or CP-OFDM symbols) or SC-FDMA symbols (or DFT-s-OFDM symbols).

[0082] Table 1 below lists the number of symbols N per slot in the NCP case based on the SCS configuration μ. slot symb The number of time slots per frame, N frame,u slot and the number of time slots N in each subframe subframe,u slot .

[0083] [Table 1]

[0084] Table 2 below lists the number of symbols per slot, the number of slots per frame, and the number of slots per subframe in the case of ECP, according to SCS.

[0085] [Table 2]

[0086] In NR systems, different OFDM(A) parameter sets (e.g., SCS, CP length, etc.) can be configured for multiple cells aggregated for a UE. Therefore, the (absolute time) duration of time resources (e.g., subframes, slots, or TTIs) comprising the same number of symbols (for convenience, time resources are collectively referred to as time units (TUs)) can be configured to be different for the aggregated cells.

[0087] In NR, various parameter sets or SCSs can be supported to support a wide range of 5G services. For example, a 15 kHz SCS can support wide areas in traditional cellular bands, while a 30 kHz / 60 kHz SCS can support dense urban areas, lower latency, and wider carrier bandwidth. When the SCS is 60 kHz or higher, bandwidths wider than 24.25 GHz can be supported to overcome phase noise.

[0088] The NR band can be defined by two types of frequency ranges, FR1 and FR2. The numerical values ​​of the frequency ranges can be changed. For example, the two types of frequency ranges can be configured as shown in Table 3 below. In the frequency ranges used in the NR system, FR1 can represent the "range below 6 GHz," and FR2 can represent the "range above 6 GHz," and can be referred to as millimeter wave (mmW).

[0089] [Table 3]

[0090] As mentioned above, the frequency range of the NR system can be changed. For example, FR1 can include a frequency band from 410 MHz to 7125 MHz as shown in Table 24 below. That is, FR1 can include a frequency band of 6 GHz (or 5850 MHz, 5900 MHz, 5925 MHz, etc.) or higher. For example, the frequency band of 6 GHz (or 5850 MHz, 5900 MHz, 5925 MHz, etc.) or higher included in FR1 can include unlicensed frequency bands. Unlicensed frequency bands can be used for various purposes, such as for vehicle communications (e.g., autonomous driving).

[0091] [Table 4]

[0092] Figure 5 The time slot structure of an NR frame applicable to this disclosure is illustrated.

[0093] Reference Figure 5 A time slot comprises multiple symbols in the time domain. For example, a time slot may include 14 symbols in normal CP and 12 symbols in extended CP. Alternatively, a time slot may include 7 symbols in normal CP and 6 symbols in extended CP.

[0094] A carrier can comprise multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple consecutive subcarriers in the frequency domain (e.g., 12 subcarriers). A bandwidth portion (BWP) can be defined as multiple consecutive (P) RBs in the frequency domain, and a BWP can correspond to a set of parameters (e.g., SCS, CP length, etc.). A carrier can comprise up to N (e.g., 5) BWPs. Data communication can be performed within an active BWP. In the resource grid, each element can be called a resource element (RE) and can be mapped to a complex symbol.

[0095] The radio interface between UEs or between a UE and the network may include layers L1, L2, and L3. In various embodiments of this disclosure, layer L1 may represent the physical layer. Layer L2 may, for example, represent at least one of the MAC layer, RLC layer, PDCH layer, or SDAP layer. Layer L3 may, for example, represent the RRC layer.

[0096] Figure 6 A communication architecture available in a 6G system based on an embodiment of the present disclosure is shown. Figure 6 The implementation methods can be combined with various implementation methods of this disclosure.

[0097] In 6G, new network features may include the following.

[0098] - Satellite Integrated Network

[0099] - Connecting Intelligence: Unlike previous generations of wireless communication systems, 6G is revolutionary, and wireless evolution can be updated from "connecting things" to "connecting intelligence." AI can be applied to every step of the communication process (or every signal processing step described below).

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

[0101] - Ubiquitous Super 3D Connectivity: Access to networks and core network functions for drones and very low Earth orbit satellites will be established with ubiquitous 6G super 3D connectivity.

[0102] Among the new network features of 6G, some common requirements may be as follows.

[0103] - Small community network

[0104] - Ultra-dense heterogeneous networks

[0105] - High-capacity return

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

[0107] - Software and virtualization

[0108] The key implementation technologies of 6G systems are described below.

[0109] - Artificial Intelligence (AI): When AI is introduced into communications, it can simplify and improve real-time data transmission. AI can determine methods for performing complex target tasks using countless analyses. In other words, AI can improve efficiency and reduce processing latency. Time-consuming operations such as switching, network selection, and resource scheduling can be performed immediately using AI. AI can also play an important role in M2M, machine-to-human, and human-to-machine interactions. Additionally, AI can enable instant communication in brain-computer interfaces (BCIs). AI-based communication systems can be supported by metamaterials, smart structures, smart networks, smart devices, intelligent cognitive radios, self-maintaining wireless networks, and machine learning.

[0110] Terahertz (THz) communication: Data rates can be increased by increasing bandwidth. This can be achieved by using sub-THz communication with wide bandwidth and applying advanced massive MIMO technology. THz waves (also known as submillimeter radiation) generally refer to the frequency band between 0.1 THz and 10 THz, where the corresponding wavelengths are in the range of 0.03 mm to 3 mm. The frequency band range of 100 GHz to 300 GHz (sub-THz band) is considered the main part of the THz band used for cellular communication. When the sub-THz band is added to the millimeter wave band, it increases the capacity of 6G cellular communication. The 300 GHz to 3 THz band in the defined THz band is in the far-infrared (IR) band. The 300 GHz to 3 THz band is part of the optical band, but it is on the boundary of the optical band and just behind the RF band. Therefore, the 300 GHz to 3 THz band is similar to RF.

[0111] Figure 7 The electromagnetic spectrum based on embodiments of this disclosure is shown. Figure 7 The implementation methods can be combined with various embodiments of this disclosure. Key characteristics of THz communication include (i) a wide range of available bandwidth supporting very high data rates, and (ii) high path loss at high frequencies (highly directional antennas are indispensable). The narrow beamwidth generated in highly directional antennas reduces interference. The small wavelength of THz signals allows a greater number of antenna elements to be integrated into devices and base stations operating in this band. Therefore, advanced adaptive placement techniques capable of overcoming range limitations can be used.

[0112] - Massive MIMO technology

[0113] - Holographic Beamforming (HBF)

[0114] - Optical wireless technology

[0115] - Free Space Optics (FSO) Backhaul Network

[0116] - Quantum communication

[0117] - Cellular communication

[0118] - Integration of wireless information and power transmission

[0119] - Integration of wireless communication and sensing

[0120] - Integrated access and backhaul networks

[0121] Big Data Analytics

[0122] - Reconfigurable smart surfaces

[0123] - Metaverse

[0124] - Blockchain

[0125] - Unmanned Aerial Vehicles (UAVs): UAVs, or drones, will be a crucial element in 6G wireless communication. In most cases, UAV technology can be used to provide high-speed data wireless connectivity. Base station (BS) entities can be installed within UAVs to provide cellular connectivity. UAVs can possess specific characteristics not found in fixed BS infrastructure, such as ease of deployment, strong line-of-sight links, and controlled degrees of freedom of mobility. During emergencies such as natural disasters, the deployment of terrestrial telecommunications infrastructure is economically infeasible and sometimes unable to provide service in volatile environments. UAVs can easily handle such situations. UAVs will be a new paradigm in the field of wireless communication. This technology contributes to the three fundamental requirements of wireless networks, such as eMBB, URLLC, and mMTC. UAVs can also serve numerous purposes such as improved network connectivity, fire detection, disaster emergency services, security and surveillance, pollution monitoring, parking monitoring, and accident monitoring. Therefore, UAV technology is considered one of the most important technologies for 6G communication.

[0126] - Autonomous Driving (Autonomous Driving): Vehicle-to-Everything (V2X), a core element in establishing autonomous driving infrastructure, refers to technologies that enable vehicles to communicate and share with various elements on the road used for autonomous driving, such as vehicle-to-vehicle (V2V) and vehicle-to-infrastructure (V2I). To maximize the performance of autonomous driving and ensure high safety, high transmission speeds and low latency technologies are essential. Furthermore, in the future, autonomous driving may need to go beyond simply delivering warnings or guidance messages to the driver and actively intervene in vehicle operations, directly controlling the vehicle in dangerous situations. Therefore, given the potentially enormous amount of information that needs to be sent and received, autonomous driving is expected to be maximized in 6G, which offers higher transmission speeds and lower latency than 5G.

[0127] - Non-terrestrial network (NTN): NTN can refer to a network or network segment that utilizes radio frequency (RF) resources on satellites (or unmanned aerial system (UAS) platforms). Figure 8 An example of a typical NTN scenario based on a transparent payload, based on an embodiment of this disclosure, is shown. Figure 9 An example of a typical NTN scenario based on a regenerable payload, based on an embodiment of this disclosure, is shown. Figure 8 or Figure 9 The implementation methods can be combined with various implementation methods of this disclosure. See also... Figure 8 A satellite (or UAS platform) can establish a service link with the UE. The satellite (or UAS platform) can connect to a gateway via a feeder link. The satellite can connect to a data network via a gateway. Beam coverage refers to the area where signals transmitted by the satellite can be received. (See reference...) Figure 9 A satellite (or UAS platform) can establish a service link with the UE. A satellite (or UAS platform) connected to the UE can connect to another satellite (or another UAS platform) via an inter-satellite link (ISL). Another satellite (or another UAS platform) can connect to the gateway via a feeder link. Based on regenerated payloads, a satellite can connect to the data network via a gateway and another satellite. If there is no ISL between two satellites, a feeder link between the satellite and the gateway may be required. Figure 8 and Figure 9This is merely an example of an NTN scenario, and NTN can be implemented based on various types of scenarios. For example, a satellite (or UAS platform) can implement transparent or regenerated (with onboard processing) payloads. For example, a satellite (or UAS platform) can generate multiple beams over a designated service area based on its field of view. For example, the field of view of a satellite (or UAS platform) can vary depending on the onboard antenna pattern and minimum elevation angle. For example, a transparent payload can include RF filtering, frequency conversion, and amplification. Therefore, the waveform signal repeated by the payload can remain unchanged. For example, a regenerated payload can include RF filtering, frequency conversion and amplification, demodulation / decryption, switching and / or routing, and encoding / modulation. For example, a regenerated payload can be substantially equivalent to equipping a satellite (or UAS platform) with all or part of the base station functionality.

[0128] - Integrated Sensing and Communication (ISAC): Wireless sensing is a technology used to acquire information about the characteristics of an environment and / or objects within that environment, using radio frequency (RF) to determine the distance (range), angle, or instantaneous linear velocity of an object. RF sensing capabilities can provide services for locating objects without a device, as there is no need to connect the object via a device in the network. The ability to obtain range, velocity, and angle information from RF signals can provide a wide range of new functionalities, such as various object detection, object recognition (e.g., vehicles, people, animals, UAVs), and high-accuracy localization, tracking, and activity recognition. For example, wireless sensing services can provide input to various vertical structures (e.g., unmanned aerial vehicles, smart homes, V2X, factories, railways, public safety, etc.) to enable applications such as intruder detection, assisted vehicle handling and navigation, trajectory tracking, collision avoidance, traffic management, health, and activity monitoring. In some cases, wireless sensing can also use non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of wireless sensing services (i.e., sensing operation) can rely on processing the transmission, reflection, and scattering of wireless sensing signals. Therefore, wireless sensing has the potential to enhance traditional systems, from communication networks to wireless and sensing networks. Figure 10 An example of sensing operation based on an embodiment of this disclosure is shown. Figure 10 The implementation methods can be combined with various implementation methods of this disclosure. Specifically, Figure 10 (a) illustrates an example of sensing using a co-located sensing receiver and sensing transmitter (e.g., single-site sensing), and Figure 10 (b) shows an example of sensing using separate sensing receivers and sensing transmitters (e.g., dual-station sensing).

[0129] Figure 11 The radio protocol architecture used for SL communication is shown. Specifically, Figure 11(a) shows the NR user plane protocol stack. Figure 11 (b) shows the NR control plane protocol stack.

[0130] The following text will describe the side link synchronization signal (SLSS) and synchronization information.

[0131] As SL-specific sequences, SLSS can include a primary sidelink synchronization signal (PSSS) and a secondary sidelink synchronization signal (SSSS). PSSS can be referred to as the primary sidelink synchronization signal (S-PSS), and SSSS can be referred to as the secondary sidelink synchronization signal (S-SSS). For example, a 127-bit M sequence can be used for S-PSS, and a 127-bit gold sequence can be used for S-SSSS. For example, a UE can use S-PSS to detect the initial signal and obtain synchronization. For example, a UE can use S-PSS and S-SSS to obtain detailed synchronization and detect the synchronization signal ID.

[0132] The Physical Sidelink Broadcast Channel (PSBCH) can be a (broadcast) channel used to transmit basic (system) information that the UE needs to know before SL signal transmission and reception. For example, basic information may include information related to SLSS, duplex mode (DM), time-division duplex uplink / downlink (TDD) UL / DL configuration, resource pool information, application type related to SLSS, subframe offset, and broadcast information. For example, to evaluate PSBCH performance in NR V2X, the PSBCH payload size can be 56 bits, including a 24-bit CRC.

[0133] S-PSS, S-SSS, and PSBCH can be included in a block format that supports periodic transmission (e.g., an SL synchronization signal (SS) / PSBCH block, referred to below as a sidelink synchronization signal block (S-SSB)). The S-SSB can have the same set of parameters (i.e., SCS and CP lengths) as the Physical Sidelink Control Channel (PSCCH) / Physical Sidelink Shared Channel (PSSCH) on the carrier, and its transmission bandwidth can be within a pre-set SL BWP. For example, the S-SSB can have a bandwidth of 11 RBs. Similarly, the PSBCH can span 11 RBs. Furthermore, the frequency location of the S-SSB can be pre-set. Therefore, the UE does not need to perform frequency hypothesis detection to discover the S-SSB on the carrier.

[0134] In an NR SL system, multiple parameter sets with different SCS and / or CP lengths can be supported. In this case, as the SCS increases, the length of the time resource for the transmitting UE to transmit S-SSBs can be shortened. Therefore, the S-SSB coverage can be narrowed. Accordingly, to ensure S-SSB coverage, the transmitting UE can transmit one or more S-SSBs to the receiving UE within an S-SSB transmission period, depending on the SCS. For example, the number of S-SSBs transmitted by the transmitting UE to the receiving UE within an S-SSB transmission period can be pre-configured or configured for the transmitting UE. For example, the S-SSB transmission period can be 160 ms. For example, a 160 ms S-SSB transmission period can be supported for all SCSs.

[0135] For example, when the SCS is 15 kHz in FR1, the transmitting UE can send one or two S-SSBs to the receiving UE within one S-SSB transmission period. For example, when the SCS is 30 kHz in FR1, the transmitting UE can send one or two S-SSBs to the receiving UE within one S-SSB transmission period. For example, when the SCS is 60 kHz in FR1, the transmitting UE can send one, two, or four S-SSBs to the receiving UE within one S-SSB transmission period.

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

[0137] When the SCS is 60 kHz, two types of CP can be supported. Furthermore, the structure of the S-SSB transmitted from the transmitting UE to the receiving UE can depend on the CP type. For example, the CP type can be Normal CP (NCP) or Extended CP (ECP). Specifically, for example, when the CP type is NCP, the number of symbols to which the PSBCH in the S-SSB transmitted by the transmitting UE is mapped can be 9 or 10. On the other hand, for example, when the CP type is ECP, the number of symbols to which the PSBCH in the S-SSB transmitted by the transmitting UE is mapped can be 7 or 6. For example, the PSBCH can be mapped to the first symbol in the S-SSB transmitted by the transmitting UE. For example, upon receiving an S-SSB, the receiving UE can perform Automatic Gain Control (AGC) operation during the time period corresponding to the first symbol of the S-SSB.

[0138] Figure 12An example of a UE performing V2X or SL communication is shown.

[0139] Reference Figure 12 In V2X or SL communication, the term UE can primarily refer to the user's UE. However, a BS can also be considered a UE when a network device, such as a BS, sends and receives signals according to a communication scheme between UEs. For example, UE 1 can be a first device 100, and UE 2 can be a second device 200.

[0140] For example, UE 1 can select a resource element corresponding to a specific resource from a resource pool (which represents a resource set). Then, UE 1 can transmit an SL signal through the resource element. For example, UE 2, as a receiving UE, can receive the configuration of the resource pool in which UE 1 can transmit signals, and can detect UE 1's signals in the resource pool.

[0141] Here, when UE 1 is within the BS's connection range, the BS can notify UE 1 of the resource pool. On the other hand, when UE 1 is outside the BS's connection range, another UE can notify UE 1 of the resource pool, or UE 1 can use a pre-configured resource pool.

[0142] Typically, a resource pool can consist of multiple resource units, and each UE can select one or more resource units and send SL signals through the selected units.

[0143] Figure 13 Examples of resource units for V2X or SL communication are shown.

[0144] Reference Figure 13 The frequency resources in the resource pool can be divided into NF sets, and the time resources in the resource pool can be divided into NT sets. Therefore, a total of NF sets can be defined in the resource pool. NT resource units. Figure 13 An exemplary case of a periodically repeating resource pool with NT subframes is shown.

[0145] like Figure 13 As shown, a resource element (e.g., element #0) can appear periodically and repeatedly. Alternatively, to achieve diversity effects in the time or frequency dimension, the index of the physical resource element to which a logical resource element is mapped can change over time in a predetermined pattern. In this structure of resource elements, a resource pool can represent the set of resource elements available to a UE intended to transmit SL signals.

[0146] Resource pools can be further subdivided into several types. For example, based on the content of the SL signals sent in each resource pool, resource pools can be divided as follows.

[0147] (1) Scheduling assignment (SA) can be a signal that includes information such as the location of the resources through which the UE transmits SL data channels, the modulation and coding scheme (MCS) or multiple-input multiple-output (MIMO) transmission scheme required for demodulating other data channels, and timing advance (TA). SA can be multiplexed with SL data and transmitted through the same resource element. In this case, the SA resource pool can refer to the resource pool where SA and SL data are multiplexed and transmitted. SA can be called the SL control channel.

[0148] (2) The SL data channel (Physical Side Link Shared Channel (PSSCH)) can be a resource pool through which the transmitting UE transmits user data. When SA and SL data are multiplexed and transmitted together in the same resource element, only the SL data channel other than the SA information can be transmitted in the resource pool for the SL data channel. In other words, the resource element (RE) used to transmit SA information in a separate resource element in the SA resource pool can still be used to transmit SL data in the resource pool for the SL data channel. For example, the transmitting UE can map the PSSCH to consecutive PRBs and transmit them.

[0149] (3) The discovery channel can be a resource pool used by the transmitting UE to send information such as its ID. Through this channel, the transmitting UE can allow neighboring UEs to discover the transmitting UE.

[0150] Even when the aforementioned SL signals have the same content, they can use different resource pools based on the transmission / reception characteristics of the SL signals. For example, even when the SL data channel or discovery message is the same in the signal, they can be classified into different resource pools based on the SL signal transmission timing (e.g., transmission at the reception time of the synchronization reference signal or transmission by applying a predetermined TA at the reception time), resource allocation scheme (e.g., the BS assigns separate signal transmission resources to a separate transmitting UE, or a separate transmitting UE selects a separate signal transmission resource within the resource pool), signal format (e.g., determined by the number of symbols occupied by each SL signal in a subframe, or the number of subframes used for the transmission of one SL signal), signal strength from the BS, transmission power of the SL UE, etc.

[0151] Figure 14 An example of a BWP based on an embodiment of this disclosure is shown. Figure 14 The implementation methods can be combined with various implementation methods of this disclosure. Figure 14 In this implementation, it is assumed that the number of BWPs is 3.

[0152] Reference Figure 14A common resource block (CRB) can be a carrier resource block numbered from one end of a carrier frequency band to the other. Alternatively, a PRB can be a resource block numbered within each BWP. Point A can indicate a common reference point for the resource block grid.

[0153] BWP can be determined by point A and its offset N from point A. start BWP and bandwidth N size BWP Configuration. For example, point A could be an external reference point for the PRB of a subcarrier 0-aligned carrier for all parameter sets (e.g., all parameter sets supported by the network on that carrier). For example, offset could be the PRB spacing between the lowest subcarrier in a given parameter set and point A. For example, bandwidth could be the number of PRBs in a given parameter set.

[0154] Sidelink synchronization signals (SLSS) can include a primary sidelink synchronization signal (PSSS) and a secondary sidelink synchronization signal (SSSS) as sidelink (SL) specific sequences. The PSSS can be called the primary sidelink synchronization signal (S-PSS), and the SSSS can be called the secondary sidelink synchronization signal (S-SSS). For example, a 127-bit M-sequence can be used for the S-PSS, and a 127-bit gold sequence can be used for the S-SSS. For example, a UE can use the S-PSS for initial signal detection and synchronization acquisition. For example, a UE can use both the S-PSS and S-SSS to obtain detailed synchronization and detect the synchronization signal ID.

[0155] The Physical Sidelink Broadcast Channel (PSBCH) can be a (broadcast) channel used to transmit default (system) information, which the UE must know before sending / receiving SL signals. For example, default information could include SLSS-related information, duplex mode (DM), Time Division Duplex (TDD) uplink / downlink (UL / DL) configuration, resource pool-related information, SLSS-related application type, subframe offset, broadcast information, etc. For instance, to evaluate PSBCH performance, in NRV2X, the PSBCH payload size can be 56 bits, including 24 bits of Cyclic Redundancy Check (CRC).

[0156] S-PSS, S-SSS, and PSBCH can be included in a block format that supports periodic transmission (e.g., SL synchronization signal (SS) / PSBCH block, hereinafter, sidelink synchronization signal block (S-SSB)). The S-SSB can have the same set of parameters (i.e., SCS and CP lengths) as the Physical Sidelink Control Channel (PSCCH) / Physical Sidelink Shared Channel (PSSCH) in the carrier, and the transmission bandwidth can exist within a (pre)configured sidelink (SL) BWP. For example, the S-SSB can have a bandwidth of 11 resource blocks (RBs). Similarly, the PSBCH can exist across 11 RBs. Furthermore, the frequency location of the S-SSB can be (pre)configured. Therefore, the UE does not need to perform hypothesis detection at the frequency to discover the S-SSB in the carrier.

[0157] Figure 15 The process of a UE performing V2X or SL communication based on a resource allocation mode, according to an embodiment of this disclosure, is illustrated. Figure 15 The implementation methods can be combined with various implementation methods of this disclosure.

[0158] Reference Figure 15 In (a) of resource allocation mode 1, the base station may schedule SL resources to be used for SL transmissions of the UE. For example, in step S1500, the base station may send information related to SL resources and / or information related to UL resources to the first UE. For example, UL resources may include PUCCH resources and / or PUSCH resources. For example, UL resources may be resources that report SL HARQ feedback to the base station.

[0159] For example, the first UE may receive information from the base station relating to Dynamic Grant (DG) resources and / or Configuration Grant (CG) resources. For example, CG resources may include CG Type 1 resources or CG Type 2 resources. In this disclosure, DG resources may be resources configured / assigned by the base station to the first UE via Downlink Control Information (DCI). In this disclosure, CG resources may be (periodic) resources configured / assigned by the base station to the first UE via DCI and / or RRC messages. For example, in the case of CG Type 1 resources, the base station may send an RRC message to the first UE including information relating to the CG resources. For example, in the case of CG Type 2 resources, the base station may send an RRC message to the first UE including information relating to the CG resources, and the base station may send a DCI relating to the activation or release of the CG resources to the first UE.

[0160] In step S1510, the first UE may send a PSCCH (e.g., Side Link Control Information (SCI) or Level 1 SCI) to the second UE based on resource scheduling. In step S1520, the first UE may send a PSSCH related to the PSCCH (e.g., Level 2 SCI, MAC PDU, data, etc.) to the second UE. In step S1530, the first UE may receive a PSFCH related to the PSCCH / PSSCH from the second UE. For example, it may receive HARQ feedback information (e.g., Negative Acknowledgment (NACK) or Acknowledgment (ACK) information) from the second UE via the PSFCH. In step S1540, the first UE may send / report HARQ feedback information to the base station via PUCCH or PUSCH. For example, the HARQ feedback information reported to the base station may be information generated by the first UE based on the HARQ feedback information received from the second UE. For example, the HARQ feedback information reported to the base station may be information generated by the first UE based on pre-configured rules. For example, the DCI may be a DCI used for SL scheduling.

[0161] Reference Figure 15 In (b) of resource allocation mode 2, the UE can determine SL transmission resources within SL resources configured by the base station / network or pre-configured SL resources. For example, the configured SL resources or pre-configured SL resources can be a resource pool. For example, the UE can autonomously select or schedule resources for SL transmission. For example, the UE can perform SL communication by autonomously selecting resources within the configured resource pool. For example, the UE can perform a sensing and resource selection (reselection) process to autonomously select resources within a selection window. For example, sensing can be performed on a sub-channel basis. For example, in step S1510, the first UE, having selected resources in the resource pool, can use the resources to send a PSCCH (e.g., Side Link Control Information (SCI) or Level 1 SCI) to the second UE. In step S1520, the first UE can send a PSSCH (e.g., Level 2 SCI, MAC PDU, data, etc.) related to the PSCCH to the second UE. In step S1530, the first UE can receive a PSFCH related to the PSCCH / PSSCH from the second UE.

[0162] Reference Figure 15 (a) or Figure 15(b) For example, the first UE may send an SCI to the second UE on the PSCCH. Alternatively, for example, the first UE may send two consecutive SCIs (e.g., two-level SCIs) to the second UE on the PSCCH and / or PSSCH. In this case, the second UE may decode the two consecutive SCIs (e.g., two-level SCIs) to receive the PSSCH from the first UE. In this disclosure, an SCI sent on the PSCCH may be referred to as 1st SCI, first SCI, first-level SCI, or first-level SCI format, and an SCI sent on the PSSCH may be referred to as 2nd SCI, second SCI, or second-level SCI format.

[0163] Reference Figure 15 (a) or Figure 15 In step (b), the first UE can receive the PSFCH in step S1530. For example, the first UE and the second UE can determine the PSFCH resource, and the second UE can use the PSFCH resource to send HARQ feedback to the first UE.

[0164] Reference Figure 15 In step (a), the first UE may send SLHARQ feedback to the base station via PUCCH and / or PUSCH in step S1540.

[0165] The aforementioned sidelinks can be defined as communication between UEs or direct communication between UEs. In this case, PSCCH can be defined as the physical control channel for communication between UEs, PSSCH can be defined as the physical data channel or physical shared channel for communication between UEs, and PSFCH can be defined as the physical feedback transmission channel between UEs.

[0166] A SoftV2X system can be a system in which a SoftV2X server receives VRU messages or Personal Safety Messages (PSMs) from vulnerable road users (VRUs) or V2X vehicles, and transmits information about neighboring VRUs or vehicles based on the VRU messages or PSMs. Alternatively, it can analyze road conditions on which neighboring VRUs or vehicles are moving, and send messages such as collision warnings to neighboring VRUs or vehicles based on the analyzed information (e.g., via downlink signals) via V2X communication using a UU interface. Here, the VRU message can be a message sent to the SoftV2X server via the UU interface, and can include mobility information about the VRU, such as the VRU's location, direction of movement, path, and speed. That is, the SoftV2X system can use methods such as receiving VRU and / or vehicle mobility information related to V2X communication via the UU interface, and controlling VRU routes or VRU movement flows based on the mobility information received by the SoftV2X server (such as a network). The SoftV2X system can be configured in relation to V2N communication.

[0167] The following text will describe in detail the methods for providing V2X services over a network, based on the above.

[0168] For V2N services, a message-based inter-network interface structure

[0169] V2X services play a crucial role in ensuring safety (including collision prevention) and controlling efficient traffic flow by allowing road users (vehicles, roadside units (RSUs), pedestrians, etc.) to send status information (location, speed, size, etc.) or environmental information (map information, signal information, etc.) to nearby road users. Currently, various V2X services exist, employing multiple communication schemes (short-range communication, long-range communication). Service level requirements are defined for the organic operation of V2X services involving multiple Intelligent Transportation System (ITS) stations.

[0170] V2X messages can be generated by vehicles and infrastructure and can carry information related to the surrounding environment, road conditions, situations, and events. V2X messages can be used for various purposes, including vehicle-to-vehicle interaction, vehicle-to-infrastructure communication, object detection, and warning systems. In other words, such V2X messages can be generated by vehicles or infrastructure and can include information related to the surrounding environment, situations, and events. Furthermore, V2X messages can include information collected through vehicle sensors, GPS information, and communication devices, and can be configured in a standardized format. Standardized V2X messages can include various data such as location, speed, acceleration, lane change information, and traffic signal status. V2X messages can be sent in a one-way or two-way manner, and the information included in V2X messages can be updated and processed in real time. In V2X environments requiring low-latency communication, rapid message transmission is essential, and latency of a few milliseconds or less can be extremely important for rapid response to situations such as accident prevention or collision warning. Furthermore, since V2X messaging-based communication relies on real-time interaction between vehicles and infrastructure, message delivery speed and reliability play a crucial role in providing warnings to drivers and enabling vehicles to respond appropriately to situations. Therefore, V2X messaging communication requires minimizing message delivery time and latency, and necessitates a design that implements appropriate buffering models and transmission methods for rapid data exchange based on network technologies and protocols suitable for real-time communication.

[0171] The connectivity architecture used to provide this V2X service considers a vehicle-to-network-to-everything (V2N2X) (or V2N or SoftV2X) architecture that extends to the network scope. This architecture can be schematically represented at a high level, depending on the requirements of specific use cases met by the vehicles, infrastructure, service providers, and information-sharing instances. The V2N architecture will be described in detail below.

[0172] Figure 16 This is a diagram used to explain the architecture of the V2N interface.

[0173] refer to Figure 16 The architecture of a V2N interface (or SoftV2X interface) can include an Infrastructure Owner Operator (IOO) Autonomous System (AS), a V2N Original Equipment Manufacturer (OEM) Autonomous System (AS), a V2N OEM application, a V2N Service Provider (SP) Autonomous System (V2XAS), and an information sharing instance. The detailed definition of each configuration is described below.

[0174] - IOO AS: As a local player providing services related to the automotive and transportation sectors, IOO AS is typically based on infrastructure such as sensors and roads or parking facilities. For example, an IOO AS can be a city, road authority, road operator, or city or parking provider.

[0175] - V2N OEM AS: As an OEM backend component (e.g., a control entity) that manages V2N OEM applications within the vehicle OEM domain, the V2N OEM AS enables vehicle connectivity. The V2N OEM AS performs proxy and filtering roles for information sent and received by the vehicle OEM applications.

[0176] - V2N OEM Applications: As in-vehicle components that provide service functions for service users within the vehicle OEM domain, V2N OEM applications receive data from other system components for service operations. Depending on the situation, V2N OEM applications may implement functions to warn human drivers or to support advanced driver assistance systems (ADAS) or autonomous driving (AD) functions in the vehicle.

[0177] - V2N V2XAS: In the service provider domain, V2N Service Provider Application Server (V2N SPAS) is a general term for a participant that provides services related to the automotive domain, and can provide services such as VRU protection services, map services, traffic information services and fleet operator services.

[0178] - Information Sharing Instances: As entities connecting each AS, information sharing instances can exchange information across national or regional borders. For example, an information sharing instance can act as a relay during connection establishment by hosting servers that are expected to be connected (similar to a rendezvous server). Furthermore, when relaying messages from entities that do not conform to standards, the information sharing instance can perform appropriate translation functions as needed.

[0179] Figure 17 It is a diagram used to explain the interface related to the connection structure between two servers providing SoftV2X services.

[0180] refer to Figure 17 A MEC or V2X system 100 may include a UE (RSU or server) 140 that sends and receives V2X messages, a first server 120 that provides SoftV2X services, and a bridge 110. The MEC or V2X system 100 may use the bridge 110 to perform data or message exchange with an external agent 221.

[0181] This connection structure can be based on interface 1. To Interface 5 At least one of the following can be used to establish the connection. For each interface, the connection structure and operation methods can be defined as follows. At least one of the interfaces described below can be an interface using the Message Queuing Telemetry Transport (MQTT) based message sending and receiving protocol. For ease of description, MQTT-based clients and MQTT-based brokers are defined and described as clients and brokers, respectively.

[0182] (1) Interface 1

[0183] Interface 1 This can be the interface between the UE 140, which generates and sends V2X messages, and the first server. The UE (or RSU, server, etc.) can be the entity publishing messages or the client subscribing to messages.

[0184] (2) Interface 2

[0185] Interface 2 This can be the interface for the proxy 121 connecting the first server 120 and the bridge (client-message relay module-client) connecting the message sending and receiving protocol to the external entity. Through interface 2... It can exchange data or messages that are compatible with standardized formats based on MQTT (the message format defined in the 5G Automotive Association (5GAA) standard), or it can exchange data or messages using non-standard message or protocol formats operated internally by the first server 120.

[0186] (3) Interface 3

[0187] Interface 3 This can be an interface connecting internal client 111 and external client 113 included in bridge 110. Alternatively, interface 3... This can be an interface connecting internal client 111, message relay module 115, and external client 113. For interface 3... At least one of the two clients can directly execute the function corresponding to the function of message relay module 115. In this case, message relay module 115 can be omitted.

[0188] Specifically, Interface 3 This could be an interface used to relay the message payload obtained by decoding the MQTT protocol stack at the internal client 111 to the external client 113. The internal client 111 uses interface 3... The relayed data or messages can have the same characteristics as those transmitted through interface 2. The received data or messages may have different message formats. For example, through interface 2. The received data or messages may include additional fields or data defined by the V2X system or the first server 120 for proprietary operations and / or for enabling faster and more efficient delivery of V2X services to users. On the other hand, through interface 3... The relayed message can be a purely standardized message according to a standardized format (see 5GAA TR-239129).

[0189] For example, internal client 111 can access the interface through interface 2. The received data or message can have the MQTT protocol stack (layer) removed, and a purely standardized message with the MQTT protocol stack removed can be sent to external client 113. Alternatively, internal client 111 can send the message via interface 2. The received data or messages are converted into messages corresponding to the messaging protocol of the external server.

[0190] (4) Interface 4 and / or Interface 5

[0191] Interface 4 This could be an interface connecting external client 113 and external proxy 221. Here, interface 4... This can be an interface for exchanging data via a Transmission Control Protocol (TCP) session connection. In this case, external client 113 and external agent 221 can be pre-initialized or configured with send and receive IP addresses, ports, topics, and configuration information. Alternatively, external client 113 can convert data or messages sent from internal client 111 with the MQTT protocol stack removed into data or messages with the MQTT protocol stack associated with the external agent. External client 113 can then publish or send the converted data or messages to external agent 221.

[0192] Interface 5 The connection between external client 113 and external proxy 221 can be established via a User Datagram Protocol (UDP) session connection. The UDP-based external client can unidirectionally transfer data from interface 3... The received messages or data are sent to the agent of the second server (or switch).

[0193] Furthermore, the aforementioned bridge can relay messages or data between two servers based on improved functionality and logic. These improved features and logic will be described in detail below.

[0194] Advanced functions and logic of bridges

[0195] Figure 18 This is a diagram used to explain the data processing of a bridge.

[0196] Data or messages related to a typical V2X service can be sent from a V2X entity or V2X system (application, infrastructure (e.g., RSU), or server) to a corresponding MQTT-based broker based on appropriate filtering information (e.g., geographic information). The data or messages can then be sent to the V2X application server via a pre-established session with the broker. In this case, data or messages for the V2X service of the V2X entity may need to be delivered to another external server (MEC, server, network, or AS). For this purpose, the V2X application server can use the bridge described above to connect to the external server. As mentioned above, the bridge can include symmetric TCP-based internal and external clients to maintain the existing TCP-based client receive or subscribe structure in the connection between the two servers using the application messaging protocol.

[0197] refer to Figure 18 The internal client can forward messages sent by the first agent to the external client after performing data processing according to additional logic.

[0198] Figure 18 Each component shown can operate as follows. For ease of description, it is assumed that data or messages are published from a first agent to provide the following description. However, the same description can be equivalently applied to the case where data or messages are published from a second agent on an external server (only the sending and receiving entities differ).

[0199] (1) Transmitter

[0200] Entities that generate and send data (applications, infrastructure (e.g., RSUs) or servers) can group and send data through connected or connectable agents (agent A, agent B, agent C, ..., agent N) according to a transport protocol (e.g., MQTT protocol).

[0201] (2) Receiver

[0202] A receiver can receive and process data sent from the sender and network. The receiver (receiving side) can accept data sent from the sender and network, decode packets, and reconstruct the packets into the message to be sent. In this case, in addition to plain message data, data for additional functions can support filtering functions for external transmission. For example, the receiver can be an external client.

[0203] (3) Data processing

[0204] Data processing can classify data or messages sent from the sender through appropriate data processing, connect the classified data or messages to the desired data interface, and perform appropriate data exchange. Data processing can operate according to the functions described below. Data processing can be performed at the application server or internal client.

[0205] 1) Data receiver

[0206] A data receiver (or internal client) can receive data or messages from a sender and perform decoding according to the transport protocol and encoding stream method. The data receiver can identify the occurrence time of messages acquired during the decoding process (e.g., through Extensible Markup Language (XML) data of the messages). The data receiver can send information about the occurrence time of the identified data or messages to a database tree, allowing the identified data or messages to be stored in the database based on their occurrence time. In this case, the message occurrence time can be set as a basic parameter.

[0207] 2) Database tree

[0208] Database trees can be configured to create tree-based databases (e.g., red-black tree-based databases) that categorize received data or messages based on their occurrence time within the relational database structure. Database trees can interoperate with the database processing manager's algorithms to configure a database where received data or messages are categorized based on the degree of correlation among additional information (e.g., geographic information, direction information, speed information, etc.) referencing the message's occurrence time. Alternatively, internal clients can configure databases to include the aforementioned database tree.

[0209] 3) Data Processing Manager

[0210] The data processing manager may include an algorithm capable of creating tree structures in the database and a send (Tx) buffer balancer. The algorithm may be an application programming interface (API) for configuring the tree in the database based on parameters of the data or messages. The buffer balancer can perform appropriate buffering and queuing of data or messages included in the database and can manage the encapsulation of queued data or messages. Alternatively, an internal client may include the data processing manager.

[0211] 4) Network interface

[0212] The network interface can encapsulate queued data using the stack required in the network domain and can perform preparation for sending messages that include the encapsulated data.

[0213] The functional units of the bridge 110 can adaptively turn data processing functions on or off based on the size or priority of the database and the grouping insertion conditions, thereby controlling or adjusting the buffer.

[0214] The following text describes in detail a buffer model that can efficiently send messages based on the transport environment associated with SoftV2X or V2X services.

[0215] Buffering Model and Aggregation Method for V2X Services

[0216] The following problems may occur in the above-described transmission structure for V2X message communication.

[0217] - Network bandwidth and congestion: Due to various mesh-based connections (vehicles, infrastructure, servers), in real-time communication environments requiring the transmission of large amounts of data, network bandwidth may be insufficient, or data processing may be concentrated within a predetermined time period, leading to significant congestion in the communication environment. Insufficient network bandwidth or congestion in the communication environment can affect the transmission speed and reliability of message transmission.

[0218] - Loss of message validity due to inappropriate buffering models or aggregation time: If V2X vehicles or infrastructure do not support appropriate buffering models, timely response to actual emergencies involving vehicles, pedestrians, etc. may not be possible, and messages may not be delivered to surrounding UEs within the effective time (or within the delay requirement).

[0219] - Quality Assurance Mechanisms: In real-time communication, latency and reliability can be critical. However, since most modules managing transmission send messages based on a static buffering model, they may not support an appropriate response to latency variations.

[0220] In V2X messaging systems, buffering models currently only perform buffering within a period corresponding to a single operational message size, and no suitable buffering model is defined. For example, buffering models in V2X messaging systems are designed such that a message is sent as it is generated. Specifically, for Sensor Data Sharing Messages (SDSM), the sending device aggregates objects in an arbitrary order, defines the value of the DetectedObjectList field to generate a single message, and sends the generated message. This buffering method (or message generation and transmission method) is a message completion-based buffering method, rather than a buffering method based on the actual transmission environment, and therefore may not be able to send data or messages efficiently according to the transmission environment, or the message may not be transmitted within the required effective time (e.g., service latency requirements).

[0221] The following are proposed: (1) a buffer condition for queuing received data; and (2) a technique for streaming the remaining data after sending basic data in a Uu-based connection session in a conventional architecture, in which the queued data is generated as a data payload and then a header is created.

[0222] In V2X services, message aggregation for message buffer modeling and transport packet configuration can be performed at various levels (vehicle, infrastructure, and network). Optimal handling (or buffer modeling) of this data or message queue can lead to faster message decoding and an improved user experience at the receiving end.

[0223] The message buffer modeling will be described in detail below.

[0224] Figure 19 This is a diagram used to explain the buffer model used for V2X communication.

[0225] refer to Figure 19 A buffer model for V2X communication may include an RX buffer configured to receive and aggregate data, and a TX buffer configured to receive the received and aggregated data and perform buffering for transmission.

[0226] Typically, data can be received at the RX buffer and stored in an array according to predetermined criteria. For output, some data stored in the array can be delivered to the TX side, and the array of output buffers on the TX side can buffer the data for transmission. In this case, The value and used to set The duration of the TX buffer period can vary depending on the implementation, but it can typically be configured based on the output of a single message. However, the configuration of the TX buffer period is not based on the actual data stream, but rather on the buffering of completed messages in the array. Furthermore, data reception does not involve receiving blocks of data one byte at a time, but can involve inputting a sequence of bytes of partially received data into the RX buffer. Therefore, an efficient aggregation method and buffer model for data packets need to be redefined. The criteria for aggregating data or data packets and / or defining the buffer model need to consider not only the buffering of the array but also the characteristics of the transport network and / or the actual object detection time. In other words, the aggregation and / or buffer model for data or data packets can be reasonably defined so that message buffering and queuing are performed based on the characteristics of the transport network and / or the actual object detection time.

[0227] The following will describe in detail a method for performing message buffering and queuing based on the characteristics of the transport network and / or the actual object detection time (hereinafter referred to as buffering condition 1 or buffering condition 2).

[0228] (1) Buffer condition 1 (treating TCP round-trip time (RTT) as a characteristic of the transmission network)

[0229] TCP RTT is a metric used to measure the time required for data to travel from source to destination and for a response to return in a TCP-based network. RTT is used as an important indicator of network latency and can play a significant role in evaluating the performance and stability of TCP communication. In TCP-based message passing, (i) a request message is first sent from the source (e.g., client) to the destination (e.g., server), (ii) the destination processes the request message and then sends a response message (or acknowledgment (ACK)) back to the source, and (iii) the source receives the response message from the destination. RX and TX buffers can be used based on the connection of the TCP session. (=TCP RTT) is used to buffer data. In this case, to avoid unnecessary consumption of (receive / decode) time on the network, the client can pre-determine the data buffering time and fill the TX buffer. When sending a data block on the TX side based on RTT buffering, the data block can be received on the RX side through a symmetric (ideal) buffer model. In this case, It can be calculated on an average basis, and the specific application method can be regarded as an implementation method problem.

[0230] (2) Buffer condition 2 (considering object detection time, which is the time used to generate or output object data)

[0231] Typically, object detection can be performed 5 to 7 times per second, generating or outputting data for the detected objects. That is, objects can be detected every 143 ms. This means that, based on 30 frames per second (fps), objects in an image can be detected once every 4.29 frames or every 5 frames. In the following text, the time it takes for the On-Board Unit (OBU) and Roadside Unit (RSU) to detect objects and output object information or object data is assumed to be... (Object detection time). In this case, it is based on the time when the actual data is generated. Execution buffering can implement a buffering model corresponding to data generation and input.

[0232] (3) Message queue size reflecting message characteristics - mandatory / optional

[0233] One method for determining the size of a message queue (or buffer) that reflects message characteristics is to determine the size of the message queue such that queuing is performed based on the priority of mandatory fields. Message characteristics may involve relationships between mandatory fields or data elements and optional fields or data elements, or relationships between static, dynamic, or semi-static data elements. For example, a PSM (which is a message used for V2X services) has mandatory fields or data elements and optional fields or data elements, i.e., static, dynamic, or semi-static data elements predefined according to a standardized data format, as shown in Table 7.

[0234] Message transmission according to the queuing scheme can be a scheme in which data or messages are temporarily buffered in a buffer for data or message transmission and sent asynchronously. Typically, a message can be sent when the entire message is complete. In this case, the RX side can perform buffering of the received data or messages and can process or output the buffered messages. The proposed message queuing scheme can be adaptively applied in different ways depending on network conditions. For example, the proposed message queuing scheme could be one where data corresponding to a specific priority is queued first and messages are sent in segments.

[0235] For example, Basic Security Messages (BSM) and PSM, representative messages of V2X, are designed for real-time communication, and therefore transmission intervals can be critical. Typically, BSM and PSM can be sent (periodically) at intervals between 100ms and 300ms. Message validity may decrease when messages arrive at transmission intervals of 300ms or greater (or when the interval between message generation and message reception is 300ms or greater). Therefore, additional operations may be needed to ensure message validity when no message is received on the RX side within a specific time. For example, when no message is received within the time required by the RX side based on the message generation time (@DSecond) and RTT, and message validity decreases (e.g., when delays between 1ms and 300ms occur consecutively), the TX side can apply a message queuing scheme or change the size of the message queue. Alternatively, similar to the TX side, the RX side can determine the time relevant to message validity based on timestamps and processing times, and can periodically send current service layer status messages (e.g., messages including determined time information) in the form of response messages or Hypertext Transfer Protocol (HTTP) responses (e.g., JavaScript Object Notation (JSON)). For example, the RX side can calculate message latency based on the message's timestamp (i.e., the message's generation time) and processing time (i.e., the decoding completion time). The RX side can report or send information about latency to the TX side via response messages or HTTP responses (e.g., JSON). In this case, the TX side (or RX side) can determine whether to apply a queuing scheme or change the size of the message queue used for sending messages.

[0236] Alternatively, the RX side (receiving device or network) can request the transmission of messages for which a message queuing scheme is applied from the TX side (transmitting device or UE) based on the processing status. For example, server A can receive and process BSMs from multiple UEs or servers. In this case, when the number of connected UEs exceeds a predetermined number, or when the message reception delay time is equal to or greater than a specific threshold time, server A can request the UEs to send messages for which the proposed message queuing scheme is applied.

[0237] The method for sending messages based on the proposed message queue scheme will be described in detail below.

[0238] Figures 20 to 22 This is a diagram used to explain how to send messages by applying a message queue scheme.

[0239] Reference Figure 20 The sending device can adaptively adjust or change the size of the message queue. To do this, the sending device can define an appropriate container by taking into account the characteristics of the message.

[0240] In the prior art, the sending device can execute or generate a message queue based on the completion of the entire message (solid box + dashed box), and can send the message. In contrast, according to the proposed disclosure, the sending device can execute or generate a message queue based on whether bits (bytes) of a size defined for a specific container are input. Here, a container or a specific container refers to a specific set of fields. Such a container corresponds to a concept associated with a message queue, and in the following text, for ease of description, the terms "message queue" and "container" are used interchangeably. Alternatively, the container can be a configuration associated with a buffer size.

[0241] Specifically, such as Figure 20 As shown, the transmitting device can be configured with a first container (or mandatory container) for mandatory data elements or mandatory fields and a second container (or optional container) for optional data elements or optional fields. Figure 20 middle, This indicates the state of an empty container with no input data, and This indicates the state of receiving or buffering data bytes based on the presence of a specific message or data (e.g., mandatory data within the data of a specific message is preferentially generated or buffered). The received or buffered data bytes can be queued or input into a first container. When the first container is completely filled with data, the sending device can send the message by executing a message queue (or, when the first container is completely filled, the sending device can execute message queuing and output for transmission). Next, when the first container becomes empty due to message transmission, the sending device can generate or buffer optional data for the message and can send the message queued or queued in a second container. When all the data in the message has been output or sent, both the first and second containers return to an empty state. After this, the transmitting device can repeat the process. arrive The processing involves pre-configuring a first container corresponding to the size of the mandatory fields and a second container corresponding to the size of the optional fields, and then sending the entire message data in segments using a message queue scheme based on the first and second containers. Here, the size of the first and second containers can be defined as the size of the message queue.

[0242] Depending on specific triggering conditions (e.g., traffic environment), it is also possible to apply only the message queuing scheme of the mandatory container (or the first container) (excluding steps). For example, when the traffic of the channel or session used for message transmission is equal to or greater than a certain threshold, the sending device can send the message by buffering data only in the mandatory container, without performing buffered or segmented message transmission based on the optional container (second container). Alternatively, the sending device can perform queuing of the mandatory data of the message according to the instructions of the receiving device. In this case, in a first segmented message including mandatory data for the mandatory container and a second segmented message including optional data for the optional container, the sending device can send only the first segmented message to the receiving device.

[0243] Reference Figure 21 The transmitting device may include a segment manager 211 for managing message segmentation, a message buffer 212, an Abstract Syntax Tag 1 (ASN.1) encoder 213, and delivery / transmission encapsulation units 214 and 215. Furthermore, the receiving device may include a segment manager 216 for managing message segmentation, a message buffer 217, an ASN.1 decoder 218, and delivery or transmission decapsulation units 219 and 220. The segment manager 211 of the transmitting device can exchange indication information related to the transmission mode with the segment manager 216 of the receiving device (see Table 6).

[0244] Specifically, the sending device can support the streaming transmission of the entire message by segmenting the message based on the aforementioned mandatory and optional containers. In this case, the sending device can segment the entire data of a single message into data for mandatory fields (or mandatory data elements) (hereinafter, first segment data) and data for optional fields (or optional data elements) (hereinafter, second segment data). When the buffering of data in the mandatory container is complete, the sending device can send the first segment message including the buffered data, i.e., the first segment data, and when the buffering of data in the optional container is complete, the sending device can send the second segment message including the buffered data, i.e., the second segment data. As described above, the sending device can send a message by segmenting the message into first segment messages and second segment messages.

[0245] Alternatively, the mandatory or optional container can be defined as the size of the message queue. For example, the sending device can configure a message queue with a size corresponding to the size of the mandatory field of the entire data of a single message, and can send a first segmented message when buffering of the message queue is complete. After sending the first segmented message, the sending device can configure the size of the message queue to correspond to the size of the optional field, and can send a second segmented message when buffering of the message queue is complete. In this case, the sending device can send the entire data of a single message in segments of mandatory and optional data elements by changing the size of the message queue based on the size of the mandatory data elements and the size of the optional data elements. To this end, among the multiple data elements of the entire data of a single message, mandatory data elements can be generated or buffered with a higher priority than optional data elements.

[0246] Alternatively, when a stream of data bytes for a single Extensible Markup Language (XML) message to be sent is continuously input, the sending device can segment the data into mandatory and optional containers to send the entire message data using message buffers and / or message queues. For example, the sending device can apply a message queuing scheme using mandatory and optional containers to segment the entire data element of a single message into mandatory and optional data elements and send them.

[0247] In this case, additional information needs to be defined so that the receiving device can identify the entire data element transmitted in segments. For example, the additional information can be added in the form of a sequence of header bytes defining the segments in the start sequence of the segment container or in the protocol header (e.g., the extension header), such as... Figure 21 As shown. Additional information or header byte sequences can be added to the container during the encoding of segmented data in the ASN.1 encoder 213, such as... Figure 21 As shown, or it can be added during the encapsulation of data into a delivery protocol (e.g., MQTT) in delivery encapsulation unit 214.

[0248] For example, as shown in Table 5, additional information or header byte sequences may include information such as pattern, length, and container initialization.

[0249] [Table 5]

[0250] As described above, the transmitting device can send segmented messages, which include segmented data and a header byte sequence for identifying the segmented data. The receiving device can identify that the received message includes segmented data by examining the header bit sequence in the delivery decapsulation unit 219 or the ASN.1 decoder 218. In this case, the receiving device can configure initialization for message data reception in the segment manager 216, and the segment manager 216 can instruct the message buffer 217 to perform appropriate buffering or queuing while delivering initialization information to the message buffer 217. The message buffer 217 can output data by performing container-based data queuing according to the segmented transmission mode received from the segment manager 216 (one of the segmented transmission modes defined in Table 6). The segment managers 211 and 216, connected for sending and receiving, can change the segmented transmission mode according to the network traffic environment, or can change the segmented transmission mode based on input from the user interface or user experience (UI / UX).

[0251] [Table 6]

[0252] The following sections will describe in detail methods for sending the entire data of a single message in segments based on static, quasi-static, or dynamic characteristics of the message.

[0253] The characteristics of a message can be predefined or classified into standardized message types, as shown in Table 7 below.

[0254] [Table 7]

[0255] (4) Message queue size reflecting message characteristics - static / dynamic

[0256] When sending messages (BSM, PSM) for V2X services, the data for that message can include static data with static characteristics and dynamic data with characteristics that change for each instance. For example, a PSM as a message for a V2X service can have dynamic data elements or fields predefined according to a standardized message format, as well as static data elements or fields, as shown in Table 7 above.

[0257] When sending messages for V2X services over a network, the sending device can repeatedly send static data with the same information through a data session established with the network. In this case, the receiving device may be inefficient in terms of message or data processing due to the repeated reception of static data. Therefore, when static and dynamic data can be sent or processed separately between the sending and receiving devices, the sending device can separate the static and dynamic data from the data configured in a single message and can prioritize the generation or transmission of dynamic data (alternatively, after sending static data, the sending device can send messages containing only dynamic data for a certain period of time). In this case, the receiving device can avoid unnecessary repeated reception of static data, thereby performing message decoding processing more quickly.

[0258] When a sending device transmits only a portion of the data configured in a single message (e.g., dynamic data), a receiving device may detect that the received message does not correspond to the complete message. In this case, the receiving device may consider or interpret the received message as consisting only of dynamic data. Dynamic data may include data elements that differ from those in previously received messages.

[0259] Reference Figure 22 The sending device can use XML parsing syntax and standard element templates to send messages to the receiving device in XML. In this case, after the transmission of static data elements within the entire data element of a single message is complete, the sending device can send segmented messages to the receiving device that only include dynamic or quasi-static data elements. That is, the sending device can appropriately adjust or change the transmission periods of static data and dynamic data in the form of a hierarchical structure and template conforming to XML. Here, the different transmission periods between static and dynamic data can be determined by the sending device's declaration and / or by a request from the receiving device. In this data transmission, Table 5 and Figure 21 The header byte sequence of the additional information described herein is added to the message (e.g., a segmented message). The transmitting device can provide the receiving device with information related to the separate transmission and initialization process of static and dynamic data through the additional information.

[0260] Figure 23 and Figure 24 This is a diagram used to explain the method of sending messages for BSM based on a message queue scheme.

[0261] For V2X services, BSMs (Balanced Messages) can be used in applications that exchange safety data related to vehicle status. BSMs can include the data required for safety and can be frequently sent to surrounding vehicles. For example, BSMs can be sent at a rate of ten times per second. Such a transmission rate can be reduced using congestion control algorithms.

[0262] Reference Figure 23 Part 1 may correspond to mandatory fields or data elements that need to be included in the BSM, and Part 2 may correspond to optional fields or data elements that can be included when required by the strategy.

[0263] As mentioned above, BSM can include Core Data (Part 1), Part 2, and region data. (See reference...) Figure 23 and Figure 24 In (a), the transmitting device can preferentially generate BSMCoredata as mandatory information for conflict assessment, cache the BSMCoredata in a buffer, queue the cached BSMCoredata into a message queue, and execute the message queue to send the segmented message of the BSM. That is, even before generating the entire BSM, the transmitting device can send a message queue (or segmented container) including BSMCoredata. Such segmented data fields or data elements can be processed at the receiving device through a series of processes using the aforementioned additional information (or extended header byte sequence) to obtain meaningful data. Compared with the prior art, the proposed method can reduce the encoding latency of message transmission by selectively sending only mandatory fields or data elements before generating the entire data of the message. In addition, the advantage provided by this disclosure is that the transmission or generation period of optional fields or data elements is adjustable while maintaining the transmission or generation period of mandatory fields or data elements. This can reduce the total end-to-end (E2E) latency while reducing unnecessary redundancy.

[0264] Next, refer to Figure 24(b) The sending device can transmit a PSM by dividing it into static and dynamic data, which is a representative V2X message. Specifically, the sending device can classify the data elements of the PSM into static, quasi-static, and dynamic elements (see Table 7), and can apply a transmission mode based on each attribute (see Table 6). More specifically, data elements included in a PSM can be classified into static, quasi-static, and dynamic data elements based on their attributes. Among the classified data elements, selected data elements can be sent preferentially according to the segmented transmission mode described above. For example, the PSM can be configured as a template in XML, where attributes indicating static or dynamic characteristics can be set based on parent elements, and child elements can inherit the corresponding parent element's attributes. It can be assumed that the tag of each data element is uniquely identifiable at the receiving device. Compared to the prior art, the proposed method can reduce encoding latency for message transmission by selectively pre-generating and sending only dynamic and / or static data before generating the entire PSM data. Furthermore, the proposed method offers the advantage that the transmission or generation time of optional fields or data elements is adjustable while maintaining the transmission or generation time of mandatory fields or data elements. This reduces overall end-to-end latency while minimizing unnecessary redundancy.

[0265] Figure 25 This is a diagram used to explain the method by which the first device sends a security message.

[0266] The first device can be a UE that provides security messages, including the perception information of the first device, to multiple UEs via a network according to the message queuing scheme proposed above. For example, the first device can be a client that sends and receives security messages for SoftV2X services via a Uu interface based on the MQTT protocol, and the network can be an MQTT broker. The first device can establish a session with the network for transmitting MQTT-based messages, and can transmit security messages to the network through this session.

[0267] Reference Figure 25 The first device can periodically send security messages queued in a message queue to multiple UEs via the network (S251). As described above, when security messages are queued in a message queue of a size corresponding to the size of the security message, the first device can send the queued security messages. The security messages can be MQTT-based messages. Furthermore, security messages can include BSM, PSM, or CAM (Cooperation Aware Message) messages for V2X services.

[0268] Next, the first device can receive a response message including delay time information for the message from at least one of the plurality of UEs via the network (S253). The delay time information may be information about the interval between the time when the first device generates the security message and the time when the at least one UE receives the security message. For example, the at least one UE can calculate the delay time information corresponding to the difference between the time when the message is generated and the time when the security message is decoded, and can send the response message including the calculated delay time information to the first device via the network.

[0269] The first device can determine whether to perform segmented transmission of the security message by changing the size of the message queue based on delay time information (S255). When the delay time information includes a delay time equal to or greater than a predetermined first threshold time, the first device can change the size of the message queue based on the characteristics of the data elements of the security message, and can send the security message by segmenting it into a first segment security message and a second segment security message based on the message queue. Conversely, when the delay time information includes a delay time less than the threshold time, or when no delay time information is received, the first device can send the entire security message without changing the size of the message queue based on the characteristics of the data elements of the security message. The first threshold time can be predetermined based on the service requirements or delay requirements of the V2X service provided through the security message as described above.

[0270] Specifically, when the delay time information includes a delay time equal to or greater than a predetermined first threshold time, the first device can change the size of the message queue based on the size of the mandatory and optional data elements included in the security message. The first device can change the size of the message queue to a size corresponding to or the same as the size of the mandatory data elements. When the queuing of mandatory data elements in the message queue is complete, the first device can send a first segmented security message containing only the mandatory data elements queued in the message queue. For this purpose, the first device can preferentially generate or buffer mandatory data elements. Here, the first segmented security message may additionally include indication information for notifying the segmented transmission of the security message, as described above. When the transmission of the first segmented security message is complete, the first device can change the size of the message queue to a size corresponding to or the same as the size of the optional data elements. When the queuing of optional data elements in the message queue is complete, the first device can send a second segmented security message containing only the optional data elements queued in the message queue.

[0271] Alternatively, the first device may receive an instruction from the network to perform segmented transmission of a security message by changing the size of the message queue, without receiving delay time information. For example, when the delay time information includes a delay time equal to or greater than a first threshold time, the network may instruct or request the first device to change the size of the message queue based on the characteristics of the data elements of the security message, and perform segmented transmission of the security message based on the change in message queue size. Alternatively, the network may specify the characteristics of the data elements to be considered for changing the message queue size. For example, when the delay time information includes a delay time equal to or greater than the first threshold time and less than a second threshold time (which is greater than the first threshold time), the network may instruct the first device to segment the security message into mandatory data elements and optional data elements for transmission. In this case, the network may preferentially receive from the first device a first segmented security message that includes only mandatory data elements. On the other hand, when the delay time information includes a delay time equal to or greater than the second threshold time, the network may instruct the first device to segment the security message into dynamic data elements and static data elements for transmission. In this case, the network may preferentially receive from the first device a first segmented security message that includes only dynamic data elements.

[0272] Alternatively, based on the traffic of a session established with the network or based on an instruction from the network, the first device may send only the first segment of the first and second segment security messages for the security message. That is, the first device may skip the transmission of the second segment security message for optional data elements.

[0273] Alternatively, the first device can change the size of the message queue based on the size of the static data elements, quasi-static data elements, and dynamic data elements included in the security message. For example, as described above, the first device can change the size of the message queue to a size corresponding to the size of the dynamic data elements included in the security message. When the queuing of dynamic data elements in the message queue is complete, the first device can execute the message queue to send segmented security messages containing only dynamic data elements. When the transmission of segmented security messages containing only dynamic data elements is complete, the first device can change the size of the message queue to a size corresponding to the size of the quasi-static data elements. When the queuing of quasi-static data elements in the message queue is complete, the first device can execute the message queue to send segmented security messages containing only quasi-static data elements. When the transmission of static data elements is performed once or more, the first device can omit the transmission of segmented security messages for static data elements.

[0274] Figure 26 This is a diagram used to explain the method of forwarding security messages received from a first device over a network.

[0275] Reference Figure 26 The network can receive security messages from the first device (S261). As described above, the security message can be a single, complete security message. The security message can be an MQTT-based message. Furthermore, the security message can include BSM, PSM, or CAM for V2X services. The network can be an MQTT-based broker.

[0276] Next, the network can send forwarding messages (S263) to multiple UEs for forwarding security messages of the first device. Here, the multiple UEs can be clients that have subscribed to a predetermined MQTT-based topic, and the network can send forwarding messages to multiple UEs that have subscribed to topics related to security messages (e.g., topics related to geographic areas related to the geographic location of the first device).

[0277] Subsequently, the network can receive a response message (S265) from at least one of the multiple UEs, including delay time information related to the security message. The delay time information may be information about the interval between the time the security message is generated and the time at least one UE receives or forwards the security message. As described above, the at least one UE can calculate the delay time information corresponding to the difference between the time the security message included in the forwarded message is generated and the time the forwarded message is decoded, and can send a response message including the calculated delay time information to the network.

[0278] Subsequently, the network can determine whether to perform segmented transmission of the forwarding message for forwarding the security message by changing the size of the message queue based on the delay time information (S267). When the delay time information includes a delay time equal to or greater than a predetermined first threshold time, the network can change the size of the message queue based on the characteristics of the data elements of the security message. The network can send the forwarding message by segmenting the forwarding message into a first segment forwarding message and a second segment forwarding message based on the message queue. On the other hand, when the delay time information includes a delay time less than the threshold time, or when no delay time information is received, the network can send or forward the entire security message by forwarding the message.

[0279] Specifically, when the delay time information includes a delay time equal to or greater than a predetermined first threshold time, the network can change the message queue size based on the size of the mandatory and optional data elements included in the security message. The network can change the message queue size to correspond to or be the same as the size of the mandatory data elements. When the queuing of mandatory data elements in the message queue is complete, the network can send a first segmented forwarding message containing only the mandatory data elements queued in the message queue. Here, the first segmented forwarding message may additionally include indication information for notifying the segmented transmission of the forwarding message, as described above. When the transmission of the first segmented forwarding message is complete, the network can change the message queue size to correspond to or be the same as the size of the optional data elements. When the queuing of optional data elements in the message queue is complete, the network can send a second segmented forwarding message containing only the optional data elements queued in the message queue.

[0280] Alternatively, based on the traffic of the session established with the first device or based on the number of UEs connected to the network, the network may send the first segment forwarding message in the first segment forwarding message and the second segment forwarding message for the forwarding message.

[0281] Alternatively, when the delay time information includes a delay time equal to or greater than a predetermined first threshold time, the network can instruct the first device to send the security message in segments based on the characteristics of the data elements of the security message. In this case, the network can receive a first segmented security message including mandatory data elements from the first device. The network can then send a first segmented forwarding message to multiple UEs for forwarding the received first segmented security message. Subsequently, the network can receive a second segmented security message including optional data elements from the first device. The network can then send a second segmented forwarding message to multiple UEs for forwarding the second segmented security message.

[0282] As described above, according to the proposed disclosure, when a security message is received with a delay, segmenting the security message transmission by changing the size of the message queue can effectively ensure the validity of the security message. Alternatively, according to the proposed disclosure, by changing the size of the message queue based on the characteristics of the security message and performing segmented transmission based on the message queue, mandatory fields or mandatory data elements can be preferentially selected and transmitted. Alternatively, according to the proposed disclosure, by segmenting the security message based on its characteristics and prioritizing the encoding and transmission of mandatory data elements, the reception waiting time at the receiving device can be effectively reduced. Alternatively, according to the proposed disclosure, while maintaining the transmission or generation period of mandatory data elements of the security message, the transmission or generation period of optional fields or data elements can be adjusted by segmenting the security message based on its characteristics.

[0283] Example of a communication system using this disclosure

[0284] Although not limited thereto, the various descriptions, functions, processes, proposals, methods and / or operation flowcharts disclosed in this document can be applied to various fields requiring wireless communication / connectivity (5G) between devices.

[0285] In the following description, it will be illustrated in more detail with reference to the accompanying drawings. In the following drawings / description, unless otherwise specified, the same reference numerals may refer to the same or corresponding hardware blocks, software blocks, or functional blocks.

[0286] Figure 27 An example of a communication system applied to this disclosure is shown.

[0287] Reference Figure 27The communication system 1 applied to this disclosure includes wireless devices, base stations (BS), and networks. Herein, a wireless device refers to a device that performs communication using a radio access technology (RAT) (e.g., 5G New RAT (NR) or Long Term Evolution (LTE)) and may be referred to as a communication / radio / 5G device. Wireless devices may include (but are not limited to) robots 100a, vehicles 100b-1 and 100b-2, extended reality (XR) devices 100c, handheld devices 100d, home appliances 100e, Internet of Things (IoT) devices 100f, and artificial intelligence (AI) devices / servers 400. For example, a vehicle may include a vehicle with wireless communication capabilities, an autonomous vehicle, and a vehicle capable of performing communication between vehicles. Herein, a vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). XR devices can include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices, and can be implemented in the form of head-mounted displays (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Handheld devices can include smartphones, smart tablets, wearable devices (e.g., smartwatches or smart glasses) and computers (e.g., laptops). Home appliances can include TVs, refrigerators, and washing machines. IoT devices can include sensors and smart meters. For example, the BS and network can be implemented as wireless devices, and a particular wireless device 200a can operate as a BS / network node relative to other wireless devices.

[0288] Wireless devices 100a to 100f can connect to network 300 via BS 200. AI technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can connect to AI server 400 via network 300. Network 300 can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although wireless devices 100a to 100f can communicate with each other via BS 200 / network 300, wireless devices 100a to 100f can also perform direct communication (e.g., sidelink communication) without going through the BS / network. For example, vehicles 100b-1 and 100b-2 can perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). IoT devices (e.g., sensors) can perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0289] Wireless communication / connections 150a, 150b, or 150c can be established between wireless devices 100a to 100f / BS 200 or between BS 200 and BS 200. In this document, wireless communication / connections can be established via various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication), or inter-BS communication (e.g., relay, integrated access backhaul (IAB)). Wireless devices and BS / wireless devices can transmit / receive radio signals to / from each other via wireless communication / connections 150a and 150b. For example, wireless communication / connections 150a and 150b can transmit / receive signals via various physical channels. For this purpose, at least a portion of the configuration information for configuring the process of transmitting / receiving radio signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes can be performed based on various proposals of this disclosure.

[0290] Examples of wireless devices using this disclosure

[0291] Figure 28 Wireless devices applicable to this disclosure are illustrated.

[0292] Reference Figure 28 The first wireless device 100 and the second wireless device 200 can transmit radio signals via various RATs (e.g., LTE and NR). In this document, {first wireless device 100 and second wireless device 200} can correspond to... Figure 27 {Wireless Device 100x and BS 200} and / or {Wireless Device 100x and Wireless Device 100x}.

[0293] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and additionally include one or more transceivers 106 and / or one or more antennas 108. The processors 102 may control the memories 104 and / or the transceivers 106, and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor 102 may process information in the memory 104 to generate a first information / signal, and then transmit a radio signal including the first information / signal via the transceivers 106. The processor 102 may receive a radio signal including a second information / signal via the transceivers 106, and then store the information obtained by processing the second information / signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various information relating to the operation of the processor 102. For example, the memory 104 may store software code including commands for performing some or all of the processes controlled by the processor 102 or for performing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. In this document, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 106 may be connected to processor 102 and transmit and / or receive radio signals via one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. Transceiver 106 may be used interchangeably with radio frequency (RF) units. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0294] The first wireless device 100 or the first device may include a processor 102, a memory 104, and a transceiver 106. The memory 104 may include components capable of executing and referencing... Figures 16 to 26 At least one program related to the operations described in the implementation method.

[0295] Specifically, the processor 102 can control the transceiver 106 to periodically send security messages queued in a message queue to multiple UEs via the network, receive response messages including delay time information for the messages from at least one of the multiple UEs via the network, and determine whether to perform segmented transmission of security messages by changing the size of the message queue based on the characteristics of the data elements of the security messages.

[0296] Alternatively, a processing device may be configured to control the transmission of a first means including object information. In this case, the processing device may include: at least one processor; and at least one memory connected to the at least one processor and storing instructions that, when executed by the at least one processor, cause the first means to periodically transmit security messages queued in a message queue to a plurality of UEs via a network, receive a response message including delay time information for the message from at least one of the plurality of UEs via the network, and determine whether to perform segmented transmission of the security message by changing the size of the message queue based on the characteristics of the data elements of the security message.

[0297] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and additionally include one or more transceivers 206 and / or one or more antennas 208. The processors 202 may control the memories 204 and / or the transceivers 206, and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processors 202 may process information in the memories 204 to generate a third information / signal, and then transmit a radio signal including the third information / signal via the transceivers 206. The processors 202 may receive a radio signal including a fourth information / signal via the transceivers 206, and then store the information obtained by processing the fourth information / signal in the memories 204. The memories 204 may be connected to the processors 202 and may store various information relating to the operation of the processors 202. For example, the memories 204 may store software code including commands for performing some or all of the processes controlled by the processors 202 or for performing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. In this document, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 206 may be connected to processor 202 and transmit and / or receive radio signals via one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. Transceiver 206 may be used interchangeably with an RF unit. In this disclosure, a wireless device may represent a communication modem / circuit / chip.

[0298] The second wireless device 200 or the second device may include a processor 202, a memory 204, and a transceiver 206. The memory 204 may include components capable of executing and referencing... Figures 16 to 26 At least one program related to the operations described in the implementation method.

[0299] Specifically, the processor 202 can control the transceiver 206 to receive security messages from the first device, send forwarding messages for forwarding security messages to multiple UEs, receive a response message including delay time information for the security messages from at least one of the multiple UEs, and determine whether to perform segmented transmission of the forwarding messages by changing the size of the message queue for the forwarding messages based on the delay time information and by changing the characteristics of the data elements of the forwarded security messages.

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

[0301] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an 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 and 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document may be included in one or more processors 102 and 202 or stored in one or more memories 104 and 204 to be driven by one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document can be implemented using firmware or software in the form of code, commands, and / or command sets.

[0302] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories 104 and 204 may be configured with read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard disk drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104 and 204 may be located internally and / or externally to one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0303] One or more transceivers 106 and 206 may transmit user data, control information, and / or radio signals / channels mentioned in the methods and / or operation flowcharts of this document to one or more other devices. One or more transceivers 106 and 206 may receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and transmit and receive radio signals. For example, one or more processors 102 and 202 may perform control to enable one or more transceivers 106 and 206 to transmit user data, control information, or radio signals to one or more other devices. One or more processors 102 and 202 may perform control to enable one or more transceivers 106 and 206 to receive user data, control information, or radio signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document through one or more antennas 108 and 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 and 206 may convert received radio signals / channels, etc., from RF band signals to baseband signals so that the received user data, control information, radio signals / channels, etc., may be processed using one or more processors 102 and 202. One or more transceivers 106 and 206 may convert user data, control information, radio signals / channels, etc., processed using one or more processors 102 and 202 from baseband signals to RF band signals. For this purpose, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0304] Examples of wireless devices using this disclosure

[0305] Figure 29 Another example of a wireless device applied to this disclosure is shown. The wireless device can be implemented in various forms depending on the use case / service (see reference). Figure 27 ).

[0306] Reference Figure 29 Wireless devices 100 and 200 can correspond to Figure 28The wireless devices 100 and 200 can be configured from various elements, components, units / parts, and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and an additional component 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include... Figure 28 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, transceiver 114 may include Figure 28 The device comprises one or more transceivers 106 and 206 and / or one or more antennas 108 and 208. Control unit 120 is electrically connected to communication unit 110, memory 130, and add-on components 140, and controls the overall operation of the wireless device. For example, control unit 120 may control the electrical / mechanical operation of the wireless device based on programs / code / commands / information stored in memory unit 130. Control unit 120 may transmit information stored in memory unit 130 to an external source (e.g., other communication devices) via communication unit 110 through a wireless / wired interface, or store information received from an external source (e.g., other communication devices) via communication unit 110 in memory unit 130 via a wireless / wired interface.

[0307] The additional component 140 can be configured differently depending on the type of wireless device. For example, the additional component 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device can be configured according to (but is not limited to) a robot ( Figure 27 100a), vehicles ( Figure 27 100b-1 and 100b-2), XR device ( Figure 27 100c), handheld device ( Figure 27 100d), home appliances ( Figure 27 100e), IoT devices ( Figure 27 100f), digital broadcasting terminals, holographic devices, public safety devices, MTC devices, medical devices, fintech devices (or financial devices), security devices, climate / environment devices, AI servers / devices ( Figure 27 400), BS ( Figure 27 This can be achieved through 200 network nodes, etc. Wireless devices can be used in mobile or fixed locations depending on the use case / service.

[0308] exist Figure 29In wireless devices 100 and 200, all elements, components, units / parts, and / or modules may be interconnected via wired interfaces, or at least a portion thereof may be wirelessly connected via communication unit 110. For example, in each of wireless devices 100 and 200, control unit 120 and communication unit 110 may be wired connected, and control unit 120 and first units (e.g., 130 and 140) may be wirelessly connected via communication unit 110. The various elements, components, units / parts, and / or modules within wireless devices 100 and 200 may also include one or more elements. For example, control unit 120 may be configured as a collection of one or more processors. As an example, control unit 120 may be configured as a collection of communication control processors, application processors, electronic control units (ECUs), graphics processing units, and memory control processors. In another example, memory 130 may be configured as random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), flash memory, volatile memory, non-volatile memory, and / or combinations thereof.

[0309] Examples of vehicles or autonomous vehicles using this disclosure

[0310] Figure 30 The illustration shows a vehicle or autonomous vehicle applicable to this disclosure. The vehicle or autonomous vehicle may be a mobile robot, car, train, manned / unmanned aerial vehicle (AV), vessel, etc.

[0311] Reference Figure 30 The vehicle or autonomous vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a drive 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 respectively correspond to... Figure 27 Blocks 110 / 130 / 140.

[0312] Communication unit 110 can send and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and roadside units), and servers. Control unit 120 can perform various operations by controlling the components of the vehicle or autonomous vehicle 100. Control unit 120 may include electronic control unit (ECU). Additionally, drive unit 140a enables the vehicle or autonomous vehicle 100 to move on a road. Drive unit 140a may include an engine, motor, powertrain, wheels, brakes, steering mechanism, etc. Power supply unit 140b supplies power to the vehicle or autonomous vehicle 100 and includes wired / wireless charging circuitry, battery, etc. Sensor unit 140c can acquire vehicle status, surrounding environment information, user information, etc. Sensor unit 140c may include inertial measurement unit (IMU) sensors, collision sensors, wheel sensors, speed sensors, slope sensors, weight sensors, heading sensors, position modules, vehicle forward / reverse sensors, battery sensors, fuel sensors, tire sensors, steering sensors, temperature sensors, depth sensors, ultrasonic sensors, lighting sensors, pedal position sensors, etc. Autonomous driving unit 140d can implement technologies for maintaining the vehicle within its lane, technologies for automatically adjusting speed (e.g., adaptive cruise control), technologies for autonomously driving along a determined path, and technologies for automatically setting a route if a destination is set, etc.

[0313] For example, communication unit 110 can receive map data, traffic information data, etc., from an external server. Autonomous driving unit 140d can generate an autonomous driving path and driving plan from the acquired data. Control unit 120 can control drive unit 140a, enabling the vehicle or autonomous vehicle 100 to move along the autonomous driving path according to the driving plan (e.g., speed / direction control). During autonomous driving, communication unit 110 can periodically or non-periodically acquire recent traffic information data from an external server and acquire surrounding traffic information data from neighboring vehicles. During autonomous driving, sensor unit 140c can acquire vehicle status and / or surrounding environment information. Autonomous driving unit 140d can update the autonomous driving path and driving plan based on newly acquired data / information. Communication unit 110 can transmit information about vehicle location, autonomous driving path, and / or driving plan to an external server. The external server can predict traffic information data using AI technology, etc., based on information collected from the vehicle or autonomous vehicle, and provide the predicted traffic information data to the vehicle or autonomous vehicle.

[0314] Here, the wireless communication technologies implemented in the wireless devices (XXX, YYY) of this specification may include, in addition to narrowband IoT for low-power communication, LTE, NR, and 6G. For example, NB-IoT technology may be an example of low-power wide-area network (LPWAN) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the aforementioned names. Alternatively, the wireless communication technologies implemented in the wireless devices (XXX, YYY) of this specification may perform communication based on LTE-M technology. In this case, as an 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 according to 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 aforementioned names. Alternatively, considering low-power communication, the wireless communication technology implemented in the wireless devices (XXX, YYY) of this specification is at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN), and is not limited to the aforementioned names. As an example, ZigBee technology can be used to generate personal area networks (PANs) related to low / low power digital communication based on various standards such as IEEE 802.15.4, and can be referred to by various names.

[0315] The above embodiments are implementations in which the components and features of this disclosure are combined in a predetermined form. Unless otherwise expressly stated, each component or feature should be considered optional. Each component or feature may be implemented without being combined with other components or features. Additionally, embodiments of this disclosure may be constructed by combining some components and / or features. The order of operations described in the embodiments of this disclosure may be changed. Some configurations or features of one embodiment may be included in other embodiments, or may be replaced by corresponding configurations or features of other embodiments. Clearly, embodiments may be constructed by combining claims that are not expressly referenced in the claims, or may be included as new claims by amendments made after filing.

[0316] In this document, embodiments of the present disclosure are primarily described based on the signal transmission / reception relationship between the terminal and the base station. Such transmission / reception relationships are extended in the same / similar manner to signal transmission / reception between the terminal and a repeater or between the base station and a repeater. In some cases, specific operations described in this document as being performed by the base station can be performed by its upstream nodes. That is, obviously, various operations performed by the base station or by network nodes other than the base station for communicating with the terminal in a network including multiple network nodes containing the base station can be performed. The base station can be replaced by terms such as fixed station, node B, eNode B (eNB), access point, etc. Additionally, the terminal can be replaced by terms such as user equipment (UE), mobile station (MS), and mobile subscriber station (MSS).

[0317] In the hardware configuration, the embodiments of this disclosure can be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.

[0318] In firmware or software configuration, the methods according to embodiments of this disclosure can be implemented in the form of modules, processes, functions, etc. Software code can be stored in a storage unit and executed by a processor. The memory is located inside or outside the processor and can send data to and receive data from the processor via various known means.

[0319] As previously described, a detailed description of preferred embodiments of the present disclosure has been provided to enable those skilled in the art to implement and perform the disclosure. While reference has been made to preferred embodiments of the present disclosure above, those skilled in the art will understand that various modifications and variations can be made to the present disclosure within its scope. For example, those skilled in the art can use the components described in the above embodiments in combination. Therefore, the above embodiments are to be interpreted in all respects as illustrative and not restrictive. The scope of the present disclosure should be determined by the appended claims and their legal equivalents, not by the foregoing description, and all changes within the meaning and scope of the appended claims are intended to be included therein.

[0320] Industrial applicability

[0321] The embodiments described above are applicable to various mobile communication systems.

Claims

1. A method for transmitting a security message by a first device in a wireless communication system, the method comprising: Security messages queued in a message queue are periodically sent to multiple user equipment (UEs) via the network. Receive a response message, including delay time information for the message, from at least one of the plurality of UEs via the network; as well as Based on the delay time information, the size of the message queue is changed by adjusting the size of the message queue according to the characteristics of the data elements of the security message to determine whether to perform segmented transmission of the security message.

2. The method according to claim 1, wherein, Based on the reception of the delay time information, including a value equal to or greater than a first threshold time, the size of the message queue is changed to a first size corresponding to the size of the mandatory data element among the mandatory and optional data elements constituting the security message, and Wherein, based on the queuing of the mandatory data elements in the message queue having the first size, the first device sends a first segmented security message as part of the security message.

3. The method according to claim 2, wherein, The first segmented security message also includes indication information for the segmented transmission of the security message.

4. The method according to claim 2, wherein, Based on the transmission of the first segmented security message, the size of the message queue is changed to a second size based on the size of the optional data element, and Wherein, based on the queuing of the optional data elements in the message queue having the second size, the first device sends a second segmented security message as part of the security message.

5. The method according to claim 2, wherein, Based on the fact that the traffic of at least one session through which the security message is sent is equal to or greater than a certain threshold, the first device only sends the first segmented security message for the security message.

6. The method according to claim 1, wherein, Based on the reception of the delay time information, which includes a value equal to or greater than a first threshold time, the first device changes the size of the message queue based on the size of the dynamic data elements constituting the security message.

7. The method according to claim 1, wherein, The security message is a message transmitted via MQTT based on message queuing telemetry.

8. The method according to claim 1, wherein, The security messages include Basic Security Message (BSM), Personal Security Message (PSM), or Collaboration Awareness Message (CAM).

9. A computer-readable recording medium having a program for performing the method according to claim 1.

10. A first means configured to transmit a security message in a wireless communication system, the first means comprising: RF transceiver; as well as The processor is connected to the RF transceiver. The processor is configured as follows: The RF transceiver is controlled to periodically send security messages queued in a message queue to multiple user equipment (UE) devices via the network; Receive a response message, including delay time information for the message, from at least one of the plurality of UEs via the network; and Whether to perform segmented transmission of the security message is determined by changing the size of the message queue based on the characteristics of the data elements of the security message.

11. A processing device in a wireless communication system, the processing device being configured to control the transmission of a first means of a security message, the processing device comprising: At least one processor; as well as At least one memory, connected to the at least one processor and storing instructions that, when executed by the at least one processor, cause the first device to: Security messages queued in a message queue are periodically sent to multiple user equipment (UEs) via the network. Receives a response message, including delay time information for the message, from at least one of the plurality of UEs via the network; and Based on the delay time information, the size of the message queue is changed by adjusting the size of the message queue according to the characteristics of the data elements of the security message to determine whether to perform segmented transmission of the security message.

12. A method for forwarding security messages over a network in a wireless communication system, the method comprising: Receive a security message from the first device; Send forwarding messages to multiple user equipment (UEs) for forwarding the security messages; Receive a response message from at least one of the plurality of UEs, including delay time information for the security message; as well as Based on the delay time information, the size of the message queue for the forwarded message is changed according to the characteristics of the data elements of the forwarded security message to determine whether to perform segmented transmission of the forwarded message.

13. A computer-readable recording medium having a program for performing the method according to claim 12.

14. A network configured to forward security messages in a wireless communication system, the network comprising: RF transceiver; as well as The processor is connected to the RF transceiver. The processor is configured as follows: Control the RF transceiver to receive security messages from the first device; Send forwarding messages to multiple user equipment (UEs) for forwarding the security messages; Receive a response message including delay time information for the security message from at least one of the plurality of UEs; and Based on the delay time information, the size of the message queue for the forwarded message is changed according to the characteristics of the data elements of the forwarded security message to determine whether to perform segmented transmission of the forwarded message.

15. A processing device in a wireless communication system, the processing device being configured to control a network forwarding secure messages, the processing device comprising: At least one processor; as well as At least one memory, connected to the at least one processor and storing instructions that, when executed by the at least one processor, cause the network to: Receive a security message from the first device; Send forwarding messages to multiple user equipment (UEs) for forwarding the security messages; Receive a response message including delay time information for the security message from at least one of the plurality of UEs; and Based on the delay time information, the size of the message queue for the forwarded message is changed according to the characteristics of the data elements of the forwarded security message to determine whether to perform segmented transmission of the forwarded message.

Images