Abstract: This disclosure relates generally to cloud radio access network (C-RAN), and more particularly to X2-messaging in the C-RAN. The method may include receiving, by a control unit in the CRAN, in the C-RAN, a request from a first virtual eNodeB (eNB) associated with a source eNodeB (eNB) to establish a X2 interface with each virtual eNB associated with a set of neighbor eNBs. A second virtual eNB associated with a target eNB may be selected from the virtual eNBs associated with the set of neighbor eNBs. A check may be made to determine whether the first virtual eNB and the second virtual eNB associated with the target eNB are co-located on same datacenter in the C-RAN. At least one X2 message may be transmitted between the first virtual eNB and the second virtual eNB that are co-located on the datacenter based on eNB information accessed from a shared storage. FIG. 2
Claims:WE CLAIM
1. A method of X2-messaging in a Cloud Radio Access Network (C-RAN), the method comprising:
receiving, by a control unit in the C-RAN, a request from a first virtual eNodeB (eNB) associated with a source eNodeB (eNB) to establish a X2 interface with each virtual eNB associated with a set of neighbor eNBs;
selecting, by the control unit, a second virtual eNB associated with a target eNB from the virtual eNBs associated with the set of neighbor eNBs;
determining, by the control unit, whether the first virtual eNB associated with the source eNB and the second virtual eNB associated with the target eNB are co-located and/or running on same datacenter in the C-RAN;
transmitting, by the control unit, at least one X2 message between the first virtual eNB and the second virtual eNB based on eNB information accessed from a shared storage when the first virtual eNB and the second virtual eNB are co-located on the datacenter; and
performing at least one X2 interface function on at least one of the source eNB and the target eNB based on the at least one X2 message transmitted between the first virtual eNB and the second virtual eNB.
2. The method of claim 1, wherein the at least one X2 interface function comprises at least one of handover coordination and load management between the source eNB and the target eNB.
3. The method of claim 2, wherein selecting the second virtual eNB associated with the target eNB from the virtual eNBs associated with the set of neighbor eNBs, comprises:
receiving, by the control unit, a request from the first virtual eNB to perform the handover coordination with one of the set of neighbor eNBs associated with the first virtual eNB;
obtaining, by the control unit, information associated with user equipment (UE) capacity and Radio Resource Control (RRC) connections of the first virtual eNB and each virtual eNB associated with the set of neighbor eNBs; and
selecting, by the control unit, the second virtual eNB associated with the target eNB from the set of neighbor eNBs by analyzing the UE capacity and the RRC connections of each virtual eNB based on a predefined criteria.
4. The method of claim 3, further comprising:
determining, by the control unit, a decision to establish at least one RRC connection from the target eNB associated with the second virtual eNB to the UE;
retrieving, by the control unit, configuration setting associated with the at least one RRC connection to be established from the target eNB to the UE; and
instructing the source eNB to share the configuration setting associated with the at least one RRC connection to the UE.
5. The method of claim 4, further comprising:
updating, in a shared storage, a new RRC connection established from the target eNB to the UE; and
automatically updating a set of neighboring eNBs of the target eNB and configuration settings associated with the set of neighboring eNBs list to perform a subsequent handover coordination.
6. The method of claim 2, wherein performing the load management based on the at least one X2 message transmitted between the first virtual eNB and the second virtual eNB, comprises:
receiving, by the control unit, a request from the first virtual eNB to perform the load management with one of a set of neighbor eNBs associated with the first virtual eNB;
obtaining by the control unit, information associated with user equipment (UE) capacity and Radio Resource Control (RRC) connections of the first virtual eNB and the set of neighbor eNBs;
selecting, by the control unit, the second virtual eNB from the set of neighbor eNBs by analyzing the UE capacity and the RRC connections of each virtual eNB based on a predefined criteria; and
determining, by the control unit, a decision to exchange overload and traffic load information between the source eNB and the target eNB associated with the second virtual eNB.
7. The method of claim 1, wherein the at least one X2 message comprises X2 Application Protocol (X2-AP) messages and General Packet Radio Service (GPRS) Tunneling Protocol (GTP) messages.
8. The method of claim 7, wherein the X2-AP messages are transmitted between the first virtual eNB and the second virtual eNB to perform load management and handover coordination at the source eNB and the target eNB.
9. The method of claim 7, wherein the GTP messages are transmitted from the first virtual eNB to the second virtual eNB to forward UE downlink data buffered at the source eNB to the target eNB.
10. The method of claim 1, wherein transmitting, by the control unit, at least one X2 message between the first virtual eNB and the second virtual eNB through inter-process communication.
11. The method of claim 1, wherein the inter-process communication is performed by one of named-pipe, memory-mapped file, message queue, and a shared storage in the C-RAN.
12. A Cloud Radio Access Network (C-RAN) comprising:
a plurality of virtual eNodeBs; and
a control unit communicatively connected to each virtual eNodeB, wherein the control unit is to:
receive a request from a first virtual eNB associated with a source eNodeB (eNB) to establish a X2 interface with each virtual eNB associated with a set of neighbor eNBs;
select a second virtual eNB associated with a target eNB from the virtual eNBs associated with the set of neighbor eNBs;
determine whether a first virtual eNB associated with the source eNB and a second virtual eNB associated with the target eNB are co-located and/or running on same datacenter in the C-RAN;
transmit at least one X2 message between the first virtual eNB and the second virtual eNB based on eNB information accessed from a shared storage when the first virtual eNB and the second virtual eNB are co-located on the datacenter; and
perform at least one X2 interface function on at least one of the source eNB and the target eNB based on the at least one X2 message transmitted between the first virtual eNB and the second virtual eNB.
13. The C-RAN of claim 12, wherein the at least one X2 interface function comprises at least one of handover coordination and load management between the source eNB and the target eNB.
14. The C-RAN of claim 12, wherein the control unit selects the second virtual eNB associated with a target eNB from the virtual eNBs associated with the set of neighbor eNBs by:
obtaining information associated with user equipment (UE) capacity and Radio Resource Control (RRC) connections of the first virtual eNB associated with the source eNB and each virtual eNB associated with the set of neighbor eNBs;
analyzing the UE capacity and the RRC connections of each virtual eNB associated with the set of neighbor eNBs based on a predefined criteria; and
selecting the second virtual eNB associated with the target eNB by analysis.
15. The C-RAN of claim 12, wherein the at least one X2 message comprises X2 Application Protocol (X2-AP) messages and General Packet Radio Service (GPRS) Tunneling Protocol (GTP) messages.
16. The C-RAN of claim 15, wherein the X2-AP messages are transmitted between the first virtual eNB and the second virtual eNB to perform load management and handover coordination at the source eNB and the target eNB.
17. The C-RAN of claim 15, wherein the GTP messages are transmitted from the first virtual eNB to the second virtual eNB to forward UE downlink data buffered at the source eNB to the target eNB.
18. The C-RAN of claim 12, wherein transmitting, by the control unit, at least one X2 message between the first virtual eNB and the second virtual eNB through inter-process communication.
19. The C-RAN of claim 18, wherein the inter-process communication is performed by one of named-pipe, memory-mapped file, message queue, and a shared storage in the C-RAN.
20. A non-transitory computer-readable storage medium having stored thereon, a set of computer-executable instructions causing a cloud radio access network (C-RAN) comprising one or more processors to:
receive, by a control unit in the C-RAN, a request from a first virtual eNodeB (eNB) associated with a source eNodeB (eNB) to establish a X2 interface with each virtual eNB associated with a set of neighbor eNBs;
select, by the control unit, a second virtual eNB associated with a target eNB from the virtual eNBs associated with the set of neighbor eNBs;
determine, by the control unit, whether the first virtual eNB associated with the source eNB and the second virtual eNB associated with the target eNB are co-located and/or running on same datacenter in the C-RAN;
transmit, by the control unit, at least one X2 message between the first virtual eNB and the second virtual eNB based on eNB information accessed from a shared storage when the first virtual eNB and the second virtual eNB are co-located on the datacenter; and
perform at least one X2 interface function on at least one of the source eNB and the target eNB based on the at least one X2 message transmitted between the first virtual eNB and the second virtual eNB.
Dated this 20th day of March, 2018
R Ramya Rao
Of K&S Partners
Agent for the Applicant
IN/PA-1607 , Description:TECHNICAL FIELD
This disclosure relates generally to X2 interface messaging, and more particularly to X2 interface messaging in a cloud radio access network (CRAN).
| # | Name | Date |
|---|---|---|
| 1 | 201841010090-STATEMENT OF UNDERTAKING (FORM 3) [20-03-2018(online)].pdf | 2018-03-20 |
| 2 | 201841010090-REQUEST FOR EXAMINATION (FORM-18) [20-03-2018(online)].pdf | 2018-03-20 |
| 3 | 201841010090-POWER OF AUTHORITY [20-03-2018(online)].pdf | 2018-03-20 |
| 4 | 201841010090-FORM 18 [20-03-2018(online)].pdf | 2018-03-20 |
| 5 | 201841010090-FORM 1 [20-03-2018(online)].pdf | 2018-03-20 |
| 6 | 201841010090-DRAWINGS [20-03-2018(online)].pdf | 2018-03-20 |
| 7 | 201841010090-DECLARATION OF INVENTORSHIP (FORM 5) [20-03-2018(online)].pdf | 2018-03-20 |
| 8 | 201841010090-COMPLETE SPECIFICATION [20-03-2018(online)].pdf | 2018-03-20 |
| 9 | abstract 201841010090.jpg | 2018-03-21 |
| 10 | 201841010090-REQUEST FOR CERTIFIED COPY [04-05-2018(online)].pdf | 2018-05-04 |
| 11 | 201841010090-Proof of Right (MANDATORY) [17-08-2018(online)].pdf | 2018-08-17 |
| 12 | Correspondence by Agent_Form1_23-08-2018.pdf | 2018-08-23 |
| 13 | 201841010090-REQUEST FOR CERTIFIED COPY [01-10-2018(online)].pdf | 2018-10-01 |
| 14 | 201841010090-PETITION UNDER RULE 137 [28-04-2021(online)].pdf | 2021-04-28 |
| 15 | 201841010090-OTHERS [28-04-2021(online)].pdf | 2021-04-28 |
| 16 | 201841010090-Information under section 8(2) [28-04-2021(online)].pdf | 2021-04-28 |
| 17 | 201841010090-FORM 3 [28-04-2021(online)].pdf | 2021-04-28 |
| 18 | 201841010090-FER_SER_REPLY [28-04-2021(online)].pdf | 2021-04-28 |
| 19 | 201841010090-DRAWING [28-04-2021(online)].pdf | 2021-04-28 |
| 20 | 201841010090-CORRESPONDENCE [28-04-2021(online)].pdf | 2021-04-28 |
| 21 | 201841010090-CLAIMS [28-04-2021(online)].pdf | 2021-04-28 |
| 22 | 201841010090-ABSTRACT [28-04-2021(online)].pdf | 2021-04-28 |
| 23 | 201841010090-FER.pdf | 2021-10-17 |
| 24 | 201841010090-PatentCertificate11-12-2023.pdf | 2023-12-11 |
| 25 | 201841010090-IntimationOfGrant11-12-2023.pdf | 2023-12-11 |
| 26 | 201841010090-PROOF OF ALTERATION [10-04-2024(online)].pdf | 2024-04-10 |
| 1 | 2020-11-0412-09-45E_04-11-2020.pdf |