For the FE-ICIC and/or CRS-IC features, what does the channel estimation algorithm look like? Is the interference cancellation only on the interfering cell(s) only or are there multiple iterations that include both the serving and interfering cells? How many iterations/what is the stopping criteria? How is it different between colliding CRS and non-colliding CRS?
For the NAICS or other non IRC based techniques that suppress intercell interference, what is the receiver that is used? Is it iterative interference cancellation or a reduced complexity maximum likelihood (R-ML) detector? If iterative interference cancellation, is the decoder within the iteration? Are there any techniques in the iterations which are suboptimal but are meant to reduce complexity? If R-ML, which particular R-ML technique is used? Please provide details if you can about the specifics of the reduced complexity technique.
Same question as above but for the SU-MIMO and MU-MIMO receiver.
Thank you!!!
Related
hi guys.....the ultimate accessory for me would be a laser gun detector, which plugged into the sdio slot.....is such a thing possible?
What part would the pda play in the detection? Would it just use the screen and speaker for the warnings?
Here in the UK all speed camera detectors, blockers, scanners etc are being outlawed under a new bill. I think they already banned in Ireland. I just read this article.
The Department for Transport said it would seek to ban the dashboard devices as soon as possible because of fears motorists were using them to break speed limits without being caught. Thousands of drivers have installed the technology after a huge rise in the use of cameras and other speed enforcement equipment by police.
The detection devices are already outlawed in many European countries including France and Ireland.
A Department for Transport spokeswoman said: "We are aware of the problem and as soon as a legislative opportunity becomes available we will seek to make these devices illegal."
Road safety groups welcomed the announcement. Rob Gifford of the Parliamentary Advisory Council for Transport Safety told The Times: "This is a long overdue closing of a legal loophole. Speed camera detectors should not be needed by law-abiding drivers."
On the issue of websites showing where speed cameras were located, transport minister David Jamieson yesterday said he was happy for people to know where the cameras were. However, he did not want information to be passed on revealing whether or not they were switched on.
He told the House of Commons Transport Committee: "If there is a map showing where they are, then I think that's a good idea, because people will then be very careful in that area."
I'm pretty sure speed cameras use RADAR, not LASER. A useful LASER detector simply does not exist at all, because of the rules of physics that apply to light.
The Origin b2 has many unique and patent protected features. The following is a list of key features.
Alerts for ALL types of fixed traps - Gatso, Truvelo, SPECS, DS2
Alerts for accident blackspots/Congestion Charging Cameras (time sensitive) & schools (time sensitive) (alerts may be switched off by user)
Alerts for user defined, personal locations
Standard laser detector
Optional radar detector
Unit ready for optional laser diffuser
Personal overspeed warnings
Driver Information System - displays distance covered, journey time and average speed
And GPS Based Detectors are not covered (unless they have an additional laser or radar module) as they have no 'active' detection, they simply report GPS Co-Ords of known locations.
Laser detectors are a complete waste of time. the police laser speed guns obtain your speed in 0.3 seconds. You cannot react qickly enough to beat this. The only way to defeat the laser guns is to jam there signal until you have slowed down enough.
The Pilgrim
Oh yes, jammers are also being outlawed.
cruisin-thru said:
Oh yes, jammers are also being outlawed.
Click to expand...
Click to collapse
No they're not - because they ALREADY are illegal.
Use of POI's in navigation software for speed/redlight camera's is already quit common in the Netherlands. Even mobile units are reported 'live' and coordinates given through TMC(radio), gprs. None of this is illegal.
Use of POI's in navigation software for speed/redlight camera's is already quit common in the Netherlands. Even mobile units are reported 'live' and coordinates given through TMC(radio), gprs. None of this is illegal.
I've the forum rules: this query does not neatly fit anywhere, so I'll apologise in advance, but it does affect millions of people in real life in a very real and practical way.
There is a function in Android called com.android.internal.telephony.Connection.DisconnectCause.
It's function is to tell who tore down the voice call connnection, and specifically if it was due to the carrier having network congestion caused by their rent seeking under spending of CAPEX and general ****ty service. This indirectly implements (via the radio interface layer) Qualcomm diagnostics and ITU standards.
As it turns out, some (if not most) manufacturers have deliberately commented it out so it does not work, almost certainly at the request of the carriers.
So I am seeking a low level engineer up for some deep hacking to come up with a solution, perhaps one of the following:-
1. Ultra low level boot program that creates a micro-RIL with a single function of talking to the Qualcomm chipset before the main OS ROm starts to run for call diagnostics
2. A variation on above, namely a patch
3. A man-in-the-middle RIL daemon inserter to interrogate
4. Hack VALIK
5. Somethng else I have not thought of (I do not know Android except it has a Linux kernel and is a collective noun for a random collection of ROMs fiddled with by manufacturers who fill them with advertising **** and crippleware)
I will pay a $5k reward to who ever can help devise a manufacturer independent means of achieving this that is not too brittle and can somehow get that data to an ordinary app. The Qualcomm manuals and calls and even sample code is available to serious developers. Please privately message me if you are interested. This is not an "all or nothing" offer: I will pay more than one person for more than one pathway.
This is a real offer with real bucks and an ongoing retainer payment.
So there it is, money, a chance to make carriers crap service measurable and accountable and fame. There is a funny clip on you tube on this exact point ("they **** you with cell phones") with Joe Pesci at:
PM me, I have extensive experience with Qualcomm chipset interfacing, AT commands, RIL Hacking, OTA Layer 3 protocol decoding & etc.
Greetings Everyone,
I'm am a mobile app noob. I'm currently doing some research on data/communication protocols between a mobile app and software. Could someone please point me in the right direction on finding out what current data protocols are currently available that let a mobile application 'talk' with a piece of software through an internet server?
Thank you
Replication of research findings across independent longitudinal studies is essential for a cumulative and innovative developmental science. Meta-analysis of longitudinal studies is often limited by the amount of published information on particular research questions, the complexity of longitudinal designs and sophistication of analyses, and practical limits on full reporting of results. In many cases, cross-study differences in sample composition and measurements impede or lessen the utility of pooled data analysis. A collaborative, coordinated analysis approach can provide a broad foundation for cumulating scientific knowledge by facilitating efficient analysis of multiple studies in ways that maximize comparability of results and permit evaluation of study differences. The goal of such an approach is to maximize opportunities for replication and extension of findings across longitudinal studies through open access to analysis scripts and output for published results, permitting modification, evaluation, and extension of alternative statistical models, and application to additional data sets.
I wanted to start this thread to discuss Doze and its impact on reliability, primarily on safety applications.
I'd like to start with a general statement: the days of our devices being merely telephones are long behind us. We still call them cell phones, but as we - especially here - know, our devices are so much more. They truly are wearable computers. They're our music, our cameras, our navigators, our communicators, our personal databases.. and for some of us, safety equipment. And they must be reliable.
Now, battery life is important. No question about that. But.. and I'm trying to put this delicately.. Doze was forced upon us with no option to globally disable, and even "whitelisting" applications doesn't fully release them from the confines of the new battery management policy. For some of us, Doze has made our devices less reliable.
The application category I'd like to call attention to first is marine anchor alarms. For those who don't boat, anchor alarms monitor a vessel's position with the GPS. If the anchor drags a certain distance (and the boat moves more than it should), an alarm is issued to alert the crew to the danger. It is entirely possible to drift (particularly when anchored in current) without triggering the significant motion sensors, limiting even whitelisted apps to 15-minute GPS polls. A lot can happen in 15 minutes.
Obviously using a portable device as your sole means of anchor drag detection is not a wise idea. Yet, many people with smaller boats do it, because that's all they have. Some of us with larger vessels do it as well, with a secondary system as a backup (since anchor alert applications make it much easier to define the anchor scope and exclusion zones precisely). This is all very much beside the point.
This category of application can no longer function reliably on Android! As of Android 6.0, anchor alerts can no longer monitor the GPS position reliably 24 hours per day unless:
1. The device is plugged in (and the power supply hasn't failed), or,
2. The application uses media input/output (a battery-wasting hack).
Unlikely as it may be, it is possible that someone will lose their small vessel this summer because their device failed to notify them that they'd slipped off the anchor, even if they knew enough to whitelist the app!
This is a pretty serious regression, and there are others. AIS (Automatic Identification System) and radar warning apps that communicate directly with ship systems via IP are no longer reliable. Tasker can no longer respond to local events with a granularity better than 15 minutes. Sleep monitoring applications are broken as well. And this is after you've manually whitelisted these applications!
I don't want this thread to sound like a rant. Doze is a fantastic addition to Android. But I would like to get the conversation started so that more people recognize that it imposes a fairly significant cost for some people.. especially those of us with extended batteries who feel virtually no benefit.
I was hoping people could respond with:
1. Other categories of applications, or individual applications that are no longer reliable on Android 6+ (particularly those related to safety),
2. A "me too" if you want the ability in custom or official roms to a) completely/situationally disable Doze without root, or b) properly whitelist applications, and,
3. Whether or not you've personally experienced critical notification delays, missed alarms, or other negative effects you attribute to Doze.
If anyone does need to disable Doze in the meantime, there is a straightforward (not well documented) way to do it if you are rooted:
Code:
dumpsys deviceidle disable
The change is non-persistent.
HUAWEI Analytics Kit is a one-stop data analysis platform for mobile app developers that utilizes data to drive daily app operations, bringing out dynamic details in a comprehensive, timely, and efficient manner. These cutting-edge solutions inspire out-of-the-box app service innovations, helping developers and operations personnel grow revenue and expand the reach of their apps.
In order to provide a comprehensive overview of how and when Analytics Kit can be applied, this article addresses a diverse range of related topics. We hope that it sheds light on the most important aspects of this exciting new app service paradigm.
In our current era of "post-mobile" Internet, characterized by slow traffic growth, and difficulty in monetizing products and services, access to both capital and users has become crucial, due to the finite nature of each. Developers have struggled to create unconventional apps that attract new users, and provide a steadily growing income. The best, and perhaps only, tool at their disposal is refined operations, which is, detailed analysis of user behavior for the purpose of gaining insight into user requirements and pain points. These assumptions are systematically verified, and then translated into marketing strategies, allowing the developers behind an app to perceive it through the eyes of its users, and grow its user base beyond previous expectations.
But how exactly can enterprises and operations personnel gain such precise insight? And how can they truly stand in users' shoes? This is where the notions of "Event" and "Event analysis" come into the picture.
What is an Event?
An event refers to the behavior of a user with regard to a product, or in other words, a specific event is something that a user completes at a specific time point, place, and manner.
Take the process of browsing for a typical item on an e-commerce platform, as an example. Corresponding events can include tapping the registration button, accessing the product details app, and exiting the page. Therefore, event monitoring is, in essence, the detailed study of user behavior within an app.
What is Event Analysis?
Event analysis attempts to determine the motivations and principles behind user events. It uses multiple dimensions to better capture the various attributes of individual users, for the purpose of user activation promotion, retention, and recall policies that are targeted precisely to match the users themselves.
Within a mobile app team, certain roles are dedicated for specific event indicators. For example, operations personnel may focus on the source of new users in recent months, product managers may care most about the geographical distribution of active users and daily purchasing trends, while R&D engineers may want to know the crash times of a new version. Event analysis provides the high-level information to satisfy each team member.
How Do I Use Event Analysis?
HUAWEI Analytics Kit implements automatic collection on various events and event presetting. If you are unable to collect system-level events for your app (such as uninstallations, resets, and crashes), Analytics Kit does so for you automatically, without need for manual tracking, analyzing user churn and app exception scenarios.
It also empowers you to customize events for in-depth and personalized analysis. For custom events, it is recommended that you set appropriate event parameters, in order to fully reveal important details, such as user trends and multi-dimensional comparisons. After setting the parameters, you can view the parameter details in the event analysis report.
By selecting an event, you'll be able to view detailed analysis corresponding to it, including real-time and historical trends, as well as custom parameters and default indicators (app version, model proportion, OS version, and number of events per session).
Event analysis also supports segmentation according to different conditions, which helps immensely with multi-dimensional drill-down analysis. By adding user attributes, audience, and login status as filter criteria, you can query event data that meets specific conditions with a high degree of precision.
Applicable scenarios for event analysis:
1: The operations personnel for a mobile game would like to know the purchasing information related to game props over the past month, such as the number of payments, number of users making payments, and the payment amount.
Define an event and the event parameters.
You can filter out and view the average number of daily events, average number of daily users, average number of payment times per user, and payment amount, according to time-based segments.
2: The operations personnel for a fresh product purchase app find that the traffic for a channel has soared recently, and they suspect that the spike in traffic is fake. How can they analyze the traffic to confirm that it's real?
Then select the event analysis details for the channel ad link, filtering out for user attributes, audience, and login status, and perform drill-down analysis based on the location, operating system, and app version to reveal the presence of fake traffic.
View the channel parameter analysis card.
Data-driven growth starts with the event model. The event-parameter model helps you gain crucial insight into the authentic interactions between users and apps. By accounting for all event-related factors, you can determine the root causes of user behavioral events, quickly locate strategic points, and enhance operations efficiency to unforeseen levels.
The event model also forms the basis for the funnel, retention, and behavior path analysis models, which will be covered in greater detail.