3GPP TDocs (written contributions) at meeting
Meeting: S6-33 - 2019-09-02 to 2019-09-06, Sophia Antipolis
meeting id: S6-33 (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
S6‑191621 | SA6 Meeting 33 Agenda | SA6 Chairman | imported from 3GU |
S6‑191622 | SA6 Meeting 32 Report | MCC | imported from 3GU |
S6‑191623 | SA6 Meeting #33 - Agenda with Tdocs allocation after submission deadline | SA6 Chairman | imported from 3GU |
S6‑191624 | SA6 Meeting #33 - Agenda with Tdocs allocation at start of the meeting | SA6 Chairman | imported from 3GU |
S6‑191625 | SA6 Meeting #33 - Chairman's notes at end of the meeting | SA6 Chairman | imported from 3GU |
S6‑191626 | Reply to LS on application layer support for V2X services | ETSI TC ITS | imported from 3GU |
S6‑191627 | Addtion of Location infomation to SDS and Enhance Status | HOME OFFICE | imported from 3GU |
S6‑191628 | Addition of optional message field to Enhanced Status | HOME OFFICE | imported from 3GU |
S6‑191629 | Payload size of 2048 octets in Broadcast | one2many B.V. | imported from 3GU |
S6‑191630 | ReplyLS to ETSI ISG MEC on Study on Application Architecture for enabling Edge Applications | 3GPP TSG-SA WG6 | imported from 3GU |
S6‑191631 | Discussion on generalization of preconfigured regrouping procedures | FirstNet | imported from 3GU |
S6‑191632 | Removal of temporary regroup procedures | FirstNet | imported from 3GU |
S6‑191633 | Removal of Requirement | one2many B.V. | imported from 3GU |
S6‑191634 | MSGin5G Architecture Considerations | one2many B.V. | imported from 3GU |
S6‑191635 | Key Issue #3 Solution on Application Server Enablement | Convida Wireless LLC | imported from 3GU |
S6‑191636 | Update to Key Issue #3 on Edge Application Server enablement on the Edge Hosting Environment | Convida Wireless LLC | imported from 3GU |
S6‑191637 | Update to Solution #8 on Registering Edge Enabler Client on Edge Enabler Server | Convida Wireless LLC | imported from 3GU |
S6‑191638 | Update to Solution #1 on Edge Application Server Discovery | Convida Wireless LLC | imported from 3GU |
S6‑191639 | Update to Solution #2 on Provisioning of Edge Data Network Configuratio | Convida Wireless LLC, Sony | imported from 3GU |
S6‑191640 | Key Issue #9 Solution on Preserving Service Continuity | Convida Wireless LLC | imported from 3GU |
S6‑191641 | Pseudo-CR on solution sharing location information outside of 3GPP | BDBOS | imported from 3GU |
S6‑191642 | Pseudo-CR on solution sharing location information on interconnected MC systems - subscription | BDBOS | imported from 3GU |
S6‑191643 | Pseudo-CR on solution sharing location information on interconnected MC systems - request | BDBOS | imported from 3GU |
S6‑191644 | Pseudo-CR on solution sharing location information on interconnected MC systems - authorization | BDBOS | imported from 3GU |
S6‑191645 | Pseudo-CR on solution sharing location information on interconnected MC systems – cancel subscription | BDBOS | imported from 3GU |
S6‑191646 | Pseudo-CR on solution sharing location information on interconnected MC systems - cancel | BDBOS | imported from 3GU |
S6‑191647 | Pseudo-CR on use case, key issue and solution for location service on past location information | BDBOS | imported from 3GU |
S6‑191648 | Proposed initial technical requirements for RAN and SA2 in support of MBMS/5G for MC | AT&T | imported from 3GU |
S6‑191649 | Scope and References sections for TR 23.xxx (SID FS_MC5MBS) | AT&T | imported from 3GU |
S6‑191650 | New Key Issue for TR 23.xxx (SID FS_MC5MBS): Enabling of unicast-multicast switching | AT&T | imported from 3GU |
S6‑191651 | New Key Issue for TR 23.xxx (SID FS_MC5MBS): Resource efficient group call mode | AT&T | imported from 3GU |
S6‑191652 | New Key Issue for TR 23.xxx (SID FS_MC5MBS): Large number of UEs | AT&T | imported from 3GU |
S6‑191653 | functional alias of called party in private call | TD Tech Ltd | imported from 3GU |
S6‑191654 | Requested priority in the MCPTT user profile configuration data | TD Tech Ltd | imported from 3GU |
S6‑191655 | 23745-FS_FFAPP-reference model | ZTE Corporation | imported from 3GU |
S6‑191656 | 23745-FS_FFAPP-Application architecture | ZTE Corporation | imported from 3GU |
S6‑191657 | 23745-FS_FFAPP-Key issue-AGV schedule & navigation | ZTE Corporation | imported from 3GU |
S6‑191658 | 23745-FS_FFAPP-Solution-Transmission application specific information to UE | ZTE Corporation | imported from 3GU |
S6‑191659 | 23745-FS_FFAPP-Solution-Obtain application specific event from UE | ZTE Corporation | imported from 3GU |
S6‑191660 | 23745-FS_FFAPP-Application architecture | ZTE Corporation | imported from 3GU |
S6‑191661 | 23745-FS_FFAPP-Key issue-Edge Computing based Industrial application analytics | ZTE Corporation | imported from 3GU |
S6‑191662 | 23745-FS_FFAPP-Solution-Edge Computing based industrial application analytics | ZTE Corporation | imported from 3GU |
S6‑191663 | 23745-FS_FFAPP-Key issue-NWDAF based Industrial application analytics | ZTE Corporation | imported from 3GU |
S6‑191664 | 23745-FS_FFAPP-Solution-NWDAF based industrial application analytics | ZTE Corporation | imported from 3GU |
S6‑191665 | 23745-FS_FFAPP-Key issue-Geographic location and positioning information support | ZTE Corporation | imported from 3GU |
S6‑191666 | 23745-FS_FFAPP-Solution-Geographic location and positioning information support | ZTE Corporation | imported from 3GU |
S6‑191667 | Revised_study_on_application_layer_support_for_Factories_of_the_Future_in_5G_network | ZTE Corporation | imported from 3GU |
S6‑191668 | Status of eMONASTERY2 | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191669 | Functional alias activated by default for group and private calls | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191670 | Functional alias activated by default for group and private calls | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191671 | Functional alias activated by default for group and p2p communications | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191672 | Procedure for changing the default functional alias | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191673 | Support of functional aliases as called party address in MCPTT emergency private calls | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191674 | Fixing the user profile configuration data for criteria triggered functional alias activation and de-activation | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191675 | Fixing the user profile configuration data for criteria triggered functional alias activation and de-activation | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191676 | Stage 1 requirement reference correction in the user profile data | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191677 | Making functional alias optional in floor control messages | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191678 | Add enhancements for interworking of MCData SDS with GSM-R SMS | Kapsch CarrierCom | imported from 3GU |
S6‑191679 | Add enhancements for interworking of MCPTT group calls with GSM-R | Kapsch CarrierCom | imported from 3GU |
S6‑191680 | Add call transfer for MCPTT private calls | Kapsch CarrierCom | imported from 3GU |
S6‑191681 | Pseudo-CR on Two Key Issues | one2many B.V. | imported from 3GU |
S6‑191682 | Interworking of calling party functional alias | Kapsch CarrierCom France S.A.S | imported from 3GU |
S6‑191683 | Functional model update for interconnection and migration | Motorola Solutions UK Ltd. | imported from 3GU |
S6‑191684 | Discussion on Partially Deployed Edge-DN support | Intel K.K. | imported from 3GU |
S6‑191685 | Discussion on EDGE-5 | Intel K.K. | imported from 3GU |
S6‑191686 | New RP - EDGE-5 | Intel K.K. | imported from 3GU |
S6‑191687 | New Key issue – Identities | Intel K.K. | imported from 3GU |
S6‑191688 | Solution for key issue – Identities | Intel K.K. | imported from 3GU |
S6‑191689 | Solution for preserving service continuity | Intel K.K. | imported from 3GU |
S6‑191690 | Pseudo-CR on updates to Key Issues 1 and 2 | VODAFONE Group Plc | imported from 3GU |
S6‑191691 | Pseudo-CR on solution to Key Issues 3 | VODAFONE Group Plc | imported from 3GU |
S6‑191692 | Pseudo-CR on solution to Key Issues 4 and 8 | VODAFONE Group Plc | imported from 3GU |
S6‑191693 | Clarification and corrections to support transmission control | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑191694 | Corrections to the transmission and reception control procedures | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑191695 | Pseudo-CR on key issue and solution for QoS Management for 5G Edge Network | Alibaba Group | imported from 3GU |
S6‑191696 | Architecture Update | Samsung | imported from 3GU |
S6‑191697 | Definition Update (Removal of ENs) | Samsung | imported from 3GU |
S6‑191698 | Solution 2 update | Samsung | imported from 3GU |
S6‑191699 | Solution 6 Update | Samsung | imported from 3GU |
S6‑191700 | New solution for application context relocation | Samsung | imported from 3GU |
S6‑191701 | pCR FS_5GMARCH identifier of the UE | China Mobile Com. Corporation | imported from 3GU |
S6‑191702 | pCR FS_5GMARCH network triggering the UE | China Mobile Com. Corporation | imported from 3GU |
S6‑191703 | pCR FS_5GMARCH group message | China Mobile Com. Corporation | imported from 3GU |
S6‑191704 | pCR FS_5GMARCH group management | China Mobile Com. Corporation | imported from 3GU |
S6‑191705 | Pseudo-CR on FS_5GMARCH broadcast message scenarios | China Unicom | imported from 3GU |
S6‑191706 | Pseudo-CR on FS_5GMARCH group message scenarios | China Unicom | imported from 3GU |
S6‑191707 | Reply LS on UAS-related terminology and model | SA1 | imported from 3GU |
S6‑191708 | Liaison Statement from SC 29/WG 11 to 3GPP SA 2 and SA 6 on NBMP [SC 29/WG 11 N 18738] | ISO IEC | imported from 3GU |
S6‑191709 | Solution #9 update about application context relocation | Samsung | imported from 3GU |
S6‑191710 | Solution for Edge Application Server’s enablement on an Edge Enabler Server | Samsung | imported from 3GU |
S6‑191711 | SA6 future meetings 2020-2021 | SA6 Chairman | imported from 3GU |
S6‑191712 | Remove 10.5.2.17 Editor's Note | L3Harris Technologies | imported from 3GU |
S6‑191713 | Update of solution 2 Provisioning of Edge Data Network configuration | Sony | imported from 3GU |
S6‑191714 | Pseudo-CR on edge application architectural requirements on security | CATT | imported from 3GU |
S6‑191715 | Pseudo-CR on issues regarding to authentication and authorization | CATT | imported from 3GU |
S6‑191716 | Pseudo-CR on clarifications to EDN configuration provisioning | CATT | imported from 3GU |
S6‑191717 | Pseudo-CR on clarifications on EDN configuration server | CATT | imported from 3GU |
S6‑191718 | Pseudo-CR on key issue 3 addition | CATT | imported from 3GU |
S6‑191719 | pCR new key issue on supporting tele-operated driving | Ericsson France S.A.S | imported from 3GU |
S6‑191720 | pCR new key issue V2X message distribution over Uu | Ericsson France S.A.S | imported from 3GU |
S6‑191721 | pCR architecture requirements | Ericsson France S.A.S | imported from 3GU |
S6‑191722 | pCR solution for supporting tele-operated driving | Ericsson France S.A.S | imported from 3GU |
S6‑191723 | Solution to Edge Application Server discover and update | Huawei, Hisilicon | imported from 3GU |
S6‑191724 | Update delopyment scanerios with applicable conditions | Huawei, Hisilicon | imported from 3GU |
S6‑191725 | Edge Application Server Discovery based on DNS | Huawei, Hisilicon | imported from 3GU |
S6‑191726 | Clarification and correction of Edge Data Network | Huawei, Hisilicon | imported from 3GU |
S6‑191727 | Update solution #2 with PCF providing EDN connection info | Huawei, Hisilicon | imported from 3GU |
S6‑191728 | Discussion on key aspects in MCX over 5G multicast broadcast | Huawei, Hisilicon | imported from 3GU |
S6‑191729 | Key issue on consideration of reusing unicast mechanism for 5G MBS | Huawei, Hisilicon | imported from 3GU |
S6‑191730 | Key issue on MC service directly over 5G MBS | Huawei, Hisilicon | imported from 3GU |
S6‑191731 | Key issue on Service performance and service continuity in 5G MBS | Huawei, Hisilicon | imported from 3GU |
S6‑191732 | Pseudo-CR on addition of Key Issues on edge application lifecycle management | Nokia Germany | imported from 3GU |
S6‑191733 | File distribution addressing based on functional alia | Union Inter. Chemins de Fer | imported from 3GU |
S6‑191734 | IP connectivity in a group | Union Inter. Chemins de Fer | imported from 3GU |
S6‑191735 | Reply LS on 3GPP SA6 Study on Edge Computing | SA6 Chairman | imported from 3GU |
S6‑191736 | Solution Evaluation - Solution #1 | Samsung Electronics | imported from 3GU |
S6‑191737 | Solution Evaluation - Solution #4 | Samsung Electronics | imported from 3GU |
S6‑191738 | Solution Evaluation - Solution #5 | Samsung Electronics | imported from 3GU |
S6‑191739 | Solution Evaluation - Solution #7 | Samsung Electronics | imported from 3GU |
S6‑191740 | Validity of registration information across EES | Samsung Electronics | imported from 3GU |
S6‑191741 | Overall Evaluations | Samsung Electronics | imported from 3GU |
S6‑191742 | Coversheet_TR 23.758 Presentation to TSG | Samsung Electronics | imported from 3GU |
S6‑191743 | Pseudo-CR on FFAPP Scope Update | Nokia | imported from 3GU |
S6‑191744 | Pseudo-CR on Key Issue on Device Onboarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191745 | Group announcement and join | Ericsson, Samsung | imported from 3GU |
S6‑191746 | EDGE-EES supporting centralized CAPIF | Samsung | imported from 3GU |
S6‑191747 | one-to-one_SDS_Session_Upgrade_to_emergency | Samsung | imported from 3GU |
S6‑191748 | group_SDS_upgrade_to_emergency_and_cancel_in-progress_emergency | Samsung | imported from 3GU |
S6‑191749 | one-to-one_emergency_FD | Samsung | imported from 3GU |
S6‑191750 | group_emergency_FD | Samsung | imported from 3GU |
S6‑191751 | one-to-one_FD_upgrade_to_emergency | Samsung | imported from 3GU |
S6‑191752 | group_FD_upgrade_to_emergency_and_cancel_in-progress_emergency | Samsung | imported from 3GU |
S6‑191753 | MCIOPS on a new TS | Ericsson | imported from 3GU |
S6‑191754 | MCIOPS TS skeleton | Ericsson | imported from 3GU |
S6‑191755 | Scope for TS MCIOPS | Ericsson | imported from 3GU |
S6‑191756 | References for TS MCIOPS | Ericsson | imported from 3GU |
S6‑191757 | Definitions and abbreviations for TS MCIOPS | Ericsson | imported from 3GU |
S6‑191758 | Application Priority discussion paper | Union Inter. Chemins de Fer | imported from 3GU |
S6‑191759 | Discussion on the support of MC sevices on IOPS | Ericsson | imported from 3GU |
S6‑191760 | Introduction for TS MCIOPS | Ericsson | imported from 3GU |
S6‑191761 | Architectural requirements for MCIOPS | Ericsson | imported from 3GU |
S6‑191762 | Functional model for MCIOPS | Ericsson | imported from 3GU |
S6‑191763 | Application priority and priority levels | Union Inter. Chemins de Fer | imported from 3GU |
S6‑191764 | Functional entities in MCIOPS | Ericsson | imported from 3GU |
S6‑191765 | Reference points in MCIOPS | Ericsson | imported from 3GU |
S6‑191766 | IP connectivity remote priority change | Union Inter. Chemins de Fer | imported from 3GU |
S6‑191767 | Application of functional model for MCIOPS | Ericsson | imported from 3GU |
S6‑191768 | Revised WID MCIOPS | Ericsson | imported from 3GU |
S6‑191769 | Study on supporting application of Railway Smart Station Services | Hansung University, LG Uplus | imported from 3GU |
S6‑191770 | Functionalities with SA2 dependency | Ericsson, Huawei | imported from 3GU |
S6‑191771 | Corrections on notifications for network monitoring procedure | Huawei, Hisilicon | imported from 3GU |
S6‑191772 | Addition of missing VAE server APIs | Huawei, Hisilicon | imported from 3GU |
S6‑191773 | Update the configurations information | Huawei, Hisilicon | imported from 3GU |
S6‑191774 | Corrections to network resource management procedures | Huawei, Hisilicon | imported from 3GU |
S6‑191775 | Remove EN on bearer type identification | Huawei, Hisilicon | imported from 3GU |
S6‑191776 | Remove EN on granularity of decision of NRM server | Huawei, Hisilicon | imported from 3GU |
S6‑191777 | Solution for Edge application service APIs publish and discovery | Huawei, Hisilicon | imported from 3GU |
S6‑191778 | Solution for Edge application registration | Huawei, Hisilicon | imported from 3GU |
S6‑191779 | Solution for Edge enabler server registration | Huawei, Hisilicon | imported from 3GU |
S6‑191780 | Update to solution 9 | Huawei, Hisilicon | imported from 3GU |
S6‑191781 | Solution for User plane management event API | Huawei, Hisilicon | imported from 3GU |
S6‑191782 | Solution for Fetch target Edge AS API | Huawei, Hisilicon | imported from 3GU |
S6‑191783 | Key issue on enabling FFAPP requirements communications | Huawei, Hisilicon | imported from 3GU |
S6‑191784 | Solution to establish communications with FFAPP requirements | Huawei, Hisilicon | imported from 3GU |
S6‑191785 | Key issue on UAS group communications | Huawei, Hisilicon | imported from 3GU |
S6‑191786 | Key issue on UAV location information | Huawei, Hisilicon | imported from 3GU |
S6‑191787 | Proposal for solution to key issue on Uu QoS monitoring and control | Huawei, Hisilicon | imported from 3GU |
S6‑191788 | Proposal for key issue on multi-PLMN coordination | Huawei, Hisilicon | imported from 3GU |
S6‑191789 | Update to Definitions and Abbreviations | Airbus DS SLC | imported from 3GU |
S6‑191790 | Update to UAS Reference Model and Description | Airbus DS SLC | imported from 3GU |
S6‑191791 | Update to Service Requirements Analysis | Airbus DS SLC | imported from 3GU |
S6‑191792 | Discussion on key aspects in MCX over 5G multicast broadcast | Huawei, Hisilicon | imported from 3GU |
S6‑191793 | Pseudo-CR on key issue and solution for QoS Management for 5G Edge Network | Alibaba Group, Vodafone Group | imported from 3GU |
S6‑191794 | LS on restricting incoming private calls | CT1 | imported from 3GU |
S6‑191795 | [DRAFT] Reply LS on on NBMP | SA6 | imported from 3GU |
S6‑191796 | Clarification and corrections to support transmission control | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑191797 | Corrections to the transmission and reception control procedures | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑191798 | One-to-one SDS Session upgrade to emergency session | Samsung | imported from 3GU |
S6‑191799 | Group SDS Session upgrade to emergency/imminent-peril session and cancel in-progress emergency/imminent-peril group state | Samsung | imported from 3GU |
S6‑191800 | Functional model update for interconnection and migration | Motorola Solutions UK Ltd. | imported from 3GU |
S6‑191801 | Remove 10.5.2.17 Editor's Note | L3Harris Technologies | imported from 3GU |
S6‑191802 | Fixing the user profile configuration data for criteria triggered functional alias activation and de-activation | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191803 | Fixing the user profile configuration data for criteria triggered functional alias activation and de-activation | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191804 | Making functional alias optional in floor control messages | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191805 | Reply LS on restricting incoming private calls | SA6 | imported from 3GU |
S6‑191806 | Application priority and priority levels | Union Inter. Chemins de Fer | imported from 3GU |
S6‑191807 | functional alias of called party in private call | TD Tech Ltd | imported from 3GU |
S6‑191808 | Support of functional aliases as called party address in MCPTT emergency private calls | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191809 | Add call transfer for MCPTT private calls | Kapsch CarrierCom | imported from 3GU |
S6‑191810 | File distribution addressing based on functional alia | Union Inter. Chemins de Fer | imported from 3GU |
S6‑191811 | IP connectivity for group communication (unicast) | Union Inter. Chemins de Fer | imported from 3GU |
S6‑191812 | Capability to change remotely the priority of the point-to-point IP connectivity communication | Union Inter. Chemins de Fer | imported from 3GU |
S6‑191813 | MCIOPS TS skeleton | Ericsson | imported from 3GU |
S6‑191814 | Scope for TS MCIOPS | Ericsson | imported from 3GU |
S6‑191815 | Definitions and abbreviations for TS MCIOPS | Ericsson | imported from 3GU |
S6‑191816 | Introduction for TS MCIOPS | Ericsson | imported from 3GU |
S6‑191817 | Architectural requirements for MCIOPS | Ericsson | imported from 3GU |
S6‑191818 | Pseudo-CR on Functional model description for MCIOPS | Ericsson | imported from 3GU |
S6‑191819 | Functional entities in MCIOPS | Ericsson | imported from 3GU |
S6‑191820 | Reference points in MCIOPS | Ericsson | imported from 3GU |
S6‑191821 | References for TS MCIOPS | Ericsson | imported from 3GU |
S6‑191822 | Application of functional model for MCIOPS | Ericsson | imported from 3GU |
S6‑191823 | Pseudo-CR on solution sharing location information on interconnected MC systems - subscription | BDBOS | imported from 3GU |
S6‑191824 | Pseudo-CR on solution sharing location information on interconnected MC systems - request | BDBOS | imported from 3GU |
S6‑191825 | Pseudo-CR on solution sharing location information on interconnected MC systems - authorization | BDBOS | imported from 3GU |
S6‑191826 | Pseudo-CR on solution sharing location information on interconnected MC systems – cancel subscription | BDBOS | imported from 3GU |
S6‑191827 | Pseudo-CR on solution sharing location information on interconnected MC systems – solution evaluation | BDBOS | imported from 3GU |
S6‑191828 | Pseudo-CR on use case, key issue and solution for location service on past location information | BDBOS | imported from 3GU |
S6‑191829 | Removal of Requirement | one2many B.V. | imported from 3GU |
S6‑191830 | Pseudo-CR on FS_5GMARCH broadcast message scenarios | China Unicom | imported from 3GU |
S6‑191831 | Pseudo-CR on FS_5GMARCH group message scenarios | China Unicom | imported from 3GU |
S6‑191832 | pCR FS_5GMARCH identifier of the UE | China Mobile Com. Corporation | imported from 3GU |
S6‑191833 | pCR FS_5GMARCH network triggering the UE | China Mobile Com. Corporation | imported from 3GU |
S6‑191834 | pCR FS_5GMARCH group management | China Mobile Com. Corporation | imported from 3GU |
S6‑191835 | Pseudo-CR on Two Key Issues | one2many B.V. | imported from 3GU |
S6‑191836 | Pseudo-CR on MSGin5G Architecture Considerations | one2many B.V. | imported from 3GU |
S6‑191837 | Solution for Edge application service APIs publish and discovery | Huawei, Hisilicon | imported from 3GU |
S6‑191838 | New solution to KI#9 about application context relocation | Samsung | imported from 3GU |
S6‑191839 | Solution for Edge enabler server registration | Huawei, Hisilicon | imported from 3GU |
S6‑191840 | Solution for Fetch target Edge AS API | Huawei, Hisilicon | imported from 3GU |
S6‑191841 | Reply LS on 3GPP SA6 Study on Edge Computing | SA6 | imported from 3GU |
S6‑191842 | Update to solution 9 | Huawei, Hisilicon | imported from 3GU |
S6‑191843 | New solution for application context relocation | Samsung | imported from 3GU |
S6‑191844 | Pseudo-CR on Update deployment scenarios with applicable conditions | Huawei, Hisilicon | imported from 3GU |
S6‑191845 | Overall Evaluations | Samsung Electronics | imported from 3GU |
S6‑191846 | Support of functional aliases as called party address in MCPTT emergency private calls | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191847 | Add call transfer for MCPTT private calls | Kapsch CarrierCom | imported from 3GU |
S6‑191848 | File distribution addressing based on functional alia | Union Inter. Chemins de Fer | imported from 3GU |
S6‑191849 | IP connectivity for group communication (unicast) | Union Inter. Chemins de Fer | imported from 3GU |
S6‑191850 | Capability to change remotely the priority of the point-to-point IP connectivity communication | Union Inter. Chemins de Fer | imported from 3GU |
S6‑191851 | Functional entities in MCIOPS | Ericsson | imported from 3GU |
S6‑191852 | General Requirements section for TR 23.xxx (SID FS_MC5MBS) | AT&T | imported from 3GU |
S6‑191853 | LS on aspects of Mission Critical Services over 5MBS | SA6 | imported from 3GU |
S6‑191854 | reference model | ZTE Corporation | imported from 3GU |
S6‑191855 | One-to-One Emergency MCData FD | Samsung | imported from 3GU |
S6‑191856 | Group emergency MCData FD | Samsung | imported from 3GU |
S6‑191857 | One-to-one FD Session upgrade to emergency session | Samsung | imported from 3GU |
S6‑191858 | Group FD communication upgrade to emergency/imminent-peril communication and cancel in-progress emergency/imminent-peril group state | Samsung | imported from 3GU |
S6‑191859 | Addtion of Location infomation to SDS and Enhance Status | HOME OFFICE | imported from 3GU |
S6‑191860 | Corrections on notifications for network monitoring procedure | Huawei, Hisilicon | imported from 3GU |
S6‑191861 | Addition of missing VAE server APIs | Huawei, Hisilicon | imported from 3GU |
S6‑191862 | Update the configurations information | Huawei, Hisilicon | imported from 3GU |
S6‑191863 | Corrections to network resource management procedures | Huawei, Hisilicon | imported from 3GU |
S6‑191864 | New RP - EDGE-5 | Intel, AT&T | imported from 3GU |
S6‑191865 | Architecture Update (Removal of EN in clause 6.2) | Samsung | imported from 3GU |
S6‑191866 | Pseudo-CR on edge application architectural requirements on security | CATT | imported from 3GU |
S6‑191867 | Pseudo-CR on clarifications on EDN configuration server | CATT | imported from 3GU |
S6‑191868 | Update to Key Issue #5 on Edge Application Server enablement on the Edge Hosting Environment | Convida Wireless LLC | imported from 3GU |
S6‑191869 | Pseudo-CR on Key Issue and Solution for QoS Management for 5G Edge Network | Alibaba Group, Vodafone Group | imported from 3GU |
S6‑191870 | Pseudo-CR on addition of Key Issues on edge application lifecycle management | Nokia Germany | imported from 3GU |
S6‑191871 | [DRAFT] LS on Lifecycle Management to support Edge Computing | SA6 | imported from 3GU |
S6‑191872 | Pseudo-CR on New Key issue: Identities | Intel K.K. | imported from 3GU |
S6‑191873 | Key Issue #3 Solution on Application Server Enablement | Convida Wireless LLC, Vodafone (?), Nokia (?), Samsung, Huawei (?) | imported from 3GU |
S6‑191874 | Pseudo-CR on solution to Key Issues 3 | VODAFONE Group Plc | imported from 3GU |
S6‑191875 | Solution for Edge Application Server’s enablement on an Edge Enabler Server | Samsung | imported from 3GU |
S6‑191876 | Pseudo-CR on updates to Key Issues 1 and 2 | Vodafone, Nokia | imported from 3GU |
S6‑191877 | Update to Solution #2 on Provisioning of Edge Data Network Configuratio | Convida Wireless LLC, Sony | imported from 3GU |
S6‑191878 | Update of solution 2 Provisioning of Edge Data Network configuration | Sony | imported from 3GU |
S6‑191879 | Pseudo-CR on clarifications to EDN configuration provisioning | CATT | imported from 3GU |
S6‑191880 | Update solution #2 with PCF providing EDN connection info | Huawei, Hisilicon | imported from 3GU |
S6‑191881 | Solution 2 update | Samsung | imported from 3GU |
S6‑191882 | Update to Solution #1 on Edge Application Server Discovery | Convida Wireless LLC | imported from 3GU |
S6‑191883 | Pseudo-CR on Solution Evaluation – Solution #1 | Samsung Electronics | imported from 3GU |
S6‑191884 | Pseudo-CR on solution to Key Issues 4 and 8 | Vodafone, Nokia | imported from 3GU |
S6‑191885 | Pseudo-CR on Solution to Edge Application Server discover and update | Huawei, Hisilicon | imported from 3GU |
S6‑191886 | Edge Application Server Discovery based on DNS | Huawei, Hisilicon | imported from 3GU |
S6‑191887 | Solution Evaluation - Solution #4 | Samsung Electronics | imported from 3GU |
S6‑191888 | Solution Evaluation - Solution #5 | Samsung Electronics | imported from 3GU |
S6‑191889 | Solution for User plane management event API | Huawei, Hisilicon | imported from 3GU |
S6‑191890 | Pseudo-CR on EES supporting centralized CAPIF | Samsung | imported from 3GU |
S6‑191891 | Solution for Edge application service APIs publish and discovery | Huawei, Hisilicon | imported from 3GU |
S6‑191892 | Pseudo-CR on issues regarding to authentication and authorization | CATT | imported from 3GU |
S6‑191893 | Solution 6 Update | Samsung | imported from 3GU |
S6‑191894 | Pseudo-CR on Solution Evaluation – Solution #7 | Samsung Electronics | imported from 3GU |
S6‑191895 | Update to Solution #8 on Registering Edge Enabler Client on Edge Enabler Server | Convida Wireless LLC, Samsung | imported from 3GU |
S6‑191896 | New solution to KI#9 about application context relocation | Samsung | imported from 3GU |
S6‑191897 | Solution for Edge enabler server registration | Huawei, Hisilicon | imported from 3GU |
S6‑191898 | Solution for Fetch target Edge AS API | Huawei, Hisilicon | imported from 3GU |
S6‑191899 | Update to solution 9 | Huawei, Hisilicon | imported from 3GU |
S6‑191900 | Key Issue #9 Solution on Preserving Service Continuity | Convida Wireless LLC, Samsung | imported from 3GU |
S6‑191901 | New solution for application context relocation | Samsung | imported from 3GU |
S6‑191902 | Pseudo-CR on Update deployment scenarios with applicable conditions | Huawei, Hisilicon | imported from 3GU |
S6‑191903 | Overall Evaluations | Samsung Electronics | imported from 3GU |
S6‑191904 | Reply LS on 3GPP SA6 Study on Edge Computing | SA6 | imported from 3GU |
S6‑191905 | pCR new key issue on supporting tele-operated driving | Ericsson France S.A.S | imported from 3GU |
S6‑191906 | pCR new key issue V2X message distribution over Uu | Ericsson France S.A.S | imported from 3GU |
S6‑191907 | Proposal for key issue on multi-PLMN coordination | Huawei, Hisilicon | imported from 3GU |
S6‑191908 | pCR architecture requirements | Ericsson France S.A.S | imported from 3GU |
S6‑191909 | pCR solution for supporting tele-operated driving | Ericsson France S.A.S | imported from 3GU |
S6‑191910 | Proposal for solution to key issue on Uu QoS monitoring and control | Huawei, Hisilicon | imported from 3GU |
S6‑191911 | reference model | ZTE Corporation | imported from 3GU |
S6‑191912 | Application architecture | ZTE Corporation | imported from 3GU |
S6‑191913 | Key issue- AGV schedule & navigation | ZTE Corporation | imported from 3GU |
S6‑191914 | Solution- AGV application assist information | ZTE Corporation | imported from 3GU |
S6‑191915 | Key issue- Edge Computing based Industrial application analytics | ZTE Corporation | imported from 3GU |
S6‑191916 | Pseudo-CR on addition of Key Issues on lifecycle management | Nokia, Nokia Shanghai Bell, Samsung | imported from 3GU |
S6‑191917 | Solution- Geographic location and positioning information support | ZTE Corporation | imported from 3GU |
S6‑191918 | Key issue- Geographic location and positioning information support | ZTE Corporation | imported from 3GU |
S6‑191919 | FFAPP Scope Correction | Nokia | imported from 3GU |
S6‑191920 | Pseudo-CR on Key Issue on Device Onboarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191921 | Key issue on enabling FFAPP requirements communications | Huawei, Hisilicon | imported from 3GU |
S6‑191922 | Solution to establish communications with FFAPP requirements | Huawei, Hisilicon | imported from 3GU |
S6‑191923 | Discussion enhMCLOc | Motorola | imported from 3GU |
S6‑191924 | Revised SID on location enhancements for mission critical services | Motorola | imported from 3GU |
S6‑191925 | Work Plan review at SA6#33 | Qualcomm | imported from 3GU |
S6‑191926 | Capability to change remotely the priority of the point-to-point IP connectivity communication | Union Inter. Chemins de Fer | imported from 3GU |
S6‑191927 | Scope section for TR 23.xxx (SID FS_MC5MBS) | AT&T | imported from 3GU |
S6‑191928 | New Key Issue for TR 23.xxx (SID FS_MC5MBS): Enabling of unicast-multicast switching | AT&T | imported from 3GU |
S6‑191929 | LS on clarifications regarding V2XAPP services | CT3 | imported from 3GU |
S6‑191930 | New Key Issue for TR 23.xxx (SID FS_MC5MBS): Resource efficient group call mode | AT&T | imported from 3GU |
S6‑191931 | New Key Issue for TR 23.xxx (SID FS_MC5MBS): Large number of UEs | AT&T | imported from 3GU |
S6‑191932 | General Requirements section for TR 23.xxx (SID FS_MC5MBS) | AT&T | imported from 3GU |
S6‑191933 | LS on MC 5MBS | SA6 | imported from 3GU |
S6‑191934 | Update to Definitions | Airbus DS SLC | imported from 3GU |
S6‑191935 | Key issue on UAS group communications | Huawei, Hisilicon | imported from 3GU |
S6‑191936 | Key issue on UAV location information | Huawei, Hisilicon | imported from 3GU |
S6‑191937 | Update to UAS Reference Model and Description | Airbus DS SLC | imported from 3GU |
S6‑191938 | Study on supporting application of Railway Smart Station Services | Hansung University, LG Uplus | imported from 3GU |
S6‑191939 | Pseudo-CR on solution to Key Issues 3 | VODAFONE Group Plc | imported from 3GU |
S6‑191940 | Clarification and corrections to support transmission control | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑191941 | Corrections to the transmission and reception control procedures | AT&T GNS Belgium SPRL | imported from 3GU |
S6‑191942 | Addtion of Location infomation to SDS and Enhance Status | HOME OFFICE | imported from 3GU |
S6‑191943 | Functional model update for interconnection and migration | Motorola Solutions UK Ltd. | imported from 3GU |
S6‑191944 | Corrections to network resource management procedures | Huawei, Hisilicon | imported from 3GU |
S6‑191945 | New RP - EDGE-5 | Intel, AT&T | imported from 3GU |
S6‑191946 | Architecture Update (Removal of EN in clause 6.2) | Samsung | imported from 3GU |
S6‑191947 | Pseudo-CR on edge application architectural requirements on security | CATT | imported from 3GU |
S6‑191948 | Update to Key Issue #5 on Edge Application Server enablement on the Edge Hosting Environment | Convida Wireless LLC | imported from 3GU |
S6‑191949 | Pseudo-CR on addition of Key Issues on lifecycle management | Nokia, Nokia Shanghai Bell, Samsung | imported from 3GU |
S6‑191950 | Pseudo-CR on clarifications to EDN configuration provisioning | CATT | imported from 3GU |
S6‑191951 | Key Issue #3 Solution on Application Server Enablement | Convida Wireless LLC, Samsung, Vodafone, Nokia, Huawei | imported from 3GU |
S6‑191952 | Pseudo-CR on solution to Key Issues 3 | VODAFONE Group Plc | imported from 3GU |
S6‑191953 | Reply LS on 3GPP SA6 Study on Edge Computing | SA6 | imported from 3GU |
S6‑191954 | [DRAFT] LS on Lifecycle Management to support Edge Computing | SA6 | imported from 3GU |
S6‑191955 | Update of solution 2 Provisioning of Edge Data Network configuration | Sony | imported from 3GU |
S6‑191956 | Pseudo-CR on Solution to Edge Application Server discover and update | Huawei, Hisilicon | imported from 3GU |
S6‑191957 | Application architecture | ZTE Corporation | imported from 3GU |
S6‑191958 | Key issue- AGV schedule & navigation | ZTE Corporation | imported from 3GU |
S6‑191959 | Key issue- Edge Computing based Industrial application analytics | ZTE Corporation | imported from 3GU |
S6‑191960 | Solution- Geographic location and positioning information support | ZTE Corporation | imported from 3GU |
S6‑191961 | FFAPP Scope Correction | Nokia | imported from 3GU |
S6‑191962 | Pseudo-CR on Key Issue on Device Onboarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191963 | pCR new key issue on supporting tele-operated driving | Ericsson France S.A.S | imported from 3GU |
S6‑191964 | pCR new key issue V2X message distribution over Uu | Ericsson France S.A.S | imported from 3GU |
S6‑191965 | Proposal for key issue on multi-PLMN coordination | Huawei, Hisilicon | imported from 3GU |
S6‑191966 | pCR architecture requirements | Ericsson France S.A.S | imported from 3GU |
S6‑191967 | pCR solution for supporting tele-operated driving | Ericsson France S.A.S | imported from 3GU |
S6‑191968 | Proposal for solution to key issue on Uu QoS monitoring and control | Huawei, Hisilicon | imported from 3GU |
S6‑191969 | Update to Definitions | Airbus DS SLC | imported from 3GU |
S6‑191970 | Key issue on UAS group communications | Huawei, Hisilicon | imported from 3GU |
S6‑191971 | Pseudo-CR on FS_5GMARCH group message scenarios | China Unicom | imported from 3GU |
S6‑191972 | Pseudo-CR on Key Issue and Solution for QoS Management for 5G Edge Network | Alibaba Group, Vodafone Group | imported from 3GU |
S6‑191973 | Pseudo-CR on New Key issue: Identities | Intel K.K. | imported from 3GU |
S6‑191974 | Pseudo-CR on updates to Key Issues 1 and 2 | Vodafone, Nokia | imported from 3GU |
S6‑191975 | One-to-One Emergency MCData FD | Samsung | imported from 3GU |
S6‑191976 | Pseudo-CR on solution sharing location information on interconnected MC systems – cancel subscription | BDBOS | imported from 3GU |
S6‑191977 | Pseudo-CR on use case, key issue and solution for location service on past location information | BDBOS | imported from 3GU |
S6‑191978 | Revised SID on location enhancements for mission critical services | Motorola | imported from 3GU |
S6‑191979 | Scope section for TR 23.xxx (SID FS_MC5MBS) | AT&T | imported from 3GU |
S6‑191980 | New Key Issue for TR 23.xxx (SID FS_MC5MBS): Resource efficient group call mode | AT&T | imported from 3GU |
S6‑191981 | Revised SID Study on application layer support for Factories of the Future in 5G network | ZTE Corporation | imported from 3GU |
S6‑191982 | Solution to establish communications with FFAPP requirements | Huawei, Hisilicon | imported from 3GU |
S6‑191983 | Key issue on UAV location information | Huawei, Hisilicon | imported from 3GU |
S6‑191984 | Update of solution 2 Provisioning of Edge Data Network configuration | Sony | imported from 3GU |
S6‑191985 | Update solution #2 with PCF providing EDN connection info | Huawei, Hisilicon | imported from 3GU |
S6‑191986 | Update to Solution #1 on Edge Application Server Discovery | Convida Wireless LLC | imported from 3GU |
S6‑191987 | Pseudo-CR on solution to Key Issues 4 and 8 | Vodafone, Nokia | imported from 3GU |
S6‑191988 | Solution 6 Update | Samsung | imported from 3GU |
S6‑191989 | Pseudo-CR on MSGin5G Architecture Considerations | one2many B.V. | imported from 3GU |
S6‑191990 | Add call transfer for MCPTT private calls | Kapsch CarrierCom | imported from 3GU |
S6‑191991 | File distribution addressing based on functional alia | Union Inter. Chemins de Fer | imported from 3GU |
S6‑191992 | Solution for Fetch target Edge AS API | Huawei, Hisilicon | imported from 3GU |
S6‑191993 | LS S6-191708 on NBMP from ISO/IEC JTC 1/SC 29/WG 11 | SA6 | imported from 3GU |
S6‑191994 | LS on aspects of Mission Critical Services over 5MBS | SA6 | imported from 3GU |
S6‑191995 | FFAPP Scope Correction | Nokia | imported from 3GU |
S6‑191996 | Pseudo-CR on Key Issue on Device Onboarding | Nokia, Nokia Shanghai Bell | imported from 3GU |
S6‑191997 | Pseudo-CR on New Key issue: Identities | Intel K.K. | imported from 3GU |
S6‑191998 | Pseudo-CR on updates to Key Issues 1 and 2 | Vodafone, Nokia | imported from 3GU |
S6‑191999 | Update to Solution #1 on Edge Application Server Discovery | Convida Wireless LLC | imported from 3GU |
S6‑192000 | Pseudo-CR on Update deployment scenarios with applicable conditions | Huawei, Hisilicon | imported from 3GU |
S6‑192001 | Proposal for key issue on multi-PLMN coordination | Huawei, Hisilicon | imported from 3GU |
S6‑192002 | pCR solution for supporting tele-operated driving | Ericsson France S.A.S | imported from 3GU |
S6‑192003 | LS on aspects of Mission Critical Services over 5MBS | SA6 | imported from 3GU |
S6‑192004 | Coversheet_TR 23.758 Presentation to TSG | Samsung Electronics | imported from 3GU |
page generated from database: 2024-04-13 13:51:47