Method and apparatus for handling services - Patents.com

Abstract

An embodiment of the present disclosure provides a method and apparatus for service handling. The method performed in a first network entity includes sending a first request targeting a resource context or a session context to a second network entity. The method further includes receiving a first rejection response from the second network entity or an alternative second network entity. The first rejection response includes information having a first parameter indicating whether the first request should be retried with the second network entity or to any other alternative second network entity and / or a second parameter indicating whether to use the alternative second network entity for subsequent requests targeting the same resource context or session context, and the first rejection response including the information having the second parameter is received from the alternative second network entity.

Description

[Technical field]

[0001] TECHNICAL FIELD The non-limiting exemplary embodiments of the present disclosure relate generally to the field of communications, and more particularly, to a method and apparatus for handling services. [Background technology]

[0002] This section introduces aspects that may facilitate a better understanding of the present disclosure. Accordingly, the statements in this section are to be read in this light and not understood as admissions about what is in the prior art or what is not in the prior art.

[0003] Network function (NF) instances are deployed such that several network function instances are present in an NF set to provide distribution, redundancy, and scalability as a set of NF instances together. The same is true for NF services. This is achieved when equivalent NFs and NF services share the same context data or by network function / NF service context transfer procedures. For example, 3rd Generation Partnership Project (3GPP) TS 23.501 V17.0.0, which is incorporated herein by reference in its entirety, supports redundancy with NF sets, which allows another NF (service) instance to take over an existing resource context or session context created / managed by another instance in the same NF set. Summary of the Invention

[0004] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0005] When an NF consumer or a service communication proxy (SCP) attempts to access a resource context or a session context on an NF and detects that the NF is no longer available (e.g., by an error response during the operation of the service invoked on the NF or an NF status notification via a network repository function (NRF)), the NF consumer or SCP may reselect an alternative NF instance in the same NF set and (re)send the service request to the alternative NF instance. The alternative NF instance restores the resource context or session context and processes the service request to continue the service. If the reselection is performed by the SCP, the SCP indicates the alternative NF instance ID (identifier) ​​as well as the target API (application programming interface) route to the NF consumer. The NF consumer considers that the resource context or session context is currently hosted by an alternative NF instance and invokes the service operation on the resource context or session context using the alternative NF instance. The same behavior is applicable to NF consumer reselection for notifications, where the notification request is sent by the NF producer and the reselection is performed by the NF producer (or SCP).

[0006] If the reselected alternative NF instance successfully processes the service request and responds with a positive status code to the sender of the service request (NF consumer or SCP), the sender can be sure that the alternative NF instance has successfully taken over the resource context or session context, and therefore sends subsequent messages for the resource context or session context towards the alternative NF instance.

[0007] However, in case of failures, the scenario may be different: for example, if a service request fails the HyperText Transfer Protocol (HTTP) stack schema check or fails the OpenAPI inspection, the service request is rejected with a corresponding error code and no higher level application logic is involved, i.e. the alternative NF instance does not attempt to restore the resource context or the session context at all.

[0008] If an alternative NF instance is busy (e.g., overloaded) when it receives a service request and is unable to process it, it may either reject the service request directly without restoring any resource or session context, or it may restore the resource or session context according to a policy, e.g., checking whether it is related to a high priority service that should be processed.

[0009] If the service request is correct (e.g., passes the HTTP stack schema check) and the alternative NF instance is not overloaded, the alternative NF instance will restore the resource or session context and continue processing the service request. However, the service request may ultimately fail due to application logic, e.g., some resources are not allowed to be modified at that time.

[0010] In particular, if a service request fails, it is very difficult for the sender of the service request to identify whether an alternative NF instance has already taken over the resource context or session context. For example, it is impossible for an SCP that does not understand the business logic to determine whether an alternative NF instance has already taken over the resource context or session context. Without identifying whether an alternative NF instance has already taken over the resource context / session context, the NF consumer or SCP will not know to which NF a subsequent message regarding the resource context / session context should be sent, for example, to the alternative NF or the original NF or another alternative NF.

[0011] Furthermore, for some errors, further retries on another alternative NF are not recommended, for example when a service request is rejected due to an application logic error or a state conflict, in which case the same result is returned regardless of the NF instance hosting the resource or session context.

[0012] To overcome or mitigate at least one of the above-mentioned problems or other problems, embodiments of the present disclosure propose an improved service processing solution.

[0013] According to one embodiment, a mechanism is provided in 5GC to enable an alternative NF to explicitly indicate the message sender of a request (e.g., an HTTP request) to address existing context data (e.g., resource context or session context) whose context data has been inherited by the alternative NF.

[0014] According to one embodiment, a mechanism in 5GC is provided that allows an alternative NF to explicitly indicate to the entity (the NF consumer, if direct communication applies, or the SCP, if indirect communication applies) that decides to perform a reselection, and that further reselections of the alternative NF should be avoided, since the same result can be obtained.

[0015] According to one embodiment, the network function producer may provide an indication in the negative service action response / notification response that the relevant resource context or session context has been assumed by the network function producer and whether further reselection of the network function producer should be avoided.

[0016] In a first aspect of the present disclosure, a method is provided that is performed in a first network entity. The method includes sending a first request to a second network entity, the first request targeting a resource context or a session context. The method further includes receiving a first rejection response from the second network entity or an alternative second network entity. The first rejection response indicates that the first request was not received by the second network entity. and any other alternative second network entity Using either Should it be retried? No and / or a second parameter indicating whether to use an alternative second network entity for subsequent requests targeting the same resource context or session context. A first rejection response including the information having the second parameter is received from the alternative second network entity.

[0017] According to one embodiment, two or more of the second network entities and / or alternative second network entities are grouped into a network function set, a network function service set, or a network function service instance set, and two or more of the second network entities and / or alternative second network entities are interchangeable and share the same resource context or session context.

[0018] According to one embodiment, the information includes whether the first request is rejected due to an application logic error or a state conflict, or whether the resource context or session context is Alternative and whether it has been taken over by a second network entity.

[0019] According to one embodiment, the method further comprises the step of: the first rejection response includes information having a first parameter, and the first parameter indicates whether the first request should be retried using the second network entity or to any other alternative second network entity. do not have and avoiding a retry of the first request if the first request indicates that the second request is not successful.

[0020] According to one embodiment, the method further includes, if the first rejection response includes information having the second parameter and the second parameter indicates using the alternative second network entity for subsequent requests targeting the same resource context or session context, using the alternative second network entity for subsequent requests targeting the same resource context or session context.

[0021] According to one embodiment, the second network entity or the alternative second network entity is a HyperText Transfer Protocol server and the first network entity is a HyperText Transfer Protocol client, and communication between the second network entity or the alternative second network entity and the first network entity is direct communication without using a service communication proxy.

[0022] According to one embodiment, the second network entity or the alternative second network entity is a HyperText Transfer Protocol server and the first network entity is a service communication proxy.

[0023] According to one embodiment, the method further includes receiving a second request from the HyperText Transfer Protocol client. Sending the first request to the second network entity, the first request targeting the resource context or the session context, is performed in response to receiving the second request from the HyperText Transfer Protocol client. The method further includes forwarding the first rejection response to the HyperText Transfer Protocol client as a response to the second request in response to receiving the first rejection response from the second network entity.

[0024] According to one embodiment, the second request includes an application program interface route of the second network entity.

[0025] According to one embodiment, the second request includes an application program interface route of another second network entity, and the method further includes determining that the other second network entity is not reachable and / or cannot handle the second request. The method further includes reselecting a second network entity based on the determination that the other second network entity is not reachable and / or cannot handle the second request. If the first rejection response includes information having a second parameter, and the second parameter indicates to use the second network entity or an alternative second network entity for a subsequent request targeting the same resource context or session context, the method further includes adding an application program interface route of the second network entity or an alternative second network entity to the first rejection response.

[0026] According to one embodiment, the information includes implicit or explicit information.

[0027] According to one embodiment, the first request includes an application program interface route of the second network entity.

[0028] According to one embodiment, the information is carried by a new HyperText Transfer Protocol header, or 3gpp-Sbi-Target-apiRoot, or 3gpp-Sbi-Binding.

[0029] In a second aspect of the present disclosure, a method is provided that is performed by a second network entity or an alternative second network entity, the method including receiving a first request from the first network entity, the first request targeting a resource context or a session context, the method further including transmitting a first rejection response to the first network entity, where the first rejection response indicates that the first request is not a valid request from the second network entity. and any other alternative second network entity Using either Should it be retried? No and / or a second parameter indicating whether to use an alternative second network entity for a subsequent request targeting the same resource context or session context. A first rejection response including the information having the second parameter is received from the alternative second network entity.

[0030] According to one embodiment, two or more of the second network entities and / or alternative second network entities are grouped into a network function set, a network function service set, or a network function service instance set, and two or more of the second network entities and / or alternative second network entities are interchangeable and share the same resource context or session context.

[0031] According to one embodiment, the information includes whether the first request is rejected due to an application logic error or a state conflict, or whether the resource context or session context is Alternative and whether it has been taken over by a second network entity.

[0032] According to one embodiment, the second network entity or the alternative second network entity is a HyperText Transfer Protocol server and the first network entity is a HyperText Transfer Protocol client, and communication between the second network entity or the alternative second network entity and the first network entity is direct communication without using a service communication proxy.

[0033] According to one embodiment, the second network entity or the alternative second network entity is a HyperText Transfer Protocol server and the first network entity is a service communication proxy.

[0034] According to one embodiment, the information includes implicit or explicit information.

[0035] According to one embodiment, the implicit information includes an application program interface route of the second network entity.

[0036] According to one embodiment, the first request includes an application program interface route of the second network entity.

[0037] According to one embodiment, the first rejection response includes an application program interface route of the second network entity or an alternative second network entity.

[0038] According to one embodiment, the information is carried by a new HyperText Transfer Protocol header, or 3gpp-Sbi-Target-apiRoot, or 3gpp-Sbi-Binding.

[0039] In a third aspect of the present disclosure, a method is provided that is performed by a third network entity. The method includes sending a request targeting a resource context or a session context to a service communication proxy. The method further includes receiving a rejection response from the service communication proxy. The rejection response includes information having a first parameter indicating whether the request should be retried with the second network entity or to any other alternative second network entity and / or a second parameter indicating whether the alternative second network entity should be used for subsequent requests targeting the same resource context or session context. A rejection response including information having the second parameter is received from the alternative second network entity. The method further includes using the alternative second network entity for subsequent requests targeting the same resource context or session context if the rejection response includes information having the second parameter, and the second parameter indicates using the alternative second network entity for subsequent requests targeting the same resource context or session context.

[0040] According to one embodiment, the request includes an application program interface route of the second network entity.

[0041] According to one embodiment, the request includes an application program interface route of another second network entity.

[0042] According to one embodiment, two or more of the second network entities and / or alternative second network entities are grouped into a network function set, a network function service set, or a network function service instance set, and two or more of the second network entities and / or alternative second network entities are interchangeable and share the same resource context or session context.

[0043] According to one embodiment, the information includes whether the request is rejected due to an application logic error or a state conflict, or whether the resource context or session context is Alternative and whether it has been taken over by a second network entity.

[0044] According to one embodiment, the information includes implicit or explicit information.

[0045] According to one embodiment, the implicit information includes an application program interface route of the second network entity.

[0046] According to one embodiment, the reject response includes an application program interface route of the second network entity or an alternative second network entity.

[0047] According to one embodiment, the information is carried by a new HyperText Transfer Protocol header, or 3gpp-Sbi-Target-apiRoot, or 3gpp-Sbi-Binding.

[0048] According to one embodiment, the third network entity is a HyperText Transfer Protocol client.

[0049] In a fourth aspect of the present disclosure, a first network entity is provided. The first network entity has a processor and a memory coupled to the processor. The memory includes instructions executable by the processor. The first network entity is operable to send a first request to a second network entity, the first request targeting a resource context or a session context. The first network entity is further operable to receive a first rejection response from the second network entity or an alternative second network entity. The first rejection response indicates that the first request has been rejected by the second network entity. and any other alternative second network entity Using either Should it be retried? No and / or a second parameter indicating whether to use an alternative second network entity for subsequent requests targeting the same resource context or session context. A first rejection response including the information having the second parameter is received from the alternative second network entity.

[0050] In a fifth aspect of the present disclosure, a second network entity or an alternative second network entity is provided. The second network entity or the alternative second network entity has a processor and a memory coupled to the processor. The memory includes instructions executable by the processor. The second network entity or the alternative second network entity is operable to receive a first request from the first network entity, the first request targeting a resource context or a session context. The second network entity or the alternative second network entity is further operable to transmit a first rejection response to the first network entity. The first rejection response indicates that the first request is not accepted by the second network entity. andany other alternative second network entity Using either Should it be retried? No and / or a second parameter indicating whether to use an alternative second network entity for subsequent requests targeting the same resource context or session context. A first rejection response including the information having the second parameter is received from the alternative second network entity.

[0051] In a sixth aspect of the present disclosure, a third network entity is provided. The third network entity has a processor and a memory coupled to the processor. The memory includes instructions executable by the processor. The third network entity is operable to send a request targeting a resource context or a session context to the service communication proxy. The third network entity is further operable to receive a rejection response from the service communication proxy. The rejection response includes information having a first parameter indicating whether the first request should be retried with the second network entity or to any other alternative second network entity, and / or a second parameter indicating whether the alternative second network entity should be used for a subsequent request targeting the same resource context or session context. The rejection response including the information having the second parameter is received from the alternative second network entity. The third network entity is further operable, if the reject response includes information having the second parameter and the second parameter indicates to use the alternative second network entity for subsequent requests targeting the same resource context or session context, to use the alternative second network entity for subsequent requests targeting the same resource context or session context.

[0052] In a seventh aspect of the present disclosure, a first network entity is provided. The first network entity has a sending module configured to send a first request targeting a resource context or a session context to a second network entity. The first network entity further has a first receiving module configured to receive a first rejection response from the second network entity or an alternative second network entity. The first rejection response indicates that the first request was not received by the second network entity. and any other alternative second network entity Using either Should it be retried? No and / or a second parameter indicating whether to use an alternative second network entity for subsequent requests targeting the same resource context or session context. A first rejection response including the information having the second parameter is received from the alternative second network entity.

[0053] According to one embodiment, the first network entity further comprises an avoidance module configured to avoid retrying the first request if the first rejection response includes information having a first parameter, where the first parameter indicates that the first request should be retried using the second network entity or to any other alternative second network entity. do not have This indicates that.

[0054] According to an embodiment, the first network entity further comprises a using module configured to, when the first rejection response includes information having the second parameter and the second parameter indicates to use the alternative second network entity for subsequent requests targeting the same resource context or session context, use the alternative second network entity for subsequent requests targeting the same resource context or session context.

[0055] According to one embodiment, the first network entity further comprises a second receiving module configured to receive a second request from the HyperText Transfer Protocol client, and the sending module is configured to send a first request targeting the resource context or the session context to the second network entity in response to receiving the second request from the HyperText Transfer Protocol client.

[0056] According to one embodiment, the first network entity further comprises a forwarding module configured to, in response to receiving the first rejection response from the second network entity, forward the first rejection response to the HyperText Transfer Protocol client as a response to the second request.

[0057] The first network entity further includes a determining module configured to determine that the other second network entity is not reachable and / or that the other second network entity is unable to process the second request.

[0058] The first network entity further has a reselection module configured to reselect the second network entity based on a determination that the other second network entity is not reachable and / or the other network entity is unable to process the second request.

[0059] The first network entity further has a first adding module configured to add an application program interface route of the second network entity or the alternative second network entity to the first rejection response when the first rejection response includes information having the second parameter and the second parameter indicates to use the second network entity or the alternative second network entity for a subsequent request targeting the same resource context or session context.

[0060] In an eighth aspect of the present disclosure, a second network entity or an alternative second network entity according to an embodiment of the present disclosure is provided. The second network entity or the alternative second network entity has a receiving module configured to receive a first request from the first network entity, the first request targeting a resource context or a session context. The second network entity or the alternative second network entity further has a transmitting module configured to transmit a first rejection response to the first network entity. The first rejection response indicates that the first request is not a valid request from the second network entity. and any other alternative second network entity Using either Should it be retried? Noand / or a second parameter indicating whether to use an alternative second network entity for subsequent requests targeting the same resource context or session context. A first rejection response including the information having the second parameter is received from the alternative second network entity.

[0061] In a ninth aspect of the present disclosure, a third network entity is provided. The third network entity has a sending module configured to send a request targeting a resource context or a session context to the service communication proxy. The third network entity further has a receiving module configured to receive a rejection response from the service communication proxy. The rejection response includes information having a first parameter indicating whether the request should be retried with the second network entity or to any other alternative second network entity, and / or a second parameter indicating whether the alternative second network entity should be used for a subsequent request targeting the same resource context or session context. The rejection response including the information having the second parameter is received from the alternative second network entity, and the third network entity further has a using module configured to use the alternative second network entity for a subsequent request targeting the same resource context or session context if the rejection response includes information having the second parameter and the second parameter indicates to use the alternative second network entity for a subsequent request targeting the same resource context or session context.

[0062] In a tenth aspect of the present disclosure, there is provided a computer-readable storage medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform any of the methods according to the first, second and third aspects of the present disclosure.

[0063] In an eleventh aspect of the present disclosure, there is provided a computer program product having instructions which, when executed on at least one processor, cause the at least one processor to perform any of the methods according to the first, second and third aspects of the present disclosure.

[0064] By applying the proposed solution according to the embodiments of the present disclosure, many advantages may be achieved. For example, some embodiments of the present disclosure may enable the second NF to indicate how the first NF (sending a request to the second NF) should send a subsequent request when a current request is rejected by the second NF. For example, the second NF may indicate to the first NF that context data (such as resource context or session context) has been carried over by the second NF or that a second network entity has been used to process a subsequent request from the first NF. The first NF updates the resource URI or session URI by replacing the apiRoot with the apiRoot of the second NF even if the current request is rejected by the second NF. Some embodiments of the present disclosure provide a mechanism to instruct an NF performing NF reselection not to perform NF reselection, which may reduce extra signaling for further NF reselection. The embodiments herein are not limited to the features and advantages described above. Those skilled in the art will recognize additional features and advantages upon reading the following detailed description. [Brief description of the drawings]

[0065] The above and other aspects, features, and advantages of various embodiments of the present disclosure will become more fully apparent from the following detailed description, by way of example, with reference to the accompanying drawings, in which like reference numbers or letters are used to designate similar or equivalent elements, and in which: The drawings are illustrated to facilitate a better understanding of the embodiments of the present disclosure and are not necessarily drawn to scale.

[0066] [Figure 1a] 1 illustrates a schematic diagram of a high-level architecture in a fifth generation network according to an embodiment of the present disclosure.

[0067] [Figure 1b] 1 illustrates a communication model for NF / NF service interaction according to an embodiment of the present disclosure.

[0068] [Diagram 2] 3 shows a flowchart of a method according to an embodiment of the present disclosure.

[0069] [Diagram 3] 3 shows a flowchart of a method according to another embodiment of the present disclosure.

[0070] [Figure 4] 3 shows a flowchart of a method according to another embodiment of the present disclosure.

[0071] [Diagram 5] 3 shows a flowchart of a method according to another embodiment of the present disclosure.

[0072] [Figure 6] 3 shows a flowchart of a method according to another embodiment of the present disclosure.

[0073] [Figure 7] 3 shows a flowchart of a method according to another embodiment of the present disclosure.

[0074] [Figure 8]3 shows a flowchart of a method according to another embodiment of the present disclosure.

[0075] [Figure 9] 1 is a block diagram illustrating an apparatus suitable for use in implementing some embodiments of the present disclosure.

[0076] [Figure 10] 1 is a block diagram illustrating a first network entity according to one embodiment of the present disclosure.

[0077] [Figure 11] 1 is a block diagram illustrating a second network entity according to an embodiment of the present disclosure.

[0078] [Figure 12] 1 is a block diagram illustrating a third network entity according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0079] Hereinafter, the embodiments of the present disclosure will be described in detail with reference to the 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 practice the present disclosure, and do not imply any limitations on the scope of the present disclosure. Throughout this specification, references to features, advantages, or similar words do not imply that all of the features and advantages that may be realized by the present disclosure should be or should be in any single embodiment of the present disclosure. Rather, words referring to features and advantages are understood to mean that the specific features, advantages, or characteristics described in connection with the embodiment are included in at least one embodiment of the present disclosure. Furthermore, the described features, advantages, and characteristics of the present disclosure can be combined in any suitable manner in one or more embodiments. Those skilled in the art will recognize that the present disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other cases, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the present disclosure.

[0080] As used herein, the term "network" refers to a network conforming to any suitable communications 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. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), which includes WCDMA and other variants of CDMA. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM). The OFDMA network may implement wireless 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" may be used interchangeably. Furthermore, communication between two devices in the network may be performed according to any suitable communication protocol, including, but not limited to, communication protocols defined by a standardization organization such as 3GPP. For example, the communication protocol may include first generation (1G), 2G, 3G, 4G, 4.5G, 5G communication protocols, and / or any other protocols currently known or to be developed in the future.

[0081] The term "network device" or "network node" or "network function (NF)" refers to any suitable function that may be implemented in a network entity (physical or virtual) of a communication network. For example, a network function may 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, for example on a cloud infrastructure. For example, a 5G system (5GS) may include multiple NFs such as AMF (Access and Mobility Function), SMF (Session Management Function), AUSF (Authentication Service Function), UDM (Unified Data Management), PCF (Policy Control Function), AF (Application Function), NEF (Network Publishing Function), UPF (User Plane Function) and NRF (Network Repository Function), RAN (Radio Access Network), SCP (Service Communication Proxy), NWDAF (Network Data Analysis Function), NSSF (Network Slice Selection Function), NSSAAF (Network Slice Specific Authentication and Authorization Function).

[0082] References herein to "one embodiment," "an embodiment," "an example embodiment," and the like indicate that the described embodiment may include a particular feature, structure, or characteristic, but not necessarily all embodiments include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, it will be understood that it is within the knowledge of one of ordinary skill in the art to affect such feature, structure, or characteristic in the context of other embodiments, whether or not explicitly described.

[0083] In this specification, terms such as "first" and "second" may be used to describe various elements, but it should be understood that these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element can be referred to as a second element, and similarly, a second element can be referred to as a first element, without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed terms.

[0084] As used herein, the phrase "at least one of A and B" or "at least one of A or B" should be understood to mean "A only, B only, or both A and B." The phrase "A and / or B" should be understood to mean "A only, B only, or both A and B."

[0085] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly dictates otherwise. The terms "have," "having," "comprises," "comprising," "including," and / or "including," as used herein, specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence of one or more other features, elements, and / or components, etc.

[0086] It should be noted that these terms used in this specification are used only to facilitate description and differentiation between nodes, devices, networks, etc. As the technology develops, other terms having similar / same meanings may also be used.

[0087] 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 belongs.

[0088] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are described with respect to a communication system conforming to the exemplary system architecture shown in FIG. 1a-1b. For simplicity, the system architecture of FIG. 1a-1b shows only some exemplary elements. In practice, the communication system may further include any additional elements suitable for facilitating communication between terminal devices, or between a wireless device and another communication device, e.g., a landline telephone, a 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 the terminal device's access to and / or use of services provided by or through the communication system.

[0089] FIG. 1a illustrates a schematic diagram of a high-level architecture in a fifth generation network according to an embodiment of the present disclosure. For example, the fifth generation network may be a 5GS. The architecture of FIG. 1a is the same as FIG. 4.2.3-1 described in 3GPP TS 23.501 V17.0.0. The system architecture of FIG. 1a may include several exemplary elements, such as AUSF, AMF, DN (Data Network), NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE (User Equipment), (R)AN ((Radio) Access Network), SCP (Service Communication Proxy), NSSAAF (Network Slice Specific Authentication and Authorization Function), and NSACF (Network Slice Admission Control Function).

[0090] According to an example embodiment, the UE can establish a signaling connection with the AMF via reference point N1, as shown in Figure 1a. This signaling connection may enable NAS (Non-Access Stratum) signaling exchange between the UE and the core network, which includes a signaling connection between the UE and the (R)AN and an N2 connection between the (R)AN and the AMF for the UE. The (R)AN can communicate with the UPF over reference point N3. The UE can establish a Protocol Data Unit (PDU) session to a DN (a data network, e.g., an operator network or the Internet) via reference point N6 and through the UPF.

[0091] As further shown in FIG. 1a, the exemplary system architecture also includes service-based interfaces, such as Nnrf, Nnef, Nausf, Nudm, Npcf, Namf, Nnsacf, and Nsmf, indicated by NFs, such as NRF, NEF, AUSF, UDM, PCF, AMF, NSACF, and SMF. Additionally, FIG. 1a also illustrates several reference points, such as N1, N2, N3, N4, N6, and N9, that can support interactions between NF services in the NFs. For example, these reference points can be realized by specifying several NF service consumers and providers and their interactions through corresponding NF service-based interfaces to perform certain system procedures.

[0092] The various NFs shown in Figure 1a may be responsible for functions such as session management, mobility management, authentication, security, etc. The AUSF, AMF, DN, NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R)AN, SCP, and NSACF may include functions as defined, for example, in clause 6.2 of 3GPP TS 23.501 V17.0.0.

[0093] As used herein, an NF consumer may be any suitable NF or NF instance that needs to use one or more services provided by another NF. An NF producer may be any suitable NF or NF instance that can provide one or more services to one or more NF consumers. If an NF can provide one or more services to any other NF, the NF may register its NF profile with the NRF.

[0094] FIG. 1b illustrates a communication model for NF / NF service interaction according to an embodiment of the present disclosure.

[0095] A service communication proxy (SCP) as a network element is introduced into the service framework. The routing of service-based interface (SBI) messages for network function (NF) interaction mechanisms may be direct as shown in Model A and Model B of Fig. 1b, or indirect in Model C and Model D of Fig. 1b. In the case of indirect communication, the SCP is used by the NF service consumer. The SCP routes messages between the NF service consumer and the NF service producer, and can perform discovery and associated selection of NF service producers on behalf of the NF service consumer.

[0096] Model A - Direct communication without NRF interaction: Neither NRF nor SCP is used. Consumers are configured with "NF profiles" of producers and communicate directly with the producers they select.

[0097] Model B - Direct Communication with NRF Interaction: The consumer performs discovery by querying the NRF. Based on the results of the discovery, the consumer makes a selection. The consumer sends a request to the selected producer.

[0098] Model C - Indirect communication without delegated discovery: The consumer performs discovery by querying the NRF. Based on the discovery results, the consumer performs the selection of an NF set or a specific NF instance of an NF set. The consumer sends a request to the SCP containing the address of the selected service producer pointing to the NF service instance or a set of NF service instances. In the latter case, the SCP selects the NF service instance. If possible, the SCP interacts with the NRF to obtain the selection parameters such as location, capacity, etc. The SCP routes the request to the selected NF service producer instance.

[0099] Model D - Indirect communication with delegated discovery: The consumer does not perform discovery or selection. The consumer adds to the service request any necessary discovery and selection parameters needed to find a suitable producer. The SCP routes the request to any producer instance using the request address and the discovery and selection parameters in the request message. The SCP can perform discovery on the NRF and get the discovery results.

[0100] As described in 3GPP TS 23.501 V17.0.0, clause 6.2.19, an SCP may include one or more of the following functions. Some or all of the SCP functions may be supported in a single instance of an SCP:

[0101] -Indirect communication.

[0102] - Delegated discovery.

[0103] - Forwarding and routing the message to the destination NF / NF service.

[0104] - Forwarding the message and routing it to the next-hop SCP.

[0105] -Communication security (e.g., permission for NF service consumers to access NF service producer APIs), load balancing, monitoring, overload control, etc.

[0106] - Optionally interacts with the UDR (Unified Data Repository) to resolve UDM (Unified Data Management) Group ID (identifier) / UDR Group ID / AUSF Group ID / PCF Group ID / CHF (Charging Function) Group ID / HSS (Home Subscriber Server) Group ID based on the UE identifier (e.g. SUPI (Subscriber Permanent Identifier) ​​or IMPI (IP Multimedia Private Identifier) / IMPU (IP Multimedia Public Identifier)).

[0107] SCPs may be deployed in a distributed, redundant, and scalable manner. SCPs may be deployed at the PLMN (Public Land Mobile Network) level, at the shared slice level, and at the slice-specific level.

[0108] To allow an SCP to route messages through several SCPs (i.e., next SCP hop discovery), an SCP can register its profile with the NRF. Alternatively, local configuration may be used.

[0109] 2 shows a flowchart of a method according to an embodiment of the present disclosure, which may be implemented in / as a first network entity or executed by an apparatus communicatively coupled to the first network entity. Thus, the apparatus may provide means for accomplishing various portions of the method 200, as well as means for accomplishing other processes in conjunction with other components.

[0110] At block 202, a first network entity may send a first request to a second network entity, the first network entity targeting a resource context or a session context. The first network entity may be any suitable network function, such as a network function consumer or a service communication proxy. The second network entity may be any suitable network function, such as a network function producer.

[0111] According to one embodiment, the second network entity is a network function producer and the first network entity is a network function consumer.

[0112] According to one embodiment, the second network entity is a network function producer and the first network entity is a service communication proxy.

[0113] According to one embodiment, the second network entity is a HyperText Transfer Protocol server, the first network entity is a HyperText Transfer Protocol client, and the communication between the second network entity and the first network entity is direct communication without using a service communication proxy.

[0114] According to one embodiment, the second network entity or the alternative second network entity is a HyperText Transfer Protocol server and the first network entity is a HyperText Transfer Protocol client, and communication between the second network entity or the alternative second network entity and the first network entity is direct communication without using a service communication proxy.

[0115] According to one embodiment, the second network entity or the alternative second network entity is a HyperText Transfer Protocol server and the first network entity is a service communication proxy.

[0116] According to one embodiment, the second network entity is a HyperText Transfer Protocol server and the first network entity is a service communication proxy.

[0117] According to one embodiment, two or more second network entities are grouped into a network function set. The two or more second network entities are replaceable and share the same resource context or session context. For example, as described in clause 5.21.3 of 3GPP TS 23.501 V17.0.0, homogeneous control plane NFs can be grouped into an NF set, e.g., several SMF instances are grouped into an SMF set. NFs in an NF set are replaceable since they share the same context data and can be deployed in different locations, e.g., different data centers. An NF producer instance is an NF instance that hosts an NF service producer. If an NF producer instance is not available, another NF producer instance in the same NF set is selected. In the case of a direct communication mode, an NF service consumer can subscribe to status change notifications of NF instances from the NRF. If the NF service consumer detects, either by being notified by the NRF or by itself, that an NF producer instance is no longer available (e.g., a request is not responded to), another available NF producer instance in the same NF set is selected by the NF service consumer. In the case of an indirect communication mode, the SCP or NF service consumer can subscribe to NF instance status change notifications from the NRF and select another NF producer instance in the same NF set if the original NF producer instance serving the UE is no longer available.

[0118] The first request may be any suitable request. For example, the first request may be any suitable request that can be sent from an NF consumer to an NF producer or from an SCP to an NF producer, as described in 3GPP TS 23.502 V17.0.0, the disclosure of which is incorporated herein by reference in its entirety. According to one embodiment, the first request may be an HTTP request.

[0119] According to one embodiment, the first request may include the application program interface route of the second network entity. The first network entity may obtain the application program interface route of the second network entity in various ways. For example, a NF / NF service discovery procedure defined in 3GPP TS 23.502 V17.0.0, clauses 4.17.4 and 4.17.5 may be performed by the first network entity. If the discovery is successful, the first network entity obtains NF profiles that match the search criteria provided in the Nnrf_NFDiscovery_Request message. If Delegated Service Discovery defined in 3GPP® TS 23.502 V17.0.0, clauses 4.17.9 and 4.17.10 is used, the NF / NF service discovery procedure defined in 3GPP® TS 23.502 V17.0.0, clauses 4.17.4 and 4.17.5 may be performed by the SCP. On successful discovery, the SCP retrieves NF profiles matching the search criteria provided in the Nnrf_NFDiscovery_Request message, selects NFs, and sends information of the selected NFs to the first network entity.

[0120] At block 204, the first network entity may receive a first rejection response from the second network entity or an alternative second network entity.

[0121] According to one embodiment, the first rejection response is a response indicating that the first request was received from the second network entity. and any other alternative second network entity Using either Should it be retried? No and / or a second parameter indicating whether to use an alternative second network entity for subsequent requests targeting the same resource context or session context. A first rejection response including the information having the second parameter is received from the alternative second network entity.

[0122] According to an embodiment, the first rejection response includes information indicating whether to avoid retrying the first request by reselecting the second network entity and / or information indicating whether to use the second network entity for subsequent requests targeting the same resource context or session context. The rejection may be due to various reasons, e.g., the first request fails an HTTP stack schema check or fails an OpenAPI inspection, the second network entity is busy (overloaded) when it receives the request message and therefore cannot process it, the first request fails due to application logic, e.g., some resource is not allowed to be modified at that time, etc.

[0123] According to one embodiment, the information may be carried by a new HyperText Transfer Protocol header, or 3gpp-Sbi-Target-apiRoot, or 3gpp-Sbi-Binding, which may be the same as 3gpp-Sbi-Target-apiRoot and 3gpp-Sbi-Binding described in 3GPP TS 29.500 V17.2.0, the disclosure of which is incorporated herein by reference in its entirety.

[0124] According to one embodiment, the information may take any suitable form, such as an indicator, bit, flag, etc.

[0125] According to one embodiment, the information includes whether the first request is rejected due to an application logic error or a state conflict, or whether the resource context or session context is Alternative and whether the resource context or the session context has been taken over by the second network entity. After receiving the first rejection response, the first network entity may know the rejection reason and whether the resource context or the session context has been taken over by the second network entity. The first network entity may perform any appropriate action based on such information. For example, the first network entity may modify the first request to avoid an application logic error or a state conflict and resend the modified first request to the second network entity. The first network entity may later resend the first request to the second network entity. Alternatively, the first network entity may inform any other appropriate network function of the error information.

[0126] According to an embodiment, the information may include implicit information or explicit information. The explicit information may be dedicated indication information. The implicit information may be any suitable information that may be used for such indication and any other suitable use. For example, the implicit information may include an application program interface root of the second network entity. The application program interface root (apiRoot) of the second network entity may be used to indicate the apiRoot of the target uniform resource identifier (URI). According to an embodiment, the application program interface root of the second network entity may be 3gpp-Sbi-Target-apiRoot as described in section 5.2.3.2.4 of 3GPP TS 29.500 V17.2.0. An example of 3gpp-Sbi-Target-apiRoot is 3gpp-Sbi-Target-apiRoot: https: / / example.com / a / b / c.

[0127] In block 206, optionally, the first network entity may send a first rejection response including information having a first parameter, and the first parameter indicating that the first request should be retried with the second network entity or to any other alternative second network entity. do not have If so, a retry of the first request may be avoided.

[0128] According to one embodiment, the first network entity may avoid retrying the first request by reselecting the second network entity if the first rejection response includes information indicating to avoid retrying the first request by reselecting the second network entity and / or information indicating to use the second network entity for subsequent requests targeting the same resource context or session context. The first network entity may know that it should avoid further reselection of an alternative second network entity since it can achieve the same result. According to this embodiment, it may reduce extra signaling for further reselection.

[0129] In block 208, optionally, the first network entity may use the alternative second network entity for subsequent requests targeting the same resource context or session context if the first rejection response includes information having the second parameter, and the second parameter indicates to use the alternative second network entity for subsequent requests targeting the same resource context or session context.

[0130] According to one embodiment, the first network entity may use the second network entity for subsequent requests targeting the same resource context or session context if the first rejection response includes information indicating to avoid retrying the first request by reselecting the second network entity and / or includes information indicating to use the second network entity for subsequent requests targeting the same resource context or session context.

[0131] FIG. 3 shows a flowchart of a method according to another embodiment of the present disclosure, which may be implemented in / as a first network entity or executed by an apparatus communicatively coupled to the first network entity. Thus, the apparatus may provide means for accomplishing various parts of the method 300 and means for accomplishing other processes in conjunction with other components. Note that some parts described in the above embodiment will not be described in detail for the sake of brevity. According to this embodiment, the second network entity may be a network function producer or a hypertext transfer protocol server, and the first network entity may be a service communication proxy.

[0132] At block 302, the first network entity may receive a second request from a HyperText Transfer Protocol client (e.g., an NF service consumer). In response to receiving the second request from the HyperText Transfer Protocol client, the first network entity may send the first request to the second network entity, the first request targeting the resource context or the session context. For example, if the HyperText Transfer Protocol client wishes to communicate with the second network entity (e.g., an NF service producer or a HyperText Transfer Protocol server), the HyperText Transfer Protocol client may send the second request to the first network entity, such as an SCP.

[0133] According to one embodiment, the second request may include discovery and selection parameters necessary to discover and select the second network entity. The discovery and selection parameters are included in the second request by the HyperText Transfer Protocol client so that the first network entity, such as the SCP, does not need to parse the request body. The first network entity, such as the SCP, may perform discovery at the time of the second request by interacting with the NRF using the Nnrf_NFDiscovery service, or may use information collected during a previous interaction with the NRF (by the Nnrf_NFDiscovery service or the Nnrf_NFManagement_NFStatusNotify service operation). The first network entity, such as the SCP, together with the NRF, authorizes the second request. The first network entity, such as the SCP, selects the second network entity.

[0134] According to another embodiment, the second request may include an application program interface route of the second network entity. For example, in a subsequent operation on the created resource context or session context, the NF service consumer addresses the existing context data (such as a resource context or a session context) via the resource address returned by the second NF. In this case, the first NF may know that the second request may be sent / forwarded to the resource address of the second NF.

[0135] At block 304, in response to receiving the second request from the network function consumer, the first network entity may send a first request to the second network entity targeting the resource context or the session context.

[0136] At block 306, the first network entity may receive a first rejection response from the second network entity or the alternative second network entity. According to an embodiment, The first rejection response is: No. 1st request using either the second network entity or any other alternative second network entity. retry Should it be or shouldn't it be? Show The first parameter is information and / or for subsequent requests that target the same resource or session context. Alternative Indicates whether to use a second network entity The second parameter is Information and has. A first rejection response including information having the second parameter is received from the alternative second network entity.

[0137] At block 308, in response to receiving the first rejection response from the second network entity, the first network entity may forward the first rejection response to the HyperText Transfer Protocol client as a response to the second request.

[0138] FIG. 4 shows a flowchart of a method according to another embodiment of the present disclosure, which may be implemented in / as a first network entity or executed by an apparatus communicatively coupled to the first network entity. Thus, the apparatus may provide means for accomplishing various parts of the method 400, as well as means for accomplishing other processes in conjunction with other components. Note that some parts described in the above embodiment will not be described in detail for brevity. According to this embodiment, the second network entity may be a network function producer, and the first network entity may be a service communication proxy.

[0139] At block 402, the first network entity may receive a second request from a HyperText Transfer Protocol client targeting a resource context or a session context.

[0140] According to one embodiment, the second request may include an application program interface route of another second network entity. For example, in a subsequent operation on the created resource, the Hypertext Transfer Protocol client (e.g., NF service consumer) addresses the existing context data (e.g., resource context / session context) via the resource address returned by the other second network entity. In this case, the first NF may know that the second request can be sent / forwarded to the resource address of the other second NF.

[0141] In block 404, the first NF may determine that the other second network entity is not reachable and / or cannot handle the second request. The first NF may determine that the other second network entity is not reachable or cannot handle the second request in various ways. For example, the first network entity may send / forward the second request to the other second network entity and receive an error response from the other second network entity or may receive an error response from the other second network entity. The second request may be rejected for various reasons, such as a temporary failure cause indicating that the second request is not processed, such as insufficient memory. The second request may time out (no response received). The first NF has already determined that the other second network entity is not reachable.

[0142] In block 406, the first network entity may reselect a second network entity based on a determination that the other second network entity is not reachable and / or the other network entity cannot process the second request. The second network entity and the other second network entity may belong to a network function set, be interchangeable, and share the same context data (e.g., resource context or session context). For example, details of the reselection of the target NF service producer instance are described in clause 6.3.1.0 of TS 23.501 V17.0.0.

[0143] At block 408, in response to receiving the second request from the network function consumer and reselecting the second network entity, the first network entity may send a first request targeted to the resource context or the session context to the reselected second network entity.

[0144] At block 410, the first network entity may receive a first rejection response from the reselected second network entity, the first rejection response having information indicating whether to avoid retrying the first request due to reselection of the second network entity and / or information indicating whether to use the second network entity for subsequent requests targeting the same resource context or session context.

[0145] At block 412, if the first rejection response includes information having the second parameter and the second parameter indicates to use the second network entity or an alternative second network entity for subsequent requests targeting the same resource context or session context, the first network entity may add an application program interface route of the second network entity or the alternative second network entity to the first rejection response.

[0146] According to one embodiment, if the first rejection response includes information indicating to avoid retrying the first request by reselecting the second network entity and / or to use the second network entity for subsequent requests targeting the same resource context or session context, the first network entity may add an application program interface route of the second network entity to the first rejection response. If the first rejection response includes an application program interface route of the second network entity, block 412 may be skipped.

[0147] In block 414, the first rejection response includes information indicating a retry of the first request by reselecting the second network entity. ("Reselection" here means selecting a different second network entity) , and / or information indicating to disable the second network entity for subsequent requests targeting the same resource context or session context, the first network entity may add an application program interface route of another second network entity to the first rejection response.

[0148] In response to receiving the first rejection response from the second network entity, the first network entity may forward the first rejection response to the HyperText Transfer Protocol client as a response to the second request, at block 416. The first rejection response includes a resource address, such as an application program interface route of the second network entity or an application program interface route of another second network entity, so that the network function consumer can use it for a subsequent request related to the associated resource.

[0149] According to one embodiment, two or more of the second network entities and / or alternative second network entities are grouped into a network function set, a network function service set, or a network function service instance set, and two or more of the second network entities and / or alternative second network entities are interchangeable and share the same resource context or session context.

[0150] 5 shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in / as or communicatively coupled to the second network entity or another second network entity. Thus, the apparatus may provide means for accomplishing various parts of the method 500, as well as means for accomplishing other processes in conjunction with other components. Note that some parts described in the above embodiment will not be described in detail for the sake of brevity.

[0151] The second network entity or an alternative second network entity may receive a first request targeting a resource context or a session context from the first network entity at block 502. For example, the first network entity may send a first request targeting a resource context or a session context to the second network entity at block 204 of FIG. 2, and the second network entity may then receive the first request targeting the resource context or the session context from the first network entity.

[0152] At block 504, the second network entity or the alternative second network entity may send a first rejection response to the first network entity.

[0153] According to one embodiment, the first rejection response is a response indicating that the first request was received from the second network entity. and any other alternative second network entity Using either Should a retry be performed? No and / or a second parameter indicating whether to use an alternative second network entity for subsequent requests targeting the same resource context or session context. A first rejection response including the information having the second parameter is received from the alternative second network entity.

[0154] According to an embodiment, the first rejection response includes information indicating whether to avoid retrying the first request by reselecting the second network entity and / or information indicating whether to use the second network entity for subsequent requests targeting the same resource context or session context. The first request may be rejected by the second network entity for various reasons. For example, the second network entity is unable to process the current first request due to an application logic error or a state conflict. Furthermore, the second network entity may have inherited context data (such as a resource context or a session context) for the first request. The second network entity expects to process subsequent requests from the first network entity. The second network entity may determine that the first network entity should not reselect another second network entity.

[0155] According to one embodiment, the first rejection response includes an application program interface route of the second network entity or an alternative second network entity.

[0156] 6 shows a flowchart of a method according to another embodiment of the present disclosure, which may be implemented in / as a third network entity or executed by an apparatus communicatively coupled to the third network entity. Thus, the apparatus may provide means for accomplishing various parts of the method 600, as well as means for accomplishing other processes in conjunction with other components. Note that some parts described in the above embodiment will not be described in detail for the sake of brevity.

[0157] In block 602, the third network entity may send a request to the service communication proxy targeting the resource context or the session context. For example, the request may be the second request as described above.

[0158] According to one embodiment, the third network entity is a HyperText Transfer Protocol client.

[0159] According to one embodiment, the request includes an application program interface route of the second network entity.

[0160] According to one embodiment, the request includes an application program interface route of another second network entity.

[0161] At block 604, the third network entity may receive a rejection response from the service communication proxy.

[0162] According to one embodiment, the reject response includes information indicating whether to avoid retrying the request by reselecting the second network entity and / or whether to use the second network entity for subsequent requests. For example, the reject response may be the first reject response described above.

[0163] According to one embodiment, the reject response is sent to the second network entity and any other alternative second network entity Using either Should it be retried? Noand / or a second parameter indicating whether to use an alternative second network entity for a subsequent request targeting the same resource context or session context. A rejection response including the information having the second parameter is received from the alternative second network entity.

[0164] According to one embodiment, the reject response includes an application program interface route of the second network entity or an alternative second network entity.

[0165] According to one embodiment, the information includes whether the request is rejected due to an application logic error or a state conflict, or whether the resource context or session context is Alternative and whether it has been taken over by a second network entity.

[0166] According to one embodiment, the information includes implicit or explicit information.

[0167] According to one embodiment, the implicit information includes an application program interface route of the second network entity.

[0168] According to one embodiment, the reject response includes an application program interface route of the second network entity.

[0169] According to one embodiment, the information is carried by a new HyperText Transfer Protocol header, or 3gpp-Sbi-Target-apiRoot, or 3gpp-Sbi-Binding.

[0170] In block 606, the third network entity may use the alternative second network entity for subsequent requests targeting the same resource context or session context if the reject response has information with the second parameter and the second parameter indicates to use the alternative second network entity for subsequent requests targeting the same resource context or session context.

[0171] According to one embodiment, the third network entity may use the second network entity for a subsequent request if the reject response includes information indicating to avoid retrying the request by reselecting the second network entity and / or information indicating to use the second network entity for a subsequent request targeting the same resource context or session context. For example, the third network entity may update the resource context or session context URI with the one included in the reject response for the subsequent request for the same resource context or session context.

[0172] 7 shows a flowchart of a method according to another embodiment of the present disclosure. According to this embodiment, the second NF1 and the second NF2 are grouped into a network function set. The second NF1 and the second NF2 are interchangeable and share the same context data. This embodiment relates to direct communication without SCP. It should be noted that although only two NFs are illustrated as being included in the network function set, the network function set may include any suitable number of NFs.

[0173] In step 701, a first NF may send an HTTP request to a second NF1. The HTTP request addresses an existing resource context or session context in the second NF1. The request URI includes an apiRoot associated with the second NF1.

[0174] In step 702, the HTTP request is rejected with a temporary failure cause indicating, for example, that the HTTP request cannot be processed by the second NF1 due to insufficient memory, or that the HTTP request times out (no response is received from the second NF), or that the first NF has already determined that the second NF1 is unreachable, etc.

[0175] In step 703, the first NF may decide to perform reselection (e.g., a second NF2 in the same NF set) according to the binding information of the context or the NF profile of the second NF1. For example, details of the reselection of the target NF service producer instance are described in section 6.3.1.0 of TS 23.501 V17.0.0.

[0176] In step 704, the first NF may send / redirect the HTTP request to the second NF2 by replacing the apiRoot in the request URI with the apiRoot of the second NF2.

[0177] In step 705, the second NF2 may send a rejection response to the first NF. For example, the HTTP request is rejected even after the second NF2 applies the application logic. For example, the HTTP request is not accepted. However, the second NF2 has decided to take over the resource context or session context. If so, the second NF2 shall include in a new 3GPP customer header, which may be called "3gpp-Sbi-Targrt-Apiroot" or "3gpp-Sbi-Response-Info", an indication that the first NF has rejected the HTTP request due to an application logic error and that the resource context or session context has been taken over by the second NF2, i.e., the first NF shall not continue with another reselection (as it would have the same result) and the first NF shall use the apiRoot (included in the HTTP request in step 704), which is the apiRoot of the second NF2, to address the resource context or session context in subsequent requests for the context.

[0178] FIG. 8 shows a flowchart of a method according to another embodiment of the present disclosure. According to this embodiment, the second NF3 and the second NF4 are grouped into a network function set. The second NF3 and the second NF4 are interchangeable and share the same context data. This embodiment relates to indirect communication with the SCP. It should be noted that although only two NFs are shown to be included in the network function set, the network function set may include any suitable number of NFs.

[0179] In step 801, a first NF may send an HTTP request to an SCP. The HTTP request addresses an existing resource context or session context in a second NF3. The request URI includes an apiRoot associated with the second NF3.

[0180] In step 802, the SCP forwards the HTTP request to a second NF3.

[0181] In step 803, the HTTP request is rejected with a temporary failure cause indicating, for example, that the HTTP request cannot be processed by the second NF3 due to insufficient memory, or that the HTTP request has timed out (no response was received from the second NF), or that the SCP has already determined that the second NF3 was unreachable.

[0182] In step 804, the SCP may decide to perform reselection (e.g., a second NF4 in the same NF set) according to the binding information of the context or the NF profile of the second NF3. For example, details of the reselection of the target NF service producer instance are described in TS 23.501 V17.0.0, section 6.3.1.0.

[0183] In step 805, the SCP may send / redirect the HTTP request to the second NF4 by replacing the apiRoot in the request URI with the apiRoot of the second NF4.

[0184] In step 806, the second NF4 may send a rejection response to the SCP. For example, the HTTP request is rejected even after the second NF4 applies the application logic. For example, the HTTP request is not accepted. However, the second NF4 has determined that it will take over the resource context or session context. If so, the second NF4 shall include in a new 3GPP customer header, which may be called "3gpp-Sbi-Targrt-Apiroot" or "3gpp-Sbi-Response-Info", an indication to the SCP that the HTTP request was rejected due to an application logic error and the resource context or session context has been taken over by the second NF4, i.e., the SCP shall not continue with another reselection (as it would have the same outcome) and the SCP shall use the apiRoot (included in the HTTP request in step 805), which is the apiRoot of the second NF4, to address the resource context or session context in subsequent signaling for the context.

[0185] In step 807, the SCP may forward / send the reject response to the first NF. If the reject response does not contain such information, the SCP may include the 3gpp-Sbi-Targrt-Apiroot, or a new 3GPP Customer Header. The first NF may update the resource context or session context URI with the one included in the 3gpp-Sbi-Targrt-Apiroot, or a new 3GPP Customer Header for subsequent signaling for the context.

[0186] By applying the proposed solution according to the embodiments of the present disclosure, many advantages may be achieved. For example, some embodiments of the present disclosure allow the second NF to indicate how to send a subsequent request to the first NF (which sends the request to the second NF) when the current request is rejected by the second NF. For example, the second NF may indicate to the first NF that the context data (such as resource context or session context) has been taken over by the second NF, or that the second network entity will be used to process the subsequent request from the first NF. The first NF updates the resource URI or session URI by replacing the apiRoot with the apiRoot of the second NF, even if the current request is rejected by the second NF. Some embodiments of the present disclosure provide a mechanism to instruct the NF performing NF reselection not to perform NF reselection, which may reduce extra signaling for further NF reselection. The embodiments herein are not limited to the features and advantages described above. Those skilled in the art will recognize additional features and advantages upon reading the following detailed description.

[0187] 9 is a block diagram illustrating an apparatus suitable for implementing some embodiments of the present disclosure. For example, any one of the first network entity, the second network entity, or the third network entity described above may be implemented as or via the apparatus 900.

[0188] The apparatus 900 has at least one processor 921, such as a digital processor (DP), and at least one memory (MEM) 922 coupled to the processor 921. The apparatus 900 may further comprise a transmitter TX and a receiver RX 923 coupled to the processor 921. The MEM 922 stores a program (PROG) 924. The PROG 924 may include instructions that, when executed on the associated processor 921, enable the apparatus 900 to operate according to embodiments of the present disclosure. The combination of the at least one processor 921 and the at least one MEM 922 may form a processing means 925 adapted to implement various embodiments of the present disclosure.

[0189] Various embodiments of the present disclosure may be implemented by computer programs executable by one or more of the processor 921, software, firmware, hardware, or combinations thereof.

[0190] MEM 922 may be implemented using any suitable data storage technology, such as, for example, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed and removable memory.

[0191] The processor 921 may be of any type suitable for the local technology environment and may include, by way of non-limiting examples, 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.

[0192] According to an embodiment in which the apparatus is implemented as or in a first network entity, the memory 922 includes instructions executable by the processor 921, whereby the first network entity operates according to any of the methods associated with the first network entity, as described above.

[0193] According to an embodiment in which the apparatus is implemented as or in a second network entity, the memory 922 includes instructions executable by the processor 921, whereby the second network entity operates according to any of the methods associated with the second network entity, as described above.

[0194] According to one embodiment in which the apparatus is implemented as or in a third network entity, the memory 922 includes instructions executable by the processor 921, whereby the third network entity operates according to any of the methods associated with the third network entity, as described above.

[0195] 10 is a block diagram illustrating a first network entity according to one embodiment of the present disclosure. As shown, the first network entity 1000 has a sending module 1001 configured to send a first request targeting a resource context or a session context to a second network entity. The first network entity 1000 further has a first receiving module 1002 configured to receive a first rejection response from the second network entity or an alternative second network entity. According to one embodiment, the first rejection response indicates that the first request is not a valid response from the second network entity. and any other alternative second network entity Using either Should it be retried? No and / or a second parameter indicating whether to use an alternative second network entity for subsequent requests targeting the same resource context or session context. A first rejection response including the information having the second parameter is received from the alternative second network entity.

[0196] According to one embodiment, the first rejection response includes information indicating whether to avoid retrying the first request by reselecting the second network entity and / or information indicating whether to use the second network entity for subsequent requests targeting the same resource context or session context.

[0197] According to one embodiment, the first network entity 1000 further comprises an avoidance module 1003 configured to avoid retrying the first request if the first rejection response includes information having a first parameter, the first parameter indicating that the first request should be retried at the second network entity or any other alternative second network entity. do not have This indicates that.

[0198] According to one embodiment, the avoidance module 1003 is configured to avoid retrying the first request by reselecting the second network entity, and the first rejection response includes information indicating to avoid retrying the first request by reselecting the second network entity and / or information indicating to use the second network entity for subsequent requests targeting the same resource context or session context.

[0199] According to an embodiment, the first network entity 1000 further includes a usage module 1004 configured to use the alternative second network entity for subsequent requests targeting the same resource context or session context if the first rejection response includes information having a second parameter, and the second parameter indicates to use the alternative second network entity for subsequent requests targeting the same resource context or session context.

[0200] According to one embodiment, the usage module 1004 is configured to use the second network entity for subsequent requests targeting the same resource context or session context if the first rejection response includes information indicating to avoid retrying the first request by reselecting the second network entity and / or includes information indicating to use the second network entity for subsequent requests targeting the same resource context or session context.

[0201] According to one embodiment, the first network entity 1000 further comprises a second receiving module 1005 configured to receive a second request from the HyperText Transfer Protocol client. The sending module 1001 is configured to send a first request targeting the resource context or the session context to the second network entity in response to receiving the second request from the HyperText Transfer Protocol client.

[0202] According to one embodiment, the first network entity 1000 further comprises a forwarding module 1006 configured to, in response to receiving the first rejection response from the second network entity, forward the first rejection response to the HyperText Transfer Protocol client as a response to the second request.

[0203] The first network entity 1000 further includes a determination module 1007 configured to determine that the other second network entity is not reachable and / or is unable to process the second request.

[0204] The first network entity 1000 further includes a reselection module 1008 configured to reselect a second network entity based on a determination that the other second network entity is not reachable and / or the other network entity is unable to process the second request.

[0205] The first network entity 1000 further includes an additional module 1009, which is configured to receive the first rejection response including information having a second parameter, and the second parameter indicates that the first rejection response includes ... of The method is configured to add an application program interface route of the second network entity or an alternative second network entity if the first rejection response indicates use for targeting subsequent requests.

[0206] According to one embodiment, the adding module 1009 is configured to add an application program interface route of the second network entity to the first rejection response, the first rejection response including information indicating to avoid retrying the first request by reselecting the second network entity and / or information indicating to use the second network entity for subsequent requests targeting the same resource context or session context.

[0207] According to one embodiment, the adding module 1009 is configured to add an application program interface route of another second network entity to the first rejection response if the first rejection response includes information indicating a retry of the first request by reselecting the second network entity and / or information indicating disabling the second network entity for subsequent requests targeting the same resource context or session context.

[0208] 11 is a block diagram illustrating a second network entity or an alternative second network entity according to an embodiment of the present disclosure. As shown, the second network entity or the alternative second network entity 1100 has a receiving module 1101 configured to receive a first request targeting a resource context or a session context from a first network entity. The second network entity or the alternative second network entity 1100 further has a transmitting module 1102 configured to transmit a first rejection response to the first network entity. According to an embodiment, the first rejection response indicates that the first request is not a response to the second network entity. and any other alternative second network entity Using either Should it be retried? No and / or a second parameter indicating whether to use an alternative second network entity for subsequent requests targeting the same resource context or session context. A first rejection response including the information having the second parameter is received from the alternative second network entity.

[0209] According to one embodiment, the first rejection response includes information indicating whether to avoid retrying the first request by reselecting the second network entity and / or information indicating whether to use the second network entity for subsequent requests targeting the same resource context or session context.

[0210] 12 is a block diagram illustrating a third network entity according to an embodiment of the present disclosure. As shown, the third network entity 1200 includes a sending module 1201 configured to send a request targeting a resource context or a session context to a service communication proxy. The third network entity 1200 further includes a receiving module 1202 configured to receive a rejection response from the service communication proxy.

[0211] According to an embodiment, the reject response includes information having a first parameter indicating whether the request should be retried with the second network entity or for any other alternative second network entity and / or a second parameter indicating whether to use the alternative second network entity for subsequent requests targeting the same resource context or session context. The reject response including the information having the second parameter is received from the alternative second network entity. According to an embodiment, the reject response includes information indicating whether to avoid retrying the request by reselecting the second network entity and / or to use the second network entity for subsequent requests. The third network entity 1200 further includes a using module 1203 configured to use the alternative second network entity for subsequent requests targeting the same resource context or session context if the reject response includes information having the second parameter and the second parameter indicates to use the alternative second network entity for subsequent requests targeting the same resource context or session context.

[0212] The term unit or module may have its conventional meaning in the field of electronic equipment, electrical devices and / or electronic devices and may include, for example, electric and / or electronic circuits, devices, modules, processors, memories, logic solid state and / or discrete devices, computer programs or instructions for performing a respective task, procedure, computation, output and / or display function, etc., as described herein.

[0213] In the functional unit, the first network entity, the second network entity, or the third network entity may not require a fixed processor or memory, and any computing resource and storage resource may be configured in the first network entity, the second network entity, or the third network entity in the communication system. The introduction of virtualization technology and network computing technology can improve the utilization efficiency of network resources and the flexibility of the network.

[0214] According to one aspect of the present disclosure, there is provided a computer program product comprising instructions tangibly stored on a computer-readable storage medium and which, when executed on at least one processor, cause the at least one processor to perform any of the methods set forth above.

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

[0216] Furthermore, the present disclosure may provide a carrier containing the above-mentioned computer program, the carrier being one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium. The computer-readable storage medium may be, for example, an optical compact disc, or an electronic memory device such as a RAM (random access memory), a ROM (read only memory), a flash memory, a magnetic tape, a CD-ROM, a DVD, a Blu-ray disc, etc.

[0217] The techniques described herein may be implemented by various means, such that an apparatus implementing one or more functions of a corresponding apparatus described with the embodiments has not only conventional means, but also means for implementing one or more functions of a corresponding apparatus described with the embodiments, and may comprise separate means for each separate function, or means that may be configured to perform two or more functions. For example, these techniques may be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or a combination thereof. The firmware or software may be implemented via modules (e.g., procedures, functions, etc.) that perform the functions described herein.

[0218] Exemplary embodiments of the present specification have been described above with reference to block diagrams and flowchart illustrations of methods and apparatus. It will be understood that each block of the block diagrams and flowchart illustrations, and combinations of each block of the block diagrams and flowchart illustrations, can be implemented by various means, 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 apparatus to generate a machine such that the instructions, which execute on the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more of the flowchart blocks.

[0219] Furthermore, although operations are depicted in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown, or in sequential order, or that all of the depicted operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, while some specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the subject matter described herein, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may be implemented in multiple embodiments separately or in any suitable subcombination.

[0220] Although the present specification contains many specific implementation details, these should not be construed as a limitation on the scope of any implementation or what may be claimed, but rather as a description of features that may be specific to a particular embodiment of a particular implementation. Certain features described in the context of separate 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 in multiple embodiments separately or in any suitable subcombination. Furthermore, features may be described above as acting in a particular combination, and even as initially claimed, one or more features from a claimed combination may, in some cases, be separated from the combination, and the claimed combination may be directed to a subcombination or a variation of the subcombination.

[0221] It will be obvious to those skilled in the art that as technology advances, the concept of the present disclosure can be implemented in various ways. The above embodiments are given to illustrate, not to limit, the present disclosure, and it should be understood that modifications and variations can be utilized without departing from the spirit and scope of the present disclosure, as those skilled in the art will easily understand. Such modifications and changes are considered to be within the scope of the present disclosure and the appended claims. The scope of protection of the present disclosure is defined by the appended claims.

Claims

1. A method (200) performed in a first network entity, comprising: Sending (202) a first request to a second network entity, the first request targeting a resource context or a session context; receiving (204) a first rejection response from the second network entity or an alternative second network entity; The first rejection response comprises: a first parameter indicating whether the first request should be retried using either the second network entity or any other alternative second network entity; and / or a second parameter indicating whether to use the alternative second network entity for subsequent requests targeting the same resource context or session context, wherein the first rejection response is received from the alternative second network entity, the first rejection response including information having the second parameter; The method further comprises: using (208) the alternative second network entity for subsequent requests targeting the same resource context or session context if the first rejection response includes information having the second parameter, and the second parameter indicates to use the alternative second network entity for subsequent requests targeting the same resource context or session context.

2. 2. The method of claim 1, wherein two or more of the second network entities and / or the alternative second network entities are grouped into a network function set, a network function service set, or a network function service instance set, and wherein the two or more of the second network entities and / or the alternative second network entities are interchangeable and share the same resource context or session context.

3. 2. The method of claim 1, wherein the information further comprises: whether the first request is rejected due to an application logic error or a state conflict; or and whether the resource context or session context has been inherited by the alternative second network entity.

4. 10. The method of claim 1 further comprising: avoiding (206) a retry of the first request if the first rejection response includes information having the first parameter, and the first parameter indicates that the first request should not be retried with the second network entity or to any other alternate second network entity.

5. 2. The method of claim 1, wherein the second network entity or an alternative second network entity is a HyperText Transfer Protocol server and the first network entity is a service communication proxy, the method further comprising: receiving (302) a second request from a HyperText Transfer Protocol client targeting the resource context or session context, where sending the first request targeting the resource context or session context to the second network entity is performed in response to receiving the second request from the HyperText Transfer Protocol client; and in response to receiving the first rejection response from the second network entity, forwarding (308) the first rejection response to the HyperText Transfer Protocol client as a response to the second request.

6. 6. The method of claim 5, wherein the second request includes an application program interface route of the second network entity, or The second request includes an application program interface route of another second network entity, the method further comprising: determining (404) that the other second network entity is not reachable and / or is unable to handle the second request; reselecting (406) the second network entity based on the determination that the other second network entity is not reachable and / or cannot handle the second request; and and if the first rejection response includes information having the second parameter, and the second parameter indicates to use the second network entity or an alternative second network entity for a subsequent request targeting the same resource context or session context, adding (412) an application program interface route of the second network entity or the alternative second network entity to the first rejection response. method.

7. A method (500) performed by a second network entity or an alternative second network entity, comprising: Receiving a first request from a first network entity targeting a resource context or a session context (502); sending 504 a first rejection response to the first network entity; The first rejection response comprises: a first parameter indicating whether the first request should be retried using either the second network entity or any other alternative second network entity; and / or a second parameter indicating whether to use the alternative second network entity for subsequent requests targeting the same resource context or session context, wherein the first rejection response is received from the alternative second network entity, the first rejection response including information having the second parameter; if the first rejection response includes information having the second parameter, and the second parameter indicates to use the alternative second network entity for a subsequent request targeting the same resource context or session context, the alternative second network entity is used for a subsequent request targeting the same resource context or session context. method.

8. 8. The method of claim 7, wherein two or more of the second network entities and / or the alternative second network entities are grouped into a network function set, a network function service set, or a network function service instance set, and wherein the two or more of the second network entities and / or the alternative second network entities are interchangeable and share the same resource or session context.

9. 8. The method of claim 7, wherein the information further comprises: whether the first request is rejected due to an application logic error or a state conflict; or and whether the resource context or session context has been inherited by the alternative second network entity.

10. 8. The method of claim 7, wherein the information comprises implicit information or explicit information; The method, wherein the implicit information includes an application program interface route of the second network entity.

11. 8. The method of claim 7, wherein the first request includes an application program interface route of the second network entity; and / or The method of claim 1, wherein the first rejection response has an application program interface route of the second network entity or the alternative second network entity.

12. A first network entity (900), A processor (921); and a memory (922) coupled to the processor (921), the memory (922) including instructions executable by the processor (921), whereby the first network entity (900) Sending a first request to a second network entity, the first request targeting the resource context or the session context; and operable to receive a first rejection response from the second network entity or an alternative second network entity; The first rejection response comprises: a first parameter indicating whether the first request should be retried using either the second network entity or any other alternative second network entity; and / or a second parameter indicating whether to use the alternative second network entity for subsequent requests targeting the same resource context or session context, wherein the first rejection response is received from the alternative second network entity, the first rejection response including information having the second parameter; The first network entity further comprises: the first network entity is operable to use the alternative second network entity for subsequent requests targeting the same resource context or session context if the first rejection response includes information having a second parameter, and the second parameter indicates to use the alternative second network entity for subsequent requests targeting the same resource context or session context.

13. A first network entity according to claim 12, wherein said first network entity is further operable to perform the method according to any one of claims 2 to 6.

14. A network entity which is a second network entity or an alternative second network entity (900), A processor (921); and a memory (922) coupled to the processor (921), the memory (922) including instructions executable by the processor (921), whereby the second network entity or the alternative second network entity (900) is receiving a first request from a first network entity targeting a resource context or a session context; operative to transmit a first rejection response to the first network entity; The first rejection response comprises: a first parameter indicating whether the first request should be retried using either the second network entity or any other alternative second network entity; and / or a second parameter indicating whether to use the alternative second network entity for subsequent requests targeting the same resource context or session context, wherein the first rejection response is received from the alternative second network entity, the first rejection response including information having the second parameter; if the first rejection response includes information having a second parameter, and the second parameter indicates to use the alternative second network entity for a subsequent request targeting the same resource context or session context, the alternative second network entity is used for a subsequent request targeting the same resource context or session context. Network entity.

15. A network entity according to claim 14, wherein the second network entity or an alternative second network entity is further operative to perform the method according to any one of claims 8 to 11.

16. A computer readable storage medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform the method of any one of claims 1 to 11.

Images