Network node, terminal, and communication method

Abstract

This network node comprises: a transmission unit that transmits, to another network node, a first message including data network name (DNN) and an identifier of single network slice selection assistance information (SNSSAI), and requesting a subscription related to analysis of an abnormally excessive control signal; and a reception unit that receives, from the other network node, a second message including information indicating that the subscription has been created.

Description

Network Node, Terminal, and Communication Method

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

[0002] In 3GPP (Registered Trademark) (3rd Generation Partnership Project), in order to achieve further increase in system capacity, further increase in data transmission speed, further reduction in latency in the radio section, etc., a wireless communication method called 5G or NR (New Radio) (hereinafter, this wireless communication method is referred to as "5G" or "NR") is being studied. In 5G, 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, various wireless technologies are being studied.

[0003] Also, the network architecture in 5GC (5G Core Network) or 5GS (5G System), which is the core network in 5G, and 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 optimization by utilizing artificial intelligence is being studied as a countermeasure against abnormal behavior in terminals and networks (for example, the generation of an abnormally excessive control signal (signalling storm)).

[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) 3GPP TS 24.501 V18.8.0 (2024 - 09)

[0006] While 3GPP is considering network optimization using artificial intelligence (AI), the procedures for utilizing information based on AI and other data analysis for network optimization are not yet clear.

[0007] This invention has been made in view of the above points, and aims to clarify the procedures for utilizing information based on data analysis in wireless communication networks.

[0008] According to the disclosed technology, a network node is provided having a transmitting unit that sends a first message to another network node requesting a subscription for the analysis of abnormally excessive control signals, including an identifier for DNN (Data Network Name) and SNSSAI (Single Network Slice Selection Assistance Information), and a receiving unit that receives a second message from the other network node, including information indicating that the subscription has been generated.

[0009] The disclosed technology can clarify the procedures for utilizing data analysis-based information in wireless communication networks.

[0010] 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 mitigation and prevention of signaling storms by NWDAF in an embodiment of the present invention. This is a diagram showing an example of a first sequence diagram in an embodiment of the present invention. This is a diagram showing an example of a second sequence diagram 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.

[0011] 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.

[0012] 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.

[0013] 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.

[0014] 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.

[0015] 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.

[0016] 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.

[0017] 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.

[0018] 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.

[0019] 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.

[0020] 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.

[0021] 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.

[0022] 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.

[0023] Figure 3 illustrates the mitigation and prevention of a signaling storm by NWDAF in an embodiment of the present invention. The sequence diagram in Figure 3 shows the procedure for mitigating and preventing a signaling storm by NWDAF. The processing of each step will be described below.

[0024] In step 1, Consumer NF30A sends a message to NWDAF30B regarding a subscription or request for analysis of an abnormally excessive signaling storm. Hereafter, Consumer NF30A may also be referred to as NF service consumer30A.

[0025] In step 2, the NWDAF30B collects data necessary for signaling storm analysis from the 5GC NF(s)30C, which is a network function in the 5G core network.

[0026] In step 3, the NWDAF30B performs a signaling storm analysis using the data collected in step 2.

[0027] In step 4, NWDAF30B sends a message to Consumer NF30A containing a notification or response regarding the detection, prediction, or mitigation of a signaling storm, based on the analysis results performed in step 3.

[0028] In step 5, Consumer NF30A performs processing in the network function based on the information contained in the notification or response received in step 4. This processing may be, for example, processing of a large volume of control signals from a terminal (massive signaling from UE), as shown in Figure 3.

[0029] For example, the AMF may set a timer (e.g., a backoff timer (T3512)) related to mobility management (MM) based on a range of recommended timer values ​​for one or more specified terminals received from the NWDAF30B.

[0030] For example, the SMF may set timers (e.g., backoff timers) related to session management (SM) based on a range of recommended timer values ​​for one or more specified terminals received from the NWDAF30B.

[0031] The following describes a method for clarifying the procedure for utilizing information based on data analysis in a wireless communication network, with regard to the processing shown in the sequence diagram of Figure 3.

[0032] (Method 1) Method 1 is a method relating to the details of the process in step 1 of Figure 3. Figure 4 is a diagram showing an example of a first sequence diagram in an embodiment of the present invention. In step 1 of Figure 4, NF service consumer 30A (corresponding to Consumer NF30A in Figure 3) sends a message to NWDAF 30B regarding a subscription or request for NWDAF assistance information related to the analysis of a signaling storm, using the service operation Nnwdaf_AnalyticsSubscription_Subscribe or Nnwdaf_AnalyticsInfo_Request. In step 2 of Figure 4, NWDAF 30B sends a message (201 Created) to NF service consumer 30A indicating that a subscription has been created.

[0033] The processing related to Method 1 described above may be as shown in the following behaviors 1 to 7. Here, NF service consumer 30A may be referred to as NF consumer.

[0034] The first behavior in this embodiment is the behavior in which an NF consumer (e.g., AMF, SMF) specifies the scope of signaling storm analytics, including the type of signaling storm analytics and related identification information, in a signaling storm analytics request or signaling storm analytics subscription request sent to the NWDAF. In the first behavior, the NF consumer (e.g., AMF, SMF) sends a signaling storm analytics request or a signaling storm analytics subscription request to the NWDAF. The request includes the type of signaling storm analytics event. If the event type indicates a signaling storm-related event (e.g., "SIGNALLING_STORM") and requests signaling storm analytics related to a specific DNN (Data Network Name) and SNSSAI (Single Network Slice Selection Assistance Information), the request includes DNN identification in the "dnns" attribute and SNSSAI identification in the "snnsais" attribute.

[0035] The second behavior in this embodiment is the behavior in which an NF consumer (e.g., AMF, SMF) specifies the scope of signaling storm analytics, including the type of signaling storm analytics and related identification information, in a signaling storm analytics request or signaling storm analytics subscription request sent to the NWDAF. In the second behavior, the NF consumer (e.g., AMF, SMF) sends a signaling storm analytics request or a signaling storm analytics subscription request to the NWDAF. The request includes the type of event for signaling storm analytics. If the event type indicates a signaling storm-related event (e.g., "SIGNALLING_STORM") and requests signaling storm analytics related only to any DNN, the request may include only attribute information that identifies any DNN. The identification of any DNN may be indicated by "any DNN indication," and the attribute information may be the "anyDNN" attribute.

[0036] The third behavior in this embodiment is the behavior in which an NF consumer (e.g., AMF, SMF) specifies the scope of signaling storm analytics, including the type of signaling storm analytics and related identification information, in a signaling storm analytics request or signaling storm analytics subscription request sent to NWDAF. In the third behavior, the NF consumer (e.g., AMF, SMF) sends a signaling storm analytics request or a signaling storm analytics subscription request to NWDAF. The request includes the type of signaling storm analytics event. If the event type indicates a signaling storm-related event (e.g., "SIGNALLING_STORM") and requests signaling storm analytics related only to any SNSSAI, the request may include only attribute information that identifies any SNSSAI. The identification of any SNSSAI may be indicated by "any SNSSAI indication," and the attribute information may be the "anySlice" attribute.

[0037] The fourth behavior in this embodiment is the behavior in which an NF consumer (e.g., AMF, SMF) specifies the scope of signaling storm analytics, including the type of signaling storm analytics and related identification information, in a signaling storm analytics request or signaling storm analytics subscription request sent to the NWDAF. In the fourth behavior, the NF consumer (e.g., AMF, SMF) sends a signaling storm analytics request or a signaling storm analytics subscription request to the NWDAF. The request includes the type of event for signaling storm analytics. If the event type indicates a signaling storm-related event (e.g., "SIGNALLING_STORM") and requests signaling storm analytics related to a specific DNN and any SNSSAI, the request may include attribute information that identifies the DNN identification and any SNSSAI in the "dnns" attribute. The identification of any SNSSAI may be indicated by "any SNSSAI indication," and the attribute information that identifies the any SNSSAI may be the "anySlice" attribute.

[0038] The fifth behavior in this embodiment is the behavior in which an NF consumer (e.g., AMF, SMF) specifies the scope of signaling storm analytics, including the type of signaling storm analytics and related identification information, in a signaling storm analytics request or signaling storm analytics subscription request sent to the NWDAF. In the fifth behavior, the NF consumer (e.g., AMF, SMF) sends a signaling storm analytics request or signaling storm analytics subscription request to the NWDAF. The request includes the type of signaling storm analytics event. If the event type indicates a signaling storm-related event (e.g., "SIGNALLING_STORM") and requests signaling storm analytics related to any DNN and a specific SNSSAI, the request may include attribute information that identifies any DNN and SNSSAI identification in the "snnsais" attribute. The identification of any DNN may be indicated by "any DNN indication," and the attribute information that identifies the any DNN may be the "anyDNN" attribute.

[0039] The sixth behavior in this embodiment is the behavior in which an NF consumer (e.g., AMF, SMF) specifies the scope of signaling storm analytics, including the type of signaling storm analytics and related identification information, in a signaling storm analytics request or signaling storm analytics subscription request sent to the NWDAF. In the sixth behavior, the NF consumer (e.g., AMF, SMF) sends a signaling storm analytics request or a signaling storm analytics subscription request to the NWDAF. The request includes the type of signaling storm analytics event. If the event type indicates a signaling storm-related event (e.g., "SIGNALLING_STORM") and requests signaling storm analytics related to any DNN and any SNSSAI, the request may include attribute information that identifies any DNN and attribute information that identifies any SNSSAI. Identifying any DNN may be indicated by "any DNN indication," and the attribute information that identifies any DNN may be the "anyDNN" attribute. The identification of any SNSSAI may be indicated by "any SNSSAI indication," and the attribute information that identifies said any SNSSAI may be the "anySlice" attribute.

[0040] The seventh behavior in this embodiment is the behavior in which an NF consumer (e.g., AMF, SMF) specifies the scope of signaling storm analytics, including the type of signaling storm analytics and related identification information, in a signaling storm analytics request or signaling storm analytics subscription request sent to the NWDAF. In the seventh behavior, the NF consumer (e.g., AMF, SMF) sends a signaling storm analytics request or a signaling storm analytics subscription request to the NWDAF. The request includes the type of signaling storm analytics event. If the event type indicates a signaling storm-related event (e.g., "SIGNALLING_STORM"), and the request does not include attribute information identifying any DNN, attribute information identifying any SNSSAI, DNN identification in the "dnns" attribute, and SNSSAI identification in the "snnsais" attribute, it may mean that signaling storm analytics related to any DNN and any SNSSAI are targeted.

[0041] Here, the first to seventh 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.

[0042] (Method 2) Method 2 is a method regarding the details of the processing in step 5 of FIG. 3. FIG. 5 is a diagram showing an example of a second sequence diagram in an embodiment of the present invention. In FIG. 5, AMF / SMF30D (corresponding to Consumer NF30A in FIG. 3) receives, from NWDAF30B, a message including a notification or response regarding the detection / prediction / mitigation of signalling storm based on the analysis result.

[0043] The AMF may set a timer related to mobility management (MM) (for example, a backoff timer (T3512)) based on the range of the recommended timer values for one or more specified terminals received from NWDAF30B.

[0044] The SMF may set a timer related to session management (SM) (for example, a backoff timer) based on the range of the recommended timer values for one or more specified terminals received from NWDAF30B.

[0045] The processing related to the above-mentioned Method 2 may be as shown in the following Behavior 11 to Behavior 22. Here, NF service consumer30A may be referred to as NF consumer.

[0046] The eleventh behavior in this embodiment is the behavior by which AMF / SMF can respond to subsequent congestion management processing by storing timer information included in the output analytics of signaling storm analytics in association with the DNN information provided at the time of the signaling storm analytics request. In the eleventh behavior, if the cause information of the signaling storm included in the output analytics of signaling storm analytics indicates a large amount of signaling from the UE, and timer information is included in the output analytics of signaling storm analytics, the DNN associated with the timer information may be the DNN information (DNN identification) provided by AMF / SMF in the signaling storm analytics request or the signaling storm analytics subscription request. When AMF / SMF receives the output analytics of signaling storm analytics from NWDAF, it stores the timer in association with the DNN provided by AMF / SMF at the time of the signaling storm analytics request or the signaling storm analytics subscription request. For this purpose, AMF / SMF needs to store the DNN information provided to NWDAF when a signaling storm analytics request or a signaling storm analytics subscription request is made. Furthermore, AMF / SMF may set the timer value of the stored timer to the back-off timer associated with the same DNN.

[0047] The twelfth behavior in this embodiment is the behavior by which AMF / SMF can respond to subsequent congestion management processing by storing timer information included in the output analytics of signaling storm analytics in association with the DNN information provided at the time of the signaling storm analytics request. In the twelfth behavior, if the cause information of the signaling storm included in the output analytics of signaling storm analytics indicates a large amount of signaling from the UE, and timer information is included in the output analytics of signaling storm analytics, and attribute information identifying any DNN is specified at the time of the signaling storm analytics request or signaling storm analytics subscription request, then the timer information may be associated with any DNN. When AMF / SMF receives the output analytics of signaling storm analytics from NWDAF, it stores the timer in association with any DNN as specified by AMF / SMF at the time of the signaling storm analytics request or signaling storm analytics subscription request. For this purpose, AMF / SMF needs to remember any DNN information provided to NWDAF when a signaling storm analytics request or a signaling storm analytics subscription request is made. Furthermore, AMF / SMF may set the timer value of the stored timer to the back-off timer associated with any DNN.

[0048] The 13th behavior in this embodiment is the behavior that enables subsequent congestion management processing by the AMF / SMF to associate and hold the timer information included in the output (output analytics) of the signalling storm analytics with the DNN information provided at the time of the signalling storm analytics request. In the 13th behavior, when the cause information (cause) of the signalling storm included in the output of the signalling storm analytics indicates massive signalling from the UE and the timer information is included in the output of the signalling storm analytics, and when the attribute information and DNN information (DNN identification) for identifying any DNN are not specified at the time of the signalling storm analytics request or the signalling storm analytics subscription request, the timer information may be associated with no DNN. When the AMF / SMF receives the output of the signalling storm analytics from the NWDAF, it saves the timer in association with no DNN. For this purpose, the AMF / SMF needs to remember the DNN information provided to the NWDAF at the time of the signalling storm analytics request or the signalling storm analytics subscription request. Furthermore, the AMF / SMF may set the timer value of the saved timer to the back-off timer associated with no DNN.

[0049] The 14th behavior in this embodiment is a behavior that enables AMF / SMF to appropriately save the output of signaling storm analytics by associating timer information with the DNN provided by NWDAF. In the 14th behavior, if the cause information of the signaling storm included in the output of signaling storm analytics indicates massive signaling from the UE, and timer information is included in the output of signaling storm analytics, the DNN to associate with the timer information is the DNN provided by NWDAF in the output of signaling storm analytics. When AMF / SMF receives the output of signaling storm analytics from NWDAF, it saves the timer associating it with the DNN provided by NWDAF in the output of signaling storm analytics. Furthermore, AMF / SMF may set the timer value of the saved timer to the back-off timer associated with the same DNN.

[0050] The 15th behavior in this embodiment is a behavior that enables AMF / SMF to appropriately save the output of signaling storm analytics by associating timer information with the DNN provided by NWDAF. In the 15th behavior, if the cause information of the signaling storm included in the output of signaling storm analytics indicates massive signaling from the UE, and timer information is included in the output of signaling storm analytics, and attribute information identifying any DNN is provided in the output of signaling storm analytics, then the timer information may be associated with any DNN. When AMF / SMF receives the output of signaling storm analytics from NWDAF, it associates the timer with any DNN based on the attribute information identifying any DNN shown in the output of signaling storm analytics and saves it. Furthermore, AMF / SMF may set the timer value of the saved timer to the back-off timer associated with the arbitrary DNN.

[0051] The sixteenth behavior in this embodiment is a behavior that enables AMF / SMF to appropriately save the output of signaling storm analytics by associating timer information with the DNN provided by NWDAF. In the sixteenth behavior, if the cause information of the signaling storm included in the output of signaling storm analytics indicates massive signaling from the UE, and timer information is included in the output of signaling storm analytics, and attribute information and DNN information (DNN identification) that identify any DNN are not provided in the output of signaling storm analytics, then the timer information may be associated with no DNN. When AMF / SMF receives the output of signaling storm analytics from NWDAF, it saves the timer associated with no DNN. Furthermore, AMF / SMF may set the timer value of the saved timer to the back-off timer associated with no DNN.

[0052] The seventeenth behavior in this embodiment is that AMF / SMF stores timer information included in the output analytics of signaling storm analytics in association with SNSSAI information provided at the time of the signaling storm analytics request, thereby enabling it to handle subsequent congestion management processing. In the seventeenth behavior, if the cause information of the signaling storm included in the output analytics of signaling storm analytics indicates a massive amount of signaling from the UE, and timer information is included in the output analytics of signaling storm analytics, the SNSSAI associated with the timer information may be the SNSSAI information (SNSSAI identification) provided by AMF / SMF in the signaling storm analytics request or the signaling storm analytics subscription request. When AMF / SMF receives the output analytics of signaling storm analytics from NWDAF, it stores the timer in association with the SNSSAI provided by AMF / SMF at the time of the signaling storm analytics request or the signaling storm analytics subscription request. For this purpose, AMF / SMF needs to store the SNSSAI information provided to NWDAF when a signaling storm analytics request or a signaling storm analytics subscription request is made. Furthermore, AMF / SMF may set the timer value of the stored timer to the back-off timer associated with the same SNSSAI.

[0053] The 18th behavior in this embodiment is the behavior by which AMF / SMF can respond to subsequent congestion management processing by storing timer information included in the output analytics of signaling storm analytics in association with the SNSSAI information provided at the time of the signaling storm analytics request. In the 18th behavior, if the cause information of the signaling storm included in the output analytics of signaling storm analytics indicates a large amount of signaling from the UE, and timer information is included in the output analytics of signaling storm analytics, and attribute information identifying any SNSSAI is specified at the time of the signaling storm analytics request or signaling storm analytics subscription request, then the timer information may be associated with any SNSSAI. When AMF / SMF receives the output analytics of signaling storm analytics from NWDAF, it stores the timer in association with any SNSSAI as specified by AMF / SMF at the time of the signaling storm analytics request or signaling storm analytics subscription request. For this purpose, AMF / SMF needs to remember any SNSSAI information provided to NWDAF when a signaling storm analytics request or a signaling storm analytics subscription request is made. Furthermore, AMF / SMF may set the timer value of the stored timer to the back-off timer associated with any SNSSAI.

[0054] The 19th behavior in this embodiment is the behavior by which AMF / SMF can respond to subsequent congestion management processing by storing timer information included in the output analytics of signaling storm analytics in association with the SNSSAI information provided at the time of the signaling storm analytics request. In the 19th behavior, if the cause information of the signaling storm included in the output analytics of signaling storm analytics indicates a large amount of signaling from the UE, and timer information is included in the output analytics of signaling storm analytics, and attribute information and SNSSAI information (SNSSAI identification) that identify any SNSSAI were not specified at the time of the signaling storm analytics request or the signaling storm analytics subscription request, then the timer information may be associated with no SNSSAI. When AMF / SMF receives the output analytics of signaling storm analytics from NWDAF, it stores the timer associated with no SNSSAI. For this purpose, AMF / SMF needs to store the SNSSAI information provided to NWDAF when a signaling storm analytics request or a signaling storm analytics subscription request is made. Furthermore, AMF / SMF may set the timer value of the stored timer to the back-off timer associated with no SNSSAI.

[0055] The 20th behavior in this embodiment is a behavior that enables AMF / SMF to appropriately save the output of signaling storm analytics by associating timer information with the SNSSAI provided by NWDAF. In the 20th behavior, if the cause information of the signaling storm included in the output of signaling storm analytics indicates massive signaling from the UE, and timer information is included in the output of signaling storm analytics, the SNSSAI to associate with the timer information is the SNSSAI provided by NWDAF in the output of signaling storm analytics. When AMF / SMF receives the output of signaling storm analytics from NWDAF, it saves the timer associating it with the SNSSAI provided by NWDAF in the output of signaling storm analytics. Furthermore, AMF / SMF may set the timer value of the saved timer to the back-off timer associated with the same SNSSAI.

[0056] The 21st behavior in this embodiment is a behavior that enables AMF / SMF to appropriately save the output of signaling storm analytics by associating timer information with SNSSAI provided by NWDAF. In the 21st behavior, if the cause information of the signaling storm included in the output of signaling storm analytics indicates massive signaling from UE, and timer information is included in the output of signaling storm analytics, and attribute information identifying any SNSSAI is provided in the output of signaling storm analytics, then the timer information may be associated with any SNSSAI. When AMF / SMF receives the output of signaling storm analytics from NWDAF, it associates the timer with any SNSSAI based on the attribute information identifying any SNSSAI shown in the output of signaling storm analytics and saves it. Furthermore, AMF / SMF may set the timer value of the saved timer to the back-off timer associated with any SNSSAI.

[0057] The 22nd behavior in this embodiment is the behavior that enables AMF / SMF to appropriately save the output of signaling storm analytics by associating timer information with SNSSAI provided by NWDAF. In the 22nd behavior, if the cause information of the signaling storm included in the output of signaling storm analytics indicates massive signaling from UE, and timer information is included in the output of signaling storm analytics, and attribute information and SNSSAI information (SNSSAI identification) that identify any SNSSAI are not provided in the output of signaling storm analytics, then the timer information may be associated with no SNSSAI. When AMF / SMF receives the output of signaling storm analytics from NWDAF, it saves the timer associated with no SNSSAI. Furthermore, AMF / SMF may set the timer value of the saved timer to the back-off timer associated with no SNSSAI.

[0058] Furthermore, as described in the 11th to 13th behaviors and the 17th to 19th behaviors, AMF / SMF needs to store the DNN or SNSSAI information provided to NWDAF when a signaling storm analytics request or a signaling storm analytics subscription request is made. In addition, AMF / SMF sets the timer value of the back-off timer based on this stored information. Here, a signaling storm analytics request or a signaling storm analytics subscription request may include a combination of DNN and S-NSSAI as described in the 1st to 7th behaviors [(DNN or any DNN or no DNN), (SNSSAI or any SNSSAI or no SNSSAI)]. At this time, the timer information included in the output of the signaling storm analytics received by AMF / SMF is stored in association with that combination. Furthermore, AMF / SMF may set the timer value of the stored timer to the back-off timer associated with the same combination.

[0059] Furthermore, as explained in the 14th to 16th behaviors and the 20th to 22nd behaviors, AMF / SMF sets the timer value of the back-off timer based on the DNN or SNSSAI information included in the output of signaling storm analytics. Here, the DNN or SNSSAI information included in the output of signaling storm analytics may include a combination of DNN and S-NSSAI [(DNN or any DNN or no DNN), (SNSSAI or any SNSSAI or no SNSSAI)]. In this case, the timer information included in the output of signaling storm analytics received by AMF / SMF is stored in association with that combination. In addition, AMF / SMF may set the timer value of the stored timer to the back-off timer associated with the same combination.

[0060] Furthermore, the output of signaling storm analytics described in behaviors 11 to 22 may be analytics result notifications from NWDAF in response to signaling storm analytics requests or signaling storm analytics subscription requests by NF consumers, as described in behaviors 1 to 7.

[0061] (Method 3) Method 3 is a method for functionally differentiating AI-based functions from older functions, taking into consideration the need to differentiate AI-based functions from older functions (by pricing structure) as an operator business.

[0062] The processing related to Method 3 may be as shown in the following behaviors 31 to 34.

[0063] The 31st behavior in this embodiment is that, if the UE supports AI / ML (Predictive) congestion control, it sends the support information to the AMF as UE capability information in the REGISTRATION REQUEST message.

[0064] The 32nd behavior in this embodiment is that when a UE indicates its intention to use AI / ML (Predictive) congestion control, it includes this preference information in the REGISTRATION REQUEST message and sends it to the AMF as UE preference information.

[0065] The 33rd behavior in this embodiment is the network behavior that enables the use of AI / ML (Predictive) congestion control (AI-based predictive congestion management) when using CIoT 5GS optimizations, after the conditions for using AI / ML (Predictive) congestion control (AI-based predictive congestion management) have been met by the network and the UE. In the 33rd behavior, if the registration procedure indicates that the UE supports one or more CIoT 5GS optimizations, the network supports one or more CIoT 5GS optimizations, the UE supports (requests / prefers) AI / ML (Predictive) congestion control (AI-based predictive congestion management), and the network decides to accept the registration request, the network notifies the UE of its support for AI / ML (Predictive) congestion control (AI-based predictive congestion management). The network's support notification may be interpreted by the UE as acceptance of the use of the function.

[0066] The 34th behavior in this embodiment is the network's behavior that enables the use of AI / ML (Predictive Congestion Control) after the network and the UE have met the conditions for using AI / ML (Predictive Congestion Control). In the 34th behavior, if the UE requests / prefers AI / ML (Predictive Congestion Control) during the registration procedure and the network decides to accept the registration request, the network notifies the UE of its support for AI / ML (Predictive Congestion Control). The network's support notification may be interpreted by the UE as acceptance of the use of the function.

[0067] For example, the UE sends a first message to the AMF requesting registration to the network, which includes information indicating that its device supports AI-powered predictive congestion management. The UE then receives a second message from the AMF accepting the registration, which also includes information indicating that the network supports AI-powered predictive congestion management. Finally, based on the second message, the UE may recognize that the use of AI-powered predictive congestion management has been approved.

[0068] (Method 4) A method relating to interaction with the upper layer (see Section 6.2.9 of Non-Patent Document 6) in the Mobile Management (MM) procedure by AMF and the Session Management (SM) procedure by SMF, for example, by notifying the upper layer of information regarding the PDU session, and the upper layer initiating the PDU session establishment procedure based on that information.

[0069] Method 4 assumes network optimization and optimization of MM / SM behavior at terminals, taking into account the optimization of communication networks using artificial intelligence (AI).

[0070] The processing related to Method 4 may be as shown in the following 41st behavior.

[0071] The 41st behavior in this embodiment is the behavior in which the AI / ML layer (component) within the UE optimizes the control of PDU sessions through the exchange of information with SM (Session Management) entities and higher layers. AI / ML requires interaction between higher layers and SM entities within the UE. The AI / ML layer (component) may request the SM entity to: a) establish a PDU session by specifying one or more PDU session attributes; b) release an existing PDU session; or c) establish a PDU session by specifying one or more PDU session attributes and release an existing PDU session. Each SM entity within the UE must provide the AI / ML layer (component) with the attributes of the newly established PDU session (e.g., PDU session identifier, SSC mode, S-NSSAI, DNN, PDU session type, access type, PDU address). In AI / ML (Predictive) congestion control, when a SM entity processing a PDU session receives the backoff timer and / or related information (e.g., cause of backoff, based on NWDAF analytics), it notifies the AI / ML layer (component) of this information. Note that requests from the AI / ML layer (component) to the SM entity may be made via a higher layer. For example, the AI / ML layer (component) may control the PDU session probability requests made by the higher layer and then make the requests to the SM entity.

[0072] For example, the UE assumes that components related to artificial intelligence and machine learning within its own device exchange information with the session management entity regarding the control of PDU (Packet Data Unit) sessions via a higher layer. The UE also receives information about backoff timers from a network node that performs predictive congestion management using artificial intelligence. Here, the UE may have the session management entity notify the component of the received backoff timer information via a higher layer.

[0073] The method described above clarifies the procedures for utilizing data analysis-based information in wireless communication networks.

[0074] (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.

[0075] <Base Station 10 and Network Node 30> Figure 6 shows an example of the functional configuration of a base station 10 and a network node 30. As shown in Figure 6, 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 6 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.

[0076] 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.

[0077] 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.

[0078] 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.

[0079] <Terminal 20> Figure 7 is a diagram showing an example of the functional configuration of terminal 20. As shown in Figure 7, 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 7 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.

[0080] 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.

[0081] 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.

[0082] 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.

[0083] (Hardware Configuration) The block diagrams (Figures 6 and 7) 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 one device or the multiple devices with software.

[0084] 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.

[0085] 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 8 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.

[0086] In the following explanation, the term "device" can be replaced with "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.

[0087] 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.

[0088] 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.

[0089] 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 6 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 7 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.

[0090] 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.

[0091] 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.

[0092] 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.

[0093] 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).

[0094] 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.

[0095] 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.

[0096] Figure 9 shows an example of the configuration of vehicle 2001. As shown in Figure 9, 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.

[0097] 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.

[0098] 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).

[0099] 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.

[0100] 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.).

[0101] 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.

[0102] 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.

[0103] 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.

[0104] 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.

[0105] 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.

[0106] <Notes> (Note 1) A network node having: a transmitting unit that transmits a first message to another network node requesting a subscription for analysis of abnormally excessive control signals, including an identifier for DNN (Data Network Name) and SNSSAI (Single Network Slice Selection Assistance Information); and a receiving unit that receives a second message from the other network node, including information indicating that the subscription has been generated. (Note 2) The network node according to Note 1, wherein the receiving unit further has a control unit that receives a third message from the other network node, including a timer value, regarding the output of the analysis, and stores the DNN and the timer value in association; and the control unit sets the timer value to a backoff timer associated with the DNN. (Note 3) A terminal comprising: a transmitting unit that transmits a first message to a network node requesting registration to the network, which includes information indicating that the device supports predictive congestion management by artificial intelligence; a receiving unit that receives a second message from the network node accepting the registration, which includes information indicating that the network supports predictive congestion management by artificial intelligence; a control unit that recognizes, based on the second message, that the use of predictive congestion management by artificial intelligence has been accepted; (Note 4) A terminal comprising: a control unit that assumes that components related to artificial intelligence and machine learning within the device exchange information with a session management entity regarding the control of PDU (Packet Data Unit) sessions via a higher layer; and a receiving unit that receives information regarding a backoff timer from a network node that performs predictive congestion management utilizing artificial intelligence, wherein the control unit causes the session management entity to notify the component of the information regarding the backoff timer via a higher layer.(Appendix 5) A communication method performed by a network node, comprising the steps of: sending a first message to another network node requesting a subscription for the analysis of abnormally excessive control signals, including an identifier for DNN (Data Network Name) and SNSSAI (Single Network Slice Selection Assistance Information); and receiving a second message from the other network node, including information indicating that the subscription has been generated.

[0107] Any of the appendices 1 to 5 can clarify the procedures for using data analysis-based information in wireless communication networks.

[0108] (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.

[0109] Furthermore, notification of information is not limited to the embodiments 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.

[0110] 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).

[0111] 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.

[0112] 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).

[0113] 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.

[0114] 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.

[0115] 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).

[0116] 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.

[0117] 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.

[0118] 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.

[0119] 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.

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

[0121] 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.

[0122] 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.

[0123] 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.

[0124] 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.

[0125] 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.

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

[0127] 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.

[0128] 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.

[0129] 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.

[0130] 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.

[0131] 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."

[0132] 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.

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

[0134] 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."

[0135] 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.

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

[0137] 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.

[0138] 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.

[0139] 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."

[0140] 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).

[0141] 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.

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

[0143] 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 sends a first message to another network node requesting a subscription for the analysis of abnormally excessive control signals, including an identifier for DNN (Data Network Name) and SNSSAI (Single Network Slice Selection Assistance Information); and a receiving unit that receives a second message from the other network node, including information indicating that the subscription has been generated.

2. The network node according to claim 1, wherein the receiving unit receives a third message relating to the output of the analysis, including a timer value, from the other network node, and further has a control unit that stores the DNN and the timer value in association, and the control unit sets the timer value to a backoff timer associated with the DNN.

3. A transmitting unit that sends a first message to a network node requesting registration to the network, which includes information indicating that the device supports predictive congestion management using artificial intelligence; a receiving unit that receives a second message from the network node accepting the registration, which includes information indicating that the network supports predictive congestion management using artificial intelligence; a control unit that recognizes, based on the second message, that the use of predictive congestion management using artificial intelligence has been accepted; and a terminal.

4. A terminal comprising: a control unit that assumes that components related to artificial intelligence and machine learning within the device exchange information regarding the control of PDU (Packet Data Unit) sessions with a session management entity via a higher layer; and a receiving unit that receives information regarding the backoff timer from a network node that performs predictive congestion management using artificial intelligence, wherein the control unit causes the session management entity to notify the components of the information regarding the backoff timer via a higher layer.

5. A communication method performed by a network node, comprising the steps of: sending a first message to another network node requesting a subscription for the analysis of abnormally excessive control signals, including an identifier for DNN (Data Network Name) and SNSSAI (Single Network Slice Selection Assistance Information); and receiving a second message from the other network node, including information indicating that the subscription has been generated.

Images