Method and apparatus for network function discovery

By introducing 'Preferred-Candidates' query parameters in 5G networks, the mobility process between NF instances is optimized, and the signaling delay and low efficiency in the mobility process between NF instances is solved, and faster SMF and PCF selection is achieved. Improves the efficiency of the mobility process.

CN114303348BActive Publication Date: 2024-11-05TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080058459.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-08-21
Filing Date
2020-08-06
Publication Date
2024-11-05
Estimated Expiration
2040-08-06

AI Technical Summary

Technical Problem

In 5G networks, during the movement between NF instances, the target AMF needs to determine whether it is necessary to change or reselect SMF and PCF, resulting in signaling delay and inefficiency, especially affecting performance during the switching process.

Method used

The new query parameter ‘Preferred-Candidates’ is introduced, allowing network entities to include candidate network entity IDs in discovery requests, ensuring that instances that meet filtering criteria are preferred to be displayed in responses, improving efficiency.

Benefits of technology

By placing NF instances that comply with filtering criteria at the beginning of the response, the target AMF can quickly determine whether the current SMF and PCF need to be replaced or removed, significantly improving the efficiency and performance of the mobility process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114303348B_ABST
    Figure CN114303348B_ABST
Patent Text Reader

Abstract

The network entity generates a discovery request and sends the discovery request to a network repository entity NRE, wherein, advantageously, the discovery request comprises a set of query parameters, the set of query parameters comprising a set of candidate network entity identifiers (IDs), the set of candidate network entity IDs comprising at least a first candidate network entity ID (e.g., an I‑SMF instance ID), wherein each candidate network entity ID included in the set of candidate network entity IDs identifies a candidate network entity.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments related to network function (NF) discovery are disclosed. Background Art

[0002] Attached Figure 1

[0003] Figure 1 A reference point representation of an exemplary wireless communication system 100 is shown, which is represented as a 5G network architecture, which includes an access network (AN) (e.g., a radio AN (R(AN)) and a core network (CN) including network entities in the form of network functions (NFs). Typically, the AN includes a base station, such as, for example, an evolved Node B (eNB) or a 5G base station (gNB) or the like. Figure 1 As shown in FIG, a user equipment (UE) is connected to an AN and an access and mobility management function (AMF). Figure 1 As further shown in the figure, 5G CN NF includes: network slice selection function (NSSF), authentication server function (AUSF), unified data management (UDM), access and mobility management function (AMF), session management function (SMF), policy control function (PCF), and application function (AF).

[0004] The reference points of the 5G network architecture represent the detailed call flows used in the development of specification standardization. The N1 reference point is defined as carrying the signaling between the UE and the AMF. The N2 and N3 reference points are defined as carrying the signaling between the R(AN) and the AMF and between the R(AN) and the UPF, respectively. The N11 reference point is defined as carrying the signaling between the AMF and the SMF. The N4 reference point is defined as carrying the signaling between the SMF and the UPF. The N9 reference point is defined as carrying the signaling between different UPFs, and the N14 reference point is defined as carrying the signaling between different AMFs. Reference points N15 and N7 are defined as carrying the signaling between the PCF and the AMF and SMF, respectively. The N12 reference point is defined as carrying the signaling between the AMF and the AUSF. The N8 and N10 reference points are defined as carrying the signaling between the UDM and the AMF and SMF, respectively. The N13 reference point is defined as carrying the signaling between the AUSF and the UDM. The N22 reference point is defined as carrying the signaling between the NSSF and the AMF.

[0005] The 5G core network is designed to separate the user plane and the control plane. The user plane carries user traffic (e.g., user data), while the control plane carries signaling in the network. Figure 1In the NF, UPF is in the user plane, while other NFs, namely AMF, SMF, PCF, AF, AUSF and UDM, are in the control plane. Separating the user plane and the control plane allows the resources in each plane to be scaled independently. It also allows the UPF to be deployed separately from the control plane functions in a distributed manner. For example, for some applications that require low latency, the UPF can be deployed very close to the UE to shorten the round trip time (RTT) between the UE and the data network.

[0006] NFs in the 5G core network architecture are independent modular functions, which allow independent evolution and scaling. The modular functional design enables the 5G core network to support a variety of services in a flexible way.

[0007] Each NF in the core network interacts directly with another NF, but intermediate functions can be used to route messages from one NF to another.

[0008] Attached Figure 2

[0009] Figure 2 An exemplary wireless communication system 200 is shown, represented as a 5G network architecture, which uses a service-based interface (SBI) between NFs in the control plane instead of in the Figure 1 Point-to-point reference points / interfaces used in the 5G network architecture. Figure 1 The NF described corresponds to Figure 2 The services provided by the NF to other authorized NFs can be opened to these authorized NFs through SBI. Figure 2 In the SBI, SBI is indicated by letter "N" followed by the name of the NF, for example, Namf is used for SBI of AMF, Nsmf is used for SBI of SMF, etc. Figure 2 The Network Open Function (NEF) and NF Repository Function (NRF) in Figure 1 However, it should be clear that although Figure 1 There is no clear indication in Figure 1 All NFs described in can be used on demand with Figure 2 The NEF and NRF interact. Figure 1 The peer-to-peer architecture in Figure 2 The main difference between the service-based architecture in NF is that the service-based architecture does not have a predefined point-to-point interface between NFs. Instead, the NF in the service-based architecture queries the NRF to discover other NFs and communicates with other NFs via SBI.

[0010] Figure 1 and Figure 2Some characteristics of the NF shown in can be described in the following way. AMF provides UE-based authentication, authorization, mobility management, etc. Even if multiple access technologies are used, the UE is basically connected to one AMF because the AMF is independent of the access technology. SMF is responsible for session management and assigning IP addresses to the UE, as well as selecting and controlling UPF for data transmission about the UE. If the UE has multiple sessions, a different SMF can be assigned to each session to manage them separately and possibly provide different functions according to each session. AF provides information about packet flows to the PCF responsible for policy control in order to support quality of service (QoS). Based on this information, the PCF determines policies on mobility and session management so that the AMF and SMF work properly. AUSF supports authentication functions for the UE and therefore stores data for authentication or the like for the UE, while the UDM stores subscription data for the UE. The data network (DN), which is not part of the 5G core network, provides Internet access or operator services or the like.

[0011] NRF supports the following functions: 1) Maintaining NF profiles of available NF instances and their supported services; 2) Allowing other NF instances to subscribe to the registration of new NF instances of a given type in NRF and get notifications about them; and 3) Supporting discovery functions. It receives NF discovery requests from NF instances and provides information about available NF instances that meet certain search criteria. The features of NRF are specified in 3GPP Technical Specification (TS) 29.501 (see, e.g., 3GPP TS 29.501 v16.0.0).

[0012] In the 5G core network, multiple different types of 5G core network NFs are always instantiated by default, such as AMF, NRF, PCF, SMF, etc. Other 5G core network NFs can be instantiated on demand, and if necessary, several NFs of the same type can also be instantiated, for example to distribute the load to additional NFs of the same type. Therefore, an NF instance can be regarded as an example or specimen of a certain NF. In this document, the terms NF and NF instance can be used interchangeably, unless otherwise explicitly stated or obvious from the context in which these terms are used. An NF instance opens one or more NF service instances.

[0013] Attached Figure 3

[0014] Figure 3 is a message flow diagram illustrating an example of a network function service framework in a service-based 5G core network. The framework includes, among other things: 1) NF service registration process and 2) NF discovery and authentication process.

[0015] Registration Process

[0016] The core network NF instance in the service-based 5G core network registers its NF profile at the NRF. Therefore, NF2 (e.g., AMF) sends a registration request (Registration Request) to the NRF in action 300a, which includes the NF profile of the registered NF2. The NF profile is typically included in the request as a JavaScript Object Notation (JSON) object or other similar data object. The NF profile indicates one or more NF services supported by the registered NF instance. In this example, it is assumed that the registered NF2 supports the NF service marked as NF service A. Typically, the NF profile may include one or more of the following items for registering the NF: NF type, fully qualified domain name (FQDN) or IP address, name of the supported service, endpoint information of each supported service instance, and possible other service parameters. In action 300b, the NRF stores the NF profile of the registered NF and preferably marks the NF instance (i.e., NF2 in this example) as available. Furthermore, the NRF may send a Registration Response to NF2 in action 300c, which response may include the registered NF profile as confirmation of the registration performed by the NRF.

[0017] This registration may occur when the NF instance becomes effective for the first time or after activation of individual NF services within the NF instance, for example, triggered after a scaling operation. The NF instance may register / open one or more NF services. The information registered for each NF service may, for example, indicate security-related information that will be used to authorize the discovery of the NF instance, for example, security information indicating the NF that is allowed to discover each NF service, for example, a certain type of NF or a specific NF type that is allowed to discover the relevant NF service. However, a NF of known technology that does not generate / support any NF service will not register any service at the NRF. Therefore, a NF instance that only consumes one or more NF services will not register anything at the NRF.

[0018] Discovery and Authentication

[0019] When a first NF instance (e.g., NF1) in a service-based 5G core network intends to use an NF service supported by a second NF instance (e.g., NF2), the first NF instance will initiate an NF discovery process (also referred to as an NF service discovery process) with the NRF for the relevant NF service. Therefore, NF2 (e.g., SMF, AMF, etc.) sends a discovery request (Discover Request) to the NRF in action 302a, which includes discovery information. The discovery information may be included in the request as a JSON data object (e.g., a file) or the like. The discovery information indicates the expected service to be consumed by the discovery NF (e.g., NF service A mentioned above). Preferably, the discovery information indicates the service name or the like of the expected NF service. Additionally or alternatively, the discovery information may indicate one or more of the following: the NF type of the expected NF (i.e., the type of NF that is expected to generate the expected NF service) and / or the NF type of the discovery NF. In general, the NF type may be any one of, for example, NSSF, NEF, AUSF, AMF, PCF, SMF, UDM or AF or the like, unless otherwise stated in the context of mentioning the NF type.

[0020] The NRF authorizes the discovery request by determining whether the discovering NF (i.e., potential service consumer) is authorized to discover the intended NF service and / or the NF instance that is expected to produce the intended service - based on the discovery information provided in the discovery request and preferably also based on the profiles registered by the relevant intended target NF instance. Figure 3 Take action 302b in FIG. 2 as an example, where the intended target NF instance is NF2 and the potential service consumer is NF1.

[0021] For example, if the expected NF instance is deployed in a certain network slice, the NRF may authorize the discovery request based on the discovery configuration of the network slice (e.g., the expected NF instance may only be discovered by NFs in the same network slice, etc.).

[0022] When authorized, the NRF determines a set of one or more discovered NF instances that support the expected service and sends a response to the discovery request (also referred to as a "query response") to the requester NF (also referred to as a "service consumer"). Therefore, the NRF sends a response to NF1 in action 302c, which includes repository information indicating one or more discovered NF instances that support the expected service (i.e., can generate the expected service). The repository information may, for example, indicate one or more of the following: an FQDN, an IP address, and / or an endpoint address (e.g., a uniform resource locator (URL) or the like) for the one or more discovered NF instances. Summary of the invention

[0023] It has been proposed that during the discovery process, a Service Consumer may include some parameters to prune the response to the discovery request sent by the NRF ("Query Response"). For example, it has been accepted to extend the NFDiscover request with an optional query parameter ("limit") that defines the maximum number of NFProfiles to be returned in the response to the discovery request. A new query parameter ("max-payload-size") has also been accepted to enable the NF Instance to indicate to the NRF the maximum payload size that the NF Instance expects for the discovery response (e.g., based on a data store, cache, or HTTP message payload limit that the NF Instance can support). This allows the NRF to limit the number of NF Profiles it returns in the response, such as to not exceed the maximum payload size indicated by the NF Instance.

[0024] As described below, there are certain challenges.

[0025] During the inter-AMF mobility process for the UE, the target AMF may receive UE context information for the UE from the source AMF, the UE context information including: pcfId, smsfId, and sessionContextList including hsmfId and / or vsmfId. The target AMF also needs to consider whether the PCF, SMSF, or V-SMF needs to be changed, and in 3GPP Release 16 (Rel-16), based on the "Support for deployment topologies with specific SMF service areas" specified in subclause 4.23 in TS 23.502, the I-SMF may be changed, or if not, a new I-SMF may be inserted, or if the SMF can directly support the TAI where the UE resides, the I-SMF may be removed.

[0026] With the introduction of query parameters "limit" and "max-payload-size", which a service consumer can include in a discovery request (e.g., HTTP GET request), it is very likely that the NRF will not be able to return a complete list of NFs matching the filtering criteria included in the discovery request, because the NRF can only include a "limited" number of matching NF profiles and the message size should be less than the "max-payload-size".

[0027] 3GPP has introduced additional procedures to enable the requester to retrieve the complete list of matching profiles, however it requires additional signaling round trips (between the requesting NF instance and the NRF), which causes further delays in the signaling, for example, affecting the performance of mobility procedures, especially for handover procedures (which are more time sensitive).

[0028] On the other hand, in many inter-NF mobility procedures for UE, the target NF (e.g., the target AMF during the inter-AMF mobility procedure (N2 handover) as specified in subclause 4.23.7 ​​of 3GPP TS 23.502v16.1.0) needs to determine whether a new I-SMF or V-SMF needs to be selected for a given one of the UE's PDU sessions, or the existing I-SMF or V-SMF can be reused, and also determine whether a new PCF needs to be selected for access mobility policy control, or the existing PCF can continue to be used.

[0029] For example, during an inter-AMF N2 handover for a PDU session involving an I-SMF and an SMF, the target AMF needs to determine whether a new I-SMF needs to be selected, or whether the current I-SMF can continue to be used, or whether no I-SMF is needed when the UE enters a new tracking area (i.e., the I-SMF is removed and the AMF needs to reconnect to the SMF). As part of the N2 handover process, the target AMF will obtain the "target TAI" (i.e., the TAI of the new tracking area) and receive the current I-SMF ID and SMF ID.

[0030] According to the existing provisions in 3GPP TS 29.510v16.0.0, the target AMF can use the SMF ID to retrieve the service area of ​​the current SMF (which constitutes the TAI list), and then check whether the service area of ​​the current SMF includes the target TAI. If the service area of ​​the current SMF includes the target TAI, the current I-SMF is not needed, and the current I-SMF can be removed. If the service area of ​​the current SMF does not include the target TAI, the target AMF can use the I-SMF ID to retrieve the service area of ​​the current I-SMF (which includes the TAI list), and then check whether the service area of ​​the current I-SMF includes the target TAI. If the service area of ​​the current I-SMF includes the target TAI, the current I-SMF can be reused. If the service area of ​​the current I-SMF does not include the target TAI, the target AMF may send an NF discovery request to the NRF, which includes a filtering criterion that enables the NRF to return a set of SMF profiles to the AMF, wherein each SMF profile in the set of SMF profiles is used to serve the SMF instance of the TA identified by the target TAI. That is, the tracking area identifier of the filtering criterion is set to the target TAI, and the target NF type is set to SMF. Once the target AMF obtains a discovery response from the NRF, the target AMF can select one of the SMFs identified in the response as the new I-SMF.

[0031] Alternatively, instead of performing all the steps described in the previous paragraph, the target AMF may send a discovery request to the NRF, which discovery request includes filtering criteria that cause the NRF to return the profile of the SMF that serves the TA identified by the target TAI. Once the target AMF obtains the response from the NRF, the target AMF may check whether the profile of the current SMF and / or the current I-SMF is included in the returned set of profiles. If the profile of the current SMF is included in the returned set of profiles, the current I-SMF is not needed and the current I-SMF can be removed. If the profile of the current SMF is not included in the returned set of profiles but the profile of the current I-SMF is included therein, there is no need to select a new I-SMF. If the profile of the current SMF and the profile of the current I-SMF are not included in the returned set of profiles, the target AMF selects an SMF from a set of SMFs identified by the discovery response and sets the selected SMF as a new I-SMF.

[0032] The disadvantage of the above alternative is that there are a very large number of profiles that may match the filtering criteria, and therefore, the discovery response will likely contain a very large number of profiles. In addition, the profiles of the current SMF and the current I-SMF may be located at the very end of the profile array, which is very inefficient. In addition, there is a lack of a mechanism that allows a service consumer to retrieve more than one target NF. Therefore, if the target AMF needs to obtain the profile of the current SMF and the profile of the current I-SMF, the target AMF must send two separate discovery requests to the NRF, which is also very inefficient.

[0033] Therefore, the present disclosure proposes a mechanism that enables a network entity (e.g., NF, network node) to more efficiently determine whether a "preferred candidate" network entity matches a filtering criterion (i.e., meets the filtering criterion). For example, in one embodiment, the mechanism enables the target AMF to more quickly determine whether the current SMF and / or the current I-SMF serves the target tracking area. For example, in one embodiment, a discovery request (e.g., an NF discovery request) sent by a network entity to a network repository entity (NRE) (e.g., an instance of a 5G NRF or a similar repository function and / or node) includes a set of one or more query parameters, wherein the set of query parameters includes a set of N candidate network entity identifiers (IDs) (N>0), wherein each candidate network entity ID (e.g., a candidate NF instance ID) included in the set of candidate network entity IDs identifies a candidate network entity. The NRE generates a response to the discovery request and sends the response to the requesting network entity (also referred to as a "service consumer"), wherein the response includes a list of profiles that meet the filtering criteria in the discovery request. In one embodiment, the list is configured such that for each network entity ID included in the set of candidate network entity IDs, the profile of the network entity identified by the network entity ID is included in the beginning of the list (i.e., within the first N profiles of the list). In one embodiment, the profile of the network entity identified by the network entity ID included in the set of candidate network entity IDs is included in the beginning of the list regardless of whether the network entity identified by the network entity ID meets the filtering criteria.

[0034] Therefore, in a specific embodiment, a new query parameter of array type is proposed. This new query parameter can be named "Preferred-Candidates". The preferred candidate query parameter is intended to include a set of candidate network entity IDs. In one embodiment, the array includes a set of tuples, wherein each tuple includes: i) an indicator (e.g., a Boolean value) and ii) a corresponding candidate network entity ID, wherein the indicator indicates whether the profile of the network entity identified by the corresponding candidate network entity ID should be included in the returned matching profile list, regardless of whether the profile of the network entity meets the filtering criteria. Therefore, in one use case, the target AMF can send a discovery request to the NRE, and in addition to other query parameters (e.g., TAI and target-nf-type), the discovery request also includes a preferred candidate query parameter, and the preferred candidate query parameter contains the ID of the current I-SMF and / or the ID of the current SMF.

[0035] Therefore, in one aspect, a method performed by a network entity (e.g., AMF) is provided. The method includes: the network entity (e.g., an instance of AMF) generates a discovery request (e.g., an NF discovery request), wherein the discovery request includes a set of query parameters, the set of query parameters includes a set of candidate network entity IDs, the set of candidate network entity IDs includes at least a first candidate network entity ID (e.g., an I-SMF instance ID), wherein each candidate network entity ID included in the set of candidate network entity IDs identifies a candidate network entity. The method also includes: the network entity sends the discovery request to an NRE.

[0036] In another aspect, a method performed by an NRE is provided. The method includes: the NRE receives a discovery request sent by a network entity (e.g., an instance of an AMF), wherein the received discovery request includes a set of query parameters, the set of query parameters includes a set of candidate network entity identifiers (IDs), the set of candidate network entity IDs includes at least a first candidate network entity ID, wherein each candidate network entity ID included in the set of candidate network entity IDs identifies a candidate network entity. The method also includes: in response to the discovery request, the NRE sends a discovery response to the network entity.

[0037] The advantage of the above-mentioned embodiment is that the efficiency of the service consumer can be greatly improved. For example, in the use case where the target AMF needs to determine whether to replace or remove the current I-SMF, by including the ID of the current I-SMF in a set of candidate network entity IDs included in the discovery request, the AMF can more efficiently obtain the profile information and other profiles it needs to make this determination. In one embodiment, the NRE is configured to place the required profile information at the beginning of the profile list, rather than at a random position within the list. In another embodiment, the discovery response will include response parameters stating whether the current SMF meets the filtering criteria and whether the current I-SMF meets the filtering criteria. Therefore, in this embodiment, efficiency is improved because the target AMF can determine, for example, that the current I-SMF does not need to be replaced or removed, and the target AMF does not have to parse any profiles included in the matching profile list included in the discovery response. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The accompanying drawings, which are incorporated herein and constitute a part of the specification, illustrate various embodiments.

[0039] Figure 1 A wireless communication system represented as a 5G network architecture is shown, where the 5G network architecture consists of NFs using point-to-point reference points or interfaces.

[0040] Figure 2Shows the use of service-based interfaces (SBIs) between NFs in the control plane instead of Figure 1 5G network architecture of point-to-point reference points / interfaces used in the 5G network architecture.

[0041] Figure 3 is a message flow diagram illustrating an example of a network function service framework in a service-based 5G core network.

[0042] Figure 4 is a flow chart illustrating a process according to an embodiment.

[0043] Figure 5 is a message flow diagram illustrating an embodiment.

[0044] Figure 6 is a flow chart illustrating a process according to an embodiment.

[0045] Figure 7 is a block diagram of an apparatus according to an embodiment.

[0046] Fig. 8A is a block diagram of a NE according to an embodiment.

[0047] Figure 8B is a block diagram of an NRE according to an embodiment. DETAILED DESCRIPTION

[0048] Attached Figure 4

[0049] Figure 4 is a flow chart illustrating a process 400 according to an embodiment. The process 400 may start in step s402.

[0050] Step s402 includes: a first network entity 504 (or simply referred to as "NE 504") (eg, AMF) (see Figure 5 ) generates a discovery request 501, wherein the discovery request includes a set of query parameters. The set of query parameters includes a set of candidate network entity IDs including at least a first candidate network entity ID (e.g., an I-SMF instance ID), wherein each candidate network entity ID included in the set of candidate network entity IDs identifies a candidate network entity. In one embodiment, the set of query parameters further includes a filtering criterion, which is used by the NRE 502 (or simply referred to as "NRE 502") to determine network entities that meet the filtering criterion, and the set of candidate network entity IDs is not part of the filtering criterion.

[0051] Unless it is clear from the context in which the term is used, the network entity 504 may be, for example, Figure 2Any of the NSSF, NEF, NRF, PCF, UDM, AUSF, AMF, SMF or UPF shown in , or any other similar network function or node. The network entity can be implemented as a network element on dedicated hardware, or a software instance running on dedicated hardware, or a virtualized function instantiated on a suitable platform (e.g., cloud infrastructure). A virtualized function can be a function in which at least a portion of the function is implemented as a virtual component (e.g., via a virtual machine executed on one or more physical processing nodes in the network).

[0052] Step s404 includes: NE 504 sends a discovery request 501 to NRE 502. Discovery request 501 may be a Hypertext Transfer Protocol (HTTP) GET request including the set of query parameters (the GET request may also include a string "nnrf-disc" or other values ​​to indicate to the NRE that the requester NE 504 is invoking a discovery service procedure). In one embodiment, in addition to the query parameter including the set of candidate network entity IDs, other query parameters may be included in the GET request, including query parameters described in Table 6.2.3.2.3.1-1 of 3GPP TS 29.510 V16.0.0 ("TS 29.510").

[0053] Table 1 below provides a description of various query parameters that may be included in request 501 .

[0054]

[0055]

[0056]

[0057]

[0058]

[0059]

[0060]

[0061]

[0062]

[0063]

[0064] As shown above, one of the potential query parameters is the "Preferred-candidates" query parameter, which is an array of data objects of type NfCandidate. In one use case, the "Preferred-candidates" query parameter contains a set of candidate network entity identifiers. Therefore, in some embodiments, NfCandidate has the same definition as NfInstanceId, where the NfInstanceId is the id of the network entity. In other embodiments, the NfCandidate is defined as shown in Table 2 below.

[0065] Table 2-NfCandidate type definition

[0066]

[0067] As shown in Table 2, the "Preferred-candidates" query parameter of the discovery request 501 may include a set of tuples (i.e., [nfInstanceId, inclusionInd]), wherein each tuple includes: i) an inclusion indicator (also referred to as "inclusionInd"), which may be a Boolean value, and ii) a corresponding candidate network entity ID, wherein the inclusion indicator indicates whether the profile of the network entity identified by the corresponding candidate network entity ID should be included in the returned list of matching profiles, regardless of whether the profile of the network entity meets the filtering criteria in the discovery request 501. Therefore, in one use case, the target AMF may send a discovery request 501 including a Preferred-candidates query parameter to the NRE 502, wherein the query parameter includes, in addition to the filtering criteria (e.g., values ​​for the TAI and target-nf-type query parameters), the ID of the current I-SMF and / or the ID of the current SMF.

[0068] After receiving the discovery request 501, the NRE 502 searches for network entity profiles that meet the search criteria. In one embodiment, the search criteria are the same as the filtering criteria included in the discovery request 501. Therefore, in one embodiment, a profile that matches the search criteria will match the filtering criteria included in the discovery request 501. In another embodiment, the search criteria is based on the filtering criteria included in the discovery request 501, but is broader than the filtering criteria. For example, assume that a set of candidate network entity IDs includes two IDs: SMF-ID1 and SMF-ID2, and assume that the filtering criteria are: tai=target-TAI (i.e., the TAI where the UE is currently located) and target-nf-type=SMF. Under this assumption, in one embodiment, the search criteria (also referred to as a "search query") is: [(tai=target-TAI AND target-nf-type=SMF)OR(target-nf-instance-id=(SMF-ID1 OR SMF-ID2))]. This search query will return at least two profiles - namely, the profile of the SMF identified by SMF-ID1 and the profile of the SMF identified by SMF-ID2. In addition, this search query will return zero or more SMF profiles indicating that the SMF service area includes the target TAI (i.e., SMF profiles that meet the filtering criteria). After performing the search, in response to the request 501, the NRE 502 sends a discovery response 503 (e.g., an HTTP GET response) that includes at least some of the profiles that match the search criteria.

[0069] Therefore, step s406 (optional) includes: the NE 504 receiving the discovery response 503 from the NRE 502 (directly or indirectly).

[0070] In one embodiment, the set of candidate network entity IDs consists of N candidate network entity IDs (N>0), the discovery response 503 includes an array of M network entity profiles (M>N), and the NRE 502 is configured such that as a result of the first candidate network entity ID i) identifying a network entity that meets the filtering criteria and ii) being included in the set of N candidate network entity IDs, the NRE 502 places the network entity profile of the network entity identified by the first candidate network entity ID in one of the first N positions of the array of M network entity profiles. In this manner, the profiles of those candidate network entities that match the filtering criteria are placed in the beginning portion of the profile array included in the discovery response 503.

[0071] In another embodiment, response 503 includes a network entity profile array, which includes a first network entity profile corresponding to the first candidate network entity ID (i.e., the first network entity profile is a profile of the network entity identified by the first candidate network entity ID), and the first network entity profile is included in the network entity profile array regardless of whether the first network entity profile meets the filtering criteria.

[0072] In one embodiment, the set of candidate network entity IDs consists of N candidate network entity IDs (N>0), the network entity profile array includes M network entity profiles (M>N), and the NRE 502 includes the network entity profile corresponding to the first candidate network entity ID in one of the first N positions of the network entity profile array, regardless of whether the first candidate network entity ID identifies a physical entity that meets the filtering criteria (i.e., regardless of whether the network entity profile corresponding to the first candidate network entity ID meets the filtering criteria). In this way, the profiles of these candidate network entities are placed in the beginning of the profile array included in the response 503, regardless of whether the profiles of these candidate network entities meet the filtering criteria.

[0073] In one embodiment, the discovery response 503 includes a search result (SearchResult) data object, which includes a set of attribute values, and the set of attribute values ​​may include a network entity profile array. For example, in one embodiment, the SearchResult object may be defined as shown in the following table:

[0074] Table 3 Definition of type SearchResult

[0075]

[0076]

[0077] As shown above, one of the potential parameters in the SearchResult data object is a "canInfo" parameter, which is an array of data objects of type Caninfo. Each such data object includes at least one of the candidate network entity IDs that is included in the set of candidate network entity IDs included in request 501. In one embodiment, each candidate network entity ID included in request 501 is included in a canInfo object. An example definition of this Caninfo is shown in Table 4 below.

[0078] Table 4 Definition of Caninfo type

[0079]

[0080] As shown in Table 4, the "canInfo" parameter in the discovery response 503 may include a set of tuples (i.e., [candidate-nfInstanceId, matchFilter]), wherein each tuple includes: i) a matchFilter indicator, which may be a Boolean value, and ii) a corresponding candidate network entity ID, wherein the matchFilter indicator indicates whether the profile of the network entity identified by the corresponding candidate network entity ID matches the filtering criteria in the discovery request 501.

[0081] In the use case where the NE 504 is the target AMF, the process 400 may further include a step s401 that occurs before step s402. Step s401 includes: the target AMF 504 receives (directly or indirectly) a message 590 from the source AMF 506, the message 590 containing UE context information for a user equipment (UE) having an established PDU session, wherein the UE context information includes PDU context information associated with the PDU session, and the PDU context information includes a first session management function SMF ID that identifies a current anchor SMF for the PDU session and a second SMF ID that identifies a current intermediate SMF (I-SMF) for the PDU session. For example, the UE context information may include a data object of type PduSessionContext, wherein the PduSessionContext is defined as shown in the following table:

[0082] Table 5 Definition of PduSessionContext

[0083]

[0084]

[0085] As described above, in this use-specific example, the target AMF may send a discovery request 501 including a Preferred-Candidates query parameter to the NRE 502, the query parameter including the ID of the current I-SMF as obtained from the PduSessionContext data object (e.g., ismfId) and / or the ID of the current SMF as obtained from the PduSessionContext data object (e.g., hsmfId). In addition, the discovery request includes filtering criteria, such as a value for the TAI query parameter and a value for the target-nf-type query parameter (in this example, target-nf-type=SMF).

[0086] In an embodiment where the UE is in idle mode, the target AMF may receive a registration request sent by the UE, which may trigger the target AMF to send a request for context information for the UE to the source AMF 589. In an embodiment where the UE is in connected mode, the source AMF may receive a handover required message from a base station serving the UE, which may trigger the source AMF to send a message 590 containing context information for the UE to the target AMF.

[0087] In addition, in the use case where NE 504 is the target AMF, process 400 may further include steps s408, s410, and s412. In step s408, the target AMF uses the information provided by the discovery response 503 to determine whether the AMF needs to select a new SMF. In step s410, in response to determining that a new SMF needs to be selected, the AMF selects a new SMF, otherwise, the AMF will use the current SMF. For example, the target AMF may use the information provided by the discovery response 503 to determine that the current I-SMF should be removed or replaced.

[0088] For example, in the case where the PduSessionContext data object includes ismfId and hsmfId, the target AMF can use the information provided by the discovery response 503 to determine whether the SMF identified by ismfId and / or the SMF identified by hsmfId serves the tracking area where the UE is currently located (assuming that the filtering criteria include: tai=target Tracking Area and target-nf-type=SMF, and the group of entity IDs included in the discovery request includes ismfId and hsmfId). As described above, if the SMF identified by hsmfId serves the target tracking area, the SMF identified by ismfId can be removed (i.e., no intermediate SMF is required). In addition, if the SMF identified by hsmfId does not serve the target tracking area, but the SMF identified by ismfId serves the target tracking area, there is no need to select a new SMF, otherwise, a new intermediate SMF will need to be selected to replace the SMF identified by ismfId.

[0089] In one embodiment, the target AMF can determine whether the SMF identified by hsmfId serves the tracking area in which the UE is currently located by checking the canInfo data object included in the discovery response. More specifically, the canInfo data object includes a tuple, which includes a matchfilter value and an hsmfId, and the target AMF can determine whether the SMF identified by hsmfId serves the tracking area in which the UE is currently located (i.e., the "target" tracking area) by checking this matchFilter value, which will indicate whether the SMF identified by hsmfId matches the filtering criteria and, therefore, will indirectly indicate whether the SMF identified by hsmfId serves the target tracking area. Alternatively, if the discovery response 503 does not include a canInfo data object, the target AMF can traverse the SMF profile array that matches the filtering criteria to determine whether the SMF profile array includes the profile of the SMF identified by hsmfId. Advantageously, in one embodiment, the NRE 502 is configured such that if the profile of the SMF identified by hsmfId matches the filtering criteria, the NRE 502 will include the profile in the top portion of the profile array (e.g., within the first N positions of the array, where N is the number of network entity IDs included in the Preferred-Candidates query parameter). In this way, the target AMF needs to look at a maximum of N profiles within the array in order to determine whether the SMF identified by hsmfId serves the target tracking area. Using the same process as described above, the target AMF can also determine whether the SMF identified by ismfId serves the target tracking area.

[0090] Attached Figure 6

[0091] Figure 6 is a flow chart illustrating a process 600 performed by the NRE 502 according to an embodiment. The process 600 may start in step s602.

[0092] Step s602 includes: NRE 502 receives a discovery request 501 sent by NE 504, wherein the received discovery request includes a set of query parameters, the set of query parameters including a set of candidate network entity IDs. The set of candidate network entity IDs includes at least a first candidate network entity ID, wherein each candidate network entity ID included in the set of candidate network entity IDs identifies a candidate network. In some embodiments, the set of query parameters further includes a filtering criterion, which is used by NRE 502 to determine network entities that meet the filtering criterion, and the set of candidate network entity IDs is not part of the filtering criterion. Step s604 includes: NRE 502 sends a discovery response 503 to NE 504, which is performed in response to the discovery request 501 (i.e., the discovery response 503 includes an array of profiles that meet the filtering criteria included in the request 501).

[0093] In some embodiments, the set of candidate network entity IDs consists of N candidate network entity IDs (N>0), and the discovery response includes an array of M network entity profiles (M>N). In such embodiments, the process further includes: NRE 502 generates a discovery response, wherein generating the discovery response includes:

[0094] 1) NRE 502 determines a first candidate network entity ID that i) identifies a network entity that meets the filtering criteria and ii) is included in the set of N candidate network entity IDs; and

[0095] 2) As a result of determining that the first candidate network entity ID i) identifies a network entity that meets the filtering criteria and ii) is included in the set of N candidate network entity IDs, NRE 502 generates an array of M network entity profiles such that the network entity profile of the network entity identified by the first candidate network entity ID is located in one of the first N positions of the array of M network entity profiles. In this manner, the profiles of the candidate network entities are placed in the beginning portion of the profile array included in the response 503.

[0096] In another embodiment, generating the discovery response includes:

[0097] 1) The NRE 502 determines that the first candidate network entity ID is included in the set of N candidate network entity IDs; and

[0098] 2) As a result of determining that the first candidate network entity ID is included in the set of N candidate network entity IDs, NRE 502 generates a network entity profile array such that the network entity profile of the network entity identified by the first candidate network entity ID is located in one of the first N positions of the network entity profile array.

[0099] In some embodiments, the set of query parameters further includes an inclusion indicator value indicating whether the network entity profile corresponding to the first candidate network entity ID should be included in the profile array even if the network entity profile does not meet the filtering criteria.

[0100] In some embodiments, the discovery response 503 includes a data object (e.g., a canInfo data object) containing each of the candidate network entity IDs, and for each of the candidate network entity IDs, the data object further includes a matchFilter indicator corresponding to the candidate network entity ID, and each matchFilter indicator indicates whether the network entity profile of the candidate network entity identified by the corresponding candidate network entity ID meets the filtering criteria.

[0101] Attached Figure 7

[0102] In embodiments where NE 504 or NRE 502 is implemented in software, Figure 7 7 is a block diagram of a physical machine (or "device") 700 that may be used to run NE 504 and / or NRE 502 according to some embodiments. For example, device 700 may run a virtual machine that runs NE 504 or NRE 502. Figure 7As shown in , the device 700 may include: a processing circuit (PC) 702, which may include one or more processors (P) 755 (for example, a general-purpose microprocessor and / or one or more other processors, such as an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), etc.), which may be co-located in a single housing or a single data center, or may be geographically distributed (that is, the device 700 may be a distributed computing device); a network interface 748, which includes a transmitter (Tx) 745 and a receiver (Rx) 747 for enabling the device 700 to send data to and receive data from other machines connected to a network 110 (for example, an Internet Protocol (IP) network), wherein the network interface 748 is (directly or indirectly) connected to the network 110 (for example, the network interface 748 may be wirelessly connected to the network 110, in which case the network interface 748 is connected to an antenna device); and a local storage unit (also referred to as a "data storage system") 708, which may include one or more non-volatile storage devices and / or one or more volatile storage devices. In embodiments where the PC 702 includes a programmable processor, a computer program product (CPP) 741 may be provided. The CPP 741 includes a computer readable medium (CRM) 742 storing a computer program (CP) 743, which includes computer readable instructions (CRI) 744. The CRM 742 may be a non-transitory computer readable medium, such as a magnetic medium (e.g., a hard disk), an optical medium, a memory device (e.g., a random access memory, a flash memory), etc. In some embodiments, the CRI 744 of the computer program 743 is configured so that when executed by the PC 702, the CRI causes the device 700 to perform the steps described herein (e.g., the steps described herein with reference to the flowcharts). In other embodiments, the device 700 may be configured to perform the steps described herein without code. That is, for example, the PC 702 may consist of only one or more ASICs. Therefore, the features of the embodiments described herein may be implemented in hardware and / or software.

[0103] Attached Fig. 8A and 8B

[0104] Fig. 8A is a block diagram of a NE 504 according to some embodiments. As shown in FIG8 , in this embodiment, the NE 504 comprises: a generating unit 802 for generating a discovery request 501, and a sending unit 904 for sending the discovery request 501 to the NRE 502 using a transmitter. Figure 8B is a block diagram of NRE 502 according to some embodiments. Figure 8BAs shown in , in this embodiment, the NRE 502 includes: a receiving unit 812, which is used to receive the discovery request 501 using a receiver, and a sending unit 814, which is used to send the discovery response 503 to the NE 504 using a transmitter.

[0105] Some embodiments

[0106] Some of the embodiments described above can be summarized as follows:

[0107] 1. A method (400), comprising:

[0108] A network entity (504) (e.g., an NF instance) generates (s402) a discovery request (501), wherein the discovery request (501) comprises a set of query parameters, the set of query parameters comprises a set of candidate network entity identifiers ID, the set of candidate network entity IDs comprises at least a first candidate network entity ID (e.g., an I-SMF instance ID or other NF instance ID), wherein each candidate network entity ID included in the set of candidate network entity IDs identifies a candidate network entity; and

[0109] The network entity sends (s404) the discovery request to a network repository entity NRE (502) (eg, an instance of NRF).

[0110] 2. The method according to embodiment 1, wherein:

[0111] The set of query parameters further includes filtering criteria used by the NRE to determine network entities that meet the filtering criteria, and

[0112] The set of candidate network entity IDs is not part of the filtering criteria.

[0113] 3. The method of embodiment 2, further comprising: receiving (s406) a response to the query from the NRE, the response comprising an array of network entity profiles, wherein:

[0114] As a result of the first candidate entity ID i) identifying a network entity that meets the filtering criteria and ii) being included in the set of N candidate network entity IDs, the network entity profile corresponding to the first candidate network entity ID is placed in the beginning of the profile array.

[0115] 4. The method of embodiment 3 further comprises: receiving a response to the query from the NRE, wherein:

[0116] The set of candidate network entity IDs includes N candidate network entity IDs,

[0117] N is greater than or equal to 1,

[0118] The response to the discovery request comprises an array of M network entity profiles,

[0119] M is greater than N, and

[0120] The network entity profile corresponding to the first candidate network entity ID is placed in one of the first N positions of the network entity profile array.

[0121] 5. The method of embodiment 2 further comprises: receiving a response to the query from the NRE, wherein:

[0122] The response includes an array of network entity profiles, and

[0123] The network entity profile array includes a first network entity profile corresponding to the first candidate network entity ID, regardless of whether the first network entity profile meets the filtering criteria.

[0124] 6. The method of embodiment 5, wherein:

[0125] The set of candidate network entity IDs includes N candidate network entity IDs,

[0126] N is greater than or equal to 1;

[0127] The network entity profile array includes M network entity profiles,

[0128] M is greater than N, and

[0129] The first network entity profile corresponding to the first candidate network entity ID is included in one of the first N positions of the network entity profile array, regardless of whether the first network entity profile meets the filtering criteria.

[0130] 7. A method according to any one of embodiments 2-6, wherein the set of query parameters further includes an inclusion indicator value, wherein the inclusion indicator value indicates whether the network entity profile corresponding to the first candidate network entity ID should be included in the query result array even if the first candidate network entity ID does not identify a network entity that meets the filtering criteria.

[0131] 8. The method according to any one of embodiments 2-6, wherein:

[0132] The set of query parameters includes an array of tuples,

[0133] Each of the tuples included in the array includes: i) one of the candidate network entity IDs, and ii) a value indicating whether a network entity profile corresponding to the candidate network entity ID should be included in the query result array even if the candidate network entity ID included in the tuple does not identify a network entity that meets the filtering criteria.

[0134] 9. The method according to any one of embodiments 1-8 further comprises: the network entity (504) receiving UE context information for a user equipment UE that has initiated a registration procedure and has a protocol data unit PDU session from another network entity (506), wherein:

[0135] The UE context information includes PDU context information associated with the PDU session, and

[0136] The PDU context information includes a first session management function SMF ID identifying an anchor SMF for the PDU session and a second SMF ID identifying an intermediate SMF (I-SMF) for the PDU session.

[0137] 10. The method of any one of embodiments 1-9, wherein the network entity is an instance of an access and mobility management function.

[0138] 11. A method (600), comprising:

[0139] The network repository entity NRE (502) receives (s602) a discovery request sent by a network entity (504) (e.g., AMF), wherein the received discovery request comprises a set of query parameters, the set of query parameters comprises a set of candidate network entity identifiers ID, the set of candidate network entity IDs comprises at least a first candidate network entity ID, wherein each candidate network entity ID included in the set of candidate network entity IDs identifies a candidate network entity; and

[0140] In response to the discovery request, the NRE sends (s604) a discovery response to the network entity.

[0141] 12. The method according to embodiment 11, wherein:

[0142] The set of query parameters further includes filtering criteria used by the NRE to determine network entities that meet the filtering criteria, and

[0143] The set of candidate network entity IDs is not part of the filtering criteria.

[0144] 13. The method of embodiment 12, wherein:

[0145] The set of candidate network entity IDs includes N candidate network entity IDs,

[0146] N is greater than or equal to 1,

[0147] The discovery response includes an array of M network entity profiles,

[0148] M is greater than N, and

[0149] The method further includes: the NRE generating the discovery response, wherein generating the discovery response includes:

[0150] The NRE determines that the first candidate network entity ID i) identifies a network entity that meets the filtering criteria and ii) is included in the set of N candidate network entity IDs; and

[0151] As a result of determining that the first candidate network entity ID i) identifies a network entity that meets the filtering criteria and ii) is included in the set of N candidate network entity IDs, the NRE generates an array of the M network entity profiles such that the network entity profile corresponding to the first candidate network entity ID is located in one of the first N positions of the array of the M network entity profiles.

[0152] 14. The method of embodiment 12, wherein:

[0153] The set of candidate network entity IDs includes N candidate network entity IDs,

[0154] N is greater than or equal to 1,

[0155] The discovery response includes an array of network entity profiles, and

[0156] The method further includes: the NRE generating the discovery response, wherein generating the discovery response includes:

[0157] The NRE determines that the first candidate network entity ID is included in the set of N candidate network entity IDs; and

[0158] As a result of determining that the first candidate network entity ID is included in the set of N candidate network entity IDs, the NRE generates the network entity profile array so that the network entity profile corresponding to the first candidate network entity ID (i.e., the profile of the instance identified by the first candidate network entity ID) is located in one of the first N positions of the network entity profile array.

[0159] 15. A method according to any one of embodiments 12-14, wherein the set of query parameters further includes an inclusion indicator value, wherein the inclusion indicator value indicates whether the network entity profile corresponding to the first candidate network entity ID should be included in the query result array even if the first candidate network entity ID does not identify a network entity that meets the filtering criteria.

[0160] 16. The method according to any one of embodiments 12-14, wherein:

[0161] The set of query parameters includes an array of tuples,

[0162] Each of the tuples included in the array includes: i) one of the candidate network entity IDs, and ii) a value indicating whether a network entity profile corresponding to the candidate network entity ID should be included in the query result array even if the candidate network entity ID included in the tuple does not identify a network entity that meets the filtering criteria.

[0163] 17. The method according to any one of embodiments 11-16, wherein:

[0164] The discovery response includes a data object, which contains each of the candidate network entity IDs, and for each of the candidate network entity IDs, the data object further includes a match filter (matchFilter) indicator corresponding to the candidate network entity ID, and each matchFilter indicator indicates whether the network entity profile of the candidate network entity identified by the corresponding candidate network entity ID meets the filtering criteria.

[0165] 18. A computer program (743) comprising instructions (744) which, when executed by a processing circuit (702) of a device (700), cause the device (700) to perform a method (400, 600) according to any one of the above embodiments.

[0166] 19. A carrier embodying the computer program according to embodiment 18, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer-readable storage medium (742).

[0167] 20. An apparatus (700) adapted to:

[0168] generating a discovery request (501), wherein the discovery request (501) comprises a set of query parameters, the set of query parameters comprising a set of candidate network entity identifiers (IDs), the set of candidate network entity IDs comprising at least a first candidate network entity ID (e.g., an I-SMF instance ID), wherein each candidate network entity ID included in the set of candidate network entity IDs identifies a candidate network entity; and

[0169] The discovery request is sent to a network repository entity NRE (502) using a transmitter (745).

[0170] 21. A device (700) adapted to:

[0171] Receiving, using a receiver (747), a discovery request sent by a network entity NE (e.g., an instance of an AMF), wherein the received discovery request includes a set of query parameters, the set of query parameters including a set of candidate network entity identifiers ID, the set of candidate network entity IDs including at least a first candidate network entity ID, wherein each candidate network entity ID included in the set of candidate network entity IDs identifies a candidate network entity; and

[0172] In response to the discovery request, a discovery response is sent to the network entity using a transmitter (745).

[0173] 22. A network entity NE (504), the network entity comprising:

[0174] a generating unit (802) configured to generate a discovery request (501), wherein the discovery request (501) comprises a set of query parameters, the set of query parameters comprises a set of candidate network entity identifiers ID, the set of candidate network entity IDs comprises at least a first candidate network entity ID (e.g., an I-SMF instance ID), wherein each candidate network entity ID included in the set of candidate network entity IDs identifies a candidate network entity; and

[0175] The sending unit (804) is configured to use the transmitter (745) to send the discovery request to the network repository entity NRE (502).

[0176] 23. A network repository entity (NRE) (502), the NRE comprising:

[0177] a receiving unit (812) configured to use a receiver (747) to receive a discovery request sent by a network entity NE, wherein the received discovery request includes a set of query parameters, the set of query parameters includes a set of candidate network entity identifiers ID, the set of candidate network entity IDs includes at least a first candidate network entity ID, wherein each candidate network entity ID included in the set of candidate network entity IDs identifies a candidate network entity; and

[0178] The sending unit (814) is configured to send a discovery response to the network entity using a transmitter (745) in response to the discovery request.

[0179] Although various embodiments of the present disclosure are described herein, it should be understood that they are presented in an exemplary and non-restrictive manner only. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above-mentioned exemplary embodiments. Generally, all terms used in this article should be interpreted according to their common meaning in the relevant technical field, unless clearly given and / or different meanings are implied from the context in which it is used. Unless otherwise clearly stated, indefinite article "one (a)" should be openly interpreted as meaning "at least one". Unless otherwise stated in this article or clearly contradictory with context, the present disclosure covers any combination of all possible variations of the elements described above.

[0180] In addition, although the processes described above and illustrated in the accompanying drawings are shown as a series of steps, this is done for illustration purposes only. Therefore, it is contemplated that some steps may be added, some steps may be omitted, the order of the steps may be rearranged, and some steps may be performed in parallel. That is, the steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as being after or before another step and / or one of the steps is inherently required to be after or before another step.

Claims

1. A method (400) performed by a network entity (504), the method comprising: The network entity (504) generates (s402) a discovery request (501), wherein the discovery request (501) comprises a set of query parameters, the set of query parameters comprising at least a first candidate network entity identifier ID, wherein each candidate network entity ID identifies a candidate network entity, wherein the set of query parameters further comprises a filtering criterion, the filtering criterion being used by a network repository entity NRE to determine network entities that meet the filtering criterion, wherein the candidate network entity ID is not part of the filtering criterion; The network entity sends (s404) the discovery request to the NRE (502); and A discovery response (503) to the discovery request is received (s406) from the NRE, the discovery response comprising a search result data object and a matching filter indicator, wherein the search result data object comprises a network entity profile array and comprises a data object at least including the at least first candidate network entity ID, the network entity profile array comprises a first network entity profile corresponding to the candidate network entity ID, and the matching filter indicator indicates whether the network entity profile of the candidate network entity identified by the corresponding candidate network entity ID meets the filtering criteria.

2. The method according to claim 1, further comprising: receiving (s406) a response to the query from the NRE, the response comprising an array of network entity profiles, wherein: As a result of the first candidate network entity ID identifying a network entity that meets the filtering criteria and being included in the set of N candidate network entity IDs, the network entity profile corresponding to the first candidate network entity ID is placed in the beginning of the profile array.

3. The method according to claim 2, further comprising: receiving a response to the query from the NRE, wherein: The set of candidate network entity IDs includes N candidate network entity IDs, N is greater than or equal to 1, The response to the discovery request comprises an array of M network entity profiles, M is greater than N, and The network entity profile corresponding to the first candidate network entity ID is placed in one of the first N positions of the network entity profile array.

4. The method according to claim 1, further comprising: receiving a response to the query from the NRE, wherein: The response includes an array of network entity profiles, and The network entity profile array includes a first network entity profile corresponding to the first candidate network entity ID, regardless of whether the first network entity profile meets the filtering criteria.

5. The method according to claim 4, wherein: The set of candidate network entity IDs includes N candidate network entity IDs, N is greater than or equal to 1; The network entity profile array includes M network entity profiles, M is greater than N, and The first network entity profile corresponding to the first candidate network entity ID is included in one of the first N positions of the network entity profile array, regardless of whether the first network entity profile meets the filtering criteria.

6. The method according to any one of claims 1 to 5, wherein: The set of query parameters further includes an inclusion indicator value indicating whether a network entity profile corresponding to the first candidate network entity ID should be included in the query result array even if the first candidate network entity ID does not identify a network entity that meets the filtering criteria.

7. The method according to any one of claims 1 to 5, wherein: The set of query parameters comprises an array of tuples, Each of the tuples included in the array includes: one of the candidate network entity IDs, and a value indicating whether a network entity profile corresponding to the candidate network entity ID should be included in the query result array even if the candidate network entity ID included in the tuple does not identify a network entity that meets the filtering criteria.

8. The method according to any one of claims 1 to 5, further comprising: The network entity (504) receives UE context information for a user equipment UE that has initiated a registration procedure and has a protocol data unit (PDU) session from another network entity (506), wherein: The UE context information includes PDU context information associated with the PDU session, and The PDU context information includes a first session management function SMF ID identifying an anchor SMF for the PDU session and a second SMF ID identifying an intermediate SMF (I-SMF) for the PDU session.

9. The method according to any one of claims 1 to 5, wherein: The network entities are instances of access and mobility management functions.

10. A method (600) performed by a network repository entity (NRE) (502), the method comprising: The NRE (502) receives (s602) a discovery request (501) sent by a network entity (504), wherein the received discovery request comprises a set of query parameters, the set of query parameters comprising at least a first candidate network entity identifier (ID), wherein each candidate network entity ID identifies a candidate network entity, wherein the set of query parameters further comprises a filtering criterion, the filtering criterion being used by the NRE to determine network entities that meet the filtering criterion, wherein the candidate network entity ID is not part of the filtering criterion; and In response to the discovery request, the NRE sends (s604) a discovery response (503) to the network entity, the discovery response comprising a search result data object and a matching filter indicator, wherein the search result data object comprises a network entity profile array and comprises a data object at least containing the at least first candidate network entity ID, the network entity profile array comprises a first network entity profile corresponding to the candidate network entity ID, and the matching filter indicator indicates whether the network entity profile of the candidate network entity identified by the corresponding candidate network entity ID meets the filtering criteria.

11. The method according to claim 10, wherein: The set of candidate network entity IDs includes N candidate network entity IDs, N is greater than or equal to 1, The discovery response includes an array of M network entity profiles, M is greater than N, and The method further includes: the NRE generating the discovery response, wherein generating the discovery response includes: The NRE determines that the first candidate network entity ID identifies a network entity that meets the filtering criteria and is included in the set of N candidate network entity IDs; and As a result of determining that the first candidate network entity ID identifies a network entity that meets the filtering criteria and is included in the set of N candidate network entity IDs, the NRE generates an array of the M network entity profiles so that the network entity profile corresponding to the first candidate network entity ID is located in one of the first N positions of the array of the M network entity profiles.

12. The method according to claim 10, wherein: The set of candidate network entity IDs includes N candidate network entity IDs, N is greater than or equal to 1, The discovery response includes an array of network entity profiles, and The method further includes: the NRE generating the discovery response, wherein generating the discovery response includes: The NRE determines that the first candidate network entity ID is included in the set of N candidate network entity IDs; and As a result of determining that the first candidate network entity ID is included in the set of N candidate network entity IDs, the NRE generates the network entity profile array so that the network entity profile corresponding to the first candidate network entity ID (i.e., the profile of the instance identified by the first candidate network entity ID) is located in one of the first N positions of the network entity profile array.

13. The method according to any one of claims 10 to 12, wherein: The set of query parameters further includes an inclusion indicator value indicating whether a network entity profile corresponding to the first candidate network entity ID should be included in the query result array even if the first candidate network entity ID does not identify a network entity that meets the filtering criteria.

14. The method according to any one of claims 10 to 12, wherein: The set of query parameters comprises an array of tuples, Each of the tuples included in the array includes: one of the candidate network entity IDs, and a value indicating whether a network entity profile corresponding to the candidate network entity ID should be included in the query result array even if the candidate network entity ID included in the tuple does not identify a network entity that meets the filtering criteria.

15. A computer program product comprising a computer program (743) comprising instructions (744) which, when executed by a processing circuit (702) of an apparatus (700), cause the apparatus (700) to perform a method (400, 600) according to any one of claims 1 to 14.

16. A computer-readable storage medium having stored thereon instructions (744) which, when executed by processing circuitry (702) of a device (700), cause the device (700) to perform the method (400, 600) according to any one of claims 1-14.

17. A network entity NE (504), the network entity comprising: a generating unit (802) configured to generate a discovery request (501), wherein the discovery request (501) comprises a set of query parameters, the set of query parameters comprises a set of candidate network entity identifiers ID, the set of candidate network entity IDs comprises at least a first candidate network entity ID, wherein each candidate network entity ID included in the set of candidate network entity IDs identifies a candidate network entity, wherein the set of query parameters further comprises a filtering criterion, the filtering criterion is used by a network repository entity NRE to determine a network entity that meets the filtering criterion, wherein the set of candidate network entity IDs is not part of the filtering criterion; A sending unit (804) configured to send the discovery request to the NRE (502) using a transmitter (745); and Receive (s406) a response to the discovery request from the NRE, the response comprising a search result data object, the search result data object comprising a network entity profile array and comprising a data object containing each of the candidate network entity IDs, the network entity profile array comprising a first network entity profile corresponding to the candidate network entity ID, and for each of the candidate network entity IDs, the data object further comprising a matching filter indicator corresponding to the candidate network entity ID, wherein the matching filter indicator indicates whether the network entity profile of the candidate network entity identified by the corresponding candidate network entity ID meets the filtering criteria.

18. A network repository entity (NRE) (502), the NRE comprising: a receiving unit (812) configured to receive, using a receiver (747), a discovery request sent by a network entity NE, wherein the received discovery request includes a set of query parameters, the set of query parameters includes a set of candidate network entity identifiers ID, the set of candidate network entity IDs includes at least a first candidate network entity ID, wherein each candidate network entity ID included in the set of candidate network entity IDs identifies a candidate network entity, wherein the set of query parameters further includes a filtering criterion, the filtering criterion is used by the NRE to determine a network entity that meets the filtering criterion, wherein the set of candidate network entity IDs is not part of the filtering criterion; and A sending unit (814) is configured to send a discovery response to the network entity using a transmitter (745) in response to the discovery request, the discovery response comprising a search result data object, the search result data object comprising a network entity profile array and comprising a data object containing each of the candidate network entity IDs, the network entity profile array comprising a first network entity profile corresponding to the candidate network entity ID, and for each of the candidate network entity IDs, the data object further comprising a matching filter indicator corresponding to the candidate network entity ID, wherein the matching filter indicator indicates whether the network entity profile of the candidate network entity identified by the corresponding candidate network entity ID meets the filtering criteria.