Location service

Abstract

One disclosure of the present specification provides a method. The method may comprise the steps of: receiving a message including information related to user plane connection and an address related to a first network entity; transmitting the message to a UE; receiving, from the UE, a UL NAS TRANSFER message including a rejection cause; transmitting, to the first network entity, a notification message including the rejection cause; transmitting an analysis request message to a second network entity related to analysis; and receiving an analysis response message from the second network entity.

Description

Location Services

[0001] This specification relates to mobile communications.

[0002] 3GPP (3rd Generation Partnership Project) LTE (Long-Term Evolution) is a technology designed to enable high-speed packet communications. Numerous approaches have been proposed to achieve LTE's goals of reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. 3GPP LTE's high-level requirements include reduced cost per bit, improved service availability, flexible use of frequency bands, a simple architecture, open interfaces, and adequate power consumption for terminals.

[0003] The International Telecommunication Union (ITU) and 3GPP have begun work on developing requirements and specifications for New Radio (NR) systems. 3GPP must identify and develop the technical components necessary to successfully standardize NR, meeting both urgent market needs and the longer-term requirements outlined by the ITU Radio communication sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. Furthermore, NR must be able to utilize any spectrum band up to at least 130 GHz, ensuring that it remains available for wireless communications well into the future.

[0004] NR aims to be a single technology framework that addresses all deployment scenarios, usage scenarios, and requirements, including enhanced Mobile Broadband (eMBB), massive Machine Type Communications (mMTC), and Ultra-Reliable and Low Latency Communications (URLLC). NR must be inherently forward-compatible.

[0005] Location services for terminals can be supported. However, conventional technology has the problem that location services based on the user plane cannot be effectively supported.

[0006] In one aspect, a method is provided. The method may include the steps of: receiving a message including information related to a user plane connection and an address related to a first network entity; transmitting the message to a UE; receiving a UL NAS TRANSFER message from the UE including a reason for rejection; transmitting a notification message including the reason for rejection to the first network entity; transmitting an analysis request message to a second network entity involved in the analysis; and receiving an analysis response message from the second network entity.

[0007] In another aspect, a device implementing the above method is provided.

[0008] In one aspect, a method is provided. The method may include: receiving an analysis request message from a first network entity associated with a location; receiving an analysis request message including a reason for rejection from the second network entity; and transmitting an analysis response message including information related to another network entity associated with the location to the first network entity and / or the second network entity.

[0009] In another aspect, a device implementing the above method is provided.

[0010] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

[0011] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0012] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0013] Figure 4 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0014] Figures 5 and 6 illustrate examples of a PDU session establishment procedure to which the implementation of the present specification applies.

[0015] Figures 7a and 7b illustrate a first example of a location request procedure.

[0016] Figure 8 shows a second example of a location request procedure.

[0017] Figure 9 is a first example of a procedure related to user plane connection.

[0018] Figure 10 is a second example of a procedure related to user plane connection.

[0019] Figure 11 is an example of a procedure related to modifying a user plane connection.

[0020] Figure 12 shows an example in which user plane information is provided.

[0021] FIG. 13 is a first example of a procedure according to one embodiment of the disclosure of the present specification.

[0022] FIG. 14 is an example of operation of a UE according to one embodiment of the disclosure of the present specification.

[0023] FIG. 15 is a second example of a procedure according to one embodiment of the disclosure of the present specification.

[0024] FIG. 16 is a third example of a procedure according to one embodiment of the disclosure of the present specification.

[0025] FIG. 17 is a fourth example of a procedure according to one embodiment of the disclosure of the present specification.

[0026] FIG. 18 is a fifth example of a procedure according to one embodiment of the disclosure of the present specification.

[0027] FIG. 19a and FIG. 19b are sixth examples of a procedure according to one embodiment of the disclosure of the present specification.

[0028] FIG. 20 is a seventh example of a procedure according to one embodiment of the disclosure of the present specification.

[0029] FIG. 21 is an example of a user plane connection establishment command procedure according to one embodiment of the disclosure of the present specification.

[0030] FIG. 22 illustrates an example of a procedure performed according to one embodiment of the disclosure of the present specification.

[0031] The following techniques, devices, and systems can be applied to various wireless multiple access systems. Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA can be implemented using wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using wireless technologies such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data rates for GSM Evolution (EDGE). OFDMA can be implemented using wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) Long-Term Evolution (LTE) is part of E-UMTS (Evolved UMTS) that utilizes E-UTRA.3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). Evolution of 3GPP LTE includes LTE-A (Advanced), LTE-A Pro, and / or 5G NR (New Radio).

[0032] For convenience of explanation, the implementation of this specification is primarily described in relation to a 3GPP-based wireless communication system. However, the technical features of this specification are not limited thereto. For example, the following detailed description is provided based on a mobile communication system corresponding to a 3GPP-based wireless communication system. However, aspects of this specification that are not limited to a 3GPP-based wireless communication system can be applied to other mobile communication systems.

[0033] For terms and technologies used in this specification that are not specifically described, reference may be made to wireless communication standard documents published prior to this specification.

[0034] As used herein, "A or B" can mean "only A," "only B," or "both A and B." Alternatively, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "only A," "only B," "only C," or "any combination of A, B and C."

[0035] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Accordingly, "A / B" can mean "only A," "only B," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0036] In this specification, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in this specification, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted identically to “at least one of A and B.”

[0037] Additionally, in this specification, “at least one of A, B and C” can mean “only A”, “only B”, “only C”, or “any combination of A, B and C”. Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” can mean “at least one of A, B and C”.

[0038] Additionally, parentheses used herein may mean "for example." Specifically, when indicated as "control information (PDCCH)", "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDCCH" may be proposed as an example of "control information." Furthermore, even when indicated as "control information (i.e., PDCCH)", "PDCCH" may be proposed as an example of "control information."

[0039] Technical features individually described in a single drawing in this specification may be implemented individually or simultaneously.

[0040] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein may be applied to various fields requiring wireless communication and / or connectivity between devices (e.g., 5G).

[0041] Hereinafter, the present specification will be described in more detail with reference to the drawings. In the following drawings and / or description, the same reference numbers may refer to the same or corresponding hardware blocks, software blocks, and / or functional blocks, unless otherwise indicated.

[0042] Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.

[0043] The 5G usage scenario shown in FIG. 1 is only an example, and the technical features of this specification can be applied to other 5G usage scenarios not shown in FIG. 1.

[0044] The three main requirement categories for 5G are (1) enhanced mobile broadband (eMBB), (2) massive machine type communication (mMTC), and (3) ultra-reliable and low latency communications (URLLC).

[0045] Referring to FIG. 1, a communication system (1) includes wireless devices (100a to 100f), a base station (BS; 200), and a network (300). FIG. 1 illustrates a 5G network as an example of a network of the communication system (1), but the implementation of the present disclosure is not limited to a 5G system and can be applied to future communication systems beyond the 5G system.

[0046] The base station (200) and the network (300) may be implemented as wireless devices, and a particular wireless device may operate as a base station / network node in relation to other wireless devices.

[0047] The wireless devices (100a to 100f) represent devices that perform communication using Radio Access Technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication / wireless / 5G devices. The wireless devices (100a to 100f) may include, but are not limited to, a robot (100a), a vehicle (100b-1 and 100b-2), an extended reality (XR) device (100c), a portable device (100d), a home appliance (100e), an Internet-of-Things (IoT) device (100f), and an artificial intelligence (AI) device / server (400). For example, the vehicles may include vehicles having wireless communication capabilities, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication. The vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and may be implemented in the form of HMD (Head-Mounted Device) and HUD (Head-Up Display) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signs, vehicles, robots, etc. Portable devices may include smartphones, smart pads, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0048] In this specification, wireless devices (100a to 100f) may be referred to as user equipment (UE). The UE may include, for example, a mobile phone, a smartphone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate PC, a tablet PC, an ultrabook, a vehicle, a vehicle with autonomous driving function, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a hologram device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or a financial device), a security device, a weather / environmental device, a 5G service-related device, or a 4th industrial revolution-related device.

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

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

[0051] NR supports multiple numerologies, or subcarrier spacings (SCS), to support diverse 5G services. For example, an SCS of 15 kHz supports wide areas in traditional cellular bands; an SCS of 30 kHz / 60 kHz supports dense urban areas, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0052] The NR frequency band can be defined by two types of frequency ranges (FR1 and FR2). The numerical values ​​of the frequency ranges can be changed. For example, the two types of frequency ranges (FR1 and FR2) can be as shown in Table 1 below. For convenience of explanation, among the frequency ranges used in the NR system, FR1 can mean the "sub 6 GHz range," and FR2 can mean the "above 6 GHz range," which can be called millimeter wave (mmW).

[0053] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

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

[0055] Frequency Range DefinitionFrequency RangeSubcarrier SpacingFR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0056] Here, the wireless communication technology implemented in the wireless device of the present specification may include not only LTE, NR, and 6G, but also Narrowband IoT (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced MTC). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (Non-Bandwidth Limited), 5) LTE-MTC, 6) LTE MTC, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device of the present specification can include at least one of ZigBee, Bluetooth, and / or LPWAN considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PANs (Personal Area Networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0057] Figure 2 illustrates an example of a wireless device to which the implementation of the present specification is applied.

[0058] In FIG. 2, the first wireless device (100) and / or the second wireless device (200) may be implemented in various forms depending on the use case / service. For example, {the first wireless device (100) and the second wireless device (200)} may correspond to at least one of {the wireless devices (100a to 100f) and the base station (200)}, {the wireless devices (100a to 100f) and the wireless devices (100a to 100f)}, and / or {the base station (200) and the base station (200)} of FIG. 1. The first wireless device (100) and / or the second wireless device (200) may be configured by various components, devices / parts, and / or modules.

[0059] The first wireless device (100) may include at least one transceiver, such as a transceiver (106), at least one processing chip, such as a processing chip (101), and / or one or more antennas (108).

[0060] The processing chip (101) may include at least one processor, such as a processor (102), and at least one memory, such as a memory (104). Additionally and / or alternatively, the memory (104) may be located external to the processing chip (101).

[0061] The processor (102) may control the memory (104) and / or the transceiver (106) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein. For example, the processor (102) may process information in the memory (104) to generate first information / signal and transmit a wireless signal including the first information / signal via the transceiver (106). The processor (102) may receive a wireless signal including second information / signal via the transceiver (106) and store information obtained by processing the second information / signal in the memory (104).

[0062] A memory (104) may be operatively connected to the processor (102). The memory (104) may store various types of information and / or instructions. The memory (104) may store firmware and / or software code (105) that implements code, instructions and / or sets of instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may implement instructions that, when executed by the processor (102), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more protocols. For example, the firmware and / or software code (105) may control the processor (102) to perform one or more air interface protocol layers.

[0063] Here, the processor (102) and memory (104) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). Each transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present specification, the first wireless device (100) may represent a communication modem / circuit / chip.

[0064] The second wireless device (200) may include at least one transceiver, such as a transceiver (206), at least one processing chip, such as a processing chip (201), and / or one or more antennas (208).

[0065] The processing chip (201) may include at least one processor, such as a processor (202), and at least one memory, such as a memory (204). Additionally and / or alternatively, the memory (204) may be located external to the processing chip (201).

[0066] The processor (202) may control the memory (204) and / or the transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein. For example, the processor (202) may process information in the memory (204) to generate third information / signal and transmit a wireless signal including the third information / signal via the transceiver (206). The processor (202) may receive a wireless signal including fourth information / signal via the transceiver (206) and store information obtained by processing the fourth information / signal in the memory (204).

[0067] A memory (204) may be operatively connected to the processor (202). The memory (204) may store various types of information and / or instructions. The memory (204) may store firmware and / or software code (205) that implements code, instructions and / or sets of instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may implement instructions that, when executed by the processor (202), perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more protocols. For example, the firmware and / or software code (205) may control the processor (202) to perform one or more air interface protocol layers.

[0068] Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). Each transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with the RF unit. In the present specification, the second wireless device (200) may represent a communication modem / circuit / chip.

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

[0070] The one or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, and / or a microcomputer. The one or more processors (102, 202) may be implemented by hardware, firmware, software, and / or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), and / or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors (102, 202). For example, the one or more processors (102, 202) may be configured by a set of a communication control processor, an Application Processor (AP), an Electronic Control Unit (ECU), a Central Processing Unit (CPU), a Graphic Processing Unit (GPU), and a Memory Control Processor. One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions and / or commands. The one or more memories (104, 204) may be configured as random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, nonvolatile memory, hard drive, register, cache memory, computer readable storage media and / or combinations thereof.One or more memories (104, 204) may be located internally and / or externally to one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0071] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed herein from one or more other devices. For example, one or more transceivers (106, 206) can be coupled to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, wireless signals, etc., to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, wireless signals, etc. from one or more other devices.

[0072] One or more transceivers (106, 206) may be coupled to one or more antennas (108, 208). Additionally and / or alternatively, one or more transceivers (106, 206) may include one or more antennas (108, 208). One or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein via one or more antennas (108, 208). In the present disclosure, one or more antennas (108, 208) may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0073] One or more transceivers (106, 206) may convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202). One or more transceivers (106, 206) may convert processed user data, control information, wireless signals / channels, etc. from baseband signals to RF band signals using one or more processors (102, 202). For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or a filter. For example, one or more transceivers (106, 206) may up-convert an OFDM baseband signal to an OFDM signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202) and transmit the up-converted OFDM signal at a carrier frequency. One or more transceivers (106, 206) may receive an OFDM signal at a carrier frequency and down-convert the OFDM signal to an OFDM baseband signal via an (analog) oscillator and / or filter under the control of one or more processors (102, 202).

[0074] Although not illustrated in FIG. 2, the wireless device (100, 200) may further include additional components. The additional components (140) may be configured in various ways depending on the type of the wireless device (100, 200). For example, the additional components (140) may include at least one of a power unit / battery, an input / output (I / O) device (e.g., an audio I / O port, a video I / O port), a driving device, and a computing device. The additional components (140) may be connected to one or more processors (102, 202) via various technologies, such as a wired or wireless connection.

[0075] In the implementation of this specification, a UE can operate as a transmitter in the uplink and as a receiver in the downlink. In the implementation of this specification, a base station can operate as a receiver in the UL and as a transmitter in the DL. For the sake of convenience of description, it is mainly assumed below that the first wireless device (100) operates as a UE and the second wireless device (200) operates as a base station. For example, a processor (102) connected to, mounted on, or released in the first wireless device (100) can be configured to perform UE operations according to the implementation of this specification or to control a transceiver (106) to perform UE operations according to the implementation of this specification. A processor (202) connected to, mounted on, or released in the second wireless device (200) can be configured to perform base station operations according to the implementation of this specification or to control a transceiver (206) to perform base station operations according to the implementation of this specification.

[0076] In this specification, a base station may be referred to as a Node B, an eNode B (eNB), or a gNB.

[0077] Figure 3 shows an example of a UE to which the implementation of this specification is applied.

[0078] Referring to FIG. 3, the UE (100) can correspond to the first wireless device (100) of FIG. 2.

[0079] The UE (100) includes a processor (102), memory (104), a transceiver (106), one or more antennas (108), a power management module (141), a battery (142), a display (143), a keypad (144), a SIM (Subscriber Identification Module) card (145), a speaker (146), and a microphone (147).

[0080] The processor (102) may be configured to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed herein. The processor (102) may be configured to control one or more other components of the UE (100) to implement the descriptions, functions, procedures, proposals, methods and / or flowcharts disclosed herein. A layer of a radio interface protocol may be implemented in the processor (102). The processor (102) may include an ASIC, other chipsets, logic circuits and / or data processing devices. The processor (102) may be an application processor. The processor (102) may include at least one of a DSP, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), and a modem (modulator and demodulator). An example of the processor (102) is the SNAPDRAGON manufactured by Qualcomm®. TM Series processors, EXYNOS made by Samsung® TM Series processors, A-series processors made by Apple®, HELIO made by MediaTek® TM ATOM series processors made by Intel® TM It can be found in the series processors or the corresponding next-generation processors.

[0081] Memory (104) is operatively coupled to the processor (102) and stores various information for operating the processor (102). Memory (104) may include ROM, RAM, flash memory, memory cards, storage media, and / or other storage devices. When the implementation is implemented in software, the techniques described herein may be implemented using modules (e.g., procedures, functions, etc.) that perform the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The modules may be stored in memory (104) and executed by the processor (102). Memory (104) may be implemented within the processor (102) or external to the processor (102), in which case it may be communicatively coupled to the processor (102) via various methods known in the art.

[0082] A transceiver (106) is operably coupled to the processor (102) and transmits and / or receives a radio signal. The transceiver (106) includes a transmitter and a receiver. The transceiver (106) may include a baseband circuit for processing a radio frequency signal. The transceiver (106) controls one or more antennas (108) to transmit and / or receive a radio signal.

[0083] The power management module (141) manages the power of the processor (102) and / or the transceiver (106). The battery (142) supplies power to the power management module (141).

[0084] The display (143) outputs the results processed by the processor (102). The keypad (144) receives input to be used by the processor (102). The keypad (144) can be displayed on the display (143).

[0085] A SIM card (145) is an integrated circuit that securely stores an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate subscribers in mobile devices such as mobile phones and computers. Additionally, many SIM cards can store contact information.

[0086] The speaker (146) outputs sound-related results processed by the processor (102). The microphone (147) receives sound-related input to be used by the processor (102).

[0087] Figure 4 shows an example of a 5G system structure to which the implementation of this specification is applied.

[0088] The 5G system (5GS; 5G system) structure consists of the following network functions (NF; Network Function).

[0089] - AUSF (Authentication Server Function)

[0090] -AMF (Access and Mobility Management Function)

[0091] - DN (Data Network), for example, operator services, Internet access, or third-party services.

[0092] - USDF (Unstructured Data Storage Function)

[0093] - NEF (Network Exposure Function)

[0094] - I-NEF (Intermediate NEF)

[0095] - NRF (Network Repository Function)

[0096] - NSSF (Network Slice Selection Function)

[0097] - PCF (Policy Control Function)

[0098] - SMF (Session Management Function)

[0099] - UDM (Unified Data Management)

[0100] - UDR (Unified Data Repository)

[0101] - UPF (User Plane Function)

[0102] - UCMF (UE radio Capability Management Function)

[0103] - AF (Application Function)

[0104] - UE (User Equipment)

[0105] - (R)AN ((Radio) Access Network)

[0106] - 5G-EIR (5G-Equipment Identity Register)

[0107] - NWDAF (Network Data Analytics Function)

[0108] - CHF (CHarging Function)

[0109] 또한, 다음과 같은 네트워크 기능이 고려될 수 있다.

[0110] - N3IWF (Non-3GPP InterWorking Function)

[0111] - TNGF (Trusted Non-3GPP Gateway Function)

[0112] - W-AGF (Wireline Access Gateway Function)

[0113] Figure 4 illustrates the 5G system architecture for a non-roaming case using a reference point representation showing how various network functions interact with each other.

[0114] For clarity of the point-to-point diagram in Figure 4, UDSF, NEF, and NRF are not illustrated. However, all network functions shown can interact with UDSF, UDR, NEF, and NRF as needed.

[0115] For clarity, the connection between UDR and other NFs (e.g., PCF) is not shown in Fig. 4. For clarity, the connection between NWDAF and other NFs (e.g., PCF) is not shown in Fig. 4.

[0116] The 5G system architecture includes the following benchmarks:

[0117] - N1: Reference point between UE and AMF.

[0118] - N2: Reference point between (R)AN and AMF.

[0119] - N3: Reference point between (R)AN and UPF.

[0120] - N4: Reference point between SMF and UPF.

[0121] - N6: Reference point between UPF and data network.

[0122] - N9: Reference point between two UPFs.

[0123] The following benchmarks illustrate the interactions that exist between NF services in NF.

[0124] - N5: Reference point between PCF and AF.

[0125] - N7: Reference point between SMF and PCF.

[0126] - N8: Reference point between UDM and AMF.

[0127] - N10: Reference point between UDM and SMF.

[0128] - N11: Reference point between AMF and SMF.

[0129] - N12: Reference point between AMF and AUSF.

[0130] - N13: Reference point between UDM and AUSF.

[0131] - N14: Reference point between two AMFs.

[0132] - N15: Reference point between PCF and AMF for non-roaming scenarios, and reference point between PCF and AMF of visited network for roaming scenarios.

[0133] - N16: Reference point between two SMFs (in case of roaming, between the SMF of the visited network and the SMF of the home network)

[0134] - N22: Reference point between AMF and NSSF.

[0135] In some cases, two NFs may need to be interconnected to serve a UE.

[0136] Describes the PDU session establishment procedure. See Section 4.3.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0137] Figures 5 and 6 illustrate examples of a PDU session establishment procedure to which the implementation of the present specification applies.

[0138] Establishing a PDU session may involve:

[0139] - UE-initiated PDU session establishment procedure

[0140] - PDU session handover between 3GPP and non-3GPP initiated by UE

[0141] - PDU session handover from UE-initiated EPS to 5GS.

[0142] - Network-triggered PDU session establishment procedure

[0143] A PDU session may be associated with either (a) a single connection type at a given time, i.e., either a 3GPP connection or a non-3GPP connection, or (b) multiple connection types simultaneously, i.e., one 3GPP connection and one non-3GPP connection. A PDU session associated with multiple connection types is called a multi-access (MA) PDU session and may be requested by an access traffic steering, switching, splitting (ATSS) capable UE.

[0144] Figures 5 and 6 specify a procedure for establishing a PDU session associated with a single connection type at a given time.

[0145] In the procedures shown in Figures 5 and 6, it is assumed that the UE is already registered with the AMF, so unless the UE is emergency registered, the AMF has already retrieved the user subscription data from the UDM.

[0146] First, the procedure of Fig. 5 is explained.

[0147] (1) Step 1: To establish a new PDU session, the UE generates a new PDU session ID.

[0148] The UE initiates the PDU session establishment procedure requested by the UE by sending an NAS message containing a PDU session establishment request message within the N1 SM container. The PDU session establishment request message includes the PDU session ID, the requested PDU session type, the requested session and service continuity (SSC) mode, 5G SM capabilities, Protocol Configuration Options (PCO), the SM PDU DN Request Container, and the UE Integrity Protection Maximum Data Rate.

[0149] If the PDU session establishment is a request to establish a new PDU session, the request type is "Initial Request." If the request refers to an existing PDU session switching between a 3GPP connection and a non-3GPP connection, or a PDU session handover from an existing packet data network (PDN) connection in the EPC, the request type is "Existing PDU Session." If the PDU session establishment is a request to establish a PDU session for emergency services, the request type is "Emergency Request." If the request refers to an existing PDU session for emergency services switching between a 3GPP connection and a non-3GPP connection, or a PDU session handover from an existing PDN connection for emergency services in the EPC, the request type is "Existing Emergency PDU Session."

[0150] The UE includes the S-NSSAI from the allowed NSSAI of the current connection type. If a mapping of allowed NSSAIs (Mapping of Allowed NSSAIs) is provided to the UE, the UE provides both the S-NSSAI of the VPLMN (visited VPLMN) from the allowed NSSAIs and the corresponding S-NSSAI of the HPLMN from the mapping of allowed NSSAIs.

[0151] (2) Step 2: AMF selects an SMF. If the request type indicates "Initial Request" or the request is due to a handover from an EPS or other non-3GPP connection provided by an AMF, AMF stores the connection type of the PDU session as well as the association of S-NSSAI(s), data network name (DNN), PDU session ID, and SMF ID.

[0152] If the request type is "Initial Request" and the message also contains a previous PDU session ID representing an existing PDU session, AMF selects an SMF and stores the association of the new PDU session ID, S-NSAI(s), and the selected SMF ID.

[0153] If the request type indicates "Existing PDU Session," AMF selects an SMF based on the SMF-ID received from the UDM. AMF updates the stored connection type for the PDU session.

[0154] If the request type indicates "Existing PDU Session", which refers to an existing PDU session moving between a 3GPP connection and a non-3GPP connection, and if the serving PLMN S-NSSAI of the PDU session is in the allowed NSSAI of the target connection type, the PDU session establishment procedure may be performed in the following cases:

[0155] - When the SMF ID and AMF corresponding to the PDU session ID belong to the same PLMN;

[0156] - If the SMF ID corresponding to the PDU session ID belongs to HPLMN;

[0157] Otherwise, AMF rejects the PDU session establishment request with an appropriate rejection cause.

[0158] AMF rejects requests from emergency-registered UEs whose request type does not indicate "Emergency Request" or "Existing Emergency PDU Session".

[0159] (3) Step 3: If the AMF is not associated with an SMF for the PDU session ID provided by the UE (e.g., when the request type indicates "Initial Request"), the AMF invokes the Create SM Context request procedure (e.g., Nsmf_PDUSession_CreateSMContext Request). If the AMF is already associated with an SMF for the PDU session ID provided by the UE (e.g., when the request type indicates "Existing PDU Session"), the AMF invokes the Update SM Context request procedure (e.g., Nsmf_PDUSession_UpdateSMContext Request).

[0160] The AMF transmits the S-NSSAI of the serving PLMN to the SMF from the allowed NSSAI. For a roaming scenario of local breakout (LBO), the AMF also transmits the corresponding S-NSSAI of the HPLMN to the SMF from the mapping of the allowed NSSAI.

[0161] The AMF ID is the UE's GUAMI, which uniquely identifies the AMF serving the UE. The AMF passes the PDU session ID along with the N1 SM container containing the PDU session establishment request message received from the UE. The GPSI (generic public subscription identifier) ​​is included if available to the AMF.

[0162] If a UE in limited service state is registered for emergency services without providing SUPI, the AMF provides PEI instead of SUPI. If a UE in limited service state is registered for emergency services while providing SUPI but is not authenticated, the AMF indicates that the SUPI is not authenticated. If the SMF does not receive a SUPI for the UE or if the AMF indicates that the SUPI is not authenticated, the UE is considered unauthenticated.

[0163] AMF can include a PCF ID in Nsmf_PDUSession_CreateSMContext. This PCFID identifies the home PCF (H-PCF) in non-roaming cases and the visited PCF (V-PCF) in LBO roaming cases.

[0164] (4) Step 4: If the session management subscription data for the S-NSSAI of the corresponding SUPI, DNN, or HPLMN is not available, the SMF can retrieve the session management subscription data from the UDM and be notified when the subscription data is modified.

[0165] (5) Step 5: SMF sends a create SM context response message (e.g., Nsmf_PDUSession_CreateSMContext Response) or an update SM context response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to AMF according to the request received in step 3.

[0166] If SMF receives the Nsmf_PDUSession_CreateSMContext Request in step 3 and can process the PDU session establishment request, SMF creates an SM context and responds to AMF by providing the SM context ID.

[0167] If the SMF decides not to accept the PDU session establishment, the SMF rejects the UE request by sending a NAS SM signal including the relevant SM rejection cause by responding to the AMF with an Nsmf_PDUSession_CreateSMContext Response. The SMF also indicates to the AMF that the PDU session ID is considered released and the SMF proceeds to step 20 below, aborting the PDU session establishment procedure.

[0168] (6) Step 6: Optional secondary authentication / authorization may be performed.

[0169] (7a) Step 7a: When dynamic policy and charging control (PCC) is used in a PDU session, the SMF can perform PCF selection.

[0170] (7b) Step 7b: SMF performs the SM policy association establishment procedure to establish a PCF and SM policy association, and obtains the basic PCC rules for the PDU session.

[0171] (8) Step 8: SMF selects one or more UPFs.

[0172] (9) Step 9: The SMF may provide information about the satisfied policy control request trigger conditions by performing the SM policy association modification procedure initiated by the SMF.

[0173] (10) Step 10: If the request type indicates an "Initial Request," the SMF may initiate the N4 Session Establishment procedure with the selected UPF. Otherwise, the SMF may initiate the N4 Session Modification procedure with the selected UPF.

[0174] In step 10a, the SMF can send an N4 session establishment / modification request to the UPF, providing packet detection, enforcement, and reporting rules to be installed in the UPF for the PDU session. In step 10b, the UPF can confirm by sending an N4 session establishment / modification response.

[0175] (11) Step 11: SMF sends an N1N2 message transfer message (e.g. Namf_Communication_N1N2 Message Transfer) to AMF.

[0176] The N1N2 Message Forwarding message may contain N2 SM information. The N2 SM information carries the following information that the AMF will forward to the (R)AN:

[0177] - CN Tunnel Info: Corresponds to the core network address of the N3 tunnel corresponding to the PDU session;

[0178] - QFI (QoS flow ID) corresponding to one or more QoS (quality of service) profiles;

[0179] - PDU Session ID: Indicates to the UE the association between RAN resources and a PDU session for the UE;

[0180] - S-NSSAI with value for serving PLMN (i.e. HPLMN S-NSSAI, or VPLMN S-NSSAI in case of LBO roaming);

[0181] - User plane security enforcement information determined by SMF;

[0182] - UE integrity protection maximum data rate received in PDU session establishment request message: if integrity protection is indicated as "Preferred" or "Required" in the user plane security enforcement information.

[0183] - RSN (redundancy sequence number) parameter

[0184] The N1N2 message transfer message may include an N1 SM container. The N1 SM container includes a PDU Session Establishment Accept message that the AMF will provide to the UE. The PDU Session Establishment Accept message includes the S-NSSAI from the allowed NSSAI. For the LBO roaming scenario, the PDU Session Establishment Accept message includes the S-NSSAI from the allowed NSSAI for the VPLMN, and also includes the corresponding S-NSSAI of the HPLMN from the mapping of the allowed NSSAI received by the SMF in step 3.

[0185] Multiple QoS rules, QoS flow levels, and QoS parameters may be included in the PDU session establishment accept message and N2 SM information within the N1 SM container, if required, for QoS flows associated with QoS rules and QoS profiles.

[0186] If the PDU session establishment fails between steps 5 and 11, the N1N2 message forwarding message contains an N1 SM container containing a PDU session establishment rejection message, but does not contain N2 SM information. The (R)AN sends an NAS message containing a PDU session establishment rejection message to the UE. In this case, steps 12-17 below are omitted.

[0187] (12) Step 12: AMF sends a NAS message containing the PDU Session ID and PDU Session Establishment Accept message destined for the UE and the N2 SM information received from SMF to (R)AN within an N2 PDU Session Request message.

[0188] (13) Step 13: The (R)AN may perform AN-specific signaling exchanges with the UE related to the information received from the SMF. For example, in the case of the NG-RAN, the UE may perform an RRC connection reconfiguration with the UE to set up the necessary NG-RAN resources related to the QoS rules for the PDU session request received in step 12.

[0189] (R)AN forwards the NAS message (PDU Session ID, N1 SM container (PDU Session Establishment Accept message)) received in step 12 to the UE. (R)AN provides the NAS message to the UE only if the AN-specific signaling exchange with the UE includes (R)AN resource additions related to the received N2 command.

[0190] If N2 SM information is not included in step 11, steps 14-16b and 17 below are omitted.

[0191] Now, the procedure of Fig. 6 following the procedure of Fig. 5 is described.

[0192] (14) Step 14: (R)AN sends an N2 PDU Session Response message to AMF. The N2 PDU Session Response message may include PDU Session ID, cause, N2 SM information (PDU Session ID, AN tunnel information, accepted / rejected QFI list, user plane enforcement policy notification), etc.

[0193] (15) Step 15: AMF sends an update SM context request message (e.g., Nsmf_PDUSession_UpdateSMContext Request) to SMF. AMF forwards the N2 SM information received from (R)AN to SMF.

[0194] (16a) Step S16a: SMF initiates the N4 session modification procedure with UPF. SMF provides AN tunnel information and corresponding forwarding rules to UPF.

[0195] (16b) Step S16b: UPF provides an N4 session modification response to SMF.

[0196] After this step, the UPF can forward any DL packets that may have been buffered for this PDU session to the UE.

[0197] (16c) Step 16c: If the SMF is not yet registered for this PDU session, the SMF may register with the UDM for the given PDU session.

[0198] (17) Step 17: SMF sends an update SM context response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to AMF.

[0199] After this step, AMF forwards the relevant events to which SMF subscribes.

[0200] (18) Step 18: At any time during the procedure after Step 5, if the PDU session establishment is not successful, the SMF can notify the AMF by calling Nsmf_PDUSession_SMContextStatusNotify (release). The SMF can also release the created N4 session, the PDU session address (e.g., IP address) if assigned, and possibly the association with the PCF. In this case, Step 19 below is omitted.

[0201] (19) Step 19: For PDU session type IPv6 or IPv4v6, SMF may generate and send an IPv6 Router Advertisement to the UE.

[0202] (20) Step 20: SMF can perform SM policy association modification initiated by SMF.

[0203] (21) Step 21: If the PDU session establishment fails after step 4, the SMF may unsubscribe for modification of session management subscription data if the SMF no longer processes the UE's PDU session.

[0204] In various examples of the disclosure of this specification, location related information may be used.

[0205] Below, examples of procedures related to location-related information are described with reference to examples of FIGS. 7a, 7b, and 8.

[0206] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0207] Figures 7a and 7b illustrate a first example of a location request procedure.

[0208] With regard to the examples of FIGS. 7a and 7b, for detailed operation, please refer to TS23.273 V18.4.0 S6.2.

[0209] The examples in FIG. 7a and FIG. 7b are one example of a Mobile Originated (MO)-Location Request (LR) procedure in 5GC.

[0210] According to the examples in FIGS. 7a and 7b, an example of typical network positioning is described where a UE requests a serving PLMN to obtain only its location related information or assistance data.

[0211] 1) When the UE is in CM-IDLE state, the UE can perform a service request triggered by the UE as defined in clause 4.2.3.2 of TS 23.502 V18.4.0 to establish a signaling connection with the AMF.

[0212] 2) The UE may transmit a MO-LR request message included in a UL NAS transmission message. The MO-LR request may optionally include up to three LPP positioning messages.

[0213] 3) AMF can select LMF. AMF can locally configure a mapping table of UE ID (e.g. MSISDN and LMF address). When receiving MO-LR, AMF can determine LMF based on local configuration or by searching in UDM of UE LCS subscriber data.

[0214] 4) AMF can send positioning-related request messages to LMF.

[0215] For example, an AMF may invoke the Nlmf_Location_DetermineLocation service operation on an LMF. This service operation may include the LCS correlation identifier, the serving cell ID, the client type, an indication of whether a location estimate or location assistance data is requested, UE positioning capabilities if available, a list of MO-LR subscription assistance data, and any LPP messages included in the MO-LR request. If the location of a UE is requested, the service request may include whether the UE supports LPP, the requested QoS, the supported GAD shapes, and the expected location time.

[0216] 5) UE positioning may be performed. For example, if the UE requests its own position, the operations described in clause 6.11 of TS 23.502 V18.4.0 may be performed together with the operations described in step 12 of clause 6.1.2 of TS 23.502 V18.4.0, if a scheduled position time exists. If the UE instead requests location assistance data, the LMF may transmit this data to the UE as described in clause 6.11.1 of TS 23.502 V18.4.0. The LMF may determine the exact location assistance data to transmit based on the data type specified by the UE, the UE location capabilities, the assistance data subscribed to the MO-LR and the current cell.

[0217] 6) LMF can send a response message related to positioning to AMF.

[0218] For example, if a location estimate that best satisfies the requested QoS is obtained or requested location assistance data has been transmitted to the UE, the LMF may send an Nlmf_Location_DetermineLocation response to the AMF. This service operation includes the LCS correlation identifier, the location estimate (if obtained), the age and accuracy of the estimate, and may include information about the positioning method.

[0219] 7) AMF can send positioning-related request messages to VGMLC.

[0220] For example, if a position estimate is successfully obtained, the AMF may invoke the Ngmlc_Location_LocationUpdate service operation toward the Visited Gateway Mobile Location Centre (VGMLC) allocated in step 2. This service operation conveys the UE's identifier, the cause event of the position estimate (5GC-MO-LR) and the position estimate, its age, an indication of the acquisition accuracy, and the LCS QoS class requested by the target UE. The service operation may also include a pseudonym indicator, an identifier of the LCS client, an AF ID, a GMLC address, a position estimate timestamp, and, if available, a service type specified by the UE.

[0221] 8) VGMLC can send a location update request message to HGMLC.

[0222] For example, if the UE did not request location transmission to the LCS client or AF in step 2, steps 8-11 may be omitted. If the VGMLC is the same NF instance as the HGMLC, step 8 may be omitted. Otherwise, the VGMLC may invoke the Ngmlc_Location_LocationUpdate service operation for the HGMLC, including the information received from the AMF (the VGMLC may query the NRF to obtain the address of the HGMLC).

[0223] 9a) HGMLC can transmit location information to external clients.

[0224] For example, if the pseudonym indicator is included in the MO-LR location information, the HGMLC can assign a pseudonym to the UE. If the identified LCS client is not accessible to the HGMLC, steps 9a and 10a are omitted. Otherwise, the GMLC sends location information to the LCS client, including the event that triggered the location estimate (5GC-MO LR), the service ID (if available), the location estimate, the location estimate timestamp (if available), and the age, according to the LCS QoS class requested by the target UE.

[0225] 9b-1) HGMLC can send a location update notification message to NEF.

[0226] For example, if an AF ID is included in step 1, HGMLC can allocate an NEF address based on local configuration or through NRF and call the Ngmlc_Location_LocationUpdateNotify service request toward the NEF, passing the AF ID. The location information parameters transmitted in this service operation are the same as in step 9a, except that they do not include a pseudonym.

[0227] 9b-2) NEF can send a location update notification message to AF.

[0228] For example, if the identified AF is not accessible to the NEF, steps 9b-2 and 10b-1 are omitted. Otherwise, the NEF can send location information to the identified AF by calling the Nnef_Location_LocationUpdateNotify service.

[0229] 10a) External clients can send location information Ack to HGMLC.

[0230] For example, if the LCS client does not support MO-LR for temporary or permanent reasons, or if the LCS client cannot process the position estimation of the UE (e.g., if the LCS client does not know the service ID, or if the UE is not registered with the LCS client, or if the LCS client does not have the data of the UE), the LCS client may send a Location Information ack message to the HGMLC with an appropriate error cause. Otherwise, the LCS client may process the position estimation according to the service ID and send a Location Information ack message to the GMLC or HGMLC to indicate that the position estimation of the UE has been successfully processed.

[0231] 10b-1) AF can send a location update notification response message to NEF.

[0232] For example, if the AF cannot process the location estimation of the UE, such as because the UE is not registered with the AF or the AF does not have the corresponding data of the UE, the AF may respond to the Nnef_Location_LocationUpdateNotify service request with an appropriate error cause. Otherwise, the AF may process the location estimation according to the service ID and respond to the Nnef_Location_LocationUpdateNotify service request indicating that the location estimation of the UE has been successfully processed.

[0233] 10b-2) NEF can send the Ngmlc_Location_LocationUpdateNotify service response with the result of the operation to HGMLC.

[0234] 11) HGMLC can send a location update response message to VGMLC.

[0235] For example, this step may be omitted if the VGMLC is the same NF instance as the HGMLC. If the identified LCS client or AF is not accessible, the HGMLC may send a Ngmlc_Location_LocationUpdate service response to the VGMLC with an appropriate error cause. Otherwise, the response may include an acknowledgement. This message may specify whether the identified LCS client or AF successfully processed the UE's position estimate, and if not, the corresponding error cause obtained in step 10.

[0236] 12) VGMLC can send a location update response message to AMF.

[0237] For example, if the VGMLC receives a MO-LR location confirmation from the HGMLC, but the identified LCS client or AF is not accessible, the VGMLC may send a Ngmlc_Location_LocationUpdate service response to the AMF with an appropriate error cause. Otherwise, the response may include an acknowledgement. This message shall indicate whether the identified LCS client or AF successfully processed the UE's position estimate, and if not, the corresponding error cause obtained in step 9 or 10. Additionally, the VGMLC may record charging information for interworking revenue billing with the UE.

[0238] 13) AMF may send a DL NAS TRASPORT message containing a MO-LR response to the UE.

[0239] For example, the UE may have requested its own position. In this case, the MO-LR response may include an indication received from the LMF indicating whether the obtained position estimate satisfies the requested accuracy, or whether the position estimate was successfully transmitted to the identified LCS client or AF, along with all position estimates requested by the UE and timestamps of the position estimates (if available). If the position estimate was successfully transmitted to the identified LCS client or AF, the MO-LR response message may specify whether the identified LCS client or AF successfully processed the UE's position estimate, and if not, the cause of the error obtained in step 13. The AMF may also record charging information.

[0240] The example in Fig. 8 is an example of a Mobile Terminated (MT)-Location Request (LR) procedure in 5GC.

[0241] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0242] Figure 8 shows a second example of a location request procedure.

[0243] The example in Figure 8 is an example of a 5GC-MT-LR procedure for regulatory location service.

[0244] Regarding the example of Fig. 8, for detailed operation, please refer to TS23.273 V18.4.0 S6.1.1.

[0245] Figure 8 illustrates an example of typical network positioning for an LCS client outside the PLMN for regulated location services in a non-roaming scenario. This scenario assumes that the target UE is identified using SUPI or GPSI.

[0246] This procedure applies to LCS client requests for the current location of the target UE, assuming that the LCS client is authorized to use location services and that no privacy verification is required.

[0247] 1. External clients can send LCS service requests to GMLC.

[0248] For example, an external location service client may send a request to the GMLC for the location of a target UE identified by GPSI or SUPI. The request may include the required QoS, a UE unaware indication, and the supported GAD types. If the location is required for more than one UE, the steps below may be repeated, in which case the GMLC may check whether the number of target UEs included in the LCS request is equal to or less than the Maximum Target UE Number of the LCS client. If the Maximum Target UE Number is exceeded, the GMLC rejects the LCS request, skips steps 2-10, and responds to the client with an appropriate error cause in step 11.

[0249] 2. The GMLC calls the Nudm_UECM_Get service operation toward the home UDM of the target UE, which is located by the GPSI or SUPI of this UE.

[0250] 3. UDM transmits the network address of the AMF currently being provided.

[0251] 4. The GMLC requests the UE's current location by calling the Namf_Location_ProvidePositioningInfo service operation to the AMF. This service operation includes the SUPI and client type, and may include the required QoS, UE unawareness indication, and supported GAD configurations.

[0252] 5. If the UE is in CM IDLE state and does not contain a UE Unknown Indication, the AMF initiates a network triggered service request procedure as defined in clause 4.2.3.3 of TS 23.502 V18.4.0 to establish a signaling connection with the UE.

[0253] 6. The AMF may select an LMF based on available information as defined in TS23.273 V18.4.0 S5.1 or based on AMF local settings. LMF selection takes into account the 5G-AN currently serving the UE. Selection may use NRF queries.

[0254] 7. AMF requests the current location of the UE by calling the Nlmf_Location_DetermineLocation service operation to the LMF.

[0255] 8. The LMF may perform one or more of the positioning procedures described in TS23.273 V18.4.0 S6.11.1, S6.11.2, and S6.11.3. During this step, the LMF may use the Namf_Communication_N1N2MessageTransfer service operation to send a positioning-related N1 message to the UE or to request that a network positioning message be sent to the serving NG-RAN node (gNB or NG-eNB) for the UE. The LMF may determine the geographic location and optionally the location in local coordinates.

[0256] 9. LMF can send a positioning response message to AMF.

[0257] For example, the LMF returns the Nlmf_Location_DetermineLocation response to the AMF to return the UE's current location and the UE's positioning capabilities. This service operation includes the LCS correlation identifier, the position estimate, the age and accuracy of the estimate, and may include information about the positioning method and timestamp of the position estimate.

[0258] 10. The AMF may return a Namf_Location_ProvidePositioningInfo response to the GMLC / LRF to return the UE's current position. This service operation includes the position estimate, its lifetime, and its accuracy, and may include information about the positioning method and timestamp of the position estimate. The AMF stores the UE positioning capabilities received from the LMF in the UE context.

[0259] 11. GMLC sends the location service response to the external location service client.

[0260] Referring to the example of FIG. 9, an example of a procedure related to user plane connectivity between a UE and an LMF is described. For the procedure related to user plane connectivity, TS23.273 V18.4.0 S6.18 may be referenced.

[0261] Describes an example of a user plane connection procedure between a UE and an LMF.

[0262] This section describes the management of user plane connections between UEs and LMFs. Either the LMF or the UE can trigger the establishment of a user plane connection. The UE and LMF can maintain the established user plane connection. The LMF can modify or terminate the established user plane connection between the UE and LMF.

[0263] The LMF can transmit user plane information (e.g., IP address or FQDN) to the UE via the DL NAS transport message of the AMF. When the LMF transmits the FQDN to the UE, a DNS server / resolver can resolve the IP address of the LMF (e.g., EASDF or local DNS for local LMF address resolution). The UE can establish a PDU session used for user plane positioning using a URSP containing user plane positioning related PDU session parameters (e.g., dedicated DNN and S-NSSAI). The SMF can select a PSA UPF (located at the central site or local site) to be associated with the LMF for this PDU session based on the S-NSSAI, DNN, and UE location information.

[0264] Session breakout for local LMF services for user plane positioning can be supported by pre-configuring the SMF with the IP address / network prefix of the local LMF and its DNAI to position a dedicated PDU session in a specific service area for local PSA and UL CL / BP insertion.

[0265] In the example of Figure 9, the LMF can initiate a user plane connection.

[0266] If the target UE does not have a user plane connection with the LMF, the LMF can trigger the user plane connection establishment after receiving a location request from the AMF. If the UE supports user plane positioning, the AMF can subscribe to the LCS user plane connection status for the target UE from the LMF using the Nlmf_Location_UP Subscribe message. Figure 9 shows the procedure triggered by the LMF to support positioning through a user plane connection between the UE and the LMF.

[0267] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0268] Figure 9 is a first example of a procedure related to user plane connection.

[0269] According to the example of Fig. 9, an NW-triggered user plane connection can be performed. The LMF performs user plane connection setup for the terminal, and thereafter, the LMF and the terminal can send and receive location-related messages to the connected user plane.

[0270] 1. LMF may decide to use the user plane for positioning.

[0271] For example, based on UE user plane positioning capabilities, control plane congestion conditions (e.g., AMF load conditions), and other implementation factors, the LMF decides whether to use positioning procedures over the user plane connection between the UE and the LMF.

[0272] The LMF may invoke the Nnrf_NFDiscovery service operation to retrieve control plane congestion status (e.g., AMF load information). Based on the AMF load information, the LMF may decide to use user plane positioning if there is a user plane connection available between the UE and the LMF.

[0273] Steps 2 to 7 may be omitted if a user plane connection context of the target UE already exists in the LMF and the LMF decides to utilize the user plane connection for positioning.

[0274] 2. [Conditional Action] LMF can send a message containing user plane information to AMF.

[0275] For example, if the LMF decides to utilize the user plane for positioning and a secure user plane connection is not established between the UE and the LMF, the LMF may invoke the Namf_communication_N1N2MessageTransfer service operation. For example, the LMF may send user plane information to the AMF in the NAS container to inform the UE to utilize the user plane over TLS for positioning. The user plane information may include the LMF's user plane positioning address and security-related information.

[0276] 3. [Conditional Action] When AMF receives user plane information from LMF in step 2, AMF transmits it to UE via DL NAS transfer message.

[0277] 4. [Conditional Action] The UE can send a UL NAS TRANSPORT message to the AMF.

[0278] For example, if there is no corresponding PDU session established for user plane positioning, the UE may establish a PDU session for user plane positioning using URSP containing user plane positioning related PDU session parameters (e.g., dedicated DNN and S-NSSAI). The UE may send an acknowledgment to the LMF via the AMF to indicate the success of utilizing the user plane connection for positioning service or the failure of utilizing the user plane connection (e.g., no appropriate PDU session is established).

[0279] 5. [Conditional Action] AMF can send the confirmation received in step 4 to LMF via the Namf_N1messageNotify service.

[0280] 7. [Conditional Action] The UE can establish a secure user plane connection with the LMF. If the LMF sends the UE an FQDN, a DNS server / resolver can be used to resolve the LMF's IP address (e.g., EASDF or local DNS for local LMF address resolution).

[0281] 8. [Conditional Action] LMF can indicate that a user plane connection between the UE and LMF has been established by sending the Nlmf_Location_UPNotify message to AMF.

[0282] 9. [Conditional] The AMF stores the LCS-UP connection context as part of UE context.

[0283] 9. [Conditional Action] AMF can store the LCS-UP connection context as part of the UE context.

[0284] 10. If the LMF or UE decides to utilize a user plane connection for positioning and a secure user plane connection is established, LPP messages may be transmitted between the UE and the LMF for UE-based positioning, UE-assisted positioning, and assistance data transfer. Ancillary service messages, such as event reporting messages, periodically triggered paging messages, and MS cancel delay position messages, may also be transmitted between the LMF and the UE over the established user plane connection.

[0285] Referring to the example of Fig. 10, an example of a user plane connection initiated by a UE is described.

[0286] If the UE does not have a user plane connection with the LMF, the UE may trigger the establishment of a user plane connection. Figure 10 illustrates a procedure triggered by the UE to support positioning through a user plane connection between the UE and the LMF.

[0287] According to the example of Fig. 10, when a terminal wishes to transmit a position-related message, the AMF may select an LMF corresponding to the terminal. The AMF may notify the LMF that a positioning-related message needs to be transmitted, and the LMF may then establish a user plane connection to handle the position-related message.

[0288] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0289] Figure 10 is a second example of a procedure related to user plane connection.

[0290] According to the example of FIG. 10, positioning via a user plane connection between the UE and the LMF can be initiated by the UE.

[0291] 1. The UE can send a UL NAS TRANSPORT message to the AMF.

[0292] For example, if a UE decides to request user plane connectivity for future positioning requests, the UE may send a NAS message containing a user plane setup request to the AMF.

[0293] 2. [Conditional Action] AMF can select LMF.

[0294] For example, if the UE is authorized to use user plane positioning based on the UE subscription, the AMF can select an LMF with which to establish a user plane session for positioning with the UE. The AMF can search for and select an appropriate LMF by querying the NRF or based on local configuration.

[0295] 3. [Conditional Action] AMF can send Nlmf_Location_UPConfig request to LMF to request LCS-UP connection setup.

[0296] 4. [Conditional Action] AMF can send a message containing user plane information to AMF.

[0297] For example, if the LMF accepts the use of the user plane for positioning and a secure user plane connection is not established between the UE and the LMF, the LMF may send user plane information to the AMF to instruct the UE to accept and use the user plane for positioning. The user plane information may include the LMF's user plane positioning address and security-related information.

[0298] 5. [Conditional Action] When AMF receives user plane information from LMF in step 4, AMF can transmit a DL NAS transport message containing user plane information to UE.

[0299] 6. [Conditional Action] If a secure user plane connection is not established, the UE can establish a secure user plane connection with the LMF. The UE can determine the PDU session parameters, including DNN+S-NSSAI, using the user plane positioning address of the LMF and the information in the URSP. The UE can establish a PDU session using the PDU session parameters. When the SMF receives the request, it can select an appropriate UPF based on the DNN+S-NSSAI and establish a connection between the UPF and the LMF.

[0300] 7. [Conditional Action] The LMF may respond to the AMF that a user plane connection between the UE and the LMF has been established.

[0301] 8. [Conditional Action] AMF can store the LCS-UP connection context as part of the UE context.

[0302] 9. [Conditional Action] After a secure user plane connection is established, the LMF may decide to utilize the user plane connection for positioning after receiving a positioning request from the AMF, or the UE may decide to utilize the user plane connection for positioning. In this case, LPP messages may be transmitted between the UE and the LMF for UE-based positioning, UE-assisted positioning, and auxiliary data transfer. Ancillary service messages such as event reporting messages, periodically triggered paging messages, and MS cancel delay position messages may also be transmitted between the LMF and the UE over the established user plane connection.

[0303] Referring to the example of Fig. 11, modification of the user plane connection between the UE and the LMF is described.

[0304] Figure 11 illustrates how a secure user plane connection between a UE and an LMF is modified. This procedure describes an LMF change, but can also be applied when the source and target LMFs are the same. This procedure can also be used to terminate a user plane connection to a source LMF without selecting a target LMF.

[0305] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0306] Figure 11 is an example of a procedure related to modifying a user plane connection.

[0307] The example in Fig. 11 is an example of a procedure related to modifying a connection between a UE and one or more LMFs.

[0308] 1a. [Conditional Action] The source LMF can send a notification message to the AMF.

[0309] For example, the LMF may detect the need to change the LMF, re-establish a user plane connection between the UE and the LMF, or terminate a user plane connection. The LMF may send an Nlmf_Location_UPNotify message. The Nlmf_Location_UPNotify message may contain information that a connection move (termination and establishment) or termination is required. If a connection move is requested, the Nlmf_Location_UPNotify message may contain the target LMF identifier. The address of the AMF may be provided to the LMF as the "Notification Target Address" in the latest Nlmf_Location_UPConfig message or the Nlmf_Location_UP Subscription message.

[0310] 1b. [Conditional Action] AMF can trigger LMF reselection.

[0311] For example, based on a target LMF identification received from a source LMF for user plane positioning, or when a UE moves to a new location (the UE may be out of the service area of ​​the source LMF and in the service area of ​​the target LMF), the AMF may select a target LMF for the current UE location based on the LMF service area, LMF user plane positioning capability information, and other information. The LMF may establish a user plane session with the UE for positioning. Additionally, when an AMF is relocated, the target AMF may notify the LMF of the AMF change.

[0312] 2. [Conditional Action] The connection can be moved to the target LMF.

[0313] For example, if an AMF reallocation occurs, this step is skipped. Otherwise, steps 3 through 8 of FIG. 10 are performed between the AMF, the UE, and the Target LMF, and the UE may also have its connection to the Source LMF terminated.

[0314] 3. AMF can send a setup request message to the source LMF.

[0315] For example, an AMF may send an Nlmf_Location_UPConfig request to the source LMF. This message may include a request for the source LMF to terminate a specific user plane connection to the UE and a target LMF identifier. Alternatively, it may include information about AMF reallocation.

[0316] 4~5. [Conditional Action] The source LMF can send a request message, and the target LMF can send a response message.

[0317] For example, if there is a UE location event reporting context that is triggered periodically, the source LMF can provide the UE's current location context by calling the Nlmf_Location_LocationContextTransfer request service operation toward the target LMF. The target LMF notifies the source LMF of the result of the location context transfer operation.

[0318] 6. [Conditional Action] The connection with the UE may be terminated.

[0319] For example, the source LMF may terminate the connection to the UE if the user plane connection to the source LMF is still active.

[0320] 7. The LMF may send the Nlmf_Location_UPConfig response message to the AMF to confirm the connection termination or to acknowledge the AMF's change. If this procedure is used for termination, the AMF may release the LCS-UP context after receiving the response message.

[0321] According to conventional technology, location management protocols are transmitted on the control plane. Location management protocols utilizing the user plane are being discussed. However, when using the user plane, there is a problem in that the operation of the terminal and the network is not defined.

[0322] For example, as described above, if the UE supports user plane location, the AMF can subscribe to receive the UE's LCS user plane status from the LMF. Additionally, the LMF can request a UP connection for user plane connection.

[0323] However, according to the prior art, when the LMF requests such a connection, the behavior of the terminal and the network (AMF and LMF) is unclear. Furthermore, when a user plane connection fails, it is unclear how the terminal and network entities (e.g., AMF and LMF) will behave.

[0324] In various examples of the disclosure of this specification, terminal operations and network operations for user plane connection can be defined.

[0325] Referring to FIG. 12, the provision of user plane connection information according to the prior art (e.g., TS24.572 V18.4.0) is described.

[0326] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0327] Figure 12 shows an example in which user plane information is provided.

[0328] The user plane connection information provisioning operations allow the network to provide user plane connection information to the UE as described in section 6.18.1 of 3GPP TS 23.273V18.4.0. The user plane connection information may be encapsulated in a UPP-CMI container of a DL NAS transport message, and the user plane positioning acknowledge may be encapsulated in a UPP-CMI container of an UL NAS transport message as defined in 3GPP TS 24.501 [4]. Figure 12 shows an example of NAS signaling transmission for user plane connection information provisioning.

[0329] Referring to Fig. 12, the following operations can be performed.

[0330] 1. LMF can perform actions related to the transmission of user plane connection information to AMF.

[0331] For example, the LMF may decide to use user plane positioning, and a secure user plane connection for LCS-UPP may not be established. In this case, the LMF may request that the AMF pass the user plane connection information by calling the Namf_Communication_N1N2MessageTransfer service operation.

[0332] 2. AMF can set the payload container type within the payload container to "UPP-CMI container" and include user plane connection information in the payload container. The payload container can be included in the DL NAS TRASNPORT message that AMF will transmit to the UE.

[0333] 3. AMF may send a DL NAS TRANSPORT message to the UE. The DL NAS TRANSPORT message may contain a payload container. The payload container may contain user plane connection information.

[0334] 4. The UE can establish a user plane connection.

[0335] For example, if a user plane connection for LCS-UPP is not established, the UE may establish a user plane connection for LCS-UPP. To indicate the success or failure of the user plane connection for LCS-UPP, the UE may set the payload container type to "UPP-CMI container" and include the payload container in the UL NAS TRANSPORT message.

[0336] 5. The UE may send a UL NAS TRASPORT message to the AMF. The UL NAS TRASPORT message may contain a payload container. The payload container may contain a user plane positioning acknowledgement.

[0337] 6. AMF can perform actions to forward a user plane positioning acknowledgment to LMF. For example, AMF can call the Namf_Communication_N1MessageNotify service action to forward a user plane positioning acknowledgment to LMF.

[0338] According to the prior art (e.g., TS24.572 V18.4.0) illustrated in FIG. 12, when a terminal does not have a PDU session to be used for user plane positioning, the LMF may perform the following operations. For example, in order to establish a connection for user plane positioning, the LMF may notify the AMF of user plane connection information. The AMF may transmit a DL NAS TRANSFPORT message to the terminal. For example, the DL NAS TRANSFPORT message may include a Payload container type and a payload container. For example, the AMF may set the Payload container type to "UPP CMI-container" type and include the user plane connection information received from the LMF in the payload container.

[0339] However, since prior art does not define subsequent operations of the terminal, the disclosure of this specification can define terminal operations in such a state. In addition, operations when an AMF or LMF network entity receives a user plane positioning ACK from the terminal can also be defined.

[0340] Below, examples of terminal operations and network operations related to user plane positioning connections are described.

[0341] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0342] FIG. 13 is a first example of a procedure according to one embodiment of the disclosure of the present specification.

[0343] For reference, in various examples, including those illustrated in FIG. 13, the UE may include an LCS client and an NAS. The LCS client and NAS may be logically implemented in the UE's processor. The UE may perform both LCS client-related operations and NAS-related operations.

[0344] 1. LMF can send messages (including user plane connection establishment commands) to AMF based on the Namf_Communication_N1N2message service operation.

[0345] 2. The AMF may send a DL NAS TRANSFER message to the UE. The DL NAS TRANSFER message may include a UPP CMI container and an address. Here, the address may refer to the address of the LMF.

[0346] 3. The UE can perform verification related to the PDU session based on the address.

[0347] For example, a terminal may receive a DL NAS TRANSFER message from AMF and perform the following actions in sequence based on the address (e.g., LMF LCS-UP address) included in the DL NAS TRANSFER message:

[0348] - 1) The UE can check whether a PDU session related to the received address is currently established. For example, if a PDU session corresponding to the received address is established, the UE can check whether data can be transmitted based on the PDU session. When the UE transmits a 5GSM message based on the PDU session, the message is piggybacked within the 5GMM message and transmitted as a 5GMM message. When transmitting this 5GMM message, the service area to which the UE intends to transmit the 5GMM message may be in the allowed area or in the non-allowed area. Alternatively, the registration area may be in the allowed area or not allowed area. That is, when a transmission for a PDU session using the corresponding user plane is transmitted through an actual wireless network, the UE may be restricted from moving the service to the user plane due to a non-allowed area (e.g., TA may not be allowed or may not be partially allowed, in which case the UE may be associated with a prohibited cell or a non-allowed cell) in the service area or registration area connected to the corresponding wireless network, and the UE may confirm this. If the service is restricted, the UE may transmit an indication with cause in step 4.

[0349] - 2) If a PDU session associated with the received address is not established, the UE may forward a PDU session associated with the LMF LCS-UP address received from the AMF. For example, the UE may perform a PDU session establishment procedure based on the address received from the AMF, for example, with the address of the address received from the AMF. For example, the UE may send a PDU session establishment request message based on the received address to the SMF via the AMF.

[0350] - 3) The UE may transmit a list of PDU sessions whose connection capability type is "LCS user planning positioning" in the Route selection description of the URSP in priority order, and may also transmit an indication that the establishment of the PDU session is triggered. For example, there may be no PDU session related to the received address, and there may not be an address received from the AMF (e.g., LMF LCS-UP address). In this case, the UE may perform the PDU session establishment procedure for the PDU session whose connection capability type is "LCS user planning positioning" in the Route Selection Description (RSD) of the URSP (UE Route Selection Policy) stored within the UE. This means that the UE does not receive the LMF address from the AMF, but uses the stored value. In this case, the UE may have one or more "LCS user planning positioning" connection capability types in the RSD of the URSP of the UE. In this case, the IP address and FQDN are stored in the traffic descriptor of the URSP rule within the URSP, and the terminal can use the address within the stored URSP. At this time, if the terminal has multiple URSP rules, the PDU session establishment procedure can be performed for the PDU session with the highest priority according to the URSP priority.

[0351] 4. The UE's NAS can forward a DL NAS TRANSFER to the LCS client. The DL NAS TRANSFER can include the UPP CMI container, address, cause and indication, and indication information requesting the use of an address within the URSP. The address can indicate the address value received from the AMF. Additionally, the address within the URSP can indicate the use of an address from the URSP value stored in the terminal.

[0352] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0353] FIG. 14 is an example of operation of a UE according to one embodiment of the disclosure of the present specification.

[0354] The example of FIG. 14 may mean the operation of the UE according to step 3 in the example of FIG. 13.

[0355] 1. The UE can determine whether a PDU session exists.

[0356] 2. If a PDU session exists, the UE can determine whether it has received an LMF address to access the PDU session.

[0357] 3. If the UE receives an LMF address for accessing a PDU session, the UE can establish a PDU session or establish a PDU session based on the received network (e.g., LMF) address.

[0358] 4. If a PDU session does not exist, or a PDU session exists but the UE has not received an address in the LMF to access the PDU session, step 4 may be performed. For example, the UE may establish a PDU session based on an address in the URSP for "LCS user plane positioning".

[0359] 5GS terminals can store their own policies, and the UE's URSP (UE route selection policy) can be pre-configured in the terminal. For example, when data is received from the upper layer, a URSP related to how the data will be transmitted to the network can be pre-configured in the terminal. This URSP has one or more URSP rules, and one URSP rule can include multiple traffic descriptors. The traffic descriptor indicates the configuration of the corresponding data traffic. At this time, the traffic descriptor has a connection capability type, and the connection capability type can indicate the connection type of the corresponding data packet. For example, if the DNN type exists, the DNN of the corresponding connection exists, and if the IP type exists, the IP address of the corresponding connection exists. At this time, if the connection capability type is "LCS user plane positioning," the corresponding connection can be regarded as a connection due to LCS user plane positioning. At this time, the terminal may receive an IP address (LMF address) that does not exist in the URSP from the AMF. In this case, the terminal can perform a new PDU session establishment request based on the newly provided address, not the address in the USRP. In this case, the LMF or AMF can indicate to the terminal which value is used first, that is, whether to use the address value provided by the AMF or the address value existing in the URSP.

[0360] Alternatively, in the case of terminal configuration, it may be configured which value is used in priority. For example, PCF may inform URSP, and the corresponding URSP value may be configured by NW. For example, URSP may be updated through NW configuration. Alternatively, URSP may be set by the terminal's own configuration rather than being provided directly over-the-air by NW. In other words, the above terminal configuration indicates that the terminal configuration due to UE implementation, not URSP, may be used.

[0361] The LMF LCS-UP address received by the terminal from the NW may not exist. In this case, when the terminal receives a DL NAS TRANFER message containing a payload container type of LPP-CMI container type from the AMF, the terminal NAS can notify the upper layer (e.g., the module or entity that processes the LMF in the terminal) of the received address and the IP address or FQDN information for the PDU session whose Connection Capability type is "LCS user planning positioning" in the Route Selection Descriptor in the USRP.

[0362] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0363] FIG. 15 is a second example of a procedure according to one embodiment of the disclosure of the present specification.

[0364] 1. LMF can send messages (including user plane connection establishment commands) to AMF based on the Namf_Communication_N1N2message service operation.

[0365] 2. The AMF may send a DL NAS TRANSFER message to the UE. The DL NAS TRANSFER message may include a UPP CMI container and an address. Here, the address may refer to the address of the LMF.

[0366] 3. The UE's NAS can forward a message to the UE's LCS client. For example, the information forwarded may include the UPP CMI container, address, cause and indication, and address information within the URSP.

[0367] 4. The UE can determine whether a PDU session related to the received address exists and whether there is a restriction in the service area or registration area to which the PDU session is to be transmitted, based on the cause and indication.

[0368] For example, a terminal may receive a DL NAS TRANSFER message with a payload container type of "UPP-CMI container" from AMF. The terminal may determine whether a PDU session mapped to the received LMF LCS-UP address has already been established.

[0369] If a PDU session has already been established, the terminal can check whether there is a restriction related to the service area or registration area to which the PDU session is to be transmitted before transmitting data to the lower layer through the PDU session.

[0370] For example, a terminal can determine whether the current TAI is included in the allowed tracking areas. The terminal's NAS can then inform the terminal's LMF (e.g., LCS client) of the service restriction area information for the current TAI.

[0371] In the example above, the service restriction area information may be as follows. The service restriction area information may include information on whether the current TAI is in an allowed tracking area or a non-allowed tracking area. Alternatively, the service restriction area information may include information on whether the current TAI is in a partially allowed tracking area or a partially rejected area. Alternatively, the service restriction area information may include information on whether the current cell is an allowed cell or a non-allowed cell.

[0372] 5. The terminal can generate a user plane connection establishment completion message based on the received address.

[0373] For example, if the received address is related to an already established PDU session and there is no service restriction of the terminal, immediate transmission may be possible. In this case, the terminal can generate a User plane connection establishment complete message. If, in step 5, data transmitted through the PDU session is restricted due to restrictions of the cell, registration area, or service area to which the data will be transmitted, a restriction may occur. In this case, the terminal can generate a User plane connection establishment failure message based on the restriction. The NW can receive the message and determine the cause of the User plane connection establishment failure and the connection establishment failure. Alternatively, the terminal can determine that the User plane connection establishment has failed by not transmitting a User plane connection establishment complete message to the NW.

[0374] 6. The terminal can send a UL NAS TRANSFER message to the AMF. The UL NAS TRANSFER message can include a UPP CMI container and an address. The UPP CMI container can include a user plane connection establishment completion message.

[0375] Here, the address may be an address associated with a user plane connection establishment completion for the terminal. For example, this address may be an address received by the terminal from the AMF. The terminal can indicate, via a 1-bit indicator, whether the address in step 6 is the address received in step 2 or the address of a PDU session pre-allocated for LCS user plane positioning within the terminal's USRP.

[0376] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0377] FIG. 16 is a third example of a procedure according to one embodiment of the disclosure of the present specification.

[0378] 1. LMF can send messages (including user plane connection establishment commands) to AMF based on the Namf_Communication_N1N2message service operation.

[0379] 2. The AMF may send a DL NAS TRANSFER message to the UE. The DL NAS TRANSFER message may include a UPP CMI container and an address. Here, the address may refer to the address of the LMF.

[0380] 3. The UE's NAS can forward a message to the UE's LCS client. For example, the information forwarded may include the UPP CMI container, address, cause and indication, and address information within the URSP.

[0381] 4. The UE can determine whether there is a PDU session related to the received address and whether there is a restriction for transmitting data transmitted through the PDU session.

[0382] For example, a terminal may receive a DL NAS TRANSFER message with a payload container type of "UPP-CMI container" from the AMF. The terminal may check whether a PDU session mapped to the received LMF LCS-UP address has already been established. Alternatively, the terminal may check whether user plane resources for the PDU session associated with the received address are available.

[0383] For example, if a PDU session related to a received address is established, the terminal can check the restriction of the service area related to the PDU session.

[0384] For reference, if the terminal determines that there is no restriction in step 4, steps 5 to 7 of FIG. 15 may be performed.

[0385] 5. The terminal may generate a user plane connection establishment rejection message including the received address and cause value (e.g., not allowed TA, not allowed cell, partially rejected TA).

[0386] For example, if a PDU session related to the received address has been established and a service restriction exists on the terminal, the terminal may generate a User plane connection establishment reject message. For example, if the terminal determines that the transmission of positioning information will fail even if the User plane positioning connection is established, the terminal may generate a User plane connection establishment reject message.

[0387] 6. The terminal can send a UL NAS TRANSFER message to the AMF.

[0388] For example, a UL NAS TRANSFER message may include a UPPCMI container, an address, and a rejection reason. For example, the rejection reason here may be the cause for which the terminal is rejecting user plane connection establishment.

[0389] For example, causes could be not allowed TA, partially rejected TA, and not allowed cell.

[0390] The AMF can perform a procedure to select a new LMF for the terminal. For example, if the UL NAS Transfer message received by the AMF includes a payload container type of UPP-CMI container and a reject cause, the AMF can perform a procedure to select a new LMF based on the location information and TA information of the terminal. In this case, the AMF can perform steps 7 and 9.

[0391] 7. AMF may send a notification message (e.g. Namf_communication_N1N2messagenotify) to LMF1 containing the user plane connection establishment rejection, address, and reason.

[0392] For example, if LMF receives a cause, LMF can help other network entities, such as AMF, GMLC, or NWDAF, request to select LMF2, which has a different address than LMF1.

[0393] Alternatively, there may be more than one LMF to which the terminal can connect. In this case, the terminal can request a "User plane Connection establishment command" to the newly selected LMF to establish a new connection using the LMF LCS-UP address corresponding to the newly selected LMF.

[0394] 8. LMF1 may send an analysis request message (e.g., Nnwdaf_analyticsinfo_request) to NWDAF. The analysis request message may be a request for NWDAF to analyze information to find the optimal LMF. The analysis request message may include the cause received in step 7.

[0395] 9. AMF may send NWDAF an analysis request message (e.g., Nnwdaf_analyticsinfo_request). The analysis request message may request NWDAF to analyze information to find the optimal LMF. The analysis request message may include the cause sent in step 7.

[0396] The NWDAF can receive or collect first location information from the LMF. For example, the first location information may be location information of the terminal held by the LMF. The NWDAF can receive or collect second location information from the AM. The second location information may be location information of the terminal held by the AMF. The second location information may include, for example, cell information of the terminal, TA information, and / or information related to whether the terminal is in an allowed area.

[0397] In step 8 or step 9, the NWDAF may receive an analysis request message containing information related to the UE from the AMF and / or LMF. In this case, the NWDAF may analyze the first location information and / or the second location information and transmit an analysis result message to the AMF and / or LMF. For example, the analysis result message may include information that LMF1 is unavailable and information related to the reason why LMF1 is unavailable. The analysis result message may also include information related to an LMF other than LMF1. Based on the analysis result message, the AMF may select a new LMF.

[0398] For example, when the existing tracking area ID of the UE changes and the tracking area ID does not belong to the allowed area of ​​the terminal (for example, when it becomes a temporary rejected tracking area), the NWDAF can notify the AMF of the LMF information to which the terminal can connect and the location information of the terminal. Alternatively, when the terminal receives a User Plane Connection establishment command from the LMF and notifies the LMF of the response thereto, the terminal can also notify the LMF of the cause information. In this case, the terminal can also notify the AMF of the LMF information to which the terminal is connected or to be connected.

[0399] Based on the information transmitted by the NWDAF, when more than one LMF is available, the AMF can help the AMF select the optimal LMF for the terminal to use. That is, the AMF can select a new LMF based on the information transmitted by the NWDAF.

[0400] For example, a terminal may decide to generate a user plane connection establishment command based on a different address within the URSP. For example, the terminal may use a different PDU session within the URSP, or a different LMF address based on operator policy may be used, using the terminal's stored value.

[0401] For example, based on operator policy, AMF may select a different LMF for the UE.

[0402] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0403] FIG. 17 is a fourth example of a procedure according to one embodiment of the disclosure of the present specification.

[0404] 1. LMF can send messages (including user plane connection establishment commands) to AMF based on the Namf_Communication_N1N2message service operation.

[0405] 2. The AMF may send a DL NAS TRANSFER message to the UE. The DL NAS TRANSFER message may include a UPP CMI container and an address. Here, the address may refer to the address of the LMF.

[0406] 3. The UE's NAS can forward a message to the UE's LCS client. For example, the forwarded information may include a UPP CMI container and address information.

[0407] For example, a terminal may receive a DL NAS TRANSFER message with a payload container type of "UPP-CMI container" from AMF.

[0408] 4. The terminal can determine whether a PDU session used for LCS user plane location exists. For example, the terminal may determine that establishment of a PDU session mapped to the received address is required.

[0409] 5. In connected mode, the terminal can trigger a PDU session establishment request for a location. For example, if a PDU session mapping to a received LMF LCS-UP address is required, the terminal can trigger a PDU session establishment request. At this time, the terminal can trigger the establishment of a PDU session based on the address received from the NW.

[0410] 6. The UE can send a PDU session establishment request message to the SMF.

[0411] 7. SMF may send a PDU Session Establishment Accept message to the UE.

[0412] 8. The NAS of the terminal can forward the result (Ack) to the LCS client. For example, if the terminal receives a PDU session establishment acceptance message, the NAS of the terminal can notify the upper layer that the PDU session establishment has been successfully completed.

[0413] 9. The LMF of the terminal can generate a "user plane connection establishment complete" message containing the received address and forward it to the NAS of the terminal.

[0414] To transmit this, the terminal NAS places the message in a UPP-CMI container through a UL NAS Transfer message and transmits it. At this time, the terminal also reports the address information for which the connection has been established. Alternatively, it notifies the NW through a 1-bit indicator whether the address is the address provided by the NW or the address of the PDU session corresponding to the LCS user plane positioning in the terminal's URSP.

[0415] 10. The terminal can send a UL NAS TRANSFER message to the AMF.

[0416] For example, a UL NAS TRANSFER message may include a UPP CMI container and an address.

[0417] 11. AMF may send a notification message (e.g., Namf_communication_N1N2messagenotify) to LMF1, including the completion of user plane connection establishment and the address.

[0418] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0419] FIG. 18 is a fifth example of a procedure according to one embodiment of the disclosure of the present specification.

[0420] 1~5. It can be performed in the same manner as steps 1 to 5 of Fig. 17.

[0421] 6. The UE may send a PDU Session Establishment Request message to the SMF. The PDU Session Establishment Request message may be a message requesting a PDU session for user plane location (or positioning).

[0422] 7. The SMF may send a PDU Session Establishment Reject message to the UE. The PDU Session Establishment Reject message may include a cause.

[0423] 8. The UE's NAS can forward the result to the LCS client. The result may include rejection information and a reason.

[0424] For example, if the terminal receives a rejection for the PDU session establishment request from the SMF, the terminal NAS can notify the upper layer of the failure of the PDU session establishment and the cause of the failure.

[0425] 9. The UE may generate a User Plane Connection Establishment Complete message including the received address and reason.

[0426] The terminal's upper layer (e.g., the terminal's LCS client) can generate and transmit a "user plane connection establishment reject" message. At this time, the terminal can also provide the reject cause information received from the terminal NAS.

[0427] For example, the terminal LMF (e.g., the terminal's LCS client) can generate a separate cause value used in the LMF based on the corresponding cause. The terminal LMF (e.g., the terminal's LCS client) can also generate a separate cause value by mapping the received cause information. In addition, the terminal LMF (e.g., the terminal's LCS client) can inform the NW through a 1-bit indicator whether the address related to the reject is the address provided by the NW or the address of the PDU session corresponding to the LCS user plane positioning in the terminal's URSP.

[0428] 10. The terminal can send a UL NAS TRANSFER message to the AMF.

[0429] For example, a UL NAS TRANSFER message may include a UPP CMI container, an address, and a reason. For example, the reason may be why the user plane connection establishment is being rejected.

[0430] When the UL NAS Transfer message includes the payload container type and reject cause of the UPP-CMI container, the AMF can newly select an LMF related to the terminal based on the location information and TA information of the terminal.

[0431] 11. AMF may send a notification message (e.g. Namf_communication_N1N2messagenotify) to LMF containing the user plane connection establishment rejection, address, and reason.

[0432] When the LMF receives a cause and a "user plane connection establishment reject" message, the LMF may request other network entities (e.g., AMF, GMLC, or NWDAF) to select an LMF with a different address.

[0433] Alternatively, if there is more than one LMF LCS-UP address that can be forwarded to the LMF, a "User plane Connection establishment command" message with a new address can be requested to establish a connection using a different LMF LCS-UP address on the same LMF.

[0434] Alternatively, there may be more than one LMF to which the terminal can connect. In this case, the terminal can request a "User plane Connection establishment command" to the newly selected LMF to establish a new connection using the LMF LCS-UP address corresponding to the newly selected LMF.

[0435] Additionally, the NWDAF may receive this information from the AMF and / or LMF and assist in selecting the optimal LMF.

[0436] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0437] FIG. 19a and FIG. 19b are sixth examples of a procedure according to one embodiment of the disclosure of the present specification.

[0438] 1~5. It can be performed in the same manner as steps 1 to 5 of Fig. 17.

[0439] 6. The UE can send a PDU session establishment request message to the SMF.

[0440] 7. The UE's NAS can forward the result (including rejection and timer information) to the UE's LCS client.

[0441] For example, a terminal may not receive a response to a PDU session establishment request from the SMF for a certain period of time. In this case, the terminal NAS may notify the upper layer of the continuous failure of PDU session establishment. However, the NAS may abort the PDU session establishment procedure.

[0442] 8. The NAS of the UE can perform local release and abort the procedure.

[0443] 9. The UE may generate a user plane connection establishment rejection message including the received address and reason.

[0444] For example, the upper layer of the terminal (e.g., the LCS client of the terminal) can generate and transmit a "user plane connection establishment reject" message. At this time, the terminal also notifies new reject cause information (e.g., "unreachable UE"). In addition, the terminal can notify the NW through a 1-bit indicator whether the address related to the PDU session where the reject occurred is the address notified by the NW or the address of the PDU session corresponding to the LCS user plane positioning in the terminal's URSP.

[0445] 10. The UE may send a UL NAS TRANSFER message to the AMF. The UL NAS TRANSFER message may include a UPP CMI container, address, and reason.

[0446] When the UL NAS Transfer message includes the payload container type and reject cause of the UPP-CMI container, the AMF can newly select an LMF related to the terminal based on the location information and TA information of the terminal.

[0447] 11. AMF may send a notification message (e.g. Namf_communication_N1N2messagenotify) to LMF containing the user plane connection establishment rejection, address, and reason.

[0448] 12. The LMF may send an analysis request message (e.g., Nnwdaf_analyticsinfo_request) to the NWDAF. The analysis request message may be a request to the NWDAF to analyze information to find the optimal LMF. The analysis request message may include the cause received in step 11.

[0449] When the LMF receives a cause and a "user plane connection establishment reject" message, the LMF may request other network entities (e.g., AMF, GMLC, or NWDAF) to select an LMF with a different address.

[0450] 13. AMF may send NWDAF an analysis request message (e.g., Nnwdaf_analyticsinfo_request). The analysis request message may request NWDAF to analyze information to find the optimal LMF. The analysis request message may include the cause sent in step 11.

[0451] Alternatively, there may be more than one LMF to which the terminal can connect. In this case, the terminal can request a "User plane Connection establishment command" to the newly selected LMF to establish a new connection using the LMF LCS-UP address corresponding to the newly selected LMF.

[0452] Additionally, the NWDAF may receive this information from the AMF and / or LMF and assist in selecting the optimal LMF.

[0453] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0454] FIG. 20 is a seventh example of a procedure according to one embodiment of the disclosure of the present specification.

[0455] 1. LMF can send messages (including user plane connection establishment commands) to AMF based on the Namf_Communication_N1N2message service operation.

[0456] 2. LMF can start a timer when sending a message in step 1 or after sending it.

[0457] For example, the LMF may request a user plane connection establishment command from the AMF and not receive a response. When the LMF sends a user plane connection establishment command, it starts a timer for the user plane connection establishment command.

[0458] 3. The AMF may send a DL NAS TRANSFER message to the UE. The DL NAS TRANSFER message may include a UPP CMI container and an address. Here, the address may refer to the address of the LMF.

[0459] 4. The UE's NAS can forward a message to the UE's LCS client. For example, the forwarded information may include a UPP CMI container and address information.

[0460] For example, a terminal may receive a DL NAS TRANSFER message with a payload container type of "UPP-CMI container" from AMF.

[0461] 5. The UE may fail to transmit the UL NAS TRANSFER message. Alternatively, the UE may transmit the UL NAS TRANSFER message to the AMF, but the AMF may fail to transmit the message to the LMF.

[0462] 6. The timer may expire.

[0463] 7. LFM can assume that it has received a user plane connection establishment rejection message.

[0464] For example, until the timer expires, the LMF may not receive any response from the UE, such as "user plane connection establishment complete" or "user plane connection establishment reject." In this case, the LMF may assume that it has received the "unspecified" cause or the "unreachable UE" cause and the "user plane connection establishment reject" cause from the UE. The cause may be an existing cause or a newly defined cause.

[0465] In addition to the examples of FIGS. 13 to 20, various examples of the disclosure of this specification are described.

[0466] For example, there may be no PDU session related to the address received by the terminal, and there may not be an address received from the AMF (e.g., LMF LCS-UP address). In this case, the terminal may perform a PDU session establishment procedure for a PDU session whose connection capability type is "LCS user planning positioning" in the Route Selection Description (RSD) of the URSP (UE Route Selection Policy) stored within the terminal. This means that the terminal does not receive the LMF address from the AMF, but uses the stored value. At this time, the terminal may have one or more "LCS user planning positioning" connection capability types in the RSD of the URSP of the terminal. In this case, the terminal may store the IP address and FQDN in the traffic descriptor of the URSP rule in the URSP, and in this case, the terminal may use the address in the stored URSP. At this time, if the terminal has multiple URSP rules, the PDU session establishment procedure can be performed for the PDU session with a higher priority according to the URSP priority.

[0467] A terminal may transmit a PDU session establishment request message for a PDU session related to "LCS user planning positioning" within a URSP. In this case, in procedures 3) to 6) of the examples of FIGS. 17 to 20 above, the PDU session related to the PDU session establishment request may be associated with the following addresses. For example, this PDU session may have an address mapped to a PDU session whose connection capability type is "LCS user planning positioning" within the Route Selection Description (RSD) within the URSP.

[0468] Below, examples to which various examples of the disclosure of this specification are applied are described.

[0469] According to the example of FIG. 12 described above, the UE sets the payload container type to "UPP-CMI container" and includes "User plane location confirmation" in the payload container in the UL NAS transmission message to indicate success in utilizing the user plane connection for LCS-UPP or to indicate failure in utilizing the user plane connection for LCS-UPP.

[0470] Based on the definition of the coding part of the message,

[0471] 1) Approval for the user plane connection setup command may be a user plane connection setup completion message.

[0472] 2) The rejection message for the user plane connection setup command may be a user plane connection setup rejection message.

[0473] A User Plane Connection Establishment Complete message may be transmitted by the UE to the LMF. The User Plane Connection Establishment Complete message may be an acknowledgement message for an establishment command message received from the LMF. Table 3 may be referenced.

[0474] A User Plane Connection Establishment Reject message may be sent by a UE to an LMF. A User Plane Connection Establishment Reject message may be sent to reject an establishment command message received from an LMF.

[0475] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0476] FIG. 21 is an example of a user plane connection establishment command procedure according to one embodiment of the disclosure of the present specification.

[0477] Figure 21 is an example of an LMF initiation user plane connection setup command procedure.

[0478] Referring to FIG. 21, an example of initiating a user plane connection information provisioning procedure by LMF is described.

[0479] According to the example of Figure 21, the network may send a user plane connection establishment command message to the UE. The network may start a timer T50xx. The UE may send a user plane connection establishment complete message to the network. The network may stop the timer T50xx.

[0480] The LMF can initiate a user plane connection setup procedure by sending a user plane connection setup command message to the UE, as shown in FIG. 21. The LMF performs the following actions:

[0481] a) LMF can generate user plane connection setup command messages;

[0482] b) LMF may send a user plane disconnect command message to the UE; and

[0483] c) LMF sends a user plane connection setup command message and can start timer T50xx.

[0484] Describes an example of user plane connection information accepted by the UE.

[0485] When the UE receives a user plane connection setup command message from the LMF, it can determine the LMF LCS-UP address to be established.

[0486] When an LMF LCS-UP address is received, the UE can check whether a PDU session corresponding to the received address is currently established and whether the PDU session is established. If a PDU session is already established, the UE can select the received address as the LMF LCS-UP address received from the LMF.

[0487] If there are no service restrictions for the S-NSSAI mapped to the PDU session for user plane positioning, the UE may send a user plane connection setup complete message containing the LMF LCS-UP address information (or indication) set to 0.

[0488] If there is a service restriction in the S-NSSAI mapped to the PDU session for user plane positioning, the UE may send a USER PLALE CONNECTION ESTABLISHMENT REJECT with the cause value (e.g. #28 Restricted Service Area) and the LMF LCS-UP address information (or indication) set to 0.

[0489] If no LMF LCS-UP address is received, the UE may use the Route selection descriptors of the URSP rule to prioritize PDU sessions with the connection function type "LCS User Plane Positioning" and use the information that the PDU session should be triggered.

[0490] If there is no PDU session mapped to the LCS user plane positioning, the UE may request a PDU session trigger to the lower layers of the UE.

[0491] When the UE indicates the result of the PDU session requested for LCS user plane positioning at the lower layers of the UE, the UE may send an acknowledgement to the LMF.

[0492] The lower layers of the UE may indicate that they have successfully received a PDU Session Establishment Accept message for LCS user plane positioning. In this case, the UE may generate a USER PLANE CONNECTION EATABLISHMENT COMPLETE message and send the USER PLANE CONNECTION ESTABLISHMENT COMPLETE message to the LMF.

[0493] After the lower layer of the UE receives a PDU session establishment rejection message containing a rejection reason, it may indicate a failure of the PDU session establishment procedure for LCS user plane positioning. In this case, the UE may generate a user plane connection establishment rejection message containing the rejection reason and transmit the user plane connection establishment rejection message to the LMF.

[0494] The PDU session establishment procedure for LCS user plane positioning may fail due to an abnormality in the lower layers of the UE (e.g., expiration of the 5th T3580). In this case, the UE may generate a USER PLANE CONNECTION EATABLISHMENT REJECT message and send it to the LMF with a rejection cause of "unreachable user plane positioning". The UE may send a "USER PLANE CONNECTION ESTABLISHMENT REJECT" message with a rejection cause of "unreachable user plane positioning" to the LMF. In this case, the UE may encounter a connection rejection when attempting to establish a user plane connection using the currently connected LMF, even though there are multiple connectable LMFs. However, if the UE attempts to establish a user plane connection using another available LMF, the connection may be established. In this case, the UE may send the rejection cause (e.g., the UE is unable to establish a user plane connection to the LMF) to the LMF. The LMF may provide the rejection cause to the NWDAF. NWDAF can then analyze this information and determine whether another LMF is capable of establishing a user plane connection, and NWDAF can then tell the AMF to select another LMF.

[0495] In other words, the UE may not accept the user plane connection information with the associated LMF. In this case, the UE may send a user plane connection establishment rejection message to the LMF along with a rejection reason. Using this rejection reason, the LMF can provide the information to the NWDAF. The NWDAF analyzes the information, and the AMF can use this information to select another LMF.

[0496] An example of an abnormal case on the network side is described. The following abnormal case can be identified: T50xx timeout. In this case, the LMF can be considered to have received a user plane connection setup rejection with a cause value of unreachable user plane positioning.

[0497] Describes an example of a UPP-CM message. A UPP-CM message may include a user plane connection setup completion message.

[0498] The definition of the User Plane Connection Establishment Complete message is as follows. To acknowledge the establishment command received from the LMF, the UE may send the User Plane Connection Complete message to the LMF. Table 3 can be referenced.

[0499] Message Type: User Plane Connection Establishment Complete

[0500] Significance: Dual

[0501] Direction: From UE to network

[0502] IEI Information Element Type / Reference Existence Format Length User Plane Connection Establishment Complete Message Message Type TS24.572 V18.4.0 S11.2.3 Reference MV1 LMF LCS-UP Address Indication LMF LCS-UP Address Indication OTV1

[0503] The example in Table 3 may be the contents of a user plane connection establishment completion message.

[0504] Describes an example of LMF LCS-UP address display.

[0505] The LMF LCS-UP address indication may be included to indicate whether the user plane positioning address of the LMF is used as a PDU session corresponding to the "LCS User Plane Positioning" connection function type of the RSD in the URSP stored in the UE, or whether the PDU session corresponding to the LMF LCS-UP address that received the user plane connection setup command message from the LMF.

[0506] 10.3.3 User plane connection establishment reject

[0507] Describes an example of a user plane connection establishment refusal.

[0508] The definition of a user plane connection establishment rejection is as follows: To reject an establishment command received by a UE from an LMF, a user plane connection rejection message may be sent to the LMF. Table 4 can be referenced.

[0509] Message Type: User Plane Connection Establishment Rejected

[0510] Significance: Dual

[0511] Direction: From UE to network

[0512] IEI Information Element Type / Reference Existence Format Length User Plane Connection Establishment Rejection Message Message Type TS24.572 V18.4.0 S11.2.3 Reference MV1 LMF LCS-UP Address Indication LMF LCS-UP Address Indication OTV1 Rejection Reason 5 GMM Reason OTV1

[0513] An example in Table 4 may be the contents of a user plane connection establishment rejection message.

[0514] For 5GMM cause, S9.11.3.2 of 3GPP TS 24.501 V18.4.0 can be referenced.

[0515] Describes an example of LMF LCS-UP address display.

[0516] The purpose of the LMF LCS-UP Address Indication information element is to indicate whether the user plane positioning address of the LMF is used for a PDU session corresponding to the "LCS User Plane Positioning" connection function type of the RSD (e.g., as defined in 3GPP TS 24.526 V18.4.0) in the URSP stored in the UE, or whether this is the LMF LCS-UP address corresponding to a PDU session that received a user plane connection establishment command message from the LMF.

[0517] The Network slicing indication information element is coded as shown in Table 5 and Table 6.

[0518] The network slicing indication information elements can be coded as shown in Tables 5 and 6.

[0519] The LMF LCS-UP address indication may be a Type 1 information element.

[0520] 87654321LMF LCS-UP Address Indication IEI0Spare0Spare0SpareLLUAI Octet 1

[0521] Table 5 shows an example of the LMF LCS-UP address indication.

[0522] LMF LCS-UP Address Indication (LLUAI) (octet 1, bit 1)Bit10LMF LCS-UP address can be used in the URSP stored in the UE, corresponding to the PDU session, with the "LCS User Plane Positioning" connection function type (defined in 3GPP TS 24.526 V18.4.0) of the RSD.1LMF LCS-UP address can be used in the LMF LCS-UP address received in the LMF corresponding to the PDU session.

[0523] The example in Table 6 is an example of an LMF LCS-UP address indication.

[0524] The following drawings are intended to illustrate specific examples of the present specification. The names of specific devices and the names of specific signals, messages, and fields depicted in the drawings are provided for illustrative purposes only, and the technical features of this specification are not limited to the specific names used in the drawings.

[0525] FIG. 22 illustrates an example of a procedure performed according to one embodiment of the disclosure of the present specification.

[0526] For reference, the procedure illustrated in FIG. 22 is merely an example, and the scope of the disclosure of this specification is not limited by the example in FIG. 22.

[0527] For example, with respect to the example of FIG. 22, the operations described in the examples of FIGS. 1 to 21 may also be applied. For example, even if operations, contents, etc. are not directly described in the example of FIG. 22, operations, contents, etc. described in various examples of the disclosure of this specification may be applied.

[0528] In the example of Figure 22, the first network entity may be a network entity related to mobility (e.g., AMF). The second network entity may be a network entity related to location (e.g., LMF). The third network entity may be a network entity related to analysis (e.g., NWDAF).

[0529] At step (S2201), the second network entity can transmit a message to the first network entity.

[0530] For example, the message may contain information related to a user plane connection and an address related to a second network entity.

[0531] For example, the address may be a Location Management Function (LMF) Location Services (LCS)- User Plane (UP) address.

[0532] In step (S2202), the first network entity may transmit a message to the UE. For example, the message may include information related to the user plane connection and the address.

[0533] In step (S2203), the UE may transmit a UL NAS TRANSFER message to the first network entity.

[0534] For example, a UL NAS TRANSFER message may include a rejection reason.

[0535] For example, the reason for rejection may be related to service area restrictions.

[0536] For example, a UL NAS message may include the rejection reason and a payload container type of User Plane Protocol - Control and Management Information (UPP-CMI).

[0537] In step (S2204), the first network entity can transmit a notification message to the second network entity.

[0538] For example, the notification message may include a reason for rejection.

[0539] For example, the notification message may cause the second network entity to send an analysis request message to the third network entity that includes the reason for the rejection.

[0540] In step (S2205), the first network entity can transmit an analysis request message to a third network entity.

[0541] For example, an analysis request message may include a reason for rejection.

[0542] For reference, the third network entity may also receive a subscription message from the first network entity containing notification information related to the rejection of the UE associated with the user plane connection.

[0543] For reference, the third network entity may also receive an analysis request message from the second network entity that includes the ID of the second network entity and the reason for rejection of the User Equipment (UE) involved in the user plane connection.

[0544] At step (S2206), the third network entity may transmit a response message to the first network entity.

[0545] For example, the response message may be an analysis response message. The response message may include information related to other network entities associated with the location.

[0546] For reference, the third network entity may transmit an analysis response message to the first network entity and / or the second network entity that includes information related to other network entities associated with the location.

[0547] For example, a first network entity may select a fourth network entity associated with a location based on information related to other network entities associated with the location.

[0548] For example, a first network entity may select a fourth network entity associated with a location based on one or more of information associated with other network entities associated with the location, location information of the UE, and Tracking Area (TA) information of the UE.

[0549] According to one embodiment of the disclosure of the present specification, when a terminal cannot establish a user plane connection based on user plane connection establishment, the terminal can inform the LMF of a reject cause for which the establishment cannot be established.

[0550] According to one embodiment of the disclosure of the present specification, the LMF and / or the NWDAF may inform the AMF of information relevant to selecting a new LMF. The AMF may select a new LMF based on the information received from the LMF and / or the NWDAF.

[0551] This specification may have various effects.

[0552] According to one embodiment of the disclosure of the present specification, location services for a terminal can be effectively supported. For example, location services based on a user plane can be effectively supported.

[0553] For example, the stability of the protocol can be ensured by defining behaviors to support new user plane connection establishment.

[0554] The effects that can be achieved through the specific examples of this specification are not limited to the effects listed above. For example, a person with ordinary skill in the relevant technical field may understand or derive various technical effects from this specification. Accordingly, the specific effects of this specification are not limited to those explicitly described herein, but may include various effects that can be understood or derived from the technical features of this specification.

[0555] For reference, the operation of the terminal (e.g., UE, relay UE, vehicle relay UE, MWAB-UE, VMR-UE) described in this specification can be implemented by the devices of FIGS. 1 to 3 described above. For example, the terminal can be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the terminal (e.g., UE) described in this specification can be processed by one or more processors (102 or 202). The operation of the terminal described in this specification can be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) executable by one or more processors (102 or 202). One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (105 or 206), and execute instructions / programs stored in one or more memories (104 or 204) to perform operations of a terminal (e.g., UE) described in the disclosure of this specification.

[0556] Additionally, the commands for performing the operations of the terminal described in the disclosure of this specification may be stored in a non-volatile computer-readable storage medium. The storage medium may be included in one or more memories (104 or 204). In addition, the commands recorded in the storage medium may be executed by one or more processors (102 or 202) to perform the operations of the terminal (e.g., UE) described in the disclosure of this specification.

[0557] For reference, the operation of a network node (e.g., AMF, SMF, UPF, PCF, UDM, LMF, NWDAF, etc.) or a base station (e.g., NG-RAN, gNB, etc.) described in this specification may be implemented by the devices of FIGS. 1 to 3 described below. For example, the network node or the base station may be the first device (100) or the second device (200) of FIG. 2. For example, the operation of the network node or the base station described in this specification may be processed by one or more processors (102 or 202). The operation of the terminal described in this specification may be stored in one or more memories (104 or 204) in the form of instructions / programs (e.g., instructions, executable codes) executable by one or more processors (102 or 202). One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (106 or 206), and execute instructions / programs stored in one or more memories (104 or 204) to perform operations of a network node or base station as described in the disclosure of this specification.

[0558] Additionally, the instructions for performing the operations of the network node or base station described in the disclosure of this specification may be stored in a non-volatile (or non-transitory) computer-readable storage medium having the instructions recorded thereon. The storage medium may be included in one or more memories (104 or 204). In addition, the instructions recorded in the storage medium may be executed by one or more processors (102 or 202) to perform the operations of the network node or base station described in the disclosure of this specification.

[0559] Although the preferred embodiments have been described above by way of example, the disclosure of this specification is not limited to these specific embodiments, and may be modified, changed, or improved in various forms within the scope described in the spirit and claims of this specification.

[0560] In the exemplary system described above, the methods are described based on a flowchart as a series of steps or blocks. However, the order of the steps described is not limited, and some steps may occur in a different order or simultaneously with other steps described above. Furthermore, those skilled in the art will understand that the steps depicted in the flowchart are not exclusive, and other steps may be included, or one or more steps in the flowchart may be deleted without affecting the scope of the invention.

[0561] The claims set forth in this specification may be combined in various ways. For example, the technical features of the method claims of this specification may be combined to implement a device, and the technical features of the device claims of this specification may be combined to implement a method. Furthermore, the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a device, and the technical features of the method claims and the technical features of the device claims of this specification may be combined to implement a method. Other implementations are within the scope of the claims.

Claims

1. A step of receiving a message including information related to a user plane connection and an address related to the first network entity from a first network entity related to a location; A step of transmitting a message including information related to the user plane connection and the address to a User Equipment (UE); A step of receiving a UL NAS TRANSFER message including a rejection reason from the UE; A step of transmitting a notification message including the reason for rejection to the first network entity; A step of transmitting an analysis request message including the above rejection reason to a second network entity involved in the analysis; and A method comprising the step of receiving an analysis response message from said second network entity that includes information related to another network entity associated with the location.

2. In paragraph 1, A method characterized in that the above address is a Location Management Function (LMF) Location Services (LCS)- User Plane (UP) address.

3. In paragraph 1 or 2, A method characterized in that the above rejection reason is related to a limitation of the service area.

4. In any one of paragraphs 1 to 3, A method characterized in that the above UL NAS message includes the rejection reason and a payload container type that is User Plane Protocol - Control and Management Information (UPP-CMI).

5. In any one of paragraphs 1 to 4, A method further comprising the step of selecting a third network entity associated with the location based on information associated with other network entities associated with the location.

6. In any one of paragraphs 1 to 5, A method characterized in that the third network is selected based on one or more of information related to another network entity associated with the location, location information of the UE, and Tracking Area (TA) information of the UE.

7. In any one of paragraphs 1 to 6, A method characterized in that the above notification message causes the first network entity to transmit an analysis request message including the rejection reason to the second network entity.

8. One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to said one or more processors; A device wherein the operation performed based on the above command being executed by the one or more processors is a method according to any one of claims 1 to 7.

9. A step of receiving an analysis request message including an ID of a second network entity related to mobility and a reason for rejection of a User Equipment (UE) related to a user plane connection from a first network entity related to a location; A step of receiving an analysis request message including the above rejection reason from the second network entity; and A method comprising the step of transmitting an analysis response message to the first network entity and / or the second network entity, the analysis response message including information related to other network entities associated with the location.

10. In paragraph 9, A method characterized in that information related to another network entity associated with a location causes the second network entity to select a third network entity associated with the location from the AMF.

11. In clause 9 or 10, A method further comprising the step of receiving a subscription message from the second network entity, the subscription message including notification information related to a rejection of the UE associated with the user plane connection.

12. In any one of paragraphs 9 to 11, A method characterized in that the above rejection reason is related to a limitation of the service area.

13. One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to said one or more processors; A device wherein the operation performed based on the above command being executed by the one or more processors is a method according to any one of claims 9 to 12.

Images