1、 Reference number ISO/IEC 24793-2:2010(E) ISO/IEC 2010INTERNATIONAL STANDARD ISO/IEC 24793-2 First edition 2010-12-15 Information technology Mobile multicast communications: Protocol over native IP multicast networks Technologies de linformation Communications de diffusion groupe mobile: protocole s
2、ur des rseaux natifs IP de diffusion groupe ISO/IEC 24793-2:2010(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installe
3、d on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products
4、 used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, plea
5、se inform the Central Secretariat at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2010 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfi
6、lm, without permission in writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published by ISO in 2011 Published i
7、n Switzerland ii ISO/IEC 2010 All rights reservedISO/IEC 24793-2:2010(E) ISO/IEC 2010 All rights reserved iiiCONTENTS Page 1 Scope 1 2 Normative references . 1 3 Definitions 1 4 Abbreviations . 1 5 Overview 2 6 Considerations 3 6.1 Protocol model 3 6.2 Protocol entities . 3 6.3 Reference network con
8、figuration 4 6.4 Messages . 5 7 Procedures 5 7.1 Multicast data transport . 5 7.2 Session join . 5 7.3 User leave 6 7.4 Status monitoring 6 7.5 Handover support 7 8 Packets 9 8.1 Packet format and common header . 9 8.2 Parameter format . 10 8.3 Packets for session join . 12 8.4 Packets for user leav
9、e 14 8.5 Packets for status monitoring 14 8.6 Packets for handover support 15 Annex A Timers . 17 Annex B State transition diagram . 18 Bibliography 20 iv Foreword .ISO/IEC 24793-2:2010(E) iv ISO/IEC 2010 All rights reservedForeword ISO (the International Organization for Standardization) and IEC (t
10、he International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with parti
11、cular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have estab
12、lished a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint techni
13、cal committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and
14、 IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC 24793-2 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 6, Telecommunications and information exchange between systems, in collaboration with ITU-T. The identica
15、l text is published as ITU-T Rec. X.604.1 (03/2010). ISO/IEC 24793 consists of the following parts, under the general title Information technology Mobile multicast communications: Part 1: Framework Part 2: Protocol over native IP multicast networks ISO/IEC 24793-2:2010 (E) Rec. ITU-T X.604.1 (03/201
16、0) 1 INTERNATIONAL STANDARD RECOMMENDATION ITU-T Information technology Mobile multicast communications: protocol over native IP multicast networks 1 Scope This Recommendation | International Standard describes the specification of mobile multicast control protocol (MMCP) over native IP multicast ne
17、tworks for mobile multicast communications. The MMCP can be used to support a variety of multimedia multicasting services in the IP-based wireless mobile networks. The MMC is targeted at the real-time one-to-many multicast services and applications over mobile communications networks. This Recommend
18、ation | International Standard describes the procedures and packet formats of the MMCP protocol. 2 Normative references The following Recommendations and International Standards contain provisions which, through reference in this text, constitute provisions of this Recommendation | International Sta
19、ndard. 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 investigate the possibility of applying the most recent edition of the Re
20、commendations 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 Recommendations. Recommendation ITU-T X.604 (2010) | ISO/IEC 24793-1:2010,
21、 Information technology Mobile multicast communications: Framework. 3 Definitions This Recommendation | International Standard uses the terms and definitions that are defined in the MMC framework, Rec. ITU-T X.604 | ISO/IEC 24793-1. 4 Abbreviations For the purposes of this Recommendation | Internati
22、onal Standard, the following abbreviations are used: AAA Authentication, Authorization and Accounting ACK Acknowledgement ASR Aggregation Status Report CTT Context Transfer Time HCT Handover Context Transfer HIC Handover Initiation Confirm HIR Handover Initiation Request HIT Handover Initiation Time
23、 HTA Handover Transfer ACK ID Identifier IGMP Internet Group Management Protocol JWT Join Waiting Time LJC Local Join Confirm LJR Local Join Request LMC Local Mobility Controller MCS Multicast Contents Server MLD Multicast Listener Discovery ISO/IEC 24793-2:2010 (E) 2 Rec. ITU-T X.604.1 (03/2010) MM
24、C Mobile Multicast Communications MMCF MMC Framework MMCP Mobile Multicast Control Protocol MN Mobile Node MR Multicast Router PoA Point of Attachment QoS Quality of Service SJC Session Join Confirm SJR Session Join Request SM Session Manager SPT Status Probe Time SRT Status Report Time TLV Type-Len
25、gth-Value ULC User Leave Confirm ULR User Leave Request USP User Status Probe USR User Status Report 5 Overview The MMCP provides the control functionality for multicast data channels: Session Join, Status Monitoring and Handover Support. A multicast data session consists of an MCS (sender) and many
26、 MNs (receivers). The MCS will transmit multicast data packets to many prospective receivers, according to a predetermined program schedule. To receive the multicast data in the network, an MN will first perform the IGMP/MLD operations with the corresponding access router in the IP subnet. The MMCP
27、can be used for control of multicast sessions together with any multicast data channels. The details of multicast data transport mechanisms are outside the scope of MMCP. For Session Join, a prospective MN shall send a session join request message to the MMCP session manager (SM). The join request m
28、essage shall include the following information: Session ID and MN ID. MN ID is an identifier allocated to the MN, which may be given a priori by a services provider. On receipt of the session join request message, the SM shall respond to the MN with a session join confirm message. The responding con
29、firmation message will indicate whether the join request is accepted or not. In case that a local mobility controller (LMC) is allocated to the MN, the session join confirm message will also contain the contact information of the associated LMC. In case that an LMC is assigned to the MN, after recei
30、ving the join confirm message, the MN shall also join the designated LMC by sending a local join request message. On receipt of the local join request message, the LMC shall respond to the MN with a local join confirm message. For User Leave, during the multicast session, an MN may want to leave the
31、 session. For this purpose, the MN may send a user leave request message to the LMC (in case that an LMC is assigned to the MN) or to the SM (in case that no LMC is assigned to the MN). The LMC (or SM) may respond to the MN with the user leave confirm message. It is noted that this user leave operat
32、ion is optional. That is, a certain MN may leave the session without any notice. Status Monitoring is used by the SM to monitor the dynamics for group/session membership and the status of multicast data channel (e.g., statistics such as total number of packets received during the session). For statu
33、s monitoring, each MN shall send a periodic status report message to its upstream LMC or SM (in case that no LMC is assigned to the MN). Each LMC will aggregate the status information for its downstream MNs, and send a periodic aggregate status report message to the SM. In the meantime, the status r
34、eport messages may be lost in the network. In this case, the upstream LMC or SM may solicit a status report message to the concerned MN or LMC by sending a status probe message. For Handover Support, after movement detection, the MN begins the handover operations by sending a handover request messag
35、e to the current LMC. The handover request message shall include the information about the new point of attachment (PoA) such as the link-layer MAC address or ID of the PoA. On receipt of a handover request message from the MN, the LMC will first identify which subnet the MN is going to move into. T
36、he current LMC can identify the new LMC by using the address of the ID of the new PoA that is indicated in the handover request message. For handover support, the current LMC shall send a handover context transfer message to the new LMC. Then, the new LMC will perform the IGMP/MLD join operation to
37、the new MR, instead of the MN. This will ensure that the MN can receive the multicast data packets in the newly visited subnet as fast as possible. After that, the new LMC will respond ISO/IEC 24793-2:2010 (E) Rec. ITU-T X.604.1 (03/2010) 3 to the current LMC with a handover transfer ACK message. In
38、 turn, the current LMC will send a handover confirm message to the MN. This will complete the handover operation of the MMCP. After further movement, the MN will complete the establishment of a new L2 and L3 connection (for a new IP address of the MN). Then, the MN performs the local join operations
39、 with the new LMC. 6 Considerations 6.1 Protocol model The MMCP is based on the mobile multicast communications framework (MMCF) specified in Rec. ITU-T X.604 | ISO/IEC 24793-1. The MMCP is designed to support one-to-many real-time multicast applications running over IP multicast-capable wireless/mo
40、bile networks. MMCP operates over IPv4/IPv6 networks with the IP multicast forwarding capability such as the IGMP/MLD and IP multicast routing protocols. As a control protocol, the MMCP provides a mobile user with the session join and user leave, status monitoring, and handover support for multicast
41、 data channels. The MMCP is a control protocol that is used for control of the mobile multicast sessions over native IP multicast mobile/wireless networks. It is assumed that the multicast data channels are provided with the help of the UDP/IP multicasting in the network. That is, the MMCP is indepe
42、ndent of multicast data channels, as depicted in Figure 1. X.604.1(10)_F01 Multicast applications UDP IP MMCP Control channel Data transport channelFigure 1 Protocol model A multicast data channel can use the MMCP protocol for the control of multicast sessions. For this purpose, the MMCP provides a
43、set of application programming interfaces (APIs) for any multicast data channels/applications. In the protocol stack point of view, an MMCP message is encapsulated into the UDP datagram. 6.2 Protocol entities This clause describes the protocol entities associated with the MMCP. 6.2.1 Mobile node (MN
44、) An MN represents an end user that receives multicast data transport services from multicast contents server. To receive the multicast data from the network, the MN should be equipped with the multicast capability such as the IGMP/MLD protocol. The MN is also required for the MMCP functionality. Wi
45、th the help of MMCP, an MN can benefit from the control services such as session join, status monitoring, and handover support. 6.2.2 Multicast contents server (MCS) In MMCP, an MCS represents the sender of the multicast data channel/session. The MCS will continue to transmit the multicast data stre
46、ams over the network, and a lot of MNs will receive the data packets after session join. The MCS is associated with the multicast data channel only rather than the MMCP control channel. The MCS could exchange some session-related information with the MMCP session manager, possibly using a dedicated
47、communication channel, which is outside the scope of this Specification. 6.2.3 Session manager (SM) The SM is responsible for the overall operations of the MMCP. In Session Join, the SM will respond to the join request of a promising MN. For authentication, the SM may contact with an AAA-related dat
48、abase or user profile that has been preconfigured by services provider, which is outside the scope of the MMCP. In Status Monitoring, the SM will monitor the overall status of the membership and session for all of the MNs. For this purpose, each MN will send periodic control messages to the SM, poss
49、ibly by way of a local mobility controller. The SM may be implemented with the MCS on the same system, which is an implementation issue. ISO/IEC 24793-2:2010 (E) 4 Rec. ITU-T X.604.1 (03/2010) 6.2.4 Local mobility controller (LMC) The LMC is used to locally control the movement of the MN. In the mobile wireless networks, when an MN moves into the other network region during the multicast session, the handover support is required for seamless multicast services. The LMC is used to support the seamless handover for the MN in the wireless/mobile netw
