DESC:TECHNICAL FIELD
[0001] The present disclosure relates to the field of mass transportation system. More particularly the present disclosure relates to a system for interfacing one or more field equipment (FE) devices and one or more operational control command (OCC) units manufactured by different original equipment manufacturers (OEMs).

BACKGROUND
[0002] Background description includes information that may be useful in understanding the present invention. It is not an admission that any of the information provided herein is prior art or relevant to the presently claimed invention, or that any publication specifically or implicitly referenced is prior art.
[0003] The mass transportation system (MTS) such as rail transportation is an interconnected network of wide variety systems such as Interlocking systems (IS), train control systems (TCS) and other external systems (ES) like passenger information display system (PIDS), Tunnel ventilation System (TVS), and many more. These equipment’s and systems are collectively termed as field equipment (FE) devices. The operational functionality of any rail transportation systems is mainly dependent on the efficient exchange of information between FEs and operational command control (OCC) system.
[0004] Generally, most of the FEs are manufactured and supplied by different original equipment manufacturers (OEMs) and there is no standardization of the interface specification available as such for information exchange and sharing. Because of diversity of OEMs, the FEs have different communication interfaces, protocols, data primitives and control command directives and the integration of data from these systems becomes challenging for system designers and developers. The availability of non-standard and paper-based formats lead to misinterpretation and inaccurate conversion of data. Existing system is that the FE from a particular OEMs cannot communicate with OCC from a different OEMs as the proprietary protocol of both the OEMs are different and non-standardized.
[0005] There is, therefore, a need of system that can efficiently interface field equipment devices made from one OEM to operations control command unit made by another OEM.

OBJECTS OF THE PRESENT DISCLOSURE
[0006] Some of the objects of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.
[0007] It is an object of the present disclosure to provide a system for interfacing one or more field equipment (FE) devices with one or more operational control command (OCC) units that is more efficient in interoperability of multiple mass transportation system.
[0008] It is an object of the present disclosure to provide a system for interfacing one or more field equipment (FE) devices with one or more operational control command (OCC) units that is more reliable in interoperability of multiple mass transportation system.
[0009] It is an object of the present disclosure to provide a system for interfacing one or more field equipment (FE) devices with one or more operational control command (OCC) units that overcomes dependencies on the different OEMs.
[0010] It is an object of the present disclosure to provide a system for interfacing one or more field equipment (FE) devices with one or more operational control command (OCC) units that is cost-effective and simple to use.
[0011] It is an object of the present disclosure to provide a system that enables operation flexibility, optimized inventory management, permits scalability on any line as well as platform and ease of configuration of network specifications.
[0012] It is an object of the present disclosure to provide a system that provides integration with standard industry-specific data models.

SUMMARY
[0013] The main objective of the present disclosure is to solve the technical problem as recited above by providing a system that can efficiently interface field equipment devices made from one OEM to operations control command unit made by another OEM. The present disclosure aims at standardizing interfaces and data formats to achieve interoperability among different subsystems in the rail network, thereby simplifying the data exchange and the processing of information.
[0014] The proposed method provides a standard representation of the information contained in the interface control documents and provides the solution for standardized exchange of information to support both designing phases and real-time operations. The solution enables interoperability between different components, equipment and system of batch processing for various OEMs. This shall provide sharing of information of rakes, radios and spare components among different lines thereby optimizing the utility of resources in running as well as preventive maintenance conditions.
[0015] The system of the present disclosure aims at interfacing one or more field equipment (FE) devices with one or more operational control command (OCC) units that are efficient and reliable in interoperability of multiple mass transportation system. The system overcomes dependencies on the different OEMs. The system and method of the proposed disclosure provide operation flexibility, where the data is standardized at the OCC, a single OCC can take control of the system with FEs from different OEMs. By achieving operational flexibility and interoperability, the use of any vendor’s equipment is possible hence the cost can be curbed.
[0016] Due to the standardization of OCC interface specification, and flexible encoding of field equipment specification, inventory management becomes easier and more flexible. Due to the availability of the proposed approach, too much inventory of OEM specific equipment is not required. Hence in comparison to traditional inventory management, a significant cost of assets would be reduced. The system provides integration with standard industry-specific data models, where many vendors which work with many industry standards and define specific information models for their solutions are integrated thereby providing standardization. The XML file needs to be changed/updated in order to add/remove/update the equipment specifications of a line a rail network thereby permitting scalability on any line as well as the platform. The proposed method enables the easy configuration of network specifications thereby helps in establishing network connections in between diverse hardware platforms i.e., from different OEM in very less or no time. The standardization of information removes inefficiency due to misinterpretation and conversion of data from non-standard, often paper-based formats.
[0017] An aspect of the present disclosure pertains to a system for interfacing one or more field equipment (FE) devices with one or more operational control command (OCC) units of a mass transportation system. The system includes a processing unit, operatively configured with the one or more FE devices and the one or more OCC units, having one or more processors configured to execute a set of instructions stored in a memory, which, on execution, causes the system to receive, from the one or more FE devices, a set of first information pertaining to one or more parameters of the mass transportation system. Each of the set of first information is received on corresponding one or more first interface protocols. The one or more first information is in a first format, transform, using a knowledge repository, the first format of the set of first information into a second format. The second format is compatible with each of the one or more OCC units, and transmit, to the one or more OCC units, the set of first information in the second format. The set of first information in the second format is transmitted on a second interface protocol.
[0018] In an aspect, the one or more parameters may comprise any or combination of location and speed of plurality of vehicles associated with the mass transportation system, signals status, route details, passenger information, and tunnel ventilation status. Transforming the first format of the set of first information into the second format may be performed using any or combination of a bit mapping, unit conversion, and data conversion technique. The first format may be non-standard format, and the one or more first protocols may be non-standard proprietary interface protocols associated with the one or more FE devices. The knowledge repository may comprise data related to conversion the non-standard proprietary interface protocols into a machine-readable format. The second format may be a standard format, and the second protocol may be a mass transportation standard specific protocol.
[0019] In an aspect, the system may be configured to receive, from the one or more OCC unit, a set of second information pertaining to one or more control parameters of the mass transportation system. The set of second information is received on the second interface protocol. Transform, using the knowledge repository, the second format of the set of second information into the first format, and transmit, to the one or more FE devices, the set of second information in the first format. The set of second information in the first format is transmitted on the one or more first interface protocols. The one or more control parameters may comprise any or combination of time table scheduling, and route scheduling of the one or more vehicles.
[0020] Various objects, features, aspects and advantages of the inventive subject matter will become more apparent from the following detailed description of preferred embodiments, along with the accompanying drawing figures in which like numerals represent like components.

BRIEF DESCRIPTION OF DRAWINGS
[0021] The accompanying drawings are included to provide a further understanding of the present disclosure, and are incorporated in and constitute a part of this specification. The drawings illustrate exemplary embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure. The diagrams are for illustration only, which thus is not a limitation of the present disclosure.
[0022] In the figures, similar components and/or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label with a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.
[0023] FIG. 1A illustrates an exemplary network architecture in which or with which proposed system for interfacing one or more FE devices with one or more OCC units in mass transportation system, in accordance with an embodiment of the present disclosure.
[0024] FIG. 1B illustrates an exemplary method of generating a knowledge repository to be used by the system for interfacing one or more FE devices with one or more OCC units in mass transportation system, in accordance with an embodiment of the present disclosure.
[0025] FIG. 1C illustrates an exemplary process of encoding of proprietary ICD into machine readable format, in accordance with an embodiment of the present disclosure.
[0026] FIG. 1D illustrates an exemplary framework for standardized data exchange for command/response, in accordance with an embodiment of the present disclosure.
[0027] FIG. 1E illustrates an exemplary standardization of data at OCC interface, in accordance with an embodiment of the present disclosure.
[0028] FIG. 2 illustrates an exemplary module diagram of the system for interfacing one or more FE devices with one or more OCC units in mass transportation system, in accordance with an embodiment of the present disclosure.
[0029] FIG. 3 illustrates an exemplary method for interfacing one or more FE devices with one or more OCC units in mass transportation system, in accordance with an embodiment of the present disclosure.
[0030] FIG. 4 illustrates computer system in which or with which embodiments of the present invention can be utilized, in accordance with embodiments of the present disclosure.

DETAILED DESCRIPTION
[0031] The following is a detailed description of embodiments of the disclosure depicted in the accompanying drawings. The embodiments are in such detail as to clearly communicate the disclosure. However, the amount of detail offered is not intended to limit the anticipated variations of embodiments; on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the scope of the present disclosure as defined by the appended claims.
[0032] In the following description, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present invention. It will be apparent to one skilled in the art that embodiments of the present invention may be practiced without some of these specific details.
[0033] The present disclosure relates to the field of mass transportation system. More particularly the present disclosure relates to a system for interfacing one or more field equipment (FE) devices and one or more operational control command (OCC) units manufactured by different original equipment manufacturers (OEMs). The system and method of the present disclosure enable to overcome the limitations of the prior art by efficiently interfacing field equipment devices made from one OEM to operations control command unit made by another OEM.
[0034] The present disclosure elaborates upon a system for interfacing one or more field equipment (FE) devices with one or more operational control command (OCC) units of a mass transportation system. The system includes a processing unit, operatively configured with the one or more FE devices and the one or more OCC units, having one or more processors configured to execute a set of instructions stored in a memory, which, on execution, causes the system to receive, from the one or more FE devices, a set of first information pertaining to one or more parameters of the mass transportation system. Each of the set of first information is received on corresponding one or more first interface protocols. The one or more first information is in a first format, transform, using a knowledge repository, the first format of the set of first information into a second format. The second format is compatible with each of the one or more OCC units, and transmit, to the one or more OCC units, the set of first information in the second format. The set of first information in the second format is transmitted on a second interface protocol.
[0035] The system receives from the one or more OCC unit a set of second information pertaining to one or more control parameters of the mass transportation system. The set of second information is received on the second interface protocol. The second format of the set of second information is transformed into the first format and transmit, to the one or more FE devices, the set of second information in the first format, wherein the set of second information in the first format is transmitted on the one or more first interface protocols.
[0036] The present disclosure aims at interfacing one or more field equipment (FE) devices with one or more operational control command (OCC) units that are efficient and reliable in the interoperability of multiple mass transportation system. The system overcomes dependencies on the different OEMs. The system and method of the proposed disclosure provide operation flexibility, where the data is standardized at the OCC, a single OCC can take control of the system with FEs from different OEMs. By achieving operational flexibility and interoperability, the use of any vendor’s equipment is possible hence the cost can be curbed. Due to the standardization of OCC interface specification, and flexible encoding of field equipment specification, inventory management becomes easier and more flexible. Due to the availability of the proposed approach, too much inventory of OEM specific equipment is not required. Hence in comparison to traditional inventory management, a significant cost of assets can be reduced.
[0037] The system provides integration with standard industry-specific data models, where many vendors which work with many industry standards and define specific information models for their solutions are integrated thereby providing standardization. The XML file needs to be changed/updated in order to add/remove/update the equipment specifications of a line a rail network thereby permitting scalability on any line as well as the platform.
[0038] The proposed method enables the easy configuration of network specifications thereby helping in establishing network connections in between diverse hardware platforms i.e., from different OEMs in very less or no time. The standardization of information removes inefficiency due to misinterpretation and conversion of data from non-standard, often paper-based formats. The description of terms and features related to the present disclosure shall be clear from the embodiments that are illustrated and described; however, the invention is not limited to these embodiments only. Numerous modifications, changes, variations, substitutions, and equivalents of the embodiments are possible within the scope of the present disclosure. Additionally, the invention can include other embodiments that are within the scope of the claims but are not described in detail with respect to the following description.
[0039] FIG. 1A illustrates an exemplary network architecture in which or with which proposed system for interfacing one or more FE devices with one or more OCC units in mass transportation system, in accordance with an embodiment of the present disclosure.
[0040] FIG. 1B illustrates an exemplary method of generating a knowledge repository to be used by the system for interfacing one or more FE devices with one or more OCC units in mass transportation system, in accordance with an embodiment of the present disclosure.
[0041] As illustrated, in a network implementation 100, a system 102 for interfacing one or more FE devices with one or more OCC units in mass transportation system can be communicatively coupled with plurality of operational control command units (OCC) devices 108-1, 108-2…108-N (collectively referred to as operational control command units 108 and individually referred to as operational control command unit 108 hereinafter) through network 104. The system 102 can be implemented using any or a combination of hardware components and software components such as a server or database 106, a computing system, a computing device, a security device and the like.
[0042] Further, the system 102 can interface with one or a plurality of field equipment devices 110-1, 110-2…110-N (collectively referred to as field equipment devices 110, and individually referred to as field equipment devices 110 hereinafter), through the client network 104. The plurality of field equipment devices 110 (also referred as one or more field equipment devices 110, herein) and the plurality of operational commence control units 108 (also referred as one or more operational commence control units 108, herein) can be manufactured by different or a plurality of original equipment manufacturers (OEM). Each of the plurality of the field equipment devices 110 can include a nonstandard or proprietary interface protocol for transferring information. In an implementation, the system 102 can be accessed by applications residing on any operating system, including but not limited to, AndroidTM, iOSTM, and the like. In a preferred embodiment, the second client devices 112 are associated with respective second entities 108.
[0043] In an embodiment, the system 102 can be configured to receive, from the one FE devices 110, a set of first information pertaining to one or more parameters of the mass transportation system. The one or more parameters can include but without limiting to location and speed of plurality of vehicles associated with the mass transportation system, signals status, route details, passenger information, and tunnel ventilation status. Each of the set of first information can be received on respective or corresponding nonstandard or proprietary protocol (also referred as first interface protocol, herein) of the plurality of field equipment devices 110. The one or more first information can be in a first format that can be un-structured and nonstandard.
[0044] In an embodiment, the first format of the set of first information can be transformed into a second format that can be structured. The transformation of the first format of the set of first information into the second format can be performed using any or combination of a bit mapping, unit conversion, and data conversion technique. The transformation can be performed by using a knowledge repository that can further include data related to conversion of the non-standard proprietary interface protocols into a machine-readable format. The second format can be compatible with each of the one or more OCC units 108.
[0045] In an embodiment, as shown in FIG. 1B, the knowledge repository can be formed manually by any system designer, route planner and manager for train operations based on respective interface control documents provided with each of the one or more field equipment devices 110 by the respective manufacturer and domain knowledge of experts. The information from the created knowledge repository is encoded into machine readable format such as extensible markup language (XML) shown in FIG. 1C. The XML format can be used for encoding as it is an open-source data structure that has been developed to simplify the transfer of data between various railroad simulations and operations computer programs. XML based data encoding can substantially reduce time in creating specialized applications such as for railroads and transmit, to the one or more OCC units, the set of first information in the second format.
[0046] In an embodiment, the second format can be compatible with each of the one or more OCC units 108 and can be transmitted to any of the one or more OCC unit 108. The one or more first information in the second format can be transmitted to any of the one or more OCC unit 108 using a standard specific protocol (also referred as second interface protocol, herein).
[0047] In an embodiment, the system 102 can be configured to receive, from the one or more OCC units 108 a set of second information pertaining to one or more control parameters of the mass transportation system. The one or more control parameters can comprise any or combination of time table scheduling, and route scheduling of the one or more vehicles. The set of second information can be received on the second interface protocol. The received second information can be transformed, using the knowledge repository, the second format of the set of second information into the first format. Further, the set of second information in the first format can be transmitted, to the one or more FE devices 110 on the one or more first interface protocols.
[0048] For example, the raw interface specifications of FEs as per their respective interface control documents (ICDs) from different OEMs is encoded into machine readable format. Formulating a knowledge base (KB) consisting FE ICD data in encoded format. The non-standardized/proprietary information from FEs of different OEMs is decoded and structured into structured data format using encoded KB. The structured data is standardized into interoperable format i.e., rail transportation specific standard input/output interface specification. Similarly, the method also takes the commands from the OCC unit 108 and follows the same path to route the standard data from the OCC 108 into FE 110 OEM specific proprietary format.
[0049] FIG. 1D illustrates an exemplary framework for standardized data exchange for command/response, in accordance with an embodiment of the present disclosure. Referring to FIG. 1D, the method receives the commands/responses from the configured OCC 108 and FEs 110. The proprietary information collected from FEs 110 is pre-processed, validated and transformed into structured data format using meta-data contained in the encoded repository. The structured information is obtained post unit conversion and bit mapping. The structured information is further converted into standardized data format for interoperable usage of the OCC 108.
[0050] For the reverse path, the standardized information from the OCC 108 received in real-time and converted into the proprietary format as per the ICDs of FEs. As a response of the received command, the method receives the response from the external field equipment 110 in a non-standardized OEM specific data format. The interfaces allow efficient data exchange between software components provided by different manufacturers. The flow of information between FEs 110 and OCC 108 interface is depicted in FIG. 1E.
[0051] FIG. 2 illustrates an exemplary module diagram of the system for interfacing one or more FE devices with one or more OCC units in mass transportation system, in accordance with an embodiment of the present disclosure.
[0052] In an aspect, module diagram 200 of the system 102 can comprise one or more processor(s) 202. The one or more processor(s) 202 can be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that manipulate data based on operational instructions. Among other capabilities, the one or more processor(s) 202 are configured to fetch and execute computer-readable instructions stored in a memory 204 of the system 102. The memory 204 can store one or more computer-readable instructions or routines, which can be fetched and executed to create or share the data units over a network service. The memory 204 can comprise any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as EPROM, flash memory, and the like.
[0053] The system 102 can also comprise an interface(s) 206. The interface(s) 206 can comprise a variety of interfaces, for example, interfaces for data input and output devices, referred to as I/O devices, storage devices, and the like. The interface(s) 206 can facilitate communication of system 102. The interface(s) 206 can also provide a communication pathway for one or more components of the system 102. Examples of such components include, but are not limited to, processing engine(s) 208 and data 210. For example,
[0054] The processing engine(s) 208 can be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) 208. In examples described herein, such combinations of hardware and programming can be implemented in several different ways. For example, the programming for the processing engine(s) 208 can be processor executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine(s) 208 can comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium can store instructions that, when executed by the processing resource, implement the processing engine(s) 208. In such examples, the system 102 can comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium can be separate but accessible to system 102 and the processing resource. In other examples, the processing engine(s) 208 can be implemented by electronic circuitry.
[0055] The database 210 can comprise data that is either stored or generated as a result of functionalities implemented by any of the components of the processing engine(s) 208 or the system 102.With reference to FIGs. 1A and 2, the present disclosure relates to a system for interfacing one or more FE devices with one or more OCC units in mass transportation system can include a receiving module 212 for receiving a set of first information in a first format, from the one or more field equipment devices 110. The set of first information can be received over one or more first protocols.
[0056] In an embodiment, the system can include a format conversion module 214 for operatively connected with the receiving module. The format conversion module can be used for converting the first format of the set of first information into a second format. The format conversion module 214 can received the set of first information from the receiving module 212 and can convert the first format into the second format.
[0057] In an embodiment, the system can include a transmitting module 216 operatively configured with the format conversion module. The transmitting module 216 can receive the set of first information in the second format from the format conversion module and can transmit the set of first information in the second format to the one or more field equipment devices 110 using the specific standard format.
[0058] FIG. 3 illustrates an exemplary method for interfacing one or more FE devices with one or more OCC units in mass transportation system, in accordance with an embodiment of the present disclosure.
[0059] As illustrated, at step 302, a method 300 interfacing one or more field equipment (FE) devices with one or more operational control command (OCC) units of a mass transportation system can include receiving, from the one or more FE devices 110, one or more first information pertaining to one or more parameters of the mass transportation system, wherein each of the one or more first information is received on corresponding one or more first interface protocols, and wherein the one or more first information is in a first format,
[0060] At step 304, the method 300 can include transforming, using a knowledge repository, the first format of the one or more first information into a second format, and the second format compatible to each of the one or more OCC units 108.
[0061] At step 306, the method 300 can include transmitting, to the one or more OCC units 108, the one or more first information in the second format, and the first information in the second format is transmitted on a second interface protocol.
[0062] FIG. 4 illustrates computer system in which or with which embodiments of the present invention can be utilized, in accordance with embodiments of the present disclosure.
[0063] Computer system 400 can include an external storage device 410, a bus 420, a main memory 430, a read only memory 440, a mass storage device 450, communication port 460, and a processor 470. A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. Examples of processor 470 include, but are not limited to, an Intel® Itanium® or Itanium 2 processor(s), or AMD® Opteron® or Athlon MP® processor(s), Motorola® lines of processors, FortiSOC™ system on chip processors or other future processors. Processor 470 may include various modules associated with embodiments of the present invention. Communication port 460 can be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. Communication port 460 may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which computer system connects.
[0064] Memory 430 can be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. Read-only memory 440 can be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or BIOS instructions for processor 470. Mass storage 550 may be any current or future mass storage solution, which can be used to store information and/or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces), e.g. those available from Seagate (e.g., the Seagate Barracuda 7102 family) or Hitachi (e.g., the Hitachi Deskstar 7K1000), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g. an array of disks (e.g., SATA arrays), available from various vendors including Dot Hill Systems Corp., LaCie, Nexsan Technologies, Inc. and Enhance Technology, Inc.
[0065] Bus 420 communicatively couple processor(s) 470 with the other memory, storage and communication blocks. Bus 420 can be, e.g., a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), USB or the like, for connecting expansion cards, drives and other subsystems as well as other buses, such a front side bus (FSB), which connects processor 470 to software system.
[0066] Optionally, operator and administrative interfaces, e.g., a display, keyboard, and a cursor control device, may also be coupled to bus 420 to support direct operator interaction with a computer system. Other operator and administrative interfaces can be provided through network connections connected through communication port 460. The external storage device 410 can be any kind of external hard-drives, floppy drives, IOMEGA® Zip Drives, Compact Disc - Read Only Memory (CD-ROM), Compact Disc-Re-Writable (CD-RW), Digital Video Disk-Read Only Memory (DVD-ROM). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.
[0067] Moreover, in interpreting the specification, all terms should be interpreted in the broadest possible manner consistent with the context. In particular, the terms “comprises” and “comprising” should be interpreted as referring to elements, components, or steps in a non-exclusive manner, indicating that the referenced elements, components, or steps may be present, or utilized, or combined with other elements, components, or steps that are not expressly referenced. Where the specification claims refer to at least one of something selected from the group consisting of A, B, C ….and N, the text should be interpreted as requiring only one element from the group, not A plus N, or B plus N, etc.
[0068] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

ADVANTAGES OF THE INVENTION
[0069] The proposed invention provides a system for interfacing one or more field equipment (FE) devices with one or more operational control command (OCC) units that is more efficient in interoperability of multiple mass transportation system.
[0070] The proposed invention provides a system for interfacing one or more field equipment (FE) devices with one or more operational control command (OCC) units that is more reliable in interoperability of multiple mass transportation system.
[0071] The proposed invention provides a system for interfacing one or more field equipment (FE) devices with one or more operational control command (OCC) units that overcomes dependencies on the different OEMs.
[0072] The proposed invention provides a system for interfacing one or more field equipment (FE) devices with one or more operational control command (OCC) units that is cost-effective and simple to use.
[0073] The proposed invention provides a system that enables operation flexibility, optimized inventory management, permits scalability on any line as well as platform and ease of configuration of network specifications.
[0074] The proposed invention provides a system that provides integration with standard industry-specific data models.
,CLAIMS:1. A system (100) for interfacing one or more field equipment (FE) devices with one or more operational control command (OCC) units of a mass transportation system, the system comprising:
one or more processors (202) configured to execute a set of instructions stored in a memory (204), which, on execution, causes the system to:
receive, from the one or more FE devices (110), a set of first information pertaining to one or more parameters of the mass transportation system, wherein each of the set of first information is received on corresponding one or more first interface protocols, and wherein the one or more first information is in a first format;
transform, using a knowledge repository, the first format of the set of first information into a second format, wherein the second format is compatible with each of the one or more OCC units (108); and
transmit, to the one or more OCC units (108), the set of first information in the second format, wherein the set of first information in the second format is transmitted on a second interface protocol.
2. The system as claimed in claim 1, wherein the one or more parameters comprises any or combination of location and speed of plurality of vehicles associated with the mass transportation system, signals status, route details, passenger information, and tunnel ventilation status.
3. The system as claimed in claim 1, wherein the transforming the first format of the set of first information into the second format is performed using any or combination of a bit mapping, unit conversion, and data conversion technique.
4. The system as claimed in claim 1, wherein the first format is non-standard format, and the one or more first protocols are non-standard proprietary interface protocols associated with the one or more FE devices.
5. The system as claimed in the claim 4, wherein the knowledge repository comprises data related to conversion the non-standard proprietary interface protocols into a machine-readable format.
6. The system as claimed in claim 1, wherein the second format is a standard format, and the second protocol is a mass transportation standard specific protocol.
7. A system as claimed in claim 1, wherein the system is configured to:
receive, from the one or more OCC unit, a set of second information pertaining to one or more control parameters of the mass transportation system, wherein the set of second information is received on the second interface protocol;
transform, using the knowledge repository, the second format of the set of second information into the first format; and
transmit, to the one or more FE devices, the set of second information in the first format, wherein the set of second information in the first format is transmitted on the one or more first interface protocols.
8. The system as claimed in claim 7, wherein the one or more control parameters comprises any or combination of time table scheduling, and route scheduling of the one or more vehicles.
9. A method (300) for interfacing one or more field equipment (FE) devices with one or more operational control command (OCC) units of a mass transportation system, the method comprising:
receiving (302), from the one or more FE devices, one or more first information pertaining to one or more parameters of the mass transportation system, wherein each of the one or more first information is received on corresponding one or more first interface protocols, and wherein the one or more first information is in a first format;
transforming (304), using a knowledge repository, the first format of the one or more first information into a second format, wherein the second format compatible to each of the one or more OCC units; and
transmitting (306), to the one or more OCC units, the one or more first information in the second format, wherein the first information in the second format is transmitted on a second interface protocol.