Description:
FORM-2
THE PATENTS ACT, 1970 (39 OF 1970)
&
The Patents Rules, 2003
COMPLETE SPECIFICATION
[See section 10 and rule 13]

"MULTI-CHANNEL COMMUNICATION SYSTEM AND METHOD THEREOF”

Name: ACL Mobile Limited
Nationality: Indian
Address: 7th Floor, Tower-4, Express Trade Towers 2, B-36, Sector-132, Noida – 201 301

The following specification particularly describes the invention and the manner in which it is to be performed.

MULTI-CHANNEL COMMUNICATION SYSTEM AND METHOD THEREOF

FIELD OF THE INVENTION
The present invention relates to the field of communication systems, and more particularly, the present invention relates to a multi-channel communication system and method thereof which connects with multiple service providers and various departments of an enterprise via unified API and helps route messages traffic to multiple service providers as per enterprise requirements.

BACKGROUND FOR THE INVENTION:
The following discussion of the background to the invention is intended to facilitate an understanding of the present invention. However, it should be appreciated that the discussion is not an acknowledgment or admission that any of the material referred to was published, known, or part of the common general knowledge in any jurisdiction as of the priority date of the application. The details provided herein the background if belongs to any publication is taken only as a reference for describing the problems, in general terminologies or principles or both of science and technology in the associated prior art.
As estimating traffic in real-time is impossible by estimating total traffic and then trying to allocate quotas for each service provider. Distributing traffic globally in an application creates logistical issues and increases hardware costs. Also, it is observed that it can also have an impact on the TPS of the whole system. Sometimes, the network lag causes messages to get delayed and make distribution incorrect. Following are some of the problems prevalent in the prior art as disclosed in Figure 1.
Operational overhead of integrating multi – channel different vendors;
Operational overhead of integrating 3rd party or business partner platforms;
Decentralized management of vendor performance and KPIs;
Under or overutilized vendor bandwidth;
Manual switching of vendors;
Traffic loss or Message Failure;
Decentralized DLR handling; and
Billing & Reconciliation issues.
One of the cited prior art documents US2008176536A1 provides enterprise web service data to mobile device synchronization that discloses Mobile Enterprise Platform creates a web service synchronization source instance using Hypertext Transfer Protocol ("HTTP") for each application or database present on a plurality of mobile devices. Corresponding to each of these web service synchronization source instances is a web-based synchronization service associated with a specific backend enterprise resource. Each synchronization service is web based and can thus live anywhere on the network or on a dedicated services tie as they need only to supply a small set of operations to offer synchronization capability to a variety of mobile devices.
One of the cited prior art documents US7412486B1 discloses embodiments operate to receive a first message to be sent to a messaging client and establish a first connection to the messaging client. The system then transmits a message processing script and the first message over the first connection to the messaging client. The message processing script enables the messaging client to display the first message and to receive and display at least one second message over the first connection to the messaging client. The system maintains the first connection in an open state after transmitting the first message to the messaging client. The system then receives a second message to be sent to the messaging client and transmits the second message over the first connection to the messaging client for receipt by the message processing script, while continuing to maintain the first connection in an open state. This can be repeated for subsequent messages using the same connection.
In light of the foregoing, there is a need for the multi-channel communication system and method thereofthat overcomes problems prevalent in the prior art.

OBJECTS OF THE INVENTION:
Some of the objects of the present disclosure, which at least one embodiment herein satisfies, are as follows.
The principal object of the present invention is to overcome the disadvantages of the prior art by providing the multi-channel communication system and method thereof.
An object of the present invention is to provide the multi-channel communication system and method thereof which connects with multiple service providers and various departments of an enterprise via unified API.
Another object of the present invention is to provide the multi-channel communication system and method thereof helps route messages traffic to multiple service providers as per enterprise requirements.
Another object of the present invention is to provide the multi-channel communication system and method thereof that tries to distribute traffic locally and is done for each message.
Another object of the present invention is to provide the multi-channel communication system and method thereof, wherein processing power and hardware requirement doesn't significantly increase due to calculation, so this is cost effective and all enterprise need to do is put vendor in ration they traffic to be distributed.
Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.

SUMMARY OF THE INVENTION:
The present invention provides a multi-channel communication system and method thereof. The system connects with multiple service providers and various departments of an enterprise via unified API. The system helps route messages traffic to multiple service providers as per enterprise requirements. The system tries to distribute traffic locally and is done for each message. It is noted that processing power and hardware requirement doesn't significantly increase due to calculation, so this is cost effective and all enterprise need to do is put vendor in ration they traffic to be distributed.
According to an exemplary non limiting implementation of the present invention, the system includes a plurality of vendors, each configured with a vendor-end electronic device embedded with a first data transferring and receiving device, a plurality of enterprise source systems, each configured with an enterprise-end device embedded with a second data transferring and receiving device for generating a server-based communication request with an electronic message to at least one vendor-end electronic device over a network through a database and an HTTP/HTTPS interface, a processor in communication with a server.
According to an embodiment of the present invention, the processor includes a publishing module, a dispatching module, a DLR module, a MIS queue, and MIS processor module.
According to an embodiment of the present invention, the publishing module is adapted to perform the following tasks:
receiving the generated request from the enterprise-end device;
validating the received request;
rejecting the request with an error message, in case validation is found faulty;
sending back a response message to the request received to an enterprise-end device, in case the validation is successful; and
segregating and sending the validated message to different queue modules comprising a one-time password (OTP) module, a non-one-time password (OTP) module, an in-app messaging module; a broadcast module, an email module, a social media module at a same time or at predefined timeline.
According to an embodiment of the present invention, the dispatching module is adapted to distribute the requests among selected vendors from a predefined vendor list. The DLR module is adapted to receive a delivery status report from the plurality of vendors on HTTPS interface and submitting to the MIS queue. The MIS queue module is adapted to store data received from the DLR module. The MIS processor module is adapted to persist the data into a database picked from the MIS queue module and inserting to MIS table and DLR table respectively.
According to an embodiment of the present invention, the dispatching module is adapted to perform following sub-steps:
(f1) receiving the data from the respective queue module;
(f2) selecting a vendor from the plurality of vendors; and
(f3) submitting a request to the selected vendors.
The proposed invention also provides a method for multi-channel communication, the method includes steps of (a) generating a server-based communication request with an electronic message to at least one vendor-end electronic device over a network through a database and an HTTP/HTTPS interface, (b) receiving the generated request from the enterprise-end device, (c) validating the received request,(d1) rejecting the request with an error message, in case validation is found faulty,(d2) sending back a response message to the request received to an enterprise-end device, in case the validation is successful, (e) segregating and sending the validated message to different queue modules comprising a one-time password (OTP) module, a non-one-time password (OTP) module, an in-app messaging module; a broadcast module, an email module, a social media module at a same time or at predefined timeline,(f) distributing the requests among selected vendors from a predefined vendor list, (g) receiving a delivery status report from the plurality of vendors on HTTPS interface and submitting to the MIS queue, (h) storing data received from the DLR module, and(i) persisting the data into a database picked from the MIS queue module and inserting to MIS table and DLR table respectively.
According to an embodiment of the present invention, thestep (f) includes sub-steps of(f1) receiving the data from the respective queue module, (f2) selecting a vendor from the plurality of vendors, and (f3) submitting a request to the selected vendors.

BRIEF DESCRIPTION OF DRAWINGS:
Reference will be made to embodiments of the invention, examples of which may be illustrated in accompanying figures. These figures are intended to be illustrative, not limiting. Although the invention is generally described in the context of these embodiments, it should be understood that it is not intended to limit the scope of the invention to these particular embodiments.
Figure 1 shows a prior art communication system; and
Figure 2 shows the proposed a multi-channel communication system.

DETAILED DESCRIPTION OF DRAWINGS:
While the present invention is described herein by way of example using embodiments and illustrative drawings, those skilled in the art will recognize that the invention is not limited to the embodiments of drawing or drawings described and are not intended to represent the scale of the various components. Further, some components that may form a part of the invention may not be illustrated in certain figures, for ease of illustration, and such omissions do not limit the embodiments outlined in any way. It should be understood that the drawings and the detailed description thereto are not intended to limit the invention to the particular form disclosed, but on the contrary, the invention is to cover all modifications, equivalents, and alternatives falling within the scope of the present invention as defined by the appended claim.
As used throughout this description, the word "may" is used in a permissive sense (i.e. meaning having the potential to), rather than the mandatory sense, (i.e. meaning must). Further, the words "a" or "an" mean "at least one” and the word “plurality” means “one or more” unless otherwise mentioned. Furthermore, the terminology and phraseology used herein are solely used for descriptive purposes and should not be construed as limiting in scope. Language such as "including," "comprising," "having," "containing," or "involving," and variations thereof, is intended to be broad and encompass the subject matter listed thereafter, equivalents, and additional subject matter not recited, and is not intended to exclude other additives, components, integers, or steps. Likewise, the term "comprising" is considered synonymous with the terms "including" or "containing" for applicable legal purposes. Any discussion of documents, acts, materials, devices, articles, and the like are included in the specification solely for the purpose of providing a context for the present invention. It is not suggested or represented that any or all these matters form part of the prior art base or were common general knowledge in the field relevant to the present invention.
In this disclosure, whenever a composition or an element or a group of elements is preceded with the transitional phrase “comprising”, it is understood that we also contemplate the same composition, element, or group of elements with transitional phrases “consisting of”, “consisting”, “selected from the group of consisting of, “including”, or “is” preceding the recitation of the composition, element or group of elements and vice versa.
The present invention is described hereinafter by various embodiments with reference to the accompanying drawing, wherein reference numerals used in the accompanying drawing correspond to the like elements throughout the description. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiment set forth herein. Rather, the embodiment is provided so that this disclosure will be thorough and complete and will fully convey the scope of the invention to those skilled in the art. In the following detailed description, numeric values and ranges are provided for various aspects of the implementations described. These values and ranges are to be treated as examples only and are not intended to limit the scope of the claims. In addition, several materials are identified as suitable for various facets of the implementations. These materials are to be treated as exemplary and are not intended to limit the scope of the invention.
The present invention provides a multi-channel communication system and method thereof. The system connects with multiple service providers and various departments of an enterprise via unified API. The system helps route messages traffic to multiple service providers as per enterprise requirements. The system tries to distribute traffic locally and is done for each message. It is noted that processing power and hardware requirement doesn't significantly increase due to calculation, so this is cost effective and all enterprise need to do is put vendor in ration they traffic to be distributed.
The present invention provides a multi-channel communication system and method thereof. The system connects with multiple service providers and various departments of an enterprise via unified API. The system helps route messages traffic to multiple service providers as per enterprise requirements. The system tries to distribute traffic locally and is done for each message. It is noted that processing power and hardware requirement doesn't significantly increase due to calculation, so this is cost effective and all enterprise need to do is put vendor in ration they traffic to be distributed.
From herein afterwards the multi-channel communication system is to referred as a system.
According to an exemplary non limiting implementation of the present invention, the system includes a plurality of vendors and a plurality of enterprise source systems.Each vendor is configured with a vendor-end electronic device. The vendor-end electronic device is embedded with a first data transferring and receiving device.Each enterprise source system is configured with an enterprise-end device embedded with a second data transferring and receiving device for generating a server-based communication request with an electronic message to at least one vendor-end electronic device over a network through a database and an HTTP/HTTPS interface. The processor is in communication with a server. The electronic device includes a mobile phone, a laptop computer, a personal computer, a tablet computer, a smartwatch, or any other Internet of Things based electronic device embedded with an android, an iOS operating system or web-based operating system. The electronic device is provided with a user interface (basically a software module for hardware interface modules), a display module and an input module. The display module includes a monitor, and any other electronic display module. The input module may include a keyboard, a keypad, a touch screen, a smart pencil, a voice command system, etc.
The data transmitting and receiving module is configured to send and receive data over a wireless network. The wireless network includes an internet, a wi-fi module, a frequency waves-based data sharing module such as Bluetooth, or a satellite-based data sharing module, etc. The processor is in communication with the server-based computing system, web server, cloud storage or database, and electronic device. The processor may be a processor, a microprocessor, a computer, a microcomputer, a controller or a microcontroller. Referring now to Figure 2, the processor includes a publishing module, a dispatching module, a DLR module, a MIS queue, and MIS processor module.
According to an embodiment of the present invention, the publishing module is adapted to perform the following tasks:
receiving the generated request from the enterprise-end device;
validating the received request;
rejecting the request with an error message, in case validation is found faulty;
sending back a response message to the request received to an enterprise-end device, in case the validation is successful; and
segregating and sending the validated message to different queue modules comprising a one-time password (OTP) module, a non-one-time password (OTP) module, an in-app messaging module; a broadcast module, an email module, a social media module at a same time or at predefined timeline.
According to an embodiment of the present invention, the dispatching module is adapted to distribute the requests among selected vendors from a predefined vendor list. The DLR module is adapted to receive a delivery status report from the plurality of vendors on HTTPS interface and submitting to the MIS queue. The MIS queue module is adapted to store data received from the DLR module. The MIS processor module is adapted to persist the data into a database picked from the MIS queue module and inserting to MIS table and DLR table respectively.
According to an embodiment of the present invention, the dispatching module is adapted to perform following sub-steps:
(f1) receiving the data from the respective queue module;
(f2) selecting a vendor from the plurality of vendors; and
(f3) submitting a request to the selected vendors.
The proposed invention also provides a method for multi-channel communication, the method includes steps of (a) generating a server-based communication request with an electronic message to at least one vendor-end electronic device over a network through a database and an HTTP/HTTPS interface, (b) receiving the generated request from the enterprise-end device, (c) validating the received request,(d1) rejecting the request with an error message, in case validation is found faulty,(d2) sending back a response message to the request received to an enterprise-end device, in case the validation is successful, (e) segregating and sending the validated message to different queue modules comprising a one-time password (OTP) module, a non-one-time password (OTP) module, an in-app messaging module; a broadcast module, an email module, a social media module at a same time or at predefined timeline,(f) distributing the requests among selected vendors from a predefined vendor list, (g) receiving a delivery status report from the plurality of vendors on HTTPS interface and submitting to the MIS queue, (h) storing data received from the DLR module, and (i) persisting the data into a database picked from the MIS queue module and inserting to MIS table and DLR table respectively.
According to an embodiment of the present invention, the step (f) includes sub-steps of (f1) receiving the data from the respective queue module, (f2) selecting a vendor from the plurality of vendors, and (f3) submitting a request to the selected vendors.
The present invention provides an advantage of providing the multi-channel communication system and method thereof. The system connects with multiple service providers and various departments of an enterprise via unified API. The system helps route messages traffic to multiple service providers as per enterprise requirements. The system tries to distribute traffic locally and is done for each message. It is noted that processing power and hardware requirement doesn't significantly increase due to calculation, so this is cost effective and all enterprise need to do is put vendor in ration they traffic to be distributed.
The disclosure has been described with reference to the accompanying embodiments herein and the various features and advantageous details thereof are explained with reference to the non-limiting embodiments in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein.
The foregoing description of the specific embodiments so fully revealed the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the scope of the embodiments as described herein.

, Claims:A multi-channel communication system, the system comprising:
a plurality of vendors, each configured with a vendor-end electronic device embedded with a first data transferring and receiving device;
a plurality of enterprise source systems, each configured with an enterprise-end device embedded with a second data transferring and receiving devicefor (a) generating a server-based communication request with an electronic message to at least one vendor-end electronic device over a network through a database and an HTTP/HTTPS interface;
a processor in communication with a server; the processor comprising:
a publishing module adapted to perform: (b) receiving the generated request from the enterprise-end device; (c) validating the received request; and(e) segregating and sending the validated message to different queue modules comprisinga one-time password (OTP) module, a non-one-time password (OTP) module, an in-app messaging module; a broadcast module, an email module, a social media module at a same time or at predefined timeline;
a dispatching module adapted to perform: (f) distributing the requests among selected vendors from a predefined vendor list;
a DLR module adapted to perform:(g) receiving a delivery status report from the plurality of vendors on HTTPS interface and submitting to the MIS queue;
a MIS queue module adapted to perform: (h) storing data received from the DLR module; and
MIS processor module adapted to perform:(i) persisting the data into a database picked from the MIS queue module and inserting to MIS table and DLR table respectively.

The system as claimed in claim 1, wherein the publishing module adapted to perform an additional step of: (d1) rejecting the request with an error message, in case validation is found faulty.

The system as claimed in claim 1, wherein the publishing module adapted to perform an additional step of: (d2) sending back a response message to the request received to an enterprise-end device, in case the validation is successful.

The system as claimed in claim 1, wherein the dispatching module adapted to perform sub-steps of: (f1) receiving the data from the respective queue module; (f2) selecting a vendor from the plurality of vendors; and (f3) submitting a request to the selected vendors.

The system as claimed in claim 1, wherein the system comprises a broadcast management module adapted to allow an authorized user to create new groups of vendors in the system to segment the target audience for one or more than one broadcasts.

The system as claimed in claim 5, wherein the broadcast management module is also adapted to manage existing broadcasts(edit and delete).

A method for multi-channel communication, the method comprising steps of:
(a) generating a server-based communication request with an electronic message to at least one vendor-end electronic device over a network through a database and an HTTP/HTTPS interface;
(b) receiving the generated request from the enterprise-end device;
(c) validating the received request;
(e) segregating and sending the validated message to different queue modules comprising a one-time password (OTP) module, a non-one-time password (OTP) module, an in-app messaging module; a broadcast module, an email module, a social media module at a same time or at predefined timeline;
(f) distributing the requests among selected vendors from a predefined vendor list;
(g) receiving a delivery status report from the plurality of vendors on HTTPS interface and submitting to the MIS queue;
(h) storing data received from the DLR module; and
(i) persisting the data into a database picked from the MIS queue module and inserting to MIS table and DLR table respectively.

The method as claimed in claim 7, wherein the method includes an additional step of: (d1) rejecting the request with an error message, in case validation is found faulty.

The method as claimed in claim 7, wherein the method includes an additional step of: (d2) sending back a response message to the request received to an enterprise-end device, in case the validation is successful.

The method as claimed in claim 7, wherein the step (f) includes sub-steps of:
(f1) receiving the data from the respective queue module;
(f2) selecting a vendor from the plurality of vendors; and
(f3) submitting a request to the selected vendors.