TW201924428A - Transferring multiple resources between Network Functions - Google Patents

Abstract

Systems and methods for transferring multiple resources between Network Functions (NFs) are provided. A method of operation of a source NF includes providing, to a target NF, information describing resources that the source NF would like to transfer. The source NF also receives a response indicating at least partial acceptance of the transfer. The source NF then transfers resources corresponding to the at least partial acceptance of the transfer. In this way, a negotiable way for pushing multiple resources between NFs is provided. This makes use of the HTTP/2 feature server push to perform the transfer. This may allow the target NF to control, and guide what resources, and the number of resources that can be accepted. This also may provide better performance by pre-emptively sending resources to avoid unnecessary signaling and waiting time which may avoid potential Head-Of-Line blocking by sending resources in separate streams.

Description

Transfer multiple resources between network functions

The present invention relates to network functions (NF) in a core network of a wireless communication system and, in particular, to transferring resources between NFs.

Figures 1 and 2 illustrate a non-roaming and roaming fifth generation (5G) system architecture as defined by the Third Generation Partnership Project (3GPP). As illustrated, a 5G core (5GC) network includes several network functions (NF), such as an access and mobility management function (AMF), a session management function (SMF), and an authentication servo. Function (AUSF), a network slice selection function (NSSF), a network exposure function (NEF), a network repository function (NRF), a principle control function (PCF), an application function (AF) And a unified data management (UDM) function. 3GPP has determined that the NF system within the 5GC Control Plane (CP) uses only service-based interfaces for its interaction, as specified in sub-clause 4.2.1 of the 3GPP Technical Specification (TS) 23.501 V1.3.0. There are usually many instances of each type of NF in the 5GC. The 5G system architecture includes the following service-based interfaces: • Namf: A service-based interface presented by AMF. • Nsmf: A service-based interface presented by SMF. • Nnef: A service-based interface presented by NEF. • Npcf: A service-based interface presented by PCF. • Nudm: A service-based interface presented by UDM. • Naf: A service-based interface presented by AF. • Nnrf: A service-based interface presented by NRF. • Nnssf: A service-based interface presented by NSSF. • Nausf: A service-based interface presented by AUSF.

One of the CP NFs within the 5GC can expose its capabilities as a service via its service-based interface (which can be reused by the CP NF). The NF service discovery enables a core network NF to discover NF instances that provide a desired or expected NF service. NF service discovery is implemented via NF discovery functionality.

In subclause 7.1.2 of 3GPP TS 23.501 V1.3.0, 3GPP further specifies an NF service consumer (ie, NF that consumes one of the other NF services) with an NF service producer (ie, produced by NF interaction between NF), one of the services of another NF consumption.

Figure 3 illustrates one request-response interaction between a consumer NF (NF A) and a producer NF (NF B). In this response-request interaction, a CP NF (NF B) receives a request from another CP NF (NF A) to provide a particular NF service to NF A. The NF service can be performing an action, providing information, or both. NF B provides the requested NF service for NF A in response to a request made by NF A. To satisfy this request, NF B can then consume NF services from other NFs. In the request-response mechanism, communication is one-to-one between two NFs (consumer and producer), and one response from producer NF from one of the consumers is expected to be expected at a specific time. Inside the box.

4 and 5 illustrate a subscription-notification mechanism. As illustrated in Figure 4, a CP NF (NF A) subscription is served by one of the other CP NF (NF B) NF services. Multiple CP NFs can subscribe to the same services provided by NF B. NF B notifies NF of the results of the NF service. A subscription request from NF A may include a request for a periodic update or notification triggered by a particular event, such as a change in one of the information subscribed by NF A, a value approaching a particular threshold, and the like. It should be noted that the subscription may be an explicit subscription or an implicit subscription (eg, due to a successful registration procedure). Figure 5 illustrates a subscription-notification mechanism in which one CP NF (NF A) subscription is served by one of the NF Bs that represent another CP NF (NF C).

Within 3GPP, the following requirements for service selection (between at least NF, such as between an AMF and an SMF) have also been agreed upon: 1. If a requestor (ie, consumer) NF and a provider (ie, producer) There is already a tie between the NFs, and both NFs consume services from each other. For example, if an AMF (AMF-1) (which is also referred to as an AMF instance) has selected a particular SMF (SMF-1) (also referred to as an SMF instance) for a packet data When the unit (PDU) work phase is established, SMF-1 uses the service of AMF-1 for the same PDU work phase. 2. If there is no tie between a requester (ie, consumer) NF and a provider (ie, producer) NF, then the requester NF discovers subclause 6.8 according to 3GPP TS 23.501 V1.3.0. The principle of 1.2 supports an NF instance of a desired or expected NF service. The requester NF then selects an NF instance among the discovered NF instances.

It should be noted that NF A and NF B may be of different NF types, such as communication between an AMF and an SMF, or the like may have the same NF type, such as communication between v-SMF and h-SMF or Communication between the old AMF and the new AMF during the AMF relocation procedure. The tie between NF A and NF B implies a state of communication between NF A (service consumer, such as an AMF) and NF B (service producer). In other words, if NF A has invoked a service supplied by NF B and the request has been accepted, then a tie is established between NF A and NF B; therefore, if NF B subsequently expects to be called by having the same NF type as NF A One of the services provided by NF, then NF B will use NF A.

Currently, Hypertext Transfer Protocol version 2.0 (HTTP/2) is selected for the service-based interface between 5GC NF. However, the communication in HTTP/2 is unidirectional, that is, full two-way communication requires two client-server pairs, one for each direction. This means that when NF A is established to NF B by sending an HTTP request to NF B via a Transmission Control Protocol (TCP) connection, NF B needs to pass NF B when it wishes to invoke one of NF A services. Another TCP connection sends an HTTP request.

The following requirements are directed to the case where an AMF can be elegantly taken out of service when the common UE content context storage function has not been deployed (eg, by Unstructured Data Storage Function (UDSF)): The AMF can forward the registered UE The context (the context of UE content grouped by the same globally unique AMF ID ( GUAMI) value) to the target AMF within the same AMF set. The UE context context contains a unique AMF N2AP UE ID per AMF set. If there is an ongoing transaction (eg, N1 procedure) for a particular UE, then the AMF immediately forwards the UE context context to one of the target AMFs in the AMF set after completion of the ongoing transaction.

However, unlike the process of gracefully taking an AMF out of service, there is no mechanism for how to forward the UE context (multiple UE contexts) from one AMF to another AMF. As such, systems and methods are needed for transferring multiple resources between NFs.

The present invention provides systems and methods for transferring multiple resources between network functions (NFs). In some embodiments, a method of operating a source NF in a core network of a wireless communication system includes providing information describing a resource that the source NF intends to transmit to a target NF from the source NF to the target NF. The method also includes receiving, by the source NF, at least a portion of the response to the one of the resources indicated by the one of the resources from the source NF to the target NF. In response to receiving the response indicating that the transmission is at least partially accepted, the method includes transmitting the at least partially accepted resource corresponding to the transmission of the resource from the source NF to the target from the source NF to the target NF. In this way, a negotiable way to push multiple resources between NFs is provided. In some embodiments, this uses the HTTP/2 feature server push to perform the transfer. This may allow the target NF to control and direct the source NF for what resources are acceptable, such as the UE context, and the number of resources. This can also provide better performance by transmitting resources in advance to avoid unnecessary messaging and latency, which can avoid potential head-of-head (HOL) blocking by sending resources in separate streams.

In some embodiments, receiving the response indicating the at least partial acceptance of the transmission comprises receiving a response indicating that all of the transmissions are accepted. In some embodiments, receiving the response indicating that the at least partial acceptance of the transmission comprises receiving a response to the partial acceptance of the transmission indicating the resource. In some embodiments, receiving the response indicating that the portion of the transmission is accepted comprises receiving an indication of one of a subset of resources that have transmitted the target NF from the source NF. In some embodiments, the indication of receiving the subset of the resources that have received the target NF from the source NF includes receiving the indication of the subset of the resources as at least one of The type of one of the resources, one of the locations associated with the resources, one of the types of services associated with the resources, and/or one of the resources.

In some embodiments, the receiving the receipt indicating the at least partial acceptance of the transmission of the resource from the source NF to the target NF comprises receiving a request to indicate one of the at least partially accepted ones of a uniform resource indicator (URI) And transmitting the resources corresponding to the at least partially accepted information includes transmitting one or more PUSH_PROMISE frames for receiving the indicated resources by the at least portion.

In some embodiments, the method further includes receiving, by the source NF, a request from the target NF to transfer a single resource from the source NF to the target NF. In response to receiving the request to transmit the single resource, the method includes transmitting the single resource corresponding to the request from the source NF to the target NF.

In some embodiments, the method also includes deactivating the source NF. In some embodiments, prior to deactivating the source NF, the method includes waiting for a predetermined amount of time after transmitting the at least partially accepted resource corresponding to the transmission of the resource from the source NF to the target NF . In some embodiments, prior to deactivating the source NF, the method includes receiving a success of the transmission system corresponding to the at least partially accepted resources of the transmission of the resource from the source NF to the target NF confirm.

In some embodiments, one of the core networks of a wireless communication system source NF is adapted to provide information describing the source NF intended to be transmitted to a target NF from the source NF to the target NF; The source NF receives at least one of the responses from the target NF indicating that the transmission of the resource from the source NF to the target NF is received; and in response to receiving the response indicating that the transmission is at least partially accepted, The at least partially accepted resource of the transfer of the source NF to the resource of the target NF is transmitted from the source NF to the target NF. In certain embodiments, the source NF is further adapted to perform the methods of any of the embodiments discussed herein.

In some embodiments, one of the core networks of a wireless communication system source NF includes a communication interface and processing circuitry associated with the communication interface. The processing circuit is operative to cause the first NF to provide information indicating that the source NF is intended to transmit a resource of a target NF to the target NF; receiving, from the target NF, transmitting one of the resources indicating the source NF to the target NF Responding to at least one of the responses; and in response to receiving the response indicating that the transmission is at least partially accepted, transmitting the at least partially accepted resource corresponding to the transmission of the resource from the source NF to the target NF to the target NF. In some embodiments, the processing circuit is further operative to cause the source NF to perform the method of any of the embodiments discussed herein.

In some embodiments, one of the core networks of a wireless communication system source NF includes a processing unit operable to cause the source NF to state information about the source NF intended to be transmitted to a target NF resource. The source NF is provided to the target NF, and the source NF receives at least one of the responses from the target NF indicating that one of the resources from the source NF to the target NF is transmitted. The source NF also includes a transmitting unit operable to cause the source NF to respond to the receipt of the response indicating the at least partial acceptance of the transmission, the transmission corresponding to the resource from the source NF to the target NF At least partially accepted resources are transferred from the source NF to the target NF.

In some embodiments, a method of operating a target NF in a core network of a wireless communication system includes receiving, by the target NF, information from a source NF indicating resources that the source NF intends to transmit to the target NF. The method also includes responding to the at least partial acceptance of the transmission of one of the resources indicative of the source NF to the target NF from the target NF to the source NF, and in response to providing the at least partially accepted indication of the transmission In response, the target NF receives from the source NF the at least partially accepted resource for the transfer corresponding to the resource from the source NF to the target NF.

In some embodiments, providing the response indicating the at least partial acceptance of the transmission comprises providing the response indicating the full acceptance of the transmission of the resource from the source NF to the target NF. In some embodiments, providing the response indicating the at least partial acceptance of the transmission comprises providing the response indicating that the portion of the transmission of the resource from the source NF to the target NF is accepted. In some embodiments, providing the response indicating that the portion of the transmission is accepted comprises providing an indication of one of the subset of the resources that have transmitted the target NF from the source NF. In some embodiments, the indication of providing the subset of the resources that have received the target NF from the source NF includes providing the indication of the subset of the resources as at least one of The type of one of the resources, one of the locations associated with the resources, one of the types of services associated with the resources, and/or one of the resources.

In some embodiments, the at least partially accepting the transmission indicating the transmission of the resource from the source NF to the target NF comprises providing a request to one of the URIs indicating the at least partial acceptance, and the receiving corresponds to the The at least partially accepted resources include receiving one or more PUSH_PROMISE frames for receiving the indicated resources by the at least portion.

In some embodiments, the method also includes requesting, by the target NF, a single resource to be transmitted from the source NF (20-A) to the target NF (20-B) to the source NF. In response to providing the request to transmit the single resource, the method includes receiving, by the target NF, the single resource corresponding to the request from the source NF.

In some embodiments, the method also includes providing, by the target NF, an acknowledgement that the transmission of the at least partially accepted resource corresponding to the transfer of the resource from the source NF to the target NF is successful to the source NF.

In some embodiments, a target NF in a core network of a wireless communication system is adapted to receive, by the target NF, a resource from a source NF that the source NF intends to transmit to the target NF (20-B) Information that provides at least a portion of the acceptance of the transmission of one of the resources from the source NF to the target NF to the source NF; and in response to providing the response indicating that the transmission is at least partially accepted, The at least partially accepted resource of the transfer corresponding to the resource from the source NF to the target NF is received by the target NF from the source NF. In certain embodiments, the target NF is further adapted to perform the method of any of the embodiments discussed herein.

In some embodiments, a target NF in a core network of a wireless communication system includes a communication interface and processing circuitry associated with the communication interface. The processing circuit is operative to cause the target NF to: receive, by the target NF, information from a source NF stating a resource that the source NF intends to transmit to the target NF; transmitting one of the resources indicating the source NF to the target NF Responding to at least a portion of the response from the target NF to the source NF; and in response to providing the response indicating the at least partial acceptance of the transmission, the target NF receiving from the source NF corresponds to the source NF to the The at least partially accepted resource of the transfer of the resource of the target NF. In some embodiments, the processing circuit is further operative to cause the target NF to perform the method of any of the embodiments as discussed herein.

In some embodiments, a target NF in a core network of a wireless communication system includes a processing unit operative to cause the target NF to receive from a source NF an indication that the source NF is intended to be transmitted to the target NF Information of the resource, and one of the at least partial acceptances of the transmission of one of the resources indicating the source NF to the target NF is provided from the target NF to the source NF. The target NF also includes a transmitting unit operable to cause the target NF to receive resources corresponding to the source from the source NF to the target NF from the source NF in response to providing the response indicating the at least partial acceptance of the transmission. The at least partially accepted resource of the transfer.

In certain embodiments, the source NF and the target NF have the same NF type. In some embodiments, the source NF and the target NF are core access and mobility management functions (AMF) NFs, and the resources include a plurality of user equipment (UE) contexts. In some embodiments, the wireless communication system is a fifth generation (5G) wireless communication system.

The embodiments set forth below are presented to enable those skilled in the art to practice the embodiments and to illustrate the best mode of practicing the embodiments. The concept of the present invention will be immediately understood by those skilled in the art from the following description of the present invention and it will be appreciated that the application of these concepts is not specifically described herein. It should be understood that such concepts and applications fall within the scope of the invention.

The following requirements are directed to gracefully taking an access and mobility from the service when a Common User Equipment (UE) content context storage function has not been deployed (eg, by Unstructured Data Storage Function (UDSF)) as follows In the case of Management Function (AMF): The AMF can forward the registered UE context context (the UE context context grouped by the same globally unique AMF ID ( GUAMI) value) to the target AMF within the same AMF set. The UE context context contains a unique AMF N2AP UE ID per AMF set. If there is an ongoing transaction (eg, N1 procedure) for a particular UE, then the AMF immediately forwards the UE context context to the target AMF upon completion of the ongoing transaction.

However, there is no general mechanism for how the UE context context (multiple UE contexts) can be forwarded from one AMF to another AMF. As such, systems and methods are needed for transferring multiple resources between NFs.

The present invention provides systems and methods for transferring multiple resources between network functions (NFs). The resources may correspond to resources associated with one or more UEs, such as, for example, a UE context for AMF or a PDU session for SMF. In some embodiments, a method of operating a source NF in a core network of a wireless communication system includes providing information describing a source NF intended to be transmitted to a target NF from a source NF to a target NF. The method also includes receiving, by the source NF, at least one of the responses of the one of the resources indicated by the source NF to the target NF. In response to receiving an at least partially accepted response indicating the transmission, the method includes transmitting at least a portion of the received resource corresponding to the transmission of the resource from the source NF to the target from the source NF to the target NF. In this way, a negotiable way to push multiple resources between NFs is provided. In some embodiments, this uses HTTP/2 feature server push to perform the transfer. This may allow the target NF to control and direct what resources (such as the UE context) and the number of resources the source NF can accept. This can also provide better performance by transmitting resources in advance to avoid unnecessary messaging and latency, which can avoid potential head-of-head (HOL) blocking by sending resources in separate streams.

In this regard, FIG. 6 illustrates an example of a wireless communication system 10 in which one embodiment of the present invention may be implemented. As illustrated, the wireless communication system 10 includes a number of wireless devices 12 served by a Radio Access Network (RAN) that includes a number of radio access nodes 14 having corresponding coverage areas or cells 16. . The wireless communication system 10 also includes a core network 18. In the embodiments set forth herein, the wireless communication system 10 is a 3rd Generation Partnership Project (3GPP) fifth generation (5G) network, and as such, the RAN is a 5G RAN and the core network 18 is a 5G core ( 5GC). The core network 18 contains a number of NFs 20. As illustrated, the NF 20 includes an Access and Mobility Management Function (AMF) 22, Work Stream Management Function (SMF) 24, Network Repository Function (NRF) 26, Network Slice Selection Function (NSSF) 28, Network Exposure Function (NEF) 30, Principle Control Function (PCF) 32 and Application Function (AF) 34. NF 20 is also known as the NF example. Thus, as an example, multiple AMFs 22 may be referred to as AMF instances.

Many of the embodiments discussed herein are about preparing to revoke the startup source NF 20-A. However, the invention is not limited thereto. In some embodiments, such programs can be used for load balancing or for any type of network optimization.

Figure 7 illustrates the operation of source NF 20-A in accordance with some embodiments of the present invention. NF 20-A will provide information to the source NF 20-A that is intended to be transmitted to the target NF 20-B to the target NF 20-B (step 100). Preferably, the resources correspond to resources associated with one or more UEs, such as, for example, a UE context for AMF or a PDU session for SMF or the like. NF 20-A and NF 20-B may be of the same NF type, which preferably provides for a particular service of the UE associated with the resource to be transmitted. Source NF 20-A receives at least one of the responses from the target NF 20-B indicating that the transfer of resources from source NF 20-A to target NF 20-B is accepted (step 102). In response to receiving at least a partially accepted response to the transmission of the indication, source NF 20-A transmits at least a portion of the resources corresponding to the transmission of resources from source NF 20-A to target NF 20-B from source NF 20-A to Target NF 20-B (step 104).

In some embodiments, the response indicates the full acceptance of the transfer. In some embodiments, the response only indicates that one of the transmissions of the resource is partially accepted. In some embodiments, the portion of the transmission accepts an indication comprising receiving one of a subset of resources from the source NF 20-A delivery target NF. In some embodiments, the indication is indicative of the subset of the resources as one of: one of the types of resources, one of the locations associated with the resources, one of the resources associated with the resources The type of service and/or the number of such resources.

In some embodiments, steps 100 and 102 may be performed multiple times as the source NF 20-A negotiates with the target NF 20-B which resources will be transmitted. For any of a number of reasons, the target NF 20-B may need to transmit one of a single resource or group of resources from the source NF 20-A. An example would be the case where the transfer of resources in step 104 ends and one or more resources have not been properly transferred. In such cases, source NF 20-A may optionally receive a request to transfer a single resource from source NF 20-A to target NF 20-B (step 106). In response to receiving the request to transmit the single resource, the source NF 20-A may optionally transmit a single resource corresponding to the request (step 108).

In embodiments where source NF 20-A seeks to initiate a revocation, there may be a need to have source NF 20-A or some other entity ensure that the transfer of such resources is completed.

Figure 7 illustrates two options. In some embodiments, source NF 20-A may wait for a predetermined amount of time (step 110A). In some of these embodiments, source NF 20-A may assume that target NF 20-B will cause source NF 20-A to be aware of any failures of the transmission. If there is no such failure in the predetermined amount of time, the source NF 20-A can assume that the transfer was successful. In some embodiments, this failure indication is implicitly conveyed by a request from a single resource from the target NF 20-B, as discussed with respect to step 106.

In some embodiments, target NF 20-B may more clearly indicate a successful transfer. In such embodiments, source NF 20-A may optionally receive a confirmation of the success of the transmission (step 110B).

Regardless of how source NF 20-A is convinced that the transfer was successful, start source NF 20-A may be revoked (step 112). It should be noted that although these embodiments only illustrate the interaction between source NF 20-A and a single target NF 20-B, if target NF 20-B is only partially accepted, then source NF 20-A may/should be Another target NF 20-B is located to negotiate the delivery of the remainder of the resources. Source NF 20-A may/should be down only when all such resources are transmitted.

Figure 8 illustrates the operation of one of the targets NF 20-B in accordance with some embodiments of the present invention. In some embodiments, such steps are considered complementary to the steps set forth in relation to source NF 20-A in FIG. The target NF 20-B receives information from the source NF 20-A describing the resources that the source NF 20-A intends to transmit to the target NF 20-B (step 200). The target NF 20-B provides at least one of the responses to the transmission of the resource indicating the source NF 20-A to the target NF 20-B (step 202). In response to providing an at least partially accepted response indicating the transmission, the target NF 20-B receives from the source NF 20-A at least partially accepted resources corresponding to the transmission of resources from the source NF 20-A to the target NF 20-B (steps) 204).

In some embodiments, the response indicates the full acceptance of the transfer. In some embodiments, the response only indicates that one of the transmissions of the resource is partially accepted. In some embodiments, the portion of the transmission is instructed to include one of a subset of resources that receive the willingness to transmit the target NF from the source NF 20-A. In some embodiments, the indication is indicative of the subset of the resources as one of: a type of the resources, a location associated with the resources, associated with the resources, A type of service and/or a number of such resources.

In some embodiments, steps 200 and 202 may be performed multiple times when source NF 20-A negotiates which resources to transfer with target NF 20-B. For any of a number of reasons, the target NF 20-B may need to transmit one of a single resource or group of resources from the source NF 20-A. An example would be when the receipt of a resource in step 204 ends and one or more resources have not been properly transmitted. In such cases, the target NF 20-B may optionally provide a request to transfer a single resource from the source NF 20-A to the target NF 20-B (step 206). In response to providing a request to transmit the single resource, the target NF 20-B may optionally receive a single resource corresponding to the request (step 208).

There may be a need for source NF 20-A or some other entity to ensure that the transfer of such resources is completed. Thus, in some embodiments, target NF 20-B may explicitly indicate a successful transfer by providing an acknowledgement that the delivery system was successful (step 210).

In some embodiments, the solution to bridge the gap in 3GPP requirements provides a negotiable way to push a huge amount of resources between NFs and use HTTP/2 feature server push to perform the transfer. Compared to other alternatives, such embodiments allow the target NF 20-B to control and direct the source NF 20-A for which resources (eg, what kind of UE context) and resources are acceptable to the target NF 20-B. Such embodiments may provide better performance by transmitting resources in advance to avoid unnecessary messaging and latency and by transmitting resources in separate streams to avoid potential HOL blocking. Many of the embodiments discussed herein relate to source NF 20-A and target NF 20-B, both of which are AMF NF and which are UE contextual contexts. However, the invention is not limited thereto.

HTTP/2 provides a novel feature of server push. In HTTP 1.x, the client requests server resources in a "discovery and extraction" mode; that is, a client usually starts extracting a web page from the server with an HTTP request, and in response, the server Respond to the web page file. After receiving the file, the client parses the file to find the associated assets and then explicitly issues the requests one by one to extract the assets. To increase performance, server push is introduced in the HTTP/2 specification (RFC7540). With server push, the server can "push" the website assets to the client in advance without waiting for the client to explicitly request the site assets.

Certain embodiments herein relate to a resource push request and response mechanism between NFs 20. This provides a general purpose mechanism that can be used to transfer resources (e.g., UE context) from one NF 20 to other NFs 20, as an example, transmitting UE context contexts between AMFs.

Source NF 20-A should be consumed when an NF 20 (source NF 20-A) decides to transfer certain resources to another NF 20 (target NF 20-B) with the same NF type and in the same group/set One of the services is provided by the target NF 20-B to indicate that the source NF 20-A intends to transmit certain resources, some of which are selected to describe the context of the UE content that the source NF 20-A intends to transmit (eg, UE usage type, UE) Location) and also the number of UE contexts.

In order to allow the target NF 20-B consumption extraction service, the source NF 20-A provides information describing and/or indicating the resources that the source NF 20-A intends to transmit to the target NF 20-B, for example, information in the form: a normal resource uniform resource indicator (URI) in the case of pushing a resource; or indicating and/or declaring a collective URI for one of the multiple resources to be pushed for this push request; or even one of the actions of a complete service operation Locator (URL).

Target NF 20-B shall be able to accept or reject or partially accept certain resources in the receiving resource, for example, when target NF 20-B will be overloaded in the event of accepting too many resources, or when certain resources require an additional feature These resources have been exhausted on target NF 20-B.

If the target NF 20-B accepts the request, including partial acceptance, then the target NF 20-B will then act as a client to consume the service on the source NF 20-A to retrieve the resource to be transmitted, where in the previous step (100, These resources are set forth and/or indicated in 200). In the case of partial acceptance, the target NF 20-B indicates the desired number of resources to be retrieved in the service request or some other subset of the supplied resources.

When acting as a source of NF 20-A for a server, the source NF 20-A shall send a response and push the requested number of resources to the target NF 20-B. In some embodiments, this is accomplished using an optimized mechanism as discussed below.

In some embodiments, an optimized procedure can be used for retrieving huge resources (eg, UE context) between NF 20 (eg, two AMFs), using a collective URI and HTTP/2 servo The push mechanism sends a resource (eg, a UE context) for each individual stream.

In such embodiments, the target NF 20-B sends an HTTP request to the source NF 20-A, which has a collective URI indicating and/or clarifying all of the resources to be transmitted, rather than referring to a single resource. A URI.

In some embodiments, the collective URI is generated by source NF 20-A for this multiple_resources_transfer request and provided to target NF 20-B in the previous step (100, 200). The collective URI may also obtain parameters to indicate a particular portion of the resources to be transmitted. For example, for the UE context of AMF, a collective URI can be of the form: After receiving the request, in addition to sending the response to the target NF 20-B, the source NF 20-A also sends a PUSH_PROMISE frame for the resource to be transmitted (one such Push_Promise frame per resource). In some embodiments, each PUSH_PROMISE frame contains: a stream ID to a particular resource reserved for this particular resource. Thereafter, source NF 20-A begins transmitting the response to target NF 20-B. Each response contains the content of the corresponding resource to be delivered via the corresponding stream reserved for the resource.

In some embodiments, in the event that a resource is not successfully delivered, the target NF 20-B may explicitly issue an HTTP request to later retrieve resources from the source NF 20-A.

Figure 9 illustrates the operation of a system including a source NF 20-A and a target NF 20-B in accordance with certain embodiments of the present invention. This example uses a server push program and preferably the collective URI discussed above. When source NF 20-A (eg, an AMF) decides to transmit certain resources (eg, UE context or PDU session) to target NF 20-B (eg, another AMF within the same AMF set), source The NF 20-A consumes the Resource_Push service on the target NF to indicate the number of resources it intends to transmit and the resources it intends to transmit (step 300). NF 20-A and NF 20-B may have the same NF type, which preferably provides for a particular service with respect to one of the UEs associated with the resources. Preferably, NF 20-A and NF 20-B are in the same group/set. In some embodiments, this is one way of performing step 100 as discussed with respect to FIG. 7 and step 200 as discussed with respect to FIG.

The service request may also carry information on the selection of the resources to be transmitted. For example, for transmitting one of the UE content context AMF, the post-data may include the UE usage type, the UE location, and the like. In addition or in another option, the service request can carry information for transmission, such as a collective URI, which indicates and/or clarifies the resources to be transmitted. This collective URI is generated from source NF 20-A and provided to target NF 20-B. Preferably, the collective URI indicates and/or states all resources to be transmitted. As discussed above, the collective URI may also use parameters to indicate a particular portion of the resource to be transmitted. For example, for the UE context context of AMF, a collective URI may be in the form discussed above.

In some embodiments, source NF 20-A knows target NF 20-B due to a set concept, where NFs in the same NF set are considered to be from the same vendor, thereby supporting the same feature. However, such NFs may be known to one another in any other suitable manner. In some embodiments, the Resource_Push service can be a new or existing service provided by the target NF 20-B. This service to be used is dependent on the NF-specific and detailed service operating system implementation.

In some embodiments, UE context context information may be affected by opaque data, which may only be understood by NFs having the same NF type and from one of the same vendors. However, in some embodiments, a standardized UE context context may be used, which enables this UE context context to be transmitted even between NFs of the same type but from different vendors.

Returning now to Figure 9, target NF 20-B accepts (or partially accepts) the service request and responds with a positive Resource_Push service response (step 302A). In some embodiments, step 302A is a way of performing step 102 as discussed with respect to FIG. 7 and step 202 as discussed with respect to FIG.

In some embodiments, the target NF 20-B may reject the service request by responding to the passive Resource_Push service response (step 302B). Some reasons for potential rejection may include that the target NF 20-B will be overloaded in the event of accepting too many UE contexts, or that certain resources are not available for UE context contexts that require additional features. In such cases, no transmission may occur. However, source NF 20-A may attempt to transmit again with this target NF 20-B upon modification request, or may contact the other target NF 20-B to transmit the resources.

If the target NF 20-B accepts the request, including partial acceptance, the target NF 20-B consumes a Multiple_Resource_Fetch service on the source NF 20-A to retrieve it using the collective URI previously received (step 300) in the Resource_Push service request. (Step 304) A plurality of resources. In the case of partial acceptance, the target NF 20-B indicates the required number of resources to be retrieved in the service request or in some other subset of the resources. In some embodiments, step 304 is a way of performing step 102 as discussed with respect to FIG. 7 and step 202 as discussed with respect to FIG.

In addition, the target NF 20-B may also carry post-data in the service request indicating service-specific or resource-specific post-data (eg, data filtering), which is allowed for a Single_Resource_Fetch service. In some embodiments, the Multiple_Resource_Fetch and Single_Resource_Fetch services to be used may be different for different NFs. In some embodiments, such services may be specific defined extensions or new services of existing services. For example, for the AMF that transmits the context of the UE content, the Single_Resource_Fetch service can directly reuse the Namf_Communication UE content context delivery service; the Multiple_Resource_Fetch can also be reused with a new extension (this is because the current Namf_Communication UE content context service system per UE context context A Namf_Communication UE context delivery service with a clear UE identity and a target AMF still does not have a UE identifier is required, or a new content context delivery service is delivered for this massive UE context context.

Returning again to Figure 9, when the source NF 20-A acting as the server receives the request, the source NF 20-A sends a Multiple_Resource_Fetch service response along with a push request to transfer the resource (step 306). In some embodiments, each push request represents a Single_Resource_Fetch service request, as if it were originally received for a particular resource from the target NF 20-B and retained as a separate stream (stream r1 to stream rn) . In some embodiments, step 306 is a way of performing step 104 as discussed with respect to FIG. 7 and step 204 as discussed with respect to FIG.

In some embodiments, each push request includes a PUSH_PROMISE frame and a subsequent CONTINUATION frame, and carries a header block containing a complete set of one of the request header fields of the server belonging to the Single_Resource_Fetch service request. Contains: • The method pseudo-header contains the HTTP method and should always be GET • The path pseudo-header contains the URI of the specific resource. For the AMF to send the UE context, it may be: /Namf_Communication/UEContexts/<UE-ID> In the case of receiving data from the Multiple_Resource_Fetch service request to receive additional services or resources, such information should also be applied to the push request. The PUSH_PROMISE frame (push request) is sent after the header of the response but before the data frame carrying the response body.

The source NF 20-A sends a push response to the target NF 20-B using the reserved stream (steps 308-1 to 308-N). Each push response contains content corresponding to the corresponding resource via the corresponding stream reserved for the corresponding resource. In some embodiments, steps 308-1 through 308-N are also included in step 104 as discussed with respect to FIG. 7 and in step 204 as discussed with respect to FIG.

As discussed above, in the event that a resource is not successfully delivered, the target NF 20-B can explicitly issue an HTTP request to later retrieve the resource from the source NF 20-A. In the event that a resource is indicated in the push request but not successfully received from the source NF 20-A, the target NF 20-B may explicitly obtain a single resource after consuming the Single_Resource_Fetch service on the source NF 20-A (steps 310 and 312). In some embodiments, steps 310 and 312 are a method of performing steps 106 and 108, respectively, as discussed with respect to FIG. 7, and performing steps 206 and 208, respectively, as discussed with respect to FIG.

As discussed above, such embodiments may provide a negotiable way to push multiple resources between NFs. In some embodiments, this uses HTTP/2 feature server push to perform the transfer. This may allow the target NF to control and direct what resources (such as the UE context) and the number of resources the source NF can accept. This can also provide better performance by transmitting resources in advance to avoid unnecessary messaging and latency, which can avoid HOL blocking by sending resources in separate streams.

FIG. 10 illustrates an example of a network node 36 in which an NF 20 may be implemented in accordance with certain embodiments of the present invention. As illustrated, network node 36 includes hardware 38 that includes a communication interface 40 that is configured to establish and maintain a wired or wireless connection with one of the different network nodes of one of wireless communication systems 10. . Network node 36 further includes processing circuitry 42 that may have storage and/or processing capabilities. In particular, processing circuitry 42 may include one or more of a programmable processor, a special application integrated circuit, a field programmable gate array, or a combination of such instructions (not shown) adapted to execute instructions. Network node 36 further includes software 44, which is stored in network node 36 or accessible by network node 36 and executable by processing circuitry 42. The software 44 includes an application 46. For example, the application 46 can provide one of the same NF type or one of the different NF types or one of the NF 20 software applications.

Figure 11 illustrates a network node 36 in accordance with some other embodiments of the present invention. As illustrated, network node 36 includes one or more modules or units 48 and 50, each of which is implemented in software. As an example, if network node 36 implements source NF 20-A, processing unit 48 is operable to cause source NF 20-A to provide information describing the resources that source NF 20-A intends to transmit to target NF 20-B, and Receiving at least one of the responses indicating the transmission of one of the resources from the source NF 20-A to the target NF 20-B is accepted. The transmitting unit 50 is operative to cause the source NF 20-A to accept at least a portion of the transmission of the resource corresponding to the source NF 20-A to the target NF 20-B in response to receiving the response indicating that the transmission is at least partially accepted Resources are transferred from source NF 20-A to target NF 20-B as set forth above with respect to, for example, FIG. 7 and/or FIG. As another example, if network node 36 implements target NF 20-B, processing unit 48 is operable to cause target NF 20-B to receive from a source NF 20-A that the source NF 20-A is intended to be transmitted to the target NF 20 -B's resource information and provides at least one of the responses to one of the resources indicated from source NF 20-A to target NF 20-B. The transmitting unit 50 is operative to cause the target NF 20-B to receive at least partial acceptance of the transmission of the resource corresponding to the source NF 20-A to the target NF 20-B in response to providing a response indicating at least partial acceptance of the transmission. Resources are as described above with respect to, for example, FIG. 8 and/or FIG.

At least some of the following abbreviations may be used in the present invention. If there is an inconsistency between abbreviations, priority should be given to how to use abbreviations above If listed below multiple times, the first listing should take precedence over any subsequent listing. • 3GPP 3rd Generation Partnership Program • 5G 5th Generation • 5GC 5th Generation Core • AF Application Features • AMF Access and Mobility Management Features • AUSF Authentication Server Features • CP Control Plane • GUAMI Global Unique AMF ID • HTTP/2 Hypertext Transfer Protocol Version 2.0 • HOL Head Blocking • ID Identifier • IE Information Elements • NEF Network Exposure Features • NF Network Features • NRF Network Repository Features • NSSF Network Slice Selection Features • O&M Operations And Maintenance • PCF Principle Control Function • PDU Packet Data Unit • RAN Radio Access Network • SMF Work Stream Management Function • TCP Transmission Control Protocol • TS Technical Specification • UDM Unified Data Management • UDSF Unstructured Data Storage Function • UE Use Device • URI Uniform Resource Indicator • URL Uniform Resource Locator

Improvements and modifications of the embodiments of the invention will be apparent to those skilled in the art. All such improvements and modifications are considered to be within the scope of the concepts disclosed herein.

10‧‧‧Wireless communication system

12‧‧‧Wireless devices

14‧‧‧ Radio Access Node

16‧‧‧corresponding to the covered area or community

18‧‧‧core network

20-A‧‧‧Source network function

20-B‧‧‧Target network function

22‧‧‧Access and operational management functions

24‧‧‧Working stage management function

26‧‧‧Network Repository Function

28‧‧‧Network Slice Selection

30‧‧‧Network exposure function

32‧‧‧ principle control function

34‧‧‧Application Features

36‧‧‧Network node

38‧‧‧ Hardware

40‧‧‧Communication interface

42‧‧‧Processing Circuit

44‧‧‧Software

46‧‧‧Application

48‧‧‧Processing unit/unit

50‧‧‧Transfer unit/unit

100‧‧‧Steps/provided

102‧‧‧Steps/reception

104‧‧‧Steps/Transfer

106‧‧‧Steps/reception

108‧‧‧Steps/Transfer

110A‧‧‧Steps/Waiting

110B‧‧‧Steps/reception

112‧‧‧ Step / Cancel Start

200‧‧‧Steps/Previous Steps/Reception

202‧‧‧Steps/provided

204‧‧‧Steps/reception

206‧‧‧Steps/provided

208‧‧‧Steps/reception

210‧‧‧Steps/provided

300‧‧‧Steps/Providing/Receiving

302A‧‧‧Steps/Providing/Receiving

302B‧‧‧Steps

304‧‧‧Steps/Providing/Receiving

306‧‧‧Steps/receive/transfer

308-1‧‧‧Steps

308-N‧‧‧Steps

310‧‧‧Steps/Providing/Receiving

312‧‧‧Steps/receive/transfer

NF A‧‧‧Consumer Network Function/Control Plane Network Function/Service Consumer

NF B‧‧‧ Producer Network Function/Control Plane Network Function/Service Producer

NF C‧‧‧Control Plane Network Function

Naf‧‧‧Service-based interface presented by application features

Namf‧‧‧Service-based interface demonstrated by access and mobility management functions

Nausf‧‧‧ Service-based interface demonstrated by the authentication server function

Nnef‧‧‧Service-based interface exposed by web exposure

Nnrf‧‧‧Service-based interface presented by the web repository feature

Nnssf‧‧‧ Service-based interface presented by the network slice selection feature

Npcf‧‧‧Service-based interface demonstrated by the principle control function

Nsmf‧‧‧Service-based interface presented by the work phase management function

Nudm‧‧‧Service-based interface presented by unified data management

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are incorporated in FIG Figures 1 and 2 illustrate a non-roaming and roaming fifth generation (5G) system architecture as defined by the Third Generation Partnership Project (3GPP). Figure 3 illustrates one request-response interaction between a consumer network function (NF) and a producer NF. 4 and 5 illustrate a subscription-notification mechanism in which one NF subscribes to one of its own NF services on its own or another NF. Figure 6 illustrates an example of a wireless communication system in which embodiments of the present invention may be implemented. Figure 7 illustrates the operation of a source network function (NF) in accordance with some embodiments of the present invention. Figure 8 illustrates the operation of one of the targets NF in accordance with some embodiments of the present invention. Figure 9 illustrates the operation of a system including a source NF and a target NF in accordance with some embodiments of the present invention. 10 and 11 illustrate an example embodiment in which one of the NF network nodes can be implemented.

Claims (34)

A method of operating a source network function (NF) (20-A) in a core network (18) of a wireless communication system (10), comprising: an indication of the source NF (20-A) intended Information transmitted to the target NF (20-B) resource from the source NF (20-A) (100, 300) to a target NF (20-B); from the source NF (20-A) The target NF (20-B) receives (102, 302A, 304) indicating that at least one of the responses from one of the source NF (20-A) to the target NF (20-B) transmits a response; and responds to Receiving the response indicating at least partial acceptance of the transmission, the at least partially accepted resource corresponding to the transmission of the resource from the source NF (20-A) to the target NF (20-B) from the source NF ( 20-A) Transfer (104, 306, 308) to the target NF (20-B). The method of claim 1, wherein the receiving the at least part of the transmission indicating the transmission of the resource from the source NF (20-A) to the target NF (20-B) comprises: receiving an indication from the source NF ( 20-A) One of the responses to the transmission of the resource to the target NF (20-B). The method of claim 1, wherein the receiving the at least part of the transmission indicating the transmission of the resource from the source NF (20-A) to the target NF (20-B) comprises: receiving an indication from the source NF ( 20-A) One of the responses to the transmission of the resource to the target NF (20-B) is one of the responses. The method of claim 3, wherein the receiving the portion of the transmission indicating the transmission from the source NF (20-A) to the target NF (20-B) further comprises: receiving the source from the source NF ( 20-A) An indication of one of a subset of the resources to transmit the target NF (20-B). The method of claim 4, wherein the indication of receiving the subset of the resources that have transmitted the target NF (20-B) from the source NF (20-A) comprises: the subset of the resources The indication is received as at least one of the group consisting of: one of the types of resources, one of the locations associated with the resources, one of the types of services associated with the resources, and the resources One number. The method of any one of claims 1 to 5, wherein: receiving (102, 302A, 304) indicating the at least the transmission of the resource from the source NF (20-A) to the target NF (20-B) The partially accepted response includes receiving a request to indicate that the at least one of the one of the uniform resource indicator URIs is received; and transmitting the resources corresponding to the at least partially accepted comprises transmitting one or more PUSH_PROMISE frames for the at least Partially accepting such resources as indicated. The method of any one of claims 1 to 6, further comprising: receiving (106, 310) from the source NF (20-A) from the target NF (20-B) to source a single resource from the source NF (20-A) transmits a request to one of the target NFs (20-B); and in response to receiving the request to transmit the single resource, the individual resource corresponding to the request is from the source NF (20-A) Transfer (108, 312) to the target NF (20-B). The method of any one of claims 1 to 7, further comprising revoking (112) the source NF (20-A). The method of claim 8, further comprising: prior to revoking the source NF (20-A), the resource corresponding to the source NF (20-A) to the target NF (20-B) The at least partially accepted resources are transmitted (110A) for a predetermined amount of time after the source NF (20-A) is transferred to the target NF (20-B). The method of claim 8, further comprising: receiving (110B) a resource corresponding to the source NF (20-A) to the target NF (20-B) before deactivating the source NF (20-A) The confirmation of the transmission of the transmission from the source NF (20-A) to the target NF (20-B) is at least partially accepted by the transmission. The method of any one of claims 1 to 10, wherein the source NF (20-A) and the target NF (20-B) have the same NF type. The method of claim 11, wherein the source NF (20-A) and the target NF (20-B) are core access and mobility management functions AMF NF and the resources include a plurality of user equipment UE content contexts. The method of any one of claims 1 to 12, wherein the wireless communication system is a fifth generation 5G wireless communication system. A source network function (NF) (20-A) in a core network (18) of a wireless communication system (10), the first NF (20-A) being adapted to: (20-A) Information intended for transmission to a target NF (20-B) resource from the source NF (20-A) to the target NF (20-B); from the source NF (20-A) The target NF (20-B) receives at least one of the responses indicating the transmission of the resource from the source NF (20-A) to the target NF (20-B); and responds to receiving the indication that the transmission is at least The partially accepted response transmits the at least partially accepted resource corresponding to the transfer of the resource from the source NF (20-A) to the target NF (20-B) from the source NF (20-A) to The target NF (20-B). The source NF (20-A) of claim 14, wherein the source NF (20-A) is further adapted to perform the method of any one of claims 2 to 13. A source network function (NF) (20-A) in a core network (18) of a wireless communication system (10), comprising: a communication interface (40); and processing circuitry (42) Associated with the communication interface (40), wherein the processing circuit (42) is operative to cause: the first NF (20-A): will clarify that the source NF (20-A) is intended to be transmitted to a target NF (20) -B) information on the resources provided to the target NF (20-B); from the target NF (20-B) receiving resources indicating the source NF (20-A) to the target NF (20-B) Responding to receiving at least one of the responses, and responding to receiving the response indicating that the transmission is at least partially accepted, corresponding to the resource from the source NF (20-A) to the target NF (20-B) The at least partially accepted resource transmitted is transmitted to the target NF (20-B). The source NF (20-A) of claim 16, wherein the processing circuit (42) is further operable to cause the source NF (20-A) to perform the method of any one of claims 2 to 13. A source network function (NF) (20-A) in a core network (18) of a wireless communication system (10), comprising: a processing unit (48) operative to cause the source NF (20-A) will provide information on the source NF (20-A) information intended to be transmitted to a target NF (20-B) from the source NF (20-A) to the target NF (20-B), And receiving, by the source NF (20-A) from the target NF (20-B), one of the at least partial acceptances of the transmission of one of the resources from the source NF (20-A) to the target NF (20-B) Responding; and a transmitting unit (50) operable to cause the source NF (20-A) to respond to receipt of the response indicating that the transmission is at least partially accepted, corresponding to the source NF (20-A) The at least partially accepted resource for the transfer to the resource of the target NF (20-B) is transmitted from the source NF (20-A) to the target NF (20-B). A method of operating a target network function (NF) (20-B) in a core network (18) of a wireless communication system (10), comprising: from the target NF (20-B) Source NF (20-A) Receive (200, 300) describes the source NF (20-A) information intended to be transmitted to the target NF (20-B); will be indicated from the source NF (20-A) to One of the at least partial acceptances of the transmission of one of the resources of the target NF (20-B) is provided in response to the target NF (20-B) (202, 302A, 304) to the source NF (20-A); Providing the response indicating the at least partial acceptance of the transmission, the target NF (20-B) receiving (204, 306, 308) from the source NF (20-A) corresponding to the source NF (20-A) The at least partially accepted resource for the transfer to the resource of the target NF (20-B). The method of claim 19, wherein the at least partially accepting the transmission indicating the transmission of the resource from the source NF (20-A) to the target NF (20-B) comprises: providing an indication from the source NF ( 20-A) The response to the transmission of the resource to the target NF (20-B) is fully accepted. The method of claim 19, wherein the at least partially accepting the transmission indicating the transmission of the resource from the source NF (20-A) to the target NF (20-B) comprises: providing an indication from the source NF ( 20-A) The response to the portion of the transmission to the target NF (20-B) is accepted. The method of claim 21, wherein the providing the portion of the transmission indicating the transfer from the source NF (20-A) to the target NF (20-B) further comprises: providing the source from the source NF ( 20-A) An indication of one of a subset of the resources that convey the target NF (20-B) willingness. The method of claim 22, wherein the providing the subset of the resources that have transmitted the target NF (20-B) from the source NF (20-A) comprises: providing the subset of the resources The indication is as at least one of the group consisting of: one of the types of resources, one of the locations associated with the resources, one of the types of services associated with the resources, and the resources A number. The method of any one of claims 19 to 23, wherein: providing the at least partial acceptance of the transmission indicating the resource from the source NF (20-A) to the target NF (20-B) comprises providing Requiring to request that at least one of the one of the uniform resource indicator URIs is received; and receiving the resources corresponding to the at least partially accepted includes receiving one or more PUSH_PROMISE frames for receiving the at least partially indicated resources . The method of any one of claims 19 to 24, further comprising: transmitting, by the target NF (20-B), a single resource from the source NF (20-A) to the target NF (20- B) one request to provide (206, 310) to the source NF (20-A); and in response to providing the request to transmit the single resource from the target NF (20-B) from the source NF (20-A) Receiving (208, 312) the single resource corresponding to the request. The method of claim 19, further comprising: by the target NF (20-B) the at least part of the transfer corresponding to the resource from the source NF (20-A) to the target NF (20-B) One of the accepted resources is a confirmation that the delivery is successful (210) to the source NF (20-A). The method of any one of claims 19 to 26, wherein the source NF (20-A) and the target NF (20-B) have the same NF type. The method of claim 27, wherein the source NF (20-A) and the target NF (20-B) are core access and mobility management functions AMF NF and the resources include a plurality of user equipment UE contexts . The method of any one of clauses 19 to 28, wherein the wireless communication system is a fifth generation 5G wireless communication system. A target network function (NF) (20-B) in a core network of a wireless communication system (10), the target NF (20-B) adapted to: by the target NF (20-B) Receiving information from a source NF (20-A) stating that the source NF (20-A) intends to transmit to the target NF (20-B); will indicate from the source NF (20-A) to the target NF One of the at least partial acceptances of the transmission of one of the resources (20-B) is provided from the target NF (20-B) to the source NF (20-A); and in response to providing an indication that the transmission is at least partially accepted In response, the target NF (20-B) receives at least the portion of the transmission corresponding to the resource from the source NF (20-A) to the target NF (20-B) from the source NF (20-A) Accepted resources. The target NF (20-B) of claim 30, wherein the target NF (20-B) is further adapted to perform the method of any one of claims 20 to 29. A target network function (NF) (20-B) in a core network (18) of a wireless communication system (10), comprising: a communication interface (40); and processing circuitry (42) Associated with the communication interface (40), wherein the processing circuit (42) is operative to cause the target NF (20-B): to be interpreted by the target NF (20-B) from a source NF (20-A) The source NF (20-A) intends to transmit information to the resource of the target NF (20-B); transmits one of the resources indicating the source NF (20-A) to the target NF (20-B) At least partially accepting one of the responses from the target NF (20-B) to the source NF (20-A); and responding to providing the response indicating that the transmission is at least partially accepted by the target NF (20-B) Receiving, from the source NF (20-A), the at least partially accepted resource of the transmission corresponding to the resource from the source NF (20-A) to the target NF (20-B). The target NF (20-B) of claim 32, wherein the processing circuit (42) is further operable to cause the target NF (20-B) to perform the method of any one of claims 20 to 29. A target network function (NF) (20-B) in a core network (18) of a wireless communication system (10), comprising: a processing unit (48) operative to cause the target NF Receiving information from a source NF (20-A) stating that the source NF (20-A) intends to transmit to the target NF (20-B) and will indicate from the source NF (20-A) to the target One of the at least partial acceptances of the transmission of one of the resources of NF (20-B) is provided from the target NF (20-B) to the source NF (20-A); and a transmission unit (50) operable Having the target NF (20-B) receive from the source NF (20-A) corresponding to the source NF (20-A) to the target NF (in response to providing the response indicating that the transmission is at least partially accepted) The at least partially accepted resource of the transfer of the resource of 20-B).