METHOD AND APPARATUS FOR TRAFFIC PROBING

Embodiments of the present disclosure provide method and apparatus for traffic probing. A method performed by a sender network function (NF) includes sending a first message to a receiver NF. The first message comprises a new HTTP header which comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF.

TECHNICAL FIELD

The non-limiting and exemplary embodiments of the present disclosure generally relate to the technical field of communications, and specifically to methods and apparatuses for traffic probing.

BACKGROUND

In communication networks for example NR (new radio) as defined by 3rd Generation Partnership Project (3GPP), it has introduced Service Based Architecture (SBA) where network entities are specified as Network Functions (NFs) providing/consuming services. NF service producer and NF service consumer communicate with each other via Service Based Interface (SBI) implemented with Hyper Text Transfer Protocol (HTTP) protocol.

SUMMARY

According to clause 7.1.2 of 3GPP TS 23.501 V17.1.1, the disclosure of which is incorporated by reference herein in its entirety, the end-to-end interaction between two Network Functions (Consumer and Producer) within an NF service framework follows two mechanisms, irrespective of whether Direct Communication or Indirect Communication is used: “Request-response” and “Subscribe-Notify”.

FIG.1shows an example of “Request-response” mechanism according to an embodiment of the present disclosure. A Control Plane NF_B (NF Service Producer) is requested by another Control Plane NF_A (NF Service Consumer) to provide a certain NF service, which either performs an action or provides information or both. NF_B provides an NF service based on the request by NF_A. In order to fulfill the request, NF_B may in turn consume NF services from other NFs. In Request-response mechanism, communication is one to one between two NFs (consumer and producer) and a one-time response from the producer to a request from the consumer is expected within a certain timeframe. The NF Service Producer may also add a Binding Indication (see clause 6.3.1.0 of 3GPP TS 23.501 V17.1.1) in the Response, which may be used by the NF Service Consumer to select suitable NF service producer instance(s) for subsequent requests. For indirect communication, the NF Service Consumer copies the Binding Indication into the Routing Binding indication, that is included in subsequent requests, to be used by the SCP to discover a suitable NF service producer instance(s).

FIG.2shows an example of “Subscribe-Notify” mechanism according to an embodiment of the present disclosure. A Control Plane NF_A (NF Service Consumer) subscribes to NF Service offered by another Control Plane NF_B (NF Service Producer). Multiple Control Plane NFs may subscribe to the same Control Plane NF Service. NF B notifies the results of this NF service to the interested NF(s) that subscribed to this NF service. The subscription request shall include the notification endpoint, i.e. Notification Target Address) and a Notification Correlation ID (e.g. the notification URL (Uniform Resource Locator)) of the NF Service Consumer to which the event notification from the NF Service Producer should be sent to.

The notification endpoint URL can contain both the notification endpoint and the Notification Correlation ID.

The NF Service Consumer may add a Binding Indication (see clause 6.3.1.0 of 3GPP TS 23.501 V17.1.1) in the subscribe request, which may be used by the NF Service Producer to discover a suitable notification endpoint. For indirect communication, the NF Service Producer copies the Binding Indication into the Routing Binding Indication, that is included in the response, to be used by the SCP to discover a suitable notification target. The NF Service Producer may also add a Binding Indication (see clause 6.3.1.0 of 3GPP TS 23.501 V17.1.1) in the subscribe response, which may be used by the NF Service Consumer (or SCP (service communication proxy)) to select suitable NF service producer instance(s) or NF producer service instance. In addition, the subscription request may include notification request for periodic updates or notification triggered through certain events (e.g. the information requested gets changed, reaches certain threshold etc.). The subscription for notification can be done through one of the following ways:Explicit subscription: A separate request/response exchange between the NF Service Consumer and the NF Service Producer; orImplicit subscription: The subscription for notification is included as part of another NF service operation of the same NF Service; orDefault notification endpoint: Registration of a notification endpoint for each type of notification the NF consumer is interested to receive, as an NF service parameter with the NRF during the NF and NF service Registration procedure as specified in clause 4.17.1 of 3GPP TS 23.502 V17.1.0, the disclosure of which is incorporated by reference herein in its entirety.

The NF Service Consumer may also add a Binding Indication (see clause 6.3.1.0 of 3GPP TS 23.501 V17.1.1) in the response to the notification request, which may be used by the NF Service Producer to discover a suitable notification endpoint. For indirect communication, the NF Service Producer copies the Binding Indication into the Routing Binding indication that is included in subsequent notification requests. The binding indication is then used by the SCP to discover a suitable notification target.

FIG.3shows an example of “Subscribe-Notify” mechanism according to another embodiment of the present disclosure. A Control Plane NF_A may also subscribe to NF Service offered by Control Plane NF_B on behalf of Control Plane NF_C, i.e. it requests the NF Service Producer to send the event notification to another consumer(s). In this case, NF_A includes the notification endpoint, i.e. Notification Target Address) and a Notification Correlation ID, of the NF_C in the subscription request. NF_A may also additionally include the notification endpoint and a Notification Correlation ID of NF A associated with subscription change related Event ID(s), e.g. Subscription Correlation ID Change, in the subscription request, so that NF_A can receive the notification of the subscription change related event. The NF_A may add Binding Indication (see clause 6.3.1.0) in the subscribe request.

Routing of the messages for the NF interaction mechanisms above may be direct, as shown in theFIGS.1-3, or indirect. In the case of Indirect Communication, an SCP is employed by the NF service consumer. The SCP routes messages between NF service consumers and NF service producers based on the Routing Binding Indication if available, and may do discovery and associated selection of the NF service producer on behalf of an NF service consumer.FIG.4shows a principle for a request-response interaction using Indirect Communication according to an embodiment of the present disclosure.FIG.5shows an example of a subscribe-notify interaction using Indirect Communication according to an embodiment of the present disclosure. The subscribe request and notify request can be routed by different SCPs.

In real network deployments, there are requirement to monitor traffic between certain network entities, e.g., to filter the traffics between two specified network entities and/or apply extra business logics like troubleshooting, performance measurement, etc.

In legacy networks, the communications model between network entities mainly based on bi-directional connection. Traffic probe can be applied with the address information of the two ends of the connection, e.g., IP addresses and port numbers of two ends of a TCP (Transmission Control Protocol)/UDP (User Datagram Protocol) connections, or the originator and terminator of the diameter path.

In 5GC (in 5G (fifth generation) Core Network) Service Based Architecture, the traffic probe with address information cannot be used due to some reasons.

As a first example, HTTP is one direction connection with request/response traffic model. Communication between two NFs usually uses multiple HTTP connections with HTTP client/server pairs. E.g., on N11 interface, access and mobility function (AMF) invokes SMF (Session Management Function) PDU (Protocol Data Unit) session service where SMF act as HTTP server (AMF create HTTP connection towards SMF) and at the same time SMF invoke AMF Communication services (SMF create HTTP connection towards the AMF).

As a second example, one NF may consume multiple services on another NF, which are exposed on different service access points with different IP (Internet protocol) address/port numbers. e.g., SMF invokes AMF Communication Service, Event Exposure Service as well as Mobile Terminating service.

As a third example, for redundancy, message prioritization, even for the same service, multiple HTTP connections will be established between two NFs to transport normal traffics. Furthermore, for HTTP/2 stream ID (identifier) exhaustion issue, new HTTP connection may be created at any time to replace old HTTP connection.

To overcome or mitigate at least one of above mentioned problems or other problems, a new solution for traffic probing is needed for example in 5GC with Service Based Architecture.

In an embodiment, as required for Network Function registration and discovery, each NF in 5GC holds a globally unique NF instance identifier. To uniquely identifier an NF pair for traffic probing, the NF instance identifier of the two NFs could be the most suitable information. To enable the traffic probing, it requires that the source NF instance ID and the target NF instance ID are carried in a service message over SBI.

In a first embodiment, the source NF instance ID and/or the target NF instance ID may be carried in a message body.

In a second embodiment, the source NF instance ID and/or the target NF instance ID may be carried in an existing HTTP header required by SBI protocols.

In a third embodiment, the source NF instance ID and/or the target NF instance ID may be carried in a new HTTP header, which may be less impact to existing protocol definition (compare to the second embodiment) and more efficient for traffic filtering (compare to the first embodiment).

In a first aspect of the disclosure, there is provided a method performed by a sender network function (NF). The method comprises sending a first message to a receiver NF. The first message comprises a new Hyper Text Transfer Protocol (HTTP) header which comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF.

In an embodiment, the NF instance ID of the sender NF and the NF instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

In an embodiment, the new HTTP header further comprises an NF service instance ID of the sender NF and an NF service instance ID of the receiver NF.

In an embodiment, the NF instance ID of the sender NF, the NF instance ID of the receiver NF, the NF service instance ID of the sender NF and the NF service instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

In an embodiment, the first message is a service request message or a notification request message.

In an embodiment, the method further comprises receiving a second message from the receiver NF. The second message comprises the NF instance ID of the sender NF and the NF instance ID of the receiver NF.

In an embodiment, the second message further comprises the NF service instance ID of the sender NF and the NF service instance ID of the receiver NF.

In an embodiment, the second message is an HTTP message.

In an embodiment, the second message is a service response message or a notification response message.

In an embodiment, the sender NF is an NF service consumer or an NF service producer.

In an embodiment, the receiver NF is an NF service producer or an NF service consumer.

In an embodiment, the sender NF is an HTTP client and the receiver NF is an HTTP server.

In an embodiment, the first message and second message further comprise an NF set ID of the sender NF and an NF set ID of the receiver NF.

In a second aspect of the disclosure, there is provided a method performed by a receiver network function (NF). The method comprises receiving a first message from a sender NF. The first message comprises a new HTTP header which comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF.

In an embodiment, the NF instance ID of the sender NF and the NF instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

In an embodiment, the new HTTP header further comprises an NF service instance ID of the sender NF and an NF service instance ID of the receiver NF.

In an embodiment, the NF instance ID of the sender NF, the NF instance ID of the receiver NF, the NF service instance ID of the sender NF and the NF service instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

In an embodiment, the first message is a service request message or a notification request message.

In an embodiment, the method further comprises sending a second message to the sender NF, wherein the second message comprises the NF instance ID of the sender NF and the NF instance ID of the receiver NF.

In an embodiment, the second message further comprises the NF service instance ID of the sender NF and the NF service instance ID of the receiver NF.

In an embodiment, the second message is an HTTP message.

In an embodiment, the second message is a service response message or a notification response message.

In an embodiment, the sender NF is an NF service consumer or an NF service producer.

In an embodiment, the receiver NF is an NF service producer or an NF service consumer.

In an embodiment, the sender NF is an HTTP client and the receiver NF is an HTTP server.

In an embodiment, the first message and second message further comprise an NF set ID of the sender NF and an NF set ID of the receiver NF.

In a third aspect of the disclosure, there is provided a method performed by a service communication proxy (SCP). The method comprises receiving a third message from a sender network function (NF) or a receiver NF. The third message comprises a new HTTP header which comprises an NF instance ID of the sender NF and an NF instance ID of the receiver NF. The method further comprises sending a fourth message to the receiver NF or the sender NF. The fourth message comprises the new HTTP header which comprises the NF instance ID of the sender NF and the NF instance ID of the receiver NF.

In an embodiment, the NF instance ID of the sender NF and the NF instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

In an embodiment, the new HTTP header further comprises an NF service instance ID of the sender NF and an NF service instance ID of the receiver NF.

In an embodiment, the NF instance ID of the sender NF, the NF instance ID of the receiver NF, the NF service instance ID of the sender NF and the NF service instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

In an embodiment, the third message and the fourth message comprise at least one of a service request message, a notification request message, a service response message, or a notification response message.

In an embodiment, the sender NF is an NF service consumer or an NF service producer.

In an embodiment, the receiver NF is NF service consumer or an NF service producer.

In an embodiment, the sender NF is an HTTP client and the receiver NF is an HTTP server.

In an embodiment, the third message and the fourth message further comprise an NF set ID of the sender NF and an NF set ID of the receiver NF.

In a fourth aspect of the disclosure, there is provided a method performed by a network entity (NE). The method comprises sending or receiving a message exchanged between a sender NF and a receiver NF. The message comprises a new HTTP header which comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF. The method further comprises identifying the message exchanged between the sender NF and the receiver NF based on the NF instance ID of the sender NF and the NF instance ID of the receiver NF.

In an embodiment, the new HTTP header further comprises an NF service instance ID of the sender NF and an NF service instance ID of the receiver NF.

In an embodiment, the message exchanged between the sender NF and the receiver NF is identified further based on the NF service instance ID of the sender NF and the NF service instance ID of the receiver NF.

In an embodiment, the message is an HTTP message.

In an embodiment, the message is a service request message or a notification request message or a service response message or a notification response message.

In an embodiment, the sender NF is an HTTP client and the receiver NF is an HTTP server.

In an embodiment, the message further comprises an NF set ID of the sender NF and an NF set ID of the receiver NF.

In an embodiment, the method further comprises performing an operation on the identified message.

In an embodiment, the operation comprises at least one of monitoring traffic, filtering traffic, applying policy, troubleshooting, or performance measurement.

In another aspect of the disclosure, there is provided a sender network function (NF). The sender NF comprises a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor. Said sender NF is operative to send a first message to a receiver NF. The first message comprises a new Hyper Text Transfer Protocol (HTTP) header which comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF.

In another aspect of the disclosure, there is provided a receiver network function (NF). The receiver NF comprises a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor. Said receiver NF is operative to receive a first message from a sender NF. The first message comprises a new HTTP header which comprises an NF instance identifier (ID) of an sender NF and an NF instance ID of an receiver NF.

In another aspect of the disclosure, there is provided a service communication proxy (SCP). The SCP comprises a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor. Said SCP is operative to receive a third message from a sender network function (NF) or a receiver NF. The third message comprises a new HTTP header which comprises an NF instance ID of the sender NF and an NF instance ID of the receiver NF. Said SCP is further operative to send a fourth message to the receiver NF or the sender NF. The fourth message comprises the new HTTP header which comprises the NF instance ID of the sender NF and the NF instance ID of the receiver NF.

In another aspect of the disclosure, there is provided a network entity (NE). The NE comprises a processor and a memory coupled to the processor. Said memory contains instructions executable by said processor. Said NE is operative to send or receive a message exchanged between a sender NF and a receiver NF. The message comprises a new HTTP header which comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF. Said NE is further operative to identify the message exchanged between the sender NF and the receiver NF based on the NF instance ID of the sender NF and the NF instance ID of the receiver NF.

In another aspect of the disclosure, there is provided a sender NF. The sender NF comprises a sending module configured to send a first message to a receiver NF. The first message comprises a new HTTP header which comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF.

In an embodiment, the sender NF further comprises a receiving module configured to receive a second message from the receiver NF. The second message comprises the NF instance ID of the sender NF and the NF instance ID of the receiver NF.

In another aspect of the disclosure, there is provided a receiver NF. The receiver NF comprises a receiving module configured to receive a first message from a sender NF. The first message comprises a new HTTP header which comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF.

In an embodiment, the receiver NF further comprises a sending module configured to send a second message to the sender NF. The second message comprises the new HTTP header which comprises the NF instance ID of the sender NF and the NF instance ID of the receiver NF.

In another aspect of the disclosure, there is provided a SCP. The SCP comprises a receiving module configured to receive a third message from a sender network function (NF) or a receiver NF. The third message comprises a new HTTP header which comprises an NF instance ID of the sender NF and an NF instance ID of the receiver NF. The SCP further comprises a sending module configured to send a fourth message to the receiver NF or the sender NF. The fourth message comprises the new HTTP header which comprises the NF instance ID of the sender NF and the NF instance ID of the receiver NF.

In another aspect of the disclosure, there is provided a NE. The NE comprises a sending or receiving module configured to send or receive a message exchanged between a sender NF and a receiver NF. The message comprises a new HTTP header which comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF. The NE further comprises an identifying module configured to identify the message exchanged between the sender NF and the receiver NF based on the NF instance ID of the sender NF and the NF instance ID of the receiver NF.

In an embodiment, the NE further comprises a performing module configured to perform an operation on the identified message.

In another aspect of the disclosure, there is provided a computer program product comprising instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any one of the first, second, third, or fourth aspects.

In another aspect of the disclosure, there is provided a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any one of the first, second, third, or fourth aspects.

Embodiments herein may provide many advantages, of which a non-exhaustive list of examples follows. In some embodiments herein, it is proposed a new mechanism to allow traffic probing between two specified network functions for example in 5GC Service Based Architecture. The embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description.

DETAILED DESCRIPTION

As used herein, the term “network” refers to a network following any suitable communication standards such as new radio (NR), long term evolution (LTE), LTE-Advanced, wideband code division multiple access (WCDMA), high-speed packet access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Address (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency-Division Multiple Access (OFDMA), Single carrier frequency division multiple access (SC-FDMA) and other wireless networks. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), etc. UTRA includes WCDMA and other variants of CDMA. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, Ad-hoc network, wireless sensor network, etc. In the following description, the terms “network” and “system” can be used interchangeably. Furthermore, the communications between two devices in the network may be performed according to any suitable communication protocols, including, but not limited to, the communication protocols as defined by a standard organization such as 3GPP. For example, the communication protocols may comprise the first generation (1G), 2G, 3G, 4G,4.5G, 5G communication protocols, and/or any other protocols either currently known or to be developed in the future.

The term “network function” refers to any suitable network function (NF) which can be implemented in a network node (physical or virtual) of a communication network. For example, the network function can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g. on a cloud infrastructure. For example, the 5G system (5GS) may comprise a plurality of NFs such as 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 Exposure Function), UPF (User plane Function) and NRF (Network Repository Function), RAN (radio access network), SCP (service communication proxy), NWDAF (network data analytics function), NSSF (Network Slice Selection Function), NSSAAF (Network Slice-Specific Authentication and Authorization Function), etc. For example, the 4G system (such as LTE) may include MME (Mobile Management Entity), HSS (home subscriber server), Policy and Charging Rules Function (PCRF), Packet Data Network Gateway (PGW), PGW control plane (PGW-C), Serving gateway (SGW), SGW control plane (SGW-C), E-UTRAN Node B (eNB), etc. In other embodiments, the network function may comprise different types of NFs for example depending on a specific network.

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 “only A, only B, or both A and B.” The phrase “A and/or B” should be understood to mean “only A, only B, or both A and B”.

It is noted that these terms as used in this document are used only for ease of description and differentiation among nodes, devices or networks etc. With the development of the technology, other terms with the similar/same meanings may also be used.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a communication system complied with the exemplary system architecture illustrated inFIGS.6-7. For simplicity, the system architectures ofFIG.6-7only depict some exemplary elements. In practice, a communication system may further include any additional elements suitable to support communication between terminal devices or between a wireless device and another communication device, such as 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 devices' access to and/or use of the services provided by, or via, the communication system.

FIG.6schematically shows a roaming 5G system architecture according to an embodiment of the present disclosure. The architecture ofFIG.6is same as FIG. 4.2.4-1 as described in 3GPP TS 23.501 V17.1.1, the disclosure of which is incorporated by reference herein in its entirety. The system architecture ofFIG.6may comprise some exemplary elements such as AUSF, AMF, DN (data network), NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R)AN, SCP (Service Communication Proxy), NSACF (Network Slice Admission Control Function), vSEPP (visited Security Edge Protection Proxy), hSEPP (home Security Edge Protection Proxy), etc.

In accordance with an exemplary embodiment, the UE can establish a signaling connection with the AMF over the reference point N1, as illustrated inFIG.6. This signaling connection may enable NAS (Non-access stratum) signaling exchange between the UE and the core network, comprising a signaling connection between the UE and the (R)AN and the N2connection for this UE between the (R)AN and the AMF. The (R)AN can communicate with the UPF over the reference point N3. The UE can establish a protocol data unit (PDU) session to the DN (data network, e.g. an operator network or Internet) through the UPF over the reference point N6.

As further illustrated inFIG.6, the exemplary system architecture also contains the service-based interfaces such as Nnrf, Nnef, Nausf, Nudm, Npcf, Namf, Nnsacf and Nsmf exhibited by NFs such as the NRF, the NEF, the AUSF, the UDM, the PCF, the AMF, the NSACF and the SMF. In addition,FIG.3also shows some reference points such as N1, N2, N3, N4, N6, N32and N9, which can support the interactions between NF services in the NFs. For example, these reference points may be realized through corresponding NF service-based interfaces and by specifying some NF service consumers and providers as well as their interactions in order to perform a particular system procedure.

FIG.7shows communication models for NF/NF services interaction according to an embodiment of the present disclosure. Table 1 summarizes the communication models, their usage and how they relate to the usage of an SCP.

TABLE 1Communication models for NF/NF services interaction summaryCommunicationbetweenCommuni-consumer andService discovery andcationproducerrequest routingmodelDirectNo NRF or SCP; direct routingAcommunicationDiscovery using NRF services;Bno SCP; direct routingIndirectDiscovery using NRF services;Ccommunicationselection for specific instancefrom the Set can be delegatedto SCP. Routing via SCPDiscovery and associated selectionDdelegated to an SCP using discoveryand selection parameters in servicerequest; routing via SCP

Model A—Direct communication without NRF interaction: Neither NRF nor SCP are used. Consumers are configured with producers' “NF profiles” and directly communicate with a producer of their choice.

Model B—Direct communication with NRF interaction: Consumers do discovery by querying the NRF. Based on the discovery result, the consumer does the selection. The consumer sends the request to the selected producer.

Model C—Indirect communication without delegated discovery: Consumers do discovery by querying the NRF. Based on discovery result, the consumer does the selection of an NF Set or a specific NF instance of NF set. The consumer sends the request to the SCP containing the address of the selected service producer pointing to an NF service instance or a set of NF service instances. In the latter case, the SCP selects an NF Service instance. If possible, the SCP interacts with NRF to get selection parameters such as location, capacity, etc. The SCP routes the request to the selected NF service producer instance.

Model D—Indirect communication with delegated discovery: Consumers do not do any discovery or selection. The consumer adds any necessary discovery and selection parameters required to find a suitable producer to the service request. The SCP uses the request address and the discovery and selection parameters in the request message to route the request to a suitable producer instance. The SCP can perform discovery with an NRF and obtain a discovery result.

FIG.8shows a flowchart of a method according to an embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a sender network function (NF) or communicatively coupled to the sender NF. As such, the apparatus may provide means or modules for accomplishing various parts of the method800as well as means or modules for accomplishing other processes in conjunction with other components.

In an embodiment, the method800may be implemented in Model A—Direct communication without NRF interaction or Model B—Direct communication with NRF interaction or Model C—Indirect communication without delegated discovery as shown inFIG.7.

At block802, the sender NF may send a first message to a receiver NF. The first message comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF. The sender NF may be any suitable network device or node or entity or function. The receiver NF may be any suitable network device or node or entity or function.

In an embodiment, the first message comprises a new Hyper Text Transfer Protocol (HTTP) header which comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF.

In an embodiment, the sender NF is an NF service consumer or an NF service producer, e.g., as shown inFIG.7.

In an embodiment, the receiver NF is an NF service producer or an NF service consumer, e.g., as shown inFIG.7.

For example, the sender NF may be an NF service consumer and the receiver NF may be an NF service producer. Alternatively, the sender NF may be an NF service producer and the receiver NF may be an NF service consumer.

In an embodiment, the sender NF is an HTTP client and the receiver NF is an HTTP server.

In an embodiment, the sender NF is an HTTP server and the receiver NF is an HTTP client.

The first message may be any suitable message which is required to be exchanged between the sender NF and the receiver NF.

In an embodiment, the first message is an HTTP message such as HTTP/1.1 (Hypertext Transfer Protocol Version 1.1) message or HTTP/2 (Hypertext Transfer Protocol Version 2) message.

In an embodiment, the first message is a service request message or a notification request message. For example, the first message may be a subscribe request as shown inFIG.7. The first message may be a request message or a subscribe request message or a notify message as shown inFIGS.1-5.

The NF instance refers to an identifiable instance of the NF. In an embodiment, the NF instance ID of the sender NF is comprised in a message body or an existing Hyper Text Transfer Protocol (HTTP) header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the receiver NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

As a first example, the NF instance ID of the sender NF may be comprised in a message body. The NF instance ID of the receiver NF may be comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

As a second example, the NF instance ID of the sender NF may be comprised in an existing HTTP header. The NF instance ID of the receiver NF may be comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

As a third example, the NF instance ID of the sender NF may be comprised in a new HTTP header. The NF instance ID of the receiver NF may be comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

As a fourth example, the NF instance ID of the sender NF may be comprised in an HTTP/2 frame. The NF instance ID of the receiver NF may be comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the sender NF and the NF instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF. For example, an NF between the sender NF and the receiver NF may identify the message exchanged between the sender NF and the receiver NF based on the NF instance ID of the sender NF and the NF instance ID of the receiver NF.

In an embodiment, the first message further comprises an NF service instance ID of the sender NF and an NF service instance ID of the receiver NF. The NF service instance refers to an identifiable instance of the NF service.

In an embodiment, the NF service instance ID of the sender NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF service instance ID of the receiver NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

As a first example, the NF service instance ID of the sender NF may be comprised in a message body. The NF service instance ID of the receiver NF may be comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

As a second example, the NF service instance ID of the sender NF may be comprised in an existing HTTP header. The NF service instance ID of the receiver NF may be comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

As a third example, the NF service instance ID of the sender NF may be comprised in a new HTTP header. The NF service instance ID of the receiver NF may be comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

As a fourth example, the NF service instance ID of the sender NF may be comprised in an HTTP/2 frame. The NF service instance ID of the receiver NF may be comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the sender NF, the NF instance ID of the receiver NF, the NF service instance ID of the sender NF and the NF service instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF. For example, an NF between the sender NF and the receiver NF may identify the message exchanged between the sender NF and the receiver NF based on the NF instance ID of the sender NF, the NF instance ID of the receiver NF, the NF service instance ID of the sender NF and the NF service instance ID of the receiver NF.

FIG.9shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a sender network function (NF) or communicatively coupled to the sender NF. As such, the apparatus may provide means or modules for accomplishing various parts of the method900as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

In an embodiment, the method900may be implemented in Model A—Direct communication without NRF interaction or Model B—Direct communication with NRF interaction or Model C—Indirect communication without delegated discovery as shown inFIG.7.

At block902, the sender NF may receive a second message from the receiver NF. The second message comprises the NF instance ID of the sender NF and the NF instance ID of the receiver NF. For example the second message may be a response for the first message. Alternatively, the second message may be any other suitable message.

The second message may be any suitable message which is required to be exchanged between the sender NF and the receiver NF.

In an embodiment, the second message is an HTTP message.

In an embodiment, the second message is a service response message or a notification response message.

In an embodiment, the NF instance ID of the sender NF is comprised in a message body or an existing Hyper Text Transfer Protocol (HTTP) header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the receiver NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the sender NF and the NF instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

In an embodiment, the second message further comprises an NF service instance ID of the sender NF and an NF service instance ID of the receiver NF. The NF service instance refers to an identifiable instance of the NF service.

In an embodiment, the NF service instance ID of the sender NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF service instance ID of the receiver NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the sender NF, the NF instance ID of the receiver NF, the NF service instance ID of the sender NF and the NF service instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

In an embodiment, the first message and second message further comprise an NF set ID of the sender NF and an NF set ID of the receiver NF. NF Set refers to a group of interchangeable NF instances of the same type, supporting the same services and the same Network Slice(s). The NF instances in the same NF Set may be geographically distributed but have access to the same context data.

In an embodiment, the NF instance ID of the sender NF, the NF instance ID of the receiver NF, the NF service instance ID of the sender NF, the NF service instance ID of the receiver NF, the NF set ID of the sender NF and the NF set ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

FIG.10shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a receiver NF or communicatively coupled to the receiver NF. As such, the apparatus may provide means or modules for accomplishing various parts of the method1000as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

In an embodiment, the method1000may be implemented in Model A—Direct communication without NRF interaction or Model B—Direct communication with NRF interaction or Model C—Indirect communication without delegated discovery as shown inFIG.7.

At block1002, the receiver NF may receive a first message from a sender NF. The first message comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF.

In an embodiment, the first message comprises a new HTTP header which comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF.

For example, the sender NF may send the first message to the receiver NF at block802ofFIG.8, and then the receiver NF may receive the first message from the sender NF. Depending on the specific type of the first message, the receiver NF may perform any suitable processing on the first message and the present disclosure has no limit on it.

In an embodiment, the NF instance ID of the sender NF is comprised in a message body or an existing Hyper Text Transfer Protocol (HTTP) header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the receiver NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the sender NF and the NF instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

In an embodiment, the first message further comprises an NF service instance ID of the sender NF and an NF service instance ID of the receiver NF.

In an embodiment, the NF service instance ID of the sender NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF service instance ID of the receiver NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the sender NF, the NF instance ID of the receiver NF, the NF service instance ID of the sender NF and the NF service instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

In an embodiment, the first message is an HTTP message.

In an embodiment, the first message is a service request message or a notification request message.

FIG.11shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a receiver NF or communicatively coupled to the receiver NF. As such, the apparatus may provide means or modules for accomplishing various parts of the method1100as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

In an embodiment, the method1200may be implemented in Model A—Direct communication without NRF interaction or Model B—Direct communication with NRF interaction or Model C—Indirect communication without delegated discovery as shown inFIG.7.

At block1102, the receiver NF may send a second message to the sender NF. The second message comprises the NF instance ID of the sender NF and the NF instance ID of the receiver NF. The second message may be a response for the first message. Alternatively, the second message may be any other suitable message. For example when the receiver NF receives the first message, it may send the second message as a response for the first message to the sender NF and then the sender NF may receive the second message from the receiver NF. Alternatively, the receiver NF may send the second message to the sender NF due to other reasons. For example, the sender NF may be an notification endpoint of a subscription event. The receiver NF may send the second message comprising the subscription event to the sender NF and then the sender NF may receive the second message from the receiver NF. Alternatively, the receiver NF may send the second message as a service request to the sender NF.

The second message may be any suitable message which is required to be exchanged between the sender NF and the receiver NF.

In an embodiment, the second message is an HTTP message.

In an embodiment, the second message is a service response message or a notification response message.

In an embodiment, the NF instance ID of the sender NF is comprised in a message body or an existing Hyper Text Transfer Protocol (HTTP) header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the receiver NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the sender NF and the NF instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

In an embodiment, the second message further comprises an NF service instance ID of the sender NF and an NF service instance ID of the receiver NF. The NF service instance refers to an identifiable instance of the NF service.

In an embodiment, the NF service instance ID of the sender NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF service instance ID of the receiver NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the sender NF, the NF instance ID of the receiver NF, the NF service instance ID of the sender NF and the NF service instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

In an embodiment, the first message and second message further comprise an NF set ID of the sender NF and an NF set ID of the receiver NF. NF Set refers to a group of interchangeable NF instances of the same type, supporting the same services and the same Network Slice(s). The NF instances in the same NF Set may be geographically distributed but have access to the same context data.

In an embodiment, the NF instance ID of the sender NF, the NF instance ID of the receiver NF, the NF service instance ID of the sender NF, the NF service instance ID of the receiver NF, the NF set ID of the sender NF and the NF set ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

FIG.12shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as an SCP or communicatively coupled to the SCP. As such, the apparatus may provide means or modules for accomplishing various parts of the method1200as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

In an embodiment, the method1200may be implemented in Model C—Indirect communication without delegated discovery as shown inFIG.7.

At block1202, the SCP may receive a third message from a sender NF or a receiver NF. The third message comprises an NF instance ID of the sender NF and an NF instance ID of the receiver NF. For example, the sender may send the first message to the receiver NF via SCP at block802ofFIG.8. In this case the third message is the first message. The sender may send the second message from the receiver NF via SCP at block902ofFIG.9. In this case the third message is the second message.

In an embodiment, the third message comprises a new HTTP header which comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF.

At block1204, the SCP may send a fourth message to the receiver NF or the sender NF. The fourth message comprises the NF instance ID of the sender NF and the NF instance ID of the receiver NF. For example, as shown in Model C—Indirect communication without delegated discovery ofFIG.7, when the SCP receives the third message from the sender NF, it may send a fourth message to the receiver NF. When the SCP receive the third message from the receiver NF, it may send a fourth message to the sender NF.

In an embodiment, the fourth message comprises the new HTTP header which comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF.

In an embodiment, the NF instance ID of the sender NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the receiver NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the sender NF and the NF instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

In an embodiment, the third message and the fourth message further comprise an NF service instance ID of the sender NF and an NF service instance ID of the receiver NF.

In an embodiment, the NF service instance ID of the sender NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF service instance ID of the receiver NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the sender NF, the NF instance ID of the receiver NF, the NF service instance ID of the sender NF and the NF service instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

In an embodiment, the third message and the fourth message are HTTP messages.

In an embodiment, the third message and the fourth message comprise at least one of a service request message, a notification request message, a service response message, or a notification response message.

In an embodiment, the sender NF is an NF service consumer or an NF service producer.

In an embodiment, the receiver NF is NF service consumer or an NF service producer.

In an embodiment, the sender NF is an HTTP client and the receiver NF is an HTTP server.

In an embodiment, the third message and the fourth message further comprise an NF set ID of the sender NF and an NF set ID of the receiver NF.

FIG.13shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as an sender NF or communicatively coupled to the sender NF. As such. the apparatus may provide means or modules for accomplishing various parts of the method1300as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

In an embodiment, the method1300may be implemented in Model D—Indirect communication with delegated discovery as shown inFIG.7.

At block1302, the sender NF may send a fifth message to a service communication proxy (SCP). The fifth message comprises an NF instance identifier (ID) of the sender NF. For example, as shown inFIG.7, the consumer (the sender NF) adds any necessary discovery and selection parameters required to find a suitable producer to the service request (e.g., the fifth message). The SCP uses the request address and the discovery and selection parameters in the request message to route the request to a suitable producer instance. The SCP can perform discovery with an NRF and obtain a discovery result.

In an embodiment, the NF instance ID of the sender NF is comprised in a message body or an existing Hyper Text Transfer Protocol (HTTP) header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the fifth message further comprises an NF service instance ID of the sender NF.

In an embodiment, the NF service instance ID of the sender NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the fifth message is an HTTP message.

In an embodiment, the fifth message is a service request message or a notification request message.

FIG.14shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as an sender NF or communicatively coupled to the sender NF. As such. the apparatus may provide means or modules for accomplishing various parts of the method1400as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

In an embodiment, the method1400may be implemented in Model D—Indirect communication with delegated discovery as shown inFIG.7.

At block1402, the sender NF may receive a sixth message from the SCP. The sixth message comprises the NF instance ID of the sender NF and an NF instance ID of a receiver NF. For example, as shown inFIG.7, the SCP may receive a response (e.g., the sixth message) from the receiver NF and send the response to the sender NF.

In an embodiment, the NF instance ID of the receiver NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the sender NF and the NF instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

In an embodiment, the sixth message further comprises the NF service instance ID of the sender NF and the NF service instance ID of the receiver NF.

In an embodiment, the NF service instance ID of the receiver NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the sender NF, the NF instance ID of the receiver NF, the NF service instance ID of the sender NF and the NF service instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

In an embodiment, the fifth message and the sixth message are HTTP messages.

In an embodiment, the sixth message comprise at least one of a service response message, or a notification response message.

In an embodiment, the sender NF is an NF service consumer or an NF service producer.

In an embodiment, the receiver NF is NF service consumer or an NF service producer.

In an embodiment, the sender NF is an HTTP client and the receiver NF is an HTTP server.

In an embodiment, the fifth message and the sixth message further comprise an NF set ID of the sender NF and an NF set ID of the receiver NF.

FIG.15shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as an SCP or communicatively coupled to the SCP. As such, the apparatus may provide means or modules for accomplishing various parts of the method1500as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

In an embodiment, the method1500may be implemented in Model D—Indirect communication with delegated discovery as shown inFIG.7.

At block1502, the SCP may receive a fifth message from a sender network function (NF). The fifth message comprises an NF instance identifier (ID) of the sender NF.

At block1504, the SCP may determine a receiver NF.

At block1506, the SCP may send a seventh message to the receiver NF. The seventh message comprises the NF instance ID of the sender NF and an NF instance ID of the receiver NF.

For example, as shown inFIG.7, the consumer (the sender NF) adds any necessary discovery and selection parameters required to find a suitable producer to the service request (e.g., the fifth message). The SCP uses the request address and the discovery and selection parameters in the request message to route the request to a suitable producer instance. The SCP can perform discovery with an NRF and obtain a discovery result. Then the SCP may send a seventh message to the receiver NF.

In an embodiment, the NF instance ID of the sender NF is comprised in a message body or an existing Hyper Text Transfer Protocol (HTTP) header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the receiver NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the sender NF and the NF instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

In an embodiment, the seventh message further comprises an NF service instance ID of the sender NF and an NF service instance ID of the receiver NF.

In an embodiment, the NF service instance ID of the sender NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF service instance ID of the receiver NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the sender NF, the NF instance ID of the receiver NF, the NF service instance ID of the sender NF and the NF service instance ID of the receiver NF are used to identify a message exchanged between the sender NF and the receiver NF.

In an embodiment, the fifth message and the seventh message are HTTP messages.

In an embodiment, the fifth message and the seventh message comprise at least one of a service request message or a notification request message.

FIG.16shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as an SCP or communicatively coupled to the SCP. As such, the apparatus may provide means or modules for accomplishing various parts of the method1600as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

In an embodiment, the method1600may be implemented in Model D—Indirect communication with delegated discovery as shown inFIG.7.

At block1602, the SCP may receive an eighth message from the receiver NF. The eighth message comprises the NF instance ID of the sender NF and an NF instance ID of the receiver NF. The eighth message may be a response for the seventh message. Alternatively, the eighth message may be any other suitable message such as a notification request message or a service request. For example when the receiver NF receives the seventh message, it may send the eighth message as a response for the seventh message to the SCP and then the SCP may receive the eighth message from the receiver NF. Alternatively, the receiver NF may send the eighth message to the SCP due to other reasons. For example, the sender NF may be an notification endpoint of a subscription event. The receiver NF may send the eighth message comprising the subscription event to the SCP and then the SCP may receive the eighth message from the receiver NF. Alternatively, the receiver NF may send the eighth message as a service request to the SCP.

At block1604, the SCP may send a sixth message to the sender NF. The sixth message comprises the NF instance ID of the sender NF and an NF instance ID of a receiver NF.

In an embodiment, the eighth message and the sixth message further comprise the NF service instance ID of the sender NF and the NF service instance ID of the receiver NF.

In an embodiment, the eighth message and the sixth message are HTTP messages.

In an embodiment, the eighth message and the sixth message comprise at least one of a service response message, or a notification response message.

In an embodiment, the sender NF is an NF service consumer or an NF service producer.

In an embodiment, the receiver NF is NF service consumer or an NF service producer.

In an embodiment, the sender NF is an HTTP client and the receiver NF is an HTTP server.

In an embodiment, the fifth message, the sixth message, the seventh message and the eighth message further comprise an NF set ID of the sender NF and an NF set ID of the receiver NF.

FIG.17shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as an NE (network entity) or communicatively coupled to the NE. As such, the apparatus may provide means or modules for accomplishing various parts of the method1700as well as means or modules for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity. The NE may be any suitable entity. For example, the NE may be entity which requires to perform traffic probing. For example, the NE may be a sender NF or a receiver NF or an entity between the sender NF and the receiver NF.

At block1702, the NE may send or receive a message exchanged between a sender NF and a receiver NF. The message comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF.

In an embodiment, the message comprises a new HTTP header which comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF.

At block1704, the NE may identify the message exchanged between the sender NF and the receiver NF based on the NF instance ID of the sender NF and the NF instance ID of the receiver NF.

In an embodiment, the NF instance ID of the sender NF is comprised in a message body or an existing Hyper Text Transfer Protocol (HTTP) header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF instance ID of the receiver NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the message further comprises an NF service instance ID of the sender NF and an NF service instance ID of the receiver NF.

In an embodiment, the NF service instance ID of the sender NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the NF service instance ID of the receiver NF is comprised in a message body or an existing HTTP header or a new HTTP header or an HTTP/2 frame.

In an embodiment, the message exchanged between the sender NF and the receiver NF is identified further based on the NF service instance ID of the sender NF and the NF service instance ID of the receiver NF.

In an embodiment, the message is an HTTP message.

In an embodiment, the message is a service request message or a notification request message or a service response message or a notification response message.

In an embodiment, the sender NF is an HTTP client and the receiver NF is an HTTP server.

In an embodiment, the message further comprises an NF set ID of the sender NF and an NF set ID of the receiver NF.

At block1706, optionally, the NE may perform an operation on the identified message. The operation may be any suitable operation. In an embodiment, the operation comprises at least one of monitoring traffic, filtering traffic, applying policy, troubleshooting, or performance measurement.

FIG.18ashows a flowchart of NF interaction mechanisms according to an embodiment of the present disclosure. Network Functions (e.g., NF1, NF2 and NF3) are configured to carry the new HTTP header indicating the sender NF instance ID and receiver NF instance ID in each service request/response. An intermediary (any NF) serving for traffic filtering can be configured to filter the traffic between two certain NFs, e.g., traffic between NF1 and NF2 in the example. According to the information carried in the new HTTP header, the intermediary filters the traffic matching the configuration, e.g., forking the traffic to a configured destination, and discards any unmatching traffic.

In an embodiment, the following information may be added into Table 5.2.3.3-1 of 3GPP TS 29.500 V17.3.0, the disclosure of which is incorporated by reference herein in its entirety.

In an embodiment, the following information may be added into 3GPP TS 29.500 V17.3.0.

This header contains the IDs of the NF (service) instance as HTTP client and the NF (service) instance as HTTP server.
The encoding of the header follows the ABNF as defined in IETF RFC 7230 [12].
3gpp-Sbi-NF-Peer-Info=“3gpp-Sbi-NF-Peer-Info” “:” OWS “srcinst=” nfInstanceIdvalue [OWS “;” “srcservinst=” nfServiceInstanceIdvalue] OWS “dstcinst=” nfInstanceIdvalue [OWS “;” “dstservinst=” nfServiceInstanceIdvalue]
The following parameters are defined:srcinst (Source NF instance): indicates the Source NF Instance ID, as defined in 3GPP TS 29.510 [8];srcservinst (Source NF service instance): indicates the Source NF Service Instance ID, as defined in 3GPP TS 29.510 [8];dstinst (Destination NF instance): indicates the Destination NF Instance ID, as defined in 3GPP TS 29.510 [8];dstservinst (Destination NF service instance): indicates the Destination NF Service Instance ID, as defined in 3GPP TS 29.510 [8];EXAMPLE: 3gpp-Sbi-NF-Peer-Info: srcinst=54804518-4191-46b3-955c-ac631f953ed8; dstinst=54804518-4191-4453-569c-ac631f74765cd

In an embodiment, the following information may be added into 3GPP TS 29.500 V17.3.0.

6.13.x SBI Messages Correlation Using NF Peer Information

The procedure enables network analytics tools or probes, to easily identify messages that were exchanged between a specified pair of NF (Service) instances. When supported and configured to be used by operator's policy, an NF as HTTP client or NF as HTTP server may include the NF (Service) instance IDs in 3gpp-Sbi-NF-Peer-Info header, to identify the HTTP requests or responses between the given pair of NF (Service) instances, as further defined in clause 6.13.x.2.

An HTTP client originating a request may include in the request the 3gpp-Sbi-NF-Peer-Info header containing the Source NF (Service) instance II) and the Destination NF (Service) instance ID).
Upon receipt of a request that includes the 3gpp-Shi-NF-Peer-Info, the HTTP server, if it supports this header, should include the header in the response sent to the HTTP client, with the same value that was contained in the 3gpp-Sbi-NF-Peer-Info header of the received HTTP request. The HTTP server may include the 3gpp-Sbi-NF-Peer-Info header in a response even when the header is not included in the request received from the HTTP client.
When forwarding a request or response that includes the 3gpp-Sbi-NF-Peer-Info header, the SCP should forward this header unmodified. In an inter-PLMN scenario, the SEPP may remove the header based on operator policies.

According to various embodiments, various messages described above such as the first message, the second message, the third message, the fourth message, the fifth message, the sixth message, the seventh message and/or the eighth message may further compirse any other suitable information (such as NF Service Set ID and/or Service name, etc.) which can be used to identify a message exchanged between a sender NF and a receiver NF.

FIG.18bis a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure. For example, any one of the sender NF, the receiver NF, the SCP, or the NE described above may be implemented as or through the apparatus1800.

The apparatus1800comprises at least one processor1821, such as a digital processor (DP), and at least one memory (MEM)1822coupled to the processor1821. The apparatus1800may further comprise a transmitter TX and receiver RX1823coupled to the processor1821. The MEM1822stores a program (PROG)1824. The PROG1824may include instructions that, when executed on the associated processor1821, enable the apparatus1800to operate in accordance with the embodiments of the present disclosure. A combination of the at least one processor1821and the at least one MEM1822may form processing means1825adapted to implement various embodiments of the present disclosure.

Various embodiments of the present disclosure may be implemented by computer program executable by one or more of the processor1821, software, firmware, hardware or in a combination thereof.

The MEM1822may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memories and removable memories, as non-limiting examples.

The processor1821may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.

In an embodiment where the apparatus is implemented as or at the sender NF, the memory1822contains instructions executable by the processor1821, whereby the sender NF operates according to any of the methods related to the sender NF as described above.

In an embodiment where the apparatus is implemented as or at the receiver NF, the memory1822contains instructions executable by the processor1821, whereby the receiver NF operates according to any of the methods related to the receiver NF as described above.

In an embodiment where the apparatus is implemented as or at the SCP, the memory1822contains instructions executable by the processor1821, whereby the SCP operates according to any of the methods related to the SCP as described above.

In an embodiment where the apparatus is implemented as or at the NE, the memory1822contains instructions executable by the processor1821, whereby the NE operates according to any of the methods related to the NE as described above.

FIG.19is a block diagram showing a sender NF according to an embodiment of the disclosure. As shown, the sender NF1900comprises a sending module1901configured to send a first message to a receiver NF. The first message comprises a new HTTP header which comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF.

In an embodiment, the sender NF1900further comprises a receiving module1902configured to receive a second message from the receiver NF. The second message comprises the NF instance ID of the sender NF and the NF instance ID of the receiver NF.

FIG.20is a block diagram showing a receiver NF according to an embodiment of the disclosure. As shown, the receiver NF2000comprises a receiving module2001configured to receive a first message from a sender NF. The first message comprises a new HTTP header which comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF.

In an embodiment, the receiver NF2000further comprises a sending module2002configured to send a second message to the sender NF. The second message comprises the NF instance ID of the sender NF and the NF instance ID of the receiver NF.

FIG.21is a block diagram showing a SCP according to an embodiment of the disclosure. As shown, the SCP2100comprises a receiving module2101configured to receive a third message from a sender network function (NF) or a receiver NF. The third message comprises a new HTTP header which comprises an NF instance ID of the sender NF and an NF instance ID of the receiver NF. The SCP further comprises a sending module2102configured to send a fourth message to the receiver NF or the sender NF, wherein the fourth message comprises a new HTTP header which comprises the NF instance ID of the sender NF and the NF instance ID of the receiver NF.

FIG.22is a block diagram showing a sender NF according to another embodiment of the disclosure. As shown, the sender NF2200comprises a sending module2201configured to send a fifth message to a service communication proxy (SCP). The fifth message comprises an NF instance identifier (ID) of the sender NF.

In an embodiment, the sender NF2200further comprises a receiving module2202configured to receive a sixth message from the SCP. The sixth message comprises the NF instance ID of the sender NF and an NF instance ID of a receiver NF.

FIG.23is a block diagram showing a SCP according to another embodiment of the disclosure. As shown, the SCP2300comprises a first receiving module2301configured to receive a fifth message from a sender network function (NF). The fifth message comprises an NF instance identifier (ID) of the sender NF. The SCP2300further comprises a determining module2302configured to determine a receiver NF. The SCP2300further comprises a first sending module2303configured to send a seventh message to the receiver NF. The seventh message comprises the NF instance ID of the sender NF and an NF instance ID of the receiver NF.

In an embodiment, the SCP2300further comprises a second receiving module2304configured to receive an eighth message from the receiver NF. The eighth message comprises the NF instance ID of the sender NF and an NF instance ID of the receiver NF.

In an embodiment, the SCP2300further comprises a second sending module2305configured to send a sixth message to the sender NF. The sixth message comprises the NF instance ID of the sender NF and an NF instance ID of a receiver NF.

FIG.24is a block diagram showing an NE according to an embodiment of the disclosure. As shown, the NE2400comprises a sending or receiving module2401configured to send or receive a message exchanged between a sender NF and a receiver NF. The message comprises a new HTTP header which comprises an NF instance identifier (ID) of the sender NF and an NF instance ID of the receiver NF. The NE2400further comprises an identifying module2402configured to identify the message exchanged between the sender NF and the receiver NF based on the NF instance ID of the sender NF and the NF instance ID of the receiver NF.

In an embodiment, the NE2400further comprises a performing module2403configured to perform an operation on the identified message.

Embodiments herein may provide many advantages, of which a non-exhaustive list of examples follows. In some embodiments herein, it is proposed a new mechanism to allow traffic probing between two specified network functions for example in 5GC Service Based Architecture. The embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description.

With function units, the sender NF, the receiver NF, the SCP, or the NE may not need a fixed processor or memory, any computing resource and storage resource may be arranged from the sender NF, the receiver NF, the SCP, or the NE in the communication system. The introduction of virtualization technology and network computing technology may improve the usage efficiency of the network resources and the flexibility of the network.

According to an aspect of the disclosure it is provided a computer program product being tangibly stored on a computer readable storage medium and including instructions which, when executed on at least one processor, cause the at least one processor to carry out any of the methods as described above.

According to an aspect of the disclosure it is provided a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to carry out any of the methods as described above.

In addition, the present disclosure may also provide a carrier containing the computer program as mentioned above, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium. The computer readable storage medium can be, for example, an optical compact disk or an electronic memory device like a RAM (random access memory), a ROM (read only memory), Flash memory, magnetic tape, CD-ROM, DVD, Blue-ray disc and the like.