3GPP TDocs (written contributions) at meeting
Meeting: S6-34 - 2019-11-11 to 2019-11-15, Reno, Nevada
meeting id: S6-34 (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
S6‑192005 | SA6 Meeting 34 Agenda | SA6 Chairman | imported from 3GU |
S6‑192006 | SA6 Meeting 33 Report | MCC | imported from 3GU |
S6‑192007 | SA6 Meeting #34 - Agenda with Tdocs allocation after submission deadline | SA6 Chairman | imported from 3GU |
S6‑192008 | SA6 Meeting #34 - Agenda with Tdocs allocation at start of the meeting | SA6 Chairman | imported from 3GU |
S6‑192009 | SA6 Meeting #34 - Chairman's notes at end of the meeting | SA6 Chairman | imported from 3GU |
S6‑192010 | NGMN 5G End-to-End Architecture Framework | NGMN Alliance Project E2E Architecture Framework | imported from 3GU |
S6‑192011 | LS reply to A-190116 3GPP SA6 application layer support for V2X services | 5GAA WG2 | imported from 3GU |
S6‑192012 | LS on clarifications regarding V2XAPP services | CT3 | imported from 3GU |
S6‑192013 | LS on O-RAN Alliance & 3GPP Coordination on O-RAN Alliance Outputs | O-RAN Alliance | imported from 3GU |
S6‑192014 | LS on SG11 activities related to improvement of the SS7 security including for digital financial services | ITU SG11 | imported from 3GU |
S6‑192015 | Reply LS to “O-RAN Alliance & 3GPP Coordination on O-RAN Alliance Outputs” | SA | imported from 3GU |
S6‑192016 | Editorial modifications | one2many B.V. | imported from 3GU |
S6‑192017 | Result element missing | one2many B.V. | imported from 3GU |
S6‑192018 | Anonymous requests and notifications | one2many B.V. | imported from 3GU |
S6‑192019 | No multicast resource management in 5GS | one2many B.V. | imported from 3GU |
S6‑192020 | LS on how the IWF obtains key material for interworking group and private communications | CT1 | imported from 3GU |
S6‑192021 | Pseudo-CR on proposed resolution of Editor’s note in KI-1 | Vodafone | imported from 3GU |
S6‑192022 | Pseudo-CR on proposed resolution of Editor’s note in KI-2 | Vodafone | imported from 3GU |
S6‑192023 | LS on clarifications regarding SEAL services | CT3 | imported from 3GU |
S6‑192024 | Mention of SA3 responsibility in a published TS is not relevant. | one2many B.V. | imported from 3GU |
S6‑192025 | Resource management over MB2 and or xMB | one2many B.V. | imported from 3GU |
S6‑192026 | Corrections to preconfigured regroup procedures | FirstNet | imported from 3GU |
S6‑192027 | Corrections to preconfigured regroup procedures | FirstNet | imported from 3GU |
S6‑192028 | Addition of preconfigured regroup procedures | FirstNet | imported from 3GU |
S6‑192029 | pCR on Scope adjustments | Intel Deutschland GmbH | imported from 3GU |
S6‑192030 | pCR on Abbreviations | Intel Deutschland GmbH | imported from 3GU |
S6‑192031 | pCR on Solution for EEC request for EAS provisioning | Intel Deutschland GmbH | imported from 3GU |
S6‑192032 | pCR on Solution for EEC subscription for EAS provisioning events | Intel Deutschland GmbH | imported from 3GU |
S6‑192033 | pCR on Solution for Application Client installation | Intel Deutschland GmbH | imported from 3GU |
S6‑192034 | pCR on Solution for Application Client la | Intel Deutschland GmbH | imported from 3GU |
S6‑192035 | pCR on Solution for EEC Notification to Application Clients | Intel Deutschland GmbH | imported from 3GU |
S6‑192036 | pCR on Solution for EAS change event to Application Clients | Intel Deutschland GmbH | imported from 3GU |
S6‑192037 | Pseudo-CR on editorial edits | one2many B.V. | imported from 3GU |
S6‑192038 | Pseudo-CR on Scenario 2 | one2many B.V. | imported from 3GU |
S6‑192039 | Communication urgency handling in the MC service system | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192040 | Functional alias in group call interconnect and interworking | Kapsch CarrierCom France S.A.S | imported from 3GU |
S6‑192041 | Handling origination side of functional alias for group calls | Kapsch CarrierCom France S.A.S | imported from 3GU |
S6‑192042 | Include functional alias in group call interconnect | Kapsch CarrierCom France S.A.S | imported from 3GU |
S6‑192043 | Add enhancements for interworking of MCPTT group calls with GSM-R | Kapsch CarrierCom | imported from 3GU |
S6‑192044 | 23745-FS_FFAPP-Discussion on FFAPP work in SA6 | ZTE Corporation | imported from 3GU |
S6‑192045 | 23745-FS_FFAPP-Key issue-local approach for the communication service on the network side | ZTE Corporation | imported from 3GU |
S6‑192046 | 23745-FS_FFAPP-FF application layer functional model | ZTE Corporation | imported from 3GU |
S6‑192047 | Single EDNCS per Application Client | Sony | imported from 3GU |
S6‑192048 | Introducing descriptive text describing the urgency handling in the MC service system | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192049 | Requested Priority in IP connectivity point to point communication | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192050 | Enhancing SDS data requests with application priority capabilities in on-network mode | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192051 | Enhancing FD data requests with application priority capabilities in on-network mode | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192052 | Priority of the user for initiating/receiving communications | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192053 | Priority of the user for initiating/receiving calls | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192054 | Priority of the user for initiating/receiving calls | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192055 | Notifications-based solution for KI #1 in 23.774 | AT&T | imported from 3GU |
S6‑192056 | Resource optimized group call mode for KI #2 in 23.774 | AT&T | imported from 3GU |
S6‑192057 | Handling large number of UEs in a cell for KI #3 in 23.774 | AT&T | imported from 3GU |
S6‑192058 | LS on further aspects of Mission Critical Services over 5MBS | AT&T | imported from 3GU |
S6‑192059 | KI#3: Solution on network assisted positioning for USS/UTM | InterDigital | imported from 3GU |
S6‑192060 | KI#3: Solution on network assisted positioning for UAV | InterDigital | imported from 3GU |
S6‑192061 | FS_EDGEAPP Solutions 8 and 17 cleanup and KI2 evaluation | Convida Wireless | imported from 3GU |
S6‑192062 | FS_EDGEAPP Solution 12 cleanup KI3 eval | Convida Wireless | imported from 3GU |
S6‑192063 | FS_EDGEAPP KI4 evaluation | Convida Wireless | imported from 3GU |
S6‑192064 | FS_EDGEAPP New solution for KI#5 | Convida Wireless | imported from 3GU |
S6‑192065 | FS_EDGEAPP Solution 2 cleanup KI7 eval | Convida Wireless | imported from 3GU |
S6‑192066 | FS_EDGEAPP Solutions 20 and 21 cleanup and KI9 eval | Convida Wireless | imported from 3GU |
S6‑192067 | FS_EDGEAPP deployment figure updates | Convida Wireless | imported from 3GU |
S6‑192068 | New MCData WID for R-17 | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑192069 | Report on SA6 related topics at SA#85 | SA6 Chairman | imported from 3GU |
S6‑192070 | Pseudo-CR on solution 14 - functional model enhancement | BDBOS | imported from 3GU |
S6‑192071 | Pseudo-CR on solution sharing location information on interconnected MC systems - configuration | BDBOS | imported from 3GU |
S6‑192072 | Discussion on common service core configuration | BDBOS | imported from 3GU |
S6‑192073 | Pseudo-CR on solution sharing location information on interconnected MC systems - authorization | BDBOS | imported from 3GU |
S6‑192074 | Pseudo-CR on overall evaluation | BDBOS | imported from 3GU |
S6‑192075 | Pseudo-CR on solution past location service | BDBOS | imported from 3GU |
S6‑192076 | Discussion on sharing location information in off-network and IOPS mode | BDBOS | imported from 3GU |
S6‑192077 | Pseudo-CR on solution for off-network and IOPS mode | BDBOS | imported from 3GU |
S6‑192078 | CR Message Delivery | Ericsson GmbH, Eurolab | imported from 3GU |
S6‑192079 | LS reply to S6-192011 on tele-operated driving | Ericsson GmbH, Eurolab | imported from 3GU |
S6‑192080 | Key Issue and Solution for Security Policy Management for 5G Edge Applications | Alibaba Group | imported from 3GU |
S6‑192081 | Status of eMONASTERY2 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192082 | (e)MONASTERY requirements and status in stage 2 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192083 | Correcting stage 1 reference on maximum number of simultaneously received group calls | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192084 | Corrections on functional alias to group binding | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192085 | Resolving EN on functional alias to group binding impacts | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192086 | Functional alias used for private communications | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192087 | Editorial changes related to functional alias interworking | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192088 | Receiving a private call from any other user | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192089 | Receiving a private call from any other user | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192090 | Revised WID on Enhancements to Application Architecture for the Mobile Communication System for Railways Phase 2 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192091 | Requirement clean up | Ericsson | imported from 3GU |
S6‑192092 | pCR 23.758 – updating the architecture | Ericsson | imported from 3GU |
S6‑192093 | pCR 23.758 – New solution | Ericsson | imported from 3GU |
S6‑192094 | Pseudo-CR on Solution #16 Evaluation | Samsung | imported from 3GU |
S6‑192095 | Pseudo-CR on Solution #21 Evaluation | Samsung | imported from 3GU |
S6‑192096 | Architectural requirements on the IP connectivity functionality | Ericsson | imported from 3GU |
S6‑192097 | Key issue for UAV flight authorisation | Motorola Mobility, Lenovo | imported from 3GU |
S6‑192098 | Solution for UAV flight authorisation | Motorola Mobility, Lenovo | imported from 3GU |
S6‑192099 | Architecture Update with new Reference Point | Motorola Mobility, Lenovo | imported from 3GU |
S6‑192100 | General user authentication in IOPS | Ericsson | imported from 3GU |
S6‑192101 | IOPS identities | Ericsson | imported from 3GU |
S6‑192102 | IOPS discovery for IP connectivity functionality | Ericsson | imported from 3GU |
S6‑192103 | Pseudo-CR on solution to Key Issue 12 (lifecycle management) | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192104 | IOPS subscription and notification for IP connectivity functionality | Ericsson | imported from 3GU |
S6‑192105 | IOPS announcement for IP connectivity functionality | Ericsson | imported from 3GU |
S6‑192106 | Use of MBMS transmissions in IOPS | Ericsson | imported from 3GU |
S6‑192107 | MCPTT group call in IOPS – Call setup based on the IP connectivity functionality | Ericsson | imported from 3GU |
S6‑192108 | MCPTT private call in IOPS – Call setup based on the IP connectivity functionality | Ericsson | imported from 3GU |
S6‑192109 | Pseudo-CR on solution to Key Issues 9 with an alternative flow | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192110 | Key Issue – alternative transport at the Edge Data Network | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192111 | Pseudo-CR - evaluation and conclusion on KI #9 | Samsung | imported from 3GU |
S6‑192112 | Architecture clean-up | Samsung | imported from 3GU |
S6‑192113 | Solution 2 update and conclusion for KI#1 | Samsung | imported from 3GU |
S6‑192114 | Solution 6 update and conclusion for KI#6 | Samsung | imported from 3GU |
S6‑192115 | Deployment options clean-up | Samsung | imported from 3GU |
S6‑192116 | Application ID clarification | Samsung | imported from 3GU |
S6‑192117 | New solution X - detailed examples | Ericsson | imported from 3GU |
S6‑192118 | Update to solution evaluation table | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192119 | SA6 future meetings 2021 | SA6 Chairman | imported from 3GU |
S6‑192120 | Alternative transport for hight throughput and low latency communications | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192121 | Removal of temporary regroup procedures | FirstNet | imported from 3GU |
S6‑192122 | EAS discovery using DNS | Samsung | imported from 3GU |
S6‑192123 | Additional MCData service requirement | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑192124 | Update and Evaluation for Solution #11 | Vodafone | imported from 3GU |
S6‑192125 | 5G_MARCH Framework for MSGin5G service architecture | Convida Wireless | imported from 3GU |
S6‑192126 | FS_5GMARCH KI3 solution | Convida Wireless | imported from 3GU |
S6‑192127 | FS_5GMARCH KI4 solution | Convida Wireless | imported from 3GU |
S6‑192128 | Alignment on MCX emergency alert procedures | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑192129 | Alignment on MCX emergency alert procedures | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑192130 | Alignment on MCX emergency alert procedures | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑192131 | Alignment on MCX emergency alert procedures | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑192132 | Deployment Options for EDNCS | Sony | imported from 3GU |
S6‑192133 | Update of Key Issue 6 | Sony | imported from 3GU |
S6‑192134 | Update of Key Issue 9 | Sony | imported from 3GU |
S6‑192135 | pCR on Evaluation of Solution #1 | Intel Deutschland GmbH | imported from 3GU |
S6‑192136 | pCR on Evaluation of Solution #2 | Intel Deutschland GmbH | imported from 3GU |
S6‑192137 | pCR on Evaluation of Solution #3 | Intel Deutschland GmbH | imported from 3GU |
S6‑192138 | pCR on Evaluation of Solution #5 | Intel Deutschland GmbH | imported from 3GU |
S6‑192139 | pCR on Evaluation of Solution #7 | Intel Deutschland GmbH | imported from 3GU |
S6‑192140 | pCR on Evaluation of Solution #8 | Intel Deutschland GmbH | imported from 3GU |
S6‑192141 | File repair with the content storage function | ENENSYS | imported from 3GU |
S6‑192142 | Update of Solution 1 | Sony | imported from 3GU |
S6‑192143 | Floor control for MCPTT in IOPS | Ericsson | imported from 3GU |
S6‑192144 | Update of Solution 2 | Sony | imported from 3GU |
S6‑192145 | EDGE_Centralized_CAPIF | Samsung | imported from 3GU |
S6‑192146 | EDGE_EAS_enablement_using_CAPIF | Samsung | imported from 3GU |
S6‑192147 | EDGE_Conclusion on KI5 | Samsung | imported from 3GU |
S6‑192148 | SEAL APIs corrections | Samsung | imported from 3GU |
S6‑192149 | Reply LS on clarifications regarding SEAL services | Samsung | imported from 3GU |
S6‑192150 | 5GMARCH_KI8_Group_Management | Samsung | imported from 3GU |
S6‑192151 | Clarifications for location management | CATT | imported from 3GU |
S6‑192152 | Pseudo-CR on architecture update | CATT | imported from 3GU |
S6‑192153 | Pseudo-CR on solution of initial provisioning with authorization | CATT | imported from 3GU |
S6‑192154 | Pseudo-CR on key issue update on resource control | CATT | imported from 3GU |
S6‑192155 | Pseudo-CR on key issue update of ProSe | CATT | imported from 3GU |
S6‑192156 | Abbreviations | Samsung Electronics | imported from 3GU |
S6‑192157 | Distributing EAS information | Samsung Electronics | imported from 3GU |
S6‑192158 | Overall evaluations | Samsung Electronics | imported from 3GU |
S6‑192159 | Conclusion on Architecture | Samsung Electronics | imported from 3GU |
S6‑192160 | Conclusions | Samsung Electronics | imported from 3GU |
S6‑192161 | Conclusion on KI#2 | Samsung Electronics | imported from 3GU |
S6‑192162 | Conclusion on KI#4 | Samsung Electronics | imported from 3GU |
S6‑192163 | Conclusion on KI#10 | Samsung Electronics | imported from 3GU |
S6‑192164 | Coversheet_TR 23.758 Approval | Samsung Electronics | imported from 3GU |
S6‑192165 | New WID EDGEAPP | Samsung Electronics | imported from 3GU |
S6‑192166 | EES_Cleanup_KI | QUALCOMM JAPAN LLC. | imported from 3GU |
S6‑192167 | EES_Cleanup_Solution | QUALCOMM JAPAN LLC. | imported from 3GU |
S6‑192168 | EES_Cleanup_SolutionEval | QUALCOMM JAPAN LLC. | imported from 3GU |
S6‑192169 | Discovery based on Route | QUALCOMM JAPAN LLC. | imported from 3GU |
S6‑192170 | Edge Capability Discovery | QUALCOMM JAPAN LLC. | imported from 3GU |
S6‑192171 | Operation_Technology_Integration_KI | QUALCOMM JAPAN LLC. | imported from 3GU |
S6‑192172 | Key issue on QoS coordination | Huawei, Hisilicon | imported from 3GU |
S6‑192173 | Solution to establish communications with FFAPP requirements | Huawei, Hisilicon | imported from 3GU |
S6‑192174 | Update of Key Issue #4 on TSN supporting | Huawei, Hisilicon | imported from 3GU |
S6‑192175 | Update to deployment option 4 | Huawei, Hisilicon | imported from 3GU |
S6‑192176 | Solution to Key issue#1 on EAS discovery from EDNCS | Huawei, Hisilicon | imported from 3GU |
S6‑192177 | Solution to KI5 with enhancement to CAPIF | Huawei, Hisilicon | imported from 3GU |
S6‑192178 | Solution 14 evaluation | Huawei, Hisilicon | imported from 3GU |
S6‑192179 | Solution 18 evaluation | Huawei, Hisilicon | imported from 3GU |
S6‑192180 | Correction on usage of service API information in access control message | Huawei, Hisilicon | imported from 3GU |
S6‑192181 | Architecture for UAS application layer | Huawei, Hisilicon | imported from 3GU |
S6‑192182 | Update to location configuration procedure | Huawei, Hisilicon | imported from 3GU |
S6‑192183 | Update API names | Huawei, Hisilicon | imported from 3GU |
S6‑192184 | Update to uplink message delivery procedure | Huawei, Hisilicon | imported from 3GU |
S6‑192185 | Reply LS on clarifications regarding V2XAPP services | Huawei, Hisilicon | imported from 3GU |
S6‑192186 | Solution on PC5 QoS aspects | Huawei, Hisilicon | imported from 3GU |
S6‑192187 | LS reply from 3GPP SA5 to NGMN on 5G End-to-End Architecture Framework | SA5 | imported from 3GU |
S6‑192188 | Update to solution#10 | Huawei, Hisilicon | imported from 3GU |
S6‑192189 | LS on Application Architecture for enabling Edge Applications | Huawei, Hisilicon | imported from 3GU |
S6‑192190 | Pseudo-CR on Key Issue and Solution for Security Policy Management for 5G Edge Applications | Alibaba Group | imported from 3GU |
S6‑192191 | New solution X – detailed examples | Ericsson | imported from 3GU |
S6‑192192 | LS on Testing and Certification of 3GPP Mission Critical features A GCF-TCCA Joint Approach to Develop and Manage MC Certification | TCCA | imported from 3GU |
S6‑192193 | UE Authentication and UEId | AT&T | imported from 3GU |
S6‑192194 | Reply LS on how the IWF obtains key material for interworking group and private communications | SA6 | imported from 3GU |
S6‑192195 | CR Message Delivery | Ericsson GmbH, Eurolab | imported from 3GU |
S6‑192196 | Update to uplink message delivery procedure | Huawei, Hisilicon, Ericsson | imported from 3GU |
S6‑192197 | Corrections to naming and other fixes | one2many B.V. | imported from 3GU |
S6‑192198 | Result element missing | one2many B.V. | imported from 3GU |
S6‑192199 | Anonymous requests | one2many B.V. | imported from 3GU |
S6‑192200 | No multicast resource management in 5GS | one2many B.V. | imported from 3GU |
S6‑192201 | Mention of SA3 responsibility in a published TS is not relevant. | one2many B.V. | imported from 3GU |
S6‑192202 | SEAL APIs corrections | Samsung | imported from 3GU |
S6‑192203 | Reply LS on clarifications regarding SEAL services | Samsung | imported from 3GU |
S6‑192204 | Update to location configuration procedure | Huawei, Hisilicon | imported from 3GU |
S6‑192205 | Corrections on functional alias to group binding | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192206 | Handling origination side of functional alias for group calls | Kapsch CarrierCom France S.A.S | imported from 3GU |
S6‑192207 | Add missing server to server information flows for group calls | Kapsch CarrierCom France S.A.S | imported from 3GU |
S6‑192208 | Add enhancements for interworking of MCPTT group calls with GSM-R | Kapsch CarrierCom | imported from 3GU |
S6‑192209 | Text improvements related to functional alias interworking | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192210 | Introducing descriptive text describing the urgency handling in the MC service system | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192211 | Requested Priority in IP connectivity point to point communication | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192212 | Enhancing SDS data requests with application priority capabilities in on-network mode | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192213 | Enhancing FD data requests with application priority capabilities in on-network mode | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192214 | Clarifications for location management | CATT | imported from 3GU |
S6‑192215 | Corrections to preconfigured regroup procedures | FirstNet | imported from 3GU |
S6‑192216 | Corrections to preconfigured regroup procedures | FirstNet | imported from 3GU |
S6‑192217 | Removal of temporary regroup procedures | FirstNet | imported from 3GU |
S6‑192218 | File repair with the content storage function | ENENSYS | imported from 3GU |
S6‑192219 | Corrections to preconfigured regroup procedures – alternative proposal | Motorola Solutions | imported from 3GU |
S6‑192220 | Receiving a private call from any other user | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192221 | Receiving a private call from any other user | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192222 | Priority of the user | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192223 | Priority of the user for initiating/receiving calls | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192224 | Priority of the user for initiating/receiving calls | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192225 | Requested Priority in IP connectivity point to point communication | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192226 | Pseudo-CR on General user authentication in IOPS | Ericsson | imported from 3GU |
S6‑192227 | Pseudo-CR on Architectural requirements on the IP connectivity functionality support | Ericsson | imported from 3GU |
S6‑192228 | Pseudo-CR on IOPS identities | Ericsson | imported from 3GU |
S6‑192229 | Pseudo-CR on IOPS discovery for the IP connectivity functionality | Ericsson | imported from 3GU |
S6‑192230 | Pseudo-CR on IOPS subscription and notification for the IP connectivity functionality | Ericsson | imported from 3GU |
S6‑192231 | Pseudo-CR on Use of MBMS transmissions in IOPS | Ericsson | imported from 3GU |
S6‑192232 | Pseudo-CR on MCPTT group call in IOPS – Call setup based on the IP connectivity functionality | Ericsson | imported from 3GU |
S6‑192233 | Pseudo-CR on MCPTT private call in IOPS – Call setup based on the IP connectivity functionality | Ericsson | imported from 3GU |
S6‑192234 | Pseudo-CR on Floor control for MCPTT in IOPS (IP connectivity functionality) | Ericsson | imported from 3GU |
S6‑192235 | Addition of preconfigured regroup procedures | FirstNet | imported from 3GU |
S6‑192236 | Alignment on MCX emergency alert procedures | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑192237 | Alignment on MCX emergency alert procedures | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑192238 | Alignment on MCX emergency alert procedures | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑192239 | Pseudo-CR on solution 14 - functional model enhancement | BDBOS | imported from 3GU |
S6‑192240 | Pseudo-CR on solution sharing location information on interconnected MC systems - configuration | BDBOS | imported from 3GU |
S6‑192241 | Pseudo-CR on solution sharing location information on interconnected MC systems - authorization | BDBOS | imported from 3GU |
S6‑192242 | Pseudo-CR on overall evaluation | BDBOS | imported from 3GU |
S6‑192243 | Pseudo-CR on solution past location service | BDBOS | imported from 3GU |
S6‑192244 | Pseudo-CR on solution for off-network mode | BDBOS | imported from 3GU |
S6‑192245 | Pseudo-CR on key issue update on resource control | CATT | imported from 3GU |
S6‑192246 | Pseudo-CR on key issue update of ProSe | CATT | imported from 3GU |
S6‑192247 | Notifications-based solution for KI #1 in 23.774 | AT&T | imported from 3GU |
S6‑192248 | Resource optimized group call mode for KI #2 in 23.774 | AT&T | imported from 3GU |
S6‑192249 | Handling large number of UEs in a cell for KI #3 in 23.774 | AT&T | imported from 3GU |
S6‑192250 | Pseudo-CR on Scenario 2 | one2many B.V. | imported from 3GU |
S6‑192251 | Framework for MSGin5G Service Architecture | Convida Wireless | imported from 3GU |
S6‑192252 | New Solution for Key Issue #3 | Convida Wireless | imported from 3GU |
S6‑192253 | Pseudo-CR on 5GMARCH KI8 group management | Samsung | imported from 3GU |
S6‑192254 | Key issue for UAV flight authorisation | Motorola Mobility, Lenovo | imported from 3GU |
S6‑192255 | KI#3: Solution on network assisted positioning for USS/UTM | InterDigital | imported from 3GU |
S6‑192256 | Architecture for UAS application layer | Huawei, Hisilicon | imported from 3GU |
S6‑192257 | Solution on PC5 QoS aspects | Huawei, Hisilicon | imported from 3GU |
S6‑192258 | Discovery of suitable Edge Application Server based on underlying Edge Data Network performance | Vodafone, Convida Wireless LLC | imported from 3GU |
S6‑192259 | Key issue - local approach for the communication service on the network side | ZTE Corporation | imported from 3GU |
S6‑192260 | FF application layer functional model | ZTE Corporation | imported from 3GU |
S6‑192261 | Key issue on QoS coordination | Huawei, Hisilicon | imported from 3GU |
S6‑192262 | Solution to establish communications with FFAPP requirements | Huawei, Hisilicon | imported from 3GU |
S6‑192263 | Update of Key Issue #4 on TSN supporting | Huawei, Hisilicon | imported from 3GU |
S6‑192264 | Revised WID on Enhancements to Application Architecture for the Mobile Communication System for Railways Phase 2 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192265 | pCR on Scope adjustments | Intel Deutschland GmbH | imported from 3GU |
S6‑192266 | pCR on Abbreviations | Intel Deutschland GmbH, Samsung Electronics | imported from 3GU |
S6‑192267 | Requirement clean up | Ericsson | imported from 3GU |
S6‑192268 | Architecture Update with new Reference Point | Motorola Mobility, Lenovo | imported from 3GU |
S6‑192269 | Architecture clean-up | Samsung | imported from 3GU |
S6‑192270 | Pseudo-CR on architecture update | CATT | imported from 3GU |
S6‑192271 | Pseudo-CR on proposed resolution of Editor’s note in KI-2 | Vodafone | imported from 3GU |
S6‑192272 | Pseudo-CR on solution of initial provisioning with authorization | CATT | imported from 3GU |
S6‑192273 | Pseudo-CR on proposed resolution of Editor’s note in KI-1 | Vodafone | imported from 3GU |
S6‑192274 | UE Authentication and UEId | AT&T | imported from 3GU |
S6‑192275 | Pseudo-CR on Evaluation of Solution #2 | Intel Deutschland GmbH | imported from 3GU |
S6‑192276 | Pseudo-CR on proposed resolution of Editor’s note in KI-2 | Vodafone | imported from 3GU |
S6‑192277 | Solution 2 update and conclusion for Key Issue #1 and #7 | Samsung | imported from 3GU |
S6‑192278 | Pseudo-CR on Evaluation of Solution #3 | Intel Deutschland GmbH | imported from 3GU |
S6‑192279 | pCR on Evaluation of Solution #8 | Intel Deutschland GmbH | imported from 3GU |
S6‑192280 | Solutions 8 and 17 clean-up and conclusion to KI#2 Edge Data Network discovery and registration | Convida Wireless | imported from 3GU |
S6‑192281 | Pseudo-CR on EAS enablement using CAPIF | Samsung | imported from 3GU |
S6‑192282 | Solution clean-up and conclusion for KI#3 Edge Application Server enablement on the Edge Hosting Environment | Convida Wireless | imported from 3GU |
S6‑192283 | Edge Application Server Discovery based on Route | QUALCOMM JAPAN LLC. | imported from 3GU |
S6‑192284 | Edge Computing platform capability discovery | QUALCOMM JAPAN LLC. | imported from 3GU |
S6‑192285 | pCR 23.758 – New solution | Ericsson | imported from 3GU |
S6‑192286 | Solution to Key issue#4 on EAS discovery from EDNCS | Huawei, Hisilicon | imported from 3GU |
S6‑192287 | EAS discovery using DNS | Samsung | imported from 3GU |
S6‑192288 | Pseudo-CR on Evaluation of Solution #1 | Intel Deutschland GmbH | imported from 3GU |
S6‑192289 | Solution Evaluation for Key Issue#4 Edge Application Server Discovery | Convida Wireless | imported from 3GU |
S6‑192290 | Pseudo-CR on Distributing Edge Application Server information | Samsung Electronics | imported from 3GU |
S6‑192291 | New solution for Key Issue#5 | Convida Wireless | imported from 3GU |
S6‑192292 | Pseudo-CR on EDGE Centralized CAPIF | Samsung | imported from 3GU |
S6‑192293 | Solution to KI5 with enhancement to CAPIF | Huawei, Hisilicon | imported from 3GU |
S6‑192294 | Update to solution#10 | Huawei, Hisilicon | imported from 3GU |
S6‑192295 | Pseudo-CR on Evaluation of Solution #5 | Intel Deutschland GmbH | imported from 3GU |
S6‑192296 | Solution 14 evaluation | Huawei, Hisilicon | imported from 3GU |
S6‑192297 | Solution 18 evaluation | Huawei, Hisilicon | imported from 3GU |
S6‑192298 | Solution #6 update and conclusion for KI#6 | Samsung | imported from 3GU |
S6‑192299 | Solution #2 clean-up and conclusion to KI#7 Dynamic availability of Edge Application Servers | Convida Wireless | imported from 3GU |
S6‑192300 | Solutions 20, 21 clean-up and conclusion to Key Issue#9 Preserving Service Continuity | Convida Wireless, Samsung | imported from 3GU |
S6‑192301 | Pseudo-CR on solution to Key Issues 9 with an alternative flow | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192302 | Pseudo-CR on Evaluation of Solution #7 | Intel Deutschland GmbH | imported from 3GU |
S6‑192303 | Pseudo-CR on Update of Key Issue 6 | Sony, Qualcomm | imported from 3GU |
S6‑192304 | Pseudo-CR on solution to Key Issue 12 (lifecycle management) | Nokia, Nokia Shanghai Bell, Vodafone | imported from 3GU |
S6‑192305 | Pseudo-CR on Update and Evaluation for Solution #11 | Vodafone | imported from 3GU |
S6‑192306 | Pseudo-CR on Additions to EDGE-5 requirements | Intel Deutschland GmbH | imported from 3GU |
S6‑192307 | Updates to Edge Deployment options figures and description corrections | Convida Wireless LLC, Samsung, Huawei?, Hisilicon? Ericsson | imported from 3GU |
S6‑192308 | Pseudo-CR on Deployment Options for EDNCS | Sony | imported from 3GU |
S6‑192309 | Pseudo-CR on Key Issue for EES Cleanup of EEC and EAS Resources | QUALCOMM JAPAN LLC. | imported from 3GU |
S6‑192310 | Pseudo-CR on Solution for EES Cleanup of EEC and EAS Resources | QUALCOMM JAPAN LLC. | imported from 3GU |
S6‑192311 | Pseudo-CR on Update and Evaluation for Solution #11 | Vodafone | imported from 3GU |
S6‑192312 | Pseudo-CR on Overall evaluations | Samsung Electronics, Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192313 | Pseudo-CR on Solution evaluation - Architecture | Samsung Electronics | imported from 3GU |
S6‑192314 | Pseudo-CR on Conclusions | Samsung Electronics | imported from 3GU |
S6‑192315 | New WID on enhancements for functional architecture and information flows for Mission Critical Data | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑192316 | New WID on Architecture for enabling Edge Applications | Samsung Electronics | imported from 3GU |
S6‑192317 | SEAL APIs corrections | Samsung | imported from 3GU |
S6‑192318 | Reply LS (S6-192023) on clarifications regarding SEAL services | SA6 | imported from 3GU |
S6‑192319 | Result element missing | one2many B.V. | imported from 3GU |
S6‑192320 | Mention of SA3 responsibility in a published TS is not relevant. | one2many B.V. | imported from 3GU |
S6‑192321 | Clarifications for location management | CATT | imported from 3GU |
S6‑192322 | Clarifications for location management | CATT | imported from 3GU |
S6‑192323 | pCR on Scope adjustments | Intel Deutschland GmbH | imported from 3GU |
S6‑192324 | Architecture clean-up | Samsung, CATT | imported from 3GU |
S6‑192325 | Pseudo-CR on architecture update | CATT | imported from 3GU |
S6‑192326 | Consolidation of KPI-related open issues in to a new key issue | Vodafone, Convida Wireless LLC | imported from 3GU |
S6‑192327 | Pseudo-CR on Update of Key Issue 6 | Sony, Qualcomm | imported from 3GU |
S6‑192328 | Pseudo-CR on Evaluation of Solution #2 | Intel Deutschland GmbH | imported from 3GU |
S6‑192329 | Solution 2 update and conclusion for Key Issue #1 and #7 | Samsung | imported from 3GU |
S6‑192330 | Solutions 8 and 17 clean-up and conclusion to KI#2 Edge Data Network discovery and registration | Convida Wireless | imported from 3GU |
S6‑192331 | Pseudo-CR on Solution for EEC subscription for configuration notifications | Intel Deutschland GmbH | imported from 3GU |
S6‑192332 | Pseudo-CR additional Key Issue – alternative transport at the Edge Data Network | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192333 | p-CR - Alternative transport for hight throughput and low latency communications | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192334 | Work Plan review | Qualcomm | imported from 3GU |
S6‑192335 | Update to uplink message delivery procedure | Huawei, Hisilicon, Ericsson | imported from 3GU |
S6‑192336 | Solution clean-up and conclusion for KI#3 Edge Application Server enablement on the Edge Hosting Environment | Convida Wireless, Samsung | imported from 3GU |
S6‑192337 | New solution for Key Issue#5 | Convida Wireless | imported from 3GU |
S6‑192338 | Update to solution#10 | Huawei, Hisilicon | imported from 3GU |
S6‑192339 | Solution 18 evaluation | Huawei, Hisilicon | imported from 3GU |
S6‑192340 | Solutions 20, 21 clean-up and conclusion to Key Issue#9 Preserving Service Continuity | Convida Wireless, Samsung | imported from 3GU |
S6‑192341 | Pseudo-CR on solution to Key Issues 9 with an alternative flow | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192342 | Pseudo-CR on solution to Key Issue 12 (lifecycle management) | Nokia, Nokia Shanghai Bell, Vodafone | imported from 3GU |
S6‑192343 | Pseudo-CR on Update and Evaluation for Solution #11 | Vodafone | imported from 3GU |
S6‑192344 | Pseudo-CR on Deployment Options for EDNCS | Sony | imported from 3GU |
S6‑192345 | Introducing descriptive text describing the urgency handling in the MC service system | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192346 | Priority of the user | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192347 | Priority of the user for initiating/receiving calls | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192348 | Priority of the user for initiating/receiving calls | Union Inter. Chemins de Fer | imported from 3GU |
S6‑192349 | Pseudo-CR on MCPTT group call in IOPS – Call setup based on the IP connectivity functionality | Ericsson | imported from 3GU |
S6‑192350 | Pseudo-CR on Floor control for MCPTT in IOPS (IP connectivity functionality) | Ericsson | imported from 3GU |
S6‑192351 | Addition of preconfigured regroup procedures | FirstNet | imported from 3GU |
S6‑192352 | Pseudo-CR on key issue update on resource control | CATT | imported from 3GU |
S6‑192353 | Pseudo-CR on solution sharing location information on interconnected MC systems - configuration | BDBOS | imported from 3GU |
S6‑192354 | Pseudo-CR on solution sharing location information on interconnected MC systems - authorization | BDBOS | imported from 3GU |
S6‑192355 | Pseudo-CR on overall evaluation | BDBOS | imported from 3GU |
S6‑192356 | Pseudo-CR on solution past location service | BDBOS | imported from 3GU |
S6‑192357 | Clarifications for location management | CATT | imported from 3GU |
S6‑192358 | Update to uplink message delivery procedure | Huawei, Hisilicon, Ericsson | imported from 3GU |
S6‑192359 | Pseudo-CR on solution of initial provisioning with authorization | CATT | imported from 3GU |
S6‑192360 | UE Authentication and UEId | AT&T | imported from 3GU |
S6‑192361 | EAS discovery using DNS | Samsung, Ericsson | imported from 3GU |
S6‑192362 | Pseudo-CR on Solution for EES Cleanup of EEC and EAS Resources | QUALCOMM JAPAN LLC. | imported from 3GU |
S6‑192363 | LS on UE types in TS 22.262 | Convida Wireless | imported from 3GU |
S6‑192364 | Key issue on QoS coordination | Huawei, Hisilicon | imported from 3GU |
S6‑192365 | Solution to establish communications with FFAPP requirements | Huawei, Hisilicon | imported from 3GU |
S6‑192366 | Pseudo-CR on solution 14 - functional model enhancement | BDBOS | imported from 3GU |
S6‑192367 | New WID on enhancements for functional architecture and information flows for Mission Critical Data | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑192368 | Reply LS on clarifications regarding V2XAPP services | Huawei | imported from 3GU |
S6‑192369 | LS on Application Architecture for enabling Edge Applications | Huawei, Hisilicon | imported from 3GU |
S6‑192370 | Architecture clean-up | Samsung, CATT | imported from 3GU |
S6‑192371 | Solution to Key issue#4 on EAS discovery from EDNCS | Huawei, Hisilicon | imported from 3GU |
S6‑192372 | Pseudo-CR on Distributing Edge Application Server information | Samsung Electronics | imported from 3GU |
S6‑192373 | pCR 23.758 – New solution | Ericsson | imported from 3GU |
S6‑192374 | EAS discovery using DNS | Samsung, Ericsson | imported from 3GU |
S6‑192375 | Pseudo-CR on solution to Key Issues 9 with an alternative flow | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192376 | Pseudo-CR on Solution for EEC subscription for configuration notifications | Intel Deutschland GmbH | imported from 3GU |
S6‑192377 | Pseudo-CR on solution to Key Issue 12 (lifecycle management) | Nokia, Nokia Shanghai Bell, Vodafone | imported from 3GU |
S6‑192378 | p-CR - Alternative transport for hight throughput and low latency communications | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192379 | Pseudo-CR additional Key Issue – alternative transport at the Edge Data Network | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192380 | Updates to Edge Deployment options figures and description corrections | Convida Wireless LLC, Samsung, Huawei, Hisilicon, Ericsson, Sony | imported from 3GU |
S6‑192381 | Pseudo-CR on Overall evaluations | Samsung Electronics, Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑192382 | File repair with the content storage function | ENENSYS | imported from 3GU |
S6‑192383 | File repair with the content storage function | ENENSYS | imported from 3GU |
S6‑192384 | CR Message Delivery | Ericsson GmbH, Eurolab | imported from 3GU |
S6‑192385 | Reply LS on clarifications regarding V2XAPP services | SA6 | imported from 3GU |
S6‑192386 | Notifications-based solution for KI #1 in 23.774 | AT&T | imported from 3GU |
S6‑192387 | Resource optimized group call mode for KI #2 in 23.774 | AT&T | imported from 3GU |
S6‑192388 | Handling large number of UEs in a cell for KI #3 in 23.774 | AT&T | imported from 3GU |
S6‑192389 | LS on further aspects of Mission Critical Services over 5MBS | AT&T | imported from 3GU |
S6‑192390 | Architecture for UAS application layer | Huawei, Hisilicon | imported from 3GU |
S6‑192391 | Framework for MSGin5G Service Architecture | Convida Wireless | imported from 3GU |
S6‑192392 | New Solution for Key Issue #3 | Convida Wireless | imported from 3GU |
S6‑192393 | Pseudo-CR on 5GMARCH KI8 group management | Samsung | imported from 3GU |
S6‑192394 | LS on UE types in TS 22.262 | SA6 | imported from 3GU |
S6‑192395 | LS reply to S6-192011 on tele-operated driving | SA6 | imported from 3GU |
S6‑192396 | New WID on Architecture for enabling Edge Applications | Samsung Electronics | imported from 3GU |
S6‑192397 | Pseudo-CR on solution to Key Issue 12 (lifecycle management) | Nokia, Nokia Shanghai Bell, Vodafone | imported from 3GU |
S6‑192398 | Solution Evaluation for Key Issue#4 Edge Application Server Discovery | Convida Wireless | imported from 3GU |
S6‑192399 | LS on Application Architecture for enabling Edge Applications | SA6 | imported from 3GU |
S6‑192400 | Presentation of Report to TSG:^^TR 23.758, Version 1.1.0^^Study on application architecture for enabling Edge Applications | Samsung Electronics | imported from 3GU |
S6‑192401 | Updates to Edge Deployment options figures and description corrections | Convida Wireless LLC, Samsung, Huawei, Hisilicon, Ericsson, Sony | imported from 3GU |
S6‑192402 | Notifications-based solution for KI #1 in 23.774 | AT&T | imported from 3GU |
S6‑192403 | Resource optimized group call mode for KI #2 in 23.774 | AT&T | imported from 3GU |
S6‑192404 | LS on further aspects of Mission Critical Services over 5MBS | SA6 | imported from 3GU |
page generated from database: 2024-04-22 07:58:53