Method and apparatus for performing sidelink positioning within base station service range in wireless communication system

Abstract

The present disclosure relates to a communication technology that fuses an IoT technology with a 5G communication system for supporting a higher data transmission rate than a 4G system, and a system therefor. The present disclosure may be applied to intelligent services (e.g., smart home, smart building, smart city, smart car or connected car, health care, digital education, retail business, security and safety-related services, etc.) based on the 5G communication technology and the IoT-related technology.

Description

Technical Field

[0001] The present disclosure relates to a method and apparatus for providing a sidelink positioning service in a mobile communication system. Background Art

[0002] In order to meet the demand for wireless data services that have grown since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi-5G communication systems. Therefore, 5G or quasi-5G communication systems are also referred to as "super 4G network" communication systems or "post-LTE systems". 5G communication systems are considered to be implemented in higher frequency (millimeter wave (mmWave)) bands (e.g., 60GHz bands) to achieve higher data rates. In order to reduce the path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming and massive antenna technology are discussed in 5G communication systems. In addition, in 5G communication systems, development of system network improvements is being carried out based on evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, coordinated multipoint (CoMP), reception interference elimination, etc. In addition, in 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coding modulation (ACM) schemes, and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies have been developed.

[0003] Meanwhile, the Internet has evolved from a human-centered connected network through which humans generate and consume information to an Internet of Things (IoT) network that sends / receives information between distributed components such as things and processes information. Internet of Everything (IoE) technology has also emerged, in which big data processing technology, etc. are combined with IoT technology through connection with cloud servers, etc. In order to realize IoT, technical elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology have been used. Recently, technologies such as sensor networks, machine-to-machine (M2M), and machine type communication (MTC) for connecting between things have been studied. In the IoT environment, smart Internet technology (IT) services that create new value in human life by collecting and analyzing data generated in connected things can be provided. By integrating and combining existing information technology (IT) with various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] Therefore, various attempts have been made to apply 5G communication systems to IoT networks. For example, 5G communication technologies such as sensor networks, machine-to-machine (M2M), and machine-type communications (MTC) have been implemented through technologies such as beamforming, MIMO, and array antennas. The application of cloud radio access networks (cloud RANs), which are big data processing technologies described above, can also be considered as an example of the fusion of 5G technology and IoT technology.

[0005] Meanwhile, in the 3GPP 5G system (5GS), it is necessary to define a method for a terminal within a communication range of a base station to perform side link positioning. Summary of the invention

[0006] Technical issues

[0007] An object of the present disclosure is to provide an apparatus and method capable of efficiently providing a service in a next generation wireless communication system.

[0008] Solution to the problem

[0009] In order to solve the above-mentioned problem, a method of a base station in an example communication system according to the present disclosure may include: obtaining a request message requesting a configuration for transmission of a sidelink positioning reference signal (SL-PRS); determining a configuration for transmission of the SL-PRS based on a parameter indicating requirements related to transmission of the SL-PRS included in the request message; and sending a configuration message including the determined configuration for transmission of the SL-PRS to a terminal performing a sidelink positioning operation, wherein the terminal performing the sidelink positioning operation may include at least one of a target terminal and an anchor terminal.

[0010] In addition, a method for a terminal in an example communication system according to the present disclosure may include: sending a request message to a base station requesting a configuration for transmission of a sidelink positioning reference signal (SL-PRS); and receiving a configuration message including a configuration for transmission of the SL-PRS based on the request message from the base station, wherein the request message may include parameters indicating requirements related to the transmission of the SL-PRS, and the terminal may be a target terminal or an anchor terminal for performing a sidelink positioning operation.

[0011] In addition, a method of a location management function (LMF) entity in an example communication system according to the present disclosure may include: confirming requirements related to the transmission of a side link positioning reference signal (SL-PRS); sending a request message to a base station requesting a configuration for the transmission of the SL-PRS, wherein the request message includes parameters indicating requirements related to the transmission of the SL-PRS; and obtaining a configuration for the transmission of the SL-PRS based on the request message.

[0012] In addition, a base station in an example communication system according to the present disclosure may include: a transceiver; and a controller, controlling the transceiver to obtain a request message requesting a configuration for transmission of a sidelink positioning reference signal (SL-PRS), determining a configuration for transmission of the SL-PRS based on parameters indicating requirements related to transmission of the SL-PRS included in the request message, and sending a configuration message including the determined configuration for transmission of the SL-PRS to a terminal performing a sidelink positioning operation, wherein the terminal performing the sidelink positioning operation may include at least one of a target terminal and an anchor terminal.

[0013] In addition, a terminal in an example communication system according to the present disclosure may include a transceiver; and a controller, controlling the transceiver to send a request message to a base station requesting a configuration for transmission of a sidelink positioning reference signal (SL-PRS), and receiving a configuration message including a configuration for transmission of the SL-PRS based on the request message from the base station, wherein the request message may include parameters indicating requirements related to the transmission of the SL-PRS, and the terminal may be a target terminal or an anchor terminal for performing a sidelink positioning operation.

[0014] In addition, a location management function (LMF) entity in an example communication system according to the present disclosure may include: a communication unit; and a controller, controlling the communication unit to confirm requirements related to the transmission of a side link positioning reference signal (SL-PRS) and to send a request message to a base station requesting a configuration for the transmission of the SL-PRS, and to obtain a configuration for the transmission of the SL-PRS based on the request message, wherein the request message may include parameters indicating requirements related to the transmission of the SL-PRS.

[0015] Advantageous Effects of the Invention

[0016] According to the device and method proposed in the present disclosure, services can be effectively provided in the next generation wireless communication system. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 is a diagram showing the structure of an NR system according to an embodiment of the present disclosure.

[0018] Figure 2 is a diagram illustrating a wireless protocol structure in an LTE and NR system according to an embodiment of the present disclosure.

[0019] Figure 3 is a diagram illustrating a network structure for providing a UE location estimation service (LCS) in a next generation mobile communication system according to an embodiment of the present disclosure.

[0020] Figure 4is a flowchart of a process for performing LCS in a next generation mobile communication system according to an embodiment of the present disclosure.

[0021] Figure 5 is a flowchart of a detailed LTE Positioning Protocol (LPP) message exchange process in a UE procedure according to an embodiment of the present disclosure.

[0022] Figure 6 is a diagram illustrating an SL-P service scenario according to an embodiment of the present disclosure.

[0023] Figure 7 is a flowchart for explaining the operation of option 1-1 based on the IC scenario according to an embodiment of the present disclosure.

[0024] Figure 8 is a flowchart for explaining the operation of option 1-2 based on the IC scenario according to an embodiment of the present disclosure.

[0025] Fig. 9 is a flowchart for explaining the operation of Option 2 based on the IC scenario according to one embodiment of the present disclosure.

[0026] Fig.10 is a flowchart of a process of selecting and sending necessary SL resources in a Mode 2 scheme when a UE has no latency requirement for SL-P transmission according to an embodiment of the present disclosure.

[0027] Fig.11 is a flowchart of a process of selecting and sending necessary SL resources in a Mode 2 scheme when a UE has a latency requirement for SL-P transmission according to an embodiment of the present disclosure.

[0028] Fig.12 is a diagram illustrating a UE device according to an embodiment of the present disclosure.

[0029] Fig.13 is a diagram illustrating a base station device according to an embodiment of the present disclosure.

[0030] Fig.14 is a block diagram of the structure of an LMF entity according to an example of the present disclosure. DETAILED DESCRIPTION

[0031] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In addition, when it is determined that a detailed description of a known function or configuration related to the present disclosure may obscure the present disclosure, a detailed description thereof will be omitted. In addition, the following terms are defined in consideration of the functions in the present disclosure and may be interpreted in different ways by the intention or practice of the user and operator. Therefore, their definitions should be interpreted based on the content in the entire specification.

[0032] By referring to the embodiments described in detail below in conjunction with the accompanying drawings, the advantages and features of the present disclosure and the ways to achieve them will be apparent. However, the present disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided only to fully disclose the present disclosure and inform those skilled in the art of the scope of the present disclosure, and the present disclosure is limited only by the scope of the attached claims. Throughout the specification, the same or similar reference numerals represent the same or similar elements.

[0033] In this article, it will be understood that each box of the flowchart diagram and the combination of boxes in the flowchart diagram can be implemented by computer program instructions. These computer program instructions can be loaded onto a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the instructions executed by the processor of the computer or other programmable data processing device create a component for implementing the function specified in the (multiple) flowchart box. These computer program instructions can also be stored in a computer-usable or computer-readable memory, wherein the computer-usable or computer-readable memory can instruct the computer or other programmable data processing device to implement the function in a particular manner, so that the instructions stored in the computer-usable or computer-readable memory produce an article of instruction components including the functions specified in the (multiple) flowchart box. The computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operating steps are performed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in the (multiple) flowchart box.

[0034] In addition, each box can represent a module, a fragment or a part of a code, which includes one or more executable instructions for implementing a specified (multiple) logical function. It should also be noted that in some alternative implementations, the functions mentioned in the box may not occur in order. For example, two boxes shown in succession can actually be performed substantially simultaneously, or boxes can sometimes be performed in reverse order, depending on the corresponding function.

[0035] As used herein, "~ unit" indicates a software element or hardware element that performs a predetermined function, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). However, "~ unit" does not always have a meaning limited to software or hardware. "~ unit" can be constructed to be stored in an addressable storage medium or to execute one or more processors. Therefore, "~ unit" includes, for example, elements, such as software elements, object-oriented software elements, class elements and task elements, processes, functions, attributes, processes, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays and parameters. The elements and functions provided by "~ unit" can be combined into a smaller number of elements and "~ unit", or divided into a larger number of elements and "~ unit". In addition, elements and "~ unit" can be implemented as one or more CPUs in a reproduction device or a secure multimedia card. In addition, in an embodiment, "~ unit" can include one or more processors.

[0036] In the following description of the present disclosure, a detailed description of known functions or configurations incorporated herein will be omitted if it is determined that the description may make the subject matter of the present disclosure unnecessarily unclear. Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0037] In the following description, for the sake of convenience, terms for identifying access nodes, terms indicating network entities, terms indicating messages, terms indicating interfaces between network entities, terms indicating various identification information, etc. are illustratively used. Therefore, the present disclosure is not limited to the terms used below, and other terms indicating objects with equivalent technical meanings may be used.

[0038] In the following description, physical channels and signals may be used interchangeably with data or control signals. For example, a physical downlink shared channel (PDSCH) is a term indicating a physical channel through which data is transmitted, but PDSCH may be used to indicate data. That is, in the present disclosure, the expression "transmitting a physical channel" may be interpreted as the expression "transmitting data or a signal through a physical channel".

[0039] In the present disclosure, higher signaling (higher layer) indicates a signal transmission method for a base station to send a signal to a terminal by using a downlink data channel of a physical layer or for a terminal to send a signal to a base station by using an uplink data channel of a physical layer. Higher signaling can be understood as radio resource control (RRC) signaling or media access control (MAC) control element (CE).

[0040] Hereinafter, for ease of description, the present disclosure uses terms and names defined in the 3rd Generation Partnership Project (3GPP) New Radio (NR) or 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) standards. However, the present disclosure is not limited by the terms and names and can be equally applied to systems conforming to other standards. In the present disclosure, gNB can be used interchangeably with eNB for ease of description. That is, a base station described as an eNB can indicate a gNB. In addition, a terminal can indicate a mobile phone, an MTC device, an NB-IoT device, a sensor, or other wireless communication devices.

[0041] Thereafter, the base station that performs resource allocation of the terminal may be at least one of, but not limited to, a gNodeB (gNB), an eNodeB (eNB), a NodeB, a base station (BS), a radio access unit, a base station controller, and a node on a network. The terminal may include, but is not limited to, a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system for performing a communication function.

[0042] The present disclosure relates to a method and apparatus for performing side link (SL) positioning in a mobile communication system. More specifically, the present disclosure relates to a method and apparatus for performing side link positioning (SL-P) by a UE within a base station communication range in 3GPP 5GS.

[0043] The present disclosure describes the signaling methods and procedures with the network required for a UE within the communication range of a base station to perform SL-P. To this end, specifically, UE capability information, transmission resource configuration information, etc. related to SL-P are newly defined. In addition, a method for allocating transmission resources required to perform sidelink positioning to a UE is described. To this end, when SL transmission resource configuration mode 1 is used, a method for the base station to allocate necessary sidelink transmission resources to the UE according to requests from the LMF and the UE will be described. In the case where mode 2 is used for SL transmission resource configuration, a method for the base station to configure a resource pool for SL-P according to a request from the LMF, and a method for the UE to determine the transmission resources for SL-P in a given resource pool according to the mode 2 scheme will be described.

[0044] Through the present disclosure, the network can instruct UEs within the communication range of the base station to perform SL-P. The location management function (LMF) can exchange SL-P related UE capability information with the UE for the SL-P service, and instruct the UE on sidelink positioning related operations. In the case where the UE needs to perform SL transmission for SL-P, the LMF can participate in configuring SL transmission resources.

[0045] For example, in the case where the mode 1 resource configuration scheme is used for SL-P, the LMF and / or the UE may request the base station to configure the transmission resources of the UE for SL-P, and the base station may configure the SL transmission resources to the UE according to the request of the LMF and the UE. In addition, for example, in the case where the mode 2 resource configuration scheme is used for SL-P, the LMF may request the base station to configure the transmission resource pool of the UE for SL-P, and the base station may allocate the transmission resource pool for SL-P to the UE according to the request of the LMF.

[0046] For example, in the case where the mode 1 resource configuration scheme is used for SL-P, the base station can configure the UE to send a side link positioning reference signal (SL-PRS). In addition, for example, in the case where the mode 2 resource configuration scheme is used for SL-P, the LMF can configure the UE to send the SL-PRS. The UE can send the SL-PRS according to the base station and LMF configuration.

[0047] In the above description, when SL resource configuration mode 1 and SL resource configuration mode 2 are used, the content described for each is used to explain a general use example, and the corresponding operation does not need to be limited to each mode. For example, when the mode 2 resource configuration scheme is used, it is also possible for the base station to configure the SL-PRS transmission configuration of the UE instead of the LMF.

[0048] The terms used in this disclosure can be defined as follows.

[0049] -Sidelink Positioning (SL-P):

[0050] The position estimation of the UE is performed using the reference signal sent on the SL. In this case, the position of the UE can be absolute positioning information, relative positioning information, and ranging information (e.g., distance / direction information relative to another UE). Ranging operations (estimation of distance / direction / relative position between UEs) can be included in the SL-P concept.

[0051] - Target UE: UE that is the target of position estimation.

[0052] -Anchor UE: A UE that helps estimate the location of a target UE. (For example, a UE that sends and receives a reference signal for estimating the location of a target UE, a UE that transmits information necessary for location estimation to a target UE via a SL, etc.)

[0053] Figure 1 is a diagram showing the structure of an NR system according to an embodiment of the present disclosure.

[0054] refer to Figure 1, the wireless communication system may be composed of a plurality of base stations (e.g., gNB 105, ng-eNB 110, ng-eNB 115, gNB 120), an access and mobility management function (AMF) 125, and a user plane function (UPF) 130. A user terminal (user equipment, UE, or terminal) 135 may access an external network through the base station (e.g., gNB 105, ng-eNB 110, ng-eNB 115, gNB 120) and UPF 130.

[0055] exist Figure 1 In the present invention, the base station (e.g., gNB 105, ng-eNB 110, ng-eNB 115, gNB 120) is an access node of the cellular network and can provide wireless access to the UE accessing the network. That is, in order to serve the user's business, the base station (e.g., gNB 105, ng-eNB 110, ng-eNB 115, gNB120) can collect and schedule the UE's status information, such as the buffer status, the available transmission power status, and the channel status, so as to support the connection between the UE and the core network (CN) (e.g., in the case of CN of NR, 5GC). At the same time, the user plane (UP) related to the transmission of actual user data in the communication and the control plane (CP) related to the connection management can be separately constructed. In this figure, it is shown that gNB 105 and gNB 120 use UP and CP technologies defined in new radio (NR) technology, and ng-eNB 110 and ng-eNB 115 use UP and CP technologies defined in long term evolution (LTE) technology even when connected to 5GC.

[0056] The AMF 125 is a device responsible for various control functions of the UE and a mobility management function and connected to a plurality of base stations, and the UPF 130 may mean a type of gateway device that provides data transmission. Figure 1 , but the NR wireless communication system may include a session management function (SMF). The SMF can manage packet data network connections provided to the UE, such as protocol data unit (PDU) sessions.

[0057] Figure 2 is a diagram illustrating a radio protocol structure in an LTE and NR system according to an embodiment of the present disclosure.

[0058] refer to Figure 2In both the UE and the eNB, the wireless protocol of the LTE system may be composed of a packet data convergence protocol (PDCP) 205 and 240, a radio link control (RLC) 210 and 235, and a medium access control (MAC) 215 and 230. The packet data convergence protocol 105 and 140 is responsible for operations such as Internet Protocol (IP) header compression / recovery, and the radio link control (hereinafter referred to as RLC) 210 and 235 reconstructs the PDCP protocol data unit (PDU) in an appropriate size. The MAC 215 and 230 are connected to a plurality of RLC layer devices constituted in one UE, and perform operations of multiplexing the RLC PDU to the MAC PDU and demultiplexing the RLC PDU from the MAC PDU. The physical (PHY) layers 220 and 225 channel encode and modulate higher layer data, convert the higher layer data into orthogonal frequency division multiplexing (OFDM) symbols, and transmit the OFDM symbols through a radio channel, or demodulate and channel decode the OFDM symbols received through the radio channel, and deliver the OFDM symbols to a higher layer. In addition, hybrid automatic repeat request (HARQ) is used for additional error correction in the physical layer, and the receiving end sends 1 bit about whether the packet sent by the transmitting end has been received. This is called HARQ confirmation (ACK) / negative ACK (NACK) information. In the case of LTE, downlink HARQ ACK / NACK information for uplink data transmission is sent through a physical channel (physical hybrid ARQ indicator channel (PHICH)). In the case of NR, whether retransmission is necessary or whether new transmission can be performed can be determined by the scheduling information of the corresponding UE on the physical dedicated control channel (PDCCH), where PDCCH is a channel through which downlink / uplink resource allocation, etc. is sent. This is because NR applies asynchronous HARQ. Uplink HARQ ACK / NACK information for downlink data transmission may be transmitted through a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) physical channel. PUCCH is usually transmitted on the uplink of a primary cell (PCell) described later, but if the UE supports it, the base station may additionally transmit PUCCH to the corresponding UE on a secondary cell (SCell) described later, and the SCell on which PUCCH is transmitted in this way is called a PUCCH SCell.

[0059] Although not shown in the drawing, a radio resource control (RRC) layer exists above the PDCP layer of each of the UE and the base station, and access and measurement-related configuration control messages may be transmitted and received through the RRC layer in order to control radio resources.

[0060] Meanwhile, the physical (PHY) layer may be formed of one or more frequencies / carriers, and a technique for simultaneously configuring and using multiple frequencies is called carrier aggregation (CA). CA technology uses a primary carrier and one or more secondary subcarriers to significantly increase the amount of transmission by the number of secondary subcarriers, rather than using only one carrier for communication between a terminal (UE) and a base station (E-UTRAN NodeB, eNB). Meanwhile, in LTE, a cell in a base station using a primary carrier is called a primary cell or primary cell (PCell), and a cell in a base station using a subcarrier is called a subcell or secondary cell (SCell).

[0061] Figure 3 is a diagram showing a network structure for providing a UE location estimation service (LoCation service, LCS) in a next generation mobile communication system according to an embodiment of the present disclosure.

[0062] refer to Figure 3 , a network for providing LCS in a next generation mobile communication system is composed of a UE 300, a base station (NG-RAN node) 305, an access and mobility management function (AMF) 310, and a location management function (LMF) 315. In this case, the UE 300 communicates with the LMF 315 through the base station 305 and the AMF 310, and exchanges information necessary for location estimation. The role of each component for providing LCS is as follows.

[0063] UE 300 may perform the role of measuring wireless signals necessary for location estimation and sending the results to LMF 115 .

[0064] The base station 305 may perform the role of transmitting downlink wireless signals necessary for position estimation to the UE, measuring uplink wireless signals transmitted by the target UE, and the like.

[0065] After receiving the LCS request message from the LCS requester (LCS client), the AMF 310 may perform the role of instructing the provision of the location providing service by delivering it to the LMF 315. In addition, when the LMF 315 processes the location estimation request and then sends a response to the location estimation result of the UE, the AMF 310 may transmit the corresponding result to the LCS requester.

[0066] LMF 315 is a device that receives and processes LCS requests from AMF 110, and can perform the role of controlling the overall process required for position estimation. For UE position estimation, LMF 315 provides auxiliary information required for position estimation and signal measurement to UE 300, and obtains the result value from the corresponding UE. In this case, the LTE Positioning Protocol (LPP) can be used as a protocol for data exchange. LPP can define the message standards exchanged between UE 300 and LMF 315 for position estimation services. In addition, LMF 315 can exchange configuration information of downlink reference signals (positioning reference signals, PRS) and measurement results of uplink reference signals (sounding reference signals, SRS) to be used for position estimation with the base station 305. In this case, NR Positioning Protocol A (NRPPa) can be used as a protocol for data exchange, and NRPPa can define the message standards exchanged between the base station 305 and LMF315.

[0067] Figure 4 is a flowchart of a process of performing LCS in a next generation mobile communication system according to an embodiment of the present disclosure.

[0068] refer to Figure 4 , after obtaining the LCS request S400a / S400b / S400c, the AMF 405 may transmit the LCS request to the LMF 407. Thereafter, the LMF 407 may control a process of exchanging required information with the UE and the base station to process the LCS request S400a / S400b / S400c transmitted from the AMF 405, and transmit a result value (position estimation result) to the AMF 405. The execution of the LCS may be completed by the AMF 405 transmitting the result value transmitted from the LMF 407 to the target (LCS client) that has requested the LCS.

[0069] There are 3 types of LCS requests, which are obtained by AMF 105 in S400a, S400b and S400c operations.

[0070] 1. LCS request received from external LCS client 110 S400a

[0071] 2. LCS request S400b generated by AMF105 itself

[0072] 3. LCS request received from UE 100 S400c

[0073] The LCS request may include an identification (ID) of the LCS target UE and LCS quality of service (QoS) request information (eg, requirements on location estimation accuracy and latency).

[0074] After obtaining one of the three types of LCS requests, the AMF 405 may request the LMF 407 to provide a location estimation service by sending a location service request message S405. Thereafter, in the NG-RAN node procedure operation S410, the LMF 407 may perform a procedure required for location estimation (e.g., configuring a PRS to a base station, obtaining SRS measurement information from a base station, etc.) via an NRPPa message exchange with the NG-RAN node 403.

[0075] In addition, in UE procedure operation S415, LMF 407 may exchange LPP messages to exchange required information with UE 400. Through the above process, LMF 407 may perform corresponding procedures such as exchanging UE capability information related to position estimation, delivering auxiliary information for UE signal measurement, requesting UE measurement results, and obtaining UE measurement results. In this regard, reference will be made later to Figure 5 Provide a more detailed description.

[0076] When LMF 407 determines the estimated location of the UE based on the various measurement results obtained, LMF 407 may deliver a location service response message S420 to AMF 405. AMF 405 may transmit an LCS response message S425a / S425b / S425c to a target that has requested LCS, and herein, the LCS response message S425a / S425b / S425c may include the UE location estimation result.

[0077] Figure 5 is a flowchart of a process of exchanging detailed LPP messages in a UE procedure according to an embodiment of the present disclosure.

[0078] refer to Figure 5 , the UE procedure according to the embodiment of the present disclosure may include the following procedures: the LMF 505 exchanges UE capability information related to position estimation with the UE 500, delivers auxiliary information for signal measurement of the UE, requests and obtains UE measurement results, etc. The use and definition of each LPP message sent and received at each operation are as follows.

[0079] LPP request capability (LMF→UE, S510)

[0080] : A message that can be used by the LMF 505 to request UE capability information related to position estimation from the UE 500. The information included in the message can be defined as shown in Table 1 below. Referring to Table 1, a request for common information regardless of a position estimation method (e.g., Global Navigation Satellite System (GNSS), Observed Time Difference of Arrival (OTDOA), Enhanced Cell ID (ECID), etc.) is included in CommonIEsRequestCapabilities, and a request for additional required information for each position estimation method can be included in a separate information element (IE) for each scheme.

[0081] [Table 1]

[0082]

[0083] LPP provides capabilities (UE→LMF, S515)

[0084] : A message that can be used by the UE 500 to transmit UE capability information requested from the LMF 505. The information included in the message can be defined as shown in the following Table 2. Referring to Table 2, similar to the LPP request capabilities message, common information regardless of the location estimation method can be included in commonIEsProvideCapabilities, and information requested for each location estimation method can be included in a separate IE.

[0085] [Table 2]

[0086]

[0087]

[0088] LPP provides auxiliary data (LMF→UE, S520)

[0089] : A message that can be used to enable the LMF 505 to provide information necessary or helpful for the UE 500 to perform radio signal measurements for position estimation. The information included in the corresponding message can be defined as shown in Table 3 below.

[0090] [Table 3]

[0091]

[0092] LPP requests location information (LMF→UE, S525)

[0093] : A message that can be used by LMF 505 to request UE 500 to measure signals required for location estimation and request a location estimation result. After determining which location estimation method will be used, what measurements the UE should perform for the location estimation method, what results and how to respond, etc., LMF 505 can send relevant information to UE 500 by including the relevant information in this message. The information included in the corresponding message can be defined as shown in Table 4 below.

[0094] [Table 4]

[0095]

[0096] LPP provides location information (UE→LMF, S530)

[0097] : A message that can be used by the UE 500 to transmit the measurement results and position estimation results requested from the LMF 505 to the LMF 105. The information included in the corresponding message can be defined as shown in Table 5 below.

[0098] [Table 5]

[0099]

[0100] Figure 6 It is a schematic diagram of a side link positioning service scenario according to an embodiment of the present disclosure.

[0101] refer to Figure 6 , the following three SL-P scenarios can be defined depending on whether the target / anchor UE is within the communication range of the base station (i.e., the cell coverage of the base station).

[0102] - Covering inner scene 600:

[0103] This is a scenario in which both the target UE 603 ​​, which is the target of position estimation in SL-P, and the anchor UE 605 , which assists in position estimation, are within the communication range of the base station 610 .

[0104] In this case, the target UE 603 / anchor UE 605 is connected to a cell operated by the base station 610 and is in a state where it can communicate via the Uu interface. In this case, the LMF 615 can exchange LPP messages with the target UE 603 / anchor UE 605 for SL-P operation and can participate in the SL-P operation. The LPP messages between the LMF 615 and the target UE 603 / anchor UE 605 are transmitted through the Uu interface between the target UE 603 / anchor UE 605 and the base station 610.

[0105] For SL-P operation, the target UE 603 ​​may transmit and receive SL-PRS with the anchor UE 605 through the PC5 interface. In addition, the target UE 603 ​​and the anchor UE 605 may transmit and receive SL-PRS and control messages for SL-P operation through the PC5 interface. Mode 1 or Mode 2 scheme may be used as a resource configuration method for sidelink (SL) transmission of the target UE 603 / anchor UE 605.

[0106] In the case where the Mode 1 scheme is used, the base station can directly allocate SL transmission resources for SL-P operation. In this case, the SL transmission resources can be allocated from a licensed based carrier used only for SL communication (a licensed carrier dedicated to SL communication) or a licensed band carrier used for SL and uplink transmission (a licensed carrier that shares resources between SL and UL communication). The SL transmission resource configuration of the base station may include information about the time (time slot) and frequency (subchannel) domains, and in the case where the resource configuration is performed in a configured grant (Configured Grant, CG) scheme, it may also include information about the periodicity of the transmission resources. In the case where the Mode 1 resource configuration scheme is used, the LMF requests the base station to configure the SL transmission resources for performing the SL-P operation of the target UE / anchor UE (for example, sending and receiving SL-PRS and control messages through the PC5 interface), and the base station can accordingly configure the SL transmission resources to the target UE / anchor UE in the Mode 1 scheme. In addition, the LMF configures the operations required for the SL-P operation to the target UE / anchor UE, and the target UE / anchor UE can directly request the SL transmission resources required for the corresponding operation from the base station. In this case, the base station can allocate the required SL transmission resources according to the request of each UE.

[0107] In the case where the Mode 2 scheme is used, the base station can allocate a resource pool (side link resource pool) that can be used for SL transmission, and the target UE / anchor UE can directly select the transmission resources required for SL-P operation from the allocated resource pool. In this case, the LMF can transmit the requirements (e.g., frequency, bandwidth, etc.) for the SL resource pool to be used for SL-P operation to the base station. The base station can configure a new SL resource pool for the target UE / anchor UE according to the LMF request, or change the configuration of the existing configured SL resource pool.

[0108] In mode 1 and mode 2 resource configurations, a shared resource pool or a dedicated resource pool can be configured as a SL resource pool for SL-P operation. Here, using a shared SL resource pool means using a resource pool configured for SL communication purposes to transmit SL-P related information, and using a dedicated SL resource pool means using a resource pool configured solely for SL-P functions to send SL-P related information.

[0109] - Partial coverage scene 620:

[0110] In SL-P, a target UE 623 that is a target of position estimation is located outside the communication range of a base station 630 , and an anchor UE 625 that assists position estimation is located within the communication range of the base station 630 .

[0111] In this case, the anchor UE 625 is connected to a cell operated by the base station 630 and is in a state where it can communicate with the base station 630 through the Uu interface, and the target UE 623 is in a state where it can communicate with the anchor UE 625 through the SL PC5 interface. In this case, the LMF 615 can exchange LPP messages with the target UE 623 / anchor UE 625 for SL-P operation, and can participate in the SL-P operation. The LPP messages between the LMF 635 and the anchor UE 625 can be sent and received through the Uu interface with the base station 630, and the LPP messages between the LMF 635 and the target UE 623 can be exchanged through the SL relay operation of the anchor UE 625. For example, the LPP message sent by the target UE 623 to the LMF 635 can be transmitted to the anchor UE 625 through the PC5 interface, and then transmitted to the network through the Uu interface of the anchor UE 625.

[0112] For SL-P operation, the target UE 623 may transmit and receive SL-PRS through the PC5 interface with the anchor UE 625. In addition, the target UE 623 and the anchor UE 625 may transmit and receive SL-PRS and control messages for SL-P operation through the PC5 interface. Mode 1 or Mode 2 scheme may be used as a resource configuration method for sidelink transmission of the target UE 623 / anchor UE 625.

[0113] In the case where the Mode 1 scheme is used, the SL transmission resources for SL-P operation can be directly allocated by the base station. In this case, the SL transmission resources can be allocated from a licensed band carrier used only for SL communication (a licensed carrier dedicated to SL communication) or a licensed band carrier used for SL and uplink transmission (a licensed carrier that shares resources between SL and UL communication). The SL transmission resource configuration of the base station may include information about the time (time slot) and frequency (subchannel) domains, and in the case where the resource configuration is performed with a configured grant (CG) scheme, it may also include information about the periodicity of the transmission resources. In the case where the Mode 1 resource configuration scheme is used, the LMF may request the base station to configure the SL transmission resources for the SL-P operation of the target UE / anchor UE (for example, sending and receiving SL-PRS and control messages through the PC5 interface), and the base station may configure the SL transmission resources to the anchor UE in the Mode 1 scheme accordingly. In addition, the LMF may configure the operations required for the SL-P operation to the target UE / anchor UE, and the anchor UE may directly request the SL transmission resources required for the corresponding operation from the base station. In this case, the base station may allocate the required SL transmission resources according to the request of the anchor UE.

[0114] In the case where the Mode 2 scheme is used, the base station can allocate a resource pool (side link resource pool) that can be used for SL transmission, and the target UE / anchor UE can directly select the transmission resources required for SL-P operation. In this case, the LMF can transmit the requirements (e.g., frequency, bandwidth, etc.) for the SL resource pool to be used for SL-P operation to the base station. The base station can configure a new SL resource pool for the target UE / anchor UE according to the LMF request, or change the configuration of a previously configured SL resource pool.

[0115] In the resource configuration of Mode 1 and Mode 2, a shared resource pool or a dedicated resource pool can be configured as an SL resource pool for SL-P operation. Here, using a shared SL resource pool means using a resource pool configured for SL communication purposes to transmit SL-P related information, and using a dedicated SL resource pool means using a resource pool configured solely for SL-P functions to send SL-P related information.

[0116] - Covering the outer scene 640:

[0117] This is a scenario in which both the target UE 643 and the anchor UE 645, which are the targets of position estimation in SL-P, are located outside the communication range of the base station.

[0118] In this case, the target UE 643 / anchor UE 645 cannot communicate with the base station through the Uu interface, and the target UE 643 is in a state where it can only communicate with the anchor UE 645 through the SL PC5 interface. In addition, the LMF cannot exchange LPP messages with the target UE 643 / anchor UE 645 for SL-P operation, and therefore cannot directly participate in the SL-P operation. For SL-P operation, the target UE 643 can send and receive SL-PRS with the anchor UE 645 through the PC5 interface. In addition, the target UE 643 and the anchor UE 645 can send and receive control messages for the transmission and reception of SL-PRS and SL-P operation through the PC5 interface. The mode 2 scheme can be used as a resource configuration method for the sidelink transmission of the target UE 643 / anchor UE 645.

[0119] In the case where the Mode 2 scheme is used, the base station can pre-allocate a resource pool (side link resource pool) that can be used for SL transmission (for example, it can be configured when within the communication range of the base station), and the target UE 643 / anchor UE 645 can use the pre-configured resource pool to directly select the transmission resources required for SL-P operation. In this case, the LMF can transmit the requirements for the SL resource pool to be used for SL-P operation (for example, frequency, bandwidth, etc.) to the base station. The base station can configure a new SL resource pool for the target UE 643 / anchor UE 645 or change the configuration of an existing configured SL resource pool based on the LMF request. A shared resource pool or a dedicated resource pool can be configured as a SL resource pool for SL-P operation. Here, using a shared SL resource pool means using a resource pool configured for SL communication purposes to transmit SL-P related information, and using a dedicated SL resource pool means using a resource pool configured separately for SL-P functions to send SL-P related information.

[0120] Figure 7 is a flowchart for explaining the operation of option 1-1 based on a scenario within coverage according to an embodiment of the present disclosure.

[0121] More specifically, Figure 7 A process is described in which the base station allocates SL resources necessary for SL-P operation to the UE in a mode 1 scheme upon the request of the LMF, and the UE performs the SL-P operation using the allocated resources (scenario: the LMF controls the entire SL-P procedure via the Uu link with both the target UE and the anchor UE, option 1-1: [LMF-requested] SL-PRS resource allocation using mode 1 with a shared SL resource pool / dedicated SL resource pool).

[0122] refer to Figure 7, the LMF 709 may indicate the SL-P operation of the target UE 700 and the anchor UE 703 through an LPP message. In this case, SL resource configuration for the SL-P operation (e.g., SL-PRS transmission) of the target UE 700 / anchor UE 703 may be performed in the Mode 1 scheme, and the LMF 709 may request the SL transmission resource configuration and the SL-PRS transmission configuration from the serving gNB 705. The operation of each process may be described as follows.

[0123] -0. Location request (S710):

[0124] AMF 707 may start the location estimation service by sending a location request message S710 for the target UE 700 to LMF 709. The location request message may include QoS requirements for the location estimation service. In this case, in the case where the ID of the anchor UE 703 is included in the LCS service request message received by AMF 707 from the LCS client for SL-P service, the location request message S710 may also include one or more anchor UE IDs and the target UE ID. For example, the general public subscription identifier (GPSI) or subscription permanent identifier (SUPI) given in the LCS service request message may be used as the UE ID. For example, the location request message S710 for SL-P service may include requirements for SL-P (ranging operation between two or more UE pairs), requirements for delay / accuracy, etc. In addition, for example, in the case where there is UE capability information (positioning UE capability information) related to the location estimation of the target UE / anchor UE that has been ensured, AMF 707 may send it to LMF 709 via a location request.

[0125] -1. LPP capability transmission with target UE (S715):

[0126] The LMF 709 and the target UE 700 may exchange UE capability information related to position estimation through an LPP message. In this case, the LPP message exchanged between the LMF 709 and the target UE 700 may include the following UE capability information related to SL-P.

[0127] *SL-PRS Tx / Rx support

[0128] * Supported SL positioning methods (e.g. RTT-based solutions using SL, SL-AoA, SL-TDOA, SL-AoD) as anchor / target UE

[0129] *Available modes of SL positioning associated with each SL positioning method (i.e., standalone, UE-based, UE-assisted).

[0130] * Available roles for SL positioning associated with each SL positioning method (e.g., target UE, reference UE, assistant UE, positioned UE)

[0131] * Known location support

[0132] *SRC L2 ID, DST L2 ID (for SL-P unicast / multicast or broadcast)

[0133] Meanwhile, in the case where the AMF 707 provides UE capability information related to the location estimation of the target UE 700 in operation 0 (S710), the operation of operation 1 (S715) may be omitted.

[0134] -2. Determine to use SL-P and select candidate anchor UE (S720):

[0135] The LMF 709 may determine to use one of the SL-P methods (e.g., RTT-based SL-P, SL-AoA, SL-TDOA, SL-AoD, etc.) based on the UE capability information and the position estimation service requirements related to the position estimation of the target UE 700 provided from the AMF 707 in operation 0 (S710). In addition, depending on the determined SL-P method, in the event that one or more anchor UEs 703 are required, the LMF 709 may select a candidate anchor UE based on the information it previously has (e.g., a list of available anchor UE IDs, a known location of each anchor UE, a positioning capability of each anchor UE, a serving cell of each anchor UE, available SL frequency / BW, etc.).

[0136] Furthermore, additionally, in case that the location request message transmitted through operation 0 includes the anchor UE ID provided by the LCS client, the LMF 709 may select the corresponding UE as a candidate anchor UE.

[0137] -3. LPP capability transmission with candidate anchor UE (S725):

[0138] If necessary, the LMF 709 may exchange UE capability information related to position estimation required for performing SL-P with one or more candidate anchor UEs 703 via LPP messages.

[0139] -4. Determine anchor UE (S730):

[0140] The LMF 709 may determine the anchor UE to be ultimately used, the location estimation technology (e.g., RTT type solution using SL, SL-AoA, SL-TDOA, SL-AoD), the location estimation mode (i.e., independent, UE-based, UE-assisted), etc. based on the UE capability information of the candidate anchor UE 703 additionally collected in operation 3 (S725).

[0141] -5. SL-PRS Tx configuration request (S735):

[0142] The LMF 709 may request the SL-PRS transmission configuration (including transmission resource configuration) required for the SL-PRS from the serving gNB 705. In this case, considering the location estimation QoS requirements (e.g., location estimation accuracy and location estimation service latency) obtained in operation 0 (S710), the location of the target UE / anchor UE (previously known location), etc., the LMF 709 may transmit the request for the SL-PRS transmission configuration to the serving gNB 705 through the following parameters.

[0143] * Resource type (i.e., aperiodic, semi-persistent, periodic), # of SL-PRS Txs required, periodicity

[0144] *SL-PRS bandwidth / frequency

[0145] * Spatial / path loss information

[0146] *SRC L2 ID, DST L2 ID (for SL-PRS unicast / multicast / broadcast)

[0147] * Scheduling delay requirement (for example, it can be a requirement on the delay between the time when the LMF requests the SL-PRS transmission configuration and the time when the configuration of the SL-PRS transmission resources is actually performed. Alternatively, in the case where the LMF indicates the SL-PRS transmission timing, it can be a requirement on whether the SL-PRS transmission should actually be performed within a specific time offset from the corresponding timing).

[0148] *SL-PRS Tx activation / deactivation time

[0149] In this case, when there are one or more UEs that need to perform SL-PRS transmission, the above parameters can be given to each UE separately. In addition, when the serving gNB 705 of each UE is different, the LMF 709 can request SL-PRS transmission configuration from one or more gNBs in parallel.

[0150] In addition, there may be several methods for configuring SL-PRS transmission resources. Here, it is assumed that the serving gNB 705 allocates SL-PRS transmission resources in mode 1 based on the request of the LMF 709, and the SL transmission resources can be allocated to the target UE / anchor UE in a dynamic grant scheme as well as a configured grant type 1 and a configured grant type 2 scheme. When using technologies that require accurate SL-PRS transmission time (such as round-trip transmission (RTT) and arrival time difference (TDOA) schemes), and technologies that send SL-PRS once or multiple times based on a specific period, the base station can configure and allocate available resources in mode 1 in the configured grant scheme.

[0151] -6. Determine SL-PRS Tx configuration (S740):

[0152] The serving gNB 705 may determine a SL-PRS transmission configuration for SL-PRS transmission based on the request received from the LMF 809 in operation 5 (S735). The SL-PRS transmission configuration may include the following information.

[0153] *SL frequency, SL BWP, SL-PRS Tx pool (shared or dedicated)

[0154] → In case both the shared SL Tx resource pool and the SL-P dedicated Tx resource pool are configured, the UE uses the SL-P dedicated Tx resource pool by default. Alternatively, an indicator of which of the two pools to use may be included in the SL-PRS configuration.

[0155] *SL-PRS Tx resource allocation (Mode 1 with Grant Type 1 / 2 configured)

[0156] *SL-PRS Tx resource type (i.e., aperiodic, semi-persistent, periodic)

[0157] *txParameters (i.e., TxThreshIC, TxThreshOoC)

[0158] * Spatial / path loss information (this can indicate sl-SSB from anchor / target UE)

[0159] *SRC L2 ID, DST L2 ID (for SL-PRS unicast / multicast / broadcast)

[0160] *SL-PRS Tx activation / deactivation time

[0161] -7.UE SL-PRS Tx configuration (S745):

[0162] The serving gNB 705 may transmit the SL-PRS transmission configuration determined in operation 6 (S740) to one or more UEs that must perform SL-PRS transmission through an RRC message. (In the case where the RTT-based method is assumed, both the target UE 700 and the anchor UE 703 require SL-PRS transmission, but in the case where the angle of arrival (AoA) or TDOA scheme is used, SL-PRS transmission may be required only for one of the anchor UE 703 and the target UE 700)

[0163] -8. Configured SL-PRS information (S750):

[0164] The serving gNB 705 may transmit the SL-PRS transmission configuration configured for each UE to the LMF 709 via an NRPPa message.

[0165] -9.SL-PRS Tx Activation (S755):

[0166] In the case where the SL-PRS transmission resource type is aperiodic or semi-persistent, a SL-PRS transmission activation / deactivation operation may be required. The serving gNB 705 may perform the SL-PRS transmission activation operation based on the request of the LMF 709.

[0167] *9a.LMF 709 may request SL-PRS transmission activation from the serving gNB 705. In this case, a specific activation time / deactivation time may be transmitted together with the SL-PRS transmission activation request.

[0168] *9b. The serving gNB 705 may use RRC / MAC control element (CE) / downlink control information (DCI) etc. to indicate the target UE 700 / anchor UE 703 to activate SL-PRS transmission.

[0169] *9c. The serving gNB 705 may report the SL-PRS transmission activation result to the LMF 709 in response. In this case, the activation result may include information about the accurate SL-PRS transmission activation timing.

[0170] -10.LPP provides auxiliary data (S760):

[0171] The LMF 709 may transmit the SL-PRS configuration information received from the serving gNB 705 in operation 8 (S750) to the target UE 700 / anchor UE 703 through an LPP message as auxiliary data for position estimation. If the activation operation of operation 9 (S755) is performed for a non-periodic / semi-persistent resource type, the information about the activation timing obtained in operation 9c may also be included in the corresponding LPP message.

[0172] -11. LPP requests location information (S765):

[0173] LMF 709 may instruct target UE 700 / anchor UE 703 to perform necessary SL-PRS measurements and report the results through LPP messages. In this case, LMF 709 may instruct SL-PRS measurements to both target UE 700 and anchor UE 703, or only to one of them, depending on the position estimation technique used.

[0174] -12.UE SL-PRS measurement (S770):

[0175] The target UE 700 / anchor UE 703 may perform necessary SL-PRS measurement according to the instruction of the LMF 709. As described above, the measurement operation may be performed on only one of the target UE 700 / anchor UE 703 depending on the position estimation technology.

[0176] -13.LPP provides location information (S775):

[0177] The target UE 700 / anchor UE 703 may report the measurement results (the location information calculated in the case of UE-based mode) to the LMF 709. In the case of the anchor UE 703, it may additionally report information about its actual location (known location) for the absolute positioning estimation of the target UE 700.

[0178] -14. Position determination (S780):

[0179] The LMF 709 may ultimately determine the location of the target UE 700 .

[0180] -15. Position response (S785):

[0181] LMF 709 can transmit the location estimation result of the target UE 700 to AMF 707.

[0182] Figure 8 is a flowchart for explaining the operation of option 1-2 based on the IC scenario according to an embodiment of the present disclosure.

[0183] More specifically, Figure 8 A process is described in which the base station allocates SL resources necessary for SL-P operation to the UE in a mode 1 scheme upon the UE's request, and the UE performs the SL-P operation using the allocated resources (scenario: the LMF controls the entire SL-P procedure via the Uu link with both the target UE and the anchor UE, option 1-2: [UE-requested] SL-PRS resource allocation using mode 1 with a shared or dedicated SL resource pool).

[0184] refer to Figure 8 , LMF 809 may indicate the SL-P operation of the target UE 800 and the anchor UE 803 through an LPP message. In this case, SL resource configuration for the SL-P operation (e.g., SL-PRS transmission) of the target UE 800 / anchor UE 803 may be performed in the Mode 1 scheme. LMF 809 may be configured to send SL-PRS to the target UE 800 and the anchor UE 803, and the target UE 800 / anchor UE 803 may request a specific SL transmission resource configuration and SL-PRS transmission configuration from the serving gNB 805. The operation of each process may be described as follows.

[0185] -0. Location request (S810):

[0186] AMF 807 may start the location estimation service by sending a location request message S810 for the target UE 800 to LMF 809. The location request message may include QoS requirements for the location estimation service. In the case where the ID of the anchor UE 103 is included in the LCS service request message received by AMF 807 from the LCS client for SL-P service, the location request message S810 may also include one or more anchor UE IDs and the target UE ID. For example, the general public subscription identifier (GPSI) or subscription permanent identifier (SUPI) given in the LCS service request message may be used as the UE ID. For example, the location request message for the SL-P service may include requirements for SL-P (ranging operation between two or more UE pairs), requirements for delay / accuracy, etc. In addition, for example, in the case where AMF 807 has UE capability information (positioning UE capability information) related to the location estimation of the target UE / anchor UE that has been ensured, AMF 807 may send it to LMF 809 via a location request.

[0187] -1. LPP capability transmission with target UE (S815):

[0188] The LMF 809 and the target UE 800 may exchange UE capability information related to position estimation through an LPP message. In this case, the corresponding LPP message may include the following UE capability information related to SL-P.

[0189] *SL-PRS Tx / Rx support

[0190] * Supported SL positioning methods (e.g. RTT-based solutions using SL, SL-AoA, SL-TDOA, SL-AoD) as anchor / target UE

[0191] *Available modes of SL positioning associated with each SL positioning method (i.e., standalone, UE-based, UE-assisted).

[0192] * Available roles for SL positioning associated with each SL positioning method (e.g., target UE, reference UE, assistant UE, positioned UE)

[0193] * Known location support

[0194] *SRC L2 ID, DST L2 ID (for SL-P unicast / multicast or broadcast)

[0195] Meanwhile, in the case where the AMF 807 provides UE capability information related to the location estimation of the target UE 800 in operation 0 (S810), the operation of operation 1 (S815) may be omitted.

[0196] -2. Determine to use SL-P and select candidate anchor UE (S820):

[0197] The LMF 809 may determine to use one of the SL-P methods (e.g., RTT-based SL-P, SL-AoA, SL-TDOA, SL-AoD, etc.) based on the UE capability information and the position estimation service requirements related to the position estimation of the target UE 800 provided from the AMF 807 in operation 0 (S810). In addition, depending on the SL-P method, in the event that one or more anchor UEs 803 are required, the LMF 809 may select a candidate anchor UE based on the information it previously has (e.g., a list of available anchor UE IDs, a known location of each anchor UE, a positioning capability of each anchor UE, a serving cell of each anchor UE, available SL frequency / BW, etc.).

[0198] Furthermore, additionally, in case the location request message transmitted through operation 0 includes the anchor UE ID provided by the LCS client, the LMF 809 may select the corresponding UE as a candidate anchor UE.

[0199] -3. LPP capability transmission with candidate anchor UE (S825):

[0200] If necessary, the LMF 809 may exchange UE capability information related to position estimation required to perform SL-P with one or more candidate anchor UEs 803 via LPP messages.

[0201] -4. Determine anchor UE (S830):

[0202] The LMF 809 may determine the anchor UE to be ultimately used, the location estimation technology (e.g., RTT type solution using SL, SL-AoA, SL-TDOA, SL-AoD), the location estimation mode (i.e., independent, UE-based, UE-assisted), etc. based on the UE capability information of the candidate anchor UE 803 additionally collected in operation 3 (S825).

[0203] -5.SL-PRS Tx configuration (S835):

[0204] The LMF 809 may request SL-PRS transmission to the target UE 800 and the anchor UE 803. In this case, considering the location estimation QoS requirements (e.g., location estimation accuracy and location estimation service latency) obtained in operation 0 (S810), the location of the target UE / anchor UE (previously known location), etc., the LMF 709 may transmit the request for SL-PRS transmission configuration to the target UE 800 and the anchor UE 803 through the following parameters.

[0205] * Resource type (i.e., aperiodic, semi-persistent, periodic), # of SL-PRS Txs required, periodicity

[0206] * Spatial / path loss information

[0207] *SRC L2 ID, DST L2 ID (for SL-PRS unicast / multicast / broadcast)

[0208] * Scheduling delay requirement (for example, it can be a requirement on the delay between the LMF requesting SL-PRS transmission configuration and the actual SL-PRS transmission resources being configured. Alternatively, in the case where the LMF indicates the SL-PRS transmission timing, it can be a requirement on whether the SL-PRS transmission should actually be performed within a specific time offset from the corresponding timing).

[0209] *SL-PRS Tx activation / deactivation time

[0210] In this case, in the case where there are one or more UEs that must perform SL-PRS transmission, the above parameters may be given to each UE separately. In addition, there may be several methods for configuring SL-PRS transmission resources. Here, it is assumed that the serving gNB 805 allocates SL-PRS transmission resources in mode 1 based on requests from the target UE 800 and the anchor UE 803. The LMF 809 may indicate SL-PRS transmission to the target UE 800 and the anchor UE 803 through an LPP message, and the UE may request SL-PRS transmission resource allocation to the serving gNB 805 through an RRC message to configure the resources required for SL-PRS transmission. The serving gNB 805 may allocate SL transmission resources to the target UE / anchor UE using a dynamic grant scheme and a configured grant type 1 and a configured grant type 2 scheme. When using technologies that require accurate SL-PRS transmission time (such as RTT and TDOA schemes), and technologies that send SL-PRS once or multiple times based on a specific period, the base station may configure and allocate available resources in mode 1 in the configured grant scheme.

[0211] -6. Request for SL-PRS Tx resource allocation (S840):

[0212] * In operation 5 (S835), each of the target UE 800 / anchor UE 803 that has requested the LMF 809 to perform the SL-PRS transmission operation may request the serving gNB 805 to allocate necessary SL transmission resources through an RRC message. In this case, the content requested from the LMF 809 in operation 5 (S835) may be transmitted to the serving gNB 805 as auxiliary information.

[0213] -7. SL-PRSTx resource allocation (S845):

[0214] The serving gNB 805 may determine a necessary SL-PRS transmission configuration based on the auxiliary information received from each UE in operation 6 (S840), and then transmit the determined SL-PRS transmission configuration to each of the target UE 800 and the anchor UE 803. Here, the SL-PRS transmission configuration may include the following information.

[0215] *SL frequency, SL BWP, SL-PRS Tx pool (shared or dedicated)

[0216] → In the case where both the shared SL Tx resource pool and the SL-P dedicated Tx resource pool are configured, the UE uses the SL-P dedicated Tx resource pool by default. Alternatively, an indicator of which of the two pools to use may be included in the SL-PRS transmission configuration.

[0217] *SL-PRS Tx resource allocation (Mode 1 (dynamic grant), Mode 1 with configured grant type 1 / 2)

[0218] *SL-PRS Tx resource type (i.e., aperiodic, semi-persistent, periodic)

[0219] *SL-PRS Tx activation / deactivation time

[0220] *txParameters (i.e., TxThreshIC, TxThreshOoC)

[0221] * Spatial / path loss information (this can indicate SL-SSB from anchor / target UE)

[0222] *SRC L2 ID, DST L2 ID (for SL-PRS unicast / multicast / broadcast)

[0223] -8.SL-PRS Tx configuration confirmation (S850):

[0224] The UE transmitting the SL-PRS may respond to the LMF 809, which may perform the SL-PRS transmission operation as requested by the LMF 809 in operation 5 (S835). In addition, in this operation, the SL-PRS transmission configuration received from the serving gNB 805 in operation 7 (S845) may be transmitted to the LMF 809.

[0225] In this case, for the operations of operations 5 (S835) and 8 (S850), a new LPP message may be defined, or an existing LPP message (requesting / providing assistance data, requesting / providing location information, etc.) may be reused.

[0226] -9.SL-PRS Tx Activation (S855):

[0227] In the case where the SL-PRS transmission resource type is aperiodic or semi-persistent, a SL-PRS transmission activation / deactivation operation may be required. The serving gNB 805 may perform the SL-PRS transmission activation operation based on the request of the LMF 809.

[0228] *9a.LMF 809 may request SL-PRS transmission activation from the serving gNB 805. In this case, LMF 809 may transmit a specific activation time / deactivation time along with the request.

[0229] *9b. The serving gNB 805 may use RRC / MAC CE / DCI etc. to indicate the target UE 800 / anchor UE 803 to activate SL-PRS transmission.

[0230] *9c. The serving gNB 805 may report the result of the SL-PRS transmission activation to the LMF 809. In this case, the activation result may include information about the accurate SL-PRS transmission activation timing.

[0231] -10.LPP provides auxiliary data (S860):

[0232] The LMF 809 may transmit the SL-PRS configuration information received from the serving gNB 805 in operation 8 (S850) as position estimation assistance data to the target UE 800 / anchor UE 803 through an LPP message. If the activation operation of operation 9 (S855) is performed for a non-periodic / semi-persistent resource type, the information about the activation timing obtained in operation 9c may also be included here.

[0233] -11.LPP requests location information (S865):

[0234] The LMF 809 may instruct the target UE 800 / anchor UE 803 to perform necessary SL-PRS measurements and report the results through an LPP message. Depending on the position estimation technology used at this time, the SL-PRS measurement may be instructed to both the target UE 800 and the anchor UE 803, or only to one of them.

[0235] -12.UE SL-PRS measurement (S870):

[0236] The target UE 800 / anchor UE 803 may perform necessary SL-PRS measurement according to the instruction of the LMF 809. As described above, the measurement operation may be performed on only one of the target UE 800 / anchor UE 803 depending on the position estimation technology.

[0237] -13.LPP provides location information (S875):

[0238] The results measured by the target UE 800 / anchor UE 803 (the location information calculated in the case of UE-based mode) may be reported to the LMF 809. In the case of the anchor UE 803, for absolute positioning estimation of the target UE 800, information about its actual location (known location) may be additionally reported to the LMF 809.

[0239] -14. Position determination (S880):

[0240] The LMF 809 may ultimately determine the location of the target UE 800 .

[0241] -15. Position response (S885):

[0242] LMF 809 can transmit the location estimation result of the target UE 800 to AMF 807.

[0243] Fig. 9 is a flowchart for explaining the operation of Option 2 based on the IC scenario according to an embodiment of the present disclosure.

[0244] More specifically, Fig. 9 A process is described in which a base station allocates a SL resource pool necessary for SL-P operation to a UE upon a request from an LMF, and then the UE selects SL resources to be used from the allocated resource pool and performs SL-P operation in a Mode 2 scheme (scenario: the LMF controls the entire SL-P procedure via Uu links with both the target UE and the anchor UE, Option 2: SL-PRS resource allocation using Mode 2 with a shared SL resource pool / dedicated SL resource pool).

[0245] refer to Fig. 9 , LMF 909 may indicate the SL-P operation of the target UE 900 and the anchor UE 903 through an LPP message. In this case, SL resource configuration for the SL-P operation (e.g., SL-PRS transmission) of the target UE 900 / anchor UE 903 may be performed in the Mode 2 scheme. LMF 909 is configured to send SL-PRS to the target UE 900 and the anchor UE 903, and the target UE 900 / anchor UE 903 selects a transmission resource in the Mode 2 scheme from the SL transmission resource pool configured by the serving gNB 905 based on the configuration, and then performs SL-P transmission. LMF 909 may transmit a requirement for SL resource pool configuration for SL-P service to the serving gNB 905 as needed, and the serving gNB 905 may configure the required SL resource pool to the target UE 900 and the anchor UE 903 accordingly. The operation of each process may be described as follows.

[0246] -0. Location request (S910):

[0247] AMF 907 may start the location estimation service by sending a location request message S910 for the target UE 900 to LMF 909. The location request message may include QoS requirements for the location estimation service. In the case where the ID of anchor UE 903 is included in the LCS service request message received by AMF 907 from the LCS client for SL-P service, the location request message S910 may also include one or more anchor UE IDs and the target UE ID. For example, the general public subscription identifier (GPSI) or subscription permanent identifier (SUPI) given in the LCS service request message may be used as the UE ID. For example, the location request message for SL-P service may include requirements for SL-P (ranging operation between two or more UE pairs), requirements for delay / accuracy, etc. In addition, for example, in the case where AMF 907 has UE capability information (positioning UE capability information) related to the location estimation of target UE 900 / anchor UE 903 that has been ensured, AMF 907 may send it to LMF 909 via a location request.

[0248] -1. LPP capability transmission with target UE (S915):

[0249] The LMF 909 and the target UE 900 may exchange UE capability information related to position estimation through an LPP message. In this case, the LPP message may include the following UE capability information related to SL-P.

[0250] *SL-PRS Tx / Rx support

[0251] * Supported SL positioning methods (e.g. RTT-based solutions using SL, SL-AoA, SL-TDOA, SL-AoD) as anchor / target UE

[0252] *Available modes of SL positioning associated with each SL positioning method (i.e., standalone, UE-based, UE-assisted).

[0253] * Available roles for SL positioning associated with each SL positioning method (e.g., target UE, reference UE, assistant UE, positioned UE)

[0254] * Known location support

[0255] *SRC L2 ID, DST L2 ID (for SL-P unicast / multicast or broadcast)

[0256] Meanwhile, in the case where the AMF 907 provides UE capability information related to the location estimation of the target UE 900 in operation 0 (S910), the operation of operation 1 (S915) may be omitted.

[0257] -2. Determine to use SL-P and select candidate anchor UE (S920):

[0258] The LMF 909 may determine to use one of the SL-P methods (e.g., RTT-based SL-P, SL-AoA, SL-TDOA, SL-AoD, etc.) based on the UE capability information and the position estimation service requirements related to the position estimation of the target UE 900 provided from the AMF 907 in operation 0 (S910). Depending on the SL-P method, in the event that one or more anchor UEs 803 are required, the LMF 909 may select a candidate anchor UE based on the information it previously has (e.g., a list of available anchor UE IDs, the known location of each anchor UE, the positioning capability of each anchor UE, the serving cell of each anchor UE, the available SL frequency / BW, etc.).

[0259] Furthermore, additionally, in case the location request message sent through operation 0 includes the anchor UE ID provided by the LCS client, the LMF 909 may select the corresponding UE as a candidate anchor UE.

[0260] -3. LPP capability transmission with candidate anchor UE (S925):

[0261] If necessary, the LMF 909 may exchange UE capability information related to position estimation required for performing SL-P with one or more candidate anchor UEs 903 via LPP messages.

[0262] -4. Determine anchor UE (S930):

[0263] The LMF 909 may determine the anchor UE to be ultimately used, the location estimation technology (e.g., RTT type solution using SL, SL-AoA, SL-TDOA, SL-AoD), the location estimation mode (i.e., independent, UE-based, UE-assisted), etc. based on the UE capability information of the candidate anchor UE 903 additionally collected in operation 3 (S925).

[0264] -5.SL-PRSTx configuration (S935):

[0265] The LMF 909 may request SL resource pool information for SL-PRS transmission from the serving gNB 905. In the case where a UE that must perform SL-PRS transmission is connected to multiple serving gNBs 905, the LMF 909 may request SL resource pool information from multiple serving gNBs 905 in parallel. If necessary, the LMF 909 may also request SL-P dedicated resource pool configuration from the serving gNB 905 through a specific indicator. In this case, the following information may be included as a preference for the requested resource pool.

[0266] *Frequency, bandwidth, subcarrier spacing (SCS) value or range

[0267] * Resource Reservation Interval (RRI) value or range

[0268] * Modulation Coding Scheme (MCS) value or range

[0269] * RSRP value or range for resource selection

[0270] * Whether semi-persistent scheduling is required

[0271] *The maximum number of SL resources (N) that can be reserved via SCI transmission SCI )

[0272] *Preemption priority threshold

[0273] -6.UE SL-P pool configuration (140):

[0274] *In the case where a new SL-P dedicated resource pool needs to be configured or an existing configured dedicated resource pool needs to be changed based on the request of LMF 909, the serving gNB 905 can allocate the new / updated dedicated resource pool to the target UE 900 and the anchor UE 903 through RRC messages.

[0275] -7. SL-PRS resource pool configuration (S943):

[0276] The serving gNB 905 may eventually share the SL resource pool information configured for SL-PRS transmission and reception to the target UE 900 and the anchor UE 903 with the LMF 909. In this case, the signaling for sharing the SL resource pool information may include the following information.

[0277] *SL frequency, SL BWP (bandwidth part)

[0278] *SL Tx / Rx resource pool (shared or dedicated)

[0279] -8a.SL-PRS Tx Configuration (S945):

[0280] The LMF 909 may request SL-PRS transmission through an LPP message to the target UE 900 and the anchor UE 903 that must perform the SL-PRS transmission operation. In this case, considering the location estimation QoS requirements (e.g., requirements for accuracy and location estimation latency) received in operation 0 (S910), the location of the target UE / anchor UE, etc., the LMF 909 may transmit the requirements for SL-PRS transmission configuration to the target UE 900 and the anchor UE 903 through the following parameters.

[0281] * Resource type (i.e., aperiodic, semi-persistent, periodic), # of SL-PRSTx required, periodicity

[0282] * Spatial / path loss information

[0283] *SL SRC L2ID, SL DST L2 ID (for unicast / multicast / broadcast)

[0284] * Scheduling delay requirement (for example, it may be a requirement on the delay between the time when the LMF requests the SL-PRS transmission configuration and the time when the configuration of the SL-PRS transmission resources is actually performed. Alternatively, in the case where the LMF indicates the transmission timing of the SL-PRS, it may be a requirement on whether the SL-PRS transmission should actually be performed within a specific time offset from the corresponding timing)

[0285] *Activation / deactivation time

[0286] In this case, in the case where there are one or more UEs that must perform SL-PRS transmission, the above parameters can be given to each UE. In addition, in the case where both the shared transmission resource pool and the SL-P dedicated transmission resource pool are configured, the UE can use the SL-P dedicated transmission resource pool by default. Alternatively, an indicator about which of the two configured pools to use can be configured for the UE.

[0287] -8b.SL-PRS Tx configuration confirmation (S950):

[0288] The SL-PRS sending UE may respond to the LMF 909, which may perform the SL-PRS transmission operation as requested by the LMF 909 in operation 8a (S945).

[0289] **For the signaling of operations 8a and 8b, new LPP messages may be defined or existing LPP messages (requesting / providing assistance data, requesting / providing location information, etc.) may be reused.

[0290] -9. Activate SL-PRS Tx (S955):

[0291] In the case where the SL-PRS resource type is non-periodic or semi-persistent, an SL-PRS transmission activation / deactivation operation may be required. The UE sending the SL-PRS may perform an activation operation according to the request of the LMF 909.

[0292] *9a.LMF 909 may request SL-PRS transmission activation to target UE 900 and anchor UE 903. Such a request may be transmitted together with information about a specific activation timing.

[0293] *9b. The UE that transmits SL-PRS may report the activation result to the LMF 909. In this case, the activation result may include information about the accurate SL-PRS transmission activation timing.

[0294] -10.LPP provides auxiliary data (S960):

[0295] The LMF 909 may transmit the SL-P transmission resource pool information and SL-PRS configuration information obtained in operation 7 (S943) and operation 8 (S950) to the target UE 900 and the anchor UE 903 as position estimation assistance data through an LPP message. If the activation operation of operation 9 (S955) is performed for a non-periodic / semi-persistent resource type, the information about the activation timing obtained in operation 9b may also be included here.

[0296] -11. LPP requests location information (S965):

[0297] LMF 909 may instruct target UE 900 and anchor UE 903 to perform necessary SL-PRS measurements and report the results through LPP messages. In this case, LMF 909 may instruct SL-PRS measurements to both target UE 900 and anchor UE 903, or only to one of them, depending on the position estimation technique used.

[0298] -12.UE SL-PRS measurement (S970):

[0299] The target UE 900 and the anchor UE 903 may perform necessary SL-PRS measurements according to the instruction of the LMF 909. As described above, depending on the position estimation technology, the measurement operation may be performed on only one of the UEs.

[0300] -13.LPP provides location information (S975):

[0301] The target UE 900 and the anchor UE 903 may report the measurement results (the location information calculated in the case of the UE-based mode) to the LMF 909. In the case of the anchor UE 903, for the absolute positioning estimation of the target UE 900, it may additionally report information about its actual location (known location).

[0302] -14. Position determination (S980):

[0303] The LMF 909 may ultimately determine the location of the target UE 900 .

[0304] -15. Position response (S985):

[0305] LMF 909 can transmit the location estimation result of the target UE 900 to AMF 907.

[0306] Fig.10 is a flowchart of a process for selecting and sending necessary SL resources in a Mode 2 scheme when a UE according to an embodiment of the present disclosure has no latency requirement for SL-P transmission.

[0307] refer to Fig.10 , in case SL MAC PDU transmission (SL-P related control message and SL-PRS transmission) is required on PC5 interface for SL-P operation, UE may select SL transmission resources in Mode 2 scheme. More specific operations are defined below.

[0308] -SL-P Tx trigger in Mode 2 (S1000):

[0309] SL MAC PDU transmission for performing SL-P operation can be triggered in the target UE and the anchor UE. In this case, when using the Mode 2 scheme, the UE can select transmission resources from a pre-configured SL transmission resource pool (e.g., sl-TxPoolSelectedNormal or sl-TxPoolSelectedNormalPS (a resource pool to which power saving is applied)).

[0310] - Reserve SL resources (ie, time slots and sub-channels) (S1005):

[0311] The UE can select transmission resources from the configured SL transmission resource pool and reserve the corresponding resources. In the case of dynamic technology, resources can be reserved for initial transmission and retransmission of each transmission block (TB) to be sent. In the case of semi-persistent technology, transmission resources can be reserved in units of resource reservation interval (RRI) for continuous TB transmission. The UE can notify other UEs whether the transmission resources have been reserved by sending side link control information (SCI). SCI may include information about reserved transmission resources (e.g., subchannels).

[0312] In addition, during the SL transmission resource selection and reservation process, the situation in which preemption is allowed for SL-P related SL MAC PDU transmission resources can be considered. In the case where SL-P is performed by sending / receiving SL MAC PDU related to SL-P (e.g., SL-P related control message or SL-PRS), the transmission priority of the SL MAC PDU can be determined as the priority mapped to the service related to the positioning. For example, a sending UE that intends to send SL-PRS, when sensing the SL resource pool to determine the SL-PRS transmission resources, if it determines that a specific resource is reserved for other SL transmissions (including other SL-PRS transmissions) and the priority of the SL-PRS transmission to be sent is higher than the priority of other SL transmissions, it can determine that the resource can be used first and select the corresponding resource accordingly.

[0313] -Any preemption from other UEs? (S1010):

[0314] If a sending UE that is to send an SL-P related SL MAC PDU determines that another UE has preempted resources that have been reserved for the corresponding transmission for another SL transmission, the sending UE may compare the SL-P related SL transmission priority with the SL transmission priority of the other UE in operation S1015 described below. If no preemption is detected, the sending UE may send the corresponding SL-P related SL MAC PDU on the previously reserved resources in operation S1025 described below.

[0315] -My SL-P Tx has a higher priority? (S1015):

[0316] As described above, if a sending UE that is to send an SL-P-related SL MAC PDU determines that another UE has already preempted the resources reserved for transmission for another SL transmission, the sending UE may compare the corresponding SL-P-related SL transmission priority with the SL transmission priority of the other UE. If the priority of the SL-P-related SL transmission is higher, the corresponding SL-P-related SL MAC PDU may be sent from the previously reserved resources in operation S1025. On the other hand, if the priority of the SL-P-related SL transmission is lower than the SL transmission priority of the other UE, the UE that sends the SL-P-related SL MAC PDU may perform a re-evaluation in operation S1020, which will be described later.

[0317] -Triggering the re-evaluation process (S1020):

[0318] The transmitting UE intending to transmit the SL-P related SL MAC PDU may reconfirm the available SL transmission resources (re-evaluation) and then reselect the resources to be used for the corresponding SL MAC PDU transmission. Afterwards, reservation may be performed through SCI transmission for the reselected resources in operation S1005.

[0319] -SL-P Tx using reserved SL resources (S1025):

[0320] A sending UE that intends to send a SL-P related SL MAC PDU may send the corresponding SL MAC PDU through the SL transmission resources that have been previously reserved.

[0321] Fig.11 is a flowchart of a process for selecting and sending necessary SL resources in a Mode 2 scheme when a UE has latency requirements for SL-P transmission according to an embodiment of the present disclosure.

[0322] refer to Fig.11 , in the case where SL MAC PDU transmission (SL-P related control message and SL-PRS transmission) is required on the PC5 interface for SL-P operation, the UE can select SL transmission resources in the mode 2 scheme. In this case, the latency requirement for SL-P related SL MAC PDU transmission (e.g., the required transmission delay time) can be given from a higher layer. For example, in the case where the SL MAC PDU to be sent includes a control message that must be exchanged for SL-P related measurement operations, the LPP layer can provide the latency requirement for the corresponding SL MAC PDU transmission based on the response time value requested by the UE from the LMF. In addition, in the case where SL-PRS transmission is required regarding SL-P, information such as the timing and maximum allowable time offset at which the corresponding SL-PRS should be sent can be provided from a higher layer. More specific operations are described below.

[0323] -SL-P Tx trigger in Mode 2 (S1100):

[0324] SL MAC PDU transmission for performing SL-P operation can be triggered in the target UE and the anchor UE. In this case, when using the Mode 2 scheme, the UE can select transmission resources from a pre-configured SL transmission resource pool (e.g., sl-TxPoolSelectedNormal or sl-TxPoolSelectedNormalPS (a resource pool to which power saving is applied)).

[0325] -Any SL resources that meet the latency requirement? (S1102):

[0326] In the case where the UE sending the SL-P related SL MAC PDU is provided with a delay requirement for the corresponding transmission from a higher layer, the UE can determine whether there are SL transmission resources that can meet the corresponding delay requirement. For example, in the case where the SL MAC PDU to be sent includes a control message that must be exchanged for SL-P related measurement operations, the UE can determine whether there are SL transmission resources that can be used for the corresponding SL MAC PDU transmission while meeting the requirements provided by the LPP layer (e.g., the required transmission delay). In the case where no SL transmission resources are available within the required transmission delay, the UE can cancel the corresponding SL MAC PDU transmission in operation S1125. However, even in the case where there are no defined SL transmission resources that can meet the delay requirement given by the higher layer, the UE can proceed to operation S1105 and continue the corresponding SL MAC PDU transmission. In addition, in the case where SL-PRS transmission is required for SL-P, it can be determined whether there are SL transmission resources that can meet the timing and maximum allowable time offset of the corresponding SL-PRS that should be sent. In addition, in a case where no SL transmission resources are available within the required transmission timing and the maximum allowable time offset from the corresponding timing, the UE may cancel the corresponding SL-PRS transmission in operation S1125.

[0327] - Reserve SL resources (ie, time slots and sub-channels) (S1105):

[0328] The UE can select transmission resources from the configured SL transmission resource pool and reserve corresponding resources. If the delay requirement for the corresponding transmission is given from a higher layer as described in operation S1102, the SL transmission resource reservation can be performed considering the corresponding delay requirement. In the case of dynamic technology, resources can be reserved for initial transmission and retransmission of each transmission block (TB) to be sent. In the case of semi-persistent technology, transmission resources can be reserved in units of resource reservation interval (RRI) for continuous TB transmission. The UE can notify other UEs whether the transmission resources are reserved by sending side link control information (SCI). SCI may include information about reserved transmission resources (e.g., subchannels).

[0329] In addition, during the SL transmission resource selection and reservation process, the case where preemption is allowed for SL-P related SL MAC PDU transmission resources can be considered. In the case where SL-P is performed by sending / receiving SL-P related SL MACP DU (e.g., SL-P related control message or SL-PR), the SL MAC PDU transmission priority can be determined as the priority mapped to the service related to the positioning. For example, if a sending UE intending to send SL-PRS determines that a specific resource is reserved for another SL transmission (including another SL-PRS transmission) when sensing the SL resource pool to determine the SL-PRS transmission resources, and if it determines that the priority of the SL-PRS transmission to be sent is higher than the priority of the other SL transmission, it can determine that the corresponding resources can be used first and select the corresponding resources accordingly.

[0330] -Any preemption from other UEs? (S1110):

[0331] If the transmitting UE intending to transmit the SL-P related SL MAC PDU determines that another UE has preempted the resources already reserved for the corresponding transmission for another SL transmission, it may compare the SL-P related SL transmission priority with the SL transmission priority of the other UE in operation S1115 described below. If no preemption is detected, the SL-P related SL MAC PDU may be transmitted from the previously reserved resources in operation S1125 described below.

[0332] -My SL-P Tx has a higher priority? (S1115):

[0333] If a transmitting UE intending to transmit an SL-P-related SL MAC PDU determines that another UE has already preempted the resources reserved for the corresponding transmission for another SL transmission, it may compare the corresponding SL-P-related SL transmission priority with the SL transmission priority of the other UE. If the priority of the SL-P-related SL transmission is higher, the corresponding SL-P-related SL MAC PDU may be transmitted on the previously reserved resources in operation S1125 described below. On the other hand, if the priority of the SL-P-related SL transmission is lower than the SL transmission priority of the other UE, the UE transmitting the SL-P-related SL MAC PDU may perform a re-evaluation in operation S1120 described below.

[0334] -Triggering the re-evaluation process (S1120):

[0335] As described above, a transmitting UE intending to transmit an SL-P related SL MAC PDU may reconfirm available SL transmission resources and then reselect resources to be used for transmitting the corresponding SL MAC PDU. Thereafter, in operation 105, reservation of the reselected resources may be performed through SCI transmission.

[0336] -SL-P Tx using reserved SL resources (S1125):

[0337] A sending UE that intends to send an SL-P related SL MAC PDU may send the corresponding SL MAC PDU through the previously reserved SL transmission resources.

[0338] Fig.12 is a block diagram illustrating a user equipment according to an embodiment of the present disclosure.

[0339] refer to Fig.12 , the UE may include a radio frequency (RF) processor 12-10, a baseband processor 12-20, a storage device 12-30, and a controller 12-40. The composition of the UE is not limited to Fig.12 The exemplary configuration shown in FIG. 1 and may include Fig.12 Fewer or more components may be shown.

[0340] The RF processor 12-10 may perform functions such as frequency band conversion, amplification, etc. for transmitting and receiving signals through a radio channel. That is, the RF processor 12-10 may up-convert a baseband signal provided from the baseband processor 12-20 into an RF band signal, and then transmit the RF band signal through an antenna, and down-convert the RF band signal received through the antenna into a baseband signal. For example, the RF processor 12-10 may include a transmitting filter, a receiving filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc., but is not limited thereto. Although in Fig.12 1, one antenna is shown, but the UE may include multiple antennas. In addition, the RF processor 12-10 may include multiple RF chains. In addition, the RF processor 12-10 may perform beamforming. For beamforming, the RF processor 12-10 may adjust the phase and amplitude of each signal sent and received through multiple antennas or antenna elements. In addition, the RF processor 12-10 may perform multiple-input multiple-output (MIMO) operations and receive multiple layers when performing MIMO operations.

[0341] The baseband processor 12-20 can perform a conversion function between a baseband signal and a bit stream according to the physical layer standard of the system. For example, the baseband processor 12-20 can encode and modulate the transmission bit stream to generate complex symbols when data is transmitted. In addition, the baseband processor 12-20 can recover the received bit stream by demodulating and decoding the baseband signal provided from the RF processor 12-10 when data is received. For example, in the case of following the orthogonal frequency division multiplexing (OFDM) scheme, when data is transmitted, the baseband processor 12-20 can encode and modulate the transmission bit stream to generate complex symbols, map the generated complex symbols to subcarriers, and then form OFDM symbols through inverse fast Fourier transform (IFFT) operations and cyclic prefix (CP) insertion. In addition, when data is received, the baseband processor 12-20 can divide the baseband signal provided from the RF processor 12-10 based on OFDM symbols, recover the signal mapped to the subcarrier through a fast Fourier transform (FFT) operation, and then recover the received bit stream through demodulation and decoding.

[0342] As described above, the baseband processor 12-20 and the RF processor 12-10 can send and receive signals. Accordingly, the baseband processor 12-20 and the RF processor 12-10 can be referred to as a transmitter, a receiver, a transceiver, or a communication unit. In addition, at least one of the baseband processor 12-20 and the RF processor 12-10 may include a plurality of communication modules for supporting different radio access technologies. In addition, at least one of the baseband processor 12-20 and the RF processor 12-10 may include different communication modules for processing signals on different frequency bands. For example, different radio access technologies may include wireless LAN (e.g., IEEE802.11), cellular networks (e.g., LTE), etc. In addition, different frequency bands may include super high frequency (SHF) (e.g., 2.NRHz and NRHz) bands and millimeter wave (e.g., 60GHz) bands. The UE may use the baseband processor 12-20 and the RF processor 12-10 to send and receive signals with the gNB, and the signals may include control information and data.

[0343] The storage device 12-30 may store basic programs, applications, configuration information, etc. for the operation of the UE. For example, the storage device 12-30 may store data information for the operation of the UE, such as basic programs, applications, and configuration information. In addition, the storage device 12-30 may provide stored data according to a request from the controller 12-40.

[0344] The storage device 12-30 may be composed of a storage medium such as ROM, RAM, hard disk, CD-ROM and DVD or any combination thereof. In addition, the storage device 12-30 may be composed of multiple memories. According to an embodiment of the present disclosure, the storage device 12-30 may store a program for executing the switching method according to the present disclosure.

[0345] The controller 12-40 may control the overall operation of the UE. For example, the controller 12-40 may send and receive signals through the baseband processor 12-20 and the RF processor 12-10.

[0346] In addition, the controller 12-40 may record data into the storage device 12-30 and read data from the storage device 12-30. To this end, the controller 12-40 may include at least one processor. For example, the controller 12-40 may include a communication processor (CP) that performs control of communication and an application processor (AP) that controls a higher layer such as an application. In addition, according to an embodiment of the present disclosure, the controller 12-40 may include a multi-connection processor 12-42 that is configured to process a process operating in a multi-connection mode. In addition, at least one configuration within the UE may be implemented as a chip.

[0347] Fig.13 is a diagram illustrating a base station device according to an embodiment of the present disclosure.

[0348] Fig.13 The base station may be included in the network described above.

[0349] like Fig.13 As shown, the base station may include an RF processor 13-10, a baseband processor 13-20, a backhaul communication unit 13-30, a storage device 13-40, and a controller 13-50. The configuration of the base station is not limited to Fig.13 The exemplary configuration shown in FIG. 1 and the base station may include Fig.13 The RF processor 13-10 may include fewer or more components than those shown in the figure. The RF processor 13-10 may perform functions such as frequency band conversion, amplification, etc. for sending and receiving signals through a radio channel. That is, the RF processor 13-10 may up-convert a baseband signal provided from the baseband processor 13-20 into an RF band signal, and then transmit the RF band signal through an antenna, and down-convert the RF band signal received through the antenna into a baseband signal. For example, the RF processor 13-10 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. Although in Fig.13One antenna is shown in the figure, but the RF processor 13-10 may include multiple antennas. In addition, the RF processor 13-10 may include multiple RF chains. In addition, the RF processor 13-10 may perform beamforming. For beamforming, the RF processor 13-10 may adjust the phase and amplitude of each signal sent and received through multiple antennas or antenna elements. The RF processor 13-10 may perform downward MIMO operations by sending one or more layers.

[0350] The baseband processor 13-20 can perform a conversion function between a baseband signal and a bit stream according to a physical layer standard. For example, the baseband processor 13-20 can encode and modulate the transmission bit stream to generate complex symbols when data is transmitted. In addition, the baseband processor 13-20 can recover the received bit stream by demodulating and decoding the baseband signal provided from the RF processor 13-10 when data is received. For example, in the case of following the OFDM scheme, when data is transmitted, the baseband processor 13-20 can encode and modulate the transmission bit stream to generate complex symbols, map the generated complex symbols to subcarriers, and then form OFDM symbols through IFFT operations and CP insertion. In addition, when data is received, the baseband processor 13-20 can divide the baseband signal provided from the RF processor 13-10 based on the OFDM symbol, recover the signal mapped to the subcarrier through the FFT operation, and then recover the received bit stream through demodulation and decoding. As described above, the baseband processor 13-20 and the RF processor 13-10 can send and receive signals. Accordingly, the baseband processor 13-20 and the RF processor 13-10 may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit. The base station may use the baseband processor 13-20 and the RF processor 13-10 to transmit and receive signals with the UE, and the signals may include control information and data.

[0351] The backhaul communication unit 13-30 may provide an interface for communicating with other nodes within the network. For example, the backhaul communication unit 13-30 may convert a bit stream sent from the master base station to other nodes (e.g., a secondary base station, a core network, etc.) into a physical signal, and convert a physical signal received from other nodes into a bit stream.

[0352] The storage device 13-40 may store data information for the operation of the main base station, such as basic programs, applications, and configuration information. The storage device 13-40 may store information about the bearers assigned to the connected UEs, the measurement results reported from the connected UEs, and the like. In addition, the storage device 13-40 may store information used as a criterion for determining whether to provide multiple connections to the UE or to terminate them. In addition, the storage device 13-40 may provide stored data according to a request from the controller 13-50. The storage device 13-40 may be constructed with a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or any combination thereof. In addition, the storage device 13-40 may be constructed with a plurality of memories. According to an embodiment of the present disclosure, the storage device 13-40 may store a program for executing the switching method according to the present disclosure.

[0353] The controller 13-50 may control the overall operation of the master base station. For example, the controller 13-50 may send and receive signals through the baseband processor 13-20 and the RF processor 13-10 or the backhaul communication unit 3-30. In addition, the controller 13-50 may record data into the storage device 13-40 and read data from the storage device 13-40. To this end, the controller 13-50 may include at least one processor. In addition, according to an embodiment of the present disclosure, the controller 13-50 may include a multi-connection processor 13-52, which is configured to process a process operating in a multi-connection mode.

[0354] Fig.14 is a block diagram of the structure of an LMF entity according to an example of the present disclosure.

[0355] refer to Fig.14 , the LMF entity according to an embodiment of the present disclosure may include a communication unit 1410, a controller 1420, and a memory 1430. The communication unit 1410, the controller 1420, and the storage device 1430 may operate according to the communication method of the LMF entity described above. However, the components of the LMF entity are not limited to the examples described above. For example, the LMF entity may include more or fewer components than those described above. For example, the LMF entity may include a communication unit 1410 and a controller 1420, and the communication unit 1410 may further include a backhaul communication unit for communicating with another network entity. In addition, the communication unit 1410, the controller 1420, and the memory 1430 may be implemented in the form of a single chip.

[0356] The communication unit 1410 is a general term for a receiver and a transmitter of an LMF entity, and can send and receive messages with other network nodes, base stations, etc. The communication unit 1410 can, for example, send a request message or a response message to the base station through a predetermined interface. The communication unit 1410 may include various configurations for sending and receiving signals, and may output a received signal to the controller 1420 and transmit a signal output from the controller 1420. In addition, the communication unit 1410 may receive a communication signal and output it to the processor, and transmit a signal output from the processor to another network entity through a network.

[0357] The memory 1430 may store data necessary for the operation of the LMF entity, such as basic programs, application programs, and configuration information. In addition, the memory 1430 may provide stored data according to a request of the controller 1420.

[0358] In the present disclosure, the controller 1420 may be defined as a circuit or an ASIC or at least one processor. The processor may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls a higher layer such as an application program. The controller 1420 may control the overall operation of the LMF entity according to the embodiments proposed in the present disclosure. For example, the controller 1420 may control the signal flow between the various blocks to perform operations according to the flowchart described above.

[0359] The method according to the embodiments described in the claims or specification of the present disclosure may be implemented as hardware, software, or a combination thereof.

[0360] In the case where the method is implemented as software, a computer-readable storage medium having one or more programs (software modules) stored therein may be provided. One or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors in an electronic device. One or more programs include instructions that cause the electronic device to perform the method according to the embodiments described in the claims or description of the present disclosure.

[0361] These programs (software modules and software) may be stored in random access memory, non-volatile memory including flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk storage, compact disk-ROM (CD-ROM), digital versatile disk (DVD), other types of optical storage devices, or magnetic tape cassettes. Alternatively, the program may be stored in a memory configured by a combination of some or all of such storage devices. In addition, each of a plurality of memories may be provided.

[0362] In addition, the program can be stored in an attachable storage device accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide LAN (WLAN), or a storage area network (SAN), or a combination thereof. The storage device can access the device executing the embodiments of the present disclosure through an external port. In addition, a separate storage device in the communication network can access the device executing the embodiments of the present disclosure.

[0363] In the present disclosure, the term "computer program product" or "computer-readable medium" may be used to generally indicate media such as memories, hard disks installed in hard disk drives, signals, etc., which are components provided for the method of reporting UE capabilities in a wireless communication system according to the present disclosure.

[0364] The machine-readable storage medium may be provided in the form of a non-transitory storage medium. The term "non-transitory storage medium" means only that the storage medium is a tangible device and does not include signals (e.g., electromagnetic waves), but the term does not distinguish between where data is semi-permanently stored in the storage medium and where data is temporarily stored in the storage medium. For example, a "non-transitory storage medium" may include a buffer that temporarily stores data.

[0365] According to an embodiment, the method according to various embodiments of the present disclosure may be included and provided in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., a compact disc read-only memory (CD-ROM)), or via an application store (e.g., Play Store TM ) online distribution (e.g., downloading or uploading), or directly between two user devices (e.g., smart phones). In the case of online distribution, at least a part of the computer program product (e.g., a downloadable app) may be temporarily generated or at least temporarily stored in a machine-readable storage medium, such as a memory of a manufacturer's server, an application store's server, or a relay server.

[0366] In the detailed embodiments of the present disclosure, the components included in the present disclosure have been expressed as singular or plural according to the detailed embodiments of the present disclosure proposed. However, for the convenience of description, the singular or plural expression has been appropriately selected, and the present disclosure is not limited to the singular or plural components, and the components expressed as plural may be configured as a single component, or the components expressed as singular may also be configured as plural components.

[0367] At the same time, the embodiments of the present disclosure disclosed in this specification and the accompanying drawings are only specific examples presented to easily explain the technical content of the present disclosure and help understand the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to a person skilled in the art to which the present disclosure belongs that other modified examples based on the technical concept of the present disclosure are feasible. In addition, each of the above-mentioned embodiments can be combined with each other and operated as needed. For example, parts of one embodiment of the present disclosure and parts of another embodiment can be combined with each other to operate a base station and a UE. In addition, the embodiments of the present disclosure can be applied to other communication systems, and other modified examples based on the technical concept of the embodiments can also be implemented. For example, the embodiments can be applied to LTE systems, 5G, NR systems, or 6G systems. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be limited not only by the scope of the claims described below, but also by the equivalents of the scope of the claims.

Claims

1. A method for a base station in a communication system, comprising: Obtaining a request message for requesting configuration for transmission of a sidelink positioning reference signal SL-PRS; determining a configuration for transmission of the SL-PRS based on a parameter indicating requirements related to transmission of the SL-PRS included in the request message; and sending a configuration message including the determined configuration for transmission of the SL-PRS to a terminal performing a sidelink positioning operation, The terminal performing the side link positioning operation includes at least one of a target terminal and an anchor terminal.

2. The method according to claim 1, wherein: The request message is received from a location management function LMF entity controlling a sidelink positioning operation or a terminal performing a sidelink positioning operation, and When the request message is received from the LMF entity, the determined configuration related to transmission of the SL-PRS is sent to the LMF entity in response to the request message.

3. The method according to claim 1, wherein: The parameters include resource type, number and periodicity of required SL-PRS transmissions, bandwidth of SL-PRS, space / path loss information, identification ID of SL-PRS multicast or broadcast, scheduling delay requirements and at least one of activation / deactivation time.

4. A method for a terminal in a communication system, comprising: Sending a request message to a base station requesting configuration for transmission of a sidelink positioning reference signal SL-PRS; and receiving, from the base station, a configuration message including a configuration for transmission of the SL-PRS based on the request message, The request message includes a parameter indicating requirements related to the transmission of the SL-PRS, The terminal is a target terminal or an anchor terminal that performs a sidelink positioning operation.

5. The method according to claim 4, further comprising: receiving a first Long Term Evolution LTE Positioning Protocol LPP message including parameters from a Location Management Function LMF entity controlling a sidelink positioning operation, Wherein, based on the first LPP message, a request message is sent to the base station, In response to the first LPP message, a second LPP message including a configuration for transmission of the SL-PRS is sent to the LMF entity, The parameters include resource type, number and periodicity of required SL-PRS transmissions, bandwidth of SL-PRS, space / path loss information, identification ID of SL-PRS multicast or broadcast, scheduling delay requirements and at least one of activation / deactivation time.

6. A method for a location management function LMF entity in a communication system, comprising: Identify requirements related to the transmission of the Sidelink Positioning Reference Signal (SL-PRS); sending a request message requesting configuration for transmission of the SL-PRS to a base station, wherein the request message includes a parameter indicating requirements related to transmission of the SL-PRS; and A configuration for transmission of SL-PRS based on the request message is obtained.

7. The method according to claim 6, wherein: A configuration for transmission of the SL-PRS is received from a base station or a terminal performing a sidelink positioning operation, When the request message is sent to the base station by the terminal performing the sidelink positioning operation which has received a first Long Term Evolution LTE Positioning Protocol LPP message including parameters from the LMF entity, a configuration for transmission of the SL-PRS is received from the terminal performing the sidelink positioning operation through a second LPP message as a response to the first LPP message, The terminal performing the sidelink positioning operation includes at least one of a target terminal and an anchor terminal, The parameters include resource type, number and periodicity of required SL-PRS transmissions, bandwidth of SL-PRS, space / path loss information, identification ID of SL-PRS multicast or broadcast, scheduling delay requirements and at least one of activation / deactivation time.

8. A base station in a communication system, comprising: Transceiver; and a controller that controls the transceiver to obtain a request message requesting a configuration for transmission of a sidelink positioning reference signal SL-PRS, determine a configuration for transmission of the SL-PRS based on a parameter indicating requirements related to transmission of the SL-PRS included in the request message, and send a configuration message including the determined configuration for transmission of the SL-PRS to a terminal that performs a sidelink positioning operation, The terminal performing the side link positioning operation includes at least one of a target terminal and an anchor terminal.

9. The base station according to claim 8, wherein: The request message is received from a location management function LMF entity controlling a sidelink positioning operation or a terminal performing a sidelink positioning operation, and When the request message is received from the LMF entity, the controller controls the transceiver to send the determined configuration for transmission of the SL-PRS to the LMF entity in response to the request message.

10. The base station according to claim 8, wherein: The parameters include resource type, number and periodicity of required SL-PRS transmissions, bandwidth of SL-PRS, space / path loss information, identification ID of SL-PRS multicast or broadcast, scheduling delay requirements and at least one of activation / deactivation time.

11. A terminal in a communication system, comprising: Transceiver; and a controller that controls the transceiver to send a request message to the base station requesting a configuration for transmission of a sidelink positioning reference signal SL-PRS, and receives a configuration message including a configuration for transmission of the SL-PRS based on the request message from the base station, The request message includes a parameter indicating requirements related to the transmission of the SL-PRS, The terminal is a target terminal or an anchor terminal that performs a sidelink positioning operation.

12. The terminal according to claim 11, wherein: The controller controls the transceiver to receive a first Long Term Evolution LTE Positioning Protocol LPP message including parameters from a location management function LMF entity controlling a sidelink positioning operation, sends a request message to a base station based on the first LPP message, and sends a second LPP message including a configuration for transmission of a SL-PRS to the LMF entity in response to the first LPP message, The parameters include resource type, number and periodicity of required SL-PRS transmissions, bandwidth of SL-PRS, space / path loss information, identification ID of SL-PRS multicast or broadcast, scheduling delay requirements and at least one of activation / deactivation time.

13. A location management function LMF entity in a communication system, comprising: Communication unit; and a controller that controls the communication unit to confirm requirements related to transmission of a side link positioning reference signal SL-PRS, and to send a request message to the base station requesting a configuration for transmission of the SL-PRS, and to obtain a configuration for transmission of the SL-PRS based on the request message, The request message includes parameters indicating requirements related to the transmission of the SL-PRS.

14. The LMF entity according to claim 13, wherein: A configuration for transmission of the SL-PRS is received from a base station or a terminal performing a sidelink positioning operation, When the request message is sent to the base station by the terminal performing the sidelink positioning operation which has received a first Long Term Evolution LTE Positioning Protocol LPP message including parameters from the LMF entity, a configuration for transmission of the SL-PRS is received from the terminal performing the sidelink positioning operation through a second LPP message as a response to the first LPP message, The terminal performing the sidelink positioning operation includes at least one of a target terminal and an anchor terminal, The parameters include resource type, number and periodicity of required SL-PRS transmissions, bandwidth of SL-PRS, space / path loss information, identification ID of SL-PRS multicast or broadcast, scheduling delay requirements and at least one of activation / deactivation time.

Images