Service type based user plane function selection for packet data unit sessions

Abstract

Embodiments of the present disclosure disclose service type based user plane function selection for packet data unit sessions. The network repository element (106) receives, from the network session element (122), a UPF request for detecting one or more UPFs from the plurality of UPFs. The UPF request at least comprises a UPF service type. The network repository element (106) is configured to identify one or more UPFs from the plurality of UPFs based on the UPF service type. The network repository element (106) is configured to send information related to the one or more UPFs to the network session element (122). The network session element (122) is configured to identify a UPF from the one or more UPFs for facilitating a packet data unit (PDU) session based on the information and the one or more selection parameters.

Description

TECHNICAL FIELD

[0001] The present disclosure relates generally to communication technologies, and more specifically to service type based user plane function selection for packet data unit sessions. BACKGROUND

[0002] Modern communication systems, such as 5G mobile communication technologies, have revolutionized various industries with their increased speed, reduced latency, and improved reliability. 5G mobile communication technologies have a mobile core infrastructure specified by the Third Generation Partnership Project (3GPP) New Radio (NR) that decouples the functions of a packet data network gateway (PGW) between a control plane and a user plane. Such split architecture of the PGW in the 5G core network allows independent scalability, evolution, and flexible deployment of the user plane and the control plane. In the 3GPP specification, the PGW user plane function is also referred to as a user plane function (UPF), which acts as an anchor point for a packet data unit (PDU) data session. Typically, a user equipment (UE) needs to access a UPF of a 5G core network through a radio access network (RAN) to access a data network (DN). Therefore, one important aspect in establishing a PDU data session is to select a UPF for accessing the 5G core network. Generally, the selection of the UPF is performed by the control plane based on various information including location, service, capability, 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 UPFs for facilitating a PDU session.

[0003] In view of the above discussion, there is a need to identify a UPF for efficiently facilitating a PDU session that improves the mobile internet experience of users.

[0004] The information disclosed in the Background section of this disclosure is only for the purpose of enhancing the understanding of the general background of the present disclosure and should not be taken as admitting or in any form implying that this information constitutes prior art known to those skilled in the art. SUMMARY

[0005] Generally, a user plane function (UPF) selection function in a session management function (SMF) can utilize a network repository function (NRF) to discover UPF instance(s). However, for specific applications or specific types of subscribers, some SMFs can need specific UPF(s) or a group of UPF(s).

[0006] In an embodiment, a network repository function is disclosed. The network repository function includes a memory and a processor. The memory is configured to store instructions and a plurality of user plane functions (UPFs) registered with the network repository function. The processor is configured to execute the instructions stored in the memory to: receive, from a network session function, a UPF request for detecting one or more UPFs from the plurality of UPFs. The UPF request includes at least a UPF service type. The processor is configured to identify the one or more UPFs from the plurality of UPFs based on the UPF service type. The processor is configured to send, to the network session function, information related to the one or more UPFs. The processor is configured to identify a UPF from the one or more UPFs based on the information and one or more selection parameters for facilitating a packet data unit (PDU) session.

[0007] In another embodiment, a method is disclosed. The method includes receiving, by a network repository function, from a network session function, a UPF request for detecting one or more UPFs from a plurality of UPFs registered with the network repository function. The UPF request includes at least a UPF service type. The method includes identifying, by the network repository function, the one or more UPFs from the plurality of UPFs based on the UPF service type. The method includes sending, by the network repository function, to the network session function, information related to the one or more UPFs. The network session function is configured to identify a UPF from the one or more UPFs based on the information and one or more selection parameters for facilitating a packet data unit (PDU) session.

[0008] In yet another embodiment, a system is disclosed. The system includes a network session function and a network repository function. The network repository function stores a plurality of user plane functions (UPFs) registered with the network repository function. The network repository function is communicatively coupled with the network session function. The network repository function is configured to receive a UPF request for detecting one or more UPFs from the plurality of UPFs. The UPF request includes at least a UPF service type. The network repository function is configured to identify the one or more UPFs from the plurality of UPFs based on the UPF service type. The network repository function is configured to send, to the network session function, information related to the one or more UPFs. The network session function is configured to identify a UPF from the one or more UPFs based on the information and one or more selection parameters for facilitating a packet data unit (PDU) session.

[0009] The above summary is illustrative only and is not intended to be limiting in any way. Still other aspects, embodiments, and features relating to the aspects and embodiments described herein can be gleaned from the drawings and the following detailed description. BRIEF DESCRIPTION OF DRAWINGS

[0010] The accompanying drawings, which are incorporated into and constitute a part of this disclosure, illustrate exemplary embodiments and together with the description, serve to explain the principles disclosed. Like numbers refer to like features and components throughout the drawings. Some embodiments of apparatuses and / or methods in accordance with embodiments of the present subject matter will now be described, by way of example only, and with reference to the accompanying drawings:

[0011] Figure 1 illustrates a schematic diagram of a 5G communication system architecture in which some embodiments of the present disclosure can be practiced;

[0012] Figure 2 illustrates a network element for service type based user plane function selection for packet data unit (PDU) session, in accordance with embodiments of the present disclosure;

[0013] Figure 3 illustrates a sequence flow diagram representing a method for registering a user plane function (UPF) with a network repository element, in accordance with embodiments of the present disclosure;

[0014] Figure 4 illustrates a sequence flow diagram representing a method for identifying a user plane function (UPF) for facilitating a packet data unit (PDU) session, in accordance with embodiments of the present disclosure;

[0015] Figure 5 illustrates a sequence flow diagram representing an exemplary method for identifying one or more user plane functions (UPFs) from a plurality of UPFs based on UPF service type international roaming, in accordance with embodiments of the present disclosure;

[0016] Figure 6 illustrates a network session element for service type based user plane function (UPF) selection for packet data unit (PDU) session, in accordance with embodiments of the present disclosure;

[0017] Figure 7 illustrates a network repository element for service type based user plane function (UPF) selection for packet data unit (PDU) session, in accordance with embodiments of the present disclosure; and

[0018] Figure 8 is a flow diagram illustrating a method for service type based user plane function (UPF) selection for packet data unit (PDU) session, in accordance with embodiments of the present disclosure.

[0019] Those skilled in the art will appreciate that any flow charts, flow diagrams, state transition diagrams, pseudocode, and the like represent various processes which can be substantially represented in computer readable medium and so executed by a computer or processor, whether or not such computer or processor is explicitly shown. DETAILED DESCRIPTION

[0020] In this document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any implementation of the subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other implementations.

[0021] While the disclosure is susceptible to various modifications and alternative forms, specific embodiments thereof have been shown by way of example in the drawings and will be described in detail herein. It should be understood, however, that it is not intended to limit the disclosure to the particular forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the disclosure.

[0022] The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion such that a setup, device, or method that comprises a list of components or steps does not include only those components or steps but can include other components or steps not expressly listed or inherent to such setup, device, or method. In other words, one or more elements of a device, system, or apparatus preceded by "comprises... a" does not, without more constraints, preclude the existence of other elements or additional elements in the device, system, or apparatus.

[0023] In the following detailed description of embodiments of the disclosure, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments in which the disclosure can be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other embodiments can be utilized and that changes can be made without departing from the scope of the present disclosure. The following description is, therefore, not to be taken in a limiting sense.

[0024] It should be noted that the disclosure uses terminology and names defined in the Third Generation Partnership Project Radio Access Network (3GPP RAN) standards for ease of explanation. More specifically, the terms'service-based architecture','service-based interface','service level agreement (SLA) criteria', 'non-public network (NPN)', 'packet data network gateway', 'packet data unit session', and 'data network' should be interpreted as per the provisions of the 3GPP RAN standards.

[0025] As used herein, the term "user plane function (UPF) selection" refers to identifying one or more UPFs for a packet data unit (PDU) session. More specifically, the one or more UPFs are selected from a plurality of UPFs based at least on a service type. In embodiments, the service type can be specified by a session management function (SMF). In examples, the SMF can specify the service type based at least on a user equipment requesting access to a data network (DN). In another embodiment, the SMF can specify a UPF that stores one or more service types for UPF profiles. UPF function selection based on service type Figures 1 to 8 is explained in detail.

[0026] Figure 1 Figure illustrates a schematic architecture 100 of a 5G communication system in which some embodiments of the present disclosure can be practiced. The architecture 100 uses a cloud-aligned service-based architecture (SBA) to support authentication, security, session management, and aggregation of traffic from connected devices, all of which require complex interconnections of network functions that form the 5G core.

[0027] Accordingly, the 5G core includes a plurality of interconnected network functions defined by 3GPP for delivering control plane and user plane functions of the 5G communication system. Generally, the plurality of interconnected network functions (NFs) are network functions that are connected to each other, where each NF is authorized to access services of other NFs. Throughout the following description, these plurality of network functions (or NFs) are interchangeably referred to as 'network elements'. Furthermore, for the purposes of the present disclosure, in the present disclosure, the term 'NF network repository function' is interchangeably referred to as 'NRF' or 'network repository element', and the term'session management function' is interchangeably referred to as 'SMF' or 'network session element'.

[0028] The architecture 100 of a 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’), an NF repository function 106 (referred to herein as ‘NRF 106’), a policy control function 108 (referred to herein as ‘PCF 108’), a 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 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 service communication proxy 124 (referred to herein as ‘SCP 124’), a network slice admission control function 126 (referred to herein as ‘NSACF 126’), a network data analytics function 128 (referred to herein as ‘NWDAF 128’), a user plane function 130 (referred to herein as ‘UPF 130’). The NSSF 102, NEF 104, NRF 106, PCF 108, UDM 110, AF 112, EASDF 114, NSSAAF 116, AUSF 118, AMF 120, SMF 122, SCP 124, NSACF 126, and NWDAF 128, and the functions of these network elements are defined by 3GPP standards, and are not explained herein for brevity. It should be noted that each of these NFs 102-128 can be implemented using hardware, software, firmware, or any combination thereof.

[0029] A user equipment 140 (referred to herein as ‘UE 140’) is configured to connect to a 5G core including the plurality of network elements 102-128 through a radio access network (RAN) 142. Examples of the UE 140 include, but are not limited to, any device used by a user for communication and / or accessing content, such as, but not limited to, a 5G-capable mobile phone, a smartphone, a laptop, a wearable device, an Internet of Things (IoT), etc. Thus, the UE 140 is configured to connect to a data network 144 (also referred to herein as ‘DN 144’), through which the UE 140 can access operator services, third-party services, etc. An example of the DN 144 is the Internet. The AMF 120 serves as a single point of entry for the UE 140 to connect with the 5G core.

[0030] As Figure 1As shown, each 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 an Nnssf interface, the NEF 104 exposes functionality via an Nnef interface, the NRF 106 exposes functionality via an Nnrf interface, the PCF 108 exposes functionality via an Npcf interface, the UDM 110 exposes functionality via an Nudm interface, the AF 112 exposes functionality via an Naf interface, the EASDF 114 exposes functionality via an Neasdf interface, the NSSAF 116 exposes functionality via an Nnssaaf interface, the AUSF 118 exposes functionality via an Nausf interface, the AMF 120 exposes functionality via an Namf interface, the SMF 122 exposes functionality via an Nsmf interface, the SCP 124 exposes functionality via an Nscp interface, the NSACF 126 exposes functionality via an Nnsaf interface, and the NWDAF 128 exposes functionality via an Nnwdaf interface.

[0031] Further, N1 is the interface between the UE 140 and the AMF 120, N2 is the interface between the Radio Access Network (RAN) 142 (i.e., gNodeB) and the AMF 12, the N3 interface performs the role of transporting user data from the RAN 142 to the UPF 130, the N4 interface is a bridge between the control plane and user plane of the 5G core, the N6 interface provides connectivity between the UPF 130 and the DN 144 (i.e., any other external or internal network or service platform, such as the Internet, public cloud, or private cloud), and N9 provides an interface between two UPFs (i.e., intermediate I-UPF and UPF session anchor).

[0032] 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. Thus, for establishing a PDU session, the selection of the UPF 130 is necessary for accessing the 5G core network. After accessing the 5G core network, there are many methods for selecting the UPF for the UE 140 to access the DN 144.

[0033] Traditionally, 3GPP's TS 23.501 specifies selection of UPF by SMF 122 by optionally utilizing NRF 106 to discover the UPF instance(s) for establishing a PDU session. In this case, SMF 122 issues a request to NRF 106 that includes 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 capability, etc. In response, NRF 106 provides a list of available UPF(s) to UE 140 for establishing a PDU session. However, the list of UPFs shared by NRF 106 is not specific to a service type.

[0034] In an example scenario, a user of a 5G communication system can be an enterprise subscriber for a service utilized by UE 140. Thus, UE 140 can be entitled to enable connectivity and advanced functionalities. In an instance, UE 140 can choose to send media content including promotional offers for display in real-time at a recipient mobile device (i.e., a current or potential enterprise customer). In another case, a user can be an Internet of Things (IoT) subscriber in a 5G communication system. Thus, UE 140 associated with the user can require services that are ultra-reliable and have low latency. In this case, a dedicated UPF that supports such services for the user can be beneficial. In other cases, a framework that allows allocation of dedicated UPF resources to a particular service or a particular subscriber or group of subscribers (e.g., to enable service independence and isolation) can be beneficial. Generally, a UPF can be selected based on one or more selection parameters such as dynamic load of the UPF, location of the UPF, UPF relative static capacity, UPF service location, service type, resource specification, etc. However, user requirements for a particular service do not impact selection of the UPF.

[0035] Various embodiments of the present disclosure disclose techniques for service type based UPF selection for packet data unit session. More specifically, at registration with the NRF 106, the UPF indicates one or more service types. Thus, when a request for a UPF for a particular service type is received from the SMF 122, one or more UPFs from the plurality of UPFs registered with the NRF 106 are identified. Further, the NRF 106 sends information related to the one or more UPFs to the SMF 122. The SMF 122 identifies a UPF from the one or more UPFs based on the information and one or more selection parameters for facilitating a PDU session for the UE 140. Further, the NRF 106 identifies suspended UPFs based on a status of each UPF to identify the one or more UPFs to ensure that a suspended UPF is not provided for the PDU session. Such techniques of providing service type specific UPFs improve the overall user experience as such UPFs are equipped to support user needs such as reduced latency, faster processing, energy efficiency, enhanced data rates, quality of service (QoS) etc. based on the application, which will be further explained with reference to Figures 2 to 8

[0036] Figure 2 Figure illustrates network elements 200 for service type based UPF selection for packet data unit session, according to an embodiment of the present disclosure. The term ‘service type’ used herein refers to a category of services that can be provided by a UPF. More specifically, each UPF can be adapted to provide one or more specific services based on available resources of the corresponding UPF. Thus, each service type can depend on one or more of: application type, number of users, mobility of the UE 140, latency requirement, data rate, etc. Some examples of service types include, but are not limited to, international roaming, corporate services, enterprise services, Internet of Things (IoT), immersive gaming, mobile network operator (MNO), mobile virtual network operator (MVNO), satellite, OTT based application services, dedicated 5G slices, domestic roaming, augmented reality application services, virtual reality application services, smart city services, multi-access edge computing (MEC), voice services, etc. For example, the service type can be immersive gaming (e.g. augmented reality, virtual reality, etc.) where a subscriber can require high data rates and low latency, which can be supported by a specific UPF from all the UPFs registered with the NRF 106. In another example, the service type can be IoT, where an IoT subscriber requires ultra-reliable and low latency services. Such service types can be used for dedicated UPF selection to enable specific service level architecture. The service type of a UPF is defined as an attribute information element in the UpfInfo.

[0037] ​In this embodiment, network element 200 is network session element 122. Network session element 122 can be configured to perform... Figure 1 The SMF 122 shown is functional. In an exemplary embodiment, network session element 122 is referred to as session management function 122 or SMF 122. In another embodiment, network element 200 is network repository element 106. Network repository element 106 can be configured to perform... Figure 1 The NRF 106 is shown to have functionality. In an exemplary embodiment, the network repository function 106 is referred to as network repository element 106 or NRF 106. In yet another embodiment, network element 200 is a system embodying the functionality of SMF 122 and NRF 106.

[0038] As previously described, network element 200 embodies one or more network functions and interconnects with other NFs 102 to 128 of the 5G core network for type-of-service (UPF) selection for PDU sessions in architecture 100. Network element 200 is capable of performing one or more of the operations described herein. It should be noted that embodiments of this disclosure have been explained herein with reference to 5G communication systems. However, for those skilled in the art, the techniques employed by network element 200 for type-of-service (UPF) selection for PDU sessions can be applied to other communication systems, such as those employing SBA, for efficient UPF selection based on the type of service for PDU sessions, as will be explained herein. Therefore, network element 200 can be a centralized or distributed server configured to perform one or more functions of SMF 122 and / or NRF 106 described herein.

[0039] Network element 200 is depicted as including processor 202, memory 204, input / output module 206, and communication interface 208. It should be noted that in some embodiments, network element 200 may include more or fewer components than depicted herein. The various components of network element 200 may be implemented using hardware, software, firmware, or any combination thereof. Furthermore, the various components of network element 200 may be operatively coupled to each other. More specifically, the various components of network element 200 are capable of communicating with each other using a communication channel medium such as a bus, interconnect, etc. In embodiments, the functionality of NRF 106 and SMF 122 may be implemented within processor 202. It should be noted that processor 202 may include fewer or more modules than described herein.

[0040] In one embodiment, the processor 202 can be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and one or more single core processors. For example, the processor 202 can be embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), processing circuitry with or without an accompanying DSP, or various other processing devices including microcontroller units (MCUs), hardware accelerators, application- specific computer chips, or the like.

[0041] In one embodiment, the memory 204 is capable of storing machine executable instructions, referred to herein as instructions 205. In an embodiment, the processor 202 is embodied as an executor of software instructions. Thus, the processor 202 is capable of executing the instructions 205 stored in the memory 204 to perform one or more operations described herein.

[0042] The memory 204 can be any type of memory that is accessible by the processor 202 to perform the respective functions. For example, the memory 204 can include one or more volatile or non-volatile memories, or a combination thereof. For example, the memory 204 can be embodied as a semiconductor memory, such as a flash memory, mask ROM, PROM (programmable ROM), EPROM (erasable PROM), RAM (random access memory), or the like.

[0043] In an embodiment, the memory 204 stores a plurality of UPFs registered with the network repository element 106. In an example, the UPFs can be categorized based on their service type, and stored in the memory 204. More specifically, a service type profile can be created for each service type, and a list of UPFs registered with such service type can be added to the corresponding service type profile.

[0044] In an embodiment, when the network element 200 is a network repository function (i.e., the NRF 106), the processor 202 is configured to execute the instructions 205 to: (1) receive a registration request from a UPF, (2) register the UPF with one or more UPF service types, (3) receive a UPF request from a network session element 122 (i.e., the SMF 122) for detecting one or more UPFs, (4) determine suspended UPFs based on a status of each UPF in a set of UPFs associated with at least one service type, (5) identify one or more UPFs from a plurality of UPFs based on the UPF service types, (6) send information related to the one or more UPFs to the network session element 122, (7) send a notification related to a new UPF registered with the NRF 106. In an embodiment, when the network element 200 is a network session element 122 (i.e., the SMF 122), the processor 202 is configured to execute the instructions 205 to: (1) send a UPF request to the network repository function 106 for detecting one or more UPFs, (2) receive information related to the one or more UPFs from the network repository function 106, (3) identify a UPF from the one or more UPFs based on the information and one or more selection parameters for facilitating a PDU session.

[0045] In an embodiment, the I / O module 206 can include mechanisms (not shown in the figure) configured to receive input from, and to provide output to, an operator of the network element 200. The term ‘operator of the network element 200’ used herein can refer to one or more persons directly or indirectly related to managing the 5G communication system, such as an operator or a service provider. To enable the reception of input and to provide output to the network element 200, the I / O module 206 can include at least one input interface and / or at least one output interface. Examples of the input interface can include, but are not limited to, a keyboard, a mouse, a joystick, a keypad, a touchscreen, soft keys, a microphone, etc. Examples of the output interface can include, but are not limited to, a display such as a light emitting diode display, a thin-film transistor (TFT) display, a liquid crystal display, an active-matrix organic light-emitting diode (AMOLED) display, a microphone, a speaker, a ringer, etc.

[0046] In an embodiment, the communication interface 208 can include mechanisms configured to communicate with other entities in a 5G communication system, such as other network elements (i.e., NFs 102, 104, 106, 108, 110, 112, 114, 116, 118, 120, 122, 124, 126, and 128), for service type based user plane function selection. In an embodiment, if the network element 200 is the network repository function 106, the input is received from the network session function 122 (i.e., SMF 122) via the communication interface 208. In another embodiment, if the network element 200 is the network session function 122, the input is received from the network repository function (i.e., NRF 106) via the communication interface 208. More specifically, the communication interface 208 is an SBI interface, which can be Nnrf if the network element 200 is the NRF 106, or the interface can be Nsmf if the network element 200 is the SMF 122, for interaction with Figure 1 other network elements (i.e., NFs 102 to 128) in the architecture 100 shown.

[0047] In an embodiment, the communication interface 208 can receive, from a UPF, a registration request for registration with the network repository element 106. The registration request includes one or more UPF service types. In an example, the UPF can indicate the service types as international roaming and premium streaming. The service type attributes are part of the UpfInfo that will be sent with the registration request. Such techniques of indicating the UPF service types as part of the registration request ensures that the network element 200 (i.e., the network repository element 106) classifies and stores each UPF based on the service types. Additionally, upon receiving a UPF request from another network element (i.e., the session management element 122), the UPF of a particular service type can be efficiently retrieved from the network repository element 106. In an embodiment, the communication interface 208 can also receive, from the network session element 122, a UPF request for one or more UPFs from a plurality of UPFs stored in the network repository element 106. The UPF request includes at least a UPF service type. More specifically, the service type of the UPF required by the network session element 122 is indicated in the UPF request. This ensures that a dedicated UPF can be provisioned for each PDU data session request. In an embodiment, the UPF request can be received as part of a subscription for UPFs of at least one service type. Receiving a subscription of UPF information of a particular service type can enable receiving a dedicated UPF for the particular service type periodically, or upon registration of a new UPF with the specified service type. In another embodiment, the UPF request can be received in response to a PDU session request from the UE 140. The PDU session can involve a particular service type, and thus the UPF request including the service type can ensure that an appropriate UPF is provided to facilitate the PDU session. For example, if the PDU session involves media streaming, and if the UPF request includes the service type (e.g., media streaming) of the UPF required for the PDU session, then a UPF that best supports such service will be provided to the UE 140.

[0048] The network element 200 is depicted in operative communication with a database 220. In one embodiment, the database 220 is configured to store UPF registration policies for registering one or more UPFs with the network repository function 106. Further, the database 220 stores a plurality of UPF profiles related to a plurality of UPFs. The UPF profiles include one or more parameters related to a UPF, such as, for example, dynamic load of the UPF, location of the UPF, UPF relative static capacity, UPF service location, service type, resource specification, etc. In an embodiment, the database 220 can also store subscription information received from one or more SMFs (e.g., SMF 122). The subscription information includes information related to UPFs of at least one particular service type. This ensures that the network repository function 106 sends an update when registering a new UPF of the particular service type requested by the NRF 106 with the network repository function 106 (i.e., the NRF 106). In some embodiments, the subscription can include a request to share information related to the UPFs registered with the NRF 106 and the service type.

[0049] The database 220 is also configured to store a status of each UPF. The status of a UPF indicates whether the UPF is active or suspended. If a UPF is registered with the NRF 106 but the UPF is not operational, the status is a suspended status. More specifically, if a UPF does not update its configuration file for a configurable amount of time (i.e., longer than a heartbeat interval), the NRF 106 changes the status of the UPF to suspended. If the UPF is operational, the status of the UPF is active for discovery by other NFs (i.e., SMF 122). These multiple UPFs can register with the NRF 106 for anchoring PDU sessions. In embodiments, the database 220 also includes one or more predefined rules for selecting a UPF for a PDU session. More specifically, the predefined rules indicate various values for each of one or more selection parameters that are used to select a UPF for a PDU session. Some examples of selection parameters include, but are not limited to, dynamic load of a UPF, UPF load prediction, location of a UPF, UPF relative static capacity, UE location information, functionality required for a PDU session, data network name (DNN), PDU session type, SSC mode selected for a PDU session, UE subscription profile, local operator policy, access technology used by the UE, user plane latency requirement, and access traffic steering, switching, and splitting (ATSSS) steering capability for a PDU session, etc. In examples, the predefined rules can specifically indicate network resources / parameters that can be critical requirements for a PDU session. For example, a predefined rule to select a UPF from a set of UPFs with a particular service type can be to select a UPF that can provide premium subscription for a UE at ‘x’ location, which has a PDU session for immersive video spanning 2 hours, and is capable of supporting a data rate of ‘y’ Mbps. It should be noted that the above predefined rules are for illustrative purposes only, and the database 220 can have multiple predefined rules with different constraints / thresholds specified on selection parameters (i.e., network resources / parameters) for optimally selecting a UPF for a PDU session.

[0050] The database 220 can include multiple storage units, such as hard disks and / or solid state disks in a redundant array of independent disks (RAID) configuration. In some embodiments, the database 220 can include a storage area network (SAN) and / or a network attached storage (NAS) system. In one embodiment, the database 220 can correspond to a distributed storage system, where individual databases are configured to store custom information, such as historical data related to suspended UPFs, UPF restoration policies, heartbeat information for each UPF, status of UPFs, subscription information, UPF configuration files, other NF configuration files, types of network resources / parameters associated with each network function, etc.

[0051] In some embodiments, the database 220 is integrated within the network element 200. For example, the network element 200 can include one or more hard disk drives as the database 220. In other embodiments, the database 220 is external to the network element 200 and can be accessed by the network element 200 using a storage interface (not shown). The storage interface is any component capable of providing the processor 202 with access to the database 220. The storage interface can include, for example, an Advanced Technology Attachment (ATA) adapter, a Serial ATA (SATA) adapter, a Small Computer System Interface (SCSI) adapter, a RAID controller, a SAN adapter, a network adapter, and / or any component that provides the processor 202 with access to the database 220. Figure 2

[0052] As previously mentioned, the communication interface 208 is configured to receive a registration request from a UPF for registration with the network repository element 106. In addition, the communication interface 208 is also configured to receive a UPF request from the network session element 122. It should be noted that the receipt of the registration request from the UPF prior to the receipt of the UPF request is explained herein for exemplary purposes, and the UPF registration request can be received at a later time after the receipt of the UPF request. The communication interface 208 is configured to forward the registration request from the UPF to the processor 202. The processor 202, in conjunction with the instructions 205 stored in the memory 204, is configured to process the registration request and perform one or more functions that will be described herein. The processing of the UPF request will be explained later with reference to Figure 4 Figure 3

[0053] Figure 3 FIG. 3 illustrates a sequence flow diagram representing a method 300 for registering a UPF 302 with a network repository element 106, according to an embodiment of the present disclosure. Each UPF instance can register, update, or deregister its profile in the network repository element 106. Thus, each UPF registers a UPF profile and a list of services provided by the UPF in the network repository element 106.

[0054] ​​​At 302, a registration request is received from the UPF 302. The registration request includes one or more UPF service types. More specifically, the registration request includes a UPF profile of the UPF 302. Typically, the UPF profile includes one or more information elements, such as one or more attributes. For example, attributes such as a list of per-SNSSAI parameters supported by the UPF, one or more SMF areas that the UPF 302 can serve, a list of user plane interfaces configured on the UPF 302, one or more service types, and PDU session types supported by the UPF, etc. It should be noted that the attributes disclosed in the UPF profile are for illustrative purposes only, and the UPF profile can include fewer or more attributes, for example, general parameters related to dynamic load capacity, interworking with EPS capabilities, UPF relative static capacity, etc.

[0055] In an embodiment, the one or more attributes are information elements in the Upflnfo. Thus, the UPF service types are information elements in the Upflnfo. Some examples of the UPF service types include, but are not limited to, international roaming, corporate services, enterprise services, Internet of Things (loT), immersive gaming, live media content subscribers, etc. It should be noted that the examples of the UPF services described herein are for illustrative purposes only, and different types of UPF service types can be defined to accommodate multiple applications based on self-organization specified by the 3GPP standards. For example, a class of subscribers (e.g., government or defense organizations) can require secure UPFs specifically dedicated to their services, and thus, a UPF can be defined to support such a service type.

[0056] In an embodiment, the UPF 302 can support one or more service types. For example, the UPF 302 is capable of supporting loT subscribers and live media subscribers. For example, the UPF 302 has resources to support low latency, low loss, and high data rate services, and thus, the UPF can register in two different service types, i.e., loT service and live media service. Thus, both of these service types can be indicated in the corresponding service type information elements of the Upflnfo. More specifically, the service type attribute can be added to the UPF NFProfile attribute of the Upflnfo defined in TS 29.510, as shown in Table 1 below. Table 1

[0057] It should be noted that although the data type has been specified as a string, any other data type can be used to indicate the service type of the UPF 302. For example, if the UPF 302 supports two different service types and the data type is a string, then the string (e.g., “ab12cd”) can be used to represent each of these service types based on a lookup table.

[0058] At 304, the network repository element 106 validates the registration request of the UPF 302.

[0059] At 306, the network repository element 106 registers the UPF 302 with the network repository element 106. More specifically, the network repository element 106 stores the UPF profile including the service type in a database or memory of the network repository element 106.

[0060] At 308, the network repository element 106 sends a notification to the UPF 302. The notification is a confirmation indicating the registration of the UPF 302.

[0061] At 310, the network repository element 106 sends a status update request to the UPF 302. After registering the UPF with the network repository element 106, the network repository element 106 can request a status update from the UPF 302 at a defined time interval (e.g., every 2 minutes). Thus, the status update request can be sent from the network repository element 106 to the UPF 302 at the defined time interval. Alternatively, the network repository element 106 sends the status update request initially, which instructs the UPF 302 to automatically share status updates at the defined time interval. This ensures that the network repository element 106 has a track of the status of the UPF 302.

[0062] At 312, the UPF 302 sends a heartbeat to the network repository element 106. In an embodiment, the heartbeat can be sent in response to receiving the status update request from the network repository element 106. In another embodiment, the UPF 302 automatically sends the heartbeat after every defined time interval for providing status updates to the network repository element 106. If the UPF 302 is operational, then the status of the UPF 302 is updated as active, whereas if the UPF 302 fails to send the heartbeat, then the status of the UPF 302 is updated as suspended. This ensures that the suspended UPFs are not selected for facilitating the PDU session.

[0063] The sequence of operations of the method 300 need not be performed in the same order as presented. Furthermore, one or more operations can be combined together and performed in the form of a single step, or an operation can have several sub-steps which can be performed in parallel or in series. The method 400 representing a method for identifying a UPF for facilitating a packet data unit (PDU) session is illustrated in accordance with an embodiment of the disclosure is explained below with reference to Figure 4

[0064] Figure 4 The method 400 representing a method for identifying a UPF for facilitating a packet data unit (PDU) session is illustrated in accordance with an embodiment of the disclosure is explained below with reference to

[0065] At 402, the network session element 122 sends a UPF request to the network repository element 106. In an embodiment, the UPF request is sent from the network session element 122 in response to a PDU session request from a UE. In an example, if the UE 140 requests a PDU session for accessing information from the DN 144, the network session element 122 generates the UPF request. In another embodiment, the UPF request is sent as part of a subscription for UPFs for at least one service type. More specifically, the network session element 122 can subscribe to receive information related to UPFs registered with the network repository element 106. In an embodiment, the UPF request includes at least one service type. For example, the UPF request from the network session element 122 can specify a service type of international roaming. It should be noted that the UPF request can include more than one service type, for example, as part of a subscription, the network session element 122 can send a UPF request including service types of international roaming subscribers, and IoT subscribers. Additionally, the UPF request can include additional attributes for the subscription, such as a frequency of receiving UPFs, conditions associated with the subscription, and the like.

[0066] At 404, the network repository element 106 identifies one or more UPFs from a plurality of UPFs based on the UPF service type. More specifically, a plurality of user profiles associated with a plurality of UPFs registered with the network repository element 106 are searched to identify a set of UPFs associated with the UPF service type specified in the UPF request. After retrieving the set of UPFs, the network repository element 106 determines suspended UPFs based on a status of each UPF in the set of UPFs to identify the one or more UPFs. Typically, the network repository element 106 stores the status of the plurality of UPFs in a database, for example, the database 220. Thus, a UPF can be in an active state and a suspended state. The UPFs in the suspended state are excluded and the one or more UPFs in the active state and providing the service type specified in the UPF request are identified. ​

[0067] At 406, the network repository element 106 sends information related to one or more UPFs to the network session element 122. More specifically, one or more UPF profiles corresponding to one or more UPFs are sent to the network session element 122 in response to the UPF request. It should be noted that the information (i.e., one or more UPF profiles) is sent in response to a subscription or request for a PDU session from the UE 140.

[0068] At 408, the network session element 122 identifies a UPF from the one or more UPFs based on the information and one or more selection parameters. Some examples of the selection parameters include, but are not limited to, dynamic load of the UPF, UPF load prediction, location of the UPF, 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 policy, access technology used by the UE, user plane latency requirement, and access traffic steering, switching, and splitting (ATSSS) steering capability for the PDU session. More specifically, a UPF is selected based on the PDU session requirement to provide a high QoS and seamless experience for the user. It should be noted that if the UPF request is a subscription, the information related to one or more UPFs is stored in a database (see database 610 of FIG. 6) of the network session element 122. Whenever a request for a PDU session is received, the network session element 122 selects a UPF (i.e., UPF 302) from one or more UPFs of the service type required for the data session by the UE 140. Figure 6

[0069] At 410, the network session element 122 facilitates a protocol data unit (PDU) session. The PDU session is facilitated by the UPF 302 selected by the network session element 122 from the one or more UPFs.

[0070] At 412, the network repository element 106 sends a notification related to a new UPF registered with at least one service type based on the subscription of the network session element 122. In an example, if the network session element 122 subscribes to receive information (i.e., user profile) related to UPFs registered with the service type international roaming, the information related to one or more UPFs with the service type international roaming can be sent to the network session element 122 after validating the subscription. In another embodiment, a new UPF can be registered with the service type international roaming at a later time. In this case, if the new UPF provides the service type international roaming, an update with the user profile is sent to the network session element 122.

[0071] ​While embodiments of the present disclosure describe selecting one or more UPFs based on a service type of the UPF, it should be noted that the UPF request can include other information elements that specify parameters / attributes for selection of one or more UPFs. For example, an SMF area identity can be used to determine whether a UPF can provide service to an area indicated by the SMF area identity. Thus, a UPF can only be selected if it matches all attributes / parameters specified in the UPF request. Further, it should be noted that the service type of the UPF is only used to select one or more UPFs from the network repository element 106, and the selection of a UPF for a PDU session for the UE 140 can be based on one or more selection parameters.

[0072] The sequence of operations of the method 400 need not be performed in the same order as presented. Further, one or more operations can be combined together and performed in the form of a single step, or an operation can have several sub-steps that can be performed in parallel or sequentially. An example scenario of identifying one or more UPFs based on a UPF request is shown and explained with reference to Figure 5

[0073] Figure 5 A sequence flow diagram representing an example method 500 for identifying one or more UPFs from a plurality of UPFs based on UPF service type international roaming is illustrated in accordance with an embodiment of the present disclosure.

[0074] At 510, the UPF 502 registers with the network repository element 106. In this example representation, the UPF 502 registers with the service type of international roaming in UpfInfo. The registration procedure of registering a UPF with the network repository element 106 is explained with reference to Figure 3 and is not explained here for brevity.

[0075] At 512, the network repository element 106 sends a notification indicating completion of the registration procedure. Similarly, at 514 and 518, the UPFs 504 and 506 register with the network repository element 106. The UPF 504 registers with the service types of immersive gaming and IoT services, while the UPF 506 registers with the service types of international roaming and IoT services. Thus, at 516 and 520, notifications of registration are sent to the UPFs 504 and 506, respectively.

[0076] At 522, the network session element 122 sends a UPF request to the network repository element 106. The UPF request includes a service type specified as international roaming, which indicates that the network session element 122 is requesting one or more UPFs that provide international roaming service.

[0077] ​At 524, the network repository element 106 identifies the UPFs 502 and 506 that provide the service type of international roaming.

[0078] At 526, in response to the UPF request, information related to the UPFs 502 and 506 is sent to the network session element 122. As explained with reference to Figure 4 the network session element 122 selects a UPF for the PDU session from the one or more UPFs based on one or more selection parameters. Block diagrams of the network session element 122 and the network repository element 106 are described below with reference to Figures 6 to 7 FIGS. 6 and 7, respectively.

[0079] Figure 6 FIG. illustrates a network session element 122 for service type based user plane function selection for packet data unit sessions, according to embodiments of the disclosure. The network session element 122 as explained herein includes the functionality of a session management function (SMF) and a packet data network gateway control (PGW-C), and is depicted in Figure 1 as the SMF 122. The network session element 122 manages the establishment of connections for the UE 140 to the DN 144, as well as managing the UPF 130 for the connection. Generally, the network session element 122 is a control function that manages PDU sessions, including the establishment, modification, and release of sessions. The network session element 122 communicates with the UE 140 indirectly through the AMF 120, which relays session related messages between the UE 140 and the network session element 122.

[0080] The network session element 122 includes a processor 602 configured to fetch programming instructions from a memory 604 to provide the various features of the disclosure. The components of the network session element 122 provided herein can not be exhaustive, and the network session element 122 can include more or less components than those shown. Further, two or more components can be embodied in a single Figure 6 component, and / or a component can be configured using multiple sub-components to perform the desired functions. Some components of the network session element 122 can be configured using hardware elements, software elements, firmware elements, and / or combinations thereof.

[0081] Via the communication interface 620, the processor 602 is configured to: (1) send a UPF request to the network repository element 106, and (2) receive information related to one or more UPFs from the network repository element 106. The communication can be implemented through API calls without loss of generality. In an embodiment, the communication interface 620 is an SBI interface, which can be Nsmf. The network session element 122 communicates with one or more network elements in the 5G communication system, such as the NFs 102, 104, 106, 108, 110, 112, 114, 116, 118, 120, 124, 126, and 128, via the communication interface 620 for service type based user plane function selection. Thus, the network session element 122 interacts with other NFs in the 5G communication system to manage a PDU session for a UE, such as the UE 140.

[0082] The memory 604 can be any type of memory accessible by the processor 602 to perform the respective functions. For example, the memory 604 can include one or more volatile or non-volatile memories, or a combination thereof, to store instructions 605 to: (1) send a UPF request including at least one service type to the network repository element 106, (2) receive information related to one or more UPFs from the network repository element 106, (3) identify a UPF from the one or more UPFs based on the information and one or more selection parameters, (4) facilitate a PDU session for the UE 140 based on the UPF.

[0083] In an embodiment, the I / O interface 608 can include mechanisms that are configured to receive input from and provide output to peripheral devices, such as the plurality of NFs 102-128 of the 5G communication system. Some examples of the I / O interface 608 include, but are not limited to, a keyboard, a mouse, a keypad, a touchscreen, soft keys, a microphone, a display, etc. The network session element 122 is depicted in operative communication with a database 610. In one embodiment, the database 610 is configured to store session management policies for managing PDU sessions, subscription information, UPF profiles, UPF requests, etc.

[0084] In one embodiment, the memory 604 is capable of storing machine executable instructions, referred to herein as instructions 605. Accordingly, the processor 202 is capable of executing the instructions 605 stored in the memory 604 to perform one or more operations described herein. The processor 602 is capable of processing information of one or more UPFs associated with a service type received from the network repository element 106 for identifying a UPF from the one or more UPFs based on one or more selection parameters for facilitating a PDU session. Further, the processor 602 manages the PDU session for the UE 140, such as establishment, modification, and release of the PDU session by communicating with the AMF 120 via the communication interface 620. A schematic block diagram of the network repository element 106 is shown and explained hereinafter with reference to Figure 7

[0085] Figure 7 is a simplified block diagram of the network repository element 106 used for service type based user plane function selection for packet data unit (PDU) session in accordance with an embodiment of the disclosure. The network repository element 106 as described herein performs one or more functions of the NRF defined in the 3GPP standards.

[0086] The network repository element 106 includes at least one processor 702, an input / output (I / O) interface 715, a communication interface 720, and a memory 704 communicably coupled to a database 710. The components of the network repository element 106 provided herein can not be exhaustive and the network repository element 106 can include more or less components than those shown. Further, two or more components can be embodied in a single component, and / or a component can be configured to use a plurality of sub-components to implement the desired functions. Some components of the network repository element 106 can be configured using hardware elements, software elements, firmware elements, and / or combinations thereof. Figure 7

[0087] The I / O interface 715 can include mechanisms configured to receive input from and provide output to peripheral devices, such as the plurality of NFs 102-128 of the 5G communication system and an operator or service provider managing the network repository element 106. For example, the I / O interface 715 can include at least one input interface and / or at least one output interface. Examples of the input interface can include, but are not limited to, a keyboard, a mouse, a joystick, a keypad, a touchscreen, soft keys, a microphone, etc. Examples of the output interface can include, but are not limited to, a UI display such as a light emitting diode display, a thin film transistor (TFT) display, a liquid crystal display, an active matrix organic light emitting diode (AMOLED) display, etc., a speaker, a ringer, a vibrator, etc.

[0088] ​​The memory 704 can be any type of memory accessible by the processor 702. For example, the memory 704 can include volatile or non-volatile memory, or a combination thereof. In an embodiment, the memory 704 stores a plurality of UPF configuration files associated with a plurality of UPFs registered with the network repository function 106. In an example, the UPFs can be categorized based on their service type and stored in the memory 704. More specifically, for each service type, a service type configuration file (e.g., immersive gaming UPF, secure UPF, etc.) can be created and a list of UPFs registered with such service type can be added to the corresponding service type configuration file.

[0089] The database 710 is capable of storing and / or retrieving data, such as but not limited to storing a UPF registration policy for registering one or more UPFs with the network repository function 106, a plurality of UPF configuration files related to a plurality of UPFs, subscription information received from one or more SMFs (e.g., SMF 122), a status of each UPF of the plurality of UPFs, a list of suspended UPFs, one or more predefined rules for selecting a UPF for a PDU session, etc. Such information can be accessed by the processor 702 using the communication interface 720 to select a UPF based on a service type of a PDU session for the UE 140.

[0090] The network repository function 106 is capable of communicating with one or more network elements in the 5G communication system, such as the NFs 102, 104, 108, 110, 112, 114, 116, 118, 120, 122, 124, 126, and 128, via the communication interface 720 for service type based user plane function selection. The communication interface 720 is an SBI interface, which can be Nnrf. In an embodiment, the network repository function 106 communicates with the UPF 302 via the communication interface 720 for: (1) receiving a registration request from the UPF 302 including one or more service types of the UPF 302, (2) sending a notification of the registration of the UPF 302, and (3) receiving heartbeats from the UPF 302 providing status updates of the UPF 302. In an embodiment, the network repository function 106 communicates with the network session element 122 via the communication interface 720 to: (1) receive a UPF request from the network session element 122, (2) send information related to one or more UPFs to the network session element 122, and (3) send a notification related to a new UPF registered with the NRF 106. It should be noted that the network repository function 106 provides services, such as registration, deactivation, update, to other NFs in the 5G communication system, which are not explained herein.

[0091] In one embodiment, the communication interface 720 includes a transceiver for wirelessly transmitting or receiving information to or from the network session element 122 or other network NFs 102, 104, 108, 110, 112, 114, 116, 118, 120, 122, 124, 126, and 128. In another embodiment, the communication interface 720 can facilitate operational communication with the NFs 102, 104, 108, 110, 112, 114, 116, 118, 120, 122, 124, 126, and 128 and cloud servers using application programming interface (API) calls. The communication can be achieved through a communication network.

[0092] The processor 702 can process a registration request to register a UPF with the network repository element 106. For example, the processor 702 is configured to receive one or more attributes related to a UPF specified in the UpfInfo, validate the registration request, and store a UPF profile having the one or more attributes in the database 710. When the network repository element 106 receives a UPF request including a service type, the processor 702 can access the database 710 to retrieve one or more UPF profiles of one or more UPFs associated with the service type. In this process, the processor 702 excludes a suspended UPF identified based on a status of each UPF and transmits information related to the one or more UPFs (i.e., the one or more UPF profiles) to the network session element 122 via the communication interface 720. The method for user plane function selection by the network repository element 106 is illustrated and explained below with reference to Figure 8

[0093] Figure 8 is a flow diagram illustrating a method 800 for service type based user plane function selection for a packet data unit (PDU) session according to embodiments of the disclosure. The method 800 depicted in the flow diagram can be performed, for example, by the network repository element 106. The operations of the flow diagram, as well as combinations of operations in the flow diagram, can be implemented by, for example, hardware associated with the execution of software including one or more computer program instructions, firmware, a processor, circuitry, and / or distinct devices. The operations of the method 800 are described herein with respect to the processor 702 embodied in the network repository element 106. It should be noted that the operations of the method 800 can be described and / or practiced with one or more processors of other systems / devices than the network repository element 106, for example, different network elements communicably coupled with the network session element 122 (i.e., the NFs 102, 104, 108-128). The method 800 begins at operation 802.

[0094] ​At operation 802 of the method 800, a UPF request to detect one or more UPFs from a plurality of UPFs registered with the network repository element 106 is received by a network repository element (such as the network repository element 106 or the network element 200) from the network session element 122. The UPF request includes at least a UPF service type. The network repository element 106 references Figures 2 to 5 , and Figure 7 to illustrate and explain.

[0095] At operation 804 of the method 800, one or more UPFs from the plurality of UPFs are identified based on the UPF service type. Identifying one or more UPFs from the plurality of UPFs references Figure 4 described by the messages and are not explained again here for brevity.

[0096] At operation 806 of the method 800, information related to the one or more UPFs is sent to the network session element 122. The network session element 122 is configured to identify a UPF from the one or more UPFs based on the information and one or more selection parameters for facilitating a packet data unit (PDU) session.

[0097] The sequence of operations of the method 800 need not necessarily be performed in the same order as presented. Furthermore, one or more operations can be combined together and performed in the form of a single step, or an operation can have several sub-steps which can be performed in parallel or sequentially.

[0098] Reference is made to Figure 8 the disclosed method, or to Figures 2 to 4 the explained one or more operations of the network session element 122 can be implemented using software including computer-readable instructions stored on one or more computer-readable media (e.g., a non-transitory computer-readable medium such as one or more optical discs, a volatile memory component (e.g., DRAM or SRAM), or a non-volatile memory or storage component (e.g., a hard-disk drive or solid-state non-volatile memory component such as a flash component)) and executed on a computer (e.g., any suitable computer such as a laptop computer, notebook computer, network book, tablet computing device, smart phone, or other mobile computing device). For example, such software can be executed on a single local computer.

[0099] Further, one or more computer-readable storage media can be used to implement embodiments consistent with the present disclosure. A computer-readable storage medium refers to any physical memory on which information or data can be stored. Thus, a computer-readable storage medium can store instructions for execution by one or more processors including instructions for causing a processor or processors to perform one or more steps or stages consistent with the embodiments described herein. The term "computer- readable medium" should be understood to include tangible items and exclude carrier waves and transient signals, i.e., non-transitory. Examples include random access memory (RAM), read-only memory (ROM), volatile memory, non-volatile memory, hard drives, CD (compact disc) ROM, DVD, flash drives, disks, and any other known physical memory storage.

[0100] In an embodiment, a network repository element 106 is disclosed. The network repository element 106 includes a memory 704 and a processor 702. The memory 704 is configured to store instructions 705 and a plurality of user plane functions (UPFs) registered with the network repository element 106. The processor 702 is configured to execute the instructions 705 stored in the memory 704 to receive, from a network session element 122, a UPF request for detecting one or more UPFs from the plurality of UPFs. The UPF request includes at least a UPF service type. The processor 702 is configured to identify the one or more UPFs from the plurality of UPFs based on the UPF service type. The processor 702 is configured to send, to the network session element 122, information related to the one or more UPFs. The network session element 122 is configured to identify a UPF from the one or more UPFs based on the information and one or more selection parameters for facilitating a packet data unit (PDU) session.

[0101] In an embodiment, the processor 702 is configured to receive a registration request from a UPF. The registration request includes one or more UPF service types. The processor 702 registers the UPF with the one or more UPF service types based on the registration request.

[0102] In an embodiment, the processor 702 is configured to receive the UPF request from the network session element 122 in response to a PDU session request from a user equipment 140. In another embodiment, the processor 702 is configured to receive the UPF request as part of a subscription for a UPF for at least one service type.

[0103] In an embodiment, the processor 702 is configured to send a notification related to a new UPF registered with at least one service type based on a subscription of the network session element 122.

[0104] In an embodiment, the processor 702 is further configured to determine suspended UPFs based on a status of each UPF to identify the one or more UPFs.

[0105] In an embodiment, the UPF service type is an information element in the Upflnfo.

[0106] In an embodiment, the network session element 122 includes a session management function (SMF) and a packet data network gateway control (PGW-C).

[0107] In another embodiment, a method is disclosed. The method includes receiving, by a network repository element 106 from a network session element 122, a UPF request for detecting one or more UPFs from a plurality of UPFs registered with the network repository element 106. The UPF request includes at least a UPF service type. The method includes identifying, by the network repository element 106, the one or more UPFs from the plurality of UPFs based on the UPF service type. The method includes sending, by the network repository element 106 to the network session element 122, information related to the one or more UPFs. The network session element 122 is configured to identify a UPF from the one or more UPFs based on the information and one or more selection parameters for facilitating a packet data unit (PDU) session.

[0108] In an embodiment, the UPF request is received from the network session element 122 in response to a PDU session request from a user equipment 140. In another embodiment, the UPF request is received from the network session element 122 as part of a subscription for UPFs of at least one service type.

[0109] In an embodiment, the method includes sending, by the network repository element 106, a notification related to a new UPF registered with at least one service type based on a subscription of the network session element 122.

[0110] In an embodiment, the method includes determining, by the network repository element 106, suspended UPFs based on a status of each UPF to identify the one or more UPFs.

[0111] In yet another embodiment, a system is disclosed. The system includes a network repository element 106 and a network session element 122. The network repository element 106 stores a plurality of user plane functions (UPFs) registered with the network repository element 106. The network repository element 106 is communicatively coupled with the network session element 122. The network repository element 106 is configured to receive a UPF request for detecting one or more UPFs from the plurality of UPFs. The UPF request includes at least a UPF service type. The network repository element 106 is configured to identify the one or more UPFs from the plurality of UPFs based on the UPF service type. The network repository element 106 is configured to send information related to the one or more UPFs to the network session element 122. The network session element 122 is configured to identify a UPF from the one or more UPFs based on the information and one or more selection parameters for facilitating a packet data unit (PDU) session.

[0112] In an embodiment, the network repository element 106 is configured to receive a registration request from a UPF. The registration request includes one or more UPF service types. The network repository element 106 registers the UPF with the one or more UPF service types based on the registration request.

[0113] In an embodiment, the network repository element 106 is configured to receive the UPF request from the network session element 122 in response to a PDU session request from a user equipment 140. In another embodiment, the network repository element 106 is configured to receive the UPF request as part of a subscription for a UPF for at least one service type.

[0114] In an embodiment, the network repository element 106 is configured to send a notification related to a new UPF registered with at least one service type based on a subscription with the network session element 122.

[0115] In an embodiment, the network repository element 106 is further configured to determine a suspended UPF to identify the one or more UPFs from the plurality of UPFs based on a status of each UPF in a set of UPFs associated with the at least one service type.

[0116] Various embodiments of the present disclosure provide many advantages. Embodiments of the present disclosure enable service type based user plane function selection for packet data unit session. Introducing attributes at registration to indicate one or more service types of a UPF ensures that the UPF profile is updated by service type and provides an option to discover UPF based on the service type of the UPF required for a user or a PDU session. Such dedicated UPFs for various functions / applications such as immersive media, IoT, international roaming services, etc. ensure improved service for the user while keeping the resource requirements of the application. Further, each UPF can be associated with more than one service type, enabling flexible and efficient use of UPFs for managing PDU sessions. Further, non-operational suspended UPFs are identified and are not provided for initiating PDU sessions, which reduces the latency of establishment of PDU sessions. Further, the network repository element 106 identifies and selects a UPF for a PDU session based on the attribute service type indicated in the UPF request, which significantly enhances the user experience and enhances the QoS provided to the user. Generally, when dedicated UPFs are used based on the service type requirements of the UE 140 for each PDU session, packet processing and traffic management is enhanced, which provides a seamless experience for the users of the 5G communication system.

[0117] Those skilled in the art will appreciate that, in general, the terms used herein are generally "open-ended" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be understood as "having at least," the term "including" should be interpreted as "including but not limited to," etc.). For example, to help with understanding, the DETAILED DESCRIPTION can contain the use of introductory phrases such as "at least one" and "one or more" to introduce a statement. However, the use of such phrases should not be interpreted as implying that the statement that is introduced by the indefinite article "a" or "an" will contain only one such statement of the description that is introduced by such introductory phrases, even if the introductory phrase "one or more" or "at least one" and the indefinite article (such as "a" and "an") are included in the statement; the same rule holds for the use of the definite article for introducing such statements. In addition, even if a particular part of the description statement that is introduced is explicitly recited, those skilled in the art will recognize that such a statement should generally be interpreted to mean at least the number of the statement (e.g., a bare statement of "two statements" without other modifiers generally means at least two statements or two or more statements).

[0118] While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.

Claims

1. A network repository element, comprising: a memory configured to store instructions and a plurality of user plane functions (UPFs) registered with the network repository element; and a processor configured to execute the instructions stored in the memory to: receive, from a network session element, a UPF request for detecting one or more UPFs from the plurality of UPFs, wherein the UPF request includes at least a UPF service type; identify the one or more UPFs from the plurality of UPFs based on the UPF service type; and send, to the network session element, information related to the one or more UPFs, wherein the network session element is configured to identify a UPF from the one or more UPFs based on the information and one or more selection parameters for facilitating a packet data unit (PDU) session.

2. The network repository element of claim 1, wherein the processor is configured to: receive a registration request from a UPF, wherein the registration request includes one or more UPF service types; and register the UPF with the one or more UPF service types based on the registration request.

3. The network repository element of claim 1, wherein the processor is configured to receive the UPF request from the network session element in response to a PDU session request from a user equipment.

4. The network repository element of claim 1, wherein the processor is configured to receive the UPF request as part of a subscription for at least one service type for a UPF.

5. The network repository element of claim 1, wherein the processor is configured to: send a notification related to a new UPF registered with the at least one service type based on the subscription of the network session element.

6. The network repository element of claim 1, wherein the processor is further configured to: determine suspended UPFs based on a status of each UPF to identify the one or more UPFs.

7. The network repository element of claim 1, wherein the UPF service type is an information element in Upflnfo.

8. The network repository element of claim 1, wherein the network session element comprises a session management function (SMF) and a packet data network gateway control (PGW-C).

9. A method, comprising: receiving, by a network repository element from a network session element, a UPF request for detecting one or more UPFs from a plurality of UPFs registered with the network repository element, wherein the UPF request includes at least a UPF service type; identifying, by the network repository element, the one or more UPFs from the plurality of UPFs based on the UPF service type; and sending, by the network repository element to the network session element, information related to the one or more UPFs, ​ wherein the network session element is configured to identify a UPF from the one or more UPFs for facilitating a packet data unit (PDU) session based on the information and one or more selection parameters.

10. The method of claim 9, comprising: receiving, by the network repository element, a registration request from a UPF, wherein the registration request comprises one or more UPF service types; and registering, by the network repository element, the UPF with the one or more UPF service types based on the registration request.

11. The method of claim 9, wherein the UPF request is received from the network session element in response to a PDU session request from a user equipment.

12. The method of claim 9, wherein the UPF request is received from the network session element as part of a subscription for UPFs for at least one service type.

13. The method of claim 9, further comprising: sending, by the network repository element, a notification related to a new UPF registered with the at least one service type based on the subscription of the network session element.

14. The method of claim 9, further comprising: determining, by the network repository element, suspended UPFs based on a status of each UPF to identify the one or more UPFs.

15. A system comprising: a network session element; and a network repository element storing a plurality of user plane functions (UPFs) registered with the network repository element, wherein the network repository element is communicably coupled with the network session element and configured to: receive a UPF request for detecting one or more UPFs from the plurality of UPFs, wherein the UPF request comprises at least a UPF service type; identify the one or more UPFs from the plurality of UPFs based on the UPF service type; and send information related to the one or more UPFs to the network session element, wherein the network session element is configured to identify a UPF from the one or more UPFs for facilitating a packet data unit (PDU) session based on the information and one or more selection parameters.

16. The system of claim 15, wherein the network repository element is configured to: receive a registration request from a UPF, wherein the registration request comprises one or more UPF service types; and register the UPF with the one or more UPF service types based on the registration request.

17. The system of claim 15, wherein the network repository element is configured to receive the UPF request from the network session element in response to a PDU session request from a user equipment.

18. The system of claim 15, wherein the network repository element is configured to receive the UPF request as part of a subscription for UPFs for at least one service type.

19. The system of claim 15, wherein the network repository element is configured to: based on the subscription to the network session element, sending a notification related to a new UPF registered with the at least one service type.

20. The system of claim 15, wherein the network repository element is further configured to: determine suspended UPFs based on a status of each UPF in a set of UPFs associated with the at least one service type to identify the one or more UPFs from the plurality of UPFs.

Images