1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T X.602TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (04/2004) SERIES X: DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS OSI networking and system aspects Networking Information technology Group management protocol ITU-T Recommendation X.602 ITU-T X-SERIES R
2、ECOMMENDATIONS DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS PUBLIC DATA NETWORKS Services and facilities X.1X.19 Interfaces X.20X.49 Transmission, signalling and switching X.50X.89 Network aspects X.90X.149 Maintenance X.150X.179 Administrative arrangements X.180X.199 OPEN SYSTEMS INTERCONNECTION Mo
3、del and notation X.200X.209 Service definitions X.210X.219 Connection-mode protocol specifications X.220X.229 Connectionless-mode protocol specifications X.230X.239 PICS proformas X.240X.259 Protocol Identification X.260X.269 Security Protocols X.270X.279 Layer Managed Objects X.280X.289 Conformance
4、 testing X.290X.299 INTERWORKING BETWEEN NETWORKS General X.300X.349 Satellite data transmission systems X.350X.369 IP-based networks X.370X.399 MESSAGE HANDLING SYSTEMS X.400X.499 DIRECTORY X.500X.599 OSI NETWORKING AND SYSTEM ASPECTS Networking X.600X.629 Efficiency X.630X.639 Quality of service X
5、.640X.649 Naming, Addressing and Registration X.650X.679 Abstract Syntax Notation One (ASN.1) X.680X.699 OSI MANAGEMENT Systems Management framework and architecture X.700X.709 Management Communication Service and Protocol X.710X.719 Structure of Management Information X.720X.729 Management function
6、s and ODMA functions X.730X.799 SECURITY X.800X.849 OSI APPLICATIONS Commitment, Concurrency and Recovery X.850X.859 Transaction processing X.860X.879 Remote operations X.880X.899 OPEN DISTRIBUTED PROCESSING X.900X.999 TELECOMMUNICATION SECURITY X.1000 For further details, please refer to the list o
7、f ITU-T Recommendations. ITU-T Rec. X.602 (04/2004) i INTERNATIONAL STANDARD ISO/IEC 16513 ITU-T RECOMMENDATION X.602 Information technology Group management protocol Summary The Group Management Protocol (GMP) is an application-layer control protocol for creating a group session and for managing th
8、e groups participating members. Generally it is assumed that there is one GMP server, one session-creating client (or Session Creator), and one or more session-participating clients (or Session Participants). The GMP includes session management (SM), membership management (MM), and the function of e
9、xchanging information between SM and MM. Source ITU-T Recommendation X.602 was approved on 29 April 2004 by ITU-T Study Group 17 (2001-2004) under the ITU-T Recommendation A.8 procedure. An identical text is also published as ISO/IEC 16513. Keywords Group Management, Membership Management, QoS Serve
10、r, Session Management. ii ITU-T Rec. X.602 (04/2004) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for st
11、udying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study gr
12、oups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with
13、 ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provis
14、ions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such
15、 words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position
16、 concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected
17、 by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2004 All rights reserved. No part of this publication may be reproduced
18、, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. X.602 (04/2004) iii CONTENTS Page 1 Scope 1 2 Normative references . 1 3 Definitions 1 3.1 Terms defined in ITU-T Rec. X.601 . 1 3.2 Terms defined in ITU-T Rec. X.605 . 2 3.3 Terms defined in this Recommendation | Int
19、ernational Standard 2 4 Abbreviations . 2 4.1 Message types . 2 4.1.1 SM Message types 2 4.1.2 MM Message types . 2 4.2 Miscellaneous 3 5 Conventions 3 6 Overview 3 6.1 Session Management. 4 6.2 Membership Management. 4 7 Protocol operations. 6 7.1 Session Management. 6 7.1.1 Session Creation 6 7.1.
20、2 Session Announcement . 7 7.1.3 Session Registration 7 7.1.4 Session Enrolment. 8 7.1.5 Session Activation. 8 7.2 Membership Management. 9 7.2.1 Membership Update 11 7.2.2 User Information Request and Response 13 7.2.3 Session Leave 13 7.2.4 Session Termination 14 7.3 Security . 15 8 GMP messages .
21、 17 8.1 Session Management message types. 17 8.2 Session Management message formats . 18 8.3 Membership Management message types. 20 8.4 Membership Management message formats . 20 9 GMP variables 22 9.1 Session-wide variables 22 9.2 Timers . 22 Bibliography 23 iv ITU-T Rec. X.602 (04/2004) Introduct
22、ion Conventional multicast transport protocols do not include a dynamic mechanism for group management according to the join/leave of receivers and for the modification of membership information. GMP provides a framework for multicast session management (SM) mechanism and membership management (MM),
23、 which supports the required management of multicast sessions and their members. This protocol can be key to reliable multicast communications. GMP will operate over conventional transport protocols and/or ECTP as shown in Figure 1. GMP Multicast application TCP, UDP, ECTP, etc. IP Figure 1 GMP mode
24、l (GMP protocol stack) ISO/IEC 16513:2004 (E) ITU-T Rec. X.602 (04/2004) 1 INTERNATIONAL STANDARD ITU-T RECOMMENDATION Information technology Group management protocol 1 Scope This Recommendation | International Standard provides a specification of a Group Management Protocol (GMP), which is an appl
25、ication-layer control protocol for creating a group session and for managing the groups participating members. The GMP consists of session management (SM), membership management (MM), and the function of exchanging information between SM and MM. SM is responsible for session creation and deletion. M
26、M manages the member lists based on session information retrieved from SM. According to ITU-T Rec. X.601, “Multi-peer communications framework“, the multi-peer communication service is achieved in seven distinct phases: registration, enrolment, activation, data transfer, deactivation, de-enrolment,
27、and de-registration. Since one of these operations data transfer may be performed using ECTP or TCP, SM may perform the rest of operations: creation, announcement, registration, enrolment, activation, including session announcement. In addition, MM manages group members who are in enrolled or active
28、 groups. SM may provide a convenient interface to users because it may be implemented on the Web. Operation of MM is transparent to users as in a transport protocol. 2 Normative references The following Recommendations and International Standards contain provisions which, through reference in this t
29、ext, constitute provisions of this Recommendation | International Standard. At the time of publication, the editions indicated were valid. All Recommendations and Standards are subject to revision, and parties to agreements based on this Recommendation | International Standard are encouraged to inve
30、stigate the possibility of applying the most recent edition of the Recommendations and Standards listed below. Members of IEC and ISO maintain registers of currently valid International Standards. The Telecommunication Standardization Bureau of the ITU maintains a list of currently valid ITU-T Recom
31、mendations. ITU-T Recommendation X.601 (2000), Multi-peer communications framework. ITU-T Recommendation X.605 (1998) | ISO/IEC 13252:1999, Information technology Enhanced Communications Transport Service definition. ITU-T Recommendation X.606 (2001) | ISO/IEC 14476-1:2002, Information technology En
32、hanced Communications Transport Protocol: Specification of simplex multicast transport. ITU-T Recommendation X.606.1 (2003) | ISO/IEC 14476-2:2003, Information technology Enhanced Communications Transport Protocol: Specification of QoS management for simplex multicast transport. 3 Definitions 3.1 Te
33、rms defined in ITU-T Rec. X.601 This Recommendation | International Standard is based on the concepts developed in the Multi-Peer Communications Framework (ITU-T Rec. X.601) and makes use of the following terms defined in that Recommendation: a) Multi-peer; b) Multi-peer communication; and c) Multic
34、ast transmission. ISO/IEC 16513:2004 (E) 2 ITU-T Rec. X.602 (04/2004) 3.2 Terms defined in ITU-T Rec. X.605 | ISO/IEC 13252 This Recommendation | International Standard is based on the concepts developed in Enhanced Communications Transport Service Definition (ITU-T Rec. X.605 | ISO/IEC 13252) and m
35、akes use of the following terms defined in that Recommendation: a) Enrolled Group; b) Registered Group; c) Active Group; and d) TC-owner. 3.3 Terms defined in this Recommendation | International Standard 3.3.1 GMP client: An application program that sends and receives GMP. Clients store and acquire
36、information through a server. All clients must log in to the server to acquire information from the server. Clients are largely divided between session creator and session participants. 3.3.2 GMP server: A server is an application program that is responsible for session management and membership man
37、agement. 3.3.3 session creator: A client who creates and who may terminate a session. Logging on to the server through its own ID, the creator inputs information about creating a session and sends the information to the server. The server that received the request from the creator adds the informati
38、on into the created session list. The Session creator may be a TC-owner defined in ECTS. 3.3.4 session client: A client who intends to be a Session Participant. 3.3.5 session participant: A Client who registers for a session intending to participate in that session. After registration, the session p
39、articipant will join the session to be an active member (i.e., start session list and registered member list). A Session Participant may be a TC-participant defined in ECTS. 4 Abbreviations For the purposes of this Recommendation | International Standard, the following abbreviations apply. 4.1 Messa
40、ge types 4.1.1 SM message types SAREQ Session Activation Request message SCACC Session Creation Accept message SCCON Session Creation Confirm message SCINF Session Creation Information message SCREJ Session Creation Reject message SCREQ Session Creation Request message SDREQ Session Deletion Request
41、 message SDRES Session Deletion Response message SJREQ Session Join Request message SJRES Session Join Response message SRACC Session Registration Accept message SRREJ Session Registration Reject message SRREQ Session Registration Request message SRRES Session Registration Response message 4.1.2 MM
42、message types KAREQ Keepalive Request message KARES Keepalive Response message UIREQ User Information Request message ISO/IEC 16513:2004 (E) ITU-T Rec. X.602 (04/2004) 3 UIRES User Information Response message LVREQ Leave Request message TRREQ Termination Request message TRIND Termination Indication
43、 message KDUPT Key Distribution Update message 4.2 Miscellaneous ECTP Enhanced Communications Transport Protocol ECTS Enhanced Communications Transport Service MM Membership Management RMT Reliable Multicast Transport SAP Session Announcement Protocol SDP Session Description Protocol SM Session Mana
44、gement IP Internet Protocol LQA Lowest Quality Allowed MSS Maximum Segment Size OT Operating Target QoS Quality of Service RSVP Resource reSerVation Protocol 5 Conventions In this Recommendation | International Standard, the keywords “MUST“, “REQUIRED“, “SHALL“, “MUST NOT“, “SHALL NOT“, “SHOULD“, “S
45、HOULD NOT“, “MAY“, and “OPTIONAL“ are to be interpreted as described in IETF RFC 2119, and indicate requirement levels for compliant ECTP implementations. Those keywords are case-sensitive. 6 Overview GMP is an application-layer control protocol for creating a group session and for managing the grou
46、ps participating members. Generally it is assumed that there is one GMP server, one session creating client (or Session Creator), and one or more session participating clients (or Session Participants) as shown in Figure 2. ISO/IEC 16513:2004 (E) 4 ITU-T Rec. X.602 (04/2004) X,602_F02Session partici
47、pantSession participant Session participantSession participantSession participant Session participantSession creatorLocal networkLocal networkGMP serverPublic InternetFigure 2 Network configuration for GMP GMP is composed of session management (SM), membership management (MM), and the function of ex
48、changing information between SM and MM. 6.1 Session Management SM may be achieved in eight distinct phases: creation, announcement, registration, enrolment, activation, de-registration, de-enrolment, and de-activation. A particular client, called a session creator, creates a session. Then, SM update
49、s the session list. The session creator will send a Session Creation Request message to the server. If accepted, the session creator will receive the Session Creation Accept message from the server. Then the session creator will send the detailed session information to the server and receive the confirmation message. If the session cannot be created or the session creator does not have the necessary rights, then the Session Creation Reject message will be returned. After successful session creation, the server
