WO2024149041A1

WO2024149041A1 - Methods, network nodes, media for nf discovery enhancement

Info

Publication number: WO2024149041A1
Application number: PCT/CN2023/140575
Authority: WO
Inventors: Qiuxiang ZHU; Yong Yang; Peng Li; Aleksejs UDALCOVS; Yunjie Lu
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2023-01-09
Filing date: 2023-12-21
Publication date: 2024-07-18

Abstract

Methods (500; 600; 700), network nodes (1000, 1100; 1200, 1300; 1200', 1300'), and computer readable storage media for NF discovery enhancement are disclosed. The method (500) performed by a first network node (1000, 1100) includes: receiving (S501), from a second network node, a first discovery request that comprises a query parameter having a plurality of values to be satisfied by NF (s) and an indication indicating a capability of receiving an aggregation of NFs of a requested target NF type and a subset of the plurality of values of the query parameter that are not satisfied by any NF of the requested target NF type that is registered in the first network node and determining (S503) that a subset of values from the plurality of values of the query parameter are not satisfied by any NF of the requested target NF type that is registered in the first network node.

Description

METHODS, NETWORK NODES, MEDIA FOR NF DISCOVERY ENHANCEMENT

TECHNICAL FIELD

The present disclosure relates to wireless communications, and in particular, to methods, network nodes, and computer readable storage media for Network Function (NF) discovery enhancement.

BACKGROUND

This section is intended to provide a background to the various embodiments of the technology described in this disclosure. The description in this section may include concepts that could be pursued, but are not necessarily ones that have been previously conceived or pursued. Therefore, unless otherwise indicated herein, what is described in this section is not prior art to the description and/or claims of this disclosure and is not admitted to be prior art by the mere inclusion in this section.

Currently, the NF discovery procedure enables an NF to discover a list of candidates NF instance (s) where each NF instance matches all query parameters except those query parameters that are defined as preferred parameters.

As specified in Section 6.2.3.2.3 of 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 29.510 v18.3.0: “The default logical relationship among the query parameters is logical “AND” , i.e., all the provided query parameters shall be matched, with the exception of the “preferred-locality” , “ext-preferred-locality” , “preferred-nf-instances” , “preferred-tai” , “preferred-api-versions” , “preferred-full-plmn” , “preferred-collocated-nf-types” , “preferred-pgw-ind” , “preferred-analytics-delays” , “preferred-features” and “mbs-session-id” query parameters (see Table 6.2.3.2.3.1-1 of 3GPP TS 29.510 v18.3.0) .

For example, when the query parameter contains a list of Tracking Area Identities (TAIs) (using “tai-list” ) , the Network Repository Function (NRF) shall ONLY return candidate NFs which support all the TAIs in the list.

However, there are several use cases where not always a single NF instance can be a candidate, i.e. to satisfy all the elements in an array or map type of query parameter.

For example:

- for time synchronization service, there might be cases when a spatial validity condition includes Tracking Areas (TAs) that are served by different Access and Mobility Management Functions (AMFs) , i.e., a single AMF does not serve all TAs in the spatial validity condition.

- for Multicast/Broadcast Service (MBS) , it is likely that the MBS service area for an MBS session includes a list of TAs that are served by different AMFs, i.e., a single AMF does not serve all TAs in the MBS service area.

The current discovery function, i.e., using “tai” , or “tai-list” or “preferred-tai” , does not enable the NRF to return a list of AMFs where none of AMFs itself supports all TAIs included in the query request but together all these AMFs will support all TAIs included in the query request.

Note that those preferred query parameters, e.g., “preferred-tai” , doesn’ t help, since the NF service consumer (doing discovery) would like to find a candidate that SHALL support all query parameters, e.g. ALL TAIs.

In addition, there may be multiple NRFs deployed in a Public Land Mobile Network (PLMN) .

For example, as currently specified for Nnrf_NFDiscovery Service, when multiple NRFs are deployed in a PLMN, these NRFs may be deployed in a multiple-NRF architecture, e.g., deployed hierarchically as exemplarily shown in FIG. 1. In the example of FIG. 1, NRF A is a higher layer NRF, and NRF 1 and NRF 2 respectively register themselves in NRF A as lower layer NRFs.

In such a multiple-NRF deployment as shown in FIG. 1, when an NF service consumer, e.g. a Multicast/Broadcast Session Management Function (MB-SMF) 1x, registered in NRF 1 needs to establish a broadcast MBS session in a number of Tracking Areas, it likely requires to consume a service (e.g. Namf_MBSBroadcast service) offered from a target NF (e.g. AMF 1x controlling a subset of the desired tracking areas) registered in an NRF (e.g. NRF 1) , but also from another target NF (e.g. AMF 2x controlling another subset of the desired tracking areas) registered in another NRF (e.g. NRF 2) . Both AMF 1x and AMF 2x need to be discovered to satisfy the service requirement to establish the broadcast MBS session in the desired tracking area.

As further exemplarily illustrated in FIG. 2, it is assumed NRF A is a higher layer NRF, and NRF 1, NRF 2 and NRF 3 respectively register themselves in NRF A as lower layer NRFs. AMF 1x registered in NRF 1 controls TA1-TA5, AMF 2x registered in NRF 2 controls TA6-TA10, and AMF 3x registered in NRF 3 controls TA11-TA15.

NRF A may learn that NRF 1 should be contacted to discover AMF, i.e., AMF 1x in this example, serving TA1-TA5, since NRF 1's nrfInfo contains servedAmfInfo. The same does for NRF 2 and NRF 3, for TA6-TA10 and TA11-TA15, respectively.

The MB-SMF 1x registered in NRF1 may require to setup a Broadcast MBS session in Tracking Areas TA1, TA2, TA3, TA9, TA10, TA12 and TA13, so it needs to find corresponding AMFs controlling Tracking Areas TA1, TA2, TA3, TA9, TA10, TA12 and TA13, in order to consume Namf_MBSBroadcast service offered by the target AMF (s) .

Thus, MB-SMF 1x needs to discover AMF 1x, AMF 2x and AMF 3x, wherein AMF 1x, AMF 2x and AMF 3x altogether can offer the service required by the MB-SMF 1x to establish the Broadcast MBS session.

In the exemplary multiple-NRF deployment in FIG. 2, however, the (local) NRF (contacted by the NF service consumer) , i.e., NRF 1, will likely reject the discovery request from the NF service consumer, e.g., the MB-SMF 1x, since NRF 1 doesn’ t have any AMF registered to serve TA9, TA10, TA12 and TA13. In particular, NRF 1 will use the SAME discovery request as it received from the NF service consumer to communicate to NRF A, regardless of whether NRF A is served in immediate redirect or forwarding. It should be noted that NRF1 cannot modify the discovery request. As such, NRF 1 will reject the discovery request from the MB-SMF 1x since the discovery request contains a query parameter, such as “tai-list” or “tai-list-for-nf-aggre” , that has some values beyond NRF 1’s knowledge (in this example, NRF 1 knows that only TA1-TA5 are served by AMF 1x) .

In addition, if the MB-SMF 1x does not utilize such a query parameter with a list of different values in the discovery request, but uses only service-name (e.g., “Namf_MBSBroadcast” ) in order to find all AMFs but registered in the (local) NRF, i.e., NRF1, the MB-SMF 1x can only find AMF 1x serving TA1-TA5, but cannot find any AMF for TA9, TA10, TA12 and TA13, since NRF 1 only knows that TA1-TA5 are served by AMF 1x registered in it (i.e., NRF1) but does not know which of other TA values are served by which AMF(s) that is registered in other NRF (s) .

It is thus desired to solve at least some of the above problems.

SUMMARY

In order to at least solve the problems as described above, the present disclosure proposes an enhancement to the NF service discovery procedure, in which a first NRF receiving, from an NF service consumer, a discovery request including a query parameter having a plurality of values (asubset of which cannot be supported by any NF registered in the first NRF) may separately process those values of the query parameter in the discovery request, returning a list of NFs registered in the first NRF that can support some of those values, and transmitting (either forwarding from the NF service consumer, or generating and transmitting by the first NRF itself) , to a second NRF, a new discovery request including the query parameter having said subset of values that cannot be supported by any NF registered in the first NRF, in order to find other list (s) of NFs registered in other NRF (s) that can support said subset of values that cannot be supported by any NF registered in the first NRF. As such, a set of NFs, that may be registered at different NRFs and these NFs altogether can satisfy ALL values of the query parameter included in the NF discovery request, may be retrieved as one of candidate NF aggregation.

According to a first aspect of the present disclosure, a method performed by a first network node for NF discovery is provided. The method may comprise receiving, from a second network node, a first discovery request that comprises a query parameter having a plurality of values to be satisfied by NF (s) and an indication indicating a capability of receiving an aggregation of NFs of a requested target NF type and a subset of the plurality of values of the query parameter that are not satisfied by any NF of the requested target NF type that is registered in the first network node. The method may comprise determining that a subset of values from the plurality of values of the query parameter are not satisfied by any NF of the requested target NF type that is registered in the first network node.

In an embodiment, the method may comprise transmitting, to the second network node, a first discovery response to the first discovery request. The first discovery response comprises said subset of values.

In an embodiment, the first discovery response may comprise a third list with a number of NFs of the requested target NF type whose registration information is known by the first network node and supporting the plurality of values, excluding said subset of values, of the query parameter.

In an embodiment, the method may comprise transmitting, to a third network node, a second discovery request that comprises the query parameter having said subset of values and the indication indicating said capability.

In an embodiment, the method may comprise receiving, from the third network node, a second discovery response to the second discovery request.

In an embodiment, the second discovery response may comprise a first list with a number of NFs of the requested target NF type that support said subset of values of the query parameter and second continue discovery information, each for indicating to transmit a third discovery request that comprises the query parameter having at least a part of said subset of values, so as to find a first list with a number of NFs of the requested target NF type that altogether support said subset of values of the query parameter.

In an embodiment, the second discovery response may further comprise a second list with a number of NFs of the requested target NF type whose registration information is known by the third network node and supporting at least a part of said subset of values of the query parameter, in addition to the second continue discovery information.

In an embodiment, the second continue discovery information comprises at least one of an indication for indicating to transmit the third discovery request that comprises the query parameter having at least the part of said subset of values, a list of at least the part of said subset of values of the query parameter, a Network Repository Function ‘NRF’ discovery Uniform Resource Identifier ‘URI’ to which the second network node can transmit the third discovery request, so as to find the second list of NFs of the requested target NF type supporting at least the part of said subset of values of the query parameter.

In an embodiment, the second discovery request is forwarded by the first network node from the second network node, and the method may comprise after determining that said subset of values of the query parameter are not satisfied by any NF of the requested target NF type that is registered in the first network node, transmitting, to the second network node, a first discovery response to the first discovery request. The first discovery response may comprise first continue discovery information for indicating the second network node to transmit the second discovery request that comprises the query parameter having said subset of values. The method may comprise receiving the second discovery request from the second network node.

In an embodiment, the first discovery response may further comprise a third list with a number of NFs of the requested target NF type whose registration information is known by the first network node and supporting the plurality of values, excluding said subset of values, of the query parameter.

In an embodiment, the first continue discovery information may comprise at least one of an indication for indicating the second network node to transmit the second discovery request that comprises the query parameter having said subset of values, a list of said subset of values of the query parameter, an NRF discovery URI to which the second network node can transmit the second discovery request, so as to find the first list of NFs of the requested target NF type supporting said subset of values of the query parameter.

In an embodiment, the method may further comprise generating a third list with a number of NFs of the requested target NF type that are registered in the first network node and support the plurality of values, excluding said subset of values, of the query parameter. The method may further comprise storing the third list of NFs. The method may further comprise being triggered to generate the second discovery request that comprises the query parameter having said subset of values.

In an embodiment, the method may further comprise transmitting, to at least one fourth network node respectively, at least one third discovery request according to the received second continue discovery information, each of the at least one third discovery request comprising the query parameter having the respective part of said subset of values.

In an embodiment, the method may further comprise receiving, from the at least one fourth network node, a first list with a number of NFs that altogether support said subset of values of the query parameter in at least one third discovery response to the at least one third discovery request as a search result.

In an embodiment, the method may further comprise combining the first list of NFs and the third list of NFs.

In an embodiment, the method may further comprise transmitting the combined list of NFs to the second network node in the first discovery response.

In an embodiment, the method may further comprise transmitting, to the second network node, a first discovery response that comprises a search ID identifying a search result for the first discovery request, and a timer indicating the second network node to retrieve the search result after the timer is expired.

In an embodiment, the method may further comprise receiving, from the second network node, a fourth discovery request that comprises the search ID for retrieving the combined list of NFs, after the timer is expired.

In an embodiment, the method may further comprise transmitting the combined list of NFs to the second network node in the fourth discovery response.

In an embodiment, the first, third and fourth network nodes respectively host NRF.

In an embodiment, the second network node implements NF service consumer of an NRF discovery service.

In an embodiment, the NF service consumer comprises at least one of: Multicast/Broadcast-Section Management Function ‘MB-SMF’ , or Time Sensitive Communication and Time Synchronization Function ‘TSCTSF’ .

In an embodiment, the NF of the requested target NF type comprises Access and Mobility Management Function ‘AMF’ .

In an embodiment, the query parameter comprises a Tracking Area ‘TA’ List.

According to a second aspect of the present disclosure, a method performed by a second network node for Network Function ‘NF’ discovery is provided. The method may comprise transmitting, to a first network node, a first discovery request that comprises a query parameter having a plurality of values to be satisfied by NF (s) and a subset of the plurality of values of the query parameter that are not satisfied by any NF of the requested target NF type that is registered in the first network node. The method may comprise receiving, from the first network node, a first discovery response to the first discovery request. The first discovery response comprises the subset of the plurality of values of the query parameter that are not satisfied by any NF of the requested target NF type that is registered in the first network node.

In an embodiment, the first discovery response comprises first continue discovery information for indicating the second network node to transmit a second discovery request that comprises the query parameter having a subset of values from the plurality of values of the query parameter not satisfied by any NF of the requested target NF type that is registered in the first network node.

In an embodiment, the method may further comprise transmitting the second discovery request to the first network node according to the first continue discovery information.

In an embodiment, the first discovery response further comprises a third list with a number of NFs of the requested target NF type whose registration information is known by the first network node and supporting the plurality of values, excluding said subset of values, of the query parameter.

In an embodiment, the first continue discovery information comprises at least one of:an indication for indicating the second network node to transmit the second discovery request that comprises the query parameter having said subset of values, a list of said subset of values of the query parameter, a Network Repository Function ‘NRF’ discovery Uniform Resource Identifier ‘URI’ to which the second network node can transmit the second discovery request, so as to find a first list with a number of NFs of the requested target NF type supporting said subset of values of the query parameter.

In an embodiment, the method may further comprise receiving, from the first network node, a second discovery response that comprises a first list with a number of NFs of the requested target NF type that support said subset of values of the query parameter or second continue discovery information. Each of the second continue discovery information may indicate the second network node to transmit a third discovery request that comprises the query parameter having a respective part of said subset of values, so as to find the first list of NFs supporting said subset of values of the query parameter.

In an embodiment, the second discovery response further comprises a second list with a number of NFs of the requested target NF type whose registration information is known by a second NRF and supporting at least a part of said subset of values of the query parameter, in addition to the second continue discovery information.

In an embodiment, the second continue discovery information comprises at least one of an indication for indicating to transmit the third discovery request that comprises the query parameter having at least the part of said subset of values, a list of at least the part of said subset of values of the query parameter, an NRF discovery URI to which the second network node can transmit the third discovery request, so as to find a second list with a number of NFs of the requested target NF type supporting at least the part of said subset of values of the query parameter.

In an embodiment, the method may further comprise transmitting, to a fourth network node, at least one of third discovery request according to the received second continue discovery information. Each of the at least one third discovery request comprising the query parameter having the respective part of said subset of values.

In an embodiment, the method may further comprise receiving, from the at least one fourth network node, the first list of NFs that altogether support said subset of values of the query parameter in at least one third discovery response to the at least one third discovery request.

In an embodiment, the NF service consumer comprises at least one of Multicast/Broadcast-Section Management Function ‘MB-SMF’ , or Time Sensitive Communication and Time Synchronization Function ‘TSCTSF’ .

In an embodiment, the query parameter comprises a Tracking Area ‘TA’ List.

According to a third aspect of the present disclosure, a first network node is provided. The first network node includes: at least one processor, and at least one memory, storing instructions which, when executed on the at least one processor, cause the first network node to perform any of the methods according to the first aspect of the present disclosure.

According to a fourth aspect of the present disclosure, a second network node is provided. The second network node includes: at least one processor, and at least one memory, storing instructions which, when executed on the at least one processor, cause the second network node to perform any of the methods according to the second aspect of the present disclosure.

According to a fifth aspect of the present disclosure, a computer readable storage medium is provided. The computer readable storage medium has computer program instructions stored thereon, the computer program instructions, when executed by at least one processor, causing the at least one processor to perform any of the methods according to any of the first to second aspects of the present disclosure.

The technical solutions according to the exemplary embodiments of the present disclosure as described above may achieve at least beneficial effects of enabling NF discovery by partially matching the query parameters in the multiple-NRF deployment (including, but not limited to the hierarchical NRF deployment) , i.e., enabling an NF service consumer to discover the target NF instance (s) or the target NF instance aggregations when these NFs are registered in different NRFs.

BRIEF DESCRIPTION OF THE DRAWINGS

Amore complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

FIG. 1 schematically shows an exemplary multiple-NRF deployment;

FIG. 2 schematically shows an exemplary service discovery with multiple NRFs in an exemplary multiple-NRF deployment;

FIG. 3 schematically shows an exemplary sequence flow of service discovery with intermediate redirecting NRF, which is corresponding to Figure 5.3.2.2.4-1 of 3GPP TS 29.510 V18.3.0;

FIG. 4 schematically shows an exemplary sequence flow of service discovery with intermediate forwarding NRF, which is corresponding to Figure 5.3.2.2.5-1 of 3GPP TS 29.510 V18.3.0;

FIG. 5A schematically shows a method performed by a first network node for NF discovery according to an exemplary embodiment of the present disclosure;

FIG. 5B schematically shows a method performed by a first network node for NF discovery according to another exemplary embodiment of the present disclosure;

FIG. 6 schematically shows a method performed by a second network node for NF discovery according to an exemplary embodiment of the present disclosure;

FIG. 7 schematically shows a method performed by a second network node for NF discovery according to another exemplary embodiment of the present disclosure;

FIG. 8 schematically shows an exemplary sequence flow in which the methods performed by the first and the second network nodes according to the exemplary embodiments of the present disclosure are involved;

FIG. 9 schematically shows another exemplary sequence flow in which the methods performed by the first and the second network nodes according to the exemplary embodiments of the present disclosure are involved;

FIG. 10 schematically shows an exemplary structural block diagram of a first network node according to an exemplary embodiment of the present disclosure;

FIG. 11 schematically shows another exemplary structural block diagram of a first network node according to an exemplary embodiment of the present disclosure;

FIG. 12 schematically shows an exemplary structural block diagram of a second network node according to some exemplary embodiments of the present disclosure;

FIG. 13 schematically shows another exemplary structural block diagram of a second network node according to some exemplary embodiments of the present disclosure;

FIG. 14 is a diagram illustrating an exemplary communication system into which an embodiment of the disclosure is applicable;

FIG. 15 is a flowchart illustrating a method performed by a service producer according to an embodiment of the disclosure;

FIG. 16 is a flowchart for explaining the method of FIG. 15;

FIG. 17 is a flowchart illustrating a method performed by a service consumer according to an embodiment of the disclosure;

FIG. 18 is a flowchart illustrating an exemplary process according to an embodiment of the disclosure;

FIG. 19 is a flowchart illustrating an exemplary process into which an embodiment of the disclosure is applicable;

FIG. 20 is a block diagram showing an apparatus suitable for use in practicing some embodiments of the disclosure;

FIG. 21 is a block diagram showing a service producer according to an embodiment of the disclosure;

FIG. 22 is a block diagram showing a service consumer according to an embodiment of the disclosure;

FIG. 23 is diagram illustrating an example of a communication system in accordance with some embodiments;

FIG. 24 is a diagram illustrating a UE in accordance with some embodiments;

FIG. 25 is a diagram illustrating a network node in accordance with some embodiments;

FIG. 26 is a diagram illustrating a host in accordance with some embodiments;

FIG. 27 is a diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized; and

FIG. 28 is a diagram illustrating a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.

DETAILED DESCRIPTION

Hereinafter, the principle and spirit of the present disclosure will be described with reference to illustrative embodiments. 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. Additional information may make reference to the following documents, which are incorporated herein in their entirety by reference:

3GPP TS 23.501 V18.2.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS) ; Stage 2 (Release 18) ” , 2023-06;

3GPP TS 23.502 V18.2.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS) ; Stage 2 (Release 18) ” , 2023-06;

3GPP TS 23.247 V18.2.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architectural enhancements for 5G multicast-broadcast services; Stage 2 (Release 18) ” , 2023-06; and

3GPP TS 29.510 V18.3.0, “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services; Stage 3 (Release 18) ” , 2023-06.

Those skilled in the art will appreciate that the term “exemplary” is used herein to mean “illustrative, ” or “serving as an example, ” and is not intended to imply that a particular embodiment is preferred over another or that a particular feature is essential. Likewise, the terms “first” and “second, ” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises, ” “comprising, ” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

In some embodiments described herein, the term “coupled, ” “connected, ” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.

The term "network node" refers to a device in a wireless communication network via which a terminal device or another network node accesses the network and receives services therefrom. The network node refers to any Network Function (NF) , a base station (BS) , an access point (AP) , or any other suitable device in the wireless communication network. The BS may be, for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , or gNB, a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, a low power node such as a femto, a pico, and so forth. Yet further examples of the network node may include multi-standard radio (MSR) radio equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs) , base transceiver stations (BTSs) , transmission points, transmission nodes. More generally, however, the network node may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a terminal device access to the wireless communication network or to provide some service to a terminal device that has accessed the wireless communication network.

In some embodiments, the non-limiting terms wireless device or UE are used interchangeably. The UE herein can be any type of wireless device capable of communicating with a network node or another wireless device over radio signals, such as wireless device. The UE may also be a radio communication device, target device, D2D wireless device, machine type wireless device or wireless device capable of machine to machine communication (M2M) , low-cost and/or low-complexity wireless device, a sensor equipped with wireless device, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE) , laptop mounted equipment (LME) , USB dongles, Customer Premises Equipment (CPE) , an Internet of Things (IoT) device, or a Narrowband IoT (NB-IOT) device, etc.

Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and/or New Radio (NR) , may be used in this disclosure, this should not be seen as limiting the scope of the present disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA) , Worldwide Interoperability for Microwave Access (WiMax) , Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM) , may also benefit from exploiting the ideas covered within this disclosure.

Note further, that functions described herein as being performed by a UE or a network node may be distributed over a plurality of UEs and/or network nodes. In other words, it is contemplated that the functions of the network node and UE described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

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.

Before describing exemplary embodiments of the technical solutions of the present disclosure, relevant 3GPP requirements will be introduced briefly.

·5G multicast-broadcast services

3GPP TS 23.502 V18.2.0, Section 5.2.7.3.2 describesNnrf_NFDiscovery_Request service operation:

- If the target NF is AMF and the consumer NF is MB-SMF for broadcast service, the request includes TAI (s) (see clause 7.3 of TS 23.247 [78] ) .

- If the target NF is AMF and the consumer NF is other than MB-SMF, the request may include:

- AMF region, AMF Set, GUAMI and Target TAI (s) .

3GPP TS 23.247 V18.2.0, Section 7.3.1 describes MBS Session Start for Broadcast:

2. The MB-SMF may use NRF to discover the AMF (s) supporting MBS based on the MBS service area and select the appropriate one (s) . Then the MB-SMF sends the Namf_MBSBroadcast_ContextCreate (TMGI, N2 SM information ( [LL SSM] , 5G QoS Profile) , MBS service area, [MBS FSA ID (s) ] ) messages to the selected AMF (s) in parallel if the service type is broadcast service. The MB-SMF may include a maximum response time in the request.

·Time Sensitive Communication and Time Synchronization

3GPP TS 23.502 V18.2.0 describes:

4.15.9.3.2 Time synchronization service activation:

If the Ntsctsf_TimeSynchronization_ConfigCreate request contains a spatial validity condition, then the TSCTSF performs the following operations:

- For each target UE, TSCTSF determines whether the TSCTSF has subscribed for the UE presence in Area of Interest composed by the TA (s) in the Time Synchronization Coverage Area. If not, the TSCTSF discovers the AMF (s) serving the TA (s) that comprise the Time Synchronization Coverage Area, using the NRF discovery service (Nnrf_NFDiscovery_Request) with the list of TA (s) . Then the TSCTSF subscribes to the AMF (s) to receive notifications about the UE presence in Area of Interest using Namf_EventExposure operation with the corresponding event filters as described in clause 5.2.2.3. The subscribed area of interest may be the same as the Time Synchronization Coverage Area or may be a subset of the Time Synchronization Coverage Area (e.g. a list of TAs) based on the latest known UE location.

4.15.9.4 Procedures for management of 5G access stratum time distribution

6a. (When the procedure is triggered by the AF request to influence the 5G access stratum time distribution) :

If the Ntsctsf_ASTI_Create request in step 2 contains a spatial validity condition, then the TSCTSF performs the following operations:

- For each target UE, TSCTSF checks with the stored Time Synchronization Subscription data if the spatial validity condition is allowed and determines whether the TSCTSF has subscribed for the UE presence in Area of Interest composed by the TAs list in the spatial validity condition. If not, the TSCTSF discovers the AMF (s) , serving in the TAs that comprises the spatial validity condition, using the NRF discovery service (Nnrf_NFDiscovery_Request) with the list of TAs. Then the TSCTSF subscribes to the AMF (s) to receive notifications about the UE presence in Area of Interest using Namf_EventExposure operation with the corresponding event filters as described in clause 5.2.2.3. The subscribed area of interest may be the same as the spatial validity condition or may be a subset of the spatial validity condition (e.g. a list of TAs) based on the latest known UE location.

3GPP TS 29.510 V18.3.0 describes:

5.3.2.2.4 Service Discovery with intermediate redirecting NRF (as shown in FIG. 3, which is corresponding to Figure 5.3.2.2.4-1 of 3GPP TS 29.510 V18.3.0)

When multiple NRFs are deployed in one PLMN, one NRF may query the “nf-instances” resource in a different NRF so as to fulfil the service discovery request from a NF service consumer. The query between these two NRFs is redirected by a third NRF.

1. NRF-1 receives a service discovery request but does not have the information to fulfil the request. Then NRF-1 sends the service discovery request to a pre-configured NRF-2.

2a. Upon receiving a service discovery request, based on the information contained in the service discovery request (e.g. the "supi" query parameter in the URI) and locally stored information NRF-2 shall identify the next hop NRF (see clause 5.2.2.2.3) , and redirect the service discovery request by returning HTTP 307 Temporary Redirect response. The locally stored information in NRF-2 may:

a) be preconfigured; or

b) registered by other NRFs (see clause 5.2.2.2.3) .

The 307 Temporary Redirect response shall contain a Location header field, the host part of the URI in the Location header field represents NRF-3.

2b. if NRF-2 does not have enough information to redirect the service discovery request, then it responds with 404 Not Found, and the rest of the steps are omitted.

3. Upon receiving 307 Temporary Redirect response, NRF-1 sends the service discovery request to NRF-3 by using the URI contained in the Location header field of the 307 Temporary Redirect response.

4a. Upon success, NRF-3 returns the search result.

4b. On failure or redirection:

- If the NF Service Consumer is not allowed to discover the NF services for the requested NF type provided in the query parameters, the NRF shall return "403 Forbidden" response.

- If the discovery request fails at the NRF due to errors in the input data in the URI query parameters, the NRF shall return "400 Bad Request" status code with the ProblemDetails IE providing details of the error.

- If the discovery request fails at the NRF due to NRF internal errors, the NRF shall return "500 Internal Server Error" status code with the ProblemDetails IE providing details of the error.

- In the case of redirection, the NRF shall return 3xx status code, which shall contain a Location header with an URI pointing to the endpoint of another NRF service instance.

5.3.2.2.5 Service Discovery with intermediate forwarding NRF (as shown in FIG. 4, which is corresponding to Figure 5.3.2.2.5-1 of 3GPP TS 29.510 V18.3.0)

When multiple NRFs are deployed in one PLMN, one NRF may query the “nf-instances” resource in a different NRF so as to fulfil the service discovery request from a NF service consumer. The query between these two NRFs is forwarded by a third NRF.

1. NRF-1 receives a service discovery request and sends the service discovery request to a pre-configured NRF-2. This may for example include cases where NRF-1 does not have sufficient information as determined by the operator policy to fulfill the request locally.

2a. Upon receiving a service discovery request, based on the information contained in the service discovery request (e.g. the "supi" query parameter in the URI) and locally stored information, NRF-2 shall identify the next hop NRF (see clause 5.2.2.2.3) , and forward the service discovery request to that NRF (i.e. NRF-3 in this example) similarly to steps 1 and 2 in Figure 5.3.2.2.2-1 where the originator of the service invocation is NRF-2 and the recipient of the service invocation is NRF-3. The locally stored information in NRF-2 may:

a) be preconfigured; or

b) registered by other NRFs (see clause 5.2.2.2.3) .

2b. if NRF-2 does not have enough information to forward the service discovery request, then it responds with 404 Not Found, and the rest of the steps are omitted.

3a. Upon success, NRF-3 returns the search result.

3b. On failure or redirection:

-If the NF Service Consumer is not allowed to discover the NF services for the requested NF type provided in the query parameters, the NRF shall return "403 Forbidden" response.

- If the discovery request fails at the NRF due to NRF internal errors, the NRF shall return “500 Internal Server Error” status code with the ProblemDetails IE providing details of the error.

4a. NRF-2 forwards the success response to NRF-1.

4b. On failure or redirection:

- NRF-2 forwards the error response to NRF-1.

NOTE: It is not assumed that there can only be two NRF hierarchies, i.e. the NRF-3 can go on to forward the service discovery request to another NRF.

When multiple NRFs are deployed in the network, a (local) NRF, e.g. NRF1 needs register itself to the higher layer NRF, NRF2 in the above figure, as specified in clause 5.2.2.2.3 “NRF registration to another NRF” of TS 29.510, where the registering NRF may include nrfInfo.

5.2.2.2.3 NRF registration to another NRF

The procedure specified in clause 5.2.2.2.2 applies. Additionally:

a) the registering NRF shall set the nfType to “NRF” in the nfProfile;

b) the registering NRF shall set the nfService to contain “nnrf-disc” , “nnrf-nfm” and optionally “nnrf-oauth2” in the nfProfile;

c) the registering NRF may include nrfInfo which contains the information of e.g. udrInfo, udmInfo, ausfInfo, amfInfo, smfInfo, upfInfo, pcfInfo, bsfInfo, nefInfo, chfInfo, pcscfInfo, lmfInfo, gmlcInfo, aanfInfo, nfInfo and nsacfInfo in the nfProfile locally configured in the NRF or the NRF received during registration of other NFs, this means the registering NRF is able to provide service for discovery of NFs subject to that information;

d) if the NRF receives an NF registration with the nfType set to “NRF” , the NRF shall use the information contained in the nfProfile to target the registering NRF when forwarding or redirecting NF service discovery request.

6.1.6.2.31 Type: NrfInfo

Table 1 (corresponding to Table 6.1.6.2.31-1 of 3GPP TS 29.510 V18.3.0) : Definition of type NrfInfo

The basic idea of the present disclosure consists in an enhancement to the NF service discovery procedure, in which a first NRF receiving, from an NF service consumer, a discovery request including a query parameter having a plurality of values (asubset of which cannot be supported by any NF of the requested target NF type registered in the first NRF) may separately process those values of the query parameter in the discovery request, returning a list of NFs of the requested target NF type registered in the first NRF that can support some of those values, and transmitting (either forwarding from the NF service consumer, or generating and transmitting by the first NRF itself) , to a second NRF, a new discovery request including the query parameter having said subset of values that cannot be supported by any NF of the requested target NF type registered in the first NRF, in order to find other list (s) of NFs of the requested target NF type registered in other NRF (s) that can support said subset of values that cannot be supported by any NF registered in the first NRF. As such, a set of NFs of the requested target NF type, that may be registered at different NRFs and these NFs, as NF aggregation, altogether can satisfy ALL values of the query parameter included in the NF discovery request, may be retrieved as one of candidate NF aggregation.

Hereinafter, a method 500 performed by a first network node for NF discovery according to an exemplary embodiment of the present disclosure will be described with reference to FIG. 5A.

In an exemplary embodiment, the first network node may host or implement NRF. An example of the first network node may be NRF 1 as shown in the exemplary sequence flows of FIGS. 8 and 9. It should be understood that the first network node may also be any other appropriate entity that can be configured to perform the method 500 as described below, including a virtualized entity that may be implemented on cloud.

As shown in FIG. 5A, the method 500 may include at least steps S501, S503, S505, and S507.

In step S501, the first network node may receive a first discovery request from a second network node.

In an embodiment, a first discovery request may comprise a query parameter having a plurality of values to be satisfied (or supported) by NF (s) and an indication indicating a capability of receiving an aggregation of NFs of a requested target NF type and a subset of the plurality of values of the query parameter that are not satisfied (or supported) by any NF of the requested target NF type that is registered in the first network node.

In an embodiment, the first discovery request may include at least a query parameter having a plurality of values to be supported by NF (s) , and an indication indicating a capability of receiving an aggregation of NFs of a requested target NF type and continue discovery information.

Here, the second network node may host or implement NF service consumer of an NRF discovery service. It should be understood that the second network node may also be any other appropriate entity that can be configured to interact with the first network node in the method 500, including a virtualized entity that may be implemented on cloud.

As an example, the second network node may host or implement MB-SMF, which may need to establish a broadcast MBS session in a number of Tracking Areas, and thus may require to consume a service (e.g. Namf_MBSBroadcast service) offered from at least one target NF (e.g. AMF controlling a subset of the desired TAs) registered in an NRF. An example of the second network node may be MB-SMF1x as shown in the exemplary sequence flows of FIGS. 8 and 9. As another example, the second network node may host or implement Time Sensitive Communication and Time Synchronization Function (TSCTSF) , which may need to discover the AMF(s) , serving in the TAs that includes the spatial validity condition, using the NRF discovery service (Nnrf_NFDiscovery_Request) with the list of TAs. The query parameter may be a TA List.

For illustration only without any limitation, in conjunction with the exemplary sequence flows as shown in FIGS. 8 and 9, an example of the first discovery request may be GET . . . /nf-instances? service-name=Namf-xx&tai-list=TA1, TA2, TA3, TA9, TA10, TA12, TA13&nf-aggre=true, wherein “tai-list=TA1, TA2, TA3, TA9, TA10, TA12, TA13” may be an example of the query parameter having a plurality of values, and “nf-aggre=true” may be an example of the indication indicating the NF service consumer’s capability of receiving an aggregation of NFs of the requested target NF type, e.g., nfInstanceAggregations, and continue discovery information, e.g., ContinueDiscInfo.

Then, the first network node may determine, in step S503, that a subset of values from the plurality of values of the query parameter are not satisfied (or supported) by any NF of the requested target NF type that is registered in the first network node. For example, the first network node, e.g., NRF 1, may use served “TargetNF” Info, such as servedAmfInfo, to learn what TAs an AMF is serving. Here, “TargetNF” is an example of the NF of the requested target NF type.

In the examples of FIGS. 8 and 9, AMF 1x registered in NRF 1 controls TA1-TA5, and thus NRF 1 may determine that TA9, TA10, TA12, TA13 in the received first discovery request are not supported.

In step S505, optionally, the first network node may transmit a second discovery request to a third network node. The second discovery request may include the query parameter having said subset of values that are not supported by any NF of the requested target NF type that is registered in the first network node. The second discovery request may also include the indication, e.g., nf-aggre=true, indicating the first network node’s capability of receiving an aggregation of NFs of a requested target NF type, e.g., nfInstanceAggregations, and continue discovery information, e.g., ContinueDiscInfo.

Here, the third network node may host or implement NRF. An example of the third network node may be NRF A as shown in the exemplary sequence flows of FIGS. 8 and 9. It should be understood that the third network node may also be any other appropriate entity that can be interact with the first network node in the method 500, including a virtualized entity that may be implemented on cloud.

In the example of FIGS. 8 and 9, NRF 1 may transmit e.g., GET ... /nf-instances? service-name=Namf-xx&tai-list= TA9, TA10, TA12, TA13&nf-aggre=true, wherein “tai-list=TA9, TA10, TA12, TA13” may be an example of the query parameter having said subset of values that are not supported by any NF of the requested target NF type that is registered in the first network node, and “nf-aggre=true” may be an example of the indication indicating the NRF 1’s capability of receiving an aggregation of NFs of the requested target NF type and continue discovery information.

Then in step S507, optionally, the first network node may receive, from the third network node, a second discovery response to the second discovery request.

The second discovery response may include a list (also called “first list” ) with a number of NFs of the requested target NF type that altogether support said subset of values of the query parameter that are not supported by any NF of the requested target NF type that is registered in the first network node.

For example, the third network node may obtain the first list of NFs of the requested target NF type, e.g., those NFs may be registered in the third network node, or the third network node may utilize “hided” (i.e., not (needed to be) known by the first network node) signaling interactions with other NRF (s) to return the whole first list of NFs of the requested target NF type (which may be a combined search result, as will be described later in following part of method 500, method 700 and the exemplary signaling sequence shown in FIG. 9) as NF aggregation that altogether support said subset of values of the query parameter. In this case, the third network node may transmit the second discovery response that includes the first list of NFs, e.g., “nfInstanceAggregations” , which may be AMF 2x and AMF 3x in this example.

Alternatively, the second discovery response may include (e.g. at least one) second continue discovery information, each for indicating to transmit a further (also called “third” ) discovery request that include the query parameter having at least a part of said subset of values, so as to find the first list of NFs of the requested target NF type that altogether support said subset of values of the query parameter.

The second continue discovery information may include at least one of:

-an indication for indicating to transmit the third discovery request that includes the query parameter having at least the part of said subset of values,

- a list of at least the part of said subset of values of the query parameter, e.g., TA9 and TA10 (or TA12 and TA13, which may be included in another second continue discovery information) ,

- an NRF discovery URI to which the second network node can transmit the third discovery request, e.g., NRF2 URI (or NRF3 URI, which may be included in another second continue discovery information) , so as to find a list (also called “second list” ) of NFs of the requested target NF type, e.g., AMF 2x (or AMF 3x, which is found based on another second continue discovery information) , supporting at least the part of said subset of values of the query parameter.

In this case, the third network node may also include, in the second discovery response, a list (also called “second list” ) of NFs of the requested target NF type whose registration information is known by the third network node and supporting at least a part of said subset of values of the query parameter, e.g., partialNfInstanceAggregations, in addition to the at least one second continue discovery information.

For example, if the third network node knows not only that the third discovery request can be transmitted to NRF 3 for TA12 and TA13, but also that AMF 3x is registered in NRF 3, the third network node may directly include AMF 3x as partialNfInstanceAggregations in the second discovery response.

Multiple continue discovery information may be corresponding to different groups of values of the query parameter and the NRF's discovery URIs that a discovery request can be sent towards, so as to find the NF (s) of the requested target NF type for these values. That is, the continue discovery information is per NRF.

In an exemplary embodiment, the second discovery request may be forwarded by the first network node from the second network node, as also shown in the example of FIG. 8.

It should be understood that only the first network node that has the capability of receiving an aggregation of NFs of the requested target NF type, e.g., nfInstanceAggregations, and continue discovery information, e.g., ContinueDiscInfo, that can forward this second discovery request to the third network node. That is, both the first network node and the second network node need to have such a capability, and indicate its capability in the indication, e.g., nf-aggre=true, to its receiving party.

In this case, the method 500 may further include: after determining, in step S503, that said subset of values of the query parameter are not supported by any NF of the requested target NF type that is registered in the first network node, the first network node may transmit, to the second network node, a first discovery response to the first discovery request.

The first discovery response may include first continue discovery information for indicating the second network node to transmit the second discovery request that includes the query parameter having said subset of values.

Similar with the second continue discovery information, the first continue discovery information may include at least one of:

- an indication for indicating the second network node to transmit the second discovery request that includes the query parameter having said subset of values,

- a list of said subset of values of the query parameter, e.g., TA9, TA10, TA12, TA 13,

- an NRF discovery URI to which the second network node can transmit the second discovery request, so as to find the first list of NFs of the requested target NF type supporting said subset of values of the query parameter.

The first discovery response may further include a third list with a number of NFs of the requested target NF type whose registration information is known by the first network node and supporting the plurality of values, excluding said subset of values, of the query parameter, e.g., partialNfInstanceAggregations, i.e., AMF1x in this example.

This first discovery response may trigger the second network node to transmit a further (also called “second” ) discovery request. Accordingly, the first network node may receive the second discovery request from the second network node, which is then forwarded by the first network node to the third network node in step S505. As previously described, the first network node may receive the second discovery response in step S507, and the second discovery response may include either the first list of NFs of the requested target NF type that altogether support said subset of values of the query parameter, or at least one second continue discovery information.

Then, the first network node may forward, to the second network node, the second discovery response that includes the first list of NFs of the requested target NF type that altogether support said subset of values of the query parameter or the at least one second continue discovery information.

In a case of the second discovery response including the second list of NFs of the requested target NF type whose registration information is known by the third network node and supporting at least the part of said subset of values of the query parameter, the first network node may forward, to the second network node, the second discovery response that includes the at least one second continue discovery information and the second list of NFs of the requested target NF type whose registration information is known by the third network node and supporting at least the part of said subset of values of the query parameter.

In another exemplary embodiment, the second discovery request may be triggered to be generated and transmitted by the first network node itself, as also shown in the example of FIG. 9.

In this case, in response to the first discovery request received from the second network node, the first network node may generate a third list with a number of NFs of the requested target NF type, e.g., AMF1x in the example of FIG. 9, that are registered in the first network node and support the plurality of values, excluding said subset of values, of the query parameter; store the third list of NFs; and being triggered to generate the second discovery request that includes the query parameter having said subset of values that are not supported by any NF of the requested target NF type that is registered in the first network node, which is transmitted to the third network node in step S505 as previously described.

After the receiving, in step S507, from the third network node, the second discovery response to the second discovery request, the first network node may transmit, to at least one fourth network node respectively, at least one third discovery request according to the received at least one second continue discovery information, each of the at least one third discovery request including the query parameter having the respective part of said subset of values; and receive, from the at least one fourth network node, a first list with a number of NFs, e.g., AMF2x and AMF3x in the example of FIG. 9, that altogether support said subset of values of the query parameter in at least one third discovery response to the at least one third discovery request as a search result.

Then, the first network node may combine the first list of NFs and the third list of NFs, and transmit the combined list of NFs to the second network node in the first discovery response.

Alternatively, the first network node may transmit to the second network node, a first discovery response to the first discovery request received in step S501. The first discovery response may include a search ID identifying a search result for the first discovery request, and a timer indicating the second network node to retrieve the search result after the timer is expired.

During the waiting time of the second network node, the first network node may transmit, to at least one fourth network node respectively, at least one third discovery request according to the received at least one second continue discovery information, each of the at least one third discovery request including the query parameter having the respective part of said subset of values; and receive, from the at least one fourth network node, a first list with a number of NFs, e.g., AMF2x and AMF3x in the example of FIG. 9, that altogether support said subset of values of the query parameter in at least one third discovery response to the at least one third discovery request as the search result.

The first network node may combine the first list of NFs and the third list of NFs.

After the timer is expired, the first network node may receive, from the second network node, a fourth discovery request that includes the search ID for retrieving the combined list of NFs; and transmit the combined list of NFs to the second network node in the fourth discovery response.

The first discovery response, the second discovery response, the third discovery response or the fourth discovery response may be either an acceptance response message, e.g., 2xx Accepted, or a rejection response message, e.g., 4xx Rejected.

Hereinafter, a method 520 performed by a first network node for NF discovery according to another exemplary embodiment of the present disclosure will be described with reference to FIG. 5B.

As shown in FIG. 5B, the method 520 may include at least step S521.

In step S521, the first network node may transmit, to the second network node, a first discovery response to the first discovery request. The first discovery response may comprise said subset of values.

Hereinafter, a method 600 performed by a second network node according to an exemplary embodiment of the present disclosure will be described with reference to FIG. 6. FIG. 8 is an exemplary sequence flow in which the methods 500 and 600 respectively performed by the first and the second network nodes according to the exemplary embodiments of the present disclosure are involved, and may also be made reference to. It should be understood that the method 600 performed by the second network node corresponds to the method 500 performed by the first network node as previously described. Thus, some description of the method 600 may refer to those of method 500, and thus will be omitted for simplicity.

As previously described, the second network node may host or implement NF service consumer of an NRF discovery service. It should be understood that the second network node may also be any other appropriate entity that can be configured to perform the method 600 as described below, including a virtualized entity that may be implemented on cloud.

As an example, the second network node may host or implement MB-SMF, which may need to establish a broadcast MBS session in a number of Tracking Areas, and thus may require to consume a service (e.g. Namf_MBSBroadcast service) offered from at least one target NF (e.g. AMF controlling a subset of the desired TAs) registered in an NRF. An example of the second network node may be MB-SMF1x as shown in the exemplary sequence flows of FIG. 8. As another example, the second network node may host or implement Time Sensitive Communication and Time Synchronization Function (TSCTSF) , which may need to discover the AMF (s) , serving in the TAs that includes the spatial validity condition, using the NRF discovery service (Nnrf_NFDiscovery_Request) with the list of TAs. The query parameter may be a TA List.

As shown in FIG. 6, the method 600 may include at least steps S601, S603 and S605.

In step S601, the second network node may transmit a first discovery request to a first network node.

In an embodiment, the first discovery request may comprise a query parameter having a plurality of values to be satisfied by NF (s) and a subset of the plurality of values of the query parameter that are not satisfied by any NF of the requested target NF type that is registered in the first network node.

In an embodiment, the first discovery request may include at least a query parameter having a plurality of values to be satisfied (or supported) by NF (s) , and an indication indicating a capability of receiving an aggregation of NFs of a requested target NF type and continue discovery information.

As previously described, the first network node may host or implement NRF. An example of the first network node may be NRF 1 as shown in the exemplary sequence flows of FIG. 8. It should be understood that the first network node may also be any other appropriate entity that can be configured to interact with the second network node in the method 600, including a virtualized entity that may be implemented on cloud.

In step S603, the second network node may receive a first discovery response to the first discovery request from the first network node.

In an embodiment, the first discovery response may comprise the subset of the plurality of values of the query parameter that are not satisfied by any NF of the requested target NF type that is registered in the first network node

In an embodiment, the first discovery response may include first continue discovery information for indicating the second network node to transmit a second discovery request that includes the query parameter having a subset of values from the plurality of values of the query parameter not supported by any NF of the requested target NF type that is registered in the first network node.

The first continue discovery information may include at least one of:

Multiple continue discovery Information are corresponding to different groups of values of the query parameter and the NRF's discovery URIs which a discovery request can be transmitted towards, so as to find the target NF (s) for these values.

If there is no NRF discovery URI included, the second network node may transmit, to the first network node by default, a further discovery request with those values not being supported.

For example, if there are multiple continue discovery information included, for each such instance, the NF service consumer may generate and transmit a discovery request with values of the query parameter that are not satisfied towards the NRF as indicated in the NRF's discovery URI if available in the continue discovery information, or towards the original NRF, e.g., NRF1, if no NRF discovery URI is included.

As an alternative to provide the NF service consumer with “partialNfInstanceAggregations” , NRF1 may include continue discovery information, e.g., ContinueDiscInfo, containing the same query parameter but excluding those values not being satisfied to the said NRF, i.e., in this example, a list of TAs served by the AMFs registered in NRF1 (that is TA1, TA2 and TA3 without including TA9, TA10, TA12 and TA13) , to request the NF service consumer to transmit a new discovery request to get what “partialNfInstanceAggregations” includes, e.g., AMF1x.

This first discovery response may trigger the second network node to transmit a further (also called “second” ) discovery request to the first network node according to the first continue discovery information in step S605 (optionally) .

As previously described, the first network node may forward the second discovery request to the third network node, receive the second discovery response that may include either a first list with a number of NFs of the requested target NF type that altogether support said subset of values of the query parameter or at least one second continue discovery information, and forward the second discovery response to the second network node.

Accordingly, the second network node may receive the second discovery response from the first network node.

As previously described, each of the at least one second continue discovery information may indicate the second network node to transmit a third discovery request that includes the query parameter having a respective part of said subset of values, so as to find the first list of NFs supporting said subset of values of the query parameter.

The second continue discovery information may include at least one of:

- an indication for indicating to transmit the third discovery request that includes the query parameter having at least the part of said subset of values,

In this case, the second discovery response may also include a list (also called “second list” ) of NFs of the requested target NF type whose registration information is known by the third network node and supporting at least a part of said subset of values of the query parameter, e.g., partialNfInstanceAggregations, in addition to the at least one second continue discovery information.

Then, the second network node may transmit, to a fourth network node, at least one of third discovery request according to the received at least one second continue discovery information, each of the at least one third discovery request including the query parameter having the respective part of said subset of values; and receive, from the at least one fourth network node, the first list of NFs that altogether support said subset of values of the query parameter in at least one third discovery response to the at least one third discovery request.

As such, the second network node may retrieve a list with a number of NFs of the requested target NF type supporting the plurality of values of the query parameter as it requested.

The first discovery response, the second discovery response, or the third discovery response may be either an acceptance response message, e.g., 2xx Accepted, or a rejection response message, e.g., 4xx Rejected.

Hereinafter, a method 700 performed by a second network node according to another exemplary embodiment of the present disclosure will be described with reference to FIG. 7. FIG. 9 is an exemplary sequence flow in which the methods 500 and 700 respectively performed by the first and the second network nodes according to the exemplary embodiments of the present disclosure are involved, and may also be made reference to. It should be understood that the method 700 performed by the second network node corresponds to the method 500 performed by the first network node and some of steps are similar with the method 600 performed by the second network node as previously described. Thus, some description of the method 700 may refer to those of methods 500 and 600, and thus will be omitted for simplicity.

The difference between the methods 600 and 700 consists in that in method 700, the first network node, e.g., NRF 1, hides all the signaling interactions between NRFs and returns a combined search results to the second network node, while in method 600, the second network node needs to transmit further discovery request to other network node than the first network node for the query parameter having said subset of values that are not supported by any NF of the requested target NF type that is registered in the first network node.

As previously described, the second network node may host or implement NF service consumer of an NRF discovery service. It should be understood that the second network node may also be any other appropriate entity that can be configured to perform the method 700 as described below, including a virtualized entity that may be implemented on cloud.

As an example, the second network node may host or implement MB-SMF, which may need to establish a broadcast MBS session in a number of Tracking Areas, and thus may require to consume a service (e.g. Namf_MBSBroadcast service) offered from at least one target NF (e.g. AMF controlling a subset of the desired TAs) registered in an NRF. An example of the second network node may be MB-SMF1x as shown in the exemplary sequence flows of FIG. 9. As another example, the second network node may host or implement Time Sensitive Communication and Time Synchronization Function (TSCTSF) , which may need to discover the AMF(s) , serving in the TAs that includes the spatial validity condition, using the NRF discovery service (Nnrf_NFDiscovery_Request) with the list of TAs. The query parameter may be a TA List.

As shown in FIG. 7, the method 700 may include at least steps S701 and S703.

In step S701, the second network node may transmit a first discovery request to a first network node. The first discovery request may include at least a query parameter having a plurality of values to be supported by NF (s) , and an indication indicating a capability of receiving an aggregation of NFs of a requested target NF type and continue discovery information.

In step S703, the second network node may receive, from the first network node, a list with a number of NFs of the requested target NF type supporting the plurality of values of the query parameter in a discovery response, which may be either an acceptance response message, e.g., 2xx Accepted, or a rejection response message, e.g., 4xx Rejected.

Alternatively or additionally, the second network node may receive, from the first network node, a search ID identifying a search result for the first discovery request, and a timer indicating the second network node to retrieve the respective search result after the timer is expired; and transmit, to the first network node, a fourth discovery request that includes the search ID for retrieving said list of NFs, after the timer is expired, so as to receive the list with a number of NFs of the requested target NF type supporting the plurality of values of the query parameter in step S703.

Hereinafter, an exemplary sequence flow in which the method 500 performed by the first network node, and the methods 600 and 700 performed by the second network node according to the exemplary embodiments of the present disclosure are involved will be described respectively in conjunction with FIGS. 8 and 9. In the example of FIGS. 8 and 9, NRF 1 is illustrated as an example of the first network node, MB-SMF1x is illustrated as an example of the second network node, NRF A is illustrated as an example of the third network node, NRF 2 and NRF 3 are illustrated as examples of the fourth network node, and AMF 1x, AMF 2x and AMF 3x are illustrated as examples of the NF of the requested target NF type. In these examples, AMF 1x is registered in NRF 1 and supports/controls TA1-TA5, AMF 2x is registered in NRF 2 and supports/controls TA6-TA10, AMF 3x is registered in NRF 3 and supports/controls TA11-TA15.

It should be understood that although NRF A in FIGS. 8 and 9 are illustrated as an NRF at a higher level (Level 1 as shown in FIGS. 8 and 9) , and NRF 1, NRF 2 and NRF 3 are illustrated as NRFs at a lower level (Level 2 as shown in FIGS. 8 and 9) as examples, the present disclosure is not only limited to such a hierarchical NRF deployment, but can also be applied to any multiple-NRF architecture besides the hierarchical NRF deployment.

FIG. 8 schematically shows an exemplary sequence flow in which the method 500 performed by the first network node and the method 600 performed by the second network node according to the exemplary embodiments of the present disclosure are involved. In particular, MB-SMF 1x performs NF service discovery procedure towards its configured NRF 1 to find a list of AMFs serving TAs 1, 2, 3, 9, 10, 12, 13 where these AMFs are registered in different (regional) NRFs.

When sending a discovery request to the NRF1 to find NF (s) of the requested target NF type for a list of TAs, MB-SMF 1x uses the query parameter “tai-list” together with a new indication (Boolean) to indicate its capability of receiving an aggregation of NFs of the requested target NF type and continue discovery information.

As shown in FIG. 8, in S8_1, MB-SMF 1x sends, to NRF1, a first discovery request: e.g.,

GET . . . /nf-instances? service-name=Namf-xx&tai-list=TA1, TA2, TA3, TA9, TA10, TA12, TA13&nf-aggre=true, wherein “tai-list= TA1, TA2, TA3, TA9, TA10, TA12, TA13” is an example of the query parameter having a plurality of values in the first discovery request as previously described, and “nf-aggre=true” is an example of the indication indicating MB-SMF 1x’s capability of receiving an aggregation of NFs of the requested target NF type and continue discovery information.

In S8_2, NRF 1 returns 2xx Accepted or 4xx Rejected as a response message, the response message including continue discovery information, and optionally including one or more target NF (s) or target NF aggregations, in this case, the AMF1x (partialNfInstanceAggregations) .

In S8_3, MB-SMF 1x sends a second discovery request for TA9, TA10, TA12, TA13:

e.g., GET . . . /nf-instances? service-name=Namf-xx&tai-list= TA9, TA10, TA12, TA13&nf-aggre=true, since AMF1x is returned for TA1-TA3, wherein “tai-list= TA9, TA10, TA12, TA13” is an example of the query parameter having said subset of values included in the second discovery request as previously described, and “nf-aggre=true” is an example of the indication indicating NRF 1’s capability of receiving an aggregation of NFs of the requested target NF type and continue discovery information.

In S8_4, NRF 1 forwards, to NRF A, the second discovery request:

GET . . . /nf-instances? service-name=Namf-xx&tai-list= TA9, TA10, TA12, TA13&nf-aggre=true.

In S8_5, NRF A transmits a second discovery response to NRF 1, which may be either an acceptance response message, e.g., 2xx Accepted, or a rejection response message, e.g., 4xx Rejected. The second discovery response may include two continue discovery information, one containing NRF2 URI, and TA9 and TA10, the other containing NRF3 URI, and TA12 and TA13, since the NRF A has learned from the nrfInfo of NRF2 and NRF3 what TAs the target AMFs registered in NRF2 or NRF3 can serve.

In S8_6, NRF 1 forwards the second discovery response, e.g., 2xx Accepted or 4xx Rejected to the MB-SMF1x.

In S8_7, MB-SMF 1x sends, to NRF2, a third discovery request:

GET . . . /nf-instances? service-name=Namf-xx&tai-list= TA9, TA10&nf-aggre=true.

In S8_8, NRF 2 returns AMF 2x in a third discovery response to the third discovery request.

In S8_9, MB-SMF 1x sends, to NRF 3, another third discovery request:

GET . . . /nf-instances? service-name=Namf-xx&tai-list= TA12, TA13&nf-aggre=true.

In S8_10, NRF 3 returns AMF 3x in a third discovery response to the other third discovery request.

In S8_11, MB-SMF 1x retrieves a list with a number of NFs of the requested target NF type supporting the plurality of values of the query parameter as it requested, i.e., nfInstanceAggregation containing AMF1x, AMF2x and AMF3x.

It should be noted that in a case where the discovery response is a rejection response message, e.g., 4xx Rejected, the continue discovery information and optionally, partialNfInstanceAggregation are included in a new data type associated with the 4xx status code, preferably called "ProblemDetailsContinueDiscovery" , which is defined as a list of to be combined data to ensure backwards compatibility. The partialNfInstanceAggregations includes a list of NFs which are satisfying at least a part of said subset of values of the query parameter, e.g., AMF 2x or AMF 3x in this example.

Thus, the case where the discovery response is a rejection response message will lead more complicated protocol changes in 3GPP TS 29.510 V18.3.0, which will be further described below. The changes are involved in e.g., Tables 6.2.3.2.3.1-3 and Section 6.2.6.2. x of 3GPP TS 29.510 V18.3.0, which are highlighted in underlined Bold Italics.

Table 6.2.3.2.3.1-3: Data structures supported by the GET Response Body on this resource

6.2.6.2. x Type: ProblemDetailsContinueDiscovery

Table 6.3.6.2.5-1: Definition of type ProblemDetailsContinueDiscovery as a list of to be combined data

FIG. 9 schematically shows another exemplary sequence flow in which the method 500 performed by the first network node and the method 700 performed by the second network node according to the exemplary embodiments of the present disclosure are involved. In particular, MB-SMF 1x performs NF service discovery procedure towards its configured NRF 1 to find a list of AMFs serving TAs 1, 2, 3, 9, 10, 12, 13 where these AMFs are registered in different (regional) NRFs. In this example, NRF1 hides all the signaling interactions between NRFs and returns a combined search results to MB-SMF 1x.

As shown in FIG. 9, in S9_1, MB-SMF 1x sends, to NRF1, a first discovery request for TA1, TA2, TA3, TA9, TA10, TA12, TA13: e.g.,

GET . . . /nf-instances? service-name=Namf-xx&tai-list= TA1, TA2, TA3, TA9, TA10, TA12, TA13&nf-aggre=true

In S9_3, NRF1 temporarily stores the search result, i.e. AMF1x for TAs 1, 2 and 3, sends a second discovery request to NRF A for the TA value beyond its range, e.g., GET . . . /nf-instances? service-name=Namf-xx&tai-list= TA9, TA10, TA12, TA13&nf-aggre=true.

In S9_4, NRF A transmits a second discovery response to NRF 1, which may be either an acceptance response message, e.g., 2xx Accepted, or a rejection response message, e.g., 4xx Rejected. The second discovery response may include two continue discovery information, one containing NRF2 URI, and TA9 and TA10, the other containing NRF3 URI, and TA12 and TA13, since the NRF A has learned from the nrfInfo of NRF2 and NRF3 what TAs the target AMFs registered in NRF2 or NRF3 can serve.

In S9_5, NRF 1 sends to NRF2, a third discovery request: e.g.,

In S9_6, NRF 2 returns AMF 2x in a third discovery response to the third discovery request.

In S9_7, NRF1 sends, to NRF 3, another third discovery request: e.g.,

In S9_8, NRF 3 returns AMF 3x in a third discovery response to the other third discovery request.

In S9_10, NRF 1 returns, to MB-SMF 1x, a response message including a combined list of NFs of the requested target NF type supporting the plurality of values of the query parameter as it requested, i.e., nfInstanceAggregation containing AMF1x, AMF2x and AMF3x that are registered in different NRFs.

As an alternative embodiment, instead waiting for the outcome received in S9_4, S9_6, and S9_8 from other NRFs, NRF 1 may return, in S9_2’ , a first discovery response to the first discovery request received in S9_1’ (which is the same as S9_1) . The first discovery response may include SearchResult containing e.g., partialNfInstanceAggregations, a Search ID, e.g., SearchId, and a Timer indicating that the NF service consumer shall use the Search ID to retrieve the search result after the Timer is expired.

Then, S9_3’ ～S9_8’ that are identical with S9_3～S9_8 are performed in this alternative embodiment.

After the timer is expired, MB-SMF1x sends to NRF1, in S9_9’ , a fourth discovery request that includes the search ID for retrieving the combined list of NFs: e.g.,

GET . . /nf-instances? searchId=xyz.

In S9_10’ , NRF1 returns, to MB-SMF 1x, a fourth response message including a combined list of NFs of the requested target NF type supporting the plurality of values of the query parameter as it requested, i.e., nfInstanceAggregation containing AMF1x, AMF2x and AMF3x that are registered in different NRFs.

Hereinafter, a structure of a first network node according to an exemplary embodiment of the present disclosure will be described with reference to FIG. 10. FIG. 10 schematically shows a block diagram of the first network node 1000 according to an exemplary embodiment of the present disclosure. The first network node 1000 in FIG. 10 may perform the methods 500 and/or 520 with reference to FIGs. 5A and 5B and signaling sequence diagrams with reference to FIGS. 8, and 9. Accordingly, some detailed description on the first network node 1000 may refer to the corresponding description of the methods 500 and 520 as shown in FIGs. 5A and 5B in conjunction with the signaling sequence diagrams as shown in FIGS. 8 and 9, and thus will be omitted here for simplicity.

As shown in FIG. 10, the first network node 1000 may include at least a receiving unit 1001, a determination unit 1003, and a transmitting unit 1005 (optionally) .

The receiving unit 701 may be configured to receive, from a second network node, a first discovery request that includes a query parameter having a plurality of values to be satisfied by NF (s) and an indication indicating a capability of receiving a list with an aggregation NFs of a requested target NF type and a subset of the plurality of values of the query parameter that are not satisfied by any NF of the requested target NF type that is registered in the first network node.

The determination unit 1003 may be configured to determine that a subset of values from the plurality of values of the query parameter are not satisfied by any NF of the requested target NF type that is registered in the first network node.

The transmitting unit 1005 may be configured to transmit a second discovery request to a third network node. The second discovery request may include the query parameter having said subset of values that are not supported by any NF of the requested target NF type that is registered in the first network node.

The transmitting unit 1005 may be further configured to transmit, to the second network node, a first discovery response to the first discovery request, wherein the first discovery response comprises said subset of values.

The first discovery response may comprise a third list with a number of NFs of the requested target NF type whose registration information is known by the first network node and supporting the plurality of values, excluding said subset of values, of the query parameter.

The receiving unit 701 may be further configured to receive, from the third network node, a second discovery response to the second discovery request.

In an exemplary embodiment, the second discovery response may include:

afirst list with a number of NFs of the requested target NF type that altogether support said subset of values of the query parameter; or

at least one second continue discovery information, each for indicating to transmit a third discovery request that includes the query parameter having at least a part of said subset of values, so as to find a first list with a number of NFs of the requested target NF type that altogether support said subset of values of the query parameter.

In an exemplary embodiment, the second discovery response may further include a second list with a number of NFs of the requested target NF type whose registration information is known by the third network node and supporting at least a part of said subset of values of the query parameter, in addition to the at least one second continue discovery information.

In an exemplary embodiment, the second continue discovery information may include at least one of:

an indication for indicating to transmit the third discovery request that includes the query parameter having at least the part of said subset of values,

a list of at least the part of said subset of values of the query parameter,

an NRF discovery URI to which the second network node can transmit the third discovery request, so as to find the second list of NFs of the requested target NF type supporting at least the part of said subset of values of the query parameter.

In an exemplary embodiment, the second discovery request may be forwarded by the first network node from the second network node. In this case, after the determination unit 1003 determines that said subset of values of the query parameter are not supported by any NF of the requested target NF type that is registered in the first network node, the transmitting unit 1005 may be further configured to, transmit, to the second network node, a first discovery response to the first discovery request, wherein the first discovery response includes first continue discovery information for indicating the second network node to transmit the second discovery request that includes the query parameter having said subset of values. And the receiving unit 1001 may be further configured to receive the second discovery request from the second network node.

In an exemplary embodiment, the first discovery response may further include a third list with a number of NFs of the requested target NF type whose registration information is known by the first network node and supporting the plurality of values, excluding said subset of values, of the query parameter.

In an exemplary embodiment, the first continue discovery information may include at least one of:

an indication for indicating the second network node to transmit the second discovery request that includes the query parameter having said subset of values,

a list of said subset of values of the query parameter,

an NRF discovery URI to which the second network node can transmit the second discovery request, so as to find the first list of NFs of the requested target NF type supporting said subset of values of the query parameter.

In an exemplary embodiment, the transmitting unit 1003 may be further configured to forward, to the second network node, the second discovery response that includes the first list of NFs of the requested target NF type that altogether support said subset of values of the query parameter or the at least one second continue discovery information.

In an exemplary embodiment, the transmitting unit 1003 may be further configured to forward, to the second network node, the second discovery response that includes the at least one second continue discovery information and the second list of NFs of the requested target NF type whose registration information is known by the third network node and supporting at least the part of said subset of values of the query parameter.

In an exemplary embodiment, the first network node 1000 may further include a generation unit (not shown) , which may be configured to generate a third list with a number of NFs of the requested target NF type that are registered in the first network node and support the plurality of values, excluding said subset of values, of the query parameter. The first network node 1000 may further include a storage unit (not shown) , which may be configured to store the third list of NFs. The generation unit may further be triggered to generate the second discovery request that includes the query parameter having said subset of values.

In an exemplary embodiment, the transmitting unit 1005 may be further configured to transmit, to at least one fourth network node respectively, at least one third discovery request according to the received at least one second continue discovery information, each of the at least one third discovery request including the query parameter having the respective part of said subset of values; and the receiving unit 1001 may be further configured to receive, from the at least one fourth network node, a first list with a number of NFs that altogether support said subset of values of the query parameter in at least one third discovery response to the at least one third discovery request as a search result.

In an exemplary embodiment, the first network node 1000 may further include a combination unit (not shown) , which may be configured to combine the first list of NFs and the third list of NFs; and the transmitting unit 1005 may be further configured to transmit the combined list of NFs to the second network node in the first discovery response.

In an exemplary embodiment, the transmitting unit 1005 may be further configured to transmit, to the second network node, a first discovery response that includes a search ID identifying a search result for the first discovery request, and a timer indicating the second network node to retrieve the search result after the timer is expired.

In an exemplary embodiment, the combination unit may be further configured to combine the first list of NFs and the third list of NFs; the receiving unit 1001 may be further configured to receive, from the second network node, a fourth discovery request that includes the search ID for retrieving the combined list of NFs, after the timer is expired; and the transmitting unit 1005 may be further configured to transmit the combined list of NFs to the second network node in the fourth discovery response.

In an exemplary embodiment, the first discovery response, the second discovery response, the third discovery response or the fourth discovery response may be one of:

an acceptance response message, or

a rejection response message.

In an exemplary embodiment, the first, third and fourth network nodes respectively host NRF, and the second network node implements NF service consumer of an NRF discovery service.

In an exemplary embodiment, the NF service consumer includes at least one of: MB-SMF, or TSCTSF, the NF of the requested target NF type includes AMF, and the query parameter includes a TA List.

Hereinafter, a structure of a first network node according to another exemplary embodiment of the present disclosure will be described with reference to FIG. 11. FIG. 11 schematically shows a block diagram of a first network node 1100 according to an exemplary embodiment of the present disclosure. The first network node 1100 in FIG. 11 may perform the methods 500 and/or 520 with reference to FIGs. 5A and 5B and signaling sequence diagrams with reference to FIGS. 8 and 9. Accordingly, some detailed description on the first network node 1100 may refer to the corresponding description of the method s 500 and/or 520 as shown in FIGs. 5A and 5B in conjunction with the signaling sequence diagrams as shown in FIGS. 8 and 9, and thus will be omitted here for simplicity.

As shown in FIG. 11, the first network node 1100 includes at least one processor 1101 and at least one memory 1103. The at least one processor 1101 includes e.g., any suitable CPU (Central Processing Unit) , microcontroller, DSP (Digital Signal Processor) , etc., capable of executing computer program instructions. The at least one memory 1103 may be any combination of a RAM (Random Access Memory) and a ROM (Read Only Memory) . The at least one memory 1103 may also include persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, or solid state memory or even remotely mounted memory.

The at least one memory 1103 stores instructions executable by the at least one processor 1101. The instructions, when loaded from the at least one memory 1103 and executed on the at least one processor 1101, may cause the first network node 1100 to perform the actions, e.g., of the procedures as described earlier in conjunction with FIGS. 5, 8 and 9, and thus will be omitted here for simplicity.

Hereinafter, a structure of a second network node according to an exemplary embodiment of the present disclosure will be described with reference to FIG. 12. FIG. 12 schematically shows a block diagram of the second network node 1200 according to an exemplary embodiment of the present disclosure. The second network node 1200 in FIG. 12 may perform the method 600 as described previously with reference to FIG. 6 and signaling sequence diagram with reference to FIG. 8. Accordingly, some detailed description on the second network node 1200 may refer to the corresponding description of the method 600 in FIG. 6 in conjunction with the signaling sequence diagram as shown in FIG. 8, and thus will be omitted here for simplicity.

As shown in FIG. 12, the second network node 1200 may include at least a transmitting unit 1201 and a receiving unit 1203.

The transmitting unit 1201 may be configured to transmit, to a first network node, a first discovery request that comprises a query parameter having a plurality of values to be satisfied by NF (s) and a subset of the plurality of values of the query parameter that are not satisfied by any NF of the requested target NF type that is registered in the first network node.

The receiving unit 1203 may be configured to receive, from the first network node, a first discovery response to the first discovery request. The first discovery response comprises the subset of the plurality of values of the query parameter that are not satisfied by any NF of the requested target NF type that is registered in the first network node

The transmitting unit 1201 may be further configured to transmit the second discovery request to the first network node according to the first continue discovery information.

a list of said subset of values of the query parameter,

an NRF discovery Uniform URI to which the second network node can transmit the second discovery request, so as to find a first list with a number of NFs of the requested target NF type supporting said subset of values of the query parameter.

In an exemplary embodiment, the receiving unit 1203 may be further configured to receive, from the first network node, a second discovery response that includes a first list with a number of NFs of the requested target NF type that altogether support said subset of values of the query parameter or at least one second continue discovery information, wherein each of the at least one second continue discovery information indicates the second network node to transmit a third discovery request that includes the query parameter having a respective part of said subset of values, so as to find the first list of NFs supporting said subset of values of the query parameter.

In an exemplary embodiment, the second discovery response further includes a second list with a number of NFs of the requested target NF type whose registration information is known by a second NRF and supporting at least a part of said subset of values of the query parameter, in addition to the at least one second continue discovery information.

a list of at least the part of said subset of values of the query parameter,

an NRF discovery URI to which the second network node can transmit the third discovery request, so as to find a second list with a number of NFs of the requested target NF type supporting at least the part of said subset of values of the query parameter.

In an exemplary embodiment, the transmitting unit 1201 may be further configured to transmit, to a fourth network node, at least one of third discovery request according to the received at least one second continue discovery information, each of the at least one third discovery request including the query parameter having the respective part of said subset of values; and the receiving unit 1203 may be further configured to receive, from the at least one fourth network node, the first list of NFs that altogether support said subset of values of the query parameter in at least one third discovery response to the at least one third discovery request.

In an exemplary embodiment, the first discovery response, the second discovery response, or the third discovery response may be one of:

an acceptance response message, or

a rejection response message.

In an exemplary embodiment, the NF service consumer includes at least one of: MB-SMF, or TSCTSF,

the NF of the requested target NF type includes AMF, and

the query parameter includes a TA List.

In another exemplary embodiment, the second network node 1200’ in FIG. 12 may perform the method 700 as described previously with reference to FIG. 7 and signaling sequence diagram with reference to FIG. 9. Accordingly, some detailed description on the second network node 1200’ may refer to the corresponding description of the method 700 in FIG. 7 in conjunction with the signaling sequence diagram as shown in FIG. 9, and thus will be omitted here for simplicity.

As shown in FIG. 12, the second network node 1200’ may include at least a transmitting unit 1201’ and a receiving unit 1203’ .

The transmitting unit 1201’ may be configured to transmit, to a first network node, a first discovery request that includes a query parameter having a plurality of values to be supported by NF (s) and an indication indicating a capability of receiving an aggregation of NFs of a requested target NF type and continue discovery information.

The receiving unit 1203’ may be configured to receive, from the first network node, a list with a number of NFs of the requested target NF type supporting the plurality of values of the query parameter.

In an exemplary embodiment, the receiving unit 1203’ may be further configured to receive, from the first network node, a search ID identifying a search result for the first discovery request, and a timer indicating the second network node to retrieve the respective search result after the timer is expired; and the transmitting unit 1201’ may be further configured to transmit, to the first network node, a fourth discovery request that includes the search ID for retrieving said list of NFs, after the timer is expired.

In an exemplary embodiment, the first network node hosts NRF, and the second network node implements NF service consumer of an NRF discovery service.

the NF of the requested target NF type includes AMF, and

the query parameter includes a TA List.

Hereinafter, a structure of a second network node according to another exemplary embodiment of the present disclosure will be described with reference to FIG. 13. FIG. 13 schematically shows a block diagram of a second network node 1300/1300’ according to an exemplary embodiment of the present disclosure.

The second network node 1300 in FIG. 13 may perform the method 600 as described previously with reference to FIG. 6 and signaling sequence diagram with reference to FIG. 8. Accordingly, some detailed description on the second network node 1300 may refer to the corresponding description of the method 600 in FIG. 6 in conjunction with the signaling sequence diagrams as shown in FIG. 8, and thus will be omitted here for simplicity.

As shown in FIG. 13, the second network node 1300 includes at least one processor 1301 and at least one memory 1303. The at least one processor 1301 includes e.g., any suitable CPU (Central Processing Unit) , microcontroller, DSP (Digital Signal Processor) , etc., capable of executing computer program instructions. The at least one memory 1003 may be any combination of a RAM (Random Access Memory) and a ROM (Read Only Memory) . The at least one memory 1303 may also include persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, or solid state memory or even remotely mounted memory.

The at least one memory 1303 stores instructions executable by the at least one processor 1301. The instructions, when loaded from the at least one memory 1303 and executed on the at least one processor 1301, may cause the second network node 1300 to perform the actions, e.g., of the procedures as described earlier respectively in conjunction with FIGS. 6 and 8, and thus will be omitted here for simplicity.

The second network node 1300’ in FIG. 13 may perform the method 700 as described previously with reference to FIG. 7 and signaling sequence diagram with reference to FIG. 9. Accordingly, some detailed description on the second network node 1300’ may refer to the corresponding description of the method 700 in FIG. 7 in conjunction with the signaling sequence diagrams as shown in FIG. 9, and thus will be omitted here for simplicity.

As also shown in FIG. 13, the second network node 1300’ includes at least one processor 1301’ and at least one memory 1303’ . The at least one processor 1301’ includes e.g., any suitable CPU (Central Processing Unit) , microcontroller, DSP (Digital Signal Processor) , etc., capable of executing computer program instructions. The at least one memory 1303’ may be any combination of a RAM (Random Access Memory) and a ROM (Read Only Memory) . The at least one memory 1303’ may also include persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, or solid state memory or even remotely mounted memory.

The at least one memory 1303’s tores instructions executable by the at least one processor 1301’ . The instructions, when loaded from the at least one memory 1303’ and executed on the at least one processor 1301’ , may cause the second network node 1300’ to perform the actions, e.g., of the procedures as described earlier respectively in conjunction with FIGS. 7 and 9, and thus will be omitted here for simplicity.

The present disclosure also provides at least one computer program product in the form of a non-volatile or volatile memory, e.g., a non-transitory computer readable storage medium, an Electrically Erasable Programmable Read-Only Memory (EEPROM) , a flash memory and a hard drive. The computer program product includes a computer program.

The computer program includes: code/computer readable instructions, which when executed by the at least one processor 1101 causes the first network node 1100 to perform the actions, e.g., of the procedures described earlier in conjunction with FIGS. 5, 8 and 9; or code/computer readable instructions, which when executed by the at least one processor 1301 causes the second network node 1300 to perform the actions, e.g., of the procedures described earlier respectively in conjunction with FIGS. 6 and 8; or code/computer readable instructions, which when executed by the at least one processor 1301’ causes the second network node 1300’ to perform the actions, e.g., of the procedures described earlier respectively in conjunction with FIGS. 7 and 9.

The computer program product may be configured as a computer program code structured in computer program modules. The computer program modules could essentially perform the actions of the flow illustrated in any of FIGS. 5～9.

The processor may be a single CPU (Central processing unit) , but could also include two or more processing units. For example, the processor may include general purpose microprocessors; instruction set processors and/or related chips sets and/or special purpose microprocessors such as Application Specific Integrated Circuit (ASICs) . The processor may also include board memory for caching purposes. The computer program may be carried by a computer program product connected to the processor. The computer program product may include a non-transitory computer readable storage medium on which the computer program is stored. For example, the computer program product may be a flash memory, a Random-access memory (RAM) , a Read-Only Memory (ROM) , or an EEPROM, and the computer program modules described above could in alternative embodiments be distributed on different computer program products in the form of memories.

As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module. ” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the present disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer) , special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as or C++. However, the computer program code for carrying out operations of the present disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN) , or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider) .

Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings.

The following describes Methods and apparatuses for discovery of network function according to various other embodiments.

The following embodiments of the disclosure generally relate to communication, and, more particularly, to methods and apparatuses for discovery of network function.

In 5th generation (5G) multicast/broadcast services (MBS) , with respect to how an MBS session is started for broadcast, 3rd generation partnership project (3GPP) technical specification (TS) 23.247 V17.4.0 has the following description in section 7.3.1.

The MB-SMF may use NRF to discover the AMF (s) supporting MBS based on the MBS service area and select the appropriate one (s) . Then the MB-SMF sends the Namf_MBSBroadcast_ContextCreate (TMGI, N2 SM information ( [LL SSM] , 5G QoS Profile) , MBS service area, [MBS FSA ID (s) ] ) messages to the selected AMF (s) in parallel if the service type is broadcast service. The MB-SMF may include a maximum response time in the request.

In time sensitive communication and time synchronization, S2-2211309 23.502 CR3610R2 (Rel-18, 'B') entitled “Support for coverage area filters for time synchronization service –procedures” has the following description in section 4.15.9.3.2 (Time synchronization service activation) .

- For each target UE, TSCTSF determines whether the TSCTSF has subscribed for the UE presence in Area of Interest composed by the TA (s) in the spatial validity condition. If not, the TSCTSF discovers the AMF (s) serving TAs that comprise the spatial validity condition, using the NRF discovery service (Nnrf_NFDiscovery_Request) with the list of TA (s) . Then the TSCTSF subscribes to the AMF (s) to receive notifications about the UE presence in Area of Interest using Namf_EventExposure operation with the corresponding event filters as described in clause 5.2.2.3. The subscribed area of interest may be the same as the spatial validity condition or may be a subset of the spatial validity condition (e.g. a list of TAs) based on the latest known UE location.

With respect to the discovery operation of network repository function (NRF) , 3GPP TS 23.502 V17.6.0 has the following description in section 5.2.7.3.2(Nnrf_NFDiscovery_Request service operation) .

- AMF region, AMF Set, GUAMI and Target TAI (s) .

One of the objects of the disclosure is to provide an improved solution for discovery of network function. In particular, one of the problems to be solved by the disclosure is that the existing solution for discovering a network function (NF) instance matching a list of query parameters of a predetermined parameter type is not flexible thereby decreasing the efficiency of discovery.

According to a twenty-first aspect of the disclosure, there is provided a method performed by a service producer. The method may comprise receiving, from a service consumer, a query request for discovering at least one NF instance that matches a predetermined condition comprising a list of query parameters of a predetermined parameter type. The request may indicate the service producer to return an NF instance aggregation comprising multiple NF instances. Each of the multiple NF instances may match a subset of the list of query parameters and the multiple NF instances together may match the list of query parameters. The method may further comprise determining a query response to the query request, based on the query request. The method may further comprise sending the query response to the service consumer.

In this way, it is possible to allow the service producer to return an NF instance aggregation in a query response thereby increasing the flexibility of discovery.

In an embodiment of the disclosure, the query response may indicate one or more NF instance aggregations each of which matches the list of query parameters.

In an embodiment of the disclosure, the query request may comprise a first indicator that indicates the list of query parameters and indicates the service producer to return an NF instance aggregation.

In an embodiment of the disclosure, the first indicator may be an array or map data structure whose elements are the query parameters contained in the list. A name of the first indicator may be configured to indicate the service producer to return an NF instance aggregation.

In an embodiment of the disclosure, the query request may comprise: a second indicator indicating the list of query parameters; and a third indicator indicating the service producer to return an NF instance aggregation.

In an embodiment of the disclosure, the third indicator may comprise: a first sub-indicator indicating a name of the second indicator; and a second sub-indicator having a first value for indicating the service producer to return an NF instance aggregation. The second sub-indicator can take the first value, or a second value for indicating the service producer to return one or more NF instances each of which matches the query parameters contained in the list.

In an embodiment of the disclosure, the second indicator may be an array or map data structure whose elements are the query parameters contained in the list.

In an embodiment of the disclosure, determining the query response to the query request may comprise determining a first set of NF instances each of which matches a subset of the list of query parameters. Determining the query response to the query request may further comprise determining, from the first set of NF instances, a second set of NF instances so that a union set of the query parameters matched by the second set of NF instances is the list of query parameters.

In an embodiment of the disclosure, the query response may comprise a fourth indicator indicating, for each of the one or more NF instance aggregations, members of the NF instance aggregation and the corresponding query parameters matched by the members.

In an embodiment of the disclosure, each of the one or more NF instance aggregations may be represented by a first map data structure.

In an embodiment of the disclosure, each member of the NF instance aggregation and the corresponding one or more query parameters matched by the member may be represented by a second map data structure.

In an embodiment of the disclosure, a key of the second map data structure may be an identifier (ID) of the member of the NF instance aggregation, and the corresponding one or more query parameters matched by the member may be represented by an array data structure.

In an embodiment of the disclosure, the NF instance aggregation may further comprise one or more NF instances each of which matches the list of query parameters.

In an embodiment of the disclosure, the service consumer may be one of: a multicast/broadcast session management function (MB-SMF) ; and a time sensitive communication and time synchronization function (TSCTSF) .

In an embodiment of the disclosure, the predetermined parameter type may be one of following types: tracking area identity (TAI) ; subscription permanent identifier (SUPI) ; public land mobile network (PLMN) ; single network slice selection assistance information (SNSSAI) ; network slice instance (NSI) ; group ID; data network access identifier (DNAI) ; event ID; network data analytics function (NWDAF) event; analytics information; and multicast/broadcast service (MBS) session ID.

In an embodiment of the disclosure, the NF instance may be an access and mobility management function (AMF) .

In an embodiment of the disclosure, the service producer may be a network repository function (NRF) .

According to a twenty-second aspect of the disclosure, there is provided a method performed by a service consumer. The method may comprise sending, to a service producer, a query request for discovering at least one NF instance that matches a predetermined condition comprising a list of query parameters of a predetermined parameter type. The request may indicate the service producer to return an NF instance aggregation comprising multiple NF instances. Each of the multiple NF instances may match a subset of the list of query parameters and the multiple NF instances together may match the list of query parameters. The method may further comprise receiving, from the service producer, a query response to the query request.

In this way, it is possible to allow the service consumer to receive an NF instance aggregation in a query response thereby increasing the flexibility of discovery.

In an embodiment of the disclosure, the third indicator may comprise: a first sub-indicator indicating a name of the second indicator; and a second sub-indicator having a first value for indicating the service producer to return an NF instance aggregation. The second sub-indicator can take the first value, or a second value for indicating the service producer to return one or more NF instances each of which matches the query parameters contained in the list

In an embodiment of the disclosure, a key of the second map data structure may be an ID of the member of the NF instance aggregation, and the corresponding one or more query parameters matched by the member may be represented by an array data structure.

In an embodiment of the disclosure, the service consumer may be one of: an MB-SMF; and a TSCTSF.

In an embodiment of the disclosure, the predetermined parameter type may be one of following types: TAI; SUPI; PLMN; SNSSAI; NSI; group ID; DNAI; event ID; NWDAF event; analytics information; and MBS session ID.

In an embodiment of the disclosure, the NF instance may be an AMF.

In an embodiment of the disclosure, the service producer may be an NRF.

According to a twenty-third aspect of the disclosure, there is provided a service producer. The service producer may comprise at least one processor and at least one memory. The at least one memory may contain instructions executable by the at least one processor, whereby the service producer may be operative to receive, from a service consumer, a query request for discovering at least one NF instance that matches a predetermined condition comprising a list of query parameters of a predetermined parameter type. The request may indicate the service producer to return an NF instance aggregation comprising multiple NF instances. Each of the multiple NF instances may match a subset of the list of query parameters and the multiple NF instances together may match the list of query parameters. The service producer may be further operative to determine a query response to the query request, based on the query request. The service producer may be further operative to send the query response to the service consumer.

In an embodiment of the disclosure, the service producer may be operative to perform the method according to the above first aspect.

According to a twenty-fourth aspect of the disclosure, there is provided a service consumer. The service consumer may comprise at least one processor and at least one memory. The at least one memory may contain instructions executable by the at least one processor, whereby the service consumer may be operative to send, to a service producer, a query request for discovering at least one NF instance that matches a predetermined condition comprising a list of query parameters of a predetermined parameter type. The request may indicate the service producer to return an NF instance aggregation comprising multiple NF instances. Each of the multiple NF instances may match a subset of the list of query parameters and the multiple NF instances together may match the list of query parameters. The service consumer may be further operative to receive, from the service producer, a query response to the query request.

In an embodiment of the disclosure, the service consumer may be operative to perform the method according to the above second aspect.

According to a twenty-fifth aspect of the disclosure, there is provided a computer program product. The computer program product may comprise instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any of the above twenty-first and twenty-second aspects.

According to a twenty-sixth aspect of the disclosure, there is provided a computer readable storage medium. The computer readable storage medium may store thereon instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any of the above twenty-first and twenty-second aspects.

According to a twenty-seventh aspect of the disclosure, there is provided a service producer. The service producer may comprise a reception module for receiving, from a service consumer, a query request for discovering at least one NF instance that matches a predetermined condition comprising a list of query parameters of a predetermined parameter type. The request may indicate the service producer to return an NF instance aggregation comprising multiple NF instances. Each of the multiple NF instances may match a subset of the list of query parameters and the multiple NF instances together may match the list of query parameters. The service producer may further comprise a determination module for determining a query response to the query request, based on the query request. The service producer may further comprise a sending module for sending the query response to the service consumer.

According to a twenty-eighth aspect of the disclosure, there is provided a service consumer. The service consumer may comprise a sending module for sending, to a service producer, a query request for discovering at least one NF instance that matches a predetermined condition comprising a list of query parameters of a predetermined parameter type. The request may indicate the service producer to return an NF instance aggregation comprising multiple NF instances. Each of the multiple NF instances may match a subset of the list of query parameters and the multiple NF instances together may match the list of query parameters. The service consumer may further comprise a reception module for receiving, from the service producer, a query response to the query request.

According to a twenty-ninth aspect of the disclosure, there is provided a method implemented in a communication system including a service producer and a service consumer. The method may comprise steps of the methods according to the above twenty-first and twenty-second aspects.

According to a thirtieth aspect of the disclosure, there is provided a communication system including a service producer according to the above third or seventh aspect and a service consumer according to the above twenty-fourth or twenty-eighth aspect.

According to some embodiment (s) of the disclosure, the service producer can be allowed to discover a set of NF instances as an NF instance aggregation, by partially matching a parameter list in the query request. This can provide a more flexible and efficient way for discovery of NF instance. In addition, the service consumer can be allowed to further use the discovered set of NF instances.

For the purpose of explanation, details are set forth in the following description in order to provide a thorough understanding of the embodiments disclosed. It is apparent, however, to those skilled in the art that the embodiments may be implemented without these specific details or with an equivalent arrangement.

Currently, the NF discovery procedure enables a NF to discover a list of candidates NF instance (s) where each NF instance matches all query parameters except those query parameters which are defined as preferred parameters.

With respect to Nnrf_NFDiscovery Service, 3GPP TS 29.510 V18.0.0 (2022-09) has the following description in section 6.2.3.2.3.1 ( “GET” ) .

As specified in Table 6.2.3.2.3.1-2 of 3GPP TS 29.510 V18.0.0, the default logical relationship among the query parameters is logical “AND” , i.e. all the provided query parameters shall be matched, with the exception of the “preferred-locality” , “ext-preferred-locality” , “preferred-nf-instances” , “preferred-tai” , “preferred-api-versions” , “preferred-full-plmn” , “preferred-collocated-nf-types” , “preferred-pgw-ind” , “preferred-analytics-delays” , “preferred-features” and “mbs-session-id” query parameters (see Table 6.2.3.2.3.1-1) .

For example, when the query parameter contains a list of TAIs (using “tai-list” ) , the network repository function (NRF) shall only return candidate NFs which support all the TAIs in the list. The term TAI refers to tracking area identity.

However, there are several use cases where no single NF instance can be a candidate, i.e. to satisfy all the elements in an array or map style query parameter. As an example, for multicast/broadcast services (MBS) , it is likely the MBS service area for an MBS session includes a list of tracking areas (TAs) that are served by different access and mobility management functions (AMFs) , i.e., a single AMF does not serve all TAs in the MBS service area. As another example, for time synchronization service, there might be cases where a spatial validity condition includes TAs that are served by different AMFs, i.e., a single AMF does not serve all TAs in the spatial validity condition.

The current discovery function, i.e. using “tai” , or “tai-list” or “preferred-tai” , does not enable the NRF to return a list of AMFs where none of the AMFs itself supports all TAIs included in the query request but together all these AMFs will support all TAIs included in the query request.

Note that those preferred query parameters, e.g., “preferred-tai” , does not help, since the NF consumer (doing discovery) would like to find a candidate that shall support all query parameters, e.g. all TAIs.

Therefore, it would be advantageous to provide a mechanism to enable NRF to return a list of candidate “NF instances aggregation (s) ” where all NF instances within an “NF instance aggregation” have the same NF type and together match all elements included in an array or map style query parameter, while each NF instance within an “NF instance aggregation” may match a subset of elements included in the array or map style query parameter.

The present disclosure proposes an improved solution for discovery of network function. Hereinafter, the solution will be described in detail with reference to FIGs. 14-28. FIG. 14 is a diagram illustrating an exemplary communication system into which an embodiment of the disclosure is applicable. As shown, the communication system comprises a user equipment (UE) 101, a (radio) access network ( (R) AN) 102, a user plane function (UPF) 103, a data network (DN) 104, a network slice-specific and SNPN authentication and authorization function (NSSAAF) 105, an authentication server function (AUSF) 106, an access and mobility management function (AMF) 107, a session management function (SMF) 108, a service communication proxy (SCP) 109, a network slice admission control function (NSACF) 110, a network slice selection function (NSSF) 111, a network exposure function (NEF) 112, a network repository function (NRF) 113, a policy control function (PCF) 114, a unified data management (UDM) 115, an application function (AF) 116, and a time sensitive communication and time synchronization function (TSCTSF) 117. The term SNPN refers to standalone non-public network. The functional description of the above entities can be found from clause 6 of 3GPP TS 23.501 V18.0.0.

Within the context of this disclosure, the term UE or terminal device may also be referred to as, for example, device, access terminal, mobile station, mobile unit, subscriber station, or the like. It may refer to any end device that can access a wireless communication network and receive services therefrom. By way of example and not limitation, the UE or terminal device may include a portable computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and playback appliance, a mobile phone, a cellular phone, a smart phone, a tablet, a wearable device, a personal digital assistant (PDA) , or the like.

In an Internet of things (IoT) scenario, a UE or terminal device 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 or terminal device and/or a network equipment. In this case, the UE or terminal device may be a machine-to-machine (M2M) device, which may, in a 3GPP context, be referred to as a machine-type communication (MTC) device. Particular examples of such machines or devices may include sensors, metering devices such as power meters, industrial machineries, bikes, vehicles, or home or personal appliances, e.g. refrigerators, televisions, personal wearables such as watches, and so on.

As used herein, the term “communication system” refers to a system following any suitable communication standards, such as the first generation (1G) , 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G communication protocols, and/or any other protocols either currently known or to be developed in the future. Furthermore, the communications between a terminal device and a network function (or a network node) in the communication system may be performed according to any suitable generation communication protocols, including, but not limited to, 1G, 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G communication protocols, and/or any other protocols either currently known or to be developed in the future. In addition, the specific terms used herein do not limit the present disclosure only to the communication system related to the specific terms, which however can be more generally applied to other communication systems.

FIG. 15 is a flowchart illustrating a method performed by a service producer according to an embodiment of the disclosure. For example, the service producer may be an NRF or any other network function having similar functionality. Note that the network function mentioned in this document may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g. on a cloud infrastructure.

At block 1502, the service producer receives, from a service consumer, a query request for discovering at least one NF instance that matches a predetermined condition comprising a list of query parameters of a predetermined parameter type. The request indicates the service producer to return an NF instance aggregation comprising multiple NF instances. Each of the multiple NF instances matches a subset of the list of query parameters and the multiple NF instances together match the list of query parameters. For example, the service consumer may be a multicast/broadcast SMF (MB-SMF) , or a TSCTSF, or any other suitable network function. The at least one NF instance may be of the same NF type which may be AMF or any other suitable NF type. The list of query parameters may be represented by any suitable data structure such as an array, a map, etc. The number of the list may be one or more than one. The predetermined parameter type may be one of following types: tracking area identity (TAI) ; subscription permanent identifier (SUPI) ; public land mobile network (PLMN) ; single network slice selection assistance information (SNSSAI) ; network slice instance (NSI) ; group identifier (ID) ; data network access identifier (DNAI) ; event ID; network data analytics function (NWDAF) event; analytics information; MBS session ID; etc. Note that in addition to the list of query parameters, the predetermined condition may comprise any other suitable condition depending on the specific application scenario.

Note that the number (or quantity) of the NF instance aggregation may be one or more than one. The term “subset” mentioned at block 1502 refers to that the size of this subset is smaller than the size of the full set of the query parameters contained in the list. Since the multiple NF instances together match the list of query parameters, the multiple NF instances within the NF instance aggregation may be deemed as one candidate NF instance. Since there may be one or more NF instances each of which matches the list of query parameters depending on the specific application scenario, the NF instance aggregation may optionally further comprise such one or more NF instances.

For example, there may be two options for the service consumer to indicate the service producer to return an NF instance aggregation. In the first option, the query request may comprise a first indicator that indicates the list of query parameters and indicates the service producer to return an NF instance aggregation. For instance, the first indicator may be an array or map data structure whose elements are the query parameters contained in the list, and a name of the first indicator may be configured to indicate the service producer to return an NF instance aggregation.

In the second option, the query request may comprise: a second indicator indicating the list of query parameters; and a third indicator indicating the service producer to return an NF instance aggregation. For instance, the second indicator may be an array or map data structure whose elements are the query parameters contained in the list. The third indicator may comprise: a first sub-indicator indicating a name of the second indicator; and a second sub-indicator having a first value for indicating the service producer to return an NF instance aggregation. The second sub-indicator can take the first value, or a second value for indicating the service producer to return one or more NF instances each of which matches the query parameters contained in the list. As an exemplary example, the first value may be a string “partial-match” and the second value may be a string “full-match” . Note that the present disclosure is not limited to the above two options and any other suitable indicating manner may be used as long as it can indicate the service producer to return an NF instance aggregation.

At block 1504, the service producer determines a query response to the query request, based on the query request. For instance, the query response may indicate one or more NF instance aggregations each of which matches the list of query parameters. As an exemplary example, the query response may comprise a fourth indicator indicating, for each of the one or more NF instance aggregations, members of the NF instance aggregation and the corresponding query parameters matched by the members. Note that since the NF instance aggregation may optionally further comprise one or more NF instances each of which matches the list of query parameters, the member mentioned here may refer to each of the multiple NF instances contained in the NF instance aggregation, and optionally each of the one or more NF instances each matching the list of query parameters.

In the fourth indicator, each of the one or more NF instance aggregations may be represented by a first map data structure. Each member of the NF instance aggregation and the corresponding one or more query parameters matched by the member may be represented by a second map data structure. A key of the second map data structure may be an ID of the member of the NF instance aggregation, and the corresponding one or more query parameters matched by the member may be represented by an array data structure.

For example, block 1504 may be implemented as including blocks 1608-1610 of FIG. 16. At block 1608, the service producer determines a first set of NF instances each of which matches a subset of the list of query parameters. For instance, for each NF instance whose NF profile is maintained by the service producer, the service producer may determine whether the query parameters supported by the NF instance has an intersection with the list of query parameters. If the determination result is positive, the NF instance may be determined as a member of the first set. At block 1610, the service producer determines, from the first set of NF instances, a second set of NF instances so that a union set of the query parameters matched by the second set of NF instances is the list of query parameters. As a simplest example, for each of various combinations of the members of the first set, the service producer may determine whether the combination satisfies the condition that the union set of the query parameters matched by the combination is the list of query parameters. If the determination result is positive, this combination may be determined as one second set.

At block 1506, the service producer sends the query response to the service consumer. With the method of FIG. 15, it is possible to allow the service producer to return an NF instance aggregation in a query response thereby increasing the flexibility of discovery.

FIG. 17 is a flowchart illustrating a method performed by a service consumer according to an embodiment of the disclosure. For example, the service consumer may be an MB-SMF, or a TSCTSF, or any other suitable network function. At block 1702, the service consumer sends, to a service producer, a query request for discovering at least one NF instance that matches a predetermined condition comprising a list of query parameters of a predetermined parameter type. The request indicates the service producer to return an NF instance aggregation comprising multiple NF instances. Each of the multiple NF instances matches a subset of the list of query parameters and the multiple NF instances together match the list of query parameters. For example, the service producer may be an NRF or any other network function having similar functionality. The at least one NF instance may be of the same NF type which may be AMF or any other suitable NF type. The predetermined parameter type may be one of following types: TAI; SUPI; PLMN; SNSSAI; NSI; group ID; DNAI; event ID; NWDAF event; analytics information; MBS session ID; etc.

Since the multiple NF instances together match the list of query parameters, the multiple NF instances within the NF instance aggregation may be deemed as one candidate NF instance. Since there may be one or more NF instances each of which matches the list of query parameters depending on the specific application scenario, the NF instance aggregation may optionally further comprise such one or more NF instances.

In the second option, the query request may comprise: a second indicator indicating the list of query parameters; and a third indicator indicating the service producer to return an NF instance aggregation. For instance, the second indicator may be an array or map data structure whose elements are the query parameters contained in the list. The third indicator may comprise: a first sub-indicator indicating a name of the second indicator; and a second sub-indicator having a first value for indicating the service producer to return an NF instance aggregation. The second sub-indicator can take the first value, or a second value for indicating the service producer to return one or more NF instances each of which matches the query parameters contained in the list. As an exemplary example, the first value may be a string “partial-match” and the second value may be a string “full-match” . Other details about the query request, the NF instance aggregation and how to indicate the service producer to return an NF instance aggregation have been described above with respect to block 1502 and thus are omitted here.

At block 1704, the service consumer receives, from the service producer, a query response to the query request. For instance, the query response may indicate one or more NF instance aggregations each of which matches the list of query parameters. As an exemplary example, the query response may comprise a fourth indicator indicating, for each of the one or more NF instance aggregations, members of the NF instance aggregation and the corresponding query parameters matched by the members. Note that since the NF instance aggregation may optionally further comprise one or more NF instances each of which matches the list of query parameters, the member mentioned here may refer to each of the multiple NF instances contained in the NF instance aggregation, and optionally each of the one or more NF instances each matching the list of query parameters.

With the method of FIG. 17, it is possible to allow the service consumer to receive an NF instance aggregation in a query response thereby increasing the flexibility of discovery.

FIG. 18 is a flowchart illustrating an exemplary process according to an embodiment of the disclosure. In this exemplary process, the service consumer is NF_A (e.g. an MB-SMF) and the service producer is an NRF. The process also relates to four entities, i.e. NF_B1 (e.g. AMF1) , NF_B2 (e.g. AMF2) , NF_B3 (e.g. AMF3) and NF_B4 (e.g. AMF4) . At step 1, an NF of a predetermined NF type register its NF (service) profile in the NRF, together with the list of potential services offered by the NF, and the NRF marks the NF as available to be discovered by other NFs. For example, an AMF registers the list of TAIs the AMF can serve to the NRF as part of AmfInfo in the NFProfile. At step 1a, AMF1 includes the taiList (TAI1, TAI2, TAI10, TAI12) in the AmfInfo during the AMF1’s registration to the NRF. At step 1b, AMF2 includes the taiList (TAI3, TAI4, TAI5, TAI7, TAI8) in the AmfInfo during the AMF2’s registration to the NRF. At step 1c, AMF3 includes the taiList (TAI6, TAI9) in the AmfInfo during the AMF3’s registration to the NRF. At step 1d, AMF4 includes the taiList (TAI16, TAI19) in the AmfInfo during the AMF3’s registration to the NRF.

At step 2, the NF service consumer discovers the candidate NF (service) instances available in the network by invoking Nnrf_NFDiscovery service towards the NRF, e.g., using the target service name and target NF type as one of query parameters for GET method as specified in clause 6.2.3.2.3.1 of 3GPP TS 29.510. In this process, at step 2a, the NF service consumer includes a new query parameter “tai-list-for-nf-aggre” , so as to request the NRF to return a list of candidates “NF instances aggregation” where a NF instance aggregation at least comprises more than one NF instances with the same NF type and together all NF instances within the NF instance aggregation match all elements included in an array or map style query parameter (in this case it is “tai-list-for-nf-aggre” ) ; while each NF instance within the “NF instance aggregation” may match a subset of elements included in the array or map style query parameter.

For example, the MB-SMF may use the NRF to discover the AMF (s) supporting MBS based on the MBS service area. It is likely that the MBS service area for a MBS session includes a list of TAs that are served by different AMFs. The MB-SMF discovers AMF (s) by using tai-list-for-nf-aggre (TAI1, TAI2, TAI3, TAI6) as a query parameter. In this example, at step 2b, the NRF returns nfInstanceAggregations (AMF1 (TAI1, TAI2) , AMF2 (TAI3) , AMF3 (TAI6) ) .

At steps 3-4, the NF service consumer communicates with the target NF instance. At step 3, the NF service consumer requests service from the target NF instance. For example, the MB-SMF sends an Namf_MBSBroadcast_ContextCreate (TMGI, N2 SM information ( [LL SSM] , 5G QoS Profile) , MBS service area, [MBS FSA ID (s) ] ) message to the selected AMF (s) (AMF1, AMF2, AMF3) in parallel if the service type is broadcast service. At step 4, the NF service consumer receives an NF service response from the target NF instance.

The above process illustrates one of example use cases of the present disclosure. In this use case, an MB-SMF needs to find a list of AMFs to start a broadcast MBS session (see step 2 of section 7.3.1 of 3GPP TS 23.247 V17.4.0) . The MB-SMF, served as an NF consumer, invokes Nnrf_NFDiscorvery service including a new query parameter, “tai-list-for-nf-aggre” which contains a list of TAIs forming the MBS service area, to request the NRF to return a map of candidate “nf instance aggregations” , where each map of the NF instance aggregations shall be a candidate which supports all TAIs included in the “tai-list-for-nf-aggre” ; while within an NF instance aggregation, each NF instance may support a subset of TAIs.

The NRF is able to return a map of NF instance aggregations, which contains one candidate NF instance aggregation, which contains AMF1, AMF2 and AMF3. The AMF4 does not serve any TAI which is part of MBS service area. The MB-SMF will then invoke Namf_MBSBroadcast service and context create request towards AMF1, AMF2 and AMF3 respectively.

Based on the above description, the process of FIG. 18 proposes an enhanced NF discovery procedure so that the NRF is able to return a list of candidate “NF instances aggregation” where all NF instances within a “NF instance set” form a candidate which together can meet the query parameter (s) . That is, each NF within a “NF instance set” supports only part of the parameters in the list. The discovery function supports partial query when query parameter contains a list of parameters (e.g. TAI, SUPI range) while the corresponding NF only supports a subset of the parameters in the list. In the search result, the NRF also includes the list of parameters (within the query parameters) supported by the NF (s) .

Note that a TSCTSF may also act as the service consumer described above. For example, suppose that the following AMFs register in the NRF lists of TAIs the AMFs can serve:

AMF1 and AMF11: (TAI1, TAI2, TAI10, TAI12)

AMF2 and AMF22: (TAI3, TAI4, TAI5, TAI7, TAI8)

AMF3 and AMF33: (TAI6, TAI9)

Assume that the TSCTSF quires the NRF which AMF (s) serve TA1, TA2, TA3, and TA6. For this purpose, the TSCTSF uses the list of TAIs (TAI1, TAI2, TAI3, TAI6) when invoking the Nnrf_NFDiscovery_Request service operation.

Based on this request, the NRF returns a list of NFs that had indicated during the registration with the NRF that they serve at least one TA from the list of TAIs in the query request. For example, the list of NFs may be as below:

AMF1 (TAI1, TAI2)

AMF2 (TAI3)

AMF3 (TAI6)

That is, a candidate “NF instance aggregation” includes AMF1, AMF2 and AMF3. An alternative candidate may be the “NF Instance aggregation” which includes AMF11, AMF22 and AMF33. Alternatively, the NRF can return an exclusive list of candidate “NF instance aggregations” . Note that the number of the returned “NF instance aggregations” can be any suitable number which is up to NRF implementation.

As an exemplary example, in the NRF, set_intersection may be used during the query to get a list of supported TAIs, as shown below.

Compared with the existing solutions in which there is no good way to enable NFs to discover a set of NF instance (s) by partially matching a parameter list in the query request, the process of FIG. 18 provides a more efficient way to discovery NF instance (s) . Additionally, it enables a NF consumer to further use the provided list of NFs. For instance, in the example of the TSCTSF, the TSCTSF, after receiving a list of AMFs, can make decision about which AMF (s) cover the largest area (with respect to the spatial validity condition) and invoke a subscription only towards these AMFs. The decision at the TSCTSF can be made based on the pre-configuration or other parameters provide in the AF request, etc.

FIG. 19 is a flowchart illustrating an exemplary process into which an embodiment of the disclosure is applicable. FIG. 19 is Figure 7.3.1-1 of 3GPP TS 23.247 V17.4.0. The discovered AMF instance (s) in FIG. 18 may be used by the MB-SMF at step 2 of this exemplary process of FIG. 19. At step 0, based on operation administration and maintenance (OAM) configuration, RAN nodes announce in system information blocks (SIBs) over the radio interface information about the MBS frequency selection area (FSA) IDs and frequencies of neighbouring cells. At step 1, to establish broadcast MBS session, the AF performs temporary mobile group identity (TMGI) allocation and MBS session creation as specified in clause 7.1.1.2 or 7.1.1.3. The MBS service type indicates to be broadcast service. The MBS FSA ID (s) of a broadcast MBS session are communicated in the service announcement towards the UE. The UE compares those MBS FSA IDs (s) with the MBS FSA ID (s) in SIBs for frequency selection.

At step 2, the MB-SMF may use NRF to discover the AMF (s) supporting MBS based on the MBS service area and select the appropriate one (s) . Then the MB-SMF sends the Namf_MBSBroadcast_ContextCreate (TMGI, N2 SM information ( [LL SSM] , 5G QoS Profile) , MBS service area, [MBS FSA ID (s) ] ) messages to the selected AMF (s) in parallel if the service type is broadcast service. The MB-SMF may include a maximum response time in the request. The “SM” refers to session management, the “SSM” refers to source specific Internet protocol (IP) multicast address, the “LL SSM” refers to lower layer SSM, and the “QoS” refers to quality of service.

At step 3, the AMF transfers the MBS Session Resource Setup Request message, which contains the N2 SM information in the received Namf_MBSBroadcast_ContextCreate Request to all next generation RANs (NG-RANs) which support MBS in the MBS service area. The AMF includes the MBS service area. At step 4, NG-RAN creates a Broadcast MBS Session Context and stores the TMGI and the QoS Profile in the MBS Session Context. The LL SSM are optional parameters and only provided by MB-SMF to NG-RAN if N3mb multicast transport is configured to be used in the 5G core network (5GC) . If MBS FSA ID (s) were received, the NG-RAN may use those MBS FSA ID (s) to determine cells/frequencies within the MBS service area to broadcast MBS session data based on OAM configuration about the MBS FSA IDs and related frequencies. At step 5, if NG-RAN prefers to use N3mb multicast transport (and if LL SSM is available in NG-RAN) , the NG-RAN joins the multicast group (i.e. LL SSM) . If NG-RAN prefers to use N3mb unicast transport (or if the LL SSM is not available in NG-RAN) between the NG-RAN and MB-UPF, NG-RAN provides its N3mb DL Tunnel Info.

At step 6, the NG-RAN reports successful establishment of the MBS Session resources (which may include multiple MBS QoS Flows) by sending MBS Session Resource Setup Response (TMGI, N2 SM information ( [N3mb DL Tunnel Info] ) ) message (s) to the AMF. N3mb downlink (DL) Tunnel Info is only available when unicast transport applies between MB-UPF and NG-RAN.

At step 7, the AMF transfers the Namf_MBSBroadcast_ContextCreate Response () to the MB-SMF. The AMF should respond success when it receives the first success response from the NG-RAN (s) . And if all NG-RAN (s) report failure, the AMF should respond failure. The MB-SMF stores the AMF (s) which responds success in the MBS Session Context as the downstream nodes. If the AMF receives the NG-RAN response (s) from all involved NG-RAN (s) , the AMF should include an indication of completion of the operation in all NG-RANs.

At step 8, if N3mb unicast transport is to be used (i.e. N3mb DL Tunnel Info is present in the Namf_MBSBroadcast_ContextCreate Response message from AMF) , the MB-SMF sends an N4mb Session Modification Request to the MB-UPF to allocate the N3mb unicast transport tunnel for a replicated MBS stream for the MBS Session. Otherwise, step 8 can be skipped.

At step 9, NG-RAN broadcasts the TMGI representing the MBS service over radio interface. Step 9 can take place in parallel with step 6. At step 10, another NG-RAN may report successful establishment of the MBS Session resources (which may include multiple MBS QoS Flows) by sending MBS Session Resource Setup Response (TMGI, N2 SM information ([N3mb DL Tunnel Info] ) ) message after the AMF transferred the Namf_MBSBroadcast_ContextCreate Response () to the MB-SMF.

At step 11, the AMF transfers the Namf_MBSBroadcast_ContextStatusNotify request () to the MB-SMF. When the AMF receives the response from all NG-RAN nodes, the AMF includes an indication of the completion of the operation. If the AMF does not receive responses from all NG-RAN nodes before the maximum response time elapses since the reception of the Namf_MBSBroadcast_ContextCreate Request, then the AMF should transfer the Namf_MBSBroadcast_ContextStatusNotify request () which indicates partial success or failure.

At step 12, if N3mb unicast transport is to be used (i.e. N3mb DL Tunnel Info is present in the MBS Session Start Response message from AMF) , the MB-SMF sends an N4mb Session Modification Request to the MB-UPF to allocate the N3mb unicast transport tunnel for a replicated MBS stream for the MBS Session. Otherwise, step 12 can be skipped.

At step 13, the AF starts transmitting the DL media stream to MB-UPF using the N6mb Tunnel, or optionally un-tunnelled i.e. as an IP multicast stream using the HL MC address. The “HL MC address” refers to higher layer IP multicast address. At step 14, the MB-UPF transmits the media stream to NG-RAN via N3mb multicast transport or unicast transport. At step 15, the NG-RAN transmits the received DL media stream using DL point to multipoint (PTM) resources.

Based on the above description, a new query parameter is proposed to be added into Table 6.2.3.2.3.1-1 ( “URI query parameters supported by the GET method on this resource” ) of section 6.2.3.2.3.1 ( “GET” ) of 3GPP TS 29.510 V18.0.0, where the changes are highlighted with underlines.

Alternative 1:

Alternative 2:

The definition of type ListMatchingLogic is as below.

The enumeration OverrideMatchingLogic represents the wanted matching logic for the list carried in discovery query parameter, as shown below.

Enumeration OverrideMatchingLogic

The following changes are proposed to be made to Table 6.2.6.2.2-1 ( “Definition of type SearchResult” ) of section 6.2.6.2.2 ( “Type: SearchResult” ) of 3GPP TS 29.510 V18.0.0, where the changes are highlighted with underlines.

The following changes are proposed to be made to Table 6.2.6.2.7-1 ( “Definition of type NfInstanceInfo” ) of section 6.2.6.2.7 ( “Type: NfInstanceInfo” ) of 3GPP TS 29.510 V18.0.0, where the changes are highlighted with underlines.

The following section is proposed to be added into 3GPP TS 29.510 V18.0.0, where the changes are highlighted with underlines.

6.2.6.2. x Type: PartialQueryParameter

Table 6.2.6.2. x-1: Definition of type PartialQueryParameter

The following changes are proposed to be made to section 6.2.6.1 of 3GPP TS 29.510 V18.0.0, where the changes are highlighted with underlines.

6.2.6.1 General

This clause specifies the application data model supported by the API.

Table 6.2.6.1-1 specifies the data types defined for the Nnrf service based interface protocol.

Table 6.2.6.1-1: Nnrf_NFDiscovery specific Data Types

The following changes are proposed to be made to section 6.2.9 of 3GPP TS 29.510 V18.0.0, where the changes are highlighted with underlines.

6.2.9 Features supported by the NFDiscovery service

The syntax of the supportedFeatures attribute is defined in clause 5.2.2 of 3GPP TS 29.571 [7] .

The following features are defined for the Nnrf_NFDiscovery service.

Table 6.2.9-1: Features of supportedFeatures attribute used by Nnrf_NFDiscovery service

FIG. 20 is a block diagram showing an apparatus suitable for use in practicing some embodiments of the disclosure. For example, any one of the service producer and the service consumer described above may be implemented through the apparatus 2000. As shown, the apparatus 2000 may include a processor 2010, a memory 2020 that stores a program, and optionally a communication interface 2030 for communicating data with other external devices through wired and/or wireless communication.

The program includes program instructions that, when executed by the processor 2010, enable the apparatus 2000 to operate in accordance with the embodiments of the present disclosure, as discussed above. That is, the embodiments of the present disclosure may be implemented at least in part by computer software executable by the processor 2010, or by hardware, or by a combination of software and hardware.

The memory 2020 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memories, magnetic memory devices and systems, optical memory devices and systems, fixed memories and removable memories. The processor 2010 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multi-core processor architectures, as non-limiting examples.

FIG. 21 is a block diagram showing a service producer according to an embodiment of the disclosure. As shown, the service producer 2100 comprises a reception module 2102, a determination module 2104 and a sending module 2106 (optionally) . The reception module 2102 may be configured to receive, from a service consumer, a query request for discovering at least one NF instance that matches a predetermined condition comprising a list of query parameters of a predetermined parameter type, as described above with respect to block 2102. The request may indicate the service producer to return an NF instance aggregation comprising multiple NF instances. Each of the multiple NF instances may match a subset of the list of query parameters and the multiple NF instances together may match the list of query parameters. The determination module 2104 may be configured to determine a query response to the query request, based on the query request, as described above with respect to block 2104. The sending module 2106 may be configured to send the query response to the service consumer, as described above with respect to block 2106.

FIG. 22 is a block diagram showing a service consumer according to an embodiment of the disclosure. As shown, the service consumer 2200 comprises a sending module 2202 and a reception module 2204. The sending module 2202 may be configured to send, to a service producer, a query request for discovering at least one NF instance that matches a predetermined condition comprising a list of query parameters of a predetermined parameter type, as described above with respect to block 2202. The request may indicate the service producer to return an NF instance aggregation comprising multiple NF instances. Each of the multiple NF instances may match a subset of the list of query parameters and the multiple NF instances together may match the list of query parameters. The reception module 2204 may be configured to receive, from the service producer, a query response to the query request, as described above with respect to block 2204. The modules described above may be implemented by hardware, or software, or a combination of both.

FIG. 23 shows an example of a communication system 2800 in accordance with some embodiments.

In the example, the communication system 2800 includes a telecommunication network 2802 that includes an access network 2804, such as a radio access network (RAN) , and a core network 2806, which includes one or more core network nodes 2808. The access network 2804 includes one or more access network nodes, such as network nodes 2810a and 2810b (one or more of which may be generally referred to as network nodes 2810) , or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 2810 facilitate direct or indirect connection of user equipment (UE) , such as by connecting UEs 2812a, 2812b, 2812c, and 2812d (one or more of which may be generally referred to as UEs 2812) to the core network 2806 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 2800 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 2800 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

The UEs 2812 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 2810 and other communication devices. Similarly, the network nodes 2810 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 2812 and/or with other network nodes or equipment in the telecommunication network 2802 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 2802.

In the depicted example, the core network 2806 connects the network nodes 2810 to one or more hosts, such as host 2816. 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 2806 includes one more core network nodes (e.g., core network node 2808) 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 2808. 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) , Security Edge Protection Proxy (SEPP) , Network Exposure Function (NEF) , and/or a User Plane Function (UPF) .

The host 2816 may be under the ownership or control of a service provider other than an operator or provider of the access network 2804 and/or the telecommunication network 2802, and may be operated by the service provider or on behalf of the service provider. The host 2816 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 2800 of FIG. 23 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 2802 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 2802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 2802. For example, the telecommunications network 2802 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) /Massive IoT services to yet further UEs.

In some examples, the UEs 2812 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 2804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 2804. 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 as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio –Dual Connectivity (EN-DC) .

In the example, the hub 2814 communicates with the access network 2804 to facilitate indirect communication between one or more UEs (e.g., UE 2812c and/or 2812d) and network nodes (e.g., network node 2810b) . In some examples, the hub 2814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 2814 may be a broadband router enabling access to the core network 2806 for the UEs. As another example, the hub 2814 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 2810, or by executable code, script, process, or other instructions in the hub 2814. As another example, the hub 2814 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 2814 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 2814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 2814 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 2814 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.

The hub 2814 may have a constant/persistent or intermittent connection to the network node 2810b. The hub 2814 may also allow for a different communication scheme and/or schedule between the hub 2814 and UEs (e.g., UE 2812c and/or 2812d) , and between the hub 2814 and the core network 2806. In other examples, the hub 2814 is connected to the core network 2806 and/or one or more UEs via a wired connection. Moreover, the hub 2814 may be configured to connect to an M2M service provider over the access network 2804 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 2810 while still connected via the hub 2814 via a wired or wireless connection. In some embodiments, the hub 2814 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 2810b. In other embodiments, the hub 2814 may be a non-dedicated hub –that is, a device which is capable of operating to route communications between the UEs and network node 2810b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

FIG. 24 shows a UE 2900 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.

AUE 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 2900 includes processing circuitry 2902 that is operatively coupled via a bus 2904 to an input/output interface 2906, a power source 2908, a memory 2910, a communication interface 2912, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIG. 24. 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 2902 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 2910. The processing circuitry 2902 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 2902 may include multiple central processing units (CPUs) .

In the example, the input/output interface 2906 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 2900. 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 2908 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 2908 may further include power circuitry for delivering power from the power source 2908 itself, and/or an external power source, to the various parts of the UE 2900 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 2908. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 2908 to make the power suitable for the respective components of the UE 2900 to which power is supplied.

The memory 2910 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 2910 includes one or more application programs 2914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 2916. The memory 2910 may store, for use by the UE 2900, any of a variety of various operating systems or combinations of operating systems.

The memory 2910 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 2910 may allow the UE 2900 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 2910, which may be or comprise a device-readable storage medium.

The processing circuitry 2902 may be configured to communicate with an access network or other network using the communication interface 2912. The communication interface 2912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 2922. The communication interface 2912 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 2918 and/or a receiver 2920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth) . Moreover, the transmitter 2918 and receiver 2920 may be coupled to one or more antennas (e.g., antenna 2922) and may share circuit components, software or firmware, or alternatively be implemented separately.

In the illustrated embodiment, communication functions of the communication interface 2912 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 2912, 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.

AUE, when in the form of an Internet of Things (IoT) 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 IoT 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 IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 2900 shown in FIG. 24.

As yet another specific example, in an IoT 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.

FIG. 25 shows a network node 3000 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 MSR BSs, 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 3000 includes a processing circuitry 3002, a memory 3004, a communication interface 3006, and a power source 3008. The network node 3000 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 3000 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 3000 may be configured to support multiple radio access technologies (RATs) . In such embodiments, some components may be duplicated (e.g., separate memory 3004 for different RATs) and some components may be reused (e.g., a same antenna 3010 may be shared by different RATs) . The network node 3000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 3000, 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 3000.

The processing circuitry 3002 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 3000 components, such as the memory 3004, to provide network node 3000 functionality.

In some embodiments, the processing circuitry 3002 includes a system on a chip (SOC) . In some embodiments, the processing circuitry 3002 includes one or more of radio frequency (RF) transceiver circuitry 3012 and baseband processing circuitry 3014. In some embodiments, the radio frequency (RF) transceiver circuitry 3012 and the baseband processing circuitry 3014 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 3012 and baseband processing circuitry 3014 may be on the same chip or set of chips, boards, or units.

The memory 3004 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 3002. The memory 3004 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 3002 and utilized by the network node 3000. The memory 3004 may be used to store any calculations made by the processing circuitry 3002 and/or any data received via the communication interface 3006. In some embodiments, the processing circuitry 3002 and memory 3004 is integrated.

The communication interface 3006 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 3006 comprises port (s) /terminal (s) 3016 to send and receive data, for example to and from a network over a wired connection. The communication interface 3006 also includes radio front-end circuitry 3018 that may be coupled to, or in certain embodiments a part of, the antenna 3010. Radio front-end circuitry 3018 comprises filters 3020 and amplifiers 3022. The radio front-end circuitry 3018 may be connected to an antenna 3010 and processing circuitry 3002. The radio front-end circuitry may be configured to condition signals communicated between antenna 3010 and processing circuitry 3002. The radio front-end circuitry 3018 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 3018 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 3020 and/or amplifiers 3022. The radio signal may then be transmitted via the antenna 3010. Similarly, when receiving data, the antenna 3010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 3018. The digital data may be passed to the processing circuitry 3002. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, the network node 3000 does not include separate radio front-end circuitry 3018, instead, the processing circuitry 3002 includes radio front-end circuitry and is connected to the antenna 3010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 3012 is part of the communication interface 3006. In still other embodiments, the communication interface 3006 includes one or more ports or terminals 3016, the radio front-end circuitry 3018, and the RF transceiver circuitry 3012, as part of a radio unit (not shown) , and the communication interface 3006 communicates with the baseband processing circuitry 3014, which is part of a digital unit (not shown) .

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

The antenna 3010, communication interface 3006, and/or the processing circuitry 3002 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 3010, the communication interface 3006, and/or the processing circuitry 3002 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 3008 provides power to the various components of network node 3000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component) . The power source 3008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 3000 with power for performing the functionality described herein. For example, the network node 3000 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 3008. As a further example, the power source 3008 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 3000 may include additional components beyond those shown in FIG. 25 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 3000 may include user interface equipment to allow input of information into the network node 3000 and to allow output of information from the network node 3000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 3000.

FIG. 26 is a block diagram of a host 3100, which may be an embodiment of the host 2816 of FIG. 23, in accordance with various aspects described herein. As used herein, the host 3100 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 3100 may provide one or more services to one or more UEs.

The host 3100 includes processing circuitry 3102 that is operatively coupled via a bus 3104 to an input/output interface 3106, a network interface 3108, a power source 3110, and a memory 3112. 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 FIGs. 24 and 25, such that the descriptions thereof are generally applicable to the corresponding components of host 3100.

The memory 3112 may include one or more computer programs including one or more host application programs 3114 and data 3116, which may include user data, e.g., data generated by a UE for the host 3100 or data generated by the host 3100 for a UE. Embodiments of the host 3100 may utilize only a subset or all of the components shown. The host application programs 3114 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 3114 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 3100 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 3114 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.

FIG. 27 is a block diagram illustrating a virtualization environment 3200 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 3200 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 3202 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc. ) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

Hardware 3204 includes processing circuitry, memory that stores software and/or instructions 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 3206 (also referred to as hypervisors or virtual machine monitors (VMMs) ) , provide VMs 3208a and 3208b (one or more of which may be generally referred to as VMs 3208) , and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 3206 may present a virtual operating platform that appears like networking hardware to the VMs 3208.

The VMs 3208 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 3206. Different embodiments of the instance of a virtual appliance 3202 may be implemented on one or more of VMs 3208, 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 3208 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 3208, and that part of hardware 3204 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 3208 on top of the hardware 3204 and corresponds to the application 3202.

Hardware 3204 may be implemented in a standalone network node with generic or specific components. Hardware 3204 may implement some functions via virtualization. Alternatively, hardware 3204 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 3210, which, among others, oversees lifecycle management of applications 3202. In some embodiments, hardware 3204 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 3212 which may alternatively be used for communication between hardware nodes and radio units.

FIG. 28 shows a communication diagram of a host 3302 communicating via a network node 3304 with a UE 3306 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 2812a of FIG. 23 and/or UE 2900 of FIG. 24) , network node (such as network node 2810a of FIG. 23 and/or network node 3000 of FIG. 25) , and host (such as host 2816 of FIG. 23 and/or host 3100 of FIG. 26) discussed in the preceding paragraphs will now be described with reference to FIG. 28.

Like host 3100, embodiments of host 3302 include hardware, such as a communication interface, processing circuitry, and memory. The host 3302 also includes software, which is stored in or accessible by the host 3302 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 3306 connecting via an over-the-top (OTT) connection 3350 extending between the UE 3306 and host 3302. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 3350.

The network node 3304 includes hardware enabling it to communicate with the host 3302 and UE 3306. The connection 3360 may be direct or pass through a core network (like core network 2806 of FIG. 23) 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 3306 includes hardware and software, which is stored in or accessible by UE 3306 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 3306 with the support of the host 3302. In the host 3302, an executing host application may communicate with the executing client application via the OTT connection 3350 terminating at the UE 3306 and host 3302. 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 3350 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 3350.

The OTT connection 3350 may extend via a connection 3360 between the host 3302 and the network node 3304 and via a wireless connection 3370 between the network node 3304 and the UE 3306 to provide the connection between the host 3302 and the UE 3306. The connection 3360 and wireless connection 3370, over which the OTT connection 3350 may be provided, have been drawn abstractly to illustrate the communication between the host 3302 and the UE 3306 via the network node 3304, 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 3350, in step 3308, the host 3302 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 3306. In other embodiments, the user data is associated with a UE 3306 that shares data with the host 3302 without explicit human interaction. In step 3310, the host 3302 initiates a transmission carrying the user data towards the UE 3306. The host 3302 may initiate the transmission responsive to a request transmitted by the UE 3306. The request may be caused by human interaction with the UE 3306 or by operation of the client application executing on the UE 3306. The transmission may pass via the network node 3304, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 3312, the network node 3304 transmits to the UE 3306 the user data that was carried in the transmission that the host 3302 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 3314, the UE 3306 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 3306 associated with the host application executed by the host 3302.

In some examples, the UE 3306 executes a client application which provides user data to the host 3302. The user data may be provided in reaction or response to the data received from the host 3302. Accordingly, in step 3316, the UE 3306 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 3306. Regardless of the specific manner in which the user data was provided, the UE 3306 initiates, in step 3318, transmission of the user data towards the host 3302 via the network node 3304. In step 3320, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 3304 receives user data from the UE 3306 and initiates transmission of the received user data towards the host 3302. In step 3322, the host 3302 receives the user data carried in the transmission initiated by the UE 3306.

One or more of the various embodiments improve the performance of OTT services provided to the UE 3306 using the OTT connection 3350, in which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may improve the discovery efficiency of NF and thereby provide benefits such as more valid throughput.

In an example scenario, factory status information may be collected and analyzed by the host 3302. As another example, the host 3302 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 3302 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights) . As another example, the host 3302 may store surveillance video uploaded by a UE. As another example, the host 3302 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 3302 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 3350 between the host 3302 and UE 3306, 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 3302 and/or UE 3306. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 3350 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 3350 may include message format, retransmission settings, preferred routing etc. ; the reconfiguring need not directly alter the operation of the network node 3304. 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 3302. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 3350 while monitoring propagation times, errors, etc.

Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

In general, the various exemplary embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto. While various aspects of the exemplary embodiments of this disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

As such, it should be appreciated that at least some aspects of the exemplary embodiments of the disclosure may be practiced in various components such as integrated circuit chips and modules. It should thus be appreciated that the exemplary embodiments of this disclosure may be realized in an apparatus that is embodied as an integrated circuit, where the integrated circuit may comprise circuitry (as well as possibly firmware) for embodying at least one or more of a data processor, a digital signal processor, baseband circuitry and radio frequency circuitry that are configurable so as to operate in accordance with the exemplary embodiments of this disclosure.

It should be appreciated that at least some aspects of the exemplary embodiments of the disclosure may be embodied in computer-executable instructions, such as in one or more program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types when executed by a processor in a computer or other device. The computer executable instructions may be stored on a computer readable medium such as a hard disk, optical disk, removable storage media, solid state memory, RAM, etc. As will be appreciated by one skilled in the art, the function of the program modules may be combined or distributed as desired in various embodiments. In addition, the function may be embodied in whole or in part in firmware or hardware equivalents such as integrated circuits, field programmable gate arrays (FPGA) , and the like.

References in the present disclosure to “one embodiment” , “an embodiment” and so on, indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

It should be understood that, although the terms “first” , “second” and so on may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of the disclosure. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed terms.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the present disclosure. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and/or “including” , when used herein, specify the presence of stated features, elements, and/or components, but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof. The terms “connect” , “connects” , “connecting” and/or “connected” used herein cover the direct and/or indirect connection between two elements. It should be noted that two blocks shown in succession in the above figures may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.

The present disclosure includes any novel feature or combination of features disclosed herein either explicitly or any generalization thereof. Various modifications and adaptations to the foregoing exemplary embodiments of this disclosure may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings. However, any and all modifications will still fall within the scope of the non-Limiting and exemplary embodiments of this disclosure.

Embodiment 1. A method performed by a service producer, comprising:

receiving, from a service consumer, a query request for discovering at least one NF instance that matches a predetermined condition comprising a list of query parameters of a predetermined parameter type, wherein the request indicates the service producer to return an NF instance aggregation comprising multiple NF instances, each of the multiple NF instances matches a subset of the list of query parameters and the multiple NF instances together match the list of query parameters;

determining a query response to the query request, based on the query request; and

sending the query response to the service consumer.

Embodiment 2. The method according to embodiment 1, wherein the query response indicates one or more NF instance aggregations each of which matches the list of query parameters.

Embodiment 3. The method according to embodiment 1 or 2, wherein the query request comprises a first indicator that indicates the list of query parameters and indicates the service producer to return an NF instance aggregation.

Embodiment 4. The method according to embodiment 3, wherein the first indicator is an array or map data structure whose elements are the query parameters contained in the list, and a name of the first indicator is configured to indicate the service producer to return an NF instance aggregation.

Embodiment 5. The method according to embodiment 1 or 2, wherein the query request comprises:

a second indicator indicating the list of query parameters; and

a third indicator indicating the service producer to return an NF instance aggregation.

Embodiment 6. The method according to embodiment 5, wherein the third indicator comprises:

a first sub-indicator indicating a name of the second indicator; and

a second sub-indicator having a first value for indicating the service producer to return an NF instance aggregation, wherein the second sub-indicator can take the first value, or a second value for indicating the service producer to return one or more NF instances each of which matches the query parameters contained in the list.

Embodiment 7. The method according to embodiment 5 or 6, wherein the second indicator is an array or map data structure whose elements are the query parameters contained in the list.

Embodiment 8. The method according to any of embodiments 1 to 7, wherein determining the query response to the query request comprises:

determining a first set of NF instances each of which matches a subset of the list of query parameters; and

determining, from the first set of NF instances, a second set of NF instances so that a union set of the query parameters matched by the second set of NF instances is the list of query parameters.

Embodiment 9. The method according to any of embodiments 2 to 8, wherein the query response comprises a fourth indicator indicating, for each of the one or more NF instance aggregations, members of the NF instance aggregation and the corresponding query parameters matched by the members.

Embodiment 10. The method according to embodiment 9, wherein each of the one or more NF instance aggregations is represented by a first map data structure.

Embodiment 11. The method according to embodiment 9 or 10, wherein each member of the NF instance aggregation and the corresponding one or more query parameters matched by the member are represented by a second map data structure.

Embodiment 12. The method according to embodiment 11, wherein a key of the second map data structure is an identifier, ID, of the member of the NF instance aggregation, and the corresponding one or more query parameters matched by the member are represented by an array data structure.

Embodiment 13. The method according to any of embodiments 1 to 12, wherein the NF instance aggregation further comprises one or more NF instances each of which matches the list of query parameters.

Embodiment 14. The method according to any of embodiments 1 to 13, wherein the service consumer is one of:

a multicast/broadcast session management function, MB-SMF; and

a time sensitive communication and time synchronization function, TSCTSF.

Embodiment 15. The method according to any of embodiments 1 to 14, wherein the predetermined parameter type is one of following types:

tracking area identity, TAI;

subscription permanent identifier, SUPI;

public land mobile network, PLMN;

single network slice selection assistance information, SNSSAI;

network slice instance, NSI;

group ID;

data network access identifier, DNAI;

event ID;

network data analytics function, NWDAF event;

analytics information; and

multicast/broadcast service, MBS, session ID.

Embodiment 16. The method according to any of embodiments 1 to 15, wherein the NF instance is an access and mobility management function, AMF.

Embodiment 17. The method according to any of embodiments 1 to 16, wherein the service producer is a network repository function, NRF.

Embodiment 18. A method performed by a service consumer, comprising:

sending, to a service producer, a query request for discovering at least one NF instance that matches a predetermined condition comprising a list of query parameters of a predetermined parameter type, wherein the request indicates the service producer to return an NF instance aggregation comprising multiple NF instances, each of the multiple NF instances matches a subset of the list of query parameters and the multiple NF instances together match the list of query parameters; and

receiving, from the service producer, a query response to the query request.

Embodiment 19. The method according to embodiment 18, wherein the query response indicates one or more NF instance aggregations each of which matches the list of query parameters.

Embodiment 20. The method according to embodiment 18 or 19, wherein the query request comprises a first indicator that indicates the list of query parameters and indicates the service producer to return an NF instance aggregation.

Embodiment 21. The method according to embodiment 20, wherein the first indicator is an array or map data structure whose elements are the query parameters contained in the list, and a name of the first indicator is configured to indicate the service producer to return an NF instance aggregation.

Embodiment 22. The method according to embodiment 18 or 19, wherein the query request comprises:

a second indicator indicating the list of query parameters; and

Embodiment 23. The method according to embodiment 22, wherein the third indicator comprises:

a first sub-indicator indicating a name of the second indicator; and

Embodiment 24. The method according to embodiment 22 or 23, wherein the second indicator is an array or map data structure whose elements are the query parameters contained in the list.

Embodiment 25. The method according to any of embodiments 19 to 24, wherein the query response comprises a fourth indicator indicating, for each of the one or more NF instance aggregations, members of the NF instance aggregation and the corresponding query parameters matched by the members.

Embodiment 26. The method according to embodiment 25, wherein each of the one or more NF instance aggregations is represented by a first map data structure.

Embodiment 27. The method according to embodiment 25 or 26, wherein each member of the NF instance aggregation and the corresponding one or more query parameters matched by the member are represented by a second map data structure.

Embodiment 28. The method according to embodiment 27, wherein a key of the second map data structure is an identifier, ID, of the member of the NF instance aggregation, and the corresponding one or more query parameters matched by the member are represented by an array data structure.

Embodiment 29. The method according to any of embodiments 18 to 28, wherein the NF instance aggregation further comprises one or more NF instances each of which matches the list of query parameters.

Embodiment 30. The method according to any of embodiments 18 to 29, wherein the service consumer is one of:

a multicast/broadcast session management function, MB-SMF; and

a time sensitive communication and time synchronization function, TSCTSF.

Embodiment 31. The method according to any of embodiments 18 to 30, wherein the predetermined parameter type is one of following types:

tracking area identity, TAI;

subscription permanent identifier, SUPI;

public land mobile network, PLMN;

single network slice selection assistance information, SNSSAI;

network slice instance, NSI;

group ID;

data network access identifier, DNAI;

event ID;

network data analytics function, NWDAF event;

analytics information; and

multicast/broadcast service, MBS, session ID.

Embodiment 32. The method according to any of embodiments 18 to 31, wherein the NF instance is an access and mobility management function, AMF.

Embodiment 33. The method according to any of embodiments 18 to 32, wherein the service producer is a network repository function, NRF.

Embodiment 34. A service producer comprising:

at least one processor; and

at least one memory, the at least one memory containing instructions executable by the at least one processor, whereby the service producer is operative to:

receive, from a service consumer, a query request for discovering at least one NF instance that matches a predetermined condition comprising a list of query parameters of a predetermined parameter type, wherein the request indicates the service producer to return an NF instance aggregation comprising multiple NF instances, each of the multiple NF instances matches a subset of the list of query parameters and the multiple NF instances together match the list of query parameters;

determine a query response to the query request, based on the query request; and

send the query response to the service consumer.

Embodiment 35. The service producer according to embodiment 34, wherein the service producer is operative to perform the method according to any of embodiments 2 to 17.

Embodiment 36. A service consumer comprising:

at least one processor; and

at least one memory, the at least one memory containing instructions executable by the at least one processor, whereby the service consumer is operative to:

send, to a service producer, a query request for discovering at least one NF instance that matches a predetermined condition comprising a list of query parameters of a predetermined parameter type, wherein the request indicates the service producer to return an NF instance aggregation comprising multiple NF instances, each of the multiple NF instances matches a subset of the list of query parameters and the multiple NF instances together match the list of query parameters; and

receive, from the service producer, a query response to the query request.

Embodiment 37. The service consumer according to embodiment 36, wherein the service consumer is operative to perform the method according to any of embodiments 19 to 33.

Embodiment 38. A computer readable storage medium storing thereon instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any of embodiments 1 to 33.

Claims

A method (500) performed by a first network node for Network Function ‘NF’ discovery, comprising:

receiving (S501) , from a second network node, a first discovery request that comprises a query parameter having a plurality of values to be satisfied by NF (s) and an indication indicating a capability of receiving an aggregation of NFs of a requested target NF type and a subset of the plurality of values of the query parameter that are not satisfied by any NF of the requested target NF type that is registered in the first network node; and

determining (S503) that a subset of values from the plurality of values of the query parameter are not satisfied by any NF of the requested target NF type that is registered in the first network node.
The method according to claim 1, further comprising:

transmitting (S521) , to the second network node, a first discovery response to the first discovery request, wherein the first discovery response comprises said subset of values.
The method according to claim 2, wherein the first discovery response comprises a third list with a number of NFs of the requested target NF type whose registration information is known by the first network node and supporting the plurality of values, excluding said subset of values, of the query parameter.
The method according to claim 1, further comprising:

transmitting (S505) , to a third network node, a second discovery request that comprises the query parameter having said subset of values and the indication indicating said capability; and

receiving (S507) , from the third network node, a second discovery response to the second discovery request.
The method (500) of claim 4, wherein the second discovery response comprises:

a first list with a number of NFs of the requested target NF type that support said subset of values of the query parameter; or

second continue discovery information, each for indicating to transmit a third discovery request that comprises the query parameter having at least a part of said subset of values, so as to find a first list with a number of NFs of the requested target NF type that altogether support said subset of values of the query parameter.
The method (500) of claim 4 or 5, wherein the second discovery response further comprises a second list with a number of NFs of the requested target NF type whose registration information is known by the third network node and supporting at least a part of said subset of values of the query parameter, in addition to the second continue discovery information.
The method (500) of any of claims 5-6, wherein the second continue discovery information comprises at least one of:

an indication for indicating to transmit the third discovery request that comprises the query parameter having at least the part of said subset of values,

a list of at least the part of said subset of values of the query parameter,

a Network Repository Function ‘NRF’ discovery Uniform Resource Identifier ‘URI’ to which the second network node can transmit the third discovery request, so as to find the second list of NFs of the requested target NF type supporting at least the part of said subset of values of the query parameter.
The method (500) of any of claims 4-7, wherein the second discovery request is forwarded by the first network node from the second network node, and the method (500) further comprises:

after determining that said subset of values of the query parameter are not satisfied by any NF of the requested target NF type that is registered in the first network node, transmitting, to the second network node, a first discovery response to the first discovery request, wherein the first discovery response comprises first continue discovery information for indicating the second network node to transmit the second discovery request that comprises the query parameter having said subset of values; and

receiving the second discovery request from the second network node.
The method (500) of claim 8, wherein the first discovery response further comprises a third list with a number of NFs of the requested target NF type whose registration information is known by the first network node and supporting the plurality of values, excluding said subset of values, of the query parameter.
The method (500) of any of claims 8-9, wherein the first continue discovery information comprises at least one of:

an indication for indicating the second network node to transmit the second discovery request that comprises the query parameter having said subset of values,

a list of said subset of values of the query parameter,

an NRF discovery URI to which the second network node can transmit the second discovery request, so as to find the first list of NFs of the requested target NF type supporting said subset of values of the query parameter.
The method (500) of any of claims 4-10, further comprising:

generating a third list with a number of NFs of the requested target NF type that are registered in the first network node and support the plurality of values, excluding said subset of values, of the query parameter;

storing the third list of NFs; and

being triggered to generate the second discovery request that comprises the query parameter having said subset of values.
The method (500) of claim 11, further comprising:

transmitting, to at least one fourth network node respectively, at least one third discovery request according to the received second continue discovery information, each of the at least one third discovery request comprising the query parameter having the respective part of said subset of values; and

receiving, from the at least one fourth network node, a first list with a number of NFs that altogether support said subset of values of the query parameter in at least one third discovery response to the at least one third discovery request as a search result.
The method (500) of claim 12, further comprising:

combining the first list of NFs and the third list of NFs; and

transmitting the combined list of NFs to the second network node in the first discovery response.
The method (500) of claim 12, further comprising:

transmitting, to the second network node, a first discovery response that comprises a search ID identifying a search result for the first discovery request, and a timer indicating the second network node to retrieve the search result after the timer is expired.
The method (500) of claim 14, further comprising:

combining the first list of NFs and the third list of NFs;

receiving, from the second network node, a fourth discovery request that comprises the search ID for retrieving the combined list of NFs, after the timer is expired; and

transmitting the combined list of NFs to the second network node in the fourth discovery response.
The method (500) of any of claims 1-15, wherein

the first, third and fourth network nodes respectively host NRF, and

the second network node implements NF service consumer of an NRF discovery service.
The method (500) of claim 16, wherein

the NF service consumer comprises at least one of: Multicast/Broadcast-Section Management Function ‘MB-SMF’ , or Time Sensitive Communication and Time Synchronization Function ‘TSCTSF’ ,

the NF of the requested target NF type comprises Access and Mobility Management Function ‘AMF’ , and

the query parameter comprises a Tracking Area ‘TA’ List.
A method (600) performed by a second network node for Network Function ‘NF’ discovery, comprising:

transmitting (S601) , to a first network node, a first discovery request that comprises a query parameter having a plurality of values to be satisfied by NF (s) and a subset of the plurality of values of the query parameter that are not satisfied by any NF of the requested target NF type that is registered in the first network node; and

receiving (S603) , from the first network node, a first discovery response to the first discovery request, wherein the first discovery response comprises the subset of the plurality of values of the query parameter that are not satisfied by any NF of the requested target NF type that is registered in the first network node.
The method (600) of claim 18, wherein the first discovery response further comprises a third list with a number of NFs of the requested target NF type whose registration information is known by the first network node and supporting the plurality of values, excluding said subset of values, of the query parameter.
The method according to claim 18 or 19, wherein the first discovery response comprises first continue discovery information for indicating the second network node to transmit a second discovery request that comprises the query parameter having a subset of values from the plurality of values of the query parameter not satisfied by any NF of the requested target NF type that is registered in the first network node.
The method according to claim 20, further comprising:

transmitting (S605) the second discovery request to the first network node according to the first continue discovery information.
The method (600) of any of claims 20-21, wherein the first continue discovery information comprises at least one of:

an indication for indicating the second network node to transmit the second discovery request that comprises the query parameter having said subset of values,

a list of said subset of values of the query parameter,

a Network Repository Function ‘NRF’ discovery Uniform Resource Identifier ‘URI’ to which the second network node can transmit the second discovery request, so as to find a first list with a number of NFs of the requested target NF type supporting said subset of values of the query parameter.
The method (600) of any of claims 20-22, further comprising:

receiving, from the first network node, a second discovery response that comprises a first list with a number of NFs of the requested target NF type that support said subset of values of the query parameter or second continue discovery information, wherein each of the second continue discovery information indicates the second network node to transmit a third discovery request that comprises the query parameter having a respective part of said subset of values, so as to find the first list of NFs supporting said subset of values of the query parameter.
The method (600) of claim 23, wherein the second discovery response further comprises a second list with a number of NFs of the requested target NF type whose registration information is known by a second NRF and supporting at least a part of said subset of values of the query parameter, in addition to the second continue discovery information.
The method (600) of claim 23 or 24, wherein the second continue discovery information comprises at least one of:

an indication for indicating to transmit the third discovery request that comprises the query parameter having at least the part of said subset of values,

a list of at least the part of said subset of values of the query parameter,

an NRF discovery URI to which the second network node can transmit the third discovery request, so as to find a second list with a number of NFs of the requested target NF type supporting at least the part of said subset of values of the query parameter.
The method (600) of any of claims 24-25, further comprising:

transmitting, to a fourth network node, at least one of third discovery request according to the received second continue discovery information, each of the at least one third discovery request comprising the query parameter having the respective part of said subset of values; and

receiving, from the at least one fourth network node, the first list of NFs that altogether support said subset of values of the query parameter in at least one third discovery response to the at least one third discovery request.
The method (600) of any of claims 18-26, wherein

the first, third and fourth network nodes respectively host NRF, and

the second network node implements NF service consumer of an NRF discovery service.
The method (600) of claim 27, wherein

the NF service consumer comprises at least one of: Multicast/Broadcast-Section Management Function ‘MB-SMF’ , or Time Sensitive Communication and Time Synchronization Function ‘TSCTSF’ ,

the NF of the requested target NF type comprises Access and Mobility Management Function ‘AMF’ , and

the query parameter comprises a Tracking Area ‘TA’ List.
A first network node (1100) , comprising:

at least one processor (1101) , and

at least one memory (1103) , storing instructions which, when executed on the at least one processor (1101) , cause the first network node (1100) to:

receive, from a second network node, a first discovery request that comprises a query parameter having a plurality of values to be satisfied by NF (s) and an indication indicating a capability of receiving a list with an aggregation NFs of a requested target NF type and a subset of the plurality of values of the query parameter that are not satisfied by any NF of the requested target NF type that is registered in the first network node; and

determine that a subset of values from the plurality of values of the query parameter are not satisfied by any NF of the requested target NF type that is registered in the first network node.
The first network node (1100) of claim 29, wherein the instructions, when executed on the at least one processor (1101) , further cause the first network node (1100) to perform the method according to any of claims 2 to 17.
A second network node (1300) , comprising:

at least one processor (1301) , and

at least one memory (1303) , storing instructions which, when executed on the at least one processor (1301) , cause the second network node (1300) to:

transmit, to a first network node, a first discovery request that comprises a query parameter having a plurality of values to be satisfied by NF (s) and an indication indicating a capability of receiving an aggregation of NFs of a requested target NF type and a subset of the plurality of values of the query parameter that are not satisfied by any NF of the requested target NF type that is registered in the first network node; and

receive, from the first network node, a first discovery response to the first discovery request, wherein the first discovery response comprises the subset of the plurality of values of the query parameter that are not satisfied by any NF of the requested target NF type that is registered in the first network node.
The second network node (1300) of claim 31, wherein the instructions, when executed on the at least one processor (1301) , further cause the second network node (1300) to perform the method according to any of claims 19-28.
A computer readable storage medium having computer program instructions stored thereon, the computer program instructions, when executed by at least one processor, causing the at least one processor to perform the method according to any of claims 1 to 28.