Abstract: The present subject matter discloses a method for establishing a call between two user equipments (102). The method comprises receiving, at a Radio Access Point (RAP) (110), a request from a first user equipment (UE1) (102-1), for establishing a call with a second user equipment (UE2) (102-2). After receiving the call request, it is determined whether the UE2 (102-2) is in a connected state with the RAP (110). The determination is performed based on information of the UE2 (102-2) stored as UE2 context in the RAP (110). Further, based on the determination, the call is established with the UE2 (102-2).
CLIAMS:1. A method for establishing a call between two user equipments (102), the method comprising:
receiving, at a Radio Access Point (RAP) (110), by a processor (202), a request from a first user equipment (UE1) (102-1), for establishing a call with a second user equipment (UE2) (102-2);
determining, by the processor (202), whether the UE2 (102-2) is in a connected state with the RAP (110), wherein the determining is based on information of the UE2 (102-2) stored as UE2 context in the RAP (110); and
establishing, by the processor (202), the call with the UE2 (102-2) based on the determining.
2. The method as claimed in claim 1, wherein the RAP (110) includes one of an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Access Network (E-UTRAN) NodeB (eNodeB) and a Home Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Access Network (E-UTRAN) NodeB (HeNB).
3. The method as claimed in claim 1 further comprising establishing the call between the UE1 (102-1) and the UE2 (102-2) over respective default bearers without routing the call to a core network.
4. The method as claimed in claim 1, wherein the UE context pertaining to the UE2 (102-2) includes at least one of an International Mobile Subscriber Identity (IMSI), System Architecture Evolution (SAE)-Temporary Mobile Subscriber Identity (TMSI) (S-TMSI), an RAP ID and S1 Application Protocol (AP) ID corresponding to the UE2 (102-2).
5. The method as claimed in claim 1 further comprising:
sending, by the processor (202), a confirmation request to the UE2 (102-2), when the UE2 (102-2) is in a disconnected state, for determining whether the UE2 (102-2) is available for connection;
receiving, by the processor (202), from the UE2 (102-2), a response to the confirmation request; and
establishing, by the processor (202), the call with the UE2 (102-2) after receiving a response from the UE2 (102-2).
6. The method as claimed in claim 5 further comprising switching, by the processor (202), the request to a core network, when the response to the confirmation request is not received from the UE2 (102-2).
7. The method as claimed in claim 5, wherein the confirmation request is sent through dummy paging.
8. The method as claimed in claim 1 further comprising
ascertaining, by the processor (202), whether the UE2 (102-2) is available in coverage areas of a second RAP (110), based on details of the UE2 (102-2) stored in a Session Initiation Protocol (SIP) server (114), when the UE2 (102-2) is determined to be in a disconnected state with the RAP (110);
forwarding, by the processor (202), the request to the second RAP (110), based on the ascertaining;
determining, at the second RAP (110), by a second processor (202), whether the UE2 (102-2) is in a connected state with the second RAP (110), wherein the determining is based on information of the UE2 (102-2) stored as the UE2 context in the second RAP (110); and
establishing, by the second processor (202), the call with the UE2 (102-2) based on the determining at the second RAP (110).
9. A Radio Access Point (RAP) (110) comprising:
a processor (202) configured to,
receive, from a first user equipment (UE1) (102-1), a request for establishing a call with a second user equipment (UE2) (102-2);
determine whether User Equipment (UE) context corresponding to the UE2 (102-2) is present in the RAP (110), wherein the UE context includes information of the UE2 (102-2); and
establish the call with the UE2 (102-2) based on the determining.
10. The RAP (110) as claimed in claim 9, wherein the RAP (110) includes one of an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Access Network (E-UTRAN) NodeB (eNodeB), and a Home Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Access Network (E-UTRAN) NodeB (HeNB).
11. The RAP (110) as claimed in claim 9, wherein the UE context pertaining to the UE2 (102-2) includes at least one of an International Mobile Subscriber Identity (IMSI), System Architecture Evolution (SAE)-Temporary Mobile Subscriber Identity (TMSI) (S-TMSI), an RAP ID and S1 Application Protocol (AP) ID corresponding to the UE2.
12. The RAP (110) as claimed in claim 9, wherein the processor (202) is configured to
send, after determining that the UE context corresponding to the UE2 (102-2) is not present in the RAP (110), a confirmation request to the UE2 (102-2) for determining whether the UE2 (102-2) is available for connection;
receive, from the UE¬2 (102-2), a response to the confirmation request; and
establish, after receiving the response, the call with the UE2 (102-2).
13. The RAP (110) as claimed in claim 12, wherein the processor (202) is configured to switch the request to a core network, when the response to the confirmation request is not received from the UE2 (102-2).
14. The RAP (110) as claimed in claim 9, wherein the UE1 (102-1) and the UE2 (102-2) are registered with different network operators (106).
15. The RAP (110) as claimed in claim 9, wherein the processor (202) is configured to establish the call between the UE1 (102-1) and the UE2 (102-2) over respective default bearers without routing the call to a core network.
16. The RAP (110) as claimed in claim 9, wherein the UE2 context is deleted from the RAP (110), when the UE2 (102-2) is in a disconnected state with the RAP (110).
17. The RAP (110) as claimed in claim 9, wherein the processor (202) is configured to
ascertain, whether the UE2 (102-2) is available in coverage areas of a second RAP (110), based on details of the UE2 (102-2) stored in a Session Initiation Protocol (SIP) server (114), when the UE2 (102-2) is determined to be in a disconnected state with the RAP (110); and
forward, the request to the second RAP (110), based on the ascertaining.
18. A non-transitory computer-readable medium having embodied thereon a computer program for executing a method for establishing a call between two user equipments (102), the method comprising:
receiving, by a processor (202), a request from a first user equipment (UE1) (102-1), for establishing a call with a second user equipment (UE2) (102-2);
determining, by the processor (202), whether the UE2 (102-2) is in a connected state with a Radio Access Point (RAP) (110), wherein the determining is based on information of the UE2 (102-2) stored as UE2 context in the RAP (110); and
establishing, by the processor (202), the call with the UE2 (102-2) based on the determining.
,TagSPECI:As Attached
| # | Name | Date |
|---|---|---|
| 1 | 1160-DEL-2014-AbandonedLetter.pdf | 2019-09-20 |
| 1 | Drawings_PD011194IN0SC-HeNB-VoIP-Alcatel-PS-Ver1-29-04-2014.pdf | 2014-04-29 |
| 2 | 1160-DEL-2014-FORM 4(ii) [05-03-2019(online)].pdf | 2019-03-05 |
| 2 | SPECIFICATION.pdf | 2014-05-02 |
| 3 | 1160-DEL-2014-FER.pdf | 2018-09-06 |
| 3 | GPOA.pdf | 2014-05-02 |
| 4 | 1160-del-2014-Correspondence Others-(13-06-2014).pdf | 2014-06-13 |
| 4 | FORM 5.pdf | 2014-05-02 |
| 5 | FORM 3.pdf | 2014-05-02 |
| 6 | 1160-del-2014-Correspondence Others-(13-06-2014).pdf | 2014-06-13 |
| 6 | FORM 5.pdf | 2014-05-02 |
| 7 | 1160-DEL-2014-FER.pdf | 2018-09-06 |
| 7 | GPOA.pdf | 2014-05-02 |
| 8 | 1160-DEL-2014-FORM 4(ii) [05-03-2019(online)].pdf | 2019-03-05 |
| 8 | SPECIFICATION.pdf | 2014-05-02 |
| 9 | 1160-DEL-2014-AbandonedLetter.pdf | 2019-09-20 |
| 9 | Drawings_PD011194IN0SC-HeNB-VoIP-Alcatel-PS-Ver1-29-04-2014.pdf | 2014-04-29 |
| 1 | searchstrategy_31-07-2018.pdf |