Title of Invention: Increased carrier monitoring
Abstract: A user equipment (UE) operable to perform inter-frequency measurements is disclosed. The UE can decode an information element (IE) received from an eNodeB. The UE can determine whether the IE received from the eNodeB includes a reduced measurement performance field. The UE can determine that a neighboring inter-frequency is configured for a reduced measurement performance when the reduced measurement performance field is included in the IE.
Detailed Description: Part general_description_paragraphs: Part RELATED APPLICATIONS: The present application is a continuation of U.S. patent application Ser. No. 15/512,822, filed Mar. 20, 2017 with a docket number of P73971US, which is a 371 nationalization of PCT Application No. PCT/US15/38674 filed Jun. 30, 2015 with a docket number of P73971PCT, which claims the benefit of U.S. Provisional Patent Application No. 62/056,289, filed Sep. 26, 2014 with a docket number of P73971Z, the entire specifications of which are hereby incorporated by reference in their entirety for all purposes.
Part BACKGROUND: The number of wireless devices (e.g., cellular phones and tablet computers) in use that connect to cellular networks has increased greatly over the past decade. Many of these wireless devices conform to existing standards established by the Third Generation Partnership Project (3GPP) requiring that up to three carrier frequencies be monitored by a device in a connected mode. The evolved universal terrestrial radio access network (E-UTRAN) or Long Term Evolution (LTE) standard established by the 3GPP, however, has been designed to be very flexible with regard to the frequency bands to provide desired bandwidth. Consequently, the number of frequency bands and frequency band combinations supported by a modern cellular device that can be very high. In order to meet today's increasing demand for fast wireless data transfer over cellular networks, the number of deployed bands and frequencies has increased significantly in recent years. As a result, minimum requirements that were established when fewer bands and frequencies were in use may ultimately be unnecessarily limiting for more modern wireless devices that support using a greater numbers of carriers.
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 is thereby intended.
Part DETAILED DESCRIPTION: Before some embodiments are disclosed and described, it is to be understood that the claimed subject matter is not limited to the particular structures, process operations, 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. Numbers provided in flow charts and processes are provided for clarity in illustrating operations and do not necessarily indicate a particular order or sequence.
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.
For Third-Generation-Partnership-Project (3GPP) Long-Term-Evolution (LTE) release 12 (rel-12) (and likely for future releases), the Radio-Access-Network-1 (RAN2) Working Group (WG) has agreed to introduce measurement capabilities that allow user equipments (UEs) to monitor an increased number of carriers. This capacity to monitor an increased number of carriers can be referred to as the increased-number-of-frequencies-to-monitor (IncMon) feature. The RAN2 WG has also agreed that separate capability bits will be defined for Universal-Mobile Telecommunications-System (UMTS) measurements and LTE measurements, respectively. However, no agreement has been reached regarding whether these bits will be split to distinguish different modes and whether the feature of monitoring an increased number of carriers will be optional.
The Radio-Access-Network-1 (RAN4) Working Group (WG) has increased the minimum number of inter-frequency carriers and cells that a user equipment (UE) is able to monitor in all radio-resource-control (RRC) states for LTE and UMTS. Signaling extensions have been defined in order to enable more carriers to be measured and for these additional measurements to be reported. For example, a new type of System Information Block (SIB) called a SIB11ter has been introduced in UMTS to enable the broadcast of additional inter-frequency neighbors on UMTS carriers. Dedicated signaling can be similarly used.
A network that supports the IncMon feature may signal if a carrier should be measured with reduced measurement performance. The network can also provide a scaling factor indicating an amount of time that a UE is to spend making measurements on a reduced-measurement-performance (RP) carrier. A carrier for which reduced measurement performance is not signaled, by contrast, is measured at a predefined rate designated for normal-measurement-performance carriers. Hence, a rel-12 UE that supports monitoring an increased number of carriers can perform measurements on legacy carriers at the same rate as legacy UEs (e.g., UEs conforming to 3GPP release 11 (rel-11)). However, a rel-12 UE can also perform measurements on additional carriers at the same rate or at a reduced rate. The scaling factor provided by the network is used to determine the reduced rate. Carriers that are measured at a reduced rate are said to be in a reduced-measurement-performance (RP) group, while carriers measured at the normal rate are said to be in the normal-measurement-performance (NP) group.
The maximum time period in between carrier measurements in 3GPP rel-11 (i.e., the measurement reporting delay) can be referred to as TIdentify_Inter_r11, while the maximum measurement reporting delay for rel-12 can be referred to as TIdentify_Inter_r12. The quantity TIdentify_Inter_r11 is defined by the following equation:




  
    T
    
      
        Identify
        ⁢
        _
        ⁢
        Inter
      
      ⁢
      
        _
        ⁢
        r
      
      ⁢
      
        
      
      ⁢
      11
    
  
  =
  
    
      
        
          T
          
            
              Basic
              ⁢
              _
              ⁢
              Identify
            
            ⁢
            
              _
              ⁢
              Inter
            
          
        
        *
        480
      
      
        T
        
          Inter
          ⁢
          
            
          
          ⁢
          1
        
      
    
    *
    
      N
      freq
    
  




TBasic_Identify_Inter is the maximum allowed time for a UE to identify a new Frequency Division Duplexing (FDD) inter-frequency cell and TInter1 is the minimum available time for inter-frequency and inter-RAT measurements during a 480 millisecond (ms) period. Nfreq refers to the number of frequencies to monitor. The quantity TIdentify_Inter_r12 includes a scaling factor (S) and is defined by the following equation:




  
    T
    
      
        Identify
        ⁢
        _
        ⁢
        Inter
      
      ⁢
      
        _
        ⁢
        r
      
      ⁢
      
        
      
      ⁢
      12
    
  
  =
  
    
      S
      
        S
        -
        1
      
    
    *
    
      
        
          T
          
            
              Basic
              ⁢
              _
              ⁢
              Identify
            
            ⁢
            
              _
              ⁢
              Inter
            
          
        
        *
        480
      
      
        T
        
          Inter
          ⁢
          
            
          
          ⁢
          1
        
      
    
    *
    
      N
      freq
    
  




The RAN4 WG has agreed that Code-Division-Multiple-Access 2000 (CDMA2000) and Global System for Mobiles (GSM) will be included in only the NP group, so no additional signaling is needed for CDMA2000 or GSM layers. The RAN4 WG has also agreed that is should be possible to indicate many different combinations of normal and reduced-performance carriers. The RAN4 WG has also opined that that it would be beneficial to have a default rule indicating which carriers belong to the NP group and which carriers belong to the RP group for cases in which a Universal Terrestrial Radio Access Network (UTRAN) does not provide any signaling related to the increased-number-of-frequencies-to-monitor (IncMon) feature.
The scaling factor and the indication of which carriers belong to which performance group needs is needed for UEs in modes such as Universal-Terrestrial-Radio-Access (UTRA) idle, UTRA cell Paging Channel (PCH), UTRA UTRAN Registration Area (URA) PCH, UTRA cell Forward Access Channel (FACH), UTRA Dedicated Channel (DCH), E-UTRA idle, and E-UTRA connected. For UEs in UTRA idle, UTRA CELL PCH, UTRA URA PCH, or LTE idle states, the RAN4 WG does not anticipate that the scaling factor will need to be configured by higher-layer signaling.
For UEs in a UTRA cell FACH mode and UEs in a UTRA cell DCH mode, the RAN4 WG anticipates that at most four scaling factors per mode would be need to be provided for UTRA carriers in the RP group. Up to four scaling factors can be explicitly signaled and an additional default value can be used for carriers for which a scaling factor is not explicitly signaled.
For UEs in E-UTRA Radio-Resource-Control (RRC) connected mode, the RAN4 WG anticipates that at most four scaling factors would be needed. Up to four scaling factors can be explicitly signaled and an additional default value can be used for carriers for which a scaling factor is not explicitly signaled. In one example, there may be two different scaling factors with values of 8 and 16. The same scaling factors may be applied to both UTRA and E-UTRA.
The RAN4 WG intends to specify mappings between scaling factors and measurement performance in 3GPP Technical Specifications (TSs) 25.133 and 36.133.The following scaling factors are presumptively mapped to performance requirements: SCALING_FACTOR_UTRA_CONFIG1, SCALING_FACTOR_UTRA_CONFIG2, SCALING_FACTOR_UTRA_CONFIG3, SCALING_FACTOR_UTRA_CONFIG4, SCALING_FACTOR_EUTRA_CONFIG1, SCALING_FACTOR_EUTRA_CONFIG2, SCALING_FACTOR_EUTRA_CONFIG3, and SCALING_FACTOR_EUTRA_CONFIG4. Only one scaling factor is used by a UE at any one time.
There are currently two choices available for a default configuration. The first choice, referred to as Mode 1, calls for all carriers to be included in the NP group. Mode 1 can reduce overall average measurement delay.
In the second choice, referred to as Mode 2, a pre-configured number of carriers can be assigned to the normal-measurement performance group and a set of scaling factors can be provided for carriers in the RP group; the pre-configured number and the scaling factors can be provided in the 3GPP specification. The NP and RP groups can be determined based on the order of a predefined ordered list. For example, if the preconfigured number of carriers is three, the first three carriers on the predefined ordered list can be assigned to the NP group. Any remaining carriers in the predefined ordered list can be assigned to the RP group. Mode 2 can reduce signaling overhead while allowing some carriers to be included in a RP group.
There are advantages that can be gained by using default configurations in rel-12 networks. However, a problem arises when a UE that complies with 3GPP rel-12 is to be used with an older network, such as a network that only conforms to 3GPP rel-11 (or an earlier release). A rel-11 network does not support the IncMon feature. As a result, if a rel-12 UE applies a default configuration specified in the rel-12 when no IncMon signaling is received from the rel-11 network, the rel-12 UE will follow the rel-12 delay requirement. The rel-12 delay requirement, however, may not satisfy the rel-11 delay requirement.
Systems and methods in accordance with the present disclosure provide several different carrier-monitoring (CM) configuration options and signaling approaches that can be used by networks and/or devices conforming to the 3GPP rel-12 standard (and possibly for subsequent releases). In some embodiments, the IncMon feature can be optional rather than mandatory in order to accommodate UEs that do not support the IncMon feature.
In a first CM configuration option (option 1), mode 1 can be used as the default configuration. In option 2, mode 1 can be used as the default configuration and mode 2 can also be adopted as a configurable configuration. In option 3, mode 2 can be used as the default configuration. In option 4, mode 2 can be used as the default configuration and mode 1 can also be adopted as a configurable configuration. In option 5, both mode 1 and mode 2 can be adopted as configurable configurations and neither mode is used as a default. For any of the options 1-5, network signaling can be introduced to indicate which configuration should be used by a UE.
FIG. 1 illustrates exemplary code describing an example of a modified Measurement-Configuration (MeasConfig) information element (IE) 100. The MeasConfig IE can be used to signal a default IncMon configuration that is used in a network. The MeasConfig IE 100, in general, specifies measurements to be performed by the UE and covers intra-frequency, inter-frequency, and inter-Radio-Access-Technology (inter-RAT) mobility as well as configuration of measurement gaps. A variable identifying the default configuration for the IncMon feature can be added to the MeasConfig IE. As shown in selection 102, the variable can be named defaultConfigIncMon-v12xy (though other names are possible). The MeasConfig IE 100 and the defaultConfigIncMon-v12xy variable can be included in a measurement-configuration (MC) communication sent from the network to the UE in order to inform the UE of which mode (e.g., mode 1 or mode 2, as in option 1 or option 3, respectively) should be used as a default configuration. The MC communication can comprise a Radio-Resource-Control (RRC) reconfiguration message.
A MeasConfig IE can comprise a MeasObjectToAddModList IE. The MeasObjectToAddModList IE can, in turn, comprise a list of measurement objects for one or more RATs (e.g., E-UTRAN, UTRAN, GSM/Enhanced Data rates for Global Evolution (EDGE) Radio Access Network (GERAN), CDMA2000). The measurement object for to E-UTRAN, for example, is known as the measObjectEUTRA IE. The list of measurement objects can comprise a list of carriers that are to be monitored.
FIG. 2 illustrates a table 200 containing exemplary field descriptions for the measObjectEUTRA IE. As shown in selection 202, a field description can be included for the defaultConfigIncMon-v12xy variable for documentation purposes.
FIG. 3 illustrates exemplary code describing another example of a modified MeasConfig IE 300. The MeasConfig IE 300 can be used to inform a UE regarding both a default IncMon configuration and a pre-configured IncMon configuration that are used in a network. The MeasConfig IE 300, in general, specifies measurements to be performed by the UE and covers intra-frequency, inter-frequency, and inter-Radio-Access-Technology (inter-RAT) mobility as well as configuration of measurement gaps. As shown in selection 302, a variable named defaultConfigIncMon-v12xy and a variable named preConfigIncMon-v12xy can be included in the MeasConfig IE 300 (although other names are possible). The MeasConfig IE 300, the defaultConfigIncMon-v12xy variable, and the preConfigIncMon-v12xy variable can be included in a measurement-configuration (MC) communication sent from the network to the UE in order to inform the UE of which mode (e.g., mode 1 or mode 2, as in option 2 or option 4) should be used as a default configuration and which mode should be used as an alternative adopted configuration. The MC communication can comprise a Radio-Resource-Control (RRC) reconfiguration message.
FIG. 4 illustrates exemplary code describing another example of a modified MeasConfig IE 400. The MeasConfig IE 400 can be used to inform a UE regarding two configurable IncMon configurations that are used by a network. The MeasConfig IE 400, in general, specifies measurements to be performed by the UE and covers intra-frequency, inter-frequency, and inter-Radio-Access-Technology (inter-RAT) mobility as well as configuration of measurement gaps. As shown in selection 402, a variable named configIncMon-v12xy can be included in the MeasConfig IE 400 (though other names are possible). The MeasConfig IE 400 and the configIncMon-v12xy variable can be can be included in a measurement-configuration (MC) communication sent from the network to the UE in order to inform the UE of which of the adopted modes (e.g., mode 1 or mode 2, as in option 5) should be used, where neither mode is used as a default configuration. The MC communication can comprise a Radio-Resource-Control (RRC) reconfiguration message.
FIG. 5 illustrates exemplary functionality 500 of an apparatus of a user equipment (UE) that supports the IncMon feature. The functionality can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included on at least one computer readable medium or one non-transitory machine readable storage medium. The UE can comprise, for example, one or more antennas, one or more processors, and a transceiver. As in block 510, circuitry at the UE (e.g., a transceiver) can identify a carrier-monitoring (CM) configuration option applied at the UE. In some examples, the circuitry can receive a measurement-configuration (MC) communication that comprises the CM configuration option from an evolved node B (eNB) via the one or more antennas. The CM configuration option can comprise any of the options 1-5, as explained above, and can comprise a default configuration and/or one or more adopted configurations. A default configuration and/or an adopted configuration can comprise mode 1 or mode 2, as explained above. In some embodiments, the MC communication can comprise a feature in a measurement-configuration (MeasConfig) information element. If the CM configuration option comprises only a default configuration and not an adopted configuration, the CM configuration option can be predefined in a technical specification to which the UE conforms and therefore does not have to be received in an MC communication.
As in block 520, circuitry at the UE (e.g., a transceiver) can also receive a list of carriers that are to be monitored via the one or more antennas. As in block 530, circuitry at the UE (e.g., one or more processors) can apply the CM configuration option at the UE by monitoring carriers in the list of carriers at one or more rates designated in the CM configuration option. In some examples, circuitry can also identify UE-capability information that comprises six bits. One bit in the six bits can correspond to a default configuration, another bit in the six bits can correspond to an adopted configuration, and four bits in the six bits can correspond to four respective configurable configurations in different radio access technologies (RATs). The circuitry at the UE (e.g., a transceiver) can send the UE-capability information to the eNB via the one or more antennas. In some examples, the circuitry at the UE can also be configured to receive an IncMon-support message from the eNB indicating whether the eNB supports the IncMon feature. If no IncMon message is received, the circuitry at the UE (e.g., one or more processors) can be configured to apply a default CM configuration. The default CM configuration may be pre-defined in a technical specification. The UE-capability information can be sent using radio-resource control signaling.
FIG. 6 illustrates exemplary functionality 600 of an apparatus of an evolved Node B (eNB) that supports the IncMon feature. The functionality can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included on at least one computer readable medium or one non-transitory machine readable storage medium. The eNB can comprise, for example, one or more antennas, one or more processors, and a transceiver. As in block 610, circuitry at the eNB (e.g., one or more processors) can identify a measurement-configuration (MC) communication, the MC communication indicating a carrier-monitoring (CM) configuration option applied by a network. The CM configuration option can comprise any of the options 1-5, as explained above, and can comprise a default configuration and/or one or more adopted configurations. A default configuration and/or an adopted configuration can comprise mode 1 or mode 2, as explained above.
For example, the CM configuration option can comprise a default configuration. The default configuration can comprise a mode (mode 1) in which all carriers in the list of carriers are monitored at a predefined rate. In another example, the default configuration can comprise a mode (mode 2) in which carriers in the list of carriers are assigned to either a normal-performance (NP) group or a reduced-performance (RP) group, wherein carriers assigned to the NP group are monitored at a predefined rate and carriers in the RP group are monitored at a reduced rate based on one or more scaling factors.
In another example, the CM configuration option can also comprise one or more adopted configurations. For example, one of either mode 1 or mode 2 can be an adopted configuration while the other respective mode can be a default configuration. In another example, both mode 1 and mode 2 can be adopted configurations.
As in block 620, circuitry at the eNB (e.g., one or more processors) can identify a list of carriers that are to be monitored. As in block 630, circuitry at the eNB (e.g., a transceiver) can send the MC communication and the list of carriers to a user equipment (UE) via the one or more antennas. The MC communication and/or list of carriers may be sent via dedicated signaling or via a broadcast signaling.
FIG. 7 provides an example illustration of the wireless device, such as a user equipment (UE), a mobile station (MS), a mobile wireless device, a mobile communication device, a tablet, a handset, or other type of wireless device. The wireless device can include one or more antennas configured to communicate with a node, macro node, low power node (LPN), or, transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE), or other type of wireless wide area network (WWAN) access point. The wireless device can be configured to communicate using at least one wireless communication standard including 3 GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi. The wireless device can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards. The wireless device can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a WWAN.
FIG. 7 also provides an illustration of a microphone and one or more speakers that can be used for audio input and output from the wireless device. The display screen can be a liquid crystal display (LCD) screen, or other type of display screen such as an organic light emitting diode (OLED) display. The display screen can be configured as a touch screen. The touch screen can use capacitive, resistive, or another type of touch screen technology. An application processor and a graphics processor can be coupled to internal memory to provide processing and display capabilities. A non-volatile memory port can also be used to provide data input/output options to a user. The non-volatile memory port can also be used to expand the memory capabilities of the wireless device. A keyboard can be integrated with the wireless device or wirelessly connected to the wireless device to provide additional user input. A virtual keyboard can also be provided using the touch screen.
Various techniques, or certain aspects or portions thereof, can take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, non-transitory computer readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. Circuitry can include hardware, firmware, program code, executable code, computer instructions, and/or software. A non-transitory computer readable storage medium can be a computer readable storage medium that does not include signal. In the case of program code execution on programmable computers, the computing device can include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. The volatile and non-volatile memory and/or storage elements can be a RAM, EPROM, flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data. The node and wireless device can also include a transceiver module, a counter module, a processing module, and/or a clock module or timer module. One or more programs that can implement or utilize the various techniques described herein can use an application programming interface (API), reusable controls, and the like. Such programs can be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) can be implemented in assembly or machine language, if desired. In any case, the language can be a compiled or interpreted language, and combined with hardware implementations.
As used herein, the term processor can include general-purpose processors, specialized processors such as VLSI, FPGAs, and other types of specialized processors, as well as base-band processors used in transceivers to send, receive, and process wireless communications.
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 can 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 can also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
Modules can also be implemented in software for execution by various types of processors. An identified module of executable code can, for instance, comprise one or more physical or logical blocks of computer instructions, which can, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but can comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
Indeed, a module of executable code can be a single instruction, or many instructions, and can even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data can be identified and illustrated herein within modules, and can be embodied in any suitable form and organized within any suitable type of data structure. The operational data can be collected as a single data set, or can be distributed over different locations including over different storage devices, and can exist, at least partially, merely as electronic signals on a system or network. The modules can be passive or active, including agents operable to perform desired functions.
As used herein, the term “processor” can include general purpose processors, specialized processors such as VLSI, FPGAs, and other types of specialized processors, as well as base band processors used in transceivers to send, receive, and process wireless communications.
Reference throughout this specification to “an example” means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the present disclosure. 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 can 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 a de facto 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 examples of the present disclosure can 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 de facto equivalents of one another, but are to be considered as separate and autonomous representations.
Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of layouts, distances, network examples, etc., to provide a thorough understanding of embodiments of the described herein. One skilled in the relevant art will recognize, however, that some embodiments can be practiced without one or more of the specific details, or with other methods, components, layouts, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.
While the forgoing examples are illustrative of the principles of the present disclosure 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 can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the disclosure. Accordingly, it is not intended that the disclosure be limited, except as by the claims set forth below.


{'bibliographic_information': "{'country': 'US', 'doc-number': '16222904', 'kind': 'B2', 'date': '20181217', 'invention_title': 'Increased carrier monitoring'}", 'source_file': './grant/2020/ipg200908.xml', 'source_data': 'USPTO-Grant'}