WO2025005683A1 - Procédé et appareil pour la relocalisation d'un contexte d'application dans un réseau de données périphérique - Google Patents

Procédé et appareil pour la relocalisation d'un contexte d'application dans un réseau de données périphérique Download PDF

Info

Publication number
WO2025005683A1
WO2025005683A1 PCT/KR2024/008970 KR2024008970W WO2025005683A1 WO 2025005683 A1 WO2025005683 A1 WO 2025005683A1 KR 2024008970 W KR2024008970 W KR 2024008970W WO 2025005683 A1 WO2025005683 A1 WO 2025005683A1
Authority
WO
WIPO (PCT)
Prior art keywords
eas
acr
ees
ues
list
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.)
Ceased
Application number
PCT/KR2024/008970
Other languages
English (en)
Inventor
Sapan Pramodkumar SHAH
Basavaraj Jayawant Pattan
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.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
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 Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Priority to KR1020257043367A priority Critical patent/KR20260029295A/ko
Publication of WO2025005683A1 publication Critical patent/WO2025005683A1/fr
Anticipated expiration legal-status Critical
Ceased 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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • 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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the 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/14—Session management
    • H04L67/148—Migration or transfer of sessions
    • 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/30—Profiles
    • H04L67/306—User profiles
    • 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/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]

Definitions

  • the present disclosure relates to wireless communication, more particularly, to performing application context relocation (ACR) in an edge data network (EDN).
  • ACR application context relocation
  • EDN edge data network
  • 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz.
  • 6G mobile communication technologies referred to as Beyond 5G systems
  • terahertz bands for example, 95GHz to 3THz bands
  • IIoT Industrial Internet of Things
  • IAB Integrated Access and Backhaul
  • DAPS Dual Active Protocol Stack
  • 5G baseline architecture for example, service based architecture or service based interface
  • NFV Network Functions Virtualization
  • SDN Software-Defined Networking
  • MEC Mobile Edge Computing
  • multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.
  • FD-MIMO Full Dimensional MIMO
  • OAM Organic Angular Momentum
  • RIS Reconfigurable Intelligent Surface
  • an Edge Enabler Layer exposes Application Programming Interfaces (APIs) to support capabilities like service provisioning, registration, application server discovery, capability exposure to an Application Server (AS) and support for service continuity.
  • APIs Application Programming Interfaces
  • AS Application Server
  • ACs Application Clients
  • EEDN Edge Data Network
  • the EAS serves the UE in specific service area.
  • the EAS serves the UE based on UE's location. So, either when the UE moves from one location to a new location or when the EAS is overloaded or unable to serve to the UE as per required Key Performance Indicators (KPIs), the EAS which is connected to the AC in the UE needs to be replaced with another EAS depending on service area, to provide better service experience to the user and the UE.
  • KPIs Key Performance Indicators
  • the EEL provides service continuity feature for minimizing the application layer service interruption.
  • the service continuity feature is supported by defining information elements and procedures for Application Context Relocation (ACR) procedures.
  • ACR Application Context Relocation
  • the ACR procedures enable transfer of Edge Enabler Client (EEC) context from one Edge Enabler Server (EES) (i.e. a source EES or S-EEC) to another EES (Target EES (T-EES)).
  • EAS Edge Enabler Server
  • S-EEAS The EAS with which the AC is connected to and receiving service in UE's current location is called as the source EAS (S-EAS).
  • S-EAS The EAS with which the AC will be connected to receive service in UE's new location is called the target EAS
  • S-EES The EES with which the EEC and S-EAS are registered is called as the source EES (S-EES).
  • S-EES source EES
  • T-EES The EES with which the T-EAS is registered and EEC will be registered in order to receive service, is called as the target EES (T-EES).
  • Conventional methods and systems include enhanced an architecture for enabling edge applications to discover common EAS.
  • This feature to discover common EAS enables the participants of the same application specific group to discover same common EAS where all participants within the EDN can connect.
  • the discovery of common EAS ensures all participants of the group, connects to same application server and thus receives same service and KPIs and no other participant can get unfair advantage by connecting to different EAS.
  • the EES announces the common EAS for specific application group to all other EESs which supports such application group.
  • the common EAS which serves multiple UEs who are part of the same application group, may be overloaded. It is predicted (based on statistical data by an Application Data Analytics Enablement (ADAE) server or any other mechanism) that the common EAS will not be able to provide required service to the UEs in the near future. In such cases, for all the UEs served by the common EAS, the ACR needs to be performed in order to minimize service interruption for all the UEs when common EAS is overloaded or unable to provide required services to the UE(s). The ACR procedure needs to be performed for all UEs such that all UEs remains connected to same common EAS after the service continuity. In conventional methods, the solution for service continuity for common EAS is not specified yet and so it is required to provide solution for such scenarios.
  • ADAE Application Data Analytics Enablement
  • the principal object of the embodiments herein is to provide service continuity procedure for bulk of UE for a common EAS.
  • Another object of the embodiments herein is to provide performing ACR in order to minimize service interruption for all UEs when common EAS is overloaded or unable to provide required services to the UE.
  • a method for application context relocation (ACR) by a source-edge application server (S-EAS) in an edge data network (EDN) is provided.
  • the method may comprise determining to perform the ACR based on key performance indicators (KPIs) being not met; and transmitting, to a source-edge enabler server (S-EES), a request for the ACR including a list of user equipments (UEs) for the ACR.
  • KPIs key performance indicators
  • S-EES source-edge enabler server
  • a method for application context relocation (ACR) by a source-edge enabler server (S-EES) in an edge data network (EDN) is provided.
  • the method may comprise determining to perform the ACR for a source-edge application server (S-EAS); identifying a list of user equipments (UEs) of an application group connected to the S-EAS; and transmitting, to the S-EAS, an ACR management notification to start application context transfer (ACT) between the S-EAS and a target-EAS (T-EAS), wherein the ACR management notification includes a list of UEs for the ACT.
  • S-EAS source-edge application server
  • UEs user equipments
  • T-EAS target-EAS
  • a source-edge application server (S-EAS) for application context relocation (ACR) in an edge data network (EDN) is provided.
  • the S-EAS may comprise a transceiver; and at least one processor coupled to the transceiver.
  • the at least one processor may be configured to determine to perform the ACR based on key performance indicators (KPIs) being not met, and transmit, to a source-edge enabler server (S-EES), a request for the ACR including a list of user equipments (UEs) for the ACR.
  • KPIs key performance indicators
  • S-EES source-edge enabler server
  • FIG. 1A and FIG. 1B are flow charts illustrating service continuity procedure for bulk of UE for common EAS, according to the embodiment as disclosed herein.
  • FIG. 2 shows various hardware components of an EES, according to the embodiments as disclosed herein.
  • circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.
  • circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block.
  • a processor e.g., one or more programmed microprocessors and associated circuitry
  • Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure.
  • the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.
  • Embodiments disclosed herein provides a system and method for performing service continuity procedure for bulk of UE for common EAS.
  • the present method includes upon receiving an EAS information from an EEC, an EES stores the information about application group ID or application group profile in EEC context or service session context which is part of EEC context.
  • the EES performs an ACR for all the UEs which are part of same application group or at least one AC of the UE is connected to the same EAS.
  • the EES identifies the T-EAS and T-EES for all the EECs or for all AC-EAS sessions.
  • the proposed method includes, the EES sends the EEC context of the EECs of all the UEs and AC-EAS sessions to a T-EES.
  • the S-EES sends an ACR management notification to the S-EAS to start Application Context Transfer (ACT).
  • ACT Application Context Transfer
  • both S-EAS and T-EAS sends an ACT completion notification to the S-EES and T-EES respectively.
  • the EES sends an ACR complete notification to the EECs of all the UEs which are part of same application group or at least one AC of the UE is connected to the same EAS.
  • the EEC is registered with EES #A.
  • EES#A receives an EAS discovery message from the EEC for application group ID and when the common EAS for the application group ID is already available then, the EES #A provides the EAS ID for common EAS along with EES endpoint (of EES #B) details where the common EAS is registered.
  • the proposed method can be used to perform the ACR in order to minimize service interruption for all UEs when the common EAS is overloaded or unable to provide required services to the UE. Without the proposed method, the ACR procedure for service continuity will be performed one by one for all UEs connected to common EAS, thus, some of the UEs may get unfair advantage by connected to superior EAS (having higher compute capabilities). The proposed method ensures that all UEs connected to common EAS still remains connected to single/common EAS even after the service continuity procedure.
  • FIGS. 1A and 2 where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.
  • FIG. 1A and FIG. 1B are flow charts (S100) illustrating service continuity procedure for bulk of UE for common EAS, according to the embodiment as disclosed herein.
  • EES #B is referred as EES or S-EES and common EAS is referred as EAS or S-EAS.
  • EES information provisioning request includes the common EAS, application group ID or application group profile and UE identifier.
  • the EES stores the information about application group ID or application group profile in EEC context or service session context which is part of EEC context.
  • the EES receives application group ID or application group profile information in EEC registration or EAS discovery or any other message from EEC to EES.
  • the S-EES either detects itself that the S-EAS will not be able to meet the required KPIs in the near future, or the S-EAS indicates to the S-EES in a request message that the S-EAS will not be able to meet the KPIs in future.
  • the indication from the S-EAS can be application group ID or the group profile or the list of UEs which are currently served by the common EAS or any other information elements (IE) or flag.
  • the S-EAS can also detect by itself that the S-EAS will not be able to meet the required KPIs in the future.
  • the S-EAS initiates ACR launching procedure with the ACR determination to indicate the S-EES that the S-EAS will not be able to meet the KPIs in future.
  • the S-EAS sends selected T-EAS declaration message to indicate the S-EES that the S-EAS will not be able to meet the KPIs in future.
  • the indication from the S-EAS can be application group ID or the group profile or the list of UEs which are currently served by the common EAS or any other information elements (IE) or flag.
  • IE information elements
  • the S-EES or the S-EAS determines that the S-EAS will not be able to meet the KPIs in future based on analytics data received from Application Data Analytics Enablement (ADAE) service.
  • Application service provider ASP
  • ASP Application service provider
  • S-EAS can provide T-EAS to the S-EES in the request message.
  • the S-EES determines to initiate ACR for the S-EAS which is a common EAS for an application group.
  • the S-EES identifies list of all UE(s) such that the UE is part of application group and at least one AC of that UE is connected to the S-EAS based on the stored information.
  • the S-EAS provides list of all UE(s), which are part of the application group and at least one AC of that UE is connected to the EAS, in the ACR launching procedure or in the selected T-EAS declaration message or in the EAS discovery procedure.
  • the S-EES identifies the T-EAS and T-EES only once using Discover T-EAS and retrieve T-EES procedures, and the same T-EAS is used to transfer application context for all the AC(s) that means the EES identifies the T-EAS and T-EES using Discover T-EAS and retrieve T-EES procedures for all the EECs or for all AC-EAS sessions.
  • the S-EES determines all the EECs whose context needs to be transferred to the T-EES. Application context for AC in these UE(s) will be transferred to the T-EAS.
  • the S-EES sends the EEC context(s) of the EECs of the all identified UE(s) and AC-EAS session(s), the application group id or application group profile to the T-EES.
  • the EEC context includes application group id or application group profile, selected ACR scenarios, etc.
  • the S-EES sends target EAS information in ACR information notification to all the EEC(s) identified for the ACR procedure associated with the application group ID or application group profile and whose EEC context is transferred to the T-EES.
  • the notification message includes an indication to the EEC indicating that the T-EAS is a common EAS for the application group ID or application group profile.
  • the S-EES sends the ACR management notification to S-EAS to start Application Context Transfer (ACT).
  • the notification includes indication to start ACT for all application contexts of all ACs for the identified UE(s) which are member of the provided application group Id and application group profile.
  • the notification message to the S-EAS includes list of all UE(s) which are part of the application group and at least one AC of that UE is connected to the EAS.
  • both S-EAS and T-EAS sends ACT status notification to the S-EES and the T-EES respectively.
  • the notification includes list of all UE identifiers or EEC IDs whose application context is successfully transferred.
  • the notification may also include application group Id and application group profile.
  • the notification includes list of all UE identifiers or EEC IDs whose application context is failed to transfer.
  • the S-EES sends ACR complete notification to all EEC(s) identified for the ACR procedure associated with the application group ID or application group profile and whose EEC context is transferred to the T-EES.
  • the service continuity procedure for bulk of UE for common EAS is applicable for the deployment with central repository or deployment without central repository.
  • FIG. 2 shows various hardware components of the EES (100), according to the embodiments as disclosed herein.
  • the EES (100) includes a processor (110), a communicator (120), a memory (130) and a service continuity procedure controller (140).
  • the processor (110) is coupled with the communicator (120), the memory (130) and the service continuity procedure controller (140).
  • the service continuity procedure controller (140) stores the information about at least one of: the application group ID, the application group profile in the EEC context, and the service session context, upon receiving the EAS information from the EEC.
  • the service session context is part of the EEC context.
  • the service continuity procedure controller (140) detects that the EAS does not able to meet required KPIs in a near future or the EAS indicates to the EES (100) in the request message that the EAS does not able to meet the KPI in future.
  • the request includes the list of UEs currently connecting with common EAS to take the service for which the ACR is required.
  • the service continuity procedure controller (140) determines to initiate ACR procedure for common EAS based on the detection.
  • the ACR for the common EAS is initiated by identifying the list of all UEs such that all UEs are part of the application group and at least one AC of that the at least one UE is connected to the EAS based on the stored information.
  • the service continuity procedure controller (140) identifies the T-EAS and the T-EES for all EECs or for all session between the AC and the EAS during the ACR procedure.
  • the T-EAS is used to transfer application context for all ACs.
  • the service continuity procedure controller (140) sends the at least one EEC context of the all EECs of all identified UEs or the AC-EAS session to the T-EES during an EEC context transfer based on the identification.
  • the service continuity procedure controller (140) sends the target EAS information in the ACR information notification to all EECs identified for the ACR procedure associated with the application group ID or the application group profile, when the EEC context is transferred to the T-EES. Further, the service continuity procedure controller (140) sends the ACR complete notification to all EECs identified for the ACR procedure associated with the application group ID or the application group profile based on the target EAS information.
  • the service continuity procedure controller (140) sends the ACR management notification to the S-EAS to start application context transfer. Further, the service continuity procedure controller (140) receives the ACT status notification from the S-EAS once the application context transfer is completed from the S-EAS to the T-EAS. Further, the service continuity procedure controller (140) sends the ACR complete notification to all EECs identified for the ACR procedure associated with the application group ID or the application group profile whose EEC context is transferred to the T-EES.
  • the service continuity procedure controller (140) is implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware.
  • the processor (110) may include one or a plurality of processors.
  • the one or the plurality of processors may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an AI-dedicated processor such as a neural processing unit (NPU).
  • the processor (110) may include multiple cores and is configured to execute the instructions stored in the memory (130).
  • the service continuity procedure controller (140) and the processor (110) may be integrally referred to as at least one processor.
  • the processor (110) is configured to execute instructions stored in the memory (130) and to perform various processes.
  • the communicator (120) is configured for communicating internally between internal hardware components and with external devices via one or more networks.
  • the memory (130) also stores instructions to be executed by the processor (110).
  • the memory (130) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.
  • EPROM electrically programmable memories
  • EEPROM electrically erasable and programmable
  • the memory (130) may, in some examples, be considered a non-transitory storage medium.
  • non-transitory may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted that the memory (130) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).
  • RAM Random Access Memory
  • the communicator (120) includes an electronic circuit specific to a standard that enables wired or wireless communication.
  • the communicator (120) is configured to communicate internally between internal hardware components of the user equipment (100) and with external devices via one or more networks.
  • the communicator (120) may be referred to as a transceiver.
  • FIG. 2 shows various hardware components of the EES (100) but it is to be understood that other embodiments are not limited thereon.
  • the EES (100) may include less or more number of components.
  • the labels or names of the components are used only for illustrative purpose and does not limit the scope of the invention.
  • One or more components can be combined together to perform same or substantially similar function in the EES (100).
  • An apparatus of an entity other than the EES (100) may include a processor, communicator, a memory and a service continuity procedure controller, described similarly as the EES (100) regarding FIG. 2.

Landscapes

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

Abstract

La divulgation concerne un système de communication 5G ou 6G permettant de prendre en charge un débit supérieur de transmission de données. Un procédé pour la relocalisation d'un contexte d'application (ACR) par un serveur d'application périphérique (S-EAS) dans un réseau de données périphérique (EDN) est proposé. Le procédé peut consister à déterminer l'exécution de l'ACR sur la base du fait que des indicateurs-clés de performance (KPI) ne sont pas satisfaits ; et à transmettre, à un serveur facilitateur périphérique source (S-EES), une demande pour l'ACR comprenant une liste d'équipements utilisateurs (UE) pour l'ACR.
PCT/KR2024/008970 2023-06-28 2024-06-27 Procédé et appareil pour la relocalisation d'un contexte d'application dans un réseau de données périphérique Ceased WO2025005683A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020257043367A KR20260029295A (ko) 2023-06-28 2024-06-27 엣지 데이터 네트워크에서 애플리케이션 컨텍스트 재배치 방법 및 장치

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202341043512 2023-06-28
IN202341043512 2024-05-21

Publications (1)

Publication Number Publication Date
WO2025005683A1 true WO2025005683A1 (fr) 2025-01-02

Family

ID=93940063

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2024/008970 Ceased WO2025005683A1 (fr) 2023-06-28 2024-06-27 Procédé et appareil pour la relocalisation d'un contexte d'application dans un réseau de données périphérique

Country Status (2)

Country Link
KR (1) KR20260029295A (fr)
WO (1) WO2025005683A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023003686A1 (fr) * 2021-07-21 2023-01-26 Intel Corporation Registre d'application d'informatique en périphérie multi-accès (mec) dans une fédération mec
US20230053805A1 (en) * 2020-01-03 2023-02-23 Samsung Electronics Co., Ltd. Method and apparatus for adjusting application context relocation in edge computing system
WO2023027477A1 (fr) * 2021-08-23 2023-03-02 Samsung Electronics Co., Ltd. Procédé et système de relocalisation de contexte d'application entre déploiements en périphérie et en nuage
WO2023039409A1 (fr) * 2021-09-07 2023-03-16 Convida Wireless, Llc Support de continuité bout à bout de service d'application en périphérie

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230053805A1 (en) * 2020-01-03 2023-02-23 Samsung Electronics Co., Ltd. Method and apparatus for adjusting application context relocation in edge computing system
WO2023003686A1 (fr) * 2021-07-21 2023-01-26 Intel Corporation Registre d'application d'informatique en périphérie multi-accès (mec) dans une fédération mec
WO2023027477A1 (fr) * 2021-08-23 2023-03-02 Samsung Electronics Co., Ltd. Procédé et système de relocalisation de contexte d'application entre déploiements en périphérie et en nuage
WO2023039409A1 (fr) * 2021-09-07 2023-03-16 Convida Wireless, Llc Support de continuité bout à bout de service d'application en périphérie

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhanced Architecture for enabling Edge Applications; (Release 18)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.700-98, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V18.1.0, 31 March 2023 (2023-03-31), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 248, XP052284169 *

Also Published As

Publication number Publication date
KR20260029295A (ko) 2026-03-04

Similar Documents

Publication Publication Date Title
WO2023146335A1 (fr) Procédé et dispositif de communication faisant appel à un service d'exposition d'événement d'upf pour un service de facturation dans un système de communication sans fil
US20240244507A1 (en) Network slice admission control based on availability of quota at nsacf apparatus in wireless network
WO2024210511A2 (fr) Gestion de procédure de désenregistrement dans un réseau sans fil
WO2023149732A1 (fr) Procédé et système de gestion de déploiement de tranches temporaires dans un protocole 3gpp
WO2023191420A1 (fr) Procédé et appareil pour une procédure de relocalisation de contexte d'application dans un réseau de données edge
WO2023136604A1 (fr) Procédé et réseau sans fil permettant de gérer des informations aériennes d'un contexte uuaa
WO2025005683A1 (fr) Procédé et appareil pour la relocalisation d'un contexte d'application dans un réseau de données périphérique
WO2023211071A1 (fr) Procédé et système de découverte de services d'application dans une fédération d'opérateurs dans un réseau sans fil
WO2023277469A1 (fr) Procédé et appareil de gestion de l'enregistrement d'un équipement utilisateur sur une tranche de réseau
WO2024237677A1 (fr) Procédé et appareil de communication entre un client d'application (ac) et un client d'activation de périphérie (eec) dans un système de communication sans fil
WO2025071162A1 (fr) Procédés et appareil pour le traitement de session(s) pdu associée(s) à une restriction de zone pour une tranche dans un système de communication sans fil
WO2024136401A1 (fr) Procédé et appareil de gestion d'accès à une tranche de réseau pour un équipement utilisateur dans un système de communication sans fil
WO2022197108A1 (fr) Procédé et système pour effectuer une procédure d'autorisation d'authentification spécifique de tranche de réseau pour une tranche de réseau
WO2023153806A1 (fr) Procédé et appareil pour déterminer un ue relais pour un ue contraint
WO2025071092A1 (fr) Procédé et appareil pour prendre en charge la mobilité d'un groupe de terminaux dans un système informatique en périphérie mobile
WO2024147722A1 (fr) Procédé de fourniture d'informations de service informatique périphérique par l'intermédiaire d'un système de communication sans fil
WO2024172624A1 (fr) Procédé de gestion d'accès à un réseau non public autonome (snpn) dans un équipement utilisateur et équipement utilisateur associé
US20240237145A1 (en) Handling ad hoc group call participation in mc network
WO2025037894A1 (fr) Procédé et appareil de fourniture de service de périphérie dans un système de communication sans fil
WO2024205295A1 (fr) Procédé et appareil pour bloquer des données de plan de gestion pour nssai et ns-aos partiellement autorisées dans un système de communication sans fil
WO2024205341A1 (fr) Systèmes et procédés pour mettre à jour le canal de notification actif dans un service de gestion de notification de couche d'architecture d'activateur de service (seal)
WO2025263953A1 (fr) Procédé et appareil pour prendre en charge un service de localisation pour de multiples équipements d'utilisateur partageant une même localisation dans un système de communication sans fil
WO2025071178A1 (fr) Procédé et appareil pour favoriser la découverte et la sélection de serveurs d'applications de périphérie dans un système informatique de périphérie mobile
WO2024196065A1 (fr) Procédés et appareil permettant de fournir une mobilité d'application dans des réseaux périphériques
WO2025005551A1 (fr) Procédé et appareil de gestion de session pdu en fonction d'une disponibilité d'emplacement de tranche dans un système de communication sans fil

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: 24832461

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE