Network node and communication method

Abstract

A network node according to the present invention comprises: a reception unit that receives, from a first network node via a second network node, a message including a first identifier indicating a terminal capability relating to the handling of an inference model, a second identifier of the inference model, and the inference model indicated by the second identifier; and a control unit that stores the first identifier, the second identifier, and the inference model in association with each other.

Description

Network node and communication method

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

[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) is currently studying a wireless communication system called 5G or NR (New Radio) (hereinafter, the wireless communication system will be referred to as "5G" or "NR") in order to achieve a larger system capacity, a higher data transmission speed, and a lower latency in wireless sections. Various wireless technologies are being studied for 5G to meet the requirements of achieving a throughput of 10 Gbps or more while keeping latency in wireless sections to 1 ms or less.

[0003] In NR, a network architecture including 5GC (5G Core Network) corresponding to EPC (Evolved Packet Core), which is the core network in the network architecture of LTE (Long Term Evolution), and NG-RAN (Next Generation - Radio Access Network) corresponding to E-UTRAN (Evolved Universal Terrestrial Radio Access Network), which is the RAN (Radio Access Network) in the network architecture of LTE, is being considered (for example, Non-Patent Document 1).

[0004] In addition, 3GPP Rel-19 is considering using artificial intelligence and machine learning models in wireless communication systems for beam management, estimation of channel state information, and terminal position estimation.

[0005] 3GPP TS 23.501 V18.6.0 (2024-06) 3GPP TS 23.502 V18.6.0 (2024-06) 3GPP TS 38.331 V18.1.0 (2024-03) 3GPP TS 33.535 V18.4.0 (2024-07) 3GPP TS 23.222 V18.5.0 (2024-06)

[0006] 3GPP Rel-19 is considering using artificial intelligence and machine learning models in wireless communication systems, but currently no details have been considered regarding how to deliver inference models to terminals.

[0007] The present invention has been made in consideration of the above points, and aims to deliver inference models to terminals in wireless communication systems.

[0008] According to the disclosed technology, a network node is provided having a receiving unit that receives a message from a first network node via a second network node, the message including a first identifier indicating a terminal capability for handling an inference model, a second identifier of the inference model, and the inference model indicated by the second identifier, and a control unit that associates and stores the first identifier, the second identifier, and the inference model.

[0009] The disclosed technology enables inference models to be delivered to terminals in a wireless communication system.

[0010] FIG. 1 is a diagram for explaining an example of a communication system. FIG. 1 is a diagram for explaining an example of a communication system in a roaming environment. FIG. 2 is a diagram showing an example of a first sequence diagram in an embodiment of the present invention. FIG. 3 is a diagram showing an example of a second sequence diagram in an embodiment of the present invention. FIG. 4 is a diagram showing an example of a fourth sequence diagram in an embodiment of the present invention. FIG. 5 is a diagram showing an example of a fifth sequence diagram in an embodiment of the present invention. FIG. 6 is a diagram showing an example of a sixth sequence diagram in an embodiment of the present invention. FIG. 7 is a diagram showing an example of a seventh sequence diagram in an embodiment of the present invention. FIG. 1 is a diagram showing an example of the functional configuration of a base station 10 and a network node 30 in an embodiment of the present invention. FIG. 2 is a diagram showing an example of the functional configuration of a terminal 20 in an embodiment of the present invention. FIG. 3 is a diagram showing an example of the hardware configuration of a base station 10, a terminal 20, and a network node 30 in an embodiment of the present invention. FIG. 4 is a diagram showing an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0012] In the operation of the wireless communication system according to the embodiment of the present invention, existing technology is used as appropriate. However, the existing technology is, for example, the existing LTE, but is not limited to the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced, and systems subsequent to LTE-Advanced (e.g., NR), or wireless LAN (Local Area Network), unless otherwise specified.

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

[0014] Fig. 1 is a diagram illustrating an example of a communication system. As shown in Fig. 1, the communication system is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, 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 a radio access function, which may include a base station 10, and is connected to a UE, an AMF (Access and Mobility Management Function), and a 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), registering management, connecting management, reachability management, and terminal mobility management. The UPF is a network node 30 having functions related to processing user plane data, such as a PDU (Protocol Data Unit) session point to the outside that interconnects with the DN (Data Network), packet routing and forwarding, and user plane Quality of Service (QoS) handling. The UPF and the DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.

[0016] The AMF is connected to the 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). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are mutually connected 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 having functions such as session management, UE IP (Internet Protocol) address allocation and management, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, and roaming function. The NEF is a network node 30 having a function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node 30 having functions such as selecting a network slice to which a UE connects, determining an allowed NSSAI (Network Slice Selection Assistance Information), determining an NSSAI to be set, and determining an AMF set to which a UE connects. The PCF is a network node 30 having a function of controlling network policies. The AF is a network node 30 having a function of controlling application servers. The NRF is a network node 30 having a 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 a UDR (User Data Repository) that stores the data.

[0018] Fig. 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Fig. 2, the network is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0019] The RAN is a network node 30 having a radio access function, and is connected to the UE, the AMF, and the 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 having functions such as a PDU session point to the outside that interconnects with the DN, packet routing and forwarding, and user plane QoS handling. The UPF and the DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.

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

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

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

[0023] (Example) A method for delivering an inference model to a terminal in a wireless communication system will be described. In this example, the terminal stores an identifier (UE radio AI capability identifier) ​​indicating terminal capabilities related to handling the inference model, an inference model, and an identifier (UE NR Aimodel identifier) ​​including version information of the inference model. Furthermore, the terminal notifies the identifier (UE radio AI capability identifier) ​​in a registration procedure and obtains the latest inference model identifier (UE NR Aimodel identifier) ​​that can be used by terminals with corresponding terminal capabilities from an ADRF (Analytics Data Repository Function) via AMF. Furthermore, the terminal appropriately specifies the inference model identifier and obtains the latest inference model from the ADRF after establishing a PDU session or a QoS flow.

[0024] The details of the processing in this embodiment will be explained below using sequence diagrams. Requests, responses, notifications, etc. sent and received in the procedures shown below may be referred to as messages (e.g., request messages). For details of existing specifications regarding the messages sent and received in this sequence diagram, refer to Non-Patent Documents 2-4, etc. Note that UDM includes the functions of ARPF (Authentication Credential Repository and Processing Function) and SIDF (Subscription Identifier De-concealing Function) or enables the invocation of these functions. Furthermore, the inference model is a model trained for a terminal, and may be referred to as an AI model, etc.

[0025] (Registration Procedure) The procedure for registering a terminal will now be described. Fig. 3 is a diagram showing an example of a first sequence diagram according to an embodiment of the present invention. The processing of each step will now be described.

[0026] S100: ADRF30J associates and stores in its own device a first identifier (UE radio AI capability identifier) ​​indicating the terminal capability for handling inference models, a second identifier (UE NR Aimodel identifier) ​​of the latest artificial intelligence (AI) model that can be used in the capability indicated by the first identifier, and information on the artificial intelligence model corresponding to the second identifier.

[0027] S101: The terminal 20 transmits to the base station 10 a request message (RRCSetupRequest) requesting settings related to the radio resource control protocol (RRC).

[0028] S102: The base station 10 transmits to the terminal 20 a message (RRCSetup) relating to RRC setup.

[0029] S103: The terminal 20 transmits a message (RRCSetupComplete) notifying completion of RRC setup to the base station 10. The message includes information indicating a registration request, and is expressed as, for example, RRCSetupComplete (dedicated NAS-Message (Registration request)).

[0030] S104: The base station 10 transmits a message (Initial UE message) including information indicating a registration request to the AMF 30A. For example, the message is expressed as an Initial UE message (NAS-PDU (Registration request)).

[0031] S105: The AMF 30A transmits to the AUSF 30B a request message (Nausf_UEAuthentication_Authenticate request) requesting the execution of authentication of the terminal 20 (hereinafter, may be simply referred to as authentication).

[0032] S106: The AUSF 30B transmits a request message (Nudm_UEAuthentication_Get request) requesting authentication information to the UDM 30C.

[0033] S107: The UDM 30C transmits a response message (Nudm_UEAuthentication_Get response) to the request message received in S106 to the AUSF 30B. The response message includes information indicating that AKMA (Authentication and Key Management for Applications) is used for authentication with the ADRF when the terminal transmits and receives application messages to and from the ADRF. For details about AKMA, see Non-Patent Document 4. For example, the request message is expressed as Nudm_UEAuthentication_Get Response (AuthenticationInfoResult(akmaInd=true, routingId)).

[0034] S108: AUSF 30B transmits to AMF 30A a response message (Nausf_UEAuthentication_Authenticate response) in response to the request message received in S105.

[0035] S109: The AMF 30A transmits a message (Downlink NAS Transport) requesting the execution of authentication to the base station 10. For example, the message is expressed as Downlink NAS Transport (NAS-PDU (Authentication request)).

[0036] S110: The base station 10 transmits a message (DLInformationTransfer) requesting the execution of authentication to the terminal 20. For example, this message is expressed as DLInformationTransfer(dedicatedNAS-Message(Authentication request)).

[0037] S111: The terminal 20 transmits a message (ULInformationTransfer) including an authentication response in response to the authentication request included in the message received in S110 to the base station 10. For example, this message is expressed as ULInformationTransfer (dedicatedNAS-Message(Authentication response)).

[0038] S112: The base station 10 transmits a message (ULInformationTransfer) including the authentication response received in S111 to the AMF 30A. For example, this message is expressed as Uplink NAS Transport (NAS-PDU (Authentication response)).

[0039] S113: The AMF 30A transmits a request message (Nausf_UEAuthentication_Authenticate request) to the AUSF 30B, requesting the execution of authentication of the terminal 20.

[0040] S114: The AUSF 30B authenticates the terminal 20 in response to the request message received in S113.

[0041] S115: AUSF 30B transmits to AMF 30A a response message (Nausf_UEAuthentication_Authenticate response) in response to the request message received in S113.

[0042] S116: A SEAF (Security Anchor Function) having an authentication function in the AMF 30A performs authentication of the terminal 20.

[0043] S117: The AUSF 30B transmits a request message (Naanf_AKMA_KeyRegistration request) to the AAnF (AKMA Anchor Function) 30D, requesting key registration in the AKMA.

[0044] S118: The AAnF 30D transmits to the AUSF 30B a response message (Naanf_AKMA_KeyRegistration response) in response to the request message received in S117.

[0045] S119: The AUSF 30B transmits a request message (Nudm_UEAuthentication_ResultConfirmation request) requesting registration of the authentication result of the terminal 20 to the UDM 30C.

[0046] S120: The UDM 30C transmits to the AUSF 30B a response message (Nudm_UEAuthentication_ResultConfirmation response) in response to the request message received in S119.

[0047] The process following S120 will now be described. Fig. 4 is a diagram showing an example of a second sequence diagram according to an embodiment of the present invention. The process of each step will now be described.

[0048] S121: The AMF 30A sends a request message (Initial Context Setup request) to the base station 10 requesting the setting of a context.

[0049] S122: The base station 10 transmits to the terminal 20 a message (SecurityModeCommand) relating to the security settings of the wireless part.

[0050] S123: The terminal 20 transmits to the base station 10 a message (SecurityModeComplete) notifying completion of the setting of security for the wireless part.

[0051] S124: The base station 10 transmits to the AMF 30A a response message (Initial Context Setup response) to the request message received in S122.

[0052] S125: The AMF 30A transmits a message (Downlink NAS Transport) related to the setting of NAS security to the base station 10. For example, this message is expressed as Downlink NAS Transport (NAS-PDU (Security Mode Command)).

[0053] S126: The base station 10 transmits a message (DLInformationTransfer) related to the setting of NAS security to the terminal 20. For example, this message is expressed as DLInformationTransfer(dedicatedNAS-Message(Security Mode Command)).

[0054] S127: The terminal 20 transmits a message (ULInformationTransfer) to the base station 10 notifying the completion of NAS security configuration. The message includes information indicating the registration request that could not be transmitted before the establishment of NAS security. In particular, the message includes an identifier (UE radio AI capability identifier) ​​indicating the terminal capability for handling the inference model. For example, the message is expressed as ULInformationTransfer(dedicatedNAS-Message(Security Mode Complete(IMEISV, NAS message container(Registration request (UE radio AI capability identifier))))).

[0055] S128: The base station 10 sends a message (Uplink NAS Transport) to the AMF 30A, which includes a notification of the completion of NAS security configuration and a request for terminal registration. The message includes an identifier (UE radio AI capability identifier) ​​indicating the terminal capability for handling the inference model. For example, the message is expressed as Uplink NAS Transport(NAS-PDU(Security Mode Complete(IMEISV, NAS message container(Registration request (UE radio AI capability identifier))))).

[0056] S129: AMF 30A sends a request message (Nudm_UECM_Registration request) to UDM 30C requesting registration of terminal 20.

[0057] S130: UDM30C sends a response message (Nudm_UECM_Registration response) to AMF30A in response to the request message received in S129.

[0058] S131: The AMF 30A transmits a request message (Nudm_SDM_Get request) requesting subscriber information of the terminal 20 to the UDM 30C.

[0059] S132: UDM30C sends a response message (Nudm_SDM_Get response) to AMF30A in response to the request message received in S131. The response message includes subscriber information including information indicating that the inference model update is permitted (AimodelUpdateAllowed). The response message also includes subscriber information including information indicating that user consent for data collection has been given. For example, the response message is expressed as Nudm_SDM_Get response (AccessAndMobilitySubscriptionData (UcSubscriptionData ([UcPurpose="DATA_COLLECTION_FOR_UE_MODEL_TRAINING",UserConsent="CONSENT_GIVEN"])), AimodelUpdateAllowed).

[0060] S133: The AMF 30A determines to acquire terminal setting information for data collection from the DEF 30E.

[0061] S134: AMF 30A sends a request message (Ndef_UeConfigurationInformation request) to DEF 30E requesting terminal setting information.

[0062] S135: The DEF 30E transmits a request message (Nnwdaf_AnalyticsInfo_Request request) to the NWDAF 30F, requesting an analysis of the network load status.

[0063] S136: The NWDAF 30F transmits to the DEF 30E a response message (Nnwdaf_AnalyticsInfo_Request response) in response to the request message received in S135. The response message includes information related to the analysis of the network load status.

[0064] S137: Based on the information received in S135, the DEF 30E determines the recommended time and place for the terminal 20 to upload collected data.

[0065] S138: The DEF 30E transmits a response message (Ndef_UeConfigurationInformation response) to the request message received in S134 to the AMF 30A. The response message includes, as terminal configuration information, information on the content of the data to be collected, information on the time to collect the data, and information on the location to collect the data. The configuration information may also include recommended values ​​for the time and location to transmit the collected data. For example, the response message is expressed as Ndef_UeConfigurationInformation response (UeConfigurationInformation (ToBeCollectedData, TimingOfDataCollection, AreaOfDataCollection, RecommendedUploadCondition)).

[0066] S139: AMF 30A sends a request message (Nadrf_MLModelManagement_Query request) to ARDF 30J requesting an inference model. The request message includes a first identifier (UE radio AI capability identifier) ​​indicating the terminal capability for handling the inference model. For example, the request message is expressed as Nadrf_MLModelManagement_Query request (UE radio AI capability identifier).

[0067] S140: The ARDF 30J decides to return the second identifier (UE NR AI model identifier) ​​of the latest inference model that can be used with the capability indicated by the first identifier (UE radio AI capability identifier) ​​received in S139.

[0068] S141: The ARDF 30J transmits a response message (Nadrf_MLModelManagement_Query response) to the request message received in S139 to the AMF 30A. The response message includes a second identifier (UE NR AI model identifier) ​​of the latest inference model among the inference models trained for a terminal having a terminal capability indicated by a first identifier (UE radio AI capability identifier) ​​indicating terminal capability related to handling of the inference model. Also, for example, the response message is expressed as Nadrf_MLModelManagement_Query response (UE NR AI model identifier).

[0069] S142: The AMF 30A transmits a message (Downlink NAS Transport) including the acceptance of the terminal registration received in S128, the terminal configuration information received in S138, and the second identifier of the latest inference model received in S141 (UE NR AI model identifier) ​​to the base station 10. For example, this message is expressed as Downlink NAS Transport (NAS-PDU(Registration accept(UeConfigurationInformation, UE NR AI model identifier))).

[0070] S143: The base station 10 sends a message (DLInformationTransfer) including the terminal configuration information received in S142 and a second identifier (UE NR AI model identifier) ​​of the latest inference model to the terminal 20. For example, the message is expressed as DLInformationTransfer (dedicatedNAS-Message(Registration accept (UeConfigurationInformation, UE NR AI model identifier))).

[0071] S144: The terminal 20 configures its own device based on the terminal configuration information (UeConfigurationInformation) received in S143, and thereafter collects necessary data as appropriate based on the terminal configuration information. The terminal 20 may also transmit a PDU session establishment request or a PDU session change request to the AMF 30A at a time and location based on the recommended values ​​for the time and location for transmitting the collected data included in the terminal configuration information.

[0072] S145: If the terminal 20 recognizes that the second identifier (UE NR AI model identifier) ​​received in S143 indicates a newer inference model than the second identifier indicating the inference model currently in use and stored in the terminal 20 (first condition), the terminal 20 may set the value of the second identifier received in S143 to a third identifier (Next UE NR AI model identifier) ​​indicating the inference model that should be acquired from the network by the terminal 20.

[0073] In addition, if the terminal 20 satisfies the first condition and the third identifier indicating the inference model to be acquired from the network is not stored in the terminal 20, or if the second identifier received in S143 indicates that it is newer than the value of the third identifier already stored in the terminal 20, the terminal 20 may set the value of the second identifier received in S143 as the third identifier.

[0074] (UE Configuration Update Procedure) The UE Configuration Update procedure will now be described. Fig. 5 is a diagram showing an example of a third sequence diagram according to an embodiment of the present invention. The processing of each step will now be described.

[0075] S151: ARDF 30J sends a request message (Nadrf_MLModelManagement_UpdateNotify request) to AMF 30A requesting an update of information related to the inference model identifier. The request message includes the identifier of the updated inference model (UE NR AI model Identifier). For example, the request message is expressed as Nadrf_MLModelManagement_UpdateNotify request (UE NR AI model Identifier).

[0076] S152: AMF 30A sends a response message (Nadrf_MLModelManagement_UpdateNotify response) to DEF 30E in response to the request message received in S151.

[0077] S153: The AMF 30A transmits a message (Downlink NAS Transport) including an identifier (UE NR AI model Identifier) ​​of the updated inference model to the base station 10. For example, the message is expressed as Downlink NAS Transport (NAS-PDU (Configuration Update Command (UE NR AI model Identifier))).

[0078] S154: The base station 10 sends a message (DLInformationTransfer) including an identifier (UE NR AImodel Identifier) ​​of the updated inference model to the terminal 20. For example, the message is expressed as DLInformationTransfer (dedicatedNAS-Message(Configuration Update Command (UE NR Aimodel Identifier))).

[0079] S155: The terminal 20 transmits a response message to the message received in S154 to the base station 10. For example, this message is expressed as ULInformationTransfer(dedicatedNAS-Message(Configuration Update Complete)).

[0080] S156: The base station 10 transmits a response message to the message received in S153 to the AMF 30A. For example, this message is expressed as Uplink NAS Transport (NAS-PDU (Configuration Update Complete)).

[0081] S157: If the terminal 20 recognizes that the second identifier (UE NR AI model identifier) ​​received in S154 indicates a newer inference model than the second identifier indicating the inference model currently in use and stored in the terminal 20 (first condition), the terminal 20 may set the value of the second identifier received in S154 to a third identifier (Next UE NR AI model identifier) ​​indicating the inference model to be acquired from the network by the terminal 20.

[0082] In addition, if the terminal 20 satisfies the first condition and a third identifier indicating the inference model to be acquired from the network is not stored in the terminal 20, or if the second identifier received in S154 indicates that it is newer than the value of the third identifier already stored in the terminal 20, the terminal 20 may set the value of the second identifier received in S154 as the third identifier.

[0083] (Procedure for establishing a PDU session for acquiring an inference model) The procedure for establishing a PDU session for acquiring an inference model will now be described. Fig. 6 is a diagram showing an example of a fourth sequence diagram in an embodiment of the present invention. The processing of each step will now be described.

[0084] S201: When a value is set in a third identifier (Next UE NR AI model identifier) ​​indicating the inference model that the terminal 20 should acquire from the network, the terminal 20 decides to establish a PDU session to acquire the inference model from the network at an appropriate time.

[0085] S202: The terminal 20 sends a message (ULInformationTransfer) to the base station 10 requesting establishment of a PDU session, including information indicating that the PDU session is for retrieving an inference model. The information may be the data network name (Data Network Name, DNN) from which the inference model is to be retrieved. For example, the message is expressed as ULInformationTransfer(dedicatedNAS-Message(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment request), DNN=for AI model retrieval))).

[0086] S203: The base station 10 sends to the AMF 30A a message (Uplink NAS Transport) requesting establishment of a PDU session, including information indicating that the PDU session is related to retrieval of an inference model. For example, the message is expressed as Uplink NAS Transport(NAS-PDU(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment request), DNN=for AI model retrieval))).

[0087] S204: AMF 30A sends to SMF 30H a request message (Nsmf_PDUSession_CreateSMContext request) requesting establishment of a PDU session, including information indicating that the PDU session is related to retrieval of an inference model. For example, the request message is expressed as Nsmf_PDUSession_CreateSMContext request(Dnn=for AI model retrieval, SmContextCreateData(n1SmMsg(PDU session establishment request))).

[0088] S205: SMF30H sends a response message (Nsmf_PDUSession_CreateSMContext response) to AMF30A in response to the request message received in S204.

[0089] S206: The SMF 30H transmits to the ADRF 30J a request message (Nadrf_ConnectionManagement request) related to an uplink (UL) connection for the ADRF 30J.

[0090] S207: The ADRF 30J transmits to the SMF 30H a response message (Nadrf_ConnectionManagement response) in response to the request message received in S206. The response message includes a UL termination point identifier (Tunnel Endpoint Identifier, TEID) for the ADRF 30J, which is information about the termination point related to UL data reception within the SMF 30H.

[0091] S208: SMF 30H transmits to UPF 30G a first request message (PFCP Session Establishment request) for UL to ADRF 30J and a second request message (PFCP Session Establishment request) for DL ​​originating from ADRF 30J, requesting that the UPF 30G set a termination point in ADRF 30J as the destination of packet forwarding settings for UL data. The first request message includes the packet forwarding rule (Forwarding Action Rule, FAR) in which the TEID for UL to ADRF 30J received in S207 is set.

[0092] S209: UPF 30G transmits to SMF 30H a first response message (PFCP Session Establishment response) to the first request message for UL to ADRF 30J, and a second response message (PFCP Session Establishment response) to the second request message for DL ​​originated from ADRF 30J, both of which were received in S208. The second response message includes a DL TEID within UPF 30G, which is information on the termination point related to DL data reception within UPF 30G.

[0093] S210: The SMF 30H transmits to the ADRF 30J a request message (Nadrf_ConnectionManagement request) requesting that a termination point in the UPF 30G be set as the destination of the packet forwarding setting for DL ​​data. The request message includes the packet forwarding setting (FAR) in which the DL TEID for the UPF 30G received in S209 is set.

[0094] S211: The ADRF 30J transmits to the SMF 30H a response message (Nadrf_ConnectionManagement response) in response to the request message received in S210.

[0095] S212: SMF 30H sends a message (Namf_Communication_N1N2MessageTransfer request) including information indicating acceptance of the PDU session establishment request to AMF 30A. For example, the request message is expressed as Namf_Communication_N1N2MessageTransfer request (N1N2MessageTransferReqData(n1MessageContainer(PDU Session Establishment accept) n2InfoContainer(smInfo(n2InfoContent(PDU Session Resource Setup Request Transfer))))).

[0096] S213: AMF 30A sends a response message (Namf_Communication_N1N2MessageTransfer response) to the request message received in S212 to SMF 30H.

[0097] S214: The AMF 30A transmits a request message (PDU Session Resource Setup request) for setting up a PDU session resource to the base station 10. For example, the request message is expressed as PDU Session Resource Setup request (NAS-PDU (DL NAS transport (Payload container type (N1 SM information), Payload container (PDU Session Establishment accept))), PDU Session Resource Setup Request Transfer).

[0098] S215: The base station 10 transmits a message (RRCReconfiguration) related to RRC reconfiguration, including information indicating acceptance of the PDU session establishment request, to the terminal 20. For example, the message is expressed as RRCReconfiguration(dedicatedNAS-Message(DL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Establishment accept)))).

[0099] S216: The terminal 20 transmits to the base station 10 a message (RRCReconfigurationComplete) indicating that the RRC reconfiguration has been completed.

[0100] S217: The base station 10 transmits a response message (PDU Session Resource Setup response) to the request message received in S214 to the AMF 30A. For example, the response message is expressed as PDU Session Resource Setup response (PDU Session Resource Setup Response Transfer).

[0101] S218: AMF 30A sends a request message (Nsmf_PDUSession_UpdateSMContext request) to SMF 30H requesting a context update of the PDU session. For example, the request message is expressed as Nsmf_PDUSession_UpdateSMContext request (SmContextUpdateData(n2SmInfo(PDU Session Resource Setup Response Transfer))).

[0102] S219: SMF30H sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30A in response to the request message received in S218.

[0103] S220: SMF30H sends a request message (PFCP Session Modification request) to UPF30G to update the user data transfer path.

[0104] S221: UPF 30G sends a response message (PFCP Session Modification response) to SMF 30H in response to the request message received in S220.

[0105] S222: A user plane path is established from the terminal 20 to the ADRF 30J via the base station 10 and the UPF 30G.

[0106] (QoS flow establishment procedure for inference model acquisition) The QoS flow establishment procedure for inference model acquisition will be described. Fig. 7 is a diagram showing an example of a fifth sequence diagram in the embodiment of the present invention. The processing of each step will be described below.

[0107] S301: When a value is set in a third identifier (Next UE NR AI model identifier) ​​indicating an inference model to be acquired from the network, the terminal 20 determines to establish a QoS flow to acquire the inference model from the network at an appropriate time. Here, it is assumed that a PDU session for the Internet has already been established.

[0108] S302: The terminal 20 sends a message (ULInformationTransfer) requesting a PDU session update, including information indicating the addition of a QoS flow related to the acquisition of an inference model, to the base station 10. For example, the message is expressed as ULInformationTransfer(dedicatedNAS-Message(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Modification request(Requested QoS rules(QFI=for AI model acquisition)))))).

[0109] S303: The base station 10 sends to the AMF 30A a message (Uplink NAS Transport) requesting a PDU session update, including information indicating that a QoS flow related to the acquisition of an inference model is to be added. For example, the message is expressed as Uplink NAS Transport(NAS-PDU(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Modification request(Requested QoS rules(QFI=for AI model acquisition)))))).

[0110] S304: The AMF 30A sends to the SMF 30H a request message (Nsmf_PDUSession_UpdateSMContext request) requesting an update of the PDU session, the request message including information indicating the addition of a QoS flow related to the acquisition of an inference model. The request message includes a QoS Flow Identifier (QFI) set to a value indicating the QoS flow for data collection. For example, the request message is expressed as Nsmf_PDUSession_UpdateSMContext request (SmContextUpdateData(n1SmMsg(PDU session modification request(Requested QoS rules(QFI=for AI model acquisition))))).

[0111] S305: SMF30H sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30A in response to the request message received in S304.

[0112] S306: The SMF 30H recognizes the message received in S304 as a QoS flow for data collection based on the QFI (QoS Flow Identifier) ​​value included in the message.

[0113] S307: The SMF 30H transmits to the ADRF 30J a request message (Nadrf_ConnectionManagement request) related to an uplink (UL) connection for the ADRF 30J.

[0114] S308: The ADRF 30J transmits to the SMF 30H a response message (Nadrf_ConnectionManagement response) in response to the request message received in S306. The response message includes a UL termination point identifier (Tunnel Endpoint Identifier, TEID) for the ADRF 30J, which is information about the termination point related to UL data reception within the SMF 30H.

[0115] S309: The SMF 30H transmits to the UPF 30G a first request message (PFCP Session Establishment request) for UL to the ADRF 30J and a second request message (PFCP Session Establishment request) for DL ​​originating from the ADRF 30J, requesting that the UPF 30G set a termination point in the ADRF 30J as the destination of the packet forwarding setting for UL data. The first request message includes a packet forwarding rule (FAR) with the UL TEID for the ADRF 30J received in S308 set. The request message also includes a packet detection rule (PDR) with the Local F (Fully Qualified)-TEID and the QFI set to a value indicating the QoS flow for inference model acquisition set.

[0116] S310: UPF 30G transmits to SMF 30H a first response message (PFCP Session Establishment response) to the first request message for UL to ADRF 30J, and a second response message (PFCP Session Establishment response) to the second request message for DL ​​originated from ADRF 30J, both of which were received in S309. The second response message includes a DL TEID within UPF 30G, which is information on the termination point related to DL data reception within UPF 30G.

[0117] S311: The SMF 30H transmits to the ADRF 30J a request message (Nadrf_ConnectionManagement request) requesting that a termination point in the UPF 30G be set as the destination of the packet forwarding setting for DL ​​data. The request message includes the packet forwarding setting (FAR) in which the DL TEID for the UPF 30G received in S310 is set.

[0118] S312: The ADRF 30J transmits to the SMF 30H a response message (Nadrf_ConnectionManagement response) in response to the request message received in S311.

[0119] S313: SMF 30H sends a message (Namf_Communication_N1N2MessageTransfer request) including information indicating acceptance of the PDU session update request to AMF 30A. For example, the request message is expressed as Namf_Communication_N1N2MessageTransfer request (N1N2MessageTransferReqData(n1MessageContainer(PDU Session Modification command) n2InfoContainer(smInfo(n2InfoContent(PDU Session Resource Modify Request Transfer))))).

[0120] S314: AMF 30A sends a response message (Namf_Communication_N1N2MessageTransfer response) to the request message received in S313 to SMF 30H.

[0121] S315: The AMF 30A transmits a request message (PDU Session Resource Modify request) for updating the PDU session resources to the base station 10. For example, the request message is expressed as PDU Session Resource Modify request (NAS-PDU (DL NAS transport (Payload container type (N1 SM information), Payload container (PDU Session Modification command))), PDU Session Resource Modify Request Transfer).

[0122] S316: The base station 10 transmits an RRC reconfiguration message (RRCReconfiguration) including information indicating acceptance of the PDU session update request to the terminal 20. For example, the message is expressed as RRCReconfiguration(dedicatedNAS-Message(DL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Modification command)))).

[0123] S317: The terminal 20 transmits to the base station 10 a message (RRCReconfigurationComplete) indicating that the RRC reconfiguration has been completed.

[0124] S318: The base station 10 transmits a response message (PDU Session Resource Modify response) to the request message received in S315 to the AMF 30A. For example, the response message is expressed as PDU Session Resource Modify response (PDU Session Resource Modify Response Transfer).

[0125] S319: AMF 30A sends a request message (Nsmf_PDUSession_UpdateSMContext request) to SMF 30H requesting a context update of the PDU session. For example, the request message is expressed as Nsmf_PDUSession_UpdateSMContext request (SmContextUpdateData(n2SmInfo(PDU Session Resource Modify Response Transfer))).

[0126] S320: SMF30H sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30A in response to the request message received in S319.

[0127] S321: The terminal 20 transmits a message (ULInformationTransfer) notifying the base station 10 of the completion of the PDU session update. For example, the message is expressed as ULInformationTransfer(dedicatedNAS-Message(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Modification complete)))).

[0128] S322: The base station 10 transmits a message (Uplink NAS Transport) notifying the AMF 30A of the completion of the PDU session update. For example, the message is expressed as Uplink NAS Transport(NAS-PDU(UL NAS transport(Payload container type(N1 SM information), Payload container(PDU Session Modification complete)))).

[0129] S323: AMF30A sends a message (Nsmf_PDUSession_UpdateSMContext request) to SMF30H notifying it of the completion of the PDU session update.

[0130] S324: SMF30H sends a response message (Nsmf_PDUSession_UpdateSMContext response) to AMF30A in response to the request message received in S323.

[0131] S325: A user plane path is established from the terminal 20 to the ADRF 30J via the base station 10 and the UPF 30G.

[0132] (Inference model acquisition procedure in the user plane) This section describes the procedure for acquiring an inference model in the user plane, which is executed following the PDU session establishment procedure for inference model acquisition or the QoS flow establishment procedure for inference model acquisition. Figure 8 is a diagram showing an example of a sixth sequence diagram in an embodiment of the present invention. The processing of each step is described below.

[0133] S401: The terminal 20 decides to execute the TLS (Transport Layer Security) 1.3 procedure (see Sections B.1.3.2.2 and 6.2.1 of Non-Patent Document 4) using the AKMA key.

[0134] S402: The terminal 20 sends a message (ClientHello) to the ADRF 30J to start the TLS 1.3 procedure.

[0135] S403: The ADRF 30J sends a request message (Naanf_AKMA_ApplicationKey_Get request) to the AAnF 30D requesting the AKMA key.

[0136] S404: The AAnF 30D sends to the ADRF 30J a response message (Naanf_AKMA_ApplicationKey_Get response) in response to the request message received in S403.

[0137] S405: The ADRF 30J sends to the terminal 20 a message (Server Hello) in response to the message received in S402.

[0138] Through the processing of S402 to S405, mutual authentication is performed between the terminal 20 and the network (ADRF 30J) via the user plane. Furthermore, in the following S407 and S408, the confidentiality and integrity of messages transmitted and received via the user plane between the terminal 20 and ADRF 30J are protected.

[0139] S406: The terminal 20 decides to acquire an inference model corresponding to the value of a third identifier (Next UE NR AI model identifier) ​​set in the terminal 20, which indicates the inference model to be acquired from the network.

[0140] S407: The terminal 20 sends a request message (Nadrf_MLModelManagement_RetrievalRequest request) to the ADRF 30J requesting acquisition of an inference model. The request message includes an identifier (UE NR AImodel identifier) ​​to which the value of a third identifier (Next UE NR AImodel identifier) ​​indicating the inference model to be acquired from the network is set. For example, the request message is expressed as Nadrf_MLModelManagement_RetrievalRequest request (UE NR AImodel identifier).

[0141] S408: The ADRF 30J sends a message (Nadrf_MLModelManagement_RetrievalRequest Response) in response to the request message received in S407 to the terminal 20. The response message includes the requested inference model.

[0142] S409: The terminal 20 sets the value of the third identifier (Next UE NR AI model identifier), which indicates the inference model to be acquired, to the second identifier (UE NR AI model identifier) ​​of the latest inference model, and erases the value set in the third identifier (Next UE NR AI model identifier). In addition, the terminal 20 switches the inference model to be used.

[0143] (Inference model input procedure) This section describes the procedure by which an external application server (such as a vendor server) inputs an inference model into the network. Figure 9 shows an example of a seventh sequence diagram in an embodiment of the present invention. The processing of each step is described below.

[0144] S501: The AF30K in the application server sends a request message (Nnef_MLModelManagement_StorageRequest request) to the NEF30H requesting storage of an inference model. The request message includes a first identifier (UE radio AI capability identifier) ​​indicating the terminal capability for handling the inference model, a second identifier (UE NR AI model identifier) ​​of the inference model, and the inference model indicated by the second identifier. For example, the request message is expressed as Nnef_MLModelManagement_StorageRequest request (UE radio AI capability identifier, UE NR AI model identifier, AI model).

[0145] S502: The NEF 30H transmits to the AF 30K a response message (Nnef_MLModelManagement_StorageRequest response) in response to the request message received in S501.

[0146] S503: The NEF 30H authenticates the application server identifier (AfId) included in the request message received in S501 using the function of CAPIF (Common API (Application Programming Interface) Framework, see Non-Patent Document 5).

[0147] S504: The NEF 30H sends a request message (Nadrf_MLModelManagement_StorageRequest request) to the ADRF 30J requesting storage of the inference model. The request message includes a first identifier (UE radio AI capability identifier) ​​indicating the terminal capability for handling the inference model, a second identifier (UE NR AI model identifier) ​​of the inference model, and the inference model indicated by the second identifier. For example, the request message is expressed as Nadrf_MLModelManagement_StorageRequest request (UE radio AI capability identifier, UE NR AI model identifier, AI model).

[0148] S505: ADRF30J associates the first identifier, second identifier, and inference model indicated by the second identifier received in S504 and stores them in its own device.

[0149] S506: The ADRF 30J transmits to the NEF 30H a response message (Nadrf_MLModelManagement_StorageRequest response) in response to the request message received in S504.

[0150] The above-described embodiments enable delivery of inference models to terminals in a wireless communication system.

[0151] (Device Configuration) Next, a description will be given of an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processes and operations described above. The base station 10, network node 30, and terminal 20 include functions for performing the above-described embodiments. However, the base station 10, network node 30, and terminal 20 may each include only a part of the functions of the embodiments.

[0152] <Base Station 10 and Network Node 30> Fig. 10 is a diagram showing an example of the functional configuration of the base station 10 and the network node 30. As shown in Fig. 10, 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 Fig. 10 is merely an example. As long as the operations according to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. Note that the network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions in the system architecture may be composed of multiple network nodes 30 separated by function.

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

[0154] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20 in a storage device, and reads out the information from the storage device as needed.

[0155] The control unit 140 performs the processes described in the embodiments, etc. The control unit 140 also performs processes related to communication with the terminal 20. The function unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the function unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0156] <Terminal 20> Fig. 11 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 11, the 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 Fig. 11 is merely an example. As long as the operations related to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. In addition, a communication device that becomes a resource holder 20 may have the same functional configuration as the terminal 20.

[0157] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving control signals, reference signals, etc. transmitted from the network node 30. A communication unit including the transmitter 210 and the receiver 220 may be configured.

[0158] The setting unit 230 stores various setting information received from the network node 30 by the receiving unit 220 in a storage device, and reads it out from the storage device as needed. The setting unit 230 also stores setting information that is set in advance.

[0159] The control unit 240 performs the processes described in the embodiments. The function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0160] (Hardware Configuration) The block diagrams (FIGS. 10 and 11) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0161] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0162] For example, the base station 10, the network node 30, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 12 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The network node 30 may have the same hardware configuration as the base station 10. The above-described base station 10 and the 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.

[0163] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0164] Each function in the base station 10 and the terminal 20 is realized by loading specified software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0165] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0166] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002 and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 10 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 11 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0167] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0168] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk 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 versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0169] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0170] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0171] 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 may be configured using different buses between each device.

[0172] Furthermore, the base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0173] Fig. 13 shows an example configuration of a vehicle 2001. As shown in Fig. 13, the 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 the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0174] The drive unit 2002 is configured, for example, by 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 operated by the user.

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

[0176] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

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

[0178] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

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

[0180] 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 an external device. For example, it transmits and receives various information to and from the external device 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, a mobile station, or the like.

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

[0182] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker 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 external devices 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 to 2029, etc. provided in the vehicle 2001.

[0183] <Additional Notes> (Additional Note 1) A network node having: a receiving unit that receives a message from a first network node via a second network node, the message including a first identifier indicating a terminal capability for handling an inference model, a second identifier of the inference model, and the inference model indicated by the second identifier, and a control unit that associates and stores the first identifier, the second identifier, and the inference model. (Additional Note 2) A network node having: a receiving unit that receives from the first network node a first message including the first identifier indicating a terminal capability for handling an inference model, and a transmitting unit that transmits to the first network node a second message including a second identifier indicating the latest inference model among inference models trained for a terminal having the terminal capability indicated by the first identifier. (Supplementary clause 3) A network node comprising: a receiver that receives from a terminal a first message requesting registration, the first message including a first identifier indicating the terminal's capabilities for handling inference models; a receiver that receives from a first network node a second message including subscriber information, the second message including information indicating permission to update the inference model; and a transmitter that transmits the second message including the first identifier to a second network node, wherein the receiver receives from the second network node a third message including a second identifier indicating the latest inference model among the inference models trained for a terminal having the terminal capabilities indicated by the first identifier; and the transmitter transmits to the terminal a fourth message including the second identifier accepting the registration.(Supplementary Item 4) A network node comprising: a receiver that receives from a first network node a first message requesting establishment of a PDU session, the first message including information indicating that the PDU session is related to the acquisition of an inference model, or a second message requesting a PDU session change, the second message including information indicating that a QoS (Quality of Service) flow related to the acquisition of an inference model is to be added; a receiver that receives from a second network node a third message including information on a termination point related to uplink data reception within the device; and a transmitter that transmits to a third network node a fourth message requesting that the termination point within the second network node be set as the destination of packet forwarding settings for uplink data; wherein the receiver receives from the third network node a fifth message including information on a termination point related to downlink data reception within the device; and the transmitter transmits to the second network node a sixth message requesting that the termination point within the third network node be set as the destination of packet forwarding settings for downlink data. (Supplementary clause 5) A communication method executed by a network node, comprising: a step of receiving a message from a first network node via a second network node, the message including a first identifier indicating a terminal capability for handling an inference model, a second identifier of the inference model, and the inference model indicated by the second identifier; and a step of associating and storing the first identifier, the second identifier, and the inference model.

[0184] Any of Supplementary Items 1 to 5 makes it possible to deliver an inference model to a terminal in a wireless communication system.

[0185] (Supplementary Notes on the Embodiments) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, 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; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (as long as there is no contradiction). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized by hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

[0186] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0187] Each aspect / embodiment described in the present disclosure may be implemented using any of the following standards: LTE (Long Term Evolution), LTE-Advanced (LTE-A), 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 (x is, for example, an integer or a decimal number)), 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.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 ( The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

[0188] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be rearranged unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

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

[0190] The information, signals, etc. described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0191] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

[0192] In the present disclosure, the determination may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0193] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0194] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

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

[0196] Note that terms described 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 a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0197] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0198] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, a radio resource may be indicated by an index.

[0199] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0200] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "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. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.

[0201] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage.

[0202] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

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

[0204] 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 some other suitable terminology.

[0205] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does 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.

[0206] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present 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, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0207] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

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

[0209] The terms "connected," "coupled," or any variation thereof, refer to 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" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0210] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0211] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0212] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

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

[0214] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0215] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0216] In the present 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 "coupled" may also be interpreted in the same way as "different."

[0217] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0218] Although the present disclosure has been described in detail above, it is 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 spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0219] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 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 wheels 2008 Rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Tire 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 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A network node having: a receiving unit that receives a message from a first network node via a second network node, the message including a first identifier indicating a terminal capability for handling an inference model, a second identifier of the inference model, and the inference model indicated by the second identifier; and a control unit that associates and stores the first identifier, the second identifier, and the inference model.

2. A network node having: a receiving unit that receives a first message from a first network node, the first message including a first identifier indicating a terminal capability for handling an inference model; and a transmitting unit that transmits to the first network node a second message including a second identifier indicating the latest inference model among inference models trained for a terminal having the terminal capability indicated by the first identifier.

3. A network node comprising: a receiver that receives from a terminal a first message requesting registration, the first message including a first identifier indicating the terminal's capabilities for handling an inference model; a receiver that receives from a first network node a second message including subscriber information, the second message including information indicating permission to update the inference model; and a transmitter that transmits the second message including the first identifier to a second network node, wherein the receiver receives from the second network node a third message including a second identifier indicating the latest inference model among the inference models trained for a terminal having the terminal capabilities indicated by the first identifier; and the transmitter transmits to the terminal a fourth message including the second identifier accepting the registration.

4. A network node comprising: a receiver that receives from a first network node a first message requesting establishment of a PDU session, the first message including information indicating that the PDU session is related to the acquisition of an inference model, or a second message requesting a PDU session change, the second message including information indicating that a QoS (Quality of Service) flow related to the acquisition of an inference model is to be added; a receiver that receives from a second network node a third message including information on a termination point related to uplink data reception within the device; and a transmitter that transmits to a third network node a fourth message requesting that the termination point within the second network node be set as the destination of packet forwarding settings for uplink data; wherein the receiver receives from the third network node a fifth message including information on a termination point related to downlink data reception within the device; and the transmitter transmits to the second network node a sixth message requesting that the termination point within the third network node be set as the destination of packet forwarding settings for downlink data.

5. A communication method executed by a network node, comprising: a step of receiving a message from a first network node via a second network node, the message including a first identifier indicating a terminal capability for handling an inference model, a second identifier of the inference model, and the inference model indicated by the second identifier; and a step of associating and storing the first identifier, the second identifier, and the inference model.

Images