A method, device and system for obtaining manufacturer's user manual MUD file
By implementing the method of obtaining MUD files from multiple MUD file servers on the MUD control management device and processing it, the problem that MUD files cannot be obtained from multiple servers in the prior art is solved, and the accurate constraints on the network behavior of the terminal device are realized and manage.
Patent Information
- Application Number
- CN202010340085.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-04-26
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2040-04-26
AI Technical Summary
In the prior art, the MUD control management device can only obtain MUD files from a single MUD file server corresponding to the manufacturer of the terminal device, and cannot support obtaining MUD files from multiple MUD file servers, resulting in the distribution of multiple MUD files on multiple servers. In the case of this, the accurate constraints on the network behavior of the terminal device cannot be achieved.
By implementing the target acquisition strategy corresponding to the terminal device on the MUD control management device, MUD files can be obtained from multiple MUD file servers, and the acquired MUD files can be processed to determine the target MUD files, ensuring accurate constraints on network behavior.
The accurate constraints on the network behavior of terminal devices in multiple MUD file server scenarios are realized, constraint conflicts caused by different MUD information of the same device description item are avoided, and the management flexibility and accuracy of network behavior are improved.
Smart Images

Figure CN113556374B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a method, device and system for obtaining a manufacturer usage description (English: Manufacturer Usage Description, abbreviated as: MUD) file. Background Art
[0002] With the continuous improvement of digitalization and intelligence, more and more terminal devices have appeared in network scenarios, such as printers, cameras, smart LED lights, conference room projection devices and other terminal devices in the Internet of Things (IoT) scenario. In order to constrain various terminal devices, the manufacturer of the terminal device will generate a MUD file that includes information such as the device type and network access rights of the terminal device, and the network device to which the terminal device is connected when it accesses the network can apply the MUD file to constrain the terminal device accordingly.
[0003] Based on the Internet Engineering Task Force (IETF) Request For Comments (RFC) 8520: "Manufacturer Usage Description Specification", the manufacturer of the terminal device saves the generated MUD file on the manufacturer's MUD file server, and only saves the Uniform Resource Locator (URL) (hereinafter referred to as MUD URL) corresponding to the MUD file on the terminal device. When the terminal device needs to access the network, the terminal device sends the MUD URL to the network device to which it is connected. The terminal device sends the MUD URL to the MUD control and management device through the network device. The MUD control and management device obtains the corresponding MUD file from the MUD file server based on the MUD URL, and maps the content of the MUD file into a network policy for constraining the network behavior of the terminal device.
[0004] It can be seen that according to the current RFC 8520 protocol, the MUD control management device can only obtain a MUD file from the MUD file server corresponding to the manufacturer of the terminal device through the MUD URL on the terminal device, and does not support obtaining MUD files from multiple MUD file servers. Based on this, it is urgent to provide a mechanism for obtaining MUD files so that the MUD control management device can obtain MUD files from multiple MUD file servers. Summary of the invention
[0005] Based on this, the embodiments of the present application provide a method, device and system for obtaining the manufacturer's instruction MUD file, so as to obtain the MUD file from the multiple MUD file servers, thereby accurately constraining the terminal device based on the obtained MUD file.
[0006] In the first aspect, the embodiment of the present application provides a method for obtaining MUD files, which is implemented by a MUD control management device. The method may include, for example: receiving a MUD URL request message sent by a terminal device; and obtaining at least one MUD file from multiple MUD file servers according to a target acquisition strategy corresponding to the terminal device. It can be seen that the MUD control management device of the embodiment of the present application has a target acquisition strategy corresponding to each terminal device, and can obtain MUD files from multiple MUD file servers based on the target acquisition strategy corresponding to the terminal device, so that in a scenario where multiple MUD files are distributed on multiple MUD file servers, the MUD files of the terminal device can be obtained from the multiple MUD file servers, thereby achieving more accurate constraints on the network behavior of the terminal device.
[0007] As an example, the MUD control management device may store a first mapping relationship between the MUD URL provided to the terminal device by the manufacturer of the terminal device and the target acquisition strategy. Then, an embodiment of the present application may also include: the MUD control management device obtains the MUD URL provided to the terminal device by the manufacturer of the terminal device from the MUD URL request message, determines that the MUD URL matches the first mapping relationship, and thereby obtains the target acquisition strategy according to the first mapping relationship.
[0008] As another example, the MUD control management device may also save the second mapping relationship between the device information of the terminal device and the target acquisition strategy. Then, the embodiment of the present application may also include: the MUD control management device obtains the device information of the terminal device from the MUD URL request message, determines that the device information matches the second mapping relationship, and thereby obtains the target acquisition strategy according to the second mapping relationship. Among them, the device information of the terminal device may include, for example, one or more of the following: the device identification of the terminal device, the device type of the terminal device, the network segment to which the terminal device belongs, the Internet Protocol (English: Internet Protocol, abbreviated: IP) address of the terminal device, the Media Access Control (English: Media Access Control, abbreviated: MAC) address of the terminal device, and the manufacturer information of the terminal device.
[0009] In some possible implementations, there is only one acquisition strategy on the MUD control management device. Then, when the MUD control management device receives a MUD URL request message sent by any terminal device, it uses the unique acquisition strategy as the target acquisition strategy and acquires at least one MUD file from multiple MUD file servers based on the target acquisition strategy.
[0010] In some other possible implementations, there are multiple acquisition strategies on the MUD control management device, then, the embodiment of the present application may also include: the MUD control management device determines the target acquisition strategy from multiple pre-configured acquisition strategies. The multiple acquisition strategies may be configured and saved locally on the MUD control management device, or may be acquired by the MUD control management device from other devices.
[0011] Wherein, the acquisition strategy (including the target acquisition strategy) is used to indicate the rules for obtaining MUD files from multiple MUD file servers. In one case, the target acquisition strategy may include, for example: according to the MUD URL provided to the terminal device by the manufacturer of the terminal device, redirecting the first MUD file server corresponding to the MUD URL to at least one target MUD file server, and obtaining the MUD files in the at least one target MUD file server, wherein the multiple MUD file servers include the first MUD file server, and the at least one target MUD file server includes the second MUD file server. Or, in another case, the target acquisition strategy may also include, for example: according to the principle of sequential reading, the MUD files that have been obtained are updated as a whole with the MUD files obtained from the most recently read MUD file server. Or, in another case, the target acquisition strategy may also include, for example: sequentially reading and saving multiple MUD files in multiple MUD file servers. Or, in another case, the target acquisition strategy may also include, for example: pre-specifying at least one target MUD file server from the multiple MUD file servers, and obtaining the MUD files in the at least one target MUD file server.
[0012] As an example, the MUD control management device obtains at least one MUD file from multiple MUD file servers according to the target acquisition strategy corresponding to the terminal device, which may specifically include: first determining at least one target MUD file server from the multiple MUD file servers according to the target acquisition strategy; and then obtaining the at least one MUD file from the at least one target MUD file server. It should be noted that the above-mentioned target MUD file server is one of the multiple MUD file servers. The above-mentioned at least one target MUD file server may be all the MUD file servers included in the multiple MUD file servers; or, the above-mentioned at least one target MUD file server may also be some of the MUD file servers among the multiple MUD file servers.
[0013] In addition, the target acquisition strategy may also include, for example: according to the MUD URL provided to the terminal device by the manufacturer of the terminal device, redirecting the first MUD file server corresponding to the MUD URL to at least one target MUD URL, and acquiring the at least one MUD file from multiple MUD file servers based on the at least one target MUD URL. Among them, the number of at least one target MUD URL is less than or equal to the number of all MUD file servers included in the multiple MUD file servers. Then, the MUD control management device acquires at least one MUD file from multiple MUD file servers according to the target acquisition strategy corresponding to the terminal device, which may specifically include: determining at least one target MUD URL from multiple MUD URLs corresponding to the multiple MUD file servers according to the target acquisition strategy; and acquiring the at least one MUD file from the at least one target MUD URL. It should be noted that the above-mentioned target MUD URL is one of the multiple MUD URLs corresponding to the multiple MUD files storing the terminal device in the multiple MUD file servers. The above-mentioned at least one target MUD URL may be all the MUD URLs included in the multiple MUD URLs; or, the above-mentioned at least one target MUD URL may also be a part of the MUD URLs in the multiple MUD URLs.
[0014] In some specific implementations, after the MUD control management device obtains at least one MUD file based on the method provided in the embodiment of the present application, the embodiment of the present application may also include: the MUD control management device processes the at least one MUD file to obtain a target MUD file, and the target MUD file is used to constrain the network behavior of the terminal device. In one case, when the at least one MUD file includes only one MUD file, the only obtained MUD file can be directly used as the target MUD file, and the network behavior of the terminal device is constrained by the target MUD file. In another case, if the at least one MUD file includes at least two MUD files, it is necessary to process the at least two MUD files to obtain the target MUD file, and the network behavior of the terminal device is constrained by the target MUD file.
[0015] As an example, the process of processing at least one MUD file to obtain a target MUD file may include, for example, a process of determining the device description items included in the target MUD file. In one case, all device description items included in the acquired MUD file may be used as device description items in the target MUD file. Assuming that at least one MUD file includes a first MUD file and a second MUD file, the first MUD file includes a first device description item of the terminal device, the second MUD file includes a second device description item of the terminal device, and the first device description item and the second device description item are different, then the target MUD file includes the first device description item and the second device description item. In another case, the device description items included in each MUD file in the acquired MUD file may also be used as device description items in the target MUD file. Assuming that at least one MUD file includes a first MUD file and a second MUD file, the first MUD file includes a first device description item and a second device description item of the terminal device, the second MUD file includes a second device description item of the terminal device, and the first device description item and the second device description item are different, then the target MUD file includes the second device description item.
[0016] In addition, when the same device description item is included in multiple MUD files of at least one MUD file obtained, but the MUD information of the same device description item is different, then the process of processing at least one MUD file to obtain the target MUD file may, for example, include a process of determining the MUD information of the device description item in the target MUD file. As an example, an embodiment of the present application may also include: based on the target MUD file processing strategy corresponding to the terminal device, obtaining the MUD information used to describe the first device description item in the target MUD file. The first device description item is the same device description item included in multiple MUD files of at least one MUD file obtained.
[0017] Wherein, the target MUD file processing strategy indicates the rule for processing the at least one obtained MUD file to obtain the target MUD file. In one case, the target MUD file processing strategy may include, for example: when the multiple MUD files are obtained in sequence, the MUD information used to describe the first device description item in the most recently obtained MUD file is used as the MUD information used to describe the first device description item in the target MUD file. Or, in another case, the target MUD file processing strategy may also include, for example: when the MUD information used to describe the first device description item exists in multiple MUD files, the MUD information used to describe the first device description item in a specified MUD file (for example: the MUD file provided by the manufacturer of the terminal device) is used as the MUD information used to describe the first device description item in the target MUD file. Or, in another case, the target MUD file processing strategy may also include, for example: when the MUD information used to describe the first device description item exists in multiple MUD files, the MUD information of the first device description item is processed using a specified operation, and the operation result is used as the MUD information of the first device description item in the target MUD file. Alternatively, in another case, the target MUD file processing strategy may also include, for example: when multiple MUD files respectively include a first MUD information and a second MUD information for describing the first device description item, obtaining the first MUD information and the second MUD information, and in the target MUD file, associating the first MUD information with a first service, and associating the second MUD information with a second service.
[0018] It can be seen that through the method provided by the embodiment of the present application, for the scenario where multiple MUD files are distributed on different MUD file servers, when the terminal device accesses the network, the MUD control management device can not only obtain at least one MUD file from multiple MUD file servers according to the target acquisition strategy corresponding to the terminal device, so as to support the acquisition of MUD files from multiple MUD file servers; but also, in order to more accurately constrain the terminal device based on the at least one MUD file obtained and avoid conflicts in the constraints on the network behavior of the terminal device caused by different MUD information of the same device description items in the multiple MUD files obtained, the MUD control management device can also process the at least one MUD file obtained and determine the target MUD file, so as to achieve accurate constraints on the network behavior of the terminal device based on the processed target MUD file.
[0019] In the second aspect, the embodiment of the present application also provides a MUD control and management device, which includes a transceiver unit and a processing unit. The transceiver unit is used to perform the transceiver operation in the method provided in the first aspect; the processing unit is used to perform other operations in the method provided in the first aspect except the transceiver operation. For example: when the MUD control and management device executes the method provided in the first aspect, the transceiver unit can be used to receive a MUD URL request message sent by a terminal device; the processing unit can be used to obtain at least one MUD file from multiple MUD file servers based on the target acquisition strategy corresponding to the terminal device.
[0020] In a third aspect, an embodiment of the present application further provides a MUD control management device, which includes a communication interface and a processor. The communication interface is used to perform the transceiver operation in the method provided in the first aspect; the processor is used to perform other operations in the method provided in the first aspect or any possible implementation of the first aspect except the transceiver operation.
[0021] In a fourth aspect, an embodiment of the present application further provides a MUD control management device, the MUD control management device comprising a memory and a processor. The memory comprises computer-readable instructions; the processor communicating with the memory is used to execute the computer-readable instructions, so that the MUD control management device is used to execute the method provided in the first aspect or any possible implementation of the first aspect.
[0022] In a fifth aspect, the present application also provides a communication system, which includes a MUD control management device, a terminal device, and multiple MUD file servers, wherein the MUD control management device may be the MUD control management device provided in the second, third, or fourth aspects above.
[0023] In a sixth aspect, an embodiment of the present application further provides a communication system. The communication system includes a MUD control management device, a terminal device, and a plurality of MUD file servers, wherein the plurality of MUD file servers include a first MUD file server, and the first MUD file server is used to store a first MUD file; the plurality of MUD file servers include a second MUD file server, and the second MUD file server is used to store a second MUD file. In addition, the plurality of MUD file servers may also include other MUD file servers, for example, the plurality of MUD file servers may also include a third MUD file server, and the third MUD file server is used to store a third MUD file.
[0024] In the communication system provided in the fifth aspect or the sixth aspect, the following related operations may also be performed:
[0025] The terminal device in the communication system is used to send a MUD uniform resource locator URL request message to the MUD control management device; the MUD control management device is used to obtain at least one MUD file from multiple MUD file servers according to a target acquisition strategy corresponding to the terminal device. For example, the at least one MUD file may include at least one of the following MUD files: a first MUD file, a second MUD file, and a third MUD file.
[0026] In some possible implementations, the MUD control management device stores a first mapping relationship between the MUD URL provided to the terminal device by the manufacturer of the terminal device and the target acquisition strategy. Then, the MUD control management device in the communication system is also used to obtain the target acquisition strategy according to the first mapping relationship.
[0027] In some other possible implementations, the MUD control and management device stores a second mapping relationship between the device information of the terminal device and the target acquisition strategy. Then, the MUD control and management device in the communication system is also used to obtain the target acquisition strategy according to the second mapping relationship. The device information of the terminal device includes one or more of the following: the device identification of the terminal device; the device type of the terminal device; the network segment to which the terminal device belongs; the Internet Protocol IP address of the terminal device; the Media Access Control MAC address of the terminal device; and the manufacturer information of the terminal device.
[0028] In some other possible implementations, the MUD control management device in the communication system is further used to determine the target acquisition strategy from a plurality of pre-configured acquisition strategies. The plurality of acquisition strategies may be locally configured and saved in the MUD control management device, or may be acquired and saved by the MUD control management device from other devices.
[0029] In some further possible implementations, the MUD control management device in the communication system is used to obtain at least one MUD file from multiple MUD file servers 1003 according to a target acquisition strategy corresponding to the terminal device, which may specifically include: determining at least one target MUD file server from the multiple MUD file servers according to the target acquisition strategy; and obtaining the at least one MUD file from the at least one target MUD file server.
[0030] Among them, the target acquisition strategy includes: according to the MUD URL provided to the terminal device by the manufacturer of the terminal device, redirecting the first MUD file server corresponding to the MUD URL to the at least one target MUD file server, and obtaining the MUD files in the at least one target MUD file server, the multiple MUD file servers include the first MUD file server, and the at least one target MUD file server includes the second MUD file server; or, according to the principle of sequential reading, updating the already obtained MUD files as a whole with the MUD files obtained from the most recently read MUD file server; or, reading and saving multiple MUD files in multiple MUD file servers in sequence; or, pre-specifying at least one target MUD file server from the multiple MUD file servers, and obtaining the MUD files in the at least one target MUD file server.
[0031] It should be noted that the at least one target MUD file server may be all the MUD file servers included in the multiple MUD file servers, or the at least one target MUD file server may also be some of the MUD file servers in the multiple MUD file servers.
[0032] In some possible implementations, the MUD control management device in the communication system is further used to process the at least one MUD file to obtain a target MUD file, and the target MUD file is used to constrain the network behavior of the terminal device.
[0033] As an example, the at least one MUD file includes a first MUD file and a second MUD file, the first MUD file includes a first device description item of the terminal device, the second MUD file includes a second device description item of the terminal device, the first device description item and the second device description item are different, and the target MUD file includes the first device description item and the second device description item.
[0034] In a possible implementation, the MUD control management device in the communication system is also used to obtain the MUD information used to describe the first device description item in the target MUD file based on the target MUD file processing strategy corresponding to the terminal device. The target MUD file processing strategy includes: when the multiple MUD files are obtained in sequence, the MUD information used to describe the first device description item in the most recently obtained MUD file is used as the MUD information used to describe the first device description item in the target MUD file; or, when the MUD information used to describe the first device description item exists in multiple MUD files, the MUD information used to describe the first device description item in the MUD file provided by the manufacturer of the terminal device is used as the MUD information used to describe the first device description item in the target MUD file; or, when multiple MUD files respectively include the first MUD information and the second MUD information used to describe the first device description item, the first MUD information and the second MUD information are obtained, and in the target MUD file, the first MUD information is associated with the first service, and the second MUD information is associated with the second service.
[0035] It should be noted that for the relevant description of the specific implementation method of the communication system provided in the fifth and sixth aspects and the effects achieved, please refer to the relevant description of the method provided in the above-mentioned first aspect or any possible implementation method of the first aspect.
[0036] In the seventh aspect, an embodiment of the present application further provides a computer-readable storage medium, which stores instructions, and when the computer-readable storage medium is run on a computer, enables the computer to execute the method provided in the first aspect or any possible implementation of the first aspect.
[0037] In an eighth aspect, an embodiment of the present application further provides a computer program product, including a computer program or computer-readable instructions. When the computer program or the computer-readable instructions are run on a computer, the computer executes the method provided in the aforementioned first aspect or any possible implementation of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.
[0039] Figure 1 A schematic diagram of a framework of a network 100 involved in an application scenario in an embodiment of the present application;
[0040] Figure 2 A schematic diagram of a communication system 200 according to an embodiment of the present application;
[0041] Figure 3 A signaling flow chart of a method 100 for obtaining a MUD file in an embodiment of the present application;
[0042] Figure 4 A signaling flow chart of a method 200 for obtaining a MUD file in an embodiment of the present application;
[0043] Figure 5 A method flow chart of a method 300 for obtaining a MUD file in an embodiment of the present application;
[0044] Figure 6 This is a structural diagram of a MUD control management device 600 in an embodiment of the present application;
[0045] Figure 7 This is a structural diagram of another MUD control management device 700 in an embodiment of the present application;
[0046] Figure 8 This is a structural diagram of another MUD control management device 800 in an embodiment of the present application;
[0047] Fig. 9 This is a schematic diagram of the structure of a communication system 900 in an embodiment of the present application;
[0048] Fig.10 Schematic diagram of the structure of another communication system 1000 in an embodiment of the present application. DETAILED DESCRIPTION
[0049] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings. The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions in the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. It is known to those skilled in the art that with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
[0050] In this application, ordinal numbers such as "1", "2", "3", "first", "second" and "third" are used to distinguish multiple objects but are not used to limit the order of multiple objects.
[0051] “A and / or B” mentioned in this application should be understood to include the following situations: only A, only B, or both A and B.
[0052] For the relevant contents of the MUD file involved in this application, please refer to the relevant instructions of the Internet Engineering Task Force (English: Internet Engineering Task Force, abbreviation: IETF) Request For Comments (English: Request For Comments, abbreviation: RFC) 8520: "Manufacturer Usage Description Specification". The above standard is incorporated into this application by reference in its entirety.
[0053] In order to constrain various terminal devices in the network, manufacturers usually generate corresponding MUD files before each terminal device leaves the factory. The network behavior of the terminal device is constrained by the MUD information corresponding to the device description items included in the MUD file. The device description items are specifically used to describe the network behavior related to the terminal device. Among them, the device description items may include, for example: the device type of the terminal device, network access rights, defined bandwidth, network priority, etc. The MUD information corresponding to the device description item is a specific description of the device description item. For example, the MUD information of the device description item that defines the bandwidth may be the numerical value of the bandwidth; for another example, the MUD information of the device description item of the network access rights may be the network access rights open to the terminal device.
[0054] In the embodiments of the present application, the terminal device may refer to any device that needs to access the network through a network device, such as a personal computer, a printer, a camera, a smart LED light, a conference room projection device, etc.
[0055] RFC 8520 is a set of protocol frameworks based on MUD files. According to RFC 8520, in order to save storage space on terminal devices, terminal device manufacturers usually save the generated MUD files on the MUD file server corresponding to the manufacturer, and only save the MUD URL corresponding to the MUD file on the terminal device. When the terminal device is connected to the network, the terminal device can send the MUD URL to the network device to which it is connected. The network device sends the MUD URL to the MUD control and management device. The MUD control and management device obtains the corresponding MUD file from the manufacturer's MUD file server based on the MUD URL, and maps the content of the MUD file to a network policy for constraining the network behavior of the terminal device.
[0056] It should be noted that, in the embodiment of the present application, the MUD control management device is assumed to be an absolutely reliable and safe device. According to the usage in RFC8520, the MUD control management device can be a MUD Manager (also known as a MUD Controller).
[0057] by Figure 1 Take the scenario shown as an example to explain the current method of obtaining MUD files.
[0058] Figure 1 This is a schematic diagram of a possible network architecture of an embodiment of the present application. Figure 1, the network 100 includes: terminal device 11, terminal device 12, ..., terminal device 1N (N is an integer greater than 1), network device 20, MUD control management device 30 and MUD file server 40. Among them, network device 20 can be an access device for terminal device 11, terminal device 12, ..., terminal device 1N (N is an integer greater than 1) to access the network, for example: the network device 20 can be a switch, a router or a firewall. The MUD control management device 30 can be any physical device that can realize the MUD Manager function, or it can be a functional module that can realize the MUD Manager function. As a functional module, the MUD control management device 30 can be integrated in any network device (such as network device 20). For example, when the MUD control management device 30 is integrated in the network device 20 as a functional module, it can exchange data with the network device 20, and can also interact with each terminal device through the communication interface of the network device 20, so as to realize the function of constraining the corresponding terminal device based on each MUD file. The MUD control management device 30 can obtain the MUD file, obtain the corresponding network policy according to the MUD file, and configure the network policy on the network device 20, so that the network device 20 implements the constraint on the corresponding terminal device based on the network policy. The MUD file server 40 can be a server used by the manufacturer to carry its corresponding MUD file. The MUD file stored on the MUD file server 40 corresponds to the MUD URL stored on the terminal device. The corresponding MUD file can be obtained from the MUD file server 40 based on the MUD URL provided by the terminal device.
[0059] As an example, the manufacturer can directly store the MUD URL in each terminal device. Then, taking the terminal device 11 as an example, the process of obtaining the MUD file may include: S11, when the terminal device 11 accesses the network, the terminal device 11 sends a message to the network device 20, and the message carries the MUD URL x, wherein the message may be, for example, a Link Layer Discovery Protocol (LLDP) request message or a Dynamic Host Configuration Protocol (DHCP) request message; S12, the network device 20 obtains the MUD URL x, and sends it directly or indirectly to the MUD control and management device 30; S13, the MUD control and management device 30 accesses the MUD file server 40 based on the MUD URL x, and obtains the MUD file 1 corresponding to the MUD URL x; S14, the MUD control and management device 30 obtains the network policy 1 according to the MUD file 1, and applies the network policy 1 to the network device 20; S15, the network device 20 that has applied the network policy 1 constrains the network behavior of the terminal device 11. The network behavior may include, for example, one or more of the network access rights, defined bandwidth, and network priority of the terminal device 11 .
[0060] From this example, we can see that, according to the current RFC 8520 protocol, the MUD control management device can only obtain a MUD file from the MUD file server corresponding to the manufacturer of the terminal device through the obtained MUD URL, and then restrict the network behavior of the terminal device based on a MUD file generated by the manufacturer.
[0061] However, in the process from the manufacturer's production to the user's use of the terminal device, many production (or deployment) links may require certain restrictions on the terminal device's network behavior and generate corresponding MUD files. For example: after the terminal device is produced by the manufacturer, it may also go through multiple intermediate production processes of multiple intermediate manufacturers before it is commercially deployed on the client side. In this case, the intermediate manufacturers or intermediate production processes may provide the terminal device with corresponding MUD files based on demand. For another example: after the terminal device is commercially deployed on the client side, it may also go through security reinforcement by the information security department, operation and maintenance enhancement by the Internet Technology (English: Internet Technology, abbreviated as: IT) maintenance department, etc. In this case, the security reinforcement or operation and maintenance enhancement process may also provide the terminal device with corresponding MUD files based on demand. So, if Figure 1 The network architecture shown cannot meet the demand for obtaining MUD files when multiple production (or deployment) links generate MUD files for a terminal device.
[0062] Based on this, an embodiment of the present application provides a communication system, which may include a terminal device, multiple MUD file servers and a MUD control and management device, wherein the MUD control and management device can communicate with the terminal device, and the MUD control and management device can also communicate with multiple MUD file servers respectively, and each of the multiple MUD file servers is used to store MUD files provided to the terminal device by one or more production (or deployment) links. For example: the communication system includes n MUD file servers, and each MUD file server includes 1 MUD file of the terminal device.
[0063] Figure 2 This is a schematic diagram of the architecture of a communication system 200 provided in an embodiment of the present application. Figure 2 In addition to the devices in the above-mentioned network 100, the communication system 200 also includes a MUD file server 50 and a MUD file server 60. The MUD file corresponding to the terminal device 11, in addition to the MUD file 1 generated by the manufacturer for the terminal device 11, also includes a MUD file 2 and a MUD file 3. Among them, MUD file 1 is stored in the MUD file server 40 corresponding to the manufacturer, corresponding to the MUD URL x stored in the terminal device 11; MUD file 2 can be stored in the MUD file server 50 corresponding to the intermediate integrator; MUD file 3 can be stored in the MUD file server 60 corresponding to the client side. It should be noted that the device description items included in multiple MUD files corresponding to a terminal device may be the same or different, and the MUD information of the same device description items in different MUD files may be the same or different. The MUD file generated in the subsequent production (or deployment) stage can be obtained by adding, deleting or modifying the device description items in the MUD file generated in the previous generation (or deployment) stage. For example: in Figure 2 In the scenario shown, MUD file 1 includes device description item 1 and device description item 2, the MUD information of device description item 1 is a1, and the MUD information of device description item 2 is b1; MUD file 2 can be based on MUD file 1 to add device description item 3, and modify the MUD information of device description item 1, such as: MUD file 2 includes device description item 1, device description item 2 and device description item 3, wherein the MUD information of device description item 1 is a2, the MUD information of device description item 2 is b1, and the MUD information of device description item 3 is c1; MUD file 3 can also be based on MUD file 2 to delete device description item 1 and device description item 2, and modify the MUD information of device description item 3, such as: MUD file 3 includes device description item 3, and the MUD information of device description item 3 is c2.
[0064] It can be seen that in the above-mentioned communication system provided by the embodiment of the present application, multiple MUD files of a terminal device are distributed on multiple MUD file servers, and these MUD files are network behavior constraints proposed by various production (or deployment) links to the terminal device. In this way, through the network framework in which multiple MUD files are distributed on multiple MUD file servers in the communication system, it becomes possible for each production (or deployment) link of the terminal device to generate multiple different MUD files for the terminal device respectively.
[0065] To facilitate understanding of similar Figure 2 The scenario shown in which multiple MUD files are distributed on multiple MUD file servers is explained below with an actual scenario. Assume that Company A purchases 50 conference terminals from Manufacturer B, designates Company C to install and deliver the 50 conference terminals, and Company A performs security and fixing operations on the 50 conference terminals. Then, the 50 conference terminals correspond to the terminal devices in the above-mentioned network 200, Manufacturer B corresponds to the manufacturer, Company C corresponds to the intermediate integrator, and Company A corresponds to the client side. Company A, Manufacturer B, and Company C provide MUD files for the 50 conference terminals, which are MUD file 1, MUD file 2, and MUD file 3 respectively; the MUD files provided by Company A, Manufacturer B, and Company C for the 50 conference terminals are stored on their respective servers, and the server of Company A corresponds to the MUD file server 60 in the above-mentioned network 200, the server of Manufacturer B corresponds to the MUD file server 40 in the above-mentioned network 200, and the server of Company C corresponds to the MUD file server 50 in the above-mentioned network 200. Among them, MUD file 1 represents the constraints imposed by the manufacturer of the terminal device on the network behavior of the terminal device, for example: whether manufacturer B allows the conference terminal to access external conferences; MUD file 2 represents the constraints imposed by the intermediate integrator of the terminal device on the network behavior of the terminal device, for example: Company C filters certain keywords output by the conference terminal; MUD file 3 represents the constraints imposed by the user side of the terminal device on the network behavior of the terminal device, for example: which conference terminals Company A allows to access external conferences.
[0066] In the communication system proposed in the embodiment of the present application, in order to realize accurate constraints on the network behavior of the terminal device, it is necessary to comprehensively consider the device description items in each MUD file of the terminal device and the MUD information of the device description items. However, in the current RFC 8520 protocol, the MUD control management device obtains a MUD file from the MUD file server corresponding to the manufacturer of the terminal device by obtaining the MUD URL by default, and does not support the mechanism of obtaining MUD files from the multiple MUD file servers. As a result, when multiple MUD files are distributed on multiple MUD file servers, it is impossible to obtain MUD files for the terminal device from multiple MUD file servers, and thus it is impossible to accurately constrain the network behavior of the terminal device.
[0067] Based on this, in an embodiment of the present application, a method for obtaining a manufacturer's user manual MUD file is provided. In a scenario where multiple MUD files are distributed on multiple MUD file servers, the method supports obtaining MUD files from multiple MUD file servers. Figure 2 In the communication system 200 shown, after receiving the MUD URL request message from the terminal device, the MUD control management device can obtain at least one MUD file from multiple MUD file servers according to the target acquisition strategy corresponding to the terminal device. It can be seen that in the method for obtaining MUD files provided in the embodiment of the present application, the MUD control management device has a target acquisition strategy corresponding to each terminal device, and can obtain MUD files from multiple MUD file servers based on the target acquisition strategy, so that in the scenario where multiple MUD files are distributed on multiple MUD file servers, the MUD files of the terminal device can be obtained from the multiple MUD file servers, thereby achieving more accurate constraints on the network behavior of the terminal device.
[0068] It should be noted that the target acquisition policy on the MUD control and management device is used to indicate the rules for obtaining at least one MUD file from multiple MUD file servers. For the target acquisition policy, in one case, it can be configured and saved by the user on the MUD control and management device; in another case, it can also be obtained and saved by the MUD control and management device from other devices. In the MUD control and management device, one terminal device corresponds to only one target acquisition policy, but one target acquisition policy can correspond to at least one terminal device, that is, the target acquisition policies corresponding to different terminal devices can be the same or different.
[0069] Among them, what is saved on the MUD control management device may be a first mapping relationship between the target acquisition strategy and the MUD URL provided to the terminal device by the manufacturer of the terminal device, so that after the MUD control management device obtains the MUD URL of the terminal device, the target acquisition strategy matching the MUD URL is determined from the first mapping relationship, thereby obtaining at least one MUD file from multiple MUD file servers based on the target acquisition strategy; or, what is saved on the MUD control management device may also be a second mapping relationship between the target acquisition strategy and the device information of the terminal device, so that after the MUD control management device obtains the device information of the terminal device, the target acquisition strategy matching the device information of the squadron device is determined from the second mapping relationship, thereby obtaining at least one MUD file from multiple MUD file servers based on the target acquisition strategy. Among them, the device information may be a unique identifier of the terminal device such as the device identifier, IP address or MAC address of the terminal device, or the device information may also be a batch identifier of the terminal device such as the device type of the terminal device, the network segment to which it belongs, or the manufacturer information. Taking the device type of the terminal device as an example, each device type corresponds to only one target acquisition strategy, and one target acquisition strategy can correspond to at least one device type. In this way, terminal devices belonging to the same device type must correspond to the same target acquisition strategy, and terminal devices of different device types may correspond to the same target acquisition strategy or different target acquisition strategies.
[0070] For example, still Figure 2 Taking the communication system 200 shown as an example, assuming that three mapping relationships between device information and acquisition strategies are pre-saved on the MUD control management device 30, and the device information is the device type, the three mapping relationships are: Mapping relationship 1: Device type A-Acquisition strategy 1 "Read and save multiple MUD files in multiple MUD file servers in sequence", Mapping relationship 2: Device type B-Acquisition strategy 2 "Pre-specify MUD file server 40 from multiple MUD file servers, and obtain MUD files in the MUD file server 40", Mapping relationship 3: Device type C-Acquisition strategy 3 "Pre-specify MUD file server 60 from multiple MUD file servers, and obtain MUD files in the MUD file server 60".
[0071] In specific implementation, the process of obtaining the MUD file may include: S21, when the terminal device 11 accesses the network, the terminal device 11 sends a MUD URL request message to the MUD control management device 30, and the MUD URL request message carries the MUD URL x; S22, the MUD control management device 30 parses the MUD URL x. URL request message, obtain the device type A of the terminal device 11; S23, the MUD control management device 30 determines from the three pre-saved mapping relationships that the mapping relationship 1 corresponds to the device type A of the terminal device 11, and uses the acquisition strategy 1 in the mapping relationship 1 as the target acquisition strategy; S24, the MUD control management device 30 determines based on the acquisition strategy 1 that the corresponding MUD files need to be obtained from the MUD file server 40, the MUD file server 50 and the MUD file server 60 respectively; S25, the MUD control management device 30 obtains MUD file 1 from the MUD file server 40; S26, the MUD control management device 30 obtains MUD file 2 from the MUD file server 50; S27, the MUD control management device 30 obtains MUD file 3 from the MUD file server 60; S28, the MUD control management device 30 determines the corresponding network policy 2 based on MUD file 1, MUD file 2 and MUD file 3, and applies the network policy 2 to the network device 20, so that the network device 20 can constrain the network behavior of the terminal device 11. Among them, S25, S26 and S27 can be executed successively or simultaneously, and the specific execution order is not limited.
[0072] In this way, by configuring the acquisition strategy on the MUD control management device 30, in a scenario where multiple MUD files are distributed on multiple MUD file servers, MUD files can be acquired from multiple MUD file servers, thereby achieving accurate constraints on the network behavior of terminal devices.
[0073] As another example, if three mapping relationships pre-saved on the MUD control management device 30 are updated according to actual needs, the updated mapping relationship 1 is specifically: Device Type A-Acquisition Strategy 4 "According to the MUD URL x provided to the terminal device by the manufacturer of the terminal device, redirect the MUD file server 40 corresponding to the MUD URL x to the MUD file server 50 and the MUD file server 60." Then, in the specific implementation, the process of obtaining the MUD file includes, in addition to the above-mentioned S21 and S22, the following: S23', the MUD control management device 30 determines from the three pre-saved mapping relationships that the device type A of the terminal device 11 corresponds to mapping relationship 1, and uses the acquisition strategy 4 in the mapping relationship 1 as the target acquisition strategy; S24', the MUD control management device 30 determines that the corresponding MUD files need to be obtained from the MUD file server 50 and the MUD file server 60 respectively based on the acquisition strategy 4 in the mapping relationship 1; S26, the MUD control management device 30 obtains MUD file 2 from the MUD file server 50; S27, the MUD control management device 30 obtains MUD file 3 from the MUD file server 60; S28', the MUD control management device 30 determines the corresponding network policy 3 based on MUD file 2 and MUD file 3, and applies the network policy 3 to the network device 20, so that the network device 20 can constrain the network behavior of the terminal device 11. Among them, S26 and S27 can be executed successively or simultaneously, and the specific execution order is not limited.
[0074] In this way, by flexibly defining different acquisition strategies according to actual needs on the MUD control management device 30, it becomes possible to obtain different MUD files according to different needs at different stages, and flexible constraints on the network behavior of the terminal device can be achieved.
[0075] It should be noted that the specific implementation details and effects can be found in the following Figure 3 The relevant descriptions in the method 100 are not repeated here.
[0076] It can be understood that the above scenario is only an example scenario provided by the embodiment of the present application, and the embodiment of the present application is not limited to this scenario.
[0077] Combine the following Figure 3 ,by Figure 2 Taking the communication system 200 shown as an example, specifically taking the terminal device 11 in the communication system 200 as an example, the method 100 for obtaining MUD files provided in an embodiment of the present application is introduced.
[0078] Figure 3A method 100 for obtaining a MUD file provided in an embodiment of the present application is shown. The method 100 may include the following S101 to S103:
[0079] S101 , the terminal device 11 sends a MUD URL request message 1 to the MUD control management device 30 .
[0080] S102 , the MUD control management device 30 receives the MUD URL request message 1 sent by the terminal device 11 .
[0081] When the terminal device 11 needs to access the network, the terminal device 11 can execute S101 and send a MUD URL request message 1 to the MUD control management device 30. The MUD URL request message 1 is used to request the MUD control management device 30 to obtain the MUD file of the terminal device 11, so as to subsequently constrain the network behavior of the terminal device 11 according to the MUD file. The MUD URL request message 1 carries the MUD URL x provided to the terminal device 11 by the manufacturer of the terminal device 11.
[0082] As an example, the MUD URL request message 1 may be an 802.1X request message, then S101 may specifically include: the terminal device 11 sends an 802.1X request message to the MUD control management device 30, and the 802.1X request message carries the MUD URL x provided to the terminal device 11 by the manufacturer of the terminal device 11.
[0083] As another example, the MUD URL request message 1 may also be a DHCP request message or a LLDP request message, then S101 may specifically include: the terminal device 11 sends a DHCP request message or a LLDP request message to the MUD control management device 30, and the DHCP request message or the LLDP request message carries the MUD URL x provided by the manufacturer of the terminal 11 to the terminal device 11. For example: the DHCP request message or the LLDP request message may carry the MUD URL x provided by the manufacturer of the terminal device 11 to the terminal device 11 through an extended option (English: OPTION) field or a type-length value (English: Type-Length-Value, abbreviated: TLV) field.
[0084] Among them, MUD URL x is built into the terminal device 11 by the manufacturer when the terminal device 11 leaves the factory, and is used to obtain the MUD file 1 generated by the manufacturer for the terminal device 11 from the MUD file server 40 corresponding to the manufacturer. There is a one-to-one correspondence between the MUD file 1, the MUD file server 40 and the MUD URL x. The MUD URL x may include: the manufacturer of the terminal device 11, the device type of the terminal device 11, the firmware version number of the terminal device 11, the system version number of the terminal device 11 and other information. For example: MUD URL x is https: / / www.huawei.com / mud / router / firmware_version_1234 / os_version_4321.json. Based on the MUD URL x, it can be known that the manufacturer of the terminal device 11 is Huawei, the device type is router, the firmware version number of the terminal device 11 is 1234, and the system version number of the terminal device is 4321.
[0085] After receiving the MUD URL request message 1 sent by the terminal device 11, the MUD control management device 30 can obtain the MUD URL x from the MUD URL request message 1. In addition, the MUD control management device 30 can also obtain the device information X of the terminal device 11 from the MUD URL request message 1. In one case, the MUD control management device 30 can obtain the device information X of the terminal device 11 by parsing the MUD URL x, for example: obtaining the device type X of the terminal device 11 by parsing the MUD URL x, and using the device type X as the device information X of the terminal device 11; in another case, the MUD control management device 30 can obtain the device information X of the terminal device 11 through other contents in the MUD URL request message 1 except the MUD URL x, for example: obtaining the source Internet Protocol (English: Internet Protocol, abbreviated: IP) address carried in the MUD URL request message 1, obtaining the network segment X to which the terminal device 11 belongs through the source IP address, and using the network segment X as the device information X of the terminal device 11.
[0086] Among them, the device information X of the terminal device 11 specifically refers to one or more attribute information of the terminal device 11, for example: the device information X of the terminal device 11 includes but is not limited to at least one of the following information: the device identification X of the terminal device 11, the device type X of the terminal device 11, the manufacturer information X of the terminal device 11, the network segment X to which the terminal device 11 belongs, the IP address of the terminal device 11 or the MAC address of the terminal device 11.
[0087] S103 , the MUD control management device 30 obtains at least one MUD file from a plurality of MUD file servers based on the target acquisition strategy X corresponding to the terminal device 11 .
[0088] Among them, between S102 and S103, the embodiment of the present application may further include a process in which the MUD control management device 30 determines the target acquisition strategy X corresponding to the terminal device 11, for example, the following S104 may be included between S102 and S103:
[0089] S104 , the MUD control management device 30 determines a target acquisition strategy X corresponding to the terminal device 11 from at least one pre-configured acquisition strategy.
[0090] At least one acquisition strategy is pre-configured and stored in the MUD control management device 30 according to actual needs, wherein the acquisition strategy is used to indicate the rules for obtaining MUD files from multiple MUD file servers.
[0091] If only one acquisition strategy is configured and saved on the MUD control management device 30, then the MUD control management device 30 can directly use the acquisition strategy as the target acquisition strategy X and execute S103.
[0092] If multiple acquisition strategies are configured and saved on the MUD control management device 30, then multiple mapping relationships including acquisition strategies can be saved on the MUD control management device 30. In specific implementation, S104 can specifically include: the MUD control management device 30 determines a mapping relationship corresponding to the terminal device 11 from at least one mapping relationship saved locally, and records the acquisition strategy in the determined mapping relationship as the target acquisition strategy X.
[0093] As an example, the multiple mapping relationships may specifically be first mapping relationships between acquisition strategies and the MUD URLs of terminal devices, and the multiple first mapping relationships include a first mapping relationship X1 between the target acquisition strategy X and the MUD URL x of the terminal device 11. For example: the MUD control and management device 30 stores m (m is greater than or equal to 1) first mapping relationships, namely: MUD URL x-acquisition strategy 1, MUD URL 2-acquisition strategy 2, ..., MUD URL m-acquisition strategy m, wherein the acquisition strategies 1 to acquisition strategies m may be the same or different, and the MUD URLs in MUD URL x to MUD URL m are all different, and the above m first mapping relationships include a first mapping relationship X1: MUD URL x-target acquisition strategy X. In this example, S104 may specifically include: the MUD control and management device 30 may search for the first mapping relationship X1 whose MUD URL is MUD URL x from at least one first mapping relationship, and record the acquisition strategy X in the first mapping relationship X1 as the target acquisition strategy X.
[0094] As another example, the multiple mapping relationships may specifically be second mapping relationships between acquisition strategies and device information of terminal devices, and the multiple second mapping relationships include a second mapping relationship X1 between the target acquisition strategy X and the device information X of the terminal device 11. For example: the MUD control and management device 30 stores m second mapping relationships, namely: device information 1-acquisition strategy 1, device information 2-acquisition strategy 2, ..., device information m-acquisition strategy m, wherein acquisition strategies 1 to acquisition strategies m may have the same acquisition strategies or may be different, and the contents of device information 1 to device information m are all different, and the above m second mapping relationships include a second mapping relationship X1: device information X-target acquisition strategy X. In this example, S104 may specifically include: the MUD control and management device 30 may search for a second mapping relationship X1 whose device information is device information X from at least one second mapping relationship, and record the acquisition strategy X in the second mapping relationship X1 as the target acquisition strategy X.
[0095] The target acquisition strategy X is one of the acquisition strategies preset by the MUD control management device. The following are several possible target acquisition strategies X:
[0096] As a first example, the target acquisition strategy X may specifically be: according to the MUD URL provided to the terminal device by the manufacturer of the terminal device, redirect the first MUD file server corresponding to the MUD URL to at least one target MUD file server among multiple MUD file servers, and acquire the MUD files in the at least one target MUD file server. The first MUD file server belongs to multiple MUD file servers, and the at least one target MUD file server after redirection includes a second MUD file server, and the second MUD file server and the first MUD file server are different servers. Taking network device 200 as an example, the target acquisition policy X corresponds to terminal device 11. When MUD file server 40 is redirected to MUD file server 40 and MUD file server 50, target acquisition policy X may specifically indicate: according to the MUD URL x of terminal device 11, redirect the MUD file server 40 corresponding to the MUD URL x to MUD file server 40 and MUD file server 50, and obtain MUD file 1 and MUD file 2 from MUD file server 40 and MUD file server 50 respectively; or, when MUD file server 40 is redirected to MUD file server 40, MUD file server 50 and MUD file server 60, target acquisition policy X may also specifically indicate: according to the MUD URL x of terminal device 11, the MUD URL x is redirected to MUD file server 40, MUD file server 50 and MUD file server 60. The MUD file server 40 corresponding to x is redirected to MUD file server 40, MUD file server 50 and MUD file server 60, and MUD file 1, MUD file 2 and MUD file 3 are obtained from MUD file server 40, MUD file server 50 and MUD file server 60 respectively; or, when MUD file server 40 is redirected to MUD file server 60, the target acquisition strategy X may further specifically indicate: according to the MUD URL x of the terminal device 11, the MUD file server 40 corresponding to the MUD URL x is redirected to MUD file server 60, and MUD file 3 is obtained from MUD file server 60.
[0097] As a second example, the target acquisition strategy X may also specifically be: pre-specify at least one target MUD file server from the multiple MUD file servers, and acquire the MUD files in the at least one target MUD file server. Taking the network device 200 as an example, when the specified target MUD file servers include: MUD file server 40 and MUD file server 50, then the target acquisition strategy X may specifically indicate: acquire MUD file 1 and MUD file 2 from MUD file server 40 and MUD file server 50, respectively; or, when the specified target MUD file servers include: MUD file server 40, MUD file server 50 and MUD file server 60, then the target acquisition strategy X may specifically indicate: acquire MUD file 1, MUD file 2 and MUD file 3 from MUD file server 40, MUD file server 50 and MUD file server 60, respectively; or, when the specified target MUD file server includes: MUD file server 60, then the target acquisition strategy X may specifically indicate: acquire MUD file 3 from MUD file server 60.
[0098] As a third example, the target acquisition strategy X may also specifically be: according to the principle of sequential reading, the MUD file obtained from the most recently read MUD file server is used to update the already obtained MUD file as a whole. Still taking the network device 200 as an example, the target acquisition strategy X corresponding to the terminal device 11 may specifically indicate: according to the principle of sequentially reading all MUD file servers in order from first to last in production (or deployment), the MUD control management device 30 first reads MUD file 1 from the MUD file server 40; then reads MUD file 2 from the MUD file server 50 and updates MUD file 1 as a whole with MUD file 2; then reads MUD file 3 from the MUD file server 60 and updates MUD file 2 as a whole with MUD file 3. Alternatively, the target acquisition strategy X corresponding to the terminal device 11 may specifically indicate: according to the principle of sequentially reading other MUD file servers except the MUD file server 40 in the order of production (or deployment) from the back to the front, the MUD control management device 30 first reads the MUD file 3 from the MUD file server 60; then reads the MUD file 2 from the MUD file server 50 and updates the MUD file 3 as a whole with the MUD file 2. It should be noted that in the third example, the target MUD file server includes all or part of the multiple MUD file servers specified by the principle of sequential reading in the target acquisition strategy X.
[0099] As a fourth example, the target acquisition strategy X may specifically be: sequentially read and save multiple MUD files in multiple MUD file servers. Still taking the network device 200 as an example, the target acquisition strategy X corresponding to the terminal device 11 may specifically indicate: read MUD file 1, MUD file 2, and MUD file 3 from the MUD file server 40, MUD file server 50, and MUD file server 60 corresponding to the terminal device 11, respectively. It should be noted that in this fourth example, the target MUD file server includes a MUD file server among the multiple MUD file servers of the terminal device.
[0100] It should be noted that, in the embodiment of the present application, the multiple MUD file servers are all MUD servers corresponding to the terminal device 11, and each of the multiple MUD file servers stores a MUD file generated for the terminal device 11 in one or more production (or deployment) links. Figure 2 In the communication system 200 shown, the multiple MUD file servers corresponding to the terminal device 11 include: MUD file server 40, MUD file server 50 and MUD file server 60. The target MUD file server is one of the multiple MUD file servers. For example, the target MUD file server corresponding to the terminal device 11 may be: MUD file server 40, MUD file server 50 or MUD file server 60. At least one target MUD file server is all or part of the multiple MUD file servers. For example, the at least one target MUD file server corresponding to the terminal device 11 may include: MUD file server 40, MUD file server 50 and MUD file server 60; or, the target MUD file server corresponding to the terminal device 11 may also be: MUD file server 40.
[0101] Executing S104 to obtain the target acquisition strategy X corresponding to the terminal device 11 provides a basis for executing S103.
[0102] For the MUD control management device 30 in S103 obtaining at least one MUD file from multiple MUD file servers based on the target acquisition strategy X corresponding to the terminal device 11, as an example, it can include: the MUD control management device 30 first determines at least one target MUD file server from multiple MUD file servers according to the target acquisition strategy X corresponding to the terminal device 11; and then obtains the at least one MUD file from the at least one target MUD file server.
[0103] As an example, if the target acquisition strategy X is: according to the MUD URL provided to the terminal device by the manufacturer of the terminal device, redirect the first MUD file server corresponding to the MUD URL to at least one target MUD file server among multiple MUD file servers, and obtain the MUD files in the at least one target MUD file server. Among them, the first MUD file server belongs to multiple MUD file servers, and the at least one target MUD file server after the redirection usually cannot include only the first MUD file server. It can be determined that the at least one target MUD file server includes a second MUD file server, and the second MUD file server and the first MUD file server are different servers. Taking network device 200 as an example, assuming that the target acquisition policy X redirects MUD file server 40 to MUD file server 40 and MUD file server 50, then S103 may specifically include: MUD control management device 30 determines at least one target MUD file server from MUD file server 40, MUD file server 50 and MUD file server 60, including MUD file server 40 and MUD file server 50, thereby obtaining MUD file 1 and MUD file 2 from MUD file server 40 and MUD file server 50 respectively. Still taking network device 200 as an example, assuming that the target acquisition policy X redirects MUD file server 40 to MUD file server 40, MUD file server 50 and MUD file server 60, then S103 may specifically include: MUD control management device 30 determines at least one target MUD file server from MUD file server 40, MUD file server 50 and MUD file server 60, thereby obtaining MUD file 1, MUD file 2 and MUD file 3 from MUD file server 40, MUD file server 50 and MUD file server 60 respectively.
[0104] As another example, if the target acquisition strategy X is: pre-specify at least one target MUD file server from the multiple MUD file servers, and obtain the MUD file in the at least one target MUD file server. Taking the network device 200 as an example, assuming that the at least one target MUD file server specified in the target acquisition strategy X is the MUD file server 40, then S103 may specifically include: the MUD control management device 30 determines that at least one target MUD file server is the MUD file server 40 from the MUD file server 40, the MUD file server 50 and the MUD file server 60, thereby obtaining the MUD file 1 from the MUD file server 40. Still taking network device 200 as an example, assuming that at least one target MUD file server specified in target acquisition policy X is MUD file server 40, MUD file server 50 and MUD file server 60, then S103 may specifically include: MUD control management device 30 determines at least one target MUD file server from MUD file server 40, MUD file server 50 and MUD file server 60 as MUD file server 40, MUD file server 50 and MUD file server 60, thereby obtaining MUD file 1, MUD file 2 and MUD file 3 from MUD file server 40, MUD file server 50 and MUD file server 60 respectively.
[0105] As another example, if the target acquisition strategy X is: according to the principle of sequential reading, the MUD file obtained from the most recently read MUD file server is used to update the already obtained MUD file as a whole. Taking the network device 200 as an example, assuming that the principle of sequential reading in the target acquisition strategy X is: the principle of reading all MUD file servers in order from first to last in production (or deployment), then S103 may specifically include: the MUD control management device 30 first reads MUD file 1 from the MUD file server 40; then reads MUD file 2 from the MUD file server 50 and updates MUD file 1 as a whole with MUD file 2; then, reads MUD file 3 from the MUD file server 60 and updates MUD file 2 as a whole with MUD file 3. Taking network device 200 as an example, assuming that the principle of sequential reading in target acquisition policy X is: reading other MUD file servers except MUD file server 40 in order from back to front in production (or deployment), then S103 may specifically include: MUD control management device 30 first reads MUD file 3 from MUD file server 60; then reads MUD file 2 from MUD file server 50 and updates MUD file 3 as a whole with MUD file 2. It should be noted that, in this example, the target MUD file server includes all or part of the multiple MUD file servers specified by the principle of sequential reading in target acquisition policy X.
[0106] As another example, if the target acquisition strategy X is: read and save multiple MUD files in multiple MUD file servers in sequence. Still taking the network device 200 as an example, S103 may specifically include: MUD reads MUD file 1, MUD file 2 and MUD file 3 from MUD file server 40, MUD file server 50 and MUD file server 60, respectively. It should be noted that, in this example, the at least one target MUD file server includes all MUD file servers in the multiple MUD file servers of the terminal device.
[0107] It should be noted that the target MUD file server in the target acquisition strategy X is determined according to actual needs. In one example, the target MUD file server can be determined by considering the trust in each production (or deployment) link. For example, if the manufacturer is trusted, the MUD file server 40 corresponding to the manufacturer is designated as the target MUD file server. For another example, if the user himself is trusted, the MUD file server 60 corresponding to the user is designated as the target MUD file server. For another example, the target MUD file server can also be determined based on business needs. In another example, the target MUD file server can also be determined by considering the subsequent processing characteristics of the MUD file.
[0108] In some other possible implementations, if the target acquisition strategy X can also indicate the location of the MUD file corresponding to the terminal device 11 stored on each target MUD file server, that is, the target acquisition strategy X indicates at least one target MUD URL. Then, S103 may specifically include: the MUD control management device 30 first determines at least one target MUD URL based on the target acquisition strategy X; and then obtains at least one MUD file based on the at least one target MUD URL. The number of at least one target MUD URL is less than or equal to the number of all MUD file servers included in the multiple MUD file servers.
[0109] Among them, the MUD control management device 30 knows multiple MUD URLs of all MUD files generated by the terminal device 11 in various production (or deployment) links. The location of MUD file 1 of the terminal device 11 on the MUD file server 40 is MUD URLx, the location of MUD file 2 on the MUD file server 50 is MUD URL y, and the location of MUD file 3 on the MUD file server 60 is MUD URL z. The MUD control management device 30 can determine at least one target MUD URL from multiple MUD URLs based on the target acquisition strategy X. Among them, the target MUD URL is a MUD URL in multiple MUD ULRs. For example, the target MUD URL corresponding to the terminal device 11 can be: MUD URL x, MUD URL y or MUD URL z. At least one target MUD URL is all or part of the MUD URLs in multiple MUD URLs. For example, the at least one target MUD URL corresponding to the terminal device 11 can include: MUD URL x, MUD URL y and MUD URL z; or, the target MUD URL corresponding to the terminal device 11 can also be: MUD URL x.
[0110] As an example, the target acquisition strategy X may also be to redirect the MUD file server 40 corresponding to the MUD URL x stored in the terminal device 11 to at least one target MUD URL. For example: when the target acquisition strategy X redirects the MUD file server 40 corresponding to the MUD URL x to MUD URL x, MUD URL y and MUD URL z, then the at least one target MUD URL includes MUD URL x, MUD URL y and MUD URL z; for another example: when the target acquisition strategy X redirects the MUD file server 40 corresponding to the MUD URL x to the MUD URL z, then the at least one target MUD URL only includes MUD URL z. In this embodiment, S103 may specifically include: the MUD control management device 30 determines at least one target MUD URL to which the MUD control management device 30 corresponding to the MUD URL x is redirected based on the target acquisition strategy X, and obtains at least one MUD file based on the at least one target MUD URL.
[0111] It should be noted that the target MUD URL in the target acquisition strategy X can be determined based on actual needs. For example, the target MUD URL can be determined based on the trust in each production (or deployment) link; for example, the target MUD URL can also be determined based on business needs; for example, the target MUD URL can also be determined based on the subsequent processing characteristics of the MUD file.
[0112] In this way, S103 can be: the MUD control management device 30 obtains the MUD file corresponding to the terminal device 11 from each target MUD file server in at least one target MUD file server respectively; or, S103 can also be: the MUD control management device 30 obtains the corresponding MUD file from the location of the target MUD URL on the MUD file server corresponding to the target MUD URL based on each target MUD URL in at least one target MUD URL.
[0113] After the MUD control management device 30 obtains at least one MUD file from multiple MUD file servers, it can comprehensively consider the at least one MUD file, determine the network policy corresponding to the terminal device 11, and apply the network policy to the network device 20, so that the network device 20 constrains the network behavior of the terminal device 11 based on the network policy. The processing method of the at least one MUD file obtained can be specifically referred to as follows Figure 4 Method 200 is shown.
[0114] It can be seen that through the method 100 provided in the embodiment of the present application, for the scenario where multiple MUD files are distributed on different MUD file servers, when a terminal device accesses the network, the MUD control management device obtains at least one MUD file from multiple MUD file servers through the target acquisition strategy corresponding to the terminal device on the MUD control management device, so that the method 100 supports obtaining MUD files from multiple MUD file servers, thereby being able to achieve more accurate constraints on the network behavior of the terminal device based on the MUD files obtained from multiple MUD file servers.
[0115] It should be noted that the method 100 provided in the embodiment of the present application can also flexibly adjust the target acquisition strategy corresponding to the terminal device on the MUD control management device according to changes in demand. By flexibly defining different target acquisition strategies on the MUD control management device according to actual needs, the mechanism for acquiring MUD files provided by the method 100, which is applicable to the scenario where multiple MUD files are distributed on multiple MUD file servers, is more flexible, and it also makes it possible to acquire different MUD files according to different needs at different stages. For example, it can support terminal devices to acquire MUD files in the event of changes in business needs, functional changes, or equipment maintenance, thereby achieving flexible and accurate constraints on the network behavior of the terminal device.
[0116] After obtaining at least one MUD file of the terminal device 11 through S103, if the at least one MUD file is one MUD file, for example, only MUD file 1 is obtained, then the MUD control management device 30 can convert the MUD file 1 into network policy 1, and apply the network policy 1 to the network device 20, so that the network device 20 constrains the network behavior of the terminal device 11 based on the network policy 1. If the at least one MUD file is at least two MUD files, then in order to avoid conflicts in the MUD information of the same device description item and better realize the constraints on the network behavior of the terminal device 11, the MUD control management device 30 needs to process the at least two MUD files and obtain the processed target MUD file, and then convert the target MUD file into network policy 2, and apply the network policy 2 to the network device 20, so that the network device 20 constrains the network behavior of the terminal device 11 based on the network policy 2.
[0117] The present application embodiment also provides another method 200 for obtaining a MUD file. Figure 4 As shown, after S103, the method 200 may further include the following S105 to S108:
[0118] S105, the MUD control management device 30 processes at least one MUD file to obtain a target MUD file.
[0119] As an example, S105 may include:
[0120] S1051 , the MUD control management device 30 determines a target MUD file processing policy X corresponding to the terminal device 11 from at least one pre-configured MUD file processing policy.
[0121] S1052, the MUD control management device 30 processes the at least one MUD file based on the target MUD file processing policy X to obtain a target MUD file.
[0122] According to actual needs, at least one MUD file processing strategy may be pre-configured and stored in the MUD control management device 30. The MUD file processing strategy is used to indicate a rule for processing the obtained at least one MUD file to obtain a target MUD file.
[0123] If only one MUD file processing policy is configured and saved on the MUD control management device 30, then the MUD control management device 30 can directly use the MUD file processing policy as the target MUD file processing policy X and execute subsequent steps.
[0124] If multiple MUD file processing policies are configured and saved on the MUD control management device 30, then multiple mapping relationships including MUD file processing policies can be saved on the MUD control management device 30. In specific implementation, S1051 can specifically include: the MUD control management device 30 determines a mapping relationship corresponding to the terminal device 11 from at least one mapping relationship saved locally, and records the MUD file processing policy in the determined mapping relationship as the target MUD file processing policy X. As an example, the multiple mapping relationships can specifically be a mapping relationship between the MUD file processing policy and the MUD URL of the terminal device, and the multiple mapping relationships include a mapping relationship X2 between the target MUD file processing policy X and the MUD URL x of the terminal device 11. As another example, the multiple mapping relationships can specifically be a mapping relationship between an acquisition policy and the device information of the terminal device, and the multiple mapping relationships include a mapping relationship X2 between the target MUD file processing policy X and the device information X of the terminal device 11.
[0125] In a possible implementation, the target MUD file processing policy X may indicate that a MUD file generated by a specific production (or deployment) link among at least two MUD files is the target MUD file. For example, assuming that the MUD files obtained in S103 include MUD file 1, MUD file 2, and MUD file 3, the target MUD file processing policy X may indicate that MUD file 1 generated by the only trusted manufacturer is the target MUD file; or, the processing policy may also indicate that the newly generated MUD file 3 is the target MUD file.
[0126] In another possible implementation, the target MUD file processing strategy X may also indicate a method for generating a target MUD file by integrating device description items in at least two MUD files. The target MUD file processing strategy X may include not only a method 1 for indicating determination of device description items in the target MUD file, but also a method 2 for indicating determination of MUD information in device description items in the target MUD file. Among them, method 1 and method 2 may be set according to actual needs.
[0127] For method 1, it can be specifically used to indicate taking the union or intersection of the device description items included in each of the obtained MUD files to obtain the device description items in the target MUD file. For example: the at least one MUD file includes MUD file 1 and MUD file 2, wherein MUD file 1 includes device description item 1 and device description item 2, and MUD file 2 includes device description item 2 and device description item 3. Then, in one case, according to the union indication of the target MUD file processing strategy X, the target MUD file may include device description item 1, device description item 2, and device description item 3; in another case, according to the intersection indication of the target MUD file processing strategy X, the target MUD file may include device description item 2.
[0128] For mode 2, it can be specifically indicated that the MUD information of each device description item in the target MUD file is determined based on the MUD information of the device description items in each MUD file obtained.
[0129] As an example, mode 2 may indicate that the MUD information of the same device description item in the target MUD file shall be based on the MUD information of the device description item in a specific MUD file. For example: the at least one MUD file includes MUD file 1 and MUD file 2, wherein MUD file 1 includes device description item 2 with MUD information Q1, and MUD file 2 includes device description item 2 with MUD information Q2. Then, in one case, if the target MUD file processing policy X indicates that for the MUD information of the same device description item in the target MUD file, the MUD information in the MUD file provided by the manufacturer of the terminal device 11 (i.e., the MUD information in MUD file 1) shall prevail, then, according to the instruction of the target MUD file processing policy X, the MUD information of the device description item 2 in the target MUD file is Q1; in another case, if the target MUD file processing policy X indicates that for the same device description item in the target MUD file, the MUD information in MUD file 2 shall prevail, then, according to the instruction of the target MUD file processing policy X, the MUD information of the device description item 2 in the target MUD file is Q2.
[0130] As another example, method 2 may also indicate that the MUD information of the same device description item in the target MUD file is the result of a first operation on the MUD information of the device description item in at least two MUD files. For example: the at least one MUD file includes MUD file 1 and MUD file 2, wherein MUD file 1 includes device description item 2 with MUD information Q1, and MUD file 2 includes device description item 2 with MUD information Q2. Then, according to the instructions of the target MUD file processing strategy X, the MUD information of device description item 2 in the target MUD file is Q=f(Q1, Q2), wherein f() may specifically be any first operation performed on the MUD information of the same device description item in different MUD files, such as: f(Q1, Q2)=min(Q1, Q2), and also such as: f(Q1, Q2)=(Q1, Q2) / 2.
[0131] As another example, method 2 may also indicate that the same device description item retains multiple MUD information, and the multiple MUD information are respectively associated with different services. For example: the at least one MUD file includes MUD file 1 and MUD file 2, wherein MUD file 1 includes device description item 2 with MUD information Q1, and MUD file 2 includes device description item 2 with MUD information Q2. Then, according to the instructions of the target MUD file processing policy X, the MUD information Q1 of the device description item 2 in the target MUD file is associated with service 1, and the MUD information Q2 of the device description item 2 is associated with service 2. In this way, when the terminal device 11 executes different services, the network behavior of the terminal device 11 can be constrained based on the MUD information of the device description item corresponding to the service.
[0132] The MUD control management device 30 executes S1051 to obtain the target MUD file processing policy X, which provides a basis for S1052.
[0133] For S1052, the MUD control management device 30 determines a target MUD file based on the target MUD file processing policy X, wherein the target MUD file includes at least one device description item and MUD information corresponding to the at least one device description item. Each device description item in the target MUD file and the MUD information of the device description item are used to constrain the network behavior of the network device 11.
[0134] As an example, if the target MUD file processing policy X indicates that a MUD file generated by a specific production (or deployment) link among at least two MUD files is the target MUD file, then S1052 is specifically: the MUD control management device 30 obtains the MUD file indicated by the target MUD file processing policy X from at least one MUD file obtained based on the target MUD file processing policy X, and uses the MUD file as the target MUD file. For example: assuming that the MUD files obtained in S103 include MUD file 1, MUD file 2, and MUD file 3, and the target MUD file processing policy X indicates that MUD file 1 generated by the only trusted manufacturer is the target MUD file, then S1052 is specifically that the MUD control management device 30 determines MUD file 1 from MUD file 1, MUD file 2, and MUD file 3 as the target MUD file.
[0135] As another example, if the target MUD file processing policy X indicates that the target MUD file is generated by integrating the device description items in at least two MUD files.
[0136] Wherein, assuming that the target MUD file processing policy X indicates that the device description items in the target MUD file are the union of the device description items included in each MUD file, then S1052 may include: the MUD control management device obtains the device description items from each obtained MUD file, and takes the union of the device description items of each MUD file as the device description items included in the target MUD file. For example: the at least one MUD file includes MUD file 1 and MUD file 2, wherein MUD file 1 includes device description item 1 and device description item 2, and MUD file 2 includes device description item 2 and device description item 3, then the target MUD file generated by S1052 may include device description item 1, device description item 2, and device description item 3.
[0137] Assuming that the target MUD file processing policy X indicates that the device description items in the target MUD file are the intersection of the device description items included in each MUD file, then S1052 may include: the MUD control management device 30 obtains the device description items from each MUD file obtained, and takes the intersection of the device description items of each MUD file as the device description items included in the target MUD file. For example: the at least one MUD file includes MUD file 1 and MUD file 2, wherein MUD file 1 includes device description item 1 and device description item 2, and MUD file 2 includes device description item 2 and device description item 3, then the target MUD file generated by S1052 may include device description item 2.
[0138] After determining the device description items of the target MUD file, the MUD information of each device description item may also be determined based on any one of the following methods.
[0139] If a device description item of the target MUD file only appears in one of the obtained MUD files, or if a device description item of the target MUD file appears in different MUD files obtained and the MUD information of the device description item in the different MUD files is the same, then S1052 may include: the MUD control management device 30 determines the MUD information of the device description item in the obtained MUD file as the MUD information of the device description item in the target MUD file.
[0140] If a device description item of the target MUD file appears in different MUD files obtained, and the MUD information of the device description item in different MUD files is different, then S1052 may include: the MUD control management device 30 processes the MUD information of the device description item in different MUD files based on the target MUD file processing strategy X to obtain the MUD information of the device description item in the target MUD file.
[0141] In one case, the target MUD file processing policy X indicates that the MUD information of the same device description item in the target MUD file shall be based on the MUD information of the device description item in the specific MUD file. In this case, the MUD control management device 30 in S1052 determines, based on the target MUD file processing policy X, that the MUD information of the device description item in the specific MUD file is the MUD information of the device description item in the target MUD file. For example: the at least one MUD file includes MUD file 1 and MUD file 2, wherein MUD file 1 includes device description item 2 with MUD information Q1, and MUD file 2 includes device description item 2 with MUD information Q2, and the target MUD file processing policy X indicates that for the same device description item, the MUD information in the target MUD file shall be based on the MUD information in the MUD file provided by the manufacturer of the terminal device 11 (i.e., the MUD information in MUD file 1), then the MUD information of device description item 2 in the target MUD file generated by S1052 is Q1; for another example: the target MUD file processing policy X indicates that for the same device description item, the MUD information in the target MUD file shall be based on the MUD information in MUD file 2, then the MUD information of device description item 2 in the target MUD file generated by S1052 is Q2.
[0142] In another case, the target MUD file processing policy X indicates that the MUD information of the same device description item in the target MUD file is the result of a first operation on the MUD information of the device description item in at least two MUD files. In this case, the MUD control management device 30 in S1052 obtains different MUD information of the same device description item from at least two MUD files based on the target MUD file processing policy X, performs a first operation on the different MUD information, and records the operation result as the MUD information of the device description item in the target MUD file. For example: the at least one MUD file includes MUD file 1 and MUD file 2, wherein MUD file 1 includes device description item 2 with MUD information Q1, and MUD file 2 includes device description item 2 with MUD information Q2. Then, the MUD information of device description item 2 in the target MUD file generated by S1052 is Q=f(Q1, Q2), wherein f() is the first operation in the target MUD file processing strategy X, such as: f(Q1, Q2)=min(Q1, Q2), and another example: f(Q1, Q2)=(Q1, Q2) / 2.
[0143] In another case, the target MUD file processing policy X indicates that the same device description item retains multiple MUD information, and the multiple MUD information are respectively associated with different services. For example: the at least one MUD file includes MUD file 1 and MUD file 2, wherein MUD file 1 includes device description item 2 with MUD information Q1, and MUD file 2 includes device description item 2 with MUD information Q2. Then, in the target MUD file generated by the MUD control management device 30 based on the target MUD file processing policy X in S1052, the MUD information Q1 of the device description item 2 is associated with service 1, and the MUD information Q2 of the device description item 2 is associated with service 2.
[0144] S106 , the MUD control management device 30 converts the target MUD file into a network policy 2 .
[0145] S107 , the MUD control management device 30 sends the network policy 2 to the network device 20 .
[0146] S108 , the network device 20 constrains the network behavior of the terminal device 11 based on the network policy 2 .
[0147] The implementation method of S106 to S108 is consistent with that specified in the RFC 8520 protocol. For specific implementation methods and related descriptions, please refer to the relevant instructions in RFC 8520 and will not be repeated here.
[0148] It should be noted that, on the MUD control management device 30, in one case, there can be two sets of mapping relationships: the first set is the mapping relationship between at least one acquisition strategy and the device information of the terminal device (or the acquisition strategy and the MUD URL provided by the manufacturer for the terminal device), and the second set is the mapping relationship between at least one MUD file processing strategy and the device information of the terminal device (or the MUD file processing strategy and the MUD URL provided by the manufacturer for the terminal device); in this case, the first set of mapping relationships is used in S104, and the second set of mapping relationships is used in S1051. Alternatively, in another case, the mapping relationship can also be a set, specifically a mapping relationship between at least one acquisition strategy, a MUD file processing strategy and the device information of the terminal device (or the acquisition strategy, the MUD file processing strategy and the MUD URL provided by the manufacturer for the terminal device). In this case, S104 utilizes the correspondence between the acquisition strategy and the device information of the terminal device (or the acquisition strategy and the MUD URL provided by the manufacturer for the terminal device) in the mapping relationship, and S1051 utilizes the correspondence between the MUD file processing strategy and the device information of the terminal device (or the MUD file processing strategy and the MUD URL provided by the manufacturer for the terminal device) in the mapping relationship.
[0149] It can be seen that through the method 200 provided in the embodiment of the present application, for the scenario where multiple MUD files are distributed on different MUD file servers, when the terminal device 11 accesses the network, the MUD control management device 30 obtains at least one MUD file from multiple MUD file servers according to the target acquisition strategy X corresponding to the terminal device 11, so that the method 200 supports obtaining MUD files from multiple MUD file servers; and, in order to more accurately constrain the terminal device 11 based on the at least one MUD file obtained, and to avoid conflicts in the constraints on the network behavior of the terminal device 11 caused by different MUD information of the same device description items in the multiple MUD files obtained, the MUD control management device 30 can also process the at least one MUD file obtained and determine the target MUD file, so that the method 200 can achieve accurate constraints on the network behavior of the terminal device 11 based on the processed target MUD file.
[0150] It should be noted that the method 200 provided in the embodiment of the present application can also flexibly adjust the target MUD file processing strategy on the MUD control management device according to changes in demand. By flexibly defining different target MUD file processing strategies on the MUD control management device according to actual needs, the method 200 provides a scenario where multiple MUD files are distributed on multiple MUD file servers, and the obtained MUD files are flexibly processed according to different needs, thereby achieving flexible and accurate constraints on the network behavior of the terminal device based on the processed target MUD files.
[0151] Figure 5 A flowchart of a method 300 for obtaining a manufacturer's user manual MUD in an embodiment of the present application is shown. The method 300 is implemented by a MUD control management device. The method 300 for obtaining a MUD may include, for example:
[0152] S301, receiving a MUD URL request message sent by a terminal device;
[0153] S302: Obtain at least one MUD file from a plurality of MUD file servers according to a target acquisition strategy corresponding to the terminal device.
[0154] The MUD control management device in the method 300 may specifically be the MUD control management device 30 in the above embodiment. The operations performed by the MUD control management device may specifically refer to the operations performed by the MUD control management device 30 in the method 100. Specifically, the description of S301 to S302 may refer to S102 to S103 in the method 100. The terminal device may refer to the terminal device 11, the MUD URL request message may be the MUD URL request message 1 in the method 100, the target acquisition strategy may refer to the target acquisition strategy X, the multiple MUD file servers may include the MUD file server 40, the MUD file server 50 and the MUD file server 60, and the at least one MUD file may include at least one of the MUD file 1, the MUD file 2 and the MUD file 3.
[0155] As an example, the MUD control management device may store a first mapping relationship between the MUD URL provided to the terminal device by the manufacturer of the terminal device and the target acquisition strategy. Then, the method 300 may also include: the MUD control management device obtains the MUD URL provided to the terminal device by the manufacturer of the terminal device from the MUD URL request message, determines that the MUD URL matches the first mapping relationship, and thereby obtains the target acquisition strategy according to the first mapping relationship.
[0156] As another example, the MUD control management device may also save the second mapping relationship between the device information of the terminal device and the target acquisition strategy. Then, the method 300 may also include: the MUD control management device obtains the device information of the terminal device from the MUD URL request message, determines that the device information matches the second mapping relationship, and thereby obtains the target acquisition strategy according to the second mapping relationship. The device information of the terminal device may include, for example, one or more of the following: the device identification of the terminal device, the device type of the terminal device, the network segment to which the terminal device belongs, the Internet Protocol IP address of the terminal device, the Media Access Control MAC address of the terminal device, and the manufacturer information of the terminal device.
[0157] In some possible implementations, there is only one acquisition strategy on the MUD control management device. Then, when the MUD control management device receives a MUD URL request message sent by any terminal device, it uses the unique acquisition strategy as the target acquisition strategy and acquires at least one MUD file from multiple MUD file servers based on the target acquisition strategy.
[0158] In some other possible implementations, there are multiple acquisition strategies on the MUD control management device, then the method 300 may also include: the MUD control management device determines the target acquisition strategy from multiple pre-configured acquisition strategies. The multiple acquisition strategies may be configured and saved locally on the MUD control management device, or may be acquired by the MUD control management device from other devices.
[0159] Wherein, the acquisition strategy (including the target acquisition strategy) is used to indicate the rules for obtaining MUD files from multiple MUD file servers. In one case, the target acquisition strategy may include, for example: according to the MUD URL provided to the terminal device by the manufacturer of the terminal device, redirecting the first MUD file server corresponding to the MUD URL to at least one target MUD file server, and obtaining the MUD files in the at least one target MUD file server, wherein the multiple MUD file servers include the first MUD file server, and the at least one target MUD file server includes the second MUD file server. Or, in another case, the target acquisition strategy may also include, for example: according to the principle of sequential reading, the MUD files that have been obtained are updated as a whole with the MUD files obtained from the most recently read MUD file server. Or, in another case, the target acquisition strategy may also include, for example: sequentially reading and saving multiple MUD files in multiple MUD file servers. Or, in another case, the target acquisition strategy may also include, for example: pre-specifying at least one target MUD file server from the multiple MUD file servers, and obtaining the MUD files in the at least one target MUD file server.
[0160] As an example, in S302, obtaining at least one MUD file from multiple MUD file servers according to the target acquisition strategy corresponding to the terminal device may specifically include: determining at least one target MUD file server from the multiple MUD file servers according to the target acquisition strategy; obtaining the at least one MUD file from the at least one target MUD file server. It should be noted that the above-mentioned target MUD file server is one of the multiple MUD file servers. The above-mentioned at least one target MUD file server may be all the MUD file servers included in the multiple MUD file servers; or, the above-mentioned at least one target MUD file server may also be some of the MUD file servers among the multiple MUD file servers.
[0161] The target acquisition strategy may also include, for example: redirecting the first MUD file server corresponding to the MUD URL to at least one target MUD URL according to the MUD URL provided to the terminal device by the manufacturer of the terminal device, and acquiring the at least one MUD file from multiple MUD file servers based on the at least one target MUD URL. The number of the at least one target MUD URL is less than or equal to the number of all MUD file servers included in the multiple MUD file servers. Then, in S302, acquiring at least one MUD file from multiple MUD file servers according to the target acquisition strategy corresponding to the terminal device may specifically include: determining at least one target MUD URL from multiple MUD URLs corresponding to the multiple MUD file servers according to the target acquisition strategy; and acquiring the at least one MUD file from the at least one target MUD URL. It should be noted that the target MUD URL is one of the multiple MUD URLs corresponding to the multiple MUD files storing the terminal device in the multiple MUD file servers. The at least one target MUD URL may be all the MUD URLs included in the multiple MUD URLs; or, the at least one target MUD URL may also be a part of the multiple MUD URLs.
[0162] In some specific implementations, after the MUD control management device executes S302 to obtain at least one MUD file, the method 300 may also include: the MUD control management device processes the at least one MUD file to obtain a target MUD file, and the target MUD file is used to constrain the network behavior of the terminal device. In one case, when the at least one MUD file includes only one MUD file, the only obtained MUD file can be directly used as the target MUD file, and the network behavior of the terminal device is constrained by the target MUD file. In another case, if the at least one MUD file includes at least two MUD files, it is necessary to process the at least two MUD files to obtain the target MUD file, and the network behavior of the terminal device is constrained by the target MUD file.
[0163] It should be noted that the relevant description of this implementation and the effects achieved can all be found in the above Figure 4 The relevant description of S105 in the method 200 is shown.
[0164] As an example, the process of processing at least one MUD file to obtain a target MUD file may include, for example, a process of determining the device description items included in the target MUD file. In one case, all device description items included in the acquired MUD file may be used as device description items in the target MUD file. Assuming that at least one MUD file includes a first MUD file and a second MUD file, the first MUD file includes a first device description item of the terminal device, the second MUD file includes a second device description item of the terminal device, and the first device description item and the second device description item are different, then the target MUD file includes the first device description item and the second device description item. In another case, the device description items included in each MUD file in the acquired MUD file may also be used as device description items in the target MUD file. Assuming that at least one MUD file includes a first MUD file and a second MUD file, the first MUD file includes a first device description item and a second device description item of the terminal device, the second MUD file includes a second device description item of the terminal device, and the first device description item and the second device description item are different, then the target MUD file includes the second device description item.
[0165] In addition, when the same device description item is included in multiple MUD files of the at least one MUD file obtained, but the MUD information of the same device description item is different, then the process of processing the at least one MUD file to obtain the target MUD file may include, for example, a process of determining the MUD information of the device description item in the target MUD file. As an example, the method 300 may also include: based on the target MUD file processing strategy corresponding to the terminal device, obtaining the MUD information used to describe the first device description item in the target MUD file. The first device description item is the same device description item included in multiple MUD files of the at least one MUD file obtained.
[0166] Wherein, the target MUD file processing strategy indicates the rule for processing the at least one obtained MUD file to obtain the target MUD file. In one case, the target MUD file processing strategy may include, for example: when the multiple MUD files are obtained in sequence, the MUD information used to describe the first device description item in the most recently obtained MUD file is used as the MUD information used to describe the first device description item in the target MUD file. Or, in another case, the target MUD file processing strategy may also include, for example: when the MUD information used to describe the first device description item exists in multiple MUD files, the MUD information used to describe the first device description item in a specified MUD file (for example: the MUD file provided by the manufacturer of the terminal device) is used as the MUD information used to describe the first device description item in the target MUD file. Or, in another case, the target MUD file processing strategy may also include, for example: when the MUD information used to describe the first device description item exists in multiple MUD files, the MUD information of the first device description item is processed using a specified operation, and the operation result is used as the MUD information of the first device description item in the target MUD file. Alternatively, in another case, the target MUD file processing strategy may also include, for example: when multiple MUD files respectively include a first MUD information and a second MUD information for describing the first device description item, obtaining the first MUD information and the second MUD information, and in the target MUD file, associating the first MUD information with a first service, and associating the second MUD information with a second service.
[0167] It can be seen that through the method 300 provided in the embodiment of the present application, for the scenario where multiple MUD files are distributed on different MUD file servers, when the terminal device accesses the network, the MUD control management device obtains at least one MUD file from multiple MUD file servers according to the target acquisition strategy corresponding to the terminal device, so that the method 300 supports obtaining MUD files from multiple MUD file servers; moreover, in order to more accurately constrain the terminal device based on the at least one MUD file obtained and avoid conflicts in the constraints on the network behavior of the terminal device due to different MUD information of the same device description items in the multiple MUD files obtained, the MUD control management device can also process the at least one MUD file obtained and determine the target MUD file, so that the method 300 can achieve accurate constraints on the network behavior of the terminal device based on the processed target MUD file.
[0168] It should be noted that the specific implementation method and effect of the method 300 in the embodiment of the present application can be referred to above. Figure 3 and Figure 4 Related descriptions in the illustrated embodiments.
[0169] In addition, the present application also provides a MUD control management device 600, see Figure 6 As shown. The MUD control and management device 600 includes a transceiver unit 601 and a processing unit 602. The transceiver unit 601 is used to execute the transceiver operation implemented by the MUD control and management device 30 in the above method 100 or method 200, or the transceiver unit 601 is also used to execute the transceiver operation implemented by the MUD control and management device in the above method 300; the processing unit 602 is used to execute other operations except the transceiver operation implemented by the MUD control and management device 30 in the above method 100 or method 200, or the processing unit 602 is also used to execute other operations except the transceiver operation implemented by the MUD control and management device in the above method 300. For example: when the MUD control and management device 600 executes the method implemented by the MUD control and management device 30 in the method 100, the transceiver unit 601 can be used to receive the MUD URL request message 1 sent by the terminal device 11; the processing unit 602 can be used to obtain at least one MUD file from multiple MUD file servers based on the target acquisition strategy X corresponding to the terminal device 11.
[0170] In addition, the present application embodiment also provides a manufacturer's instruction manual for MUD control management device 700, see Figure 7 The MUD control management device 700 includes a communication interface 701 and a processor 702. The communication interface 701 includes a first communication interface 701a and a second communication interface 701b. The first communication interface 701a is used to perform the receiving operation performed by the MUD control management device 30 in the embodiment shown in the aforementioned method 100 or method 200, or the first communication interface 701a is also used to perform the receiving operation performed by the MUD control management device in the embodiment shown in the aforementioned method 300; the second communication interface 701b is used to perform the sending operation performed by the MUD control management device 30 in the embodiment shown in the aforementioned method 100 or method 200, or the second communication interface 701b is also used to perform the sending operation performed by the MUD control management device in the embodiment shown in the aforementioned method 300; the processor 702 is used to perform other operations except the receiving operation and the sending operation performed by the MUD control management device 30 in the embodiment shown in the aforementioned method 100 or method 200, or the processor 702 is also used to perform other operations except the receiving operation and the sending operation performed by the MUD control management device in the embodiment shown in the aforementioned method 300. For example: the processor 702 can perform the operation in the embodiment of the method 100: based on the target acquisition strategy X corresponding to the terminal device 11, at least one MUD file is obtained from multiple MUD file servers.
[0171] In addition, the present application embodiment also provides a manufacturer's instruction manual for MUD control management device 800, see Figure 8 As shown. The MUD control management device 800 includes a memory 801 and a processor 802 communicating with the memory 801. The memory 801 includes computer-readable instructions; the processor 802 is used to execute the computer-readable instructions, so that the MUD control management device 800 executes the method executed by the MUD control management device 30 side in the above method 100 or method 200, or the MUD control management device 800 executes the method executed by the MUD control management device side in the above method 300.
[0172] It is understandable that in the above embodiments, the processor may be a central processing unit (CPU), a network processor (NP) or a combination of a CPU and a NP. The processor may also be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The above PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof. The processor may refer to one processor or may include multiple processors. The memory may include a volatile memory (English: volatile memory), such as a random access memory (English: random-access memory, abbreviated: RAM); the memory may also include a non-volatile memory (English: non-volatile memory), such as a read-only memory (English: read-only memory, abbreviated: ROM), a flash memory (English: flash memory), a hard disk drive (English: hard disk drive, abbreviated: HDD) or a solid-state drive (English: solid-state drive, abbreviated: SSD); the memory may also include a combination of the above-mentioned types of memory. The memory may refer to one memory or may include multiple memories. In a specific embodiment, the memory stores computer-readable instructions, and the computer-readable instructions include multiple software modules, such as a sending module, a processing module and a receiving module. After executing each software module, the processor may perform corresponding operations according to the instructions of each software module. In this embodiment, the operation performed by a software module actually refers to the operation performed by the processor according to the instructions of the software module. After the processor executes the computer-readable instructions in the memory, it may perform all operations that can be performed by the device for obtaining the MUD file according to the instructions of the computer-readable instructions.
[0173] It can be understood that in the above embodiment, the communication interface 701 of the MUD control management device 700 can be specifically used as the transceiver unit 601 in the MUD control management device 600 to realize data communication between the MUD control management device and other devices (such as terminal devices).
[0174] In addition, the present application embodiment also provides a communication system 900, see Fig. 9 As shown. The communication system 900 includes a MUD control management device 901, a terminal device 902, and a plurality of MUD file servers 903, wherein the MUD control management device 901 may specifically be the above-mentioned MUD control management device 600, MUD control management device 700, or MUD control management device 800. The plurality of MUD file servers 903 may include: MUD file server 9031, MUD file server 9032, ..., MUD file server 903M (where M is an integer greater than or equal to 2). As an example, the MUD control management device 901 may also be Figure 2 The MUD control management device 30 in the communication system 200 shown in FIG. 2 and the terminal device 902 may be Figure 2 In any one of the terminal devices 11, 12, ..., 1N in the communication system 200, the value of M in the multiple MUD file servers 903 is 3, that is, the multiple MUD file servers 903 include MUD file servers 9031, MUD file servers 9032 and MUD file servers 9033, corresponding to Figure 2 The communication system 200 includes MUD file server 40, MUD file server 50 and MUD file server 60.
[0175] In addition, the present application embodiment also provides a communication system 1000, see Fig.10 The communication system 1000 includes a MUD control management device 1001, a terminal device 1002, and a plurality of MUD file servers 1003, wherein the plurality of MUD file servers 1003 include a first MUD file server 10031, the first MUD file server 10031 is used to store a first MUD file; the plurality of MUD file servers 1003 include a second MUD file server 10032, the second MUD file server 10032 is used to store a second MUD file.
[0176] As an example, the multiple MUD file servers 1003 further include a third MUD file server 10033, and the third MUD file server 10033 is used to store a third MUD file.
[0177] In the communication system 1000, the terminal device 1002 is used to send a MUD uniform resource locator URL request message to the MUD control management device 1001; the MUD control management device 1001 is used to obtain at least one MUD file from multiple MUD file servers 1003 according to a target acquisition strategy corresponding to the terminal device 1002. For example, the at least one MUD file may include at least one of the following MUD files: a first MUD file, a second MUD file, and a third MUD file.
[0178] In some possible implementations, the MUD control management device 1001 stores a first mapping relationship between the MUD URL provided by the manufacturer of the terminal device to the terminal device 1002 and the target acquisition strategy. Then, the MUD control management device 1001 is further used to obtain the target acquisition strategy according to the first mapping relationship.
[0179] In some other possible implementations, the MUD control management device 1001 stores a second mapping relationship between the device information of the terminal device 1002 and the target acquisition strategy. Then, the MUD control management device 1001 is also used to obtain the target acquisition strategy according to the second mapping relationship. The device information of the terminal device 1002 includes one or more of the following: the device identification of the terminal device; the device type of the terminal device; the network segment to which the terminal device belongs; the Internet Protocol IP address of the terminal device; the Media Access Control MAC address of the terminal device; and the manufacturer information of the terminal device.
[0180] In some other possible implementations, the MUD control management device 1001 is further configured to determine the target acquisition strategy from a plurality of pre-configured acquisition strategies. The plurality of acquisition strategies may be locally configured and saved in the MUD control management device 1001, or may be acquired and saved by the MUD control management device 1001 from other devices.
[0181] In some other possible implementations, the MUD control management device 1001 is used to obtain at least one MUD file from multiple MUD file servers 1003 according to a target acquisition strategy corresponding to the terminal device 1002, which may specifically include: the MUD control management device 1001 determines at least one target MUD file server from the multiple MUD file servers according to the target acquisition strategy; the MUD control management device 1001 obtains the at least one MUD file from the at least one target MUD file server.
[0182] Among them, the target acquisition strategy includes: according to the MUD URL provided to the terminal device 1002 by the manufacturer of the terminal device 1002, redirecting the first MUD file server 10031 corresponding to the MUD URL to the at least one target MUD file server, and obtaining the MUD files in the at least one target MUD file server, the multiple MUD file servers include the first MUD file server 10031, and the at least one target MUD file server includes the second MUD file server 10032; or, according to the principle of sequential reading, updating the already obtained MUD files as a whole with the MUD files obtained from the most recently read MUD file server; or, reading and saving multiple MUD files in multiple MUD file servers 1003 in sequence; or, pre-specifying at least one target MUD file server from the multiple MUD file servers 1003, and obtaining the MUD files in the at least one target MUD file server.
[0183] It should be noted that the at least one target MUD file server may be all the MUD file servers included in the multiple MUD file servers 1003, or the at least one target MUD file server may also be some of the MUD file servers in the multiple MUD file servers 1003.
[0184] In some possible implementations, the MUD control management device 1001 is further used to process the at least one MUD file to obtain a target MUD file, and the target MUD file is used to constrain the network behavior of the terminal device 1002 .
[0185] As an example, the at least one MUD file includes a first MUD file and a second MUD file, the first MUD file includes a first device description item of the terminal device, the second MUD file includes a second device description item of the terminal device, the first device description item and the second device description item are different, and the target MUD file includes the first device description item and the second device description item.
[0186] In a possible implementation, the MUD control management device 1001 is also used to obtain the MUD information used to describe the first device description item in the target MUD file based on the target MUD file processing strategy corresponding to the terminal device 1002. The target MUD file processing strategy includes: when the multiple MUD files are obtained in sequence, the MUD information used to describe the first device description item in the most recently obtained MUD file is used as the MUD information used to describe the first device description item in the target MUD file; or, when the MUD information used to describe the first device description item exists in multiple MUD files, the MUD information used to describe the first device description item in the MUD file provided by the manufacturer of the terminal device 1002 is used as the MUD information used to describe the first device description item in the target MUD file; or, when multiple MUD files respectively include the first MUD information and the second MUD information used to describe the first device description item, the first MUD information and the second MUD information are obtained, and in the target MUD file, the first MUD information is associated with the first service, and the second MUD information is associated with the second service.
[0187] It can be seen that, through the communication system 1000 provided by the embodiment of the present application, for the scenario where multiple MUD files are distributed on multiple MUD file servers 1003, when the terminal device 1002 accesses the network, the MUD control management device 1001 can obtain at least one MUD file from multiple MUD file servers 1003 according to the target acquisition strategy corresponding to the terminal device 1002, and supports obtaining MUD files from multiple MUD file servers 1003. In addition, in order to more accurately constrain the terminal device 1002 based on the at least one MUD file obtained, and avoid conflicts in the constraints on the network behavior of the terminal device due to different MUD information of the same device description item in the multiple MUD files obtained, the MUD control management device 1001 can also process the at least one MUD file obtained, determine the target MUD file, and thereby accurately constrain the network behavior of the terminal device 1002 based on the processed target MUD file.
[0188] It should be noted that the functions implemented by the terminal device 1002, the MUD control management device 1001 and the multiple MUD file servers 1003 in the communication system 1000 in the embodiment of the present application can correspond to the above-mentioned Fig. 9 The communication system 900 shown in FIG. 9 includes a MUD control management device 901, a terminal device 902, and multiple MUD file servers 903. For a detailed description of the implementation and the effects achieved, refer to the above Figure 3 and Figure 4 Related descriptions in the illustrated embodiments.
[0189] In addition, an embodiment of the present application also provides a computer-readable storage medium, which stores instructions. When the computer-readable storage medium is run on a computer, the computer executes the method for obtaining MUD files in the embodiments shown in the above method 100, method 200 or method 300.
[0190] In addition, an embodiment of the present application also provides a computer program product, including a computer program or computer-readable instructions. When the computer program or the computer-readable instructions are run on a computer, the computer executes the method of obtaining MUD files in the embodiments shown in the aforementioned method 100, method 200 or method 300.
[0191] Through the description of the above implementation methods, it can be known that those skilled in the art can clearly understand that all or part of the steps in the above-mentioned embodiment method can be implemented by means of software plus a general hardware platform. Based on such an understanding, the technical solution of the present application can be embodied in the form of a software product, which can be stored in a storage medium, such as a read-only memory (ROM) / RAM, a magnetic disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network communication device such as a router) to execute the methods described in each embodiment of the present application or some parts of the embodiments.
[0192] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments. The device and system embodiments described above are merely schematic, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without creative work.
[0193] The above is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. It should be noted that, for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the present application, and these improvements and modifications should also be regarded as the protection scope of the present application.
Claims
1. A method for obtaining a manufacturer's instruction MUD file, characterized in that: Implemented by a MUD control management device, the method includes: Receiving a MUD uniform resource locator URL request message sent by a terminal device; Obtaining at least one MUD file from a plurality of MUD file servers according to a target acquisition strategy corresponding to the terminal device; Wherein, the target acquisition strategy includes: redirecting, according to a MUD URL provided to the terminal device by the manufacturer of the terminal device, a first MUD file server corresponding to the MUD URL to at least one target MUD file server, and obtaining a MUD file in the at least one target MUD file server, wherein the multiple MUD file servers include the first MUD file server, and the at least one target MUD file server includes a second MUD file server; or According to the principle of sequential reading, the MUD file that has been obtained is completely updated with the MUD file obtained from the most recently read MUD file server; or Read and save multiple MUD files from multiple MUD file servers in sequence; or At least one target MUD file server is pre-specified from the multiple MUD file servers, and the MUD files in the at least one target MUD file server are obtained.
2. The method according to claim 1, characterized in that The MUD control management device stores a first mapping relationship between the MUD URL provided to the terminal device by the manufacturer of the terminal device and the target acquisition strategy.
3. The method according to claim 2, characterized in that The method further comprises: The target acquisition strategy is obtained according to the first mapping relationship.
4. The method according to claim 1, characterized in that: The MUD control management device stores a second mapping relationship between the device information of the terminal device and the target acquisition strategy.
5. The method according to claim 4, characterized in that The method further comprises: The target acquisition strategy is obtained according to the second mapping relationship.
6. The method according to claim 4, characterized in that The device information of the terminal device includes one or more of the following: The device identification of the terminal device; The device type of the terminal device; The network segment to which the terminal device belongs; The Internet Protocol IP address of the terminal device; The media access control MAC address of the terminal device; Manufacturer information of the terminal device.
7. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: The target acquisition strategy is determined from a plurality of pre-configured acquisition strategies.
8. The method according to any one of claims 1 to 6, characterized in that: The step of obtaining at least one MUD file from a plurality of MUD file servers according to a target acquisition strategy corresponding to the terminal device comprises: Determining the at least one target MUD file server from the plurality of MUD file servers according to the target acquisition strategy; The at least one MUD file is obtained from the at least one target MUD file server.
9. The method according to claim 8, characterized in that The at least one target MUD file server is all the MUD file servers included in the multiple MUD file servers.
10. The method according to claim 8, characterized in that The at least one target MUD file server is some of the multiple MUD file servers.
11. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: The at least one MUD file is processed to obtain a target MUD file, where the target MUD file is used to constrain the network behavior of the terminal device.
12. The method according to claim 11, characterized in that The at least one MUD file includes a first MUD file and a second MUD file, the first MUD file includes a first device description item of the terminal device, the second MUD file includes a second device description item of the terminal device, the first device description item and the second device description item are different, and the target MUD file includes the first device description item and the second device description item.
13. The method according to claim 11, characterized in that The method further comprises: Based on the target MUD file processing strategy corresponding to the terminal device, the MUD information used to describe the first device description item in the target MUD file is obtained.
14. The method according to claim 13, characterized in that The target MUD file processing strategy includes: When the multiple MUD files are acquired in sequence, the MUD information used to describe the first device description item in the most recently acquired MUD file is used as the MUD information used to describe the first device description item in the target MUD file; or When MUD information for describing the first device description item exists in multiple MUD files, the MUD information for describing the first device description item in the MUD file provided by the manufacturer of the terminal device is used as the MUD information for describing the first device description item in the target MUD file; or When multiple MUD files respectively include first MUD information and second MUD information for describing the first device description item, the first MUD information and the second MUD information are obtained, and in the target MUD file, the first MUD information is associated with a first service, and the second MUD information is associated with a second service.
15. A manufacturer's instruction for use of a MUD control management device, characterized in that: include: a memory including computer-readable instructions; A processor in communication with the memory, the processor being configured to execute the computer-readable instructions so that the MUD control management device is configured to execute the method of any one of claims 1-14.
16. A communication system, characterized in that: The communication system includes the manufacturer's instructions for use MUD control management device as described in claim 15, multiple MUD file servers and terminal devices.
17. The communication system according to claim 16, characterized in that: The multiple MUD file servers include a first MUD file server and a second MUD file server, The first MUD file server is used to store the first MUD file; The second MUD file server is used to store the second MUD file.
18. The communication system according to claim 17, characterized in that: The plurality of MUD file servers further comprises a third MUD file server, The third MUD file server is used to store the third MUD file.
19. The communication system according to any one of claims 16 to 18, characterized in that: The terminal device is used to send a MUD uniform resource locator URL request message to the MUD control management device; The MUD control management device is used to obtain at least one MUD file from a plurality of MUD file servers according to a target acquisition strategy corresponding to the terminal device; Wherein, the target acquisition strategy includes: redirecting, according to a MUD URL provided to the terminal device by the manufacturer of the terminal device, a first MUD file server corresponding to the MUD URL to at least one target MUD file server, and obtaining a MUD file in the at least one target MUD file server, wherein the multiple MUD file servers include the first MUD file server, and the at least one target MUD file server includes a second MUD file server; or According to the principle of sequential reading, the MUD file that has been obtained is completely updated with the MUD file obtained from the most recently read MUD file server; or Read and save multiple MUD files from multiple MUD file servers in sequence; or At least one target MUD file server is pre-specified from the multiple MUD file servers, and the MUD files in the at least one target MUD file server are obtained.
20. The communication system according to claim 19, characterized in that The MUD control management device stores a first mapping relationship between the MUD URL provided to the terminal device by the manufacturer of the terminal device and the target acquisition strategy.
21. The communication system according to claim 20, characterized in that The MUD control management device is further used to obtain the target acquisition strategy according to the first mapping relationship.
22. The communication system according to claim 19, characterized in that The MUD control management device stores a second mapping relationship between the device information of the terminal device and the target acquisition strategy.
23. The communication system according to claim 22, characterized in that The MUD control management device is further used to obtain the target acquisition strategy according to the second mapping relationship.
24. The communication system according to claim 22, characterized in that The device information of the terminal device includes one or more of the following: The device identification of the terminal device; The device type of the terminal device; The network segment to which the terminal device belongs; The Internet Protocol IP address of the terminal device; The media access control MAC address of the terminal device; Manufacturer information of the terminal device.
25. The communication system according to any one of claims 20 to 24, characterized in that: The MUD control management device is also used to determine the target acquisition strategy from a plurality of pre-configured acquisition strategies.
26. The communication system according to any one of claims 20 to 24, characterized in that: The MUD control management device is specifically used for: Determining the at least one target MUD file server from the plurality of MUD file servers according to the target acquisition strategy; The at least one MUD file is obtained from the at least one target MUD file server.
27. The communication system according to claim 26, characterized in that The at least one target MUD file server is all the MUD file servers included in the multiple MUD file servers.
28. The communication system according to claim 26, characterized in that The at least one target MUD file server is some of the multiple MUD file servers.
29. The communication system according to any one of claims 20 to 24, characterized in that: The MUD control management device is also used to process the at least one MUD file to obtain a target MUD file, and the target MUD file is used to constrain the network behavior of the terminal device.
30. The communication system according to claim 29, characterized in that The at least one MUD file includes a first MUD file and a second MUD file, the first MUD file includes a first device description item of the terminal device, the second MUD file includes a second device description item of the terminal device, the first device description item and the second device description item are different, and the target MUD file includes the first device description item and the second device description item.
31. The communication system according to claim 29, characterized in that The MUD control management device is also used to obtain the MUD information used to describe the first device description item in the target MUD file based on the target MUD file processing strategy corresponding to the terminal device.
32. The communication system according to claim 31, characterized in that The target MUD file processing strategy includes: When the multiple MUD files are acquired in sequence, the MUD information used to describe the first device description item in the most recently acquired MUD file is used as the MUD information used to describe the first device description item in the target MUD file; or When MUD information for describing the first device description item exists in multiple MUD files, the MUD information for describing the first device description item in the MUD file provided by the manufacturer of the terminal device is used as the MUD information for describing the first device description item in the target MUD file; or When multiple MUD files respectively include first MUD information and second MUD information for describing the first device description item, the first MUD information and the second MUD information are obtained, and in the target MUD file, the first MUD information is associated with a first service, and the second MUD information is associated with a second service.
33. A computer-readable storage medium comprising computer-readable instructions, characterized in that: When the computer-readable instructions are executed on a computer, the computer is caused to implement the method according to any one of claims 1 to 14.
