Search

EP-4740509-A1 - SYSTEM AND METHOD FOR ORCHESTRATING INTERFACE REQUESTS IN A CONFIGURABLE AND ADAPTIVE FULFILMENT MANAGEMENT SYSTEM

EP4740509A1EP 4740509 A1EP4740509 A1EP 4740509A1EP-4740509-A1

Abstract

The present disclosure is related to a method and system for orchestrating interface requests in a configurable and adaptive fulfilment management system (FMS [102]). The method comprising: receiving, by a transceiver unit [101], a request from a northbound interface (NBI) [106] associated with the FMS [102]; adapting, by an adapting unit [103], a set of attributes from the request to a predefined format by using a configurable framework of the FMS[102]; translating, by a translating unit [105], the adapted request into a sequence of predefined application programming interface (API) calls; and executing, by an authentication unit [107], the sequence of predefined API calls to fulfil the received request.

Inventors

  • MURARKA, ANKIT
  • Gill, Kapil
  • BHATNAGAR, AAYUSH
  • AHMAD, RIZWAN
  • MAGU, Sameer
  • Godara, Rohtas
  • JAIN, ARPIT
  • MALIK, KAMAL
  • VERMA, RAHUL
  • Bhushan, Shashank

Assignees

  • Jio Platforms Limited

Dates

Publication Date
20260513
Application Date
20240611

Claims (16)

  1. 1. A method for orchestrating interface requests in a configurable and adaptive fulfilment management system (FMS) [102], the method comprises: receiving, by a transceiver unit [101], a request from a northbound interface (NBI) [106] associated with the FMS [102]; adapting, by an adapting unit [103], a set of attributes from the request to a predefined format by using a configurable framework of the FMS [102]; translating, by a translating unit [105], the adapted request into a sequence of predefined application programming interface (API) calls; and executing, by an authentication unit [107], the sequence of predefined API calls to fulfil the received request.
  2. 2. The method as claimed in claim 1, wherein the request received from the NBI [106] is an Application Programming Interface (API) request that comprises an extensive set of attributes for a plurality of southbound interface (SBI) APIs.
  3. 3. The method as claimed in claim 2, wherein the executing further comprises routing, by a routing unit [109], the executed request to one or more network nodes based on at least one attribute associated with the request, and wherein the one or more network nodes are associated with a southbound interface (SBI) of the FMS [102],
  4. 4. The method as claimed in claim 3, wherein the set of attributes further comprises configuring one of an endpoint and a Uniform Resource Locator (URL) associated with the one or more network nodes associated with the southbound interface (SBI) of the FMS [102], and wherein the one of the endpoint and the URL is configurable through the configurable framework of the FMS [102],
  5. 5. The method as claimed in claim 1, wherein the adapting the set of attributes comprises configuring at least one field of the received request comprising at least one of a name field, a type field, and a flag field.
  6. 6. The method as claimed in claim 1, wherein the request is received from a user equipment (UE) associated with a user.
  7. 7. The method as claimed in claim 1, wherein the method comprises dynamically managing, by an adapting unit [103], one or more changes in the one or more network nodes based on an activation of one or more configuration changes in the FMS [102],
  8. 8. A system for orchestrating interface requests in a configurable and adaptive fulfilment management system (FMS) [102], the system comprises: a transceiver unit [101] configured to receive a request from a northbound interface (NBI) [106] associated with the FMS [102]; an adapting unit [103] connected at least to the transceiver unit [101], wherein the adapting unit [103] is configured to adapt a set of attributes from the request to a predefined format by using a configurable framework of the FMS [102]; a translating unit [105] connected at least to the adapting unit [103], wherein the translating unit [105] is configured to translate the adapted request into a sequence of predefined application programming interface (API) calls; and an authentication unit [107] connected at least to the translating unit [105], wherein the authentication unit [107] is configured to execute the sequence of predefined API calls to fulfil the received request.
  9. 9. The system as claimed in claim 8, wherein the request received from the NBI [106] is an Application Programming Interface (API) request that comprises an extensive set of attributes for a plurality of southbound interface (SBI) APIs.
  10. 10. The system as claimed in claim 9, the system comprises a routing unit [109] connected at least to the authentication unit [107] and is configured to route the executed request to one or more network nodes based on at least one attribute associated with the request, and wherein the one or more network nodes are associated with a southbound interface (SBI) of the FMS [102],
  11. 11. The system as claimed in claim 10, wherein the set of attributes further comprises configuring one of an endpoint and a Uniform Resource Locator (URL) associated with the one or more network nodes associated with the southbound interface (SBI) of the FMS [102], and wherein the one of the endpoint and the URL is configurable through the configurable framework of the FMS [102],
  12. 12. The system as claimed in claim 8, wherein the adaption of the set of attributes in the request format comprises configuration of at least one field of the received request comprising at least one of a name field, a type field, and a flag field.
  13. 13. The system as claimed in claim 8, wherein the request is received from a user equipment (UE) associated with a user.
  14. 14. The system as claimed in claim 8, wherein the system comprises an adapting unit [103] connected at least to the routing unit [109] and is configured to dynamically manage one or more changes in the one or more network nodes based on an activation of configuration changes in the FMS [102],
  15. 15. A user equipment (UE) comprises: a transceiver unit configured to: transmit a request to a system [100], wherein request comprises a set of attributes, and receive a response from the system [100], wherein the response is generated by the system [100] based on: adaptation of the set of attributes from the request to a predefined format, translation of the adapted request into a sequence of predefined application programming interface (API) calls, and execution of the sequence of predefined API calls to fulfil the received request.
  16. 16. A non-transitory computer readable storage medium storing instruction for orchestrating interface requests in a configurable and adaptive fulfilment management system (FMS) [102], the instructions when executed by one or more units of a system [100], causes: a transceiver unit [101] of the system [100] to receive a request from a northbound interface (NBI) [106] associated with the FMS [102]; an adapting unit [103] of the system [100] to adapt a set of attributes from the request to a predefined format by using a configurable framework of the FMS [102]; a translating unit [105] of the system [100] to translate the adapted request into a sequence of predefined application programming interface (API) calls; and an authentication unit [107] of the system [100] to execute the sequence of predefined API calls to fulfil the received request.

Description

SYSTEM AND METHOD FOR ORCHESTRATING INTERFACE REQUESTS IN A CONFIGURABLE AND ADAPTIVE FULFILMENT MANAGEMENT SYSTEM FIELD OF THE DISCLOSURE [0001] Embodiments of the present disclosure relates generally to the field of wireless communication systems. More particularly, embodiments of the present disclosure relate to method and system for orchestration of interface requests in a configurable and adaptive fulfilment management system (FMS). BACKGROUND [0002] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art. [0003] 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. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The third-generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users. [0004] Many traditional systems (such as a system configured in a wireless communication network for providing communication facilities) do not have the capability to adapt to changes in the request or response formats of integrated systems without making code-level changes, which could require additional development efforts and potentially introduce system downtime. Existing systems often struggle to support complex workflows, including sequential, parallel, conditional, and looped execution patterns. This inflexibility can limit the complexity and variety of processes that can be effectively managed. Further, traditional systems often lack the ability to configure field details such as name, type, and optional/mandatory flag etc. This lack of configurability requires additional coding efforts each time these attributes need to be altered. Further, existing systems often lack efficient and configurable routing capabilities, especially based on specific attributes of the requests. This can limit the performance and flexibility of the system when dealing with multiple interface endpoints. [0005] Thus, there exists an imperative need in the art for a configurable and adaptive fulfilment management system for interface request orchestration and method thereof, and that aims to address these issues, offering a more flexible, adaptable, and efficient approach to managing the fulfilment of requests from various systems. OBJECTS OF THE DISCLOSURE [0006] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below. [0007] It is another object of the present disclosure to provide a configurable and adaptive fulfilment management system for interface request orchestration and method thereof. [0008] It is another object of the present disclosure to provide a configurable and adaptive fulfilment management system for interface request orchestration and method thereof that can adapt to changes in the request or response formats of integrated systems without needing to make code-level changes. [0009] It is another object of the present disclosure to provide a configurable and adaptive fulfilment management system for interface request orchestration and method thereof that support complex workflows, including sequential, parallel, conditional, and loop execution patterns, all configurable as per the requirements of the integrated system. [00010] It is another object of the present disclosure to provide a configurable and adaptive fulfilment management system for interface request orchestration and method thereof to enable configurable field details such as name, type, and optional/mandatory flag for rapid and flexible modification of these attributes as needed. [00011] It is another object of the present disclosure to provide a configurable and adaptive fulfilment management system for interface request orchestration and method thereof that allows easy management of the endpoints or URLs for the southbound interfaces to handle changes in