TDoc | Title | Source |
---|---|---|
S6-250001 | SA6 Meeting #65 - Initial agenda | SA6 Chair |
S6-250002 | SA6 Meeting #65 - Agenda with Tdocs allocation after submission deadline | SA6 Chair |
S6-250003 | SA6 Meeting #65 - Agenda with Tdocs allocation at start of the meeting | SA6 Chair |
S6-250004 | SA6 Meeting #65 - Chair's notes at end of the meeting | SA6 Chair |
TDoc | Title | Source |
---|---|---|
S6-250005 | SA6 Chair Report from SA#106 | SA6 Chair |
S6-250007 | SA6 Meeting 64 Report | MCC |
TDoc | Title | Source |
---|---|---|
S6-250008 | LS reply on API availability support | SA5 [S5-246295] |
S6-250009 | LS on GSMA OPG PRDs publication and document restructuring | OPG [OPG_197_Doc 03] |
S6-250010 | LS on Questions on the Reserve_Network_Resource service operation | CT3 [C3-246507] |
S6-250011 | Reply LS on Usage of E2E Data Volume Transfer Time Analytics | SA2 [S2-2412872] |
S6-250012 | Reply LS on Coordination for Spatial Mapping Management Enabler | SA4 [S4-242173] |
S6-250013 | Reply LS on clarifications on consent management | SA [SP-241934] |
TDoc | Title | Source |
---|---|---|
S6-250069 | Dynamic Generation of AF-Specific UEID | AT&T Services, Inc. |
S6-250070 | LS on Dynamic Generation of AF specific UEID | AT&T Services, Inc. |
S6-250214 | LS reply on Questions on the Reserve_Network_Resource service operation | Ericsson |
S6-250286 | LS on Generation of AF specific UE ID | SA6 |
S6-250287 | LS reply on Questions on the Reserve_Network_Resource service operation | Ericsson |
S6-250330 | LS on User Authentication for IOPS | SA6 |
S6-250507 | Reply LS on LS on GSMA OPG PRDs publication and document restructuring | Huawei |
S6-250518 | LS on the questions on GSMA OPG PRDs publication | Huawei |
S6-250520 | LS reply on Questions on the Reserve_Network_Resource service operation | Ericsson |
S6-250562 | LS reply on Questions on the Reserve_Network_Resource service operation | SA6 |
S6-250563 | LS regarding questions from SEALPhase4 study | Huawei |
S6-250593 | LS regarding questions from SEALPhase4 study | Huawei |
S6-250597 | LS regarding questions from SEALPhase4 study | SA6 |
TDoc | Title | Source |
---|---|---|
S6-250197 | Handling of response to non-3GPP Security Message | Sepura Ltd |
S6-250198 | Handling of response to non-3GPP Security Message | Sepura Ltd |
S6-250199 | Handling of response to non-3GPP Security Message | Sepura Ltd |
S6-250200 | Handling of response to non-3GPP Security Message | Sepura Ltd |
S6-250201 | Handling of response to non-3GPP Security Message | Sepura Ltd |
S6-250311 | Handling of response to non-3GPP Security Message | Sepura Ltd |
S6-250312 | Handling of response to non-3GPP Security Message | Sepura Ltd |
S6-250313 | Handling of response to non-3GPP Security Message | Sepura Ltd |
S6-250314 | Handling of response to non-3GPP Security Message | Sepura Ltd |
S6-250315 | Handling of response to non-3GPP Security Message | Sepura Ltd |
TDoc | Title | Source |
---|---|---|
S6-250083 | Correction on service provisioning | Samsung |
S6-250084 | Correction on service provisioning | Samsung |
S6-250085 | Correction on service provisioning | Samsung |
S6-250362 | Correction on service provisioning | Samsung |
S6-250363 | Correction on service provisioning | Samsung |
S6-250364 | Correction on service provisioning | Samsung |
TDoc | Title | Source |
---|---|---|
S6-250023 | Removing Editors Notes from 23.180 - IOPS | FirstNet Authority |
S6-250111 | Resolve the EN in clause 10.13 | Huawei, Hisilicon |
S6-250112 | Resolve the EN in clause 10.13 | Huawei, Hisilicon |
S6-250113 | Resolve ENs in clause 10.14 | Huawei, Hisilicon |
S6-250114 | Resolve ENs in clause 10.14 | Huawei, Hisilicon |
S6-250119 | Resolve the EN in clause 7.5.2.23 | Huawei, Hisilicon |
S6-250120 | Resolve the EN in clause 7.5.2.23 | Huawei, Hisilicon |
S6-250121 | Resolve the EN in clause 7.5.2.24 | Huawei, Hisilicon |
S6-250122 | Resolve the EN in clause 7.5.2.24 | Huawei, Hisilicon |
S6-250123 | Resolve the EN in clause 7.5.3.4 | Huawei, Hisilicon |
S6-250124 | Resolve the EN in clause 7.5.3.4 | Huawei, Hisilicon |
S6-250125 | Resolve the EN in clause 7.5.3.7 | Huawei, Hisilicon |
S6-250126 | Resolve the EN in clause 7.5.3.7 | Huawei, Hisilicon |
S6-250127 | Resolve the EN in clause 10.16.2.1 | Huawei, Hisilicon |
S6-250128 | Resolve the EN in clause 10.16.1 | Huawei, Hisilicon |
S6-250129 | Resolve the EN in clause 10.8.3.2a.2 | Huawei, Hisilicon |
S6-250130 | Resolve the EN in clause 10.8.3.2a.2 | Huawei, Hisilicon |
S6-250202 | Correction in the Group regroup with preconfigured group procedure | Nokia |
S6-250203 | Correction in the User regroup with preconfigured group procedure | Nokia |
S6-250216 | Correction in MC service configuration on primary MC system | Nokia |
S6-250217 | Correction in MC service configuration on primary MC system | Nokia |
S6-250220 | Resolving Editor’s notes in clause describing MC service group affiliation and MC service group de-affiliation | Nokia |
S6-250221 | Resolving Editor’s notes in clause describing MC service group affiliation and MC service group de-affiliation | Nokia |
S6-250222 | Adding the Off-network functional model | Nokia |
S6-250223 | Adding the Off-network functional model | Nokia |
S6-250307 | Resolve the EN in clause 10.13 | Huawei, Hisilicon |
S6-250308 | Resolve the EN in clause 10.13 | Huawei, Hisilicon |
S6-250309 | Resolve ENs in clause 10.14 | Huawei, Hisilicon |
S6-250310 | Resolve ENs in clause 10.14 | Huawei, Hisilicon |
S6-250316 | Resolve the EN in clause 7.5.2.23 | Huawei, Hisilicon |
S6-250317 | Resolve the EN in clause 7.5.2.23 | Huawei, Hisilicon |
S6-250318 | Resolve the EN in clause 7.5.2.24 | Huawei, Hisilicon |
S6-250319 | Resolve the EN in clause 7.5.2.24 | Huawei, Hisilicon |
S6-250320 | Resolve the EN in clause 10.8.3.2a.2 | Huawei, Hisilicon |
S6-250321 | Resolve the EN in clause 10.8.3.2a.2 | Huawei, Hisilicon |
S6-250322 | Correction in MC service configuration on primary MC system | Nokia |
S6-250323 | Correction in MC service configuration on primary MC system | Nokia |
S6-250324 | Resolve the EN in clause 7.5.3.4 | Huawei, Hisilicon |
S6-250325 | Resolve the EN in clause 7.5.3.7 | Huawei, Hisilicon |
S6-250326 | Resolving an editor’s note in clause describing MC service group affiliation and MC service group de-affiliation | Nokia |
S6-250327 | Resolving an editor’s note in clause describing MC service group affiliation and MC service group de-affiliation | Nokia |
S6-250328 | Adding the Off-network functional model | Nokia |
S6-250329 | Adding the Off-network functional model | Nokia |
S6-250331 | Resolve the EN in clause 7.5.3.4 | Huawei, Hisilicon |
S6-250332 | Resolve the EN in clause 7.5.3.7 | Huawei, Hisilicon |
S6-250333 | Resolve the EN in clause 10.16.2.1 | Huawei, Hisilicon |
TDoc | Title | Source |
---|---|---|
S6-250056 | CAPIF supported features | Apple (UK) Limited |
S6-250057 | Correction to obtaining CAPIF credentials | Apple, Telefonica, Lenovo, NCSRD, UMA |
S6-250087 | Correction on ACR operation related to simultaneous connectivity | Samsung |
S6-250088 | Correction on ACR operation related to simultaneous connectivity | Samsung |
S6-250105 | Corrections to figure 6.3-1 | Huawei, Hisilicon |
S6-250174 | Resvole the EN about the security and privacy aspects for location management | CATT |
S6-250175 | Resvole the EN about the security and privacy aspects for location management | CATT |
S6-250189 | Correction to clause numbering | Ericsson, MCC |
S6-250365 | Correction to obtaining CAPIF credentials | Apple, Telefonica, Lenovo, NCSRD, UMA |
S6-250366 | Correction on ACR operation related to simultaneous connectivity | Samsung |
S6-250367 | Correction on ACR operation related to simultaneous connectivity | Samsung |
S6-250368 | Corrections to figure 6.3-1 | Huawei, Hisilicon |
S6-250369 | Resvole the EN about the security and privacy aspects for location management | CATT |
S6-250370 | Resvole the EN about the security and privacy aspects for location management | CATT |
S6-250371 | CAPIF supported features | Apple (UK) Limited |
S6-250521 | CAPIF supported features | Apple (UK) Limited |
TDoc | Title | Source |
---|---|---|
S6-250094 | 23700-23_TR clean up | China Mobile |
TDoc | Title | Source |
---|---|---|
S6-250067 | Enhanced Business Relationship for SEAL Service | ZTE Corporation |
S6-250068 | SEAL Service Usage Guidance | ZTE Corporation |
S6-250131 | Pseudo-CR on new solution to KI on NRM XR API | Huawei, Hisilicon |
S6-250139 | Pseudo-CR on Location Retrieval API enhancements | Samsung |
S6-250142 | Pseudo-CR on Location Verification API | Samsung |
S6-250163 | PCR on the solution for the Gap#4-3-2-1-Location (deployed by PLMN operators without NEF) | Huawei, Hisilicon |
S6-250164 | Solutionfor business relationship for SEAL service involving SEAL client | Huawei, Hisilicon |
S6-250165 | Gap of Incompleted Deployment of SEAL service without SEAL client | Huawei, Hisilicon |
S6-250166 | Solution for Deployment of SEAL service involving SEAL client | Huawei, Hisilicon |
S6-250167 | Terminology of API service and API protocol | Huawei, Hisilicon |
S6-250168 | Discussion on the principle of API services granularity | Huawei, Hisilicon |
S6-250169 | PCR on the API service granularity guidlines | Huawei, Hisilicon |
S6-250170 | Pseudo-CR on the gap of SEAL mapping with OpenGateway | Huawei, Hisilicon |
S6-250171 | PCR on updated Solution 5 for the content improvement | Huawei, Hisilicon |
S6-250172 | Updated solution 2 for the content improvement | Huawei, Hisilicon |
S6-250205 | Correction to SBA of 3GPP System Supporting SEAL Services | Ericsson |
S6-250235 | New gap on service based SEAL | Lenovo |
S6-250484 | Solutionfor business relationship for SEAL service involving SEAL client | Huawei, Hisilicon |
S6-250485 | SEAL Service Usage Guidance | ZTE Corporation |
S6-250486 | PCR on the API service granularity guidlines | Huawei, Hisilicon |
S6-250487 | Pseudo-CR on new solution to KI on NRM XR API | Huawei, Hisilicon |
S6-250488 | Pseudo-CR on Location Retrieval API enhancements | Samsung |
S6-250489 | Pseudo-CR on Location Verification API | Samsung |
S6-250490 | PCR on the solution for the Gap#4-3-2-1-Location (deployed by PLMN operators without NEF) | Huawei, Hisilicon |
S6-250491 | Gap of Incompleted Deployment of SEAL service without SEAL client | Huawei, Hisilicon |
S6-250492 | Solution for Deployment of SEAL service involving SEAL client | Huawei, Hisilicon |
S6-250493 | Terminology of API service and API protocol | Huawei, Hisilicon |
S6-250495 | Pseudo-CR on the gap of SEAL mapping with OpenGateway | Huawei, Hisilicon |
S6-250496 | PCR on updated Solution 5 for the content improvement | Huawei, Hisilicon |
S6-250508 | Updated solution 2 for the content improvement | Huawei, Hisilicon |
S6-250509 | Correction to SBA of 3GPP System Supporting SEAL Services | Ericsson |
S6-250510 | New gap on service based SEAL | Lenovo |
S6-250514 | Solution for Deployment of SEAL service involving SEAL client | Huawei, Hisilicon |
S6-250522 | Solutionfor business relationship for SEAL service involving SEAL client | Huawei, Hisilicon |
S6-250523 | PCR on the API service granularity guidlines | Huawei, Hisilicon |
S6-250524 | PCR on the solution for the Gap#4-3-2-1-Location (deployed by PLMN operators without NEF) | Huawei, Hisilicon |
S6-250525 | Gap of Incompleted Deployment of SEAL service without SEAL client | Huawei, Hisilicon |
S6-250526 | Solution for Deployment of SEAL service involving SEAL client | Huawei, Hisilicon |
S6-250546 | Pseudo-CR on the gap of SEAL mapping with OpenGateway | Huawei, Hisilicon |
S6-250564 | PCR on the API service granularity guidlines | Huawei, Hisilicon |
S6-250565 | Pseudo-CR on Location Verification API | Samsung |
S6-250566 | PCR on the solution for the Gap#4-3-2-1-Location (deployed by PLMN operators without NEF) | Huawei, Hisilicon |
S6-250567 | Solution for Deployment of SEAL service involving SEAL client | Huawei, Hisilicon |
S6-250592 | Pseudo-CR on new solution to KI on NRM XR API | Huawei, Hisilicon |
TDoc | Title | Source |
---|---|---|
S6-250015 | Remove MCData recording from Rel-19 | Airbus |
S6-250016 | Remove MCData recording from Rel-19 | Airbus |
S6-250017 | Corrections to IETF references | Airbus |
S6-250018 | Corrections to IETF references | Airbus |
S6-250052 | Floor remote request in emergency communication for private call | BDBOS |
S6-250082 | Alignment on 5G ProSe multi-hop UE-to-network relay support | Nokia |
S6-250116 | Resolve the EN in clause 5.3.5 | Huawei, Hisilicon |
S6-250117 | Some editorial changes to 23.289 | Huawei, Hisilicon |
S6-250118 | Editorial changes to TS23.281 | Huawei, Hisilicon |
S6-250134 | Adding a reference to TS 23.273 | Ericsson |
S6-250144 | Correcting figure 7.3.1.2-1 and the text order in clause 10.9.1 | Ericsson |
S6-250277 | Clarifications to the definitions | Airbus |
S6-250300 | Corrections to IETF references | Airbus |
S6-250301 | Floor remote request in emergency communication for private call | BDBOS, Nokia |
S6-250302 | Some editorial changes to 23.289 | Huawei, Hisilicon |
S6-250303 | Editorial changes to TS23.281 | Huawei, Hisilicon |
S6-250304 | Adding a reference to TS 23.273 | Ericsson |
S6-250305 | Correcting figure 7.3.1.2-1 and the text order in clause 10.9.1 | Ericsson |
S6-250306 | Clarifications to the definitions | Airbus |
S6-250334 | Remove MCData recording from Rel-19 | Airbus |
S6-250335 | Remove MCData recording from Rel-19 | Airbus |
TDoc | Title | Source |
---|---|---|
S6-250115 | Update the Annex A | Huawei, Hisilicon |
S6-250185 | MC gateway UE fixes | Samsung, Nokia, Huawei, Hisilicon |
S6-250336 | MC gateway UE fixes | Samsung, Nokia, Huawei, Hisilicon |
S6-250547 | MC gateway UE fixes | Samsung, Nokia, Huawei, Hisilicon |
TDoc | Title | Source |
---|---|---|
S6-250153 | Handling of Editors Notes in TS 23.434 | Samsung |
S6-250360 | Handling of Editors Notes in TS 23.434 | Samsung |
S6-250513 | Consolidation of Reserve Network Resource and Request Unicast Resource | Ericsson |
S6-250519 | Consolidation of Reserve Network Resource and Request Unicast Resource | Ericsson |
TDoc | Title | Source |
---|---|---|
S6-250152 | Remove EN in clause 8.1.4 | China Mobile |
S6-250154 | Remove EN in clause 8.7.5.2 and 8.8.4.2 | China Mobile |
S6-250156 | Remove EN in clause 11.2 | China Mobile |
TDoc | Title | Source |
---|---|---|
S6-250086 | Removing EN on EAS load information | Samsung |
S6-250147 | Update to discovery process | Samsung |
S6-250361 | Update to discovery process | Samsung |
S6-250577 | Removing EN on EAS load information | Samsung |
TDoc | Title | Source |
---|---|---|
S6-250106 | Informative wording corrections | Huawei, Hisilicon |
S6-250107 | Corrections to 3GPP spec reference | Huawei, Hisilicon |
S6-250108 | NOTE number correction | Huawei, Hisilicon |
S6-250109 | Add missing figures to clause 9.12.2.3 | Huawei, Hisilicon |
S6-250110 | Message name style alignment | Huawei, Hisilicon |
S6-250186 | Correction on mode of reporting | Ericsson |
S6-250187 | Corrections to non-3GPP access measurements | Ericsson |
S6-250442 | Corrections to 3GPP spec reference | Huawei, Hisilicon |
S6-250443 | NOTE number correction | Huawei, Hisilicon |
S6-250444 | Add missing figures to clause 9.12.2.3 | Huawei, Hisilicon, China mobile |
S6-250445 | Message name style alignment | Huawei, Hisilicon |
S6-250527 | Message name style alignment | Huawei, Hisilicon |
TDoc | Title | Source |
---|---|---|
S6-250030 | Delete term of AI/ML server | ZTE Corporation |
S6-250031 | Unified use of AIML enablement | ZTE Corporation |
S6-250053 | Resolving Editor's Notes in clause 8.8 and 8.13 | KPN N.V. |
S6-250054 | Aligning AIMLE client discovery with the AIMLE client registration IEs | KPN N.V. |
S6-250055 | AIMLE client selection subscription update and subscription cancel | KPN N.V. |
S6-250058 | Corrections related to ML model data types | Apple |
S6-250059 | Consistent VAL Service ID usage | Apple |
S6-250060 | Corrections to AIMLE client registration | Apple |
S6-250061 | Update to AIMLE client selection | Apple |
S6-250062 | Additional AIMLE identifiers | Apple |
S6-250092 | Remove the EN about the split operation node registration | China Mobile |
S6-250095 | Address the EN about the split AIML operation | China Mobile (Hangzhou) Inf. |
S6-250133 | EN resolutions in TS 23.482 | Lenovo |
S6-250188 | Definitions of terms and abbreviations | China Mobile |
S6-250190 | AIMLE Functional Description updata AIML service | China Mobile |
S6-250191 | S6-AIML_APP_AIMLE Functional Description update | China Mobile International Ltd |
S6-250192 | S6-AIML_APP_Definitions of terms and abbreviations | China Mobile International Ltd |
S6-250193 | Definitions of terms and abbreviations | China Mobile |
S6-250194 | S6-AIML_APP_AIMLE Functional Description update Edge AIMLE | China Mobile International Ltd |
S6-250195 | AIMLE Functional Description updata AIML service | China Mobile |
S6-250196 | AIMLE Functional Description updata | China Mobile |
S6-250225 | Updates to the Response of ML Model Information Storage and Discovery | Ericsson |
S6-250226 | Updates to ML Model Training Notification | Ericsson |
S6-250227 | Updates to AI/ML Task Transfer | Ericsson |
S6-250228 | Corrections to AIML Service Operations | Ericsson |
S6-250229 | Updates to FL Member Grouping | Ericsson |
S6-250230 | Adding AIMLE Client to FL Member Registration Procedure and Informaiton Flows | Ericsson |
S6-250231 | Adding Missing Service Operations to API Clauses | Ericsson |
S6-250232 | Add Functional Description for the Hierarchical Computing | Ericsson |
S6-250233 | Align Termination for ADAE Analyitcs ID | Ericsson |
S6-250234 | Corrections | Ericsson |
S6-250446 | Delete term of AI/ML server | ZTE Corporation |
S6-250447 | Unified use of AIML enablement | ZTE Corporation |
S6-250448 | Definitions of terms and abbreviations | China Mobile |
S6-250452 | Aligning AIMLE client discovery with the AIMLE client registration IEs | KPN N.V. |
S6-250453 | Corrections related to ML model data types | Apple |
S6-250454 | Consistent VAL Service ID usage | Apple |
S6-250455 | Corrections to AIMLE client registration | Apple |
S6-250456 | Update to AIMLE client selection | Apple |
S6-250457 | Updates to the Response of ML Model Information Storage and Discovery | Ericsson, Apple |
S6-250458 | Updates to ML Model Training Notification | Ericsson |
S6-250459 | Corrections to AIML Service Operations | Ericsson |
S6-250460 | Adding AIMLE Client to FL Member Registration Procedure and Informaiton Flows | Ericsson |
S6-250461 | Corrections to Procedures and Informaiton Flows | Ericsson |
S6-250462 | Add Functional Description for the Hierarchical Computing | Ericsson, China Mobile |
S6-250463 | EN resolutions in TS 23.482 | Lenovo |
S6-250464 | Resolving Editor's Notes in clause 8.8 and 8.13 | KPN N.V. |
S6-250465 | remove the EN about the split operation node registration | China Mobile |
S6-250466 | Address the EN about the split AIML operation | China Mobile (Hangzhou) Inf. |
S6-250467 | Updates to AI/ML Task Transfer | Ericsson |
S6-250468 | AIMLE client selection subscription update and subscription cancel | KPN N.V. |
S6-250469 | Updates to FL Member Grouping | Ericsson |
S6-250528 | Corrections to AIMLE client registration | Apple, KT Corp., KPN N.V. |
S6-250568 | Updates to FL Member Grouping | Ericsson |
S6-250581 | Address the EN about the split AIML operation | China Mobile (Hangzhou) Inf. |
TDoc | Title | Source |
---|---|---|
S6-250032 | Correction for clause 8.4 | ZTE Corporation |
S6-250033 | Spatial anchor retrieve operation | ZTE Corporation |
S6-250034 | Spatial anchor usage information report | ZTE Corporation |
S6-250035 | Spatial anchor usage information broadcast report | ZTE Corporation |
S6-250036 | Fix for clause 8.3.3 | ZTE Corporation |
S6-250037 | Architectural requirements | ZTE Corporation |
S6-250038 | Business relationships | ZTE Corporation |
S6-250039 | Deployment models | ZTE Corporation |
S6-250040 | Identities | ZTE Corporation |
S6-250155 | Metaverse_App_Remove EN on acess control rules | Samsung |
S6-250157 | Removing EN on additional events | Samsung |
S6-250159 | update on Architecture to support permission management | China Mobile Com. Corporation |
S6-250160 | procedures on usage of digital asset permission | China Mobile Com. Corporation |
S6-250173 | Removing EN on Get operation | Samsung |
S6-250182 | Support for metaverse services requiring multiple devices | Samsung |
S6-250183 | Update to create spatial map | Samsung |
S6-250184 | Update to requestory identity in information flows | Samsung |
S6-250238 | SMAS discovery procedure | InterDigital |
S6-250239 | Spatial anchor usage reporting | InterDigital |
S6-250243 | Spatial anchor usage editorial fixes | InterDigital |
S6-250257 | Proposal for clause 3 abbreviations | Nokia |
S6-250258 | Proposal for clause 4 overview | Nokia |
S6-250259 | Proposal for clause 5 architectural requirements | Nokia |
S6-250260 | Proposal for clause 8 digital asset media management | Nokia |
S6-250261 | Proposal for Annex deployment models | Nokia |
S6-250262 | Proposal for Annex business relationships | Nokia |
S6-250263 | Proposal for Editorial fixes | Nokia |
S6-250268 | Proposal for clause 3 abbreviations | Nokia |
S6-250269 | Proposal for clause 4 overview | Nokia |
S6-250270 | Proposal for clause 5 architectural requirements | Nokia |
S6-250271 | Proposal for clause 8 digital asset media management | Nokia |
S6-250272 | Proposal for Annex deployment models | Nokia |
S6-250273 | Proposal for Annex business relationships | Nokia |
S6-250274 | Proposal for Editorial fixes | Nokia |
S6-250279 | Corrections to the Spatial Anchor usage info procedure IE table | Ericsson |
S6-250280 | Enhancements to Spatial Map events | Ericsson |
S6-250281 | Enhancements to the SM create service | Ericsson |
S6-250285 | Enhancements to SM data source services | Ericsson |
S6-250401 | Removing EN on Get operation | Samsung, ZTE Corporation |
S6-250402 | Spatial anchor usage reporting | InterDigital, ZTE Corporation |
S6-250403 | Correction for clause 8.4 | ZTE Corporation, Ericsson, InterDigital |
S6-250404 | SMAS discovery procedure | InterDigital, Samsung |
S6-250405 | Enhancements to SM data source services | Ericsson |
S6-250406 | Update to create spatial map | Samsung |
S6-250407 | Enhancements to the SM create service | Ericsson |
S6-250408 | Enhancements to Spatial Map events | Ericsson |
S6-250409 | Metaverse_App_Remove EN on acess control rules | Samsung |
S6-250410 | Update to requestory identity in information flows | Samsung |
S6-250411 | Proposal for clause 4 overview | Nokia |
S6-250412 | Proposal for clause 5 architectural requirements | Nokia, ZTE Corporation |
S6-250413 | Proposal for Annex business relationships | Nokia, ZTE Corporation |
S6-250414 | Proposal for Annex deployment models | Nokia, ZTE Corporation |
S6-250415 | Identities | ZTE Corporation |
S6-250416 | Proposal for clause 8 digital asset media management | Nokia |
S6-250417 | update on Architecture to support permission management | China Mobile Com. Corporation |
S6-250418 | procedures on usage of digital asset permission | China Mobile Com. Corporation |
S6-250419 | Support for metaverse services requiring multiple devices | Samsung |
S6-250540 | Update to requestory identity in information flows | Samsung |
S6-250548 | Spatial anchor usage reporting | InterDigital, ZTE Corporation |
S6-250569 | Update to requestory identity in information flows | Samsung |
S6-250582 | Update to requestor identity in information flows | Samsung |
TDoc | Title | Source |
---|---|---|
S6-250071 | Pseudo-CR on added missing subsection in section 8 | Huawei, HiSilicon |
S6-250072 | Pseudo-CR on correct the section number in section 6 | Huawei, HiSilicon |
S6-250073 | Pseudo-CR on corrections on the DC application profiles downloading procedure | Huawei, HiSilicon |
S6-250074 | Pseudo-CR on delete unnecessary abbreviation | Huawei, HiSilicon |
S6-250075 | Pseudo-CR on identities | Huawei, HiSilicon |
S6-250076 | Pseudo-CR on overview | Huawei, HiSilicon |
S6-250077 | Pseudo-CR on remove the element of application type in the Get Root application request | Huawei, HiSilicon |
S6-250078 | Pseudo-CR on uniform the terminology of DC application profile | Huawei, HiSilicon |
S6-250079 | Pseudo-CR on uniform the terminology of MMTel Enabler Server and MMTel Enabler Client | Huawei, HiSilicon |
S6-250136 | Update of Functional entities | China Mobile M2M Company Ltd. |
S6-250137 | Solution of Call control conflict handling | China Mobile M2M Company Ltd. |
S6-250141 | pCR on clause 4 overview | China Mobile Com. Corporation |
S6-250143 | pCR on clause 5 Architectural requirements | China Mobile Com. Corporation |
S6-250145 | pCR on adding Application ID | China Mobile Com. Corporation |
S6-250146 | pCR on add missing sub-clauses in clause 8 | China Mobile Com. Corporation |
S6-250148 | pCR on update the architecture | China Mobile Com. Corporation |
S6-250149 | pCR on update of 8.4.2 third party call | China Mobile Com. Corporation |
S6-250150 | pCR on update the reference points | China Mobile Com. Corporation |
S6-250151 | pCR on clause 9 Deployment Guideline | China Mobile Com. Corporation |
S6-250240 | Pseudo-CR on information flows of the Application calling service API | Huawei, HiSilicon |
S6-250276 | MMTel App DCH alignment with SA2 A2P flow | Ericsson Canada Inc. |
S6-250278 | MMTel App DCH alignment with SA2 P2A flow | Ericsson Canada Inc. |
S6-250372 | pCR on update the architecture | China Mobile Com. Corporation |
S6-250373 | Update of Functional entities | China Mobile M2M Company Ltd. |
S6-250374 | Solution of Call control conflict handling | China Mobile M2M Company Ltd. |
S6-250375 | pCR on update of 8.4.2 third party call | China Mobile Com. Corporation |
S6-250376 | Pseudo-CR on information flows of the Application calling service API | Huawei, HiSilicon |
S6-250377 | MMTel App DCH alignment with SA2 A2P flow | Ericsson Canada Inc. |
S6-250378 | MMTel App DCH alignment with SA2 P2A flow | Ericsson Canada Inc. |
S6-250379 | Pseudo-CR on corrections on the DC application profiles downloading procedure | Huawei, HiSilicon |
S6-250380 | pCR on clause 4 overview | China Mobile Com. Corporation, Huawei, HiSilicon |
S6-250381 | pCR on clause 5 Architectural requirements | China Mobile Com. Corporation |
S6-250382 | pCR on adding Application ID | China Mobile Com. Corporation, Huawei, HiSilicon |
S6-250383 | pCR on add missing sub-clauses in clause 8 | China Mobile Com. Corporation, Huawei, HiSilicon |
S6-250384 | pCR on clause 9 Deployment Guideline | China Mobile Com. Corporation |
S6-250549 | MMTel App DCH alignment with SA2 A2P flow | Ericsson Canada Inc. |
S6-250550 | MMTel App DCH alignment with SA2 P2A flow | Ericsson Canada Inc. |
TDoc | Title | Source |
---|---|---|
S6-250176 | Resvole the EN for handling the “loss of connectivity” in LM server | CATT |
S6-250177 | Uniform the IE description for the velocity | CATT |
S6-250264 | Correction on reference UE usage | Nokia |
S6-250275 | Correction on reference UE usage | Nokia |
S6-250449 | Resolve the EN for handling the “loss of connectivity” in LM server | CATT |
S6-250450 | Uniform the IE description for the velocity | CATT |
S6-250451 | Correction on reference UE usage | Nokia |
TDoc | Title | Source |
---|---|---|
S6-250091 | Add service operation of Crossflow measurement and delay difference for XR application | China Mobile (Hangzhou) Inf. |
S6-250097 | Address the EN in UE-to-UE communication | China Mobile |
S6-250098 | Correction of 9.12.2.3 Tethering link measurement and provisioning | China Mobile |
S6-250099 | Remove the EN about multi-modal flow synchronization and crossflow measurement | China Mobile |
S6-250100 | Add update and delete service operation of SEALDD client policy configuration | China Mobile |
S6-250132 | Add service operation of Crossflow measurement and delay difference for XR application | China Mobile |
S6-250140 | Multi-Modal traffic indication in SEALDD layer | China Mobile M2M Company Ltd. |
S6-250213 | Solving Editor’s Notes on PDU set an RTT | Ericsson |
S6-250242 | Completion of SEALDD-enabled flow Alignment procedure | Ericsson |
S6-250435 | Address the EN in UE-to-UE communication | China Mobile |
S6-250436 | Correction of 9.12.2.3 Tethering link measurement and provisioning | China Mobile |
S6-250437 | Remove the EN about multi-modal flow synchronization and crossflow measurement | China Mobile |
S6-250438 | Add update and delete service operation of SEALDD client policy configuration | China Mobile |
S6-250439 | Add service operation of Crossflow measurement and delay difference for XR application | China Mobile |
S6-250440 | Multi-Modal traffic indication in SEALDD layer | China Mobile M2M Company Ltd. |
S6-250441 | Completion of SEALDD-enabled flow Alignment procedure | Ericsson |
S6-250541 | Address the EN in UE-to-UE communication | China Mobile |
S6-250551 | Completion of SEALDD-enabled flow Alignment procedure | Ericsson |
S6-250570 | Multi-Modal traffic indication in SEALDD layer | China Mobile M2M Company Ltd. |
TDoc | Title | Source |
---|---|---|
S6-250048 | Correction of the description of the procedures for UE requesting satellite coverage availability information in TS23.434 | NTT DOCOMO INC.. |
S6-250049 | Addition of response elements in the 5GSAT procedure in TS23.434 | NTT DOCOMO |
S6-250051 | Correction of the description of the procedures for UE requesting satellite coverage availability information in TS23.434 | NTT DOCOMO |
S6-250081 | Add the business relationship for SEAL deployment with satellite connectivity | NTT DOCOMO |
S6-250089 | Add the business relationship for EDGEAPP deployment with satellite connectivity | NTT DOCOMO |
S6-250090 | Add the specification for Satellite edge computing considering EAS onboard | NTT DOCOMO |
S6-250135 | Minor correction in clause 4.12.1 | Ericsson |
S6-250178 | Add the APIs for VAL server obtaning the SCAI | CATT |
S6-250237 | Solving ENs on Service provisioning considering EES onboard | Ericsson |
S6-250244 | UE unavailability information | Samsung |
S6-250245 | Client initiated data transmission | Samsung |
S6-250476 | Correction of the description of the procedures for UE requesting satellite coverage availability information in TS23.434 | NTT DOCOMO |
S6-250477 | Add the business relationship for SEAL deployment with satellite connectivity | NTT DOCOMO |
S6-250478 | Add the business relationship for EDGEAPP deployment with satellite connectivity | NTT DOCOMO |
S6-250479 | Add the APIs for VAL server obtaning the SCAI | CATT |
S6-250480 | Solving ENs on Service provisioning considering EES onboard | Ericsson |
S6-250481 | UE unavailability information | Samsung |
S6-250483 | Client initiated data transmission | Samsung |
S6-250542 | Add the business relationship for SEAL deployment with satellite connectivity | NTT DOCOMO |
S6-250543 | Add the business relationship for EDGEAPP deployment with satellite connectivity | NTT DOCOMO |
S6-250553 | UE unavailability information | Samsung |
S6-250571 | Solving ENs on Service provisioning considering EES onboard | Ericsson |
S6-250572 | Client initiated data transmission | Samsung |
S6-250587 | Solving ENs on Service provisioning considering EES onboard | Ericsson |
S6-250594 | Solving ENs on Service provisioning considering EES onboard | Ericsson |
TDoc | Title | Source |
---|---|---|
S6-250043 | Updates to RNAA deployments | NTT DOCOMO |
S6-250044 | Add the specification for Obtaining Resource Owner Consent | NTT DOCOMO |
S6-250045 | Add the specification for Resource Owner Consent Revocation | NTT DOCOMO |
S6-250046 | Add the specification for API instantiation based on service discovery | NTT DOCOMO |
S6-250047 | Addition of response elements in the CAPIF procedure in TS23.222 | NTT DOCOMO INC.. |
S6-250050 | Addition of response elements in the CAPIF procedure in TS23.222 | NTT DOCOMO |
S6-250063 | Authentication Between the Resource Owner Function and the CAPIF Core Function | ZTE Corporation |
S6-250064 | Procedure for Revoking Resource Owner Authorization | ZTE Corporation |
S6-250065 | Procedure for CCF Obtaining Resource Owner Authorization | ZTE Corporation |
S6-250066 | Resource Owner authorization Management for Nested API Invocation | ZTE Corporation |
S6-250096 | Address the EN about the reference of charging TS | China Mobile |
S6-250103 | DISC on AEF or API instantiation | Huawei, Hisilicon |
S6-250104 | Dynamic AEF instantiation | Huawei, Hisilicon |
S6-250206 | Solving ENs on CAPIF interconnection | Ericsson |
S6-250207 | UE accessing resources not owned by that UE | Ericsson |
S6-250208 | Clarification of API invoker authorization and RO authorization functions | Ericsson |
S6-250209 | Correction to Procedure for API invoker obtaining authorization from resource owner | Ericsson |
S6-250210 | Corrections to UE-access of other UEs’ resources of a group | Ericsson |
S6-250211 | Service API category as discovery policy information | Ericsson |
S6-250212 | Solving ENs on finer granularity of access control for service API | Ericsson |
S6-250215 | Correction on Revocation on CAPIF interconnection | Ericsson |
S6-250241 | CAPIF_Clarification_of_ROF_and_Authorization_function | Ericsson Canada Inc. |
S6-250246 | Clarification on resource owner consent upon service API invocation | Samsung |
S6-250247 | Group user consent | Samsung |
S6-250248 | Discover service APIs without onboarding | Samsung, Ericsson |
S6-250253 | Clarification of the ROF and Authorization Function responsibilities | Ericsson Canada Inc. |
S6-250256 | Proposal for AEF instantiation support in CAPIF | Nokia |
S6-250265 | Address EN in 8.33.2 on security specs in 33.122 | Ericsson Canada Inc. |
S6-250267 | Proposal for AEF instantiation support in CAPIF | Nokia |
S6-250282 | On mapping of active-inactive API states to SA5 solutions and aligning Service API Information descriptions | Ericsson |
S6-250283 | Discussion on answers from SA5 in LS (S6-245008) on LS reply to SA6 LS on API availability support | Ericsson Canada Inc. |
S6-250284 | Group Information Provisioning in CAPIF to support RNAA | Nokia |
S6-250421 | Updates to RNAA deployments | NTT DOCOMO, Nokia |
S6-250422 | Procedure for CCF Obtaining Resource Owner Authorization | ZTE Corporation, NTT DOCOMO |
S6-250423 | Procedure for Revoking Resource Owner Authorization | ZTE Corporation |
S6-250424 | Proposal for AEF instantiation support in CAPIF | Nokia, Huawei, Hisilicon, NTT DOCOMO |
S6-250425 | Addition of response elements in the CAPIF procedure in TS23.222 | NTT DOCOMO |
S6-250426 | Authentication Between the Resource Owner Function and the CAPIF Core Function | ZTE Corporation |
S6-250427 | Address the EN about the reference of charging TS | China Mobile |
S6-250428 | Solving ENs on CAPIF interconnection | Ericsson |
S6-250429 | UE accessing resources not owned by that UE | Ericsson |
S6-250430 | Correction to Procedure for API invoker obtaining authorization from resource owner | Ericsson |
S6-250431 | Corrections to UE-access of other UEs’ resources of a group | Ericsson |
S6-250432 | Service API category as discovery policy information | Ericsson |
S6-250433 | Correction on Revocation on CAPIF interconnection | Ericsson |
S6-250434 | CAPIF_Clarification_of_ROF_and_Authorization_function | Ericsson Canada Inc. |
S6-250470 | Clarification on resource owner consent upon service API invocation | Samsung |
S6-250471 | Group user consent | Samsung |
S6-250472 | Group Information Provisioning in CAPIF to support RNAA | Nokia |
S6-250473 | Discover service APIs without onboarding | Samsung, Ericsson |
S6-250474 | Clarification of the ROF and Authorization Function responsibilities | Ericsson Canada Inc. |
S6-250475 | On mapping of active-inactive API states to SA5 solutions and aligning Service API Information descriptions | Ericsson |
S6-250544 | Clarification of the ROF and Authorization Function responsibilities | Ericsson Canada Inc. |
S6-250545 | Clarification of the ROF and Authorization Function responsibilities | Ericsson Canada Inc. |
S6-250552 | Proposal for AEF instantiation support in CAPIF | Nokia, Huawei, Hisilicon, NTT DOCOMO |
S6-250554 | Clarification on resource owner consent upon service API invocation | Samsung |
S6-250555 | Discover service APIs without onboarding | Samsung, Ericsson |
S6-250573 | Procedure for CCF Obtaining Resource Owner Authorization | ZTE Corporation, NTT DOCOMO |
S6-250574 | Procedure for Revoking Resource Owner Authorization | ZTE Corporation, NTT DOCOMO |
S6-250575 | Clarification on resource owner consent upon service API invocation | Samsung |
S6-250576 | Group user consent | Samsung |
S6-250583 | Procedure for CCF Obtaining Resource Owner Authorization | ZTE Corporation, NTT DOCOMO |
S6-250584 | UE accessing resources not owned by that UE | Ericsson |
S6-250585 | Corrections to UE-access of other UEs’ resources of a group | Ericsson |
S6-250586 | Correction on Revocation on CAPIF interconnection | Ericsson |
S6-250589 | Corrections to UE-access of other UEs’ resources of a group | Ericsson |
S6-250590 | UE accessing resources not owned by that UE | Ericsson |
S6-250595 | Group Information Provisioning in CAPIF to support RNAA | Nokia |
TDoc | Title | Source |
---|---|---|
S6-250014 | New WID on Enhanced Mission Critical Services Architecture Phase-2 | Motorola Solutions UK Ltd. |
S6-250020 | New study item proposals - Recording and Discreet Monitoring | Airbus |
S6-250021 | Study on logging and recording of mission critical services, Phase2 | Airbus |
S6-250022 | Study on discreet monitoring of mission critical services, Phase 2 | Airbus |
S6-250024 | New WID on Mission Critical Services for UE-to-UE and UE-to-network over multi-hop relay | FirstNet |
S6-250025 | Skeleton for FS_MCLOG_Ph2 | Airbus |
S6-250026 | Skeleton for FS_MCDISC_Ph2 | Airbus |
S6-250027 | FS_MCDISC_Ph2 References and Annex A | Airbus |
S6-250028 | FS_MCLOG_Ph2 References and Annex A | Airbus |
S6-250029 | Discussion on Remote Device Control | HOME OFFICE |
S6-250041 | Initial analysis of TR23784 for FS_MCLOG_Ph2 | Airbus |
S6-250042 | New WID - Mission Critical Solutions Enhancements Phase-2 | Motorola Solutions UK Ltd. |
S6-250080 | New WID on Railways specific Enhancements to Mission Critical Services Phase 6 | Nokia, UIC, Kontron Transportation France, Hytera, Airbus |
S6-250093 | New SID on Application enabler for XR_Services_Phase2 | China Mobile (Hangzhou) Inf. |
S6-250101 | New SID on application enabler layer service for energy efficiency | Huawei, Hisilicon |
S6-250102 | New SID on SEALDD phase 3 | Huawei, Hisilicon |
S6-250138 | New SID on Study on application enablement aspects for MMTel phase 2 | China Mobile Com. Corporation |
S6-250158 | New WID on application enablement for mobile metaverse services – Phase 2 | Samsung |
S6-250161 | Revised study on Service Enabler Architecture Layer (SEAL) | Huawei, Hisilicon |
S6-250162 | Work plan of SEAL Phase 4 | Huawei, Hisilicon |
S6-250179 | Discussion paper for SID proposal of Ambient IoT for SA6 R20 5GA | CATT |
S6-250180 | New SID on application enablement for Ambient IoT services | CATT |
S6-250181 | New SID on application enablement for satellite access enabled 5G services Phase 2 | CATT |
S6-250204 | New SID for Study on Application Enablement for Energy Efficiency and Energy Saving | Ericsson |
S6-250218 | New WID on Enhanced Mission Critical Services Architecture Phase-2 | Motorola Solutions UK Ltd. |
S6-250219 | New WID - Mission Critical Solutions Enhancements Phase-2 | Motorola Solutions UK Ltd. |
S6-250224 | New SID on application enablement for AI/ML service; Phase 2 | Lenovo |
S6-250236 | New SID on application enablement layer consolidation for IoT | InterDigital |
S6-250249 | 5GSAT_Ph4_App-Study-Discussion-Presentation | Samsung |
S6-250250 | New study item on 5GSAT_Ph4_App enhancements | Samsung |
S6-250251 | CAPIF_Ph4 Study-Discussion-Presentation | Samsung |
S6-250252 | CAPIF_Ph4 Study-FS_CAPIF_Ph4 | Samsung |
S6-250254 | Consolidated architecture for User Consent Management 4 applications | Ericsson Canada Inc. |
S6-250255 | New study item on CAPIF Phase 4 | Nokia |
S6-250266 | New study item on CAPIF Phase 4 | Nokia |
S6-250288 | Revised study on Service Enabler Architecture Layer (SEAL) | Huawei, Hisilicon |
S6-250289 | SA6 Rel-20 planning - Thoughts and ideas | SA6 Chair |
S6-250290 | Study on logging and recording of mission critical services, Phase2 | Airbus |
S6-250291 | Study on discreet monitoring of mission critical services, Phase 2 | Airbus |
S6-250292 | New WID on Mission Critical Services for UE-to-UE and UE-to-network over multi-hop relay | FirstNet |
S6-250293 | New WID on Railways specific Enhancements to Mission Critical Services Phase 6 | Nokia, UIC, Kontron Transportation France, Hytera, Airbus |
S6-250294 | New SID on SEALDD phase 3 | Huawei, Hisilicon |
S6-250295 | New WID on Enhanced Mission Critical Services Architecture Phase-2 | Motorola Solutions UK Ltd. |
S6-250296 | New SID on Application enabler for XR_Services_Phase2 | China Mobile (Hangzhou) Inf. |
S6-250297 | New SID on Study on application enablement aspects for MMTel phase 2 | China Mobile Com. Corporation |
S6-250298 | New WID on application enablement for mobile metaverse services – Phase 2 | Samsung |
S6-250299 | New SID on application enablement for Ambient IoT services | CATT |
S6-250400 | New SID on application enablement for AI/ML service; Phase 2 | Lenovo |
S6-250420 | New SID on application enablement layer consolidation for IoT | InterDigital |
S6-250482 | Discussion material for S6-250254 with context GSMA OPG and CAMARA | Ericsson |
S6-250494 | New SID on application enabler layer service for energy efficiency | Huawei, Hisilicon |
S6-250497 | New SID for Study on Application Enablement for Energy Efficiency and Energy Saving | Ericsson |
S6-250498 | New WID on Enhanced Mission Critical Services Architecture Phase-2 | Motorola Solutions UK Ltd. |
S6-250499 | Study on discreet monitoring of mission critical services, Phase 2 | Airbus |
S6-250500 | Study on logging and recording of mission critical services, Phase2 | Airbus |
S6-250501 | New WID on Mission Critical Services for UE-to-UE and UE-to-network over multi-hop relay | FirstNet |
S6-250502 | New WID on Railways specific Enhancements to Mission Critical Services Phase 6 | Nokia, UIC, Kontron Transportation France, Hytera, Airbus |
S6-250503 | New SID on Application enabler for XR_Services_Phase2 | China Mobile (Hangzhou) Inf. |
S6-250504 | New SID on Study on application enablement aspects for MMTel phase 2 | China Mobile Com. Corporation |
S6-250505 | New SID on application enablement layer consolidation for IoT | InterDigital |
S6-250506 | Consolidated architecture for User Consent Management 4 applications | Ericsson Canada Inc. |
S6-250515 | New SID on application enablement for AI/ML service; Phase 2 | Lenovo |
S6-250516 | New study item on 5GSAT_Ph4_App enhancements | Samsung |
S6-250517 | New study item on CAPIF Phase 4 | Nokia, Samsung |
S6-250529 | Revised study on Service Enabler Architecture Layer (SEAL) | Huawei, Hisilicon |
S6-250530 | New WID on Enhanced Mission Critical Services Architecture Phase-2 | Motorola Solutions UK Ltd. |
S6-250531 | New SID on Application enabler for XR_Services_Phase2 | China Mobile (Hangzhou) Inf. |
S6-250532 | New SID for Study on Application Enablement for Energy Efficiency and Energy Saving | Ericsson |
S6-250533 | New SID on SEALDD phase 3 | Huawei, Hisilicon |
S6-250534 | New WID on application enablement for mobile metaverse services – Phase 2 | Samsung |
S6-250535 | New SID on application enablement for AI/ML service; Phase 2 | Lenovo |
S6-250536 | New SID on application enablement layer consolidation for IoT | InterDigital |
S6-250537 | New study item on enhancements to application enablement for satellite access enabled 5G services | Samsung, CATT |
S6-250538 | New study item on CAPIF Phase 4 | Nokia, Samsung |
S6-250539 | Consolidated architecture for User Consent Management 4 applications | Ericsson Canada Inc. |
S6-250556 | New SID on SEALDD phase 3 | Huawei, Hisilicon |
S6-250557 | New SID on Study on application enablement aspects for MMTel phase 2 | China Mobile Com. Corporation |
S6-250558 | New WID on application enablement for mobile metaverse services – Phase 2 | Samsung |
S6-250559 | New SID on application enablement for AI/ML service; Phase 2 | Lenovo |
S6-250560 | New study item on enhancements to application enablement for satellite access enabled 5G services | Samsung, CATT |
S6-250561 | Consolidated architecture for User Consent Management 4 applications | Ericsson Canada Inc. |
S6-250578 | New SID on application enablement layer consolidation for IoT | InterDigital |
S6-250588 | New study item on CAPIF Phase 4 | Nokia, Samsung |
S6-250591 | Revised study on Service Enabler Architecture Layer (SEAL) | Huawei, Hisilicon |
S6-250596 | Revised study on Service Enabler Architecture Layer (SEAL) | Huawei, Hisilicon |
TDoc | Title | Source |
---|---|---|
S6-250006 | SA6 Meeting #65 – Work Plan Review | SA6 Chair |
S6-250019 | Status of Editor’s Notes in SA6 specifications | SA6 Chair |
S6-250511 | Presentation of TS 23.392 to SA for approval | China Mobile |
S6-250512 | Presentation of TS 23.438 to SA for approval | SA6 |
S6-250579 | SA6 Meeting #65 – Work Plan Review | SA6 Chair |
S6-250580 | Presentation of TS 23.392 to SA for approval | SA6 |
TDoc | Title | Source |
---|---|---|
S6-250337 | (reserved) | NaN |
S6-250338 | (reserved) | NaN |
S6-250339 | (reserved) | NaN |
S6-250340 | (reserved) | NaN |
S6-250341 | (reserved) | NaN |
S6-250342 | (reserved) | NaN |
S6-250343 | (reserved) | NaN |
S6-250344 | (reserved) | NaN |
S6-250345 | (reserved) | NaN |
S6-250346 | (reserved) | NaN |
S6-250347 | (reserved) | NaN |
S6-250348 | (reserved) | NaN |
S6-250349 | (reserved) | NaN |
S6-250350 | (reserved) | NaN |
S6-250351 | (reserved) | NaN |
S6-250352 | (reserved) | NaN |
S6-250353 | (reserved) | NaN |
S6-250354 | (reserved) | NaN |
S6-250355 | (reserved) | NaN |
S6-250356 | (reserved) | NaN |
S6-250357 | (reserved) | NaN |
S6-250358 | (reserved) | NaN |
S6-250359 | (reserved) | NaN |
S6-250385 | (reserved) | NaN |
S6-250386 | (reserved) | NaN |
S6-250387 | (reserved) | NaN |
S6-250388 | (reserved) | NaN |
S6-250389 | (reserved) | NaN |
S6-250390 | (reserved) | NaN |
S6-250391 | (reserved) | NaN |
S6-250392 | (reserved) | NaN |
S6-250393 | (reserved) | NaN |
S6-250394 | (reserved) | NaN |
S6-250395 | (reserved) | NaN |
S6-250396 | (reserved) | NaN |
S6-250397 | (reserved) | NaN |
S6-250398 | (reserved) | NaN |
S6-250399 | (reserved) | NaN |