Communication method and device

Abstract

The present application relates to the field of communication technology. A communication method and apparatus are provided for enabling a new IO device to join a wireless networking architecture. First, a first virtual port device receives first information from a virtual switch, the first information being used to indicate a device identifier and a port identifier, the device identifier being the identifier of the virtual switch, and the port identifier including the identifier of at least one virtual port device. Then, the first virtual port device sends a link layer discovery protocol LLDP message to a first industrial device, the LLDP message including a first link layer discovery protocol packet data unit LLDP PDU, the device identifier in the first LLDP PDU being the identifier of the virtual switch, the port identifier in the first LLDP PDU including the identifier of at least one virtual port device, and the first LLDP PDU being used to determine an alias for the first industrial device. An alias is configured for the first industrial device, thereby enabling the new IO device to join the wireless networking architecture.

Description

Technical Field

[0001] The embodiments of the present application relate to fields such as communications, and in particular to a communication method and apparatus. Background Art

[0002] Industrial automation and control systems (IACS) are composed of numerous electronic and controller components and are widely used in various industries, including the chemical industry, papermaking, power plants, oil and gas refining, and telecommunications. Controllers take up a lot of space, and circuit flow is difficult to modify and maintain. The advent of programmable logic controllers (PLCs) has solved these problems.

[0003] After the widespread introduction of PLCs into automated control systems, a master PLC and input / output (IO) devices are connected via a switch. North of the switch are other nodes that can be managed. Communication between these nodes occurs via wired connections, such as copper wire, twisted pair cables, or optical fiber.

[0004] With the further development of communication technology, wireless communication is gradually becoming a new medium for connecting industrial field networks. This allows wireless access to existing PLCs, I / O devices, and other equipment, enabling more flexible and convenient networking for industrial equipment. For example, it supports new industrial terminal devices such as automated guided vehicles (AGVs), which require both mobility and flexible networking.

[0005] In wireless networking, when an IO device is damaged, how to add a new IO device to the wireless networking architecture is a technical problem that needs to be solved. Summary of the Invention

[0006] The embodiments of the present application provide a communication method and apparatus for enabling new IO devices to join a wireless networking architecture.

[0007] In a first aspect, a communication method is provided, wherein the execution subject of the method may be a first virtual port device, or a component applied to the first virtual port device, such as a chip, a processor, etc. The following description is made by taking the execution subject being the first virtual port device as an example. First, the first virtual port device receives first information from a virtual switch, wherein the first information is used to indicate a first device identifier and a first port identifier, wherein the first device identifier is an identifier of the virtual switch, and the first port identifier includes an identifier of at least one virtual port device. Then, the first virtual port device may send a Link Layer Discovery Protocol (LLDP) message to the first industrial device, wherein the LLDP message includes a first Link Layer Discovery Protocol Packet Data Unit (LLDP PDU), wherein the first device identifier in the first LLDP PDU is an identifier of the virtual switch, and the first port identifier in the first LLDP PDU includes an identifier of at least one virtual port device, and the first LLDP PDU is used to determine an alias of the first industrial device.

[0008] This example is applicable to scenarios where each virtual port device connects to one industrial device, and one industrial device can connect to one or more virtual port devices. The virtual switch indicates the port ID and device ID to the virtual port device, where the port ID is the virtual port device ID and the device ID is the virtual switch ID. The virtual port device determines the LLDP message based on the virtual switch's instructions and sends the LLDP message to the new industrial device, allowing the new industrial device to determine its own alias based on the LLDP PDU in the LLDP message. The new industrial device can determine a unique alias based on the existing LLDP protocol specifications and existing naming rules, thereby enabling the new I / O device to join the wireless networking architecture.

[0009] In a possible implementation, the first information may be a service message; the message body of the service message includes the first LLDP PDU. This approach only requires parsing and transparent transmission for the virtual port device, and is relatively simple to implement.

[0010] In one possible implementation, the first information may further include first indication information, where the first indication information is used to instruct transparent transmission of the first LLDP PDU. In this way, the virtual port device can accurately and promptly transparently transmit the first LLDP PDU in the service message, thereby avoiding confusion with other messages and the situation in which the first LLDP PDU in the service message is not transparently transmitted.

[0011] In one possible implementation, the first virtual port device can generate the first LLDP PDU based on the first device identifier and the first port identifier indicated by the first information. In this manner, after storing the port identifier and the device identifier, the virtual port device can send LLDP packets to the industrial device connected to the virtual port device at any time without triggering the virtual switch. This increases the effectiveness of determining the alias of the new industrial device, and other control devices are unaware of this process.

[0012] In one possible implementation, the first virtual port device may further receive second indication information from the virtual switch, where the second indication information is used to instruct the first virtual port device to generate an LLDP PDU. In this way, the virtual port device can generate the LLDP PDU promptly and accurately, avoiding a situation where the virtual port device confuses the first indication information with other received information and does not know what to do with it.

[0013] In one possible implementation, the first virtual port device may also receive a discovery message from the control device to trigger the generation of the first LLDP PDU. The discovery message is used to instruct the acquisition of the first industrial device information. If the control device does not send a discovery message to the industrial device, typically no industrial device replacement event has occurred. If the virtual port device sends an LLDP message to the industrial device during this period, this process wastes signaling. Therefore, the first virtual port device can trigger the generation of the first LLDP PDU upon receiving a discovery message from the control device. This transmission does not waste signaling.

[0014] In one possible implementation, after the first virtual port device sends the LLDP message to the first industrial device, the first virtual port device may also send the discovery message to the first industrial device, where the discovery message is used to instruct the device to obtain parameter information related to the first industrial device. The first virtual port device may then receive a response message from the first industrial device, where the response message includes the parameter information related to the first industrial device. The first virtual port device may then send the response message to the control device, where the response message includes the parameter information related to the first industrial device. This allows for lossless service replacement.

[0015] In a second aspect, a communication method is provided, wherein the execution subject of the method may be a virtual switch, or a component used in the virtual switch, such as a chip, a processor, etc. The following description is made by taking the execution subject being a virtual switch as an example. First, the virtual switch generates first information, wherein the first information is used to indicate a first device identifier and a first port identifier, and the first device identifier and the first port identifier are used to generate a first link layer discovery protocol packet data unit LLDP PDU, wherein the first device identifier is an identifier of the virtual switch, and the first port identifier includes an identifier of at least one virtual port device; the first LLDP PDU is used to determine an alias of the first industrial device. Then, the virtual switch may send the first information to a first virtual port device, wherein the at least one virtual port device includes the first virtual port device.

[0016] This example is applicable to scenarios where each virtual port device connects to one industrial device, and one industrial device can connect to one or more virtual port devices. The virtual switch indicates the port ID and device ID to the virtual port device, where the port ID is the virtual port device ID and the device ID is the virtual switch ID. The virtual port device determines the LLDP message based on the virtual switch's instructions and sends the LLDP message to the new industrial device, allowing the new industrial device to determine its own alias based on the LLDP PDU in the LLDP message. The new industrial device can determine a unique alias based on the existing LLDP protocol specifications and existing naming rules, thereby enabling the new I / O device to join the wireless networking architecture.

[0017] In a possible implementation, the first information may be a service message; the message body of the service message includes the first LLDP PDU. This approach only requires parsing and transparent transmission for the virtual port device, and is relatively simple to implement.

[0018] In one possible implementation, the first information may further include first indication information, where the first indication information is used to instruct transparent transmission of the first LLDP PDU. In this way, the virtual port device can accurately and promptly transparently transmit the first LLDP PDU in the service message, thereby avoiding confusion with other messages and the situation in which the first LLDP PDU in the service message is not transparently transmitted.

[0019] In one possible implementation, the virtual switch may also send second indication information to the first virtual port device, where the second indication information is used to instruct the first virtual port device to generate an LLDP PDU. In this way, for the virtual port device, after storing the port identifier and device identifier, it can send LLDP messages to the industrial device connected to the virtual port device at any time without triggering the virtual switch. This makes it more effective to determine the alias of the new industrial device, and for other control devices, this process is imperceptible. In addition, the second indication information can enable the virtual port device to generate LLDP PDUs in a timely and accurate manner, so as to avoid the situation where the virtual port device confuses the first indication information with other received information and does not know what to do with it.

[0020] In a third aspect, a communication method is provided, wherein the execution subject of the method can be a first industrial device, or a component used in the first industrial device, such as a chip, a processor, etc. The following description is made by taking the execution subject being the first industrial device as an example. First, the first industrial device can receive an LLDP message from a first virtual port device, wherein the LLDP message includes a first link layer discovery protocol packet data unit LLDP PDU; the first device identifier included in the first LLDP PDU is an identifier of a virtual switch, and the first port identifier included in the first LLDP PDU includes an identifier of at least one virtual port device; the first LLDP PDU is used to determine an alias of the first industrial device. Then, the first industrial device determines the alias of the first industrial device based on the first device identifier and the first port identifier. For example, the alias is the identifier of the virtual switch and the identifier of the at least one virtual port device.

[0021] This example is applicable to scenarios where each virtual port device connects to one industrial device, and one industrial device can connect to one or more virtual port devices. The virtual switch indicates the port ID and device ID to the virtual port device, where the port ID is the virtual port device ID and the device ID is the virtual switch ID. The virtual port device determines the LLDP message based on the virtual switch's instructions and sends the LLDP message to the new industrial device, allowing the new industrial device to determine its own alias based on the LLDP PDU in the LLDP message. The new industrial device can determine a unique alias based on the existing LLDP protocol specifications and existing naming rules, thereby enabling the new I / O device to join the wireless networking architecture.

[0022] In one possible implementation, the first industrial device may receive a discovery message that includes the first industrial device's alias and instructs the user to obtain parameter information related to the first industrial device. The first industrial device may then send a response message that includes the parameter information related to the first industrial device. The first industrial device then receives first parameter information related to the old industrial device it replaces. This parameter information does not include the media access control (MAC) address of the old industrial device, thereby achieving lossless service replacement.

[0023] The first to third aspects are applicable to a scenario where the industrial device and the virtual port device are two devices, and the fourth and fifth aspects are applicable to a scenario where the industrial device and the virtual port device are combined into one device.

[0024] In a fourth aspect, a communication method is provided, wherein the execution subject of the method can be a virtual switch, or a component applied to the virtual switch, such as a chip, a processor, etc. The following description is made by taking the execution subject as an example. First, the virtual switch can generate a service message, the message body of the service message including a first link layer discovery protocol packet data unit LLDP PDU, the first device identifier included in the first LLDP PDU being the identifier of the virtual switch, the first port identifier included in the first LLDP PDU being the permanent equipment identifier (PEI) or the international mobile equipment identity (IMEI) of the first industrial device, and the first LLDP PDU being used to determine the alias of the first industrial device. Then, the virtual switch can send the service message to the first industrial device.

[0025] The virtual switch generates a service message containing an LLDP PDU and sends it to the new industrial device, allowing it to determine its own alias based on the LLDP PDU in the service message. The new industrial device can determine a unique alias based on the existing LLDP protocol specifications and naming rules, using the Permanent Equipment Identity (PEI) or International Mobile Equipment Identity (IMEI) as a port identifier, allowing the new IO device to join the wireless networking architecture.

[0026] In a fifth aspect, a communication method is provided, wherein the execution subject of the method may be a first industrial device, or a component used in the first industrial device, such as a chip, a processor, etc. The following description is made by taking the execution subject being the first industrial device as an example. First, the first industrial device receives a service message from the virtual switch, wherein the service message includes a first link layer discovery protocol packet data unit LLDP PDU, the first device identifier included in the first LLDP PDU is the identifier of the virtual switch, the port identifier included in the first LLDP PDU is the permanent equipment identity code PEI or the international mobile equipment identity code IMEI of the first industrial device, and the first LLDP PDU is used to determine the alias of the first industrial device. Then, the first industrial device determines the alias of the first industrial device based on the first device identifier and the first port identifier. For example, the alias is the international mobile equipment identity code IMEI of the new IO device. The identifier of the virtual switch.

[0027] The virtual switch generates a service message containing an LLDP PDU and sends it to the new industrial device, allowing it to determine its own alias based on the LLDP PDU in the service message. The new industrial device can determine a unique alias based on the existing LLDP protocol specifications and naming rules, using the Permanent Equipment Identity (PEI) or International Mobile Equipment Identity (IMEI) as a port identifier, allowing the new IO device to join the wireless networking architecture.

[0028] In one possible implementation, the first industrial device may also receive a discovery message, which includes the alias of the first industrial device and is used to instruct the user to obtain relevant parameter information about the first industrial device. The first industrial device may then send a response message, which includes the relevant parameter information about the first industrial device. Next, the first industrial device may receive first parameter information, which includes the relevant parameter information about the old industrial device it replaces. This parameter information does not include the media access control (MAC) address of the old industrial device, thereby achieving lossless service replacement.

[0029] In a sixth aspect, a communication device is provided, wherein the device has the functions of implementing any of the above aspects and any possible implementations of any of the above aspects. These functions can be implemented by hardware or by hardware executing corresponding software implementations. The hardware or software includes one or more functional modules corresponding to the above functions.

[0030] In the seventh aspect, a communication device is provided, comprising a processor and, optionally, a memory; the processor and the memory are coupled; the memory is used to store computer programs or instructions; the processor is used to execute part or all of the computer programs or instructions in the memory, and when the part or all of the computer programs or instructions are executed, is used to implement the functions of any of the above aspects and any possible implementation methods of any aspect.

[0031] In one possible implementation, the apparatus may further include a transceiver configured to transmit a signal processed by the processor or receive a signal input to the processor. The transceiver may perform the transmitting action or the receiving action in any aspect and any possible implementation of any aspect.

[0032] In an eighth aspect, the present application provides a chip system comprising one or more processors (also referred to as processing circuits), the processors being electrically coupled to a memory (also referred to as a storage medium); the memory being located in the chip system or not; the memory being used to store computer programs or instructions; the processor being used to execute part or all of the computer programs or instructions in the memory, and when the part or all of the computer programs or instructions are executed, to implement the functions of any of the above aspects and any possible implementation methods of any aspect.

[0033] In one possible implementation, the chip system may further include an input / output interface (also referred to as a communication interface), the input / output interface being configured to output signals processed by the processor or receive signals input to the processor. The input / output interface may perform a sending action or a receiving action in any aspect and any possible implementation of any aspect. Specifically, the output interface performs a sending action, and the input interface performs a receiving action.

[0034] In a possible implementation, the chip system may be composed of a chip, or may include a chip and other discrete devices.

[0035] In a ninth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program includes instructions for implementing the functions of any aspect and any possible implementation of any aspect.

[0036] Alternatively, a computer-readable storage medium is used to store a computer program, which, when executed by a computer, can enable the computer to perform any of the above aspects and any possible implementation method of any aspect.

[0037] In a tenth aspect, a computer program product is provided, comprising: a computer program code, which, when executed on a computer, enables the computer to execute a method in any of the above aspects and any possible implementation of any of the aspects.

[0038] In an eleventh aspect, a communication system is provided, comprising a virtual switch, a first virtual port device, and a first industrial device performing the method of any of the first through third aspects and any possible implementations thereof. Alternatively, the communication system comprises a virtual switch and a first industrial device performing the method of any of the fourth through fifth aspects and any possible implementations thereof.

[0039] In one example, a virtual switch is configured to generate first information, wherein the first information is configured to indicate a first device identifier and a first port identifier, wherein the first device identifier is an identifier of the virtual switch, and the first port identifier includes an identifier of at least one virtual port device;

[0040] A first virtual port device is configured to receive first information from a virtual switch and send an LLDP message to a first industrial device, wherein the LLDP message includes a first LLDP PDU, the first device identifier in the first LLDP PDU is an identifier of the virtual switch, the first port identifier in the first LLDP PDU includes an identifier of at least one virtual port device, and the first LLDP PDU is used to determine an alias of the first industrial device.

[0041] The first industrial device is configured to receive an LLDP message from a first virtual port device and determine an alias of the first industrial device based on the first device identifier and the first port identifier.

[0042] In one example, the first information is a service message; and the message body of the service message includes the first LLDP PDU.

[0043] In one example, the first information further includes first indication information, and the first indication information is used to indicate transparent transmission of the first LLDP PDU.

[0044] In an example, the first virtual port device is further configured to generate the first LLDP PDU based on the first device identifier and the first port identifier indicated by the first information.

[0045] In one example, the virtual switch is further configured to send second indication information to the first virtual port device, where the second indication information is configured to instruct the first virtual port device to generate an LLDP PDU;

[0046] The first virtual port device is further configured to receive second indication information from the virtual switch.

[0047] In one example, the first virtual port device is configured to receive a discovery message from a control device to trigger generation of the first LLDP PDU, where the discovery message is used to instruct acquisition of the first industrial device information.

[0048] In one example, the first virtual port device is further configured to, after sending the LLDP message to the first industrial device, send the discovery message to the first industrial device, where the discovery message is used to instruct the acquisition of relevant parameter information of the first industrial device; and receive a response message from the first industrial device, where the response message includes the relevant parameter information of the first industrial device; and send the response message to the control device, where the response message includes the relevant parameter information of the first industrial device;

[0049] In one example, the first industrial device is also used to receive a discovery message, the discovery message includes an alias of the first industrial device, and the discovery message is used to instruct the acquisition of relevant parameter information of the first industrial device; send a response message, the response message includes relevant parameter information of the first industrial device; and receive first parameter information, the first parameter information is relevant parameter information of the old industrial device replaced by the first industrial device, and the relevant parameter information does not include the media access control address MAC of the old industrial device.

[0050] The technical effects of the above-mentioned sixth to eleventh aspects can refer to the descriptions in the first to fifth aspects, and the repeated parts will not be repeated. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Figure 1a A schematic diagram of an LLDP message format provided in an embodiment of the present application;

[0052] Figure 1b This is a schematic diagram of an LLDPDU format provided in an embodiment of the present application;

[0053] Figure 2a A schematic diagram of the communication system structure provided in an embodiment of the present application;

[0054] Figure 2b A schematic diagram of the communication system structure provided in an embodiment of the present application;

[0055] Figure 2c A schematic diagram of the communication system structure provided in an embodiment of the present application;

[0056] Figure 3a A schematic diagram of a communication system architecture provided in an embodiment of the present application;

[0057] Figure 3b A flow chart of a communication method provided in an embodiment of the present application;

[0058] Figure 4 A flow chart of a communication method provided in an embodiment of the present application;

[0059] Figure 5 A flow chart of a communication method provided in an embodiment of the present application;

[0060] Figure 6 A flow chart of a communication method provided in an embodiment of the present application;

[0061] Figure 7 A flow chart of a communication method provided in an embodiment of the present application;

[0062] Figure 8 A schematic diagram of a communication system architecture provided in an embodiment of the present application;

[0063] Figure 9 A flow chart of a communication method provided in an embodiment of the present application;

[0064] Figure 10 A flow chart of a communication method provided in an embodiment of the present application;

[0065] Figure 11 A schematic diagram of a communication system architecture provided in an embodiment of the present application;

[0066] Figure 12 A flow chart of a communication method provided in an embodiment of the present application;

[0067] Figure 13 A structural diagram of a communication device provided in an embodiment of the present application;

[0068] Figure 14 This is a structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0069] To facilitate understanding of the embodiments of the present application, some terms used in the embodiments of the present application are explained below to facilitate understanding by those skilled in the art.

[0070] 1) Link layer discovery protocol (LLDP):

[0071] LLDP, defined in 802.1ab, is a Layer 2 protocol. LLDP provides a standard link layer discovery method. It organizes information such as the local node's primary capabilities, management address, device identifier, and interface identifier into different type / length / value (TLV) formats. These information is encapsulated in Link Layer Discovery Protocol Packet Data Units (LLDP PDUs, also referred to as LLDPDUs) and distributed to directly connected nodes. Directly connected nodes receive this information and store it in a standard Management Information Base (MIB) for network management systems to query and determine link communication status.

[0072] LLDP is a protocol for notifying and obtaining information. Information sent by LLDP does not typically require confirmation and cannot be used to request information. LLDP is a unidirectional protocol that operates only in the active notification mode. It does not require confirmation and cannot be queried or requested.

[0073] The message encapsulated with LLDPDU is called LLDP message, such as Figure 1a The following figure shows the LLDP message format:

[0074] Destination MAC address: This field represents the destination media access control address (MAC), which is a fixed multicast MAC address (0x0180-C200-000E). The MAC address, also known as the physical address or hardware address, is burned into the network card by the manufacturer during production and cannot be modified.

[0075] Source MAC address: indicates the source MAC address, which can be the port MAC address or the device bridge MAC address. If a port address exists, the port MAC address is used; otherwise, the device bridge MAC address is used.

[0076] Type: indicates the message type, usually 0x88CC.

[0077] Data: data, which is LLDPDU.

[0078] FCS: Frame check sequence (FCS) allows the network card or interface receiving the frame to determine whether an error has occurred.

[0079] LLDPDU is a data unit encapsulated in the data part of the LLDP message. Before forming the LLDPDU, the device first encapsulates the local information into TLV format, and then combines several TLVs into an LLDPDU and encapsulates it in the data part of the LLDP message. Figure 1b The figure below provides a schematic diagram of the LLDPDU format. Currently, each LLDPDU can carry up to 28 TLVs. The Chassis ID TLV, Port ID TLV, Time To Live TTL TLV, and End TLV are mandatory, while the remaining TLVs are optional.

[0080] The Chassis ID TLV indicates the chassis ID of the LLDPDU sender. It is actually used to identify the device and is referred to as the device ID in this application.

[0081] Port ID TLV, used to indicate the port of the device that sends the LLDPDU.

[0082] TTL TLV is used to indicate how long this information is valid.

[0083] End TLV, used to indicate the end of an LLDPDU.

[0084] 2) Discovery and Basic Configuration Protocol (DCP), which operates at the data link layer. In PROFINET, DCP has four main functions: Set, Identify, Hello, and Get. The following sections use Set and Identify as examples to explain each.

[0085] Set request: Configuration primarily involves network parameters and auxiliary functions, including the IP address, subnet mask, gateway, device name, and flash identification. The device name is similar to an Ethernet domain name; whereas a domain name is internationally unique, the device name only needs to be unique within the control network. Domain names are resolved to IP addresses via DNS, while device names are bound to MAC addresses for easier memorization and use within the communication network.

[0086] Set response: After the sender sends a Set request frame, the receiver returns the corresponding data information in the Set response.

[0087] Identify request: It is mainly used to scan PN devices in the network. This frame only needs the source MAC address, and the destination address is generally the broadcast MAC. All devices (including controllers) that receive this frame will respond, and the device information in the network can be known to prepare for subsequent connection establishment.

[0088] Identify response: Scan all devices, and the devices will respond with all data, including IP, device name, manufacturer information, MAC address, device alias, etc.

[0089] 3) PROFINET (PN) IO device replacement mechanism:

[0090] Early PROFINET IO devices required the insertion of a multimedia card (MMC), which stored the device name. If an interface module failed and needed to be replaced, simply inserting the MMC card restored PROFINET IO device communication. A programmer (PG) or personal computer (PC) could then be used to reconfigure the IO device, saving maintenance costs.

[0091] IO devices that support the PROFINET "Device replacement without removable media / PG" function do not require removable media (such as MMC) or a PG to assign a device name during the replacement process. The device name of the new IO device after replacement is assigned by the IO controller (such as PLC) rather than by the removable media or PG. To this end, the IO controller of the new IO device and the adjacent PROFINET devices must support the PROFINET "Device replacement without removable media / PG" function. The "Device replacement without removable media / PG" function is implemented based on the LLDP protocol.

[0092] 4) The user plane function (UPF) network element is responsible for forwarding and receiving user data in the terminal device. User data can be received from the data network and transmitted to the terminal device through the access network device; the user plane network element can also receive user data from the terminal device through the access network device and forward it to the data network. The transmission resources and scheduling functions that provide services to the terminal device in the user plane network element are managed and controlled by the SMF network element. In the 5G communication system, the user plane network element can be a user plane function (UPF) network element. In future communication systems, the user plane network element can still be a UPF network element, or it can have other names, which are not limited in this application. This application can deploy UPF in an industrial park as a user plane server in the industrial park.

[0093] 5) Radio access network (RAN) equipment is a device that provides wireless communication functions for terminal devices. The RAN equipment in this application includes but is not limited to: the next generation base station (g nodeB, gNB) in 5G, evolved node B (eNB), radio network controller (RNC), node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (BBU), transmission point (TRP), transmitting point (TP), mobile switching center, etc. In systems using different wireless access technologies, the names of devices with base station functions may vary. For example, in the fifth generation (5G) system, it is called RAN or gNB (5GNodeB); in the LTE system, it is called evolved NodeB (eNB or eNodeB); in the third generation (3G) system, it is called Node B, etc.

[0094] To facilitate understanding of the technical solutions of the embodiments of the present application, the system architecture of the method provided in the embodiments of the present application is briefly described below. It is understood that the system architecture described in the embodiments of the present application is for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application and does not constitute a limitation on the technical solutions provided in the embodiments of the present application.

[0095] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as satellite communication systems and traditional mobile communication systems. The satellite communication system can be integrated with a traditional mobile communication system (i.e., a terrestrial communication system). Communication systems include, for example, wireless local area network (WLAN) communication systems, wireless fidelity (WiFi) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, fifth generation (5G) systems or new radio (NR), sixth generation (6G) systems, and other future communication systems. It also supports communication systems that integrate multiple wireless technologies. For example, it can also be applied to systems that integrate non-terrestrial networks (NTNs) such as drones, satellite communication systems, and high altitude platform stations (HAPS) communications with terrestrial mobile communication networks.

[0096] To facilitate understanding of the embodiments of the present application, the application scenarios of the present application are introduced below. The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Ordinary technicians in this field can know that with the emergence of new business scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0097] IACS (Integrated Automation Control Systems) are composed of numerous electronic and controller components and are widely used in various industries, including the chemical industry, papermaking, power plants, oil and gas refining, and telecommunications. Controllers take up a lot of space, and circuit flow is difficult to modify and maintain. The advent of programmable logic controllers (PLCs) has solved these problems.

[0098] like Figure 2a The figure shows a networking architecture for an industrial automation system after the widespread introduction of PLCs into automated control systems: a master PLC and other nodes, such as input and output devices, are connected via a switch (SW). A management node (such as a PLC) is located north of the switch. Communication between nodes occurs via wired connections, such as copper wire, twisted pair cables, or optical fiber.

[0099] When an IO device fails or has other reasons, it needs to be replaced. Figure 1a As shown in the figure, the process of replacing an IO2 device with a new IO device is introduced as an example.

[0100] Using the Link Layer Discovery Protocol (LLDP), nodes such as I / O devices and PLCs can exchange information with switches, such as device names and port numbers. Table 1 below shows the information about each device and its directly connected nodes, as described in LLDP.

[0101] Table 1:

[0102]

[0103] As can be seen from Table 1, the port of the local device is connected to the port of the remote device. For the local device, the alias of the remote device is: the port ID of the local device. The local device ID.

[0104] For example, if Port 01 of a Switch is connected to Port 01 of a PLC, then for the PLC, the alias of the Switch is Port01.PLC; for the Switch, the alias of the PLC is Port01.Switch;

[0105] For example, if Port 02 of Switch is connected to Port 01 of IO1, then for IO1, the alias of Switch is Port01.IO1; for Switch, the alias of IO1 is Port02.Switch.

[0106] For example, if Port 03 of Switch is connected to Port 01 of IO2, then for IO2, the alias of Switch is Port01.IO2; for Switch, the alias of IO2 is Port03.Switch.

[0107] When the new IO device replaces the IO2 device and is connected to the SW (the port of the SW to which the new IO device is connected is the port of the SW to which the IO2 device is connected), the new IO device has no device name or alias in the initial settings.

[0108] The Switch (SW) and the new I / O device exchange LLDP messages, sharing their information. For example, if the Switch sends an LLDP message to the new I / O device, with the setup identifier in the LLDPPDU as SW and the port identifier as Port03 (SW), the new I / O device can set its alias to Port03.Switch. The PLC then discovers the alias of the new I / O device through the Discovery and Configuration Protocol (DCP) and sets other parameters for the new I / O device, including its device name and service parameters. The device name of the new I / O device is the same as the device name of the I / O device it replaces, for example, IO2.

[0109] It is understandable that for the new IO, the alias of Switch is Port01.IO2.

[0110] With the continued development of communication technologies, wireless communication technologies, represented by 5G, are gradually becoming the new medium for connecting industrial field networks. Wireless communication technologies can enable wireless access to existing nodes such as PLCs and I / O devices, enabling more flexible networking for industrial equipment.

[0111] like Figure 2b The figure shows a possible networking structure for an industrial automation system after the introduction of a wireless communication system. A wireless communication network (e.g., a 5G network) is deployed between the switch and the I / O devices. For example, one or more UPF network elements and one or more RAN network elements are deployed between the switch and the I / O devices.

[0112] If the IO device has wireless network access capability, the IO device can be directly connected to the RAN. However, some IO devices do not have wireless network (such as 5G network) access capability. Figure 2c As shown, one or more customer premise equipment (CPE) can be deployed in front of the IO device. CPE is a mobile signal access device that receives mobile signals and forwards them as wireless WIFI signals. It is equivalent to providing an access port for the wireless network for the IO device. A CPE can be connected to one or more IO devices. An IO device can also be connected to one or more CPEs. When an IO device is connected to multiple CPEs, the connection reliability can be improved. The connection between the IO device and the CPE is usually physical. Usually, the CPE has only one physical port, and a CPE can only be physically connected to one IO device. When a CPE is connected to multiple IO devices, a SW can be deployed between the CPE and the IO device. The SW is physically connected to the CPE. One SW can be connected to multiple IO devices, and one IO device is connected to one SW.

[0113] In a wireless access network, multiple network elements are deployed between the switch (SW) and the I / O devices. If these multiple devices still communicate using the Link Layer Discovery Protocol (LLDP), the following situation may occur: For the switch, the UPF's alias is Port01.SW; for the UPF, the SW's alias is Port01.UPF, and the RAN's alias is Port02.UPF, etc. For the RAN, the UPF and CPE's aliases are RAN's port ID.RAN device ID. For the CPE, the RAN and IO device's aliases are CPE's port ID, CPE device ID. When a new IO device replaces the IO2 device and is connected to the switch, the new IO device has no device name or alias in its initial settings. The switch cannot forward LLDP packets across domains, resulting in the switch (SW) being unable to configure an alias for the new IO device based on LLDP.

[0114] One method for configuring an alias for a new IO device is to have a management node (e.g., a PLC) maintain the connection relationship between the CPE and the IO device. The management node can obtain the connection relationship between each device (or node) in a normal network. The CPE sends an LLDP message to the IO device, where the LLDP PDU includes a device identifier that is the CPE identifier and a port identifier that is the identifier of a port on the CPE. The alias of the new IO device is: the port identifier on the CPE. The CPE device identifier. After discovering the alias of the new IO device through the Discovery and Configuration Protocol (DCP), the management node can further set other parameters for the new IO device, such as the device name and service parameters of the new IO device. On the one hand, most CPEs currently do not support actively sending LLDP messages. On the other hand, when a CPE is connected to multiple IO devices, a SW connection is required between the IO device and the CPE. The IO device and the CPE are no longer directly connected, and the CPE cannot forward LLDP messages across domains. Therefore, the CPE can no longer configure an alias for the new IO device based on LLDP.

[0115] Based on this, the present application proposes a variety of technical solutions to implement the configuration of aliases for new IO devices under wireless networking, so as to enable new IO devices to join the wireless networking architecture. The solution of the present application can be applied to a variety of scenarios and has good compatibility.

[0116] In a wireless network, the ports for communication between network elements are usually logical ports, not physical ports. Logical ports cannot be distinguished, and a point can be found as the so-called "physical port". This application uses the virtual port device to which industrial equipment (such as IO devices) is connected as the so-called "physical port". The virtual switch is similar to the switch SW in Table 1; the virtual port device is used as the virtual port of the virtual switch, and the virtual port device is similar to the ports in Table 1: port1, port2, port3. The alias of the industrial equipment can be determined based on the device name of the virtual switch and the device name of the virtual port device.

[0117] The virtual switches in this application include UPFs, mobile edge computing (MEC) nodes, gateways (GW), etc. Virtual port devices include switches, routers, terminals, CPEs, bridges, and other gateway devices that enable industrial equipment to access. Industrial equipment includes IO devices, etc.

[0118] The following is a detailed description of the solution with reference to the accompanying drawings. The features or contents marked with dotted lines in the accompanying drawings can be understood as optional operations or optional structures of the embodiments of the present application.

[0119] The various embodiments involved in this application can be referenced to each other, and the various embodiments can also be combined to form one embodiment. The devices marked with "×" in the embodiments are devices that need to be replaced, for example Figure 3a 、 Figure 3b 、 Figure 8 、 Figure 11 、 Figure 12 The second industrial equipment in the system is replaced by the first industrial equipment.

[0120] Example 1:

[0121] like Figure 3a As shown, a schematic diagram of a communication system is introduced, in which a virtual switch is connected to one or more virtual port devices through RAN, the first virtual port device is any virtual port device in the network, each virtual port device is connected to an industrial device, and an industrial device can be connected to one or more virtual port devices. The first virtual port device is connected to the second industrial device, and the second industrial device is connected to at least one virtual port device, and the at least one virtual port device includes the first virtual port device. If the second industrial device fails or for other reasons, the first industrial device is used to replace the second industrial device. After the replacement, the first industrial device maintains the same connection relationship with the second industrial device, and the alias of the industrial device does not change. The connection relationship involved in this embodiment can be a wireless connection such as a 5G connection and a WiFi connection, or it can be a wired connection such as a copper wire, optical fiber, or a twisted pair.

[0122] like Figure 3b As shown, a flow chart of a communication method is introduced, which can be applied to Figure 3a The communication system shown includes the following steps:

[0123] Step 301: a virtual switch (eg, called VSW) sends first information to a first virtual port device (eg, called VPORT). Correspondingly, the first virtual port device receives the first information from the virtual switch.

[0124] The first information is used to indicate a first device identifier and a first port identifier, and the first device identifier and the first port identifier are used to generate a first Link Layer Discovery Protocol Packet Data Unit (LLDP PDU). The first LLDP PDU is used to determine an alias of the industrial device.

[0125] In this embodiment, the first device identifier is the identifier of the virtual switch, and the first port identifier includes the identifier of at least one virtual port device, which may be the International Mobile Equipment Identity (IMEI) of the virtual port device.

[0126] In the present application, the first LLDP PDU may be generated by the virtual switch, or by the first virtual port device.

[0127] It can be understood that the virtual switch sends the first information to the first virtual port device through the RAN.

[0128] Step 302: The first virtual port device sends an LLDP message to the first industrial device. Correspondingly, the first industrial device receives the LLDP message from the first virtual port device.

[0129] The LLDP message includes the first LLDP PDU. The first device identifier in the first LLDP PDU is the identifier of the virtual switch, the first port identifier in the first LLDP PDU includes the identifier of at least one virtual port device, and the first LLDP PDU is used to determine the alias of the first industrial device.

[0130] In an optional example, a virtual switch generates a first LLDP PDU and sends the first LLDP PDU to a first virtual port device. For example, the first information is a service message; the message body of the service message includes the first LLDP PDU. That is, the virtual switch adds a message header to the generated first LLDP PDU and sends the entire message to the first virtual port device. The first virtual port device can parse the service message to obtain the first LLDP PDU and encapsulate the first LLDP PDU into an LLDP message. This approach is relatively simple for the virtual port device, as it only requires parsing and transparent transmission.

[0131] Optionally, the virtual switch may also send first indication information to the first virtual port device. Accordingly, the first virtual port device receives the first indication information from the virtual switch, and the first indication information is used to instruct transparent transmission of the first LLDP PDU. The first indication information may be carried in the first information, or may be carried in other information different from the first information. In this way, the virtual port device can accurately and timely transparently transmit the first LLDP PDU in the service message to avoid confusion with other messages and the situation where the first LLDP PDU in the service message is not transparently transmitted. Of course, the virtual switch and the first virtual port device may mutually agree, or the protocol may stipulate that the virtual switch generates the first LLDP PDU and the first virtual port device transparently transmits the first LLDP PDU. In this way, there is no need for the virtual switch to send the first indication information to the first virtual port device.

[0132] In an optional example, the first virtual port device generates the first LLDP PDU. For example, the first information indicates that the first device identifier is the identifier of a specific virtual switch, such as VSW1 or VSW2 or other VSW. The first indication information may also indicate that the first port identifier is the identifier of a specific virtual port device, such as VPORT1 or VPORT2 or other VPORT. In this way, the first virtual port device generates the first LLDP PDU based on the first device identifier and the first port identifier indicated by the first information, and encapsulates the first LLDP PDU into an LLDP message. In this way, for the virtual port device, after storing the port identifier and the device identifier, it can send LLDP messages to the industrial device connected to the virtual port device at any time without the need for triggering the virtual switch. In this way, the effectiveness of determining the alias of the new industrial device is higher, and for other control devices, this process is imperceptible.

[0133] It is understandable that if an industrial device is connected to a virtual port device, the port identifier is the identifier of the virtual port device to which the industrial device is connected. In this case, the virtual switch may not need to indicate the first port identifier to the first virtual port device, or the first port identifier indicated by the virtual switch to the first virtual port device is the first virtual port device identifier itself. The virtual port device is connected to the RAN, and the virtual switch (such as the UPF) is variable and invisible to the virtual port device. Typically, the virtual port device does not store the identifier of the virtual switch to which it is connected. However, if the virtual port device can store the identifier of the virtual switch to which it is connected, the virtual switch may not need to indicate the first device identifier to the first virtual port device.

[0134] Optionally, the virtual switch may further send second indication information to the first virtual port device. Accordingly, the first virtual port device receives the second indication information from the virtual switch, where the second indication information is used to instruct the first virtual port device to generate an LLDP PDU. This allows the virtual port device to generate an LLDP PDU promptly and accurately, avoiding a situation where the virtual port device confuses the first indication information with other received information and does not know what to do with it. Of course, the virtual switch and the first virtual port device may mutually agree, or the protocol may stipulate, that the first virtual port device generates the first LLDP PDU. In this case, the virtual switch does not need to send the second indication information to the first virtual port device.

[0135] In the case where the first virtual port device generates the first LLDP PDU, the first virtual port device may trigger the generation of the first LLDP PDU when receiving the second indication information from the virtual switch. Alternatively, the first virtual port device may trigger the generation of the first LLDP PDU by receiving a discovery message from the control device, and the discovery message is used to indicate the acquisition of the first industrial device information. The discovery message is sent by the control device to the virtual switch, and then sent by the virtual switch to the first virtual port device. In the case where the control device does not send a discovery message to the industrial device, generally, no industrial device replacement event occurs. If the virtual port device sends an LLDP message to the industrial device during this period, this process will waste signaling. Therefore, the first virtual port device can trigger the generation of the first LLDP PDU when receiving the discovery message from the control device, and the sending at this time will not cause signaling waste.

[0136] Step 303: The first industrial device determines an alias of the first industrial device based on the first device identifier and the first port identifier in the first LLDP PDU.

[0137] For example, the first industrial device determines its own alias as: first port identifier. identifier of the first device, ie, identifier of the at least one virtual port device (VPORT). identifier of the virtual switch (eg, VSW).

[0138] In this application, the alias is merely a reference and may be any other form, as long as it is mutually agreed upon by the devices within the network. For example, the device identifier may be placed first, followed by the port identifier, such as VSW.VPORT. For another example, other characters, such as "-" or "_", may be used between the port identifier and the device identifier.

[0139] In this embodiment, the virtual switch indicates the port identifier and device identifier to the virtual port device, where the port identifier is the virtual port device identifier and the device identifier is the virtual switch identifier. The virtual port device determines an LLDP message based on the virtual switch's instructions and sends the LLDP message to the new industrial device, allowing the new industrial device to determine its own alias based on the LLDP PDU in the LLDP message. The new industrial device can determine a unique alias based on existing LLDP protocol specifications and existing naming rules.

[0140] In an optional example, the control device can periodically obtain the relevant parameter information of the industrial device based on the device identification of the industrial device in order to obtain the latest network relationship. Due to the failure of the second industrial device, the control device sends a discovery message to the second industrial device based on the device name of the second industrial device, which will cause a timeout and failure to receive a response from the second industrial device. Then, the control device can send a discovery message to the second industrial device based on the alias of the second industrial device. Since the second industrial device is replaced by the first industrial device, the first industrial device will receive the discovery message, and the first industrial device will report its relevant parameter information to the control device. The control device can also query the relevant parameter information of the second industrial device, and inform the first industrial device of the relevant parameter information of the second industrial device (excluding the media access control address MAC of the second industrial device), so that the first industrial device can update the parameter information to achieve lossless replacement of the service.

[0141] The interaction between the control device and the industrial device must go through the virtual port device. For example, the first virtual port device and the first industrial device perform the following process:

[0142] The first virtual port device sends a discovery message to the first industrial device, and the first industrial device receives the discovery message. The discovery message is used to instruct the first industrial device to obtain relevant parameter information. The discovery message includes an alias for the first industrial device, such as VSW.VPORT. The discovery message can be, for example, a Discovery and Configuration Protocol Identify (DCP Identify) request.

[0143] The first industrial device sends a response message to the discovery message, and accordingly, the first virtual port device receives a response message from the first industrial device, where the response message includes relevant parameter information of the first industrial device; for example, the response message may be a Discovery and Configuration Protocol Identification (DCP Identify) response.

[0144] If the discovery message sent by the first virtual port device to the first industrial device comes from the control device, the first virtual port device may further send the response message to the control device, where the response message includes relevant parameter information of the first industrial device.

[0145] After receiving the response message, the control device can send first parameter information to the first industrial device. Accordingly, the first industrial device receives the first parameter information. The first parameter information is the relevant parameter information of the second industrial device replaced by the first industrial device, and the relevant parameter information does not include the media access control address MAC of the second industrial device.

[0146] like Figure 4 As shown in the figure, a specific communication process diagram is introduced. In this example, a CPE is connected to an IO, and an IO is connected to a CPE. The UPF generates LLDP PDUs, and the CPE supports transparent transmission of the LLDP PDUs constructed by the UPF. The following steps are included:

[0147] Step 400: An industrial field enable service (IFES) functional entity may obtain a network topology relationship under normal operation.

[0148] For example, obtain relevant parameter information of each device such as industrial equipment (such as PLC, IO, etc.), newly added network elements of the wireless network (such as UPF, RAN, CPE) and the connection relationship between them.

[0149] For example, IFES sends a discovery message (such as a DCP Identify all request) to all network devices in a multicast manner. The devices that receive the discovery message can feed back their device names, aliases, and other parameter information to IFES.

[0150] IFES can be understood as an APP that can be deployed on the UPF platform or separated from the UPF deployment platform.

[0151] This example uses the connection of IO2 to CPE3 and CPE3 to UPF1 as an example. IFES can obtain the device name of IO2 as IO2 and the alias of IO2 as CPE3.UPF1.

[0152] Step 401: UPF1 generates a service message, and UPF1 sends the service message to CPE3 through RAN. Correspondingly, CPE3 receives the service message from UPF1.

[0153] The message body of the service message includes an LLDP PDU, the device identifier included in the LLDP PDU is the identifier of the UPF1, and the port identifier included in the LLDP PDU is the identifier of the CPE3. As shown in Table 2, the content of an LLDP PDU constructed by UPF1 is introduced.

[0154] Table 2:

[0155]

[0156] The service message generated by UPF1 can be a repackaging of LLDP PDU. In the prior art, LLDP PDU can only be transmitted between two adjacent nodes. In actual applications, RAN will also send LLDP messages to CPE, and the LLDP messages also include LLDP PDU.

[0157] When UPF1 determines that an IO2 device is faulty or needs to be replaced, it can trigger the generation of a service message. For example, if UPF1 frequently fails to receive a response when sending messages to the IO2 device based on its device name, it can determine that the IO2 device needs to be replaced. Alternatively, a manual operation can be performed to notify UPF1 that a new IO device is replacing the IO2 device. This application does not limit how UPF1 determines that an IO2 device needs to be replaced. Typically, the new IO device has essentially the same functionality as the replaced IO2 device, and may even be the same model, enabling lossless service replacement.

[0158] Optionally, CPE3 sends a response message to UPF1 to indicate receipt of the service message.

[0159] It is understandable that there may be switches and other devices between the UPF and the RAN, which is not limited in this application. The UPF1 is connected to the CPE directly or through other network elements.

[0160] Step 402: CPE3 parses the service message to obtain the LLDP PDU, and generates an LLDP message. The message body of the LLDP message is the LLDP PDU obtained by parsing.

[0161] It can also be understood that CPE3 converts the service message into the layer 2 standard LLDP PDU.

[0162] The device identifier included in the LLDP PDU is the identifier of the UPF1, and the port identifier included is the identifier of the CPE3.

[0163] Step 403: CPE3 sends an LLDP message to the new IO device (IO2 device has been replaced by the new IO device). The new IO device receives the LLDP message from CPE3. The LLDP message includes an LLDP PDU.

[0164] It can also be understood that CPE3 transparently transmits (forwards) the LLDP PDU to the new IO device.

[0165] Step 404: The new IO device determines an alias of the new IO device based on the LLDP PDU in the LLDP message.

[0166] For example, a new IO device can specify an alias name as: CPE3's ID.UPF1's ID. As mentioned above, this alias is merely illustrative and can be used in other ways, as long as the devices within the network agree on a common format. For example, the device ID can appear first, followed by the port ID, such as UPF1's ID.CPE3's ID. For another example, other characters, such as "-" or "_," can be used between the port ID and the device ID.

[0167] According to the logic of the prior art, for a new IO device, the device identifier included in the LLDP PDU from CPE3 is the identifier of the CPE3, and the port identifier is the identifier of a port in the CPE3. However, in the present application, UPF1 generates the LLDP PDU, and the device identifier included in the LLDP PDU is the identifier of UPF1, and the port identifier is the identifier of CPE3. UPF1 sends the LLDP PDU to CPE3 as the message body of the service message. CPE3 transparently transmits the LLDP PDU to the new IO device. In this case, the LLDP PDU received by the new IO device includes the device identifier of UPF1 and the port identifier of CPE3. The alias determined by the new IO device is the identifier of UPF1 and the identifier of CPE3.

[0168] Optionally, step 405a: the PLC sends a discovery message to the UPF1, and correspondingly, the UPF1 receives the discovery message from the PLC.

[0169] Discovery messages are used to obtain relevant parameter information of industrial equipment.

[0170] The discovery message may be sent only to the IO2 device, for example, the discovery message includes the device name of the IO2 device. The discovery message may also be sent to all network devices, and the discovery message may be a multicast message.

[0171] The discovery message may be, for example, a DCP identify request.

[0172] Optionally, step 405b: UPF1 sends a discovery message from PLC to IFES, and IFES receives the discovery message from UPF1.

[0173] Step 405c: IFES sends a discovery message to all network devices (mainly industrial devices), but does not receive a response from the IO2 device after a timeout. In this case, it can be determined that IO2 is faulty.

[0174] IFES can send discovery messages in multicast or unicast mode.

[0175] The discovery message may come from UPF1. IFES may replace PLC to construct the old and new device parameter replacement process. IFES itself decides to send the discovery message. In this case, step 405a and step 405b may be omitted.

[0176] When the old and new device parameter replacement process is constructed by the PLC, step 405a and step 405b are not omitted.

[0177] Step 406: IFES can determine the alias of the IO2 device based on the pre-stored network topology, and send a discovery message to the IO2 device based on the alias of the IO2 device (eg, CPE3 ID.UPF1 ID). At this time, the new IO device receives the discovery message.

[0178] The discovery message is, for example, a DCP Identify request.

[0179] IFES can send discovery messages in multicast or unicast mode.

[0180] Table 3 shows the aliases of various devices in the entire network topology.

[0181] Table 3:

[0182]

[0183] As can be seen from Table 3 above, the PLC is connected to UPF1, UPF1 is connected to CPE1, CPE2, and CPE3, the PLC is connected to CPE1, the IO1 device is connected to CPE2, and the IO2 device is connected to CPE3. After the IO2 device fails, a new IO device replaces the IO2 device and is connected to CPE3.

[0184] For UPF, the alias of the IO1 device is CPE2.UPF1; the alias of the IO2 device and the new IO device are both CPE3.UPF1; the alias of the PLC is CPE1.UPF1; or, if there is no CPE1 between the PLC and UPF1, the alias can be port1.UPF1.

[0185] For IO1 device, UPF1 is aliased as port1.IO1;

[0186] For IO2 devices, the alias of UPF1 is port1.IO2;

[0187] For PLC, the alias of UPF1 is CPE1.UPF1 or port1.PLC.

[0188] Step 407: The new IO device sends a response message to the IFES. The response message includes relevant parameter information of the new IO device.

[0189] The response message is, for example, a DCP Identify response. Optionally, the response message may include success indication information, for example, carrying 0x00 in the header to indicate success.

[0190] The relevant parameter information of the new IO device includes the MAC address of the new IO device, site name (NameOfStation), device role (Device Role), device vendor (Device Vendor), device ID (Device ID), device options (Device Options), IP parameters (IP Parameter), DHCP parameters (DHCParameter), manufacturer specific parameters (Manufacturer Specific Parameter), and alias (AliasName).

[0191] Step 408: IFES queries the stored original configuration parameters of the IO2 device.

[0192] Step 409: IFES configures the old parameters of the original configuration parameters except the MAC address to the new IO device, such as the IO2 device's device name, site name (NameOfStation), device role (DeviceRole), device vendor (DeviceVendor), device ID (DeviceID), device options (DeviceOptions), IP parameters (IPParameter), DHCP parameters (DHCPParameter), and manufacturer-specific parameters (ManufacturerSpecificParameter).

[0193] To ensure uninterrupted communication, the SET process ensures parameter consistency (except for the MAC address). For example, IFES sends a DCP Set request to the new I / O device, including the old configuration parameters except for the MAC address. The parameters are stored in the history of industrial topology discovery.

[0194] Step 410: The new IO device sends a response (eg, a DCP Set response) to the IFES, indicating that the DCP Set request has been received.

[0195] The new IO device has updated its parameters based on the old parameters.

[0196] It is understandable that the interaction between IFES and the new IO device requires the participation of UPF1 and CPE3.

[0197] Optionally, step 411a: IFES sends a response message to UPF1, where the response message includes the MAC address of the new IO address.

[0198] The remaining old parameters except MAC remain unchanged.

[0199] The response message is, for example, a DCP Identify response.

[0200] Optionally, step 411b: UPF1 sends a response message from IFES to PLC.

[0201] By letting UPF act as a virtual switch and CPE as a virtual port, the alias of the new IO device can be managed; and based on the existing topology, the remaining parameters of the original device can be completely restored, realizing a more efficient and controllable device replacement and recovery mechanism compared to the existing industrial scene device replacement, thus ensuring the operation of the business.

[0202] like Figure 5 As shown in FIG, a specific communication process diagram is introduced. In this example, one CPE is connected to one IO, one IO is connected to multiple CPEs, and the UPF generates LLDP PDU. Figure 5 Example with Figure 4 The differences in the examples include: Figure 4 In the example, one IO is connected to one CPE. Figure 5 In the example, one IO is connected to two CPEs. The following steps are included:

[0203] Step 500: The Industrial Field Enabling Service (IFES) functional entity may obtain a network topology relationship under normal operation.

[0204] This example uses the case where IO2 is connected to CPE3 and CPE4, which are both connected to UPF1. IFES can obtain the device name of IO2, which is IO2, and the alias of IO2, which is CPE3&CPE4.UPF1.

[0205] For other technical details, please refer to the introduction of step 400.

[0206] Step 501a: UPF1 generates a service message, and UPF1 sends the service message to CPE3 through RAN. Correspondingly, CPE3 receives the service message from UPF1.

[0207] Step 501b: UPF1 generates a service message, and UPF1 sends the service message to CPE4 through RAN. Correspondingly, CPE4 receives the service message from UPF1.

[0208] In steps 501a and 501b, the service message body includes an LLDP PDU. The device identifier included in the LLDP PDU is the identifier of UPF1, and the port identifiers included in the LLDP PDU are the identifier of CPE3 and the identifier of CPE4. This ensures that the port identifiers carried in the LLDP PDUs sent by each connection of the dual connection are consistent, thereby ensuring that the two LLDP PDUs received by the first industrial device are consistent.

[0209] Steps 501a and 501b are similar to step 401, except that the port identifier in step 401 is the CPE3 identifier, while the port identifiers in steps 501a and 501b are the CPE3 identifier and the CPE4 identifier. For other technical details, refer to the description of step 401.

[0210] UPF1 may send a service message to at least one of the multiple CPEs connected to the IO2 device, that is, both step 501a and step 501b may be executed, or only one of them may be executed.

[0211] Step 502a: CPE3 parses the service message to obtain the LLDP PDU, and generates an LLDP message. The message body of the LLDP message is the LLDP PDU obtained by parsing.

[0212] Step 502b: CPE4 parses the service message to obtain the LLDP PDU, and generates an LLDP message. The message body of the LLDP message is the LLDP PDU obtained by parsing.

[0213] Steps 502a and 502b may both be performed, or one of them may be performed. The LLDP PDUs in steps 502a and 502b are the same. For other technical details, please refer to the description of step 402.

[0214] Step 503a: CPE3 sends an LLDP message to the new IO device (IO2 device has been replaced by the new IO device). The new IO device receives the LLDP message from CPE3. The LLDP message includes an LLDP PDU.

[0215] Step 503b: CPE4 sends an LLDP message to the new IO device (IO2 device has been replaced by the new IO device). The new IO device receives the LLDP message from CPE4. The LLDP message includes an LLDP PDU.

[0216] Steps 503a and 503b may both be performed, or one of them may be performed. The LLDP PDUs in steps 503a and 503b are the same. For other technical details, please refer to the description of step 403.

[0217] Step 504: The new IO device determines an alias of the new IO device based on the LLDP PDU in the LLDP message.

[0218] For example, the new IO device determines that the alias of the new IO device is: the identifier of the CPE3 & the identifier of the CPE4. The identifier of the UPF1. For other technical details, please refer to the introduction of step 404.

[0219] Optionally, step 505a: the PLC sends a discovery message to the UPF1, and correspondingly, the UPF1 receives the discovery message from the PLC.

[0220] Step 505a is the same as step 405a and will not be repeated.

[0221] Optionally, step 505b: UP1F sends a discovery message from PLC to IFES, and IFES receives the discovery message from UPF1.

[0222] Step 505b is the same as step 405b and will not be repeated.

[0223] Step 505c: IFES sends a discovery message to all network devices (mainly industrial devices), but does not receive a response from the IO2 device after a timeout. In this case, it can be determined that IO2 is faulty.

[0224] Step 505c is the same as step 405c and will not be repeated.

[0225] Step 506: IFES can determine the alias of the IO2 device based on the pre-stored network topology, and send a discovery message to the IO2 device based on the alias of the IO2 device (eg, CPE3 ID & CPE4 ID & UPF ID). At this time, the new IO device receives the discovery message.

[0226] Table 4 shows the aliases of various devices in the entire network topology.

[0227] Table 4:

[0228]

[0229]

[0230] As can be seen from Table 4 above, the PLC is connected to UPF1, UPF1 is connected to CPE1, CPE2, and CPE3, the PLC is connected to CPE1, the IO1 device is connected to CPE2, and the IO2 device is connected to CPE3 and CPE4. After the IO2 device fails, the new IO device replaces the IO2 device and is connected to CPE3 and CPE4.

[0231] For UPF, the alias of the IO1 device is CPE2.UPF1; the alias of the IO2 device and the new IO device are both CPE3&CPE4.UPF1; the alias of the PLC is CPE1.UPF1; or, if there is no CPE1 between the PLC and UPF1, the alias can be port1.UPF1.

[0232] For IO1 device, UPF1 is aliased as port1.IO1;

[0233] For IO2 devices, the alias of UPF1 is port1.IO2;

[0234] For PLC, the alias of UPF1 is CPE1.UPF1 or port1.PLC.

[0235] For other technical details, please refer to the introduction of step 406.

[0236] Step 507: The new IO device sends a response message to the IFES, which includes relevant parameter information of the new IO device. The response message is, for example, a DCP Identify response. The relevant parameter information of the new IO device includes the MAC address of the new IO device.

[0237] Step 507 is the same as step 407 and will not be repeated.

[0238] Step 508: IFES queries the stored original configuration parameters of the IO2 device.

[0239] Step 508 is the same as step 407 and will not be repeated.

[0240] Step 509: IFES configures the old parameters of the original configuration parameters except MAC to the new IO device.

[0241] For example, the device name of the IO2 device is used to ensure uninterrupted communication.

[0242] For example, the IFES sends a DCP Set request to the new IO device, including the old parameters except the MAC in the original configuration parameters.

[0243] Step 509 is the same as step 409 and will not be repeated.

[0244] Step 510: The new IO device sends a response (eg, a DCP Set response) to the IFES, indicating that the DCP Set request has been received.

[0245] Step 510 is the same as step 410 and will not be repeated.

[0246] Optionally, step 511a: the IFES sends a response message to the UPF, the response message including the MAC address of the new IO address, and other old parameters except the MAC remain unchanged. The response message is, for example, a DCP Identify response.

[0247] Step 511a is the same as step 411a and will not be repeated.

[0248] Optionally, step 411b: the UPF sends a response message from the IFES to the PLC.

[0249] Step 511b is the same as step 411b and will not be repeated.

[0250] like Figure 6 As shown, a specific communication process diagram is provided. In this example, one CPE is connected to one IO, one IO is connected to one CPE, and the CPE generates LLDP PDU. Figure 6 Example with Figure 4 The differences in the examples include: Figure 4 In the example, the LLDP PDU is generated by UPF. Figure 6 In the example, the CPE generates the LLDP PDU. The following steps are involved:

[0251] The following steps are involved:

[0252] Step 600 (same as step 400): the Industrial Field Enabling Service IFES functional entity may obtain the network topology relationship under normal operation.

[0253] This example uses the connection of IO2 to CPE3 and CPE3 to UPF1 as an example. IFES can obtain the device name of IO2 as IO2 and the alias of IO2 as CPE3.UPF1.

[0254] Step 601: UPF1 sends first information to CPE3 through RAN. Correspondingly, CPE3 receives the first information from UPF1.

[0255] The first information indicates that the first device identifier is UPF1. The first indication information may also indicate that the first port identifier is CPE3. In this way, the first virtual port device may construct an LLDP PDU with the device identifier UPF1 and the port identifier CPE3 based on the first information.

[0256] It is understood that if an industrial device is connected to a virtual port device, the port identifier is the identifier of the virtual port device to which the industrial device is connected. In this case, the virtual switch does not need to indicate the first port identifier to the first virtual port device. The virtual port device is connected to the RAN, and the virtual switch (such as the UPF) is variable and invisible to the virtual port device. Typically, the virtual port device does not store the identifier of the virtual switch to which it is connected. However, if the virtual port device can store the identifier of the virtual switch to which it is connected, the virtual switch does not need to indicate the first device identifier to the first virtual port device.

[0257] Optionally, the virtual switch may further send second indication information to the first virtual port device. Accordingly, the first virtual port device receives the second indication information from the virtual switch, where the second indication information is used to instruct the first virtual port device to generate an LLDP PDU. Of course, the virtual switch and the first virtual port device may mutually agree, or the protocol may stipulate, that the first virtual port device generates the first LLDP PDU, thereby eliminating the need to send the second indication information to the first virtual port device.

[0258] Optionally, CPE3 may send a response message to UPF1 to indicate receipt of information from UPF1.

[0259] Step 602: CPE3 saves relevant parameters for constructing LLDP PDU, for example, the storage device identifier is the identifier of UPF1, and the port identifier is the identifier of CPE3.

[0260] Optionally, step 603a (same as step 405a): the PLC sends a discovery message to the UPF, and correspondingly, the UPF receives the discovery message from the PLC.

[0261] Discovery messages are used to obtain relevant parameter information about industrial devices. This discovery message can be sent only to IO2 devices, for example, including the device name of the IO2 device. This discovery message can also be sent to all devices in the network, and can be a multicast message. For example, this discovery message can be a DCP identify request.

[0262] Optionally, step 603b (same as step 405b): UPF1 sends a discovery message from PLC to IFES, and IFES receives the discovery message from UPF1.

[0263] Optionally, step 603c: IFES sends a discovery message to all network devices (mainly IO devices) or IO2 devices.

[0264] IFES can send discovery messages in multicast or unicast mode.

[0265] Step 603c is similar to step 405c and will not be repeated.

[0266] Step 604: CPE3 generates an LLDP message, including an LLDP PDU. The LLDP PDU is generated based on the relevant parameters for constructing the LLDP PDU stored in step 602.

[0267] For example, the device identifier in the LLDP PDU is the identifier of UPF1, and the port identifier is the identifier of CPE3.

[0268] CPE3 may trigger the generation of LLDP PDU based on the discovery message in step 603c.

[0269] If step 603c is not performed, CPE3 may directly perform step 604 after step 602.

[0270] Step 605: CPE3 sends the LLDP message generated in step 604 to the new IO device (IO2 device has been replaced by the new IO device). The new IO device receives the LLDP message from CPE3. The LLDP message includes an LLDP PDU.

[0271] Step 606 (same as step 404): the new IO device determines an alias of the new IO device based on the LLDP PDU in the LLDP message.

[0272] For example, the new IO device determines that the alias of the new IO device is: the identifier of the CPE3.the identifier of the UPF1.

[0273] Step 607a: The new IO device sends relevant parameter information of the new IO device to CPE3.

[0274] The relevant parameter information of the new IO device includes the MAC address of the new IO device, and reference may be made to the introduction in step 407 .

[0275] Step 607b: CPE3 sends the relevant parameter information of the new IO device in step 605 to IFES.

[0276] For example, CPE3 sends a response message to IFES, where the response message includes relevant parameter information of the new IO device.

[0277] The response message is, for example, a DCP Identify response. Optionally, the response message may include success indication information, for example, carrying 0x00 in the header to indicate success.

[0278] Step 607 a and step 607 b are similar to step 407 .

[0279] In this example, after sending a DCP identification request, the control device does not experience a waiting timeout and can receive a response in advance, thus achieving a non-perceptual replacement.

[0280] Step 608 (same as step 408): IFES queries the stored original configuration parameters of the IO2 device.

[0281] Step 609 (same as step 409): IFES configures the old parameters of the original configuration parameters except MAC to the new IO device, for example, the device name of the IO2 device.

[0282] To ensure uninterrupted communication as much as possible, the consistency of parameters (except MAC) is guaranteed through the SET process. For example, IFES sends a DCP Set request to the new IO device, including the old parameters except MAC in the original configuration parameters.

[0283] Step 610 (same as step 410): the new IO device sends a response (eg, a DCP Set response) to the IFES, indicating that the DCP Set request has been received.

[0284] The new IO device has updated its parameters based on the old parameters.

[0285] It is understandable that the interaction between IFES and the new IO device requires the participation of UPF1 and CPE3.

[0286] Optionally, step 611a (same as step 411a): IFES sends a response message to UPF1, where the response message includes the MAC address of the new IO address.

[0287] The remaining old parameters except MAC remain unchanged.

[0288] The response message is, for example, a DCP Identify response.

[0289] Optionally, step 611b (same as step 411b): UPF1 sends the response message from IFES to PLC.

[0290] In a specific communication process, if the CPE supports the DCP SET command, steps 607a to 610 may be replaced by the following process:

[0291] CPE3 stores relevant parameter information of the replaced IO2 device. CPE3 sends a configuration message to the new IO device to configure relevant parameter information of the replaced IO2 device.

[0292] The consistency of parameters (except MAC) can be ensured through the SET process. For example, CPE3 sends a DCPSet request to the new IO device, including the old parameters of the original parameters of the IO2 device except MAC.

[0293] The new IO device sends a response (e.g., a DCP Set response) to CPE3, indicating that it has received the DCP Set request and that the new IO device has updated its parameters based on the old parameters. Optionally, the response message may include a success indication, such as a header containing 0x00 to indicate success.

[0294] CPE3 sends a response message to IFES, where the response message includes the MAC address of the new IO address and the old parameters of the IO2 device except the MAC.

[0295] The response message is, for example, a DCP Identify response. Optionally, the response message may include success indication information, for example, carrying 0x00 in the header to indicate success.

[0296] When one CPE is connected to one IO and one IO is connected to multiple CPEs, the CPE can also generate LLDP PDU, UPF sends the first information to multiple CPEs, and multiple CPEs send LLDP messages to the new IO device. Figure 5 The example is similar and will not be described in detail.

[0297] Example 2:

[0298] The example of embodiment 1 may also be applicable to a scenario where a certain virtual port device (such as CPE) is damaged.

[0299] like Figure 7 As shown, a flow chart of a communication method is introduced, which includes the following steps:

[0300] Step 700: The control device (eg, IFES) obtains the network topology relationship under normal operation.

[0301] For example, the device name of IO2 is IO2, and its alias is CPE3.UPF1. If CPE3 fails and CPE5 comes online, completes authentication, and connects to the wireless industrial network, UPF will know that CPE5 has replaced CPE3.

[0302] When configuring an alias for an IO2 device, the port identifier (e.g., the CPE's International Mobile Equipment Identity (IMEI)) in the LLDP PDU can be changed from CPE3 to CPE5. This means the IO2 device's alias can be changed from CPE3.UPF1 to CPE5.UPF1. Furthermore, the SIM card can be removed from the old device (e.g., CPE3) and placed in the new device (e.g., CPE5), leaving the International Mobile Subscriber Identity (IMSI) unchanged.

[0303] That is to say, the Figure 3b The first virtual port device in the IO2 is the new virtual port device: CPE5, and the first industrial device is the industrial device that has not been replaced: IO2 device.

[0304] Step 701: a virtual switch (eg, UPF1) sends first information to a first virtual port device (eg, CPE5), and correspondingly, the first virtual port device receives the first information from the virtual switch.

[0305] For specific details, please refer to the introduction of step 301 and will not be repeated here.

[0306] Step 702: The first virtual port device (eg, CPE5) sends an LLDP message to the first industrial device (eg, IO2 device). Correspondingly, the first industrial device receives the LLDP message from the first virtual port device.

[0307] For specific details, please refer to the introduction of step 302 and will not be repeated here.

[0308] Step 703: The first industrial device (eg, IO2 device) determines an alias of the first industrial device based on the first device identifier and the first port identifier in the first LLDP PDU.

[0309] For example, the first industrial device determines its own alias as: CPE5.UPF1.

[0310] Optionally, step 704: the control device (eg, IFES) sends a discovery message to the first industrial device (eg, IO2 device) based on the device name of the first industrial device (eg, IO2 device).

[0311] The discovery message is, for example, a DCP Identify request. The IFES may send the discovery message in a multicast or unicast manner.

[0312] Optionally, step 705: the first industrial device (eg, IO2 device) may send a response message to the control device (eg, IFES), the response message including an alias of the first industrial device (eg, IO2 device), such as CPE5.UPF1, and other parameters remain unchanged.

[0313] The response message is, for example, a DCP Identify response. Optionally, the response message may include success indication information, for example, carrying 0x00 in the header to indicate success.

[0314] If only the CPE is replaced, that is, the virtual port device changes, you only need to set the downstream IO alias once.

[0315] Table 5 shows the aliases of various devices.

[0316] Table 5:

[0317]

[0318] As can be seen from Table 5 above, the PLC is connected to UPF1, UPF1 is connected to CPE1, CPE2, and CPE3, the PLC is connected to CPE1, the IO1 device is connected to CPE2, and the IO2 device is connected to CPE3; after CPE3 fails, CPE5 replaces CPE3.

[0319] For UPF, the alias of the IO1 device is CPE2.UPF1; the original alias of the IO2 device is CPE3.UPF1, and the updated alias of the IO2 device is CPE5.UPF; the alias of the PLC is CPE1.UPF1; or, if there is no CPE1 between the PLC and UPF1, the alias can be port1.UPF1.

[0320] For IO1 device, UPF1 is aliased as port1.IO1;

[0321] For IO2 devices, regardless of whether the CPE is updated, the alias of UPF1 is port1.IO2;

[0322] For PLC, the alias of UPF1 is CPE1.UPF1 or port1.PLC.

[0323] Example 3:

[0324] like Figure 8 The figure shows a schematic diagram of a communication system. A virtual switch connects one or more virtual port devices via a RAN. The first virtual port device is any virtual port device in the network. Each virtual port device is connected to a switch. Each switch (SW) is connected to multiple industrial devices, and each industrial device is connected to a SW. The first virtual port device is connected to a second industrial device and other industrial devices. If the second industrial device fails or for other reasons, the first industrial device is used to replace the second industrial device. After the replacement, the first industrial device maintains the same connection relationship with the second industrial device. The connection relationship involved in this embodiment can be a wireless connection such as a 5G connection or a WiFi connection, or a wired connection such as a copper wire, optical fiber, or twisted pair cable.

[0325] exist Figure 8 In the communication system shown in FIG. Figure 4 The core idea of ​​the communication process shown is that the virtual switch constructs LLDP PDU to configure the alias and other related parameter information for the first industrial device (such as IO2 device) in addition to the MAC address. Figure 8 In the communication system shown, the virtual switch sends a service message including an LLDP PDU to the switch SW. The switch SW performs the function of a virtual port device (eg, CPE3) to parse the service message, obtain an LLDP PDU, and send the LLDP PDU to the first industrial device.

[0326] exist Figure 8 In the communication system shown in FIG. 1 , the following may also be used: Figure 6 The idea of ​​the communication process shown is that the virtual switch sends the device identifier and port identifier for constructing LLDP PDU to the virtual port device, and the virtual port device constructs LLDP PDU to configure the alias and other related parameter information except MAC address for the first industrial device (such as IO2 device). However, the difference is that in Figure 8 In the communication system shown, the switch SW performs the function of a virtual port device (eg, CPE3). The virtual switch sends a device identifier and a port identifier for constructing an LLDP PDU to the switch SW. The virtual switch constructs the LLDP PDU and sends the LLDP PDU to the first industrial device.

[0327] In addition, the port identifier in the LLDP PDU needs to be changed. Accordingly, the alias of the second industrial device (e.g., IO2 device) and the alias of the first industrial device (e.g., new IO device) will also be changed. For example, the port identifier of the switch is added on the original basis. The port identifier of the switch refers to the identifier of the port on the switch that is connected to the industrial device to be replaced (also the new industrial device). For example, the first port identifier in the first LLDP PDU is the identifier of the first virtual port device and the port identifier of the switch. The aliases of the first industrial device (e.g., new IO device) and the second industrial device (e.g., IO2 device) are: the identifier of the first virtual port device - the port identifier of the switch. The identifier of the virtual switch.

[0328] For example, if a new IO device is connected to port 2 of switch SW, which is connected to CPE3, which is connected to UPF1, the alias of the new IO device could be: CPE3-2.UPF1, where "2" represents the switch port identifier. Alternatively, the alias of the new IO device could be: CPE3-port2.UPF1, or port2-CPE3.UPF1, or UPF1.port2-CPE3. The alias of the new IO device can be any variation that uniquely identifies the new IO device.

[0329] The following provides a method suitable for Figure 7 In the communication process of the communication system, in this example, the switch SW and the new IO device use the existing method to exchange information, for example:

[0330] The switch sends an LLDP message to the new IO device, and the new IO device receives the LLDP message from the switch. The device identifier in the LLDP PDU in the LLDP message is the identifier of the switch SW, and the port identifier is the port identifier of the switch.

[0331] The new IO device determines its alias based on the LLDP PDU. For example, if the device ID in the LLDP PDU is the ID of the switch SW and the port ID is Port02 of the switch, the new IO device can set its alias to Port02.Switch.

[0332] When the control device sends a discovery message to the new IO device to obtain relevant parameter information of the new IO device, the new IO device may report its own alias to the control device.

[0333] IFES can send discovery messages in multicast or unicast mode.

[0334] The discovery message is, for example, a DCP Identify request, which may include the alias of the IO2 device (ie, the new IO device), or the discovery message is, for example, a DCP Identify all request.

[0335] It is understandable that the interaction between the control device and the new IO device requires the virtual switch, the virtual port device and the switch.

[0336] like Figure 9 As shown, a method suitable for Figure 7 The communication process of the communication system includes the following steps:

[0337] Step 900: The Industrial Field Enabling Service (IFES) functional entity may obtain a network topology relationship under normal operation.

[0338] This example uses the example where IO2 and IO3 are connected to CPE3 through switch SW, CPE3 is connected to UPF1, and a new IO device replaces the faulty IO2. IFES can obtain the device name of IO2, which is IO2 and its alias is Port02.Switch. IFES can also obtain the device name of IO3, which is IO3 and its alias is Port03.Switch.

[0339] Step 901: The switch and the new IO device send LLDP PDUs to each other, and determine that the alias of the new IO device is Port02.Switch.

[0340] Step 902 (same as step 405c): IFES sends a discovery message to all network devices (mainly industrial devices), but does not receive a response from the IO2 device within a timeout period. In this case, it can be determined that IO2 is faulty.

[0341] Step 903 (same as step 406): IFES can determine the alias of the IO2 device based on the pre-stored network topology, and send a discovery message to the IO2 device based on the alias of the IO2 device (eg, Port02.Switch).

[0342] The discovery message is, for example, a DCP Identify request. The IFES may send the discovery message in a multicast or unicast manner.

[0343] The above-mentioned steps 902 and 903 may also be replaced by IFES sending a discovery message to all network devices (mainly industrial devices), and the new IO device receives the discovery message.

[0344] Step 904 (same as step 407): the new IO device sends a response message to the IFES, where the response message includes relevant parameter information of the new IO device.

[0345] The response message is, for example, a DCP Identify response. The relevant parameter information of the new IO device includes the alias and MAC address of the new IO device.

[0346] Step 905 (same as step 408): IFES queries the stored original configuration parameters of the IO2 device.

[0347] Step 906 (same as step 409): IFES configures the old parameters of the original configuration parameters except MAC to the new IO device, such as the device name of the IO2 device.

[0348] To ensure uninterrupted communication, the SET process ensures parameter consistency (except for the MAC address). For example, IFES sends a DCP Set request to the new I / O device, including the old configuration parameters except for the MAC address. The parameters are stored in the history of industrial topology discovery.

[0349] Step 907 (same as step 410): the new IO device sends a response (eg, a DCP Set response) to the IFES, indicating that the DCP Set request has been received.

[0350] The new IO device has updated its parameters based on the old parameters.

[0351] It is understandable that the interaction between IFES and the new IO device requires the participation of UPF1, CPE3, and SW.

[0352] like Figure 10 As shown, a method suitable for Figure 7 The communication process of the communication system, Figure 10 Example with Figure 9 The difference between the examples mentioned above is that the IO device alias stored on the IFES includes CPE and UPF information, while the IO device alias determined by the IO device and the switch SW based on existing methods only contains the switch identifier and switch port identifier, without CPE and UPF information. When the control device sends a message to the IO device, the CPE needs to be able to map the alias. The CPE will convert the alias in the message based on the alias mapping rules so that the IO device can recognize it.

[0353] Step 1000: The Industrial Field Enabling Service (IFES) functional entity may obtain a network topology relationship under normal operation.

[0354] This example uses the case where IO2 and IO3 are connected to CPE3 through switch SW, CPE3 is connected to UPF1, and a new IO device replaces the faulty IO2 device. IFES can obtain the device name of IO2, which is IO2, and the alias of IO2, which is CPE3-2.UPF (where "2" represents Port 02 of the switch). IFES can also obtain the device name of IO3, which is IO3, and the alias of IO3, which is CPE3-3.UPF (where "3" represents Port 03 of the switch).

[0355] Step 1001: The switch and the new IO device send LLDP PDUs to each other, and determine that the alias of the new IO device is Port02.Switch.

[0356] Step 1002: IFES sends a discovery message to CPE3.

[0357] Optionally, the discovery message may include the alias CPE3-2.UPF of the IO2 device.

[0358] The discovery message is, for example, a DCP Identify request. The IFES may send the discovery message in a multicast or unicast manner.

[0359] Step 1003: CPE3 sends a discovery message, and the new IO device receives the discovery message.

[0360] Optionally, CPE3 converts the alias of the IO2 device based on the alias mapping rule, for example, converting CPE3-2.UPF to Port02.Switch. CPE3 sends a discovery message to the alias after conversion (for example, Port02.Switch).

[0361] Step 1004 (similar to step 407): the new IO device sends a response message to CPE3, where the response message includes relevant parameter information of the new IO device.

[0362] The response message is, for example, a DCP Identify response. Optionally, the response message may include success indication information, for example, carrying 0x00 in the header to indicate success.

[0363] The relevant parameter information of the new IO device includes the alias of the new IO device (the alias of the new IO device here is the alias determined with the switch, such as Port02.Switch), MAC address, station name (NameOfStation), device role (Device Role), device vendor (Device Vendor), device ID (Device ID), device options (DeviceOptions), IP parameters (IP Parameter), DHCP parameters (DHCParameter), manufacturer specific parameters (Manufacturer Specific Parameter), and alias (AliasName).

[0364] Step 1005: Based on the alias mapping rules, CPE3 converts the alias of the IO2 device, for example, converting Port02.Switch to CPE3-2.UPF. CPE3 sends a response message to the IFES, which includes parameter information related to the new IO device. The response message, for example, a DCP Identify response, includes the new IO device's alias (here, the converted alias, for example, CPE3-2.UPF), its MAC address, and may also include the information described in step 1004 above.

[0365] Step 1006 (same as step 408): IFES queries the stored original configuration parameters of the IO2 device.

[0366] Step 1007 (similar to step 409): IFES configures the old parameters of the original configuration parameters except MAC to CPE3, such as the device name of the IO2 device, and may also include the information introduced in step 1004 above. There may be no alias in step 1007.

[0367] For example, the IFES sends a DCP Set request to the new IO device, including the old parameters except the MAC in the original configuration parameters.

[0368] During configuration, the message sent to CPE3 carries the alias of the IO2 device stored in the IFES, for example, CPE3-2.UPF.

[0369] Step 1008: CPE3 converts the alias of the IO2 device based on the alias mapping rules, for example, converting CPE3-2.UPF to Port02.Switch. CPE3 configures the IO device with the original configuration parameters, excluding the MAC address. For example, the device name of the IO2 device may also include the information described in step 1007 above.

[0370] Step 1009 (similar to step 410): the new IO device sends a response (eg, a DCP Set response) to the IFES through CPE3, indicating that the DCP Set request has been received.

[0371] The new IO device has updated its parameters based on the old parameters.

[0372] Table 6 shows the alias list for CPE3. The contents of Table 6 refer to the descriptions of Tables 3, 4, and 5, and are not detailed here.

[0373] Table 6:

[0374]

[0375] Table 7 below shows the alias list on the network side. The content in Table 7 can be referred to in the introductions to Tables 3, 4, and 5, and will not be repeated here.

[0376] Table 7:

[0377]

[0378] Example 3:

[0379] like Figure 11 As shown, a schematic diagram of a communication system is introduced. A virtual switch connects one or more industrial devices via a RAN. The industrial devices have wireless access capabilities. The virtual port device can be omitted, or the industrial device and the virtual port device can be understood as being combined into one. If the second industrial device fails or for other reasons, the first industrial device is used to replace the second industrial device. After the replacement, the first industrial device maintains the same connection relationship as the second industrial device, but the alias will change. The connection relationship involved in this embodiment can be a wireless connection such as a 5G connection and a WiFi connection, or it can be a wired connection such as a copper wire, optical fiber, or twisted pair cable.

[0380] like Figure 12 As shown, a flow chart of a communication method is introduced, which can be applied to Figure 11 The communication system shown, Figure 12 Example with Figure 3b The differences in the examples include:

[0381] exist Figure 3b In the example, the virtual switch generates a service message including an LLDP PDU and sends the service message to the virtual port device. After the virtual port device parses the LLDP PDU, it constructs an LLDP message and sends the LLDP message to the first industrial device. Figure 12In the example, since the first industrial device integrates the function of the virtual port device, the service message including the LLDP PDU generated by the virtual switch can be directly sent to the first industrial device. The first industrial device can parse the LLDP PDU and determine the alias of the first industrial device based on the LLDP PDU.

[0382] Figure 12 The following steps are involved:

[0383] Step 1200: The virtual switch sends a service message to the first industrial device. Correspondingly, the first industrial device receives the service message from the virtual switch.

[0384] The service message body includes a first Link Layer Discovery Protocol Packet Data Unit (LLDP PDU). That is, the virtual switch adds a message header to the generated first LLDP PDU and sends the entire message to the first industrial device. The first industrial device can parse the service message to obtain the first LLDP PDU.

[0385] The first LLDP PDU is used to determine an alias of the industrial device.

[0386] In this embodiment, the first device identifier included in the first LLDP PDU is the identifier of the virtual switch, and the first port identifier included in the first LLDP PDU is the permanent equipment identifier (PEI) or international mobile equipment identity (IMEI) of the first industrial device.

[0387] When registering, the industrial device has reported its own PEI and / or IMEI to the network side, so the virtual port device knows the PEI and / or IMEI of the new industrial device.

[0388] In scenarios where an industrial device and a virtual port device are combined into one, when an industrial device is replaced, the PEI and IMEI of the new industrial device will change relative to the original industrial device, so the alias of the new industrial device will also change relative to the original industrial device. For example, if the device name of the replaced second industrial device is IO2 and the alias is CPE3.UPF1, and the PEI / IMEI of the first industrial device is CPE4, the alias of the first industrial device is CPE4.UPF1.

[0389] It can be understood that the virtual switch sends service information to the first industrial device through the RAN.

[0390] Step 1201: A first industrial device determines an alias of the first industrial device based on the first device identifier and the first port identifier.

[0391] For example, the first industrial device determines its own alias as: first port identifier.identifier of the first device, that is, IMEI.identifier of the virtual switch.

[0392] This alias is merely a reference and may be any other form, as long as it is agreed upon by all devices within the network. For example, the device identifier may be placed first, followed by the port identifier, such as the virtual switch identifier.IMEI. For another example, other characters, such as "-" or "_", may be used between the port identifier and the device identifier.

[0393] In this embodiment, the first industrial device can also report its own relevant parameter information to the control device, and the control device can send the relevant parameter information of the second industrial device (the second industrial device is damaged and replaced by the first industrial device) to the first industrial device (excluding the media access control address MAC of the second industrial device) to achieve lossless replacement of services. This process is the same as the process described in Example 1, for example:

[0394] The control device sends a discovery message to the first industrial device, and the first industrial device receives the discovery message in response. The discovery message is used to instruct the first industrial device to obtain relevant parameter information. The discovery message includes an alias for the first industrial device. The discovery message can be, for example, a Discovery and Configuration Protocol (DCP) Identify request.

[0395] The first industrial device sends a response message to the discovery message. Accordingly, the control device receives a response message from the first industrial device, where the response message includes relevant parameter information of the first industrial device. For example, the response message may be a Discovery and Configuration Protocol Identification (DCP Identify) response.

[0396] After receiving the response message, the control device can send first parameter information to the first industrial device. Accordingly, the first industrial device receives the first parameter information. The first parameter information is the relevant parameter information of the second industrial device replaced by the first industrial device, and the relevant parameter information does not include the media access control address MAC of the second industrial device.

[0397] The specific process can be referred to Figure 4 For example, the process from step 405a to step 411b can be referred to Figure 5 The process from step 505a to step 511b in the embodiment will not be repeated.

[0398] The virtual switch generates a service message containing an LLDP PDU and sends it to the new industrial device, allowing it to determine its own alias based on the LLDP PDU in the service message. The new industrial device can determine a unique alias based on the existing LLDP protocol specifications and naming rules, using the Permanent Equipment Identity (PEI) or International Mobile Equipment Identity (IMEI) as a port identifier, allowing the new IO device to join the wireless networking architecture.

[0399] The preceding text describes the method of the embodiment of the present application. The following text describes the device of the embodiment of the present application. The method and device are based on the same technical concept. Since the principles of the method and device to solve the problem are similar, the implementation of the device and method can refer to each other, and the repeated parts will not be repeated.

[0400] In the embodiments of the present application, the functional modules of the device can be divided according to the above method examples. For example, each function can be divided into various functional modules, or two or more functions can be integrated into one module. These modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiments of the present application is schematic and is only a logical functional division. Other division methods may be used in specific implementations.

[0401] Based on the same technical concept as the above method, see Figure 13 , provides a schematic structural diagram of a communication device 1300. The device 1300 may include a processing module 1310 and, optionally, a receiving module 1320a, a sending module 1320b, and a storage module 1330. The processing module 1310 may be connected to the storage module 1330, the receiving module 1320a, and the sending module 1320b, respectively. The storage module 1330 may also be connected to the receiving module 1320a and the sending module 1320b.

[0402] In an example, the above-mentioned receiving module 1320a and sending module 1320b can also be integrated together and defined as a transceiver module.

[0403] In an example, the apparatus 1300 may be a first virtual port device, or a chip or functional unit used in the first virtual port device. The apparatus 1300 has any function of the first virtual port device in the above method, for example, the apparatus 1300 can execute the above Figure 3b 、 Figure 4 、 Figure 5 、 Figure 6 、 Figure 7 、 Figure 9 、 Figure 10 、 Figure 12The steps of the method are performed by the first virtual port device.

[0404] The receiving module 1320a may execute the receiving action performed by the first virtual port device in the above method embodiment.

[0405] The sending module 1320b may execute the sending action performed by the first virtual port device in the above method embodiment.

[0406] The processing module 1310 may execute other actions except the sending action and the receiving action among the actions executed by the first virtual port device in the above method embodiment.

[0407] In one example, the receiving module 1320a is used to receive first information from a virtual switch, where the first information is used to indicate a first device identifier and a first port identifier, where the first device identifier is the identifier of the virtual switch, and the first port identifier includes the identifier of at least one virtual port device.

[0408] The sending module 1320b is used to send a link layer discovery protocol LLDP message to the first industrial device, where the LLDP message includes a first link layer discovery protocol packet data unit LLDP PDU, the first device identifier in the first LLDP PDU is the identifier of the virtual switch, the first port identifier in the first LLDP PDU includes the identifier of at least one virtual port device, and the first LLDP PDU is used to determine the alias of the first industrial device.

[0409] In a possible implementation, the first information may be a service message; and the message body of the service message includes the first LLDP PDU.

[0410] In a possible implementation, the first information may further include first indication information, where the first indication information is used to instruct transparent transmission of the first LLDP PDU.

[0411] In a possible implementation, the processing module 1310 may be configured to generate the first LLDP PDU based on the first device identifier and the first port identifier indicated by the first information.

[0412] In a possible implementation, the receiving module 1320a is further configured to receive second indication information from the virtual switch, where the second indication information is used to instruct the first virtual port device to generate an LLDP PDU.

[0413] In a possible implementation, the receiving module 1320a is further configured to receive a discovery message from a control device to trigger generation of the first LLDP PDU, where the discovery message is used to instruct acquisition of the first industrial device information.

[0414] In one possible implementation, the sending module 1320b is further configured to send the discovery message to the first industrial device, where the discovery message is used to instruct the acquisition of relevant parameter information of the first industrial device. The receiving module 1320a is further configured to receive a response message from the first industrial device, where the response message includes the relevant parameter information of the first industrial device. The sending module 1320b is further configured to send the response message to the control device, where the response message includes the relevant parameter information of the first industrial device.

[0415] In an example, the storage module 1330 may store computer-executable instructions for the method executed by the first virtual port device, so that the processing module 1310 , the receiving module 1320 a , and the sending module 1320 b execute the method executed by the first virtual port device in the above example.

[0416] In one example, the device 1300 may be a virtual switch, or a chip or functional unit used in a virtual switch. The device 1300 has any function of the virtual switch in the above method, for example, the device 1300 can execute the above Figure 3b 、 Figure 4 、 Figure 5 、 Figure 6 、 Figure 7 、 Figure 9 、 Figure 10 、 Figure 12 The steps in the method are performed by the virtual switch.

[0417] The receiving module 1320a can execute the receiving action performed by the virtual switch in the above method embodiment.

[0418] The sending module 1320b can execute the sending action performed by the virtual switch in the above method embodiment.

[0419] The processing module 1310 may execute other actions except the sending action and the receiving action among the actions executed by the virtual switch in the above method embodiment.

[0420] In one example, the processing module 1310 is configured to generate first information, the first information being used to indicate a first device identifier and a first port identifier, the first device identifier and the first port identifier being used to generate a first Link Layer Discovery Protocol Packet Data Unit (LLDP) PDU, wherein the first device identifier is the identifier of the virtual switch, the first port identifier includes the identifier of at least one virtual port device, and the first LLDP PDU is used to determine an alias for the first industrial device. The sending module 1320b is configured to send the first information to a first virtual port device, the at least one virtual port device including the first virtual port device.

[0421] In a possible implementation, the first information may be a service message; and the message body of the service message includes the first LLDP PDU.

[0422] In a possible implementation, the first information may further include first indication information, where the first indication information is used to instruct transparent transmission of the first LLDP PDU.

[0423] In a possible implementation, the sending module 1320b is further configured to send second indication information to the first virtual port device, where the second indication information is used to instruct the first virtual port device to generate an LLDP PDU.

[0424] In an example, the storage module 1330 may store computer-executable instructions for the method executed by the virtual switch, so that the processing module 1310 , the receiving module 1320 a , and the sending module 1320 b execute the method executed by the virtual switch in the above example.

[0425] In one example, the device 1300 may be a first industrial device, or a chip or functional unit used in the first industrial device. The device 1300 has any function of the first industrial device in the above method, for example, the device 1300 can execute the above Figure 3b 、 Figure 4 、 Figure 5 、 Figure 6 、 Figure 7 、 Figure 9 、 Figure 10 、 Figure 12 The steps of the method are performed by the first industrial device.

[0426] The receiving module 1320a can execute the receiving action performed by the first industrial device in the above method embodiment.

[0427] The sending module 1320b can execute the sending action performed by the first industrial device in the above method embodiment.

[0428] The processing module 1310 may execute other actions except the sending action and the receiving action among the actions executed by the first industrial device in the above method embodiment.

[0429] In one example, the receiving module 1320a is configured to receive an LLDP message from a first virtual port device, the LLDP message including a first Link Layer Discovery Protocol Packet Data Unit (LLDP PDU); the first device identifier included in the first LLDP PDU is an identifier of a virtual switch, and the first port identifier included in the first LLDP PDU includes an identifier of at least one virtual port device; the first LLDP PDU is used to determine an alias for the first industrial device. The processing module 1310 is configured to determine an alias for the first industrial device based on the first device identifier and the first port identifier. For example, the alias is the identifier of the virtual switch and the identifier of the at least one virtual port device.

[0430] In one possible implementation, the receiving module 1320a is further configured to receive a discovery message, the discovery message including the alias of the first industrial device, and the discovery message instructing the acquisition of parameter information related to the first industrial device. The sending module 1320b is further configured to send a response message including the parameter information related to the first industrial device. The receiving module 1320a is further configured to receive first parameter information, the first parameter information being parameter information related to the old industrial device replaced by the first industrial device, the parameter information not including the media access control address (MAC) of the old industrial device.

[0431] In an example, the storage module 1330 may store computer-executable instructions for a method executed by the first industrial device, so that the processing module 1310 , the receiving module 1320 a , and the sending module 1320 b execute the method executed by the first industrial device in the above example.

[0432] For example, the storage module may include one or more memories, which may be devices in one or more devices or circuits used to store programs or data. The storage module may be a register, cache, or RAM, etc., and the storage module may be integrated with the processing module. The storage module may be a ROM or other type of static storage device that can store static information and instructions, and the storage module may be independent of the processing module.

[0433] The transceiver module may be an input or output interface, a pin or a circuit, etc.

[0434] As a possible product form, the device can be implemented by a general bus architecture.

[0435] like Figure 14 As shown, a schematic block diagram of a communication device 1400 is provided.

[0436] The apparatus 1400 may include a processor 1410 and, optionally, a transceiver 1420 and a memory 1430. The transceiver 1420 may be configured to receive programs or instructions and transmit them to the processor 1410. Alternatively, the transceiver 1420 may be configured to allow the apparatus 1400 to communicate with other communication devices, such as exchanging control signaling and / or service data. The transceiver 1420 may be a code and / or data reader / writer, or a signal transmission transceiver between the processor and the transceiver. The processor 1410 and the memory 1430 are electrically coupled.

[0437] In one example, the apparatus 1400 may be a first virtual port device, or a chip used in the first virtual port device. It should be understood that the apparatus has any function of the first virtual port device in the above method, for example, the apparatus 1400 can execute the above method. Figure 3b 、 Figure 4 、 Figure 5 、 Figure 6 、 Figure 7 、 Figure 9 、 Figure 10 、 Figure 12 The steps of the method performed by the first virtual port device in the example are shown in FIG. For example, the memory 1430 is used to store a computer program; the processor 1410 can be used to call the computer program or instructions stored in the memory 1430 to perform the method performed by the first virtual port device in the example, or to perform the method performed by the first virtual port device in the example through the transceiver 1420.

[0438] In one example, the device 1400 may be a virtual switch or a chip used in a virtual switch. It should be understood that the device has any function of the virtual switch in the above method. For example, the device 1400 can execute the above method. Figure 3b 、 Figure 4 、 Figure 5 、 Figure 6 、 Figure 7 、 Figure 9 、 Figure 10 、 Figure 12 The steps of the method performed by the virtual switch are shown in FIG. For example, the memory 1430 is used to store a computer program; the processor 1410 can be used to call the computer program or instructions stored in the memory 1430 to execute the method performed by the virtual switch in the above example, or to execute the method performed by the virtual switch in the above example through the transceiver 1420.

[0439] In one example, the device 1400 may be a first industrial device, or a chip used in the first industrial device. It should be understood that the device has any function of the first industrial device in the above method, for example, the device 1400 can execute the above Figure 3b 、 Figure 4 、 Figure 5 、 Figure 6 、 Figure 7 、 Figure 9 、 Figure 10 、 Figure 12 The steps of the method performed by the first industrial device in the example are shown in FIG. For example, the memory 1430 is used to store a computer program; the processor 1410 can be used to call the computer program or instructions stored in the memory 1430 to execute the method performed by the first industrial device in the example, or to execute the method performed by the first industrial device in the example through the transceiver 1420.

[0440] Figure 13 The processing module 1310 in can be implemented by the processor 1410.

[0441] Figure 13 The receiving module 1320a and the sending module 1320b in the embodiment can be implemented by the transceiver 1420. Alternatively, the transceiver 1420 is divided into a receiver and a transmitter, the receiver performs the function of the receiving module, and the transmitter performs the function of the sending module.

[0442] Figure 13 The storage module 1330 can be implemented by the memory 1430.

[0443] As a possible product form, the device may be implemented by a general-purpose processor (a general-purpose processor may also be referred to as a chip or a chip system).

[0444] In one possible implementation, a general processor implemented in an apparatus for a first virtual port device or an apparatus for a virtual switch or a first industrial device includes: a processing circuit (a processing circuit may also be referred to as a processor); optionally, further including: an input and output interface internally connected to and communicating with the processing circuit, and a storage medium (a storage medium may also be referred to as a memory), wherein the storage medium is used to store instructions executed by the processing circuit to execute the method executed by the first virtual port device or virtual switch or first industrial device in the above example.

[0445] Figure 13 The processing module 1310 in can be implemented by a processing circuit.

[0446] Figure 13The receiving module 1320a and the sending module 1320b in the embodiment can be implemented by an input / output interface. Alternatively, the input / output interface is divided into an input interface and an output interface, the input interface performs the function of the receiving module, and the output interface performs the function of the sending module.

[0447] Figure 13 The storage module 1330 can be implemented by a storage medium.

[0448] As a possible product form, the device of the embodiment of the present application can also be implemented using the following: one or more FPGAs (field programmable gate arrays), PLDs (programmable logic devices), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits that can perform the various functions described throughout this application.

[0449] The present application also provides a computer-readable storage medium storing a computer program, which, when executed by a computer, enables the computer to perform the aforementioned communication method. In other words, the computer program includes instructions for implementing the aforementioned communication method.

[0450] An embodiment of the present application further provides a computer program product, including: computer program code, which, when executed on a computer, enables the computer to execute the communication method provided above.

[0451] An embodiment of the present application further provides a communication system, which includes: a virtual switch for executing the above-mentioned communication method, a first virtual port device, and a first industrial device.

[0452] In addition, the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), a baseband processor, the baseband processor and the CPU may be integrated together or separated, or may be a network processor (NP) or a combination of a CPU and an NP. The processor may further include a hardware chip or other general-purpose processor. The above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) and other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. or any combination thereof. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0453] The memory mentioned in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0454] The transceiver mentioned in the embodiments of the present application may include a separate transmitter and / or a separate receiver, or may be an integrated transmitter and receiver. The transceiver may operate under the instructions of a corresponding processor. Optionally, the transmitter may correspond to a transmitter in a physical device, and the receiver may correspond to a receiver in a physical device.

[0455] Those skilled in the art will appreciate that the various method steps and units described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the steps and components of each embodiment have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0456] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or can be electrical, mechanical or other forms of connection.

[0457] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of the present application.

[0458] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0459] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0460] The term "and / or" in this application describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent three situations: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the objects associated with each other are in an "or" relationship. The term "multiple" referred to in this application refers to two or more. In addition, it should be understood that in the description of this application, words such as "first" and "second" are only used to distinguish the description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order.

[0461] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the present application.

[0462] Obviously, those skilled in the art may make various changes and modifications to the embodiments of the present application without departing from the spirit and scope of the embodiments of the present application. Thus, if these modifications and variations of the embodiments of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations.

Claims

1. A communication method, characterized in that: include: The first virtual port device receives first information from the virtual switch, where the first information is used to indicate a first device identifier and a first port identifier, where the first device identifier is an identifier of the virtual switch, and the first port identifier includes an identifier of at least one virtual port device; The first virtual port device sends an LLDP message to the first industrial device, where the LLDP message includes a first LLDP PDU, the first device identifier in the first LLDP PDU is the identifier of the virtual switch, the first port identifier in the first LLDP PDU includes the identifier of at least one virtual port device, and the first LLDP PDU is used to determine an alias of the first industrial device.

2. The method according to claim 1, wherein The first information is a service message; and the message body of the service message includes the first LLDP PDU.

3. The method according to claim 2, wherein The first information further includes first indication information, where the first indication information is used to instruct transparent transmission of the first LLDP PDU.

4. The method according to claim 1, wherein Also includes: The first virtual port device generates the first LLDP PDU based on the first information.

5. The method according to claim 4, wherein Also includes: The first virtual port device receives second indication information from the virtual switch, where the second indication information is used to instruct the first virtual port device to generate an LLDP PDU.

6. The method according to claim 4 or 5, characterized in that Also includes: The first virtual port device receives a discovery message from the control device, triggering generation of the first LLDP PDU, where the discovery message is used to instruct acquisition of the first industrial device information.

7. The method according to any one of claims 1 to 5, characterized in that After the first virtual port device sends the LLDP message to the first industrial device, the method further includes: The first virtual port device sends a discovery message to the first industrial device, where the discovery message is used to instruct the acquisition of relevant parameter information of the first industrial device; The first virtual port device receives a response message from the first industrial device, where the response message includes relevant parameter information of the first industrial device; The first virtual port device sends the response message to the control device, where the response message includes relevant parameter information of the first industrial device.

8. The method according to any one of claims 1 to 5, wherein: Also includes: The virtual switch generates the first information; The virtual switch sends the first information to the first virtual port device, and the at least one virtual port device includes the first virtual port device.

9. The method according to any one of claims 1 to 5, wherein: Also includes: The first industrial device receives the LLDP message from the first virtual port device; The first industrial device determines an alias of the first industrial device based on the first device identifier and the first port identifier.

10. The method according to claim 9, wherein Also includes: The first industrial device receives a discovery message, where the discovery message includes an alias of the first industrial device, and the discovery message is used to instruct the acquisition of relevant parameter information of the first industrial device; The first industrial device sends a response message, where the response message includes relevant parameter information of the first industrial device; The first industrial device receives first parameter information, where the first parameter information is related parameter information of an old industrial device replaced by the first industrial device. The related parameter information does not include a media access control address MAC of the old industrial device.

11. A communication system, characterized in that: include: A virtual switch, configured to generate first information, wherein the first information is used to indicate a first device identifier and a first port identifier, wherein the first device identifier is an identifier of the virtual switch, and the first port identifier includes an identifier of at least one virtual port device; A first virtual port device, configured to receive first information from the virtual switch and send an LLDP message to a first industrial device, wherein the LLDP message includes a first LLDP PDU, wherein the first device identifier in the first LLDP PDU is an identifier of the virtual switch, and the first port identifier in the first LLDP PDU includes an identifier of at least one virtual port device, and the first LLDP PDU is used to determine an alias of the first industrial device; The first industrial device is configured to receive an LLDP message from a first virtual port device and determine an alias of the first industrial device based on the first device identifier and the first port identifier.

12. The system according to claim 11, wherein The first information is a service message; and the message body of the service message includes the first LLDP PDU.

13. The system according to claim 12, wherein: The first information further includes first indication information, where the first indication information is used to instruct transparent transmission of the first LLDP PDU.

14. The system according to claim 11, wherein: The first virtual port device is further configured to generate the first LLDP PDU based on the first device identifier and the first port identifier indicated by the first information.

15. The system according to claim 14, wherein: The virtual switch is further configured to send second indication information to the first virtual port device, where the second indication information is used to instruct the first virtual port device to generate an LLDP PDU; The first virtual port device is further configured to receive second indication information from the virtual switch.

16. The system according to claim 14 or 15, characterized in that The first virtual port device is configured to receive a discovery message from a control device to trigger generation of the first LLDP PDU, where the discovery message is used to instruct acquisition of the first industrial device information.

17. The system according to any one of claims 11 to 15, wherein: The first virtual port device is further configured to, after sending the LLDP message to the first industrial device, send a discovery message to the first industrial device, wherein the discovery message is used to instruct the acquisition of relevant parameter information of the first industrial device; and receive a response message from the first industrial device, wherein the response message includes the relevant parameter information of the first industrial device; And sending the response message to the control device, where the response message includes relevant parameter information of the first industrial device.

18. The system according to any one of claims 11 to 15, wherein: The first industrial device is further configured to receive a discovery message, wherein the discovery message includes an alias of the first industrial device, and the discovery message is used to instruct the acquisition of relevant parameter information of the first industrial device; Sending a response message, wherein the response message includes relevant parameter information of the first industrial device; And first parameter information is received, where the first parameter information is related parameter information of the old industrial equipment replaced by the first industrial equipment, and the related parameter information does not include the media access control address MAC of the old industrial equipment.

19. A communication device, characterized in that: include: A functional module for implementing the method according to any one of claims 1 to 10.

20. A communication device, characterized in that: comprising a processor coupled to a memory; The memory is used to store computer programs or instructions; The processor is configured to execute part or all of the computer programs or instructions in the memory, and when the part or all of the computer programs or instructions are executed, is configured to implement the method according to any one of claims 1 to 10.

21. A communication device, characterized in that: including processor and memory; The memory is used to store computer programs or instructions; The processor is configured to execute part or all of the computer programs or instructions in the memory, and when the part or all of the computer programs or instructions are executed, is configured to implement the method according to any one of claims 1 to 10.

22. A chip system, characterized in that: The chip system includes: a processing circuit; the processing circuit is coupled to a storage medium; The processing circuit is used to execute part or all of the computer programs or instructions in the storage medium, and when the part or all of the computer programs or instructions are executed, it is used to implement the method according to any one of claims 1 to 10.

23. A computer-readable storage medium, characterized in that Used to store a computer program, wherein the computer program includes instructions for implementing the method according to any one of claims 1 to 10.

24. A computer program product, characterized in that The computer program product comprises: a computer program code, and when the computer program code is run on a computer, the computer is caused to perform the method according to any one of claims 1 to 10.

Images