Patent Description:
In wireless communication systems, a radio access network generally comprises one or more access nodes (such as a base station) which communicate on radio channels over a radio or air interface with plural wireless terminals. In some technologies such a wireless terminal is also called a User Equipment (UE). A group known as the 3rd Generation Partnership Project ("3GPP") has undertaken to define globally applicable technical specifications and technical reports for present and future generation wireless communication systems. The 3GPP Long Term Evolution ("LTE") and 3GPP LTE Advanced (LTE-A) are projects to improve an earlier Universal Mobile Telecommunications System ("UMTS") mobile phone or device standard in a manner to cope with future requirements.

In typical cellular mobile communication systems, the base station broadcasts on the radio channels certain information which is required for mobile stations to access to the network. In Long-Term Evolution (LTE) and LTE Advanced (LTE-A), such information is called "system information" ("SI"). Each access node, such as an evolved NodeB ("eNB") or a gNB (for, e.g., New Radio [NR] technology), broadcasts such system information to its coverage area via several System Information Blocks (SIBs) on downlink radio resources allocated to the access node.

Typical radio communication systems employ the capability to restrict/control accesses from users when the network is congested, known as Access Control (AC). In Long-Term Evolution (LTE) and LTE Advanced (LTE-A) (a. <NUM> network), every user equipment (UE) maintains at least one Access Class, a classifier programmed and saved in the Universal Integrated Circuit Card (UICC) inserted in the UE. During a congestion, the network may broadcast access barring information for each of the Access Classes on which the access restrictions are necessary.

In one method of AC, the access barring information may configure UEs to restrict all types of access attempts per Access Class. This configuration is referred as Access Class Barring (ACB). Other access restriction configurations introduced in LTE/LTE-A include Service Specific Access Control (SSAC) (restricting certain types of access, such as voice calls), ACB for Circuit Switched Fallback (CSFB) (restricting falling back to <NUM> voice services), Smart Congestion Mitigation (SCM) (restricting data communications initiated background during a voice call), Extended Access Barring (EAB) (AC for Machine-Type Communications) and Access Control for general Data Connectivity (ACDC) (restrict access from specific user applications). The access barring information for these configurations may be broadcasted by eNBs (base stations) in System Information Block Type <NUM> (SIB2) or System Information Block Type <NUM> (SIB14).

3GPP is currently discussing introduction of a unified approach for the Access Control scheme to be adopted for <NUM> network. This unified approach may be applicable to not only gNBs (<NUM> base stations) but also eNBs that connect to <NUM> core networks.

What is needed, therefore, and an example object of the technology disclosed herein, are methods, apparatus, and techniques for a wireless terminal to make access control decisions in dependence upon type(s) of core networks for which the wireless terminal is configured.

<CIT> describes a procedure for multiple mobile phone providers to either share or jointly use a radio access network for mobile telephony, in which a single radio access network is used jointly by multiple mobile phone providers, wherein to differentiate the central networks of each of the different mobile phone providers, the identity of each network operator is provided, the PLMN identity, in the radio access network, RAN or BSS, to the mobile telephone subscriber, UE or MS, through the sending of more than one mobile telephone operator identifier, PLMN identity, in a control channel common, BCCH, carrying out the issuance of more than one PLMN identity in a mobile telephone system according to the UMTS standard through the Master Information Block, MIB (Master Information Block), and/or the System Information Block <NUM>, SIB1 (System Information Block <NUM>), or in a mobile telephone system according to the GSM standard based on System Information Type <NUM>, SI3 (System Information Type <NUM>), and communicating the subscriber/subscriber terminal, when expressing a desire to connect to the radio access network by signaling a PLMN identity that has been selected from a multitude of PLMN identities issued on the BCCH, with which of the different core networks or PLMN a connection has to be established without having to change the radio access network.

<CIT> describes a method for access network sharing, among multiple core networks, including transmitting information about the core network sharing the common access network, e.g., a pseudo network identity or the number of core networks sharing the common access network or pointer information, in a system information message. The communication device uses the information provided in the system information message to connect to a core network.

<CIT> describes an enhanced access control method for machine-type communications (MTC) in a 3GPP LTE-Advanced network. An MTC device is configured for enhanced access barring (EAB). When the MTC device attempts access to the network, the NAS layer checks whether EAB is applicable for the MTC device. If yes, then the NAS layer forwards EAB configuration to the AS layer for further EAB control. Based on the EAB configuration, a base station broadcasts EAB information to UEs via system information block. The EAB information indicates whether barring is applied to a number of EAB categories and a number of access classes. Based on the EAB information, the MTC devices performs EAB for access attempt to RRC. If access is not barred under EAB, then the MTC device further performs ACB for access attempt to RRC.

There is provided a wireless terminal and a method in a wireless terminal, as defined in the independent claims, respectively.

The foregoing and other objects, features, and advantages of the technology disclosed herein will be apparent from the following more particular description of preferred embodiments as illustrated in the accompanying drawings in which reference characters refer to the same parts throughout the various views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the technology disclosed herein.

In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the technology disclosed herein. However, it will be apparent to those skilled in the art that the technology disclosed herein may be practiced in other embodiments. In some instances, detailed descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the technology disclosed herein with unnecessary detail. All statements herein reciting principles, aspects, and embodiments of the technology disclosed herein, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof.

Thus, for example, it will be appreciated by those skilled in the art that block diagrams herein can represent conceptual views of illustrative circuitry or other functional units embodying the principles of the technology. Similarly, it will be appreciated that any flow charts, state transition diagrams, pseudocode, and the like represent various processes which may be substantially represented in computer readable medium and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.

As used herein, the term "core network" can refer to a device, group of devices, or sub-system in a telecommunication network that provides services to users of the telecommunications network. Examples of services provided by a core network include aggregation, authentication, call switching, service invocation, gateways to other networks, etc..

As used herein, the term "wireless terminal" can refer to any electronic device used to communicate voice and/or data via a telecommunications system, such as (but not limited to) a cellular network. Other terminology used to refer to wireless terminals and non-limiting examples of such devices can include user equipment terminal, UE, mobile station, mobile device, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, cellular phones, smart phones, personal digital assistants ("PDAs"), laptop computers, netbooks, e-readers, wireless modems, etc..

As used herein, the term "access node", "node", or "base station" can refer to any device or group of devices that facilitates wireless communication or otherwise provides an interface between a wireless terminal and a telecommunications system. A non-limiting example of a base station can include, in the 3GPP specification, a Node B ("NB"), an enhanced Node B ("eNB"), a gNB (for, e.g., New Radio [NR] technology), a home eNB ("HeNB") or some other similar terminology. Another non-limiting example of a base station is an access point. An access point may be an electronic device that provides access for wireless terminal to a data network, such as (but not limited to) a Local Area Network ("LAN"), Wide Area Network ("WAN"), the Internet, etc. Although some examples of the systems and methods disclosed herein may be described in relation to given standards (e.g., 3GPP Releases <NUM>, <NUM>, <NUM>, <NUM>, and/or <NUM> and higher), the scope of the present disclosure should not be limited in this regard. At least some aspects of the systems and methods disclosed herein may be utilized in other types of wireless communication systems.

As used herein, the term "telecommunication system" or "communications system" can refer to any network of devices used to transmit information. A non-limiting example of a telecommunication system is a cellular network or other wireless communication system.

As used herein, the term "cellular network" can refer to a network distributed over cells, each cell served by at least one fixed-location transceiver, such as a base station. A "cell" may be any communication channel that is specified by standardization or regulatory bodies to be used for International Mobile Telecommunications-Advanced ("IMTAdvanced"). All or a subset of the cell may be adopted by 3GPP as licensed bands (e.g., frequency band) to be used for communication between a base station, such as a Node B, and a UE terminal. A cellular network using licensed frequency bands can include configured cells. Configured cells can include cells of which a UE terminal is aware and in which it is allowed by a base station to transmit or receive information.

As illustrated by the high level generic view of <FIG>, a typical radio communication system comprises a core network <NUM>; a radio access network including one or more base stations or access nodes <NUM>, and terminal devices <NUM> used by the end users. The Core Network (CN) <NUM> includes the central part of the radio communication system that provides various services to customers who are connected by the Radio Access Network. Example functions of a core network are discussed above. The core network in the <NUM> network is called Evolved Packet Core (EPC), whereas the core network in the <NUM> network is referred as <NUM> Core Network (5GCN). The Radio Access Network (RAN) comprises, e.g., is a part of, a radio communication system that resides between terminal devices and the core network. The RAN provides connectivity to the devices through radio interfaces via the base station(s) or access node(s) <NUM>, e.g., via eNB (in LTE/LTE-A RAN) or via gNB (in <NUM> RAN). The terminal devices <NUM> which are used by end users are also referred to as wireless terminals or User Equipment (UE).

While <FIG> shows a generic radio communications system <NUM>, <FIG> through <FIG> show architectural configurations of differing example embodiments and modes of respective radio communications systems <NUM>-<NUM> through <NUM>-<NUM>. Each radio communications system <NUM> comprises one or more core networks <NUM>, a base station or access node <NUM>, and one or more wireless terminals or UEs <NUM>. For example, radio communications system <NUM>-<NUM> comprises core network <NUM>-<NUM>, access node <NUM>-<NUM>, and wireless terminal <NUM>-<NUM>; radio communications system <NUM>-<NUM> comprises core network <NUM>-<NUM>, access node <NUM>-<NUM>, and wireless terminal <NUM>-<NUM>; and so forth. The example radio communications system <NUM>-<NUM> of <FIG> comprises two core networks, e.g., core network <NUM>-<NUM>-EPC and core network <NUM>-<NUM>-5GCN and two different types of wireless terminals, e.g., wireless terminal <NUM>-4LTE and wireless terminal <NUM>-<NUM>-eLTE.

One objective of various example embodiments and modes of the technology disclosed herein is to control access by the one or more wireless terminals <NUM> to the respective radio communications system <NUM>, particularly but not exclusively in a situation of network congestion. <FIG> shows a generic example embodiment and mode of both an access node <NUM> and a wireless terminal <NUM> for which such access control is implemented. <FIG> shows, for example, that radio access node <NUM> communicates over air or radio interface <NUM> (e.g., Uu interface) with wireless terminal <NUM>. As mentioned above, and depending upon which type of radio communications system <NUM> is employed, the radio access node <NUM> may be any suitable node for communicating with the wireless terminal <NUM>, such as a base station node, an eNodeB ("eNB"), or a gNB (for, e.g., New Radio [NR] technology), for example. The node <NUM> comprises node processor circuitry ("node processor <NUM>") and node transceiver circuitry <NUM>. The node transceiver circuitry <NUM> typically comprises node transmitter circuitry <NUM> and node receiver circuitry <NUM>, which are also called node transmitter <NUM> and node receiver <NUM>, respectively.

The wireless terminal <NUM> comprises terminal processor circuitry <NUM> ("terminal processor <NUM>") and terminal transceiver circuitry <NUM>. The terminal transceiver circuitry <NUM> typically comprises terminal transmitter circuitry <NUM> and terminal receiver circuitry <NUM>, which are also called terminal transmitter <NUM> and terminal receiver <NUM>, respectively. The wireless terminal <NUM> also typically but is not required to comprise user interface <NUM>. The terminal user interface <NUM> may serve for both user input and output operations, and may comprise (for example) a screen such as a touch screen that can both display information to the user and receive information entered by the user. The user interface <NUM> may also include other types of devices, such as a speaker, a microphone, or a haptic feedback device, for example.

For both the radio access node <NUM> and radio interface <NUM>, the respective transceiver circuitries <NUM> include antenna(s). The respective transmitter circuits <NUM> and <NUM> may comprise, e.g., amplifier(s), modulation circuitry and other conventional transmission equipment. The respective receiver circuits <NUM> and <NUM> may comprise, e.g., e.g., amplifiers, demodulation circuitry, and other conventional receiver equipment.

In general operation node, <NUM> and wireless terminal <NUM> communicate with each other across radio interface <NUM> using predefined configurations of information. By way of non-limiting example, the radio access node <NUM> and wireless terminal <NUM> may communicate over radio interface <NUM> using "frames" of information that may be configured to include various channels. In Long Term Evolution (LTE), for example, a frame, which may have both downlink portion(s) and uplink portion(s), may comprise plural subframes, with each LTE subframe in turn being divided into two slots. The frame may be conceptualized as a resource grid (a two dimensional grid) comprised of resource elements (RE). Each column of the two dimensional grid represents a symbol (e.g., an OFDM symbol on downlink (DL) from node to wireless terminal; an SC-FDMA symbol in an uplink (UL) frame from wireless terminal to node). Each row of the grid represents a subcarrier. The frame and subframe structure serves only as an example of a technique of formatting of information that is to be transmitted over a radio or air interface. It should be understood that "frame" and "subframe" may be utilized interchangeably or may include or be realized by other units of information formatting, and as such may bear other terminology (such as blocks, for example).

To cater to the transmission of information between radio access node <NUM> and wireless terminal <NUM> over radio interface <NUM>, the node processor <NUM> and terminal processor <NUM> of <FIG> are shown as comprising respective information handlers. For an example implementation in which the information is communicated via frames, the information handler for radio access node <NUM> is shown as node frame/signal scheduler/handler <NUM>, while the information handler for wireless terminal <NUM> is shown as terminal frame/signal handler <NUM>. It should be understood that, in differing technologies, the configurations of information may not necessarily be denominated as "frames" or have the LTE frame structure, but for such other differing technology the configurations of information may be otherwise structure and referenced.

The wireless terminal <NUM> also comprises a storage device or memory <NUM>. As explained herein with reference to <FIG>, for example, the memory <NUM> may take the form of read only memory (ROM), random access memory (RAM), cache memory, or semiconductor memory, just to name a few examples. One or more executable computer programs may be stored in program memory <NUM>. One or more applications executed by the terminal processor <NUM> of wireless terminal <NUM> in conjunction with services rendered by or using wireless terminal <NUM> may be stored in applications memory <NUM>.

In the various example embodiments and modes described herein, the wireless terminal <NUM> comprises a terminal access controller <NUM>, also known as access controller <NUM>. As described herein, the access controller <NUM> executes an access control program <NUM> generically depicted by <FIG> further shows that the access control program <NUM> generically employs access control information <NUM> obtained from the core network <NUM> in making access control checks. The execution of the access control program <NUM> results in performance of an access control procedure <NUM> which is generically shown in <FIG>.

The access controller <NUM> may comprise or be realized by, for example, terminal processor <NUM>. Thus, the wireless terminal <NUM> comprises a least one processor (e.g., terminal processor <NUM>) and at least one memory <NUM> (e.g., program memory <NUM>) including computer program code stored on non-transient memory. The memory <NUM> and the computer program code, e.g., of the access control program <NUM>, are configured to, working with the at least one processor, to perform access control operations of the generic access control procedure <NUM>. Whereas <FIG> shows a generic access control program <NUM>, <FIG> through <FIG> show respective other example access control programs <NUM>-<NUM> through <NUM>-<NUM> which may also be stored in memory and which, working with at least one processor, perform the access control operations of the respective access control procedures <NUM>-<NUM> through <NUM>-<NUM> shown in <FIG> through <FIG>, respectively.

As mentioned above, the access control program <NUM> is performed in conjunction with access control information <NUM>. The access control information <NUM>, in at least some example embodiments and modes, is received from the radio communications system. In example embodiments and modes, the access control information <NUM> may be transmitted to the wireless terminal <NUM> in broadcast system information. The broadcast system information may be formatted in system information, such as (for example) in one or more system information blocks (SIBs). Thus, <FIG> also shows the access node <NUM> as comprising system information generator <NUM>. The access control information <NUM>, which may be included in the system information generated by system information generator <NUM>, is transmitted by node transmitter <NUM> over radio interface premise <NUM> to the terminal receiver <NUM> of wireless terminal <NUM>, where it is handled by system information processor <NUM> of wireless terminal <NUM>.

A first example embodiment, not covered by the claims, is illustrated with reference to the radio communications system <NUM>-<NUM> of <FIG>, the access node <NUM>-<NUM> and wireless terminal <NUM>-<NUM> of <FIG>, the access control program <NUM>-<NUM> of <FIG>; and the access control procedure <NUM>-<NUM> of <FIG>. <FIG> particularly shows a network architecture for the <NUM> network, where the core network <NUM>-<NUM> is EPC, providing LTE/LTE-A services. In this case, the eNB <NUM>-<NUM> is capable of connecting only to EPC (not to 5GCN). The UE <NUM>-<NUM> shown in <FIG> is capable of receiving services provided by the <NUM> network and may also support <NUM> features. However, when connected to this eNB <NUM>-<NUM>, the UE <NUM>-<NUM> may not activate such <NUM> features.

The access controller <NUM>-<NUM> of <FIG> is shown as making an access control decision based on EPC access control information comprising access control barring parameters. The EPC access control barring parameters may be obtained from broadcast system information obtained from the core network <NUM>-<NUM>.

<FIG> shows that the access control program <NUM>-<NUM> executed by access controller <NUM> of <FIG> comprises an EPC access control check main routine <NUM>-<NUM>; access barring check subroutine <NUM>; extended access barring (EAB) check subroutine <NUM>; and access barring check for ACDC subroutine <NUM>. The EPC access control check main routine <NUM>-<NUM> utilizes EPC access control information <NUM>-<NUM> which, as shown in <FIG>, comprises access control barring parameters.

The access control procedure <NUM>-<NUM> performed upon execution of the EPC access control check main routine <NUM>-<NUM> is shown in <FIG>. As act <NUM>-<NUM>-<NUM>, an indication of an access attempt is received by the EPC access control check main routine <NUM>-<NUM>. As used herein, an indication of an access attempt may be received when an access attempt is generated for any reason, such as (for example) by an application (stored in applications memory <NUM>), e.g., upon requesting a service or connection for performance of the application, or for other reason associated with operation of the wireless terminal <NUM> (such as, for example, a tracking area update). Upon receiving an access attempt, as act <NUM>-<NUM>-<NUM> the EPC access control check main routine <NUM>-<NUM> determines whether the access attempt is barred. If the decision of act <NUM>-<NUM>-<NUM> is that the access request is not barred, then as act <NUM>-<NUM>-<NUM> the access is permitted. Otherwise, if the decision of act <NUM>-<NUM>-<NUM> is that the access request is barred, then as act <NUM>-<NUM>-<NUM> the access is not permitted.

A specific implementation of the access control program <NUM>-<NUM> of <FIG> and the access control procedure <NUM>-<NUM> of <FIG> is illustrated with reference to Listing <NUM> and Listing <NUM> provided below. Listing <NUM> shows the EPC access control information <NUM>-<NUM> for the first example embodiment and mode, Listing <NUM> describes in more detail example acts of the access control procedure <NUM>-<NUM> resulting from execution of access control program <NUM>-<NUM>.

In Listing <NUM>, the information element ac-BarringInfo comprises the information for Access Class Barring (ACB). The two information elements, ssac-BarringForMMTEL-Voice-r9 and ssac-BarringForMMTEL-Video-r9 comprise SSAC for restricting voice calls and video calls, respectively. ac-BarringForCSFB-r10 includes information for ACB for CSFB. ac-BarringSkipForMMTELVoice-r12, ac-BarringSkipForMMTELVideo-r12, ac-BarringSkipForSMS-r12 and ac-BarringPerPLMN-List-r12 information elements conveys barring parameters for SCM. acdc-BarringForCommon-r13 and acdc-BarringPerPLMN-List-r13 are the information elements for ACAD. Finally, SIB14 is dedicated for Extended Access Barring (EAB).

As indicated above, <FIG> shows a high level view of the UE access control procedure for the UE that has received SIB2/SIB14 for the first example embodiment and mode. The access control procedure <NUM>-<NUM> may be invoked when an event of an access attempt occurs in the UE. An access attempt is an action triggered by the UE to access the network for initiating services. Examples of such actions include (but not limited to) Radio Resource Control (RRC) connection establishment for a voice/video/data/emergency call, mobile-originated signaling messages and short message services (SMS). When such an access attempt occurs, the UE may perform Access Check shown in <FIG>, which may derive an access decision indicating whether this access attempt is allowed (not barred) or not (barred).

In Listing <NUM>, the acts of section <NUM>. <NUM> may comprise the access barring check subroutine <NUM>; the acts of section <NUM>. <NUM> may comprise the extended access barring (EAB) check subroutine <NUM>; and the acts of section <NUM>. <NUM> may comprise the access barring check for ACDC subroutine <NUM>. The other acts of Listing <NUM> may comprise the EPC access control check main routine <NUM>-<NUM>. The calls of the subroutines by EPC access control check main routine <NUM>-<NUM> may pass to the subroutines, or require the subroutines to utilize, a "Tbarring" and "AC barring parameter". The "Tbarring" is typically representative of a time value; the "AC barring parameter" typically comprises a value against which a number randomly generated by the subroutine is compared for determining if an access attempt is barred.

Listing <NUM> and Listing <NUM> refers to various timers, e.g., timer T302, timer T303, timer T305, timer T306 and timer T308. Timer T302 starts when receiving RRCConnectionReject while performing RRC connection establishment. In terms of Listing <NUM>, if T302 is still running, this means that RRC connection establishment is not allowed until the timer expires. Timer T303 starts when an access gets barred while performing RRC connection establishment for mobile originating calls. If running, mobile originating calls are still considered to be barred. Timer T305 starts when an access gets barred while performing RRC connection establishment for mobile originating signaling. If running, mobile originating signaling is still considered to be barred. Timer T306 starts when an access gets barred while performing RRC connection establishment for mobile originating CS fallback. If running, mobile originating CS fallback is still considered to be barred. Timer T308 starts when an access gets barred due to Access Control for general Data Connectivity (ACDC). If running, the cell is still barred for an access attempt subject to ACDC. <IMG>
<IMG>
<IMG>
<IMG>.

<IMG>
<IMG>
<IMG>
<IMG>
<IMG>
<IMG>
<IMG>
<IMG>.

A second example embodiment, not covered by the claims, is illustrated with reference to the radio communications system <NUM>-<NUM> of <FIG>, the access node <NUM>-<NUM> and wireless terminal <NUM>-<NUM> of <FIG>, the access control program <NUM>-<NUM> of <FIG>; and the access control procedure <NUM>-<NUM> of <FIG>. <FIG> particularly shows a network architecture for the <NUM> network, where the core network is 5GCN, providing <NUM> services. In this case, the <NUM> gNB <NUM>-<NUM> is capable of connecting only to 5GCN (not to EPC). The UE <NUM>-<NUM> shown in <FIG> supports <NUM> features and may also support LTE/LTE-A capabilities. However, when connected to this gNB <NUM>-<NUM>, the UE <NUM>-<NUM> may disable such LTE/LTE-A capabilities.

The access controller <NUM>-<NUM> of <FIG> is shown as making an access control decision using access control information included in broadcasted system information and an access category number. As described herein, the access category number is dependent upon both a type of access attempt and a condition related to the wireless terminal. Correspondingly, the system information generator <NUM> of <FIG> is shown as generating system information that includes access control information.

<FIG> shows that the access control program <NUM>-<NUM> executed by access controller <NUM>-<NUM> of <FIG> comprises <NUM> access control check main routine <NUM>-<NUM> and access barring check subroutine <NUM>. The <NUM> access control check main routine <NUM>-<NUM> utilizes <NUM> access control information <NUM>-<NUM>. Differing example, alternative formats of the <NUM> access control information <NUM>-<NUM> are shown in <FIG>, and <FIG>.

The access control program <NUM>-<NUM> shown in <FIG> for the second example embodiment and mode also includes categorization routine <NUM>. The categorization routine <NUM> utilizes <NUM> category configuration information <NUM>. In an example implementation, the <NUM> category configuration information <NUM> comprises both type of access attempt information and information concerning conditions related to the UE (wireless terminal). Table <NUM>-<NUM> below shows a generic implementation of the <NUM> category configuration information <NUM>, while Table <NUM>-<NUM> below shows a specific example implementation of the generic Table <NUM>-<NUM> with sample entries for the type of access attempts and the conditions related to the UE.

In more detail, the access control procedure <NUM>-<NUM> performed upon execution of the <NUM> access control check main routine <NUM>-<NUM> is shown in <FIG>. As act <NUM>-<NUM>-<NUM>, an indication of an access attempt is received by the access control program <NUM>-<NUM>. As used herein, an indication of an access attempt may be received when an access attempt is generated for any reason, such as (for example) by an application (stored in applications memory <NUM>), e.g., upon requesting a service or connection for performance of the application, or for other reason associated with operation of the wireless terminal <NUM>-<NUM> (such as, for example, a tracking area update). Upon receiving an access attempt, as act <NUM>-<NUM>-<NUM> the categorization routine <NUM> categorizes the access attempt using the <NUM> category configuration information <NUM>. In an example implementation, the categorization routine <NUM> uses both the type of access attempt information and information concerning conditions related to the UE as understood with reference, for example, to Table <NUM>-<NUM> and Table <NUM>-<NUM>. As a result of act <NUM>-<NUM>-<NUM>, the categorization routine <NUM> outputs an access category number. As act <NUM>-<NUM>-<NUM> the <NUM> access control check main routine <NUM>-<NUM> uses both the access category number and the access control information <NUM>-<NUM> to determine whether the access attempt is barred. If the decision of act <NUM>-<NUM>-<NUM> is that the access request is not barred, then as act <NUM>-<NUM>-<NUM> the access is permitted (e.g., not barred). Otherwise, if the decision of act <NUM>-<NUM>-<NUM> is that the access request is barred, then as act <NUM>-<NUM>-<NUM> the access is not permitted.

As mentioned above, Table <NUM>-<NUM> is a generic structure of the <NUM> access category configuration information <NUM>. In Table <NUM>-<NUM>, the column "type of access attempt" specifies the classification of the access attempt (such as, for sake of example, "emergency call", and "mobile-originated signaling") and the column "Conditions related to UE" may indicate any additional conditions that apply to classify the access attempt. When an access attempt is generated, the UE may use a table such as Table <NUM>-<NUM> or Table <NUM>-<NUM> to determine the access category by finding the suitable access category number whose "Conditions related to UE" and "Type of access attempt" both match.

The operation of categorizing an access attempt may be explained using an exemplary implementation of the <NUM> access category configuration information shown in Table <NUM>-<NUM>. Suppose, for example, that the access attempt is a short message service (SMS), that the UE is not configured for delay tolerant service, and the Access Class of the UE is <NUM>. In such case the Access category number is <NUM>. As another example case, if the access attempt is for an emergency call and one of the Access Classes is <NUM>, then the Access category number is <NUM>.

In the case there are more than one access category match, in one non-limiting example configuration, the UE <NUM>-<NUM> may choose the one in the highest order (e.g., listed earlier/higher in the Table <NUM>-<NUM>, e.g., with smallest access category number), or alternatively the lowest order in the Table <NUM>-<NUM> (e.g., with the greatest access category number). In this case, choosing either the highest or lowest may be pre-configured or configured by the network through broadcast signal (such as System Information).

The UE <NUM>-<NUM> then further performs AC Check shown as act <NUM>-<NUM>-<NUM> in <FIG> to determine whether the Access category is barred at this moment. In order to do so, the UE <NUM>-<NUM> may have already received <NUM> access control information <NUM>-<NUM> broadcasted by the gNB via System Information.

As used herein, the <NUM> access control information <NUM>-<NUM> is also known as 5gAccessBarringInfo. <FIG> shows a first example configuration of <NUM> access control information <NUM>-2A wherein each access category that is subject to barring is associated with the access barring configuration (AC-BarringConfig). The access barring configuration (AC-BarringConfig) includes the ac-barring parameters such as ac-BarringFactor, ac-BarringTime, and ac-BarringForSpecialAC, all as previously described.

Only the access category numbers that are potentially subject to barring are included in the access control information <NUM>-<NUM>: any access category that is not potentially subject to barring is not included. For example, <FIG> shows that each of AccessCategory#i, AccessCategory#j, and AccessCategory#k may be potentially subject to barring. It should be understood that for <FIG> each of AccessCategory#j, and AccessCategory#k have the AC-BarringConfig information elements in the same manner as shown in the tree like structure for AccessCategory#i, but with barring values for the respective AccessCategory#j, and AccessCategory#k.

By "potentially subject to barring" is meant that the access category may or may not be barred depending on the evaluation of the subroutine (access barring check subroutine <NUM>) that may be invoked by the <NUM> access control check main routine <NUM>-<NUM>. As such, whether the access category is barred may in turn depend on the ac-barring parameters such as ac-BarringFactor, ac-BarringTime, and ac-BarringForSpecialAC as evaluated by the appropriate subroutine. For example, when the determined access category is one of the access categories listed in the 5gAccessBarringInfo, the UE may apply (for example) the associated access barring configuration, per "<NUM>. <NUM> Access barring check" in Listing <NUM> as discussed in conjunction with embodiment <NUM>.

In view of the foregoing, it will be appreciated that access node <NUM>-<NUM> of <FIG> may generate access control information in a particular format. In particular, the system information generator <NUM> of access node <NUM>-<NUM> may generate an access control information element (e.g., AC-BarringConfig) comprising access control information. The access control information element may comprise: one or more access category numbered information elements (e.g., AccessCategory#i, AccessCategory#j, and AccessCategory#k) which identify respective one or more access categories which are subject to potential barring from access; and for each access category numbered information element, one or more access control parameter information elements (e.g., ac-BarringFactor, ac-BarringTime, and ac-BarringForSpecialAC) configured to be used for evaluation by a wireless terminal in making an access control decision. The node transmitter <NUM> is configured to transmit the access control information element over the radio interface to the wireless terminal <NUM>-<NUM>.

In one network deployment configuration, the gNB/RAN may be shared by more than one operator. In order to support independent access control scheme for each operator, 5gAccessBarringInfo may be constructed in the manner shown in <FIG>, where for each Public Land Mobile Network (PLMN) identifying a network operator, barred access categories and associated access barring configurations are specified. Thus, in <FIG>, a first or upper tier grouping is based on PLMN number and the second tier grouping is based on access category number. <FIG> shows information elements for each of PLMN#p, PLMN#q, and PLMN#r. It should be understood that for <FIG> each of PLMN#p, PLMN#q, and PLMN#r have an associated one or more access category information elements, such as AccessCategory#i, AccessCategory#j, and AccessCategory#k shown only for PLMN#p. The access category numbers associated with different PLMNs may be different, but the same type of tree structure is applicable.

<FIG> thus illustrates that the access control information may comprise identifiers of plural public land mobile network (PLMN) identifiers, and that the one or more access category numbered information elements may be associated with one of the PLMN identifiers. <FIG> particularly shows that the one or more access category numbered information elements are associated with one of the PLMN identifiers by being sub-information elements of information elements for the respective PLMN identifiers.

<FIG> is an alternative implementation of <FIG>, wherein a first or upper tier grouping is based on access category number and the second tier grouping is based on PLMN number. It should be understood that for <FIG> each of AccessCategory#i, AccessCategory#j, and AccessCategory#k have an associated one or more access category information elements, such as PLMN#p, PLMN#q, and PLMN#r. Again, the PLMN numbers associated with different access categories may be different, but the same type of tree structure is applicable. <FIG> thus illustrates that the one or more access category numbered information elements are associated with one of the PLMN identifiers by information elements for the respective PLMN identifiers being sub-information elements of a respective one of the one or more access category numbered information elements.

The <NUM> gNB <NUM>-<NUM> may broadcast the 5gAccessBarringInfo information element shown in <FIG>, or <FIG> on its <NUM> (also referred as New Radio) radio interface. In one non-limiting example implementation, the 5gAccessBarringInfo information element may comprise (e.g., be a part of or included in) a SIB which may or may not be dedicated to access barring purposes. In another example non-limiting implementation the 5gAccessBarringInfo information element may comprise an independent SIB (SIBx) dedicated to access barring purposes.

<FIG> shows basic, representative acts or steps performed by a <NUM> access node <NUM>-<NUM> in accordance with the example embodiment and mode of <FIG>, and particularly for generating an access control information element. Act <NUM>-<NUM> comprises using processor circuitry (e.g., node processor <NUM>) to generate an access control information element comprising access control information. Act <NUM>-<NUM> comprises including in the access control information element one or more access category numbered information elements which identify respective one or more access categories which are subject to potential barring from access. Act <NUM>-<NUM> comprises, for each access category numbered information element, including one or more access control parameter information elements configured to be used for evaluation by a wireless terminal in making an access control decision. Act <NUM>-<NUM> comprises transmitting the access control information element over a radio interface to the wireless terminal <NUM>-<NUM>.

A third example embodiment, not covered by the claims, is illustrated with reference to the radio communications system <NUM>-<NUM> of <FIG>, the access node <NUM>-<NUM> and wireless terminal <NUM>-<NUM> of <FIG>, the access control program <NUM>-<NUM> of <FIG>; and the access control procedure <NUM>-<NUM> of <FIG>. <FIG> particularly shows a network architecture for embodiment <NUM>, where the core network is 5GCN, providing <NUM> services. In this case, the LTE eNB <NUM>-<NUM> supports the LTE/LTE-A radio interface and is able to connect to 5GCN <NUM>-<NUM> (and thus also serves as eNB-<NUM>). The UE <NUM>-<NUM> camping on this eNB-<NUM> supports <NUM> protocols necessary for services provided by the 5GCN core network <NUM>-<NUM>. In order to prevent UEs not supporting the <NUM> features/protocols from camping on this eNB-5B, the eNB-<NUM> may transmit an indication of supported core network (e.g. EPC or 5GCN) via a broadcasted manner (e.g. in Master Information Block (MIB) or in at least one SIB) so that the UE that does not support <NUM> may be motivated to seek an LTE cell instead.

In the network configuration of <FIG> and in Embodiment <NUM>, due to the core network capabilities, the <NUM> (unified) access control scheme disclosed in Embodiment <NUM> may be used. Namely, the eNB-<NUM> <NUM>-<NUM> may broadcast the 5gAccessBarringInfo information element shown in <FIG>, or <FIG> on its LTE/LTE-A radio interface. In one configuration, the information element is a part of an existing LTE/LTE-A SIB, such as SIB2. In another configuration, it is included in an independent SIB (SIBx). The UE procedure for receiving the SIB and the actions on an access attempt may be the same as described in Embodiment <NUM>.

Like the second embodiment, the access controller <NUM>-<NUM> of <FIG> is shown as making an access control decision using access control information included in broadcasted system information and an access category number. As described herein, the access category number is dependent upon both a type of access attempt and a condition related to the wireless terminal.

<FIG> shows that the wireless terminal <NUM>-<NUM> of <FIG> may execute a network detection routine <NUM> to determine to which and what type of network the wireless terminal <NUM>-<NUM> is in communication. Execution of the network detection routine <NUM> may comprise receipt of an indication of supported core network (e.g. EPC or 5GCN) via a broadcasted manner (e.g. in Master Information Block (MIB) or in at least one SIB) from the eNB-<NUM>.

The access control procedure <NUM>-<NUM> of <FIG> is essentially the same as the access control procedure <NUM>-<NUM> of <FIG>. The acts of <FIG> are identified as <NUM>-<NUM>-x, but are essentially the same as the acts <NUM>-<NUM>-x of <FIG>.

A fourth example embodiment and mode according to the present invention is illustrated with reference to the radio communications system <NUM>-<NUM> of <FIG>, the access node <NUM>-<NUM> and wireless terminal <NUM>-<NUM>-eLTE of <FIG>, the access control program <NUM>-<NUM> of <FIG>; and the access control procedure <NUM>-<NUM> of <FIG>. <FIG> particularly shows the network architecture of the fourth embodiment, where the eNB-<NUM> <NUM>-<NUM> is connected to both EPC CN <NUM>-<NUM>-EPC and 5GCN <NUM>-<NUM>-5GCN. Similar to Embodiment <NUM>, the eNB-<NUM> <NUM>-<NUM> may broadcast (e.g. in MIB or SIB) the indication of supported core networks (indicating support of both EPC and 5GCN).

In this embodiment, the eNB-<NUM> <NUM>-<NUM> broadcasts the EPC access control information, such as SIB2 and/or SIB <NUM> disclosed in the Embodiment <NUM>, in order to support access control for EPC. In parallel, the eNB-<NUM> <NUM>-<NUM> may also broadcast the <NUM> access category configuration information as disclosed in Embodiment <NUM> in order to support access control for 5GCN. Accordingly, to illustrate the parallel broadcast of different types of system information, the system information generator <NUM> of <FIG> as shown as comprising LTE system information generator <NUM>-LTE and <NUM> system information generator <NUM>-<NUM>. The LTE system information may be included in an existing LTE/LTE-A SIB (e.g. SIB2). As described in Embodiment <NUM>, the <NUM> access category configuration information may be incorporated into an existing LTE/LTE-A SIB (e.g. SIB2) or may be included in an independent SIB (SIBx).

As shown in <FIG>, two types of UEs or wireless terminals that may camp on eNB-<NUM> <NUM>-<NUM>: UEs that support only EPC (such as UE <NUM>-<NUM>-LTE of <FIG>) and UEs that support both EPC and 5GCN (such as UE <NUM>-<NUM>-eLTE of <FIG>). Of these two UE types, the LTE-UE <NUM>-<NUM>-LTE may be able to camp on the eNB-<NUM> but may be able to receive only services from EPC. For this reason, the LTE-UE <NUM>-<NUM>-LTE may process only the EPC access control information and follow the UE procedure upon an arrival of an access attempt as specified in Embodiment <NUM>. On the other hand, due to its dual core network connectivity, the UE <NUM>-<NUM>-eLTE may be subject to access control from either or both of EPC core network <NUM>-<NUM>-EPC and core network <NUM>-<NUM>-5GCN. Therefore, the wireless terminal <NUM>-<NUM>-eLTE may process the EPC access control information as well as the <NUM> access category configuration information (for 5GCN). The access control program <NUM>-<NUM> of <FIG> and the access control procedure <NUM>-<NUM> of <FIG> described herein are thus program and procedure executed/performed by wireless terminal <NUM>-<NUM>-eLTE.

The access controller <NUM>-<NUM> of the wireless terminal <NUM>-<NUM>-eLTE of <FIG> is shown as making an aggregated access control decision. <FIG> shows that the access control program <NUM>-<NUM> executed by access controller <NUM>-<NUM> of <FIG> comprises the access control program <NUM>-<NUM> (shown in <FIG>, which is an access control program for EPC), the access control program <NUM>-<NUM> (shown in <FIG>, which is an access control program for <NUM>), and multicore network aggregated access control routine <NUM> (described below).

The access control procedure <NUM>-<NUM> performed upon execution of the access control program <NUM>-<NUM> of <FIG> is shown in <FIG>. As act <NUM>-<NUM>-<NUM>, an indication of an access attempt is received by access control program <NUM>-<NUM>. As used herein, an indication of an access attempt may be received when an access attempt is generated for any reason, such as (for example) by an application (stored in applications memory <NUM>), e.g., upon requesting a service or connection for performance of the application, or for other reason associated with operation of the wireless terminal <NUM> (such as, for example, a tracking area update). Upon receiving an access attempt, the access control program <NUM>-<NUM> executes both act <NUM>-<NUM>-<NUM> and <NUM>-<NUM>-<NUM>, in parallel (either essentially simultaneously or consecutively). Act <NUM>-<NUM>-<NUM> comprises executing the EPC access control program <NUM>-<NUM>; act <NUM>-<NUM>-<NUM> comprises executing the <NUM> access control program <NUM>-<NUM>. Execution of the EPC access control program <NUM>-<NUM> results in an EPC access control decision, which EPC access control decision is either "barred" or "not barred". Likewise, execution of the <NUM> access control program <NUM>-<NUM> results in a <NUM> access control decision, which <NUM> access control decision is either "barred" or "not barred". Act <NUM>-<NUM>-<NUM> comprises execution of the multi core network aggregated access control routine <NUM>. Execution of the multicore network aggregated access control routine <NUM> utilizes as inputs both the EPC access control decision and the <NUM> access control decision, and possibly/optionally other inputs (e.g., configured parameter(s) or configured information).

<FIG> thus illustrates the procedure for the wireless terminal <NUM>-<NUM>-eLTE upon an arrival of an access attempt, wherein the access attempt is evaluated by two branches, the AC procedure for EPC (Embodiment <NUM>) as act <NUM>-<NUM>-<NUM> and the AC procedure for 5GCN (Embodiment <NUM>) as act <NUM>-<NUM>-<NUM>. For this purpose, the wireless terminal <NUM>-<NUM>-eLTE may have been pre-configured with the <NUM> access category configuration information as disclosed in Embodiment <NUM>.

For such an access attempt, each of those two branches, e.g., access control program <NUM>-<NUM> of act <NUM>-<NUM>-<NUM> and access control program <NUM>-<NUM> of act <NUM>-<NUM>-<NUM>, may generate their respective access decisions, such as access allowed (not barred) or access not allowed (barred). The decisions from the two branches may be fed into the multi core network aggregated access control routine <NUM>, so that act <NUM>-<NUM>-<NUM> of <FIG> is performed in order to generate an aggregated access control decision.

There are the following four cases for the input of the Multi core network access decision:.

In case of Case <NUM>, the access attempt is barred. The wireless terminal <NUM>-<NUM>-eLTE may cancel or postpose the attempt.

For Case <NUM> or Case <NUM>, in one non-limiting example implementation, the <NUM>-<NUM>-LTE may fallback to whichever network allowed the access and proceed to initiating access through that allowing network. In another configuration, the wireless terminal <NUM>-<NUM>-eLTE may be configured with a set of configuration parameters to determine if the allowed network is suitable. For example, access attempts for certain types of applications/services may be only available in 5GCN (or EPC). In this case, the configuration parameters may instruct the wireless terminal <NUM>-<NUM>-eLTE the suitability of the core network per application/service. If suitable, the wireless terminal <NUM>-<NUM>-eLTE may proceed in initiating access through that allowing network, otherwise, it may consider the access attempt is barred.

For Case <NUM>, in one non-limiting example configuration, the choice of the core network may be pre-configured in the wireless terminal <NUM>-<NUM>-eLTE. For instance, the wireless terminal <NUM>-<NUM>-eLTE may automatically choose to access 5GCN (or EPC). In another example implementation, another set of configuration parameters may indicate the priorities of the core networks. In some example implementations, this set of configuration parameters may be also per application/service as described above.

The configuration parameters for Case <NUM>, <NUM> or <NUM> may be preloaded into the wireless terminal <NUM>-<NUM>-eLTE or transmitted (broadcast or unicast) by eNG-<NUM>.

Thus, the terminal processor <NUM> (e.g., access controller <NUM>-<NUM>) of wireless terminal <NUM>-<NUM>-eLTE is configured to perform a first access control procedure configured for a first core network and to obtain therefrom a first access control decision; perform a second access control procedure configured for a second core network and to obtain therefrom a second access control decision; and then make an aggregated access control decision dependent at least in part on the first access control decision and the second access control decision, the aggregated access control decision determining an appropriate one of the first core network and the second core network. For example, with reference to <FIG> as a non-limiting example, the first access control procedure may result from execution of the LTE access control program <NUM>-<NUM> (e.g., act <NUM>-<NUM>-<NUM>) and the first access control decision may an LTE access control decision of either barred or not barred; the second access control procedure may result from execution of the <NUM> access control program <NUM>-<NUM> (e.g., act <NUM>-<NUM>-<NUM>) and the second access control decision may a <NUM> access control decision of either barred or not barred; and the aggregated access control decision may be obtained upon execution of multicore network aggregated access control routine <NUM>. The terminal transmitter <NUM> of wireless terminal <NUM>-<NUM>-eLTE is configured to transmit, over a radio interface, an access request to the appropriate core network.

It should be understood that, although <FIG> shows the first core network is being a <NUM> LTE core network and the second core network as being a <NUM> core network, that the network selection of the technology disclosed herein is not limited to any specific one or more types networks, but that the technology disclosed herein may be applicable to other types of existing or here-after developed core networks.

As understood from <FIG>, and particularly the discussion of case <NUM> and case <NUM> above, when one of the first access control decision and the second access control decision is a negative decision and another of the first access control decision and the second access control decision is a positive decision (e.g., a case <NUM> or case <NUM> split decision), the access controller <NUM>-<NUM> is configured to make the aggregated access control decision to initiate the access request to whichever of the first core network and the second core network is the appropriate core network as indicated by the positive decision. Moreover, in a split decision situation such as case <NUM> or case <NUM>, the access controller <NUM>-<NUM> may make the aggregated access control decision not only on the first access control decision and the second access control decision, but may also make the aggregated access control decision based on a parameter configured at the wireless terminal. For example, such parameter configured at the wireless terminal may indicate whether the appropriate core network, although passing the case <NUM>/case <NUM> analysis, is nevertheless suitable for the access request. As mentioned above, for example, it may be that, under certain circumstances, although one of the EPC access control program <NUM>-<NUM> and the <NUM> access control program <NUM>-<NUM> indicates that their respective core networks are appropriate, the configured parameter may nevertheless preclude or override sending an access request to the supposedly appropriate network at this particular point in time. Such preclusion or override may be based, for example, upon whether the appropriate core network is suitable for a service or application associated with the access request.

The multi core network aggregated access control routine <NUM> and act <NUM>-<NUM>-<NUM> may use configuration information for case <NUM> as well, e.g., when both the first access control decision and the second access control decision are positive decisions. For case <NUM> the access controller <NUM>-<NUM> upon executing the multi core network aggregated access control routine <NUM> as act <NUM>-<NUM>-<NUM> may make the aggregated access control decision based at least in part on configuration information. For example, as act <NUM>-<NUM>-<NUM> the access controller <NUM>-<NUM> may make the aggregated access control decision based on configuration information which indicates a relative priority of the first core network and the second core network. As a non-limiting example, when the first core network is a <NUM> LTE core network and the second core network is a <NUM> core network, the configuration information utilized by multicore network aggregated access control routine <NUM> in act <NUM>-<NUM>-<NUM> may indicate that the <NUM> core network is to be selected as the appropriate core network over the <NUM> core network.

As indicated above and illustrated in <FIG>, the access control program <NUM>-<NUM> of embodiment <NUM> executes both the EPC access control program <NUM>-<NUM> and the <NUM> access control program <NUM>-<NUM>. The access control program <NUM>-<NUM> may perform the first access control procedure (e.g., EPC access control program <NUM>-<NUM>) using access control barring parameters, with the access control barring parameters being obtained from broadcasted system information obtained from the first core network (as described in embodiment <NUM>). The access control program <NUM>-<NUM> perform the second access control procedure (e.g., <NUM> access control program <NUM>-<NUM>) using access control information included in broadcasted system information and an access category number, with the access category number being dependent upon both a type of access attempt and a condition related to the wireless terminal (as described in embodiment <NUM>).

It should be noted that the procedure illustrated in <FIG> may be implemented in a different manner but logically equivalent. Specifically, upon arrival of an access attempt <NUM>-<NUM>-<NUM>, a first access control procedure (one of the access control procedures, act <NUM>-<NUM>-<NUM> or act <NUM>-<NUM>-<NUM>) may be selected and performed, and then if the decision is positive (not barred), the wireless terminal <NUM>-<NUM>-eLTE may proceed to initiating the access request to the core network corresponding the first access control procedure. The wireless terminal <NUM>-<NUM>-eLTE performs the second access control procedure (the access control procedure not selected for the first access control procedure) only if the first access control procedure results in a negative decision. If the second access control procedure results in a positive decision, the wireless terminal <NUM>-<NUM>-eLTE proceeds to initiating the access request to the core network corresponding the second access control procedure. Otherwise, the access attempt <NUM>-<NUM>-<NUM> is considered to be barred. In one configuration, the order of performing the access control procedures for multiple core networks may be pre-configured, or configured by eNB-<NUM> <NUM>-<NUM> transmitting (unicast or broadcast) a set of configuration parameters. In addition, in some configuration the wireless terminal <NUM>-<NUM>-eLTE may be pre-configured or configured by eNB-<NUM> <NUM>-<NUM> to use a subset of the access control procedures for making an access control decision. In this case, the access control decision may be made only by the access control procedure(s) in this subset.

<FIG> shows example, representative acts or steps performed by the wireless terminal <NUM>-<NUM>-eLTE in an example embodiment and mode. Act <NUM>-<NUM> comprises performing a first access control procedure configured for a first core network and to obtain therefrom a first access control decision. See, for example, act <NUM>-<NUM>-<NUM> of <FIG>. Act <NUM>-<NUM> comprises performing a second access control procedure configured for a second core network and to obtain therefrom a second access control decision. See, for example, act <NUM>-<NUM>-<NUM> of <FIG>. Act <NUM>-<NUM> comprises making an aggregated access control decision dependent at least in part on the first access control decision and the second access control decision, See, for example, act <NUM>-<NUM>-<NUM> of <FIG>. The aggregated access control decision determines an appropriate one of the first core network and the second core network. Act <NUM>-<NUM> through act <NUM>-<NUM> may be performed by the processor circuitry of wireless terminal <NUM>-<NUM>-eLTE, e.g., by access controller <NUM>-<NUM>. Act <NUM>-<NUM> comprises transmitting, over a radio interface, an access request to the appropriate core network. The representative acts or steps of <FIG> are described as being performed by the wireless terminal <NUM>-<NUM>-eLTE, but it should be understood that these basic acts or steps may be performed by any wireless terminal which is making an access control decision when any two or more core networks are involved. That is, the acts of <FIG> may be performed in conjunction with an access control decision between any two core networks, not just between LTE and <NUM> core networks.

Features of any one or more of the example embodiments and modes described herein may be combined with any other example embodiment(s) and mode(s) described herein.

Certain units and functionalities of access node <NUM> and wireless terminal <NUM> of the various foregoing example embodiments and modes are, in example embodiments, implemented by electronic machinery, computer, and/or circuitry. For example, the node processors <NUM> and terminal processors <NUM> of the example embodiments herein described and/or encompassed may be comprised by the computer circuitry of <FIG> shows an example of such electronic machinery or circuitry, whether node or terminal, as comprising one or more processor(s) circuits <NUM>, program instruction memory <NUM>; other memory <NUM> (e.g., RAM, cache, etc.); input/output interfaces <NUM>; peripheral interfaces <NUM>; support circuits <NUM>; and busses <NUM> for communication between the aforementioned units.

The program instruction memory <NUM> may comprise coded instructions which, when executed by the processor(s), perform acts including but not limited to those described herein. Thus is understood that each of node processor <NUM> and terminal processor <NUM>, for example, comprise memory in which non-transient instructions are stored for execution.

The memory <NUM>, or computer-readable medium, may be one or more of readily available memory such as random access memory (RAM), read only memory (ROM), floppy disk, hard disk, flash memory or any other form of digital storage, local or remote, and is preferably of non-volatile nature. The support circuits <NUM> are coupled to the processors <NUM> for supporting the processor in a conventional manner. These circuits include cache, power supplies, clock circuits, input/output circuitry and subsystems, and the like.

Although the processes and methods of the disclosed embodiments may be discussed as being implemented as a software routine, some of the method steps that are disclosed therein may be performed in hardware as well as by a processor running software. As such, the embodiments may be implemented in software as executed upon a computer system, in hardware as an application specific integrated circuit or other type of hardware implementation, or a combination of software and hardware. The software routines of the disclosed embodiments are capable of being executed on any computer operating system, and is capable of being performed using any CPU architecture. The instructions of such software are stored on non-transient computer readable media.

The functions of the various elements including functional blocks, including but not limited to those labeled or described as "computer", "processor" or "controller", may be provided through the use of hardware such as circuit hardware and/or hardware capable of executing software in the form of coded instructions stored on computer readable medium. Thus, such functions and illustrated functional blocks are to be understood as being either hardware-implemented and/or computer-implemented, and thus machine-implemented.

In terms of hardware implementation, the functional blocks may include or encompass, without limitation, digital signal processor (DSP) hardware, reduced instruction set processor, hardware (e.g., digital or analog) circuitry including but not limited to application specific integrated circuit(s) [ASIC], and/or field programmable gate array(s) (FPGA(s)), and (where appropriate) state machines capable of performing such functions.

In terms of computer implementation, a computer is generally understood to comprise one or more processors or one or more controllers, and the terms computer and processor and controller may be employed interchangeably herein. When provided by a computer or processor or controller, the functions may be provided by a single dedicated computer or processor or controller, by a single shared computer or processor or controller, or by a plurality of individual computers or processors or controllers, some of which may be shared or distributed. Moreover, use of the term "processor" or "controller" shall also be construed to refer to other hardware capable of performing such functions and/or executing software, such as the example hardware recited above.

Moreover, the technology can additionally be considered to be embodied entirely within any form of computer-readable memory, such as solid-state memory, magnetic disk, or optical disk containing an appropriate set of computer instructions that would cause a processor to carry out the techniques described herein.

It will be appreciated that the technology disclosed herein is directed to solving radio communications-centric issues and is necessarily rooted in computer technology and overcomes problems specifically arising in radio communications. Moreover, in at least one of its aspects the technology disclosed herein improves the functioning of the basic function of a wireless terminal and/or node itself so that, for example, the wireless terminal and/or node can operate more effectively by prudent use of radio resources.

Claim 1:
A wireless terminal (<NUM>) comprising:
receiver unit (<NUM>) configured to receive from an access node (<NUM>) first access control information and to separately receive from the access node (<NUM>) second access control information, the first access control information comprising first access barring information for a first core network, the second access control information comprising second access barring information for a second core network;
processor unit (<NUM>) configured to:
generate an access attempt;
perform, based on the first access barring information, a first access control procedure to determine whether the access attempt is allowed or barred for the first core network, and to
perform, based on the second access barring information, a second access control procedure to determine whether the access attempt is allowed or barred for the second core network; and
transmitter unit (<NUM>) configured to transmit
an access request for the first core network, in case that the access attempt is allowed by the first access control procedure and,
an access request for the second core network, in case that the access attempt is barred by the first access control procedure but the access attempt is allowed by the second access control procedure.