WIRELESS COMMUNICATIONS

Related Application

This application claims priority to U.S. Provisional Application Number

62/420,933, filed November 11, 2016, which is hereby incorporated by reference in its entirety.

Field

Embodiments of the present disclosure generally relate to the field of wireless communication networks, and more particularly, to apparatuses, systems, and methods associated with a cognitive decision engine that utilizes circumstance information.

Background

A user equipment (UE) may be able to communicate over multiple radio access technologies (RATs), such as a wireless cellular network, wireless local area network (e.g., Wi-Fi), Bluetooth, and/or other RATs. Additionally, within an RAT, the UE may be able to switch its connection between multiple base stations or access points, and/or otherwise change its configuration. Typically, the decision of the UE configuration is determined based on present network conditions.

Brief Description of the Drawings

Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings.

Figure 1 illustrates a wireless network environment according to some embodiments.

Figure 2 schematically illustrates a predictive configuration system in accordance with some embodiments.

Figure 3 illustrates propagation of a message including operational information between a Layer n and a Layer n-1 of a protocol stack, in accordance with some embodiments.

Figure 4 illustrates a protocol stack architecture for the predictive configuration system, in accordance with various embodiments.

Figure 5 illustrates an example operation flow/algorithmic structure of a communication device according to some embodiments. Figure 6 illustrates an example operation flow/algorithmic structure of a user equipment according to some embodiments.

Figure 7 illustrates an example operation flow/algorithmic structure of a communication device according to some embodiments.

Figure 8 illustrates a computer system according to some embodiments.

Detailed Description

In the following detailed description, reference is made to the accompanying drawings, which form a part hereof wherein like numerals designate like parts throughout, and in which is shown by way of illustration embodiments that may be practiced. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure.

Various operations may be described as multiple discrete actions or operations in turn, in a manner that is most helpful in understanding the claimed subject matter.

However, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations may not be performed in the order of presentation. Operations described may be performed in a different order than the described embodiment. Various additional operations may be performed or described operations may be omitted in additional embodiments.

For the purposes of the present disclosure, the phrases "A or B," "A and/or B," and "A/B" mean (A), (B), or (A and B).

The description may use the phrases "in an embodiment," or "in embodiments," which may each refer to one or more of the same or different embodiments. Furthermore, the terms "comprising," "including," "having," and the like, as used with respect to embodiments of the present disclosure, are synonymous.

As used herein, the term "circuitry" may refer to, be part of, or include any combination of integrated circuits (for example, a field-programmable gate array

("FPGA") an application specific integrated circuit ("ASIC"), etc.), discrete circuits, combinational logic circuits, system on a chip, SOC, system in a package, SiP, that provides the described functionality. In some embodiments, the circuitry may execute one or more software or firmware modules to provide the described functions. In some embodiments, circuitry may include logic, at least partially operable in hardware.

Figure 1 illustrates a wireless network environment 100. A user equipment (UE) 104 may be able to connect with one or more networks using different radio access technologies (RATs). The UE 104 may connect with an individual network via respective base stations or access points. For example, the wireless network environment may include a base station 108 (e.g., an evolved Node B (eNB) and/or next generation base station (gNB), including, but not limited to Pico/Femto/Micro/Macro eNBs, small cells, etc.) of a wireless cellular network (e.g., a wireless cellular network according to a Third Generation Partnership Protocol (3GPP) Standard, such as a Long Term Evolution (LTE) and/or LTE- Advanced network), a wireless local area network (WLAN) access point 112 of a WLAN (e.g., using Wi-Fi), and/or an access point 116 of another suitable RAT, such as Bluetooth, and/or device-to-device communication. In some embodiments, the wireless network environment 100 may include multiple base stations or access points available for a given RAT. The UE 104 may communicate with one or more of the base stations or access points at a given time. It will be apparent that the embodiments described herein may be used with any suitable RAT radio link protocols, such as one or more of the radio link protocols listed further below.

Additionally, while embodiments are described herein with reference to a UE, which is a term normally used for the mobile terminal in 3GPP cellular networks, it will be apparent that the embodiments are applicable to any mobile terminal that communicates over one or more wireless networks, even if the mobile terminal does not communicate over a 3GPP cellular network. Accordingly, the term UE as used herein encompasses any suitable type of mobile terminal.

Additionally, the UE 104 may be any suitable type of mobile terminal, such as a smartphone, a laptop, a desktop, a tablet, an IoT device such as a Smart Watch, health tracker, camera with wireless capabilities or another suitable type of user device.

Additionally, or alternatively, the UE 104 may be a vehicular communication component, for example in a car, truck, utility vehicle or any other type of vehicle. These devices may operate in a UE-Infrastructure configuration, a UE-UE (Vehicle-to-Vehicle) configuration, UE-Person configuration, UE-Network configuration and vice versa. Also, a configuration is possible in which the signaling information (control plane) is conveyed via a network/infrastructure/cellular link (such as Uu LTE interface) and the user information (data plane) is conveyed over a device-to-device direct link (such as PC5 LTE interface) or vice versa.

In various embodiments, the configuration of the UE 104 (e.g., the selection of the RAT to use, the selection of the base station or access point to connect with for a given RAT, and/or one or more configurable parameters for communication with the base station or access point) may be determined based on past operational information associated with a same behavioral context. Accordingly, the configuration may be adjusted based on the experience of the UE (or another UE) when the UE was previously in the same situation.

Figure 2 schematically illustrates a predictive configuration system 200 in accordance with various embodiments. The predictive configuration system 200 may include user circumstance circuitry 204, a decision making engine 208, and/or a database 212. In various embodiments, some or all components of the predictive configuration system 200 may be included in the UE 104. Additionally, or alternatively, some or all components of the predictive configuration system 200 may be included in a network entity remotely located from the UE 104 (e.g., base station 108, WLAN access point 112, and/or access point 116). In some embodiments, one or more components of the predictive configuration system 200 may be included in the UE 104, and one or more other components of the predictive configuration system 200 may be included in a network entity remotely located from the UE 104. In one non-limiting example, the user circumstance circuitry 204 may be included in the UE 104, and the decision making engine 208 and/or database 212 may be included in the network entity remotely located from the UE 104.

In various embodiments, the user circumstance circuitry 204 may determine current operational information of the UE 104. The current operational information may include any suitable information, such as radio parameters (e.g., location information, signal quality parameters (e.g., signal strength, signal-to-interference-plus-noise ratio (SINR), packet error rate), available base stations or access points (e.g., cellular base stations visible, Wi-Fi access points visible, etc.)), and/or application parameters (e.g., information identifying one or more applications being run by the UE 104, and/or usage parameters (e.g., data rate)). The location information may be determined from any suitable source, such as global positioning system (GPS) data, network data, data from one or more applications on the UE 104, and/or another suitable source. In various embodiments, the current operational information may include information for multiple RATs and/or for multiple base stations or access points for a same RAT.

The user circumstance circuitry 204 may receive one or more portions of the current operational information from any suitable components, such as measurement circuitry 216 and/or application circuitry 220 of the UE 104. For example, measurement circuitry 216 may measure radio parameters and provide the radio parameters to the user circumstance circuitry 204, and/or the application circuitry 220 may provide application parameters. In various embodiments, the user circumstance circuitry 204 may further determine a behavioral context of the UE 104 that is associated with the current operational information. The behavioral context may correspond, for example, to a location of the UE 104 (whether stationary or traveling from one location to another) and/or activity being performed by the user of the UE 104 (e.g., playing tennis or other sports, walking, running, driving, etc.). The user circumstance circuitry 204 may determine the behavioral context based on any suitable information. For example, in some embodiments, the user circumstance circuitry 204 may determine the behavioral context of the UE 104 based on the current operational information (e.g., the location information, the serving base station or access point, or the available base stations or access points).

Additionally, or alternatively, the user circumstance circuitry 204 may receive information from the user to indicate the location and/or activity. In some embodiments, the user may assign a name to the location and/or activity (e.g., by typing in a name of the user's choosing or selecting a name from a pre-defined list of names). The previously assigned names may be stored (e.g., in the database 212), so that when the user is again at the same location or engaging in the same activity, the user may select from the previously used names.

Additionally, or alternatively, the user circumstance circuitry 204 may use information from one or more other sources to determine the behavioral context of the UE 104. For example, the user circumstance circuitry 204 may obtain data from a map/navigation application, a calendar application, and/or a social network that indicates the user's location or activity.

In various embodiments, the user circumstance circuitry 204 may transform the current operational information and the behavioral context into machine readable user circumstances information 224. The user circumstance circuitry 204 may store or cause to be stored the machine readable user circumstances 224 (including the current operational information and the user behavioral context) in the database 212.

In various embodiments, the cognitive decision making engine 208 may also receive the user behavioral context. In some embodiments, the cognitive decision making engine 208 may further receive the current operational information. The cognitive decision making engine 208 may query the database 212 to determine whether the database 212 has any past operational information associated with the same user behavioral context. If there is past operational information associated with the same user behavioral context stored in the database 212, the cognitive decision making engine 208 obtains the past operational information from the database 212. The cognitive decision making engine 208 then determines a configuration for the UE 104 based on the past operational information (and, optionally, the current operational information). The configuration may include, for example, link selection (e.g., selection of one of the RATs and/or one of the base stations or access points of the RAT with which the UE 104 is to connect).

The UE 104 may then communicate within the wireless network environment 100 using the configuration (e.g., over the selected link). For embodiments in which the cognitive decision engine 208 is included in a network entity that's remotely disposed from the UE 104, the network entity may transmit the configuration to the UE 104.

In some embodiments, the database 212 may also store a trust indicator associated with the past operational information. The value of the trust indicator may be determined based on any suitable factors, such as a difference between the current operational information and past operational information associated with the same behavioral context (e.g., as stored in the database 212). In some embodiments, the user circumstance circuitry 204 may determine the value of the trust indicator and include the trust indicator in the machine readable user circumstance information 224.

To provide a non-limiting example in accordance with one embodiment, assume the current user circumstance is a 30 minute commute from work to home. The historic context information under these user circumstances in the database 212 is, for example, high mean LTE data rate at small standard deviation and low mean HSPA data rate at high standard deviation observed by, e.g., an audio streaming app. In this example, the standard deviation of the observed data rate may be used as the trust indicator. Whenever the UE 104 is in these user circumstances, i.e. commuting from work to home, the user circumstance circuitry 204 may consider the currently observed data rate to re-calculate the mean value and standard deviation of the data rate observed by the audio streaming app (e.g., according to a statistical model). The user circumstance circuitry 204 may then update the historical context information and trust indicator in the database 212 with the re-calculated values.

In this example, the decision making engine 208 may consider past context information and trust indicator from the data base 212 to select the best network when the user starts the audio streaming app. If the UE 104 is, for example, currently in coverage of a HSPA cell with high signal strength and a LTE cell with moderate signal strength, the decision making engine 208 in the UE 104 may decide to attach to the LTE cell because past context information and trust indicator from data base 212 suggest that the LTE connection will be stable throughout the whole commute from work to home whereas the HSPA throughput will fluctuate significantly. Without past context information and trust indicator, the UE 104 might have selected the HSPA cell based on current signal strength and the user might have suffered from poor throughput and degraded audio quality during the commute.

In addition to, or instead of the trust indicator, the operational information stored in the database 212 may have a temporal validity indicator, such as a validity lifetime or a timestamp. Past operational information may no longer be used or may be de-emphasized (e.g., by lowering the associated trust indicator) as it becomes older and/or as newer operational information for the same user behavioral context is added to the database 212.

In some embodiments, the database 212 may store a plurality of entries for one user behavioral context, with each entry including operational information from different instances that the UE 104 was in the user behavioral context. In other embodiments, the database 212 may include a single entry for each user behavioral context, and the past operational information may be updated based on the current operational information. For example, the past operational information may be updated using a weighted average, e.g., based on the age of the past operational information and/or based on the trust indicator.

In some embodiments, the cognitive decision engine 208 may further receive past operational information from other UEs associated with the same user behavioral context. For example, past operational information for multiple UEs may be stored in the database 212 and/or in one or more other databases. The cognitive decision engine 208 may use past operational information from multiple UEs to determine the configuration for the UE 104.

In various embodiments, the user circumstances information may include any suitable fields. For example, the user circumstances information may include an index that corresponds to the user behavioral context. Additionally, or alternatively, the user circumstances information may include a plurality of fields corresponding to the details of the user behavioral context. The fields may include, for example, "Object 1," "Action," "Object 2," and/or "Time Period." In some situations, the "Object 1" field may indicate the starting location and/or the "Object 2" field may indicate the destination location. The user circumstances information may further include one or more fields for operational parameters, such as one or more radio parameters and/or one or more application parameters. Table 1 below shows some examples of contents of the user circumstances information. The possible entries for each field may be pre-defined to make the user circumstances information machine-readable.

Table 1

In some embodiments, the user circumstances circuitry 204 may be implemented across multiple protocol layers of a protocol stack included in the UE 104. For example, the user circumstances circuitry 204 may obtain portions of the current operational information and/or user behavioral context from different protocol layers of the protocol stack. The user circumstances circuitry 204 may pass a message between protocol layers, and different protocol layers may add respective portions of the current operational information to the message and then pass the updated message to the next protocol layer. In some embodiments, the message may be passed to a subset of all the protocol layers.

Figure 3 illustrates propagation of a message 300 between a Layer n and a Layer n-

1 of a protocol stack, in accordance with various embodiments. The Layer n receives the message 300 from the Layer n-1 that includes the operational information from Layer n-1 and Layers n-2 and lower layers (if applicable). The Layer n adds the operational information from the Layer n to the message 300 and passes the updated message 300 to a subsequent layer (if applicable). The user circumstances circuitry 204 may employ different protocol stacks for each RAT that is included in the operational information. In some embodiments, the user circumstances circuitry 204 may use the Open Systems Interconnection (OSI) model for the protocol stacks to facilitate interoperability between different RATs. Figure 4 illustrates a protocol stack architecture 400 (hereinafter "architecture 400") for the predictive configuration system (e.g., the predictive configuration system 200), in accordance with various embodiments. The architecture 400 may include a respective user circumstance protocol stack 404a-d and a respective control protocol stack 408a-d for different respective RATs. One or more RATs may share one or more protocol layers of the user circumstance protocol stack 404a-d and/or the control protocol stack 408a-d (e.g., as shown for control protocol stacks 408c-d). According to the OSI model, the individual user circumstance protocol stacks 404a-d and/or control protocol stacks 408a-d may include, in order from an uppermost layer to a lowermost layer, an application layer, a presentation layer, a session layer, a transport layer, a network layer, a data link layer, and a physical layer. In some embodiments, one or more of the protocol stacks may use a different protocol stack configuration.

In various embodiments, the cognitive decision engine 412 may be implemented in the application layer, and may receive the operational information from the plurality of user circumstance protocol stacks 404a-d. In some embodiments, the message that includes the current operational information may be passed from a lower protocol layer of the protocol stacks 404a-d upward through the respective protocol stack 404a-d to the cognitive decision engine 412 in the application layer. The cognitive decision engine 412 may determine the configuration of the UE as described herein, and pass the configuration back down through the respective control protocol stacks 408a-d. Accordingly, the user circumstance protocol stacks 404a-d may pass user circumstance information upward through the respective user circumstance protocol stacks 404a-d, while the control protocol stacks 408a-d may pass control information downward through the respective control protocol stacks 408a-d. Other schemes may be used in other embodiments.

In various embodiments, the physical layers of the respective control protocol stacks 408a-d may communicate with respective protocol stacks 416a-d of different RATs. The communication may be performed in accordance with the configuration determined by the cognitive decision engine 412.

Figure 5 illustrates an example operation flow/algorithmic structure 500 of a communication device according to some embodiments. The communication device may correspond to, for example, the UE 104, the base station 108, the WLAN access point 112, and/or the access point 116. In some embodiments, the communication device may implement aspects of the predictive configuration system 200.

The operation flow/algorithmic structure 500 may include, at 504, identifying a current behavioral context associated with a UE. At 508, the operation flow/algorithmic structure 500 may include obtaining current operational information associated with the UE. At 512, the operation flow/algorithmic structure 500 may include identifying a stored past behavioral context associated with the current behavioral context. At 516, the operation flow/algorithmic structure 500 may include obtaining past operational information associated with the stored past behavioral context. At 520, the operation flow/algorithmic structure 500 may include determining, based on the past operational information and the current operational information, a configuration for the UE in a wireless communication network. The determination of the configuration may include, for example, selection of an RAT and/or selection of a base station or access point with which the UE is to connect.

Figure 6 illustrates an example operation flow/algorithmic structure 600 of a UE (e.g., UE 104) according to some embodiments.

The operation flow/algorithmic structure 600 may include, at 604, determining current operational information for the UE. The operation 604 may be performed, for example, by measurement circuitry (e.g., the measurement circuitry 206) of the UE.

At 608, the operation flow/algorithmic structure 600 may include identifying a behavioral context of the UE associated with the current operational information. At 612, the operation flow/algorithmic structure may include storing or causing to be stored the current operational information and an indicator of the behavioral context in a database for use by a cognitive decision engine for a future decision on a network link selection for the UE when the UE again has the behavioral context. In some embodiments, the cognitive decision engine and/or database may be included in the UE. In other embodiments, the cognitive decision engine and/or database may be included in a network entity remotely disposed from the UE (e.g., a base station or access point).

In some embodiments, the operation 608 and/or operation 612 may be performed by user circumstance circuitry (e.g., the user circumstance circuitry 204) of the UE.

Figure 7 illustrates an example operation flow/algorithmic structure 700 of a communication device according to some embodiments. In some embodiments, the communication device may be a network entity that is remotely disposed from the UE. For example, the network entity may be a base station (e.g., base station 108, such as an eNB or gNB), a WLAN access point (e.g., WLAN access point 112), and/or an access point for another RAT (e.g., access point 116). In other embodiments, the communication device may be the UE.

The operation flow/algorithmic structure 700 may include, at 704, storing or causing to be stored past operational information of a UE in a database. The past operational information may be associated with a behavioral context of the UE. The behavioral context and/or an indicator of the behavioral context may also be stored in the database.

At 708, the operation flow/algorithmic structure 700 may include receiving, from the UE, an indicator of the behavioral context of the UE and current operational information for the UE. At 712, the operation flow/algorithmic structure 700 may include retrieving the past operational information from the database based on the indicator of the behavioral context.

At 716, the operation flow/algorithmic structure 700 may include determining a network link selection for the UE based on the past operational information. In embodiments in which the operation flow/algorithmic structure 700 is implemented in a network entity that is remotely disposed from the UE, the operation flow/algorithmic structure 700 may further include, at 720, transmitting, to the UE, an indicator of the network link selection. The indicator may include, for example, a message instructing the UE to connect with a specific RAT and/or base station/access point.

Example Use Case

An example use case for the predictive configuration system (e.g., predictive configuration system 200) described herein will now be described. A mobile device (UE) may typically be used in various user circumstances which are either unique - e.g., a user is on a one-time visit in a foreign city - or which may occur again (in cycles) - e.g. a user is driving from his or her home to work, taking kids to school, etc. This scenario may address the case in which a UE finds itself repeatedly in similar user circumstances. In such a case, the UE may store observations (e.g., averaged) of the operational information, e.g. availability of specific RATs, link quality metrics, the type of applications being used, etc. in a database. The UE may additionally store information indicating the behavioral context of the UE that is associated with the operational information. When the concerned user is identified to be in similar User Circumstances again, the historic information may be exploited - typically in combination with instantaneous measurements - in order to implement predictive decision making. Accordingly, future changes in Key Performance Indicators (KPIs) may be anticipated and corresponding configuration changes may be implemented well in advance, e.g. in order to avoid call drops occurring repeatedly in a given area or similar.

Various stakeholders may be involved in some or all aspects of the embodiments described herein. For example, the stakeholders may include the mobile devices (UEs) accessing the internet and other mobile data services. Additionally, network operators of a single network or multiple networks may operate and maintain infrastructure. Some network operators may additionally operate other networks in other frequency bands. The network operator (e.g., through the base station or access point managed by the network operator) may provide user circumstances information to the mobile device (UE) to enable the mobile device to select an RAT and/or access point/base station. Additionally, or alternatively, the network operator may provide one or more constraints for the UE to use in the link selection process. The one or more constraints may include, for example, an RAT preference (e.g., LTE preferred over 3G and 2G, or WiFi preferred over cellular), and/or a preferred operator in roaming scenarios. In some embodiments, a third party context provider may provide the UE with user circumstances information that is aggregated from multiple UEs. For example, the third party context provider may provide the aggregated user circumstances information via a Cognitive Pilot Channel.

As discussed herein, the acquired user circumstances information may be exploited in order to identify the best possible configuration for a concerned mobile device. For this purpose a combination of instantaneous observations together with historical (averaged) data may be used in order to enable predictive decision making. Depending on the choice of the decision making entity (e.g., network centric decision making, mobile device centric decision making, hybrid decision making split between network and mobile device), the user circumstances information may be transported (and accumulated from various sources) to the decision making entity.

For example, a mobile device may be a car and/or a device traveling in a car that travels along a route. Without predictive decision making, the mobile device may maintain a connection to a specific RAT, and a call drop may occur. With predictive decision making as described herein, then the call drop is anticipated based on past observation and a handover to a different configuration (e.g., different RAT and/or different base station/access point) is made. Therefore, the link quality of the mobile device is maintained.

To support the predictive decision making described herein, the following may be provided by the UE and/or network entity remotely disposed from the UE:

· Standardized acquisition of instantaneous context information (e.g., user circumstances information including a behavioral context and operational information as described above), depending on the available sensors, such as location determination, characterization of radio links, interference environment, etc.

• Transfer of instantaneous context information to a processing entity (e.g., user circumstance circuitry 204) for i) deriving historical (averaged) database entries and ii) deriving a machine readable representation of the user circumstances information.

• Standardized access to historical (averaged) information for supporting predictive decision making. Any of the radio links described herein may operate according to any one or more of the following radio communication technologies and/or standards including but not limited to: a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3GPP) radio communication technology, for example Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3 GPP Long Term Evolution Advanced (LTE Advanced), Code division multiple access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed Circuit-Switched Data (HSCSD), Universal Mobile

Telecommunications System (Third Generation) (UMTS (3G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+), Universal Mobile Telecommunications System-Time-Division Duplex (UMTS-TDD),

Time Division-Code Division Multiple Access (TD-CDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3 GPP Rel. 8 (Pre-4G)), 3GPP Rel. 9 (3rd Generation Partnership Project Release 9), 3GPP Rel. 10 (3rd Generation Partnership Project Release 10) , 3 GPP Rel. 11 (3rd Generation Partnership Project Release 11), 3 GPP Rel. 12 (3rd Generation Partnership Project Release 12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3 GPP Rel. 14 (3rd Generation Partnership Project Release 14), 3 GPP Rel. 15 (3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rd Generation Partnership Project Release 16), 3GPP Rel. 17 (3rd Generation Partnership Project Release 17) and subsequent Releases (such as Rel. 18, Rel. 19, etc.), 3GPP 5G, 3 GPP LTE Extra, LTE-Advanced Pro, LTE Licensed- Assisted Access (LAA), MuLTEfire, UMTS

Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G), Code division multiple access 2000 (Third generation) (CDMA2000 (3G)), Evolution- Data Optimized or Evolution-Data Only (EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS (1G)), Total Access Communication System/Extended Total Access Communication System (TACS/ETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Telephone System (AMTS), OLT (Norwegian for Offentlig Landmobil Telefoni, Public Land Mobile Telephony), MTD (Swedish abbreviation for Mobiltelefonisystem D, or Mobile telephony system D), Public

Automated Land Mobile (Autotel/PALM), ARP (Finnish for Autoradiopuhelin, "car radio phone"), NMT (Nordic Mobile Telephony), High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex,

DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handy-phone System (PHS), Wideband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA), also referred to as 3 GPP Generic Access Network, or GAN standard), Zigbee, Bluetooth(r), Wireless Gigabit Alliance (WiGig) standard, mmWave standards in general (wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802.11 ad, IEEE 802.11 ay, etc.), technologies operating above 300 GHz and THz bands, (3GPP/LTE based or IEEE 802. l ip and other) Vehicle-to-Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to-Infrastructure (V2I) and Infrastructure-to-Vehicle (I2V) communication technologies, 3GPP cellular V2X, DSRC (Dedicated Short Range Communications) communication systems such as Intelligent-Transport-Systems and others, the European ITS-G5 system (i.e. the European flavor of IEEE 802.1 lp based DSRC, including ITS- G5A (i.e., Operation of ITS-G5 in European ITS frequency bands dedicated to ITS for safety re-lated applications in the frequency range 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., Operation in European ITS frequency bands dedicated to ITS non- safety applications in the frequency range 5,855 GHz to 5,875 GHz), ITS-G5C (i.e., Operation of ITS applications in the frequency range 5,470 GHz to 5,725 GHz)), etc.

Aspects described herein may be used in the context of any spectrum management scheme including dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as LSA = Licensed Shared Access in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies and SAS = Spectrum Access System in 3.55-3.7 GHz and further frequencies). Applicable spectrum bands include IMT (International Mobile Telecommunications) spectrum (including 450 - 470 MHz, 790 - 960 MHz, 1710 - 2025 MHz, 2110 - 2200 MHz, 2300 - 2400 MHz, 2500 - 2690 MHz, 698-790 MHz, 610 - 790 MHz, 3400 - 3600 MHz, etc). Note that some bands are limited to specific region(s) and/or countries), IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range, etc.), spectrum made available under FCC's "Spectrum Frontier" 5G initiative (including 27.5 - 28.35 GHz, 29.1 - 29.25 GHz, 31 - 31.3 GHz, 37 - 38.6 GHz, 38.6 - 40 GHz, 42 - 42.5 GHz, 57 - 64 GHz, 71 - 76 GHz, 81 - 86 GHz and 92 - 94 GHz, etc), the ITS

(Intelligent Transport Systems) band of 5.9 GHz (typically 5.85-5.925 GHz) and 63-64 GHz, bands currently allocated to WiGig such as WiGig Band 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz) and WiGig Band 3 (61.56-63.72 GHz) and WiGig Band 4 (63.72-65.88 GHz), the 70.2 GHz - 71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated to automotive radar applications such as 76-81 GHz, and future bands including 94-300 GHz and above. Furthermore, the scheme can be used on a secondary basis on bands such as the TV White Space bands (typically below 790 MHz), such as the 400 MHz and 700 MHz bands. Besides cellular applications, specific applications for vertical markets may be provided such as PMSE (Program Making and Special Events), medical, health, surgery, automotive, low-latency, drones, etc.

applications.

Some embodiments may implement a hierarchical application of the predictive decision making scheme described herein, e.g. by introducing a hierarchical prioritization of usage for different types of users (e.g., low/medium/high priority, etc.), based on a prioritized access to the spectrum (e.g., with highest priority to tier-1 users, followed by tier-2, then tier-3, etc).

Aspects described herein can also be applied to different Single Carrier or orthogonal frequency division multiplexing (OFDM) flavors (e.g., CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3 GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

Some of the features described herein are defined for the network side, such as Access Points, eNodeBs, etc. However, a UE may take this role as well and act as an Access Point, eNodeB, etc. Accordingly, some or all features defined for network equipment may be implemented by a UE.

Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software. Figure 8 illustrates, for one embodiment, example components of an electronic device 800. In embodiments, the electronic device 800 may be, implement, be incorporated into, or otherwise be a part of a UE (e.g., UE 104), a base station (e.g., base station 108, such as an eNB or gNB), a WLAN access point (e.g., WLAN access point 112), and/or an access point of another RAT (e.g., access point 116). In some embodiments, the electronic device 800 may include application circuitry 802, baseband circuitry 804, Radio Frequency (RF) circuitry 806, front-end module

(FEM) circuitry 808 and one or more antennas 810, coupled together at least as shown. In embodiments where the electronic device 800 is implemented in or by an eNB 108, the electronic device 800 may also include network interface circuitry (not shown) for communicating over a wired interface (for example, an X2 interface, an SI interface, and the like).

The application circuitry 802 may include one or more application processors. For example, the application circuitry 802 may include circuitry such as, but not limited to, one or more single-core or multi-core processors 802a. The processor(s) 802a may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors 802a may be coupled with and/or may include computer-readable media 802b (also referred to as "CRM 802b", "memory 802b", "storage 802b", or "memory /storage 802b") and may be configured to execute instructions stored in the CRM 802b to enable various applications and/or operating systems to run on the system.

The baseband circuitry 804 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 804 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 806 and to generate baseband signals for a transmit signal path of the RF circuitry 806. Baseband circuity 804 may interface with the application circuitry 802 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 806. For example, in some embodiments, the baseband circuitry 804 may include a second generation (2G) baseband processor 804a, third generation (3G) baseband processor 804b, fourth generation (4G) baseband processor 804c, and/or other baseband processor(s) 804d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 804 (e.g., one or more of baseband processors 804a-d) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 806. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, and the like. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 804 may include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 804 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.

Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

In some embodiments, the baseband circuitry 804 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (E-UTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements. A central processing unit (CPU) 804e of the baseband circuitry 804 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In various embodiments, baseband circuitry 804 may implement user circumstances protocol stacks and/or control protocol stacks for multiple RATs, as described with respect to Figure 4.

In some embodiments, the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 804f. The audio DSP(s) 804f may include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. The baseband circuitry 804 may further include computer-readable media 804g (also referred to as "CRM 804g", "memory 804g", "storage 804g", or "memory /storage 804b"). The CRM 804g may be used to load and store data and/or instructions for operations performed by the processors of the baseband circuitry 804. For example, the CRM 804g may load and store data and/or instructions that, when executed by one or more processors of the baseband circuitry 804, cause the baseband circuitry 804 to implement the operation flow/algorithmic structure 500, 600, and/or 700.

CRM 804g for one embodiment may include any combination of suitable volatile memory and/or non-volatile memory. The CRM 804g may include any combination of various levels of memory /storage including, but not limited to, read-only memory (ROM) having embedded software instructions (e.g., firmware), random access memory (e.g., dynamic random access memory (DRAM)), cache, buffers, etc.). The CRM 804g may be shared among the various processors or dedicated to particular processors. Components of the baseband circuitry 804 may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 804 and the application circuitry 802 may be implemented together, such as, for example, on a system on a chip (SOC).

In some embodiments, the baseband circuitry 804 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 804 may support communication with an E-UTRAN and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 804 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

RF circuitry 806 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various

embodiments, the RF circuitry 806 may include switches, filters, amplifiers, etc., to facilitate the communication with the wireless network. RF circuitry 806 may include a receive signal path that may include circuitry to down-convert RF signals received from the FEM circuitry 808 and provide baseband signals to the baseband circuitry 804. RF circuitry 806 may also include a transmit signal path that may include circuitry to up- convert baseband signals provided by the baseband circuitry 804 and provide RF output signals to the FEM circuitry 808 for transmission.

In some embodiments, the RF circuitry 806 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 806 may include mixer circuitry 806a, amplifier circuitry 806b and filter circuitry 806c. The transmit signal path of the RF circuitry 806 may include filter circuitry 806c and mixer circuitry 806a. RF circuitry 806 may also include synthesizer circuitry 806d for synthesizing a frequency for use by the mixer circuitry 806a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 806a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 808 based on the synthesized frequency provided by synthesizer circuitry 806d. The amplifier circuitry 806b may be configured to amplify the down-converted signals and the filter circuitry 806c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 804 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 806a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 806a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 806d to generate RF output signals for the FEM circuitry 808. The baseband signals may be provided by the baseband circuitry 804 and may be filtered by filter circuitry 806c. The filter circuitry 806c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion, respectively. In some embodiments, the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path may be arranged for direct downconversion and/or direct upconversion, respectively. In some embodiments, the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path may be configured for super-heterodyne operation.

In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 806 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 804 may include a digital baseband interface to communicate with the RF circuitry 806.

In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 806d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 806d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider. The synthesizer circuitry 806d may be configured to synthesize an output frequency for use by the mixer circuitry 806a of the RF circuitry 806 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 806d may be a fractional N/N+l synthesizer.

In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 804 or the application circuitry 802 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 802.

Synthesizer circuitry 806d of the RF circuitry 806 may include a divider, a delay- locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A). In some embodiments, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 806d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 806 may include an IQ/polar converter.

FEM circuitry 808 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 810, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 806 for further processing. FEM circuitry 808 may also include a transmit signal path that may include circuitry configured to amplify signals for transmission provided by the RF circuitry 806 for transmission by one or more of the one or more antennas 810. In some embodiments, the FEM circuitry 808 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry 808 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 806). The transmit signal path of the FEM circuitry 808 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 806), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 810).

In some embodiments, the electronic device 800 may include additional elements such as, for example, a display, a camera, one or more sensors, and/or interface circuitry (for example, input/output (I/O) interfaces or buses) (not shown). In embodiments where the electronic device is implemented in or by a base station (e.g., eNB or gNB) or an access point, the electronic device 800 may include network interface circuitry. The network interface circuitry may be one or more computer hardware components that connect electronic device 800 to one or more network elements, such as one or more servers within a core network or one or more other base stations or access points via a wired connection. To this end, the network interface circuitry may include one or more dedicated processors and/or field programmable gate arrays (FPGAs) to communicate using one or more network communications protocols such as X2 application protocol (AP), SI AP, Stream Control Transmission Protocol (SCTP), Ethernet, Point-to-Point (PPP), Fiber Distributed Data Interface (FDDI), and/or any other suitable network communications protocols.

Some non-limiting Examples of various embodiments are provided below.

Example 1 is one or more computer-readable media having instructions, stored thereon, that, when executed by one or more processors of a communication device, cause the communication device to: identify a current behavioral context associated with a user equipment (UE); obtain current operational information associated with the UE; identify a stored past behavioral context associated with the current behavioral context; obtain past operational information associated with the stored past behavioral context; and determine, based on the past operational information and the current operational information, a configuration for the UE in a wireless communication network.

Example 2 is the one or more media of Example 1, wherein the current behavioral context includes information associated with a location of the UE or an activity being performed by a user of the UE.

Example 3 is the one or more media of Example 2, wherein the information includes a name of the location or activity, wherein the name is assigned by the user.

Example 4 is the one or more media of any one of Examples 1 to 3, wherein the current operational information includes one or more of signal strength, cell towers visible, wireless fidelity (Wi-Fi) access points visible, signal to interference plus noise ratio (SINR), or packet error rate.

Example 5 is the one or more media of any one of Examples 1 to 4, wherein the past operational information includes information associated with different radio access technologies (RATs).

Example 6 is the one or more media of Example 5, wherein the determination of the configuration for the UE includes selection of one of the RATs for a communication link.

Example 7 is the one or more media of any one of Examples 1 to 6, wherein the past operational information is obtained from a database, and wherein the instructions, when executed, further cause the communication device to update the past operational information in the database based on the current operational information.

Example 8 is the one or more media of Example 7, wherein the past operational information includes a trust indicator, and wherein the instructions, when executed, further cause the communication device to update the trust indicator based on a difference between the past operational information and the current operational information. Example 9 is the one or more media of Example 7 or Example 8, wherein the past operational information is updated using a weighted average based on an age of the past operational information.

Example 10 is the one or more media of any one of Examples 1 to 9, wherein, to obtain the current operational context information, the instructions, when executed, are to cause the communication device to collect portions of the operational context information from different protocol layers of a protocol stack of the UE using a message that is passed from a physical layer of the protocol stack to an application layer of the protocol stack.

Example 1 1 is the one or more media of any one of Examples 1 to 10, wherein the past operational information includes operational information from other UEs.

Example 12 is the one or more media of any one of Examples 1 to 1 1, wherein the current operational information includes information associated with an application currently run by the UE or a current data usage of the UE.

Example 13 is the one or more media of any one of Examples 1 to 12, wherein the communication device is the UE, and wherein the instructions, when executed, further cause the UE to communicate over the wireless communication network using the configuration.

Example 14 is the one or more media of any one of Examples 1 to 12, wherein the communication device is a network entity remotely located from the UE, and wherein the instructions, when executed, further cause the communication device to transmit the configuration to the UE.

Example 15 is a user equipment (UE) comprising: measurement circuitry to determine current operational information for the UE; and user circumstance circuitry coupled to the measurement circuitry. The user circumstance circuitry is to: identify a behavioral context of the UE associated with the current operational information; and store or cause to be stored the current operational information and an indicator of the behavioral context in a database for use by a cognitive decision engine for a future decision on a network link selection for the UE when the UE again has the behavioral context.

Example 16 is the UE of Example 15, wherein the UE includes the cognitive decision engine and the database.

Example 17 is the UE of Example 15 or Example 16, wherein the cognitive decision engine is implemented in an application layer of a protocol stack including a plurality of protocol layers, wherein the user circumstance circuitry is to determine the current operational information via a message that is passed from a protocol layer of the plurality of protocol layers that is at a lower protocol level than the application layer, and wherein the message includes portions of the current operational information from multiple protocol layers of the plurality of protocol layers.

Example 18 is the UE of any one of Examples 15 to 17, wherein the user circumstance circuitry is further to assign a trust indicator to the current operational information based on past operational information associated with the behavioral context that is stored in the database.

Example 19 is the UE of any one of Examples 15 to 18, wherein the current operational information includes signal quality information for multiple radio access technologies (RATs).

Example 20 is a base station or access point comprising: a database to store past operational information of a user equipment (UE), wherein the past operational information is associated with a behavioral context of the UE; and a cognitive decision engine coupled to the database. The cognitive decision engine is to: receive, from the UE, an indicator of the behavioral context of the UE and current operational information for the UE; retrieve the past operational information from the database based on the indicator of the behavioral context; determine a configuration for the UE based on the past operational information; and transmit, to the UE, an indicator of the configuration.

Example 21 is the base station or access point of Example 20, wherein the cognitive decision engine is further to update the past operational information stored in the database based on the current operational information.

Example 22 is the base station or access point of Example 21, wherein the past operational information includes a trust indicator, and wherein the cognitive decision engine is to update the trust indicator based on a difference between the past operational information and the current operational information.

Example 23 is the base station or access point of any one of Examples 20 to 22, wherein the database is further to store past operational information for other UEs associated with the behavioral context of the other UEs, and wherein the configuration is determined based on the past operational information for the UE and the past operational information for the other UEs.

Example 24 is the base station or access point of any one of Examples 20 to 23, wherein the current operational information includes signal quality information for multiple radio access technologies (RATs). Example 25 is the base station or access point of any one of Examples 20 to 24, wherein the current operational information includes information associated with an application currently run by the UE or a current data usage of the UE.

Example 26 is the base station or access point of any one of Examples 20 to 25, wherein the configuration of the UE is a network link selection.

Example 27 is the base station or access point of any one of Examples 20 to 26, wherein the base station or access point is an evolved Node B (eNB).

Example 28 is the base station or access point of any one of Examples 20 to 26, wherein the base station or access point is a wireless local area network (WLAN) access point of a WLAN.

Example 29 is a wireless communication device comprising: means to identify a current behavioral context associated with a user equipment (UE); means to obtain current operational information associated with the UE; means to identify a stored past behavioral context associated with the current behavioral context; means to obtain past operational information associated with the stored past behavioral context; and means to determine, based on the past operational information and the current operational information, a configuration for the UE in a wireless communication network.

Example 30 is the wireless communication device of Example 29, wherein the current behavioral context includes information associated with a location of the UE or an activity being performed by a user of the UE.

Example 31 is the wireless communication device of Example 29 or Example 30, wherein the current operational information includes one or more of signal strength, cell towers visible, wireless fidelity (Wi-Fi) access points visible, signal to interference plus noise ratio (SINR), or packet error rate.

Example 32 is the wireless communication device of any one of Examples 29 to

31 , wherein the past operational information includes information associated with different radio access technologies (RATs), and wherein the determination of the configuration for the UE includes selection of one of the RATs for a communication link.

Example 33 is the wireless communication device of any one of Examples 29 to 32, wherein the past operational information is obtained from a database, and wherein the wireless communication device further comprises means to update the past operational information in the database based on the current operational information.

Example 34 is the wireless communication device of Example 33, wherein the past operational information includes a trust indicator, and wherein the wireless communication device further comprises means to update the trust indicator based on a difference between the past operational information and the current operational information.

Example 35 is the wireless communication device of any one of Examples 29 to 34, wherein, to obtain the current operational context information, the wireless communication device further comprises means to collect portions of the operational context information from different protocol layers of a protocol stack of the UE using a message that is passed from a physical layer of the protocol stack to an application layer of the protocol stack.

Example 36 is the wireless communication device of any one of Examples 29 to

35, wherein the past operational information includes operational information from other UEs.

Example 37 is the wireless communication device of any one of Examples 29 to

36, wherein the current operational information includes information associated with an application currently run by the UE or a current data usage of the UE.

Example 38 is the wireless communication device of any one of Examples 29 to

37, wherein the wireless communication device is the UE, and wherein the wireless communication device further comprises means to communicate over the wireless communication network using the configuration.

Example 39 is the wireless communication device of any one of Examples 29 to

37, wherein the communication device is a network entity remotely located from the UE, and wherein the wireless communication device further comprises means to cause the communication device to transmit the configuration to the UE.

The present disclosure is described with reference to flowchart illustrations or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations or block diagrams, and combinations of blocks in the flowchart illustrations or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for

implementing the functions/acts specified in the flowchart or block diagram block or blocks. These computer program instructions may also be stored in a computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instruction means that implement the function/act specified in the flowchart or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart or block diagram block or blocks.

The description herein of illustrated implementations, including what is described in the Abstract, is not intended to be exhaustive or to limit the present disclosure to the precise forms disclosed. While specific implementations and examples are described herein for illustrative purposes, a variety of alternate or equivalent embodiments or implementations calculated to achieve the same purposes may be made in light of the above detailed description, without departing from the scope of the present disclosure, as those skilled in the relevant art will recognize.