Apparatus and method for priority frequency band derivation in wireless communications
Through the autonomous priority band/band combination derivation method, the radio link failure problem caused by excessive frequency bands of mobile communication equipment is solved, and higher service continuity and user experience are achieved, and the carrier aggregation characteristics are provided with network requests. compatibility.
Patent Information
- Application Number
- CN201780089058.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2017-05-02
- Publication Date
- 2025-01-14
- Estimated Expiration
- 2037-05-02
AI Technical Summary
When a mobile communication device reports too many supported frequency bands and frequency band combinations, the network may truncate the response message, resulting in radio link failures and service continuity interruptions, affecting the user experience.
Through the autonomous priority band/band combination derivation (APBD) method, the system information of the UE stationed in the cell is used to deduce the frequency band and frequency band combination combination of the network, limit the frequency band and frequency band combination report in the UE uplink message, and reduce network reception The capability information length ensures service continuity.
Effectively reduces the occurrence of radio link failures, improves user experience, and provides higher compatibility and accuracy in early network infrastructure, avoiding negative network impacts.
Smart Images

Figure CN110506445B_ABST
Abstract
Description
Technical Field
[0001] Various aspects of the disclosure are generally directed to methods and apparatus for wireless communications. Background Art
[0002] The increased power of mobile communication devices (e.g., user equipment (UE)) increases the number of frequency bands and frequency band combinations that the device can support. Although this provides a more powerful UE in terms of connecting to a wider range of Radio Access Technology (RAT) frequencies, if the UE reports too many supported frequencies in response to a UE capability request from the network, the network will truncate the response message from the UE, causing some network capability information to be lost, which can lead to radio link failures. As a result, interruptions in service continuity can occur, thereby deteriorating the user experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0003] In the drawings, like reference numerals generally refer to the same parts throughout the different views. The drawings are not necessarily to scale, with emphasis generally being placed on illustrating the principles of the invention. In the following description, various embodiments of the invention are described with reference to the following drawings, in which:
[0004] Figure 1 is an overview of the methods and apparatus of the present disclosure;
[0005] Figure 2 is the method of frequency band reporting;
[0006] Figure 3 is a flow chart showing the accumulation of priority bands in LTE;
[0007] Figure 4 is a flow chart showing the derivation of frequency bands from SIB 1;
[0008] Figure 5 is a flowchart showing the processing of multiBandInfoList in SIB 1;
[0009] Figure 6 is a flow chart showing the derivation of frequency bands from SIB 5;
[0010] Figure 7 is a flow chart illustrating the processing of an Evolved Absolute Radio Frequency Channel Number (EARFCN);
[0011] Figure 8 is a flow chart showing processing for other frequencies of interest;
[0012] Fig. 9 is a flow chart showing the derivation of frequency bands from SIB 19;
[0013] Fig.10 is a flow chart illustrating application of priority bands;
[0014] Fig.11 is a flow chart showing the construction of UE-EUTRA-Capability based on a priority band list;
[0015] Fig.12 is a flow chart illustrating the supplementation of a priority frequency band list;
[0016] Fig.13 A wireless communication network is shown;
[0017] Fig.14 is a message sequence chart (MSC) illustrating an exemplary scenario in an aspect of the present disclosure; and
[0018] Fig.15 shows the configuration of a device configured to execute the methods and algorithms of the present disclosure; and
[0019] Fig.16 A flow chart describing the method of the present disclosure is shown. DETAILED DESCRIPTION
[0020] The following detailed description refers to the accompanying drawings that show, by way of illustration, specific details and embodiments in which the invention may be practiced.
[0021] The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs.
[0022] The words "plurality" and "multiple" (if any) in the specification and claims are used to expressly refer to a quantity greater than one. Therefore, any phrase that explicitly invokes the above words to refer to a quantity of objects (e.g., "plurality of [objects]", "plurality of [objects]") is intended to expressly refer to more than one of the objects. The terms "group", "set", "collection", "series", "sequence", "grouping", "selection", etc., and the like (if any) in the specification and claims are used to refer to a quantity equal to or greater than one, i.e., one or more. Therefore, the phrases "group of [objects]", "collection of [objects]", "collection of [objects]", "series of [objects]", "sequence of [objects]", "grouping of [objects]", "selection of [objects]", "group of [objects]", "collection of [objects]", "series of [objects]", "sequence of [objects]", "grouping of [objects]", "selection of [objects]", "group of [objects]", "collection of [objects]", "series of [objects]", "sequence of [objects]", "grouping of [objects]", "selection of [objects]", etc., used herein in connection with a quantity of objects, are intended to refer to a quantity of one or more of the objects. It will be understood that reference to a number of objects is intended to refer to one or more of the objects unless reference is made directly to an explicitly stated plurality (e.g., “two [objects],” “three of [objects],” “ten or more [objects],” “at least four [objects],” etc.) or the word “plurality,” “multiple,” or similar phrases are expressly used.
[0023] "Circuit" used herein is understood as any kind of entity that implements logic, which may include dedicated hardware or a processor that executes software. The circuit can thus be an analog circuit, a digital circuit, a mixed signal circuit, a logic circuit, a processor, a microprocessor, a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), a field programmable gate array (FPGA), an integrated circuit, an application-specific integrated circuit (ASIC), etc., or any combination of these. Any other kind of implementation of each function described in more detail below may also be understood as a "circuit". It is to be understood that any two (or more) of the circuits detailed herein may be implemented as a single circuit with substantially equivalent functions, and conversely, any single circuit detailed herein may be implemented as two (or more) separate circuits with substantially equivalent functions. In addition, mentioning "circuit" may refer to two or more circuits that form a single circuit as a whole. The term "circuit arrangement" may refer to a single circuit, a collection of circuits, and / or an electronic device consisting of one or more circuits.
[0024] As used herein, a "processing circuit" (or equivalently a "processing circuit" or "processor") is understood to be any circuit that performs (one or more) operations on (one or more) signals, such as any circuit that performs processing on an electrical or optical signal. A processing circuit may thus refer to any analog or digital circuit that changes the characteristics or properties of an electrical or optical signal, which may include analog and / or digital data. A processing circuit may thus refer to an analog circuit (specifically referred to as an "analog processing circuit"), a digital circuit (specifically referred to as a "digital processing circuit"), a logic circuit, a processor, a microprocessor, a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), a field programmable gate array (FPGA), an integrated circuit, an application specific integrated circuit (ASIC), etc., or any combination of these. Thus, a processing circuit may refer to a circuit that performs processing on an electrical or optical signal as hardware or as software, such as software executed on hardware (e.g., a processor or microprocessor). As used herein, "digital processing circuitry" may refer to circuitry implemented with digital logic that performs processing on signals (e.g., electrical or optical signals), and may include (one or more) logic circuits, (one or more) processors, (one or more) scalar processors, (one or more) vector processors, (one or more) microprocessors, (one or more) controllers, (one or more) microcontrollers, (one or more) central processing units (CPUs), (one or more) graphics processing units (GPUs), (one or more) digital signal processors (DSPs), (one or more) field programmable gate arrays (FPGAs), (one or more) integrated circuits, (one or more) application specific integrated circuits (ASICs), or any combination of these. In addition, it is understood that a single processing circuit may be equivalently divided into two separate processing circuits, and conversely, two separate processing circuits may be combined into a single equivalent processing circuit.
[0025] As used herein, "memory" may be understood as an electrical component in which data or information may be stored for retrieval. References to "memory" included herein may be understood to refer to volatile or non-volatile memory, including random access memory (RAM), read-only memory (ROM), flash memory, solid-state storage device, tape, hard drive, optical drive, etc., or any combination of these. In addition, it is understood that registers, shift registers, processor registers, data buffers, etc. are also encompassed by the term "memory" herein. It is understood that a single component referred to as a "memory" or "a memory" may be composed of more than one different type of memory, thereby referring to a collective component including one or more types of memory. It is readily understood that any single memory "component" may be distributed or separated into a plurality of substantially identical memory components, and vice versa. In addition, it is understood that although a "memory" may be depicted as being separated from one or more other components (e.g., in the accompanying drawings), it is understood that the memory may be integrated within another component, such as on a common integrated chip.
[0026] For purposes of the present disclosure, a radio communication technology may be classified as one of a short-range radio communication technology, a metropolitan area system radio communication technology, or a cellular wide area radio communication technology. Short-range radio communication technologies include Bluetooth, WLAN (e.g., according to any IEEE 802.11 standard), and other similar radio communication technologies. Metropolitan area system radio communication technologies include Worldwide Interoperability for Microwave Access (WiMax) (e.g., according to IEEE 802.16 radio communication standards, such as WiMax fixed or WiMax mobile), and other similar radio communication technologies. Cellular wide area radio communication technology includes Global System for Mobile Communications (GSM), Code Division Multiple Access 2000 (CDMA2000), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), General Packet Radio Service (GPRS), Evolution-Data Optimized (EV-DO), Enhanced Data Rates for GSM Evolution (EDGE), High Speed Packet Access (HSPA), etc., as well as other similar radio communication technologies. Cellular wide area radio communication technology also includes "small cells" of this technology, such as micro cells, femto cells and pico cells. Cellular wide area radio communication technology may be generally referred to as "cellular" communication technology in this article. It is to be understood that the exemplary scenarios detailed herein are illustrative and therefore may be similarly applied to various other mobile communication technologies, whether existing or yet to be developed, particularly where such mobile communication technologies share similar features with the disclosed content with respect to the examples that follow.
[0027] The term "network" as utilized herein, e.g. referring to a communication network such as a mobile communication network, is intended to cover both access components of the network (e.g. radio access network (RAN) components) and core components of the network (e.g. core network components).
[0028] Unless explicitly stated otherwise, the term "sending" encompasses both direct sending (point-to-point) and indirect sending (via one or more intermediate points). Similarly, the term "receiving" encompasses both direct receiving and indirect receiving. The term "communicating" encompasses one or both of sending and receiving, i.e., unidirectional or bidirectional communication in one or both of the inbound and outbound directions. The term "computing" encompasses both "direct" computation via mathematical expressions / formulas / relationships, as well as computation via lookup tables and other array indexing or searching operations.
[0029] The disclosure herein provides a method and apparatus for systematically reducing the frequency bands and frequency band combinations supported by a UE reported in an uplink message to a network, such as a Radio Resource Control (RRC) message "UECapabilityInformation" in Long Term Evolution (LTE) or an RRC connection setup complete and UE capability information message in a Universal Terrestrial Radio Access Network (UTRAN). It has been observed in LTE network testing that if the UE reports too many supported frequency bands and frequency band combinations in the RRC message "UECapabilityInformation", the RRC connection reconfiguration process triggered by the network for handover does not occur, resulting in a radio link failure. This is attributed to the network truncating the capability information reported by the UE in the "UECapabilityInformation" message according to its limitations, so that some of the capability information reported by the UE is not received by the network, resulting in an interruption in service continuity. However, if the UE reports fewer supported frequency bands and frequency band combinations, the length of the "UECapabilityInformation" message can be shortened and the RRC reconfiguration handover can be performed seamlessly.
[0030] The method and apparatus of the present disclosure utilize information broadcast by the cell on which the UE is camped to autonomously derive the frequency bands and band combinations supported by the network and / or the UE. When reporting to the network, the UE can therefore limit its response to only include those derived frequency bands and band combinations in order to reduce the length of the UE capability information sent to and / or received by the network. The methods and algorithms implemented by the signal processing components of the present disclosure are collectively referred to as Autonomous Priority Band / Band-combination Derivation (APBD).
[0031] For example, the LTE radio access network (RAN) broadcasts system information in a System Information Block (SIB) containing "FreqBandIndicator", "multiBandInfoList", "interFreqCarrierFreqList", etc., and sends measurement configurations, i.e., "measConfig", which are received by the UE. The APBD uses these information elements to deduce the frequency bands and band combinations supported by the network, so that the length of the UE uplink capability message can be reduced to achieve better service continuity, thereby improving the user experience.
[0032] The Third Generation Partnership Project (3GPP) introduced an optional feature called "Network requested CA Band Combination Capability Signaling (NRCAS)" to restrict UEs from reporting the frequency bands and band combinations they support, but this feature requires both the UE and the network to be upgraded to the latest corresponding version of the standard in order to support this feature. APBD provides a more flexible and compatible solution, and can also serve as a supplement to the currently specified solution, while allowing UEs to work better in earlier network infrastructure versions compared to NRCAS. In the first scenario showing that APBD has higher compatibility than NRCAS, if the network does not support NRCAS and whether the UE supports NRCAS or not, the UE configured to implement APBD can still provide the network with a shorter and more reasonable frequency band / band combination without introducing any negative impact on the network. In the second scenario showing that APBD has higher compatibility than NRCAS, if both the UE and the network support NRCAS, the UE configured with APBD will still be able to provide the network with a more accurate frequency band / band combination.
[0033] APBD can be used in multiple modes, for example, in both LTE mode and 3G mode. For UEs operating in Evolved UTRAN (E-UTRAN) mode, i.e., LTE mode, E-UTRAN queries the UE about its capabilities. APBD uses system information, including information broadcast by SIB 1, SIB 5 and / or SIB 15, and measurement configuration (e.g., measConfig in the rrcConnectionReconfig message) to derive the supported frequency bands and frequency band combinations, allowing the UE to report the derived capability information to E-UTRAN. For UEs operating in UTRAN mode, i.e., 3G mode, APBD can also use information broadcast by SIB 19 and / or measurement control to derive the supported frequency bands and frequency band combinations so as to set the derived capability information in the RRC Connection Setup Complete message and / or the UE Capability Information message.
[0034] Figure 1 is a diagram 100 illustrating an overview of the APBD method of the present disclosure. It is to be understood that diagram 100 is exemplary and thus may be simplified for the purposes of description herein.
[0035] To obtain service, the UE selects a cell to camp on and registers its presence with the network. For the access layer protocol stack, the UE performs the procedures depicted in 102-110 to comply with the 3GPP specifications. In 102, the UE obtains the necessary system information from the SIB broadcast by the network. In 104, the UE establishes an RRC connection when registering with the network or initiating a service. In 106, the E-UTRAN requests the UE to provide its capability information, for example, in LTE, the evolved Node B (eNodeB, or eNB) sends a UE capability inquiry downlink message to the UE. In 108, the network reconfigures the RRC connection, for example, during an inter-cell handover. In 110, the RRC connection is released when the registration process or service is terminated.
[0036] Features introduced by APBD are shown in 202-206. In 202, APBD accumulates and sorts frequency bands and / or frequency band combinations according to priority. In 204, the accumulated and sorted frequency bands and / or frequency band combinations are used to construct a priority band list. And in 206, the priority bands in the database can be supplemented (i.e., updated) to keep the UE up to date with the latest network conditions.
[0037] Figure 2 200 is a flowchart illustrating frequency band reporting according to APBD implemented in the present disclosure. Flowchart 200 shows 202-206 because in order to Figure 1 They are applied in , and they are related to each other.
[0038] The APBD implements a local database for storing priority frequency bands. The local database may be initialized to an invalid value and may include at least one of the following characteristics: it includes a list of cell identities and frequency bands; it does not contain duplicate frequency bands in the list; it has a priority order, with the first frequency band on the list having the highest priority; it is cleared each time a cell is changed (e.g., during cell selection, cell reselection, handover, etc.); it is cleared each time SIB 1 and / or SIB 5 is changed; and the number of stored priority frequency bands may be limited to a certain number, for example, selected so that the information sent to the network in an uplink message does not exceed the number of spaces allocated for such uplink messages.
[0039] Figure 3 3 is a flowchart 300 illustrating the accumulation of priority bands in one aspect of the present disclosure. It is to be understood that the flowchart 300 is exemplary and may be simplified for the purpose of description herein. The flowchart 300 is an example when the UE is in E-UTRAN (i.e., LTE) mode, but it is to be understood that similar processes may be applied to corresponding features in UTRAN (i.e., 3G) mode.
[0040] The accumulation of priority bands may be triggered when camping on a cell and / or when receiving system information from the network 302. The priority bands may be derived from SIB 1 304 and added to the database 350 with a priority band list, wherein SIB 1 304 contains a mandatory information element (IE) "freqBandIndicator" and other optional IEs, such as "multiBandInfoList", "freqBandIndicator-v9e0", "multiBandInfoList-v9e0", "freqBandIndicatorPriority-r12", etc. The priority bands are derived from SIB 1 in Figure 4 Shown in more detail in .
[0041] In addition to deriving priority bands from information from SIB 1 (e.g., from "freqBandIndicator" and other IEs), APBD also derives priority bands from SIB 5 308 and adds these priority bands to database 350. SIB 5 contains mandatory IE "interFreqCarrierFreqList" and other optional IEs, such as "interFreqCarrierFreqList-v8h0", "interFreqCarrierFreqList-v9e0", "interFreqCarrierFreqListExt-r12", etc., and APBD uses the frequencies from these IEs to derive priority bands to add to database 350. Derivation of priority bands from SIB 5 is Figure 6 Shown in more detail in .
[0042] Additionally, if it is determined at 310 that other frequencies of interest 312 are available, the priority frequency band may be derived from the other frequencies of interest 312. The frequencies of interest may be, for example, subscription service frequencies, such as for evolved Multimedia Broadcast Multicast Service (eMBMS), Closed Subscriber Group (CSG), etc. The processing of these frequencies of interest is described in Figure 8 Shown in more detail in .
[0043] If the UE is in UTRAN mode, it may also receive SIB 19 ( Figure 3 (not shown in FIG. 1 ). SIB 19 contains IEs "eutra-FrequencyBandPriorityInfoList", "multipleEUTRAFrequencyBandIndicatorList", etc. The priority bands can also be derived from these IEs and added to the database 350. The frequency bands derived from SIB 19 when the UE is in Fig. 9 Shown in more detail in .
[0044] Figure 4 A flowchart 400 is shown corresponding to 304 in the figure for deriving priority bands from SIB 1. It is to be understood that flowchart 400 is exemplary and may be simplified for the purpose of description herein.
[0045] The UE may receive the IE "freqBandIndicator-v9e0" 402 in SIB 1 and use this IE to determine a first frequency band, such as Band A, 404. If Band A is supported by the UE, it is added to a database including a prioritized frequency band list 408. If it is determined that it is not supported by the UE 406, it is not added. If the UE also receives "multiBandInfoList-v9e0" 410, it may deduce more frequency bands 412, which are Figure 5 After completing the acquisition of frequency bands from SIB 1 and adding them to the database, the UE may determine whether SIB 1 contains a "freqBandIndicatorPriority-r12" IE 414 in order to sort 416 the priority frequency band list.
[0046] Figure 5 Shown with Figure 4 412 in FIG. 5 is a flowchart 500 for processing multibandInfoList for SIB 1. It should be understood that the flowchart 500 is exemplary and may be simplified for the purpose of description herein.
[0047] For each freqBandIndicator 502 on the multibandInfoList, the UE may determine whether it supports the frequency band 504. If it does not, it moves on to the next freqBandIndicator until it exhausts the list. If the frequency band is supported, the UE determines whether the frequency band is already on the priority band list in the database, e.g., whether it matches the frequency band from Figure 4 If it is, then the band does not need to be added to the database again (thus avoiding duplication in order to shorten the priority band list), but if it is not, then the band is added to the priority band list in the database 508. This is repeated until all bands from freqBandIndicator are processed 510.
[0048] Figure 6 The diagram shows Figure 3 Flowchart 600 for deriving priority bands from SIB 5 is shown in 308 of FIG. It is to be understood that flowchart 600 is exemplary and may be simplified for the purposes of description herein.
[0049] For each Evolved Absolute Radio Frequency Channel Number (EARFCN) of the "dl-CarrierFreq" in the "interFreqCarrierFreqList" IE, the UE performs processing 604 for each EARFCN, namely deriving a priority frequency band from the IE, which may be Figure 7See more details in . The UE may then determine whether SIB5 contains an associated "multiBandInfoList" 606, and if it does not, it may use the same Figure 5 The multiBandInfolist is processed in a similar manner as shown in 608. Each EARFCN is processed in this manner until the EARFCN is exhausted 610.
[0050] Figure 7 The diagram shows Figure 6 604 in the flowchart 700 corresponding to the processing of each EARFCN. It should be understood that the flowchart 700 is exemplary and may be simplified for the purpose of description herein.
[0051] For each EARFCN 702, the EARFCN is mapped to its frequency band 704. The UE then determines whether it supports this frequency band 706, and if it does not, it determines whether the frequency band is already in a database containing a list of prioritized frequency bands 708. If the band is not in the database, the band is added 710.
[0052] Figure 8 The diagram shows Figure 3 Flowchart 800 of the processing of the frequency of interest shown in 312 of FIG. It is to be understood that flowchart 800 is exemplary and may be simplified for the purpose of description herein.
[0053] As previously indicated, the frequencies of interest may include, for example, frequencies for transmitting MBMS, cell frequencies for CSG cells, and the like. For each frequency of interest 802, the frequency is first mapped to its corresponding frequency band 804 so that the UE can determine whether it supports the corresponding frequency band 806. If the corresponding frequency band is supported by the UE, the UE determines whether it is already in the priority frequency band list in the database 808. If not, the corresponding frequency band is added to the head (i.e., front end) of the priority frequency band list 810. If the corresponding frequency band is already on the list, i.e., the same frequency band is already on the list, it is moved to the head of the priority list 812, and the corresponding (or same) frequency band is discarded to avoid duplication of the same frequency band.
[0054] Fig. 9 is a flow chart 900 illustrating the derivation of frequency band from SIB 19 when the UE is in UTRAN mode. It is to be understood that flow chart 900 is exemplary and may be simplified for the purpose of description herein.
[0055] For each available EARFCN 902 in the "eutra-FrequencyAndPriorityInfo(Extension)List", the EARFCN is represented by Figure 7904. After the EARFCN is processed, the UE determines whether it has received the associated "multipleEutraFrequencyInfo(Extension)List" 906, and if so, it Figure 5 This list is processed in the manner shown in 908. The UE repeats this process until all frequency bands of the EARFCN obtained from SIB 19 are determined 910.
[0056] Fig.10 1 is a flowchart 1000 illustrating the application of the assembled priority bands in forming a priority band list to be sent to the network. It is to be understood that the flowchart 1000 is exemplary and thus may be simplified for the purpose of description herein.
[0057] The RAN, such as an LTE RAN or a 3G RAN, may trigger the UE to include UE-EUTRA (or UTRA) capabilities in any uplink message 1002. For example, this may be done when the eNB sends a UE capability query to the UE (see Fig.16 ). When triggered, the UE may determine whether the priority band list stored on its database is valid 1004, and if so, it may construct a response regarding the UE's capabilities (in EUTRA or UTRA) based on the priority band list 1006. If the priority band list is no longer valid (e.g., the UE has camped on a new cell and has not updated its priority band list), the construction of the UE's capabilities may be performed according to the 3GPP standard 1008. In either case, once the UE's capabilities have been constructed, an uplink message may be sent back to the network 1010.
[0058] Fig.11 It is shown based on Figure 3-Figure 9 A flowchart 1100 of EUTRA capability of a UE is constructed based on a priority band list of a database assembled in the manner shown. It is to be understood that the flowchart 1100 is exemplary and can be simplified for the purpose of description here. For example, the flowchart 1100 demonstrates the case where the UE is in E-UTRAN (i.e., LTE) mode, but it is to be understood that a similar process can be applied to a UE in UTRAN (i.e., 3G) mode.
[0059] In 1102, the UE sets the content of "supportedBandListEUTRA(-v9e0 / -v1250)" to consist of the bands in the derived priority band list. In 1104, the UE sets the content of "bandListEUTRA" to consist of the bands in the derived priority band list. In 1106, the UE sets the content of "supportedBandCombination(Add-r11 / Add-v11d0 / Add-v1250 / Add-v1270 / Ext / -v1090 / -v10i0 / -v1130 / -v1250 / -v1270)" to consist of the bands in the derived priority band list according to the order specified in the standard. In 1108, the UE sets the content of other band-related IEs to consist of information related to the bands in the derived priority band list. In 1110, the UE sets the content of other IEs according to the 3GPP standard and encodes the message for uplink transmission.
[0060] In another aspect of the present disclosure, the UE may be configured to set a limit on the number of frequency bands it reports back to the network in the uplink. Thus, flow chart 1100 may be used to implement a priority for the UE's capability information to be included in reports back to the network, where frequency bands lower in the priority list may be omitted from reports sent to the network.
[0061] Fig.12 1 is a flowchart 1200 illustrating the replenishment of the priority frequency band. It is to be understood that the flowchart 1200 is exemplary and may be simplified for the purpose of the description herein. In addition, it is to be understood that the flowchart 1100 corresponds to Figure 1 and Figure 2 of 206.
[0062] After receiving the measurement configuration from the network 1202, for example during handover, the UE determines the measurement object 1204 indicating the valid EARFCN and Figure 7 EARFCN 1206 is processed in the manner shown in FIG.
[0063] Fig.13 A radio access network 1300 in one aspect of the present disclosure is shown. The network 1300 may be an LTE network including a UE 1302 and base stations 1310-1312. The base stations 1310-1312 may be LTE base stations (i.e., eNodeBs, eNBs) and may provide coverage to cells 1320 and 1322, respectively. In addition, the cells 1320-1322 may be sectorized, i.e., comprised of multiple LTE cells. Although shown in the network 1300 as having clear boundaries, it is understood that the cells 1320-1322 may have overlapping coverage with adjacent cells.
[0064] UE 1302 may exchange uplink 1350u and / or downlink 1350d data with base station 1310. For example, UE 1302 may camp on cell 1320 via base station 1310. In addition, at least one of UE 1302 or base station 1310 may be configured according to a multiple input multiple output (MIMO) scheme, wherein a channel between the two may include multiple MIMO channels, each MIMO channel corresponding to a unique path between a transmit antenna of base station 1310 and a receive antenna of UE 1302. After moving to cell 1322, the UE may be configured to perform APBD again in order to update its priority band list.
[0065] Fig.14 14 is a message sequence chart (MSC) 1400 of a scenario during which the APBD method of the present disclosure is applied. It is to be understood that the MSC 1400 is exemplary and may be simplified for the purpose of description herein.
[0066] MSC 1400 shows an exchange of RRC signaling between the UE and the eNB, referred to as UE capability transfer. The serving eNB queries the UE about its radio access capabilities in a UE capability query 1404. Before responding, the UE forms its response 1404b based on the priority band list according to the APBD method of the present disclosure. In one aspect of the present disclosure, the UE may perform acquisition of priority bands 1402a in anticipation of receiving the query 1404 from the eNB. In either case, the UE sends UE capability information 1406 back to the eNB based on the priority band list assembled by the APBD method.
[0067] Fig.15 1 shows the internal configuration of UE 1500 which can be configured to perform the APBD of the present disclosure. Fig.15 As shown in , UE 1500 may include an antenna system 1502, a radio frequency (RF) transceiver 1504, a baseband modem 1506 (including a physical layer processing circuit 1508 and a controller 1510), a data source 1512, a memory 1514, and a data sink 1516. Fig.15Although not explicitly shown, UE 1500 may include one or more additional hardware, software and / or firmware components (e.g., processor / microprocessor, controller / microcontroller, other dedicated or general-purpose hardware / processor / circuitry, etc.), (one or more) peripheral devices, memory, power supply, (one or more) external device interfaces, (one or more) subscriber identify modules (SIM), user input / output devices ((one or more) displays, (one or more) keypads, (one or more) touch screens, (one or more) speakers, (one or more) external buttons, (one or more) cameras, (one or more) microphones, etc.), etc.
[0068] As an abbreviated operational overview, UE 1500 may transmit and receive radio signals over one or more radio access networks (RANs) (e.g., LTE RANs). Baseband modem 1506 may direct such communication functions of UE 1500 according to communication protocols associated with each RAN, and may perform control over antenna system 1502 and RF transceiver 1504 to transmit and receive radio signals according to formatting and scheduling parameters defined by each communication protocol.
[0069] UE 1500 may transmit and receive radio signals using antenna system 1502, which may be a single antenna or an antenna array consisting of multiple antennas and may additionally include analog antenna combining and / or beamforming circuits. The receive path (RX) of RF transceiver 1504 may receive analog RF signals from antenna system 1502 and perform analog and digital RF front-end processing on the analog RF signals to generate digital baseband samples (e.g., in-phase / quadrature (IQ) samples) to provide to baseband modem 1506. RF transceiver 1504 may accordingly include analog and digital receive circuits, including amplifiers (e.g., low noise amplifiers (LNA)), filters, RF demodulators (e.g., RF IQ demodulators) and analog-to-digital converters (ADCs) to convert received RF signals into digital baseband samples. In the transmit path (TX), the RF transceiver 1504 may receive digital baseband samples from the baseband modem 1506 and perform analog and digital RF front-end processing on the digital baseband samples to generate analog RF signals to provide to the antenna system 1502 for wireless transmission. The RF transceiver 1504 may thus include analog and digital transmit circuits, including amplifiers (e.g., power amplifiers (PA)), filters, RF modulators (e.g., RF IQ modulators), and digital-to-analog converters (DACs) to mix the digital baseband samples received from the baseband modem 1506 to generate analog RF signals for wireless transmission by the antenna system 1502. The baseband modem 1506 may control RF transmission and reception of the RF transceiver 1504, including specifying transmit and receive radio frequencies for operation of the RF transceiver 1504.
[0070] like Fig.15As shown in , the baseband modem 1506 may include a physical layer processing circuit 1508, which may perform physical layer (i.e., layer 1) transmission and reception processing to prepare outgoing transmission data provided by the controller 1510 for transmission via the RF transceiver 1504 and to prepare incoming reception data provided by the RF transceiver 1504 for processing by the controller 1510. The physical layer processing circuit 1510 may accordingly perform one or more of the following: channel estimation, adaptive filtering, error detection, forward error correction encoding / decoding, channel coding and interleaving, physical channel modulation / demodulation, physical channel mapping, radio measurement and search, frequency and time synchronization, antenna diversity processing, power control and weighting, rate matching, retransmission processing, etc. The physical layer processing circuit 1508 may be structurally implemented as hardware logic, such as an integrated circuit or FPGA, as software logic, such as a program code defining operations, control and / or I / O instructions stored in a non-transitory computer-readable storage medium and executed on a processor, or as a combination of hardware and software logic. Although in Fig.15 Although not explicitly shown in the figure, the physical layer processing circuit 1508 may include a control circuit, such as a processor, which is configured to control various hardware and software processing components of the physical layer processing circuit 1508 according to the physical layer control logic defined by the communication protocol for the relevant radio access technology (RAT). Fig.15 Although depicted as a single component in FIG. 1 , the physical layer processing circuitry 1508 may be collectively comprised of separate portions of physical layer processing circuitry, with each respective portion dedicated to physical layer processing for a particular RAT.
[0071] The physical layer processing circuit 1508 may include hardware and / or software to implement the APBD method of the present disclosure.
[0072] UE 1500 may be configured to operate according to one or more RATs, which may be directed by controller 1510. Controller 1510 may thus be responsible for controlling the radio communication components (antenna system 1502, RF transceiver 1504, and physical layer processing circuit 1508) of UE 1500 according to the communication protocol of each supported RAT, and accordingly may represent the access layer (Access Stratum, AS) and non-access layer (Non-Access Stratum, NAS) (also covering layer 2 and layer 3) of each supported RAT. Controller 1510 may be structurally implemented as a protocol processor, which is configured to execute protocol software (such as Fig.15The controller memory MEM shown in the figure retrieves), such as hardware and / or software that implements the APBD method of the present disclosure, and then controls the radio communication components of the UE 1500 to send and receive communication signals according to the corresponding protocol control logic defined in the protocol software.
[0073] The controller 1510 can therefore be configured to manage the radio communication functions of the UE 1500 in order to communicate with various radio and core network components of the radio communication network, and accordingly can be configured according to the communication protocols for both the LTE network and the GSM / UMTS traditional network. The controller 1510 can either be a unified controller that is overall responsible for all supported RATs (e.g., LTE and GSM / UMTS), or can be composed of multiple separate controllers, each of which is a dedicated controller for a specific RAT, such as a dedicated LTE controller and a dedicated traditional controller (or a dedicated LTE controller, a dedicated GSM controller, and a dedicated UMTS controller). In any case, the controller 1510 can be responsible for directing the radio communication activities of the UE 1500 according to the communication protocols of the LTE and traditional networks. As previously described with respect to the physical layer processing circuit 1508, one or both of the antenna system 1502 and the RF transceiver 1504 can be similarly divided into multiple dedicated components, each of which corresponds to one or more of the supported RATs. Depending on the details of each such configuration and the number of supported RATs, the controller 1510 may be configured to control the radio communication operations of the UE 1500 according to a master / slave RAT hierarchy or a multi-SIM scheme.
[0074] UE 1500 may also include a data source 1512, a memory 1514, and a data sink 1516, wherein the data source 1510 may include a source of communication data above the controller 1510 (i.e., above the NAS / layer 3), and the data sink 1516 may include a destination of communication data above the controller 1510 (i.e., above the NAS / layer 3). This may include, for example, an application processor of the UE 1500, which may be configured to execute various applications and / or programs of the UE 1500 at an application layer of the UE 1500, such as an operating system (OS), a user interface (UI) for supporting user interaction with the UE 1500, and / or various user applications. The application processor may interface with the baseband modem 1506 (as the data source 1512 / data sink 1516) as an application layer to send and receive user data, such as voice data, audio / video / image data, messaging data, application data, basic Internet / web access data, etc., over the radio network connection(s) provided by the baseband modem 1506. The data source 1512 and the data sink 1516 may also represent various user input / output devices of the UE 1500, such as display(s), keypad(s), touchscreen(s), speaker(s), external button(s), camera(s), microphone(s), etc., which may allow the user of the UE 1500 to control various communication functions of the UE 1500 associated with the user data.
[0075] The memory 1514 may include a memory component of the UE 1500, such as a hard drive or another such persistent storage device. Fig.15 It is not clearly described, but Fig.15 The various other components of the UE 1500 shown in FIG. 1 may also each include integrated persistent and non-persistent memory components, eg, for storing software program code, buffering data, and the like.
[0076] Fig.16 A flowchart 1600 is shown describing a process for reporting frequency bands supported by a communication device to a network. It is to be understood that the flowchart 1600 is exemplary and may be simplified for the purposes of description herein.
[0077] In 1602, the communication device obtains information from the network. This obtaining may include receiving SIBs broadcast from the network, such as SIBs 1, 5, and / or 19. In 1604, the communication device may assemble a database including a plurality of frequency bands derived from the information obtained from the network.
[0078] In 1606, the communication device creates a priority frequency band list using extraction parameters, wherein the priority frequency band list is composed of one or more frequency bands from a plurality of frequency bands in a database. The communication device may be configured to perform 1606 simultaneously with 1604. The extraction parameters may include reduction parameters and / or priority parameters. The communication device is configured to implement these parameters to avoid the repeated frequency bands in the priority frequency band list and / or to promote the frequency bands to a higher priority (i.e., move upward) in the priority frequency band list. The frequency band may be subject to two parameters, such as when the frequency band is already on the list, the repeated frequency band may be eliminated, but the frequency band already on the list may be promoted to a higher priority. In addition, the extraction parameters may include a restriction parameter, which limits the number of frequency bands to be reported to the network to a certain value. This value may be based on the length of the report to be transmitted to the network by uplink (e.g., based on the length of "UE capability information") and / or the data size in order to ensure that the highest priority support frequency bands are reported to the network.
[0079] The communication device reports the priority frequency band list to the network at 1608. For example, the communication device may report the priority frequency band list in response to a trigger, such as a network request.
[0080] In Example 1, a method for a communication device to determine one or more supported frequency bands to report to a network includes: obtaining information from the network; assembling a database, the database including multiple frequency bands derived from the information obtained from the network; creating a priority frequency band list using extracted parameters, wherein the priority frequency band list is composed of one or more frequency bands from multiple frequency bands in the database; and reporting the priority frequency band list to the network.
[0081] In Example 2, the subject matter of Example 1 may include, wherein the extracting parameters include reducing parameters.
[0082] In Example 3, the subject matter of Example 2 may include, wherein the reduction parameter is configured to eliminate duplication of frequency bands in the prioritized frequency band list.
[0083] In Example 4, the subject matter of Examples 1-3 may include, wherein the extraction parameter includes a priority parameter.
[0084] In Example 5, the subject matter of Example 4 may include, wherein the priority parameter is configured to reprioritize frequency bands in the priority frequency band list.
[0085] In Example 6, the subject matter of Examples 1-5 may include: receiving a measurement configuration for a corresponding frequency from a network; mapping the corresponding frequency to a corresponding frequency band; determining whether the corresponding frequency band is supported by the communication device; and determining whether the corresponding frequency band is in a database.
[0086] In Example 7, the subject matter of Example 6 may include, wherein when the corresponding frequency band is not in the database, further comprising adding the frequency band to the database, or, wherein when the corresponding frequency band is in the database, discarding the corresponding frequency.
[0087] In Example 8, the subject matter of Examples 1-7 may include triggering a report to the network in response to the network request.
[0088] In Example 9, the subject matter of Example 8 may include, wherein the network request comprises a user equipment (UE) capability query.
[0089] In Example 10, the subject matter of Example 9 may include sending UE capability information in response to a UE capability query, wherein the UE capability information includes a prioritized frequency band list.
[0090] In Example 11, the subject matter of Example 10 may include, wherein the UE capability information includes E-UTRAN information.
[0091] In Example 12, the subject matter of Example 8 may include, wherein the network request comprises a radio resource control (RRC) connection setup message.
[0092] In Example 13, the subject matter of Example 12 may include sending an RRC connection setup complete message in response to the RRC connection setup message, wherein the RRC connection setup complete message includes the priority frequency band list.
[0093] In Example 14, the subject matter of Examples 1-13 may include, wherein the information broadcast from the network includes information from at least one of system information block (SIB) 1 or SIB 5.
[0094] In Example 15, the subject matter of Example 14 may include obtaining one or more frequencies from a freqBandIndicator component of SIB 1.
[0095] In Example 16, the subject matter of Example 15 may include determining whether one or more frequencies are supported by the communication device.
[0096] In Example 17, the subject matter of Example 16 may include adding the one or more frequencies to a database of priority frequencies.
[0097] In Example 18, the subject matter of Examples 14-17 may include obtaining at least one additional frequency from a multiBandList component of SIB 1.
[0098] In Example 19, the subject matter of Example 18 may include determining whether the at least one additional frequency is supported by the communication device.
[0099] In Example 20, the subject matter of Example 19 may include determining whether the at least one additional frequency is in the database of priority frequencies.
[0100] In Example 21, the subject matter of Example 20 may include adding at least one additional frequency to the database of priority frequencies.
[0101] In Example 22, the subject matter of Examples 1-21 may include obtaining a second set of frequencies from the SIB 5 component, wherein the second set includes one or more frequencies.
[0102] In Example 23, the subject matter of Example 22 may include, wherein the SIB 5 component includes interFreqCarrierFreqList.
[0103] In Example 24, the subject matter of Example 23 may include obtaining an evolved absolute radio frequency channel number (EARFCN).
[0104] In Example 25, the subject matter of Example 24 may include mapping the EARFCN to a corresponding frequency band.
[0105] In Example 26, the subject matter of Example 25 may include determining whether the corresponding frequency band is supported by the communication device.
[0106] In Example 27, the subject matter of Example 26 may include determining whether the corresponding frequency band is in a database of priority frequencies.
[0107] In Example 28, the subject matter of Example 27 may include adding the corresponding frequency band to a database of priority frequencies.
[0108] In Example 29, the subject matter of Examples 22-28 may include obtaining at least one additional frequency from a multiBandList component of SIB 5.
[0109] In Example 30, the subject matter of Example 29 may include determining whether at least one additional frequency is supported by the communication device.
[0110] In Example 31, the subject matter of Example 30 may include determining whether the at least one additional frequency is in a database of priority frequencies.
[0111] In Example 32, the subject matter of Example 31 may include adding at least one additional frequency to the database of priority frequencies.
[0112] In Example 33, the subject matter of Examples 1-32 may include obtaining one or more supplemental frequencies from an additional source. The additional source may be, for example, from a memory component in the communication device or from a source that is readily accessible to the communication device.
[0113] In Example 34, the subject matter of Example 33 may include mapping one or more supplemental frequencies to their corresponding supplemental frequency bands.
[0114] In Example 35, the subject matter of Example 34 may include determining whether the communication device supports the corresponding supplemental frequency band.
[0115] In Example 36, the subject matter of Example 35 may include determining whether the corresponding supplemental frequency band is in a database of priority frequencies.
[0116] In Example 37, the subject matter of Example 36 may include adding the corresponding supplemental frequency band to the database of priority frequencies.
[0117] In Example 38, the subject matter of Example 35 may include, wherein when the corresponding supplementary frequency band is in the database of priority frequencies, moving the corresponding supplementary frequency band to the head of the list of priority frequencies.
[0118] In Example 39, the subject matter of Examples 1-38 may include obtaining one or more secondary frequencies from SIB 19.
[0119] In Example 40, the subject matter of Examples 1-39 may include creating the prioritized frequency band list based on a database includes setting content of one or more uplinks to include only frequency bands from the database.
[0120] In Example 41, the subject matter of Example 40 may include setting the content of "supportedBandListEUTRA" in one or more uplinks to include only frequency bands from a database.
[0121] In Example 42, the subject matter of Examples 40-41 may include setting the content of "bandListEUTRA" in one or more uplinks to include only frequency bands from a database.
[0122] In Example 43, the subject matter of Examples 40-42 may include setting the content of "supportedBandCombination" in one or more uplinks to include only frequency bands from a database.
[0123] In Example 44, the subject matter of Examples 1-43 may include, wherein the database includes at least one frequency stored on a memory component of the communication device.
[0124] In Example 45, the subject matter of Example 44 may include, wherein the at least one frequency stored on the memory component of the communication device is selected from the group consisting of Multimedia Broadcast Multicast Service (MBMS) and Closed Subscriber Group (CSG) cells.
[0125] In Example 46, a signal processing circuit is used to determine one or more supported frequencies for a communication device to report to a network, and the signal processing circuit is configured to: obtain information from the network; assemble a database of priority frequencies, the database comprising multiple frequency bands derived from the information obtained from the network; create a priority frequency band list using extraction parameters, wherein the priority frequency band list is composed of one or more frequency bands from the multiple frequency bands in the database; and report the priority frequency band list to the network.
[0126] In Example 47, the subject matter of Example 46 may include, wherein the extracting parameters include reducing parameters.
[0127] In Example 48, the subject matter of Example 47 may include, wherein the reduction parameter is configured to eliminate duplication of frequency bands in the priority frequency band list.
[0128] In Example 49, the subject matter of Examples 46-48 may include, wherein the extraction parameters include a priority parameter.
[0129] In Example 50, the subject matter of Example 49 may include, wherein the priority parameter is configured to reprioritize frequency bands in the priority frequency band list.
[0130] In Example 51, the subject matter of Examples 46-50 may include the signal processing circuit being further configured to: receive a measurement configuration for a frequency from a network; map the frequency to a frequency band; determine whether the frequency band is supported by the communication device; and determine whether the frequency band exists in a database.
[0131] In Example 52, the subject matter of Example 51 may include, wherein, when the corresponding frequency band is not in the database, the signal processing circuit is further configured to add the frequency band to the database, or, wherein when the corresponding frequency band is in the database, the signal processing circuit is further configured to discard the corresponding frequency.
[0132] In Example 53, the subject matter of Examples 46-52 may include the signal processing circuit being further configured to trigger a report to the network in response to the network request.
[0133] In Example 54, the subject matter of Example 53 may include, wherein the network request comprises a user equipment (UE) capability query.
[0134] In Example 55, the subject matter of Example 54 may include the signal processing circuit being further configured to send UE capability information in response to the UE capability query, wherein the UE capability information includes the prioritized frequency band list.
[0135] In Example 56, the subject matter of Example 55 may include, wherein the UE capability information includes E-UTRAN information.
[0136] In Example 57, the subject matter of Example 53 may include, wherein the network request comprises a radio resource control (RRC) connection setup message.
[0137] In Example 58, the subject matter of Example 57 may include that the signal processing circuit is further configured to send an RRC connection setup complete message in response to the RRC connection setup message, wherein the RRC connection setup complete message includes the priority frequency band list.
[0138] In Example 59, the subject matter of Examples 46-58 may include, wherein the information broadcast from the network includes information from at least one of system information block (SIB) 1 or SIB 5.
[0139] In Example 60, the subject matter of Example 59 may include the signal processing circuit being further configured to obtain the one or more frequencies from a freqBandIndicator component of SIB 1.
[0140] In Example 61, the subject matter of Example 60 may include the signal processing circuit being further configured to determine whether the one or more frequencies are supported by the communication device.
[0141] In Example 62, the subject matter of Example 61 may include the signal processing circuit being further configured to add the one or more frequencies to a database of priority frequencies.
[0142] In Example 63, the subject matter of Example 59 may include the signal processing circuit being further configured to obtain at least one additional frequency from the multiBandList component of SIB 1.
[0143] In Example 64, the subject matter of Example 63 may include the signal processing circuit being further configured to determine whether the at least one additional frequency is supported by the communication device.
[0144] In Example 65, the subject matter of Example 64 may include the signal processing circuit being further configured to determine whether the at least one additional frequency is in the database of priority frequencies.
[0145] In Example 66, the subject matter of Example 65 may include the signal processing circuit being further configured to add the at least one additional frequency to the database of priority frequencies.
[0146] In Example 67, the subject matter of Examples 46-66 may include the signal processing circuit being further configured to obtain a second set of frequencies from the SIB 5 component, wherein the second set includes one or more frequencies.
[0147] In Example 68, the subject matter of Example 67 may include, wherein the SIB 5 component includes interFreqCarrierFreqList.
[0148] In Example 69, the subject matter of Example 68 may include the signal processing circuit being further configured to obtain an evolved absolute radio frequency channel number (EARFCN).
[0149] In Example 70, the subject matter of Example 69 may include the signal processing circuit being further configured to map the EARFCN to a corresponding frequency band.
[0150] In Example 71, the subject matter of Example 70 may include that the signal processing circuit is further configured to determine whether the corresponding frequency band is supported by the communication device.
[0151] In Example 72, the subject matter of Example 71 may include the signal processing circuit being further configured to determine whether the corresponding frequency band is in a database of priority frequencies.
[0152] In Example 73, the subject matter of Example 72 may include the signal processing circuit being further configured to add the corresponding frequency band to a database of priority frequencies.
[0153] In Example 74, the subject matter of Examples 67-73 may include the signal processing circuit being further configured to obtain at least one additional frequency from a multiBandList component of SIB 5.
[0154] In Example 75, the subject matter of Example 74 may include the signal processing circuit being further configured to determine whether the at least one additional frequency is supported by the communication device.
[0155] In Example 76, the subject matter of Example 75 may include the signal processing circuit being further configured to determine whether the at least one additional frequency is in the database of priority frequencies.
[0156] In Example 77, the subject matter of Example 76 may include the signal processing circuit being further configured to add the at least one additional frequency to the database of priority frequencies.
[0157] In Example 78, the subject matter of Examples 46-77 can include the signal processing circuit being further configured to obtain the one or more supplemental frequencies from an additional source, such as a memory component in the communication device or a source readily accessible to the communication device.
[0158] In Example 79, the subject matter of Example 78 may include the signal processing circuit being further configured to map the one or more supplemental frequencies to their corresponding supplemental frequency bands.
[0159] In Example 80, the subject matter of Example 79 may include the signal processing circuit being further configured to determine whether the communication device supports the corresponding supplemental frequency band.
[0160] In Example 81, the subject matter of Example 80 may include the signal processing circuit being further configured to determine whether the corresponding supplemental frequency band is in a database of priority frequencies.
[0161] In Example 82, the subject matter of Example 81 may include the signal processing circuit being further configured to add the corresponding supplemental frequency band to the database of priority frequencies.
[0162] In Example 83, the subject matter of Example 82 may include, wherein when the corresponding supplemental frequency band is in the database of priority frequencies, the circuitry is further configured to move the corresponding supplemental frequency band to the head of the list of priority frequencies.
[0163] In Example 84, the subject matter of Examples 46-83 may include the signal processing circuit being further configured to obtain the one or more auxiliary frequencies from SIB 19.
[0164] In Example 85, the subject matter of Examples 46-84 may include the signal processing circuit being further configured to create a priority frequency band list based on a database by setting content of the one or more uplinks to include only frequency bands from the database.
[0165] In Example 86, the subject matter of Example 85 may include the signal processing circuit being further configured to set the content of "supportedBandListEUTRA" in one or more uplinks to include only frequency bands from the database.
[0166] In Example 87, the subject matter of Examples 85-86 may include the signal processing circuit being further configured to set the content of "bandListEUTRA" in one or more uplinks to include only frequency bands from the database.
[0167] In Example 88, the subject matter of Examples 85-87 may include the signal processing circuit being further configured to set the content of "supportedBandCombination" in one or more uplinks to include only frequency bands from a database.
[0168] In Example 89, the subject matter of Examples 46-88 may include the database comprising at least one frequency stored on a memory component accessible to the signal processing circuit.
[0169] In Example 90, the subject matter of Example 89 may include, wherein the at least one frequency stored on the memory component accessible to the signal processing circuit is selected from the group consisting of Multimedia Broadcast Multicast Service (MBMS) and Closed Subscriber Group (CSG) cells.
[0170] In Example 91, the subject matter of Examples 46-90 may include the signal processing circuit being operatively coupled to a transceiver of the communication device, the transceiver being configured to communicate with a network.
[0171] In Example 92, a communication device is configured to determine one or more supported frequency bands to report to a network, the communication device comprising: a transceiver configured to communicate with the network; a baseband unit operatively coupled to the transceiver and configured to: obtain information from the network via the transceiver; assemble a database comprising a plurality of frequency bands derived from the information obtained from the network or at least one frequency stored on a memory component of the communication device; create a priority frequency band list using extraction parameters, wherein the priority frequency band list consists of one or more frequency bands from a plurality of frequency bands in the database; and report the priority frequency band list to the network via the transceiver; and a memory configured to store the database.
[0172] In Example 93, the subject matter of Example 92 may include, wherein the extracting parameters include reducing parameters.
[0173] In Example 94, the subject matter of Example 93 may include, wherein the reduction parameter is configured to eliminate duplication of frequency bands in the priority frequency band list.
[0174] In Example 95, the subject matter of Examples 92-94 may include, wherein the extraction parameters include a priority parameter.
[0175] In Example 96, the subject matter of Example 95 may include, wherein the priority parameter is configured to reprioritize frequency bands in the priority frequency band list.
[0176] In Example 97, the subject matter of Examples 92-96 may include the baseband unit being further configured to: receive a measurement configuration for a frequency from a network; map the frequency to a frequency band; determine whether the frequency band is supported by the communication device; and determine whether the frequency band exists in a database.
[0177] In Example 98, the subject matter of Example 97 may include, wherein, when the corresponding frequency band is not in the database, the baseband unit is further configured to add the frequency band to the database, or, wherein when the corresponding frequency band is in the database, the baseband unit is further configured to discard the corresponding frequency.
[0178] In Example 99, a communication device has a signal processing component configured to implement the method of any one of Examples 1-45.
[0179] In Example 100 , a computer readable medium includes program instructions that, when executed by a processor of a device, cause the device to implement the method of any one of Examples 1-45.
[0180] Although the above description and the associated drawings may depict electronic device components as separate elements, those skilled in the art will appreciate the various possibilities of combining or integrating discrete elements into a single element. This may include combining two or more circuits to form a single circuit, mounting two or more circuits on a common chip or housing to form an integrated element, executing discrete software components on a common processor core, and the like. Conversely, those skilled in the art will recognize the possibility of separating a single element into two or more discrete elements, such as splitting a single circuit into two or more separate circuits, separating a chip or housing into discrete elements originally provided thereon, separating a software component into two or more parts and executing each part on a separate processor core, and the like.
[0181] It is to be understood that the implementation of the method described in detail herein is illustrative, and thus is understood to be implemented in the corresponding device. Similarly, it is to be understood that the implementation of the device described in detail herein is understood to be implemented as the corresponding method. It is thus to be understood that the device corresponding to the method described in detail herein may include one or more components configured to perform each aspect of the related method.
[0182] All abbreviations defined in the above description also apply in all claims included herein.
[0183] Although the present invention has been specifically shown and described with reference to specific embodiments, it will be understood by those skilled in the art that various changes in form and details may be made thereto without departing from the spirit and scope of the present invention as defined in the appended claims. The scope of the present invention is thus indicated by the appended claims, and therefore it is intended to include all changes within the equivalent meaning and scope of the claims.
Claims
1. A signal processing circuit for determining one or more supported frequencies of a communication device to report to a network, the signal processing circuit being configured to perform the following operations: obtaining information from the network; assembling a database of priority frequencies, the database comprising a plurality of frequency bands derived from said information obtained from said network; creating a prioritized frequency band list using the extracted parameters, wherein the prioritized frequency band list is composed of one or more frequency bands from the plurality of frequency bands in the database; and reporting the priority frequency band list to the network, The extraction parameters include a reduction parameter and a priority parameter, the reduction parameter is configured to eliminate duplication of frequency bands in the priority frequency band list, and the priority parameter is configured to re-prioritize the frequency bands in the priority frequency band list, And wherein the signal processing circuit is further configured to: when a frequency band is already in the priority frequency band list, eliminate duplicate frequency bands and increase the priority of the frequency band already in the priority frequency band list.
2. The signal processing circuit according to claim 1, wherein the signal processing circuit is further configured to perform the following operations: receiving a measurement configuration for a frequency from the network; mapping the frequencies to frequency bands; determining whether the frequency band is supported by the communication device; and A determination is made as to whether the frequency band exists in the database.
3. The signal processing circuit according to claim 2, wherein: When the corresponding frequency band is not in the database, the signal processing circuit is further configured to add the frequency band to the database, or, when the corresponding frequency band is in the database, the signal processing circuit is further configured to discard the corresponding frequency. 4 . The signal processing circuit of claim 1 , further configured to trigger the report to the network in response to a network request.
5. The signal processing circuit according to claim 4, wherein the signal processing circuit is further configured to send UE capability information in response to the network request, wherein: The UE capability information includes the priority frequency band list.
6. The signal processing circuit according to claim 1, wherein: The information broadcast from the network includes information from at least one of system information blocks SIB 1 or SIB 5. 7 . The signal processing circuit of claim 6 , further configured to obtain one or more frequencies from a freqBandIndicator component of SIB 1. 8 .
8. The signal processing circuit of claim 1, further configured to obtain a second set of frequencies from a SIB 5 component, wherein: The second group includes one or more frequencies.
9. The signal processing circuit of claim 1, further configured to obtain one or more supplemental frequencies from additional sources for inclusion in the database.
10. The signal processing circuit according to claim 9, wherein: The additional source is a memory component of the communication device, and at least one of the one or more supplemental frequencies is selected from the group consisting of Multimedia Broadcast Multicast Service (MBMS) and Closed Subscriber Group (CSG) cells.
11. The signal processing circuit of claim 9, further configured to determine whether a corresponding supplemental frequency band of each of the one or more supplemental frequencies is in a database of the priority frequencies, wherein: When the corresponding supplementary frequency band is in the database of priority frequencies, the signal processing circuit is further configured to move the corresponding supplementary frequency band to the head of the priority frequency band list.
12. The signal processing circuit of any one of claims 1-11, further configured to create the priority frequency band list by setting the content of one or more uplinks to include only frequency bands from the assembled database.
13. A communication device configured to determine one or more supported frequencies to report to a network, the communication device comprising: a transceiver configured to communicate with the network; A baseband unit is operatively coupled to the transceiver and is configured to: acquiring information from the network via the transceiver; assembling a database comprising a plurality of frequency bands derived from said information obtained from said network or at least one frequency stored on a memory component of said communication device; creating a prioritized frequency band list using the extracted parameters, wherein the prioritized frequency band list is composed of one or more frequency bands from the plurality of frequency bands in the database; and reporting the priority frequency band list to the network via the transceiver; and a memory configured to store the database, The extraction parameters include a reduction parameter and a priority parameter, the reduction parameter is configured to eliminate duplication of frequency bands in the priority frequency band list, and the priority parameter is configured to re-prioritize the frequency bands in the priority frequency band list, And wherein the baseband unit is further configured to: when a frequency band is already in the priority frequency band list, eliminate duplicate frequency bands and increase the priority of the frequency band already in the priority frequency band list.
14. A method for a communication device to determine one or more supported frequency bands and report to a network, the method comprising: obtaining information from the network; assembling a database comprising a plurality of frequency bands derived from said information obtained from said network; creating a prioritized frequency band list using the extracted parameters, wherein the prioritized frequency band list is composed of one or more frequency bands from the plurality of frequency bands in the database; and reporting the priority frequency band list to the network, The extraction parameters include a reduction parameter and a priority parameter, the reduction parameter is configured to eliminate duplication of frequency bands in the priority frequency band list, and the priority parameter is configured to re-prioritize the frequency bands in the priority frequency band list, And wherein the method further comprises: in the case where the frequency band is already in the priority frequency band list, eliminating duplicate frequency bands and increasing the priority of the frequency band already in the priority frequency band list.
15. The method of claim 14, further comprising: receiving a measurement configuration for a corresponding frequency from the network; Mapping the corresponding frequencies to corresponding frequency bands; determining whether the corresponding frequency band is supported by the communication device; as well as It is determined whether the corresponding frequency band is in the database.
16. The method according to claim 14 or 15, wherein: The database includes one or more supplemental frequencies from a memory component of the communication device, and at least one of the one or more supplemental frequencies is selected from the group consisting of Multimedia Broadcast Multicast Service (MBMS) and Closed Subscriber Group (CSG) cells.
17. A machine-readable medium comprising code, which, when executed, causes a machine to perform the method of any one of claims 14 to 16.