Method and apparatus for network function discovery

Abstract

The embodiment of the invention provides a method and a device for NF (Network Function) discovery. A method performed by an NF may include sending a first NF discovery request including at least one query parameter to a first network repository function (NRF). The method may further include receiving a first NF discovery response from the first NRF. The first NF discovery response may include a search result and information indicating at least one neglected unsupported query parameter and / or at least one neglected supported query parameter of the at least one query parameter for the search result.

Description

Technical Field

[0001] The non-limiting and exemplary embodiments of this disclosure generally relate to the field of communication technology, and more particularly to methods and apparatus for network function (NF) discovery. Background Technology

[0002] This section introduces several aspects that can help in a better understanding of this disclosure. Therefore, the statements in this section should be read in this light and should not be construed as an admission of what is in or not in the prior art.

[0003] In networks such as fifth-generation core networks (5GC), NF service consumers can discover NF producer candidates via the Network Repository Function (NRF). To do this, NF consumers can send a discovery request to the NRF. This discovery request can include a set of discovery factors (i.e., query parameters) to filter one or more target NF producer candidates (such as NF type, service area, etc.), or provide its own information to allow the NRF to verify the NF service consumer's accessibility to the target NF producer. Summary of the Invention

[0004] The present invention is provided in a simplified form to introduce a chosen concept, which is further described in the following detailed description. This summary is neither intended to identify key or essential features of the claimed subject matter nor to limit the scope of the claimed subject matter.

[0005] When the NRF receives a discovery request that includes unsupported query parameters, it can choose to reject the request or return search / discovery results by ignoring the unsupported query parameters. However, both methods have significant drawbacks.

[0006] When an NRF ignores one or more unsupported query parameters and uses the remaining one or more query parameters to provide one or more NF producer candidates, the search / discovery results may not be usable by the NF consumer / NF service consumer if the ignored query parameters are essential to the service logic (e.g., for the Service Data Network Name (DNN) of a Session Management Function (SMF)). Whether the unsupported query parameters are critical to the service logic is unpredictable, and in fact, an NRF acting as a repository function should not always be aware of it.

[0007] When an NRF simply rejects a discovery request, the NF consumer may need to know in advance which query parameters the NRF supports to avoid discovery failure. In deployment, it's possible to align one or more supported query parameters through configuration within the NF consumer. Since any NF can potentially be an NF consumer, such configuration can already be challenging in the network. Furthermore, in Public Land Mobile Network (PLMN) scenarios, the configuration within the NF consumer can become completely unmanageable, where the NF consumer, either the visiting NRF (vNRF) or the home NRF (hNRF), needs to communicate with numerous partner PLMNs' NRFs, and these NRFs may each have different supported query parameters.

[0008] There should be a mechanism to help NRF understand how to handle one or more unsupported query parameters and / or help NF consumers understand how discovery results are generated.

[0009] To overcome or mitigate at least one of the above-mentioned or other problems, embodiments of this disclosure propose an improved solution for NF discovery.

[0010] In a first aspect of this disclosure, a method performed by a network function (NF) is provided. The method may include sending a first NF discovery request, including at least one query parameter, to a first network repository function (NRF). The method may further include receiving a first NF discovery response from the first NRF. The first NF discovery response may include search results and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among the at least one query parameter for the search results.

[0011] In an embodiment, the method may further include obtaining information about one or more query parameters supported by the first NRF. The method may further include determining one or more query parameters not supported by the first NRF. The at least one query parameter may include at least one of the one or more query parameters supported by the first NRF, and may not include one or more query parameters not supported by the first NRF.

[0012] In an embodiment, obtaining information about one or more query parameters supported by a first NRF may include sending a first bootstrapping request or a second NF discovery request to the first NRF and receiving a first bootstrapping response or a second NF discovery response from the first NRF that includes information about one or more query parameters supported by the first NRF.

[0013] In an embodiment, the method may further include obtaining information about one or more query parameters supported by a second NRF.

[0014] In an embodiment, the method may further include determining one or more query parameters that are not supported by a second NRF.

[0015] In an embodiment, when the first NF discovery request contains the network identifier of the second NRF, the at least one query parameter may include at least one of one or more query parameters supported by the second NRF, and may not include one or more query parameters not supported by the second NRF.

[0016] In an embodiment, obtaining information about one or more query parameters supported by the second NRF may include: sending a second bootstrapping request or a third NF discovery request to the first NRF, including the network identifier of the second NRF; and receiving a second bootstrapping response or a third NF discovery response from the first NRF, including information about one or more query parameters supported by the second NRF.

[0017] In an embodiment, the first NRF may include a visiting NRF, and the second NRF may include a home NRF.

[0018] In an embodiment, the first NRF may include the home NRF, and the second NRF may include the visit NRF.

[0019] In an embodiment, the method may further include: determining whether the search results are useful based on at least one ignored unsupported query parameter and / or at least one ignored supported query parameter.

[0020] In an embodiment, the first NF discovery request may further include first information indicating whether a query parameter in at least one query parameter is critical to the service logic.

[0021] In an embodiment, the first NF discovery response may include at least one of the following: a search result generated by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter in at least one query parameter, a rejection message and information indicating the reason why a critical query parameter in at least one query parameter is not supported, or a redirection message when a critical query parameter in at least one query parameter is not supported.

[0022] In an embodiment, the first information may include at least one of the following: a new query parameter containing a list of names of at least one key query parameter, a Hypertext Transfer Protocol (HTTP) header containing a list of names of at least one key query parameter, or a pattern or extension directly on the query parameter name indicating keyness.

[0023] In a second aspect of this disclosure, a method performed by a first NRF is provided. The method may include receiving a first NF discovery request from an NF containing at least one query parameter. The method may further include sending a first NF discovery response to the NF. The first NF discovery response may include search results and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among the at least one query parameter for the search results.

[0024] In an embodiment, at least one query parameter may include at least one of one or more query parameters supported by the first NRF, and may not include one or more query parameters not supported by the first NRF.

[0025] In an embodiment, the method may further include receiving a first bootstrapping request or a second NF discovery request from the NF. The method may further include sending a first bootstrapping response or a second NF discovery response to the NF, including information about one or more query parameters supported by a first NRF.

[0026] In an embodiment, when the first NF discovery request contains the network identifier of the second NRF, the at least one query parameter may include at least one of one or more query parameters supported by the second NRF, and may not include one or more query parameters not supported by the second NRF.

[0027] In an embodiment, the method may further include receiving a second bootstrapping request or a third NF discovery request from the NF, including a network identifier of the second NRF. The method may further include sending a third bootstrapping request or a fourth NF discovery request to the second NRF. The method may further include receiving a third bootstrapping response or a fourth NF discovery response from the second NRF, including information about one or more query parameters supported by the second NRF. The method may further include sending a second bootstrapping response or a third NF discovery response to the NF, including information about one or more query parameters supported by the second NRF.

[0028] In an embodiment, the first NRF may include a visiting NRF, and the second NRF may include a home NRF.

[0029] In an embodiment, the first NRF may include the home NRF, and the second NRF may include the visit NRF.

[0030] In an embodiment, the first NF discovery request may further include first information indicating whether a query parameter in at least one query parameter is critical to the service logic.

[0031] In an embodiment, the first NF discovery response may include a search result generated by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter among at least one query parameter, or a rejection message and reason information indicating that a critical query parameter among at least one query parameter is not supported, or a redirection message when a critical query parameter among at least one query parameter is not supported.

[0032] In an embodiment, the first information may include at least one of the following: a new query parameter containing a list of names of at least one key query parameter, an HTTP header containing a list of names of at least one key query parameter, or a pattern or extension directly on the query parameter name to indicate keyness.

[0033] In an embodiment, when the first NF discovery request contains the network identifier of the second NRF, the method may further include sending a fifth NF discovery request, including at least one query parameter, to the second NRF. The method may further include receiving a fifth NF discovery response from the second NRF.

[0034] In an embodiment, the fifth NF discovery response may include a search result and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among at least one query parameter for the search result.

[0035] In an embodiment, the fifth NF discovery request may further include first information indicating whether a query parameter in at least one query parameter is critical to the service logic.

[0036] In an embodiment, the fifth NF discovery response may include at least one of the following: a search result generated by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter in at least one query parameter, a rejection message and information indicating the reason why a critical query parameter in at least one query parameter is not supported, or a redirection message when a critical query parameter in at least one query parameter is not supported.

[0037] In an embodiment, when the first NF discovery request does not contain the network identifier of the second NRF, the method may further include at least one of the following: determining the search results by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter in at least one query parameter; or determining whether to reject or accept the first NF discovery request based on the criticality of the unsupported query parameter in at least one query parameter; or determining redirection information when the critical query parameter in at least one query parameter is not supported.

[0038] In a third aspect of this disclosure, a method performed by a second NRF is provided. The method may include receiving a fifth NF discovery request from a first NRF, including at least one query parameter. The method may further include sending a fifth NF discovery response to the first NRF. The method may further include determining search results by ignoring at least one non-critical, unsupported query parameter and / or at least one non-critical, supported query parameter among the at least one query parameter.

[0039] In an embodiment, at least one query parameter may include at least one of one or more query parameters supported by the second NRF, and may not include one or more query parameters not supported by the second NRF.

[0040] In an embodiment, the method may further include receiving a third bootstrapping request or a fourth NF discovery request from a first NRF. The method may further include sending a third bootstrapping response or a fourth NF discovery response to the first NRF, including information about one or more query parameters supported by a second NRF.

[0041] In an embodiment, the first NRF may include a visiting NRF, and the second NRF may include a home NRF.

[0042] In an embodiment, the first NRF may include the home NRF, and the second NRF may include the visit NRF.

[0043] In an embodiment, the fifth NF discovery response may include a search result and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among at least one query parameter for the search result.

[0044] In an embodiment, the fifth NF discovery request may further include first information indicating whether a query parameter in the at least one query parameter is critical to the service logic.

[0045] In an embodiment, the fifth NF discovery response may include at least one of the following: a search result generated by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter in the at least one query parameter, a rejection message and a reason message indicating that a critical query parameter in the at least one query parameter is not supported, or a redirection message when a critical query parameter in the at least one query parameter is not supported.

[0046] In an embodiment, the method may further include: at least one non-critical supported query parameter among at least one query parameter; or, determining whether to reject or accept the fifth NF discovery request based on the criticality of the unsupported query parameter among at least one query parameter; or, determining redirection information when the critical query parameter among at least one query parameter is not supported.

[0047] In a fourth aspect of this disclosure, an NF (Network Function) is provided. The NF may include a processor and memory coupled to the processor. The memory stores instructions executable by the processor. The NF is operable to send a first NF discovery request, including at least one query parameter, to a first Network Repository Function (NRF). The NF may further operate to receive a first NF discovery response from the first NRF. The first NF discovery response may include search results and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among the at least one query parameter for the search results.

[0048] In a fifth aspect of this disclosure, a first NRF is provided. The first NRF may include a processor and a memory coupled to the processor. The memory stores instructions executable by the processor. The first NRF is operable to receive a first NF discovery request from an NF including at least one query parameter. The first NRF is further operable to send a first NF discovery response to the NF. The first NF discovery response may include a search result and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among the at least one query parameter of the search result.

[0049] In a sixth aspect of this disclosure, a second NRF is provided. The second NRF may include a processor and memory coupled to the processor. The memory stores instructions executable by the processor. The second NRF is operable to receive a fifth NF discovery request from a first NRF, including at least one query parameter. The second NRF is further operable to send a fifth NF discovery response to the first NRF. The second NRF is further operable to determine search results by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter among the at least one query parameter.

[0050] In a seventh aspect of this disclosure, an NF is provided. The NF may include a first sending module configured to send a first NF discovery request, including at least one query parameter, to a first Network Repository Function (NRF). The NF may include a first receiving module configured to receive a first NF discovery response from the first NRF. The first NF discovery response may include a search result and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among the at least one query parameter for the search result.

[0051] In an embodiment, the NF may further include a first obtaining module configured to obtain information about one or more query parameters supported by the first NRF.

[0052] In an embodiment, the NF may further include a first determining module configured to determine one or more query parameters not supported by the first NRF. The at least one query parameter may include at least one of the one or more query parameters supported by the first NRF, and may not include one or more query parameters not supported by the first NRF.

[0053] In an embodiment, the NF may further include a second obtaining module configured to obtain information about one or more query parameters supported by the second NRF.

[0054] In an embodiment, the NF may further include a second determining module configured to determine one or more query parameters not supported by the second NRF. When the first NF discovers that the request contains the network identifier of the second NRF, the at least one query parameter may include at least one of the one or more query parameters supported by the second NRF, and may not include one or more query parameters not supported by the second NRF.

[0055] In an embodiment, the NF may further include a third determining module configured to determine whether the search results are useful based on at least one ignored unsupported query parameter and / or at least one ignored supported query parameter.

[0056] In an eighth aspect of this disclosure, a first NRF is provided. The first NRF may include a first receiving module configured to receive a first NF discovery request from the NF containing at least one query parameter. The first NRF may further include a first sending module configured to send a first NF discovery response to the NF. The first NF discovery response may include search results and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among the at least one query parameter for the search results.

[0057] In an embodiment, the first NRF may include a second receiving module configured to receive a first boot request or a second NF discovery request from the NF.

[0058] In an embodiment, the first NRF may further include a second sending module configured to send a first bootstrap response or a second NF discovery response to the NF, including information about one or more query parameters supported by the first NRF.

[0059] In an embodiment, the first NRF may further include a third receiving module configured to receive from the NF a second bootstrapping request or a third NF discovery request that includes the network identifier of the second NRF.

[0060] In an embodiment, the first NRF may further include a third sending module configured to send a third boot request or a fourth NF discovery request to the second NRF.

[0061] In an embodiment, the first NRF may further include a fourth receiving module configured to receive from the second NRF a third bootstrap response or a fourth NF discovery response including information about one or more query parameters supported by the second NRF.

[0062] In an embodiment, the first NRF may further include a fourth sending module configured to send a second bootstrap response or a third NF discovery response to the NF, including information about one or more query parameters supported by the second NRF.

[0063] In an embodiment, when the first NF discovery request includes the network identifier of the second NRF, the first NRF may further include a fifth sending module configured to send a fifth NF discovery request including at least one query parameter to the second NRF. The first NRF may further include a fifth receiving module configured to receive a fifth NF discovery response from the second NRF.

[0064] In an embodiment, when the first NF discovery request does not contain the network identifier of the second NRF, the first NRF may further include a first determining module configured to determine the search results by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter among at least one query parameter. The first NRF may further include a second determining module configured to determine whether to reject or accept the first NF discovery request based on the criticality of the unsupported query parameter among at least one query parameter. The first NRF may further include a first determining module configured to determine redirection information when a critical query parameter among at least one query parameter is not supported.

[0065] In a ninth aspect of this disclosure, a second NRF is provided. The second NRF may include a first receiving module configured to receive a fifth NF discovery request from the first NRF, including at least one query parameter. The second NRF may further include a first sending module configured to send a fifth NF discovery response to the first NRF. The second NRF may further include a first determining module configured to determine a search result by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter among the at least one query parameter.

[0066] In an embodiment, the second NRF may further include a second receiving module configured to receive a third bootstrapping request or a fourth NF discovery request from the first NRF. The second NRF may further include a second sending module configured to send a third bootstrapping response or a fourth NF discovery response to the first NRF, including information about one or more query parameters supported by the second NRF.

[0067] In an embodiment, the second NRF may further include a second determining module configured to determine whether to reject or accept the fifth NF discovery request based on the criticality of an unsupported query parameter in at least one query parameter.

[0068] In an embodiment, the second NRF may further include a third determining module configured to determine redirection information when a key query parameter in the at least one query parameter is not supported.

[0069] In a tenth aspect of this disclosure, a computer-readable storage medium is provided that stores instructions, when executed by at least one processor, causing the at least one processor to perform any method according to a first, second, or third aspect of this disclosure.

[0070] In the eleventh aspect of this disclosure, a computer program product including instructions is provided, which, when executed by at least one processor, cause the at least one processor to perform any method according to the first, second, or third aspect of this disclosure.

[0071] Many advantages can be achieved by applying the solutions proposed according to embodiments of this disclosure. In some embodiments herein, it can provide a coordinated approach for NRF and NF consumers to perform NF discovery. In some embodiments herein, it can eliminate ambiguity in the behavior of the NRF in processing the request and the NF consumer in processing the search results when the query parameters provided by the NF consumer may not be supported by the NRF. In some embodiments herein, it can avoid network traffic waste and negative KPIs caused by service request rejection. The embodiments herein are not limited to the features and advantages described above. Additional features and advantages will be recognized by those skilled in the art upon reading the following detailed description. Attached Figure Description

[0072] From the following detailed description with reference to the accompanying drawings, by way of example, the above and other aspects, features, and benefits of various embodiments of the present disclosure will become more fully apparent, in which similar reference numerals or letters are used to refer to similar or equivalent elements. The drawings are shown to facilitate a better understanding of embodiments of the present disclosure and are not necessarily drawn to scale, wherein:

[0073] Figure 1a An advanced architecture in a fifth-generation network according to an embodiment of the present disclosure is illustrated schematically.

[0074] Figure 1b This illustration schematically depicts a 5G system roaming architecture with a service-based interface in a home routing scenario within the control plane, according to embodiments of the present disclosure.

[0075] Figure 1c An NRF roaming architecture in a reference point representation is schematically illustrated according to an embodiment of the present disclosure;

[0076] Figure 1d The service discovery flowchart within the same PLMN is shown.

[0077] Figure 1e The service discovery flowchart is shown in different PLMNs;

[0078] Figure 2a A flowchart of a method according to an embodiment of the present disclosure is shown;

[0079] Figure 2b A flowchart of a method according to another embodiment of the present disclosure is shown;

[0080] Figure 2c A flowchart of a method according to another embodiment of the present disclosure is shown;

[0081] Figure 2d A flowchart of a method according to another embodiment of the present disclosure is shown;

[0082] Figure 2e A flowchart of a method according to another embodiment of the present disclosure is shown;

[0083] Figure 2f A flowchart of a method according to another embodiment of the present disclosure is shown;

[0084] Figure 2g A flowchart of a method according to another embodiment of the present disclosure is shown;

[0085] Figure 3a A flowchart of a method according to another embodiment of the present disclosure is shown;

[0086] Figure 3b A flowchart of a method according to another embodiment of this disclosure is shown;

[0087] Figure 3c A flowchart of a method according to another embodiment of this disclosure is shown;

[0088] Figure 3d A flowchart of a method according to another embodiment of this disclosure is shown;

[0089] Figure 3e A flowchart of a method according to another embodiment of this disclosure is shown;

[0090] Figure 4a A flowchart of a method according to another embodiment of this disclosure is shown;

[0091] Figure 4b A flowchart of a method according to another embodiment of this disclosure is shown;

[0092] Figure 4c A flowchart of a method according to another embodiment of this disclosure is shown;

[0093] Figure 5a A flowchart of solution 1.1 according to an embodiment of the present disclosure is shown;

[0094] Figure 5b A flowchart of solution 1.2 according to an embodiment of the present disclosure is shown;

[0095] Figure 6 A flowchart of solution 2 according to an embodiment of the present disclosure is shown;

[0096] Figure 7a A flowchart of solution 3 according to another embodiment of this disclosure is shown;

[0097] Figure 7b A flowchart of solution 3 according to another embodiment of this disclosure is shown;

[0098] Figure 7c A flowchart of solution 3 according to another embodiment of this disclosure is shown;

[0099] Figure 8a This is a block diagram illustrating an apparatus suitable for practicing some embodiments of the present disclosure;

[0100] Figure 8b This is a block diagram illustrating an NF according to an embodiment of the present disclosure;

[0101] Figure 8c This is a block diagram illustrating a first NRF according to an embodiment of the present disclosure;

[0102] Figure 8d This is a block diagram illustrating a second NRF according to an embodiment of the present disclosure;

[0103] Figure 9 An example of a communication system according to an embodiment of the present disclosure is shown;

[0104] Figure 10 A UE according to some embodiments is shown;

[0105] Figure 11 A network node according to some embodiments is shown;

[0106] Figure 12 This is a block diagram illustrating a host according to an embodiment of the present disclosure;

[0107] Figure 13 This is a block diagram illustrating a virtualization environment in which the functionality implemented in some embodiments can be virtualized; and

[0108] Figure 14 A communication diagram is shown in which a host communicates with a UE via a network node through a partial wireless connection according to an embodiment of the present disclosure. Detailed Implementation

[0109] Embodiments of this 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 in the art to better understand and thus implement this disclosure, and not to suggest any limitation on the scope of this disclosure. References to features, advantages, or similar language throughout this specification do not imply that all features and advantages achievable with this disclosure should be present in or in any single embodiment of this disclosure. Rather, references to features and advantages should be understood as meaning that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of this disclosure. Furthermore, in one or more embodiments, the features, advantages, and characteristics described in this disclosure may be combined in any suitable manner. Those skilled in the art will recognize that this disclosure can be practiced without one or more specific features or advantages in a particular embodiment. In other instances, additional features and advantages may be recognized in some embodiments, and these additional features and advantages may not be present in all embodiments of this disclosure.

[0110] As used herein, the term "network" refers to a network that conforms to any suitable communication standard, 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 Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and other wireless networks. CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA). UTRA includes other variants of WCDMA and CDMA. TDMA networks can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies 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 networks, wireless sensor networks, etc. In the following description, the terms "network" and "system" are used interchangeably. Furthermore, communication between two devices in a network can be performed according to any suitable communication protocol, including but not limited to those defined by standards organizations such as 3GPP. For example, communication protocols may include first-generation (1G), 2G, 3G, 4G, 4.5G, 5G, 6G communication protocols and / or any other currently known or future-developed protocols.

[0111] The terms "network device," "network node," or "network function" refer to any suitable function that can be implemented in a (physical or virtual) network entity within a communication network. For example, a network function can be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on a suitable platform, such as cloud infrastructure. For instance, a 5G system (5GS) can include multiple NFs, such as Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Service Function (AUSF), Unified Data Management (UDM), Policy Control Function (PCF), Application Function (AF), Network Open Function (NEF), User Plane Function (UPF), and Network Repository Function (NRF), Radio Access Network (RAN), Serving Communication Agent (SCP), Network Data Analysis Function (NWDAF), Network Slice Selection Function (NSSF), Network Slice Specific Authentication and Authorization Function (NSSAAF), and so on. For example, a 4G system (such as LTE (Long Term Evolution)) may include a Mobility Management Entity (MME), Home Subscriber Server (HSS), PCRF (Policy and Charging Rules Function), Packet Data Network Gateway (PGW), PGW Control Plane (PGW-C), Serving Gateway (SGW), SGW Control Plane (SGW-C), E-UTRAN Node B (eNB), etc. In other embodiments, depending on the specific network, network functions may include different types of NFs.

[0112] The term "terminal device" refers to any terminal device that can access a communication network and receive services from it. By way of example and not limitation, a terminal device refers to a mobile terminal, user equipment (UE), or other suitable device. A UE can be, for example, a subscriber station (SS), a portable subscriber station, a mobile station (MS), or an access terminal (AT). Terminal devices can include, but are not limited to, portable computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable devices, personal digital assistants (PDAs), portable computers, desktop computers, wearable terminal devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEE), laptop installed devices (LME), USB dongles, smart devices, wireless customer premises equipment (CPE), etc. In the following description, the terms "terminal device," "terminal," "user equipment," and "UE" are used interchangeably. As an example, a terminal device may represent a UE configured to communicate according to one or more communication standards published by 3GPP (3rd Generation Partnership Project), such as 3GPP's LTE or NR standards. As used herein, a "User Equipment" or "UE" may not necessarily have a "user" in relation to a human user who owns and / or operates the associated device. In some embodiments, a terminal device may be configured to send and / or receive information without direct human interaction. For example, when triggered by an internal or external event, or in response to a request from a communication network, a terminal device may be designed to send information to the network according to a predetermined schedule. Alternatively, a UE may represent a device intended for sale to a human user or operated by a human user but which may not initially be associated with a particular human user.

[0113] As another example, in the Internet of Things (IoT) scenario, a terminal device can represent a machine or other device that performs monitoring and / or measurement, and transmits the results of such monitoring and / or measurement to another terminal device and / or network device. In this case, the terminal device can be a machine-to-machine (M2M) device, which in the 3GPP context can be referred to as a machine-type communication (MTC) device. As a specific example, a terminal device can be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (e.g., electricity meters), industrial machinery, or household or personal appliances such as refrigerators, televisions, personal wearable devices (e.g., watches), etc. In other scenarios, a terminal device can represent a vehicle or other device capable of monitoring and / or reporting its operating status or other functions related to its operation.

[0114] References to "an embodiment," "embodiment," "exemplary embodiment," etc., in the specification indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is claimed that, whether explicitly described or not, its influence in conjunction with other embodiments is within the knowledge of those skilled in the art.

[0115] It should be understood that while the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed terms.

[0116] As used herein, the phrase “at least one of A and B” or “at least one of A or B” should be understood as “A only, B only, or both A and B”. The phrase “A and / or B” should be understood as “A only, B only, or both A and B”.

[0117] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” as used herein are also intended to include the plural forms. It will be further understood that, as used herein, the terms “comprising,” “including,” “having,” “owning,” “containing,” and / or “covering” specify the presence of the stated features, elements, and / or components, but do not include the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0118] Note that the terms used in this article are for ease of description and to distinguish between nodes, devices, or networks, etc. As technology evolves, other terms with similar / identical meanings may also be used.

[0119] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0120] Although the subjects described herein can be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are related to conforming to... Figures 1a-1c The communication system described is based on the exemplary system architecture shown. For simplicity, Figures 1a-1c The system architecture described herein only depicts a few exemplary elements. In practice, a communication system may further include any additional elements suitable for supporting communication between terminal devices or between a wireless device and another communication device (such as a landline telephone, service provider, or any other network node or terminal device). The communication system may provide communication and various types of services to one or more terminal devices to facilitate their access to and / or use of services provided by or via the communication system.

[0121] Figure 1a An advanced architecture in a fifth-generation network according to an embodiment of the present disclosure is illustrated schematically. Figure 1a The architecture is the same as that in Figure 4.2.3-1 of 3GPP TS 23.501 V18.0.0, and the public information of 3GPP TS 23.501 V18.0.0 is incorporated herein by reference in its entirety. Figure 1a The system architecture may include some exemplary elements such as AUSF, AMF, DN (Data Network), NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R)AN, SCP (Service Communication Agent), NSSAAF (Network Slice Specific Authentication and Authorization Function), NSACF (Network Slice Admission Control Function), Edge Application Server Discovery Function (EASDF), etc.

[0122] According to an exemplary embodiment, the UE can establish a signaling connection with the AMF through reference point N1, such as... Figure 1a As shown in the diagram. This signaling connection enables NAS (Non-Access Stratum) signaling exchange between the UE and the core network, including the signaling connection between the UE and the (R)AN, and the N2 connection for the UE between the (R)AN and the AMF. The (R)AN can communicate with the UPF via reference point N3. The UE can establish a Protocol Data Unit (PDU) session with the DN (Data Network, e.g., Operator Network or Internet) via reference point N6 through the UPF.

[0123] like Figure 1a The exemplary system architecture further illustrated also includes service-based interfaces presented by NFs (such as NRF, NEF, AUSF, UDM, PCF, AMF, NSACF, EASDF, and SMF), such as Nnrf, Nnef, Nausf, Nudm, Npcf, Namf, Nnsacf, Neasdf, and Nsmf. Furthermore, Figure 1aReference points, such as N1, N2, N3, N4, N6, and N9, are also shown, which can support interaction between NF services within an NF. For example, these reference points can be implemented through corresponding NF service-based interfaces, and by specifying NF service consumers and providers and their interactions to execute specific system processes.

[0124] Figure 1b This illustration schematically depicts a 5G system roaming architecture with a service-based interface in a home routing scenario within the control plane, according to embodiments of the present disclosure. Figure 1b Its architecture is the same as Figure 4.2.4-3 of 3GPP TS 23.501 V18.0.0.

[0125] SCPs can be used for indirect communication between NF and NF services within a VPLMN (Visiting PLMN), an HPLMN (Home PLMN), or both a VPLMN and an HPLMN. For simplicity, SCPs are not shown in this roaming architecture.

[0126] The Secure Edge Protection Proxy (SEPP) is a non-transparent proxy and supports the following features:

[0127] - Message filtering and policy enforcement on the control plane interface between PLMNs.

[0128] SEPP protects the connection between service consumers and service providers from a security perspective. That is, SEPP will not duplicate the service licenses applied by the service provider, as specified in Clause 7.1.4 of 3GPP TS 23.501 V18.0.0.

[0129] - Topology hiding.

[0130] The detailed functions, related procedures, and N32 reference points of SEPP are specified in 3GPP TS 33.501 V18.1.0, the contents of which are incorporated herein by reference in their entirety.

[0131] Figure 1c An NRF roaming architecture, represented by a reference point, is schematically illustrated according to an embodiment of the present disclosure. Figure 1c Its architecture is the same as that in Figure 4.2.4-7 of 3GPP TS 23.501 V18.0.0.

[0132] For the roaming scenario described above, each PLMN implements a proxy function to ensure interconnection security and hide the topology on the interface between PLMNs.

[0133] For clarity, Figure 1c SEPPs on both sides of the PLMN boundary are not depicted.

[0134] The 5G system architecture includes the following reference points:

[0135] N1: Reference point between UE and AMF.

[0136] N2: (R) The reference point between AN and AMF.

[0137] N3: (R) Reference point between AN and UPF.

[0138] N4: Reference point between SMF and UPF.

[0139] N6: Reference point between UPF and data network.

[0140] N9: Reference point between the two UPFs.

[0141] N27: The reference point between the NRF in the visited network and the NRF in the home network.

[0142] N32: A reference point between a SEPP in one PLMN or SNPN and a SEPP in another PLMN or SNPN; or a reference point between a SEPP in an SNPN (Standalone Non-Public Network) and a SEPP in a CH (Certificate Holder) / DCS (Conditional Switching), where the CH / DCS includes a UDM / AUSF.

[0143] Figure 1d A flowchart of service discovery in the same PLMN is shown, which is identical to Figure 5.3.2.2.2-1 in 3GPP 29.510 V18.2.0, the disclosure of which is incorporated herein by reference in its entirety.

[0144] Clause 5.3.2.2.2 in 3GPP 29.510 V18.2.0 describes Figure 1d The steps are as follows.

[0145] This service operation is performed by querying the "nf-instances" resource. The request will be sent to the NRF in the same PLMN as the NF service consumer.

[0146] 1. NF service consumers should send an HTTP GET request to the resource collection resource with the resource URI "nf-instances". The input filter criteria for this discovery request should be included in the query parameters.

[0147] An SCP can request to discover the full profile (including, for example, authorization attributes) of an NF instance that matches the query parameters. Upon receiving such a request, the NRF should verify whether the requesting entity is authorized to discover the full profile of the NF instance based on local policies or an access token received granting such permission. If the requesting entity is not authorized to do so, the NRF should reject the request or treat it as a service discovery request that cannot access the full profile.

[0148] 2a. On success, a "200 Success" response should be returned. The response body should include a validity period (during which the NF service consumer can cache search results), an array of NF profile objects, and / or a mapping of NFInstanceInfo objects for NF instances that meet the search filter criteria (if the NF service consumer indicates support for the Enh-NF-Discovery feature in the request) (e.g., all NF instances providing a specific NF service name in the "Registered" state, or an empty array if the search filter criteria do not match NF instances in the "Registered" state). In the latter case, the response may include a noProfileMatchInfo attribute to provide a specific reason why no NF instances matching the search filter criteria were found.

[0149] 2b. In case of failure or redirection:

[0150] - If an NF service consumer is not allowed to discover NF services for the requested NF type provided in the query parameters, the NRF should return a "403 Forbidden" response.

[0151] - If the discovery request fails at the NRF due to an error in the input data in the URI query parameters, the NRF should return a "400 Error Request" status code with a Problem Details IE that provides details of the error.

[0152] - If a discovery request fails at the NRF due to an internal NRF error, the NRF should return a "500 Internal Server Error" status code with ProblemDetails providing details of the error.

[0153] In the case of a redirect, NRF should return a 3xx status code that includes a location header with a URI pointing to an endpoint of another NRF service instance.

[0154] The NF profile object returned in a successful result should contain general data for each NF instance, applicable to any NF type, and may also contain NF-specific data for NF instances belonging to a specific type (e.g., when the NF instance's type is "UDR", the NF profile typically contains the attribute "udrInfo"). Additionally, for NF instances with custom NF types, the NF profile may contain the attribute "customInfo".

[0155] For those NF instances, the "customInfo" attribute (if available) should be returned by NRF as part of the NF profile returned in the discovery response.

[0156] The NRF should also include in the returned NF profile object any provider-specific attributes that may have already been provided by the registered NF instance (see 3GPP TS 29.500 [4], Clause 6.6.3).

[0157] If the response contains a mapping of an NFInstanceInfo object for an NF instance, the NF service consumer can retrieve an NF profile by issuing a service discovery request with a target-nf-instance-id parameter that identifies the target NF instance ID, or a target-nf-instance-id-list parameter that identifies a list of target NF instance IDs held by the same NRF. If an nrfDiscApiUri attribute is received in the NFInstanceInfo object, and if the service discovery request is addressed to a different NRF than the one holding one or more NF profiles, the service discovery request should also include an nrf-disc-uri parameter set to the API URI of the Nnrf_NFDiscovery service of the NRF holding one or more NF profiles.

[0158] Figure 1e The flowchart of service discovery in different PLMNs is shown, which is the same as Figure 5.3.2.2.3-1 of 3GPP 29.510 V18.2.0.

[0159] Clause 5.3.2.2.3 in 3GPP 29.510 V18.2.0 describes Figure 1e The steps are as follows.

[0160] Service discovery in different PLMNs is accomplished by querying the "nf-instances" resource in the NRF of the home PLMN.

[0161] To do this, perform step 1 in section 5.3.2.2.2 of 3GPP 29.510 V18.2.0 (send a GET request to the NRF in the serving PLMN); the request should include the identifier of the PLMN belonging to the NRF in the query parameters of the URI.

[0162] If the NRF in the serving PLMN knows that the NF discovery service for accessing the NRF in the home PLMN requires authorization based on Oauth2 (e.g., by learning this in an earlier boot process or local configuration), and if the request received by the NRF in the serving PLMN does not contain an access token, the NRF in the serving PLMN may refuse the request using a 401 Unauthorized condition as specified in Clause 6.7.3 of 3GPP TS 29.500 [4].

[0163] Then, steps 1-2 of 3GPP 29.510 V18.2.0 Figure 5.3.2.2.3-1 are executed between the NRF in the serving PLMN and the NRF in the home PLMN. In this step, the presence of the home NRF's PLMN ID in the query parameters of the URI is not required. The home PLMN's NRF will return a status code with the operation result. The serving PLMN's NRF should be configured with:

[0164] - If TLS protection between the NRF and SEPP in the serving PLMN relies on the use of a telescopic FQDN, then the telescopic FQDN of the NRF in the home PLMN (see 3GPP TS 23.003

[12] and 3GPP TS 29.500 [4]); or

[0165] Note: This is required by the NRF in the service PLMN to route the NF discovery request to the NRF in the HPLMN via the SEPP in the service PLMN, and the SEPP needs to terminate the TLS connection with a wildcard certificate.

[0166] - If TLS protection between the NRF and SEPP in the service PLMN relies on the use of the 3gpp-Sbi-Target-apiRoot header, the FQDN of the SEPP is configured (or, if communication between the NRF and SEPP is through the SCP, the FQDN of the SCP is configured).

[0167] See section 6.1.4.3 of 3GPP TS 29.500 [4].

[0168] Finally, perform step 2 in Clause 5.3.2.2.2 of 3GPP 29.510 V18.2.0; based on the result received from the NRF in the home PLMN, return a status code to the NF service consumer in the serving PLMN.

[0169] Steps 1 and 2 are similar to steps 1 and 2 in Figure 5.3.2.2.2-1 of 3GPP 29.510 V18.2.0, where the initiator of the service call is the NRF in the service PLMN and the receiver of the service call is the NRF in the home PLMN.

[0170] In practice, NF consumers may provide specific query parameters that the NRF does not support. For example, the NF consumer may have implemented a newer version of the 3GPP specification than the NRF, or the NRF may selectively implement some query parameters instead of all. In the latter case, even feature negotiation is useless. As specified in 3GPP 29.510 V18.2.0, the NRF only sets the feature bit when all query parameters controlled by that feature are supported.

[0171] According to 3GPP TS 29.500 V18.1.0 (the contents of which are incorporated herein by reference in their entirety), there are two options that NRF can take when receiving unsupported query parameters.

[0172] Section 5.2.9 of 3GPP TS 29.500 V18.1.0 describes the handling of unsupported query parameters, as shown below.

[0173] Unless otherwise specified by the application programming interface (API), an NF service provider that receives an HTTP request containing one or more unsupported (i.e., ununderstood) query parameters should:

[0174] a) For secure HTTP methods (such as HTTP GET requests):

[0175] - Ignore unsupported query parameters and respond to the request based on the rest of the request (such as other supported query parameters); or

[0176] - For insecure HTTP methods, reject HTTP requests according to the following rules, such as based on other query parameters in the request or based on the response becoming very large;

[0177] When the NRF receives an unsupported query parameter, it can choose to reject the request or return the search results by ignoring the unsupported query parameter (as specified in 3GPP TS 29.500 V18.1.0), but either way, there are obvious drawbacks as described above.

[0178] There should be a mechanism to help NRF understand how to handle one or more unsupported query parameters and / or help NF consumers understand how discovery results are generated.

[0179] To overcome or mitigate at least one of the above-mentioned or other problems, embodiments of this disclosure propose an improved solution for NF discovery.

[0180] Figure 2a A flowchart of a method according to an embodiment of the present disclosure is shown, which can be performed by means implemented in a network function (NF), or means implemented as an NF, or means communicatively coupled to an NF. Therefore, the means can provide components for implementing various parts of method 200, as well as components for combining with other components to implement other processes.

[0181] At box 202, the NF can send a first NF discovery request to the first network repository function (NRF), which includes at least one query parameter.

[0182] The NF can be any suitable node, entity, or function as described in various 3GPP specifications, such as 3GPP TS 23.501 V18.0.0, 3GPP TS 29.500 V18.1.0, 3GPP 29.510 V18.2.0, 3GPP TS23.502 V18.0.0, etc.

[0183] In the embodiments, the NF can be, for example, an NF service consumer or NF consumer as described in various 3GPP specifications, such as 3GPP TS 23.501 V18.0.0, 3GPP TS 29.500 V18.1.0, 3GPP 29.510 V18.2.0, 3GPP TS 23.502 V18.0.0, 3GPP TS 23.502 V18.0.0, etc.

[0184] The first NRF can be any suitable node, entity, or function capable of implementing network repository functionality. In embodiments, the first NRF can be the NRF described in 3GPP TS 23.501 V18.0.0, 3GPP TS 29.500 V18.1.0, 3GPP 29.510 V18.2.0, 3GPP TS 23.502 V18.0.0, etc.

[0185] In an embodiment, the NF discovery service may allow NF or SCP instances to discover other NF instances with potential services offered by them, or to discover SEPP instances in the same PLMN, by querying the local NRF.

[0186] In this embodiment, the NF discovery service can allow SCPs to discover other SCP instances.

[0187] In an embodiment, the NF discovery service may allow an NF or SCP to discover a list of NRF instances that are part of an NRF set. For each NRF instance, if the NRF is part of an NRF set, the list contains its NRF instance ID and addressing information.

[0188] In an embodiment, the NF discovery service may allow an NRF in a PLMN to reissue a discovery request to an NRF in another PLMN (e.g., an HPLMMN of a specific user equipment (UE)).

[0189] The first NF discovery request can be an existing message or a new message. In an embodiment, the first NF discovery request can be, for example, Nnrf_NFDiscovery_Request as described in 3GPP TS 23.502 V18.0.0 or an HTTP GET request as described in Clause 5.3.2.2 of 3GPP 29.510 V18.2.0.

[0190] The at least one query parameter can be any suitable query parameter, such as an existing query parameter or a new query parameter. In an embodiment, the at least one query parameter may include any query parameter as described in Clause 5.2.7.3.2 of 3GPP TS 23.502 V18.0.0, or any query parameter as described in Clause 6.2.3.2.3.1 of 3GPP 29.510 V18.2.0.

[0191] In an embodiment, the at least one query parameter may include at least one of one or more query parameters supported by the first NRF, and may not include one or more query parameters not supported by the first NRF.

[0192] In an embodiment, when the first NF discovery request contains the network identifier of the second NRF, the at least one query parameter may include at least one of one or more query parameters supported by the second NRF, and may not include one or more query parameters not supported by the second NRF.

[0193] At box 204, the NF can receive a first NF discovery response from the first NRF.

[0194] The first NF discovery response can be an existing message or a new message. In an embodiment, the first NF discovery response can be, for example, an Nnrf_NFDiscovery_Request response as described in 3GPP TS 23.502 V18.0.0, or an HTTP GET response as described in Clause 5.3.2.2 of 3GPP 29.510 V18.2.0.

[0195] In an embodiment, the first NF discovery response may include search results and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among at least one query parameter for the search results.

[0196] Figure 2b A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by means implemented in an NF, or by means implemented as an NF, or by means communicatively coupled to an NF. Therefore, the means can provide components for implementing various parts of method 210, as well as components for combining with other components to implement other processes. For the parts already described in the above embodiments, their description is omitted here for brevity.

[0197] In step 212, the NF can obtain information about one or more query parameters supported by the first NRF.

[0198] The NF can obtain information about one or more query parameters supported by the first NRF in a variety of ways, and this disclosure is not limited thereto. For example, the NF can obtain such information from other network devices or the first NRF. Such information can be configured in the NF.

[0199] For example, when an NF obtains information about one or more query parameters supported by a first NRF from a first NRF, that information can be included in any appropriate message, such as an NF discovery request or an NF discovery response (e.g., a failed NF discovery or a successful NF discovery).

[0200] At box 214, NF can determine one or more query parameters that are not supported by the first NRF.

[0201] An NF can determine one or more query parameters that are not supported by a first NRF in a variety of ways, and this disclosure is not limited in this regard. For example, an NF can obtain such information from another network device or the first NRF. Such information can be configured in the NF.

[0202] In an embodiment, the NF can determine one or more query parameters that are not supported by the first NRF based on information about one or more query parameters supported by the first NRF.

[0203] In an embodiment, at least one query parameter included in the first NF discovery request may include at least one of one or more query parameters supported by the first NRF, and may not include one or more query parameters not supported by the first NRF.

[0204] Figure 2c A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by means implemented in an NF, or by means implemented as an NF, or by means communicatively coupled to an NF. Therefore, the means can provide components for implementing various parts of method 220, as well as components for combining with other components to implement other processes. For the parts already described in the above embodiments, their description is omitted here for brevity.

[0205] At box 222, the NF can send a first boot request or a second NF discovery request to the first NRF.

[0206] The second NF discovery request can be an existing message or a new message. In an embodiment, the second NF discovery request can be, for example, Nnrf_NFDiscovery_Request as described in 3GPP TS 23.502 V18.0.0 or an HTTP GET request as described in Clause 5.3.2.2 of 3GPP 29.510 V18.2.0.

[0207] NRF can provide a bootstrapping service that allows NRF service consumers to know the NRF-supported service endpoints, NRF instance IDs (identifiers), and NRF set IDs (if the NRF is part of an NRF set) by using version-independent URI (Uniform Resource Identifier) ​​endpoints (without having to discover the version-independent URI endpoints using a discovery service).

[0208] When there is no pre-configured information indicating the version of the service deployed in PLMN-B, the bootstrapping service can be used in inter-PLMN scenarios where the NRF in PLMN-A needs to call the service from the NRF in PLMN-B.

[0209] The bootstrapping service can also be used in PLMN scenarios to avoid statically configuring information about the service version deployed in the NRF that will be used by different NFs.

[0210] The first bootstrapping request can be an existing message or a new message. In an embodiment, the first bootstrapping request can be, for example, an Nnrf_Bootstrapping_Get request as described in 3GPP TS 23.502 V18.0.0, or an HTTP GET request as described in Clause 5.5.2.2 of 3GPP 29.510 V18.2.0.

[0211] At box 224, the NF can receive a first bootstrap response or a second NF discovery response from the first NRF, which includes information about one or more query parameters supported by the first NRF.

[0212] In an embodiment, the first bootstrap response or the second NF discovery response may include information about one or more query parameters supported by the first NRF and / or information about one or more query parameters not supported by the first NRF.

[0213] The second NF discovery response can be an existing message or a new message. In an embodiment, the second NF discovery response can be, for example, an Nnrf_NFDiscovery_Request response as described in 3GPP TS 23.502 V18.0.0 or an HTTP GET response as described in Clause 5.3.2.2 of 3GPP 29.510 V18.2.0.

[0214] The first bootstrapping response can be an existing message or a new message. In an embodiment, the first bootstrapping response can be, for example, an Nnrf_Bootstrapping_Get response as described in 3GPP TS 23.502 V18.0.0, or an HTTP GET response as described in Clause 5.5.2.2 of 3GPP 29.510 V18.2.0.

[0215] Figure 2d A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by means implemented in an NF, or by means implemented as an NF, or by means communicatively coupled to an NF. Therefore, the means can provide components for implementing various parts of method 230, as well as components for combining with other components to implement other processes. For the parts already described in the above embodiments, their description is omitted here for brevity.

[0216] At box 232, the NF can obtain information about one or more query parameters supported by the second NRF.

[0217] An NF can obtain information about one or more query parameters supported by a second NRF in a variety of ways, and this disclosure makes no limitation thereto. For example, an NF can obtain such information from another network device or a second NRF. Such information can be configured within the NF.

[0218] For example, when an NF obtains information about one or more query parameters supported by a second NRF from a second NRF, such information can be included in any appropriate message, such as an NF discovery request or an NF discovery response, such as a failed NF discovery or a successful NF discovery.

[0219] At box 234, NF can determine one or more query parameters that are not supported by the second NRF.

[0220] An NF can determine one or more query parameters that are not supported by a second NRF in a variety of ways, and this disclosure does not limit this. For example, an NF can obtain such information from other network devices or a second NRF. Such information can be configured in the NF.

[0221] In an embodiment, the NF can determine one or more query parameters that are not supported by the second NRF based on information about one or more query parameters supported by the second NRF.

[0222] In an embodiment, when the first NF discovery request contains the network identifier of the second NRF, the at least one query parameter may include at least one of one or more query parameters supported by the second NRF, and may not include one or more query parameters not supported by the second NRF.

[0223] Figure 2e A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by means implemented in an NF, or by means implemented as an NF, or by means communicatively coupled to an NF. Therefore, the means can provide components for implementing various parts of method 240, as well as components for combining with other components to implement other processes. For the parts already described in the above embodiments, their description is omitted here for brevity.

[0224] At box 242, the NF can send a second boot request or a third NF discovery request to the first NRF, which includes the network identifier of the second NRF.

[0225] The network identifier of the second NRF can be any identifier, such as the PLMN identifier of the second NRF (e.g., the home NRF).

[0226] The third NF discovery request can be an existing message or a new message. In an embodiment, the third NF discovery request can be, for example, Nnrf_NFDiscovery_Request as described in 3GPP TS 23.502 V18.0.0, or an HTTP GET request as described in Clause 5.3.2.2 of 3GPP 29.510 V18.2.0.

[0227] The second bootstrapping request can be an existing message or a new message. In an embodiment, the second bootstrapping request can be, for example, an Nnrf_Bootstrapping_Get request as described in 3GPP TS 23.502 V18.0.0, or an HTTP GET request as described in Clause 5.5.2.2 of 3GPP 29.510 V18.2.0.

[0228] At box 244, the NF can receive a second bootstrap response or a third NF discovery response from the first NRF, which includes information about one or more query parameters supported by the second NRF.

[0229] In an embodiment, the second bootstrap response or the third NF discovery response may include information about one or more query parameters supported by the second NRF and / or information about one or more query parameters not supported by the second NRF.

[0230] The third NF discovery response can be an existing message or a new message. In an embodiment, the third NF discovery response can be, for example, an Nnrf_NFDiscovery_Request response as described in 3GPP TS 23.502 V18.0.0 or an HTTP GET response as described in Clause 5.3.2.2 of 3GPP 29.510 V18.2.0.

[0231] The second bootstrapping response can be an existing message or a new message. In an embodiment, the second bootstrapping response can be, for example, an Nnrf_Bootstrapping_Get response as described in 3GPP TS 23.502 V18.0.0, or an HTTP GET response as described in Clause 5.5.2.2 of 3GPP 29.510 V18.2.0.

[0232] In an embodiment, the first NRF may include an NRF in a first network, a first service area, or a first network slice, and the second NRF may include an NRF in a second network, a second service area, or a second network slice.

[0233] In an embodiment, the first NRF may include a visiting NRF, and the second NRF may include a home NRF.

[0234] In an embodiment, the first NRF may include the home NRF, and the second NRF may include the visit NRF.

[0235] Figure 2f A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by means implemented in an NF, or by means implemented as an NF, or by means communicatively coupled to an NF. Therefore, the means can provide components for implementing various parts of method 250, as well as components for combining with other components to implement other processes. For the parts already described in the above embodiments, their description is omitted here for brevity.

[0236] At box 252, the NF may send a first NF discovery request to the first NRF, including at least one query parameter.

[0237] At box 254, the NF can receive a first NF discovery response from the first NRF.

[0238] In an embodiment, the first NF discovery response may include search results and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among at least one query parameter for the search results.

[0239] For example, search results can be generated by ignoring at least one unsupported query parameter and / or at least one supported query parameter.

[0240] At box 256, NF can determine whether a search result is useful based on at least one ignored unsupported query parameter and / or at least one ignored supported query parameter.

[0241] For example, if at least one ignored unsupported query parameter and / or at least one ignored supported query parameter is not critical to the service logic, then NF can determine that the search result is useful. Otherwise, NF can determine that the search result is useless.

[0242] Figure 2g A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by means implemented in an NF, or by means implemented as an NF, or by means communicatively coupled to an NF. Therefore, the means can provide components for implementing various parts of method 260, as well as components for combining with other components to implement other processes. For the parts already described in the above embodiments, their description is omitted here for brevity.

[0243] At box 262, the NF may send a first NF discovery request to the first NRF, including at least one query parameter.

[0244] In an embodiment, the first NF discovery request may further include first information indicating whether a query parameter in at least one query parameter is critical to the service logic.

[0245] The first information can be any suitable information, and this disclosure does not limit it.

[0246] In an embodiment, the first information may include at least one of the following: a new query parameter containing a list of names of at least one key query parameter, a Hypertext Transfer Protocol (HTTP) header containing a list of names of at least one key query parameter, or a pattern or extension directly on the query parameter name indicating keyness.

[0247] At box 264, the NF can receive a first NF discovery response from the first NRF.

[0248] In an embodiment, the first NF discovery response may include at least one of the following: a search result generated by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter among at least one query parameter, a rejection message and a reason message indicating that a critical query parameter among at least one query parameter is not supported, or a redirection message when a critical query parameter among at least one query parameter is not supported.

[0249] For example, at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter in at least one query parameter can refer to query parameters that are not necessary or critical to the service logic. At least one critical query parameter in at least one query parameter can refer to query parameters that are necessary or critical to the service logic.

[0250] Figure 3a A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by means implemented in a first NRF, or by means implemented as a first NRF, or by means communicatively coupled to a first NRF. Therefore, the means can provide components for implementing various parts of method 300, as well as components for combining with other components to implement other processes. For the parts already described in the above embodiments, their description is omitted here for brevity.

[0251] At box 302, the first NRF can receive a first NF discovery request from the NF, which includes at least one query parameter.

[0252] At box 304, the first NRF can send a first NF discovery response to the NF.

[0253] For example, when a first NRF receives a first NF discovery request from an NF that includes at least one query parameter, and the first NF discovery request does not contain the network identifier of a second NRF, the first NRF can process the first NF discovery request. For example, the first NRF can process the first NF discovery request as described in Clause 5.3.2.2 of 3GPP 29.510 V18.2.0 or Clause 4.17 of 3GPP TS 23.502 V18.0.0. Furthermore, the first NRF can process the first NF discovery request according to embodiments of this disclosure.

[0254] In an embodiment, at least one query parameter may include at least one of one or more query parameters supported by the first NRF, and may not include one or more query parameters not supported by the first NRF.

[0255] In an embodiment, when the first NF discovery request contains the network identifier of the second NRF, the at least one query parameter may include at least one of one or more query parameters supported by the second NRF, and may not include one or more query parameters not supported by the second NRF.

[0256] In an embodiment, the first NRF may include a visiting NRF, and the second NRF may include a home NRF.

[0257] In an embodiment, the first NRF may include the home NRF, and the second NRF may include the visit NRF.

[0258] In an embodiment, the first NF discovery response includes a search result and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among at least one query parameter for the search result.

[0259] In an embodiment, the first NF discovery request may further include first information indicating whether a query parameter in at least one query parameter is critical to the service logic.

[0260] In an embodiment, the first NF discovery response may include a search result generated by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter among at least one query parameter, or a rejection message and reason information indicating that a critical query parameter among at least one query parameter is not supported, or a redirection message when a critical query parameter among at least one query parameter is not supported.

[0261] In an embodiment, the first information may include at least one of the following: a new query parameter containing a list of names of at least one key query parameter, an HTTP header containing a list of names of at least one key query parameter, or a pattern or extension directly on the query parameter name to indicate keyness.

[0262] In an embodiment, the search results may be generated by a first NRF or a second NRF.

[0263] Figure 3b A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by means implemented in a first NRF, or by means implemented as a first NRF, or by means communicatively coupled to a first NRF. Therefore, the means can provide components for implementing various parts of method 310, as well as components for combining with other components to implement other processes. For the parts already described in the above embodiments, their description is omitted here for brevity.

[0264] At box 312, the first NRF can receive a first boot request or a second NF discovery request from the NF.

[0265] At box 314, the first NRF may send a first bootstrap response or a second NF discovery response to the NF, including information about one or more query parameters supported by the first NRF.

[0266] Figure 3c A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by means implemented in a first NRF, or by means implemented as a first NRF, or by means communicatively coupled to a first NRF. Therefore, the means can provide components for implementing various parts of method 320, as well as components for combining with other components to implement other processes. For the parts already described in the above embodiments, their description is omitted here for brevity.

[0267] At box 322, the first NRF can receive a second boot request or a third NF discovery request from the NF, which contains the network identifier of the second NRF.

[0268] At box 324, the first NRF can send a third boot request or a fourth NF discovery request to the second NRF.

[0269] The fourth NF discovery request can be an existing message or a new message. In an embodiment, the fourth NF discovery request can be, for example, Nnrf_NFDiscovery_Request as described in 3GPP TS 23.502 V18.0.0 or an HTTP GET request as described in Clause 5.3.2.2 of 3GPP 29.510 V18.2.0.

[0270] The third bootstrapping request can be an existing message or a new message. In an embodiment, the third bootstrapping request can be, for example, an Nnrf_Bootstrapping_Get request as described in 3GPP TS 23.502 V18.0.0, or an HTTP GET request as described in Clause 5.5.2.2 of 3GPP 29.510 V18.2.0.

[0271] At box 326, the first NRF may receive a third bootstrap response or a fourth NF discovery response from the second NRF, which includes information about one or more query parameters supported by the second NRF.

[0272] In an embodiment, the third bootstrap response or the fourth NF discovery response may include information about one or more query parameters supported by the second NRF and / or information about one or more query parameters not supported by the second NRF.

[0273] The fourth NF discovery response can be an existing message or a new message. In an embodiment, the fourth NF discovery response can be, for example, an Nnrf_NFDiscovery_Request response as described in 3GPP TS 23.502 V18.0.0, or an HTTP GET response as described in Clause 5.3.2.2 of 3GPP 29.510 V18.2.0.

[0274] The third bootstrapping response can be an existing message or a new message. In an embodiment, the third bootstrapping response can be, for example, an Nnrf_Bootstrapping_Get response as described in 3GPP TS 23.502 V18.0.0, or an HTTP GET response as described in Clause 5.5.2.2 of 3GPP 29.510 V18.2.0.

[0275] At box 328, the first NRF may send a second bootstrap response or a third NF discovery response to the NF, including information about one or more query parameters supported by the second NRF.

[0276] Figure 3d A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by means implemented in a first NRF, or by means implemented as a first NRF, or by means communicatively coupled to a first NRF. Therefore, the means can provide components for implementing various parts of method 330, as well as components for combining with other components to implement other processes. For the parts already described in the above embodiments, their description is omitted here for brevity.

[0277] At box 332, when the first NF discovery request contains the network identifier of the second NRF, the first NRF may send a fifth NF discovery request to the second NRF, which includes at least one query parameter.

[0278] For example, after receiving a first NF discovery request containing the network identifier of a second NRF, the first NRF may send a fifth NF discovery request to the second NRF, which includes at least one query parameter.

[0279] The fifth NF discovery request can be an existing message or a new message. In an embodiment, the fifth NF discovery request can be, for example, Nnrf_NFDiscovery_Request as described in 3GPP TS 23.502 V18.0.0, or an HTTP GET request as described in Clause 5.3.2.2 of 3GPP 29.510 V18.2.0.

[0280] At box 334, the first NRF can receive the fifth NF discovery response from the second NRF. Then, the first NRF can send the first NF discovery response to the NF.

[0281] The fifth NF discovery response can be an existing message or a new message. In an embodiment, the fifth NF discovery response can be, for example, an Nnrf_NFDiscovery_Request response as described in 3GPP TS 23.502 V18.0.0 or an HTTP GET response as described in Clause 5.3.2.2 of 3GPP 29.510 V18.2.0.

[0282] In an embodiment, the fifth NF discovery response may include a search result and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among at least one query parameter for the search result.

[0283] In an embodiment, the fifth NF discovery request may further include first information indicating whether a query parameter in the at least one query parameter is critical to the service logic.

[0284] In an embodiment, the fifth NF discovery response may include at least one of the following: a search result generated by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter in the at least one query parameter, a rejection message and a reason message indicating that a critical query parameter in the at least one query parameter is not supported, or a redirection message when a critical query parameter in the at least one query parameter is not supported.

[0285] Figure 3eA flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by means implemented in a first NRF, or by means implemented as a first NRF, or by means communicatively coupled to a first NRF. Therefore, the means can provide components for implementing various parts of method 340, as well as components for combining with other components to implement other processes. For the parts already described in the above embodiments, their description is omitted here for brevity.

[0286] In an embodiment, when the first NF discovery request does not contain the network identifier of the second NRF (e.g., a service discovery request in the same PLMN), at least one of blocks 342, 344, and 346 may be executed.

[0287] At box 342, optionally, the first NRF can determine the search results by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter among at least one query parameter.

[0288] For example, the first NRF discovery request may further include first information indicating whether a query parameter among the at least one query parameter is critical to the service logic. The first NRF can then determine which of the at least one query parameter is critical to the service logic. Alternatively, the first NRF can determine which of the at least one query parameter is critical to the service logic on its own, for example, based on pre-configuration or machine learning.

[0289] In an embodiment, when the first NRF does not support at least one non-critical query parameter, the first NRF can determine the search result by ignoring at least one non-critical unsupported query parameter.

[0290] In an embodiment, if the search filter criteria do not match the NF instance, the first NRF may attempt to ignore at least one non-critical supported query parameter and then determine the search results that may include one or more matching NF instances.

[0291] At box 344, optionally, the first NRF can determine whether to reject or accept the first NF discovery request based on the criticality of at least one unsupported query parameter in the query parameters. If the first NF discovery request is accepted, box 342 can be executed.

[0292] For example, if an unsupported query parameter in at least one query parameter is critical to the service logic, the first NRF can determine to reject the first NF discovery request. If an unsupported query parameter in at least one query parameter is not critical to the service logic, the first NRF can determine to accept the first NF discovery request.

[0293] At box 346, optionally, when a key query parameter in at least one query parameter is not supported, the first NRF can determine redirection information.

[0294] For example, redirection information may include endpoint information from another NRF that supports at least one or more key query parameters in at least one query parameter. Endpoint information can be any suitable information, such as a URI pointing to an endpoint of another NRF service instance.

[0295] For example, in the case of a redirect, the first NRF may return a 3xx status code, which may include a location header with a URI pointing to an endpoint of another NRF service instance, which may support at least one or more key query parameters in at least one query parameter.

[0296] Figure 4a A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by means implemented in a second NRF, or by means implemented as a second NRF, or by means communicatively coupled to a second NRF. Therefore, the means can provide components for implementing various parts of method 400, as well as components for combining with other components to implement other processes. For the parts already described in the above embodiments, their description is omitted here for brevity.

[0297] At box 402, the second NRF can receive a fifth NF discovery request from the first NRF, which includes at least one query parameter.

[0298] At box 404, the second NRF can send a fifth NF discovery response to the first NRF.

[0299] For example, the second NRF can process the fifth NF discovery request as described in Clause 5.3.2.2 of 3GPP 29.510 V18.2.0 or Clause 4.17 of 3GPP TS23.502 V18.0.0. Furthermore, the second NRF can process the fifth NF discovery request according to embodiments of this disclosure.

[0300] In an embodiment, at least one query parameter may include at least one of one or more query parameters supported by the second NRF, and may not include one or more query parameters not supported by the second NRF.

[0301] In an embodiment, the first NRF may include a visiting NRF, and the second NRF may include a home NRF.

[0302] In an embodiment, the first NRF may include the home NRF, and the second NRF may include the visit NRF.

[0303] In an embodiment, the fifth NF discovery response may include search results and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among at least one query parameter for the search results.

[0304] In an embodiment, the fifth NF discovery request may further include first information indicating whether a query parameter in at least one query parameter is critical to the service logic.

[0305] In an embodiment, the fifth NF discovery response may include at least one of the following: a search result generated by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter in at least one query parameter, a rejection message and information indicating the reason why a critical query parameter in at least one query parameter is not supported, or a redirection message when a critical query parameter in at least one query parameter is not supported.

[0306] In box 406, the second NRF can determine the search results by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter in at least one query parameter.

[0307] For example, the fifth NRF discovery request may also include first information indicating whether a query parameter among the at least one query parameter is critical to the service logic. The second NRF can then determine which of the at least one query parameter is critical to the service logic. Alternatively, the second NRF can determine which of the at least one query parameter is critical to the service logic independently, for example, based on pre-configuration or machine learning.

[0308] In an embodiment, when the second NRF does not support at least one non-critical query parameter, the second NRF can determine the search result by ignoring at least one non-critical unsupported query parameter.

[0309] In an embodiment, if the search filter criteria do not match the NF instance, the second NRF may attempt to ignore at least one non-critical supported query parameter and then determine the search results that may include one or more matching NF instances.

[0310] Figure 4bA flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by means implemented in a second NRF, or by means implemented as a second NRF, or by means communicatively coupled to a second NRF. Therefore, the means can provide components for implementing various parts of method 410, as well as components for combining with other components to implement other processes. For the parts already described in the above embodiments, their description is omitted here for brevity.

[0311] At box 412, the second NRF can receive a third boot request or a fourth NF discovery request from the first NRF.

[0312] At box 414, the second NRF may send a third bootstrap response or a fourth NF discovery response to the first NRF, which includes information about one or more query parameters supported by the second NRF.

[0313] Figure 4c A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by means implemented in a second NRF, or by means implemented as a second NRF, or by means communicatively coupled to a second NRF. Therefore, the means can provide components for implementing various parts of method 420, as well as components for combining with other components to implement other processes. For the parts already described in the above embodiments, their description is omitted here for brevity.

[0314] At box 422, optionally, the second NRF can determine whether to reject or accept the fifth NF discovery request based on the criticality of an unsupported query parameter in at least one query parameter.

[0315] For example, if an unsupported query parameter in at least one of the query parameters is critical to the service logic, the second NRF can determine to reject the first NF discovery request. If an unsupported query parameter in at least one of the query parameters is not critical to the service logic, the second NRF can determine to accept the fifth NF discovery request. If the fifth NF discovery request is accepted, box 422 can be executed.

[0316] At box 424, optionally, a second NRF can determine redirection information when a key query parameter in at least one query parameter is not supported.

[0317] For example, redirection information may include endpoint information from another NRF that supports at least one or more key query parameters in at least one query parameter. Endpoint information can be any suitable information, such as a URI pointing to an endpoint of another NRF service instance.

[0318] For example, in the case of a redirect, the second NRF may return a 3xx status code, which may include a location header with a URI pointing to an endpoint of another NRF service instance, which may support at least one or more key query parameters in at least one query parameter.

[0319] In an embodiment, a mechanism is proposed to allow the NRF to successfully and efficiently process one or more unsupported query parameters by allowing the NF consumer to know a list of supported query parameters to avoid sending one or more unsupported query parameters; or to allow the NF consumer to explicitly indicate the criticality of one or more query parameters, and the NRF decides to reject or accept the NF discovery request based on the criticality of the one or more unsupported query parameters and / or the criticality of the one or more supported query parameters.

[0320] In the embodiments, there may be different possible solutions to solve at least one of the above problems.

[0321] In this embodiment, Solution 1 is provided: The NRF can inform the NF consumer which set of query parameters (or one or more query parameters) is supported.

[0322] In an embodiment, a mechanism may be introduced to allow the NRF to inform the NF consumer about the supported set of query parameters (or one or more supported query parameters) to avoid the NF consumer providing one or more unsupported query parameters, and the NRF receiving one or more unsupported query parameters.

[0323] In one embodiment, solution 1.1 is provided: a set of query parameters (or one or more query parameters) that can be supported via an NRF bootstrapping service. In another embodiment, an NRF such as vNRF can relay bootstrapping service messages to another NRF such as hNRF.

[0324] In the embodiments, solution 1.2 is provided: a set of query parameters (or one or more query parameters) that can provide support in the response to the discovery request, for example, a failure response to the discovery request due to one or more unsupported query parameters, or a success response to the discovery request.

[0325] In an embodiment, a supported set of query parameters (or one or more query parameters) may be returned in another response (or message) to proactively avoid using one or more unsupported query parameters.

[0326] Figure 5a A flowchart of solution 1.1 according to an embodiment of the present disclosure is shown.

[0327] In step 501, the NF consumer may send a GET / bootstrapping request to vNRF as described in Clause 5.5.2.2.1 of 3GPP 29.510 V18.2.0.

[0328] In step 502, the NF consumer can receive a GET / bootstrapping response from vNRF as described in Clause 5.5.2.2.1 of 3GPP 29.510 V18.2.0. The GET / bootstrapping response may contain a body: BootStrapingInfo (the supported set of query parameters).

[0329] In step 503, the NF consumer can determine one or more query parameters that are not supported by vNRF.

[0330] In step 504, the NF consumer may send an Nnrf_NFDiscovery_Request to vNRF as described in 3GPP 23.502 V18.0.0, and avoid including one or more unsupported query parameters in the Nnrf_NFDiscovery_Request.

[0331] The following steps are used for NF / NF service discovery across PLMNs.

[0332] In step 505, the NF consumer can send a GET / bootstrapping request to vNRF including plmn={HPLMN ID}.

[0333] In step 506, vNRF can send a GET / bootstrapping request to hNRF.

[0334] In step 507, vNRF can receive a GET / bootstrapping response from hNRF, including the subject: BootStrapingInfo (the supported set of query parameters), and send the response to the NF consumer.

[0335] In step 508, the NF consumer can determine one or more query parameters that hNRF does not support.

[0336] In step 509, the NF consumer can send an Nnrf_NFDiscovery_Request to the hNRF via the vNRF, and avoid including one or more unsupported query parameters in the Nnrf_NFDiscovery_Request.

[0337] Figure 5b A flowchart of solution 1.2 according to an embodiment of the present disclosure is shown.

[0338] In step 511, the NF consumer may send an Nnrf_NFDiscovery_Request (with unsupported query parameters) to vNRF as described in 3GPP 23.502 V18.0.0.

[0339] In step 512, the NF consumer can receive an Nnrf_NFDiscovery_Request response from vNRF as described in 3GPP 23.502 V18.0.0. The Nnrf_NFDiscovery_Request response may include a body containing: issue details (supported set of query parameters).

[0340] In step 513, the NF consumer can determine one or more query parameters that are not supported by vNRF.

[0341] In step 514, the NF consumer can send an Nnrf_NFDiscovery request to vNRF and avoid including one or more unsupported query parameters in the Nnrf_NFDiscovery request.

[0342] The following steps are used for NF / NF service discovery across PLMNs.

[0343] In step 515, the NF consumer can send an Nnrf_NFDiscovery_Request (with unsupported query parameters) to the vNRF, and the vNRF can send an Nnrf_NFDiscovery_Request (with unsupported query parameters) to the hNRF.

[0344] In step 516, vNRF can receive an Nnrf_NFDiscovery_Request response from hNRF, including the body: problem details (supported query parameter set), and send the response to the NF consumer.

[0345] In step 517, the NF consumer can determine one or more query parameters that hNRF does not support.

[0346] In step 518, the NF consumer can send an Nnrf_NFDiscovery request to the hNRF via the vNRF, and avoid including one or more unsupported query parameters in the Nnrf_NFDiscovery request.

[0347] In one embodiment, a second solution is provided: NRF can indicate one or more query parameters (if any) that are ignored in the discovery / search results.

[0348] In an embodiment, if the NRF chooses to continue the discovery request by ignoring one or more unsupported query parameters and / or one or more supported query parameters, the NRF may include an Information Element (IE) indicating the ignored unsupported query parameters and / or supported query parameters for the search result. The NF consumer can then determine whether the search result is available based on the ignored unsupported query parameters and / or supported query parameters; for example, if a particular ignored query parameter is critical to the service logic, the search result is unavailable.

[0349] Figure 6 A flowchart of solution 2 according to an embodiment of the present disclosure is shown.

[0350] In step 601, the NF consumer may send an Nnrf_NFDiscovery_Request (with unsupported query parameters) to vNRF as described in 3GPP 23.502 V18.0.0.

[0351] In step 602, the NF consumer can receive an Nnrf_NFDiscovery_Request response from vNRF as described in 3GPP 23.502 V18.0.0. The Nnrf_NFDiscovery_Request response may include a body of search results by ignoring one or more unsupported query parameters (the ignored query parameters).

[0352] In step 603, based on one or more ignored query parameters, the NF consumer can determine whether the search results are useful.

[0353] The following steps are used for NF / NF service discovery across PLMNs.

[0354] In step 604, the NF consumer can send an Nnrf_NFDiscovery_Request (with unsupported query parameters) to the hNRF via the vNRF, as described in 3GPP 23.502 V18.0.0.

[0355] In step 605, the NF consumer may receive an Nnrf_NFDiscovery_Request response as described in 3GPP 23.502 V18.0.0 from the hNRF via the vNRF. The Nnrf_NFDiscovery_Request response may include a body containing search results by ignoring one or more unsupported query parameters (ignored query parameters).

[0356] In step 606, based on one or more ignored query parameters, the NF consumer can determine whether the search results are useful.

[0357] In this embodiment, Solution 3 is provided: the NF consumer can indicate the criticality of one or more query parameters in the discovery request.

[0358] In an embodiment, a mechanism may be introduced to allow the NF consumer to explicitly indicate the criticality of one or more query parameters in a discovery request. Since the NF consumer can know the usage of one (or each) query parameter in the discovery request, it can determine whether a particular query parameter is critical to the service logic. The NRF can then determine whether to continue processing the discovery request (e.g., if the unsupported query parameters are non-critical) or reject the discovery request (if the unsupported query parameters are critical) based on the criticality of one or more unsupported query parameters.

[0359] In this embodiment, the indication of criticality can be provided in different ways. For example, a new query parameter containing a list of names of critical query parameters can be used. A new (3GPP-customized) HTTP header containing a list of names of critical query parameters can be used. Patterns / extensions directly on the query parameter names can be used to indicate criticality, for example, adding the extension ":m" / ":o" to the end of the query parameter to indicate criticality.

[0360] Figure 7a A flowchart of solution 3 according to another embodiment of this disclosure is shown.

[0361] In step 701, negotiation of features using bootstrapping or previously discovered features is performed between the NF consumer and the vNRF.

[0362] In step 702, the NF consumer can send an Nnrf_NFDiscovery_Request to vNRF (with unsupported query parameters, list of key query parameters: [list of key query parameters]).

[0363] In step 703, based on the criticality of one or more unsupported query parameters, vNRF can determine whether to reject or accept the request.

[0364] You can perform either step 704a or 705b.

[0365] In step 704a, vNRF may send an Nnrf_NFDiscovery_Request response to the NF consumer, which includes search results by ignoring one or more non-critical, unsupported query parameters.

[0366] In step 705b, vNRF can send an Nnrf_NFDiscovery_Request response to the NF consumer, including the subject: problem details (reason: key query parameter is not supported).

[0367] The following steps are used for NF / NF service discovery across PLMNs.

[0368] In step 706, negotiation using previously discovered features can be performed between the NF consumer and the hNRF.

[0369] In step 707, the NF consumer can send an Nnrf_NFDiscovery_Request (with unsupported query parameters, list of key query parameters: [list of key query parameters]) to hNRF via vNRF.

[0370] In step 708, based on the criticality of the unsupported query parameters, hNRF can determine whether to reject or accept the request.

[0371] You can perform either step 709a or 710b.

[0372] In step 709a, hNRF may send an Nnrf_NFDiscovery_Request response to the NF consumer via vNRF, which includes search results by ignoring one or more non-critical, unsupported query parameters.

[0373] In step 710b, hNRF can send an Nnrf_NFDiscovery_Request response, including subject: problem details (reason: key query parameters are not supported), to the NF consumer via vNRF.

[0374] Figure 7b A flowchart of solution 3 according to another embodiment of this disclosure is shown.

[0375] In step 711, the NF consumer can send an Nnrf_NFDiscovery_Request to vNRF (with unsupported query parameters, 3gpp-Sbi-Critical-Query-Parameters: [list of critical query parameters]).

[0376] In step 712, based on the criticality of the unsupported query parameters, vNRF can determine whether to reject or accept the request.

[0377] You can perform either step 713a or 714b.

[0378] In step 713a, vNRF may send an Nnrf_NFDiscovery_Request response to the NF consumer, which includes search results by ignoring one or more non-critical, unsupported query parameters.

[0379] In step 714b, vNRF can send an Nnrf_NFDiscovery_Request response to the NF consumer, including the subject: problem details (reason: key query parameter is not supported).

[0380] The following steps are used for NF / NF service discovery across PLMNs.

[0381] In step 715, the NF consumer can send an Nnrf_NFDiscovery_Request (with unsupported query parameters, 3gpp-Sbi-Critical-Query-Parameters: [list of critical query parameters]) to hNRF via vNRF.

[0382] In step 716, based on the criticality of the unsupported query parameters, hNRF can determine whether to reject or accept the request.

[0383] You can perform either step 717a or 718b.

[0384] In step 717a, hNRF may send an Nnrf_NFDiscovery_Request response to the NF consumer via vNRF, which includes search results by ignoring one or more non-critical, unsupported query parameters.

[0385] In step 718b, hNRF can send an Nnrf_NFDiscovery_Request response to the NF consumer via vNRF. This response includes the body: problem details (reason: key query parameters are not supported).

[0386] Figure 7c A flowchart of solution 3 according to another embodiment of this disclosure is shown.

[0387] In step 721, negotiation of features using bootstrapping or previously discovered features is performed between the NF consumer and the vNRF.

[0388] In step 722, the NF consumer can send an Nnrf_NFDiscovery_Request to vNRF (with unsupported query parameters). Extensions to the key query parameters ":m" are allowed, such as "tai:m"; "dnn:m".

[0389] In step 723, based on the criticality of the unsupported query parameters, vNRF can determine whether to reject or accept the request.

[0390] You can perform either step 724a or 725b.

[0391] In step 724a, vNRF may send an Nnrf_NFDiscovery_Request response to the NF consumer, which includes search results by ignoring one or more non-critical, unsupported query parameters.

[0392] In step 725b, vNRF can send an Nnrf_NFDiscovery_Request response to the NF consumer, including the subject: problem details (reason: key query parameters are not supported).

[0393] The following steps are used for NF / NF service discovery across PLMNs.

[0394] In step 726, negotiation using previously discovered features can be performed between the NF consumer and the hNRF.

[0395] In step 727, the NF consumer can send an Nnrf_NFDiscovery_Request (with unsupported query parameters) to hNRF via vNRF. There are extensions to the key query parameters, such as "tai:m"; "dnn:m".

[0396] In step 728, based on the criticality of the unsupported query parameters, hNRF can decide whether to reject or accept the request.

[0397] You can perform either step 729a or 730b.

[0398] In step 729a, hNRF may send an Nnrf_NFDiscovery_Request response to the NF consumer via vNRF, which includes search results by ignoring one or more non-critical, unsupported query parameters.

[0399] In step 720b, hNRF can send an Nnrf_NFDiscovery_Request response to the NF consumer via vNRF, including the subject: problem details (reason: key query parameter is not supported).

[0400] Some messages in Figures 5A, 5B, 6, 7A, 7B, and 7C may be identical to the corresponding messages described in 3GPP TS 23.502 V18.0.0 or 3GPP 29.510 V18.2.0. According to some embodiments of this disclosure, some messages in Figures 5A, 5B, 6, 7A, 7B, and 7C may be modified.

[0401] Table 1 below lists the evaluation and considerations for different solutions:

[0402] Table 1

[0403]

[0404] Communication models B, C, and D are described in Appendix E of 3GPP TS 23.501 V18.0.0, as shown below.

[0405] Model B - Direct Communication with NRF: Consumers perform discovery by querying the NRF. Consumers make selections based on the discovery results. Consumers then send requests to the selected service providers.

[0406] Model C - Indirect Communication for Delegated Discovery: The consumer performs discovery by querying the NRF. Based on the discovery results, the consumer selects either an NF set or a specific NF instance within that set. The consumer sends a request to the SCP containing the address of the selected service producer pointing to either an NF service instance or a set of NF service instances. In the latter case, the SCP selects an NF service instance. If possible, the SCP interacts with the NRF to obtain selection parameters such as location and capacity. The SCP then routes the request to the selected NF service producer instance.

[0407] Model D – Indirect Communication with Delegated Discovery: The consumer does not perform any discovery or selection. The consumer adds any necessary discovery and selection parameters required to find the appropriate producer to the service request. SCP uses the request address in the request message, along with the discovery and selection parameters, to route the request to the appropriate producer instance. SCP can perform discovery with NRF and obtain the discovery results.

[0408] Solutions 1.1 and 3.1 & 3.3 require the NF consumer to detect features supported by the NRF or call the bootstrapping service on the NRF to identify which query parameters(s) can be included in the discovery request (or whether extensions are allowed) before discovery. This requirement makes these solutions less compatible with discovery between communication models D and PLMN, where the NF consumer does not actually know which NRF will ultimately handle the discovery request.

[0409] Solution 1.2 requires the same NRF to be used for subsequent discovery requests, providing the supported set of query parameters in the first rejection. While this may not be a problem in practice, given the possible homogeneous deployment of NRFs within a PLMN, another drawback is that rejection will occur when any unsupported query parameters are received, which has a negative impact on key performance indicators (KPIs).

[0410] Solution 2 satisfies all communication scenarios. This solution also avoids NRF rejection as a negative KPI, at the cost of search results (which are often large) potentially being unusable by the NF consumer.

[0411] Solution 3.2 satisfies all scenarios and avoids returning unnecessary search results. Rejection (due to unsupported key query parameters) can be considered acceptable, or even expected.

[0412] Solution 3.2, which introduces new HTTP custom headers to indicate the criticality of query parameters, is recommended and may be the way forward.

[0413] Solution 2 can also help NF consumers know which query parameters are ignored for the search results, and this can be used in conjunction with Solution 3.2.

[0414] Many advantages can be achieved by applying the solutions proposed according to embodiments of this disclosure. In some embodiments herein, it can provide a coordinated approach for NRF and NF consumers to perform NF discovery. In some embodiments herein, it can eliminate ambiguity in the behavior of the NRF in processing the request and the NF consumer in processing the search results when the query parameters provided by the NF consumer may not be supported by the NRF. In some embodiments herein, it can avoid network traffic waste and negative KPIs caused by service request rejection. The embodiments herein are not limited to the features and advantages described above. Additional features and advantages will be recognized by those skilled in the art upon reading the following detailed description.

[0415] Figure 8a This is a block diagram illustrating an apparatus suitable for practicing some embodiments of the present disclosure. For example, the aforementioned NF, first NRF, or second NRF can be implemented as or through apparatus 800.

[0416] Device 800 may include at least one processor 821 (e.g., a digital processor (DP)) and at least one memory (MEM) 822 coupled to the processor 821. Device 800 may further include a transmitter TX and a receiver RX 823 coupled to the processor 821. MEM 822 stores a program (PROG) 824. PROG 824 may contain instructions that, when executed on the associated processor 821, enable device 800 to operate according to embodiments of the present disclosure. Combinations of at least one processor 821 and at least one MEM 822 can form a processing device 825 suitable for implementing various embodiments of the present disclosure.

[0417] Various embodiments of this disclosure can be implemented by a computer program that can be executed by one or more of a processor 821, software, firmware, hardware, or a combination thereof.

[0418] MEM 822 can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as, by way of non-limiting examples, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.

[0419] The processor 821 may be of any type suitable for the local technical environment and may include, as a non-limiting example, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture.

[0420] In embodiments where the device is implemented as an NF or at an NF, memory 822 stores instructions executable by processor 821, thereby allowing the NF to operate according to any method performed by the NF as described above.

[0421] In embodiments where the device is implemented as a first NRF or at a first NRF, memory 822 stores instructions executable by processor 821, thereby allowing the first NRF to operate according to any method performed by the first NRF as described above.

[0422] In embodiments where the device is implemented as a second NRF or at a second NRF, memory 822 stores instructions executable by processor 821, thereby allowing the second NRF to operate according to any method performed by the second NRF as described above.

[0423] Figure 8bThis is a block diagram illustrating an NF according to an embodiment of the present disclosure. As shown, NF 850 ​​may include a first sending module 851 configured to send a first NF discovery request including at least one query parameter to a first Network Repository Function (NRF). NF 850 ​​may include a first receiving module 852 configured to receive a first NF discovery response from the first NRF. The first NF discovery response may include a search result and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among the at least one query parameter for the search result.

[0424] In an embodiment, NF 850 ​​may further include a first acquisition module 853 configured to acquire information about one or more query parameters supported by a first NRF.

[0425] In an embodiment, NF 850 ​​may further include a first determining module 854 configured to determine one or more query parameters not supported by the first NRF. The at least one query parameter may include at least one of the one or more query parameters supported by the first NRF, and may not include one or more query parameters not supported by the first NRF.

[0426] In an embodiment, NF 850 ​​may further include a second acquisition module 855 configured to acquire information about one or more query parameters supported by a second NRF.

[0427] In an embodiment, NF 850 ​​may further include a second determining module 856 configured to determine one or more query parameters not supported by the second NRF. When the first NF discovers a request containing the network identifier of the second NRF, the at least one query parameter may include at least one of the one or more query parameters supported by the second NRF, and may not include one or more query parameters not supported by the second NRF.

[0428] In an embodiment, NF 850 ​​may further include a third determining module 857 configured to determine whether a search result is useful based on at least one ignored unsupported query parameter and / or at least one ignored supported query parameter.

[0429] Figure 8cA block diagram of a first NRF according to an embodiment of the present disclosure is shown. As shown, the first NRF 860 may include a first receiving module 861 configured to receive a first NF discovery request from an NF including at least one query parameter. The first NRF 860 may further include a first sending module 862 configured to send a first NF discovery response to the NF. The first NF discovery response may include a search result and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among the at least one query parameter for the search result.

[0430] In an embodiment, the first NRF 860 may include a second receiving module 863 configured to receive a first boot request or a second NF discovery request from the NF.

[0431] In an embodiment, the first NRF 860 may further include a second sending module 864 configured to send a first bootstrap response or a second NF discovery response to the NF, including information about one or more query parameters supported by the first NRF.

[0432] In an embodiment, the first NRF 860 may further include a third receiving module 865, which is configured to receive from the NF a second boot request or a third NF discovery request including the network identifier of the second NRF.

[0433] In an embodiment, the first NRF 860 may further include a third transmitting module 866, which is configured to send a third boot request or a fourth NF discovery request to the second NRF.

[0434] In an embodiment, the first NRF 860 may further include a fourth receiving module 867 configured to receive from the second NRF a third bootstrap response or a fourth NF discovery response including information about one or more query parameters supported by the second NRF.

[0435] In an embodiment, the first NRF 860 may further include a fourth sending module 868, which is configured to send a second bootstrap response or a third NF discovery response to the NF, including information about one or more query parameters supported by the second NRF.

[0436] In an embodiment, when the first NF discovery request includes the network identifier of the second NRF, the first NRF 860 may further include a fifth sending module 869, configured to send a fifth NF discovery request including at least one query parameter to the second NRF. The first NRF 860 may further include a fifth receiving module 870, configured to receive a fifth NF discovery response from the second NRF.

[0437] In an embodiment, when the first NF discovery request does not contain the network identifier of the second NRF, the first NRF 860 may further include a first determination module 871, configured to determine the search results by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter among at least one query parameter. The first NRF 860 may further include a second determination module 872, configured to determine whether to reject or accept the first NF discovery request based on the criticality of the unsupported query parameter among at least one query parameter. The first NRF 860 may further include a first determination module 873, configured to determine redirection information when a critical query parameter among at least one query parameter is not supported.

[0438] Figure 8d This is a block diagram illustrating a second NRF according to an embodiment of the present disclosure. As shown, the second NRF 880 may include a first receiving module 881 configured to receive a fifth NF discovery request including at least one query parameter from the first NRF. The second NRF 880 may further include a first sending module 882 configured to send a fifth NF discovery response to the first NRF.

[0439] In an embodiment, the second NRF 880 may further include a second receiving module 883 configured to receive a third bootstrapping request or a fourth NF discovery request from the first NRF. The second NRF 880 may further include a second sending module 884 configured to send a third bootstrapping response or a fourth NF discovery response to the first NRF, including information about one or more query parameters supported by the second NRF.

[0440] In an embodiment, the second NRF 880 may further include a first determining module 885 configured to determine the search results by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter among at least one query parameter.

[0441] In an embodiment, the second NRF 880 may further include a second determination module 886, which is configured to determine whether to reject or accept the fifth NF discovery request based on the criticality of an unsupported query parameter in at least one query parameter.

[0442] In an embodiment, the second NRF 880 may further include a third determining module 887, which is configured to determine redirection information when a key query parameter in at least one query parameter is not supported.

[0443] The term unit or module may have the conventional meaning in the field of electronic, electrical and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, outputs and / or display functions, and the like, as described herein.

[0444] Using functional units, the NF, the first NRF, or the second NRF does not require a fixed processor or memory; arbitrary computing and storage resources can be deployed from the NF, the first NRF, or the second NRF within the communication system. The introduction of virtualization and network computing technologies can improve the efficiency of network resource utilization and network flexibility.

[0445] In addition, an exemplary overall communication system including terminal devices (e.g., UE) and network nodes (e.g., NF, first NRF, or second NRF) will be described below.

[0446] Figure 9 An example of a communication system QQ100 according to some embodiments is shown.

[0447] In this example, the communication system QQ100 includes a telecommunications network QQ102, which includes an access network QQ104 (e.g., a radio access network (RAN)) and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may generally be referred to as network node QQ110), or any other similar 3GPP access node or non-3GPP access point. Furthermore, as those skilled in the art will understand, network nodes are not necessarily limited to implementations of radio and baseband portions provided and integrated by a single supplier. Therefore, it will be understood that network nodes include their decomposed implementations or portions. For example, in some embodiments, the telecommunications network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the QQ102 telecommunications network that supports the ORAN specification (e.g., the specification published by the O-RAN Alliance or any similar organization) and can operate independently or together with other nodes to perform one or more functions of any node in the QQ102 telecommunications network (including one or more network nodes QQ110 and / or core network node QQ108).

[0448] Examples of ORAN network nodes include Open Radio Units (O-RUs), Open Distributed Units (O-DUs), Open Central Units (O-CUs), O-CU control planes (O-CU-CPs) or O-CU user planes (O-CU-UPs), RAN intelligent controllers (near real-time or non-real-time) with managed software or software plugins, such as near real-time control applications (e.g., xApps) or non-real-time control applications (e.g., rApps), or any combination thereof (the adjective "open" indicates support for the ORAN specification). Network nodes can support the specification by, for example, supporting interfaces defined by the ORAN specification (e.g., A1, F1, W1, E1, E2, X2, Xn interfaces, Open Fronthaul User Plane interfaces, or Open Fronthaul Management Plane interfaces). Furthermore, ORAN access nodes can be logical nodes within physical nodes. Additionally, ORAN network nodes can be implemented in a virtualized environment (described further below), where one or more network functions are virtualized. For example, a virtualized environment may contain an O-Cloud computing platform orchestrated by a service management and orchestration framework via the O-2 interface or comparable technologies defined by the O-RAN Alliance. Network node QQ110 facilitates direct or indirect connections for user equipment (UEs), such as connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may generally be referred to as UE QQ112) to the core network QQ106 via one or more radio connections.

[0449] Examples of wireless communication via wireless connection include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without the use of wires, cables, or other conductors. Furthermore, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals, whether via wired or wireless connections. The communication system QQ100 may include and interface with any type of communication, telecommunications, data, cellular, radio network, and / or other similar type of system.

[0450] UE QQ112 can be any of a wide variety of communication devices, including wireless devices that are arranged, configured, and / or operable to communicate wirelessly with network node QQ110 and other communication devices. Similarly, network node QQ110 is arranged, capable, configured, and / or operable to communicate directly or indirectly with UE QQ112 and / or with other network nodes or devices in telecommunication network QQ102 to enable and / or provide network access (e.g., wireless network access) and / or perform other functions (e.g., management in telecommunication network QQ102).

[0451] In the depicted example, core network QQ106 connects network node QQ110 to one or more hosts (e.g., host QQ116). These connections can be direct or indirect, via one or more intermediate networks or devices. In other examples, network nodes can be directly coupled to hosts. Core network QQ106 includes one or more core network nodes (e.g., core network node QQ108), which are composed of hardware and software components. The characteristics of these components can be substantially similar to those described for UEs, network nodes, and / or hosts, such that the description generally applies to the corresponding components of core network node QQ108. Example core network nodes include one or more of the following: Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Dehiding Function (SIDF), Unified Data Management (UDM), Security Edge Protection Agent (SEPP), Network Open Function (NEF), and / or User Plane Function (UPF).

[0452] The host QQ116 may be owned or controlled by a service provider other than the operator or provider of access network QQ104 and / or telecommunications network QQ102, and may be operated by or on behalf of the service provider. The host QQ116 may host various applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services (e.g., retrieving and compiling data from various environmental conditions detected by multiple UEs), analytics functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by the server.

[0453] Overall, Figure 9The QQ100 communication system enables connections between the UE, network nodes, and hosts. In this sense, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards, including but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE) and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards, such as Global Microwave Access Interoperability (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards, such as LoRa and Sigfox.

[0454] In some examples, the QQ102 telecom network is a cellular network implementing 3GPP standardized features. Therefore, the QQ102 telecom network can support network slicing to provide different logical networks to different devices connected to it. For example, the QQ102 telecom network can provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs, and / or providing massive machine-type communication (mMTC) / massive IoT services to even more UEs.

[0455] In some examples, UE QQ112 is configured to send and / or receive information without direct human-machine interaction. For example, the UE may be designed to transmit information to access network QQ104 according to a predetermined schedule, when triggered by internal or external events, or in response to a request from access network QQ104. Furthermore, the UE may be configured to operate in single or multiple RAT or multi-standard modes. For example, the UE may operate using any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., configured for multiple radio dual connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio Dual Connectivity (EN-DC).

[0456] In this example, hub QQ114 communicates with access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, hub QQ114 may be a controller, router, content source and analytics, or any other communication device described herein with respect to the UE. For example, hub QQ114 may be a broadband router that enables the UE to access core network QQ106. As another example, hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UE. Commands or instructions may be received from the UE, network node QQ110, or by executable code, scripts, procedures, or other instructions in hub QQ114. As another example, hub QQ114 may be a data collector that acts as temporary storage for UE data, and in some embodiments, may perform data analytics or other processing. As another example, hub QQ114 may be a content source. For example, for a UE acting as a VR headset, display, speaker, or other media delivery device, the QQ114 hub can retrieve VR assets, video, audio, or other media or sensor-related data via network nodes, and then provide it to the UE directly, after performing local processing, and / or after adding additional local content. In yet another example, the QQ114 hub acts as a proxy server or coordinator for the UE, particularly when one or more of the UEs are low-power IoT devices.

[0457] Hub QQ114 can have a constant / persistent or intermittent connection to network node QQ110b. Hub QQ114 can also allow different communication schemes and / or scheduling between hub QQ114 and UEs (e.g., UEs QQ112c and / or QQ112d) and between hub QQ114 and core network QQ106. In other examples, hub QQ114 is connected to core network QQ106 and / or one or more UEs via a wired connection. Furthermore, hub QQ114 can be configured to connect to an M2M service provider via access network QQ104 and / or to another UE via a direct connection. In some scenarios, a UE can establish a wireless connection with network node QQ110 while still being connected via a wired or wireless connection via hub QQ114. In some embodiments, hub QQ114 may be a dedicated hub, i.e., a hub whose primary function is to route communication from the UE to network node QQ110b and / or from network node QQ110b to the UE. In other embodiments, hub QQ114 may be a non-dedicated hub, i.e., a device capable of operating to route communication between the UE and network node QQ110b, but also capable of operating as a communication start and / or end point for some data channels.

[0458] Figure 10 A UE QQ200 according to some embodiments is illustrated. As used herein, a UE refers to a device capable of, configured, positioned, and / or operable to wirelessly communicate with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cellular phones, VoIP phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless client devices (CPEs), vehicles, in-vehicle or in-vehicle embedded / integrated wireless devices, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including Narrowband Internet of Things (NB-IoT) UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs.

[0459] For example, by implementing 3GPP standards for sidelink communication, Dedicated Short Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X), the UE can support device-to-device (D2D) communication. In other examples, the UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated equipment. Instead, the UE may represent a device intended for sale to or operated by a human user, but may not be associated with a particular human user, or may not initially be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, the UE may represent a device not intended for sale to or operated by an end user, but may be associated with a user or operated for the user's benefit (e.g., a smart meter).

[0460] UE QQ200 includes processing circuitry QQ202, which is operatively coupled via bus QQ204 to input / output interface QQ206, power supply QQ208, memory QQ210, communication interface QQ212, and / or any other component, or any combination thereof. Some UEs may use... Figure 10 The components shown may be all or some of the components. The degree of integration between components may vary from UE to UE. In addition, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0461] The processing circuit QQ202 is configured to process instructions and data and can be configured to implement any sequential state machine operable to execute instructions stored as a machine-readable computer program in memory QQ210. The processing circuit QQ202 can be implemented as one or more hardware-implemented state machines (e.g., discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic along with appropriate firmware; one or more stored computer programs, a general-purpose processor (e.g., a microprocessor or digital signal processor (DSP)) along with appropriate software; or any combination of the foregoing. For example, the processing circuit QQ202 may include multiple central processing units (CPUs).

[0462] In this example, the input / output interface QQ206 can be configured to provide one or more interfaces to input devices, output devices, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, other output devices, or any combination thereof. Input devices can allow users to capture information into the UE QQ200. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital camcorders, webcams, etc.), microphones, sensors, mice, trackballs, steering wheels, touchpads, scroll wheels, smart cards, etc. Presence-sensitive displays may include capacitive or resistive touch sensors to sense input from the user. Sensors may be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, optical sensors, proximity sensors, biosensors, etc., or any combination thereof. Output devices can use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port can be used to provide both input and output devices.

[0463] In some embodiments, the power supply QQ208 is configured as a battery or battery pack. Other types of power sources can be used, such as external power sources (e.g., power outlets), photovoltaic devices, or batteries. The power supply QQ208 may further include power supply circuitry for delivering power from the power supply QQ208 itself and / or an external power source to various components of the UE QQ200 via input circuitry or an interface (e.g., a power cable). The power delivery may be used, for example, to charge the power supply QQ208. The power supply circuitry may format, convert, or otherwise modify the power from the power supply QQ208 to suit the power supply for the various components of the UE QQ200 being powered.

[0464] The memory QQ210 can be a memory or is configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), disk, optical disk, hard disk, removable cassette tape, flash drive, etc. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, widget, utility engine, or other application, and corresponding data QQ216. The memory QQ210 can store any of a variety of operating systems or combinations of operating systems for use by the UE QQ200.

[0465] The QQ210 memory can be configured to include multiple physical drive units, such as a Redundant Array of Independent Disks (RAID), flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital multifunction optical disc (HD-DVD) drive, an internal hard drive, a Blu-ray disc drive, a holographic digital data storage (HDDS) disc drive, an external micro dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, smart card memory (e.g., a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more subscriber identification modules (SIMs), such as USIM and / or ISIM), other memory, or any combination thereof. The UICC can be an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a "SIM card." The QQ210 memory allows the UE QQ200 to access instructions, applications, etc., stored on temporary or non-temporary storage media to offload or upload data. Articles of manufacture (e.g., articles of manufacture utilizing a communication system) may be tangibly embodied in or located in memory QQ210, which may be or include a device-readable storage medium.

[0466] The processing circuitry QQ202 can be configured to communicate with an access network or other network using a communication interface QQ212. The communication interface QQ212 may include one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers for communication, such as through one or more remote transceivers (e.g., another UE or network node in the access network) of another device capable of wireless communication. Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 suitable for providing network communication (e.g., optical, electrical, frequency allocation, etc.). Furthermore, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuitry, software, or firmware, or alternatively may be implemented separately.

[0467] In the illustrated embodiment, the communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication (e.g., Bluetooth, near-field communication), location-based communication (e.g., using a Global Positioning System (GPS) to determine location), other similar communication functions, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Fiber Network (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), etc.

[0468] Regardless of the sensor type, the UE can provide the output of data captured by its sensors via its communication interface QQ212 through a wireless connection to the network node. Data captured by the UE's sensors can be transmitted to the network node via another UE through the wireless connection. The output can be periodic (e.g., every 15 minutes if it reports sensed temperature), random (e.g., to balance the load of reports from multiple sensors), responsive to trigger events (e.g., sending an alarm when moisture is detected), responsive to requests (e.g., user-initiated requests), or a continuous stream (e.g., real-time video feed of a patient).

[0469] As another example, the UE includes actuators, motors, or switches associated with a communication interface configured to receive wireless input from a network node via a wireless connection. The state of the actuator, motor, or switch can change in response to the received wireless input. For example, the UE may include a motor that adjusts the control surfaces or rotors of a drone in flight based on the received input, or control a robotic arm performing a medical procedure based on the received input.

[0470] When a UE is in the form of an Internet of Things (IoT) device, it can be a device used in one or more application areas, including but not limited to urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices include or are embedded in the following devices: connected refrigerators or freezers, TVs, connected lighting devices, electricity meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, electric door locks, connected doorbells, air conditioning systems (such as heat pumps), autonomous vehicles, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearable devices for haptic or sensory enhancement, sprinklers, animal or object tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any type of medical device (such as heart rate monitors or remote-controlled surgical robots). UEs in the form of IoT devices, in addition to including those related to… Figure 10 In addition to the other components described in the UE QQ200 description, it further includes circuitry and / or software depending on the intended application of the IoT device.

[0471] As another specific example, in IoT scenarios, a UE can represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another UE and / or network node. In this case, the UE can be an M2M device, which can be referred to as an MTC device in the 3GPP context. As a specific example, a UE can implement the 3GPP NB-IoT standard. In other scenarios, a UE can represent a vehicle, such as a car, bus, truck, ship, and aircraft, or other devices capable of monitoring and / or reporting their operational status or other functions related to their operation.

[0472] In practice, any number of UEs can be used for a single use case. For example, the first UE may be a drone or integrated into a drone, providing the drone's speed information (obtained via a speed sensor) to a second UE, i.e., a remote controller operating the drone. When the user makes a change from the remote controller, the first UE can adjust the throttle on the drone (e.g., by controlling actuators) to increase or decrease the drone's speed. The first UE and / or the second UE may further include more than one of the functions described above. For example, the UE may include sensors and actuators, as well as communications for processing data from the speed sensors and actuators.

[0473] Figure 11A network node QQ300 according to some embodiments is illustrated. As used herein, a network node refers to a device that is capable of, configured, arranged, and / or operable to communicate directly or indirectly with a UE and / or other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)), O-RAN nodes, or components of O-RAN nodes (e.g., O-RUs, O-DUs, O-CUs).

[0474] Base stations can be classified according to the coverage they provide (or, in other words, their transmit power level); therefore, depending on the coverage provided, a base station can be referred to as a femtobase, picobase, microbase, or macrobase. A base station can be a relay node or a relay donor node controlling a relay. A network node can further comprise one or more (or all) portions of a distributed radio base station, such as centralized digital units, distributed units (e.g., in O-RAN access nodes), and / or remote radio units (RRUs), sometimes referred to as remote radio headends (RRHs). Such remote radio units may or may not be integrated with an antenna as antenna-integrated radios. The portions of a distributed radio base station can also be referred to as nodes in a distributed antenna system (DAS).

[0475] Other examples of network nodes include multiple transport point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment (e.g., MSR BS), network controllers (e.g., radio network controller (RNC) or base station controller (BSC)), base transceiver stations (BTS), transport points, transport nodes, multi-cell / multicast coordination entities (MCE), operation and maintenance (O&M) nodes, operations support system (OSS) nodes, self-organizing network (SON) nodes, location nodes (e.g., evolved servicing mobile location center (E-SMLC)), and / or minimized drive test (MDT).

[0476] Network node QQ300 includes processing circuitry QQ302, memory QQ304, communication interface QQ306, and power supply QQ308. Network node QQ300 can consist of multiple physically independent components (e.g., node B components and RNC components, or BTS components and BSC components, etc.), each component may have its own components. In some scenarios where network node QQ300 includes multiple independent components (e.g., BTS and BSC components), one or more of these independent components can be shared among multiple network nodes. For example, a single RNC can control multiple node Bs. In this case, each unique node B and RNC pair can be considered a single independent network node in some situations. In some embodiments, network node QQ300 can be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., a separate memory QQ304 for different RATs), and some components may be reused (e.g., the same antenna QQ310 may be shared by different RATs). The network node QQ300 may further include various components for different wireless technologies integrated into the network node QQ300, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, radio frequency identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node QQ300.

[0477] The processing circuitry QQ302 may include a combination of one or more of the following: a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array or any other suitable computing device, resource or combination of hardware, software and / or coding logic, which may be used alone or in combination with other network node QQ300 components (e.g., memory QQ304) to provide network node QQ300 functionality.

[0478] In some embodiments, the processing circuit QQ302 includes a system-on-a-chip (SOC). In some embodiments, the processing circuit QQ302 includes one or more of a radio frequency (RF) transceiver circuit QQ312 and a baseband processing circuit QQ314. In some embodiments, the RF transceiver circuit QQ312 and the baseband processing circuit QQ314 may be located on separate chips (or chipsets), circuit boards, or units (e.g., radio units and digital units). In alternative embodiments, some or all of the RF transceiver circuit QQ312 and the baseband processing circuit QQ314 may be located on the same chip or a set of chips, boards, or units.

[0479] The memory QQ304 may include any form of volatile or non-volatile computer-readable memory, including but not limited to persistent memory, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, optical disc (CD), or digital video disc (DVD)) and / or any other volatile or non-volatile, non-transient device-readable and / or computer-executable memory device, used to store information, data, and / or instructions that can be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including computer programs, software, applications, including one or more of the following: logic, rules, code, tables, and / or other instructions that can be executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations performed by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and the memory QQ304 are integrated.

[0480] Communication interface QQ306 is used for wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As shown, communication interface QQ306 includes a port / terminal QQ316 for transmitting and receiving data to and from the network, for example, via a wired connection. Communication interface QQ306 further includes radio front-end circuitry QQ318, which may be coupled to antenna QQ310, or in some embodiments to a portion of antenna QQ310. Radio front-end circuitry QQ318 includes a filter QQ320 and an amplifier QQ322. Radio front-end circuitry QQ318 may be connected to antenna QQ310 and processing circuitry QQ302. Radio front-end circuitry QQ318 can be configured to modulate the signal transmitted between antenna QQ310 and processing circuitry QQ302. Radio front-end circuitry QQ318 can receive digital data to be transmitted wirelessly to other network nodes or UEs. Radio front-end circuitry QQ318 can use a combination of filter QQ320 and / or amplifier QQ322 to convert digital data into radio signals with appropriate channel and bandwidth parameters. Radio signals can then be transmitted via antenna QQ310. Similarly, when receiving data, antenna QQ310 can collect radio signals, which are then converted into digital data by radio front-end circuitry QQ318. The digital data can then be passed to processing circuitry QQ302. In other embodiments, communication interface QQ306 may include different components and / or different combinations of components.

[0481] In some alternative embodiments, network node QQ300 does not include a separate radio front-end circuit QQ318; instead, processing circuitry QQ302 includes radio front-end circuitry and is connected to antenna QQ310. Similarly, in some embodiments, all or part of RF transceiver circuitry QQ312 is part of communication interface QQ306. In other embodiments, communication interface QQ306 includes one or more ports or terminals QQ316, radio front-end circuitry QQ318, and RF transceiver circuitry QQ312 (not shown) as part of a radio unit, and communication interface QQ306 communicates with baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0482] Antenna QQ310 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna QQ310 may be coupled to radio front-end circuitry QQ318 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna QQ310 is decoupled from network node QQ300 and may be connected to network node QQ300 via an interface or port.

[0483] Antenna QQ310, communication interface QQ306, and / or processing circuitry QQ302 can be configured to perform any receive operation and / or certain acquire operation described herein by a network node. Any information, data, and / or signals can be received from the UE, another network node, and / or any other network device. Similarly, antenna QQ310, communication interface QQ306, and / or processing circuitry QQ302 can be configured to perform any transmit operation described herein by a network node. Any information, data, and / or signals can be transmitted to the UE, another network node, and / or any other network device.

[0484] Power supply QQ308 provides power to the various components of network node QQ300 in a manner suitable for each component (e.g., at the voltage and current levels required by each individual component). Power supply QQ308 may further include or be coupled to power management circuitry to provide power to the components of network node QQ300 for performing the functions described herein. For example, network node QQ300 may be connected to an external power source (e.g., mains, power outlet) via input circuitry or an interface such as a cable, thereby supplying power to the power circuitry of power supply QQ308. As a further example, power supply QQ308 may include a power source in the form of a battery or battery pack, which is connected to or integrated into the power circuitry. The battery can provide backup power in the event of an external power failure.

[0485] Implementations of the network node QQ300 may include, except Figure 11Additional components beyond those shown may be used to provide certain aspects of the network node's functionality, including any of the functions described herein and / or any functionality required to support the topics described herein. For example, the network node QQ300 may include a user interface device to allow information to be input into and output from the network node QQ300. This can allow users to perform diagnostic, maintenance, repair, and other management functions on the network node QQ300.

[0486] Figure 12 This is a block diagram of the QQ400 host based on the various aspects described in this article, which can be... Figure 9 The embodiment of host QQ116. As used herein, host QQ400 can be or include a combination of various hardware and / or software, including standalone servers, blade servers, cloud-implemented servers, distributed servers, virtual machines, containers, or processing resources in a server farm. Host QQ400 can provide one or more services to one or more UEs.

[0487] The host QQ400 includes processing circuitry QQ402, operatively coupled via bus QQ404 to input / output interfaces QQ40 and QQ404, a network interface QQ408, a power supply QQ410, and a memory QQ412. Other components may be included in other embodiments. The characteristics of these components may be substantially similar to those described with respect to the terminal device, such that the description generally applies to the corresponding components of the host QQ400.

[0488] The memory QQ412 can store one or more computer programs (including one or more host applications QQ414) and data QQ41QQ4, which may include user data, such as data generated by the UE for the host QQ400 or data generated by the host QQ400 for the UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application QQ414 can be implemented in a container-based architecture and can provide support for video codecs (e.g., Multi-Function Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for various categories, types, or implementations of UEs (e.g., mobile phones, desktop computers, wearable display systems, and head-up display systems). The host application QQ414 can also provide user authentication and authorization checks and can periodically report health status, routing, and content availability to a central node (e.g., devices in the core network or at the edge). Therefore, the host QQ400 can select and / or indicate different hosts for the UE to use for over-the-top services. The host application QQ414 can support various protocols, such as HTTP Real-Time Streaming (HLS), Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0489] Figure 13 This is a block diagram illustrating a virtualized environment QQ500, in which functionality implemented in certain embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or equipment, which may include a virtualized hardware platform, storage devices, and network resources. As used herein, virtualization can be applied to any device or component thereof described herein and involves at least a portion of functionality being implemented as an implementation of one or more virtual components. Some or all of the functionality described herein can be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more hardware nodes (e.g., hardware computing devices running as network nodes, UEs, core network nodes, or hosts). Furthermore, in embodiments where virtual nodes do not require radio connectivity (e.g., core network nodes or hosts), the nodes can be fully virtualized. In some embodiments, the virtualized environment QQ500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a service management and orchestration framework via an O-2 interface.

[0490] The application QQ502 (which may also be referred to as a software instance, virtual device, network function, virtual node, virtual network function, etc.) is run in the virtualization environment Q400 to implement some of the features, functions and / or advantages of some embodiments disclosed herein.

[0491] Hardware QQ504 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices described herein, such as network interfaces, input / output interfaces, etc. The software can be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM QQ508A and QQ508B (one or more of which may be collectively referred to as VM QQ508), and / or perform any functionality, features, and / or advantages related to some embodiments described herein. Virtualization layer QQ506 can present a virtual operating platform to VMQQ508, which appears as networked hardware.

[0492] VM QQ508 includes virtual processing, virtual memory, virtual networks or interfaces, and virtual storage devices, and can be run by the corresponding virtualization layer QQ506. Different embodiments of virtual device QQ502 instances can be implemented on one or more VM QQ508, and can be implemented in different ways. Hardware virtualization is sometimes referred to as Network Functions Virtualization (NFV). NFV can be used to consolidate many types of network devices onto industry-standard high-capacity server hardware, physical switches, and physical storage, which can reside in data centers and client devices.

[0493] In the context of NFV, a VM QQ508 can be a software implementation of a physical machine, whose runtime environments behave as if they were running on a physical, non-virtualized machine. Each VM QQ508, along with the portion of the hardware QQ504 running that VM (whether dedicated to that VM or shared by that VM with other VMs), forms a separate virtual network element. Still within the NFV context, the virtual network function is responsible for handling specific network functions running on one or more VMQQ508s on top of the hardware QQ504, and corresponds to the application QQ502.

[0494] The hardware QQ504 can be implemented in a standalone network node with general or specific components. Some functions of the hardware QQ504 can be implemented via virtualization. Alternatively, the hardware QQ504 can be part of a larger hardware cluster (e.g., in a data center or CPE) where many hardware nodes work together and are managed via a management and orchestration QQ510, which, among other things, oversees the lifecycle management of the application QQ502. In some embodiments, the hardware QQ504 is coupled to one or more radio units, each including one or more transmitters and one or more receivers, which may be coupled to one or more antennas. The radio units can communicate directly with other hardware nodes via one or more suitable network interfaces and can be used in conjunction with virtual components to provide radio capabilities to virtual nodes (e.g., radio access nodes or base stations). In some embodiments, a control system QQ512 can be used to provide some signaling; the control system QQ512 can alternatively be used for communication between the hardware nodes and the radio units.

[0495] Figure 14 A communication diagram is shown illustrating communication between host QQ602 and UE QQ606 via network node QQ604 over a partial wireless connection, according to some embodiments. Reference will now be made to various embodiments. Figure 14 To describe the UEs discussed in the previous paragraphs (e.g.) Figure 9 UE QQ112a), network nodes (e.g. Figure 9 Network node QQ110a) and host (e.g. Figure 9 The host QQ116 and / or Figure 12 Example implementation of QQ400 (host).

[0496] Similar to host QQ400, embodiments of host QQ602 include hardware such as a communication interface, processing circuitry, and memory. Host QQ602 further includes software stored in or accessible by host QQ602 and executable by the processing circuitry. This software includes a host application operable to provide services to remote users, such as UE QQ606 connected via an over-the-top (OTT) connection QQ650 extending between UE QQ606 and host QQ602. In providing services to remote users, the host application can provide user data transmitted using the OTT connection QQ650.

[0497] Network node QQ604 includes hardware that enables it to communicate with host QQ602 and UE QQ606. Connection to QQ604 can be direct or via a core network (such as...). Figure 9The core network (QQ106) and / or one or more other intermediate networks (such as one or more public, private, or hosted networks). For example, an intermediate network could be a backbone network or the Internet.

[0498] UE QQ606 comprises hardware and software. The software is stored in or accessible by UE QQ606 and can be executed by the UE's processing circuitry. The software includes client applications, such as web browsers or operator-specific "applications," operable to provide services to human or non-human users via UE QQ606 with the support of host QQ602. In host QQ602, the executing host application can communicate with the executing client application via OTT connection QQ650, which terminates between UE QQ606 and host QQ602. When providing services to a user, the UE's client application can receive request data from the host application of the host and provide user data in response to the request data. OTT connection QQ650 can transmit both request data and user data. The UE's client application can interact with the user to generate user data, which is provided to the host application via OTT connection QQ650.

[0499] The OTT connection QQ650 can be extended via connection QQ660 between host QQ602 and network node QQ604, and via wireless connection QQ670 between network node QQ604 and UE QQ606, to provide connectivity between host QQ602 and UE QQ606. Connection QQ660 and wireless connection QQ670 (through which OTT connection QQ650 can be provided) have been abstractly drawn to illustrate communication between host QQ602 and UE QQ606 via network node QQ604, without explicitly mentioning any intermediate devices or the precise routing of messages via these devices.

[0500] As an example of data transmission via an OTT connection QQ650, in step QQ608, host QQ602 provides user data, which can be performed by running a host application. In some embodiments, the user data is associated with a specific human user interacting with UE QQ606. In other embodiments, the user data is associated with UE QQ606 sharing data with host QQ602 without explicit human interaction. In step QQ610, host QQ602 initiates a transmission carrying user data to UE QQ606. Host QQ602 may initiate the transmission in response to a request sent by UE QQ606. This request may be caused by human interaction with UE QQ606 or by an operation of a client application running on UE QQ606. According to the teachings of the embodiments described in this disclosure, the transmission may be carried out via network node QQ604. Therefore, in step QQ612, according to the teachings of the embodiments described throughout this disclosure, network node QQ604 transmits the user data carried in the transmission initiated by host QQ602 to UE QQ606. In step QQ614, UE QQ606 receives user data carried in the transmission. This reception can be performed by a client application running on UEQQ606, which is associated with a host application running on host QQ602.

[0501] In some examples, UE QQ606 runs a client application that provides user data to host QQ602. The user data can be provided as a reaction or response to data received from host QQ602. Therefore, in step QQ616, UE QQ606 can provide user data, which can be performed by running the client application. When providing user data, the client application may also consider user input received from the user via the input / output interface of UE QQ606. Regardless of the specific manner in which user data is provided, UE QQ606 initiates a transmission of user data to host QQ602 via network node QQ604 in step QQ618. In step QQ620, in accordance with the teachings of the embodiments described in this disclosure, network node QQ604 receives user data from UE QQ606 and initiates a transmission of the received user data to host QQ602. In step QQ622, host QQ602 receives the user data carried in the transmission initiated by UE QQ606.

[0502] One or more embodiments in various implementations improve the performance of OTT services provided to UE QQ606 using OTT connection QQ650, where wireless connection QQ670 forms the final segment. More specifically, in some embodiments herein, it can provide a coordinated approach for NRF and NF consumers to perform NF discovery. In some embodiments herein, it can eliminate ambiguity in the behavior of the NRF in processing the request and the NF consumer in processing the search results when the query parameters provided by the NF consumer may not be supported by the NRF. In some embodiments herein, it can avoid network traffic waste and negative KPIs caused by service request rejection.

[0503] In the example scenario, host QQ602 can collect and analyze plant status information. As another example, host QQ602 can process audio and video data that may have been retrieved from the UE for map creation. As another example, host QQ602 can collect and analyze real-time data to assist in controlling traffic congestion (e.g., controlling traffic lights). As another example, host QQ602 can store surveillance video uploaded by the UE. As another example, host QQ602 can store or control access to media content such as video, audio, VR, or AR that can be broadcast, multicast, or unicast to the UE. As other examples, host QQ602 can be used for energy pricing, remote control of non-time-critical power loads to balance generation demand, location services, presentation services (compiling charts, etc., based on data collected from remote devices), or any other function that collects, retrieves, stores, analyzes, and / or transmits data.

[0504] In some examples, a measurement process may be provided to monitor data rate, latency, and other factors that one or more embodiments improve upon. Optional network functions may also exist for reconfiguring the OTT connection QQ650 between host QQ602 and UE QQ606 in response to changes in measurement results. The measurement process and / or the network functions for reconfiguring the OTT connection may be implemented in the software and hardware of host QQ602 and / or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or associated with other devices through which the OTT connection QQ650 traverses; the sensors may participate in the measurement process by providing values ​​of the exemplified monitored quantities described above or by providing values ​​of other physical quantities, which the software may calculate or estimate based on the values ​​of those other physical quantities. Reconfiguration of the OTT connection QQ650 may include message formatting, retransmission settings, preferred routing, etc.; reconfiguration does not require a direct change to the operation of network node QQ604. Such processes and functions are known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling, which helps host QQ602 measure throughput, propagation time, latency, etc. Measurements can be achieved by having the software use an OTT connection to transmit messages (especially empty or "virtual" messages) via QQ650, while simultaneously monitoring transmission time, errors, etc.

[0505] While the computing devices described herein (e.g., UE, network node, host) may include the hardware component combinations shown, other embodiments may include computing devices with different component combinations. It will be understood that these computing devices may include any suitable hardware and / or software combination required to perform the tasks, features, functions, and methods disclosed herein. The determination, computation, acquisition, or similar operations described herein may be performed by processing circuitry that processes information by, for example, converting acquired information into other information, comparing the acquired or converted information with information stored in a network node, and / or performing one or more operations based on the acquired or converted information, and making determinations based on the results of said processing. Furthermore, although components are depicted as single boxes located within larger boxes or nested within multiple boxes, in practice, a computing device may include multiple different physical components constituting a single illustrated component, and functionality may be partitioned between individual components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of a component may be partitioned between processing circuitry and the communication interface. In another example, non-computationally intensive functionality of any such component may be implemented in software or firmware, while computationally intensive functionality may be implemented in hardware.

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

[0507] Example 1. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising:

[0508] Processing circuitry is configured to provide user data; and

[0509] A network interface is configured to initiate the transmission of user data to a network node in a cellular network for transmission to a user equipment (UE). The network node has a communication interface and processing circuitry, which is configured to perform any operations associated with the network node as described above to send user data from the host to the UE.

[0510] Example 2. The host according to the foregoing embodiments, wherein:

[0511] The host's processing circuitry is configured to run host applications that provide user data; and

[0512] The UE includes processing circuitry configured to run a client application associated with the host application to receive transmissions of user data from the host.

[0513] Example 3. A method implemented in a host, the host being configured to operate in a communication system, the communication system further including a network node and a user equipment (UE), the method comprising:

[0514] Provide user data to the UE; and

[0515] Transmission of user data to a UE is initiated via a cellular network including the network node, wherein the network node performs operations associated with the network node as described above to send the user data from the host to the UE.

[0516] Example 4. The method according to the foregoing embodiments further includes transmitting user data provided by the host to the UE at the network node.

[0517] Example 5. The method according to any of the first two examples, wherein the user data is provided at the host by running a host application that interacts with a client application running on the UE, the client application being associated with the host application.

[0518] Example 6. A communication system configured to provide over-the-top (OTT) services, the communication system comprising:

[0519] The host includes:

[0520] Processing circuitry is configured to provide user data to a user equipment (UE), the user data being associated with an over-the-top service; and

[0521] A network interface is configured to initiate the transmission of user data to a cellular network node for transmission to a UE. The network node has a communication interface and processing circuitry, which is configured to perform any operations related to the network node as described above to send user data from the host to the UE.

[0522] Example 7. The communication system according to the foregoing embodiments further includes:

[0523] The network node; and / or

[0524] The user equipment.

[0525] Example 8. A communication system according to the preceding two embodiments, wherein: the host's processing circuitry is configured to run a host application, thereby providing user data; and

[0526] The host application is configured to interact with a client application running on the UE, which is associated with the host application.

[0527] Example 9. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising:

[0528] The processing circuitry is configured to initiate the reception of user data; and

[0529] A network interface is configured to receive user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any operations related to the network node as described above in order for the host to receive user data from the user equipment (UE).

[0530] Example 10. The host according to the first two examples, wherein:

[0531] The host's processing circuitry is configured to run host applications, thereby providing user data; and

[0532] The host application is configured to interact with a client application running on the UE, which is associated with the host application.

[0533] Example 11. The host according to any of the first two examples, wherein initiating the reception of user data includes requesting user data.

[0534] Example 12. A method implemented by a host configured to operate in a communication system, the communication system further including a network node and a user equipment (UE), the method comprising:

[0535] At the host, the reception of user data from the UE is initiated. This user data originates from a transmission that the network node has already received from the UE. The network node performs operations related to the network node as described above in order to receive user data from the UE for the host.

[0536] Example 13. The method according to the foregoing embodiments further includes sending the received user data to the host at the network node.

[0537] Example 14. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising:

[0538] Processing circuitry is configured to provide user data; and

[0539] A network interface is configured to initiate the transmission of user data to a cellular network for transmission to a user equipment (UE), wherein the UE includes a communication interface and processing circuitry, and the UE's communication interface and processing circuitry are configured to perform any operations related to the UE as described above to receive user data from a host.

[0540] Example 15. The host according to the foregoing embodiments, wherein the cellular network further includes a network node configured to communicate with the UE to send user data from the host to the UE.

[0541] Example 16. The host according to the first two examples, wherein:

[0542] The host's processing circuitry is configured to run host applications, thereby providing user data; and

[0543] The host application is configured to interact with a client application running on the UE, which is associated with the host application.

[0544] Example 17. A method implemented by a host operating in a communication system, the communication system further including a network node and a user equipment (UE), the method comprising:

[0545] Provide user data to the UE; and

[0546] The transmission of user data to the UE is initiated via a cellular network including the network node, wherein the UE performs any operations related to the UE as described above to receive user data from the host.

[0547] Example 18. The method according to the foregoing embodiments further includes:

[0548] At the host, a host application associated with the client application running on the UE is run to receive user data from the UE.

[0549] Example 19. The method according to the foregoing embodiments further includes:

[0550] At the host, input data is sent to the client application running on the UE, which is provided by the host application.

[0551] User data is provided by the client application in response to input data from the host application.

[0552] Example 20. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising:

[0553] The processing circuitry is configured to use user data; and

[0554] The network interface is configured to receive the transmission of user data from the user equipment (UE) to the cellular network.

[0555] The UE includes a communication interface and processing circuitry, which are configured to perform any operations related to the UE as described above to send user data to the host.

[0556] Example 21. The host according to the foregoing embodiments, wherein the cellular network further includes a network node configured to communicate with the UE to send user data from the UE to the host.

[0557] Example 22. The host according to the first two examples, wherein:

[0558] The host's processing circuitry is configured to run host applications, thereby providing user data; and

[0559] The host application is configured to interact with a client application running on the UE, which is associated with the host application.

[0560] Example 23. A method implemented by a host configured to operate in a communication system, the communication system further including network nodes and user equipment (UE), the method comprising:

[0561] At the host, user data sent by the UE to the host via the network node is received, wherein the UE performs any operations related to the UE as described above to send the user data to the host.

[0562] Example 24. The method according to the foregoing embodiments further includes:

[0563] At the host, a host application associated with the client application running on the UE is run to receive user data from the UE.

[0564] Example 25. The method according to the foregoing embodiments further includes:

[0565] At the host, input data is sent to the client application running on the UE, which is provided by the host application.

[0566] This user data is provided by the client application in response to input data from the host application.

[0567] The term unit or module may have the conventional meaning in the field of electronic, electrical and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, outputs and / or display functions, and the like, as described herein.

[0568] According to one aspect of this disclosure, a computer program product is provided, which is tangibly stored on a computer-readable storage medium and includes instructions that, when executed on at least one processor, cause the at least one processor to perform any of the methods described above.

[0569] According to one aspect of this disclosure, a computer-readable storage medium is provided that stores instructions, when executed on at least one processor, causing the at least one processor to perform any of the methods described above.

[0570] Furthermore, this disclosure may also provide a carrier containing the aforementioned computer program, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium. The computer-readable storage medium may be, for example, an optical disc or an electronic storage device, such as RAM (random access memory), ROM (read-only memory), flash memory, magnetic tape, CD-ROM, DVD, Blu-ray disc, etc.

[0571] The techniques described herein can be implemented in various ways, such that the means for implementing one or more functions of the corresponding apparatus described in the embodiments includes not only prior art components, but also components for implementing one or more functions of the corresponding apparatus described in the embodiments, and may include separate components for each individual function, or components that can be configured to perform two or more functions. For example, these techniques can be implemented in hardware (one or more apparatuses), firmware (one or more apparatuses), software (one or more modules), or a combination thereof. For firmware or software, implementation can be accomplished by modules (e.g., processes, functions, etc.) that perform the functions described herein.

[0572] Exemplary embodiments of the present document have been described above with reference to block diagrams and flowcharts of methods and apparatus. It will be understood that each block of the block diagrams and flowcharts, as well as combinations of blocks in the block diagrams and flowcharts, can be implemented by various components including computer program instructions. These computer program instructions can be loaded onto a general-purpose computer, a special-purpose computer, or other programmable data processing equipment to produce a machine, such that the instructions, which execute on the computer or other programmable data processing equipment, create components for implementing the functions specified in the flowchart blocks or blocks.

[0573] Furthermore, although the operations are depicted in a specific order, this should not be construed as requiring that these operations be performed in the specific order shown or sequentially, or requiring that all illustrated operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, these should not be construed as limiting the scope of the subject matter described herein, but rather as descriptions of features that may be specific to particular embodiments. Certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0574] While this specification contains numerous specific implementation details, these should not be construed as limiting the scope of any implementation or the scope that may be claimed, but rather as descriptions of features that may be specific to particular embodiments of a particular implementation. Some features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually in multiple embodiments or in any suitable sub-combination. Furthermore, while the features described above may be described as functioning in certain combinations, and even initially claimed in this way, in certain circumstances one or more features from the claimed combination may be removed from the combination, and the claimed combination may be for sub-combinations or variations thereof.

[0575] It will be apparent to those skilled in the art that the inventive concept can be implemented in various ways with advancements in technology. The above embodiments are given for description purposes only and not for limitation of this disclosure, and it should be understood that modifications and variations can be made without departing from the spirit and scope of this disclosure, as will be readily apparent to those skilled in the art. Such modifications and variations are considered to be within the scope of this disclosure and the appended claims. The scope of protection of this disclosure is defined by the appended claims.

Claims

1. A method (200) performed by a network function NF, comprising: Send a (202) first NF discovery request to the first network repository function (NRF) including at least one query parameter; as well as Receive (204) first NF discovery response from the first NRF; The first NF discovery response includes a search result and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among the at least one query parameter for the search result.

2. The method according to claim 1, further comprising: Obtain (212) information about one or more query parameters supported by the first NRF; as well as Determine (214) one or more query parameters that are not supported by the first NRF. The at least one query parameter includes at least one of the one or more query parameters supported by the first NRF, and does not include the one or more query parameters not supported by the first NRF.

3. The method according to claim 2, wherein, The process of obtaining information about one or more query parameters supported by the first NRF includes: Send (222) a first bootstrapping request or a second NF discovery request to the first NRF; and Receive (224) a first bootstrap response or a second NF discovery response from the first NRF, including information about one or more query parameters supported by the first NRF.

4. The method according to any one of claims 1-3, further comprising: Obtain (232) information about one or more query parameters supported by the second NRF; as well as Determine (234) one or more query parameters that are not supported by the second NRF. Wherein, when the first NF discovery request contains the network identifier of the second NRF, the at least one query parameter includes at least one of the one or more query parameters supported by the second NRF, and does not include the one or more query parameters not supported by the second NRF.

5. The method according to claim 4, wherein, The process of obtaining information about one or more query parameters supported by the second NRF includes: Send (242) a second bootstrapping request or a third NF discovery request, including the network identifier of the second NRF, to the first NRF; and Receive (244) from the first NRF a second bootstrap response or a third NF discovery response including information about one or more query parameters supported by the second NRF.

6. The method according to claim 4 or 5, wherein, The first NRF includes a visiting NRF and the second NRF includes a home NRF, or the first NRF includes a home NRF and the second NRF includes a visiting NRF.

7. The method according to claim 1, wherein the method further comprises: Based on the at least one ignored unsupported query parameter and / or the at least one ignored supported query parameter, determine (256) whether the search result is useful.

8. The method according to claim 1, wherein, The first NF discovery request further includes first information indicating whether a query parameter in the at least one query parameter is critical to the service logic; and The first NF discovery response includes at least one of the following: Search results generated by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter in the at least one query parameter; The rejection message and the reason why the key query parameter in at least one of the query parameters is not supported; or Redirection information when a key query parameter in at least one of the query parameters is not supported.

9. The method according to claim 8, wherein, The first information includes at least one of the following: A new query parameter that contains a list of names of at least one key query parameter; A Hypertext Transfer Protocol (HTTP) header containing a list of names of at least one key query parameter; or Patterns or extensions used to indicate key information are placed directly on the query parameter names.

10. A method (300) executed by a first NRF, comprising: Receive a first NF discovery request (302) from the NF, including at least one query parameter; as well as Send a (304) first NF discovery response to the NF; The first NF discovery response includes a search result and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among the at least one query parameter for the search result.

11. The method according to claim 10, wherein, The at least one query parameter includes at least one of one or more query parameters supported by the first NRF, and does not include one or more query parameters not supported by the first NRF.

12. The method of claim 11, further comprising: Receive (312) a first boot request or a second NF discovery request from the NF; as well as Send (314) a first bootstrap response or a second NF discovery response to the NF, including information about the one or more query parameters supported by the first NRF.

13. The method according to claim 10, wherein, When the first NF discovery request contains the network identifier of the second NRF, the at least one query parameter includes at least one of one or more query parameters supported by the second NRF, and does not include one or more query parameters not supported by the second NRF.

14. The method of claim 13, further comprising: Receive (322) a second bootstrapping request or a third NF discovery request from the NF, including the network identifier of the second NRF; Send a (324) third boot request or a fourth NF discovery request to the second NRF; Receive (326) a third bootstrap response or a fourth NF discovery response from the second NRF, including information about the one or more query parameters supported by the second NRF; as well as Send (328) a second bootstrap response or a third NF discovery response to the NF, including the information about the one or more query parameters supported by the second NRF.

15. The method according to claim 13 or 14, wherein, The first NRF includes a visiting NRF and the second NRF includes a home NRF, or the first NRF includes a home NRF and the second NRF includes a visiting NRF.

16. The method of claim 10, wherein, The first NF discovery request further includes first information indicating whether a query parameter in the at least one query parameter is critical to the service logic; as well as The first NF discovery response includes: Search results generated by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter in the at least one query parameter; or Rejection information and reason information indicating that a key query parameter in at least one of the query parameters is not supported; or Redirection information when a key query parameter in at least one of the query parameters is not supported.

17. The method according to claim 16, wherein, The first information includes at least one of the following: A new query parameter that contains a list of names of at least one key query parameter; An HTTP header containing a list of names of at least one key query parameter; or Patterns or extensions used to indicate key information are placed directly on the query parameter names.

18. The method according to any one of claims 10-17, wherein, When the first NF discovery request contains the network identifier of the second NRF, the method further includes: Send (332) a fifth NF discovery request, including the at least one query parameter, to the second NRF; and Receive (334) Fifth NF discovery response from the second NRF.

19. The method according to claim 18, wherein, The fifth NF discovery response includes search results and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among the at least one query parameter for the search results.

20. The method of claim 18, wherein The fifth NF discovery request further includes first information indicating whether a query parameter in the at least one query parameter is critical to the service logic, and The fifth NF discovery response includes at least one of the following: Search results generated by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter in the at least one query parameter; The rejection message and the reason why the key query parameter in at least one of the query parameters is not supported; or Redirection information when a key query parameter in at least one of the query parameters is not supported.

21. The method according to any one of claims 10-17, wherein, When the first NF discovery request does not contain the network identifier of the second NRF, the method further includes at least one of the following: The search results (342) are determined by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter among the at least one query parameter. Based on the criticality of the unsupported query parameter in the at least one query parameter, determine (344) whether to reject or accept the first NF discovery request, or When a key query parameter in at least one of the query parameters is not supported, determine (346) redirection information.

22. A method (400) executed by a second NRF, comprising: Receive (402) a fifth NF discovery request including at least one query parameter from the first NRF; as well as Send a (404) fifth NF discovery response to the first NRF; The search results (406) are determined by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter among the at least one query parameter.

23. The method according to claim 22, wherein, The at least one query parameter includes at least one of one or more query parameters supported by the second NRF, and does not include one or more query parameters not supported by the second NRF.

24. The method according to claim 22 or 23, further comprising: Receive (412) a third boot request or a fourth NF discovery request from the first NRF; as well as Send (414) a third bootstrap response or a fourth NF discovery response to the first NRF, including information about the one or more query parameters supported by the second NRF.

25. The method according to any one of claims 22-24, wherein, The first NRF includes a visiting NRF and the second NRF includes a home NRF, or the first NRF includes a home NRF and the second NRF includes a visiting NRF.

26. The method according to any one of claims 22-25, wherein, The fifth NF discovery response includes search results and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among the at least one query parameter for the search results.

27. The method according to any one of claims 22-26, wherein The fifth NF discovery request further includes first information indicating whether a query parameter in the at least one query parameter is critical to the service logic, and The fifth NF discovery response includes at least one of the following: Search results generated by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter in the at least one query parameter; The rejection message and the reason why the key query parameter in at least one of the query parameters is not supported; or Redirection information when a key query parameter in at least one of the query parameters is not supported.

28. The method according to any one of claims 22-27, further comprising: Based on the criticality of the unsupported query parameter in the at least one query parameter, determine (422) whether to reject or accept the fifth NF discovery request, or When a key query parameter in at least one of the query parameters is not supported, determine (424) redirection information.

29. An NF (900) comprising: Processor (921); as well as A memory (922) coupled to the processor (921) stores instructions executable by the processor (921), thereby enabling the NF (900) to: Send a first NF discovery request, including at least one query parameter, to the first network repository function (NRF); and Receive a first NF discovery response from the first NRF; The first NF discovery response includes a search result and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among the at least one query parameter for the search result.

30. The NF according to claim 29, wherein, The NF is further operable to perform the method of any one of claims 2 to 9.

31. A first NRF (900), comprising: Processor (921); as well as A memory (922) coupled to the processor (921) stores instructions executable by the processor (921), thereby enabling the first NRF (900) to operate as follows: Receive a first NF discovery request from the NF, which includes at least one query parameter; as well as Send a first NF discovery response to the NF; The first NF discovery response includes a search result and information indicating at least one ignored unsupported query parameter and / or at least one ignored supported query parameter among the at least one query parameter for the search result.

32. The first NRF according to claim 31, wherein, The first NRF is further operable to perform the method of any one of claims 11 to 21.

33. A second NRF (900), comprising: Processor (921); as well as A memory (922) coupled to the processor (921) stores instructions executable by the processor (921), thereby enabling the second NRF (900) to: Receive a fifth NF discovery request from the first NRF, including at least one query parameter; as well as Send a fifth NF discovery response to the first NRF; The search results are determined by ignoring at least one non-critical unsupported query parameter and / or at least one non-critical supported query parameter among the at least one query parameter.

34. The second NRF according to claim 33, wherein, The second NRF is further operable to perform the method of any one of claims 23 to 28.

35. A computer-readable storage medium storing instructions, which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 28.

36. A computer program product comprising instructions, which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 28.

Images