WO2024196203A1 - Method for processing error in positioning procedure in wireless communication system and apparatus therefor - Google Patents

Abstract

The present disclosure relates to a method by which a user equipment (UE) performs positioning in a wireless communication system. In particular, the method comprises the steps of: receiving a positioning protocol message from at least one peer UE; verifying the at least one positioning protocol message; generating a positioning protocol error message on the basis that there is an error in the at least one positioning protocol message; and transmitting the positioning protocol error message, wherein the positioning protocol error message comprises information regarding at least one error that has occurred when verifying the at least one positioning protocol message.

Description

Error handling method in positioning procedure in wireless communication system and device therefor

This specification relates to a wireless communication system. More specifically, it relates to an error handling method in a positioning procedure in a wireless communication system and a device therefor.

Wireless communication systems are being widely deployed to provide various types of communication services such as voice and data. In general, wireless communication systems are multiple access systems that can support communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.). Examples of multiple access systems include CDMA (code division multiple access) systems, FDMA (frequency division multiple access) systems, TDMA (time division multiple access) systems, OFDMA (orthogonal frequency division multiple access) systems, and SC-FDMA (single carrier frequency division multiple access) systems.

Sidelink (SL) refers to a communication method that establishes a direct link between UEs to directly exchange voice or data, etc., between UEs without going through a BS (Base Station). SL is being considered as a solution to solve the burden on base stations due to rapidly increasing data traffic.

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

Meanwhile, as more and more communication devices require greater communication capacity, there is a growing need for improved mobile broadband communication over existing Radio Access Technology (RAT). Accordingly, communication systems that consider services or terminals sensitive to reliability and latency are being discussed, and the next-generation radio access technology that considers improved mobile broadband communication, massive MTC (Machine Type Communication), URLLC (Ultra-Reliable and Low Latency Communication), etc. can be called new RAT (new radio access technology) or NR (new radio). V2X (vehicle-to-everything) communication can also be supported in NR.

Based on the above discussion, the following proposes an error handling method and a device therefor in a positioning procedure in a wireless communication system.

The technical problems to be solved by this specification are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art related to this specification from the detailed description below.

In one aspect of the present specification, a method performed by a User Equipment (UE) in a wireless communication system is provided. The method comprises: receiving a positioning protocol message from at least one peer UE; verifying the at least one positioning protocol message; generating a positioning protocol error message based on an error in the at least one positioning protocol message; and transmitting the positioning protocol error message, wherein the positioning protocol error message includes information regarding at least one error that occurred during verification of the at least one positioning protocol message.

In another aspect of the present disclosure, a User Equipment (UE) is provided in a wireless communication system. The UE comprises: 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. The operations include: receiving a positioning protocol message from at least one peer UE; verifying the at least one positioning protocol message; generating a positioning protocol error message based on an error in the at least one positioning protocol message; and transmitting the positioning protocol error message, wherein the positioning protocol error message includes information regarding at least one error that occurred during verification of the at least one positioning protocol message.

In another 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: receiving a positioning protocol message from at least one peer UE; verifying the at least one positioning protocol message; generating a positioning protocol error message based on an error in the at least one positioning protocol message; and transmitting the positioning protocol error message, wherein the positioning protocol error message includes information regarding at least one error that occurred during verification of the at least one positioning protocol message.

In another 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: receiving a positioning protocol message from at least one peer UE; verifying the at least one positioning protocol message; generating a positioning protocol error message based on an error in the at least one positioning protocol message; and transmitting the positioning protocol error message, wherein the positioning protocol error message includes information regarding at least one error that occurred during verification of the at least one positioning protocol message.

Preferably, the positioning protocol error message includes at least one of common error information and positioning method specific error information.

Preferably, the information about said at least one error includes: information about an area of a header of said positioning protocol message or a body of said positioning protocol message in which said at least one error occurred; and information about a type of said at least one error.

Preferably, if there are a plurality of peer UEs, the positioning protocol error message can be groupcast to the plurality of peer UEs. In particular, the information about the at least one error included in the positioning protocol error message includes information about the corresponding peer UE.

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.

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

The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are 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.

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:

Figure 1 shows the structure of the NR system.

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

Figure 3 shows the radio protocol architecture of the NR system.

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

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

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

FIGS. 7 and 8 illustrate wireless devices according to one embodiment of the present disclosure.

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

Figure 10 shows a radio protocol architecture for SL communication.

Figure 11 shows the synchronization source or synchronization reference of V2X.

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

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

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

Figure 15 shows 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.

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

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

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.

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

Fig. 20 is a drawing exemplifying a method for transmitting a response message of an LPP message according to the prior art.

Fig. 21 is a drawing exemplifying a method for retransmitting an LPP message according to the prior art.

Figure 22 illustrates an example of transmitting a positioning error message according to the prior art.

FIG. 23 illustrates an example of transmitting a positioning error message according to the present disclosure.

The following technology 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, E-UTRA (Evolved UTRA). UTRA is a part of UMTS (Universal Mobile Telecommunications System). 3GPP(3rd Generation Partnership Project) LTE(long term evolution) is a part of E-UMTS(Evolved UMTS) that uses E-UTRA, 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.

As more and more communication devices require greater communication capacity, there is a growing need for improved mobile broadband communications compared to existing RATs (Radio Access Technology). In addition, massive MTC (Machine Type Communications), which connects multiple devices and objects to provide various services anytime and anywhere, is also one of the major issues to be considered in next-generation communications. In addition, a communication system design that considers services/terminals that are sensitive to reliability and latency is being discussed. In this way, the introduction of next-generation RATs that consider eMBB (enhanced Mobile BroadBand Communication), massive MTC, URLLC (Ultra-Reliable and Low Latency Communication), etc., is being discussed, and in this disclosure, the technology is conveniently called NR (New Radio or New RAT).

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

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 corresponding 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 expects/assumes (or expects/assumes that the terminal does not perform) the specific operation and operates. In addition, the expression that the base station performs (or does not perform) the specific operation can also be interpreted as meaning that the terminal expects/assumes (or expects/assumes that the base station does not perform) the specific operation and operates. 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 individually. In addition, in describing each section, embodiment, example, option, method, plan, etc., if there is no explicitly conflicting/opposing technology, 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 some.

Figure 1 shows the structure of the NR system.

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-NodeB (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), a Wireless Device, etc. 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), an Access Point, etc.

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

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

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 & provision, and dynamic resource allocation. The AMF can provide functions such as NAS (Non Access Stratum) security and idle state mobility processing. The UPF can provide functions such as mobility anchoring and PDU (Protocol Data Unit) processing. The SMF (Session Management Function) can provide functions such as terminal IP (Internet Protocol) address allocation and PDU session control.

The layers of the radio interface protocol between the terminal and the network can be divided into L1 (the first layer), L2 (the second layer), and L3 (the third layer) 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 the first layer provides an information transfer service using a physical channel, and the RRC (Radio Resource Control) layer located in the third layer 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.

Fig. 3 shows the radio protocol architecture of the NR system. Specifically, Fig. 3 (a) shows the radio protocol architecture for the user plane, and Fig. 3 (b) shows the radio protocol architecture for the control plane. The user plane is a protocol stack for user data transmission, and the control plane is a protocol stack for control signal transmission.

Referring to Figure 3, the physical layer provides information transmission services to the upper layer using a physical channel. The physical layer is connected to the upper layer, the MAC (Medium Access Control) layer, through a transport channel. Data moves between the MAC layer and the physical layer through the transport channel. The transport channel is classified according to how and with what characteristics data is transmitted through the wireless interface.

Data is transferred between different physical layers, that is, between the physical layers of the transmitter and receiver, through a physical channel. The physical channel can be modulated using the OFDM (Orthogonal Frequency Division Multiplexing) method and utilizes time and frequency as radio resources.

The MAC layer provides services to the upper layer, the radio link control (RLC) layer, through logical channels. The MAC layer provides a mapping function from multiple logical channels to multiple transport channels. In addition, the MAC layer provides a logical channel multiplexing function by mapping from multiple logical channels to a single transport channel. The MAC sublayer provides data transmission services on logical channels.

The RLC layer performs concatenation, segmentation, and reassembly of RLC SDUs (Service Data Units). In order to guarantee various QoS (Quality of Service) required by Radio Bearer (RB), the RLC layer provides three operation modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). AM RLC provides error correction through automatic repeat request (ARQ).

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 in relation to the configuration, re-configuration, and release of radio bearers. RB refers to a logical path provided by the first layer (physical layer or PHY layer) and the second layer (MAC layer, RLC layer, PDCP (Packet Data Convergence Protocol) layer) for data transmission between the terminal and the network.

The functions of the PDCP layer in the user plane include forwarding of user data, header compression, and ciphering. The functions of the PDCP layer in the control plane include forwarding of control plane data and ciphering/integrity protection.

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

Establishing an RB means the process of specifying the characteristics of the radio protocol layer and channel to provide a specific service, and setting each specific parameter and operation method. RB can be divided into two types: SRB (Signaling Radio Bearer) and DRB (Data Radio Bearer). SRB is used as a channel to transmit RRC messages in the control plane, and DRB is used as a channel to transmit user data in the user plane.

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, an RRC_INACTIVE state is additionally defined, and a terminal in the RRC_INACTIVE state can release the connection with the base station while maintaining the connection with the core network.

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

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).

A physical channel consists of multiple OFDM symbols in the time domain and multiple sub-carriers in the frequency domain. One sub-frame 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 sub-carriers. In addition, each subframe can use specific sub-carriers of specific OFDM symbols (e.g., the first OFDM symbol) of the corresponding subframe for the Physical Downlink Control Channel (PDCCH), i.e., the L1/L2 control channel. A Transmission Time Interval (TTI) is a unit time of subframe transmission.

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

Referring to FIG. 4, uplink and downlink transmissions in NR are composed of 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 subframes (Subframes, SF). A subframe is divided into one or more slots, and the number of slots in a subframe depends on Subcarrier Spacing (SCS). Each slot contains 12 or 14 OFDM (Orthogonal Frequency Division Multiplexing) symbols depending on a CP (cyclic prefix). When a normal CP is used, each slot contains 14 OFDM symbols. When an extended CP is used, each slot contains 12 OFDM symbols.

Table 1 shows the number of OFDM symbols per slot ( N ^slot _symb ), the number of slots per frame ( N ^frame,u _slot ), and the number of slots per subframe ( N ^subframe,u _slot ) according to SCS for regular CP.

u	N slot Symb	N frame,u slot	N subframe,u slot
0	14	10	1
1	14	20	2
2	14	40	4
3	14	80	8
4	14	160	16

Table 2 shows the number of OFDM symbols per slot ( N ^slot _symb ), the number of slots per frame ( N ^frame,u _slot ), and the number of slots per subframe ( N ^subframe,u _slot ) according to SCS when extended CP is used.

u	N slot Symb	N frame,u slot	N subframe,u slot
2	12	40	4

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 changed in various ways.

In an NR system, OFDM numerologies (e.g., SCS) may be set differently between multiple cells merged into one terminal. Accordingly, (absolute time) sections of time resources (e.g., SFs, slots, or TTIs) (conveniently referred to as TUs (Time Units)) consisting of the same number of symbols may be set differently between the merged cells. Here, the symbols may include OFDM symbols (or CP-OFDM symbols), SC-FDMA symbols (or Discrete Fourier Transform-spread-OFDM, DFT-s-OFDM symbols).

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

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 one 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 one terminal. Each element in the resource grid is referred to as a Resource Element (RE), and one complex symbol can be mapped to it.

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

Referring to FIG. 6, the communication system (1) includes a wireless device, a base station, and a network. Here, the wireless device means 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 Thing) 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. Portable devices can include smartphone, smart pad, wearable device (e.g., smart watch, smart glass), computer (e.g., laptop, 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.

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). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

Wireless communication/connection (150a, 150b, 150c) can be established between wireless devices (100a to 100f)/base stations (200), and base stations (200)/base stations (200). Here, the wireless communication/connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink/downlink communication (150a) and sidelink communication (150b) (or, D2D communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access Backhaul)). Through the wireless communication/connection (150a, 150b, 150c), a wireless device and a base station/wireless device, and a base station and a base station can transmit/receive wireless signals to/from each other. For example, the 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.

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

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

A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may additionally include one or more transceivers (106) and/or one or more antennas (108). The processor (102) controls the memory (104) and/or the transceiver (106), and may be configured to implement the descriptions, functions, procedures, suggestions, 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). Additionally, 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 codes including instructions for performing the descriptions, functions, procedures, proposals, methods, and/or operational 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 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.

The second wireless device (200) includes one or more processors (202), one or more memories (204), and may additionally include one or more transceivers (206) and/or one or more antennas (208). The processor (202) may be configured to control the memories (204) and/or the transceivers (206), and implement the descriptions, functions, procedures, suggestions, 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). Additionally, 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 codes including instructions for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in the present 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.

Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operational 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 operational flowcharts disclosed in this document. One or more processors (102, 202) can generate signals (e.g., baseband signals) comprising PDUs, SDUs, messages, control information, data or information according to the functions, procedures, suggestions and/or methodologies 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, suggestions, methods and/or operational flowcharts disclosed herein.

The one or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. The 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 the one or more processors (102, 202). The descriptions, functions, procedures, suggestions, 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 operational flowcharts disclosed in this document may be implemented using firmware or software configured to perform one or more of the following: included in one or more processors (102, 202), or stored in one or more memories (104, 204) and driven by one or more of the processors (102, 202). The descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and/or sets of instructions.

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 comprised of 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.

One or more transceivers (106, 206) can transmit user data, control information, wireless signals/channels, etc., as described 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 described in the descriptions, functions, procedures, suggestions, methods and/or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be coupled 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, and 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) may 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 processed user data, control information, wireless signals/channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and/or filter.

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.

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 overall operations of the wireless device. For example, the control unit (120) may control electrical/mechanical operations of the wireless device based on programs/codes/commands/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).

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.

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 one or more processor sets. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphic 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.

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

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.

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.), servers, etc. 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, a light 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.

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 a driving plan based on the acquired data. The control unit (120) can control the driving 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, the sensor unit (140c) can acquire vehicle status and surrounding environment information during autonomous driving. The autonomous driving unit (140d) can update the autonomous driving route and driving plan based on the newly acquired data/information. The communication unit (110) can transmit information on the vehicle location, autonomous driving route, driving plan, etc. to an external server. External servers can predict traffic information data in advance using AI technology, etc. based on information collected from vehicles or autonomous vehicles, and provide the predicted traffic information data to vehicles or autonomous vehicles.

Below, V2X or SL communication is explained.

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.

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

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 (signal detection) and acquire synchronization using the S-PSS. For example, the terminal may acquire detailed synchronization and detect a synchronization signal ID using the S-PSS and the S-SSS.

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

The 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 a 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 RB (Resource Block). 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 frequency to discover the S-SSB in the carrier.

Below, the synchronization acquisition of the SL terminal is described.

In TDMA (time division multiple access) and FDMA (frequency division multiples access) 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). The same applies to V2X. In V2X, for time/frequency synchronization, the physical layer can use the SL synchronization signal (sidelink synchronization signal, SLSS), and the RLC (radio link control) layer can use the MIB-SL-V2X (master information block-sidelink-V2X).

Figure 11 shows the synchronization source or synchronization reference of V2X.

Referring to Fig. 11, in V2X, a terminal can be directly synchronized to GNSS (global navigation satellite systems), or can be indirectly synchronized to GNSS through a terminal (within network coverage or out of 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 UTC (Coordinated Universal Time) and a (pre-)configured DFN offset.

Alternatively, the terminal may be directly synchronized 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, when the terminal is within network coverage, the terminal may receive synchronization information provided by the base station and be directly synchronized to the base station. Thereafter, the terminal may provide the synchronization information to other adjacent terminals. When the base station timing is set as the synchronization criterion, the terminal may follow the cell associated with the frequency (if it is within cell coverage at the frequency), the primary cell, or the serving cell (if it is outside cell coverage at the frequency) for synchronization and downlink measurement.

A base station (e.g., a serving cell) may provide synchronization settings for a carrier used for V2X or SL communication. 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 the V2X or SL communication and does not receive synchronization settings from the serving cell, the terminal may follow the preset synchronization settings.

Alternatively, the terminal may be synchronized to 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.

Whether GNSS-based synchronization 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.

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.

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 a resource allocation mode. Hereinafter, for convenience of explanation, the transmission mode in LTE may be referred to as an LTE transmission mode, and the transmission mode in NR may be referred to as an NR resource allocation mode.

For example, (a) of Fig. 12 represents a terminal operation related to LTE transmission mode 1 or LTE transmission mode 3. Or, for example, (a) of Fig. 12 represents a 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.

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.

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.

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

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 PUCCH or 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.

Referring to (b) of FIG. 12, in LTE transmission mode 2, LTE transmission mode 4 or NR resource allocation mode 2, a terminal may determine an SL transmission resource within an SL resource set by a base station/network or a preset SL resource. For example, the set SL resource or the preset SL resource may be a resource pool. For example, the terminal may autonomously select or schedule resources for SL transmission. For example, the terminal may perform SL communication by selecting a resource by itself within the set resource pool. For example, the terminal may perform sensing and resource (re)selection procedures to select a resource by itself within a selection window. For example, the sensing may 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 may transmit a PSCCH (e.g., SCI (Sidelink Control Information) or 1st-stage SCI) to a second terminal using the resource. In step S8020, the first terminal can 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 can receive a PSFCH related to the PSCCH/PSSCH from the second terminal.

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.

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

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

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

Specifically, (a) of FIG. 13 represents SL communication of a broadcast type, (b) of FIG. 13 represents SL communication of a unicast type, and (c) of FIG. 13 represents SL communication of a groupcast type. In the case of SL communication of a unicast type, a terminal can perform one-to-one communication with another terminal. In the case of SL communication of a groupcast type, 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 may be replaced with SL multicast communication, SL one-to-many communication, etc.

<Integrated sensing and communication (ISAC)>

Wireless sensing is a technology that uses radio frequencies to detect the instantaneous linear velocity, angle, distance (range), etc. of an object, thereby obtaining information about the characteristics of the environment and/or objects within the environment. Since this radio frequency sensing function does not require a connection to the object via a device within a network, it can provide a service for identifying the location of the object without a device.

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

FIG. 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 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).

<Positioning>

Figure 15 shows 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.

Referring to FIG. 15, the AMF may receive a request for location service 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 the location service on behalf of a specific target UE. Then, the AMF may transmit the location service request to the 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, etc. 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.

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

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 OTDOA (Observed Time Difference Of Arrival), which is one of the positioning methods of the E-UTRAN, by utilizing downlink measurements acquired by the target UE via signals transmitted from eNB and/or PRS dedicated TPs in the E-UTRAN.

Meanwhile, the LMF may be connected to the SLP (SUPL Location Platform). 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 position measurements of the UE. For positioning of the target UE, the LMF may determine a positioning method based on an LCS (Location Service) client type, a required QoS (Quality of Service), UE positioning capabilities, gNB positioning capabilities, and ng-eNB positioning capabilities, and may apply the positioning method to the serving gNB and/or the serving ng-eNB. In addition, the LMF may determine additional information, such as a position estimate for the target UE and the accuracy of the position estimate and velocity. The SLP is a SUPL (Secure User Plane Location) entity responsible for positioning via the user plane.

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 and 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 position of the UE independently of NG-RAN transmissions. This independently acquired positioning information may be utilized as auxiliary information for the positioning information acquired from the network.

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

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

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

Thereafter, the AMF may send a location service request to the LMF according to step 2, and the LMF may initiate location procedures with the serving ng-eNB, the serving gNB to obtain location measurement data or location measurement assistance data according to step 3a. 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 position estimate or a position measurement. Meanwhile, step 3b may be performed additionally after step 3a is performed, or may be performed instead of step 3a.

In step 4, the LMF may provide a location service response to the AMF. In addition, the location service response may include information on whether the location estimation of the UE was successful and a location estimate of the UE. After that, 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 GMLC, and if the procedure of FIG. 16 was initiated by step 1b, the AMF may use the location service response to provide location services related to emergency calls, etc.

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

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

For example, via the LPP protocol, the target device and the location server can exchange capability information, exchange auxiliary data for positioning, and/or exchange location information. In addition, error information can be exchanged and/or an LPP procedure can be stopped via LPP messages.

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.

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

The procedures of the NRPPa protocol 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.). The two types of procedures may be supported independently or simultaneously.

<Positioning Method>

Meanwhile, positioning methods supported by NG-RAN, i.e., positioning methods, may include GNSS, OTDOA, E-CID (enhanced cell ID), air 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 one positioning method, but the position of the UE may also be measured using two or more positioning methods.

(1) OTDOA (Observed Time Difference Of Arrival)

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

The OTDOA positioning method uses the timing of measurements of downlink signals received from multiple TPs, including 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 geographical coordinates of neighboring TPs, the location of the UE can be determined.

A UE connected to a gNB may request a measurement gap for OTDOA measurements from a TP. If the UE is not aware of 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.

Here, 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.

For accurate OTDOA measurement, it is necessary to measure the time of arrival (TOA) of signals received from three or more geographically distributed TPs or base stations. For example, TOAs for TP 1, TP 2, and TP 3 are measured respectively, and RSTD for TP 1-TP 2, RSTD for TP 2-TP 3, and RSTD for TP 3-TP 1 are calculated based on the three TOAs, and a geometric hyperbola is determined based on these, and the point where these hyperbolas intersect can be estimated as the position of the UE. At this time, since there may be accuracy and/or uncertainty for each TOA measurement, the estimated position of the UE may be known within a certain range according to the measurement uncertainty.

(2) E-CID (Enhanced Cell ID)

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

Meanwhile, the E-CID positioning method may utilize additional UE measurements and/or NG-RAN radio resources to improve the UE position estimation in addition to the CID positioning method. 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 only for position measurement of the UE. In other words, a separate measurement configuration or measurement control message may not be provided for measuring the position of the UE, and the UE also does not expect to be requested to perform additional measurement operations only for position measurement, and may report measurements acquired through measurement methods that the UE can generally measure.

(3) UTDOA (Uplink Time Difference of Arrival)

UTDOA is a method to determine the location of a UE by estimating the arrival time of an SRS. When calculating the estimated SRS arrival time, the serving cell is used as a reference cell, and the location of the UE can be estimated through the difference in arrival times with other cells (or base stations/TPs). To implement UTDOA, the E-SMLC can designate the serving cell of a target UE to instruct the target UE to transmit SRS. In addition, the E-SMLC can provide configurations such as whether the SRS is periodic/aperiodic, bandwidth, and frequency/group/sequence hopping.

<Side link positioning>

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 scheduled to be supported starting from the recent 3GPP NR standard release 18.

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

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

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 required for positioning through the LPP protocol, and the target UE receives positioning information required for positioning through the LMF. Additionally, the LMF sets up a base station (gNB) through the NRPPa protocol, exchanges positioning-related messages, and performs positioning operations.

Meanwhile, in sidelink positioning, positioning operations are performed by exchanging positioning protocol messages with anchor UEs around the target UE, not the LMF. Therefore, sidelink positioning operations in the protocol layer are performed between UEs through the sidelink positioning protocol (SLPP).

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

- SL Positioning Capability Transfer

- SL Positioning Assistance Data exchange

- SL Location Information Transfer

- Error handling

- Abort

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

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

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.

2) The target UE and candidate UE decide on the final anchor UE through negotiation after basic information exchange. When performing negotiation for SL positioning, the decision on the anchor UE is limited to cases where the request to perform the role of anchor UE is not rejected during the negotiation process (negotiation success).

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

<Method for ensuring transmission reliability of LPP messages>

Conventional LPP messages use the ACK (Acknowledgement) response method to ensure transmission reliability.

Fig. 20 is a drawing exemplifying a method for transmitting a response message of an LPP message according to the prior art, and Fig. 21 is a drawing exemplifying a method for retransmitting an LPP message according to the prior art. In particular, the part indicated by a dotted line in Fig. 21 exemplifies a case where a message is transmitted but not successfully received.

Referring to Figure 20, endpoint A transmits message N to endpoint B by setting the Acknowledgement field, which is defined as a common field of the LPP message, to a specific value.

Endpoint B, which receives message N, checks the Acknowledgement field set to a specific value and then transmits a response message of message N containing only a sequence number to endpoint A. Here, the sequence number contains a value corresponding to message N.

Endpoint A, which receives the response message, considers message N to have been successfully transmitted and sends the next message N+1 to endpoint B.

However, if endpoint A does not receive a response message to message N within a specified time as in Fig. 21, endpoint A performs retransmission of message N with the same sequence number after the timeout period.

Retransmission is performed up to 3 times, and if a response message to message N is not received, the positioning session is aborted.

Meanwhile, if endpoint A retransmits, the receiver can check for message duplication using the sequence number.

<SLPP error message>

According to the LPP standard 3GPP TS 37.355, the cases in which errors are detected and the corresponding actions are as follows.

- Decoding error occurred: Send error message

- Duplicate receipt of the same message: Message not sent

- Invalid message type received: Error message sent

- Receiving segment messages of different message types: Sending error messages

- Receiving a message containing unsupported information: Sending a random message

According to 3GPP standard document TS 37.355, error messages include the cause of the error.

As shown in Table 3 below, the cause of the error is notified whether it occurred in the message header (lppMessageHeaderError) or the message body (lppMessageBodyError), and if it is an error in the segment message (lppSegmentationError-v1450), it is notified separately.

-- ASN1START CommonIEsError ::= SEQUENCE { errorCause ENUMERATED { undefined, lppMessageHeaderError, lppMessageBodyError, epduError, incorrectDataValue, ..., lppSegmentationError-v1450 } } -- ASN1STOP

In addition to the common error messages described above, if an error occurs in the Request Assistance Data and Request Location information messages of each positioning method, an error argument is inserted into the Provide message of the corresponding positioning method and transmitted.

In conventional procedures, an error type is included when transmitting a common error message. Here, by sending an error type in the common error message, the transmitting end that receives the error message from the receiving end can retransmit or modify the error message according to the cause of the error. For example, in the case of receiving an invalid message type, the message type is modified/changed and transmitted. In the case of a simple decoding error, the message is simply retransmitted because there is a possibility that it is a problem with the physical channel.

However, the problem is that the conventional LPP error message does not include an error type. The error cause does not include error type information, but only indicates which part of the message the error occurred in. That is, whether it occurred in the message header, the message body, or whether it is a segment message. In other words, since the error message only indicates the part where the error occurred (i.e., the header or the body), even if the sender normally receives the error message, it is difficult to identify the exact cause of the error that occurred at the receiver.

Therefore, the transmitter must find the cause of the error in the message in which the error occurred, correct the cause of the error as necessary, and (re)transmit it. In the conventional one-to-one communication LPP protocol, this problem is partially implemented in which the transmitter's error estimation is possible.

For example, if an error is detected in the header, there is a high probability that the transaction information in the header is invalid. If an error is detected in the body, there is a high probability that a decoding error occurred. If an error is detected in the segment message, there is a high probability that a different message type was transmitted.

However, in the SLPP protocol, which is a one-to-many communication, the cause of the error may be different for each UE where the error occurred. For example, even if the same message is transmitted by the target UE to anchor UE A and anchor UE B and the same header error occurs, a header error due to a decoding error may occur in UE A, but it may be invalid information in UE B. Therefore, it is difficult to predict the exact cause of the error in terms of implementation with only the error information that occurred in the header or body.

Additionally, according to the prior art, if an error occurs in the Request Assistance Data and Request Location information messages of each positioning method, the error argument of the Provide message of the corresponding positioning method is inserted and transmitted. However, in SLPP, the required information can be designed by dividing it into common and different parts without distinguishing it by positioning method. In this case, using the error message in common without distinguishing it by positioning method can reduce the overhead in message processing and increase efficiency.

Therefore, SLPP, a one-to-many communication protocol, needs improvement in error messages that enable accurate error handling for each UE and integrate various positioning methods.

In this disclosure, we propose an extended SLPP error message for effective SLPP error handling.

Table 4 below shows the SLPP error messages proposed in this disclosure, which are divided into a common error area (commonIEsError) and a dedicated error area (dedicatedIEsError).

-- ASN1START Error ::= CHOICE { error-r18 Error-r18-IEs, criticalExtensionsFuture SEQUENCE {} } Error-r18-IEs ::= SEQUENCE { commonIEsError CommonIEsError OPTIONAL, -- Need ON dedicatedIEsError DedicatedIEsError OPTIONAL, -- Need ON ..., }- - ASN1STOP

The common error area is used to transmit errors that are common regardless of the positioning method. On the other hand, the individual error areas are used to transmit errors that are distinct for each positioning method. Each area is included when necessary. That is, an error message includes a common error area and/or an individual error area.

The SLPP error message header contains the UE role/type in sidelink positioning, i.e. whether it is a target/anchor/server UE, and/or sender/receiver information, so that it can be determined who transmitted the SLPP error message (sender information) and to whom it is intended to be delivered (receiver information).

In addition, the SLPP error message of the present disclosure can be transmitted in unicast and groupcast/broadcast. Unicast transmission is when transmitting to a specific UE, and groupcast/broadcast transmission is when transmitting the same message to multiple UEs.

Meanwhile, the common error area includes error cause (errorCause) and error type (errorType). Here, the error cause indicates the part of the message where the error occurred. That is, it indicates whether it is a message header, a message body, or a segmented message, as in the conventional LPP.

An error type contains the cause of the error and can contain the following elements:

- decodingError: Decoding error

- invalidType: Invalid message type received (a message that does not match the current procedure is received in the same transaction)

- differentType: Receive segment messages of different message types.

- notSupportedCapability: Receiving a message containing unsupported information.

- wrongUEType: Received message corresponding to wrong UE type

Here, the reception of a message corresponding to wrongUEType is a case where a message that does not match the UE type is received. For example, when SL-PRS configuration (assistance data) data is transmitted to the server UE. Meanwhile, the above-described error cause is only an example and may be added.

Error types can be defined as ENUMERATED or BIT STRING.

Tables 5 and 6 below illustrate common error areas (commonIEsError) of SLPP error messages proposed in the present disclosure. In particular, Table 5 illustrates a case where the error type is defined in the ENUMERATED format, and Table 6 illustrates a case where the error type is defined in the BIT STRING format.

When an error type is defined in the ENUMERATED format as in Table 5, a specific error type is specified in the same way as the conventional LPP message. On the other hand, when an error type is defined in the BIT STRING format as in Table 6, multiple error types can be notified at once even if they occur.

In addition, the SLPP error message of the present disclosure may include the ID information of the UE. Accordingly, if the error cause and type are different for each message received from multiple UEs, they can be designated differently for each UE. On the other hand, if the SLPP error message is applied commonly (i.e., the same error message is transmitted to all UEs receiving the error message), the UE ID is omitted or notified as an argument corresponding to the information that it is a common UE.

-- ASN1START CommonIEsError ::= SEQUENCE (SIZE (1..UE)) OF CommonIEsErrorIE CommonIEsErrorIE ::= SEQUENCE { UE-ID UserIdentity OPTIONAL, -- Need ON, errorCause ENUMERATED { undefined, slppMessageHeaderError, slppMessageBodyError, ..., slppSegmentationError-v1450 } errorType ENUMERATED { undefined (0), decodingError (1), invalidType (2), differentType (3), notSupportedCapability (4), wrongUEType (5), } (SIZE (1..8)), ... } -- ASN1STOP

-- ASN1START CommonIEsError ::= SEQUENCE (SIZE (1..UE)) OF CommonIEsErrorIE CommonIEsErrorIE ::= SEQUENCE { UE-ID UserIdentity OPTIONAL, -- Need ON, errorCause ENUMERATED { undefined, slppMessageHeaderError, slppMessageBodyError, ..., slppSegmentationError-v1450 } errorType BIT STRING { undefined (0), decodingError (1), invalidType (2), differentType (3), notSupportedCapability (4), wrongUEType (5), } (SIZE (1..8)), ... } -- ASN1STOP

Additionally, Table 7 below proposes standard definitions of the error causes and error types defined in Tables 6 and 7 above.

errorCause This IE defines the cause for an error. ' slppMessageHeaderError ' and ' slppMessageBodyError ' is used if a receiver is able to detect a coding error in the SLPP header (ie, in the common fields) and SLPP message body, respectively. ' slppSegmentationError ' is used if a receiver detects an error in SLPP message segmentation.

errorType This IE defines the type for an error. 'decodingError' is used if a receiver is able to detect a decoding error in the SLPP header and/or SLPP message body. 'invalidType' is used if a receiver is able to detect that the message type is invalid for the current state of the procedure. 'differentType' is used if the message includes the IE SegmentationInfo and if the message type is different to the stored message type for this session and SLPP-TransactionID. 'wrongUEType' is used if a receiver is able to detect that the message type is wrong for the UE type (eg Target/Anchor/Server UE).

Meanwhile, individual error areas contain errorMethod, errorMode, and errorCase.

Specifically, errorMethod refers to the currently operating sidelink positioning method, such as SL-TDOA, SL-AOD, and SL-RTT.

Additionally, errorMode indicates the currently operating sidelink positioning mode, such as UE-based positioning mode and/or UE-assisted positioning mode.

Additionally, errorCase indicates an error case that occurred in the currently operating sidelink positioning method and sidelink positioning mode, and can be defined in the form of ENUMERATED or BIT STRING.

When defined in ENUMERATED format, it specifies a specific error case, just like the conventional LPP. On the other hand, when defined in BIT STRING format, it can notify multiple error cases at once when multiple error cases occur.

Additionally, the dedicatedIEsError section is defined in SEQUENCE format, allowing error information for multiple sidelink positioning methods and sidelink positioning modes to be transmitted through a single error message.

Preferably, it may include the ID information of the UE. Accordingly, if errorMethod, errorMode and errorCase are different for each message received from multiple UEs, they can be designated differently for each UE. If it is applied commonly to UEs (i.e., if it is applied commonly to all UEs receiving the error message), the UE ID is omitted or notified as an argument corresponding to the information of the common UE.

Table 8 below illustrates the individual error fields (dedicatedIEsError) of the SLPP error messages proposed in this disclosure.

-- ASN1START DedicatedIEsError ::= SEQUENCE (SIZE (1..UE)) OF DedicatedIEsErrorIE DedicatedIEsErrorIE ::= SEQUENCE { errorMethod ENUMERATED { undefined, SL-DL-TDOA, SL-UL-TDOA, SL-DL-AOA, SL-UL-AOA, SL-singleSide-RTT, SL-dualSide-RTT, ..., } errorMode ENUMERATED { undefined, UE-based, UE-assisted, UE-based and UE-assisted, ..., } errorCase BIT STRING { undefined (0), notSupportedMethod (1), notSupportedMode (2), assistanceDataNotSupported (3), assistanceDataSupportedButCurrentlyNotAvailable(4), notProvidedAssistanceDataNotSupported(5); assistance-data-missing (6), sl-prs-configuration-missing (7), unableToMeasureSL-PRS (8), unableToTransmit-sl-prs (9), attemptedButUnableToMeasureSomeSL-PRS(10), thereWereNotEnoughSignalsReceived(11), locationCalculationAssistanceDataMissing(12); ..., } (SIZE (1..16)), } -- ASN1STOP

Additionally, Table 9 below proposes standard definitions of the error causes and error types defined in Tables 6 and 7 above.

errorMethod This IE defines the not supported sidelink positioning method for an error. This IE is available if errorType is ‘notSupportedCapability”. It may be used to provide sidelink positioning specific error reason for each sidelink positioning method.

errorMode This IE defines the sidelink positioning mode, ie UE-based and/or UE-assisted.

errorCase This IE defines the case for an error for the ongoing sidelink positioning method and mode.

FIG. 22 illustrates an example of transmitting a positioning error message according to the prior art, and FIG. 23 illustrates an example of transmitting a positioning error message according to the present disclosure.

In particular, FIGS. 22 and 23 assume that UE B and UE C perform error processing for Request Assistance Data for different positioning methods.

Referring to FIG. 22, UE A transmits ProvideAssistanceData regarding SL-TDOA error to UE B in a unicast, and also UE A transmits ProvideAssistanceData regarding SL-RTT error to UE C in a unicast. That is, different messages must be generated and error messages must be transmitted individually.

On the other hand, referring to FIG. 23, it is possible to include information about both SL-RTT error and SL-TDOA error in the SLPP error message according to the present disclosure and transmit it in the form of groupcast.

The proposed extended SLPP error message in this disclosure enables the transmitter to more accurately identify the cause of the error at the receiver. This allows for more effective handling of errors by (re)transmitting a message with the error corrected, thereby reducing signaling overhead due to improper message transmission and time delay due to retransmission of the corrected message later.

The extended SLPP error message proposed in this disclosure can reduce signaling overhead and time delay by conveying multiple error information as a single integrated error message.

The above embodiment is an example and can be used in various cases where an error message is transmitted to multiple UEs in an integrated manner, and moreover, the cause of a more accurate error can be explicitly notified. The present disclosure is a technology for an SLPP error message used in sidelink positioning, but it is also a technology applicable to an LPP error message used in Uu-based positioning.

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

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.

It is also possible to construct an embodiment 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 obvious that claims that do not have an explicit citation relationship in the scope of the patent may be combined to construct an embodiment, or may be included as a new claim by amendment after filing.

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. Accordingly, the above detailed description should not be construed as limiting in all respects but should be considered as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all changes within the equivalent scope of the present disclosure are intended to be included in the scope of the present disclosure.

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

Claims (12)

1. A method performed by a UE (User Equipment) in a wireless communication system,

   A step of receiving a positioning protocol message from at least one peer UE;

   A step of verifying at least one positioning protocol message;

   generating a positioning protocol error message based on an error in at least one of the positioning protocol messages; and

   comprising a step of transmitting the above positioning protocol error message,

   The above positioning protocol error message is,

   Containing information about at least one error that occurred during validation of at least one positioning protocol message;

   method.
2. In paragraph 1,

   The above positioning protocol error message includes at least one of common error information and positioning method specific error information.

   method.
3. In paragraph 1,

   Information about at least one of the above errors,

   Information about the area in which at least one error occurred in the header of the positioning protocol message or the body of the positioning protocol message; and

   Containing information about at least one type of error,

   method.
4. In paragraph 1,

   Based on the above peer UE being multiple, the positioning protocol error message is groupcast to the multiple peer UEs.

   method.
5. In paragraph 4,

   The information about the at least one error included in the positioning protocol error message includes information about the corresponding peer UE.

   method.
6. As a UE (User equipment) in a wireless communication system,

   At least one transceiver;

   at least one processor; and

   At least one computer memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations, said operations comprising:

   A step of receiving a positioning protocol message from at least one peer UE;

   A step of verifying at least one positioning protocol message;

   generating a positioning protocol error message based on an error in at least one of the positioning protocol messages; and

   comprising a step of transmitting the above positioning protocol error message,

   The above positioning protocol error message is,

   Containing information about at least one error that occurred during validation of at least one positioning protocol message;

   UE.
7. In paragraph 6,

   The above positioning protocol error message includes at least one of common error information and positioning method specific error information.

   UE.
8. In paragraph 6,

   Information about at least one of the above errors,

   Information about the area in which at least one error occurred in the header of the positioning protocol message or the body of the positioning protocol message; and

   Containing information about at least one type of error,

   UE.
9. In Article 8,

   Based on the above peer UE being multiple, the positioning protocol error message is groupcast to the multiple peer UEs.

   UE.
10. In Article 9,

    The information about the at least one error included in the positioning protocol error message includes information about the corresponding peer UE.

    UE.
11. In a processing device in a wireless communication system,

    at least one processor; and

    At least one computer memory operably connected 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), said operations comprising:

    A step of receiving a positioning protocol message from at least one peer UE;

    A step of verifying at least one positioning protocol message;

    generating a positioning protocol error message based on an error in at least one of the positioning protocol messages; and

    comprising a step of transmitting the above positioning protocol error message,

    The above positioning protocol error message is,

    Containing information about at least one error that occurred during validation of at least one positioning protocol message;

    Processing unit.
12. In a computer-readable storage medium,

    The above 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 operations comprising:

    A step of receiving a positioning protocol message from at least one peer UE;

    A step of verifying at least one positioning protocol message;

    generating a positioning protocol error message based on an error in at least one of the positioning protocol messages; and

    comprising a step of transmitting the above positioning protocol error message,

    The above positioning protocol error message is,

    Containing information about at least one error that occurred during validation of at least one positioning protocol message;

    Storage medium.

Images