EP-4740369-A1 - SYSTEM AND METHOD FOR CONFIGURING SYNCHRONOUS AND AN ASYNCHRONOUS RESPONSE MECHANISM IN FULFILMENT MANAGEMENT SYSTEM

Abstract

In an embodiment, the present disclosure relates to a method for configuring a synchronous response mechanism and an asynchronous response mechanism in a FMS [101], the method comprising: receiving, by a transceiver unit [102], a request for interaction from a requesting system, the requesting system comprising at least one of a northbound interface (NBI) system [202] and a third-party system; determining, by a determination unit [104], a type of application programming interface (API) interaction supported by the requesting system based on the received request, wherein the type of API interaction is one of a synchronous interaction and an asynchronous interaction; configuring the FMS [101], by an analysis unit [106], to generate a response based on the determined type of API interaction; and transmitting, by the transceiver unit [102], the generated response to the requesting system based on the determined type of API interaction

Inventors

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

Assignees

• Jio Platforms Limited

Dates

Publication Date

20260513

Application Date

20240612

Claims (16)

1. 1. A method for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system (FMS) [101], said method comprising: receiving, by a transceiver unit [102] at the FMS [101], a request for interaction from a requesting system, the requesting system comprising at least one of a northbound interface (NBI) system [202] and a third-party system; determining, by a determination unit [104] at the FMS [101], a type of application programming interface (API) interaction supported by the requesting system based on the received request, wherein the type of API interaction is one of a synchronous interaction and an asynchronous interaction; configuring the FMS [101], by an analysis unit [106] at the FMS [101], to generate a response based on the determined type of API interaction; and transmitting, by the transceiver unit [102], the generated response to the requesting system based on the determined type of API interaction.
2. 2. The method as claimed in claim 1, wherein the request is one of a call type requests and a command type request.
3. 3. The method as claimed in claim 2, wherein the one of the call type requests and the command type request is associated with performing a set of tasks on a data in the FMS [101],
4. 4. The method as claimed in claim 1, wherein the determining the type of API interaction comprises analysing, by the analysis unit [106], the request for determining one of the synchronous interactions and the asynchronous interaction supported by the requesting system.
5. 5. The method as claimed in claim 3, wherein the synchronous interaction corresponds to a blocking operation, and the asynchronous interaction corresponds to a non-blocking operation, wherein the blocking operation comprises waiting, by the requesting system, for a response before proceeding with other tasks, and the non-blocking operation comprises continuing, by the requesting system, with other operations without waiting for a response.
6. 6. The method as claimed in claim 1, wherein the configuring the FMS [101], by the analysis unit [106] at the FMS [101], to generate the response comprises one of: structuring the response for immediate transmission for the synchronous interaction, and preparing the response for later transmission for the asynchronous interaction.
7. 7. The method as claimed in claim 1, wherein the transmitting, by the transceiver unit [102], the generated response comprises one of: sending, by the transceiver unit [102], an immediate response for the synchronous interaction, and sending, by the transceiver unit [102], an acknowledgment when ready for the asynchronous interaction, aligning with the configured type of API interaction.
8. 8. A system [100] for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system (FMS) [101], the FMS [101] further comprising: a transceiver unit [102] configured to receive a request for interaction from a requesting system, the requesting system comprising at least one of a northbound interface (NBI) system [202] and a third-party system; a determination unit [104] connected at least to the transceiver unit [102], the determination unit [104] configured to determine a type of application programming interface (API) interaction supported by the requesting system based on the received request, wherein the type of API interaction is one of a synchronous interaction and an asynchronous interaction; an analysis unit [106] connected at least to the determination unit [104], the analysis unit [106] configured to configure the FMS [101] to generate a response based on the determined type of API interaction; and the transceiver unit [102] further configured to transmit the generated response to the requesting system based on the determined type of API interaction.
9. 9. The system [100] as claimed in claim 8, wherein the request is one of a call type requests or a command type request.
10. 10. The system [100] as claimed in claim 9, wherein the one of the call type requests and the command type request is associated with performing a set of tasks on a data in the FMS [101].
11. 11. The system [100] as claimed in claim 8, wherein for determining the type of API interaction, the analysis unit [106] is configured to analyse the request for determining one of the synchronous interactions or the asynchronous interaction supported by the requesting system.
12. 12. The system [100] as claimed in claim 10, wherein the synchronous interaction corresponds to a blocking operation and the asynchronous interaction corresponds to a non-blocking operation, wherein the blocking operation comprises waiting, by the requesting system, for a response before proceeding with other tasks, and the non-blocking operation comprises continuing, by the requesting system, with other operations without waiting for a response.
13. 13. The system [100] as claimed in claim 8, wherein the analysis unit [106] for configuring the FMS [101], is configured to perform one of: structuring the response for immediate transmission for the synchronous interaction, and preparing the response for later transmission for the asynchronous interaction.
14. 14. The system [100] as claimed in claim 8, wherein the transceiver unit [102], for transmitting the generated response, is configured to perform one of: sending an immediate response for the synchronous interaction, and sending an acknowledgement when ready for the asynchronous interaction, aligning with the configured type of API interaction.
15. 15. A user equipment (UE) [502] for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system (FMS) [101], said UE [502] comprising: a processor configured to: transmit a request for interaction to a requesting system, the requesting system comprising at least one of a northbound interface (NBI) system [202] and a third-party system; determine a type of application programming interface (API) interaction supported by the requesting system based on the request, wherein the type of API interaction is one of a synchronous interaction and an asynchronous interaction; configure the FMS [101] to generate a response based on the determined type of API interaction; and receive the generated response from the requesting system based on the determined type of API interaction.
16. 16. A non-transitory computer-readable storage medium storing instruction for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system (FMS) [101], the storage medium comprising executable code which, when executed by one or more units of a system, causes: a transceiver unit [102] to receive a request for interaction from a requesting system, the requesting system comprising at least one of a northbound interface (NBI) system [202] and a third-party system; a determination unit [104] connected at least to the transceiver unit [102], the determination unit [104] to determine a type of application programming interface (API) interaction supported by the requesting system based on the received request, wherein the type of API interaction is one of a synchronous interaction and an asynchronous interaction; an analysis unit [106] connected at least to the determination unit [104], the analysis unit [106] to configure the FMS [101] to generate a response based on the determined type of API interaction; and the transceiver unit [102] to further transmit the generated response to the requesting system based on the determined type of API interaction.

Description

SYSTEM AND METHOD FOR CONFIGURING SYNCHRONOUS AND AN ASYNCHRONOUS RESPONSE MECHANISM IN FUEFIEMENT MANAGEMENT SYSTEM FIEED OF THE DISCEOSURE [0001] The present disclosure relates generally to the field of wireless communication systems. In particular, the present disclosure relates to application programming interface (API) communication and interaction mechanisms. More particularly, the present disclosure relates to system and method for configuring a synchronous response mechanism and an asynchronous response mechanism in a 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 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 show incompatibility with other systems. If one system uses only synchronous APIs and another system uses only asynchronous APIs, there might be compatibility issues when they try to interact with each other. The systems might not be able to communicate effectively because they are designed to handle requests and responses differently. Synchronous APIs can be less efficient than asynchronous ones, especially for complex or timeconsuming operations. When a request is made using a synchronous API, the client must wait for the response before it can continue processing. This "blocking" nature can lead to inefficient usage of resources, especially if the server takes a long time to respond. Asynchronous APIs allow the client to continue processing while waiting for the server's response. While this approach can be more efficient, it also introduces complexity because the client must be able to handle the response whenever it arrives. Further, for traditional systems, each time a system needs to interact with a new interface or third-party system, developers might need to write custom code to accommodate the specific sync or async API requirements of that system. This increases development time and effort. Furthermore, for existing systems, if a system only supports synchronous APIs, it might struggle to scale because each active request ties up resources until the response is received. On the other hand, while asynchronous APIs can help with scalability, they come with their own challenges in managing and coordinating responses, which can get more complex as the system scales up. [0005] Thus, there exists an imperative need in the art for configuring a synchronous response mechanism and an asynchronous response mechanism to provide an improved compatibility, efficiency, and scalability, while also reducing development and integration effort. The present disclosure aims to address this solution. OBJECTS OF THE PRESENT 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 an object of the present disclosure to provide a system and method for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system. [0008] It is another object of the present disclosure to provide a system and method for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system that offers flexibility in API interactions. The system is designed to support both sync and async API calls, which can adapt to different interfaces and third-party systems, irrespective of whether they support sync or async interactions. [0009] It is another object of the present disclosure to provide a system and a method for configuring a synchronous response mechanism and an as