User plane feature selection based on service type for packet data unit sessions

Abstract

Embodiments of this disclosure disclose user plane feature selection based on service type for packet data unit (PDU) sessions. A network repository element (106) receives a UPF request from a network session element (122) to discover one or more UPFs from a plurality of UPFs. The UPF request includes at least a UPF service type. The network repository element (106) is configured to identify one or more UPFs from a plurality of UPFs based on the UPF service type. The network repository element (106) is configured to transmit information related to one or more UPFs to the network session element (122). The network session element (122) is configured to identify one UPF from one or more UPFs based on the information and one or more selection parameters to facilitate a packet data unit (PDU) session.

Description

Technical Field

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

Background Art

[0002] Modern communication systems such as 5G mobile communication technologies have brought about a revolution in various industries due to their improved speed, reduced latency, and enhanced reliability. 5G mobile communication technologies have a mobile core infrastructure specified by the New Radio (NR) of the 3rd Generation Partnership Project (3GPP (registered trademark)), which separates the functions of the packet data network gateway (PGW) between the control plane and the user plane. Such a split architecture of the PGW in the 5G core network enables independent scalability, evolution, and flexible deployment of the user plane and the control plane. In 3GPP specifications, the PGW user plane function is also called the user plane function (UPF) that functions as an anchor point for packet data unit (PDU) data sessions. Generally, a user equipment (UE) needs to access the UPF of the 5G core network through a radio access network (RAN) so as to access a data network (DN). Therefore, an important aspect when establishing a PDU data session is the selection of the UPF for accessing the 5G core network. Usually, the selection of the UPF is performed by the control plane based on various information including location, service, function, and load. More specifically, network elements such as the session management function (SMF) of the 5G core network obtain information of one or more UPFs and select one or more UPFs to facilitate the PDU session.

[0003] In view of the above discussion, it is necessary to identify a UPF for efficiently promoting a PDU session that improves the user's mobile Internet experience.

[0004] The information disclosed in this background section of the disclosure is intended solely to enhance the understanding of the general background of the disclosure and should not be construed as an endorsement or any suggestion of forming prior art already known to those skilled in the art. [Overview of the project] [Means for solving the problem]

[0005] Generally, the User Plane Function (UPF) selection function of a Session Management Function (SMF) can discover UPF instances using the Network Repository Function (NRF). However, some SMFs may require a specific UPF or group of UPFs for certain applications or types of subscribers.

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

[0007] In another embodiment, a method is disclosed. This method includes the step of a network repository element receiving a UPF request from a network session element in order to discover one or more UPFs from a plurality of UPFs registered with the network repository element. The UPF request includes at least a UPF service type. This method includes the step of the network repository element identifying one or more UPFs from a plurality of UPFs based on the UPF service type. This method includes the step of the network repository element transmitting information related to one or more UPFs to the network session element. The network session element is configured to identify UPFs from one or more UPFs based on that information and one or more selection parameters to facilitate a packet data unit (PDU) session.

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

[0009] The above-described outline of the invention is illustrative and not intended to be limiting. Further embodiments, features, and characteristics will become apparent by referring to the drawings and the following "Modes for Carrying Out the Invention," in addition to the exemplary aspects, embodiments, and features described above.

[0010] The accompanying drawings incorporated in this disclosure and constituting part of this disclosure illustrate exemplary embodiments and, together with the description, help to illustrate the disclosed principles. The same numbers are used throughout the drawings to refer to similar features and components. Hereinafter, several embodiments of devices and / or methods according to embodiments of the subject matter are described, merely as examples, with reference to the accompanying drawings. [Brief explanation of the drawing]

[0011] [Figure 1] This is a schematic diagram of a 5G communication system architecture in which several embodiments of the present disclosure may be implemented.

[0012] [Figure 2] This figure shows network elements for selecting user plane functionality based on the service type of a packet data unit (PDU) session, according to one embodiment of the present disclosure.

[0013] [Figure 3] This is a sequence flow diagram illustrating a method for registering a user plane function (UPF) in a network repository element according to one embodiment of the present disclosure.

[0014] [Figure 4] This is a sequence flow diagram illustrating a method for identifying user plane functions (UPFs) to facilitate a packet data unit (PDU) session, according to one embodiment of the present disclosure.

[0015] [Figure 5]This is a sequence flow diagram illustrating an exemplary method for identifying one or more user plane functions (UPFs) from a plurality of UPFs based on UPF service type international roaming, according to one embodiment of the present disclosure.

[0016] [Figure 6] This figure shows a network session element for service type-based user plane function (UPF) selection for a packet data unit (PDU) session, according to one embodiment of the present disclosure.

[0017] [Figure 7] This figure shows a network repository element for service type-based user plane function (UPF) selection for a packet data unit (PDU) session, according to one embodiment of the present disclosure.

[0018] [Figure 8] This flowchart shows a method for selecting a user plane function (UPF) based on the service type for a packet data unit (PDU) session, according to one embodiment of the present disclosure. [Modes for carrying out the invention]

[0019] Those skilled in the art will understand that all block diagrams in this specification represent conceptual diagrams of exemplary systems embodying the principles of this subject matter. Similarly, it will be understood that any flowcharts, flow charts, state transition diagrams, and pseudocode, whether or not a computer or processor is explicitly indicated, represent various processes that can be substantially represented in a computer-readable medium and executed by a computer or processor.

[0020] As used herein, the word "exemplary" is used in the sense of "serving as an example, instance, or illustration". Any embodiment or implementation of the subject matter described herein as "exemplary" should not necessarily be construed as being more preferred or advantageous than other embodiments.

[0021] Although the present disclosure is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will be described in detail below. However, it is not intended to limit the present disclosure to the specific forms disclosed, and on the contrary, it should be understood that the present disclosure is intended to cover all modifications, equivalents, and alternative forms within the spirit and scope of the present disclosure.

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

[0023] In the following "Modes for Carrying Out the Invention" of embodiments of the present disclosure, reference is made to the accompanying drawings which form a part of this specification and illustrate specific embodiments by which the present disclosure can be practiced. These embodiments are described in sufficient detail so that those skilled in the art can practice the present disclosure, and it should be understood that other embodiments can be utilized and changes can be made without departing from the scope of the present disclosure. Therefore, the following description should not be construed in a limiting sense.

[0024] For the sake of clarity, this disclosure uses the terms and names defined in the Third Generation Partnership Project Radio Access Network (3GPP RAN) standard. More specifically, the terms “service-based architecture,” “service-based interface,” “service level agreement (SLA) standard,” “non-public network (NPN),” “packet data network gateway,” “packet data unit session,” and “data network” should be interpreted as specified in the 3GPP RAN standard.

[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, one or more UPFs are selected from a group of UPFs based on at least the service type. In one embodiment, the service type may be specified by a Session Management Function (SMF). In one example, the SMF may specify the service type based on at least the user equipment requesting access to the data network (DN). In another embodiment, the SMF may specify one or more service types of UPFs for storing UPF profiles. UPF function selection based on service type will be described in detail with reference to Figures 1 to 8.

[0026] Figure 1 shows a schematic architecture 100 of a 5G communication system in which several embodiments of the present disclosure may be implemented. Architecture 100 uses a cloud-aligned services-based architecture (SBA) to support authentication, security, session management, and traffic aggregation from connected devices, all of which require complex interconnection of network functions forming the 5G core.

[0027] Therefore, the 5G core includes multiple interconnected network functions as defined by 3GPP to provide control plane and user plane functions for the 5G communication system. Generally, multiple interconnected network functions (NFs) are interconnected network functions, each with other NFs authorized to access the services of other NFs. These multiple network functions (or NFs) will henceforth be referred to interchangeably as “Network Element” throughout this disclosure. Furthermore, for the purposes of this disclosure, the term “NF Network Repository Function” will be interchangeable with “NRF” or “Network Repository Element,” and the term “Session Management Function” will, in this specification, be interchangeable with “SMF” or “Network Session Element” throughout this disclosure.

[0028] The 5G communication system architecture 100 includes a network slicing 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"), integrated 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"), and a session management function 122 (referred to herein as "SMF 110") The diagram illustrates 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, as well as the functions of these network elements, which are defined by 3GPP standards and are not described 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] User equipment 140 (hereinafter referred to as "UE 140") is configured to connect to a 5G core, which includes multiple network elements 102-128, via a radio access network (RAN) 142. Examples of UE 140 include, but are 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, and the Internet of Things (IoT) with 5G capabilities. Thus, UE 140 is configured to connect to a data network 144 (hereinafter also referred to as "DN 144"), which can be accessed by operator services, third-party services, etc. An example of DN 144 is the internet. The AMF 120 serves as a single entry point for UE 140 to connect to the 5G core.

[0030] As shown in Figure 1, each of the multiple network elements 102 to 128 exposes its respective function through a service-based interface (SBI). For example, NSSF 102 exposes its functions via the Nnssf interface, NEF 104 exposes its functions via the Nnef interface, NRF 106 exposes its functions via the Nnrf interface, PCF 108 exposes its functions via the Npcf interface, UDM 110 exposes its functions via the Nudm interface, AF 112 exposes its functions via the Naf interface, EASDF 114 exposes its functions via the Neasdf interface, NSSAAF 116 exposes its functions via the Nnssaaf interface, AUSF 118 exposes its functions via the Nausf interface, AMF 120 exposes its functions via the Namf interface, SMF 122 exposes its functions via the Nsmf interface, SCP 124 exposes its functions via the Nscp interface, NSACF 126 exposes its functions via the Nnsacf interface, and NWDAF 128 exposes its functions via the Nnwdaf interface.

[0031] Furthermore, N1 is the interface between UE 140 and AMF 120, N2 is the interface between Radio Access Network (RAN) 142 (i.e., gNodeB) and AMF 120, N3 interface performs the role of transporting user data from RAN 142 to UPF 130, N4 interface is a bridge between the 5G core control plane and user plane, N6 interface provides connectivity between UPF 130 and 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 the interface between two UPFs (i.e., intermediate I-UPF and UPF session anchor).

[0032] UE 140 needs to access UPF 130 of the 5G core network via RAN 142 in order to access DN 144. Therefore, to establish a PDU session, selection of UPF 130 is necessary to access the 5G core network. After accessing the 5G core network, there are several ways for UE 140 to select UPF to access DN 144.

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

[0034] In an exemplary scenario, a user of a 5G communication system may be an enterprise subscriber to services available through a UE 140. Thus, the UE 140 may be qualified to enable connectivity and advanced functionality. In some cases, the UE 140 may have the option to transmit media content, including promotional offers, for real-time display on a receiving mobile device (i.e., a current or future enterprise customer). In another exemplary scenario, the user may be an Internet of Things (IoT) subscriber in a 5G communication system. Thus, the UE 140 associated with the user may require services with ultra-high reliability and low latency. In such a scenario, a dedicated UPF to support such services for the user may be beneficial. In other cases, a framework that allows dedicated UPF resources to be allocated to specific services or specific subscribers or subscriber groups (e.g., to enable service independence and isolation) may be beneficial. Typically, a UPF may be selected based on one or more selection parameters such as the UPF's dynamic load, UPF location, UPF's relative static capacity, UPF service location, service type, and resource specifications. However, user requirements for specific services do not influence the selection of a UPF.

[0035] Various embodiments of this disclosure disclose techniques for UPF selection based on the service type of a packet data unit session. More specifically, a UPF indicates one or more service types while registered with NRF 106. Thus, when a request for a UPF of a particular service type is received from SMF 122, one or more UPFs from multiple UPFs registered with NRF 106 are identified. Furthermore, NRF 106 transmits information related to one or more UPFs to SMF 122. SMF 122 identifies a UPF from one or more UPFs based on this information and one or more selection parameters to facilitate the PDU session of UE 140. Furthermore, NRF 106 identifies one or more UPFs by identifying suspended UPFs based on the status of each UPF, thereby ensuring that no suspended UPFs are provided to the PDU session. Such technologies that provide service-type specific UPFs improve the overall user experience because such UPFs are equipped to support user requirements such as reduced latency, faster processing, energy efficiency, improved data rates, and quality of service (QoS) based on the application, as further explained with reference to Figures 2-8.

[0036] Figure 2 shows a network element 200 for UPF selection based on service type for a packet data unit session according to one embodiment of the present disclosure. As used herein, the term “service type” refers to a category of services that may be provided by a UPF. More specifically, each UPF may be suitable for providing one or more specific services based on the available resources of the corresponding UPF. Thus, each service type may depend on one or more of the following: application type, number of users, UE mobility, latency requirements, 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 operators (MNOs), mobile virtual network operators (MVNOs), satellite, over-the-top (OTT) based application services, private 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, a service type could be an immersive game (e.g., augmented reality, virtual reality, etc.) that requires high data rates and low latency, which can be supported by a specific UPF among all UPFs registered with NRF 106 by the subscriber. In another example, a service type could be an IoT where an IoT subscriber requires a service that is ultra-reliable and low latency. Such a service type can be used for dedicated UPF selection to enable a specific service level architecture. The service type of a UPF is defined as an attribute information element of UpfInfo.

[0037] In one embodiment, the network element 200 is a network session element 122. The network session element 122 may be configured to perform the functions of the SMF 122 shown in Figure 1. In one exemplary embodiment, the network session element 122 is referred to as the session management function 122 or SMF 122. In another embodiment, the network element 200 is a network repository element 106. The network repository element 106 may be configured to perform the functions of the NRF 106 shown in Figure 1. In one exemplary embodiment, the network repository function 106 is referred to as the network repository element 106 or NRF 106. In yet another embodiment, the network element 200 is a system that embodies the functions of the SMF 122 and NRF 106.

[0038] As already described, the network element 200 embodies one or more network functions and is interconnected with other NFs 102-128 of the 5G core network for UPF selection based on the service type for PDU sessions in architecture 100. The network element 200 can perform one or more of the operations described herein. It should be noted that embodiments of this disclosure are described herein with reference to a 5G communication system. However, it will be apparent to those skilled in the art that the techniques employed by the network element 200 for UPF selection based on the service type of a PDU session, as described herein, can be applied to other communication systems, such as communication systems employing SBAs. Accordingly, the network element 200 may be a centralized or distributed server configured to perform one or more functions of the SMF 122 and / or NRF 106 described herein.

[0039] The network element 200 is shown to include a processor 202, memory 204, input / output module 206, and communication interface 208. Note that in some embodiments, the network element 200 may include more or fewer components than those shown herein. Various components of the network element 200 may be implemented using hardware, software, firmware, or any combination thereof. Furthermore, various components of the network element 200 may be operably coupled to one another. More specifically, various components of the network element 200 may be able to communicate with one another using a communication channel medium (e.g., bus, interconnect, etc.). In one embodiment, the functions of NRF 106 and SMF 122 may be embodied within the processor 202. Note that the processor 202 may include fewer or more modules than those described herein.

[0040] In one embodiment, the processor 202 may be embodied as a multicore processor, a single-core processor, or a combination of one or more multicore processors and one or more single-core processors. For example, the processor 202 may be embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), processing circuits with or without an associated DSP, or various other processing devices including a microcontroller unit (MCU), a hardware accelerator, a dedicated computer chip, etc.

[0041] In one embodiment, memory 204 can store machine-executable instructions, referred to herein as instructions 205. In one embodiment, processor 202 is embodied as an execution unit for software instructions. Thus, processor 202 can execute instructions 205 stored in memory 204 to perform one or more operations described herein.

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

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

[0044] In one embodiment, when the network element 200 is a network repository element (i.e., NRF 106), the processor 202 is configured to execute instructions 205 to: (1) receive a registration request from a UPF; (2) register a UPF with one or more UPF service types; (3) receive a UPF request from a network session element 122 (i.e., SMF 122) to discover one or more UPFs; (4) determine suspended (suspended) UPFs based on the 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 type; (6) send information relating to one or more UPFs to the network session element 122; and (7) send a notification relating to a new UPF registered with the NRF 106. In one embodiment, when the network element 200 is a network session element 122 (i.e., SMF 122), the processor 202 is configured to execute an instruction 205 to (1) send a UPF request to the network repository element 106 to find one or more UPFs, (2) receive information related to one or more UPFs from the network repository element 106, and (3) identify a UPF from one or more UPFs based on the information and one or more selection parameters to facilitate a PDU session.

[0045] In one embodiment, the I / O module 206 may include a mechanism configured to receive input from an operator of a network element 200 (not shown in the figure) and to provide output to the operator. As used herein, the term “operator of network element 200” may refer to one or more individuals, e.g., an operator or service provider, directly or indirectly associated with the management of a 5G communication system. To enable the reception of input and to provide output to the network element 200, the I / O module 206 may include at least one input interface and / or at least one output interface. Examples of input interfaces may include, but are not limited to, a keyboard, mouse, joystick, keypad, touchscreen, soft key, microphone, etc. Examples of output interfaces may include, but are not limited to, a display such as a light-emitting diode display, thin-film transistor (TFT) display, liquid crystal display, active-matrix organic light-emitting diode (AMOLED) display, microphone, speaker, ringer, etc.

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

[0047] In one embodiment, the communication interface 208 may receive registration requests from a UPF for registration with the network repository element 106. The registration request includes one or more UPF service types. In one example, a UPF may indicate service types as international roaming and premium streaming media. The service type attribute is part of the UpfInfo sent with the registration request. Such a technique of indicating the UPF service type 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 its service type. In addition, UPFs of a particular service type can be efficiently retrieved from the network repository element 106 when a UPF request is received from another network element (i.e., the session management element 122). In one embodiment, the communication interface 208 may also receive UPF requests from the network session element 122 for one or more UPFs from a plurality of UPFs stored in the network repository element 106. The UPF request includes at least one 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 one embodiment, a UPF request may be received as part of a subscription to at least one service type of UPF. A subscription to receive information on UPFs of a particular service type allows for the periodic receipt of dedicated UPFs of that service type, or when new UPFs register for the specified service type. In another embodiment, a UPF request may be received in response to a PDU session request from UE 140. Since a PDU session may be associated with a particular service type, a UPF request including the service type ensures that the appropriate UPF is provided to facilitate the PDU session.For example, if a PDU session is related to media streaming and the UPF request includes the service type of UPF required for the PDU session (e.g., media streaming), then the UE 140 will be provided with a UPF that best supports such a service.

[0048] Network element 200 is configured to communicate operationally with database 220. In one embodiment, database 220 is configured to store UPF registration policies for registering one or more UPFs with network repository element 106. Furthermore, database 220 stores multiple UPF profiles associated with multiple UPFs. A UPF profile includes one or more parameters associated with a UPF, such as the dynamic load of the UPF, the location of the UPF, the relative static capacity (capacity) of the UPF, the UPF service location, the service type, and resource specifications. In one embodiment, database 220 may also store subscription information received from one or more SMFs (e.g., SMF 122). The subscription information includes information associated with at least one particular service type of UPF. This ensures that network repository element 106 (i.e., NRF 106) sends an update when a new UPF of a particular service type requested by NRF 106 is registered with NRF 106. In some embodiments, a subscription may include a request that shares information associated with the UPF registered with NRF 106 along with the service type.

[0049] Database 220 is also configured to store the status of each UPF. The status of a UPF indicates whether the UPF is active or suspended (suspended). If a UPF is registered with NRF 106 but is not operational, its status is suspended. More specifically, if a UPF has not updated its profile for a configurable amount of time (i.e., longer than the heartbeat interval), NRF 106 changes the status of the UPF to suspended. If a UPF is operational, its status is active so that it can be discovered by other NFs (i.e., SMF 122). These multiple UPFs may be registered with NRF 106 to anchor PDU sessions. In one embodiment, database 220 also includes one or more predefined rules for selecting a UPF for a PDU session. More specifically, these predefined rules indicate various values ​​for each of one or more selection parameters used to select a UPF for a PDU session. Some examples of selection parameters include, but are not limited to, the dynamic load of the UPF, UPF load forecasting, UPF location, UPF relative static capacity, UE location information, required capabilities 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 requirements, and access traffic steering, switching and splitting (ATSSS) steering capabilities for the PDU session. For example, a predefined rule might specifically indicate network resources / parameters that may be key requirements for a PDU session. An example of a predefined rule for selecting a UPF from a set of UPFs with a particular service type might be to select a UPF that can serve a UE with a premium subscription at location "x" with a PDU session spanning two hours of immersive video, and that can support a data rate of "y" Mbps.The predefined rules described above are for illustrative purposes only, and it should be noted that database 220 may have multiple predefined rules with different constraints / thresholds specified for selection parameters (i.e., network resources / parameters) in order to optimally select UPF for PDU sessions.

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

[0051] In some embodiments, the database 220 is integrated within the network element 200. For example, the network element 200 may include one or more hard disk drives as the database 220. In other embodiments, the database 220 may be external to the network element 200 and accessed by the network element 200 using a storage interface (not shown in Figure 2). The storage interface is any component that can provide the processor 202 with access to the database 220. The storage interface may 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.

[0052] As previously described, the communication interface 208 is configured to receive registration requests from the UPF for registration with the network repository element 106. In addition, the communication interface 208 is also configured to receive UPF requests from the network session element 122. The receipt of registration requests from the UPF before the receipt of the UPF request is described herein for illustrative purposes only, and it should be noted that the UPF registration request may be received at a later time after the receipt of the UPF request. The communication interface 208 is configured to forward the registration requests from the UPF to the processor 202. The processor 202 is configured to process the registration requests in conjunction with instructions 205 stored in memory 204 and to perform one or more functions as described herein. The processing of UPF requests will be described later with reference to Figure 4. Referring to Figure 3, a sequence flow diagram showing the registration of the UPF to the network repository element 106 will be shown and described next.

[0053] Figure 3 shows a sequence flow diagram representing a method 300 for registering a UPF 302 with a network repository element 106 according to one embodiment of the present disclosure. Each UPF instance can register, update, or unregister their profiles with the network repository element 106. Thus, each UPF registers its UPF profile with the network repository element 106, along with a list of services provided by the UPF.

[0054] In 302, a registration request is received from UPF 302. The registration request includes one or more UPF service types. More specifically, the registration request includes the UPF profile of UPF 302. Generally, the UPF profile includes one or more informational elements, such as one or more attributes. For example, attributes such as a list of parameters supported by the UPF for each SNSSAI, one or more SMF areas that UPF 302 can service, a list of user plane interfaces configured on UPF 302, PDU session types supported by the UPF, and one or more service types. Note that the attributes disclosed in the UPF profile are for illustrative purposes only, and the UPF profile may include fewer or more attributes, such as general parameters related to dynamic load capacity, interaction with EPS functions, UPF relative static capacity, etc.

[0055] In one embodiment, one or more attributes are information elements of UpfInfo. Therefore, a UPF service type is an information element of UpfInfo. Some examples of UPF service types include, but are not limited to, international roaming, corporate services, enterprise services, Internet of Things (IoT), immersive gaming, and live streaming media content subscribers. It should be noted that the examples of UPF services described herein are for illustrative purposes only, and different types of UPF service types may be defined on an ad-hoc basis to suit multiple applications as specified by the 3GPP standard. For example, a category of subscriber, such as a government or defense agency, may require a secure UPF dedicated to their services, and therefore a UPF may be defined to support such a service type.

[0056] In one embodiment, UPF 302 may support one or more service types. For example, UPF 302 may be able to support IoT subscribers and live streaming media subscribers. For example, UPF 302 has resources to support low latency, low loss, and high data rate services, and therefore UPF may register for both different service types, namely IoT services and live streaming media services. Thus, both of these service types may be indicated in the corresponding service type information elements of UpfInfo. More specifically, the service type attribute may be added to the UPF NFProfile attribute of UpfInfo as defined in TS 29.510, as shown in Table 1 below. [Table 1]

[0057] Although the data type is specified as a string, it should be noted that any other data type may be used to indicate a UPF 302 service type. For example, if UPF 302 supports two different service types and the data type is a string, a string (e.g., "ab12cd") may be used to represent each of these service types based on a lookup table.

[0058] In 304, the network repository element 106 verifies the registration request for UPF 302.

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

[0060] In 308, the network repository element 106 sends a notification to UPF 302. This notification is an acknowledgment indicating registration in UPF 302.

[0061] In 310, the network repository element 106 sends a status update request to the UPF 302. After the UPF is registered with the network repository element 106, the network repository element 106 may request a status update from the UPF 302 at defined time intervals, for example, every two minutes. Thus, a status update request may be sent from the network repository element 106 to the UPF 302 at defined time intervals. Alternatively, the network repository element 106 sends the first status update request to the UPF 302 to automatically share the status update at defined time intervals. This ensures that the network repository element 106 has a track of the status of the UPF 302.

[0062] In 312, the UPF 302 sends a heartbeat to the network repository element 106. In one embodiment, the heartbeat may be sent in response to a status update request received from the network repository element 106. In another embodiment, the UPF 302 automatically sends a heartbeat at defined time intervals to provide a status update to the network repository element 106. If the UPF 302 is operational, its status is updated to active; if the UPF 302 fails to send a heartbeat, its status is updated to paused. This ensures that a paused UPF is not selected to facilitate a PDU session.

[0063] The sequence of operations in Method 300 does not necessarily have to be performed in the same order as presented. Furthermore, one or more operations may be grouped together and performed in the form of a single step, or one operation may have several substeps that can be performed in parallel or sequentially. Next, with reference to Figure 4, we will describe how to facilitate the PDU session of UE 140.

[0064] Figure 4 is a sequence flow diagram representing a method 400 for identifying a UPF to facilitate a packet data unit (PDU) session, according to one embodiment of the present disclosure. The selection of a UPF for a PDU session is a critical step in ensuring that a seamless experience is provided to the user.

[0065] In 402, the network session element 122 sends a UPF request to the network repository element 106. In one embodiment, the UPF request is sent from the network session element 122 in response to a PDU session request from the UE. For example, if UE 140 requests a PDU session to access information from DN 144, the network session element 122 generates a UPF request. In another embodiment, the UPF request is sent as part of a subscription to at least one service type of UPF. More specifically, the network session element 122 may subscribe to receive information related to the UPF registered with the network repository element 106. In one embodiment, the UPF request includes at least one service type. For example, a UPF request from the network session element 122 may specify the service type as international roaming. Note that a UPF request may include multiple service types, and for example, as part of a subscription, the network session element 122 may send a UPF request that includes the service type, international roaming subscriber, and IoT subscriber. In addition, a UPF request may include additional attributes for the subscription, such as the frequency of receiving UPFs and the conditions associated with the subscription.

[0066] In 404, the network repository element 106 identifies one or more UPFs from a group of UPFs based on the UPF service type. More specifically, it searches for multiple user profiles associated with multiple UPFs registered in the network repository element 106 and identifies a set of UPFs associated with the UPF service type specified in the UPF request. After obtaining the set of UPFs, the network repository element 106 identifies one or more UPFs by determining which UPFs are suspended based on the status of each UPF in the set. Generally, the network repository element 106 stores the status of multiple UPFs in a database, for example, database 220. Thus, UPFs can be active or suspended. Suspended UPFs are excluded, and one or more UPFs that are active and provide the service type specified in the UPF request are identified.

[0067] In 406, the network repository element 106 transmits 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 transmitted to the network session element 122 in response to a UPF request. Note that the above information (i.e., one or more UPF profiles) is transmitted in response to a request from UE 140 for a subscription or PDU session.

[0068] In 408, the network session element 122 identifies a UPF from one or more UPFs based on the above information and one or more selection parameters. Some examples of selection parameters include, but are not limited to, the dynamic load of the UPF, the UPF load forecast, the location of the UPF, the relative static capacity of the UPF, the location information of the UE, the functionality required for the PDU session, the data network name (DNN), the PDU session type, the SSC mode selected for the PDU session, the UE subscription profile, the local operator policy, the access technology used by the UE, the user plane latency requirements, and the access traffic steering, switching and partitioning (ATSSS) steering capability for the PDU session. More specifically, a UPF is selected that provides the user with high QoS and a seamless experience based on the PDU session requirements. Note that if the UPF request is a subscription, information related to one or more UPFs is stored in the database of the network session element 122 (see database 610 in Figure 6). Whenever a request for a PDU session is received, the network session element 122 selects a UPF (i.e., UPF 302) from among one or more UPFs of the service type required for the data session by the UE 140.

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

[0070] In 412, the network repository element 106 sends notifications related to new UPFs registered for at least one service type, based on the subscription of the network session element 122. For example, if the network session element 122 subscribes to receive information related to UPFs registered for the service type international roaming (i.e., user profiles), then after verifying the subscription, information related to one or more UPFs with the service type international roaming may be sent to the network session element 122. In another embodiment, a new UPF may register for the service type international roaming at a later time. In such a scenario, if the new UPF provides the international roaming service type, an update is sent to the network session element 122 along with the user profile.

[0071] Embodiments of this disclosure describe the selection of one or more UPFs based on the service type of the UPF, but it should be noted that a UPF request may include other informational elements specifying parameters / attributes for the selection of one or more UPFs. For example, an SMF area identity may be used to determine whether a UPF can service the area indicated by the SMF area identity. Thus, a UPF may only be selected if it matches all the attributes / parameters specified in the UPF request. Furthermore, it should be noted that the service type of the UPF is used only to select one or more UPFs from the network repository element 106, and the selection of UPFs to facilitate the PDU session of UE 140 may be based on one or more selection parameters.

[0072] The sequence of operations in Method 400 does not necessarily have to be performed in the same order as presented. Furthermore, one or more operations may be grouped together and performed in the form of a single step, or one operation may have several substeps that can be performed in parallel or sequentially. An exemplary scenario demonstrating the identification of one or more UPFs based on a UPF request is shown and explained with reference to Figure 5.

[0073] Figure 5 shows a sequence flow diagram representing an exemplary method 500 for identifying one or more UPFs from a plurality of UPFs based on UPF service type international roaming, according to one embodiment of the present disclosure.

[0074] In 510, UPF 502 registers with the network repository element 106. In this illustrative representation, UPF 502 registers with the international roaming service type in UpfInfo. The process of registering UPF with the network repository element 106 is illustrated with reference to Figure 3 and is not described here for brevity.

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

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

[0077] In 524, the network repository element 106 identifies UPF 502 and 506, which provide international roaming service types.

[0078] In 526, information related to UPFs 502 and 506 is sent to the network session element 122 in response to the UPF request. The network session element 122 selects a UPF from one or more UPFs for the PDU session based on one or more selection parameters, as described with reference to Figure 4. The block diagram representations of the network session element 122 and the network repository element 106 are described below with reference to Figures 6 and 7.

[0079] Figure 6 shows a network session element 122 for user plane function selection based on service type for a packet data unit session, according to one embodiment of the present disclosure. The network session element 122 described herein includes session management function (SMF) and packet data network gateway control (PGW-C) functions, and is shown as SMF 122 in Figure 1. The network session element 122 manages the setup of connectivity of UE 140 to DN 144 and the management of UPF 130 for that connectivity. Generally, the network session element 122 is a control function that manages PDU sessions, including session establishment, modification, and release. The network session element 122 communicates indirectly with UE 140 through AMF 120, which relays session-related messages between UE 140 and the network session element 122.

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

[0081] Through 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. Communication can be achieved through API calls without loss of generality. In one embodiment, the communication interface 620 is an SBI interface which may be an Nsmf. The network session element 122 communicates with one or more network elements of the 5G communication system, such as NFs 102, 104, 106, 108, 110, 112, 114, 116, 118, 120, 124, 126, and 128, through the communication interface 620 for user plane feature selection based on service type. Thus, the network session element 122 interacts with other NFs of the 5G communication system to manage PDU sessions for UEs such as UE 140.

[0082] Memory 604 can be any type of storage accessible to the processor 602 to perform its respective function. For example, memory 604 may include one or more volatile or non-volatile memories, or a combination thereof, for storing instructions 605 for (1) sending a UPF request including at least one service type to the network repository element 106, (2) receiving information related to one or more UPFs from the network repository element 106, (3) identifying one UPF from one or more UPFs based on the information and one or more selection parameters, and (4) facilitating a PDU session for the UE 140 based on the UPF.

[0083] In one embodiment, the I / O interface 608 may include a mechanism configured to receive inputs from and provide outputs to a plurality of peripheral devices such as NF 102-128 of the 5G communication system. Some examples of the I / O interface 608 include, but are not limited to, keyboards, mice, keypads, touchscreens, soft keys, microphones, and displays. The network session element 122 is shown to communicate operably with the database 610. In one embodiment, the database 610 is configured to store session management policies, subscription information, UPF profiles, UPF requests, etc., for managing PDU sessions.

[0084] In one embodiment, memory 604 can store machine-executable instructions, referred to herein as instructions 605. Thus, the processor 202 can execute the instructions 605 stored in memory 604 to perform one or more operations described herein. The processor 602 can process information about one or more UPFs associated with a service type received from the network repository element 106 to identify a UPF from one or more UPFs based on one or more selection parameters to facilitate a PDU session. Furthermore, the processor 602 manages the establishment, modification, and release of PDU sessions to the UE 140, e.g., PDU sessions, by communicating with the AMF 120 via the communication interface 620. A schematic block diagram of the network repository element 106 is shown and described below with reference to Figure 7.

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

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

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

[0088] Memory 704 can be any type of storage accessible to the processor 702. For example, memory 704 may include volatile or non-volatile memory, or a combination thereof. In one embodiment, memory 704 stores multiple UPF profiles associated with multiple UPFs registered in the network repository element 106. In one example, UPFs may be categorized based on their service type and stored in memory 704. More specifically, a service type profile (e.g., Immersive Game UPF, Secure UPF, etc.) may be created for each service type, and a list of UPFs registered for such service types may be added to the corresponding service type profile.

[0089] The database 710 can store and / or retrieve data such as, but is not limited to, UPF registration policies for registering one or more UPFs with the network repository element 106, multiple UPF profiles associated with multiple UPFs, subscription information received from one or more SMFs (e.g., SMF 122), the status of each of the multiple UPFs, a list of suspended UPFs, and one or more predetermined rules for selecting a UPF for a PDU session. Such information can be accessed by the processor 702 using the communication interface 720 to select a UPF based on the service type of the PDU session of the UE 140.

[0090] The network repository element 106 can communicate via the communication interface 720 with one or more network elements of the 5G communication system, such as NF 102, 104, 108, 110, 112, 114, 116, 118, 120, 122, 124, 126, and 128, for user plane function selection based on service type. The communication interface 720 is an SBI interface which may be an Nnrf. In one embodiment, the network repository element 106 communicates with UPF 302 via the communication interface 720 for (1) receiving registration requests from UPF 302 that include one or more service types of UPF 302, (2) sending registration notifications of UPF 302, and (3) receiving heartbeats from UPF 302 that provide status updates for UPF 302. In one embodiment, the network repository element 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) transmit information related to one or more UPFs to the network session element 122, and (3) transmit a notification related to a new UPF registered with the NRF 106. Note that the network repository element 106 also provides services to other NFs of the 5G communication system, such as registration, deactivation, and updating, which are not described herein.

[0091] In one embodiment, the communication interface 720 includes transceivers for wirelessly communicating information to or receiving information from network session element 122 or other networks NF 102, 104, 108, 110, 112, 114, 116, 118, 120, 122, 124, 126, and 128. In another embodiment, the communication interface 720 can use application programming interface (API) calls to facilitate operational communication with NF 102, 104, 108, 110, 112, 114, 116, 118, 120, 122, 124, 126, and NF 128 as well as a cloud server. Communication may be achieved over a communication network.

[0092] The processor 702 can process registration requests to register UPFs with the network repository element 106. For example, the processor 702 is configured to receive one or more attributes related to the UPF specified in UpfInfo, validate the registration request, and store the UPF profile with 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 for one or more UPFs associated with the service type. In this process, the processor 702 excludes suspended UPFs identified based on the status of each UPF and sends information related to one or more UPFs (i.e., one or more UPF profiles) to the network session element 122 via the communication interface 720. Referring to Figure 8, the method for user plane function selection by the network repository element 106 will be shown and explained next.

[0093] Figure 8 is a flowchart of a method 800 for user plane function selection based on the service type of a packet data unit (PDU) session, according to one embodiment of the present disclosure. The method 800 shown in the flowchart may be performed, for example, by a network repository element 106. The operation of the flowchart, and combinations thereof, may be performed, for example, by different devices associated with the execution of hardware, firmware, processors, circuits, and / or software including one or more computer program instructions. The operation of method 800 is described herein with the help of a processor 702 embodied within the network repository element 106. It should be noted that the operation of method 800 may be described and / or performed by using one or more processors of systems / devices other than the network repository element 106, for example, different network elements (i.e., NFs 102, 104, 108-128) communicably coupled with a network session element 122. Method 800 begins in operation 802.

[0094] In operation 802 of method 800, a UPF request is received from the network session element 122 by a network repository element such as the network repository element 106 or network element 200 in order to find one or more UPFs from a plurality of UPFs registered in the network repository element 106. The UPF request includes at least a UPF service type. The network repository element 106 is shown and described with reference to Figures 2 to 5 and Figure 7.

[0095] In operation 804 of method 800, one or more UPFs from a plurality of UPFs are identified based on the UPF service type. Identifying one or more UPFs from a plurality of UPFs is described in detail with reference to Figure 4 and is not described herein for brevity.

[0096] In operation 806 of method 800, information relating to one or more UPFs is transmitted to the network session element 122. The network session element 122 is configured to identify one or more UPFs based on the above information and one or more selection parameters to facilitate a packet data unit (PDU) session.

[0097] The sequence of operations in method 800 does not necessarily have to be performed in the same order as presented. Furthermore, one or more operations may be grouped together and performed in the form of a single step, or one operation may have several substeps that can be performed in parallel or sequentially.

[0098] The methods disclosed with reference to Figure 8, or one or more operations of the network session element 122 described with reference to Figures 2 to 4, may be implemented using software that includes computer executable instructions stored in one or more computer-readable media (e.g., one or more optical media disks, non-temporary computer-readable media such as volatile memory components (e.g., DRAM or SRAM), or non-volatile memory or storage components (e.g., hard drives or solid-state non-volatile memory components such as flash memory components)) and executed on a computer (e.g., any suitable computer such as a laptop computer, netbook, webbook, tablet computing device, smartphone, or other mobile computing device). Such software may be executed, for example, on a single local computer.

[0099] Furthermore, one or more computer-readable storage media may be used when carrying out embodiments consistent with the Disclosure. Computer-readable storage media refers to any type of physical memory in which information or data readable by a processor can be stored. Thus, computer-readable storage media may store instructions for execution by one or more processors, including instructions for causing a processor to perform steps or stages consistent with the embodiments described herein. The term “computer-readable media” should be understood to include tangible articles and exclude carrier waves and transient signals, i.e., non-transient. Examples include random-access memory (RAM), read-only memory (ROM), volatile memory, non-volatile memory, hard drives, CD (Compact Disc) ROMs, DVDs, flash drives, disks, and any other known physical storage media.

[0100] In one 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 in the network repository element 106. The processor 702 is configured to execute the instructions 705 stored in the memory 704 and to receive a UPF request from a network session element 122 to discover one or more UPFs from a plurality of UPFs. The UPF request includes at least a UPF service type. The processor 702 is configured to identify one or more UPFs from a plurality of UPFs based on the UPF service type. The processor 702 is configured to send information related to one or more UPFs to the network session element 122. The network session element 122 is configured to identify a UPF from one or more UPFs based on the above information and one or more selection parameters to facilitate a packet data unit (PDU) session.

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

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

[0103] In one embodiment, the processor 702 is configured to send notifications related to new UPFs registered for at least one service type, based on the subscription of the network session element 122.

[0104] In one embodiment, the processor 702 is further configured to identify one or more UPFs by determining which UPFs have been suspended based on the status of each UPF.

[0105] In one embodiment, the UPF service type is an information element of UpfInfo.

[0106] In one 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. This method includes the step of receiving a UPF request from a network session element 122 in order for a network repository element 106 to discover 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. This method includes the step of the network repository element 106 identifying one or more UPFs from a plurality of UPFs based on the UPF service type. This method includes the step of the network repository element 106 transmitting information related to one or more UPFs to the network session element 122. The network session element 122 is configured to identify a UPF from one or more UPFs based on this information and one or more selection parameters to facilitate a packet data unit (PDU) session.

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

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

[0110] In one embodiment, the method includes the step of identifying one or more UPFs by determining which UPFs have been suspended based on the status of each UPF using a network repository element 106.

[0111] In yet another embodiment, a system is disclosed. The system includes a network session element 122 and a network repository element 106. 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 communicably coupled with the network session element 122. The network repository element 106 is configured to receive UPF requests for the discovery of one or more UPFs from a plurality of UPFs. A UPF request includes at least a UPF service type. The network repository element 106 is configured to identify one or more UPFs from a plurality of UPFs based on the UPF service type. The network repository element 106 is configured to send information related to one or more UPFs to the network session element 122. The network session element 122 is configured to identify UPFs from one or more UPFs based on the above information and one or more selection parameters for facilitating a packet data unit (PDU) session.

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

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

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

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

[0116] Various embodiments of this disclosure offer numerous advantages. Embodiments of this disclosure enable user plane feature selection based on service type for packet data unit sessions. The introduction of attributes indicating one or more service types for a UPF during registration ensures that the UPF profile is updated with the service type and provides the option to discover UPFs based on the service type of UPF required for a user or PDU session. Such dedicated UPFs for various features / applications such as immersive media, IoT, and international roaming services ensure improved service for users while maintaining the resource requirements of the applications. Furthermore, each UPF may be associated with two or more service types, thereby enabling the flexibility and efficient use of UPFs for managing PDU sessions. Additionally, suspended UPFs, which are in a non-operational state, are identified and not offered to initiate PDU sessions, reducing latency when establishing PDU sessions. Furthermore, the network repository element 106 identifies and selects UPFs for PDU sessions based on the attribute service type indicated in the UPF request, thereby significantly improving the user experience and enhancing the QoS provided to users. Generally, when a dedicated UPF is used based on the UE 140 service type requirements for each PDU session, packet processing and traffic management are enhanced, thereby providing a seamless experience for users of the 5G communication system.

[0117] In general, it will be understood by those skilled in the art that the terms used herein are generally intended to be “open” terms (for example, “including” should be interpreted as “including but not limited to,” “having” as “having at least,” and “includes” as “includes but not limited to,” etc.). For example, to aid understanding, detailed explanations may include the use of introductory phrases “at least one” and “one or more” to introduce enumerations. However, the use of such phrases should not be interpreted as meaning that the introduction of an enumeration by the indefinite article "a" or "an" means limiting any particular part of the description containing such an introduced enumeration to a disclosure containing only one such enumeration, even if the enumeration includes an indefinite article such as the introductory phrase "one or more" or "at least one" and "a" or "an" (for example, "a" and / or "an" should typically be interpreted as meaning "at least one" or "one or more"). The same applies to the use of the definite article used to introduce such an enumeration. In addition, even if a particular part of the enumeration in the introduced description is explicitly enumerated, a person skilled in the art will recognize that such an enumeration should typically be interpreted as meaning at least the number enumerated (for example, a mere enumeration of "two enumerations" without other modifiers typically means at least two enumerations or two or more enumerations).

[0118] While various aspects and embodiments are disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for illustrative purposes only and are not intended to limit, and their true scope and spirit are shown by the following detailed description.

Claims

1. A network repository element, A memory configured to store instructions and a plurality of user plane functions (UPFs) registered in the network repository element, A processor that executes the instructions stored in the memory: To detect one or more UPFs from the plurality of UPFs, a UPF request is received from a network session element, the UPF request includes at least one UPF service type; Identify one or more UPFs from the plurality of UPFs based on the UPF service type; and, A processor configured to transmit information related to one or more UPFs to the network session element, The network session element is configured to identify a UPF from one or more UPFs based on the information and one or more selection parameters for facilitating a packet data unit (PDU) session. Network repository element.

2. The aforementioned processor, A registration request is received from UPF, and the registration request includes one or more UPF service types; and, The system is configured to register the UPF to one or more UPF service types based on the registration request. The network repository element according to claim 1.

3. The processor is configured to receive the UPF request from the network session element in response to a PDU session request from a user device. The network repository element according to claim 1.

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

5. The aforementioned processor, Based on the subscription of the network session element, it is configured to send notifications related to new UPFs registered for at least one service type. The network repository element according to claim 1.

6. The aforementioned processor, The system is further configured to identify one or more suspended UPFs by determining which UPFs are suspended based on the status of each UPF. The network repository element according to claim 1.

7. The aforementioned UPF service type is an information element of UpfInfo. The network repository element according to claim 1.

8. The aforementioned network session element includes a session management function (SMF) and a packet data network gateway control (PGW-C). The network repository element according to claim 1.

9. It is a method, Receiving a UPF request from a network session element in order to detect one or more UPFs from a plurality of UPFs registered in the network repository element, wherein the UPF request includes at least one UPF service type; The network repository element identifies one or more UPFs from the plurality of UPFs based on the UPF service type; and, The network repository element transmits information related to one or more UPFs to the network session element, The network session element is configured to identify a UPF from one or more UPFs based on the information and one or more selection parameters for facilitating a packet data unit (PDU) session. method.

10. The network repository element receives a registration request from UPF, wherein the registration request includes one or more UPF service types; and The network repository element includes registering the UPF to one or more UPF service types based on the registration request, The method according to claim 9.

11. The aforementioned UPF request is received from the network session element in response to a PDU session request from the user device. The method according to claim 9.

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

13. The network repository element further includes sending notifications related to new UPFs registered for the at least one service type based on the subscription of the network session element, The method according to claim 9.

14. The network repository element further includes determining which UPFs have been suspended based on the status of each UPF, and identifying one or more UPFs. The method according to claim 9.

15. It is a system, Network session elements, and A network repository element that stores a plurality of user plane functions (UPFs) registered in the network repository element, wherein the network repository element is communicably connected to the network session element; To detect one or more UPFs from the plurality of UPFs, a UPF request is received, the UPF request includes at least one UPF service type; Based on the UPF service type, one or more UPFs are identified from the plurality of UPFs; and, A network repository element configured to transmit information related to one or more UPFs to the network session element, The network session element is configured to identify a UPF from one or more UPFs based on the information and one or more selection parameters for facilitating a packet data unit (PDU) session. system.

16. The aforementioned network repository element is A registration request is received from UPF, and the registration request includes one or more UPF service types; and, The system is configured to register the UPF to one or more UPF service types based on the registration request. The system according to claim 15.

17. 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 device. The system according to claim 15.

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

19. The aforementioned network repository element is Based on the subscription to the network session element, it is configured to send notifications related to new UPFs registered for the at least one service type. The system according to claim 15.

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

Images