TITLE

APPARATUS AND METHOD FOR REQUESTING/PROVIDING CAPABILITY

INFORMATION FOR SPECIFIC NETWORKS

BACKGROUND: Field:

[0001] Embodiments of t e invention generally relate to wireless or mobile communications networks, such as, but not limited to, the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), future 5G radio access technology, and/or High Speed Packet Access (HSPA).

Description of the Related Art:

[0002] Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) refers to a communications network including base stations, or Node Bs, and for example radio network controllers (RNC). UTRAN allows for connectivity between the user equipment (UE) and the core network. The RNC provides control functionalities for one or more Node Bs. The RNC and its corresponding Node Bs are called the Radio Network Subsystem (RNS). In case of E-UTRAN (enhanced UTRAN), no RNC exists and radio access functionality is provided in the evolved Node B (eNodeB or eNB) or many eNBs. Multiple eNBs are involved for a single UE connection, for example, in case of Coordinated Multipoint Transmission (CoMP) and in dual connectivity.

[0003] Long Term Evolution (LTE) or E-UTRAN provides a new radio access technology and refers to the improvements of UMTS through improved efficiency and services, lower costs, and use of new spectrum opportunities. In particular, LTE is a 3GPP standard that provides for uplink peak rates of at least, for example, 75 megabits per second (Mbps) per carrier and downlink peak rates of at least, for example, 300 Mbps per carrier. LTE supports scalable carrier bandwidths from 20 MHz down to 1 .4 MHz and supports both Frequency Division Duplexing (FDD) and Time Division Duplexing (TDD).

[0004] As mentioned above, LTE may also improve spectral efficiency in networks, allowing carriers to provide more data and voice services over a given bandwidth. Therefore, LTE is designed to fulfill the needs for high-speed data and media transport in addition to high-capacity voice support. Advantages of LTE include, for example, high throughput, low latency, FDD and TDD support in the same platform, an improved end- user experience, and a simple architecture resulting in low operating costs.

[0005] Certain releases of 3GPP LTE (e.g., LTE Rel-1 1 , LTE Rel-12, LTE Rel-13) are targeted towards international mobile telecommunications advanced (IMT-A) systems, referred to herein for convenience simply as LTE-Advanced (LTE-A).

[0006] LTE-A is directed toward extending and optimizing the 3GPP LTE radio access technologies. A goal of LTE-A is to provide significantly enhanced services by means of higher data rates and lower latency with reduced cost. LTE-A is a more optimized radio system fulfilling the international telecommunication union-radio (ITU-R) requirements for I MT- Advanced while keeping the backward compatibility. One of the key features of LTE- A, introduced in LTE Rel-10, is carrier aggregation, which allows for increasing the data rates through aggregation of two or more LTE carriers, e.g., to the transmission bandwidth of up to 100 MHz. LTE-A in later releases may include even wider bandwidths as specified so far. Further, aggregating or interworking on the radio access level with the wireless LAN (WLAN) access network is foreseen.

BRIEF DESCRIPTION OF THE DRAWINGS:

[0007] For proper understanding of the invention, reference should be made to the accompanying drawings, wherein:

[0008] Fig. 1 illustrates a diagram of a system, according to one embodiment;

[0009] Fig. 2 illustrates a diagram of a system, according to another embodiment;

[00010] Fig. 3a illustrates a block diagram of an apparatus according to an embodiment;

[00011] Fig. 3b illustrates a block diagram of an apparatus according to another embodiment;

[00012] Fig. 3c illustrates a block diagram of an apparatus according to another embodiment;

[00013] Fig. 3d illustrates a block diagram of an apparatus according to another embodiment;

[00014] Fig. 4a illustrates a flow diagram of a method according to one embodiment;

[00015] Fig. 4b illustrates a flow diagram of a method according to another embodiment;

[00016] Fig. 4c illustrates a flow diagram of a method according to another embodiment;

[00017] Fig. 4d illustrates a flow diagram of a method according to another embodiment;

[00018] Fig. 5a illustrates a block diagram of an apparatus according to an embodiment;

[00019] Fig. 5b illustrates a block diagram of an apparatus according to another embodiment;

[00020] Fig. 5c illustrates a block diagram of an apparatus according to another embodiment; and

[00021] Fig. 5d illustrates a block diagram of an apparatus according to another embodiment.

DETAILED DESCRIPTION:

[00022] It will be readily understood that the components of the invention, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of embodiments of systems, methods, apparatuses, and computer program products for requesting/providing capability information for specific networks, as represented in the attached figures, is not intended to limit the scope of the invention, but is merely representative of some selected embodiments of the invention.

[00023] The features, structures, or characteristics of the invention described throughout this specification may be combined in any suitable manner in one or more embodiments. For example, the usage of the phrases "certain embodiments," "some embodiments," or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present invention. Thus, appearances of the phrases "in certain embodiments," "in some embodiments," "in other embodiments," or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[00024] Additionally, if desired, the different functions discussed below may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions may be optional or may be combined. As such, the following description should be considered as merely illustrative of the principles, teachings and embodiments of this invention, and not in limitation thereof.

[00025] A small network, which could be referred to as a "local", "mini" or "small" evolved packet core (EPC), may be comprised of a core network entities/functionalities. These core network entities may include a local mobility management entity (MME), local home subscriber server (HSS), local packet data network gateway (PDN-GW) and the local EPC may connect to a base station (eNB) so as to form a small network on its own. The small network may also be called a "network-in-a-box." One issue related to the small network is how UEs connecting to this small network can be authenticated without storing duplicated credentials in both a local HSS located in the local EPC and a macro HSS located in the macro EPC, which would lead to security concerns. Stealing information from the local HSS means compromising the full system, in that the provisioning server sends the same credentials to all local HSSs and therefore not only one small network but all small networks are compromised.

[00026] Some embodiments of the invention may generally relate to the small networks introduced above, which as an example may be an isolated operation mode network, such as in isolated operation of E-UTRAN for public safety (IOPS) users. An isolated E-UTRAN network may comprise a single eNB or multiple eNBs. An IOPS network therefore is made up of one or more eNBs operating in IOPS mode and connected to a local evolved packet core (EPC).

[00027] The UEs in the coverage of the Isolated E-UTRAN network should be able to continue communicating among each other and provide a restricted set of services supporting voice, data and group communications, to their public safety users. An IOPS- capable eNB refers to an eNB that has the capability of IOPS mode operation, which provides a local IP connectivity and public safety services to the UEs via local evolved packet core (EPC), for example, when the eNB has lost backhaul to the Macro EPC, when the eNB has no backhaul to the Macro EPC, and/or when the eNB decides to operate in local EPC for other reasons (e.g., efficiency, load balancing, etc.). The Macro EPC refers to the EPC which serves an eNB in normal mode of operation.

[00028] SA1 has specified in 3GPP TS 22.346 a set of requirements for Isolated E- UTRAN stating that "The Isolated E-UTRAN is expected to provide for the authentication of participating entities and for the confidentiality and integrity of communications." Section 5.6.2 of TS 22.346 lists the requirements for security, authorization and privacy. In particular, it is required that the "Isolated E-UTRAN shall ensure the confidentiality and integrity of both user data and network signalling to a level comparable with that provided by the existing 3GPP system". It is noted that an Isolated E-UTRAN is characterized by having no backhaul connection or a limited backhaul connection. Limited backhaul means that either only limited bandwidth signalling backhaul or both limited bandwidth signalling and user data backhaul is available.

[00029] SA2 TR 23.797 defines an IOPS network as one or more eNBs with a co- located local EPC with no or limited backhaul. It may be operated with a fully functional "local EPC", in which case all EPC network elements, such as the local mobility management entity (MME), would be available. In an IOPS network with no backhaul, a local home subscriber server/authentication center (HSS/AuC) would need to have subscription details of all lOPS-UEs for running authentication and key agreement (AKA).

[00030] It should be noted that, while certain embodiments are described herein in reference to IOPS networks, this is merely one example and other embodiments are not necessarily limited to such networks. In fact, embodiments of the invention may be applicable in any situation where isolated mode can be used. One example is remote areas that can be connected via the "network-in-a-box" solution, or liquid applications.

[00031] Fig. 1 illustrates an example high level system architecture depicting the relation between an EPC and IOPS network. As illustrated in Fig. 1 , the system may include a UE 100, an eNB 101 , local EPC 102, and Macro EPC 105. The Local EPC 102 is an entity which provides functionality that eNBs in IOPS mode of operation use, instead of the Macro EPC 105, in order to support public safety services. Meanwhile, as mentioned above, the Macro EPC 105 is the EPC which serves an eNB in normal mode of operation. The local EPC 102 may include a local MME, local HSS/AuC, and other local components. The Macro EPC 105 may include a MME, HSS/AuC, and other components.

[00032] A MME may be considered the main control node for a core network. Some features handled by MME may include: bearer activation/de-activation, idle mode UE tracking, choice of serving gateway (SGW) for a UE, intra-LTE handover involving core network node location, interacting with the HSS to authenticate user on attachment, and providing temporary identities for UEs. HSS refers to a server comprising a central database that contains user-related and subscription-related information, for example. Functions of the HSS may be related to mobility management, call and session establishment support, user authentication and access authorization.

[00033] It is noted that IOPS can be set-up as a completely independent system. In this case, the local HSS may be completely pre-installed with subscriber data of all UEs that are allowed to be used in this system. In this situation, a problem arises that only those UEs that are known by the lOPS-Home Public Land Mobile Network (HPLMN) can be served. However, it could be advantageous if UEs that are IOPS capable but just visiting t e cell area served by this IOPS-HPLMN would also be allowed to attach.

[00034] In the case where IOPS is not an independent system (backhaul was earlier available or limited backhaul is still available), one solution is that the macro HSS is requested to provide international mobile subscriber identities (IMSIs) of UEs that are lOPS-capable to the local MME. Embodiments of the invention are able to avoid situations in which the macro HSS has no data record of lOPS-capable UEs and in such case cannot send any authenticating vectors (AVs) to the local MME (i.e., avoiding unnecessary requests from several local MMEs to the macro HSS), and in which the macro HSS is sending AVs to several local MMEs to which the UE may never attach (thus, generating many AVs that may never be needed, because the UE will never be in this traffic area).

[00035] At least these architecture scenarios can be improved by certain embodiments of the invention. Furthermore, embodiments of the invention provide a generalization for the provisioning of AVs to a local MME, which in fact could be provided by several network entities (e.g. , the macro HSS or macro MME) depending on the architecture decisions as will be discussed and specified in 3GPP.

[00036] 3GPP TR 23.797 states that when an authorized public safety (PS) UE selects the lOPS-mode cell, it attaches to the dedicated PLMN and is authenticated using security procedures to be identified by SA3. For example, a PS UE is provided with 2 USIM applications, one dedicated for IOPS and allowing only the access of the IOPS network for PS UEs that have before registered for this specific IOPS network. Certain embodiments of the invention provide a method and apparatus that allow a UE the usage of the same security procedures as in normal operation mode after it attaches to a cell in IOPS mode.

[00037] As will be discussed in detail below, embodiments of the invention provide that information on isolated E-UTRAN operation capable UEs is provided from the macro EPC (e.g., MME) to the local EPC (e.g., MME) proactively to prepare for the future isolated eNB operation mode. This may be useful because the probability is high that those UEs may still be located in the area in case of an isolation of the eNB. Some embodiments may especially serve the use case where the eNB switches from a normal mode to isolated mode and possibly back to the normal mode.

[00038] According to an embodiment, if an authorized PS UE attaches to the PLMN (macro EPC), the MME of the macro EPC keeps or stores a list of UEs (e.g., IMSIs or globally unique temporary identifier (GUTI)) that have been attached, and information whether these UEs are lOPS-capable, and optionally also to which traffic area they have attached. As long as macro EPC is available, the macro MME may perform the following: 1 ) the MME follows the usual procedure, i.e., if the macro MME has no authentication vector available for the UE, it requests authentication vectors from the HSS of the HPLMN for each IMSI ; 2) the MME of the macro EPC checks, for any UE that attaches to its PLMN in normal operation, whether that UE is also "lOPS-capable", i.e., a PS UE. The macro MME or another macro network entity keeps a record of this additional information, i.e., whether a particular UE, possibly identified by IMSI, can be used in IOPS mode.

[00039] Thus, according to one embodiment, an additional field may be added, e.g., in the database of a macro MME or macro HSS, to indicate the capability of a UE as "IOPS- capable" (assuming cell area of the UE current position is logged anyway). One alternative is to store the information in the macro HSS, and the macro MME can request and receive the information from the HSS.

[00040] Another embodiment provides an addition to the macro MME procedural behaviour when a UE attaches. If a macro MME gets an attach request it does its normal authentication and key agreement (AKA) procedure for providing service to the UE (i.e., either MME uses the available K ASME related to the IMSI of the UE or MME requests a new AV from the HSS/AuC), and additionally the MME sends the information "IOPS- capable UE with IMSI x has been attached", possibly including cell or traffic area information, to those local MMEs that would serve the same cell or traffic area in an IOPS mode situation. Such a local MME may be part of a local EPC co-located to eNBs that would serve the traffic area if the eNB would switch to the isolated mode. If there are several eNBs co-located to local EPCs, one or several local MMEs can store the information.

[00041] According to an embodiment, the local MME has only those lOPS-capable UEs, e.g., their IMSIs, stored that have been active in the cell or traffic area that would be served by this local MME. In this example embodiment, the purpose is to have a list of active UEs available in the local MME, since the probability is high that those may still be located in the area in case of an isolation of the eNB were to happen. Now, the local MME may pro-actively request AVs from the macro EPC (MME or HSS/AuC) for each of those lOPS-capable UEs, e.g. identified by their IMSIs, using the normal Sa6 protocol request. If several local MMEs have stored information about the same lOPS-capable UE, all of them may decide to ask the macro EPC. Each of the local MMEs would receive their own specific AVs. In an embodiment, the local MME knows from the identity of the IOPS- capable UE, e.g., the IMSI, whether there is a need to pro-actively request the AVs from the macro HSS. If, for example, the IMSI indicates that the local MME would need to ask the local HSS/AuC, then there is no need to do this pro-actively. Thus, requesting the AVs proactively may only be needed for visiting UEs, for example if t e local EPC has been pre-configured for a set of lOPS-capable UEs.

[00042] In an embodiment of the invention, there is no change in the existing Sa6 protocol and implementation and no change for the HSS, but in addition to the normal behavior of the MME, the macro MME informs local MMEs about lOPS-capable UEs that have attached in a certain cell or traffic area during normal mode of operation. If the local MME receives the list of identities of lOPS-capable UEs from the MME of the macro EPC and the local MME has already requested AVs for some of those UEs, the local MME does not need to request new AVs, if it decides that those AVs are sufficient, e.g., fresh enough. In this case, the local MME does not initiate a new request. Also, if the identity of the lOPS-capable UE, e.g., IMSI, is known to be served by the local EPC, i.e., pre- registered in the local HSS/AuC, there is no need to pro-actively request. This may only be needed for visiting UEs.

[00043] Fig. 1 illustrates an example system according to one embodiment of the invention. As illustrated in Fig. 1 , the system may include an IOPS capable UE 100, which sends an attach request to an eNB 101 . In this example embodiment, the eNB 101 may discover that there is no backhaul (i.e., S1 ) connectivity to the macro EPC and switch to the isolated mode of operation and to the local EPC 102. In an embodiment, the IMSI of the IOPS capable UE 100 may be forwarded to the local MME 103 of the local EPC 102. The local MME 103 may check if, for the IMSI of the IOPS capable UE 100, AV(s) are available. If so, the local MME 103 may provide AKA response.

[00044] In a MME data records can include list entries, for example, as follows:

[IMSI1 - AV(1 ..i) from PLMN1 ]

[IMSI2 - AV(1 ..j) from PLMN2] [IMSI3 - AV(1 ..k) from PLMN1 ]

Etc.

According to an embodiment of the invention, an additional entry in the database may look like the following:

[IMSI1 - AV(1 ..i) from PLMN1 , lOPS-capable (y/n)]

If, for example IMSI 1 and IMSI 3 are both lOPS-capable and would have been identified as served by one local MME, for which the MME would normally request AVs for serving network PLMN1 , the MME may decide to send IMSI1 and IMSI3 to the local MME, which can request AVs from HSS of PLMN1 using its own PLMN Id as the IOPS Serving Network Id. The HSS generates AVs and returns them to the local MME for IMSI1 and IMSI3. The local MME stores those AVs for the emergency case that no backhaul is available and the eNB needs to be operated with the local MME only. If IMSI2 is also IOPS capable, the MME sends IMSI2, but indicating PLMN2 as the home network. Thus, this time the local MME requests the AVs from the HSS of PLMN2, but using again its own PLMN Id as the IOPS SN Id.

[00045] Another embodiment of the invention provides that lOPS-capable UEs store and/or send an indication that they can be operated in isolated E-UTRAN. This may be an indicator, such as "allowed to be operated in isolated E-UTRAN", that is independent of whether the isolated E-UTRAN is used for public safety. In some embodiments, such an indicator may be stored by or be part of the ME (mobile equipment), or may be part of the UICC (Universal Integrated Circuit Card), possibly in a non-volatile part of ME or UICC.

[00046] If a UE needs to operate in an IOPS situation, it must be lOPS-capable and also be identifiable as such. As mentioned above, IOPS mode means that the eNB continues service via a local EPC which provides functionality that eNBs in isolated E- UTRAN mode of operation use (instead of the Macro EPC), in order to support public safety services.

[00047] While each UE could be allowed to use services in IOPS mode, it may be preferable that only the public safety community is using the limited services in case of no backhaul connectivity (according to 3GPP TS 22.346 and TR 23.797). Thus, the eNB and a local EPC may only serve UEs that are for public safety. Accordingly, only IOPS authorised UEs may be allowed to participate. However, currently no definition of an lOPS-capable UE is given in 3GPP TR 23.797 and TS 22.346 and behavior of network elements is not specified.

[00048] Future scenarios may include the commercial use case. For example, in the future, if commercial UEs would pay for an extra service to be also served in the IOPS situation by such an lOPS-capable eNB/local EPC, this would be an addition to the value chain. An interesting possibility is, in case of non-pre-configured IOPS networks, in which dynamic feeding of local MMEs with information of lOPS-capable UEs is possible. As one example, for a taxi or ride sharing business, it may be possible to keep your local MMEs up to state as to who is around and can be served locally.

[00049] In certain embodiments, it is assumed that an eNB has a co-located local EPC and is able to operate in isolated E-UTRAN. If such eNB has no backhaul connectivity (no S1 connection) to the macro EPC, it must decide whether to forward the UE attach request to t e local MME of the local EPC. 3GPP has set up a work item for isolated E- UTRAN in public safety (PS), such that only PS UEs are allowed to continue in such scenarios. 3GPP TS 22.346 specifies the following requirements: the Isolated E-UTRAN shall admit Public Safety UEs to the Isolated E-UTRAN, and the Isolated E-UTRAN shall manage Public Safety UE mobility between Nomadic eNBs ((N)eNBs) within the Isolate E- UTRAN. Therefore, the UE must be identifiable by eNBs to be authorized for lOPS mode of operation.

[00050] Thus, embodiments of the invention introduce an information element or indicator of whether the UE is authorized or not authorized for lOPS mode, and a method, configuration flag, or logic in the eNB is provided to decide whether to allow the UE to access the local MME and how to handle an attach request from the UE.

[00051] According to an embodiment, the indicator allows the eNB to make a decision whether the UE is allowed to operate in lOPS mode. This allows the eNB to process the attachment request to the local EPC. Whether the UE is allowed to operate still depends on the success of the AKA between the UE and local MME.

[00052] In situations where the eNB still has limited backhaul, but the operator has configured the eNB that in such case only public safety operation is allowed to use the backhaul connection, the eNB can use this indicator for allowing lOPS-capable UEs to attach and run AKA with the MME of the macro EPC by using the signalling on the backhaul. In situations where the eNB has no backhaul connectivity, it can still allow lOPS UEs to attach via the local MME.

[00053] The new information element (IE) indicating whether a UE is "lOPS Authorized" may provide information on the authorization status of the UE for lOPS services, as indicated in the following table:

[00054] Further, a definition for "lOPS-capable UE" may be provided as "An IOPS- capable UE is a public safety UE (PS UE) that is allowed to be operated in an lOPS network."

[00055] In an embodiment, once an eNB switches to lOPS mode it will reject UEs that have either no "lOPS Authorized" indicator or lOPS Authorized indicator set to "not authorized". According to certain embodiments, behavior of the eNB and the UE may depend on the information broadcast by the eNB in IOPS mode and the UE's operator configuration:

[00056] With respect to filtering of attach requests by the eNB, an embodiment may proceed based on the following:

• If the UE knows that eNB is operating in IOPS mode and UE is allowed to operate in IOPS mode, the UE may automatically add the indicator.

• If the UE does not know that eNB is in IOPS mode, UE will be rejected the first time, but can re-attempt with the indicator set to "authorized".

· UE can always set the indicator to its appropriate value regardless of the eNB to avoid resource waste in particular in emergency situations.

[00057] Selection of the MME may depend on configuration options of the operator. For example, if the UE performs an attach request with indicator set to "authorized", the eNB forwards to MME if normal operation of the network or it forwards to either MME or local MME if limited backhaul available (depending on operator policy how to manage limited backhaul). If the UE performs an attach request with indicator set to "authorized", the eNB forwards to local MME if IOPS mode of operation with no backhaul.

[00058] Fig. 2 illustrates an example system according to one embodiment of the invention. As illustrated in the example of Fig. 2, a UE 100 may send an attach request, which includes an indication of whether the UE is IOPS authorized, to a MME of macro EPC 105. The MME may then request the AV for the UE 100 from an HSS and receive the AV from the HSS. The MME may also check if the UE is IOPS capable and, if so, send the IMSI of the UE to the local MME 103 of local EPC 102. The local MME 103 may store the IMSI of the IOPS capable UE, and then request and receive the AV of the IMSI from the HSS. The local MME 103 may also store the received AV.

[00059] Fig. 3a illustrates an example of an apparatus 10 according to an embodiment. In an embodiment, apparatus 10 may be a node, host, or server in a communications network or serving such a network. For example, in certain embodiments, apparatus 10 may be a network entity or control entity for a radio access network, such as an LTE, LTE-A, or 5G network. In certain embodiments, apparatus 10 may be a network entity, such as an MME in a macro EPC, serving an eNB in normal mode. However, in other embodiments, apparatus 10 may be the eNB itself. It should be noted that one of ordinary skill in the art would understand that apparatus 10 may include components or features not shown in Fig. 3a.

[00060] As illustrated in Fig. 3a, apparatus 10 includes a processor 22 for processing information and executing instructions or operations. Processor 22 may be any type of general or specific purpose processor. While a single processor 22 is shown in Fig. 3a, multiple processors may be utilized according to other embodiments. In fact, processor 22 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples.

[00061] Apparatus 10 may further include or be coupled to a memory 14 (internal or external), which may be coupled to processor 22, for storing information and instructions that may be executed by processor 22. Memory 14 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and removable memory. For example, memory 14 may be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, or any other type of non- transitory machine or computer readable media. The instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 22, enable the apparatus 10 to perform tasks as described herein.

[00062] In some embodiments, apparatus 10 may also include or be coupled to one or more antennas 25 for transmitting and receiving signals and/or data to and from apparatus 10. Apparatus 10 may further include or be coupled to a transceiver 28 configured to transmit and receive information. For instance, transceiver 28 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 25 and demodulate information received via the antenna(s) 25 for further processing by other elements of apparatus 10. In other embodiments, transceiver 28 may be capable of transmitting and receiving signals or data directly.

[00063] Processor 22 may perform functions associated with the operation of apparatus 10 which may include, for example, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 10, including processes related to management of communication resources.

[00064] In an embodiment, memory 14 may store software modules that provide functionality when executed by processor 22. The modules may include, for example, an operating system that provides operating system functionality for apparatus 10. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 10. The components of apparatus 10 may be implemented in hardware, or as any suitable combination of hardware and software.

[00065] As mentioned above, in one embodiment, apparatus 10 may be a network entity or control entity in a radio access network, such as a MME or eNB. According to an embodiment, apparatus 10 may be controlled by memory 14 and processor 22 to determine, for each UE that attaches to a macro EPC, whether the UE is capable of isolated mode operation. In an embodiment, the isolated mode operation may be IOPS mode.

[00066] When it is determined that the UE is capable of isolated mode operation, apparatus 10 may be controlled by memory 14 and processor 22 to store a record indicating that the UE is isolated mode operation capable, and to send information that the UE is isolated mode operation capable to a local network entity that would serve the UE in an isolated mode operation situation. In an embodiment, the local network entity may be a local MME in a local EPC.

[00067] In certain embodiments, the information sent to the local network entity may include an indication that "isolated mode operation capable user equipment with international mobile subscriber identity x has been attached". According to one embodiment, the information further comprises traffic area information.

[00068] Fig. 3b illustrates an example of an apparatus 20 according to another embodiment. In an embodiment, apparatus 20 may be a node, host, or server in a communications network or serving such a network. For example, in certain embodiments, apparatus 20 may be a network entity or control entity for a radio access network, such as an LTE, LTE-A, or 5G network. In certain embodiments, apparatus 20 may be a network entity, such as a local MME in a local EPC. For example, the local MME may be the entity that serves the eNB when it loses backhaul connectivity. It should be noted that one of ordinary skill in the art would understand that apparatus 20 may include components or features not shown in Fig. 3b.

[00069] As illustrated in Fig. 3b, apparatus 20 includes a processor 32 for processing information and executing instructions or operations. Processor 32 may be any type of general or specific purpose processor. While a single processor 32 is shown in Fig. 3b, multiple processors may be utilized according to other embodiments. In fact, processor 32 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples.

[00070] Apparatus 20 may further include or be coupled to a memory 34 (internal or external), which may be coupled to processor 32, for storing information and instructions that may be executed by processor 32. Memory 34 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and removable memory. For example, memory 34 may be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, or any other type of non- transitory machine or computer readable media. The instructions stored in memory 34 may include program instructions or computer program code that, when executed by processor 32, enable the apparatus 20 to perform tasks as described herein.

[00071] In some embodiments, apparatus 20 may also include or be coupled to one or more antennas 35 for transmitting and receiving signals and/or data to and from apparatus 20. Apparatus 20 may further include a transceiver 38 configured to transmit and receive information. For instance, transceiver 38 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 35 and demodulate information received via the antenna(s) 35 for further processing by other elements of apparatus 20. In other embodiments, transceiver 38 may be capable of transmitting and receiving signals or data directly.

[00072] Processor 32 may perform functions associated with the operation of apparatus 20 including, without limitation, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 20, including processes related to management of communication resources.

[00073] In an embodiment, memory 34 stores software modules that provide functionality when executed by processor 32. The modules may include, for example, an operating system that provides operating system functionality for apparatus 20. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 20. The components of apparatus 20 may be implemented in hardware, or as any suitable combination of hardware and software.

[00074] As mentioned above, according to one embodiment, apparatus 20 may be a network entity, such as a local MME. In this embodiment, apparatus 20 may be controlled by memory 34 and processor 32 to receive information that a UE is isolated mode operation capable, where apparatus 20 is a network entity that would serve the UE in an isolated mode operation situation. In an embodiment, the UE has been active in a traffic area served by the network entity. Apparatus 20 may then be controlled by memory 34 and processor 32 to store the received information that the UE is isolated mode operation capable.

[00075] According to an embodiment, apparatus 20 may be controlled by memory 34 and processor 32 to request AVs from a HSS for each IMSI associated with the UE. Apparatus 20 may then be controlled by memory 34 and processor 32 to receive the AVs from the HSS and store the AVs.

[00076] Fig. 3c illustrates an example of an apparatus 40 according to another embodiment. In an embodiment, apparatus 40 may be a node or element in a communications network or associated with such a network. For instance, in some embodiments, apparatus 40 may be a mobile device, mobile unit, or user equipment (UE) associated with a communications network. It should be noted that one of ordinary skill in the art would understand that apparatus 40 may include components or features not shown in Fig. 3c.

[00077] As illustrated in Fig. 3c, apparatus 40 includes a processor 42 for processing information and executing instructions or operations. Processor 42 may be any type of general or specific purpose processor. While a single processor 42 is shown in Fig. 3c, multiple processors may be utilized according to other embodiments. In fact, processor 42 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples.

[00078] Apparatus 40 may further include or be coupled to a memory 44 (internal or external), which may be coupled to processor 42, for storing information and instructions that may be executed by processor 42. Memory 44 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and removable memory. For example, memory 44 may be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, or any other type of non- transitory machine or computer readable media. The instructions stored in memory 44 may include program instructions or computer program code that, when executed by processor 42, enable t e apparatus 40 to perform tasks as described herein.

[00079] In some embodiments, apparatus 40 may also include or be coupled to one or more antennas 45 for transmitting and receiving signals and/or data to and from apparatus 40. Apparatus 40 may further include a transceiver 48 configured to transmit and receive information. For instance, transceiver 48 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 45 and demodulate information received via the antenna(s) 45 for further processing by other elements of apparatus 40. In other embodiments, transceiver 48 may be capable of transmitting and receiving signals or data directly.

[00080] Processor 42 may perform functions associated with the operation of apparatus 40 including, without limitation, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 40, including processes related to management of communication resources.

[00081] In an embodiment, memory 44 stores software modules that provide functionality when executed by processor 42. The modules may include, for example, an operating system that provides operating system functionality for apparatus 40. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 40. The components of apparatus 40 may be implemented in hardware, or as any suitable combination of hardware and software.

[00082] As mentioned above, according to one embodiment, apparatus 40 may be a mobile device or UE. In this embodiment, apparatus 40 may be controlled by memory 44 and processor 42 to send, to an eNB, an indication of whether or not the apparatus 40 is authorized for isolated mode operation. In an embodiment, the indication is included in an information element for indicating whether the apparatus 40 is authorized for IOPS mode. According to certain embodiments, the indication may be sent along with an attach request to the eNB. In some embodiments, apparatus 40 may be controlled by memory 44 and processor 42 to add the indication to the attach request when the apparatus 40 knows that the eNB is operating in IOPS mode.

[00083] Fig. 3d illustrates an example of an apparatus 50 according to an embodiment. In an embodiment, apparatus 50 may be a node, host, or server in a communications network or serving such a network. For example, in certain embodiments, apparatus 50 may be a network node or control entity for a radio access network, such as a LTE, LTE-A, or 5G network. In certain embodiments, apparatus 50 may be a base station or eNB. However, in other embodiments, apparatus 50 may be other components within a radio access network. It should be noted that one of ordinary skill in the art would understand that apparatus 50 may include components or features not shown in Fig. 3d.

[00084] As illustrated in Fig. 3d, apparatus 50 includes a processor 52 for processing information and executing instructions or operations. Processor 52 may be any type of general or specific purpose processor. While a single processor 52 is shown in Fig. 3d, multiple processors may be utilized according to other embodiments. In fact, processor 52 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples.

[00085] Apparatus 50 may further include or be coupled to a memory 54 (internal or external), which may be coupled to processor 52, for storing information and instructions that may be executed by processor 52. Memory 54 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and removable memory. For example, memory 54 may be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, or any other type of non- transitory machine or computer readable media. The instructions stored in memory 54 may include program instructions or computer program code that, when executed by processor 52, enable the apparatus 50 to perform tasks as described herein.

[00086] In some embodiments, apparatus 50 may also include or be coupled to one or more antennas 55 for transmitting and receiving signals and/or data to and from apparatus 50. Apparatus 50 may further include or be coupled to a transceiver 58 configured to transmit and receive information. For instance, transceiver 58 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 55 and demodulate information received via the antenna(s) 55 for further processing by other elements of apparatus 50. In other embodiments, transceiver 58 may be capable of transmitting and receiving signals or data directly.

[00087] Processor 52 may perform functions associated with the operation of apparatus 50 which may include, for example, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 50, including processes related to management of communication resources.

[00088] In an embodiment, memory 54 may store software modules that provide functionality when executed by processor 52. The modules may include, for example, an operating system that provides operating system functionality for apparatus 50. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 50. The components of apparatus 50 may be implemented in hardware, or as any suitable combination of hardware and software.

[00089] As mentioned above, in one embodiment, apparatus 50 may be a network entity or control entity in a radio access network, such as a base station or eNB, for example. According to an embodiment, apparatus 50 may be controlled by memory 54 and processor 52 to receive an indication of whether or not a UE is authorized for isolated mode operation. In an embodiment, the indication may be received in an information element for indicating whether the UE is authorized for IOPS mode. According to one embodiment, the indication may be received along with an attach request to the apparatus 50. In certain embodiments, when the indication indicates that the UE is authorized for isolated mode operation and the apparatus 50 is in IOPS mode, apparatus 50 may be controlled by memory 54 and processor 52 to forward a message according to the UE capabilities to a local MME.

[00090] Fig. 4a illustrates an example flow diagram of a method, according to one embodiment of the invention. In one embodiment, the method of Fig. 4a may be performed by a network entity or control entity, such as an MME. As illustrated in Fig. 4a, the method may include, at 400, determining, for each UE that attaches to a macro EPC, whether the UE is capable of isolated mode operation. When it is determined that the UE is capable of isolated mode operation, the method may further include, at 410, storing a record indicating that the UE is isolated mode operation capable and, at 420, sending information that the UE is isolated mode operation capable to a local MME that would serve the UE in an isolated mode operation situation.

[00091] Fig. 4b illustrates an example flow diagram of a method, according to another embodiment of the invention. In one embodiment, the method of Fig. 4b may be performed by a network entity or control entity, such as a local MME in a local EPC. As illustrated in Fig. 4b, the method may include, at 430, receiving, by a network entity, information that a UE is isolated mode operation capable, where the network entity is a network entity that would serve the UE in an isolated mode operation situation. In an embodiment, the UE has been active in a traffic area served by the network entity. The method may also include, at 440, storing the received information that the user equipment is isolated mode operation capable. According to one embodiment, the method may include, at 450, requesting AVs from a HSS for each IMSI associated with the UE. At 460, the method may include receiving the AVs from the HSS and, at 465, storing the AVs.

[00092] Fig. 4c illustrates a flow diagram of a method, according to another embodiment. In one embodiment, the method of Fig. 4c may be performed by a UE, for example. The method may include, at 470, sending an indication of whether or not the UE is authorized for isolated mode operation to an eNB. The indication may be included in an information element for indicating whether the UE is authorized for IOPS. In an embodiment, the indication may be sent along with an attach request to the eNB. According to one embodiment, the method may further include adding the indication to the attach request when the UE knows that the eNB is operating in IOPS mode.

[00093] Fig. 4d illustrates an example flow diagram of a method, according to another embodiment of the invention. In one embodiment, the method of Fig. 4d may be performed by a network node or control entity, such as an eNB. As illustrated in Fig. 4d, the method may include, at 480, receiving an indication of whether or not a UE is authorized for isolated mode operation. The indication may be received in an information element for indicating whether the UE is authorized for IOPS. In an embodiment, the indication is received along with an attach request. According to one embodiment, when the indication indicates that the UE is authorized for isolated mode operation and the network node is in IOPS mode, the method may include, at 490, forwarding the user equipment IMSI to a local MME.

[00094] Fig. 5a illustrates a block diagram of an apparatus 500, according to an embodiment of the invention. In an embodiment, apparatus 500 may be a node, host, or server in a communications network or serving such a network, such as a MME. As illustrated in Fig. 5a, apparatus 500 may include a determining unit 505, storing unit 510, and transceiving unit 520. In an embodiment, determining unit 505 may determine, for each UE that attaches to a macro EPC, whether the UE is capable of isolated mode operation. In an embodiment, the isolated mode operation may be IOPS mode.

[00095] When it is determined that the UE is capable of isolated mode operation, storing unit 510 may store a record indicating that the UE is isolated mode operation capable, and transceiving unit 520 may send information that the UE is isolated mode operation capable to a local network entity that would serve the UE in an isolated mode operation situation. In an embodiment, the local network entity may be a local MME in a local EPC. In certain embodiments, the information sent to the local network entity may include an indication that "isolated mode operation capable user equipment with international mobile subscriber identity x has been attached". According to one embodiment, the information further comprises traffic area information.

[00096] Fig. 5b illustrates a block diagram of an apparatus 501 , according to another embodiment of the invention. In an embodiment, apparatus 501 may be a node, host, or server in a communications network or serving such a network, such as a local MME in a local EPC. As illustrated in Fig. 5b, apparatus 501 may include a transceiving unit 530, storing unit 540, and requesting unit 550. In an embodiment, transceiving unit 530 may receive information that a UE is isolated mode operation capable, where apparatus 500 is a network entity that would serve the UE in an isolated mode operation situation. In an embodiment, the UE has been active in a traffic area served by the network entity. Storing unit 540 may store the received information that the UE is isolated mode operation capable. According to an embodiment, requesting unit 550 may request AVs from a HSS for each IMSI associated with the UE. Transceiving unit 530 may receive the AVs from the HSS and storing unit 540 may store the AVs.

[00097] Fig. 5c illustrates a block diagram of an apparatus 502, according to another embodiment of the invention. In an embodiment, apparatus 502 may be a mobile device, mobile unit, or user equipment (UE) associated with a communications network. As illustrated in Fig. 5c, apparatus 502 may include a transceiving unit 560 and an adding unit 570. In an embodiment transceiving unit 560 may send, to an eNB, an indication of whether or not the apparatus 502 is authorized for isolated mode operation. In an embodiment, the indication is included in an information element for indicating whether the apparatus 502 is authorized for IOPS mode. According to certain embodiments, the indication may be sent along with an attach request to the eNB. In some embodiments, adding unit 570 may add the indication to the attach request when the apparatus 40 knows that the eNB is operating in IOPS mode.

[00098] Fig. 5d illustrates a block diagram of an apparatus 503, according to another embodiment of the invention. In an embodiment, apparatus 503 may be a network node or control entity for a radio access network, such as a base station or eNB. As illustrated in Fig. 5d, apparatus 503 may include a receiving unit 580 and a forwarding unit 590. In an embodiment, receiving unit 580 may receive an indication of whether or not a UE is authorized for isolated mode operation. In an embodiment, the indication may be received in an information element for indicating whether the UE is authorized for IOPS mode. According to one embodiment, the indication may be received along with an attach request to the apparatus 503. In certain embodiments, when the indication indicates that the UE is authorized for isolated mode operation and the apparatus 503 is in IOPS mode, forwarding unit 590 may forward the UE IMSI to a local MME.

[00099] In view of the above, embodiments of the invention provide several advantages and technical improvements. For example, in certain embodiments, no decision help from the HSS to identify which UEs to generate AVs for is needed. Additionally, embodiments allow lOPS-capable UEs to be served independently of the owner of the local EPC, if the public safety operator allows this feature for its UEs, such as in situations where police, firemen and hospital usually operate over different PLMNs but want to communicate together with priority. Another advantage is that the local MME has already the list of IMSIs available that have been active in the location area. Yet another advantage lays in combining embodiments of the present invention with the approach in which all PS UEs registered with one PLMN ID are pre-installed at a local HSS (as part of the local EPC). In this case, an advantage of the present invention lays in serving also roaming PS UEs that would usually not be allowed to use the network in this scenario. Thus, at the same time as serving the PS UEs for which the present PLMN Id is the HPLMN and which have been registered in the local HSS, it is possible to serve roaming PS UEs, for which the local MME has requested a list of AVs during backhaul connectivity. In addition, these mechanisms could be also commercially used in future.

[000100] According to embodiments, programs, also called program products or computer programs, including software routines, applets and macros, may be stored in any apparatus-readable data storage medium and they include program instructions to perform particular tasks. A computer program product may comprise one or more computer-executable components which, when the program is run, are configured to carry out embodiments. The one or more computer-executable components may be at least one software code or portions of it. Modifications and configurations required for implementing functionality of an embodiment may be performed as routine(s), which may be implemented as added or updated software routine(s). Software routine(s) may be downloaded into the apparatus.

[000101] Software or a computer program code or portions of it may be in a source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The computer readable medium or computer readable storage medium may be a non- transitory medium.

[000102] In other embodiments, the functionality of any method or apparatus described herein may be performed by hardware, for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another embodiment, the functionality may be implemented as a signal, a non-tangible means that may be carried by an electromagnetic signal downloaded from the Internet or other network.

[000103] According to an embodiment, an apparatus, such as a node, device, or a corresponding component, may be configured as a computer or a microprocessor, such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation and an operation processor for executing the arithmetic operation.

[000104] One having ordinary skill in the art will readily understand that the invention as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the invention has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the invention. In order to determine the metes and bounds of the invention, therefore, reference should be made to the appended claims.