3GPP TDocs (written contributions) at meeting
Meeting: S6-48-e - 2022-04-05 to 2022-04-14, Online
meeting id: S6-48-e (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| S6‑220566 | FS_NSCALE_Evaluation of Solution 10 | China Mobile (Hangzhou) Inf. | imported from 3GU |
| S6‑220567 | Update Solution #12 | Samsung | imported from 3GU |
| S6‑220568 | Updates to architectural requirements for EAS Service APIs | ETRI, Uangel | imported from 3GU |
| S6‑220569 | Solution #8 update: ENs and evaluation | ETRI, Uangel | imported from 3GU |
| S6‑220570 | S6-eEDGEAPP_Solution for KI#5 | China Mobile E-Commerce Co. | imported from 3GU |
| S6‑220571 | Solution for KI#3 | Samsung | imported from 3GU |
| S6‑220572 | S6-eEDGEAPP_Update Solution #8 | China Mobile E-Commerce Co. | imported from 3GU |
| S6‑220573 | LS Reply on ECS provider identification in ECS address provisioning | vivo | imported from 3GU |
| S6‑220574 | Solution for KI#1 – Creation of PIN | vivo | imported from 3GU |
| S6‑220575 | Solution for KI#1 – Determination of the role: PEMC | vivo | imported from 3GU |
| S6‑220576 | New KI on service switch in PIN | vivo | imported from 3GU |
| S6‑220577 | New KI on service continuity | vivo | imported from 3GU |
| S6‑220578 | FS_NSCALE architectural requirements | AsiaInfo Technologies Inc | imported from 3GU |
| S6‑220579 | network slice optimization based on AF policy | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220580 | Deployment models | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220581 | application architecture updata | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220582 | architecture requirement update | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220583 | Identities and commonly used values | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220584 | overall evaluation | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220585 | Solution to KI #11 on application layer slice SLA alignment capability | AsiaInfo Technologies Inc,Huawei,CMCC | imported from 3GU |
| S6‑220586 | solution for KI 1 | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220587 | Interaction between the centralized NSCE server and edge NSCE server | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220588 | solution evaluation for solution 6 | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220589 | solution evaluation for solution 7 | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220590 | Delete the EN in solution 8 | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220591 | Delete the EN in solution 9 | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220592 | Correction of figure title in solution 3 | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220593 | Clarification on general description for Solution #3 | NTT DOCOMO | imported from 3GU |
| S6‑220594 | Functional model description to support 3rd party API providers with SNA | NTT DOCOMO | imported from 3GU |
| S6‑220595 | Obtaining resource owner consent in a cascade API invocation | NTT DOCOMO | imported from 3GU |
| S6‑220596 | Key Issue for the resource owner authentication | NTT DOCOMO | imported from 3GU |
| S6‑220597 | 3GPP authentication for the resource owner | NTT DOCOMO | imported from 3GU |
| S6‑220598 | Solution #3 evaluation | NTT DOCOMO | imported from 3GU |
| S6‑220599 | Solution #4 evaluation | NTT DOCOMO | imported from 3GU |
| S6‑220600 | Overall evaluation | NTT DOCOMO | imported from 3GU |
| S6‑220601 | FS_eEDGEAPP the procedure for solution #11 EASs to invoke MEC services API using CAPIF | AsiaInfo Technologies Inc | imported from 3GU |
| S6‑220602 | FS_NSCALE_evaluation of solution of communication service management exposure | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| S6‑220603 | FS_NSCALE_Update mapping of Solutions to Key Issues | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| S6‑220604 | Application architecture enhancement of broadcast aspect | Huawei, Hisilicon | imported from 3GU |
| S6‑220605 | Broadcast Message delivery procedure | Huawei, Hisilicon | imported from 3GU |
| S6‑220606 | Charging architectural requirements | Huawei, Hisilicon | imported from 3GU |
| S6‑220607 | Delete the example of the originator address in Table 8.11.5-1 | Huawei, Hisilicon | imported from 3GU |
| S6‑220608 | Editoral corrections | Huawei, Hisilicon | imported from 3GU |
| S6‑220609 | eEDGEAPP_new KI on Enhancement of EES | China Mobile E-Commerce Co. | imported from 3GU |
| S6‑220610 | Clarification of MC gateway UE selection | BDBOS, Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑220611 | Clarifications related to multi carrier support for MBS session creation and announcement | Ericsson | imported from 3GU |
| S6‑220612 | Clarifications related to multi carrier support for MBS session update | Ericsson | imported from 3GU |
| S6‑220613 | Update to service continuity procedure from an MBS session to 5G ProSe UE-to-network relay | Ericsson | imported from 3GU |
| S6‑220614 | Update to service continuity procedure from 5G ProSe UE-to-network relay to an MBS session | Ericsson | imported from 3GU |
| S6‑220615 | Requirements related to 5G ProSe Layer-3 relaying via N3IWF | Ericsson | imported from 3GU |
| S6‑220616 | FS_NSCALE_evalution of solution of dynamic slice alignment | HUAWEI TECHNOLOGIES Co. Ltd., AsiaInfo | imported from 3GU |
| S6‑220617 | FS_NSCALE_summary on KIs for NSCE | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| S6‑220618 | Removal of Gate Control EN | Ericsson España S.A. | imported from 3GU |
| S6‑220619 | pCR on introduction of general architecture requirements | BDBOS | imported from 3GU |
| S6‑220620 | pCR on introduction of user and group authorization requirements | BDBOS | imported from 3GU |
| S6‑220621 | Update the description for solution #11 EASs to invoke MEC services API using CAPIF | AsiaInfo Technologies Inc | imported from 3GU |
| S6‑220622 | FS_eEDGEAPP the procedure for solution #11 EASs to invoke MEC services API using CAPIF | AsiaInfo Technologies Inc | imported from 3GU |
| S6‑220623 | pCR on Solution proposal for Key issue #17: Discovery of a common EAS | Apple GmbH | imported from 3GU |
| S6‑220624 | S6-eDGEAPP_Update Solution 8 | China Mobile E-Commerce Co. | imported from 3GU |
| S6‑220625 | Pseudo-CR on new solution for CAPIF adaptation | Ericsson | imported from 3GU |
| S6‑220626 | Fix S-EAS decided ACR | Ericsson | imported from 3GU |
| S6‑220627 | Solve EN in UE ID API | Ericsson | imported from 3GU |
| S6‑220628 | ACR between CAS and EAS | Ericsson | imported from 3GU |
| S6‑220629 | Common EAS selection solution | Ericsson | imported from 3GU |
| S6‑220630 | Add CAPIF-11 | Ericsson | imported from 3GU |
| S6‑220631 | Support simultaneous EAS Connectivity in ACR | Ericsson | imported from 3GU |
| S6‑220632 | New KI Simultaneous EAS Connectivity in ACR | Ericsson | imported from 3GU |
| S6‑220633 | Application Server monitoring via CAPIF | Ericsson | imported from 3GU |
| S6‑220634 | Reply LS on AF specific UE ID retrieval | SA6 | imported from 3GU |
| S6‑220635 | S6-eEDGEAPP_Solution for KI#1- Enhanced notification service to the EEC | China Mobile E-Commerce Co. | imported from 3GU |
| S6‑220636 | bulk registration for constrained device over MSGin5G-6 reference point | China Mobile Com. Corporation | imported from 3GU |
| S6‑220637 | Values and usage of Priority type | China Mobile Com. Corporation | imported from 3GU |
| S6‑220638 | S6-eEDGEAPP_Solution for KI#12- EEL service differentiation | China Mobile E-Commerce Co. | imported from 3GU |
| S6‑220639 | message aggregation and segment | China Mobile Com. Corporation | imported from 3GU |
| S6‑220640 | DP on potential topics and planned work | Lenovo Future Communications | imported from 3GU |
| S6‑220641 | Solution proposal for the configuration parameters required for Ad hoc group communication | Samsung | imported from 3GU |
| S6‑220642 | Key Issue on API related analytics | Lenovo Future Communications | imported from 3GU |
| S6‑220643 | update of MSGin5G group management | China Mobile Com. Corporation | imported from 3GU |
| S6‑220644 | Key Issue on support for analytics related to slicing | Lenovo Future Communications | imported from 3GU |
| S6‑220645 | Key Issue on CAPIF enhancements | Lenovo Future Communications | imported from 3GU |
| S6‑220646 | Key Issue on DN related energy analytics | Lenovo Future Communications | imported from 3GU |
| S6‑220647 | Solution proposal for MC service server determining the participants list for ad hoc group communication | Samsung, Kontron Transportation France, Nokia, Nokia Shanghai Bell, FirstNet | imported from 3GU |
| S6‑220648 | update of abbreviations | China Mobile Com. Corporation | imported from 3GU |
| S6‑220649 | Solution to KI #1 - support for application performance analytics | Lenovo Future Communications | imported from 3GU |
| S6‑220650 | Solution to KI #2 - support for edge analytics | Lenovo Future Communications | imported from 3GU |
| S6‑220651 | Evaluation of solution #3 | Lenovo Future Communications | imported from 3GU |
| S6‑220652 | Solution#8 update and evaluation | Lenovo Future Communications | imported from 3GU |
| S6‑220653 | SEAL Notification Management service – Functional Model | Samsung, AT&T | imported from 3GU |
| S6‑220654 | Solution to KI #2 - Support for USS re-mapping for a UAS | Lenovo Future Communications | imported from 3GU |
| S6‑220655 | Discussion on fused location service architecture | CATT | imported from 3GU |
| S6‑220656 | Pseudo-CR on solution#1 update | CATT | imported from 3GU |
| S6‑220657 | Pseudo-CR on solution for supporting geo-fencing applications | CATT | imported from 3GU |
| S6‑220658 | Pseudo-CR on update on solution #2 | CATT | imported from 3GU |
| S6‑220659 | Pseudo-CR on solution for supporting location QoS | CATT | imported from 3GU |
| S6‑220660 | Solution to KI #1 on VRU zone provisioning | Lenovo Future Communications | imported from 3GU |
| S6‑220661 | Key Issue on trust enablement for automated V2X transactions | Lenovo Future Communications | imported from 3GU |
| S6‑220662 | Minor essential corrections to TS 23.434 | Samsung | imported from 3GU |
| S6‑220663 | Pseudo-CR on solution to KI#13 - Edge enabler layer support for EAS synchronization | Samsung | imported from 3GU |
| S6‑220664 | Pseudo-CR on solution to KI#3 | Samsung | imported from 3GU |
| S6‑220665 | Corrections to the use of MC service system | AT&T GNS Belgium SPRL | imported from 3GU |
| S6‑220666 | Implicit registration handling in service continuity | Samsung | imported from 3GU |
| S6‑220667 | Discussion on fused location service architecture | CATT | imported from 3GU |
| S6‑220668 | Pseudo-CR on solution#1 update | CATT | imported from 3GU |
| S6‑220669 | Pseudo-CR on solution for supporting geo-fencing applications | CATT | imported from 3GU |
| S6‑220670 | Pseudo-CR on update on solution #2 | CATT | imported from 3GU |
| S6‑220671 | Pseudo-CR on solution for supporting location QoS | CATT | imported from 3GU |
| S6‑220672 | Replay LS on query on EEC Registration Update procedure | Samsung Electronics Nordic AB | imported from 3GU |
| S6‑220673 | Corrections to the use of MC service system | AT&T GNS Belgium SPRL | imported from 3GU |
| S6‑220674 | Corrections to the use of MC service system | AT&T GNS Belgium SPRL | imported from 3GU |
| S6‑220675 | Corrections to the use of MC service system | AT&T GNS Belgium SPRL | imported from 3GU |
| S6‑220676 | Corrections to the use of MC service system | AT&T GNS Belgium SPRL | imported from 3GU |
| S6‑220677 | Update to EEC registration update procedure | Samsung Electronics Nordic AB | imported from 3GU |
| S6‑220678 | MCPTT-5 for 5GS | AT&T GNS Belgium SPRL | imported from 3GU |
| S6‑220679 | 2024 Meeting Calendar | SA6 Chair | imported from 3GU |
| S6‑220680 | Chair or Qualcomm Input | Qualcomm Incorporated | imported from 3GU |
| S6‑220681 | Meetings Calls Discussion | SA6 Chair | imported from 3GU |
| S6‑220682 | Pseudo-CR on solution to KI#14 | Samsung Electronics Benelux BV | imported from 3GU |
| S6‑220683 | 6.x NS Info delivery general | Samsung Electronics | imported from 3GU |
| S6‑220684 | 6.x.1.2 NS Info delivery | Samsung Electronics | imported from 3GU |
| S6‑220685 | 6.x.1.3 NS Info subscription | Samsung Electronics | imported from 3GU |
| S6‑220686 | 6.x.1.4 NS Info Notify | Samsung Electronics | imported from 3GU |
| S6‑220687 | 6.x.1.5 NS Info delivery in Registration phase | Samsung Electronics | imported from 3GU |
| S6‑220688 | 6.x NS Allocation by VAL server | Samsung Electronics | imported from 3GU |
| S6‑220689 | solution evaluation for solution 9 | Samsung | imported from 3GU |
| S6‑220690 | Corrections in MBS UE session join notification | Samsung R&D Institute India/Kiran | imported from 3GU |
| S6‑220691 | Small editorial corrections | Samsung R&D Institute India/Kiran | imported from 3GU |
| S6‑220692 | Update to 5G MBS service announcement | Samsung R&D Institute India/Kiran | imported from 3GU |
| S6‑220693 | Update to broadcast MBS sessions monitoring and the reception quality of the MBS session | Samsung R&D Institute India/Kiran | imported from 3GU |
| S6‑220694 | EDGE-5 APIs | Qualcomm | imported from 3GU |
| S6‑220695 | Federation and roaming | Qualcomm | imported from 3GU |
| S6‑220696 | Linked EASs | Qualcomm | imported from 3GU |
| S6‑220697 | UE identification with NAT | Qualcomm | imported from 3GU |
| S6‑220698 | ECS configuration information | Qualcomm | imported from 3GU |
| S6‑220699 | Reply LS on ECS provider identification in ECS address provisioning | Qualcomm | imported from 3GU |
| S6‑220700 | Update to remotely initiated call request procedure to support pre-emptive or high priority and commencement mode | Samsung R&D Institute India/Kiran | imported from 3GU |
| S6‑220701 | Added MC GW UnMapGroupToBearer request and response support | Samsung R&D Institute India/Kiran | imported from 3GU |
| S6‑220702 | Corrections to EEC context and ACR | Huawei, Hisilicon | imported from 3GU |
| S6‑220703 | Corrections for selected T-EAS declaration | Huawei, Hisilicon | imported from 3GU |
| S6‑220704 | Corrections for incomplete functions of ECS and EDGE-6 | Huawei, Hisilicon | imported from 3GU |
| S6‑220705 | Corrections to ACT status subscription and notification | Huawei, Hisilicon | imported from 3GU |
| S6‑220706 | Sharing location information across VAL servers | Huawei, Hisilicon | imported from 3GU |
| S6‑220707 | Usage of SEAL in FFAPP | Huawei, Hisilicon | imported from 3GU |
| S6‑220708 | Deployment of FFAPP with Edge Enabler Layer | Huawei, Hisilicon | imported from 3GU |
| S6‑220709 | Resolve the EN about architecture and reference alignment in clause 4.7.1 | Huawei, Hisilicon | imported from 3GU |
| S6‑220710 | Resolve the EN in clause 5.2 | Huawei, Hisilicon | imported from 3GU |
| S6‑220711 | Resolve the EN on SA4 aspect | Huawei, Hisilicon | imported from 3GU |
| S6‑220712 | Discussion on Clarifications regarding SEALDD architecture | Huawei, Hisilicon | imported from 3GU |
| S6‑220713 | Update to KI #5: SEALDD enabled Data Storage | Huawei, Hisilicon | imported from 3GU |
| S6‑220714 | Update to SEALDD architecture for traffic flow description | Huawei, Hisilicon | imported from 3GU |
| S6‑220715 | Solution on KI#4: SEALDD integrating MSGin5G for message transfer | Huawei, Hisilicon | imported from 3GU |
| S6‑220716 | Solution on KI#6: SEALDD server discovery and selection for specific EAS | Huawei, Hisilicon | imported from 3GU |
| S6‑220717 | Solution on KI#7: SEALDD server discovery and selection for specific VAL server | Huawei, Hisilicon | imported from 3GU |
| S6‑220718 | Enhancement to Solution on ACR scenario combination | Huawei, Hisilicon | imported from 3GU |
| S6‑220719 | Key issue on EAS discovery in Edge Node sharing scenario | Huawei, Hisilicon | imported from 3GU |
| S6‑220720 | Solution for EAS discovery in Edge Node sharing scenario | Huawei, Hisilicon | imported from 3GU |
| S6‑220721 | Solution for selection of one common EAS for a group of Ues | Huawei, Hisilicon | imported from 3GU |
| S6‑220722 | Solution for T-EAS discovery for linkage of AC with multiple EAS(s) | Huawei, Hisilicon | imported from 3GU |
| S6‑220723 | Solution for T-EAS discovery in Edge Node sharing scenario | Huawei, Hisilicon | imported from 3GU |
| S6‑220724 | Evaluation of solution #17 | Huawei, Hisilicon | imported from 3GU |
| S6‑220725 | Evaluation of solution #19 | Huawei, Hisilicon | imported from 3GU |
| S6‑220726 | Overall Evaluation of key issue#14 | Huawei, Hisilicon | imported from 3GU |
| S6‑220727 | Solution for KI#3 - Enhancements to service continuity planning with prediction expiration time | Huawei, Hisilicon | imported from 3GU |
| S6‑220728 | Evaluation of Solution#4 | Huawei, Hisilicon | imported from 3GU |
| S6‑220729 | Evaluation of Solution#5 | Huawei, Hisilicon | imported from 3GU |
| S6‑220730 | Evaluation of Solution #6 - ACR update in service continuity planning | Huawei, Hisilicon | imported from 3GU |
| S6‑220731 | Solution for ACR scenario selection for linkage EAS(s) | Huawei, Hisilicon | imported from 3GU |
| S6‑220732 | Resolving location of ROAF in CAPIF | Huawei, Hisilicon | imported from 3GU |
| S6‑220733 | Solution for V2X service deployment with Edge Enabler Layer | Huawei, Hisilicon | imported from 3GU |
| S6‑220734 | Revised SID for Study on enhancements to application layer support for V2X services; Phase 2 | Huawei, Hisilicon | imported from 3GU |
| S6‑220735 | Revised SID for Study on SEAL data delivery enabler for vertical application | Huawei, Hisilicon | imported from 3GU |
| S6‑220736 | Pseudo-CR on Solution to KI#11 | Samsung | imported from 3GU |
| S6‑220737 | Pseudo-CR on Solution to KI#17 | Samsung | imported from 3GU |
| S6‑220738 | FS eEDGEAPP Work plan | Samsung | imported from 3GU |
| S6‑220739 | FS 5GFLS Way forward | Samsung | imported from 3GU |
| S6‑220740 | Pseudo-CR on update to solution#3 | Samsung | imported from 3GU |
| S6‑220741 | Pseudo-CR on Update to Solution #6 | Samsung | imported from 3GU |
| S6‑220742 | update to solution 1 | Samsung | imported from 3GU |
| S6‑220743 | New solution for enhancements to service continuity planning | KPN N.V., Ericsson | imported from 3GU |
| S6‑220744 | Extended Architecture for ACR between EAS and CAS | KPN N.V. | imported from 3GU |
| S6‑220745 | Data storage solution | Convida Wireless LLC | imported from 3GU |
| S6‑220746 | Reply LS to 3GPP on MEC Federation and interest to collaborate | SA6 | imported from 3GU |
| S6‑220747 | SA6 Meeting #48-e - Agenda with Tdocs allocation at start of the meeting | SA6 Chair | imported from 3GU |
| S6‑220748 | Issues on usage of ACR with LADNs | InterDigital, Europe, Ltd. | imported from 3GU |
| S6‑220749 | Minor essential corrections to TS 23.434 | Samsung | imported from 3GU |
| S6‑220750 | LS on network slice LCM consumption and use cases | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220751 | Comparison of solutions for Common EAS Selection | Samsung | imported from 3GU |
| S6‑220752 | LS on PIN Application Server Discovery | InterDigital Communications | imported from 3GU |
| S6‑220753 | Clean-up of clause 11 specifying MC gateway UE support | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S6‑220754 | Clarification regarding the protocol used on new reference points | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑220755 | Clarify the association between certain entities | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑220756 | Migration during an ongoing group communication | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑220757 | Migration during an ongoing private communication | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑220758 | Private call using functional alias towards a partner MC system | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
| S6‑220759 | Clarifications related to multi carrier support for MBS session creation and announcement | Ericsson | imported from 3GU |
| S6‑220760 | Clarifications related to multi carrier support for MBS session update | Ericsson, Huawei | imported from 3GU |
| S6‑220761 | Update to service continuity procedure from an MBS session to 5G ProSe UE-to-network relay | Ericsson | imported from 3GU |
| S6‑220762 | Update to service continuity procedure from 5G ProSe UE-to-network relay to an MBS session | Ericsson, Samsung | imported from 3GU |
| S6‑220763 | Requirements related to 5G ProSe Layer-3 relaying via N3IWF | Ericsson | imported from 3GU |
| S6‑220764 | Corrections in MBS UE session join notification | Samsung R&D Institute India/Kiran | imported from 3GU |
| S6‑220765 | Small editorial corrections | Samsung R&D Institute India/Kiran | imported from 3GU |
| S6‑220766 | Update to 5G MBS service announcement | Samsung R&D Institute India/Kiran | imported from 3GU |
| S6‑220767 | Update to broadcast MBS sessions monitoring and the reception quality of the MBS session | Samsung R&D Institute India/Kiran | imported from 3GU |
| S6‑220768 | Update to remotely initiated call request procedure to support pre-emptive or high priority and commencement mode | Samsung R&D Institute India/Kiran | imported from 3GU |
| S6‑220769 | Updates on Solution #3 | Samsung | imported from 3GU |
| S6‑220770 | Update Solution #12 | Samsung | imported from 3GU |
| S6‑220771 | Clarification on general description for Solution #3 | NTT DOCOMO | imported from 3GU |
| S6‑220772 | Functional model description to support 3rd party API providers with SNA | NTT DOCOMO, Deutsche Telekom | imported from 3GU |
| S6‑220773 | Reducing resource owner consent inquiry in a nested API invocation | NTT DOCOMO | imported from 3GU |
| S6‑220774 | Solution #3 evaluation | NTT DOCOMO | imported from 3GU |
| S6‑220775 | Solution #4 evaluation | NTT DOCOMO | imported from 3GU |
| S6‑220776 | Overall evaluation | NTT DOCOMO | imported from 3GU |
| S6‑220777 | Update for key Issue 1 Ad hoc group communication | Kontron Transportation France, UIC, Nokia, Nokia Shanghai Bell, Samsung | imported from 3GU |
| S6‑220778 | Pseudo-CR on Solution evaluation for solution 6: VAL server authorization and authentication via slice enabler layer | Huawei Tech.(UK) Co.. Ltd | imported from 3GU |
| S6‑220779 | discussion on bulk registration over MSGin5G-6 | China Mobile Com. Corporation | imported from 3GU |
| S6‑220780 | Clarification on general description for Solution #3 | NTT DOCOMO, AT&T | imported from 3GU |
| S6‑220781 | bulk registration for constrained device over MSGin5G-6 reference point | China Mobile Com. Corporation | imported from 3GU |
| S6‑220782 | application architecture updata | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220783 | Pseudo-CR on Solution evaluation for solution 6: VAL server authorization and authentication via slice enabler layer | Huawei Tech.(UK) Co.. Ltd | imported from 3GU |
| S6‑220784 | architecture requirement update | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220785 | Identities and commonly used values | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220786 | overall evaluation | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220787 | solution for KI 1 | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220788 | Interaction between the centralized NSCE server and edge NSCE server | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220789 | solution evaluation for solution 6 | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220790 | solution evaluation for solution 7 | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220791 | Correction of figure title in solution 3 | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220792 | LS on network slice LCM consumption and use cases | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220793 | FS_NSCALE architectural requirements | AsiaInfo Technologies Inc | imported from 3GU |
| S6‑220794 | network slice optimization based on AF policy | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220795 | Deployment models | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220796 | Values and usage of Priority type | China Mobile Com. Corporation | imported from 3GU |
| S6‑220797 | MC gateway UE – MC client disassociation procedure | Union Inter. Chemins de Fer, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S6‑220798 | Solution to KI #11 on application layer slice SLA alignment capability | AsiaInfo Technologies Inc,Huawei,CMCC | imported from 3GU |
| S6‑220799 | message aggregation and segment | China Mobile Com. Corporation | imported from 3GU |
| S6‑220800 | update of MSGin5G group management | China Mobile Com. Corporation | imported from 3GU |
| S6‑220801 | Reply LS to 3GPP on MEC Federation and interest to collaborate | SA6 | imported from 3GU |
| S6‑220802 | Solution proposal for the configuration parameters required for Ad hoc group communication | Samsung | imported from 3GU |
| S6‑220803 | Solution for KI#1 – PINAPP architecture and PIN management | vivo, Samsung | imported from 3GU |
| S6‑220804 | Solution for KI#1 – Determination of PEMC to the UE | vivo | imported from 3GU |
| S6‑220805 | New KI on service switch in PIN | vivo | imported from 3GU |
| S6‑220806 | New KI on service continuity | vivo | imported from 3GU |
| S6‑220807 | Solution proposal for MC service server determining the participants list for ad hoc group communication | Samsung, Kontron Transportation France, Nokia, Nokia Shanghai Bell, FirstNet | imported from 3GU |
| S6‑220808 | SEAL Notification Management service – Functional Model | Samsung, AT&T | imported from 3GU |
| S6‑220809 | Minor essential corrections to TS 23.434 | Samsung | imported from 3GU |
| S6‑220810 | update of abbreviations | China Mobile Com. Corporation | imported from 3GU |
| S6‑220811 | Evaluation of Solution 10 | China Mobile (Hangzhou) Inf. | imported from 3GU |
| S6‑220812 | FS_NSCALE_evaluation of solution of communication service management exposure | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
| S6‑220813 | Cleanups of the procedures for Solution #1 | InterDigital | imported from 3GU |
| S6‑220814 | Evaluation of Solution #1 | InterDigital | imported from 3GU |
| S6‑220815 | Evaluation of solution #3 | Lenovo, Huawei | imported from 3GU |
| S6‑220816 | Solution#8 update and evaluation | Lenovo, Huawei, CMCC | imported from 3GU |
| S6‑220817 | Solution to KI #1 on VRU zone provisioning | Lenovo Future Communications | imported from 3GU |
| S6‑220818 | Key Issue on support for analytics related to slicing | Lenovo Future Communications | imported from 3GU |
| S6‑220819 | Solution to KI #1 - support for application performance analytics | Lenovo Future Communications | imported from 3GU |
| S6‑220820 | Solution to KI #2 - support for edge analytics | Lenovo Future Communications | imported from 3GU |
| S6‑220821 | Solution to KI #2 - Support for USS re-mapping for a UAS | Lenovo Future Communications | imported from 3GU |
| S6‑220822 | Update to solution #14 | InterDigital | imported from 3GU |
| S6‑220823 | Solution for KI#17 – Common EAS | InterDigital | imported from 3GU |
| S6‑220824 | Solution for KI#19 – ACR selection and coordination | InterDigital, Ericsson, Samsung | imported from 3GU |
| S6‑220825 | Application architecture enhancement of broadcast aspect | Huawei, Hisilicon | imported from 3GU |
| S6‑220826 | Broadcast Message delivery procedure | Huawei, Hisilicon | imported from 3GU |
| S6‑220827 | Charging architectural requirements | Huawei, Hisilicon | imported from 3GU |
| S6‑220828 | Delete the example of the originator address in Table 8.11.5-1 | Huawei, Hisilicon | imported from 3GU |
| S6‑220829 | Editoral corrections | Huawei, Hisilicon | imported from 3GU |
| S6‑220830 | Update Annex A.4- ETSI MEC and EDGEAPP system comparison | China Mobile E-Commerce Co. | imported from 3GU |
| S6‑220831 | Update Solution #8 | China Mobile E-Commerce Co. | imported from 3GU |
| S6‑220832 | eEDGEAPP_update KI#2 | China Mobile E-Commerce Co. | imported from 3GU |
| S6‑220833 | Update Solution 8 | China Mobile E-Commerce Co. | imported from 3GU |
| S6‑220834 | pCR on Solution proposal for Key issue #17: Discovery of a common EAS | Apple GmbH | imported from 3GU |
| S6‑220835 | Removal of the Editor's Note on dynamic EAS instantiation information | InterDigital, Samsung | imported from 3GU |
| S6‑220836 | 6.x NS Info delivery general | Samsung Electronics | imported from 3GU |
| S6‑220837 | 6.x.1.2 NS Info delivery | Samsung Electronics | imported from 3GU |
| S6‑220838 | 6.x.1.3 NS Info subscription | Samsung Electronics | imported from 3GU |
| S6‑220839 | 6.x.1.4 NS Info Notify | Samsung Electronics | imported from 3GU |
| S6‑220840 | 6.x.1.5 NS Info delivery in Registration phase | Samsung Electronics | imported from 3GU |
| S6‑220841 | 6.x NS Allocation by VAL server | Samsung Electronics | imported from 3GU |
| S6‑220842 | Pseudo-CR on solution#1 update | CATT | imported from 3GU |
| S6‑220843 | Pseudo-CR on solution for supporting geo-fencing applications | CATT | imported from 3GU |
| S6‑220844 | Pseudo-CR on update on solution #2 | CATT | imported from 3GU |
| S6‑220845 | Pseudo-CR on solution for supporting location QoS | CATT | imported from 3GU |
| S6‑220846 | Pseudo-CR on solution to KI#14 | Samsung Electronics Benelux BV | imported from 3GU |
| S6‑220847 | Issues on usage of ACR with LADNs | InterDigital | imported from 3GU |
| S6‑220848 | LS on FS_eEDGEAPP, Solution for Dynamic EAS instantiation | InterDigital | imported from 3GU |
| S6‑220849 | Solution for KI#9 - Enhancement of dynamic EAS instantiation triggering | InterDigital, Ericsson, Samsung | imported from 3GU |
| S6‑220850 | LS on Issues using Application Context Relocation with Local Area Data Networks | InterDigital | imported from 3GU |
| S6‑220851 | New KI on PIN Application Server Discovery | InterDigital | imported from 3GU |
| S6‑220852 | LS on PIN Application Server Discovery | InterDigital Communications | imported from 3GU |
| S6‑220853 | EDGE-5 APIs | Qualcomm | imported from 3GU |
| S6‑220854 | Federation and roaming | Qualcomm | imported from 3GU |
| S6‑220855 | Linked EASs | Qualcomm | imported from 3GU |
| S6‑220856 | UE identification with NAT | Qualcomm, KPN N.V., Ericsson | imported from 3GU |
| S6‑220857 | ECS configuration information | Qualcomm, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S6‑220858 | Reply LS on ECS provider identification in ECS address provisioning | Qualcomm | imported from 3GU |
| S6‑220859 | Removal of Gate Control EN | Ericsson España S.A. | imported from 3GU |
| S6‑220860 | Key Issue on DN related energy analytics | Lenovo Future Communications | imported from 3GU |
| S6‑220861 | New solution for enhancements to service continuity planning | KPN N.V., Ericsson | imported from 3GU |
| S6‑220862 | Change ROAF to AF | Ericsson | imported from 3GU |
| S6‑220863 | Application Server monitoring via CAPIF | Ericsson | imported from 3GU |
| S6‑220864 | ACR between CAS and EAS | Ericsson, KPN | imported from 3GU |
| S6‑220865 | Reply LS on AF specific UE ID retrieval | SA6 | imported from 3GU |
| S6‑220866 | Solve EN in UE ID API | Ericsson | imported from 3GU |
| S6‑220867 | Fix S-EAS decided ACR | Ericsson | imported from 3GU |
| S6‑220868 | Support simultaneous EAS Connectivity in ACR | Ericsson | imported from 3GU |
| S6‑220869 | Common EAS selection solution | Ericsson | imported from 3GU |
| S6‑220870 | Pseudo-CR on Solution to KI#11 | Samsung, Qualcomm | imported from 3GU |
| S6‑220871 | Pseudo-CR on Solution to KI#17 | Samsung | imported from 3GU |
| S6‑220872 | Pseudo-CR on update to solution#3 | Samsung | imported from 3GU |
| S6‑220873 | Pseudo-CR on Update to Solution #6 | Samsung | imported from 3GU |
| S6‑220874 | Pseudo-CR on solution to KI#13 - Edge enabler layer support for EAS synchronization | Samsung | imported from 3GU |
| S6‑220875 | Pseudo-CR on solution to KI#3 | Samsung | imported from 3GU |
| S6‑220876 | Implicit registration handling in service continuity | Samsung | imported from 3GU |
| S6‑220877 | Replay LS on query on EEC Registration Update procedure | Samsung Electronics Nordic AB | imported from 3GU |
| S6‑220878 | Update to EEC registration update procedure | Samsung Electronics Nordic AB | imported from 3GU |
| S6‑220879 | update to solution 1 | Samsung | imported from 3GU |
| S6‑220880 | Corrections to EEC context and ACR | Huawei, Hisilicon | imported from 3GU |
| S6‑220881 | Corrections for selected T-EAS declaration | Huawei, Hisilicon | imported from 3GU |
| S6‑220882 | Corrections for incomplete functions of ECS and EDGE-6 | Huawei, Hisilicon | imported from 3GU |
| S6‑220883 | Corrections to ACT status subscription and notification | Huawei, Hisilicon | imported from 3GU |
| S6‑220884 | Sharing location information across VAL servers | Huawei, Hisilicon | imported from 3GU |
| S6‑220885 | Usage of SEAL in FFAPP | Huawei, Hisilicon | imported from 3GU |
| S6‑220886 | Deployment of FFAPP with Edge Enabler Layer | Huawei, Hisilicon | imported from 3GU |
| S6‑220887 | Resolve the EN in clause 5.2 | Huawei, Hisilicon | imported from 3GU |
| S6‑220888 | Resolve the EN on SA4 aspect | Huawei, Hisilicon | imported from 3GU |
| S6‑220889 | Update to SEALDD architecture for traffic flow description | Huawei, Hisilicon | imported from 3GU |
| S6‑220890 | Solution on KI#4: SEALDD integrating MSGin5G for message transfer | Huawei, Hisilicon | imported from 3GU |
| S6‑220891 | Solution on KI#6: SEALDD server discovery and selection for specific EAS | Huawei, Hisilicon | imported from 3GU |
| S6‑220892 | Solution on KI#7: SEALDD server discovery and selection for specific VAL server | Huawei, Hisilicon | imported from 3GU |
| S6‑220893 | Enhancement to Solution on ACR scenario combination | Huawei, Hisilicon | imported from 3GU |
| S6‑220894 | Key issue on EAS discovery in Edge Node sharing scenario | Huawei, Hisilicon | imported from 3GU |
| S6‑220895 | Solution for selection of one common EAS for a group of UEs | Huawei, Hisilicon | imported from 3GU |
| S6‑220896 | Solution for T-EAS discovery for linkage of AC with multiple EAS(s) | Huawei, Hisilicon | imported from 3GU |
| S6‑220897 | Evaluation of solution #17 | Huawei, Hisilicon | imported from 3GU |
| S6‑220898 | Evaluation of solution #19 | Huawei, Hisilicon | imported from 3GU |
| S6‑220899 | Overall Evaluation of key issue#14 | Huawei, Hisilicon | imported from 3GU |
| S6‑220900 | Evaluation of Solution#4 | Huawei, Hisilicon | imported from 3GU |
| S6‑220901 | Evaluation of Solution#5 | Huawei, Hisilicon | imported from 3GU |
| S6‑220902 | Solution for ACR scenario selection for linkage EAS(s) | Huawei, Hisilicon | imported from 3GU |
| S6‑220903 | Resolving location of ROAF in CAPIF | Huawei, Hisilicon | imported from 3GU |
| S6‑220904 | Solution for V2X service deployment with Edge Enabler Layer | Huawei, Hisilicon | imported from 3GU |
| S6‑220905 | Corrections to EEC context and ACR | Huawei, Hisilicon | imported from 3GU |
| S6‑220906 | Corrections for selected T-EAS declaration | Huawei, Hisilicon | imported from 3GU |
| S6‑220907 | Corrections for incomplete functions of ECS and EDGE-6 | Huawei, Hisilicon | imported from 3GU |
| S6‑220908 | Corrections to ACT status subscription and notification | Huawei, Hisilicon | imported from 3GU |
| S6‑220909 | Sharing location information across VAL servers | Huawei, Hisilicon | imported from 3GU |
| S6‑220910 | Resolve the EN in clause 5.2 | Huawei, Hisilicon | imported from 3GU |
| S6‑220911 | Resolve the EN on SA4 aspect | Huawei, Hisilicon | imported from 3GU |
| S6‑220912 | Update to SEALDD architecture for traffic flow description | Huawei, Hisilicon | imported from 3GU |
| S6‑220913 | Updates to architectural requirements for EAS Service APIs | ETRI, Uangel | imported from 3GU |
| S6‑220914 | Solution #8 update: ENs and evaluation | ETRI, Uangel | imported from 3GU |
| S6‑220915 | EAS selection synchronization at registration | Convida Wireless LLC | imported from 3GU |
| S6‑220916 | ECS Publish Discovery CAPIF | Convida Wireless LLC, Deutsche Telekom | imported from 3GU |
| S6‑220917 | AC Association | Convida Wireless LLC | imported from 3GU |
| S6‑220918 | Redundant transport solution | Convida Wireless LLC | imported from 3GU |
| S6‑220919 | Data storage solution | Convida Wireless LLC | imported from 3GU |
| S6‑220920 | UE API Invoker onboarding KI | Convida Wireless LLC | imported from 3GU |
| S6‑220921 | UE API Invoker onboarding solution | Convida Wireless LLC | imported from 3GU |
| S6‑220922 | RO registration via AF | Convida Wireless LLC | imported from 3GU |
| S6‑220923 | Enhanced API Invocation using RO consent | Convida Wireless LLC | imported from 3GU |
| S6‑220924 | KI1 Update UE triggered NS adaptation | Convida Wireless LLC | imported from 3GU |
| S6‑220925 | Data analytics enablement solution | Convida Wireless LLC | imported from 3GU |
| S6‑220926 | Update FFA-2 based on notification | Convida Wireless LLC | imported from 3GU |
| S6‑220927 | Update FFA-2 based on service requirements | Convida Wireless LLC | imported from 3GU |
| S6‑220928 | UE activity pattern and monitoring solution | Convida Wireless LLC | imported from 3GU |
| S6‑220929 | Revised WID eSEAL2 update for FS_ACE_IoT | Convida Wireless LLC | imported from 3GU |
| S6‑220930 | Reply LS on ECS provider identification in ECS address provisioning | Qualcomm | imported from 3GU |
| S6‑220931 | Reply LS on MEC Federation and interest to collaborate | SA6 | imported from 3GU |
| S6‑220932 | LS on network slice LCM consumption and use cases | SA6 | imported from 3GU |
| S6‑220933 | Implicit registration handling in service continuity | Samsung | imported from 3GU |
| S6‑220934 | Minor essential corrections to TS 23.434 | Samsung | imported from 3GU |
| S6‑220935 | Minor essential corrections to TS 23.434 | Samsung | imported from 3GU |
| S6‑220936 | Usage of SEAL in FFAPP | Huawei, Hisilicon | imported from 3GU |
| S6‑220937 | Minor corrections on network resource management for 5G TSC | Ericsson España S.A. | imported from 3GU |
| S6‑220938 | Minor corrections on network resource management for 5G TSC | Ericsson España S.A. | imported from 3GU |
| S6‑220939 | bulk registration for constrained device over MSGin5G-6 reference point | China Mobile Com. Corporation | imported from 3GU |
| S6‑220940 | FS_NSCALE_Evaluation of Solution 10 | China Mobile (Hangzhou) Inf. | imported from 3GU |
| S6‑220941 | application architecture updata | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220942 | Identities and commonly used values | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220943 | solution evaluation for solution 7 | China Mobile (Suzhou) Software | imported from 3GU |
| S6‑220944 | Obtaining resource owner consent in a cascade API invocation | NTT DOCOMO | imported from 3GU |
| S6‑220945 | Functional model description to support 3rd party API providers with SNA | NTT DOCOMO | imported from 3GU |
| S6‑220946 | Change ROAF to AF | Ericsson | imported from 3GU |
| S6‑220947 | Clarification on general description for Solution #3 | NTT DOCOMO | imported from 3GU |
| S6‑220948 | Application Server monitoring via CAPIF | Ericsson | imported from 3GU |
| S6‑220949 | Pseudo-CR on update on solution #2 | CATT | imported from 3GU |
| S6‑220950 | Pseudo-CR on solution for supporting location QoS | CATT | imported from 3GU |
| S6‑220951 | Update Solution #12 | Samsung | imported from 3GU |
| S6‑220952 | S6-eDGEAPP_Update Solution 8 | China Mobile E-Commerce Co. | imported from 3GU |
| S6‑220953 | S6-eEDGEAPP_Update Solution #8 | China Mobile E-Commerce Co. | imported from 3GU |
| S6‑220954 | Solution for KI#17 – Common EAS | InterDigital | imported from 3GU |
| S6‑220955 | pCR on Solution proposal for Key issue #17: Discovery of a common EAS | Apple GmbH | imported from 3GU |
| S6‑220956 | Evaluation of Solution#5 | Huawei, Hisilicon | imported from 3GU |
| S6‑220957 | Solution for KI#3 - Enhancements to service continuity planning with prediction expiration time | Huawei, Hisilicon | imported from 3GU |
| S6‑220958 | S6-eEDGEAPP_Solution for KI#5 | China Mobile E-Commerce Co. | imported from 3GU |
| S6‑220959 | Linked EASs | Qualcomm | imported from 3GU |
| S6‑220960 | UE identification with NAT | Qualcomm | imported from 3GU |
| S6‑220961 | Pseudo-CR on Solution to KI#11 | Samsung | imported from 3GU |
| S6‑220962 | Evaluation of Solution#4 | Huawei, Hisilicon | imported from 3GU |
| S6‑220963 | Evaluation of solution #17 | Huawei, Hisilicon | imported from 3GU |
| S6‑220964 | Cleanups of the procedures for Solution #1 | InterDigital | imported from 3GU |
| S6‑220965 | Redundant transport solution | Convida Wireless LLC | imported from 3GU |
| S6‑220966 | Overall Evaluation of key issue#14 | Huawei, Hisilicon | imported from 3GU |
| S6‑220967 | Data storage solution | Convida Wireless LLC | imported from 3GU |
| S6‑220968 | Update to SEALDD architecture for traffic flow description | Huawei, Hisilicon | imported from 3GU |
| S6‑220969 | Solution on KI#4: SEALDD integrating MSGin5G for message transfer | Huawei, Hisilicon | imported from 3GU |
| S6‑220970 | Solution on KI#7: SEALDD server discovery and selection for specific VAL server | Huawei, Hisilicon | imported from 3GU |
| S6‑220971 | Solution to KI #1 on VRU zone provisioning | Lenovo Future Communications | imported from 3GU |
| S6‑220972 | Solution to KI #2 - support for edge analytics | Lenovo Future Communications | imported from 3GU |
| S6‑220973 | Solution for KI#1 – Creation of PIN | vivo, Samsung | imported from 3GU |
| S6‑220974 | New KI on service continuity | vivo | imported from 3GU |
| S6‑220975 | Network slice info delivery | Samsung | imported from 3GU |
| S6‑220976 | Reply LS on AF specific UE ID retrieval | SA6 | imported from 3GU |
| S6‑220977 | AC Association aware EEC Registration | Convida Wireless LLC | imported from 3GU |
| S6‑220978 | Key issue on EAS discovery in Edge Node sharing scenario | Huawei, Hisilicon | imported from 3GU |
| S6‑220979 | SA6 Meeting #48-e - Chair's notes at end of the meeting | SA6 chair | imported from 3GU |
page generated from database: 2024-05-06 06:38:32