WO2019173124A1 - Apparatus and method for communication regarding selection of radio access technology - Google Patents

Abstract

A wireless terminal comprises processor circuitry and communications circuitry. The processor circuitry is configured to process for communication, with a core network on a non-access stratum level, selectivity information regarding selectivity of one or more radio access technologies for use by the wireless terminal. The communications circuitry is configured to communicate the selectivity information between the core network and the wireless terminal.

Description

APPARATUS AND METHOD FOR COMMUNICATION REGARDING SELECTION OF RADIO ACCESS

TECHNOLOGY

This application claims the priority and benefit of US provisional application

62/640,482, filed March 8, 2018, entitled“APPARATUS AND METHOD FOR

COMMUNICATION REGARDING SELECTION OF RADIO ACCESS TECHNOLOGY” which is incorporated by reference herein in its entirety.

TECHNICAL FIELD

[0001] The technology relates to wireless communications, and particularly to methods and apparatus for communicating the selectivity, and controlling the selectivity, of radio access technologies.

BACKGROUND

[0002] 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). The access node, in addition to being called a base station, in later radio access technologies (RATs), may also be referred to as an evolved NodeB (“eNB") or a gNB (for, e.g., New Radio [NR] technology).

[0003] 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 earlier radio access technologies (RATs) such as Global System for Mobile Communication (GSM) and Universal Mobile Telecommunications System (“UMTS”) in a manner to cope with future requirements.

[0004] A core network is a central part of a telecommunications network that provides various services to customers, e.g., wireless terminals, who are connected by an access network, such as a radio access network. . A core network may provide services such as call authentication, call control and switching, charging (invoicing), and service invocation. A particular radio access technology (RAT) may be associated with a corresponding particular core network. For example, General Packet Radio Service (GPRS), which is a packet oriented mobile data service on the 2G and 3G cellular communication system's global system for mobile communications (GSM), may be associated with a GPRS core network. The GPRS core network is a central part of the GPRS which allows 2G, 3G and WCDMA mobile networks to transmit Internet Protocol (IP) packets to external networks such as the Internet. The GPRS system is an integrated part of the GSM network switching subsystem. The core network part of the LTE system is known as the Evolved Packet Core (EPC); the core network part of the 5G system is known as the 5GC.

[0005] A 3GPP Technical Specification Group on Service and System Aspects is known as“SA”. The TSG Service and System Aspects (TSG-SA) is responsible for the overall architecture and service capabilities of systems based on 3GPP specifications and, as such, has a responsibility for cross TSG co-ordination. The SA includes subgroups on different topics, such as SA1 : Services; SA2: Architecture; SA3: Security; SA4: Codec; SA5: Telecom

Management; and, SA6: Mission-critical Applications.

[0006] SA1 is currently working to specify a configuration option on the UE that would selectively disable access technologies. The issue was triggered by a Liaison Statement (LS), i.e., S1-173278, from SA3 to SA1 that requested SA1 to specify a configuration option on the

UE that would selectively disable legacy access technologies. The intent of SA3 is to provide an option of a more secure wireless environment as the user needs it, while still being flexible to use legacy technologies if needed. There is also a mirror requirement that the home operator can disallow selection of one or more of the Mobile Equipment’s (ME’s) radio technologies for access to a radio access network, regardless of Public Land Mobile Networks (PLMNs).

[0007] As a means to capture the requirements, SA1 looks to revise the text in 3GPP TS 22.011 V16.0.0 (2017-12),“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service accessibility (Release 16)”, incorporated by reference herein, with the following potential text: 7.3 UE configured radio technology restriction

A UE shall support a Man Machine Interface setting for the user to disable use of one or more of the ME's radio technologies for access to a radio access network, regardless of PLMNs. Radio technologies that individually can be disabled is dependent on supported radio technology of the UE such as GSM/EDGE, WCDMA, LTE, and NR.

A UE shall support a Man Machine Interface setting enabling the user to re-enable use of one or more of the ME's radio technologies for access to a radio access network, regardless of PLMNs. The user can only re-allow a radio technology that the user has previously dis-allowed.

NOTE: The described MMI user setting is a proprietary function of most legacy UE products to allow a user of a UE to change the radio capabilities of the UE. Legacy radio technologies may lack means to mitigate some security attack. If severe enough, the home operator may want to disallow their subscribers to access a radio access network with such radio technology. This configuration of the UE is valid for all PLMNs.

A UE shall support a secure mechanism for the home operator to disallow selection of one or more of the ME's radio technologies for access to a radio access network, regardless of PLMNs. Radio technologies that individually can be disallowed are at least GSM/EDGE, WCDMA, LTE, and NR.

A UE shall support a secure mechanism for the home operator to re-allow selection of one or more of the ME's radio technologies for access to a radio access network, regardless of PLMNs. Radio technologies that individually can be re-allowed are at least GSM/EDGE, WCDMA, LTE, and NR. The home operator can only re-allow a radio technology that the home operator has previously dis-allowed.

For a prioritized service (e.g., Emergency Services, MPS, Mission Critical Services), the UE shall support a mechanism to automatically override user and network disallowed RATs when there are no PLMNs on the allowed radio technologies identified that the UE is able to access. Upon power-cycle or when the USIM is disabled, the UE configuration of enabled/disabled radio technologies configured by the user shall remain as it was before such events happen. The radio technologies disallowed by the HPLMN shall remain as it was before a power cycle. The radio technologies disallowed by the HPLMN shall be bound to the USIM.

[0008] Provision of an interface for enabling a user to disable use of one or more of the ME’s radio technologies for access to a radio access network causes one or more problems, some examples of which are described below. [0009] A first problem is that the core network, whether the GPRS Core Network, the

EPC, or the 5GC may waste system resources and be inefficient by, for example, trying to perform activities for a radio access technology (RAT) which has been disabled by the user of the wireless terminal. For example, the core network may try to page a UE on a RAT that has been disabled by the user of the wireless terminal. [00010] A second problem is that, in some situations, an operator, e.g., of a core network, may select a configuration for a wireless terminal that governs or controls what radio access technologies the wireless terminal may use, and thus which radio access technologies the wireless terminal may select or de-select/disable. As used herein, a“Configuration” represents how the User or Operator has set enabled/disabled state for all of the radio access technologies. A“state” represents the enabled/disabled setting of an individual radio access technology (RAT). Without knowledge of the operator’s configuration for a wireless terminal, which governs the wireless terminal’s ability to select or disable radio access technologies, the wireless terminal may waste resources and be inefficient by, for example, performing ineffective activities such as trying to attach to a radio access technology (RAT) that the network operator has disabled for the wireless terminal.

[00011] What is needed, therefore, and an example object of the technology disclosed herein, are methods, apparatus, and techniques for a wireless terminal and a core network communicating with regard to selectable use of radio access technologies. SUMMARY

[00012] In one of its many example aspects the technology disclosed herein concerns a wireless terminal that comprises processor circuitry and communications circuitry. The processor circuitry is configured to process for communication, with a core network on a non- access stratum level, selectivity information regarding selectivity of one or more radio access technologies for use by the wireless terminal. As used herein,“selectivity” encompasses information about a user’s selection of one or more radio access technologies, as well as information regarding eligibility, e.g., selectability, of one or more radio access technologies, e.g., whether the particular radio access technologies are permitted to be included in a list of radio access technologies for which the user may make a selection. The communications circuitry is configured to communicate the selectivity information between the core network and the wireless terminal.

[00013] In another of its example aspects the technology disclosed herein concerns a method in a wireless terminal. In a basic mode the method comprises using processor circuitry to process for communication, with a core network on a non-access stratum level, selectivity information regarding selectivity of one or more radio access technologies for use by the wireless terminal; and communicating the selectivity information between the wireless terminal and the core network.

[00014] In another of its example aspects the technology disclosed herein concerns a core network node comprising processor circuitry and interface circuitry. The processor circuitry is configured to process for communication, with a core network on a non-access stratum level, selectivity information regarding selectivity of one or more radio access technologies for use by the wireless terminal. The interface circuitry configured to communicate the selectivity information between the core network and the wireless terminal. [00015] In another of its example aspects the technology disclosed herein concerns a method in core network node. In a basic aspect the method comprises using processor circuitry to process for communication, with a wireless terminal on a non-access stratum level, selectivity information regarding selectivity of one or more radio access technologies for use by the wireless terminal, and communicating the selectivity information between the core network and the wireless terminal.

BRIEF DESCRIPTION OF THE DRAWINGS

[00016] 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. [00017] Fig. 1 is a diagrammatic view showing a generic architectural configuration of a radio communications system in which access control is implemented; Fig. 1-1 through Fig. 1- 5 are diagrammatic views showing architectural configurations of differing radio

communications systems according to different respective example embodiments and modes.

[00018] Fig. 2 is a schematic view of a generic radio communications system comprising a core network and a wireless terminal between which generic radio access technology selectivity information is communicated.

[00019] Fig. 2A is a schematic view of a radio communications system in which the selectivity information which is communicated between the wireless terminal and the core network comprises user selection information indicating of one or more radio access technologies selected or not selected by the user of the wireless terminal.

[00020] Fig. 2B is a schematic view of a radio communications system in which the selectivity information which is communicated between the wireless terminal and the core network comprises RAT selectability information indicating of one or more radio access technologies are permitted by the core network to be selected or not selected by the user of the wireless terminal. [00021] Fig. 3 is a flowchart showing basic, generic representative acts or steps performed by the wireless terminal of Fig. 2.

[00022] Fig. 4 is a flowchart showing basic, generic representative acts or steps performed by the core network of Fig. 2. [00023] Fig. 5 is a schematic view of a generic radio communications system in which selectivity information is between a core network and wireless terminal by inclusion in a RRC message.

[00024] Fig. 6A is a diagrammatic view of a format of the Device Properties IEI message as currently defined prior to the technology disclosed herein. [00025] Fig. 6B is a diagrammatic view of an example format of the Device Properties IEI message as proposed by the technology disclosed herein.

[00026] Fig. 7A is a flowchart showing example, representative, acts or steps comprising use and transport of the URECD information when a UE transitions from IDLE to

ATTACHED. [00027] Fig. 7B is a flowchart showing example, representative, acts or steps comprising use and transport of the URECD information when a user of a wireless terminal changes the UREDC configuration and the wireless terminal is in ATTACHED mode.

[00028] Fig. 8A is a diagrammatic view showing nesting of a user RAT enabled/disabled configuration (UREDC) message in one or more non-access stratum (NAS) messages, in a RRC message, and in a channel, when a wireless terminal transitions from idle mode to attached mode.

[00029] Fig. 8B is a diagrammatic view showing nesting of a user RAT enabled/disabled configuration (UREDC) message in one or more non-access stratum (NAS) messages, in a RRC message, and in a channel, when a user of a wireless terminal, in attached mode, changes the UREDC configuration.

[00030] Fig. 9A is a diagrammatic view of a format of the Network Policy IEI message as currently defined prior to the technology disclosed herein; Fig. 9B is a diagrammatic view of an example format of the Network Policy IEI message as proposed by the technology disclosed herein.

[00031] Fig. 10 is a flowchart showing basic, representative, example acts or steps that may be performed in an example embodiment and mode when home network operator makes a change to enable or disable any of the RATS that the home network operator has determined that the wireless terminal 26 may/may not use.

[00032] Fig. 11 is a diagrammatic view showing nesting of an operator RAT

enabled/disabled configuration (OREDC) message in one or more non-access stratum (NAS) messages, in a RRC message, and in a channel, when a network operator changes the OREDC configuration for a wireless terminal. [00033] Fig. 12 is a diagrammatic view showing example electronic machinery which may comprise node electronic machinery or terminal electronic machinery.

DETAILED DESCRIPTION

[00034] 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 that depart from these specific details. That is, those skilled in the art will be able to devise various arrangements which, although not explicitly described or shown herein, embody the principles of the technology disclosed herein and are included within its spirit and scope. 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. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future, i.e., any elements developed that perform the same function, regardless of structure. [00035] 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.

[00036] 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. [00037] 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.

[00038] 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 8, 9, 10, 11, and/or 12 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.

[00039] 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.

[00040] 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. [00041] As illustrated by the high level generic view of Fig. 1, a typical radio

communication system 20 comprises a core network 21; one or more radio access networks (RAN) 22 including one or more base stations or access nodes 23, and terminal devices used by the end users, represented by wireless terminal or UE 26.

[00042] The Core Network (CN) 21 includes the central part of the radio communication system that provides various services to customers who are connected by the radio access network 22. Example functions of a core network are discussed above. The core network for the Global System for Mobile Communication (GSM) is called the GSM Network Switching Subsystem or NS S or the GSM core network; the core network for the Universal Mobile Telecommunications System (UMTS) is a migration of that used for GSM with further elements overlaid to enable the additional functionality demanded by UMTS and is called the UTMS core network; the core network in the 4G network is called Evolved Packet Core (EPC), and the core network in the 5G network is referred as 5G Core Network (5GC). [00043] The Radio Access Network (RAN) 22 comprises, e.g., is a part of, a radio communication system that resides between terminal devices such as wireless terminal 26 and a core network 21. The RAN 22 provides connectivity to the devices through radio interfaces via the base station(s) or access node(s) 24, e.g., via eNB (in LTE/LTE-A RAN) or via gNB (in 5G RAN). The terminal devices 26 which are used by end users are also referred to as wireless terminals or User Equipment (UE).

[00044] While Fig. 1 shows a generic radio communications system 20, Fig. 1-1 through Fig. 1-5 show architectural configurations of differing example embodiments and modes of respective radio communications systems 20-1 through 20-5. Each radio communications system 20 comprises one or more core networks 21, a base station or access node 24, and one or more wireless terminals or UEs 26. For example, radio communications system 20-1 comprises core network 21-1, access node 24-1, and wireless terminal 26-1; radio

communications system 20-2 comprises core network 21-2, access node 24-2, and wireless terminal 26-2; and so forth. The example radio communications system 20-4 of Fig. 1-4 comprises two core networks, e.g., core network 21-4-EPC and core network 21-4-5GCN and two different types of wireless terminals, e.g., wireless terminal 26-4LTE and wireless terminal 26-4-eLTE. The example radio communications system 20-5 of Fig. 1-5 also comprises two core networks, e.g., core network 21-5-EPC and core network 21-5-5GCN.

[00045] As described above, in some situations a user of wireless terminal 26 may be able, through a user interface, to enter selectivity information regarding selectivity of one or more radio access technologies. That is, the user may be able to make a selection regarding one or more radio access technologies which the user desires for the wireless terminal 26 to be able to access. As used herein,“selection” encompasses both selection and de-selection. As such, using the user interface, the user of the wireless terminal 26 may either select one or more radio access technologies, de-select or not select one or more radio access technologies, or perform a combination of selection and de-selection/non-selection of various radio access technologies.

[00046] The technology disclosed herein comprises, in ones of its aspects, the

communication on a non-access stratum level, between a wireless terminal 26 and a core network 21, of selectivity information, e.g., information regarding user selectivity of one or more radio access technologies. As used herein,“selectivity” encompasses information about a user’s selection of one or more radio access technologies, e.g., an indication of what radio access technology(ies) are selected for use for the wireless terminal 26, or conversely not selected for use for the wireless terminal 26, by the user of the wireless terminal 26. In addition,“selectivity” encompasses information regarding eligibility, e.g., selectability, of one or more radio access technologies, e.g., whether the particular radio access technologies are permitted by the core network 21 to be included in a list of radio access technologies for which the user may make a selection.

[00047] In one of its example embodiments and modes, hereinafter illustrated by way of example with reference to Fig. 2A, the technology disclosed herein comprises the wireless terminal 26, and particularly processor circuitry of the wireless terminal 26, being configured to generate a RAT selection message, to send to core network 21 on a non-access stratum level. The RAT selection message, being based on user RAT enabled/disabled configuration

(UREDC) input, is also known as the user RAT enabled/disabled configuration (UREDC) message or UREDC message. The UREDC message includes the selectivity information regarding selectivity of one or more radio access technologies for use by the wireless terminal 26.

[00048] Moreover, in some example embodiments and modes, hereinafter illustrated by way of example with reference to Fig. 2B, the user’s choice of radio access technologies may be configured, e.g., limited or constrained, by the core network 21. Thus, as another aspect of the technology disclosed herein, the core network 21 is configured to generate and send to wireless terminal 26 a core network RAT selection configuration message, also known as an operator RAT enabled/disabled configuration (OREDC) message. The operator RAT enabled/disabled confirmation (OREDC) message advises the wireless terminal 26 of the core networks’ configuration for the wireless terminal 26 with respect to radio access technology (RAT) selection.

[00049] Thus both the user RAT enabled/disabled configuration (UREDC) message and the operator RAT enabled/disabled confirmation (OREDC) message include and are examples of selectivity information. The user RAT enabled/disabled configuration (UREDC) message, generated by the wireless terminal 26, includes selectivity information in the sense that the information included concerns what radio access technologies have been selected by the user of the wireless terminal 26, e.g., the user’s selection of one or more radio access technologies. The operator RAT enabled/disabled confirmation (OREDC) message, generated by the core network 21, includes selectivity information in the sense that the information included informs the wireless terminal 26 regarding which radio access technologies are selectable, e.g., which radio access technologies are eligible for selection by the user of the wireless terminal 26.

[00050] Fig. 2 shows a generic example embodiment and mode of a radio

communications system 20 in which selectivity information is communicated between the wireless terminal 26 and core network 21. The radio access network 22 is situated between core network 21 and wireless terminal 26. The radio access network 22 comprises access node 24 which communicates over air or radio interface 27 (e.g., Uu interface) with wireless terminal 26. The radio access node 24 may be any suitable node for communicating with the wireless terminal 26, such as a base station node, an eNodeB (“eNB”), or a gNB (for, e.g., New Radio [NR] technology), for example.

[00051] The core network node 28 of core network 21 may comprise one or more nodes of the core network 21, and may either be co-located or distributed at different locations (e.g., server locations) of core network 21. In an example embodiment and mode, core network node 28 comprises core network node processor 30, also known core network node processor circuitry or core node processor, as well as core network node communications interface (I/F) 32, also known as core network node communications circuitry 32. The core network node communications circuitry 32 may be connected over a core-RAN interface 33 to the radio access network 22, and to access node 24 in particular. When serving between the LTE radio access network and the evolved packet core, the interface 33 may be known as the Sl interface. The core network node communications circuitry 32 may comprise core node transmitter circuitry 34 and core node receiver circuitry 36, which are also called core node transmitter 34 and core node receiver 36, respectively.

[00052] The core network node processor 30 may provide many functionalities of the core network 21. Fig. 2 specifically shows core network node processor 30 as providing or comprising non-access stratum (NAS) entity 38 described herein.

[00053] The wireless terminal 26 comprises terminal processor circuitry 40 (“terminal processor 40”) and terminal communications circuitry 42. The terminal communications circuitry 42, which also is referred to as terminal transceiver circuitry, typically comprises terminal transmitter circuitry 44 and terminal receiver circuitry 46, which are also called terminal transmitter 44 and terminal receiver 46, respectively. The wireless terminal 26 also comprises user interface 48. The terminal user interface 48 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 48 may also include other types of devices, such as a speaker, a microphone, or a haptic feedback device, for example.

[00054] For both the radio access node 24 and radio interface 29, the respective transceiver circuitries 24 include antenna(s). The respective transmitter circuits 34 and 44 may comprise, e.g., amplifier(s), modulation circuitry and other conventional transmission equipment. The respective receiver circuits 36 and 46 may comprise, e.g., e.g., amplifiers, demodulation circuitry, and other conventional receiver equipment.

[00055] The wireless terminal 26 also comprises a storage device(s) and/or memory 54.

As explained herein with reference to Fig. 12, for example, the memory 54 may take the form of one or more 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 56. One or more applications executed by the terminal processor 40 of wireless terminal 26 in conjunction with services rendered by or using wireless terminal 26 may be stored in applications memory 58. Memory 54 includes a non- volatile memory section, in which is stored information that must survive power cycles (power being turned off). As such the non-volatile memory section may comprise many memory objects, including a memory object or data object URECD DO 59. As explained herein, the memory object URECD MO 59 represents a data object that captures the“Enabled/Disabled Configuration” for each of the RATS that the UE supports, as set by the user for the UE.

[00056] The wireless terminal 26 typically also comprises a universal subscriber identity module, such as a USIM card 60, which may take the form of a chip and contain both account information and memory, and can store subscriber information and authentication information, and provides storage space for text messages and phone book contacts. The USIM card 60 may be inserted into a slot on a circuit board of the wireless terminal 26.

[00057] The wireless terminal 26, which may also be called User Equipment (UE) is a device used by subscriber/access network services. To make its design modular, the wireless terminal 26 may be conceptualized as divided into logical parts, such as the Universals Subscriber Identity module (USIM card 60) and the Mobile Equipment (ME) 62. The Mobile Equipment (ME) 62 may further be divided into the Mobile Termination (MT) 64 and the Terminal Equipment (TE) 66. The Mobile Termination (MT) 64 performs functions such as radio transmission termination, authentication, and mobility management. The Terminal Equipment (TE) 66 manages the hardware, e.g. speaker, microphones, video cameras and user data, and hosts user applications, e.g., the applications in applications memory 58 and a web browser. The functions of Mobile Equipment (ME) 62, including the functions of Mobile Termination (MT) 64 and Terminal Equipment (TE) 66, may be performed by one or more processors comprising terminal processor 40.

[00058] The terminal processor 40 may also include or comprise both terminal non-access stratum (NAS) entity 68 and terminal radio resource control (RRC) entity 69, which may also respectively be referred to as NAS entity 68 and RRC entity 69. Fig. 2 reflects an example high- level structure of the UE protocol stack, wherein Non-Access Stratum (NAS) is a functional layer to communicate with the core network and radio resource control (RRC) is responsible for managing the radio resource/connection between the wireless terminal and the eNB. The terminal non-access stratum (NAS) entity 68 mat receive input from an upper layer, e.g., applications layer, such as one or more of the applications in applications memory 58. The terminal radio resource control (RRC) entity 69 may communicate with a lower layer over the interface 29.

[00059] In general operation, access node, 24 and wireless terminal 26 communicate with each other across radio interface 29, and communicate using predefined configurations of information. By way of non-limiting example, the radio access node 24 and wireless terminal 26 may communicate over radio interface 29 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). [00060] To cater to the transmission of information between radio access node 24 and wireless terminal 26 over radio interface 29, terminal processor 40 of Fig. 2 is shown as comprising terminal frame/signal handler 72. 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.

[00061] The user selectivity or a radio access technology may occur using a graphical or other type user interface through which the user of wireless terminal 26 may provide an indication of which radio access technologies are selected and/or not selected. Fig. 2 shows user interface 48 of wireless terminal 26 as including UREDC interface 74 through which a user of wireless terminal 26 may provide, e.g., may input, an indication of user selection of the one or more radio access technologies (RATs). The input of the user via UREDC interface 74 may define, alter, or modify the contents of the memory/data object URECD DO 59 in the non volatile section of memory 54. The UREDC interface 74 may function in conjunction with a UREDC application 76 included in the applications memory 58. The UREDC interface 74 may receive the input of a user selected or de-selected/not-selected radio access technology in any suitable manner, such as via keyboard, stylus or mouse click, touch screen, microphone, for example.

[00062] As mentioned above, the technology disclosed herein comprises, in ones of its aspects, the communication on a non-access stratum level, between a wireless terminal 26 and a core network 21, of selectivity information, e.g., information regarding user selectivity of one or more radio access technologies. Fig. 2 generically shows the communication of a “selectivity information” message between core network 21 and wireless terminal 26, and particularly between non-access stratum (NAS) entity 38 of core network 21 and terminal non- access stratum (NAS) entity 68 of wireless terminal 26.

[00063] In one of its example embodiments and modes, illustrated by way of example in Fig. 2A, the technology disclosed herein comprises the wireless terminal 26, and particularly processor circuitry of the wireless terminal 26, being configured to generate a RAT selection message, to send to core network 21 on a non-access stratum level. The RAT selection message, being based on user RAT enabled/disabled configuration (UREDC) input via UREDC interface 74 and stored in UREDC data object 59, is also known as the user RAT enabled/disabled configuration (UREDC) message or UREDC message. The UREDC message includes the selectivity information regarding selectivity of one or more radio access technologies for use by the wireless terminal 26. [00064] The terminal processor 40 of Fig. 2A comprises enabled/disabled configuration

(UREDC) message generator 80. The user RAT enabled/disabled configuration (UREDC) message generator 80 may comprise or be included in terminal non-access stratum (NAS) entity 68. The enabled/disabled configuration (UREDC) message generator 80 generates a non- access stratum message including the selectivity information (obtained from the user via UREDC interface 74). The user RAT enabled/disabled configuration (UREDC) message is generated by user RAT enabled/disabled configuration (UREDC) message generator 80 for transmission to the core network, e.g., to core network node 28. The selectivity information comprises the selection by the user of the wireless terminal of the one or more radio access technologies. As mentioned before, as used herein,“selection” of a radio access technology encompasses not only selection but also de-selection/non-selection of one or more radio access technologies. The core network node communications interface 32 transmits the user RAT enabled/disabled configuration (UREDC) message to the core network.

[00065] The non-access stratum (NAS) entity 38 of core network node 28 is shown in Fig. 2A as comprising UREDC message handler 82, also known as or UREDC message receiver 82. The UREDC message handler 82 is configured to process, e.g., de-format or decode, the URECD message, and thus to determine the content of the user RAT enabled/disabled configuration (UREDC) message and relay such content to the remainder of core network 21 via the non-access stratum (NAS) entity 38. The user RAT enabled/disabled configuration (UREDC) message is shown as“UREDC message” in Fig. 2A, and is shown as being generated from terminal non-access stratum (NAS) entity 68 and transmitted from wireless terminal 26 to the core network node 28 of core network 21 where it is processed by non- access stratum (NAS) entity 38.

[00066] In one of its example embodiments and modes, illustrated in by way of example in Fig. 2B, the technology disclosed herein comprises the core network 21, and particularly processor circuitry 30 of core network node 28, being configured to generate a RAT selectability message, to send to wireless terminal 26 on a non-access stratum level. In similar manner as the wireless terminal 26 having a UREDC data object 59 stored in non-volatile memory, so also the core network 21, e.g., core network node 28, has OREDC data object 84 stored in non-volatile memory. The RAT selectability message, being based on core network or operator RAT enabled/disabled configuration for the wireless terminal 26 as stored in the core network 21, e.g., OREDC data object 84, is also known as the operator RAT

enabled/disabled confirmation (OREDC) message, or the OREDC message. The OREDC message includes either a listing of which radio access technologies are eligible for selection by wireless terminal 26, or a listing of which radio access technologies are ineligible for selection by wireless terminal 26, or both listings. Fig. 2B shows that the operator RAT enabled/disabled confirmation (OREDC) message may be generated by OREDC message generator 86 of non-access stratum (NAS) entity 38 of core network node 28, and is received and/or processed by OREDC message handler 88 of the terminal non-access stratum (NAS) entity 68 of wireless terminal 26. The operator RAT enabled/disabled confirmation (OREDC) message is shown as“OREDC message” in Fig. 2B, and is shown as being generated from non-access stratum (NAS) entity 38 and transmitted from core network node 28 of core network 21 to wireless terminal 26 where it is processed by OREDC message handler 88 of terminal non-access stratum (NAS) entity 68. Information comprising the OREDC message as received by the CNRSC message handler 88 is also stored in a non-volatile portion of memory 54 and/or USIM card 60, so as to be available across power cycle.

[00067] The selectivity information message of Fig. 2 thus may be either the user RAT enabled/disabled configuration (UREDC) message shown in Fig. 2A, or the operator RAT enabled/disabled confirmation (OREDC) message of Fig. 2B. It should further be realized that the example embodiment and mode of Fig. 2B may be used in conjunction with the example embodiment and mode of Fig. 2A: that in an example embodiment and mode both the operator RAT enabled/disabled confirmation (OREDC) message and the user RAT enabled/disabled configuration (UREDC) message may be communicated between the wireless terminal 26 and the core network 21.

[00068] Fig. 3 shows basic, representative example acts or steps performed by the wireless terminal 26 of Fig. 2. Act 3-1 comprises using processor circuitry to process for

communication, with a core network on a non-access stratum level, selectivity information regarding selectivity of one or more radio access technologies for use by the wireless terminal. The processor circuitry utilized for performance of act 3-1 may be, for example, the terminal processor 40 which may include terminal non-access stratum (NAS) entity 68. In view of the generic nature of Fig. 2, using the processor circuitry to“process” the selectivity information may take the form of the processor circuitry generating the user RAT enabled/disabled configuration (UREDC) message in the manner of Fig. 2A, or of the processor circuitry handling the operator RAT enabled/disabled confirmation (OREDC) message in the manner of Fig. 2B. Act 3-2 comprises communicating the selectivity information between the wireless terminal and the core network. In view of the generic nature of Fig. 2,“communicating” the selectivity information may take the form of transmitting the user RAT enabled/disabled configuration (UREDC) message in the manner of Fig. 2A, or receiving the operator RAT enabled/disabled confirmation (OREDC) message in the manner of Fig. 2B.

[00069] Fig. 4 shows basic, representative example acts or steps performed by the core network 21 of Fig. 2, and by core network node 28 in particular. Act 4-1 comprises using processor circuitry to process for communication, with a wireless terminal on a non-access stratum level, selectivity information regarding selectivity of one or more radio access technologies for use by the wireless terminal. The processor circuitry utilized for performance of act 4-1 may be, for example, the core network node processor 30 which may include core node non-access stratum (NAS) entity 38. In view of the generic nature of Fig. 2, using processor circuitry to process for communication the selectivity information may take the form of the processor circuitry handling the user RAT enabled/disabled configuration (UREDC) message in the manner of Fig. 2A, or may take the form of the processor circuitry generating the operator RAT enabled/disabled confirmation (OREDC) message in the manner of Fig. 2B. Act 4-2 comprises the core network node 28 communicating the selectivity information between the core network (node) and the wireless terminal. In view of the generic nature of Fig. 2,“communicating” the selectivity information make take the form of receiving or handling the user RAT enabled/disabled configuration (UREDC) message in the manner of Fig. 2A, or take the form of generating the operator RAT enabled/disabled confirmation (OREDC) message in the manner of Fig. 2B.

[00070] Fig. 5 shows that, while the selectivity information is included in a non-access stratum (NAS) message, in an example embodiment and mode the non-access stratum (NAS) message may in turn be included in a radio resource control (RRC) message. The radio resource control (RRC) message may be transmitted between the radio access network and the wireless terminal on a dedicated control channel. In Fig. 5, the selectivity information message is depicted as an arrow labeled as“selectivity information”, and is shown as being transmitted between terminal non-access stratum (NAS) entity 68 and non-access stratum (NAS) entity 38. Fig. 5 further shows that the selectivity information message is included in a message labeled as“RRC message”, which is depicted as a hatched rectangle through which the arrow of the selectivity information message extends. The RRC message extends between the terminal radio resource control (RRC) entity 69 of wireless terminal 26 and node RRC entity 90 of the access node 24. Fig. 5 further shows the access node 24 as comprising node processor 92 and node transceiver 94. The node transceiver 94 may comprise receiver circuitry and transmitter circuitry in similar manner as above described for wireless terminal 26.

[00071] Which of the terminal radio resource control (RRC) entity 69 and the node RRC entity 90 generates the selectivity information, and which of the terminal radio resource control (RRC) entity 69 and the node RRC entity 90 receives/processes the selectivity information message, depends on the nature of the selectivity information. If the selectivity information message is a user RAT enabled/disabled configuration (UREDC) message, the terminal radio resource control (RRC) entity 69 generates the RRC message to include the user RAT enabled/disabled configuration (UREDC) message and to send the RRC message to the node RRC entity 90 of the access node 24. The access node 24 then forwards the user RAT enabled/disabled configuration (UREDC) message over interface 33 to core network node 28. On the other hand, if the selectivity information message is an operator RAT enabled/disabled confirmation (OREDC) message, the node RRC entity 90 generates the RRC message to include the operator RAT enabled/disabled confirmation (OREDC) message and sends same to the terminal radio resource control (RRC) entity 69 of the wireless terminal 26. The terminal radio resource control (RRC) entity 69 then forwards the operator RAT enabled/disabled confirmation (OREDC) message to the terminal non-access stratum (NAS) entity 68.

[00072] Thus, in one example aspect the technology disclosed herein informs a core network 21, e.g., one or more of the GPRS Core Network, the EPC and the 5GC, of the configuration that the user has selected for the wireless terminal 26 with respect to the enabling or disabling the RATS (e.g. GSM, UMTS, LTE, and NR) that the UE may support. A “Configuration” represents how the User or Operator has set enabled/disabled state for ALL of the RATS. The core network, such as the GPRS or the EPS or the 5GS, needs to know this UE configuration so as to not waste system resources, such as by trying to page a UE on a RAT that the user has disabled. [00073] As another example aspect, the wireless terminal 26 is informed of the configuration that the operator has selected with respect to the enabled or disabled RATS (e.g. GSM, UMTS, LTE, and NR) that the UE may use. By knowing the operator’s configuration, the wireless terminal advantageously need not waste system resources, such as by trying to attach to a RAT that the operator has disabled for the UE.

[00074] In others of its aspects, in example embodiments and modes the technology disclosed herein specifies example existing non-access stratum (NAS) messages, and bits within such non-access stratum (NAS) messages, that may be used to carry the selectivity information. [00075] As an example of usage of existing non-access stratum (NAS) messages, as a non-limiting implementation of the example embodiment and mode of Fig. 2A, the selectivity information in the form of the user RAT enabled/disabled configuration (UREDC) message may occupy or comprise three unused bits in the NAS message“Device Properties”

(TS24.008, section 10.5.7.8) that can be assigned as a bit map to represent the enabled/disabled state of three of the four potential RATS that the wireless terminal 26 may support: GSM,

UMTS, LTE, 5G. One of the four RATS is not represented in the bitmap, as that RAT is used to transport the Device Properties message, and thus by default is not disabled and therefor the CN can ascertain its state as enabled. As used herein, a“State” represents the enabled/disabled setting of an individual RAT. [00076] As another example of usage of existing non-access stratum (NAS) messages, as a non-limiting implementation of the example embodiment and mode of Fig. 2B, the selectivity information in the form of operator RAT enabled/disabled configuration (OREDC) message may occupy or comprise three unused bits in the NAS message“Network Policy” (TS24.301, section 9.9.3.52) that can be assigned as a bit map to represent the enabled/disabled configuration of three of the four potential RATS that the UE may support: GSM, UMTS,

LTE, 5G. One of the four RATS is not represented in the bitmap, as that RAT is used to transport the Device Properties message, and thus by default is not disabled and therefor the UE can ascertain its state as enabled. [00077] The terminology“Device Properties” NAS message and“Network Policy” NAS message are often used herein to represent an existing NAS message that may be utilized to carry or include the selectivity information. But such specific mention of“Device Properties” NAS message and“Network Policy” NAS message is not intended to be exhaustive or confining, since other NAS messages defined in 3GPP TS24.008 and 3GPP TS24.301 with three un-used bits could also be used. For example, other NAS messages with three un-used bits that could be used in this manner are as follows:

• MS Network feature support

• Auxiliary states

• Called party subaddress

• Calling party BCD number

• Connected number

• Connected subaddress

• Redirecting party BCD number

• TMSI status

• P-TMSI type

• User Plane integrity indicator

• Non-3GPP NW provided policies

• Quality of service

• Tear down indicator

• Device properties

• UE radio capability information update needed

• GUTI type

• Network policy

• ESM information transfer flag

• Control plane only indication

[00078] EXAMPLE IMPLEMENTATIONS OF THE UREDC MESSAGE

[00079] In some of its aspects the technology disclosed herein provides a means to inform the core networks (e.g., GPRS, EPS or 5GS) of the current state of the User RAT

Enabled/Disabled Configuration (UREDC data object, as set by the user on the UE, and stored in the UE’s non-volatile memory). The UREDC represents a data object that captures the “Enabled/Disabled Configuration” for each of the RATS that the wireless terminal 26 supports, as set by the user for the wireless terminal 26. Moreover, in an example, non-limiting implementation the technology disclosed herein uses three previously unused bits of the “Device Properties” IEI (see 3GPP TS 24.008.10.5.7.8) to transport the enabled/disabled states of three of the four RATs (as captured in the UREDC of the wireless terminal 26) to the core network, and how the enabled/disabled state of the fourth RAT (as captured in the

memory/data object URECD DO 59 of the wireless terminal ) is implied to the core network by the RAT used to transport the Device Properties IEI, i.e., the state of the fourth RAT must be enabled as it is used for transport.

[00080] The Device Properties IEI message is defined in 3GPP TS24.008 V15.1.0. One purpose of the Device Properties IEI message is to indicate if the MS (wireless terminal) is configured for NAS signaling low priority. The network uses the Device Properties information element for core-network congestion handling and for charging purposes. The Device Properties is a type 1 information element. The different formats and the four categories of information elements (type 1, 2, 3, and 4) are defined in 3GPP TS 24.007. The IEI of a standard IE consists of a half octet or one octet. A standard IE with IEI consisting of a half octet has format TV, and its value part consists of a half octet. The value of the IEI depends on the standard IE, not on its information element type. The format of the Device Properties IEI message as currently defined prior to the technology disclosed herein is shown in Fig. 6A.

[00081] As indicated above, in accordance with an example aspect of the technology disclosed herein, three previously unused bits in the NAS message“Device Properties” (3GPP TS24.008, section 10.5.7.8) may be assigned as a bit map to represent the enabled/disabled state of three of the four potential RATS that the UE may support: GSM, UMTS, LTE, 5G. One of the four RATS is not represented in the bitmap, as that RAT is used to transport the Device Properties message, and thus by default is not disabled and therefor the core network 21 can ascertain its state as enabled. The assignment of a RAT to a bit in the bitmap is dependent upon which RAT is used to transport the Device Properties message.

[00082] An example format of the Device Properties IEI message as proposed by the technology disclosed herein is shown in Fig. 6B. For example, if New Radio (NR), e.g., 5^th generation 5GCN, is used to transport the Device Properties message, then the first bit of the bitmap is assigned to represent the enable/disable state of GSM, and the second bit is assigned to UMTS and the third bit is assigned to LTE. If LTE is used to transport the Device Properties message, then the first bit of the bitmap is assigned to represent the enable/disable state of GSM, and the second bit is assigned to UMTS and the third bit is assigned to NR. If UMTS is used to transport the Device Properties message, then the first bit of the bitmap is assigned to represent the enable/disable state of GSM, and the second bit is assigned to LTE and the third bit is assigned to NR. If GSM is used to transport the Device Properties message, then the first bit of the bitmap is assigned to represent the enable/disable state of UMTS, and the second bit is assigned to LTE and the third bit is assigned to NR. It should be understood that the foregoing bitmap assignment schemes present exemplary configurations and does not limit other assigning schemes. For example, when NR is used to transport the Device Properties information element, the first bit of the bitmap may be LTE, the second may be UMTS and the third may be GSM.

[00083] The foregoing is thus a first example in which wherein a non-access stratum (NAS) message, such as the user RAT enabled/disabled configuration (UREDC) message, includes a bitmap comprising N-l bits, N being a number or radio access technologies potentially usable by the wireless terminal. Based on the particular radio access technology utilized for transmission of the non-access stratum (NAS) message, the N-l bits of the bitmap are in predetermined association with the N-l radio access technologies not used for transmission of the non-access stratum (NAS) message. In an example implementation, the N- 1 bits of the bitmap correspond in order to the following radio access technologies excepting the particular radio access technology utilized for transmission of the non-access stratum (NAS) message: Global System for Mobile Communication (GSM), Universal Mobile Telecommunications System (UMTS), 3GPP Long Term Evolution (LTE), and Fifth

Generation (5G). This example is just one way in which a UREDC bitmap may be expressed.

[00084] As indicated above, the wireless terminal 26 provides the user with an interface, such UREDC interface 74, by which the user may selectively enable or disable any one or more of the RATS that the UE supports. When the user changes the configuration of the enabled/disabled RATS (e.g., makes a change to enable or disable any of the RATS that the UE supports, as compared to the last saved configuration), the wireless terminal 26 may capture the updated configuration and save the configuration in static memory, e.g., in memory/data object URECD DO 59, such that the information is preserved across power cycles.

[00085] In one of its example aspects, the technology disclosed herein uses the selectivity information, such as the“Device Properties” IEI, to transport the UREDC information when the UE transitions from IDLE to ATTACHED. Fig. 7A shows example, representative, acts or steps comprising use and transport of the URECD information when the UE transitions from IDLE to ATTACHED. In particular, act 7A-1 comprises the wireless terminal 26 detecting or being informed of a need to transition from IDLE mode to ATTACHED mode, e.g., as part of the RACH procedure. As act 7A-2 the NAS layer of the wireless terminal 26, e.g., terminal non-access stratum (NAS) entity 68, accesses the current UREDC data object, as saved in static memory. As act 7A-3, the terminal non-access stratum (NAS) entity 68 provides to the RRC layer, e.g., to terminal radio resource control (RRC) entity 69, via a NAS layer message, a bitmap of the current UREDC. The NAS layer message carrying the UREDC bitmap may be the aforementioned Device Properties IEI, which is itself carried in one of several other NAS messages, such as ATTACH REQUEST or EXTENDED SERVICE REQUEST or SERVICE REQUEST or CONTROL PLANE SERVICE REQ message. The ATTACH REQUEST and EXTENDED SERVICE REQUEST and CONTROL PLANE SERVICE REQ messages are defined in 3GPP TS 24.301 and are used for EPS/5GS, while SERVICE REQUEST and ATTACH REQUEST are defined in 3 GPP TS 24.008 and are for GPRS). When the RRC layer prepares to send the RRCConnectionSetupComplete or RRCConnectionResumeComplete message (as part of the RACH procedure), the RRC will prepare its RRC message to include the DedicatedlnfoNAS message, and the DedicatedlnfoNAS message will carry the NAS message: ATTACH REQUEST or EXTENDED SERVICE REQUEST or SERVICE

REQUEST or CONTROL PLANE SERVICE REQ message. Thus, act 7A-4 shows the RRC entity generating an RRC message which ultimately includes the selectivity information, e.g., the UREDC-derived bitmap. As explained above, the selectivity information, e.g., the UREDC-derived bitmap may be nested in other NAS layer messages within the RRC message. Act 7A-5 comprises terminal radio resource control (RRC) entity 69 using the UL-DCCH- Message class to transport the RRCConnectionSetupComplete or

RRCConnectionResumeComplete, thus informing the GPRS or EPS/5GS of the current configuration of the wireless terminal respecting the enabled/disabled RATS when the UE has transitioned from IDLE to ATTACHED mode.

[00086] Fig. 8 A shows a non-limiting example of how the selectivity information may be included in other NAS messages and ultimately in an RRC message, with the RRC message being carried on an UL-DCCH channel. Fig. 8A shows the selectivity information as comprising three bits of a Device Properties IEI, which in turn is included in an ATTACH REQUEST non-access stratum (NAS) message, with the ATTACH REQUEST in turn being included in a DedicatedlnfoNAS message, which in turn is included in

RRCConnectionSetupComplete (RRC) message, with the RRCConnectionSetupComplete message being transported on an uplink dedicated control channel (UL DCCH).

[00087] Table 1 below describes the ATTACH REQUEST message, which is defined in 3 GPP TS24.008 V15.1.0 and in 3GPP TS 24.301 V15.1.1. The ATTACH REQUEST message is sent by the wireless terminal 26 to the network in order to perform an attach procedure. The ATTACH Request message carries, as an optional Information Element, the Device Properties IEI.

[00088] Table 1 : ATTACH REQUEST MESSAGE

IEI Information Element Type/Reference Presence Format

Length

Protocol discriminator Protocol discriminator M V ½ Security header type Security header type M V ½ Attach request message identity Message type M V 1 EPS attach type EPS attach type M V ½ NAS key set identifier NAS key set identifier M V ½ EPS mobile identity EPS mobile identity M LV 5-12 UE network capability UE network capability M LV 3-14 ESM message container ESM message container M LV-E 5-n 19 Old P-TMSI signature P-TMSI signature O TV 4

50 Additional GUTI EPS mobile identity O TLV 13

52 Last visited registered TAI Tracking area identity O TV 6

5C DRX parameter DRX parameter O TV 3

31 MS network capability MS network capability O TLV 4-10 13 Old location area identification Location area identification O TV 6 9- TMSI status TMSI status O TV 1

11 Mobile station classmark 2 Mobile station classmark 2 O TLV 5

20 Mobile station classmark 3 Mobile station classmark 3 O TLV 2-34

40 Supported Codecs Supported Codec List O TLV 5-n

F- Additional update type Additional update type O TV 1

5D Voice domain preference Voice domain preference O TLV 3 and UE's usage setting and UE's usage setting

D- Device properties Device properties O TV 1

E- Old GUTI type GUTI type O TV 1

C- MS network feature support MS network feature support O TV 1

10 TMSI based NRI container Network resource identifier container O TLV 4

6A T3324 value GPRS timer 2 O TLV 3

5E T3412 extended value GPRS timer 3 O TLV 3

6E Extended DRX parameters Extended DRX parameters O TLV 3

6F UE additional security capability UE additional security capability O TLV 8

[00089] Table 2 below describes the DedicatedlnfoNAS message, which is defined in 3GPP TS36.331 V15.1.0. A purpose of the IE DedicatedlnfoNAS is to transfer UE-specific NAS layer information, such as the ATTACH REQUEST message, between the network and the UE. The RRC layer is transparent for this information. A UE in RRC CONNECTED initiates the UL information transfer procedure whenever there is a need to transfer NAS or non-3GPP dedicated information, except at RRC connection establishment or resume in which case the NAS information is piggybacked to the RRCConnectionSetupComplete or

RRCConnectionResumeComplete message correspondingly. The UE initiates the UL information transfer procedure by sending the ULInformationTransfer message.

[00090] Table 2: DedicatedlnfoNAS MESSAGE

[00091] Table 3 below describes the RRCConnectionSetupComplete IE message. The RRCConnectionSetupComplete IE message is defined in TS36.3318 V15.1.0. The RRCConnectionSetupComplete message is used to confirm the successful completion of an RRC connection establishment. Signalling radio bearer SRB1 is used. Logical channel DCCH is used. The RRCConnectionSetupComplete message is used to carry the DedicatedlnfoNAS IE message. [00092] TABLE 3: RRCConnectionSetupComplete IE message

[00093] Table 4 below describes the UL-DCCH-Message. The UL-DCCH-Message is defined in TS36.3318 V15.1.0. The UL-DCCH-Message class is the set of RRC messages that may be sent from the UE to the E-UTRAN or from the RN to the E-UTRAN on the uplink DCCH logical channel. The UL-DCCH-Message message is used to carry the

RRCConnectionSetupComplete IE, the RRCConnectionResumeComplete IE and the

ULInformationTransfer IE. [00094] TABLE 4: the UL-DCCH-Message

[00095] In another of its example aspects the technology disclosed herein describes how the “Device Properties” IEI is used to transport the UREDC information when the user changes the UREDC configuration and the wireless terminal 26 is in ATTACHED mode. Fig. 7B shows basic, example, representative acts of steps comprising use and transport of the URECD information when the user changes the UREDC configuration and the wireless terminal 26 is in ATTACHED mode. Act 7B-1 comprises making a determination that, when the wireless terminal 26 is in ATTACHED mode, the user has changed the UREDC (e.g., via UREDC interface 74). As a result of the determination of the change, the NAS layer, e.g., terminal non- access stratum (NAS) entity 68, of the wireless terminal 26 may access the current UREDC data object, e.g., memory/data object URECD DO 59, as saved in static memory. As act 7B-3 the terminal non-access stratum (NAS) entity 68 provides to the RRC layer, e.g., to terminal radio resource control (RRC) entity 69, a bitmap of the current UREDC in a non-access stratum (NAS) message. The NAS layer message carrying the UREDC bitmap may be the Device Properties IEI, which is itself carried in one of several other NAS message: ATTACH REQUEST or EXTENDED SERVICE REQUEST or SERVICE REQUEST or CONTROL PLANE SERVICE REQ message. The ATTACH REQUEST and EXTENDED SERVICE REQUEST and CONTROL PLANCE SERVICE REQ are defined in 3GPP TS 24.301 and are used for EPS/5GS, while SERVICE REQUEST and ATTACH REQUEST are defined in 3 GPP TS 24.008 and are for GPRS. As act 7B-4 the terminal radio resource control (RRC) entity 69 generates an RRC message which ultimately includes the UREDC-derived bitmap. Such RRC message may be, for example, an ULInformationTransfer message. When the RRC layer prepares to send the ULInformationTransfer message (A UE in RRC CONNECTED initiates the UL information transfer procedure whenever there is a need to transfer NAS or non-3GPP dedicated information), the RRC may include in its RRC message the DedicatedlnfoNAS message, and the DedicatedlnfoNAS message will carry the NAS message: SERVICE REQUEST or EXTENDED SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST message. As act 7B-5, the terminal radio resource control (RRC) entity 69 may use the UL-DCCH-Message class to transport the ULInformationTransfer message, thus informing the GPRS or EPS/5GS of the current configuration for the wireless terminal 26 of the enabled/disabled RATS when the new configuration for the wireless terminal 26 of the enabled/disabled RATS when the UE is in ATTACHED mode. [00096] Fig. 8B shows a non-limiting example of how the selectivity information may be included in other NAS messages and ultimately in an RRC message, with the RRC message being carried on an UL-DCCH channel. Fig. 8B shows the selectivity information as comprising three bits of a Device Properties IEI, which in turn is included in an ATTACH REQUEST non-access stratum (NAS) message, with the ATTACH REQUEST in turn being included in a DedicatedlnfoNAS message, which in turn is included in ULInformationTransfer message, with the ULInformationTransfer message being transported on an uplink dedicated control channel (UL DCCH).

[00097] EXAMPLE IMPLEMENTATIONS OF THE OREDC MESSAGE [00098] Thus in some of its aspects the technology disclosed herein provides a means to inform the wireless terminal 26 of current configuration for enabled/disabled RATS, also known as Operator RAT Enabled/Disabled Configuration (OREDC) or the OREDC data object 84, as set by the home operator, e.g., at the core network 21, for the wireless terminal 26. The OREDC data object 84 represents a data object that captures the“Enabled/Disabled

Configuration” for each of the RATS that the wireless terminal supports, as set by the user for the wireless terminal.

[00099] Moreover, in an example, non-limiting implementation the technology disclosed herein uses three previously unused bits of the“Network Policy” IEI (see 3GPP TS24.301, section 9.9.3.52) to transmit the selectivity information, and the operator RAT

enabled/disabled configuration (OREDC) message in particular. One purpose of the Network policy information element is to provide network policy information to the UE during attach or tracking area updating procedure via the ATTACH ACCEPT message or TRACKING AREA UPDATE ACCEPT message. The Network policy is a type 1 information element. The different formats and the four categories of information elements (type 1, 2, 3, and 4) are defined in 3GPP TS 24.007. A prior art format for the“Network Policy” IEI is shown in Fig. 9A. The IEI of a standard IE consists of a half octet or one octet. A standard IE with IEI consisting of a half octet has format TV, and its value part consists of a half octet. The value of the IEI depends on the standard IE, not on its information element type. [000100] In an example, non-limiting implementation the technology disclosed herein, three previously unused bits of the“Network Policy” IEI (see 3GPP TS24.301, section 9.9.3.52) are used to transport the enabled/disabled states of three of the four RATs (as captured in the OREDC) to the wireless terminal. The enabled/disabled state of the fourth RAT (as captured in the OREDC) is implied to the wireless terminal by the RAT used to transport the Network Properties IEI (i.e. the state of the fourth RAT must be enabled as it is used for transport). An example format of the Network Policy IEI message as proposed by the technology disclosed herein is shown in Fig. 9B. For example, the core network 21, e.g., OREDC message generator 86 , identifies three unused bits in the NAS message“Network Policy” (3GPP TS24.301, section 9.9.3.52) that can be assigned as a bit map to represent the enabled/disabled state of three of the four potential RATS that the UE may support: GSM, UMTS, LTE, 5G. One of the four RATS is not represented in the bitmap, as that RAT is used to transport the Network Policy message, and thus by default is not disabled and therefor the wireless terminal can ascertain its state as enabled. The assignment of a RAT to a bit in the bitmap is dependent upon which RAT is used to transport the Network Policy message. For example, if the 5th generation New Radio (NR) is used to transport the Network Policy message, then the first bit of the bitmap is assigned to represent the enable/disable state of GSM, and the second bit is assigned to UMTS and the third bit is assigned to LTE. If LTE is used to transport the Network Policy message, then the first bit of the bitmap is assigned to represent the enable/disable state of GSM, and the second bit is assigned to UMTS and the third bit is assigned to NR. If UMTS is used to transport the Network Policy message, then the first bit of the bitmap is assigned to represent the enable/disable state of GSM, and the second bit is assigned to LTE and the third bit is assigned to NR. If GSM is used to transport the Network Policy message, then the first bit of the bitmap is assigned to represent the enable/disable state of UMTS, and the second bit is assigned to LTE and the third bit is assigned to NR.

[000101] The foregoing including Fig. 9B is thus a second example in which wherein a non-access stratum (NAS) message, such as the operator RAT enabled/disabled configuration (OREDC) message, includes a bitmap comprising N-l bits, N being a number or radio access technologies potentially usable by the wireless terminal. Based on the particular radio access technology utilized for transmission of the non-access stratum (NAS) message, the N-l bits of the bitmap are in predetermined association with the N-l radio access technologies not used for transmission of the non-access stratum (NAS) message. In an example implementation, the N- 1 bits of the bitmap correspond in order to the following radio access technologies excepting the particular radio access technology utilized for transmission of the non-access stratum (NAS) message: Global System for Mobile Communication (GSM), Universal Mobile Telecommunications System (UMTS), 3GPP Long Term Evolution (LTE), and Fifth

Generation (5G). As mentioned above, the foregoing descriptions of the bitmap are merely for sake of example and not limiting other assigning schemes. For example, when NR is used to transport the Device Properties information element, the first bit of the bitmap may be LTE, the second may be UMTS and the third may be GSM. This example is just one way in which an OREDC bitmap may be expressed.

[000102] Fig. 10 shows operation of the core network 21 and wireless terminal 26 when a home network operator changes the configuration of the enabled/disabled RATS, e.g., makes a change to enable or disable any of the RATS that the home network operator has determined that the wireless terminal 26 may/may not use, as compared to the last home network operator configuration. Such a change by the home network operator affects the OREDC data object 84 maintained by the core network 21. Act 10-1 comprises detecting or being informed of a change to enable or disable any of the RATS that the home network operator has determined that the wireless terminal 26 may/may not use, e.g., a change in the in OREDC configuration. Upon detection of such change of act 10-1, as act 10-2 the core network will access the OREDC data object 84. As act 10-3 the core network will make a bitmap to reflect the OREDC data object 84, and the OREDC message generator 86 may provide the bitmap to the RRC layer in a non-access stratum (NAS) message. For example, the OREDC message generator 86 may provide the bitmap as an operator RAT enabled/disabled configuration (OREDC) message. For an example implementation, the OREDC message generator 86 may provide the bitmap as three bits of the Network Policy IE shown in Fig. 9B. The operator RAT enabled/disabled configuration (OREDC) message including the OREDC-derived bitmap is transmitted by the core network node 28 to the access node 24 of radio access network 22. As act 10-4 the node RRC entity 90 of access node 24 may generate an RRC message which includes the OREDC-derived bitmap, and transports the RRC message including the OREDC- derived bitmap to the wireless terminal 26 in a downlink dedicated control channel (DL- DCCH) to wireless terminal 26. As act 10-5, the wireless terminal 26, upon receipt of the RRC message with its included OREDC-derived bitmap, uses terminal radio resource control (RRC) entity 69 to process the RRC message, and uses terminal non-access stratum (NAS) entity 68 to process the included operator RAT enabled/disabled configuration (OREDC) message, to obtain the selectivity information in the form of the OREDC-derived bitmap, e.g., the operator RAT enabled/disabled configuration (OREDC) message. As act 10-6 the wireless terminal 26 saves the updated configuration obtained from the OREDC-derived bitmap, e.g., save the updated configuration in USIM card 60. In being saved in the USIM card 60, the updated configuration is preserved across UE power cycles. [000103] Upon saving of the updated configuration obtained from the OREDC-derived bitmap, as has occurred at act 10-6, the user of wireless terminal 26 is thereby constrained, when using the UREDC interface 74, to make a selection of radio access technologies only from among those permitted by the updated configuration obtained from the OREDC-derived bitmap which has been stored in the USIM card 60. [000104] As mentioned above, in one example implementation the technology disclosed may uses the“Network Policies” IEI to transport the OREDC information when the UE is ATTACHED to the network, in the manner shown, for example, by Fig. 9B.

[000105] As an example implementation of the foregoing, when the wireless terminal 26 transition from IDLE mode to ATTACHED mode (as part of the RACH procedure) and the home network operator wants to configure/revise the OREDC data in the UE, the network will provide to the RRC layer via a NAS layer message, a bitmap of the current OREDC data. The NAS layer message carrying the OREDC bitmap may be the Network Policy IEI, which is itself carried in one of the NAS messages: ATTACH ACCEPT or TRACKING AREA

UPDATE ACCEPT The ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT are defined in 24.301. When the RRC layer prepares to send the DLInformationTransfer message

(E-UTRAN initiates the DL information transfer procedure whenever there is a need to transfer NAS or non-3GPP dedicated information. E-UTRAN initiates the DL information transfer procedure by sending the DLInformationTransfer message), the RRC will include in its RRC message the DedicatedlnfoNAS message, and the DedicatedlnfoNAS message will carry the NAS message: ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT. The RRC will use the DL-DCCH-Message class to transport the DLInformationTransfer message, thus informing the UE of the operators current configuration of the enabled/disabled RATS when the UE has transitioned from IDLE to ATTACHED mode or of the operators new

configuration of the enabled/disabled RATS when the UE is in ATTACHED mode.

[000106] Fig. 11 shows non-limiting example of how the selectivity information may be included in other NAS messages and ultimately in an RRC message, with the RRC message being carried on a DL-DCCH channel. Fig. 11 shows the selectivity information as comprising three bits of a Network Policy IEI, which in turn is included in an ATTACH ACCEPT non- access stratum (NAS) message, with the ATTACH ACCEPT message in turn being included in a DedicatedlnfoNAS message, which in turn is included in a DLInformationTransfer (RRC) message, with the DLInformationTransfer message being transported on a downlink dedicated control channel (DL DCCH).

[000107] Table 5 below describes the ATTACH ACCEPT message. The ATTACH ACCEPT message is defined in 3 GPP TS 24.008 V15.1.0 and 3 GPP TS 24.301 V15.1.0. The ATTACH ACCEPT message is sent by the network to the wireless terminal 26 to indicate that the corresponding attach request has been accepted. The ATTACH ACCEPT message carries, as an optional information element, the Network Policy IEI.

[000108] Table 5: ATTACH ACCEPT message

[000109] Table 6 below describes the DedicatedlnfoNAS message. The

DedicatedlnfoNAS message is defined in 3GPP TS36.331 V15.1.0. One purpose of the IE DedicatedlnfoNAS is to transfer UE specific NAS layer information, such as the Attach Accept message, between the network and the UE. The RRC layer is transparent for this information. [000110] Table 6: DedicatedlnfoNAS message

[000111] Table 7 below describes the DLInformationTransfer message. The

DLInformationTransfer IE message is defined in 3GPP TS36.3318 V15.1.0. The

DLInformationTransfer message may be used for the downlink transfer of NAS or non-3GPP dedicated information. Signalling radio bearer: SRB2 or SRB1 (only if SRB2 not established yet. If SRB2 is suspended, E-UTRAN does not send this message until SRB2 is resumed.). The DLInformationTransfer message is used to carry the DedicatedlnfoNAS IE message.

[000112] Table 7: DLInformationTransfer message

[000113] Table 8 below describes the DL-DCCH-message. The DL-DCCH-Message is defined in 3 GPP TS36.3318 V15.1.0. The DL-DCCH -Message class is the set of RRC messages that may be sent from the E-UTRAN to the UE or from the E-UTRAN to the RN on the downlink DCCH logical channel. The DL-DCCH-Message message may be used to carry the dllnformationTransfer IE.

[000114] Table 8: DL-DCCH-message

[000115] The foregoing as described, among its many aspects, how existing non-access stratum (NAS) messages may be used to carry the selectivity information, such as the user RAT enabled/disabled configuration (UREDC ) message being carried by a Device Properties IEI and the operator RAT enabled/disabled configuration (OREDC) message being carried by the Network Policy IEI. It should be understood that, rather than using existing non-access stratum (NAS) messages, one or more completely new NAS protocol messages may be developed, and possibly eventually defined in 3 GPP TS 24.008 or other relevant document, to provide for the transport of the enabled/disabled state of the RATS that a UE may support (e.g. GSM, UMTS, LTE, NR). A revision of the Attach Request NAS message could be made to carry the new NAS protocol message. A revision of the Extended Service Request NAS message could be made to carry the new NAS protocol message.

[000116] Certain units and functionalities of the core network 21, including core network node 28, of access node 22 and of wireless terminal 26 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 30 and terminal processors 40 of the example embodiments herein described and/or encompassed may be comprised by the computer circuitry of Fig. 12. Fig. 12 shows an example of such electronic machinery or circuitry, whether node or terminal, as comprising one or more processor(s) circuits 191, program instruction memory 192; other memory 194 (e.g., RAM, cache, etc.); input/output interfaces 196; peripheral interfaces 198; support circuits 199; and busses 200 for

communication between the aforementioned units.

[000117] The program instruction memory 192 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 30 and terminal processor 40, for example, comprise memory in which non-transient instructions are stored for execution.

[000118] The memory 194, 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 199 are coupled to the processors 191 for supporting the processor in a conventional manner. These circuits include cache, power supplies, clock circuits, input/output circuitry and subsystems, and the like.

[000119] The technology of this application thus encompasses but is not limited to the following example embodiments, example features, and example advantages: [000120] Example Embodiment 1. A wireless terminal comprising: processor circuitry configured to process for communication, with a core network on a non-access stratum level, selectivity information regarding selectivity of one or more radio access technologies for use by the wireless terminal;

communications circuitry configured to communicate the selectivity information between the core network and the wireless terminal.

[000121] Example Embodiment 2. The wireless terminal of Example Embodiment 1, wherein the selectivity information is included in a non-access stratum (NAS) message, wherein the non-access stratum (NAS) message is in turn included in a radio resource control (RRC) message, and wherein the radio resource control (RRC) message is transmitted between the radio access network and the wireless terminal on a dedicated control channel.

[000122] Example Embodiment 3. The wireless terminal of Example Embodiment 1, wherein the selectivity information in included in a non-access stratum (NAS) message, and wherein the non-access stratum (NAS) message includes a bitmap comprising N-l bits, N being a number or radio access technologies potentially usable by the wireless terminal, and wherein, based on the particular radio access technology utilized for transmission of the non- access stratum (NAS) message, the N-l bits of the bitmap are in predetermined association with the N-l radio access technologies not used for transmission of the non-access stratum (NAS) message.

[000123] Example Embodiment 4. The wireless terminal of Example Embodiment 3, wherein the N-l bits of the bitmap correspond to the following radio access technologies excepting the particular radio access technology utilized for transmission of the non-access stratum (NAS) message: Global System for Mobile Communication (GSM), Universal Mobile Telecommunications System (UMTS), 3GPP Long Term Evolution (LTE), and Fifth

Generation (5G).

[000124] Example Embodiment 5. The wireless terminal of Example Embodiment 1, further comprising a user interface configured to obtain an indication of user selection of the one or more radio access technologies (RATs); wherein the processor circuitry is configured to generate a non-access stratum message including the selectivity information for transmission to the core network, wherein the selectivity information comprises the selection (including de selection) by the user of the wireless terminal of the one or more radio access technologies; and wherein the communications circuitry is configured to transmit the non-access stratum message to the core network.

[000125] Example Embodiment 6. The wireless terminal of Example Embodiment 5, wherein the selectivity information is included in a first non-access stratum (NAS) message; the first non-access stratum (NAS) message is included in a second non-access stratum (NAS) message, the second non-access stratum (NAS) message being one of the following:

ATTACH REQUEST;

EXTENDED SERVICE REQUEST;

SERVICE REQUEST;

CONTROL PLANE SERVICE REQUEST;

the second non-access stratum (NAS) message being included in a radio resource control (RRC) message, the radio resource control (RRC) message being one of the following:

RRCConnectionSetupComplete;

RRCConnectionResumeComplete;

ULInformationTransfer;

the radio resource control (RRC) message being transmitted over a radio interface on an uplink dedicated control channel (UL-DCCH).

[000126] Example Embodiment 7. The wireless terminal of Example Embodiment 6, wherein the selectivity information being included in the first non-access stratum (NAS) message comprises the selectivity information being included in a Device Properties

Information Element.

[000127] Example Embodiment 8. The wireless terminal of Example Embodiment 1, wherein the processor circuitry is configured to process a non-access stratum message received from the core network, the non-access stratum (NAS) message including the selectivity information for transmission, wherein the selectivity information comprises selectability by the user of the wireless terminal, as permitted by the core network, of the one or more radio access technologies in accordance with a core network configuration for the wireless terminal; and wherein the communications circuitry is configured to receive the non-access stratum message from the core network.

[000128] Example Embodiment 9. The wireless terminal of Example Embodiment 8, wherein the selectivity information is included in a first non-access stratum (NAS) message; the first non-access stratum (NAS) message is included in a second non-access stratum (NAS) message, the second non-access stratum (NAS) message being one of the following:

ATTACH ACCEPT;

TRACKING AREA UPDATE ACCEPT;

the second non-access stratum (NAS) message being included in a

DLInformationTransfer radio resource control (RRC) message,

the radio resource control (RRC) message being transmitted over a radio interface on a downlink dedicated control channel (DL-DCCH).

[000129] Example Embodiment 10. The wireless terminal of Example Embodiment 9, wherein the selectivity information being included in the first non-access stratum (NAS) message comprises the selectivity information being included in a Network Properties Information Element. [000130] Example Embodiment 11. A method in a wireless terminal comprising: using processor circuitry to process for communication, with a core network on a non- access stratum level, selectivity information regarding selectivity of one or more radio access technologies for use by the wireless terminal; communicating the selectivity information between the wireless terminal and the core network.

[000131] Example Embodiment 12. The method of Example Embodiment 11, further comprising: including the selectivity information in a non-access stratum (NAS) message; including the non-access stratum (NAS) message in a radio resource control (RRC) message, and transmitting the radio resource control (RRC) message between the core network and the wireless terminal on a dedicated control channel.

[000132] Example Embodiment 13. The method of Example Embodiment 11, further comprising: including the selectivity information in a non-access stratum (NAS) message, and including in the non-access stratum (NAS) message a bitmap comprising N-l bits, N being a number or radio access technologies potentially usable by the wireless terminal, and wherein, based on the particular radio access technology utilized for transmission of the non- access stratum (NAS) message, the N-l bits of the bitmap are in predetermined association with the N-l radio access technologies not used for transmission of the non-access stratum (NAS) message.

[000133] Example Embodiment 14. The method of Example Embodiment 13, further comprising configuring the non-access stratum (NAS) message whereby the N-l bits of the bitmap correspond to the following radio access technologies excepting the particular radio access technology utilized for transmission of the non-access stratum (NAS) message: Global System for Mobile Communication (GSM), Universal Mobile Telecommunications System (UMTS), 3GPP Long Term Evolution (LTE), and Fifth Generation (5G). [000134] Example Embodiment 15. The method of Example Embodiment 11, further comprising: obtaining, from a user interface, an indication of user selection of the one or more radio access technologies (RATs);

using the processor circuitry to generate a non-access stratum message including the selectivity information for transmission to the core network, wherein the selectivity information comprises the selection (including de-selection) by the user of the wireless terminal of the one or more radio access technologies; and

transmitting the non-access stratum message to the core network.

[000135] Example Embodiment 16. The method of Example Embodiment 15, further comprising: including the selectivity information in a first non-access stratum (NAS) message; including the first non-access stratum (NAS) message in a second non-access stratum (NAS) message, the second non-access stratum (NAS) message being one of the following:

ATTACH REQUEST;

EXTENDED SERVICE REQUEST;

SERVICE REQUEST;

CONTROL PLANE SERVICE REQUEST;

including the second non-access stratum (NAS) message being in a radio resource control (RRC) message, the radio resource control (RRC) message being one of the following:

RRCConnectionSetupComplete;

RRCConnectionResumeComplete;

ULInformationTransfer;

transmitting the radio resource control (RRC) message over a radio interface on an uplink dedicated control channel (UL-DCCH). [000136] Example Embodiment 17. The method of Example Embodiment 16, further comprising including the selectivity information in a Device Properties Information Element.

[000137] Example Embodiment 18. The method of Example Embodiment 11, further comprising using the processor circuitry to process a non-access stratum message received from the core network, the non-access stratum (NAS) message including the selectivity information for transmission, wherein the selectivity information comprises selectability by the user of the wireless terminal, as permitted by the core network, of the one or more radio access technologies in accordance with a core network configuration for the wireless terminal; and wherein the communications circuitry is configured to receive the non-access stratum message from the core network.

[000138] Example Embodiment 19. The method of Example Embodiment 18, further comprising: including the selectivity information in a first non-access stratum (NAS) message; including the first non-access stratum (NAS) message in a second non-access stratum (NAS) message, the second non-access stratum (NAS) message being one of the following:

ATTACH ACCEPT;

TRACKING AREA UPDATE ACCEPT;

including the second non-access stratum (NAS) message in a DLInformationTransfer radio resource control (RRC) message,

transmitting the radio resource control (RRC) message over a radio interface on a downlink dedicated control channel (DL-DCCH).

[000139] Example Embodiment 20. The method of Example Embodiment 19, further comprising including the selectivity information in a Network Properties Information Element.

[000140] Example Embodiment 21. A core network node comprising: processor circuitry configured to process for communication, with a core network on a non-access stratum level, selectivity information regarding selectivity of one or more radio access technologies for use by the wireless terminal; interface circuitry configured to communicate the selectivity information between the core network and the wireless terminal.

[000141] Example Embodiment 22. The core network node of Example Embodiment 21, wherein the selectivity information in included in a non-access stratum (NAS) message, and wherein the non-access stratum (NAS) message includes a bitmap comprising N-l bits, N being a number or radio access technologies potentially usable by the wireless terminal, and wherein, based on the particular radio access technology utilized for transmission of the non- access stratum (NAS) message, the N-l bits of the bitmap are in predetermined association with the N-l radio access technologies not used for transmission of the non-access stratum (NAS) message.

[000142] Example Embodiment 23. The core network node of Example Embodiment 22, wherein the N-l bits of the bitmap correspond in order to the following radio access technologies excepting the particular radio access technology utilized for transmission of the non-access stratum (NAS) message: Global System for Mobile Communication (GSM), Universal Mobile Telecommunications System (UMTS), 3GPP Long Term Evolution (LTE), and Fifth Generation (5G).

[000143] Example Embodiment 24. The core network node of Example Embodiment 21, wherein the processor circuitry is configured to handle a non-access stratum message including the selectivity information which has been transmitted to the core network, wherein the selectivity information comprises the selection (including de-selection), by the user of the wireless terminal, of the one or more radio access technologies; and wherein the interface circuitry is configured to receive the non-access stratum message.

[000144] Example Embodiment 25. The core network node of Example Embodiment 24, wherein the selectivity information is obtained from a Device Properties Information Element. [000145] Example Embodiment 26. The core network node of Example Embodiment 21, wherein the processor circuitry is configured to generate a non-access stratum message for use by the wireless terminal, the non-access stratum (NAS) message including the selectivity information for transmission, wherein the selectivity information comprises selectability by the user of the wireless terminal, as permitted by the core network, of the one or more radio access technologies in accordance with a core network configuration for the wireless terminal; and wherein the interface circuitry is configured to transmit the non-access stratum message from the core network. [000146] Example Embodiment 27. The core network node of Example Embodiment 26, wherein the selectivity information is included in a first non-access stratum (NAS) message.

[000147] Example Embodiment 28. The core network node of Example Embodiment 27, wherein the selectivity information is included in a Network Properties Information Element.

[000148] Example Embodiment 29. A method in core network node comprising: using processor circuitry to process for communication, with a wireless terminal on a non-access stratum level, selectivity information regarding selectivity of one or more radio access technologies for use by the wireless terminal;

communicating the selectivity information between the core network and the wireless terminal. [000149] Example Embodiment 30. The method of Example Embodiment 28, wherein the selectivity information is included in a non-access stratum (NAS) message.

[000150] Example Embodiment 32. The method of Example Embodiment 28, wherein the selectivity information in included in a non-access stratum (NAS) message, and wherein the non-access stratum (NAS) message includes a bitmap comprising N-l bits, N being a number or radio access technologies potentially usable by the wireless terminal, and wherein, based on the particular radio access technology utilized for transmission of the non-access stratum (NAS) message, the N-l bits of the bitmap are in predetermined association with the N-l radio access technologies not used for transmission of the non-access stratum (NAS) message.

[000151] Example Embodiment 33. The method of Example Embodiment 31, wherein the N-l bits of the bitmap correspond in order to the following radio access technologies excepting the particular radio access technology utilized for transmission of the non-access stratum (NAS) message: Global System for Mobile Communication (GSM), Universal Mobile Telecommunications System (UMTS), 3GPP Long Term Evolution (LTE), and Fifth

Generation (5G).

[000152] Example Embodiment 34. The method of Example Embodiment 28, wherein the processor circuitry is configured to handle a non-access stratum message including the selectivity information which has been transmitted to the core network, wherein the selectivity information comprises the selection (including de-selection), by the user of the wireless terminal, of the one or more radio access technologies; and wherein the interface circuitry is configured to receive the non-access stratum message. [000153] Example Embodiment 35. The method of Example Embodiment 33, wherein the selectivity information is obtained from a Device Properties Information Element.

[000154] Example Embodiment 36. The method of Example Embodiment 28, wherein the processor circuitry is configured to generate a non-access stratum message to send to the wireless terminal, the non-access stratum (NAS) message including the selectivity information, wherein the selectivity information comprises selectability by the user of the wireless terminal, as permitted by the core network, of the one or more radio access technologies in accordance with a core network configuration for the wireless terminal; and wherein the interface circuitry is configured to transmit the non-access stratum message from the core network.

[000155] Example Embodiment 37. The method of Example Embodiment 35, wherein the selectivity information is included in a Network Properties Information Element.

[000156] All 3 GPP TS documents mentioned herein are incorporated herein by reference in their entirety. The following are 3GPP documents having content that may be relevant to the technology disclosed herein, all of which are incorporated herein by reference in their entirety:

3GPP TS 36.331 V15.0.1 (2018-01), 3rd Generation Partnership Project; Technical

Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E- UTRA); Radio Resource Control (RRC); Protocol specification (Release 15)

3GPP TS 38.331 V15.0.0 (2017-12), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network NR Radio Resource Control (RRC) protocol specification (Release 15)

3GPP TS 24.008 V15.1.0 (2017-12) 3rd Generation Partnership Project; Technical

Specification Group Core Network and Terminals; Mobile radio interface Layer 3

Specification; Core network protocols; Stage 3(Release 15)

3GPP TS 24.007 V14.0.0 (2017-03) 3rd Generation Partnership Project; Technical

Specification Group Core Network and Terminals; Mobile radio interface signalling layer 3; General aspects (Release 14)

3GPP TS 24.301 V15.1.1 (2018-01) 3rd Generation Partnership Project; Technical

Specification Group Core Network and Terminals; Non- Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 (Release 15)

[000157] 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.

[000158] 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.

[000159] 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.

[000160] 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.

[000161] 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.

[000162] Nodes that communicate using the air interface also have suitable radio communications circuitry. 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.

[000163] 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 the core network so that, for example, upon user selection and de- selection of radio access technologies, the wireless terminal and/or core network can operate more effectively when attempting to operate in accordance with such selection/de-selection.

[000164] Although the description above contains many specificities, these should not be construed as limiting the scope of the technology disclosed herein but as merely providing illustrations of some of the presently preferred embodiments of the technology disclosed herein. Thus the scope of the technology disclosed herein should be determined by the appended claims and their legal equivalents. Therefore, it will be appreciated that the scope of the technology disclosed herein fully encompasses other embodiments which may become obvious to those skilled in the art, and that the scope of the technology disclosed herein is accordingly to be limited by nothing other than the appended claims, in which reference to an element in the singular is not intended to mean "one and only one" unless explicitly so stated, but rather "one or more." All structural, chemical, and functional equivalents to the elements of the above-described preferred embodiment that are known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the present claims. Moreover, it is not necessary for a device or method to address each and every problem sought to be solved by the technology disclosed herein, for it to be encompassed by the present claims. Furthermore, no element, component, or method step in the present disclosure is intended to be dedicated to the public regardless of whether the element, component, or method step is explicitly recited in the claims. No claim element herein is to be construed under the provisions of 35 U.S.C. 112, sixth paragraph, unless the element is expressly recited using the phrase "means for."

Claims

WHAT IS CLAIMED IS:

1. A wireless terminal comprising:

processor circuitry configured to process for communication, with a core network on a non-access stratum level, selectivity information regarding selectivity of one or more radio access technologies for use by the wireless terminal;

communications circuitry configured to communicate the selectivity information between the core network and the wireless terminal.

2. The wireless terminal of claim 1, wherein the selectivity information is included in a non-access stratum (NAS) message, wherein the non-access stratum (NAS) message is in turn included in a radio resource control (RRC) message, and wherein the radio resource control (RRC) message is transmitted between the radio access network and the wireless terminal on a dedicated control channel.

3. The wireless terminal of claim 1, wherein the selectivity information in included in a non-access stratum (NAS) message, and wherein the non-access stratum (NAS) message includes a bitmap comprising N-l bits, N being a number or radio access technologies potentially usable by the wireless terminal, and wherein, based on the particular radio access technology utilized for transmission of the non-access stratum (NAS) message, the N-l bits of the bitmap are in predetermined association with the N-l radio access technologies not used for transmission of the non-access stratum (NAS) message.

4. The wireless terminal of claim 1, further comprising a user interface configured to obtain an indication of user selection of the one or more radio access technologies (RATs); wherein the processor circuitry is configured to generate a non-access stratum message including the selectivity information for transmission to the core network, wherein the selectivity information comprises the selection (including de-selection) by the user of the wireless terminal of the one or more radio access technologies; and wherein the

communications circuitry is configured to transmit the non-access stratum message to the core network.

5. The wireless terminal of claim 1, wherein the processor circuitry is configured to process a non-access stratum message received from the core network, the non-access stratum (NAS) message including the selectivity information for transmission, wherein the selectivity information comprises selectability by the user of the wireless terminal, as permitted by the core network, of the one or more radio access technologies in accordance with a core network configuration for the wireless terminal; and wherein the communications circuitry is configured to receive the non-access stratum message from the core network.

6. A method in a wireless terminal comprising:

using processor circuitry to process for communication, with a core network on a non- access stratum level, selectivity information regarding selectivity of one or more radio access technologies for use by the wireless terminal;

communicating the selectivity information between the wireless terminal and the core network.

7. The method of claim 6, further comprising:

including the selectivity information in a non-access stratum (NAS) message;

including the non-access stratum (NAS) message in a radio resource control (RRC) message, and

transmitting the radio resource control (RRC) message between the core network and the wireless terminal on a dedicated control channel.

8. The method of claim 6, further comprising:

including the selectivity information in a non-access stratum (NAS) message, and including in the non-access stratum (NAS) message a bitmap comprising N-l bits, N being a number or radio access technologies potentially usable by the wireless terminal, and wherein, based on the particular radio access technology utilized for transmission of the non- access stratum (NAS) message, the N-l bits of the bitmap are in predetermined association with the N-l radio access technologies not used for transmission of the non-access stratum (NAS) message.

9. The method of claim 6, further comprising:

obtaining, from a user interface, an indication of user selection of the one or more radio access technologies (RATs);

using the processor circuitry to generate a non-access stratum message including the selectivity information for transmission to the core network, wherein the selectivity information comprises the selection (including de-selection) by the user of the wireless terminal of the one or more radio access technologies; and

transmitting the non-access stratum message to the core network.

10. The method of claim 6, further comprising using the processor circuitry to process a non-access stratum message received from the core network, the non-access stratum (NAS) message including the selectivity information for transmission, wherein the selectivity information comprises selectability by the user of the wireless terminal, as permitted by the core network, of the one or more radio access technologies in accordance with a core network configuration for the wireless terminal; and wherein the communications circuitry is configured to receive the non-access stratum message from the core network.

11. A core network node comprising:

processor circuitry configured to process for communication, with a core network on a non-access stratum level, selectivity information regarding selectivity of one or more radio access technologies for use by the wireless terminal;

interface circuitry configured to communicate the selectivity information between the core network and the wireless terminal.

12. The core network node of claim 11, wherein the selectivity information in included in a non-access stratum (NAS) message, and wherein the non-access stratum (NAS) message includes a bitmap comprising N-l bits, N being a number or radio access technologies potentially usable by the wireless terminal, and wherein, based on the particular radio access technology utilized for transmission of the non-access stratum (NAS) message, the N-l bits of the bitmap are in predetermined association with the N-l radio access technologies not used for transmission of the non-access stratum (NAS) message.

13. The core network node of claim 11, wherein the processor circuitry is configured to handle a non-access stratum message including the selectivity information which has been transmitted to the core network, wherein the selectivity information comprises the selection (including de-selection), by the user of the wireless terminal, of the one or more radio access technologies; and wherein the interface circuitry is configured to receive the non-access stratum message.

14. The core network node of claim 11, wherein the processor circuitry is configured to generate a non-access stratum message for use by the wireless terminal, the non-access stratum (NAS) message including the selectivity information for transmission, wherein the selectivity information comprises selectability by the user of the wireless terminal, as permitted by the core network, of the one or more radio access technologies in accordance with a core network configuration for the wireless terminal; and wherein the interface circuitry is configured to transmit the non-access stratum message from the core network.

15. A method in core network node comprising:

using processor circuitry to process for communication, with a wireless terminal on a non-access stratum level, selectivity information regarding selectivity of one or more radio access technologies for use by the wireless terminal;

communicating the selectivity information between the core network and the wireless terminal.

16. The method of claim 15, wherein the selectivity information is included in a non- access stratum (NAS) message.

17. The method of claim 15, wherein the selectivity information in included in a non- access stratum (NAS) message, and wherein the non-access stratum (NAS) message includes a bitmap comprising N-l bits, N being a number or radio access technologies potentially usable by the wireless terminal, and wherein, based on the particular radio access technology utilized for transmission of the non-access stratum (NAS) message, the N-l bits of the bitmap are in predetermined association with the N-l radio access technologies not used for transmission of the non-access stratum (NAS) message.

18. The method of claim 15, wherein the processor circuitry is configured to handle a non-access stratum message including the selectivity information which has been transmitted to the core network, wherein the selectivity information comprises the selection (including de selection), by the user of the wireless terminal, of the one or more radio access technologies; and wherein the interface circuitry is configured to receive the non-access stratum message.

19. The method of claim 15, wherein the processor circuitry is configured to generate a non-access stratum message to send to the wireless terminal, the non-access stratum (NAS) message including the selectivity information, wherein the selectivity information comprises selectability by the user of the wireless terminal, as permitted by the core network, of the one or more radio access technologies in accordance with a core network configuration for the wireless terminal; and wherein the interface circuitry is configured to transmit the non-access stratum message from the core network.