GERAN Frequency Based Insight Delivery To Mobile Devices

Abstract

Network insights may be useful in various communication networks. For example, certain cellular or similar networks may benefit from the delivery of cellular network insights to subscriber devices based on global system for mobile communication (GSM) enhanced data rates for GSM evolution (EDGE) radio access network (GERAN) frequencies. For example, a method can include detecting, by a device, at least one advertised value. The at least one advertised value can be received by the device over a cellular system information message that includes information indicative of radio frequency bands relevant for cell re-selection. One or more of the indicated radio frequency bands can be indicative of the presence of the at least one advertised value. The method can also include extracting, from the at least one advertised value, at least one cellular network insight.

Description

CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application is a continuation-in-part of and claims the benefit and priority of PCT/US2015/041073, filed Jul. 20, 2015, the entirety of which is hereby incorporated herein by reference. This application is also a continuation-in-part of and claims the benefit and priority of Patent Cooperation Treaty (PCT) Patent Application No. PCT/EP2014/069585, filed Sep. 15, 2014, which is hereby incorporated herein by reference in its entirety. This application is additionally related to and claims the benefit and priority of U.S. Provisional Patent Application No. 62/175,676 filed Jun. 15, 2015, which is hereby incorporated herein by reference in its entirety.

BACKGROUND

[0002] 1. Field

[0003] Network insights may be useful in various communication networks. For example, certain cellular or similar networks may benefit from the delivery of cellular network insights to subscriber devices based on global system for mobile communication (GSM) enhanced data rates for GSM evolution (EDGE) radio access network (GERAN) frequencies.

[0004] 2. Description of the Related Art

[0005] The use of mobile wireless devices for sending and/or receiving data is increasing. At the same time, the delivery of video data is consuming a larger and larger share of available wireless capacity, both because of the popularity of video and because video applications inherently consume relatively great amounts of data.

[0006] Various techniques such as media optimization and adaptive streaming servers promise to significantly increase system capacity and video quality in wireless networks such as third generation partnership project (3GPP) long term evolution (LTE) networks. For example, media optimizer and adaptive streaming servers can manage downloading of video to user equipment, such as a camera phone, smart phone, tablet computer, media play with wireless capability, or the like, just in time to be played. Such an approach may avoid waste of resources when a user abandons a video before the video is complete, because the approach can avoid transferring data that will never be used.

[0007] A user may frequently experience a gap in coverage or impaired coverage, so that under some circumstances video will be not be available at the moment it is needed. Delivering data before it is needed, which may be referred to as pre-filling data, can avoid interruption or degradation of video quality. This discussion will be presented primarily in terms of video data, but the mechanisms described here may be applied to any circumstances in which data is delivered as needed in order to use transmission capacity efficiently, but in which conditions are evaluated to determine whether data should be delivered before it is immediately needed.

[0008] The need for pre-filling of data can vary based on the particular circumstances of a user equipment (UE). In addition, turning to the example of video data, much video data can be configured so as to be playable only by a single UE, as in the case in which video is encrypted with a key provided only to a single UE or a few UEs, or in the case in which digital rights management (DRM) is used, so that video is configured to be transferable only to a single UE.

[0009] If video data is to be reliably delivered, however, accommodations may need to be made for areas experiencing poor coverage or significant loads, interfering with the ability of a UE to receive data just in time for playback. Under such circumstances, the UE may benefit from receiving data during times when it may be efficiently delivered, so that the data can be available for playback during a period of slow or no delivery. The control if video transfers can be related to network knowledge sharing, or the sharing of network analytic insights.

[0010] Data analytics insights are transforming various industries by linking these insights with decisions. Network infrastructure can generate network insights, for example, from the evolved node B (eNB), Radio Applications Cloud Server (RACS) and customer experience manager (CEM). These types of insights can be useful to many devices or elements of the network. For instance, this type of information can be useful to mobile applications also known as apps. An app may be considered to be a self-contained program or piece of software designed to fulfill a particular purpose, for example as downloaded by a user to a mobile device. Apps on mobile devices (e.g., smartphones, tablets, other portable computing devices, etc.) may make many decisions, using nuanced and rapidly changing app knowledge.

SUMMARY

[0011] According to certain embodiments, a method can include detecting, by a device, at least one advertised value. The at least one advertised value can be received by the device over a cellular system information message that includes information indicative of radio frequency bands relevant for cell re-selection. One or more of the indicated radio frequency bands can be indicative of the presence of the at least one advertised value. The method can also include extracting, from the at least one advertised value, at least one cellular network insight.

[0012] In certain embodiments, a method can include selecting, by a device, at least one advertised value. The at least one advertised value can be transmitted by the device over a cellular system information message that includes information indicative of radio frequency bands relevant for cell re-selection. One or more of the indicated radio frequency bands can be indicative of the presence of the at least one advertised value. The method can also include transmitting, in association with the at least one advertised value, at least one cellular network insight.

[0013] An apparatus, according to certain embodiments, can include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus at least to detect, by a device, at least one advertised value. The at least one advertised value can be received by the device over a cellular system information message that includes information indicative of radio frequency bands relevant for cell re-selection. One or more of the indicated radio frequency bands can be indicative of the presence of the at least one advertised value. The at least one memory and the computer program code can also be configured to, with the at least one processor, cause the apparatus at least to extract, from the at least one advertised value, at least one cellular network insight.

[0014] An apparatus, in certain embodiments, can include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus at least to select, by a device, at least one advertised value. The at least one advertised value can be transmitted by the device over a cellular system information message that includes information indicative of radio frequency bands relevant for cell re-selection. One or more of the indicated radio frequency bands can be indicative of the presence of the at least one advertised value. The at least one memory and the computer program code can also be configured to, with the at least one processor, cause the apparatus at least to transmit, in association with the at least one advertised value, at least one cellular network insight.

[0015] According to certain embodiments, an apparatus can include means for detecting, by a device, at least one advertised value. The at least one advertised value can be received by the device over a cellular system information message that includes information indicative of radio frequency bands relevant for cell re-selection. One or more of the indicated radio frequency bands can be indicative of the presence of the at least one advertised value. The apparatus can also include means for extracting, from the at least one advertised value, at least one cellular network insight.

[0016] In certain embodiments, an apparatus can include means for selecting, by a device, at least one advertised value. The at least one advertised value can be transmitted by the device over a cellular system information message that includes information indicative of radio frequency bands relevant for cell re-selection. One or more of the indicated radio frequency bands can be indicative of the presence of the at least one advertised value. The apparatus can also include means for transmitting, in association with the at least one advertised value, at least one cellular network insight.

[0017] A computer program product can, in certain embodiments, be encoded with instructions for performing any of the above-described methods.

[0018] A non-transitory computer-readable medium can, according to certain embodiments, be encoded with instructions that, when executed in hardware, perform any of the above-described methods.

BRIEF DESCRIPTION OF THE DRAWINGS

[0019] For proper understanding of the invention, reference should be made to the accompanying drawings, wherein:

[0020] FIG. 1 illustrates a method according to certain embodiments.

[0021] FIG. 2 illustrates a system according to certain embodiments.

DETAILED DESCRIPTION

[0022] Certain embodiments provide a mechanism to enable identifying that subscribers are going to perform a proprietary knowledge sharing protocol between the subscriber device and the network. This knowledge sharing protocol may govern sharing congestion information down to the user equipment (UE), and obtaining advanced knowledge of anticipated user traffic activity up from the UE.

[0023] More particularly, certain embodiments provide for utilizing ARFCN/Carrier/Band(s) that do not exist in order to convey specific network assistance data to UEs. Each UE can have a list of frequencies, such as CarrierFreqsGERAN, which the UE supports. The UE can compare those with frequencies indicated by the network. There may be a number of specific ARFCN-ValueGERAN values which could be indicated over system information block type 7 (SIB7 or SystemInformationBlockType7), which would be ignored by UEs as no UE would support that carrier.

[0024] These unsupported values can be seen, for example, within table 2-2 within 3GPP TS 45.005, where a large number of the n values between zero and 1023 are not valid for any row as per the third column of that table. For example, such AFCN or n values include 125-127, 252-258, 294-305, 341-511, and 886-939.

[0025] The attributes of any such unsupported carrier can be used to convey proprietary information to appropriately configured UEs over SIB7. Unconfigured or normal UEs may ignore the parameters as that frequency is not supported by the UE. In other words, to convey network assistance data, certain embodiments may use a carrier or band or absolute radio frequency channel number (ARFCN) that does not exist within CarrierFreqsInfoList. Additionally, the network may choose among a group of such ARFCN values based on one or more of observations of the current radio conditions, and the neighboring station configurations.

[0026] It is possible that LTE may later define use for additional carriers or bands. Nevertheless, device vendors may implement, within their handsets, an auto network knowledge disable timeout functionality wherein the device can stop extracting network knowledge from the spare bits if more than a threshold number of months have elapsed subsequent to the UE's last software update.

[0027] Similarly, eNB software may implement a timer, such that after a threshold number of months after the latest software update, the eNB will stop utilizing network knowledge over the spare bits.

[0028] There can be up to maxGNFG instances of CarrierFreqsInfoGERAN. In certain embodiments, a setting for the carrierFreqs information element (IE) within an instance of CarrierFreqsInfoGERAN can be used to indicate proprietary usage of that particular instance of CarrierFreqsInfoGERAN. For example, certain embodiments can signal a carrier within carrierFreqs which would not be used in any real deployment. Thus, certain embodiments can use the IEs under the commonInfo IE of that CarrierFreqsInfoGERAN instance to signal the load information. Because there can be up to maxGNFG instances of CarrierFreqsInfoGERAN, SIB7 can be utilized to simultaneously provide usable CarrierFreqsInfoGERAN guidance to UEs on a first carrierFreqs IE while also providing network assistance information over a second carrierFreqs IE within a single SIB7 message.

[0029] For example, ncc-Permitted is an 8-bit string, and consequently can be used to provide 8 bits of load information. In addition, the selection of which of the ARFCN values (not supported by the UEs) is used, may further convey additional bits of network assistance and/or load information.

[0030] In further embodiments, the network can choose to not update the systemInfoValueTag when the changes are made within the network assistance data within the SIB7 message have a lower priority. When the changes in the network assistance data are relatively high priority, then the systemInfoValueTag may be updated.

[0031] Certain embodiments may be configured to avoid inefficiencies by sharing knowledge/preferences between UE/Apps and eNB. Inefficiencies can include eNB inactivity. Thus, in certain embodiments C-DRX decisions can use knowledge of UE traffic preferences. Similarly, UE decisions can use eNB knowledge of congestion. In this discussion, an eNB is provided as one example of an access node. Other kinds of access nodes, such as other kinds of base stations or access points are also permitted.

[0032] This sharing of information may enable a host of things including, for example, improving battery life and capacity, avoiding excess UE connected/modem-on time and excess RRC transitions, and creating numerous additional improvements from joint decision-making

[0033] Certain embodiments may define a protocol for this knowledge sharing. This protocol may relate to radio level messaging, avoiding conflicts with current and future LTE standards releases.

[0034] Furthermore, certain embodiments can work with both idle and connected UEs. In response to the signaled indication of ARFCN/Carrier/Band(s) that do not exist, the UE can convey an uplink (UL) knowledge sharing message to the eNB using an uplink (UL) MAC control element (CE) with a currently reserved index.

[0035] The eNB can transmit downlink (DL) knowledge sharing message with a MAC CE with currently reserved index. This DL message can be sent if eNB receives an UL, with MAC CE reserved index, or if the eNB checks the UE's international mobile station equipment identity (IMIEI) software version (IMEISV).

[0036] Certain embodiments can use indication of GERAN carrier frequencies that are inconsistent with the indicated band. In particular, each UE can have a list of frequencies, for example CarrierFreqsGERAN, which the UE supports. Each UE can compare the supported frequencies with the frequencies indicated by the network.

[0037] In certain embodiments, a specific ARFCN-ValueGERAN value can be indicated over the SIB7. The specific value can be selected based on the fact that it would be ignored by UEs that are unaware of the special meaning of the value, as no UE would support that carrier. Thus, use of the value can avoid disrupting the operation of non-cooperating or otherwise unaware UEs.

[0038] Additionally, the attributes of that unsupported carrier can be used to convey proprietary information to specially configured UEs over SIB7. Other unconfigured or normal UEs may simply ignore the parameters as that frequency is not supported by the UE.

[0039] The operator can configure a different frequency to be used for this mechanism. The frequency can be used under that operator's public land mobile network (PLMN). Device vendors can use that PLMN/frequency combination to find the proprietary information. Optionally, a device can not only evaluate the table from 3GPP TS 45.005, but can further take into account which combinations of PLMN and carrier frequencies can occur. However, in certain embodiments, the device can be preconfigured with information that can obviate the need for such evaluation, such as a list of identified ARFCN values are not used in any PLMN.

[0040] For example, certain embodiments can use an indication of a carrier, band, or ARFCN that does not exist to convey payload. Within CarrierFreqsInfoList there can be up to maxGNFG instances of CarrierFreqsInfoGERAN.

[0041] Certain embodiments can identify a setting for the carrierFreqs IE within an instance of CarrierFreqsInfoGERAN that would indicate proprietary usage of that particular instance of CarrierFreqsInfoGERAN. As mentioned above, this can involve signaling a carrier within carrierFreqs that would not be used in any real deployment.

[0042] Then certain embodiments can use the IEs under the commonInfo IE of that CarrierFreqsInfoGERAN instance to signal the load information. For example, ncc-Permitted is an 8-bit string. This 8-bit string can be encoded in a proprietary way to provide the load information and/or other desired information.

[0043] By tunneling such information over LTE, certain embodiments can convey that the network assistance data is available over the entire cellular coverage area. In contrast, with the use of proprietary signaling over RRC or MAC, the delivery may be repetitively delivered to many different UEs throughout the cell over unicast signaling. In addition, various embodiments described above can work not only for connected UEs but also for idle UEs.

[0044] In addition to the above, there can be additional downlink payload and/or knowledge sharing attributes encoded for example in the 8-bit string. The downlink knowledge sharing messaging can convey one or more specific information elements. These information elements can include one or more of: a short-term or long-term congestion, on one or more of the uplink and the downlink; a short-term or long-term congestion across both up and downlink, which could be a unitless number between one and 8 indicating the congestion state associated with whichever of the two link directions is more congested (this congestion estimate could correspond to a planned bidirectional transfer); an indication of the congestion over alternative wireless technologies, such as Wi-Fi; or an indication of the timescale or cells associated with the congestion estimate provided, for example indicating the timescale associated with the long-term congestion estimate provided over the knowledge sharing protocol.

[0045] These information elements can include an indication of a mobility congestion estimate, for example indicating that this is the likely congestion the UE will encounter if the UE is mobile, based on one or more neighbor/likely handoff cells, as opposed to a congestion estimate which is to be expected by the UE if the UE remains relatively static/in that location.

[0046] These information elements can include an indication of a recommended time for a transfer, for example within a specific time window indicated by the UE.

[0047] These information elements can include an indication of the transfer direction associated with the recommended time for the transfer. Furthermore, these information elements can include an indication of a recommended transfer size, in bytes and/or seconds, associated with the recommended time for the transfer. For example, this could apply in the case where the UE has requested/indicated it plans a particularly large transfer, but the network has identified a smaller uncongested opportunity and has recommended that the UE perform a fraction of the planned transfer during this opportunistic interval.

[0048] These information elements can include one or more of the following: an indication that the recommended time for a transfer corresponds to the anticipated transfer indicated by the UE in the uplink knowledge sharing protocol; an indication of the congestion in the cell resulting from a particular category of UEs, for example an indication of the congestion in the cell resulting from UEs from a particular UE provider or vendor, or corresponding to subscribers which support the knowledge sharing protocol; or an indication of congestion in one or more other cells, for example neighboring cells, or an explicit indication of the congestion in an overlay macro cell, which may be relevant for example when a UE is under a small cell, which is in the middle of the coverage area of the macrocell, and the UE has some mobility.

[0049] These information elements can include an indication of subscriber experience, for example quality of experience (QoE), corresponding to the experience of the lowest quality subscriber experience in that cell, wherein that subscriber is from a particular category of subscribers. For example, the QoE may be the lowest from a particular UE provider or vendor, or among the UEs using the knowledge sharing protocol in that cell or geographic region.

[0050] These information elements can include an indication of the likely sensitivity of the subscriber throughput to the signal strength at the UE. For example, this indication can provide a parameter to the UE which enables the UE to estimate the multiplicative change in the likely throughput achieved as the signal strength (RSRP or RSRQ) changes as the UE moves within that cell, while the cell has a constant level of congestion. In other words the subscriber can use this parameter within a predetermined function to estimate the degree to which changes in signal strength will correlate with faster or slower transfer opportunities.

[0051] These information elements can include any of the following: an indication of the RRC inactivity timer value currently planned to be used by the network/eNB for that UE; an indication of the eNB vendor type and/or knowledge sharing protocol version; or an indication that the UE should wait in idle mode until it enters another cell, at which point it should connect in order to determine the current congestion over the knowledge sharing protocol. The indication to wait in idle mode may further indicate specific neighboring cells, for example cells that are lower congestion, where the UE may use this approach

[0052] These information elements can include an indication of the type of neighboring cells where the subscriber should subsequently attempt to connect to determine the congestion level. For example, the indication may indicate that the subscriber should connect in order to determine the congestion level over the knowledge sharing protocol only within cells with particular configurations, or cells of particular types, for example small cells, femto cells, or macro cells.

[0053] These information elements can include an indication that specific neighboring cells support the knowledge sharing protocol, e.g. using specific references such as cell names or associated cell broadcast information which will enable the UE to later identify that the UE is near such specific cells.

[0054] These information elements can include an indication that the knowledge sharing protocol support at that cell is ending shortly. For example, the indication may indicate the time interval after which the protocol support information should be deleted from the UE and/or the UE operating system/ecosystem.

[0055] These information elements can include the following: an indication to the UE indicating how to estimate the downlink cell congestion from RSRQ, for example compensating for the level of other cell interference also being received in that approximate location; or an indication to the UE indicating how to estimate the uplink cell congestion from the modulation coding sequence (MCS) assigned as a part of uplink grant(s).

[0056] These information elements can include an indication of the degree to which the UE can generate knowledge sharing protocol messaging over the uplink. For example, this indication may prohibit the UEs from transmitting long uplink knowledge sharing messaging in the case where the uplink is congested. This configuration may further be implicit such that the UE automatically determines that it is disallowed from transmitting one or more uplink knowledge sharing messages after it receives a message from the network indicating that the uplink is congested. Furthermore, this portion of the knowledge sharing protocol may prohibit all uplink knowledge sharing messaging, while still indicating that downlink knowledge sharing messaging may occur. Alternatively, this indication may allow the UE to perform messaging which indicates planned transfers, but which disallows providing knowledge sharing inputs on network configuration such as inactivity timer and/or discontinuous reception (DRx). Conversely, this may allow the UE to provide inputs with respect to inactivity timer and/or DRx, but disallow inputs with respect to planned transfers. The network may then configure this downlink indication in order to optimize the network performance, while considering the overhead generated by this uplink knowledge sharing messaging, and the observed benefits generated by this knowledge sharing messaging. Furthermore, the network may disallow this messaging from a subset of the UE devices, for example where the benefit of such messaging is expected to be smaller, or where the UE devices which tend to generate less traffic, or where subscriber device's power preference indicator indicates that performance is more important than conserving power.

[0057] FIG. 1 illustrates a method according to certain embodiments. As shown in FIG. 1, a method can include, at 130, detecting, by a device, at least one advertised value of system information block type seven (SIB7). The at least one advertised value can be received by the device over a cellular system information block message, after having sent by an access node at 120. The access node can select the at least one advertised value of SIB7 at 110, prior to sending at 120.

[0058] The method can further include, at 140, extracting, from the at least one advertised value, at least one cellular network insight, for example a cellular network insight for a cellular network condition.

[0059] Network assistance data can be detected to be present within SIB7 based on detecting a value of CarrierFreqsGERAN that does not correspond to any GSM band. For example, as mentioned above, the value of CarrierFreqsGERAN can be at least one of: 125-127, 252-258, 294-305, 341-511, or 886-939.

[0060] The method can also include, at 160, upon detecting the value of the CarrierFreqsGERAN, extracting the network assistance data from at least one of the following: cellReselectionPriority, ncc-Permitted, q-RxLevMin, p-MaxGERAN, threshX-High ReselectionThreshold, or threshX-Low ReselectionThreshold. The data in these values can be referred to as the payload. This payload can be included by the access node at 125.

[0061] The at least one cellular network insight can include at least one of: uplink congestion, downlink congestion, or a randomization interval over which a user equipment should wait before performing access.

[0062] The randomization interval may further avoid surges and congestion on the uplink resulting from lots of UEs simultaneously attempting to connect after detecting that the cell is uncongested.

[0063] If the UE subsequently performs access, after being informed through this mechanism that there is a lack of congestion, then this access may not be a page response, and consequently may not use the special reserved IMSI value which was paged.

[0064] FIG. 2 illustrates a system according to certain embodiments of the invention. It should be understood that each block of the flowchart of FIG. 1 may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and/or circuitry. In one embodiment, a system may include several devices, such as, for example, network element 210 and user equipment (UE) or user device 220. The system may include more than one UE 220 and more than one network element 210, although only one of each is shown for the purposes of illustration. A network element can be an access point, a base station, an eNode B (eNB), or any other network element, such as any access node. Each of these devices may include at least one processor or control unit or module, respectively indicated as 214 and 224. At least one memory may be provided in each device, and indicated as 215 and 225, respectively. The memory may include computer program instructions or computer code contained therein, for example for carrying out the embodiments described above. One or more transceiver 216 and 226 may be provided, and each device may also include an antenna, respectively illustrated as 217 and 227. Although only one antenna each is shown, many antennas and multiple antenna elements may be provided to each of the devices. Other configurations of these devices, for example, may be provided. For example, network element 210 and UE 220 may be additionally configured for wired communication, in addition to wireless communication, and in such a case antennas 217 and 227 may illustrate any form of communication hardware, without being limited to merely an antenna.

[0065] Transceivers 216 and 226 may each, independently, be a transmitter, a receiver, or both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception. The transmitter and/or receiver (as far as radio parts are concerned) may also be implemented as a remote radio head which is not located in the device itself, but in a mast, for example. It should also be appreciated that according to the "liquid" or flexible radio concept, the operations and functionalities may be performed in different entities, such as nodes, hosts or servers, in a flexible manner. In other words, division of labor may vary case by case. One possible use is to make a network element to deliver local content. One or more functionalities may also be implemented as a virtual application that is provided as software that can run on a server.

[0066] A user device or user equipment 220 may be a mobile station (MS) such as a mobile phone or smart phone or multimedia device, a computer, such as a tablet, provided with wireless communication capabilities, personal data or digital assistant (PDA) provided with wireless communication capabilities, portable media player, digital camera, pocket video camera, navigation unit provided with wireless communication capabilities or any combinations thereof. The user device or user equipment 220 may be a sensor or smart meter, or other device that may usually be configured for a single location.

[0067] In an exemplifying embodiment, an apparatus, such as a node or user device, may include means for carrying out embodiments described above in relation to FIG. 1.

[0068] Processors 214 and 224 may be embodied by any computational or data processing device, such as a central processing unit (CPU), digital signal processor (DSP), application specific integrated circuit (ASIC), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), digitally enhanced circuits, or comparable device or a combination thereof. The processors may be implemented as a single controller, or a plurality of controllers or processors. Additionally, the processors may be implemented as a pool of processors in a local configuration, in a cloud configuration, or in a combination thereof.

[0069] For firmware or software, the implementation may include modules or unit of at least one chip set (e.g., procedures, functions, and so on). Memories 215 and 225 may independently be any suitable storage device, such as a non-transitory computer-readable medium. A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. The memories may be combined on a single integrated circuit as the processor, or may be separate therefrom. Furthermore, the computer program instructions may be stored in the memory and which may be processed by the processors can be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language. The memory or data storage entity is typically internal but may also be external or a combination thereof, such as in the case when additional memory capacity is obtained from a service provider. The memory may be fixed or removable.

[0070] The memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus such as network element 210 and/or UE 220, to perform any of the processes described above (see, for example, FIG. 1). Therefore, in certain embodiments, a non-transitory computer-readable medium may be encoded with computer instructions or one or more computer program (such as added or updated software routine, applet or macro) that, when executed in hardware, may perform a process such as one of the processes described herein. Computer programs may be coded by a programming language, which may be a high-level programming language, such as objective-C, C, C++, C#, Java, etc., or a low-level programming language, such as a machine language, or assembler. Alternatively, certain embodiments of the invention may be performed entirely in hardware.

[0071] Furthermore, although FIG. 2 illustrates a system including a network element 210 and a UE 220, embodiments of the invention may be applicable to other configurations, and configurations involving additional elements, as illustrated and discussed herein. For example, multiple user equipment devices and multiple network elements may be present, or other nodes providing similar functionality, such as nodes that combine the functionality of a user equipment and an access point, such as a relay node.

[0072] One having ordinary skill in the art will readily understand that the invention as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the invention has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the invention. In order to determine the metes and bounds of the invention, therefore, reference should be made to the appended claims.

Claims

1. A method, comprising: detecting, by a device, at least one advertised value, wherein the at least one advertised value is received by the device over a cellular system information message comprising information indicative of radio frequency bands relevant for cell re-selection; wherein one or more of the indicated radio frequency bands is indicative of the presence of the at least one advertised value; and extracting, from the at least one advertised value, at least one cellular network insight.

2. The method of claim 1, wherein network assistance data is detected in an evolved radio access network to be present within system information block type seven (SIB7) based on detecting a value of CarrierFreqsGERAN that does not correspond to any global system for mobile communication band.

3. The method of claim 2, wherein the value of CarrierFreqsGERAN comprises at least one of: 125-127, 252-258, 294-305, 341-511, or 886-939.

4. The method of claim 2, further comprising: upon detecting the value of the CarrierFreqsGERAN, extracting the network assistance data from at least one of the following: cellReselectionPriority CellReselectionPriority, ncc-Permitted, q-RxLevMin, p-MaxGERAN, threshX-High ReselectionThreshold, or threshX-Low ReselectionThreshold

5. The method of claim 1, wherein the at least one cellular network insight comprises at least one of: uplink congestion, downlink congestion, or a randomization interval over which a user equipment should wait before performing access.

6. A method, comprising: selecting, by a device, at least one advertised value, wherein the at least one advertised value is to be transmitted by the device over a cellular system information message comprising information indicative of radio frequency bands relevant for cell re-selection; wherein one or more of the indicated radio frequency bands is indicative of the presence of the at least one advertised value; and transmitting, in association with the at least one advertised value, at least one cellular network insight.

7. The method of claim 6, wherein network assistance data is indicated in an evolved radio access network as being present within system information block type seven (SIB7) based on indicating a value of CarrierFreqsGERAN that does not correspond to any global system for mobile communication band.

8. The method of claim 7, wherein the value of CarrierFreqsGERAN comprises at least one of: 125-127, 252-258, 294-305, 341-511, or 886-939.

9. The method of claim 7, further comprising: including the network assistance data in at least one of the following: cellReselectionPriority CellReselectionPriority, ncc-Permitted, q-RxLevMin, p-MaxGERAN, threshX-High ReselectionThreshold, or threshX-Low ReselectionThreshold

10. The method of claim 6, wherein the at least one cellular network insight comprises at least one of: uplink congestion, downlink congestion, or a randomization interval over which a user equipment should wait before performing access.

11. An apparatus, comprising: at least one processor; and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to detect, by a device, at least one advertised value, wherein the at least one advertised value is received by the device over a cellular system information message comprising information indicative of radio frequency bands relevant for cell re-selection; wherein one or more of the indicated radio frequency bands is indicative of the presence of the at least one advertised value; and extract, from the at least one advertised value, at least one cellular network insight.

12. The apparatus of claim 11, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to detect in an evolved radio access network network assistance data as being present within system information block type seven (SIB7) based on detecting a value of CarrierFreqsGERAN that does not correspond to any global system for mobile communication band.

13. The apparatus of claim 12, wherein the value of CarrierFreqsGERAN comprises at least one of: 125-127, 252-258, 294-305, 341-511, or 886-939.

14. The apparatus of claim 12, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to, upon detecting the value of the CarrierFreqsGERAN, extract the network assistance data from at least one of the following: cellReselectionPriority CellReselectionPriority, ncc-Permitted, q-RxLevMin, p-MaxGERAN, threshX-High ReselectionThreshold, or threshX-Low ReselectionThreshold

15. The apparatus of claim 11, wherein the at least one cellular network insight comprises at least one of: uplink congestion, downlink congestion, or a randomization interval over which a user equipment should wait before performing access.

16. An apparatus, comprising: at least one processor; and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to select, by a device, at least one advertised value, wherein the at least one advertised value is to be transmitted by the device over a cellular system information message comprising information indicative of radio frequency bands relevant for cell re-selection; wherein one or more of the indicated radio frequency bands is indicative of the presence of the at least one advertised value; and transmit, in association with the at least one advertised value, at least one cellular network insight.

17. The apparatus of claim 16, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to indicate in an evolved radio access network network assistance data as being present within system information block type seven (SIB7) based on indicating a value of CarrierFreqsGERAN that does not correspond to any global system for mobile communication band.

18. The apparatus of claim 17, wherein the value of CarrierFreqsGERAN comprises at least one of: 125-127, 252-258, 294-305, 341-511, or 886-939.

19. The apparatus of claim 17, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to include the network assistance data in at least one of the following: cellReselectionPriority CellReselectionPriority, ncc-Permitted, q-RxLevMin, p-MaxGERAN, threshX-High ReselectionThreshold, or threshX-Low ReselectionThreshold

20. The apparatus of claim 16, wherein the at least one cellular network insight comprises at least one of: uplink congestion, downlink congestion, or a randomization interval over which a user equipment should wait before performing access.

Images