[go: up one dir, main page]

WO2025069096A1 - Procédé et système de communication entre un microservice et un moteur d'exécution de politique (peegn) - Google Patents

Procédé et système de communication entre un microservice et un moteur d'exécution de politique (peegn) Download PDF

Info

Publication number
WO2025069096A1
WO2025069096A1 PCT/IN2024/051893 IN2024051893W WO2025069096A1 WO 2025069096 A1 WO2025069096 A1 WO 2025069096A1 IN 2024051893 W IN2024051893 W IN 2024051893W WO 2025069096 A1 WO2025069096 A1 WO 2025069096A1
Authority
WO
WIPO (PCT)
Prior art keywords
request message
type
subscriber
event
unit
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/IN2024/051893
Other languages
English (en)
Inventor
Aayush Bhatnagar
Adityakar -
Ankit Murarka
Yog VASHISHTH
Meenakshi Rani
Santosh Kumar YADAV
Jugal Kishore
Gaurav Saxena
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.)
Jio Platforms Ltd
Original Assignee
Jio Platforms 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 Jio Platforms Ltd filed Critical Jio Platforms Ltd
Publication of WO2025069096A1 publication Critical patent/WO2025069096A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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/50—Network services
    • H04L67/55—Push-based network services
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/542—Event management; Broadcasting; Multicasting; Notifications
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/546—Message passing systems or structures, e.g. queues
    • 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

Definitions

  • the present disclosure generally relates to network performance management systems. More particularly, embodiments of the present disclosure relate to methods and systems for communication between a microservice and a policy execution engine (PEEGN).
  • PEEGN policy execution engine
  • Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements.
  • the first generation of wireless communication technology was based on analog technology and offered only voice services.
  • 2G second-generation
  • 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services.
  • 4G fourth-generation
  • 5G fifth-generation
  • wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
  • PEEGN Policy Execution Engine
  • VNF virtualized network
  • the PEEGN enriches the NFV SDN Platform with automatic scaling and healing functionality of network components and services.
  • the PEEGN provide policies for Resource, Security, Availability, and Scalability.
  • ERM is an event routing manager, which is used to route all the incoming requests to the PEEGN and all the outgoing requests from the PEEGN. This interface follows a subscription and notification model based on the events which are published to it. Each micro service registers its standard platform events with the ERM.
  • An aspect of the present disclosure may relate to a method for communication between a microservice and a policy execution engine (PEEGN).
  • the method includes receiving, by a transceiver unit, at an Event Routing Manager (ERM) unit, a request message comprising at least an event type and a publisher type, wherein the publisher type is at least one of the PEEGN and the microservice.
  • the method further includes determining, by a determination unit, at the ERM unit, a target publisher, associated with the request message, based on the publisher type, wherein the publisher type is the PEEGN.
  • ERP Event Routing Manager
  • the method further includes transmitting, by the transceiver unit, from the ERM unit to the target publisher, the request message; receiving, by the transceiver unit, at the ERM unit, from the target publisher, a response for the request message, the response comprising a subscriber type associated with the request message.
  • the method further includes identifying, by an identification unit, at the ERM unit, a subscriber, associated with the request message, based on the subscriber type.
  • the method further includes transmitting, by the transceiver unit, from the ERM unit to the subscriber, the response associated with the request message
  • the method further comprises identifying, by the identification unit, at the ERM unit, the subscriber as the microservice in an event the target publisher is the PEEGN.
  • the event type is at least one of an event and an acknowledgement for an event.
  • the method further comprises transmitting, by the transceiver unit, from the ERM unit to the target publisher, the request message, in a scenario the event type is the event.
  • the method further comprises transmitting, by the transceiver unit, from the ERM unit to the subscriber, the response associated with the request message, in a scenario the event type is the acknowledgement.
  • the system comprises an event routing manager (ERM) unit comprising a transceiver unit [302],
  • the transceiver unit [302] is configured to receive a request message comprising at least an event type and a publisher type, wherein the publisher type is at least one of the PEEGN.
  • the transceiver unit [302] is further configured to transmit to the target publisher, the request message.
  • the transceiver unit [302] is further configured to receive from the target publisher, a response for the request message, the response comprising a subscriber type associated with the request message.
  • the system further comprises an identification unit [304] configured to identify a subscriber, associated with the request message, based on the subscriber type.
  • the transceiver unit [302] is further configured to transmit to the subscriber, the response associated with the request message.
  • Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for communication between a microservice and a policy execution engine (PEEGN), the instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit to receive a request message comprising at least an event type and a publisher type, wherein the publisher type is at least one of the PEEGN.
  • the executable code when executed further causes transceiver unit to transmit to the target publisher, the request message.
  • the executable code when executed further causes the transceiver unit to receive from the target publisher, a response for the request message, the response comprising a subscriber type associated with the request message.
  • the executable code when executed further causes an identification unit to identify a subscriber, associated with the request message, based on the subscriber type.
  • the executable code when executed further causes the transceiver unit to transmit to the subscriber the response associated with the request message.
  • PEEGN policy execution engine
  • ERP Event Routing Manager
  • PEEGN Policy Execution Engine
  • FIG. 1 illustrates an exemplary block diagram representation of a management and orchestration (MANO) architecture, in accordance with exemplary implementation of the present disclosure.
  • MANO management and orchestration
  • FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
  • FIG. 3 illustrates an exemplary block diagram of a system for communication between a microservice and a policy execution engine (PEEGN), in accordance with exemplary implementations of the present disclosure.
  • PEEGN policy execution engine
  • FIG. 4 illustrates a method flow diagram for communication between a microservice and a policy execution engine (PEEGN), in accordance with exemplary implementations of the present disclosure.
  • PEEGN policy execution engine
  • FIG. 5 illustrates an exemplary block diagram of a system architecture for communication between a microservice and a policy execution engine (PEEGN), in accordance with exemplary implementations of the present disclosure.
  • PEEGN policy execution engine
  • FIG. 6 illustrates a process flow diagram for communication between a microservice and a policy execution engine (PEEGN), in accordance with exemplary implementations of the present disclosure.
  • PEEGN policy execution engine
  • exemplary and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples.
  • any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art.
  • a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions.
  • a processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital Signal Processing (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc.
  • DSP Digital Signal Processing
  • the processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
  • a user equipment may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure.
  • the user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure.
  • the user device may contain at least one input means configured to receive an input from unit(s) which are required to implement the features of the present disclosure.
  • storage unit or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine.
  • a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media.
  • the storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
  • interface refers to a shared boundary across which two or more separate components of a system exchange information or data.
  • the interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
  • All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
  • DSP digital signal processor
  • ASIC Application Specific Integrated Circuits
  • FPGA Field Programmable Gate Array circuits
  • the transceiver unit includes at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.
  • the present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a method and system for communication between a microservice and a policy execution engine (PEEGN).
  • PEEGN policy execution engine
  • FIG. 1 an exemplary block diagram representation of a management and orchestration (MANO) architecture [100], in accordance with exemplary implementation of the present disclosure is illustrated.
  • the MANO architecture [100] is developed for managing telecom cloud infrastructure automatically, managing design or deployment design, managing instantiation of a network node(s) etc.
  • the MANO architecture [100] deploys the network node(s) in the form of Virtual Network Function (VNF) and Cloud-native/ Container Network Function (CNF).
  • VNF Virtual Network Function
  • CNF Cloud-native/ Container Network Function
  • the MANO architecture [100] is used to auto-instantiate the VNFs into the corresponding environment of the present disclosure so that it could help in onboarding other vendor(s) CNFs and VNFs to the platform.
  • the MANO architecture comprises a user interface layer, a network function virtualization (NFV) and software defined network (SDN) design function module [104]; a platforms foundation services module [106], a platform core services module [108] and a platform resource adapters and utilities module [112], wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.
  • NFV network function virtualization
  • SDN software defined network
  • the NFV and SDN design function module [104] further comprises a VNF lifecycle manager (compute) [1042]; a VNF catalogue [1044]; a network services catalogue [1046]; a network slicing and service chaining manager [1048]; a physical and virtual resource manager [1050] and a CNF lifecycle manager [1052],
  • the VNF lifecycle manager (compute) [1042] is responsible for determining on which server of the communication network the microservice will be instantiated.
  • the VNF lifecycle manager (compute) [1042] will manage the overall flow of incoming/ outgoing requests during interaction with the user.
  • the VNF lifecycle manager (compute) [1042] is responsible for determining which sequence to be followed for executing the process.
  • the VNF catalogue [1044] stores the metadata of all the VNFs (also CNFs in some cases).
  • the network services catalogue [1046] stores the information of the services that need to be run.
  • the network slicing and service chaining manager [1048] manages the slicing (an ordered and connected sequence of network service/ network functions (NFs)) that must be applied to a specific networked data packet.
  • the physical and virtual resource manager [1050] stores the logical and physical inventory of the VNFs. Just like the VNF lifecycle manager (compute) [1042], the CNF lifecycle manager [1052] is similarly used for the CNFs lifecycle management.
  • the platforms foundation services module [106] further comprises a microservices edge load balancer [1062]; an identify & access manager [1064]; a command line interface (CLI) [1066]; a central logging manager [1068]; and an event routing manager (ERM) [1070] (alternatively referred to as ERM unit [1070] herein).
  • the microservices edge load balancer [1062] is used for maintaining the load balancing of the request for the services.
  • the identify & access manager [1064] is used for logging purposes.
  • the command line interface (CLI) [1066] is used to provide commands to execute certain processes which require changes during the run time.
  • the central logging manager [1068] is responsible for keeping the logs of every service.
  • the logs are generated by the MANO architecture [100], The logs are used for debugging purposes.
  • the ERM unit [1070] is responsible for routing the events i.e., the application programming interface (API) hits to the
  • the platforms core services module [108] further comprises NFV infrastructure monitoring manager [1082]; an assure manager [1084]; a performance manager [1086]; a policy execution engine (PEEGN) [1088]; a capacity monitoring manager (CP) [1090]; a release management (mgmt.) repository [1092]; a configuration manager & Golden Configuration Template (GCT))[1094]; an NFV platform decision analytics [1096]; a platform NoSQL DB [1098]; a platform schedulers and cron jobs (PSC) service [1100]; a VNF backup & upgrade manager [1102]; a microservice auditor [1104]; and a platform operations, administration and maintenance manager [1106],
  • the NFV infrastructure monitoring manager [1082] monitors the infrastructure part of the NFs.
  • the assure manager [1084] is responsible for supervising the alarms the vendor is generating.
  • the performance manager [1086] is responsible for manging the performance counters.
  • the PEEGN [1088] is responsible for managing all the policies.
  • the capacity monitoring manager (CP) [1090] is responsible for sending the request to the PEEGN [1088],
  • the capacity monitoring manager (CP) [1090] is capable of monitoring usage of network resources such as but not limited to CPU utilization, RAM utilization and storage utilization across all the instances of the virtual infrastructure manager (VIM) or simply the NFV infrastructure monitoring manager [1082],
  • the capacity monitoring manager (CP) [1090] is also capable of monitoring said network resources for each instance of the VNF.
  • the capacity monitoring manager (CP) [1090] is responsible for constantly tracking the network resource utilization.
  • the release management (mgmt.) repository [1092] is responsible for managing the releases and the images of all the vendor network nodes.
  • the configuration manager & GCT [1094] manages the configuration and GCT of all the vendors.
  • the NFV platform decision analytics [1096] helps in deciding the priority of using the network resources. It is further noted that the PEEGN [1088], the configuration manager & GCT [1094] and the NFV platform decision analytics [1096] work together.
  • the platform NoSQL DB [1098] is a database for storing all the inventory (both physical and logical) as well as the metadata of the VNFs and CNF.
  • the platform schedulers and cron jobs (PSC) service [1100] schedules the task such as but not limited to triggering of an event, traversing the network graph etc.
  • the VNF backup & upgrade manager [1102] takes backup of the images, binaries of the VNFs and the CNFs and produces those backups on demand in case of server failure.
  • the microservice auditor [1104] audits the microservices.
  • the microservice auditor [1104] audits and informs the same so that resources can be released for services running in the MANO architecture [100], thereby assuring the services only run on the MANO architecture [100],
  • the platform operations, administration, and maintenance manager [1106] is used for newer instances that are spawning.
  • the platform resource adapters and utilities module [112] further comprises a platform external API adaptor and gateway [1122]; a generic decoder and indexer (XML, CSV, JSON) [1124]; a docker service adaptor [1126]; an API adapter [1128]; and a NFV gateway [1130],
  • the platform external API adaptor and gateway [1122] is responsible for handling the external services (to the MANO architecture [100]) that require the network resources.
  • the generic decoder and indexer (XML, CSV, JSON) [1124] directly gets the data of the vendor system in the XML, CSV, JSON format.
  • the docker service adaptor [1126] is the interface provided between the telecom cloud and the MANO architecture [100] for communication.
  • the API adapter [1128] is used to connect with the virtual machines (VMs).
  • the NFV gateway [1130] is responsible for providing the path to each service going to/incoming from the MANO architecture [100], [0045]
  • FIG. 2 illustrates an exemplary block diagram of a computing device [200] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
  • the computing device [200] may also implement a method for communication between a microservice and a policy execution engine (PEEGN) utilising the system [300],
  • the computing device [200] itself implements the method for communication between a microservice and a policy execution engine (PEEGN) using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
  • the computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a processor [204] coupled with bus [202] for processing information.
  • the processor [204] may be, for example, a general-purpose microprocessor.
  • the computing device [200] may also include a main memory [206], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the processor [204],
  • the main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [204], Such instructions, when stored in non-transitory storage media accessible to the processor [204], render the computing device [200] into a special-purpose machine that is customized to perform the operations specified in the instructions.
  • the computing device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204],
  • ROM read only memory
  • a storage device [210] such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [202] for storing information and instructions.
  • the computing device [200] may be coupled via the bus [202] to a display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user.
  • An input device [214] including alphanumeric and other keys, touch screen input means, etc.
  • a cursor controller [216] such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling cursor movement on the display [212].
  • the input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
  • the computing device [200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [200] causes or programs the computing device [200] to be a special-purpose machine.
  • the techniques herein are performed by the computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206], Such instructions may be read into the main memory [206] from another storage medium, such as the storage device [210], Execution of the sequences of instructions contained in the main memory [206] causes the processor [204] to perform the process steps described herein.
  • hard-wired circuitry may be used in place of or in combination with software instructions.
  • the computing device [200] also may include a communication interface [218] coupled to the bus [202], The communication interface [218] provides a two-way data communication coupling to a network link [220] that is connected to a local network [222],
  • the communication interface [218] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line.
  • the communication interface [218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN.
  • LAN local area network
  • Wireless links may also be implemented.
  • the communication interface [218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
  • the computing device [200] can send messages and receive data, including program code, through the network(s), the network link [220] and the communication interface [218],
  • a server [230] might transmit a requested code for an application program through the Internet [228], the ISP [226], the local network [222], a host [224] and the communication interface [218],
  • the received code may be executed by the processor [204] as it is received, and/or stored in the storage device [210], or other non-volatile storage for later execution.
  • the computing device [200] encompasses a wide range of electronic devices capable of processing data and performing computations.
  • Examples of computing device [200] include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers, and embedded systems.
  • the devices may operate independently or as part of a network and can perform a variety of tasks such as data storage, retrieval, and analysis.
  • computing device [200] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, sselling their versatility in various technological applications.
  • FIG. 3 an exemplary block diagram of a system [300] for communication between a microservice and a policy execution engine (PEEGN), is shown, in accordance with the exemplary implementations of the present disclosure.
  • the system [300] comprises at least ERM unit [1070],
  • the ERM unit [1070] further comprises at least one transceiver unit [302], and at and at least one identification unit [304],
  • all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below.
  • all units shown within the system [300] should also be assumed to be connected to each other. Also, in FIG.
  • system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure.
  • the system [300] may be present in a user device/ user equipment [102] to implement the features of the present disclosure.
  • the system [300] may be a part of the user device [102]/ or may be independent of but in communication with the user device [102] (may also referred herein as a UE).
  • the system [300] may reside in a server or a network entity.
  • the system [300] may reside partly in the server/ network entity and partly in the user device.
  • the system [300] is configured for communication between a microservice and a policy execution engine (PEEGN), with the help of the interconnection between the components/units of the system [300],
  • PEEGN policy execution engine
  • the system [300] comprises an event routing manager (ERM) unit [1070],
  • the ERM unit [1070] further comprises a transceiver unit [302] configured to receive a request message comprising at least an event type and a publisher type, wherein the publisher type is at least one of the PEEGN.
  • the transceiver unit [302] receives the request message for registering an event.
  • the request message comprises at least the event type and the publisher type.
  • the publisher is at least one of the PEEGN.
  • the request message includes the event type which specifies the nature of the event.
  • event type may relate to a request for resource allocation.
  • each publisher type there can be multiple subscribers.
  • the event type is at least one of an event and an acknowledgement for an event.
  • the acknowledgment is sent in the form of notification by the ERM unit [1070] to the subscribers informing them of the said event.
  • the transceiver unit [302] is further configured to transmit to the target publisher, the request message.
  • the transceiver unit [302] transmits to the target publisher, the request message.
  • target publisher refers to the specific or targeted microservice or the Policy Execution Engine (PEEGN) that is assigned to handle the request message transmitted by the transceiver unit [302],
  • PEEGN Policy Execution Engine
  • the transceiver unit [302] is further configured to transmit, to the target publisher, the request message, in a scenario the event type is the event.
  • the transceiver unit [302] transmits to the target publisher, the request message, in a scenario the event type is the event.
  • the transceiver unit [302] is further configured to receive from the target publisher, a response for the request message, the response comprising a subscriber type associated with the request message. [0065] The transceiver unit [302] receives from the target publisher, the response for the request message. The response further comprises the subscriber type associated with the request message. In an exemplary aspect, when the target publisher processes the request message, it sends back the response that includes the subscriber type related to the initially sent request.
  • the subscriber type may include such as but not limited to containerized network function lifecycle manager (CNFLM) [1052], network function virtualization (NFV) platform decision analytics (NPDA) [1096], physical virtual resource manager (PVIM) [1050] (also referred as physical and virtual resource manager [1050]), policy execution engine (PEEGN) [1088], user interface (U.I) etc.
  • CFLM containerized network function lifecycle manager
  • NFV network function virtualization
  • NPDA network function virtualization platform decision analytics
  • PVIM physical virtual resource manager
  • PEEGN policy execution engine
  • U.I user interface
  • the system [300] further comprises an identification unit [304] configured to identify a subscriber, associated with the request message, based on the subscriber type.
  • the identification unit [304] identifies the subscriber, associated with the request message based on the subscriber type.
  • the identification unit [304] is further configured to identify the subscriber as the microservice in an event the target publisher is the PEEGN.
  • the identification unit [304] identifies the subscriber as the microservice.
  • the transceiver unit [302] is further configured to transmit to the subscriber, the response associated with the request message.
  • the transceiver unit [302] Based on the identification of the subscriber as the microservice, the transceiver unit [302] transmits to the subscriber the response associated with the request message.
  • the transceiver unit [302] is further configured transmit, to the subscriber, the response associated with the request message, in a scenario the event type is the acknowledgement.
  • the transceiver unit [302] transmits to the subscriber, the response associated with the request message, in a scenario the event type is the acknowledgement.
  • FIG. 4 an exemplary method flow diagram [400] for communication between a microservice and a policy execution engine (PEEGN), in accordance with exemplary implementations of the present disclosure is shown.
  • the method [400] is performed by the system [300], Further, in an implementation, the system [300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 4, the method [400] starts at step [402],
  • the method [400] comprises receiving, by a transceiver unit [302], at the ERM unit [1070], a request message comprising at least an event type and a publisher type, wherein the publisher type is at least one of the PEEGN.
  • the transceiver unit [302] receives the request message for registering an event.
  • the request message comprises at least the event type and the publisher type.
  • the publisher is at least one of the PEEGN.
  • the request message includes the event type which specifies the nature of the event.
  • event type may relate to a request for resource allocation.
  • each publisher type there can be multiple subscribers.
  • the event type is at least one of an event and an acknowledgement for an event.
  • the acknowledgment is sent in the form of notification by the ERM unit [1070] to the subscribers informing them of the said event.
  • the method [400] comprises transmitting, by the transceiver unit [302], from the ERM unit [1070], to the target publisher, the request message.
  • the transceiver unit [302] transmits to the target publisher, the request message.
  • target publisher refers to the specific or targeted microservice or the Policy Execution Engine (PEEGN) that is assigned to handle the request message transmitted by the transceiver unit [302], [0084]
  • the method [400] further comprises transmitting, by the transceiver unit [302], from the ERM unit [1070], to the target publisher, the request message, in a scenario the event type is the event.
  • the transceiver unit [302] transmits to the target publisher, the request message, in a scenario the event type is the event.
  • the method [400] comprises receiving, by the transceiver unit [302], at the ERM unit [1070], from the target publisher, a response for the request message, the response comprising a subscriber type associated with the request message.
  • the transceiver unit [302] receives from the target publisher, the response for the request message.
  • the response further comprises the subscriber type associated with the request message.
  • the target publisher processes the request message, it sends back the response that includes the subscriber type related to the initially sent request.
  • the subscriber type may include such as but not limited to containerized network function lifecycle manager (CNFLM) [1052], network function virtualization (NFV) platform decision analytics (NPDA) [1096], physical virtual resource manager (PVIM) [1050] (also referred as physical and virtual resource manager [1050]), policy execution engine (PEEGN) [1088], user interface (U.I) etc.
  • CFLM containerized network function lifecycle manager
  • NFV network function virtualization
  • NPDA network function virtualization platform decision analytics
  • PVIM physical virtual resource manager
  • PEEGN policy execution engine
  • U.I user interface
  • the method [400] comprises identifying, by an identification unit [304], at the ERM unit [1070], a subscriber, associated with the request message, based on the subscriber type.
  • the identification unit [304] identifies the subscriber, associated with the request message based on the subscriber type.
  • the method further comprises identifying, by the identification unit [304], at the ERM unit [1070], the subscriber as the microservice in an event the target publisher is the PEEGN.
  • the identification unit [304] identifies the subscriber as the microservice.
  • the method [400] comprises transmitting, by the transceiver unit [302], from the ERM unit [1070], to the subscriber, the response associated with the request message.
  • the transceiver unit [302] Based on the identification of the subscriber as the microservice, the transceiver unit [302] transmits to the subscriber the response associated with the request message.
  • the method [400] further comprises transmitting, by the transceiver unit [302], from the ERM unit [1070], to the subscriber, the response associated with the request message, in a scenario the event type is the acknowledgement.
  • the transceiver unit [302] transmits to the subscriber, the response associated with the request message, in a scenario the event type is the acknowledgement.
  • step [414] the method [400] is terminated.
  • FIG. 5 an exemplary block diagram of a system architecture [500] for communication between a microservice and a policy execution engine (PEEGN), is shown, in accordance with the exemplary implementations of the present disclosure.
  • the system architecture comprises at least one microservice [502], at least one PEEGN [1088], and at least one ERM unit [1070],
  • ERM unit [1070] is an event routing manager, which is used to route all the incoming request to PEEGN [1088] and all the outgoing request from PEEGN [1088], This interface follows a subscription and notification model based on the events which are published to it.
  • Each micro service registers its standard platform events with the ERM unit [1070], For each event, there can be multiple subscribers. Whenever the event of interest is received, the notifications are sent by the ERM unit [1070] to the subscribers informing them of the said event.
  • FIG. 6 an exemplary process [600] flow diagram for communication between a microservice and a policy execution engine (PEEGN), in accordance with exemplary implementations of the present disclosure is shown.
  • the process [600] is performed by the system [300]
  • the process [600] starts at step [602], [0101]
  • step [604] If any microservice [502] wants to send request to PEEGN [1088] then that event should be registered in ERM unit [1070] as publisher as PEEGN [1088] and subscriber as other microservice [502],
  • the process [600] comprises checking, at PE EM interface, in the event for publisher name as PEEGN [1088] and if finds true then it will send request to PEEGN [1088],
  • the process [600] comprises checking, at PE EM interface, the event which is being sent by PEEGN [1088] for the publisher’s name and redirects the request to same publisher.
  • ERM unit [1070] will pass the request to publisher, and if event type is “eventAck” then ERM unit [1070] will pass the request to subscriber.
  • the present disclosure further discloses a non-transitory computer readable storage medium storing instructions for communication between a microservice and a policy execution engine (PEEGN), the instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit [302] to receive a request message comprising at least an event type and a publisher type, wherein the publisher type is at least one of the PEEGN.
  • the executable code when executed further causes transceiver unit [302] to transmit to the target publisher, the request message.
  • the executable code when executed further causes transceiver unit [302] to receive from the target publisher, a response for the request message, the response comprising a subscriber type associated with the request message.
  • the executable code when executed further causes an identification unit [304] configured to identify a subscriber, associated with the request message, based on the subscriber type.
  • the executable code when executed further causes the transceiver unit [302] is further configured to transmit to the subscriber, the response associated with the request message.
  • PEEGN policy execution engine
  • the present invention provides a solution for optimizing system performance by enhancing operation capability and simplifying routing request based on robust communication between Event Routing Manager (ERM) unit and Policy Execution Engine (PEEGN) via PE EM interface.
  • the present solution further provides easy Request routing that increases overall system efficiency, operational issue to add/modify request subscriber publisher.
  • the present solution enhances request reusability ensuring that there is no nonservice impact.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer And Data Communications (AREA)

Abstract

La présente divulgation concerne un procédé et un système de communication entre un microservice et un moteur d'exécution de politique (PEEGN). La présente divulgation comprend la réception d'un message de demande comprenant au moins un type d'événement et un type d'éditeur, le type d'éditeur étant le PEEGN et/ou le microservice ; la détermination d'un éditeur cible, associé au message de demande, sur la base du type d'éditeur, le type d'éditeur étant le PEEGN ; la transmission à l'éditeur cible, du message de demande ; la réception en provenance de l'éditeur cible, d'une réponse pour le message de demande, la réponse comprenant un type d'abonné associé au message de demande ; l'identification d'un abonné, associé au message de demande, sur la base du type d'abonné ; et la transmission à l'abonné, de la réponse associée au message de demande.
PCT/IN2024/051893 2023-09-28 2024-09-28 Procédé et système de communication entre un microservice et un moteur d'exécution de politique (peegn) Pending WO2025069096A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202321065361 2023-09-28
IN202321065361 2023-09-28

Publications (1)

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

Family

ID=95201416

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IN2024/051893 Pending WO2025069096A1 (fr) 2023-09-28 2024-09-28 Procédé et système de communication entre un microservice et un moteur d'exécution de politique (peegn)

Country Status (1)

Country Link
WO (1) WO2025069096A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180109634A1 (en) * 2014-10-21 2018-04-19 Twilio, Inc. System and method for providing a micro-services communication platform
US20220286360A1 (en) * 2021-03-06 2022-09-08 Juniper Networks, Inc. Global network state management

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180109634A1 (en) * 2014-10-21 2018-04-19 Twilio, Inc. System and method for providing a micro-services communication platform
US20220286360A1 (en) * 2021-03-06 2022-09-08 Juniper Networks, Inc. Global network state management

Similar Documents

Publication Publication Date Title
WO2025062464A1 (fr) Procédé et système de routage d'événements dans un environnement de réseau
WO2025069096A1 (fr) Procédé et système de communication entre un microservice et un moteur d'exécution de politique (peegn)
WO2025069109A1 (fr) Procédé et système de routage d'une demande par l'intermédiaire d'une interface
WO2025069098A1 (fr) Procédé et système de gestion d'instances de fonction de réseau virtuel (vnf) dans un réseau
WO2025074399A1 (fr) Procédé et système de gestion d'événement(s) concernant des politiques relatives à une ou à plusieurs opérations
WO2025069110A1 (fr) Procédé et système de fourniture d'informations de fonction de réseau virtuel au niveau d'un moteur d'exécution de politiques
WO2025069103A1 (fr) Procédé et système de gestion du fonctionnement de composants de fonction réseau conteneurisée (cnfc)
WO2025069060A1 (fr) Procédé et système de gestion d'une fonction de réseau
WO2025069099A1 (fr) Procédé et système de gestion de ressources de fonction de réseau virtuel (vnf)
WO2025069047A1 (fr) Procédé et système de réservation de ressources pour l'instanciation d'une fonction de réseau
WO2025069081A1 (fr) Procédés et systèmes de gestion d'opérations de base de données dans un réseau
WO2025062419A1 (fr) Procédé et système de planification d'une tâche par un planificateur de plateforme et service de travaux cron
WO2025057213A1 (fr) Procédé et système de gestion de données relatives à des fonctions réseau
WO2025062461A1 (fr) Procédé et système permettant d'exécuter au moins une tâche de service
WO2025069082A1 (fr) Procédés et systèmes d'attribution d'une ou de plusieurs ressources de réseau dans un réseau de télécommunication
WO2025062450A1 (fr) Procédé et système de mise en œuvre d'actions correctives pendant un événement d'erreur de seuil de ressource
WO2025074391A1 (fr) Procédés et systèmes de mise en œuvre de gestion et d'orchestration de ressources dynamiques dans un réseau
WO2025069083A1 (fr) Procédé et système de distribution du trafic de données dans un réseau
WO2025057236A1 (fr) Procédé et système de distribution d'une charge de trafic à l'aide d'une interface
WO2025069114A1 (fr) Procédé et système d'instanciation de fonctions de réseau de conteneurs sur un hôte
WO2025069085A1 (fr) Procédé et système pour effectuer une ou plusieurs opérations sur une ou plusieurs fonctions de réseau dans un réseau
WO2025069073A1 (fr) Procédé et système de gestion de contraintes de ressources dans un réseau
WO2025062451A1 (fr) Procédé et système d'évaluation d'une hystérésis pour un événement d'erreur
WO2025062465A1 (fr) Système et procédé d'équilibrage de charge de demandes
WO2025069077A1 (fr) Procédé et système de distribution de trafic de données dans un réseau

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

Country of ref document: EP

Kind code of ref document: A1