Status on Rh interface between RACF and CPE/CPN CCSA CCSA 31 March to 2 April in 2008

Definition in RACF R2 Rh is the reference point between RACF and CPE/CPN. Should home gateway be the endpoint of Rh at the CPN side? Should it be a PD-PE or TRC-PE or TRE-PE or others within CPN? Is there a separated function entity in/out of CPN which works as the H-RAC-PE for CPN control? Scope of this contribution Page 2

The contribution from CT and Huawei Q4/13 believe that, the following decisions is for further discussion. have a specific RACF in home gateway providing a subset of RACF functions and supporting a subset of RACF reference points have the different instances of the same RACF in the Home Gateway, in the Access Network in the Core Network China Telcom and Huawei submitted a contribution ‘Proposed texts to Rh interface (C417 to Q4/13 and C101 to Q5/11 )’ This contribution make the proposal of four scenarios in CPN QoS control. Page 3

Scenario 1: Network side RAC-PE takes full charge of QoS control of CPN no policy based QoS control capability in CPN. RACF in the access network is in full charge of collecting information, monitoring resource status and installing transport polices to TRE-PE1 in CPN. It is appropriate for TRE-PE1 to be implemented in HGW. Rh in this scenario is similar to Rp in access network. Page 4

Scenario 2: H-TRC-PE controlled by PD-PE there is a separated transport resource control entity for CPN named H-TRC-PE Like TRC-PE0 in access network, parallel with TRC-PE0 and both are controlled by PD-PE. H-TRC-PE may reside in HGW or act as an independent physical entity. Rh in this scenario is similar to Rt in access network. Page 5

Scenario 3: H-TRC-PE controlled by TRC-PE0 separated transport resource control entity for CPN named H-TRC-PE. controlled by TRC-PE0 instead of PD-PE. H-TRC-PE may reside in HGW or act as an independent physical entity. Rh in this scenario is similar to Rp in access network. Page 6

Scenario 4: HGW implements parts of SCF function home gateway implements parts of SCF function, might be named as home RAC-PE (including H-TRC-PE and H-PD-PE), in full charge of CPN QoS control and does not need access RAC-PE home RAC-PE is a self-contained system within CPN. Rh is not necessary in this scenario. Page 7

Conclusion of the meeting The conclusion from Q4/13: the meeting agreed that the RACF R2 work, regarding the interaction between the CPN and RACF, address only the following two scenarios practical in the near term: The CPN implements a PE-FE to enforce policy under the control of a network PD-FE. In this case, the reference point is named Rh’, which is functionally similar to Rw. The CPN implements a PD-FE to coordinate with a network PD-FE. In this case, the reference point is named Rh, which is functionally similar to Ri. The conclusion from Q5/11 The meeting agreed the proposal and add the text proposed into Q.rcp8 as the starting point. Page 8

summary This contribution is just review the discussion in last Jan SG13 meeting in Seoul. The definition of Rh needs further study as the functions in CPE/CPN for resource control is not specific. There might have different views among SDOs such as SG13 , DSL Forum and HGI on QoS in CPE/CPN. Q4/13 and Q5/11 might have joint discussion on CPE/CPN resource control In May NGN-GSI meeting, further discussion on this topic is welcomed and contributions are invited. Page 9