Supporting CBRS operation using non-real time ran intelligent controller (NON-RT RIC) applications
A wireless communications system includes radio components (O-RU, O-DU, O-CU), an ORAN Non-Real-Time RAN Intelligent Controller (Non-RT RIC) framework, an O-RU Controller and a CBSD Controller interfacing with a Spectrum Access System (SAS) using the Wireless Innovation Forum (WINNF) CBSD-SAS Interface. An example of CBSD Controller is a Domain Proxy (DP) defined by WINNF. The CBSD Controller is disclosed as an application belonging to the Non-RT RIC. This application could be an rApp. The Non RT MC Framework operates as a broker to route information between the O-RU Controller and the CBSD Controller. Data types are defined to be exchanged over the R1 interface.
1. An information routing system for a wireless communications network having radio components including Open Radio Access Network Radio Unit (O-RU), ORAN Distributed Unit (O-DU), and ORAN Centralized Unit (O-CU), said information routing system comprising:
an Open Radio Access Network (ORAN) Non-Real-Time RAN Intelligent Controller (Non-RT RIC) framework;
an O-RU Controller; and
a Citizens Broadband Radio Service Device (CBSD) Controller interfacing with a Spectrum Access System (SAS);
wherein the Non RT RIC Framework is configured to function as a broker to route information between the O-RU Controller and the CBSD Controller.
2. The system according to claim 1 , wherein the O-RU controller is configured as a producer of one of data type “ruInformation” or “ruInformationArray”, and the CBSD Controller is configured as a consumer of one of the data type “ruInformation” or “ruInformationArray”.
3. The system according to claim 2 , wherein the “ruInformation” data type contains at least one of the following parameters for a given O-RU:
RU Identity;
Component Carrier Identity, wherein each O-RU can support multiple component carriers in a Carrier Aggregation;
one of Common Channel Group (CCG) Identity or Single Frequency Group (SFG) Identity representing the group to which the given O-RU belongs, wherein all O-RUs obligated to use spectrum grants with the same frequency range must have one of the same CCG identity or the same SFG identity;
one of Interference Coordination Group (ICG) Identity or Spectrum Reuse Group (SRG) Identity representing a group of O-RUs that will not cause interference with one another in the case the O-Rus use spectrum grants with the same frequency range.
4. The system according to claim 2 , wherein the “ruInformationArray” data type contains an array of at least one vector, each vector contains one “ruInformation” data type, and each vector contains information related to one O-RU.
5. The system according to claim 1 , wherein the CBSD Controller is configured as a producer of one of data type “ruSpectrumGrant” or “ruSpectrumGrantArray”, and the O-RU Controller is configured as a consumer of one of data type “ruSpectrumGrant” or “ruSpectrumGrantArray”.
6. The system according to claim 5 , wherein the “ruSpectrumGrant” data type contains at least one of the following parameters for a given O-RU:
RU Identity;
Component Carrier Identity, wherein each O-RU can support multiple component carriers in a Carrier Aggregation;
one of Common Channel Group (CCG) Identity or Single Frequency Group (SFG) Identity representing the group to which the given O-RU belongs, wherein all O-RUs obligated to use spectrum grants with the same frequency range must have one of the same CCG identity or the same SFG identity;
low frequency, representing the lower boundary of the granted frequency range;
high frequency, representing the upper boundary of the granted frequency range; and
maximum Effective Isotropic Radiated Power (EIRP) likely to be permitted for the granted frequency range.
7. The system according to claim 5 , wherein the “ruSpectrumGrantArray” data type contains an array of at least one vector, each vector contains one “ruSpectrumGrant” data type, and each vector contains information related to one O-RU.
8. The system according to claim 1 , wherein the CBSD Controller is configured as an application, as part of Non-RT RIC domain.
9. The system according to claim 8 , wherein rApp is an application as defined by the O-RAN specifications, and wherein the CBSD Controller application is a Non-RT RIC rApp.
10. A method of routing information for a wireless communications system having radio components including Open Radio Access Network Radio Unit (O-RU), ORAN Distributed Unit (O-DU), and ORAN Centralized Unit (O-CU), the method comprising:
providing an Open Radio Access Network (ORAN) Non-Real-Time RAN Intelligent Controller (Non-RT RIC) framework;
providing an O-RU Controller; and
providing a Citizens Broadband Radio Service Device (CBSD) Controller interfacing with a Spectrum Access System (SAS);
wherein the Non-RT RIC Framework functions as a broker to route information between the O-RU Controller and the CBSD Controller.
11. The method according to claim 10 , further comprising:
utilizing the O-RU Controller as a producer of one of data type “ruInformation” or “ruInformationArray”; and
utilizing the CBSD Controller as a consumer of one of the data type “ruInformation” or “ruInformationArray”.
12. The method according to claim 11 , wherein the “ruInformation” data type contains at least one of the following parameters for a given O-RU:
RU Identity;
Component Carrier Identity, wherein each O-RU can support multiple component carriers in a Carrier Aggregation;
one of Common Channel Group (CCG) Identity or Single Frequency Group (SFG) Identity representing the group to which the given O-RU belongs, wherein all O-RUs obligated to use spectrum grants with the same frequency range must have one of the same CCG identity or the same SFG identity;
one of Interference Coordination Group (ICG) Identity or Spectrum Reuse Group (SRG) Identity representing a group of O-RUs that will not cause interference with one another in the case the O-Rus use spectrum grants with the same frequency range.
13. The method according to claim 11 , wherein the “ruInformationArray” data type contains an array of at least one vector, each vector contains one “ruInformation” data type, and each vector contains information related to one O-RU.
14. The method according to claim 10 , further comprising:
utilizing the CBSD Controller as a producer of one of data type “ruSpectrumGrant” or “ruSpectrumGrantArray”; and
utilizing the O-RU Controller as a consumer of one of data type “ruSpectrumGrant” or “ruSpectrumGrantArray”.
15. The method according to claim 14 , wherein the “ruSpectrumGrant” data type contains at least one of the following parameters for a given O-RU:
RU Identity;
Component Carrier Identity, wherein each O-RU can support multiple component carriers in a Carrier Aggregation;
one of Common Channel Group (CCG) Identity or Single Frequency Group (SFG) Identity representing the group to which the given O-RU belongs, wherein all O-RUs obligated to use spectrum grants with the same frequency range must have one of the same CCG identity or the same SFG identity;
low frequency, representing the lower boundary of the granted frequency range;
high frequency, representing the upper boundary of the granted frequency range; and
maximum Effective Isotropic Radiated Power (EIRP) likely to be permitted for the granted frequency range.
16. The method according to claim 14 , wherein the “ruSpectrumGrantArray” data type contains an array of at least one vector, each vector contains one “ruSpectrumGrant” data type, and each vector contains information related to one O-RU.
17. The method according to claim 10 , wherein the CBSD Controller is configured as an application, as part of Non-RT RIC domain.
18. The method according to claim 17 , wherein rApp is an application as defined by the O-RAN specifications, and wherein the CBSD Controller application is a Non-RT RIC rApp.
19. The method according to claim 11 , further comprising at least one of:
i) the O-RU Controller registers the data type “ruInformation”;
ii) the Non-RT RIC Framework sets up a routing rule specifying the O-RU Controller as the producer of the data type “ruInformation”; and
iii) the Non-RT RIC Framework sets up a routing rule specifying the CBSD Controller as the consumer of the data type “ruInformation”.