3GPP TSG SA WG1 #

Size: px

Start display at page:

Download "3GPP TSG SA WG1 #"

亮濮阳
4 years ago
Views:

1 3GPP TSG SA WG1 #

2 3GPP TSG SA1#57 European Friends of 3GPP 2 parallel session 96 SA1 parallel session Proximity Service (ProSe) User Plane Congestion Management (UPCON) SA1 Proximity Service (ProSe) 12 (contribution) UE WLAN (RN) M2M service enablement 12 4 Intel WLAN 2 UPCON 14 (contribution) 6 1

3 Proximity-based service (ProSe) Machine Type Communication (MTC) User Plane Congestion Control (UPCON) Release 12 SA1 operator network ProSe UPCON 3GPP network ETSI TC M2M M2MSE 5/7-5/11 3GPP SA1 #58 LTE/LTE-A ProSe 5/7-5/11 3GPP SA1 #58 LTE/LTE-A MTC/M2MSE SA1 R12 UPCON 2

5 . 3GPP TSG-SA WG1 Meeting #58. 3GPP TSG-SA WG1 Meeting #58 (TR) Proximity Service ProSe UE WLAN (RN) M2M service enablement 12 2 UPCON ProSe Intel WLAN ProSe. 2012/5/7 ~ 2012/5/11. 4

6 . ( ) Q0 Q1 Q2 Q3 Q4 Q5 08:00 09:00 09:00 10:30 11:00 12:30 Lunch 14:00 15:30 16:00 18:00 18:00 19:30 3GPP TSG-SA WG1 Meeting #58 Seville, Spain, 7th 11th May 2012 Monday Tuesday Wednesday Thursday Friday 1. Opening 4. LS 10.2 MTC Rel-12 prio 5. New WI 5. New WI 3.11 ProSe non-3gpp access ProSe Comm Disc ProSe PS UPCON new UC UPCON considerations UPCON Defn Drafting: 9.6 ProSe (A) 9.7 UPCON (B) Drafting: 9.6 ProSe (A) 9.7 UPCON (B) 10.1 PWS 8.3 IPXSNAT ProSe Defn ProSe Gen 9.6 ProSe (remainder) Drafting: 9.6 ProSe (A) 9.7 UPCON (B) 1.3 SA1#57 Report 3.1 Report from SA 8.4 SSO_int 9.4 UMONC 9.8 RSE MMS (Room PRADO) Start 18:30 Drafting: 9.6 ProSe (A) 9.7 UPCON (B) Drafting: 9.6 ProSe (A) 9.8 UPCON (B) Drafting: 9.6 ProSe (A) 9.8 RSE (B) 3.11 ProSe non-3gpp access 7.1 SIMTC 9.2 FS_AMTC 9.3 FS_MTCe 5. New WI 5. New WI 4. LS 3.11 ProSe non-3gpp access Drafting: 9.6 ProSe (A) 9.7 UPCON (B) Drafting: ProSe/RSE 6. Rel TEI SMURFs 8.2 IMS_TELEP 8.3 IPXSNAT Revisions 4. LS 9.4 UMONC 7.1 SIMTC 9.2 FS_AMTC 9.3 FS_MTCe 10.1 PWS Revisions MSISDNless MO SMS 5. New WI 4. LS 8.1 SMURFs 6. Rel FS_AMTC 9.7 UPCON Revisions 9.7 UPCON 8.4 SSO_int 9.6 ProSe Revisions (GCSEL WID) 9.6 ProSe Revisions 10.1 PWS 9.6 ProSe 3.11 ProSe non-3gpp access 9.8 RSE Remaining Revisions Remaining Revisions 11.3 Others 11.1 Work plan 11.2 WI/SI status update (close by 16:30) 5

7 ( ) Potential Sub working groups Slots allocation based on contribution Rapporteur SIMTC FS_AMTC FS_MTCe FS_ProSe 7 FS_SSO_int SSO_int IMS_TELEP FS_UMONC SMURFs Toon Norp (KPN) Gary Jones (T-Mobile US) Laurence Meriau (Huawei) Hovey, Rich (Qualcomm)/ George Tsirtsis(Qualcomm) Christopher Wallace (IDCC) Bruno Tossou (Orange) Zong Zaifeng (ZTE) Mona Mustapha (Vodafone) FS_UPCON 6 John Visser (KDDI) FS_RSE 1 Joerg Swetina (NEC) IPXSNAT MMS Toon Norp (KPN) Joerg Swetina (NEC) VC Ilario Macchi (G&D) ProSe UPCON R12 SI ( ) (proximity-based) (APP) (discovery) 3GPP (public safety) 3GPP (traffic) (signaling) (proximity-based) (APP) 3GPP 56 ProSe (Study on Proximity-based Services) 6

8 ProSe ProSe ProSe (use case) Qualcomm ProSe Qualcomm George Tsirtsis ProSe (use case) (requirement) 3GPP : (1) (2) (user experience) (3) (4) (offload) (5) UE enb ( 1) 56 direct mode ( 2) 57 locally routed ( 3) UE 1 enb SGW/PGW UE 2 enb 1: Default data path setup in the EPS for communication between two UEs. 7

9 UE 1 enb SGW/PGW UE 2 enb 2: The direct mode data path in the EPS for communication between two UEs. UE 1 enb UE 2 SGW/PGW enb 3: The locally routed data path in the EPS for communication between two UEs. ProSe (ProSe Discovery) (Terminology) (Public Saftey) (Federal Communications Commission, FCC) LTE 8

10 (First responders) (FCC) 700 MHz (LTE) ProSe (requirement) (public safety) (commercial network) HPLMN ProSe ProSe ProSe ProSe (1) ProSe (ProSe-enabled) (2) ProSe (device discovery) (data exchange) ProSe ProSe UE (RN) UE S S S Apps (smart phone) Apps Apps App Apps 9

11 (timely discover) (exchange required information) (timely) (requirement) (server-based solutions) ProSe ProSe Telematics App (server-based location) (use case) S Service Continuity Use Case with Subscribers in Land Vehicles Moving at High Speed S ProSe (requirements) Service Continuity during switching from Infrastructure to/from direct path Requirements Note: ProSe specifications should take into account the relative speed of ProSe-enabled UEs. S Enhanced Open Discovery Use Case (open discovery) (use case) (requirements) (digital signage) (interactive discovery) (digital signage) ( LCD, LED, ) 10

12 (interactive advertisements) (business model) ProSe ProSe Relay ProSe E-UTRAN RN S UE S UE S S The Data Path is Locally Routed through the RN ProSe (Technical Report) (UE) ProSe enb 3GPP (UE) ProSe (UE) 3GPP RN E-UTRAN (UE) (data path) RN DeNB 3GPP 11

13 UE 1 RN UE 2 DeNB SGW/PGW RN 4: The locally routed data path for communication between two UEs. (UE) enb (data path) RN RN DeNB E-UTRAN DeNB DeNB 3GPP (EPC) (Intel ) WLAN S Establish data path between E-UTRA and non-e-utra interfaces for proximity service non E-UTRA (smartphones) IEEE IEEE NFC link (near field communication) non E-UTRA (direct mode communication) ProSe (data path) non E-UTRA ( IEEE IEEE NFC link) E-UTRA (control path) MAC/PHY (data 12

14 path) ( Bluetooth v3.0 + HS) Intel WLAN Intel WLAN S S S WLAN ProSe Intel S Use case: ProSe communication via WLAN ProSe (Objects) (subscribers) (discover) (communicate) 3GPP (RAT) ProSe WLAN 3GPP 3GPP WLAN I-WLAN WLAN 3GPP WLAN 3GPP 3GPP 3GPP (interference) WLAN (discovery) (communication) (network offloading) (use cases) FCC (Public Safety) LTE WLAN Use case: ProSe communication via WLAN 3GPP WLAN ProSe (use case) (requirements) S

15 (Description): ProSe (UE) WLAN (Pre-conditions): Bob John MNO Bob John WLAN (UE) ProSe (Discovery) (Communication) Bob ProSe John 3GPP (EPC) WLAN Bob John (Service Flow): Bob HD John 3GPP (EPC) WLAN Bob Bob John WLAN Bob WLAN HD John (Post-conditions): John Bob HD S Intel, III, Vodafone, T-Mobile, Telecom Italia, CMCC, Telefonica, KPN, Sprint, Bell Mobility, Cisco, Motorola Mobility, Interdigital, NEC, Radisys, ZTE, Juniper, Panasonic, Hitachi Ltd, ITRI, ETRI, TCS ProSe (TR) (requirements) 14

16 5.1.8 ProSe Communication via WLAN Requirements Subject to operator policy and user consent, a ProSe-enabled UE may be able to establish WLAN communication with another ProSe-enabled UE, based on ProSe Discovery and WLAN configuration information from the 3GPP EPC. M2M/MTC (Intel ) ProSe-Enabled MTC Intel S Use Case: Proximity Services Enabled MTC scenarios ProSe MTC MTC MTC 5 API Server 1 /User 1 D2D Communication between proximity enabled MTC devices Proximity enabled Device MTC Device (e.g. Sensors) Proximity enabled Device Proximity enabled Gateway Device Operator Domain (MTC) Server3 API API MTC Server2 /MTC User 2 (MTC) User 3 5: Deployment model for Proximity Services Enabled MTC Devices Intel S S Use Case: 15

17 Proximity Services Enabled MTC scenarios S (Description): ProSe MTC MTC MTC (use case) (requirements) (Pre-conditions): (smart parking meter) ProSe MTC A ProSe MTC (UE) A ProSe (Service Flow): A ProSe MTC (smart car) (Seattle) (parking spot) X ProSe MTC (Parking Meter) X A X X X A (parking fee information) A A (smart phone) (smart car) (Parking Meter) X ProSe MTC A (parking spot) 16

18 (Parking Meter) X A (parking fee) 17

19 (Post-conditions): (parking authority) A Intel S S ProSe (TR) (requirements) ProSe Services for large numbers of devices Potential Requirements: ProSe Discovery and Communication shall take into account the potentially large numbers of concurrently participating ProSe-enabled UEs (KPN ) M2M service enablement MTC ETSI TC M2M M2M 3GPP MTC MTC 3GPP M2M SA Plenary SA1 S Support for interworking with M2M service enablement S Work Item 14 Work Item (Justification) 18

20 Standardisation work related to MTC is on-going in other standardisation bodies (e.g. ETSI TC M2M) on M2M service enablement. The work on service enablement will require complementing work in 3GPP that affect existing MTC requirements in the 3GPP system and requirements on the interfaces between the 3GPP system and the M2M service enablement layer. (Objective) 1. 3GPP (service requirements) 3GPP ETSI TC M2M M2M service enablement (interworking) Clarify the relation/mapping between the MTC Server and ETSI TC M2M service capabilities Requirements for handling subscriber identities across service enablement layers and the 3GPP system Requirements of interworking and integration of accounting and charging information 2. 3GPP M2M service enablement AMTC S S KPN S TR (requirements) (potential requirements) The following are potential requirements identified in this Technical Report for which normative 19

21 requirements may be added to normative Technical Specifications. Vodafone S TR

22 9.1 MSISDN (E.164) with existing number length Dynamic pooling of existing MSISDNs may be used to address MTC devices. This overcomes issues arising from MSISDN scarcity. It also reduces the impact of mass MTC wake-up on the network, from a network protection perspective. Billing is not impacted as the legacy IMSI can be used to identify the device for charging purposes. The use of ITU-T E.164 International Network country calling codes (e.g. 882 and 883) with existing interpersonal MSISDN ranges can also be used to overcome MSISDN shortage for MTC device addressing. In some territories new regulation has been enforced which prohibits the use of MSISDNs from existing interpersonal number ranges for MTC services, (e.g. Netherlands). MTCe MTCe MTC S S S ITRI S Requirement for Synchronized communication scenario S Possible Requirement The system shall be able to provide MTC Device connection status information to the authorized MTC server Vodafone S Distinguishing devices behind a (MTC) Gateway (distinguishing) MTC MTC MTC (globally unique identity) 21

Scenario) MTC MTC MTC (identity) UPCON : SA1 R12 SI UPCON (User Plane Congestion

23 WLAN UE Operator network Gateway 6: Devices behind a MTC Gateway (Per-Device Usage Scenario) (mobile hot-spot service) WLAN 3GPP MiFi (subscriber) WLAN MTC (Customer Care Scenario) MTC MTC MTC (identity) UPCON : SA1 R12 SI UPCON (User Plane Congestion Management) (QoE, quality of experience) UPCON : (RAN, Radio Access Network) congestion (CN, Core Network) 22

24 user plan congestion control QoE UPCON TR RAN (congestion control) (the subscription of the user) (the type of application) (the type of content) ( ) UPCON TR (use cases) Basic Concepts User/subscriber-based Use Cases Application-based Use Case Non-real time Use Cases Other use cases ( ) UPCON S : Addition of User plane congestion due to 3GPP RAN to EPC interface capacity limitation KDDI, CHTTL (Mobile backhaul) (Use case) (Mobile backhaul) EPC A,B,C 23

25 S : UPCON Consideration on efficiency Ericsson `` RAN Ericsson WCDMA 90% 1.2 CDF duration 110% 100% 90% 80% 70% 60% 90% of congestion durations are less than 1.2 seconds 50% 40% 30% 20% 10% 0,0 0,2 0,4 0,6 0,8 1,0 1,2 1,4 1,6 0% 1,8 2,0 2,2 2,4 2,6 2,8 3,0 3,2 3,4 3,6 3,8 4,0 4,2 4,4 4,6 4,8 5,0 Congestion duration [s in 0.1 s intervals] 24

26 WCDMA 90% 720 bursty CDF separation 100% 90% 80% 70% 60% 50% 40% 90% of congestion separations are less than 780 seconds 30% 20% 10% 0% Separation between congestion periods [s in 1s intervals] 988 Ericsson bursty ( ) 25

27 Lag External Regulator(s) (e.g. in CN) Congestion No Congestion Congestion No Congestion Capacity Rate reduction Rate increase 100% Cell load Rate reducing action is too late Rate increase takes effect at high load (too late) Mean system throughput Negative impact on utilization Time S : Different charging policy based on RAN congestion status China Telecom CHTTL UPCON use case bursty RAN S : User Plane Congestion Management Definitions KDDI Hitachi CHTTL QoE (Quality of User Experience) UPCON QoS (Quality of Service) 3GPP QoS QoS QoE QoS QoE UPCON 26

KDDI RIM UPCON use case use case cell A 75Mbps cell RAN 100Mbps cell S1-121284:

28 Motorola QoE SA4 TR UPCON noted S : Clean-up of RAN User Plane capacity exhaust situations KDDI RIM UPCON use case use case cell A 75Mbps cell RAN 100Mbps cell S : Consideration on UPCON terminology for network and system Huawei China Unicom network system UPCON network system system UE? network third party 27

29 ? network system? TR system network TR system UE S : RAN congestion handling before congestion occurs Huawei Hisilicon UPCON (congestion) (congestion status) (load status) 28

30 . UPCON ProSe 8 UPCON 75% TR Use cases 2012/9 TR UPCON WI R12 PWS Security WID System Improvements for Group Communication over LTE R12 SI/WI PreSe : ProSe Use Cases 50% TR % (use cases) ProSe TR WLAN SA2 CT ProSe TR ProSe MTC : MTC TR (Study on Enhancements for MTC) TR % MTC use cases MTC ETSI TC M2M M2M 3GPP MTC MTC 3GPP M2M Support for interworking 29

31 with M2M service enablement SA Plenary SA1 S Work Item 14 MTC M2M UPCON : SA1 SI/WI MODAI UPCON 3GPP 911 public safety public safety SA1 PWS ProSe public safety 3GPP 30

32 . 1. : Meeting Date Place SA1#59 30 July 03 Aug 2012 Chicago, US SA1# Nov 2012 Edinburgh, UK SA1#61 28 Jan 1 Feb 2013 Prague, Czech Republic SA1# May 2013 India? SA1# Aug 2013 Zagreb, Croatia SA1# Nov 2013 North America? 2. UPCON ProSe R12 WI. (ftp://ftp.3gpp.org/tsg_sa/wg1_serv/tsgs1_58_seville/docs) 1. S , Discovery Use Case with Subscribers in Land Vehicles Moving at High Speed < Noted > 2. S , Open Discovery Use Case with Subscriber in Land Vehicle Moving at High Speed < Noted > 3. S , Addition of User plane congestion due to 3GPP RAN to EPC interface capacity limitation < Accepted > 4. S , Addressing the concerns on enabling ProSe via LTE+WLAN < Noted > 5. S , WID clarifications for WLAN usage as part of ProSe < Noted > 6. S , Enhanced Open Discovery Use Case < Noted > 7. S , WLAN offline discussion output < Noted > 8. S , Different charging policy based on RAN congestion status < Accepted > 9. S , Relay Communication Use Case < Noted > 10. S , Regulation and Assistance in the Open Discovery Use Case < Noted > 11. S , Modification on Service Continuity < Accepted > 12. S , Use case: ProSe communication via WLAN < Accepted > 13. S , Use Case: Proximity Services Enabled MTC scenarios < Accepted > 14. S , Support for interworking with M2M service enablement < Accepted > 31

出國報告電子檔規格

出國報告電子檔規格會議報告 ( 會議類別 : 其他 ) 3GPP RAN #69 Meeting 會議報告出席人員 : 陳瓊璋 / 陳弘仁派赴地區 : 美國 / 鳳凰城會議期間 :104 年 9 月 14 日至 9 月 18 日報告日期 :104 年 10 月 15 日 1 摘要本次 3GPP RAN #69 會議於 9 月在美國的