WiMAX Forum Requirements for WiMAX BS/WFAP Local Routing of the Bearer Traffic

WMF-T-0-v0 0 0 0 0 0 Copyright Notice, Use Restrictions, Disclaimer, and Limitation of Liability. Copyright 0. All rights reserved. The owns the copyright in this document and reserves all rights herein. This document is available for download from the and may be duplicated for internal use by the members, provided that all copies contain all proprietary notices and disclaimers included herein. Except for the foregoing, this document may not be duplicated, in whole or in part, or distributed without the express written authorization of the. Use of this document is subject to the disclaimers and limitations described below. Use of this document constitutes acceptance of the following terms and conditions: THIS DOCUMENT IS PROVIDED AS IS AND WITHOUT WARRANTY OF ANY KIND. TO THE GREATEST EXTENT PERMITTED BY LAW, THE WiMAX FORUM DISCLAIMS ALL EXPRESS, IMPLIED AND STATUTORY WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF TITLE, NONINFRINGEMENT, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE WiMAX FORUM DOES NOT WARRANT THAT THIS DOCUMENT IS COMPLETE OR WITHOUT ERROR AND DISCLAIMS ANY WARRANTIES TO THE CONTRARY. Any products or services provided using technology described in or implemented in connection with this document may be subject to various regulatory controls under the laws and regulations of various governments worldwide. The user is solely responsible for the compliance of its products and/or services with any such laws and regulations and for obtaining any and all required authorizations, permits, or licenses for its products and/or services as a result of such regulations within the applicable jurisdiction. NOTHING IN THIS DOCUMENT CREATES ANY WARRANTIES WHATSOEVER REGARDING THE APPLICABILITY OR NON-APPLICABILITY OF ANY SUCH LAWS OR REGULATIONS OR THE SUITABILITY OR NON-SUITABILITY OF ANY SUCH PRODUCT OR SERVICE FOR USE IN ANY JURISDICTION. NOTHING IN THIS DOCUMENT CREATES ANY WARRANTIES WHATSOEVER REGARDING THE SUITABILITY OR NON-SUITABILITY OF A PRODUCT OR A SERVICE FOR CERTIFICATION UNDER ANY CERTIFICATION PROGRAM OF THE WiMAX FORUM OR ANY THIRD PARTY. The has not investigated or made an independent determination regarding title or noninfringement of any technologies that may be incorporated, described or referenced in this document. Use of this document or implementation of any technologies described or referenced herein may therefore infringe undisclosed third-party patent rights or other intellectual property rights. The user is solely responsible for making all assessments relating to title and noninfringement of any technology, standard, or specification referenced in this document and for obtaining appropriate authorization to use such technologies, technologies, standards, and specifications, including through the payment of any required license fees. NOTHING IN THIS DOCUMENT CREATES ANY WARRANTIES OF TITLE OR NONINFRINGEMENT WITH RESPECT TO ANY TECHNOLOGIES, STANDARDS OR SPECIFICATIONS REFERENCED OR INCORPORATED INTO THIS DOCUMENT. IN NO EVENT SHALL THE WiMAX FORUM OR ANY LICENCEE BE LIABLE TO THE USER OR TO A THIRD PARTY FOR ANY CLAIM ARISING FROM OR RELATING TO THE USE OF THIS DOCUMENT, INCLUDING, WITHOUT LIMITATION, A CLAIM THAT SUCH USE INFRINGES A THIRD PARTY S INTELLECTUAL PROPERTY RIGHTS OR THAT IT FAILS TO COMPLY WITH APPLICABLE LAWS OR REGULATIONS. BY USE OF THIS DOCUMENT, THE USER WAIVES ANY SUCH CLAIM AGAINST THE WiMAX FORUM AND ITS LICENCEE RELATING TO THE USE OF THIS DOCUMENT. The reserves the right to modify or amend this document without notice and in its sole discretion. The user is solely responsible for determining whether this document has been superseded by a later version or a different document. WiMAX, Mobile WiMAX, Fixed WiMAX,, WiMAX Certified, Certified, the logo and the Certified logo are trademarks or registered trademarks of the. All other trademarks are the property of their respective owners. of

WMF-T-0-v0 0 0 0 Table of Contents INTRODUCTION (INFORMATIVE)... OBJECTIVE AND SCOPE... ABBREVIATIONS, DEFINITIONS, AND CONVENTIONS (INFORMATIVE). Conventions (Informative).... Abbreviations and Acronyms (Informative).... Definitions (Informative)..... Definitions Error! Bookmark not defined. REFERENCES... USE CASES (INFORMATIVE)... ERROR! BOOKMARK NOT DEFINED.. Use Case..... Short Description.. Actors.. Pre-conditions.. Post-conditions.. Normal Flow.. Alternative Flow 0 REQUIREMENTS (CONDITIONAL NORMATIVE).... Service Requirement... Error! Bookmark not defined... General Requirements Error! Bookmark not defined... Naming, identification and Addressing Requirements Error! Bookmark not defined.. Functional Requirements..... System Requirements.. Network Requirements.. Device Requirements Error! Bookmark not defined... Air Interface Requirements Error! Bookmark not defined.. Roaming Requirements.... Accounting and Management Requirements.... Security Requirements... of

WMF-T-0-v0. Regulatory Requirements... GUIDANCE AND RECOMMENDATION TO OTHER WIMAX WGS... ANNEX A DOCUMENT HISTORY (INFORMATIVE)... of

WMF-T-0-v0. Introduction (Informative) This document defines stage requirements for the BS/WFAP Local Routing of Bearer Traffic feature for broadband wireless networks based on Certified products. It describes usage scenarios and functional requirements for BS/WFAP Local Routing of Bearer Traffic. Architecture details shall be specified in stage- and stage- specifications based on the requirements outlined in this document. of

WMF-T-0-v0 0. Objective and Scope The objective of this specification is to identify use case scenarios and to define requirements to enable BS/WFAP Local Routing of Bearer Traffic. The scope of the specification is as follows: To identify use cases (e.g. consumers & enterprises) to support BS/WFAP Local Routing of Bearer Traffic To define Policy control for BS/WFAP Local Routing of Bearer Traffic To identify the support for service flow and QoS management for BS/WFAP Local Routing of Bearer Traffic To support backward compatibility to legacy network equipment To address provisioning/activation/deactivation/charging for BS/WFAP Local Routing of Bearer Traffic To address application mobility support of BS/WFAP Local Routing of Bearer Traffic. Note: The BS/WFAP Local Routing feature does not impact the current Mobility features as defined in [] nor introduce any architectural changes to the existing data path functional entities (e.g. lawful intercept, charging).. Abbreviations, Definitions, and Conventions (Informative) 0. Conventions (Informative) The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in Ref [] RFC.. Abbreviations and Acronyms (Informative) 0 0 ASN BB BS DP GW IP LI LR MS NAP NSP PCC QoS SF SS VoIP Access Service Network Business to Business Base Station Data Path Gateway Internet Protocol Lawful Intercept Local Routing Mobile Station Network Access Provider Network Service Provider Policy Control and Charging Quality of Service Service Flow Subscriber Station Voice Over IP of

WMF-T-0-v0 WFAP WiMAX Femto Access Point. Definitions (Informative).. BS/WFAP Local Routing Feature A feature which involves creating a data-path between two communicating User Devices whose DPs are going through the same BS/WFAP... BS/WFAP Local Routing Enforcement Point 0 0 0 BS/WFAP Local Routing Enforcement Point is a node (WFAP, BS, ASN-GW) which has Local Routing capability and is responsible for enforcing local routing of media data traffic... BS/WFAP Local Routing Policy BS/WFAP Local Routing Policy (e.g., PCC) is a set of rules that controls the Local Routing behavior. The rules reside with the NSP and are forwarded to the NAP for enforcement... BS/WFAP Local Routing Control Point BS/WFAP Local Routing Control Point is the entity where Local Routing Policy is available and which is responsible for controlling Local Routing behavior... BS/WFAP Local Routing Point BS/WFAP Local Routing Point consists of BS/WFAP Local Routing Control Point and/or BS/WFAP Local Routing Enforcement Point. The Local Routing Control Point and the Local Routing Enforcement Point may be the same.. References [] Requirements and Recommendations For Release. TM Air Interface [] Recommendation and Requirements for Networks based on Certified Products, DRAFT-T--R00v0-A_ASN-Local-Routing-Requirements.docx [] WMF-T-0-R0v0 WiMAX Roaming Exchange Dynamic Routing & Roaming Srvcs Requirements [] WMF-T-0-R0v0 Network Architecture detailed Protocols and Procedures Policy and Charging Control [] RFC Key words for use in RFCs to Indicate Requirement Levels [] Network Architecture Detailed Protocol and Procedures Base Specification, WMF-T-00-R0v0 of

WMF-T-0-v0. Use Cases (Informative). Use Case - Subscriber Device Synchronization.. Short Description Bob, a subscriber of MAX and FMAX (Femto service from MAX), uses various WiMAX embedded devices such as laptop PC, tablet and smartphone. Bob synchronizes data from his laptop PC to tablet and smartphone when all of his WiMAX enabled devices are being served by his WFAP. 0.. Actors Bob Subscriber of WiMAX operator MAX and WiMAX Femtocell service FMAX... Pre-conditions Laptop PC, tablet and smartphone have WiMAX modem embedded. All devices are located within range of FMAX WFAP. Each device has a certain shared folder which can be shared with various devices. Data files to be synchronized should be located in the shared folder... Post-conditions - After devices finish their data synchronizations, different billing schemes may be applied for the uploaded/downloaded data. of

WMF-T-0-v0.. Normal Flow - WiMAX subscriber Bob copies data files to the shared folder of his laptop which is connected to MAX (macro network) getting ready to share these data files with other user devices. - Bob activates his tablet and finds out from the screen that some data files are ready to be downloaded into the shared folder. - Bob executes the command to download data files into shared folder. - WiMAX network MAX checks user credentials. 0 0 - After user authentication is done, MAX checks if both sender and receiver are located within the same BS/WFAP. - Since the laptop is connected to MAX but located within the coverage of FMAX, MAX forces the laptop to handover to FMAX. - Once FMAX realizes that both sender and receiver are connected to the same WFAP, FMAX authorizes routing the data locally via WFAP. - Bob acknowledges that his devices are being synchronized within WFAP. 0- After download has been completed, Bob may be informed that a reduced rate has been applied for the locally routed data usage of

WMF-T-0-v0.. Alternative Flow - WiMAX subscriber Bob copies data files to the shared folder on his laptop getting ready to share these data files with other user devices. - Bob activates his tablet and finds out from the screen that some data files are ready to be downloaded into the shared folder. - Bob executes command to download data files into shared folder. - WiMAX network MAX checks user credentials. - After user authentication is done, MAX checks if both sender and receiver are located within the same BS/WFAP. 0 - When MAX acknowledges that both sender and receiver are located within the same BS, MAX authorizes the BS to route traffic between the sender and receiver locally. - Bob acknowledges that his devices are being synchronized within MAX BS. - After download has been completed, Bob may be informed that a reduced rate has been applied for the locally routed data usage.. Use Case - Private VoIP.. Short Description 0 Bob, a doctor at a university hospital is equipped with a WiMAX VoIP multimode smartphone which allows internal WiMAX VoIP calls within the hospital and external calls using other networks (e.g. CDMA, WCDMA). Bob uses this phone for calls within the hospital between doctors and nurses. Bob s hospital is a BB subscriber of WiMAX operator MAX which includes free VoIP calls within the hospital... Actors Bob, receptionist users of WiMAX VoIP service from WiMAX operator MAX. 0 of

WMF-T-0-v0.. Pre-conditions Bob and the receptionist s WiMAX smartphones support WVS (WiMAX VoIP Services). Smartphones located within the hospital can use VoIP services provided by MAX. All hospital employees are equipped with a WiMAX smartphone. The Hospital is covered by Pico-BS which covers only within Hospital property. Pico-BS also supports WVS... Post-conditions Private VoIP service is not available outside the hospital. For a VoIP call made to user not locally routable, a reduced rate cannot be applied. of

WMF-T-0-v0.. Normal Flow. WiMAX smartphone user Bob needs to check his appointment schedule and calls to the Hospital receptionist to find out the schedule.. Bob initiates a call to the receptionist who is also equipped with a WiMAX smartphone.. WiMAX network MAX checks user credentials.. After user authentication is done, MAX checks if both caller and receiver are located within the Hospital.. When MAX finds out that both caller and receiver are located within the hospital, MAX authorize the BS to route traffic between the sender and receiver locally. 0. Bob is aware that his VoIP call is free of charge (for locally routable calls within the Hospital).. Bob terminates the call after checking his appointment schedule... Alternative Flow - WiMAX smartphone user Bob needs to check his appointment schedule and calls to the Hospital receptionist to find out his schedule. - Bob initiates a call to the receptionist who is also equipped with a WiMAX smartphone. - WiMAX network MAX checks user credentials. 0 - After user authentication is done, MAX checks if both caller and receiver are located within the Hospital. - When MAX finds out that only the caller is located within the Hospital, MAX terminates the call and informs caller that this call cannot be locally routed via Pico-BS. of

WMF-T-0-v0 - Bob makes the call using other available networks (e.g. EVDO, WCDMA, WiMAX, etc.). Note; In this case, WiMAX coverage is provided by public macro Base Stations. of

WMF-T-0-v0. Requirements (Conditional Normative) The following sections describe a list of requirements to support the WiMAX BS/WFAP Local Routing feature. It should be noted that this feature is an optional one for the network, but if supported, these requirements define the expected behavior. Note that all subsections in this section are conditional normative unless stated otherwise. 0 Normative requirements of [] apply to WiMAX BS/WFAP Local Routing, except when explicitly stated otherwise in the requirements below. Requirements for WiMAX BS/WFAP Local Routing are intended to be part of WiMAX network releases beyond Release.0 and it should be compatible with WiMAX Network releases before the availability of the BS/WFAP Local Routing feature. BS/WFAP Local Routing SHALL NOT impact the air interface.. Functional Requirements.. System Requirements R -[0] WiMAX BS/WFAP Local Routing SHALL support IPv. R -[0] WiMAX BS/WFAP Local Routing SHALL support IPv. 0 R -[0] WiMAX Networks supporting BS/WFAP local routing SHALL NOT impact accounting record generation and their transport to the Home AAA even when the BS/WFAP is performing Local Routing. R -[0] WiMAX BS/WFAP Local Routing SHALL support simultaneous IPv and IPv flows if dual stack is supported by the WiMAX Network. R -[0] Accounting SHALL be backward compatible with previous releases without impacting accounting record generation and their transport to the Home AAA even when the BS/WFAP is performing Local Routing... Network Requirements R -[0] The WiMAX Network supporting BS/WFAP Local Routing SHALL support all applicable requirements of WiMAX Network Release.0 or later. of

WMF-T-0-v0. Policy Control Requirements R -[0] The BS/WFAP Local Routing Policy SHALL be under the home NSP control. R -[0] In case of roaming, the visited network SHALL be able to restrict BS/WFAP local routing (eg. when one of the parties of the connection is currently the Subject of LI) even if BS/WFAP local routing is allowed by the home network. R -[0] The WiMAX Network SHALL support BS/WFAP Local Routing Policy transfer from NSP to NAP. R -[0] The WiMAX Network SHALL support BS/WFAP Local Routing with per-service flow granularity. 0 R -[] The decision to enable BS/WFAP Local Routing on a particular service flow SHALL be based on operator policy (e.g., type of traffic, lawful intercept status) Note: An operator can enable or disable local routing for all the service flows in a network. R -[] The BS/WFAP Local Routing performed by the operator SHOULD follow the service flow based policy (e.g., PCC []). Service Flow and QoS Requirements R -[] The WiMAX Network SHOULD have the ability of reconfiguring a service flow to enable/disable BS/WFAP Local Routing after handover within the same ASN-GW. 0 Note: This handover requirement does not mandate providing session continuity at the network layer. Session continuity may be provided at the application layer.. Provisioning Activation Deactivation Requirements R -[] The WiMAX Network SHALL support BS/WFAP Local Routing Policy provisioning and updates. of

WMF-T-0-v0. Backward Compatibility Requirements R -[] The WiMAX Network supporting BS/WFAP Local Routing SHALL be backward compatible with a legacy WiMAX Network which does not support BS/WFAP Local Routing. R -[] A WiMAX BS/WFAP supporting local routing SHALL interwork with a legacy WiMAX System. R -[] WiMAX Systems supporting BS/WFAP local routing SHALL interwork with a legacy BS/WFAP.. Roaming Requirements 0 R -[] Handover SHALL be supported between a BS/WFAP that supports BS/WFAP Local Routing and a BS/WFAP that does not support BS/WFAP Local Routing. Note: The two BS/WFAPs should be within the same domain. R -[] The WiMAX Network SHALL comply with the requirements described in [] for a roaming subscriber when BS/WFAP Local Routing is invoked.. Accounting and Management Requirements 0 R -[0] The WiMAX Network SHALL identify the local routing sessions to enable different charging models. R -[] When BS/WFAP Local Routing accounting is enabled, the information (e.g., service application, usage) SHALL be made available to the core network. R -[] The WiMAX Network SHALL support various charging models, including pre-paid and postpaid, when BS/WFAP Local Routing is enabled.. Security Requirements R -[] The WiMAX BS/WFAP Local Routing feature SHALL NOT impact the security mechanisms defined in previous WiMAX Releases. 0 of

WMF-T-0-v0. Regulatory Requirements.. United States Country Lawful Intercept Requirements Lawful Interception is always done in accordance with the applicable national/regional laws and technical regulations. 0 The requirements in this section address BS/WFAP Local Routing of communications subject to Lawful Interception. The requirements in this section apply both to traffic that is routed to another user attached to the same WFAP or BS (i.e., traffic undergoing local routing) and to traffic that is diverted to another service provider, such as an internet service provider, at the WFAP or BS (i.e., traffic undergoing local breakout). These requirements are in addition to other Lawful Interception requirements that may exist for the particular service to which BS/WFAP Local Routing is applied (e.g., broadband access, VoIP). R -[] WiMAX BS/WFAP Local Routing implementation SHALL comply with the Lawful Intercept requirements of []. Editors note; reference is SPWG rel. requirements doc. R -[] The WiMAX network SHALL provide a capability to ensure that communications being intercepted prior to the invocation of BS/WFAP Local Routing continue to be intercepted by the WiMAX network after the invocation of BS/WFAP Local Routing. 0 R -[] The WiMAX network SHALL support a toggle to enable or disable the capability defined in R- [] for WFAP Local Routing on a per intercept order basis. This toggle shall be usable at both the time of delivery of the intercept order and at any subsequent time during the period the intercept order is active. Enabling or disabling the capability defined in R-[] (i.e., the setting of the toggle) is based on input from the Law Enforcement Agency at the time the intercept order is delivered to the WiMAX service provider or at a subsequent time during the period the intercept order is active. The default value of the toggle SHALL be to enable the capability defined in R- []. R [] After invocation of BS/WFAP Local Routing, the WiMAX network SHALL continue to report Communication Content (CmC) and Communication Identifying Information (CmII) if authorized by the intercept order. R [] After invocation of BS/WFAP Local Routing, the WiMAX network SHALL continue to report only CmII, if only CmII is authorized by the intercept order. 0 Note: national or regional laws and technical regulations, if they exist, will apply (e.g., In the Matter of Communications Assistance for Law Enforcement Act, Third Report and Order, CC Docket No. -, FCC Record ()). of

WMF-T-0-v0 R [] When intercept data (i.e., CmII only or CmII and CmC) is reported both before and after the invocation of BS/WFAP Local Routing, the WiMAX network SHALL correlate the intercept data reported before BS/WFAP Local Routing with the intercept data reported after BS/WFAP Local Routing invocation. R [0] For the traffic that is subject to Lawful intercept, the WiMAX network SHALL report the invocation of BS/WFAP Local Routing when the invocation BS/WFAP results in the WiMAX network no longer being able to report all CmII and CmC, or all CmII as per the lawful authorization. 0 Note: Invocation reporting SHALL include identification of the network containing the Local Routing Point. Note: If the invocation of BS/WFAP Local Routing is transparent to the Collection Function (i.e., the WiMAX network continues to report the same intercept data before and after BS/WFAP Local Routing invocation and there is no change in the Delivery Function reporting of the intercept data) then the WiMAX network is not required to report that invocation of BS/WFAP Local Routing. R [] Accessing and reporting information on the invocation of BS/WFAP Local Routing and the network containing the BS/WFAP Local Routing Point SHOULD be consistent with national/regional laws and technical regulations that may exist related to the completeness and unobtrusiveness of the intercept.. Guidance and Recommendation to other WiMAX WGs 0 The BS/WFAP Local Routing feature SHALL not have any impact or add any new requirement on the air interface. BS/WFAP Local Routing functionality SHALL not have any impact on the MS. of