IP Library › Granted Patent US 12,676,793
Granted Patent B2
US 12,676,793 · App. 18/787,545 · Granted Jul 7, 2026

Method and apparatus for edge enabler server lifecycle management

Inventors: Deepanshu Gautam (Bangalore, IN); Nishant Gupta (Bangalore, IN); Walter Featherstone (Middlesex, GB)
Assignee: Samsung Electronics Co., Ltd
H04L41/0806H04L41/0895H04W24/02
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,676,793
App. No.
18/787,545
Filed
Jul 29, 2024
Granted
Jul 7, 2026
Kind
B2
Art Unit
2451
USPC
709/222
Abstract

In embodiments of the present disclosure, a method by a first network node includes transmitting, to a second network node, a request for creating a managed object instance (MOI), the request including one or more requirements related to an edge enabler server (EES), and receiving, from the second network node, a response including information associated with the MOI for an EESfunction information object class (IOC) created based on the one or more requirements included in the request, wherein the created MOI includes one or more attributes indicated in the EESfunction IOC, and wherein the one or more attributes include an identifier of the EES, serving location information for the EES, and information indicating whether the EES supports service continuity.

Claims (20)

1 . A method by a first network node, the method comprising:

transmitting, to a second network node, a request for creating a managed object instance (MOI), the request including one or more requirements related to an edge enabler server (EES); and

receiving, from the second network node, a response including information associated with the MOI for an EESfunction information object class (IOC) created based on the one or more requirements included in the request,

wherein the created MOI contains one or more attributes as defined in the EESfunction IOC, and

wherein the one or more attributes include an identifier of the EES, serving location information for the EES, and information indicating whether the EES supports service continuity.

2 . The method of claim 1 ,

wherein the one or more requirements include at least one of an edge data network (EDN) identifier that identifies a host EDN to instantiate the EES and an edge application server (EAS) identifier that identifies a list of EASs registered with the EES.

3 . The method of claim 1 ,

wherein the first network node is a service consumer device and the second network node is a service provider device.

4 . A first network node, the first network node comprising:

a transceiver; and

at least one processor coupled to the transceiver, wherein the at least one processor is configured to:

control the transceiver to transmit, to a second network node, a request for creating a managed object instance (MOI), the request including one or more requirements related to an edge enabler server (EES), and

receive, from the second network node, a response including information associated with the MOI for an EESfunction information object class (IOC) created based on the one or more requirements included in the request,

wherein the created MOI contains one or more attributes as defined in the EESfunction IOC, and

wherein the one or more attributes include an identifier of the EES, serving location information for the EES, and information indicating whether the EES supports service continuity.

5 . The first network node of claim 4 ,

wherein the one or more requirements include at least one of an edge data network (EDN) identifier that identifies a host EDN to instantiate the EES and an edge application server (EAS) identifier that identifies a list of EASs registered with the EES.

6 . The first network node of claim 4 ,

wherein the first network node is a service consumer device and the second network node is a service provider device.

Priority Claims (2)
IN 202041027497 · Jun 29, 2020 · national
IN 202041027497 · Jun 23, 2021 · national
Continuity (2)
Continuation 18012782 · Jun 29, 2021
Related Publication 20250030595A1 · Jan 23, 2025
References Cited (17)
US 12068921B2 · Gupta · 2024 [cited by examiner]
US 12088459B2 · Gautam · 2024 [cited by examiner]
US 20190266012A1 · Chou · 2019 [cited by applicant]
US 20200021487A1 · Yao et al. · 2020 [cited by applicant]
US 20210021494A1 · Yao · 2021 [cited by applicant]
US 20230047849A1 · Ge · 2023 [cited by applicant]
CN 109314649 · 2019 [cited by applicant]
DE 102018127383 · 2020 [cited by applicant]
WO WO20120120450 · 2012 [cited by applicant]
PCT/ISA/210 Search Report issued on PCT/KR2021/008169, Oct. 6, 2021, pp. 3. [cited by applicant]
PCT/ISA/237 Written Opinion issued on PCT/KR2021/008169, Oct. 6, 2021, pp. 4. [cited by applicant]
3GPP TS 28.526 Life Cycle Management for mobile networks that include virtualized network functions, (Release 17), Mar. 31, 2022, pp. 39. [cited by applicant]
3GPP; TSG SA; Architecture for enabling Edge Applications; (Release 17), Jun. 4, 2020, pp. 72. [cited by applicant]
3GPP; TSG SA; Management and orchestration; Generic management services; (Release 16), Mar. 27, 2020, pp. 239. [cited by applicant]
3GPP; TSG SA; Management and orchestration; Performance assurance (Release 16), Mar. 27, 2020, pp. 117. [cited by applicant]
Indian Examination Report dated Jun. 28, 2022 issued on counterpart Application No. IN 202041027497, pp. 6. [cited by applicant]
Chinese Office Action dated Apr. 22, 2026 issued on counterpart Application No. 202180045905.9, 18 pages. [cited by applicant]