Selection of user plane function and providing selected user plane functionality

Abstract

Embodiments of the present disclosure disclose a Network Repository Function (NRF). The NRF is configured to receive, from at least one user plane function (UPF), a profile registration request. The profile registration request comprises a plurality of attributes supported by the at least one UPF. The plurality of attributes at least comprise one or more of: Network Address Translation (NAT) functionality, Distributed Denial-of-Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string. The NRF is further configured to register the profile of the at least one UPF based on the plurality of attributes supported by UPF network function (NF) of the at least one UPF. The NRF is then configured to transmit a registration response indicating the registration of the UPF.

Description

SELECTION OF USER PLANE FUNCTION AND PROVIDING SELECTED USER PLANE FUNCTIONALITYCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority to Indian Provisional Application No. 202441010774, filed on February 15, 2024, and Indian Application No. 202441010774 filed on June 4, 2024 the disclosure of which is incorporated by reference herein in its entirety.FIELD

[0002] The embodiments disclosed herein generally relate to selection of user plane function and providing selected user plane functionality.BACKGROUND

[0003] Modern communication systems, such as the 5G mobile communication technology, has revolutionized a wide variety of industries with its increased speed, reduced latency and improved reliability. The Fifth Generation (5G) technology is designed to provide highspeed, low-latency, and reliable communication services, enabling the delivery of large volumes of data. Data often flows from internet server to 5G User Equipment (UEs). This has enabled the seamless transmission of large volumes of data across wireless networks.

[0004] The User Plane Function (UPF) plays a crucial role in the 5G network by facilitating low latency and high throughput. As an essential part of the Control and User Plane Separation (CUPS) strategy, the UPF embodies the advancement of the data plane, separating control and user plane functions. This separation allows packet processing and traffic aggregation to occur either within the network core or closer to its edge. Consequently, this approach enhances bandwidth efficiency and decreases network traffic. In general, the User Equipment (UE) needs to access the UPF of the 5G core network through the Radio Access Network (RAN), so that it can access the Data Network (DN).Typically, selection of an UPF is performed by the control plane based on various information including location, service, capabilities and load. More specifically, a network element i .e., such as a Session Management Function (SMF) of the 5G core network obtains information of one or more UPFs, and selects one or more UPF for facilitating the PDU session.

[0005] The information disclosed in this background section is only for enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.SUMMARY

[0006] In standard operator network configurations, various distributed UPFs may cater to different purposes like low-latency edge applications, offload requirements, or tailored services. Co-locating service functions with UPFs offers efficiencies, particularly when microservices already support some or all of these functions. Additionally, certain UPF vendors have integrated value-added service functions like deep packet inspection (DPI) and other optimization modules into their products, with some offering security or analytic capabilities. However, Network Repository Function (NRF) currently lacks the functionality to discover UPFs that consolidate these value-added service functions. Therefore, there exists a need in the art to select a UPF for efficiently facilitating the PDU session which improves a users’ mobile internet experience.

[0007] In one non-limiting embodiment of the present disclosure, a Network Repository Function (NRF) is disclosed. The NRF is configured to receive, from at least one user plane function (UPF), a profile registration request. The profile registration request comprises a plurality of attributes supported by the at least one UPF. The plurality of attributes at least comprise one or more of: Network Address Translation (NAT) functionality, Distributed Denial-of-Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operatorspecific string. The NRF is further configured to register the profile of the at least one UPF based on the plurality of attributes supported by UPF network function (NF) of the at least one UPF. The NRF is then configured to transmit a registration response indicating the registration of the UPF.

[0008] In one non-limiting embodiment of the present disclosure, a Network Repository Function (NRF) is disclosed. The NRF is configured to receive, from a session management function (SMF), a user plane function (UPF) request. The UPF request comprises one or more attributes. The NRF is further configured to identify one or more UPF, among registered UPF, at least based on the one or more attributes. The NRF is then configured to transmit information associated with the one or more identified UPF to the SMF.

[0009] In another non-limiting embodiment of the present disclosure, a method is disclosed. The method comprises receiving, from at least one user plane function (UPF), a profile registration request. The profile registration request comprises a plurality of attributes supported by the at least one UPF. The plurality of attributes at least comprise one or more of Network Address Translation (NAT) functionality, Distributed Denial-of-Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string. The method then comprises registering the profile of the at least one UPF based on the plurality of attributes supported by UPF network function (NF) of the at least one UPF. The method further comprises transmitting a registration response indicating the registration of the UPF.

[0010] In yet another non-limiting embodiment of the present disclosure, a method is disclosed. The method comprises receiving, from a session management function (SMF), a user plane function (UPF) request. The UPF request comprises one or more attributes. The method then comprises identifying one or more UPF, among registered UPF, at least based on the one or more attributes. The method then comprises transmitting information associated with the one or more identified UPF to the SMF.

[0011] In yet another non-limiting embodiment of the present disclosure, a non-transitory computer-readable medium is disclosed. The non-transitory computer-readable medium having computer-readable instructions that when executed by an apparatus causes the apparatus to perform operations of obtaining, from at least one user plane function (UPF), a profde registration request. The profile registration request comprises a plurality of attributes supported by the at least one UPF. The plurality of attributes at least comprise one or more of Network Address Translation (NAT) functionality, Distributed Denial-of- Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string. The computer-readable instructions when executed by the apparatus further causes the apparatus to perform operation of registering the profile of the at least one UPF based on the plurality of attributes supported by UPF network function (NF) of the at least one UPF. The computer-readable instructions when executed by the apparatus further causes the apparatus to perform operation of transmitting a registration response indicating the registration of the UPF.

[0012] In yet another non-limiting embodiment of the present disclosure, a non-transitory computer-readable medium is disclosed. The non-transitory computer-readable medium having computer-readable instructions that when executed by an apparatus causes the apparatus to perform operations of obtaining, from a session management function (SMF), a user plane function (UPF) request. The UPF request comprises one or more attributes. The computer-readable instructions when executed by the apparatus further causes the apparatus to perform operation of identifying one or more UPF, among registered UPF, at least based on the one or more attributes. The computer-readable instructions when executed by the apparatus further causes the apparatus to perform operation of transmitting information associated with the one or more identified UPF to the SMF.BRIEF DESCRIPTION OF DRAWINGS

[0013] Further embodiments and advantages of the present disclosure will be readily understood from the following detailed description with reference to the accompanying drawings. Reference numerals have been used to refer to identical or functionally similarelements. The figures together with a detailed description below, are incorporated in and form part of the specification, and serve to further illustrate the embodiments and explain various principles and advantages, in accordance with the present disclosure wherein:

[0014] FIG. 1 illustrates a schematic representation of 5G communication system architecture, in accordance with some embodiments of the present disclosure;

[0015] FIG. 2A illustrates a signaling diagram for registration of a User Plane Function, in accordance with some embodiments of the present disclosure;

[0016] FIG. 2B illustrates a signaling diagram for identification of a User Plane Function for facilitating a Packet Data Unit (PDU) session, in accordance with an embodiment of the present disclosure;

[0017] FIG 3 illustrates a detailed diagram of an apparatus for registration of a User Plane Function and identification of a User Plane Function for facilitating a Packet Data Unit (PDU) session, in accordance with some embodiments of the present disclosure;

[0018] FIG. 4 shows a flowchart of a method for registration of a User Plane Function with a network repository element, in accordance with some embodiments of the present disclosure;

[0019] FIG. 5 shows a flowchart of method for identification of a User Plane Function, in accordance with some embodiments of the present disclosure; and

[0020] FIG. 6 shows a diagram of example components of a network repository element (NRF) for registration of user plane function and selection of user plane function, in accordance with embodiments of the present disclosure;DETAILED DESCRIPTION

[0021] The following detailed description of example embodiments refers to the accompanying drawings. The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations. Further, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, the flowchart and description of operations provided below relate to one of the various embodiments. It should be noted that it is possible to make other embodiments that do not exactly match the flowchart and its description. It is understood that in other embodiments one or more operations may be omitted, one or more operations may be added, one or more operations may be performed simultaneously (at least in part).

[0022] It will be apparent that systems and / or methods, described herein, may be implemented in different forms of hardware, software, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the implementations. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It is understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0023] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of implementations includes each dependent claim in combination with every other claim in the claim set.

[0024] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” areintended to include one or more items, and may be used interchangeably with “one or more.” Also, as used herein, the terms “has,” “have,” “having,” “include,” “including,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Furthermore, expressions such as “at least one of [A] and [B],” “[A] and / or [B],” or “at least one of [A] or [B]” are to be understood as including only A, only B, or both A and B

[0025] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.

[0026] It shall be noted that, for convenience of explanation, the disclosure uses terms and names defined in the 3rd Generation Partnership Project Radio Access Network (3 GPP RAN) standards. More specifically, the terms ‘Service-Based Architecture’, ‘Service-Based Interface’, ‘Service-Level Agreement (SLA) criterion’, ‘Non-Public Network (NPN)’, ‘packet data network gateway’, ‘Packet Data Unit session’ and ‘Data Network’ are to be interpreted as specified by the 3 GPP RAN standards.

[0027] The term “User Plane Function (UPF) selection” as used herein refers to identifying one or more UPFs for Packet Data Unit (PDU) sessions. More specifically, the one or more UPFs are selected from among a plurality of UPFs based on at least a user plane functionality service function. In an embodiment, the user plane functionality service function may be specified by the Session Management Function (SMF). In an embodiment, the SMF may specify the user plane functionality service function based on at least an User Equipment requesting access to the Data Network (DN). In another embodiment, SMF may specify one or more user plane functionality service function of UPF for storing UPF profiles. UPF function selection based on user plane functionality service function is explained in detail with reference to FIGS. 1-6.

[0028] FIG. 1 illustrates a schematic architecture 100 of 5G communication system, where some embodiments of the present disclosure may be practiced. The architecture 100 uses a cloud-native service-based architecture (SBA) to support authentication, security, session management and aggregation of traffic from connected devices, all of which requires the complex interconnection of network functions which form a 5G core.

[0029] Accordingly, the 5G core includes a plurality of interconnected Network Functions which are defined by the 3GPP for delivering the control plane functionality and user plane functionality of the 5G communication system. In general, the plurality of interconnected Network Functions (NFs) are interconnected Network Functions with each NF authorized to access the services of other NFs. These plurality of Network Functions (or NFs) are hereinafter interchangeably referred to as ‘network element’ throughout the description. Further, for purpose of the present disclosure the term ‘NF Network Repository Function’ is interchangeably referred to as ‘NRF’ or ‘network repository element’, the term ‘Session Management Function” is interchangeably referred to herein as ‘SMF’ or ‘network session element’, and the term ‘User Plane Function’ is interchangeably referred to herein as ‘UPF’ or ‘UPF network function’ or ‘UPF NF’ throughout the disclosure.

[0030] The architecture 100 of the 5G communication system depicts a Network Slice Selection Function 102 (referred to herein as ‘NSSF 102’), a Network Exposure Function 104 (referred to herein as ‘NEF 104’), a NF Repository Function 106 (referred to herein as ‘NRF 106’), a Policy Control Function 108 (referred to herein as ‘PCF 108’), an Unified Data Management 110 (referred to herein as ‘UDM 110’), an Application Function 112 (referred to herein as ‘AF 112’), an Edge Application Server Discovery Function 114 (referred to herein as ‘EASDF 114’), a Network Slice-Specific and Stand-alone Non-Public Network (SNPN) Authentication and Authorization Function 116 (referred to herein as ‘NSSAAF 116’), an Authentication Server Function 118 (referred to herein as ‘AUSF 118’), an Access and Mobility Management Function 120 (referred to herein as ‘AMF 120’), a Session Management Function 122 (referred to herein as ‘SMF 122’), , a Network Slice Admission Control Function 126 (referred to herein as ‘NSACF 126’), a Network DataAnalytics Function 128 (referred to herein as ‘NWDAF 128’), an User Plane Function 130 (referred to herein as ‘a UPF 130’). The NSSF 102, the NEF 104, the NRF 106, the PCF 108, the UDM 110, the AF 112, the EASDF 114, the NSSAAF 116, the AUSF 118, the AMF 120, the SMF 122, the SCP 124, the NSACF 126 and the NWDAF 128 and functions of these network elements are defined by the 3 GPP standard and are not explained herein for the sake of brevity. It shall be noted that each of these NFs 102-128 may be implemented using hardware, software, firmware or any combinations thereof.

[0031] The User Equipment 140 (hereinafter referred to as ‘UE 140’) is configured to connect over the Radio Access Network (RAN) 142 to the 5G core comprising the plurality of network elements 102-128. Examples of the UE 140 include, but not limited to, any device used by a user to communicate and / or access content such as, but not limited to, mobile phones, smartphones, laptops, wearables, Internet of Things (loTs), and the like with 5G capabilities. As such, the UE 140 may be configured to connect to Data Networks 144 (also referred to herein as ‘DN 144’) through which operator services, 3rd party services, etc., can be accessed by the UE 140. An example of the DN 144 is the Internet. The AMF 120 acts as a single-entry point for the UE 140 to connect with the 5G core.

[0032] As depicted in FIG. 1, each network element of the plurality of network elements 102-128 exposes its respective functionality through a Service-Based Interface (SBI). For example, the NSSF 102 exposes functionality via Nnssf interface, the NEF 104 exposes functionality via Nnef interface, the NRF 106 exposes functionality via Nnrf interface, the PCF 108 exposes functionality via Npcf interface, the UDM 110 exposes functionality via Nudm interface, the AF 112 exposes functionality via Naf interface, the EASDF 114 exposes functionality via Neasdf interface, the NSSAAF 116 exposes functionality via Nnssaaf interface, the AUSF 118 exposes functionality via Nausf interface, the AMF 120 exposes functionality via Namf interface, the SMF 122 exposes functionality via Nsmf interface, the NSACF 126 exposes functionality via Nnsacf interface and the NWDAF 128 exposes functionality via Nnwdaf interface.

[0033] Further, N1 is an interface between the UE 140 and the AMF 120, N2 is an interface between the Radio Access Network (RAN) 142 (i.e., gNodeB) and the AMF 120, N3 interface performs the role of conveying user data from the RAN 142 to the UPF 130, N4 interface is the bridge between the control plane and the user plane of the 5G core, N6 interface provides connectivity between the UPF 130 and the DN 144 (i.e., any other external or internal networks or service platforms, such as the Internet, the public cloud or private clouds), and N9 provides an Interface between two UPF's (i.e., the Intermediate I- UPF and the UPF Session Anchor).

[0034] The UE 140 needs to access the UPF 130 of the 5G core network through the RAN 142, so that it can access the DN 144. As such, for establishing a PDU session, selection of the UPF 130 is necessary for accessing the 5G core network. There are many ways for the selection of an UPF 130 for accessing the DN 144 after accessing the 5G core network. The SMF performs selection and reselection of the UPF for PDU session establishment, UE mobility or UE traffic offloading by considering UPF deployment scenarios such as centrally located UPF and distributed UPF located close to or at the access network site.

[0035] Conventionally, TS 23.501 of 3GPP specifies selection of the UPF by the SMF 122 by optionally utilizing the NRF 106 to discover UPF instance(s) for establishing the PDU session. In this case, the SMF 122 issues a request including parameters such as Data Network Name (DNN), Single - Network Slice Selection Assistance Information (S- NSSAI), SMF Area Identity, Access Traffic Steering, Switching and Splitting (ATSSS) steering capabilities to the NRF 106. In response, the NRF 106 provides a list of available UPF(s) to the UE 140 for establishing the PDU session. However, the list of UPF shared by the NRF 106 are not specific for user plane functionality service function.

[0036] Conventionally, the N6 LAN is the portion of the 5G network that carries data from the UPF 130 to the DN 144 (i.e., Internet) and serves as a platform for service providers to offer a range of value-added services, utilizing distinctive features enabled by a mix of IPbased service functions. These functions may include firewall services, Carrier-GradeNetwork Address Translation (CGNAT), deep packet inspection (DPI), policy control, as well as traffic and content optimization.

[0037] In the current 5G architecture, Service Function Chaining, also called N6-LAN Traffic Steering, can be used to the steering of subscriber's traffic flows to appropriate operator or third party service functions in the N6-LAN. Some examples of the third party service functions include, but not limited to, NAT, antimalware, parental control, Distributed Denial-of-Service (DDoS) protection. These service functions are typically provided by a wide variety of vendors. Service providers need to steer the traffic and direct it to specific service functions, which might be linked together, as required, to adhere to specific policy enforcement and service-level agreements tailored to individual subscribers.

[0038] However, there are multiple challenges in the current approach such as, increased latency of service chaining, operational complexity, consistency of the application platform and additional Capex / Opex. One of the primary goals of 5G is to provide reduced and bound latency. The use of multiple user-plane network functions in a service chain might considerably increase processing time, defeating the primary goal of 5G. Further, mixing CNFs from various vendors adds cloud-native network function (CNF) sprawl and adds operational complexity due to different tooling needed to manage these CNFs throughout their life cycle. Moreover, the service providers need the CNFs to be deployed across the network to where it makes most sense, whether different cloud providers, on-premise data centres, or edge locations. The application platform needs to provide a consistent experience across these different environments. Furthermore, additional Capex / Opex is required for the operators to maintain separate service functions for these value add services.

[0039] In clause 5.6.16.1, as outlined in TS 23.501 [2], it is noted that all UPFs in the operator network serving as PDU Session Anchor (PSA) for the Data Network Name (DNN) / Single - Network Slice Selection Assistance Information (S-NSSAI) / Data Network Access Identifier (DNAI) subject to N6-LAN traffic steering need to be configured with the same traffic steering information for N6-LAN traffic steering. However, it'simportant to recognize that such uniformity may present drawbacks, including limitations in flexibility, scalability concerns, and potential security implications.

[0040] In standard operator network configurations, various distributed UPFs may cater to different purposes like low-latency edge applications, offload requirements, or tailored services. Co-locating service functions with UPFs offers efficiencies, particularly when microservices already support some or all of these functions. Additionally, certain UPF vendors have integrated value-added service functions like DPI and other optimization modules into their products, with some offering security or analytic capabilities. UPF has supported to register in NRF. This registration phase uses the Nnrf NFManagement NFRegister operation. But some the UPF capabilities are not included in the UPF Provisioning Information in the NRF. Thus, NRF currently lacks the functionality to discover UPFs that consolidate these value-added service functions.

[0041] In an example scenario, where some of the UPFs support NAT, it is a challenge to select a UPF as per requirement. For example, selecting an UPF from UPFs with NAT, UPFs without NAT. Moreover, each UPF with NAT may have specific range / address of public IP. In such a scenario, identifying a UPF from the UPFs supporting features as NAT is a challenge.

[0042] In another example scenario, if a UPF enabled with security features, for example, DDoS or Firewall support in UPF needs to be identified, then it becomes a challenge to identify which of the UPF supports such security features. One of the key product capabilities that is often integrated in the UPF is DPI based services. DPI is the examination of layer 7 (L7), which contains Uniform Resource Identifier (URI) information. In some cases, layer 3 (L3) and layer 4 (L4) analyzers that identify a trigger condition are insufficient for billing purposes, so layer 7 examination is used. In such example scenarios, layer 7 (L7) UPF equipped with features for DPI inspection need to be identified. In view of the above, there exists a need to extend the existing UPF advertising capabilities in case UPF hasintegrated additional functionalities such as, NAT, security features, DPI capabilities, etc. to identify which UPF may suit the service function.

[0043] Various embodiments of the present disclosure disclose techniques for registering a profile of UPF with NRF 106 based on additional parameters or supported service functions, such as but not limited to, supporting NAT, supporting DDoS or Firewall, L7 DPI, and the like. More specifically, UPFs indicate one or more service functions while registering with the NRF 106. When a request for UPFs of a specific user plane functionality is received from the SMF 122, one or more UPFs from a plurality of UPFs registered with the NRF 106 are identified based on the user plane functionality. Further, the NRF 106 sends information related to the one or more UPFs to the SMF 122 for facilitating a PDU session for the UE 140. In other words, during the discovery of UPF supporting selected user plane functionality, a SMF 122 may include in a discovery request to NRF 106, a required UPF capability information. As such, the NRF 106 returns one or more UPF candidates to the SMF 122. Such techniques of providing UPFs specific to a service function or user plane functionality requested by the SMF 122 and improves overall user experience as such UPFs are equipped to support user requirements such as, reduced latency, faster processing, energy efficiency, enhanced data rates, Quality of Service (QoS) and the like, based on the application.

[0044] Referring to FIG. 2A which illustrates a signaling diagram 200a for registration of a User Plane Function (UPF) 130, in accordance with an embodiment of present disclosure. The signaling diagram 200a includes UPF 130 and NRF 106.

[0045] Initially, the UPF 130 may send the Nnrf_NFManagement_NFRegister request message to NRF 106, when the NF service consumer becomes operative for the first time (as shown by step SI). The Nnrf_NFManagement_NFRegister request message is used to inform the NRF 106 of NF profile parameters / attributes associated with the UPF 130. The UPF NF profile parameters may include existing parameters defined e.g,. S-NSSAI(s) and the associated NSI ID(s), DNN(s), IP range, DNAI etc. Further, the UPF NF profileparameters may additionally include one or more of Network Address Translation (NAT) functionality, Distributed Denial-of-Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string. However, the NF profile param eters / attributes are not limited to above stated param eters / attributes and any other NF profile parameters / attributes for supporting different network functionalities of the UPF 130 is well within the scope of present disclosure.

[0046] The NRF 106 may register the profile of the UPF 130 based on the UPF NF profile parameters / attributes (as shown by step S2). The registration may include storing of the UPF NF profile parameters / attributes against the respective UPF in the NRF 106.

[0047] The NRF 106 may then acknowledge UPF Registration is accepted via Nnrf_NFManagement_NFRegister response. The Nnrf_NFManagement_NFRegister response is then transmitted to the UPF 130 (as shown by step S3). In one non-limiting embodiment, the above step S1-S3 may be performed by the plurality of UPFs to register with the NRF 106.

[0048] Thus, the present disclosure facilitates enhanced UPF registration in NRF to support UPF selection / discovery with specific user plane functionalities.

[0049] Referring to FIG. 2B which illustrates a signaling diagram for identification of a User Plane Function for facilitating a Packet Data Unit (PDU) session, in accordance with an embodiment of the present disclosure. The signaling diagram 200a includes SMF 122 and NRF 106.

[0050] Initially, the SMF 122 (or consumer) discovers the UPF via the NRF by invoking the Nnrf_NFDiscovery_Request service operation (as shown by step SI). In an embodiment, the UPF request is sent from the network session element 122 in response toa PDU session request from the UE. The Nnrf_NFDiscovery_Request may include one or more selected user plane functionality / attributes required by the consumer. The one or more attributes may comprise one or more of: Network Address Translation (NAT) functionality, Distributed Denial-of-Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string. In one non-limiting embodiment, the one or more attributes may also comprise existing parameters defined e.g,. S-NSSAI(s) and the associated NSI ID(s), DNN(s), IP range, DNAI etc.

[0051] Then, the NRF 106 authorizes the NF service discovery request and identifies one or more UPF, among registered UPF, based on the one or more attributes present in the Nnrf_NFDiscovery_Request (as shown by step S2). In an embodiment, the plurality of user profiles associated with the plurality of UPFs registered with the NRF 106 are searched to identify the one or more UPF associated with the one or more attributes specified in the Nnrf_NFDi scovery_Request.

[0052] Once the one or more UPF are identified, the NRF 106 notifies the consumer with the one or more UPF using the Nnrf_NFDiscovery_Request Response (as shown by step S3). The user plane functionality capability information of the one or more UPF may include NAT, DDoS or Firewall, Layer 7 DPI capability, etc.

[0053] Thus, the present disclosure provides UPFs specific to a service function or user plane functionality requested by the SMF 122 and improves overall user experience as such UPFs are equipped to support user requirements such as, reduced latency, faster processing, energy efficiency, enhanced data rates, and Quality of Service (QoS).

[0054] Referring now to FIG. 3 which illustrates a detailed diagram of an apparatus 300, in accordance with some embodiments of the present disclosure. The apparatus 300 may be network repository function (NRF) 106, as discussed in above embodiments.

[0055] In some implementations, the apparatus 300 may include an I / O interface 301, a processor 303, and a memory 305. In an embodiment, the memory 305 may be communicatively coupled to the processor 303. The processor 303 may be configured to perform one or more functions of the NRF 106 for registration of a User Plane Function and identification of a User Plane Function for facilitating a Packet Data Unit (PDU) session. In an embodiment, the memory 305 may store data 307. Although the FIG. 3 shows the hardware components of the NRF 106, it is to be understood that other embodiments are not limited thereon. In other embodiments, the NRF 106 may include less or a greater number of components. Further, the labels or names of the components are used only for illustrative purpose and does not limit the scope. One or more components can be combined together to perform same or substantially similar technical feature for the co-ordination between the NRF, UPF, and SMF.

[0056] In an embodiment, the data 307 stored in the memory 305 may include, without limitation, UPF profile data 311 and other data 313. In some implementations, the data 307 may be stored within the memory 305 in the form of various data structures. Additionally, the data 307 may be organized using data models, such as relational or hierarchical data models. The other data 313 may include various temporary data and files generated by the one or more modules 309.

[0057] In an embodiment, the data 307 may be processed by one or more modules 309 of the NRF 106. In some implementations, the one or more modules 309 may be communicatively coupled to the processor 303 for performing one or more functions of the NRF 106. In an implementation, the one or more modules 309 may include, without limiting to, a transceiver module 315 and other modules 317.

[0058] As used herein, the term module may refer to an Application Specific Integrated Circuit (ASIC), an electronic circuit, a hardware processor 303 (shared, dedicated, or group) and memory that execute one or more software or firmware programs, a combinational logiccircuit, and / or other suitable components that provide the described functionality. In an implementation, each of the one or more modules 309 may be configured as stand-alone hardware computing units. In an embodiment, the other modules 317 may be used to perform various miscellaneous functionalities on the NRF 306. It will be appreciated that such one or more modules 309 may be represented as a single module or a combination of different modules.

[0059] The I / O interfaces 301 may allow the apparatus 300 to communicate with one or more nodes / devices either directly or through other devices. The I / O interfaces 301 may include network interface to allow the apparatus 300 to interact with one or more networks either directly or via any other network.

[0060] The processor 303 may be configured to receive a profile registration request. The profile registration request may comprise a plurality of attributes supported by the at least one UPF. The profile registration request may be received from a user plane function (UPF). The plurality of attributes may include one or more of: Network Address Translation (NAT) functionality, Distributed Denial-of-Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string.

[0061] In an embodiment, the packet inspection functionality at least comprises layer 7 deep packet inspection (DPI) and the packet inspection functionality further comprises specific transport levels or applications. Further, the one or more hardware configurations may include Network Interface Controllers (NIC) with different latency characteristics. However, the packet inspection functionality and the one or more hardware configurations are not limited to above example and any other packet inspection functionality or hardware configuration known to a person skilled in the art is well within the scope of the present disclosure.Y1

[0062] In an embodiment, the operator specific string comprises text field indicating operator specific configurability. The operator specific string may support one or more functionalities supported by the UPF.

[0063] In one non-limiting embodiment, the plurality of attributes may also include existing one or more parameters such as UPF’s dynamic load, UPF’s location, UPF relative static capacity, UPF service location, service type, resource specifications, and the like.

[0064] The processor 303 may be then configured to register the profile of the UPF based on the plurality of attributes supported by UPF network function (NF) of the UPF. The registration may include storing of the UPF profile data 311 in the memory 305. The processor 303 may be then configured to transmit a registration response indicating the registration of the UPF, as discussed in step S3 of FIG. 2A.

[0065] Thus, the apparatus 300 facilitates enhanced UPF registration in NRF to support UPF selection / discovery with specific user plane functionalities.

[0066] In an embodiment, the processor 303 may be configured to receive a user plane function (UPF) request comprising one or more attributes. The UPF request may be received from a session management function (SMF). The one or more attributes may include one or more of Network Address Translation (NAT) functionality, Distributed Denial-of-Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string. In one non-limiting embodiment, the one or more attributes may also include UPF’s dynamic load, UPF load prediction, UPF’s location, UPF relative static capacity, UE location information, functionality required for the PDU session, Data Network Name (DNN), PDU session type, SSC mode selected for the PDU session, UE subscription profile, local operator policies, access technology used by the UE, user plane latency requirements, and Access Traffic Steering, Switching and Splitting (ATSSS) steering capability for the PDU session, and the like.

[0067] The processor 303 may be configured to identify one or more UPF at least based on the one or more attributes. The processor 303 may be configured to search / compare one or more attributes in the registered UPF profiles.

[0068] In response to identification of the one or more UPFs supporting the one or more attributes, the processor 303 may be configured to transmit information associated with the one or more identified UPF to the SMF.

[0069] Thus, the apparatus 300 provides UPFs specific to a service function or user plane functionality requested by the SMF and improves overall user experience as such UPFs are equipped to support user requirements such as, reduced latency, faster processing, energy efficiency, enhanced data rates, and Quality of Service (QoS).

[0070] Referring now to FIG. 4, which illustrates a flowchart of a method for registration of a User Plane Function with a network repository element. The method 400 is merely provided for exemplary purposes, and embodiments are intended to include or otherwise cover timing advance management procedures. In one non-limiting embodiment, the method 400 may be performed by the NRF 106, as discussed in above embodiments.

[0071] The method 400 may include, at block 401, receiving a profile registration request. The profile registration request may comprise a plurality of attributes supported by the at least one UPF. The profile registration request may be received from a user plane function (UPF). The plurality of attributes may include one or more of: Network Address Translation (NAT) functionality, Distributed Denial-of-Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string.

[0072] In an embodiment, the packet inspection functionality at least comprises layer 7 deep packet inspection (DPI) and the packet inspection functionality further comprises specific transport levels or applications. Further, the one or more hardware configurations may include Network Interface Controllers (NIC) with different latency characteristics. However, the packet inspection functionality and the one or more hardware configurations are not limited to above example and any other packet inspection functionality or hardware configuration known to a person skilled in the art is well within the scope of the present disclosure.

[0073] In an embodiment, the operator specific string comprises text field indicating operator specific configurability. The operator specific string may support one or more functionalities supported by the UPF.

[0074] In one non-limiting embodiment, the plurality of attributes may also include existing one or more parameters such as UPF’s dynamic load, UPF’s location, UPF relative static capacity, UPF service location, service type, resource specifications, and the like.

[0075] The method 400 may include, at block 403, registering the profile of the UPF based on the plurality of attributes supported by UPF network function (NF) of the UPF. The registration may include storing of the UPF profile data in the memory.

[0076] The method 400 may include, at block 405, transmitting a registration response indicating the registration of the UPF, as discussed in step S3 of FIG. 2A. Thus, the method 400 facilitates enhanced UPF registration in NRF to support UPF selection / discovery with specific user plane functionalities.

[0077] Referring now to FIG 5, which illustrates a flowchart of method for identification of a User Plane Function. The method 500 is merely provided for exemplary purposes, and embodiments are intended to include or otherwise cover any timing advance managementmethods or procedures. In one non-limiting embodiment, the method 500 may be performed by NRF 106.

[0078] The method 500 may include, at block 501, receiving a user plane function (UPF) request comprising one or more attributes. The UPF request may be received from a session management function (SMF). The one or more attributes may include one or more of Network Address Translation (NAT) functionality, Distributed Denial-of-Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string. In one nonlimiting embodiment, the one or more attributes may also include UPF’s dynamic load, UPF load prediction, UPF’s location, UPF relative static capacity, UE location information, functionality required for the PDU session, Data Network Name (DNN), PDU session type, SSC mode selected for the PDU session, UE subscription profile, local operator policies, access technology used by the UE, user plane latency requirements, and Access Traffic Steering, Switching and Splitting (ATSSS) steering capability for the PDU session, and the like.

[0079] The method 500 may include, at block 503, identifying one or more UPF at least based on the one or more attributes. The identifying may include searching one or more attributes in the registered UPF profiles by comparing the one or more attributes present in the UPF request with registered / stored UPF network function (NF) profiles.

[0080] The method 500 may include, at block 505, in response to identification of the one or more UPFs supporting the one or more attributes, transmitting information associated with the one or more identified UPF to the SMF.

[0081] Thus, the method 500 provides UPFs specific to a service function or user plane functionality requested by the SMF and improves overall user experience as such UPFs are equipped to support user requirements such as, reduced latency, faster processing, energy efficiency, enhanced data rates, and Quality of Service (QoS).

[0082] FIG. 6 illustrates an embodiment of a network repository function (NRF) 600. As shown in FIG. 6, the NRF comprises a processor 610, a memory 620, a storage component 630, an input component 640, an output component 650, a communication interface 660, and a bus 670.

[0083] The processor 610, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 610 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and / or one or more single core processors, a distributed processing system, or the like. The processor 502 may be a Central Processing Unit (CPU)a graphics processing unit (GPU), an accelerated processing unit (APU), an applicationspecific integrated circuit (ASIC), or another type of processing component.

[0084] The memory 620 includes a non-transitory computer readable medium. Memory 620 includes a random-access memory (RAM), a read only memory (ROM), and / or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, and / or an optical memory) that stores information and / or instructions for use by processor 610. The memory 620 comprises machine-readable instructions which are executable by the processor 610. These machine-readable instructions when executed by the processor 502 cause the processor 610 to perform one or more method steps of an embodiment described above.

[0085] The storage component 630 stores information and / or software related to the operation and use of the NRF 600. For example, the storage component 630 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and / or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transitory computer-readable medium, along with a corresponding drive.

[0086] The input component 640 is configured to receive information, such as user input. For example, the input component 640 may include, but not be limited to, a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone. Additionally, or alternatively, the input component 640 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gyroscope, and / or an actuator).

[0087] The output component 650 is configured to provide output information from the NRF 600. For example, the output component 650 may be, but not limited to, a display, a speaker, instructions to an external device, and / or one or more light-emitting diodes (LEDs).

[0088] The communication interface 660 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 660 can be a wired connection, a wireless connection, or a combination of wired and wireless connections, and can be a direct connection or an indirect connection via a communication network that exists between the NRF 600 and other devices. In other words, the standard of the communication interface 660 is not limited.

[0089] The bus 670 acts as an interconnect between the processor 610, the memory 620, the storage component 630, the input component 640, the output component 650, and the communication interface 660 of the NRF 600. The bus 670 may include a wired interconnection or a wireless interconnection.

[0090] The number and arrangement of components shown in FIG. 6 are provided as an example. In practice, NRF 600 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 6. Additionally, or alternatively, a set of components (e.g., one or more components) of theNRF 600 may perform one or more functions described as being performed by another set of components of the NRF 600.

[0091] The present disclosure may further include the below embodiments:

[0001] A Network Repository Function (NRF) configured to: receive, from at least one user plane function (UPF), a profile registration request comprising a plurality of attributes supported by the at least one UPF, wherein the plurality of attributes at least comprise one or more of: Network Address Translation (NAT) functionality, Distributed Denial-of- Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string; register the profile of the at least one UPF based on the plurality of attributes supported by UPF network function (NF) of the at least one UPF; and transmit a registration response indicating the registration of the UPF.[2] The NRF of embodiment 1, wherein the packet inspection functionality at least comprises layer 7 deep packet inspection (DPI), and wherein the packet inspection functionality further comprises specific transport levels or applications.[3] The NRF of embodiment 1, wherein the one or more hardware configurations comprises Network Interface Controllers (NIC) with different latency characteristics.[4] The NRF of embodiment 1, wherein the operator specific string comprises text field indicating operator specific configurability.[5] A Network Repository Function (NRF) configured to: receive, from a session management function (SMF), a user plane function (UPF) request comprising one or more attributes; identify one or more UPF, among registered UPF, at least based on the one or more attributes; and transmit information associated with the one or more identified UPF to the SMF.[6] The NRF of embodiment 5, wherein to identify one or more UPF, the NRF is configured to: compare the one or more attributes present in the UPF request with stored UPF network function (NF) profiles.[7] The NRF of embodiment 5, wherein the one or more attributes at least comprises one or more of Network Address Translation (NAT) functionality, Distributed Denial-of- Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string.[8] A method performed by a Network Repository Function (NRF), the method comprising: receiving, from at least one user plane function (UPF), a profile registration request comprising a plurality of attributes supported by the at least one UPF, wherein the plurality of attributes at least comprise one or more of Network Address Translation (NAT) functionality, Distributed Denial-of-Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string; registering the profile of the at least one UPF based on the plurality of attributes supported by UPF network function (NF) of the at least one UPF; and transmitting a registration response indicating the registration of the UPF.[9] The method of embodiment 8, wherein the packet inspection functionality at least comprises layer 7 deep packet inspection (DPI), and wherein the packet inspection functionality further comprises specific transport levels or applications.

[0010] The method of embodiment 8, wherein the one or more hardware configurations comprises Network Interface Controllers (NIC) with different latency characteristics.

[0011] The method of embodiment 8, wherein the operator specific string comprises text field indicating operator specific configurability.

[0012] A method performed by a Network Repository Function (NRF), the method comprising: receiving, from a session management function (SMF), a user plane function (UPF) request comprising one or more attributes; identifying one or more UPF, among registered UPF, at least based on the one or more attributes; and transmitting information associated with the one or more identified UPF to the SMF.

[0013] The method of embodiment 12, wherein identifying one or more UPF comprises: comparing the one or more attributes present in the UPF request with stored UPF network function (NF) profiles.

[0014] The method of embodiment 12, wherein the one or more attributes at least comprises one or more of: Network Address Translation (NAT) functionality, Distributed Denial-of- Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string.

[0015] A non-transitory computer-readable medium having computer-readable instructions that when executed by an apparatus causes the apparatus to perform operations of: obtaining, from at least one user plane function (UPF), a profile registration request comprising a plurality of attributes supported by the at least one UPF, wherein the plurality of attributes at least comprise one or more of Network Address Translation (NAT) functionality, Distributed Denial-of-Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string; registering the profile of the at least one UPF based on the plurality of attributes supported by UPF network function (NF) of the at least one UPF; and transmitting a registration response indicating the registration of the UPF.

[0016] A non-transitory computer-readable medium having computer-readable instructions that when executed by an apparatus causes the apparatus to perform operations of: obtaining, from a session management function (SMF), a user plane function (UPF) request comprising one or more attributes; identifying one or more UPF, among registered UPF, at least basedon the one or more attributes; and transmitting information associated with the one or more identified UPF to the SMF.

Claims

WE CLAIM1. A Network Repository Function (NRF) configured to: receive, from at least one user plane function (UPF), a profile registration request comprising a plurality of attributes supported by the at least one UPF, wherein the plurality of attributes at least comprise one or more of: Network Address Translation (NAT) functionality, Distributed Denial-of-Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string; register the profile of the at least one UPF based on the plurality of attributes supported by UPF network function (NF) of the at least one UPF; and transmit a registration response indicating the registration of the UPF.

2. The NRF of claim 1, wherein the packet inspection functionality at least comprises layer 7 deep packet inspection (DPI), and wherein the packet inspection functionality further comprises specific transport levels or applications.

3. The NRF of claim 1, wherein the one or more hardware configurations comprises Network Interface Controllers (NIC) with different latency characteristics.

4. The NRF of claim 1, wherein the operator specific string comprises text field indicating operator specific configurability.

5. A Network Repository Function (NRF) configured to: receive, from a session management function (SMF), a user plane function (UPF) request comprising one or more attributes; identify one or more UPF, among registered UPF, at least based on the one or more attributes; and transmit information associated with the one or more identified UPF to the SMF.

6. The NRF of claim 5, wherein to identify one or more UPF, the NRF is configured to: compare the one or more attributes present in the UPF request with stored UPF network function (NF) profiles.

7. The NRF of claim 5, wherein the one or more attributes at least comprises one or more of Network Address Translation (NAT) functionality, Distributed Denial-of-Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string.

8. A method performed by a Network Repository Function (NRF), the method comprising: receiving, from at least one user plane function (UPF), a profile registration request comprising a plurality of attributes supported by the at least one UPF, wherein the plurality of attributes at least comprise one or more of Network Address Translation (NAT) functionality, Distributed Denial-of-Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string; registering the profile of the at least one UPF based on the plurality of attributes supported by UPF network function (NF) of the at least one UPF; and transmitting a registration response indicating the registration of the UPF.

9. The method of claim 8, wherein the packet inspection functionality at least comprises layer 7 deep packet inspection (DPI), and wherein the packet inspection functionality further comprises specific transport levels or applications.

10. The method of claim 8, wherein the one or more hardware configurations comprises Network Interface Controllers (NIC) with different latency characteristics.

11. The method of claim 8, wherein the operator specific string comprises text field indicating operator specific configurability.

12. A method performed by a Network Repository Function (NRF), the method comprising: receiving, from a session management function (SMF), a user plane function (UPF) request comprising one or more attributes; identifying one or more UPF, among registered UPF, at least based on the one or more attributes; and transmitting information associated with the one or more identified UPF to the SMF.

13. The method of claim 12, wherein identifying one or more UPF comprises: comparing the one or more attributes present in the UPF request with stored UPF network function (NF) profiles.

14. The method of claim 12, wherein the one or more attributes at least comprises one or more of: Network Address Translation (NAT) functionality, Distributed Denial-of- Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string.

15. A non-transitory computer-readable medium having computer-readable instructions that when executed by an apparatus causes the apparatus to perform operations of: obtaining, from at least one user plane function (UPF), a profile registration request comprising a plurality of attributes supported by the at least one UPF, wherein the plurality of attributes at least comprise one or more of Network Address Translation (NAT) functionality, Distributed Denial-of-Service (DDoS) protection, Domain Name Service (DNS) spoofing, packet inspection functionality, energy saving, one or more hardware configurations, and operator specific string; registering the profile of the at least one UPF based on the plurality of attributes supported by UPF network function (NF) of the at least one UPF; and transmitting a registration response indicating the registration of the UPF.

16. A non-transitory computer-readable medium having computer-readable instructions that when executed by an apparatus causes the apparatus to perform operations of: obtaining, from a session management function (SMF), a user plane function (UPF) request comprising one or more attributes; identifying one or more UPF, among registered UPF, at least based on the one or more attributes; and transmitting information associated with the one or more identified UPF to the SMF.

Images