Access priority for private LTE radio services

Abstract

A system and method for providing access priority to a private Long Term Evolution (LTE) network operating in the Citizens Broadband Radio Service (CBRS) spectrum includes: receiving, at a network device of the private Long Term Evolution (LTE) network, a functional group associated with a user equipment (UE) and a traffic load of a cell of the private LTE network associated with the UE. An access priority associated with the functional group and the traffic load is determined and provided to a CBRS access point (AP) that controls access to the cell. The access priority indicates to the CBRS AP the priority with which the UE is allowed access to the cell and the access priority may include high priority, low priority, or no access indication.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of and priority to U.S. non-provisional patent application No. 16 / 672,123, filed on November 1, 2019, entitled “ACCESS PRIORITIZATION FOR PRIVATE LTE RADIO SERVICE,” the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] The present technology relates to enterprise networks, and more particularly to access priority for private Long Term Evolution (LTE) services in the Citizens Broadband Radio Service (CBRS) spectrum based on enterprise group affiliation. Background Art

[0004] In the United States, the Citizens Broadband Radio Service (CBRS) is a 150MHz-wide spectrum in the 3550-3700MHz frequency range. The US government uses a portion of this spectrum for its radar systems. When portions of this spectrum are unused, they can be made available for use by other entities. The Federal Communications Commission (FCC) has established rules for commercial use of the CBRS spectrum. Businesses can use this CBRS spectrum to build private Long Term Evolution (LTE) networks and allow access for consumers and Internet of Things (IoT) devices. Businesses can expand and increase the coverage density of their private LTE networks by integrating CBRS into their wireless connectivity services. Plans are also underway in Europe and other parts of the world to use CBRS-type shared spectrum in other frequency bands.

[0005] The use of CBRS spectrum is governed by a three-tier spectrum authorization framework (Existing Access, Priority Access, General Authorized Access) to accommodate a variety of commercial uses on a shared basis with existing federal and non-federal users of the band. Existing Access users include authorized federal and privileged fixed satellite service users. Priority Access includes priority access licenses allocated for competitive bidding within the band. Finally, General Authorized Access is licensed by rules to allow the widest possible group of potential users open and flexible access to any portion of the band not allocated to either of the two higher tiers. Access to and operation of the bands on the three different tiers is managed by a dynamic Spectrum Access System (SAS). BRIEF DESCRIPTION OF THE DRAWINGS

[0006] In order to illustrate the manner in which the above and other advantages and features of the present disclosure can be obtained, a more particular description of the principles briefly described above will be presented by reference to specific embodiments thereof as illustrated in the accompanying drawings. Understanding that these drawings depict only exemplary embodiments of the present disclosure and are therefore not to be considered limiting of its scope, the principles herein will be described and explained with additional uniqueness and detail through the use of the accompanying drawings, in which:

[0007] Figure 1 An example CBRS network architecture according to aspects of the present disclosure is shown;

[0008] Figure 2 is a network environment for deploying a CBRS network according to example aspects of the present disclosure;

[0009] Figure 3 and Figure 4 An example flow for providing access priority based on functional groups in a CBRS network according to example aspects of the present disclosure is shown;

[0010] Figure 5 Another process for providing access priority based on functional groups in a CBRS network according to aspects of the present disclosure is shown;

[0011] Figure 6 shows an example network device according to various examples; and

[0012] Figure 7 An example computing device according to various examples is shown. DETAILED DESCRIPTION

[0013] Various embodiments of the present disclosure are discussed in detail below. Although specific embodiments are discussed, it should be understood that this is done for illustrative purposes only. Those skilled in the relevant art will recognize that other components and configurations may be used without departing from the spirit and scope of the present disclosure. Therefore, the following description and drawings are illustrative and should not be construed as limiting. Many specific details are described to provide a thorough understanding of the present disclosure. However, in some cases, in order to avoid obscuring the description, well-known or conventional details are not described. References to an embodiment or an embodiment in the present disclosure may be references to the same embodiment or any embodiment; and, such references represent at least one of the embodiments.

[0014] Reference to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. The appearances of the phrase "in one embodiment" in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Furthermore, various features are described that may be exhibited by some embodiments but not others.

[0015] The terms used in this specification generally have their ordinary meaning in the art within the context of this disclosure and in the specific context in which each term is used. Alternative language and synonyms may be used for any one or more of the terms discussed herein, and no special meaning should be given to whether a term is elaborated or discussed herein. In some cases, synonyms for certain terms are provided. The statement of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification, including examples of any term discussed herein, is illustrative only and is not intended to further limit the scope and meaning of the disclosure or any example term. Likewise, the disclosure is not limited to the various embodiments given in this specification.

[0016] Without intending to limit the scope of the present disclosure, examples of instruments, devices, methods and related results thereof according to embodiments of the present disclosure are given below. Note that, for the convenience of the reader, titles or subtitles may be used in the examples, which should in no way limit the scope of the present disclosure. Unless otherwise defined, the technical and scientific terms used herein have the meanings commonly understood by those of ordinary skill in the art as disclosed herein. In the event of a conflict, this document (including definitions) shall prevail.

[0017] Additional features and advantages of the present disclosure will be set forth in the following description and, in part, will be apparent from the description or may be learned by practice of the principles disclosed herein. The features and advantages of the present disclosure may be realized and obtained by the instruments and combinations particularly pointed out in the appended claims. These and other features of the present disclosure will become more fully apparent from the following description and the appended claims or may be learned by practice of the principles set forth herein.

[0018] Overview

[0019] Various aspects of the invention are set out in the independent claims and preferred features are set out in the dependent claims. Features of one aspect may apply to each aspect alone or in combination with the other aspects.

[0020] Disclosed herein are systems, methods, and computer-readable media for providing access priority to one or more devices for connecting to a private LTE network in the CBRS spectrum based on a functional group associated with the one or more devices. In some examples, an employee or enterprise functional group is associated with a cell identifier (cell ID) of a user equipment (UE). Based on the functional group of a cell associated with the UE, the UE can be allowed or prevented from locking onto the cell. Additionally, based on the functional group, the UE can be provided with preferred access to the cell.

[0021] In one example embodiment, an enterprise's authentication, authorization, and accounting (AAA) server is configured with a functional group of the UE. Based on the functional group and cell ID of the UE, a digital network architecture (DNA) device is configured with access control and traffic priority. Cell-specific load information may also be provided to the DNA device for use in determining traffic priority for a given group of UEs. After the UE locks onto a CBRS cell and attempts to connect to a private LTE network, the private LTE network may request the DNA device to provide access control and traffic priority related information for the UE. The private LTE network may provide the DNA device with relevant functional group and cell information of the UE. Based on the information configured for group access and priority and other load information on the cell, the DNA device may determine the access control and traffic priority information for the UE, which may be provided to the access point (e.g., eNodeB) to enable appropriate access and priority treatment for the UE.

[0022] In some examples, a method is provided. The method includes receiving, at a network device of a private Long Term Evolution (LTE) network operating in a Citizens Broadband Radio Service (CBRS) spectrum, a functional group associated with a user equipment (UE); receiving, at the network device, a traffic load of a cell of the private LTE network associated with the UE; determining an access priority associated with the functional group and the traffic load; and providing the access priority to a CBRS access point (AP) that controls access to the cell, wherein the access priority indicates to the CBRS AP a priority with which the UE is allowed to access the cell.

[0023] In some examples, a system is provided that includes: one or more processors; and a non-transitory computer-readable storage medium including instructions that, when executed on the one or more processors, cause the one or more processors to perform operations including: receiving, at a network device of a private Long Term Evolution (LTE) network operating in a Citizens Broadband Radio Service (CBRS) spectrum, a functional group associated with a user equipment (UE); receiving, at the network device, a traffic load of a cell of the private LTE network associated with the UE; determining an access priority associated with the functional group and the traffic load; and providing the access priority to a CBRS access point (AP) that controls access to the cell, wherein the access priority indicates to the CBRS AP the priority with which the UE is allowed to access the cell.

[0024] In some examples, a non-transitory machine-readable storage medium is provided, comprising instructions configured to cause a data processing device to perform operations, the operations comprising: receiving, at a network device of a private Long Term Evolution (LTE) network operating in a Citizens Broadband Radio Service (CBRS) spectrum, a functional group associated with a user equipment (UE); receiving, at the network device, a traffic load of a cell of the private LTE network associated with the UE; determining an access priority associated with the functional group and the traffic load; and providing the access priority to a CBRS access point (AP) that controls access to the cell, wherein the access priority indicates to the CBRS AP the priority with which the UE is allowed to access the cell.

[0025] In some examples, the access priority includes high priority, low priority, or no access indication.

[0026] In some examples, if the UE is authenticated as attached to a cell and one or more UEs of a higher priority functional group consume traffic load of the cell, the access priority of the UE includes a no access indication.

[0027] In some examples, the no access indication is temporary for a period of time until the traffic load of the cell decreases.

[0028] In some examples, providing access priority to the CBRS AP includes providing access priority to a mobility management entity (MME) of the private LTE network, wherein the functional group is received from the MME based on the UE's request to establish an attachment to the cell.

[0029] In some examples, the network device is a Digital Network Architecture (DNA) device of a private LTE network.

[0030] Some examples also include receiving a user profile and subscription information associated with the UE from one or more authentication, authorization, and accounting (AAA) servers of the private LTE network. In some examples, the one or more AAA servers include a CBRS AAA server and an enterprise AAA server.

[0031] Description of Exemplary Embodiments

[0032] The disclosed technology addresses the need in the art for priority access to private LTE radio services. In certain operating environments using the CBRS spectrum, such access priority is considered a desired feature. For example, in an enterprise network, the enterprise group affiliation of a user (or UE) can form the basis for determining both access to a network cell and access priority relative to other groups of users. For example, given that an automobile manufacturer has many different functional areas and a mix of users and Internet of Things (IoT) devices (e.g., robots) that move between CBRS cells, it may be desirable to ensure that certain user groups have higher priority over other groups in certain locations. For example, a robot equipped with CBRS access may be considered to have a higher priority than a user accessing the network for streaming media content. Such priority can provide an enterprise network with the ability to ensure that network access is fully utilized while also guaranteeing connectivity to certain high-priority users.

[0033] In some examples, users belonging to a particular group (e.g., a Digital Network Architecture Center (DNA-C) group) may be considered to have higher priority for CBRS network access at a location than users belonging to other groups. In existing CBRS spectrum usage rules, a unique CBRS-Network Identifier (CBRS-NID) is provided for each enterprise deploying a CBRS private LTE network. In addition, all CBRS networks have a common Shared Home Network Identifier (SHNI), where, in some cases, the SHNI value is "315-010." The above two identifiers, CBRS-NID and SHNI, uniquely identify a CBRS enterprise network. According to currently defined access regulations, all UEs belonging to an enterprise and having a profile that matches the enterprise's CBRS-NID and SHNI (and in some cases, other valid authentication credentials) can be allowed to access the enterprise network. According to example aspects, improvements to currently defined access regulations are provided, wherein these improvements can both allow / disallow access and (when allowed) prioritize access to certain UE groups (e.g., based on their functional group IDs mentioned above).

[0034] Figure 1An example deployment of a CBRS network 100 is illustrated. In the CBRS network 100, the CBRS spectrum can be used along with 4G LTE technology to support a private LTE network. Similar to an LTE network, the CBRS network 100 can include: eNodeBs, a core network for packet services, and an IMS for voice and multimedia services. In addition to the traditional LTE network, the CBRS network 100 can include an additional node (shown as a spectrum access system (SAS) 110) that is used to manage and control access to the CBRS network 100. The SAS 110 can be implemented using a three-tier spectrum authorization framework to accommodate various commercial uses based on sharing with existing federal and non-federal CBRS band users.

[0035] The CBRS network 100 can be accessed by one or more UEs 102, which are identified as CBRS UEs. UEs 102 can include various computing and networking devices (e.g., mobile devices, laptops, desktops, etc.). One or more access points, such as CBRS APs 104A-D, can control and provide network access to UEs 102. In some examples, CBRS APs 104A-D can include evolved Node Bs (eNodeBs), CBRS base stations, or CBRS devices (CBSDs). CBRS APs 104A-D can belong to different networks or enterprises (e.g., private LTE networks) and can communicate directly with UEs 102 of that network. CBRS APs 104A-D, CBSDs, or eNodeBs configured to support the CBRS band can be categorized into two types: CBSD-Type A and CBSD-Type B.

[0036] SAS 110 can manage a three-tiered license structure for the following types of access. The first access license (called Incumbent Access (IA)) is the access license used by the US Navy and is also used for Fixed Satellite Service (FSS). IA access has absolute priority over other types of allocations.

[0037] The second access license, referred to as the Priority Access License (PAL), is an access license that can be used by hospitals, utilities and government agencies, as well as non-critical users such as mobile network operators (MNOs). PALs are allocated to various enterprise and commercial users within the 3550-3650 MHz frequency block of the CBRS spectrum through the use of competitive bidding. Each access license under the PAL is limited to a non-renewable authorization to use a 10 MHz channel in a single census tract (e.g., in a closed location or small geographic area / region) for a fixed term (e.g., three years). Up to seven PALs may be allocated to any given census tract, including up to four PALs granted to any single applicant. During the first competitive bidding period, applicants may obtain up to two consecutive PAL terms within any given license area.

[0038] A third access license, known as General Authorized Access (GAA), is provided to user(s), which can potentially access all 150 MHz of the 3550-3700 MHz spectrum. GAA users are allowed to use any portion of the 3550-3700 MHz band not allocated to higher-tier users, and can also operate opportunistically on unused Priority Access channels.

[0039] The SAS 110 can control the operation of the CBRS APs 104A-D based on a three-tiered permission model. In some examples, the SAS 110 can inform the CBRS APs 104A-D of the frequency bands or channels to be used in the CBRS spectrum and the transmit / receive power for any particular time or period. The interface between the SAS 110 and the CBRS APs 104A-D can be based on the HTTP over Transport Layer Security (HTTP-TSL) protocol. The interface can include message exchanges for the following operations: CBSD registration request / response, spectrum query request / response, authorization request / response, and heartbeat request / response.

[0040] When the CBRS APs 104A-D are powered on, they initiate a SAS-CBSD registration procedure with the SAS 110 to gain access to the CBRS spectrum. For example, the CBRS APs 104A-D send their respective registration requests (along with other parameters required by the SAS 110). Following a registration response from the SAS 110 (indicating a successful registration), the CBRS APs 104A-D perform a spectrum query for available channel information from the CBRS spectrum. Upon receiving a spectrum query response to the spectrum query, the CBRS APs 104A-D send an authorization request with one of the operating channels and peak power indicated in the spectrum query response. The spectrum query is an optional procedure. If the spectrum query fails, the CBRS APs 104A-D may proceed with the authorization procedure. In response to the authorization request, the CBRS APs 104A-D obtain approval for the requested frequency channel and peak transmit power. The CBRS APs 104A-D may also receive an authorized time period. Once CBRS APs 104A-D reach an authorized state, they initiate a heartbeat procedure and receive authorization from SAS 110 to conduct RF transmissions.

[0041] The CBRS APs 104A-D may provide corresponding access rules and policies to the UE 102 for accessing the CBRS network 100 (or a portion of the CBRS network 100) through the corresponding CBRS AP 104A-D, wherein the rules and policies may include frequency channels that have been assigned to the CBRS APs 104A-D and, according to example aspects, may include access permissions and priorities.

[0042] An evolved packet core (EPC) 106 may also be deployed within the CBRS network 100. The EPC 106 may provide various functions for the CBRS network 100. For example, the EPC 106 may manage session state, authentication, and communications associated with access points and / or user devices within the CBRS network 100. The EPC 106 may also be used to route communications (e.g., data packets), manage quality of service (QoS), and provide deep packet inspection (DPI) functionality within the CBRS network.

[0043] In addition, the CBRS network 100 may include a digital network architecture (DNA) device 108 that can be configured to manage the CBRS APs 104A-D. For example, the DNA device 108 can obtain the work assignment for each CBRS AP 104A-D provided by the SAS 110. In some examples, the DNA device 108 can monitor the performance of the CBRS APs 104A-D and the associated UEs 102 to detect when interference exists. In some examples, when interference is detected, the DNA device 108 can determine different parameters to assign to one or more CBRS APs 104A-D and dynamically reallocate the operating parameters of the access points to minimize and / or eliminate the detected interference. In this way, the DNA device 108 can resolve interference issues between the CBRS APs 104A-D and / or the UEs 202 that the SAS 110 may not be able to resolve.

[0044] Figure 2 An environment 200 is illustrated in which a CBRS network 100 may be deployed according to example aspects of the present disclosure. In one example, the environment 200 may include a manufacturing facility having various zones. To illustrate some example features, the zones are shown as non-overlapping geographic locations, but the disclosed aspects are equally applicable to zones including overlapping geographic locations. An enterprise private LTE network 220 that may be deployed in the environment 200 using CBRS spectrum may include a SAS, which may be composed of various components.

[0045] The private LTE network 220 can provide access to the CBRS spectrum for one or more cells or sectors (e.g., to connect to the Internet 222), where each cell or sector can include a corresponding CBRS spectrum (e.g., Cell 1 and Cell 2, respectively, shown as eNodeBs 204A-B (collectively, eNodeBs 204)). The eNodeBs 204 can provide access to the UEs 202 in the corresponding Cells 1 and 2.

[0046] In some examples, the private LTE network 220 may include a mobility management entity (MME) 206, which may be a key control node for the private LTE network 220. The MME 206 may communicate with the eNodeB 204 in conjunction with the Evolved Packet Core (EPC) or a Serving Gateway (S-GW) 214 within the private LTE network 220. The MME 206 may select from one or more S-GWs for the UE 202 during initial attach and during intra-LTE handovers involving core network (CN) node relocation. The MME 206 may also select a Packet Data Network (PDN) Gateway (P-GW) (e.g., P-GW 216) to connect to the PDN. In various examples, the MME 206 may serve as a termination point for non-access stratum (NAS) signaling and may also be configured to generate temporary identities and assign these temporary identities to the UE 202.

[0047] In some examples, the MME 206 can authenticate the UE 202 according to aspects of the present disclosure by interacting with one or more authentication, authorization, and accounting (AAA) modules (e.g., the enterprise AAA 210a and the CBRS AAA 212). In some examples, the UEs 202 can each be associated with a corresponding functional group, and the enterprise AAA 210 and / or the CBRS AAA 212 can be configured to store the functional group of the UE 202. The functional group of the UE 202 can be bound to a cell ID (e.g., Figure 2 Based on the functional group to which UE 202 is bound, UE 202 may be allowed to lock onto or access the corresponding cell 1 or cell 2. In addition, depending on the functional group bound to the cell for a particular UE 202, UE 202 may be given preferential traffic treatment when accessing the cell.

[0048] The MME 206 may also communicate with the DNA device 208, which may be similarly configured to provide functionality related to the DNA device 108. In some examples, the DNA device 208 may assist the MME 206 in detecting and resolving interference issues between the eNodeB 204 and / or the UE 202. In some examples, the DNA device 208 may be configured with access control and traffic prioritization based on the functional group and cell ID (e.g., cell 1 or cell 2) of the UE 202. In some examples, cell-specific load information may also be provided to the DNA device 208 (e.g., by the MME 206) for use in making decisions regarding traffic prioritization for a given UE 202 functional group.

[0049] like Figure 2As shown, different access priority categories are identified, including high priority 230A, low priority 230B, or no access 232. UEs 202 with a high priority 230A functional group are given priority access over UEs 202 with a low priority 230B functional group. In some examples, the access priority of a UE 202 associated with a functional group may be determined to be no access 232 in the following circumstances: when one or more UEs of a functional group with a higher priority consume the available resources of the cell. The available resources of a cell (e.g., available bandwidth) may be based on the existing traffic load or bandwidth consumption of the cell. Therefore, access to a cell is generally based on the available resources of the cell (e.g., based on the traffic load of the cell). In some cases, if the traffic load of the cell decreases after a period of time, no access 232 may be temporary and can be withdrawn.

[0050] When UE 202 locks (or attaches) to one of the cells (cell 1 or cell 2) and attempts to connect to private LTE network 220, MME 206 can request DNA device 208 to provide access control and traffic priority related information. In various examples, DNA device 208 can obtain functional group and cell information from private LTE network 220 (e.g., illustratively shown as DNA configuration information 208A, where related configurations 210A and 212A are also shown for enterprise AAA 210 and CBRS AAA 212, respectively). DNA device 208 can also obtain traffic load information in the cell. Based on the functional group and traffic load, DNA device 208 can determine the access priority of UEs belonging to the functional group and provide access control and priority information for the functional group to MME 206.

[0051] In some examples, the MME 206 can communicate the priority information to the eNodeB 204 so that the eNodeB can provide appropriate treatment to the UE 202. For example, for a UE 202 whose functional group falls within the no access 232 category of cell 1, access can be denied by the eNodeB 204A. For a group of UEs 202 with high priority 230A in cell 1 and cell 2, high priority access can be provided by the corresponding eNodeB 204A and eNodeB 204B. Similarly, for a group of UEs with low priority 230B in cell 1, low priority access can be provided by the eNodeB 204A (i.e., based on prioritizing UEs 202 in the high priority 230A group relative to UEs 202 in the low priority 230B group). Prioritizing a group of UEs 202 can include providing preferential treatment to / from the UEs 202 (e.g., in the high priority 230A group). In some examples, additional priority levels (e.g., one or more intermediate priority categories between high priority 230A and low priority 230B) may also be included and prioritized in a corresponding order. In some examples, the IEC sgMemberShip Info field used in data packet communications between various nodes (e.g., from DNA device 208 to MME 206 to eNodeB 204) includes priority tags "high," "medium," "low," and "none" to indicate different priority levels and access permissions for UE 202. In some examples, a reason code may be included for communicating with a UE 202 that may be in a closed subscriber group (CSG) with a valid authorization, but is temporarily denied connectivity due to, for example, available bandwidth being provided to a higher priority group of UEs 202.

[0052] Figure 3-4 Example processes 300 and 400 for implementing the above-described functional group based on access priority of a private LTE network are shown. In some examples, processes 300 and 400 can be implemented in CBRS network 100 or environment 200. It will be understood that the steps described with reference to processes 300 and 400 can be implemented in any order or any combination thereof (including combinations that exclude, add, or modify certain steps).

[0053] Beginning with step 1 of process 300, one or more UEs 202 in cell 1 or cell 2 may provide configuration information to the corresponding eNodeB 204. In step 2, the eNodeB 204 may register and provide the configuration (e.g., CSG cell ID) to the MME 206. In step 3, the CBRS AAA 212 may obtain or generate UE authorization and subscription information (e.g., based on configuration 212A for all UEs 202), which may then be provided to the MME 206. In step 4, the enterprise AAA 210 may be configured with UE subscription profiles and authentication-related information, including group ID mappings (e.g., based on configuration 210A for all UEs 202), which may then be provided to the MME 206. In step 5, the DNA device 208 may be configured with network access priorities. For example, the DNA device 208 may be configured with information and priorities related to UE groups (e.g., based on configuration 208A for UEs 202), which may then be provided to the MME 206.

[0054] In step 6, the eNodeB 204 connects to the MME 206 (e.g., using an S1 setup procedure) and informs the MME 206 of supported Shared Home Network Identifiers (SHNIs), Closed Subscriber Group (CSG) lists, etc. In step 7, the eNodeB may broadcast information (e.g., in the form of a Master Information Block (MIB), a System Information Block (SIB), etc.) for evaluating whether the UE 202 can access the cell.

[0055] UE 102 may be associated with a public land mobile network (PLMN). A PLMN may be uniquely identified by a PLMN identifier (PLMN ID). The PLMN ID may include a mobile country code (MCC) and a mobile network code (MNC). The UE may be configured with a private enterprise PLMN ID and different authentication modes. In some examples, the UE may perform PLMN selection and may attach to one of the (multiple) CBSDs or one of the (multiple) eNodeBs 204 of the private LTE network 220 using the CBRS band. For example, in step 8, the eNodeB 204 may broadcast information received by the UE 202, wherein the information may include the PLMN from the broadcast in step 7. In step 9, the UE 202 may select a cell by comparing the PLMN ID and the CSG, and select a cell that supports SHNI.

[0056] For a UE 202 that may wish to attach to a specific eNodeB 204, steps 10-12 illustrate an attach procedure. The attach procedure may include a random access procedure in step 10, radio resource control (RRC) in step 11, and RRC setup completion in step 12, after which the UE 202 may have established its intention to attach to the eNodeB 204. In step 13, the attach request for the UE 202 may be forwarded from the eNodeB 204 to the MME 206. In step 14, the MME 206 may download a subscription profile for the UE 202 from the CBRS AAA 212.

[0057] In step 15, the MME 206 and / or CBRS AAA may perform initial authentication and security procedures. For example, in this step 15, a determination may be made as to whether the UE 202 is allowed to attach (remember, this is different from the No Access 232 priority, which is a determination that is subsequently made for a UE 202 that may be allowed to attach but may be denied access due to other high-priority accesses that may be exhausting the available bandwidth). If the UE 202 is allowed to attach, then in step 16, the MME 206 may establish a channel through which it may communicate with the UE 202.

[0058] In step 17, the MME may download or collect the configuration and priority information generated or obtained in steps 3-5 for the UE 202. For example, the information obtained in steps 3-5 from the CBRS AAA 212, the enterprise AAA 210, and the DNA device 208 may be referred to as a user profile, which may include the functional group ID of the UE 202. The MME 206 may determine the functional group of the UE 202 based on the user profile of the UE 202 in this step.

[0059] Reference Figure 4 , Figure 3 The process 300 in the embodiment may continue to Figure 4 The process 400 in step 18 starts at step 18, where the MME 206 may provide the functional group determined for the UE 202 in step 17 to the DNA device 208. The DNA device 208 may, for example, refer to its mapping table or configuration 208A (or reference Figure 3 5) to obtain the priority of UE 202 (e.g., high priority 230A or low priority 230B) and provide the priority to MME 206. In step 20, MME 206 may also establish a PDN connection with one of the following gateways: S-GW 214 or P-GW 216. Based on this, MME 206 may provide the initial context and settings and the priority of UE 202 to eNodeB 204 in step 21.

[0060] In step 22, eNodeB 204 may send an RRC connection reconfiguration to UE 202 (or accept the attach request in step 12), having identified the high priority of UE 202 in this example. In step 23, a PDN connection is established for high-priority access of UE 202. For low-priority access, steps 24-29 are similar to steps 18-23 discussed above. In some cases, steps 24-29 may be performed as an alternative to steps 18-23.

[0061] Steps 30-33 correspond to the case where UE 202 is denied access based on its associated functional group, again remembering that this is a case where UE 202 is allowed to attach but may be denied access (e.g., temporarily due to traffic load). In some cases, steps 30-33 may be performed as an alternative to steps 18-29. In step 30, MME 206 may provide the functional group determined for UE 202 in step 17 to DNA device 208. DNA device 208 may, for example, consult its configuration 208A (or reference Figure 3 5) to obtain the priority of UE 202 (e.g., high priority 230A or low priority 230B) and provide the priority to MME 206. In step 31, no priority associated with the functional group is found, or the priority may indicate no access. Based on this, DNA device 208 may notify MME 206 in step 32 that UE 202 will be rejected in step 33, and this notification may be transmitted to the UE in step 33.

[0062] Having described example systems and concepts, the disclosure now turns to Figure 5 The process 500 is shown. The steps or blocks outlined herein are examples, and the steps or blocks may be implemented in any combination thereof (including combinations that exclude, add, or modify certain steps).

[0063] At block 502, flow 500 may include receiving, at a network device of a private Long Term Evolution (LTE) network operating in a Citizens Broadband Radio Service (CBRS) spectrum, a functional group associated with a user equipment (UE). For example, DNA device 208 of private LTE network 220 may receive (e.g., in steps 18, 24, 30) a request from MME 206 that includes a functional group associated with UE 202 attached to a cell.

[0064] At block 504 , process 500 may include receiving, at a network device, traffic loads of cells of a private LTE network associated with the UE. For example, traffic loads of cell 1 and cell 2 in environment 200 may be obtained from eNodeB 204 .

[0065] At block 506, process 500 may include determining an access priority associated with the functional group and the traffic load. For example, based on configuration 208A and the traffic load, the DNA device may obtain a priority for UE 202 (e.g., as shown in steps 19, 25, and 31).

[0066] At block 508, process 500 may include providing an access priority to a CBRS access point (AP) that controls access to the cell, wherein the access priority indicates to the CBRS AP the priority with which the UE is allowed to access the cell. For example, as shown in steps 20, 26, and 32, the access priority may be provided to the eNodeB 204 by the MME 206. The access priority may include a high priority, a low priority, or a no access indication, wherein the access priority of the UE includes a no access indication if the UE is authenticated as attached to the cell and one or more UEs of a functional group with a higher priority consume the traffic load of the cell. In some examples, the no access indication is temporary for a period of time until the traffic load of the cell decreases.

[0067] In some examples, the DNA device may receive user profile and subscription information associated with the UE from one or more authentication, authorization, and accounting (AAA) servers of the private LTE network (e.g., the CBRS AAA 212 server and the enterprise AAA server 210).

[0068] Figure 6 An example network device 600 suitable for implementing policy agents and performing switching, routing, and other networking operations is shown. The network device 600 includes a central processing unit (CPU) 604, an interface 602, and a connection structure 610 (e.g., a PCI bus). When operating under the control of appropriate software or firmware, the CPU 604 is responsible for performing packet management, error detection, and / or routing functions. The CPU 604 preferably implements all of these functions under the control of the following software: the software includes an operating system and any appropriate application software. The CPU 604 may include one or more processors 608 (e.g., a processor from the INTEL X86 series of microprocessors). In some cases, the processor 608 may be specially designed hardware for controlling the operation of the network device 600. In some cases, a memory 606 (e.g., non-volatile RAM, ROM, etc.) also forms part of the CPU 604. However, there are many different ways in which memory can be coupled to the system.

[0069] Interfaces 602 are typically provided as modular interface cards (sometimes referred to as "line cards"). Typically, interfaces control the transmission and reception of data packets across the network and, in some cases, support other peripheral devices used with network device 600. Interfaces that may be provided include Ethernet, Frame Relay, Cable, DSL, Token Ring, and the like. Additionally, various ultra-high-speed interfaces may be provided, such as Fast Token Ring, wireless, Ethernet, Gigabit Ethernet, ATM, HSSI, POS, FDDI, WiFi, 3G / 4G / 5G cellular, CAN Bus, LoRA, and the like. Typically, these interfaces may include ports suitable for communicating with appropriate media. In some cases, the interfaces may also include independent processors and, in some cases, volatile RAM. Independent processors may control communication-intensive tasks, such as packet switching, media control, signal processing, cryptographic processing, and management. By providing a separate processor for communication-intensive tasks, these interfaces allow the main microprocessor 604 to efficiently perform routing calculations, network diagnostics, security functions, and the like.

[0070] Although Figure 6 The system shown in FIG600 is a specific network device of the present technology, but it is by no means the only network device architecture that can implement the present technology. For example, the following architecture is often used: the architecture has a single processor that handles communication and routing calculations. In addition, other types of interfaces and media can also be used with network device 600.

[0071] Regardless of the configuration of the network device, the network device may employ one or more of the following memories or memory modules (including memory 606): The memory or memory module is configured to store program instructions for general network operations and mechanisms for roaming, route optimization, and routing functions described herein. For example, the program instructions may control the operation of an operating system and / or one or more applications. The one or more memories may also be configured to store tables, such as mobility binding, registration, and association tables. The memory 606 may also store various software containers and virtualized execution environments and data.

[0072] Network device 600 may also include an application-specific integrated circuit (ASIC) that may be configured to perform routing and / or switching operations. The ASIC may communicate with other components in network device 600 via connection fabric 610 to exchange data and signals and coordinate various types of operations of network device 600, such as routing, switching, and / or data storage operations.

[0073] Figure 7The architecture of a computing system 700 is illustrated, in which the components of system 700 electrically communicate with each other using a connection 705 (e.g., a bus). Example system 700 includes a processing unit (CPU or processor) 710 and system connection 705, which couples various system components (e.g., read-only memory (ROM) 720 and random access memory (RAM) 725) including system memory 715 to processor 710. System 700 may include a cache of high-speed memory that is directly connected to, immediately adjacent to, or integrated as part of processor 710. System 700 may copy data from memory 715 and / or storage devices 730 to cache 712 for faster access by processor 710. In this way, the cache can provide a performance boost that prevents processor 710 from stalling while waiting for data. These and other modules may control or be configured to control processor 710 to perform various actions. Other system memories 715 may also be used. Memory 715 may include a variety of different types of memory with different performance characteristics. Processor 710 may include any general-purpose processor and hardware or software modules configured to control processor 710 (e.g., module 1 732, module 2 734, and module 3 736 stored in storage device 730), as well as proprietary processors in which software instructions are incorporated into the actual processor design. Processor 710 may be a fully self-contained computing system containing multiple cores or processors, a bus, a memory controller, a cache, etc. Multi-core processors may be symmetric or asymmetric.

[0074] To enable a user to interact with the computing system 700, the input device 745 can represent any number of input mechanisms (e.g., a microphone for voice, a touch-sensitive screen for gesture or graphic input, a keyboard, a mouse, motion input, and voice, etc.). The output device 735 can also be one or more of several output mechanisms known to those skilled in the art. In some cases, a multimodal system can enable a user to provide multiple types of input to communicate with the computing system 700. The communication interface 740 can generally govern and manage user input and system output. There is no limitation on the operation of any particular hardware arrangement, so the basic features here can be easily replaced with improved hardware or firmware arrangements as they are developed.

[0075] The storage device 730 is a non-volatile memory and may be a hard disk or other type of computer-readable medium that can store computer-accessible data (e.g., magnetic tape, flash memory cards, solid-state storage devices, digital versatile disks, cassettes, random access memory (RAM) 725, read-only memory (ROM) 720, and combinations thereof).

[0076] The storage device 730 may include modules 732, 734, 736 for controlling the processor 710. Other hardware or software modules are also contemplated. The storage device 730 may be connected to the system connection 705. In one aspect, a hardware module that performs a particular function may include a software component stored in a computer-readable medium and associated with the necessary hardware components (e.g., the processor 710, the connection 705, the output device 735, etc.) to perform that function.

[0077] For clarity of explanation, in some instances, the technology may be presented as including separate functional blocks comprising devices, device components, steps or routines in a method embodied in software, or a combination of hardware and software.

[0078] In some embodiments, computer-readable storage devices, media, and memories may include cables or wireless signals containing bit streams, etc. However, when referred to, non-transitory computer-readable storage media expressly excludes media such as energy, carrier signals, electromagnetic waves, and signals themselves.

[0079] In summary, a system and method for providing access priority to a private Long Term Evolution (LTE) network operating in the Citizens Broadband Radio Service (CBRS) spectrum includes: receiving, at a network device of the private Long Term Evolution (LTE) network, a functional group associated with a user equipment (UE) and a traffic load of a cell of the private LTE network associated with the UE. Determining an access priority associated with the functional group and the traffic load, and providing the access priority to a CBRS access point (AP) that controls access to the cell. The access priority indicates to the CBRS AP the priority with which the UE is allowed access to the cell, and the access priority may include a high priority, a low priority, or no access indication.

[0080] The method according to the above example can be implemented using computer-executable instructions, which are stored or otherwise obtained from a computer-readable medium. These instructions may include, for example, instructions and data, which cause or otherwise configure a general-purpose computer, a private computer, or a private processing device to perform a specific function or function group. The computer resources used in part can be accessed over a network. Computer-executable instructions can be, for example, binary, intermediate format instructions (for example, assembly language, firmware, or source code). Examples of computer-readable media that can be used for storing instructions, information used, and / or information created during the method according to the described example include disks or optical disks, flash memory, USB devices provided with non-volatile memory, network storage devices, etc.

[0081] Devices implementing the methods according to these disclosures may include hardware, firmware, and / or software and may take any of a variety of form factors. Some examples of such form factors include laptops, smartphones, small personal computers, personal digital assistants, rack-mounted devices, standalone devices, and the like. The functionality described herein may also be embodied in peripheral devices or add-in cards. As a further example, such functionality may also be implemented on different chips or circuit boards between different processes executed in a single device.

[0082] Instructions, the media for transmitting these instructions, computing resources for executing these instructions, and other structures for supporting these computing resources are the means for providing the functionality described in this disclosure.

[0083] Although various examples and other information are used to explain aspects within the scope of the appended claims, no limitation to the claims should be implied based on the specific features or arrangements in such examples, as one of ordinary skill would be able to use these examples to deduce various implementations. In addition, although some subject matter may have been described in language specific to structural features and / or examples of method steps, it should be understood that the subject matter defined in the appended claims is not necessarily limited to these described features or actions. For example, such functionality may be distributed differently or performed in components other than those identified herein. Instead, the described features and steps are disclosed as examples of components of systems and methods within the scope of the appended claims.

[0084] Claim language reciting "at least one of a set" indicates that one member of the set or multiple members of the set satisfy the claim. For example, claim language reciting "at least one of A and B" means "A," "B," or "A and B."

Claims

1. A method for an enterprise network, comprising: receiving, at a network device of a private Long Term Evolution (LTE) network operating in a Citizens Broadband Radio Service (CBRS) spectrum, a functional group associated with a user equipment (UE); receiving, at the network device, a traffic load of a cell of the private LTE network associated with the UE; determining an access priority associated with the functional group and the traffic load; as well as The access priority is provided to a CBRS access point (AP) that controls access to the cell, wherein the access priority indicates to the CBRS AP the priority with which the UE is allowed to access the cell, wherein providing the access priority to the CBRS AP includes providing the access priority to a mobility management entity (MME) of the private long term evolution (LTE) network based on a mapping table.

2. The method according to claim 1, wherein The access priority includes high priority, low priority or no access indication.

3. The method according to claim 2, wherein: If the UE is authenticated as being attached to the cell and one or more UEs of a functional group with a higher priority consume a traffic load of the cell, the access priority of the UE includes the no access indication.

4. The method according to claim 3, wherein: The no access indication is temporary for a period of time until the traffic load of the cell decreases.

5. The method according to any one of claims 1 to 4, wherein The functional group is received from the MME based on a request by the UE to establish an attachment to the cell.

6. The method according to any one of claims 1 to 4, wherein The network device is a Digital Network Architecture (DNA) device of the private Long Term Evolution (LTE) network.

7. The method of claim 6, further comprising receiving user profile and subscription information associated with the UE from one or more authentication, authorization, and accounting (AAA) servers of the private LTE network.

8. The method according to claim 7, wherein: The one or more AAA servers include a CBRS AAA server and an enterprise AAA server.

9. A system for an enterprise network, comprising: one or more processors; as well as A non-transitory computer-readable storage medium comprising instructions that, when executed on one or more processors, cause the one or more processors to perform the following operations, including: receiving, at a network device of a private Long Term Evolution (LTE) network operating in a Citizens Broadband Radio Service (CBRS) spectrum, a functional group associated with a user equipment (UE); receiving, at the network device, a traffic load of a cell of the private LTE network associated with the UE; determining an access priority associated with the functional group and the traffic load; and The access priority is provided to a CBRS access point (AP) that controls access to the cell, wherein the access priority indicates to the CBRS AP the priority with which the UE is allowed to access the cell, wherein providing the access priority to the CBRS AP includes providing the access priority to a mobility management entity (MME) of the private long term evolution (LTE) network based on a mapping table.

10. The system according to claim 9, wherein: The access priority includes high priority, low priority or no access indication.

11. The system according to claim 10, wherein: If the UE is authenticated as being attached to the cell and one or more UEs of a functional group with a higher priority consume a traffic load of the cell, the access priority of the UE includes the no access indication.

12. The system according to claim 11, wherein The no access indication is temporary for a period of time until the traffic load of the cell decreases.

13. The system according to any one of claims 9 to 12, wherein: The functional group is received from the MME based on a request by the UE to establish an attachment to the cell.

14. The system according to any one of claims 9 to 12, wherein: The network device is a Digital Network Architecture (DNA) device of the private Long Term Evolution (LTE) network.

15. The system of claim 14, further comprising receiving user profile and subscription information associated with the UE from one or more authentication, authorization, and accounting (AAA) servers of the private LTE network.

16. The system according to claim 15, wherein: The one or more AAA servers include a CBRS AAA server and an enterprise AAA server.

17. A non-transitory machine-readable storage medium comprising instructions, the instructions being configured to cause a data processing device to perform the following operations, including: receiving, at a network device of a private Long Term Evolution (LTE) network operating in a Citizens Broadband Radio Service (CBRS) spectrum, a functional group associated with a user equipment (UE); receiving, at the network device, a traffic load of a cell of the private LTE network associated with the UE; determining an access priority associated with the functional group and the traffic load; as well as The access priority is provided to a CBRS access point (AP) that controls access to the cell, wherein the access priority indicates to the CBRS AP the priority with which the UE is allowed to access the cell, wherein providing the access priority to the CBRS AP includes providing the access priority to a mobility management entity (MME) of the private long term evolution (LTE) network based on a mapping table.

18. The non-transitory machine-readable storage medium of claim 17, wherein: The access priority includes high priority, low priority or no access indication.

19. The non-transitory machine-readable storage medium of claim 18, wherein: If the UE is authenticated as being attached to the cell and one or more UEs of a functional group with a higher priority consume a traffic load of the cell, the access priority of the UE includes the no access indication.

20. The non-transitory machine-readable storage medium of claim 19, wherein: The no access indication is temporary for a period of time until the traffic load of the cell decreases.

21. An apparatus for an enterprise network, comprising: means for receiving, at a network device of a private Long Term Evolution (LTE) network operating in a Citizens Broadband Radio Service (CBRS) spectrum, a functional group associated with a user equipment (UE); means for receiving, at the network device, a traffic load of a cell of the private LTE network associated with the UE; means for determining an access priority associated with said functional group and said traffic load; as well as The access priority is provided to a device of a CBRS access point (AP) that controls access to the cell, wherein the access priority indicates to the CBRS AP the priority with which the UE is allowed to access the cell, wherein providing the access priority to the CBRS AP includes providing the access priority to a mobility management entity (MME) of the private long term evolution (LTE) network based on a mapping table.

22. The apparatus of claim 21, further comprising means for implementing the method of any one of claims 2 to 8.

23. A computer program product comprising instructions which, when executed by a computer, cause the computer to perform the steps of the method according to any one of claims 1 to 8.

24. A computer-readable medium comprising instructions which, when executed by a computer, cause the computer to perform the steps of the method according to any one of claims 1 to 8.

Images