A reported 130 operators around the world have written LTE into their technology roadmaps. In December 2009, TeliaSonera launched the world’s first LTE networks in Norway and Sweden and an estimated 17 operators are expected to follow in its footsteps in 2010.
Cập nhật tình hình thị trường bất động sản, địa ốc hiện nay tại Việt Nam. Tìm hiểu về bất động sản, thị trường nhà đất, bất động sản Việt Nam.Cnlax.com
Sunday, February 28, 2010
GSM-UMTS Network migration towards LTE
A reported 130 operators around the world have written LTE into their technology roadmaps. In December 2009, TeliaSonera launched the world’s first LTE networks in Norway and Sweden and an estimated 17 operators are expected to follow in its footsteps in 2010.
BBC and Ubiquisys stream multiple videos over a femtocell at MWC 2010
Thursday, February 25, 2010
Femtocells for LTE
Meanwhile, the femto players are looking ahead to LTE, where there are many indications from operators that tiny cells will play a big part in the strategy. The devices will be used from day one by some carriers - to offload data from the macrocell or to provide indoor coverage in high frequencies like 2.6GHz. They could also add capacity to deployments in low frequencies like 700MHz and even be used as a starting point for greenfield providers, which could then add macro networks later, explained Simon Saunders, chair of the Femto Forum.
Continuous Computing has been eyeing the femto market for several years from its heartlands in protocol stacks, core networking and traffic shaping. At MWC, it worked with picoChip and Cavium Networks to show the first complete LTE femtocell reference design. Available immediately, this includes the LTE modem, RF and packet processors, protocol software, intelligent router functionality and a complete Evolved Packet Core (EPC) simulator.
"The demand for LTE femtocells is unquestionable. We are already seeing operators asking for small cell access points to start testing in the second half of this year. Femtocells represent the key to avoiding the difficulties surrounding the first 3G deployments where roll-outs cost too much, took too long and did not meet user expectations," said Mike Dagenais, CEO of Continuous.
Tuesday, February 23, 2010
Monday, February 22, 2010
Codec's for LTE
CODEC stands for “COder-DECoder,” but is also known as an enCOder-DECoder and COmpression-DECompression system when used in video systems. Codec's are important as they compress the voice/video data/packets so less bandwidth is required for the data to be transmitted. At the same time it has to be borne in mind that the capacity to withstand errors decrease with higher compression ratio and as a result it may be necessary to change the codecs during the voice/video call. This calls for flexibility as in case of AMR (Adaptive Multi Rate) Codecs.
The following is from Martin Sauter's book "Beyond 3G – Bringing Networks, Terminals and the Web Together":
Voice codecs on higher layers have been designed to cope with packet loss to a certain extent since there is not usually time to wait for a repetition of the data. This is why data from circuit-switched connections is not repeated when it is not received correctly but simply ignored. For IP sessions, doing the same is difficult, since a single session usually carries both real-time services such as voice calls and best-effort services such as Web browsing simultaneously. In UMTS evolution networks, mechanisms such as ‘Secondary PDP contexts’ can be used to separate the real-time data traffic from background or signaling traffic into different streams on the air interface while keeping a single IP address on the mobile device.
UMTS uses the same codecs as GSM. On the air interface users are separated by spreading codes and the resulting data rate is 30–60 kbit/s depending on the spreading factor. Unlike GSM, where timeslots are used for voice calls, voice capacity in UMTS depends less on the raw data rate but more on the amount of transmit power required for each voice call. Users close to the base station require less transmission power in downlink compared with more distant users. To calculate the number of voice calls per UMTS base station, an assumption has to be made about the distribution of users in the area covered by a cell and their reception conditions. In practice, a UMTS base station can carry 60–80 voice calls per sector. A typical three-sector UMTS base station can thus carry around 240 voice calls. As in the GSM example, a UMTS cell also carries data traffic, which reduces the number of simultaneous voice calls.
The following is an extract from 3G Americas white paper, "3GPP Mobile Broadband Innovation Path to 4G: Release 9, Release 10 and Beyond: HSPA+, SAE/LTE and LTE-Advanced,":
Real-time flows (voice/video) based on rate adaptive codecs can dynamically switch between different codec rates. Codec rate adaptation allows an operator to trade off voice/video quality on one side and network capacity (e.g. in terms of the number of accepted VoIP calls), and/or radio coverage on the other side. Operators have requested a standardized solution to control the codec rate adaptation for VoIP over LTE, and a solution has been agreed upon and specified in the 3GPP Rel-9 specifications, which is provided in this paper.
CODEC RATE ADAPTATION BASED ON ECN
Given previous discussion in 3GPP (3GPP S4-070314) it was clear that dropping IP packets was not an acceptable means for the network to trigger a codec rate reduction. Instead an explicit feedback mechanism had to be agreed on by which the network (e.g. the eNodeB) could trigger a codec rate reduction. The mechanism agreed on for 3GPP Rel-9 is the IP-based Explicit Congestion Notification (ECN) specified in an IETF RFC. ECN is a 2 bit field in the end-to-end IP header. It is used as a “congestion pre-warning scheme” by which the network can warn the end points of incipient congestion so that the sending endpoint can decrease its sending rate before the network is forced to drop packets or excessive delay of media occurs. Any ECN-based scheme requires two parts: network behavior and endpoint behavior. The first part had already been fully specified in an IETF RFC106 and merely had to be adopted into the corresponding specifications (3GPP TS 23.401 and 3GPP TS 36.300). The network behavior is completely service and codec agnostic. That is, it works for both IMS and non-IMS based services and for any voice/video codec with rate-adaptation capabilities. The main work in 3GPP focused on the second part: the endpoint behavior. For 3GPP Rel-9, the endpoint behavior has been specified for the Multimedia Telephony Service for IMS (MTSI - 3GPP TS 26.114). It is based on a generic (i.e. non-service specific) behavior for RTP/UDP based endpoints, which is being standardized in the IETF.
Furthermore, it was agreed that no explicit feedback was needed from the network to trigger a codec rate increase. Instead, the Rel-9 solution is based on probing from the endpoints – more precisely the Initial Codec Mode (ICM) scheme that had already been specified in 3GPP Rel-7 (3GPP S4-070314). After the SIP session has been established, the sending side always starts out with a low codec rate. After an initial measurement period and RTCP receiver reports indicating a “good channel,” the sending side will attempt to increase the codec rate. The same procedure is executed after a codec rate reduction.
Figure 6.8 depicts how codec rate reduction works in Rel-9:
- Step 0. The SIP session is negotiated with the full set of codec rates and independent of network level congestion. The use of ECN has to be negotiated separately for each media stream (e.g. VoIP).
- Steps 1 and 2. After ECN has been successfully negotiated for a media stream the sender must mark each IP packet as ECN-Capable Transport (ECT). Two different values, 10 and 01, have been defined in an IETF RFC106 to indicate ECT. However, for MTSI only 10 shall be used.
- Step 3. To free up capacity and allow more VoIP calls and/or to improve VoIP coverage, the eNodeB sets the ECN field to Congestion Experienced (CE) in an IP packet that belongs to an IP flow marked as ECT. Note that the ECN-CE codepoint in an IP packet indicates congestion in the direction in which the IP packets are being sent.
- Steps 4 and 5. In response to an ECN-CE the receiving MTSI client issues an RTCP message to trigger a codec rate reduction.
ONGOING WORK IN 3GPP
A new work item called, Enabling Encoder Selection and Rate Adaptation for UTRAN and E-UTRAN, has been created for 3GPP Rel-10. Part of this work item is to extend the scope of the codec rate adaptation solution agreed in Rel-9 to also apply to HSPA and non-voice RTP-based media streams.
Further Reading:
- 3GPP S4-070314, Rate-Adaptive Real-time Media, Reply Liaison from SA4 to RAN2, 2007 (http://www.3gpp.org/ftp/TSG_SA/WG4_CODEC/TSGS4_43/Docs/S4-070314.zip)
- IETF RFC 3168 (09/2001), The Addition of Explicit Congestion Notification (ECN) to IP. (http://tools.ietf.org/html/rfc3168)
- 3GPP TS 23.401: General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (http://www.3gpp.org/ftp/Specs/archive/23_series/23.401/)
- 3GPP TS 36.300: Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (http://www.3gpp.org/ftp/Specs/archive/36_series/36.300/)
- 3GPP TS 26.114: IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction (http://www.3gpp.org/ftp/Specs/archive/26_series/26.114/)
- Westerlund, M., et al., Explicit Congestion Notification (ECN) for RTP over UDP, draft-westerlund-avt-ecn-for-rtp-02, work in progress (ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-westerlund-avt-ecn-for-rtp-02.txt)
- 3GPP TR 23.860: Enabling Coder Selection and Rate Adaptation for UTRAN and E-UTRAN for Load Adaptive Applications; Stage 2 (http://www.3gpp.org/ftp/Specs/archive/23_series/23.860/)
- 3GPP TS 26.071: Mandatory speech CODEC speech processing functions; AMR speech CODEC; General description(http://www.3gpp.org/ftp/Specs/archive/26_series/26.071/)
- 3GPP TS 26.171: Speech codec speech processing functions; Adaptive Multi-Rate - Wideband (AMR-WB) speech codec; General description (http://www.3gpp.org/ftp/Specs/archive/26_series/26.171/)
Sunday, February 21, 2010
Femtocells update from Mobile World Congress 2010
Among a host of announcements, the leading silicon supplier for this segment, picoChip, was working hard to maintain its headstart as Qualcomm and others gear up to enter the market. It announced no fewer than six new customers, many coming from the Taiwanese ecosystem that is so vital to the mass adoption and price competitiveness of any emerging consumer product.
The new customers are Alpha Networks, Argela, Askey, C&S Micro, Contela and Zyxel, all of which will use the UK firm's PC302 picoXcell system-on-chip for HSPA(+). This is designed to reduce cost and time to market for vendors, and now has over 20 adopters, including Vodafone's femto supplier Alcatel-Lucent, and AT&T's, Cisco/ip.access.
Meanwhile, the femto players are looking ahead to LTE, where there are many indications from operators that tiny cells will play a big part in the strategy. The devices will be used from day one by some carriers - to offload data from the macrocell or to provide indoor coverage in high frequencies like 2.6GHz. They could also add capacity to deployments in low frequencies like 700MHz and even be used as a starting point for greenfield providers, which could then add macro networks later, explained Simon Saunders, chair of the Femto Forum.
Continuous Computing has been eyeing the femto market for several years from its heartlands in protocol stacks, core networking and traffic shaping. At MWC, it worked with picoChip and Cavium Networks to show the first complete LTE femtocell reference design. Available immediately, this includes the LTE modem, RF and packet processors, protocol software, intelligent router functionality and a complete Evolved Packet Core (EPC) simulator.
"The demand for LTE femtocells is unquestionable. We are already seeing operators asking for small cell access points to start testing in the second half of this year. Femtocells represent the key to avoiding the difficulties surrounding the first 3G deployments where roll-outs cost too much, took too long and did not meet user expectations," said Mike Dagenais, CEO of Continuous.
The reference design used a picoChip modem, mezzanine RF card and PHY software; Cavium's Octeon Plus multicore processor; and Continuous' Trillium LTE Layer 2/3 protocols, eNodeB reference application and EPC emulator.
Saturday, February 20, 2010
Wednesday, February 17, 2010
LTE Conformance Testing Logs
Monday, February 15, 2010
Self Organizing Networks and Enhancements
- Coverage and Capacity Optimization. Coverage and Capacity Optimization techniques are currently under study in 3GPP and will provide continuous coverage and optimal capacity of the network. The performance of the network can be obtained via key measurement data and adjustments can then be made to improve the network performance. For instance, call drop rates will give an initial indication of the areas within the network that have insufficient coverage and traffic counters can be used to identify capacity problems. Based on these measurements, the network can optimize the performance by trading off capacity and coverage.
- Mobility Robustness Optimization. Mobility Robustness Optimization aims at reducing the number of hand over related radio link failures by optimally setting the hand over parameters. A secondary objective is to avoid the ping-pong effect or prolonged connection to a non-optimal cell.
- Mobility Load Balancing. Related to Mobility Robustness is Mobility Load Balancing, which aims to optimize the cell reselection and handover parameters to deal with unequal traffic loads. The goal of the study is to achieve this while minimizing the number of handovers and redirections needed to achieve the load balancing.
- RACH Optimization. To improve the access to the system, RACH Optimization has been proposed to optimize the system parameters based upon monitoring the network conditions, such as RACH load and the uplink interference. The goal is to minimize the access delays for all the UEs in the system and the RACH load.
Sunday, February 14, 2010
New Technologies for Mobile Phone Theft prevention
Design Out Crime: Mobile Phone solutions from Design Council on Vimeo.
Three prototype solutions for preventing mobile phone theft have been unveiled.
The i-migo, the 'tie' solution and TouchSafe have been developed to counter crimes such as mobile phone identity fraud, which rose by over 70 per cent in 2009.
TouchSafe uses Near Field Communications (NFC) technology similar to that used by the Oyster Card and requires the handset's owner to carry a small card with them that they touch on the phone every time they make a purchase.
The 'tie' solution makes an association between a handset and theSIM chip so that other SIMs cannot be used on the handset should the mobile phone be stolen.
And the i-migo is a small device carried by the mobile phone's owner that sounds an alert and locks the handset should it be taken outside of a set range. Additionally, it automates the back-up of any data stored on the device.
The prototypes were inspired by a Home Office initiative to develop new ways of preventing mobile phone theft and will be shown off atMobile World Congress in Barcelona next week.
Home Office Minister Alan Campbell said: "As new technology creates new opportunities for the user it can also provide criminals with opportunities as well.
"I believe the solutions developed by this challenge have the potential to be as successful as previous innovations like Chip and Pin, which reduced fraud on lost or stolen cards to an all-time low, and would encourage industry to continue working with us and take them up," Campbell continued.
LTE World Summit promising to be a grand event
Friday, February 12, 2010
A quick Introduction to M2M Communications
The following is from 3G Americas report on 3GPP standards and their evolution to 4G:
By leveraging connectivity, Machine-to-Machine (M2M) communication would enable machines to communicate directly with one another. In so doing, M2M communication has the potential to radically change the world around us and the way that we interact with machines.
In Rel-10, 3GPP is in the process of establishing requirements for 3GPP network system improvements that support Machine-Type Communications (MTC). The objective of this study is to identify 3GPP network enhancements required to support a large number of MTC devices in the network and to provide necessary network enablers for MTC communication service. Specifically, transport services for MTC as provided by the 3GPP system and the related optimizations are being considered as well as aspects needed to ensure that MTC devices and/or MTC servers and/or MTC applications do not cause network congestion or system overload. It is also important to enable network operators to offer MTC services at a low cost level, to match the expectations of mass market machine-type services and applications.
The 3GPP study on M2M communications has shown potential for M2M services beyond the current "premium M2M market segment." The example of applications for mass M2M services include machine type communications in smart power grid, smart metering, consumer products, health care, and so forth. The current mobile networks are optimally designed for Human-to-Human communications, but are less optimal for M2M applications.
A study item on M2M communications (3GPP TR 22.868) was completed in 2007; however, no subsequent normative specification has been published. For Rel-10 and beyond, 3GPP intends to take the results on network improvements from the study item forward into a specification phase and address the architectural impacts and security aspects to support MTC scenarios and applications. As such, 3GPP has defined a work item on Network Improvements for Machine-Type Communication (NIMTC). The following goals and objectives are described in the work item:
The goal of this work item is to:
A RAN study item to investigate the air interface enhancements for the benefit of M2M communication has also been recently approved. The study will be initiated in early 2010.
- 3GPP TR 22.868: Study on Facilitating Machine to Machine Communication in 3GPP Systems; (http://www.3gpp.org/ftp/Specs/archive/22_series/22.868/)
- 3GPP TR 33.812: Feasibility Study on the Security Aspects of Remote Provisioning and Change of Subscription for M2M Equipment; (http://www.3gpp.org/ftp/Specs/archive/33_series/33.812/)
- 3GPP's initial thoughts on Machine to Machine communication (http://docbox.etsi.org/workshop/2008/2008_06_M2MWORKSHOP/3GPPs_SWETINA_M2MWORKSHOP.pdf)
- M2M Activities in ETSI (http://www.pole-scs.org/index.php?m=6&l=en&x=file.download&h=0&fileid=57063)
- ETSI Workshop on M2M STANDARDIZATION 4th and 5th of June 2008: Agenda (http://docbox.etsi.org/Workshop/2008/2008_06_M2MWORKSHOP/00M2Magenda_FINALVERSION.pdf)
- ETSI Workshop on M2M STANDARDIZATION 4th and 5th of June 2008: Presentations (http://docbox.etsi.org//Workshop/2008/2008_06_M2MWORKSHOP/)
- M2M: the Internet of 50 billion devices, Jan 2010, Win-Win (http://www.huawei.com/publications/view.do?id=6083&cid=11392&pid=10664)
- 5 Myths about M2M (http://www.slideshare.net/blueslice/5-myths-about-m2m-presentation)
Thursday, February 11, 2010
M2M will become really big
Wednesday, February 10, 2010
UICC and USIM in 3GPP Release 8 and Release 9
In good old days of GSM, SIM was physical card with GSM "application" (GSM 11.11)
In the brave new world of 3G+, UICC is the physical card with basic logical functionality (based on 3GPP TS 31.101) and USIM is 3G application on a UICC (3GPP TS 31.102). The UICC can contain multiple applications like the SIM (for GSM), USIM and ISIM (for IMS). There is an interesting Telenor presentation on current and future of UICC which may be worth the read. See references below.
UICC was originally known as "UMTS IC card". The incorporation of the ETSI UMTS activities into the more global perspective of 3GPP required a change of this name. As a result this was changed to "Universal Integrated Circuit Card". Similarly USIM (UMTS Subscriber Identity Module) changed to Universal Subscriber Identity Module.
The following is from the 3G Americas Whitepaper on Mobile Broadband:
UICC (3GPP TS 31.101) remains the trusted operator anchor in the user domain for LTE/SAE, leading to evolved applications and security on the UICC. With the completion of Rel-8 features, the UICC now plays significant roles within the network.
Some of the Rel-8 achievements from standards (ETSI, 3GPP) are in the following areas:
USIM (TS 31.102)
With Rel-8, all USIM features have been updated to support LTE and new features to better support non-3GPP access systems, mobility management, and emergency situations have been adopted.
The USIM is mandatory for the authentication and secure access to EPC even for non-3GPP access systems. 3GPP has approved some important features in the USIM to enable efficient network selection mechanisms. With the addition of CDMA2000 and HRPD access technologies into the PLMN, the USIM PLMN lists now enable roaming selection among CDMA, UMTS, and LTE access systems.
Taking advantage of its high security, USIM now stores mobility management parameters for SAE/LTE. Critical information like location information or EPS security context is to be stored in USIM rather than the device.
USIM in LTE networks is not just a matter of digital security but also physical safety. The USIM now stores the ICE (In Case of Emergency) user information, which is now standardized. This feature allows first responders (police, firefighters, and emergency medical staff) to retrieve medical information such as blood type, allergies, and emergency contacts, even if the subscriber lies unconscious.
3GPP has also approved the storage of the eCall parameters in USIM. When activated, the eCall system establishes a voice connection with the emergency services and sends critical data including time, location, and vehicle identification, to speed up response times by emergency services. ECalls can be generated manually by vehicle occupants or automatically by in-vehicle sensors.
TOOLKIT FEATURES IMPROVEMENT (TS 31.111)
New toolkit features have been added in Rel-8 for the support of NFC, M2M, OMA-DS, DM and to enhance coverage information.
The contactless interface has now been completely integrated with the UICC to enable NFC use cases where UICC applications proactively trigger contactless interfaces.
Toolkit features have been updated for terminals with limited capabilities (e.g. datacard or M2M wireless modules). These features will be notably beneficial in the M2M market where terminals often lack a screen or a keyboard.
UICC applications will now be able to trigger OMA-DM and DS sessions to enable easier device support and data synchronization operations, as well as interact in DVB networks.
Toolkit features have been enriched to help operators in their network deployments, particularly with LTE. A toolkit event has been added to inform a UICC application of a network rejection, such as a registration attempt failure. This feature will provide important information to operators about network coverage. Additionally, a UICC proactive command now allows the reporting of the signal strength measurement from an LTE base station.
CONTACT MANAGER
Rel-8 defined a multimedia phone book (3GPP TS 31.220) for the USIM based on OMA-DS and its corresponding JavaCard API (3GPP TS 31.221).
REMOTE MANAGEMENT EVOLUTION (TS 31.115 AND TS 31.116)
With IP sessions becoming prominent, an additional capability to multiplex the remote application and file management over a single CAT_TP link in a BIP session has been completed. Remote sessions to update the UICC now benefit from additional flexibility and security with the latest addition of the AES algorithm rather than a simple DES algorithm.
CONFIDENTIAL APPLICATION MANAGEMENT IN UICC FOR THIRD PARTIES
The security model in the UICC has been improved to allow the hosting of confidential (e.g. third party) applications. This enhancement was necessary to support new business models arising in the marketplace, with third party MVNOs, M-Payment and Mobile TV applications. These new features notably enable UICC memory rental, remote secure management of this memory and its content by the third party vendor, and support new business models supported by the Trusted Service Manager concept.
SECURE CHANNEL BETWEEN THE UICC AND TERMINAL
A secure channel solution has been specified that enables a trusted and secure communication between the UICC and the terminal. The secure channel is also available between two applications residing respectively on the UICC and on the terminal. The secure channel is applicable to both ISO and USB interfaces.
RELEASE 9 ENHANCEMENTS: UICC: ENABLING M2M AND FEMTOCELLS
The role of femtocell USIM is increasing in provisioning information for Home eNodeB, the 3GPP name for femtocell. USIMs inside handsets provide a simple and automatic access to femtocells based on operator and user-controlled Closed Subscriber Group list.
Work is ongoing in 3GPP for the discovery of surrounding femtocells using toolkit commands. Contrarily to macro base stations deployed by network operators, a femtocell location is out of the control of the operator since a subscriber can purchase a Home eNodeB and plug it anywhere at any time. A solution based on USIM toolkit feature will allow the operator to identify the femtocells serving a given subscriber. Operators will be able to adapt their services based on the femtocells available.
The upcoming releases will develop and capitalize on the IP layer for UICC remote application management (RAM) over HTTP or HTTPS. The network can also send a push message to UICC to initiate a communication using TCP protocol.
Additional guidance is also expected from the future releases with regards to the M2M dedicated form factor for the UICC that is currently under discussion to accommodate environments with temperature or mechanical constraints surpassing those currently specified by the 3GPP standard.
Some work is also expected to complete the picture of a full IP UICC integrated in IP-enabled terminal with the migration of services over EEM/USB and the capability for the UICC to register on multicast based services (such as mobile TV).
Further Reading:
- Business perspective and Mobile service offer through Future SIM - Telenor (http://www.ux.uis.no/atc08/workshop/Larsen.pdf)
- The role of the UICC in Long Term Evolution all IP networks - Gemalto (http://www.gemalto.com/telecom/download/lte_gemalto_whitepaper.pdf)
- Technical White Paper: Smart Card in IMS - 3G Americas (http://www.3gamericas.org/documents/GEM_WP_IMS.pdf)
- 3GPP TS 31.101: UICC-terminal interface; Physical and logical characteristics (http://www.3gpp.org/ftp/Specs/archive/31_series/31.101/)
- 3GPP TS 31.102: Universal Subscriber Identity Module (USIM) application (http://www.3gpp.org/ftp/Specs/archive/31_series/31.102/)
- 3GPP TS 31.111: Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) (http://www.3gpp.org/ftp/Specs/archive/31_series/31.111/)
- 3GPP TS 31.115: Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications (http://www.3gpp.org/ftp/Specs/archive/31_series/31.115/)
- 3GPP TS 31.116: Remote APDU Structure for (U)SIM Toolkit applications (http://www.3gpp.org/ftp/Specs/archive/31_series/31.116/)
- 3GPP TS 31.220: Characteristics of the Contact Manager for 3GPP UICC applications (http://www.3gpp.org/ftp/Specs/archive/31_series/31.220/)
- 3GPP TS 31.221: Contact Manager Application Programming Interface (API); Contact Manager API for Java Card™ (http://www.3gpp.org/ftp/Specs/archive/31_series/31.221/)
Tuesday, February 9, 2010
Google real time speech translation mobile in couple of years
Live language translation on mobile phones could be just two years away, according to search giant Google. The company already offers text translation services and voice recognition, and Franz Och, head of translation services, says that work has already begun on combining the two.
The technology would work by translating phrases rather than individual words, and the company hopes that by looking at the huge amount of translated text already online, it can produce systems that are much more accurate than current versions. “If you look at the progress in machine translation and corresponding advances in voice recognition, there has been huge progress recently,” he said.
With over 6,000 languages spoken around the world, however, and only 52 currently on offer through Google’s existing translations services, the service is some way from meaning that language teaching in schools becomes redundant. “Clearly, for it to work smoothly, you need a combination of high-accuracy machine translation and high-accuracy voice recognition, and that's what we're working on,” said Mr Och.
So far, that is not yet possible, and language experts suggested that seamless technology is currently a distant prospect. David Crystal, honorary professor of linguistics at Bangor University, said the problems of dealing with speed of speech and range of accents could prove insurmountable.
'No system at the moment can handle that properly,' he added.
Monday, February 8, 2010
Coordinated Multi-Point (CoMP) transmission and reception
The following is from the 3G Americas report on CoMP:
Coordinated Multi-Point transmission/reception (CoMP) is considered by 3GPP as a tool to improve coverage, cell-edge throughput, and/or system efficiency.
The main idea of CoMP is as follows: when a UE is in the cell-edge region, it may be able to receive signals from multiple cell sites and the UE’s transmission may be received at multiple cell sites regardless of the system load. Given that, if the signaling transmitted from the multiple cell sites is coordinated, the DL performance can be increased significantly. This coordination can be simple as in the techniques that focus on interference avoidance or more complex as in the case where the same data is transmitted from multiple cell sites. For the UL, since the signal can be received by multiple cell sites, if the scheduling is coordinated from the different cell sites, the system can take advantage of this multiple reception to significantly improve the link performance. In the following sections, the CoMP architecture and the different CoMP schemes will be discussed.
CoMP communications can occur with intra-site or inter-site CoMP as shown in Figure 7.7.
With intra-site CoMP, the coordination is within a cell site. The characteristics of each type of CoMP architecture are summarized in Table 7.1.
An advantage of intra-site CoMP is that significant amount of exchange of information is possible since this communication is within a site and does not involve the backhaul (connection between base stations). Inter-site CoMP involves the coordination of multiple sites for CoMP transmission. Consequently, the exchange of information will involve backhaul transport. This type of CoMP may put additional burden and requirement upon the backhaul design.
An interesting CoMP architecture is the one associated with a distributed eNB depicted in Figure 7.8. In this particular illustration, the Radio Remote Units (RRU) of an eNB are located at different locations in space. With this architecture, although the CoMP coordination is within a single eNB, the CoMP transmission can behave like inter-site CoMP instead.
DL COMP
In terms of downlink CoMP, two different approaches are under consideration: Coordinated scheduling, or Coordinated Beamforming (CBF), and Joint Processing/Joint Transmission (JP/JT). In the first category, the transmission to a single UE is transmitted from the serving cell, exactly as in the case of non-CoMP transmission. However, the scheduling, including any Beamforming functionality, is dynamically coordinated between the cells in order to control and/or reduce the interference between different transmissions. In principle, the best serving set of users will be selected so that the transmitter beams are constructed to reduce the interference to other neighboring users, while increasing the served user’s signal strength.
For JP/JT, the transmission to a single UE is simultaneously transmitted from multiple transmission points, across cell sites. The multi-point transmissions will be coordinated as a single transmitter with antennas that are geographically separated. This scheme has the potential for higher performance, compared to coordination only in the scheduling, but comes at the expense of more stringent requirement on backhaul communication.
Depending on the geographical separation of the antennas, the coordinated multi-point processing method (e.g. coherent or non-coherent), and the coordinated zone definition (e.g. cell-centric or user-centric), network MIMO and collaborative MIMO have been proposed for the evolution of LTE. Depending on whether the same data to a UE is shared at different cell sites, collaborative MIMO includes single-cell antenna processing with multi-cell coordination, or multi-cell antenna processing. The first technique can be implemented via precoding with interference nulling by exploiting the additional degrees of spatial freedom at a cell site. The latter technique includes collaborative precoding and CL macro diversity. In collaborative precoding, each cell site performs multi-user precoding towards multiple UEs, and each UE receives multiple streams from multiple cell sites. In CL macro diversity, each cell site performs precoding independently and multiple cell sites jointly serve the same UE.
UL COMP
Uplink coordinated multi-point reception implies reception of the transmitted signal at multiple geographically separated points. Scheduling decisions can be coordinated among cells to control interference. It is important to understand that in different instances, the cooperating units can be separate eNBs’ remote radio units, relays, etc. Moreover, since UL CoMP mainly impacts the scheduler and receiver, it is mainly an implementation issues. The evolution of LTE, consequently, will likely just define the signaling needed to facilitate multi-point reception.
INTER-CELL INTERFERENCE COORDINATION
Another simple CoMP transmission scheme which relies on resource management cooperation among eNBs for controlling inter-cell interference is an efficient way to improve the cell edge spectral efficiency. The Inter-Cell Interference Coordination (ICIC) enhancement currently being studied for LTE-Advanced can be classified into dynamic Interference Coordination (D-ICIC) and Static Interference Coordination (S-ICIC). In D-ICIC, the utilization of frequency resource, spatial resource (beam pattern) or power resource is exchanged dynamically among eNBs. This scheme is flexible and adaptive to implement the resource balancing in unequal load situations. For S-ICIC, both static and semi-static spatial resource coordination among eNBs are being considered.
More information coule be found in:
- Coordinated Multipoint Trials in the Downlink - Fraunhofer Heinrich Hertz Institute
- 3GPP TR 36.814: Further Advancements for E-UTRA Physical Layer Aspects