ENTITY ACCESS FOR AN APPLICATION

Apparatuses, methods, and systems are disclosed for entity access for an application. One method includes receiving, by a first entity, an application registry request for at least one application. The method includes determining whether the at least one application is enabled to access at least one management entity or at least one managed entity.

FIELD

The subject matter disclosed herein relates generally to wireless communications and more particularly relates to entity access for an application.

BACKGROUND

The following abbreviations are herewith defined, at least some of which are referred to within the following description: Third Generation Partnership Project (“3GPP”), 5thGeneration (“5G”), 5G System (“5GS”), 5G QoS Indicator (“5QI”), Authentication, Authorization, and Accounting (“AAA”), Positive-Acknowledgment (“ACK”), Application Function (“AF”), Automated Guided Vehicles (“AGV”), Artificial Intelligence (“AI”), Authentication and Key Agreement (“AKA”), Aggregation Level (“AL”), Access and Mobility Management Function (“AMF”), Angle of Arrival (“AoA”), Angle of Departure (“AoD”), Access Point (“AP”), Application Programmable Interface (“API”), Augmented Reality (“AR”), Access Stratum (“AS”), Application Service Provider (“ASP”), Autonomous Uplink (“AUL”), Authentication Server Function (“AUSF”), Authentication Token (“AUTN”), Background Data (“BD”), Background Data Transfer (“BDT”), Beam Failure Detection (“BFD”), Beam Failure Recovery (“BFR”), Binary Phase Shift Keying (“BPSK”), Base Station (“BS”), Buffer Status Report (“BSR”), Bandwidth (“BW”), Bandwidth Part (“BWP”), Control to Control (“C2C”), Cell RNTI (“C-RNTI”), Carrier Aggregation (“CA”), Channel Access Priority Class (“CAPC”), Common API Framework (“CAPIF”), Channel Busy Ratio (“CBR”), Contention-Based Random Access (“CBRA”), Clear Channel Assessment (“CCA”), Common Control Channel (“CCCH”), Control Channel Element (“CCE”), Cyclic Delay Diversity (“CDD”), Code Division Multiple Access (“CDMA”), Control Element (“CE”), Contention-Free Random Access (“CFRA”), Configured Grant (“CG”), Closed-Loop (“CL”), Core Network (“CN”), Coordinated Multipoint (“CoMP”), Category of Requirements (“CoR”), Channel Occupancy Time (“COT”), Cyclic Prefix (“CP”), Channel Quality Indicator (“CQI”), Cyclical Redundancy Check (“CRC”), Communication Service (“CS”), Channel State Information (“CSI”), Channel State Information-Reference Signal (“CSI-RS”), Common Search Space (“CSS”), Control Resource Set (“CORESET”), Discrete Fourier Transform Spread (“DFTS”), Dual Connectivity (“DC”), Downlink Control Information (“DCI”), Downlink Feedback Information (“DFI”), Dynamic Grant (“DG”), Downlink (“DL”), Demodulation Reference Signal (“DMRS”), Data Network (“DN”), Data Network Name (“DNN”), Data Radio Bearer (“DRB”), Discontinuous Reception (“DRX”), Dedicated Short-Range Communications (“DSRC”), Downlink Pilot Time Slot (“DwPTS”), Enhanced Clear Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), Enhanced V2X (“eV2X”), Extensible Authentication Protocol (“EAP”), Edge Configuration Server (“ECS”), Edge Enabler Client (“EEC”), Edge Enabler Server (“EES”), Enhanced ICIC (“eICIC”), Effective Isotropic Radiated Power (“EIRP”), Evolved Packet System (“EPS”), European Telecommunications Standards Institute (“ETSI”), Frame Based Equipment (“FBE”), Frequency Division Duplex (“FDD”), Frequency Division Multiplexing (“FDM”), Frequency Division Multiple Access (“FDMA”), Frequency Division Orthogonal Cover Code (“FD-OCC”), Factory of the Future (“FF”), Frequency Range 1—sub 6 GHz frequency bands and/or 410 MHz to 7125 MHz (“FR1”), Frequency Range 2-24.25 GHz to 52.6 GHz (“FR2”), Universal Geographical Area Description (“GAD”), Guaranteed Bit Rate (“GBR”), Guaranteed Flow Bit Rate (“GFBR”), Group Leader (“GL”), 5G Node B or Next Generation Node B (“gNB”), Global Navigation Satellite System (“GNSS”), General Packet Radio Services (“GPRS”), Guard Period (“GP”), Global Positioning System (“GPS”), Generic Public Subscription Identifier (“GPSI”), Global System for Mobile Communications (“GSM”), Generic Network Slice Template (“GST”), Globally Unique Temporary UE Identifier (“GUTI”), Home AMF (“hAMF”), Hybrid Automatic Repeat Request (“HARQ”), Home Location Register (“HLR”), Handover (“HO”), Home PLMN (“HPLMN”), Home Subscriber Server (“HSS”), Hash Expected Response (“HXRES”), Inter-cell Interference Coordination (“ICIC”), Identity or Identifier (“ID”), Information Element (“IE”), Industrial Internet of Things (“IIoT”), International Mobile Equipment Identity (“IMEI”), International Mobile Subscriber Identity (“IMSI”), International Mobile Telecommunications (“IMT”), Information Object Class (“IoC”), Internet-of-Things (“IoT”), Intelligent Transportation Systems (“ITS”), Key Performance Indicator (“KPI”), Layer 1 (“L1”), Layer 2 (“L2”), Layer 3 (“L3”), Licensed Assisted Access (“LAA”), Local Area Data Network (“LADN”), Local Area Network (“LAN”), Load Based Equipment (“LBE”), Listen-Before-Talk (“LBT”), Logical Channel (“LCH”), Logical Channel Group (“LCG”), Logical Channel Prioritization (“LCP”), Log-Likelihood Ratio (“LLR”), Level of Automation (“LoA”), Line of Sight (“LOS”), Long Term Evolution (“LTE”), LTE Vehicle (“LTE-V”), Multiple Access (“MA”), Medium Access Control (“MAC”), Multimedia Broadcast Multicast Services (“MBMS”), Maximum Bit Rate (“MBR”), Minimum Communication Range (“MCR”), Modulation Coding Scheme (“MCS”), Management Domain (“MD”), Managed Element (“ME”), Mobile Edge Computing (“MEC”), Master Information Block (“MIB”), Massive IoT (“mIoT”), Multiple Input Multiple Output (“MIMO”), Machine Learning (“ML”), Mobility Management (“MM”), Mobility Management Entity (“MME”), Master Node (“MN”), Management Service (“MnS”), Mobile Network Operator (“MNO”), Mobile Originated (“MO”), Managed Object Instance (“MOI”), Mean Opinion Score (“MOS”), massive MTC (“mMTC”), Maximum Power Reduction (“MPR”), Multi-Radio Dual Connectivity (“MR-DC”), Machine Type Communication (“MTC”), Multiple Transmission and Reception Point (“M-TRP”), Multi User Shared Access (“MUSA”), Non Access Stratum (“NAS”), Narrowband (“NB”), Negative-Acknowledgment (“NACK”) or (“NAK”), New Data Indicator (“NDI”), Network Entity (“NE”), Network Exposure Function (“NEF”), Network Exposure Function/Service Capability Exposure Function (“NEF/SCEF”), NEtwork Slice Type (“NEST”), Network Function (“NF”), Non-LOS (“NLOS”), Next Generation (“NG”), NG 5G S-TMSI (“NG-5G-S-TMSI”), Neural Networks (“NN”), Non-Orthogonal Multiple Access (“NOMA”), Non Public Network (“NPN”), New Radio (“NR”), NR Unlicensed (“NR-U”), Network Repository Function (“NRF”), Network Slice as a Service (NsaaS), Network Scheduled Mode (“NS Mode”) (e.g., network scheduled mode of V2X communication resource allocation—Mode-1 in NR V2X and Mode-3 in LTE V2X), Network Slice Instance (“NSI”), Network Slice Selection Assistance Information (“NSSAI”), Network Slice Selection Function (“NSSF”), Network Slice Subnet Instance (“NSSI”), Network Slice Selection Policy (“NSSP”), Operation, Administration, and Maintenance System or Operation and Maintenance Center (“OAM”), Original Equipment Manufacturer (“OEM”), Orthogonal Frequency Division Multiplexing (“OFDM”), Orthogonal Frequency Division Multiple Access (“OFDMA”), Open-Loop (“OL”), Operator Defined Open and Intelligent Radio Access Networks (“O-RAN”), Other System Information (“OSI”), Over-the-top (“OTT”), Power Angular Spectrum (“PAS”), Physical Broadcast Channel (“PBCH”), Power Control (“PC”), UE to UE interface (“PC5”), Principal Component Analysis (“PCA”), Policy and Charging Control (“PCC”), Primary Cell (“PCell”), Policy and Charging Rules Function (“PCRF”), Policy Control Function (“PCF”), Physical Cell Identity (“PCI”), Physical Downlink Control Channel (“PDCCH”), Packet Data Convergence Protocol (“PDCP”), Packet Data Network Gateway (“PGW”), Physical Downlink Shared Channel (“PDSCH”), Pattern Division Multiple Access (“PDMA”), Packet Data Unit (“PDU”), Physical Hybrid ARQ Indicator Channel (“PHICH”), Power Headroom (“PH”), Power Headroom Report (“PHR”), Physical Layer (“PHY”), Public Land Mobile Network (“PLMN”), Precoding Matrix Index (“PMI”), Physical Network Function (“PNF”), Prose Per Packet Priority (“PPPP”), Prose Per Packet Reliability (“PPPR”), PC5 5QI (“PQIs”), Predictive QoS (“P-QoS”), Physical Random Access Channel (“PRACH”), Physical Resource Block (“PRB”), Proximity Services (“ProSe”), Positioning Reference Signal (“PRS”), Physical Sidelink Control Channel (“PSCCH”), Primary Secondary Cell (“PSCell”), Physical Sidelink Feedback Control Channel (“PSFCH”), Physical Uplink Control Channel (“PUCCH”), Physical Uplink Shared Channel (“PUSCH”), QoS Class Identifier (“QCI”), Quasi Co-Located (“QCL”), QoS Flow Indicator (“QFI”), Quality of Experience (“QoE”), Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”), Registration Area (“RA”), RA RNTI (“RA-RNTI”), Radio Access Network (“RAN”), Random (“RAND”), Radio Access Technology (“RAT”), Serving RAT (“RAT-I”) (serving with respect to Uu), Other RAT (“RAT-2”) (non-serving with respect to Uu), Random Access Procedure (“RACH”), Random Access Preamble Identifier (“RAPID”), Random Access Response (“RAR”), Resource Block Assignment (“RBA”), Resource Element Group (“REG”), Representational State Transfer (“REST”), Rank Indicator (“RI”), RAN Intelligent Controller (“RIC”), Radio Link Control (“RLC”), RLC Acknowledged Mode (“RLC-AM”), RLC Unacknowledged Mode/Transparent Mode (“RLC-UM/TM”), Radio Link Failure (“RLF”), Radio Link Monitoring (“RLM”), Radio Network Information (“RNI”), RNI Service (“RNIS”), Radio Network Temporary Identifier (“RNTI”), Reference Signal (“RS”), Recursive Model (“RM”), Remaining Minimum System Information (“RMSI”), Radio Resource Control (“RRC”), Radio Resource Management (“RRM”), Resource Spread Multiple Access (“RSMA”), Reference Signal Received Power (“RSRP”), Received Signal Strength Indicator (“RSSI”), Real Time (“RT”), Round Trip Time (“RTT”), Receive (“RX”), Service Capability Exposure Function (“SCEF”), Sparse Code Multiple Access (“SCMA”), Service Provider (“SP”), Scheduling Request (“SR”), Sounding Reference Signal (“SRS”), Single Carrier Frequency Division Multiple Access (“SC-FDMA”), Secondary Cell (“SCell”), Secondary Cell Group (“SCG”), Shared Channel (“SCH”), Sidelink Control Information (“SCI”), Sub-carrier Spacing (“SCS”), Space Division Multiplexing (“SDM”), Service Data Unit (“SDU”), Security Anchor Function (“SEAF”), Service Enabler Architecture Layer (“SEAL”), Sidelink Feedback Content Information (“SFCI”), Serving Gateway (“SGW”), System Information Block (“SIB”), SystemInformationBlockType1 (“SIB1”), SystemInformationBlockType2 (“SIB2”), Subscriber Identity/Identification Module (“SIM”), Signal-to-Interference-Plus-Noise Ratio (“SINR”), Sidelink (“SL”), Service Level Agreement (“SLA”), Sidelink Synchronization Signals (“SLSS”), Session Management (“SM”), Session Management Function (“SMF”), Secondary Node (“SN”), Special Cell (“SpCell”), Single Network Slice Selection Assistance Information (“S-NSSAI”), Semi-Persistent Scheduling (“SPS”), Scheduling Request (“SR”), Signaling Radio Bearer (“SRB”), Shortened TMSI (“S-TMSI”), Shortened TTI (“sTTI”), Synchronization Signal (“SS”), Survival Time (“ST”), Sidelink CSI RS (“S-CSI RS”), Sidelink PRS (“S-PRS”), Sidelink SSB (“S-SSB”), Synchronization Signal Block (“SSB”), Subscription Concealed Identifier (“SUCI”), Scheduling User Equipment (“SUE”), Supplementary Uplink (“SUL”), Subscriber Permanent Identifier (“SUPI”), Support Vector Machine (“SVM”), Tracking Area (“TA”), TA Identifier (“TAI”), TA Update (“TAU”), Timing Alignment Timer (“TAT”), Transport Block (“TB”), Transport Block Size (“TBS”), Transmission Configuration Indicator (“TCI”), Time-Division Duplex (“TDD”), Time Division Multiplex (“TDM”), Time Division Orthogonal Cover Code (“TD-OCC”), Time Domain Resource Allocation (“TDRA”), Temporary Mobile Subscriber Identity (“TMSI”), Time of Flight (“ToF”), Transmission Power Control (“TPC”), Transmission Reception Point (“TRP”), Time Sensitive Communication (“TSC”), Time Sensitive Assistance Information (“TSCAI”), Time Sensitive Networking (“TSN”), Transmission Time Interval (“TTI”), Transmit (“TX”), Unmanned Aircraft System (“UAS”), Uplink Control Information (“UCI”), Unified Data Management Function (“UDM”), Unified Data Repository (“UDR”), User Entity/Equipment (Mobile Terminal) (“UE”) (e.g., a V2X UE), UE Autonomous Mode (UE autonomous selection of V2X communication resource—e.g., Mode-2 in NR V2X and Mode-4 in LTE V2X. UE autonomous selection may or may not be based on a resource sensing operation), Uplink (“UL”), UL SCH (“UL-SCH”), Universal Mobile Telecommunications System (“UMTS”), User Plane (“UP”), UP Function (“UPF”), Uplink Pilot Time Slot (“UpPTS”), Uniform Resource Locator (“URL”), Ultra-reliability and Low-latency Communications (“URLLC”), UE Route Selection Policy (“URSP”), Vehicle-to-Vehicle (“V2V”), Vehicle-to-Everything (“V2X”), V2X Control Function (“V2XCF”), V2X UE (e.g., a UE capable of vehicular communication using 3GPP protocols), V2X Application Enabler (“VAE”), Visiting AMF (“vAMF”), Virtual Network Function (“VNF”), Visiting NSSF (“vNSSF”), Visiting PLMN (“VPLMN”), Virtual Reality (“VR”), Wide Area Network (“WAN”), and Worldwide Interoperability for Microwave Access (“WiMAX”).

In certain wireless communications networks, management entities or managed entities may be used.

BRIEF SUMMARY

Methods for entity access for an application are disclosed. Apparatuses and systems also perform the functions of the methods. One embodiment of a method includes receiving, by a first entity, an application registry request for at least one application. In some embodiments, the method includes determining whether the at least one application is enabled to access at least one management entity or at least one managed entity.

One apparatus for entity access for an application includes a receiver that receives an application registry request for at least one application. In various embodiments, the apparatus includes a processor that determines at least one management entity or at least one managed entity of the telecom management system based on the application registry request, wherein the at least one application is enabled to access the at least one management entity or the at least one managed entity.

DETAILED DESCRIPTION

FIG.1depicts an embodiment of a wireless communication system100for entity access for an application. In one embodiment, the wireless communication system100includes remote units102, and network units104. Even though a specific number of remote units102, and network units104are depicted inFIG.1, one of skill in the art will recognize that any number of remote units102, and network units104may be included in the wireless communication system100.

The network units104may be distributed over a geographic region. In certain embodiments, a network unit104may also be referred to and/or may include one or more of an access point, an access terminal, a base, a base station, a Node-B, an eNB, a gNB, a Home Node-B, a relay node, a device, a core network, an aerial server, a radio access node, an AP, NR, a network entity, an AMF, a UDM, a UDR, a UDM/UDR, a PCF, a RAN, an NSSF, an OAM, an SMF, a UPF, an application function, or by any other terminology used in the art. The network units104are generally part of a radio access network that includes one or more controllers communicably coupled to one or more corresponding network units104. The radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.

In one implementation, the wireless communication system100is compliant with NR protocols standardized in 3GPP, wherein the network unit104transmits using an OFDM modulation scheme on the DL and the remote units102transmit on the UL using a SC-FDMA scheme or an OFDM scheme. More generally, however, the wireless communication system100may implement some other open or proprietary communication protocol, for example, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, Bluetooth®, ZigBee, Sigfoxx, among other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

In various embodiments, a network unit104may receive, by a first entity, an application registry request for at least one application. In some embodiments, the network unit104may determine whether the at least one application is enabled to access at least one management entity or at least one managed entity. Accordingly, the network unit104may be used for entity access for an application. As used herein, a management entity may refer to any entity that manages another entity or device (e.g., a management entity may be a management domain, vendor device, vendor solution 5GS operator domain, 3GPP core, 3GPP RAN, cloud domain, datacenter, transport network, operator administrative domain, country domain, LCM, FCAPS management, API management, and so forth). Moreover, as used herein a managed entity may refer to any entity that is managed by another entity or device (e.g., a managed entity may be: API, CS, NSI, NSSI, network functions or other resources in telecom networks such as virtualized network function and/or physical entities such as PNFs).

FIG.2depicts one embodiment of an apparatus200that may be used for entity access for an application. The apparatus200includes one embodiment of the remote unit102. Furthermore, the remote unit102may include a processor202, a memory204, an input device206, a display208, a transmitter210, a receiver212, one or more network interfaces214, and one or more application interfaces216. In some embodiments, the input device206and the display208are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit102may not include any input device206and/or display208. In various embodiments, the remote unit102may include one or more of the processor202, the memory204, the transmitter210, and the receiver212, and may not include the input device206and/or the display208.

Although only one transmitter210and one receiver212are illustrated, the remote unit102may have any suitable number of transmitters210and receivers212. The transmitter210and the receiver212may be any suitable type of transmitters and receivers. In one embodiment, the transmitter210and the receiver212may be part of a transceiver.

FIG.3depicts one embodiment of an apparatus300that may be used for entity access for an application. The apparatus300includes one embodiment of the network unit104. Furthermore, the network unit104may include a processor302, a memory304, an input device306, a display308, a transmitter310, a receiver312, one or more network interfaces314, and one or more application interfaces316. As may be appreciated, the processor302, the memory304, the input device306, the display308, the transmitter310, and the receiver312may be substantially similar to the processor202, the memory204, the input device206, the display208, the transmitter210, and the receiver212of the remote unit102, respectively.

In certain embodiments, the receiver312may receive an application registry request for at least one application. In various embodiments, the processor302may determine at least one management entity or at least one managed entity of the telecom management system based on the application registry request, wherein the at least one application is enabled to access the at least one management entity or the at least one managed entity.

In some embodiments, a third party application, such as a V2X application, may use telecom management system services to manage telecom networks. In such embodiments, the telecom management system may need to be made aware of these applications. Moreover, in such embodiments, a telecommunication management system may refer to management systems according to a specification of telecom standard bodies such as 3GPP or ETSI.

In certain embodiments, network slicing is a key feature (e.g., 5G). In such embodiments, network slicing may introduce logical end-to-end sub-networks corresponding to different verticals. In some embodiments, network slicing may enable the deployment of multiple logical networks known as network slice instances offering 3rd parties and verticals customized communication services on the top of a shared infrastructure. In various embodiments, based on a physical network that might be operated by a public operator or an enterprise, 5G may provide the means to run multiple slices for different communication purposes. In certain embodiments, 5G may enable slices to be independently run and/or isolated from one another.

In some embodiments, a network slice instance (e.g., private or public slice) may include a RAN part and/or a CN part. In various embodiments, a sub-part of a network slice instance may be called a network slice subnet instance (NSSI) which may contain further NSSI.

In certain embodiments, there may be application support for slices, such as in 3GPP 5GS. In some embodiments, an application may use any one of the following managed entities: CS, NSI, NSSI, network functions or other resources in telecom networks such as virtualized network function and/or physical entities such as PNFs.

In various embodiments, there may be slice access with application preference. In certain embodiments, there may be scenarios in which applications (e.g., gaming applications, online video applications, etc.) may access 5GS over multiple slices for different services (e.g., based on user membership) and/or applications may have different priorities on different slices based on an ASP request. In some embodiments, different slices may be available in all provided frequencies or a sub-set of them (e.g., FR1 or FR2 only) based on MNO and ASP agreement and/or network capabilities to support a slice requirement.

In certain embodiments, a mobile network operator has provisioned a set of network slices (e.g., Slice #1, Slice #2, Slice #3) which may be used by different ASPs (e.g., Slice #1 for online video services, Slice #2 for gaming, Slice #3 for eMBB or IOT service).

In some embodiments, different ASPs may use slices (or a subset of them) for different services that they offer. Furthermore, in certain embodiments, if an application changes network slices to be accessed, the application may be agnostic to UEs accessing service and/or may be performed automatically.

In one example, users A and B (e.g., using UE1and UE2respectively) have installed game applications and video applications and may have high priorities based on their membership to the video and game services. The high priorities may enable the users A and B to connect automatically to Slice #1 and Slice #2 to guarantee their QoS compared with other users having a lower priority. The priority over the slices to be used by UE1and UE2may change based on an ASP request (e.g., a UE moves to a different service area or an area in which a certain frequency is not available, different slice load conditions, or 3rd party ASP rolls out new services and/or applications and the user membership changes).

In various embodiments, a management system of a 5GS operator (e.g., a management domain) may be aware of ASP applications as well as: 1) a kind of slice management related request each application may make; and/or 2) management data that the ASP may consume.

As used herein, non-RT RIC may mean: a logical function that enables non-real-time control and optimization of RAN elements and resources, AI/ML workflow including model training and updates, and policy-based guidance of applications and/or features in Near-RT RIC.

Moreover, as used herein, near-RT RIC and framework functions may mean: a logical function that enables near-real-time control and optimization of RAN elements and resources via fine-grained (e.g., UE basis, cell basis) data collection and actions over an E2 interface. Near-RT RIC may include near-RT RIC basic and/or framework functions which may include subscription management, conflict mitigation, E2 termination (“E2T”), and/or management services.

Furthermore, as used herein, management Services of an RIC platform may include Life-Cycle Management (“LCM”) of an xApp and/or fault, configuration, accounting, performance, security (“FCAPS”) management of Near-RT RIC. These services may be provided by a near-RT RIC to an xApp (e.g., via Open API) or from an SMO (Non-RT RIC) to xApps (via O1).

An xApp as used herein may mean: an application designed to run on a Near-RT RIC. Such an application may be likely to include one or more microservices and at a point of on-boarding may identify which data it consumes and which data it provides. The xApp application is independent of a Near-RT RIC and may be provided by any third party. E2 may enable a direct association between the xApp and RAN functionality.

Moreover, as used herein rApp may mean: an application similar to xApp which is designed to run on a Non-RT RIC. Furthermore, A1 may be an interface between non-RT RIC and Near-RT RIC to enable policy-driven guidance of Near-RT RIC applications and/or functions, and may support AI and/or ML workflow. E2 may refer to an interface connecting a Near-RT RIC and a NR system. Moreover, O1 may refer to an interface between orchestration & management entities and O-RAN managed elements.

In various embodiments, an E2 Node may be a logical node terminating an E2 interface. Moreover, in some embodiments, open API may be an interface between framework functions and xAPPs.

In some embodiments, open API and/or O-RAN API may refer to an interface between framework functions and xAPPs.

In certain embodiments, API management services may enable a RIC platform to provide support for O-RAN APIs (e.g., O-RAN APIs may be defined as open APIs within an O-RAN scope) which may be provided by either a RIC framework or xApps in a service-based manner. In particular, API management services may include: repository and/or registry services for the O-RAN APIs, services that enable discovery of registered O-RAN APIs, services to authenticate xApps for use of O-RAN APIs, and/or services that enable generic subscription and event notification.

In various embodiments, API management services may be accessed via an xApp enablement API by xApps for supporting API discovery, providing authentication, and generic subscription and event notification.

In some embodiments, an application support layer may be used for vertical applications (e.g., known as vertical application enabler layer) which may act as a middleware for exposing northbound APIs to verticals as well as to provide some server-client support functionalities for the connected devices.

In certain embodiments, to be able to use management services and data, management exposure for applications may need to be configured in a corresponding management system. In such embodiments, the management system may be aware of the applications. In various embodiments, a telecom management system may be made aware of applications to enable the applications to register with the telecom management system. In some embodiments, to be able to modify communication services, NSI, or other managed entities, an application may be made aware of a management system.

FIG.4is a communications diagram illustrating one embodiment of communications400for application registration with a telecom management system. The communications400include messages transmitted between an approving authority402(e.g., for an MD), an application registry service producer404(e.g., in an MD), an exposure gateway406(e.g., from MD, including exposure governance interface), a middleware408(e.g., or trusted application, preauthorized to use the application registry service producer404), and an application410(e.g., or applications). As may be appreciated, each communication of the communications400may include one or more messages.

As may be appreciated, in various embodiments: 1) the application410may be aware about which management domain to contact for appropriate service handling; 2) there may exist an application or middleware (e.g., the middleware408) trusted by the management domain that may use the application registry service producer404; and 3) the approving authority402management function may already know a correct exposure for a given application ID middleware408combination.

In a first communication412transmitted from the application410to the middleware408, the application410sends a request to register itself (e.g., registration request) with the middleware408optionally providing any one or more of the following: 1) an application identifier; 2) an identifier of a management domain to be registered to; 3) an indication of a level of exposure required and/or management services that need to be exposed; 4) management data to be exposed; 5) IoCs to be exposed; 6) authentication details of the application410; and/or 7) an associated managed entity in the managed domain (e.g., CS, NSI, NSSI, and so forth) that the application410is interested in.

In a second communication414transmitted from the middleware408to the exposure gateway406, the middleware408transmits the registration request to the exposure gateway406.

In a third communication416transmitted from the exposure gateway406to the application registry service producer404, the exposure gateway406transmits the registration request to the application registry service producer404(“ARSP”). With the second communication414and the third communication416, the middleware408authenticates the application410and authorizes that the application410is allowed to request registration with the MD. The middleware408sends a request to register the application410with the respective management domain's application registry service producer404. As may be appreciated, the registration request may be sent to the application registry service producer404via direct communication or the exposure gateway406. The registration request may include: 1) an application identifier (e.g., a way to identify the application410); 2) a call back interface to the application410; 3) an indication of the level of exposure or the management services that need to be exposed; 4) credentials of the application410; and/or 5) an associated managed entity in the managed domain (e.g., CS, NSI, NSSI, and so forth) that the application410is interested in.

In a fourth communication418transmitted from the application registry service producer404to the approving authority402, the application registry service producer404sends a request for application registration approval to the approving authority402(e.g., to determine whether the application410can access the requested exposure of management service, function, data, or MOI). The request may include an application ID, an exposure request type, and/or an exposure request ID.

In a fifth communication420transmitted from the approving authority402to the application registry service producer404, the approving authority402may send an approval to the application registry service producer404specifying the approved details (e.g., if the application410is approved). The approval may include an application ID, an exposure request type, and/or an exposure request ID.

In a sixth communication422transmitted from the application registry service producer404to the exposure gateway406, the application registry service producer404configures the exposure gateway406for the approved exposure for the application410. Configuration information for configuring the exposure gateway406may include an application ID, an exposure request type, and/or an exposure request ID.

In a seventh communication424transmitted from the exposure gateway406to the application registry service producer404, the exposure gateway406transmits an acknowledgement of successful configuration to the application registry service producer404.

In an eighth communication426transmitted from the application registry service producer404to the middleware408, the application registry service producer404transmits an acknowledgment of successful registration of the application410with the management domain to the middleware408. The eighth communication426may include access details for accessing the approved management functions, management services, management data, or MOIs.

In a nineth communication428transmitted from the middleware408to the application410, the middleware408forwards successful registration information and appropriate access details to the application410.

It should be noted that an order of the communications400may be changed from what is described above. Furthermore, the approving authority402and the application registry service producer404may be part of the same entity and/or device. In certain embodiments, the approving authority402may be a human entity such that the fourth communication418may be sent to a dashboard (e.g., computer screen) for the human to approve.

In a first embodiment, the communications400ofFIG.4may be implemented in a 3GPP system.FIG.5is a communications diagram illustrating the first embodiment of communications500for application registration with a telecom management system (e.g., 3GPP system). The communications500include messages transmitted between an approving authority502(e.g., for a 3GPP domain), an application registry service producer504(e.g., in the 3GPP domain), an exposure gateway506(e.g., to the 3GPP domain), a middleware508(e.g., or trusted application, preauthorized to use the application registry service producer504), and an application510(e.g., or applications). As may be appreciated, each communication of the communications500may include one or more messages.

Specifically,FIG.5presents a 3GPP specific embodiment in which applications (e.g., vertical applications) can register to a 3GPP management domain of an operator using the middleware508(e.g., SEAL server, any other vertical enabler server, or a CAPIF entity). The first embodiment may assume that: 1) the middleware508is trusted by the 3GPP management domain to use the application registry service producer504; 2) the application510knows which 3GPP management domain to connect to (e.g., via PLMN ID, or a REST interface URL); and 3) the approving authority502is preconfigured to know what exposures an application and middleware combination is authorized for a request.

In a first communication512transmitted from the application510to the middleware508, the application510sends a request to register itself (e.g., registration request) with the middleware508optionally providing any one or more of the following: 1) an application identifier; 2) an identifier of a 3GPP domain to be registered to (e.g., PLMN ID); 3) an indication of a level of exposure required and/or management services that need to be exposed; 4) management data to be exposed; 5) IoCs to be exposed; 6) authentication details of the application510; and/or 7) an associated managed entity in the managed domain (e.g., CS, NSI, NSSI, and so forth) that the application510is interested in.

In a second communication514transmitted from the middleware508to the exposure gateway506, the middleware508transmits the registration request to the exposure gateway506.

In a third communication516transmitted from the exposure gateway506to the application registry service producer504, the exposure gateway506transmits the registration request to the application registry service producer504(“ARSP”). With the second communication514and the third communication516, the middleware508authenticates the application510and authorizes that the application510is allowed to request registration with the 3GPP domain. The middleware508sends a request to register the application510with the respective management domain's application registry service producer504. As may be appreciated, the registration request may be sent to the application registry service producer504via direct communication or the exposure gateway506. The registration request may include: 1) an application identifier (e.g., a way to identify the application510); 2) a call back interface to the application510; 3) an indication of the level of exposure or the management services that need to be exposed; 4) credentials of the application510; and/or 5) an associated managed entity in the managed domain (e.g., CS, NSI, NSSI, and so forth) that the application510is interested in.

In a fourth communication518transmitted from the application registry service producer504to the approving authority502, the application registry service producer504sends a request for application registration approval to the approving authority502(e.g., to determine whether the application510can access the requested exposure of management service, function, data, or MOI). The request may include an application ID, an exposure request type, and/or an exposure request ID.

In a fifth communication520transmitted from the approving authority502to the application registry service producer504, the approving authority502may send an approval to the application registry service producer504specifying the approved details (e.g., if the application510is approved). The approval may include an application ID, an exposure request type, and/or an exposure request ID.

In a sixth communication522transmitted from the application registry service producer504to the exposure gateway506, the application registry service producer504configures the exposure gateway506for the approved exposure for the application510. Configuration information for configuring the exposure gateway506may include an application ID, an exposure request type, and/or an exposure request ID.

In a seventh communication524transmitted from the exposure gateway506to the application registry service producer504, the exposure gateway506transmits an acknowledgement of successful configuration to the application registry service producer504.

In an eighth communication526transmitted from the application registry service producer504to the middleware508, the application registry service producer504transmits an acknowledgment of successful registration of the application510with the management domain to the middleware508. The eighth communication526may include access details for accessing the approved management functions, management services, management data, or MOIs.

In a nineth communication528transmitted from the middleware508to the application510, the middleware508forwards successful registration information and appropriate access details to the application510.

In a second embodiment, the communications400ofFIG.4may be implemented in an O-RAN system.FIG.6is a communications diagram illustrating the second embodiment of communications600for application registration with a telecom management system (e.g., O-RAN system). The communications600include messages transmitted between an approving authority602(e.g., for a corresponding MD), an xApp registry service producer604, a API management services606(e.g., middleware, trusted application, preauthorized to use the xApp registry service producer604), and an xApp608(e.g., or xApps). As may be appreciated, each communication of the communications600may include one or more messages.

Specifically,FIG.6presents an O-RAN specific embodiment in which xApps may register to an RIC platform to use management services (e.g., offered by RIC or any O-RAN entity). The second embodiment may assume that: 1) the API management services606is trusted by the O-RAN management domain to use the xApp registry service producer604; 2) the xApp608knows which management domain to connect to (e.g., via a REST interface URL); and 3) the approving authority602is preconfigured to know what exposures an application and middleware combination is authorized for a request. Moreover, inFIG.6, the API management services606may be known to the xApp608via discovery and/or configuration.

In a first communication610transmitted from the xApp608to the API management services606, the xApp608sends a request to register itself (e.g., registration request) with the API management services606optionally providing any one or more of the following: 1) an xAPP identifier; 2) an identifier of an O-RAN operator and/or management domain to be registered to (e.g., O-RAN network ID); 3) an indication of a level of exposure required and/or management services that need to be exposed; 4) management data to be exposed; 5) IoCs to be exposed; 6) authentication details of the xApp608; and/or 7) an associated managed entity in the managed domain (e.g., CS, NSI, NSSI, and so forth) that the xApp608is interested in.

The API management services606authenticates the xApp608and authorizes that the xApp608can request registration to the xApp registry service producer604for the O-RAN MD (e.g., near-RT RIC platform, non-RT RIC platform, an external management system).

In a second communication612transmitted from the API management services606to the xApp registry service producer604, the API management services606transmits the registration request to the xApp registry service producer604(“xARSP”). As may be appreciated, the registration request may be sent to the xApp registry service producer604via direct communication or via an operator management service exposure gateway. The registration request may include: 1) an application identifier (e.g., a way to identify the xApp608); 2) a call back interface to the xApp608; 3) an indication of the level of exposure or the management services that need to be exposed; 4) credentials of the xApp608(e.g., authentication and/or authorization details); and/or 5) an associated managed entity in the managed domain (e.g., CS, NSI, NSSI, and so forth) that the xApp608is interested in.

In a third communication614transmitted from the xApp registry service producer604to the approving authority602, the xApp registry service producer604sends a request for application registration approval to the approving authority602(e.g., to determine whether the xApp608can access the requested exposure of management service, function, data, or MOI). The request may include an application ID, an exposure request type, and/or an exposure request ID.

In a fourth communication616transmitted from the approving authority602to the xApp registry service producer604, the approving authority602may send an approval to the xApp registry service producer604specifying the approved details (e.g., if the xApp608is approved). The approval may include an application ID, an exposure request type, and/or an exposure request ID.

In a fifth communication618transmitted from the xApp registry service producer604to the API management services606, the xApp registry service producer604configures the API management services606for the approved exposure for the xApp608. Configuration information for configuring the API management services606may include an application ID, an exposure request type, and/or an exposure request ID.

In a sixth communication620transmitted from the API management services606to the xApp registry service producer604, the API management services606transmits an acknowledgement of successful configuration to the xApp registry service producer604.

In a seventh communication622transmitted from the xApp registry service producer604to the API management services606, the xApp registry service producer604transmits an acknowledgment of successful registration of the xApp608with the management domain to the API management services606. The eighth communication626may include access details for accessing the approved management functions, management services, management data, or MOIs.

In an eighth communication624transmitted from the API management services606to the xApp608, the API management services606forwards successful registration information and appropriate access details to the xApp608.

As may be appreciated,FIG.6may assume that a gateway to access an xApp registry service is a part of the API management services606. Furthermore, an xApp registry service may be collocated with the API management services606.

FIG.7is a flow chart diagram illustrating one embodiment of a method700for entity access for an application. In some embodiments, the method700is performed by an apparatus, such as the network unit104. In certain embodiments, the method700may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

In various embodiments, the method700includes receiving702, by a first entity, an application registry request for at least one application. In some embodiments, the method700includes determining704whether the at least one application is enabled to access at least one management entity or at least one managed entity.

In certain embodiments, the method700further comprises, in response to determining that the at least one application is enabled to access the at least one management entity or the at least one managed entity, configuring a gateway entity to enable the at least one application to access the at least one management entity or the at least one managed entity. In some embodiments, the application registry request comprises: a network operator; a level of exposure; management services to be exposed; management data to be exposed; information object classes to be exposed; management object instances to be exposed; authentication details associated with an application; an associated managed entity; or some combination thereof.

In various embodiments, the method700further comprises: transmitting first information corresponding to the application registry request to an approval device; and receiving second information from the approval device indicating whether the application registry request is approved. In some embodiments, the second information comprises a list of management entities approved, a list of managed entities approved, or a combination thereof. In one embodiment, third information is transmitted to at least one second entity, and the third information indicates whether the application registry request is approved, at least one approved management entity, at least one approved managed entity, information for accessing the at least one approved management entity, information for accessing the at least one approved managed entity, a description corresponding to the at least one approved management entity, a description corresponding to the at least one approved managed entity, or some combination thereof.

In certain embodiments, the at least one second entity comprises any one of a trusted application, a gateway, an application programming interface registry, or the at least one application. In some embodiments, the at least one application is configured to run on a near real-time random-access network intelligent controller. In various embodiments, the first entity comprises a telecom management system, a management domain, a middleware, a trusted application, an application programming interface, a management service implementation, a management function, a management entity, an entity for approving authorizations, or some combination thereof.

In one embodiment, a method comprises: receiving, by a first entity, an application registry request for at least one application; and determining whether the at least one application is enabled to access at least one management entity or at least one managed entity.

In certain embodiments, the method further comprises, in response to determining that the at least one application is enabled to access the at least one management entity or the at least one managed entity, configuring a gateway entity to enable the at least one application to access the at least one management entity or the at least one managed entity.

In some embodiments, the application registry request comprises: a network operator; a level of exposure; management services to be exposed; management data to be exposed; information object classes to be exposed; management object instances to be exposed; authentication details associated with an application; an associated managed entity; or some combination thereof.

In various embodiments, the method further comprises: transmitting first information corresponding to the application registry request to an approval device; and receiving second information from the approval device indicating whether the application registry request is approved.

In some embodiments, the second information comprises a list of management entities approved, a list of managed entities approved, or a combination thereof.

In one embodiment, third information is transmitted to at least one second entity, and the third information indicates whether the application registry request is approved, at least one approved management entity, at least one approved managed entity, information for accessing the at least one approved management entity, information for accessing the at least one approved managed entity, a description corresponding to the at least one approved management entity, a description corresponding to the at least one approved managed entity, or some combination thereof.

In certain embodiments, the at least one second entity comprises any one of a trusted application, a gateway, an application programming interface registry, or the at least one application.

In some embodiments, the at least one application is configured to run on a near real-time random-access network intelligent controller.

In various embodiments, the first entity comprises a telecom management system, a management domain, a middleware, a trusted application, an application programming interface, a management service implementation, a management function, a management entity, an entity for approving authorizations, or some combination thereof.

In one embodiment, an apparatus is in a telecom management system. The apparatus comprises: a receiver that receives an application registry request for at least one application; and a processor that determines at least one management entity or at least one managed entity of the telecom management system based on the application registry request, wherein the at least one application is enabled to access the at least one management entity or the at least one managed entity.

In certain embodiments, the processor configures a gateway entity to enable the application to access the at least one management entity or the at least one managed entity.

In some embodiments, the application registry request comprises: a network operator; a level of exposure; management services to be exposed; management data to be exposed; information object classes to be exposed; management object instances to be exposed; authentication details associated with an application; an associated managed entity; or some combination thereof.

In various embodiments, the apparatus further comprises a transmitter, wherein: the transmitter transmits first information corresponding to the application registry request to an approval device; and the receiver receives second information from the approval device indicating whether the application registry request is approved.

In some embodiments, the second information comprises a list of management entities approved, a list of managed entities approved, or a combination thereof.

In one embodiment, third information is transmitted to at least one second entity, and the third information indicates whether the application registry request is approved, at least one approved management entity, at least one approved managed entity, information for accessing the at least one approved management entity, information for accessing the at least one approved managed entity, a description corresponding to the at least one approved management entity, a description corresponding to the at least one approved managed entity, or some combination thereof.

In certain embodiments, the receiver receiving the application registry request comprises the receiver receiving the application registry request from the at least one application or middleware

In some embodiments, the at least one application is configured to run on a near real-time random-access network intelligent controller.

In various embodiments, the apparatus (or system) comprises at least one computer executable program stored on a plurality of memory devices, and the plurality of memory devices are physically in different locations (e.g., located remote from one another, in different geographic locations).

In one embodiment, the apparatus is a telecom management system, a management domain, a middleware, a trusted application, an application programming interface, a management service implementation, a management function, a management entity, an entity for approving authorizations, or some combination thereof.