3GPP和TISPAN固定接入IMS研讨会-研讨会摘要和下一步行动

30-31March2005Workshop"IMSoverFixedAccess"-Washington13GPP&TISPAN

Workshopon"IMSoverFixedAccess"

-WorkshopSummary

&Nextsteps-AlainLeRoux(FranceTelecom),TISPANChairmanalainxavier.leroux@MagnusOlsson(Ericsson),3GPPSA2Chairmanmagnus.m.olsson@NotesfromDavidBoswarthick(ETSI),TISPANsupport

david.boswarthick@AllWorkshopDocumentsandtdoclistareavailableat/ftp/workshop/2005-03-30_3GPP_TISPAN_Washington/Tdocs/30-31March2005Workshop"IMSoverFixedAccess"-Washington2AgendaDocuments&TimingApprovalofagendaandDocuments (s1)Workshopobjectives (s1)DocWS(05)01NGN(Release1)Architecturestatus (s1)DocWS(05)02(TISPAN),33(ITU-TFGNGN)IMSArchitectureandR6&R7status (s1)DocWS(05)03(3GPP)ReviewoftheNGN-IMSissues&status (s2)DocWS(05)04FixedAccesstoIMSissues/discussion (s2-s3-s4-s5)DocWS(05)05->16(TISPANinputs),34(FGNGNRacs)20(FMMS),21->26(Security6.3),28(Emtel6.10)30(Access-IMS,6.11),31(IMS-SigSimulationservices,6.11)Backboneissues/Intercoschemes (s6)DocWS(05)17,18SessionBorderControllersconcept (s6-s7)DocWS(05)29,OtherSBCrelatedTISPAN-inputsunderItem6.Currentactivitiesandworkplan (s8)DocWS(05)19(NGN-R1),22(IMSSecurity),32(IMS)Nextsteps/Futurecooperation (s7)DocWS(05)27,21(SA3-WG7),35(Endorsements)Anyotherissue&12.Wrap-up/Closure

DocWS(05)36(s8)30-31March2005Workshop"IMSoverFixedAccess"-Washington3AgendaItem6"IMSoFA"issues6.1Services&SupplementaryservicesdocTD-056.2Useridentificationissues(with6.1)6.3Security&Authentication(andLegalIntercept)docTD-10&26(reqts),23&25(isim),24,21&22(WG7-SA3)6.4SupportofIPv4/IPv6,NATTD-066.5SIP/SDPProfileforIMSoFATD-076.6"Gq"requirementsdocTD-08r1,346.7BearerQoSclasses&mappingdocTD-096.8Audio&VideoCodecsusedocTD-116.9IMSSpecsendorsementforNGNR1docTD-126.10EmergencycommunicationsdocTD-136.11OtherR1requirements/topicsdocTD-14,15r16.12BeyondR1requirementsdocTD-1630-31March2005Workshop"IMSoverFixedAccess"-Washington4OpeningandApprovalofAgendaOpeningofMeetingMrTimJeffriesofATISwelcomeddelegatestoWashingtononbehalfoftheHost.MrAlainleRouxandMrMagnusOlssonco-chairedthemeetingandexplainedtheorganizationforthetwodayworkshop.ApprovaloftheAgendaMrAlainleRouxintroducedtheagendaforthemeeting[TD-001r1_Agenda_objectives]TwonewdocumentsfromITU-TFGNGNwereaddedtotheagenda[TD-033toAgendaItem3andTD-034toItem6.6]TheAgendaoftheworkshopwasAGREED30-31March2005Workshop"IMSoverFixedAccess"-Washington5NGNRelease1StatusNGNRel-1ArchitectureandStatusPresentedin[TD-002_TISPAN_NGN_R1_Architecture]PresentstheTISPANWI02007(generalArchitecture).PresentsNGNarchitecture(incl.NASS,RACS,PES,IMS)Providesanarchitecturalcomparisonbetween3GPPR6andTISPANR1NGN.DescribesNGNimpactsonIMSDiscussionPSTNIDSNEmulation(providesPSTNservicestolegacyTerminalsviaagateway).Twosolutionspresentlyunderdevelopment(Monolithic,IMS-like).TISPANismainlyconcentratingontheinterfaces.UserAuthentificationdataaccessingaremotenetwork30-31March2005Workshop"IMSoverFixedAccess"-Washington6IMSR6andR7Status3GPPIMSStatusforRel6andRel-7Presentedin[TD-003_3GPP_IMS_R6_R7Status]AllmainWorkitemsforRel-6IMScompletedasofMarch2005.SomeMinorStage3definitionsstillopen(IMS-ALGprocedures,Mninterfaceprofile,PoCcharging,WLANaccess).Rel-7WorkItemFixedBroadbandAccesstoIMS,TR24.189isaplaceholderforIMSchanges(fromTISPANandotherSDOs)CRsthatarebeneficialfor3GPPIMScouldbedirectlyimplementedinTS24.229.ThosespecifictoTISPANwillbedocumentedintheTRfirst.Stage1requirementsexpectedfrozenSept2005.DiscussionTISPANR1willreference3GPPIMSRel-7specs.[seeTD-035]3GPPstructurehaschanged(/TB/home.htm)TISPANalsoneedtolookat“systemarchitectureevolution”workthatisunderwayin3GPP30-31March2005Workshop"IMSoverFixedAccess"-Washington7ITU-TNGNFocusGroupITU-TNGNFocusGroupActivitiesPresentedin[TD-033_FGNGN_Activity_status]PresentsgroupToRandworkingstructureListsNGNdeliverablesDescribesNGNdefinitionShowsNGNfunctionalarchitecturediagramListstheNGNServicesandcapabilitiesProvidesNGNscenariosandexamplesProvidestheNGNFGschedulefor2005PlantofinishRel-1andinitiateRel-2byDec2005.Discussion3GPPshouldbeinvolvedintheITU-Tdiscussionsontheterminologyformobility.Expectedtobehandledbyliaisons.30-31March2005Workshop"IMSoverFixedAccess"-Washington8NGN-IMSissuesStatusReviewoftheNGN-IMSissues(fromWorkshop22-23June2004)&theirstatusPresentedin[TD-004_IMS_NGN_WS1_issues]ListstheNGNrelatedissuesinTISPANaswellasdescribingtheirstatusDescribeswhereworkisbeinghandledwithinTISPANWGsandthepresentstatus30-31March2005Workshop"IMSoverFixedAccess"-Washington9NGNServices(6.1)ServiceRequirements-Release1Presentedin[TD-005_WG1_ServReqts]IncludesrequirementsfromEU(regulatoryservices)TISPANhaveproposedalistof(simulation)servicesto3GPP(SA)fortheirconsiderationTheseareTISPANRel-1Requirements.ThosethatcannotbeincludedinRel-1maymovetoRel-2.TISPANRel-1servicerequirementsexpectedtobefrozenatTISPAN6.DiscussionAssertedLocationInformationisrequiredasEUrecommendation.Issueofvoiceservicesin3GPPIMSRel-7hasyettobediscussedin3GPPTSGSAWG130-31March2005Workshop"IMSoverFixedAccess"-Washington10SupportofIPv4/v6&

NAT(6.4)[1of2]ExtendedP-CSCFfunctionalityPresentedin[TD-006_NAPT_Topology_Hiding]DescribesNAPT(-PT),TopologyHidingandHostedNATImpactson3GPPworkitemsandspecifications[TS23.228and23.229]DiscussionIETFarepresentlydiscussinggenericsolutionsforalltypesofNAT.DoubtsexpressedthatTISPANworkresolvesalloftheissues,andalsothatitmaybecompletedinaRel-1timescale.TISPANproposealighterfallbacksolutionforterminalsthatdonotsupporttheIETFsolution.HoweverthisstillneedstobefinallydecidedinTISPAN(forstage2and3).NATisnotcontrolledbyoperator.SignallingflowsrequiredbetweenP-CSCFandNATfunction.TISPANneedtore-examinehowtheywillsupportNATconsideringtheIETFdocumentation[draft-iab-nat-traversal].IssueofNATrelatedSecurityneedsfurtherconsiderationbyTISPAN(WG2andWG7)30-31March2005Workshop"IMSoverFixedAccess"-Washington11SupportofIPv4/v6&

NAT(6.4)[2of2]Discussion(cont)SDPoffermaycontainURLinformation.TheissueofMediastreamMSRPawarenessneedstobeexaminedinTISPAN.Topologyhidingwasexaminedin3GPPbutlateritwasdropped.TISPANshouldbecarefulnotre-usingthemechanismrejectedbyIETF.P-CSCFfunctionalimpactshavealreadybeenexaminedin3GPPandcausedsomeconcernswithIETF.NATmayresideeitherinCPEorinNetwork30-31March2005Workshop"IMSoverFixedAccess"-Washington12SIPProfileIssues(6.5)3GPPSIPProfileIssuesandImpactsPresentedin[TD-007_SIP_Profile.zip]TISPANendorsementof3GPPTS23.228,24.229,29.162AddanxDSLspecificannexto24.229SomeSIPconstraintswillberelaxedattheUE(optionalsupport)AdditionofnewSIPcapabilitiestosupportsupplementaryservicesDiscussionARFCexistsfordiscoveringSIPservers.TISPANmaywishtoconsiderthisasanalternativesolution.Changesto3GPPspecificationswillbediscussedandapprovedinTISPAN,andthenpresented(aspotentialCRs)to3GPPtobediscussedandincludedintheirdocumentation(R6orR7).Relaxingofrequirementsshouldbeconditionalonaccessnetwork(andnotoptional)P-Access-Network-InfoisnotrelevanttothefixedUE30-31March2005Workshop"IMSoverFixedAccess"-Washington13Security-Authentication

LegalIntercept(6.3)NGNSecurityRequirementsPresentedbyTISPANin[TD-010_Sec-Auth_LI]Requirementstoensureasecureandtrustworthyenvironmentforcustomers,networkoperatorsandserviceprovidersTISPANlookingatSecurityarchitecture,threatanalysisTISPANwillendorse3GPPsecuritydocumentationaswellasdevelopingNGNspecificdocumentsJointdiscussionsrequiredwith3GPPSA3Discussion3GPPhasdoneworkonearlyIMSsecurity.TISPANneedtoconsiderthisworkalthoughitdoesnotcoveralloftheNGNsecurityrequirements30-31March2005Workshop"IMSoverFixedAccess"-Washington14Security-Authentication

LegalIntercept(6.3)SecurityrequirementsforIMSoverFixedPresentedin[TD-026_security_requirements]fromAxalto/GemplusIdentifies3GPPworkingassumptionsandsecurityrequirements,andsuggeststheadoptionofabaselinefortheaccesssecuritysolutioninfixednetwork

ProposesadditionofadditionalsecurityrequirementsforIMSoverfixedDiscussionThisdocumentshouldbecontributedtoTISPANfordeliberationontherequirements30-31March2005Workshop"IMSoverFixedAccess"-Washington15UserIdentification(6.3)UserIdentificationwithnon-ISIMdevicesPresentedin[TD-023_user_identi_without_ISIM]PresentsproposalsonhowtouseISIMinnon-ISIMdevices(soft/hardISIM,lineidentifiers)ProposesasecureandfullystandardsolutionIncludeafixedUICCinRGWusingSIPB2BUADiscussionQuestiononhowtoprotecttheISIMinanon-ISIMdevice(authentication).HavetoensureuserhaspermissionsLineidentificationislimitedwhenwirelesstechnologiesareused(WLAN/Bluetooth)30-31March2005Workshop"IMSoverFixedAccess"-Washington16IMSsecurity(6.3)UsageofISIMinIMSnetworksPresentedin[TD-025_ISIM_in_IMS]3GPPIMSandIMSoverfixedaccessshouldusesamesecuritymechanismsProposesaremovabletamperresistantdevicetosecureIMServicesforfixedaccessRecommendstheadoptionofUICC-basedISIMTISPANdeliberationrequired(currentlynotmandated)IMSsignallingprotectionwithTLSPresentedin[TD-024_IMS_security]ProposesusingTLSasopposedtothepresentIMSsecuritySupportedingeneralbutthisneedstobeexaminedin3GPPinordertomakeitgenericandnotTISPANspecific.30-31March2005Workshop"IMSoverFixedAccess"-Washington17TISPAN/SA3interwork(6.3)TISPANand3GPPSA3InterworkingPresentedin[TD-021r1_Interworking_TISPAN_and_3GPP_Security]SuggestsaworksplitforTISPANand3GPPSA3forsecurityworkDiscussionsWillbediscussedinTISPANWG7(April2005)Resultswillbecommunicatedto3GPPSA3(inaLS)30-31March2005Workshop"IMSoverFixedAccess"-Washington18IMSsecurityextensions(6.3)IMSsecurityextensionsWIfor3GPPR7Presentedin[TD-022_IMS_security_extensions]TISPANWG7Interimmeeting(Oslo)shouldsendaLStoSAWG3AskSAWG3tostartworkon”IMSsecurityextensions”SendasummaryofNGN/IMSR1workingassumptionsandrequirements(coveringrequirementsfromallTISPANWGs,e.g.WG1andWG2)DiscussionsProposestokeepthemaintenanceofIMScoresecurityspecificationsin3GPP30-31March2005Workshop"IMSoverFixedAccess"-Washington19"Gq'"Requirements(6.6)TISPANNGNGq’requirementsPresentedin[TD-008r1_Gq_Interface_requirement]PresentstheNGNrequirementsonGqref.pointUsesinfo.exchangebetweentheApplicationFunction(AF)andPolicyDecisionFunction(SPDF)RACSarchitectureandrequirementsonGqshouldbefinalizedinApril(20-21/04inDarmstadt)DiscussionWhycombiningResource/QoScontrol(Gq)andNATcontrol(Gq')?ImpactsarelimitedtoGqinterfaceLIonGq'?Notexcluded.AFtodecideonpersessionormultiplesessionsflows30-31March2005Workshop"IMSoverFixedAccess"-Washington20ResourceandAdmissionControlNGNFGResourceandAdmissionControlPresentedin[TD-034_FGNGN_WG3_RACS]SimilartoTISPANbutwiderscopethanTISPANRelease1(e.g.includingcorenetworkcontrolandinter-domainPDF-PDFcommunication)Resourcemediationlayer(corenetworkselection)isstillunderdiscussioninITU-TNGNFG.DiscussionTISPANhavesomedivergencewithNGNFG(typicallyresourcemediation).WillhinderthesmoothevolutionforaconvergedarchitectureDoubtsontheneedforTopologycollection30-31March2005Workshop"IMSoverFixedAccess"-Washington21BearerQoSClasses(6.7)BearerQoSclassesandmappingPresentedin[TD-009_QoS_Mapping]QoSFrameworkandrequirementscontainedinETSIDTS/TISPAN-05008TISPANwillsubtractthe3GobjectivesfromtheY.1541objectivesDiscussion3GPPhavenotdocumentedtheamountofjitterandarenotpresentlystudyingthisissue3GPPhascurrentlynoworkitemonjittervaluesandapportionmentofQoSparameterstodifferentsegmentsNodirectimpactonTISPANR130-31March2005Workshop"IMSoverFixedAccess"-Washington22Codecsuse(6.8)CodecssupportbynetworksandNGNRel-1Presentedin[TD-011_Codecs_support]TISPANprinciplesforCodecsupportinWIDTS-05008ListsthecodecssupportedbythenetworkandUEDiscussionNoissuesraised30-31March2005Workshop"IMSoverFixedAccess"-Washington23IMSSpecsendorsement(6.9)Endorsementof3GPPIMSSpecificationsPresentedin[TD-012r1_IMS_endorsements]STF280isevaluatingIMSR6specificationsforendorsementWG3willendorsetheactualIMSdocumentsThecontributionliststheTISPANWIsandthe3GPPspecsthatareunderconsideration3GPPhaveaworkitemtosupportNGN“SystemenhancementsforfixedbroadbandaccesstoIMS”,Acronym“FBI”.DiscussionTISPANplanstoEndorse3GPPIMSspecificationswherepossibleandidentifyareasnotcovered.Similarexperiencein3GPPandIETFforSIP.Bettertomakechangesinthebasedocuments(IETF).3GPPpreferthatchangesaremadeinthecoreIMSspecifications3GPPhasconcernswiththeendorsement/replacementmechanism.(seerelateddocumentinTD-035)30-31March2005Workshop"IMSoverFixedAccess"-Washington24Emergencycommunications(6.10)StatusofEmergencyCommsworkPresentedin[TD-013_Emergency]Requirementsalmostfixed,alignedwith3GPPwherepossibleUseAccesslevelroutingorIMSlevelroutingLocationinformationmechanismsnotyetdecidedIETFdraft-ietf-sip-resource-priority-07stillneedstobeconsideredforpriorityhandlingDiscussionEnsureonecommonprocedureforIMSlevelrouting.Thisisbeingstudiedin3GPPTSGSAWG2(TR23.867).30-31March2005Workshop"IMSoverFixedAccess"-Washington25Emergencycommunications(6.10)Handlinglocationinformationforemergencyservices

Presentedin[TD-028_location_infor_for_emergency](Ericssonproposal)AnoptionwherebytheIMScorerequeststhelocationinformationfromtheNASSappearstohavetheadvantagesofnotrequiringthetrustoftheterminal,andnotrequiringtheuseofalocationcentreforemergencyservices.

DiscussionNoagreementtoremovetwootheroptionsContributionwillbeexaminedin3GPPSA2andCT130-31March2005Workshop"IMSoverFixedAccess"-Washington26ControlofProcessingoverloads(6.11)ControlofProcessingOverloadsPresentedin[TD-014_NGN_NOCA]TISPANR1willhavemechanismsthatautomaticallymaximiseeffectivethroughputatanyoverloadedressourceTISPANplanstodefinea(GOCAP)GenericOverloadControlApplicationProtocolOverloadcontrolarchitecture[WI02026]andprotocols[03034]DiscussionTISPANwillevaluateextensionstoexistingprotocolordefinitionofanewGOCAPprotocol30-31March2005Workshop"IMSoverFixedAccess"-Washington27FSMS/MMSHarmonization(6.11)HarmonizationofSMS/MMSoverIPPresentedin[TD-015r1_SMS_MMS_over_IP_Harmz]ETSITCATisdevelopingDES/AT-030036,“FixedNetworkShortMessageService(F-SMS)3GPPSA2isdeveloping3GPPTR23.804,“SupportofSMSandMMSovergeneric3GPPIPaccess;”Theyaresimilarbuthavedifferentarchitectures,needtobeharmonizedCooperationbetween3GPPSA2,ETSITISPANandETSIATisrequiredDiscussion3GPPworkisonlyaTRsonotfullyfinalised,stilltimetomakechangesin3GPPAgreementtodotheworkinoneplace30-31March2005Workshop"IMSoverFixedAccess"-Washington28FSMS/MMSHarmonization(6.11)ComparisonofthesolutionsforprovidingSMS/MMSoverIPPresentedin[TD-020_SMS_MMS_IP_Access_Solns]ContributioncomparesthetwosolutionsNokiabelievethe3GPParchitectureismorealignedwithexistingimplementationsanditshouldbethereferencearchitecture

DiscussionNoissuesraised30-31March2005Workshop"IMSoverFixedAccess"-Washington29OtherR1requirements(6.11)IMSSupportforSignallingofPSTNSupplementaryandSimulationServicesPresentedin[TD-031_IMS_SS_Signalling]SignallingofPSTNSSinformationneededbetweennetworkentitiesForPSTNbridgingscenariosTointerworkwithSubscriberSSControlproceduresLucentproposesadoptionofrequirementsforNetworkSSControlsignalling3GPPCTWGsexpectedtoperformdetailedworkunderWIDforFBI(fixedbroadbandIMS)WithinputfromSDOssuchasTISPANDiscussionSomeIMSnodesneednotinterpretISUPItwassuggestedthatinterworkingshouldbepossiblewithoutencapsulation

FurtherworkrequiredinTISPANbeforethisissueistakento3GPP.30-31March2005Workshop"IMSoverFixedAccess"-Washington30OtherR1requirements(6.11)IMSdependenciesonaccesstechnologyPresentedin[TD-030_IMS_access_tech]ProposesthatshouldbenorequirementintheIMSorassociatedUEforconfigurationtoaparticularaccesstechnology3GPPshouldinvestigatemechanismstoallowtheP-CSCFandtheUEtomakeconsistentdeterminationoftheaccesstechnologyNeedtodecidehowmuchmixturesoftechnologyinIP-CANshouldbetakenintoaccount

DiscussionNoissuesraised30-31March2005Workshop"IMSoverFixedAccess"-Washington31BeyondR1(6.12)GenericNGNIPAccessPresentedin[TD-016_Generic_IP_Access]PresentsapossiblearchitecturetoaccessNGNservicesbyusingtheso-calledGenericIPAccessPossiblenewareaofco-operationbetweenETSITISPANand3GPPDiscussionWorkneedstobecoordinatedbetweenTISPANand3GPP3GPPAAAservermayalsoberequired.Mobilityscenarios(fixed/mobile)needtobestudiedThisisbeyondthescopeof3GPPRel-6andTISPANR1EnhancedfunctionalityforQoScontrolisbeingstudiedin3GPPRel-7andincludesI-WLAN.[3GPPTR23.803]30-31March2005Workshop"IMSoverFixedAccess"-Washington32Backbone&IP-IPinterconnectionissues(7)NGNBackbonesandInterconnectionPresentedin[TD-017_Backbone_Interco]PresentstheoptionsfortheNGNbackbone(public/privateinternet/isolatedsubnets)Suggeststhecreationofaforumtodiscussthevariousoptionsfromanoperationalperspective.DiscussionGRXwasinitiallydesignedbyGSMAIREGforGPRSroamingfortheexclusiveuseofGSM/UMTSNeedtoclarifythefunctionsprovidedbytheGRXGSMAIREGisexaminingtheevolutionoftheGRXtoe.g.supportIMSinterconnectTISPANshouldworkwithGSMAIREGtoconsidertheevolutionoftheGRXtoincludefixedaccessandQoSconsiderationsContributionswelcomedinTISPANonidentifyingtherequirementsontheGRXItispossiblethatthereismorethanonesolution–theuseofco-existingoptionalsolutionscouldbeonemethod30-31March2005Workshop"IMSoverFixedAccess"-Washington33Backbone&IP-IPinterconnectionissues(7)IP-IPinterconnectionPresentedin[TD-018_IP_IP_interconnection]DescribesthestatusofIPtoIPinterconnectinTISPANDiscussionH248chosenforIainterface.NodecisionyetforGq’TheRACSissuewillbefurtherdiscussedinaTISPANrapporteursmeetingApril200530-31March2005Workshop"IMSoverFixedAccess"-Washington34SessionBorderControllersconcept(8)IssueswithSessionBorderControllers

Presentedin[TD-029r1_Session_Border_contribution]PresentsanumberofquestionsrelatedtoSBCstoensureinteroperabilityCommonFunctionalityisrequiredAgreementonRequirementsbyCarriersisEssential(Carriersneedtotakeinitiativequickly)SBCProposesaGlobalCarrierInitiativeto:DevelopRequirementsBeDeliveredtoStandardsDevelopmentDiscussionNeedtoinvolvethemobileoperators30-31March2005Workshop"IMSoverFixedAccess"-Washington35CurrentactivitiesandWorkplans(9)TISPAN_NGNProjectplanPresentedin[TD-019r1_TISPAN_NGN_Project_plan]PresentstheproposedTISPANWorkplanSimilarmechanismto3GPPworkplanningWillbeupdatedandadoptedatTISPAN6DiscussionsCaninclude3GPPandTISPANin.zipfilesothattheycanbecomparedStage1,Stage2,andStage3completiondatesneedtobestudiedfurther.Theyshouldnotfinishatthesametime(althoughTISPANaredoingsomereverseengineering.30-31March2005Workshop"IMSoverFixedAccess"-Washington36NextstepsandWorkingarrangements(10)SpecificationoftheIMSCore(includingTISPANenhancements)Presentedin[TD-035_Specification_of_the_IMS_Core]3GPPasksTISPANtorecommittoasinglesetofIMScorespecs.IndicationfromTISPANonhow“standardized”thesespecificationsmustbe:(availableon3GPPwebsite,TS,ES,EN):TISPANtoprovide3GPPwithalistofspecstheyneedtoreferto.UnderstandingoftheTISPANRel-1timelines/prioritiesDiscussionsTISPANREL-1isbasedupon(refersto)3GPPIMSRel-7specsResultsinsinglesetofIMSspecsforcompaniestoimplementThisprocessisalreadyandsuccessfullyusedinthejointworkinggroupwithTISPANOSAand3GPP(WGCT5)TISPANmaybringDRAFTCRsto3GPPastheywillberefinedIdeallyTISPANwishtohave3GPPIMSspecificationsbySept-05TISPANwillprovide3GPPwithalist