Background data transfer

By integrating cycle-related information into BDT negotiations, the inefficiencies in periodic data transfer are addressed, optimizing resource usage and streamlining operations in background data transfer within the 5G network.

WO2024228529A1PCT designated stage expired Publication Date: 2024-11-07LG ELECTRONICS INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2024/005795
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-03
Filing Date
2024-04-29
Publication Date
2024-11-07

AI Technical Summary

Technical Problem

Background data transfer (BDT) operations in existing systems are inefficient, particularly due to the need for repeated negotiations with the 5G core network for periodic data transfer patterns, which leads to inefficiencies in resource utilization and management.

Method used

Incorporating cycle-related information in BDT negotiation messages between Application Functions (AF) and the 5G Core Network (CN), allowing for optimized radio resource usage based on periodic patterns, such as weekly or daily cycles, to streamline background data transmission and reduce the need for frequent renegotiations.

Benefits of technology

This approach enhances the efficiency of background data transfer by aligning data transmission with optimized resource allocation, improving utilization and reducing operational overhead in managing periodic data transfer scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024005795_07112024_PF_FP_ABST
    Figure KR2024005795_07112024_PF_FP_ABST
Patent Text Reader

Abstract

One disclosure of the present specification provides a method by which a network node associated with an application performs communication. The method comprises the steps of: transmitting a request message related to BDT negotiation to a NEF; and receiving a response message to the request message from the NEF.
Need to check novelty before this filing date? Find Prior Art

Description

Background data transfer

[0001] This specification relates to mobile communications.

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

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

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

[0005] Background data transfer (BDT) operations must be supported in 5G systems. However, conventional technologies have a problem in that BDT operations are not performed efficiently.

[0006] BDT operation can be supported based on period-related information.

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

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

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

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

[0011] Figures 5 and 6 illustrate examples of registration procedures to which the implementation of the present specification applies.

[0012] Figures 7 and 8 illustrate examples of a PDU session establishment procedure to which the implementation of the present specification applies.

[0013] FIG. 9 is an example of a procedure involved in negotiation for a future BDT according to one embodiment of the present specification.

[0014] FIG. 10 is an example of a service specific parameter provisioning procedure according to one embodiment of the disclosure of the present specification.

[0015] FIG. 11A and FIG. 11B illustrate an example of a procedure according to one embodiment of the disclosure of the present specification.

[0016] FIG. 12 illustrates an example of the operation of AF and NEF according to one embodiment of the disclosure of the present specification.

[0017] FIG. 13 illustrates an example of operations according to one embodiment of the disclosure of the present specification.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0076] - AUSF (Authentication Server Function)

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

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

[0079] - USDF (Unstructured Data Storage Function)

[0080] - NEF (Network Exposure Function)

[0081] - I-NEF (Intermediate NEF)

[0082] - NRF (Network Repository Function)

[0083] - NSSF (Network Slice Selection Function)

[0084] - PCF (Policy Control Function)

[0085] - SMF (Session Management Function)

[0086] - UDM (Unified Data Management)

[0087] - UDR (Unified Data Repository)

[0088] - UPF (User Plane Function)

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

[0090] - AF (Application Function)

[0091] - UE (User Equipment)

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

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

[0094] - NWDAF (Network Data Analytics Function)

[0095] - CHF (CHarging Function)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0123] Describes the registration procedure. See section 4.2.2.2 of 3GPP TS 23.502 V16.3.0 (2019-12).

[0124] Figures 5 and 6 illustrate examples of registration procedures to which the implementation of the present specification applies.

[0125] A UE must register with the network to receive services, enable mobility tracking, and enable reachability. The UE initiates the registration process using one of the following registration types:

[0126] - Initial registration for 5GS; or

[0127] - mobility registration update; or

[0128] - Periodic registration update; or

[0129] - Emergency registration

[0130] The general registration procedures of Figures 5 and 6 apply to all registration procedures described above, but periodic registration updates do not need to include all parameters used in other registration procedures.

[0131] The general registration procedures of Figures 5 and 6 can also be used to register a UE for a 3GPP connection when it is already registered for a non-3GPP connection, and vice versa. Registering a UE for a 3GPP connection when it is already registered for a non-3GPP connection scenario may require an AMF change.

[0132] First, the procedure of Fig. 5 is described.

[0133] (1) Step 1: The UE transmits a Registration Request message to the (R)AN. The Registration Request message corresponds to an AN message.

[0134] The registration request message may include AN parameters. For NG-RAN, the AN parameters include, for example, the 5G SAE temporary mobile subscriber identity (5G-S-TMSI) or the 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 an establishment cause. The establishment cause provides the reason for requesting 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 inclusion mode parameter.

[0135] A 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 RM-DEREGISTERED state), or a mobility registration update (i.e., the UE is in RM-REGISTERED state and the registration procedure is initiated because the UE moves, or the UE wants to update its capabilities or protocol parameters, or because the UE requests a change in the set of network slices it is allowed to use), or a periodic registration update (i.e., the UE is in RM-REGISTERED state and the registration procedure is initiated because the periodic registration update timer has expired), or an emergency registration (i.e., the UE is in restricted service state).

[0136] When a UE performs initial registration, the UE indicates its UE ID in the registration request message, listed in decreasing priority order.

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

[0138] ii) Native 5G-GUTI (if available) allocated by the PLMN in which the UE is attempting to register;

[0139] iii) Native 5G-GUTI allocated by a PLMN equivalent to the PLMN in which the UE is attempting to register;

[0140] iv) Native 5G-GUTI allocated by another PLMN (if available);

[0141] v) Otherwise, the UE includes a subscriber concealed identifier (SUCI) in the registration request message.

[0142] If a UE performing initial registration has both a valid EPS GUTI and a native 5G-GUTI, the UE also indicates the native 5G-GUTI as an additional GUTI. If more than one native 5G-GUTI is available, the UE selects a 5G-GUTI from items (ii)-(iv) in decreasing priority order in the list above.

[0143] When the UE performs initial registration with native 5G-GUTI, the UE indicates the relevant GUAMI information in the AN parameters. When the UE performs initial registration with SUCI, the UE does not indicate the GUAMI information in the AN parameters.

[0144] For emergency registration, if the UE does not have a valid 5G-GUTI, the SUCI is included. If the UE does not have a subscriber permanent identifier (SUPI) and does not have a valid 5G-GUTI, the PEI (Permanent Equipment Identifier) ​​is included. Otherwise, the 5G-GUTI is included, indicating the last serving AMF.

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

[0146] (2) Step 2: (R)AN selects AMF.

[0147] If 5G-S-TMSI or GUAMI is not included, or if 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.

[0148] When the UE is in CM-CONNECTED state, (R)AN can forward a registration request message to AMF based on the N2 connection of the UE.

[0149] If the (R)AN cannot select an appropriate AMF, the (R)AN performs AMF selection by forwarding a registration request message to the AMF configured in the (R)AN.

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

[0151] The registration request message may contain all of the information and / or part of the information contained in the registration request message received from the UE described in step 1.

[0152] The registration request message may include an N2 parameter. When NG-RAN is used, the N2 parameter includes the selected PLMN ID (or PLMN ID and NID), location information and cell ID related to the cell where the UE is camping, and a UE context request indicating that a UE context including security information should be established in the NG-RAN. When NG-RAN is used, the N2 parameter also includes an establishment cause.

[0153] If the registration type indicated by the UE is periodic registration update, steps 4-19 described below may be omitted.

[0154] (4) Step 4: If the UE's 5G-GUTI 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 to the previous AMF, including the full registration request non-access stratum (NAS) message to request the UE's SUPI and UE context.

[0155] (5) Step 5: The old AMF can respond to the new AMF for the Namf_Communication_UEContextTransfer call including the UE's SUPI and UE context.

[0156] (6) Step 6: If SUCI is not provided by the UE or not retrieved from the previous AMF, the new AMF may initiate an ID request procedure by sending an Identity Request message to request SUCI from the UE.

[0157] (7) Step 7: The UE may respond with an Identity Response message including the SUCI. The UE derives the SUCI using the provided public key of the home PLMN (HPLMN).

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

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

[0160] (10) Step 10: If the AMF has changed, the new AMF may call the Namf_Communication_RegistrationCompleteNotify service operation to notify the old AMF that the UE registration with the new AMF is complete. If the authentication / security procedure fails, the registration is rejected and the new AMF may call the Namf_Communication_RegistrationCompleteNotify service operation with a reject indication reason code to the old AMF. The old AMF may continue as if the UE context transfer service operation was not received.

[0161] (11) Step 11: If the PEI was not provided by the UE or was not retrieved from the previous AMF, the new AMF may initiate the ID request procedure by sending an Identity Request message to the UE to retrieve the PEI. The PEI is transmitted encrypted, except when the UE performs emergency registration and cannot be authenticated.

[0162] (12) Step 12: Optionally, the new AMF can initiate ME ID checking by calling the N5g-eir_EquipmentIdentityCheck_Get service operation.

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

[0164] (13) Step 13: When step 14 below is performed, the new AMF can select a UDM based on SUPI, and the UDM can select a UDR instance.

[0165] (14) Step 14: New AMFs can be registered with UDM.

[0166] (15) Step 15: New AMF can select PCF.

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

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

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

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

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

[0172] (21) Step 21: The new AMF sends a Registration Accept message to the UE.

[0173] The new AMF sends the UE a Registration Accept message indicating that the registration request has been accepted. If the new AMF allocates a new 5G-GUTI, it includes the 5G-GUTI. If the UE is already in the RM-REGISTERED state through another connection to the same PLMN, the UE uses the 5G-GUTI received in the Registration Accept message for both registrations. If the Registration Accept message does not include a 5G-GUTI, the UE uses the 5G-GUTI assigned to the existing registration for the new registration. If the new AMF allocates a new registration area, it sends the registration area to the UE in the Registration Accept message. If the Registration Accept message does not include a registration area, the UE considers the previous registration area to be valid. Mobility Restrictions are included if mobility restrictions apply to the UE and the registration type is not emergency registration. The new AMF indicates the PDU sessions established for the UE in the PDU Session State. The UE locally removes internal resources associated with PDU sessions that are not marked as established in the received PDU Session State. When a UE is connected to two AMFs belonging to different PLMNs via a 3GPP connection and a non-3GPP connection, the UE locally removes internal resources associated with PDU sessions in the current PLMN that are not marked as established in the received PDU session status. If PDU session status information is present in the Registration Accept message, the new AMF indicates the PDU session status to the UE.

[0174] The Allowed NSSAI provided in the Registration Accept message is valid for the registration area and applies to all PLMNs that have a tracking area included in the registration area. The Mapping of Allowed NSSAIs maps HPLMN S-NSSAIs to each S-NSSAI of the Allowed NSSAIs. The Mapping of Configured NSSAIs maps HPLMN S-NSSAIs to each S-NSSAI of the Configured NSSAI for the serving PLMN.

[0175] Additionally, optionally, the new AMF performs UE policy association establishment.

[0176] (22) Step 22: If the UE successfully updates itself, it can send a Registration Complete message to the new AMF.

[0177] The UE may send a registration complete message to the new AMF to confirm that a new 5G-GUTI has been allocated.

[0178] (23) Step 23: In case of registration via 3GPP connection, if the new AMF does not release the signaling connection, the new AMF may send RRC Inactive Assistance information to the NG-RAN. In case of registration via non-3GPP connection, if the UE is in CM-CONTENED state on the 3GPP connection, the new AMF may send RRC Inactive Assistance information to the NG-RAN.

[0179] (24) Step 24: AMF can perform information updates on UDM.

[0180] (25) Step 25: The UE may execute a network slice-specific authentication and authorization (NSSAA) procedure.

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

[0182] Figures 7 and 8 illustrate examples of a PDU session establishment procedure to which the implementation of the present specification applies.

[0183] Establishing a PDU session may involve:

[0184] - UE-initiated PDU session establishment procedure

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

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

[0187] - Network-triggered PDU session establishment procedure

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

[0189] Figures 7 and 8 specify a procedure for establishing a PDU session associated with a single connection type at a given time.

[0190] In the procedures shown in FIGS. 7 and 8, it is assumed that the UE is already registered with the AMF, so unless the UE is emergency registered, the AMF has already retrieved the user subscription data from the UDM.

[0191] First, the procedure of Fig. 7 is explained.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0228] - RSN (redundancy sequence number) parameter

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

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

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

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

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

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

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

[0236] Now, the procedure of Fig. 8 following the procedure of Fig. 7 is described.

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

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

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

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

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

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

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

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

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

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

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

[0248] (21) Step 21: If the PDU session establishment fails after step 4, the SMF may unsubscribe from modifications to the session management subscription data if the SMF no longer processes the UE's PDU session.

[0249] Background data transfer (BDT) may be supported in 5G systems.

[0250] The following is a description of 5GS Transfer of Policies for Background Data Transfer (BDT).

[0251] 5G will offer significantly greater available RAN capacity than 4G. UEs can upload large amounts of data via 5G systems. For example, connected cars can upload in-vehicle sensor data for diagnostics and photo / LIDAR data for dynamic map generation to servers in third-party data centers. BDT can be used to efficiently utilize radio and core network resources.

[0252] If the policy is transmitted from a server outside the core network or the 3GPP system, the UE may assist the 3GPP system to optimize radio resource usage based on the policy for background data transmission (e.g., time window, network area information, etc.).

[0253] "BDT" is captured in TS 22.101 under the keyword "background data transfer" and in TS 22.368 under the title "Time control".

[0254] Conventional BDT-related technologies have primarily focused on background data transmission policy negotiation between the 5G core network and third-party application functions (3rd-party application functions), but have not considered the UE. If BDT policies (e.g., time windows, network area information, etc.) are transmitted from a server outside the core network or 3GPP system, the UE can support the 3GPP system based on these BDT policies to optimize radio resource utilization.

[0255] The following example shows the BDT description from TS 23.503v18.1.0.

[0256] Describes negotiations for future (or future) BDT.

[0257] An AF can communicate with a PCF via the NEF (and the Npcf_BDTPolicyControl_Create service operation) to request a time window and associated conditions for a future BDT. An NEF can communicate with any PCF within the operator's network.

[0258] The AF can send a request message to the PCF. The request message from the AF can include an ASP identifier, the amount of data to be transmitted per UE, the expected number of UEs, the desired time window, an external group identifier, and optionally network area information, a MAC address or an IP 3-tuple for identifying application servers, and a notification request. The AF can provide network area information, such as a geographic area (e.g., civic address or shapes) or an area of ​​interest, which includes a list of TAs or a list of NG-RAN nodes and / or a list of cell identifiers. If the AF provides a geographic area, the NEF, based on its local configuration, maps the geographic area to the list of TAs and / or the list of NG-RAN nodes and / or the list of cell identifiers provided to the PCF. The NEF, based on its local configuration, can map the ASP identifier to the DNN and S-NSSAI additionally provided to the PCF. The MAC address or IP 3-tuple identifying the application server can be provided by the AF or configured locally by the PCF. Additionally, the MAC address or IP 3-tuple is used to generate URSP rules for the application as well as PCC rules for application traffic. A notification request is an indication that the ASP accepts the BDT policy and may renegotiate it using the BDT alert notification procedure.

[0259] The PCF can first retrieve all existing BDT policies stored for all ASPs from the UDR. The PCF can retrieve the "Network Performance" analysis from the NWDAF. Then, the PCF can determine one or more BDT policies based on the information provided by the AF, the "Network Performance" analysis if available, and other available information (e.g., network policies and existing BDT policies). If the NEF does not provide the PCF with the DNN and S-NSSAI, the PCF can map the ASP identifier to the target DNN and S-NSSAI.

[0260] A BDT policy may include a recommended time window for background data transmission, a reference charging rate for this time window, and optionally a maximum aggregated bitrate (indicating that charging according to the referenced charging rate is applied only to the aggregated traffic of all involved UEs that remains below this value). Finally, the PCF may provide the AF with a list of candidate BDT policies via the NEF along with the background data transmission reference ID. If the AF receives more than one BDT policy, the AF selects one of them and informs the PCF about the selected BDT policy.

[0261] The selected BDT policy is stored in the UDR by the PCF as a data set "Policy Data" and a data subset "Background Data Transfer data", together with the Background Data Transfer reference ID, network area information, the amount of data to be transferred per UE, the expected number of UEs, the ASP identifier, the MAC address or IP 3-tuple identifying the application server, one or more path selection components (DNN, S-NSSAI), the desired time window, and whether the AF accepts BDT policy renegotiation. The same or another PCF can retrieve this BDT policy and its related information from the UDR and consider it in future decisions regarding BDT policies associated with the same or another ASP.

[0262] When AF wishes to apply a background data transfer policy to an existing session, AF provides PCF (via the N5 interface) with a background data transfer reference ID for each UE along with AF session information when BDT is initiated. PCF retrieves the corresponding BDT policy from the policy data set of the UDR and derives PCC rules for BDT based on this transfer policy.

[0263] When the AF wants to apply a background data transfer policy to a future session, the AF provides the NEF with a background data transfer reference ID together with an external identifier (e.g., GPSI) or an external group identifier of the UE to which the policy applies. The NEF converts the external group identifier to an internal group identifier or converts the external identifier to a SUPI. The NEF stores the background data transfer reference ID in the UDR along with the application data set and the background data transfer data subset for the internal group identifier or SUPI and the ASP identifier to request to apply the background data transfer policy to future sessions for the UE(s). The PCF serving the UE(s) (i.e., the PCF serving the UE for the UE policy) can retrieve the background data transfer reference ID by retrieving the application data of the UE from the UDR or by subscribing to notifications about changes in the application data of the UE from the UDR. Additionally, PCF identifies application servers based on the received background data transfer reference ID stored in the policy data set from the UDR by retrieving the specific background data transfer policy and the corresponding network zone information and MAC address or IP 3-tuple.

[0264] When the PCF decides to send a URSP rule related to the background data transfer policy to the UE, the PCF creates a URSP rule using the MAC address or IP 3-tuple (application server identification) as the traffic descriptor. The RSD part of the URSP rule is populated with the S-NSSAI and DNN associated with the ASP identifier. The path selection validation criterion of the URSP rule is populated with the time window set as the recommended time window of the BDT policy, and if the BDT policy does not apply to the entire network, the location criterion is set to the network area information of the BDT policy. The PCF stores the URSP rule in the UDR as part of the policy set entry of the UE. The PCF stores the background data transfer reference ID in the PDU session policy control subscription information of the UE using the S-NSSAI and DNN associated with the ASP identifier stored in the application data.

[0265] PCF uses local policy to determine when URSP rules related to background data transfer policy are transmitted to the UE. Depending on operator configuration, PCF may trigger a UE configuration update procedure when an AF request is received to apply BDT policy to future sessions, or wait until it receives notification from AMF that the UE has entered a tracking or presence area where BDT policy applies, or wait until the time window where BDT policy applies approaches.

[0266] The UE uses the Route Selection Validation Criteria to determine whether to establish a PDU session. The time window and location criteria do not need to be revalidated during the lifetime of the PDU session. Support for the UE's validation criteria is optional in the URSP rules.

[0267] When a PDU session is established, the PCF serving the PDU session retrieves the corresponding BDT policy and related information from the UDR using the background data transfer reference ID in the UE's PDU session policy control subscription information, and derives the PCC rules for BDT based on this information.

[0268] If the S-NSSAI and DNN corresponding to the BDT policy and validation criteria are not met, the PCF may reject the establishment of the SM policy association. Based on this feedback, the SMF rejects the establishment of the PDU session.

[0269] After a PDU session is successfully established, the PCF may trigger a PDU session teardown if the validation criteria are no longer met.

[0270] PCF can subscribe to NWDAF's "Network Performance" analysis for the area and time period of interest of BDT policies, based on procedures and services that display reporting thresholds in Analytics Reporting information. The reporting threshold value is set by the PCF according to operator configuration. If network performance is determined to fall below the threshold, NWDAF notifies the PCF of the results of the network performance analysis for the area and time period of interest. Upon receiving the notification from NWDAF, the PCF can attempt to renegotiate the affected BDT policies with the AFs that have accepted BDT policy renegotiation. To do this, the PCF retrieves all BDT policies from the UDR along with stored AF-provided information (e.g., the desired time period), identifies BDT policies that are no longer desirable due to network performance degradation, and attempts to compute a new candidate BDT policy for the ASP to select. If the PCF does not find a new candidate BDT policy or the relevant AF does not accept BDT policy renegotiation, the previously negotiated BDT policy remains in effect, and no interaction with the ASP occurs. When PCF discovers one or more new candidate BDT policies, PCF notifies the relevant ASP via NEF of both the obsolete BDT policy and the candidate BDT policy.

[0271] PCF invalidates the BDT policy stored in the UDR for the given BDT reference ID while BDT policy renegotiation is in progress. PCF rejects PDU session requests corresponding to invalid BDT policies.

[0272] Upon receiving a notification, the AF can select one of the BDT policies included in the candidate list and then notify the PCF about the selected BDT policy. The PCF stores the newly selected BDT policy in the UDR for the corresponding Background Data Transfer Reference ID and removes any BDT policies that are no longer valid. Furthermore, the PCF updates the URSP rules corresponding to the BDT policy using the new validation criteria in the policy set entries of all UEs. As a result, the PCF identifies UEs that have already been provided with a BDT policy and uses the procedure to update the URSP rules corresponding to the BDT policy.

[0273] If the AF does not select one of the BDT policies included in the candidate list, the PCF removes the BDT policy stored in the UDR along with the corresponding Background Data Transfer Reference ID and all related information, and the URSP rule corresponding to the BDT policy in the policy set entries of all UEs. As a result, the PCF identifies UEs that are already provisioned with a URSP rule corresponding to the BDT policy and removes the URSP rule corresponding to the BDT policy using the procedure.

[0274] Below are examples of BDT-related procedures and service operations used between AF and 5G CN as defined in TS 23.502v18.1.1.

[0275] Describes an example of negotiations for future background data transfer.

[0276] The future background data transfer procedure specified in section 4.16.7.2 of TS 23.502v18.1.1 enables negotiation between the NEF and the H-PCF regarding the transfer policy for future background data transfers (as described in section 6.1.2.4 of TS 23.503 V18.0.0). The transfer policy consists of a desired time window for background data transfers, a reference to the charging rate for the time window, network area information, and optionally a maximum aggregate bit rate, as described in section 6.1.2.4 of TS 23.503 V18.0.0.

[0277] This negotiation is performed preliminarily before the UE's PDU session is established (when the AF initiates the procedure to the NEF). If the AF wants to apply a background data transfer policy to an existing PDU session, the AF calls the Npcf_PolicyAuthorization_Create service directly to the PCF or through the NEF to apply the background data transfer policy to the individual UE when the background data transfer is about to start. If the AF wants to apply the background data transfer policy to a future PDU session, the AF calls the Nnef_ApplyPolicy_Create service to provide the NEF with the background data transfer reference ID together with the external identifier or external group identifier of the UE to which the policy applies.

[0278] In accordance with the BDT alert notification procedure specified in section 4.16.7.3 of TS 23.502v18.1.1, the PCF may notify the AF that network performance in an area of ​​interest has fallen below the operator-defined threshold as described in section 6.1.2.4 of TS 23.503 V18.0.0.

[0279] With reference to the example of Fig. 9, the procedure related to future data transmission will be described.

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

[0281] FIG. 9 is an example of a procedure involved in negotiation for a future BDT according to one embodiment of the present specification.

[0282] According to Figure 9, the procedure involved in negotiation for future background data transmission is described.

[0283] 1. The AF can send a request message to the NEF. The AF can call the Nnef_BDTPNegotiation_Create service operation related to BDT negotiation. The AF can send a request message related to BDT negotiation creation to the NEF. For example, the AF can send the Nnef_BDTPNegotiation_Create message. The Nnef_BDTPNegotiation_Create message can contain the ASP identifier, the number of UEs, the volume per UE, the desired time window, and optionally the external group identifier, network area information, a notification request, and the MAC address or IP 3-tuple of the application server. The notification request indicates that a BDT alert notification should be sent to the AF.

[0284] Step 2 may include Step 2a and / or Step 2b as follows:

[0285] 2a. Based on the AF request, NEF can request UDM to translate the external group identifier into an internal group identifier using Nudm_SDM_Get(Translate group identifier, including external group identifier).

[0286] 2b. The NEF may send a BDT policy control creation request message to the PCF. For example, to authorize the creation of a policy regarding background data transfer, the NEF calls the Npcf_BDTPolicyControl_Create (with ASP identifier, number of UEs, volume per UE, desired time window, and optionally an internal group identifier, network area information, notification request, and the MAC address or IP 3-tuple of the application server) to the H-PCF. If the notification request is provided to the PCF, the PCF may send a BDT alert notification to the AF as described in clause 4.16.7.3 of TS 23.502v18.1.1.

[0287] 3. H-PCF can send a request message to UDR. For example, H-PCF can use the Nudr_DM_Query (includes policy data, background data transfer) service operation to request UDR the background data transfer policy stored for all ASPs.

[0288] 4. The UDR can send a response message to the H-PCF. For example, the UDR can provide the H-PCF with all stored background data transmission policies and related information (e.g., the amount of data to be transmitted per UE, the expected number of UEs).

[0289] 5. H-PCF can perform policy decisions. For example, based on information provided by AF and other available information, H-PCF can determine one or more background data transmission policies. PCF can interact with NWDAF to request network performance analysis information and network area information for a desired period of time.

[0290] 6. H-PCF can send a BDT policy creation response message to NEF. For example, H-PCF sends an acknowledgment message to NEF containing the allowed background data transfer policy and background data transfer reference ID.

[0291] 7. The NEF can send a BDT negotiation creation response message to the AF. For example, to provide the AF with one or more background data transfer policies and a background data transfer reference ID, the NEF sends the Nnef_BDTPNegotiation_Create response to the AF. The AF stores the background data transfer reference ID for future interactions with the PCF. If the NEF receives only one background data transfer policy from the PCF, steps 8 to 11 are not performed, and step 12 is performed. Otherwise, step 8 is performed.

[0292] 8. AF can send a BDT negotiation update request message to NEF. For example, AF calls the Nnef_BDTPNegotiation_Update service to provide NEF with the background data transfer reference ID and the selected background data transfer policy.

[0293] 9. NEF can send a BDT policy control update request message to H-PCF. To provide H-PCF with the selected background data transfer policy and the associated background data transfer reference ID, NEF calls the Npcf_BDTPolicyControl_Update service.

[0294] 10. H-PCF can send a BDT policy control update response message to NEF. For example, H-PCF sends an acknowledgement message to NEF.

[0295] 11. NEF sends an acknowledgment message to AF.

[0296] 12. The H-PCF can send an update request message to the UDR. For example, the H-PCF can call Nudr_DM_Update (containing BDT reference ID, Policy Data, Background Data Transfer) with a new background data transfer policy, related information (e.g., the amount of data to be transferred per UE, the expected number of UEs), and optionally the MAC address or IP 3-tuple of the application server. Accordingly, the H-PCF stores the background data transfer reference ID in the UDR along with the related information received from the AF.

[0297] Step 12 is not performed if PCF decides to store the background data transfer policy locally.

[0298] 13. UDR sends a response to H-PCF as an acknowledgment of this.

[0299] Below, we will describe various examples of BDT policy control services.

[0300] The BDT policy control service can be, for example, the Npcf_BDTPolicyControl service.

[0301] The Npcf_BDTPolicyControl service provides background data transfer policies, which can include the following features:

[0302] - Ability to get background data transfer policy based on AF's request via NEF; and

[0303] - Ability to update background data transmission based on selections provided by AF.

[0304] Below, various examples of the Npcf_BDTPolicyControl service are described.

[0305] Describes the BDT policy control creation service operation. For example, the BDT policy control creation service operation can be the Npcf_BDTPolicyControl_Create service operation. The Npcf_BDTPolicyControl_Create service operation can be described as follows.

[0306] Service Action Name: Npcf_BDTPolicyControl_Create

[0307] Description: This service creates background data transfer policies.

[0308] Inputs, Required: ASP identifier, volume per UE, number of UEs, desired time window.

[0309] Inputs, Optional: S-NSSAI, DNN, Internal Group Identifier, Network Zone Information, Request for Notification, MAC address or IP 3-tuple of the application server.

[0310] Outputs, Required: One or more background data transfer policies, background data transfer reference IDs.

[0311] Outputs, Optional: None.

[0312] Describes the BDT policy control update service operation. For example, the BDT policy control update service operation may be the Npcf_BDTPolicyControl_Update service operation. The Npcf_BDTPolicyControl_Update service operation can be described as follows.

[0313] Service Action Name: Npcf_BDTPolicyControl_Update

[0314] Description: This service updates the background data transfer policy to PCF.

[0315] Input, required: ASP identifier, background data transfer policy, background data transfer reference ID.

[0316] Input, optional: Stop notifications.

[0317] Output, required: None.

[0318] Output, optional: None.

[0319] Describes the operation of the BDT policy control notification service. For example, the BDT policy control notification service operation may be the Npcf_BDTPolicyControl_Notify service operation. The Npcf_BDTPolicyControl_Notify service operation can be described as follows.

[0320] Service Action Name: Npcf_BDTPolicyControl_Notify

[0321] Description: This service operation sends a BDT alert notification to the NF consumer.

[0322] Input, required: Background data transfer reference ID.

[0323] Input, optional: network zone information, time window, list of background data transfer policy candidates.

[0324] Output, required: None.

[0325] Output, optional: None.

[0326] Describes the BDT policy service operation. For example, the BDT policy control notification service operation may be the Npcf_BDTPolicyControl_Notify service operation. The Npcf_BDTPolicyControl_Notify service operation can be described as follows.

[0327] Describes services related to BDT negotiation. For example, the services described below may be related to BDT policy negotiation. For example, the Nnef_BDTPNegotiation service is described.

[0328] For the Nnef_BDTPNegotiation service, reference may be made to the example described above in Fig. 9.

[0329] For example, the BDT policy negotiation creation service operation is described. For example, the BDT policy negotiation creation service operation can be the Nnef_BDTPNegotiation_Create service operation. The Nnef_BDTPNegotiation_Create service operation can be described as follows.

[0330] Service action name: Nnef_BDTPNegotiation_Create.

[0331] Description: A consumer requests a background data transfer policy.

[0332] Input, Required: Input, Required: ASP identifier, Volume per UE, Number of UEs, Desired time window.

[0333] Input, optional: external group identifier, network zone information, notification request, MAC address of the application server, or IP 3-tuple.

[0334] Output, required: Background data transfer reference ID, one or more background data transfer policies.

[0335] Output, optional: None.

[0336] For example, the BDT policy negotiation update service operation is described. For example, the BDT policy negotiation update service operation may be the Nnef_BDTPNegotiation_Update service operation. The Nnef_BDTPNegotiation_Update service operation can be described as follows.

[0337] Service action name: Nnef_BDTPNegotiation Update.

[0338] Description: Requests that the consumer set a background data transfer policy of their choice.

[0339] Input, required: Background Data Transfer Reference ID, Background Data Transfer Policy.

[0340] Input, optional: Stop notifications.

[0341] Output, required: None.

[0342] Output, optional: None.

[0343] For example, the BDT policy negotiation notification service operation is described. For example, the BDT policy negotiation notification service operation may be the Nnef_BDTPNegotiation_Notify service operation. The Nnef_BDTPNegotiation_Notify service operation can be described as follows.

[0344] Service Action Name: Nnef_BDTPNegotiation_Notify

[0345] Description: NEF sends a BDT warning notification to NF consumers.

[0346] Input, required: Background data transfer reference ID.

[0347] Input, optional: network zone information, time window, list of candidate background data transfer policies.

[0348] Output, required: None.

[0349] Output, optional: None.

[0350] According to the data types defined below, the time-related information included in the BDT negotiation process between AF and NEF may be in the form of a time window. For example, the time window includes a start time and a stop time.

[0351] For example, time windows can be included in various services and / or messages as follows: The Nnef_BDTPNegotiation_Create Request can include a desired time window. The Nnef_BDTPNegotiation_Create Response can include a time window that configures a background data transfer policy. The Nnef_BDTPNegotiation_Notify can include a time window. And the Nnef_BDTPNegotiation_Notify can include time window information that configures a background data transfer policy.

[0352] The ResourceManagementOfBdt API is described. TS 29.122v18.1.0, Section 5.4 can be referenced.

[0353] The ResourceManagementOfBdt API is a RESTful API that allows a Services Capability Server (SCS) / Application Server (AS) to request background data transmission-related conditions for a set of UEs. An AF can perform the same operations as the SCS / AS. The ResourceManagementOfBdt API defines a data model, a set of resources, and related procedures for creating and managing background data transmission requests. The corresponding JSON schema for representing the resources and operations defined by the ResourceManagementOfBdt API can be provided in its complete form in Appendix A.4 of TS 29.122v18.1.0.

[0354] Describes the data model.

[0355] Describes resource data types.

[0356] Resource data types define the data structures to be used for resource representations.

[0357] Table 3 specifies the data types reused by the ResourceManagementOfBdt API, including references to their specifications and, where necessary, brief descriptions of how they are used within the ResourceManagementOfBdt API.

[0358] Data TypeReference CommentGeographicArea3GPP TS 29.572 V18.0.0Identifies the user's geographical information.CivicAddress3GPP TS 29.572 V18.0.0Identifies the user's civic address information.NetworkAreaInfo3GPP TS 29.554 V18.0.0Identifies the network area information.SupportedFeatures3GPP TS 29.571 V18.0.0Used to negotiate the applicability of optional features defined in Table 5.4.4-1 of TS 29.122v18.1.0.

[0359] The examples in Table 3 illustrate the ResourceManagementOfBdt API re-used Data Types.

[0360] Table 4 below describes the data types defined for the ResourceManagementOfBdt API.

[0361] Data TypeDefined SectionDescriptionApplicabilityBdt5.4.2.1.2 of TS 29.122v18.1.0Indicates a background data transfer subscription.BdtPatch5.4.2.1.3 of TS 29.122v18.1.0Indicates a background data transfer subscription modification request.ExNotification5.4.2.1.4 of TS 29.122v18.1.0Indicates a background data transfer notification.TrafficDescriptor5.4.2.3.2 of TS 29.122v18.1.0Identifies a traffic descriptor as defined in Section 5.2.2 of GPP TS 24.526 V18.0.0.TransferPolicy5.4.2.2.2 of TS 29.122v18.1.0Identifies an offered transfer policy sent from an SCEF to an SCS / AS or from an SCS / AS. Indicates the selected transfer policy transmitted to SCEF.

[0362] Table 4 shows examples of ResourceManagementOfBdt API specific data types.

[0363] Below, Type: Bdt is described. This type represents a BDT subscription. The same structure is used for subscription requests and subscription responses.

[0364] Attribute Name Data Type Cardinality Description Applicability (NOTE 1) selfLink 0..1 Links to the "Individual BDT Subscription" resource. This parameter is provided in the HTTP response from the SCEF. supportedFeatures SupportedFeatures 0..1 Used to negotiate optional features supported by the API, as described in Section 5.2.7 of TS 29.122 v18.1.0. This property MUST be provided in the POST request and the response of a successful resource creation. volumePerUEUsageThreshold1 Identifies the expected data volume to transfer per UE. numberOfUEsInteger1 Identifies the number of UEs. desiredTimeWindowTimeWindow1 Identifies the time interval. locationAreaLocationArea0..1 Identifies the area for which the SCS / AS requests the number of UEs. BdtlocationArea5GLocationArea5G0..1 Identifies the area for which the AF requests the number of UEs. LocBdt_5GreferenceIdBdtReferenceId0..1 Identifies the selected background data transfer policy. transferPoliciesarray(TransferPolicy)0..N Identifies the provided transfer policy. selectedPolicyinteger0..1 Identifier of the selected background data transfer policy. It must not exist in the initial message exchange and may be provided by the NF service consumer in subsequent message exchanges. externalGroupIdExternalGroupId0..1 Identifies the user group. (NOTE 2) Group_IdnotificationDestinationLink0..1 Contains the URI for receiving BDT notifications from the NEF. BdtNotification_5GwarnNotifEnabledboolean0..1 Indicates whether BDT warning notifications are enabled.When set to True, BDT alert notifications are enabled, and when set to False or Absent, BDT alert notifications are disabled. BdtNotification_5GtrafficDesTrafficDescriptor0..1 Contains the traffic descriptor for background data. (Note 2) NOTE 1: Attributes marked as capabilities defined in clause 5.4.4 of TS 29.122v18.1.0 apply as described in clause 5.2.7 of TS 29.122v18.1.0. If a capability is not marked, the associated attribute applies to all capabilities. NOTE 2: This attribute is only applicable to NEF.

[0365] Table 5 shows an example of the definition of type Bdt.

[0366] Type: Describes a BdtPatch. This type represents a BDT request for a service provided by the SCS / AS to the SCEF via the T8 interface. This structure is used in PATCH requests.

[0367] Attribute Name Data Type Cardinality Description Applicability (NOTE) selectedPolicy integer 1 Identity of the selected Background Data Transfer policy.warnNotifEnabledboolean0..1 Indicates whether BDT warning notifications are enabled. - true: BDT warning notifications are enabled; - false: BDT warning notifications are disabled. BdtNotification_5GnotificationDestinationLink0..1 Contains the URI for receiving BDT notifications from the NEF. enNBNOTE: Attributes marked with a capability defined in section 5.4.4 of TS 29.122v18.1.0 apply as described in section 5.2.7 of TS 29.122v18.1.0. If a capability is not marked, the associated attribute applies to all capabilities.

[0368] Table 6 shows an example of the definition of type BdtPatch.

[0369] Type: Describes ExNotification. This type represents a BDT notification provided by NEF to AF. This structure is used in POST requests.

[0370] Attribute NameData TypeCardinalityDescriptionApplicability (NOTE)bdtRefIdBdtReferenceId1 This IE indicates the transfer policy for the background data transfer to which the notification applies.locationArea5GLocationArea5G0..1 This IE indicates the network area where network performance falls below an operator-configured baseline.timeWindowTimeWindow0..1 This IE indicates the time window during which network performance falls below an operator-configured baseline.candPoliciesarray(TransferPolicy)0..N This IE indicates the list of candidate transfer policies from which the AF can select a new transfer policy due to network performance degradation.NOTE: Attributes marked with a capability defined in Section 5.4.4 of TS 29.122v18.1.0 apply as described in Section 5.2.7 of TS 29.122v18.1.0. If a capability is not marked, the relevant attribute applies to all capabilities.

[0371] Table 7 shows an example of the definition of type ExNotification.

[0372] Describes referenced structured data types. This defines the structured data types referenced in previously defined data structures.

[0373] Type: Describes TransferPolicy. This data type represents the transfer policy provided when transferring from SCEF to SCS / AS, or the selected transfer policy when transferring from SCS / AS to SCEF.

[0374] Attribute NameData TypeCardinalityDescriptionApplicability (NOTE)bdtPolicyIdinteger1Identifier of the transmission policymaxUplinkBandwidthBandwidth0..1Indicates the maximum aggregate bitrate of the uplink authorized by the PCRFmaxDownlinkBandwidthBandwidth0..1Indicates the maximum aggregate bitrate of the downlink authorized by the PCRFratingGroupInteger1Indicates the rating group for a time windowtimeWindowTimeWindow1Indicates the recommended time window of the transmission policyNOTE: Attributes marked with a capability defined in clause 5.4.4 apply as described in clause 5.2.7 of TS 29.122v18.1.0. If a capability is not marked, the relevant attribute applies to all capabilities.

[0375] Regarding the Nnef_BDTPNegotiation_Create Request described above, the desired time window information provided by the AF can be used when URSP rules related to BDT are configured. For example, when a URSP rule provided to the UE is configured in relation to BDT, the desired time window information can be reflected as Time Window information in the Route Selection Validation Criteria. The Time Window information can be expressed as Start Time and Stop Time.

[0376] Below, an example of UE Route Selection Policy (URSP) information is described. For reference, URSP defined in TS 23.503v18.1.0 S6.6.2 may be referenced.

[0377] Describes the structure of a URSP. A URSP may contain a priority list of URSP rules.

[0378] Information Name Description Category PCF permitted to modify information in URSP Scope Route Selection Descriptor Precedence Determines the order in which Route Selection Descriptors are applied. Mandatory (NOTE 1) Yes UE context Route selection components This section defines the route selection components. Mandatory (NOTE 2) SSC Mode Selection A single value for the SSC mode. (NOTE 5) Optional Yes UE context Network Slice Selection A single value or a list of values ​​for the S-NSSAI. Optional (NOTE 3) Yes UE context DNN Selection A single value or a list of values ​​for the DNN. Optional Yes UE context PDU Session Type Selection A single value for the PDU session type. Conditional (NOTE 8) Yes UE context Non-Seamless Offload indication Indicates whether the traffic of the matching application will be offloaded to non-3GPP access outside the PDU session. Optional (NOTE 4) Yes UE context ProSe Layer-3 UE-to-Network Relay Offload indication Indicates whether the traffic of the matching application is to be transmitted via a ProSe Layer-3 UE-to-network relay outside the PDU session. Optional (NOTE 4) Yes UE context ProSe Multi-path Preference Indicates whether the traffic of the matching application is to be transmitted via a PDU session via a Uu reference point or via a ProSe Layer-3 UE-to-network relay outside the PDU session.Optional(NOTE 9)YesUE contextAccess Type preferenceIndicates the preferred access type (3GPP or non-3GPP or multi-access) when establishing a PDU session for a matching application.OptionalYesUE contextPDU Session Pair IDIndication shared by the redundant PDU session.OptionalYesUE contextRSN as described in clause 5.33.2.1 of RSNTS 23.501v18.1.0.OptionalYesUE contextRoute Selection Validation Criteria(NOTE 6)This section defines the components of the Route Validation Criteria.OptionalTimeWindowThe time window within which matching traffic is permitted. The RSD is not considered valid if the current time does not fall within this time window.OptionalYesUE contextLocationCriteriaThe UE location within which matching traffic is permitted. If the UE location does not match the location criteria, the RSD rule is not considered valid. OptionalYesUE contextNOTE 1: All path selection descriptors in the list must have different priority values.NOTE 2: At least one of the path selection components must be present.NOTE 3: If the subscription information contains only one S-NSSAI in the UDR, the PCF does not need to provision the UE using the S-NSSAI in the network slice selection information. A "match all" URSP rule contains at most one S-NSSAI.NOTE 4: If this indication is present in the path selection descriptor, no other components shall be included in the path selection descriptor.NOTE 5: SSC mode 3 can be used only when the PDU session type is IP.NOTE 6: If all the provided validation criteria are not met, the path selection descriptor is not considered valid. NOTE 7: The inclusion of validation criteria in a roaming scenario is not considered. NOTE 8: This component shall be present if the path selection component does not include "Non-seamless Offload Indication" or "ProSe Layer-3 UE-to-Network Relay Offload Indication". NOTE 9: If this indication is present in the path selection descriptor, the ProSe Layer-3 UE-to-Network Relay Offload Indication is not included in the path selection descriptor.

[0379] Table 9 is an example of a Route Selection Descriptor (RSD).

[0380] Describes encoding related to URSP. Referring to the example in Table 10, an example of encoding of the UE policy part type URSP is described.

[0381] URSP Rule Precedence Value (octet v+2) The URSP rule precedence value field is used to specify the precedence of a URSP rule among all URSP rules in the URSP. This field contains a binary encoding of the precedence value in the range 0 to 255 (decimal). A higher precedence value field indicates a lower precedence of the URSP rule. Multiple URSP rules in a URSP cannot have the same precedence value. Traffic Descriptor (octets v+5 to w) The Traffic Descriptor field is of variable size and contains a variable number (one or more) of Traffic Descriptor components. Each Traffic Descriptor component is encoded as a sequence consisting of a one-octet Traffic Descriptor Component Type Identifier and a Traffic Descriptor Component Value field. The Traffic Descriptor Component Type Identifier is transmitted first.트래픽 설명자 구성요소 타입 식별자(Traffic descriptor component type identifier)Bits8 7 6 5 4 3 2 10 0 0 0 0 0 0 1 Match-all type0 0 0 0 1 0 0 0 OS Id + OS App Id type (NOTE 1)(NOTE 3)0 0 0 1 0 0 0 0 IPv4 remote address type0 0 1 0 0 0 0 1 IPv6 remote address / prefix length type0 0 1 1 0 0 0 0 Protocol identifier / next header type0 1 0 1 0 0 0 0 Single remote port type (NOTE 6)0 1 0 1 0 0 0 1 Remote port range type (NOTE 6)0 1 0 1 0 0 1 0 IP 3 tuple type0 1 1 0 0 0 0 0 Security parameter index type0 1 1 1 0 0 0 0 Type of service / traffic class type1 0 0 0 0 0 0 0 Flow label type1 0 0 0 0 0 0 1 Destination MAC address type (NOTE 7)1 0 0 0 0 0 1 1 802.1Q C-TAG VID type (NOTE 4)1 0 0 0 0 1 0 0 802.1Q S-TAG VID type (NOTE 4)1 0 0 0 0 1 0 1 802.1Q C-TAG PCP / DEI type (NOTE 4)1 0 0 0 0 1 1 0 802.1Q S-TAG PCP / DEI type (NOTE 4)1 0 0 0 0 1 1 1 Ethertype type1 0 0 0 1 0 0 0 DNN type (NOTE 3)1 0 0 1 0 0 0 0 Connection capabilities type (NOTE 3)1 0 0 1 0 0 0 1 Destination FQDN1 0 0 1 0 0 1 0 Regular expression1 0 1 0 0 0 0 0 OS App Id type (NOTE 3)1 0 1 0 0 0 0 1 Destination MAC address range type (NOTE 7)All other values ​​are preliminary. When received, it is interpreted as unknown....Route selection descriptor component type identifierBits8 7 6 5 4 3 2 10 0 0 0 0 0 0 1 SSC mode type0 0 0 0 0 0 1 0 S-NSSAI type0 0 0 0 0 1 0 0 DNN type0 0 0 0 1 0 0 0 PDU session type type0 0 0 1 0 0 0 0 Preferred access type type (NOTE 2)0 0 0 1 0 0 0 1 Multi-access preference type (NOTE 2)0 0 1 0 0 0 0 0 Non-seamless non-3GPP offload indication type0 1 0 0 0 0 0 0 Location criteria type1 0 0 0 0 0 0 0 Time window type1 0 0 0 0 0 0 1 5G ProSe layer-3 UE-to-network relay offload indication type1 0 0 0 0 0 1 0 PDU session pair ID type (NOTE 5) All other values ​​are reserved. If received, they will be interpreted as unknown....For " time window type ", the path selection descriptor component value field is encoded as a sequence of a Starttime field and a Stoptime field. The Starttime field is expressed in seconds since 00:00:00, January 1, 1970, and is encoded in the 64-bit NTP timestamp format defined in IETF RFC 5905. The integer portion of the Starttime field is binary encoded in the first 32 bits, and the fractional portion is binary encoded in the last 32 bits. The encoding of the Stoptime field is identical to that of the Starttime field.

[0382] The example in Table 10 is an example of the contents of a UE policy part containing a URSP rule.

[0383] Conventional technology suffers from the problem of only supporting BDT at specific time periods, as in the example described above. The AF may, or may desire, negotiate BDT operations in a periodic fashion / pattern. In such cases, conventional technology requires the AF to repeatedly perform the BDT negotiation procedure with the 5G CN every cycle. This procedure leads to inefficiency. A solution is needed to address these inefficiencies.

[0384] For example, examples of scenarios where BDT operations are performed in a periodic form / pattern can vary and include:

[0385] - In cases where the factory periodically uploads logs of work performed by product assembly terminals to a server, the factory may also periodically upload video data recorded by worksite recording terminals to the server. Here, the cycle may be, for example, every Sunday (i.e., once a week) between a certain time and a certain time, every two weeks between a certain time and a certain time on Saturday, or every three days between a certain time and a certain time.

[0386] - There may be instances where the factory periodically downloads / updates work instructions / work instructions / design drawings to the product assembly terminal, or transmits report instructions based on event occurrences to the product assembly terminal. Here, the cycle could be, for example, every Sunday (i.e., every week) between a certain time and a certain time, every three weeks between a certain time and a certain time, or every day between a certain time and a certain time.

[0387] In a factory, a production process support robot may periodically transmit work progress data to a server. This cycle may be, for example, every Sunday (i.e., once a week) between a certain time and a certain time, every two weeks between a certain time and a certain time on Saturday, or every day between a certain time and a certain time.

[0388] - There may be instances where the campus / school periodically downloads / updates the following week's class schedule, presentation materials, textbooks, videos, etc. via electronic whiteboard terminals or electronic podium terminals. Here, the cycle could be, for example, every week (i.e., weekly) between a certain time and a certain time on Saturday, once every four weeks (or once a month or monthly) between a certain time and a certain time on Sunday, or every two weeks between a certain time and a certain time on Sunday, etc.

[0389] The period expressed as "from hour to hour" above is merely an example, and the scope of the disclosure of this specification is not limited thereto. Examples of the period may include units of minutes or seconds, such as "hour, minute, hour, minute, and second."

[0390] The above scenarios can also be applied by laying a private network (or non-public network) in a factory or campus.

[0391] Various examples of the disclosure herein describe methods for supporting periodic background data transfer. Methods for supporting periodic background data transfer may be comprised of a combination of one or more of the following operations / configurations / steps.

[0392] In this specification, UE (User Equipment) and terminal may be used as terms with the same meaning.

[0393] In this specification, AF (Application Function) can be interpreted as Application Server. AF or AS can also be expressed as a network node (or network entity) associated with the application.

[0394] In this specification, URSP, URSP rule and URSP rules may be used as terms with the same meaning.

[0395] In this specification, performing a BDT operation in a periodic form / pattern may mean the following examples. For example, it may mean performing data transmission routinely, regularly, in a scheduled form / pattern, in a Time Controlled form / pattern, or repeatedly.

[0396] [1-1] First example of disclosure of this specification

[0397] A first example of the disclosure of this specification is described.

[0398] When Background Data Transfer negotiation procedures are performed between the AF and the 5G CN, periodic information (or periodic timing information, or periodic time validation information) may be included. For example, the AF may transmit a message related to BDT negotiation to the 5G CN. Here, the message transmitted by the AF may include periodic information.

[0399] When AF performs BDT negotiation-related operations with NEF (for example, when sending an Nnef_BDTPNegotiation_Create Request message), it may include cycle-related information. For example, the Nnef_BDTPNegotiation_Create Request message sent by AF may include cycle-related information. This cycle-related information may be configured / expressed in various formats / types / parameters. The unit of the cycle may be various, such as minutes, hours, days, weeks, fortnights, months, quarters, halves, years, etc. Various values, such as every few seconds, every few minutes, every few hours, and every few days, may be used to express the cycle. For example, if the cycle is expressed as 168 hours, it may mean that BDT is performed on a weekly basis.

[0400] Additionally, various forms of cycles can be used, as described in the BDT operation in the periodic form / pattern performed in the factory according to the example described above.

[0401] The information regarding periodicity provided (or included) by AF may be applied throughout this specification.

[0402] For example, the periodic information transmitted by AF may be in the form of a Time of Day (Time of Day) that constitutes the WLAN Selection Policy (WLANSP) defined in TS 24.526 v18.2.0, or an extension thereof. An example of the encoding of WLANSP is described below.

[0403] The purpose of the WLANSP field is to indicate rules related to wireless LAN selection and reselection. The WLANSP field can be encoded as shown in the examples in Tables 11 through 18 below.

[0404] 87654321Length of WLANSP ruleoctet 4octet 5Rule identifieroctet 6Rule priorityoctet 7Roamingvalidity area ind3GPP loc indWLAN loc indGeo loc indtime of day ind0spare0spareoctet 8Selection criteriaoctet 9octet rValidity areaoctet r+1*octet s*Time of dayoctet s+1*octet u*

[0405] Table 11 shows an example of a WLANSP rule. A WLANSP rule may include, for example, the length of the WLANSP rule, a rule identifier, a rule priority, a selection criterion, a validity area, and a time.

[0406] 87654321Length of time of dayoctet s+1octet s+2number of time of day entriesoctet s+3Time of day entry 1octet s+4octet n1Time of day entry 2octet n1+1*octet n2*...octet n2+1*octet n3*Time of day entry noctet n3+1*octet u*

[0407] Table 12 is an example of the Time of day included in Table 11.

[0408] 87654321Length of time of day entryoctet s+4octet s+5number of sub fieldsoctet s+6*ToD sub field 1octet s+7octet z1ToD sub field 2octet z1+1*octet z2*......octet z2+1*octet z3*ToD sub field yoctet z3+1*octet n1*

[0409] The example in Table 13 is an example of the subfield of Time of day in Table 12.

[0410] 87654321Length of ToD sub fieldoctet s+7*ToD sub field typeoctet s+8*ToD sub field contentsoctet s+9octet f

[0411] Table 14 is an example of the ToD sub field in Table 13.

[0412] 87654321Length of ToD sub fieldoctet s+7*ToD sub field type ={time start, time stop}octet s+8*ToD sub field contentsoctet s+9octet f

[0413] Table 15 is an example of the ToD subfield in Table 13. In the example in Table 15, the field type of the ToD subfield can be either "time start" or "time stop."

[0414] 87654321Length of ToD sub fieldoctet s+7*ToD sub field type ={ date start, date stop}octet s+8*ToD sub field contentsoctet s+9octet f

[0415] Table 16 is an example of the ToD subfield in Table 13. In the example in Table 16, the field type of the ToD subfield can be either "date start" or "date stop."

[0416] 87654321Length of ToD sub fieldoctet s+7*ToD sub field type ={ day of week}octet s+8*1MonTueWedThuFriSatSunoctet s+9

[0417] Table 17 is an example of the ToD sub field in Table 13. In the example in Table 17, the field type of the ToD sub field may be "day of the week."

[0418] The value part of the WLANSP information element (octets 4 to x) AND the SP Info type (bits 1 to 4 of octet 1) is set to "0001" (WLANSP). Bits 8 to 5 of octet 1 are spare and are encoded as 0. Length of WLANSP content (octets 2 to 3) Length of WLANSP rule (octets 4 to 5) Rule identifier (octet 6) This field contains a binary encoding of the WLANSP rule identifier. Rule priority (octet 7) This field contains a binary encoding of the WLANSP rule priority. Spare bits and are encoded as 0. (bits 1 to 2 of octet 8)Time of day index (bit 3 of octet 8)Bit30 WLANSP rules do not contain time information.1 WLANSP rules contain time of day information....Time of day (octets s+1 to u)This field contains a binary encoding of the time of day condition for a particular WLANSP rule.ToD subfield type ={time start, time stop, date start, date stop, day of week} (octet s+8)Bits8 7 6 5 4 3 2 10 0 0 0 0 0 0 1 time start0 0 0 0 0 1 0 time stop0 0 0 0 0 1 0 0 date start0 0 0 1 0 0 0 date stop0 0 0 1 0 0 0 day of the weekAll other values ​​are reserved.If the field type is " time start " or " If the field type is set to " time stop ", the value of this ToD subfield content is the time of day expressed in string format as defined in ISO 8601:2004. If the field type is set to " date start " or " date stop ", the value of this ToD subfield content is the date expressed in string format as defined in ISO 8601:2004.If the field type is set to "day of the week", the value of this ToD subfield content will be an 8-bit integer in bitmap format representing the day of the week. The most significant bit is set to 1. The remaining bits represent the day of the week.

[0419] Table 18 shows an example of a WLANSP information element.

[0420] The period-related information provided by the AF to the NEF may be used / provided in subsequent BDT-related procedures. For example, the period-related information may be included in the Npcf_BDTPolicyControl_Create Request message transmitted by the NEF to the PCF. The period-related information may be provided / included in messages that can be used in connection with BDT, in which existing time-related information (desired time window or time window parameters) is provided / included.

[0421] The above period-related information may be included / provided by extending an existing desired time window or time window parameter (or information element or data type). Alternatively, the period-related information may be included / provided as a separately defined parameter.

[0422] PCF can use / reference the period-related information provided by AF when setting the BDT policy.

[0423] [1-2] Second example of disclosure of this specification

[0424] As described in [1-1] above, the AF can provide cycle-related information to the NEF. The PCF can set a BDT policy based on the cycle-related information. At this time, the PCF can set recommended cycle-related information. Based on the recommended cycle-related information, the PCF can set the cycle-related information when setting a URSP (UE Route Selection Policy) rule for the UE.

[0425] Based on the recommended period-related information included in the BDT policy, the PCF can establish a URSP rule. For the operation in which the PCF uses the recommended period-related information included in the BDT policy, an example in which the recommended time window information included in the existing BDT policy is used when establishing a URSP rule can be referenced (see Section 6.1.2.4 of TS 23.503 v18.1.0).

[0426] The above period-related information may also be included as part of the Route Selection Validation Criteria. In this case, the period-related information may be included by defining new information / parameters or by extending the time window. Alternatively, the newly defined information / parameters may be included in the Route Selection Descriptor (RSD). The period-related information may be included in the URSP rule in various forms. This period-related information may be configured / expressed in various formats / forms / parameters, and the contents described in [1-1] above may be referenced for details. This can be applied throughout this specification.

[0427] For reference, the example in Table 19 below shows an example of an RSD that constitutes a URSP rule.

[0428] Information Name Description Category PCF permitted to modify information in URSP Scope Route Selection Descriptor Precedence Determines the order in which Route Selection Descriptors are applied. Mandatory (NOTE 1) Yes UE context Route selection components This section defines the route selection components. Mandatory (NOTE 2) SSC Mode Selection A single value for the SSC mode. (NOTE 5) Optional Yes UE context Network Slice Selection A single value or a list of values ​​for the S-NSSAI. Optional (NOTE 3) Yes UE context DNN Selection A single value or a list of values ​​for the DNN. Optional Yes UE context PDU Session Type Selection A single value for the PDU session type. Conditional (NOTE 8) Yes UE context Non-Seamless Offload indication Indicates whether the traffic of the matching application will be offloaded to non-3GPP access outside the PDU session. Optional (NOTE 4) Yes UE context ProSe Layer-3 UE-to-Network Relay Offload indication Indicates whether the traffic of the matching application is to be transmitted via a ProSe Layer-3 UE-to-network relay outside the PDU session. Optional (NOTE 4) Yes UE context ProSe Multi-path Preference Indicates whether the traffic of the matching application is to be transmitted via a PDU session via a Uu reference point or via a ProSe Layer-3 UE-to-network relay outside the PDU session.Optional(NOTE 9)YesUE contextAccess Type preferenceIndicates the preferred access type (3GPP or non-3GPP or multi-access) when establishing a PDU session for a matching application.OptionalYesUE contextPDU Session Pair IDIndication shared by the redundant PDU session.OptionalYesUE contextRSNTS 23.501 V18.1.0, clause 5.33.2.1.OptionalYesUE contextRoute Selection Validation Criteria(NOTE 6)This section defines the components of the Route Validation Criteria.OptionalTimeWindowThe time window within which matching traffic is permitted. The RSD is not considered valid if the current time does not fall within this time window.OptionalYesUE contextLocationCriteriaThe UE location within which matching traffic is permitted. If the UE location does not match the location criteria, the RSD rule is not considered valid. OptionalYesUE contextNOTE 1: All path selection descriptors in the list must have different priority values.NOTE 2: At least one of the path selection components must be present.NOTE 3: If the subscription information contains only one S-NSSAI in the UDR, the PCF does not need to provision the UE using the S-NSSAI in the network slice selection information. A "match all" URSP rule contains at most one S-NSSAI.NOTE 4: If this indication is present in the path selection descriptor, no other components shall be included in the path selection descriptor.NOTE 5: SSC mode 3 can be used only when the PDU session type is IP.NOTE 6: If all the provided validation criteria are not met, the path selection descriptor is not considered valid. NOTE 7: The inclusion of validation criteria in a roaming scenario is not considered. NOTE 8: This component shall be present if the path selection component does not include "Non-seamless Offload Indication" or "ProSe Layer-3 UE-to-Network Relay Offload Indication". NOTE 9: If this indication is present in the path selection descriptor, the ProSe Layer-3 UE-to-Network Relay Offload Indication is not included in the path selection descriptor.

[0429] Table 19 is an example of a Route Selection Descriptor (RSD).

[0430] A UE can receive a URSP rule containing periodic information. Based on the periodic information, the UE can perform periodic BDT operations. For example, based on the indications of the periodic information, the UE can periodically establish a PDU session for BDT. Such UE operations can be applied throughout this specification.

[0431] [1-3] Third example of disclosure of this specification

[0432] The AF may utilize the Application Guidance for URSP determination procedure. Based on this procedure, the AF may ensure that the URSP (UE Route Selection Policy) rule includes period-related information.

[0433] For reference, for procedures / actions related to Application guidance for URSP determination, reference may be made to TS 23.502 V18.1.1, clauses 4.15.6.7 and 4.15.6.10, and TS 23.548, clause 6.6.

[0434] The example in Figure 10 is an example of the Service specific parameter provisioning procedure defined in section 4.15.6.7 of TS 23.502.

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

[0436] FIG. 10 is an example of a service specific parameter provisioning procedure according to one embodiment of the disclosure of the present specification.

[0437] 0a and 0b. UE registration procedures can be performed. For specific registration procedures, refer to the examples in FIGS. 5 and 6. The AMF can perform operations related to policy association with the PCF. The PCF can send a subscription message to the UDR.

[0438] 1. AF can generate AF requests.

[0439] 2. AF can send request messages related to creating, updating, or deleting service parameters to NEF.

[0440] For reference, for the example in Fig. 10, the specific operation can refer to the Service specific parameter provisioning procedure defined in section 4.15.6.7 of TS 23.502.

[0441] According to one embodiment of the disclosure of the present specification, in step 2, the AF may perform the following actions. For example, the AF may send an Nnef_ServiceParameter_Create Request message to the NEF. The AF may include period-related information in the request message sent to the NEF. Thus, the period-related information may be used or included when the PCF sets the URSP rule.

[0442] 2a. NEF can call UDM and Nudm_SDM_Get services.

[0443] 2b. Authorization of service-specific parameters can be performed.

[0444] 3. Information may be stored, updated, or removed.

[0445] 4. NEF can send a response message to AF for the request message received in step 2.

[0446] 5. UDR can send notification messages to PCF.

[0447] 6. The PCF can perform AMF, (R)AN, UE, and UE policy delivery procedures. Based on the policy delivery procedures, URSP rules, configured by considering period-related information provided by the AF, can be delivered to the UE.

[0448] 7. PCF may also send notification messages to NEF.

[0449] 8. NEF can also send notification messages to AF.

[0450] [1-4] Fourth example of disclosure of this specification

[0451] According to the prior art, a terminal can establish a PDU session using a matching RSD in a URSP rule. After the PDU session is established, the validity condition in the RSD of the used URSP rule may become invalid or unfulfilled. However, even if the validity condition becomes invalid or unfulfilled, the terminal does not release the corresponding PDU session.

[0452] One embodiment of the disclosure of this specification may allow a terminal or AF to transmit application traffic only when a validity condition is satisfied. To this end, the terminal may remember (or store) the RSD used when establishing a PDU Session used by the application. The terminal may check the validity condition included in the RSD.

[0453] The validity condition may be invalid / not fulfilled (i.e., the validity condition may no longer be valid or fulfilled). In this case, the terminal may release the corresponding PDU Session. If the terminal has not completed traffic transmission, the terminal may notify the application server of this failure or that the session connection has been disconnected before releasing the PDU Session.

[0454] Due to validity conditions, a terminal may not be able to establish a PDU session using an RSD. In this case, according to the prior art, the terminal attempts to establish a PDU session based on a low-priority RSD or / Traffic Descriptor. In this case, for application traffic that should be transmitted only at a specific time / location, the terminal may establish a PDU session using a different RSD without validity conditions and transmit the traffic at any time / location.

[0455] In order to prevent such behavior, the following actions may be applied in the disclosure of this specification. The PCF may include an indication of whether an RSD / Traffic Descriptor with low priority may be used in the Traffic Descriptor or RSD of the URSP rule. If the terminal receives such an indication, the terminal may fail to establish a PDU session based on the selected RSD. In this case, the terminal notifies the application layer that the PDU session establishment has failed and does not perform conventional operations (e.g., attempting to establish a PDU session using a different RSD / Traffic Descriptor). When the terminal notifies that the PDU session has failed, the terminal may inform the application layer of validity condition information regarding the RSD. Based on this information, the application layer may attempt to transmit traffic again later.

[0456] Hereinafter, with reference to FIGS. 11A and 11B, an example of a procedure according to various examples including Examples 1 to 4 of the disclosure of the present specification is described.

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

[0458] FIG. 11A and FIG. 11B illustrate an example of a procedure according to one embodiment of the disclosure of the present specification.

[0459] In FIG. 11a and FIG. 11b, the UE policy PCF can be interpreted as a PCF for UE or a PCF for UE policy, and the SM PCF can be interpreted as a PCF for PDU Session or a PCF for Session Management. The UE Policy PCF and the SM PCF may be the same PCF or different PCFs.

[0460] 1. The UE can perform a registration procedure with the 5G core network. The specific operations of the registration procedure can be seen in the examples in FIGS. 5 and 6. At this time, the UE policy PCF can subscribe to a service that notifies the UE of parameter and information updates regarding the UDR. For example, step 0b of FIG. 10 can be performed.

[0461] 2. The UE can establish a PDU Session. For example, the PDU session establishment procedure can be performed based on the examples of FIGS. 7 and 8.

[0462] 3. The UE can exchange information related to periodic BDT with the AF (or Application Server). Alternatively, the UE can receive configuration related to periodic BDT from the AF. The operation of step 3 can be performed based on application layer messages exchanged between the UE and the AF via the PDU Session established in step 2. The periodic BDT-related information / configuration can include, for example, information about the cycle for performing BDT.

[0463] If the PDU Session established in Step 2 is no longer needed, the PDU Session may be released. For example, the UE may release the PDU Session after receiving information related to the periodic BDT from the AF.

[0464] 4-10. Negotiation for future background data transfer according to the example of FIG. 9 may be referenced. For example, steps 4 and 5 may be performed in the same manner as steps 1 and 2 of FIG. 9. Step 6 may be performed in the same manner as steps 3 and 4 of FIG. 9. Steps 7 and 9 may be performed in the same manner as steps 5 and 7 of FIG. 9. The BDT policy update operation of step 10 may be performed in the same manner as steps 8 to 13 of FIG. 9.

[0465] A BDT negotiation procedure that includes the period-related information (or periodic time information, or periodic time validation information) proposed in this specification can be performed. In step 4, the AF can transmit the period-related information to the NEF. In step 7, the PCF can use / reference the period-related information provided by the AF when establishing the BDT policy. In step 8, the PCF can provide the AF with a BDT policy that includes the period-related information.

[0466] For steps 4 to 10, specific operations may be referred to the first example of the disclosure of [1-1] this specification.

[0467] 11. The UDR can store the UE's BDT policy. The UDR can provide information about the BDT policy to the PCF.

[0468] 12. PCF can configure URSP rules related to the periodic BDT policy. For example, PCF can configure URSP rules that include periodic information. For a detailed description of the actions performed by PCF, see Example 2 of the disclosure of [1-2].

[0469] [1-3] As described in the third example of the disclosure of this specification, the AF may use the Application guidance for URSP determination procedure to have the PCF configure URSP rules related to the periodic BDT policy. The operations described in the third example of the disclosure of this specification may additionally be performed for steps 4 to 10 of FIGS. 11A and 11B.

[0470] 13. PCF can provide URSP rules to the UE based on the UE policy delivery procedure. Section 4.2.4.3 of TS 23.502 can be referenced.

[0471] 14. Afterwards, the UE can establish a PDU Session for performing BDT based on the URSP rule provided above. The PDU Session for BDT and the PDU Session for exchanging BDT-related information / configuration with the AF (e.g., the PDU Session established in Step 2) may be the same PDU Session or different PDU Sessions.

[0472] 15. UE can perform BDT with AF (or Application Server).

[0473] [1-4] As described in the fourth example of the disclosure of this specification, the UE may release the PDU Session.

[0474] If the BDT execution cycle needs to be changed, the UE can exchange periodic BDT-related information with the AF (or Application Server) again or receive periodic BDT-related configuration from the AF again. For these operations, refer to steps 2 and 3 described above.

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

[0476] FIG. 12 illustrates an example of the operation of AF and NEF according to one embodiment of the disclosure of the present specification.

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

[0478] For example, with respect to the example of FIG. 12, the operations described in the examples of FIGS. 1 to 11A and 11B may also be applied. For example, even if operations, contents, etc. are not directly described in the example of FIG. 12, operations, contents, etc. described in various examples of the disclosure of this specification may be applied.

[0479] The AF may also send an application layer message to the UE containing information related to the BDT period.

[0480] In step (S1201), the AF may transmit a request message. For example, the AF may transmit a request message related to background data transfer negotiation to the NEF.

[0481] The request message may include information related to the BDT cycle. The NEF may send a BDT policy control-related message containing information related to the BDT cycle to the PCF.

[0482] The request message may be a Nnef_BDTPNegotiation_Create request message.

[0483] In step (S1202), the NEF may transmit a response message to the AF. The response message may include BDT policy information generated based on information related to the BDT cycle.

[0484] The response message may be a Nnef_BDTPNegotiation_Create response message.

[0485] Information related to the BDT period can be used by the PCF to generate URSP rules to be transmitted to the UE. Based on the URSP rules, the UE can perform BDT-related actions with the network node (e.g., AF) associated with the application.

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

[0487] FIG. 13 illustrates an example of operations according to one embodiment of the disclosure of the present specification.

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

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

[0490] For reference, the PCF in the example of FIG. 13 may be the PCF in the case where the UE Policy PCF and the SM PCF in the examples of FIGS. 11a and 11b are the same. Alternatively, although one PCF is illustrated in the example of FIG. 13, two PCFs (e.g., the UE Policy PCF and the SM PCF in FIGS. 11a and 11b) may perform their respective operations.

[0491] For reference, steps (S1301), (S1304), (S1305), and (S1306) may be optionally performed.

[0492] In step (S1301), the UE may transmit a BDT-related message to the AF. The AF may transmit the BDT-related message to the UE. The BDT-related message may be an application layer message. The BDT-related message may be transmitted through a PDU session established by the UE.

[0493] The AF may also send an application layer message to the UE containing information related to the BDT period.

[0494] Before step (S1301) is performed, the UE may perform a registration procedure (e.g., see examples in FIGS. 5 and 6). The UE may perform a PDU session establishment procedure (e.g., see examples in FIGS. 7 and 8). For example, the UE may transmit a registration request message. For example, the UE may receive a registration acceptance message.

[0495] In step (S1302), the AF may transmit a request message. For example, the AF may transmit a request message related to background data transfer negotiation to the NEF.

[0496] The request message may include information related to the BDT cycle. The NEF may send a BDT policy control-related message containing information related to the BDT cycle to the PCF.

[0497] Information related to the BDT period can be used by the PCF to generate URSP rules to be transmitted to the UE. Based on the URSP rules, the UE can perform BDT-related actions with the network node (e.g., AF) associated with the application.

[0498] For example, PCF can determine policies for BDT based on information related to the BDT cycle. For example, PCF can generate PCC rules based on information related to the BDT cycle. For example, PCF can generate URSP rules based on information related to the BDT cycle.

[0499] In step (S1303), the NEF may transmit a response message to the AF. The response message may include BDT policy information generated based on information related to the BDT cycle.

[0500] The response message may be a Nnef_BDTPNegotiation_Create response message.

[0501] In step (S1304), the PCF may transmit URSP rule information including information related to the cycle of BDT to the UE.

[0502] In step (S1305), the UE may perform a PDU session establishment procedure to establish a PDU session for BDT based on the URSP rules. For example, the UE may transmit a PDU session establishment request message to the SMF. The UE may receive a PDU session establishment acceptance message from the SMF.

[0503] For example, the UE may periodically establish a PDU session for the BDT based on the period of the BDT.

[0504] For example, the UE can check the validity condition based on the BDT cycle. For example, based on the URSP rule, the UE can check whether the application traffic satisfies the validity condition related to the BDT cycle. If the validity condition related to the BDT cycle is invalid, the UE can send a PDU Session Release Request message to the SMF to release the PDU session for the BDT.

[0505] In step (S1306), the UE can perform an operation related to BDT based on the PDU session for BDT.

[0506] If the cycle of the above BDT is changed, the UE may receive an application layer message containing information related to the changed BDT cycle from a network node (e.g., AF) associated with the application.

[0507] According to one embodiment of the present specification, the AF can perform BDT negotiation with the NEF. The AF can transmit period-related information during the BDT negotiation process.

[0508] According to one embodiment of the present specification, a PCF (e.g., a PCF performing Session Management or a PCF managing a PDU Session) may perform operations such as setting / providing a BDT policy, controlling / managing a PDU Session of a UE, etc. based on period-related information. For reference, the description in Section 6.1.2.4 of TS 23.503 may be applied to operations related to period-related information.

[0509] According to one embodiment of the present specification, a PCF (e.g., a PCF managing UE policy) can set a URSP rule for a UE based on period-related information. The PCF can provide the URSP rule to the UE.

[0510] According to one embodiment of the present specification, a URSP rule may include period-related information. In this case, the UE may establish a PDU session and perform BDT operations based on the period-related information. For reference, section 6.6.2.3 of TS 23.503 may be referenced for operations based on period-related information.

[0511] This specification may have various effects.

[0512] For example, periodic BDT operations can be effectively supported. For example, an AF may wish to perform BDT operations in a periodic fashion / pattern. In such cases, the AF can perform BDT negotiation with the 5G CN based on the period-related information it provides. This eliminates the inefficiency of the prior art, where the AF must repeatedly perform BDT negotiation procedures with the 5G CN every period.

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

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

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

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

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

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

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

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

Claims

1. In the method of communication between network nodes related to the application, A step of sending a request message related to Background Data Transfer (BDT) negotiation to NEF; comprising a step of receiving a response message to the request message from the NEF; The above request message includes information related to the cycle of the BDT, A method characterized in that information related to the cycle of the BDT is included in a message related to BDT policy control transmitted by the NEF to the PCF.

2. In paragraph 1, A method characterized in that the above response message includes BDT policy information generated based on information related to the cycle of the BDT.

3. In paragraph 1 or 2, The above request message is a Nnef_BDTPNegotiation_Create request message, A method characterized in that the above response message is a Nnef_BDTPNegotiation_Create response message.

4. In any one of paragraphs 1 to 3, A method further comprising the step of transmitting an application layer message including information related to the cycle of the BDT to a User Equipment (UE).

5. In any one of paragraphs 1 to 4, A method characterized in that information related to the cycle of the BDT is used to generate a UE Route Selection Policy (URSP) rule to be transmitted to the UE by the PCF or another PCF managing the UE policy.

6. In any one of paragraphs 1 to 5, A method characterized in that the above URSP rule is used to establish a Packet Data Unit (PDU) session used by the UE to perform BDT-related operations with a network node associated with the application.

7. In a network node related to an application performing communication, the network node related to the application: One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; A network node associated with an application, wherein the operation performed based on the above command being executed by the one or more processors is a method according to any one of claims 1 to 6.

8. In the method of User Equipment (UE) performing communication, Step of sending a registration request message; Step of receiving a registration acceptance message; A step of receiving a UE Route Selection Policy (URSP) rule including information related to a period of Background Data Transfer (BDT) from a PCF; A step of transmitting a Packet Data Unit (PDU) session establishment request message to establish a Packet Data Unit (PDU) session for the BDT based on the above URSP rule; A step of receiving a PDU session establishment acceptance message; and A method comprising the step of performing an operation related to the BDT based on a PDU session for the BDT.

9. In paragraph 8, A method further comprising the step of periodically establishing a PDU session for the BDT based on the cycle of the BDT.

10. In paragraph 8 or 9, A method further comprising the step of receiving an application layer message including information related to the cycle of the BDT from a network node associated with the application.

11. In any one of paragraphs 8 to 10, A method further comprising the step of receiving an application layer message including information related to the changed BDT cycle from a network node associated with the application, when the cycle of the above BDT is changed.

12. In any one of paragraphs 8 to 11, A method further comprising a step of checking whether the validity condition related to the cycle of the BDT is valid for application traffic based on the above URSP rule.

13. In any one of paragraphs 8 to 12, A method further comprising the step of transmitting a PDU session release request message for releasing a PDU session for the BDT when a validity condition related to the cycle of the BDT is invalid.

14. In a UE (User Equipment) configured to operate in a wireless communication system, the UE: One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; The actions performed based on the above instructions being executed by the one or more processors are: A UE according to any one of claims 8 to 13.

15. In the method of PCF performing communication, A step of receiving a request message related to Background Data Transfer (BDT) policy control including information related to the cycle of BDT from NEF; A step of determining a policy related to the BDT based on the cycle of the BDT; A step of transmitting a response message related to BDT policy control including a policy related to the BDT to the NEF; A step of generating a User Equipment (UE) Route Selection Policy (URSP) rule including information related to the cycle of the BDT; and A method comprising the step of transmitting the above URSP rule to the UE.

16. In paragraph 15, A method characterized in that the URSP rule including information related to the cycle of the BDT is used by the UE to establish a Packet Data Unit (PDU) session for the BDT.

17. In the PCF performing communication, the PCF: One or more transmitters and receivers; one or more processors; and comprising one or more memories capable of storing instructions and being operable to the one or more processors; An operation performed based on the above instruction being executed by the one or more processors is a PCF method according to any one of claims 15 or 16.

Citation Information

Patent Citations

  • Policy Determining Method and Apparatus, and System

    US20230040486A1