4/24/20071 Convergence of Communication Technologies and Strategies for Higher Ed Tim Callahan University of Michigan 4/24/2007

Tim Callahan University of Michigan - Ann Arbor 2 Overview  The current environment  Rising problems to address, reasoning  Emerging technical areas  The potential  The reality  Conclusions

4/24/2007Tim Callahan University of Michigan - Ann Arbor 3 Convergence Today  Today’s wireless networks are typically built for portable data access, but some mobility is becoming available  We see trends towards true mobility supporting real time applications

4/24/2007Tim Callahan University of Michigan - Ann Arbor 4 Which Convergence ?  Convergence is coming in many forms  On the infrastructure: WLAN-Cellular-WiMAX  Across networks: wired and wireless management  At the backend and across services:  Unified communications  VoIP-VoFi-PBX (likewise with video, etc.)  IMS, SIP  At the user:  Multi-mode devices (dual-mode phones)  Cognigtive radios

4/24/2007Tim Callahan University of Michigan - Ann Arbor 5 Reasons to change?  Consider your mission  For example: Provide communication tools and resources to foster research and education  with cost recovery in mind  opt-in (i.e., decentralized) participation  Consider level of reliability, risks, financial stakes, and who pays  Do “Very Good Things” (VGT)

4/24/2007Tim Callahan University of Michigan - Ann Arbor 6 Reasons to Change  Convergences may enable:  Reduced installation and operational costs  new, valued services  Reduction of redundant infrastructures  Same voice service on PBX, VoIP, VoFi, Cellular  Reduce total customer bills (good for the school/state)  Services across previous previous barriers

4/24/2007Tim Callahan University of Michigan - Ann Arbor 7 Reasons: Rising Problems  Fading use of traditional voice  Increased integration of communications into the classroom  New teaching and learning models  New tools- DyKnow, consumer technology  Capacity and coverage in wireless  Dense user areas  More devices per user: dual mode, media, game systems  Cellular on campus and inside

4/24/2007Tim Callahan University of Michigan - Ann Arbor 8 Reasons: Rising Problems  Why not just outsource?  What’s so special about higher ed?  The academic enterprise and response from providers  Successful partnerships?

4/24/2007Tim Callahan University of Michigan - Ann Arbor 9 Evolving Technologies  Today’s environment is not mature, but it is evolving  FMC, UMA, IMS, Vo-Fi, WiMAX, DAS  Some hype, some sales pitch, some reality  Fixed and mobile wireless, services  What do they mean - for you-  Time of creativity, opportunity, and development  They will make an impact during the lifetime of technologies implemented today

4/24/2007Tim Callahan University of Michigan - Ann Arbor 10 Important New Elements  Presence / location awareness  Network: Know where you are before initiating communications (may require a “phone home” component for the user  Physical: Geographical location and user profile (service acts different at different locations)  Caution: users have more than one device

4/24/2007Tim Callahan University of Michigan - Ann Arbor 11 Important New Elements  Ability to cross boundaries  Internal: WLAN to LAN infrastructures, across services  Internal-External: From the network you control to a network you don’t control  “what” crosses the boundaries?

4/24/2007Tim Callahan University of Michigan - Ann Arbor 12 The Potential  Do some Very Good Things:  If you could start fresh?  Can head towards a pervasive communications environment  Redefine communication models: number and address replacement with more intuitive models  The user is the center of his universe and that universe follows him everywhere  Think “security alert”

4/24/2007Tim Callahan University of Michigan - Ann Arbor 13 The Potential, Continued  Pervasive communications, continued…  Role based access  Think guest access, visiting scholars, 1st time users  “Cognitive Services”  Services react to conditions in the user profile  User profile defined by user, administrator, network conditions, location, etc…  Actions based on profiles of all parties involved (sender and receiver)

4/24/2007Tim Callahan University of Michigan - Ann Arbor 14 The Potential  Direct money and resources to one infrastructure supporting all services  Better efficiencies, better capacity and coverage (in theory, but new risks too)  Enable more versatile distribution of content, anytime anywhere learning  Handoffs possible across boundaries  Consistency of functionality across boundaries

4/24/2007Tim Callahan University of Michigan - Ann Arbor 15 The Reality  We can’t start from scratch  Efficient upgrades, integrations with existing systems  Pervasive, wall to wall network is different than a portable data network (buildout, requirements for services)  If it isn’t pervasive, then will the case for new services and architecture still be supported?

4/24/2007Tim Callahan University of Michigan - Ann Arbor 16 The Reality -Risks  We can’t start from scratch, cont’d  User adoption - why change?  F/S vs Students  Intuitive interfaces and the “lazy user”  Meet the fundamental needs first  The correct default profile and training  Pay now for future features? Fund that…  Users are throwing money at you now to…

4/24/2007Tim Callahan University of Michigan - Ann Arbor 17 The Reality - Risks  Technologies aren’t mature; higher risk; $  Not all good technologies/companies survive  How important is your school (compared to the rest of the combined market)? How about all of Higher Ed combined?  Will we be allowed to use new features?  Think GPS on your cell phone  Sold / affordable for carriers only?

4/24/2007Tim Callahan University of Michigan - Ann Arbor 18 Conclusions  First, state the obvious  When possible, follow standards  SIP for communications  Bariblu app on dual mode, desk, cell handset  IP infrastructure  (now think cellular data integration, mobile broadband…)  Justify the changes over the lifetime of the investment  Know your user’s (evolving) requirements

4/24/2007Tim Callahan University of Michigan - Ann Arbor 19 Conclusions  Changes may only be beneficial by looking at an integrated architecture across services and infrastructures  Changes may require different funding models and strategies  Changes will be significantly more than an equipment upgrade  Can you deploy it and are you allowed to configure the desired features, will they work across boundaries?

4/24/2007Tim Callahan University of Michigan - Ann Arbor 20 Conclusions  It may be prudent to wait  Let the market evolve more  Wait for changes to solidify, such as 11.n  … or play a more active role in the evolution of the technologies  Can we (Higher Ed) take a team approach and voice our requirements for features, functionality, and service options?  Better response from carriers and vendors?  We don’t all have the same needs, but what do we have in common? What’s so special…

4/24/2007Tim Callahan University of Michigan - Ann Arbor 21 Thank You  Questions and Discussions?  Tim Callahan University of Michigan - Ann Arbor 