Method for determining URPS rules

Abstract

One disclosure of the present specification provides a method in which a target V-SMF performs communication. The method comprises the following steps: establishing a first UE policy association with an H-PCF for a first UE; establishing a second UE policy association with the H-PCF for the second UE; receiving service parameters from the V-UDR; selecting the first UE policy association or the second UE policy association based on the fact that the service parameter is applicable to the first UE and the second UE; and transmitting a policy message including service parameters for the first UE and the second UE to the H-PCF through the selected one UE policy association, where the first UE is different from the second UE, and the first UE and the second UE may be UEs subscribing to an HPLMN including the H-PCF.

Description

Technical Field

[0001] This specification relates to mobile communications. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a technology for enabling high-speed packet communications. Many solutions have been proposed for LTE objectives, including those aimed at reducing user and provider costs, improving quality of service, and extending and improving coverage and system capacity. As an upper layer requirement, 3GPP LTE needs to reduce cost per bit, increase service availability, flexibly use frequency bands, have a simple structure, open interfaces, and sufficient power consumption of terminals.

[0003] In the International Telecommunication Union (ITU) and 3GPP, requirements and specifications for a New Radio (NR) system have been started. 3GPP must identify and develop technical components that will successfully standardize a new RAT that will meet both the urgent market needs in a timely manner and the longer-term requirements set forth in the International Mobile Telecommunications (IMT)-2020 process of the ITU Radiocommunication Sector (ITU-R). In addition, NR should be able to use any spectrum band in the range of at least up to 100 GHz that may be available for wireless communications even in the more distant future.

[0004] The goal of NR is to solve a single technical framework for all usage scenarios, requirements, and deployment scenarios, including enhanced mobile broadband (eMBB), massive machine type communication (mMTC), ultra-reliable and low-latency communication (URLLC), etc. NR should be inherently forward compatible. Summary of the Invention

[0005] Technical Solution

[0006] If the same service parameters apply to multiple UEs, the V-PCF may send the service parameters to the H-PCF only once for multiple UEs. Brief Description of the Drawings

[0007] Figure 1 An example of a communication system to which an embodiment of the present disclosure is applied is shown.

[0008] Figure 2 An example of a wireless device to which an implementation of the present disclosure is applied is shown.

[0009] Figure 3 An example of a UE to which an implementation of the present disclosure is applied is shown.

[0010] Figure 4 is a block diagram of a next-generation cellular network.

[0011] Figure 5 An example 5G system structure to which an implementation of this specification can be applied is illustrated.

[0012] Figure 6 and Figure 7 shows an example of a registration process applying an implementation of the present disclosure.

[0013] Figure 8a and Figure 8b shows a process according to an embodiment of the present specification.

[0014] Figure 9 shows a process of a target V-PCF according to the disclosure of the present specification.

[0015] Figure 10 shows a process of a target H-PCF according to the disclosure of the present specification. Detailed Embodiments

[0016] The following technologies, devices, and systems can be applied to various wireless multi-access systems. Examples of multi-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 specifically implemented through radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be specifically implemented through radio 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 specifically implemented through radio technologies such as Institute of Electrical and Electronics Engineers (IEEE) 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). The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of the Evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE employs OFDMA in the DL and SC-FDMA in the UL. The evolution of 3GPP LTE includes LTE-A (Advanced), LTE-A Pro, and / or 5G NR (New Radio).

[0017] For convenience of description, implementations of the present disclosure are mainly described with respect to 3GPP-based wireless communication systems. However, the technical features of the present disclosure are not limited thereto. For example, although the following detailed description is given based on a mobile communication system corresponding to a 3GPP-based wireless communication system, aspects of the present disclosure not limited to 3GPP-based wireless communication systems are applicable to other mobile communication systems.

[0018] For terms and technologies not specifically described among the terms and technologies adopted in this disclosure, reference may be made to the wireless communication standard documents published prior to this disclosure.

[0019] In this disclosure, "A or B" may mean "only A", "only B", or "both A and B". In other words, "A or B" in this disclosure may be interpreted as "A and / or B". For example, "A, B, or C" in this disclosure may mean "only A", "only B", "only C", or "any combination of A, B, and C".

[0020] In this disclosure, a slash ( / ) or a comma (,) may mean "and / or". For example, "A / B" may mean "A and / or B". Therefore, "A / B" may mean "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B, or C".

[0021] In this disclosure, "at least one of A and B" may mean "only A", "only B", or "both A and B". Additionally, the expressions "at least one of A or B" or "at least one of A and / or B" in this disclosure may be interpreted the same as "at least one of A and B".

[0022] Additionally, in the disclosure, "at least one of A, B, and C" may 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" may mean "at least one of A, B, and C".

[0023] Additionally, the parentheses used in this disclosure may mean "for example". Specifically, when shown as "control information (PDCCH)", "PDCCH" may be presented as an example of "control information". In other words, "control information" in this disclosure is not limited to "PDCCH", and "PDCCH" may be presented as an example of "control information". Additionally, even when shown as "control information (i.e., PDCCH)", "PDCCH" may be presented as an example of "control information".

[0024] The technical features separately described in one of the drawings in this disclosure may be implemented separately or simultaneously.

[0025] Although not limited thereto, the various descriptions, functions, processes, suggestions, methods, and / or operation flowcharts of this disclosure disclosed herein may be applied to various fields that require wireless communication and / or connection (e.g., 5G) between devices.

[0026] Hereinafter, this disclosure will be described in more detail with reference to the drawings. Unless otherwise indicated, the same reference numerals in the following drawings and / or descriptions may represent the same and / or corresponding hardware blocks, software blocks, and / or functional blocks.

[0027] Figure 1 An example of a communication system implementing the embodiments of the present disclosure is shown.

[0028] Figure 1 The 5G usage scenarios shown are only exemplary, and the technical features of the present disclosure can be applied to Figure 1 other 5G usage scenarios not shown.

[0029] The three main requirement categories of 5G include (1) the enhanced mobile broadband (eMBB) category, (2) the massive machine type communication (mMTC) category, and (3) the ultra-reliable and low-latency communication (URLLC) category.

[0030] Referring to Figure 1 , the communication system 1 includes wireless devices 100a to 100f, a base station (BS) 200, and a network 300. Although Figure 1 a 5G network is shown as an example of the network of the communication system 1, the embodiments of the present disclosure are not limited to 5G systems and can be applied to future communication systems other than 5G systems.

[0031] The BS 200 and the network 300 can be implemented as wireless devices, and a specific wireless device can operate as a BS / network node relative to other wireless devices.

[0032] The wireless devices 100a to 100f represent devices that perform communication using a radio access technology (RAT) (e.g., 5G new RAT (NR) or LTE), and can be referred to as communication / radio / 5G devices. The wireless devices 100a to 100f can include (but are not limited to) a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a household appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device / server 400. For example, the vehicle can include a vehicle with wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. The vehicle can include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device can include an AR / VR / hybrid reality (MR) device and can be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) mounted in a vehicle, a TV, a smart phone, a computer, a wearable device, a household appliance device, a digital sign, a vehicle, a robot, etc. The handheld device can include a smart phone, a smart board, a wearable device (e.g., a smart watch or smart glasses), and a computer (e.g., a notebook). The household appliance can include a TV, a refrigerator, and a washing machine. The IoT device can include sensors and smart meters.

[0033] In the present disclosure, wireless devices 100a to 100f may be referred to as user equipment (UE). For example, the UE may include a cellular phone, a smart phone, a laptop computer, a digital broadcast terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a slate personal computer (PC), a tablet PC, a superbook, a vehicle, a vehicle with an autonomous driving function, a connected car, a UAV, an AI module, a robot, an AR device, a VR device, an MR device, a holographic device, a public safety device, an MTC device, an IoT device, a medical device, a fintech device (or financial device), a security device, a weather / environment device, a device related to 5G services, or a device related to the fourth industrial revolution field.

[0034] For example, a UAV may be an aircraft that flies through a wireless control signal without a person on board.

[0035] For example, a VR device may include a device for implementing an object or background of a virtual world. For example, an AR device may include a device implemented by connecting an object or background of a virtual world to an object or background of the real world. For example, an MR device may include a device implemented by merging an object or background of a virtual world into an object or background of the real world. For example, a holographic device may include a device for implementing a 360-degree stereoscopic image by recording and reproducing three-dimensional information using an optical interference phenomenon generated when two lasers called holography meet.

[0036] For example, a public safety device may include an image relay device or an image device that can be worn on a user's body.

[0037] For example, MTC devices and IoT devices may be devices that do not require direct human intervention or manipulation. For example, MTC devices and IoT devices may include smart meters, vending machines, thermometers, smart bulbs, door locks, or various sensors.

[0038] For example, a medical device may be a device for the purpose of diagnosing, treating, alleviating, curing, or preventing diseases. For example, a medical device may be a device for the purpose of diagnosing, treating, alleviating, or correcting injuries or traumas. For example, a medical device may be a device for the purpose of examining, replacing, or modifying structures or functions. For example, a medical device may be a device for adjusting pregnancy. For example, a medical device may include a device for treatment, a device for operation, a device for (in vitro) diagnosis, a hearing aid, or a device for surgery.

[0039] For example, a security device may be a device installed to prevent possible dangers and maintain safety. For example, a security device may be a camera, a closed-circuit TV (CCTV), a recorder, or a black box.

[0040] For example, a fintech device may be a device capable of providing financial services such as mobile payments. For example, the fintech device may include a payment device or a point-of-sale (POS) system.

[0041] For example, a weather / environment device may include a device for monitoring or predicting weather / environment.

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

[0043] Wireless communications / connections 150a, 150b, and 150c may be established between wireless devices 100a to 100f and / or between wireless devices 100a to 100f and BS200 and / or between BS200s. Herein, wireless communications / connections may be established through various RATs (e.g., 5G NR), such as uplink / downlink communication 150a, sidelink communication, or device-to-device (D2D) communication 150b, inter-base station communication 150c (e.g., relay, integrated access and backhaul (IAB)), etc. Wireless devices 100a to 100f and BS200 / wireless devices 100a to 100f may send / receive radio signals to / from each other through wireless communications / connections 150a, 150b, and 150c. For example, wireless communications / connections 150a, 150b, and 150c may send / receive signals through various physical channels. To this end, at least a part of various configuration information configuration processes, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes for sending / receiving radio signals may be performed based on various proposals of the present disclosure.

[0044] AI refers to the field of studying artificial intelligence or methods for creating it, and machine learning refers to the field of defining various problems solved in the field of AI and methods for solving them. Machine learning is also defined as an algorithm for increasing the performance of a task through stable experience of the task.

[0045] A robot refers to a machine that automatically processes or operates a given task by its own ability. In particular, a robot with the ability to recognize the environment and determine the execution actions by itself can be called an intelligent robot. According to the purpose of use or field, robots can be classified into industrial, medical, household, military, etc. Robots can perform various physical operations, such as moving robot joints using actuators or motors. Mobile robots also include driven wheels, brakes, thrusters, etc., allowing them to travel on the ground or fly in the air.

[0046] Autonomous driving refers to the technology of self-driving, and an autonomous vehicle refers to a vehicle that drives without user control or with minimal user control. For example, autonomous driving can include maintaining the lane during movement, automatically adjusting the speed (such as adaptive cruise control), driving automatically along a set route, and automatically setting a route when a destination is set. Vehicles cover vehicles equipped with an internal combustion engine, hybrid vehicles equipped with an internal combustion engine and an electric motor, and electric vehicles equipped with an electric motor, and can include trains, motorcycles, etc. as well as cars. Autonomous vehicles can be regarded as robots with autonomous driving functions.

[0047] Extended reality is collectively referred to as VR, AR, and MR. VR technology provides real-world objects and backgrounds only through computer graphics (CG) images. AR technology provides virtual CG images on top of real object images. MR technology is a CG technology that combines virtual objects into the real world. The similarity between MR technology and AR technology is that they display real objects and virtual objects together. However, the difference is that in AR technology, virtual objects are used as a supplementary form of real objects, while in MR technology, virtual objects and real objects are used as equal individuals.

[0048] NR supports multiple parameter sets (and / or multiple subcarrier spacings (SCS)) to support various 5G services. For example, if the SCS is 15 kHz, a wide area can be supported in the traditional cellular band. If the SCS is 30 kHz / 60 kHz, dense cities, lower latency, and wider carrier bandwidth can be supported. If the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz can be supported to overcome phase noise.

[0049] NR frequency bands can be defined as two types of frequency ranges, namely, FR1 and FR2. The numerical values of the frequency ranges can change. For example, the two types of frequency ranges (FR1 and FR2) can be as shown in Table 1 below. For ease of explanation, in the frequency ranges used in the NR system, FR1 can mean "below 6 GHz range", FR2 can mean "above 6 GHz range" and can be called millimeter wave (mmW).

[0050] [Table 1]

[0051] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 450 MHz - 6000 MHz 15, 30, 60 kHz FR2 24250 MHz - 52600 MHz 60, 120, 240 kHz

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

[0053] [Table 2]

[0054] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 410 MHz - 7125 MHz 15, 30, 60 kHz FR2 24250 MHz - 52600 MHz 60, 120, 240 kHz

[0055] Here, the radio communication technologies implemented in the wireless device in the present disclosure may include narrowband Internet of Things (NB-IoT) technology for low-power communication, as well as LTE, NR, and 6G. For example, NB-IoT technology can be an example of low-power wide area network (LPWAN) technology, can be implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above names. Additionally and / or alternatively, the radio communication technologies implemented in the wireless device in the present disclosure can communicate based on LTE-M technology. For example, LTE-M technology can be an example of LPWAN technology and is known by various names such as enhanced machine-type communication (eMTC). For example, LTE-M technology can be implemented in at least one of various specifications such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth-limited (non-BL), 5) LTE-MTC, 6) LTE machine-type communication, and / or 7) LTE M, and is not limited to the above names. Additionally and / or alternatively, the radio communication technologies implemented in the wireless device in the present disclosure may include at least one of ZigBee, Bluetooth, and / or LPWAN considering low-power communication, and are not limited to the above names. For example, ZigBee technology can generate a personal area network (PAN) associated with small / low-power digital communication based on various specifications such as IEEE 802.15.4, and can be known by various names.

[0056] Figure 2 An example of a wireless device showing an implementation manner applying the present disclosure.

[0057] In Figure 2In [the description], the first wireless device 100 and / or the second wireless device 200 can be implemented in various forms according to usage scenarios / services. For example, {the first wireless device 100 and the second wireless device 200} can correspond to Figure 1 at least one of {wireless devices 100a to 100f and BS200}, {wireless devices 100a to 100f and wireless devices 100a to 100f}, and / or {BS200 and BS200} of [a certain system]. The first wireless device 100 and / or the second wireless device 200 can be configured by various components, devices / parts, and / or modules.

[0058] The first wireless device 100 can include at least one transceiver (e.g., transceiver 106), at least one processing chip (e.g., processing chip 101), and / or one or more antennas 108.

[0059] The processing chip 101 can include at least one processor (e.g., processor 102) and at least one memory (e.g., memory 104). Additionally and / or alternatively, the memory 104 can be placed outside the processing chip 101.

[0060] The processor 102 can control the memory 104 and / or the transceiver 106, and can be adapted to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts described in this disclosure. For example, the processor 102 can process the information in the memory 104 to generate first information / signals, and then send radio signals including the first information / signals through the transceiver 106. The processor 102 can receive radio signals including second information / signals through the transceiver 106, and then store the information obtained by processing the second information / signals in the memory 104.

[0061] The memory 104 can be operably connected to the processor 102. The memory 104 can store various types of information and / or instructions. The memory 104 can store firmware and / or software code 105 that implements codes, commands, and / or command sets, which, when executed by the processor 102, execute the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, the firmware and / or software code 105 can implement instructions that, when executed by the processor 102, execute the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, the firmware and / or software code 105 can control the processor 102 to execute one or more protocols. For example, the firmware and / or software code 105 can control the processor 102 to execute one or more layers of a radio interface protocol.

[0062] In this document, the processor 102 and the memory 104 can be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 106 can be connected to the processor 102 and send and / or receive radio signals via one or more antennas 108. Each transceiver 106 can include a transmitter and / or a receiver. The transceiver 106 can be used interchangeably with the radio frequency (RF) unit. In this disclosure, the first wireless device 100 can represent a communication modem / circuit / chip.

[0063] The second wireless device 200 can include at least one transceiver (e.g., transceiver 206), at least one processing chip (e.g., processing chip 201), and / or one or more antennas 208.

[0064] The processing chip 201 can include at least one processor (e.g., processor 202) and at least one memory (e.g., memory 204). Additionally and / or alternatively, the memory 204 can be placed outside the processing chip 201.

[0065] The processor 202 can control the memory 204 and / or the transceiver 206, and can be adapted to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts described in this disclosure. For example, the processor 202 can process the information within the memory 204 to generate a third information / signal, and then send a radio signal including the third information / signal via the transceiver 206. The processor 202 can receive a radio signal including a fourth information / signal via the transceiver 106, and then store the information obtained by processing the fourth information / signal in the memory 204.

[0066] The memory 204 can be operatively connected to the processor 202. The memory 204 can store various types of information and / or instructions. The memory 204 can store firmware and / or software code 205 that implements code, commands, and / or command sets, which when executed by the processor 202 perform the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, the firmware and / or software code 205 can implement instructions that, when executed by the processor 202, perform the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, the firmware and / or software code 205 can control the processor 202 to execute one or more protocols. For example, the firmware and / or software code 205 can control the processor 202 to execute one or more layers of a radio interface protocol.

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

[0068] Hereinafter, the hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers can be implemented by one or more processors 102 and 202, but are not limited thereto. For example, the one or more processors 102 and 202 can 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). The one or more processors 102 and 202 can 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, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. The one or more processors 102 and 202 can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure, and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 can receive signals (e.g., baseband signals) from the one or more transceivers 106 and 206, and obtain PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, programs, suggestions, methods, and / or operation flowcharts disclosed in this disclosure.

[0069] One or more processors 102 and 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processor devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors 102 and 202. For example, the one or more processors 102 and 202 may be configured by a collection of a communication control processor, an application processor (AP), an electronic control unit (ECU), a central processing unit (CPU), a graphics processing unit (GPU), and a memory control processor.

[0070] One or more memories 104, 204 may be associated with the one or more processors 102, 202 and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104, 204 may include random access memory (RAM), dynamic RAM (DRAM), read only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, non-volatile memory, a hard disk drive, registers, a cache memory, a computer readable storage medium, and / or a combination thereof. The one or more memories 104, 204 may be located inside and / or outside of the one or more processors 102, 202. In addition, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 via various technologies such as wired or wireless connections.

[0071] One or more transceivers 106, 206 may send user data, control information, wireless signals / channels, etc. mentioned in the descriptions, features, processes, suggestions, methods, and / or flowcharts of operations disclosed herein to one or more other devices. The one or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, features, processes, suggestions, methods, and / or flowcharts of operations disclosed herein from one or more other devices. For example, the one or more transceivers 106, 206 may be associated with the one or more processors 102, 202 and may send and receive wireless signals. For example, the one or more processors 102, 202 may control the one or more transceivers 106, 206 to send user data, control information, wireless signals, etc. to one or more other devices. In addition, the one or more processors 102, 202 may control the 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 associated with one or more antennas 108, 208. Additionally and / or alternatively, the one or more transceivers 106, 206 may include the one or more antennas 108, 208. The one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, features, processes, suggestions, methods, and / or flowcharts of operations disclosed herein via the one or more antennas 108, 208. As used herein, the 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 the received user data, control information, radio signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, radio signals / channels, etc. using the one or more processors 102, 202. The one or more transceivers 106, 206 may use the one or more processors 102, 202 to convert the processed user data, control information, radio signals / channels, etc. from baseband signals to RF band signals. To this end, the one or more transceivers 106, 206 may include (analog) oscillators and / or filters. For example, the one or more transceivers 106, 206 may, under the control of the one or more processors 102, 202, upconvert an OFDM baseband signal to an OFDM signal via an (analog) oscillator and / or filter and transmit the upconverted OFDM signal at a carrier frequency. The one or more transceivers 106, 206 may receive an OFDM signal at a carrier frequency and downconvert the OFDM signal to an OFDM baseband signal via an (analog) oscillator and / or filter under the control of the one or more processors 102, 202.

[0074] Although Figure 2 not shown in, wireless devices 100 and 200 may also include additional components. The additional components 140 may be configured differently according to the types of the wireless devices 100 and 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 coupled to the one or more processors 102 and 202 via various techniques such as wired or wireless connections.

[0075] In an implementation of the present disclosure, the UE may operate as a transmitting device in the uplink (UL) and as a receiving device in the downlink (DL). In an implementation of the present disclosure, the BS may operate as a receiving device in the UL and as a transmitting device in the DL. Hereinafter, for convenience of description, it is mainly assumed that the first wireless device 100 acts as the UE and the second wireless device 200 acts as the BS. For example, a processor 102 connected to, installed on, or initiated in the first wireless device 100 may be adapted to perform UE behavior according to an implementation of the present disclosure or control a transceiver 106 to perform UE behavior according to an implementation of the present disclosure. A processor 202 connected to, installed on, or initiated in the second wireless device 200 may be adapted to perform BS behavior according to an implementation of the present disclosure or control a transceiver 206 to perform BS behavior according to an implementation of the present disclosure.

[0076] In the present disclosure, the BS is also referred to as a Node B (NB), an eNode B (eNB), or a gNB.

[0077] Figure 3 An example of a UE to which an implementation of the present disclosure is applied is shown.

[0078] Figure 3 An example of a UE to which an implementation of the present disclosure is applied is shown.

[0079] Referring to Figure 3 the first wireless device 100 corresponding to the UE 100 may be Figure 2 as shown.

[0080] The UE 100 includes a processor 102, a 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 subscriber identity module (SIM) card 145, a speaker 146, and a microphone 147.

[0081] The processor 102 may be adapted to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in the present disclosure. The processor 102 may be adapted to control one or more other components of the UE 100 to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in the present disclosure. Layers of the radio interface protocol may be implemented in the processor 102. The processor 102 may include an ASIC, other chip sets, 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, a GPU, and a modem (modulator and demodulator). Examples of the processor 102 can be found in manufactured SNAPDRAGON TMSeries processors, manufactured EXYNOS TM series processors, a series of processors manufactured, manufactured HELIO TM series processors, manufactured ATOM TM series processors or corresponding next-generation processors.

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

[0083] Transceiver 106 is operatively coupled to processor 102 and transmits and / or receives radio signals. Transceiver 106 includes a transmitter and a receiver. Transceiver 106 may include baseband circuitry to process radio frequency signals. Transceiver 106 controls one or more antennas 108 to transmit and / or receive radio signals.

[0084] Power management module 141 manages the power of processor 102 and / or transceiver 106. Battery 142 supplies power to power management module 141.

[0085] Display 143 outputs the results processed by processor 102. Keypad 144 receives inputs to be used by processor 102. Keypad 144 may be displayed on display 143.

[0086] SIM card 145 is an integrated circuit designed to securely store the International Mobile Subscriber Identity (IMSI) number and its associated key for identifying and authenticating subscribers on mobile phone devices (such as mobile phones and computers). Contact information may also be stored on many SIM cards.

[0087] Speaker 146 outputs the sound-related results processed by processor 102. Microphone 147 receives sound-related inputs to be used by processor 102.

[0088] Figure 4 is a block diagram of a next-generation cellular network.

[0089] The 5G Core (5GC) may include various components, some of which areFigure 5 As shown, such as the Access and Mobility Management Function (AMF) (410), Session Management Function (SMF) (420), Policy Control Function (PCF) (430), User Plane Function (UPF) (440), Application Function (AF) (450), Unified Data Management (UDM) (460), and Non-3rd Generation Partnership Project (3GPP) Interworking Function (N3IWF) (490).

[0090] The UE 100 is connected to the data network via the UPF 440 through the Next Generation Radio Access Network (NG-RAN) including the gNB 20.

[0091] Data services can also be provided to the UE 100 via untrusted non-3GPP access (such as Wireless Local Area Network (WLAN)). To connect the non-3GPP access to the core network, the N3IWF 490 can be deployed.

[0092] The shown N3IWF 490 performs the function of managing the interworking between non-3GPP access and the 5G system. When the UE 100 is associated with non-3GPP access (e.g., WiFi, also known as IEEE 801.11), the UE 100 can be associated with the 5G system via the N3IWF 490. The N3IWF 490 communicates with the AMF 410 for control signaling and communicates with the UPF 440 via the N3 interface for data transmission.

[0093] The shown AMF 410 can manage access and mobility in the 5G system. The AMF 410 can perform the function of managing Non-Access Stratum (NAS) security. The AMF 410 can perform the function of handling mobility in the idle state.

[0094] The shown UPF 440 is a gateway through which user data is sent and received. The UPF node 440 can perform all or part of the user plane functions of the Serving Gateway (S-GW) and Packet Data Network Gateway (P-GW) of the 4th generation mobile communication.

[0095] The UPF 440 serves as the demarcation point between the next-generation radio access network (NG-RAN) and the core network and is the element that maintains the data path between the gNB 20 and the SMF 420. Additionally, when the UE 100 moves across the area served by the gNB 20, the UPF 440 serves as the mobility anchor. The UPF 440 can perform the function of processing PDUs. For mobility within the NG-RAN (the next-generation radio access network defined in 3GPP Release 15 and subsequent releases), the UPF can route packets. The UPF 440 can also be used as an anchor for mobility with other 3GPP networks (RANs defined before 3GPP Release 15, such as UTRAN, E-UTRAN (Evolved UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access Network), or GERAN (Global System for Mobile Communications (GSM) / EDGE (Global Evolution Enhanced Data Rate) Radio Access Network). The UPF 440 can correspond to the termination point of the data interface to the data network.

[0096] The illustrated PCF 430 is a node that controls the operator's policies.

[0097] The illustrated AF 450 is a server for providing multiple services to the UE 100.

[0098] The illustrated UDM 460 is a type of server that manages subscriber information, such as the Home Subscriber Server (HSS) in fourth-generation mobile communications. The UDM 460 stores and manages subscriber information in the Unified Data Repository (UDR).

[0099] The illustrated SMF 420 can perform the function of assigning an Internet Protocol (IP) address to the UE. The SMF 420 can also control the Protocol Data Unit (PDU) session.

[0100] As a reference point, the reference numerals of the AMF 410, SMF 420, PCF 430, UPF 440, AF 450, UDM460, N3IWF 490, gNB 20, or UE 100 may be omitted in this document.

[0101] The fifth-generation mobile communications supports multiple parameter sets or subcarrier spacings (SCSs) to support various 5G services. For example, an SCS of 15 kHz supports wide-area coverage in traditional cellular bands; an SCS of 30 kHz / 60 kHz supports dense cities, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports a bandwidth greater than 24.25 GHz to overcome phase noise.

[0102] Figure 5 An example 5G system architecture in which the implementations of this specification can be applied is illustrated.

[0103] The 5G system (5GS; 5G System) architecture consists of the following network functions (NFs).

[0104] - AUSF (Authentication Server Function)

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

[0106] - DN (Data Network), such as operator services, Internet access, or third-party services

[0107] - USDF (Unstructured Data Storage Function)

[0108] - NEF (Network Exposure Function)

[0109] - I-NEF (Intermediate NEF)

[0110] - NRF (Network Repository Function)

[0111] - NSSF (Network Slice Selection Function)

[0112] - PCF (Policy Control Function)

[0113] - SMF (Session Management Function)

[0114] - UDM (Unified Data Management)

[0115] - UDR (Unified Data Repository)

[0116] - UPF (User Plane Function)

[0117] - UCMF (UE Radio Capability Management Function)

[0118] - AF (Application Function)

[0119] - UE (User Equipment)

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

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

[0122] - NWDAF (Network Data Analytics Function)

[0123] - CHF (Charging Function)

[0124] In addition, the following network functions may be considered.

[0125] - N3IWF (Non-3GPP Interworking Function)

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

[0127] -W-AGF (Wired Access Gateway Function)

[0128] Figure 5 Shows the 5G system architecture for a non-roaming scenario represented using reference points that illustrate how various network functions interact with each other.

[0129] In Figure 5 For the sake of clarity of the point-to-point diagram, UDSF, NEF, and NRF are not described. However, all the network functions shown can interact with UDSF, UDR, NEF, and NRF as required.

[0130] For the sake of clarity, the connection between UDR and other NFs (e.g., PCF) is not shown in Figure 5 For the sake of clarity, Figure 5 the connection between NWDAF and other NFs (e.g., PCF) is not shown in

[0131] The 5G system architecture includes the following reference points.

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

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

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

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

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

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

[0138] The following reference points show the interactions that exist between NF services in the NFs.

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

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

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

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

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

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

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

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

[0147] - N15: Reference point between the PCF and the AMF in the case of a non-roaming scenario, and between the PCF of the visited network and the AMF in the case of a roaming scenario.

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

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

[0150] In some cases, it may be necessary to connect two NFs to each other to serve the UE.

[0151] <Registration process>

[0152] Describe the registration process. Reference can be made to Section 4.2.2.2 of 3GPP TS23.502 V16.3.0 (2019-12).

[0153] Figure 6 and Figure 7 shows an example of the registration process implementing the present disclosure.

[0154] The UE needs to register with the network to obtain authorization to receive services, to enable mobility tracking and to achieve reachability. The UE initiates the registration process using one of the following registration types:

[0155] - Initial registration to 5GS; or

[0156] - Mobility registration update; or

[0157] - Periodic registration update; or

[0158] - Emergency registration.

[0159] Figure 6 and Figure 7 The general registration process in and applies to all these registration processes, but the periodic registration update does not need to include all the parameters used in other registration cases.

[0160] Figure 6 and Figure 7 The general registration process in is also used for the case where the UE registers in 3GPP access when it has already been registered in non-3GPP access, and vice versa. The registration in 3GPP access when the UE has already been registered in a non-3GPP access scenario may require a change of AMF.

[0161] First, describeFigure 6 process

[0162] (1) Step 1: The UE sends a registration request message to the (R)AN. The registration request message corresponds to the AN message.

[0163] The registration request message may include AN parameters. In the case of NG-RAN, the AN parameters include, for example, a 5G SAE temporary mobile subscriber identity (5G-S-TMSI) or a globally unique AMF ID (GUAMI), the selected public land mobile network (PLMN) ID (or PLMN ID and network identifier (NID)), and the requested network slice selection assistance information (NSSAI). The AN parameters also include the establishment cause. The establishment cause provides the reason for requesting the establishment of an RRC connection. Whether and how the UE includes the requested NSSAI as part of the AN parameters depends on the value of the access stratum connection establishment NSSAI containment mode parameter.

[0164] The registration request message may include a registration type. The registration type indicates whether the UE wants to perform an initial registration (i.e., the UE is in the RM-DEREGISTERED state), a mobility registration update (i.e., the UE is in the RM-REGISTERED state and initiates the registration process due to mobility or because the UE needs to update its capabilities or protocol parameters or requests to change the set of network slices it is allowed to use), a periodic registration update (i.e., the UE is in the RM-REGISTERED state and initiates the registration process due to the expiration of the periodic registration update timer), or an emergency registration (i.e., the UE is in a restricted service state).

[0165] When the UE is performing an initial registration, the UE shall indicate its UE identity in the registration request message as follows, listed in descending order of preference:

[0166] i) If the UE has a valid evolved packet system EPS GUTI, the 5G globally unique temporary identifier (5G-GUTI) mapped from the EPS GUTI.

[0167] ii) The native 5G-GUTI assigned by the PLMN to which the UE is attempting to register (if available);

[0168] iii) The native 5G-GUTI assigned by an equivalent PLMN to the PLMN to which the UE is attempting to register (if available);

[0169] iv) The native 5G-GUTI assigned by any other PLMN (if available);

[0170] v) Otherwise, the UE shall include its subscriber concealed identifier (SUCI) in the registration request message.

[0171] When the UE performing the initial registration has both a valid EPS GUTI and a native 5G-GUTI, the UE shall also indicate the native 5G-GUTI as an additional GUTI. If more than one native 5G-GUTI is available, the UE shall select the 5G-GUTI in descending order of preference among the entries (ii) to (iv) in the list above.

[0172] When the UE is performing the initial registration using the native 5G-GUTI, the UE shall indicate the relevant GUAMI information in the AN parameters. When the UE performs the initial registration using its SUCI, the UE shall not indicate any GUAMI information in the AN parameters.

[0173] For emergency registration, if the UE does not have an available valid 5G-GUTI, the SUCI shall be included; when the UE does not have a Subscriber Permanent Identifier (SUPI) and does not have a valid 5G-GUTI, the Permanent Equipment Identifier (PEI) shall be included. In other cases, the 5G-GUTI is included and it indicates the last serving AMF.

[0174] The registration request message may also include security parameters, PDU session status, etc. The security parameters are used for authentication and integrity protection. The PDU session status indicates the previously established PDU sessions in the UE. When the UE is connected to two AMFs belonging to different PLMNs via 3GPP access and non-3GPP access, the PDU session status indicates the established PDU sessions of the current PLMN in the UE.

[0175] (2) Step 2: The (R)AN selects an AMF.

[0176] If the 5G-S-TMSI or GUAMI is not included, or the 5G-S-TMSI or GUAMI does not indicate a valid AMF, the (R)AN selects an AMF based on the (R)AT and the requested NSSAI (if available).

[0177] If the UE is in the CM-CONNECTED state, the (R)AN may forward the registration request message to the AMF based on the UE's N2 connection.

[0178] If the (R)AN cannot select an appropriate AMF, it forwards the registration request message to the configured AMF in the (R)AN to perform AMF selection.

[0179] (3) Step 3: The (R)AN sends a registration request message to the new AMF. The registration request message corresponds to the N2 message.

[0180] The registration request message may include all the information and / or a part of the information included in the registration request message received from the UE described in Step 1.

[0181] The registration request message may include N2 parameters. When using NG-RAN, the N2 parameters include the selected PLMN ID (or PLMN ID and NID), location information related to the cell where the UE is resident and the cell identity, and a UE context request indicating that a UE context including security information needs to be set up at the NG-RAN. When using NG-RAN, the N2 parameters shall also include the establishment cause.

[0182] If the registration type indicated by the UE is a periodic registration update, steps 4 to 19 may be omitted.

[0183] (4) Step 4: If the 5G-GUTI of the UE is included in the registration request message and the serving AMF has changed since the last registration procedure, the new AMF may invoke the Namf_Communication_UEContextTransfer service operation on the old AMF including the complete registration request non-access stratum (NAS) message to request the SUPI and UE context of the UE.

[0184] (5) Step 5: The old AMF may respond to the new AMF for the Namf_Communication_UEContextTransfer by including the SUPI and UE context of the UE.

[0185] (6) Step 6: If the SUCI is not provided by the UE or retrieved from the old AMF, the identity request procedure may be initiated by the new AMF sending an identity request message to the UE requesting the SUCI.

[0186] (7) Step 7: The UE may respond with an identity response message including the SUCI. The UE obtains the SUCI by using the provisioned public key of the home PLMN (HPLMN).

[0187] (8) Step 8: The new AMF may decide to initiate UE authentication by invoking the AUSF. In this case, the new AMF selects the AUSF based on the SUPI or SUCI.

[0188] (9) Step 9: Authentication / security may be established by the UE, the new AMF, the AUSF, and / or the UDM.

[0189] (10) Step 10: If the AMF has changed, the new AMF can notify the old AMF of the UE's successful registration with the new AMF by invoking the Namf_Communication_RegistrationCompleteNotify service operation. If the authentication / security process fails, the registration will be rejected, and the new AMF can invoke the Namf_Communication_RegistrationCompleteNotify service operation with a rejection indication reason code to the old AMF. The old AMF can continue as if it had never received the UE context transfer service operation.

[0190] (11) Step 11: If the PEI is not provided by the UE or retrieved from the old AMF, the identity request process can be initiated by the new AMF sending an identity request message to the UE to retrieve the PEI. The PEI shall be transmitted encrypted, unless the UE performs an emergency registration and cannot be authenticated.

[0191] (12) Step 12: Optionally, the new AMF can initiate an ME identity check by invoking the N5g-eir_EquipmentIdentityCheck_Get service operation.

[0192] Now, describe the Figure 6 process after Figure 7 the process.

[0193] (13) Step 13: If the following Step 14 is to be performed, the new AMF can select the UDM based on the SUPI, and then the UDM can select a UDR instance.

[0194] (14) Step 14: The new AMF can register with the UDM.

[0195] (15) Step 15: The new AMF can select the PCF.

[0196] (16) Step 16: The new AMF can optionally perform AM policy association establishment / modification.

[0197] (17) Step 17: The new AMF can send an update / release SM context message (e.g., Nsmf_PDUSession_UpdateSMContext and / or Nsmf_PDUSession_ReleaseSMContext) to the SMF.

[0198] (18) Step 18: If the new AMF and the old AMF are in the same PLMN, the new AMF can send a UE context modification request to the N3IWF / TNGF / W-AGF.

[0199] (19) Step 19: The N3IWF / TNGF / W-AGF may send a UE context modification response to the new AMF.

[0200] (20) Step 20: After the new AMF receives the response message from the N3IWF / TNGF / W-AGF in Step 19, the new AMF may register with the UDM.

[0201] (21) Step 21: The new AMF sends a registration acceptance message to the UE.

[0202] The new AMF sends a registration acceptance message to the UE, indicating that the registration request has been accepted. If the new AMF allocates a new 5G-GUTI, the 5G-GUTI is included. If the UE is already in the RM-REGISTERED state via another access in the same PLMN, the UE shall use the 5G-GUTI received in the registration acceptance message for both registrations. If the 5G-GUTI is not included in the registration acceptance message, the UE shall also use the 5G-GUTI allocated for the existing registration for the new registration. If the new AMF allocates a new registration area, it shall send the registration area to the UE via the registration acceptance message. If the registration area is not included in the registration acceptance message, the UE shall consider the old registration area as valid. In the case where mobility restrictions apply to the UE and the registration type is not an emergency registration, the mobility restrictions are included. The new AMF indicates the established PDU sessions to the UE in the PDU session state. The UE locally removes any internal resources related to the PDU sessions that are not marked as established in the received PDU session state. When the UE is connected to two AMFs belonging to different PLMNs via 3GPP access and non-3GPP access, the UE locally removes any internal resources related to the PDU sessions of the current PLMN that are not marked as established in the received PDU session state. If the PDU session state information is in the registration request message, the new AMF shall indicate the PDU session state to the UE.

[0203] The allowed NSSAI provided in the registration acceptance message is valid within the registration area, and it applies to all PLMNs whose tracking area is included in the registration area. The mapping of the allowed NSSAI is the mapping of each S-NSSAI of the allowed NSSAI to the HPLMN S-NSSAI. The mapping of the configured NSSAI is the mapping of each S-NSSAI of the configured NSSAI for the serving PLMN to the HPLMN S-NSSAI.

[0204] In addition, optionally, the new AMF performs UE policy association establishment.

[0205] (22) Step 22: When the UE successfully updates itself, the UE may send a registration completion message to the new AMF.

[0206] The UE may send a registration completion message to the new AMF to confirm whether a new 5G-GUTI has been allocated.

[0207] (23) Step 23: For a registration via 3GPP access, if the new AMF does not release the signaling connection, the new AMF may send the RRC inactivity assistance information to the NG-RAN. For a registration via non-3GPP access, if the UE is also in the CM-CONNECTED state on 3GPP access, the new AMF may send the RRC inactivity assistance information to the NG-RAN.

[0208] (24) Step 24: The new AMF may perform information updates towards the UDM.

[0209] (25) Step 25: The UE may perform network slice specific authentication and authorization procedures.

[0210] <URSP in the VPLMN>

[0211] Currently, the URSP is only controlled and determined by the HPLMN. Therefore, in order to influence the URSP determination, the AF needs to provide input to the HPLMN. The application guidance for URSP determination can be used for edge services or for location-based services, which means that there may be a situation where the URSP rules determined based on the application guidance can only be applied and are effective when the UE is in any specific VPLMN in a roaming scenario. In any case, in this situation, the AF may need to provide the application guidance for URSP determination to all PLMNs to which its subscribers may roam into the VPLMN, and the AF has a service level agreement with them. Additionally, if the AF includes a geographical area as a spatial validity condition in the application guidance for URSP determination, the NEF may need to convert this information into a 3GPP identifier (e.g., TAI). For this purpose, the NEF needs to know the 3GPP identifier (e.g., TAI) of the VPLMN.

[0212] The AF provides the application guidance for URSP determination to the PLMN that provides the relevant service or routes the relevant traffic (i.e., via the NEF of this PLMN to the UDR). The H-PCF of the roaming UE obtains the application guidance for URSP determination from the VPLMN by requesting the V-PCF to subscribe to the V-UDR for notifications on data creation / modification of the UE. When service parameters are available for UE policy association, the V-PCF subscribes to the V-UDR on behalf of the H-PCF by adding a new PCRT requesting notification. If the AF provides input to the V-UDR via the V-NEF, the V-PCF provides the data notified by the V-UDR to the H-PCF.

[0213] When supplying application guidance for URSP determination for all HPLMNs to which its subscribers may roam in the VPLMN, the AF may include the PLMN ID to indicate that the supplied information is for roamers from that PLMN ID. The application data in the UDR is extended to provide the PLMN ID as a Data Key. Table 3 shows "PLMNID" as an additional Data Key.

[0214] [Table 3]

[0215]

[0216] This solution reuses the existing Npcf_UEPolicyControl service so that the H-PCF can receive new / updated service parameters for the UE using a new PCRT subscription, and so that the V-PCF can notify the H-PCF and provide the service parameters for the UE to the H-PCF.

[0217] If the S-NSSAI subscription information indicates that the DNN, S-NSSAI are subscribed to and LBO roaming is allowed, the H-PCF generates a new URSP rule or updates an existing URSP rule with the same service descriptor as provided in the service parameters.

[0218] The H-PCF uses the existing procedure to send the URSP rule to the UE. In addition, the H-PCF subscribes to "change of PLMN", and then when the UE moves to a different PLMN, the H-PCF removes or updates the URSP rule sent to the UE to remove the RSD for the services routed through the VPLMN registered by the UE. When the V-PCF requests termination of the UE policy association, the H-PCF also removes or updates the sent URSP rule to remove the RSD for the services routed through the VPLMN.

[0219] <Disclosure of this specification>

[0220] In a roaming scenario, a method for an HPLMN to receive information from a VPLMN to generate URSP rules can be proposed. Additionally, a method for providing URSP rules to the UE can be proposed.

[0221] The method for efficiently providing service parameters from the VPLMN to the HPLMN can consist of a combination of one or more of the following operations / configurations / steps.

[0222] In this specification, service parameters can be used interchangeably with service parameter information, AF application guidance, AF application guidance information, AF guidance, AF guidance information, AF request information, AF input, service data, UDR stored data, etc.

[0223] This specification is not limited to the service parameters provided by the VPLMN to the HPLMN. Additionally, it can be applied to various information provided by the VPLMN to the HPLMN, such as events, supplementary information, policy control related information, etc.

[0224] In this specification, UE (User Equipment) and terminal are used interchangeably.

[0225] In this specification, AF (Application Function), AS (Application Server), and server are described interchangeably.

[0226] This specification mainly describes the proposed content. The basic operations of the 5G system can be referred to in TS23.501 V17.6.0, TS23.502 V17.6.0, TS23.503 V17.6.0, etc.

[0227] Figure 8a and Figure 8b shows a process according to an embodiment of this specification.

[0228] Figure 8a and Figure 8b shows a process for determining the URSP based on the service parameters obtained from the V-PLMN.

[0229] 1. The UE can register to the 5GC and perform UE policy association between the AMF and the H-PCF via the V-PCF. Additionally, the H-PCF can subscribe to the V-PCF using the new PCRT "received service parameters". If available, the V-PCF can provide the service parameters.

[0230] 2. Based on the new PCRT received from the H-PCF, when creating a UE policy association for a subscriber of this HPLMN, if the V-UDR cannot be subscribed, the V-PCF can subscribe to receive service parameters from the AF to determine the URSP rules for any UE registered in this VPLMN for this HPLMN.

[0231] Assuming the AF provides application guidance for URSP determination to the VPLMN, the V-PCF can include the VPLMN DNN and S-NSSAI in the subscription request to the UDR.

[0232] 3. To provide application guidance for URSP determination as specified in clause 4.15.6.10 of TS23.502 V17.6.0, the AF can create a new request.

[0233] 4 - 6. As specified in steps 2 to 4 of clause 4.15.6.7 of TS 23.502 V17.6.0, the AF may send its request to the NEF, and the NEF may store the AF request information in the UDR and may respond to the AF. The NEF may be a V - NEF, and the UDR may be a V - UDR.

[0234] The AF request may be for any UE (all UEs) of the HPLMN registered in the VPLMN. Therefore, the V - NEF may authorize the request based on the service level agreement between the AF and the VPLMN (e.g., based on the AF Id) according to the local policy without requesting any service - specific authorization from the UDM, as specified in clause 4.15.6.10 of TS 23.502 V17.6.0.

[0235] The case where the AF may require targeting a specific UE or group of UEs is not applicable to this solution because service - specific authorization for a single UE or group of UEs from the NEF to the UDM must be performed for the AF request, as specified in clause 4.15.6.10 of TS 23.502 V17.6.0.

[0236] 7. The V - PCF may receive a Nudr_DM_Notify notification of data change from the V - UDR.

[0237] 8. The V - PCF may send the data change notification (including the service parameters received from the UDR) from the V - UDR of the invoked Npcf_UEPolicyControl_Update to the H - PCF. The V - PCF may also provide the H - PCF with the mapping of VPLMN S - NSSAI to HPLMN S - NSSAI and the mapping of VPLMN DNN to HPLMN DNN.

[0238] 9. The H - PCF may determine the URSP rules to be sent to the UE based on the service parameters received from the V - PCF, the S - NSSAI subscription information for the SUPI, and the DNN and S - NSSAI retrieved from the UE context policy control subscription information from the UDR. The H - PCF may generate new URSP rules or update the existing URSP rules sent to the UE for the same service descriptor to include the new RSD with the DNN and S - NSSAI provided by the V - PCF, and then consider the information provided by the V - PCF to set the RSD precedence and validity conditions.

[0239] For example, the H - PCF may replace any URSP rules related to the routing descriptor including the DNN and S - NSSAI.

[0240] 10. The H-PCF may provide the URSP rules to the UE via the V-PCF by using the UE configuration update procedure for transparent UE policy delivery as specified in clause 4.2.4.3 of TS 23.502 V17.6.0. The H-PCF may provide the S-NSSAI and DNN values of the VPLMN to the UE in the RSD component of the URSP rules.

[0241] 11. The UE may need to send traffic, for example, to edge services. Therefore, the UE determines the URSP rules applicable to the traffic. For the URSP rules applicable to the VPLMN, if the S-NSSAI value is in the allowed NSSAI rather than in the mapping of the allowed NSSAI, the UE may consider the RSD valid.

[0242] 12. If there is no PDU session that matches all components in the selected RSD within the URSP rules, the UE may establish a PDU session. The UE may provide both the S-NSSAI of the VPLMN (e.g., the S-NSSAI in the URSP rules) and the S-NSSAI of the HPLMN obtained from the mapping of the allowed NSSAI to the HPLMN S-NSSAI, as described in clause 5.15.5.3 of TS 23.501 V17.6.0. The UE may include the DNN of the VPLMN, e.g., the DNN in the URSP rules (if provided as the DNN requested by the UE), as described in clause 6.6.2.1 of TS 23.503 V17.6.0. If the DNN requested by the UE is supported but not subscribed, the AMF may check if there is a mapping to the configured HPLMN DNN and then use it for subscription checking. The AMF uses the DNN requested by the UE as the selected DNN and then performs SMF selection. The AMF may send both the selected DNN (e.g., the DNN requested by the UE) and the DNN value of the HPLMN to the SMF. The SMF may use the DNN value of the HPLMN and the S-NSSAI value of the HPLMN for subscription checking, as described in clause 4.3.2.2.1 of TS 23.502 V17.6.0.

[0243] 13. The UE may communicate with an application server (e.g., an edge application server).

[0244] For the procedure shown in Figure 8, the H-PCF, V-PCF, H-UDR, UE, and AMF shall support the following actions or functions:

[0245] H-PCF:

[0246] - May subscribe to a new PCRT "Received Service Parameters".

[0247] - It can receive service parameters for the UE policy control association established with the V-PCF.

[0248] - It can determine the URSP rules by considering the S-NSSAI subscription information based on the data provided by the AF and received via the V-UDR and V-PCF.

[0249] - Extended to include S-NSSAI subscription information on whether LBO is allowed.

[0250] V-PCF:

[0251] - If the H-PCF provides the PCRT, it can subscribe to the V-UDR to be notified about the creation / modification of service parameters for roaming UEs.

[0252] - It can provide the service parameters notified by the V-UDR to the H-PCF.

[0253] H-UDR:

[0254] - The S-NSSAI subscription information needs to include an indication of whether LBO roaming is allowed for the DNN and S-NSSAI.

[0255] UE:

[0256] - For the URSP rules applicable in the VPLMN, if the S-NSSAI value is in the allowed NSSAI but not in the mapping of the allowed NSSAI, the UE can consider the RSD as valid.

[0257] AMF:

[0258] - At the time of PDU session establishment, using the DNN requested by the UE as the selected DNN, for subscription checking, the AMF can map the DNN requested by the UE to the HPLMN DNN.

[0259] In the above process, the service parameters provided by the AF can be provided to apply to all PLMN subscribers. In this case, even if the service parameter information is the same, the V-PCF can provide it through the signaling exchanged between the V-PCF and the H-PCF for each UE.

[0260] For example, if UE#1 that has subscribed to the HPLMN where the service parameters are applied roams to the VPLMN, the V-PCF of the VPLMN can use the policy association established with the H-PCF for UE#1 to provide the service parameters to the H-PCF. If another UE (UE#2) that has subscribed to the same PLMN as UE#1's HPLMN roams to the VPLMN, the V-PCF of the VPLMN uses the policy association established with the H-PCF for UE#2 to provide the service parameters to the H-PCF.

[0261] In this way, the V-PCF may repeatedly provide the same service parameters as many times as the number of H-PCF and UE, which may lead to inefficiency.

[0262] This may not be efficient in terms of signaling, because each UE will have to send a message to the HPLMN to provide the same service parameters.

[0263] I. First Embodiment

[0264] The process according to the first embodiment basically follows what is described in FIG. 8.

[0265] The content of step 8 in FIG. 8 according to the first embodiment will be described below.

[0266] 8. The V-PCF may send / provide the data received from the UDR to the H-PCF. The data may include the service parameters provided by the AF.

[0267] In this regard, the following may be applied:

[0268] 1) If the data (service parameters) are applied to all terminals (any UE) that have joined the HPLMN, the V-PCF may decide to provide / notify the data (service parameters) to the H-PCF only once. Regarding step 8, 1-1) and / or 1-2) described below may be performed.

[0269] 1-1) The V-PCF may select a UE to provide the data to the H-PCF. This may mean selecting a UE policy association to provide the data to the H-PCF.

[0270] A UE policy association may be established between the V-PCF and the H-PCF for each UE (step 1). Multiple UEs may establish a UE policy association with the V-PCF and the H-PCF. If the above data (service parameters) are applied to all terminals (any UE) that have joined the HPLMN, the V-PCF may select a UE policy association to provide the data to the H-PCF.

[0271] UE policy associations can be established for the HPLMN and for multiple H-PCFs for multiple UEs. For example, a UE policy association can be established with a first H-PCF for a first UE, and a UE policy association can be established with a second H-PCF for a second UE. In this case, the V-PCF can select one UE policy association to provide data for each H-PCF. If only one UE has a policy association (e.g., UE policy association) established with the H-PCF, the V-PCF can select the corresponding UE. If there are multiple UEs that have a policy association (e.g., UE policy association) established with the H-PCF, the V-PCF can select one of the multiple UEs.

[0272] The selection by the V-PCF can be based on various information / situations.

[0273] For example, the selection of the V-PCF can be performed based on local policies and local configurations.

[0274] For example, the selection of the V-PCF can be performed based on the number of UEs that have roamed from the HPLMN (served by the V-PCF or VPLMN). For example, if the number of UEs is greater than / exceeds a certain threshold, the V-PCF can decide to provide data to the H-PCF only once.

[0275] For example, in addition to the data provided by the UDR, if there are also UEs that need to send an Npcf_UEPolicyControl_Update message to the H-PCF due to another event / problem, the V-PCF can select the UE by taking this into account. When selecting the UE that needs to send an Npcf_UEPolicyControl_Update message to the above H-PCF, the V-PCF can send the Npcf_UEPolicyControl_Update message together with the above data to the UE.

[0276] The V-PCF can use the selected UE policy association to provide data to the H-PCF. When the V-PCF selects a UE policy connection for each of multiple H-PCFs, the V-PCF can use each selected UE policy association to provide data to the H-PCF. The V-PCF can use each selected UE policy association to send an Npcf_UEPolicyControl_Update containing the data to the H-PCF. In this case, the V-PCF can explicitly or implicitly include one or more of the following a, b, and c in the Npcf_UEPolicyControl_Update. For this purpose, new information elements can be defined in the Npcf_UEPolicyControl_Update message.

[0277] a. Information indicating that the above data applies to / is applied to all UEs (any UE (all UEs))

[0278] b. Information indicating that the above data is provided to the selected UE (or provided only once) but applies to / is applied to all UEs (any UE (all UEs))

[0279] c. Information requesting that the above data be applied to all UEs (any UE (all UEs))

[0280] 1 - 2) The V - PCF can provide the above data to the H - PCF.

[0281] To provide the above data from the V - PCF to the H - PCF, a new PCF service operation can be defined, or traditional PCF service operations can be extended and used. For example, service operations other than Npcf_UEPolicyControl_Update can be used.

[0282] The above data provision can be interpreted as the V - PCF providing data to the H - PCF without using UE policy association. Or, the above data provision can be interpreted as the V - PCF providing data to the H - PCF without using per - UE signaling. Or, the above data provision can be interpreted as the V - PCF providing data to the H - PCF through the association / signaling between PCFs.

[0283] When multiple UEs establish UE policy associations with multiple H - PCFs, the V - PCF can provide data to each of the multiple H - PCFs. The PCF can send Npcf_UEPolicyControl_Update containing the data to each of the multiple H - PCFs. In this case, the V - PCF can explicitly or implicitly include one or more of the following i and ii in the Npcf_UEPolicyControl_Update:

[0284] i. Information indicating that the above data applies to / is applied to all UEs (any UE (AllUE))

[0285] ii. Information requesting that the above data be applied to all terminals (any UE (all UEs))

[0286] 2) If the above data is applied to a specific UE in the HPLMN or UEs belonging to a specific group, the V - PCF can provide / notify the data to the H - PCF for each target UE. For example, the V - PCF can provide data to the H - PCF through the UE policy association established for the target UE with the H - PCF.

[0287] In the above (1) and (2), the determination of applying the data of the V-PCF to any UE, or a specific UE, or UEs belonging to a specific group in the HPLMN may be based on one or more of the following information.

[0288] - Information included in the service parameters provided by the AF

[0289] - Information provided by the NEF based on the service parameters provided by the AF (e.g., target UE information, PLMN ID information, DNN information, S-NSSAI information, etc.)

[0290] - Local policy / configuration information of the V-PCF

[0291] When multiple UEs managed by one H-PCF (e.g., multiple UEs that have joined the HPLMN including one H-PCF) roam to the VPLMN, the multiple UEs can establish UE policy associations with the V-PCF and the H-PCF. If the service parameters received by the V-PCF are applicable to all the multiple UEs, the V-PCF can provide the service parameters to the H-PCF only once for the multiple UEs. For example, the V-PCF may not need to send the service parameters to the H-PCF as many times as the number of the multiple UEs.

[0292] Step 9. The H-PCF can determine that the data (possibly the service parameters provided by the AF) provided by the V-PCF should be applied to any UE (all UEs) based on one or more of the following information:

[0293] - The target UE of the data (e.g., service parameters) is set to any UE (all UEs)

[0294] - One or more of the information a) to c) described in step 8 above

[0295] If the H-PCF determines that the provided data should be applied to all UEs, the H-PCF can perform the URSP rule determination related operations (the operations described in step 9 of Figure 8) for all UEs (any UE). All UEs (any UE) can be the UEs roaming (registered) in the VPLMN (e.g., the PLMN to which the V-PCF belongs). For example, the H-PCF can perform the URSP rule determination related operations for the UEs it serves that have roamed (registered) in the VPLMN (i.e., the PLMN to which the V-PCF belongs).

[0296] The H-PCF can determine the corresponding URSP rules for multiple UEs based on the same service parameters.

[0297] The H-PCF may send a response message to the V-PCF, including response information indicating that the provided data will be applied to any UE (all UEs).

[0298] If the V-PCF supports the operations described in step 8, it may provide them to the H-PCF when establishing a UE policy association. If the H-PCF supports the operations described in step 9, it may provide them to the V-PCF when establishing a UE policy association. The V-PCF may operate in the form described in step 8 only when the H-PCF notifies its support for the above. Based on the fact that the H-PCF has notified support for the operations described in step 9, the V-PCF may perform the operations described in step 8.

[0299] The H-PCF may send the determined URSP rules to the terminal via the V-PCF.

[0300] The following steps may be applied to the content of Figure 8.

[0301] The following drawings are created to illustrate specific examples of this specification. The names of specific devices depicted in the drawings or the names of specific signals / messages / fields are presented as examples, so the technical features of this specification are not limited to the specific names used in the following drawings.

[0302] Figure 9 The process of the target V-PCF according to the disclosure of this specification is shown.

[0303] 1. The V-PCF may establish a first policy association with the H-PCF (home PCF) for a first UE (user equipment).

[0304] 2. The V-PCF may establish a second policy association with the H-PCF for a second UE.

[0305] 3. The V-PCF may receive service parameters from the V-UDR (visited unified data repository).

[0306] 4. The V-PCF may select a UE policy association from among the first policy association and the second policy association based on the service parameters being applicable to the first UE and the second UE.

[0307] 5. The V-PCF may send a policy message including the service parameters for the first UE and the second UE to the H-PCF via the selected UE policy association.

[0308] The first UE may be a UE different from the second UE.

[0309] The first UE and the second UE may be UEs that have joined the HPLMN (home public land mobile network) to which the H-PCF belongs.

[0310] The first UE and the second UE have roamed to the VPLMN (Visited PLMN) to which the V-PCF belongs.

[0311] The policy message may include information that service parameters are applied to the first UE and the second UE.

[0312] The steps for establishing the first policy association may include:

[0313] Receiving from the H-PCF the capability information that the H-PCF can determine to apply service parameters to the first UE and the second UE.

[0314] The step of sending the policy message may be performed based on the capability information.

[0315] The V-PCF may receive, based on the policy message, a first URSP (UE Routing Selection Policy) rule based on service parameters from the H-PCF.

[0316] The V-PCF may send the first URSP rule to the first UE.

[0317] The V-PCF may receive, based on the policy message, a second URSP rule based on service parameters from the H-PCF.

[0318] The V-PCF may send the second URSP rule to the second UE.

[0319] Figure 10 The process of the target H-PCF disclosed according to this specification is shown.

[0320] 1. The H-PCF may establish a first policy association for the first UE (User Equipment) with the V-PCF (Visited PCF).

[0321] 2. The H-PCF may establish a second policy association for the second UE with the V-PCF.

[0322] 3. The H-PCF may receive from the V-PCF a policy message including service parameters applicable to the first UE and the second UE.

[0323] 4. The H-PCF may determine a first URSP rule for the first UE based on the service parameters.

[0324] 5. The H-PCF may send the first URSP rule to the first UE.

[0325] 6. The H-PCF may determine a second URSP rule for the second UE based on the service parameters.

[0326] 7. The H-PCF may send the second URSP rule to the second UE.

[0327] The first UE can be a UE different from the second UE.

[0328] The first UE and the second UE have roamed to the VPLMN (visited PLMN) to which the V-PCF belongs.

[0329] The first UE and the second UE can be UEs that have joined the HPLMN to which the H-PCF belongs.

[0330] The policy message can include information that service parameters are applied to the first UE and the second UE.

[0331] The steps of establishing the first policy association can include:

[0332] Sending to the V-PCF the capability information that the H-PCF can determine to apply the service parameters to the first UE and the second UE.

[0333] The step of receiving the policy message can be performed based on the capability information.

[0334] Hereinafter, apparatuses for performing communication according to some embodiments of the present specification will be described.

[0335] For example, the target V-SMF can include a processor, a transceiver, and a memory.

[0336] For example, the processor can be configured to be operatively coupled to the memory and the processor.

[0337] The processor can perform: establishing a first policy association for a first UE (user equipment) with an H-PCF (home PCF); establishing a second policy association for the second UE with the H-PCF; receiving service parameters from a V-UDR (visited unified data repository); selecting a UE policy association from among the first policy association and the second policy association based on the service parameters being applicable to the first UE and the second UE; and sending, via the selected UE policy association, a policy message including the service parameters for the first UE and the second UE to the H-PCF, where the first UE is a UE different from the second UE, and where the first UE and the second UE are UEs that have joined the HPLMN (home public land mobile network) to which the H-PCF belongs.

[0338] Hereinafter, processors for providing communication according to some embodiments of the present specification will be described.

[0339] The processor is configured to: establish a first policy association for a first UE (User Equipment) with an H-PCF (Home PCF); establish a second policy association for a second UE with the H-PCF; receive service parameters from a V-UDR (Visited Unified Data Repository); select a UE policy association from among the first policy association and the second policy association based on the service parameters being applicable to the first UE and the second UE; and send a policy message including the service parameters for the first UE and the second UE to the H-PCF via the selected UE policy association, where the first UE is a UE different from the second UE, and where the first UE and the second UE are UEs that have joined an HPLMN (Home Public Land Mobile Network) to which the H-PCF belongs.

[0340] Hereinafter, a non-transitory computer-readable medium storing one or more instructions for providing a multicast service in wireless communication will be described according to some embodiments of the present specification.

[0341] According to some embodiments of the present disclosure, the technical features of the present disclosure can be implemented directly as hardware, software executed by a processor, or a combination of both. For example, in wireless communication, a method performed by a wireless device can be implemented using hardware, software, firmware, or any combination thereof. For example, the software can reside in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or other storage medium.

[0342] Some examples of the storage medium are coupled to the processor such that the processor can read information from the storage medium. Alternatively, the storage medium can be integrated into the processor. The processor and the storage medium can reside in an ASIC. For another example, the processor and the storage medium can reside as separate components.

[0343] The computer-readable medium can include a tangible and non-transitory computer-readable storage medium.

[0344] For example, the non-transitory computer-readable medium can include a random access memory (RAM), such as a synchronous dynamic random access memory (SDRAM), a read-only memory (ROM), or a non-volatile random access memory (NVRAM). A read-only memory (EEPROM), a flash memory, a magnetic or optical data storage medium, or other media that can be used to store instructions or data structures, or a combination of the above can also be included in the non-transitory computer-readable medium.

[0345] In addition, the methods described herein can be implemented at least in part by a computer-readable communication medium that carries or conveys code in the form of instructions or data structures and can be accessed, read, and / or executed by a computer.

[0346] According to some embodiments of the present disclosure, a non-transitory computer-readable medium has one or more instructions stored thereon. The one or more instructions stored can be executed by a processor of a base station.

[0347] The one or more instructions stored cause the processor to: establish a first policy association for a first UE (user equipment) with an H-PCF (home PCF); establish a second policy association for a second UE with the H-PCF; receive service parameters from a V-UDR (visited unified data repository); select a UE policy association among the first policy association and the second policy association based on the service parameters being applicable to the first UE and the second UE; send, via the selected UE policy association, a policy message including the service parameters for the first UE and the second UE to the H-PCF, wherein the first UE is a UE different from the second UE, and wherein the first UE and the second UE are UEs that have joined an HPLMN (home public land mobile network) to which the H-PCF belongs.

[0348] This specification can have various effects.

[0349] For example, service parameters can be efficiently provided from a VPLMN to an HPLMN.

[0350] The effects obtainable through specific examples of this specification are not limited to the effects listed above. For example, there may be various technical effects that those of ordinary skill in the relevant art can understand or derive from this specification. Therefore, the specific effects of this specification are not limited to those explicitly described herein and can include various effects that can be understood or derived from the technical characteristics of this specification.

[0351] The claims described herein can be combined in various ways. For example, the technical features of the method claims of this specification can be combined and implemented as a device, and the technical features of the device claims of this specification can be combined and implemented as a method. In addition, the technical features of the method claims of this specification and the technical features of the device claims of this specification can be combined and implemented as a device, and the technical features of the method claims of this specification and the technical features of the device claims of this specification can be combined and implemented as a method. Other embodiments are within the scope of the appended claims.

Claims

1. A method for performing communication executed by a Visited Policy Control Function (V-PCF), the method comprising the following steps: Establish a first policy association for a first User Equipment (UE) with a Home PCF (H-PCF); Establish a second policy association for a second UE with the H-PCF; Receive service parameters from a Visited Unified Data Repository (V-UDR); Based on the service parameters being applicable to the first UE and the second UE, select one UE policy association among the first policy association and the second policy association; Via the selected one UE policy association, send a policy message to the H-PCF, the policy message including the service parameters for the first UE and the second UE, wherein the first UE is a UE different from the second UE, wherein the first UE and the second UE are UEs that have joined a Home Public Land Mobile Network (HPLMN) to which the H-PCF belongs.

2. The method according to claim 1, Among them, wherein the first UE and the second UE have roamed to a Visited PLMN (VPLMN) to which the V-PCF belongs.

3. The method according to claim 1 or 2, Among them, wherein the policy message includes information that the service parameters are applied to the first UE and the second UE.

4. The method according to any one of claims 1 to 3, Among them, wherein the step of establishing the first policy association includes: Receive, from the H-PCF, capability information that the H-PCF is capable of determining to apply the service parameters to the first UE and the second UE, wherein the step of sending the policy message is performed based on the capability information.

5. The method according to any one of claims 1 to 4, the method further comprising the following steps: Based on the policy message, receive a first User Routing Selection Policy (URSP) rule for the first UE from the H-PCF, based on the service parameters; Send the first URSP rule to the first UE; Based on the policy message, receive a second URSP rule for the second UE from the H-PCF, based on the service parameters; Send the second URSP rule to the second UE.

6. A method for performing communication executed by a Home Policy Control Function (H-PCF), the method comprising the following steps: Establish a first policy association for a first User Equipment (UE) with a Visited PCF (V-PCF); Establish a second policy association for a second UE with the V-PCF; Receive a policy message from the V-PCF, the policy message including service parameters applicable to the first UE and the second UE; Determine a first URSP rule for the first UE based on the service parameters; Send the first URSP rule to the first UE; Determine a second URSP rule for the second UE based on the service parameters; Send the second URSP rule to the second UE, wherein the first UE is a UE different from the second UE.

7. The method according to claim 6, Among them, The first UE and the second UE have roamed to the visited PLMN VPLMN to which the V-PCF belongs. Wherein, the first UE and the second UE are UEs that have joined the HPLMN to which the H-PCF belongs.

8. The method according to claim 6 or 7, Among them, The policy message includes information that the service parameters are applied to the first UE and the second UE.

9. The method according to any one of claims 6 to 8, Among them, The step of establishing the first policy association includes: Sending, to the V-PCF, capability information indicating that the H-PCF is capable of determining to apply the service parameters to the first UE and the second UE, Wherein, the step of receiving the policy message is performed based on the capability information.

10. A visited policy control function V-PCF for performing communication, the V-PCF includes: A transceiver; And A processor, Wherein, the processor performs operations as the method according to any one of claims 1 to 5.

11. A visited policy control function V-PCF for performing communication, the V-PCF includes: A transceiver; And A processor, Wherein, the processor performs operations as the method according to any one of claims 6 to 9.

12. A device in mobile communication, the device includes: At least one processor; And At least one memory, the at least one memory stores instructions and is operatively electrically connected to the at least one processor, Wherein, based on the instructions, the at least one processor operates, and the instructions perform operations as the method according to any one of claims 1 to 5.

13. A non-transitory computer-readable storage medium storing instructions, Among them, The instructions, when executed by one or more processors, cause the one or more processors to perform operations as the method according to any one of claims 1 to 5.

Images