3GPP MBMS protocol stack

Slides:



Advertisements
Similar presentations
1 IPv6. 2 Problem: 32-bit address space will be completely allocated by Solution: Design a new IP with a larger address space, called the IP version.
Advertisements

© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Addressing the Network – IPv4 Network Fundamentals – Chapter 6.
1 Internet Protocol Version 6 (IPv6) What the caterpillar calls the end of the world, nature calls a butterfly. - Anonymous.
Problem of non-Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.0 Agenda Item: TBD.
Network Layer Packet Forwarding IS250 Spring 2010
K. Salah 1 Chapter 31 Security in the Internet. K. Salah 2 Figure 31.5 Position of TLS Transport Layer Security (TLS) was designed to provide security.
Introduction to Transport Layer. Transport Layer: Motivation A B R1 R2 r Recall that NL is responsible for forwarding a packet from one HOST to another.
William Stallings Data and Computer Communications 7 th Edition (Selected slides used for lectures at Bina Nusantara University) Transport Layer.
FIREWALLS & NETWORK SECURITY with Intrusion Detection and VPNs, 2 nd ed. 6 Packet Filtering By Whitman, Mattord, & Austin© 2008 Course Technology.
IETF 80: NETEXT Working Group – Logical Interface Support for IP Hosts 1 Logical Interface Support for IP Hosts Sri Gundavelli Telemaco Melia Carlos Jesus.
Chapter Overview TCP/IP Protocols IP Addressing.
Packet Filtering. 2 Objectives Describe packets and packet filtering Explain the approaches to packet filtering Recommend specific filtering rules.
Chapter 6: Packet Filtering
Networks – Network Architecture Network architecture is specification of design principles (including data formats and procedures) for creating a network.
CS 447 Networks and Data Communication
Doc.: IEEE /0961r0 Submission July 2012 Alex Ashley, NDS LtdSlide 1 Layer 2 Service Discovery Protocols Date: Authors:
The InetAddress Class Nipat J.. public class InetAddress  This class represents an Internet Protocol (IP) address.  An IP address is either a 32-bit.
3GPP Rel-13 Interworking discussions
Answer the Questions Regarding Pending Issues on Access Control Group Name: WG4 SEC Source: LG Electronics Meeting Date: Agenda Item: SEC#11.4.
Dean Cheng Jouni Korhonen Mehamed Boucadair
Omar A. Abouabdalla Network Research Group (USM) SIP – Functionality and Structure of the Protocol SIP – Functionality and Structure of the Protocol By.
Protocol Headers 0x0800 Internet Protocol, Version 4 (IPv4) 0x0806 Address Resolution Protocol (ARP) 0x8100 IEEE 802.1Q-tagged frame 0x86DD Internet Protocol,
Presented by Rebecca Meinhold But How Does the Internet Work?
Status Report on Access TP8 Group Name: WG2 Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:
Primitive End-to-End Security Requirements Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting.
1 Transport Protocols Relates to Lab 5. An overview of the transport protocols of the TCP/IP protocol suite. Also, a short discussion of UDP.
1 Chapters 2 & 3 Computer Networking Review – The TCP/IP Protocol Architecture.
Issues pertaining to IOP test Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd. Meeting Date: Agenda Item: TBD.
Routing Problem of the Current Architecture Group Name: ARC Source: Hongbeom Ahn, LG Electronics, Meeting Date: Agenda.
IETF 80: NETEXT Working Group – Logical Interface Support for IP Hosts 1 Logical Interface Support for IP Hosts Telemaco Melia, Sri Gundavelli, Carlos.
Subscription and Notification Issue Group Name: WG2 Source: Qi Yu, Mitch Tseng- Huawei Technologies, Co. LTD. Meeting Date: ~23 Agenda Item:
Specifying the Address of Management Client of Managed Entity Group Name: ARC Source: Hongbeom Ahn, SK Telecom, Meeting Date: TP#21 Agenda.
3GPP Rel-13 Interworking discussions Group Name: TP #18 Source: Rejesh Bhalla, ZTE Corporation, Meeting Date: Agenda Item:
1 Computer Networks Chapter 5. Network layer The network layer is concerned with getting packets from the source all the way to the destination. Getting.
3GPP R13 Small Data Delivery
Managing Retransmission Timers in Sleep Mode
Resource subscription using DDS in oneM2M
Transport Protocols Relates to Lab 5. An overview of the transport protocols of the TCP/IP protocol suite. Also, a short discussion of UDP.
Provisional Architecture for oneM2M
CSE Retargeting to AE, IPE, and NoDN Hosted Resources
CSE Retargeting to AE, IPE, and NoDN Hosted Resources
Group multicast fanOut Procedure
Group multicast fanOut Procedure
3GPP interworking in R3 Group Name: ARC
Managing Retransmission Timers in Sleep Mode
Issues of <locationPolicy> Discussion
draft-xu-isis-nvo-cp-00 Xiaohu Xu (Huawei) Saumya Dikshit (Cisco)
NIDD Discussion Points
MAF&MEF Interface Specification discussion of the next steps
3GPP Rel-13 Interworking discussions
OneM2M-ARC BRequest_Resource Architecture Proposal to address Broadcasting/Multicasting Requirements Group Name: WG2 Source: Takanori Iwai,
OSI Protocol Stack Given the post man exemple.
Group multicast Group Name: ARC
CMDH Refinement Contribution: oneM2M-ARC-0397R01
Session Initiation Protocol (SIP)
MinitorEvent(UE_Reachability)
Service Layer Dynamic Authorization [SLDA]
Transport Protocols Relates to Lab 5. An overview of the transport protocols of the TCP/IP protocol suite. Also, a short discussion of UDP.
Subject Name: Computer Communication Networks Subject Code: 10EC71
Transport Protocols Relates to Lab 5. An overview of the transport protocols of the TCP/IP protocol suite. Also, a short discussion of UDP.
Transport Protocols An overview of the transport protocols of the TCP/IP protocol suite. Also, a short discussion of UDP.
3GPP V2X Interworking Potential Impact
Chapter 10 IGMP Prof. Choong Seon HONG.
Technical Issues with draft-ietf-mpls-bfd-directed
16EC Computer networks unit II Mr.M.Jagadesh
Notification Target Discussion
Transport Protocols Relates to Lab 5. An overview of the transport protocols of the TCP/IP protocol suite. Also, a short discussion of UDP.
draft-ietf-bier-ipv6-requirements-01
IS 4506 Configuring the FTP Service
Presentation transcript:

3GPP MBMS protocol stack Group Name: ARC Source: Echo, Huawei, echo.xubei@huawei.com Meeting Date: 2017-05-22 Agenda Item: WI-0002 - Architecture

Question Is multicastAddress mandatory when the multicastType is 3GPP_MBMS_group? Table 10.2.7.13-1: Multicast Group Information managed by group hosting CSE Information Multiplicity Description groupID 1 Indicates the <group> resource identifier which the Multicaste Group Information belongs to. multicastType Indicates the underlying networks multicast capability of the group members, the value shall be one of the following: 3GPP_MBMS_group, IP_mulicast_group. externalGroupID 0..1 If the multicastType is 3GPP_MBMS_group, the externalGroupID is the External-Group-ID as specified in 3GPP TS23.682[i.14] clause 4.6.3 multicastAddress 1?? The multicast address is allocated to the members in the memberList and shared by the members of this multicast group. The procedure of multicast address configuration is specified in RFC7390[xx] addressType It is used to describe the address type of the multicastAddress, e.g. IPv4 or IPv6. multicastGroupFanoutTarget Used as the target URI of the fan out request sending to the members. It is a virtual identifier allocated by the group hosting CSE corresponding to the access paths (i.e. Resource-IDs, which may be different) of the member resources on the member hosting CSEs. memberList 1(L) List of all member resourceIDs in the multicast group. Each member resourceID corresponds to a member resource. groupServiceServerAddress It is used only when the multicastType is 3GPP_MBMS_group, and it is the address of 3GPP group service server (e.g. SCEF);

UDP shall be terminated at the GCS AS and BM‑SC. 3GPP TS29.468 7 MB2‑U Protocol 7.1 Protocol Stack Figure 7.1-1: The user plane protocol stack without security protocols on the MB2-U reference point and in the EPC User plane data, for instance an IP layer and UDP layer. The user plane data are transparently transported between the GCS AS and the UE. The BM‑SC shall forward these protocol layers transparently. UDP shall be terminated at the GCS AS and BM‑SC. IP transported by lower layers L1 and L2. These layers shall be terminated at the GCS AS and BM‑SC. Figure 7.1‑1 depicts the MB2‑U protocol stack without security protocols. The stack shall include: 1)User plane data, for instance an IP layer and UDP layer. The user plane data are transparently transported between the GCS AS and the UE. The BM‑SC shall forward these protocol layers transparently. -2)UDP according to IETF RFC 768 [12]. UDP shall be terminated at the GCS AS and BM‑SC. -3)IP transported by lower layers L1 and L2. These layers shall be terminated at the GCS AS and BM‑SC.

User Data Plane Structure oneM2M Primitives oneM2M Primitives User Data Plane: Destination IP: multicastAddress COAP COAP UDP Multicast UDP IP Multicast IP T8 GMD GMD 3GPP TS36.300 LET-Uu EPC/eNB MB2-U UDP HTTP HTTP TCP TCP IP IP unicast unicast SCEF IN-CSE UE

Answer The multicastAddress is mandatory even when the multicastType is 3GPP_MBMS_group. Table 10.2.7.13-1: Multicast Group Information managed by group hosting CSE Information Multiplicity Description groupID 1 Indicates the <group> resource identifier which the Multicaste Group Information belongs to. multicastType Indicates the underlying networks multicast capability of the group members, the value shall be one of the following: 3GPP_MBMS_group, IP_mulicast_group. externalGroupID 0..1 If the multicastType is 3GPP_MBMS_group, the externalGroupID is the External-Group-ID as specified in 3GPP TS23.682[i.14] clause 4.6.3 multicastAddress The multicast address is allocated to the members in the memberList and shared by the members of this multicast group. The procedure of multicast address configuration is specified in RFC7390[xx] addressType It is used to describe the address type of the multicastAddress, e.g. IPv4 or IPv6. multicastGroupFanoutTarget Used as the target URI of the fan out request sending to the members. It is a virtual identifier allocated by the group hosting CSE corresponding to the access paths (i.e. Resource-IDs, which may be different) of the member resources on the member hosting CSEs. memberList 1(L) List of all member resourceIDs in the multicast group. Each member resourceID corresponds to a member resource. groupServiceServerAddress It is used only when the multicastType is 3GPP_MBMS_group, and it is the address of 3GPP group service server (e.g. SCEF);

Thanks for your listening! Q & A