Patent Description:
In the communication arena, <NUM> communication system can support artificial intelligence (AI) or machine learning (ML) services. To avoid authorization risks in AI/ML operations, the <NUM> communication system needs to enable: <NUM> system assistance for the security management which requires data transmission support for application layer AI/ML operation over the <NUM> communication system, authentication and authorization involving data collection and sharing among terminal devices, Application Function (AF) and <NUM> core network, to take part in application layer AI/ML operations. It is also needed for the <NUM> communication system to enable secure AI/ML based services and operations, and to enable secure provisioning of the external parameters required for AI/ML, such as expected terminal device behaviors, and expected terminal device mobility, etc..

Recent <NUM> communication system can support AI/ML, but the <NUM> core network cannot support authorization per terminal device level. Therefore, it is needed to be solved how the <NUM> core network can authorize analytics requests coming from the terminal device. In patent application <CIT>, a method and apparatus for providing network auxiliary information, electronic device, and computer-readable storage medium are disclosed. Furthermore, in patent application <CIT>, a Network Data Analytics Function, NWDAF, including: means for receiving analytics information regarding cell re-selection by User Equipment, UE, among cells; and means for notifying another network node of matching the analytics information with an exception so that the other network node takes actions for solving the exception is disclosed. "<NPL> is a standardization document relating to Architecture enhancements for <NUM> System (5GS) to support network data analytics services.

In general, example embodiments of the present disclosure provide a solution for terminal device authorization for requesting analytics. According to the present invention, a terminal device as defined in claims <NUM> to <NUM>, a unified data management as defined in claims <NUM> to <NUM>, methods as defined in claims <NUM> to <NUM>, and a non-transitory computer readable medium as defined in claim <NUM> are provided.

In a first aspect, there is provided a device. The device comprises at least one processor; and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the device to transmit, at a terminal device, a subscription for an analytics with an analytics identity to a Unified Data Management (UDM), receive a subscribed analytics identity from the UDM, according to the subscription for the analytics, transmit a request comprising the analytics identity to a Session Management Function (SMF) or an Application Function (AF), and receive analytics result data from the SMF or the AF, according to the analytics identity after authorization of the request.

In a second aspect, there is provided a device. The device comprises at least one processor; and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the device to receive, at a Unified Data Management (UDM), a subscription for an analytics with an analytics identity from a terminal device, in response to receiving the subscription for the analytics, register a terminal device information in the UDM, along with Public Land Mobile Network (PLMN) information and slice information associated with the terminal device, transmit a subscribed analytics identity to the terminal device.

In a third aspect, there is provided a device. The device comprises at least one processor; and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the device to receive, at a Network Repository Function (NRF) an access token request comprising a terminal device identity, a slice identity, and at least one analytics identity, from a Session Management Function (SMF) or an Application Function (AF), get, from a Unified Data Management (UDM), a terminal device information associated with the analytics identity and the terminal device identity, verify based on the got terminal device information, whether the terminal device is authorized to receive the analytics identity, in response to success of the verification with the got terminal device information, transmit an access token with the terminal device identity, the slice identity, and the analytics identity, to the SMF or the AF.

In a fourth aspect, there is provided a device. The device comprises at least one processor; and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the device to receive, at a Network Data Analytics Function (NWDAF), a service request with an analytics identity from a Session Management Function (SMF) or an Application Function (AF), and transmit analytics result data to the SMF or the AF, according to the analytics identity after authorization of the service request.

In a fifth aspect, there is provided a device. The device comprises at least one processor; and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the device to receive, at a Session Management Function (SMF), a request with an analytics identity from a terminal device, transmit, to a Network Data Analytics Function (NWDAF), a service request comprising the an analytics identity, receive, from the NWDAF, analytics result data, according to the service request, and transmit the analytics result data to the terminal device.

In a sixth aspect, there is provided a device. The device comprises at least one processor; and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the device to receive, at an Application Function (AF), a request with an analytics identity from a terminal device, transmit, to a Network Data Analytics Function (NWDAF), a service request comprising the analytics identity, receive, from the NWDAF, analytics result data according to the service request, and transmit, to the terminal device, the analytics result data.

In a seventh aspect, there is provided a method implemented at a terminal device. The method comprises transmitting, a subscription for an analytics with an analytics identity to a Unified Data Management (UDM), receiving a subscribed analytics identity from the UDM, according to the subscription for the analytics, transmitting a request comprising the analytics identity to a Session Management Function (SMF) or an Application Function (AF), and receiving analytics result data from the SMF or the AF, according to the analytics identity after authorization of the request.

In an eighth aspect, there is provided a method implemented at a Unified Data Management (UDM). The method comprises receiving a subscription for an analytics with an analytics identity from a terminal device, in response to receiving the subscription for the analytics, registering a terminal device information in the UDM, along with Public Land Mobile Network (PLMN) information and slice information associated with the terminal device, and transmitting a subscribed analytics identity to the terminal device.

In a ninth aspect, there is provided a method implemented at a Network Repository Function (NRF). The method comprises receiving an access token request with a terminal device identity, a slice identity, and at least one analytics identity, from a Session Management Function (SMF) or an Application Function (AF), getting, from a Unified Data Management (UDM), a terminal device information associated with the at least one analytics identity and the terminal device identity, verifying with the got terminal device information, whether the terminal device is authorized to receive the analytics identity, and in response to success of the verification with the got terminal device information, transmitting an access token with the terminal device identity, the slice identity, and the analytics identity, to the SMF or the AF.

In a tenth aspect, there is provided a method implemented at a Network Data Analytics Function (NWDAF). The method comprises receiving a service request with an analytics identity from a Session Management Function (SMF) or an Application Function (AF), and transmitting analytics result data to the SMF or an AF, according to the analytics identity after authorization of the service request.

In an eleventh aspect, there is provided a method implemented at a Session Management Function (SMF). The method comprises receiving a request with an analytics identity from a terminal device, transmitting, to a Network Data Analytics Function (NWDAF), a service request comprising the analytics identity, receiving, from the NWDAF, analytics result data, according to the service request, and transmitting the analytics result data to the terminal device.

In a twelfth aspect, there is provided a method implemented at an Application Function (AF). The method comprises receiving a request with an analytics identity from a terminal device, transmitting, to a Network Data Analytics Function (NWDAF), a service request comprising the analytics identity, receiving, from the NWDAF, analytics result data according to the service request, according to the service request, and transmitting, to the terminal device, the analytics result data.

In a thirteenth aspect, there is provided an apparatus comprising means for transmitting, at a terminal device, a subscription for an analytics with an analytics identity to a Unified Data Management (UDM), means for receiving a subscribed analytics identity from the UDM, according to the subscription for the analytics, means for transmitting a request comprising the analytics identity to a Session Management Function (SMF) or an Application Function (AF), and means for receiving analytics result data from the SMF or the AF, according to the analytics identity after authorization of the request.

In a fourteenth aspect, there is provided an apparatus comprising means for receiving, at a Unified Data Management (UDM), a subscription for an analytics identity with an analytics from a terminal device, means for in response to receiving the subscription for the analytics, registering a terminal device information in the UDM, along with Public Land Mobile Network (PLMN) information and slice information associated with the terminal device, and means for transmitting a subscribed analytics identity to the terminal device.

In a fifteenth aspect, there is provided an apparatus comprising means for receiving, at a Network Repository Function (NRF), an access token request with a terminal device identity, a slice identity, and at least one analytics identity, from a Session Management Function (SMF) or an Application Function (AF), means for getting, from a Unified Data Management, a terminal device information associated with the at least one analytics identity and the terminal device identity, means for verifying with the got terminal device information, whether the terminal device is authorized to receive the analytics identity, and means for in response to success of the verification with the got terminal device information, transmitting an access token with the terminal device identity, the slice identity, and the analytics identity, to the SMF or the AF.

In a sixteenth aspect, there is provided an apparatus comprising means for receiving, at a Network Data Analytics Function (NWDAF), a service request with an analytics identity from a Session Management Function (SMF) or an Application Function (AF), and means for transmitting analytics result data to the SMF or an AF, according to the analytics identity after authorization of the service request.

In a seventeenth aspect, there is provided an apparatus comprising means for receiving, at a Session Management Function (SMF), a request with an analytics identity from a terminal device, means for transmitting, to a Network Data Analytics Function (NWDAF), a service request comprising the analytics identity, means for receiving, from the NWDAF, analytics result data, according to the service request, and means for transmitting the analytics result data to the terminal device.

In a eighteenth aspect, there is provided an apparatus comprising means for receiving, at an Application Function (AF), a request with an analytics identity from a terminal device, means for transmitting, to a Network Data Analytics Function (NWDAF), a service request comprising the analytics identity, means for receiving, from the NWDAF, analytics result data according to the service request, according to the service request, and means for transmitting, to the terminal device, the analytics result data.

In a nineteenth aspect, there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method according to any one of the above seventh to twelfth aspect.

As used herein, the term "network function" refers to a function in <NUM> core network, including at least one of Unified Data Management (UDM), Network Repository Function (NRF), Network Data Analytics Function (NWDAF), Session Management Function (SMF), Access and Mobility Management Function (AMF), Application Function (AF) and Network Exposure Function (NEF). These network functions are associated with the terminal device authorization for requesting analytics for AL/ML in the example embodiments of the present disclosure. It is commonly understood by one of ordinary skills in the art that a <NUM> core network may comprise more functions than the UDM, NRF, NWDAF, SMF, AMF, AF and NEF, such as Policy Control Function (PCF), Network Slice Selection Function (NSSF), Authentication Server Function (AUSF), etc. The AI/ML services may be any AI/ML services that can be supported in the <NUM> core network, such as image recognition, auto driving, online gaming, etc..

The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like.

As descripted in the background, recent <NUM> communication system can support AI/ML, but the <NUM> core network cannot support authorization per terminal device level. Therefore, it is needed to be solved how the <NUM> core network can authorize analytics requests coming from the terminal device.

According to embodiments of the present disclosure, there is providing a solution for terminal device authorization for requesting analytics with <NUM> core network.

Principle and embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. Reference is first made to <FIG>, which illustrates a process <NUM> for terminal device authorization for requesting analytics according to some embodiments of the present disclosure. The process <NUM> may involve a terminal device (TD) <NUM>, plurality of network functions, such as an AMF <NUM>, a SMF103, a NRF <NUM>, a UDM <NUM>, and a NWDAF <NUM>.

According to example embodiments of the present disclosure, the TD <NUM> transmits <NUM> a subscription for an analytics with an analytics identity to the UDM <NUM>. The subscription for the analytics with the analytics identity may be transmitted through an Application Function (AF), a Customer Relationship Management (CRM), or a portal. In response to receiving the subscription for the analytics with an analytics identity, UDM <NUM> registers a terminal device information in the UDM <NUM>, along with Public Land Mobile Network (PLMN) information and slice information associated with the TD <NUM>. After the registration, The UDM <NUM> transmits <NUM> a subscribed analytics identity to the TD <NUM>. The subscribed analytics identity may be transmitted via a UE Parameter Update (UPU) procedure from the UDM105 to the TD <NUM>. The analytics is an AI/ML logic or AI/ML service or AIML model running in the network. The analytics identity is an identity of the analytics. Terminal device uses this identity to invoke relevant applications in the network.

The TD <NUM> transmits <NUM> a request comprising the analytics identity to the SMF <NUM>. Specifically, the TD <NUM> may set up a Protocol Data Unit (PDU) session with the SMF <NUM>, then transmit the request comprising the analytics identity to the SMF <NUM> with the PDU session. According to example embodiments of the present disclosure, the request comprising the analytics identity from the TD <NUM> may be transmitted through the AMF <NUM> to the SMF <NUM>, due to the <NUM> core network architecture.

The SMF <NUM> transmits <NUM>, to the NRF <NUM>, an access token request with the terminal device identity, a slice identity, and the analytics identity.

According to an example embodiment of the present disclosure, the Table <NUM>. <NUM>-<NUM>: Definition of type AccessTokenReq in 3GPP specification TS <NUM> may be updated with the additional terminal device identity, slice identity, and analytics identity, as with the gray background in the following table. It is commonly understood by one of ordinary skills in the art that the following table shows the table update in the 3GPP specification with an example embodiment of the present disclosure, but without any limitation for the update of the table. The data type of the analytics identity, the terminal device identity (UE ID) or the slice identity (slice ID) may be other data type, the description may be illustrated in other format, the table number may be amended, etc.
<IMG>.

According to example embodiments of the present disclosure, the SMF <NUM> receives the terminal device identity from the request comprising the analytics identity from the TD <NUM>. The slice identity is for network slicing for the AI/ML services, which may be carried out in the NSSF.

The NRF <NUM>, transmits <NUM> to the UDM <NUM>, a request for the terminal device information, wherein the request comprises the analytics identity and the terminal device identity. In response to the request for the terminal device information, the UDM <NUM> transmits <NUM> the terminal device information back to the NRF <NUM>. The terminal device information may comprise the terminal device identity, the analytics identity, at least one supported slice identity per analytics identity, and at least one supported PLMN identity per analytics identity. According to example embodiments of the present disclosure, analytics <NUM> such as image recognition is allowed for slice <NUM> and/or slice <NUM>, and the terminal device may use analytics <NUM> in PLMN <NUM> and / or PLMN <NUM>.

The NRF <NUM> verifies <NUM> with the got terminal device information, whether the terminal device identity is authorized to receive the analytics identity.

In response to success of the verification with the got terminal device information, the NRF <NUM> transmits <NUM> an access token with the terminal device identity, the slice identity, and the analytics identity, to the SMF <NUM>.

According to an example embodiment of the present disclosure, the Table <NUM>. <NUM>-<NUM>: Definition of type AccessTokenClaims in 3GPP specification TS <NUM> may be updated with the additional terminal device identity, slice identity, and analytics identity, as with the gray background in the following table. It is commonly understood by one of ordinary skills in the art that the following table shows the table update in the 3GPP specification with an example embodiment of the present disclosure, but without any limitation for the update of the table. The data type of the analytics identity, the terminal device identity (UE ID) or the slice identity (slice ID) may be other data type, the description may be illustrated in further format, the table number may be amended, etc.
<IMG>.

The SMF <NUM> transmits <NUM>, to the NWDAF <NUM>, a service request comprising the analytics identity and the access token. The NWDAF <NUM> verifies <NUM> the access token with the terminal device identity and the analytics identity. The terminal device information used in the access token verification may be from the UDM <NUM>. In response to success of the verification of the access token, the NWDAF <NUM> transmits <NUM> an analytics result data to the SMF <NUM>. The SMF <NUM> transmits <NUM> the analytics result data to the TD <NUM>. The analytics result data may be transmitted from the SMF <NUM> to the TD <NUM> via the AMF <NUM>, due to the architecture of the <NUM> core network.

According to example embodiments of the present disclosure, in the process <NUM>, the authorization is implemented in the NRF <NUM> based on a terminal device information and associated information.

According to example embodiments of the present disclosure, an analytics is an artificial intelligence (AI) / machine learning (ML) logic or AI / ML service or AI / ML model running in a <NUM> core network. The analytics identity is an identity for an analytics, to invoke a relevant application in the <NUM> core network.

According to example embodiments of the present disclosure, the process for terminal device authorization for requesting analytics may be implemented without the NRF <NUM>, and without the access token, as illustrated in <FIG>. Without access token, the implementation of the process may be simplified.

In the process <NUM> in <FIG>, the TD <NUM> and the network functions AMF <NUM>, SMF <NUM>, NWDAF <NUM>, UDM <NUM> are the same with those in <FIG>, and the steps <NUM>, <NUM>, <NUM>, <NUM>, <NUM> may be the same with those in <FIG> as well.

Without the NRF <NUM>, SMF <NUM> transmits <NUM> to the NWDAF <NUM>, a service request with an analytics identity. The NWDAF <NUM> transmits <NUM> a request for a terminal device information associated with the analytics identity and the terminal device identity to the UDM <NUM>, then receives <NUM> the terminal device information from the UDM <NUM>, wherein the terminal device information comprises the analytics identity, the terminal device identity, at least one supported slice identity per analytics identity, and at least one supported PLMN identity per analytics identity. The NWDAF <NUM> verifies <NUM> the authorization of the analytics identity and the terminal device identity based on the received terminal device information from UDM <NUM>. In response to the success of verifying the authorization, the NWDAF <NUM> transmits <NUM> the analytics result data to the SMF <NUM>.

According to example embodiments of the present disclosure, in the process <NUM>, the authorization is implemented in the UDM <NUM> based on a terminal device information and associated information.

According to example embodiments of the present disclosure, the process for terminal device authorization for requesting analytics may be implemented without the AF, or the SMF, but with an AF, as illustrated in <FIG>.

As illustrated in the process <NUM> in <FIG>, compared with <FIG>, the AMF <NUM> and the SMF <NUM> are removed, while an AF <NUM> is added. In the process <NUM> in <FIG>, the steps <NUM>, <NUM>, <NUM>, <NUM>,<NUM>, and <NUM> may be the same with those in <FIG>.

TD <NUM> transmits <NUM> a request comprising the analytics identity to an AF <NUM>. In <NUM>, the AF <NUM> converts a terminal device IP address to a Subscription Permanent Identifier (SUPI), and uses the SUPI as the terminal device identity. The AF <NUM> transmits <NUM>, to the NRF <NUM>, an access token request comprising the terminal device identity, a slice identity, and an analytics identity. The NRF <NUM> verifies <NUM> based on the got terminal device information, whether the terminal device identity is authorized to receive the analytics identity. In response to success of the verification with the got terminal device information, the NRF <NUM> transmits <NUM> an access token with the terminal device identity, the slice identity, and the analytics identity, to the AF <NUM>.

The AF <NUM> transmits <NUM>, to the NWDAF <NUM>, a service request with the analytics identity and the access token received from the NRF <NUM>. In case of successful verification of the access token by the NWDAF <NUM>, the analytics result data is sent by the NWDAF <NUM>. The AF <NUM> then receives <NUM> an analytics result data according to the service request. Finally, the AF <NUM> transmits <NUM> the analytics result data to the terminal device.

According to example embodiments of the present disclosure, NRF104 may also be removed from process <NUM>, as well as the access token, for the simplicity of implementation, as in <FIG>.

As illustrated in <FIG>, process <NUM> comprises TD <NUM>, AF <NUM>, NWDAF <NUM>, UDM <NUM>, as the same with those in <FIG>. The steps <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> may be the same with those in <FIG>. The steps <NUM>, <NUM>, and <NUM> may be the same with those in <FIG>.

According to example embodiments of the present disclosure, the AF <NUM> transmits <NUM>, to the NWDAF <NUM>, a service request with an analytics identity. The NWDAF <NUM> transmits <NUM> a request for a terminal device information associated with the analytics identity and the terminal device identity to the UDM <NUM>, then receives <NUM> the terminal device information from the UDM <NUM>, wherein the terminal device information comprises the analytics identity, the terminal device identity, at least one supported slice identity per analytics identity, and at least one supported PLMN identity per analytics identity. The NWDAF <NUM> verifies <NUM> the authorization of the analytics identity and the terminal device identity based on the received terminal device information from UDM <NUM>. In response to the success of verifying the authorization, the NWDAF <NUM> transmits <NUM> the analytics result data to the AF <NUM>. Finally, the AF <NUM> transmits the analytics result data to the TD <NUM>.

<FIG> illustrates a flowchart of a method implemented at a terminal device according to some embodiments of the present disclosure. For the purpose of discussion, the method <NUM> will be described from the perspective of the terminal device <NUM> with reference to <FIG>, <FIG>.

At block <NUM>, the terminal device <NUM> transmits, a subscription for an analytics with an analytics identity to a Unified Data Management (UDM). At block <NUM>, the terminal device <NUM> receives a subscribed analytics identity from the UDM, according to the subscription for the analytics. At block <NUM>, the terminal device <NUM> transmits a request comprising the analytics identity to a Session Management Function (SMF) or an Application Function (AF). At block <NUM>, the terminal device <NUM> receives analytics result data from the SMF or the AF, according to the analytics identity after authorization of the request.

In some embodiments, the terminal device is caused to transmit the subscription with the analytics identity by: transmitting the subscription with the analytics identity to the UDM through the AF, a Customer Relationship Management (CRM), or a portal, and / or the terminal device is caused to receive the subscribed analytics identity by: receiving the subscribed analytics identity from the UDM through a UE Parameter Update (UPU) procedure.

In some embodiments, the terminal device is caused to transmit the request by: setting up a Protocol Data Unit (PDU) session with the SMF, transmitting the request comprising the analytics identity to the SMF with the PDU session through an Access and Mobility Management Function (AMF), or transmitting a Hyper Text Transfer Protocol (HTTP) request comprising the analytics identity to the AF.

In some embodiments, the authorization is implemented in the UDM or in a Network Repository Function based on terminal device information and associated information.

In some embodiments, the analytics is an artificial intelligence (AI) / machine learning (ML) logic or AI / ML service or AI / ML model running in a <NUM> core network; the analytics identity is an identity of the analytics, to invoke a relevant application in the <NUM> core network,.

<FIG> illustrates a flowchart of a method implemented at a Unified Data Management (UDM) according to some embodiments of the present disclosure. For the purpose of discussion, the method <NUM> will be described from the perspective of the UDM <NUM> with reference to <FIG>, <FIG>.

At block <NUM>, the UDM <NUM> receives, a subscription for an analytics with an analytics identity from a terminal device. At block <NUM>, in response to receiving the subscription for the analytics, the UDM <NUM> registers a terminal device information in the UDM, along with Public Land Mobile Network (PLMN) information and slice information associated with the terminal device. At block <NUM>, the UDM <NUM> transmits a subscribed analytics identity to the terminal device.

In some embodiments, the terminal device information comprises at least one of: a terminal device identity, the analytics identity, at least one supported slice identity per analytics identity, and at least one supported PLMN identity per analytics identity.

In some embodiments, the UDM <NUM> is further caused to: receive a request for a terminal device information associated with the analytics identity and the terminal device identity from a Network Repository Function (NRF), or from a Network Data Analytics Function (NWDAF), in response to receiving the request for the terminal device information, transmit the terminal device information to the NRF, or the NWDAF.

<FIG> illustrates a flowchart of a method implemented at a Network Repository Function (NRF) according to some embodiments of the present disclosure. For the purpose of discussion, the method <NUM> will be described from the perspective of the NRF <NUM> with reference to <FIG>, and <FIG>.

At block <NUM>, the NRF <NUM> receives, an access token request comprising a terminal device identity, a slice identity, and at least one analytics identity, from a Session Management Function (SMF) or an Application Function (AF). At block <NUM>, the NRF <NUM> gets, from a Unified Data Management (UDM), a terminal device information associated with the analytics identity and the terminal device identity. At block <NUM>, the NRF <NUM> verifies based on the got terminal device information, whether the terminal device is authorized to receive the analytics identity. At block <NUM>, in response to success of the verification with the got terminal device information, the NRF <NUM> transmits an access token with the terminal device identity, the slice identity, and the analytics identity, to the SMF or the AF.

In some embodiments, the NRF <NUM> is caused to get the terminal device information by: transmitting, to the UDM, a request for the terminal device information, wherein the request comprised an analytics identity and a terminal device identity, receiving, from the UDM, the terminal device information, wherein the terminal device information comprises the terminal device identity, the analytics identity, at least one supported slice identity per analytics identity, and at least one supported Public Land Mobile Network (PLMN) identity per analytics identity.

<FIG> illustrates a flowchart of a method implemented at a Network Data Analytics Function (NWDAF) according to some embodiments of the present disclosure. For the purpose of discussion, the method <NUM> will be described from the perspective of the NWDAF <NUM> with reference to <FIG>, <FIG>.

At block <NUM>, the NWDAF <NUM> receives, a service request with an analytics identity from a Session Management Function (SMF) or an Application Function (AF). At block <NUM>, the NWDAF <NUM> transmits analytics result data to the SMF or the AF, according to the analytics identity after authorization of the service request.

In some embodiments, before transmitting the analytics result data, the NWDAF <NUM> is further caused to: verifying an access token with a terminal device identity and the analytics identity, in response to the success of verifying the access token, transmitting the analytics result data to the SMF, wherein the service request comprises the access token.

In some embodiments, before transmitting the analytics result data, the NWDAF <NUM> is further caused to: transmitting a request for a terminal device information associated with an analytics identity and a terminal device identity to a Unified Data Management (UDM), receiving the terminal device information from the UDM, wherein the terminal device information comprises an analytics identity, a terminal device identity, at least one supported slice identity per analytics identity, and at least one supported Public Land Mobile Network (PLMN) identity per analytics identity, verifying the authorization of the analytics identity and the terminal device identity, in response to the success of verifying the authorization, transmitting the analytics result data to the SMF or the AF.

<FIG> illustrates a flowchart of a method implemented at a Session Management Function (SMF) according to some embodiments of the present disclosure. For the purpose of discussion, the method <NUM> will be described from the perspective of the SMF <NUM> with reference to <FIG>.

At block <NUM>, the SMF <NUM> receives a request with an analytics identity from a terminal device. At block <NUM>, the SMF <NUM> transmits, to a Network Data Analytics Function (NWDAF), a service request comprising the analytics identity. At block <NUM>, the SMF <NUM> receives, from the NWDAF, analytics result data, according to the service request. At block <NUM>, the SMF <NUM> transmits the analytics result data to the terminal device.

In some embodiments, before transmitting the service request to the NWDAF, the SMF <NUM> is further caused to: transmitting, to a Network Repository Function (NRF), an access token request with a terminal device identity, a slice identity, and the analytics identity, receiving from the Network Repository Function, an access token with the terminal device identity, the slice identity, and the analytics identity, according to the access token request. The SMF <NUM> then adds the received access token into the service request to be transmitted to the NWDAF.

<FIG> illustrates a flowchart of a method implemented at an Application Function (AF) according to some embodiments of the present disclosure. For the purpose of discussion, the method <NUM> will be described from the perspective of the AF <NUM> with reference to <FIG>.

At block <NUM>, the AF <NUM> receives, a request with an analytics identity from a terminal device. At block <NUM>, the AF <NUM> transmits, to a Network Data Analytics Function (NWDAF), a service request comprising the analytics identity. At block <NUM>, the AF <NUM> receives, from the NWDAF, analytics result data according to the service request. At block <NUM>, the AF <NUM> transmits, to the terminal device, the analytics result data.

In some embodiments, before transmitting the service request, the AF <NUM> is further caused to: transmitting, to a Network Repository Function (NRF), an access token request with a terminal device identity, a slice identity, and the analytics identity, receiving, from the NRF, the access token with the terminal device identity, the slice identity, and the analytics identity, according to the access token request. The AF <NUM> adds the received access token into the service request to be transmitted to the NWDAF.

In some embodiments, the AF <NUM> is a trusted AF, or the AF is a Network Exposure Function (NEF).

In some embodiments, an apparatus capable of performing any of the method <NUM> (for example, the terminal device <NUM>) may comprise means for performing the respective steps of the method <NUM>. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

In some embodiments, the apparatus comprises means for transmitting a subscription for an analytics with an analytics identity to a Unified Data Management (UDM), means for receiving a subscribed analytics identity from the UDM, according to the subscription for the analytics, means for transmitting a request comprising the analytics identity to a Session Management Function (SMF) or an Application Function (AF), and means for receiving analytics result data from the SMF or the AF, according to the analytics identity after authorization of the request.

In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method <NUM>. In some embodiments, the means comprises at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

In some embodiments, an apparatus capable of performing any of the method <NUM> (for example, the UDM <NUM>) may comprise means for performing the respective steps of the method <NUM>. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

In some embodiments, the apparatus comprises means for receiving, a subscription for an analytics with an analytics identity from a terminal device, means for in response to receiving the subscription for the analytics, registering a terminal device information in the UDM, along with Public Land Mobile Network (PLMN) information and slice information associated with the terminal device, means for transmitting a subscribed analytics identity to the terminal device.

In some embodiments, an apparatus capable of performing any of the method <NUM> (for example, the NRF <NUM>) may comprise means for performing the respective steps of the method <NUM>. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

In some embodiments, the apparatus comprises means for means for receiving, an access token request comprising a terminal device identity, a slice identity, and at least one analytics identity, from a Session Management Function (SMF) or an Application Function (AF), means for getting, from a Unified Data Management, a terminal device information associated with the analytics identity and the terminal device identity, means for verifying based on the got terminal device information, whether the terminal device is authorized to receive the analytics identity, means for in response to success of the verification with the got terminal device information, transmitting an access token with the terminal device identity, the slice identity, and the analytics identity, to the SMF or the AF.

In some embodiments, an apparatus capable of performing any of the method <NUM> (for example, the NWDAF <NUM>) may comprise means for performing the respective steps of the method <NUM>. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

In some embodiments, the apparatus comprises means for receiving a service request with an analytics identity from a Session Management Function (SMF) or an Application Function (AF), means for transmitting analytics result data to the SMF or an AF, according to the analytics identity after authorization of the service request.

In some embodiments, an apparatus capable of performing any of the method <NUM> (for example, the SMF <NUM>) may comprise means for performing the respective steps of the method <NUM>. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

In some embodiments, the apparatus comprises means for receiving a request with an analytics identity from a terminal device, means for transmitting, to a Network Data Analytics Function (NWDAF), a service request comprising the analytics identity, means for receiving, from the NWDAF, analytics result data, according to the service request, means for transmitting the analytics result data to the terminal device.

In some embodiments, an apparatus capable of performing any of the method <NUM> (for example, the AF <NUM>) may comprise means for performing the respective steps of the method <NUM>. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

In some embodiments, the apparatus comprises means for receiving a request with an analytics identity from a terminal device, means for transmitting, to a Network Data Analytics Function (NWDAF), a service request comprising the analytics identity, means for receiving, from the NWDAF, analytics result data according to the service request, according to the service request, means for transmitting, to the terminal device, the analytics result data.

<FIG> is a simplified block diagram of a device <NUM> that is suitable for implementing embodiments of the present disclosure. The device <NUM> may be provided to implement the terminal device or the network functions, for example the TD <NUM>, the AMF <NUM>, the SMF <NUM>, the NRF <NUM>, the UDM <NUM>, the NWDAF <NUM>, and the AF <NUM> as shown in <FIG>, <FIG>. As shown, the device <NUM> includes one or more processors <NUM>, one or more memories <NUM> coupled to the processor <NUM>, and one or more transmitters and/or receivers (TX/RX) <NUM> coupled to the processor <NUM>.

The TX/RX <NUM> is for bidirectional communications. The communication interface may represent any interface that is necessary for communication with other network functions.

In some embodiments, the program <NUM> may be tangibly contained in a computer readable medium which may be included in the device <NUM> (such as in the memory <NUM>) or other storage devices that are accessible by the device <NUM>.

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 program modules, being executed in a device on a target real or virtual processor, to carry out the method <NUM> as described above with reference to <FIG>. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

Claim 1:
A terminal device (<NUM>; <NUM>), comprising:
at least one processor (<NUM>); and
at least one memory (<NUM>) including computer program codes;
the at least one memory and the computer program codes are configured to, with the at least one processor, cause the terminal device to:
transmit, a subscription for an analytics with an analytics identity to a Unified Data Management, UDM, (<NUM>)
receive a subscribed analytics identity from the UDM, according to the subscription for the analytics,
transmit a request comprising the analytics identity to a Session Management Function, SMF, (<NUM>) or an Application Function, AF, (<NUM>) and
receive analytics result data from the SMF or the AF, according to the analytics identity after authorization of the request.