WO2023145187A1 - ソフトウェア更新システム、通信装置、及び更新情報のデータ構造、ソフトウェア更新方法 - Google Patents

ソフトウェア更新システム、通信装置、及び更新情報のデータ構造、ソフトウェア更新方法 Download PDF

Info

Publication number
WO2023145187A1
WO2023145187A1 PCT/JP2022/041498 JP2022041498W WO2023145187A1 WO 2023145187 A1 WO2023145187 A1 WO 2023145187A1 JP 2022041498 W JP2022041498 W JP 2022041498W WO 2023145187 A1 WO2023145187 A1 WO 2023145187A1
Authority
WO
WIPO (PCT)
Prior art keywords
update
information
communication device
identification information
control software
Prior art date
Application number
PCT/JP2022/041498
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
政彦 大西
Original Assignee
住友電気工業株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 住友電気工業株式会社 filed Critical 住友電気工業株式会社
Priority to JP2023576630A priority Critical patent/JPWO2023145187A1/ja
Publication of WO2023145187A1 publication Critical patent/WO2023145187A1/ja

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network

Definitions

  • the present disclosure relates to a software update system, a communication device, a data structure of update information, and a software update method.
  • Patent Document 1 discloses wireless firmware update (FOTA: Firmware Over-The-Air) in wireless communication equipment for cellular communication.
  • FOTA Firmware Over-The-Air
  • a software update system includes a communication device connectable to a mobile communication network, and a server that provides the communication device with update information used to update control software for the communication device,
  • the communication device includes an acquisition unit that acquires first carrier identification information for identifying a carrier that provides the mobile communication network to which the communication device connects, and the control software that can be provided to the communication device.
  • a first requesting unit for requesting the server to provide the update information in which the second operator identification information corresponding to the specified second operator identification information, the first operator identification information, and the second operator identification a second request unit for requesting provision of update data for updating the control software corresponding to the second operator identification information when the information matches, and the received update data, an updating unit for updating the control software for the communication device.
  • a communication device is a communication device connectable to a mobile communication network, and is a first operator for identifying a communication carrier that provides the mobile communication network to which the communication device connects.
  • an acquisition unit that acquires identification information; a first request unit that requests a server to provide update information in which second operator identification information corresponding to the control software that can be provided to the communication device is specified; Providing update data for updating the control software corresponding to the second operator identification information when the first operator identification information and the second operator identification information match. and an updating unit for updating the control software for the communication device according to the received update data.
  • a data structure of update information is a data structure of update information used for updating control software of a communication device connectable to a mobile communication network, the control software that can be provided to the communication device.
  • the first operator identification information identifies the communication operator that provides the mobile communication network corresponding to the control software used by the communication device for updating. It is used in a process of comparison with the second operator identification information obtained by the communication device to determine.
  • a software update method for update information includes: a communication device connectable to a mobile communication network; a server that provides the communication device with update information used to update control software for the communication device; a software update method for a software update system comprising a step of acquiring first carrier identification information for identifying a carrier that provides the mobile communication network to which the communication device is connected; requesting the server to provide the update information in which the second operator identification information corresponding to the control software that can be provided to the communication device is specified; the first operator identification information; requesting provision of update data for updating the control software corresponding to the second operator identification information if the second operator identification information matches; and the received update. and updating the control software for the communication device with the data.
  • FIG. 1 is a diagram showing an example of the configuration of a software update system according to an embodiment.
  • FIG. 2 is a diagram for explaining the format of the S-NSSAI.
  • FIG. 3 is a diagram showing the correspondence between SST values and slice types.
  • 4 is a block diagram illustrating an example of a hardware configuration of a gateway according to the embodiment;
  • FIG. 5 is a block diagram illustrating an example of a hardware configuration of a server according to the embodiment;
  • FIG. FIG. 6 is a functional block diagram showing an example of functions of the software update system according to the embodiment.
  • FIG. 7 is a diagram showing an example of an update list.
  • FIG. 8A is a flowchart showing the first half of an example of FW update determination processing by the GW according to the embodiment.
  • FIG. 8A is a flowchart showing the first half of an example of FW update determination processing by the GW according to the embodiment.
  • FIG. 8B is a flowchart illustrating the second half of an example of FW update determination processing by the GW according to the embodiment.
  • FIG. 9 is a flowchart illustrating an example of FW update processing by the GW according to the embodiment.
  • FIG. 10 is a diagram showing a first modification of the update list.
  • FIG. 11 is a diagram showing a second modification of the update list.
  • 5G 5th generation mobile communication system
  • 4G 4th generation mobile communication system
  • cellular communication also called “cellular communication”.
  • 5G 5th generation mobile communication system
  • 4G 4th generation mobile communication system
  • communication carriers Each of multiple cellular communication carriers (hereinafter also referred to as “communication carriers”) provides control software (firmware) that has been verified to work with cellular communication, and users can install firmware that has been verified to operate. It was necessary to incorporate it into the communication device.
  • a software update system comprises a communication device connectable to a mobile communication network, and a server that provides the communication device with update information used to update control software for the communication device.
  • the communication device comprises an acquisition unit for acquiring first carrier identification information for identifying a carrier that provides the mobile communication network to which the communication device is connected; a first requesting unit for requesting the server to provide the update information in which the second operator identification information corresponding to the software is specified; the first operator identification information; and the second operator. a second request unit for requesting provision of update data for updating the control software corresponding to the second operator identification information when the identification information matches the received update data; , an updater for updating the control software for the communication device.
  • the communication device can identify the control software provided by the carrier of the mobile communication network to which the communication device is connected, and update to the identified control software. Therefore, updating of the control software of the communication device becomes efficient.
  • PLMN Public Land Mobile Network
  • the acquisition unit obtains the second operator identification information
  • the acquisition unit further acquires the Home PLMN, and the first request unit provides the update information corresponding to the Home PLMN acquired by the acquisition unit, may be requested.
  • the update information only needs to include the Home PLMN and the Visited PLMN of the roaming destination that can be used in the Home PLMN as carrier identification information, so the carrier identification information in the update information is limited, and the data volume of the update information is reduced. can be suppressed.
  • the second request unit is different from the Visited PLMN and the Home PLMN acquired by the acquisition unit, and the PLMN specified in the update information and the acquisition unit If the Visited PLMN obtained by is consistent with the Visited PLMN, a request may be made to provide the update data for updating the control software corresponding to the Visited PLMN.
  • the control software of the communication device can be updated to control software compatible with the Visited PLMN.
  • the communication device can be set to either a first mode or a second mode, and the second request unit is set to the first mode.
  • the update for updating to the control software corresponding to the Visited PLMN when the provision of data is requested and the second mode is set, when the PLMN specified in the update information and the Home PLMN acquired by the acquisition unit match, Provision of the update data for updating the control software corresponding to the Home PLMN may be requested.
  • the control software of the communication device can be updated to control software compatible with the Visited PLMN.
  • the control software of the communication device can be updated to the control software compatible with the Home PLMN regardless of whether the communication device is receiving roaming service by the Visited PLMN.
  • the acquisition unit further acquires model information of the communication device, and the first request unit acquires the model type acquired by the acquisition unit.
  • the server may be requested to provide the update information corresponding to the information.
  • the acquisition unit further acquires slice information indicating a network slice set in the communication device, and the update information is sent to the communication device
  • the second operator identification information and slice information indicating a network slice corresponding to the control software are specified in the control software that can be provided, and the second request unit is configured to identify the first operator
  • the control software is updated to correspond to the second operator identification information and the slice information. You may request the provision of updated data for Thereby, when a specific network slice is set in the communication device, the control software of the communication device can be updated to the control software corresponding to the network slice.
  • the communication device when the first business identification information and the second business identification information match, further comprising a notification unit for notifying the user that the control software corresponding to the second operator identification information can be updated, wherein the second request unit corresponds to the second operator identification information
  • the provision of the update data may be requested when an instruction to update the control software is received from the user. This allows the user to determine whether or not the control software needs to be updated.
  • a communication device is a communication device connectable to a mobile communication network, and is a first business for identifying a communication carrier that provides the mobile communication network to which the communication device connects.
  • a first requesting unit that requests a server to provide update information in which second business identification information corresponding to the control software that can be provided to the communication device is specified; , when the first business identification information and the second business identification information match, update data for updating the control software corresponding to the second business identification information.
  • the data structure of update information is a data structure of update information used for updating control software of a communication device connectable to a mobile communication network, and the control data structure that can be provided to the communication device.
  • a first operator identification information for identifying a communication operator that provides the mobile communication network corresponding to the software, wherein the first operator identification information is the control software used by the communication device for updating is used in the process of comparing with the second business identification information acquired by the communication device to determine the
  • the communication device can identify the control software provided by the carrier of the mobile communication network to which the communication device is connected, and update to the identified control software. can be done. Therefore, updating of the control software of the communication device becomes efficient.
  • a software update method for update information provides a communication device connectable to a mobile communication network and update information used for updating control software for the communication device to the communication device.
  • a software update method for a software update system comprising a server, the step of acquiring first carrier identification information for identifying a carrier that provides the mobile communication network to which the communication device is connected. and the control software that can be provided to the communication device, requesting the server to provide the update information in which the second operator identification information corresponding to the specified second operator identification information is specified; and the first operator identification information. and the second operator identification information match, a step of requesting provision of update data for updating the control software corresponding to the second operator identification information; and updating the control software for the communication device with the updated data.
  • the communication device can identify the control software provided by the carrier of the mobile communication network to which the communication device is connected, and update to the identified control software. Therefore, updating of the control software of the communication device becomes efficient.
  • FIG. 1 is a diagram showing an example of the configuration of a software update system according to an embodiment.
  • Software update system 10 includes gateways (hereinafter also referred to as “GW”) 100A, 100B, 100C and server 600 .
  • GW gateways
  • GW100A, 100B, and 100C are communication devices capable of cellular communication.
  • GWs 100A, 100B, and 100C are arranged in factories or commercial facilities.
  • the facilities where the GWs 100A, 100B, and 100C are arranged are owned and operated by one operator (company).
  • the GW 100A is arranged at the facility of the base a.
  • the GW 100B is arranged at the facility of the base b.
  • the GW 100C is arranged at the facility of the base c.
  • base a and base b exist in different regions (for example, different prefectures) in the same country (Japan).
  • Site c is in a different country (eg, USA) than sites a and b.
  • GW 100A is connectable to carrier A's cellular network (cellular NW) 400A
  • GW 100B is connectable to carrier A's cellular network 400A
  • GW 100C is connectable to carrier C's cellular network 400C.
  • Cellular networks 400A and 400C are 5G mobile communication networks.
  • Each of the cellular networks 400A, 400C includes a core network and a RAN (Radio Access Network) and is connected to the Internet 500.
  • the RAN of cellular network 400A includes radio base stations 300A and 300B, and the RAN of cellular network 400C includes radio base station 300C.
  • GW 100A is connected to cellular network 400A via radio base station 300A
  • GW 100B is connected to cellular network 400A via radio base station 300B
  • GW 100C is connected to cellular network 400C via radio base station 300C. connected to
  • a core network of each of the cellular networks 400A and 400C includes UDM (Unified Data Management) 410A and 410C.
  • UDMs 410A and 410C manage subscriber information.
  • UDM 410A When establishing a communication connection session between GW 100A, 100B and cellular network 400A, UDM 410A notifies GW 100A, 100B of the Visited PLMN of the connection destination.
  • UDM 410C When establishing a communication connection session between GW 100C and cellular network 400C, UDM 410C notifies GW 100C of the Visited PLMN of the connection destination.
  • PLMN Public Land Mobile Network
  • MCC Mobile Country Number
  • MNC Mobile Network Code
  • Home PLMN is the identification information of the telecommunications carrier with whom the subscriber has a contract for cellular communication services.
  • Visited PLMN is the identification information of the roaming destination telecommunications carrier.
  • MVNO Mobile Virtual Network Operator
  • the Visited PLMN is the identification information of the MVNO. If you are subscribed to the cellular communication service of an MNO (Mobile Network Operator) and connect to the MNO's cellular network (not roaming), the Visited PLMN is the identification information of the MNO and matches the Home PLMN.
  • the GW 100A located at the site a subscribes to the cellular communication service provided by the telecommunications carrier A and connects to the cellular network 400A of the telecommunications carrier A.
  • Carrier A is an MNO, and carrier A owns cellular network 400A.
  • GW 100B located at site b subscribes to the cellular communication service provided by telecommunications carrier B and connects to cellular network 400A.
  • Carrier B is an MVNO.
  • Carrier B rents cellular network 400A from carrier A and provides connection services to cellular network 400A to subscribers.
  • the GW 100C located at the base c subscribes to the cellular communication service provided by the telecommunications carrier A, and makes a roaming connection to the cellular network 400C of the telecommunications carrier C.
  • FIG. The Home PLMN and Visited PLMN of GW 100A both indicate carrier A.
  • the Home PLMN of GW 100B indicates carrier A, and the Visited PLMN of GW 100B indicates carrier B.
  • the Home PLMN of GW 100C indicates carrier A, and the Visited PLMN of GW 100C indicates carrier C.
  • network slicing is performed to virtualize networks, divide network resources, and allocate logical networks (network slices, hereinafter also referred to as "slices") to User Equipment (UE), which is a mobile station.
  • UE User Equipment
  • slice information hereinafter referred to as "slice setting information"
  • GW 100A, 100B, 100C is transmitted, and GW 100A, 100B, 100C selects the requested slice based on the slice setting information.
  • FIG. 2 is a diagram for explaining the format of the S-NSSAI.
  • NSSAI includes multiple S-NSSAI (Single-NSSAI).
  • S-NSSAI includes SST (Slice/Service Type) and SD (Slice Differentiator).
  • SST is a number indicating the type of slice.
  • FIG. 3 is a diagram showing the correspondence between SST values and slice types. An SST value of "1" indicates eMBB (enhanced Mobile Broadband). eMBB is a slice of high-speed bulk communication.
  • An SST value of "2" indicates URL LLC (Ultra-Reliable and Low Latency Communications).
  • URLLC is a slice of reliable low-latency communication.
  • An SST value of "3" indicates mMTC (massive Machine Type Communications).
  • mMTC is a slice of multi-concurrent communication. Refer to FIG. 2 again. SD is slice definition information obtained by subdividing the slice type indicated by SST.
  • Each of the GWs 100A, 100B, and 100C is connected to a plurality of sensors 200 arranged within the facility.
  • Sensors 200 are, for example, cameras, temperature sensors, humidity sensors, motion sensors, pressure sensors, and vibration sensors.
  • the GWs 100A, 100B, 100C and the sensor 200 are connected by, for example, a LAN (Local Area Network).
  • the sensor 200 transmits data obtained by measurement (hereinafter referred to as "sensor data") to the GWs 100A, 100B, and 100C.
  • the GWs 100A, 100B, and 100C store the sensor data transmitted from the sensor 200 in a database (not shown) connected to the Internet 500 via a standard communication path (hereinafter referred to as 510A, 510B, and 510C (referred to as "first communication path").
  • a standard communication path hereinafter referred to as 510A, 510B, and 510C (referred to as "first communication path").
  • the GWs 100A, 100B, and 100C use communication means that are not standardized by the Third Generation Partnership Project, such as wireless LAN (Local Area Network), wired LAN, and Bluetooth (registered trademark) communication paths (hereinafter referred to as "second communication paths ) 520A, 520B, and 520C.
  • wireless LAN Local Area Network
  • wired LAN wired LAN
  • Bluetooth registered trademark
  • the server 600 is connected to the Internet 500.
  • the server 600 can download to the GWs 100A, 100B and 100C an update list (update information) used to update the control software (firmware, hereinafter also referred to as "FW") of the GWs 100A, 100B and 100C.
  • update list updated information
  • FW control software
  • the database 700 is connected to the Internet 500.
  • the database 700 stores update data for updating the FWs of the GWs 100A, 100B, and 100C.
  • the update data includes the updated FW and the FW installer.
  • Database 700 can download update data to GWs 100A, 100B, and 100C in response to requests from GWs 100A, 100B, and 100C.
  • GW100A, 100B, and 100C may be collectively referred to as "GW100".
  • Radio base stations 300A, 300B, and 300C may be collectively referred to as “radio base station 300”.
  • Cellular networks 400A and 400C may be collectively referred to as "cellular network 400”.
  • FIG. 4 is a block diagram showing an example of the hardware configuration of the gateway according to this embodiment.
  • GW 100 includes processor 101, nonvolatile memory 102, volatile memory 103, input/output interface (I/O) 104, first communication interface (I/F) 105, second communication interface (I/F ) 106.
  • I/O input/output interface
  • I/F first communication interface
  • I/F second communication interface
  • the volatile memory 103 is a semiconductor memory such as SRAM (Static Random Access Memory) or DRAM (Dynamic Random Access Memory).
  • the nonvolatile memory 102 is, for example, a flash memory, a hard disk, or a ROM (Read Only Memory).
  • the non-volatile memory 102 stores the FW 107 and data used to execute the FW 107 .
  • the non-volatile memory 102 stores the FW update program 108 and data used for executing the FW update program 108 .
  • the non-volatile memory 102 further stores a GW program 109 and data used to execute the GW program 109 .
  • the GW 100 is configured with a computer, and each function of the GW 100 is exhibited by the computer programs FW 107, FW update program 108, and GW program 109 stored in the storage device of the computer being executed by the processor 101. be done.
  • Each of the FW 107, the FW update program 108, and the GW program 109 can be stored in recording media such as flash memory, ROM, and CD-ROM.
  • GW 100 functions as a UE of cellular network 400 by processor 101 executing FW 107 .
  • the GW 100 can download the update data and update the firmware.
  • the GW program 109 By executing the GW program 109 by the processor 101, the GW 100 can collect sensor data from the sensors 200 and upload the collected sensor data to the database.
  • the processor 101 is, for example, a CPU (Central Processing Unit). However, the processor 101 is not limited to a CPU.
  • the processor 101 may be a GPU (Graphics Processing Unit).
  • the processor 101 may be, for example, an ASIC (Application Specific Integrated Circuit), or may include a programmable logic device such as a gate array or FPGA (Field Programmable Gate Array). In this case, the ASIC or programmable logic device is configured to be able to execute processing similar to at least one of the FW update program 108 and the GW program 109, for example.
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • the I/O 104 is connected to the sensor 200. Sensor data output from the sensor 200 is input to the I/O 104 . Sensor data input to the I/O 104 is provided to the processor 101 .
  • the first communication I/F 105 is a 5G-compliant wireless communication interface.
  • First communication I/F 105 includes a radio antenna and is capable of radio communication with radio base station 300 .
  • First communication I/F 105 can communicate with an external device through first communication path 510 including cellular network 400 .
  • the sensor data output from the sensor 200 is processed by the processor 101 or provided to the first communication I/F 105 without being processed by the processor 101 .
  • Processed or unprocessed sensor data is uploaded from the first communication I/F 105 to the database.
  • the second communication I/F 106 is, for example, an Ethernet interface (“ETHERNET” is a registered trademark), a wireless LAN interface, or a Bluetooth interface, and is a communication I/F that is not a standard established by the Third Generation Partnership Project. .
  • Second communication I/F 106 is connected to Internet 500 without going through cellular network 400 .
  • Second communication I/F 106 can communicate with an external device through second communication path 520 that does not include cellular network 400 .
  • FIG. 5 is a block diagram showing an example of the hardware configuration of the server according to this embodiment.
  • Server 600 includes processor 601 , nonvolatile memory 602 , volatile memory 603 , and communication interface (I/F) 604 .
  • I/F communication interface
  • the volatile memory 603 is a semiconductor memory such as SRAM or DRAM, for example.
  • the nonvolatile memory 602 is, for example, flash memory, hard disk, or ROM.
  • the non-volatile memory 602 stores a FOTA server program 605 and data used to execute the FOTA server program 605 .
  • a plurality of update lists 606 are also stored in the non-volatile memory 602 .
  • the server 600 is configured with a computer, and each function of the server 600 is exhibited by the processor 601 executing a FOTA server program 605, which is a computer program stored in the storage device of the computer.
  • the FOTA server program 605 can be stored in recording media such as flash memory, ROM, and CD-ROM.
  • FOTA server program 605 executed by processor 601 enables server 600 to download update list 606 to GW 100 .
  • the processor 601 is, for example, a CPU. However, the processor 601 is not limited to a CPU. Processor 601 may be a GPU. Processor 601 may be, for example, an ASIC, a gate array, or an FPGA programmable logic device. In this case, the ASIC or programmable logic device is configured to be able to execute processing similar to the FOTA server program 605 .
  • the communication I/F 604 is, for example, an Ethernet interface, a wireless LAN interface, or a Bluetooth interface, and is a communication I/F that is not a standard established by the Third Generation Partnership Project. Communication I/F 604 is connected to Internet 500 without going through cellular network 400 .
  • FIG. 6 is a functional block diagram showing an example of functions of the software update system according to the embodiment.
  • the GW 100 executes the FW update program 108, the GW 100 includes an acquisition unit 121, a first request unit 122, a first reception unit 123, a notification unit 124, an instruction reception unit 125, a second It functions as a request unit 126 , a second reception unit 127 and an update unit 128 .
  • the server 600 functions as a request receiving section 611 and an update information providing section 612 .
  • the acquisition unit 121 acquires the PLMN for identifying the telecommunications carrier that provides the cellular network 400 to which the GW 100 connects. Specifically, the acquisition unit 121 can acquire the Home PLMN and the Visited PLMN. For example, a SIM (Subscriber Identity Module) card stores a Home PLMN. The acquisition unit 121 can read Home PLMN from the SIM card attached to the GW 100 . The acquisition unit 121 can receive the Visited PLMN from the UDM 410 when establishing a communication connection session with the cellular network 400 .
  • SIM Subscriber Identity Module
  • the acquisition unit 121 can acquire the model information of the GW 100. Specifically, model information 110 is stored in the nonvolatile memory 102 (see FIG. 4). The acquisition unit 121 can read the model information 110 from the nonvolatile memory 102 .
  • the acquisition unit 121 can acquire the SST.
  • SST is an example of slice information indicating a slice set in GW 100 .
  • the acquiring unit 121 can receive the SST when establishing a communication connection session with the cellular network 400 .
  • the acquisition unit 121 can acquire the name (FW name) and version information of the FW 107 operating in the GW 100 .
  • the FW 107 installed in the nonvolatile memory 102 includes FW name and version information.
  • the acquisition unit 121 can acquire the FW name and version information from the FW 107 .
  • the first request unit 122 requests the server 600 to provide the update list 606 .
  • the update list 606 is information specifying the PLMN corresponding to each FW that can be provided to the GW 100 .
  • first request unit 122 generates a URL (Uniform Resource Locator) for downloading update list 606 .
  • the first request unit 122 generates a URL from the model information and Home PLMN acquired by the acquisition unit 121 .
  • the non-volatile memory 602 of the server 600 stores an update list 606 corresponding to the combination of the model information of the GW 100 and the Home PLMN. For example, if there are two models TYPE01 and TYPE02 and three MNOs of carriers A, C, and D, an update list 606 corresponding to the combination of TYPE01 and carrier A, and TYPE01 and carrier An update list 606 corresponding to a combination of Provider C, an update list 606 corresponding to a combination of TYPE01 and carrier D, an update list 606 corresponding to a combination of TYPE02 and carrier A, and TYPE02 and carrier C and an update list 606 corresponding to a combination of TYPE02 and carrier D are stored in non-volatile memory 602 .
  • the first requesting unit 122 when the acquiring unit 121 acquires the type information “TYPE01” and the PLMN “PLMN0” indicating the communication carrier A, the first requesting unit 122 generates a URL from “TYPE01” and “PLMN0”. This URL is information for downloading the update list 606 corresponding to the combination of TYPE01 and carrier A from the server 600 .
  • the first request unit 122 requests the server 600 to provide the update list 606 by accessing the generated URL.
  • the request accepting unit 611 of the server 600 accepts a request to provide the update list 606 from the first requesting unit 122.
  • the update information providing unit 612 transmits the update list 606 to the GW 100 in response to the request accepted by the request accepting unit 611 .
  • the first receiving unit 123 receives the update list 606 transmitted from the server 600 .
  • FIG. 7 is a diagram showing an example of an update list.
  • the update list 606 is information specifying Visited PLMN (operator identification information), SST (slice information), FW name, and version information for each FW that can be provided to GW 100 .
  • Each update list 606 corresponds to a combination of model information and Home PLMN, and in each update list 606, Visit PLMN, SST, FW name, and version information corresponding to FW that can be provided are specified. Therefore, by using the update list 606, it is possible to identify the FW corresponding to the combination of model information, Home PLMN, Visit PLMN, SST, FW name, and version information.
  • the update list 606 shown in FIG. 7 corresponds to a combination of type information "TYPE01” and Home PLMN "PLMN0".
  • each row is FW information corresponding to FW that can be provided to the GW100.
  • the FW information 606a on the first line includes Visited PLMN "PLMN0”, FW name "FW01”, and version information "1.2".
  • the FW information 606a is for the GW 100 of type "TYPE01" that connects to the cellular network of the telecommunications carrier identified by PLMN0, has been confirmed by the telecommunications carrier identified by Visited PLMN "PLMN0", and is the FW A FW whose name is “FW01” and whose version is "1.2" is shown.
  • the FW information 606b on the second line includes Visited PLMN "PLMN0", slice information "SST1", FW name "FW02", and version information "2.0".
  • the FW information 606b is for the GW 100 of type "TYPE01" that connects to the cellular network of the telecommunications carrier identified by PLMN0, and has been checked for operation by the telecommunications carrier identified by Visited PLMN "PLMN0", and sliced "SST1 , which has a FW name of 'FW02' and a version of '2.0'.
  • the FW information 606c on the third line includes Visited PLMN "PLMN0", slice information "SST2", FW name "FW03", and version information "1.1.2".
  • the FW information 606c is for the GW 100 of type "TYPE01" that connects to the cellular network of the telecommunications carrier identified by PLMN0, has been checked by the telecommunications carrier identified by Visited PLMN "PLMN0”, and is sliced "SST2 , which has a FW name of "FW03” and a version of "1.1.2".
  • the FW information 606d on the fourth line includes Visited PLMN "PLMN0", slice information "SST3", FW name "FW04", and version information "3.4".
  • the FW information 606d is for the GW 100 of type "TYPE01" that connects to the cellular network of the telecommunications carrier identified by PLMN0, has been checked by the telecommunications carrier identified by Visited PLMN "PLMN0”, and is sliced "SST3 , which has a FW name of "FW04" and a version of "3.4".
  • FW information 606e on the fifth line includes Visited PLMN "PLMN1", FW name “FW11”, and version information "2.4".
  • the FW information 606e is for the GW 100 of type "TYPE01" that connects to the cellular network of the telecommunications carrier identified by PLMN0, has been confirmed by the telecommunications carrier identified by Visited PLMN "PLMN1”, and is the FW A FW whose name is "FW11” and whose version is "2.4" is shown.
  • FW information 606f on the sixth line includes Visited PLMN "PLMN2", slice information "SST1", FW name "FW21”, and version information "5.1.1".
  • the FW information 606f is for the GW 100 of type "TYPE01" that connects to the cellular network of the telecommunications carrier identified by PLMN0, has been confirmed by the telecommunications carrier identified by Visited PLMN "PLMN2", and is sliced "SST1 , which has a FW name of 'FW21' and a version of '5.1.1'.
  • the FW information 606g on the seventh line includes Visited PLMN "PLMN3", slice information "SST1", FW name "FW31”, and version information "3.0.2".
  • the FW information 606g is for the GW 100 of type "TYPE01" that connects to the cellular network of the telecommunications carrier identified by PLMN0, and has been checked for operation by the telecommunications carrier identified by Visited PLMN "PLMN3", and sliced "SST1 , which has a FW name of "FW31” and a version of "3.0.2".
  • update data 710 for updating to FW corresponding to FW information 606 a to 606 g included in update list 606 is stored in database 700 .
  • the notification unit 124 compares the Visited PLMN identified in the update list 606 received from the server 600 with the Home PLMN or Visited PLMN acquired by the acquisition unit 121 .
  • the notification unit 124 can update to the FW corresponding to the PLMN.
  • a user for example, a facility worker
  • notification section 124 compares the SST identified in update list 606 with the SST acquired by acquisition section 121 .
  • the notification unit 124 compares the FW name specified in the update list 606 and the FW name acquired by the acquisition unit 121 .
  • the notification unit 124 compares the version information specified in the update list 606 and the version information acquired by the acquisition unit 121 .
  • the notification unit 124 contains the visited PLMN, SST, and FW names that match the PLMN, SST, and FW names acquired by the acquisition unit 121, and is a newer version than the version information (current version) acquired by the acquisition unit 121.
  • FW information including information (updated version) is included in the update list 606, the user is notified that the FW can be updated.
  • the GW 100 can be set to either the first mode or the second mode of operation.
  • the operation mode is set using the optimization flag 111 stored in the nonvolatile memory 102 (see FIG. 4). If the optimization flag 111 is valid, the first mode is set. If the optimization flag 111 is invalid, the second mode is set.
  • the notification unit 124 compares the Visited PLMN acquired by the acquisition unit 121 with the Visited PLMN identified in the update list 606 .
  • the notification unit 124 includes Visited PLMN, SST, and FW names that match the Visited PLMN, SST, and FW names acquired by the acquisition unit 121, and includes version information that is newer than the version information acquired by the acquisition unit 121. If the FW information is included in the update list 606, notify the user that the FW can be updated.
  • FW information including Visited PLMN, SST, and FW names that match the Visited PLMN, SST, and FW names acquired by the acquisition unit 121 exists in the update list 606, the FW corresponding to this FW information is connected to the GW 100.
  • it is FW optimized for SST set in GW100. Therefore, if the updated FW version is newer than the current version, the FW can be updated to a FW suitable for the communication environment in the cellular network 400 of the GW 100 .
  • this FW information is the FW optimized for the visited PLMN cellular network 400 to which the GW 100 connects.
  • the FW information including the Visited PLMN (same PLMN as the Home PLMN), SST, and FW names that match the Visited PLMN, SST, and FW names acquired by the acquisition unit 121 is included in the updated list. 606, the FW corresponding to this FW information is the FW optimized for the Home PLMN cellular network 400 to which the GW 100 connects.
  • the notification unit 124 compares the Home PLMN acquired by the acquisition unit 121 with the Visited PLMN identified in the update list 606 .
  • the notification unit 124 includes Visited PLMN, SST, and FW names that match the Home PLMN, SST, and FW names acquired by the acquisition unit 121, and includes version information that is newer than the version information acquired by the acquisition unit 121. If the FW information is included in the update list 606, notify the user that the FW can be updated.
  • FW information including the Visited PLMN, SST, and FW names that match the Home PLMN, SST, and FW names acquired by the acquisition unit 121 exists in the update list 606
  • this FW information cannot be said to be a FW optimized for the visited PLMN cellular network 400 to which the GW 100 connects.
  • the FW provided by carrier A can receive the service provided by carrier A, but the FW provided by carriers B and C cannot receive the service.
  • GW 100A Home PLMN and Visited PLMN correspond to carrier A, and FW provided by carrier A is used. Therefore, the GW 100A can use the services provided by the telecommunications carrier A.
  • the GWs 100B and 100C have a Home PLMN corresponding to the telecommunications carrier A and a Visited PLMN corresponding to the telecommunications carriers B and C. If the GWs 100B and 100C are set to the second mode, the GWs 100B and 100C use the FW provided by the carrier A. Therefore, the GWs 100B and 100C can also use the services provided by the carrier A.
  • the optimization flag 111 can be rewritten by the user.
  • the user can remotely operate the GW 100 using an external device such as the terminal 800 to rewrite the optimization flag 111 .
  • the user sets the optimization flag 111 to "valid”.
  • the user sets the GW 100 to the second mode, the user sets the optimization flag 111 to "invalid”.
  • the GW 100 can be connected to the terminal 800 used by the user through the second communication I/F 106, for example.
  • the notification unit 124 transmits to the terminal 800 information for notifying the user that the FW 107 can be updated.
  • the terminal 800 displays, for example, a screen for notifying that the FW 107 can be updated.
  • the user can input an update instruction for the FW 107 to the terminal 800.
  • the terminal 800 transmits an instruction to update the FW 107 from the user to the GW 100 .
  • the instruction receiving unit 125 receives the update instruction transmitted from the terminal 800.
  • the instruction receiving unit 125 receives an instruction to update the FW 107
  • the GW 100 updates the FW 107 .
  • the notification function of the notification unit 124 is not limited to the above.
  • the GW 100 has a web server function, and the notification unit 124 may generate a web page for notifying that the FW 107 can be updated.
  • the notification unit 124 may generate a web page for notifying that the FW 107 can be updated.
  • the user By accessing the web page of the GW 100 from an external information terminal such as the terminal 800, the user can be notified that the FW 107 can be updated.
  • GW 100 may send information to notify that FW 107 can be updated using auto-management protocol.
  • the GW 100 can switch between enabling and disabling the automatic update of the FW 107.
  • the GW 100 updates the FW 107 upon receiving an update instruction from the user as described above.
  • the GW 100 includes the Visited PLMN, SST, and FW names that match the PLMN, SST, and FW names acquired by the acquisition unit 121 if the FW 107 can be updated, and If the update list 606 includes FW information including version information newer than the version information acquired by the acquisition unit 121, the FW 107 is updated.
  • the second request unit 126 When the GW 100 updates the FW 107, the second request unit 126 includes the visited PLMN, SST, and FW names that match the PLMN, SST, and FW names acquired by the acquisition unit 121, and acquires by the acquisition unit 121 A request is made to the database 700 to provide update data 710 corresponding to FW information including version information newer than the received version information (hereinafter referred to as "compatible FW information"). Specifically, second request unit 126 generates a URL for downloading update data 710 corresponding to the compatible FW information. In this embodiment, the second request unit 126 generates a URL from the Visited PLMN, SST, FW name, and version information included in the compatible FW information.
  • update list 606 may include a URL associated with each piece of FW information 606a-606g.
  • the second request unit 126 can acquire the URL corresponding to the compatible FW information from the update list 606.
  • the second request unit 126 requests the database 700 to provide the update data 710 by accessing the generated URL.
  • the database 700 accepts a request to provide the update data 710 from the second request section 126.
  • Database 700 transmits update data 710 to GW 100 in response to the received request.
  • the second receiving unit 127 receives the update data 710 transmitted from the database 700.
  • the updating unit 128 updates the FW 107 of the GW 100 with the received update data 710.
  • FIG. 8A and 8B are flowcharts showing an example of FW update determination processing by the GW according to the embodiment.
  • the processor 101 of the GW 100 acquires model information, Home PLMN, Visited PLMN, SST, FW name, and version information (step S101). As described above, the processor 101 can obtain the Home PLMN from the SIM card. The processor 101 can acquire the Visited PLMN and SST when establishing a communication connection session with the cellular network 400 . Processor 101 can obtain FW name and version information from FW 107 .
  • the processor 101 generates a download URL for the update list 606 from the acquired model information and Home PLMN (step S102).
  • Processor 101 accesses the URL and requests server 600 to provide update list 606 .
  • Server 600 transmits update list 606 to GW 100 upon request.
  • Processor 101 downloads update list 606 from server 600 (step S103).
  • the processor 101 determines whether the optimization flag 111 is valid (step S104). If optimization flag 111 is valid (YES in step S104), GW 100 is set to the first mode. In this case, the processor 101 checks whether or not the acquired Visited PLMN, SST, and FW names and the Visited PLMN, SST, and FW names match FW information (that is, matching FW information) in the update list 606. Determine (step S105). If compatible FW information does not exist in update list 606 (NO in step S105), processor 101 ends the FW update determination process. If compatible FW information exists in update list 606 (YES in step S105), processor 101 moves to step S107.
  • the GW 100 is set to the second mode.
  • the processor 101 checks whether or not the updated list 606 contains FW information (that is, compatible FW information) that matches the acquired Home PLMN, SST, and FW names with the Visited PLMN, SST, and FW names. Determine (step S106). If compatible FW information does not exist in update list 606 (NO in step S106), processor 101 ends the FW update determination process. If compatible FW information exists in update list 606 (YES in step S106), processor 101 moves to step S107.
  • FW information that is, compatible FW information
  • the processor 101 determines whether the version information (updated version) included in the compatible FW information is newer than the acquired version information (current version) (step S107). If the updated version is the same as or older than the current version (NO in step S107), processor 101 ends the FW update determination process.
  • processor 101 determines whether automatic update is valid (step S108). If automatic update is valid (YES in step S108), processor 101 executes FW update processing (step S111).
  • processor 101 notifies the user that FW update is possible (step S109). For example, as described above, the terminal 800 notifies that the FW update is possible.
  • a user can give a FW update instruction to the GW 100 via the terminal 800, for example.
  • the processor 101 determines whether or not a FW update instruction has been received from the user (step S110). If the FW update instruction is not accepted (NO in step S110), processor 101 ends the FW update determination process. If the FW update instruction is received (YES in step S110), processor 101 executes FW update processing (step S111).
  • FIG. 9 is a flowchart showing an example of FW update processing by the GW according to the embodiment.
  • the processor 101 generates a download URL for the update data 710 from the visited PLMN, SST, FW name, and version information included in the compatible FW information (step S201).
  • the processor 101 accesses the URL and requests the database 700 to provide update data 710 .
  • Database 700 transmits update data 710 to GW 100 upon request.
  • Processor 101 downloads update data 710 from database 700 (step S202).
  • the processor 101 installs a new FW using the update data 710 (step S203).
  • the FW 107 of the nonvolatile memory 102 is rewritten with a new FW.
  • the processor 101 reboots the GW 100 (step S204). This terminates the old FW 107 and activates the new FW. This completes the FW update.
  • step S111 when the FW update process (step S111) ends, the FW update determination process ends.
  • the update list 606 is requested from the GW 100 to the server 600, the update list 606 is downloaded from the server 600 to the GW 100, and the update data 710 is requested from the GW 100 to the database 700.
  • the update data 710 is downloaded from the GW 100 through the first communication paths 510A, 510B, 510C.
  • the communication between GW 100 and server 600 and the communication between GW 100 and database 700 can be performed through second communication paths 520A, 520B and 520C.
  • the first request unit 122 requests the server 600 to provide the update list 606 corresponding to the combination of the model information of the GW 100 and the Home PLMN, but the present invention is not limited to this.
  • the first request unit 122 requests the server 600 to provide an update list corresponding to the Home PLMN.
  • the non-volatile memory 602 of the server 600 stores an update list corresponding to the Home PLMN.
  • an update list corresponding to carrier A, an update list corresponding to carrier C, and an update list corresponding to carrier D are stored in the non-volatile memory 602 .
  • the acquiring unit 121 acquires “PLMN0” which is the PLMN indicating the communication carrier A
  • the first requesting unit 122 generates a URL from “PLMN0”. This URL is information for downloading the update list corresponding to carrier A from server 600 .
  • FIG. 10 is a diagram showing a first modification of the update list.
  • the update list 606A according to the first modification is information specifying the model information, Visited PLMN (operator identification information), SST (slice information), FW name, and version information for each FW that can be provided to the GW 100. be.
  • Each update list 606A corresponds to Home PLMN, and in each update list 606A, model information, Visit PLMN, SST, FW name, and version information corresponding to FW that can be provided are specified. Therefore, by using the update list 606A, it is possible to identify the FW corresponding to the combination of model information, Home PLMN, Visit PLMN, SST, FW name, and version information.
  • each row is FW information corresponding to FW that can be provided to GW 100 . More specifically, the FW information 606Aa on the first line includes type information "TYPE01”, Visited PLMN "PLMN0”, FW name "FW01", and version information "1.2".
  • the FW information 606Aa is for the GW 100 of type "TYPE01" that connects to the cellular network of the telecommunications carrier identified by PLMN0, has been checked by the telecommunications carrier identified by Visited PLMN "PLMN0", and is the FW A FW whose name is “FW01” and whose version is "1.2" is shown.
  • the FW information 606Ab on the second line includes type information "TYPE01”, Visited PLMN "PLMN0", slice information "SST1", FW name "FW02", and version information "2.0".
  • the FW information 606Ab is for the GW 100 of type "TYPE01” that connects to the cellular network of the telecommunications carrier identified by PLMN0, and has been checked for operation by the telecommunications carrier identified by Visited PLMN "PLMN0", and sliced "SST1 , which has a FW name of 'FW02' and a version of '2.0'.
  • the FW information 606Ac on the third line includes type information "TYPE01”, Visited PLMN "PLMN0", slice information "SST2", FW name "FW03", and version information "1.1.2".
  • the FW information 606Ac is for the GW 100 of type "TYPE01” that connects to the cellular network of the telecommunications carrier identified by PLMN0, has been checked for operation by the telecommunications carrier identified by Visited PLMN "PLMN0”, and is sliced "SST2 , which has a FW name of "FW03” and a version of "1.1.2".
  • the FW information 606Ad on the fourth line includes type information "TYPE01”, Visited PLMN "PLMN0", slice information "SST3", FW name "FW04", and version information "3.4".
  • the FW information 606Ad is for the GW 100 of model "TYPE01” that connects to the cellular network of the telecommunications carrier identified by PLMN0, and has been checked by the telecommunications carrier identified by Visited PLMN "PLMN0", and sliced “SST3 , which has a FW name of "FW04" and a version of "3.4".
  • the FW information 606Ae on the fifth line includes type information "TYPE01”, Visited PLMN "PLMN1", FW name "FW11”, and version information "2.4".
  • the FW information 606Ae is for the GW 100 of type "TYPE01” that connects to the cellular network of the telecommunications carrier identified by PLMN0, has been confirmed by the telecommunications carrier identified by Visited PLMN "PLMN1”, and is the FW A FW whose name is "FW11” and whose version is "2.4" is shown.
  • the FW information 606Af on the sixth line includes type information "TYPE02", Visited PLMN "PLMN0", slice information "SST2", FW name "FW41”, and version information "10.2".
  • the FW information 606Af is for the GW 100 of type "TYPE02" that connects to the cellular network of the telecommunications carrier identified by PLMN0, and has been checked by the telecommunications carrier identified by Visited PLMN "PLMN0", and sliced “SST2 , which has a FW name of "FW41” and a version of "10.2".
  • the FW information 606Ag on the seventh line includes type information "TYPE02”, Visited PLMN "PLMN0", slice information "SST1", FW name "FW42”, and version information "5.6.1”.
  • the FW information 606Ag is for the GW 100 of type "TYPE02" that connects to the cellular network of the telecommunications carrier identified by PLMN0, has been checked by the telecommunications carrier identified by Visited PLMN "PLMN0”, and is sliced "SST1 , which has a FW name of "FW42” and a version of "5.6.1".
  • the FW information 606Ah on the eighth line includes type information "TYPE02”, Visited PLMN “PLMN1”, slice information "SST1", FW name "FW51”, and version information "3.4.2".
  • the FW information 606Ah is for the GW 100 of type "TYPE02" that connects to the cellular network of the telecommunications carrier identified by PLMN0, has been checked by the telecommunications carrier identified by Visited PLMN "PLMN1”, and is sliced "SST1 , which has a FW name of "FW51” and a version of "3.4.2".
  • the FW information 606Ai on the 9th line includes type information "TYPE02”, Visited PLMN "PLMN2", slice information "SST3", FW name "FW61”, and version information "5.5.2".
  • the FW information 606Ai is for the GW 100 of type "TYPE02" that connects to the cellular network of the telecommunications carrier identified by PLMN0, and has been confirmed by the telecommunications carrier identified by Visited PLMN "PLMN2", and sliced “SST3 , which has a FW name of "FW61” and a version of "5.5.2".
  • the first request unit 122 requests the server 600 to provide an update list corresponding to the model information.
  • the non-volatile memory 602 of the server 600 stores an update list corresponding to model information.
  • an update list corresponding to TYPE01 and an update list corresponding to TYPE02 are stored in the nonvolatile memory 602 .
  • the acquiring unit 121 acquires the type information “TYPE01”
  • the first requesting unit 122 generates a URL from “TYPE01”. This URL is information for downloading the update list corresponding to TYPE01 from the server 600 .
  • FIG. 11 is a diagram showing a second modification of the update list.
  • the update list 606B according to the second modification is information specifying the Home PLMN, Visited PLMN, SST, FW name, and version information for each FW that can be provided to the GW 100 .
  • Each update list 606B corresponds to model information, and in each update list 606B, Home PLMN, Visit PLMN, SST, FW name, and version information corresponding to FW that can be provided are specified. Therefore, by using the update list 606B, it is possible to identify the FW corresponding to the combination of model information, Home PLMN, Visit PLMN, SST, FW name, and version information.
  • each row is FW information corresponding to FW that can be provided to GW 100 .
  • the FW information 606Ba on the first line includes Home PLMN "PLMN0”, Visited PLMN “PLMN0”, FW name "FW01”, and version information "1.2".
  • the FW information 606Ba is for the GW 100 of type "TYPE01" that connects to the cellular network of the telecommunications carrier identified by PLMN0, has been checked by the telecommunications carrier identified by Visited PLMN "PLMN0", and is the FW A FW whose name is “FW01” and whose version is "1.2" is shown.
  • the FW information 606Bb on the second line includes Home PLMN "PLMN0", Visited PLMN “PLMN0”, slice information "SST1", FW name "FW02", and version information "2.0".
  • the FW information 606Bb is for the GW 100 of type "TYPE01" that connects to the cellular network of the telecommunications carrier identified by PLMN0, and has been checked for operation by the telecommunications carrier identified by Visited PLMN "PLMN0", and sliced "SST1 , which has a FW name of 'FW02' and a version of '2.0'.
  • the FW information 606Bc on the third line includes Home PLMN "PLMN0", Visited PLMN “PLMN0”, slice information "SST2", FW name "FW03", and version information "1.1.2".
  • the FW information 606Bc is for the GW 100 of type "TYPE01" that connects to the cellular network of the telecommunications carrier identified by PLMN0, has been checked by the telecommunications carrier identified by Visited PLMN "PLMN0”, and is sliced “SST2 , which has a FW name of "FW03” and a version of "1.1.2".
  • the FW information 606Bd on the fourth line includes Home PLMN "PLMN0", Visited PLMN “PLMN0”, slice information "SST3", FW name "FW04", and version information "3.4".
  • the FW information 606Bd is for the GW 100 of model "TYPE01" that connects to the cellular network of the telecommunications carrier identified by PLMN0, and has been checked for operation by the telecommunications carrier identified by Visited PLMN "PLMN0", and sliced “SST3 , which has a FW name of "FW04" and a version of "3.4".
  • the FW information 606Be on the fifth line includes Home PLMN "PLMN0", Visited PLMN “PLMN1”, FW name "FW11”, and version information "2.4".
  • the FW information 606Be is for the GW 100 of type "TYPE01" that connects to the cellular network of the telecommunications carrier identified by PLMN0, and has been confirmed by the telecommunications carrier identified by the Visited PLMN "PLMN1".
  • a FW whose name is "FW11” and whose version is "2.4” is shown.
  • the FW information 606Bf on the sixth line includes Home PLMN "PLMN2", Visited PLMN “PLMN2", slice information "SST1", FW name "FW71”, and version information "8.3.1”.
  • the FW information 606Bf is for the GW 100 of model "TYPE01" that connects to the cellular network of the telecommunications carrier identified by PLMN2, and has been checked by the telecommunications carrier identified by Visited PLMN "PLMN2", and sliced "SST1 , which has a FW name of 'FW71' and a version of '8.3.1'.
  • the FW information 606Bg on the seventh line includes Home PLMN "PLMN2", Visited PLMN “PLMN2”, slice information "SST2", FW name "FW72", and version information "6.7.3".
  • the FW information 606Bg is for the GW 100 of type "TYPE01" that connects to the cellular network of the telecommunications carrier identified by PLMN2, and has been checked for operation by the telecommunications carrier identified by Visited PLMN "PLMN2", and sliced “SST2 , which has a FW name of "FW72” and a version of "6.7.3".
  • the FW information 606Bh on the eighth line includes Home PLMN "PLMN2", Visited PLMN “PLMN1”, slice information "SST1", FW name "FW81”, and version information "10.3.1”.
  • the FW information 606Bh is for the GW 100 of type "TYPE01" that connects to the cellular network of the telecommunications carrier identified by PLMN2, and has been checked for operation by the telecommunications carrier identified by Visited PLMN "PLMN1", and sliced “SST1 , which has a FW name of "FW81” and a version of "10.3.1".
  • the FW information 606Bi on the ninth line includes Home PLMN "PLMN2", Visited PLMN “PLMN1”, slice information "SST2", FW name "FW82”, and version information "10.2.8".
  • the FW information 606Bi is for the GW 100 of model "TYPE01" that connects to the cellular network of the telecommunications carrier identified by PLMN2, and has been checked by the telecommunications carrier identified by Visited PLMN "PLMN1", and sliced “SST2 , which has a FW name of "FW82” and a version of "10.2.8".
  • server 600 provided the update list 606 to the GW 100 and the database 700 provided the update data 710 to the GW 100, but the present invention is not limited to this.
  • server 600 may provide update list 606 and update data 710 to GW 100 .
  • a software update system 10 includes a GW 100 (communication device) and a server 600 .
  • GW 100 is connectable to cellular network 400 .
  • the server 600 provides the GW 100 with an update list 606 (update information) used for updating the FW 107 (control software) for the GW 100 .
  • GW 100 includes an acquisition unit 121 , a first request unit 122 , a second request unit 126 and an update unit 128 .
  • Acquisition unit 121 acquires first carrier identification information for identifying a communication carrier that provides cellular network 400 to which GW 100 connects.
  • the first request unit 122 requests the server 600 to provide an update list 606 specifying the second operator identification information corresponding to each FW that can be provided to the GW 100 .
  • the second request unit 126 provides update data for updating to the FW corresponding to the second business journal identification information when the first business identification information and the second business identification information match. 710 is requested.
  • the updating unit 128 updates the FW 107 for the GW 100 with the received update data 710 .
  • the GW 100 can identify the FW provided by the carrier of the cellular network 400 to which the GW 100 connects, and update to the identified FW. Therefore, updating of the FW of the GW 100 becomes efficient.
  • the communication device 100 performs processing necessary for selecting appropriate update data 710, but the present invention is not limited to this.
  • the server 600 may perform the processing.
  • the communication device 100 transmits part or all of the operator identification information, Home PLMN, Visited PLMN, model information of the communication device 100, slice information and other information to the server 600, and the server 600 transmits the operator identification information It determines whether or not there is update data for the control software corresponding to the control software and whether or not the update is possible.
  • Server 600 then transmits the determination result (appropriate update data 710 ) to communication device 100 . In this way, selection and judgment processing can also be performed by a device other than the communication device 100 .
  • Each process (each function) of the above-described embodiment is realized by a processing circuit (circuitry) including one or more processors.
  • the processing circuit may be configured by an integrated circuit in which, for example, one or more memories, various analog circuits, and various digital circuits are combined.
  • the one or more memories store programs (instructions) that cause the one or more processors to execute the processes.
  • the one or more processors may execute the above processes according to the program read from the one or more memories, or execute the above processes according to a logic circuit designed in advance to execute the above processes. may be executed.
  • the above processors are CPU (Central Processing Unit), GPU (Graphics Processing Unit), DSP (Digital Signal Processor), FPGA (Field Programmable Gate Array), and ASIC (Application Specific Integrate d Circuit), etc., which are suitable for computer control processor.
  • the plurality of physically separated processors may cooperate with each other to execute the above processes.
  • the processors installed in each of a plurality of physically separated computers cooperate with each other via networks such as LAN (Local Area Network), WAN (Wide Area Network), and the Internet to perform each of the above processes. may be executed.
  • the program may be installed in the memory via the network from an external server device, for example, CD-ROM (Compact Disc Read Only Memory), DVD-ROM (Digital Versatile Disk Read Only Memory), and It may be distributed in a state stored in a recording medium such as a semiconductor memory and installed in the memory from the recording medium.
  • CD-ROM Compact Disc Read Only Memory
  • DVD-ROM Digital Versatile Disk Read Only Memory

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/JP2022/041498 2022-01-31 2022-11-08 ソフトウェア更新システム、通信装置、及び更新情報のデータ構造、ソフトウェア更新方法 WO2023145187A1 (ja)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2023576630A JPWO2023145187A1 (enrdf_load_stackoverflow) 2022-01-31 2022-11-08

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2022012590 2022-01-31
JP2022-012590 2022-01-31

Publications (1)

Publication Number Publication Date
WO2023145187A1 true WO2023145187A1 (ja) 2023-08-03

Family

ID=87471373

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/041498 WO2023145187A1 (ja) 2022-01-31 2022-11-08 ソフトウェア更新システム、通信装置、及び更新情報のデータ構造、ソフトウェア更新方法

Country Status (2)

Country Link
JP (1) JPWO2023145187A1 (enrdf_load_stackoverflow)
WO (1) WO2023145187A1 (enrdf_load_stackoverflow)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104601798A (zh) * 2014-12-02 2015-05-06 惠州Tcl移动通信有限公司 一种定制应用程序启动控制方法及装置
JP2015524966A (ja) * 2012-07-02 2015-08-27 アマゾン テクノロジーズ インク アプリケーション互換性の評価
JP2018180767A (ja) * 2017-04-07 2018-11-15 富士通株式会社 情報処理装置、情報処理方法、及び、情報処理プログラム

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015524966A (ja) * 2012-07-02 2015-08-27 アマゾン テクノロジーズ インク アプリケーション互換性の評価
CN104601798A (zh) * 2014-12-02 2015-05-06 惠州Tcl移动通信有限公司 一种定制应用程序启动控制方法及装置
JP2018180767A (ja) * 2017-04-07 2018-11-15 富士通株式会社 情報処理装置、情報処理方法、及び、情報処理プログラム

Also Published As

Publication number Publication date
JPWO2023145187A1 (enrdf_load_stackoverflow) 2023-08-03

Similar Documents

Publication Publication Date Title
EP3968702B1 (en) Determining a network function to perform service communication with another network function
CN111201765B (zh) 通信网络中的服务注册和发现
CN104838618B (zh) 在无线通信系统中验证访问授权的方法和设备
CN102668642B (zh) 网络选择机制
CN104539686B (zh) 免流量下载应用的方法、终端和服务端
WO2016173348A1 (zh) 一种网络接入方法及移动通信终端
KR101264819B1 (ko) 표적 동작 객체를 찾아내기 위한 장치 관리 서버, 클라이언트 및 방법
CN102355500B (zh) 业务推送方法和装置
CN112740642B (zh) 通信方法及多接入边缘计算服务器
JP6067853B2 (ja) 制御装置、制御方法、通信システムおよびプログラム
JP2016535895A (ja) ソフトウェア更新方法、システム及びデバイス
US20090138444A1 (en) Method of searching metadata servers
US10932171B2 (en) Access point switching method and apparatus
WO2009109980A2 (en) Method and system for transfer of application between devices
WO2016173349A1 (zh) 一种网络接入方法及移动通信终端
EP4091349A1 (en) Establishing and maintaining cellular data communication using remote subscriber identification module profile
WO2013167207A1 (en) Object version management
CN109196892B (zh) 订户实体的远程提供方法
KR101042526B1 (ko) 단말에 선호 사업자망의 변경을 자동 업데이트하는 방법 및장치
WO2023145187A1 (ja) ソフトウェア更新システム、通信装置、及び更新情報のデータ構造、ソフトウェア更新方法
CN111770487B (zh) 一种接入点名称apn信息配置方法、设备及介质
CN105282728A (zh) 一种删除通告资源的方法和公共业务实体
CN110830540A (zh) 智能电视接入云服务器的方法、存储介质及应用服务器
CN110719574B (zh) 一种网点访问方法及相关设备
WO2021115464A1 (zh) 一种网络切片选择方法及相关装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22924041

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2023576630

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22924041

Country of ref document: EP

Kind code of ref document: A1