Terminal and communication method

Abstract

This terminal uses a reasoning model and comprises: a control unit that manages information pertaining to software for the reasoning model; and a transmission unit that transmits the information to a network node via a base station.

Description

Terminal and communication method

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

[0002] In 3GPP (registered trademark) (3rd Generation Partnership Project), a wireless communication system called 5G or NR (New Radio) (hereinafter, the wireless communication system is referred to as "5G" or "NR") has been introduced to achieve further increase in system capacity, further increase in data transmission speed, and further reduction in latency in a radio section, etc. Various wireless technologies have been introduced in 5G to satisfy the requirement that the latency in the radio section is 1 ms or less while achieving a throughput of 10 Gbps or more. Furthermore, studies are also being conducted on 6G, which is a future communication system.

[0003] In addition, provision of services using AI / ML (Artificial Intelligence / Machine Learning) is under consideration in 3GPP (registered trademark).

[0004] 3GPP TS 23.502 V19.2.0 (2024-12)

[0005] In the use of AI / ML, it is conceivable that, for example, a terminal uses an inference model to perform beam estimation, position information estimation, and the like. However, at present, a method for delivering an inference model to a terminal is not clearly defined.

[0006] The present invention has been made in view of the above points, and an object of the present invention is to provide a technique for delivering an inference model to a terminal in a wireless communication system.

[0007] According to the disclosed technology, there is provided a terminal that uses an inference model, comprising: a control unit that manages information related to software for the inference model; and a transmission unit that transmits the information to a network node via a base station.

[0008] According to the disclosed technology, there is provided a technique for delivering an inference model to a terminal in a wireless communication system.

[0009] This is a diagram illustrating an example of a communication system. This is a diagram illustrating an example of a communication system in a roaming environment. This is a diagram illustrating an example of a system configuration. This is a sequence diagram showing an example of operation. This is a sequence diagram showing an example of operation. This is a sequence diagram showing an example of operation. This is a sequence diagram showing an example of operation. This is a diagram illustrating an example of the functional configuration of a network node 100 in an embodiment of the present invention. This is a diagram illustrating an example of the functional configuration of a terminal 20 in an embodiment of the present invention. This is a diagram illustrating an example of the hardware configuration of a terminal 20 and a network node 100 in an embodiment of the present invention. This is a diagram illustrating an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

[0010] Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to those described below.

[0011] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies may be used as appropriate. However, such existing technologies include, for example, existing LTE or existing NR, but are not limited to these.

[0012] Furthermore, in embodiments of the present invention, "configuring" wireless parameters means that predetermined values ​​are pre-configured, or that wireless parameters notified from a network node or terminal 20 are configured. Below, we will first describe an example of a core network configuration to which the technology of the present invention can be applied with reference to Figure 1, and then describe the configuration and operation related to embodiments of the present invention.

[0013] Figure 1 is a diagram illustrating an example of a communication system corresponding to a core network. As shown in Figure 1, this communication system consists of a UE (Terminal 20) and multiple network nodes. Note that a configuration including one or more network nodes may be referred to as a "network". Hereafter, one network node will be assigned to each function, but one network node may implement multiple functions, or multiple network nodes may implement one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0014] Furthermore, although Figure 1 shows the 5G core network, all or some of the network nodes in the core network shown in Figure 1 may also be used in 6G. Also, the names of network nodes that have the same functions as in 5G may be different in 6G.

[0015] The RAN (Radio Access Network) 10 is a network node with radio access functionality, which may include a base station 10, and is connected to the UE 20, AMF (Access and Mobility Management Function) 35, and UPF (User plane function) 30. The RAN 10 may also be called the gNB 10. The AMF 35 is a network node that has functions such as RAN interface termination, NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and mobility management. The UPF 30 is a network node that interconnects with the DN (Data Network) and has functions such as PDU (Protocol Data Unit) session point to the outside, packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF 30 and DN constitute a network slice.

[0016] AMF35 is connected to UE20, RAN10, SMF (Session Management function)40, NSSF (Network Slice Selection Function), NEF (Network Exposure Function)65, NRF (Network Repository Function), UDM (Unified Data Management)55, AUSF (Authentication Server Function)50, PCF (Policy Control Function)45, AF (Application Function)80, and UDR (User Data Repository). AMF35, SMF40, NSSF, NEF65, NRF, UDM55, AUSF50, PCF45, AF80, and UDR are network nodes that are interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, Naf, and Nudr.

[0017] SMF40 is a network node with functions such as session management, IP (Internet Protocol) address assignment and management for UE20, DHCP (Dynamic Host Configuration Protocol) functionality, ARP (Address Resolution Protocol) proxy, and roaming functionality. NEF65 is a network node with the function of notifying other NFs (Network Functions) of capabilities and events. NSSF is a network node with functions such as selecting the network slice to which UE20 connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be set, and determining the AMF set to which UE20 connects. PCF45 is a network node with the function of controlling network policies. AF80 is a network node with the function of controlling application servers. NRF is a network node with the function of discovering NF instances that provide services. UDM55 is a network node that manages subscriber data and authentication data. UDM55 is connected to the UDR that holds the said data. Furthermore, AF80 can also be referred to as an application function.

[0018] Figure 1 also shows the Equipment Identity Register (EIR) 60. The EIR can be used to check, for example, the Permanent Equipment Identifier (PEI).

[0019] Figure 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Figure 2, the network consists of a terminal 20 (UE) and multiple network nodes.

[0020] SEPP is an opaque proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). In Figure 2, vSEPP is SEPP in the visited network, and hSEPP is SEPP in the home network.

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

[0022] (Regarding the challenges) As mentioned above, 3GPP (registered trademark) is considering providing services that utilize AI / ML (Artificial Intelligence / Machine Learning).

[0023] Terminals can apply inference models to functions such as beam estimation and position estimation. For terminals to utilize inference models, the inference models must be delivered to them. However, currently, the method for delivering inference models to terminals is not clearly defined.

[0024] One possible method for delivering inference models to terminals is to have the terminal initiate the inference model acquisition procedure. However, this method could cause network congestion if many terminals initiate the procedure simultaneously.

[0025] (System Configuration) Figure 3 shows a communication system equipped with the devices related to this embodiment. The communication system includes UE20, gNB10, UPF30, AMF35, SMF40, PCF45, AUSF50, UDM / ARPF / SIDF55, EIR60, NEF65, Vendor server70, and Vendor model storage75. The operation sequence of these devices will be described later.

[0026] Note that since ARPF (Authentication Credential Repository and Processing Function) and SIDF (Subscriber Identity De-concealing Function) are both functional elements of UDM55, they are written as UDM / ARPF / SIDF55. Also, Vendor server 70 is one of AF80.

[0027] (Outline of the Embodiment) In this embodiment, in order to solve the above problems, a method is introduced in which the inference model acquisition procedure is initiated on the network side. The outline of the specific process is as follows. The AI ​​model described below may also be called an inference model or an AI inference model.

[0028] UE20 sends a device trigger subscription request to AMF35 regarding an AI model update. The device trigger subscription request includes a newly introduced SVNAI (Software Version Number for AI). SVNAI is an example of software information about the AI ​​model.

[0029] SVNAI includes "the ability to apply an AI model as a terminal capability, or from the perspective of what UE20 currently owns, or both," "the identifier of the AI ​​model owned by UE20 for said AI application capability," and "the version number of said AI model." The AI ​​model identifier includes the identifier (name) of the vendor providing said AI model.

[0030] Furthermore, SVNAI may include, or may include at least one of, "the function of applying an AI model as a terminal capability, or from the perspective of an AI model currently owned by UE20, or both," "the identifier of the AI ​​model owned by UE20 for said AI application function," and "the version number of said AI model." In addition, SVNAI may include, separately from the AI ​​model identifier, the identifier (name) of the vendor providing said AI model.

[0031] The AMF35 sends a request message to the SMF40, along with auxiliary information (e.g., the vendor's name), so that the SMF40 can forward the device trigger subscription request to the AF80, which is installed separately for each terminal manufacturing vendor.

[0032] When AF80 detects an AI model update, it sends a device trigger to UE20 containing information about the newly available inference model and the recommended waiting time until the inference model is acquired. AF80 may send the device trigger at different times for each UE20. UE20 then initiates the inference model acquisition procedure as appropriate, based on the recommended waiting time until the inference model is acquired.

[0033] Furthermore, UE20 manages SVNAI. UE20 updates SVNAI when a new AI model is added, or when a new version of an already stored AI model is added.

[0034] Furthermore, the method of notification from AF80 to UE20 when an AI model update is detected is not limited to device triggers. Notification may be given by methods other than device triggers.

[0035] (Operation Example) An example of the operation of the communication system in this embodiment will be described in detail with reference to the sequence diagrams in Figures 4 to 8.

[0036] <Initial Registration and Subscription> First, the procedure for initial registration and subscription will be explained with reference to Figures 4 to 7.

[0037] In step 1 (S1) of Figure 4, UE20 sends an RRCSetupRequest to gNB10. In step 2 (S2), gNB10 sends an RRCSetup to UE20.

[0038] In S3, UE20 sends RRCSetupComplete (dedicatedNAS-Message(Registration request)) to gNB10.

[0039] In S4, gNB10 sends an Initial UE message (NAS-PDU (Registration request)) to AMF35. In S5, AMF35 sends a Nausf_UEAuthentication_Authenticate request to AUSF50.

[0040] In S6, AUSF50 sends a Nudm_UEAuthentication_Get request to UDM / ARPF / SIDF55. In S7, UDM / ARPF / SIDF55 sends a Nudm_UEAuthentication_Get response to AUSF50.

[0041] In S8, AUSF50 sends a Nausf_UEAuthentication_Authenticate response to AMF35. In S9, AMF35 sends a Downlink NAS Transport (NAS-PDU (Authentication request)) to gNB10.

[0042] In S10, gNB10 sends DLInformationTransfer(dedicatedNAS-Message(Authentication request)) to UE20. In S11, UE20 sends ULInformationTransfer(dedicatedNAS-Message(Authentication response)) to gNB10.

[0043] In S12, gNB10 sends an Uplink NAS Transport (dedicatedNAS-Message (Authentication response)) to AMF35. In S13, AMF35 sends a Nausf_UEAuthentication_Authenticate request to AUSF50.

[0044] In step S14, AUSF 50 transmits a Nausf_UEAuthentication_Authenticate response to AMF 35. In step S15, AUSF 50 transmits a Nudm_UEAuthentication_ResultConfirmation request to UDM / ARPF / SIDF 55.

[0045] In step S16, UDM / ARPF / SIDF 55 transmits a Nudm_UEAuthentication_ResultConfirmation response to AUSF 50. In step S17, AMF 35 transmits an Initial Context Setup request to gNB 10.

[0046] In step S18, gNB 10 transmits a SecurityModeCommand to UE 20. In step S19, UE 20 transmits a SecurityModeComplete to gNB 10.

[0047] In step S20, gNB 10 transmits an Initial Context Setup response to AMF 35. In step S21, AMF 35 transmits Downlink NAS Transport (NAS-PDU (Security Mode Command)) to gNB 10. In step S22, gNB 10 transmits DLInformationTransfer (dedicatedNAS-Message (Security Mode Command)) to UE 20.

[0048] In S23 of FIG. 5, the UE 20 transmits ULInformationTransfer to the gNB 10. The ULInformationTransfer includes "dedicatedNAS-Message(Security Mode Complete(NAS message container(Registration request), NAS message container2(Control Plane Service request(Payload container type(CIoT user data container), Payload container(user data container(Nadrf_MLModelManagement_RetrievalRequest_Subscribe request(SVNAI=bb))), nefTargetAf(Vendor server)))))".

[0049] In S24, the gNB 10 transmits Uplink NAS Transport to the AMF 35. The Uplink NAS Transport includes "dedicatedNAS-Message(Security Mode Complete(NAS message container(Registration request), NAS message container2(Control Plane Service request(Payload container type(CIoT user data container), Payload container(user data container(Nadrf_MLModelManagement_RetrievalRequest_Subscribe request(SVNAI=bb))), nefTargetAf(Vendor server)))))".

[0050] In S23 and S24, the message transmitted from the UE 20 to the AMF 35 via the gNB 10 includes "a request message for setting a route on the control plane for a server installed for each vendor".

[0051] Furthermore, in S23 and S24, the message sent from UE20 to AMF35 via gNB10 includes "a message that includes SVNAI and a request to send a notification message to UE20 when the version number of the inference model is updated."

[0052] AMF35 obtains the PEI (e.g., IMEI, IMEISV) from UE20 in steps S25 to S34 below. AMF35 also obtains the SVNAI from UE20 in steps S25 to S34 below. In step S35, described later, AMF35 uses the PEI or SVNAI to determine the vendor that provides the "Vendor server" for the inference model used by UE20. The "Vendor server" is a server installed for each vendor.

[0053] In S25, AMF35 sends a Downlink NAS Transport to gNB10. The Downlink NAS Transport includes "NAS-PDU(Identity request(Identity type=IMEISV, Software type=SVNAI))".

[0054] In S26, gNB10 sends DLInformationTransfer to UE20. DLInformationTransfer contains "NAS-PDU(Identity request(Identity type=IMEISV, Software type=SVNAI))".

[0055] In S27, UE20 sends ULInformationTransfer to gNB10. ULInformationTransfer contains "NAS-PDU(Identity response(Mobile identity(IMEISV=aa), Software version(SVNAI=bb)))".

[0056] In S28, gNB10 sends an Uplink NAS Transport to AMF35. The Uplink NAS Transport includes "NAS-PDU(Identity response(Mobile identity(IMEISV=aa), Software version(SVNAI=bb)))".

[0057] In S28, the message received by AMF35 is an example of a message that includes "the device identifier of a terminal, or information about the software of the inference model used by the terminal, or both the device identifier and the information."

[0058] In S29, AMF35 sends an N5g-eir_EquipmentIdentityCheck_Get request to EIR60. In S30, EIR60 sends an N5g-eir_EquipmentIdentityCheck_Get response to AMF35.

[0059] In S31, AMF35 sends a Nudm_UECM_Registration request to UDM / ARPF / SIDF55. In S32, UDM / ARPF / SIDF55 sends a Nudm_UECM_Registration response to AMF35.

[0060] In S33, AMF35 sends a Nudm_SDM_Get request to UDM / ARPF / SIDF55. In S34, UDM / ARPF / SIDF55 sends a Nudm_SDM_Get response to AMF35.

[0061] In S35, AMF35 derives information supplementing the "Vendor server" from PEI (or SVNAI) (e.g., vendor name, or AI function name, or both vendor name and AI function name).

[0062] Based on the Control Plane Service request received in S24, the AMF35 initiates the NIDD (Non-IP Data Delivery) procedure as follows:

[0063] In S36 of Figure 6, AMF35 sends an Nsmf_PDUSession_CreateSMContext request to SMF40. The Nsmf_PDUSession_CreateSMContext request includes "nefTargetAf(Vendor server), nefTargetAfAddInfo(vendor name=cc, AI function name=dd)".

[0064] The message sent from AMF35 to SMF40 in S36 is an example of a "request message that adds the vendor's name to a request message for setting up a route on the C plane to a server installed by each vendor."

[0065] In S37, SMF40 sends an Nsmf_PDUSession_CreateSMContext response to AMF35.

[0066] In S38, SMF40 uses the nefTargetAf and nefTargetAfAddInfo received in S36 to refer to local information and derive the IP address of the destination Vendor server 70.

[0067] In S39, SMF40 sends an Nnef_SMContext_Create request (nefTargetAfIpAddress(Vendor server IP address)) to NEF65. The message sent from SMF40 to NEF65 in S39 is a message requesting Vendor server 70 to configure a route on the C plane, and includes the IP address of Vendor server 70.

[0068] In S40, NEF65 sends an Nnef_SMContext_Create response to SMF40.

[0069] In S41, SMF40 sends a Namf_Communication_N1N2MessageTransfer request to AMF35. In S42, AMF35 sends a Namf_Communication_N1N2MessageTransfer response to SMF40.

[0070] According to steps S43 to S46 below, NEF65 connects to Vendor server 70.

[0071] In S43, NEF65 sends an Nnef_NIDDConfiguration_TriggerNotify request to Vendor server70. In S44, Vendor server70 sends an Nnef_NIDDConfiguration_TriggerNotify response to NEF65.

[0072] In S45, Vendor server 70 sends an Nnef_NIDDConfiguration_Create request to NEF65. In S46, NEF65 sends an Nnef_NIDDConfiguration_Create response to Vendor server 70.

[0073] In S47 of Figure 7, AMF35 sends an Nsmf_PDUSession_SendMOData request to SMF40. The Nsmf_PDUSession_SendMOData request includes "SendMoDataReqData(moData(RefToBinaryData), Nadrf_MLModelManagement_RetrievalRequest_Subscribe request(SVNAI=bb))".

[0074] In S48, SMF40 sends an Nsmf_PDUSession_SendMOData response to AMF35.

[0075] In S49, SMF40 sends an Nnef_SMContext_Delivery request to NEF65. The Nnef_SMContext_Delivery request includes "data(RefToBinaryData), Nadrf_MLModelManagement_RetrievalRequest_Subscribe request(SVNAI=bb)".

[0076] In S50, NEF65 sends an Nnef_SMContext_Delivery response to SMF40.

[0077] In S51, NEF65 sends an Nnef_NIDD_DeliveryNotify request to Vendor server70. The Nnef_NIDD_DeliveryNotify request includes "NiddUplinkDataNotification(data(Nadrf_MLModelManagement_RetrievalRequest_Subscribe request(SVNAI=bb)))".

[0078] In S51, the message that Vendor server 70 receives from NEF65 is an example of a subscription message that includes information about the software used by UE20 and a request to notify UE20 when the version number of the inference model is updated.

[0079] In S52, the Vendor server 70 accepts event subscriptions related to version updates of the AI ​​model held by UE20, based on the SVNAI received in S51.

[0080] In S53, the Vendor server 70 sends an Nnef_NIDD_DeliveryNotify response to the NEF 65.

[0081] In S54, Vendor server 70 sends an Nnef_NIDD_Delivery request to NEF65. The Nnef_NIDD_Delivery request includes "NiddDownlinkDataTransfer(data(Nadrf_MLModelManagement_RetrievalRequest_Subscribe response))". In S55, NEF65 sends an Nnef_NIDD_Delivery response to Vendor server 70.

[0082] In S56, NEF65 sends an Nsmf_NIDD_Delivery request to SMF40. The Nsmf_NIDD_Delivery request includes a "DeliverReqData(mtData(RefToBinaryData)), Nadrf_MLModelManagement_RetrievalRequest_Subscribe response". In S57, SMF40 sends an Nsmf_NIDD_Delivery response to NEF65.

[0083] In S58, SMF40 sends a Namf_Communication_N1N2MessageTransfer request to AMF35. The Namf_Communication_N1N2MessageTransfer request includes "N1N2MessageTransferReqData(mtData(RefToBinaryData)), Nadrf_MLModelManagement_RetrievalRequest_Subscribe response". In S59, AMF35 sends a Namf_Communication_N1N2MessageTransfer response to SMF40.

[0084] In S60, AMF35 sends a Downlink NAS Transport to gNB10. The Downlink NAS Transport includes "NAS-PDU(Registration accept(NAS message container2(Service accept(Payload container type(CIoT user data container), Payload container(user data container(Nadrf_MLModelManagement_RetrievalRequest_Subscribe response))))))".

[0085] In S61, gNB10 sends DLInformationTransfer to UE20. DLInformationTransfer contains "dedicatedNAS-Message(Registration accept(NAS message container2(Service accept(Payload container type(CIoT user data container), Payload container(user data container(Nadrf_MLModelManagement_RetrievalRequest_Subscribe response))))))".

[0086] <Device Trigger> The procedure for device triggering will be explained with reference to Figure 8.

[0087] In S71 of Figure 8, the Vendor server 70 detects an update to the version number of the AI ​​model held by UE20. The Vendor server 70 may also derive the waiting time until the AI ​​model acquisition procedure is started for each UE. Alternatively, the Vendor server 70 may also derive the waiting time until the following message is sent for each UE.

[0088] In S72, the Vendor server 70 sends an Nnef_Trigger_Delivery request to the NEF 65. The Nnef_Trigger_Delivery request includes "DeviceTriggering(triggerPayload (Nadrf_MLModelManagement_RetrievalRequest_Notify request(updated AI model identifier, version number of the updated AI model identifier, wait-timer, FQDN of the vendor model storage)))".

[0089] The message sent to NEF65 in S72 is an example of a "notification message addressed to UE20, which includes the identifier of the updated inference model and the updated version number of the inference model."

[0090] `wait-timer` is an example of a recommended waiting time for UE20 to begin the process of retrieving the inference model after receiving a message containing `wait-timer`. `FQDN of the vendor model storage` is the FQDN of Vendor model storage 75 (the inference model storage server).

[0091] In S73, the Device triggering procedure via Nnef (Non-Patent Literature 1 (TS 23.502, 4.13.2.2)) is executed. That is, a device trigger message including "updated AI model identifier, version number of the updated AI model identifier, wait-timer, FQDN of the vendor model storage" is sent from the Vendor server 70 to the UE20 via the AMF35 and gNB10.

[0092] In S74, UE20 receives the above message, waits for the duration of the wait timer, and then initiates the AI ​​model acquisition procedure.

[0093] In S75, UE20 sends a Nadrf_MLModelManagement_RetrievalRequest request (UE NR AImodel identifier) ​​to the Vendor model storage 75.

[0094] In S76, the Vendor model storage 75 sends a Nadrf_MLModelManagement_RetrievalRequest response (AI model) to UE20.

[0095] In S77, internal processing is performed between the Vendor server 70 and the Vendor model storage 75, and in S78, the Vendor server 70 updates the version number of the AI ​​model held by UE20 and continues the subscription.

[0096] (Effects of the Embodiment) The technology according to this embodiment provides a technology for delivering an inference model to a terminal in a wireless communication system. Furthermore, the technology according to this embodiment can reduce the possibility of causing network congestion compared to a method in which the terminal initiates the inference model acquisition procedure.

[0097] (Device Configuration) Next, an example of the functional configuration of the network node 100 and UE 20 (hereinafter referred to as terminal 20) that perform the processing and operations described above will be explained. The network node 100 corresponds to, for example, AMF35, SMF40, NEF65, AF80, and Vendor server 70. However, the network node 100 is not limited to AMF35, SMF40, NEF65, AF80, and Vendor server 70.

[0098] <Network Node 100> Figure 9 is a diagram showing an example of the functional configuration of network node 100. As shown in Figure 9, network node 100 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 9 is merely an example. Any functional classification and functional unit names are acceptable as long as they enable the operation according to the embodiment of the present invention.

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

[0100] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20 or other network nodes in a storage device, and reads it from the storage device as needed. The control unit 140 controls the network node 100. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120. The transmission unit 110 and the reception unit 120 may also be called the transmitter and receiver, respectively.

[0101] <Terminal 20> Figure 10 is a diagram showing an example of the functional configuration of terminal 20. As shown in Figure 10, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 10 is merely an example. Any functional classification and functional unit names are acceptable as long as they enable the operation according to the embodiment of the present invention.

[0102] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly (or via wire). The receiving unit 220 receives various signals wirelessly (or via wire) and acquires signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals or reference signals transmitted from the base station. A communication unit including the transmitting unit 210 and the receiving unit 220 may be configured.

[0103] The setting unit 230 stores various setting information received from base stations, etc., by the receiving unit 220 in its storage device and reads it from the storage device as needed. The setting unit 230 also stores pre-set setting information.

[0104] The control unit 240 controls the terminal 20. The signal transmission function of the control unit 240 may be included in the transmission unit 210, and the signal reception function of the control unit 240 may be included in the reception unit 220. The transmission unit 210 and the reception unit 220 may also be called the transmitter and receiver, respectively.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0128] Furthermore, if the communication module 2013 includes a network node 100 (or terminal 20), the communication module 2013 can perform the operations of the aforementioned network node 100 (or terminal 20).

[0129] This specification discloses at least the configurations described in Appendix 1 and Appendix 2 below.

[0130] <Note 1: Terminal side> (Note 1) A terminal that uses an inference model, comprising a control unit that manages information about the software of the inference model, and a transmission unit that transmits the information to a network node via a base station. (Note 2) The terminal according to Note 1, wherein the information includes the function by which the terminal applies the inference model, the name of the vendor that provides the inference model, an identifier for the inference model, or the version number of the inference model indicated by the identifier. (Note 3) The terminal according to Note 2, wherein the information includes the version number, and the transmission unit transmits a message to the network node via the base station, which includes the information and a request to send a notification message to the terminal when the version number is updated. (Note 4) The terminal according to Note 3, further comprising a receiving unit that receives the notification message from the network node via the base station, which includes a recommended value for the waiting time until the inference model is acquired, and the control unit starts a procedure for acquiring the inference model after the waiting time has elapsed since receiving the notification message. (Note 5) The terminal according to Note 1, wherein when the terminal stores a new inference model or a new version of an inference model already stored, the control unit updates the information relating to the software for the inference model used by the terminal. (Note 6) A communication method performed by a terminal using an inference model, comprising the steps of: managing information relating to the software for the inference model; and transmitting the information to a network node via a base station.

[0131] The network node in appendices 1 to 6 is, for example, an AMF35. Any of appendices 1 to 6 provides a technology for delivering inference models to terminals in a wireless communication system. According to appendice 2, the software information about the inference model may include the function that the terminal applies the inference model to, the name of the vendor providing the inference model, the identifier of the inference model, or the version number of the inference model indicated by the identifier.

[0132] According to Appendix 3, it is possible to request notification when the version number is updated. According to Appendix 4, the procedure for obtaining the inference model can be initiated after a specified waiting period has elapsed. According to Appendix 5, it is possible to keep the software information about the inference model used by the terminal up to date.

[0133] <Note 2: Network side> (Note 1) A network node comprising: a receiving unit that receives a message from a terminal via a base station that includes the device identifier of the terminal, or information about the software of the inference model used by the terminal, or both the device identifier and the information; and a control unit that derives the name of the vendor that provides the inference model used by the terminal based on the device identifier or the information. (Note 2) The network node according to Note 1, further comprising: a transmitting unit that receives a request message from the terminal via the base station for setting up a route on the C plane to a server installed for each vendor, and transmits the request message with the vendor's name added to it to a specific network node.

[0134] The target network node in appendices 1 and 2 is, for example, AMF35. The specific network node is, for example, SMF40. (Appendix 3) A network node comprising: a receiving unit that receives a request message from a first network node, including the name of the vendor, for setting up a route on the C plane to a server installed for each vendor; a control unit that derives the IP address of the server from the name of the vendor; and a transmitting unit that sends a message to a second network node, including the IP address, requesting the setting up of the route.

[0135] The target network node in Appendix 3 is, for example, SMF40. The first network node is, for example, AMF35. The second network node is, for example, NEF65. (Appendix 4) A network node comprising: a receiving unit that receives a subscription message from a specific network node, which includes information about the software of the inference model used by the terminal, generated by the terminal, and a request to notify the terminal when the version number of the inference model is updated; a control unit that detects that the version number of the inference model has been updated; and a transmitting unit that sends a notification message to the specific network node, which includes the identifier of the updated inference model and the updated version number of the inference model, addressed to the terminal. (Appendix 5) The network node according to Appendix 4, wherein the notification message includes a recommended value for the waiting time until the terminal acquires the inference model. (Appendix 6) The network node according to Appendix 4, wherein the notification message includes the FQDN of an inference model storage server installed for each vendor, and the terminal acquires the inference model from the inference model storage server.

[0136] The target network node in appendices 4 to 6 is, for example, Vendor server 70. The specific network node is, for example, NEF65.

[0137] Any of the appendices 1 to 6 provides a technology for delivering inference models to a terminal in a wireless communication system. According to appendice 2, a request message with the vendor's name added can be sent. According to appendice 5, a waiting time can be instructed to the terminal. According to appendice 6, the terminal can access the inference model storage server using the FQDN.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0158] Either the network node 100 or the terminal 20 may be called a transmitting device, receiving device, communication device, etc. Furthermore, any one of the base station 10, network node 100, or terminal 20 may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes cases where the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that autonomously drives based on operational commands. Furthermore, the mobile entity may be a vehicle (e.g., a car, an airplane), an unmanned mobile entity (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). Note that 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0172] This patent application claims priority based on Japanese Patent Application No. 2025-030638, filed on 27 February 2025, and the entire contents of Japanese Patent Application No. 2025-030638 are incorporated herein by reference.

[0173] 10 RAN (Base Station, gNB) 20 Terminal, UE 30 UPF 35 AMF 40 SMF 45 PCF 50 AUSF 55 UDM / ARPF / SIDF 60 EIR 65 NEF 70 Vendor server 75 Vendor model storage 80 AF 100 Network node 110 Transmitter 120 Receiver 130 Configuration unit 140 Control unit 210 Transmitter 220 Receiver 230 Configuration unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims

1. A terminal that uses an inference model, comprising: a control unit that manages information regarding the software of the inference model; and a transmission unit that transmits the information to a network node via a base station.

2. The terminal according to claim 1, wherein the information includes a function of the terminal to apply the inference model, the name of the vendor providing the inference model, an identifier for the inference model, or the version number of the inference model indicated by the identifier.

3. The terminal according to claim 2, wherein the information includes the version number, and the transmitting unit transmits a message to the network node via the base station, the message including the information and a request to send a notification message to the terminal when the version number is updated.

4. The terminal according to claim 3, further comprising a receiving unit that receives the notification message from the network node via the base station, which includes a recommended value for the waiting time until the inference model is obtained, wherein the control unit starts a procedure for obtaining the inference model after the waiting time has elapsed since receiving the notification message.

5. The terminal according to claim 1, wherein when the terminal stores a new inference model or a new version of an inference model already stored, the control unit updates the information relating to the software for the inference model used by the terminal.

6. A communication method performed by a terminal using an inference model, comprising the steps of: managing information relating to the software of the inference model; and transmitting the information to a network node via a base station.

Images