Patent Publication Number: US-2016226632-A1

Title: Carrier aggregation enhancements for unlicensed  spectrum and 5g

Description:
CLAIM OF PRIORITY 
     Priority of U.S. Provisional patent application Ser. No. 62/109,168, attorney docket No. P80195Z, filed Jan. 29, 2015, is claimed and is hereby incorporated by reference. 
    
    
     BACKGROUND 
     Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless mobile device. In the third generation partnership project (3GPP) long term evolution (LTE) systems, the base station may be an evolved Node Bs (eNode Bs or eNBs) in a Universal Terrestrial Radio Access Network (UTRAN) or an evolved UTRAN (eUTRAN), which communicates with the wireless mobile device, e.g., a user equipment (UE). 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       The invention described herein is illustrated by way of example and not by way of limitation in the accompanying figures. For simplicity and clarity of illustration, elements illustrated in the figures are not necessarily drawn to scale. For example, the dimensions of some elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference labels have been repeated among the figures to indicate corresponding or analogous elements. 
         FIG. 1  schematically illustrates an example of a network comprising a UE and an eNB, in accordance with various embodiments. 
         FIG. 2  illustrates an electronic device circuitry according to an embodiment. 
         FIG. 3  illustrates an example of a layer structure in radio protocol architecture according to an embodiment. 
         FIG. 4  illustrates an example of a layer structure in radio protocol architecture according to an embodiment. 
         FIG. 5  illustrates a flow chart of a method in accordance with an embodiment; 
         FIG. 6  illustrates a flow chart of a method in accordance with an embodiment; 
         FIG. 7  illustrates a flow chart of a method in accordance with an embodiment; 
         FIG. 8  illustrates a flow chart of a method in accordance with an embodiment; 
         FIG. 9  illustrates a flow chart of a method in accordance with an embodiment; 
         FIG. 10  illustrates a flow chart of a method in accordance with an embodiment; 
         FIG. 11  illustrates a flow chart of a method in accordance with an embodiment; and 
         FIG. 12  illustrates an example of a block diagram of a mobile communication device in accordance with an embodiment. 
     
    
    
     Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended. 
     DETAILED DESCRIPTION 
     Before the present invention is disclosed and described, it is to be understood that this invention is not limited to the particular structures, process steps, or materials disclosed herein, but is extended to equivalents thereof as would be recognized by those ordinarily skilled in the relevant arts. It should also be understood that terminology employed herein is used for the purpose of describing particular examples only and is not intended to be limiting. The same reference numerals in different drawings represent the same element. 
     References in the specification to “one embodiment”, “an embodiment”, “an example embodiment”, etc., indicate that the embodiment described may comprise a particular feature, structure, or characteristic, but every embodiment may not necessarily comprise the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. 
     Embodiments of the invention may be implemented in hardware, firmware, software, or any combination thereof. Embodiments of the invention may also be implemented as instructions stored on a machine-readable medium, which may be read and executed by one or more processors. A machine-readable medium may comprise any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computing device). For example, a non-transitory machine-readable medium may comprise read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices. For another example, a machine-readable medium may comprise electrical, optical, acoustical or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.), and others. 
     The following description may comprise terms, such as first, second, etc. that are used for descriptive purposes only and are not to be construed as limiting. As used herein, the term “module” may refer to, be part of, or comprise an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable component(s) that provide the described functionality. 
     Further, various operations will be described as multiple discrete operations, in turn, in a manner that is most helpful in understanding the illustrative embodiments; however, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations need not be performed in the order of presentation. 
     An initial overview of technology embodiments is provided below and then specific technology embodiments are described in further detail later. This initial summary is intended to aid readers in understanding the technology more quickly but is not intended to identify key features or essential features of the technology nor is it intended to limit the scope of the claimed subject matter. The following definitions are provided for clarity of the overview and embodiments described below. 
     In 3GPP radio access network (RAN) LTE systems, a transmission station may be a combination of Evolved universal terrestrial radio access network (E-UTRAN) Node Bs (or may be denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, and/or eNBs), which may communicate with a wireless mobile device, known as a user equipment (UE). 
     Some embodiments may be used in conjunction with various devices and systems, for example, a user equipment (UE), a mobile device (MD), a wireless station (STA), a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a smart phone, a server computer, a handheld computer, a handheld device, a personal digital assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wireless node, a base station (BS), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a cellular network, a cellular node, a cellular device, a wireless local area network (WLAN), a multiple input multiple output (MIMO) transceiver or device, a device having one or more internal antennas and/or external antennas, digital video broadcast (DVB) devices or systems, multi-standard radio devices or systems, a wired or wireless handheld device, e.g., a smartphone, a wireless application protocol (WAP) device, vending machines, sell terminals, or the like. 
     Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems, for example, radio frequency (RF), frequency-division multiplexing (FDM), orthogonal FDM (OFDM), single carrier frequency division multiple access (SC-FDMA), time-division multiplexing (TDM), time-division multiple access (TDMA), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code-division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi-tone (DMT), Bluetooth®, global positioning system (GPS), wireless fidelity (Wi-Fi), Wi-Max, ZigBee™, ultra-wideband (UWB), global system for mobile (GSM), second generation (2G), 2.5G, 3G, 3.5G, 4G, 4.5G, fifth generation (5G) mobile networks, 3GPP, long term evolution (LTE) cellular system, LTE advance cellular system, high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), high-speed packet access (HSPA), HSPA+, single carrier radio transmission technology (1×RTT), evolution-data optimized (EV-DO), enhanced data rates for GSM evolution (EDGE), and the like. Other embodiments may be used in various other or future devices, systems and/or networks. 
     Some demonstrative embodiments are described herein with respect to a LTE network. However, other embodiments may be implemented in any other suitable cellular network or system, e.g., a GSM network, a 3G cellular network such as a Universal Mobile Telecommunications System (UMTS) cellular system, a 4G cellular network, a 4.5G network, a 5G cellular network, a WiMax cellular network, or the like or other future network. 
       FIG. 1  schematically illustrates a wireless communication network  100  in accordance with various embodiments. The wireless communication network  100  (hereinafter “network  100 ”) may be an access network of a 3GPP LTE network such as E-UTRAN, 3GPP LTE-A network, 4G network, 4.5G network, a 5G cellular network or other future communication network, a WiMax cellular network, HSPA, Bluetooth, WiFi or other type of wireless access networks. The network  100  may comprise one or more wireless communication devices capable of communicating content, data, information and/or signals via one or more wireless mediums, for example, a radio channel, a cellular channel, an RF channel, a wireless-local-area-network (WLAN) channel such as a WiFi channel, and/or the like. In some demonstrative embodiments, one or more elements of network  100  may optionally be capable of communicating over any suitable wired communication links. 
     In some demonstrative embodiments, the network  100  may comprise a base station, e.g., an enhanced node base station (eNB)  110  that may wirelessly communicate with a mobile device or terminal, e.g., a user equipment (UE)  120 . In some demonstrative embodiments, the eNB  110  may be comprised in a radio access network that may comprise one or more cellular nodes, e.g., an eNB, a Node B, a base station (BS), a base transceiver station (BTS), and/or the like. 
     In some demonstrative embodiments, UE  120  may be a subscriber station that may be configured to utilize radio resources across one or more carriers such as in a carrier aggregation scheme. In some embodiments, UE  120  may be configured to utilize carrier aggregation (CA), wherein one or more component carriers (CCs) may be aggregated for communication between eNB  110  and UE  120 . For example, UE  120  may connect with a primary serving cell (PCell) of eNB  110  utilizing a primary CC. UE  120  may connect with one or more secondary serving cells (SCells) of eNB  110  utilizing one or more secondary CCs. In various embodiments, UE  120  may communicate in one or more wireless communication networks, including 3GPP LTE network, 3GPP LTE-U network, 3GPP LTE-A network, a 5G cellular network or other wireless networks such as a 4G network, a 4.5G network, a WiMax cellular network, WiMAX, HSPA, Bluetooth, WiFi, or the like. 
     In some demonstrative embodiments, eNB  110  and/or UE  120  may comprise an LTE system that may utilize a licensed spectrum assigned to a corresponding LTE service provider (or operator). The LTE system that is to operate in a licensed spectrum may be called as LTE in Licensed Spectrum or simply LTE. In response to an upsurge in demand for wireless broadband data, 3GPP Release 13 may transmit data through an unlicensed spectrum and/or a licensed spectrum to increase a data throughput of an LTE system. The LTE system that is to operate in an unlicensed spectrum may be called as LTE in Unlicensed Spectrum or LTE-U. A system that may integrate LTE and LTE-U using carrier aggregation (CA) technology may be called as Licensed-Assisted Access (LAA) using LTE, or simply LAA. In LAA, an LTE licensed carrier may be served as a primary cell or PCell and one or more LTE-U carriers may be served as secondary cell(s) or SCell(s). 
     A CC may support one or more communication channels according to a release of 3GPP LTE-advanced communication standard. For example, a CC may support one or more communication channels to carry information between UE  120  and eNB  110 . A CC may include one or more uplink and downlink subframes to carry information between eNB  110  and UE  120 . One or more radio bearers may be used to implement a quality of service (QoS) supporting in an air interface. In carrier aggregation, a radio bearer may be transmitted and/or received on one or more serving cells. 
     In some embodiments, radio environments on one or more serving cells may not be fundamentally different. In some embodiments, a radio environment on an unlicensed spectrum may be different from that on a licensed spectrum of an LTE system. In the radio environment on the unlicensed spectrum, an LTE operator such as eNB  110  may need to control various interference sources, e.g., other radio access technologies (RAT) such as WiFi or one or more LAA-capable eNBs/UEs of other operator(s), etc. In some embodiments, an unlicensed carrier may be switched off due to relatively strong interference. One or more unstable radio conditions in an unlicensed spectrum may impact QoS or other requirements of one or more bearers, e.g., latency/reliability requirement. Examples of the one or more bearers may comprise voice, real time gaming, or signaling radio bearer (SRB) and other bearers that may have latency and/or reliability requirements. In some other embodiments, for services such as a best-effort service, QoS may not be impacted using LAA. 
     In an example of a bearer carried over a radio link control (RLC) unacknowledged mode (UM), in response to an uplink (UL) grant in a serving cell, a UE, e.g., UE  120 , may apply logical channel prioritization (LCP) to decide how to utilize the UL grant. Here, uplink is used as an example. In some embodiments, UE  120  may not distinguish from which carrier the UE receives the UL grant. In response to the UL grant, UE  120  may transmit on a licensed spectrum or an unlicensed spectrum data of a delay/reliability sensitive service, e.g., voice, real time gaming, or signaling radio bearer (SRB) or any other service with latency and/or reliability requirements. For example, if UE  120  transmits the data of the delay/reliability sensitive service in an unlicensed spectrum, latency/reliability requirement of the delay/reliability sensitive service may not be satisfied, e.g., due to one or more unstable radio conditions in unlicensed spectrum. One embodiment may restrict that one or more bearers are to be transmitted/received to/from only a subset of serving cells in carrier aggregation to satisfy latency/reliability requirement(s) for the one or more bearers. 
     The Fifth generation (5G) of mobile technology may enable a mobile and/or a connected environment and may empower socio-economic transformations. For example, one requirement of 5G may reduce latency, e.g., an end to end latency. In one example, carrier aggregation architecture may be used to utilize radio resource(s) of LTE and/or radio resource(s) of 5G RAT for a UE. 
     One embodiment may restrict that a communication of a signaling radio bearer (SRB) and/or a data radio bearer with one or more QoS requirements may be only on a subset of serving cells or carriers of an eNB based on a service type of the communication, e.g., a LTE communication, a LTE-A communication, a 5G communication and/or other future RAT communication. For example, one embodiment may restrict that the SRB and/or the data radio bearer to be transmitted and/or received from/to only a subset of serving cells or carriers based on a type of a service for the transmission and/or the reception. The restriction may be included or fixed in one or more wireless standard specifications, e.g., LTE specification, LTE-A specification, 5G specification and/or specifications of other wireless communication standards. For example, for a LAA, one embodiment may map a delay/latency sensitive radio bearer (e.g., voice over internet protocol (VoIP) and/or real time gaming services, etc.) and/or a radio bearers that require relatively high reliability (e.g., SRB services, etc.) only on one or more licensed serving cells or carriers to satisfy one or more requirements such as latency or reliability requirement and/or other requirement. For example, in LAA, one embodiment may transmit and/or receive a data radio bearer with QoS requirements and/or a SRB only in PCell or licensed carriers. In another embodiment, for 5G, a radio bearer with one or more requirements such as latency/reliability and/other requirement may be mapped on only one or more 5G RAT serving cells or carriers to satisfy one or more of the requirements. For example, in the case of 5G, the one or more bearers may only be transmitted on 5G RAT carriers. 
     Another embodiment may configure radio resource control signaling. For example, for one or more legacy/reliability sensitive bearers where the restriction(s) are to be applied, the RRC signaling may be configured to comprise configuration information associated with the one or more restrictions, e.g., information element (IE) ul-DataCellList. For example, one embodiment may modify 3GPP specification, e.g., TS 36.331, to include the configuration information, ul-DataCellList. Table 1 shows an embodiment of the configuration information that may be added to the specification. 
     
       
         
           
               
               
               
               
             
               
                 TABLE 1 
               
               
                   
               
             
            
               
                 DRB-ToAddMod ::=  SEQUENCE { 
                   
                   
                   
               
               
                   eps-BearerIdentity 
                 INTEGER (0..15) 
                 OPTIONAL, 
                 -- Cond DRB-Setup 
               
               
                   drb-Identity 
                 DRB-Identity, 
               
               
                   pdcp-Config 
                 PDCP-Config 
                 OPTIONAL, 
                 -- Cond PDCP 
               
               
                   rlc-Config 
                 RLC-Config 
                 OPTIONAL, 
                 --Cond SetupM 
               
               
                   logicalChannelIdentity 
                 INTEGER (3..10) 
                 OPTIONAL, 
                 -- Cond DRB-Setup 
               
               
                   logicalChannelConfig 
                 LogicalChannelConfig 
                 OPTIONAL, 
                 -- Cond SetupM 
               
               
                   ..., 
               
            
           
           
               
               
               
            
               
                   [[ drb-TypeChange-r12 
                     ENUMERATED (toMCG)  OPTIONAL, 
                   -- Cond ToMCG 
               
            
           
           
               
               
               
               
            
               
                   rlc-Config-v12xy 
                 RLC-Config-v12xy 
                 OPTIONAL 
                 -- Cond Setup 
               
               
                   ]] 
               
            
           
           
               
               
            
               
                   [[ ul-DataCellList-r13 (SIZE (1..8)) OF ServCellIndex-r10 
                 OPTIONAL, 
               
               
                 } 
               
               
                  ul-DataCellList 
               
               
                  Indicates the list of serving cell indicies where the bearer can be transmitted. 
               
               
                   
               
            
           
         
       
     
     The IE ul-DataCellList may list one or more indices of the one or more serving cells on which the legacy/reliability sensitive bearers can be transmitted/received. While Table 1 illustrates an embodiment that may use ul-DataCellList, some embodiments may use other configuration information relating to the restriction(s) that delay/reliability sensitive bearers are to be transmitted/received only on a subset of serving cells or radio carriers. In some embodiments, pdcp-Config and/or LogicalChannelConfig and/or other RRC signaling may comprise the list of one or more indices of the one or more serving cells on which the legacy/reliability sensitive bearers can be transmitted/received. 
     Referring to  FIG. 1 , eNB  110  may comprise one or more of a processor module  116 , a transmitter module  112 , a receiver module  114  and one or more antennas  118 . The eNB  110  may optionally comprise other hardware components and/or software components, e.g., a memory, a storage, an input module, an output module, one or more radio modules and/or one or more digital modules, and/or other components. Transmitter module  112  may be configured to transmit signals to UE  120  via one or more antennas  118 . Receiver module  114  may be configured to receive signals from UE  120  via one or more antennas  118 . 
     Processor module  116  may be coupled with transmitter module  112  and receiver module  114 . In some embodiments, processor module  116  may control one or more functionalities of eNB  110  and/or control one or more communications performed by eNB  110 . In some demonstrative embodiments, processor module  116  may execute instructions of software and/or firmware, e.g., of an operating system (OS) of eNB  110  and/or of one or more applications. Processor module  116  may comprise or may be implemented using suitable circuitry, e.g., controller circuitry, scheduler circuitry, processor circuitry, memory circuitry, and/or any other circuitry, which may be configured to perform at least part of the functionality of processor module  116 . In some embodiments, one or more functionalities of processor module  116  may be implemented by logic, which may be executed by a machine and/or one or more processors. 
     In some demonstrative embodiments, processor module  116  may comprise an identifying module  115  and a configuration module  117 . Identifying module  115  may be configured to identify or obtain configuration information for a radio bearer that a restriction may be applied. In some embodiments, examples of the radio bearer that has the restriction may comprise, e.g., delay/reliability sensitive bearers such as voice, VoIP, real time gaming, or SRB and/or other bearers that may be delay/legacy sensitive and/or require higher reliability. The transmitter module  112  and the receiver module  114  may be configured to transmit and/or receive the restricted radio bear to or from the subset of serving cells based on the configuration information, respectively. 
     The transmitter module  112  may be configured to transmit the configuration information to UE  120 . In some embodiments, the configuration may comprise information on the restriction that the radio bearer can be transmitted/received via only a subset of one or more serving cells of eNB  110 . For example, the configuration information may comprise an RRC signal, e.g., ul-DataCellList, that may indicate a list of one or more serving cell indices for transmission/reception of the restricted radio bearer. In some embodiments, the configuration information may comprise other information relating to the restriction, e.g., a list of one or more licensed radio carrier indices on which the radio bearer can be transmitted/received and/or a list of one or more 5G RAT serving cell/carrier indices. The transmitter module  112  may be configured to transmit the configuration information to UE  120  via, e.g., RRC signaling. 
     In some embodiments, configuration module  117  may be configured to configure UE&#39;s switching (e.g.,  920  of  FIG. 9 ) of transmission and/or reception of a radio bear to/from a subset of one or more serving cells of eNB  110 . In some embodiments, configuration module  117  may be configured to configure the switching performed by UE  120  via RRC signaling. In some embodiments, configuration module  117  may be configured to configure the switching performed by UE  120  via MAC CE signaling. 
     For example, configuration module  117  may be configured to reconfigure media access control (MAC) carrier information and/or physical layer (PHY) carrier information for the radio bearer with the restriction, e.g., based on the configuration information such as the list of one or more serving cell indices on which the radio bearer can be transmitted/received or other configuration information relating to the restriction. The transmitter module  112  may be configured to transmit reconfigured MAC carrier information and/or PHY carrier information to UE  120  via RRC signaling. In some embodiments, eNB  110  may include, e.g., via the configuration module  117 , the received MAC carrier information and/or PHY carrier information in the restricted radio bearer. Transmitter module  112  may be configured to transmit the MAC carrier information and/or the PHY carrier information to UE  120  via RRC signaling. 
     In some embodiments, configuration module  117  may be configured to configure UE  120 &#39;s switching of transmission and/or reception of the radio bear to/from a subset of serving cells or radio carriers of eNB  110  via MAC CE signaling. Configuration module  117  may be configured to configure MAC information and/or PHY information for all serving cells of eNB  110 . For example, configuration module  117  may configure MAC information and/or PHY information to indicate only the subset of serving cells that can be used for data transmission and/or reception, e.g., based on configuration information, e.g., ul-DataCellList. For example, the data transmission/reception may comprise transmission/reception of one or more delay/reliability sensitive radio bearers that a restriction may be applied. Transmission/reception of the delay/reliability sensitive radio bearers may be restricted to the subset of serving cells indicated by MAC information and/or PHY information. Transmitter module  112  may be configured to transmit the MAC information and/or PHY information to UE  120  via, e.g., RRC signaling and/or MAC control element (CE) signaling. 
     Referring to  FIG. 1 , in some demonstrative embodiments, UE  120  may comprise a processor module  126 , a transmitter module  122 , a receiver module  124  and one or more antennas  128 . UE  120  may comprise other hardware components and/or software components, e.g., a memory, a storage, an input unit, an output unit and/or any other components. Transmitter module  122  may transmit signals to eNB  110  via one or more antennas  128 . Receiver module  124  may receive signals from eNB  110  via one or more antennas  128 . 
     In some embodiments, processor module  126  may be coupled to receiver module  124  and transmitter module  122 . In some embodiments, processor module  126  may control one or more functionalities of UE  120  and/or control one or more communications performed by UE  120 . In some demonstrative embodiments, processor module  126  may execute instructions of software and/or firmware, e.g., of an operating system (OS) of UE  120  and/or of one or more applications. Processor module  126  may comprise or may be implemented using suitable circuitry, e.g., controller circuitry, scheduler circuitry, processor circuitry, memory circuitry, and/or any other circuitry, which may be configured to perform at least part of the functionality of processor module  12 . In some embodiments, one or more functionalities of processor module  126  may be implemented by logic, which may be executed by a machine and/or one or more processors. 
     In some embodiments, processor module  126  may comprise a central processing unit (CPU), a digital signal processor (DSP), a graphic processing unit (GPU), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, circuitry, a baseband circuitry, a radio frequency (RF) circuitry, a logic unit, an integrated circuit (IC), an application-specific IC (ASIC), or any other suitable multi-purpose or specific processor or controller and/or any combination thereof. 
     In some embodiments, processor module  126  may comprise a switching module  127  and a detecting module  129 . Receiver module  124  may be configured to receive configuration information from eNB  110 , e.g., via RRC signaling. For example, the configuration information may comprise configuration information on a restriction that a radio bearer is to be transmitted/received on only a subset of one or more serving cells of eNB  110 . The configuration information may comprise a RRC signal, e.g., ul-DataCellList, that may indicate the list of the subset of serving cell indices where the restricted radio bearer can be transmitted/received. Transmitter module  122  and receiver module  124  may be configured to transmit and/or receive the restricted radio bearer to or from eNB  110  based on the configuration information, respectively. 
     In some embodiments, receiver module  124  may further be configured to receive RRC signaling and/or MAC CE signaling from eNB  110 . Switching module  127  may be configured to switch transmission and/or reception of the radio bearer where the restriction applies to or from only the subset of one or more serving cells of eNB  110  based on the RRC signaling and/or the MAC CE signaling. The RRC signaling may comprise MAC carrier information and/or PHY carrier information that may comprise a list of one or more serving cell indices associated with the subset of serving cells for the restricted radio bearer. The MAC CE signaling may comprise MAC information and/or PHY information to indicate from all the serving cells the subset of serving cells of eNB  110  that can be used to transmit and/or receive the restricted radio bearer. Switching module  127  may be configured to switch transmission and/or reception of the restricted radio bearer to or from the subset of serving cells indicated by RRC signaling and/or MAC CE signaling received from eNB  110 . 
     In some embodiments, receiver module  124  may be configured to receive downlink signaling, e.g., for a physical downlink control channel from all activate serving cells of eNB  110 . Switching module  127  may be configured to switch transmission and/or reception of the radio bearer where the restriction applies to or from a serving cell, from which the data or scheduling grant is received first via the receiver module  124 . 
     In some embodiments, radio link quality detecting module  129  may be configured to detect or check a radio link quality of one or more serving cells or component carriers of eNB  110 . Switching module  127  may be configured to switch transmission and/or reception of the radio bearer where the restriction applies to or from a serving cell based on the detected radio link quality. 
     Transmitter module  112  may comprise, or may be coupled with one or more antennas  118  of eNB  110  to communicate wirelessly with other components of the wireless communication network  100 , e.g., UE  120 . Transmitter module  122  may comprise, or may be coupled with one or more antennas  128  of UE  120  to communicate wirelessly with other components of the wireless communication network  100 , e.g., eNB  110 . In some embodiments, transmitter module  112  and/or transmitter module  122  may each comprise one or more transmitters, one or more receivers, one or more transmitter modules, one or more receiver modules and/or one or more transceivers that may be able to send and/or receive wireless communication signals, radio frequency (RF) signals, frames, blocks, transmission streams, packets, messages, data items, data, information and/or any other signals. 
     In some demonstrative embodiments, transmitter module  122  may support a WLAN communication for UE  120 . For example, transmitter module  122  may perform functionality of one or more stations, e.g., WiFi stations, WLAN stations, and/or millimeter Wave (mmWave) stations or the like. 
     In some demonstrative embodiments, the antennas  118  and/or the antennas  128  may comprise any type of antennas suitable to transmit and/or receive wireless communication signals, RF signals, blocks, frames, transmission streams, packets, messages, data items and/or data. For example, the antennas  118  and/or the antennas  128  may comprise any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. In some embodiments, the antennas  118  and/or the antennas  128  may implement transmit and/or receive functionalities using separate transmit and/or receive antenna elements. In some embodiments, the antennas  118  and/or the antennas  128  may implement transmit and/or receive functionalities using common and/or integrated transmit/receive elements. The antenna may comprise, for example, a phased array antenna, a single element antenna, a dipole antenna, a set of switched beam antennas, and/or the like. 
     In some demonstrative embodiments, UE  120  may comprise two antennas, e.g., antennas  128   a  and  128   b , or any other number of antennas, e.g., one or more than two antennas. In some demonstrative embodiments, eNB  110  may comprise two antennas, e.g., antennas  118   a  and  118   b , or any other number of antennas, e.g., one or more than two antennas. 
     While  FIG. 1  illustrates some components of eNB  110 , in some embodiments, the eNB  110  may optionally comprise other suitable hardware, software and/or firmware components that may be interconnected or operably associated with one or more components in the eNB  110 . While  FIG. 1  illustrates some components of UE  120 , in some embodiments, UE  120  may optionally comprise other suitable hardware, software and/or firmware components that may be interconnected or operably associated with one or more components in UE  120 . For example, eNB  110  and/or UE  120  may comprise one or more radio modules (not shown) to modulate and/or demodulate signals transmitted or received on an air interface, and one or more digital modules (not shown) to process signals transmitted and received on the air interface. 
     In some demonstrative embodiments, eNB  110  and/or UE  120  may comprise one or more input units (not shown) and/or one or more output units (not shown). For example, one or more input units may comprise a keyboard, a keypad, a mouse, a touch-screen, a touch-pad, a track-ball, a stylus, a microphone, or any other pointing/input unit or device. For example, one or more output units may comprise a monitor, a screen, a touch-screen, a flat panel display, a Cathode Ray Tube (CRT) display unit, a Liquid Crystal Display (LCD) display unit, a plasma display unit, one or more audio speakers or earphones, or any other output unit or device. 
     In some demonstrative embodiments, UE  120  may comprise, for example, a mobile computer, a mobile device, a station, a laptop computing device, a notebook computing device, a netbook, a tablet computing device, an ultrabook computing device, a handheld computing device, a handheld device, a storage device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a mobile phone, a cellular telephone, a PCS device, a mobile or portable GPS device, a DVB device, a wearable device a relatively small computing device, a non-desktop computer, a “carry small live large” (CSLL) device, an ultra mobile device (UMD), an ultra mobile PC (UMPC), a mobile internet device (MID), an “Origami” device or computing device, a video device, an audio device, an audio/video (A/V) device, a gaming device, a media player, a smartphone, a mobile station (MS), a mobile wireless device, a mobile communication device, a handset, a cellular phone, a mobile phone, a personal computer (PC), a handheld mobile device, an universal integrated circuit card (UICC), a customer premise equipment (CPE), or other consumer electronics such as digital cameras and the like, personal computing accessories and existing and future arising wireless mobile devices which may be related in nature and to which the principles of the embodiments could be suitably applied. 
       FIG. 2  illustrates an electronic device circuitry  200  according to an embodiment. The electronic device circuitry  200  may be eNB circuitry, UE circuitry, or other type of circuitry in accordance with various embodiments. For example, the electronic device circuitry  200  may communicate using one or more wireless communication standards such as 3GPP LTE, 3GPP LTE-A, 3GPP LTE-U, WiMAX, HSPA, Bluetooth, WiFi, 5G standards or other wireless standards in various embodiments. The electronic device circuitry  200  may communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a wireless wide area network (WWAN) or other network in various embodiments. 
     In various embodiments, the electronic device circuitry  200  may be, or may be incorporated into or otherwise a part of, an eNB, a UE, or other type of electronic device. The electronic device circuitry  200  may comprise radio transmit circuitry  212  and receive circuitry  216  coupled to control circuitry  214 . In some embodiments, the transmit circuitry  212  and/or receive circuitry  216  may be elements or modules of a transceiver circuitry. The electronic device circuitry  200  may be coupled with one or more plurality of antenna elements of one or more antennas  218 . The electronic device circuitry  200  and/or the components of the electronic device circuitry  200  may be configured to perform operations similar to those described herein. 
     In some demonstrative embodiments, the electronic device circuitry  200  may be part of or comprise an application specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry  200  may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. 
       FIG. 3  illustrates an example of a layer structure in radio protocol architecture  300 , e.g., of an E-UTRAN. In some demonstrative embodiments, the layer structure  300  may comprise one or more radio protocol sublayers, e.g., a medium access control (MAC) sublayer  330 , a radio link control (RLC) sublayer  320  and a packet data convergence protocol (PDCP) sublayer  310 . In some demonstrative embodiments, the MAC sublayer  330 , RLC sublayer  320  and the PDCP sublayer  310  may correspond to Layer 2 sublayers. 
     In some demonstrative embodiments, the MAC sublayer  330  may perform one or more services and/or functions, e.g., hybrid automatic report request (HARD) ( 334 ). In some demonstrative embodiments, the MAC sublayer  330  may perform multiplexing ( 332 ) of one or more logical channels  370  (e.g., radio bearers  360 ) on the same transport channel  380  (e.g., transport block). In some other embodiments, the MAC sublayer  330  may further perform demultiplexing of MAC service data units belonging to one or more logical channels  370  from transport blocks delivered from a physical (PHY) layer (not shown) on one or more transport channels  380 . In some other embodiments, the MAC sublayer  330  may perform mapping (not shown) between logical channels  370  and transport channel  380 . 
     In some demonstrative embodiments, RLC sublayer  320  may perform one or more services and/or functions, e.g., segmentation of RLC service data units and/or automatic repeat request (ARQ) ( 322 ). The PDCP sublayer  310  may perform one or more services and/or functions, e.g., robust header compression (ROHC) ( 312 ) and/or security functions ( 314 ). While  FIG. 3  illustrates MAC layer  330 , RLC layer  320  and DPCP layer  310  may perform some services and/or functions, some embodiments may comprise one or more other services or functions. 
     Referring to  FIG. 3 , in some demonstrative embodiments, in carrier aggregation (CA), two or more component carriers (CCs) may be aggregated to support a wider transmission bandwidth. In one embodiment, a CC may correspond to a serving cell. For example, UE  120  may be configured to simultaneously receive or transmit on one or more of the CCs. In some embodiments, the number of downlink CCs that can be configured may depend on downlink aggregation capability of UE  120  and the number of uplink CCs that can be configured may depend on uplink aggregation capability of UE  120 . 
       FIG. 3  illustrates an example of a bearer mapping in carrier aggregation. In some demonstrative embodiments, a radio bearer, e.g.,  360 , may be mapped to one or more of all serving cells, e.g., PCell(s) and SCell(s) or the set of CCs  340   1  to  340   X , wherein X may represent a number of CCs in the transmission bandwidth. In some demonstrative embodiments, for one or more legacy sensitive and/or reliability sensitive bearers, UE  120  may be configured to restrict the one or more legacy sensitive and/or reliability sensitive bearers be transmitted/received only on one or more PCell(s) and/or licensed CCs corresponding to the PCell(s). For example, the one or more bearers may comprise SRB, VoIP, real time gaming or any other bearer that has legacy and/or reliability requirement(s). In some other demonstrative embodiments, for 5G, UE  120  may be configured to transmit/receive the one or more legacy sensitive and/or reliability sensitive bearers in 5G RAT only. 
     In some demonstrative embodiments, logical channel prioritization (LCP) procedure in MAC layer  330  may be modified to implement the one or more restriction in radio protocol. In one embodiment, in response to performing LCP, e.g., by the LCP module  125 , UE  120  may only transmit data associated with a bearer to one or more serving cells based on RRC configuration, e.g., of RRC signaling. For example, in response to receiving an uplink grant from a serving cell, if the restriction related information, e.g., the ul-DataCellList field, is signaled for a logical channel, UE  120  may determine, by LCP module  125 , if the serving cell transmitting the uplink grant is in the ul-DataCellList. In response to determining that the serving cell transmitting the uplink grant is not in the ul-DataCellList, UE  120  may not consider the logical channel during LCP procedure. Contrarily, in response to determining that the serving cell that transmits the uplink grant is in the ul-DataCellList, UE  120  may transmit the bearer via the serving cell. In some demonstrative embodiments, the eNB  110  may transmit the restriction related information to UE  120 , e.g., via RRC signaling. 
       FIG. 4  illustrates an example of a layer structure  400  of radio protocol architecture with carrier aggregation.  FIG. 4  illustrates an embodiment of a switch  450 , e.g., among a set of one or more component carriers (CCs)  440   1  to  440   X , wherein X may represent a number of CCs in a transmission bandwidth. 
     In some demonstrative embodiments, an eNB, e.g.,  110 , may configure the switch  450  via RRC signaling. For example, eNB  110  may reconfigure MAC/PHY carrier information for a radio bearer. For a legacy/reliability sensitive bearer where a restriction applies, eNB  110  may configure the MAC sublayer carrier information and/or the physical layer carrier information to restrict transmission/reception of the legacy/reliability sensitive bearer only on a subset of one or more serving cells or CCs. The eNB  110  may configure the MAC sublayer carrier information and/or the physical layer carrier information to comprise indices of the subset of one or more serving cells based on, e.g., ul-DataCellList, and other configuration information relating to the restriction. In some embodiments, eNB  110  may transmit the MAC sublayer carrier information and/or the physical layer (PHY) carrier information to UE  120 , e.g., via RRC signaling. The legacy/reliability sensitive bearer may comprise the list of serving cell indices???. UE  120  may switch transmission/reception of the legacy/reliability sensitive bearer to the subset of one or more serving cells or CCs based on the received MAC sublayer carrier information and/or PHY carrier information. 
     As shown in  FIG. 4 , RLC sublayer  420  and/or PDCP sublayer  410  are still in eNB  110  in the example of MAC carrier information and/or the PHY carrier information. In some demonstrative embodiments, eNB  110  may not re-establish RLC sublayer  420  and/or PDCP  410  with the carrier switching. The MAC sublayer  430  may perform one or more functions or services, e.g., unicast scheduling and/or priority handling ( 436 ), multiplexing and/or de-multiplexing, e.g., MAC service data units ( 432 ) and/or HARQ ( 434 ). 
     In some other demonstrative embodiments, eNB  110  may configure the switch  450  via MAC CEsignaling. For example, eNB  110  may configure MAC information and/or PHY information for all serving cells. In some embodiments, eNB  110  may configure the MAC information and/or PHY information to indicate if a corresponding serving cell can be used for data transmission and/or reception. For example, the MAC information and/or PHY information may be configured to indicate if a corresponding serving cell is to be used for transmission/reception of a legacy/reliability sensitive bearer. UE  120  may use the one or more serving cells indicated by the MAC information and/or the PHY information for data transmission and/or reception. In some embodiments, UE  120  may switch transmission and/or reception of the legacy/reliability sensitive bearer based on the MAC information and/or the PHY information received from eNB  110  via, e.g., MAC CE signaling. For example, UE  120  may switch to only one or more serving cells indicated by the MAC information and/or the PHY information to transmit/receive a legacy/reliability sensitive bearer to/from the serving cell. 
     In some demonstrative embodiments, RLC sublayer  420  may have different RLC values (e.g., RLC reorder timer) depending on respective serving cells or carriers indicated by the MAC information and/or the PHY information such as licensed carriers, unlicensed carriers, LTE carriers or 5G RAT carriers, etc. In some embodiments, PDCP sublayer  410  may have different PDCP values depending on corresponding serving cells indicated by the MAC information and/or the PHY information such as licensed carriers, unlicensed carriers, LTE carriers or 5G RAT carriers, etc. One embodiment may apply an RLC value and/or a PDCP value automatically based on an actual serving cell that is used for data transmission/reception. 
     In some other demonstrative embodiments, UE  120  may perform the switching  450  implicitly based on data reception by UE  120 . For example, UE  120  may receive downlink signaling for a physical downlink control channel (PDCCH) on all activated serving cells of eNB  110 . UE  120  may perform a carrier switching based on data/scheduling grant that UE  120  receives first. For example, in response to receiving a downlink/uplink scheduling grant from a 5G RAT serving cell or carrier first, UE  120  may map a radio bearer corresponding to the downlink/uplink scheduling grant to the 5G RAT carrier or serving cell. In some demonstrative embodiments, a RLC value may be automatically applied based on the actual serving cell that is used to transmit and/or receive a radio bear. For example, RLC value (e.g., RLC reorder timer) may depend on whether the actual serving cell is a licensed carrier, an unlicensed carrier, an LTE carrier or a 5G RAT carrier. In another embodiment, a PDCP value may depend on the actual serving cell, e.g., a licensed carrier, an unlicensed carrier, an LTE carrier, or a 5G RAT carrier. 
     In some other demonstrative embodiments, UE  120  may perform a carrier switching  450  based on a radio link quality. For example, UE  120  may detect a radio link quality of a carrier that is to be used to transmit and/or receive a radio bearer. In response to detecting a radio link problem (e.g., a radio link failure) on the carrier, e.g., an unlicensed carrier or a 5G RAT carrier, UE  120  may switch to an LTE licensed carrier or an LTE carrier for the transmitting and/or receiving of the radio bearer. In some other embodiments, in response to detecting a radio link failure on a carrier or serving cell that is to be used to transmit and/or receive a legacy/reliability sensitive radio bear, UE  120  may switch to a serving cell that may have an improved radio link quality, e.g., an LTE licensed carrier or an LTE carrier of eNB  110 , e.g., in the subset of serving cells or carriers for the restricted radio bearers. 
       FIG. 5  illustrates an example of a method  500  according to an embodiment. In some embodiments, the method  500  may be performed by eNB  110 , e.g., processor module  116 , and/or electronic device circuitry  200 , e.g., control circuitry  214 . In some demonstrative embodiments, eNB  110  may be configured with carrier aggregation in a long term evolution (LTE), LTE-advanced (LTE-A), and/or 5G RAT. Referring to  FIG. 5 , eNB  110  may identify or obtain configuration information for a radio bearer that a restriction may apply ( 510 ). Examples of the radio bearer that the restriction applies may comprise delay/reliability sensitive bearers, e.g., VoIP, SRB, real time gaming and/or other bearers that may require higher reliability. The configuration information may comprise information on the restriction that UE  120  is to transmit and/or receive a radio bearer via only a subset of one or more serving cells of a wireless network. In some demonstrative embodiments, the configuration information may comprise an information element, e.g., ul-DatacellList, that may list the subset of serving cell indicies where the radio bearer can be transmitted. The eNB  110  may transmit the configuration information to UE  120  ( 520 ) via, e.g., RRC signaling. In some embodiments, eNB  110  may transmit and/or receive the radio bearer to/from one or more serving cells in the subset based on the configuration information. 
       FIG. 6  illustrates an example of a method  600  according to an embodiment. In some embodiments, the method  600  may be performed by UE  120 , e.g., processor modules  126 , and/or electronic device circuitry  200 , e.g., control circuitry  214 . In some demonstrative embodiments, UE  120  may be configured with carrier aggregation in a long term evolution (LTE), LTE-advanced (LTE-A), and/or 5G RAT or other future RAT. Referring to  FIG. 6 , UE  120  may receive from eNB  110  configuration information for a radio bearer that a restriction may apply ( 610 ). UE  120  may receive the configuration information from eNB  110 . Examples of the radio bearer that the restriction applies may comprise delay/reliability sensitive bearers, e.g., VoIP, SRB, real time gaming and/or any other bearers that may require higher reliability. For example, the configuration information may comprise restriction information, e.g., ul-DatacellList that may indicate the list of serving cell indicies where the radio bearer can be transmitted. UE  120  may receive the configuration information via, e.g., RRC signaling. UE  120  may transmit and/or receive the radio bearer to/from one or more serving cells in the subset based on the configuration information (block  620 ). 
       FIG. 7  illustrates an example of a method  700  according to an embodiment. In some demonstrative embodiments, the method  700  may be used by UE  120 , e.g., processor module  126 , and/or electronic device circuitry  200 , e.g., control circuitry  214 . Referring to  FIG. 7 , UE  120  may receive an uplink grant from a serving cell of eNB  110  ( 710 ). UE  120  may receive from eNB  110  configuration information for a logical channel associated with the serving cell ( 720 ). In some embodiments, the configuration information may comprise information on a restriction that a radio bearer is to be transmitted and/or received only on a subset of one or more serving cells. For example, the restriction information may comprise a list of one or more serving cell indices where a radio bearer can be transmitted/received. UE  120  may receive the restriction information, e.g., ul-DataCellList, via RRC signaling. Examples of the radio bearer that the restriction applies may comprise delay/reliability sensitive bearers, e.g., VoIP, SRB, real time gaming and/or other bearers that may be legacy sensitive or require higher reliability. 
     Referring to  FIG. 7 , UE  120  may perform a logical channel prioritization (LCP) based on the configuration information ( 730 ). For example, UE  120  may perform the restriction based on the configuration information in response to performing the logical channel prioritization. For example, UE  120  may determine if the serving cell that transmits the uplink grant is in the list of serving cells indices in the restriction information, e.g., ul-DataCellList. UE  120  may not consider the logical channel associated with the serving cell in the LCP procedure in response to determining that the serving cell is not in ul-DataCellList. On the contrary, in response to determining that the serving cell is in ul-DataCellList, UE  120  may prioritize the logical channel and/or may transmit and/or receive the radio bearer to/from the serving cell and/or one or more other serving cells in the ul-DataCellList based on the configuration information ( 740 ). 
       FIG. 8  illustrates an example of a method  800  according to an embodiment. In some demonstrative embodiments, method  800  may be performed by eNB  110 , e.g., processor module  116 , and/or electronic device circuitry  200 , e.g., control circuitry  214 . Referring to  FIG. 8 , eNB  110  may configure a switch, e.g., by UE  120 , of transmission/reception of a radio bearer to or from a subset of one or more serving cells of eNB  110  ( 810 ). Examples of the radio bearer may comprise delay/reliability sensitive bearers, e.g., VoIP, SRB, real time gaming and/or other bearers that may be legacy sensitive or require higher reliability. In some demonstrative embodiments, eNB  110  may configure the switch of the transmission/reception of the radio bearer to a subset of one or more serving cells via RRC signaling and/or MAC CE signaling ( 810 ). The eNB  110  may transmit to UE  120  information on the switch of the transmission/reception of the radio bearer via RRC signaling and/or MAC CE signaling ( 820 ). 
     Referring to  FIG. 8 , in some demonstrative embodiments, eNB  110  may reconfigure carrier information of a MAC sublayer and/or a PHY layer for the radio bearer. The MAC/PHY carrier information may indicate one or more carriers or serving cells that can be used to transmit and/or receive the radio bearer. For example, eNB  110  may indicate in the MAC/PHY carrier information a list of serving cell indices that can be used to transmit/receive the radio bearer. The list of serving cell indices may be included in the radio bearer. The eNB  110  may transmit to UE  120  the MAC/PHY carrier information via RRC signaling ( 820 ). Referring to  FIGS. 4 and 8 , RLC sublayer  420  and/or PDCP layer  410  may still be in the same eNB  110  in response to the reconfiguration of the MAC/PHY carrier information. The eNB  110  may not re-establish a RLC sublayer and/or a PDCP layer with the switch. 
     Referring to  FIG. 8 , in some other demonstrative embodiments, eNB  110  may configure MAC/PHY information for all serving cells of eNB  110 . For example, eNB  110  may indicate in the MAC/PHY information a list of serving cell indices that can be used to transmit delay/reliability sensitive radio bearer. The eNB  110  may transmit to UE  120  the MAC/PHY information via MAC CE signaling ( 820 ). Referring to  FIGS. 4 and 8 , RLC sublayer  420  may have one or more different RLC values (e.g., RLC reorder timer) depending on a serving cell or carrier, e.g., licensed carriers, unlicensed carriers, LTE carriers or 5G RAT carriers, etc., that may be used to transmit and/or receive a radio bearer. In some other embodiments, PDCP layer  410  may have one or more different PDCP values depending on respective serving cell or carrier that is used, e.g., licensed carriers, unlicensed carriers, LTE carriers or 5G RAT carriers, etc. In some demonstrative embodiments, an RLC value and/or a PDCP value may be applied automatically based on the actual serving cell that is used for data transmission/reception. 
       FIG. 9  illustrates an example of a method  900  according to an embodiment. In some demonstrative embodiments, method  900  may be performed by UE  120 , e.g., processor module  126 , and/or electronic device circuitry  200 , e.g., control circuitry  214 . Referring to  FIG. 9 , in some demonstrative embodiments, UE  120  may receive from eNB  110  information on a switch of transmission/reception of a radio bearer to or from a subset of one or more serving cells of eNB  110  ( 910 ). Examples of the radio bearer may comprise delay/reliability sensitive bearers, e.g., VoIP, SRB, real time gaming and/or other bearers that may be legacy sensitive or require higher reliability. 
     In some embodiments, UE  120  may receive the indication that may comprise MAC/PHY carrier information via, e.g., RRC signaling. The MAC/PHY carrier information may comprise a list of serving cell indices that can be used to transmit/receive the radio bearer. In some other embodiments, UE  120  may receive the indication that may comprise MAC/PHY information via, e.g., MAC CE signaling. The MAC/PHY information may comprise a list of serving cell indices that can be used to transmit/receive the radio bearer. For example, UE  120  may use the one or more serving cells indicated by the RRC signaling and/or MAC CE signaling to transmit/receive delay/reliability sensitive radio bearers. 
     Referring to  FIG. 9 , in response to receiving the indication on the switch, UE  120  may switch the transmission and/or reception of the radio bearer based on the information ( 920 ). For example, UE  120  may switch the transmission and/or reception of the radio bearer to or from a subset of one or more serving cells indicated by the MAC/PHY carrier information. In another embodiment, UE  120  may switch the transmission and/or reception of the radio bearer to or from a subset of one or more serving cells indicated by the MAC/PHY information. 
       FIG. 10  illustrates an example of a method  1000  according to an embodiment. In some demonstrative embodiments, method  1000  may be performed by UE  120 , e.g., processor module  126 , and/or electronic device circuitry  200 , e.g., control circuitry  214 . Referring to  FIG. 10 , UE  120  may receive from eNB  110  downlink signaling, e.g., one or more data/scheduling grants, for a physical downlink control channel (PDCCH) on one or more activated serving cells or carriers ( 1010 ). Based on from which serving cell data/scheduling grant is received first, UE  120  may implicitly perform a switch of transmission and/or reception of a radio bearer to that serving cell. For example, if the data/scheduling grant, e.g., a downlink/uplink scheduling grant, that UE  120  receives first is from a 5G RAT carrier or a 5G RAT serving cell, UE  120  may map transmission and/or reception of a radio bearer that a restriction applies to the 5G RAT carrier or serving cell. In another embodiment, if the data/scheduling grant that UE  120  receives first is from a licensed serving cell or carrier, UE  120  may switch transmission and/or reception of the restricted radio bearer to/from the licensed serving cell or carrier. 
     Referring to  FIGS. 4 and 10 , RLC sublayer  420  may have one or more different RLC values (e.g., RLC reorder timer) depending on a serving cell or carrier, e.g., licensed carriers, unlicensed carriers, LTE carriers or 5G RAT carriers, etc., that may be used to transmit and/or receive a radio bearer. In some other embodiments, PDCP layer  410  may have one or more different PDCP values depending on respective serving cell or carrier that is used, e.g., licensed carriers, unlicensed carriers, LTE carriers or 5G RAT carriers, etc. In some demonstrative embodiments, an RLC value and/or a PDCP value may be applied automatically based on the actual serving cell that is used for the data transmission/reception. 
       FIG. 11  illustrates an example of a method  1100  according to an embodiment. In some embodiments, the method may be performed by UE  120 , e.g., processor module  126 , and/or electronic device circuitry  200 , e.g., control circuitry  214 . Referring to  FIG. 11 , UE  120  may detect radio link quality of a serving cell or carrier that may be used to transmit and/or receive a radio bearer that a restriction may apply ( 1110 ). Examples of the radio bearer may comprise voice, real time gaming, or signaling radio bearer (SRB) and other bearers that may have latency and/or reliability requirements. In some demonstrative embodiments, UE  120  may detect the radio link quality of an unlicensed carrier and/or a 5G RAT carrier. 
     In response to detecting a radio link failure of the unlicensed carrier and/or the 5G RAT carrier, UE  120  may perform a switch of transmission and/or reception of the radio bearer to a serving cell or carrier that may have a better radio link quality ( 1120 ). UE  120  may implicitly perform the switch based on a radio link quality of a serving cell or carrier that may be used to transmit and/or receive the radio bearer. For example, UE  120  may switch transmission and/or reception of the radio bearer to a licensed serving cell or carrier or an LTE carrier. In some demonstrative embodiments, an RLC value and/or a PDCP value may be applied automatically based on the actual serving cell that is used for the data transmission/reception. 
     Embodiments described herein may be implemented into a system that may use any suitably configured hardware, software and/or firmware. In some demonstrative embodiments,  FIG. 12  illustrates an example system  1200  that may comprise a radio frequency (RF) circuitry  1230 , a baseband circuitry  1220 , an application circuitry  1210 , memory/storage  1240 , a display  1202 , a camera  1204 , a sensor  1206 , and an input/output (I/O) interface  1208  that may be coupled with each other at least as shown in  FIG. 12 . 
     The application circuitry  1210  may comprise circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may comprise any combination of general-purpose processors and/or dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with one or more memory and/or one or more storage, e.g.,  1240  and may execute one or more instructions stored in the memory/storage  1240  to enable various applications and/or operating systems running on the system  1200 . 
     The baseband circuitry  1220  may comprise circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may comprise a baseband processor. The baseband circuitry  1220  may handle one or more radio control functions that may enable communication with one or more radio networks, e.g., via RF circuitry  1230 . The one or more radio control functions may comprise, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, etc. In some embodiments, the baseband circuitry  1220  may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry  1220  may support communication with an evolved universal terrestrial radio access network (EUTRAN) 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  1220  may be configured to support radio communications of more than one wireless protocol and may be referred to as multi-mode baseband circuitry. 
     In various embodiments, baseband circuitry  1220  may comprise circuitry to operate with signals that may not be limited to be in a baseband frequency. For example, in some embodiments, baseband circuitry  1220  may comprise circuitry to operate with signals having an intermediate frequency that may be between a baseband frequency and a radio frequency. 
     RF circuitry  1230  may enable communication with wireless networks, e.g., using modulated electromagnetic radiation through a non-solid medium. In some demonstrative embodiments, the RF circuitry  1230  may comprise switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. In some demonstrative embodiments, RF circuitry  1230  may comprise circuitry to operate with signals that may not be limited to a radio frequency. For example, in some embodiments, RF circuitry  1230  may comprise circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency. 
     In various embodiments, transmit circuitry, control circuitry, and/or receive circuitry discussed or described herein may be embodied in whole or in part in one or more of the RF circuitry  1230 , the baseband circuitry  1220 , and/or the application circuitry  1210 . As used herein, the term “circuitry” may refer to, be part of, or comprise an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. 
     In some embodiments, some or all of the constituent components of the baseband circuitry  1220 , the application circuitry  1210 , and/or memory and/or storage  1240  may be implemented together on a system on a chip (SOC). 
     Memory/storage  1240  may be used to load and store, e.g., data, information, and/or instruction, or the like. Memory/storage  1240  for one embodiment may comprise any combination of suitable volatile memory (e.g., dynamic random access memory (DRAM)) and/or non-volatile memory (e.g., Flash memory). Examples of memory may comprise a random access memory (RAM), a read only memory (ROM), a dynamic RAM (DRAM), a synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units. Examples of storage may comprise a hard disk drive, a floppy disk drive, a Compact Disk (CD) drive, a CD-ROM drive, a DVD drive, or other suitable removable or non-removable storage units. 
     In various embodiments, I/O interface  1208  may comprise one or more user interfaces that may enable user interaction with the system and/or one or more peripheral component interfaces that may enable peripheral component interaction with the system. Examples of user interfaces may comprise, but are not limited to, a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. Examples of peripheral component interfaces may comprise, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power supply interface. 
     In various embodiments, sensor  1206  may comprise one or more sensing devices that may determine environmental conditions and/or location information related to the system. In some embodiments, examples of the sensors may comprise, but are not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit or other sensing device. The positioning unit may also be part of, or interact with, the baseband circuitry and/or RF circuitry to communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite. 
     In various embodiments, examples of the display  1202  may comprise a display, e.g., a liquid crystal display, a touch screen display, etc. 
     In various embodiments, the system may comprise a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, etc. In various embodiments, system may have more or less components, and/or different architectures. 
     Examples 
     Example 1 may comprise a user equipment (UE) configured with carrier aggregation in LTE and/or 5G. The UE may have circuitry to: receive a configuration from an evolved node B (eNB) with the information on the restriction that certain bearers are only transmitted to a subset of serving cells; and transmit/receive the configured bearers to the said eNB according to the configuration information. 
     Example 2 may comprise the circuitry of example 1 or some other example herein, wherein the configuration information is via RRC signaling. 
     Example 3 may comprise the circuitry of example 1 or some other example herein, wherein when UE performs logical channel prioritization, UE performs the restriction according to the said configuration. 
     Example 4 may comprise a user equipment (UE) configured with carrier aggregation in LTE and/or 5G, the UE having circuitry to switch the transmission/reception of certain bearers to/from a subset of serving cells of an evolved node B (eNB). 
     Example 5 may comprise the circuitry of example 1, wherein said eNB configures the switching via RRC signaling. 
     Example 6 may comprise the circuitry of example 1 or some other example herein, wherein said eNB configures the switching via MAC CE signaling. 
     Example 7 may comprise the circuitry of example 1 or some other example herein, wherein said UE performs the switching implicitly by data reception. 
     Example 8 may comprise the circuitry of example 1 or some other example herein, wherein said UE performs the switching implicitly based on radio link quality. 
     Example 9 may comprise a user equipment (UE) comprising: receive circuitry to receive, from an evolved NodeB (eNB), configuration information related to restriction of restricted radio bearers that are only transmitted to a subset of serving cells of a wireless network that uses carrier aggregation; and transmit circuitry coupled with the transmit circuitry, the transmit circuitry to transmit the restricted radio bearers to the eNB based on the configuration information. 
     Example 10 may comprise the UE of example 9 or some other example herein, wherein the receive circuitry is further to receive the restricted radio bearers in accordance with the configuration information. 
     Example 11 may comprise the UE of example 9 or some other example herein, wherein the wireless network is a long term evolution (LTE), LTE-advanced (LTE-A), and/or 5G network. 
     Example 12 may comprise the UE of example 9 or some other example herein, wherein the receive circuitry is to receive the configuration information via one or more radio resource control (RRC) signals. 
     Example 13 may comprise the UE of example 9 or some other example herein, further comprising control circuitry to: perform logical channel prioritization; and perform the restriction in accordance with the configuration information. 
     Example 14 may comprise the UE of example 9 or some other example herein, further comprising control circuitry to switch the transmission/reception of the restricted radio bearers to or from a subset of serving cells of an evolved NodeB (eNB). 
     Example 15 may comprise the UE of example 14 or some other example herein, wherein the receive circuitry is to receive an indication of the switch via one or more radio resource control (RRC) signals and/or medium access control (MAC) signals. 
     Example 16 may comprise the UE of example 14 or some other example herein, wherein the switch is based on data reception and/or radio link quality. 
     Example 17 may comprise a method comprising receiving, by a user equipment (UE) from an evolved NodeB (eNB), configuration information related to restriction of restricted radio bearers that are only transmitted to a subset of serving cells used in carrier aggregation of a long term evolution (LTE), LTE-advanced (LTE-A), and or 5G wireless network; and transmitting and/or receiving, by the UE, the restricted radio bearers to/from eNB based on the configuration information. 
     Example 18 may comprise the method of example 17 or some other example herein, further comprising receiving, by the UE, the configuration information via one or more radio resource control (RRC) signals. 
     Example 19 may comprise the method of example 17 or some other example herein, further comprising performing, by the UE, logical channel prioritization; and performing, by the UE, the restriction in accordance with the configuration information. 
     Example 20 may comprise the method of example 17 or some other example herein, further comprising switching, by the UE, the transmission/reception of the restricted radio bearers to or from a subset of serving cells of an evolved NodeB (eNB). 
     Example 21 may comprise the method of example 20 or some other example herein, further comprising receiving, by the UE, an indication of the switching via one or more radio resource control (RRC) signals and/or medium access control (MAC) signals. 
     Example 22 may comprise the method of example 20 or some other example herein, wherein the switching is based on data reception and/or radio link quality. 
     Example 23 may comprise an evolved NodeB (eNB) comprising: control circuitry to identify configuration information related to restriction of restricted radio bearers that are only transmitted to a subset of serving cells of a wireless network that uses carrier aggregation; and transmit circuitry coupled with the control circuitry, the transmit circuitry to transmit, to a user equipment (UE) an indication of the configuration information; and transmit the restricted radio bearers to the UE based on the configuration information. 
     Example 24 may comprise the eNB of example 23 or some other example herein, further comprising receive circuitry coupled with the transmit circuitry, the receive circuitry to receive the restricted radio bearers in accordance with the configuration information. 
     Example 25 may comprise the eNB of example 23 or some other example herein, wherein the wireless network is a long term evolution (LTE), LTE-advanced (LTE-A), and/or 5G network. 
     Example 26 may comprise the eNB of example 23 or some other example herein, wherein the transmit circuitry is to transmit the indication via one or more radio resource control (RRC) signals. 
     Example 27 may comprise the eNB of example 23 or some other example herein, wherein the transmit circuitry is to transmit an indication of a switch of transmission/reception of the restricted radio bearers to or from a subset of serving cells of eNB. 
     Example 28 may comprise the eNB of example 27 or some other example herein, wherein the transmit circuitry is to transmit the indication of the switch via one or more radio resource control (RRC) signals and/or medium access control (MAC) signals. 
     Example 29 may comprise a method comprising transmitting, by an evolved NodeB (eNB) to a user equipment (UE), an indication of configuration information related to restriction of restricted radio bearers that are only transmitted to a subset of serving cells of a wireless network that uses carrier aggregation; and transmitting, by the eNB, the restricted radio bearers to the UE based on the configuration information. 
     Example 30 may comprise the method of example 29 or some other example herein, further comprising receiving, by the eNB, the restricted radio bearers in accordance with the configuration information. 
     Example 31 may comprise the method of example 29 or some other example herein, wherein the wireless network is a long term evolution (LTE), LTE-advanced (LTE-A), and/or 5G network. 
     Example 32 may comprise the method of example 29 or some other example herein, further comprising transmitting, by the eNB, the indication via one or more radio resource control (RRC) signals. 
     Example 33 may comprise the method of example 29 or some other example herein, further comprising transmitting, by the eNB, an indication of a switch of transmission/reception of the restricted radio bearers to or from a subset of serving cells of eNB. 
     Example 34 may comprise the method of example 33 or some other example herein, further comprising transmitting, by the eNB, the indication of the switch via one or more radio resource control (RRC) signals and/or medium access control (MAC) signals. 
     Example 35 may comprise a method comprising receiving, by a user equipment (UE) from an evolved NodeB (eNB), configuration information relating to restriction of one or more radio bearers that are transmitted on only a subset of serving cells of the eNB; and transmitting, by the UE, the one or more radio bearers to the eNB on one or more serving cells in the subset in response to receiving the configuration information. 
     Example 36 may comprise the method of example 35, further comprising receiving by the UE, the one or more radio bearers from only the subset of the serving cells of the eNB based on the configuration information. 
     Example 37 may comprise the method of example 35 or some other example herein, further comprising receiving, by the UE, the configuration information via one or more radio resource control (RRC) signals. 
     Example 38 may comprise the method of example 35 or some other example herein, further comprising performing, by the UE, logical channel prioritization based on the configuration information, the configuration information to comprise an information element ul-DataCellList to indicate indices of the subset of the serving cell where the one or more radio bearers can be transmitted and/or received by the UE. 
     Example 39 may comprise the method of example 35 or some other example herein, further comprising receiving, by the UE, an indication of a switching via one or more radio resource control (RRC) signals and/or medium access control (MAC) control element (CE) signals. 
     Example 40 may comprise the method of example 39 or some other example herein, further comprising switching, by the UE, transmission and/or reception of the one or more radio bearers to or from a serving cell of the subset of serving cells based on the indication of the switching. 
     Example 41 may comprise the method of example 35 or some other example herein, further comprising switching, by the UE, transmission and/or reception of the one or more radio bearers to or from a serving cell in the subset of serving cells, in response that the UE receives a downlink signal from the serving cell first. 
     Example 42 may comprise the method of example 35 or some other example herein, further comprising switching, by the UE, transmission and/or reception of the one or more radio bearers to or from a serving cell in the subset of serving cells in response to determining that the serving cell has a better radio link quality than the other serving cells in the subset of serving cells of the eNB. 
     Example 43 may comprise the method of example 35 or some other example herein, wherein the serving cells to be used in carrier aggregation of a long term evolution (LTE), LTE-advanced (LTE-A), and/or 5G wireless network. 
     Example 44 may comprise a user equipment (UE), comprising receive circuitry to receive from an evolved node B (eNB) a configuration with restriction information on one or more bearers that the one or more bearers are transmitted on only a subset of serving cells of the eNB used in carrier aggregation of a long term evolution (LTE), LTE-advanced (LTE-A), and or 5G wireless network; and transmit circuitry to transmit the one or more bearers to the said eNB on one or more serving cells in the subset based on the configuration. 
     Example 45 may comprise the UE of example 44, wherein the receive circuitry to receive the configuration via RRC signaling. 
     Example 46 may comprise the UE of example 44 or some other example herein, further comprising a logical channel prioritization (LCP) module to perform a restriction that the one or more bearers are transmitted based on said configuration in response to performing logical channel prioritization. 
     Example 47 may comprise the UE of example 44 or some other example herein, further comprising control circuitry to switch transmission/reception of the one or more bearers to/from a serving cell of the subset of serving cells based on RRC signaling corresponding to said restriction information from the eNB. 
     Example 48 may comprise the UE of example 44 or some other example herein, further comprising control circuitry to switch transmission/reception of the one or more bearers to/from a serving cell of the subset of serving cells based on MAC CE signaling corresponding to the restriction information from the eNB. 
     Example 49 may comprise the UE of example 47 or some other example herein, further comprising control circuitry to switch transmission/reception of the one or more bearers to/from a serving cell of the subset of serving cells, wherein the serving cell is the first serving cell, from which the receive circuitry receives the RRC signaling. 
     Example 50 may comprise the UE of example 47 or some other example herein, wherein said control circuitry is to perform the switching implicitly based on radio link quality of one or more serving cells of the eNB. 
     Example 51 may comprise the UE of example 44 or some other example herein, further comprising control circuitry to perform logical channel prioritization based on the configuration. 
     Example 52 may comprise an evolved NodeB (eNB), comprising control circuitry to identify configuration information relating to a restriction that one or more radio bearers are only transmitted to a subset of serving cells of a wireless network with carrier aggregation; and transmit circuitry to transmit to a user equipment (UE) an indication of the configuration information and to transmit to the UE the one or more radio bearers based on the configuration information. 
     Example 53 may comprise the eNB of example 52 or some other example herein, further comprising receive circuitry to receive from the UE the one or more radio bearers based on the configuration information. 
     Example 54 may comprise the eNB of example 52 or some other example herein, wherein the wireless network to comprise at least one of a long term evolution (LTE) network, a LTE-advanced (LTE-A) network, and/or a 5G network. 
     Example 55 may comprise the eNB of example 52 or some other example herein, wherein the transmit circuitry is to transmit to the UE the indication via one or more radio resource control (RRC) signals. 
     Example 56 may comprise the eNB of example 52 or some other example herein, wherein the transmit circuitry to transmit to the UE another indication relating to a switch of transmission/reception of the restricted radio bearers via a serving cell in the subset of serving cells. 
     Example 57 may comprise the eNB of example 52 or some other example herein, wherein the transmit circuitry is to transmit to the UE the another indication relating to the switch via one or more RRC signals and/or MAC CE signals. 
     Example 58 may comprise a non-transitory machine-readable medium having instructions, stored thereon, that, when executed cause an evolved NodeB (eNB) to transmit an indication of configuration information relating to a restriction of one or more radio bearers that are transmitted only on a subset of serving cells of a wireless network that is to use carrier aggregation; and transmit the one or more radio bearers to a user equipment (UE) on a serving cell of the subset of serving cells based on the configuration information. 
     Example 59 may comprise the non-transitory machine-readable medium of example 58 or some other example herein, having instructions, stored thereon, that, when executed cause the eNB further to receive the one or more radio bearers on a serving cell of the subset of serving cells based on the configuration information. 
     Example 60 may comprise the non-transitory machine-readable medium of example 58 or some other example herein, wherein the wireless network to comprise one or more of a long term evolution (LTE), a LTE-advanced (LTE-A), and/or a 5G network. 
     Example 61 may comprise the non-transitory machine-readable medium of example 58 or some other example herein, having instructions, stored thereon, that, when executed cause the eNB further to transmit the indication to the UE via one or more radio resource control (RRC) signals. 
     Example 62 may comprise the non-transitory machine-readable medium of example 58 or some other example herein, having instructions, stored thereon, that, when executed cause the eNB further to transmit to the UE an indication of a switch of transmission/reception of the one or more radio bearers to or from a serving cell in the subset of serving cells of the eNB. 
     Example 63 may comprise the non-transitory machine-readable medium of example 62 or some other example herein, having instructions, stored thereon, that, when executed cause the eNB further to transmit, by the eNB, the indication of the switch via one or more radio resource control (RRC) signals and/or medium access control (MAC) signals. 
     Example 64 may comprise a user equipment (UE), comprising a receiving module to receive from an evolved node B (eNB) a radio bearer on only a subset of one or more carriers based on a restriction corresponding to a service type provided by the eNB; and a transmitting module to transmit to the eNB the radio bearer on one or more carriers in the subset of carriers. 
     Example 65 may comprise the UE of example 64 or some other example herein, wherein the service type to correspond to a long term evolution (LTE) service, LTE-advanced (LTE-A) service, and/or 5G service. 
     Example 66 may comprise the UE of example 64 or some other example herein, wherein the subset of carriers to comprise one or more licensed LTE carriers for the service type of a LTE service or a LTE-A service. 
     Example 67 may comprise the UE of example 64 or some other example herein, wherein the subset of carriers to comprise one or more 5G carriers for the service type of a 5G service. 
     Example 68 may comprise the UE of example 64 or some other example herein, wherein the radio bearer to comprise a signaling radio bearer (SRB) or a data radio bearer with one or more quality of service (QoS) requirements. 
     Example 69 may comprise the UE of example 68 or some other example herein, wherein the data radio bearer to comprise a voice bearer, a voice over internet protocol (VoIP) bearer, or a real time gaming bearer. 
     Example 70 may comprise the UE of example 64 or some other example herein, further comprising a logical channel prioritization (LCP) module to determine if a serving cell of a logical channel is corresponding to a carrier in the subset of carriers in response to an uplink grant from the serving cell, and to prioritize the logical channel in response to determining that the serving cell corresponds to the carrier in the subset of carriers. 
     Example 71 may comprise the UE of example 64 or some other example herein, further comprising a switching module to switch transmission and/or reception of the radio bearer from an unlicensed LTE carrier to a licensed LTE carrier for the service type of a LTE service or a LTE-A service. 
     Example 72 may comprise the UE of example 64 or some other example herein, further comprising a switching module to switch transmission and/or reception of the radio bearer from a carrier to a 5G carrier for the service type of a 5G RAT service. 
     Example 73 may comprise an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-8, 17-22, 29-34, 35-43, and/or any other method or process described herein. 
     Example 74 may comprise one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-8, 17-22, 29-34, 35-43, and/or any other method or process described herein. 
     Example 75 may comprise an apparatus comprising control circuitry, transmit circuitry, and/or receive circuitry to perform one or more elements of a method described in or related to any of examples 1-8, 17-22, 29-34, 35-43 and/or any other method or process described herein. 
     Example 76 may comprise a method of communicating in a wireless network as shown and described herein. 
     It should be understood that many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like. 
     Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executable code of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module. 
     A module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. The modules may be passive or active, including agents operable to perform desired functions. 
     Reference throughout this specification to “an example” means that a particular feature, structure, or characteristic described in connection with the example is comprised in at least one embodiment of the present invention. Thus, appearances of the phrases “in an example” in various places throughout this specification are not necessarily all referring to the same embodiment. 
     As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as an equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. In addition, various embodiments and example of the present invention may be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as equivalents of one another, but are to be considered as separate and autonomous representations of the present invention. 
     Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of search spaces, to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention may be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention. 
     While the forgoing examples are illustrative of the principles of the present invention in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation may be made without the exercise of inventive faculty, and without departing from the principles and concepts of the invention. Accordingly, it is not intended that the invention be limited, except as by the claims set forth below. 
     While the methods of  FIGS. 1, 2, 7 and 8  is illustrated to comprise a sequence of processes, the methods in some embodiments may perform illustrated processes in a different order. 
     While certain features of the invention have been described with reference to embodiments, the description is not intended to be construed in a limiting sense. Various modifications of the embodiments, as well as other embodiments of the invention, which are apparent to persons skilled in the art to which the invention pertains are deemed to lie within the spirit and scope of the invention.