3GPP TDocs (written contributions) at meeting
Meeting: S6-47-e - 2022-02-14 to 2022-02-22, Online
meeting id: S6-47-e (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| S6‑220001 | SA6 Meeting 47-e Agenda | SA6 Chair | imported from 3GU |
| S6‑220002 | SA6 Meeting 46-e Report | MCC | imported from 3GU |
| S6‑220003 | SA6 Meeting #47-e - Agenda with Tdocs allocation after submission deadline | SA6 Chair | imported from 3GU |
| S6‑220004 | SA6 Meeting #47-e - Agenda with Tdocs allocation at start of the meeting | SA6 Chair | imported from 3GU |
| S6‑220005 | SA6 Meeting #47-e - Chairman's notes at end of the meeting | SA6 Chair | imported from 3GU |
| S6‑220006 | Liaison about Publication of Standard MEF 84 Network Slice Service and Attributes | MEF Forum | imported from 3GU |
| S6‑220007 | Further reply on MBS broadcast service continuity | RAN2 | imported from 3GU |
| S6‑220008 | Reply LS on Bearer pre-emption rate limit issue for GBR bearer establishment in MC systems | RAN3 | imported from 3GU |
| S6‑220009 | LS on reply to SA6 about new SID on Application Enablement for Data Integrity Verification Service in IOT | SA3 | imported from 3GU |
| S6‑220010 | Reply LS to CT3 Questions and Feedback on EVEX | SA4 | imported from 3GU |
| S6‑220011 | Reply LS on maximum number of MBS sessions that can be associated to a PDU session | SA2 | imported from 3GU |
| S6‑220012 | LS on follow-up on EAS definition | SA4 | imported from 3GU |
| S6‑220013 | Reply LS from GSMA Operator Platform Group to 3GPP SA, SA2, SA5, SA6 and ETSI ISG MEC on edge computing definition and integration | GSMA OPG (Operator Platform Group) | imported from 3GU |
| S6‑220014 | LS on Identification of ACRs | CT1 | imported from 3GU |
| S6‑220015 | Reply LS on Prioritized Vehicle to Cloud Technical Solutions (Automotive Edge Computing Consortium (AECC)) | SA5 | imported from 3GU |
| S6‑220016 | Reply LS on 3GPP SA1 clarifications on problematic UAV | SA1 | imported from 3GU |
| S6‑220017 | Reply LS from GSMA Operator Platform API Group to 3GPP SA, SA2, SA5, SA6 and ETSI ISG MEC on edge computing definition and integration. | GSMA Operator Platform API Group | imported from 3GU |
| S6‑220018 | LS on Energy Efficiency as guiding principle for new solutions | SA | imported from 3GU |
| S6‑220019 | Revised SID on Study on enhanced architecture for UAS Applications | InterDigital | imported from 3GU |
| S6‑220020 | Inclusion of specification-number of SA2-TR | InterDigital | imported from 3GU |
| S6‑220021 | Solution for KI#9 - Enhancement of dynamic EAS instantiation triggering | InterDigital | imported from 3GU |
| S6‑220022 | Correction of two information flow descriptions | BDBOS | imported from 3GU |
| S6‑220023 | Correction to On-demand usage of location information procedure | BDBOS | imported from 3GU |
| S6‑220024 | CR on Authorization of MCPTT user at LMS | BDBOS | imported from 3GU |
| S6‑220025 | CR on authorization of MCData user at LMS | BDBOS | imported from 3GU |
| S6‑220026 | CR on authorization of MCVideo user at LMS | BDBOS | imported from 3GU |
| S6‑220027 | Discussion paper on authorization of MC service user at LMS | BDBOS | imported from 3GU |
| S6‑220028 | Edge Notification Server | AT&T | imported from 3GU |
| S6‑220029 | Selected T-EAS declaration procedure corrections | VODAFONE Group Plc | imported from 3GU |
| S6‑220030 | Solution for KI#10 - V-ECS Discovery via the H-ECS | InterDigital | imported from 3GU |
| S6‑220031 | Alignment of section 4.7 of 23.289 with latest version of 23.247 (v 17.1.0) | AT&T | imported from 3GU |
| S6‑220032 | Key issue on support efficient content delivery | AsiaInfo Technologies Inc | imported from 3GU |
| S6‑220033 | FS_NSCALE architectural requirements | AsiaInfo Technologies Inc | imported from 3GU |
| S6‑220034 | FS_NSCALE solution evaluation for solution 4 | AsiaInfo Technologies Inc | imported from 3GU |
| S6‑220035 | FS_NSCALE Update the architecture for network slice capability enablement | AsiaInfo Technologies Inc | imported from 3GU |
| S6‑220036 | FS_NSCALE Solution to key issue #12 on the modification of NSCE server | AsiaInfo Technologies Inc | imported from 3GU |
| S6‑220037 | Solution to KI #6 on application layer dynamic slice SLA alignment capability | AsiaInfo Technologies Inc | imported from 3GU |
| S6‑220038 | FS_eEDGEAPP the procedure for solution #11 EASs to invoke MEC services API using CAPIF | AsiaInfo Technologies Inc | imported from 3GU |
| S6‑220039 | FS_eEDGEAPP architectural requirements | AsiaInfo Technologies Inc | imported from 3GU |
| S6‑220040 | New Solution for call transfer between MCPTT users in different MCPTT systems | Kontron Transportation France, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S6‑220041 | Correction of Enhanced Status description | Sepura Ltd | imported from 3GU |
| S6‑220042 | LS on clarifications to the Application Context Relocation (ACR) functionality | CT3 | imported from 3GU |
| S6‑220043 | LS on Enquires on Application Context Relocation (ACR) functionality | CT1, CT3 | imported from 3GU |
| S6‑220044 | LS on ECS provider identification in ECS address provisioning | CT1 | imported from 3GU |
| S6‑220045 | LS on MBS Service Area Identity and start procedure for broadcast service | RAN3 | imported from 3GU |
| S6‑220046 | Reply LS on energy efficiency as guiding principle for new solutions | SA5 | imported from 3GU |
| S6‑220047 | Reply LS on slicing management aspects in relation to SEAL | SA5 | imported from 3GU |
| S6‑220048 | Reply LS on network slice management service consumption | SA5 | imported from 3GU |
| S6‑220049 | TR skeleton for the study on Ad hoc group communications support for mission critical services | Samsung Electronics | imported from 3GU |
| S6‑220050 | Pseudo-CR on adding description to Introduction sections | Samsung Electronics | imported from 3GU |
| S6‑220051 | Pseudo-CR on adding description to Scope section | Samsung Electronics | imported from 3GU |
| S6‑220052 | Pseudo-CR on adding description to References and Definition sections | Samsung Electronics | imported from 3GU |
| S6‑220053 | Pseudo-CR on Key issue 1 for Ad hoc group communication | Samsung, FirstNet, AT&T, Nokia, Nokia Shanghai Bell, Kontron Transportation France, UIC | imported from 3GU |
| S6‑220054 | Pseudo-CR on Key issue 2 for Ad hoc group communication | Samsung, FirstNet, AT&T, Nokia, Nokia Shanghai Bell, Kontron Transportation France, UIC | imported from 3GU |
| S6‑220055 | Pseudo-CR on Key issue 3 for Ad hoc group communication | Samsung, FirstNet, AT&T, Nokia, Nokia Shanghai Bell, Kontron Transportation France, UIC | imported from 3GU |
| S6‑220056 | Pseudo-CR on Solution proposal for key issue 1 | Samsung, FirstNet, AT&T | imported from 3GU |
| S6‑220057 | MCPTT Group ID for pre-configured group call | AT&T GNS Belgium SPRL | imported from 3GU |
| S6‑220058 | Resolve the ENs in clause 7.8 | AT&T GNS Belgium SPRL | imported from 3GU |
| S6‑220059 | FFAPP Architecture | ZTE Corporation | imported from 3GU |
| S6‑220060 | FFAPP Deployment models | ZTE Corporation | imported from 3GU |
| S6‑220061 | FFAPP Involved entities and relationships | ZTE Corporation | imported from 3GU |
| S6‑220062 | Revised SID on Service Function Chaining support for Edge Data Networks | Intel Technology India Pvt Ltd | imported from 3GU |
| S6‑220063 | Control of allowing service continuity planning | Samsung | imported from 3GU |
| S6‑220064 | Update ECS configuration information to support roaming and federation | Samsung | imported from 3GU |
| S6‑220065 | Solution on enhancement of service continuity planning | Samsung | imported from 3GU |
| S6‑220066 | Editorial corrections around the MC gateway UE solution | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑220067 | Functional model reference points | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑220068 | Functional model media plane aspects | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑220069 | Using identities behind the MC gateway UE | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑220070 | MC gateway UE routing capabilties | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑220071 | Overall evaluation udate | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑220072 | Study Conclusions | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑220073 | Presentation TR 23.700-90 to TSG for Approval | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S6‑220074 | New WID on Interconnection and Migration Aspects for Railways | Nokia, Nokia Shanghai Bell, UIC, Kontron Transportation France | imported from 3GU |
| S6‑220075 | ECS provider ID correction | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S6‑220076 | Reply LS on ECS provider identification in ECS address provisioning | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S6‑220077 | Pseudo-CR on Reference to CAPIF Architecture | China Mobile Com. Corporation | imported from 3GU |
| S6‑220078 | Pseudo-CR on KI of Coordination Between Uu and PC5 | China Mobile Com. Corporation | imported from 3GU |
| S6‑220079 | Pseudo-CR on Preconditions of Solution 7 | China Mobile Com. Corporation | imported from 3GU |
| S6‑220080 | Pseudo-CR on Reference to CAPIF Architecture | China Mobile Com. Corporation | imported from 3GU |
| S6‑220081 | solution for KI 10 | China Mobile Com. Corporation | imported from 3GU |
| S6‑220082 | Proposed skeleton for TR 23.700-36 | Lenovo Future Communications | imported from 3GU |
| S6‑220083 | Scope for 3GPP TR 23.700-36 | Lenovo Future Communications | imported from 3GU |
| S6‑220084 | Introduction for 3GPP TR 23.700-36 | Lenovo Future Communications | imported from 3GU |
| S6‑220085 | Proposed skeleton for TR 23.700-38 | BDBOS | imported from 3GU |
| S6‑220086 | Proposed functional architecture for ADAES | Lenovo Future Communications | imported from 3GU |
| S6‑220087 | A UE capability to identify ECS address providers | vivo | imported from 3GU |
| S6‑220088 | Discussion paper: A UE capability to identify ECS address providers | vivo | imported from 3GU |
| S6‑220089 | LS Reply on ECS provider identification in ECS address provisioning | vivo | imported from 3GU |
| S6‑220090 | Study on Application layer support for Personal IoT Networks | vivo Mobile Communications Ltd, China Unicom, China Telecom, Spreadtrum | imported from 3GU |
| S6‑220091 | Proposed skeleton for 3GPP TR 23.700-78 | vivo | imported from 3GU |
| S6‑220092 | Introduction for 3GPP TR 23.700-78 | vivo | imported from 3GU |
| S6‑220093 | Scope for 3GPP TR 23.700-78 | vivo | imported from 3GU |
| S6‑220094 | New KI on PIN Management | vivo | imported from 3GU |
| S6‑220095 | New KI on route control of PIN | vivo | imported from 3GU |
| S6‑220096 | Scope for TR 23.700-38 | BDBOS | imported from 3GU |
| S6‑220097 | Correct the terminologies of NSCM to NSCE | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| S6‑220098 | Add expansions of the abbreviations | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| S6‑220099 | Add solutions of communication service management | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| S6‑220100 | Address Editor's notes in the clause of requirements and architectures | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| S6‑220101 | New reference point between ECSs for the non-roaming scenario | NTT DOCOMO | imported from 3GU |
| S6‑220102 | Modify figure for low power mode support procedure | NTT DOCOMO | imported from 3GU |
| S6‑220103 | Definition of Abbreviations | NTT DOCOMO | imported from 3GU |
| S6‑220104 | Addition of reference | NTT DOCOMO | imported from 3GU |
| S6‑220105 | Discussion on the near real-time consent | NTT DOCOMO | imported from 3GU |
| S6‑220106 | Evaluation of Solution #3 | NTT DOCOMO | imported from 3GU |
| S6‑220107 | Near real-time consent | NTT DOCOMO | imported from 3GU |
| S6‑220108 | Constraint of roaming scenario | NTT DOCOMO | imported from 3GU |
| S6‑220109 | Revised SID on application enablement aspects for subscriber-aware northbound API access | NTT DOCOMO | imported from 3GU |
| S6‑220110 | Address Editor's notes of fault management | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| S6‑220111 | Discussion on the near real-time consent | NTT DOCOMO INC. | imported from 3GU |
| S6‑220112 | Add Geographic area to user profile configuration data | TD Tech Ltd | imported from 3GU |
| S6‑220113 | FS_NSCALE_solution evaluation for solution 4 QoS verification capability | Huawei Tech.(UK) Co.. Ltd | imported from 3GU |
| S6‑220114 | Discussion on fused location service architecture | CATT | imported from 3GU |
| S6‑220115 | Pseudo-CR on solution#1 update | CATT | imported from 3GU |
| S6‑220116 | Pseudo-CR on solution for supporting geo-fencing applications | CATT | imported from 3GU |
| S6‑220117 | Mapping Considerations of EAS IE and MEC App Instance IE | Intel Technology India Pvt Ltd | imported from 3GU |
| S6‑220118 | EAS Profile update for accessing EES APIs from MEC App Instance | Intel Technology India Pvt Ltd | imported from 3GU |
| S6‑220119 | FS_NSCALE solution evaluation for solution 5 Network slice related performance and analytics exposure | Huawei Tech.(UK) Co.. Ltd | imported from 3GU |
| S6‑220120 | Further Operator Platform Group questions following SDO Workshop | GSMA OPG (Operator Platform API Group) | imported from 3GU |
| S6‑220121 | architecture requirement update | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220122 | Application architecture update | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220123 | Deployment models | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220124 | Key issue on network slice optimization | China Mobile (Suzhou) Software,Huawei | imported from 3GU |
| S6‑220125 | solution for network slice optimization | China Mobile (Suzhou) Software,Lenovo, Huawei | imported from 3GU |
| S6‑220126 | solution 5 update | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220127 | Solution for KI#12- EAS discovery for different users | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220128 | Solve the EN about ECS configuration information | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220129 | Correction on Message Segment Recovery | Huawei, Hisilicon | imported from 3GU |
| S6‑220130 | Correction on Point-to-Point Message Segmentation and Reassembly | Huawei, Hisilicon | imported from 3GU |
| S6‑220131 | Correction on Usage of Network Capabilities | Huawei, Hisilicon | imported from 3GU |
| S6‑220132 | Editoral corrections | Huawei, Hisilicon | imported from 3GU |
| S6‑220133 | Updating aspects related to the MBS resources update | Ericsson | imported from 3GU |
| S6‑220134 | Alignment of some information flows within TS 23.289 | Ericsson | imported from 3GU |
| S6‑220135 | Correction the last step of Segmentation and Reassembly | Huawei, Hisilicon | imported from 3GU |
| S6‑220136 | Use of 5G ProSe UE-to-network relay service for MCx services | Ericsson | imported from 3GU |
| S6‑220137 | Updating aspects and terminology related to MBS session creation and MC traffic transmission | Ericsson | imported from 3GU |
| S6‑220138 | Updating the MBS session release related terminology and aspects | Ericsson | imported from 3GU |
| S6‑220139 | NS Life Cycle for 3rd Party | Samsung Electronics Polska | imported from 3GU |
| S6‑220140 | new KI on advertisement of the existing Network Slice to 3rd party | Samsung Electronics Polska | imported from 3GU |
| S6‑220141 | new KI on Network Slice creation for the 3rd party | Samsung Electronics Polska | imported from 3GU |
| S6‑220142 | Minor corrections to the procedures related to MBS session creation | Samsung Electronics | imported from 3GU |
| S6‑220143 | Removal of Gate Control EN | Ericsson Hungary Ltd | imported from 3GU |
| S6‑220144 | Updates in Annexure Figure Caption | Intel Technology India Pvt Ltd | imported from 3GU |
| S6‑220145 | Solution #8 update: CAPIF interconnection for EAS Service APIs | ETRI, Uangel | imported from 3GU |
| S6‑220146 | Solution #11 update: interacting procedures via CAPIF interconnection | ETRI, Uangel | imported from 3GU |
| S6‑220147 | Pseudo-CR on solution#1 update | CATT | imported from 3GU |
| S6‑220148 | Pseudo-CR on solution for supporting geo-fencing applications | CATT | imported from 3GU |
| S6‑220149 | Pseudo-CR on update on solution #4 | CATT | imported from 3GU |
| S6‑220150 | Pseudo-CR on evaluation on solution #6 | CATT | imported from 3GU |
| S6‑220151 | SA for information | CATT | imported from 3GU |
| S6‑220152 | Fix consistency issue | Ericsson | imported from 3GU |
| S6‑220153 | Remove ACR example in UE ID API | Ericsson | imported from 3GU |
| S6‑220154 | Solve ACR API inconsistency | Ericsson | imported from 3GU |
| S6‑220155 | Solve EN for ACR co-existence | Ericsson | imported from 3GU |
| S6‑220156 | Clarify the VAL UE ID | Ericsson | imported from 3GU |
| S6‑220157 | Correct TSC stream availability discovery | Ericsson | imported from 3GU |
| S6‑220158 | Complete location retrieval in an area | Ericsson | imported from 3GU |
| S6‑220159 | Constraint device in EDGEAPP | Ericsson | imported from 3GU |
| S6‑220160 | New KI Simultaneous EAS Connectivity in ACR | Ericsson | imported from 3GU |
| S6‑220161 | Support simultaneous EAS Connectivity in ACR | Ericsson | imported from 3GU |
| S6‑220162 | Discover a proper AEF | Ericsson | imported from 3GU |
| S6‑220163 | UE-originated API invocation within CAPIF | Ericsson | imported from 3GU |
| S6‑220164 | Initial EAS selection declaration | Ericsson | imported from 3GU |
| S6‑220165 | Correct QoS monitoring service | Ericsson | imported from 3GU |
| S6‑220166 | Key Issue on support for application performance analytics | Lenovo Future Communications | imported from 3GU |
| S6‑220167 | Key Issue on interactions with SEAL | Lenovo Future Communications | imported from 3GU |
| S6‑220168 | New solution for enhancements to service continuity planning | KPN N.V., Ericsson | imported from 3GU |
| S6‑220169 | Key Issue on edge analytics enablement | Lenovo Future Communications | imported from 3GU |
| S6‑220170 | Key Issue on support for application data collection coordination | Lenovo Future Communications | imported from 3GU |
| S6‑220171 | Update of Key Issue 12 | Lenovo Future Communications | imported from 3GU |
| S6‑220172 | Solution on slice optimization for edge based NSCE deployments | Lenovo Future Communications | imported from 3GU |
| S6‑220173 | New WID on support of the 5GMSG Service phase 2 | China Mobile Com. Corporation | imported from 3GU |
| S6‑220174 | Clarification on clause 5.3.3 functional entity of MSGin5G Client | China Mobile Com. Corporation | imported from 3GU |
| S6‑220175 | correction on clause 8.8 Other MSGin5G messaging related procedures | China Mobile Com. Corporation | imported from 3GU |
| S6‑220176 | Correct TSC stream availability discovery | Ericsson | imported from 3GU |
| S6‑220177 | Clarification and correction on clause 8.11 Constrained devices | China Mobile Com. Corporation | imported from 3GU |
| S6‑220178 | Presentation of TR23.700-99 to TSG | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220179 | Pseudo-CR on Key issue #X: EAS discovery for multi-player sessions | Apple GmbH | imported from 3GU |
| S6‑220180 | Pseudo-CR on Solution proposal for Key issue #X: EAS discovery for multi-player sessions | Apple GmbH | imported from 3GU |
| S6‑220181 | New KI Method of supporting federated EAS service | Samsung Electronics Benelux BV | imported from 3GU |
| S6‑220182 | FS_ACE_IOT_Reference points for Application Service Management | Samsung | imported from 3GU |
| S6‑220183 | FS_ACE_IoT_Status collection from ASM client | Samsung | imported from 3GU |
| S6‑220184 | Implicit registration handling in service continuity | Samsung | imported from 3GU |
| S6‑220185 | FS_eEDGEAPP_Solution to KI#3 | Samsung | imported from 3GU |
| S6‑220186 | FS_eEDGEAPP_solution to KI#13 | Samsung | imported from 3GU |
| S6‑220187 | Definitions of Gateway UE and Relay UE | Samsung | imported from 3GU |
| S6‑220188 | FS_SNAAPP-KI_Resource Owner Related API | Samsung | imported from 3GU |
| S6‑220189 | FS_SNAAPP-Solution to KI#4 | Samsung | imported from 3GU |
| S6‑220190 | Service Provisioning correction | Convida Wireless LLC | imported from 3GU |
| S6‑220191 | EAS selection synchronization at registration | Convida Wireless LLC | imported from 3GU |
| S6‑220192 | ECS announcement | Convida Wireless LLC | imported from 3GU |
| S6‑220193 | End-to-End AC interaction via Common EAS KI | Convida Wireless LLC | imported from 3GU |
| S6‑220194 | Cache management KI | Convida Wireless LLC | imported from 3GU |
| S6‑220195 | Discussion on MSGin5G-SEALDD integration | Convida Wireless LLC | imported from 3GU |
| S6‑220196 | Solution for KI#10 - V-ECS Discovery during Steering of Roaming | InterDigital | imported from 3GU |
| S6‑220197 | Solution for MSGin5G-SEALDD integration | Convida Wireless LLC | imported from 3GU |
| S6‑220198 | Terminology alignment and corrections | Convida Wireless LLC | imported from 3GU |
| S6‑220199 | Obtaining RO consent enhancements | Convida Wireless LLC | imported from 3GU |
| S6‑220200 | Onboarding UE API Invokers | Convida Wireless LLC | imported from 3GU |
| S6‑220201 | LS on FS_eEDGEAPP Solution for Support of Roaming UEs | InterDigital | imported from 3GU |
| S6‑220202 | IoT Platform functional models | Convida Wireless LLC | imported from 3GU |
| S6‑220203 | UE activity pattern and monitoring solution | Convida Wireless LLC | imported from 3GU |
| S6‑220204 | Device Triggering Services Solution | Convida Wireless LLC | imported from 3GU |
| S6‑220205 | Revised SID on Application Capability Exposure for IoT Platforms | Convida Wireless LLC | imported from 3GU |
| S6‑220206 | EPS interworking requirements | Ericsson | imported from 3GU |
| S6‑220207 | Solution to KI#2 – Change of USS during flight | InterDigital | imported from 3GU |
| S6‑220208 | MC services over 5GS supporting EPS interworking | Ericsson | imported from 3GU |
| S6‑220209 | Constrained devices | Qualcomm | imported from 3GU |
| S6‑220210 | EDGE-5 APIs | Qualcomm | imported from 3GU |
| S6‑220211 | Federation and Roaming | Qualcomm | imported from 3GU |
| S6‑220212 | Involved relation for Federation and Roaming | Qualcomm | imported from 3GU |
| S6‑220213 | New KI on linkage between EASs | Qualcomm | imported from 3GU |
| S6‑220214 | Network notifications of EPS interworking related events | Ericsson | imported from 3GU |
| S6‑220215 | Update to inter-system switching between 5G MBS and eMBMS procedures | Ericsson | imported from 3GU |
| S6‑220216 | Stage 3 identified issues for EDGEAPP | Huawei, Hisilicon | imported from 3GU |
| S6‑220217 | Adding missing events for ACR notifications | Huawei, Hisilicon | imported from 3GU |
| S6‑220218 | Correction of ACR request and response messages | Huawei, Hisilicon | imported from 3GU |
| S6‑220219 | Unique identification in ACR procedures | Huawei, Hisilicon | imported from 3GU |
| S6‑220220 | Unique identification of the EEC context in ACR procedures | Huawei, Hisilicon | imported from 3GU |
| S6‑220221 | Reply LS on Enquires on Application Context Relocation (ACR) functionality | Huawei, Hisilicon | imported from 3GU |
| S6‑220222 | Reply LS on Identification of ACRs | Huawei, Hisilicon | imported from 3GU |
| S6‑220223 | Reply LS on clarifications to the Application Context Relocation (ACR) functionality | Huawei, Hisilicon | imported from 3GU |
| S6‑220224 | Correction to clarify about sharing location information across VAL servers | Huawei, Hisilicon | imported from 3GU |
| S6‑220225 | Corrections for operations of C2 communication mode switching | Huawei, Hisilicon | imported from 3GU |
| S6‑220226 | Correction for realtime UAV status | Huawei, Hisilicon | imported from 3GU |
| S6‑220227 | Clean up of EPS-5GMBS interworking | Huawei, Hisilicon | imported from 3GU |
| S6‑220228 | Clean up of switching between unicast and 5G MBS, between LTE eMBMS and 5G MBS | Huawei, Hisilicon | imported from 3GU |
| S6‑220229 | Enhanced MCPTT group call setup procedure with 5MBS session | Huawei, Hisilicon | imported from 3GU |
| S6‑220230 | Information flows for media distribution over 5MBS | Huawei, Hisilicon | imported from 3GU |
| S6‑220231 | Description of 5G MBS usage for MCData | Huawei, Hisilicon | imported from 3GU |
| S6‑220232 | Updates to usage of 5MBS for MCVideo | Huawei, Hisilicon | imported from 3GU |
| S6‑220233 | Corrections to align with SA2 5G MBS specification | Huawei, Hisilicon | imported from 3GU |
| S6‑220234 | Usage of FEC capabilities | Huawei, Hisilicon | imported from 3GU |
| S6‑220235 | Architectural model over 5G ProSe | Huawei, Hisilicon | imported from 3GU |
| S6‑220236 | Off-network functional model over 5G ProSe | Huawei, Hisilicon | imported from 3GU |
| S6‑220237 | Off network group communication for MC service | Huawei, Hisilicon | imported from 3GU |
| S6‑220238 | Off network private communication for MC service | Huawei, Hisilicon | imported from 3GU |
| S6‑220239 | 5G ProSe UE-to-network relay for MC service | Huawei, Hisilicon | imported from 3GU |
| S6‑220240 | Service continuity with a 5G ProSe UE-to-network relay for MBMS | Huawei, Hisilicon | imported from 3GU |
| S6‑220241 | Communication with FFAPP service requirements | Huawei, Hisilicon | imported from 3GU |
| S6‑220242 | MCData via full service mode | Huawei, Hisilicon | imported from 3GU |
| S6‑220243 | Key Issue on Ad hoc group call | Huawei, Hisilicon | imported from 3GU |
| S6‑220244 | Solution for Ad hoc group call | Huawei, Hisilicon | imported from 3GU |
| S6‑220245 | Key issue on SEALDD coordination with EDGEAPP | Huawei, Hisilicon | imported from 3GU |
| S6‑220246 | Key issue on SEALDD enabled Data Caching | Huawei, Hisilicon | imported from 3GU |
| S6‑220247 | Solution on SEALDD enabled Data Caching | Huawei, Hisilicon | imported from 3GU |
| S6‑220248 | Key issue on SEALDD server discovery and selection | Huawei, Hisilicon | imported from 3GU |
| S6‑220249 | Solution on KI#1: E2E redundant transmission path establishment | Huawei, Hisilicon | imported from 3GU |
| S6‑220250 | Update to SEALDD architecture for traffic flow description | Huawei, Hisilicon | imported from 3GU |
| S6‑220251 | Key issue on ACR scenarios overlapping | Huawei, Hisilicon | imported from 3GU |
| S6‑220252 | Key issue on EAS discovery in roaming scenario | Huawei, Hisilicon | imported from 3GU |
| S6‑220253 | Update to key issue on T-EES discovery for Edge services support across ECSPs | Huawei, Hisilicon | imported from 3GU |
| S6‑220254 | Solution on ACR scenario overlapping | Huawei, Hisilicon | imported from 3GU |
| S6‑220255 | Solution on EAS discovery in roaming scenario | Huawei, Hisilicon | imported from 3GU |
| S6‑220256 | Solution on T-EAS discovery in roaming scenario | Huawei, Hisilicon | imported from 3GU |
| S6‑220257 | Solution on T-EES discovery for roaming scenario | Huawei, Hisilicon | imported from 3GU |
| S6‑220258 | Solution on application traffic influence for initial EAS discovery | Huawei, Hisilicon | imported from 3GU |
| S6‑220259 | Solution for KI#3 - Enhancements to service continuity planning for ACR modification | Huawei, Hisilicon | imported from 3GU |
| S6‑220260 | Solution for KI#3 - Enhancements to service continuity planning with prediction expiration time | Huawei, Hisilicon | imported from 3GU |
| S6‑220261 | Update to Functional model solution | Huawei, Hisilicon | imported from 3GU |
| S6‑220262 | reply LS - Reply LS on maximum number of MBS sessions that can be associated to a PDU session | SA6 | imported from 3GU |
| S6‑220263 | Reply LS ( S6-220120) to SA - Further Operator Platform Group questions following SDO Workshop | SA6 | imported from 3GU |
| S6‑220264 | Reply LS (S6-220012) - LS on follow-up on EAS definition | SA6 | imported from 3GU |
| S6‑220265 | Reply LS - Reply LS on Prioritized Vehicle to Cloud Technical Solutions (Automotive Edge Computing Consortium (AECC)) | SA6 | imported from 3GU |
| S6‑220266 | Transferring bearer pre-emption rate limitation information from MME up to the MC AS | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S6‑220267 | Revised SID on 5G-enabled fused location service capability exposure | CATT | imported from 3GU |
| S6‑220268 | Relationship between SEALDD and MSGin5G | Huawei | imported from 3GU |
| S6‑220269 | Updating aspects related to the MBS resources update | Ericsson | imported from 3GU |
| S6‑220270 | Alignment of some information flows within TS 23.289 | Ericsson | imported from 3GU |
| S6‑220271 | Use of 5G ProSe UE-to-network relay service for MC services | Ericsson | imported from 3GU |
| S6‑220272 | Updating aspects and terminology related to MBS session creation and MC traffic transmission | Ericsson | imported from 3GU |
| S6‑220273 | Updating the MBS session release related terminology and aspects | Ericsson | imported from 3GU |
| S6‑220274 | Edge Notification Server | AT&T | imported from 3GU |
| S6‑220275 | Alignment of section 4.7 of 23.289 with latest version of 23.247 (v 17.1.0) | AT&T, Huawei, Hisilicon | imported from 3GU |
| S6‑220276 | Functional model reference points | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑220277 | Functional model media plane aspects | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑220278 | Using identities behind the MC gateway UE | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑220279 | New WID on Interconnection and Migration Aspects for Railways | Nokia, Nokia Shanghai Bell, UIC, Kontron Transportation France | imported from 3GU |
| S6‑220280 | Selected T-EAS declaration procedure corrections | VODAFONE Group Plc | imported from 3GU |
| S6‑220281 | Pseudo-CR on Key issue #X: EAS discovery for multi-player sessions | Apple GmbH | imported from 3GU |
| S6‑220282 | Correction of Enhanced Status description | Sepura Ltd | imported from 3GU |
| S6‑220283 | LS on FS_eEDGEAPP Solution for Support of Roaming UEs | InterDigital | imported from 3GU |
| S6‑220284 | Solution for KI#10 - V-ECS Discovery via the H-ECS | InterDigital | imported from 3GU |
| S6‑220285 | Solution for KI#9 - Enhancement of dynamic EAS instantiation triggering | InterDigital, Ericsson | imported from 3GU |
| S6‑220286 | Alignment with the approved study on UAV Ph2 in SA2 | InterDigital | imported from 3GU |
| S6‑220287 | Solution to KI#2 – Change of USS during flight | InterDigital | imported from 3GU |
| S6‑220288 | Update EDGE UE ID in UE ID API | Ericsson | imported from 3GU |
| S6‑220289 | Correct QoS monitoring service | Ericsson | imported from 3GU |
| S6‑220290 | Solve EN for ACR co-existence | Ericsson | imported from 3GU |
| S6‑220291 | Complete location retrieval in an area | Ericsson | imported from 3GU |
| S6‑220292 | Fix consistency issue | Ericsson | imported from 3GU |
| S6‑220293 | Solve ACR API inconsistency | Ericsson | imported from 3GU |
| S6‑220294 | Discover a proper AEF | Ericsson | imported from 3GU |
| S6‑220295 | UE-originated API invocation within CAPIF | Ericsson | imported from 3GU |
| S6‑220296 | Initial EAS selection declaration | Ericsson | imported from 3GU |
| S6‑220297 | New KI Simultaneous EAS Connectivity in ACR | Ericsson | imported from 3GU |
| S6‑220298 | Support simultaneous EAS Connectivity in ACR | Ericsson | imported from 3GU |
| S6‑220299 | Solution #8 update: CAPIF interconnection for EAS Service APIs | ETRI, Uangel | imported from 3GU |
| S6‑220300 | Revised SID on Service Function Chaining support for Edge Data Networks | Intel Technology India Pvt Ltd | imported from 3GU |
| S6‑220301 | Mapping Considerations of EAS IE and MEC App Instance IE | Intel Technology India Pvt Ltd | imported from 3GU |
| S6‑220302 | EAS Profile update for accessing EES APIs from MEC App Instance | Intel Technology India Pvt Ltd | imported from 3GU |
| S6‑220303 | Updates in Annexure Figure Caption | Intel Technology India Pvt Ltd | imported from 3GU |
| S6‑220304 | New Solution for call transfer between MCPTT users in different MCPTT systems | Kontron Transportation France, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S6‑220305 | FS_NSCALE architectural requirements | AsiaInfo Technologies Inc | imported from 3GU |
| S6‑220306 | FS_NSCALE solution evaluation for solution 4 | AsiaInfo Technologies Inc | imported from 3GU |
| S6‑220307 | FS_NSCALE Update the architecture for network slice capability enablement | AsiaInfo Technologies Inc,CMCC | imported from 3GU |
| S6‑220308 | FS_NSCALE solution evaluation for solution 4 | AsiaInfo Technologies Inc,Huawei | imported from 3GU |
| S6‑220309 | FS_eEDGEAPP architectural requirements | AsiaInfo Technologies Inc | imported from 3GU |
| S6‑220310 | architecture requirement update | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220311 | Application architecture update | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220312 | Deployment models | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220313 | Key issue on network slice optimization | China Mobile (Suzhou) Software,Huawei | imported from 3GU |
| S6‑220314 | solution for network slice optimization | China Mobile (Suzhou) Software,Lenovo, Huawei | imported from 3GU |
| S6‑220315 | Solution for KI#12- EAS discovery for different users | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220316 | New WID on support of the 5GMSG Service phase 2 | China Mobile Com. Corporation | imported from 3GU |
| S6‑220317 | Solve the EN about ECS configuration information | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220318 | Clarification on clause 5.3.3 functional entity of MSGin5G Client | China Mobile Com. Corporation | imported from 3GU |
| S6‑220319 | correction on clause 8.8 Other MSGin5G messaging related procedures | China Mobile Com. Corporation | imported from 3GU |
| S6‑220320 | Clarification and correction on clause 8.11 Constrained devices | China Mobile Com. Corporation | imported from 3GU |
| S6‑220321 | FS_NSCALE solution evaluation for solution 5 Network slice related performance and analytics exposure | Huawei Tech.(UK) Co.. Ltd | imported from 3GU |
| S6‑220322 | FS_NSCALE solution evaluation for solution 5 Network slice related performance and analytics exposure | Huawei Tech.(UK) Co.. Ltd | imported from 3GU |
| S6‑220323 | FFAPP Architecture | ZTE Corporation | imported from 3GU |
| S6‑220324 | FFAPP Deployment models | ZTE Corporation | imported from 3GU |
| S6‑220325 | EAS selection synchronization at registration | Convida Wireless LLC | imported from 3GU |
| S6‑220326 | IoT Platform functional models | Convida Wireless LLC | imported from 3GU |
| S6‑220327 | End-to-End AC interaction via Common EAS KI | Convida Wireless LLC | imported from 3GU |
| S6‑220328 | Terminology alignment and corrections | Convida Wireless LLC | imported from 3GU |
| S6‑220329 | Obtaining RO consent enhancements | Convida Wireless LLC | imported from 3GU |
| S6‑220330 | Onboarding UE API Invokers | Convida Wireless LLC | imported from 3GU |
| S6‑220331 | Device Triggering Services Solution | Convida Wireless LLC | imported from 3GU |
| S6‑220332 | New solution for enhancements to service continuity planning | KPN N.V., Ericsson | imported from 3GU |
| S6‑220333 | Revised SID on Application Capability Exposure for IoT Platforms | Convida Wireless LLC | imported from 3GU |
| S6‑220334 | Pseudo-CR on Preconditions of Solution 7 | China Mobile Com. Corporation | imported from 3GU |
| S6‑220335 | Pseudo-CR on KI of Coordination Between Uu and PC5 | China Mobile Com. Corporation | imported from 3GU |
| S6‑220336 | solution for KI 10 | China Mobile Com. Corporation | imported from 3GU |
| S6‑220337 | Add solutions of communication service management | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| S6‑220338 | Address Editor's notes in the clause of requirements and architectures | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| S6‑220339 | Address Editor's notes of fault management | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| S6‑220340 | New KI Method of supporting federated EAS service | Samsung Electronics Benelux BV | imported from 3GU |
| S6‑220341 | Service Provisioning correction | Convida Wireless LLC | imported from 3GU |
| S6‑220342 | Minor corrections to the procedures related to MBS session creation | Samsung Electronics | imported from 3GU |
| S6‑220343 | Pseudo-CR on Solution proposal for key issue 1 | Samsung, FirstNet, AT&T | imported from 3GU |
| S6‑220344 | Pseudo-CR on Solution proposal for key issue 1 | Samsung, FirstNet, AT&T | imported from 3GU |
| S6‑220345 | Pseudo-CR on Key issue 1 for Ad hoc group communication | Samsung, FirstNet, AT&T | imported from 3GU |
| S6‑220346 | Constrained devices | Qualcomm | imported from 3GU |
| S6‑220347 | EDGE-5 APIs | Qualcomm | imported from 3GU |
| S6‑220348 | Federation and Roaming | Qualcomm | imported from 3GU |
| S6‑220349 | Involved relation for Federation and Roaming | Qualcomm | imported from 3GU |
| S6‑220350 | New KI on linkage between EASs | Qualcomm | imported from 3GU |
| S6‑220351 | Reply LS on follow-up on EAS definition | Qualcomm | imported from 3GU |
| S6‑220352 | Control of allowing service continuity planning | Samsung | imported from 3GU |
| S6‑220353 | Update ECS configuration information to support roaming and federation | Samsung | imported from 3GU |
| S6‑220354 | Reply LS on Prioritized Vehicle to Cloud Technical Solutions (Automotive Edge Computing Consortium (AECC)) | SA6 | imported from 3GU |
| S6‑220355 | Introduction for 3GPP TR 23.700-36 | Lenovo Future Communications | imported from 3GU |
| S6‑220356 | Proposed functional architecture for ADAES | Lenovo Future Communications | imported from 3GU |
| S6‑220357 | Key Issue on support for application performance analytics | Lenovo Future Communications | imported from 3GU |
| S6‑220358 | Key Issue on interactions with SEAL | Lenovo Future Communications | imported from 3GU |
| S6‑220359 | Key Issue on edge analytics enablement | Lenovo Future Communications | imported from 3GU |
| S6‑220360 | Key Issue on support for application data collection coordination | Lenovo Future Communications | imported from 3GU |
| S6‑220361 | Update of Key Issue 12 | Lenovo Future Communications | imported from 3GU |
| S6‑220362 | Correction on Message Segment Recovery | Huawei, Hisilicon | imported from 3GU |
| S6‑220363 | Correction on Point-to-Point Message Segmentation and Reassembly | Huawei, Hisilicon | imported from 3GU |
| S6‑220364 | FS_ACE_IOT_Reference points for Application Service Management | Samsung | imported from 3GU |
| S6‑220365 | FS_ACE_IoT_Status collection from ASM client | Samsung | imported from 3GU |
| S6‑220366 | EDGEAPP_Implicit registration handling in service continuity | Samsung | imported from 3GU |
| S6‑220367 | FS_eEDGEAPP_Solution to KI#3 | Samsung | imported from 3GU |
| S6‑220368 | 5GMARCH_Definitions of gateway UE and relay UE | Samsung | imported from 3GU |
| S6‑220369 | FS_SNAAPP-KI_Resource Owner Related API | Samsung | imported from 3GU |
| S6‑220370 | FS_SNAAPP-Solution to KI#4 | Samsung | imported from 3GU |
| S6‑220371 | Withdrawn | SA6 | imported from 3GU |
| S6‑220372 | EEC capability to identify ECS address | vivo | imported from 3GU |
| S6‑220373 | Study on Application layer support for Personal IoT Networks | vivo Mobile Communications Ltd, China Unicom, China Telecom, Spreadtrum | imported from 3GU |
| S6‑220374 | Proposed skeleton for 3GPP TR 23.700-78 | vivo | imported from 3GU |
| S6‑220375 | Introduction for 3GPP TR 23.700-78 | vivo | imported from 3GU |
| S6‑220376 | Scope for 3GPP TR 23.700-78 | vivo | imported from 3GU |
| S6‑220377 | New KI on PIN Management | vivo | imported from 3GU |
| S6‑220378 | New KI on PINAPP accesses 5G network by application mechanism | vivo | imported from 3GU |
| S6‑220379 | S6-220140_Rev1_new KI on advertisement of the existing Network Slice to 3rd party | Samsung Electronics Polska, Lenovo | imported from 3GU |
| S6‑220380 | Constraint device in EDGEAPP | Ericsson | imported from 3GU |
| S6‑220381 | S6-220141_Rev1_new KI on Network Slice creation for the 3rd party | Samsung Electronics Polska | imported from 3GU |
| S6‑220382 | Adding missing events for ACR notifications | Huawei, Hisilicon | imported from 3GU |
| S6‑220383 | Unique identification in ACR procedures | Huawei, Hisilicon | imported from 3GU |
| S6‑220384 | Unique identification of the EEC context in ACR procedures | Huawei, Hisilicon | imported from 3GU |
| S6‑220385 | Reply LS on Enquires on Application Context Relocation (ACR) functionality | Huawei, Hisilicon | imported from 3GU |
| S6‑220386 | Reply LS on Identification of ACRs | Huawei, Hisilicon | imported from 3GU |
| S6‑220387 | Reply LS on clarifications to the Application Context Relocation (ACR) functionality | Huawei, Hisilicon | imported from 3GU |
| S6‑220388 | Correction to clarify about sharing location information across VAL servers | Huawei, Hisilicon | imported from 3GU |
| S6‑220389 | Corrections for operations of C2 communication mode switching | Huawei, Hisilicon | imported from 3GU |
| S6‑220390 | Clean up of EPS-5GMBS interworking | Huawei, Hisilicon | imported from 3GU |
| S6‑220391 | Clean up of switching between unicast and 5G MBS, between LTE eMBMS and 5G MBS | Huawei, Hisilicon | imported from 3GU |
| S6‑220392 | Enhanced MCPTT group call setup procedure with 5MBS session | Huawei, Hisilicon | imported from 3GU |
| S6‑220393 | Information flows for media distribution over 5MBS | Huawei, Hisilicon | imported from 3GU |
| S6‑220394 | Description of 5G MBS usage for MCData | Huawei, Hisilicon | imported from 3GU |
| S6‑220395 | Updates to usage of 5MBS for MCVideo | Huawei, Hisilicon | imported from 3GU |
| S6‑220396 | Corrections to align with SA2 5G MBS specification | Huawei, Hisilicon | imported from 3GU |
| S6‑220397 | Usage of FEC capabilities | Huawei, Hisilicon | imported from 3GU |
| S6‑220398 | Architectural model over 5G ProSe | Huawei, Hisilicon | imported from 3GU |
| S6‑220399 | Off-network functional model over 5G ProSe | Huawei, Hisilicon | imported from 3GU |
| S6‑220400 | Off network private communication for MC service | Huawei, Hisilicon | imported from 3GU |
| S6‑220401 | 5G ProSe UE-to-network relay for MC service | Huawei, Hisilicon | imported from 3GU |
| S6‑220402 | Service continuity with a 5G ProSe UE-to-network relay for MBMS | Huawei, Hisilicon | imported from 3GU |
| S6‑220403 | Communication with FFAPP service requirements | Huawei, Hisilicon | imported from 3GU |
| S6‑220404 | MCData via full service mode | Huawei, Hisilicon | imported from 3GU |
| S6‑220405 | Key Issue on Ad hoc group call | Huawei, Hisilicon, Samsung, FirstNet, AT&T, Kontron Transportation France, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S6‑220406 | Solution for Ad hoc group call | Huawei, Hisilicon | imported from 3GU |
| S6‑220407 | Key issue on SEALDD coordination with EDGEAPP | Huawei, Hisilicon | imported from 3GU |
| S6‑220408 | Key issue on SEALDD enabled Data Storage | Huawei, Hisilicon, AsiaInfo Technologies Inc, Convida Wireless LLC | imported from 3GU |
| S6‑220409 | Key issue on SEALDD server discovery and selection | Huawei, Hisilicon | imported from 3GU |
| S6‑220410 | Solution on KI#1: E2E redundant transmission path establishment | Huawei, Hisilicon | imported from 3GU |
| S6‑220411 | Update to SEALDD architecture for traffic flow description | Huawei, Hisilicon | imported from 3GU |
| S6‑220412 | Key issue on ACR scenarios overlapping | Huawei, Hisilicon, InterDigital | imported from 3GU |
| S6‑220413 | Key issue on EAS discovery in roaming scenario | Huawei, Hisilicon | imported from 3GU |
| S6‑220414 | Update to key issue on T-EES discovery for Edge services support across ECSPs | Huawei, Hisilicon | imported from 3GU |
| S6‑220415 | Solution on ACR scenario overlapping | Huawei, Hisilicon | imported from 3GU |
| S6‑220416 | Solution on application traffic influence for initial EAS discovery | Huawei, Hisilicon | imported from 3GU |
| S6‑220417 | Solution for KI#3 - Enhancements to service continuity planning for ACR modification | Huawei, Hisilicon | imported from 3GU |
| S6‑220418 | Solution for KI#3 - Enhancements to service continuity planning with prediction expiration time | Huawei, Hisilicon | imported from 3GU |
| S6‑220419 | Update to Functional model solution | Huawei, Hisilicon | imported from 3GU |
| S6‑220420 | New reference point between ECSs for the non-roaming scenario | NTT DOCOMO | imported from 3GU |
| S6‑220421 | Addition of reference | NTT DOCOMO, China Mobile | imported from 3GU |
| S6‑220422 | Evaluation of Solution #3 | NTT DOCOMO | imported from 3GU |
| S6‑220423 | Near real-time consent | NTT DOCOMO | imported from 3GU |
| S6‑220424 | Revised SID on application enablement aspects for subscriber-aware northbound API access | NTT DOCOMO | imported from 3GU |
| S6‑220425 | Pseudo-CR on solution#1 update | CATT | imported from 3GU |
| S6‑220426 | Pseudo-CR on update on solution #4 | CATT | imported from 3GU |
| S6‑220427 | Revised SID on 5G-enabled fused location service capability exposure | CATT | imported from 3GU |
| S6‑220428 | SA6#47-e Work Plan Review | SA6 chair | imported from 3GU |
| S6‑220429 | LS on FS_eEDGEAPP Solution for Support of Roaming UEs | SA6 | imported from 3GU |
| S6‑220430 | Adding missing events for ACR notifications | Huawei, Hisilicon | imported from 3GU |
| S6‑220431 | Reply LS on Enquires on Application Context Relocation (ACR) functionality | SA6 | imported from 3GU |
| S6‑220432 | Reply LS on further Operator Platform Group questions following SDO Workshop | SA6 | imported from 3GU |
| S6‑220433 | Correction on Message Segment Recovery | Huawei, Hisilicon | imported from 3GU |
| S6‑220434 | Correction on Point-to-Point Message Segmentation and Reassembly | Huawei, Hisilicon | imported from 3GU |
| S6‑220435 | Correction on Usage of Network Capabilities | Huawei, Hisilicon | imported from 3GU |
| S6‑220436 | Editoral corrections | Huawei, Hisilicon | imported from 3GU |
| S6‑220437 | Clarification on clause 5.3.3 functional entity of MSGin5G Client | China Mobile Com. Corporation | imported from 3GU |
| S6‑220438 | correction on clause 8.8 Other MSGin5G messaging related procedures | China Mobile Com. Corporation | imported from 3GU |
| S6‑220439 | Clarification and correction on clause 8.11 Constrained devices | China Mobile Com. Corporation | imported from 3GU |
| S6‑220440 | Clean up of EPS-5GMBS interworking | Huawei, Hisilicon | imported from 3GU |
| S6‑220441 | Clean up of switching between unicast and 5G MBS, between LTE eMBMS and 5G MBS | Huawei, Hisilicon | imported from 3GU |
| S6‑220442 | FFAPP Deployment models | ZTE Corporation | imported from 3GU |
| S6‑220443 | Pseudo-CR on Key issue 1 for Ad hoc group communication | Samsung, FirstNet, AT&T, Nokia, Nokia Shanghai Bell, Kontron Transportation France, UIC | imported from 3GU |
| S6‑220444 | Pseudo-CR on Solution proposal for key issue 1 | Samsung, FirstNet, AT&T | imported from 3GU |
| S6‑220445 | new KI on advertisement of the existing Network Slice to 3rd party | Samsung Electronics Polska | imported from 3GU |
| S6‑220446 | new KI on Network Slice creation for the 3rd party | Samsung Electronics Polska | imported from 3GU |
| S6‑220447 | Key issue on network slice optimization | China Mobile (Suzhou) Software,Huawei | imported from 3GU |
| S6‑220448 | solution for KI 10 | China Mobile Com. Corporation | imported from 3GU |
| S6‑220449 | Update to Functional model solution | Huawei, Hisilicon | imported from 3GU |
| S6‑220450 | UE-originated API invocation within CAPIF | Ericsson | imported from 3GU |
| S6‑220451 | Near real-time consent | NTT DOCOMO | imported from 3GU |
| S6‑220452 | Discover a proper AEF | Ericsson | imported from 3GU |
| S6‑220453 | Evaluation of Solution #3 | NTT DOCOMO | imported from 3GU |
| S6‑220454 | Mapping Considerations of EAS IE and MEC App Instance IE | Intel Technology India Pvt Ltd | imported from 3GU |
| S6‑220455 | Updates in Annexure Figure Caption | Intel Technology India Pvt Ltd | imported from 3GU |
| S6‑220456 | FS_ACE_IoT_Status collection from ASM client | Samsung | imported from 3GU |
| S6‑220457 | Update to key issue on T-EES discovery for Edge services support across ECSPs | Huawei, Hisilicon | imported from 3GU |
| S6‑220458 | Pseudo-CR on Key issue #X: EAS discovery for multi-player sessions | Apple GmbH, Convida Wireless LLC | imported from 3GU |
| S6‑220459 | New KI on linkage between EASs | Qualcomm | imported from 3GU |
| S6‑220460 | Key issue on ACR scenarios overlapping | Huawei, Hisilicon | imported from 3GU |
| S6‑220461 | FS_eEDGEAPP architectural requirements | AsiaInfo Technologies Inc | imported from 3GU |
| S6‑220462 | Constrained devices | Qualcomm | imported from 3GU |
| S6‑220463 | Control of allowing service continuity planning | Samsung | imported from 3GU |
| S6‑220464 | Update ECS configuration information to support roaming and federation | Samsung | imported from 3GU |
| S6‑220465 | Solution for KI#10 - V-ECS Discovery via the H-ECS | InterDigital | imported from 3GU |
| S6‑220466 | Initial EAS selection declaration | Ericsson | imported from 3GU |
| S6‑220467 | EAS selection synchronization at registration | Convida Wireless LLC | imported from 3GU |
| S6‑220468 | Solution for KI#12- EAS discovery for different users | China Mobile (Suzhou) Software, Ericsson | imported from 3GU |
| S6‑220469 | Constraint device in EDGEAPP | Ericsson | imported from 3GU |
| S6‑220470 | Solution on ACR scenario overlapping | Huawei, Hisilicon | imported from 3GU |
| S6‑220471 | Pseudo-CR on KI of Coordination Between Uu and PC5 | China Mobile Com. Corporation | imported from 3GU |
| S6‑220472 | Key issue on SEALDD enabled Data Caching | Huawei, Hisilicon, AsiaInfo Technologies Inc, Convida Wireless LLC | imported from 3GU |
| S6‑220473 | Solution on KI#1: E2E redundant transmission path establishment | Huawei, Hisilicon | imported from 3GU |
| S6‑220474 | Key Issue on interactions with SEAL | Lenovo Future Communications | imported from 3GU |
| S6‑220475 | New KI on PIN Management | vivo | imported from 3GU |
| S6‑220476 | New KI on PINAPP accesses 5G network by application mechanism | vivo | imported from 3GU |
| S6‑220477 | New WID on support of the 5GMSG Service phase 2 | China Mobile Com. Corporation | imported from 3GU |
| S6‑220478 | Service continuity with a 5G ProSe UE-to-network relay for MBMS | Huawei, Hisilicon | imported from 3GU |
| S6‑220479 | Solution for KI#3 - Enhancements to service continuity planning for ACR modification | Huawei, Hisilicon | imported from 3GU |
| S6‑220480 | Solution on application traffic influence for initial EAS discovery | Huawei, Hisilicon | imported from 3GU |
| S6‑220481 | SA6 Meeting #47-e - Chairman's notes at end of the meeting | SA6 Chair | imported from 3GU |
page generated from database: 2024-04-22 07:58:53