Method of gNB-CU-CP device, method of AMF device, method of SMF device, gNB-CU-CP device, AMF device, SMF device, and UPF device

Abstract

This disclosure proposes a solution to provide optimized user plane processing in 5GS. [Solution] The communication device method includes performing functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and functions of a User Plane Function (UPF) device, communicating with a gNB Distributed Unit (gNB-DU) device, and communicating with a gNB Centralized Unit-Control Plane (gNB-CU-CP) device.

Description

Technical Field

[0001] The present disclosure relates to a method for a communication device, a method for a gNB-CU-CP device, a method for an AMF device, a method for an SMF device, a method for a gNB-DU device, a method for a UPF device, a communication device, a gNB-CU-CP device, an AMF device, an SMF device, a gNB-DU device, and a UPF device.

Background Art

[0002] The overall architecture for NG-RAN is shown in Non-Patent Document 2. NG-RAN includes a set of gNBs connected to 5GC through the NG interface. A gNB may include a gNB-CU and one or more gNB-DUs.

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

Non-Patent Document 4

Non-Patent Document 5

[0004] In order to process user data according to Non-Patent Document 13 and Non-Patent Document 2, there are at least three user plane entities in 5GS, namely, gNB-DU, gNB-CU-UP, and UPF. It is true that transmission delay is added every time user data crosses a user plane entity. On the other hand, for example, when 5GS is used for time critical applications such as remote machine control, drone control, or remote surgery, high performance in user data processing is required with respect to latency.

[0005] To meet low latency requirements, the current 5GS architecture may be too redundant to achieve the identified requirements. [Means for Solving the Problems]

[0006] In an aspect of the present disclosure, a method of a communication device includes performing functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and functions of a User Plain Function (UPF) device, communicating with a gNB Distributed Unit (gNB-DU) device, and communicating with a gNB Centralized Unit-Control Plane (gNB-CU-CP) device.

[0007] In an aspect of the present disclosure, a method of a gNB Centralized Unit-Control Plane (gNB-CU-CP) device includes receiving a Protocol Data Unit (PDU) session establishment request message from a User Equipment (UE). The method includes transmitting an UPLINK NAS TRANSPORT message to an Access and Mobility management Function (AMF) device. The UPLINK NAS TRANSPORT message includes the PDU session establishment request message and information indicating that the gNB-CU-CP device supports communication with a communication device that executes functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and functions of a User Plain Function (UPF) device. The method includes receiving an INITIAL CONTEXT SETUP REQUEST message from the AMF device. The INITIAL CONTEXT SETUP REQUEST message includes information regarding the gNB-CU-UP. The method includes selecting the gNB-CU-UP based on the information regarding the gNB-CU-UP. The method includes performing a PDU session establishment procedure for the UE.

[0008] In an aspect of the present disclosure, a method of an Access and Mobility management Function (AMF) device includes receiving an UPLINK NAS TRANSPORT message from a gNB Centralized Unit Control Plane (gNB-CU-CP) device. The UPLINK NAS TRANSPORT message includes a Protocol Data Unit (PDU) session establishment request message and information indicating that the gNB-CU-CP device supports communication with a communication device that executes functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and functions of a User Plain Function (UPF) device. The method includes transmitting an Nsmf_PDUSession_CreateSMContext request message to a Session Management Function (SMF) device. The Nsmf_PDUSession_CreateSMContext request message includes the information. The method includes receiving an Nsmf_PDUSession_CreateSMContext response message from the SMF device. The Nsmf_PDUSession_CreateSMContext response message includes information regarding the UPF device. The method includes receiving a Namf_Communication_N1N2MessageTransfer message from the SMF device. The Namf_Communication_N1N2MessageTransfer message includes information regarding the gNB-CU-UP device. The method includes transmitting an INITIAL CONTEXT SETUP REQUEST message to the gNB-CU-CP device. The INITIAL CONTEXT SETUP REQUEST message includes the information regarding the gNB-CU-UP device.The method includes performing a PDU session establishment procedure.

[0009] In an aspect of the present disclosure, a method of a Session Management Function (SMF) device includes receiving an Nsmf_PDUSession_CreateSMContext request message from an Access and Mobility management Function (AMF) device. The Nsmf_PDUSession_CreateSMContext request message includes information indicating that a gNB Centralized Unit Control Plane (gNB-CU-CP) device supports communication with a communication device that executes functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and a User Plain Function (UPF) device. The method includes sending an Nsmf_PDUSession_CreateSMContext response message to the AMF device. The Nsmf_PDUSession_CreateSMContext response message includes information regarding the UPF device. The method includes selecting the UPF device when the Nsmf_PDUSession_CreateSMContext request message includes the information. The method includes contacting the communication device to secure resources for processing user data. The method includes sending a Namf_Communication_N1N2MessageTransfer message to the AMF device. The Namf_Communication_N1N2MessageTransfer message includes information regarding the gNB-CU-UP device. The method includes performing a PDU session establishment procedure.

[0010] In an aspect of the present disclosure, a method of a gNB Distributed Unit (gNB-DU) device includes communicating with a gNB Centralized Unit-Control Plane (gNB-CU-CP) device and communicating with a User Plane Function (UPF) device without involving a gNB Centralized Unit User Plane (gNB-CU-UP) device.

[0011] In an aspect of the present disclosure, a method of a gNB Centralized Unit-Control Plane (gNB-CU-CP) device includes communicating with a gNB Distributed Unit (gNB-DU) device and communicating with a User Plane Function (UPF) device without involving a gNB Centralized Unit User Plane (gNB-CU-UP) device.

[0012] In an aspect of the present disclosure, a method of an Access and Mobility management Function (AMF) device includes receiving an UPLINK NAS TRANSPORT message from a gNB Centralized Unit Control Plane (gNB-CU-CP) device. The UPLINK NAS TRANSPORT message includes first information indicating that the gNB-CU-CP device supports the gNB Distributed Unit (gNB-DU) device to be connected to a User Plane Function (UPF) device without accompanying the gNB Centralized Unit User Plane (gNB-CU-UP) device. The method includes sending an Nsmf_PDUSession_CreateSMContext request message to a Session Management Function (SMF) device. The Nsmf_PDUSession_CreateSMContext request message includes the first information. The method includes receiving an Nsmf_PDUSession_CreateSMContext response message from the SMF device. The Nsmf_PDUSession_CreateSMContext response message includes second information indicating that the UPF device supports the gNB-DU device to be connected to the UPF device without accompanying the gNB-CU-UP device. The method includes receiving a Namf_Communication_N1N2MessageTransfer message from the SMF device.The Namf_Communication_N1N2MessageTransfer message includes a gNB-CU-UP UE E1AP ID and third information indicating a pair of an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID) for uplink data processing. The method includes transmitting an INITIAL CONTEXT SETUP REQUEST message to the gNB-CU-CP device. The INITIAL CONTEXT SETUP REQUEST message includes the gNB-CU-UP UE E1AP ID and the third information. The method includes receiving an INITIAL CONTEXT SETUP RESPONSE message from the gNB-CU-CP device. The method includes performing a PDU session establishment procedure.

[0013] In an aspect of the present disclosure, a method of a Session Management Function (SMF) device includes receiving an Nsmf_PDUSession_CreateSMContext request message from an Access and Mobility management Function (AMF) device. The Nsmf_PDUSession_CreateSMContext request message includes first information indicating that a gNB Distributed Unit (gNB-DU) device is supported by a gNB Centralized Unit-Control Plane (gNB-CU-CP) device to be connected to a User Plane Function (UPF) device without a gNB Centralized Unit User Plane (gNB-CU-UP) device. The method includes transmitting an Nsmf_PDUSession_CreateSMContext response message to the AMF device. The Nsmf_PDUSession_CreateSMContext response message includes second information indicating that the UPF device supports the gNB-DU device being connected to the UPF device without the gNB-CU-UP device. The method includes transmitting an N4 session establishment request message to the UPF device. The N4 session establishment request message includes the first information. The method includes receiving an N4 session establishment response message from the UPF device. The N4 session establishment response message includes a gNB-CU-UP UE E1AP ID and third information indicating a pair of an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID) for uplink data processing. The method includes transmitting a Namf_Communication_N1N2MessageTransfer message to the AMF device.The Namf_Communication_N1N2MessageTransfer message includes the gNB-CU-UP UE E1AP ID and the third information. The method includes performing a PDU session establishment procedure.

[0014] In an aspect of the present disclosure, a method of a User Plane Function (UPF) device includes communicating with a gNB Distributed Unit (gNB-DU) device without a gNB Centralized Unit User Plane (gNB-CU-UP) device and communicating with a gNB Centralized Unit-Control Plane (gNB-CU-CP) device without the gNB-CU-UP device.

[0015] In an aspect of the present disclosure, a communication device includes means for executing functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and a User Plain Function (UPF) device, means for communicating with a gNB Distributed Unit (gNB-DU) device, and means for communicating with a gNB Centralized Unit-Control Plane (gNB-CU-CP) device.

[0016] In an aspect of the present disclosure, a gNB Centralized Unit-Control Plane (gNB-CU-CP) apparatus includes means for receiving a Protocol Data Unit (PDU) session establishment request message from a User Equipment (UE). The gNB-CU-CP apparatus includes means for transmitting an UPLINK NAS TRANSPORT message to an Access and Mobility management Function (AMF) apparatus. The UPLINK NAS TRANSPORT message includes the PDU session establishment request message and information indicating that the gNB-CU-CP apparatus supports communication with a communication apparatus that executes functions of a gNB Centralized Unit User Plane (gNB-CU-UP) apparatus and functions of a User Plain Function (UPF) apparatus. The gNB-CU-CP apparatus includes means for receiving an INITIAL CONTEXT SETUP REQUEST message from the AMF apparatus. The INITIAL CONTEXT SETUP REQUEST message includes information regarding the gNB-CU-UP. The gNB-CU-CP apparatus includes means for selecting the gNB-CU-UP based on the information regarding the gNB-CU-UP. The gNB-CU-CP apparatus includes means for performing a PDU session establishment procedure for the UE.

[0017] In an aspect of the present disclosure, an Access and Mobility management Function (AMF) device includes means for receiving an UPLINK NAS TRANSPORT message from a gNB Centralized Unit Control Plane (gNB-CU-CP) device. The UPLINK NAS TRANSPORT message includes a Protocol Data Unit (PDU) session establishment request message and information indicating that the gNB-CU-CP device supports communication with a communication device that executes functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and functions of a User Plain Function (UPF) device. The AMF device includes means for transmitting an Nsmf_PDUSession_CreateSMContext request message to a Session Management Function (SMF) device. The Nsmf_PDUSession_CreateSMContext request message includes the information. The AMF device includes means for receiving an Nsmf_PDUSession_CreateSMContext response message from the SMF device. The Nsmf_PDUSession_CreateSMContext response message includes information regarding the UPF device. The AMF device includes means for receiving a Namf_Communication_N1N2MessageTransfer message from the SMF device. The Namf_Communication_N1N2MessageTransfer message includes information regarding the gNB-CU-UP device. The AMF device includes means for transmitting an INITIAL CONTEXT SETUP REQUEST message to the gNB-CU-CP device. The INITIAL CONTEXT SETUP REQUEST message includes the information regarding the gNB-CU-UP device.The AMF device includes means for performing a PDU session establishment procedure.

[0018] In an aspect of the present disclosure, a Session Management Function (SMF) device includes means for receiving an Nsmf_PDUSession_CreateSMContext request message from an Access and Mobility management Function (AMF) device. The Nsmf_PDUSession_CreateSMContext request message includes information indicating that a gNB Centralized Unit Control Plane (gNB-CU-CP) device supports communication with a communication device that executes functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and a User Plain Function (UPF) device. The SMF device includes means for transmitting an Nsmf_PDUSession_CreateSMContext response message to the AMF device. The Nsmf_PDUSession_CreateSMContext response message includes information regarding the UPF device. The SMF device includes means for selecting the UPF device when the Nsmf_PDUSession_CreateSMContext request message includes the information. The SMF device includes means for contacting the communication device to secure resources for processing user data. The SMF device includes means for transmitting a Namf_Communication_N1N2MessageTransfer message to the AMF device. The Namf_Communication_N1N2MessageTransfer message includes information regarding the gNB-CU-UP device. The SMF device includes means for performing a PDU session establishment procedure.

[0019] In an aspect of the present disclosure, a gNB Distributed Unit (gNB-DU) device includes means for communicating with a gNB Centralized Unit-Control Plane (gNB-CU-CP) device and means for communicating with a User Plane Function (UPF) device without involving a gNB Centralized Unit User Plane (gNB-CU-UP) device.

[0020] In an aspect of the present disclosure, a gNB Centralized Unit-Control Plane (gNB-CU-CP) device includes means for communicating with a gNB Distributed Unit (gNB-DU) device and means for communicating with a User Plane Function (UPF) device without involving a gNB Centralized Unit User Plane (gNB-CU-UP) device.

[0021] In an aspect of the present disclosure, an Access and Mobility management Function (AMF) device includes means for receiving an UPLINK NAS TRANSPORT message from a gNB Centralized Unit Control Plane (gNB-CU-CP) device. The UPLINK NAS TRANSPORT message includes first information indicating that the gNB-CU-CP device supports the connection of a gNB Distributed Unit (gNB-DU) device to a User Plane Function (UPF) device without involving a gNB Centralized Unit User Plane (gNB-CU-UP) device. The AMF device includes means for transmitting an Nsmf_PDUSession_CreateSMContext request message to a Session Management Function (SMF) device. The Nsmf_PDUSession_CreateSMContext request message includes the first information. The AMF device includes means for receiving an Nsmf_PDUSession_CreateSMContext response message from the SMF device. The Nsmf_PDUSession_CreateSMContext response message includes second information indicating that the UPF device supports the connection of the gNB-DU device to the UPF device without involving the gNB-CU-UP device. The AMF device includes means for receiving a Namf_Communication_N1N2MessageTransfer message from the SMF device.The Namf_Communication_N1N2MessageTransfer message includes a gNB-CU-UP UE E1AP ID and third information indicating a pair of an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID) for uplink data processing. The AMF device includes means for transmitting an INITIAL CONTEXT SETUP REQUEST message to the gNB-CU-CP device. The INITIAL CONTEXT SETUP REQUEST message includes the gNB-CU-UP UE E1AP ID and the third information. The AMF device includes means for receiving an INITIAL CONTEXT SETUP RESPONSE message from the gNB-CU-CP device. The AMF device includes means for performing a PDU session establishment procedure.

[0022] In an aspect of the present disclosure, a Session Management Function (SMF) device includes means for receiving an Nsmf_PDUSession_CreateSMContext request message from an Access and Mobility management Function (AMF) device. The Nsmf_PDUSession_CreateSMContext request message includes first information indicating that a gNB Distributed Unit (gNB-DU) device is supported by a gNB Centralized Unit-Control Plane (gNB-CU-CP) device to be connected to a User Plane Function (UPF) device without a gNB Centralized Unit User Plane (gNB-CU-UP) device. The SMF device includes means for transmitting an Nsmf_PDUSession_CreateSMContext response message to the AMF device. The Nsmf_PDUSession_CreateSMContext response message includes second information indicating that the UPF device supports the gNB-DU device being connected to the UPF device without the gNB-CU-UP device. The SMF device includes means for transmitting an N4 session establishment request message to the UPF device. The N4 session establishment request message includes the first information. The SMF device includes means for receiving an N4 session establishment response message from the UPF device. The N4 session establishment response message includes a gNB-CU-UP UE E1AP ID and third information indicating a pair of an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID) for uplink data processing. The SMF device includes means for transmitting a Namf_Communication_N1N2MessageTransfer message to the AMF device.The Namf_Communication_N1N2MessageTransfer message includes the gNB-CU-UP UE E1AP ID and the third information. The SMF device includes means for performing a PDU session establishment procedure.

[0023] In an aspect of the present disclosure, a User Plane Function (UPF) device includes means for communicating with a gNB Distributed Unit (gNB-DU) device without a gNB Centralized Unit User Plane (gNB-CU-UP) device, and means for communicating with a gNB Centralized Unit-Control Plane (gNB-CU-CP) device without the gNB-CU-UP device.

Brief Description of the Drawings

[0024]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Best Mode for Carrying Out the Invention

[0025] The present disclosure relates to a method of a communication device, a method of a gNB-CU-CP device, a method of an AMF device, a method of an SMF device, a method of a gNB-DU device, a method of a UPF device, a communication device, a gNB-CU-CP device, an AMF device, an SMF device, a gNB-DU device, and a UPF device.

[0026] In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the aspects of the present disclosure. It will be apparent, however, that one or more aspects may be practiced without these specific details. In other instances, well-known structures and devices are shown schematically in order to simplify the drawings.

[0027] Those skilled in the art will understand that the elements in the figures are shown simplified and need not be drawn to scale. Further, with respect to the structure of the device, one or more components of the device may sometimes be represented by conventional symbols in the figures, and the figures may show only such specific details as are appropriate to enable those skilled in the art who benefit from the description herein to readily understand the aspects of the present disclosure without obscuring the figures with details that are well understood to those of ordinary skill in the art.

[0028] To facilitate an understanding of the principles of the present disclosure, reference is now made to the aspects shown in the figures and specific terms are used to describe the principles. It will be understood, however, that no intention is thereby being made to limit the scope of the present disclosure. Such modifications and further refinements of the shown system, and such further applications of the principles of the present disclosure as would normally occur to one of ordinary skill in the art, are to be construed as being within the scope of the present disclosure.

[0029] The terms "comprising", "comprises", or any other variation thereof are intended to cover non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may also include other steps not expressly listed or inherent to such a process or method. Similarly, one or more devices, entities, subsystems, elements, structures, or components that begin with "comprising" do not, in the absence of further constraints, exclude the presence of other devices, subsystems, elements, structures, components, additional devices, additional subsystems, additional elements, additional structures, or additional components. Throughout this specification, the phrases "in an aspect", "in another aspect", and similar terms, when they appear, may all refer to the same aspect but do not necessarily have to.

[0030] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. The systems, methods, and examples provided herein are illustrative only and not intended to be limiting.

[0031] In the following specification and claims, reference is made to a number of terms that are defined to have the following meanings. The singular forms "a", "an", and "the" include plural references unless the context clearly dictates otherwise.

[0032] As used herein, information is associated with data and findings such that the data is meaningful information representing a value attributable to a parameter. Further, findings mean the understanding of an abstract or concrete concept. Note that this exemplary system is simplified to facilitate the description of the subject matter of the present disclosure and is not intended to limit the scope of the present disclosure. In addition to or instead of the system, other devices, systems, and configurations may be used to implement the aspects disclosed herein, and all such aspects are assumed to be within the scope of the present disclosure.

[0033] Each of the aspects, and the elements included in each of the aspects described below, can be implemented independently or in combination with each other. The aspects include different novel features from each other. Therefore, the aspects contribute to the achievement of the objective or the solution of different problems from each other, and contribute to obtaining different advantages from each other.

[0034] <Abbreviations> For the purposes of this specification, the abbreviations given in Non-Patent Document 1 and the following ones apply. The abbreviations defined in this specification take precedence over the definitions of the same abbreviations in Non-Patent Document 1 if there are the same abbreviations in Non-Patent Document 1. 4G-GUTI 4G Globally Unique Temporary UE Identity 5GC 5G Core Network 5GLAN 5G Local Area Network 5GS 5G System 5G-AN 5G Access Network 5G-AN PDB 5G Access Network Packet Delay Budget 5G-EIR 5G-Equipment Identity Register 5G-GUTI 5G Globally Unique Temporary Identifier 5G-BRG 5G Broadband Residential Gateway 5G-CRG 5G Cable Residential Gateway 5G GM 5G Grand Master 5G-RG 5G Residential Gateway 5G-S-TMSI 5G S-Temporary Mobile Subscription Identifier 5G VN 5G Virtual Network 5QI 5G QoS Identifier ABBA Anti-Bidding-down Between Architectures AF Application Function AMF Access and Mobility Management Function AN Access Network API Application Programming Interface AS Access Stratum ATSSS Access Traffic Steering, Switching, Splitting ATSSS-LL ATSSS Low-Layer AUSF Authentication Server Function AUTN Authentication token BBF Broadband Forum BMCA Best Master Clock Algorithm BSF Binding Support Function CAG Closed Access Group CAPIF Common API Framework for 3GPP northbound APIs CHF Charging Function CN PDB Core Network Packet Delay Budget CP Control Plane CU Centralized Unit / Central Unit DAPS Dual Active Protocol Stacks DL Downlink DN Data Network DNAI DN Access Identifier DNN Data Network Name DRB Data Radio Bearer DRX Discontinuous Reception DS-TT Device-side TSN translator DU Distributed Unit ePDG evolved Packet Data Gateway EAP Extensible Authentication Protocol EBI EPS Bearer Identity EPS Evolved Packet System EUI Extended Unique Identifier FAR Forwarding Action Rule FN-BRG Fixed Network Broadband RG FN-CRG Fixed Network Cable RG FN-RG Fixed Network RG FQDN Fully Qualified Domain Name GFBR Guaranteed Flow Bit Rate GMLC Gateway Mobile Location Centre gNB-CU-CP gNB Central Unit Control Plane gNB-CU-UP gNB Central Unit User Plane gNB-DU gNB Distributed Unit GPSI Generic Public Subscription Identifier GUAMI Globally Unique AMF Identifier GUTI Globally Unique Temporary UE Identity HR Home Routed (roaming) IAB Integrated access and backhaul IMEI International Mobile Equipment Identity IMEI / TAC IMEI Type Allocation Code IMS IP Multimedia Subsystem IOWN Innovative Optical and Wireless Network IPUPS Inter PLMN UP Security I-SMF Intermediate SMF I-UPF Intermediate UPF LADN Local Area Data Network LBO Local Break Out (roaming) LMF Location Management Function LoA Level of Automation LPP LTE Positioning Protocol LRF Location Retrieval Function LTE Long Term Evolution MAC Medium Access Control MCC Mobile country code MCX Mission Critical Service MDBV Maximum Data Burst Volume MFBR Maximum Flow Bit Rate MICO Mobile Initiated Connection Only MNC Mobile Network Code MO Mobile Originated MPS Multimedia Priority Service MPTCP Multi-Path TCP Protocol MT Mobile Terminated MT Mobile Termination N3IWF Non-3GPP InterWorking Function N5CW Non-5G-Capable over WLAN NAI Network Access Identifier NAS Non-Access Stratum NEF Network Exposure Function NF Network Function NFV Network Functions Virtualization NGAP Next Generation Application Protocol ngKSI Next Generation Key Set Identifier NID Network identifier NPN Non-Public Network NR New Radio NRF Network Repository Function NSI ID Network Slice Instance Identifier NSSAA Network Slice-Specific Authentication and Authorization NSSAAF Network Slice-Specific Authentication and Authorization Function NSSAI Network Slice Selection Assistance Information NSSF Network Slice Selection Function NSSP Network Slice Selection Policy NW-TT Network-side TSN translator NWDAF Network Data Analytics Function O&M Operations & Maintenance O-RAN Open RAN Alliance O-DU O-RAN Distributed Unit O-CU O-RAN Centralized Unit O-RU O-RAN Radio Unit PCF Policy Control Function PDB Packet Delay Budget PDCP Packet Data Convergence Protocol PDR Packet Detection Rule PDU Protocol Data Unit PEI Permanent Equipment Identifier PER Packet Error Rate PFD Packet Flow Description PLMN Public Land Mobile Network PNI-NPN Public Network Integrated Non-Public Network PPD Paging Policy Differentiation PPF Paging Proceed Flag PPI Paging Policy Indicator PSA PDU Session Anchor PTP Precision Time Protocol QFI QoS Flow Identifier QoE Quality of Experience QoS Quality of Service RACS Radio Capabilities Signalling optimisation (R)AN (Radio) Access Network RG Residential Gateway RU Radio Unit RIM Remote Interference Management RLC Radio Link Control RQA Reflective QoS Attribute RQI Reflective QoS Indication RRC Radio Resource Control RSN Redundancy Sequence Number SA NR Standalone New Radio SBA Service Based Architecture SBI Service Based Interface SCP Service Communication Proxy SD Slice Differentiator SDAP Service Data Adaptation Protocol SEAF Security Anchor Functionality SEPP Security Edge Protection Proxy SMF Session Management Function SMS Short Message Service SMSF Short Message Service Function SN Sequence Number SN name Serving Network Name. SNPN Stand-alone Non-Public Network S-NSSAI Single Network Slice Selection Assistance Information SOR Steering Of Roaming SSC Session and Service Continuity SSCMSP Session and Service Continuity Mode Selection Policy SST Slice / Service Type SUCI Subscription Concealed Identifier SUPI Subscription Permanent Identifier SV Software Version TAI Tracking Area Identity TCP Transmission Control Protocol TNAN Trusted Non-3GPP Access Network TNAP Trusted Non-3GPP Access Point TNGF Trusted Non-3GPP Gateway Function TNL Transport Network Layer TNLA Transport Network Layer Association TSC Time Sensitive Communication TSCAI TSC Assistance Information TSN Time Sensitive Networking TSN GM TSN Grand Master TSP Traffic Steering Policy TT TSN Translator TWIF Trusted WLAN Interworking Function UCMF UE radio Capability Management Function UDM Unified Data Management UDR Unified Data Repository UDSF Unstructured Data Storage Function UE User Equipment UL Uplink UL CL Uplink Classifier UP User Plane UPF User Plane Function URLLC Ultra Reliable Low Latency Communication URRP-AMF UE Reachability Request Parameter for AMF URSP UE Route Selection Policy UU Interface between User Equipment and Radio Access Network VID VLAN Identifier VLAN Virtual Local Area Network W-5GAN Wireline 5G Access Network W-5GBAN Wireline BBF Access Network W-5GCAN Wireline 5G Cable Access Network W-AGF Wireline Access Gateway Function WLAN Wireless Local Area Network WUS Wake Up Signal

[0035] <Definition> For the purposes of this specification, the terms and definitions given in Non-Patent Document 1, and the following, apply. Terms defined in this specification take precedence over the definitions of the same terms in Non-Patent Document 1, if any.

[0036] <General Introduction> This disclosure proposes a solution that provides optimized user plane processing in 5GS. For example, this disclosure proposes a solution that improves the latency related to user data processing in 5GS.

[0037] FIG. 1 shows an NG-(R)AN architecture as defined by the combination of Non-Patent Document 13 and Non-Patent Document 2.

[0038] This is the target architecture, and this disclosure proposes a development therefrom.

[0039] Note that the following interpretations may apply in this disclosure. - gNB-CU-CP may be interpreted as the gNB-CU control plane. - CU-CP may be interpreted as the gNB-CU control plane. - gNB-CU-UP may be interpreted as the gNB-CU user plane. - CU-UP may be interpreted as the gNB-CU user plane. - DU may be interpreted as gNB-DU. - The F1 interface may be interpreted as the F1 reference point.

[0040] This disclosure mainly discloses solutions for gNBs, but all aspects of this disclosure are equally applicable to ng-eNBs. To apply the solutions to ng-eNBs, the following replacements are necessary. - gNB-CU-CP and CU-CP are replaced by ng-eNB-CU-CP. - gNB-CU-UP and CU-UP are replaced by ng-eNB-CU-UP. - gNB-DU and DU are replaced by ng-eNB-DU. - The F1 interface and F1 reference point are replaced by the W1 interface and W1 reference point, respectively.

[0041] <First Aspect: NG-(R)AN Architecture with Collocated gNB-CU-UP and UPF> Figure 2 shows a proposed NG-(R)AN architecture with collocated (or co-located) gNB-CU-UP and UPF. Collocated gNB-CU-UP and UPF means that the gNB-CU-UP and UPF share the same physical server, the same hardware module, or the same virtual module. For example, a blade server for gNB-CU-UP and another blade server for UPF are attached to the same chassis. For example, the functions of gNB-CU-UP and the functions of UPF can be implemented by the same memory and at least one same hardware processor connected to the memory in a communication device.

[0042] This approach can reduce the total number of hardware involved in the end-to-end PDU session, so the failure of gNB-CU-UP due to hardware failure, virtual resource failure, and related equipment failure can be reduced.

[0043] In addition, since this architecture can reduce the N3 connection, the service quality of the transport layer in 5GS can be improved by this architecture.

[0044] The detailed process of establishing a PDU session using co-located gNB-CU-UP and UPF is shown in Figure 3.

[0045] The detailed process of the procedure is described as follows.

[0046] 1. The UE sends an RRC message containing the NAS message "PDU session establishment request" to gNB-CU-CP6201 via gNB-DU61.

[0047] 2. gNB-CU-CP6201 sends an UPLINK NAS TRANSPORT message containing the NAS message "PDU session establishment request" and combined UP support parameters to AMF70. The combined UP support parameters indicate to AMF70 that gNB-CU-CP6201 supports the co-located gNB-CU-UP and UPF configuration based on the instructions from 5GC. The combined UP support parameters may indicate to the AMF that gNB-CU-CP6201 supports the co-located gNB-CU-UP and UPF configuration. The combined UP support parameters may indicate that gNB-CU-CP6201 supports communication with a communication device that executes the functions of the co-located gNB-CU-UP and UPF.

[0048] When the AMF 70 receives a UPLINK NAS TRANSPORT message from the gNB-CU-CP 6201, the AMF 70 sends an Nsmf_PDUSession_CreateSMContext request message including the NAS message "PDU session establishment request" and the combined UP support parameters to the SMF 7101. The NAS message "PDU session establishment request" may be the same as the NAS message "PDU session establishment request" included in the UPLINK NAS TRANSPORT message in step 2. The combined UP support parameters may be the same as the combined UP support parameters in the UPLINK NAS TRANSPORT message in step 2. The combined UP support parameters may indicate to the SMF 7101 that at least one of the gNB-CU-CP 7101 and the AMF 70 supports a co-located gNB-CU-UP and UPF configuration based on an instruction from the 5GC. The combined UP support parameters may indicate to the SMF 7101 that at least one of the gNB-CU-CP 6201 and the AMF 70 supports a co-located gNB-CU-UP and UPF configuration.

[0049] When the SMF 7101 receives an Nsmf_PDUSession_CreateSMContext request message including the NAS message "PDU session establishment request" from the AMF 70, the SMF 7101 sends an Nsmf_PDUSession_CreateSMContext response message to the AMF 70. The Nsmf_PDUSession_CreateSMContext response message may include the combined UP support parameters. The combined UP support parameters indicate to the AMF 70 that the UPF can be combined with the gNB-CU-UP. The combined UP support parameters may indicate to the AMF 70 that the UPF can perform the functions of the gNB-CU-UP. The combined UP support parameters may indicate to the AMF 70 that the UPF can perform the functions of the UPF and the gNB-CU-UP.

[0050] For example, SMF7101 may obtain information indicating whether UPF7201 can be connected to gNB-CU-UP from another network node (e.g., UPF7201). When SMF7101 obtains information indicating that UPF7201 can be connected to gNB-CU-UP, SMF7101 may send an Nsmf_PDUSession_CreateSMContext response message including a combined UP support parameter indicating that UPF7201 can be connected to gNB-CU-UP to AMF70.

[0051] For example, SMF7101 may pre-store information indicating that UPF7201 can be connected to gNB-CU-UP, and SMF7101 may send an Nsmf_PDUSession_CreateSMContext response message including a combined UP support parameter indicating that UPF7201 can be connected to gNB-CU-UP to AMF70.

[0052] 5. When the combined UP support parameter is indicated in the Nsmf_PDUSession_CreateSMContext request message, SMF7101 selects UPF7201 that can be connected to gNB-CU-UP and contacts UPF7201 to ensure the resources required for processing user data at UPF7201. For example, when SMF7101 obtains information indicating that UPF7201 can be connected to gNB-CU-UP, or when SMF7101 stores information indicating that UPF7201 can be connected to gNB-CU-UP, SMF7101 may select UPF7201 as the UPF that can be connected to gNB-CU-UP.

[0053] For example, SMF7101 may send an N4 session establishment request message to UPF7201 to ensure the resources required for processing user data at UPF7201, and UPF7201 may send an N4 session establishment response message in response to the N4 session establishment request message. For example, after ensuring the resources required for processing user data at UPF7201, UPF7201 sends an N4 session establishment response message.

[0054] Note that step 5 can be performed before step 4.

[0055] 6. The SMF 7101 sends a Namf_Communication_N1N2MessageTransfer message including the PDU session ID and N2 SM information to the AMF 70. The N2 SM information includes the PDU session ID, CN tunnel information, and RAN tunnel information. The RAN tunnel information (info) (or the RAN tunnel information) can be the FQDN or Internet Protocol (IP) address of the gNB-CU-UP that can be the best pair with the UPF 7201 selected for the PDU session, or an IP address having the Tunnel Endpoint Identifier (TEID) of the gNB-CU-UP. The RAN tunnel information can be the FQDN or IP address of the gNB-CU-UP collocated with the UPF 7201 selected for the PDU session, or an IP address having the TEID of the gNB-CU-UP. The RAN tunnel information can be the FQDN or IP address of the gNB-CU-UP 62021 collocated with the UPF 7201 selected for the PDU session, or an IP address having the TEID of the gNB-CU-UP 62021. The RAN tunnel information can be the FQDN of the gNB-CU-UP 62021 or the IP address of the gNB-CU-UP 62021, or an IP address having the TEID of the gNB-CU-UP 62021. The PDU session ID can be used by the AN to associate with the Data Radio Bearer (DRB) between the AN and the UE3.

[0056] For example, SMF7101 may obtain RAN tunnel information from another network node (e.g., gNB-CU-UP62021). When SMF7101 obtains the RAN tunnel information, SMF7101 may send a Namf_Communication_N1N2MessageTransfer message containing the RAN tunnel information to AMF70.

[0057] For example, SMF7101 may pre-store the RAN tunnel information, and SMF7101 may send a Namf_Communication_N1N2MessageTransfer message containing the RAN tunnel information to AMF70.

[0058] 7. AMF70 sends an INITIAL CONTEXT SETUP REQUEST message containing the PDU session ID, CN tunnel information, and RAN tunnel information to gNB-CU-CP6201. The PDU session ID, CN tunnel information, and RAN tunnel information may each be the same as the PDU session ID, CN tunnel information, and RAN tunnel information received in step 6.

[0059] 8. Upon receiving the INITIAL CONTEXT SETUP REQUEST message containing the RAN tunnel information, gNB-CU-CP6201 selects gNB-CU-UP based on the received RAN tunnel information. For example, when gNB-CU-UP62021 is indicated by the RAN tunnel information (e.g., when the FQDN or IP address of gNB-CU-UP62021, or the IP address having the TEID of gNB-CU-UP62021 is indicated by the RAN tunnel information), gNB-CU-CP6201 may select gNB-CU-UP62021.

[0060] 9. gNB-CU-CP 6201 sends a BEARER CONTEXT SETUP REQUEST message to gNB-CU-UP 62021. For example, gNB-CU-CP 6201 may send the BEARER CONTEXT SETUP REQUEST message to gNB-CU-UP 62021 by using the FQDN or IP address of gNB-CU-UP 62021 indicated by the RAN tunnel information, or an IP address having the TEID of gNB-CU-UP 62021.

[0061] 10. gNB-CU-UP 62021 sends a BEARER CONTEXT SETUP RESPONSE message to gNB-CU-CP 6201.

[0062] 11. When receiving the BEARER CONTEXT SETUP RESPONSE message from gNB-CU-UP 62021, gNB-CU-CP 6201 contacts gNB-DU 61 to set up the F1 UE context. For example, gNB-CU-CP 6201 may initiate the F1 UE context setup procedure to set up the F1 UE context.

[0063] 12. gNB-CU-CP 6201 sends an INITIAL UE CONTEXT SETUP RESPONSE message to AMF 70.

[0064] 13. The PDU session establishment procedure continues from step 15 in section 4.3.2.2.1 of Non-Patent Document 14.

[0065] <First Variant of the First Aspect: Service Request Procedure> The service request procedure for gNB-CU-UP and UPF arranged together can be realized with the following changes to the first aspect.

[0066] - In step 1, the RRC message includes a service request message instead of a PDU session establishment request message.

[0067] - In step 2, the UPLINK NAS TRANSPORT message includes a NAS service request message instead of a PDU session establishment request message.

[0068] - In step 3, the message name is Nsmf_PDUSession_UpdateSMContext request instead of Nsmf_PDUSession_CreateSMContext request. For example, the AMF 70 may send an Nsmf_PDUSession_UpdateSMContext request message instead of an Nsmf_PDUSession_CreateSMContext request message.

[0069] - In step 4, the message name is Nsmf_PDUSession_UpdateSMContext response instead of Nsmf_PDUSession_CreateSMContext response. For example, the SMF 7101 may send an Nsmf_PDUSession_UpdateSMContext response message instead of an Nsmf_PDUSession_CreateSMContext response message.

[0070] - In step 13, the subsequent procedure starts from step 15 of the UE-triggered service request procedure in item 4.2.3.2 of Non-Patent Document 14.

[0071] At least one of the first aspect and the modification examples of the first aspect proposes a solution for providing optimized user plane processing in 5GS.

[0072] For example, at least one of the first aspect and the modification examples of the first aspect proposes a solution for improving the latency related to user data processing in 5GS.

[0073] For example, according to at least one of the first aspect and the modification example of the first aspect, the total number of hardware involved in the end-to-end PDU session can be reduced, so that the failure of the gNB-CU-UP due to hardware failure, virtual resource failure, and related equipment failure can be reduced.

[0074] For example, according to at least one of the first aspect and the modification example of the first aspect, the N3 connection can be reduced, so that the service quality of the transport layer in 5GS can be improved.

[0075] For example, at least one of the first aspect and the modification example of the first aspect can solve the problem regarding the transmission delay that occurs every time user data crosses the user plane entity.

[0076] For example, at least one of the first aspect and the modification example of the first aspect can solve the problem that the current 5GS architecture may be too redundant to meet the low latency requirements for time-critical applications.

[0077] <Second Aspect: NG-(R)AN Architecture without gNB-CU-UP> Figure 4 shows a proposed NG-(R)AN architecture without gNB-CU-UP.

[0078] Since this architecture can reduce the N3 connection, the service quality of the transport layer in 5GS can be improved by this architecture.

[0079] With this NG-(R)AN architecture, the gNB-DU is directly connected to the UPF. For example, the gNB-DU communicates with the UPF without gNB-CU-UP. For example, the UPF communicates with the gNB-DU without gNB-CU-UP.

[0080] With this NG-(R)AN architecture, the gNB-CU-CP is directly connected to the UPF. For example, the gNB-CU-CP communicates with the UPF without the gNB-CU-UP. For example, the UPF communicates with the gNB-CU-CP without the gNB-CU-UP.

[0081] Note that the reference point between the gNB-DU61 and the UPF7201 is shown as F1-U in Figure 4, and the reference point between the gNB-DU61 and the UPF7201 can be interpreted as the N3 reference point from the perspective of the UPF7201.

[0082] Note that the reference point between the gNB-DU61 and the UPF7202 is shown as F1-U in Figure 4, and the reference point between the gNB-DU61 and the UPF7202 can be interpreted as the N3 reference point from the perspective of the UPF7202.

[0083] Note that the UPF7201 can be interpreted as the gNB-CU-UP from the perspective of the gNB-DU61.

[0084] Note that the UPF7201 can be interpreted as the gNB-CU-UP from the perspective of the gNB-CU-CP6201.

[0085] Note that the UPF7202 can be interpreted as the gNB-CU-UP from the perspective of the gNB-DU61.

[0086] Note that the UPF7202 can be interpreted as the gNB-CU-UP from the perspective of the gNB-CU-CP6201.

[0087] The detailed process of establishing a PDU session without the gNB-CU-UP is shown in Figure 5.

[0088] The detailed process of the procedure is described as follows.

[0089] The UPF 7201 regarded as the gNB-CU-UP by the 0-1 gNB-CU-CP sends a GNB-CU-CP E1 SETUP REQUEST message including a gNB-CU-UP ID, a gNB-CU-UP name, and a No CU-UP support parameter to the gNB-CU-CP 6201. The "No CU-UP support parameter" indicates to the gNB-CU-CP 6201 that the UPF 7201 supports the "No gNB-CU-UP feature". The "No gNB-CU-UP feature" means (or indicates) that the gNB-DU can be directly connected to the UPF without the gNB-CU-UP. For example, the No gNB-CU-UP feature may mean that the gNB-DU 61 can be directly connected to the UPF 7201 without the gNB-CU-UP. For example, the No gNB-CU-UP feature may mean that the gNB-DU can communicate with the UPF without the gNB-CU-UP.

[0090] For example, the UPF 7201 may determine whether the UPF 7201 supports the No gNB-CU-UP feature based on the local configuration in the UPF 7201 or the stored information in the UPF 7201. If the UPF 7201 determines that the UPF 7201 supports the No gNB-CU-UP feature, the UPF 7201 may include the No CU-UP support parameter in the GNB-CU-CP E1 SETUP REQUEST message.

[0091] The No gNB-CU-UP feature may be represented by a DU-UPF direct connection feature, a DU-UPF direct bearer feature, an optimized user plane RAN feature, or any other indication.

[0092] When gNB-CU-CP 6201 receives a 0-2.GNB-CU-CP E1 SETUP REQUEST message, it sends a GNB-CU-CP E1 SETUP RESPONSE message containing the no-CU-UP support parameter to UPF 7201. The no-CU-UP support parameter indicates to UPF 7201 that gNB-CU-CP 6201 supports the no-gNB-CU-UP function. Through the mutual function negotiation regarding the no-gNB-CU-UP function between UPF 7201 and gNB-CU-CP 6201, this no-gNB-CU-UP function can be activated when both UPF 7201 and gNB-CU-CP support the function.

[0093] For example, gNB-CU-CP 6201 may determine whether it supports the no-gNB-CU-UP function based on the local configuration in gNB-CU-CP 6201 or the stored information in gNB-CU-CP 6201. If gNB-CU-CP 6201 supports the no-gNB-CU-UP function, gNB-CU-CP 6201 may include the no-CU-UP support parameter in the GNB-CU-CP E1 SETUP RESPONSE message.

[0094] 1. UE 3 sends an RRC message containing the NAS message "PDU session establishment request" to gNB-CU-CP 6201 via gNB-DU 61.

[0095] 2. gNB-CU-CP 6201 sends an UPLINK NAS TRANSPORT message containing the NAS message "PDU session establishment request" and the no-CU-UP support parameter to AMF 70. The no-CU-UP support parameter indicates to AMF 70 that gNB-CU-CP 6201 supports the no-gNB-CU-UP function.

[0096] When the AMF 70 receives a UPLINK NAS TRANSPORT message from the gNB-CU-CP 6201, the AMF 70 sends an Nsmf_PDUSession_CreateSMContext request message including the NAS message "PDU session establishment request" and no CU-UP support parameters to the SMF 7101. The no CU-UP support parameters may indicate to the SMF 7101 that the gNB-CU-CP 6201 supports the no gNB-CU-UP function.

[0097] When the SMF 7101 receives an Nsmf_PDUSession_CreateSMContext request message including the NAS message "PDU session establishment request" from the AMF 70, the SMF 7101 sends an Nsmf_PDUSession_CreateSMContext response message to the AMF 70. The Nsmf_PDUSession_CreateSMContext response message may include no CU-UP support parameters. The no CU-UP support parameters indicate to the AMF 70 that the UPF supports the no gNB-CU-UP function. The no CU-UP support parameters may indicate to the AMF 70 that the UPF 7201 supports the no gNB-CU-UP function.

[0098] For example, the SMF 7101 may obtain information indicating whether the UPF supports the no gNB-CU-UP function from another network node (e.g., the UPF 7201). When the SMF 7101 obtains information indicating that the UPF 7201 supports the no gNB-CU-UP function, the SMF 7101 may send an Nsmf_PDUSession_CreateSMContext response message including no CU-UP support parameters indicating that the UPF 7201 supports the no gNB-CU-UP function to the AMF 70.

[0099] For example, SMF7101 may pre-store information indicating that UPF7201 supports the non-gNB-CU-UP function, and SMF7101 may send an Nsmf_PDUSession_CreateSMContext response message including a non-CU-UP support parameter indicating that UPF7201 supports the non-gNB-CU-UP function to AMF70.

[0100] 5. When the non-CU-UP support parameter is indicated in the Nsmf_PDUSession_CreateSMContext request message, SMF7101 selects a UPF that supports the non-gNB-CU-UP function and sends an N4 session establishment request message including the non-CU-UP support parameter to UPF7201. The non-CU-UP support parameter may indicate to UPF7201 that gNB-CU-CP6201 supports the non-gNB-CU-UP function.

[0101] For example, when the non-CU-UP support parameter is included in the Nsmf_PDUSession_CreateSMContext request message (or the non-CU-UP support parameter included in the Nsmf_PDUSession_CreateSMContext request message indicates that gNB-CU-CP6201 supports the non-gNB-CU-UP function, and the non-CU-UP support parameter included in the Nsmf_PDUSession_CreateSMContext response message indicates that UPF7201 supports the non-gNB-CU-UP function), SMF7101 may select UPF7201 as the UPF that supports the non-gNB-CU-UP function, and SMF7101 sends an N4 session establishment request message including the non-CU-UP support parameter indicating that gNB-CU-CP6201 supports the non-gNB-CU-UP function.

[0102] Upon receiving an N4 session establishment request message that does not contain CU-UP support parameters, the UPF 7201 secures the resources necessary for processing user data at the UPF 7201 and the resources necessary for processing user data as the gNB-CU-UP.

[0103] When all the necessary resources are prepared, the UPF 7201 sends an N4 session establishment response message containing the gNB-CU-UP ID, the gNB-CU-UP UE E1AP ID, and the PDU session resource setup list parameters to the SMF 7101. The PDU session resource setup list parameters include UL UP parameters that include an IP address and TEID pair for UL data processing. The gNB-CU-UP ID indicates the identifier of the UPF 7201 as the gNB-CU-UP. The gNB-CU-UP ID is transferred to the gNB-CU-CP 6201 via the AMF 70, and the gNB-CU-CP 6201 uses this information to find the destination of the BEARER CONTEXT SETUP REQUEST message in step 8. The gNB-CU-UP UE E1AP ID can be assigned to uniquely identify the UE at the E1 interface within the UPF 7201.

[0104] 6. The SMF 7101 sends a Namf_Communication_N1N2MessageTransfer message containing the PDU session ID and N2 SM information to the AMF 70. The N2 SM information includes the PDU session ID, CN tunnel information, gNB-CU-UP ID, gNB-CU-UP UE E1AP ID, and PDU session resource set-up list parameters. The PDU session ID can be used by the AN to associate with a Data Radio Bearer (DRB) between the AN and the UE. The gNB-CU-UP UE E1AP ID and PDU session resource set-up list parameters can be the same as the gNB-CU-UP UE E1AP ID and PDU session resource set-up list parameters received in step 5, respectively. The CN tunnel information indicates the CN tunnel information as a user plane endpoint in the UPF 7201 and is transmitted to the gNB-CU-CP 6201 via the AMF 70. The CN tunnel information can indicate the user plane endpoint in the UPF 7201. Note that step 10 describes how the CN tunnel information is used by the gNB-CU-CP 6201 to establish a direct connection between the gNB-DU 61 and the UPF 7201.

[0105] 7. The AMF 70 sends an INITIAL CONTEXT SETUP REQUEST message containing the PDU session ID, CN tunnel information, gNB-CU-UP ID, gNB-CU-UP UE E1AP ID, and PDU session resource set-up list parameters to the gNB-CU-CP 6201. The gNB-CU-UP UE E1AP ID and PDU session resource set-up list parameters can be the same as the gNB-CU-UP UE E1AP ID and PDU session resource set-up list parameters received in step 6, respectively.

[0106] When receiving an INITIAL CONTEXT SETUP REQUEST message including the gNB-CU-UP ID, the gNB-CU-UP UE E1AP ID, and the PDU session resource set-up list parameters, the gNB-CU-CP 6201 finds the UPF 7201 as the gNB-CU-UP from the perspective of the gNB-CU-CP 6201 based on the received gNB-CU-UP ID within the INITIAL CONTEXT SETUP REQUEST message. The gNB-CU-CP 6201 can confirm whether the non-CU-UP support function is supported by the UPF 7201 by checking the "non-CU-UP support parameters" within the GNB-CU-CP E1 SETUP REQUEST message in step 0-1. If the non-CU-UP support function is not supported by the UPF 7201, the gNB-CU-CP 6201 finds an appropriate gNB-CU-UP and sends a BEARER CONTEXT SETUP REQUEST message to the found gNB-CU-UP without the gNB-CU-UP UE E1AP ID and the PDU session resource set-up list parameters to continue the PDU session establishment procedure without using the non-CU-UP support function. Otherwise (i.e., if the non-CU-UP support function is supported by the UPF 7201), the gNB-CU-UP 6201 sends a BEARER CONTEXT SETUP REQUEST message including the gNB-CU-UP UE E1AP ID and the PDU session resource set-up list parameters to the UPF 7201 as the gNB-CU-UP. The gNB-CU-UP UE E1AP ID and the PDU session resource set-up list parameters should be the same as the gNB-CU-UP UE E1AP ID and the PDU session resource set-up list parameters received in step 7, respectively.

[0107] 9. Based on the received gNB-CU-UP UE E1AP ID, UPF7201 links to the resources secured in step 5 and sends a BEARER CONTEXT SETUP RESPONSE message to gNB-CU-CP6201. For example, UPF7201 may link the received gNB-CU-UP UE E1AP ID to the resources secured in step 5.

[0108] 10. When receiving a BEARER CONTEXT SETUP RESPONSE message from UPF7201, gNB-CU-CP6201 contacts gNB-DU61 to set up the F1 UE context.

[0109] To set up the F1 UE context, gNB-CU-CP6201 sends a UE CONTEXT SETUP REQUEST message to gNB-DU61, including the UL configuration IE (UL Configuration IE) in the DRB to Be Setup Item IE (DRB to Be Setup Item IE) along with the information in the PDU session resource setup list parameter received in the INITIAL CONTEXT SETUP REQUEST message in step 7. Similarly, the UE CONTEXT SETUP REQUEST message includes the UP transport layer information IE (UP Transport Layer Information IE) in the DRB to Be Setup Item IE along with the information in the CN tunnel information received in the INITIAL CONTEXT SETUP REQUEST message in step 7. By this process or this procedure, the uplink user data is directly transferred from gNB-DU61 to UPF7201.

[0110] When receiving a UE CONTEXT SETUP REQUEST message, gNB-DU61 sends a UE CONTEXT SETUP RESPONSE message containing DL UP TNL information to the DL UP TNL Information to Be Setup Item IE (DL UP TNL Information to Be Setup Item IE) to gNB-CU-CP6201.

[0111] 11. gNB-CU-CP6201 sends an INITIAL CONTEXT SETUP RESPONSE message containing a DL QoS flow for each TNL information to the PDU Session Resource Setup Response Item IE (PDU Session Resource Setup Response Item IE) together with the DL UP TNL information received in the UE CONTEXT SETUP RESPONSE message in step 10 to AMF70. By this process or this procedure, the downlink user data is directly transferred from UPF7201 to gNB-DU61.

[0112] 12. The PDU session establishment procedure continues from step 15 of section 4.3.2.2.1 in Non-Patent Document 14.

[0113] <The First Variation of the Second Aspect: Service Request Procedure> The service request procedure for an NG-(R)AN architecture without gNB-CU-UP can be realized with the following changes to the second aspect.

[0114] - In step 1, the RRC message contains a service request message instead of a PDU session establishment request message.

[0115] - In step 2, the UPLINK NAS TRANSPORT message contains a service request message instead of a PDU session establishment request message.

[0116] - In step 3, the message name is the Nsmf_PDUSession_UpdateSMContext request instead of the Nsmf_PDUSession_CreateSMContext request. For example, the AMF 70 may send an Nsmf_PDUSession_UpdateSMContext request message instead of an Nsmf_PDUSession_CreateSMContext request message.

[0117] - In step 4, the message name is the Nsmf_PDUSession_UpdateSMContext response instead of the Nsmf_PDUSession_CreateSMContext response. For example, the SMF 7201 may send an Nsmf_PDUSession_UpdateSMContext response message instead of an Nsmf_PDUSession_CreateSMContext response message.

[0118] - In step 12, the subsequent procedure starts from step 15 of the UE trigger service request procedure in item 4.2.3.2 of Non-Patent Document 14.

[0119] <Second Modification of the Second Aspect: Optimized Service Flow> In one example, both step 8 and step 9 in FIG. 5 may be omitted.

[0120] This omission is possible when the PDU session resource set-up list and related information are secured by the UPF itself in step 5 and are notified to the gNB-CU-CP 6201 via the AMF 70 in steps 6 and 7.

[0121] <Third Modification of the Second Aspect: Handover between gNB-CU-CPs> If the gNB-CU-CP handover is triggered after step 12, the source gNB-CU-CP includes a per-PDU session indication indicating whether the no-gNB-CU-UP function is applied to the PDU session in the HANDOVER REQUEST message, and the target gNB-CU-CP can handle the PDU session with the no-gNB-CU-UP function controversially in the GNB-CU-CP E1 SETUP procedure according to the state of the function negotiation between the target gNB-CU-CP and the UPF.

[0122] At least one of the second aspect and the modification example of the second aspect proposes a solution that provides optimized user plane processing in 5GS.

[0123] For example, at least one of the second aspect and the modification example of the second aspect proposes a solution that improves the latency related to user data processing in 5GS.

[0124] For example, according to at least one of the second aspect and the modification example of the second aspect, since the total number of hardware involved in the end-to-end PDU session can be reduced, the failure of gNB-CU-UP due to hardware failure, virtual resource failure, and related equipment failure can be reduced.

[0125] For example, according to at least one of the second aspect and the modification example of the second aspect, since the N3 connection can be reduced, the service quality of the transport layer in 5GS can be improved.

[0126] For example, at least one of the second aspect and the modification example of the second aspect can solve the problem regarding the transmission delay that occurs every time user data crosses the user plane entity.

[0127] For example, at least one of the second aspect and the modification of the second aspect may solve the problem that the current 5GS architecture may be too redundant to meet the low latency requirements for time-critical applications.

[0128] <System Overview> FIG. 6 schematically shows a telecommunication system 1 for a mobile (cellular or wireless) device (known as a user equipment (UE)) to which the above aspect is applicable.

[0129] The telecommunication system 1 represents a system overview enabling end-to-end communication. For example, the UE 3 (or user equipment, "mobile device" 3) communicates with other UEs 3 or service servers within the data network 20 via respective (R)AN nodes 5 and the core network 7.

[0130] (R)AN node 5 supports any radio access, and the any radio access includes 5G radio access technology (RAT), E-UTRA radio access technology, Beyond 5G RAT, 6G RAT, and non-3GPP RAT including wireless local area network (WLAN) technology as defined by the Institute of Electrical and Electronics Engineers (IEEE).

[0131] (R)AN node 5 may be separated into a Radio Unit (RU), a Distributed Unit (DU), and a Centralized Unit (CU). In some aspects, each unit may be connected to each other by adopting an architecture as defined by the Open RAN (O-RAN) Alliance to construct the (R)AN node 5, and the above units are respectively referred to as O-RU, O-DU, and O-CU.

[0132] (R)AN node 5 can be separated into one or more control plane functions and one or more user plane functions. Further, multiple user plane functions can be allocated to support communications. In some aspects, user traffic may be distributed among multiple user plane functions, and the user traffic in each user plane function is aggregated at both UE3 and (R)AN node 5. This separation architecture may be referred to as "dual connectivity" or "multi-connectivity".

[0133] (R)AN node 5 can also support communications using satellite access. In some aspects, (R)AN node 5 can support satellite access and terrestrial access.

[0134] In addition, (R)AN node 5 can also be referred to as an access node for non-radio access. Non-radio access includes fixed network access as defined by the Broadband Forum (BBF) and optical access as defined by the Innovative Optical and Wireless Network (IOWN).

[0135] Core network 7 can include logical nodes (or "functions") that support communications in telecommunication system 1. For example, core network 7 can be a 5G Core Network (5GC) that includes, among other functions, control plane functions and user plane functions. Each function in a logical node can be regarded as a network function. The network functions can be provided to another node by adapting the Service Based Architecture (SBA).

[0136] A Network Function (NF) can be deployed as a distributed, redundant, stateless, and scalable entity that provides services from several locations and provides several execution instances at each location by applying network virtualization technologies as defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV).

[0137] Core network 7 can support a Non-Public Network (NPN). The NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0138] As is well known, when UE3 is moving around the perimeter of the geographical area covered by the telecommunications system 1, UE3 can enter and exit the area (i.e., the radio cell) served by (R)AN node 5. To maintain the tracking of UE3 and facilitate the handover between various (R)AN nodes 5, core network 7 comprises at least one access and mobility management function (AMF) 70. AMF 70 communicates with (R)AN node 5 connected to core network 7. In some core networks, a mobility management entity (MME) or a mobility management node for Beyond 5G, or a mobility management node for 6G can be used instead of AMF 70.

[0139] The core network 7 also includes, in particular, a Session Management Function (SMF) 71, a User Plane Function (UPF) 72, a Policy Control Function (PCF) 73, a Network Exposure Function (NEF) 74, a Unified Data Management (UDM) 75, and a Network Data Analytics Function (NWDAF) 76. When the UE 3 roams to a visited Public Land Mobile Network (VPLMN), the home Public Land Mobile Network (HPLMN) of the UE 3 provides the UDM 75 and at least a part of the functions of the SMF 71, the UPF 72, and the PCF 73 to the roaming-out UE 3.

[0140] UE3 and each serving (R)AN node 5 are connected via an appropriate air interface (e.g., the so-called "Uu" interface and / or the like). Adjacent (R)AN nodes 5 are connected to each other via an appropriate (R)AN node 5 for an (R)AN node interface (such as the so-called "Xn" interface and / or the like). Each (R)AN node 5 is also connected to a node in the core network 7 (such as a so-called core network node) via an appropriate interface (such as the so-called "N2" / "N3" interface and / or the like). A connection to the data network 20 is also provided from the core network 7. The data network 20 can be the Internet, a public network, an external network, a private network, or an internal network of a PLMN. When the data network 20 is provided by a PLMN operator or a Mobile Virtual Network Operator (MVNO), IP Multimedia Subsystem (IMS) services can be provided by that data network 20. UE3 can be connected to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet, or an unstructured data type.

[0141] The "Uu" interface can include a control plane and a user plane.

[0142] The user plane of the Uu interface is responsible for transmitting user traffic between UE3 and the serving (R)AN node 5. The user plane of the Uu interface can have a hierarchical structure with SDAP, PDCP, RLC, and MAC sublayers by means of a physical connection.

[0143] The control plane of the Uu interface is responsible for establishing, modifying, and releasing the connection between UE3 and the serving (R)AN node 5. The control plane of the Uu interface may have a hierarchical structure with RRC, PDCP, RLC, and MAC sublayers by means of a physical connection.

[0144] For example, the following messages are communicated in the RRC layer to support AS signaling.

[0145] - RRC setup request message: This message is sent from UE3 to the (R)AN node 5. In addition to the parameters disclosed by some aspects of the present disclosure, any of the following parameters may be included together in the RRC setup request message. -- establishmentCause and ue-Identity. The ue-Identity may have a value of ng-5G-S-TMSI-Part1 or a randomValue.

[0146] - RRC setup message: This message is sent from the (R)AN node 5 to UE3. In addition to the parameters disclosed by some aspects of the present disclosure, any of the following parameters may be included together in the RRC setup message. -- masterCellGroup and radioBearerConfig

[0147] - RRC setup complete message: This message is sent from UE3 to the (R)AN node 5. In addition to the parameters disclosed by some aspects of the present disclosure, any of the following parameters may be included together in the RRC setup complete message. --guami type, iab-NodeIndication, idleMeasAvailable, mobilityState, ng-5G-S-TMSI - Part 2, registeredAMF, selectedPLMN-Identity

[0148] UE3 and AMF70 are connected via an appropriate interface (e.g., the so-called N1 interface and / or the like). The N1 interface plays a role of providing communication between UE3 and AMF70 to support NAS signaling. The N1 interface can be established in 3GPP access and non-3GPP access. For example, the following messages are communicated in the N1 interface.

[0149] - Registration request message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed by some aspects of the present disclosure, any of the following parameters may be included together in the registration request message. --5GS registration type, ngKSI, 5GS mobile identity, Non-current native NAS key set identifier, 5GMM capability, UE security capability, Requested NSSAI, Last visited registered TAI, S1 UE network capability, Uplink data status, PDU session status, MICO indication, UE status, Additional GUTI, Allowed PDU session status, UE’s usage setting, Requested DRX parameters, EPS NAS message container, LADN indication, Payload container type, Payload container, Network slicing indication, 5GS update type, Mobile station classmark 2, Supported codecs, NAS message container, EPS bearer context status, Requested extended DRX parameters, T3324 value, UE radio capabilityID), Requested mapped NSSAI, Additional information requested, Requested WUS assistance information, N5GC indication, and Requested NB-N1 mode DRX parameters.

[0150] - Registration approval message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by some aspects of the present disclosure, any of the following parameters may be included together in the registration approval message. --5GS registration result, 5G-GUTI, Equivalent PLMNs, TAI list, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS network feature support, PDU session status, PDU session reactivation result, PDU session reactivation result error cause, LADN information, MICO indication, Network slicing indication, Service area list, T3512 value, Non-3GPP de-registration timer value, T3502 value, Emergency number list, Extended emergency number list, SOR transparent container, EAP message, NSSAI inclusion mode, Operator-defined access category definitions, Negotiated DRX parameters, Non-3GPP NW policies, EPS bearer context status, Negotiated extended DRX parameters, T3447 value, T3448 value, T3448value), T3324 value, UE radio capability ID, UE radio capability ID deletion indication, Pending NSSAI, Ciphering key data, CAG information list, Truncated 5G-S-TMSI configuration, Negotiated WUS assistance information, Negotiated NB-N1 mode DRX parameters, and Extended rejected NSSAI.

[0151] - Registration complete message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed by some aspects of the present disclosure, the following parameters may be included together in the registration complete message. -- SOR transparent container.

[0152] - Authentication request message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed by some aspects of the present disclosure, any of the following parameters may be included together in the authentication request message. -- ngKSI, ABBA, Authentication parameter RAND (5G authentication challenge), Authentication parameter AUTN (5G authentication challenge), and EAP message.

[0153] - Authentication response message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed by some aspects of the present disclosure, any of the following parameters may coexist within the authentication response message. -- Authentication response message identity, Authentication response parameter, and EAP message.

[0154] - Authentication result message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed by some aspects of the present disclosure, any of the following parameters may coexist within the authentication result message. -- ngKSI, EAP message, and ABBA.

[0155] - Authentication failure message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed by some aspects of the present disclosure, any of the following parameters may coexist within the authentication failure message. -- Authentication failure message identity, 5GMM cause, and Authentication failure parameter.

[0156] - Authentication rejection message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed by some aspects of the present disclosure, the following parameters may coexist within the authentication rejection message. -- EAP message.

[0157] - Service request message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed by some aspects of the present disclosure, any of the following parameters may coexist within the service request message. -- ngKSI, Service type, 5G-S-TMSI, Uplink data status, PDU session status, Allowed PDU session status, NAS message container.

[0158] - Service approval message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed by some aspects of the present disclosure, any of the following parameters may coexist within the service approval message. -- PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message, and T3448 value.

[0159] - Service rejection message: This message is sent from AMF70 to UE3. In addition to the parameters disclosed by some aspects of the present disclosure, any of the following parameters may coexist within the service rejection message. -- 5GMM cause, PDU session status, T3346 value, EAP message, T3448 value, and CAG information list.

[0160] - Configuration update command message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters disclosed by some aspects of the present disclosure, any of the following parameters may coexist within the configuration update command message. -- Configuration update indication, 5G-GUTI, TAI list, Allowed NSSAI, Service area list, Full name for network, Short name for network, Local time zone, Universal time and local time zone, Network daylight saving time, LADN information, MICO indication, Network slicing indication, Configured NSSAI, Rejected NSSAI, Operator-defined access category definitions, SMS indication, T3447 value, CAG information list, UE radio capability ID, UE radio capability ID deletion indication, 5GS registration result, Truncated 5G-S-TMSI configuration, Additional configuration indication, and Extended rejected NSSAI.

[0161] - Configuration update complete message: This message is sent from UE3 to AMF70. In addition to the parameters disclosed by some aspects of the present disclosure, the following parameters may coexist within the configuration update complete message. -- Configuration update complete message identity.

[0162] <User equipment (UE)> FIG. 7 is a block diagram showing the main components of UE3 (Mobile Device 3). As shown, UE3 includes a transceiver circuit 31, which is operable to transmit signals to and receive signals from a connection node via one or more antennas 32. Further, UE3 may include a user interface 34 for inputting information from the outside or outputting information to the outside. Although not necessarily shown in the figure, UE3 may have all the normal functions of a conventional mobile device, which may be provided by any one or any combination of hardware, software, and firmware as needed. For example, the software may be pre-installed in the memory and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The controller 33 controls the operation of UE3 according to the software stored in the memory 36. The software particularly includes an operating system 361 and a communication control module 362 having at least a transceiver control module 3621. The communication control module 362 (using its transceiver control module 3621) is responsible for processing (generating / sending / receiving) signaling and uplink / downlink data packets between UE3 and other nodes such as (R)AN node 5 and AMF 10. Such signaling may include, for example, appropriately formatted signaling messages (e.g., registration request messages and associated response messages) regarding access and mobility management procedures (for UE3). The controller 33 interacts with one or more Universal Subscriber Identity Modules (USIMs) 35. When multiple USIMs 35 are provided, the controller 33 may activate only one USIM 35 or may activate multiple USIMs 35 simultaneously.

[0163] UE3 may support, for example, a Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0164] UE3 may be, for example, an item of equipment for production or manufacturing, and / or an item of energy-related machinery (e.g., boilers, engines, turbines, solar panels, wind turbines, hydroelectric generators, thermal power generators, nuclear power generators, batteries, nuclear systems and / or related equipment, heavy electrical machinery, pumps including vacuum pumps, compressors, fans, blowers, hydraulic equipment, pneumatic equipment, metalworking machinery, manipulators, robots and / or their application systems, tools, molds or dies, rolls, conveying equipment, lifting equipment, material handling equipment, textile machinery, sewing machinery, printing machinery and / or related machinery, paper industry machinery, chemical machinery, mining machinery and / or construction machinery and / or related equipment, machinery and / or implements for agriculture, forestry, and / or fishery, safety and / or environmental protection equipment, tractors, precision bearings, chains, gears, power transmission equipment, lubrication equipment, valves, pipe fittings, and / or application systems for any of the aforementioned equipment or machinery).

[0165] UE3 may be, for example, an item of transportation equipment (e.g., vehicles, automobiles, motorcycles, bicycles, trains, buses, trucks, rickshaws, ships and other vessels, aircraft, rockets, satellites, drones, balloons, etc.).

[0166] UE3 may be, for example, an item of information and communication equipment (e.g., electronic computers and related equipment, communication and related equipment, information and communication equipment such as electronic components).

[0167] UE3 can be, for example, a refrigeration machine, a refrigeration machine application product, an item of equipment for commercial and / or service industries, a vending machine, an automatic service machine, an office machine or equipment, a consumer electronic device and an electrical appliance (for example, a consumer electronic appliance such as an audio device, a video device, a loudspeaker, a radio, a television, a microwave oven, a rice cooker, a coffee machine, a dishwasher, a washing machine, a dryer, an electric fan or a related appliance, a vacuum cleaner, etc.).

[0168] UE3 can be, for example, an electrical application system or equipment (for example, an electrical application system or equipment such as an x-ray system, a particle accelerator, a radioisotope equipment, a sonic equipment, an electromagnetic application equipment, an electric power application equipment, etc.).

[0169] UE3 can be, for example, an electronic lamp, a lighting fixture, a measuring instrument, an analyzer, a testing machine, or a surveying or detecting device (for example, a surveying or detecting device such as a smoke alarm, a human alarm sensor, a motion sensor, a wireless tag, etc.), a wristwatch or a wall clock, a laboratory equipment, an optical device, a medical device and / or system, a weapon, an item of cutlery, a hand tool, or the like.

[0170] UE3 can be, for example, a wireless equipped personal digital assistant or a related device (such as a wireless card or module designed to be attached to or inserted into another electronic device (for example, a personal computer, an electrical measuring machine)).

[0171] UE3 can be part of a device or system that uses various wired and / or wireless communication technologies to provide the applications, services, and solutions described below with respect to the "internet of things (IoT)".

[0172] An Internet of Things device (or "thing") may comprise suitable electronic devices, software, sensors, network connectivity, and / or the like, whereby the device can collect and exchange data with each other and with other communication devices. An IoT device may comprise automated devices that follow software instructions stored in internal memory. An IoT device can operate without the need for human supervision or interaction. An IoT device can also remain stationary and / or powered off for long periods of time. An IoT device can be implemented as part of a (generally) fixed installation. An IoT device can also be incorporated into a non-fixed device (e.g., a vehicle) or attached to an animal or person being monitored / tracked.

[0173] It will be understood that IoT technology can be implemented on any communication device that can connect to a communication network to send / receive data, regardless of whether such communication device is controlled by human input or by software instructions stored in memory.

[0174] It will be understood that IoT devices are sometimes also referred to as Machine-Type Communication (MTC) devices or Machine-to-Machine (M2M) communication devices, or Narrow Band-IoT UEs (NB-IoT UEs). It will be understood that UE3 can support one or more IoT or MTC applications.

[0175] UE3 can be a smartphone or a wearable device (e.g., smart glasses, smartwatch, smart ring, or hearable device).

[0176] UE3 can be a vehicle, a connected car, a self-driving car, a vehicle device, a motorcycle, or a Vehicle to Everything (V2X) communication module (e.g., a vehicle-to-vehicle communication module, a vehicle-to-infrastructure communication module, a vehicle-to-person communication module, and a vehicle-to-network communication module).

[0177] <(R)AN node> FIG. 8 is a block diagram showing the main components of an exemplary (R)AN node 5, e.g., a base station (an "eNB" in LTE, a "gNB" in 5G, a base station for Beyond 5G, a base station for 6G). As shown, the (R)AN node 5 includes a transceiver circuit 51, which is operable to transmit signals to and receive signals from a connected UE3 via one or more antennas 52, and to transmit signals to and receive signals from other network nodes (directly or indirectly) via a network interface 53. A controller 54 controls the operation of the (R)AN node 5 according to software stored in a memory 55. For example, the software may be pre-installed in the memory and / or downloaded via a telecommunications network or from a removable data storage device (e.g., an RMD).

[0178] The software particularly includes an operating system 551 and a communication control module 552 having at least a transceiver control module 5521.

[0179] The communication control module 552 (using its transceiver control sub-module) is responsible for processing (generating / sending / receiving) signaling between the (R)AN node 5 and other nodes such as the UE 3, another (R)AN node 5, the AMF 70, and the UPF 72, either directly or indirectly. The signaling may include, for example, properly formatted signaling messages (such as RRC connection establishment and other RRC messages), NG application protocol (NGAP) messages (i.e., messages at the N2 reference point), Xn application protocol (XnAP) messages (i.e., messages at the Xn reference point), etc., regarding the radio connection and connection to the core network 7 for a specific UE 3, particularly regarding connection establishment and maintenance. Such signaling may also include, in the case of transmission, for example, broadcast information (such as master information and system information).

[0180] The controller 54 is also configured (by software or hardware) to process related tasks such as UE mobility estimation and / or movement trajectory estimation when implemented.

[0181] (R)AN node 5 may support a Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0182] <System Overview of (R)AN Node 5 Based on the O-RAN Architecture> Figure 9 schematically shows (R)AN node 5 based on the O-RAN architecture to which the (R)AN node 5 aspect is applicable.

[0183] The (R)AN node 5 based on the O-RAN architecture represents a system overview in which the (R)AN node is separated into a Radio Unit (RU) 60, a Distributed Unit (DU) 61, and a Centralized Unit (CU) 62. The centralized unit may be called the central part. In some aspects, the various parts may be combined. For example, the RU 60 may be integrated / connected to the DU 61 as an integration / connection part, and the DU 61 may be integrated / connected to the CU 62 as another integration / connection part. Any function described for a particular part (e.g., one of the RU 60, DU 61, and CU 62) may be implemented in the above integration / connection part. Further, the CU 62 may be separated into two functional parts such as a CU-Control plane (CU-CP) and a CU-User plane (CU-UP). The CU-CP has control plane functions in the (R)AN node 5. The CU-UP has user plane functions in the (R)AN node 5. Each CU-CP is connected to the CU-UP via an appropriate interface (such as the so-called "E1" interface and / or the like).

[0184] UE3 and each serving RU60 are connected via an appropriate air interface (e.g., the so-called "Uu" interface and / or the like). Each RU60 is connected to the DU61 via an appropriate interface (such as the so-called "front haul", "open front haul", "F1" interface, and / or the like). Each DU61 is connected to the CU62 via an appropriate interface (such as the so-called "mid haul", "open mid haul", "E2" interface, and / or the like). Each CU62 is also connected to a node within the core network 7 (such as a so-called core network node) via an appropriate interface (such as the so-called "back haul", "open back haul", "N2" / "N3" interface, and / or the like). In addition, the user plane part of the DU61 may also be connected to the core network node 7 via an appropriate interface (such as the so-called "N3" interface and / or the like).

[0185] According to the functions separated among the RU60, DU61, and CU62, each part provides a part of the functions provided by the (R)AN node 5. For example, the RU60 may provide the function of communicating with the UE3 at the air interface, the DU61 may provide the function of supporting the MAC layer and the RLC layer, and the CU62 may provide the function of supporting the PDCP layer, the SDAP layer, and the RRC layer.

[0186] <Radio Unit (RU)> FIG. 10 is a block diagram showing the main components of the RU part of an exemplary RU60, for example, a base station (an "eNB" in LTE, a "gNB" in 5G, a base station for Beyond 5G, a base station for 6G). As shown, the RU60 includes a transceiver circuit 601, which is operable to transmit signals to and receive signals from a connected UE3 via one or more antennas 602, and to transmit signals to and receive signals from other network nodes or network parts (directly or indirectly) via a network interface 603. A controller 604 controls the operation of the RU60 according to software stored in a memory 605. For example, the software may be pre-installed in the memory and / or may be downloaded via a telecommunication network or from a removable data storage device (e.g., a removable memory device (RMD)). The software particularly includes an operating system 6051 and a communication control module 6052 having at least a transceiver control module 60521.

[0187] The communication control module 6052 (using its transceiver control sub-module) is responsible for processing (generating / sending / receiving) signaling between the RU60 and other nodes or parts such as the UE3, another RU60, and the DU61 (e.g., directly or indirectly). The signaling may include, for example, properly formatted signaling messages related to the radio connection and connection with the RU60 (for a specific UE3), particularly related to the MAC layer and the RLC layer.

[0188] The controller 604 is also configured (by software or hardware) to process related tasks such as UE mobility estimation and / or movement trajectory estimation when implemented.

[0189] RU60 can support a Non-Public Network (NPN). The NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0190] As described above, RU60 can be integrated / connected to DU61 as an integration / connection part. Any function in the description of RU60 can be implemented in the above integration / connection part.

[0191] <Distributed Unit (DU)> FIG. 11 is a block diagram showing the main components of an exemplary DU61, for example, the DU part of a base station (such as "eNB" in LTE, "gNB" in 5G, a base station for Beyond 5G, a base station for 6G). As shown, the apparatus includes a transceiver circuit 611, and the transceiver circuit 611 is operable to transmit signals to and receive signals from other nodes or parts (including RU60) via a network interface 612. A controller 613 controls the operation of DU61 according to software stored in a memory 614. For example, the software may be pre-installed in the memory 614 and / or downloaded via a telecommunications network or from a removable data storage device (such as a removable memory device (RMD)). The software includes, in particular, an operating system 6141 and a communication control module 6142 having at least a transceiver control module 61421. The communication control module 6142 (using its transceiver control module 61421) is responsible for processing (generating / sending / receiving) signaling between DU61 and other nodes or parts such as RU60 and other nodes or parts.

[0192] DU61 can support a Non-Public Network (NPN). The NPN can be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0193] As described above, DU61 can be integrated / connected to RU60 or CU62 as an integration / connection unit. Any function in the description of DU61 can be implemented in one of the above integration / connection units.

[0194] gNB-DU can have the same components as DU61.

[0195] <Centralized Unit / Central Unit (CU)> FIG. 12 is a block diagram showing the main components of an exemplary CU62, e.g., the CU part of a base station (such as an "eNB" in LTE, a "gNB" in 5G, a base station for Beyond 5G, a base station for 6G). As shown, the apparatus includes a transceiver circuit 621, which is operable to transmit signals to and receive signals from other nodes or parts (including DU61) via a network interface 622. A controller 623 controls the operation of CU62 according to software stored in a memory 624. For example, the software may be pre-installed in the memory 624 and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software particularly includes an operating system 6241 and a communication control module 6242 having at least a transceiver control module 62421. The communication control module 6242 (using its transceiver control module 62421) is responsible for processing (generating / sending / receiving) signaling between CU62 and other nodes or parts such as DU61 and other nodes or parts.

[0196] CU62 may support a Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0197] As described above, CU62 may be integrated / connected to DU61 as an integration / connection part. Any function in the description of CU62 may be implemented in the above integration / connection part.

[0198] gNB-CU-CP may have the same components as CU62.

[0199] The gNB-CU-UP may have the same components as CU62.

[0200] <amf> Figure 13 is a block diagram showing the main components of the AMF 70. As shown, the apparatus includes a transceiver circuit 701, which is operable to transmit signals to and receive signals from other nodes (including UE3) via a network interface 702. A controller 703 controls the operation of the AMF 70 according to software stored in a memory 704. For example, the software may be pre-installed in the memory 704 and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, in particular, an operating system 7041 and a communication control module 7042 having at least a transceiver control module 70421. The communication control module 7042 (using its transceiver control module 70421) is responsible for processing (generating / sending / receiving) signaling between the AMF 70 and other nodes, such as UE3 (e.g., via an (R)AN node 5) and other core network nodes including core network nodes in the HPLMN of UE3 when UE3 is roaming in. Such signaling may include, for example, appropriately formatted signaling messages (e.g., registration request messages and associated response messages) related to access and mobility management procedures (for UE3).

[0201] The AMF 70 may support a Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0202] <smf> Figure 14 is a block diagram showing the main components of SMF71. As shown, the apparatus includes a transceiver circuit 711, which is operable to transmit signals to and receive signals from other nodes (including AMF70) via a network interface 712. A controller 713 controls the operation of SMF71 according to software stored in a memory 714. For example, the software may be pre-installed in the memory 714 and / or downloaded via a telecommunications network or from a removable memory device (RMD). The software particularly includes an operating system 7141 and a communication control module 7142 having at least a transceiver control module 71421. The communication control module 7142 (using its transceiver control module 71421) is responsible for processing (generating / sending / receiving) signaling between SMF71 and other nodes such as UPF72 and other core network nodes including core network nodes in the HPLMN of UE3 when UE3 is roaming in. Such signaling may include, for example, appropriately formatted signaling messages (e.g., Hypertext Transfer Protocol (HTTP) RESTful methods based on a service-based interface) related to session management procedures (for UE3).

[0203] SMF71 may support a Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0204] <upf> FIG. 15 is a block diagram showing the main components of UPF72. As shown, the apparatus includes a transceiver circuit 721, which is operable to transmit signals to and receive signals from other nodes (including SMF71) via a network interface 722. A controller 723 controls the operation of UPF72 according to software stored in a memory 724. For example, the software may be pre-installed in the memory 724 and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software particularly includes an operating system 7241 and a communication control module 7242 having at least a transceiver control module 72421. The communication control module 7242 (using its transceiver control module 72421) is responsible for processing (generating / sending / receiving) signaling between UPF72 and other nodes such as SMF71 and other core network nodes including core network nodes in the HPLMN of UE3 when UE3 is roaming in. Such signaling may include, for example, appropriately formatted signaling messages (e.g., GPRS Tunneling Protocol (GTP) for the user plane) regarding user data processing for (UE3).

[0205] UPF72 may support a Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0206] A co-located gNB-CU-UP and UPF, or a communication device that executes the functions of a co-located gNB-CU-UP and UPF, or a communication device that executes the functions of a gNB-CU-UP and a UPF may have the same components as the UPF 72.

[0207] <pcf> FIG. 16 is a block diagram showing the main components of the PCF 73. As shown, the apparatus includes a transceiver circuit 731, which is operable to transmit signals to and receive signals from other nodes (including the AMF 70) via a network interface 732. A controller 733 controls the operation of the PCF 73 according to software stored in a memory 734. For example, the software may be pre-installed in the memory 734 and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, in particular, an operating system 7341 and a communication control module 7342 having at least a transceiver control module 73421. The communication control module 7342 (using its transceiver control module 73421) is responsible for processing (generating / sending / receiving) signaling between the PCF 73 and other nodes such as the AMF 70 and other core network nodes including the core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming in. Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on a service-based interface) regarding policy management procedures (for the UE 3).

[0208] The PCF 73 may support a Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0209] <nef> Figure 17 is a block diagram showing the main components of NEF74. As shown, the apparatus includes a transceiver circuit 741, which is operable to transmit signals to and receive signals from other nodes (including UDM75) via a network interface 742. A controller 743 controls the operation of NEF74 according to software stored in a memory 744. For example, the software may be pre-installed in the memory 744 and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, in particular, an operating system 7441 and a communication control module 7442 having at least a transceiver control module 74421. The communication control module 7442 (using its transceiver control module 74421) is responsible for processing (generating / sending / receiving) signaling between NEF74 and other nodes such as UDM75 and other core network nodes including core network nodes in the HPLMN of UE3 when UE3 is roaming in. Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on a service-based interface) regarding network exposure capabilities procedures (for UE3).

[0210] NEF74 may support a Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0211] <udm> Figure 18 is a block diagram showing the main components of the UDM75. As shown, the apparatus includes a transceiver circuit 751, which is operable to transmit signals to and receive signals from other nodes (including the AMF70) via a network interface 752. A controller 753 controls the operation of the UDM75 according to software stored in a memory 754. For example, the software may be pre-installed in the memory 754 and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, in particular, an operating system 7541 and a communication control module 7542 having at least a transceiver control module 75421. The communication control module 7542 (using its transceiver control module 75421) is responsible for processing (generating / sending / receiving) signaling between the UDM75 and other nodes such as the AMF70 and other core network nodes including the core network nodes in the VPLMN of the UE3 when the UE3 is roaming out. Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on a service-based interface) regarding mobility management procedures (for the UE3).

[0212] The UDM75 may support a Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0213] <nedaf> Figure 19 is a block diagram showing the main components of NWDAF 76. As shown, the apparatus includes a transceiver circuit 761, which is operable to transmit signals to and receive signals from other nodes (including AMF 70) via a network interface 762. A controller 763 controls the operation of NWDAF 76 according to software stored in a memory 764. For example, the software may be pre-installed in the memory 764 and / or downloaded via a telecommunications network or from a removable data storage device (e.g., a removable memory device (RMD)). The software includes, in particular, an operating system 7641 and a communication control module 7642 having at least a transceiver control module 76421. The communication control module 7642 (using its transceiver control module 76421) is responsible for processing (generating / sending / receiving) signaling between NWDAF 76 and other nodes such as AMF 70 and other core network nodes including core network nodes in the HPLMN of UE3 when UE3 is roaming in. Such signaling may include, for example, appropriately formatted signaling messages (e.g., HTTP RESTful methods based on a service-based interface) regarding network data analytics capabilities procedures (for UE3).

[0214] NWDAF 76 may support a Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0215] <Revisions and Alternatives> Detailed aspects have been described above. Still, those skilled in the art will understand that numerous modifications and alternatives can be made to the above aspects while receiving the benefits of the present disclosure embodied herein. By way of mere example, numerous such alternatives and modifications are described herein.

[0216] In the above description, the UE3 and the network device are described as having a number of separate modules (such as a communication control module) to facilitate understanding. Thus, these modules can be provided, for example, for specific applications where an existing system is modified to implement the present disclosure, or in other applications, for example, in a system designed from the start considering the features of the invention. However, since these modules may be built into the overall operating system or code, these modules may not need to be recognized as separate entities. These modules can also be implemented in software, hardware, firmware, or a combination thereof.

[0217] Each controller may comprise a processing circuit in any suitable form, for example, one or more hardware-implemented computer processors, microprocessors, central processing units (CPUs), arithmetic logic units (ALUs), input / output (IO) circuits, internal memory / cache (program and / or data), processing registers, communication buses (e.g., control bus, data bus, and / or address bus), direct memory access (DMA) functionality, hardware or software-implemented counters, pointers and / or timers, and / or the like (but not limited to these).

[0218] In the above aspect, a number of software modules were described. Those skilled in the art will understand that the software modules may be provided in a compiled form or a non-compiled form, and may be supplied to the UE3 and the network device as signals in a computer network or on a recording medium. Furthermore, the functions performed by some or all of the software may be performed using one or more dedicated hardware circuits. However, software modules are preferably used to update the functions of the UE3 and the network device in order to facilitate the update of the UE3 and the network device.

[0219] In the above aspect, 3GPP wireless communication (radio access) technology is used. However, any other wireless communication technology (e.g., WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fixed-line communication technologies (e.g., BBF access, cable access, optical access, etc.) may also be used according to the above aspect.

[0220] Items of user equipment may include communication devices such as, for example, mobile phones, smartphones, user equipment, personal digital assistants, laptop / tablet computers, web browsers, e-book readers, and / or the like. Such mobile (and generally fixed) devices are usually operated by a user, but it is also possible to connect so-called "Internet of Things" (IoT) devices and similar machine-type communication (MTC) devices to the network. For the sake of simplicity, this application refers to mobile devices (or UEs) in the description, but it will be understood that the technology described can be implemented on any (mobile and / or generally fixed) communication device that can be connected to a communication network for transmitting / receiving data, regardless of whether such a communication device is controlled by human input or by software instructions stored in memory.

[0221] Various other modifications will be apparent to those skilled in the art and are not described in further detail herein.

[0222] The present disclosure has been illustrated and described in detail with reference to exemplary aspects of the present disclosure, but the present disclosure is not limited to such aspects. It will be understood by those skilled in the art that various changes in form and detail may be made without departing from the spirit and scope of the present disclosure as defined by this specification. For example, the above aspects are not limited to 5GS, and the aspects are also applicable to communication systems other than 5GS (e.g., 6G systems, Beyond 5G systems).

[0223] All or part of the exemplary aspects of the above disclosure may be described as follows, but are not limited to the following appendices.

[0224] Appendix 1. A method of a communication device, the method comprising: performing functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and functions of a User Plane Function (UPF) device; communicating with a gNB Distributed Unit (gNB-DU) device; communicating with a gNB Centralized Unit-Control Plane (gNB-CU-CP) device; A method comprising.

[0225] Appendix 2. A method of a gNB Centralized Unit-Control Plane (gNB-CU-CP) device, the method comprising: receiving a Protocol Data Unit (PDU) session establishment request message from a User Equipment (UE); To send an uplink NAS transport message to an Access and Mobility management Function (AMF) device, wherein the uplink NAS transport message includes the PDU session establishment request message and information indicating that the gNB-CU-CP device supports communication with a communication device that executes functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and a User Plain Function (UPF) device, To receive an Initial Context Setup Request message from the AMF device, wherein the Initial Context Setup Request message includes information about the gNB-CU-UP, To select the gNB-CU-UP based on the information about the gNB-CU-UP, To perform a PDU session establishment procedure for the UE, A method comprising the above steps.

[0226] Appendix 3. A method for an Access and Mobility management Function (AMF) device, the method comprising: Receiving an uplink NAS transport message from a gNB Centralized Unit Control Plane (gNB-CU-CP) device, The UPLINK NAS TRANSPORT message includes a Protocol Data Unit (PDU) session establishment request message and information indicating that the gNB-CU-CP device supports communication with a communication device that executes the functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and a User Plain Function (UPF) device. Transmitting an Nsmf_PDUSession_CreateSMContext request message to a Session Management Function (SMF) device, wherein the Nsmf_PDUSession_CreateSMContext request message includes the information. Receiving an Nsmf_PDUSession_CreateSMContext response message from the SMF device, wherein the Nsmf_PDUSession_CreateSMContext response message includes information about the UPF device. Receiving a Namf_Communication_N1N2MessageTransfer message from the SMF device, wherein the Namf_Communication_N1N2MessageTransfer message includes information about the gNB-CU-UP device. Transmitting an INITIAL CONTEXT SETUP REQUEST message to the gNB-CU-CP device, wherein the INITIAL CONTEXT SETUP REQUEST message includes the information about the gNB-CU-UP device. Performing a PDU session establishment procedure, A method including the above.

[0227] Appendix 4. A method for a Session Management Function (SMF) device, the method comprising: Receiving an Nsmf_PDUSession_CreateSMContext request message from an Access and Mobility management Function (AMF) device, wherein the Nsmf_PDUSession_CreateSMContext request message includes information indicating that a gNB Centralized Unit Control Plane (gNB-CU-CP) device supports communication with a communication device that executes functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and a User Plain Function (UPF) device; Sending an Nsmf_PDUSession_CreateSMContext response message to the AMF device, wherein the Nsmf_PDUSession_CreateSMContext response message includes information about the UPF device; Selecting the UPF device when the Nsmf_PDUSession_CreateSMContext request message includes the information; Contacting the communication device to allocate resources for user data processing; Sending a Namf_Communication_N1N2MessageTransfer message to the AMF device, wherein the Namf_Communication_N1N2MessageTransfer message includes information about the gNB-CU-UP device; Performing a PDU session establishment procedure; and the method includes the above steps.

[0228] A method of a gNB Distributed Unit (gNB-DU) device, the method comprising: communicating with a gNB Centralized Unit-Control Plane (gNB-CU-CP) device; communicating with a User Plane Function (UPF) device without a gNB Centralized Unit User Plane (gNB-CU-UP) device; A method comprising the above.

[0229] A method of a gNB Centralized Unit-Control Plane (gNB-CU-CP) device, the method comprising: communicating with a gNB Distributed Unit (gNB-DU) device; communicating with a User Plane Function (UPF) device without a gNB Centralized Unit User Plane (gNB-CU-UP) device; A method comprising the above.

[0230] Receiving a GNB-CU-CP E1 SETUP REQUEST message from the UPF device, wherein the GNB-CU-CP E1 SETUP REQUEST message includes first information indicating that the UPF device supports the connection of the gNB-DU device to the UPF device without the gNB-CU-UP device; Sending a GNB-CU-CP E1 SETUP RESPONSE message to the UPF device, The GNB-CU-CP E1 SETUP RESPONSE message includes second information indicating that the gNB-CU-CP device supports the connection of the gNB-DU device to the UPF device without the gNB-CU-UP device. Receiving a Protocol Data Unit (PDU) session establishment request message from a User Equipment (UE). Transmitting an UPLINK NAS TRANSPORT message to an Access and Mobility management Function (AMF) device, wherein the UPLINK NAS TRANSPORT message includes the second information. Receiving an INITIAL CONTEXT SETUP REQUEST message from the AMF device, wherein the INITIAL CONTEXT SETUP REQUEST message includes a gNB-CU-UP UE E1AP ID and third information indicating a pair of an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID) for uplink data processing. Transmitting a UE CONTEXT SETUP REQUEST message to the gNB-DU device, wherein the UE CONTEXT SETUP REQUEST message includes the third information and a UL configuration Information Element (IE). Receiving a UE CONTEXT SETUP RESPONSE message from the gNB-DU device. Transmitting an INITIAL CONTEXT SETUP RESPONSE message to the AMF device, Performing a PDU session establishment procedure, The method according to Appendix 6, further comprising.

[0231] Appendix 8. A method for an Access and Mobility management Function (AMF) device, the method comprising: Receiving an UPLINK NAS TRANSPORT message from a gNB Centralized Unit Control Plane (gNB-CU-CP) device, The UPLINK NAS TRANSPORT message includes first information indicating that the gNB-CU-CP device supports the gNB Distributed Unit (gNB-DU) device to connect to a User Plane Function (UPF) device without a gNB Centralized Unit User Plane (gNB-CU-UP) device, Transmitting an Nsmf_PDUSession_CreateSMContext request message to a Session Management Function (SMF) device, The Nsmf_PDUSession_CreateSMContext request message includes the first information, Receiving an Nsmf_PDUSession_CreateSMContext response message from the SMF device, The Nsmf_PDUSession_CreateSMContext response message includes second information indicating that the UPF device supports the gNB-DU device connecting to the UPF device without the gNB-CU-UP device, Receiving a Namf_Communication_N1N2MessageTransfer message from the SMF device, The Namf_Communication_N1N2MessageTransfer message includes a gNB-CU-UP UE E1AP ID and third information indicating a pair of an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID) for uplink data processing, Sending an INITIAL CONTEXT SETUP REQUEST message to the gNB-CU-CP device, The INITIAL CONTEXT SETUP REQUEST message includes the gNB-CU-UP UE E1AP ID and the third information, Receiving an INITIAL CONTEXT SETUP RESPONSE message from the gNB-CU-CP device, Performing a PDU session establishment procedure, A method including.

[0232] Appendix 9. A method of a Session Management Function (SMF) device, the method comprising: Receiving an Nsmf_PDUSession_CreateSMContext request message from an Access and Mobility management Function (AMF) device, The Nsmf_PDUSession_CreateSMContext request message includes first information indicating that the gNB Distributed Unit (gNB-DU) device supports connecting to a User Plane Function (UPF) device without a gNB Centralized Unit User Plane (gNB-CU-UP) device, and transmitting an Nsmf_PDUSession_CreateSMContext response message to the AMF device, wherein the Nsmf_PDUSession_CreateSMContext response message includes second information indicating that the UPF device supports the gNB-DU device connecting to the UPF device without the gNB-CU-UP device, and transmitting an N4 session establishment request message to the UPF device, wherein the N4 session establishment request message includes the first information, and receiving an N4 session establishment response message from the UPF device, wherein the N4 session establishment response message includes a gNB-CU-UP UE E1AP ID and third information indicating a pair of an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID) for uplink data processing, and transmitting a Namf_Communication_N1N2MessageTransfer message to the AMF device, The Namf_Communication_N1N2MessageTransfer message includes the gNB-CU-UP UE E1AP ID and the third information, which means that Performing a PDU session establishment procedure, A method including.

[0233] Appendix 10. A method of a User Plane Function (UPF) device, the method including: Communicating with a gNB Distributed Unit (gNB-DU) device without involving a gNB Centralized Unit User Plane (gNB-CU-UP) device, Communicating with a gNB Centralized Unit-Control Plane (gNB-CU-CP) device without involving the gNB-CU-UP device, A method including.

[0234] Appendix 11. Transmitting a GNB-CU-CP E1 SETUP REQUEST message to the gNB-CU-CP device, where The GNB-CU-CP E1 SETUP REQUEST message includes first information indicating that the gNB-CU-CP device supports the gNB-DU device being connected to the UPF device without involving the gNB-CU-UP device, which means that Receiving a GNB-CU-CP E1 SETUP RESPONSE message from the gNB-CU-CP device, where The GNB-CU-CP E1 SETUP RESPONSE message includes second information indicating that the gNB-CU-CP device supports the gNB-DU device being connected to the UPF device without involving the gNB-CU-UP device, which means that Receiving an N4 session establishment request message from a Session Management Function (SMF) device, wherein the N4 session establishment request message includes the second information, transmitting an N4 session establishment response message to the SMF device, wherein the N4 session establishment response message includes a gNB-CU-UP UE E1AP ID and third information indicating a pair of an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID) for uplink data processing, performing a PDU session establishment procedure, The method according to Appendix 10, further comprising.

[0235] Appendix 12. A communication device, means for executing functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and functions of a User Plain Function (UPF) device, means for communicating with a gNB Distributed Unit (gNB-DU) device, means for communicating with a gNB Centralized Unit-Control Plane (gNB-CU-CP) device, A communication device comprising.

[0236] Appendix 13. A gNB Centralized Unit-Control Plane (gNB-CU-CP) device, means for receiving a Protocol Data Unit (PDU) session establishment request message from a User Equipment (UE), Means for transmitting an uplink NAS transport message to an Access and Mobility management Function (AMF) device, wherein the uplink NAS transport message includes the PDU session establishment request message and information indicating that the gNB-CU-CP device supports communication with a communication device that executes functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and a User Plain Function (UPF) device; means for receiving an Initial Context Setup Request message from the AMF device, wherein the Initial Context Setup Request message includes information about the gNB-CU-UP; means for selecting the gNB-CU-UP based on the information about the gNB-CU-UP; means for performing a PDU session establishment procedure for the UE; A gNB-CU-CP device comprising the above.

[0237] Appendix 14. An Access and Mobility management Function (AMF) device, wherein means for receiving an uplink NAS transport message from a gNB Centralized Unit Control Plane (gNB-CU-CP) device; The UPLINK NAS TRANSPORT message includes a Protocol Data Unit (PDU) session establishment request message and information indicating that the gNB-CU-CP device supports communication with a communication device that executes the functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and a User Plain Function (UPF) device, and means for this. Means for sending an Nsmf_PDUSession_CreateSMContext request message to a Session Management Function (SMF) device, wherein the Nsmf_PDUSession_CreateSMContext request message includes the information, and means for this. Means for receiving an Nsmf_PDUSession_CreateSMContext response message from the SMF device, wherein the Nsmf_PDUSession_CreateSMContext response message includes information regarding the UPF device, and means for this. Means for receiving a Namf_Communication_N1N2MessageTransfer message from the SMF device, wherein the Namf_Communication_N1N2MessageTransfer message includes information regarding the gNB-CU-UP device, and means for this. Means for sending an INITIAL CONTEXT SETUP REQUEST message to the gNB-CU-CP device, wherein the INITIAL CONTEXT SETUP REQUEST message includes the information regarding the gNB-CU-UP device, and means for this. Means for performing a PDU session establishment procedure, An AMF device comprising the above.

[0238] Appendix 15. A Session Management Function (SMF) device, means for receiving an Nsmf_PDUSession_CreateSMContext request message from an Access and Mobility management Function (AMF) device, wherein the Nsmf_PDUSession_CreateSMContext request message includes information indicating that a gNB Centralized Unit Control Plane (gNB-CU-CP) device supports communication with a communication device that executes functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and a User Plain Function (UPF) device; means for transmitting an Nsmf_PDUSession_CreateSMContext response message to the AMF device, wherein the Nsmf_PDUSession_CreateSMContext response message includes information regarding the UPF device; means for selecting the UPF device when the Nsmf_PDUSession_CreateSMContext request message includes the information; means for contacting the communication device to secure resources for processing user data; means for transmitting a Namf_Communication_N1N2MessageTransfer message to the AMF device, wherein the Namf_Communication_N1N2MessageTransfer message includes information regarding the gNB-CU-UP device; means for performing a PDU session establishment procedure; An SMF device comprising the above.

[0239] An additional note 16. A gNB Distributed Unit (gNB-DU) device, means for communicating with a gNB Centralized Unit-Control Plane (gNB-CU-CP) device; means for communicating with a User Plane Function (UPF) device without involving a gNB Centralized Unit User Plane (gNB-CU-UP) device; A gNB-DU device comprising the above.

[0240] An additional note 17. A gNB Centralized Unit-Control Plane (gNB-CU-CP) device, means for communicating with a gNB Distributed Unit (gNB-DU) device; means for communicating with a User Plane Function (UPF) device without involving a gNB Centralized Unit User Plane (gNB-CU-UP) device; A gNB-CU-CP device comprising the above.

[0241] An additional note 18. Means for receiving a GNB-CU-CP E1 SETUP REQUEST message from the UPF device, wherein the GNB-CU-CP E1 SETUP REQUEST message includes first information indicating that the UPF device supports the connection of the gNB-DU device to the UPF device without involving the gNB-CU-UP device; means for transmitting a GNB-CU-CP E1 SETUP RESPONSE message to the UPF device, means, wherein the GNB-CU-CP E1 SETUP RESPONSE message includes second information indicating that the gNB-CU-CP device supports the connection of the gNB-DU device to the UPF device without the gNB-CU-UP device; means for receiving, from a User Equipment (UE), a Protocol Data Unit (PDU) session establishment request message; means for transmitting an UPLINK NAS TRANSPORT message to an Access and Mobility management Function (AMF) device, wherein the UPLINK NAS TRANSPORT message includes the second information; means for receiving, from the AMF device, an INITIAL CONTEXT SETUP REQUEST message, wherein the INITIAL CONTEXT SETUP REQUEST message includes a gNB-CU-UP UE E1AP ID and third information indicating a pair of an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID) for uplink data processing; means for transmitting a UE CONTEXT SETUP REQUEST message to the gNB-DU device; wherein the UE CONTEXT SETUP REQUEST message includes the third information and a UL configuration Information Element (IE); means for receiving, from the gNB-DU device, a UE CONTEXT SETUP RESPONSE message; means for transmitting an INITIAL CONTEXT SETUP RESPONSE message to the AMF device; means for performing a PDU session establishment procedure; The gNB-CU-CP device according to appendix 17, further comprising:

[0242] Appendix 19. An Access and Mobility management Function (AMF) device, comprising: means for receiving an UPLINK NAS TRANSPORT message from a gNB Centralized Unit Control Plane (gNB-CU-CP) device, wherein the UPLINK NAS TRANSPORT message includes first information indicating that the gNB-CU-CP device supports the connection of a gNB Distributed Unit (gNB-DU) device to a User Plane Function (UPF) device without involving a gNB Centralized Unit User Plane (gNB-CU-UP) device; means for transmitting an Nsmf_PDUSession_CreateSMContext request message to a Session Management Function (SMF) device, wherein the Nsmf_PDUSession_CreateSMContext request message includes the first information; means for receiving an Nsmf_PDUSession_CreateSMContext response message from the SMF device, wherein the Nsmf_PDUSession_CreateSMContext response message includes second information indicating that the UPF device supports the connection of the gNB-DU device to the UPF device without involving the gNB-CU-UP device; Means for receiving a Namf_Communication_N1N2MessageTransfer message from the SMF device, wherein the Namf_Communication_N1N2MessageTransfer message includes a gNB-CU-UP UE E1AP ID and third information indicating a pair of an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID) for uplink data processing; and means for transmitting an INITIAL CONTEXT SETUP REQUEST message to the gNB-CU-CP device, wherein the INITIAL CONTEXT SETUP REQUEST message includes the gNB-CU-UP UE E1AP ID and the third information; and means for receiving an INITIAL CONTEXT SETUP RESPONSE message from the gNB-CU-CP device; means for performing a PDU session establishment procedure; An AMF device comprising the above.

[0243] Appendix 20. A Session Management Function (SMF) device, means for receiving an Nsmf_PDUSession_CreateSMContext request message from an Access and Mobility management Function (AMF) device, means for the Nsmf_PDUSession_CreateSMContext request message to include first information indicating that the gNB Distributed Unit (gNB-DU) device supports connecting to a User Plane Function (UPF) device without a gNB Centralized Unit User Plane (gNB-CU-UP) device, by a gNB Centralized Unit-Control Plane (gNB-CU-CP) device; means for transmitting an Nsmf_PDUSession_CreateSMContext response message to the AMF device, wherein the Nsmf_PDUSession_CreateSMContext response message includes second information indicating that the UPF device supports the gNB-DU device connecting to the UPF device without the gNB-CU-UP device; means for transmitting an N4 session establishment request message to the UPF device, wherein the N4 session establishment request message includes the first information; means for receiving an N4 session establishment response message from the UPF device, wherein the N4 session establishment response message includes a gNB-CU-UP UE E1AP ID and third information indicating a pair of an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID) for uplink data processing; means for transmitting a Namf_Communication_N1N2MessageTransfer message to the AMF device, wherein the Namf_Communication_N1N2MessageTransfer message includes the gNB-CU-UP UE E1AP ID and the third information; Means for performing a PDU session establishment procedure, and an SMF device comprising the same.

[0244] Appendix 21. A User Plane Function (UPF) device, comprising means for communicating with a gNB Distributed Unit (gNB-DU) device without a gNB Centralized Unit User Plane (gNB-CU-UP) device, and means for communicating with a gNB Centralized Unit-Control Plane (gNB-CU-CP) device without the gNB-CU-UP device. An UPF device comprising the same.

[0245] Appendix 22. Means for transmitting a GNB-CU-CP E1 SETUP REQUEST message to the gNB-CU-CP device, wherein the GNB-CU-CP E1 SETUP REQUEST message includes first information indicating that the UPF device supports the gNB-DU device being connected to the UPF device without the gNB-CU-UP device; means for receiving a GNB-CU-CP E1 SETUP RESPONSE message from the gNB-CU-CP device, wherein the GNB-CU-CP E1 SETUP RESPONSE message includes second information indicating that the gNB-CU-CP device supports the gNB-DU device being connected to the UPF device without the gNB-CU-UP device; means for receiving an N4 session establishment request message from a Session Management Function (SMF) device, wherein the N4 session establishment request message includes the second information. Means for transmitting an N4 session establishment response message to the SMF device, wherein the N4 session establishment response message includes a gNB-CU-UP UE E1AP ID and third information indicating a pair of an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID) for uplink data processing; and means for performing a PDU session establishment procedure; and The UPF device according to Appendix 21, further comprising:

[0246] Although the present invention has been described with reference to the embodiments (and examples), the present invention is not limited to the above embodiments (and examples). Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

[0247] This application claims priority based on Indian Provisional Patent Application No. 202111039053 filed on August 28, 2021, and incorporates the entire disclosure thereof herein.

Description of Reference Numerals

[0248] 1 Telecommunication system 3 UE 5 (R)AN node 7 Core network 20 Data network 31 Transceiver circuit 32 Antenna 33 Controller 34 User interface 35 USIM 36 Memory 51 Transceiver circuit 52 Antenna 53 Network interface 54 Controller 55 Memory 60 RU 61 DU 62 CU 70 AMF 71 SMF 72 UPF 73 PCF 74 NEF 75 UDM 76 NWDAF 361 Operating System 362 Communication Control Module 551 Operating System 552 Communication Control Module 601 Transceiver Circuit 602 Antenna 603 Network Interface 604 Controller 605 Memory 611 Transceiver Circuit 612 Network Interface 613 Controller 614 Memory 621 Transceiver Circuit 622 Network Interface 623 Controller 624 Memory 701 Transceiver Circuit 702 Network Interface 703 Controller 704 Memory 711 Transceiver Circuit 712 Network Interface 713 Controller 714 Memory 721 Transceiver Circuit 722 Network Interface 723 Controller 724 Memory 731 Transceiver Circuit 732 Network Interface 733 Controller 734 Memory 741 Transceiver Circuit 742 Network Interface 743 Controller 744 Memory 751 Transceiver Circuit 752 Network Interface 753 Controller 754 Memory 761 Transceiver Circuit 762 Network Interface 763 Controller 764 Memory 3621 Transceiver Control Module 5521 Transceiver Control Module 6051 Operating System 6052 Communication Control Module 6141 Operating System 6142 Communication Control Module 6241 Operating System 6242 Communication Control Module 7041 Operating System 7042 Communication Control Module 7141 Operating System 7142 Communication Control Module 7241 Operating System 7242 Communication Control Module 7341 Operating System 7342 Communication Control Module 7441 Operating System 7442 Communication Control Module 7541 Operating System 7542 Communication Control Module 7641 Operating System 7642 Communication Control Module 60521 Transceiver Control Module 61421 Transceiver Control Module 62421 Transceiver Control Module 70421 Transceiver Control Module 71421 Transceiver Control Module 72421 Transceiver Control Module 73421 Transceiver Control Module 74421 Transceiver Control Module 75421 Transceiver Control Module 76421 Transceiver Control Module< / nedaf> < / udm> < / nef> < / pcf> < / upf> < / smf> < / amf>

Claims

1. A method for a gNB Centralized Unit-Control Plane (gNB-CU-CP) device, the method comprising: Receiving a Protocol Data Unit (PDU) session establishment request message from a User Equipment (UE); Sending an UPLINK NAS TRANSPORT message to an Access and Mobility management Function (AMF) device, wherein the UPLINK NAS TRANSPORT message includes the PDU session establishment request message and information indicating that the gNB-CU-CP device supports communication with a communication device that executes functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and a UserPlane Function (UPF) device; Receiving an INITIAL CONTEXT SETUP REQUEST message from the AMF device, wherein the INITIAL CONTEXT SETUP REQUEST message includes information about the gNB-CU-UP device; Selecting the gNB-CU-UP device based on the information about the gNB-CU-UP device; Performing a PDU session establishment procedure for the UE; and the method.

2. A method for an Access and Mobility management Function (AMF) device, the method comprising: Receiving an uplink NAS transport message from a gNB Centralized Unit Control Plane (gNB-CU-CP) device, wherein the uplink NAS transport message includes a Protocol Data Unit (PDU) session establishment request message and information indicating that the gNB-CU-CP device supports communication with a communication device that executes functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and a User Plane Function (UPF) device, sending an Nsmf_PDUSession_CreateSMContext request message to a Session Management Function (SMF) device, wherein the Nsmf_PDUSession_CreateSMContext request message includes the information, receiving an Nsmf_PDUSession_CreateSMContext response message from the SMF device, wherein the Nsmf_PDUSession_CreateSMContext response message includes information regarding the UPF device, receiving a Namf_Communication_N1N2MessageTransfer message from the SMF device, wherein the Namf_Communication_N1N2MessageTransfer message includes information regarding the gNB-CU-UP device, sending an INITIAL CONTEXT SETUP REQUEST message to the gNB-CU-CP device, The INITIAL CONTEXT SETUP REQUEST message includes the information about the gNB-CU-UP device, and performing a PDU session establishment procedure, A method comprising: **Claim 3** A method for a Session Management Function (SMF) device, the method comprising: Receiving an Nsmf_PDUSession_CreateSMContext request message from an Access and Mobility management Function (AMF) device, where the Nsmf_PDUSession_CreateSMContext request message includes information indicating that a gNB Centralized Unit Control Plane (gNB-CU-CP) device supports communication with a communication device that executes functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and a UserPlane Function (UPF) device, and Sending an Nsmf_PDUSession_CreateSMContext response message to the AMF device, where the Nsmf_PDUSession_CreateSMContext response message includes information about the UPF device, and selecting the UPF device when the Nsmf_PDUSession_CreateSMContext request message includes the information, and contacting the communication device to secure resources for processing user data, and Sending a Namf_Communication_N1N2MessageTransfer message to the AMF device, where The Namf_Communication_N1N2MessageTransfer message includes information about the gNB-CU-UP device, performing a PDU session establishment procedure, A method comprising:

4. A gNB Centralized Unit-Control Plane (gNB-CU-CP) device, means for receiving a Protocol Data Unit (PDU) session establishment request message from a User Equipment (UE); means for transmitting an UPLINK NAS TRANSPORT message to an Access and Mobility management Function (AMF) device, wherein the UPLINK NAS TRANSPORT message includes the PDU session establishment request message and information indicating that the gNB-CU-CP device supports communication with a communication device that executes functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and functions of a UserPlane Function (UPF) device; means for receiving an INITIAL CONTEXT SETUP REQUEST message from the AMF device, wherein the INITIAL CONTEXT SETUP REQUEST message includes information about the gNB-CU-UP device; means for selecting the gNB-CU-UP device based on the information about the gNB-CU-UP device; means for performing a PDU session establishment procedure for the UE; A gNB-CU-CP device comprising:

5. An Access and Mobility management Function (AMF) device, means for receiving an UPLINK NAS TRANSPORT message from a gNB Centralized Unit Control Plane (gNB-CU-CP) device, wherein the UPLINK NAS TRANSPORT message includes a Protocol Data Unit (PDU) session establishment request message and information indicating that the gNB-CU-CP device supports communication with a communication device that executes functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and a UserPlane Function (UPF) device; means for transmitting an Nsmf_PDUSession_CreateSMContext request message to a Session Management Function (SMF) device, wherein the Nsmf_PDUSession_CreateSMContext request message includes the information; means for receiving an Nsmf_PDUSession_CreateSMContext response message from the SMF device, wherein the Nsmf_PDUSession_CreateSMContext response message includes information regarding the UPF device; means for receiving a Namf_Communication_N1N2MessageTransfer message from the SMF device, wherein the Namf_Communication_N1N2MessageTransfer message includes information regarding the gNB-CU-UP device; Means for transmitting an Initial Context Setup Request message to the gNB-CU-CP device, wherein the Initial Context Setup Request message includes the information regarding the gNB-CU-UP device, and means for performing a PDU session establishment procedure, and an AMF device comprising the above. **Claim 6** A Session Management Function (SMF) device, wherein means for receiving an Nsmf_PDUSession_CreateSMContext request message from an Access and Mobility management Function (AMF) device, wherein the Nsmf_PDUSession_CreateSMContext request message includes information indicating that a gNB Centralized Unit Control Plane (gNB-CU-CP) device supports communication with a communication device that executes functions of a gNB Centralized Unit User Plane (gNB-CU-UP) device and a User Plane Function (UPF) device, and means for transmitting an Nsmf_PDUSession_CreateSMContext response message to the AMF device, wherein the Nsmf_PDUSession_CreateSMContext response message includes information regarding the UPF device, and means for selecting the UPF device when the Nsmf_PDUSession_CreateSMContext request message includes the information, and means for contacting the communication device to secure resources for processing user data, and Means for transmitting the Namf_Communication_N1N2MessageTransfer message to the AMF device, where the Namf_Communication_N1N2MessageTransfer message includes information about the gNB-CU-UP device, and means; means for performing a PDU session establishment procedure; An SMF device comprising. **Claim 7**: A gNB Centralized Unit-Control Plane (gNB-CU-CP) device, means for communicating with a gNB Distributed Unit (gNB-DU) device; means for communicating with a User Plane Function (UPF) device without a gNB Centralized Unit User Plane (gNB-CU-UP) device; means for receiving a GNB-CU-CP E1 SETUP REQUEST message from the UPF device, where the GNB-CU-CP E1 SETUP REQUEST message includes first information indicating that the UPF device supports the gNB-DU device being connected to the UPF device without the gNB-CU-UP device, and means; means for transmitting a GNB-CU-CP E1 SETUP RESPONSE message to the UPF device, where the GNB-CU-CP E1 SETUP RESPONSE message includes second information indicating that the gNB-CU-CP device supports the gNB-DU device being connected to the UPF device without the gNB-CU-UP device, and means; means for receiving a Protocol Data Unit (PDU) session establishment request message from a User Equipment (UE); means for transmitting an UPLINK NAS TRANSPORT message to an Access and Mobility management Function (AMF) device, wherein the UPLINK NAS TRANSPORT message includes the second information; means for receiving an INITIAL CONTEXT SETUP REQUEST message from the AMF device, wherein the INITIAL CONTEXT SETUP REQUEST message includes a gNB-CU-UP UE E1AP ID and third information indicating a pair of an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID) for uplink data processing; means for transmitting a UE CONTEXT SETUP REQUEST message to the gNB-DU device, wherein the UE CONTEXT SETUP REQUEST message includes the third information and a UL configuration Information Element (IE); means for receiving a UE CONTEXT SETUP RESPONSE message from the gNB-DU device; means for transmitting an INITIAL CONTEXT SETUP RESPONSE message to the AMF device; means for performing a PDU session establishment procedure; A gNB-CU-CP device further comprising the above.

8. An Access and Mobility management Function (AMF) device, means for receiving an UPLINK NAS TRANSPORT message from a gNB Centralized Unit Control Plane (gNB-CU-CP) device, wherein the UPLINK NAS TRANSPORT message includes first information indicating that the gNB-CU-CP device supports the connection of a gNB Distributed Unit (gNB-DU) device to a User Plane Function (UPF) device without a gNB Centralized Unit User Plane (gNB-CU-UP) device; means for sending an Nsmf_PDUSession_CreateSMContext request message to a Session Management Function (SMF) device, wherein the Nsmf_PDUSession_CreateSMContext request message includes the first information; means for receiving an Nsmf_PDUSession_CreateSMContext response message from the SMF device, wherein the Nsmf_PDUSession_CreateSMContext response message includes second information indicating that the UPF device supports the connection of the gNB-DU device to the UPF device without the gNB-CU-UP device; means for receiving a Namf_Communication_N1N2MessageTransfer message from the SMF device, The Namf_Communication_N1N2MessageTransfer message includes means and the third information indicating a pair of a gNB-CU-UP UE E1AP ID and an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID) for uplink data processing. Means for transmitting an INITIAL CONTEXT SETUP REQUEST message to the gNB-CU-CP device, where The INITIAL CONTEXT SETUP REQUEST message includes means and the third information, and the third information indicates a pair of a gNB-CU-UP UE E1AP ID and the third information. Means for receiving an INITIAL CONTEXT SETUP RESPONSE message from the gNB-CU-CP device Means for performing a PDU session establishment procedure An AMF device comprising the above. Claim 9 A Session Management Function (SMF) device, where Means for receiving an Nsmf_PDUSession_CreateSMContext request message from an Access and Mobility management Function (AMF) device The Nsmf_PDUSession_CreateSMContext request message includes means for indicating first information that the gNB Distributed Unit (gNB-DU) device is supported by the gNB Centralized Unit-Control Plane (gNB-CU-CP) device to connect to a User Plane Function (UPF) device without the gNB Centralized Unit User Plane (gNB-CU-UP) device. Means for transmitting an Nsmf_PDUSession_CreateSMContext response message to the AMF device, The Nsmf_PDUSession_CreateSMContext response message includes means for indicating second information that the UPF device supports the gNB-DU device to be connected to the UPF device without the gNB-CU-UP device. Means for transmitting an N4 session establishment request message to the UPF device, The N4 session establishment request message includes means for including the first information. Means for receiving an N4 session establishment response message from the UPF device, The N4 session establishment response message includes means for including a gNB-CU-UP UE E1AP ID and third information indicating a pair of an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID) for uplink data processing. Means for transmitting a Namf_Communication_N1N2MessageTransfer message to the AMF device, The Namf_Communication_N1N2MessageTransfer message includes means for including the gNB-CU-UP UE E1AP ID and the third information. means for performing a PDU session establishment procedure, an SMF device comprising:

10. A User Plane Function (UPF) device, means for communicating with a gNB Distributed Unit (gNB-DU) device without a gNB Centralized Unit User Plane (gNB-CU-UP) device, means for communicating with a gNB Centralized Unit-Control Plane (gNB-CU-CP) device without the gNB-CU-UP device, means for transmitting a GNB-CU-CP E1 SETUP REQUEST message to the gNB-CU-CP device, wherein the GNB-CU-CP E1 SETUP REQUEST message includes first information indicating that the UPF device supports the gNB-DU device being connected to the UPF device without the gNB-CU-UP device, means for receiving a GNB-CU-CP E1 SETUP RESPONSE message from the gNB-CU-CP device, wherein the GNB-CU-CP E1 SETUP RESPONSE message includes second information indicating that the gNB-CU-CP device supports the gNB-DU device being connected to the UPF device without the gNB-CU-UP device, means for receiving an N4 session establishment request message from a Session Management Function (SMF) device, wherein the N4 session establishment request message includes the second information, means for transmitting an N4 session establishment response message to the SMF device, The N4 session establishment response message includes means, which includes a gNB-CU-UP UE E1AP ID and third information indicating a pair of an Internet Protocol (IP) address and a Tunnel Endpoint Identifier (TEID) for uplink data processing. means for performing a PDU session establishment procedure A UPF device comprising the above.

Images