Method for generating session identifier for positioning in wireless communication system and apparatus therefor

Abstract

The present disclosure relates to a method performed by a user equipment (UE) in a wireless communication system. Specifically, the method comprises the steps of: establishing a session with a peer UE; randomly obtaining a session number; generating a session identifier including an identifier of the UE and the obtained session number on the basis that the obtained session number does not match at least one pending session number; and transmitting a message including the session identifier to the peer UE on the established session.

Description

Method for generating a session identifier for positioning in a wireless communication system and device therefor

[0001] This specification relates to a wireless communication system. More specifically, it relates to a method for generating a session identifier for positioning in a wireless communication system and a device therefor.

[0002] Wireless communication systems are widely deployed to provide various types of communication services, such as voice and data. Typically, wireless communication systems are multiple access systems that support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power). 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), and single-carrier frequency division multiple access (SC-FDMA).

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

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

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

[0006] Based on the above discussion, the following proposes a method for generating a session identifier for positioning in a wireless communication system and a device therefor.

[0007] The technical tasks that this specification aims to achieve are not limited to the technical tasks mentioned above, and other technical tasks that are not mentioned will be clearly understood by those skilled in the art related to this specification from the detailed description below.

[0008] In one aspect of the present disclosure, a method performed by a User Equipment (UE) in a wireless communication system is provided. The method comprises: establishing a session with a peer UE; randomly obtaining a session number; generating a session identifier including an identifier of the UE and the obtained session number based on whether the obtained session number does not match at least one pending session number; and transmitting a message including the session identifier to the peer UE over the established session.

[0009] In one aspect of the present disclosure, a User Equipment (UE) is provided in a wireless communication system. The UE includes: at least one transceiver; at least one processor; and at least one computer memory operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations for the UE. The operations include: establishing a session with a peer UE; randomly obtaining a session number; generating a session identifier including an identifier of the UE and the obtained session number based on whether the obtained session number does not match at least one pending session number; and transmitting a message including the session identifier to the peer UE over the established session.

[0010] In one aspect of the present disclosure, a processing device is provided in a wireless communication system. The processing device includes: at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations for a user equipment (UE). The operations include: establishing a session with a peer UE; randomly obtaining a session number; generating a session identifier including an identifier of the UE and the obtained session number based on whether the obtained session number does not match at least one pending session number; and transmitting a message including the session identifier to the peer UE over the established session.

[0011] In one aspect of the present disclosure, a computer-readable storage medium is provided. The computer-readable storage medium stores at least one computer program comprising instructions that, when executed by at least one processor, cause the at least one processor to perform operations for a User Equipment (UE). The operations include: establishing a session with a peer UE; randomly obtaining a session number; generating a session identifier comprising an identifier of the UE and the obtained session number based on whether the obtained session number does not match at least one pending session number; and transmitting a message comprising the session identifier to the peer UE over the established session.

[0012] Preferably, at least one of the pending session numbers may be associated with at least one session that was established prior to the establishment of the session and has not been terminated.

[0013] Preferably, the session identifier may be included in the header of the message.

[0014] Meanwhile, in another aspect of the present specification, a method performed by a UE (User Equipment) in a wireless communication system is provided. The method is characterized by comprising: randomly obtaining a session identifier; transmitting a session establishment request message including the obtained session identifier to a peer UE based on whether the obtained session identifier does not match at least one pending session identifier; and transmitting at least one message to the peer UE based on receiving a session establishment acceptance message from the peer UE.

[0015] In another aspect of the present disclosure, a User Equipment (UE) is provided in a wireless communication system. The UE includes: at least one transceiver; at least one processor; and at least one computer memory operably connectable to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations for the UE. The operations include: randomly obtaining a session identifier; transmitting a session establishment request message including the obtained session identifier to a peer UE based on whether the obtained session identifier does not match at least one pending session identifier; and transmitting at least one message to the peer UE based on receiving a session establishment acceptance message from the peer UE.

[0016] Preferably, the message and / or the at least one message may be a positioning message for positioning the UE or a UE-based sensing message.

[0017] The above problem solving methods are only some of the examples of this specification, and various examples reflecting the technical features of this specification can be derived and understood by a person having ordinary knowledge in the relevant technical field based on the detailed description below.

[0018] According to the present disclosure, wireless signal transmission and reception can be efficiently performed in a wireless communication system.

[0019] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

[0020] To aid in understanding implementations of this specification, the accompanying drawings, which are included as part of the detailed description, provide examples of implementations of this specification and, together with the detailed description, illustrate implementations of this specification:

[0021] Figure 1 shows the structure of the NR system.

[0022] Figure 2 shows the functional division between NG-RAN and 5GC.

[0023] Figure 3 shows the radio protocol architecture of the NR system.

[0024] Figure 4 illustrates the structure of a radio frame of an NR system.

[0025] Figure 5 illustrates a resource grid of slots in an NR system.

[0026] Figure 6 illustrates a communication system (1) to which the present disclosure is applicable.

[0027] Figures 7 and 8 illustrate a wireless device according to an embodiment of the present disclosure.

[0028] FIG. 9 illustrates a vehicle or autonomous vehicle according to one embodiment of the present disclosure.

[0029] Figure 10 shows a radio protocol architecture for SL communication.

[0030] Figure 11 shows a synchronization source or synchronization reference of V2X.

[0031] Figure 12 shows a procedure for a terminal to perform V2X or SL communication depending on the transmission mode.

[0032] FIG. 13 illustrates three cast types according to one embodiment of the present disclosure.

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

[0034] Figure 15 illustrates an example of an architecture in a 5G system capable of positioning a UE connected to a Next Generation-Radio Access Network (NG-RAN) or E-UTRAN.

[0035] Figure 16 shows an example implementation of a network for measuring the location of a UE.

[0036] Figure 17 shows an example of a protocol layer used to support LPP (LTE Positioning Protocol) message transmission between an LMF and a UE.

[0037] Figure 18 shows an example of the protocol layers used to support NR Positioning Protocol A (NRPPa) PDU transmission between LMF and NG-RAN nodes.

[0038] FIG. 19 is a diagram for explaining an OTDOA (Observed Time Difference Of Arrival) positioning method according to one embodiment of the present disclosure.

[0039] FIG. 20 is a flowchart illustrating an example of transmitting a message using a session identifier generated according to the present disclosure.

[0040] FIG. 21 is a flowchart illustrating another example of transmitting a message using a session identifier generated according to the present disclosure.

[0041] The following technologies can be used in various wireless access systems, such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with radio technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented with radio technologies such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented with radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (Evolved UTRA). UTRA is a part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (long term evolution) is part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A.

[0042] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communications compared to existing Radio Access Technology (RAT) is emerging. Furthermore, massive Machine Type Communications (MTC), which connects multiple devices and objects to provide diverse services anytime, anywhere, is also a key issue to be considered in next-generation communications. Furthermore, communication system design that considers reliability and latency-sensitive services / terminals is being discussed. Accordingly, the introduction of next-generation RATs that consider enhanced Mobile BroadBand Communication (eMBB), massive MTC, and Ultra-Reliable and Low Latency Communication (URLLC) is being discussed. For convenience, this disclosure will refer to these technologies as NR (New Radio or New RAT).

[0043] For clarity of explanation, the description will focus on 3GPP NR, but the technical idea of ​​the present disclosure is not limited thereto.

[0044] In this specification, the expression "setting" can be replaced with the expression "configure / configuration", and the two can be used interchangeably. In addition, conditional expressions (e.g., "if", "in a case", or "when", etc.) can be replaced with the expressions "based on that ~~" or "in a state / status". In addition, the operation of the terminal / base station or the SW / HW configuration according to the satisfaction of the condition can be inferred / understood. In addition, if the process of the receiving (or transmitting) side can be inferred / understood from the process of the transmitting (or receiving) side in signal transmission / reception between wireless communication devices (e.g., base stations, terminals), the description thereof can be omitted. For example, signal determination / generation / encoding / transmission, etc. of the transmitting side can be understood as signal monitoring reception / decoding / determination, etc. of the receiving side. In addition, the expression that the terminal performs (or does not perform) a specific operation can also be interpreted as meaning that the base station operates while expecting / assuming (or expecting / assuming that the terminal does not perform) the specific operation. In addition, the expression that the base station performs (or does not perform) a specific operation can also be interpreted as meaning that the terminal operates while expecting / assuming (or expecting / assuming that the base station does not perform) the specific operation. In addition, the division and index of each section, embodiment, example, option, method, plan, etc. in the following description are for the convenience of explanation and should not be interpreted as meaning that each constitutes an independent disclosure or that each must be implemented only individually. In addition, in describing each section, embodiment, example, option, method, plan, etc., if there is no explicitly conflicting / opposing description, it can be inferred / interpreted that at least some of them can be combined and implemented together, or at least some can be implemented with the omission of each.

[0045] Figure 1 shows the structure of the NR system.

[0046] Referring to FIG. 1, a Next Generation - Radio Access Network (NG-RAN) may include a base station (20) that provides user plane and control plane protocol termination to a terminal (10). For example, the base station (20) may include a next generation Node B (gNB) and / or an evolved Node B (eNB). For example, the terminal (10) may be fixed or mobile, and may be referred to by other terms such as a Mobile Station (MS), a User Terminal (UT), a Subscriber Station (SS), a Mobile Terminal (MT), or a Wireless Device. For example, the base station may be a fixed station that communicates with the terminal (10), and may be referred to by other terms such as a Base Transceiver System (BTS), or an Access Point.

[0047] The example of Fig. 1 illustrates a case that includes only gNB. The base stations (20) can be connected to each other via Xn interfaces. The base stations (20) can be connected to a 5th generation core network (5G Core Network: 5GC) via an NG interface. More specifically, the base station (20) can be connected to an access and mobility management function (AMF) (30) via an NG-C interface, and can be connected to a user plane function (UPF) (30) via an NG-U interface.

[0048] Figure 2 shows the functional division between NG-RAN and 5GC.

[0049] Referring to FIG. 2, the gNB can provide functions such as inter-cell radio resource management (Inter Cell RRM), radio bearer management (RB control), connection mobility control (Connection Mobility Control), radio admission control (Radio Admission Control), measurement configuration and provision, and dynamic resource allocation. The AMF can provide functions such as Non Access Stratum (NAS) security and idle state mobility processing. The UPF can provide functions such as mobility anchoring and protocol data unit (PDU) processing. The session management function (SMF) can provide functions such as terminal Internet Protocol (IP) address allocation and PDU session control.

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

[0051] Figure 3 illustrates the radio protocol architecture of the NR system. Specifically, Figure 3 (a) illustrates the radio protocol architecture for the user plane, and Figure 3 (b) illustrates the radio protocol architecture for the control plane. The user plane is a protocol stack for transmitting user data, and the control plane is a protocol stack for transmitting control signals.

[0052] Referring to Figure 3, the physical layer provides information transmission services to higher layers using physical channels. The physical layer is connected to the upper layer, the Medium Access Control (MAC) layer, via a transport channel. Data travels between the MAC layer and the physical layer via the transport channel. Transport channels are classified based on how and with what characteristics data is transmitted over the wireless interface.

[0053] Data travels between different physical layers, i.e., between the physical layers of a transmitter and a receiver, via a physical channel. This physical channel can be modulated using Orthogonal Frequency Division Multiplexing (OFDM) and utilizes time and frequency as radio resources.

[0054] The MAC layer provides services to the upper layer, the radio link control (RLC) layer, through logical channels. The MAC layer provides mapping from multiple logical channels to multiple transport channels. Furthermore, the MAC layer provides logical channel multiplexing, which maps multiple logical channels to a single transport channel. The MAC sublayer provides data transmission services on logical channels.

[0055] The RLC layer performs the concatenation, segmentation, and reassembly of RLC Service Data Units (SDUs). To guarantee the various Quality of Service (QoS) required by radio bearers (RBs), the RLC layer provides three operating modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). AM RLC provides error correction through automatic repeat request (ARQ).

[0056] The RRC (Radio Resource Control) layer is defined only in the control plane. The RRC layer is responsible for controlling logical channels, transport channels, and physical channels, related to the configuration, reconfiguration, and release of radio bearers. RBs represent the logical paths provided by Layer 1 (physical layer or PHY layer) and Layer 2 (MAC layer, RLC layer, and PDCP (Packet Data Convergence Protocol) layer) for data transmission between the terminal and the network.

[0057] The functions of the PDCP layer in the user plane include the transmission of user data, header compression, and ciphering. The functions of the PDCP layer in the control plane include the transmission of control plane data and encryption / integrity protection.

[0058] The Service Data Adaptation Protocol (SDAP) layer is defined only in the user plane. It performs mapping between QoS flows and data radio bearers, marking QoS flow identifiers (IDs) within downlink and uplink packets, and more.

[0059] Establishing a Radio Bearer (RB) refers to the process of defining the characteristics of the radio protocol layer and channel to provide a specific service, and setting specific parameters and operating methods for each. RBs can be further divided into two types: the Signaling Radio Bearer (SRB) and the Data Radio Bearer (DRB). The SRB is used as a channel to transmit RRC messages in the control plane, while the DRB is used as a channel to transmit user data in the user plane.

[0060] When an RRC connection is established between the RRC layer of the terminal and the RRC layer of the base station, the terminal is in the RRC_CONNECTED state. Otherwise, it is in the RRC_IDLE state. For NR, the RRC_INACTIVE state is additionally defined, and a terminal in the RRC_INACTIVE state can maintain a connection with the core network while releasing the connection with the base station.

[0061] Downlink transmission channels that transmit data from the network to the terminal include the Broadcast Channel (BCH), which transmits system information, and the downlink Shared Channel (SCH), which transmits user traffic or control messages. Traffic or control messages for downlink multicast or broadcast services may be transmitted through the downlink SCH or a separate downlink Multicast Channel (MCH). Meanwhile, uplink transmission channels that transmit data from the terminal to the network include the Random Access Channel (RACH), which transmits initial control messages, and the uplink Shared Channel (SCH), which transmits user traffic or control messages.

[0062] Logical channels that are located above the transport channel and are mapped to the transport channel include the Broadcast Control Channel (BCCH), Paging Control Channel (PCCH), Common Control Channel (CCCH), Multicast Control Channel (MCCH), and Multicast Traffic Channel (MTCH).

[0063] A physical channel consists of multiple OFDM symbols in the time domain and multiple subcarriers in the frequency domain. A single subframe consists of multiple OFDM symbols in the time domain. A resource block is a resource allocation unit and consists of multiple OFDM symbols and multiple subcarriers. Additionally, each subframe can use specific subcarriers of specific OFDM symbols (e.g., the first OFDM symbol) of the subframe for the Physical Downlink Control Channel (PDCCH), i.e., the L1 / L2 control channel. A Transmission Time Interval (TTI) is a unit time for subframe transmission.

[0064] Figure 4 illustrates the structure of a radio frame of an NR system.

[0065] Referring to Figure 4, uplink and downlink transmissions in NR are structured as frames. Each radio frame has a length of 10 ms and is divided into two 5 ms half-frames (Half-Frames, HF). Each half-frame is divided into five 1 ms sub-frames (Subframes, SF). A sub-frame is divided into one or more slots, and the number of slots within a sub-frame depends on the Subcarrier Spacing (SCS). Each slot contains 12 or 14 Orthogonal Frequency Division Multiplexing (OFDM) symbols, depending on the cyclic prefix (CP). When a normal CP is used, each slot contains 14 OFDM symbols. When an extended CP is used, each slot contains 12 OFDM symbols.

[0066] Table 1 shows the number of OFDM symbols per slot according to SCS for regular CP (N slotsymb ), number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe,u slot ) is shown.

[0067] uN slot symb N frame,u slot N subframe,u slot 01410111420221440431480841416016

[0068] Table 2 shows the number of OFDM symbols per slot according to SCS when extended CP is used (N slot symb ), number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe,u slot ) is shown.

[0069] uN slot symb N frame,u slot N subframe,u slot 212404

[0070] The structure of the frame is only an example, and the number of subframes, number of slots, and number of symbols in the frame can be varied.

[0071] In an NR system, OFDM numerology (e.g., SCS) may be set differently between multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., SF, slot, or TTI) (conveniently referred to as TU (Time Unit)) consisting of the same number of symbols may be set differently between the merged cells. Here, the symbol may include an OFDM symbol (or CP-OFDM symbol), an SC-FDMA symbol (or Discrete Fourier Transform-spread-OFDM, DFT-s-OFDM symbol).

[0072] Figure 5 illustrates a resource grid of slots in an NR system.

[0073] Referring to Fig. 5, a slot includes multiple symbols in the time domain. For example, in the case of a regular CP, one slot includes 14 symbols, but in the case of an extended CP, one slot includes 12 symbols. A carrier includes multiple subcarriers in the frequency domain. An RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth Part) is defined as multiple consecutive PRBs (Physical RBs) in the frequency domain and can correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication is performed through activated BWPs, and only one BWP can be activated for a single terminal. Each element in the resource grid is referred to as a Resource Element (RE), and one complex symbol can be mapped to it.

[0074] Figure 6 illustrates a communication system (1) to which the present disclosure is applicable.

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

[0076] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, etc. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). Additionally, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0077] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and base station-to-base station communication (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present disclosure.

[0078] FIG. 7 illustrates a wireless device according to an embodiment of the present disclosure. The embodiment of FIG. 7 may be combined with various embodiments of the present disclosure.

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

[0080] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). Furthermore, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present disclosure, a wireless device may also mean a communication modem / circuit / chip.

[0081] A second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). In addition, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present disclosure, a wireless device may also mean a communication modem / circuit / chip.

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

[0083] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0084] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0085] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0086] FIG. 8 illustrates a wireless device according to an embodiment of the present disclosure. The wireless device may be implemented in various forms depending on the use case / service (see FIG. 6). The embodiment of FIG. 8 may be combined with various embodiments of the present disclosure.

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

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

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

[0090]

[0091]

[0092] FIG. 9 illustrates a vehicle or autonomous vehicle according to one embodiment of the present disclosure. The vehicle or autonomous vehicle may be implemented as a mobile robot, a car, a train, a manned or unmanned aerial vehicle (AV), a ship, or the like. The embodiment of FIG. 9 may be combined with various embodiments of the present disclosure.

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

[0094] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g., base stations, road side units, etc.), and servers. The control unit (120) can control elements of the vehicle or autonomous vehicle (100) to perform various operations. The control unit (120) can include an ECU (Electronic Control Unit). The drive unit (140a) can drive the vehicle or autonomous vehicle (100) on the ground. The drive unit (140a) can include an engine, a motor, a power train, wheels, brakes, a steering device, etc. The power supply unit (140b) supplies power to the vehicle or autonomous vehicle (100) and can include a wired / wireless charging circuit, a battery, etc. The sensor unit (140c) can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit (140c) may include an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an incline sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit (140d) may implement a technology for maintaining a driving lane, a technology for automatically controlling speed such as adaptive cruise control, a technology for automatically driving along a set path, a technology for automatically setting a path and driving when a destination is set, etc.

[0095] For example, the communication unit (110) can receive map data, traffic information data, etc. from an external server. The autonomous driving unit (140d) can generate an autonomous driving route and driving plan based on the acquired data. The control unit (120) can control the drive unit (140a) so that the vehicle or autonomous vehicle (100) moves along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit (110) can irregularly / periodically acquire the latest traffic information data from an external server and can acquire surrounding traffic information data from surrounding vehicles. In addition, during autonomous driving, the sensor unit (140c) can acquire vehicle status and surrounding environment information. The autonomous driving unit (140d) can update the autonomous driving route and driving plan based on newly acquired data / information. The communication unit (110) can transmit information regarding the vehicle location, autonomous driving route, driving plan, etc. to the external server. External servers can predict traffic information data in advance using AI technology or other technologies based on information collected from vehicles or autonomous vehicles, and provide the predicted traffic information data to the vehicles or autonomous vehicles.

[0096]

[0097] Below, V2X or SL communication is explained.

[0098] FIG. 10 illustrates a radio protocol architecture for SL communication. The embodiment of FIG. 10 can be combined with various embodiments of the present disclosure. Specifically, (a) of FIG. 10 illustrates a user plane protocol stack, and (b) of FIG. 10 illustrates a control plane protocol stack.

[0099] Describes the Sidelink Synchronization Signal (SLSS) and synchronization information.

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

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

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

[0103] Below, the synchronization acquisition of the SL terminal is described.

[0104] In time division multiple access (TDMA) and frequency division multiple access (FDMA) systems, accurate time and frequency synchronization is essential. If time and frequency synchronization is not accurate, system performance may be degraded due to inter-symbol interference (ISI) and inter-carrier interference (ICI). This is also the case in V2X. In V2X, for time / frequency synchronization, the sidelink synchronization signal (SLSS) can be used in the physical layer, and the master information block-sidelink-V2X (MIB-SL-V2X) can be used in the radio link control (RLC) layer.

[0105] Figure 11 shows a synchronization source or synchronization reference of V2X.

[0106] Referring to FIG. 11, in V2X, a terminal can be directly synchronized to a global navigation satellite system (GNSS), or can be indirectly synchronized to GNSS through a terminal (within network coverage or outside network coverage) that is directly synchronized to GNSS. When GNSS is set as a synchronization source, the terminal can calculate the DFN and subframe number using Coordinated Universal Time (UTC) and a (pre-)configured DFN offset.

[0107] Alternatively, the terminal may be synchronized directly to the base station, or may be synchronized to another terminal that is time / frequency synchronized to the base station. For example, the base station may be an eNB or a gNB. For example, if the terminal is within network coverage, the terminal may receive synchronization information provided by the base station and be synchronized directly to the base station. Thereafter, the terminal may provide the synchronization information to other adjacent terminals. If the base station timing is set as the synchronization reference, the terminal may follow the cell associated with the frequency (if within cell coverage at the frequency), the primary cell, or the serving cell (if outside cell coverage at the frequency) for synchronization and downlink measurements.

[0108] A base station (e.g., a serving cell) may provide synchronization settings for a carrier used for V2X or SL communications. In this case, the terminal may follow the synchronization settings received from the base station. If the terminal does not detect any cell on the carrier used for V2X or SL communications and does not receive synchronization settings from the serving cell, the terminal may follow the preset synchronization settings.

[0109] Alternatively, the terminal may synchronize with another terminal that has not obtained synchronization information directly or indirectly from the base station or GNSS. The synchronization source and preference may be preset for the terminal. Alternatively, the synchronization source and preference may be set via a control message provided by the base station.

[0110] Whether GNSS-based or base station-based synchronization is used can be (pre-)configured. In single-carrier operation, the terminal can derive its transmission timing from the available synchronization reference with the highest priority.

[0111] For example, the terminal can (re)select a synchronization reference, and the terminal can obtain synchronization from the synchronization reference. Then, the terminal can perform SL communication (e.g., PSCCH / PSSCH transmission / reception, PSFCH (Physical Sidelink Feedback Channel) transmission / reception, S-SSB transmission / reception, reference signal transmission / reception, etc.) based on the obtained synchronization.

[0112] Figure 12 illustrates a procedure for a terminal to perform V2X or SL communication according to a transmission mode. In various embodiments of the present disclosure, the transmission mode may be referred to as a mode or resource allocation mode. Hereinafter, for convenience of explanation, the transmission mode in LTE may be referred to as the LTE transmission mode, and the transmission mode in NR may be referred to as the NR resource allocation mode.

[0113] For example, (a) of Fig. 12 represents terminal operation related to LTE transmission mode 1 or LTE transmission mode 3. Or, for example, (a) of Fig. 12 represents terminal operation related to NR resource allocation mode 1. For example, LTE transmission mode 1 can be applied to general SL communication, and LTE transmission mode 3 can be applied to V2X communication.

[0114] For example, (b) of FIG. 12 represents terminal operation related to LTE transmission mode 2 or LTE transmission mode 4. Or, for example, (b) of FIG. 12 represents terminal operation related to NR resource allocation mode 2.

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

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

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

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

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

[0120] Referring to (a) or (b) of FIG. 12, in step S8030, the first terminal may receive a PSFCH. For example, the first terminal and the second terminal may determine PSFCH resources, and the second terminal may transmit HARQ feedback to the first terminal using the PSFCH resources.

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

[0122] FIG. 13 illustrates three cast types according to an embodiment of the present disclosure. The embodiment of FIG. 13 can be combined with various embodiments of the present disclosure.

[0123] Specifically, (a) of FIG. 13 represents broadcast type SL communication, (b) of FIG. 13 represents unicast type SL communication, and (c) of FIG. 13 represents groupcast type SL communication. In the case of unicast type SL communication, a terminal can perform one-to-one communication with another terminal. In the case of groupcast type SL communication, a terminal can perform SL communication with one or more terminals within the group to which it belongs. In various embodiments of the present disclosure, SL groupcast communication can be replaced with SL multicast communication, SL one-to-many communication, etc.

[0124]

[0125] Integrated Sensing and Communication (ISAC)

[0126] Wireless sensing is a technology that uses radio frequencies to determine the instantaneous linear velocity, angle, distance (range), and other characteristics of objects within the environment, thereby obtaining information about the environment and / or the characteristics of objects within the environment. Because this radio frequency sensing capability does not require a network device to connect to the object, it can provide a device-less object location service.

[0127] The ability to obtain range, velocity, and angle information from radio frequency signals can enable a wide range of new capabilities, such as object detection, object recognition (e.g., vehicles, humans, animals, UAVs), and high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to a wide range of industries (e.g., unmanned aerial vehicles, smart homes, V2X, factories, railways, public safety, etc.), enabling applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, wireless sensing can utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of wireless sensing services, i.e., sensing operations, can rely on the transmission, reflection, and scattering of wireless sensing signals. Therefore, wireless sensing can provide an opportunity to enhance existing communication systems from a communication network to a wireless communication and sensing network.

[0128] FIG. 14 illustrates an example of a sensing operation according to an embodiment of the present disclosure. In particular, the embodiment of FIG. 14 can be combined with various embodiments of the present disclosure. Specifically, FIG. 14(a) illustrates an example of sensing using a sensing receiver and a sensing transmitter located at the same location (e.g., monostatic sensing), and FIG. 14(b) illustrates an example of sensing using a separated sensing receiver and sensing transmitter (e.g., bistatic sensing).

[0129]

[0130] Positioning

[0131] Figure 15 illustrates an example of an architecture in a 5G system that enables positioning for UEs connected to a Next Generation-Radio Access Network (NG-RAN) or E-UTRAN.

[0132] Referring to FIG. 15, the AMF may receive a request for location services related to a specific target UE from another entity, such as a Gateway Mobile Location Center (GMLC), or the AMF itself may decide to initiate location services on behalf of a specific target UE. Then, the AMF may transmit a location service request to a Location Management Function (LMF). The LMF, which has received the location service request, may process the location service request and return a processing result, including an estimated location of the UE, to the AMF. Meanwhile, if the location service request is received from another entity, such as a GMLC, other than the AMF, the AMF may forward the processing result received from the LMF to the other entity.

[0133] ng-eNB (new generation evolved-NB) and gNB are network elements of NG-RAN that can provide measurement results for position estimation. They can measure radio signals for target UEs and transmit the results to the LMF. In addition, ng-eNB can control several Transmission Points (TPs), such as remote radio heads (REHs), or PRS-only TPs that support a PRS-based beacon system for E-UTRA.

[0134] The LMF is connected to an Enhanced Serving Mobile Location Center (E-SMLC), and the E-SMLC can enable the LMF to access the E-UTRAN. For example, the E-SMLC can enable the LMF to support Observed Time Difference Of Arrival (OTDOA), one of the positioning methods of the E-UTRAN, by utilizing downlink measurements acquired by the target UE via signals transmitted from the eNB and / or PRS-dedicated TPs in the E-UTRAN.

[0135] Meanwhile, the LMF may be connected to the SUPL Location Platform (SLP). The LMF may support and manage different positioning services for target UEs. The LMF may interact with a serving ng-eNB or a serving gNB for the target UE to obtain the UE's location measurement. For positioning of the target UE, the LMF may determine a positioning method based on the Location Service (LCS) client type, the required Quality of Service (QoS), the UE positioning capabilities, the gNB positioning capabilities, and the ng-eNB positioning capabilities, and may apply this positioning method to the serving gNB and / or the serving ng-eNB. In addition, the LMF may determine a position estimate for the target UE and additional information such as the accuracy of the position estimate and velocity. The SLP is a Secure User Plane Location (SUPL) entity responsible for positioning via the user plane.

[0136] The UE can measure downlink signals from sources such as NG-RAN and E-UTRAN, different Global Navigation Satellite Systems (GNSS), Terrestrial Beacon Systems (TBS), Wireless Local Access Network (WLAN) access points, Bluetooth beacons, and UE barometric pressure sensors. The UE may include an LCS application, or may access an LCS application through communication with a network to which the UE is connected or through other applications included in the UE. The LCS application may include measurement and calculation functions necessary to determine the position of the UE. For example, the UE may include an independent positioning function, such as a Global Positioning System (GPS), and may report the UE's position independently of NG-RAN transmissions. This independently acquired positioning information may be utilized as supplementary information to the positioning information acquired from the network.

[0137] Figure 16 shows an example implementation of a network for measuring the location of a UE.

[0138] When the AMF receives a location service request while the UE is in CM-IDLE (Connection Management - IDLE) state, the AMF may establish a signaling connection with the UE and request a network trigger service to allocate a specific serving gNB or ng-eNB. This operation process is omitted in Fig. 15. That is, in Fig. 15, it can be assumed that the UE is in connected mode. However, the signaling connection may be released by the NG-RAN during the positioning process due to reasons such as signaling and data inactivity.

[0139] Referring to FIG. 16, the network operation process for specifically measuring the location of a UE will be described below. In step 1a, a 5GC entity such as a GMLC may request a location service to measure the location of a target UE from a serving AMF. However, even if the GMLC does not request a location service, the serving AMF may determine, according to step 1b, that a location service is necessary to measure the location of the target UE. For example, the serving AMF may decide to directly perform a location service to measure the location of a UE for an emergency call.

[0140] Thereafter, the AMF may transmit a location service request to the LMF according to step 2, and the LMF may initiate location procedures with the serving ng-eNB and the serving gNB according to step 3a to obtain location measurement data or location measurement assistance data. Additionally, the LMF may initiate location procedures for downlink positioning with the UE according to step 3b. For example, the LMF may transmit location assistance data (Assistance data defined in 3GPP TS 36.355) to the UE, or obtain a location estimate or a location measurement. Meanwhile, step 3b may be additionally performed after step 3a is performed, or may be performed instead of step 3a.

[0141] In step 4, the LMF may provide a location service response to the AMF. The location service response may also include information about whether the UE's location estimation was successful and an estimate of the UE's location. If the procedure of FIG. 16 was initiated by step 1a, the AMF may forward the location service response to a 5GC entity, such as the GMLC. If the procedure of FIG. 16 was initiated by step 1b, the AMF may utilize the location service response to provide location services related to emergency calls, etc.

[0142] Figure 17 shows an example of a protocol layer used to support LPP (LTE Positioning Protocol) message transmission between an LMF and a UE.

[0143] LPP PDUs can be transmitted via NAS PDUs between AMF and UE. Referring to FIG. 17, LPP can be terminated between a target device (e.g., a UE in the control plane or a SUPL Enabled Terminal (SET) in the user plane) and a location server (e.g., an LMF in the control plane or an SLP in the user plane). LPP messages can be transmitted in the form of transparent PDUs over an intermediate network interface using a suitable protocol, such as NGAP (NG Application Protocol) over the NG-C (NG-Control Plane) interface, NAS / RRC over the LTE-Uu and NR-Uu interfaces. The LPP protocol enables positioning for NR and LTE using various positioning methods.

[0144] For example, via the LPP protocol, a target device and a location server can exchange capability information, auxiliary data for positioning, and / or location information. Furthermore, LPP messages can be used to exchange error information and / or indicate the termination of an LPP procedure.

[0145] Figure 18 shows an example of the protocol layers used to support NR Positioning Protocol A (NRPPa) PDU transmission between LMF and NG-RAN nodes.

[0146] NRPPa can be used to exchange information between NG-RAN nodes and LMFs. Specifically, NRPPa can exchange Enhanced-Cell ID (E-CID) for measurements transmitted from ng-eNB to LMF, data to support OTDOA positioning methods, Cell-ID for NR Cell ID positioning methods, and Cell Location ID. Even if the AMF does not have information about the associated NRPPa transaction, it can route NRPPa PDUs based on the routing ID of the associated LMF through the NG-C interface.

[0147] The NRPPa protocol's procedures for location and data collection can be divided into two types. The first type is a UE-associated procedure for conveying information about a specific UE (e.g., position measurement information, etc.), and the second type is a non-UE-associated procedure for conveying information applicable to NG-RAN nodes and associated TPs (e.g., gNB / ng-eNB / TP timing information, etc.). These two types of procedures may be supported independently or simultaneously.

[0148]

[0149] Positioning Method

[0150] Meanwhile, positioning methods supported by NG-RAN, i.e., positioning methods, may include GNSS, OTDOA, E-CID (enhanced cell ID), barometric pressure sensor positioning, WLAN positioning, Bluetooth positioning and TBS (terrestrial beacon system), UTDOA (Uplink Time Difference of Arrival), etc. Among the above positioning methods, the position of the UE may be measured using any one of the positioning methods, but the position of the UE may also be measured using two or more positioning methods.

[0151] (1) OTDOA (Observed Time Difference Of Arrival)

[0152] FIG. 19 is a diagram for explaining an OTDOA (Observed Time Difference Of Arrival) positioning method according to one embodiment of the present disclosure.

[0153] The OTDOA positioning method utilizes the timing measurements of downlink signals received by the UE from multiple TPs, including the eNB, ng-eNB, and PRS-dedicated TPs. The UE measures the timing of the received downlink signals using location assistance data received from a location server. Based on these measurement results and the geographic coordinates of neighboring TPs, the UE's location can be determined.

[0154] A UE connected to a gNB can request a measurement gap for OTDOA measurements from a TP. If the UE does not recognize a Single Frequency Network (SFN) for at least one TP in the OTDOA assistance data, the UE may use an autonomous gap to obtain the SFN of the OTDOA reference cell before requesting a measurement gap to perform Reference Signal Time Difference (RSTD) measurements.

[0155] Here, the RSTD can be defined based on the smallest relative time difference between the boundaries of two subframes received from the reference cell and the measurement cell, respectively. That is, it can be calculated based on the relative time difference between the start time of the subframe of the reference cell that is closest to the start time of the subframe received from the measurement cell. Meanwhile, the reference cell can be selected by the UE.

[0156] Accurate OTDOA measurement requires measuring the time of arrival (TOA) of signals received from three or more geographically dispersed TPs or base stations. For example, the TOA for TP 1, TP 2, and TP 3 can be measured, and based on the three TOAs, the RSTD for TP 1-TP 2, the RSTD for TP 2-TP 3, and the RSTD for TP 3-TP 1 can be calculated. Based on these, a geometric hyperbola can be determined, and the point where these hyperbolas intersect can be used to estimate the UE's location. In this case, since each TOA measurement may have accuracy and / or uncertainty, the estimated UE's location may be known within a certain range depending on the measurement uncertainty.

[0157] (2) E-CID (Enhanced Cell ID)

[0158] In the Cell ID (CID) positioning method, the location of the UE can be measured through geographic information of the UE's serving ng-eNB, serving gNB, and / or serving cell. For example, geographic information of the serving ng-eNB, serving gNB, and / or serving cell can be obtained through paging, registration, etc.

[0159] Meanwhile, the E-CID positioning method may utilize additional UE measurements and / or NG-RAN radio resources in addition to the CID positioning method to improve the UE position estimate. In the E-CID positioning method, some of the same measurement methods as the measurement control system of the RRC protocol may be used, but generally, additional measurements are not performed solely for UE position measurement. In other words, a separate measurement configuration or measurement control message may not be provided to measure the UE's position, and the UE may not expect to be requested to perform additional measurement operations solely for position measurement, and may report measurements obtained through measurement methods generally available to the UE.

[0160] (3) UTDOA (Uplink Time Difference of Arrival)

[0161] UTDOA is a method for determining the location of a UE by estimating the arrival time of the SRS. When calculating the estimated SRS arrival time, the serving cell is used as a reference cell, and the UE's location can be estimated based on the arrival time difference with other cells (or base stations / TPs). To implement UTDOA, the E-SMLC can designate the serving cell of the target UE to instruct the target UE to transmit SRS. In addition, the E-SMLC can provide configuration settings such as whether the SRS is periodic or aperiodic, bandwidth, and frequency / group / sequence hopping.

[0162]

[0163] Side link positioning

[0164] NR positioning discussed in the existing 3GPP NR standard release 17 only supported network-based Uu positioning, and did not support positioning operations using SL (sidelink) communication. However, SL positioning is expected to be supported starting with the recent 3GPP NR standard release 18.

[0165] Conventional Uu positioning is a method of searching for a location through a connection between a target UE and a base station (gNB / LMF), but SL positioning is a new method of searching for a location through a connection between a target UE and one or more anchor UEs.

[0166] Sidelink positioning is a new method of performing positioning operations by exchanging sidelink positioning reference signals (SL-PRS) with anchor UEs surrounding the target UE through direct connections using sidelink communication technology, rather than through a base station (gNB). Therefore, sidelink positioning operations at the physical layer are performed through SL-PRS transmission and measurement between the target UE and anchor UE.

[0167]

[0168] Conventionally, Uu positioning uses the LPP protocol. An LPP session is a point-to-point communication protocol between a target UE and an LMF. Therefore, the LMF receives positioning information through the LPP protocol, and the target UE receives positioning information through the LMF. Additionally, the LMF configures a base station (gNB) and exchanges positioning-related messages via the NRPPa protocol to perform positioning operations.

[0169] Meanwhile, in sidelink positioning, positioning operations are performed by exchanging positioning protocol messages with anchor UEs surrounding the target UE, not the LMF. Therefore, sidelink positioning operations at the protocol layer are performed between UEs via the sidelink positioning protocol (SLPP).

[0170] The SLPP procedure is based on a positioning protocol session established between the target UE and the anchor UE(s). The SLPP procedure (procedure / transaction) basically includes the following five components:

[0171] - SL Positioning Capability Transfer

[0172] - SL Positioning Assistance Data exchange

[0173] - SL Location Information Transfer

[0174] - Error handling

[0175] - Abort

[0176] Additionally, 3GPP is also considering session-less positioning operation, where no message exchange between UEs is required.

[0177]

[0178] It has been discussed that anchor UE determination in SL positioning proceeds through the following process.

[0179] 1) Through the discovery search process, the target UE exchanges performance information (UE capability) with surrounding UEs capable of SL communication (hereinafter, candidate UEs) through SL communication. At this time, basic information such as whether the discovered UEs support SL positioning is exchanged, and the anchor UE's decision is limited to cases where the UE supports SL positioning.

[0180] 2) After exchanging basic information, the target UE and candidate UE negotiate to determine the final anchor UE. When negotiating for SL positioning, the anchor UE is determined only if the request to assume the role of anchor UE is not rejected during the negotiation process (negotiation success).

[0181] 3) Additionally, the anchor UE provides information to the target UE regarding whether or not it can determine its own location. For absolute positioning, the anchor UE must already know its own location or be able to measure it using Uu positioning.

[0182]

[0183] Positioning Protocol Session

[0184] An LPP session is used between a location server and a target device to obtain location-related measurements or estimates or to transmit assistance data.

[0185] The LPP session uses a one-to-one (point-to-point) communication method between the target UE and the LMF,

[0186] It separates existing data communication procedures from positioning procedures. Furthermore, the LPP protocol operates independently of RATs and positioning methods. This means that the LPP protocol can support all RATs and positioning methods. Currently, it supports OTDOA (based on LTE signals), A-GNSS, E-CID (based on LTE signals), Sensor, TBS, WLAN, Bluetooth, NR E-CID, NR DL-TDOA, NR DL-AoD, and NR Multi-RTT.

[0187] Specifically, one LPP session corresponds to one location request originating from an LCS client, and multiple LPP sessions are created when there are multiple location requests.

[0188] The LPP session described above consists of one or more LPP transactions, and each LPP transaction corresponds to one LPP procedure (e.g., capability exchange, assistance transfer, location information transfer, etc.). Notably, LPP transactions may occur sequentially or concurrently.

[0189] Additionally, each LPP transaction is identified by an LPP transaction identifier. Therefore, each LPP transaction identifier identifies a related message. That is, related LPP messages use the same LPP transaction identifier.

[0190] Since the validity of each transaction is verified based on information received from previous transactions, if multiple sessions are supported, the validity of each transaction must be verified for each session. Therefore, distinguishing LPP sessions is crucial. For example, during LPP operation, when detecting duplication, the sequence number of each LPP message is determined to be valid within a specific session. During error detection, each LPP message is also determined to be valid within a specific session. Furthermore, the retransmission process also operates within a specific session.

[0191] Meanwhile, LPP session differentiation is not performed at the LPP layer. LPP sessions are differentiated based on the routing identifier and correlation identifier of the NAS layer.

[0192]

[0193] Session Distinction in Sidelink Positioning

[0194] Unlike conventional LPP, SLPP (sidelink positioning protocol) supports a point-to-multipoint communication protocol between the target UE and other surrounding UEs (e.g., anchor UEs). Therefore, in sidelink positioning, one anchor UE can support the sidelink positioning of multiple target UEs. That is, since one anchor UE can transmit and receive SL-PRS with multiple target UEs, one anchor UE can be connected to multiple target UEs through multiple SLPP sessions.

[0195] Meanwhile, unlike LPP, SLPP cannot distinguish positioning sessions at the NAS level. If an anchor UE is connected to multiple target UEs and multiple SLPP sessions are operating simultaneously, the anchor UE has no way to distinguish the individual SLPP sessions.

[0196] In recent 3GPP standardization, unlike the conventional LPP, it was discussed to add an SLPP session identifier to the SLPP header to distinguish each session in SLPP.

[0197] Meanwhile, as described above, a conventional LPP session is distinguished by a routing identifier and a correlation identifier at the upper level of the NAS, and since this distinction itself is made at the network level, the routing identifier and the correlation identifier can be implemented to have unique values.

[0198] However, since SLPP session identifiers are generated independently by each UE, it is difficult to ensure that they are unique and non-overlapping. If the generated SLPP session identifiers do not have unique values, anchor UEs cannot distinguish between SLPP sessions. In such cases, the anchor UE can only support a single session, which significantly limits sidelink positioning operations. Therefore, a method is needed that ensures that UEs have unique values ​​when generating SLPP session identifiers.

[0199] The present disclosure proposes a method for generating an SLPP session identifier or a similar method for uniquely distinguishing sessions. For convenience of explanation, the SLPP session identifier is abbreviated as a session identifier.

[0200] First, we can consider generating the session identifier randomly. Here, the session identifier has a specific number of bits, and the session identifier is randomly generated within the range of that specific number of bits.

[0201] For example, if a session identifier is 8 bits, it can have values ​​from 0 to 255 (or 1 to 256). The UE that creates the session randomly generates the session identifier within that range. This reduces the probability of overlap between different UEs' sequentially generated session identifiers, but it is difficult to guarantee that the generated identifiers have unique values.

[0202] Below, a method for configuring a session identifier proposed in the present disclosure is described.

[0203] <Option 1>

[0204] First, each UE creating a session can generate a session identifier using a combination of its own unique UE identifier and a session number. Preferably, the combination is a combination of a unique UE identifier and a session number.

[0205] Specifically, a unique UE identifier refers to a unique identifier of a specific UE that does not overlap with other UEs. For example, it can be an MEID (Mobile Equipment Identifier) ​​or IMEI (International Mobile Station Equipment Identity) included in a UE (ME: mobile equipment). Or, it can be an MDN (Mobile Directory Number) or IMSI included in a UICC (universal integrated circuit card) or SIM (Subscriber Identification Module) card. Alternatively, any identifier that can distinguish a UE, such as an identifier generated by an application or a Source Layer 2 ID used in sidelink communication, can be used.

[0206] Additionally, a session number is a sequential or randomly generated integer value. A session number has a specific number of bits and is generated sequentially or randomly within a range of that specific number of bits. For example, if a session number is 8 bits, it can have values ​​from 0 to 255 (or 1 to 256).

[0207] To ensure the generation of unique session identifiers, the UE may require that additional session numbers generated after one or more sessions have been created must not overlap with session numbers of previously created sessions that have not been terminated. In this case, terminated session numbers can be reused.

[0208]

[0209] FIG. 20 is a flowchart illustrating an example of transmitting a message using a session identifier generated according to the present disclosure.

[0210] Referring to FIG. 20, in step A05, the UE establishes a session with a peer UE.

[0211] A UE that establishes a session first randomly obtains a session number, as in step A10. However, the session number has a specific number of bits and is randomly generated within the range of that specific number of bits. For example, if the session number is 8 bits, it can have values ​​from 0 to 255 (or 1 to 256).

[0212] Next, if the session number acquired in step A10 does not match at least one pending session number, the UE generates a session identifier including the identifier of the UE and the acquired session number in step A15. Here, the at least one pending session number refers to one that is established prior to the establishment of the session and is related to at least one session that has not been terminated, with the constraint that it must not overlap with session numbers of sessions that were previously created and have not been terminated.

[0213] Finally, in step A20, the UE transmits a message including the session identifier to the peer UE over the established session. Preferably, the session identifier is included in the header of the message. Furthermore, the message may be a positioning message for positioning the UE or a UE-based sensing-related message.

[0214]

[0215] <Option 2>

[0216] Next, we can consider a method to distinguish sessions by including a unique UE identifier in the SLPP.

[0217] Here, the unique UE identifier refers to a unique identifier of a specific UE that does not overlap with other UEs. For example, it can be the MEID (Mobile Equipment Identifier) ​​or IMEI (International Mobile Station Equipment Identity) included in the UE (ME: mobile equipment). Or, it can be the MDN (Mobile Directory Number) or IMSI included in the UICC (universal integrated circuit card) or SIM (Subscriber Identification Module) card. Alternatively, any identifier that can distinguish the UE, such as an identifier generated by an application or a Source Layer 2 ID used in sidelink communication, can be used.

[0218] Here, a unique UE identifier is included in the SLPP message. That is, the unique UE identifier is included in the SLPP header or a specific part of each SLPP message.

[0219] Additionally, the session identifier itself is generated sequentially or randomly. The anchor UE can distinguish sessions by combining the session identifier with a unique UE included in the SLPP.

[0220]

[0221] <Option 3>

[0222] Additionally, sessions can be distinguished using the Source ID in the SCI (Sidelink Control Information) and / or MAC header.

[0223] Here, SCI means a 1-stage SCI and / or a 2-stage SCI, and the SCI includes a part of the 24-bit source ID for sidelink communication or the entire 24-bit source ID, and the header of the MAC PDU included in the message includes a part of the source ID for sidelink communication.

[0224] The entire 24-bit source ID can be determined using only the first-stage SCI. Alternatively, the entire 24-bit source ID can be determined by combining the second-stage SCI and MAC header information.

[0225] In this way, the session number of each SLPP message (transaction) and the UE that established the session can be distinguished through the entire 24-bit source ID.

[0226]

[0227] <Option 4>

[0228] Ensuring the uniqueness of session identifiers through session establishment acceptance procedures and session establishment rejection procedures can also be considered.

[0229] A UE that receives a session establishment request may reject the session establishment if the session identifier is duplicated (i.e., overlaps with one or more currently used session identifiers). In this case, the UE may indicate that the rejection is due to a duplicate session identifier.

[0230] Here, if the UE requesting session establishment receives a session establishment rejection message due to session identifier duplication from at least one UE included in the session, the UE requesting session establishment generates a new session identifier and re-requests session establishment. Through this process, the UE can confirm that the session identifier is duplicated, i.e., lacks uniqueness.

[0231] Of course, a UE that has received a session establishment request may accept the session establishment if the session identifier is not duplicated (i.e., does not overlap with any of the currently used session identifiers).

[0232] Session establishment acceptance and session establishment rejection can be used interchangeably. That is, if there is no session establishment rejection, the session establishment can be considered accepted. Alternatively, if there is no session establishment acceptance, the session establishment can be considered rejected.

[0233]

[0234] The above proposals 1 to 4 may be applied alone, or two or more proposals may be applied in combination.

[0235] FIG. 21 is a flowchart illustrating another example of transmitting a message using a session identifier generated according to the present disclosure.

[0236] Referring to FIG. 21, the UE first randomly obtains or generates a session identifier in step B05.

[0237] Next, if the session identifier acquired or generated in step B05 does not match at least one pending session identifier, then in step B10, the UE transmits a session establishment request message including the acquired session identifier to the peer UE. Here, the at least one pending session identifier refers to one that is established prior to the establishment of the session and is related to at least one session that has not been terminated, with the constraint that it must not overlap with session identifiers of sessions that have been generated in advance and have not been terminated.

[0238] Finally, in step B15, if the UE receives a session establishment acceptance message from the peer UE, the session is considered successfully established. Subsequently, in step B20, the UE transmits at least one message to the peer UE over the established session. Preferably, the at least one message may be a positioning message for positioning the UE or a UE-based sensing-related message.

[0239]

[0240] In this disclosure, a UE refers to a UE included in an SLPP session for a specific sidelink positioning. That is, it includes all UEs that are responsible for various tasks (roles), such as a target UE, anchor UE, and server UE for sidelink positioning, and that require SLPP message transmission / reception.

[0241] Embodiments of the present disclosure can be applied to implement the wireless sensing and radio frequency sensing functions described above.

[0242] In addition, although the term sidelink positioning is used in the present disclosure for convenience of explanation, the configuration of the present disclosure can be applied to positioning based on a communication method that directly exchanges voice or data, etc. by establishing a direct link between UEs without going through a BS.

[0243] It is also possible to construct embodiments of the present disclosure. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment, or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments, or may be incorporated as new claims through post-filing amendments.

[0244] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the scope of the present disclosure. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present disclosure are intended to be included within the scope of the present disclosure.

[0245] The present disclosure may be used in a terminal, base station, or other equipment of a wireless mobile communication system.

Claims

1. A method performed by a UE (User Equipment) in a wireless communication system, Step of establishing a session with a peer UE; A step of randomly obtaining a session number; generating a session identifier including an identifier of the UE and the acquired session number based on the acquired session number not matching at least one pending session number; and characterized in that it comprises a step of transmitting a message including the session identifier to the peer UE on the established session. method.

2. In paragraph 1, characterized in that the above session identifier is included in the header of the message; method.

3. In paragraph 1, wherein the message is characterized in that it relates to positioning of the UE or relates to UE-based sensing. method.

4. In paragraph 1, At least one session number that is pending above, characterized in that it relates to at least one session established prior to the establishment of the above session and which has not been terminated; method.

5. As a UE (User equipment) in a wireless communication system, At least one transmitter / receiver; at least one processor; and At least one computer memory operably connectable to said at least one processor, and storing instructions that, when executed, cause said at least one processor to perform operations for said UE; The above actions are, Step of establishing a session with a peer UE; A step of randomly obtaining a session number; generating a session identifier including an identifier of the UE and the acquired session number based on the acquired session number not matching at least one pending session number; and characterized in that it comprises a step of transmitting a message including the session identifier to the peer UE on the established session. UE.

6. In paragraph 5, characterized in that the above session identifier is included in the header of the message; UE.

7. In paragraph 5, wherein the message is characterized in that it relates to positioning of the UE or relates to UE-based sensing. UE.

8. In paragraph 6, At least one session number that is pending above, characterized in that it relates to at least one session established prior to the establishment of the above session and which has not been terminated; UE.

9. In a processing device in a wireless communication system, at least one processor; and At least one computer memory operably connectable to said at least one processor, and storing instructions that, when executed, cause said at least one processor to perform operations for a UE (User Equipment), The above actions are, Step of establishing a session with a peer UE; A step of randomly obtaining a session number; generating a session identifier including an identifier of the UE and the acquired session number based on the acquired session number not matching at least one pending session number; and characterized in that it comprises a step of transmitting a message including the session identifier to the peer UE on the established session. Processing unit.

10. In a computer-readable storage medium, The storage medium stores at least one program code including instructions that, when executed, cause at least one processor to perform operations for a UE (User Equipment), The above actions are, Step of establishing a session with a peer UE; A step of randomly obtaining a session number; generating a session identifier including an identifier of the UE and the acquired session number based on the acquired session number not matching at least one pending session number; and characterized in that it comprises a step of transmitting a message including the session identifier to the peer UE on the established session. Computer readable storage medium.

11. A method performed by a UE (User Equipment) in a wireless communication system, A step of randomly obtaining a session identifier; A step of transmitting a session establishment request message including the acquired session identifier to a peer UE based on the acquired session identifier not matching at least one pending session identifier; and A method comprising: transmitting at least one message to the peer UE based on receiving a session establishment acceptance message from the peer UE; method.

12. In paragraph 11, wherein said at least one message is characterized in that it is related to positioning of said UE or related to UE-based sensing. method.

13. As a UE (User equipment) in a wireless communication system, At least one transmitter / receiver; at least one processor; and At least one computer memory operably connectable to said at least one processor, and storing instructions that, when executed, cause said at least one processor to perform operations for said UE; The above actions are, A step of randomly obtaining a session identifier; A step of transmitting a session establishment request message including the acquired session identifier to a peer UE based on the acquired session identifier not matching at least one pending session identifier; and A method comprising: transmitting at least one message to the peer UE based on receiving a session establishment acceptance message from the peer UE; UE.

14. In paragraph 13, wherein said at least one message is characterized in that it is related to positioning of said UE or related to UE-based sensing. UE.

Images