Section: K.2.3 IOPS network configuration
Content: An IOPS network can comprise either: - a Local EPC and a single isolated IOPS-capable eNodeB, which may be co-located or have connectivity to the Local EPC; or - a Local EPC and two or more IOPS-capable eNodeBs, which have connectivity to a single Local EPC. Existing procedures described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ]  [5] can be used to achieve dynamic configuration of the S1-MME interface. An IOPS-capable eNodeB can be pre-provisioned with IP endpoint information, relating to the MMEs of one or more candidate Local EPC instances. For each local MME in turn the eNodeB can try to initialize a SCTP association. Once SCTP connectivity has been established, the eNodeB and local MME exchange application level configuration data over the S1-MME application protocol with the S1 Setup Procedure (see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ]  [36]). In line with local operator policies the eNodeB can be provisioned with the IP endpoint of a preferred Local EPC MME instance and the IP endpoints of one or more alternative Local EPC MME instances. The alternative Local EPC instances will be used if an S1-MME path cannot be established with the local MME of the preferred Local EPC instance. All Local EPCs deployed by a public safety authority / operator assume the same PLMN-Id. In order to achieve the broadcast of different TAIs on separate IOPS networks the TACs broadcast by the cells of eNodeBs connected to different Local EPCs are distinct to ensure the required UE mobility behaviour (see clause K.2.5). Therefore, the TAC broadcast by the cells of an eNodeB operating in IOPS mode will be dependent upon the Local EPC to which the eNodeB has established an S1-MME connection. If the scope of service of a Local EPC is a single eNodeB, then all cells served by the eNodeB share the same TAC (assigned for use in IOPS mode) and neighbouring eNodeBs that are also operating in IOPS mode with the same dedicated PLMN-Id are assigned different TACs (resulting in different TAIs) so a TAU attempt is triggered upon mobility. If multiple eNodeBs are configured to be served by a single Local EPC, configuration of TAIs for IOPS can be done according to local operator policies in such a way that a reselection to a cell operating a PLMN in normal mode always triggers an attach request. If sharing the same PLMN-Id, it is assumed the TAC assigned to cells in a Nomadic EPS would be different from the TACs assigned to infrastructure eNodeBs operating in IOPS mode, so as to trigger a TAU between these systems. The support by IOPS network entities of S1-flex and/or eMBMS is up to local operator policy and configuration.