<p> omniran-16-0060-01-CF00</p><p>1 Comment Resolution for Chapter of Authorization, QoS, and policy control Date: 2016-09-27 Authors: Name Affiliation Phone Email Hao Wang Fujitsu R&D Center +86-10-59691000 [email protected] Xiaojing Fan Fujitsu R&D Center +86-10-59691000 [email protected] Su Yi Fujitsu R&D Center +86-10-59691000 [email protected] Ryuichi Matsukura Fujitsu/Fujitsu Laboratory+81-44-754-2667 [email protected]</p><p>Notice: This document does not represent the agreed view of the OmniRAN TG It represents only the views of the participants listed in the ‘Authors:’ field above. It is offered as a basis for discussion. It is not binding on the contributor, who reserve the right to add, amend or withdraw material contained herein. Copyright policy: The contributor is familiar with the IEEE-SA Copyright Policy <http://standards.ieee.org/IPR/copyrightpolicy.html>. Patent policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: <http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and <http://standards.ieee.org/guides/opman/sect6.html#6.3>. 2 3</p><p>4 Abstract 5 This document provides the comment resolution for authorization, QoS and policy control in 6 Recommended Practice specification of IEEE 802.1CF D0.2 to address the technical comment of 7 #56 of omniRAN-16/0059 (CID number refers to the line number in the excel). 8 9 10 11 12 13 14</p><p>15 Comments on D0.2: 16</p><p> omniran-16-0060-01-CF00</p><p>CI Category Page Sub- Line# Comment Proposed Change Must Be D Cause Satisfied 56 More texts are Technic needed for the TBD al 70 7.6.7 1990 part in 7.6.7 17</p><p>18 Discussion: 19 For comment CID#56, revision for chapter 7.6.7 is proposed. 20 21 Proposed Text Changes: 22 23 Instruction to Editor: 24 Please replace the t.b.d of 7.6.7 of IEEE802.1CF D0.2 with the following text. 25 26 ------Begin Text Changes ------</p><p>40 7.1.1 Detailed procedures</p><p>41 7.1.1.1 Pre-provisioned service flow establishment 42 The user specific QoS policy is passed to ANC from SS during the authorization process, 43 together with the information about pre-provisioned service flows (SF), such as the number of 44 pre-provisioned service flows and the relative QoS parameters. After that, ANC assigns SFID to 45 each pre-provisioned service flow, and initiates the service flow establishment by sending data 46 path registration request to NA, as shown in Fig. 32. 47 Upon receiving the request, NA may reject or permit the establishment based on the admission 48 control policy towards the pre-provisioned service flows and its available resources. 49  If permitted, the service flow will be attached to a data path (DP), and NA will send SF 50 addition request to TE including the permitted QoS parameters. If these parameters are 51 accepted by TE according to its QoS capability, the pre-provisioned service flow is 52 established. NA then reserves the resource and notifies ANC with data path registration 53 response about the service flow establishment. The pre-provisioned service flow is activated 54 by data path registration ACK and SF addition ACK. 55  If rejected, NA responses to ANC with the preferred QoS parameters for negotiation. In this 56 case, ANC may adjust the QoS parameters for the pre-provisioned service flow and restart 57 the whole procedure. If it is rejected for certain times, ANC will declare failure of the pre- 58 provisioned service flow establishment to SS. 59 60 61 Fig.32 Pre-provisioned service flow establishment procedure</p><p>62 7.1.1.2 Service flow initialization by terminal 63 Terminal may initiate service flows with the preferred QoS parameters after authorization during 64 the user session by sending service flow addition request to NA. Upon receiving the request, NA </p><p> omniran-16-0060-01-CF00</p><p>65 should reply service flow addition received message to TE as an immediate acknowledgement 66 with the integrity verification, then decide to admit or reject the request based on the admission 67 control policy. 68 In case of admission, NA attaches the permitted service flow to a data path, and sends data path 69 registration request to ANC, including the QoS parameters of the service flow and data path ID. 70 If the request is accepted by ANC applying the user specific policy, it will assign SFID for the 71 service flow and notify NA with the data path registration response, so that NA will reserve 72 resources for the accepted service flows. NA sends service flow addition response to TE to notify 73 the service flow establishment. 74 TE should reply service flow addition ACK, and NA should send data path registration ACK to 75 confirm with ANC. 76 77 Fig. 33 Service flow initialization by terminal</p><p>78 7.1.1.3 Service flow initialization by access router 79 Access router may initiate service flows with the preferred QoS parameters after authorization by 80 sending service flow addition request to BH. Upon receiving the request, BH should reply 81 service flow addition received message to AR as an immediate acknowledgement with the 82 integrity verification, then decide to admit or reject the request based on the admission control 83 policy. 84 In case of admission, BH attaches the permitted service flow to a data path, and sends data path 85 registration request to ANC, including the permitted QoS parameters of the service flow and data 86 path ID. If the request is accepted by ANC applying the user specific QoS policy, it will assign 87 SFID for the service flow and notify BH with data path registration response, so that BH will 88 reserve resources for the accepted service flows. BH will send service flow addition response to 89 AR to notify the service flow establishment. 90 AR should reply service flow addition ACK, and BH should send data path registration ACK to 91 confirm with ANC. 92 93 Fig. 34 Service flow initialization by access router</p><p>94 7.1.1.4 Service flow modification by terminal 95 Terminal can modify the ongoing service flows by sending service flow change request to NA, 96 including the modified QoS parameter and the specified service flow. Upon receiving the 97 request, NA should reply service flow change received message to TE as an immediate 98 acknowledgement with the integrity verification, then decide to admit or reject the request based 99 on the admission control policy. 100 In case of admission, NA sends data path modification request to ANC, including the permitted 101 modification on the QoS parameter. If the request is accepted by ANC applying the user specific 102 QoS policy, it will send data path modification response to NA as a confirmation. And then, NA 103 should change the reserved resources for the service flows, and send service flow change 104 response to TE to notify the modification. 105 TE should reply service flow change ACK, and NA should send data path modification ACK to </p><p> omniran-16-0060-01-CF00</p><p>106 confirm with ANC. 107 108 Fig. 35 Service flow modification by terminal</p><p>109 7.1.1.5 Service flow termination by terminal 110 Terminal can terminate the ongoing service flows by sending service flow delete request to NA, 111 including information of the service flows to be terminated. Upon receiving the request, NA 112 should reply service flow delete response to TE indicating that the resource reserved for the 113 specified service flow has been found and the owner has been verified, and send data path de- 114 registration request to ANC including the relative information about service flow and data path. 115 ANC then removes the specified service flow, terminates the accounting, and replies data path 116 de-registration response to NA indicating that the service flow has been successfully removed. 117 NA will release the reserved resources, delete the service flows, and send data-path de- 118 registration ACK to ANC. 119 120 Fig. 36 Service flow termination by terminal</p><p>121 7.1.1.6 Change of authorization by subscription service 122 SS can change the QoS policies of specific user by sending the authorization change request to 123 ANC. Upon receiving the request, ANC should update the QoS policies specified to the users, 124 and initiate deletion and modification on the related service flows which may conflict with the 125 new QoS policies. 126</p><p>127 128 Fig. 37 Change of authorization by subscription service 129</p><p>130 ------End Text Changes ------131 132</p>