IP Library Granted Patent US 12,413,475
Granted Patent B2
US 12,413,475 · App. 18/550,276 · Granted Sep 9, 2025

A1 policy functions for open radio access network (O-RAN) systems

Inventors: Dawei Ying (Hillsboro, OR); Leifeng Ruan (Beijing, CN); Jaemin Han (Portland, OR); Qian Li (Beaverton, OR)
Assignee: Intel Corporation
H04L41/0894
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,413,475
App. No.
18/550,276
Filed
Sep 12, 2023
Granted
Sep 9, 2025
Kind
B2
Art Unit
2454
USPC
709/223
Abstract

The present invention relates to an apparatus comprising: memory to store policy statement information for a plurality of radio access network (RAN) automation applications (rApps); and processing circuitry, coupled with the memory, to: retrieve the policy statement information from the memory, wherein the policy statement information includes respective policy scope identifiers for respective rApps in the plurality of rApps; identify a conflict associated with common or overlapping policy scope identifiers between two or more rApps from the plurality of rApps; modify one or more A1 policies associated with an A1 interface connecting a non-real-time (non-RT) RAN intelligence controller (RIC) and a near-real-time (near-RT) RIC to resolve the conflict; and notify the two or more rApps of the modification of the one or more A1 policies.

Claims (60)

1. An apparatus comprising:

memory to store policy statement information for a plurality of radio access network (RAN) automation applications (rApps); and

processor circuitry, coupled with the memory, to:

retrieve the policy statement information from the memory, wherein the policy statement information includes respective policy scope identifiers for respective rApps in the plurality of rApps;

identify a conflict associated with common or overlapping policy scope identifiers between two or more rApps from the plurality of rApps;

modify one or more A1 policies associated with an A1 interface connecting a non-real-time (non-RT) RAN intelligence controller (RIC) and a near-real-time (near-RT) RIC to resolve the conflict; and

notify the two or more rApps of the modification of the one or more A1 policies.

2. The apparatus of claim 1 , wherein the processor circuitry is further to:

track an enforcement status of an A1 policy created in the non-RT RIC; and

notify an rApp subscribed to the tracked A1 policy when the enforcement status of the tracked A1 policy changes.

3. The apparatus of claim 1 , wherein the processor circuitry is further to track a supported A1 policy type for each of a plurality of near-RT RICs.

4. The apparatus of claim 3 , wherein the processor circuitry is to notify an rApp of a supported A1 policy type for a near-RT RIC based on a policy identifier.

5. The apparatus of claim 3 , wherein the processor circuitry is to notify an rApp of a change in supported policy types for a near-RT RIC.

6. The apparatus of claim 1 , wherein the processor circuitry is further to generate an A1-related service that includes: a RAN intent discovery service, an A1 policy management service, or an A1 policy type discovery service.

7. The apparatus of claim 1 , wherein the processor circuitry is further to:

receive a supported A1 policy types query request via an R1 termination; and

in response to the supported A1 policy types query request, send a query response that includes an indication of supported A1 policy types to a policy generation rApp via the R1 termination.

8. The apparatus of claim 1 , wherein the processor circuitry is further to:

receive an A1 policy feedback message from the near-RT RIC via an A1 termination to indicate a change of A1 policy enforcement status; and

send a notification of the A1 policy enforcement status change to a policy generation rApp via an R1 termination.

9. The apparatus of claim 1 , wherein the processor circuitry is further to:

receive an A1 policy modification request from a policy generation rApp via an R1 termination;

update an A1 policy over the A1 interface based on the A1 policy modification request; and

send an A1 policy modification response to the policy generation rApp via the R1 termination.

10. The apparatus of claim 1 , wherein the processor circuitry is further to:

receive an A1 policy deletion request from a policy generation rApp via an R1 termination;

remove an A1 policy over the A1 interface based on the A1 policy deletion request; and

send an A1 policy deletion response to the policy generation rApp via the R1 termination.

11. One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause an A1 policy function to:

identify a conflict associated with common or overlapping policy scope identifiers between two or more radio access network (RAN) automation applications (rApps) from a plurality of rApps based on policy statement information that includes respective policy scope identifiers for respective rApps in the plurality of rApps;

modify one or more A1 policies associated with an A1 interface connecting a non-real-time (non-RT) RAN intelligence controller (RIC) and a near-real-time (near-RT) RIC to resolve the conflict; and

notify the two or more rApps of the modification of the one or more A1 policies.

12. The one or more non-transitory computer-readable media of claim 11 , wherein the media further stores instructions to:

track an enforcement status of an A1 policy created in the non-RT RIC; and

notify an rApp subscribed to the tracked A1 policy when the enforcement status of the tracked A1 policy changes.

13. The one or more non-transitory computer-readable media of claim 11 , wherein the media further stores instructions to:

track a supported A1 policy type for each of a plurality of near-RT RICs; and

notify an rApp of a supported A1 policy type for a near-RT RIC based on a policy identifier; or

notify an rApp of a change in supported policy types for a near-RT RIC.

14. The one or more non-transitory computer-readable media of claim 11 , wherein the media further stores instructions to:

receive a supported A1 policy types query request via an R1 termination; and

in response to the supported A1 policy types query request, send a query response that includes an indication of supported A1 policy types to a policy generation rApp via the R1 termination.

15. The one or more non-transitory computer-readable media of claim 11 , wherein the media further stores instructions to:

receive an A1 policy feedback message from the near-RT RIC via an A1 termination to indicate a change of A1 policy enforcement status; and

send a notification of the A1 policy enforcement status change to a policy generation rApp via an R1 termination.

16. The one or more non-transitory computer-readable media of claim 11 , wherein the media further stores instructions to:

receive an A1 policy modification request from a policy generation rApp via an R1 termination;

update an A1 policy over the A1 interface based on the A1 policy modification request; and

send an A1 policy modification response to the policy generation rApp via the R1 termination.

17. The one or more non-transitory computer-readable media of claim 11 , wherein the media further stores instructions to generate an A1-related service that includes: a RAN intent discovery service, an A1 policy management service, or an A1 policy type discovery service.

18. One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause an A1 policy function to:

identify a conflict associated with common or overlapping policy scope identifiers between two or more radio access network (RAN) automation applications (rApps) from a plurality of rApps based on policy statement information that includes respective policy scope identifiers for respective rApps in the plurality of rApps;

modify one or more A1 policies associated with an A1 interface connecting a non-real-time (non-RT) RAN intelligence controller (RIC) and a near-real-time (near-RT) RIC to resolve the conflict;

notify the two or more rApps of the modification of the one or more A1 policies; and

track a supported A1 policy type for each of a plurality of near-RT RICs, and either: notify an rApp of a supported A1 policy type for a near-RT RIC based on a policy identifier, or notify an rApp of a change in supported policy types for a near-RT RIC.

19. The one or more non-transitory computer-readable media of claim 18 , wherein the media further stores instructions to send, to an rApp via an R1 termination, one or more of;

an indication of a change in an enforcement status of a tracked A1 policy;

an indication of supported A1 policy types; and

a notification of an A1 policy enforcement status change.

20. The one or more non-transitory computer-readable media of claim 18 , wherein the media further stores instructions to generate an A1-related service that includes: a RAN intent discovery service, an A1 policy management service, or an A1 policy type discovery service.

Continuity (2)
Provisional Application 63218861 · Jul 6, 2021
Related Publication 20240214272A1 · Jun 27, 2024
References Cited (13)
US 20200329381A1 · Chou et al. · 2020 [cited by applicant]
US 20210184989A1 · Wu et al. · 2021 [cited by applicant]
US 20210241090A1 · Chen · 2021 [cited by examiner]
US 20220295309A1 · Akhtar · 2022 [cited by examiner]
WO 2021048831A1 · 2021 [cited by applicant]
O-RAN, “O-RAN Architecture Description,” O-RAN.WG1.O-RAN-Architecture-Description-v04.00, 2021 by O-RAN Alliance e.V., Alfter, Germany, 33 pages. [cited by applicant]
O-RAN, “O-RAN Working Group 3 Near-Real-time RAN Intelligent Controller Near-RT RIC Architecture,” O-RAN.WG3. RICARCH-v02.00, 2021 by O-RAN Alliance e.V., Alfter, Germany, 59 pages. [cited by applicant]
O-RAN, “O-RAN Working Group 2 Non-RT RIC Architecture,” O-RAN.WG2.Non-RT-RIC-ARCH-TS-v01.00, 2021 by O-RAN Alliance e.V., Alfter, Germany, 17 pages. [cited by applicant]
O-RAN, “O-RAN Working Group 2 Non-RT RIC: Functional Architecture,” O-RAN.WG2.Non-RT-RIC-ARCH-TR-v01.01, 2021 by O-RAN Alliance e.V., Alfter, Germany, 51 pages. [cited by applicant]
O-RAN, “O-RAN Working Group 2 (Non-RT RIC and A1 interface WG) A1 interface: General Aspects and Principles,” O-RAN.WG2.A1GAP-v02.02, 2021 by O-RAN Alliance e.V., Alfter, Germany, 21 pages. [cited by applicant]
International Patent Office—International Search Report and Written Opinion mailed Oct. 26, 2022, from International Patent Application No. PCT/US2022/036130, 10 pages. [cited by applicant]
Westerberg, et al., “The innovation potential of Non Real-time RAN Intelligent Controller,” Ericssion Blog, Innovation potential of Non Real-time RIC—Ericsson, website: https://www.ericsson.com/en/blog/2020/10/innovatio… [cited by applicant]
Qualcomm Incorporated, “NWDAF Decompose Architecture,” SA WG2 Meeting #139E, S2-2003862, Agenda Item: 8.2, Jun. 1,-Jun. 12, 2020, Elbonia, 4 pages. [cited by applicant]
Cited By (1)
US 12,718,415