Feature negotiation method and apparatus for network function discovery
The method updates discovery parameters to align capabilities across network nodes, addressing unclear feature negotiation in network function discovery, ensuring accurate and compatible results.
Patent Information
- Application Number
- PCT/CN2026/095325
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
In network function discovery across multiple Public Land Mobile Networks (PLMNs), the feature negotiation information is unclear regarding the capabilities of the original network node and intermediate nodes, leading to incorrect discovery results and failed procedures due to overestimation of capabilities.
A method and apparatus for feature negotiation that updates discovery parameters based on the capabilities of both the original network node and intermediate nodes, ensuring accurate negotiation and proper discovery results.
Ensures accurate feature negotiation and discovery results by aligning the capabilities of all involved nodes, preventing failures and ensuring compatibility with supported features.
Smart Images

Figure CN2026095325_12112026_PF_FP_ABST
Abstract
Description
FEATURE NEGOTIATION METHOD AND APPARATUS FOR NETWORK FUNCTION DISCOVERYTechnical Field
[0001] The embodiments herein relate generally to the field of communication, and more particularly, the embodiments herein relate to feature negotiation method and apparatus for network function discovery.Background
[0002] 3rd Generation Partnership Project (3GPP) defines functionality for Network Function (NF) and NF service discovery and selection for 5th Generation Mobile Communication Technology (5G) , referring to 3GPP TS 23.501 V19.3.0.
[0003] The NF discovery and / or NF service discovery enable Core Network (CN) entities (NFs or Service Communication Proxy (SCP) ) to discover a set of NF instance (s) and / or NF service instance (s) for a specific NF service or an NF type. NF service discovery is enabled via the NF discovery procedure that is implemented via the Network Repository Function (NRF) . NRF is the logical function that is used to support the functionality of NF and NF service discovery and status notification.
[0004] In order for the requested NF type or NF service (NF service provider) to be discovered via the NRF, the NF instance needs to be registered in the NRF. This is done by sending a Nnrf_NFManagement_NFRegister containing the NF profile. The NF profile contains information related to the NF instance, such as NF instance Identifier (ID) , supported NF service instances. The registration service enables NF service provider to register its NF profile and make it available to be discovered by other NF (s) . see the example NFprofile in clause 6.2.6.2 of 3GPP TS 23.501 V19.3.0.
[0005] In order for the requester NF or SCP to obtain information about the NF and / or NF service (s) registered, the requester NF or SCP may initiate a discovery procedure with the NRF by providing the type of the NF and optionally a list of the specific service (s) it is attempting to discover. The requester NF or SCP may also provide other service parameters e.g. slicing related information, location information. Such input parameters included in the discovery request then enable NRF to find and match a target NF that registered in NRF which best serves the requesting NF.
[0006] The requester NF may also provide NF Set related information to enable reselection of NF instances within the NF set.
[0007] For NF and NF service discovery across PLMNs, the NRF in the local Public Land Mobile Network (PLMN) interacts with the NRF in the remote PLMN to retrieve the NF profile (s) of the NF instance (s) in the remote PLMN that matches the discovery criteria. The remote PLMN NRF may further interact with a target PLMN NRF.Feature Negotiation
[0008] In different releases or revisions of 3GPP service Application Programming Interfaces (APIs) , there could be many resources or features introduced. Thus, 3GPP defines feature negotiation method to support the negotiation of the applicable features among NF peers.
[0009] For each service API, the NF (e.g. Hypertext Transfer Protocol (HTTP) client and HTTP server) can exchange its own supported feature to the peer NF over the interface towards its peer.
[0010] Figure 1 is a schematic signaling chart showing the messages in an example feature negotiation procedure for NF discovery.
[0011] As shown in Figure 1, in the discovery request (that may be a discovery service request e.g. Nnrf_NFDiscovery_Request or NF status subscription request / notify e.g. Nnrf_NFManagement_NFStatusSubscribe / Nnrf_NFManagement_NFStatusNotify) , the NF consumer (NFc) indicates feature negotiation information (i.e. its own capability of supported features) as part of discovery parameters. NRF 131 checks the received supported-features of NFc included in the discovery parameters and determines whether or not certain features should be applied to the discovery result, then generates and sends back the discovery result accordingly. In the discovery response, NRF 131 can then also indicate its own capability of supported features.Delegated discovery
[0012] 3GPP supports a procedure for delegated NF discovery for indirect communication, i.e. when the SCP 211 is used in the communication path between NFc 121 and NFp 141 or NFc 121 and NRF 131. See more detail in 3GPP TS 23.502 V19.3.0.
[0013] If the requester NF 121 is configured to delegate discovery, the requester NF 121 may omit the discovery procedure with the NRF 131 and instead delegate the discovery to the SCP 211; the SCP 211 will then act on behalf of the requester NF 121. In this case, the requester NF 121 adds any necessary discovery and selection parameters to the request in order for the SCP 211 to be able to do discovery and associated selection. The SCP 211 may interact with the NRF 131 to perform discovery and obtain discovery result. The SCP 211 then selects a suitable NF instance and / or NF service instance based on discovery and selection parameters provided by the requester NF 121 and interaction with the NRF 131.
[0014] Figure 2 is a schematic signaling chart showing the messages in an example delegated NF discovery procedure, which shows delegated NF service discovery when NF service consumer 121 and NF service producer 141 are in different PLMNs. As shown in Figure 2, the delegated discovery is in two PLMNs, i.e., the PLMN-1 as serving network and the PLMN-2 as home network. The delegated discovery could be performed in the same PLMN as well, i.e. PLMN1=PLMN2, and there is no extra interaction between the two NRFs 212, 131.
[0015] Instead of NFc 121 invoking discovery request towards NRF 131 directly, NFc 121 invokes service quest towards SCP 211 and include the discovery parameters in the request. SCP 211 then performs the discovery of target NF (NFp) 141 based on the received the discovery parameters towards NRF 131 on behave of NFc 121.
[0016] [Rectified under Rule 91, 22.06.2026]The signaling chart in Figure 2 may include the following messages or steps:
[0017] Step 1. The NF service consumer 121 intends to communicate with an NF service producer 141. The NF service consumer 121 sends the request to an SCP 211. The request includes at least the source PLMN ID and the target PLMN ID in the discovery and selection parameters necessary for the SCP 211 to discover and select a NF service producer instance 141. The discovery and selection parameters are included in the request by the NF service consumer 121 in a way that the SCP 211 does not need to parse the request body.
[0018] Step 2. The SCP 211 recognizes that the request is for a NF service producer 141 in another PLMN. SCP 211 interacts with NRF 212 using the Nnrf_NFDiscovery service.
[0019] Step 3. NRF 212 in PLMN-1 and NRF 131 in PLMN 2 interact using the Nnrf_NFDiscovery service. See step 2 in clause 4.17.5 of 3GPP TS 23.502 V19.3.0.
[0020] Step 4. SCP 211 gets Nnrf_NFDiscovery service response with NF profile (s) .
[0021] Step 5. SCP 211 selects a NF service producer instance 141 in PLMN-2.
[0022] Step 6. SCP 211 forwards the request to the selected NF service producer instance in PLMN-2.Summary
[0023] For the feature negotiation with the scenario of Figure 2, which includes one or more intermediate network nodes (for example, SCP 211 due to the delegated discovery; and / or NRF 212 due to multiple PLMNs) , the feature negotiation is done hop-by-hop. As a result, when the NRF 131 receive feature negotiation information, it is unclear whether the feature negotiation information included in the NF discovery procedure is associated with the original NF triggering the discovery procedure (such as NFc 121) or with the intermediate NFs that sends / forwards the discovery message (such as SCP 211 or NRF 212) , thus it may not obtain the real capability of NFc 121 and / or intermediate node (s) . For example, the NRF 131 may overestimates the capability of the NF service consumer 121 and / or intermediate node (s) (such as SCP 211 or NRF 212) , which results that the discovery result cannot be recognized by the discovery requester 121 and / or intermediate node (s) (such as SCP 211 or NRF 212) when it receives the discovery result contains features it does not support.
[0024] In view of the above, the embodiments herein propose feature negotiation method and apparatus for network function discovery.
[0025] In some embodiments, there proposes a method performed by a first network node, comprising: receiving a first message comprising one or more first discovery parameters from a second network node; transmitting a second message comprising one or more second discovery parameters to a third network node; and receiving a third message comprising a discovery result from the third network node. At least one of the one or more first discovery parameters and the one or more second discovery parameters may impact the returned discovery result by the third network node for a discovered NF. The one or more second discovery parameters may be at least in part updated based on the one or more first discovery parameters.
[0026] In some embodiments, there proposes a method performed by a third network node, comprising: receiving a second message comprising one or more second discovery parameters from a first network node, the one or more second discovery parameters are at least in part updated based on one or more first discovery parameters from a second network node; and transmitting a third message comprising a discovery result to the first network node. At least one of the one or more first discovery parameters and the one or more second discovery parameters may impact the returned discovery result by the third network node for a discovered NF.
[0027] In some embodiments, there proposes a network node in a communication network. The network node may comprise processing circuitry and a memory. The processing circuitry may be configured to perform the above methods. The network node may be configured as any one of the above first, second, or third network node.
[0028] In some embodiments, there proposes a communication system. The communication system may comprise the first, second, and third network nodes.
[0029] In some embodiments, there proposes a computer readable medium comprising instructions that, when executed by a network node, cause the network node to perform the above methods.
[0030] In some embodiments, there proposes a computer readable product comprising instructions that, when executed by a network node, cause the network node to perform the above methods.
[0031] With the embodiments, the one or more second discovery parameters may be at least in part updated based on the one or more first discovery parameters, which ensures feature negotiation working for a forwarded or delegated discovery request.Brief Description of the Drawings
[0032] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate various embodiments of the present disclosure and, together with the description, further serve to explain the principles of the disclosure and to enable a person skilled in the pertinent art to make and use the embodiments disclosed herein. In the drawings, like reference numbers indicate identical or functionally similar elements, and in which:
[0033] Figure 1 is a schematic signaling chart showing the messages in an example feature negotiation procedure for NF discovery;
[0034] Figure 2 is a schematic signaling chart showing the messages in an example delegated NF discovery procedure;
[0035] Figure 3 is a schematic signaling chart showing the messages in an example feature negotiation procedure for delegated NF discovery, according to the embodiments herein;
[0036] Figure 4 is a schematic signaling chart showing the messages in another example feature negotiation procedure for delegated NF discovery, according to the embodiments herein;
[0037] Figure 5 is a schematic flow chart showing an example method in the first network node, according to the embodiments herein;
[0038] Figure 6 is a schematic flow chart showing an example method in the third network node, according to the embodiments herein;
[0039] Figure 7 is a schematic block diagram showing an example first network node, according to the embodiments herein;
[0040] Figure 8 is a schematic block diagram showing an example third network node, according to the embodiments herein;
[0041] Figure 9 is a schematic block diagram showing an example computer-implemented apparatus, according to the embodiments herein; and
[0042] Figure 10 is a schematic block diagram showing an example communication system, according to the embodiments herein.Detailed Description of Embodiments
[0043] The embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed only for the purpose of enabling those skilled persons in the art to better understand and thus implement the present disclosure, rather than suggesting any limitations on the scope of the present disclosure. Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present disclosure should be or are in any single embodiment of the disclosure. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present disclosure. Furthermore, the described features, advantages, and characteristics of the disclosure may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that the disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the disclosure.
[0044] As used herein, the term “network” (or called as “system” , “communication system” or “communication network” ) refers to a network or system following any suitable communication standards such as new radio (NR) , long term evolution (LTE) , LTE-Advanced, wideband code division multiple access (WCDMA) , high-speed packet access (HSPA) , Code Division Multiple Access (CDMA) , Time Division Multiple Address (TDMA) , Frequency Division Multiple Access (FDMA) , Orthogonal Frequency-Division Multiple Access (OFDMA) , Single carrier frequency division multiple access (SC-FDMA) and other wireless networks. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA) , etc. UTRA includes WCDMA and other variants of CDMA. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM) . An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA) , Ultra Mobile Broadband (UMB) , IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDMA, Ad-hoc network, wireless sensor network, etc. In the following description, the terms “network” and “system” can be used interchangeably. Furthermore, the communications between two devices in the network may be performed according to any suitable communication protocols, including, but not limited to, the communication protocols as defined by a standard organization such as 3GPP. For example, the communication protocols may comprise the first generation (1G) , 2G, 3G, 4G, 4.5G, 5G, 6G communication protocols, and / or any other protocols either currently known or to be developed in the future.
[0045] The term “network device” or “network node” or “network function” refers to any suitable function which can be implemented in a network entity (physical or virtual) of a communication network. For example, the network function can 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. For example, the 5G system (5GS) may comprise a plurality of NFs such as Access and Mobility Management Function (AMF) , Charging Function (CHF) , Session Management Function (SMF) , Authentication Service Function (AUSF) , Unified Data Management (UDM) , Policy Control Function (PCF) , Application Function (AF) , Network Exposure Function (NEF) , User plane Function (UPF) and Network Repository Function (NRF) , radio access network (RAN) , service communication proxy (SCP) , network data analytics function (NWDAF) , network slice Selection Function (NSSF) , network slice-Specific Authentication and Authorization Function (NSSAAF) , an Ambient Internet of Things Function (AIOTF) , Unified Data Repository (UDR) , etc. In other embodiments, the network function may comprise different types of NFs for example depending on a specific network. For example, the 4G system (such as Long Term Evolution (LTE) ) may include Mobile Management Entity (MME) , home subscriber server (HSS) , PCRF (Policy and Charging Rules Function) , PGW (Packet Data Network Gateway) , PGW control plane (PGW-C) , PGW user plane (PGW-U) Serving gateway (SGW) , application server (AS) , SGW control plane (SGW-C) , SGW user plane (SGW-U) , E-UTRAN Node B (eNB) , etc. In other embodiments, the network function may comprise different types of NFs for example depending on a specific network.
[0046] The term “terminal device” refers to any end device that can access a communication network and receive services therefrom. By way of example and not limitation, the terminal device refers to a mobile terminal, user equipment (UE) , or other suitable devices. The UE may be, for example, a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , zero-energy (ZE) IoT (ZE-IoT) devices, Passive-IoT device, Ambient power-enabled IoT, or Ambient IoT devices, or an Access Terminal (AT) . The terminal device may include, but not limited to, a portable computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and a playback appliance, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, a wearable device, a personal digital assistant (PDA) , a portable computer, a desktop computer, a wearable terminal device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop-embedded equipment (LEE) , a laptop-mounted equipment (LME) , a USB dongle, a smart device, a wireless customer-premises equipment (CPE) and the like. In the following description, the terms “terminal device” , “terminal” , “user equipment” and “UE” may be used interchangeably. As one example, a terminal device may represent a UE configured for communication in accordance with one or more communication standards promulgated by the 3GPP (3rd Generation Partnership Project) , such as 3GPP LTE standard or NR standard. As used herein, a “user equipment” or “UE” may not necessarily have a “user” in the sense of a human user who owns and / or operates the relevant device. In some embodiments, a terminal device may be configured to transmit and / or receive information without direct human interaction. For instance, a terminal device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the communication network. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but that may not initially be associated with a specific human user.
[0047] As yet another example, in an IoT scenario, a 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 terminal device and / or network equipment. The terminal device may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as a machine-type communication (MTC) device. As one particular example, the terminal device may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances, for example refrigerators, televisions, personal wearables such as watches etc. In other scenarios, a terminal device may represent a vehicle or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.
[0048] References in the specification to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like 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 affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
[0049] It shall be understood that although the terms “first” and “second” etc. 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 example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed terms.
[0050] As used herein unless expressly stated to the contrary, the phrase “at least one of A and B”or “at least one of A or B” should be understood to mean any of the following “only A, only B, or both A and B. ” The phrase “A and / or B” should be understood to mean any of the following “only A, only B, or both A and B” .
[0051] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. 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 etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.
[0052] It is noted that these terms as used in this document are used only for ease of description and differentiation among nodes, devices or networks etc. With the development of the technology, other terms with the similar / same meanings may also be used.
[0053] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.
[0054] As mentioned above, the discovery parameters may be comprised in the messages associated with a network function (NF) discover, such the message in step 2a of Figure 1. For example, the discovery parameters for Nnrf_NFDiscovery_Request message is outlined in Table 6.2.3.2.3.1-1 of 3GPP TS 29.510 V19.2.0, and the Information Element (IE) "requester-features" indicates the feature negotiation information of the NFc 121, i.e. its own capability of supported features.
[0055] Additionally, the optional query parameter corresponding to a supported feature can be included in the discovery parameters. For example, the optional IE "max-payload-size" can be included in the query parameters, if the optional feature "Query-Params-Ext1" is supported and indicated in the IE "requester-features" .
[0056] Table 6.2.3.2.3.1-1 of 3GPP TS 29.510 V19.2.0: URI query parameters supported by the GET method on this resource
[0057] The following two tables 6.2.9-1 and 6.1.9-1 of 3GPP TS 29.510 V19.2.0 outline the available features that can be supported and / or negotiated for NF discovery service and NF registration service by NFc 121, NF provider (NFp) 141, and NRF 131 respectively.
[0058] Table 6.2.9-1 of 3GPP TS 29.510 V19.2.0: Features of supportedFeatures attribute used by Nnrf_NFDiscovery service
[0059] Table 6.1.9-1 of 3GPP TS 29.510 V19.2.0: Features of supportedFeatures attribute used by Nnrf_NFManagement service
[0060] Based on the feature negotiation, the discovery requester (e.g., NFc 121 in Figure 1) includes discovery parameters that reveals certain capabilities the discovery requester supports by itself and expected discovery results.
[0061] The expected discovery result provided by the discovery receiver (e.g., NRF 131 in Figure 1) can be influenced by the feature bit of the feature negotiation information (e.g. the "requester-features" IE of discovery parameters) alone, or the feature bit of the feature negotiation information (e.g. the "requester-features" IE of discovery parameters) and the corresponding optional query parameter together.
[0062] For example, the "max-payload-size" of Feature #2 (i.e. Query-Params-Ext1) in the above Table 6.2.9-1 of 3GPP TS 29.510 V19.2.0 is within the discovery parameter (aka query parameter) IE "requester-features" which the discovery requester uses to indicate the optional feature "Query-Params-Ext1" about "maximum payload size of the discovery result from NRF" it can support. The optional IE "max-payload-size" (see Table 6.2.3.2.3.1-1 of 3GPP TS 29.510 V19.2.0) is associated with this optional feature can be included in the query parameters, if the optional feature "Query-Params-Ext1" is supported and indicated in the IE "requester-features" . Based on the IE "max-payload-size" and IE "requester-features" (with feature bit "Query-Params-Ext1" setting to true) , the discovery receiver can decide max-payload-size of the discovery result that the discovery requester can support.
[0063] For another example, the "Service-Map" of Feature #6 in Table 6.2.9-1 of 3GPP TS 29.510 V19.2.0 is within the discovery parameter IE "requester-features" which the discovery requester uses to indicate whether certain schema / form (i.e. a list of NF Service Instances as a map in this case) of the discovery result from NRF it can support. Based on the IE "requester-features" (with feature bit "Service-Map" setting to true) , the discovery receiver can decide the list of NF service instances as a map can be supported in the discovery result by the discovery requester.
[0064] The mentioned features (e.g. "max-payload-size" , "Service-Map" ) indicated in Table 6.2.9-1 of 3GPP TS 29.510 V19.2.0 requires feature negotiation properly being performed between the discovery requester and discovery receiver so that NRF 131 can decide whether a specific feature is supported by the discovery requester, and then provide the discovery result accordingly (i.e. the content of discovery result can contain information with or without the mentioned feature) . Otherwise, the discovery result cannot be recognized by the discovery requester when it receives the discovery result contains features it does not support.
[0065] As shown in Figure 2, in case a NF discovery procedure (that can be a discovery request e.g. Nnrf_NFDiscovery_Request or NF status subscription request / notify e.g. Nnrf_NFManagement_NFStatusSubscribe / Nnrf_NFManagement_NFStatusNotify, or a service request contains discovery information (3gpp-Sbi-Discovery header) ) triggered by or associated with NFc 121 is forwarded by or delegated to one or more intermediate NF (s) (e.g. SCP 211, NRF 212) towards a target NRF 131, it is unclear whether the feature negotiation information (e.g. "requester-features" IE) included in the NF discovery procedure is associated with the original NF triggering the discovery procedure or with the intermediate NFs that sends / forwards the discovery message, thus it does not properly indicate the capability of NFc 121 or intermediate NF (s) (e.g. SCP 211, NRF 212) towards the target NRF 131, then feature negotiation with the target NRF 131 does not work properly. Hence the NF discovery procedure fails, or wrong discovery result can be consumed by the NFc 121 or the intermediate NF (s) 211, 212.
[0066] For example, for Figure 2, in which NFc 121, SCP 211, NRF1 212, NRF2 (as target NRF 131) are involved in the discovery procedure. NFc 121 may include the IE "requester-features" (with feature bit “Query-Params-Ext1” setting to true) and the IE "max-payload-size" = 2MB in the discovery parameters in the request message in step 1; SCP 211 may send the discovery message to NRF1 212 with all received discovery parameters in step 2 i.e. including the IE "requester-features" (with feature bit "Query-Params-Ext1" setting to true) and the IE "max-payload-size" = 2MB; though SCP 211 may only support payload size of discovery result not bigger than 1MB; NRF1 212 may forward similarly the discovery message to NRF2 131 with all received discovery parameters in step 3; though NRF1 212 may only support payload size of discovery result not bigger than 1MB; NRF2 141 determines the discovery result can be about 2MB based on the received discovery parameters, i.e. the IE "requester-features" (with feature bit "Query-Params-Ext1" setting to true) and the IE "max-payload-size" = 2MB, and sends back the discovery result of 2MB size in step 3.
[0067] When NRF1 212 receives discovery result of 2MB size in step3, it may not be able to handle the discovery result properly thus may drop the message, so that the discovery procedure fails. Similarly, if SCP 211 receives discovery result of 2MB size in step4, it may not be able to handle the discovery result properly thus may drop the message, so that the discovery procedure fails.
[0068] Figure 3 is a schematic signaling chart showing the messages in an example feature negotiation procedure for delegated NF discovery, according to the embodiments herein.
[0069] In an example, the flow / procedure may take delegated discovery as an example i.e. SCP 211 may act as intermediate NF. The flow procedure may also applicable similarly for other use cases when an intermediate NF is involved in the discovery procedure and forward / redirect the discovery procedure triggered by NFc 121. For example, in case of roaming, Access and Mobility Management Function (AMF) as NFc 121 may perform NF discovery towards home NRF (as NRF 131) via visiting NRF (as intermediate NF 212) .
[0070] Note that, there could be one or more SCPs and NRFs which performs similar roles as the SCP 211 / NRF 212 shown in Figures 2 to 4 and indicated in the flow below, and acts as an intermediate node involved in the discovery path.
[0071] As shown in Figure 3, the SCP 211 is an intermediate network node between a network function (NF) service consumer 121 and a Network Repository Function (NRF) for NF service discovery 131, which sometimes may be referred as "a first network node" . The NFc 121 is a network node which transmits its feature negotiation information to the first network node, which sometimes may be referred as "a second network node" (note that the second network node may be the NF service consumer or another intermediate network node adjacent to the first network node) . The NRF 131 is a network node which receives feature negotiation information from the first network node, which sometimes may be referred as "a third network node" (note that the second network node may be the NRF or another intermediate network node adjacent to the first network node) .
[0072] In an embodiment, the signaling chart in Figure 3 may show the feature negotiation for delegated NF discovery and may include the following messages or steps:
[0073] Step 1. The NF service consumer (NFc) 121 may send the service request to an SCP 211. The request includes discover parameter (s) (sometimes may be referred as "one or more discovery parameters" or "one or more parameters for NF discovery" ) for the SCP 211 to discover and select a NF service producer (NFp 141) .
[0074] The discovery parameter (s) may contain the feature negotiation information 1 (e.g. "requester-features" IE) , which indicates the supported features of NFc 121. Note, the discovery selection parameters may also not contain the feature negotiation information 1.
[0075] In an example, the feature negotiation information 1 may indicate whether one or more feature are supported. For example, the feature negotiation information 1 may include IE "requester-features" of Table 6.2.3.2.3.1-1 of 3GPP TS 29.510 V19.2.0 (with feature bit "Service-Map" setting to true) to indicate that the feature "Service-Map" (feature number #6 of Table 6.2.9-1 of 3GPP TS 29.510 V19.2.0) is supported.
[0076] In an example, the feature negotiation information 1 may indicate whether one or more feature are supported. For example, the feature negotiation information 1 may include IE "requester-features" of Table 6.2.3.2.3.1-1 of 3GPP TS 29.510 V19.2.0 (with feature bit "Query-Params-Ext1" setting to true) to indicate that the feature "Query-Params-Ext1" (feature number #2 of Table 6.2.9-1 of 3GPP TS 29.510 V19.2.0) is supported. In addition, the feature negotiation information 1 may include IE "Query-Params-Ext1" including the value "max-payload-size" (for example 2M) to indicate a value "max-payload-size" associated with the supported feature.
[0077] In an example, the IE "requester-features" of Table 6.2.3.2.3.1-1 of 3GPP TS 29.510 V19.2.0 may be extended to include more feature bit, see the following amended Table 6.2.3.2.3.1-1 for 3GPP TS 29.510 V19.2.0. Amended Table 6.2.3.2.3.1-1: U RI query parameters supported by the GET method on this resource
[0078] Note, step 1 can be a discovery request or service request sent / forwards by an intermediate NFs (e.g. SCP 211, NRF 212) .
[0079] The discovery parameters may contain one or more feature negotiation information which associates with one or more NFc or Intermediates NF (s) in the previous hops.
[0080] Step 2. The SCP 211 may recognize that the request is for discovery and / or select NFp 141. The SCP 211 may determine feature negotiation information 2 (also be referred as feature negotiation info2) (e.g. "requester-features" IE, or new IE such as "scp-features" ) , which indicates the supported feature of SCP 211. The SCP 211 may determine the feature negotiation info2, based on the received feature negotiation info1 of NFc 121, and / or its own capability of supported features, and / or the received discovery parameters.
[0081] In an example, SCP 211 may not update the feature negotiation information 1 or generate the feature negotiation information2. That is, one or more feature in the feature negotiation information 1 may be also supported by the SCP 211. In addition, one or more values associated with the one or more feature may be also acceptable by the SCP 211. As a result, the feature negotiation information2 may be same as the feature negotiation information 1 (see also step 3a of Figure 3) .
[0082] For example, the feature negotiation information 1 may include IE "requester-features" of Table 6.2.3.2.3.1-1 of 3GPP TS 29.510 V19.2.0 (with feature bit "Service-Map" setting to true) to indicate that the feature "Service-Map" (feature number #6 of Table 6.2.9-1 of 3GPP TS 29.510 V19.2.0) is supported. The SCP 211 may determine that this feature "Service-Map" may be also supported by the SCP 211, and then SCP 211 does not change this feature "Service-Map" .
[0083] For example, the feature negotiation information 1 may include IE "requester-features" of Table 6.2.3.2.3.1-1 of 3GPP TS 29.510 V19.2.0 (with feature bit "Query-Params-Ext1" setting to true) to indicate that the feature "Query-Params-Ext1" (feature number #2 of Table 6.2.9-1 of 3GPP TS 29.510 V19.2.0) is supported. In addition, the feature negotiation information 1 may include IE "Query-Params-Ext1" including the value "max-payload-size" to indicate a value "max-payload-size" (for example 2M) associated with the supported feature. The SCP 211 may determine that this feature "Query-Params-Ext1" may be also supported by the SCP 211, and this value "max-payload-size" (for example 2M) may be also acceptable by the SCP 211, and then SCP 211 does not change this feature "Query-Params-Ext1" and / or its value "max-payload-size" (for example 2M) .
[0084] The SCP 211 may remove the features it doesn’ t support but included in the feature negotiation information 1, and generate the feature negotiation information 2 by updating the feature negotiation information 1. As a result, the feature negotiation information2 may be updated from the feature negotiation information 1 (see also step 3b of Figure 3) .
[0085] For example, the feature negotiation information 1 may include IE "requester-features" of Table 6.2.3.2.3.1-1 of 3GPP TS 29.510 V19.2.0 (with feature bit "Service-Map" setting to true) to indicate that the feature "Service-Map" (feature number #6 of Table 6.2.9-1 of 3GPP TS 29.510 V19.2.0) is supported. The SCP 211 may determine that this feature "Service-Map" is not supported by the SCP 211, and then SCP 211 may discard or drop this feature "Service-Map" .
[0086] For example, the feature negotiation information 1 may include IE "requester-features" of Table 6.2.3.2.3.1-1 of 3GPP TS 29.510 V19.2.0 (with feature bit "Query-Params-Ext1" setting to true) to indicate that the feature "Query-Params-Ext1" (feature number #2 of Table 6.2.9-1 of 3GPP TS 29.510 V19.2.0) is supported. In addition, the feature negotiation information 1 may include IE "Query-Params-Ext1" including the value "max-payload-size" to indicate a value "max-payload-size" (for example 2M) associated with the supported feature. The SCP 211 may determine that this feature "Query-Params-Ext1" is not supported by the SCP 211, and then SCP 211 may discard or drop this feature "Query-Params-Ext1" .
[0087] In an example, if all of features in the feature negotiation information 1 are discarded or dropped by the SCP 211, then the SCP 211 does not need to transmit feature negotiation information 2 to NRF 131 (see also step 3d of Figure 3) .
[0088] In an example, SCP 211 may add the features it supports but not included in the feature negotiation information 1, and generate the feature negotiation information 2 by updating the feature negotiation information 1 (see also step 3b of Figure 3) .
[0089] For example, the feature negotiation information 1 may not include IE "requester-features" of Table 6.2.3.2.3.1-1 of 3GPP TS 29.510 V19.2.0 (with feature bit "Service-Map" setting to true) to indicate that the feature "Service-Map" (feature number #6 of Table 6.2.9-1 of 3GPP TS 29.510 V19.2.0) is supported. That is, the NFc 121 may not indicate whether it support the feature "Service-Map" . The SCP 211 may determine that this feature "Service-Map" may be supported by the SCP 211, and then SCP 211 may add this feature "Service-Map" to feature negotiation information 2 to indicate that the feature "Service-Map" is supported.
[0090] For example, the feature negotiation information 1 may not include IE "requester-features" of Table 6.2.3.2.3.1-1 of 3GPP TS 29.510 V19.2.0 (with feature bit "Query-Params-Ext1" setting to true) to indicate that the feature "Query-Params-Ext1" (feature number #2 of Table 6.2.9-1 of 3GPP TS 29.510 V19.2.0) is supported. That is, the NFc 121 may not indicate whether it support the feature "Query-Params-Ext1" . The SCP 211 may determine that this feature "Query-Params-Ext1" may be supported by the SCP 211, and then SCP 211 may add this feature "Query-Params-Ext1" to feature negotiation information 2 to indicate that the feature "Query-Params-Ext1" is supported. The SCP 211 may also determine the value of value "max-payload-size" (for example 1M) according to its capability.
[0091] In an example, SCP 211 may change the value of the features it supports and included in the feature negotiation information 1, and generate the feature negotiation information 2 by updating the feature negotiation information 1 (see also step 3b of Figure 3) .
[0092] For example, the feature negotiation information 1 may include IE "requester-features" of Table 6.2.3.2.3.1-1 of 3GPP TS 29.510 V19.2.0 (with feature bit "Query-Params-Ext1" setting to true) to indicate that the feature "Query-Params-Ext1" (feature number #2 of Table 6.2.9-1 of 3GPP TS 29.510 V19.2.0) is supported. In addition, the feature negotiation information 1 may include IE "Query-Params-Ext1" including the value "max-payload-size" to indicate a value "max-payload-size" (for example 2M) associated with the supported feature. The SCP 211 may determine that this feature "Query-Params-Ext1" may be also supported by the SCP 211, but this value "max-payload-size" (for example 2M) is not acceptable by the SCP 211 (for example the SCP 211 support a "max-payload-size" of 1M) , and then SCP 211 does not change this feature "Query-Params-Ext1" but amending the value "max-payload-size" to for example 2M, according to its own capability.
[0093] In an example, SCP 211 may generate the feature negotiation information 2, if the feature negotiation information 1 is not received (see also step 3b of Figure 3) .
[0094] For example, the NFc does not send the feature negotiation information 1 to the SCP 211. The SCP 211 may determine that this feature "Service-Map" may be supported by the SCP 211, and then SCP 211 may add this feature "Service-Map" to feature negotiation information 2 to indicate that the feature "Service-Map" is supported.
[0095] For example, the NFc does not send the feature negotiation information 1 to the SCP 211. The SCP 211 may determine that this feature "Query-Params-Ext1" may be supported by the SCP 211, and then SCP 211 may add this feature "Query-Params-Ext1" to feature negotiation information 2 to indicate that the feature "Query-Params-Ext1" is supported. The SCP 211 may also determine the value of "max-payload-size" (for example 1M) according to its capability.
[0096] In an example, SCP 211 may transmit both the feature negotiation information 1 from NFc 121 and the feature negotiation information 2 its own to the NRF 131 (see also step 3c of Figure 3) .
[0097] The SCP also determines discovery parameters 2, based on the feature negotiation info2, and / or the received feature negotiation info1, and / or its own capability of supported features, and / or the received discovery parameters.
[0098] In an example, depending on the feature negotiation information to be transmitted from the SCP 211, the SCP 211 may set the IE "requester-features" of Table 6.2.3.2.3.1-1 of 3GPP TS 29.510 V19.2.0 accordingly.
[0099] For example, the SCP 211 may set the feature bit "Service-Map" to true, if the feature negotiation information to be transmitted supports feature "Service-Map" .
[0100] For example, the SCP 211 may set the feature bit "Query-Params-Ext1" to true, if the feature negotiation information to be transmitted supports feature "Query-Params-Ext1" . In addition, the SCP 211 may set the value of "max-payload-size" to for example 1M, if the feature negotiation information to be transmitted supports a "max-payload-size" of 1M.
[0101] In an example, the SCP 211 may update the discovery parameters 1 and generate the discovery parameters 2 based on the discovery parameters 1, e.g. ● remove the discovery parameters it doesn’ t support but included in the discovery parameters 1. ● add the discovery parameters it supports but not included in the discovery parameters 1 ● change the value of the discovery parameters it supports and included in the discovery parameters 1.
[0102] In an example, the SCP 211 may not change the discovery parameters 1 and not generate the discovery parameters 2.
[0103] For example, SCP 211 may change the supporting the “Service-Map” of Feature #6 in Table 6.2.9-1 of 3GPP TS 29.510 V19.2.0, from YES to NO (or vice versa) in feature negotiation information
[0104] For example, SCP 211 may change the supporting the “max-payload-size” of Feature #2 in Table 6.2.9-1 of 3GPP TS 29.510 V19.2.0 in feature negotiation information, and / or change the value of “max-payload-size” in discovery parameters
[0105] Step 3. SCP 211 may send the discovery request to the target NRF 131, includes discover parameters1 and / or discovery parameters 2 in the discovery request and decide how to handle the feature negotiation information (s) the discovery request based on the determination at step 2.
[0106] For example, the SCP 211 may: ● Send the feature negotiation information1 in the discover parameters (step 3a of Figure 3) ; ● Send the feature negotiation information2 in the discover parameters (step 3b of Figure 3) ; ● Send both the feature negotiation information1 and the feature negotiation information2 in the discover parameters (step 3c of Figure 3) ; or ● Send no feature negotiation information in the discover parameters (step 3d of Figure 3) .
[0107] Note that step 3 can be performed between an intermediate NF (e.g. SCP, NRF or other NF) and another intermediate NF (e.g. SCP, NRF or other NF) . i.e. there could be one or more intermediate NFs (such as SCP 211, NRF 212) before the request reaches the target NRF 131.
[0108] Step 4. The target NRF 131 determines the discovery result based on the received discover parameters and / or feature negotiation information (s) .
[0109] The target NRF 131 may also determines feature negotiation information 3 which associates with the discovery result, based on received feature negotiation info (s) , and / or its own capability of supported features, and / or the received discovery parameters.
[0110] The target NRF 131 may send back the discovery result and / or feature negotiation information 3.
[0111] SCP 211 may get discover response with target NF profile (s) in the discovery result and / or feature negotiation3.
[0112] Step 5. SCP 211 may perform rest of handling the service request.
[0113] SCP 211 may send back the discovery result to its previous hop, e.g. in case the SCP 211 receives the request from another Intermediate NF as mentioned in step1.
[0114] SCP 211 may also include the feature negotiation information2 and / or feature negotiation information 3 and / or updated discovery parameters in the message, which indicates to the previous hop the association between the discovery result with the feature negotiation information (s) and / or updated discovery parameters.
[0115] Figure 4 is a schematic signaling chart showing the messages in another example feature negotiation procedure for delegated NF discovery, according to the embodiments herein.
[0116] As shown in Figure 4, when a NRF discovery message progresses towards its final target NRF 131, it traverses through various intermediate network functions (such as SCP 211, NRF 212) . Some of these function purely as transparent proxies, without decoding the message content, while others need to intercept and understand the content's version / feature set.
[0117] The challenge arises because the content's version / feature set can differ across various network functions in the path. Some network functions may support older versions / features, while others may support newer ones. Consequently, the final target network function / NRF 131 must consider the capabilities of all network functions along the message path to decide on the appropriate feature set to use.
[0118] The objective is to find the most mutually compatible version / feature set that enables all necessary network functions to intercept and process the content correctly, while also taking advantage of the benefits introduced by the latest version / features whenever possible.
[0119] So that, a list of feature negotiation information (e.g. Requester Features List can be included in the discovery request or service request, e.g. the above mentioned feature negotiation info1 or feature negotiation info2. This list would include the "requester-features" of all network functions (NFs) along the message path. Each NF in the path may play a different role in handling the message, either as a transparent proxy or as an interception proxy. For example, some NFs function solely as transparent proxies, while others act as interception proxies that need to decode the message and process specific parts of it.
[0120] By utilizing a requester-features-list, it can ensure that the message is compatible with the requirements and capabilities of all NFs it encounters. This approach allows each NF to access the necessary feature information relevant to its role, facilitating the appropriate handling of the message and optimizing the use of supported features across the network path.
[0121] In response, the target NRF 131 will provide a Path-Optimized Feature Set along with a TTL (time to live) value (e.g., the above mentioned feature negotiation info3) . This feature set can be used by all NFs along the message path. Each NF can cache the feature set within the duration specified by the TTL, ensuring adherence to the Path-Optimized Feature Set during its valid period.
[0122] This approach allows for efficient and consistent message handling across multiple NFs by standardizing the feature set used throughout the path. By caching the feature set, NFs can quickly access and apply the necessary features, reducing processing time and enhancing interoperability. The TTL ensures that cached information remains relevant and encourages timely updates when necessary.
[0123] Requester Features List Definition and Example
[0124] The requester-features-list is a structured JSON array designed to capture the features requested by NFs along a message path. Each item in this list is an object containing the following properties: ● requesterId: A string identifier for the requester NF. ● requester-features: A string representing the requested features of the NF, following the pattern ^ [A-Fa-f0-9] *$. ● proxyMode: A string indicating the mode of proxy operation for the NF, with possible values being: ○ "Transparent Proxy" ○ "Interception Proxy"
[0125] The list is ordered, ensuring the sequence of items reflects the intended processing order. JSON Schema for Requester Features List
[0126] Example of Requester Features List Below is an example of a requester-features-list containing three items:
[0127] Path-Optimized Features Set Definition and Example
[0128] The Path-Optimized-Features-Set is a JSON object designed to convey the optimal feature set and its validity period for use by NFs along the message path. It includes the following properties: ● featureSet: A string representing the SupportedFeatures as defined in 3GPP TS 29.510, following the pattern ^ [A-Fa-f0-9] *$. ● TTL: An integer representing the Time-To-Live, specifying the duration (in seconds) for which the feature set is valid.
[0129] JSON Schema for Path-Optimized Features Set
[0130] Example of Path-Optimized Features Set Below is an example of a Path-Optimized-Features-Set:
[0131] In this example: ● featureSet is represented as a hexadecimal string abc123, complying with the pattern ^ [A-Fa-f0-9] *$. ● TTL is set to 3600 seconds, indicating that the feature set is valid for one hour.
[0132] This structure ensures efficient management of feature sets across different NFs by standardizing the use and validity period of the optimal features.
[0133] The embodiments of this disclosure introduce methods and procedures to allow the intermediate NF (s) (e.g. SCP 211, NRF 212) to indicate toward the target NRF 131 the feature negotiation information and / or discovery parameters for a forwarded or delegated discovery request.
[0134] The intermediate NF (s) (e.g. SCP 211) may insert / update / replace the feature negotiation information and / or discovery parameters for a forwarded or delegated discovery request.
[0135] The embodiments of this disclosure may ensure feature negotiation working for a forwarded or delegated discovery request.
[0136] Note that, the expression "the value of " max-payload-size" (for example 1M) " used in the above embodiments does not aim to limit the "value" to only integer type. Instead, the "value" should be understood as also comprising or including other types, such as integer, char, Boolean, string, enumeration, and / or other data structure and / or data type defined.
[0137] Figure 5 is a schematic flow chart showing an example method 500 in the first network node, according to the embodiments herein. In an embodiment, the flow chart in Figure 5 may be implemented in the first network node, such as the SCP 211, but may also implemented in other intermediate network node between a network function (NF) service consumer and a Network Repository Function (NRF) for NF service discovery.
[0138] The method 500 may comprise the step S501, in which the first network node (such as the SCP 211) may receive a first message comprising one or more first discovery parameters from a second network node (such as NFc 121) .
[0139] The method 500 may comprise the step S502, in which the first network node (such as the SCP 211) may transmit a second message comprising one or more second discovery parameters to a third network node (such as NRF 131) . The one or more second discovery parameters are at least in part updated based on the one or more first discovery parameters
[0140] The method 500 may comprise the step S503, in which the first network node (such as the SCP 211) may receive a third message comprising a discovery result from the third network node (such as NRF 131) . At least one of the one or more first discovery parameters and the one or more second discovery parameters impacts the returned discovery result by the third network node 131 for a discovered NF.
[0141] In an embodiment, at least one of the one or more first discovery parameters and the one or more second discovery parameters comprises feature negotiation information indicating whether one or more feature are supported, such as the above mentioned "Service-Map" , and "Query-Params-Ext1" .
[0142] In an embodiment, the feature negotiation information further indicates a value associated with a supported feature, such as a value "max-payload-size" (for example 2M) associated with the feature "Query-Params-Ext1" .
[0143] In an embodiment, at least one of the first message and the second message is associated with a network function (NF) discovery.
[0144] In an embodiment, the one or more first discovery parameters comprise first feature negotiation information indicating that a first feature is supported by the second network node 121, such as the above mentioned "Service-Map" , and "Query-Params-Ext1" . The one or more second discovery parameters comprise second feature negotiation information indicating that the first feature is supported by the first network node 211, such as the above mentioned "Service-Map" , and "Query-Params-Ext1" .
[0145] In an embodiment, the first feature negotiation information and the second feature negotiation information each indicates a same value associated with the first feature, such as a value "max-payload-size" (for example 2M) associated with the feature "Query-Params-Ext1" .
[0146] In an embodiment, the second feature negotiation information indicates a second value associated with the first feature, such as a value "max-payload-size" (for example 1M) associated with the feature "Query-Params-Ext1" . The second value (for example 1M) is based on a first value indicated by the second network node 121 (for example 2M) and / or a capability of the first network node 211 (for example 1M) .
[0147] In an embodiment, the second value is based on the smaller one between the first value and a value based on the capability of the first network node 211.
[0148] In an embodiment, the one or more first discovery parameters comprise first feature negotiation information indicating that a first feature is supported by the second network node 121, such as the above mentioned "Service-Map" . The one or more second discovery parameters comprise second feature negotiation information indicating that the first feature is supported by the second network node 121 such as the above mentioned "Service-Map" and that a second feature is supported by the first network node 211 such as the above mentioned "Query-Params-Ext1" .
[0149] In an embodiment, the one or more first discovery parameters comprise first feature negotiation information indicating that a first feature is supported by the second network node 121, such as the above mentioned "Service-Map" . The one or more second discovery parameters comprise second feature negotiation information indicating that both the first feature such as the above mentioned "Service-Map" and a second feature such as the above mentioned "Query-Params-Ext1" are supported by the first network node 211.
[0150] In an embodiment, the first feature negotiation information further indicates a first value associated with the first feature. The second feature negotiation information further indicates the first value associated with the first feature and a second value associated with the second feature.
[0151] In an embodiment, the first feature negotiation information further indicates an operation mode of the second network node 121. The second feature negotiation information further indicates an operation mode of the second network node 121 and an operation mode of the first network node 211.
[0152] In an embodiment, the operation mode comprises: -a transparent mode, in which the first or second feature does not impact the discovery result; -an interception mode, in which it is possible that the first or second feature impacts the discovery result.
[0153] In an embodiment, the first and / or second feature negotiation information indicates a feature list comprising identifier of a network node 121, 211, 212, a feature supported by respective network node 121, 211, 212, an operation mode of respective network node 121, 211, 212, see Figure 4.
[0154] In an embodiment, the one or more first discovery parameters do not comprise feature negotiation information. The one or more second discovery parameters comprises second feature negotiation information indicating that a second feature is supported by the first network node 211, such as the above mentioned "Service-Map" , and "Query-Params-Ext1" .
[0155] In an embodiment, the second feature negotiation information further indicates a value associated with the second feature, such as a value "max-payload-size" (for example 2M) associated with the feature "Query-Params-Ext1" .
[0156] In an embodiment, the one or more first discovery parameters comprise first feature negotiation information indicating that a first feature is supported by the second network node 121, such as the above mentioned "Service-Map" , and "Query-Params-Ext1" . The one or more second discovery parameters do not comprise second feature negotiation information, or the one or more second discovery parameters comprise second feature negotiation information indicating that the first feature is not supported by the first network node 211, such as the above mentioned "Service-Map" , and "Query-Params-Ext1" .
[0157] In an embodiment, the first feature negotiation information further indicates a first value associated with the first feature, such as a value "max-payload-size" (for example 2M) associated with the feature "Query-Params-Ext1" ; and the first value is removed by the first network node 211.
[0158] In an embodiment, the discovery result comprises a time to live (TTL) value to indicate a valid time of the discovery result.
[0159] In an embodiment, the discovery result comprises one or more third parameters comprising third feature negotiation information from the third network node 131, such as the above mentioned "Service-Map" , and "Query-Params-Ext1" .
[0160] In an embodiment, the method may further comprise the step of transmitting a fourth message to the second network node 121 (not shown in Figure 5) . The fourth message comprises the discovery result not updated or changed by the first network node 211, for example when the first network node 211 is operated in a transparent mode. In an example, the fourth message comprises the discovery result updated or changed by the first network node 211, for example when the first network node 211 is operated in an interception mode.
[0161] In an embodiment, the first network node 211 may implement a first intermediate network node between a network function (NF) service consumer and a Network Repository Function (NRF) for NF service discovery. The second network node 121 may implement the NF service consumer or a second intermediate network node adjacent to the first intermediate network node. The third network node 131 may implement the NRF or a third intermediate network node adjacent to the first intermediate network node.
[0162] In an embodiment, the first message and / or the second message may be one of: -a discovery service request; -a NF status subscription request; -a NF status subscription notify; -a service request comprising discovery information.
[0163] In an embodiment, the first, second, or third intermediate network node may be one of: -a Service Communication Proxy (SCP) ; -a NRF; -a NF other than NRF.
[0164] In an embodiment, the first, second, or third network node 121, 211, 131 may be at serving network or at home network.
[0165] In an embodiment, at least one of the one or more first discovery parameters and the one or more second discovery parameters impact a form of NF candidates within the discovery result, a maximum size of the discovery result, or a maximum number of NF candidates within the discovery result.
[0166] In an embodiment, a bit of the feature negotiation information indicates whether a feature impacting the discovery result is supported, such as feature bit "Service-Map" of IE "requester-features" .
[0167] In an embodiment, the bit may indicate one of: -Service-Map; -Enh-NF-Discovery; -Allowed-ruleset; -DNN-List-Optimization; -Shared-Data.
[0168] In an embodiment, a bit of the feature negotiation information indicates whether a feature impacting the discovery result is supported, such as feature bit "Query-Params-Ext1" of IE "requester-features" . In addition, a respective information element of the feature negotiation information indicates a value associated with a supported feature, such as a value "max-payload-size" (for example 2M) associated with the feature "Query-Params-Ext1" .
[0169] The above steps are only examples, and the first network node (such as the SCP 211) may perform any related actions described with respect to Figure 1 to Figure 4.
[0170] Figure 6 is a schematic flow chart showing an example method 600 in the third network node, according to the embodiments herein. In an embodiment, the flow chart in Figure 6 may be implemented in the third network node, such as the NRF 131, but may also implemented in other network node, which receives feature negotiation information from an intermediate network node between a network function (NF) service consumer and a Network Repository Function (NRF) for NF service discovery.
[0171] The method 600 may comprise the step S601, in which the third network node (such as the NRF 131) may receive a second message comprising one or more second discovery parameters from a first network node (such as the SCP 211) , the one or more second discovery parameters are at least in part updated based on one or more first discovery parameters from a second network node (such as the NFc 121) .
[0172] The method 600 may comprise the step S602, in which the third network node (such as the NRF 131) may transmit a third message comprising a discovery result to the first network node 211. At least one of the one or more first discovery parameters and the one or more second discovery parameters impacts the returned discovery result by the third network node 131 for a discovered NF.
[0173] In an embodiment, the one or more first discovery parameters comprise first feature negotiation information indicating that a first feature is supported by the second network node 121, such as the above mentioned "Service-Map" . The one or more second discovery parameters comprise second feature negotiation information indicating that the first feature is supported by the second network node 121 such as the above mentioned "Service-Map" and that a second feature is supported by the first network node (211) such as the above mentioned "Query-Params-Ext1" .
[0174] In an embodiment, the one or more first discovery parameters comprise first feature negotiation information indicating that a first feature is supported by the second network node 121, such as the above mentioned "Service-Map" , and "Query-Params-Ext1" . The one or more second discovery parameters comprise second feature negotiation information indicating that the first feature is supported by the first network node 211, such as the above mentioned "Service-Map" , and "Query-Params-Ext1" .
[0175] In an embodiment, the first feature negotiation information further indicates a first value associated with the first feature. The second feature negotiation information further indicates the first value associated with the first feature and a second value associated with the second feature.
[0176] In an embodiment, the first feature negotiation information further indicates an operation mode of the second network node 121. The second feature negotiation information further indicates an operation mode of the second network node 121 and an operation mode of the first network node 211.
[0177] In an embodiment, the operation mode comprises: -a transparent mode, in which the first or second feature does not impact the discovery result; -an interception mode, in which it is possible that the first or second feature impacts the discovery result.
[0178] In an embodiment, the first and / or second feature negotiation information indicates a feature list comprising identifier of a network node 121, 211, 212, a feature supported by respective network node 121, 211, 212, an operation mode of respective network node 121, 211, 212, see Figure 4.
[0179] In an embodiment, the discovery result may be generated based on one or more features supported by respective one or more network nodes 121, 211, 212, and one or more operation modes of respective one or more network nodes 121, 211, 212.
[0180] In an embodiment, the discovery result comprises a time to live (TTL) value to indicate a valid time of the discovery result.
[0181] In an embodiment, the method may further comprise the step caching the discovery result during the valid time of the discovery result (not shown in Figure 6) .
[0182] The above steps are only examples, and the third network node (such as the NRF 131) may perform any related actions described with respect to Figure 1 to Figure 4.
[0183] Figure 7 is a schematic block diagram showing an example first network node 700, according to the embodiments herein. In an embodiment, the example first network node 700 in Figure 7 may be implemented as the above mentioned first network node, such as the SCP 211 or NRF 212, but may also implemented as other intermediate network node for feature negotiation.
[0184] In an embodiment, the first network node 700 may comprise processing circuitry 701; and a memory 702. The processing circuitry 701 may be configured to perform the above method 500.
[0185] Note that, the first network node 700 may be implemented as hardware, software, firmware and any combination thereof. For example, the first network node 700 may include a plurality of units, circuities, modules or the like, each of which may be used to perform one or more steps of the example method 500 or one or more steps shown in Figure 5 related to the first network node (such as the SCP 211 or NRF 212) .
[0186] Figure 8 is a schematic block diagram showing an example third network node 800, according to the embodiments herein. In an embodiment, the example third network node 800 in Figure 8 may be implemented as the above mentioned third network node, such as the NRF 212 or NRF 131, but may also implemented in other network node for receiving feature negotiation information from an intermediate network node.
[0187] In an embodiment, the third network node 800 may comprise processing circuitry 801; and a memory 802. The processing circuitry 801 may be configured to perform the above method 600.
[0188] Note that, the third network node 800 may be implemented as hardware, software, firmware and any combination thereof. For example, the third network node 800 may include a plurality of units, circuities, modules or the like, each of which may be used to perform one or more steps of the example method 600 or one or more steps shown in Figure 6 related to the third network node (such as the NRF 212 or NRF 131) .
[0189] Figure 9 is a schematic block diagram showing an example computer-implemented network node 900, according to the embodiments herein. In an embodiment, the network node 900 may be configured as the above mentioned network node, such as the NFc 121, the SCP 211, the NRF 211, the NRF 131, the NFp 141 as shown in Figure 1 to Figure 4.
[0190] In an embodiment, the network node 900 may include but not limited to at least one processor such as Central Processing Unit (CPU) 901, a computer-readable medium 902, and a memory 903. The memory 903 may comprise a volatile (e.g., Random Access Memory, RAM) and / or non-volatile memory (e.g., a hard disk or flash memory) . In an embodiment, the computer-readable medium 902 may be configured to store a computer program and / or instructions, which, when executed by the processor 901, causes the processor 901 to carry out any of the above mentioned methods 500 or 600.
[0191] In an embodiment, the computer-readable medium 902 (such as tangible, non-transient computer readable medium) may be stored in the memory 903. In another embodiment, the computer program may be stored in a remote location for example computer program product 904 (also may be embodied as or include a tangible, non-transient computer-readable medium) , and accessible by the processor 901 via for example carrier 905.
[0192] The computer-readable medium 902 and / or the computer program product 904 may be distributed and / or stored on a removable computer-readable medium, e.g. diskette, CD (Compact Disk) , DVD (Digital Video Disk) , flash or similar removable memory media (e.g. compact flash, SD (secure digital) , memory stick, mini SD card, MMC multimedia card, smart media) , HD-DVD (High Definition DVD) , or Blu-ray DVD, USB (Universal Serial Bus) based removable memory media, magnetic tape media, optical storage media, magneto-optical media, bubble memory, or distributed as a propagated signal via a network (e.g. Ethernet, ATM, ISDN, PSTN, X. 25, Internet, Local Area Network (LAN) , or similar networks capable of transporting data packets to the infrastructure node) .
[0193] Figure 10 is a schematic block diagram showing an example communication system 1000, according to the embodiments herein.
[0194] In an embodiment, the communication system 1000 may comprise the first network node 700, the second network node 1001 and the third network node 800. In an embodiment, the communication system 1000 may comprise terminal devices and / or network nodes such as the NFc 121, the SCP 211, the NRF 211, the NRF 131, the NFp 141 as shown in Figure 1 to Figure 4.
[0195] In an embodiment, the communication system 1000 may be configured in an OTT scenario. The OTT connection may be transparent in the sense that the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, the network nodes 700, 1001, 800, the NFc 121, the SCP 211, the NRF 211, the NRF 131, or the NFp 141 may not or need not be informed about the past routing of an incoming downlink communication with data originating from one or more network functions to be forwarded (e.g., handed over) to a connected terminal device (s) . Similarly, the network nodes 700, 1001, 800, the NFc 121, the SCP 211, the NRF 211, the NRF 131, or the NFp 141 needs not be aware of the future routing of an outgoing uplink communication originating from the terminal device (s) towards one or more network functions.
[0196] It should also be understood that, a network element (such as the network nodes 700, 1001, 800, the NFc 121, the SCP 211, the NRF 211, the NRF 131, or the NFp 141) may be implemented either as 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.
[0197] This disclosure also proposes the following embodiments / implements.The First Change Request for 3GPP TS 29.500 V19.2.0
[0198] Title: Discovery Factors Handling for Indirect Communication
[0199] Reason for change: For indirect communication with delegated discovery / reselection, the NF consumer will include discovery factors (which are HTTP request header mapped from NRF query parameters, one header per query parameter) , with each header indicate the value of the query parameter. The SCP will convert the discovery factors to the corresponding query parameters in the discovery request to the NRF to find the NF producer (s) to process the service request. When NRF processing the NF discovery request, based on the value of certain query parameters and / or certain feature bits in requester-features query parameter, the NRF will generate the discovery result accordingly to secure that the NF candidates in the discovery result can be successfully accepted / parsed / understood by the NF consumer. For indirect communication with delegated discovery / reselection, as the discovery result will be handled by the SCP, the value of these query parameters and / or feature bits shall be set according to the SCP capabilities. This requires that: 1. the NF consumer should not include such discovery factors and / or feature bits in the service request, and 2. even if the SCP received these headers / feature bits, the SCP should replace with values according to its own capabilities in corresponding query parameters to the NRF.
[0200] Summary of change: Add description to clarify how NF consumer and SCP dealing with discovery factors for query parameters / feature bits that will impact the format of NRF discovery result.
[0201] Consequences if not approved: Indirection communication with delegate discovery and / or reselection will not work, if the SCP incorrectly forwarded the query parameters / feature bits with NF consumer provided values which are not supported by the SCP, because the SCP cannot handle the discovery result returned by the NRF.
[0202] ***First Change **** (the underline indicates the parts to be added) 6.10.3.2 Conveyance of NF Discovery Factors When the NF service consumer is configured to use delegated service discovery, it shall include in the HTTP / 2 request message the necessary NF service discovery factors to be used by the SCP to perform the NF service discovery procedures and the Service access authorization procedures (see clause 13.4.1.3.2 of 3GPP TS 33.501
[0017] ) on behalf of the NF service consumer. The latter shall convey these NF service discovery factors using the"3gpp-Sbi-Discovery-*" request headers. How to set the values of these "3gpp-Sbi-Discovery-*" request headers is detailed in clause 5.2.3.2.7. The NF service consumer should also include at least the target NF type and service name in the corresponding "3gpp-Sbi-Discovery-*" request header (s) in its request to the SCP. The NF service consumer may indicate the NRF to use, e.g. as a result of an NSSF query, by including the 3gpp-Sbi-Nrf-Uri header with the NRF API URIs. *******Text Skipped for Clarity (referring to 3GPP TS 29.500 V19.2.0 for more details) ******* If the service request contains "3gpp-Sbi-Discovery-*" request header (s) that are not supported by the SCP, the latter should include the corresponding query parameters in the discovery request to the NRF. Based on operator policy, the SCP may alternatively reject the request and return a response with the status code "400 Bad Request" to the NF service consumer with an "INVALID_DISCOVERY_PARAM" error. If the service request does not contain the 3gpp-Sbi-Discovery-preferred-api-versions header, the SCP shall select an NF instance and / or service instance that supports the MAJOR version received in the request URI of the service request message. Otherwise, the preferred API MAJOR version included in the 3gpp-Sbi-Discovery-preferred-api-versions header shall be the same as the MAJOR version of the request URI of the service request message. The SCP shall reject the request and return a response with the status code "400 Bad Request" to the NF service consumer with an "INVALID_API" error if no NF profile is found matching the MAJOR version; in this case, the SCP may indicate in the problem details the MAJOR API version (s) known to be supported by NF service producers for the corresponding service.If the NF service consumer delegates the discovery or reselection to the SCP, the service request should not include the "3gpp-Sbi-Discovery-*" request header (s) that will impact the max number of candidates / max size of discovery result, e.g. the 3gpp-Sbi-Discovery-limit, 3gpp-Sbi-Discovery-max-payload-size and 3gpp-Sbi-Discovery-max-payload-size-ext headers. If the SCP has received these request headers in the service request with values that are not supported by the SCP, when sending the discovery request to the NRF the SCP shall either discard these headers or lower the values (in the corresponding query parameters) according to its own capabilities. Additionally, if the SCP received the 3gpp-Sbi-Discovery-requester-features request header, when sending the discovery request to the NRF the SCP shall set the feature bits (in the requester-features query parameter) which will impact the form of the NF candidates to be returned (e.g. "Service-Map" , "Enh-NF-Discovery" , "Allowed-ruleset" , "DNN-List-Optimization" or "Shared-Data" ) according to its own capabilities. ***End of Changes ***The Second Change Request for 3GPP TS 29.510 V19.2.0
[0203] Title: Correction on Requester Features and Query Parameters
[0204] Reason for change: 1 / In order to allow the NRF to determine the format of the discovery result, the NF consumer should indicate certain feature bits in the requester-features query parameters. Currently some feature bits are missing in the description. 2 / TS 23.502 has indicated that the NRF in PLMN 1 may cache the discovery result from NRF in PLMN 2: The NRF in PLMN-1 may cache the response and use it to answer subsequent Nnrf_NFDiscovery without interactions with the NRF in PLMN-2. In order to successfully process the discovery result from NRF in PLMN 2, the NRF in PLMN 1 needs to adjust the value of certain query parameters to secure that the discovery result can be successfully processed.
[0205] Summary of change: 1 / Clarify the NRF in Serving PLMN shall adjust the value of query parameters to secure successfully processing of discovery result received from Home PLMN. 2 / Add missing feature bits in the description of requester-features parameter.
[0206] Consequences if not approved: NRF cannot return optimized discovery result according to NF consumer capability; the NRF in PLMN 1 cannot process the discovery result from NRF in PLMN 2 during NF discovery between different PLMNs.
[0207] ***First Change **** (the underline indicates the parts to be added) 5.3.2.2.3 Service Discovery in a different PLMN NOTE 1: The requirements specified in this clause are defined assuming an inter-PLMN NF Discovery request sent from a Serving PLMN to a Home PLMN. The same requirements apply to any NF Discovery request sent from a source PLMN or SNPN towards a target PLMN or SNPN, where the source PLMN / SNPN and the target PLMN / SNPN can correspond to a serving network, a home network or a 3rd network (e.g. inter-PLMN mobility between two VPLMNs) . The service discovery in a different PLMN is done by querying the "nf-instances" resource in the NRF of the Home PLMN. *******Text Skipped for Clarity (referring to 3GPP TS 29.510 V19.2.0 for more details) ******* -the indComWoDelDiscReq IE set to true to indicate that indirect communication without delegated discovery with NF selection at target domain is requested. If either the indComWithDelDiscReq or the indComWoDelDiscReq IE is included in the search result, the search result may also include: -the allNfTypesInd IE set to true to indicate that the indirect communication information provided in the NF Discovery response applies to all NF types (otherwise the indirect communication information shall only apply to the NF type requested in the Nnrf_NFDiscovery request) ; and / or -the scpApiRoot IE indicating the apiRoot of an SCP in the Home PLMN where to send the service request; the authority of the apiRoot may correspond to an authority of a specific SCP, or to an authority that can resolve into several SCPs for scalability, load sharing and resiliency purposes. NOTE 3: "Target domain" can refer to a target PLMN or a target SNPN, i.e. the above procedure can be used for selecting the target NF in the target PLMN or SNPN.If the NRF in Serving PLMN is configured to cache the response from NRF in Home PLMN for subsequent discovery result, in step 1 when forwarding the NRF in Serving PLMN shall adjust the value of the query parameters when forwarding the discovery request to the NRF in Home PLMN in order to successfully process the discovery result:-lower the value of query parameters impacting the max number of candidates / max size of discovery result, e.g. the limit, max-payload-size and max-payload-size-ext query parameters, according to its own capability; and-clear the feature bit impacting the format of the discovery result, e.g. "Service-Map" , "Enh-NF-Discovery" , "Allowed-ruleset" , "DNN-List-Optimization" or "Shared-Data" , if not supported.
[0208] ***Next Change **** (the underline indicates the parts to be added) 6.2.3.2.3.1 GET This operation retrieves a list of NF Instances, and their offered services, currently registered in the NRF, satisfying a number of filter criteria, such as those NF Instances offering a certain service name, or those NF Instances of a given NF type (e.g., AMF) . Table 6.2.3.2.3.1-1: URI query parameters supported by the GET method on this resource When certain query parameters in the discovery request are not supported by the NRF, the NRF shall ignore the unsupported query parameters and continue processing the request with the supported query parameters. The default logical relationship among the supported 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" , "mbs-session-id" , "ind-com-with-del-disc" , "ind-com-wo-del-disc" , "preferred-upf-packet-inspection-func" and "preferred-operator-config-capabilities" query parameters (see Table 6.2.3.2.3.1-1) . The NRF may support the Complex query expression as defined in 3GPP TS 29.501 [5] for the NF Discovery service. If the "complexQuery" query parameter is included, then the logical relationship among the query parameters contained in "complexQuery" query parameter is as defined in 3GPP TS 29.571 [7] . A NRF not supporting Complex query expression shall reject a NF service discovery request including a complexQuery parameter, with a ProblemDetails IE including the cause attribute set to INVALID_QUERY_PARAM and the invalidParams attribute indicating the complexQuery parameter. *******Text Skipped for Clarity (referring to 3GPP TS 29.510 V19.2.0 for more details) **********End of Changes ***
[0209] It will be recognized that principles of the disclosure are not limited to the embodiments so described, but instead can be practiced with modification and alteration without departing from the scope of the appended claims. The above embodiments may include the undertaking only a subset of such features, undertaking a different order of such features, undertaking a different combination of such features, and / or undertaking additional features than those features explicitly listed. The scope of the embodiments should, therefore, be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.
Claims
1.A method (500) performed by a first network node (211) , comprising:-receiving a first message comprising one or more first discovery parameters from a second network node (121) ;-transmitting a second message comprising one or more second discovery parameters to a third network node (131) ; and-receiving a third message comprising a discovery result from the third network node (131) ,wherein at least one of the one or more first discovery parameters and the one or more second discovery parameters impact the returned discovery result by the third network node (131) for a discovered NF, and wherein the one or more second discovery parameters are at least in part updated based on the one or more first discovery parameters.2.The method (500) according to claim 1, wherein at least one of the one or more first discovery parameters and / or the one or more second discovery parameters comprise feature negotiation information indicating whether one or more feature are supported.3.The method (500) according to claim 2, the feature negotiation information further indicates a value associated with a supported feature.4.The method (500) according to any one of claims 1 to 3, wherein at least one of the first message and the second message is associated with a network function (NF) discovery.5.The method (500) according to any one of claims 1 to 4, wherein the one or more first discovery parameters comprise first feature negotiation information indicating that a first feature is supported by the second network node (121) ; andthe one or more second discovery parameters comprise second feature negotiation information indicating that the first feature is supported by the first network node (211) .6.The method (500) according to claim 5, wherein the first feature negotiation information and the second feature negotiation information each indicates a same value associated with the first feature.7.The method (500) according to claim 5, wherein the second feature negotiation information indicates a second value associated with the first feature, and wherein the second value is based on a first value indicated by the second network node (121) and / or a capability of the first network node (211) .8.The method (500) according to claim 7, wherein the second value is based on the smaller one between the first value and a value based on the capability of the first network node (211) .9.The method (500) according to any one of claims 1 to 4, wherein the one or more first discovery parameters comprise first feature negotiation information indicating that a first feature is supported by the second network node (121) ; andthe one or more second discovery parameters comprise second feature negotiation information indicating that the first feature is supported by the second network node (121) and that a second feature is supported by the first network node (211) or that both the first feature and a second feature are supported by the first network node (211) .10.The method (500) according to claim 9, wherein the first feature negotiation information further indicates a first value associated with the first feature; andthe second feature negotiation information further indicates the first value associated with the first feature and a second value associated with the second feature.11.The method (500) according to claim 9 or 10, wherein the first feature negotiation information further indicates an operation mode of the second network node (121) ; andwherein the second feature negotiation information further indicates an operation mode of the second network node (121) and an operation mode of the first network node (211) .12.The method (500) according to claim 11, wherein the operation mode comprises:-a transparent mode, in which the first or second feature does not impact the discovery result; or-an interception mode, in which it is possible that the first or second feature impacts the discovery result.13.The method (500) according to claim 12, wherein the first and / or second feature negotiation information indicates a feature list comprising an identifier of a network node (121, 211, 212) , a feature supported by respective network node (121, 211, 212) , an operation mode of respective network node (121, 211, 212) .14.The method (500) according to any one of claims 1 to 4, wherein the one or more first discovery parameters do not comprise feature negotiation information; andthe one or more second discovery parameters comprise second feature negotiation information indicating that a second feature is supported by the first network node (211) .15.The method (500) according to claim 14, wherein the second feature negotiation information further indicates a value associated with the second feature.16.The method (500) according to any one of claims 1 to 4, wherein the one or more first discovery parameters comprise first feature negotiation information indicating that a first feature is supported by the second network node (121) ; andthe one or more second discovery parameters do not comprise second feature negotiation information, or the one or more second discovery parameters comprise second feature negotiation information indicating that the first feature is not supported by the first network node (211) .17.The method (500) according to claim 16, wherein first feature negotiation information further indicates a first value associated with the first feature; and the first value is removed by the first network node (211) .18.The method (500) according to any one of claims 1 to 17, wherein the discovery result comprises a time to live (TTL) value to indicate a valid time of the discovery result.19.The method (500) according to any one of claims 1 to 18, wherein the discovery result comprises one or more third parameters comprising third feature negotiation information from the third network node (131) .20.The method (500) according to any one of claims 1 to 19, further comprising:-transmitting a fourth message to the second network node (121) , the fourth message comprises the discovery result or a discovery result updated by the first network node (211) .21.The method (500) according to any one of claims 1 to 20, whereinthe first network node (211) implements a first intermediate network node between a network function (NF) service consumer and a Network Repository Function (NRF) for NF service discovery;the second network node (121) implements the NF service consumer or a second intermediate network node adjacent to the first intermediate network node; and / orthe third network node (131) implements the NRF or a third intermediate network node adjacent to the first intermediate network node.22.The method (500) according to any one of claims 1 to 21, wherein the first message and / or the second message are one of:-a discovery service request;-a NF status subscription request;-a NF status subscription notify;-a service request comprising discovery information.23.The method (500) according to any one of claims 1 to 22, wherein the first, second, or third intermediate network node is one of:-a Service Communication Proxy (SCP) ;-a NRF;-a NF other than NRF.24.The method (500) according to any one of claims 1 to 23, wherein the first, second, or third network node (121, 211, 131) is at serving network or at home network.25.The method (500) according to any one of claims 1 to 24, wherein at least one of the one or more first discovery parameters and the one or more second discovery parameters impact a form of NF candidates within the discovery result, a maximum size of the discovery result, or a maximum number of NF candidates within the discovery result.26.The method (500) according to claim 2, wherein a bit of the feature negotiation information indicates whether a feature impacting the discovery result is supported.27.The method (500) according to claim 26, wherein the bit indicates one of:-Service-Map;-Enh-NF-Discovery;-Allowed-ruleset;-DNN-List-Optimization;-Shared-Data.28.The method (500) according to claim 3, wherein a bit of the feature negotiation information indicates whether a feature impacting the discovery result is supported, and wherein a respective information element of the feature negotiation information indicates a value associated with a supported feature.29.A method (600) performed by a third network node (131) , comprising:-receiving a second message comprising one or more second discovery parameters from a first network node (211) , the one or more second discovery parameters are at least in part updated based on one or more first discovery parameters from a second network node (121) ; and-transmitting a third message comprising a discovery result to the first network node (211) ,wherein at least one of the one or more first discovery parameters and the one or more second discovery parameters impact the returned discovery result by the third network node (131) for a discovered NF.30.The method (600) according to claim 29, wherein the one or more first discovery parameters comprise first feature negotiation information indicating that a first feature is supported by the second network node (121) ; andthe one or more second discovery parameters comprise second feature negotiation information indicating that a first feature is supported by the second network node (121) and that a second feature is supported by the first network node (211) .31.The method (600) according to claim 30, wherein the first feature negotiation information further indicates a first value associated with the first feature; andthe second feature negotiation information further indicates the first value associated with the first feature and a second value associated with the second feature.32.The method (600) according to claim 30 or 31, wherein the first feature negotiation information further indicates an operation mode of the second network node (121) ; andwherein the second feature negotiation information further indicates an operation mode of the second network node (121) and an operation mode of the first network node (211) .33.The method (600) according to claim 32, wherein the operation mode comprises:-a transparent mode, in which the first or second feature does not impact the discovery result; or-an interception mode, in which it is possible that the first or second feature impacts the discovery result.34.The method (600) according to claim 33, wherein the first and / or second feature negotiation information indicates a feature list comprising identifier of a network node (121, 211, 212) , a feature supported by respective network node (121, 211, 212) , an operation mode of respective network node (121, 211, 212) .35.The method (600) according to claim 34, wherein the discovery result is generated based on one or more features supported by respective one or more network nodes (121, 211, 212) and one or more operation modes of respective one or more network nodes (121, 211, 212) .36.The method (600) according to any one of claims 29 to 35, wherein the discovery result comprises a time to live (TTL) value to indicate a valid time of the discovery result;the method (600) further comprising:-caching the discovery result during the valid time of the discovery result.37.A first network node (700) , comprising:-processing circuitry (701) ; and-a memory (702) ;wherein the processing circuitry (701) is configured to perform the method (500) according to any one of claims 1 to 28.38.A third network node (800) , comprising:-processing circuitry (801) ; and-a memory (802) ;wherein the processing circuitry (801) is configured to perform the method (600) according to any one of claims 29 to 36.39.A communication system (1000) , comprising:-a first network node (700) , comprising:-processing circuitry (701) ; and-a memory (702) ;wherein the processing circuitry (701) is configured to perform the method (500) according to any one of claims 1 to 28;-a second network node (1001) , comprising:-processing circuitry; and-a memory;wherein the processing circuitry is configured to transmit a first message comprising one or more first discovery parameters to the first network node (211) and receive the discovery result from the first network node (211) ; and-a third network node (800) , comprising:-processing circuitry (801) ; and-a memory (802) ;wherein the processing circuitry (801) is configured to perform the method (600) according to any one of claims 29 to 36.40.A computer readable medium (902) comprising instructions that, when executed by a network node (700, 800, 900) , cause the network node (700, 800, 900) to perform the method (500, 600) according to any one of claims 1 to 36.41.A computer readable product (904) comprising instructions that, when executed by a network node (700, 800, 900) , cause the network node (700, 800, 900) to perform the method (500, 600) according to any one of claims 1 to 36.
