Provision of services that facilitate analysis of network functional behavior

Abstract

Example embodiments of the present disclosure relate to devices, methods, and computer-readable storage media for facilitating analysis of services from a network function (NF) for service provision. In an example embodiment, one or more logs are received from at least one of a first NF, a network repository function (NRF), and a service communication agent (SCP). One or more logs are associated with a service from a second NF. In addition, the provision of services from the second NF is facilitated based on the one or more logs.

Description

Technical Field

[0001] Example embodiments of the present disclosure relate generally to the field of communications, and in particular to an apparatus, method, and computer-readable storage medium for service provisioning to facilitate analysis of services from a network function (NF). Background Art

[0002] The service-based architecture in the 3rd Generation Partnership Project (3GPP) relies on the consumer-producer paradigm. The key function of the service-based architecture is the network repository function (NRF), which provides registration, discovery and authorization for services from network functions (NFs) so that NFs can identify services from each other. For example, after a NF as a service consumer discovers a group of services from a NF as a service producer via NRF, the consumer can select services from the producer and request an access token for the selected service from the NRF. The NRF can authorize the consumer and generate an access token to allow the consumer to request the producer's service. In addition, the consumer can use the access token to access the service from the producer directly or indirectly via a service communication proxy (SCP). However, there is no mechanism available to track the activities of the consumer, producer and / or NRF. Summary of the invention

[0003] Generally speaking, example embodiments of the present disclosure provide apparatus, methods, and computer-readable storage media for service provisioning to facilitate analysis of services from network functions (NFs).

[0004] In a first aspect, a device is provided, comprising at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to receive one or more logs from at least one of a first network function, a network repository function, and a service communication agent. The one or more logs are associated with a service from a second network function. The device is also caused to facilitate analysis of provisioning of services from the second network function based on the one or more logs.

[0005] In a second aspect, a device is provided at a first network function, comprising at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the device to send at least one of a request for an access token to access a service from a second network function or a request for a service. The device is also caused to generate a log to facilitate analysis of provisioning of the service from the second network function. The log is associated with the service from the second network function.

[0006] In a third aspect, a device is provided at a service communication agent, comprising at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the device to receive a request for a service from a second network function from a first network function. The device is also caused to generate a log to facilitate analysis of the provision of the service from the second network function. The log is associated with the service from the second network function.

[0007] In a fourth aspect, a device is provided at a network repository function, comprising at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to receive a request for an access token from one of a first network function and a service communication agent, the access token to be used by the first network function to access a service from a second network function. The device is caused to send the access token to one of the first network function and the service communication agent. In addition, the device is caused to generate a log to facilitate analysis of the provision of services from the second network function. The log is associated with the service from the second network function.

[0008] In a fifth aspect, a method is provided. In the method, one or more logs are received from at least one of a first network function, a network repository function, and a service communication agent. The one or more logs are associated with a service from a second network function. In addition, analysis of provisioning of the service from the second network function is facilitated based on the one or more logs.

[0009] In a sixth aspect, a method implemented at a first network function is provided. In the method, at least one of a request for an access token to access a service from a second network function or a request for a service is sent. In addition, a log is generated to facilitate analysis of provisioning of the service from the second network function. The log is associated with the service from the second network function.

[0010] In a seventh aspect, a method implemented at a service communication agent is provided. In the method, a request for a service from a second network function is received from a first network function. In addition, a log is generated to facilitate analysis of the provision of the service from the second network function. The log is associated with the service from the second network function.

[0011] In an eighth aspect, a method implemented at a network repository function is provided. In the method, a request for an access token is received from one of a first network function and a service communication agent, the access token to be used by the first network function to access a service from a second network function. The access token is sent to the one of the first network function and the service communication agent. In addition, a log is generated to facilitate analysis of provisioning of the service from the second network function. The log is associated with the service from the second network function.

[0012] In a ninth aspect, there is provided an apparatus comprising means for performing the method according to the fifth, sixth, seventh or eighth aspect.

[0013] In a tenth aspect, a computer-readable storage medium is provided, comprising program instructions stored thereon, wherein when the instructions are executed by a processor of a device, the device executes the method according to the fifth, sixth, seventh or eighth aspect.

[0014] It should be understood that the invention summary is not intended to identify the key or essential features of the exemplary embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0016] FIG1( a ) illustrates a flow chart of an example process for a NF to obtain an access token from an NRF;

[0017] FIG1( b ) illustrates a flow chart of an example process of one NF accessing a service from another NF;

[0018] Figure 2(a)-Figure 2(d) illustrates an example communication model between NFs;

[0019] Figure 3 illustrates an example environment in which example embodiments of the present disclosure may be implemented;

[0020] Figure 4 illustrates a flow chart of an example method according to some example embodiments of the present disclosure;

[0021] Figure 5 illustrates a flow chart of an example method according to some example embodiments of the present disclosure;

[0022] Figure 6 illustrates a flow chart of an example method according to some example embodiments of the present disclosure;

[0023] Figure 7 a flowchart illustrating an example method according to some example embodiments of the present disclosure; and

[0024] Figure 8 A simplified block diagram of an apparatus suitable for implementing an example embodiment of the present disclosure is illustrated.

[0025] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0026] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these example embodiments are described only for illustrative purposes and to help those skilled in the art understand and implement the present disclosure without implying any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various ways different from the way described below.

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

[0028] As used herein, the term "network function" or "NF" refers to a physical, virtual, or hybrid function or entity that is deployed on the network side and provides one or more services to the client. For example, NF can be deployed at a device in an access network or a core network. NF can be implemented in hardware, software, firmware, or some combination thereof.

[0029] As used herein, the term "circuitry" may refer to one or more or all of the following:

[0030] (a) a pure hardware circuit implementation (such as an implementation of analog and / or digital circuitry only), and

[0031] (b) a combination of hardware circuitry and software, such as (where applicable): (i) a combination of analog and / or digital hardware circuitry and software / firmware, and (ii) any portion of hardware processor(s) and software (including digital signal processor(s), software and memory(s) that work together to enable a device such as a mobile phone or server to perform various functions), and

[0032] (c) Hardware circuit(s) and / or processor(s) that require software (e.g., firmware) to operate, such as microprocessor(s) or portion(s) of microprocessor(s), but the software may not be present when it is not required for operation.

[0033] This definition of circuitry applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. By way of example and where applicable to a particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular base station, or other computing or base station.

[0034] As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "including" and variations thereof should be interpreted as open terms meaning "including but not limited to". The term "based on" should be interpreted as "based at least in part on". The terms "one embodiment" and "an embodiment" should be interpreted as "at least one embodiment". The term "another embodiment" should be interpreted as "at least one other embodiment". Other definitions, whether explicit or implicit, may be included below.

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

[0036] In a service-based architecture in 3GPP, if a NF intends to access a service from another NF, the NF may request an access token from the NRF and further use the access token to request a service from the other NF. An example service access process based on token authentication will be discussed below with reference to FIG. 1(a) and FIG. 1(b).

[0037] FIG. 1( a ) shows a flow of an example process 100 in which the NF 105 obtains an access token from the NRF 110 .

[0038] In the process 100 as shown in FIG. 1( a), the NF 105 sends (115) a request for an access token to the NRF 120, which the NF 105 will use to access a service from another NF (not shown). For example, the request may be a Nnrf_AccessToken_Get request, as defined in the 3GPP specification. The request may include one or more expected service names, NF types of the NF 105 and / or another NF, client identity (or ID), etc. The NRF 120 authorizes (120) the client and generates (125) an access token. The NRF 120 sends (130) the access token to the NF 105. For example, the NRF 120 may send a Nnrf_AccessToken_Get response, as defined in the 3GPP specification. The response may include the access token and other parameters, such as the expiration time of the token.

[0039] FIG. 1( b ) illustrates the flow of an example process 140 for a NF 105 to access a service from another NF 145 .

[0040] In process 140 as shown in FIG. 1( b), NF 105 sends (135) a request for a service from NF 145 to NF 145. The service request may include an access token. NF 145 verifies (155) the access token. For example, NF 145 may verify the integrity of the access token and the claims in the access token. If the verification is successful, NF 145 performs (160) the requested service. NF 145 sends (165) a response to NF 105.

[0041] Several communication models can be used for NF / NF service interaction. For example, a NF as a service consumer can communicate with a NF as a service producer directly or indirectly via a service communication proxy (SCP). Example communication models will be referred to below. Figure 2(a)-Figure 2(d) Have a discussion.

[0042] In the communication model 200 as shown in FIG2( a), NF 105 and 145 communicate directly with each other. For example, NF 105 may be configured with an NF profile of NF 145 to communicate directly with NF 145. As shown in FIG2( a), NF 105 sends (205) a service request to NF 145 and receives (210) a service response from NF 145. In addition, NF 105 sends (215) a subsequent service request to NF 145.

[0043] In the communication model 220 as shown in FIG. 2( b), NF 105 and 145 may also communicate directly with each other. Unlike the communication model 220 in FIG. 2( a), the communication model 220 involves NRF 110 for NF discovery. As shown in FIG. 2( b), before sending (205) a service request to NF 145, NF 105 queries (225) NRF 110 for NF discovery and receives (230) a NF profile from NRF. In addition, NF 105 utilizes the NF profile to communicate with NF 145.

[0044] In the communication model 235 shown in FIG. 2( c) and the communication model 240 shown in FIG. 2( d), the NF 105 does not communicate directly with the NF 145, but communicates with the NF 145 indirectly via the SCP 245. In the communication model 235 shown in the figure, after the NF 105 performs NF discovery with the NRF 110, the NF 105 sends (250) a service request to the SCP 245, and then the SCP 245 sends (255) a service request to the NF 145. After the SCP 245 receives (260) a service response from the NF 145, the SCP 245 sends (265) a service response to the NF 105. The NF 105 further sends (270) a subsequent service request to the SCP 245, and the SCP 245 sends (275) a subsequent service request to the NF 145.

[0045] Unlike communication model 235, in communication model 240, NF 105 does not perform NF discovery with NRF 110. Instead, NF 105 sends (280) a service request to SCP 245, which contains parameters required to find a suitable producer. SCP 245 uses the parameters to perform (285) NF discovery with NRF 110. Then, SCP 245 sends (290) a service request to NF 145.

[0046] As mentioned above, NRF 110 can provide access token (or authorization token) to NF 105 to allow NF 105 to access the services of NF 145, as shown in Figures 1(a) and 1(b). However, there is no available mechanism to track the activities of (multiple) NFs and / or NRFs. For example, it is impossible to analyze or determine whether a token is likely to be successfully used.

[0047] In some cases, the NF as a service producer may be malicious and not provide a service, but pre-registered for the service. In addition, the NRF has granted authorization for the service. In these cases, the NF may charge for the authorization token to access this service, but the producer may not process the service request from the NF using the authorization token. Another possible scenario is that the NF directly or indirectly via the SCP requests an access token (such as an OAuth token) from the NRF to access the services of another NF, but the consumer NF does not then use the token.

[0048] Such malicious NFs may be identifiable or observed or detected if the NF is denied service. However, the following issues may be difficult to detect:

[0049] A) Whether NRF has provided a token,

[0050] B) Whether NF uses the token provided by the producer

[0051] C) Whether the producer behaves as expected, e.g., whether the access token granted to use the producer's service ultimately allows consumption of that service, and / or

[0052] D) Whether the NF replayed a token, used invalid tokens continuously, etc.

[0053] An example embodiment of the present disclosure proposes a mechanism for analyzing the provision of services from NF. The mechanism defines security logs and services that can be used to detect malicious NFs, such as services provided by NFs that have been tampered with by malicious NFs. Through this mechanism, consumers of services from NFs, NRFs and / or SCPs provide logs associated with the service to devices to facilitate analysis of service provision. For example, a consumer or SCP can record whether it has received an access token from the NRF and whether the service from the NF is provided or rejected. The NRF can record any request from the consumer or SCP. Based on the logs, analyze the provision of services from the NF, for example, determine whether the service provision is successful.

[0054] In this way, the provision of a specific service from the NF can be tracked. For example, successful authorization on the consumer side may be correlated with the success or failure of service provision from the producer side. As a result, malicious NFs can be detected, and thus security in NF services can be improved.

[0055] Figure 3 An example environment 300 is illustrated in which example embodiments of the present disclosure may be implemented.

[0056] The environment 300, which may be part of a communication network, includes two NFs 310 and 320, which are respectively referred to as a first NF 310 and a second NF 320. The two NFs 310 and 320 may provide one or more services for access by other NFs. For example, the first NF 310 may act as a consumer of services from the second NF 320, and vice versa.

[0057] The environment 300 also includes an SCP 330 that acts as an intermediate between the two NFs 310 and 320. The first and second NFs 310 and 320 may communicate via the SCP 330. The two NFs 310 and 320 may also communicate directly with each other in a direct communication mode similar to the communication models 200 and 220 shown in FIG. 2( a) and FIG. 2( b).

[0058] In the environment 300, the NRF 340 provides NF discovery and NF profile maintenance. For example, if the first NF 310 is to access a service from the second NF 320, the first NF 310 can perform NF discovery by querying the NRF 340, which is similar to the operations in the communication models 220 and 230 shown in Figures 2 (b) and 2 (c). The first NF 310 can also send the parameters of NF discovery to the SCP 330, and then the SCP 330 performs NR discovery with the NRF 340, which is similar to the operations in the communication model 240 shown in Figure 2 (d). Specifically, the NRF 340 can provide an access token to the first NF 310 or the SCP 330 to allow the first NF 310 to access the service from the second NF 320.

[0059] It should be understood that the NF 310 or 320, SCP or NRF 340 can be implemented as any suitable physical or virtual function or entity on the network side in the communication network. The scope of the present disclosure shall not be limited in this regard.

[0060] like Figure 3 As shown in FIG. 3 , the environment 300 further includes a network data analysis function (NWDAF) 350 for collecting various data or information from the NF 310 or 320, the SCP, or the NRF 340. In some embodiments of the present disclosure, the NWDAF 350 may be supplied with one or more logs associated with the service from the NF, including, for example, an identifier of a consumer, a producer, a service, a token, an NRF, and an indication of whether the service is successfully provided, from the NF 310 or 320, the SCP, and / or the NRF 340. For example, based on the log(s), the service provision result may be analyzed to detect whether the service access is successful or failed.

[0061] It should be understood that NWDAF 350 Figure 3310 or 320, SCP, NRF 340 or other devices (not shown) may be used as such devices.

[0062] Figure 4 A flow chart of an example method 400 is illustrated according to some example embodiments of the present disclosure.

[0063] Method 400 may be implemented in a system such as Figure 3 or any other suitable device (such as NF 310 or 320, SCP 330 or NRF 340) that can collect logs to further analyze service provisioning based on the collected logs. For the purpose of discussion, reference will be made to Figure 3 The method 400 is described in a scenario where the first NF 310 accesses a service from the second NF 320. It should be understood that the method 400 is also applicable to the case where the second NF 320 accesses a service from the first NF 310.

[0064] At block 405, one or more logs associated with a service from the second NF 320 are received from at least one of the first NF 310, the SCP 330, and the NRF 340. The one or more logs may be received in any suitable manner. For example, the logs may be obtained during a token request process and / or a service request process.

[0065] In some embodiments, the one or more logs may include at least one log generated upon requesting an access token to be used by the first NF 310 to access a service from the second NF 320 from the NRF 340. For example, the first NF 310 may send a request for an access token to the NRF 340. After receiving the access token from the NRF 340, the first NF 310 and / or the NRF 340 may generate one or more logs associated with the service. The log may include an identifier of the first NF 310, an identifier of the second NF 320, an identifier of the NRF 340, an identifier of the service, a timestamp associated with the request for the access token, and / or an identifier of the access token.

[0066] As another example, after the SCP 330 receives the request for the service from the first NF 310, the request for the access token may be sent by the SCP 330 to the NRF 340. In this case, the SCP 330 and / or the NRF 340 may generate one or more logs associated with the service. Therefore, the logs may be received from the first NF 310, the SCP 330, and / or the NRF 340.

[0067] In some example embodiments, the received one or more logs may include at least one log generated upon requesting a service from the second NF 320. For example, in the case where a direct communication model is enabled between the first and second NFs 310 and 320, the first NF 310 may directly send a request for a service to the second NF 320. After receiving a response from the second NF 320, the first NF 310 may generate a log associated with the service from the second NF 320. For example, the log may include an identifier of the first NF 310, an identifier of the second NF 320, an identifier of the service, a timestamp associated with the request for the service, and / or an indication of whether the service is provided by the second network function.

[0068] The first NF 310 may also generate a log if the service provision fails due to maliciousness or other reasons of the second NF 320. For example, the log may be generated by the first NF 310 after a predetermined time period has expired after a request for a service or after other predetermined triggers.

[0069] In some example embodiments, the first NF 310 may send a request for a service together with an access token obtained in advance from the NRF 340 during the token request process. The request for a service and the access token may be sent together in any suitable manner. The access token may be included in the request for the service. The request for the service and the access token may also be sent separately. Thus, the second NF 320 may verify the access token. In these example embodiments, the log of the first NF 310 may also include the identifier of the NRF 340 and / or the validity of the access token.

[0070] If the direct communication model is not allowed between the first and second NFs 310 and 320, the first NF 310 may send a request for a service to the SCP 330, which forwards it to the second NF 320. In some example embodiments, after receiving the request for a service, the SCP 330 may first send a request for an access token to the NFR 340 and generate a corresponding log associated with the service, as described above. After receiving the access token from the NRF 340, the SCP 330 further sends the request for the service and the access token obtained from the NFR 340 to the second NF 320. Alternatively or additionally, after receiving a response from the second NF 320, the SCP 330 may generate a log associated with the service from the second NF 320.

[0071] The log may include an identifier of the first NF 310, an identifier of the second NF 320, an identifier of the service, a timestamp associated with the request for the service, the validity of an access token obtained from the NRF 340 for accessing the service, an identifier of the NRF, or an indication of whether the service is provided by the second NF 320. In some example embodiments, the SCP 330 may further record the number of requests to access the service.

[0072] In an example embodiment where the first NF 310 sends a service request together with an access token, the SCP 330 may directly forward the request for the service to the second NF 320. After receiving a response from the second NF 320, the SCP 330 may generate a log associated with the service from the second NF 320.

[0073] After the first NF 310, SCP 330 and / or NRF 340 generates logs associated with services from NF 320, the first NF 310, SCP 330 and / or NRF 340 may report (e.g., send or push) the logs to a device such as NWDAF 350 to facilitate analysis of service provision from the second NF 320.

[0074] In some example embodiments, the first NF 310, SCP 330 and / or NRF 340 may not report logs to the collection device, but store the logs locally or in a remote device, such as a shared repository or another NF, SCP and / or NRF. Alternatively or additionally, the logs may be collected by one or more of the first NF 310, SCP 330 and / or NRF 340 reporting the log collection to the collection device. The stored logs may be retrieved or pulled by the collection device when needed.

[0075] As described above, one of the first NF 310, SCP 330, and / or NRF 340 may serve as a collection device. For example, in the case where the NRF 340 serves as a collection device, the NRF 340 may receive logs from the first NF 310 and / or SCP 330, while obtaining its own logs by reading its own logs from local storage.

[0076] In some example embodiments, a new service may be provided to enable a collection device to receive one or more logs associated with a service from the second NF 320 from the first NF 310, SCP 330, and / or NRF 340. Table 1 shows an example definition of such a new service in the case where the NWDAF 350 is used for log collection.

[0077] Table 1

[0078]

[0079] In this example, as shown, the new service is named Nnwdaf_SecurityLog. Using this service, the NRF or SCP can report a log of authentication and authorization requests, such as token requests and / or service requests. This service can also enable the NWDAF to actively retrieve such logs.

[0080] After receiving one or more logs, at block 410, analysis of the provision of services from the second NF 320 is facilitated based on the logs. In some example embodiments, the analysis may be performed by a collection device. In some other example embodiments, the analysis may be performed by any other suitable device. For example, the collection device may send or report the collected logs to a dedicated analysis device, such as a dedicated NWDAF, to facilitate analysis of the service provision at the analysis device.

[0081] For example, it may be detected whether the service is successfully provided from the second NF 320. Therefore, any malicious activity from the second NF 320 may be detected. This may trigger an alarm to an operator managing the second NF 320.

[0082] The logs collected from various devices such as the first NF 310, the SCP 330, and the NRF 340 may be maintained at the collecting device in any suitable manner. An example information model for recording the logs is as follows.

[0083]

[0084] For example, as shown, the information model may include several fields such as timestamp, consumer ID, producer ID, service ID (authenticated), token ID, token validity, service ID (provided), number of requests for service access, service ID (requested), etc., which are derived from NF, NRF and / or SCP. These fields can be implemented in any suitable data type, such as timestamp, variable string (Varchar), Boolean, etc., as shown in Table 1.

[0085] The field of timestamp can record the timestamp reported by NF, NRF and / or SCP, or the time when the log is obtained from NF, NRF and / or SCP. The field of consumer ID can record the identifier (ID) of the consumer of the service from NF. The field of producer ID can record the identifier of the producer that provides the service. The field of service ID (authenticated) can record the identifier of the service that has been authenticated to the consumer. The field of token ID can record the identifier of the access token or authentication token. The field of token validity can indicate whether the access token is valid. The field of service ID (provided) can record the identifier of the service that has been provided to the consumer. The field of the number of requests for service access can record the number of requests for access to the requested service. The field of service ID (requested) can record the identifier of the service requested by the consumer.

[0086] It should be understood that the information model described above is only an example. Any suitable type of information can be collected from any one of the NF, SCP and / or NRF and recorded in a suitable information model.

[0087] Using the information or data recorded in the information model, the provision of services from the NF can be analyzed. In this way, the service provision can be tracked and detected. As a result, the NF that tampers with its service can be detected, and thus the security in the NF service can be improved.

[0088] Figure 5 1 is a flowchart of an example method 500 according to some example embodiments of the present disclosure. The method 500 may be implemented at the first NF 310 in the case where the first NF 310 requests a service from the second NF 320, or at the second NF 320 in the case where the second NF 320 requests a service from the first NF 310. For the purpose of discussion, reference will be made to Figure 3 The method 500 is described in the case where the first NF 310 is to access a service from the second NF 320.

[0089] At block 505, the first NF 310 sends at least one of a request for an access token for accessing a service from a second network function or a request for a service. For example, in a communication model similar to the communication models 220 and 235 shown in FIG. 2(b) and FIG. 2(c), the first NF 310 may send a request for an access token to the NRF 340. In a communication model similar to the communication models 200 and 220 shown in FIG. 2(a) and FIG. 2(b), the first NF 310 may send a request for a service to the second NF 320, and in the communication models 210 and 215, the first NF 310 may send a request for a service to the SCP 330.

[0090] Upon a request for an access token and / or a request for a service, at block 510, the first NF 310 generates a log associated with the service from the second NF 320. The first NF 310 may report the log to a device, such as the NWDAF 350, to facilitate analysis of the provision of the service from the second NF 320. Alternatively or additionally, the log may be stored at the first NF 320, and a collection device may retrieve or pull the log when needed.

[0091] The log may be generated by the first NF 310 during the token request process and / or the service request process. For example, after sending a request for an access token to the NRF 340, the first NF 310 may generate a log after receiving the access token from the NRF 340. The log may include any suitable information. For example, the log may include an identifier of the first NF 310, an identifier of the second NF 320, an identifier of the NRF 340, an identifier of the service, a timestamp associated with the request for the access token, and / or an identifier of the access token.

[0092] As another example, the first NF 310 may generate a log after sending a request for a service to the SCP 330 in a communication model similar to the communication model 235 or 240 shown in FIG. 2 (c) or FIG. 2 (d), or generate a log after sending a request for a service to the second NF 310 in a communication model similar to the communication model 200 or 220 shown in FIG. 2 (c) or FIG. 2 (d). In this example, the log may include an identifier of the first NF 310, an identifier of the second NF 320, an identifier of the service, a timestamp associated with the request for the service, and / or an indication of whether the service is provided by the second network function. In the case where the first NF 310 sends an access token obtained from the NRF together with the request for the service, the second NF 320 may make the access token valid. Therefore, the log may also include the validity of the access token. Alternatively or additionally, the log may include an identifier of the NRF 340.

[0093] Figure 6 600 according to some example embodiments of the present disclosure. Figure 3 For the purpose of discussion, reference will be made to SCP 330. Figure 3 The method 600 is described in a scenario where the first NF 310 wants to access a service from the second NF 320 .

[0094] At block 605, the SCP 330 receives a request for a service from the second NF 320 from the first NF 310. For example, the SCP 330 may receive a request for a service from the first NF 310 in a communication model similar to the communication model 235 or 240 shown in FIG. 2(c) or FIG. 2(d).

[0095] Upon receiving the request for the service, at block 610, the SCP 330 generates a log associated with the service from the second NF 320 for use by a device such as the NWDAF 350 to facilitate analysis of the provision of the service from the second NF 320. The log may be generated after the SCP 330 forwards the request for the service to the second NF 320. For example, if a request for the service and an access token obtained from the NRF 340 are received from the first NF 310, the SCP 330 may send the request for the service and the access token to the second NF 320. In addition, the SCP 330 may generate a log including an identifier of the first NF 310, an identifier of the second NF 320, an identifier of the NRF 340, an identifier of the service, a timestamp associated with the request for the service, the number of requests to access the service, the validity of the access token, or an indication of whether the service is provided by the second NF 320.

[0096] If the SCP 330 receives only a request for a service without an access token from the first NF 310, the SCP 330 may send a request for an access token to access the service to the NRF 340. After receiving the access token from the NRF 340, the SCP 330 generates a log including, for example, an identifier of the first NF 310, an identifier of the second NF 320, an identifier of the NRF 340, an identifier of the service, a timestamp associated with the request for the access token, and / or an identifier of the access token.

[0097] In some example embodiments, the SCP 330 reports (eg, sends or pushes) the log to a device for analyzing the provision of services from the second NF 320. Alternatively or additionally, the SCP 330 may store the log for retrieval or pulling by the analysis device when needed.

[0098] Figure 7 1 shows a flow chart of an example method 700 according to some example embodiments of the present disclosure. The method 700 may be performed as follows: Figure 3 For the purpose of discussion, reference will be made to the NRF 340. Figure 3 The method 700 is described in a scenario where the first NF 310 wants to access a service from the second NF 320.

[0099] At block 705, the NRF 340 receives a request for an access token from the first NF 310 or the SCP 330, which access token is to be used by the first NF 310 to access the service from the second NF 320. For example, in a communication model similar to the communication model 220 or 235 shown in FIG. 2(b) or FIG. 2(c), the NRF 340 may receive a request for an access token from the first NF 310. In a communication model similar to the communication model 240 shown in FIG. 2(d), the NRF 340 may receive a request for an access token from the SCP 330.

[0100] At block 710, the NRF 340 sends the access token to the first NF 310 or the SCP 330 accordingly. At block 715, the NRF 340 generates a log associated with the service from the second NF 320. For example, the log may include an identifier of the first NF 310, an identifier of the second NF 320, an identifier of the NRF 340, an identifier of the service, a timestamp associated with the request for the access token, and / or an identifier of the access token.

[0101] In some example embodiments, the logs may be reported (e.g., sent or pushed) by the NRF 340 to a device such as the NWDAF 350 for analyzing the provision of services from the second NF 320. Alternatively or additionally, the logs may be stored by the NRF 340 for retrieval or pulling by an analysis device when needed.

[0102] As shown in Figure 1- Figure 4 All operations and features described are equally applicable to methods 500, 600 and 700 and have similar effects. For simplicity, details will be omitted.

[0103] Figure 8 8 is a simplified block diagram of a device 800 suitable for implementing an example embodiment of the present disclosure. The device 800 may be implemented at or as part of a first or second NF 310 or 320, an SCP 330, an NRF 340, a device such as an NWDAF 350, etc., to facilitate analysis of provision of services from the NF.

[0104] As shown, the device 800 includes a processor 810, a memory 820 coupled to the processor 810, a communication module 830 coupled to the processor 810, and a communication interface (not shown) coupled to the communication module 830. The memory 820 stores at least a program 840. The communication module 830 is used for two-way communication, for example, via multiple antennas or via a cable. The communication interface can represent any interface required for communication.

[0105] Assume that program 840 includes program instructions that, when executed by associated processor 810, enable device 800 to operate in accordance with example embodiments of the present disclosure, as described herein with reference to FIGS. 1 to 3. Figure 7 The example embodiments herein may be implemented by computer software executable by the processor 810 of the device 800, or by hardware, or by a combination of software and hardware. The processor 810 may be configured to implement various example embodiments of the present disclosure.

[0106] The memory 820 may be of any type suitable for the local technology network and may be implemented using any appropriate data storage technology, such as, as non-limiting examples, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Although only one memory 820 is shown in the device 800, there may be several physically different memory modules in the device 800. The processor 810 may be of any type suitable for the local technology network and, as non-limiting examples, may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 800 may have multiple processors, such as a dedicated integrated circuit chip that is time-slave to a clock synchronized with a main processor.

[0107] When the device 800 acts as a collection device such as NWDAF 350, the processor 810 may implement the above-described process with reference to FIG. 1- Figure 4 When the device 800 acts as the first or second NF 310 or 320, the processor 810 may implement the above-described operation or action of the collection device with reference to FIG. Figure 4 When the device 800 acts as the SCP 330, the processor 810 may perform the operations or actions of the first NF 310 as described above with reference to FIG. Figure 6 When the device 800 acts as the NRF 340, the processor 810 may implement the operations or actions of the SCP 330 as described above with reference to FIG. Figure 7 The operation or action of the NRF 340.

[0108] As shown in Figure 1- Figure 7 All operations and features described are also applicable to the device 800 and have similar effects. For the sake of simplicity, the details will be omitted.

[0109] In general, various example embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the example embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the boxes, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.

[0110] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions, such as those included in a program module, which are executed in a device on a target real or virtual processor to perform the above-mentioned reference Figures 1 to Figure 7 The operations and actions described. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various example embodiments, the functionality of program modules can be combined or split between program modules as desired. Machine executable instructions for program modules can be executed in local devices or distributed devices. In distributed devices, program modules can be located in local and remote storage media.

[0111] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code can be executed entirely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0112] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals and computer-readable media.

[0113] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared or semiconductor system, device or apparatus, or any suitable combination of the foregoing. More specific examples of computer readable storage media would include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), a digital versatile disk (DVD), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0114] In addition, although each operation is depicted in a specific order, this should not be interpreted as requiring such operations to be performed in the specific order shown or in sequence, or performing all illustrated operations to achieve the desired result. In some scenarios, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of the present disclosure, but should be interpreted as descriptions of features that may be specific to a particular example embodiment. Certain features described in the context of separate example embodiments may also be combined in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented separately in multiple example embodiments or in any suitable sub-combination.

[0115] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

[0116] Various example embodiments of the technology have been described. In addition to or as an alternative to the above, the following examples are described. Features described in any of the following examples can be utilized with any other examples described herein.

[0117] In some aspects, a device includes: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to: obtain one or more logs from at least one of a first network function, a network repository function, and a service communication agent, the one or more logs being associated with a service from a second network function; and facilitate analysis of the provision of the service from the second network function based on the one or more logs.

[0118] In some example embodiments, the one or more logs include at least one log generated by at least one of the first network function, the network repository function, and the service communication agent upon requesting the network repository function for an access token to be used by the first network function to access the service, the at least one log including at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the network repository function, an identifier of the service, a timestamp associated with the request for the access token, or an identifier of the access token.

[0119] In some example embodiments, the one or more logs include a log generated by the first network function after sending a request for a service to a service communication agent or a second network function, the log including: an identifier of the first network function, an identifier of the second network function, an identifier of the service, a timestamp associated with the request for the service, a validity of an access token obtained from a network repository function for accessing the service, an identifier of the network repository function, or an indication of whether the service is provided by the second network function.

[0120] In some example embodiments, the one or more logs include a log generated by the service communication agent after receiving a request for a service from a first network function, the log including at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the service, a timestamp associated with the request for the service, a number of requests to access the service, a validity of an access token obtained from a network repository function to access the service, an identifier of the network repository function, or an indication of whether the service is provided by the second network function.

[0121] In some example embodiments, the device includes functionality capable of collecting one or more logs.

[0122] In some aspects, a device includes: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to: send, by a first network function, at least one of a request for an access token to access a service from a second network function or a request for the service; and generate, by the first network function, a log to facilitate analysis of provision of the service from the second network function, the log being associated with the service from the second network function.

[0123] In some example embodiments, the device is caused to send at least one of a request for an access token or a request for a service by: sending a request for an access token to a network repository function; and the device is caused to generate a log by: receiving the access token from the network repository function and generating a log including at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the network repository function, an identifier of the service, a timestamp associated with the request for the access token, or an identifier of the access token.

[0124] In some example embodiments, the device is caused to send at least one of a request for an access token or a request for a service by: sending the request for the service to a service communication agent or a second network function; and the device is caused to generate a log by: generating a log including at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the service, a timestamp associated with the request for the service, a validity of an access token obtained from a network repository function to access the service, an identifier of the network repository function, or an indication of whether the service is provided by the second network function.

[0125] In some example embodiments, the device is further caused to: send, by the first network function, a log to the device for analysis of provision of services from the second network function.

[0126] In some aspects, a device includes: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to: receive a request for a service from a second network function from a first network function; generate a log to facilitate analysis of the provision of the service from the second network function, the log being associated with the service from the second network function.

[0127] In some example embodiments, a device is caused to generate a log by: sending a request for an access token for accessing a service to a network repository function; receiving the access token from the network repository function; and generating a log including at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the network repository function, an identifier of the service, a timestamp associated with the request for the access token, or an identifier of the access token.

[0128] In some example embodiments, a device is caused to receive a request for a service by: receiving a request for a service and an access token obtained from a network repository function for accessing the service from a first network function; and the device is caused to generate a log by: sending a request for a service and the access token to a second network function; generating a log including at least one of the following: an identifier of the first network function, an identifier of the second network function, an identifier of the network repository function, an identifier of the service, a timestamp associated with the request for the service, a number of requests to access the service, a validity of the access token, or an indication of whether the service is provided by the second network function.

[0129] In some example embodiments, the device is further caused to: send the log to the device for analysis of provision of the service from the second network function.

[0130] In some aspects, a device includes: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to: receive, by a network repository function, a request for an access token from one of a first network function and a service communication agent, the access token to be used by the first network function to access a service from a second network function; send, by the network repository function, the access token to the one of the first network function and the service communication agent; and generate, by the network repository function, a log to facilitate analysis of the provision of services from the second network function, the log being associated with the services from the second network function.

[0131] In some example embodiments, the log includes at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the network repository function, an identifier of the service, a timestamp associated with the request for the access token, or an identifier of the access token.

[0132] In some example embodiments, the device is further caused to: send, by the network repository function, the log to the device for analysis of provision of services from the second network function.

[0133] In some aspects, a method includes: receiving one or more logs from at least one of a first network function, a network repository function, and a service communication agent, the one or more logs associated with a service from a second network function; and facilitating analysis of the service from the second network function based on the one or more logs.

[0134] In some example embodiments, the one or more logs include at least one log generated by at least one of the first network function, the network repository function, and the service communication agent upon requesting the network repository function for an access token to be used by the first network function to access the service, the at least one log including at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the network repository function, an identifier of the service, a timestamp associated with the request for the access token, or an identifier of the access token.

[0135] In some example embodiments, the one or more logs include a log generated by the first network function after sending a request for a service to a service communication agent or a second network function, the log including: an identifier of the first network function, an identifier of the second network function, an identifier of the service, a timestamp associated with the request for the service, a validity of an access token obtained from a network repository function for accessing the service, an identifier of the network repository function, or an indication of whether the service is provided by the second network function.

[0136] In some example embodiments, the one or more logs include a log generated by the service communication agent after receiving a request for a service from a first network function, the log including at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the service, a timestamp associated with the request for the service, a number of requests to access the service, a validity of an access token obtained from a network repository function for accessing the service, an identifier of the network repository function, or an indication of whether the service is provided by the second network function.

[0137] In some example embodiments, the method is implemented at a function capable of collecting one or more logs.

[0138] In some aspects, a method implemented at a first network function includes: sending at least one of a request for an access token to access a service from a second network function or a request for a service; generating a log to facilitate analysis of provisioning of the service from the second network function, the log being associated with the service from the second network function.

[0139] In some example embodiments, sending at least one of a request for an access token or a request for a service includes: sending a request for an access token to a network repository function; and generating a log includes: receiving the access token from the network repository function, and generating a log including at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the network repository function, an identifier of the service, a timestamp associated with the request for the access token, or an identifier of the access token.

[0140] In some example embodiments, sending at least one of a request for an access token or a request for a service includes: sending a request for the service to a service communication agent or a second network function; generating a log includes: generating a log including at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the service, a timestamp associated with the request for the service, a validity of an access token obtained from a network repository function for accessing the service, an identifier of the network repository function, or an indication of whether the service is provided by the second network function.

[0141] In some example embodiments, the method further comprises sending the log to the device for analyzing provision of the service from the second network function.

[0142] In some aspects, a method implemented at a service communication agent includes: receiving a request for a service from a second network function from a first network function; and generating a log to facilitate analysis of provisioning of the service from the second network function, the log associated with the service from the second network function.

[0143] In some example embodiments, generating a log includes: sending a request for an access token for accessing a service to a network repository function; receiving the access token from the network repository function; generating a log including at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the network repository function, an identifier of the service, a timestamp associated with the request for the access token, or an identifier of the access token.

[0144] In some example embodiments, receiving a request for a service includes: receiving a request for the service and an access token obtained from a network repository function to access the service from a first network function; and generating a log includes: sending the request for the service and the access token to a second network function; and generating a log including at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the network repository function, an identifier of the service, a timestamp associated with the request for the service, a number of requests to access the service, a validity of the access token, or an indication of whether the service is provided by the second network function.

[0145] In some example embodiments, the method further comprises sending the log to the device for analyzing provision of the service from the second network function.

[0146] In some aspects, a method implemented at a network repository function includes: receiving a request for an access token from one of a first network function and a service communication agent, the access token to be used by the first network function to access a service from a second network function; sending the access token to the one of the first network function and the service communication agent; and generating a log to facilitate analysis of the provisioning of the service from the second network function, the log being associated with the service from the second network function.

[0147] In some example embodiments, the log includes at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the network repository function, an identifier of the service, a timestamp associated with the request for the access token, or an identifier of the access token.

[0148] In some example embodiments, the method further comprises sending the log to the device for analyzing provisioning of services from the second network function.

[0149] In some aspects, an apparatus includes: a component for receiving one or more logs from at least one of a first network function, a network repository function, and a service communication agent, the one or more logs being associated with a service from a second network function; and a component for facilitating analysis of the service from the second network function based on the one or more logs.

[0150] In some example embodiments, the one or more logs include at least one log generated by at least one of the first network function, the network repository function, and the service communication agent after requesting from the network repository function an access token to be used by the first network function to access the service, the at least one log including at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the network repository function, an identifier of the service, a timestamp associated with the request for the access token, or an identifier of the access token.

[0151] In some example embodiments, the one or more logs include a log generated by the first network function after sending a request for a service to a service communication agent or a second network function, the log including: an identifier of the first network function, an identifier of the second network function, an identifier of the service, a timestamp associated with the request for the service, a validity of an access token obtained from a network repository function for accessing the service, an identifier of the network repository function, or an indication of whether the service is provided by the second network function.

[0152] In some example embodiments, the one or more logs include a log generated by the service communication agent after receiving a request for a service from a first network function, the log including at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the service, a timestamp associated with the request for the service, a number of requests to access the service, a validity of an access token obtained from a network repository function for accessing the service, an identifier of the network repository function, or an indication of whether the service is provided by the second network function.

[0153] In some example embodiments, the apparatus is implemented at a functionality capable of collecting one or more logs.

[0154] In some aspects, an apparatus implemented at a first network function includes: a component for sending at least one of a request for an access token to access a service from a second network function or a request for a service; and a component for generating a log to facilitate analysis of the provision of the service from the second network function, the log being associated with the service from the second network function.

[0155] In some example embodiments, the component for sending at least one of a request for an access token or a request for a service includes: a component for sending a request for an access token to a network repository function; and the component for generating a log includes: a component for receiving an access token from the network repository function, and a component for generating a log, the log including at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the network repository function, an identifier of the service, a timestamp associated with the request for the access token, or an identifier of the access token.

[0156] In some example embodiments, the component for sending at least one of a request for an access token or a request for a service includes: a component for sending the request for the service to a service communication agent or a second network function; and the component for generating a log includes: a component for generating a log including at least one of the following: an identifier of the first network function, an identifier of the second network function, an identifier of the service, a timestamp associated with the request for the service, a validity of an access token obtained from a network repository function for accessing the service, an identifier of the network repository function, or an indication of whether the service is provided by the second network function.

[0157] In some example embodiments, the apparatus further comprises means for sending the log to the device to facilitate analysis of provisioning of services from the second network function.

[0158] In some aspects, an apparatus implemented at a service communication agent includes: a component for receiving a request for a service from a second network function from a first network function; and a component for generating a log to facilitate analysis of the provision of the service from the second network function, the log being associated with the service from the second network function.

[0159] In some example embodiments, components for generating a log include: components for sending a request for an access token for accessing a service to a network repository function; components for receiving the access token from the network repository function; and components for generating a log including at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the network repository function, an identifier of the service, a timestamp associated with the request for the access token, or an identifier of the access token.

[0160] In some example embodiments, the component for receiving a request for a service includes: a component for receiving a request for a service from a first network function and an access token for accessing the service obtained from a network repository function; the component for generating a log includes: a component for sending a request for a service and the access token to a second network function; and a component for generating a log including at least one of the following: an identifier of the first network function, an identifier of the second network function, an identifier of the network repository function, an identifier of the service, a timestamp associated with the request for the service, a number of requests to access the service, a validity of the access token, or an indication of whether the service is provided by the second network function.

[0161] In some example embodiments, the apparatus further comprises means for sending the log to the device to facilitate analysis of provisioning of services from the second network function.

[0162] In some aspects, an apparatus implemented at a network repository function includes: a component for receiving a request for an access token from one of a first network function and a service communication agent, the access token to be used by the first network function to access a service from a second network function; a component for sending the access token to the one of the first network function and the service communication agent; and a component for generating a log to facilitate analysis of the provision of services from the second network function, the log being associated with the services from the second network function.

[0163] In some example embodiments, the log includes at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the network repository function, an identifier of the service, a timestamp associated with the request for the access token, or an identifier of the access token.

[0164] In some example embodiments, the apparatus further comprises means for sending the log to the device to facilitate analysis of provisioning of services from the second network function.

[0165] In some aspects, a computer-readable storage medium includes program instructions stored thereon, which when executed by a processor of a device causes the device to perform a method according to some example embodiments of the present disclosure.

Claims

1. A device for communication, comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: receiving one or more logs from at least one of the first network function, the network repository function, and the service communication agent, the one or more logs being associated with a service from the second network function; as well as facilitating analysis of provisioning of the service from the second network function based on the one or more logs; wherein the one or more logs include at least one log generated by at least one of the first network function, the network repository function, and the service communication agent upon requesting an access token to be used by the first network function to access the service from the network repository function, the at least one log including at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of said network repository function, an identifier of the service, a timestamp associated with the request for the access token, An identifier for the access token.

2. The apparatus of claim 1 , wherein the one or more logs further include a log generated by the first network function after sending a request for the service to the service communication agent or the second network function, the log comprising: an identifier of the first network function, an identifier of the second network function, an identifier of the service, a timestamp associated with the request to the service, the validity of an access token obtained from said network repository function for accessing said service, an identifier of said network repository function, An indication of whether the service is provided by the second network function.

3. The apparatus of claim 1 , wherein the one or more logs further include a log generated by the service communication agent after receiving a request for the service from the first network function, the log comprising at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the service, a timestamp associated with the request to the service, the number of requests to access the service, the validity of an access token obtained from said network repository function for accessing said service, an identifier of said network repository function, An indication of whether the service is provided by the second network function.

4. The device according to any one of claims 1-3, wherein the device comprises functionality capable of collecting the one or more logs.

5. A device at a first network function, comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: sending, by the first network function, at least one of a request for an access token to access a service from the second network function or a request for the service; as well as generating, by the first network function, a log to facilitate analysis of provisioning of the service from the second network function, the log being associated with the service from the second network function; wherein the log comprises at least one log generated by the first network function upon requesting an access token to be used by the first network function to access the service from a network repository function, the at least one log comprising at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of said network repository function, an identifier of the service, a timestamp associated with the request for the access token, An identifier for the access token.

6. The device according to claim 5, wherein The device is caused to send at least one of the request for the access token or the request for the service by: sending the request for the service to a service communication agent or the second network function; and The device is configured to generate the log by: Generate the log including at least one of the following: an identifier of the first network function, an identifier of the second network function, an identifier of the service, a timestamp associated with the request to the service, the validity of an access token obtained from said network repository function for accessing said service, an identifier of said network repository function, An indication of whether the service is provided by the second network function.

7. The device according to any one of claims 5-6, wherein the device is further configured to: The log is sent by the first network function to a device to facilitate analysis of provision of the service from the second network function.

8. A device at a serving communication agent, comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: receiving, from the first network function, a request for a service from the second network function; as well as generating a log to facilitate analysis of provisioning of the service from the second network function, the log being associated with the service from the second network function; wherein the log comprises at least one log generated by the service communication agent upon requesting an access token to be used by the first network function to access the service from a network repository function, the at least one log comprising at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of said network repository function, an identifier of the service, a timestamp associated with the request for the access token, An identifier for the access token.

9. The device according to claim 8, wherein the device is caused to generate the log by: sending a request to the network repository function for an access token for accessing the service; receiving the access token from the network repository function; as well as Generate the log including at least one of the following: an identifier of the first network function, an identifier of the second network function, an identifier of said network repository function, an identifier of the service, a timestamp associated with the request for the access token, An identifier for the access token.

10. The device according to claim 8, wherein The device is caused to receive the request for the service by: receiving, from the first network function, the request for the service and an access token obtained from a network repository function to access the service; as well as The device is configured to generate the log by: sending the request for the service and the access token to the second network function; as well as Generate the log including at least one of the following: an identifier of the first network function, an identifier of the second network function, an identifier of said network repository function, an identifier of the service, a timestamp associated with the request to the service, the number of requests to access the service, the validity of the access token, An indication of whether the service is provided by the second network function.

11. The apparatus according to any one of claims 8 to 10, wherein the apparatus is further configured to: The log is sent to a device to facilitate analysis of provisioning of the service from the second network function.

12. An apparatus at a network repository function, comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the device to at least: receiving, by the network repository function, from one of the first network function and the service communication agent, a request for an access token to be used by the first network function to access a service from a second network function; sending, by the network repository function, the access token to the one of the first network function and the service communication agent; as well as generating, by the network repository function, a log to facilitate analysis of provision of the service from the second network function, the log being associated with the service from the second network function; wherein the log comprises the log being generated by the network repository function upon requesting an access token to be used by the first network function to access the service from the network repository function, The log includes at least one of the following: an identifier of the first network function, an identifier of the second network function, an identifier of said network repository function, an identifier of the service, a timestamp associated with the request for the access token, An identifier for the access token.

13. The apparatus of claim 12, wherein the apparatus is further configured to: The log is sent by the network repository function to a device to facilitate analysis of provisioning of the service from the second network function.

14. A method for communication, comprising: receiving one or more logs from at least one of the first network function, the network repository function, and the service communication agent, the one or more logs being associated with a service from the second network function; as well as facilitating analysis of provisioning of the service from the second network function based on the one or more logs; wherein the one or more logs include at least one log generated by at least one of the first network function, the network repository function, and the service communication agent upon requesting an access token to be used by the first network function to access the service from the network repository function, the at least one log including at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of said network repository function, an identifier of the service, a timestamp associated with the request for the access token, An identifier for the access token.

15. The method of claim 14, wherein the one or more logs include a log generated by the first network function after sending a request for the service to the service communication agent or the second network function, the log comprising: an identifier of the first network function, an identifier of the second network function, an identifier of the service, a timestamp associated with the request to the service, the validity of an access token obtained from said network repository function for accessing said service, an identifier of said network repository function, An indication of whether the service is provided by the second network function.

16. The method of claim 14, wherein the one or more logs include a log generated by the service communication agent after receiving a request for the service from the first network function, the log including at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of the service, a timestamp associated with the request to the service, the number of requests to access the service, the validity of an access token obtained from said network repository function for accessing said service, an identifier of said network repository function, An indication of whether the service is provided by the second network function.

17. The method according to any one of claims 14 to 16, wherein the method is implemented at a function capable of collecting the one or more logs.

18. A method implemented at a first network function, comprising: sending at least one of a request for an access token to access a service from a second network function or a request for the service; as well as generating a log to facilitate analysis of provisioning of the service from the second network function, the log being associated with the service from the second network function; wherein the log comprises at least one log generated by the first network function upon requesting an access token to be used by the first network function to access the service from a network repository function, the at least one log comprising at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of said network repository function, an identifier of the service, a timestamp associated with the request for the access token, An identifier for the access token.

19. The method according to claim 18, wherein Sending at least one of the request for the access token or the request for the service comprises: sending the request for the service to a service communication agent or the second network function; as well as Generating the log includes: Generate the log including at least one of the following: an identifier of the first network function, an identifier of the second network function, an identifier of the service, a timestamp associated with the request to the service, the validity of the access token obtained from the network repository function for accessing the service, an identifier of said network repository function, An indication of whether the service is provided by the second network function.

20. The method according to any one of claims 18-19, further comprising: The log is sent to a device to facilitate analysis of provisioning of the service from the second network function.

21. A method implemented at a service communication agent, comprising: receiving, from the first network function, a request for a service from the second network function; as well as generating a log to facilitate analysis of provisioning of the service from the second network function, the log being associated with the service from the second network function; wherein the log comprises at least one log generated by the service communication agent upon requesting an access token to be used by the first network function to access the service from a network repository function, the at least one log comprising at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of said network repository function, an identifier of the service, a timestamp associated with the request for the access token, An identifier for the access token.

22. The method of claim 21, wherein generating the log comprises: sending a request to the network repository function for an access token for accessing the service; receiving the access token from the network repository function; as well as Generating the log including at least one of the following: an identifier of the first network function, an identifier of the second network function, an identifier of said network repository function, an identifier of the service, a timestamp associated with the request for the access token, An identifier for the access token.

23. The method according to claim 21, wherein Receiving the request for the service includes: receiving, from the first network function, the request for the service and an access token obtained from a network repository function to access the service; as well as Generating the log includes: sending the request for the service and the access token to the second network function; as well as Generating the log including at least one of the following: an identifier of the first network function, an identifier of the second network function, an identifier of said network repository function, an identifier of the service, a timestamp associated with the request to the service, the number of requests to access the service, the validity of the access token, An indication of whether the service is provided by the second network function.

24. The method according to any one of claims 21 to 23, further comprising: The log is sent to a device to facilitate analysis of provisioning of the service from the second network function.

25. A method implemented at a network repository function, comprising: receiving, from one of a first network function and a service communication agent, a request for an access token to be used by the first network function to access a service from a second network function; sending the access token to the one of the first network function and the service communication agent; as well as generating a log to facilitate analysis of provisioning of the service from the second network function, the log being associated with the service from the second network function; wherein the log comprises at least one log generated by the network repository function upon requesting an access token to be used by the first network function to access the service from the network repository function, the at least one log comprising at least one of: an identifier of the first network function, an identifier of the second network function, an identifier of said network repository function, an identifier of the service, a timestamp associated with the request for the access token, An identifier for the access token.

26. The method according to claim 25, further comprising: The log is sent to a device to facilitate analysis of provisioning of the service from the second network function.

27. An apparatus for communication comprising means for performing the method according to any one of claims 14 to 17.

28. An apparatus at a first network function, comprising means for performing the method according to any one of claims 18 to 20.

29. An arrangement at a serving communication agent, comprising means for performing the method according to any one of claims 21 to 24.

30. An apparatus at a network repository function, comprising means for performing a method according to any one of claims 25 to 26.

31. A computer-readable medium comprising program instructions, which, when executed by an apparatus, cause the apparatus to at least perform the method according to any one of claims 14-17.

32. A computer-readable medium comprising program instructions, which, when executed by an apparatus, cause the apparatus to at least perform the method according to any one of claims 18 to 20.

33. A computer readable medium comprising program instructions which, when executed by an apparatus, cause the apparatus to at least perform the method according to any one of claims 21 to 24.

34. A computer readable medium comprising program instructions which, when executed by an apparatus, cause the apparatus to at least perform the method according to any one of claims 25-26.

Images