Wireless Future - Telenor

More documents

Recommendations

Info

112 X:User 1:Device 2:Device 3:Device Figure 9 Initiating service from an IP-based device ISUP PSTN/ISDN Gateway ISUP Gateway Gateway Mobile Network In order to realise the Use Case Initiating Service the following conditions must be met: • Every object Virtual Terminal must have an identity that is visible to all devices, i.e. it should be possible to address the Virtual Terminal from any device. Each Virtual Terminal may have several identifiers: - An MSISDN number (telephone number); - An email address; SIP/H323 IP-based Network A:Service X:Virtual Terminal - Some kind of unique identifiers conformed to OSA/Parlay [7,8]. If the Virtual Terminal has several identifiers, a mapping between these identifiers is required. • It should be possible to establish a connection from any device to the Virtual Terminal and a connection from the Virtual Terminal to any service or any other device. The Virtual Terminal must be capable of acting as a connector that connects the streams together. The user may have different devices connected to different networks. One device can be an IP phone or a PC directly connected to an IP-based network, another device can be a fixed phone or cordless phone connected to the PSTN/ISDN network, and a third device can be a cellular phone connected to a mobile network such as GSM. The protocols used to establish and terminate a connection vary for different networks. For IPbased networks either SIP [9] or H323 [10] protocols should be used but for PSTN/ISDN and mobile networks, the protocol is SS7 ISUP. When the user initiates a service from a chosen device a connection must be established from this device to the Virtual Terminal. Different protocols should therefore be used depending on the type of device, i.e. IP-based device contra PSTN/ISDN or mobile device. Let us consider these two device types successively. 6.1.1 Initiating Services from an IP-based Device If the user uses a device that is connected to an IP-based network, either SIP or H323 protocol is used for signalling. In addition, information on the requested service or device must be conveyed to the Virtual Terminal so that it knows which service or device to connect to. This case is illustrated in Figure 9. Two implementation alternatives are identified: Alternative 1: • Use SIP/H323 for establishment of connections. • Use CORBA/Java RMI for control and information exchange with the Virtual Terminal [11,12]. Alternative 2: • Use OSA/Parlay API for establishment of connections. • Use CORBA/Java RMI for control and information exchange with the Virtual Terminal. The most straightforward implementation will be to incorporate either SIP or H323 in the Virtual Terminal. However, such a solution does not imply portability since the code of the Virtual Terminal needs to be changed for each protocol. A better solution might be to use OSA/Parlay API since a generic and network independent Call control API is offered. Portability is hence ensured and the Virtual Terminal will function on either SIP or H323. 6.1.2 Initiating Services from PSTN/ISDN or Mobile Devices If the user uses either a device connected to the PSTN/ISDN network or a device connected to a mobile network such as GSM, the SS7 ISUP is used to establish connection. Assume that a user wants to make a telephone call to another phone. He dials the number of the addressed phone. The signalling must somehow be routed to the Virtual Terminal, and there is a need for an IN service, which sends the signalling to the Virtual Terminal. This IN service Telektronikk 1.2001
Box 2 – Parlay API The Parlay Group is an open, non-profit, multi-vendor forum organized to create open, technology independent Application Programming Interfaces (APIs) that enable IT companies, ASPs, ISVs, Internet Companies, E-Business Companies, software creators, service bureaux, and large and small enterprises as well as network providers, network equipment vendors and application suppliers to develop applications across multiple networks. Furthermore, the Group promotes the use of Parlay APIs and ultimate standardization. The Parlay API specifications are open and technologyindependent, so that the widest possible range of market players may develop and offer advanced telecommunication services. Framework Resource Functions provided by the service interfaces allow access to traditional network capabilities such as call management, messaging, and user interaction. The service interfaces also include generic application interfaces to ease the deployment of communications applications. In the current specification, Parlay API 2.1, the following Service interfaces are specified: Mobility, Call Control, User Interaction and Connectivity. All interfaces are specified in both OMG IDL (CORBA) and Microsoft MIDL (DCOM), which make the Parlay API independent of programming language, platform and Operating System. The call control service interface in Parlay 2.1 specifies one-to-one call, multiparty call, multimedia call and conference call. It is also possible for applications to initiate calls (“Call from the blue”). The Parlay API does not specify any mapping from service interfaces to proprietary interfaces. The implementers of the Parlay API have to perform the mapping according to the wanted underlying network technology such as SIP, H.323, CAMEL and ISUP, etc. The 3GPP OSA API is based on the Parlay API. The specification is available for free download at http://www.parlay.org/. is instantiated when the user registers a device as a component of the Virtual Terminal. The Virtual Terminal will then forward the signalling towards the addressed phone. If the party at the addressed phone accepts the call, two connections, one between the device and the Virtual Terminal and one between the Virtual Terminal and the addressed phone, will be established. This is shown in Figure 10. Telektronikk 1.2001 Resource Interface Applications Parlay APIs Resource Interface The Parlay architecture Service Interface Resource Interface The connection between the PSTN/ISDN or mobile device and the Virtual Terminal is established using the existing signalling mechanism, i.e. SS7 ISUP. However, the gateway between PSTN/ISDN and the mobile network must be capable of converting the signalling to either SIP or H323. For establishing the connection between the Virtual Terminal and the addressed phone there are 113
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 116 and 117: Figure 10 Initiating call from PSTN
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

Create successful ePaper yourself

Delete template?

Save as template?