WO2025071196A1 - Support informatique en périphérie - Google Patents

Support informatique en périphérie Download PDF

Info

Publication number
WO2025071196A1
WO2025071196A1 PCT/KR2024/014486 KR2024014486W WO2025071196A1 WO 2025071196 A1 WO2025071196 A1 WO 2025071196A1 KR 2024014486 W KR2024014486 W KR 2024014486W WO 2025071196 A1 WO2025071196 A1 WO 2025071196A1
Authority
WO
WIPO (PCT)
Prior art keywords
eas
information
dns
message
easdf
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/KR2024/014486
Other languages
English (en)
Korean (ko)
Inventor
김홍석
김래영
김재우
윤명준
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Publication of WO2025071196A1 publication Critical patent/WO2025071196A1/fr
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/289—Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices

Definitions

  • This specification relates to mobile communications.
  • 3GPP(3rd Generation Partnership Project) LTE(Long-Term Evolution) is a technology to enable high-speed packet communication. Many methods have been proposed to achieve the LTE goals of reducing costs for users and operators, improving service quality, expanding coverage, and increasing system capacity. 3GPP LTE requires cost reduction per bit, improved service usability, flexible use of frequency bands, simple structure, open interface, and appropriate power consumption of terminals as upper-level requirements.
  • 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 technology components necessary to successfully standardize NR in a timely manner that meets both urgent market needs and the longer-term requirements presented by the ITU Radio communication sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process.
  • ITU-R ITU Radio communication sector
  • IMT International Mobile Telecommunications
  • 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).
  • eMBB enhanced Mobile Broadband
  • mMTC massive Machine Type-Communications
  • URLLC Ultra-Reliable and Low Latency Communications
  • Edge computing services can be supported for terminals. However, in the past, edge computing services had to be provided using only static information provided by AF in the network. There is a problem that edge computing services cannot be effectively supported when the network environment, such as EAS load conditions, changes dynamically.
  • a method may include the steps of transmitting an NF discovery request message to an NRF, the NF discovery request message including information querying information that an AF can provide; receiving an NF discovery response message from the NRF; receiving an event notification message from the NEF; and transmitting a request message requesting EAS re-discovery to an SMF serving the UE.
  • a device implementing the method is provided.
  • a method may include the steps of: receiving a PDU Session Establishment Request message from a UE; transmitting a PDU Session Establishment Accept message to the UE; receiving a request message requesting EAS re-discovery from an EASDF; and transmitting a PDU Session Modification Command message including information requesting the EAS re-discovery to the UE.
  • a device implementing the method is provided.
  • a method comprises the steps of: transmitting a PDU session establishment request message to an SMF; receiving a PDU session establishment acceptance message from the SMF; and receiving a PDU session modification command message from the SMF, the PDU session modification command message including information requesting the EAS re-discovery.
  • a device implementing the method is provided.
  • Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.
  • Figure 2 illustrates an example of a wireless device to which the implementation of this specification is applied.
  • Figure 3 shows an example of a UE to which the implementation of this specification is applied.
  • Figure 4 shows an example of a 5G system structure to which the implementation of this specification is applied.
  • FIGS 5 and 6 illustrate examples of PDU session establishment procedures to which the implementation of this specification applies.
  • FIG. 7a and FIG. 7b are examples of an EAS search procedure based on EASDF according to one embodiment of the disclosure of the present specification.
  • FIG. 8 illustrates an example of an EAS discovery procedure based on a local DNS server/resolver according to one embodiment of the disclosure of the present specification.
  • FIGS. 9A and 9B illustrate examples of an EAS re-search procedure according to one embodiment of the disclosure of the present specification.
  • FIG. 10 illustrates an example of operations according to one embodiment of the disclosure of the present specification.
  • CDMA Code Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • TDMA Time Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • MC-FDMA Multi-Carrier Frequency Division Multiple Access
  • CDMA can be implemented via wireless technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000.
  • TDMA can be implemented via wireless technologies such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data rates for GSM Evolution (EDGE).
  • GSM Global System for Mobile communications
  • GPRS General Packet Radio Service
  • EDGE Enhanced Data rates for GSM Evolution
  • OFDMA can be implemented over wireless technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA).
  • UTRA is part of Universal Mobile Telecommunications System (UMTS).
  • 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) is part of Evolved UMTS (E-UMTS) using E-UTRA.
  • 3GPP LTE uses OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL).
  • Evolutions of 3GPP LTE include LTE-A (Advanced), LTE-A Pro, and/or 5G NR (New Radio).
  • a or B can mean “only A”, “only B”, or “both A and B”. In other words, 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”.
  • a slash (/) or a comma can mean “and/or”.
  • A/B can mean “A and/or B”.
  • A/B can mean "only A”, “only B”, or “both A and B”.
  • A, B, C can mean "A, B, or C”.
  • At least one of A and B can mean “only A”, “only B” or “both A and B”. Additionally, as used herein, the expressions “at least one of A or B” or “at least one of A and/or B” can be interpreted identically to “at least one of A and B”.
  • 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”.
  • control information when it is indicated as “control information (PDCCH)", “PDCCH” may be proposed as an example of “control information”.
  • control information in this specification is not limited to “PDCCH”, and “PDCCH” may be proposed as an example of "control information”.
  • control information i.e., PDCCH
  • PDCCH control information
  • Figure 1 illustrates an example of a communication system to which the implementation of this specification is applied.
  • the 5G usage scenarios shown in Fig. 1 are only examples, and the technical features of this specification can be applied to other 5G usage scenarios not shown in Fig. 1.
  • enhanced mobile broadband eMBB
  • massive machine type communications mMTC
  • ultra-reliable and low latency communications URLLC
  • a communication system (1) includes wireless devices (100a to 100f), a base station (BS; 200), and a network (300).
  • FIG. 1 describes a 5G network as an example of a network of the communication system (1), but the implementation of the present specification is not limited to a 5G system, and can be applied to future communication systems beyond the 5G system.
  • 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.
  • the wireless devices (100a to 100f) represent devices that perform communications using Radio Access Technology (RAT) (e.g., 5G NR or LTE) and may also be referred to as communication/wireless/5G devices.
  • RAT Radio Access Technology
  • 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).
  • the vehicles may include vehicles having wireless communication functions, autonomous vehicles, and vehicles capable of performing vehicle-to-vehicle communication.
  • the vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones).
  • UAVs unmanned aerial vehicles
  • 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), HUD (Head-Up Display) mounted on vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, 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.
  • wireless devices may be referred to as user equipment (UE).
  • the UE may include, for example, a mobile phone, a smart phone, a laptop computer, a digital broadcasting terminal, a PDA (Personal Digital Assistant), a PMP (Portable Multimedia Player), 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.
  • PDA Personal Digital Assistant
  • PMP Portable Multimedia Player
  • 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).
  • vehicles can communicate directly (e.g., vehicle-to-vehicle (V2V)/vehicle-to-everything (V2X) communication).
  • IoT devices e.g., sensors
  • IoT devices can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).
  • Wireless communications/connections 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).
  • the wireless communications/connections can be established through various RATs (e.g., 5G NR), such as uplink/downlink communications (150a), sidelink communications (150b) (or, D2D (Device-To-Device) communications), and inter-base station communications (150c) (e.g., relay, IAB (Integrated Access and Backhaul)).
  • 5G NR 5G NR
  • uplink/downlink communications 150a
  • sidelink communications 150b
  • D2D Device-To-Device
  • inter-base station communications e.g., relay, IAB (Integrated Access and Backhaul)
  • wireless communications/connections 150a, 150b, 150c
  • the wireless devices (100a to 100f) and the base station (200) can transmit/receive wireless signals to/from each other.
  • wireless communication/connection 150a, 150b, 150c
  • wireless communication/connection can transmit/receive signals through various physical channels.
  • 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.
  • NR supports multiple numerologies or subcarrier spacings (SCS) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands; when the SCS is 30 kHz/60 kHz, it supports dense-urban, lower latency, and wider carrier bandwidth; and when the SCS is 60 kHz or higher, it supports a bandwidth greater than 24.25 GHz to overcome phase noise.
  • SCS subcarrier spacings
  • the NR frequency band can be defined by two types of frequency ranges (FR1, FR2).
  • the numerical values of the frequency ranges can be changed.
  • the two types of frequency ranges (FR1, FR2) can be as shown in Table 1 below.
  • FR1 can mean "sub 6GHz range”
  • FR2 can mean “above 6GHz range” and can be called millimeter wave (mmW).
  • mmW millimeter wave
  • Frequency range definition Frequency range Subcarrier spacing FR1 450MHz - 6000MHz 15, 30, 60kHz FR2 24250MHz - 52600MHz 60, 120, 240kHz
  • FR1 can include a band of 410 MHz to 7125 MHz as shown in Table 2 below. That is, FR1 can include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher.
  • the frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher included in FR1 can include an unlicensed band.
  • the unlicensed band can be used for various purposes, for example, it can be used for communications for vehicles (e.g., autonomous driving).
  • Frequency range definition Frequency range Subcarrier spacing FR1 410MHz - 7125MHz 15, 30, 60kHz FR2 24250MHz - 52600MHz 60, 120, 240kHz
  • the wireless communication technology implemented in the wireless device of the present specification may include LTE, NR, and 6G, as well as narrowband IoT (NB-IoT) for low-power communication.
  • the 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.
  • the wireless communication technology implemented in the wireless device of the present specification may perform communication based on LTE-M technology.
  • the LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced MTC).
  • the 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.
  • 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.
  • the 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.
  • Figure 2 illustrates an example of a wireless device to which the implementation of this specification is applied.
  • the first wireless device (100) and/or the second wireless device (200) may be implemented in various forms depending on the usage example/service.
  • ⁇ 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.
  • 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).
  • a transceiver such as a transceiver (106)
  • a processing chip such as a processing chip (101)
  • antennas 108
  • 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).
  • the processor (102) may control the memory (104) and/or the transceiver (106), and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed herein.
  • 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).
  • 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.
  • 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.
  • the firmware and/or software code (105) may control the processor (102) to perform one or more protocols.
  • the firmware and/or software code (105) may control the processor (102) to perform one or more wireless interface protocol layers.
  • the processor (102) and the 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 coupled to the processor (102) to 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) section.
  • the first wireless device (100) may represent a communication modem/circuit/chip.
  • 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).
  • a transceiver such as a transceiver (206)
  • at least one processing chip such as a processing chip (201)
  • one or more antennas 208
  • 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).
  • the processor (202) may control the memory (204) and/or the transceiver (206), and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed herein.
  • 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).
  • 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.
  • 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.
  • the firmware and/or software code (205) may control the processor (202) to perform one or more protocols.
  • the firmware and/or software code (205) may control the processor (202) to perform one or more wireless interface protocol layers.
  • the processor (202) and the 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 coupled to the processor (202) to 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 section.
  • the second wireless device (200) may represent a communication modem/circuit/chip.
  • one or more protocol layers may be implemented by one or more processors (102, 202).
  • 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).
  • 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).
  • PHY physical
  • MAC Media Access Control
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • RRC Radio Resource Control
  • SDAP Service Data Adapt
  • 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, suggestions, 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, suggestions, methods and/or operational flowcharts disclosed herein.
  • signals e.g., baseband signals
  • 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.
  • one or more ASICs Application Specific Integrated Circuits
  • one or more DSPs Digital Signal Processors
  • one or more DSPDs Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGAs Field Programmable Gate Arrays
  • 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 comprised of random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), erasable programmable ROM (EPROM), flash memory, volatile memory, nonvolatile memory, hard drives, registers, cache memory, computer readable storage media, and/or combinations thereof.
  • the one or more memories (104, 204) may be located internally and/or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.
  • One or more transceivers (106, 206) can transmit user data, control information, wireless signals/channels, etc., referred to in the descriptions, functions, procedures, suggestions, 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, suggestions, methods, and/or flowcharts disclosed herein from one or more other devices.
  • one or more transceivers (106, 206) can be coupled to one or more processors (102, 202) and can transmit and receive wireless signals.
  • 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.
  • 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). As used herein, one or more antennas (108, 208) may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).
  • One or more transceivers (106, 206) may convert received user data, control information, wireless signals/channels, etc. from RF band signals to baseband signals for processing 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).
  • one or more transceivers (106, 206) may include an (analog) oscillator and/or a filter.
  • 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).
  • 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).
  • 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 wired or wireless connections.
  • a UE can operate as a transmitter in the uplink and as a receiver in the downlink.
  • a base station can operate as a receiver in the UL and as a transmitter in the DL.
  • the first wireless device (100) operates as a UE
  • the second wireless device (200) operates as a base station.
  • a processor (102) connected to, mounted on, or released in the first wireless device (100) can be configured to perform UE operations according to an implementation of the present disclosure or to control a transceiver (106) to perform UE operations according to an implementation of the present disclosure.
  • 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 an implementation of the present disclosure or to control a transceiver (206) to perform base station operations according to an implementation of the present disclosure.
  • a base station may be referred to as a Node B, an eNode B (eNB), or a gNB.
  • eNB eNode B
  • gNB gNode B
  • Figure 3 shows an example of a UE to which the implementation of this specification is applied.
  • the UE (100) can correspond to the first wireless device (100) of FIG. 2.
  • 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).
  • a processor 102
  • memory 104
  • a transceiver 106
  • one or more antennas 108
  • a power management module 141
  • a battery 142
  • a display a keypad
  • SIM Subscriber Identification Module
  • the processor (102) may be configured to implement the descriptions, functions, procedures, suggestions, 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, suggestions, 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 chipset, logic circuitry 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).
  • processors (102) can be found in the SNAPDRAGON TM series processors made by Qualcomm®, the EXYNOS TM series processors made by Samsung®, the A series processors made by Apple®, the HELIO TM series processors made by MediaTek®, the ATOM TM series processors made by Intel®, or their corresponding next-generation processors.
  • Memory (104) is operatively coupled with processor (102) and stores various information for operating processor (102).
  • Memory (104) may include ROM, RAM, flash memory, memory card, storage media, and/or other storage devices.
  • modules e.g., procedures, functions, etc.
  • the modules may be stored in memory (104) and executed by processor (102).
  • Memory (104) may be implemented within processor (102) or external to processor (102), in which case it may be communicatively coupled with processor (102) via various methods known in the art.
  • a transceiver (106) is operatively coupled to the processor (102) and transmits and/or receives wireless signals.
  • the transceiver (106) includes a transmitter and a receiver.
  • the transceiver (106) may include baseband circuitry for processing radio frequency signals.
  • the transceiver (106) controls one or more antennas (108) to transmit and/or receive wireless signals.
  • 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).
  • the display (143) outputs the result 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).
  • SIM card (145) is an integrated circuit for securely storing an International Mobile Subscriber Identity (IMSI) and associated keys, and is used to identify and authenticate subscribers in mobile phone devices such as mobile phones and computers. Contact information can also be stored on many SIM cards.
  • IMSI International Mobile Subscriber Identity
  • 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).
  • Figure 4 shows an example of a 5G system structure to which the implementation of this specification is applied.
  • the 5G system (5GS; 5G system) structure consists of the following network functions (NF; Network Function).
  • Data Network for example operator services, Internet access or third-party services.
  • Figure 4 illustrates the 5G system architecture for a non-roaming case using a reference point representation that shows how various network functions interact with each other.
  • the 5G system architecture includes the following benchmarks:
  • two NFs may need to be interconnected to serve a UE.
  • FIGS 5 and 6 illustrate examples of PDU session establishment procedures to which the implementation of this specification applies.
  • Establishing a PDU session can involve:
  • a PDU session may be associated with (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.
  • MA multi-access
  • Figures 5 and 6 specify the procedure for establishing a PDU session associated with a single connection type at a given time.
  • Step 1 To establish a new PDU session, the UE generates a new PDU session ID.
  • the UE initiates the PDU session establishment procedure requested by the UE by transmitting an NAS message containing a PDU Session Establishment Request message within an N1 SM container.
  • the PDU Session Establishment Request message includes a PDU session ID, a Requested PDU Session Type, a requested session and service continuity (SSC) mode, 5G SM capabilities, Protocol Configuration Options (PCO), an SM PDU DN Request Container, and a UE Integrity Protection Maximum Data Rate.
  • 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".
  • the Request Type is "Existing Emergency PDU Session".
  • the UE includes the S-NSSAI from the allowed NSSAI of the current connection type. If the Mapping Of Allowed NSSAI is provided to the UE, the UE provides both the S-NSSAI of the VPLMN (visited VPLMN) from the allowed NSSAI and the corresponding S-NSSAI of the HPLMN from the Mapping Of Allowed NSSAI.
  • 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.
  • AMF selects an SMF and stores the association of the new PDU session ID, S-NSAI(s), and the selected SMF ID.
  • AMF selects an SMF based on the SMF-ID received from the UDM. AMF updates the stored connection type for the PDU session.
  • the PDU session establishment procedure may be performed in the following cases:
  • AMF rejects the PDU session establishment request with an appropriate rejection cause.
  • AMF rejects requests from emergency-registered UEs whose request type does not indicate "Emergency Request” or "Existing Emergency PDU Session".
  • Step 3 If 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"), AMF calls the Create SM Context request procedure (e.g., Nsmf_PDUSession_CreateSMContext Request). If 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"), AMF calls the Update SM Context request procedure (e.g., Nsmf_PDUSession_UpdateSMContext Request).
  • the Create SM Context request procedure e.g., Nsmf_PDUSession_CreateSMContext Request.
  • the AMF forwards the S-NSSAI of the serving PLMN to the SMF from the allowed NSSAI.
  • the AMF also forwards the corresponding S-NSSAI of the HPLMN to the SMF from the mapping of the allowed NSSAI.
  • the AMF ID is the GUAMI of the UE, 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 generic public subscription identifier (GPSI) is included if available to the AMF.
  • the AMF provides PEI instead of SUPI. If a UE in restricted 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 SUPI for the UE or if the AMF indicates that the SUPI is not authenticated, the UE is considered not authenticated.
  • AMF can include PCF ID in Nsmf_PDUSession_CreateSMContext. This PCFID identifies H-PCF (home PCF) in non-roaming case and V-PCF (visited PCF) in LBO roaming case.
  • Step 4 If the session management subscription data for the S-NSSAI of the corresponding SUPI, DNN, and 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.
  • 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.
  • a create SM context response message e.g., Nsmf_PDUSession_CreateSMContext Response
  • an update SM context response message e.g., Nsmf_PDUSession_UpdateSMContext Response
  • 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.
  • the SMF rejects the UE request via NAS SM signaling including the relevant SM rejection cause by responding to the AMF with 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 and the PDU session establishment procedure is aborted.
  • Step 6 Optional secondary authentication/authorization may be performed.
  • Step 7a When dynamic policy and charging control (PCC) is used for a PDU session, the SMF can perform PCF selection.
  • PCC dynamic policy and charging control
  • Step 7b SMF performs the SM policy association establishment procedure to establish a SM policy association with the PCF and obtain the default PCC rules for the PDU session.
  • Step 8 SMF selects one or more UPFs.
  • Step 9 The SMF may perform the SM policy association modification procedure initiated by the SMF to provide information about the satisfied policy control request trigger conditions.
  • 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.
  • step 10a SMF can send N4 session establishment/modification request to UPF and provide packet detection, enforcement and reporting rules to be installed in UPF for PDU session.
  • step 10b UPF can confirm by sending N4 session establishment/modification response.
  • Step 11 SMF sends an N1N2 Message Transfer message (e.g. Namf_Communication_N1N2 Message Transfer) to AMF.
  • N1N2 Message Transfer message e.g. Namf_Communication_N1N2 Message Transfer
  • the N1N2 Message Forwarding message may contain N2 SM information.
  • the N2 SM information carries the following information that the AMF is to forward to the (R)AN:
  • QFI QoS flow ID
  • QoS quality of service
  • - PDU Session ID Indicates to the UE the association between RAN resources and a PDU session for the UE;
  • - S-NSSAI with value for the serving PLMN (i.e. HPLMN S-NSSAI, or VPLMN S-NSSAI in case of LBO roaming);
  • the N1N2 Message Transfer message may contain an N1 SM container.
  • the N1 SM container contains a PDU Session Establishment Accept message that the AMF will provide to the UE.
  • the PDU Session Establishment Accept message contains an S-NSSAI from the allowed NSSAIs.
  • the PDU Session Establishment Accept message contains an S-NSSAI from the allowed NSSAIs for the VPLMN and also contains the corresponding S-NSSAI of the HPLMN from the mapping of the allowed NSSAIs received by the SMF in step 3.
  • QoS rules, QoS flow levels, and QoS parameters, if required, for QoS flows associated with QoS rules and QoS profiles can be included in the PDU session establishment accept message and N2 SM information within the N1 SM container.
  • the N1N2 message transfer message contains an N1 SM container containing a PDU session establishment rejection message, and 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.
  • 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.
  • Step 13 (R)AN may perform AN specific signaling exchange with the UE related to the information received from the SMF.
  • the UE may perform 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.
  • (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 addition related to the received N2 command.
  • steps 14-16b and step 17 below are omitted.
  • 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.
  • 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.
  • Step S16a SMF initiates the N4 session modification procedure with UPF.
  • SMF provides AN tunnel information and corresponding forwarding rules to UPF.
  • Step S16b UPF provides an N4 session modification response to SMF.
  • the UPF can forward any DL packets that may have been buffered for this PDU session to the UE.
  • Step 16c If the SMF is not already registered for this PDU session, the SMF may register with the UDM for the given PDU session.
  • Step 17 SMF sends an update SM context response message (e.g., Nsmf_PDUSession_UpdateSMContext Response) to AMF.
  • update SM context response message e.g., Nsmf_PDUSession_UpdateSMContext Response
  • AMF forwards the relevant events to which SMF subscribes.
  • 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.
  • Step 19 For PDU session type IPv6 or IPv4v6, SMF may generate and send an IPv6 Router Advertisement to the UE.
  • Step 20 SMF can perform SM policy association modification initiated by SMF.
  • Step 21 If the PDU session establishment fails after step 4, the SMF may unsubscribe for modification of session management subscription data if the SMF no longer processes the UE's PDU session.
  • 3GPP has been describing in its standard specifications the solutions agreed upon for various key issues for Edge Computing support in 5GS.
  • Key Issue #1 the support method was reviewed with the following Objective to support the procedure for finding an Edge Application Server of a terminal through a 5G core network.
  • a single application service can be provided by multiple edge application servers, typically deployed at different sites. These multiple edge application server instances hosting the same content or service can use a single IP address (anycast address) or different IP addresses.
  • IP address anycast address
  • a new edge application server can be used to replace the old server to serve the application/UE.
  • the re-election of an edge application server can be triggered by events occurring at the 5GS or application layer. For example, in the first case, it can be triggered by a network-initiated user plane change, such as a mobility event (e.g., handover), or a failure event that ultimately triggers a 5GS. In the second case, it can be triggered by an edge application server becoming congested or unavailable. This requirement depends on whether the application can tolerate changes in application server instances.
  • EAS discovery procedure that supports the conventional DNS mechanism through 5GC during the EAS (Edge Application Server) search process of the terminal were agreed upon. Accordingly, a new NF (Network Function), Edge Application Server Discovery Function (EASDF), was introduced. 5GC can control the DNS procedure with the terminal through EASDF. In addition, 5GC can forward the DNS query message transmitted from the terminal through EASDF to the local DNS server, so that the local DNS server can resolve this message.
  • NF Network Function
  • EASDF Edge Application Server Discovery Function
  • search or navigation may both mean Discovery.
  • EAS distribution information can be applied to all PDU sessions with a specific DNN, S-NSSAI, and/or a specific internal group identifier.
  • - SMF may provide a BaselineDNS Pattern (BaselineDNSPattern) to EASDF.
  • the BaselineDNS Pattern is derived from the EAS distribution information provided by AF and is not dedicated to a particular PDU session; SMF configures EASDF with the BaselineDNS Pattern according to the procedure defined in clause 6.2.3.4 of TS 23.548 V18.3.0.
  • the baseline DNS message detection template ID can be used to reference the baseline DNS message detection template in EASDF and derive an array of FQDN ranges and/or an array of EAS IP address ranges.
  • the baseline DNS processing job ID can be used to reference baseline DNS processing job information in EASDF and derive job-related parameters.
  • the baseline DNS message detection template ID and baseline DNS processing task ID must be unique per SMF set if the SMF set controls the EASDF, and must be unique per SMF within the EASDF baseline otherwise.
  • a BaselineDNSPattern may contain one or more entries, each of which is a baseline DNS message detection template or baseline DNS handling task information. Each BaselineDNSPattern entry may be updated or deleted using the baseline DNS message detection template ID or baseline DNS handling task ID to identify the updated or deleted entry.
  • DNS message type DNS query: - Array of (FQDN ranges).
  • DNS Message Type DNS Response: - Array of FQDN ranges and/or array of EAS IP address ranges.
  • Baseline DNS handling actions information - Baseline DNS handling actions ID: (ECS option, local DNS server IP address)
  • the SMF may obtain the EAS distribution information from the NEF if the EAS distribution information is not yet available (e.g. by joining the NEF with respect to that information as described in clause 6.2.3.4.3 of TS 23.548 V18.3.0). If the EAS distribution information is preset for the SMF, the SMF may select the EASDF and provide its address to the UE as the DNS server to be used for the PDU session.
  • SMF configures EASDF with DNS message processing rules to process DNS messages related to UE.
  • DNS message processing rules have a unique identifier and contain information used for DNS message detection and related actions.
  • DNS processing rules are defined as follows:
  • Baseline DNS message detection template ID and/or DNS message detection template contains one or more of the following):
  • DNS message type is DNS Query: an array of source IP addresses (i.e., UE IP addresses). (FQDN ranges) (optional).
  • DNS message type is DNS response: an array of FQDN ranges and/or an array of EAS IP address ranges (optional).
  • DNS message content is reported to SMF (e.g. target FQDN and, if available: IP address information provided back by the DNS server). This reporting action may include the reporting-once flag. If included, EASDF reports DNS message content to SMF only once, when the DNS message detection template matches the first incoming DNS query or DNS response message.
  • A. Contains information to build an optional EDNS Client Subnet Option to be included in DNS messages, or used to replace an EDNS Client Subnet Option received in a DNS query message from the UE. (Information for EASDF to build the EDNS Client Subnet Option is included in the DNS processing rules, or the baseline DNS processing task ID serves as a reference to the baseline DNS processing task information.) This corresponds to Option A, defined below.
  • Option B Information about the DNS message destination address is included in the DNS processing rule as a DNS server address, or the baseline DNS processing task ID included in the DNS processing rule may refer to the DNS message destination address information.
  • EASDF shall forward the DNS message to the locally pre-configured default DNS server/resolver. This corresponds to Option B defined below.
  • EASDF is configured by SMF not to forward DNS queries to a DNS server, but instead generates responses based on the EAS IP address provided by SMF.
  • EASDF Constructs a DNS response from a DNS query based on the indicated IP address (e.g., a generic EAS).
  • EASDF is expected to process the constructed response in the same way as a response received from a remote DNS server.
  • EASDF When EASDF forwards DNS messages (to a DNS server via UE or N6), EASDF uses its own address as the source address of the DNS message. When EASDF forwards DNS messages to UE, it replaces the received EDNS Client Subnet option with the option provided by UE (i.e. if provided by UE) or removes all received EDNS Client Subnets, depending on the configuration.
  • SMF can use the following information to create rules for processing DNS messages associated with a PDU session:
  • PDU session information such as PDU session L-PSA and ULCL/BP;
  • the FQDN in the DNS query may match the FQDN provided by SMF in the DNS message detection template, as per SMF's guidance.
  • one of the following options is executed by EASDF according to the corresponding DNS message processing rules:
  • EASDF includes or replaces the EDNS Client Subnet (ECS) option in the DNS Query message as defined in RFC 7871 and sends the DNS Query message to a DNS server to resolve the FQDN.
  • the DNS server can resolve the EAS IP address by considering the EDNS Client Subnet option and send the DNS response to EASDF;
  • EASDF sends a DNS query message to a local DNS server responsible for resolving the FQDN within the L-DN.
  • EASDF receives a DNS response message from the local DNS server.
  • An instruction from SMF for a matching FQDN may also direct EASDF to contact SMF.
  • SMF then provides DNS message processing rules to EASDF;
  • the EASDF may forward the DNS query to a preset DNS server/resolver for DNS resolution;
  • EASDF When EASDF receives DNS response message, EASDF notifies EAS information (i.e. EAS IP address, corresponding IP address in ECS DNS option) to SMF if DNS message reporting condition provided by SMF is met (i.e. EAS IP address or FQDN is within IP/FQDN range). Then SMF can select target DNAI based on EAS information and trigger UL CL/BP and L-PSA insertion as specified in clause 6.3.3 of TS 23.501 V18.0.0 according to the notification.
  • EAS information i.e. EAS IP address, corresponding IP address in ECS DNS option
  • SMF can select target DNAI based on EAS information and trigger UL CL/BP and L-PSA insertion as specified in clause 6.3.3 of TS 23.501 V18.0.0 according to the notification.
  • SMF can now decide to have DNS messages for FQDNs handled by the local DNS resolver/server.
  • the SMF may send reporting-once control information (i.e., a DNS message processing rule having a DNS message detection template that includes EAS IP address ranges with report-once indication set) to EASDF to instruct EASDF to report only for DNS messages corresponding to the reporting-once control information of the DNS message detection template.
  • reporting-once control information i.e., a DNS message processing rule having a DNS message detection template that includes EAS IP address ranges with report-once indication set
  • the SMF may instruct EASDF not to report DNS responses corresponding to some FQDN ranges and/or EAS IP address ranges to SMF while there is a setting for EASDF to report DNS responses after UL CL/BP and L-PSA are inserted for that EAS IP address range for a pre-configured session breakout (e.g., when UL CL/BP and L-PSA are inserted for that EAS IP address range for a pre-configured session breakout). After removing or changing the L-PSA, the SMF can instruct the EASDF to resume reporting DNS messages.
  • SMF may decide that the interaction between EASDF and DNS server of DN should be done through UPF based on local configuration.
  • SMF sends corresponding N4 rule to this UPF to instruct this UPF to forward DNS messages between EASDF and external DNS server.
  • DNS messages between EASDF and DNS server described in this section are transparently forwarded through this UPF.
  • FIG. 7a and FIG. 7b are examples of an EAS search procedure based on EASDF according to one embodiment of the disclosure of the present specification.
  • the UE transmits a PDU Session Establishment Request to the SMF as shown in step 1 of Figures 5 and 6.
  • the SMF retrieves the UE subscription information from the UDM (optionally including a UE authorization indication for EAS discovery via EASDF) and checks whether the UE is authorized to discover EAS via EASDF. If not authorized, this procedure is terminated and subsequent steps are skipped.
  • SMF selects EASDF as described in section 6.3 of TS 23.501 V18.0.0.
  • SMF may select EASDF as DNS server for PDU session based on UE subscription information.
  • the SMF may indicate to the UE that use of the EDC capability is allowed for a PDU session, or may indicate to the UE that use of the EDC capability is required for a PDU session.
  • SMF determines that interaction between EASDF and DNS servers of a DN should be via PSA UPF based on local configuration, SMF configures PSA UPF within N4 rule to forward DNS messages between EASDF and DN.
  • Neasdf_DNSContext_Create request including UE IP address, SUPI, DNN, notification endpoint, (DNS message processing rule)).
  • This step is performed before step 11 of the PDU session establishment procedure of FIGS. 5 and 6.
  • EASDF creates a DNS context for the PDU session and stores the UE IP address, SUPI, notification endpoint, and potentially provided DNS message processing rules in the context.
  • DNS message processing rules are provided to EASDF before a DNS query message is received by EASDF or as a result of a DNS query report.
  • EASDF calls the service operation Neasdf_DNSContext_Create in response.
  • the SMF includes the IP address of the EASDF as the DNS server/resolver for the UE in the PDU Session Setup Accept message as defined in step 11 of section 4.3.2.2.1 of TS 23.502 V18.0.0.
  • the UE configures the EASDF as the DNS server for that PDU session.
  • the SMF responds to the UE via a DHCP response with the allocated UE IP address and/or a DNS server address containing the IP address of the EASDF.
  • SMF can call Neasdf_DNSContext_Update request (with EASDF context ID, (DNS message processing rules)) to EASDF.
  • Update can be triggered by UE mobility, e.g. when UE moves to a new location, or by EASDF reporting of DNS queries with specific FQDN. Update can also be triggered by insertion/removal of local PSA, e.g. update of rules for processing DNS messages from UE, or new PCC rule information.
  • EASDF responds with a Neasdf_DNSContext_Update response.
  • the application on the UE uses the EDC function to send a DNS query to the EASDF.
  • the UE sends a DNS query message to the EASDF.
  • EASDF sends a DNS message report to SMF by calling Neasdf_DNSContext_Notify request (with information about the DNS query, e.g., the target FQDN of the DNS query).
  • EASDF may add a DNS message identifier to Neasdf_DNSContext_Notify.
  • the DNS message identifier uniquely identifies the reported DNS message and is used to associate the corresponding DNS message processing rule included in the Neasdf_DNSContext_Update request with the identified DNS message.
  • the DNS message identifier is generated by EASDF.
  • the DNS message processing rules for the received FQDN may need to be updated (e.g., to provide information updates to build/replace EDNS Client Subnet Options information).
  • the SMF calls a Neasdf_DNSContext_Update request (DNS Message Processing Rules) to the EASDF. If the EASDF provided a DNS message identifier, the SMF adds this DNS message identifier to the corresponding DNS message processing rules included in the Neasdf_DNSContext_Update. If the EASDF did not provide a DNS message identifier, the SMF can use the DNS message type (request) and the target FQDN to uniquely identify the DNS message.
  • the DNS processing rule will contain the corresponding IP address to be used to build/replace the EDNS Client Subnet option.
  • the DNS processing rule will contain the corresponding local DNS server IP address. Additionally, the DNS processing rule can also simply instruct EASDF to forward DNS queries to a pre-configured DNS server/resolver.
  • EASDF applies the DNS message processing rules only to that DNS message. EASDF responds with a Neasdf_DNSContext_Update response.
  • EASDF processes the DNS query message received from the UE as follows:
  • EASDF adds/replaces the EDNS Client Subnet option to the DNS Query message as specified in RFC 7871 and sends it to the C-DNS server;
  • EASDF receives the EDNS Client Subnet option in a DNS query, it removes it and forwards the DNS query message to the local DNS server.
  • EASDF can simply forward the DNS query to a pre-configured DNS server/resolver.
  • EASDF receives a DNS response containing the EAS IP address determined by the DNS system and verifies whether the DNS response can be forwarded to the UE.
  • EASDF sends a DNS message report to SMF by calling Neasdf_DNSContext_Notify request with EAS information. If EASDF receives multiple EAS IP addresses from the DNS server it contacts, the DNS message report may contain multiple EAS IP addresses. The DNS message report may contain the FQDN and EDNS Client Subnet option received in the DNS response message. EASDF may also add a DNS message identifier to the report. The DNS message identifier uniquely identifies the reported DNS response, and EASDF may associate the corresponding DNS message processing rule included in the Neasdf_DNSContext_Update request with the identified DNS response. The DNS message identifier is generated by EASDF.
  • EASDF may wait for an SMF command (step 17) without sending a DNS response message to the UE (i.e., buffering the DNS response message).
  • EASDF reports to SMF only once by calling Neasdf_DNSContext_Notify request for DNS responses matching the DNS message detection template.
  • SMF calls the Neasdf_DNSContext_Notify response service operation.
  • SMF can perform UL CL/BP and local PSA selection and insert UL CL/BP and local PSA.
  • SMF can determine DNAI.
  • SMF can determine related N6 traffic routing information for DNAI according to N6 traffic routing information for DNAI included in EAS deployment information, and set local PSA UPF with forwarding action derived from N6 traffic routing information.
  • SMF can perform UL CL/BP and local PSA selection and insertion as described in TS 23.502 V18.0.0.
  • traffic detection rules and traffic routing rules are determined by SMF according to IP address range per DNAI included in EAS deployment information or PCC rules received from PCF or pre-configured information.
  • SMF calls Neasdf_DNSContext_Update request (DNS message processing rule). If EASDF provided DNS message identifier, SMF adds this identifier to the corresponding DNS message processing rule included in Neasdf_DNSContext_Update Request. If EASDF did not provide DNS message identifier, SMF can use DNS message type (response) and FQDN to uniquely identify DNS response message.
  • a DNS message processing rule with a control action of "forward buffered DNS response message to UE" instructs EASDF to forward the buffered DNS response to UE in step 14.
  • Other DNS message processing rules may instruct EASDF not to send any more DNS response messages corresponding to the FQDN range and/or EAS IP address range.
  • EASDF applies DNS message processing rules only to the corresponding DNS response. EASDF responds with Neasdf_DNSContext_Update response.
  • EASDF forwards the DNS response to the UE as described above and processes the EDNS Client Subnet option.
  • SMF calls the Neasdf_DNSContext_Delete service to remove the DNS context.
  • the DNS query is routed to the local DNS resolver/server corresponding to the DNAI to which the L-PSA is associated.
  • the SMF selects the local DNS server address based on the DNAI corresponding to the inserted local PSA, the local configuration, and the EAS distribution information of the AF request as specified in TS23.548 V18.3.0 Section 6.2.3.4.2.
  • a UL CL/BP and a local PSA are inserted, one of the following options may apply (either during or after PDU session establishment):
  • SMF configures the local DNS server as the new DNS server for the UE.
  • SMF may indicate to the UE that the use of EDC feature is allowed for the PDU session or that the use of EDC feature is required for the PDU session.
  • SMF configures traffic routing rules in the UL CL (e.g. containing the local DNS server address) or BP (e.g. new IP prefix @ local PSA) to route traffic containing DNS query messages destined for L-DN to L-PSA.
  • the L-DNS server communicates with other DNS servers to resolve DNS queries locally or recursively.
  • SMF is configured to allow DNS queries for FQDN (range) queries to be routed locally on the UL CL, subsequent DNS queries for the FQDN (range) will be routed locally to the local DNS server.
  • FIG. 8 illustrates an example of an EAS discovery procedure based on a local DNS server/resolver according to one embodiment of the disclosure of the present specification.
  • Figure 8 is an example of EAS discovery with Local DNS server/resolver.
  • the UE sends a PDU Session Establishment Request to the SMF as shown in step 1 of Figures 5 and 6.
  • the SMF retrieves the UE subscription information from the UDM (optionally including an indication of UE authorization for EAS discovery via EASDF) and checks whether the UE is authorized to discover EAS via EASDF. If not authorized, the EASDF-related tasks in this procedure are skipped.
  • SMF inserts UL CL/BP and local PSA.
  • the insertion of UL CL/BP/Local PSA can be triggered by DNS messages as described in TS 23.548 V18.0.0 section 6.2.3.2.2.
  • the SMF can pre-configure the UL CL/BP and Local PSA before the UE sends the DNS Query message (e.g. when the UE is moving).
  • the SMF includes the IP address of the local DNS server in the PDU Session Setup Acknowledge message as per step 11 of section 4.3.2.2.1 of TS 23.502 V18.0.0 or the network-initiated PDU session modification procedure.
  • the UE configures the local DNS server as the DNS server for that PDU session.
  • SMF sets the UL CL/BP for DNS query processing:
  • steps 2 and 3 are performed:
  • the SMF sends a PDU session modification command (local DNS server address) to the UE.
  • the SMF sends a PDU Session Modification Command (Local DNS Server Address) to the UE.
  • PDU Session Modification Command (Local DNS Server Address)
  • the UE responds with a PDU Session Modification Command Ack.
  • the UE sets the local DNS server as the DNS server for the PDU session.
  • the UE sends the following DNS queries to the designated local DNS server.
  • SMF can remove the DNS context of EASDF by calling the Neasdf_DNSContext_Delete service.
  • the application in the UE sends a DNS query to the DNS resolver/DNS server specified by the SMF in step 0 using the EDC functionality as described in TS 23.548 V18.0.0 section 6.2.4.
  • the UE sends the DNS query message.
  • the UE selects the source IP prefix according to the IPv6 multihoming routing rules provided by the SMF.
  • the DNS query message is forwarded to the local DNS server and processed as described below:
  • the target address of the DNS query is the IP address of the local DNS server.
  • the DNS query is forwarded to the local DNS server by the UL CL/BP and the local PSA.
  • the local DNS server resolves the FQDN of the DNS query by itself or communicates with other DNS servers to recursively resolve the EAS IP address.
  • the local PSA forwards DNS traffic to a local DNS server that either resolves the FQDN target of the DNS query on its own or communicates with a C-DNS server to recursively resolve the EAS IP address.
  • the local PSA receives a DNS response message from the local DNS server and forwards it to the UL CL/BP, and the UL CL/BP forwards the DNS response message to the UE.
  • SMF decides to remove the UL CL/BP and Local PSA as defined in clause 4.3.5.5 of TS 23.502 V18.0.0, e.g., due to UE mobility, the SMF sends a PDU Session Modification Command to configure the new address of the DNS server on UE (e.g. to set it to the address of EASDF).
  • the SMF decides to remove the UL CL/BP and local PSA as defined in clause 4.3.5.5 of TS 23.502 V18.0.0, the SMF sends a PDU Session Modification command to set the new address of the DNS server in the UE (e.g. to the address of the EASDF).
  • 5GC can support EAS discovery procedure.
  • 5GC can select EASDF or local DNS server/resolver for DNS query message transmitted by terminal and resolve the message based on controllable form.
  • 5GC can provide EAS IP address to terminal.
  • Edge relocation/EAS rediscovery procedure is supported for changing EAS providing service to terminal according to request from AF or decision of 5GC (especially SMF).
  • the SMF can determine the DNS server to be provided to the terminal.
  • the DNS server address information can be the address of a local DNS server located close to the terminal or the address of the EASDF.
  • the SMF can determine the DNS server based on the EDI (EAS Deployment Information) provided from the AF or the local configuration.
  • EDI EAS Deployment Information
  • EDI information provided by AF may include information such as DNN, S-NSSAI, FQDN(s), DNAI(s), DNS Server Information, and EAS IP address range Information.
  • EDI information is stored in UDR through NEF, and this information can be referenced by SMF. Also, the information may be preconfigured in SMF. SMF can perform EASDF selection and DNS message handing rule generation based on EDI information.
  • EASDF can receive DNS message handling rules from SMF.
  • EASDF can report to SMF about reception of DNS query from terminal or DNS response message from DNS server/resolver based on DNS message handling rules.
  • SMF can update DNS message handling rules for EASDF based on reported information.
  • SMF In the conventional EAS discovery support technology through EASDF, SMF only refers to static information in EDI provided from AF. SMF has a problem of setting DNS message handling rules and supporting terminal DNS procedures based only on static information.
  • SMF and EASDF can provide edge computing services to terminals.
  • SMF and/or EASDF receive EAS Deployment Information (EDI) from AF.
  • EDI EAS Deployment Information
  • the conventional EDI contains only static information. This causes a problem in that the network cannot utilize EAS load information that changes in real time. In addition, even if the network utilizes EAS load information that changes in real time, there is a problem in that SMF must manage this information, which causes signaling overhead.
  • AF provides EAS Deployment Information (EDI) to SMF/EASDF.
  • EDI EAS Deployment Information
  • SMF and/or EASDF can support edge computing services to terminals based only on static information in EDI.
  • 5GC Due to the nature of edge computing applications, in order to provide optimal EAS information to terminals, 5GC needs a way to receive dynamically changing information, such as EAS load status. In addition, 5GC needs a way to support EAS discovery of new terminals and Edge relocation procedures of existing terminals based on dynamically changing information, such as EAS load status.
  • the method of providing 5GC with and managing each dynamically updated EAS load information through control plane signaling has the problem of causing signaling overhead. Therefore, a more efficient method is needed for 5GC to receive the corresponding information.
  • 5GC can support EAS discovery of new terminals and Edge relocation procedures of existing terminals based on dynamically changing information.
  • the method by which 5GC receives and manages each EAS load information that is dynamically updated through control plane signaling may cause signaling overhead. Therefore, a more efficient method for 5GC to receive the corresponding information is needed.
  • the disclosure of this specification proposes an operation for supporting EAS discovery and Edge relocation for a terminal receiving the Edge computing service. For example, when an AF transmits information related to a change in a specific EAS overload situation to a local EASDF, the local EASDF can track/update this information and request/perform Edge relocation to the SMF.
  • AF can provide EAS overload situation change information to 5GC.
  • the existing Naf_EventExposure_Subscribe service operation can be extended.
  • 5GC especially EASDF
  • AF can receive notification of EAS overload situation through NEF.
  • AF can include overload threshold in the service.
  • 5GC can receive notification from AF again.
  • 5GC can receive notification about occurrence and release of overload situation for a specific EAS. Based on the notification, 5GC can request Edge relocation to be determined/performed for terminals receiving service from the corresponding EAS. In addition, the corresponding information can be referenced/considered in the EAS discovery process of a new terminal.
  • the EASDF may then receive notification from the AF that the EAS overload condition has been lifted.
  • the EASDF may request a DNS message handling rule update so that the corresponding EAS information can be provided to the terminal again.
  • the EASDF can receive a notification from the AF about the occurrence and release of an overload situation of the EAS upon the request of the EASDF.
  • the EASDF can request an Edge relocation decision and EAS (re)discovery based on the notification.
  • the disclosure of this specification describes a method for supporting such operations.
  • UE User Equipment
  • terminal may be used as terms having the same meaning.
  • 5GC can obtain EAS overload related information from AF.
  • the AF can provide information related to changes in the overload status for each EAS providing Edge computing services to the terminal to 5GC (particularly EASDF). Based on the information, 5GC can support Edge relocation decisions of the terminal and EAS (re)discovery procedures, etc.
  • 5GC (especially EASDF) can obtain EAS overload status change information from AF.
  • EAS overload information can be obtained by following the Data Collection from AF procedure.
  • the conventional technology supports a Data Collection procedure in which NWDAF receives specific Event and related information from AF.
  • the corresponding service procedure is described in sections 6.2.2.2 and 6.2.2.3 of the TS 23.288 V18.0.0 standard.
  • NWDAF can subscribe to specific Events directly from AF or through NEF.
  • the Nnef_EventExposure_Subscribe service operation and the Naf_EventExposure_Subscribe service operation of the prior art may include the following information. For example, Event ID(s) identifying a specific event defined in 5GC, Type information for Event Parameters, Event Filter Information specifying Value(s), and Event Reporting Information related to Event reporting settings may be included.
  • the AF may send a notification including information about a specific Event for the subscription.
  • Event Filter Information and Event Reporting Information are extended to enable EASDF to perform the above service operations and service procedures.
  • application-specific data information (including AF identifier) that can be provided from AF can be provisioned from O&M to NEF.
  • EASDF can subscribe to AF that serves terminals managed by EASDF.
  • EASDF can subscribe to AF through NEF for EAS overload situation change information.
  • EASDF can perform NEF discovery and selection process through NRF.
  • EASDF can query by sending message including AF identifier.
  • EASDF can receive corresponding AF identifier from SMF based on information in EDI during DNS context generation process.
  • EASDF can subscribe to EAS overload situation change information to AF within the EAS discovery procedure of the terminal.
  • EASDF can obtain overload situation information for a specific EAS from AF.
  • the AF can provide IP address information and overload indication of the corresponding EAS. This operation can be utilized for the purpose of preventing a new terminal from connecting to an EAS in an overload situation based on an AF request.
  • the AF may include/store the corresponding information (e.g., information about a specific EAS in Overload state) in the Traffic Influence information in the UDR via the NEF.
  • the information about a specific EAS in Overload state may be identified by an IP address.
  • the information about a specific EAS in Overload state may be the IP address(es) of the EAS(s) in Overload state.
  • the PCF may forward the PCC rule including the corresponding information received from the AF to the serving SMFs of the PDU Session associated with the DNN/S-NSSAI in the AF request.
  • the serving SMF of the PDU Session may provide the corresponding information to the EASDF when selecting the EASDF and creating the DNS context in the EAS discovery procedure of the terminal.
  • the AF may operate in a manner of releasing the previously provided overload indication including the corresponding EAS address. For example, depending on whether specific EAS(s) are overloaded, the AF may transmit an overload indication (e.g., Set to 'true') together with the IP address identifying the EASs in the overload situation.
  • the NEF may store and manage the IP addresses of the EASs in the overload situation in the UDR. The overload situation may be resolved in a specific EAS. In this case, the AF may transmit the overload indication set to 'false' together with the IP address of the corresponding EAS. Then, the NEF may exclude the corresponding EAS from the EASs in the overload situation in the UDR.
  • a second example of the disclosure of this specification describes an example of how EASDF utilizes EAS overload status change information.
  • EASDF can obtain EAS overload situation change information based on the procedure described in the first example of the disclosure of this specification.
  • EASDF can support Edge computing of UE based on the obtained EAS overload situation change information.
  • Determining/requesting/performing Edge relocation and EAS (re)discovery procedures of the UE may be supported based on a combination of one or more of the following actions/configurations/steps:
  • Conventional Edge relocation decisions can be performed upon request from the AF or based on the mobility of the UE in the 5GC (especially the SMF).
  • the AF can provide information related to the overload/congestion situation of a specific EAS and information such as DNN/S-NSSAI associated therewith to the EASDF.
  • EASDF may be aware of overload/congestion situation of a specific EAS.
  • EASDF may inform one or more SMFs controlling EASDF about information related to overload/congestion situation of a specific EAS.
  • EASDF may request SMF to perform Edge relocation for terminals using the corresponding EAS.
  • the SMF may decide and/or perform Edge relocation. Depending on the Edge relocation decision/performance, the SMF may transmit an EAS rediscovery indication to the terminal through the PDU Session Modification procedure. The terminal may refresh stale EAS information and perform the EAS (re)discovery procedure to acquire the EAS IP address again.
  • the terminal internally stores the address information of the Application Server through the DNS procedure for connection to the Application Server. Therefore, the terminal can attempt to connect to the Application Server using the internally stored server address without performing the DNS procedure to find the Server each time.
  • the PDU Session Modification procedure may be performed according to the Edge relocation decision of the SMF.
  • the SMF may transmit a PDU Session Modification Command message to the terminal.
  • the message may include DNAI information in the [impact field] field together with the EAS re-discovery indication.
  • the message may include the EAS re-discovery indication and the [impact field] field may be empty.
  • the terminal can recognize the information of the Application Servers included/corresponding to the DNAI as stale information.
  • the terminal can erase the address information of the Application Servers that were stored and perform the DNS procedure to find a new server.
  • the terminal can clear the addresses of all internally stored application servers and, if necessary, perform a new DNS procedure to obtain the server address.
  • the EASDF can support the EAS discovery procedure of the terminal considering the load situation of the Server.
  • the EAS overload situation change information can be overload information for a specific EAS provided by the AF, and can also be load information for each EAS according to the subscription of 5GC (particularly, SMF).
  • the dynamic load information of the Application Server was not considered in the EAS discovery procedure.
  • the terminal may become a target of Edge relocation to find another EAS.
  • the EAS address information of the overload situation may be provided to the terminal in the EAS discovery procedure of a new terminal.
  • the method by which EASDF supports EAS discovery based on EAS load/overload situation information can be supported based on EAS information provided through the DNS procedure of the terminal.
  • the DNS response received from the DNS server/resolver can include multiple EAS IP addresses.
  • the SMF can modify/reassemble the corresponding contents (e.g., EAS information) based on the EAS load/overload information.
  • the above EAS information modification/recombination method can be performed by pre-filtering specific EAS IP address information according to EAS overload information.
  • the EAS information modification/recombination method can be performed through priority change/recombination considering the EAS load situation.
  • a DNS response including modified/recombined EAS information based on EAS load/overload can be transmitted to the terminal. Accordingly, selection of the optimal EAS can be supported. In addition, signaling and Edge relocation procedures for resolving overload situations from AF to 5GC can be reduced.
  • FIGS. 9a and 9b The disclosure of this specification describes an example of EAS re-discovery based on EAS overload information of EASDF.
  • FIGS. 9a and 9b The examples of FIGS. 9a and 9b include an example of EAS re-discovery due to EAS overload procedure.
  • FIGS. 9A and 9B illustrate examples of an EAS re-search procedure according to one embodiment of the disclosure of the present specification.
  • Figures 9a and 9b illustrate an example of an EAS rescan procedure due to EAS overload.
  • steps 1a to 1c may refer to operations according to prior art.
  • NEF may send a request message related to NF management (e.g., Nnrf_NFManagement_NFUpdate_request) to NRF.
  • NF management e.g., Nnrf_NFManagement_NFUpdate_request
  • NRF can store the NF profile.
  • NRF may send a response message related to NF management (e.g., Nnrf_NFManagement_NFUpdate_response) to NEF.
  • NF management e.g., Nnrf_NFManagement_NFUpdate_response
  • registration with NEF can be performed for information that AF can provide.
  • the registration information of the NEF i.e. NEF profile
  • Information that the AF can provide may include information that the AF can notify the EAS of a congestion situation.
  • step 2 the UE and the SMF may perform a PDU session establishment procedure.
  • the PDU session establishment procedure according to the examples of FIGS. 5 and 6 may be performed.
  • step 3 SMF can select EASDF.
  • SMF can send a request message related to DNS context creation (e.g., Neasdf_DNSContext_Create Request) to EASDF.
  • EASDF can send a response message related to DNS context creation (e.g., Neasdf_DNSContext_Create Response) to SMF.
  • a DNS Context may be created.
  • the SMF may obtain EAS Deployment Information from the AF through UDR or NEF.
  • the SMF may also set the AF ID included in the EAS Deployment Information in the DNS Context.
  • EASDF may send a request message (e.g., Nnrf_NFDiscovery_Request_request) related to a discovery request to NRF.
  • a request message e.g., Nnrf_NFDiscovery_Request_request
  • NRF may send a response message (e.g., Nnrf_NFDiscovery_Request_response) related to the discovery request to EASDF.
  • a response message e.g., Nnrf_NFDiscovery_Request_response
  • EASDF can query NRF for information available from AFs.
  • EASDF can obtain available data and NEF information that can be provided for each AF.
  • EASDF can also obtain NEF information that can provide EAS overload situation information among AFs being serviced by terminals by using AF ID information in DNS Context.
  • EASDF can search for information that can be provided from each AF by using AF IDs stored in DNS context as identifiers.
  • AFs deployed in the network there may be AFs that support the function of providing EAS overload situation information through NEF and AFs that do not support such function.
  • EASDF needs to know AFs and NEFs that support this function.
  • EASDF cannot search whether all AFs in the network support the function.
  • EASDF can find AFs that can provide EAS overload situation information among serving AFs of a terminal by using AF IDs (e.g., serving AFs) stored in DNS context.
  • AF IDs e.g., serving AFs
  • EASDF can send messages related to event subscription or event unsubscription (e.g., Nnef_EventExposure_Subscribe/ Nnef_EventExposure_Unsubscribe) to NEF.
  • event subscription or event unsubscription e.g., Nnef_EventExposure_Subscribe/ Nnef_EventExposure_Unsubscribe
  • NEF can forward the message transmitted by EASDF to AF.
  • EASDF can subscribe/unsubscribe to EAS overload situation information from AF through NEF.
  • EASDF can subscribe/unsubscribe to events related to EAS overload situation information.
  • EASDF can subscribe/unsubscribe to EAS overload situation information from AF via SMF and NEF.
  • EASDF subscribes/unsubscribes via SMF and NEF
  • EASDF can subscribe/unsubscribe without directly knowing the AF ID.
  • the EASDF can also receive notifications of EAS overload situation information directly from the AF.
  • the AF may send a notification message (e.g., Naf_EventExposure_Notify) related to the event to the NEF.
  • the notification message may include the target UE identifier, EAS IP address, and an overload indication.
  • NEF may send a notification message (e.g., Nnef_EventExposure_Notify) sent by AF to EASDF.
  • the notification message may include target UE identifier, EAS IP address, and overload indication.
  • the AF can provide address information (e.g., EAS IP address) for the EAS in an overload situation and address information of terminals receiving service from the EAS (e.g., target UE identifier) to the EASDF through the NEF.
  • address information e.g., EAS IP address
  • address information of terminals receiving service from the EAS e.g., target UE identifier
  • the notification sent by AF may contain information about the terminals that require EAS rediscovery.
  • the notification message may contain a list of specific terminals (e.g. terminal IP addresses), a number of terminals that must be reduced to resolve congestion, information indicating that no more terminals can be serviced, etc.
  • EASDF may send a request message related to DNS context notification to SMF.
  • the EASDF can determine which terminals require EAS rediscovery based on the information received in step 8.
  • the EASDF can identify the terminals connected to the EAS in overload situation and the serving SMFs of the corresponding terminals.
  • the EASDF can request EAS re-discovery by transmitting a request message including terminal information and DNN/S-NSSAI information to the SMF.
  • the EASDF can also know the EAS address currently being used by a specific terminal based on the DNS response that the EASDF responds to the terminal. Based on this EAS address, the EASDF can also generate a list of terminals that directly use the EAS that is in overload situation.
  • the EASDF may receive information from the AF indicating that it can no longer service the terminal. In this case, the EASDF may transmit the information that the AF cannot service the terminal to the SMF along with the EAS address information. The SMF may, based on this information, determine not to use the EAS address any more when performing EAS discovery for other terminals.
  • the SMF may send a PDU Session Modification Command message to the UE.
  • the PDU Session Modification Command message may include an EAS rescan indication and/or an impact field.
  • the EAS rescan indication may be information related to EAS rescan.
  • the UE may send a PDU Session Modification Command ack message to the SMF.
  • an EAS re-discovery procedure may be performed.
  • steps 7 to 19 of the EAS re-discovery procedure according to section 6.2.3.2.2 of TS23.548 V17.6.0 may be performed.
  • the SMF may perform EAS re-discovery of the terminal according to a request from the EASDF in Step 9.
  • the SMF may transmit a PDU Session Modification Command including an EAS re-discovery indication to the terminal.
  • the terminal may perform a DNS procedure for DNS cache refresh and finding a new EAS.
  • EAS information provided to the terminal during the DNS procedure may include EAS information in an overload situation.
  • the EASDF may decide/perform deletion or priority adjustment of the corresponding record by itself according to local configuration or according to a DNS message handling rule update from the SMF.
  • the terminal may receive EAS information from a DNS server.
  • the EAS information may include multiple application server address information, and each address information may be referred to as a record. Therefore, deleting/prioritizing the record may mean excluding a specific application server address or adjusting the order of the record according to the priority.
  • the terminal receives a DNS response message including multiple server address records, the terminal attempts to connect sequentially from the top server address.
  • EASDF manages EAS overload status information within EASDF, and EAS overload status can also be referenced in the EAS discovery procedure of a new terminal.
  • 5GC can receive EAS-specific load information or overload situation change for a specific EAS from AF. Based on the information related to the overload situation change, 5GC can support Edge relocation decision/request of a terminal and EAS re-discovery.
  • the following description may be applied to a method of receiving EAS load/overload information from AF and a method of requesting Edge relocation of a terminal to SMF. For example, these operations may be performed based on an extended service operation of a conventional service operation, a new service operation, or a conventional service procedure or a new service procedure.
  • conventional parameters may be reused or new indications or parameters may be generated and transmitted.
  • the third example of the disclosure of this specification describes an example of a procedure based on the various examples of the disclosure of this specification described above.
  • FIG. 10 illustrates an example of operations according to one embodiment of the disclosure of the present specification.
  • FIG. 10 The operations illustrated in FIG. 10 are merely examples, and the scope of the disclosure of this specification is not limited to the operations illustrated in FIG. 10.
  • EASDF may receive a DNS context creation request message from SMF.
  • EASDF may send a DNS context creation response message to SMF.
  • the DNS context creation response message may include received EAS deployment information provided by the AF.
  • EASDF can send an NF discovery request message to NRF.
  • an NF search request message may include information querying what information the AF can provide.
  • the NRF may transmit an NF discovery response message to the EASDF.
  • an NF search response message may include data that the AF can provide and information related to one or more NEFs associated with the AF.
  • the EASDF may store information in the NEF that can provide EAS overload situation information to the AF based on the NF search response message received.
  • EASDF may send an event subscription message to NEF requesting notification regarding an EAS overload situation.
  • the event notification message may be received based on the fact that the event subscription message was sent.
  • the AF can transmit an event notification message to the EASDF.
  • an event notification message may include burrow information, address information of an overloaded EAS, and information related to a UE requiring EAS rescan.
  • EASDF may determine edge relocation for the UE. For example, based on the edge relocation being determined, EASDF may transmit a request message of step (S1004).
  • EASDF may identify the SMF serving the UE.
  • EASDF can send a request message to SMF.
  • the EASDF may send a request message requesting EAS re-discovery to the SMF serving the UE based on an event notification message.
  • the request message can be used by the SMF to send a PDU Session Modification Command message to the UE for EAS re-discovery.
  • the request message may include EAS address information and information that the service is unavailable.
  • the request message may further include one or more UE information and DNN, S-NSSAI information that require EAS re-discovery.
  • the SMF may transmit a PDU session modification command message to the UE.
  • the PDU Session Modification Command message can be used by the UE to perform DNS cache refresh operation and DNS procedures to discover a new EAS.
  • the SMF may receive a PDU session modification ack message from the UE.
  • the operations proposed in the disclosure of this specification can be performed by EASDF.
  • EADSF can perform the operations proposed in the disclosure of this specification for a terminal receiving Edge computing service through 5GC.
  • AF can provide information on overload/congestion situation of EAS and information on target using the EAS.
  • EASDF can subscribe to EAS overload/congestion situation information from AF.
  • EASDF can receive information related to the corresponding event through NEF.
  • EASDF can query NRF for information provided by AF.
  • EASDF can perform NEF discovery and selection process for AFs that can provide EAS overload/congestion information among AFs that serve terminals managed by EASDF.
  • EASDF can receive EAS overload/congestion information from AFs through NEF.
  • SMF can provide AF identifier information required during the NEF discovery and selection process to EASDF during the DNS context creation process.
  • EASDF can subscribe/unsubscribe to AF via the above NEF for EAS overload/congestion information.
  • EASDF can subscribe/unsubscribe to AF via SMF and NEF for EAS overload/congestion information.
  • AF can transmit notification information about subscription of EASDF.
  • Notification information can include EAS address information in overload/congestion situation, address information of terminal using the EAS, information indicating that terminal can no longer be serviced, etc.
  • the EAS overload/congestion related information can be stored and updated within the EASDF.
  • EASDF can identify SMFs serving the terminals using the corresponding EAS.
  • EASDF can identify the EAS address currently in use by a specific terminal, and based on the EAS address, it can also create/manage a list of terminals that directly use the EAS that has experienced overload.
  • EASDF can decide/request edge relocation of a terminal based on EAS overload/congestion situation information.
  • EASDF can decide/request edge relocation for terminals receiving services from that EAS.
  • the EASDF can receive EAS overload/congestion situation information from the AF according to the first example of the disclosure of this specification. Based on the EAS overload/congestion situation information, the EASDF can determine which terminals require EAS rediscovery.
  • EASDF can identify terminals connected to EAS and their serving SMFs that are in overload/congestion condition.
  • EASF can request EAS re-discovery to the corresponding SMFs. This decision can be made based on local configuration or permission/request from AF.
  • the EASDF can update the EAS information to be provided to the terminal.
  • EASDF can support EAS (re-)discovery procedure of terminals based on EAS overload/congestion related information.
  • EASDF can know EAS address information in an overload situation.
  • a record in EAS information received by DNS operation in the EAS re-discovery procedure of a terminal according to the Edge relocation of the second example of the disclosure of this specification or in the EAS discovery procedure of a new terminal can be updated.
  • EASDF when EASDF performs record update in EAS information to be provided to the terminal, EASDF can perform the following actions.
  • EASDF can delete EAS information in an overload situation from the record, or change the priority between records.
  • the EASDF may receive information from the AF in the first example of the disclosure of this specification indicating that a particular EAS can no longer serve terminals. In this case, the EASDF may inform the SMF of the corresponding EAS address information.
  • the SMF may receive from the EASDF information about EAS addresses that can no longer serve terminals. Based on this information, the SMF may also prevent the terminal from being connected to the corresponding EAS in the new terminal EAS discovery procedure.
  • the service experience of the terminal can be improved.
  • the signaling overhead for handling overload situations can be reduced.
  • the EAS relocation procedure can be performed efficiently.
  • Edge computing service through 5GC can be effectively supported.
  • the load/overload situation change information of Edge Application Server can directly affect Edge computing service through 5GC.
  • the load/overload situation change information of Edge Application Server can be referenced/managed in EASDF.
  • the core network including EASDF can determine Edge relocation of terminal and support EAS re-discovery procedure.
  • signaling overhead can be reduced.
  • information on overload/congestion situation can be efficiently received rather than dynamically changing EAS-specific load.
  • terminals can be prevented from being connected to EAS in overload situation, and requests and procedures for performing edge relocation of terminals from conventional AF can be reduced by performing relocation.
  • EAS overload/congestion related information can also be provided by policies/decisions within the AF.
  • EAS overload/congestion related information can be received based on subscription from 5GC (particularly EASDF).
  • information on overload/congestion situation can be efficiently received, and signaling overhead can be reduced.
  • load information within a server is generally expressed as a percentage, and can change very quickly. If an update message is received every time the load information that changes very quickly is changed, there is a problem that the signaling overhead is large.
  • overload situation status information rather than load information that changes rapidly, can be received based on policies and/or decisions of the AF/application layer. This can prevent the problem of wasted signaling.
  • EASDF can manage/reference information related to EAS overload/congestion.
  • EASDF can determine/request EAS discovery procedure of terminal based on EAS load/overload situation.
  • EASDF can determine/request Edge relocation for terminal that is provided with existing Edge computing service. Through this, connection of terminal to EAS in overload situation can be prevented in conventional EAS discovery procedure. Accordingly, requests and procedures for performing Edge relocation of terminal from AF can be reduced.
  • the local EASDF can effectively determine and support information management and service procedures.
  • the operation of the terminal may be implemented by the devices of FIGS. 1 to 3 described above.
  • the terminal may be the first device (100) or the second device (200) of FIG. 2.
  • 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).
  • One or more processors (102 or 202) may control one or more memories (104 or 204) and one or more transceivers (105 or 206), and execute instructions/programs stored in one or more memories (104 or 204) to perform operations of a terminal (e.g., UE) as described in the disclosure of this specification.
  • a terminal e.g., UE
  • commands for performing the operations of the terminal described in the disclosure of this specification may be stored in a nonvolatile computer-readable storage medium having the commands recorded therein.
  • the storage medium may be included in one or more memories (104 or 204).
  • 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.
  • a network node e.g., AMF, PCF, SMF, UPF, UDM, NEF, AF, NRF, UPF UL CL/BP, UPF L-PSA, UPF PSA, EASDF, DNS server, local DNS resolver, local DNS server, C-DNS, etc.
  • a base station e.g., NG-RAN, gNB, RAN, (R)AN, etc.
  • the network node or the base station may be the first device (100) or the second device (200) of FIG. 2.
  • 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 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 (106 or 206), and execute instructions/programs stored in one or more memories (104 or 204) to perform the operation of the network node or base station described in the disclosure of this specification.
  • the instructions for performing the operations of the network node or base station described in the disclosure of the present specification may be stored in a non-volatile (or non-transitory) computer-readable storage medium having the instructions recorded therein.
  • the storage medium may be included in one or more memories (104 or 204).
  • 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 the present specification.
  • the methods are described based on the flow chart as a series of steps or blocks, but 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 flow chart are not exclusive, and other steps may be included or one or more of the steps in the flow chart may be deleted without affecting the scope of the rights.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention divulgue un procédé. Le procédé peut comprendre les étapes consistant à : transmettre, à une NRF, un message de demande de découverte de NF comprenant des informations pour interroger des informations pouvant être fournies par une AF ; recevoir un message de réponse de découverte de NF en provenance de la NRF ; recevoir un message de notification d'événement provenant d'une NEF ; et transmettre un message de demande demandant une redécouverte d'EAS à une SMF desservant un UE.
PCT/KR2024/014486 2023-09-27 2024-09-25 Support informatique en périphérie Pending WO2025071196A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363540675P 2023-09-27 2023-09-27
US63/540,675 2023-09-27

Publications (1)

Publication Number Publication Date
WO2025071196A1 true WO2025071196A1 (fr) 2025-04-03

Family

ID=95201623

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2024/014486 Pending WO2025071196A1 (fr) 2023-09-27 2024-09-25 Support informatique en périphérie

Country Status (1)

Country Link
WO (1) WO2025071196A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022036102A1 (fr) * 2020-08-12 2022-02-17 Idac Holdings, Inc. Relocalisation de serveur d'application périphérique
KR20220118273A (ko) * 2021-02-18 2022-08-25 삼성전자주식회사 에지 어플리케이션 서버 디스커버리 방법 및 장치

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022036102A1 (fr) * 2020-08-12 2022-02-17 Idac Holdings, Inc. Relocalisation de serveur d'application périphérique
KR20220118273A (ko) * 2021-02-18 2022-08-25 삼성전자주식회사 에지 어플리케이션 서버 디스커버리 방법 및 장치

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 5G System Enhancements for Edge Computing; Stage 2 (Release 18)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.548, no. V18.3.0, 19 September 2023 (2023-09-19), pages 1 - 87, XP052512121 *
ANONYMOUS: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 18)", 3GPP STANDARD; 3GPP TS 23.501, vol. SA WG2, no. V18.3.0, 19 September 2023 (2023-09-19), pages 1 - 696, XP052512111 *
HUAWEI, HISILICON: "Edge service continuity procedure", 3GPP DRAFT; S6-201139, vol. SA WG6, 15 July 2020 (2020-07-15), pages 1 - 3, XP051908906 *

Similar Documents

Publication Publication Date Title
WO2022215909A1 (fr) Procédé de gestion de sessions pdu
WO2019190166A1 (fr) Procédé, équipement utilisateur et nœud de réseau pour mise en œuvre d'une procédure d'établissement de session de pdu pour ladn
WO2022211519A1 (fr) Procédé de mesure de performance pour qos
WO2021029512A1 (fr) Communication liée à une modification de serveur d'application
WO2019194633A1 (fr) Dispositif et procédé de gestion de politique d'un équipement utilisateur dans un système de communication sans fil
WO2024210592A1 (fr) Communication basée sur une tranche de réseau
WO2023172094A1 (fr) Communication associée à des informations d'analyse
WO2023182728A1 (fr) Procédé d'enregistrement de réseau pour transmission de trafic et dispositif prenant en charge celui-ci
WO2024147621A1 (fr) Communication basée sur un calcul de périphérie
WO2025071196A1 (fr) Support informatique en périphérie
WO2025037917A1 (fr) Sélection de réseau pour services localisés
WO2024186077A1 (fr) Tranche de réseau
WO2026089434A1 (fr) Communication associée à un dns
WO2024162818A1 (fr) Commutation de trajet
WO2024215120A2 (fr) Commande de station de base mobile
WO2025174150A1 (fr) Tranche de réseau
WO2024085512A1 (fr) Autorisation directe c2
WO2024025276A1 (fr) Communication relative à une session d'unité de données de protocole (pdu) redondante
WO2025121717A1 (fr) Gestion de station de base mobile
WO2024025332A1 (fr) Communication relative à une session pdu redondante
WO2025155049A1 (fr) Service de localisation
WO2025150874A1 (fr) Service sms en fonction d'un changement d'utilisateur
WO2025170221A1 (fr) Communication basée sur une station de base mobile
WO2025216515A1 (fr) Itinérance en cas de catastrophe
WO2025033836A1 (fr) Communication associée à une demande d'af

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24872904

Country of ref document: EP

Kind code of ref document: A1