Hi, The ROS concept can be found in the ITU-T X.880 series Recommendations, but it may be too detailed for the first round. The H.323 suppl. services are adaptations of ISDN supplementary services, so it seems worthwhile to look first into ETSI's ETS 300 196-1. This contains the general concept and basic constructs for the functional protocol of ISDN supplementary services (a practical application of ROS). In case you do not find what you are looking for, there remains the X.880 series...
Best Regards, Gy�rgy ============================================ dr. Gy�rgy R�THY Ericsson Communications Systems Hungary Lim. Conformance Center tel.: +36 1 437-7006; fax: +36 1 437-7767 mobile: +36 30 297-7862 e-mail: [EMAIL PROTECTED] web: http://www.r.eth.ericsson.se/~ethgry ============================================ >-----Original Message----- >From: Steen Oluf Karlsen [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, November 27, 2001 8:40 AM >To: [EMAIL PROTECTED] >Subject: RE: [ASN.1] ROS APDU > > >Then how about this: > >"However, there seems to be a consensus emerging that the solution will >involve replacing the ASN.1 macros with "tables". Where in the >past a macro >would be defined, instead a table type would be defined. > >A table type governs the number of columns in the table, and their >characteristics. The coloumns correspond to the various facets of this >kind of information object. For example, in the OPERATION table one >column might be declared to hold (UNIQUE) object identifier values; >this might model the opcode of the operation. Another column might be >declared to hold arbitrary ASN.1 types; this might model the >argument of >the operation (parameters to be transferred in the call of the -remote- >operation). > >A different user can then define particular rows of such a table, >(in this case the spec group of your H.xxx VoIP application) >corresponding to particular instances of that kind of information >object. The row of the OPERATION table corresponding to the "submit" >message operation for example, could be defined by supplying a specific >object identifier value for the opcode column ( of the table). > >As well as individual rows, a usere can also define, name, export and >import row-sets." > >Let this be a Tuesday morning Nov. 27. puzzle for you ASN.1 >experts - where >is this quote from ? > >Regards > >Steen Oluf Karlsen >S�holtvej 6 >Vester Vandet >DK-7700 Thisted >Danmark >email [EMAIL PROTECTED] >Tel +45 97 97 72 72 > > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Tanu >Malhotra >Sent: 26. november 2001 16:06 >To: [EMAIL PROTECTED] >Subject: RE: [ASN.1] ROS APDU > > >Hi > >It is related to H.450 Supplementary Services for VoIP. >Nothin' to do with >Mobile Communication in particular. Some traces of ROS concept >is also there >in Oliver's book but I want something more on it. > >For eg. ROS Invoke APDUs are send to invoke Call >tranfer(H.450.2) kind of >supplementary service in audio over IP phone. > >-tanu > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of >[EMAIL PROTECTED] >Sent: Monday, November 26, 2001 6:53 PM >To: [EMAIL PROTECTED] >Subject: RE: [ASN.1] ROS APDU > > >Maybe best if you could mention your application ? > >Just guessing: Mobile telecommunication ? > >Steen Oluf Karlsen >S�holtvej 6 >Vester Vandet >DK-7700 Thisted >Danmark >email [EMAIL PROTECTED] >Tel +45 97 97 72 72 > >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Tanu >Malhotra >Sent: 26. november 2001 10:18 >To: [EMAIL PROTECTED] >Subject: [ASN.1] ROS APDU > > >Hello All, > >Can anybody give me some information abt the Remote Operation Service >APDU(ROS)? I am basically interested in getting some >information abt the >Invoke APDUs, their linkID, InvokeID and the opCode part. > >Any kind of help would be appreciated. > >TIA >Tanu > >
