Wireless Future - Telenor

More documents

Recommendations

Info

Figure 10 Initiating call from PSTN/ISDN or mobile phone 114 SCP IN serv CallReq(Y:Device) X:User 2:Device 3:Device ISUP Gateway two alternatives similar to the ones mentioned in the previous section: To use SIP/H323 or an open API like OSA or Parlay. 6.2 Receiving Service When a service is addressed to the user the service request is sent to the Virtual Terminal. The Virtual Terminal will deduce the most appropriate device by going through the list of registered devices and the user profile. The Virtual Terminal is initiating signalling at this device. At this point there are three use cases: Accepting a request, receiving in mailbox and refusing a request. 6.2.1 Accepting a Request If the user accepts the service, two connections will be established: one between the requesting service or device and the Virtual Terminal and another between the Virtual Terminal and the selected device. It is worth noting that there are again three solutions that are similar to the ones considered earlier in the use case Initiating service. Y:Device PSTN/ISDN 6.2.2 Receiving in Mailbox If the user is busy or does not want to receive the service at the time of the request he can specify that the service should be delivered to his mailbox. Again there are several alternatives for the mailbox, e.g. voice mail, e-mail and SMS. 6.2.3 Refusing a Request If the user receives a service request he does not want to accept, he can simply refuse the request and no connection is made. The user should be able to keep a list of services, phone numbers, IP addresses etc. that he does not want to receive in his Virtual Terminal, or he can refuse the request manually after a notification of the service request. ISUP Gateway Gateway Mobile Network 1:Device SIP/H323 IP-based Network CallReq (Y:Device) X:Virtual Terminal 6.3 Using Multiple Devices After a service is initiated or a service request is accepted, a connection is established. During a session, the user might want to use multiple devices for input and output simultaneously and to dynamically change which devices to use according to what kind of services he is using and according to his needs and available devices at any time. He may also wish to add new devices to his session on the fly. The Virtual Terminal will manage this for him without requiring the user to have any technical skills. 6.3.1 Activating and Deactivating Devices This use case is used by the use cases Changing device and Adding/Releasing device, which will be described later. When the user is changing devices, what he is really doing is to activate one device and deactivate the previous one. Similarly, when adding or releasing devices to or from an ongoing session, one is simply activating or deactivating the devices in question. During an ongoing session, activating a device will include it in the session and deactivating it will exclude it. No device is considered active in idle mode. There are two ways of activating/deactivating a device: • Manually: The user tells the Virtual Terminal which device or devices to be used explicitly. Such activation should be easy to perform or else the user will not use it. For PCs, PDAs, it is no problem letting the user enter his selection. For mobile phones, which have a more restricted user interface, it is more difficult. One solution is to assign a number to each device. The user can use any phone with a # key to register a device by simply enter * then the number assigned to this device and termi- Telektronikk 1.2001
nate with #. In this scheme USSD (Unstructured Supplementary Services Data) is used to send the command to the IN service, which forwards it to the Virtual Terminal. • Automatically: Bluetooth may be used to detect and activate devices. The user still needs to activate an initial device as for example his mobile phone. When entering his office where a multimedia PC is available or when entering his living room where a stereo system or a TV is available, the mobile phone will detect the presence of these devices. The mobile phone asks for the device IDs, e.g. IP address etc. and also what types the devices are. It is necessary to have sufficient authentication and access control schemes to prevent illegal use of the equipment. It is worth noting that with automatic registration it is not necessary to have a definition of a device in the user profile since the device type can be provided on the fly by the device itself. It is, however, more important to have sufficient security. The mobile phone can then send the device ID and the device type to the IN service, which forwards it to the Virtual Terminal. The Virtual Terminal can then activate the device. It is necessary to elaborate a strategy for selection and activation of devices because approaching a device does not necessarily mean that the user wants to change over to this device. A combination of automatic and manual activation of devices might be the preferred solution: Devices are detected automatically, and the user is simply asked whether or not he wants this new device to be activated or not by his active device. In this way the user will gain control over which devices are active, but minimal user interaction is required. microphone Telektronikk 1.2001 LS stereo Bluetooth for detection of unknown devices TV LS 6.3.2 Using Multiple Devices Simultaneously If a user wants to use a device during a communication session, it is required that the appropriate input and output streams are delivered to this device. In the case where the user wants to use multiple devices simultaneously, the need arises to deliver multiple streams to the different devices simultaneously. In order to achieve this, there must be some sort of splitting or multiplying of the incoming stream that is to be delivered to several output devices and some sort of merging of the outgoing streams that are collected from different input devices. We will look at the two different situations where the connections are established and routed through the Virtual Terminal and where they are routed directly between the device and the service. 6.3.2.1 Connection through the Virtual Terminal We now assume that a connection is being made between one or more of the user’s devices and a service, and that this connection is routed through the Virtual Terminal. X:User PC TELECOM NETWORK 1:Device 2:Device 3:Device 4:Device LS = loudspeaker VT Stream (x) Figure 11 Multiplying the incoming stream in the Virtual Terminal and delivering identical streams to all active devices X:Virtual Terminal A:Service Stream (x) Figure 12 Virtual Terminal as a set of communication devices + other electronic devices connected to the network 115
Page 2 and 3:
Telektronikk Volume 97 No. 1 - 2001
Page 4 and 5:
Per Hjalmar Lehne (42) obtained his
Page 6 and 7:
Stein Svaet (41) is Senior Research
Page 8 and 9:
Pbit/day 6 150 125 100 75 50 25 0 F
Page 10 and 11:
8 Video communication as a utility
Page 12 and 13:
10 The idea of reconfigurable mobil
Page 14 and 15:
12 Switched lobe Dynamically phased
Page 16 and 17:
Figure 10 The All IP vision Figure
Page 18 and 19:
16 The IP world has some problems t
Page 20 and 21:
18 Abbreviations and acronyms less
Page 22 and 23:
Jorge Pereira (40) obtained his Eng
Page 24 and 25:
(Millions) Figure 1 Exponential gro
Page 26 and 27:
24 Defining Generation based upon D
Page 28 and 29:
Multi-mode Terminal by Software Rad
Page 30 and 31:
distribution layer possible return
Page 32 and 33:
30 A Co-Ordinated Approach to 4G As
Page 34 and 35:
Figure 2 Applications will grow fas
Page 36 and 37:
Figure 5 Evolution from multi-mode
Page 38 and 39:
Operator/Provider download librarie
Page 40 and 41:
Radio network subsystem - service c
Page 42 and 43:
Dr. Techn. Jørgen Bach Andersen (6
Page 44 and 45:
Figure 3 Two arrays with M and N el
Page 46 and 47:
Figure 5 Cumulative probability dis
Page 48 and 49:
Figure 8 As in Figure 5, but with F
Page 50 and 51:
48 Conclusion The challenge of prov
Page 52 and 53:
50 models are described simply by a
Page 54 and 55:
52 ping intervals or “quantizatio
Page 56 and 57:
Figure 3 ASE as a function of the a
Page 58 and 59:
56 7 Conclusion and Further Researc
Page 60 and 61:
Dave Wisely (39) graduated in 1982
Page 62 and 63:
Figure 2 Business case study Figure
Page 64 and 65:
Figure 6 BRAIN QoS architecture 62
Page 66 and 67: 64 4 BRAIN homepage. (2001, March 6
Page 68 and 69: Figure 2 The Bluetooth protocol sta
Page 70 and 71: Figure 5 A Bluetooth radio module i
Page 72 and 73: 70 • Instant postcard: A Bluetoot
Page 74 and 75: 72 work visions come true, it is ne
Page 76 and 77: Table 1 Allocated HiperLAN bands (i
Page 78 and 79: Figure 4 Basic MAC frame structure
Page 80 and 81: 78 Preamble BCH FCH ACHs Preamble S
Page 82 and 83: throughput bit/s 80 3 2.5 2 1.5 1 0
Page 84 and 85: 82 5 References 1 CEPT. ERC Decisio
Page 86 and 87: 84 IETF Internet Engineering Task F
Page 88 and 89: Figure 2-3 Mobile IPv6 architecture
Page 90 and 91: 88 domain, it attaches to a new lea
Page 92 and 93: 90 Domain GFA/MAP Figure 3-3 Archit
Page 94 and 95: Geir Gylterud (35) is Research Scie
Page 96 and 97: 94 Framework Resource Resource Int
Page 98 and 99: Figure 6 SCSs and network functiona
Page 100 and 101: Figure 9 The new business model. Fr
Page 102 and 103: 100 A strong consortium backs up th
Page 104 and 105: 102 Music Company Figure 3 Service
Page 106 and 107: Figure 4 OSA architecture service c
Page 108 and 109: Do van Thanh (43) obtained his MSc
Page 110 and 111: Figure 2 The first use case diagram
Page 112 and 113: 110 Box 1 - The Open Service Archit
Page 114 and 115: 112 X:User 1:Device 2:Device 3:Devi
Page 118 and 119: Figure 13 Splitting the incoming st
Page 120 and 121: Figure 17 A set of communication de
Page 122 and 123: 120 Box 3 continued Session Descrip
Page 124 and 125: Figure 21 A laptop and peripheral d
Page 126 and 127: 124 Box 4 - Bluetooth Bluetooth is
Page 128 and 129: 126 6 The ICEBERG project. (2001, M
Page 130 and 131: 128 new door towards the upcoming f
Page 132 and 133: ? Figure 1 The Mobile Service Platf
Page 134 and 135: Figure 2 Needs and Related Services
Page 136 and 137: 134 Telektronikk 1.2001
Page 138 and 139: 136 Telektronikk 1.2001
Page 140 and 141: Anne Lise Lillebø (52) is Adviser
Page 142 and 143: 140 with other SDOs (Standards Deve
Page 144 and 145: 142 Box 2 - ETNO Declaration We, th
Page 146 and 147: Arve Meisinset (52) is Senior Resea
Page 148 and 149: 146 In ITU-T we have seen needs to
Page 150 and 151: 148 Each viewpoint constitutes a se
Page 152 and 153: Figure 2 UML class diagrams for tra
Page 154 and 155: 152 The functionality describing th
Page 156 and 157: 154 9 Potter, B et al. An introduct
show all

Wireless Future - Telenor

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?