Abstract: The present disclosure introduces a technique to manage requests within a network. A request is initiated at a predetermined time setting and sent to a designated server. Further, the relevant parameters are extracted from the request. The parameters are associated with a user profile of the user. Further, the information associated with the parameters is retrieved from a database. The information may include tasks assigned for the user related to network health, network connectivity, network coverage, recommendations, suggestions, action status, cell tower wrong tilt, cell tower’s incorrect height, any obstruction in network, etc. The retrieved information is then transmitted to a user device, which processes the information to perform specific operations, enhancing efficiency by automating request handling, data retrieval, and processing based on predefined time settings. The specific operation may include storing the retrieved information in a storage of the user device. Figure.6
WE CLAIM:
1. A method (600) for managing one or more requests in a network (106), the
method (600) comprising:
5 triggering (602), by a user equipment (UE) (104), a first request based on a
predefined setting time towards at least one server;
extracting (604), by the at least one server (408), one or more parameters
associated with the triggered first request;
querying (606), by the at least one server (408), a database (210) to retrieve
10 information associated with the one or more extracted parameters;
transmitting (608), by the at least one server (408), the retrieved information to
the UE (104); and
performing (610), by the UE (104), one or more operations associated with the
retrieved information.
15 2. The method (600) as claimed in claim 1, wherein the one or more parameters
are associated with a user profile related to a user associated with the UE (104).
3. The method (600) as claimed in claim 1, wherein the one or more operations
performed by the UE (104) comprising at least one of processing the retrieved
20 information or storing the retrieved information at the UE (104).
4. The method (600) as claimed in claim 3, further comprising:
triggering, by the UE (104), a second request associated with the processed
retrieved information based on the predefined setting time towards the at least one
25 server (408);
41
validating, by the at least one server (408), the triggered second request to
authenticate the processed retrieved information;
storing, by the at least one server (408), the processed retrieved information;
and
5 transmitting, by the at least one server (408), a response message comprising
either a success message or a failure message towards the UE (104).
| # | Name | Date |
|---|---|---|
| 1 | 202421021616-STATEMENT OF UNDERTAKING (FORM 3) [21-03-2024(online)].pdf | 2024-03-21 |
| 2 | 202421021616-PROVISIONAL SPECIFICATION [21-03-2024(online)].pdf | 2024-03-21 |
| 3 | 202421021616-FORM 1 [21-03-2024(online)].pdf | 2024-03-21 |
| 4 | 202421021616-DRAWINGS [21-03-2024(online)].pdf | 2024-03-21 |
| 5 | 202421021616-FORM-26 [22-03-2024(online)].pdf | 2024-03-22 |
| 6 | 202421021616-ORIGINAL UR 6(1A) FORM 26-120624.pdf | 2024-06-20 |
| 7 | 202421021616-Proof of Right [16-07-2024(online)].pdf | 2024-07-16 |
| 8 | 202421021616-ORIGINAL UR 6(1A) FORM 1-090824.pdf | 2024-08-16 |
| 9 | 202421021616-Power of Attorney [17-02-2025(online)].pdf | 2025-02-17 |
| 10 | 202421021616-Covering Letter [17-02-2025(online)].pdf | 2025-02-17 |
| 11 | 202421021616-FORM-5 [18-02-2025(online)].pdf | 2025-02-18 |
| 12 | 202421021616-DRAWING [18-02-2025(online)].pdf | 2025-02-18 |
| 13 | 202421021616-CORRESPONDENCE-OTHERS [18-02-2025(online)].pdf | 2025-02-18 |
| 14 | 202421021616-COMPLETE SPECIFICATION [18-02-2025(online)].pdf | 2025-02-18 |
| 15 | Abstract.jpg | 2025-03-28 |
| 16 | 202421021616-FORM 18 [16-07-2025(online)].pdf | 2025-07-16 |