3GPP TDocs (written contributions) at meeting
Meeting: S6-39-bis-e - 2020-10-12 to 2020-10-20, Online
meeting id: S6-39-bis-e (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
S6‑201689 | SA6 Meeting 39-bis-e Agenda | SA6 Chairman | imported from 3GU |
S6‑201690 | SA6 Meeting 39-e Report | MCC | imported from 3GU |
S6‑201691 | SA6 Meeting #39-bis-e - Agenda with Tdocs allocation after submission deadline | SA6 Chairman | imported from 3GU |
S6‑201692 | SA6 Meeting #39-bis-e - Agenda with Tdocs allocation at start of the meeting | SA6 Chairman | imported from 3GU |
S6‑201693 | SA6 Meeting #39-bis-e - Chairman's notes at end of the meeting | SA6 Chairman | imported from 3GU |
S6‑201694 | LS on ETSI Plugtest reports | CT1 | imported from 3GU |
S6‑201695 | LS on clarifications for authorised user learning about the users whose floor requests are queued | CT1 | imported from 3GU |
S6‑201696 | LS on application layer impact of FS_enh_EC solution #16 | SA2 | imported from 3GU |
S6‑201697 | LS on IP address to GPSI translation | SA2 | imported from 3GU |
S6‑201698 | Response LS on 5GMSG requirement clarifications | SA1 | imported from 3GU |
S6‑201699 | LS on 5GMSG store and forward | SA1 | imported from 3GU |
S6‑201700 | Reply LS on security procedures for Edge Applications | SA3 | imported from 3GU |
S6‑201701 | Reply LS on Key Management procedure in SEAL | SA3 | imported from 3GU |
S6‑201702 | LS on Rel-17 schedule | SA | imported from 3GU |
S6‑201703 | Group Location | Motorola Solutions UK Ltd. | imported from 3GU |
S6‑201704 | Key issue on mission critical traffic routing function of gateway UE | CALTTA | imported from 3GU |
S6‑201705 | Key issue on mission critical capabilities exposure of gateway UE | CALTTA | imported from 3GU |
S6‑201706 | Discussion paper on enhancement to IP connectivity point-to-point MCData service to allow optionally a direct connection between the involved clients | Kontron Transportation France | imported from 3GU |
S6‑201707 | Enhancement to IP connectivity point-to-point MCData service to allow optionally a direct connection between the involved clients | Kontron Transportation France | imported from 3GU |
S6‑201708 | Alignment of the definition of UAS | InterDigital | imported from 3GU |
S6‑201709 | Report on SA6 related topics at SA#89-e | SA6 Chairman | imported from 3GU |
S6‑201710 | Align Annex B with changes to “auto-send” | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑201711 | Correction to the transmission control configuration parameters | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑201712 | Align Annex B with changes to “auto-send” | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑201713 | Correction to the transmission control configuration parameters | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑201714 | Support of UAVs in 3GPP system and interfacing with USS/UTM | ACJA (GSMA and GUTMA) | imported from 3GU |
S6‑201715 | Update solution#6 switching C2 between UAV-UAV-C and USS-UTM navigated | InterDigital | imported from 3GU |
S6‑201716 | pCR on End-to-end acknowledgement in 5GMARCH | one2many B.V. | imported from 3GU |
S6‑201717 | pCR on capabilities of UE without 5GMSGS client in 5GMARCH | one2many B.V. | imported from 3GU |
S6‑201718 | Dynamic availability of Edge Application Server | ETRI | imported from 3GU |
S6‑201719 | Pseudo-CR on FS 5GMARCH Clarifications on solution about interworking with SMS | Huawei, Hisilicon | imported from 3GU |
S6‑201720 | Solution on message reply from Non-3GPP UE to 5GMSGS UE | Huawei, Hisilicon | imported from 3GU |
S6‑201721 | Pseudo-CR on FS 5GMARCH Solution on message reply from UE to App Server | Huawei, Hisilicon | imported from 3GU |
S6‑201722 | Pseudo-CR on FS 5GMARCH solution on APIs provided by MSGin5G server | Huawei, Hisilicon | imported from 3GU |
S6‑201723 | Pseudo-CR on FS 5GMARCH KI on using CAPIF | Huawei, Hisilicon | imported from 3GU |
S6‑201724 | Pseudo-CR on FS 5GMARCH Solution on using CAPIF | Huawei, Hisilicon | imported from 3GU |
S6‑201725 | Pseudo-CR on FS 5GMARCH Conclusions | Huawei, Hisilicon | imported from 3GU |
S6‑201726 | EDGEAPP: Proposal to modify the API service operation names | ETRI | imported from 3GU |
S6‑201727 | Add new UE ID | China Mobile Com. Corporation | imported from 3GU |
S6‑201728 | Add new UE ID | China Mobile Com. Corporation | imported from 3GU |
S6‑201729 | Authorized user being notified about other users floor queue status | Samsung R&D Institute India | imported from 3GU |
S6‑201730 | Reply LS on clarifications for authorised user learning about the users whose floor requests are queued | Samsung R&D Institute India | imported from 3GU |
S6‑201731 | Solution -#x: QoS requirement provisioning during C2 connectivity establishment | InterDigital | imported from 3GU |
S6‑201732 | Progress and completion of FS_UASAPP | InterDigital | imported from 3GU |
S6‑201733 | Update to EEC executed application context relocation | InterDigital | imported from 3GU |
S6‑201734 | Clarifications on Source EAS decided application context relocation | InterDigital | imported from 3GU |
S6‑201735 | Device Onboarding support | ZTE Corporation | imported from 3GU |
S6‑201736 | Constrained devices supporting | ZTE Corporation | imported from 3GU |
S6‑201737 | OPC-UA integration | ZTE Corporation | imported from 3GU |
S6‑201738 | Pseudo-CR on terminology alignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑201739 | Pseudo-CR on functional architecture | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑201740 | Pseudo-CR on connection authorisation | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑201741 | Pseudo-CR on combined connection and service authorisation | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑201742 | Pseudo-CR on using IMS identities | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑201743 | Various corrections | AT&T | imported from 3GU |
S6‑201744 | Key issues to Solutions Mapping | Tencent | imported from 3GU |
S6‑201745 | Pseudo-CR on key issue x: UAS Identification management | Tencent | imported from 3GU |
S6‑201746 | Clarification to Edge Configuration Server discovery | vivo,OPPO,Xiaomi | imported from 3GU |
S6‑201747 | Way forward of providing ECS information/IP address to UE | vivo | imported from 3GU |
S6‑201748 | LS Reply on application layer impact of FS_enh_EC solution #16 | vivo | imported from 3GU |
S6‑201749 | Clarification on UP path management event API | Samsung | imported from 3GU |
S6‑201750 | EEC detection in application context relocation | Samsung | imported from 3GU |
S6‑201751 | Network Capability Exposure information transfer | Samsung | imported from 3GU |
S6‑201752 | Determination of common application context transfer solutions | Apple, Intel | imported from 3GU |
S6‑201753 | T-EES executed application context relocation procedure | Samsung | imported from 3GU |
S6‑201754 | UE NAS mode and interaction with 3GPP network | Samsung | imported from 3GU |
S6‑201755 | User plane connectivity modification in S-EES executed ACR | Samsung | imported from 3GU |
S6‑201756 | Pseudo-CR on ECS Discovery from 5GC | Sony | imported from 3GU |
S6‑201757 | Pseudo-CR on EEC ID in Service provisioning | Sony | imported from 3GU |
S6‑201758 | Pseudo-CR on Service Continuity Support Indication | Sony | imported from 3GU |
S6‑201759 | Pseudo-CR on Application Context Relocation Decision Making | Sony | imported from 3GU |
S6‑201760 | Add EAS discovery in EDGE-3 | Ericsson | imported from 3GU |
S6‑201761 | MC service emergency alert clarifications | FirstNet | imported from 3GU |
S6‑201762 | Remove location EN | Ericsson | imported from 3GU |
S6‑201763 | MCPTT in-progress emergency group state cancel modification | FirstNet | imported from 3GU |
S6‑201764 | AF influence in Application Context Relocation | Ericsson, Intel | imported from 3GU |
S6‑201765 | EAS DNAI in EES profile and selected EAS | Ericsson | imported from 3GU |
S6‑201766 | Support AEF location and API invoker interface for edge application | Ericsson | imported from 3GU |
S6‑201767 | Application Context: Transfer or Relocation? | Apple | imported from 3GU |
S6‑201768 | Separation between geographical and topological location | Intel Deutschland GmbH, InterDigital, Convida Wireless, Samsung, Apple | imported from 3GU |
S6‑201769 | UE internal movement detection | Intel Deutschland GmbH, Apple | imported from 3GU |
S6‑201770 | Support group-based location exposure | Ericsson | imported from 3GU |
S6‑201771 | Support more UE IDs in QoS exposure | Ericsson | imported from 3GU |
S6‑201772 | Proposal of solution for assisting dynamic C2 mode switching | Lenovo, Motorola Mobility | imported from 3GU |
S6‑201773 | Updated Solution on FFAE layer support for network slicing | Lenovo, Motorola Mobility | imported from 3GU |
S6‑201774 | PC5 Provisioning in multi-operator V2X scenarios | Lenovo, Motorola Mobility | imported from 3GU |
S6‑201775 | Source EAS decided application context relocation | InterDigital | imported from 3GU |
S6‑201776 | Pseudo-CR on deduplication of application context relocation | Qualcomm Technologies Int | imported from 3GU |
S6‑201777 | LS Reply on application layer impact of FS_enh_EC solution #16 | Qualcomm Technologies Int | imported from 3GU |
S6‑201778 | Fixing media resources request procedure from MC service server | Ericsson | imported from 3GU |
S6‑201779 | Fixing media resources request procedure from MC service server | Ericsson | imported from 3GU |
S6‑201780 | Access resource information in MCPTT information flows | Ericsson | imported from 3GU |
S6‑201781 | Access resource information in MCPTT information flows | Ericsson | imported from 3GU |
S6‑201782 | Resources request from MC service server at session establishment | Ericsson | imported from 3GU |
S6‑201783 | Discussion of new work leveraging 5GS Location Service | CATT | imported from 3GU |
S6‑201784 | MCVideo pull and push corrections | Ericsson | imported from 3GU |
S6‑201785 | New SID on study on location management service supporting 5G location services | CATT | imported from 3GU |
S6‑201786 | Minor changes to information elements and procedures | Samsung R&D Institute India | imported from 3GU |
S6‑201787 | Discussion on Constrained devices - CoAP | Ericsson | imported from 3GU |
S6‑201788 | SEAL support for CoAP | Ericsson | imported from 3GU |
S6‑201789 | IP connectivity, SDS and FD functional model correction | Union Inter. Chemins de Fer | imported from 3GU |
S6‑201790 | IP connectivity, SDS and FD functional model correction | Union Inter. Chemins de Fer | imported from 3GU |
S6‑201791 | TS 23.289 Skeleton | Union Inter. Chemins de Fer | imported from 3GU |
S6‑201792 | TS 23.289 Introduction, scope, references and terms | Union Inter. Chemins de Fer | imported from 3GU |
S6‑201793 | TS 23.289 Clause 4 multiple access and session connectivity | Union Inter. Chemins de Fer | imported from 3GU |
S6‑201794 | Pseudo-CR on key issue x: UAS media application session management | Tencent | imported from 3GU |
S6‑201795 | Application information optionality | Samsung Electronics | imported from 3GU |
S6‑201796 | EAS discovery filters flag | Samsung Electronics | imported from 3GU |
S6‑201797 | EAS discovery and dynamic information subscription | Samsung Electronics | imported from 3GU |
S6‑201798 | EEC context | Samsung Electronics, Convida, Sony | imported from 3GU |
S6‑201799 | EDGE-1 and EDGE-4 APIs | Samsung Electronics, AT&T, Deutsche Telekom, Intel | imported from 3GU |
S6‑201800 | Relation between DNAIs of EAS, EES and EDN | Samsung Electronics | imported from 3GU |
S6‑201801 | AC service KPIs | Samsung Electronics | imported from 3GU |
S6‑201802 | EEC ID and UE ID | Samsung Electronics | imported from 3GU |
S6‑201803 | Registering EAS instances | Samsung Electronics | imported from 3GU |
S6‑201804 | UE Identifier API | Samsung Electronics, Intel | imported from 3GU |
S6‑201805 | Intra-EDN mobility and load balancers | Samsung Electronics | imported from 3GU |
S6‑201806 | Target EES and target EAS selection | Samsung Electronics | imported from 3GU |
S6‑201807 | EN related to UE location | Samsung Electronics | imported from 3GU |
S6‑201808 | Duplicate ENs in Session with QoS API | Samsung Electronics | imported from 3GU |
S6‑201809 | Update to capability exposure clause | Samsung Electronics | imported from 3GU |
S6‑201810 | Aligning API nomenclature with CAPIF | Samsung Electronics | imported from 3GU |
S6‑201811 | EAS, EES registration APIs | Samsung Electronics | imported from 3GU |
S6‑201812 | Informing EES of the selected EAS | Samsung Electronics | imported from 3GU |
S6‑201813 | LS reply on UE IP address to GPSI translation | Samsung Electronics | imported from 3GU |
S6‑201814 | UE ID API | Samsung Electronics | imported from 3GU |
S6‑201815 | Discussion on Provisioning ECS Address Information via the 5GC | Convida Wireless LLC, ATT, Samsung | imported from 3GU |
S6‑201816 | [DRAFT] Reply LS on application layer impact of FS_enh_EC solution #16 | Convida Wireless LLC, ATT, Samsung | imported from 3GU |
S6‑201817 | ACR indicator for EAS discovery requests | Convida Wireless LLC | imported from 3GU |
S6‑201818 | MSGin5G Store and Forward Solution | Convida Wireless LLC | imported from 3GU |
S6‑201819 | FS_5GMARCH nomenclature alignment | Convida Wireless LLC | imported from 3GU |
S6‑201820 | Pseudo-CR on update to solution #16 | CATT | imported from 3GU |
S6‑201821 | Pseudo-CR on FS_5GMARCH deliver message to Application Client | China Mobile Com. Corporation | imported from 3GU |
S6‑201822 | Pseudo-CR on FS_5GMARCH solution 5GMSGS messaging when contact is unknown (non-IMS) | China Mobile Com. Corporation | imported from 3GU |
S6‑201823 | Evaluation of solution #15 | CATT | imported from 3GU |
S6‑201824 | Pseudo-CR on FS_5GMARCH KI18 solution MSGin5G Roaming | China Mobile Com. Corporation | imported from 3GU |
S6‑201825 | Pseudo-CR on FS_5GMARCH Conclusions and recommendations: KIs and solutions | China Mobile Com. Corporation | imported from 3GU |
S6‑201826 | Decoupling EEC registration with EAS discovery | Huawei, Hisilicon, Ericsson, Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑201827 | Service provisioning without Application Client profile(s) | Huawei, Hisilicon, Qualcomm, CATT, China Mobile | imported from 3GU |
S6‑201828 | EAS discovery without Discovery filters | Huawei, Hisilicon, Qualcomm, CATT, China Mobile | imported from 3GU |
S6‑201829 | Alignment between functionalities of functional entities and Reference Points | Huawei, Hisilicon | imported from 3GU |
S6‑201830 | Clarification on Edge Application Server Registration | Huawei, Hisilicon | imported from 3GU |
S6‑201831 | Editorial changes to Application layer architecture | Huawei, Hisilicon | imported from 3GU |
S6‑201832 | Trigger the EAS instantiation by ECS | Huawei, Hisilicon | imported from 3GU |
S6‑201833 | ACR with full operations at edge enabler layer | Huawei, Hisilicon | imported from 3GU |
S6‑201834 | Application relocation information notification | Huawei, Hisilicon | imported from 3GU |
S6‑201835 | User Plane Path Management event information flow update | Huawei, Hisilicon | imported from 3GU |
S6‑201836 | User Plane Path Management event and notification enhancement | Huawei, Hisilicon | imported from 3GU |
S6‑201837 | User Plane Path Management event enhancement with application context availability | Huawei, Hisilicon | imported from 3GU |
S6‑201838 | User Plane Path Management event enhancement with available target EAS | Huawei, Hisilicon | imported from 3GU |
S6‑201839 | DNAI clarifications | Huawei, Hisilicon | imported from 3GU |
S6‑201840 | LS on DNAI clarification and enhancements | Huawei, Hisilicon | imported from 3GU |
S6‑201841 | Editorial correction to solution#2 | Huawei, Hisilicon | imported from 3GU |
S6‑201842 | Supporting OPC UA | Huawei, Hisilicon | imported from 3GU |
S6‑201843 | Location management mechanism backward compatibility | Huawei, Hisilicon | imported from 3GU |
S6‑201844 | Call restrictions for normal private calls | Huawei, Hisilicon | imported from 3GU |
S6‑201845 | FA controlling role description in MCVideo | Huawei, Hisilicon | imported from 3GU |
S6‑201846 | FA controlling role description in MCVideo | Huawei, Hisilicon | imported from 3GU |
S6‑201847 | FA management procedure in MCVideo | Huawei, Hisilicon | imported from 3GU |
S6‑201848 | FA management procedure in MCVideo | Huawei, Hisilicon | imported from 3GU |
S6‑201849 | Assisting discovery of USS/UTM | Huawei, Hisilicon | imported from 3GU |
S6‑201850 | Relationship of SA2 and SA6 UAS architecture | Huawei, Hisilicon | imported from 3GU |
S6‑201851 | Support for on-demand pairing of UAV-C with UAV | Huawei, Hisilicon | imported from 3GU |
S6‑201852 | Discussion on UASAPP progress update considering SA2 and SA6 work | Huawei, Hisilicon | imported from 3GU |
S6‑201853 | V2X application layer architecture enhancement | Huawei, Hisilicon | imported from 3GU |
S6‑201854 | Business relationships between V2X service providers | Huawei, Hisilicon | imported from 3GU |
S6‑201855 | V2X service discovery across multiple V2X service providers | Huawei, Hisilicon | imported from 3GU |
S6‑201856 | Support for HD map dynamic information | Huawei, Hisilicon | imported from 3GU |
S6‑201857 | Tracking UE and obtaining dynamic UE information | Huawei, Hisilicon | imported from 3GU |
S6‑201858 | Editorial corrections | Huawei, Hisilicon | imported from 3GU |
S6‑201859 | Missing solution evaluations | Huawei, Hisilicon | imported from 3GU |
S6‑201860 | Pseudo-CR on Solution for group list fetch | Samsung | imported from 3GU |
S6‑201861 | Pseudo-CR on Solution for positioning method negotiation | Samsung | imported from 3GU |
S6‑201862 | Pseudo-CR on new key issue to support message communication | Samsung | imported from 3GU |
S6‑201863 | Pseudo-CR on solution to the key issue to support message communication | Samsung | imported from 3GU |
S6‑201864 | Pseudo-CR on solution for the group communication | Samsung | imported from 3GU |
S6‑201865 | Pseudo-CR on MSGin5G Segment Recovery procedure | Samsung | imported from 3GU |
S6‑201866 | Updates to group creation notification | Samsung | imported from 3GU |
S6‑201867 | Clarification on group join notification | Samsung | imported from 3GU |
S6‑201868 | Pseudo-CR on delivery report aggregation | Samsung | imported from 3GU |
S6‑201869 | Pseudo-CR on Solution for group notification | Samsung | imported from 3GU |
S6‑201870 | Discussion regarding enhancements to SEAL | Samsung | imported from 3GU |
S6‑201871 | New WID for enhanced Service Enabler Architecture Layer for Verticals | Samsung | imported from 3GU |
S6‑201872 | Resolution of ENs on security aspects | Samsung | imported from 3GU |
S6‑201873 | Pseudo-CR Enable FFAP for 5G CN capabilities | Samsung | imported from 3GU |
S6‑201874 | Pseudo-CR New Solution to enable FFAP for 5G CN capabilities | Samsung | imported from 3GU |
S6‑201875 | Pseudo-CR on Key issue on monitor flight path | Samsung | imported from 3GU |
S6‑201876 | Pseudo-CR on Key Issue - Detection of problematic UAV | Samsung | imported from 3GU |
S6‑201877 | Pseudo-CR on Solution to monitor UAV flight path | Samsung | imported from 3GU |
S6‑201878 | Pseudo-CR on Solution to detection of problematic UAV | Samsung | imported from 3GU |
S6‑201879 | Pseudo-CR on Update to Solution #1 | Samsung | imported from 3GU |
S6‑201880 | Pseudo-CR on pCR based on SA1 clarifications | Samsung | imported from 3GU |
S6‑201881 | Support of multiple delivery mechanisms | Convida Wireless LLC | imported from 3GU |
S6‑201882 | LS on application layer impact of FS_enh_EC solution #16 | SA2 | imported from 3GU |
S6‑201883 | Reply LS on ETSI Plugtest reports | UPV/EHU (ETSI MCX Plugtests) | imported from 3GU |
S6‑201884 | LS on APIs in EDGEAPP | SA6 | imported from 3GU |
S6‑201885 | pCR: Key issues to Solutions Mapping | Tencent | imported from 3GU |
S6‑201886 | Pseudo-CR on key issue x: UAS Identification usage in application layer architecture | Tencent | imported from 3GU |
S6‑201887 | Pseudo-CR on key issue x: UAS media application session management | Tencent | imported from 3GU |
S6‑201888 | Pseudo-CR on functional architecture | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑201889 | Pseudo-CR on connection authorisation | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑201890 | Pseudo-CR on combined connection authorisation | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑201891 | Application Context: Transfer or Relocation? | Apple | imported from 3GU |
S6‑201892 | Pseudo-CR on Determination of common application context transfer solutions | Apple, Intel | imported from 3GU |
S6‑201893 | EDGEAPP: Proposal to modify the API service operation names | ETRI, Samsung | imported from 3GU |
S6‑201894 | IP connectivity, SDS and FD functional model correction | Union Inter. Chemins de Fer | imported from 3GU |
S6‑201895 | MC service emergency alert clarifications | FirstNet | imported from 3GU |
S6‑201896 | MCPTT in-progress emergency group state cancel modification | FirstNet | imported from 3GU |
S6‑201897 | Pseudo-CR on TS 23.289 Clause 4 multiple access and session connectivity | Union Inter. Chemins de Fer | imported from 3GU |
S6‑201898 | Pseudo-CR on capabilities of UE without 5GMSGS client | one2many B.V. | imported from 3GU |
S6‑201899 | Align Annex B with changes to “auto-send” | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑201900 | Correction to the transmission control configuration parameters | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑201901 | Align Annex B with changes to “auto-send” | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑201902 | Correction to the transmission control configuration parameters | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑201903 | LS Reply on application layer impact of FS_enh_EC solution #16 | Qualcomm Technologies Int | imported from 3GU |
S6‑201904 | Pseudo-CR on update to solution #16 | CATT | imported from 3GU |
S6‑201905 | New SID on study on location management service supporting 5G location services | CATT | imported from 3GU |
S6‑201906 | Pseudo-CR on ECS Discovery from 5GC | Sony | imported from 3GU |
S6‑201907 | Pseudo-CR on EEC ID in Service provisioning | Sony, Samsung Electronics | imported from 3GU |
S6‑201908 | Pseudo-CR on Service Continuity Support Indication | Sony | imported from 3GU |
S6‑201909 | Pseudo-CR on Application Context Relocation Decision Making | Sony | imported from 3GU |
S6‑201910 | Authorized user being notified about other users floor queue status | Samsung R&D Institute India | imported from 3GU |
S6‑201911 | Reply LS on clarifications for authorised user learning about the users whose floor requests are queued | Samsung R&D Institute India | imported from 3GU |
S6‑201912 | Clarification on UP path management event API | Samsung | imported from 3GU |
S6‑201913 | EEC detection in application context relocation | Samsung | imported from 3GU |
S6‑201914 | User plane connectivity modification in S-EES executed ACR | Samsung | imported from 3GU |
S6‑201915 | Separation between geographical and topological location | Intel Deutschland GmbH, InterDigital, Convida Wireless, Samsung, Apple | imported from 3GU |
S6‑201916 | UE internal movement detection | Intel Deutschland GmbH, Apple | imported from 3GU |
S6‑201917 | AF influence in Application Context Relocation | Ericsson, Intel | imported from 3GU |
S6‑201918 | Support AEF location and API invoker interface for edge application | Ericsson | imported from 3GU |
S6‑201919 | EAS DNAI in EES profile and selected EAS | Ericsson | imported from 3GU |
S6‑201920 | Add EAS discovery in EDGE-3 | Ericsson, InterDigital | imported from 3GU |
S6‑201921 | Remove location EN | Ericsson, Samsung, InterDigital | imported from 3GU |
S6‑201922 | context maintained on EES | Ericsson | imported from 3GU |
S6‑201923 | Fixing media resources request procedure from MC service server | Ericsson | imported from 3GU |
S6‑201924 | Access resource information in MCPTT information flows | Ericsson | imported from 3GU |
S6‑201925 | Request for network resources at session establishment from the MC service server | Ericsson | imported from 3GU |
S6‑201926 | SEAL support for CoAP | Ericsson | imported from 3GU |
S6‑201927 | Pseudo-CR on FS 5GMARCH Clarifications on solution about interworking with SMS | Huawei, Hisilicon | imported from 3GU |
S6‑201928 | Pseudo-CR on FS 5GMARCH Solution on message reply from Non-3GPP UE to 5GMSGS UE | Huawei, Hisilicon | imported from 3GU |
S6‑201929 | Pseudo-CR on FS 5GMARCH Solution on message reply from UE to App Server | Huawei, Hisilicon | imported from 3GU |
S6‑201930 | Pseudo-CR on FS 5GMARCH solution on APIs provided by MSGin5G server | Huawei, Hisilicon | imported from 3GU |
S6‑201931 | Pseudo-CR on FS 5GMARCH KI on using CAPIF | Huawei, Hisilicon | imported from 3GU |
S6‑201932 | Pseudo-CR on FS 5GMARCH Solution on using CAPIF | Huawei, Hisilicon | imported from 3GU |
S6‑201933 | Minor changes to information elements and procedures | Samsung R&D Institute India | imported from 3GU |
S6‑201934 | IP connectivity, SDS and FD functional model correction | Union Inter. Chemins de Fer | imported from 3GU |
S6‑201935 | Clarification on group join notification | Samsung | imported from 3GU |
S6‑201936 | Resolution of ENs on security aspects | Samsung | imported from 3GU |
S6‑201937 | Pseudo-CR on Solution for positioning method negotiation | Samsung | imported from 3GU |
S6‑201938 | Pseudo-CR on new key issue to support message communication | Samsung | imported from 3GU |
S6‑201939 | Pseudo-CR Enable FFAP for 5G CN capabilities | Samsung | imported from 3GU |
S6‑201940 | Pseudo-CR New Solution to enable FFAP for 5G CN capabilities | Samsung | imported from 3GU |
S6‑201941 | Pseudo-CR on Evaluation of Key issue #1 | Samsung, InterDigital | imported from 3GU |
S6‑201942 | Pseudo-CR on Key issue on monitor flight path | Samsung | imported from 3GU |
S6‑201943 | Pseudo-CR on Key Issue - Detection of problematic UAV | Samsung | imported from 3GU |
S6‑201944 | Pseudo-CR on pCR based on SA1 clarifications | Samsung | imported from 3GU |
S6‑201945 | Pseudo-CR on MSGin5G Segment Recovery procedure | Samsung | imported from 3GU |
S6‑201946 | Pseudo-CR on Solution for group list fetch | Samsung | imported from 3GU |
S6‑201947 | Pseudo-CR on Solution for group notification | Samsung | imported from 3GU |
S6‑201948 | Pseudo-CR on delivery report aggregation | Samsung, one2many B.V. | imported from 3GU |
S6‑201949 | New WID for enhanced Service Enabler Architecture Layer for Verticals | Samsung | imported from 3GU |
S6‑201950 | Pseudo CR on Alignment of the definition of UAS | InterDigital, Tencent, Deutsche Telekom, Qualcomm | imported from 3GU |
S6‑201951 | Subscription to Group Location | Motorola Solutions UK Ltd. | imported from 3GU |
S6‑201952 | Proposal of solution for assisting dynamic C2 mode switching | Lenovo, Motorola Mobility | imported from 3GU |
S6‑201953 | Updated Solution on FFAE layer support for network slicing | Lenovo, Motorola Mobility | imported from 3GU |
S6‑201954 | PC5 Provisioning in multi-operator V2X scenarios | Lenovo, Motorola Mobility | imported from 3GU |
S6‑201955 | Pseudo CR on Update solution#6 switching C2 between UAV-UAV-C and USS-UTM navigated | InterDigital | imported from 3GU |
S6‑201956 | Pseudo CR on Solution #x: QoS requirement provisioning during C2 connectivity establishment | InterDigital | imported from 3GU |
S6‑201957 | Update to EEC executed application context relocation | InterDigital | imported from 3GU |
S6‑201958 | Clarifications on Source EAS decided application context relocation | InterDigital | imported from 3GU |
S6‑201959 | Clarification to Edge Configuration Server discovery | vivo,OPPO,Xiaomi | imported from 3GU |
S6‑201960 | Application information optionality | Samsung Electronics | imported from 3GU |
S6‑201961 | EAS discovery filters flag | Samsung Electronics | imported from 3GU |
S6‑201962 | EAS discovery and dynamic information subscription | Samsung Electronics, ETRI, UANGEL | imported from 3GU |
S6‑201963 | EEC context | Samsung Electronics, Convida, Sony | imported from 3GU |
S6‑201964 | EDGE-1 and EDGE-4 APIs | Samsung Electronics, AT&T, Deutsche Telekom, Intel, ETRI | imported from 3GU |
S6‑201965 | Relation between DNAIs of EAS, EES and EDN | Samsung Electronics | imported from 3GU |
S6‑201966 | UE Identifier API | Samsung Electronics, Intel | imported from 3GU |
S6‑201967 | Target EES and target EAS selection | Samsung Electronics | imported from 3GU |
S6‑201968 | Update to capability exposure clause | Samsung Electronics | imported from 3GU |
S6‑201969 | EAS, EES registration APIs | Samsung Electronics, ETRI | imported from 3GU |
S6‑201970 | Informing EES of the selected EAS | Samsung Electronics | imported from 3GU |
S6‑201971 | LS reply on UE IP address to GPSI translation | Samsung Electronics | imported from 3GU |
S6‑201972 | UE ID API | Samsung Electronics | imported from 3GU |
S6‑201973 | LS on APIs in EDGEAPP | SA6 | imported from 3GU |
S6‑201974 | MSGin5G Store and Forward Solution | Convida Wireless LLC | imported from 3GU |
S6‑201975 | 5GMARCH nomenclature alignment | Convida Wireless LLC | imported from 3GU |
S6‑201976 | Support of multiple delivery mechanisms | Convida Wireless LLC | imported from 3GU |
S6‑201977 | Pseudo-CR on FS_5GMARCH deliver message to Application Client | China Mobile Com. Corporation | imported from 3GU |
S6‑201978 | Pseudo-CR on FS_5GMARCH solution 5GMSGS message delivery based on message topic(non-IMS) | China Mobile Com. Corporation | imported from 3GU |
S6‑201979 | Pseudo-CR on FS_5GMARCH KI18 solution MSGin5G Roaming | China Mobile Com. Corporation | imported from 3GU |
S6‑201980 | Pseudo-CR on FS_5GMARCH Overall Evaluation, Conclusions and recommendations | China Mobile Com. Corporation | imported from 3GU |
S6‑201981 | Pseudo-CR on TS 23.289 Clause 4 multiple access and session connectivity | Union Inter. Chemins de Fer | imported from 3GU |
S6‑201982 | Service provisioning without Application Client profile(s) | Huawei, Hisilicon, Qualcomm, CATT, China Mobile | imported from 3GU |
S6‑201983 | EAS discovery without Discovery filters | Huawei, Hisilicon, Qualcomm, CATT, China Mobile, Nokia | imported from 3GU |
S6‑201984 | Clarification on Edge Application Server Registration | Huawei, Hisilicon, Samsung | imported from 3GU |
S6‑201985 | Editorial changes to Application layer architecture | Huawei, Hisilicon | imported from 3GU |
S6‑201986 | Trigger the EAS instantiation by ECS | Huawei, Hisilicon | imported from 3GU |
S6‑201987 | ACR with full operations at edge enabler layer | Huawei, Hisilicon | imported from 3GU |
S6‑201988 | Application relocation information notification | Huawei, Hisilicon | imported from 3GU |
S6‑201989 | User Plane Path Management event and notification enhancement | Huawei, Hisilicon | imported from 3GU |
S6‑201990 | User Plane Path Management event enhancement with application context availability | Huawei, Hisilicon | imported from 3GU |
S6‑201991 | User Plane Path Management event enhancement with available target EAS | Huawei, Hisilicon | imported from 3GU |
S6‑201992 | DNAI clarifications | Huawei, Hisilicon | imported from 3GU |
S6‑201993 | Supporting OPC UA | Huawei, Hisilicon, ZTE | imported from 3GU |
S6‑201994 | Location management mechanism backward compatibility | Huawei, Hisilicon | imported from 3GU |
S6‑201995 | FA controlling role description in MCVideo | Huawei, Hisilicon | imported from 3GU |
S6‑201996 | Assisting discovery of USS/UTM | Huawei, Hisilicon | imported from 3GU |
S6‑201997 | Relationship of SA2 and SA6 UAS architecture | Huawei, Hisilicon | imported from 3GU |
S6‑201998 | Support for on-demand pairing of UAV-C with UAV | Huawei, Hisilicon | imported from 3GU |
S6‑201999 | V2X application layer architecture enhancement | Huawei, Hisilicon | imported from 3GU |
S6‑202000 | Business relationships between V2X service providers | Huawei, Hisilicon | imported from 3GU |
S6‑202001 | V2X service discovery across multiple V2X service providers | Huawei, Hisilicon | imported from 3GU |
S6‑202002 | Support for HD map dynamic information | Huawei, Hisilicon | imported from 3GU |
S6‑202003 | Tracking UE and obtaining dynamic UE information | Huawei, Hisilicon | imported from 3GU |
S6‑202004 | Pseudo CR on Solution #x: QoS requirement provisioning during C2 connectivity establishment | InterDigital | imported from 3GU |
S6‑202005 | SA6#39 BIS-e Work Plan discussion | SA6 Chair | imported from 3GU |
S6‑202006 | Authorized user being notified about other users floor queue status | Samsung R&D Institute India | imported from 3GU |
S6‑202007 | Reply LS on clarifications for authorised user learning about the users whose floor requests are queued | Samsung R&D Institute India | imported from 3GU |
S6‑202008 | Reply LS on IP address to GPSI translation | SA6 | imported from 3GU |
S6‑202009 | LS on APIs in EDGEAPP | SA6 | imported from 3GU |
S6‑202010 | Correction to the transmission control configuration parameters | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑202011 | Correction to the transmission control configuration parameters | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑202012 | PC5 Provisioning in multi-operator V2X scenarios | Lenovo, Motorola Mobility | imported from 3GU |
S6‑202013 | Tracking UE and obtaining dynamic UE information | Huawei, Hisilicon | imported from 3GU |
S6‑202014 | Communicating FF application service requirements with 3GPP system | Huawei, Hisilicon, ZTE | imported from 3GU |
S6‑202015 | Pseudo-CR Enable FFAP for 5G CN capabilities | Samsung | imported from 3GU |
S6‑202016 | Pseudo-CR New Solution to enable FFAP for 5G CN capabilities | Samsung | imported from 3GU |
S6‑202017 | Support of multiple delivery mechanisms | Convida Wireless LLC, Samsung | imported from 3GU |
S6‑202018 | Pseudo-CR on Solution for group notification | Samsung | imported from 3GU |
S6‑202019 | Pseudo-CR on FS_5GMARCH Conclusions and recommendations: KIs and solutions | China Mobile, Huawei, Hisilicon | imported from 3GU |
S6‑202020 | Pseudo-CR on key issue x: UAS Identification management | Tencent, InterDigital | imported from 3GU |
S6‑202021 | pCR: Key issues to Solutions Mapping | Tencent, Huawei, Hisilicon | imported from 3GU |
S6‑202022 | Pseudo-CR on using IMS identities | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑202023 | Clarification to Edge Configuration Server discovery | vivo, OPPO, Xiaomi, Spreadtrum | imported from 3GU |
S6‑202024 | Pseudo-CR on ECS Discovery from 5GC | Sony | imported from 3GU |
S6‑202025 | LS Reply on application layer impact of FS_enh_EC solution #16 | SA6 | imported from 3GU |
S6‑202026 | EAS discovery and dynamic information subscription | Samsung Electronics, ETRI, UANGEL | imported from 3GU |
S6‑202027 | Separation between geographical and topological location | Intel, InterDigital, Convida Wireless, Samsung, Apple | imported from 3GU |
S6‑202028 | Relation between DNAIs of EAS, EES and EDN | Samsung Electronics | imported from 3GU |
S6‑202029 | Clarification on UP path management event API | Samsung, Huawei, Hisilicon | imported from 3GU |
S6‑202030 | User Plane Path Management event and notification enhancement | Huawei, Hisilicon | imported from 3GU |
S6‑202031 | Pseudo-CR on Service Continuity Support Indication | Sony | imported from 3GU |
S6‑202032 | Pseudo-CR on Application Context Relocation Decision Making | Sony | imported from 3GU |
S6‑202033 | EEC detection in application context relocation | Samsung, InterDigital | imported from 3GU |
S6‑202034 | User plane connectivity modification in S-EES executed ACR | Samsung | imported from 3GU |
S6‑202035 | Support AEF location and API invoker interface for edge application | Ericsson | imported from 3GU |
S6‑202036 | New WID for enhanced Service Enabler Architecture Layer for Verticals | Samsung | imported from 3GU |
page generated from database: 2024-07-20 12:15:34