Network node and communication method

Abstract

This network node comprises: a transmission unit that transmits, to another network node, a first message for requesting subscriber information including at least one of information indicating user consent for abnormality analysis and information indicating user consent for the training of an abnormality detection model; and a reception unit that receives, from the other network node, a second message including the requested subscriber information and information including whether user consent is given.

Description

Network Node and Communication Method

[0001] The present invention relates to a network node and a communication method in a communication system.

[0002] In 3GPP (Registered Trademark) (3rd Generation Partnership Project), in order to achieve further increases in system capacity, further increases in data transmission speed, further reduction in latency in the radio section, etc., a radio communication method called 5G or NR (New Radio) (hereinafter, this radio communication method is referred to as "5G" or "NR") is being studied. In 5G, various radio technologies are being studied in order to meet the requirement of achieving a throughput of 10 Gbps or more while reducing the latency in the radio section to 1 ms or less.

[0003] Also, the network architecture in 5GC (5G Core Network) or 5GS (5G System), which is the core network in 5G, and in 6GC (6G Core Network) or 6GS (6G System), which is the successor to 5G, is also being studied (for example, Non-Patent Document 1).

[0004] Also, in 3GPP, a mechanism for optimizing by utilizing artificial intelligence (AI) is being studied as a countermeasure against abnormal behavior in terminals and networks (for example, the occurrence of an abnormally excessive control signal (signalling storm)). To utilize AI, various data (for example, the signal amount and connection pattern of a terminal, etc.) are required for machine learning model formation and AI inference.

[0005] 3GPP TS 23.501 V18.7.0 (2024-09) 3GPP TR 23.700-84 V2.0.0 (2024-09) 3GPP TS 23.288 V18.7.0 (2024-09) 3GPP TS 29.503 V18.7.0 (2024-09) 3GPP TS 29.520 V18.7.0 (2024-09)

[0006] In the use of data necessary for utilizing artificial intelligence (AI), user consent may be required. Non-patent document 3 here stipulates a mechanism in which users (subscriber information) grant permission for data use from the perspective of protecting personal information, depending on "for what purpose the data will be used" and "for what purpose the data will be collected."

[0007] However, this system makes it difficult to reflect the user's intentions and fails to achieve the purpose of user permission.

[0008] This invention has been made in view of the above points, and aims to introduce a mechanism that reflects the user's intentions in user permission for data use in wireless communication networks.

[0009] According to the disclosed technology, a network node is provided having: a transmitting unit that transmits a first message to another network node requesting subscriber information, which includes at least one of information indicating user permission for anomaly analysis and information indicating user permission for training an anomaly detection model; and a receiving unit that receives a second message from the other network node, which includes the requested subscriber information and information indicating whether or not user permission has been granted.

[0010] According to the disclosed technology, a mechanism can be introduced to reflect the user's intentions in user permission for data use in wireless communication networks.

[0011] This is a diagram illustrating an example of a communication system. This is a diagram illustrating an example of a communication system in a roaming environment. This is a diagram illustrating the processing related to "UcPurpose extension" in an embodiment of the present invention. This is a diagram illustrating the processing related to "UserConsent extension" in an embodiment of the present invention. This is a diagram illustrating the processing when some of the permissions are denied in an embodiment of the present invention. This is a diagram illustrating the processing when all of the permissions are denied in an embodiment of the present invention. This is a diagram illustrating the processing when the permission is revoked in an embodiment of the present invention. This is a diagram showing an example of the functional configuration of the base station 10 and network node 30 in an embodiment of the present invention. This is a diagram showing an example of the functional configuration of the terminal 20 in an embodiment of the present invention. This is a diagram showing an example of the hardware configuration of the base station 10, terminal 20, and network node 30 in an embodiment of the present invention. This is a diagram showing an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

[0012] Embodiments of the present invention will be described below with reference to the drawings. The embodiments described below are examples, and the embodiments to which the present invention applies are not limited to those described below. Furthermore, in the following description, " / " means "and / or" unless otherwise specified, or unless it is clear from the context that it has a different meaning.

[0013] In the operation of the wireless communication system according to the embodiments of the present invention, existing technologies may be used as appropriate. However, such existing technologies include, for example, existing LTE, but are not limited to existing LTE. Furthermore, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced, LTE-Advanced and later technologies (e.g., NR), or wireless LAN (Local Area Network), unless otherwise specified.

[0014] Furthermore, in the embodiments of the present invention, "configuring" wireless parameters, etc., may mean that predetermined values ​​are pre-configured, or that wireless parameters notified from the network node 30 or terminal 20 are configured.

[0015] Figure 1 is a diagram illustrating an example of a communication system. As shown in Figure 1, the communication system consists of a terminal 20 (UE) and multiple network nodes 30. Hereafter, one network node 30 will be assumed to correspond to each function, but one network node 30 may implement multiple functions, or multiple network nodes 30 may implement one function. Also, the "connection" described below may be a logical connection or a physical connection.

[0016] The RAN (Radio Access Network) is a network node 30 having wireless access functionality, which may include a base station 10, and is connected to a UE, AMF (Access and Mobility Management Function), and UPF (User plane function). The AMF is a network node 30 having functions such as terminating the RAN interface, terminating the NAS (Non-Access Stratum), registration management, connection management, reachability management, and terminal mobility management. The UPF is a network node 30 interconnected with the DN (Data Network) and having functions related to processing user plane data, such as a PDU (Protocol Data Unit) session point to the outside, packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and DN constitute a network slice. In the wireless communication network in the embodiment of the present invention, a plurality of network slices are constructed.

[0017] AMF is connected to UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), PCF (Policy Control Function), and AF (Application Function). AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0018] The SMF is a network node 30 that has functions such as session management, IP (Internet Protocol) address allocation and management for UEs, DHCP (Dynamic Host Configuration Protocol) functionality, ARP (Address Resolution Protocol) proxy, and roaming functionality. The NEF is a network node 30 that has the function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node 30 that has functions such as selecting the network slice to which the UE connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be set, and determining the AMF set to which the UE connects. The PCF is a network node 30 that has the function of controlling network policies. The AF is a network node 30 that has the function of controlling application servers. The NRF is a network node 30 that has the function of discovering NF instances that provide services. The UDM is a network node 30 that manages subscriber data and authentication data. The UDM is connected to the UDR (User Data Repository) that holds the said data.

[0019] Figure 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Figure 2, the network consists of a terminal 20 (UE) and multiple network nodes 30. Hereafter, one network node 30 will be assigned to each function, but one network node 30 may implement multiple functions, or multiple network nodes 30 may implement one function. Also, the "connection" described below may be a logical connection or a physical connection.

[0020] The RAN is a network node 30 having wireless access functionality and is connected to the UE, AMF, and UPF. The AMF is a network node 30 having functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 interconnected with the DN, having functions such as external PDU session point, packet routing and forwarding, and user plane QoS handling. The UPF and DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.

[0021] AMF is connected to UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy). AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0022] SMF is a network node 30 that has functions such as session management, IP address allocation and management for UEs, DHCP functionality, ARP proxy, and roaming functionality. NEF is a network node 30 that has the function of notifying other NFs of capabilities and events. NSSF is a network node 30 that has functions such as selecting the network slice to which the UE connects, determining which NSSAIs are allowed, determining which NSSAIs are configured, and determining which AMF set the UE connects to. PCF is a network node 30 that has the function of controlling network policies. AF is a network node 30 that has the function of controlling application servers. NRF is a network node 30 that has the function of discovering NF instances that provide services. SEPP is an opaque proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). In Figure 2, vSEPP is the SEPP in the visited network, and hSEPP is the SEPP in the home network.

[0023] As shown in Figure 2, the UE is in a roaming environment connected to the RAN and AMF in the Visited PLMN. The Visited PLMN and Home PLMN are connected via vSEPP and hSEPP. The UE can communicate with the UDM of the Home PLMN, for example, via the AMF of the Visited PLMN.

[0024] The following describes how to implement a mechanism that reflects the user's wishes in user permission for data use in wireless communication networks.

[0025] Regarding abnormal behavior in terminals and networks, such as the generation of excessively high signaling signals (signalling storms), if a user refuses to have their location information collected and their lifestyle patterns analyzed or inferred (e.g., user behavior analytics such as UE velocity), but allows the use of that data to have AI detect that the terminal has been hacked and is behaving abnormally (for signalalling storm analytics purposes), the existing specifications cannot accommodate this. In the existing specifications, there are only two purposes that can be specified for signalalling storms: "ANALYTICS" and "MODEL_TRAINING". If a user permits "ANALYTICS" or "MODEL_TRAINING" for the purpose of signalalling storms, it will be assumed that they have also uniformly permitted other use cases (e.g., user behavior analytics such as UE velocity) regardless of their intentions.

[0026] The following describes a new type of user license related to signaling storm and two methods for obtaining user licenses (Method 1 and Method 2).

[0027] Method 1 is a method for obtaining user consent regarding the detection and prediction of abnormal behavior (signalling storms) between an NWDAF (Network Data Analytics Function) including an Analytics Logical Function and a UDM (Ndum).

[0028] Method 2 is a method for processing based on acquired user consent between network functions such as AMF and NWDAF (Nnwdaf).

[0029] (Method 1) Method 1 includes a method using "UcPurpose extension" which extends the information indicating the purpose (Method 1-1), and a method using "UserConsent extension" which extends the information indicating user consent (Method 1-2). For processing and messages in the existing specifications of this method, please refer to Non-Patent Document 4.

[0030] (Method 1-1) Figure 3 is a diagram illustrating the process related to "UcPurpose extension" in an embodiment of the present invention. In step 1 of the sequence diagram shown in Figure 3, an NF service consumer 30A such as an NWDAF sends a message to the UDM 30B requesting user-authorized subscriber information (UcSubscriptionData). In response to this request, in step 2a, the UDM 30B sends a message to the NF service consumer 30A containing the said subscriber information (UcSubscriptionData). This message includes information regarding whether or not user authorization has been granted.

[0031] Here, as shown in Figure 3, 300, the message in step 1 may include extended information (ANOMALY_ANALYTICS / ANOMALY_MODEL_TRAINING) that explicitly indicates that the data is being used in a signaling storm, as an "UcPurpose extension" that expands the information indicating the purpose. ANOMALY_ANALYTICS is information indicating user consent for abnormal analytics, and ANOMALY_MODEL_TRAINING is information indicating user consent for abnormal detection model training.

[0032] (Method 1-2) Figure 4 is a diagram illustrating the process related to "UserConsent extension" in an embodiment of the present invention. In step 1 of the sequence diagram shown in Figure 4, an NF service consumer 30A such as an NWDAF sends a message to the UDM 30B requesting user-authorized subscriber information (UcSubscriptionData). In response to this request, in step 2a, the UDM 30B sends a message to the NF service consumer 30A containing the said subscriber information (UcSubscriptionData). This message includes information regarding whether or not user consent has been given.

[0033] Here, as shown in 301 of Figure 4, the message in step 2a may include extended information (CONSENT_NOT_GIVEN_ANOMALY or CONSENT_GIVEN_ANOMALY) that explicitly indicates that the data is being used in a signaling storm, as an extended "UserConsent extension" that extends the information indicating user consent. CONSENT_NOT_GIVEN_ANOMALY indicates that user consent for abnormal detection has not been given, while CONSENT_GIVEN_ANOMALY indicates that user consent for abnormal detection has been given.

[0034] (Method 2) Method 2 includes methods for cases where some licenses are denied (Method 2-1), cases where all licenses are denied (Method 2-2), and cases where licenses are revoked (Method 2-3). For processing and messages in the existing specifications of these methods, please refer to Non-Patent Document 5.

[0035] (Method 2-1) Figure 5 is a diagram illustrating the process when some of the permissions in the embodiment of the present invention are denied. In step 1 of the sequence diagram shown in Figure 5, an NF service consumer 30A such as AMF sends a message to NWDAF 30C requesting subscriptions for event notifications related to data analysis, etc. In response to this request, in step 2, NWDAF 30C sends a message to NF service consumer 30A containing information indicating that the requested subscriptions have been created.

[0036] Here, as shown in Figure 5, 303, in step 2, if not all of the requested analysis events are not permitted, NWDAF30C may notify by including the failEventReports attribute in the NwdafFailureCode(201) message indicating that user permission failed for some of the events.

[0037] Furthermore, as shown in Figure 5, 304, the message in step 2 may include information indicating that user permission has not been granted (USER_CONSENT_NOT_GRANTED) / information indicating that user permission regarding the detection of abnormal behavior has not been granted (ANOMALY_USER_CONSENT_NOT_GRANTED).

[0038] (Method 2-2) Figure 6 is a diagram illustrating the processing when all permissions in an embodiment of the present invention are denied. In step 1 of the sequence diagram shown in Figure 6, an NF service consumer 30A such as AMF sends a message to NWDAF 30C requesting subscriptions to event notifications related to data analysis, etc. In response to this request, in step 2, as shown in 305 of Figure 6, NWDAF 30C may send a message (error response to the request) that includes a reason (cause) indicating that user permission has not been obtained, since user permission has not been obtained for the requested data analysis, etc. The message may include information indicating that user permission for anomaly detection has not been obtained (ANOMALY_USER_CONSENT_NOT_GRANTED) as the reason, as shown in 306 of Figure 6.

[0039] (Method 2-3) Figure 7 is a diagram illustrating the processing when the license is revoked in an embodiment of the present invention. As a premise, NWDAF30C receives a message from an NF service consumer 30A such as MF requesting subscriptions for event notifications related to data analysis on data for which user permission for anomaly detection has been granted, and sends a message to the NF service consumer 30A containing information indicating that the requested subscription has been created. Furthermore, it is assumed that the data related to the created subscription has been for which user permission for anomaly detection has been granted.

[0040] In step 1 of the sequence diagram shown in Figure 7, as shown in 307 of Figure 7, if the aforementioned user license is revoked, NWDAF30C may send a message to NF service consumer30A notifying that the user license has been revoked. This message may include information indicating that the user license for anomaly detection has been revoked (ANOMALY_USER_CONSENT_REVOKED), as shown in 308 of Figure 7.

[0041] (Behavior 1 to Behavior 12) The behaviors based on the information obtained by dm, as explained in the first to twelfth behaviors of Nu by AMF, are described below.

[0042] The first behavior in this embodiment is the behavior in which AMF determines whether to request signaling storm analytics from NWDAF based on user permission information regarding data usage obtained from UDM. In the first behavior, AMF obtains user permission information regarding data usage from UDM via the Nudm_SDM service API with the query parameter uc-purpose set to "ANALYTICS". If both data usage in signaling storm analytics and data usage outside of signaling storm analytics are not permitted, AMF may skip requesting signaling storm analytics (related to the user in question) using the relevant data (it does not need to request it from NWDAF).

[0043] The second behavior in this embodiment is the behavior in which AMF determines whether to request signaling storm analytics from NWDAF based on user permission information regarding data usage obtained from UDM. In the second behavior, AMF obtains user permission information regarding data usage from UDM via the Nudm_SDM service API with the query parameter uc-purpose set to "ANALYTICS". If data usage for signaling storm analytics is not permitted but data usage for other services is permitted, AMF may send a request for services other than signaling storm analytics to NWDAF. AMF may also subscribe to change notifications for permission information regarding data usage other than signaling storm analytics (if not already subscribed). Subscribing to change notifications may mean subscribed to change notifications for permission information regarding data usage other than signaling storm analytics by targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation.

[0044] The third behavior in this embodiment is the behavior in which the AMF determines whether to request signalling storm analytics from the NWDAF based on the user permission information regarding data usage obtained from the UDM. In the third behavior, the AMF obtains the user permission information regarding data usage from the UDM via the Nudm_SDM service API with the query parameter uc-purpose set to "ANALYTICS". If the data usage in signalling storm analytics is permitted but the data usage other than signalling storm analytics is not permitted, the AMF may send a request regarding signalling storm analytics to the NWDAF. Also, the AMF may subscribe to the change notification of the permission information regarding the data usage in signalling storm analytics (if it has not already subscribed). Subscribing to the change notification may mean subscribing to the change notification of the permission information regarding the data usage in signalling storm analytics by targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation.

[0045] The fourth behavior in this embodiment is the behavior in which the AMF determines whether to request signalling storm analytics from the NWDAF based on the user permission information regarding data usage obtained from the UDM. In the fourth behavior, the AMF obtains the user permission information regarding data usage from the UDM via the Nudm_SDM service API with the query parameter uc-purpose set to "MODEL_TRAINING". If neither the data usage in signalling storm analytics nor the data usage other than signalling storm analytics is permitted, the AMF may skip the request for signalling storm analytics using the corresponding data (not request it from the NWDAF) related to the corresponding user.

[0046] The fifth behavior in this embodiment is the behavior in which AMF determines whether to request signaling storm analytics from NWDAF based on user permission information regarding data usage obtained from UDM. In the fifth behavior, AMF obtains user permission information regarding data usage from UDM via the Nudm_SDM service API with the query parameter uc-purpose set to "MODEL_TRAINING". If data usage for signaling storm analytics is not permitted but data usage for other services is permitted, AMF may send a request for services other than signaling storm analytics to NWDAF. AMF may also subscribe to change notifications for permission information regarding data usage other than signaling storm analytics (if not already subscribed). Subscribing to change notifications may mean subscribed to change notifications for permission information regarding data usage other than signaling storm analytics by targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation.

[0047] The sixth behavior in this embodiment is the behavior in which the AMF determines whether to request signalling storm analytics from the NWDAF based on the user permission information regarding data usage obtained from the UDM. In the sixth behavior, the AMF obtains the user permission information regarding data usage from the UDM via the Nudm_SDM service API with the query parameter uc-purpose set to "MODEL_TRAINING". If data usage in signalling storm analytics is permitted but data usage other than signalling storm analytics is not permitted, the AMF may send a request regarding signalling storm analytics to the NWDAF. Also, the AMF may subscribe to the change notification of the permission information regarding data usage in signalling storm analytics (if it has not already subscribed). Subscribing to the change notification may mean subscribing to the change notification of the permission information regarding data usage in signalling storm analytics by targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation.

[0048] The seventh behavior in this embodiment is the behavior in which the AMF determines whether to request signalling storm analytics from the NWDAF based on the user permission information regarding data usage obtained from the UDM. In the seventh behavior, the AMF obtains the user permission information regarding data usage from the UDM via the Nudm_SDM service API with the query parameter uc-purpose set to the second information. If neither data usage in signalling storm analytics nor data usage other than signalling storm analytics is permitted, the AMF may skip the request for signalling storm analytics using the corresponding data (it does not have to request it from the NWDAF).

[0049] The eighth behavior in this embodiment is the behavior in which AMF determines whether to request signaling storm analytics from NWDAF based on user permission information regarding data usage obtained from UDM. In the eighth behavior, AMF obtains user permission information regarding data usage from UDM via the Nudm_SDM service API with the query parameter uc-purpose set to the second information, and if data usage for signaling storm analytics is not permitted but data usage for other services is permitted, AMF may send a request for services other than signaling storm analytics to NWDAF. AMF may also subscribe to change notifications for permission information regarding data usage other than signaling storm analytics (if not already subscribed). Subscribing to change notifications may mean subscribed to change notifications for permission information regarding data usage other than signaling storm analytics by targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation.

[0050] The ninth behavior in this embodiment is the behavior in which AMF determines whether to request signaling storm analytics from NWDAF based on user permission information regarding data usage obtained from UDM. In the ninth behavior, AMF obtains user permission information regarding data usage from UDM via the Nudm_SDM service API with the query parameter uc-purpose set to the second information, and if data usage for signaling storm analytics is permitted but data usage for other purposes is not permitted, AMF may send a request for signaling storm analytics to NWDAF. AMF may also subscribe to notifications of changes to the permission information regarding data usage for signaling storm analytics (if not already subscribed). Subscribing to change notifications may mean subscribed to notifications of changes to the permission information regarding data usage for signaling storm analytics by targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation.

[0051] The tenth behavior in this embodiment is the behavior in which AMF determines whether to request signaling storm analytics from NWDAF based on user permission information regarding data usage obtained from UDM. In the tenth behavior, AMF obtains user permission information regarding data usage from UDM via the Nudm_SDM service API, where the query parameter uc-purpose is set to the first information. If both data usage in signaling storm analytics and data usage outside of signaling storm analytics are not permitted, AMF may skip requesting signaling storm analytics (related to the user) using the relevant data (it does not need to request it from NWDAF).

[0052] The eleventh behavior in this embodiment is the behavior in which AMF determines whether to request signaling storm analytics from NWDAF based on user permission information regarding data usage obtained from UDM. In the eleventh behavior, AMF obtains user permission information regarding data usage from UDM via the Nudm_SDM service API with the query parameter uc-purpose set to the first information, and if data usage for signaling storm analytics is not permitted but data usage for other services is permitted, AMF may send a request for services other than signaling storm analytics to NWDAF. AMF may also subscribe to change notifications for permission information regarding data usage other than signaling storm analytics (if not already subscribed). Subscribing to change notifications may mean subscribed to change notifications for permission information regarding data usage other than signaling storm analytics by targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation.

[0053] The twelfth behavior in this embodiment is the behavior in which AMF determines whether to request signaling storm analytics from NWDAF based on user permission information regarding data usage obtained from UDM. In the twelfth behavior, AMF obtains user permission information regarding data usage from UDM via the Nudm_SDM service API with the query parameter uc-purpose set to the first information, and if data usage for signaling storm analytics is permitted but data usage for other purposes is not permitted, AMF may send a request for signaling storm analytics to NWDAF. AMF may also subscribe to notifications of changes to the permission information regarding data usage for signaling storm analytics (if not already subscribed). Subscribing to change notifications may mean subscribed to notifications of changes to the permission information regarding data usage for signaling storm analytics by targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation.

[0054] The use of data in signaling storm analytics, as described in the first through twelfth behaviors, can be interpreted as data usage when the Analytics ID requested by AMF from NWDAF is "Signalling Storm". The use of data outside of signaling storm analytics can be interpreted as data usage when the Analytics ID requested by AMF from NWDAF is anything other than "Signalling Storm".

[0055] Furthermore, the information indicating permission for data use in signaling storm analytics, as described in the first to twelfth behaviors, may be, for example, the information in the twelfth behavior. The information indicating that permission is not granted when data use in signaling storm analytics is not granted may be, for example, the information in the eleventh behavior. If data use is permitted outside of signaling storm analytics, this may be indicated by "CONSENT_GIVEN," and if data use is not permitted outside of signaling storm analytics, this may be indicated by "CONSENT_NOT_GIVEN." In addition, the information regarding user permission in signaling storm analytics may be information indicating whether or not user permission has been granted in signaling storm analytics, and is not limited to the information in the eleventh or twelfth behavior.

[0056] Furthermore, the distinction between requests to NWDAF that are not related to signaling storm analytics, as described in the first to twelfth behaviors, and requests related to signaling storm analytics may be made based on the Analytics ID included in the request.

[0057] Furthermore, the query parameter uc-purpose, as described in the first through twelfth behaviors, may be information indicating the user licensing purpose that AMF includes when obtaining user licensing information from UDM.

[0058] Furthermore, in requests to obtain user permission information regarding data usage from the UDM, as described in the first through twelfth behaviors, multiple uc-purpose values ​​may be included at once. For example, the first information may be set in uc-purpose value #1, and "MODEL_TRAINING" may be set in uc-purpose value #2.

[0059] Furthermore, user permission information regarding the use of data obtained from the UDM, as described in the first through twelfth behaviors, may be included in and shown in UserConsent.

[0060] Furthermore, the user consent information regarding data usage obtained from the UDM, as described in the first through twelfth behaviors, may include multiple UserConsent values ​​at once. For example, UserConsent value #1 may contain the twelfth piece of information indicating that data usage in signaling storm analytics is permitted, while UserConsent value #2 may be set to "CONSENT_NOT_GIVEN," indicating that data usage outside of signaling storm analytics is not permitted.

[0061] Up to this point, the procedures described in the first through twelfth behaviors have been for AMF to send uc-purpose as a query parameter to UDM. However, the query parameter that AMF sends to UDM is not limited to uc-purpose. As described in the 61st behavior, AMF may also send uc-purpose / analytics information to UDM. In this case, UDM may query user permission information based on the uc-purpose / analytics information and respond to AMF. For example, if AMF uses the uc-purpose / analytics information set as the query parameter "ANALYTICS" to obtain user permission information regarding data usage from UDM via the Nudm_SDM service API, and this user permission information includes analytics information for which user permission has not been granted and analytics information for which user permission has been granted, AMF may subscribe to notifications of changes in permission information regarding the analytics information for which user permission has been granted. Similarly, if AMF obtains user permission information regarding data usage from UDM via the Nudm_SDM service API using the uc-purpose / analytics information set as the query parameter "MODEL_TRAINING", and the user permission information includes analytics information for which user permission has not been granted and analytics information for which user permission has been granted, AMF may subscribe to notifications of changes in permission information regarding the analytics information for which user permission has been granted. Similarly, if AMF obtains user permission information regarding data usage from UDM via the Nudm_SDM service API using the uc-purpose / analytics information set as the second query parameter, and the user permission information includes analytics information for which user permission has not been granted and analytics information for which user permission has been granted, AMF may subscribe to notifications of changes in permission information regarding the analytics information for which user permission has been granted.Similarly, if AMF obtains user permission information regarding data usage from UDM via the Nudm_SDM service API using the information set in query parameter 1 and the uc-purpose / analytics information, and if the user permission information includes analytics information for which user permission has not been granted and analytics information for which user permission has been granted, AMF may subscribe to notifications of changes to the permission information regarding the analytics information for which user permission has been granted.

[0062] (Behavior 111 to Behavior 122) The behaviors of SMF based on information obtained by Nudm (Behavior 111 to Behavior 122) will be described. Behavior 111 in this embodiment is the behavior in which SMF decides whether to request signaling storm analytics from NWDAF based on user permission information regarding data usage obtained from UDM. In Behavior 111, SMF obtains user permission information regarding data usage from UDM via the Nudm_SDM service API with the query parameter uc-purpose set to "ANALYTICS", and if both data usage in signaling storm analytics and data usage outside of signaling storm analytics are not permitted, SMF may skip requesting signaling storm analytics using the relevant data (related to the relevant user) (it does not need to request it from NWDAF).

[0063] The 112th behavior in this embodiment is the behavior in which the SMF determines whether to request signaling storm analytics from the NWDAF based on user permission information regarding data usage obtained from the UDM. In the 112th behavior, the SMF obtains user permission information regarding data usage from the UDM via the Nudm_SDM service API with the query parameter uc-purpose set to "ANALYTICS". If data usage for signaling storm analytics is not permitted but data usage for other services is permitted, the SMF may send a request for services other than signaling storm analytics to the NWDAF. The SMF may also subscribe to notifications of changes to permission information regarding data usage other than signaling storm analytics (if it is not already subscribed). Subscribing to change notifications may mean subscribed to notifications of changes to permission information regarding data usage other than signaling storm analytics by targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation.

[0064] The 113th behavior in this embodiment is the behavior in which the SMF determines whether to request signaling storm analytics from the NWDAF based on user permission information regarding data usage obtained from the UDM. In the 113th behavior, the SMF obtains user permission information regarding data usage from the UDM via the Nudm_SDM service API with the query parameter uc-purpose set to "ANALYTICS". If data usage for signaling storm analytics is permitted but data usage for other purposes is not permitted, the SMF may send a request for signaling storm analytics to the NWDAF. The SMF may also subscribe to notifications of changes to the permission information regarding data usage for signaling storm analytics (if it is not already subscribed). Subscribing to notifications of changes means targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation to subscribe to notifications of changes to the permission information regarding data usage for signaling storm analytics.

[0065] The 114th behavior in this embodiment is the behavior in which the SMF determines whether to request signaling storm analytics from the NWDAF based on user permission information regarding data usage obtained from the UDM. In the 114th behavior, the SMF obtains user permission information regarding data usage from the UDM via the Nudm_SDM service API with the query parameter uc-purpose set to "MODEL_TRAINING". If both data usage in signaling storm analytics and data usage outside of signaling storm analytics are not permitted, the SMF may skip requesting signaling storm analytics (related to the user in question) using the relevant data (it does not need to request it from the NWDAF).

[0066] The 115th behavior in this embodiment is the behavior in which the SMF determines whether to request signaling storm analytics from the NWDAF based on user permission information regarding data usage obtained from the UDM. In the 115th behavior, the SMF obtains user permission information regarding data usage from the UDM via the Nudm_SDM service API with the query parameter uc-purpose set to "MODEL_TRAINING". If data usage for signaling storm analytics is not permitted but data usage for other services is permitted, the SMF may send a request for services other than signaling storm analytics to the NWDAF. The SMF may also subscribe to notifications of changes to permission information regarding data usage other than signaling storm analytics (if it is not already subscribed). Subscribing to change notifications may mean subscribed to notifications of changes to permission information regarding data usage other than signaling storm analytics by targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation.

[0067] The 116th behavior in this embodiment is the behavior in which the SMF determines whether to request signaling storm analytics from the NWDAF based on user permission information regarding data usage obtained from the UDM. In the 116th behavior, the SMF obtains user permission information regarding data usage from the UDM via the Nudm_SDM service API with the query parameter uc-purpose set to "MODEL_TRAINING". If data usage for signaling storm analytics is permitted but data usage for other purposes is not permitted, the SMF may send a request for signaling storm analytics to the NWDAF. The SMF may also subscribe to notifications of changes to the permission information regarding data usage for signaling storm analytics (if it is not already subscribed). Subscribing to notifications of changes means targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation to subscribe to notifications of changes to the permission information regarding data usage for signaling storm analytics.

[0068] The 117th behavior in this embodiment is the behavior in which the SMF determines whether to request signaling storm analytics from the NWDAF based on user permission information regarding data usage obtained from the UDM. In the 117th behavior, the SMF obtains user permission information regarding data usage from the UDM via the Nudm_SDM service API, where the query parameter uc-purpose is set to the second information. If both data usage in signaling storm analytics and data usage outside of signaling storm analytics are not permitted, the SMF may skip requesting signaling storm analytics (related to the user in question) using the relevant data (it does not need to request it from the NWDAF).

[0069] The 118th behavior in this embodiment is the behavior in which the SMF determines whether to request signaling storm analytics from the NWDAF based on user permission information regarding data usage obtained from the UDM. In the 118th behavior, the SMF obtains user permission information regarding data usage from the UDM via the Nudm_SDM service API, where the query parameter uc-purpose is set to the second piece of information. If data usage for signaling storm analytics is not permitted, but data usage for services other than signaling storm analytics is permitted, the SMF may send a request for services other than signaling storm analytics to the NWDAF. The SMF may also subscribe to notifications of changes to permission information regarding data usage other than signaling storm analytics (if it is not already subscribed). Subscribing to change notifications may mean targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation to subscribe to notifications of changes to permission information regarding data usage other than signaling storm analytics.

[0070] The 119th behavior in this embodiment is the behavior in which the SMF determines whether to request signaling storm analytics from the NWDAF based on the user permission information regarding data usage obtained from the UDM. In the 119th behavior, the SMF obtains user permission information regarding data usage from the UDM via the Nudm_SDM service API, where the query parameter uc-purpose is set to the second piece of information. If data usage for signaling storm analytics is permitted but data usage for other purposes is not permitted, the SMF may send a request for signaling storm analytics to the NWDAF. The SMF may also subscribe to notifications of changes to the permission information regarding data usage for signaling storm analytics (if it is not already subscribed). Subscribing to notifications of changes means targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation to subscribe to notifications of changes to the permission information regarding data usage for signaling storm analytics.

[0071] The 120th behavior in this embodiment is the behavior in which the SMF determines whether to request signaling storm analytics from the NWDAF based on user permission information regarding data usage obtained from the UDM. In the 120th behavior, the SMF obtains user permission information regarding data usage from the UDM via the Nudm_SDM service API, where the query parameter uc-purpose is set to the first information. If neither data usage in signaling storm analytics nor data usage outside of signaling storm analytics is permitted, the SMF may skip requesting signaling storm analytics (related to the user in question) using the relevant data (it does not need to request it from the NWDAF).

[0072] The 121st behavior in this embodiment is the behavior in which the SMF determines whether to request signaling storm analytics from the NWDAF based on user permission information regarding data usage obtained from the UDM. In the 121st behavior, the SMF obtains user permission information regarding data usage from the UDM via the Nudm_SDM service API, where the query parameter uc-purpose is set to the first information. If data usage is not permitted for signaling storm analytics but is permitted for other uses, the SMF may send a request to the NWDAF for uses other than signaling storm analytics. The SMF may also subscribe to notifications of changes to permission information regarding data usage other than signaling storm analytics (if it is not already subscribed). Subscribing to change notifications may mean subscribed to notifications of changes to permission information regarding data usage other than signaling storm analytics by targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation.

[0073] The 122nd behavior in this embodiment is the behavior in which the SMF determines whether to request signaling storm analytics from the NWDAF based on user permission information regarding data usage obtained from the UDM. In the 122nd behavior, the SMF obtains user permission information regarding data usage from the UDM via the Nudm_SDM service API, where the query parameter uc-purpose is set to the first information. If data usage for signaling storm analytics is permitted but data usage for other purposes is not permitted, the SMF may send a request for signaling storm analytics to the NWDAF. The SMF may also subscribe to notifications of changes to the permission information regarding data usage for signaling storm analytics (if it is not already subscribed). Subscribing to notifications of changes means targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation to subscribe to notifications of changes to the permission information regarding data usage for signaling storm analytics.

[0074] The data usage in signaling storm analytics, as described in behaviors 111 through 122, may be interpreted as data usage when the Analytics ID requested by SMF from NWDAF is "Signalling Storm". The data usage other than signaling storm analytics, as described in behaviors 111 through 122, may be interpreted as data usage when the Analytics ID requested by SMF from NWDAF is anything other than "Signalling Storm".

[0075] Furthermore, the information indicating permission for data use in signaling storm analytics, as described in behaviors 111 through 122, may be, for example, the information in 12. If data use is permitted outside of signaling storm analytics, it may be indicated by "CONSENT_GIVEN," and if data use is not permitted outside of signaling storm analytics, it may be indicated by "CONSENT_NOT_GIVEN." Furthermore, the information indicating that data use in signaling storm analytics is not permitted may be, for example, the information in 11. Information regarding user permission in signaling storm analytics may be information indicating whether or not user permission has been granted in signaling storm analytics, and is not limited to the information in 11 or 12.

[0076] Furthermore, the distinction between requests to NWDAF that are not related to signaling storm analytics, as described in behaviors 111 through 122, and requests related to signaling storm analytics may be made based on the Analytics ID included in the request.

[0077] Furthermore, the query parameter uc-purpose, as described in the behaviors from the 111th to the 122nd, may be information indicating the user licensing purpose that the SMF includes when obtaining user licensing information from the UDM.

[0078] Furthermore, in requests to obtain user permission information regarding data usage from the UDM, as described in behaviors 111 through 122, multiple uc-purpose values ​​may be included at once. For example, the first piece of information may be set in uc-purpose value #1, and "MODEL_TRAINING" may be set in uc-purpose value #2.

[0079] Furthermore, user permission information regarding the use of data obtained from the UDM, as described in behaviors 111 through 122, may be included in UserConsent.

[0080] Furthermore, the user consent information regarding data usage obtained from the UDM, as described in the behaviors from 111 to 122, may include multiple UserConsent values ​​at once. For example, UserConsent value #1 may contain the 12th piece of information indicating that data usage in signaling storm analytics is permitted, while UserConsent value #2 may be set to "CONSENT_NOT_GIVEN" indicating that data usage outside of signaling storm analytics is not permitted.

[0081] Up to this point, in the behaviors described in section 111 through 122, we have explained the procedure by which the SMF sends uc-purpose as a query parameter to the UDM. However, the query parameter that the SMF sends to the UDM is not limited to uc-purpose; as explained in behavior 61, the SMF may also send uc-purpose / analytics information to the UDM. In this case, the UDM may query user permission information based on the uc-purpose / analytics information and respond to the SMF. For example, if the SMF uses the uc-purpose / analytics information set as the query parameter "ANALYTICS" to obtain user permission information regarding data usage from the UDM via the Nudm_SDM service API, and the user permission information includes analytics information for which user permission has not been granted and analytics information for which user permission has been granted, the SMF may subscribe to notifications of changes in permission information regarding the analytics information for which user permission has been granted. Similarly, if SMF retrieves user permission information regarding data usage from UDM via the Nudm_SDM service API using the uc-purpose / analytics information set as the query parameter "MODEL_TRAINING", and the user permission information includes analytics information for which user permission has not been granted and analytics information for which user permission has been granted, SMF may subscribe to notifications of changes to the permission information regarding the analytics information for which user permission has been granted. Similarly, if SMF retrieves user permission information regarding data usage from UDM via the Nudm_SDM service API using the uc-purpose / analytics information set as the second query parameter, and the user permission information includes analytics information for which user permission has not been granted and analytics information for which user permission has been granted, SMF may subscribe to notifications of changes to the permission information regarding the analytics information for which user permission has been granted.Similarly, if SMF obtains user permission information regarding data usage from UDM via the Nudm_SDM service API using the information of query parameter 1 and the configured uc-purpose / analytics information, and if the user permission information includes analytics information for which user permission has not been granted and analytics information for which user permission has been granted, SMF may subscribe to notifications of changes to the permission information regarding the analytics information for which user permission has been granted.

[0082] (Behavior 31 to Behavior 44) This section describes the behaviors (Behavior 31 to Behavior 44) based on the information obtained by Nudm via NWDAF.

[0083] The 31st behavior in this embodiment is the behavior in which NWDAF determines how to respond to an analytics request from an NF consumer based on user permission information. In the 31st behavior, if user permission information regarding data usage is obtained from the UDM via the Nudm_SDM service API with the query parameter uc-purpose set to "ANALYTICS", and if neither data usage in signaling storm analytics nor data usage outside of signaling storm analytics is permitted, NWDAF may send an HTTP "403 Forbidden" error response to the NF consumer with the information from the 23rd example set in the "cause" attribute.

[0084] The 32nd behavior in this embodiment is the behavior in which NWDAF determines how to respond to an analytics request from an NF consumer based on user permission information. In the 32nd behavior, if user permission information regarding data usage is obtained from UDM via the Nudm_SDM service API with the query parameter uc-purpose set to "ANALYTICS", and data usage is not permitted for signaling storm analytics but is permitted for other applications, NWDAF responds with a "201 Created" status code, and the message body may include information about the created subscription. Furthermore, the NwdafFailureCode may be set in the 21st information to indicate the events and reasons for subscription failures, including the "failEventReports" attribute. NWDAF may also subscribe to notifications of changes to permission information regarding data usage other than signaling storm analytics (if not already subscribed). Subscribing to change notifications means targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation to subscribe to change notifications regarding permission information for data usage other than signaling storm analytics.

[0085] The 33rd behavior in this embodiment is the behavior in which NWDAF determines how to respond to an analytics request from an NF consumer based on user permission information. In the 33rd behavior, if user permission information regarding data usage is obtained from UDM via the Nudm_SDM service API with the query parameter uc-purpose set to "ANALYTICS", and data usage is permitted for signaling storm analytics but not for other applications, NWDAF responds with a "201 Created" status code, and the message body may include information about the created subscription. Furthermore, the NwdafFailureCode may be set in the 22nd information to indicate the events and reasons for subscription failures, including the "failEventReports" attribute. NWDAF may also subscribe to notifications of changes to permission information regarding data usage in signaling storm analytics (if not already subscribed). Subscribing to change notifications means targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation to subscribe to change notifications regarding permission information for data usage other than signaling storm analytics.

[0086] The 34th behavior in this embodiment is the behavior in which NWDAF determines how to respond to an analytics request from an NF consumer based on user permission information. In the 34th behavior, if user permission information regarding data usage is obtained from the UDM via the Nudm_SDM service API with the query parameter uc-purpose set to "MODEL_TRAINING", and neither data usage in signaling storm analytics nor data usage outside of signaling storm analytics is permitted, NWDAF may send an HTTP "403 Forbidden" error response to the NF consumer with the information from the 23rd example set in the "cause" attribute.

[0087] The 35th behavior in this embodiment is the behavior in which NWDAF determines how to respond to an analytics request from an NF consumer based on user permission information. In the 35th behavior, NWDAF obtains user permission information regarding data usage from UDM via the Nudm_SDM service API with the query parameter uc-purpose set to "MODEL_TRAINING". If data usage is not permitted for signaling storm analytics but is permitted for other applications, NWDAF responds with a "201 Created" status code, and the message body may include information about the created subscription. Furthermore, the NwdafFailureCode may be set in the 21st information to indicate the events and reasons for subscription failures, including the "failEventReports" attribute. NWDAF may also subscribe to notifications of changes to permission information regarding data usage other than signaling storm analytics (if not already subscribed). Subscribing to change notifications means targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation to subscribe to change notifications regarding permission information for data usage other than signaling storm analytics.

[0088] The 36th behavior in this embodiment is the behavior in which NWDAF determines how to respond to an analytics request from an NF consumer based on user permission information. In the 36th behavior, NWDAF obtains user permission information regarding data usage from UDM via the Nudm_SDM service API with the query parameter uc-purpose set to "MODEL_TRAINING". If data usage is permitted for signaling storm analytics but not for other applications, NWDAF responds with a "201 Created" status code, and the message body may include information about the created subscription. Furthermore, the NwdafFailureCode may be set in the 22nd information to indicate events where the subscription failed and the reason for those failures, including the "failEventReports" attribute. NWDAF may also subscribe to notifications of changes to permission information regarding data usage in signaling storm analytics (if not already subscribed). Subscribing to change notifications means targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation to subscribe to change notifications regarding permission information for data usage other than signaling storm analytics.

[0089] The 37th behavior in this embodiment is the behavior in which NWDAF determines how to respond to an analytics request from an NF consumer based on user permission information. In the 37th behavior, if user permission information regarding data usage is obtained from the UDM via the Nudm_SDM service API with the query parameter uc-purpose set to the second information, and neither data usage in signaling storm analytics nor data usage outside of signaling storm analytics is permitted, NWDAF may send an HTTP "403 Forbidden" error response to the NF consumer with the information from the 23rd instance set in the "cause" attribute.

[0090] The 38th behavior in this embodiment is the behavior in which NWDAF determines how to respond to an analytics request from an NF consumer based on user permission information. In the 38th behavior, if user permission information regarding data usage is obtained from the UDM via the Nudm_SDM service API with the query parameter uc-purpose set to the second information, and data usage is permitted for services other than signaling storm analytics but not for signaling storm analytics, NWDAF responds with a "201 Created" status code, and the message body may include information about the created subscription. Furthermore, the NwdafFailureCode may be set to the 21st information to indicate events where the subscription failed and the reason for the failure, including the "failEventReports" attribute. NWDAF may also subscribe to notifications of changes to permission information regarding data usage other than signaling storm analytics (if not already subscribed). Subscribing to change notifications means targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation to subscribe to change notifications regarding permission information for data usage other than signaling storm analytics.

[0091] The 39th behavior in this embodiment is the behavior in which NWDAF determines how to respond to an analytics request from an NF consumer based on user permission information. In the 39th behavior, if user permission information regarding data usage is obtained from the UDM via the Nudm_SDM service API, where the query parameter uc-purpose is set to the second piece of information, and data usage is permitted for signaling storm analytics but not for other applications, NWDAF responds with a "201 Created" status code, and the message body may include information about the created subscription. Furthermore, the "failEventReports" attribute may be included, and NwdafFailureCode may be set to the 22nd piece of information to indicate events where the subscription failed and the reasons for those events. NWDAF may also subscribe to notifications of changes to permission information regarding data usage in signaling storm analytics (if not already subscribed). Subscribing to change notifications means targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation to subscribe to change notifications regarding permission information for data usage other than signaling storm analytics.

[0092] The 40th behavior in this embodiment is the behavior in which NWDAF determines how to respond to an analytics request from an NF consumer based on user permission information. In the 40th behavior, if user permission information regarding data usage is obtained from the UDM via the Nudm_SDM service API with the query parameter uc-purpose set to the first information, and neither data usage in signaling storm analytics nor data usage outside of signaling storm analytics is permitted, NWDAF may send an HTTP "403 Forbidden" error response to the NF consumer with the 23rd information set in the "cause" attribute.

[0093] The 41st behavior in this embodiment is the behavior in which NWDAF determines how to respond to an analytics request from an NF consumer based on user permission information. In the 41st behavior, if user permission information regarding data usage is obtained from the UDM via the Nudm_SDM service API with the query parameter uc-purpose set to the first information, and data usage is permitted for services other than signaling storm analytics but not for signaling storm analytics, NWDAF responds with a "201 Created" status code, and the message body may include information about the created subscription. Furthermore, the NwdafFailureCode may be set in the 21st information to indicate events where the subscription failed and the reason for the failure, including the "failEventReports" attribute. NWDAF may also subscribe to notifications of changes to permission information regarding data usage other than signaling storm analytics (if not already subscribed). Subscribing to change notifications means targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation to subscribe to change notifications regarding permission information for data usage other than signaling storm analytics.

[0094] The 42nd behavior in this embodiment is the behavior in which NWDAF determines how to respond to an analytics request from an NF consumer based on user permission information. In the 42nd behavior, if user permission information regarding data usage is obtained from the UDM via the Nudm_SDM service API with the query parameter uc-purpose set to the first information, and data usage is permitted for signaling storm analytics but not for other purposes, NWDAF responds with a "201 Created" status code, and the message body may include information about the created subscription. Furthermore, the NwdafFailureCode may be set in the 22nd information to indicate events where the subscription failed and the reason for the failure, including the "failEventReports" attribute. NWDAF may also subscribe to notifications of changes to permission information regarding data usage in signaling storm analytics (if not already subscribed). Subscribing to change notifications means targeting the "SdmSubscriptions" resource and calling the Nudm_SDM_Subscribe service operation to subscribe to change notifications regarding permission information for data usage other than signaling storm analytics.

[0095] The data usage in signaling storm analytics, as described in behaviors 31 through 42, may be interpreted as data usage when the Analytics ID requested by the NF consumer (Nnwdaf consumer) from NWDAF is "Signalling Storm". Similarly, data usage outside of signaling storm analytics may be interpreted as data usage when the Analytics ID requested by the NF consumer (Nnwdaf consumer) from NWDAF is anything other than "Signalling Storm". Furthermore, the NF consumer may be an AMF or an SMF, and is not limited to these.

[0096] Furthermore, the information indicating permission for data use in signaling storm analytics, as described in behaviors 31 through 42, may be, for example, the information in section 12. The information indicating that permission for data use in signaling storm analytics is not granted may be, for example, the information in section 11. If data use is permitted outside of signaling storm analytics, this may be indicated by "CONSENT_GIVEN," and if data use is not permitted outside of signaling storm analytics, this may be indicated by "CONSENT_NOT_GIVEN." In addition, the information regarding user permission in signaling storm analytics may be information indicating whether or not user permission has been granted in signaling storm analytics, and is not limited to the information in section 11 or section 12.

[0097] Furthermore, the distinction between requests to NWDAF that are not related to signaling storm analytics, as described in behaviors 31 through 42, and requests related to signaling storm analytics may be made based on the Analytics ID included in the request.

[0098] Furthermore, the query parameter uc-purpose, as described in the 31st behavior to the 42nd behavior, may be information indicating the user licensing purpose that NWDAF includes when obtaining user licensing information from the UDM.

[0099] Furthermore, in requests to obtain user permission information regarding data usage from the UDM, as described in the 31st behavior to the 42nd behavior, multiple uc-purposes may be included at once. For example, uc-purpose#1 may be set to the first information, and uc-purpose#2 may be set to "MODEL_TRAINING".

[0100] Furthermore, in requests to obtain user permission information regarding data usage from the UDM, as described in the 31st to 42nd behaviors, multiple uc-purpose values ​​may be included at once. For example, the first piece of information may be set in uc-purpose value #1, and "MODEL_TRAINING" may be set in uc-purpose value #2.

[0101] Furthermore, user permission information regarding the use of data obtained from the UDM, as described in Behavior 31 to Behavior 42, may be included in UserConsent.

[0102] Furthermore, the user consent information regarding data usage obtained from the UDM, as described in Behavior 31 to Behavior 42, may include multiple UserConsent values ​​at once. For example, UserConsent value #1 may contain information 12 indicating that data usage in signaling storm analytics is permitted, while UserConsent value #2 may be set to "CONSENT_NOT_GIVEN" indicating that data usage outside of signaling storm analytics is not permitted.

[0103] Up to this point, in behaviors 31 through 42, we have described the procedure by which NWDAF sends uc-purpose as a query parameter to UDM. However, the query parameter that NWDAF sends to UDM is not limited to uc-purpose. As explained in behavior 61, NWDAF may also send uc-purpose / analytics information to UDM. In this case, UDM may query user permission information based on the uc-purpose / analytics information and respond to NWDAF. For example, if NWDAF uses the uc-purpose / analytics information set as the query parameter "ANALYTICS" to obtain user permission information regarding data usage from UDM via the Nudm_SDM service API, and this user permission information includes analytics information for which user permission has not been granted and analytics information for which user permission has been granted, NWDAF may subscribe to notifications of changes in permission information regarding the analytics information for which user permission has been granted. Similarly, if NWDAF obtains user permission information regarding data usage from UDM via the Nudm_SDM service API using the uc-purpose / analytics information set as the query parameter "MODEL_TRAINING", and the user permission information includes analytics information for which user permission has not been granted and analytics information for which user permission has been granted, NWDAF may subscribe to notifications of changes to the permission information regarding the analytics information for which user permission has been granted. Similarly, if NWDAF obtains user permission information regarding data usage from UDM via the Nudm_SDM service API using the uc-purpose / analytics information set as the second query parameter, and the user permission information includes analytics information for which user permission has not been granted and analytics information for which user permission has been granted, NWDAF may subscribe to notifications of changes to the permission information regarding the analytics information for which user permission has been granted.Similarly, if NWDAF uses the information of query parameter 1 and the configured uc-purpose / analytics information to obtain user permission information regarding data usage from UDM via the Nudm_SDM service API, and if the user permission information includes analytics information for which user permission has not been granted and analytics information for which user permission has been granted, NWDAF may subscribe to notifications of changes to the permission information regarding the analytics information for which user permission has been granted.

[0104] The 44th behavior in this embodiment is the behavior in which the NWDAF notifies the NF consumer ((Nnwdaf consumer e.g., AMF, SMF) of the termination of the user license. In the 44th behavior, the NWDAF receives notification from the UDM that the user license has been terminated (user license revoked) and notifies the NF consumer of the reason for the termination of the license, including the reason in the "termCause" attribute. For example, if the user license for signaling storm analytics is revoked, the NWDAF may indicate in the "termCause" attribute that the user license has been revoked. Here, "ANOMALY_USER_CONSENT_REVOKED" may be set as the reason value for the revocation of the user license for signaling storm analytics.

[0105] The 31st to 42nd behaviors in this embodiment may be implemented by calling the Nnwdaf_EventsSubscription service operation, or by calling the Nnwdaf_AnalyticsInfo service operation, or are not limited to these service operations. For example, they may be implemented by a service operation dedicated to signaling storm analytics.

[0106] (Behavior 61, Behavior 62) This section explains how to obtain Nudm user permission information using AMF / SMF (Behavior 61, Behavior 62).

[0107] The 61st behavior in this embodiment is the behavior in which NF consumer #1 (e.g., NWDAF, DCCF, NEF, trusted AF, AMF, SMF, PC) sends a GET request to the UDM to obtain user permission information. In the 61st behavior, NF consumer #1 (e.g., NWDAF, DCCF, NEF, trusted AF, AMF, SMF, PC) sends a request to a resource representing the UE's user permission information (subscriber information) and specifies uc-purpose in the query parameter. When querying user permission information related to signaling storm analytics, NF consumer #1 may set either the first information or the second information in the query parameter. Furthermore, the query parameter only needs to indicate that user permission information related to signaling storm analytics is to be obtained, and is not limited to the first information or the second information. In addition, the query parameter may also include analytics information in addition to uc-purpose. Here, analytics information may be information that identifies analytics or data collection performed by NWDAF, or it may be information that identifies a request sent by NF consumer #2 (e.g., AMF, SMF) that requests analytics or data collection from NWDAF. Analytics information may be indicated by "Analytics ID", and the data type representing said information may be EventId. Note that a request to query user permission information may contain multiple analytics information. For example, NF consumer #1 may include multiple analytics information in an Array type query parameter in a request to query user permission information.

[0108] The 62nd behavior in this embodiment is the behavior of the UDM in sending a response containing user permission information to an NF consumer (e.g., NWDAF, DCCF, NEF, trusted AF, AMF, SMF, PC). In the 62nd behavior, when the GET request shown in the 61st behavior is successful, the UDM responds with "200 OK", and the message body contains the user permission information of the requesting UE. In a request to inquire about user permission information regarding signalling storm analytics, if permission has been granted, the UDM may set the 12th information in UcSubscriptionData included in the response. If permission has not been granted, the UDM may set the 11th information in UcSubscriptionData. Furthermore, the response that the UDM sends to the NF consumer may contain multiple user permission information. For example, if the request described in the 61st behavior contains multiple uc-purpose / analytics information, user permission information may be included in a way that maps to each uc-purpose / analytics information. In other words, the UDM may indicate user permission for each piece of analytics information as user permission information.

[0109] (Information Explanation) The first to 25 pieces of information regarding the behavior described above will be explained below.

[0110] The first information in this embodiment is information indicating the user licensing purpose that NF consumer includes when obtaining user licensing information from UDM. For example, the first information may be information indicating the model training purpose in signaling storm analytics, and may be indicated as "ANOMALY_MODEL_TRAINING".

[0111] The second piece of information in this embodiment is information indicating the user licensing purpose, which is included when the NF consumer obtains user licensing information from the UDM. For example, the second piece of information may be information indicating the analytical purpose in signaling storm analytics, and may be indicated as "ANOMALY_ANALYTICS".

[0112] The eleventh piece of information in this embodiment is information indicating user permission information obtained by NF consumer from UDM. For example, the eleventh piece of information may be information indicating that data use in signaling storm analytics is not permitted, and may be indicated as "CONSENT_NOT_GIVEN_ANOMALY".

[0113] The twelfth piece of information in this embodiment is information indicating user permission information obtained by the NF consumer from the UDM. For example, the twelfth piece of information may be information indicating that data use in signaling storm analytics is permitted, and may be indicated as "CONSENT_GIVEN_ANOMALY".

[0114] The 21st piece of information in this embodiment is the error reason value that NWDAF returns to an analytics request received from an NF consumer. The 21st piece of information may be, for example, a reason value indicating that the user has not authorized it, and may be indicated as "USER_CONSENT_NOT_GRANTED".

[0115] The 22nd piece of information in this embodiment is the reason value for the error that NWDAF returns in response to an analytics request received from an NF consumer. The 22nd piece of information may be, for example, a reason value indicating that the user has not authorized signaling storm analytics, and may be indicated as "ANOMALY_USER_CONSENT_NOT_GRANTED".

[0116] The 23rd piece of information in this embodiment is an error value that NWDAF returns to an analytics request received from an NF consumer. The 23rd piece of information may be, for example, an error value indicating that the user has not authorized it, and may be represented as "USER_CONSENT_NOT_GRANTED".

[0117] The 24th piece of information in this embodiment is an error value that NWDAF returns to an analytics request received from an NF consumer. The 24th piece of information may be, for example, an error value indicating that the user has not authorized signaling storm analytics, and may be represented as "ANOMALY_USER_CONSENT_NOT_GRANTED".

[0118] The 25th piece of information in this embodiment is a reason value that NWDAF includes in its notification to the NF consumer when it terminates a previously granted user license. The 25th piece of information may be, for example, a reason value indicating that the user license has been terminated with respect to signaling storm analytics, and may be indicated as "ANOMALY_USER_CONSENT_REVOKED".

[0119] By the method described above, a mechanism can be introduced to reflect the user's intentions in user permission for data use in wireless communication networks.

[0120] (Device Configuration) Next, an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processing and operations described above will be explained. The base station 10, network node 30, and terminal 20 include the functions to perform the embodiments described above. However, the base station 10, network node 30, and terminal 20 may each be equipped with only some of the functions in the embodiments.

[0121] <Base Station 10 and Network Node 30> Figure 8 shows an example of the functional configuration of a base station 10 and a network node 30. As shown in Figure 8, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 8 is merely an example. The functional classifications and names of the functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. The network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions on the system architecture may be composed of multiple network nodes 30 separated by function.

[0122] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 or other network node 30 and transmitting the signal by wire or wireless. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 or other network node 30 and obtaining information from the received signal, for example, information from a higher layer. A communication unit including the transmitting unit 110 and the receiving unit 120 may be configured.

[0123] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20 in a storage device, and reads them from the storage device as needed.

[0124] The control unit 140 performs the processes described in the embodiment. The control unit 140 also performs processing related to communication with the terminal 20. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120.

[0125] <Terminal 20> Figure 9 is a diagram showing an example of the functional configuration of terminal 20. As shown in Figure 9, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 9 is merely an example. The functional classifications and names of the functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. In addition, the communication device that becomes the resource holder 20 may have a functional configuration similar to that of terminal 20.

[0126] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and obtains signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving control signals or reference signals transmitted from the network node 30. A communication unit including the transmitting unit 210 and the receiving unit 220 may be configured.

[0127] The setting unit 230 stores various setting information received from the network node 30 by the receiving unit 220 in its storage device and reads it from the storage device as needed. The setting unit 230 also stores pre-configured setting information.

[0128] The control unit 240 performs the processing described in the embodiment. The signal transmission function in the control unit 240 may be included in the transmission unit 210, and the signal reception function in the control unit 240 may be included in the reception unit 220.

[0129] (Hardware Configuration) The block diagrams (Figures 8 and 9) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the above one device or the above multiple devices with software.

[0130] Functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0131] For example, the base station 10, network node 30, terminal 20, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 10 is a diagram showing an example of the hardware configuration of the base station 10 and terminal 20 according to one embodiment of the present disclosure. The network node 30 may have a hardware configuration similar to that of the base station 10. The above-mentioned base station 10 and terminal 20 may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0132] In the following explanation, the term "device" can be read as "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0133] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and storage device 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the storage device 1002 and auxiliary storage device 1003.

[0134] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001.

[0135] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the base station 10 shown in Figure 8 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in Figure 9 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above-described processes have been explained as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from the network via a telecommunications line.

[0136] The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of the present disclosure.

[0137] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital multipurpose disk, a Blu-ray® disk), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0138] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmitting and receiving antenna, amplifier section, transmitting and receiving section, transmission path interface, etc., may be implemented by the communication device 1004. The transmitting and receiving section may be implemented in a physically or logically separated manner, with a transmitting section and a receiving section.

[0139] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0140] Furthermore, each device, such as the processor 1001 and the storage device 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0141] Furthermore, the base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0142] Figure 11 shows an example of the configuration of vehicle 2001. As shown in Figure 11, vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013.

[0143] The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel, which is operated by the user.

[0144] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0145] Signals from various sensors 2021 to 2029 include current signals from current sensor 2021 for sensing motor current, front and rear wheel rotation speed signals acquired by rotation speed sensor 2022, front and rear wheel air pressure signals acquired by air pressure sensor 2023, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression signals acquired by accelerator pedal sensor 2029, brake pedal depression signals acquired by brake pedal sensor 2026, shift lever operation signals acquired by shift lever sensor 2027, and detection signals acquired by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0146] The Information Service Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001. The Information Service Unit 2012 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0147] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0148] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via the communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-29 provided in the vehicle 2001.

[0149] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information with external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

[0150] The communication module 2013 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include the information based on the above input.

[0151] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0152] <Notes> (Note 1) A network node having: a transmitting unit that transmits a first message to another network node requesting subscriber information, which includes at least one of the following: information indicating user permission for anomaly analysis and information indicating user permission for training an anomaly detection model; and a receiving unit that receives a second message from the other network node, which includes the requested subscriber information and information indicating whether or not user permission has been granted. (Note 2) A network node having: a receiving unit that receives a first message to another network node requesting subscriber information; and a transmitting unit that transmits a second message to the other network node, which includes the requested subscriber information and information indicating that user permission for anomaly detection has been granted, or information indicating that user permission for anomaly detection has not been granted. (Note 3) A network node having: a receiving unit that receives a first message to another network node requesting a subscription to event notifications related to data analysis; and a transmitting unit that transmits a second message to the other network node, which includes information indicating that user permission for some events has failed. (Note 4) A network node having: a receiving unit that receives a first message from another network node requesting a subscription to event notifications relating to data analysis; and a transmitting unit that transmits to the other network node a second message which is an error response to the request, including a reason indicating that user permission for anomaly detection has not been obtained. (Note 5) A network node having: a receiving unit that receives a first message from another network node requesting a subscription to event notifications relating to data analysis for which user permission for anomaly detection has been granted; and a transmitting unit that transmits to the other network node a second message which includes information indicating that the subscription has been generated, wherein the transmitting unit transmits to the other network node a third message which includes information indicating that user permission for anomaly detection has been revoked if user permission for data relating to the subscription has been revoked.(Appendix 6) A communication method performed by a network node, comprising: sending a first message to another network node requesting subscriber information, which includes at least one of information indicating user permission for anomaly analysis and information indicating user permission for training an anomaly detection model; and receiving a second message from the other network node, which includes the requested subscriber information and information including whether or not user permission has been granted.

[0153] Any of the provisions of Appendix 1 to Appendix 6 can be used to introduce a mechanism that reflects the user's intentions in user permission for data use in wireless communication networks.

[0154] (Supplement to Embodiments) Embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may be stored in any suitable storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or other appropriate storage medium.

[0155] Furthermore, notification of information is not limited to the embodiments / models described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0156] Each aspect / embodiment described in this disclosure refers to LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20 may apply to at least one system utilizing UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. Alternatively, multiple systems may be applied in combination (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0157] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

[0158] In this specification, specific operations performed by the base station 10 may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station 10, it is clear that various operations performed for communication with the terminal 20 can be performed by the base station 10 and at least one of the other network nodes (for example, an MME or S-GW, but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station 10, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0159] The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

[0160] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0161] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0162] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0163] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0164] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0165] In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0166] The terms “system” and “network” as used in this disclosure are interchangeable.

[0167] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0168] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0169] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "base station equipment", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0170] A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0171] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform control or operation based on the information.

[0172] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0173] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0174] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0175] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminals 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0176] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal described above.

[0177] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in a table, database, or other data structure), or ascertaining. “Determining” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, or accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0178] The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0179] The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard.

[0180] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0181] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

[0182] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.

[0183] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0184] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0185] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0186] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0187] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0188] This patent application claims priority based on Japanese Patent Application No. 2024-195653, filed on November 8, 2024, and the entire contents of Japanese Patent Application No. 2024-195653 are incorporated herein by reference.

[0189] 10 Base station 110 Transmitting unit 120 Receiving unit 130 Setting unit 140 Control unit 20 Terminal 210 Transmitting unit 220 Receiving unit 230 Setting unit 240 Control unit 30 Network node 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheel 2008 Rear wheel 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driver assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (I / O port)

Claims

1. A network node having: a transmitting unit that transmits a first message to another network node requesting subscriber information, which includes at least one of the following: information indicating user permission for anomaly analysis and information indicating user permission for training an anomaly detection model; and a receiving unit that receives a second message from the other network node, which includes the requested subscriber information and information including whether or not user permission has been granted.

2. A network node having: a receiving unit that receives a first message requesting subscriber information from another network node; and a transmitting unit that transmits a second message to the other network node, which includes the requested subscriber information and information indicating that user permission for anomaly detection has been granted, or information indicating that user permission for anomaly detection has not been granted.

3. A network node having: a receiving unit that receives a first message from another network node requesting a subscription to event notifications related to data analysis; and a transmitting unit that sends a second message to the other network node that includes information indicating that user permission for some events has failed.

4. A network node having: a receiving unit that receives a first message from another network node requesting a subscription to event notifications related to data analysis; and a transmitting unit that sends a second message to the other network node which is an error response to the request, including a reason indicating that user permission for anomaly detection has not been obtained.

5. A network node comprising: a receiving unit that receives a first message from another network node requesting a subscription to event notifications regarding the analysis of data for which user permission for anomaly detection has been granted; and a transmitting unit that transmits a second message to the other network node containing information indicating that the subscription has been generated, wherein the transmitting unit transmits a third message to the other network node containing information indicating that the user permission for anomaly detection has been revoked if the user permission for data related to the subscription has been revoked.

6. A communication method performed by a network node, comprising the steps of: sending a first message to another network node requesting subscriber information, which includes at least one of information indicating user permission for anomaly analysis and information indicating user permission for training an anomaly detection model; and receiving a second message from the other network node, which includes the requested subscriber information and information including whether or not user permission has been granted.

Images