Sign In to Follow Application
View All Documents & Correspondence

System And Method For Managing An Over The Air (Ota) Update

Abstract: ABSTRACT System and Method for Managing an Over-the-Air (OTA) Update Present invention provides a system (100) for managing an Over-the-Air (OTA) update. The system (100) comprises a master database (102) comprising one or more elements pertaining to the OTA update and a slave database (104) communicably coupled to the master database (102). A control unit (106) is communicably coupled to the master database (102) and the slave database (104). The control unit (106) is configured to mirror, the one or more elements stored in the master database (102) to the slave database (104) and analyse, the one or more elements mirrored in the slave database (104). The one or more elements are then processed by the control unit 106 for performing the OTA update on a user device (108) from one of the master database (102) and the slave database (104) upon receiving an update request. The system (100) ensures that the OTA updates are seamless and error-free. Reference Figure 1

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
21 March 2024
Publication Number
39/2025
Publication Type
INA
Invention Field
COMPUTER SCIENCE
Status
Email
Parent Application

Applicants

TVS MOTOR COMPANY LIMITED
“Chaitanya”, No.12 Khader Nawaz Khan Road, Nungambakkam, Chennai 600 006, Tamil Nadu, India

Inventors

1. GUDI VENKATA RAMANA
TVS Motor Company Limited, “Chaitanya”, No 12 Khader Nawaz Khan Road, Nungambakkam, Chennai 600 006, Tamil Nadu, India
2. RAHUL KISHAN
TVS Motor Company Limited, “Chaitanya”, No 12 Khader Nawaz Khan Road, Nungambakkam, Chennai 600 006, Tamil Nadu, India
3. VIRAM RAMESH MANJARE
TVS Motor Company Limited, “Chaitanya”, No 12 Khader Nawaz Khan Road, Nungambakkam, Chennai 600 006, Tamil Nadu, India
4. MADDULA SAI SUNAMDHA HARINHI
TVS Motor Company Limited, “Chaitanya”, No 12 Khader Nawaz Khan Road, Nungambakkam, Chennai 600 006, Tamil Nadu, India

Specification

Description:FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
&
THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
[Refer Section 10, Rule 13]

TITLE OF INVENTION
System and Method for Managing an Over-the-Air (OTA) Update

APPLICANT
TVS MOTOR COMPANY LIMITED, an Indian company, having its address at “Chaitanya”, No.12 Khader Nawaz Khan Road, Nungambakkam, Chennai 600 006, Tamil Nadu, India.

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

FIELD OF THE INVENTION
[001] Present invention relates to a system and a method for managing an Over-the-Air (OTA) update.

BACKGROUND OF THE INVENTION
[002] Conventional Over-the-Air (OTA) update systems typically consist of two frontend parts, one being an operational frontend which is a User Interface (UI) framework and another being an analytics frontend. In existing systems, the operational frontend and the analytics frontend perform their tasks independently of each other. A database, consisting of data pertaining to the OTA update is provided in the system, is in communication with the operational frontend and the analytics frontend. Accordingly, the operational frontend and the analytics frontend have access to the data present in the database. Since the operational frontend and the analytics frontend have access to the same database, there is a performance bottleneck due to the high load on the database and simultaneous access by operational and analytics frontends. Such a scenario leads to a performance degradation of the whole OTA update system. Also, there exists an inconsistent or an outdated data across the operational frontend and analytics frontend leading to error in OTA update management, reporting and decision-making. Moreover, the operational frontend and analytics frontend having access to the same database leads to data loss or corruption, when the data is not properly updated or synchronized. Consequently, leading to discrepancies and irrecoverable errors in the OTA update system, which is undesirable.
[003] Additionally, using a single database makes the OTA system vulnerable to security breaches such as unauthorized access, data breaches or injection attacks which compromises the confidentiality, integrity, and availability of OTA data. Also, usage of the single database makes the system unable to handle increased data volume, user traffic leading to scalability challenges and performance degradation.
[004] Thus, there is a need for a system and a method for managing an Over-the-Air (OTA) update, which address at least one of the aforesaid problems.

SUMMARY OF THE INVENTION
[005] In one aspect, a system for managing an Over-the-Air (OTA) update is disclosed. The system comprises a master database comprising one or more elements pertaining to the OTA update, a slave database communicably coupled to the master database. A control unit communicably coupled to the master database and the slave database which is configured to mirror the one or more elements stored in the master database to the slave database. The control unit then analyses the one or more elements mirrored in the slave database. Thereafter, process the one or more elements for performing the OTA update on a user device from one of the master database and the slave database upon receiving an update request, for managing the OTA update.
[006] In an embodiment, the control unit is configured to mirror the one or more elements stored in the master database to the slave database upon receiving an update trigger when the one or more elements are modified in the master database.
[007] In an embodiment, the control unit is configured to mirror the one or more elements stored in the master database to the slave database through a replication technique.
[008] In an embodiment, the control unit is configured to analyse the one or more elements in the slave database, by application of one or more analytic techniques. The one or more elements are further processed based on the application of the one or more analytic techniques on the one or more elements.
[009] In an embodiment, the control unit is configured to generate one or more reports based on the analysis of the one or more elements.
[010] In an embodiment, the control unit is configured to secure the one or more elements, while mirroring the one or more elements from the master database to the slave database (104). The control unit is further configured to secure the one or more elements by at least one of a data encryption technique, an access control technique and an audit trail technique.
[011] In an embodiment, the control unit is configured to monitor the one or more elements of the OTA update processed to the user device upon receiving the update request. The control unit is further configured to monitor the one or more elements based on at least one of a campaign performance parameter, an update progress parameter and an operational metric parameter.
[012] In an embodiment, the control unit is configured to access the slave database in a read-only mode.
[013] In an embodiment, the one or more elements comprises at least one of an OTA package, vehicle details, component details of the user device, flashing details, download fail, flashing fail and campaign.
[014] In another aspect, a method for managing the Over-the-Air (OTA) update is provided. The method comprises steps of mirroring, by the control unit, one or more elements stored in the master database to the slave database. The method further comprises steps of analysing, by the control unit, the one or more elements mirrored in the slave database. The control unit further processes the one or more elements for performing the OTA update on a user device from one of the master database and the slave database upon receiving an update request, for managing the OTA update.

BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS
[015] 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 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 is a block diagram of system for managing an Over-the-Air (OTA) update, in accordance with an exemplary embodiment of the present invention.
Figure 2 is a a block diagram of system for managing an Over-the-Air (OTA) update, in accordance with an exemplary embodiment of the present invention.
Figure 3 is a flow diagram showing a method for for managing an Over-the-Air (OTA) update, in accordance with an exemplary embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION
[016] Present invention relates a system and a method for managing an Over-the-Air (OTA) update. Embodiments of the present invention relates to the system and the method for managing the OTA update for a user device such as smart vehicles. The system ensures that the OTA updates are seamless and error-free, thereby ensuring a stable update to the user device receiving the OTA update. Also, the load on a master database of the system is significantly reduced, thereby mitigating redundancy issues while managing the OTA update.
[017] Figure 1 is a block diagram of a system 100 for managing an Over-the-Air (OTA) update, in accordance with an exemplary embodiment of the present invention. The system 100 is configured to manage the OTA update to a user device 108. The user device 108 may be a smart vehicle of a user, wherein the smart vehicle can be a single-wheeled vehicle, a two-wheeled vehicle or any other multi-wheeled vehicle.
[018] The system 100 comprises a master database 102 that comprises one or more elements pertaining to the OTA update. The “one or more elements” relate to information or data pertaining to the OTA update such as an OTA package, vehicle details, component details of the user device 108, flashing details, download fail details, flashing fail detail, update campaign details, vehicle details and the like. The master database 102 may be a robust relational database management system implemented using PostgreSQL. In an embodiment, the master database 102 is configured to be set up with appropriate table structures (not shown) for storing the one or more elements pertaining to the OTA update. The master database 102 is be configured to capture database triggers based on data changes or Change Data Capture (CDC) mechanisms or by employing other data change capture mechanisms known in the art.
[019] Further, a slave database 104 is provided in the system 100. The slave database 104 is communicably coupled to the master database 102 through wired or wireless communication protocols known in the art. The slave database 104 is capable of storing the one or more elements pertaining to the OTA update that is stored in the master database 102. The data stored in the slave database is a mirrored data of the master database 102. In an embodiment, the slave database 104 is provided as a replica of the master database 102 for purposes of reporting the data stored or changed or deleted. The slave database 104 is provided with permissions to restrict write operations only to ensure consistency in data while reporting. In other words, the slave database 104 is permitted to be accessed in a read-only mode, for ensuring consistency in data while reporting.
[020] In an embodiment, the system 100 comprises microservices module 110 in communication with the master database 102 and the slave database 104. The microservices module 110 is capable of executing one or more replication techniques required for replication of the data (i.e. one or more elements pertaining to the OTA update) from the master database 102 to the slave database 104. Further, the microservices module 110 enables scalability of the system 100, for accommodating data pertaining to the user device(s) 108 while maintaining optimum performance and reliability.
[021] In an embodiment, the system 100 comprises a dashboard 114 displayed on a display component of a computing device (not shown) such as a workstation. The dashboard 114 is in communication with the master database 102 and the slave database 104 through an Application Programming Interface (API) gateway module 112. Additionally, an admin (i.e. a user controlling the system 100) of the system 100 can access the master database 102 for performing control actions, such as updating or changing or deleting data in the master database 102 through the dashboard 114. The dashboard 114 is provided with a User Interface (not shown) for enabling the admin to navigate and perform the control actions required for the OTA update. Further, the dashboard 114 is also capable of displaying comprehensive reports and analytics for managing the OTA update. This allows the admin to derive actionable insights and make informed decisions of managing the OTA update. As an example, if the dashboard 114 depicts that the OTA update was unsuccessful for the user devices 108, the admin based on this depiction from the dashboard 114 can change or delete or add relevant data in the master database 102, thereby managing the OTA update.
[022] In an embodiment, the dashboard 114 allows the admin to manage the master database 102 through a React Web App, which is in communication with the microservices module 110 through API module 112. This provides the admin a user friendly interface for managing the OTA updates in the system 100.
[023] In an embodiment, the dashboard 114 allows the admin to visualise and derive actionable insights from the data pertaining to the OTA update through a Microsoft-Power Bi app. This assists the admin in decision-making processes and enables strategic planning of the OTA updates. Also, this assists in performing real-time analysis of OTA campaign performance.
[024] Referring to Figure 2 in conjunction with Figure 1, the system 100 further comprises a control unit 106. The control unit 106 is communicably coupled to the master database 102, the slave database 104, the microservices module 110, the API gateway module and the user device 108 through wired or wireless communication techniques known in the art. The control unit 106 is adapted to manage the OTA update to the user device 108.
[025] The control unit 106 is communicably coupled to an input/output module 118 and a memory unit 120. The control unit 106 is capable of executing instructions stored within the memory unit 120 to perform the operations described herein.
[026] The control unit 106 is configured to mirror the data (i.e. the one or more elements) from the master database 102 to the slave database 104. In an embodiment, the control unit 106 is configured to mirror the data from the master database 102 to the slave database 104 through replication techniques known in the art stored in the memory unit 120. In an embodiment, the control unit 106 is configured to mirror the data from the master database 102 to the slave database 104 through the microservices module 110. As such, the control unit 106 operates in tandem with microservices module 110, thereby enhancing efficiency of the system 100 for managing the OTA update. In an embodiment, the control unit 106 is configured to mirror the data from the master database 102 to the slave database 104, when an update trigger is received from the input/output module 118. In an embodiment, the update trigger may be in the form an update request from the user of the user device 108, a change or addition or deletion of the one or more elements of the OTA update in the master database 102. As such, the data in the slave database 104 is always up to date vis-à-vis the master database 102.
[027] The control unit 106 comprises an analytic module 122 that is configured to analyse the one or more elements of the OTA update in the slave database 104. The analytic module 122 is configured to map the one or more elements in the master database 102 with the slave database 104 for checking integrity of the mirrored one or more elements. In an embodiment, the control unit 106 is configured to analyse the one or more elements in the slave database 104 by employing one or more analytic techniques known in the art. If a discrepancy is observed in the mirrored data, the control unit 106 is adapted to process the one or more elements suitably from the master database 102 to the slave database 104 for overcoming the discrepancy.
[028] In an embodiment, the analytic module 122 is configured to visualise and derive actionable insights from the data pertaining to the OTA update. This assists the admin in decision-making processes and enables strategic planning of the OTA updates. Also, this assists in performing real-time analysis of OTA campaign performance.
[029] Further, the control unit 106 is configured to process the one or more elements for performing the OTA update on the user device 108, upon receiving the update request from the user device 108. The control unit 106 processes the update from the master database 102 and/or the slave database 104. In an embodiment, processing of the one or more elements corresponds to transmitting of relevant data to the user device 108 based on the user device configuration.
[030] Further, the control unit 106 is adapted to monitor the one or more elements of the OTA update processed to the user device 108. The control unit 106 monitors the one or more elements based on at least one of a campaign performance parameter, an update progress parameter and an operational metric parameter.
[031] In an embodiment, the ‘campaign performance parameter’ is a factor of total number of user devices 108 that are successfully updated in the campaign. Considering the above mentioned example, if the OTA update is transmitted to 4 user devices, out of which OTA update for 2 user devices were found to be successful, the ‘campaign performance parameter’ can be considered as 50% or 0.5.
[032] In an embodiment, the ‘update progress parameter’ may be a parameter of total number of user devices 108 being updated at a given time. As an example, if the OTA update is transmitted to 4 user devices, out of which OTA update for 2 user devices are processing the update (which can be by way of downloading or verifying or installation of the OTA update), the ‘update progress parameter’ can be considered as 50% or 0.5.
[033] In an embodiment, the ‘operational metric parameter’ may be a parameter of total number of user devices 108 that are functioning efficiently after successful OTA update. As an example, if the OTA update is successfully installed in 4 user devices, out of which OTA update for 2 user devices are functioning efficiently, the ‘operational metric parameter’ can be considered as 50% or 0.5.
[034] The control unit 106 is configured to transmit the monitored data from to a reporting module 124. The reporting module 124 may be configured to organize the data monitored by the control unit 106 and generate one or more reports basis the analysed data. The one or more reports are transferred to the computing device to be displayed in an admin preferred format. In an embodiment, the reporting module 124 may transfer the one or more reports to the dashboard 114 through the computing device for visualization by the admin.
[035] As an example, if the OTA update was transmitted to 4 user devices, out of which OTA update for 2 user devices were found to be successful, while the remaining two OTA updates was unsuccessful due to device configuration mismatch. The control unit 106 is adapted to detect list of user devices with successful updates versus the unsuccessful updates. This analysis is transmitted to the dashboard 114 for visualization to the admin.
[036] In an embodiment, the master database 102 is embedded or hosted in a server or a virtual machine. In another embodiment, the slave database 104 is also embedded or hosted in a server or a virtual machine. In another embodiment, the master database 102 and the slave database 104 may be embedded in distinct servers or at distinct location as per feasibility and requirement in the system 100.
[037] In an embodiment, the control unit 106 is adapted to secure the one or more elements in the master database 102 and/or the slave database 104, by implementing at least one of a data encryption technique, an access control technique and an audit trail technique known in the art. In an embodiment, the control unit 106 provides a role based access control for the master database 102 and/or the slave database 104. The term “role based access control” corresponds to access control provided to the admin based on his designation within an organization. The security for the one or more elements pertaining to the OTA updates enhances trust and confidence in the integrity and confidentiality of the system 100.
[038] In an embodiment, the control unit 106 is adapted to direct queries from the user in relation to the OTA update to the master database 102, while analysis of the data pertaining to the OTA updates is carried out based on the data in the slave database 104 by the control unit 106. Thus, the control unit 106 ensures that queries are directed to the master database 102, while queries based on analysis requests are directed to the slave database 104, thereby balancing the load in the system 100. Consequently, the performance of the system 100 improved. In an embodiment, the queries from the user may be an OTA update request, an update checking request and the like.
[039] In an embodiment, the control unit 106 is embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and one or more single core processors. For example, the control unit 106 is embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. In another embodiment, the control unit 106 is configured to execute hard-coded functionality.
[040] Figure 3 is a flow diagram of a method 300 for managing the OTA update to the user device 108, in accordance with an exemplary embodiment of the present invention. The method 300 is performed by the system, such as the system 100 or the control unit 106.
[041] At step 302, the control unit 106 is configured to mirror the one or more elements stored in the master database 102 to the slave database 104. In an embodiment, the control unit 106 is configured to mirror the data from the master database 102 to the slave database 104 through the replication techniques known in the art, which are stored in the memory unit 120. In an embodiment, the control unit 106 is configured to mirror the data from the master database 102 to the slave database 104 through the microservices module 110.
[042] At step 304, the control unit 106 is configured to analyse the one or more elements mirrored in the slave database 104. The control unit 106 analyses the one or more elements through one or more analytic techniques known in the art, as described in description pertaining to Figure 2.
[043] At step 306, the control unit 106 is adapted to process the one or more elements for performing the OTA update on the user device from one of the master database 102 and the slave database 104 upon receiving the update request.
[044] The claimed invention as disclosed above is not routine, conventional, or well understood in the art, as the claimed aspects enable the following solutions to the existing problems in conventional technologies. Specifically, the claimed aspect of mirroring the one or more elements to the slave database and analysing the data in the slave database enables load sharing between the master database and the slave database. Thus, ensuring that the OTA updates are seamless and error-free, thereby ensuring a stable update to the user device receiving the OTA update. Consequently, improving performance of the system carrying out the OTA update. Also, the load on a master database of the system is significantly reduced, thereby mitigating redundancy issues while managing the OTA update.
[045] Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present disclosure. A computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term “computer-readable storage medium” should be understood to include tangible items and exclude carrier waves and transient signals, i.e., be non-transitory. Examples include random access memory (RAM), read-only memory (ROM), volatile memory, non-volatile memory, hard drives, CD ROMs, DVDs, flash drives, disks, and any other known physical storage media”.
[046] While the present invention has been described with respect to certain embodiments, it will be apparent to those skilled in the art that various changes and modification may be made without departing from the scope of the invention as defined in the following claims.

Reference Numerals
100 – System
102 – Master database
104 – Slave database
106 – Control unit
108 – User device
110 – Microservices module
112 – API gateway module
114 – Dashboard
118 – Input/output module
120 – Memory unit
122 – Analytics module
124 – Reporting module
, Claims:WE CLAIM:
1. A system (100) for managing an Over-the-Air (OTA) update, the system (100) comprising:
a master database (102) comprising one or more elements pertaining to the OTA update;
a slave database (104) communicably coupled to the master database (102),
a control unit (106) communicably coupled to the master database (102) and the slave database (104), the control unit (106) being configured to:
mirror, the one or more elements stored in the master database (102) to the slave database (104),
analyse, the one or more elements mirrored in the slave database (104), and
process, the one or more elements for performing the OTA update on a user device (108) from one of the master database (102) and the slave database (104) upon receiving an update request, for managing the OTA update.

2. The system (100) as claimed in claim 1, wherein the control unit (106) being configured to mirror the one or more elements stored in the master database (102) to the slave database (104) upon receiving an update trigger when the one or more elements are modified in the master database (102).

3. The system (100) as claimed in claim 1, wherein the control unit (106) being configured to mirror the one or more elements stored in the master database (102) to the slave database (104) through a replication technique.

4. The system (100) as claimed in claim 1, wherein the control unit (106) being configured to analyse the one or more elements in the slave database (104), by application of one or more analytic techniques, wherein the processing of the one or more elements is further based on the application of the one or more analytic techniques on the one or more elements.

5. The system (100) as claimed in claim 4, wherein the control unit (106) being configured to generate one or more reports based on the analysis of the one or more elements.

6. The system (100) as claimed in claim 1, wherein the control unit (106) being configured to secure the one or more elements, while mirroring the one or more elements from the master database (102) to the slave database (104),
the control unit (106) being configured to secure the one or more elements by at least one of a data encryption technique, an access control technique and an audit trail technique.

7. The system (100) as claimed in claim 1, wherein the control unit (106) being configured to monitor the one or more elements of the OTA update processed to the user device (108) upon receiving the update request,
the control unit (106) being configured to monitor the one or more elements based on at least one of a campaign performance parameter, an update progress parameter and an operational metric parameter.

8. The system (100) as claimed in claim 1, wherein the control unit (106) being configured to access the slave database (104) in a read-only mode.

9. The system (100) as claimed in claim 1, wherein the one or more elements comprises at least one of: an OTA package, vehicle details, component details of the user device (108), flashing details, download fail, flashing fail and campaign.

10. A method for managing an Over-the-Air (OTA) update, the method comprising:
mirroring, by a control unit (106), one or more elements stored in a master database (102) to a slave database (104);
analysing, by the control unit (106), the one or more elements mirrored in the slave database (104); and
processing, by the control unit (106), the one or more elements for performing the OTA update on a user device (108) from one of the master database (102) and the slave database (104) upon receiving an update request, for managing the OTA update.

11. The method as claimed in claim 10 comprising mirroring, by the control unit (106), the one or more elements stored in the master database (102) to the slave database (104) upon receiving an update trigger, when the one or more elements are modified in the master database (102).

12. The method as claimed in claim 10 comprising mirroring, by the control unit (106), the one or more elements stored in the master database (102) to the slave database (104) through a replication technique.

13. The method as claimed in claim 10 comprising analysing, by the control unit (106), the one or more elements in the slave database (104), by employing one or more analytic techniques.

14. The method as claimed in claim 13 comprising generating, by the control unit (106), one or more reports based on the analysis of the one or more elements.

15. The method as claimed in claim 10 comprising securing, by the control unit (106), the one or more elements by at least one of a data encryption technique, an access control technique and an audit trail technique, while mirroring the one or more elements from the master database (102) to the slave database (104).

16. The method as claimed in claim 10 comprising monitoring, by the control unit (106), the one or more elements of the OTA update processed to the user device (108) upon receiving the update request,
the control unit (106) being configured to monitor the one or more elements based on at least one of a campaign performance parameter, an update progress parameter and an operational metric parameter.

17. The method as claimed in claim 10 comprising accessing, by the control unit (106), the slave database (104) in a read-only mode.

Dated this 21st day of March 2024
TVS MOTOR COMPANY LIMITED
By their Agent & Attorney

(Nikhil Ranjan)
of Khaitan & Co
Reg No IN/PA-1471

Documents

Application Documents

# Name Date
1 202441021722-STATEMENT OF UNDERTAKING (FORM 3) [21-03-2024(online)].pdf 2024-03-21
2 202441021722-REQUEST FOR EXAMINATION (FORM-18) [21-03-2024(online)].pdf 2024-03-21
3 202441021722-PROOF OF RIGHT [21-03-2024(online)].pdf 2024-03-21
4 202441021722-POWER OF AUTHORITY [21-03-2024(online)].pdf 2024-03-21
5 202441021722-FORM 18 [21-03-2024(online)].pdf 2024-03-21
6 202441021722-FORM 1 [21-03-2024(online)].pdf 2024-03-21
7 202441021722-FIGURE OF ABSTRACT [21-03-2024(online)].pdf 2024-03-21
8 202441021722-DRAWINGS [21-03-2024(online)].pdf 2024-03-21
9 202441021722-DECLARATION OF INVENTORSHIP (FORM 5) [21-03-2024(online)].pdf 2024-03-21
10 202441021722-COMPLETE SPECIFICATION [21-03-2024(online)].pdf 2024-03-21
11 202441021722-Proof of Right [05-07-2024(online)].pdf 2024-07-05