3GPP TDocs (written contributions) at meeting
Meeting: S6-40-e - 2020-11-16 to 2020-11-24, Online
meeting id: S6-40-e (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| S6‑202037 | SA6 Meeting 40-e Agenda | SA6 Chairman | imported from 3GU |
| S6‑202038 | SA6 Meeting 39-bis-e Report | MCC | imported from 3GU |
| S6‑202039 | SA6 Meeting #40-e - Agenda with Tdocs allocation after submission deadline | SA6 Chairman | imported from 3GU |
| S6‑202040 | SA6 Meeting #40-e - Agenda with Tdocs allocation at start of the meeting | SA6 Chairman | imported from 3GU |
| S6‑202041 | SA6 Meeting #40-e - Chairman's notes at end of the meeting | SA6 Chairman | imported from 3GU |
| S6‑202042 | Reply LS on ETSI Plugtest reports | UPV/EHU (ETSI MCX Plugtests) | imported from 3GU |
| S6‑202043 | LS on Service Layer aspects for 5G MBS | SA2 | imported from 3GU |
| S6‑202044 | Reply LS for IP address to GPSI translation | SA3 | imported from 3GU |
| S6‑202045 | LS to SA6 on the relation between EDGEAPP and ETSI MEC architectures | SA5 | imported from 3GU |
| S6‑202046 | Pseudo CR on alignment of KI #3 and its proposed solutions | InterDigital | imported from 3GU |
| S6‑202047 | Pseudo CR on cleanup on solution #8 | InterDigital | imported from 3GU |
| S6‑202048 | Application specific metadata container | AT&T GNS Belgium SPRL | imported from 3GU |
| S6‑202049 | Pseudo-CR on FS_5GMARCH on Registration | AT&T GNS Belgium SPRL | imported from 3GU |
| S6‑202050 | Pseudo-CR on Clarification on network slicing using by MC system over 5G system | CALTTA | imported from 3GU |
| S6‑202051 | Pseudo-CR on key issue x: UAS Media session monitor and management | Tencent | imported from 3GU |
| S6‑202052 | Solution to Key issue #5.8: UAS Identification usage in application layer architecture | Tencent | imported from 3GU |
| S6‑202053 | Pseudo-CR on Aggregated New Message Request | one2many B.V. | imported from 3GU |
| S6‑202054 | Pseudo-CR on Evaluation in Solution 1 | one2many B.V. | imported from 3GU |
| S6‑202055 | Pseudo-CR on Removal of ENs in 6.7.1.2 | one2many B.V. | imported from 3GU |
| S6‑202056 | Pseudo-CR on Resolution of EN in section 4.2.4 | one2many B.V. | imported from 3GU |
| S6‑202057 | A temporary broadcast group from a combination of Groups and Users | TD Tech Ltd | imported from 3GU |
| S6‑202058 | A temporary broadcast group from a combination of Groups and Users | TD Tech Ltd | imported from 3GU |
| S6‑202059 | Conclusion | Huawei, Hisilicon | imported from 3GU |
| S6‑202060 | Corrections about MSGin5G gateway | Huawei, Hisilicon | imported from 3GU |
| S6‑202061 | Corrections on solution of MOAT messaging | Huawei, Hisilicon | imported from 3GU |
| S6‑202062 | Corrections on solution of APIs | Huawei, Hisilicon | imported from 3GU |
| S6‑202063 | Pseudo-CR on MCOver5GS – use of 5GS by the MC functional | Union Inter. Chemins de Fer | imported from 3GU |
| S6‑202064 | Pseudo-CR on MCOver5GS - 5GS QoS handling | Union Inter. Chemins de Fer | imported from 3GU |
| S6‑202065 | Positioning Service Level for Solution #7 | ZTE Corporation | imported from 3GU |
| S6‑202066 | Entities aligned with the functional model for Solution #11 | ZTE Corporation | imported from 3GU |
| S6‑202067 | Clarify the functionality of FAE server for device monitoring in Solution #18 | ZTE Corporation | imported from 3GU |
| S6‑202068 | Pesudo-CR to remove EN in 6.11.1 | China Mobile Com. Corporation | imported from 3GU |
| S6‑202069 | Pesudo-CR on MGSin5G Group message without using SEAL | China Mobile Com. Corporation | imported from 3GU |
| S6‑202070 | ECS discovery for roaming UEs | Samsung | imported from 3GU |
| S6‑202071 | Path Assessment API | Samsung | imported from 3GU |
| S6‑202072 | UE NAS mode and interaction with 3GPP network | Samsung | imported from 3GU |
| S6‑202073 | EAS instantiation triggered by EES | Samsung | imported from 3GU |
| S6‑202074 | Clarification on target DNAI information | Samsung | imported from 3GU |
| S6‑202075 | Resolution of the EN on DNAI list as a TSA | Intel, Convida Wireless, Samsung, Apple | imported from 3GU |
| S6‑202076 | Clarification on ECS discovery | Samsung | imported from 3GU |
| S6‑202077 | Update requirement for Edge-aware applications | Intel Deutschland GmbH | imported from 3GU |
| S6‑202078 | Deduplication of AF influence | Samsung | imported from 3GU |
| S6‑202079 | Application Context Relocation coordination | Samsung | imported from 3GU |
| S6‑202080 | pCR on service continuity | Samsung | imported from 3GU |
| S6‑202081 | Discussion on IP address to GPSI mapping | Intel Deutschland GmbH | imported from 3GU |
| S6‑202082 | Clarification on S-EAS decided ACR | Samsung | imported from 3GU |
| S6‑202083 | Clarification on S-EES executed ACR | Samsung | imported from 3GU |
| S6‑202084 | pCR on EEC executed ACR via T-EES | Samsung | imported from 3GU |
| S6‑202085 | LS on EEL IP address to GPSI mapping | Intel Deutschland GmbH | imported from 3GU |
| S6‑202086 | 3GPP TS 23.554 skeleton | China Mobile Com. Corporation | imported from 3GU |
| S6‑202087 | Pseudo-CR on FS_5GMARCH overall Evaluation | China Mobile Com. Corporation | imported from 3GU |
| S6‑202088 | Add N6 routing info in EAS profile | Ericsson | imported from 3GU |
| S6‑202089 | AF influence in ACR event | Ericsson | imported from 3GU |
| S6‑202090 | EEC ID clarification | Ericsson | imported from 3GU |
| S6‑202091 | Event report information in UPPM | Ericsson | imported from 3GU |
| S6‑202092 | Removal of duplicate MCData disposition notification information flow | Samsung Electronics Iberia SA | imported from 3GU |
| S6‑202093 | Solving EN for session with QoS API | Ericsson, Apple | imported from 3GU |
| S6‑202094 | EAS ID and EES ID | Ericsson | imported from 3GU |
| S6‑202095 | Support more UE IDs in QoS exposure | Ericsson | imported from 3GU |
| S6‑202096 | Support CAPIF | Ericsson | imported from 3GU |
| S6‑202097 | Support local MBMS | Ericsson | imported from 3GU |
| S6‑202098 | support local MBMS | Ericsson | imported from 3GU |
| S6‑202099 | Clarification to relationship between EAS and MEC application | vivo | imported from 3GU |
| S6‑202100 | Relation between EDGEAPP and ETSI MEC architectures | vivo | imported from 3GU |
| S6‑202101 | LS Reply on relation between EDGEAPP and ETSI MEC architectures | vivo | imported from 3GU |
| S6‑202102 | Corrections to FD using HTTP procedures and editorials | Samsung | imported from 3GU |
| S6‑202103 | Pseudo-CR on ACR initiated by EEC clean-up | Apple, Intel | imported from 3GU |
| S6‑202104 | SEAL support for device onboarding and remote provisioning in an SNPN | Ericsson | imported from 3GU |
| S6‑202105 | Utilize unified 5GC location and report converged location | Ericsson | imported from 3GU |
| S6‑202106 | Consideration on coexistence of ACR solutions | Apple | imported from 3GU |
| S6‑202107 | Discussion on new work regarding network slicing capability exposure | China Mobile Com. Corporation | imported from 3GU |
| S6‑202108 | Discussion on new work regarding network slicing capability exposure | China Mobile Com. Corporation | imported from 3GU |
| S6‑202109 | Discussion on new work regarding network slicing capability exposure | China Mobile Com. Corporation | imported from 3GU |
| S6‑202110 | Evaluation of solution #20 | Ericsson | imported from 3GU |
| S6‑202111 | Discussion on new work regarding network slicing capability exposure | China Mobile Com. Corporation | imported from 3GU |
| S6‑202112 | Discussion on new work regarding network slicing capability exposure | China Mobile Com. Corporation | imported from 3GU |
| S6‑202113 | Discussion on new work regarding network slicing capability exposure | China Mobile Com. Corporation | imported from 3GU |
| S6‑202114 | Evaluation of solution #9 | Ericsson | imported from 3GU |
| S6‑202115 | Initial conclusions for sol#9 and sol#20 | Ericsson | imported from 3GU |
| S6‑202116 | New WID on Network Slice Capability Exposure | China Mobile Com. Corporation | imported from 3GU |
| S6‑202117 | New WID on Network Slice Capability Exposure | China Mobile Com. Corporation | imported from 3GU |
| S6‑202118 | New WID on Network Slice Capability Exposure | China Mobile Com. Corporation | imported from 3GU |
| S6‑202119 | New WID on Network Slice Capability Exposure | China Mobile Com. Corporation | imported from 3GU |
| S6‑202120 | New WID on Network Slice Capability Exposure | China Mobile Com. Corporation | imported from 3GU |
| S6‑202121 | Pseudo-CR on TR 23.783 key issue 10 support of low latency requirements | UIC, Kontron Transportation France | imported from 3GU |
| S6‑202122 | pCR on Correction of EAS Discovery Procedure | Apple | imported from 3GU |
| S6‑202123 | Architecture for TSC services | Ericsson | imported from 3GU |
| S6‑202124 | Scope text restructure | The Police of the Netherlands | imported from 3GU |
| S6‑202125 | Cover sheet Presentation of TR 23.783 to SA for information | The Police of the Netherlands | imported from 3GU |
| S6‑202126 | Pseudo-CR on Resolving EN on Application Context definition | InterDigital | imported from 3GU |
| S6‑202127 | Removal of empty clause 5, renumbering of other subclauses | The Police of the Netherlands | imported from 3GU |
| S6‑202128 | UE-to-UE broadcast/groupcast configuration by VAE layer | Lenovo, Motorola Mobility | imported from 3GU |
| S6‑202129 | SA6 ToR Update | SA6 Leadership | imported from 3GU |
| S6‑202130 | SA6 1H2021 Meeting Calendar | SA6 Chairman | imported from 3GU |
| S6‑202131 | Network slice re-mapping for V2X applications | Lenovo, Motorola Mobility | imported from 3GU |
| S6‑202132 | Update a Note to avoid normative language | Sony | imported from 3GU |
| S6‑202133 | Removal of OSId from ACID | Sony | imported from 3GU |
| S6‑202134 | Definition of non-3GPP device | Nokia, Nokia Shanghai Bell, BDBOS, UIC | imported from 3GU |
| S6‑202135 | UE Location in EAS discovery request | Sony | imported from 3GU |
| S6‑202136 | Connection authorisation principles | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑202137 | Network slice adaptation for VAL applications | Lenovo, Motorola Mobility | imported from 3GU |
| S6‑202138 | Functional architecture refinements | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑202139 | Procedure refinements when the MC gateway UE performs connection authorization | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S6‑202140 | Procedure refinements when the MC server performs connection authorization | Nokia, Nokia Shanghai Bell, BDBOS | imported from 3GU |
| S6‑202141 | Clarifications for T8 interface | CATT | imported from 3GU |
| S6‑202142 | Clarifications for functional alias private calls | CATT | imported from 3GU |
| S6‑202143 | V2V communication mode switching | CATT | imported from 3GU |
| S6‑202144 | Support for local MBMS delivery | CATT | imported from 3GU |
| S6‑202145 | V2X UE registration enhancement | CATT | imported from 3GU |
| S6‑202146 | Clarifications for netwok monitoring information notification | CATT | imported from 3GU |
| S6‑202147 | Depositing file contents distributed via FD communication using HTTP into MCData message store | Samsung Electronics Iberia SA, AT&T | imported from 3GU |
| S6‑202148 | mirror CR on clarifications for T8 interface | CATT | imported from 3GU |
| S6‑202149 | Distribution of file residing in MCData message store account of the MCData user | Samsung, AT&T | imported from 3GU |
| S6‑202150 | pCR on application context relocation vs. service continuity | Qualcomm Technologies Int | imported from 3GU |
| S6‑202151 | pCR on flows and IEs for notify & complete in EEC executed ACR | Qualcomm Technologies Int | imported from 3GU |
| S6‑202152 | pCR on flows and IEs for notify & complete in S-EES executed ACR | Qualcomm Incorporated | imported from 3GU |
| S6‑202153 | Subscription service requirements | Samsung | imported from 3GU |
| S6‑202154 | Updates to EDGE-9 | Samsung | imported from 3GU |
| S6‑202155 | EHE representation | Samsung | imported from 3GU |
| S6‑202156 | EAS profile ID | Samsung | imported from 3GU |
| S6‑202157 | Handling app info optionality in Service provisioning | Samsung, Huawei, Intel, AT&T, Convida | imported from 3GU |
| S6‑202158 | Handling app info optionality in EAS discovery | Samsung, Huawei, Intel, AT&T, Convida | imported from 3GU |
| S6‑202159 | EAS discovery filters flag | Samsung | imported from 3GU |
| S6‑202160 | EES profile in service provisioning | Samsung | imported from 3GU |
| S6‑202161 | DNAIs | Samsung | imported from 3GU |
| S6‑202162 | Exposing UE location API to EEC | Samsung | imported from 3GU |
| S6‑202163 | Update to UE location API | Samsung | imported from 3GU |
| S6‑202164 | Terms for ACR | Samsung | imported from 3GU |
| S6‑202165 | Intra-EDN mobility | Samsung | imported from 3GU |
| S6‑202166 | EAS proxies in ACR | Samsung | imported from 3GU |
| S6‑202167 | ACR decision making | Samsung | imported from 3GU |
| S6‑202168 | Target EAS discovery | Samsung | imported from 3GU |
| S6‑202169 | Target EAS selelction | Samsung | imported from 3GU |
| S6‑202170 | Target EAS notification | Samsung | imported from 3GU |
| S6‑202171 | ENs related to EEC authentication and authorization | Samsung | imported from 3GU |
| S6‑202172 | Deployments in relation with CAPIF | Samsung | imported from 3GU |
| S6‑202173 | Presentation_of_TS23558_v120_for_approval | Samsung | imported from 3GU |
| S6‑202174 | Pseudo-CR on handling of EEC and AC caching of EAS endpoint information | Qualcomm Technologies Int | imported from 3GU |
| S6‑202175 | EDGEAPP Resolving Editor Note 8.4.2.1 | Convida Wireless LLC | imported from 3GU |
| S6‑202176 | 5GMARCH Resolving Editor Note KI 24 | Convida Wireless LLC | imported from 3GU |
| S6‑202177 | 5GMARCH Resolving Editor Notes solutions 9 10 20 | Convida Wireless LLC | imported from 3GU |
| S6‑202178 | 5GMARCH AC IDs | Convida Wireless LLC | imported from 3GU |
| S6‑202179 | FFApp solution 11 ENs and updates | Convida Wireless LLC | imported from 3GU |
| S6‑202180 | Update to relationship between ETSI MEC and 3GPP EDGEAPP | Huawei, Hisilicon | imported from 3GU |
| S6‑202181 | Target EAS discovery subscription-notification procedure | Huawei, Hisilicon | imported from 3GU |
| S6‑202182 | Supporting service provisioning over NAS | Huawei, Hisilicon | imported from 3GU |
| S6‑202183 | Providing EES DNAI to EEC | Huawei, Hisilicon | imported from 3GU |
| S6‑202184 | ACR when roaming to another PLMN | Huawei, Hisilicon | imported from 3GU |
| S6‑202185 | Service provisioning in roaming scenario | Huawei, Hisilicon | imported from 3GU |
| S6‑202186 | Trigger the EAS instantiation by EES | Huawei, Hisilicon | imported from 3GU |
| S6‑202187 | Automated ACR operations at edge enabler layer | Huawei, Hisilicon, CATT | imported from 3GU |
| S6‑202188 | Edge Enabler Server's capabilities exposure requirements | Huawei, Hisilicon | imported from 3GU |
| S6‑202189 | AF influence at ECS to enable efficient EES traffic routing | Huawei, Hisilicon | imported from 3GU |
| S6‑202190 | Change EES ID to EES endpoint in EEC Registration Procedure | Huawei, Hisilicon | imported from 3GU |
| S6‑202191 | Editorial changes to Application layer architecture | Huawei, Hisilicon | imported from 3GU |
| S6‑202192 | Resolve the EN on EEC registration optionality | Huawei, Hisilicon | imported from 3GU |
| S6‑202193 | User Plane Path Management enhancement | Huawei, Hisilicon | imported from 3GU |
| S6‑202194 | Temporary Groups formation (eSEAL) | Huawei, Hisilicon | imported from 3GU |
| S6‑202195 | Tracking UE and obtaining dynamic UE information | Huawei, Hisilicon, Samsung, AT&T | imported from 3GU |
| S6‑202196 | Network monitoring procedure enhancement | Huawei, Hisilicon | imported from 3GU |
| S6‑202197 | Relay the V2X traffic from Uu to PC5 broadcast | Huawei, Hisilicon | imported from 3GU |
| S6‑202198 | Discussion on integration of OPC UA with FFAPP | Huawei, Hisilicon | imported from 3GU |
| S6‑202199 | Integration of OPC UA with FFAPP | Huawei, Hisilicon | imported from 3GU |
| S6‑202200 | Revised SID Study on application layer support for UAS service | Huawei, Hisilicon | imported from 3GU |
| S6‑202201 | New WID for application layer support for UAS | Huawei, Hisilicon | imported from 3GU |
| S6‑202202 | Proposed skeleton for TS on Application layer support for UAS | Huawei, Hisilicon | imported from 3GU |
| S6‑202203 | Proposal for Introduction (UASAPP) | Huawei, Hisilicon | imported from 3GU |
| S6‑202204 | Proposal for Scope (UASAPP) | Huawei, Hisilicon | imported from 3GU |
| S6‑202205 | Proposal for Terms (UASAPP) | Huawei, Hisilicon | imported from 3GU |
| S6‑202206 | Relation between 3GPP EDGEAPP and ETSI MEC architectures | Huawei, Hisilicon | imported from 3GU |
| S6‑202207 | DNAI clarification and enhancements | Huawei, Hisilicon | imported from 3GU |
| S6‑202208 | New KI on supporting UAV and UAV Controller Pairing | Huawei, Hisilicon | imported from 3GU |
| S6‑202209 | New KI on Using MCVideo and MCData | Huawei, Hisilicon | imported from 3GU |
| S6‑202210 | New KI on Using applications deployed in edge data network | Huawei, Hisilicon | imported from 3GU |
| S6‑202211 | General requirements | Huawei, Hisilicon | imported from 3GU |
| S6‑202212 | Solution to KI#4 on Capability Exposure using CAPIF | Huawei, Hisilicon | imported from 3GU |
| S6‑202213 | Resolving editorial aspects | Huawei, Hisilicon | imported from 3GU |
| S6‑202214 | Presentation of Report to TSG SA: TR 23.755, Version 0.c.0 | Huawei, Hisilicon | imported from 3GU |
| S6‑202215 | [Draft] LS on Clarification on UAS requirements | Samsung | imported from 3GU |
| S6‑202216 | Correction to location notification to VAL server | Samsung, AT&T | imported from 3GU |
| S6‑202217 | Pseudo-CR on ENs remove without action | Samsung | imported from 3GU |
| S6‑202218 | Pseudo-CR on EN additional APIs | Samsung | imported from 3GU |
| S6‑202219 | Pseudo-CR on EN group update notification | Samsung | imported from 3GU |
| S6‑202220 | Pseudo-CR on EN gateway translation | Samsung | imported from 3GU |
| S6‑202221 | Pseudo-CR on target resolution and gateway selection | Samsung | imported from 3GU |
| S6‑202222 | Pseudo-CR on new key issue to support message communication | Samsung | imported from 3GU |
| S6‑202223 | Pseudo-CR on Update to Solution #21 | Samsung | imported from 3GU |
| S6‑202224 | Pseudo-CR on Key Issue - Detection of problematic UAV | Samsung | imported from 3GU |
| S6‑202225 | Pseudo-CR on Key issue on monitor flight path | Samsung | imported from 3GU |
| S6‑202226 | 3GPP TS 23.554 skeleton | China Mobile Com. Corporation | imported from 3GU |
| S6‑202227 | LS on Clarification on UAS requirements | SA6 | imported from 3GU |
| S6‑202228 | Clarifications for netwok monitoring information notification | CATT | imported from 3GU |
| S6‑202229 | Pseudo-CR on Aggregated New Message Request | one2many B.V. | imported from 3GU |
| S6‑202230 | Pseudo-CR on Evaluation in Solution 1 | one2many B.V. | imported from 3GU |
| S6‑202231 | Pseudo-CR on Resolution of EN in section 4.2.4 | one2many B.V. | imported from 3GU |
| S6‑202232 | Corrections about MSGin5G gateway | Huawei, Hisilicon | imported from 3GU |
| S6‑202233 | Pseudo-CR on key issue x: UAS Media session monitor and management | Tencent | imported from 3GU |
| S6‑202234 | Solution to Key issue #5.8: UAS Identification usage in application layer architecture | Tencent | imported from 3GU |
| S6‑202235 | Corrections on solution of MOAT messaging | Huawei, Hisilicon | imported from 3GU |
| S6‑202236 | Definition of non-3GPP device | Nokia, Nokia Shanghai Bell, BDBOS, UIC | imported from 3GU |
| S6‑202237 | Connection authorisation principles | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑202238 | Procedure refinements when the MC gateway UE performs connection authorization | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S6‑202239 | Procedure refinements when the MC server performs connection authorization | Nokia, Nokia Shanghai Bell, BDBOS | imported from 3GU |
| S6‑202240 | 5GMARCH Resolving Editor Note in KI 24 | Convida Wireless LLC | imported from 3GU |
| S6‑202241 | Clarification on ECS discovery | Samsung | imported from 3GU |
| S6‑202242 | 5GMARCH Resolving Editor Notes in solutions 9 10 20 | Convida Wireless LLC | imported from 3GU |
| S6‑202243 | ECS discovery for roaming UEs | Samsung | imported from 3GU |
| S6‑202244 | FFApp solution 11 ENs and updates | Convida Wireless LLC | imported from 3GU |
| S6‑202245 | pCR on service continuity | Samsung | imported from 3GU |
| S6‑202246 | Clarification on S-EAS decided ACR | Samsung | imported from 3GU |
| S6‑202247 | Clarification on S-EES executed ACR | Samsung | imported from 3GU |
| S6‑202248 | new SID on Enabler Layer Support Network Slice Capability Exposure for Vertical Application | China Mobile Com. Corporation | imported from 3GU |
| S6‑202249 | pCR on EEC executed ACR via T-EES | Samsung | imported from 3GU |
| S6‑202250 | Removal of duplicate MCData disposition notification information flow | Samsung Electronics Iberia SA | imported from 3GU |
| S6‑202251 | Depositing file contents distributed via FD communication using HTTP into MCData message store | Samsung Electronics Iberia SA, AT&T, FirstNet | imported from 3GU |
| S6‑202252 | Resolution of the EN on DNAI list as a TSA | Intel, Convida Wireless, Samsung, Apple | imported from 3GU |
| S6‑202253 | FS_5GMARCH on Registration | AT&T GNS Belgium SPRL | imported from 3GU |
| S6‑202254 | Distribution of file residing in MCData message store account of the MCData user | Samsung, AT&T, FirstNet | imported from 3GU |
| S6‑202255 | Update requirement for Edge-aware applications | Intel Deutschland GmbH | imported from 3GU |
| S6‑202256 | SEAL_Rel-16_Correction_Location notification to VAL server | Samsung, AT&T | imported from 3GU |
| S6‑202257 | 5GMARCH_EN additional APIs | Samsung | imported from 3GU |
| S6‑202258 | 5GMARCH_EN gateway translation | Samsung | imported from 3GU |
| S6‑202259 | 5GMARCH_TargetResolution_And_Gateway_Selection | Samsung, AT&T | imported from 3GU |
| S6‑202260 | FFAPP_KI_Messaging_Aspect | Samsung | imported from 3GU |
| S6‑202261 | Pseudo-CR on Update to Solution #21 | Samsung | imported from 3GU |
| S6‑202262 | Pseudo-CR on Key issue on monitor flight path | Samsung, InterDigital | imported from 3GU |
| S6‑202263 | EDGEAPP Working Assumption | SA6 Chairman | imported from 3GU |
| S6‑202264 | SA6 ToR Update | SA6 Leadership | imported from 3GU |
| S6‑202265 | Pseudo-CR on handling of EEC and AC caching of EAS endpoint information | Qualcomm Technologies Int | imported from 3GU |
| S6‑202266 | pCR on application context relocation vs. service continuity | Qualcomm Technologies Int | imported from 3GU |
| S6‑202267 | pCR on flows and IEs for notify & complete in EEC executed ACR | Qualcomm Technologies Int | imported from 3GU |
| S6‑202268 | pCR on flows and IEs for notify & complete in S-EES executed ACR | Qualcomm Incorporated | imported from 3GU |
| S6‑202269 | Clarify the functionality of FAE server for device monitoring in Solution #18 | ZTE Corporation | imported from 3GU |
| S6‑202270 | Add N6 routing info in EAS profile | Ericsson | imported from 3GU |
| S6‑202271 | EEC ID clarification | Ericsson | imported from 3GU |
| S6‑202272 | Solving EN for session with QoS API | Ericsson, Apple | imported from 3GU |
| S6‑202273 | EAS ID and EES ID | Ericsson | imported from 3GU |
| S6‑202274 | Support CAPIF | Ericsson | imported from 3GU |
| S6‑202275 | SEAL support for device onboarding and remote provisioning in an SNPN | Ericsson | imported from 3GU |
| S6‑202276 | Utilize unified 5GC location and report converged location | Ericsson, ZTE | imported from 3GU |
| S6‑202277 | Evaluation of solution #9 | Ericsson | imported from 3GU |
| S6‑202278 | Architecture for TSC services | Ericsson | imported from 3GU |
| S6‑202279 | AF influence in ACR event | Ericsson | imported from 3GU |
| S6‑202280 | Support local MBMS | Ericsson | imported from 3GU |
| S6‑202281 | support local MBMS | Ericsson, CATT | imported from 3GU |
| S6‑202282 | Handling app info optionality in Service provisioning | Samsung, Huawei, Intel, AT&T, Convida, Qualcomm | imported from 3GU |
| S6‑202283 | Handling app info optionality in EAS discovery | Samsung, Huawei, Intel, AT&T, Convida, Qualcomm | imported from 3GU |
| S6‑202284 | EES profile in service provisioning | Samsung | imported from 3GU |
| S6‑202285 | DNAIs | Samsung | imported from 3GU |
| S6‑202286 | Terms for ACR | Samsung, InterDigital | imported from 3GU |
| S6‑202287 | Target EAS selection | Samsung | imported from 3GU |
| S6‑202288 | Target EAS notification | Samsung | imported from 3GU |
| S6‑202289 | ENs related to EEC authentication and authorization | Samsung | imported from 3GU |
| S6‑202290 | Update a Note to avoid normative language | Sony | imported from 3GU |
| S6‑202291 | Removal of OSId from ACID | Sony | imported from 3GU |
| S6‑202292 | Pesudo-CR to remove EN in 6.11.1 | China Mobile Com. Corporation | imported from 3GU |
| S6‑202293 | Pesudo-CR on MGSin5G Group message without using SEAL | China Mobile Com. Corporation | imported from 3GU |
| S6‑202294 | Pseudo-CR on FS_5GMARCH overall Evaluation | China Mobile Com. Corporation | imported from 3GU |
| S6‑202295 | 3GPP TS 23.554 skeleton | China Mobile Com. Corporation | imported from 3GU |
| S6‑202296 | Clarifications for T8 interface | CATT | imported from 3GU |
| S6‑202297 | V2V communication mode switching | CATT | imported from 3GU |
| S6‑202298 | Support for local MBMS delivery | CATT | imported from 3GU |
| S6‑202299 | V2X UE registration enhancement | CATT | imported from 3GU |
| S6‑202300 | Clarifications for netwok monitoring information notification | CATT | imported from 3GU |
| S6‑202301 | CR on clarifications for T8 interface | CATT | imported from 3GU |
| S6‑202302 | UE-to-UE broadcast/groupcast configuration by VAE layer | Lenovo, Motorola Mobility | imported from 3GU |
| S6‑202303 | Network slice re-mapping for V2X applications | Lenovo, Motorola Mobility | imported from 3GU |
| S6‑202304 | Network slice adaptation for VAL applications | Lenovo, Motorola Mobility | imported from 3GU |
| S6‑202305 | Scope text restructure | The Police of the Netherlands | imported from 3GU |
| S6‑202306 | Cover sheet Presentation of TR 23.783 to SA for information | The Police of the Netherlands | imported from 3GU |
| S6‑202307 | Removal of empty clause 5, renumbering of other subclauses | The Police of the Netherlands | imported from 3GU |
| S6‑202308 | Pseudo-CR on MCOver5GS – use of 5GS by the MC functional | Union Inter. Chemins de Fer | imported from 3GU |
| S6‑202309 | Pseudo-CR on MCOver5GS - 5GS QoS handling | Union Inter. Chemins de Fer | imported from 3GU |
| S6‑202310 | Pseudo-CR on TR 23.783 key issue 10 support of low latency requirements | UIC, Kontron Transportation France | imported from 3GU |
| S6‑202311 | Update to relationship between ETSI MEC and 3GPP EDGEAPP | Huawei, Hisilicon | imported from 3GU |
| S6‑202312 | Target EAS discovery subscription-notification procedure | Huawei, Hisilicon | imported from 3GU |
| S6‑202313 | Trigger the EAS instantiation by EES | Huawei, Hisilicon, Samsung, InterDigital | imported from 3GU |
| S6‑202314 | Atomic ACR operations at edge enabler layer | Huawei, Hisilicon, CATT, China Mobile, TD Tech | imported from 3GU |
| S6‑202315 | AF influence at ECS to enable efficient EES traffic routing | Huawei, Hisilicon | imported from 3GU |
| S6‑202316 | Change EES ID to EES endpoint in EEC Registration Procedure | Huawei, Hisilicon | imported from 3GU |
| S6‑202317 | Resolve the EN on EEC registration optionality | Huawei, Hisilicon, Convida Wireless LLC | imported from 3GU |
| S6‑202318 | Network monitoring procedure enhancement | Huawei, Hisilicon | imported from 3GU |
| S6‑202319 | Relay the V2X traffic from Uu to PC5 broadcast | Huawei, Hisilicon | imported from 3GU |
| S6‑202320 | Revised SID Study on application layer support for UAS service | Huawei, Hisilicon | imported from 3GU |
| S6‑202321 | New WID for application layer support for UAS | Huawei, Hisilicon | imported from 3GU |
| S6‑202322 | Proposed skeleton for TS on Application layer support for UAS | Huawei, Hisilicon | imported from 3GU |
| S6‑202323 | Proposal for Introduction (UASAPP) | Huawei, Hisilicon | imported from 3GU |
| S6‑202324 | Proposal for Terms (UASAPP) | Huawei, Hisilicon | imported from 3GU |
| S6‑202325 | Relation between 3GPP EDGEAPP and ETSI MEC architectures | Huawei, Hisilicon | imported from 3GU |
| S6‑202326 | DNAI clarification and enhancements | Huawei, Hisilicon | imported from 3GU |
| S6‑202327 | New KI on supporting UAV and UAV Controller Pairing | Huawei, Hisilicon | imported from 3GU |
| S6‑202328 | New KI on Using applications deployed in edge data network | Huawei, Hisilicon | imported from 3GU |
| S6‑202329 | General requirements | Huawei, Hisilicon | imported from 3GU |
| S6‑202330 | Solution to KI#4 on Capability Exposure using CAPIF | Huawei, Hisilicon | imported from 3GU |
| S6‑202331 | Presentation of Report to TSG SA: TR 23.755, Version 0.c.0 | Huawei, Hisilicon | imported from 3GU |
| S6‑202332 | SA6#40-e Work Plan discussion | SA6 Chair | imported from 3GU |
| S6‑202333 | EHE representation | Samsung | imported from 3GU |
| S6‑202334 | EES profile in service provisioning | Samsung, Huawei | imported from 3GU |
| S6‑202335 | Pseudo-CR on handling of EEC and AC caching of EAS endpoint information | Qualcomm Technologies Int | imported from 3GU |
| S6‑202336 | AF influence in ACR event | Ericsson, Huawei | imported from 3GU |
| S6‑202337 | Support more UE IDs in QoS exposure | Ericsson | imported from 3GU |
| S6‑202338 | pCR on service continuity | Samsung | imported from 3GU |
| S6‑202339 | Clarification on S-EES executed ACR | Samsung, AT&T | imported from 3GU |
| S6‑202340 | pCR on EEC executed ACR via T-EES | Samsung | imported from 3GU |
| S6‑202341 | Deployments in relation with CAPIF | Samsung, AT&T | imported from 3GU |
| S6‑202342 | Support local MBMS | Ericsson | imported from 3GU |
| S6‑202343 | support local MBMS | Ericsson, CATT | imported from 3GU |
| S6‑202344 | UE-to-UE broadcast/groupcast configuration by VAE layer | Lenovo, Motorola Mobility | imported from 3GU |
| S6‑202345 | Network monitoring procedure enhancement | Huawei, Hisilicon | imported from 3GU |
| S6‑202346 | Clarifications for netwok monitoring information notification | CATT | imported from 3GU |
| S6‑202347 | Clarify the functionality of FAE server for device monitoring in Solution #18 | ZTE Corporation | imported from 3GU |
| S6‑202348 | Pseudo-CR on Update to Solution #21 | Samsung | imported from 3GU |
| S6‑202349 | Pseudo-CR on Key issue on monitor flight path | Samsung, InterDigital | imported from 3GU |
| S6‑202350 | Solution to KI#4 on Capability Exposure using CAPIF | Huawei, Hisilicon | imported from 3GU |
| S6‑202351 | 5GMARCH Resolving Editor Notes in solutions 9 10 20 | Convida Wireless LLC | imported from 3GU |
| S6‑202352 | Pseudo-CR on Aggregated New Message Request | one2many B.V. | imported from 3GU |
| S6‑202353 | Network slice adaptation for VAL applications | Lenovo, Motorola Mobility | imported from 3GU |
| S6‑202354 | Proposal for Introduction (UASAPP) | Huawei, Hisilicon | imported from 3GU |
| S6‑202355 | Relation between 3GPP EDGEAPP and ETSI MEC architectures | Huawei, Hisilicon | imported from 3GU |
| S6‑202356 | Update to relationship between ETSI MEC and 3GPP EDGEAPP | Huawei, Hisilicon, Interdigital, Nokia | imported from 3GU |
| S6‑202357 | V2X UE registration enhancement | CATT | imported from 3GU |
| S6‑202358 | MSGin5G way forward | Convida | imported from 3GU |
| S6‑202359 | FS_5GMARCH on Registration | AT&T GNS Belgium SPRL | imported from 3GU |
| S6‑202360 | Conclusion | Huawei, Hisilicon | imported from 3GU |
| S6‑202361 | pCR on flows and IEs for notify & complete in S-EES executed ACR | Qualcomm Incorporated | imported from 3GU |
| S6‑202362 | Temporary Groups formation (eSEAL) | Huawei, Hisilicon | imported from 3GU |
| S6‑202363 | SA6 1H2021 Meeting Calendar | SA6 Chairman | imported from 3GU |
page generated from database: 2024-07-20 12:15:34