Abstract: A method and system for federating location of a point of emergency across a plurality of networks is disclosed. The method includes receiving, by a Location Service Orchestrator (LSO), an emergency alert from a User Equipment (UE), wherein the UE is communicatively coupled with a first network from the plurality of networks. The method further includes determining, by the LSO, a location of the UE based on the received emergency alert. The method includes refining, by the LSO, the determined location based on a network initiated location determination mechanism of the first network, when the accuracy of determined location of the UE is below a pre-defined threshold for locational accuracy. The method further includes federating, by the LSO, the refined location of the UE across the plurality of networks. FIG.1
Claims:WE CLAIM:
1. A method of federating location of a point of emergency across a plurality of networks, the method comprising:
receiving, by a Location Service Orchestrator (LSO), an emergency alert from a User Equipment (UE), wherein the UE is communicatively coupled with a first network from the plurality of networks;
determining, by the LSO, a location of the UE based on the received emergency alert;
refining, by the LSO, the determined location based on a network initiated location determination mechanism of the first network, when the accuracy of determined location of the UE is below a pre-defined threshold for locational accuracy; and
federating, by the LSO, the refined location of the UE across the plurality of networks.
2. The method of claim 1, wherein the refined location is federated across the plurality of networks through an LSO-Gateway (LSO-GW) associated with the LSO.
3. The method of claim 2, wherein the LSO-GW is one of a distributed LSO-GW and a centralized LSO-GW, and wherein the distributed LSO-GW is located within an associated LSO, and wherein the centralized LSO-GW is communicatively coupled to LSOs associated with the plurality of networks and facilitates communication amongst the LSOs.
4. The method of claim 1, wherein federating comprises:
embedding information regarding the refined location in a Session Initiation Protocol (SIP) message, wherein a header of the SIP message indicates emergency; and
forwarding the SIP message to an IP Multimedia Subsystem (IMS) server.
5. The method of claim 1, further comprising determining location of a plurality of neighboring UEs within a predefined area of the UE, based on the federated refined location of the UE.
6. The method of claim 5, further comprising:
generating a request to instruct at least one neighboring UE from the plurality of neighboring UEs to act as an access point in communication with the UE;
determining location of the at least one neighboring UE in response to each of the at least one neighboring UE acting as an access point; and
triangulating location of the UE based on determined location of the at least one neighboring UE.
7. The method of claim 5, further comprising providing emergency service to the UE based on the determined location of one or more of the plurality of neighboring UEs.
8. The method of claim 7, further comprising triggering an emergency request comprising location coordinates of the UE to one or more of the plurality of neighboring UEs.
9. The method of claim 1, further comprising creating a blind zone database comprising information associated with geographical areas receiving zero coverage from the first network, based on reports received from the UE.
10. The method of claim 1, wherein the emergency alert is generated by the UE in response to a trigger received from an external device communicatively coupled to the UE, wherein the external device is configured to detect an emergency situation.
11. The method of claim 1, wherein the first network is one of a 3rd Generation Partnership Project (3GPP) network, a non-3GPP network, and a Wi-Fi network.
12. The method of claim 1, wherein the network initiated location determination mechanism is implemented in one of a Multi-access Edge Computing (MEC) safety application server and a non-MEC safety application server.
13. The method of claim 1 further comprising:
retrieving at least one antecedent location of the UE;
identifying a path being traversed by the UE based on mean square error between coordinates of the at least one antecedent location of the UE and coordinates of the path; and
enhancing the refined location of the UE based on the identified path.
14. The method of claim 12 further comprising:
determining antecedent locations of a set of neighboring UEs;
identifying a neighboring UE from the set of neighboring UEs, wherein antecedent locations associated with the neighboring UE is within a predefined radius of one of the at least one antecedent location of the UE during a predefined time period.
15. A system comprising a Location Service Orchestrator (LSO) for federating location of a point of emergency across a plurality of networks, the system comprising:
a processor; and
a memory communicatively coupled to the processor, wherein the memory stores processor instructions, which, on execution, causes the processor to:
receive an emergency alert from a User Equipment (UE), wherein the UE is communicatively coupled with a first network from the plurality of networks;
determine a location of the UE based on the received emergency alert;
refine the determined location based on a network initiated location determination mechanism of the first network, when the accuracy of determined location of the UE is below a pre-defined threshold for locational accuracy; and
federate the refined location of the UE across the plurality of networks.
Dated this 26th day of December, 2018
Madhusudan S.T
Of K&S Partners
Agent for the Applicant
IN/PA-1297
, Description:TECHNICAL FIELD
[001] This disclosure relates generally to determining location of point of emergency and more particularly to method and system for federating location of point of emergency across networks.
| # | Name | Date |
|---|---|---|
| 1 | 201841049217-REQUEST FOR EXAMINATION (FORM-18) [26-12-2018(online)].pdf | 2018-12-26 |
| 2 | 201841049217-POWER OF AUTHORITY [26-12-2018(online)].pdf | 2018-12-26 |
| 3 | 201841049217-FORM 18 [26-12-2018(online)].pdf | 2018-12-26 |
| 4 | 201841049217-FORM 1 [26-12-2018(online)].pdf | 2018-12-26 |
| 5 | 201841049217-DRAWINGS [26-12-2018(online)].pdf | 2018-12-26 |
| 6 | 201841049217-DECLARATION OF INVENTORSHIP (FORM 5) [26-12-2018(online)].pdf | 2018-12-26 |
| 7 | 201841049217-COMPLETE SPECIFICATION [26-12-2018(online)].pdf | 2018-12-26 |
| 8 | 201841049217-Request Letter-Correspondence [28-12-2018(online)].pdf | 2018-12-28 |
| 9 | 201841049217-Power of Attorney [28-12-2018(online)].pdf | 2018-12-28 |
| 10 | 201841049217-Form 1 (Submitted on date of filing) [28-12-2018(online)].pdf | 2018-12-28 |
| 11 | 201841049217-Request Letter-Correspondence [09-01-2019(online)].pdf | 2019-01-09 |
| 12 | 201841049217-Power of Attorney [09-01-2019(online)].pdf | 2019-01-09 |
| 13 | 201841049217-Form 1 (Submitted on date of filing) [09-01-2019(online)].pdf | 2019-01-09 |
| 14 | 201841049217-Proof of Right (MANDATORY) [06-05-2019(online)].pdf | 2019-05-06 |
| 15 | Correspondence by Agent_Proof of Right_10-05-2019.pdf | 2019-05-10 |
| 16 | 201841049217-RELEVANT DOCUMENTS [25-08-2021(online)].pdf | 2021-08-25 |
| 17 | 201841049217-PETITION UNDER RULE 137 [25-08-2021(online)].pdf | 2021-08-25 |
| 18 | 201841049217-OTHERS [25-08-2021(online)].pdf | 2021-08-25 |
| 19 | 201841049217-Information under section 8(2) [25-08-2021(online)].pdf | 2021-08-25 |
| 20 | 201841049217-FORM 3 [25-08-2021(online)].pdf | 2021-08-25 |
| 21 | 201841049217-FER_SER_REPLY [25-08-2021(online)].pdf | 2021-08-25 |
| 22 | 201841049217-DRAWING [25-08-2021(online)].pdf | 2021-08-25 |
| 23 | 201841049217-CORRESPONDENCE [25-08-2021(online)].pdf | 2021-08-25 |
| 24 | 201841049217-COMPLETE SPECIFICATION [25-08-2021(online)].pdf | 2021-08-25 |
| 25 | 201841049217-CLAIMS [25-08-2021(online)].pdf | 2021-08-25 |
| 26 | 201841049217-ABSTRACT [25-08-2021(online)].pdf | 2021-08-25 |
| 27 | 201841049217-FER.pdf | 2021-10-17 |
| 28 | 201841049217-US(14)-HearingNotice-(HearingDate-02-08-2023).pdf | 2023-07-20 |
| 29 | 201841049217-POA [25-07-2023(online)].pdf | 2023-07-25 |
| 30 | 201841049217-FORM 13 [25-07-2023(online)].pdf | 2023-07-25 |
| 31 | 201841049217-Correspondence to notify the Controller [25-07-2023(online)].pdf | 2023-07-25 |
| 32 | 201841049217-AMENDED DOCUMENTS [25-07-2023(online)].pdf | 2023-07-25 |
| 33 | 201841049217-Written submissions and relevant documents [17-08-2023(online)].pdf | 2023-08-17 |
| 34 | 201841049217-PatentCertificate25-08-2023.pdf | 2023-08-25 |
| 35 | 201841049217-IntimationOfGrant25-08-2023.pdf | 2023-08-25 |
| 1 | SS_201841049217E_28-01-2021.pdf |