WO2023198733A1 - Efficient determination of user subscription information in a multi-domain network - Google Patents

Abstract

Embodiments include methods for network exposure function (NEF) of a communication network. Such methods include sending, to a first network node or function (NNF) of the communication network, a request to identify a network function (NF) producer associated with a user equipment (UE) The request includes: an identifier of the UE, a first type of NF of the communication network, and a second type of NF of the communication network to be checked when an NF producer profile is not available for the first type of NF. Such methods include, when the NF producer profile is not available for the first type of NF, receiving from the first NNF a response including one of the following: a uniform resource identifier (URI) associated with an NF producer of the second type, or an error message. Other embodiments include complementary methods for network repository functions (NRFs), unified data repositories (UDRs), and service communication proxies (SCPs) of the communication network, as well as NNFs configured to perform such methods.

Description

EFFICIENT DETERMINATION OF USER SUBSCRIPTION INFORMATION IN A MULTI-DOMAIN NETWORK

TECHNICAL FIELD

The present disclosure relates generally to communication networks and more specifically to techniques for efficiently determining and/or obtaining user subscription information from one of multiple domains (e g., 4G and 5G) of an operator network, or an unambiguous indication that such subscription information does not exist in either domain.

BACKGROUND

Long-Term Evolution (LTE) is an umbrella term for so-called fourth-generation (4G) radio access technologies developed within the Third-Generation Partnership Project (3 GPP) and initially standardized in Release 8 (Rel-8) and Release 9 (Rel-9), also known as Evolved UTRAN (E-UTRAN). LTE is targeted at various licensed frequency bands and is accompanied by improvements to non-radio aspects commonly referred to as System Architecture Evolution (SAE), which includes Evolved Packet Core (EPC) network. LTE continues to evolve through subsequent releases.

An overall exemplary architecture of a network comprising LTE and SAE is shown in Figure 1. E-UTRAN 100 includes one or more evolved Node B’s (eNB), such as eNBs 105, 110, and 115, and one or more user equipment (UE), such as UE 120. As used within the 3GPP standards, “user equipment” or “UE” means any wireless communication device e.g., smartphone or computing device) that is capable of communicating with 3 GPP-standard-compliant network equipment, including E-UTRAN as well as UTRAN and/or GERAN, as the third-generation (“3G”) and second-generation (“2G”) 3GPP RANs are commonly known.

As specified by 3GPP, E-UTRAN 100 is responsible for all radio-related functions in the network, including radio bearer control, radio admission control, radio mobility control, scheduling, and dynamic allocation of resources to UEs in uplink and downlink, as well as security of the communications with the UE. These functions reside in the eNBs, such as eNBs 105, 110, and 115. Each of the eNBs can serve a geographic coverage area including one more cells, including cells 106, 111, and 115 served by eNBs 105, 110, and 115, respectively

The eNBs in the E-UTRAN communicate with each other via the X2 interface, as shown in Figure 1. The eNBs also are responsible for the E-UTRAN interface to the EPC 130, specifically the SI interface to the Mobility Management Entity (MME) and the Serving Gateway (SGW), shown collectively as MME/S-GWs 134 and 138 in Figure 1. In general, the MME/S- GW handles both the overall control of the UE and data flow between the UE and the rest of the EPC. More specifically, the MME processes the signaling (e.g., control plane) protocols between the UE and the EPC, which are known as the Non-Access Stratum (NAS) protocols. The S-GW handles all Internet Protocol (IP) data packets (e.g., data or user plane) between the UE and the EPC and serves as the local mobility anchor for the data bearers when the UE moves between eNBs, such as eNBs 105, 110, and 115.

EPC 130 can also include a Home Subscriber Server (HSS) 131, which manages user- and subscriber-related information. HSS 131 can also provide support functions in mobility management, call and session setup, user authentication and access authorization. The functions of HSS 131 can be related to the functions of legacy Home Location Register (HLR) and Authentication Centre (AuC) functions or operations. HSS 131 can also communicate with MMEs 134 and 138 via respective S6a interfaces and, in some arrangements, with a user data repository (UDR - labelled EPC-UDR 135 in Figure 1) via a Ud interface. EPC-UDR 135 can store user credentials after they have been encrypted by AuC algorithms. These algorithms are not standardized (z.e., vendor-specific), such that encrypted credentials stored in EPC-UDR 135 are inaccessible by any other vendor than the vendor of HSS 131.

Although not shown in Figure 1, EPC 130 can include a Policy and Charging Rules Function (PCRF) that supports service data flow detection, policy enforcement, and flow-based charging. In general, the PCRF enables an operator to control services offered by the network and to better align service revenue and corresponding network resources. Additionally, EPC 130 can include a Service Capabilities Exposure Function (SCEF), which was introduced in Rel-13 to securely expose the services and capabilities provided by the 3GPP network interfaces.

The fifth generation (“5G”) of cellular systems, also referred to as New Radio (NR), was initially standardized 3GPP Rel-15 and continues to evolve in subsequent releases. NR is developed for maximum flexibility to support a variety of different use cases including enhanced mobile broadband (eMBB), machine type communications (MTC), ultra-reliable low latency communications (URLLC), side-link device-to-device (D2D), and several other use cases. 5G/NR technology shares many similarities with fourth-generation LTE.

At a high level, the 5G System (5GS) consists of an Access Network (AN) and a Core Network (CN). The AN provides UEs connectivity to the CN, e.g., via base stations such as gNBs or ng-eNBs described below. The CN includes a variety of Network Functions (NF) that provide a wide range of different functionalities such as session management, connection management, charging, authentication, etc.

Figure 2 illustrates a high-level view of an exemplary 5G network architecture, consisting of a Next Generation Radio Access Network (NG-RAN) 299 and a 5G Core (5GC) 298. NG-RAN 299 can include one or more gNodeB’s (gNBs) connected to the 5GC via one or more NG interfaces, such as gNBs 200, 250 connected via interfaces 202, 252, respectively. More specifically, gNBs 200, 250 can be connected to one or more Access and Mobility Management Functions (AMFs) in the 5GC 298 via respective NG-C interfaces. Similarly, gNBs 200, 250 can be connected to one or more User Plane Functions (UPFs) in 5GC 298 via respective NG-U interfaces. Various other network functions (NFs) can be included in the 5GC 298, as described in more detail below.

In addition, the gNBs can be connected to each other via one or more Xn interfaces, such as Xn interface 240 between gNBs 200 and 250. The radio technology for the NG-RAN is often referred to as “New Radio” (NR). With respect the NR interface to UEs, each of the gNBs can support frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof. Each of the gNBs can serve a geographic coverage area including one or more cells and, in some cases, can also use various directional beams to provide coverage in the respective cells.

NG-RAN 299 is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, i.e., the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL. For each NG-RAN interface (NG, Xn, Fl) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport and signaling transport. In some exemplary configurations, each gNB is connected to all 5GC nodes within an “AMF Region” with the term “AMF” referring to an access and mobility management function in the 5GC.

The NG RAN logical nodes shown in Figure 2 include a Central Unit (CU or gNB-CU) and one or more Distributed Units (DU or gNB-DU). For example, gNB 200 includes gNB-CU 220 and gNB-DUs 220 and 230. CUs e.g., gNB-CU 220) are logical nodes that host higher-layer protocols and perform various gNB functions such controlling the operation of DUs. A DU (e.g., gNB-DUs 220, 230) is a decentralized logical node that hosts lower layer protocols and can include, depending on the functional split option, various subsets of the gNB functions. A gNB- CU connects to one or more gNB-DUs over respective Fl logical interfaces (e.g., 222 and 232).

One change in 5G networks (e g., in 5GC) is that traditional peer-to-peer interfaces and protocols found in earlier-generation networks are modified and/or replaced by a Service Based Architecture (SB A) in which Network Functions (NFs) provide one or more services to one or more service consumers. This can be done, for example, by Hyper Text Transfer Protocol/Representational State Transfer (HTTP/REST) application programming interfaces (APIs). In general, the various services are self-contained functionalities that can be changed and modified in an isolated manner without affecting other services.

Furthermore, the services are composed of various “service operations”, which are more granular divisions of the overall service functionality. The interactions between service consumers and producers can be of the type “request/response” or “subscribe/notify”. In the 5G SB A, network repository functions (NRF) allow every network function to discover the services offered by other network functions, and Data Storage Functions (DSF) allow every network function to store its context. This 5G SBA model is based on principles including modularity, reusability and self-containment of NFs, which can enable network deployments to take advantage of the latest virtualization and software technologies.

A Network Exposure Function (NEF) acts as entry point into an operator's core network (CN), by securely exposing network capabilities and events provided by other NFs and by providing ways for the applications (e.g., application functions, AFs) to securely provide information to the CN. When an operator deploys both LTE/EPC and 5GC networks, the same NEF can be used for both. In certain event exposure or parameter provisioning scenarios, this common NEF must first identify whether a target UE to be reached is associated with a 4G subscription stored in HSS (see, e.g., Figure 1) or associated with a 5G subscription stored in the unified data management (UDM) function of the 5G network. The requesting entity (e.g., application) typically provides an identifier (called MSISDN) that maps a user’s telephone number to the subscriber identity module (SIM) in the target UE. The NEF’s selection will be determined by whether the target UE is provisioned in 5G and 4G domains or only in 4G domain.

SUMMARY

However, there are various problems, issues, and/or difficulties when applications (or AFs) external to the operator network contact the NEF regarding a target UE. For example, the external application may provide an unknown MSISDN or an unknown external identifier. This can cause unnecessary signaling between the NEF and other NFs, thereby wasting scarce network resources.

Embodiments of the present disclosure provide specific improvements to management of external applications access to users in a dual-CN deployment, such as by facilitating solutions to overcome exemplary problems summarized above and described in more detail below.

Some embodiments include methods (e.g., procedures) for an NEF of a communication network (e.g., 5GC). These exemplary methods can include sending, to a first network node or function (NNF) of the communication network, a request to identify a network function (NF) producer associated with a UE. The request includes:

• an identifier of the UE,

• a first type of NF of the communication network, and

• a second type of NF of the communication network to be checked when an NF producer profile is not available for the first type of NF. These exemplary methods can also include when the NF producer profile is not available for the first type of NF, receiving from the first NNF a response including one of the following:

• a uniform resource identifier (URI) associated with a NF producer of the second type, or

• an error message.

In some embodiments, the URI is received from the first NNF when the UE has a subscription provisioned in the second type of NF. Likewise, the error message is received from the first NNF when the UE has no subscription provisioned in the second type of NF.

In some embodiments, the first type of NF is a unified data management (UDM) function of a 5GC and the second type of NF is an HSS of an EPC. In some of these embodiments, the URI is at least part of a fully qualified domain name (FQDN)associated with an HSS in which the UE has a subscription provisioned.

In some embodiments, the first NNF is a network repository function (NRF), the request is a discovery request, and the response is a discovery response. In other embodiments, the first NNF is a service communication proxy (SCP), the request is a service request, and the response is a service response.

In some embodiments, these exemplary methods can also include, based on receiving the error message, determining that the UE has no subscription provisioned in either the first or second type of NF in the communication network.

In some embodiments, these exemplary methods can also include, when the URI associated with the NF producer of the second type is received, contacting the NF producer associated with the UE using the URI.

In some embodiments, the request to identify the NF producer associated with the UE comprises a flag indicating that the second type of NF should be checked when an NF producer profile is not available for the first type of NF.

Other embodiments include methods (e.g., procedures) for a network repository function (NRF) of a communication network (e.g., 5GC). These exemplary methods can include receiving, from a second NNF of the communication network, a discovery request to identify a NF producer associated with a UE. The discovery request includes:

• an identifier of the UE,

• a first type of NF of the communication network, and

• a second type of NF of the communication network to be checked when the NF producer profile is not available for the first type of NF.

These exemplary methods can also include sending to a UDR of the communication network a group mapping request that includes: the identifier of the UE, and the first and second types of NFs. These exemplary methods can also include receiving from the UDR a group mapping response that includes one of the following: a group identifier associated with an NF of the second type, or an error message. These exemplary methods can also include sending to the second NNF a discovery response that includes one of the following: an NF producer profile of an NF producer of the first type, a URI associated with an NF producer of the second type, or the error message.

In some embodiments, the NF producer profile is sent when the received group identifier is associated with an NF producer of the first type, the URI is sent when the received group identifier is associated with the NF producer of the second type, and the error message is sent when no group identifier is received.

In some embodiments, sending the group mapping request is based on determining one of the following: that an NF producer profile for the first type of NF is not available at the NRF, or that an NF producer profile for the first type of NF is available at the NRF but does not include the identifier of the UE.

In some embodiments, the group identifier associated with an NF producer of the second NF type is received from the UDR and the URI is sent to the second NNF, when the UE has a subscription provisioned in the second type of NF. Also, the error message is received from the UDR and sent to the second NNF, when the UE has no subscription provisioned in the second type of NF.

In some embodiments, the first type of NF is a UDM function of a 5GC and the second type of NF is an HSS of an EPC. In some of these embodiments, the group identifier associated with the NF producer of the second type is a FQDN associated with an HSS in which the UE has a subscription provisioned. The URI comprises at least part of the FQDN.

In some embodiments, the second NNF is an NEF of a 5GC. In other embodiments, the second NNF is an SCP of a 5GC. In some embodiments, the second type of NF is included in the group mapping request based on the received discovery request including a flag indicating that the second type of NF should be checked when an NF producer profile is not available for the first type of NF.

Other embodiments include methods (e.g., procedures) for a UDR of a communication network (e.g., 5GC). These exemplary methods can include receiving, from an NRF of the communication network, a group mapping request that includes the following: an identifier of a UE; and first and second types of NFs, of the communication network, to be checked for an NF producer profile associated with the UE. These exemplary methods can also include determining whether the UE has a subscription provisioned in each of the first and second types of NF. These exemplary methods can also include, when it is determined that the UE has no subscription provisioned in the first type of NF, sending to the NRF a group mapping response that includes one of the following:

• a group identifier associated with an NF producer of the second type, or

• an error message.

In some embodiments, the group identifier is sent when it is determined that the UE has a subscription provisioned in the second type of NF, and the error message is sent when it is determined that the UE has no subscription provisioned in the second type of NF.

In some embodiments, the first type of NF is a UDM function of a 5GC and the second type of NF is an HSS of an EPC. In some of these embodiments, the group identifier associated with the NF producer of the second type is a FQDN associated with an HSS in which the UE has a subscription provisioned.

Other embodiments include methods (e.g, procedures) for a service communication proxy (SCP) of a communication network (e.g., 5GC). These exemplary methods can include receiving, from an NEF of the communication network, a service request to identify an NF producer associated with a UE. The service request can include the following:

• an identifier of the UE,

• a first type of NF of the communication network, and

• a second type of NF of the communication network to be checked when an NF producer profile is not available for the first type.

These exemplary methods can also include sending the service request to a third NNF of the communication network, as a further message. These exemplary methods can also include receiving from the third NNF a response to the further message that includes one of the following:

• an NF producer profile of an NF producer of the first type,

• a URI associated with an NF producer of the second type, or

• an error message.

In some embodiments, the NF producer profile is received when an NF producer of the first type is identified, the URI is received when an NF producer of the second type is identified but an NF producer of the first type is not identified, and the error message is received when no NF producer of the first or second types is identified.

In some embodiments, when the UE has no subscription provisioned in the first type of NF, the URI is received from the third NNF when the UE has a subscription provisioned in the second type of NF, and the error message is received from the first NNF when the UE has no subscription provisioned in the second type of NF. In some embodiments, the first type of NF is a UDM function of a 5GC and the second type of NF is an HSS of an EPC. In some of these embodiments, the URI comprises at least part of a FQDN associated with an HSS in which the UE has a subscription provisioned.

In some embodiments, the third NNF is an NRF, the further message is a discovery request, and the response to the further message is a discovery response. In other embodiments, the third NNF is a UDR, the further message is a group mapping request, and the response to the further message is a group mapping response.

In some embodiments, these exemplary methods can also include forward the further message to the NEF in a service response.

Other embodiments include NEFs, NRFs, UDRs, and SCPs (or network nodes hosting and/or implementing these functions) configured to perform operations corresponding to any of the exemplary methods described herein. Other embodiments include non-transitory, computer- readable media storing program instructions that, when executed by processing circuitry, configure such NEFs, NRFs, UDRs, and SCPs (or network nodes hosting and/or implementing these functions) to perform operations corresponding to any of the exemplary methods described herein.

These and other embodiments described herein can unambiguously inform a consumer NF (e.g., NEF) whether a UE has a 4G subscription, such that the consumer NF receives an address from which to obtain subscription-related information only when one exists. The consumer NF can refrain from further query signaling when no address is received, which reduces unnecessary signaling between NFs in the network and consequent degradation to network KPIs. Also, returning the address avoids the need to search for the UE identity in the 4G/EPC domain, which can save significant computing resources when there is a large list of UEs/sub scribers to search. At a high level, embodiments facilitate deployment of networks with multiple domains (e.g., 4G/EPC and 5G/5GC) and delivery of services via such networks.

These and other objects, features, and advantages of embodiments of the present disclosure will become apparent upon reading the following Detailed Description in view of the Drawings briefly described below.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure l is a high-level block diagram of an exemplary LTE network architecture.

Figure 2 is a high-level block diagram of an exemplary 5G/NR network architecture.

Figure 3 shows an exemplary non-roaming 5G reference architecture with service-based interfaces and various 3GPP-defined NFs.

Figure 4 shows an exemplary service communication proxy (SCP) deployment in 5GC. Figure 5 is a signaling diagram that illustrates certain problems, issues, and/or difficulties when UEs are not provisioned in NF profiles but a Groupld is assigned to each UE.

Figures 6-9 show diagrams of various exemplary network signaling procedures, according to various embodiments of the present disclosure.

Figure 10 shows an exemplary method (e.g., procedure) for an NEF of a communication network (e.g., 5GC), according to various embodiments of the present disclosure.

Figure 11 shows an exemplary method (e.g., procedure) for an NRF of a communication network (e.g., 5GC), according to various embodiments of the present disclosure.

Figure 12 shows an exemplary method e.g., procedure) for a UDR of a communication network (e.g., 5GC), according to various embodiments of the present disclosure.

Figure 13 shows an exemplary method (e.g., procedure) for an SCP of a communication network (e.g., 5GC), according to various embodiments of the present disclosure.

Figure 14 shows a communication system according to various embodiments of the present disclosure.

Figure 15 shows a UE according to various embodiments of the present disclosure.

Figure 16 shows a network node according to various embodiments of the present disclosure.

Figure 17 shows host computing system according to various embodiments of the present disclosure.

Figure 18 is a block diagram of a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.

Figure 19 illustrates communication between a host computing system, a network node, and a UE via multiple connections, according to various embodiments of the present disclosure.

Figures 20-24 show diagrams of various exemplary network signaling procedures, according to various embodiments of the present disclosure.

Figure 25 shows an exemplary method (e.g., procedure) for a UDR of a communication network (e.g., 5GC), according to various embodiments of the present disclosure.

Figure 26 shows an exemplary method (e.g., procedure) for an NRF of a communication network (e.g., 5GC), according to various embodiments of the present disclosure.

Figure 27 shows a network node according to various embodiments of the present disclosure. DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

Furthermore, the following terms are used throughout the description given below:

• Radio Node: As used herein, a “radio node” can be either a “radio access node” or a “wireless device.”

• Radio Access Node: As used herein, a “radio access node” (or equivalently “radio network node,” “radio access network node,” or “RAN node”) can be any node in a radio access network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB/en-gNB) in a 3 GPP Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB/ng-eNB) in a 3GPP LTE network), base station distributed components (e.g., CU and DU), base station control- and/or user-plane components (e.g., CU-CP, CU-UP), a high-power or macro base station, a low-power base station (e.g., micro, pico, femto, or home base station, or the like), an integrated access backhaul (IAB) node, a transmission point, a remote radio unit (RRU or RRH), and a relay node.

• Core Network Node: As used herein, a “core network node” is any type of node in a core network. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a serving gateway (SGW), a Packet Data Network Gateway (P-GW), an access and mobility management function (AMF), a session management function (AMF), a user plane function (UPF), a Service Capability Exposure Function (SCEF), or the like.

• Wireless Device: As used herein, a “wireless device” (or “WD” for short) is any type of device that has access to (i.e., is served by) a cellular communications network by communicate wirelessly with network nodes and/or other wireless devices. Communicating wirelessly can involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. Some examples of a wireless device include, but are not limited to, smart phones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable devices, wireless endpoints, mobile stations, tablets, laptops, laptop- embedded equipment (LEE), laptop-mounted equipment (LME), smart devices, wireless customer-premise equipment (CPE), mobile-type communication (MTC) devices, Intemet-of-Things (loT) devices, vehicle-mounted wireless terminal devices, etc. Unless otherwise noted, the term “wireless device” is used interchangeably herein with the term “user equipment” (or “UE” for short).

• Network Node: As used herein, a “network node” is any node that is either part of the radio access network (e.g., a radio access node or equivalent name discussed above) or of the core network e.g., a core network node discussed above) of a cellular communications network. Functionally, a network node is equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the cellular communications network, to enable and/or provide wireless access to the wireless device, and/or to perform other functions ( .g., administration) in the cellular communications network.

Note that the description herein focuses on a 3 GPP cellular communications system and, as such, 3 GPP terminology or terminology similar to 3 GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system. Furthermore, although the term “cell” is used herein, it should be understood that (particularly with respect to 5G NR) beams may be used instead of cells and, as such, concepts described herein apply equally to both cells and beams.

As briefly mentioned above, there are various problems, issues, and/or difficulties when applications (or AFs) external to the operator network contact the NEF regarding a target UE. This is discussed in more detail below, after the following introduction to 5GC architecture. Figure 3 shows an exemplary non-roaming 5G reference architecture with service-based interfaces and various 3GPP-defined NFs within the Control Plane (CP). These include the following NFs, with additional details provided for those most relevant to the present disclosure:

• Application Function (AF, with Naf interface) interacts with the 5GC to provision information to the network operator and to subscribe to certain events happening in operator's network. An AF offers applications for which service is delivered in a different layer (i.e., transport layer) than the one in which the service has been requested (i.e., signaling layer), the control of flow resources according to what has been negotiated with the network. An AF communicates dynamic session information to PCF (via N5 interface), including description of media to be delivered by transport layer.

• Policy Control Function (PCF, with Npcf interface) supports unified policy framework to govern the network behavior, via providing PCC rules (e.g., on the treatment of each service data flow that is under PCC control) to the SMF via the N7 reference point. PCF provides policy control decisions and flow based charging control, including service data flow detection, gating, QoS, and flow-based charging (except credit management) towards the SMF. The PCF receives session and media related information from the AF and informs the AF of traffic (or user) plane events.

• User Plane Function (UPF)- supports handling of user plane traffic based on the rules received from SMF, including packet inspection and different enforcement actions (e.g., event detection and reporting). UPFs communicate with the RAN (e.g., NG-RNA) via the N3 reference point, with SMFs (discussed below) via the N4 reference point, and with an external packet data network (PDN) via the N6 reference point. The N9 reference point is for communication between two UPFs.

• Session Management Function (SMF, with Nsmf interface) interacts with the decoupled traffic (or user) plane, including creating, updating, and removing Protocol Data Unit (PDU) sessions and managing session context with the User Plane Function (UPF), e.g., for event reporting. For example, SMF performs data flow detection (based on filter definitions included in PCC rules), online and offline charging interactions, and policy enforcement.

• Charging Function (CHF, with Nchf interface) is responsible for converged online charging and offline charging functionalities. It provides quota management (for online charging), re-authorization triggers, rating conditions, etc. and is notified about usage reports from the SMF. Quota management involves granting a specific number of units (e.g., bytes, seconds) for a service. CHF also interacts with billing systems. • Access and Mobility Management Function (AMF, with Namf interface) terminates the RAN CP interface and handles all mobility and connection management of UEs (similar to MME in EPC). AMFs communicate with UEs via the N1 reference point and with the RAN (e.g., NG-RAN) via the N2 reference point.

• Network Exposure Function (NEF) with Nnef interface - acts as the entry point into operator's network, by securely exposing to AFs the network capabilities and events provided by 3 GPP NFs and by providing ways for the AF to securely provide information to 3GPP network. For example, NEF provides a service that allows an AF to provision specific subscription data (e.g., expected UE behavior) for various UEs. In general, NEF provides services similar to services provided by SCEF in EPC.

• Network Repository Function (NRF) with Nnrf interface - provides service registration and discovery, enabling NFs to identify appropriate services available from other NFs.

• Network Slice Selection Function (NSSF) with Nnssf interface - a “network slice” is a logical partition of a 5G network that provides specific network capabilities and characteristics, e.g., in support of a particular service. A network slice instance is a set of NF instances and the required network resources (e.g., compute, storage, communication) that provide the capabilities and characteristics of the network slice. The NSSF enables other NFs (e.g., AMF) to identify a network slice instance that is appropriate for a UE’s desired service.

• Authentication Server Function (AUSF) with Nausf interface - based in a user’s home network (HPLMN), it performs user authentication and computes security key materials for various purposes.

• Network Data Analytics Function (NWDAF) with Nnwdaf interface, described in more detail above and below.

• Location Management Function (LMF) with Nlmf interface - supports various functions related to determination of UE locations, including location determination for a UE and obtaining any of the following: DL location measurements or a location estimate from the UE; UL location measurements from the NG RAN; and non-UE associated assistance data from the NG RAN.

The Unified Data Management (UDM) function supports generation of 3 GPP authentication credentials, user identification handling, access authorization based on subscription data, and other subscriber-related functions. To provide this functionality, the UDM uses subscription data (including authentication data) stored in the 5GC unified data repository (UDR). In addition to the UDM, the UDR supports storage and retrieval of policy data by the PCF, as well as storage and retrieval of application data by NEF. The terms “UDM” and “UDM function” are used interchangeably herein.

The NRF allows every NF to discover the services offered by other NF s, and Data Storage Functions (DSF) allow every NF to store its context. In addition, the NEF provides exposure of capabilities and events of the 5GC to AFs within and outside of the 5GC. For example, NEF provides a service that allows an AF to provision specific subscription data (e.g., expected UE behavior) for various UEs.

As briefly mentioned above, when an operator deploys both LTE/EPC and 5GC networks, one NEF can be common to both. In certain event exposure or parameter provisioning scenarios, this common NEF must first identify whether a target UE to be reached is associated with a 4G subscription stored in HSS (see, e.g., Figure 1) or associated with a 5G subscription stored in the UDM/UDR. The requesting entity (e.g., AF or NF) typically provides an identifier (called MSISDN) that maps a user’s telephone number to the subscriber identity module (SIM) in the target UE. The NEF’ s selection will be determined by whetherthe target UE is provisioned in 5G and 4G domains or only in 4G domain.

Service Communication Proxy (SCP) is a 5GC NF that was introduced in Rel-16. SCP provides centralized capabilities such as service-based interface (SBI) routing, NF discovery and selection, failover, message screening, etc. More generally, SCP facilitates 5GC implementation in a highly distributed multi-access edge compute cloud environment. SCP provides a single point of entry for a cluster of NFs after they have been successfully discovered by the NRF. As such, the SCP becomes the delegated discovery point in a data center, offloading NRF from the distributed service meshes that can comprise a network operator’s infrastructure.

Figure 4 shows an exemplary deployment of an SCP in a 5GC, which is further described in 3GPP TS 23.501 (vl7.3.0) Annex E incorporated herein by reference in its entirety. In this example, the SCP discovers the NF service producer (“producer” or “NFp”) via NRF on behalf of the NF service consumer (“consumer” or “NFc”). As such, the NFc (e.g., the NEF discussed above) does not have to interact directly with NRF in contrast to arrangements without SCPs.

In some deployments, UE group identifiers (Groupld) are provisioned (e g., stored or included) in an NFp profile but individual UE identifiers (or UE identifier ranges) are not. As such, for the NRF to discover the corresponding NFp profile for a certain UE, it has to find first the corresponding Groupld via the UDR service GroupIdMap. In some cases, however, operators (e.g., Verizon or AT&T) may provision a Groupld for each individual UE, although often the same Groupld will be assigned to many UEs. This facilitates porting or moving a subscriber between operators (e.g., in accordance with regulations) without needing to modify Groupld ranges. Figure 5 shows a signaling diagram that illustrates certain problems, issues, and/or difficulties associated with the above-described arrangement. The procedure involves a first HSS (HSS1) that holds subscription credentials for a first UE (UE1), a second HSS (HSS2) that holds subscription credentials for a second UE (UE2), and a UDM that holds subscription credentials for a third UE (UE3). The network arrangement also includes a 5GC UDR and an EPC UDR In this arrangement, the 5GC NEF is assumed to be co-located with the EPC SCEF.

In operation 0 (which can also be considered a pre-requisite or pre-condition), HSS1, HSS2, and UDM register with NRF as NFp’s with respect to Grouplds but not with respect to individual UE identifiers. In operation 1, the NEF sends the NRF a discovery request for another UE, identified by UE5. Since the NFp profiles include Grouplds but neither UE IDs nor UE ID ranges (e.g., MSISDN number series), in operation 2 the NRF uses the 5GC UDR GroupIdMap service to find the Groupld associated with UE5. If the UE1 does not have a 5G subscription (i.e., 5G data not provisioned), then there is no mapping from UE5 to a Groupld in the 5GC UDR, which returns a “user not found” error in operation 3. In operation 4, since the NRF could not obtain any valid UDM profile for UE5, it responds to the NEF’s discovery request successfully but with an empty list of NFp profiles.

Given this empty list of NFp profiles, the NEF assumes that UE5 is not a 5G user and thus is a 4G user, primarily because NEF has other way to properly identify UE5 as an actual 4G user. In the example shown in Figure 5, this assumption may be incorrect if the UE5 public identifier (e.g., MSISDN, External Identifier) is not even provisioned in the network. Nevertheless, based on the assumption by NEF, the co-located 4G SCEF tries to contact HSS via legacy diameter routing agent (DRA). Thus, in operation 5, the SCEF sends an HSS request to DRA with identifier of UE5. In operation 6, the DRA sends a request for the corresponding HSSId for UE5 to the EPC UDR, which returns an error in operation 7 since UE5 is not provisioned in EPC. In operation 8, DRA informs SCEF of this error.

The error condition illustrated in Figure 5 can occur when applications (or AFs) external to the operator network contact the NEF regarding a target UE. For example, the external application may provide an unknown MSISDN or an unknown external identifier. This can cause unnecessary signaling between the NEF and other NFs, since SCEF+NEF is blindly contacting 5GC and EPC UDRs to eventually receive “identity unknown” in both domains. This wastes network signaling resources and increments the HSS error counter, which negatively impacts network key performance indicators (KPIs).

Accordingly, embodiments of the present disclosure provide novel, flexible, and efficient techniques whereby a consumer NF (NFc, e.g., NEF) is unambiguously informed about whether a target UE has a 4G subscription to an operator network, in the event that the target UE does not have a 5G subscription to the operator network (i.e., when the network operator deploys both 4G and 5G). These techniques involve the following features and/or aspects:

• a flag (or field) in the NFc (e.g., NEF) discovery request, indicating a new expected behaviour by the NRF ;

• an NFtype (e.g., HSS) in the NFc discovery request, indicating a second domain that needs to be checked.

• NRF queries UDR via GroupIdMap for the user Groupld, in both original NFtype (e.g., UDM) and new NFtype (e.g., HSS);

• when user is provisioned in the 4G but not 5G, NFc receives a redirection indication with corresponding endpoint/address to reach the new NFtype corresponding to the 4G subscription; and

• when user is provisioned in neither 4G nor 5G, NFc receives a “404 Not Found Error” that is safely interpreted as the user is not provisioned in the network.

Embodiments provide various benefits, advantages, and/or solutions to problems described herein. For example, a consumer NF (e.g., NEF) is unambiguously informed about whether a target UE has a 4G subscription and receives an address from which to obtain user information related to that 4G subscription only when one exists. Thus, the consumer NF can refrain from further query signaling when no address is received, which reduces unnecessary signaling between NFs in the operator network and consequent degradation to network KPIs. Also, returning the address avoids the need to search for the UE identity in the EPC domain, which can save significant computing resources when there is a large list of UEs/subscribers to search.

Figures 6-7 show signaling diagrams for scenarios when a target UE is and is not found in another (e g., EPC) domain, respectively, according to various of the present disclosure. These figures show signaling between the same NFs as discussed above in relation to Figure 5. Although the operations in Figures 6-7 are given numerical labels, this is done to facilitate explanation and is not intended to imply any specific ordering of the operations, unless expressly stated to the contrary.

As a pre-requisite or pre-condition, UE public identifiers (e.g., MSISDNs, External Identifiers, etc.) are provisioned in UDR in association with a Groupld for each NF type, e.g., UDMGroupID for UDM, HSSGroupId for HSS. In this manner, a mapping from UE identifiers to HSSGroupId becomes accessible via GroupIdMap. In operation 0 (which can also be considered a pre-requisite or pre-condition), HSS1, HSS2, and UDM register with NRF as NFp’s with respect to Grouplds but not with respect to individual UE identifiers. In operation 1, the NEF sends the NRF a discovery request for UE1, whose 4G subscription credentials are stored in HSS1. In addition to an identifier for UE1 and NFtype = UDM indicating a first domain needing to be checked, the discovery request includes the following:

• a flag indicating a new expected behaviour by the NRF; and

• NFtype = HSS, indicating a second domain needing to be checked in relation to the request.

In operation 2, NRF uses the 5GC UDR GroupIdMap service to find a Groupld associated with UE1. NRF includes both NFtypes indicated by the NEF (i.e., UDR and HSS), which is currently allowed by UDM.

The case shown in Figure 6A is described as follows. In response to the GroupIdMap service request, UDR determines that there is no UDMGroupID associated with UE1, but that there is an HSSGroupId associated with UE1. In operation 3, the UDR responds to NRF with the HSSGroupId associated with UE1.

In operation 4, based on the HSSGroupId received in operation 3, the NRF responds with a HTTP 303 (See Other) message including a Location Header with information about where to find a valid resource for the discovery request for the target UE ID. In particular, the NRF includes a uniform resource identifier (URI) of the HSS endpoint where the UE’s subscription information is stored. One pre-requisite is that the HSSGroupId for each UE should be encoded in a way that allows the NEF to identify the HSS endpoint. For example, an HSSGroupId can be a fully qualified domain name (FQDN) of the diameter HSS pool serving the UE, e.g., <HSSGroupId>. diameter. <hss-pool>, where <hss-pool> is a domain label (e.g., hss-pool- Lericsson.com) that identifies the specific HSS diameter pool serving the UE in EPC.

When the Location Header in the HTTP 303 response in operation 4 (for the case where UDM group is not found but the HSS group is found) includes the HSS pool identity, the subsequent DRA request towards EPC (e.g., operation 6 in Figure 5) includes the request destination so that DRA is not required to search its database for the target HSS pool associated with the target UE ID (e.g., UE1). Thus, only oneUE search is required/performed, i.e., by UDR in operation 2 above.

For completeness, the case where the NRF has an UDM profile that includes a Groupld for a target UE is shown in Figure 6B. In this scenario, the NRF uses the UDR GroupIdMap service to find a Groupld associated with the identifier for UE3. NRF includes both NFtypes indicated by the NEF (i.e., UDM and HSS), and UDR returns a UDMGroupId3 corresponding to the UE3 identifier. The NRF finds the UDM profile that includes UDMGroupId3, and provides it to the NEF in a discovery response. The case when a target UE is not found in another (e.g., EPC) domain is shown in Figure 7 and described as follows. In operation 1, the NEF sends the NRF a discovery request for UE5, which has no subscription provisioned in UDM, HSS1, or HSS2. As in Figure 6, the discovery request includes the flag and both NFtypes. In operation 2, NRF uses the UDR GroupIdMap service to find a Groupld associated with UE5. NRF includes both NFtypes indicated by the NEF (i.e., UDR and HSS). In response to the GroupIdMap service request in operation 2, UDR determines that there is no UDMGroupID associated with UE5 and there is no HSSGroupId associated with UE1. In operation 3, the UDR responds to NRF with “404 Not Found Error”, which the NRF sends to NEF in operation 4 responsive to the discovery request in operation 1. Accordingly, NEF correctly interprets that UE5 is provisioned in neither 5G nor 4G.

Figure 8 shows a signaling diagram for another scenario where a target UE is found in another (e.g., EPC) domain. The primary difference between Figures 6 and 8 is the introduction of the SCP for indirect communication between NEF and NRF, such as illustrated in Figure 4. In other words, NEF does not perform discovery directly with NRF but instead provides service requests to SCP which acts on behalf of NEF towards NRF (and vice versa).

From NRF and UDR viewpoints, operations 2-5 in Figure 8 are substantially the same as respective operations 1-4 in Figure 6, except that operations 2 and 5 involve SCP rather than NEF. In operation 6, the SCP does not interpret the HTTP 303 response in operation 5 as if the SCP needs to perform the redirection, but rather passes the HTTP 303 response with the HSS URI back to NEF as a proxy. The NEF can then query the HSS URI, either directly or via SCP.

As a variant, the SCP can query the UDR using the GroupIdMap service rather than querying the NRF with a discovery request as shown in Figure 8. In this way, the SCP in this variant behaves similar to the NRF shown in Figure 6.

In the event that UDR responds to NRF with “404 Not Found Error” in operation 4, the NRF will forward this error message to NEF via SCP in operations 5-6.

In some cases, a target UE may be provisioned in NFp profiles at the NRF. For example, a range of UE identifiers may be provisioned when all the UEs in this range have 5G subscriptions in the network. In other words, if a target UE is included in the range of UE identifiers in the UDM profile, then the target UE has a 5G subscription. Similarly, individual UEs may be provisioned in the UDM profile at NRF, once their respective 5G subscriptions are provisioned/ active in the network. Thus, an NRF can infer that a target UE has a 5G subscription only if that target UE is provisioned in a UDM profile at the NRF.

Figure 9 shows a signaling diagram for another scenario where a target UE is found in another (e.g., EPC) domain. In this scenario, UE public IDs (e.g., MSISDN, external Identifier, etc.) are provisioned in UDM (i.e., NFp) profile stored in NRF, either as individual UEs or as UE ranges but without Grouplds. Even so, Group Ids are assigned to UEs with subscriptions provisioned in an HSS, so that a mapping from UEs to HSSGroupId is accessible via GroupIdMap service.

In operation 0 (which can also be considered a pre-requisite or pre-condition), HSS1, HSS2, and UDM register with NRF as NFp’s with respect to individual UE identifiers. For example, UDM can register for UEs that have a 5G subscription and HSS1, HSS2 can register for UEs that have 4G rather than 5G subscriptions.

Operation 1 is substantially identical to Figure 6 operation 1, described above. In operation 2, the NRF searches the UDM profile and does not find UE1. Based on the flag and in the discovery request, the NRF then performs the GroupIdMap service operation towards UDR, providing the identifier of UE1 and indicating to search HSS. In operation 3, the UDR responds with Groupldl associated with the identifier of UE1. The NRF responds to the NEF in operation 4 with an HTTP 303 (See Other) message including a Location Header with information about where to find a valid resource for the discovery request for the target UE ID. In particular, the NRF includes a uniform resource identifier (URI) of the HSS endpoint where the UE’s subscription information is stored, which can be part of the Groupldl received from UDR (as described above).

Alternately, when the UDR does not find an HSS-associated group ID for UE1, it responds in operation 4 with "404 Not Found Error”, which the NRF provides to the NEF such as in Figure 7. Based on this, NEF correctly interprets that UE1 is provisioned in neither 5G nor 4G. Although Figure 9 shows direct communication between NEF and NRF, the NEF and NRF can exchange the messages in operations 1 and 4 via SCP such as in Figure 8.

The embodiments described above in relation to Figures 6-9 are further illustrated by Figures 10-13, which depict exemplary methods (e.g., procedures) for an NEF, an NRF, a UDR, and an SCP, respectively. Put differently, various features of the operations described below correspond to various embodiments described above. The exemplary methods shown in Figures 10-13 can be used cooperatively (e.g., with each other and with other procedures described herein) to provide benefits, advantages, and/or solutions to problems described herein. Although the exemplary methods are illustrated in Figures 10-13 by specific blocks in particular orders, the operations corresponding to the blocks can be performed in different orders than shown and can be combined and/or divided into blocks and/or operations having different functionality than shown. Optional blocks and/or operations are indicated by dashed lines.

In particular, Figure 10 illustrates an exemplary method (e.g., procedure) for an NEF of a communication network (e.g., 5GC), according to various embodiments of the present disclosure. For example, the exemplary method shown in Figure 10 can be performed by an NEF (or a network node hosting the same) such as described elsewhere herein.

The exemplary method can include the operations of block 1010, where the NEF can send, to a first network node or function (NNF) of the communication network, a request to identify a NF producer associated with a UE. The request includes:

• an identifier of the UE,

• a first type of NF of the communication network, and

• a second type of NF of the communication network to be checked when an NF producer profile is not available for the first type of NF.

The exemplary method can also include the operations of block 1020, where when the NF producer profile is not available for the first type of NF, the NEF can receive from the first NNF a response including one of the following:

• a URI associated with a NF producer of the second type, or

• an error message.

In some embodiments, the URI is received from the first NNF (e.g., in block 1020) when the UE has a subscription provisioned in the second type of NF. Likewise, the error message is received from the first NNF (e.g., in block 1020) when the UE has no subscription provisioned in the second type of NF.

In some embodiments, the first type of NF is a UDM function of a 5GC and the second type of NF is an HSS of an EPC. In some of these embodiments, the URI is at least part of a FQDN associated with an HSS in which the UE has a subscription provisioned.

In some embodiments, the first NNF is an NRF, the request is a discovery request, and the response is a discovery response. In other embodiments, the first NNF is an SCP, the request is a service request, and the response is a service response.

In some embodiments, the exemplary method can also include the operations of block 1030, where based on receiving the error message, the NEF can determine that the UE has no subscription provisioned in either the first or second type of NF in the communication network.

In some embodiments, the exemplary method can also include the operations of block 1040, where when the URI associated with the NF producer of the second type is received, the NEF can contact the NF producer associated with the UE using the URI.

In some embodiments, the request to identify the NF producer associated with the UE comprises a flag indicating that the second type of NF should be checked when an NF producer profile is not available for the first type of NF.

In addition, Figure 11 illustrates an exemplary method (e.g., procedure) for an NRF of a communication network (e.g., 5GC), according to various embodiments of the present disclosure. For example, the exemplary method shown in Figure 11 can be performed by an NRF (or a network node hosting the same) such as described elsewhere herein.

The exemplary method can include the operations of block 1110, where the NRF can receive, from a second NNF of the communication network, a discovery request to identify a NF producer associated with a UE. The discovery request includes:

• an identifier of the UE,

• a first type of NF of the communication network, and

• a second type of NF of the communication network to be checked when the NF producer profile is not available for the first type of NF.

The exemplary method can also include the operations of block 1120, where the NRF can send to a UDR of the communication network a group mapping request that includes: the identifier of the UE, and the first and second types of NFs. The exemplary method can also include the operations of block 1130, where the NRF can receive from the UDR a group mapping response that includes one of the following: a group identifier associated with an NF producer of the first type or of the second type, or an error message. The exemplary method can also include the operations of block 1140, where the NRF can send to the second NNF a discovery response that includes one of the following: an NF producer profile of an NF producer of the first type, a URI associated with an NF producer of the second type, or the error message.

In some embodiments, the NF producer profile is sent when the received group identifier is associated with an NF producer of the first type, the URI is sent when the received group identifier is associated with the NF producer of the second type, and the error message is sent when no group identifier is received.

In some embodiments, sending the group mapping request in block 1120 is based on the operations of block 1115, where the NRF can determine one of the following: that an NF producer profile for the first type of NF is not available at the NRF, or that an NF producer profile for the first type of NF is available at the NRF but does not include the identifier of the UE.

In some embodiments, the group identifier associated with an NF producer of the second NF type is received from the UDR (e.g., in block 1130) and the URI is sent to the second NNF (e.g., in block 1140), when the UE has a subscription provisioned in the second type of NF. Also, the error message is received from the UDR (e.g., in block 1130) and sent to the second NNF (e.g., in block 1140) when the UE has no subscription provisioned in the second type of NF.

In some embodiments, the first type of NF is a UDM function of a 5GC and the second type of NF is an HSS of an EPC. In some of these embodiments, the group identifier associated with the NF producer of the second type is a FQDN associated with an HSS in which the UE has a subscription provisioned. The URI comprises at least part of the FQDN, such as described above. In some embodiments, the second NNF is an NEF of a 5GC. In other embodiments, the second NNF is an SCP of a 5GC. In some embodiments, the second type of NF is included in the group mapping request (e.g., sent in block 1120) based on the discovery request (e.g., received in block 1110) including a flag indicating that the second type of NF should be checked when an NF producer profile is not available for the first type of NF.

In addition, Figure 12 illustrates an exemplary method ( .g., procedure) for a UDR of a communication network (e.g., 5GC), according to various embodiments of the present disclosure. For example, the exemplary method shown in Figure 12 can be performed by a UDR (or a network node hosting the same) such as described elsewhere herein

The exemplary method can include the operations of block 1210, where the UDR can receive, from an NRF of the communication network, a group mapping request that includes the following: an identifier of a UE; and first and second types of NFs, of the communication network, to be checked for a NF producer profile associated with the UE. The exemplary method can also include the operations of block 1220, where the UDR can determine whether the UE has a subscription provisioned in each of the first and second types of NF. The exemplary method can also include the operations of block 1230, where when it is determined that the UE has no subscription provisioned in the first type of NF, the UDR can send to the NRF a group mapping response that includes one of the following:

• a group identifier associated with an NF producer of the second type, or

• an error message.

In some embodiments, the group identifier is sent when it is determined (e g., in block 1220) that the UE has a subscription provisioned in the second type of NF, and the error message is sent (e.g., in block 1220) when it is determined that the UE has no subscription provisioned in the second type of NF.

In some embodiments, the first type of NF is a UDM function of a 5GC and the second type of NF is an HSS of an EPC. In some of these embodiments, the group identifier associated with the NF producer of the second type is a FQDN associated with an HSS in which the UE has a subscription provisioned.

In addition, Figure 13 illustrates an exemplary method e.g., procedure) for an SCP of a communication network (e.g., 5GC), according to various embodiments of the present disclosure. For example, the exemplary method shown in Figure 13 can be performed by a SCP (or a network node hosting the same) such as described elsewhere herein.

The exemplary method can include the operations of block 1310, where the SCP can receive, from an NEF of the communication network, service request to identify an NF producer associated with a UE. The service request can include the following: • an identifier of the UE,

• a first type of NF of the communication network, and

• a second type of NF of the communication network to be checked when an NF producer profile is not available for the first type.

The exemplary method can also include the operations of block 1320, where the SCP can send the service request to a third NNF of the communication network, as a further message. The exemplary method can also include the operations of block 1330, where the SCP can receive from the third NNF a response to the further message that includes one of the following:

• an NF producer profile of an NF producer of the first type,

• a URI associated with an NF producer of the second type, or

• an error message.

In some embodiments, the NF producer profile is received when an NF producer of the first type is identified (i.e., by the third NNF), the URI is received when an NF producer of the second type is identified but an NF producer of the first type is not identified, and the error message is received when no NF producer of the first or second types is identified.

In some embodiments, when the UE has no subscription provisioned in the first type of NF, the URI is received from the third NNF (e.g., in block 1330) when the UE has a subscription provisioned in the second type of NF, and the error message is received from the third NNF (e.g., in block 1330) when the UE has no subscription provisioned in the second type of NF.

In some embodiments, the first type of NF is a UDM function of a 5GC and the second type of NF is an HSS of an EPC. In some of these embodiments, the URI is at least part of a FQDN associated with an HSS in which the UE has a subscription provisioned.

In some embodiments, the third NNF is an NRF, the further message is a discovery request, and the response to the further message is a discovery response. In other embodiments, the third NNF is a UDR, the further message is a group mapping request, and the response to the further message is a group mapping response.

In some embodiments, the exemplary method can also include the operations of block 1340, where the SCP can forward the further message to the NEF in a service response.

Although various embodiments are described herein above in terms of methods, apparatus, devices, computer-readable medium and receivers, the person of ordinary skill will readily comprehend that such methods can be embodied by various combinations of hardware and software in various systems, communication devices, computing devices, control devices, apparatuses, non-transitory computer-readable media, etc.

Figure 14 shows an example of a communication system 1400 in accordance with some embodiments. In this example, the communication system 1400 includes a telecommunication network 1402 that includes an access network 1404, such as a radio access network (RAN), and a core network 1406, which includes one or more core network nodes 1408. The access network 1404 includes one or more access network nodes, such as network nodes 1410a and 1410b (one or more of which may be generally referred to as network nodes 1410), or any other similar 3^rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 1410 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1412a, 1412b, 1412c, and 1412d (one or more of which may be generally referred to as UEs 1412) to the core network 1406 over one or more wireless connections.

Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1400 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system 1400 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

The UEs 1412 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1410 and other communication devices. Similarly, the network nodes 1410 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1412 and/or with other network nodes or equipment in the telecommunication network 1402 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1402.

In the depicted example, the core network 1406 connects the network nodes 1410 to one or more hosts, such as host 1416. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1406 includes one more core network nodes (e.g., core network node 1408) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1408. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM) function, Unified Data Repository (UDR), Service Communication Proxy (SCP), Network Repository Function (NEF), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

The host 1416 may be under the ownership or control of a service provider other than an operator or provider of the access network 1404 and/or the telecommunication network 1402, and may be operated by the service provider or on behalf of the service provider. The host 1416 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

As a whole, the communication system 1400 of Figure 14 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

In some examples, the telecommunication network 1402 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1402 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1402. For example, the telecommunications network 1402 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

In some examples, the UEs 1412 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1404 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1404. Additionally, a UE may be configured for operating in single- or multi -RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e., being configured for multi -radio dual connectivity (MR-DC), such asE-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

In the example, the hub 1414 communicates with the access network 1404 to facilitate indirect communication between one or more UEs (e.g., UE 1412c and/or 1412d) and network nodes (e.g., network node 1410b). In some examples, the hub 1414 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1414 may be a broadband router enabling access to the core network 1406 for the UEs. As another example, the hub 1414 may be a controller that sends commands or instructions to one or more actuators in the UEs Commands or instructions may be received from the UEs, network nodes 1410, or by executable code, script, process, or other instructions in the hub 1414. As another example, the hub 1414 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1414 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1414 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1414 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 1414 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

The hub 1414 may have a constant/persi stent or intermittent connection to the network node 1410b. The hub 1414 may also allow for a different communication scheme and/or schedule between the hub 1414 and UEs (e.g., UE 1412c and/or 1412d), and between the hub 1414 and the core network 1406. In other examples, the hub 1414 is connected to the core network 1406 and/or one or more UEs via a wired connection. Moreover, the hub 1414 may be configured to connect to an M2M service provider over the access network 1404 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1410 while still connected via the hub 1414 via a wired or wireless connection. In some embodiments, the hub 1414 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1410b. In other embodiments, the hub 1414 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1410b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

Figure 15 shows a UE 1500 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop -mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

The UE 1500 includes processing circuitry 1502 that is operatively coupled via a bus 1504 to an input/output interface 1506, a power source 1508, a memory 1510, a communication interface 1512, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 15. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

The processing circuitry 1502 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1510. The processing circuitry 1502 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1502 may include multiple central processing units (CPUs).

In the example, the input/output interface 1506 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1500. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

In some embodiments, the power source 1508 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 1508 may further include power circuitry for delivering power from the power source 1508 itself, and/or an external power source, to the various parts of the UE 1500 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1508. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1508 to make the power suitable for the respective components of the UE 1500 to which power is supplied.

The memory 1510 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1510 includes one or more application programs 1514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1516. The memory 1510 may store, for use by the UE 1500, any of a variety of various operating systems or combinations of operating systems.

The memory 1510 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 1510 may allow the UE 1500 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1510, which may be or comprise a device-readable storage medium.

The processing circuitry 1502 may be configured to communicate with an access network or other network using the communication interface 1512. The communication interface 1512 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1522. The communication interface 1512 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 1518 and/or a receiver 1520 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1518 and receiver 1520 may be coupled to one or more antennas (e.g., antenna 1522) and may share circuit components, software or firmware, or alternatively be implemented separately.

In the illustrated embodiment, communication functions of the communication interface 1512 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1512, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1500 shown in Figure 15.

As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.

In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’ s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

Figure 16 shows a network node 1600 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).

Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi -standard radio (MSR) equipment such as MSRBSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).

The network node 1600 includes a processing circuitry 1602, a memory 1604, a communication interface 1606, and a power source 1608. The network node 1600 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc ), which may each have their own respective components. In certain scenarios in which the network node 1600 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1600 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e g , separate memory 1604 for different RATs) and some components may be reused (e.g., a same antenna 1610 may be shared by different RATs). The network node 1600 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1600, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1600.

The processing circuitry 1602 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1600 components, such as the memory 1604, to provide network node 1600 functionality.

In some embodiments, the processing circuitry 1602 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1602 includes one or more of radio frequency (RF) transceiver circuitry 1612 and baseband processing circuitry 1614. In some embodiments, the radio frequency (RF) transceiver circuitry 1612 and the baseband processing circuitry 1614 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1612 and baseband processing circuitry 1614 may be on the same chip or set of chips, boards, or units.

The memory 1604 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1602. The memory 1604 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions (collectively denoted computer program product 1604a) capable of being executed by the processing circuitry 1602 and utilized by the network node 1600. The memory 1604 may be used to store any calculations made by the processing circuitry 1602 and/or any data received via the communication interface 1606. In some embodiments, the processing circuitry 1602 and memory 1604 is integrated.

The communication interface 1606 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1606 comprises port(s)/terminal(s) 1616 to send and receive data, for example to and from a network over a wired connection. The communication interface 1606 also includes radio front-end circuitry 1618 that may be coupled to, or in certain embodiments a part of, the antenna 1610. Radio front-end circuitry 1618 comprises filters 1620 and amplifiers 1622. The radio front-end circuitry 1618 may be connected to an antenna 1610 and processing circuitry 1602. The radio front-end circuitry may be configured to condition signals communicated between antenna 1610 and processing circuitry 1602. The radio front-end circuitry 1618 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio frontend circuitry 1618 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1620 and/or amplifiers 1622. The radio signal may then be transmitted via the antenna 1610. Similarly, when receiving data, the antenna 1610 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1618. The digital data may be passed to the processing circuitry 1602. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, the network node 1600 does not include separate radio front-end circuitry 1618, instead, the processing circuitry 1602 includes radio front-end circuitry and is connected to the antenna 1610. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1612 is part of the communication interface 1606. In still other embodiments, the communication interface 1606 includes one or more ports or terminals 1616, the radio frontend circuitry 1618, and the RF transceiver circuitry 1612, as part of a radio unit (not shown), and the communication interface 1606 communicates with the baseband processing circuitry 1614, which is part of a digital unit (not shown).

The antenna 1610 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 1610 may be coupled to the radio front-end circuitry 1618 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 1610 is separate from the network node 1600 and connectable to the network node 1600 through an interface or port.

The antenna 1610, communication interface 1606, and/or the processing circuitry 1602 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 1610, the communication interface 1606, and/or the processing circuitry 1602 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.

The power source 1608 provides power to the various components of network node 1600 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1608 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1600 with power for performing the functionality described herein. For example, the network node 1600 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1608. As a further example, the power source 1608 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

Embodiments of the network node 1600 may include additional components beyond those shown in Figure 16 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 1600 may include user interface equipment to allow input of information into the network node 1600 and to allow output of information from the network node 1600. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1600.

In some embodiments, different variants of network node 1600 can implement and/or host various network functions described herein, such as NEF, NRF, UDR, and SCP. In such embodiments, the components of network node 1600 can be configured to perform operations corresponding to methods (e.g., procedures) described herein as being performed by such entities.

Figure 17 is a block diagram of a host 1700, which may be an embodiment of the host 1416 of Figure 14, in accordance with various aspects described herein. As used herein, the host 1700 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1700 may provide one or more services to one or more UEs.

The host 1700 includes processing circuitry 1702 that is operatively coupled via a bus 1704 to an input/output interface 1706, a network interface 1708, a power source 1710, and a memory 1712. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 15 and 16, such that the descriptions thereof are generally applicable to the corresponding components of host 1700.

The memory 1712 may include one or more computer programs including one or more host application programs 1714 and data 1716, which may include user data, e g., data generated by a UE for the host 1700 or data generated by the host 1700 for a UE. Embodiments of the host 1700 may utilize only a subset or all of the components shown. The host application programs 1714 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1714 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1700 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 1714 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

Figure 18 is a block diagram illustrating a virtualization environment 1800 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1800 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

Applications 1802 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1800 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. For example, one or more of an NEF, NRF, UDR, and SCP described herein can be implemented as virtual nodes or virtual NFs in virtualization environment 1800.

Hardware 1804 includes processing circuitry, memory that stores software and/or instructions (collectively denoted computer program product 1804a) executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1806 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1808a and 1808b (one or more of which may be generally referred to as VMs 1808), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 1806 may present a virtual operating platform that appears like networking hardware to the VMs 1808.

The VMs 1808 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1806. Different embodiments of the instance of a virtual appliance 1802 may be implemented on one or more of VMs 1808, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, a VM 1808 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1808, and that part of hardware 1804 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1808 on top of the hardware 1804 and corresponds to the application 1802.

Hardware 1804 may be implemented in a standalone network node with generic or specific components. Hardware 1804 may implement some functions via virtualization. Alternatively, hardware 1804 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1810, which, among others, oversees lifecycle management of applications 1802. In some embodiments, hardware 1804 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1812 which may alternatively be used for communication between hardware nodes and radio units.

Figure 19 shows a communication diagram of a host 1902 communicating via a network node 1904 with a UE 1906 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1412a of Figure 14 and/or UE 1500 of Figure 15), network node (such as network node 1410a of Figure 14 and/or network node 1600 of Figure 16), and host (such as host 1416 of Figure 14 and/or host 1700 of Figure 17) discussed in the preceding paragraphs will now be described with reference to Figure 19.

Like host 1700, embodiments of host 1902 include hardware, such as a communication interface, processing circuitry, and memory. The host 1902 also includes software, which is stored in or accessible by the host 1902 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1906 connecting via an over-the-top (OTT) connection 1950 extending between the UE 1906 and host 1902. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1950.

The network node 1904 includes hardware enabling it to communicate with the host 1902 and UE 1906. The connection 1960 may be direct or pass through a core network (like core network 1406 of Figure 14) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

The UE 1906 includes hardware and software, which is stored in or accessible by UE 1906 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1906 with the support of the host 1902. In the host 1902, an executing host application may communicate with the executing client application via the OTT connection 1950 terminating at the UE 1906 and host 1902. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1950 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1950. The OTT connection 1950 may extend via a connection 1960 between the host 1902 and the network node 1904 and via a wireless connection 1970 between the network node 1904 and the UE 1906 to provide the connection between the host 1902 and the UE 1906. The connection 1960 and wireless connection 1970, over which the OTT connection 1950 may be provided, have been drawn abstractly to illustrate the communication between the host 1902 and the UE 1906 via the network node 1904, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

As an example of transmitting data via the OTT connection 1950, in step 1908, the host 1902 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1906. In other embodiments, the user data is associated with a UE 1906 that shares data with the host 1902 without explicit human interaction. In step 1910, the host 1902 initiates a transmission carrying the user data towards the UE 1906. The host 1902 may initiate the transmission responsive to a request transmitted by the UE 1906. The request may be caused by human interaction with the UE 1906 or by operation of the client application executing on the UE 1906. The transmission may pass via the network node 1904, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1912, the network node 1904 transmits to the UE 1906 the user data that was carried in the transmission that the host 1902 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1914, the UE 1906 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1906 associated with the host application executed by the host 1902.

In some examples, the UE 1906 executes a client application which provides user data to the host 1902. The user data may be provided in reaction or response to the data received from the host 1902. Accordingly, in step 1916, the UE 1906 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 1906. Regardless of the specific manner in which the user data was provided, the UE 1906 initiates, in step 1918, transmission of the user data towards the host 1902 via the network node 1904. In step 1920, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1904 receives user data from the UE 1906 and initiates transmission of the received user data towards the host 1902. In step 1922, the host 1902 receives the user data carried in the transmission initiated by the UE 1906.

One or more of the various embodiments improve the performance of OTT services provided to the UE 1906 using the OTT connection 1950, in which the wireless connection 1970 forms the last segment. More precisely, embodiments described herein can unambiguously inform a consumer NF (e.g., NEF) whether a UE has a 4G subscription, such that the consumer NF receives an address from which to obtain subscription-related information only when one exists. The consumer NF can refrain from further query signaling when no address is received, which reduces unnecessary signaling between NFs in the network and consequent degradation to network KPIs. Also, returning the address avoids the need to search for the UE identity in the 4G (e.g., EPC) domain, which can save significant computing resources when there is a large list of UEs/sub scribers to search. At a high level, embodiments facilitate deployment of networks with multiple domains (e g , 4G/EPC and 5G/5GC) and delivery of OTT services via such networks.

In an example scenario, factory status information may be collected and analyzed by the host 1902. As another example, the host 1902 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1902 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1902 may store surveillance video uploaded by a UE. As another example, the host 1902 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 1902 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.

In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1950 between the host 1902 and UE 1906, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1902 and/or UE 1906. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1950 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1950 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1904. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1902. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1950 while monitoring propagation times, errors, etc.

In examples discussed above, such as the examples discussed with reference to Figs. 6 to 9, a discovery request is sent from the network exposure function (NEF) to the network repository function (NRF) or from the service communication proxy (SCP) to the NRF. In each example discussed above, the discovery request identifies a particular UE and includes an indication of a first type of NF of the communication network and an indication of a second type of NF of the communication network to be checked when the NF producer profile is not available for the first type of NF. Upon receipt of the discovery request, the NRF is shown to communicate with the unified data repository (UDR) (i.e., using the 5GC UDR GroupIdMap service) to find a Groupld associated with the identified UE.

In some examples, however, the UDR may receive a GroupIdMap service request that does not identify a second type of NF to be checked when the NF producer profile is not available for the first type of NF. The GroupIdMap service request may be sent by any consumer (e g., any requesting network function (NF) of the communication network. In such examples, a policy may be consulted to determine whether or not the UDR is to check for a second type of NF when the NF producer profile is not available for the first type of NF.

Figure 20 shows a signaling diagram for a scenario where the UDR consults a policy and determines that a check for a second type of NF should be made.

As a pre-requisite or pre-condition, (operation 0), a policy is configured or provisioned in the UDR. The policy may define particular behaviours to be initiated or triggered in the UDR, for example in response to consulting the policy. In some examples, the act of configuring or provisioning the policy may itself cause UDR to follow or adopt the particular behaviours.

In operation 1, the UDR GroupIdMap service is used to find a GroupID associated with UE1. The GroupIdMap service request may be sent to the UDR by any consumer. Here, “any consumer” refers to any requesting NF, such as an NEF, an NRF, an SCP, or the like. The GroupIdMap service request sent to the UDR includes an identifier for the UE (i.e., UE1 in this case) and an indication of the first type of NF (i.e., UDM in this case).

In operation 2, the UDR consults the policy that was configured or provisioned in operation 0. In some examples, the policy may relate to a particular requesting NF. For example, the policy may apply when the requesting NF comprises an NEF. In other examples, the policy may apply generally, regardless of the requesting NF. The policy may specify whether or not the UDR is to check for a second type of NF when the NF producer profile is not available for the first type of NF. In the example shown in Figure 20, the policy stipulates that, responsive to determining that UE1 has no subscription provisioned in the first type of NF (i.e., UDM in this case), the UDR is to determine whether UE1 has a subscription provisioned in a second type of NF (i.e., HSS in this case).

In operation 3, the UDR sends a group mapping response to the requesting NF based on the policy. In this example, the UDR determines that there is no UDMGroupID associated with UE1 , but that there is an HSSGroupId associated with UE1. Thus, the response sent by the UDR to the requesting NF includes the HSSGroupID associated with UE1.

Figure 21 shows a signaling diagram for a scenario where a policy associated with the UDR stipulates that a check for a second type of NF should not be made.

Operation 0 in Figure 21 is similar to the corresponding operation in Figure 20 above. Specifically, a policy is configured or provisioned in the UDR.

In operation 1, the UDR Group IdMap service is used to find a GroupID associated with UE3. As in Figure 20, the Group IdMap service request shown in Figure 21 may be sent to the UDR by any consumer (e.g., any requesting NF).

In operation 2, the UDR consults the policy that was configured or provisioned in operation 0. In the example shown in Figure 21, the policy stipulates that, responsive to determining that UE2 has no subscription provisioned in the first type of NF (i.e., UDM in this case), the UDR is not to determine whether UE2 has a subscription provisioned in a second type of NF (i.e., HSS in this case). In other words, the UDR’s policy does not permit it to check for the second type of NF.

Accordingly, in operation 3, the UDR sends a group mapping response to the requesting NF based on the policy. In this example, the UDR determines that there is no UDMGroupID associated with UE2, but does not check whether there is an HSSGroupId associated with UE2. Thus, the response sent by the UDR to the requesting NF indicates that no GroupID is found for UE2. In an example, the UDR responds to NRF with “404 Not Found Error”.

Figure 22 shows a signaling diagram for a scenario where the UDR determines that the UE identifies in the GroupIdMap service request does have a subscription provisioned in the type of NF indicated in the request.

Operation 0 in Figure 22 is the same as the corresponding operation in Figures 20 and 21 above. Specifically, a policy is configured or provisioned in the UDR.

In operation 1, the GroupIdMap service request is sent to the UDR by any consumer (e.g., any requesting NF), to find a GroupID associated with UE3.

In operation 2, the UDR consults the policy that was configured or provisioned in operation 0. In this example, the UDR determines that there is a UDMGroupID associated with UE3 and, therefore, the UDR does not need to determine, from the policy, how it is to behave in the event that there is no UDMGroupID associated with UE3.

In operation 3, the UDR sends a group mapping response to the requesting NF which, in this example, includes the UDMGroupId.

In some examples, the policy may specify that the UDR is to determine whether the identified UE has a subscription provisioned in a second type of NF regardless of whether or not the UE is determined to have a subscription provisioned in the first type of NF. In such examples, in operation 3, the UDR may send a group mapping response to the requesting NF which includes the GroupID for the first type of NF (e g., the UDMGroupID) and the GroupID for the second type of NF (e.g., the HSSGroupId).

In other examples, a policy associated with the NRF (rather than the UDR) may specify whether or not a second type of NF should be included in a GroupIdMap service request sent to the UDR. In some examples, actions may be carried out in accordance with the policy associated with the NRF rather than in accordance with a policy associated with the UDR (as described above with reference to Figures 20-22) while in other examples, actions may be carried out in accordance with the policy associated with the NRF as well as in accordance with a policy associated with the

UDR.

Figure 23 shows a signaling diagram for a scenario where the NRF consults a policy and determines that a second type of NF should be included in a GroupIdMap service request sent to the UDR.

As a pre-requisite or pre-condition, (operation 0), a policy is configured or provisioned in the NRF. The policy may define particular behaviours to be initiated or triggered in the NRF, for example in response to consulting the policy. In some examples, the act of configuring or provisioning the policy may itself cause NRF to follow or adopt the particular behaviours.

In operation 1, the NRF receives an NRF discovery request for a UE. The discovery request includes an identifier for the UE (in this case, UE1) and an indication of a first type of NF (in this case, UDM) indicating a first domain to be checked for subscription credentials for

UEI . The discovery request may be sent to the NRF by any consumer. Here, “any consumer” refers to any requesting NF, such as an NEF, an SCP, or the like.

In operation 2, the NRF consults the policy that was configured or provisioned in operation 0. In some examples, the policy may relate to a particular requesting NF. For example, the policy may apply when the requesting NF comprises an NEF. In other examples, the policy may apply generally, regardless of the requesting NF. The policy may specify whether or not the NRF is include a second type of NF in a GroupIdMap service request to be sent to the UDR. The second type of NF may be included if it is intended that the second type of NF is to be checked when the NF producer profile is not available for the first type of NF. In the example shown in Figure 23, the policy stipulates that a second type of NF (i.e., HSS in this case) is to be included in the GroupIdMap service request to be sent by the NRF to the UDR.

In operation 3, the UDR GroupIdMap service is used to find a GroupID associated with UE1. The GroupIdMap service request is sent to the UDR by the NRF, and includes an identifier for the UE (i.e., UE1 in this case), an indication of the first type of NF (i.e., UDM in this case) and, in accordance with the policy associated with the NRF, an indication of the second type of NF (i.e., HSS in this case).

In operation 4, the UDR sends a group mapping response to the NRF. In this example, the UDR determines that there is a UDMGroupID associated with UE1 and, therefore, the response sent by the UDR to the NRF includes the UDMGroupID (e.g., a UDM profile) associated with UE1.

In operation 5, the NRF sends a discovery response to the requesting NF, based on the group mapping response received by the NRF from the UDR. In this example, the NRF sends a discovery response to the requesting NF that includes the UDMGroupID (e.g., a UDM profile) associated with UE1.

In other examples, the UDR may determine (in response to receiving the GroupIdMap service request sent by the NRF in operation 3) that there is no UDMGroupID associated with UE1, but there is an HSSGroupID associated with UE1. In such examples, the group mapping response sent by the UDR to the NRF may include a uniform resource identifier (URI) associated with a NF producer of the second type (i.e., a URI redirecting the requesting NF to the HSS producer).

It yet other examples, the UDR may determine (in response to receiving the GroupIdMap service request sent by the NRF in operation 3) that there is no UDMGroupID associated with the identified UE and no HSSGroupID associated with the identified UE (when it is specified by the policy that the second type of NF - here, the HSS - should be checked). In such examples, the the group mapping response sent by the UDR to the NRF may include an error message (e.g., “404 Not Found Error”).

Figure 24 shows a signaling diagram for a scenario where a policy associated with the NRF stipulates that a second type of NF should not be included in the GroupIdMap service request to be sent to the UDR.

Operation 0 in Figure 24 is similar to the corresponding operation in Figure 23 above. Specifically, a policy is configured or provisioned in the NRF. In operation 1, the NRF receives an NRF discovery request for UE2. As in Figure 23, the discovery request shown in Figure 24 may be sent to the NRF by any consumer (e.g., any requesting NF).

In operation 2, the NRF consults the policy that was configured or provisioned in operation 0. In the example shown in Figure 24, the policy stipulates that a second type of NF is not to be included in the GroupIdMap service request to be sent by the NRF to the UDR.

Accordingly, in operation 3, the NRF sends a GroupIdMap service request to the UDR that identifies the UE (i.e., UE2 in this example) and includes an indication of the first time of NF, which in this case is the UDMGroupID (e g., a UDM profile) associated with UE2

In operation 4, the UDR sends a group mapping response to the NRF. If the UDR determines that there is a UDMGroupID associated with UE2, then the group mapping response includes the UDMGroupID. However, since the policy specified that a second type of NF was not to be included in the GroupIdMap service request, if the UDR determines that there is no UDMGroupID associated with UE2, then the group mapping response includes an error message (e.g., “404 Not Found Error”).

In operation 5, the NRF sends a discovery response to the requesting NF, based on the group mapping response received by the NRF from the UDR.

Figure 25 is a flowchart illustrating an exemplary method (e.g., procedure) 2500 for a UDR of a communication network (e.g., 5GC), according to various embodiments of the present disclosure. At block 2502, the method 2500 may include receiving, from a requesting network function (NF) of the communication network, a group mapping request. The group mapping request may include an identifier of a user equipment (UE) and an indication of a first type of network function (NF) of the communication network. At block 2504, the method 2500 may include determining whether the UE has a subscription provisioned in the first type of NF. At block 2506, the method 2500 may include, responsive to determining that the UE has no subscription provisioned in the first type of NF, sending to the requesting NF a group mapping response based on a policy associated with the UDR. The signaling diagrams in Figures 20, 21 and 22 show specific examples of the method 2500 of Figure 25.

Figure 26 is a flowchart illustrating an exemplary method (e.g., procedure) 2600 for an NRF of a communication network (e.g., 5GC), according to various embodiments of the present disclosure. At block 2602, the method 2600 may include receiving, from a requesting network function (NF) of the communication network, a discovery request to identify a NF producer associated with a user equipment (UE). The discovery request may include an identifier of a user equipment (UE) and an indication of a first type of NF of the communication network. At block 2604, the method 2600 may include sending, to a unified data repository (UDR) of the communication network, a group mapping request based on a policy associated with the NRF. The signaling diagrams in Figures 23 and 24 show specific examples of the method 2600 of Figure 26.

Figure 27 shows a network node 2700 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. The network node 2700 may be operable as a core network node, a core network function or, more generally, a core network entity, such as the core network node 1408 described above with respect to Figure 14). Examples of network nodes in this context include core network entities such as one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), Policy Control Function (PCF) and/or a User Plane Function (UPF).

The network node 2700 includes processing circuitry 2702, a memory 2704, a communication interface 2706, and a power source 2708, and/or any other component, or any combination thereof. The network node 2700 may be composed of multiple physically separate components, which may each have their own respective components. In certain scenarios in which the network node 2700 comprises multiple separate components, one or more of the separate components may be shared among several network nodes.

The processing circuitry 2702 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 2700 components, such as the memory 2704, network node 2700 functionality. For example, the processing circuitry 2702 may be configured to cause the network node to perform operations described with reference to the core network functions illustrated in Figures 5 to 9 and 20 to 24, or to perform the methods as described with reference to Figures 10 to 13, 25 and 26.

The memory 2704 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 2702. The memory 2704 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 2702 and utilized by the network node 2700. The memory 2704 may be used to store any calculations made by the processing circuitry 2702 and/or any data received via the communication interface 2706. In some embodiments, the processing circuitry 2702 and memory 2704 is integrated.

The communication interface 2706 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE.

The power source 2708 provides power to the various components of network node 2700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 2708 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 2700 with power for performing the functionality described herein. For example, the network node 2700 may be connectable to an external power source (e g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 2708. As a further example, the power source 2708 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

Embodiments of the network node 2700 may include additional components beyond those shown in Figure 27 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 2700 may include user interface equipment to allow input of information into the network node 2700 and to allow output of information from the network node 2700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 2700.

The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in view of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the disclosure and can be thus within the spirit and scope of the disclosure. Various embodiments can be used together with one another, as well as interchangeably therewith, as should be understood by those having ordinary skill in the art. The term unit, as used herein, can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

As described herein, device and/or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor. Furthermore, functionality of a device or apparatus can be implemented by any combination of hardware and software. A device or apparatus can also be regarded as an assembly of multiple devices and/or apparatuses, whether functionally in cooperation with or independently of each other. Moreover, devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

In addition, certain terms used in the present disclosure, including the specification and drawings, can be used synonymously in certain instances (e.g., “data” and “information”). It should be understood, that although these terms (and/or other terms that can be synonymous to one another) can be used synonymously herein, there can be instances when such words can be intended to not be used synonymously. Further, to the extent that the prior art knowledge has not been explicitly incorporated by reference herein above, it is explicitly incorporated herein in its entirety. All publications referenced are incorporated herein by reference in their entireties.

The techniques and apparatus described herein include, but are not limited to, the following enumerated examples:

Cl. A method for a unified data repository (UDR) of a communication network, the method comprising: receiving, from a network repository function (NRF) of the communication network, a group mapping request that includes: an identifier of a user equipment (UE); and first and second types of network functions (NFs), of the communication network, to be checked for a NF producer profile associated with the UE; determining whether the UE has a subscription provisioned in each of the first and second types of NF; and when it is determined that the UE has no subscription provisioned in the first type of NF, sending to the NRF a group mapping response that includes one of the following: a group identifier associated with an NF producer of the second type, or an error message.

C2. The method of embodiment Cl, wherein: the first type of NF is a unified data management (UDM) function of a 5G core (5GC) network; and the second type of NF is a home subscriber server (HSS) of an Evolved Packet Core (EPC) network. C3. The method of embodiment C2, wherein the group identifier associated with the NF producer of the second type is a fully qualified domain name (FQDN) associated with an HSS in which the UE has a subscription provisioned

C4. The method of any of embodiments C1-C3, wherein when it is determined that the UE has no subscription provisioned in the first type of NF: the group identifier is sent when it is determined that the UE has a subscription provisioned in the second type of NF; and the error message is sent when it is determined that the UE has no subscription provisioned in the second type of NF.

DI. A method for a service communication proxy (SCP) of a communication network, the method comprising: receiving, from a network exposure function (NEF) of the communication network, a service request to identify a network function (NF) producer associated with a user equipment (UE), wherein the service request includes: an identifier of the UE, a first type of NF of the communication network, and a second type of NF of the communication network to be checked when an NF producer profile is not available for the first type of NF; sending the service request to a third network node or function (NNF) of the communication network, as a further message; and receiving from the third NNF a response to the further message that includes one of the following: an NF producer profile of an NF producer of the first type, a uniform resource identifier (URI) associated with an NF producer of the second type, or an error message.

Dla. The method of embodiment DI, wherein: the NF producer profile is received when an NF producer of the first type is identified; the URI is received when an NF producer of the second type is identified but an NF producer of the first type is not identified; and the error message is received when no NF producer of the first or second types is identified. D2. The method of any of embodiments Dl-Dla, wherein: the first type of NF is a unified data management (UDM) function of a 5G core (5GC) network; and the second type of NF is a home subscriber server (HSS) of an Evolved Packet Core (EPC) network.

D3. The method of embodiment D2, wherein the URI is at least part of a fully qualified domain name (FQDN) associated with an HSS in which the UE has a subscription provisioned

D4. The method of any of embodiments D1-D3, wherein the third NNF is a network repository function (NRF), the further message is a discovery request, and the response to the further message is a discovery response.

D5. The method of any of embodiments D1-D3, wherein the third NNF is a unified data repository (UDR), the further message is a group mapping request, and the response to the further message is a group mapping response.

D6. The method of any of embodiments D1-D5, further comprising forwarding the further message to the NEF in a service response.

D7. The method of any of embodiments D1-D6, wherein when the UE has no subscription provisioned in the first type of NF: the URI is received from the third NNF when the UE has a subscription provisioned in the second type of NF; and the error message is received from the first NNF when the UE has no subscription provisioned in the second type of NF.

Gl. A unified data repository (UDR) of a communication network, wherein: the UDR is implemented by communication interface circuitry and processing circuitry that are operably coupled; and the processing circuitry and interface circuitry are configured to perform operations corresponding to any of the methods of embodiments C1-C4. G2. A unified data repository (UDR) of a communication network, the UDR being configured to perform operations corresponding to any of the methods of embodiments C1-C4.

G3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry associated with a unified data repository (UDR) of a communication network, configure the UDR to perform operations corresponding to any of the methods of embodiments C1-C4.

G4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry associated with a unified data repository (UDR) of a communication network, configure the UDR to perform operations corresponding to any of the methods of embodiments C1-C4.

Hl. A service communication proxy (SCP) associated with a communication network, wherein: the SCP is implemented by communication interface circuitry and processing circuitry that are operably coupled; and the processing circuitry and interface circuitry are configured to perform operations corresponding to any of the methods of embodiments D1-D7.

H2. A service communication proxy (SCP) associated with a communication network, the SCP being configured to perform operations corresponding to any of the methods of embodiments D1-D7.

H3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry associated with a service communication proxy (SCP) associated with a communication network, configure the SCP to perform operations corresponding to any of the methods of embodiments D1-D7.

H4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry associated with a service communication proxy (SCP) associated with a communication network, configure the SCP to perform operations corresponding to any of the methods of embodiments D1-D7.

II. A method for a unified data repository (UDR) of a communication network, the method comprising: receiving, from a requesting network function (NF) of the communication network, a group mapping request that includes: an identifier of a user equipment (UE); and an indication of a first type of network function (NF) of the communication network; determining whether the UE has a subscription provisioned in the first type of NF; and responsive to determining that the UE has no subscription provisioned in the first type of NF, sending to the requesting NF a group mapping response based on a policy associated with the UDR.

12. The method of embodiment II, wherein the policy stipulates that the UDR is to check whether the UE has a subscription provisioned in a second type of NF, and the method further comprises: responsive to determining that the UE has no subscription provisioned in the first type of NF, determining whether the UE has a subscription provisioned in a second type of NF.

13. The method of embodiment 12, wherein, responsive to determining that the UE has a subscription provisioned in the second type of NF, the group mapping response comprises a group identifier associated with an NF producer of the second type.

14. The method of embodiment 12 or 13, wherein, responsive to determining that the UE has no subscription provisioned in the second type of NF, the group mapping response comprises an error message.

15. The method of embodiment II, wherein the policy stipulates that the UDR is not to check whether the UE has a subscription provisioned in a second type of NF; and wherein, responsive to determining that the UE has no subscription provisioned in the first type of NF, the group mapping response comprises an error message.

16. The method of embodiment II, wherein, responsive to determining that the UE has a subscription provisioned in the first type of NF, the method further comprises: sending to the requesting NF a group mapping response that includes a group identifier associated with an NF producer of the first type.

17. The method of any of embodiments 12-15, wherein: the first type of NF is a unified data management (UDM) function of a 5G core (5GC) network; and the second type of NF is a home subscriber server (HSS) of an Evolved Packet Core (EPC) network.

18. The method of embodiment 17, wherein the group identifier associated with the NF producer of the second type is a fully qualified domain name (FQDN) associated with an HSS in which the UE has a subscription provisioned.

19. The method of any of embodiments 11-18, further comprising: provisioning the policy in the UDR.

JI. A method for a network repository function (NRF) of a communication network, the method comprising: receiving, from a requesting network function (NF) of the communication network, a discovery request to identify a NF producer associated with a user equipment (UE), wherein the discovery request includes: an identifier of a user equipment (UE); and an indication of a first type of NF of the communication network; sending, to a unified data repository (UDR) of the communication network, a group mapping request based on a policy associated with the NRF.

J2. The method of embodiment JI, wherein the policy stipulates that the group mapping request is to include an indication of a second type of NF; wherein sending the group mapping request comprises sending a group mapping request that includes the indication of the second type of NF.

J3. The method of embodiment J2, further comprising: receiving, from the UDR, a group mapping response that includes one of the following: a group identifier associated with an NF producer of the first type or of the second type, or an error message.

J4. The method of embodiment J3, further comprising: sending, to the requesting NF, a discovery response that includes one of the following: an NF producer profile of an NF producer of the first type, a uniform resource identifier (URI) associated with an NF producer of the second type, or the error message.

J5. The method of embodiment J4, wherein: the NF producer profile is sent when the received group identifier is associated with an

NF producer of the first type; the URI is sent when the received group identifier is associated with the NF producer of the second type, and the error message is sent when no group identifier is received.

J6. The method of embodiment JI, wherein the policy stipulates that the group mapping request is not to include an indication of a second type of NF; wherein sending the group mapping request comprises sending a group mapping request that does not include the second type of NF.

J7. The method of any of embodiments J2-J6, wherein: the first type of NF is a unified data management (UDM) function of a 5G core (5GC) network; and the second type of NF is a home subscriber server (HSS) of an Evolved Packet Core (EPC) network.

J7. The method of any of embodiments J1-J6, further comprising: provisioning the policy in the NRF.

KI. A unified data repository (UDR) of a communication network, wherein: the UDR is implemented by communication interface circuitry and processing circuitry that are operably coupled; and the processing circuitry and interface circuitry are configured to perform operations corresponding to any of the methods of embodiments 11-19.

K2. A unified data repository (UDR) of a communication network, the UDR being configured to perform operations corresponding to any of the methods of embodiments 11-19. K3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry associated with a unified data repository (UDR) of a communication network, configure the UDR to perform operations corresponding to any of the methods of embodiments 11-19.

K4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry associated with a unified data repository (UDR) of a communication network, configure the UDR to perform operations corresponding to any of the methods of embodiments 11-19.

LI. A network repository function (NRF) associated with a communication network, wherein: the NRF is implemented by communication interface circuitry and processing circuitry that are operably coupled; and the processing circuitry and interface circuitry are configured to perform operations corresponding to any of the methods of embodiments J1-J7.

L2. A network repository function (NRF) associated with a communication network, the NRF being configured to perform operations corresponding to any of the methods of embodiments J1-J7.

L3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry associated with a network repository function (NRF) associated with a communication network, configure the NRF to perform operations corresponding to any of the methods of embodiments J1-J7.

L4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry associated with a network repository function (NRF) associated with a communication network, configure the NRF to perform operations corresponding to any of the methods of embodiments J1-J7.

Claims

1. A method for a network exposure function (NEF) of a communication network, the method comprising: sending (1010), to a first network node or function (NNF) of the communication network, a request to identify a network function (NF) producer associated with a user equipment (UE), wherein the request includes: an identifier of the UE, a first type of NF of the communication network, and a second type of NF of the communication network to be checked when an NF producer profile is not available for the first type of NF; and when the NF producer profile is not available for the first type of NF, receiving (1020) from the first NNF a response including one of the following: a uniform resource identifier (URI) associated with a NF producer of the second type, or an error message.

2. The method of claim 1, wherein: the first type of NF is a unified data management (UDM) function of a 5G core (5GC) network; and the second type of NF is a home subscriber server (HSS) of an Evolved Packet Core (EPC) network.

3. The method of claim 2, wherein the URI is at least part of a fully qualified domain name (FQDN) associated with an HSS in which the UE has a subscription provisioned.

4. The method of any of claims 1-3, wherein the first NNF is a network repository function (NRF), the request is a discovery request, and the response is a discovery response.

5. The method of any of claims 1-3, wherein the first NNF is a service communication proxy (SCP), the request is a service request, and the response is a service response.

6. The method of any of claims 1-5, further comprising based on receiving the error message, determining that the UE has no subscription provisioned in either the first or second type of NF in the communication network.

7. The method of any of claims 1-6, further comprising, when the URI associated with the NF producer of the second type is received, contacting the NF producer associated with the UE using the URI.

8. The method of any of claims 1-7, wherein the request to identify the NF producer associated with the UE further comprises a flag indicating that the second type of NF should be checked when an NF producer profile is not available for the first type of NF.

9. The method of any of claims 1-8, wherein when the UE has no subscription provisioned in the first type of NF: the URI is received from the first NNF when the UE has a subscription provisioned in the second type of NF; and the error message is received from the first NNF when the UE has no subscription provisioned in the second type of NF.

10. A method for a network repository function (NRF) of a communication network, the method comprising: receiving (1110), from a second network node or function (NNF) of the communication network, a discovery request to identify a network function (NF) producer associated with a user equipment (UE), wherein the discovery request includes: an identifier of the UE, a first type of NF of the communication network, and a second type of NF of the communication network to be checked when the NF producer profile is not available for the first type of NF; sending (1120), to a unified data repository (UDR) of the communication network, a group mapping request that includes the identifier of the UE and the first and second types of NFs; receiving (1130) from the UDR a group mapping response that includes one of the following: a group identifier associated with an NF producer of the first type or of the second type, or an error message; and sending (1140), to the second NNF, a discovery response that includes one of the following: an NF producer profile of an NF producer of the first type, a uniform resource identifier (URI) associated with an NF producer of the second type, or the error message.

11. The method of claim 10, wherein: the NF producer profile is sent when the received group identifier is associated with an NF producer of the first type; the URI is sent when the received group identifier is associated with the NF producer of the second type, and the error message is sent when no group identifier is received.

12. The method of any of claims 10-11, wherein sending the group mapping request is based on determining one of the following: that an NF producer profile for the first type of NF is not available at the NRF, or that an NF producer profile for the first type of NF is available at the NRF but does not include the identifier of the UE.

13. The method of any of claims 10-12, wherein: the first type of NF is a unified data management (UDM) function of a 5G core (5GC) network; and the second type of NF is a home subscriber server (HSS) of an Evolved Packet Core (EPC) network.

14. The method of claim 13, wherein: the group identifier associated with the NF producer of the second type is a fully qualified domain name (FQDN) associated with an HSS in which the UE has a subscription provisioned; and the URI comprises at least part of the FQDN.

15. The method of any of claims 10-14, wherein the second NNF is one of the following: a network exposure function (NEF) of a 5G core (5GC) network, or a service communication proxy (SCP) of a 5GC network.

16. The method of any of claims 10-15, wherein the second type of NF is included in the group mapping request based on the discovery request including a flag indicating that the second type of NF should be checked when an NF producer profile is not available for the first type of NF.

17. The method of any of claims 10-16, wherein when the UE has no subscription provisioned in the first type of NF: the group identifier associated with an NF producer of the second NF type is received from the UDR and the URI is sent to the second NNF, when the UE has a subscription provisioned in the second type of NF; and the error message is received from the UDR and sent to the second NNF, when the UE has no subscription provisioned in the second type of NF.

18. A method for a service communication proxy (SCP) of a communication network, the method comprising: receiving (1310), from a network exposure function (NEF) of the communication network, a service request to identify a network function (NF) producer associated with a user equipment (UE), wherein the service request includes: an identifier of the UE, a first type of NF of the communication network, and a second type of NF of the communication network to be checked when an NF producer profile is not available for the first type of NF; sending (1320) the service request to a third network node or function (NNF) of the communication network, as a further message; and receiving (1330) from the third NNF a response to the further message that includes one of the following: an NF producer profile of an NF producer of the first type, a uniform resource identifier (URI) associated with an NF producer of the second type, or an error message.

19. A network exposure function (NEF) associated with a communication network, wherein: the NEF is implemented by communication interface circuitry and processing circuitry that are operably coupled; and the processing circuitry and interface circuitry are configured to perform operations corresponding to any of the methods of claims 1-9.

20. A network exposure function (NEF) associated with a communication network, the NEF being configured to perform operations corresponding to any of the methods of claims 1-9.

21. A network repository function (NRF) associated with a communication network, wherein: the NRF is implemented by communication interface circuitry and processing circuitry that are operably coupled; and the processing circuitry and interface circuitry are configured to perform operations corresponding to any of the methods of claims 10-17.

22. A network repository function (NRF) associated with a communication network, the NRF being configured to perform operations corresponding to any of the methods of claims 10- 17.

23. A service communication proxy (SCP) associated with a communication network, the SCP being configured to perform operations corresponding to the method of claims 18.

24. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry associated with a network function (NF) associated with a communication network, configure the NF to perform operations corresponding to any of the methods of claims 1-18.

25. A computer program product comprising computer-executable instructions that, when executed by processing circuitry associated with a network function (NF) associated with a communication network, configure the NF to perform operations corresponding to any of the methods of claims 1-18.