WO2023134338A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2023134338A1
WO2023134338A1 PCT/CN2022/137353 CN2022137353W WO2023134338A1 WO 2023134338 A1 WO2023134338 A1 WO 2023134338A1 CN 2022137353 W CN2022137353 W CN 2022137353W WO 2023134338 A1 WO2023134338 A1 WO 2023134338A1
Authority
WO
WIPO (PCT)
Prior art keywords
industrial
identifier
lldp
information
virtual
Prior art date
Application number
PCT/CN2022/137353
Other languages
English (en)
French (fr)
Inventor
朱锦涛
周凯
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023134338A1 publication Critical patent/WO2023134338A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/70—Virtual switches
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/03—Protocol definition or specification 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks

Definitions

  • the embodiments of the present application relate to fields such as communications, and in particular, to a communication method and device.
  • the industrial automation and control system is composed of many electronic and controller components, which are widely used in various industrial industries such as chemical industry, paper industry, power plant, oil and gas refining, and telecommunications industry.
  • the controller takes up a lot of space, and the loop flow is not easy to modify and maintain.
  • programmable logic controller programmable logic controller, PLC
  • a master PLC and input-output (input-output, IO) devices are connected through a switch.
  • IO input-output
  • the communication between different nodes is connected by wires, such as copper wires, twisted pair wires, and optical fibers.
  • wireless communication technology has gradually become a new medium for industrial field network connection.
  • the existing PLC, IO and other equipment can be wirelessly connected, realizing a more flexible networking mode of industrial equipment, and it can be more convenient, such as supporting the needs of automatic guided vehicles (automated guided vehicle, AGV).
  • a new type of industrial terminal equipment with mobility and flexible networking is a new type of industrial terminal equipment with mobility and flexible networking.
  • Embodiments of the present application provide a communication method and device for implementing a new IO device to join a wireless networking architecture.
  • a communication method is provided, and the execution subject of the method may be a first virtual port device, or may be a component applied to the first virtual port device, such as a chip, a processor, and the like.
  • the following description is made by taking the execution subject as the first virtual port device as an example.
  • the first virtual port device receives first information from the virtual switch, the first information is used to indicate the first device identifier and the first port identifier, the first device identifier is the identifier of the virtual switch, the The first port identifier includes an identifier of at least one virtual port device.
  • the first virtual port device can send a link layer discovery protocol LLDP message to the first industrial device, the LLDP message includes the first link layer discovery protocol packet data unit LLDP PDU, and the first LLDP PDU
  • the first device identifier is the identifier of the virtual switch
  • the first port identifier in the first LLDP PDU includes at least one virtual port device identifier
  • the first LLDP PDU is used to determine the identity of the first industrial device alias.
  • each virtual port device is connected to one industrial device, and one industrial device may be connected to one or more virtual port devices.
  • the virtual switch indicates the port ID and device ID to the virtual port device, 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 packet based on the indication of the virtual switch, and sends the LLDP packet to the new industrial devices, so that new industrial devices can determine their own aliases based on the LLDP PDU in the LLDP message.
  • New industrial devices can determine a unique alias based on the existing LLDP protocol specification and existing naming rules, so as to realize the addition of new IO devices to the wireless networking architecture.
  • the first information may be a service message; a message body of the service message includes the first LLDP PDU.
  • this method only needs to analyze the transparent transmission, and the implementation is relatively simple.
  • the first information may further include first indication information, where the first indication information is used to indicate transparent transmission of the first LLDP PDU.
  • the virtual port device can accurately and timely transparently transmit the first LLDP PDU in the service message, so as to avoid confusion with other messages and fail to transparently transmit the first LLDP PDU in the service message.
  • the first virtual port device may generate the first LLDP PDU based on the first device identifier and the first port identifier indicated by the first information. In this way, for a virtual port device, after storing the port ID and device ID, it can send LLDP packets to the industrial device connected to the virtual port device at any time without triggering the virtual switch, thus determining the alias of the new industrial device The effectiveness is higher, and for other control devices, this process is imperceptible.
  • 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 the LLDP PDU.
  • the virtual port device can generate LLDP PDUs in a timely and accurate manner, so as to prevent the virtual port device from confusing the first indication information with other received information, and does not know how to deal with it.
  • the first virtual port device may also receive a discovery message from the control device, triggering generation of the first LLDP PDU, where the discovery message is used to instruct to acquire the information of the first industrial device.
  • the control device does not send a discovery message to the industrial device
  • the replacement event of the industrial device usually does not occur. If the virtual port device sends an LLDP message to the industrial device during this period, this process will waste signaling. Therefore, when the first virtual port device receives the discovery message from the control device, it can trigger the generation of the first LLDP PDU, and sending at this time will not cause signaling waste.
  • the first virtual port device may also send the discovery message to the first industrial device , the discovery message is used to instruct to obtain related parameter information of the first industrial device. Then, the first virtual port device may receive a response message from the first industrial device, where the response message includes relevant parameter information of the first industrial device. Next, the first virtual port device may send the response message to the control device, where the response message includes relevant parameter information of the first industrial device. In order to realize the non-destructive replacement of the business.
  • a communication method is provided, and the execution subject of the method may be a virtual switch, or may be a component applied to the virtual switch, such as a chip, a processor, and the like.
  • the following description is made by taking the execution subject as an example of a virtual switch.
  • the virtual switch generates first information, where 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 the identifier of the virtual switch, and the first port identifier includes at least one virtual port device identifier; the first LLDP PDU is used to determine the first industrial device alias for . Then, the virtual switch may send the first information to a first virtual port device, where the at least one virtual port device includes the first virtual port device.
  • each virtual port device is connected to one industrial device, and one industrial device can be connected to one or more virtual port devices.
  • the virtual switch indicates the port ID and device ID to the virtual port device, 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 packet based on the indication of the virtual switch, and sends the LLDP packet to the new industrial devices, so that new industrial devices can determine their own aliases based on the LLDP PDU in the LLDP message.
  • New industrial devices can determine a unique alias based on the existing LLDP protocol specification and existing naming rules, so as to realize the addition of new IO devices to the wireless networking architecture.
  • the first information may be a service message; a message body of the service message includes the first LLDP PDU.
  • this method only needs to analyze the transparent transmission, and the implementation is relatively simple.
  • the first information may further include first indication information, where the first indication information is used to indicate transparent transmission of the first LLDP PDU.
  • the virtual port device can accurately and timely transparently transmit the first LLDP PDU in the service message, so as to avoid confusion with other messages and fail to transparently transmit the first LLDP PDU in the service message.
  • the virtual switch may further 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 the LLDP PDU.
  • the second indication information can enable the virtual port device to generate LLDP PDUs in a timely and accurate manner, so as to prevent the virtual port device from confusing the first indication information with other received information and not knowing how to deal with it.
  • a communication method is provided, and the execution body of the method may be the first industrial equipment, or may be a component applied to the first industrial equipment, such as a chip, a processor, and the like.
  • the following description will be made by taking the execution subject as an example of the first industrial equipment.
  • the first industrial device may receive an LLDP message from the first virtual port device, the LLDP message includes a first link layer discovery protocol packet data unit LLDP PDU; the first device included in the first LLDP PDU
  • the identifier 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 the alias of the first industrial device.
  • the first industrial device determines an 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.the identifier of the at least one virtual port device.
  • each virtual port device is connected to one industrial device, and one industrial device may be connected to one or more virtual port devices.
  • the virtual switch indicates the port ID and device ID to the virtual port device, 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 packet based on the indication of the virtual switch, and sends the LLDP packet to the new industrial devices, so that new industrial devices can determine their own aliases based on the LLDP PDU in the LLDP message.
  • New industrial devices can determine a unique alias based on the existing LLDP protocol specification and existing naming rules, so as to realize the addition of new IO devices to the wireless networking architecture.
  • the first industrial device may receive a discovery message, where the discovery message includes an alias of the first industrial device, and the discovery message is used to instruct to obtain the related information of the first industrial device. Parameter information. Then, the first industrial device may send a response message, where the response message includes relevant parameter information of the first industrial device. Next, the first industrial equipment receives first parameter information, and the first parameter information is relevant parameter information of the old industrial equipment replaced by the first industrial equipment, and the relevant parameter information does not include the old industrial equipment.
  • the media access control address MAC of industrial equipment In order to realize the non-destructive replacement of the business.
  • the first to third aspects are applicable to the scenario where the industrial device and the virtual port device are divided into two devices, and the fourth and fifth aspects are applicable to the scenario where the industrial device and the virtual port device are combined into one device.
  • a communication method is provided, and the execution subject of the method may be a virtual switch, or may be a component applied to the virtual switch, such as a chip, a processor, and the like.
  • the following description is made by taking the execution subject as an example of a virtual switch.
  • the virtual switch can generate a service message, the message body of 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, and the The first port identifier included in the first LLDP PDU is a permanent equipment identifier (PEI) or an international mobile equipment identity (IMEI) of the first industrial equipment, and the first LLDP PDU is used for An alias of the first industrial device is determined. Then, the virtual switch may send the service message to the first industrial device.
  • PEI permanent equipment identifier
  • IMEI international mobile equipment identity
  • the virtual switch generates a service message containing LLDP PDU, and sends the service message to a new industrial device, so that the new industrial device determines its own alias based on the LLDP PDU in the service message.
  • New industrial equipment can determine the unique alias based on the existing LLDP protocol specification and existing naming rules, and use the permanent equipment identity code PEI or the international mobile equipment identity code IMEI as the port identification, so as to realize the new IO equipment to join the wireless group network architecture.
  • a communication method is provided, and the execution body of the method may be the first industrial equipment, or may be a component applied to the first industrial equipment, such as a chip, a processor, and the like.
  • the first industrial device receives a service message from the virtual switch, the service message includes a first link layer discovery protocol packet data unit LLDP PDU, and the first device identified in the first LLDP PDU is 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 equipment, and the first LLDP PDU is used to determine the alias of the first industrial equipment.
  • the first industrial device determines an alias of the first industrial device based on the first device identifier and the first port identifier.
  • the alias is the International Mobile Equipment Identity IMEI of the new IO device.
  • the virtual switch generates a service message containing LLDP PDU, and sends the service message to a new industrial device, so that the new industrial device determines its own alias based on the LLDP PDU in the service message.
  • New industrial equipment can determine the unique alias based on the existing LLDP protocol specification and existing naming rules, and use the permanent equipment identity code PEI or the international mobile equipment identity code IMEI as the port identification, so as to realize the new IO equipment to join the wireless group network architecture.
  • the first industrial device may also receive a discovery message, where the discovery message includes an alias of the first industrial device, and the discovery message is used to indicate to acquire the Related parameter information. Then, the first industrial device may send a response message, where the response message includes relevant parameter information of the first industrial device. Next, the first industrial equipment may receive first parameter information, the first parameter information is relevant parameter information of the old industrial equipment replaced by the first industrial equipment, and the relevant parameter information does not include the Media Access Control Address MAC for legacy industrial equipment. In order to realize the non-destructive replacement of the business.
  • a communication device in a sixth aspect, has a function of realizing any one of the above aspects and any possible implementation of any one aspect. These functions may be implemented by hardware, or may be implemented by executing corresponding software through hardware.
  • the hardware or software includes one or more functional modules corresponding to the above functions.
  • a communication device including a processor, and optionally, a memory; the processor is coupled to the memory; the memory is used to store computer programs or instructions; the processor, For executing part or all of the computer programs or instructions in the memory, when the part or all of the computer programs or instructions are executed, for implementing any of the above aspects and any possible implementation method of any aspect function.
  • the device may further include a transceiver, configured to send a signal processed by the processor, or receive a signal input to the processor.
  • the transceiver may perform a sending action or a receiving action in any aspect and any possible implementation of any aspect.
  • the present application provides a system-on-a-chip, which includes one or more processors (also referred to as processing circuits), and the electrical coupling between the processors and memories (also referred to as storage media)
  • the memory may or may not be located in the chip system; the memory is used to store computer programs or instructions; the processor is used to execute part or all of the memory Computer programs or instructions, when part or all of the computer programs or instructions are executed, are used to realize the functions in any of the above-mentioned aspects and any possible implementation methods of any of the aspects.
  • the chip system may further include an input and output interface (also referred to as a communication interface), the input and output interface is used to output the signal processed by the processor, or receive an input to the signal 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.
  • system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • a computer-readable storage medium for storing a computer program, and the computer program includes instructions for realizing the functions in any aspect and any possible implementation of any aspect.
  • a computer-readable storage medium for storing a computer program.
  • the computer program When the computer program is executed by a computer, the computer can execute any one of the above-mentioned aspects and any possible implementation method of any one of the aspects.
  • a computer program product comprising: computer program code, when the computer program code is run on a computer, the computer is made to perform any of the above-mentioned aspects and any possibility of any aspect. method in the implementation.
  • a communication system in an eleventh aspect, includes a virtual switch and a first virtual port in any possible implementation method of the above-mentioned first to third aspects and any one of the first to third aspects equipment and primary industrial equipment.
  • the communication system includes the virtual switch and the first industrial device in the method for implementing the fourth aspect to the fifth aspect and any possible implementation method of the fourth aspect to the fifth aspect.
  • the virtual switch is configured to generate first information, where the first information is used to indicate a first device identifier and a first port identifier, the first device identifier is an identifier of the virtual switch, and the first a port identification includes at least one virtual port device identification;
  • the first virtual port device is configured to receive the first information from the virtual switch, and send an LLDP message to the first industrial device, the LLDP message includes the first LLDP PDU, and the first LLDP PDU in the first LLDP PDU
  • the device identifier is the 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 the alias of the first industrial device.
  • the first industrial device is configured to receive the LLDP packet from the first virtual port device, and determine an alias of the first industrial device based on the first device identifier and the first port identifier.
  • the first information is a service message; a message body of the service message includes the first LLDP PDU.
  • the first information further includes first indication information, and the first indication information is used to indicate transparent transmission of the first LLDP PDU.
  • 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.
  • 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.
  • the first virtual port device is configured to receive a discovery message from the control device and trigger generation of the first LLDP PDU, where the discovery message is used to instruct acquisition of the first industrial device information.
  • the first virtual port device is further configured to send the discovery message to the first industrial device after sending the LLDP message to the first industrial device, and the discovery message is used to indicate Obtaining the relevant parameter information of the first industrial equipment; and receiving a response message from the first industrial equipment, the response message including the relevant parameter information of the first industrial equipment; and sending the A response message, where the response message includes relevant parameter information of the first industrial equipment;
  • the first industrial device is further configured to receive a discovery message, the discovery message includes an alias of the first industrial device, and the discovery message is used to instruct to obtain the related information of the first industrial device.
  • Parameter information sending a response message, the response message including relevant parameter information of the first industrial equipment; and receiving first parameter information, the first parameter information is the old industrial equipment replaced by the first industrial equipment
  • the related parameter information does not include the media access control address MAC of the old industrial equipment.
  • Figure 1a is a schematic diagram of a LLDP message format provided in the embodiment of the present application.
  • Figure 1b is a schematic diagram of a LLDPDU format provided in the embodiment of the present application.
  • FIG. 2a is a schematic structural diagram of a communication system provided in an embodiment of the present application.
  • FIG. 2b is a schematic structural diagram of a communication system provided in an embodiment of the present application.
  • FIG. 2c is a schematic structural diagram of a communication system provided in an embodiment of the present application.
  • FIG. 3a is a schematic diagram of a communication system architecture provided in an embodiment of the present application.
  • Fig. 3b is a flow chart of a communication method provided in the embodiment of the present application.
  • FIG. 4 is a flowchart of a communication method provided in an embodiment of the present application.
  • FIG. 5 is a flowchart of a communication method provided in an embodiment of the present application.
  • FIG. 6 is a flowchart of a communication method provided in an embodiment of the present application.
  • FIG. 7 is a flowchart of a communication method provided in an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a communication system architecture provided in an embodiment of the present application.
  • FIG. 9 is a flowchart of a communication method provided in an embodiment of the present application.
  • FIG. 10 is a flowchart of a communication method provided in an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a communication system architecture provided in an embodiment of the present application.
  • FIG. 12 is a flow chart of a communication method provided in an embodiment of the present application.
  • FIG. 13 is a structural diagram of a communication device provided in an embodiment of the present application.
  • FIG. 14 is a structural diagram of a communication device provided in an embodiment of the present application.
  • link layer discovery protocol (link layer discovery protocol, LLDP):
  • LLDP is defined in 802.1ab, which is a Layer 2 protocol.
  • LLDP provides a standard link layer discovery method, which can organize the main capabilities, management addresses, device identifiers, interface identifiers and other information of the local node into different type/length/value (type/length/value, TLV) , encapsulated in a link layer discovery protocol packet data unit (link layer discovery protocol packet data unit, LLDP PDU, which can also be referred to as LLDPDU for short) and published to the nodes directly connected to itself.
  • LLDP PDU link layer discovery protocol packet data unit
  • the directly connected nodes save it in the form of a standard management information base (MIB) for the network management system to query and judge the communication status of the link.
  • MIB management information base
  • LLDP is a protocol for information notification and acquisition.
  • the information sent by LLDP usually does not require confirmation, and cannot be used to request certain information.
  • LLDP is a one-way protocol. There is only active notification, and no confirmation is required. Inquiry and request are not possible.
  • FIG. 1a A message encapsulated with an LLDPDU is called an LLDP message, as shown in Figure 1a, which provides a schematic diagram of an LLDP message format, where:
  • Destination MAC address Indicates the destination media access control address (media access control address, MAC) address, which is a fixed multicast MAC address 0x0180-C200-000E. MAC address is also called physical address and hardware address. It is burned into the network card when it is produced by the manufacturer and cannot be modified.
  • media access control address media access control address, MAC
  • MAC address is also called physical address and hardware address. It is burned into the network card when it is produced by the manufacturer and cannot be modified.
  • Source MAC address Indicates the source MAC address, which is the port MAC address or device bridge MAC address. If there is a port address, use the port MAC address, otherwise use the device bridge MAC address.
  • Type Indicates the message type, usually 0x88CC.
  • Data which is LLDPDU.
  • FCS frame check sequence (frame check sequence, FCS), let the network card or interface receiving the frame determine whether an error has occurred.
  • LLDPDU is a data unit encapsulated in the data part of an LLDP packet.
  • the device Before composing an LLDPDU, the device first encapsulates the local information into a TLV format, and then combines several TLVs into an LLDPDU and encapsulates it in the data part of the LLDP packet.
  • a schematic diagram of the LLDPDU format is provided.
  • each LLDPDU can carry up to 28 kinds of TLVs, among which Chasis ID TLV, port identification Port ID TLV, Time To Live TTL TLV and End TLV are required. carried, and the remaining TLVs are optional.
  • Chassis ID TLV used to indicate the chassis ID of the sender of the LLDPDU, is actually used to identify the device, which is called the device identifier in this application.
  • Port ID TLV used to indicate the port of the device sending the LLDPDU.
  • TTL TLV used to indicate how long the information is valid for.
  • End TLV used to indicate the end of LLDPDU.
  • DCP Discovery and basic configuration protocol
  • the content of the configuration is mainly network parameters and auxiliary functions, including IP address, subnet mask, gateway, device name, flashing recognition, etc.
  • the device name is similar to the domain name of the Ethernet. In comparison, the domain name is internationally unique, and the device name only needs to be unique in the control network; the domain name is resolved to an IP address through DNS, and the device name is bound to the MAC address. , all for better memory and use of communication networks.
  • Set (Set) response After the sender sends the Set (Set) request frame, the receiver returns the corresponding data information in the Set (Set) response.
  • Identify (Identify) request mainly used to scan PN devices in the network, the frame only needs the source MAC address, the target address is generally broadcast MAC, all devices (including the controller) that receive the frame will respond, Then you can know the device information in the network and prepare for the subsequent connection establishment.
  • Identify (Identify) response Scan all devices, and the device will respond to all data, including IP, device name, manufacturer information, MAC address, device alias, etc.
  • IO devices that support PROFINET's "Device replacement without removable media/PG” function do not need to insert removable media (such as MMC) or assign device names to them during the replacement process.
  • the device name of the replaced new IO device is assigned by the IO controller (such as PLC), not by the removable medium or PG.
  • the IO controller of the replaced 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.
  • the user plane function (UPF) network element is responsible for forwarding and receiving user data in the terminal device. It can receive user data from the data network and transmit it 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 for terminal equipment in user plane network elements are managed and controlled by SMF network elements.
  • the user plane network element may be a user plane function (user plane function, UPF) network element.
  • UPF user plane function
  • the user plane network element may still be a UPF network element, or may have other names, which are not limited in this application.
  • the UPF may be deployed in an industrial park as a user plane server in the industrial park.
  • Radio access network equipment is a device that provides wireless communication functions for terminal equipment.
  • the RAN equipment in this application includes but is not limited to: next-generation base stations (g nodeB, gNB) in 5G , evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), node B (node B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseBand unit, BBU), transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP ), Mobile Switching Center, etc.
  • next-generation base stations g nodeB, gNB
  • eNB evolved node B
  • RNC radio network controller
  • node B node B
  • base station controller base station controller
  • BTS base transceiver station
  • home base station for example,
  • the names of devices with base station functions may be different.
  • RAN Fifth Generation
  • gNB Fifth Generation NodeB
  • eNB evolved Node B
  • 3rd generation, 3G 3rd generation
  • system architecture of the method provided by the embodiments of the present application will be briefly described below. It can be understood that the system architecture described in the embodiments of the present application is for more clearly illustrating the technical solutions of the embodiments of the present application, and does not constitute a limitation on the technical solutions provided by the embodiments of the present application.
  • 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 the traditional mobile communication system (i.e. the ground communication system).
  • Communication systems such as: wireless local area network (wireless local area network, WLAN) communication system, wireless fidelity (wireless fidelity, WiFi) system, long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) ) system, LTE time division duplex (time division duplex, TDD), fifth generation (5th generation, 5G) system or new radio (new radio, NR), sixth generation (6th generation, 6G) system, and other future Communication systems, etc., also support communication systems that integrate multiple wireless technologies. For example, they can also be applied to non-terrestrial networks such as unmanned aerial vehicles, satellite communication systems, and high altitude platform station (HAPS) communications.
  • NTN is a system that integrates terrestrial mobile communication networks.
  • the automatic control system IACS is composed of many electronic and controller components, which are widely used in various industrial industries such as chemical industry, paper industry, power plant, oil and gas refining, and telecommunication industry.
  • the controller takes up a lot of space, and the loop flow is not easy to modify and maintain.
  • the appearance of the programmable logic controller (PLC) can solve these problems.
  • FIG. 2a it provides a networking structure of the industrial automation system after the PLC is introduced into the automation control system on a large scale: a main control PLC and other input and output IO devices and other nodes are connected through a switch (Switch, SW) .
  • a management node (such as PLC) that can implement management is set on the northbound side of the switch.
  • the communication between different nodes is connected by wires, such as copper wires, twisted pair wires, and optical fibers.
  • the IO device fails or other reasons, the IO device needs to be replaced. Combining with what is shown in FIG. 1a, taking the replacement of the IO2 device with a new IO device as an example, the process of replacing the IO device is introduced.
  • nodes such as IO devices and PLCs can exchange their own information with the switch, such as device names and port numbers.
  • Table 1 below introduces the information corresponding to each device and its directly connected nodes according to the link layer discovery protocol LLDP.
  • the port of the local device is connected to the port of the peer device.
  • the alias of the peer device is: port ID of the local device.ID of the local device.
  • Port 01 of Switch is connected to Port 01 of PLC, then for PLC, the alias of Switch is Port01.PLC; for Switch, the alias of PLC is Port01.Switch;
  • 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;
  • 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.
  • the new IO device replaces the IO2 device and is connected to the SW (the port of the SW connected to the new IO device is the port of the SW connected to the IO2 device), there is no device name or alias in the initial setting of the new IO device.
  • the SW and the new IO device send LLDP packets to each other to inform themselves of their own information.
  • SW sends an LLDP packet to a new IO device, and the setting identifier in the LLDPPDU is SW, and the port identifier is Port03 of SW, then the new IO device can set its own alias as Port03.Switch.
  • the PLC discovers the alias of the new IO device through the discovery and configuration protocol DCP, it further sets other parameters for the new IO device.
  • the other parameters include the device name of the new IO device and service parameters.
  • the device name of the new IO device is the device name of the IO device replaced by the new IO device, such as IO2.
  • the alias of Switch is Port01.IO2.
  • Wireless communication technology represented by 5G has gradually become a new medium for industrial site network connection.
  • Wireless communication technology can realize wireless access to existing PLC, IO equipment and other nodes, realizing a more flexible networking mode of industrial equipment.
  • a possible networking structure of an industrial automation system after introducing a wireless communication system is provided.
  • a wireless communication network such as a 5G network
  • switches and IO devices For example, one or more UPF network elements, one or more RAN network elements, etc. are deployed between the switch and the IO device.
  • the IO device can be directly connected to the RAN.
  • the IO device can be directly connected to the RAN.
  • CPE customer premise equipment
  • the CPE is a A mobile signal access device that receives mobile signals and forwards them with wireless WIFI signals. It is equivalent to providing a wireless network access network port for IO devices.
  • One CPE can connect 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. There is usually a physical connection between the IO device and the CPE.
  • the CPE has only one physical port, and a CPE can only be physically connected to one IO device.
  • a SW can be deployed between the CPE and the IO devices, and the SW and the CPE are physically connected.
  • One SW can connect multiple IO devices, and one IO device is connected to one SW.
  • the aliases of UPF and CPE are: RAN port ID.
  • RAN device ID the aliases of the CPE, and the IO device are: the port identifier of the CPE, and the device identifier of the CPE.
  • the switch cannot forward LLDP packets across domains, so the switch SW cannot configure aliases for new IO devices based on LLDP.
  • the management node (such as PLC) maintains the connection relationship between the CPE and the IO device, and the management node can obtain the information between each device (or called a node) in a normal network. connection relationship.
  • the CPE sends an LLDP message to the IO device, wherein the device identifier included in the LLDP PDU is the identifier of the CPE, and the port identifier is the identifier of a certain port in the CPE.
  • the alias of the new IO device is: ID of the port in the CPE.CPE device ID.
  • the management node After the management node discovers the alias of the new IO device through the discovery and configuration protocol DCP, it can further set other parameters for the new IO device, such as the device name and service parameters of the new IO device.
  • 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.
  • most CPEs currently do not support sending LLDP packets on their own initiative.
  • 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 packets across domains. New IO device configuration alias.
  • the present application proposes a variety of technical solutions to configure an alias for a new IO device in a wireless networking, so as to enable the new IO device to join the wireless networking architecture.
  • the solution of this application can be applied to various scenarios and has good compatibility.
  • the communication ports between network elements are usually logical ports, not physical ports. Logical ports cannot be distinguished, and a point can be found as a so-called "physical port”.
  • a virtual port device accessed by an industrial device is regarded as a so-called "physical port”.
  • the virtual switch is similar to the switch SW in Table 1; the virtual port device is used as a 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 device can be determined based on the device name of the virtual switch and the device name of the virtual port device.
  • the virtual switch in this application is, for example, a UPF, a mobile edge computing (mobile edge computing, MEC) node, a gateway (gateway, GW) and the like.
  • Virtual port devices such as switches, routers, terminals, CPE, bridges and other gateway devices that enable industrial devices to access.
  • Industrial equipment such as IO equipment, etc.
  • the equipment marked with " ⁇ " in the embodiment is the equipment that needs to be replaced, for example, the second industrial equipment in Figure 3a, Figure 3b, Figure 8, Figure 11, and Figure 12 is replaced by the first industrial equipment.
  • the virtual switch is connected to one or more virtual port devices through the RAN.
  • the first virtual port device is any virtual port device in the network, and each virtual port device is connected to a Industrial equipment, an industrial equipment can be connected to one or more virtual port equipment.
  • 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.
  • the second industrial equipment fails or other reasons, and the first industrial equipment is used to replace the second industrial equipment. After the replacement, the first industrial device maintains the same connection relationship as the second industrial device, and the alias of the industrial device will not change.
  • the connection relationship involved in this embodiment may be a wireless connection such as a 5G connection, a WiFi connection, or a wired connection such as a copper wire, an optical fiber, or a twisted pair.
  • Step 301 The virtual switch (for example, VSW) sends first information to a first virtual port device (for example, VPORT), and correspondingly, the first virtual port device receives the first information from the virtual switch.
  • VSW virtual switch
  • VPORT virtual port device
  • 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 the alias of the industrial device.
  • the first device identifier is an identifier of the virtual switch
  • the first port identifier includes an identifier of at least one virtual port device.
  • the identifier of the virtual port device may be an International Mobile Equipment Identity (IMEI) of the virtual port device.
  • IMEI International Mobile Equipment Identity
  • the first LLDP PDU may be generated by the virtual switch, or the first LLDP PDU may be generated by the first virtual port device.
  • the virtual switch sends the first information to the first virtual port device through the RAN.
  • Step 302 the first virtual port device sends the LLDP packet to the first industrial device, and correspondingly, the first industrial device receives the LLDP packet from the first virtual port device.
  • the LLDP packet 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 an identifier of at least one virtual port device
  • the first LLDP PDU is used to determine The alias of the first industrial device.
  • the virtual switch generates the first LLDP PDU, and sends the first LLDP PDU to the first virtual port device.
  • the first information is a service message; a 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, obtain the first LLDP PDU, and encapsulate the first LLDP PDU into an LLDP message. For the virtual port device, this method only needs to analyze the transparent transmission, and the implementation is relatively simple.
  • the virtual switch may also send first indication information to the first virtual port device.
  • the first virtual port device receives the first indication information from the virtual switch, and the first indication information is used to indicate transparent transmission of the first indication information.
  • 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, so as to avoid confusion with other messages and fail to transparently transmit the first LLDP PDU in the service message.
  • the virtual switch and the first virtual port device can agree with each other, or the agreement stipulates that the virtual switch will generate the first LLDP PDU, and the first virtual port device will transparently transmit the first LLDP PDU.
  • the port device sends first indication information.
  • the first LLDP PDU is generated by the first virtual port device.
  • the first information indicates that the identity of the first device is an identity of a specific virtual switch, such as VSW1 or VSW2 or other VSWs.
  • the first indication information may also indicate that the first port identifier is an identifier of a specific virtual port device, for example, VPORT1 or VPORT2 or other VPORTs.
  • 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 packet.
  • a virtual port device after storing the port ID and device ID, it can send LLDP packets to the industrial device connected to the virtual port device at any time without triggering the virtual switch, thus determining the alias of the new industrial device
  • the effectiveness is higher, and for other control devices, this process is imperceptible.
  • the port identifier is the identifier of a virtual port device connected to the industrial device.
  • the virtual switch does not need to indicate the first virtual port device to the first virtual port device.
  • the port identifier, or the virtual switch indicates to the first virtual port device that the first port identifier is the first virtual port device identifier itself.
  • the virtual port device is connected to the RAN, and the virtual switch (such as UPF) changes and is invisible to the virtual port device.
  • the virtual port device does not save the identity of the virtual switch it is connected to, but the same reason , if the virtual port device can save 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.
  • the virtual switch may also send second indication information to the first virtual port device.
  • the first virtual port device receives the second indication information from the virtual switch, and the second indication information is used to indicate that the first virtual port device receives the second indication information from the virtual switch.
  • Virtual port devices generate LLDP PDUs.
  • the virtual port device can generate LLDP PDUs in a timely and accurate manner, so as to prevent the virtual port device from confusing the first indication information with other received information, and does not know how to deal with it.
  • the virtual switch and the first virtual port device may agree with each other, or the agreement stipulates that the first virtual port device generates the first LLDP PDU, so that the virtual switch does not need to send the second indication information to the first virtual port device.
  • the first virtual port device may trigger the generation of the first LLDP PDU when receiving the second indication information from the virtual switch.
  • the first virtual port device may receive a discovery message from the control device, triggering generation of the first LLDP PDU, and the discovery message is used to instruct acquisition of the first industrial device information.
  • the discovery message is sent by the virtual switch to the first virtual port device after the control device sends it to the virtual switch.
  • the control device does not send a discovery message to the industrial device, the replacement event of the industrial device usually does not occur. If the virtual port device sends an LLDP message to the industrial device during this period, this process will waste signaling. Therefore, when the first virtual port device receives the discovery message from the control device, it can trigger the generation of the first LLDP PDU, and sending at this time will not cause signaling waste.
  • Step 303 The first industrial device determines the alias of the first industrial device based on the first device identifier and the first port identifier in the first LLDP PDU.
  • the first industrial device determines its own alias as: first port identifier.
  • the identifier of the first device that is, the identifier of the at least one virtual port device (VPORT).
  • VPORT virtual port device
  • the identifier of the virtual switch for example, VSW.
  • the alias is just an indication, and it can also be other forms of expression, as long as each device in the network agrees with each other.
  • the device ID may be in front, and the port ID may be in the back, for example, VSW.VPORT.
  • other characters may be used between the port identifier and the device identifier, such as "-", "_" and so on.
  • the virtual switch indicates the port identifier and the device identifier to the virtual port device, the port identifier is the virtual port device identifier, and the device identifier is the virtual switch identifier; the virtual port device determines the LLDP packet based on the indication of the virtual switch, and sends the LLDP The message is sent to the new industrial device so that the new industrial device can determine its own alias based on the LLDP PDU in the LLDP message.
  • New industrial equipment can determine a unique alias based on the existing LLDP protocol specification and existing naming rules.
  • the control device may periodically obtain relevant parameter information of the industrial device based on the device identifier of the industrial device, so as to obtain the latest network relationship. Due to a 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 may cause a timeout and fail 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 own relevant parameter information to the control device.
  • the control device can also inquire about 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 MAC address MAC of the second industrial device), so that the first industrial device can Update the parameter information so as to realize the non-destructive replacement of the service.
  • the interaction between the control device and the industrial device needs to go through the virtual port device.
  • the first virtual port device and the first industrial device perform the following process:
  • the first virtual port device sends a discovery message to the first industrial device, and correspondingly, the first industrial device receives the discovery message; the discovery message is used to instruct acquisition of relevant parameter information of the first industrial device.
  • the discovery message includes the alias of the first industrial device, eg VSW.VPORT.
  • the discovery message may be, for example, a Discovery and Configuration Protocol Identify (DCP Identify) request.
  • the first industrial device sends a response message to the discovery message, and correspondingly, the first virtual port device receives the response message from the first industrial device, and the response message includes the related information of the first industrial device.
  • Parameter information for example, the response message may be, for example, a discovery and configuration protocol identification (DCP Identify) response.
  • DCP Identify discovery and configuration protocol identification
  • the discovery message sent by the first virtual port device to the first industrial device is from the control device, then the first virtual port device may also send the response message to the control device, and the response message includes the The relevant parameter information of the first industrial equipment.
  • the control device may send first parameter information to the first industrial device, and correspondingly, the first industrial device receives the first parameter information, and the first parameter information is set by the first industrial device. Relevant parameter information of the second industrial equipment to be replaced, where the medium access control address MAC of the second industrial equipment is not included in the relevant parameter information.
  • FIG. 4 a schematic diagram of a specific communication process is introduced.
  • one CPE is connected to one IO, and one IO is connected to one CPE.
  • UPF generates LLDP PDUs, and CPE supports transparent transmission of LLDP PDUs constructed by UPF. Include the following steps:
  • Step 400 The industrial field enable service (IFES) functional entity can obtain the network topology relationship under normal operation.
  • IIFES industrial field enable service
  • IFES sends a discovery message (such as a DCP Identify all request) to devices on the entire network in a multicast manner, and the device that receives the discovery message can feed back its device name, alias and other parameter information to IFES.
  • a discovery message such as a DCP Identify all request
  • IFES can be understood as an APP, which can be deployed on the UPF platform or separated from the UPF deployment platform.
  • the IO2 device is connected to CPE3, and CPE3 is connected to UPF1 as an example.
  • IFES can obtain the device name of the IO2 device: IO2, and the alias of the IO2 device: CPE3.UPF1.
  • Step 401 UPF1 generates a service message, UPF1 sends the service message to CPE3 through RAN, and CPE3 receives the service message from UPF1 accordingly.
  • 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
  • the port identifier included in the LLDP PDU is the identifier of the CPE3.
  • Table 2 the content of an LLDP PDU constructed by UPF1 is introduced.
  • the service message generated by UPF1 can be used to repackage the LLDP PDU, and the LLDP PDU in the prior art can only be transmitted between two adjacent nodes.
  • RAN will also send LLDP message to CPE, and LLDP message also includes LLDP PDU.
  • UPF1 After UPF1 determines that the IO2 device is faulty or replaced, it can trigger the generation of a service message. For example, when UPF1 often fails to receive a response when sending information to the IO2 device based on the device name of the IO2 device, it can be determined that the IO2 device needs to be replaced. It can also be operated manually to tell UPF1 that there is a new IO device to replace the IO2 device. This application does not limit the process of how UPF1 determines that the IO2 device needs to be replaced. Usually, the functions of the new IO device and the replaced IO2 device are basically the same, even the models are the same, which can realize the non-destructive replacement of the business.
  • CPE3 sends a response message to UPF1 to indicate receipt of the service message.
  • UPF1 is connected to the CPE directly or through other network elements.
  • Step 402 CPE3 analyzes the service message, obtains the LLDP PDU, and generates an LLDP message, and the message body of the LLDP message is the LLDP PDU obtained through analysis.
  • CPE3 converts service messages into layer 2 standard LLDP PDUs.
  • the device identifier included in the LLDP PDU is the identifier of the UPF1, and the included port identifier is the identifier of the CPE3.
  • Step 403 CPE3 sends an LLDP message to the new IO device (the IO2 device has been replaced by the new IO device), and the new IO device receives the LLDP message from CPE3, and the LLDP message includes the LLDP PDU.
  • CPE3 transparently transmits (forwards) the LLDP PDU to the new IO device.
  • Step 404 The new IO device determines the alias of the new IO device based on the LLDP PDU in the LLDP message.
  • the new IO device determines an alias name of the new IO device: the identifier of the CPE3.the identifier of the UPF1.
  • the alias is just a hint, and it can also be in other forms, as long as the devices in the network agree with each other.
  • the device identifier may also be preceded by the port name identifier, for example, the identifier of UPF1.the identifier of CPE3.
  • other characters may be used between the port identifier and the device identifier, such as "-", "_" and so on.
  • 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 certain port in the CPE3.
  • the device ID included in LLDP PDU is the ID of UPF1
  • the port ID is CPE3 ID.
  • UPF1 sends the LLDP PDU as the message body of the service message to CPE3, and CPE3 transparently transmits the LLDP PDU to the new server.
  • the device ID included in the LLDP PDU received by the new IO device is the ID of UPF1
  • the port ID is the ID of CPE3
  • the alias determined by the new IO device is the ID of UPF1.
  • step 405a PLC sends a discovery message to UPF1, and UPF1 receives the discovery message from PLC accordingly.
  • Discovery messages are used to obtain relevant parameter information of industrial equipment.
  • the discovery message may be sent only for the IO2 device, for example, the discovery message includes the device name of the IO2 device.
  • the discovery message may also be sent for devices on the entire network, and the discovery message may be a multicast message.
  • the discovery message may be, for example, a DCP identify request.
  • step 405b UPF1 sends a discovery message from PLC to IFES, and IFES receives the discovery message from UPF1.
  • Step 405c IFES sends a discovery message to all network devices (mainly referring to industrial devices), but does not receive a response from the IO2 device after timeout, at this time it can be determined that IO2 is faulty.
  • IFES can send discovery messages in multicast or unicast mode.
  • the discovery message may come from UPF1, and the IFES may replace the PLC to construct a new and old device parameter replacement process, and the IFES itself decides to send the discovery message.
  • step 405a and step 405b may be omitted.
  • Step 405a and step 405b are not omitted when constructing the new and old device parameter replacement process by the PLC.
  • Step 406 The IFES can determine the alias of the IO2 device according to the pre-saved network topology relationship, and send a discovery message to the IO2 device according to the alias of the IO2 device (for example, CPE3 ID.UPF1 ID). At this time, the new IO device receives the discovery message.
  • the alias of the IO2 device for example, CPE3 ID.UPF1 ID.
  • a discovery message is, for example, a DCP Identify request.
  • IFES can send discovery messages in multicast or unicast mode.
  • the alias of the IO1 device is CPE2.UPF1; the aliases 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 for port1.UPF1.
  • the alias of UPF1 is port1.IO1;
  • the alias of UPF1 is port1.IO2;
  • UPF1 For PLC, the alias of UPF1 is CPE1.UPF1 or port1.PLC.
  • Step 407 The new IO device sends a response message to the IFES, and the response message includes relevant parameter information of the new IO device.
  • the reply message is, for example, a DCP Identify reply.
  • the response message may include success indication information, for example, carrying 0x00 in a header (header), indicating success.
  • the relevant parameter information of the new IO device includes the MAC address of the new IO device, the site name (NameOfStation), the device role (Device Role), the device vendor (Device Vendor), the device ID (Device ID), the device options (Device Options), IP Parameter (IP Parameter), DHCP Parameter (DHCParameter), Manufacturer Specific Parameter (Manufacturer Specific Parameter), Alias Name (AliasName).
  • Step 408 IFES queries the stored original configuration parameters of the IO2 device.
  • Step 409 The IFES configures the old parameters in the original configuration parameters except the MAC to the new IO device.
  • the device name of the IO2 device For example, the device name of the IO2 device, the site name (NameOfStation), the device role (Device Role), the device vendor (Device Vendor), the device ID (Device ID), the device option (Device Options), the IP parameter (IP Parameter), DHCP Parameter (DHCParameter), Manufacturer Specific Parameter (Manufacturer Specific Parameter).
  • IFES sends a DCP Set request to the new IO device, including the old parameters in the original configuration parameters except MAC.
  • the parameter source is the historical storage of industrial topology discovery.
  • Step 410 The new IO device sends a response (such as a DCP Set response) to the IFES, indicating that the DCP Set request has been received.
  • a response such as a DCP Set response
  • the new IO device has updated its own parameters according to the old parameters.
  • step 411a the IFES sends a response message to UPF1, and the response message includes the MAC address of the new IO address.
  • the reply message is, for example, a DCP Identify reply.
  • step 411b UPF1 sends the reply message from IFES to PLC.
  • FIG. 5 a schematic diagram of a specific communication process is introduced.
  • one CPE is connected to one IO
  • one IO is connected to multiple CPEs
  • UPF generates LLDP PDUs.
  • the difference between the example in FIG. 5 and the example in FIG. 4 includes: in the example in FIG. 4 , one IO is connected to one CPE, and in the example in FIG. 5 , one IO is connected to two CPEs. Include the following steps:
  • Step 500 The industrial field enabling service IFES functional entity can obtain the network topology relationship under normal operation.
  • the IO2 device is connected to CPE3 and CPE4, and both CPE3 and CPE4 are connected to UPF1.
  • IFES can obtain the device name of the IO2 device: IO2, and the alias name of the IO2 device: CPE3&CPE4.UPF1.
  • step 400 refers to the introduction of step 400 .
  • Step 501a UPF1 generates a service message, UPF1 sends the service message to CPE3 through RAN, and CPE3 receives the service message from UPF1 accordingly.
  • Step 501b UPF1 generates a service message, UPF1 sends the service message to CPE4 through RAN, and CPE4 receives the service message from UPF1 accordingly.
  • 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
  • the port identifier included in the LLDP PDU is the identifier of the CPE3 and the identifier of the UPF1.
  • the above CPE4 logo It is ensured that the port identifiers carried in the LLDPPDUs sent by each connection of the dual connection are consistent, thereby ensuring that the two LLDPPDUs received by the first industrial device are consistent.
  • Step 501a and step 501b are similar to step 401, except that: the port ID in step 401 is the ID of CPE3, and the port ID in step 501a and step 501b is the ID of CPE3 and CPE4.
  • the port ID in step 401 is the ID of CPE3
  • CPE4 the port ID in step 501a and step 501b
  • UPF1 may send a service message to at least one CPE among multiple CPEs connected to the IO2 device, that is, step 501a and step 501b may both be performed, or one of them may be performed.
  • Step 502a CPE3 analyzes the service message, obtains the LLDP PDU, and generates an LLDP message, and the message body of the LLDP message is the LLDP PDU obtained through analysis.
  • Step 502b CPE4 analyzes the service message, obtains the LLDP PDU, and generates an LLDP message, and the message body of the LLDP message is the LLDP PDU obtained through analysis.
  • step 502a and step 502b may be executed, or one of them may be executed.
  • the LLDP PDUs in step 502a and step 502b are the same. For other technical details, refer to the introduction of step 402 .
  • Step 503a CPE3 sends an LLDP message to the new IO device (the IO2 device has been replaced by the new IO device), and the new IO device receives the LLDP message from CPE3, and the LLDP message includes the LLDP PDU.
  • Step 503b CPE4 sends an LLDP packet to the new IO device (the IO2 device has been replaced by the new IO device), and the new IO device receives the LLDP packet from the CPE4, and the LLDP packet includes the LLDP PDU.
  • step 503a and step 503b may be executed, or one of them may be executed.
  • the LLDP PDUs in step 503a and step 503b are the same. For other technical details, refer to the introduction of step 403 .
  • Step 504 The new IO device determines the alias of the new IO device based on the LLDP PDU in the LLDP message.
  • 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.
  • the alias of the new IO device is: the identifier of the CPE3&the identifier of the CPE4.the identifier of the UPF1.
  • step 505a PLC sends a discovery message to UPF1, and UPF1 receives the discovery message from PLC accordingly.
  • Step 505a is the same as step 405a and will not be repeated here.
  • step 505b UP1F sends the discovery message from PLC to IFES, and IFES receives the discovery message from UPF1.
  • Step 505b is the same as step 405b and will not be repeated here.
  • Step 505c IFES sends a discovery message to all network devices (mainly refers to industrial devices), but does not receive a response from IO2 device after timeout, then it can be determined that IO2 is faulty.
  • Step 505c is the same as step 405c, and will not be repeated here.
  • Step 506 The IFES can determine the alias of the IO2 device according to the pre-saved network topology relationship, and send a discovery message to the IO2 device according to the alias of the IO2 device (for example, CPE3 ID&CPE4 ID.UPF ID). At this time, the new IO device receives the discovery message.
  • the alias of the IO2 device for example, CPE3 ID&CPE4 ID.UPF ID.
  • the alias of the IO1 device is CPE2.UPF1; the aliases 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 for port1.UPF1.
  • the alias of UPF1 is port1.IO1;
  • the alias of UPF1 is port1.IO2;
  • UPF1 For PLC, the alias of UPF1 is CPE1.UPF1 or port1.PLC.
  • step 406 refers to the introduction of step 406 .
  • Step 507 The new IO device sends a response message to the IFES, and the response message includes relevant parameter information of the new IO device.
  • the reply message is, for example, a DCP Identify reply.
  • the relevant parameter information of the new IO device includes the MAC address of the new IO device.
  • Step 507 is the same as step 407 and will not be repeated here.
  • Step 508 IFES queries the stored original configuration parameters of the IO2 device.
  • Step 508 is the same as step 407 and will not be repeated here.
  • Step 509 The IFES configures the old parameters in the original configuration parameters except the MAC to the new IO device.
  • the device name of the IO2 device to try to ensure that the communication is not interrupted.
  • IFES sends a DCP Set request to the new IO device, including the old parameters in the original configuration parameters except MAC.
  • Step 509 is the same as step 409 and will not be repeated here.
  • Step 510 The new IO device sends a response (such as a DCP Set response) to the IFES, indicating that the DCP Set request has been received.
  • a response such as a DCP Set response
  • Step 510 is the same as step 410 and will not be repeated here.
  • step 511a the IFES sends a response message to the UPF, the response message includes the MAC address of the new IO address, and other old parameters except the MAC remain unchanged.
  • the reply message is, for example, a DCP Identify reply.
  • Step 511a is the same as step 411a and will not be repeated here.
  • step 411b the UPF sends the response message from the IFES to the PLC.
  • Step 511b is the same as step 411b and will not be repeated here.
  • FIG. 6 a schematic diagram of a specific communication process is provided.
  • one CPE is connected to one IO
  • one IO is connected to one CPE
  • the CPE generates an LLDP PDU.
  • the difference between the example in Figure 6 and the example in Figure 4 includes: in the example in Figure 4, the LLDP PDU is generated by the UPF, and in the example in Figure 6, the LLDP PDU is generated by the CPE. Include the following steps:
  • Step 600 the industrial field enabling service IFES functional entity can obtain the network topology relationship under normal operation.
  • the IO2 device is connected to CPE3, and CPE3 is connected to UPF1 as an example.
  • IFES can obtain the device name of the IO2 device: IO2, and the alias of the IO2 device: CPE3.UPF1.
  • Step 601 UPF1 sends first information to CPE3 through RAN, and CPE3 receives the first information from UPF1 accordingly.
  • the first information indicates that the identifier of the first device is UPF1.
  • the first indication information may also indicate that the first port identifier is CPE3.
  • the device identifier in the LLDP PDU constructed by the first virtual port device based on the first information is UPF1, and the port identifier is CPE3.
  • the port identifier is the identifier of a virtual port device connected to the industrial device.
  • the virtual switch does not need to indicate the first virtual port device to the first virtual port device Port ID.
  • the virtual port device is connected to the RAN, and the virtual switch (such as UPF) changes and is invisible to the virtual port device.
  • the virtual port device does not save the identity of the virtual switch it is connected to, but the same reason , if the virtual port device can save 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.
  • the virtual switch may also send second indication information to the first virtual port device.
  • the first virtual port device receives the second indication information from the virtual switch, and the second indication information is used to indicate that the first virtual port device receives the second indication information from the virtual switch.
  • Virtual port devices generate LLDP PDUs.
  • the virtual switch and the first virtual port device may agree with each other, or the agreement stipulates that the first virtual port device generates the first LLDP PDU, so that there is no need to send the second indication information to the first virtual port device.
  • CPE3 may send a response message to UPF1 to indicate that the information from UPF1 is received.
  • Step 602 CPE3 saves relevant parameters for constructing the LLDP PDU, for example, the storage device ID is the ID of UPF1, and the port ID is the ID of CPE3.
  • step 603a the PLC sends a discovery message to the UPF, and the UPF receives the discovery message from the PLC accordingly.
  • Discovery messages are used to obtain relevant parameter information of industrial equipment.
  • the discovery message may be sent only for the IO2 device, for example, the discovery message includes the device name of the IO2 device.
  • the discovery message may also be sent for devices on the entire network, and the discovery message may be a multicast message.
  • the discovery message may be, for example, a DCP identify request.
  • step 603b (same as step 405b): UPF1 sends a discovery message from PLC to IFES, and IFES receives the discovery message from UPF1.
  • step 603c the IFES sends a discovery message to all network devices (mainly referring to IO devices) or IO2 devices.
  • IFES can send discovery messages in multicast or unicast mode.
  • Step 603c is similar to step 405c and will not be repeated here.
  • Step 604 CPE3 generates an LLDP packet, including an LLDP PDU, and the LLDP PDU is generated based on the relevant parameters stored in step 602 for constructing the LLDP PDU.
  • the device ID in the LLDP PDU is the ID of UPF1, and the port ID is the ID of CPE3.
  • CPE3 may trigger the generation of LLDP PDUs based on the discovery message in step 603c.
  • CPE3 may also directly perform step 604 after step 602 .
  • Step 605 CPE3 sends the LLDP message generated in step 604 to the new IO device (the IO2 device has been replaced by the new IO device), and the new IO device receives the LLDP message from CPE3, and the LLDP message includes the LLDP PDU.
  • Step 606 the new IO device determines the alias of the new IO device based on the LLDP PDU in the LLDP message.
  • the new IO device determines an alias name of the new IO device: the identifier of the CPE3.the identifier of the UPF1.
  • Step 607a The new IO device sends relevant parameter information of the new IO device to CPE3.
  • 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 .
  • Step 607b CPE3 sends the relevant parameter information of the new IO device in step 605 to the IFES.
  • CPE3 sends a response message to the IFES, and the response message includes relevant parameter information of the new IO device.
  • the reply message is, for example, a DCP Identify reply.
  • the response message may include success indication information, for example, carrying 0x00 in a header (header), indicating success.
  • Step 607a and step 607b are similar to step 407.
  • the control device after sending the DCP identify identify request, there will be no waiting timeout, and the response can be received in advance, and the replacement without perception can be realized.
  • Step 608 (same as step 408): IFES queries the stored original configuration parameters of the IO2 device.
  • Step 609 (same as step 409): IFES configures the old parameters in the original configuration parameters except the MAC to the new IO device. For example, the device name of the IO2 device.
  • IFES sends a DCP Set request to the new IO device, including the old parameters in the original configuration parameters except MAC.
  • Step 610 (same as step 410): the new IO device sends a response (such as a DCP Set response) to the IFES, indicating that the DCP Set request has been received.
  • a response such as a DCP Set response
  • the new IO device has updated its own parameters according to the old parameters.
  • step 611a (same as step 411a): IFES sends a response message to UPF1, and the response message includes the MAC address of the new IO address.
  • the reply message is, for example, a DCP Identify reply.
  • step 611b (same as step 411b): UPF1 sends the reply message from IFES to PLC.
  • step 607a-step 610 can be replaced with the following process:
  • the CPE3 stores the relevant parameter information of the replaced IO2 device, and the CPE3 sends a configuration message to the new IO device for configuring the relevant parameter information of the replaced IO2 device.
  • CPE3 sends a DCP Set request to the new IO device, including the old parameters of the original parameters of the IO2 device except MAC.
  • the new IO device sends a response (such as a DCP Set response) to CPE3, indicating that the DCP Set request has been received, and the new IO device has updated its own parameters according to the old parameters.
  • the response message may include success indication information, for example, carrying 0x00 in a header (header), indicating success.
  • the CPE3 sends a reply message to the IFES, and the reply message includes the MAC address of the new IO address and the old parameters of the IO2 device except the MAC.
  • the reply message is, for example, a DCP Identify reply.
  • the response message may include success indication information, for example, carrying 0x00 in a header (header), indicating success.
  • the CPE can also generate LLDP PDUs, UPF sends the first information to multiple CPEs, and multiple CPEs send LLDP packets to the new IO device, as shown in Figure 5
  • UPF sends the first information to multiple CPEs
  • multiple CPEs send LLDP packets to the new IO device, as shown in Figure 5
  • the examples are similar and will not be described in detail.
  • Embodiment 1 may also be applicable to a scenario where a certain virtual port device (such as a CPE) is damaged.
  • a certain virtual port device such as a CPE
  • Step 700 The control device (such as IFES) acquires the network topology relationship under normal operation.
  • the device name of the IO2 device is: IO2
  • the alias of the IO2 device is: CPE3.UPF1.
  • CPE3 is faulty. After CPE5 goes online, completes authentication and accesses the wireless industrial network, the UPF can know that CPE5 has replaced the original CPE3.
  • the port identifier in the LLDP PDU (such as the international mobile equipment identity code IMEI of the CPE) can be changed from the original CPE3 to CPE5, and the alias of the IO2 device can be changed from the original CPE3 .
  • UPF1 becomes CPE5.UPF1.
  • the SIM card can be pulled out from the old machine (such as CPE3) and placed in a new machine (such as CPE5), and then the international mobile subscriber identity (IMSI) can remain unchanged.
  • the first virtual port device in FIG. 3 b of Embodiment 1 is the new virtual port device: CPE5, and the first industrial device is the unreplaced industrial device: IO2 device.
  • Step 701 The virtual switch (such as UPF1) sends the first information to the first virtual port device (such as CPE5), and correspondingly, the first virtual port device receives the first information from the virtual switch.
  • the first virtual port device such as CPE5
  • step 301 For specific details, reference may be made to the introduction of step 301, and details are not repeated here.
  • Step 702 The first virtual port device (such as CPE5) sends the LLDP packet to the first industrial device (such as IO2 device), and correspondingly, the first industrial device receives the LLDP packet from the first virtual port device.
  • the first virtual port device such as CPE5
  • the first industrial device such as IO2 device
  • step 302 For specific details, reference may be made to the introduction of step 302, and details are not repeated here.
  • Step 703 The first industrial device (such as IO2 device) determines the alias of the first industrial device based on the first device identifier and the first port identifier in the first LLDP PDU.
  • the first industrial equipment determines its own alias as: CPE5.UPF1.
  • step 704 the control device (for example, IFES) sends a discovery message to the first industrial device (for example, IO2 device) based on the device name of the first industrial device (for example, IO2 device).
  • the control device for example, IFES
  • a discovery message is, for example, a DCP Identify request.
  • IFES can send discovery messages in multicast or unicast mode.
  • step 705 the first industrial device (such as IO2 device) may send a response message to the control device (such as IFES), and the response message includes the alias of the first industrial device (such as IO2 device), such as CPE5.UPF1, The rest of the parameters remain unchanged.
  • the control device such as IFES
  • the response message includes the alias of the first industrial device (such as IO2 device), such as CPE5.UPF1, The rest of the parameters remain unchanged.
  • the reply message is, for example, a DCP Identify reply.
  • the response message may include success indication information, for example, carrying 0x00 in a header (header), indicating success.
  • 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; If there is no CPE1 in between, the alias can be port1.UPF1.
  • the alias of UPF1 is port1.IO1;
  • UPF1 For PLC, the alias of UPF1 is CPE1.UPF1 or port1.PLC.
  • the virtual switch is connected to one or more virtual port devices through the RAN.
  • the first virtual port device is any virtual port device in the network, and each virtual port device is connected to a A switch, each switch SW is connected to multiple industrial devices, and each industrial device is connected to one SW.
  • the first virtual port device connects the second industrial device with other industrial devices.
  • the second industrial equipment fails or other reasons, and the first industrial equipment is used to replace the second industrial equipment. After the replacement, the first industrial device maintains the same connection relationship as the second industrial device.
  • the connection relationship involved in this embodiment may be a wireless connection such as a 5G connection, a WiFi connection, or a wired connection such as a copper wire, an optical fiber, or a twisted pair.
  • a virtual switch is used to construct an LLDP PDU, so as to configure an alias for the first industrial device (such as an IO2 device) and remove the MAC Other relevant parameter information other than the address.
  • the virtual switch sends the service message containing the LLDP PDU to the switch SW, and the switch SW executes the function of a virtual port device (such as CPE3) to parse the service message and obtain the LLDP PDU , and send the LLDPPDU to the first industrial device.
  • a virtual port device such as CPE3
  • the virtual switch sends the device ID and port ID used to construct the LLDP PDU to the virtual port device, and the virtual port device sends Construct the LLDP PDU to configure the alias for the first industrial equipment (such as IO2 equipment) and other relevant parameter information except the MAC address.
  • the switch SW performs the function of a virtual port device (such as CPE3), and the virtual switch sends the device identification and port identification for constructing the LLDP PDU to the switch SW, and the virtual switch sends Construct LLDP PDU and send LLDP PDU to the first industrial equipment.
  • the port identification in the LLDP PDU needs to be changed, and correspondingly, the aliases of the second industrial equipment (such as IO2 equipment) and the aliases of the first industrial equipment (such as new IO equipment) will also be changed.
  • the port identification of the switch is added on the original basis, and the port identification of the switch refers to the identification of the port connected to the industrial equipment (also new industrial equipment) to be replaced on the switch.
  • 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 (such as a new IO device) and the second industrial device (such as an IO2 device) are: ID of the first virtual port device-port ID of the switch.ID of the virtual switch.
  • the new IO device is connected to port2 of the switch SW, the switch SW is connected to CPE3, and CPE3 is connected to UPF1, then the alias of the new IO device can be: CPE3-2.UPF1, where "2" represents the port ID of the switch .
  • the alias of the new IO device is: CPE3-port2.UPF1, or port2-CPE3.UPF1, or UPF1.port2-CPE3, and the alias of the new IO device can be any variant that can uniquely represent the new IO device.
  • the switch SW and the new IO device perform information interaction in an existing manner, for example:
  • the switch sends the 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 switch SW identifier, and the port identifier is the switch port identifier.
  • the new IO device is based on the LLDP PDU to determine the alias of the new IO device. 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, then the new IO device can set its own alias as Port02.Switch.
  • the new IO device may report its own alias to the control device.
  • IFES can send discovery messages in multicast or unicast mode.
  • the discovery message is, for example, a DCP Identify request, and the discovery message may include the alias of the IO2 device (that is, the new IO device). Or a discovery message such as a request for DCP Identify all.
  • control device needs to go through the virtual switch, the virtual port device, and the arrangement of the switch.
  • Step 900 The industrial field enabling service IFES functional entity can obtain the network topology relationship under normal operation.
  • IO2 and IO3 devices are connected to CPE3 through the switch SW, CPE3 is connected to UPF1, and the new IO device replaces the faulty IO2 device as an example.
  • IFES can obtain the device name of the IO2 device: IO2, the name of the IO2 device The alias name is: Port02.Switch, and the device name of the IO3 device can also be obtained: IO3, and the alias name of the IO3 device is: Port03.Switch.
  • 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.
  • Step 902 (same as step 405c): IFES sends a discovery message to all network devices (mainly refers to industrial devices), but does not receive a response from IO2 device after timeout, then it can be determined that IO2 is faulty.
  • Step 903 (same as step 406): IFES can determine the alias of the IO2 device according to the pre-saved network topology, and send a discovery message to the IO2 device according to the alias of the IO2 device (eg Port02.Switch). At this time, the new IO device receives the discovery message.
  • IFES can determine the alias of the IO2 device according to the pre-saved network topology, and send a discovery message to the IO2 device according to the alias of the IO2 device (eg Port02.Switch). At this time, the new IO device receives the discovery message.
  • the IO2 device eg Port02.Switch
  • a discovery message is, for example, a DCP Identify request.
  • IFES can send discovery messages in multicast or unicast mode.
  • the above steps 902 and 903 may also be replaced by IFES sending a discovery message to all network devices (mainly referring to industrial devices), and the new IO device receives the discovery message.
  • Step 904 (same as step 407): the new IO device sends a response message to the IFES, and the response message includes relevant parameter information of the new IO device.
  • the reply message is, for example, a DCP Identify reply.
  • the relevant parameter information of the new IO device includes the alias and the MAC address of the new IO device.
  • Step 905 (same as step 408): IFES queries the stored original configuration parameters of the IO2 device.
  • Step 906 configures the old parameters in the original configuration parameters except MAC for the new IO device. For example, the device name of the IO2 device.
  • IFES sends a DCP Set request to the new IO device, including the old parameters in the original configuration parameters except MAC.
  • the parameter source is the historical storage of industrial topology discovery.
  • Step 907 the new IO device sends a response (such as a DCP Set response) to the IFES, indicating that the DCP Set request has been received.
  • a response such as a DCP Set response
  • the new IO device has updated its own parameters according to the old parameters.
  • a communication process suitable for the communication system as shown in Figure 7 is introduced.
  • the difference between the example in Figure 10 and the example in Figure 9 includes: the alias of the IO device saved on the IFES includes CPE and UPF
  • the alias of the IO device and the switch SW determined based on the existing method only includes the identifier of the switch and the port identifier of the switch, without the information of the CPE and UPF.
  • the control device sends a message to the IO device, the CPE needs to have the function of mapping the alias, and the CPE will convert the alias in the message based on the alias mapping rule so that the IO device can recognize it.
  • Step 1000 The industrial field enabling service IFES functional entity can obtain the network topology relationship under normal operation.
  • IO2 and IO3 devices are connected to CPE3 through the switch SW, CPE3 is connected to UPF1, and the new IO device replaces the faulty IO2 device as an example.
  • IFES can obtain the device name of the IO2 device: IO2, the name of the IO2 device The alias name is: CPE3-2.UPF (where "2" represents the Port02 of the switch), and the device name of the IO3 device can also be obtained: IO3, and the alias name of the IO3 device is: CPE3-3.UPF (where "3" Indicates Port03 of the switch).
  • Step 1001 The switch and the new IO device send LLDP PDUs to each other, and determine the alias of the new IO device as Port02.Switch.
  • Step 1002 IFES sends a discovery message to CPE3.
  • the discovery message may include the alias CPE3-2.UPF of the IO2 device.
  • a discovery message is, for example, a DCP Identify request.
  • IFES can send discovery messages in multicast or unicast mode.
  • Step 1003 CPE3 sends a discovery message, and the new IO device receives the discovery message.
  • CPE3 converts the alias of the IO2 device based on the alias mapping rule, for example, converts CPE3-2.UPF to Port02.Switch. CPE3 sends a discovery message to the converted alias (for example, Port02.Switch).
  • Step 1004 (similar to step 407): the new IO device sends a response message to CPE3, and the response message includes relevant parameter information of the new IO device.
  • the reply message is, for example, a DCP Identify reply.
  • the response message may include success indication information, for example, carrying 0x00 in a header (header), indicating success.
  • 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, site name (NameOfStation), device role (Device Role) , Device Vendor, Device ID, Device Options, IP Parameter, DHCP Parameter, Manufacturer Specific Parameter, AliasName .
  • Step 1005 CPE3 converts the alias of the IO2 device based on the alias mapping rule, for example, converts Port02.Switch to CPE3-2.UPF.
  • CPE3 sends a response message to the IFES, and the response message includes relevant parameter information of the new IO device.
  • the reply message is, for example, a DCP Identify reply.
  • the relevant parameter information of the new IO device includes the alias of the new IO device (here, the alias of the new IO device is the converted alias, such as CPE3-2.UPF), MAC address, and may also include the information introduced in step 1004 above.
  • Step 1006 (same as step 408): IFES queries the stored original configuration parameters of the IO2 device.
  • Step 1007 (similar to step 409): IFES configures the old parameters in the original configuration parameters except MAC to CPE3.
  • the device name of the IO2 device may also include the information introduced in step 1004 above, and there may be no alias in step 1007.
  • IFES sends a DCP Set request to the new IO device, including the old parameters in the original configuration parameters except MAC.
  • the alias of the IO2 device saved in the IFES carried in the message sent to CPE3, for example, CPE3-2.UPF.
  • Step 1008 CPE3 converts the alias of the IO2 device based on the alias mapping rule, for example, converts CPE3-2.UPF to Port02.Switch.
  • the CPE3 configures the old parameters in the original configuration parameters except the MAC to the IO device.
  • the device name of the IO2 device may also include the information introduced in step 1007 above.
  • Step 1009 the new IO device sends a response (such as a DCP Set response) to the IFES through the CPE3, indicating that the DCP Set request has been received.
  • a response such as a DCP Set response
  • the new IO device has updated its own parameters according to the old parameters.
  • Table 6 the alias list under CPE3 is introduced.
  • the content introduced in Table 6 can refer to the introductions in Table 3, Table 4, and Table 5, and will not be described in detail.
  • Table 7 As shown in Table 7 below, the alias list under the network side is introduced.
  • the content introduced in Table 7 can refer to the introductions in Table 3, Table 4, and Table 5, and will not be repeated in detail.
  • the virtual switch connects one or more industrial devices through the RAN.
  • the industrial devices have wireless access functions, and the virtual port device can be omitted. It can also be understood as an industrial device and a virtual port device.
  • the second industrial equipment fails or other reasons, and the first industrial equipment is used to replace the second industrial equipment. 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 may be a wireless connection such as a 5G connection, a WiFi connection, or a wired connection such as a copper wire, an optical fiber, or a twisted pair.
  • the virtual switch generates service messages including LLDP PDUs and sends the service messages to the virtual port device.
  • the virtual port device parses the LLDP PDU, it constructs an LLDP message and sends the LLDP message to the first industrial equipment.
  • the service message including LLDP PDU generated by the virtual switch can be directly sent to the first industrial device, and the first industrial device can parse out the LLDP PDU, thereby determining the alias of the first industrial device according to the LLDP PDU.
  • Figure 12 includes the following steps:
  • Step 1200 the virtual switch sends a service message to the first industrial device, and correspondingly, the first industrial device receives the service message from the virtual switch.
  • the message body of the service message includes the first link layer discovery protocol packet data unit LLDP PDU, that is, the virtual switch adds a message header to the first LLDP PDU generated, and sends the entire message to the first industrial device.
  • the first industrial equipment can parse the service message to obtain the first LLDP PDU.
  • the first LLDP PDU is used to determine the alias of the industrial device.
  • the first device identifier included in the first LLDP PDU is an identifier of a virtual switch
  • the first port identifier included in the first LLDP PDU is a permanent equipment identifier of the first industrial device. , PEI) or international mobile equipment identity (international mobile equipment identity, IMEI).
  • the industrial equipment When the industrial equipment is registered, it has reported its own PEI and/or IMEI to the network side, so the virtual port equipment knows the PEI and/or IMEI of the new industrial equipment.
  • 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 be different from the original The alias of the industrial device will also change.
  • the device name corresponding to the replaced second industrial device is IO2, and its alias is: CPE3.UPF1
  • the PEI/IMEI of the first industrial device is CPE4, then the alias of the first industrial device is: CPE4.UPF1.
  • the virtual switch sends service information to the first industrial device through the RAN.
  • Step 1201 The first industrial device determines an alias of the first industrial device based on the first device identifier and the first port identifier.
  • 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.
  • the alias is just a hint, and it can also be in other forms, as long as the devices in the network agree with each other.
  • the device ID may be in front and the port ID in the back, for example, the ID of the virtual switch.IMEI.
  • other characters may be used between the port identifier and the device identifier, such as "-", "_" and so on.
  • the first industrial device can also report its own relevant parameter information to the control device, and the control device can send the second industrial device to the first industrial device (the second industrial device is damaged, and it is replaced by the first industrial device) ) related parameter information (not including the media access control address MAC of the second industrial device), so as to realize lossless replacement of services.
  • This process is the same as that described in Example 1, for example:
  • the control device sends a discovery message to the first industrial device, and correspondingly, the first industrial device receives the discovery message; the discovery message is used to instruct acquisition of relevant parameter information of the first industrial device.
  • the alias of the first industrial device is included in the discovery message.
  • the discovery message may be, for example, a Discovery and Configuration Protocol Identify DCP Identify request.
  • the first industrial device sends a response message to the discovery message, and correspondingly, the control device receives the response message from the first industrial device, where the response message includes relevant parameter information of the first industrial device;
  • the response message may be, for example, a discovery and configuration protocol identification DCP Identify response.
  • the control device may send first parameter information to the first industrial device, and correspondingly, the first industrial device receives the first parameter information, and the first parameter information is set by the first industrial device. Relevant parameter information of the second industrial equipment to be replaced, where the medium access control address MAC of the second industrial equipment is not included in the relevant parameter information.
  • step 405a to step 411b in FIG. 4 for example, refer to the process from step 505a to step 511b in FIG. 5 , which will not be repeated here.
  • the virtual switch generates a service message containing LLDP PDU, and sends the service message to a new industrial device, so that the new industrial device determines its own alias based on the LLDP PDU in the service message.
  • New industrial equipment can determine the unique alias based on the existing LLDP protocol specification and existing naming rules, and use the permanent equipment identity code PEI or the international mobile equipment identity code IMEI as the port identification, so as to realize the new IO equipment to join the wireless group network architecture.
  • the method in the embodiment of the present application is introduced above, and the device in the embodiment of the present application will be introduced in the following.
  • the method and the device are based on the same technical concept. Since the principles of the method and the device to solve problems are similar, the implementation of the device and the method can be referred to each other, and the repetition will not be repeated.
  • the embodiment of the present application may divide the device into functional modules according to the above method example, for example, each function may be divided into each functional module, or two or more functions may be integrated into one module.
  • These modules can be implemented not only in the form of hardware, but also in the form of software function modules. It should be noted that the division of the modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be another division manner during specific implementation.
  • 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 and the receiving module 1320a and the sending module 1320b respectively, and the storage module 1330 may also be connected to the receiving module 1320a and the sending module 1320b.
  • the above-mentioned receiving module 1320a and sending module 1320b may also be integrated together and defined as a transceiver module.
  • the apparatus 1300 may be a first virtual port device, or may be a chip or a functional unit applied to the first virtual port device.
  • the apparatus 1300 has any function of the first virtual port device in the above-mentioned method, for example, the apparatus 1300 can execute the methods in the above-mentioned Figure 3b, Figure 4, Figure 5, Figure 6, Figure 7, Figure 9, Figure 10, Figure 12 Various steps performed by the first virtual port device.
  • the receiving module 1320a may perform the receiving action performed by the first virtual port device in the above method embodiment.
  • the sending module 1320b can execute the sending action performed by the first virtual port device in the above method embodiment.
  • the processing module 1310 may execute other actions except the sending action and the receiving action among the actions performed by the first virtual port device in the above method embodiment.
  • the receiving module 1320a is configured 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, and the first device identifier is the An identifier of a virtual switch, where the first port identifier includes an identifier of at least one virtual port device.
  • the sending module 1320b is configured to send a link layer discovery protocol LLDP message to the first industrial equipment, the LLDP message includes a first link layer discovery protocol packet data unit LLDP PDU, and the first LLDP PDU contains The first device identifier is the identifier of the virtual switch, the first port identifier in the first LLDP PDU includes at least one virtual port device identifier, and the first LLDP PDU is used to determine the identity of the first industrial device alias.
  • the first information may be a service message; a message body of the service message includes the first LLDP PDU.
  • the first information may further include first indication information, where the first indication information is used to indicate transparent transmission of the first LLDP PDU.
  • 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.
  • the receiving module 1320a is further configured to receive second indication information from the virtual switch, where the second indication information is used to indicate that the first virtual port device generates the LLDP PDU.
  • the receiving module 1320a is further configured to receive a discovery message from the control device, and trigger generation of the first LLDP PDU, where the discovery message is used to instruct acquisition of the first industrial device information.
  • 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 to obtain related 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 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 relevant parameter information of the first industrial device.
  • the storage module 1330 may store computer-executed instructions of the method executed by the first virtual port device, so that the processing module 1310, the receiving module 1320a, and the sending module 1320b execute the first virtual port device in the above examples. Methods.
  • the apparatus 1300 may be a virtual switch, or may be a chip or a functional unit applied to the virtual switch.
  • the device 1300 has any function of the virtual switch in the above method, for example, the device 1300 can execute the virtual switch in the methods shown in Figure 3b, Figure 4, Figure 5, Figure 6, Figure 7, Figure 9, Figure 10, and Figure 12 steps performed.
  • the receiving module 1320a can perform the receiving action performed by the virtual switch in the above method embodiment.
  • the sending module 1320b can execute the sending action performed by the virtual switch in the above method embodiment.
  • the processing module 1310 may execute other actions except the sending action and the receiving action among the actions performed by the virtual switch in the above method embodiments.
  • the processing module 1310 is configured to generate first information, where 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 It is 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, and the first port identifier includes an identifier of at least one virtual port device; the second An LLDP PDU is used to determine the alias of the first industrial device.
  • the sending module 1320b is configured to send the first information to a first virtual port device, where the at least one virtual port device includes the first virtual port device.
  • the first information may be a service message; a message body of the service message includes the first LLDP PDU.
  • the first information may further include first indication information, where the first indication information is used to indicate transparent transmission of the first LLDP PDU.
  • 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 the LLDP PDU.
  • the storage module 1330 may store computer-executed instructions of the method executed by the virtual switch, so that the processing module 1310, the receiving module 1320a, and the sending module 1320b execute the method executed by the virtual switch in the above example.
  • the apparatus 1300 may be the first industrial equipment, or may be a chip or a functional unit applied in the first industrial equipment.
  • the device 1300 has any function of the first industrial equipment in the above-mentioned method, for example, the device 1300 can execute the above-mentioned methods in Fig. 3b, Fig. 4, Fig. 5, Fig. 6, Fig. 7, Fig. 9, Fig. Steps performed by the first industrial plant.
  • the receiving module 1320a may perform the receiving action performed by the first industrial device in the above method embodiment.
  • the sending module 1320b can execute the sending action performed by the first industrial device in the above method embodiment.
  • the processing module 1310 may execute other actions except the sending action and the receiving action among the actions performed by the first industrial device in the above method embodiments.
  • the receiving module 1320a is configured to receive an LLDP packet from a first virtual port device, where the LLDP packet includes a first link layer discovery protocol packet data unit LLDP PDU; the first The first device identifier included in the 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 the first industrial device alias for .
  • the processing module 1310 is configured to determine an 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.the identifier of the at least one virtual port device.
  • the receiving module 1320a is also configured to receive a discovery message, the discovery message includes the alias of the first industrial device, and the discovery message is used to indicate to obtain the first industrial device Device related parameter information.
  • the sending module 1320b is further configured to send a response message, where the response message includes relevant parameter information of the first industrial device.
  • the receiving module 1320a is further configured to receive first parameter information, 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 old industrial equipment.
  • the media access control address MAC of industrial equipment is also configured to receive a discovery message, the discovery message includes the alias of the first industrial device, and the discovery message is used to indicate to obtain the first industrial device Device related parameter information.
  • the sending module 1320b is further configured to send a response message, where the response message includes relevant parameter information of the first industrial device.
  • the receiving module 1320a is further configured to receive first parameter information, the first parameter information is related parameter information of the old industrial equipment replaced by the first industrial equipment
  • the storage module 1330 can store computer-executed instructions of the method executed by the first industrial equipment, so that the processing module 1310, the receiving module 1320a, and the sending module 1320b execute the method executed by the first industrial equipment in the above examples .
  • the storage module may include one or more memories, and the memories may be devices used to store programs or data in one or more devices and circuits.
  • the storage module may be a register, a cache, or a RAM, etc., and the storage module may be integrated with the processing module.
  • the storage module can be ROM or other types of static storage devices that can store static information and instructions, and the storage module can be independent from the processing module.
  • the transceiver module may be an input or output interface, a pin or a circuit, and the like.
  • the device can be realized by a general bus architecture.
  • FIG. 14 a schematic block diagram of a communication device 1400 is provided.
  • the apparatus 1400 may include: a processor 1410 , and optionally, a transceiver 1420 and a memory 1430 .
  • the transceiver 1420 can be used to receive programs or instructions and transmit them to the processor 1410, or the transceiver 1420 can be used for the device 1400 to communicate and interact with other communication devices, such as interactive control signaling and/or business data etc.
  • the transceiver 1420 may be a code and/or data read/write transceiver, or the transceiver 1420 may be a signal transmission transceiver between the processor and the transceiver.
  • the processor 1410 is electrically coupled to the memory 1430 .
  • the apparatus 1400 may be a first virtual port device, or may be a chip applied to the first virtual port device. It should be understood that the device has any function of the first virtual port device in the above method, for example, the device 1400 can execute the above-mentioned Figure 3b, Figure 4, Figure 5, Figure 6, Figure 7, Figure 9, Figure 10, Figure 12 The various steps performed by the first virtual port device in the method.
  • the memory 1430 is configured to store a computer program; the processor 1410 may be configured to invoke the computer program or instruction stored in the memory 1430 to execute the method performed by the first virtual port device in the above example, or
  • the transceiver 1420 executes the method executed by the first virtual port device in the foregoing example.
  • the apparatus 1400 may be a virtual switch, or may be a chip applied to the 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 methods in Figure 3b, Figure 4, Figure 5, Figure 6, Figure 7, Figure 9, Figure 10, Figure 12 Individual steps performed by the virtual switch.
  • the memory 1430 is used to store computer programs; the processor 1410 can be used to call the computer programs or instructions stored in the memory 1430 to execute the method performed by the virtual switch in the above example, or through the The transceiver 1420 performs the method performed by the virtual switch in the above example.
  • the apparatus 1400 may be the first industrial equipment, or may be a chip applied to the first industrial equipment. It should be understood that the device has any function of the first industrial equipment in the above method, for example, the device 1400 can perform the above-mentioned Figure 3b, Figure 4, Figure 5, Figure 6, Figure 7, Figure 9, Figure 10, Figure 12 Steps in the method performed by the first industrial plant.
  • the memory 1430 is used to store computer programs; the processor 1410 can be used to invoke the computer programs or instructions stored in the memory 1430 to execute the method performed by the first industrial equipment in the above examples, or through The transceiver 1420 executes the method executed by the first industrial device in the above example.
  • the processing module 1310 in FIG. 13 may be implemented by the processor 1410 .
  • the receiving module 1320a and the sending module 1320b in FIG. 13 may be implemented by the transceiver 1420 .
  • 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.
  • the storage module 1330 in FIG. 13 may be implemented by the memory 1430 .
  • the device may be implemented by a general-purpose processor (a general-purpose processor may also be referred to as a chip or system-on-a-chip).
  • a general-purpose processor may also be referred to as a chip or system-on-a-chip.
  • implementing the device applied to the first virtual port device or the device of the virtual switch or the general processor of the first industrial device includes: a processing circuit (the processing circuit may also be referred to as a processor); , further comprising: an input-output interface connected and communicated with the processing circuit internally, a storage medium (the storage medium may also be referred to as a memory), and the storage medium is used to store instructions executed by the processing circuit to execute the first virtual A method performed by a port device or a virtual switch or a first industrial device.
  • the processing module 1310 in FIG. 13 may be implemented by a processing circuit.
  • the receiving module 1320a and the sending module 1320b in FIG. 13 can be implemented through input and output interfaces.
  • 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.
  • the storage module 1330 in FIG. 13 may be implemented by a storage medium.
  • the device of the embodiment of the present application can also be realized using the following: one or more FPGAs (Field Programmable Gate Arrays), PLDs (Programmable Logic Devices), controllers, state machines, Any combination of gate logic, discrete hardware components, any other suitable circuitry, or circuitry capable of performing the various functions described throughout this application.
  • FPGAs Field Programmable Gate Arrays
  • PLDs Programmable Logic Devices
  • controllers state machines, Any combination of gate logic, discrete hardware components, any other suitable circuitry, or circuitry capable of performing the various functions described throughout this application.
  • the embodiment of the present application also provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a computer, the computer can be used to execute the above communication method.
  • the computer program includes instructions for implementing the above communication method.
  • the embodiment of the present application also provides a computer program product, including: computer program code, when the computer program code is run on the computer, the computer can execute the communication method provided above.
  • An embodiment of the present application further provides a communication system, and the communication system includes: a virtual switch for performing the above communication method, a first virtual port device, and a first industrial device.
  • processors mentioned in the embodiment of the present application may be a central processing unit (central processing unit, CPU), a baseband processor, and the baseband processor and the CPU may be integrated or separated, or may be a network processor (network processing unit).
  • processor NP
  • processors may further include hardware chips or other general-purpose processors.
  • the aforementioned hardware chip may be an application-specific integrated circuit (application-specific integrated circuit, ASIC), a programmable logic device (programmable logic device, PLD) or a combination thereof.
  • the above PLD can be complex programmable logic device (complex programmable logic device, CPLD), field programmable logic gate array (field-programmable gate array, FPGA), general array logic (generic array logic, GAL) and other programmable logic devices , discrete gate or transistor logic devices, discrete hardware components, etc., or any combination thereof.
  • CPLD complex programmable logic device
  • FPGA field programmable logic gate array
  • GAL general array logic
  • GAL generator array logic
  • a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
  • the memory mentioned in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electronically programmable Erase Programmable Read-Only Memory (Electrically EPROM, EEPROM) or Flash.
  • the volatile memory can be Random Access Memory (RAM), which acts as external cache memory.
  • RAM Static Random Access Memory
  • SRAM Static Random Access Memory
  • DRAM Dynamic Random Access Memory
  • Synchronous Dynamic Random Access Memory Synchronous Dynamic Random Access Memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • enhanced SDRAM ESDRAM
  • Synchlink DRAM SLDRAM
  • Direct Memory Bus Random Access Memory Direct Rambus RAM, DR RAM
  • the transceiver mentioned in the embodiment of the present application may include a separate transmitter and/or a separate receiver, or the transmitter and the receiver may be integrated. Transceivers can operate under the direction of corresponding processors.
  • the transmitter may correspond to the transmitter in the physical device, and the receiver may correspond to the receiver in the physical device.
  • the disclosed systems, devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment of the present application.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.
  • the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • 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 software products, and the computer software products are stored in a storage medium
  • several instructions are included to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

Abstract

本申请涉及通信技术领域。提供一种通信方法及装置，用以实现新IO设备加入无线组网架构。首先，第一虚拟端口设备接收来自虚拟交换机的第一信息，第一信息用于指示设备标识和端口标识，设备标识为虚拟交换机的标识，端口标识包括至少一个虚拟端口设备的标识。然后，第一虚拟端口设备向第一工业设备发送链路层发现协议LLDP报文，LLDP报文中包括第一链路层发现协议分组数据单元LLDP PDU，第一LLDP PDU中的设备标识为虚拟交换机的标识，第一LLDP PDU中的端口标识包括至少一个虚拟端口设备的标识，第一LLDP PDU用于确定第一工业设备的别名。为第一工业设备配置别名，从而实现新IO设备加入无线组网架构。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2022年01月17日提交中国专利局、申请号为202210050568.9、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信等领域，尤其涉及一种通信方法及装置。
背景技术
自动化控制系统(industrial automation and control system，IACS)是由许多电子与控制器等元件所组成，其广泛应用于化工产业、造纸业、发电厂、石油天然气提炼，以及电信业等各个工业行业中。控制器占用空间大，且回路流程不易修改与维护，可编程逻辑控制器(programmable logic controller，PLC)的出现使得这些问题得以决解。
在PLC大规模引入自动化控制系统后，一个主控的PLC和输入输出(input-output，IO)设备通过一个交换机进行连接。在交换机的北向还有可以实施管理的其他节点。不同节点之间的通信均通过有线的方式进行连接，例如铜线、双绞线、光纤。
随着通信技术的进一步发展，无线通信技术逐渐成为新的工业现场网络连接介质。这样可以将现有的PLC、IO等设备实现无线接入，实现了工业设备更加灵活的组网方式，并且可以更加便捷，例如支持例如自动引导车(automated guided vehicle，AGV)在内的需要兼顾移动性和灵活组网的新型工业终端设备。
在无线组网下，当某一IO设备损坏，如何实现新IO设备加入无线组网架构是需要解决的技术问题。
发明内容
本申请实施例提供一种通信方法及装置，用以实现新IO设备加入无线组网架构。
第一方面，提供了一种通信方法，该方法的执行主体可以是第一虚拟端口设备，也可以是应用于第一虚拟端口设备中的部件，例如芯片、处理器等。下面以执行主体是第一虚拟端口设备为例进行描述。首先，第一虚拟端口设备接收来自虚拟交换机的第一信息，所述第一信息用于指示第一设备标识和第一端口标识，所述第一设备标识为所述虚拟交换机的标识，所述第一端口标识包括至少一个虚拟端口设备的标识。然后，第一虚拟端口设备可以向第一工业设备发送链路层发现协议LLDP报文，所述LLDP报文中包括第一链路层发现协议分组数据单元LLDP PDU，所述第一LLDP PDU中的第一设备标识为所述虚拟交换机的标识，所述第一LLDP PDU中的第一端口标识包括至少一个虚拟端口设备的标识，所述第一LLDP PDU用于确定所述第一工业设备的别名。
该示例可以适用于每个虚拟端口设备连接一个工业设备，一个工业设备可以连接一个或多个虚拟端口设备的场景。虚拟交换机向虚拟端口设备指示端口标识和设备标识，端口标识为虚拟端口设备标识，设备标识为虚拟交换机标识；虚拟端口设备基于虚拟交换机的 指示来确定LLDP报文，并将LLDP报文发送给新的工业设备，以便新的工业设备基于LLDP报文中的LLDP PDU确定自身的别名。新的工业设备可以基于现有的LLDP协议的规范及现有的命名规则来确定唯一的别名，从而实现新IO设备加入无线组网架构。
在一种可能的实现中，所述第一信息可以为业务消息；所述业务消息的消息体包括所述第一LLDP PDU。这种方式对于虚拟端口设备来说，只需要解析透传即可，实现比较简单。
在一种可能的实现中，所述第一信息还可以包括第一指示信息，所述第一指示信息用于指示透传所述第一LLDP PDU。这样虚拟端口设备可以准确及时地透传该业务消息中的第一LLDP PDU，以避免与其它消息混乱，而未透传该业务消息中的第一LLDP PDU的情况。
在一种可能的实现中，所述第一虚拟端口设备可以基于所述第一信息指示的第一设备标识和第一端口标识，生成所述第一LLDP PDU。这种方式对于虚拟端口设备来说，在存储了端口标识和设备标识之后，可以随时向与该虚拟端口设备连接的工业设备发送LLDP报文，无需虚拟交换机的触发，这样确定新工业设备的别名的实效性更高，并且对于其它控制设备来说，这个过程是无感知的。
在一种可能的实现中，所述第一虚拟端口设备还可以接收来自虚拟交换机的第二指示信息，所述第二指示信息用于指示由所述第一虚拟端口设备生成LLDP PDU。这样虚拟端口设备可以及时准确地生成LLDP PDU，以避免虚拟端口设备将该第一指示信息与接收的其它信息混乱，而不知道作何处理的情况。
在一种可能的实现中，第一虚拟端口设备还可以接收来自控制设备的发现消息，触发生成所述第一LLDP PDU，所述发现消息用于指示获取所述第一工业设备信息。在控制设备未向工业设备发送发现消息的情况下，通常是未发生工业设备的替换事件的，如果在此期间，虚拟端口设备向工业设备发送LLDP报文，这个过程会浪费信令。所以第一虚拟端口设备可以在接收到来自控制设备的发现消息时，再触发生成所述第一LLDP PDU，这时发送不会造成信令浪费。
在一种可能的实现中，在所述第一虚拟端口设备向第一工业设备发送所述LLDP报文之后，所述第一虚拟端口设备还可以向所述第一工业设备发送所述发现消息，所述发现消息用于指示获取所述第一工业设备的相关参数信息。然后，所述第一虚拟端口设备可以接收来自所述第一工业设备的应答消息，所述应答消息包括所述第一工业设备的相关参数信息。接下来，所述第一虚拟端口设备可以向所述控制设备发送所述应答消息，所述应答消息中包括所述第一工业设备的相关参数信息。以便实现业务的无损替换。
第二方面，提供了一种通信方法，该方法的执行主体可以是虚拟交换机，也可以是应用于虚拟交换机中的部件，例如芯片、处理器等。下面以执行主体是虚拟交换机为例进行描述。首先，虚拟交换机生成第一信息，所述第一信息用于指示第一设备标识和第一端口标识，所述第一设备标识和所述第一端口标识用于生成第一链路层发现协议分组数据单元LLDP PDU，其中，所述第一设备标识为所述虚拟交换机的标识，所述第一端口标识包括至少一个虚拟端口设备的标识；所述第一LLDP PDU用于确定第一工业设备的别名。然后，所述虚拟交换机可以向第一虚拟端口设备发送所述第一信息，所述至少一个虚拟端口设备包括所述第一虚拟端口设备。
该示例可以适用于每个虚拟端口设备连接一个工业设备，一个工业设备可以连接一个 或多个虚拟端口设备的场景。虚拟交换机向虚拟端口设备指示端口标识和设备标识，端口标识为虚拟端口设备标识，设备标识为虚拟交换机标识；虚拟端口设备基于虚拟交换机的指示来确定LLDP报文，并将LLDP报文发送给新的工业设备，以便新的工业设备基于LLDP报文中的LLDP PDU确定自身的别名。新的工业设备可以基于现有的LLDP协议的规范及现有的命名规则来确定唯一的别名，从而实现新IO设备加入无线组网架构。
在一种可能的实现中，所述第一信息可以为业务消息；所述业务消息的消息体包括所述第一LLDP PDU。这种方式对于虚拟端口设备来说，只需要解析透传即可，实现比较简单。
在一种可能的实现中，所述第一信息还可以包括第一指示信息，所述第一指示信息用于指示透传所述第一LLDP PDU。这样虚拟端口设备可以准确及时地透传该业务消息中的第一LLDP PDU，以避免与其它消息混乱，而未透传该业务消息中的第一LLDP PDU的情况。
在一种可能的实现中，所述虚拟交换机还可以向第一虚拟端口设备发送第二指示信息，所述第二指示信息用于指示由所述第一虚拟端口设备生成LLDP PDU。这种方式对于虚拟端口设备来说，在存储了端口标识和设备标识之后，可以随时向与该虚拟端口设备连接的工业设备发送LLDP报文，无需虚拟交换机的触发，这样确定新工业设备的别名的实效性更高，并且对于其它控制设备来说，这个过程是无感知的。另外，第二指示信息可以使虚拟端口设备可以及时准确地生成LLDP PDU，以避免虚拟端口设备将该第一指示信息与接收的其它信息混乱，而不知道作何处理的情况。
第三方面，提供了一种通信方法，该方法的执行主体可以是第一工业设备，也可以是应用于第一工业设备中的部件，例如芯片、处理器等。下面以执行主体是第一工业设备为例进行描述。首先，第一工业设备可以接收来自第一虚拟端口设备的LLDP报文，所述LLDP报文中包括第一链路层发现协议分组数据单元LLDP PDU；所述第一LLDP PDU包括的第一设备标识为虚拟交换机的标识，所述第一LLDP PDU包括的第一端口标识包括至少一个虚拟端口设备的标识；所述第一LLDP PDU用于确定所述第一工业设备的别名。然后，所述第一工业设备基于所述第一设备标识和所述第一端口标识，确定所述第一工业设备的别名。例如，别名为所述虚拟交换机的标识.所述至少一个虚拟端口设备的标识。
该示例可以适用于每个虚拟端口设备连接一个工业设备，一个工业设备可以连接一个或多个虚拟端口设备的场景。虚拟交换机向虚拟端口设备指示端口标识和设备标识，端口标识为虚拟端口设备标识，设备标识为虚拟交换机标识；虚拟端口设备基于虚拟交换机的指示来确定LLDP报文，并将LLDP报文发送给新的工业设备，以便新的工业设备基于LLDP报文中的LLDP PDU确定自身的别名。新的工业设备可以基于现有的LLDP协议的规范及现有的命名规则来确定唯一的别名，从而实现新IO设备加入无线组网架构。
在一种可能的实现中，所述第一工业设备可以接收发现消息，所述发现消息中包括所述第一工业设备的别名，所述发现消息用于指示获取所述第一工业设备的相关参数信息。然后，所述第一工业设备可以发送应答消息，所述应答消息中包括所述第一工业设备的相关参数信息。接下来，所述第一工业设备接收第一参数信息，所述第一参数信息为所述第一工业设备所替换的旧工业设备的相关参数信息，所述相关参数信息中不包括所述旧工业设备的媒体存取控制地址MAC。以便实现业务的无损替换。
第一方面至第三方面适用于工业设备与虚拟端口设备分为两个设备的场景，第四方面 与第五方面适用于工业设备与虚拟端口设备合二为一个设备的场景。
第四方面，提供了一种通信方法，该方法的执行主体可以是虚拟交换机，也可以是应用于虚拟交换机中的部件，例如芯片、处理器等。下面以执行主体是虚拟交换机为例进行描述。首先，虚拟交换机可以生成业务消息，所述业务消息的消息体包括第一链路层发现协议分组数据单元LLDP PDU，所述第一LLDP PDU包括的第一设备标识为虚拟交换机的标识，所述第一LLDP PDU包括的第一端口标识为第一工业设备的永久设备身份码(permanent equipment identifier，PEI)或国际移动设备身份码(international mobile equipment identity，IMEI)，所述第一LLDP PDU用于确定所述第一工业设备的别名。然后，所述虚拟交换机可以向所述第一工业设备发送所述业务消息。
虚拟交换机来生成包含LLDP PDU的业务消息，并将业务消息发送给新的工业设备，以便新的工业设备基于业务消息中的LLDP PDU确定自身的别名。新的工业设备可以基于现有的LLDP协议的规范及现有的命名规则来确定唯一的别名，将永久设备身份码PEI或国际移动设备身份码IMEI作为端口标识，从而实现新IO设备加入无线组网架构。
第五方面，提供了一种通信方法，该方法的执行主体可以是第一工业设备，也可以是应用于第一工业设备中的部件，例如芯片、处理器等。下面以执行主体是第一工业设备为例进行描述。首先，第一工业设备接收来自虚拟交换机的业务消息，所述业务消息中包括第一链路层发现协议分组数据单元LLDP PDU，所述第一LLDP PDU包括的第一设备标识为所述虚拟交换机的标识，所述第一LLDP PDU包括的端口标识为第一工业设备的永久设备身份码PEI或国际移动设备身份码IMEI，所述第一LLDP PDU用于确定所述第一工业设备的别名。然后，所述第一工业设备基于所述第一设备标识和所述第一端口标识，确定所述第一工业设备的别名。例如别名为所述新IO设备的国际移动设备识别码IMEI.所述虚拟交换机的标识。
虚拟交换机来生成包含LLDP PDU的业务消息，并将业务消息发送给新的工业设备，以便新的工业设备基于业务消息中的LLDP PDU确定自身的别名。新的工业设备可以基于现有的LLDP协议的规范及现有的命名规则来确定唯一的别名，将永久设备身份码PEI或国际移动设备身份码IMEI作为端口标识，从而实现新IO设备加入无线组网架构。
在一种可能的实现中，所述第一工业设备还可以接收发现消息，所述发现消息中包括所述第一工业设备的别名，所述发现消息用于指示获取所述第一工业设备的相关参数信息。然后，所述第一工业设备可以发送应答消息，所述应答消息中包括所述第一工业设备的相关参数信息。接下来，所述第一工业设备可以接收第一参数信息，所述第一参数信息为所述第一工业设备所替换的旧工业设备的相关参数信息，所述相关参数信息中不包括所述旧工业设备的媒体存取控制地址MAC。以便实现业务的无损替换。
第六方面，提供了一种通信装置，所述装置具有实现上述任一方面及任一方面的任一可能的实现中的功能。这些功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的功能模块。
第七方面，提供了一种通信装置，包括处理器，可选的，还包括存储器；所述处理器和所述存储器耦合；所述存储器，用于存储计算机程序或指令；所述处理器，用于执行所述存储器中的部分或者全部计算机程序或指令，当所述部分或者全部计算机程序或指令被执行时，用于实现上述任一方面及任一方面的任一可能的实现的方法中的功能。
在一种可能的实现中，所述装置还可以包括收发器，所述收发器，用于发送所述处理 器处理后的信号，或者接收输入给所述处理器的信号。所述收发器可以执行任一方面及任一方面的任一可能的实现中的发送动作或接收动作。
第八方面，本申请提供了一种芯片系统，该芯片系统包括一个或多个处理器(也可以称为处理电路)，所述处理器与存储器(也可以称为存储介质)之间电耦合；所述存储器可以位于所述芯片系统中，也可以不位于所述芯片系统中；所述存储器，用于存储计算机程序或指令；所述处理器，用于执行所述存储器中的部分或者全部计算机程序或指令，当所述部分或者全部计算机程序或指令被执行时，用于实现上述任一方面及任一方面的任一可能的实现的方法中的功能。
在一种可能的实现中，所述芯片系统还可以包括输入输出接口(也可以称为通信接口)，所述输入输出接口，用于输出所述处理器处理后的信号，或者接收输入给所述处理器的信号。所述输入输出接口可以执行任一方面及任一方面的任一可能的实现中的发送动作或接收动作。具体的，输出接口执行发送动作，输入接口执行接收动作。
在一种可能的实现中，该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第九方面，提供了一种计算机可读存储介质，用于存储计算机程序，所述计算机程序包括用于实现任一方面及任一方面的任一可能的实现中的功能的指令。
或者，一种计算机可读存储介质，用于存储计算机程序，所述计算机程序被计算机执行时，可以使得所述计算机执行上述任一方面及任一方面的任一可能的实现的方法。
第十方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述任一方面及任一方面的任一可能的实现中的方法。
第十一方面，提供了一种通信系统，所述通信系统包括执行上述第一方面至第三方面及第一方面至第三方面任一可能的实现的方法中的虚拟交换机、第一虚拟端口设备和第一工业设备。或者，所述通信系统包括执行上述第四方面至第五方面及第四方面至第五方面任一可能的实现的方法中的虚拟交换机和第一工业设备。
一种示例中，虚拟交换机，用于生成第一信息，所述第一信息用于指示第一设备标识和第一端口标识，所述第一设备标识为所述虚拟交换机的标识，所述第一端口标识包括至少一个虚拟端口设备的标识；
第一虚拟端口设备，用于接收来自虚拟交换机的第一信息，并向第一工业设备发送LLDP报文，所述LLDP报文中包括第一LLDP PDU，所述第一LLDP PDU中的第一设备标识为所述虚拟交换机的标识，所述第一LLDP PDU中的第一端口标识包括至少一个虚拟端口设备的标识，所述第一LLDP PDU用于确定所述第一工业设备的别名。
第一工业设备，用于接收来自第一虚拟端口设备的LLDP报文，并基于所述第一设备标识和所述第一端口标识，确定所述第一工业设备的别名。
一种示例中，所述第一信息为业务消息；所述业务消息的消息体包括所述第一LLDP PDU。
一种示例中，所述第一信息还包括第一指示信息，所述第一指示信息用于指示透传所述第一LLDP PDU。
一种示例中，所述第一虚拟端口设备，还用于基于所述第一信息指示的第一设备标识和第一端口标识，生成所述第一LLDP PDU。
一种示例中，所述虚拟交换机，还用于向所述第一虚拟端口设备发送第二指示信息，所述第二指示信息用于指示由所述第一虚拟端口设备生成LLDP PDU；
所述第一虚拟端口设备，还用于接收来自所述虚拟交换机的第二指示信息。
一种示例中，第一虚拟端口设备，用于接收来自控制设备的发现消息，触发生成所述第一LLDP PDU，所述发现消息用于指示获取所述第一工业设备信息。
一种示例中，所述第一虚拟端口设备，还用于在向第一工业设备发送所述LLDP报文之后，向所述第一工业设备发送所述发现消息，所述发现消息用于指示获取所述第一工业设备的相关参数信息；并接收来自所述第一工业设备的应答消息，所述应答消息包括所述第一工业设备的相关参数信息；以及向所述控制设备发送所述应答消息，所述应答消息中包括所述第一工业设备的相关参数信息；
一种示例中，所述第一工业设备，还用于接收发现消息，所述发现消息中包括所述第一工业设备的别名，所述发现消息用于指示获取所述第一工业设备的相关参数信息；发送应答消息，所述应答消息中包括所述第一工业设备的相关参数信息；以及接收第一参数信息，所述第一参数信息为所述第一工业设备所替换的旧工业设备的相关参数信息，所述相关参数信息中不包括所述旧工业设备的媒体存取控制地址MAC。
上述第六方面至第十一方面的技术效果可以参照第一方面至第五方面中的描述，重复之处不再赘述。
附图说明
图1a为本申请实施例中提供的一种LLDP报文格式示意图；
图1b为本申请实施例中提供的一种LLDPDU格式示意图；
图2a为本申请实施例中提供的一种通信系统结构示意图；
图2b为本申请实施例中提供的一种通信系统结构示意图；
图2c为本申请实施例中提供的一种通信系统结构示意图；
图3a为本申请实施例中提供的一种通信系统架构示意图；
图3b为本申请实施例中提供的一种通信方法流程图；
图4为本申请实施例中提供的一种通信方法流程图；
图5为本申请实施例中提供的一种通信方法流程图；
图6为本申请实施例中提供的一种通信方法流程图；
图7为本申请实施例中提供的一种通信方法流程图；
图8为本申请实施例中提供的一种通信系统架构示意图；
图9为本申请实施例中提供的一种通信方法流程图；
图10为本申请实施例中提供的一种通信方法流程图；
图11为本申请实施例中提供的一种通信系统架构示意图；
图12为本申请实施例中提供的一种通信方法流程图；
图13为本申请实施例中提供的一种通信装置结构图；
图14为本申请实施例中提供的一种通信装置结构图。
具体实施方式
为便于理解本申请实施例，以下对本申请实施例的部分用语进行解释说明，以便于本领域技术人员理解。
1)、链路层发现协议(link layer discovery protocol，LLDP)：
LLDP定义在802.1ab中，它是一个二层协议。LLDP提供了一种标准的链路层发现方式，可以将本端节点的主要能力、管理地址、设备标识、接口标识等信息组织成不同的类型/长度/值(type/length/value，TLV)，封装在链路层发现协议数据单元(link layer discovery protocol packet data unit，LLDP PDU，也可以简称为LLDPDU)中发布给与自己直连的节点。直连的节点收到这些信息后将其以标准管理信息库(management information base，MIB)的形式保存起来，以供网络管理系统查询及判断链路的通信状况。
LLDP是一个用于信息通告和获取的协议，LLDP发送的信息通常不需要确认，不能用来请求获取某些信息，LLDP是一个单向的协议，只有主动通告这一种工作方式，无需确认，不能查询、请求。
封装有LLDPDU的报文称为LLDP报文，如图1a所示，提供了一种LLDP报文格式示意图，其中：
Destination MAC address：表示目的媒体存取控制位址(media access control address，MAC)地址，为固定的组播MAC地址0x0180-C200-000E。MAC地址也叫物理地址、硬件地址，由制造商生产时烧录在网卡中的，不可修改。
Source MAC address：表示源MAC地址，为端口MAC地址或设备桥MAC地址，如果有端口地址则使用端口MAC地址，否则使用设备桥MAC地址。
Type：表示报文类型，通常为0x88CC。
Data：数据，为LLDPDU。
FCS：帧检验序列(frame check sequence，FCS)，让接收帧的网卡或接口判断是否发生了错误。
LLDPDU是封装在LLDP报文数据部分的数据单元。在组成LLDPDU之前，设备先将本地信息封装成TLV格式，再由若干个TLV组合成一个LLDPDU封装在LLDP报文的数据部分。如图1b所示，提供了一种LLDPDU格式示意图，目前的每个LLDPDU最多可携带28种TLV，其中Chasis ID TLV、端口标识Port ID TLV、Time To Live TTL TLV和End TLV这四种是必须携带的，其余的TLV则为可选携带。
Chassis ID TLV，用于表示该LLDPDU发送者的chassis ID，实际上是用于标识设备的，在本申请中将其称为设备标识。
Port ID TLV，用于表示发送该LLDPDU的设备的端口。
TTL TLV，用于表示这些信息的有效期有多长。
End TLV，用于表示LLDPDU结束。
2)发现和配置协议(discovery and basic configuration protocol，DCP)，其工作在数据链路层。DCP在PROFINET中有设置(Set)，识别(ldentify)，Hello，获取(Get)四大功能。下面以Set和Identify为例分别介绍。
设置(Set)请求：配置的内容主要是网络参数和辅助功能，包括IP地址，子网掩码，网关，设备名称，闪烁识别等。设备名称类似于以太网的域名，相比较而言，域名是国际唯一的，而设备名称只要保证在控制网络中唯一即可；域名通过DNS解析为IP地址，而 设备名称与MAC地址相绑定，都是为了更好的记忆和使用通信网络。
设置(Set)应答：发送端发送设置(Set)请求帧后，接收端在设置(Set)应答中返回相应的数据信息。
识别(Identify)请求：主要用来扫描网络中的PN设备，该帧只需要源MAC地址就可以了，目标地址一般为广播MAC，所有接收到该帧的设备(包括控制器)都进行应答，就可以知到网络中的设备信息，为后续建立连接做准备。
识别(Identify)应答：扫描所有的设备，设备会应答所有的数据，包括IP，设备名称，厂家信息，MAC地址，设备别名等。
3)PROFINET(简称PN)IO设备的替换机制：
早期的PROFINET IO设备需要插入多媒体卡(multimedia card，MMC)，MMC卡用来存储PN IO设备的设备名。当接口模块发生故障需要更换时，只需要把MMC卡插入到新的模块中即可恢复PROFINET IO设备通讯，编程器(programmer，PG)/个人电脑(personal computer，PC)对该IO设备进行重新组态，节约了维护的成本。
支持PROFINET的“设备更换无需可移动介质/PG”功能的IO设备在更换过程中无需插入可移动介质(例如MMC)或无需PG为其分配设备名。替换后的新IO设备的设备名由IO控制器(例如PLC)分配，而不是由可移动介质或PG分配。为此，替换的新IO设备的IO控制器和邻近的PROFINET设备必须支持PROFINET的“设备更换无需可移动介质/PG”功能。“设备更换无需可移动介质/PG”功能基于LLDP协议实现的。
4)用户面功能(user plane function，UPF)网元负责终端设备中用户数据的转发和接收。可以从数据网络接收用户数据，通过接入网设备传输给终端设备；用户面网元还可以通过接入网设备从终端设备接收用户数据，转发到数据网络。用户面网元中为终端设备提供服务的传输资源和调度功能由SMF网元管理控制的。在5G通信系统中，该用户面网元可以是用户面功能(user plane function，UPF)网元。在未来通信系统中，用户面网元仍可以是UPF网元，或者，还可以有其它的名称，本申请不做限定。本申请可以将UPF部署在工业园区中，作为工业园区内的用户面的服务器。
5)无线接入网设备(radio access network，RAN)是一种为终端设备提供无线通信功能的设备，本申请中的RAN设备包括但不限于：5G中的下一代基站(g nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(baseBand unit，BBU)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同，例如，在第五代(5th generation，5G)系统中，称为RAN或者gNB(5G NodeB)；在LTE系统中，称为演进的节点B(evolved NodeB，eNB或者eNodeB)；在第三代(3rd generation，3G)系统中，称为节点B(Node B)等。
为便于理解本申请实施例的技术方案，下面将对本申请实施例提供的方法的系统架构进行简要说明。可理解的，本申请实施例描述的系统架构是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定。
本申请实施例的技术方案可以应用于各种通信系统，例如：卫星通信系统、传统的移动通信系统。其中，所述卫星通信系统可以与传统的移动通信系统(即地面通信系统)相 融合。通信系统例如：无线局域网(wireless local area network，WLAN)通信系统，无线保真(wireless fidelity，WiFi)系统，长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、第五代(5th generation，5G)系统或新无线(new radio，NR)，第六代(6th generation，6G)系统，以及其他未来的通信系统等，还支持多种无线技术融合的通信系统，例如，还可以应用于无人机、卫星通信系统、高空平台(high altitude platform station，HAPS)通信等非地面网络(non-terrestrial network，NTN)融合地面移动通信网络的系统。
为便于理解本申请实施例，接下来对本请的应用场景进行介绍，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
自动化控制系统IACS是由许多电子与控制器等元件所组成，其广泛应用于化工产业、造纸业、发电厂、石油天然气提炼，以及电信业等各个工业行业中。控制器占用空间大，且回路流程不易修改与维护，可编程逻辑控制器(PLC)的出现使得这些问题得以决解。
如图2a所示，提供了一种在PLC大规模引入自动化控制系统后，工业自动化系统的组网结构：一个主控PLC和其他输入输出IO设备等节点通过一个交换机(Switch，SW)进行连接。在交换机的北向设置可以实施管理的管理节点(例如PLC)。不同节点之间的通信均通过有线的方式进行连接，例如铜线、双绞线、光纤等。
当IO设备发生故障或者其它原因，则需要对IO设备进行替换。结合图1a所示，以新IO设备替换IO2设备为例，对IO设备替换的过程进行介绍。
基于链路层发现协议LLDP，IO设备、PLC等节点可以与交换机互相交换各自的信息，例如设备名、端口号等。如下表1所示，介绍了根据链路层发现协议LLDP，每个设备与其直连节点对应的信息。
表1：
Figure PCTCN2022137353-appb-000001
由表1可以看出，本端设备的端口连接对端设备的端口，对于本端设备来说，对端设备的别名为：本端设备的端口标识.本端设备标识。
例如，Switch的Port 01连接PLC的Port 01，则对于PLC来说，Switch的别名为Port01.PLC；对于Switch来说，PLC的别名为Port01.Switch；
例如，Switch的Port 02连接IO1的Port 01，则对于IO1来说，Switch的别名为Port01.IO1；对于Switch来说，IO1的别名为Port02.Switch；
例如，Switch的Port 03连接IO2的Port 01，则对于IO2来说，Switch的别名为Port01.IO2；对于Switch来说，IO2的别名为Port03.Switch。
当新IO设备替换IO2设备接入到SW(新IO设备接入的SW的端口为IO2设备接入的SW的端口)上后，新IO设备初始设置中无设备名，也无别名。
SW与新IO设备相互发送LLDP报文，告知自身的信息。例如，SW向新IO设备发送LLDP报文，LLDPPDU中的设置标识为SW，端口标识为SW的Port03上，则新IO设备可以将自己的别名设置为Port03.Switch。然后由PLC通过发现和配置协议DCP发现新IO设备的别名后，再进一步为该新IO设备设置其他参数，该其它参数中包括新IO设备的设备名，还有业务参数等。新IO设备的设备名为该新IO设备所替换下去的IO设备的设备名，例如IO2。
可以理解的是，对于新IO来说，Switch的别名为Port01.IO2。
随着通信技术的进一步发展，以5G为代表的无线通信技术逐渐成为新的工业现场网络连接介质。无线通信技术可以将现有的PLC、IO设备等节点实现无线接入，实现了工业设备更加灵活的组网方式。
如图2b所示，提供了一种在引入无线通信系统后，可能的工业自动化系统的组网结构。在交换机和IO设备之间部署无线通信网络(例如5G网络)。例如，在交换机和IO设备之间部署一个或多个UPF网元、一个或多个RAN网元等。
如果IO设备具有无线网络接入能力，IO设备可以直接与RAN连接。但是目前也有一部分IO设备不具有无线网络(例如5G网络)接入能力，如图2c所示，可以在IO设备前部署一个或多个客户前置设备(customer premise equipment，CPE)，CPE是一种接收移动信号并以无线WIFI信号转发出来的移动信号接入设备。相当于为IO设备提供了无线网络的接入网口。一个CPE可以连接一个或多个IO设备。一个IO设备也可以连接一个或多个CPE。当一个IO设备连接多个CPE时，可以提高连接可靠性。IO设备与CPE之间通常为物理连接，通常CPE只有一个物理端口，一个CPE在物理上只能连接一个IO设备。当一个CPE连接多个IO设备时，CPE与IO设备之间可以部署一个SW，SW与CPE之间物理连接，一个SW可以连接多个IO设备，一个IO设备连接到一个SW上。
在无线接入网络下，SW与IO设备之间部署了多个网元，若多个设备之间仍采用链路层发现协议LLDP通信，则会出现以下情况：对于SW来说，UPF的别名为：Port01.SW；对于UPF来说，SW的别名为：Port01.UPF，RAN的别名为Port02.UPF等。对于RAN来说，UPF和CPE的别名为：RAN的端口标识.RAN设备标识。对于CPE来说，RAN和IO设备的别名为：CPE的端口标识，CPE设备标识。当新IO设备替换IO2设备接入到SW上后，新IO设备初始设置中无设备名，也无别名。交换机无法跨域转发LLDP报文，导致交换机SW无法再基于LLDP为新IO设备配置别名。
一种为新IO设备配置别名的方式为：由管理节点(例如PLC)维护CPE与IO设备之间的连接关系，管理节点可以获取正常组网下的各个设备(或称为节点)之间的连接关系。CPE向IO设备发送LLDP报文，其中的LLDP PDU包括的设备标识为所述CPE的标识，端口标识为所述CPE中的某一端口的标识。新IO设备的别名为：CPE中的端口的标识.CPE设备标识。管理节点可以通过发现和配置协议DCP发现新IO设备的别名后，再进一步为该新IO设备设置其他参数，例如新IO设备的设备名、业务参数等。一方面，目前大部分CPE不支持自身主动发送LLDP报文。另一方面，当一个CPE连接多个IO设备时，IO设备与CPE之间需要SW的连接，IO设备与CPE不再是直接连接，CPE无法跨域转发LLDP报文，CPE无法再基于LLDP为新IO设备配置别名。
基于此，本申请提出了多种技术方案，来实现无线组网下，为新IO设备配置别名，以实现新IO设备加入无线组网架构。本申请的方案可以适用于多种场景，有较好的兼容性。
在无线网络下，网元之间通信的端口通常是逻辑端口，不是物理端口，逻辑端口无法区分，可以找到一个点来作为所谓的“物理端口”。本申请将工业设备(例如IO设备)接入的虚拟端口设备来作为所谓的“物理端口”。虚拟交换机类似于表1中的交换机SW；将虚拟端口设备作为虚拟交换机的虚拟端口，虚拟端口设备类似于表1中的端口：port1、port2、port3。工业设备的别名可以基于虚拟交换机的设备名和虚拟端口设备的设备名确定。
本申请的虚拟交换机例如UPF、移动边缘计算(mobile edge computing，MEC)节点、网关(gateway，GW)等。虚拟端口设备例如交换机、路由器、终端、CPE、网桥等能够使工业设备接入的网关设备。工业设备例如IO设备等。
接下来将结合附图对方案进行详细介绍。附图中以虚线标识的特征或内容可理解为本申请实施例的可选操作或者可选结构。
本申请涉及的多个实施例之间可以相互参考，多个实施例之间也可以相互组合作为一个实施例。实施例中标“×”的设备为需要被替换的设备，例如图3a、图3b、图8、图11、图12中的第二工业设备被第一工业设备替换掉。
实施例1：
如图3a所示，介绍了一种通信系统示意图，虚拟交换机通过RAN连接一个或多个虚拟端口设备，第一虚拟端口设备为组网中的任一虚拟端口设备，每个虚拟端口设备连接一个工业设备，一个工业设备可以连接一个或多个虚拟端口设备。第一虚拟端口设备连接第二工业设备，第二工业设备连接至少一个虚拟端口设备，至少一个虚拟端口设备中包括所述第一虚拟端口设备。第二工业设备故障或其它原因，第一工业设备用于替换第二工业设备。替换后，第一工业设备保持与第二工业设备相同的连接关系，且工业设备的别名不会发生变化。本实施例中涉及的连接关系可以是5G连接，WiFi连接等无线连接，也可以是铜线、光线、双绞线等有线连接。
如图3b所示，介绍了一种通信方法流程图，该方法可以适用于图3a所示的通信系统，包括以下步骤：
步骤301：虚拟交换机(例如称为VSW)向第一虚拟端口设备(例如称为VPORT)发送第一信息，相应的，第一虚拟端口设备接收来自虚拟交换机的第一信息。
所述第一信息用于指示第一设备标识和第一端口标识，所述第一设备标识和所述第一端口标识用于生成第一链路层发现协议分组数据单元LLDP PDU。所述第一LLDP PDU用于确定工业设备的别名。
在本实施例中，所述第一设备标识为所述虚拟交换机的标识，所述第一端口标识包括至少一个虚拟端口设备的标识。虚拟端口设备的标识可以是虚拟端口设备的国际移动设备身份码IMEI。
本申请可以由虚拟交换机来生成第一LLDP PDU，也可以由第一虚拟端口设备生成第一LLDP PDU。
可以理解的是，虚拟交换机通过RAN向第一虚拟端口设备发送第一信息。
步骤302：第一虚拟端口设备向第一工业设备发送LLDP报文，相应的，第一工业设备接收来自第一虚拟端口设备的LLDP报文。
所述LLDP报文中包括所述第一LLDP PDU。所述第一LLDP PDU中的第一设备标识为所述虚拟交换机的标识，所述第一LLDP PDU中的第一端口标识包括至少一个虚拟端口设备的标识，所述第一LLDP PDU用于确定所述第一工业设备的别名。
在一种可选的示例中，由虚拟交换机来生成第一LLDP PDU，并将第一LLDP PDU发送给第一虚拟端口设备。例如，所述第一信息为业务消息；所述业务消息的消息体包括所述第一LLDP PDU。也就是虚拟交换机在生成的第一LLDP PDU外再加一层消息头，将整个消息发给第一虚拟端口设备。第一虚拟端口设备可以解析业务消息，得到第一LLDP PDU，并将第一LLDP PDU封装成LLDP报文。这种方式对于虚拟端口设备来说，只需要解析透传即可，实现比较简单。
可选的，虚拟交换机还可以向第一虚拟端口设备发送第一指示信息，相应的，第一虚拟端口设备接收来自虚拟交换机的第一指示信息，第一指示信息用于指示透传所述第一LLDP PDU。第一指示信息可以携带在第一信息中，也可以是在不同于第一信息的其它信息中携带。这样虚拟端口设备可以准确及时地透传该业务消息中的第一LLDP PDU，以避免与其它消息混乱，而未透传该业务消息中的第一LLDP PDU的情况。当然，虚拟交换机与第一虚拟端口设备可以相互约定，或者协议规定，由虚拟交换机来生成第一LLDP PDU，由第一虚拟端口设备透传第一LLDP PDU，这样就无需虚拟交换机向第一虚拟端口设备发送第一指示信息。
在一种可选的示例中，由第一虚拟端口设备来生成第一LLDP PDU。例如，第一信息指示第一设备标识为具体的虚拟交换机的标识，例如VSW1或VSW2或其它VSW。第一指示信息还可以指示第一端口标识为具体的虚拟端口设备的标识，例如，VPORT1或VPORT2或其它VPORT。这样，第一虚拟端口设备基于所述第一信息指示的第一设备标识和第一端口标识，生成所述第一LLDP PDU，并将第一LLDP PDU封装成LLDP报文。这种方式对于虚拟端口设备来说，在存储了端口标识和设备标识之后，可以随时向与该虚拟端口设备连接的工业设备发送LLDP报文，无需虚拟交换机的触发，这样确定新工业设备的别名的实效性更高，并且对于其它控制设备来说，这个过程是无感知的。
可以理解的是，如果一个工业设备连接到一个虚拟端口设备上，端口标识即为该工业设备连接到的一个虚拟端口设备的标识，此时，虚拟交换机可以无需向第一虚拟端口设备指示第一端口标识，或者虚拟交换机向第一虚拟端口设备指示第一端口标识即为第一虚拟端口设备标识本身。虚拟端口设备对上连接的是RAN，虚拟交换机(例如UPF)是变化的，对于虚拟端口设备来说是不可见的，通常虚拟端口设备不会保存有其连接的虚拟交换机的标识，但是同理，如果虚拟端口设备可以保存有其连接的虚拟交换机的标识，虚拟交换机可以无需向第一虚拟端口设备指示第一设备标识。
可选的，虚拟交换机还可以向第一虚拟端口设备发送第二指示信息，相应的，第一虚拟端口设备接收来自虚拟交换机的第二指示信息，第二指示信息用于指示由所述第一虚拟端口设备生成LLDP PDU。这样虚拟端口设备可以及时准确地生成LLDP PDU，以避免虚拟端口设备将该第一指示信息与接收的其它信息混乱，而不知道作何处理的情况。当然，虚拟交换机与第一虚拟端口设备可以相互约定，或者协议规定，由第一虚拟端口设备来生成第一LLDP PDU，这样就无需虚拟交换机向第一虚拟端口设备发送第二指示信息。
在由第一虚拟端口设备来生成第一LLDP PDU的情况下，第一虚拟端口设备可以是在接收到来自虚拟交换机的第二指示信息时，触发生成第一LLDP PDU。或者，第一虚拟端 口设备可以是接收来自控制设备的发现消息，触发生成所述第一LLDP PDU，所述发现消息用于指示获取所述第一工业设备信息。该发现消息是控制设备发送给虚拟交换机后，虚拟交换机发送给第一虚拟端口设备的。在控制设备未向工业设备发送发现消息的情况下，通常是未发生工业设备的替换事件的，如果在此期间，虚拟端口设备向工业设备发送LLDP报文，这个过程会浪费信令。所以第一虚拟端口设备可以在接收到来自控制设备的发现消息时，再触发生成所述第一LLDP PDU，这时发送不会造成信令浪费。
步骤303：第一工业设备基于所述第一LLDP PDU中的所述第一设备标识和所述第一端口标识，确定所述第一工业设备的别名。
例如，第一工业设备确定自身的别名为：第一端口标识.所述第一设备的标识，即所述至少一个虚拟端口设备的标识(VPORT).所述虚拟交换机的标识(例如VSW)。
在本申请中，别名只是一种示意，也可以是其它的表现形式，只要网络内各个设备相互约定好即可。例如可以是设备标识在前，端口标识在后，例如，VSW.VPORT。再例如，端口标识与设备标识之间可以采用其他的字符来代替，例如采用“-”，“_”等。
本实施例中，虚拟交换机向虚拟端口设备指示端口标识和设备标识，端口标识为虚拟端口设备标识，设备标识为虚拟交换机标识；虚拟端口设备基于虚拟交换机的指示来确定LLDP报文，并将LLDP报文发送给新的工业设备，以便新的工业设备基于LLDP报文中的LLDP PDU确定自身的别名。新的工业设备可以基于现有的LLDP协议的规范及现有的命名规则来确定唯一的别名。
在一种可选的示例中，控制设备可以基于工业设备的设备标识周期性地获取工业设备的相关参数信息，以便得到最新的网络关系。由于第二工业设备故障，控制设备基于第二工业设备的设备名向第二工业设备发送发现消息，会导致超时无法收到来自第二工业设备的响应。然后，控制设备可以基于第二工业设备的别名向第二工业设备发送发现消息，由于第二工业设备被第一工业设备所替换，第一工业设备会收到该发现消息，第一工业设备会把自己的相关参数信息上报给控制设备。控制设备还可以查询第二工业设备的相关参数信息，将第二工业设备的相关参数信息(不包括第二工业设备的媒体存取控制地址MAC)告知给第一工业设备，让第一工业设备进行参数信息的更新，以便实现业务的无损替换。
控制设备与工业设备之间的交互，都需要经过虚拟端口设备，例如，第一虚拟端口设备和第一工业设备执行如下过程：
所述第一虚拟端口设备向所述第一工业设备发送发现消息，相应的，所述第一工业设备接收发现消息；所述发现消息用于指示获取所述第一工业设备的相关参数信息。发现消息中包括第一工业设备的别名，例如VSW.VPORT。发现消息例如可以是发现和配置协议识别(DCP Identify)请求。
所述第一工业设备发送针对该发现消息的应答消息，相应的，所述第一虚拟端口设备接收来自所述第一工业设备的应答消息，所述应答消息包括所述第一工业设备的相关参数信息；例如，该应答消息例如可以是发现和配置协议识别(DCP Identify)应答。
第一虚拟端口设备向第一工业设备发送的发现消息是来自于控制设备的，则所述第一虚拟端口设备还可以向所述控制设备发送所述应答消息，所述应答消息中包括所述第一工业设备的相关参数信息。
控制设备在接收到应答消息后，可以向第一工业设备发送第一参数信息，相应的，所述第一工业设备接收第一参数信息，所述第一参数信息为所述第一工业设备所替换的第二 工业设备的相关参数信息，所述相关参数信息中不包括所述第二工业设备的媒体存取控制地址MAC。
如图4所示，介绍一种具体的通信过程示意图，在该示例中，一个CPE连接一个IO，一个IO连接一个CPE，由UPF生成LLDP PDU，CPE支持透传UPF构造的LLDP PDU。包括以下步骤：
步骤400：工业现场使能服务(industry field enable service，IFES)功能实体可以获取正常运转下的网络拓扑关系。
例如，获取工业设备(例如PLC，IO等)，无线网络新增的网元(例如UPF、RAN、CPE)等各个设备的相关参数信息及相互之间的连接关系等。
例如，IFES向全网设备采用组播的方式发送发现消息(例如DCP Identify all请求)，接收到该发现消息的设备就可以将自己的设备名、别名及其他的参数信息反馈给IFES。
IFES可以理解为一个APP，可以部署在UPF的平台上，也可以与UPF的部署平台分离开来。
该示例以IO2设备连接到CPE3，CPE3连接到UPF1上为例进行介绍，IFES可以获取到IO2设备的设备名为：IO2，IO2设备的别名为：CPE3.UPF1。
步骤401：UPF1生成业务消息，UPF1通过RAN向CPE3发送业务消息，相应的，CPE3接收来自UPF1的业务消息。
所述业务消息的消息体中包括LLDP PDU，所述LLDP PDU包括的设备标识为所述UPF1的标识，所述LLDP PDU包括的端口标识为所述CPE3标识。如表2所示，介绍一种UPF1构造的LLDP PDU的内容。
表2：
Figure PCTCN2022137353-appb-000002
UPF1生成的业务消息可以是对LLDP PDU进行再一次包装，现有技术中的LLDP PDU只能在相邻的两个节点中进行传递。在实际应用中，RAN也会向CPE发送LLDP报文，LLDP报文中也包括LLDP PDU。
UPF1在确定IO2设备故障或被替换，则可以触发生成业务消息。例如，UPF1基于IO2设备的设备名向IO2设备发送信息时，经常收不到响应，则可以确定需要替换该IO2设备。也可以是人工进行操作，来告诉UPF1有新IO设备对IO2设备进行替换。本申请对于UPF1如何确定需要替换IO2设备的过程不进行限制。通常，新IO设备与被替换的IO2设备的功能基本相同，甚至型号都相同，可以实现业务的无损替换。
可选的，CPE3向UPF1发送响应消息，以表示收到业务消息。
可以理解的是，UPF与RAN之间可能还会有交换机等设备，本申请不进行限定。UPF1直接或通过其它网元与所述CPE连接。
步骤402：CPE3解析业务消息，得到所述LLDP PDU，并生成LLDP报文，LLDP报文的报文体即为解析得到的LLDP PDU。
也可以理解为CPE3将业务消息转换为层2标准的LLDP PDU。
LLDP PDU中包括的设备标识为所述UPF1的标识，包括的端口标识为所述CPE3标识。
步骤403：CPE3向新IO设备(IO2设备已被新IO设备替换)发送LLDP报文，新IO设备接收来自CPE3的LLDP报文，LLDP报文中包括LLDP PDU。
也可以理解为CPE3将LLDP PDU透传(转发)给新IO设备。
步骤404：新IO设备基于该LLDP报文中的LLDP PDU确定新IO设备的别名。
例如，新IO设备确定新IO设备的别名为：所述CPE3的标识.所述UPF1的标识。前文已经介绍，该别名只是一种示意，也可以是其它的表现形式，只要网络内的各个设备相互约定好即可。例如还可以是设备标识在前，端口名标识在后，例如，UPF1的标识.CPE3的标识。再例如，端口标识与设备标识之间可以采用其他的字符来代替，例如采用“-”，“_”等。
按照现有技术的逻辑，对于新IO设备来说，来自CPE3的LLDP PDU包括的设备标识为所述CPE3的标识，端口标识为所述CPE3中的某一端口的标识。而本申请中由于UPF1来生成LLDP PDU，LLDP PDU包括的设备标识为UPF1的标识、端口标识为CPE3标识，UPF1将LLDP PDU作为业务消息的消息体发送给CPE3，CPE3将LLDP PDU透传给新IO设备，则新IO设备接收到的LLDP PDU包括的设备标识为UPF1的标识、端口标识为CPE3标识，新IO设备确定的别名为UPF1的标识.所述CPE3的标识。
可选的，步骤405a：PLC向UPF1发送发现消息，相应的，UPF1接收来自PLC的发现消息。
发现消息用于获取工业设备的相关参数信息。
该发现消息可以是仅针对IO2设备发送的，例如，该发现消息中包括IO2设备的设备名。该发现消息也可以是针对全网设备发送的，该发现消息可以是个组播消息。
该发现消息例如可以是DCP identify请求。
可选的，步骤405b：UPF1向IFES发送来自PLC的发现消息，IFES接收来自UPF1的发现消息。
步骤405c：IFES向全网设备(主要指工业设备)发送发现消息，但是超时未收到来自IO2设备的响应，这时可以确定IO2故障。
IFES可以组播或单播的方式发送发现消息。
该发现消息可以来自UPF1，IFES可以替代PLC构造新旧设备参数替换流程，IFES自身来决定发送发现消息，这时，可以省略步骤405a和步骤405b。
在由PLC构造新旧设备参数替换流程时，不省略步骤405a和步骤405b。
步骤406：IFES可以根据预先保存的全网拓扑关系，确定IO2设备的别名，根据IO2设备的别名(例如CPE3标识.UPF1标识)向IO2设备发送发现消息。这时，新IO设备接收到该发现消息。
发现消息例如为DCP Identify请求。
IFES可以组播或单播的方式发送发现消息。
如表3所示，介绍了全网拓扑关系中各个设备的别名。
表3：
Figure PCTCN2022137353-appb-000003
由上述表3可以看出，PLC连接UPF1，UPF1连接CPE1、CPE2、CPE3，PLC连接到CPE1上，IO1设备连接到CPE2上，IO2设备连接到CPE3上，IO2设备故障后，新IO设备替换IO2设备连接到CPE3上。
对于UPF来说，IO1设备的别名为CPE2.UPF1；IO2设备和新IO设备的别名均为CPE3.UPF1；PLC的别名为CPE1.UPF1；或者，若PLC与UPF1之间无CPE1，则别名可以为port1.UPF1。
对于IO1设备来说，UPF1的别名为port1.IO1；
对于IO2设备来说，UPF1的别名为port1.IO2；
对于PLC来说，UPF1的别名为CPE1.UPF1或port1.PLC。
步骤407：新IO设备向IFES发送应答消息，该应答消息中包括所述新IO设备的相关参数信息。
应答消息例如为DCP Identify应答。可选的，应答消息中可以包括成功指示信息，例如在头部(header)中携带0x00，表示success的。
新IO设备的相关参数信息包括新IO设备的MAC地址，站点名称(NameOfStation)、设备角色(Device Role)、设备供应商(Device Vendor)、设备ID(Device ID)、设备选项(Device Options)、IP参数(IP Parameter)、DHCP参数(DHCParameter)、制造商特定参数(Manufacturer Specific Parameter)、别名(AliasName)。
步骤408：IFES查询存储的IO2设备的原有组态参数。
步骤409：IFES向新IO设备配置该原有组态参数中除MAC之外的旧参数。例如IO2设备的设备名，站点名称(NameOfStation)、设备角色(Device Role)、设备供应商(Device Vendor)、设备ID(Device ID)、设备选项(Device Options)、IP参数(IP Parameter)、DHCP参数(DHCParameter)、制造商特定参数(Manufacturer Specific Parameter)。
为尽量保证通信不中断，通过SET流程保证参数(除MAC外)的一致性，例如，IFES向新IO设备发送DCP Set请求，包括原有组态参数中除MAC之外的旧参数。参数来源是工业拓扑发现的历史存储。
步骤410：新IO设备向IFES发送响应(例如DCP Set应答)，表示收到DCP Set请求。
新IO设备已根据旧参数对自身的参数进行更新。
可以理解的是，IFES与新IO设备之间的交互，需要通过UPF1、CPE3之间的参与。
可选的，步骤411a：IFES向UPF1发送应答消息，所述应答消息中包括新IO地址的MAC地址。
除MAC外的其余旧参数保持不变。
应答消息例如为DCP Identify应答。
可选的，步骤411b：UPF1将来自IFES的应答消息发送给PLC。
通过让UPF扮演虚拟交换机、CPE扮演虚拟端口，实现对新IO设备的别名进行管理；并且基于已有拓扑，实现了对于原有设备的其余参数进行完整恢复，实现了相较于现有工业场景设备替换更加高效、可控的设备替换恢复机制，保障了业务的运行。
如图5所示，介绍一种具体的通信过程示意图，在该示例中，一个CPE连接一个IO，一个IO连接多个CPE，由UPF生成LLDP PDU。图5示例与图4的示例的区别包括：图4的示例中，一个IO连接一个CPE，图5的示例中，一个IO连接2个CPE。包括以下步骤：
步骤500：工业现场使能服务IFES功能实体可以获取正常运转下的网络拓扑关系。
该示例以IO2设备连接到CPE3和CPE4，CPE3和CPE4均连接到UPF1上为例进行介绍，IFES可以获取到IO2设备的设备名为：IO2，IO2设备的别名为：CPE3&CPE4.UPF1。
其余技术细节可以参考步骤400的介绍。
步骤501a：UPF1生成业务消息，UPF1通过RAN向CPE3发送业务消息，相应的，CPE3接收来自UPF1的业务消息。
步骤501b：UPF1生成业务消息，UPF1通过RAN向CPE4发送业务消息，相应的，CPE4接收来自UPF1的业务消息。
在步骤501a和步骤501b中，所述业务消息的消息体中包括LLDP PDU，所述LLDP PDU包括的设备标识为所述UPF1的标识，所述LLDP PDU包括的端口标识为所述CPE3标识和所述CPE4标识。保证双连接的每个连接发出的LLDPPDU携带的端口标识是一致的，进而保证第一工业设备收到的两个LLDPPDU是一致的。
步骤501a和步骤501b与步骤401类似，不同之处为：步骤401中的端口标识为CPE3标识，步骤501a和步骤501b中的端口标识为CPE3标识和CPE4的标识。其余技术细节可以参考步骤401的介绍。
UPF1可以向IO2设备连接的多个CPE中的至少一个CPE发送业务消息，也就是步骤501a和步骤501b可以都执行，也可以是执行其中之一。
步骤502a：CPE3解析业务消息，得到所述LLDP PDU，并生成LLDP报文，LLDP报文的报文体即为解析得到的LLDP PDU。
步骤502b：CPE4解析业务消息，得到所述LLDP PDU，并生成LLDP报文，LLDP报文的报文体即为解析得到的LLDP PDU。
步骤502a和步骤502b可以都执行，也可以是执行其中之一。步骤502a和步骤502b中的LLDP PDU相同。其余技术细节可以参考步骤402的介绍。
步骤503a：CPE3向新IO设备(IO2设备已被新IO设备替换)发送LLDP报文，新IO设备接收来自CPE3的LLDP报文，LLDP报文中包括LLDP PDU。
步骤503b：CPE4向新IO设备(IO2设备已被新IO设备替换)发送LLDP报文，新IO设备接收来自CPE4的LLDP报文，LLDP报文中包括LLDP PDU。
步骤503a和步骤503b可以都执行，也可以是执行其中之一。步骤503a和步骤503b中的LLDP PDU相同。其余技术细节可以参考步骤403的介绍。
步骤504：新IO设备基于该LLDP报文中的LLDP PDU确定新IO设备的别名。
例如，新IO设备确定新IO设备的别名为：所述CPE3的标识&所述CPE4的标识.所述UPF1的标识。其余技术细节可以参考步骤404的介绍。
可选的，步骤505a：PLC向UPF1发送发现消息，相应的，UPF1接收来自PLC的发现消息。
步骤505a与步骤405a相同，不再重复赘述。
可选的，步骤505b：UP1F向IFES发送来自PLC的发现消息，IFES接收来自UPF1的发现消息。
步骤505b与步骤405b相同，不再重复赘述。
步骤505c：IFES向全网设备(主要指工业设备)发送发现消息，但是超时未收到来自IO2设备的响应，这时可以确定IO2故障。
步骤505c与步骤405c相同，不再重复赘述。
步骤506：IFES可以根据预先保存的全网拓扑关系，确定IO2设备的别名，根据IO2设备的别名(例如CPE3标识&CPE4标识.UPF标识)向IO2设备发送发现消息。这时，新IO设备接收到该发现消息。
如表4所示，介绍了全网拓扑关系中各个设备的别名。
表4：
Figure PCTCN2022137353-appb-000004
由上述表4可以看出，PLC连接UPF1，UPF1连接CPE1、CPE2、CPE3，PLC连接CPE1上，IO1设备连接到CPE2上，IO2设备连接到CPE3和CPE4上，IO2设备故障后，新IO设备替换IO2设备连接到CPE3和CPE4上。
对于UPF来说，IO1设备的别名为CPE2.UPF1；IO2设备和新IO设备的别名均为CPE3&CPE4.UPF1；PLC的别名为CPE1.UPF1；或者，若PLC与UPF1之间无CPE1，则别名可以为port1.UPF1。
对于IO1设备来说，UPF1的别名为port1.IO1；
对于IO2设备来说，UPF1的别名为port1.IO2；
对于PLC来说，UPF1的别名为CPE1.UPF1或port1.PLC。
其余技术细节可以参考步骤406的介绍。
步骤507：新IO设备向IFES发送应答消息，该应答消息中包括所述新IO设备的相关参数信息。应答消息例如为DCP Identify应答。新IO设备的相关参数信息包括新IO设备的MAC地址。
步骤507与步骤407相同，不再重复赘述。
步骤508：IFES查询存储的IO2设备的原有组态参数。
步骤508与步骤407相同，不再重复赘述。
步骤509：IFES向新IO设备配置该原有组态参数中除MAC之外的旧参数。
例如IO2设备的设备名，以尽力保证通信不中断。
例如，IFES向新IO设备发送DCP Set请求，包括原有组态参数中除MAC之外的旧参数。
步骤509与步骤409相同，不再重复赘述。
步骤510：新IO设备向IFES发送响应(例如DCP Set应答)，表示收到DCP Set请求。
步骤510与步骤410相同，不再重复赘述。
可选的，步骤511a：IFES向UPF发送应答消息，所述应答消息中包括新IO地址的MAC地址，除MAC外的其余旧参数保持不变。应答消息例如为DCP Identify应答。
步骤511a与步骤411a相同，不再重复赘述。
可选的，步骤411b：UPF将来自IFES的应答消息发送给PLC。
步骤511b与步骤411b相同，不再重复赘述。
如图6所示，提供了一种具体的通信过程示意图，在该示例中，一个CPE连接一个IO，一个IO连接一个CPE，由CPE生成LLDP PDU。图6的示例与图4的示例的区别包括：图4的示例中，由UPF生成LLDP PDU，图6的示例中，由CPE生成LLDP PDU。包括以下步骤：
包括以下步骤：
步骤600(与步骤400相同)：工业现场使能服务IFES功能实体可以获取正常运转下的网络拓扑关系。
该示例以IO2设备连接到CPE3，CPE3连接到UPF1上为例进行介绍，IFES可以获取到IO2设备的设备名为：IO2，IO2设备的别名为：CPE3.UPF1。
步骤601：UPF1通过RAN向CPE3发送第一信息，相应的，CPE3接收来自UPF1的第一信息。
第一信息指示第一设备标识为UPF1。第一指示信息还可以指示第一端口标识为CPE3。这样，第一虚拟端口设备可以基于所述第一信息构造的LLDP PDU中的设备标识为UPF1，端口标识为CPE3。
可以理解的是，如果一个工业设备连接到一个虚拟端口设备上，端口标识即为该工业设备连接到的一个虚拟端口设备的标识，此时，虚拟交换机可以无需向第一虚拟端口设备指示第一端口标识。虚拟端口设备对上连接的是RAN，虚拟交换机(例如UPF)是变化的，对于虚拟端口设备来说是不可见的，通常虚拟端口设备不会保存有其连接的虚拟交换机的标识，但是同理，如果虚拟端口设备可以保存有其连接的虚拟交换机的标识，虚拟交换机 可以无需向第一虚拟端口设备指示第一设备标识。
可选的，虚拟交换机还可以向第一虚拟端口设备发送第二指示信息，相应的，第一虚拟端口设备接收来自虚拟交换机的第二指示信息，第二指示信息用于指示由所述第一虚拟端口设备生成LLDP PDU。当然，虚拟交换机与第一虚拟端口设备可以相互约定，或者协议规定，由第一虚拟端口设备来生成第一LLDP PDU，这样就无需向第一虚拟端口设备发送第二指示信息。
可选的，CPE3可以向UPF1发送响应消息，用于表示接收到来自UPF1的信息。
步骤602：CPE3保存用于构造LLDP PDU的相关参数，例如存储设备标识为UPF1的标识，端口标识为CPE3的标识。
可选的，步骤603a(与步骤405a相同)：PLC向UPF发送发现消息，相应的，UPF接收来自PLC的发现消息。
发现消息用于获取工业设备的相关参数信息。该发现消息可以是仅针对IO2设备发送的，例如，该发现消息中包括IO2设备的设备名。该发现消息也可以是针对全网设备发送的，该发现消息可以是个组播消息。该发现消息例如可以是DCP identify请求。
可选的，步骤603b(与步骤405b相同)：UPF1向IFES发送来自PLC的发现消息，IFES接收来自UPF1的发现消息。
可选的，步骤603c：IFES向全网设备(主要指IO设备)或IO2设备发送发现消息。
IFES可以组播或单播的方式发送发现消息。
步骤603c与步骤405c类似，不再重复赘述。
步骤604：CPE3生成LLDP报文，包括LLDP PDU，LLDP PDU基于步骤602存储的用于构造LLDP PDU的相关参数生成。
例如，LLDP PDU中的设备标识为UPF1的标识，端口标识为CPE3的标识。
CPE3可以基于步骤603c的发现消息，触发生成LLDP PDU。
如果不执行步骤603c，也可以是CPE3在步骤602之后，直接执行步骤604。
步骤605：CPE3向新IO设备(IO2设备已被新IO设备替换)发送步骤604生成的LLDP报文，新IO设备接收来自CPE3的LLDP报文，LLDP报文中包括LLDP PDU。
步骤606(与步骤404相同)：新IO设备基于该LLDP报文中的LLDP PDU确定新IO设备的别名。
例如，新IO设备确定新IO设备的别名为：所述CPE3的标识.所述UPF1的标识。
步骤607a：新IO设备向CPE3发送所述新IO设备的相关参数信息。
新IO设备的相关参数信息包括新IO设备的MAC地址，可以参考步骤407中的介绍。
步骤607b：CPE3将步骤605中的新IO设备的相关参数信息发送给IFES。
例如，CPE3向IFES发送应答消息，该应答消息中包括所述新IO设备的相关参数信息。
应答消息例如为DCP Identify应答。可选的，应答消息中可以包括成功指示信息，例如在头部(header)中携带0x00，表示success的。
步骤607a和步骤607b与步骤407类似。
该示例对于控制设备来说，在发送了DCP识别dentify请求后，不会出现等待超时的情况，可以提前收到响应，可以实现无感知的替换。
步骤608(与步骤408相同)：IFES查询存储的IO2设备的原有组态参数。
步骤609(与步骤409相同)：IFES向新IO设备配置该原有组态参数中除MAC之外的旧参数。例如IO2设备的设备名。
为尽量保证通信不中断，通过SET流程保证参数(除MAC外)的一致性，例如，IFES向新IO设备发送DCP Set请求，包括原有组态参数中除MAC之外的旧参数。
步骤610(与步骤410相同)：新IO设备向IFES发送响应(例如DCP Set应答)，表示收到DCP Set请求。
新IO设备已根据旧参数对自身的参数进行更新。
可以理解的是，IFES与新IO设备之间的交互，需要通过UPF1、CPE3之间的参与。
可选的，步骤611a(与步骤411a相同)：IFES向UPF1发送应答消息，所述应答消息中包括新IO地址的MAC地址。
除MAC外的其余旧参数保持不变。
应答消息例如为DCP Identify应答。
可选的，步骤611b(与步骤411b相同)：UPF1将来自IFES的应答消息发送给PLC。
在一种具体的通信过程中，若CPE支持DCP SET命令，则可将步骤607a-步骤610替换为以下过程：
CPE3中保存有被替换的IO2设备的相关参数信息，CPE3向新IO设备发送配置消息，用于配置被替换的IO2设备的相关参数信息。
可以通过SET流程保证参数(除MAC外)的一致性，例如，CPE3向新IO设备发送DCP Set请求，包括IO2设备原有的参数中除MAC之外的旧参数。
新IO设备向CPE3发送响应(例如DCP Set应答)，表示收到DCP Set请求，新IO设备已根据旧参数对自身的参数进行更新。可选的，应答消息中可以包括成功指示信息，例如在头部(header)中携带0x00，表示success的。
CPE3向IFES发送应答消息，所述应答消息中包括新IO地址的MAC地址，以及除MAC外的IO2设备的旧参数。
应答消息例如为DCP Identify应答。可选的，应答消息中可以包括成功指示信息，例如在头部(header)中携带0x00，表示success的。
一个CPE连接一个IO，一个IO连接多个CPE的情况下，也可以由CPE生成LLDP PDU，UPF向多个CPE发送第一信息，多个CPE向新IO设备发送LLDP报文，与图5的示例类似，不再详细介绍。
实施例2：
实施例1的示例也可以适用于某一虚拟端口设备(例如CPE)损坏的场景。
如图7所示，介绍了一种通信方法流程示意图，包括以下步骤：
步骤700：控制设备(例如IFES)获取了获取正常运转下的网络拓扑关系。
例如：IO2设备的设备名为：IO2，IO2设备的别名为：CPE3.UPF1。CPE3故障，CPE5上线后，完成认证，接入无线工业网络，UPF可以知道CPE5代替了原来的CPE3。
在向IO2设备配置别名的过程中，可以将LLDP PDU中的端口标识(例如CPE的国际移动设备身份码IMEI)由原来的CPE3改为CPE5，对于IO2设备就可以将自己的别名 由原来的CPE3.UPF1变为CPE5.UPF1。另外，SIM卡可以从旧机器(例如CPE3)中拔出来放到新机器(例如CPE5)中，则国际移动用户识别码(international mobile subscriber identity，IMSI)可以不变。
也就是说实施例1的图3b中的第一虚拟端口设备即为新的虚拟端口设备：CPE5，第一工业设备即为未被替换的工业设备：IO2设备。
步骤701：虚拟交换机(例如UPF1)向第一虚拟端口设备(例如CPE5)发送第一信息，相应的，第一虚拟端口设备接收来自虚拟交换机的第一信息。
具体细节可以参考步骤301的介绍，不再重复赘述。
步骤702：第一虚拟端口设备(例如CPE5)向第一工业设备(例如IO2设备)发送LLDP报文，相应的，第一工业设备接收来自第一虚拟端口设备的LLDP报文。
具体细节可以参考步骤302的介绍，不再重复赘述。
步骤703：第一工业设备(例如IO2设备)基于所述第一LLDP PDU中的所述第一设备标识和所述第一端口标识，确定所述第一工业设备的别名。
例如，第一工业设备确定自身的别名为：CPE5.UPF1。
可选的，步骤704：控制设备(例如IFES)基于第一工业设备(例如IO2设备)的设备名，向第一工业设备(例如IO2设备)发送发现消息。
发现消息例如为DCP Identify请求。IFES可以组播或单播的方式发送发现消息。
可选的，步骤705：第一工业设备(例如IO2设备)可以向控制设备(例如IFES)发送应答消息，该应答消息中包括第一工业设备(例如IO2设备)的别名，例如CPE5.UPF1，其余参数不变。
应答消息例如为DCP Identify应答。可选的，应答消息中可以包括成功指示信息，例如在头部(header)中携带0x00，表示success的。
仅替换CPE，即虚拟端口设备发生变化，设置一次下挂IO别名即可。
如表5所示，介绍了各个设备的别名。
表5：
Figure PCTCN2022137353-appb-000005
由上述表5可以看出，PLC连接UPF1，UPF1连接CPE1、CPE2、CPE3，PLC连接到CPE1上，IO1设备连接到CPE2上，IO2设备连接到CPE3上；CPE3故障后，CPE5替换CPE3。
对于UPF来说，IO1设备的别名为CPE2.UPF1；IO2设备原来的别名为CPE3.UPF1， IO2设备更新后的别名为CPE5.UPF；PLC的别名为CPE1.UPF1；或者，若PLC与UPF1之间无CPE1，则别名可以为port1.UPF1。
对于IO1设备来说，UPF1的别名为port1.IO1；
对于IO2设备来说，不管是否更新CPE，UPF1的别名为port1.IO2；
对于PLC来说，UPF1的别名为CPE1.UPF1或port1.PLC。
实施例3：
如图8所示，介绍了一种通信系统示意图，虚拟交换机通过RAN连接一个或多个虚拟端口设备，第一虚拟端口设备为组网中的任一虚拟端口设备，每个虚拟端口设备连接一个交换机，每个交换机SW连接多个工业设备，每个工业设备连接一个SW。第一虚拟端口设备连接第二工业设备和其它工业设备。第二工业设备故障或其它原因，第一工业设备用于替换第二工业设备。替换后，第一工业设备保持与第二工业设备相同的连接关系。本实施例中涉及的连接关系可以是5G连接，WiFi连接等无线连接，也可以是铜线、光线、双绞线等有线连接。
在图8所示的通信系统中，可以采用如图4所示的通信流程的核心思想：由虚拟交换机来构造LLDP PDU，以实现为第一工业设备(例如IO2设备)配置别名，及除MAC地址外的其他的相关参数信息。但是不同之处是，在图8所示的通信系统中，虚拟交换机将包含LLDP PDU的业务消息发送给交换机SW，交换机SW执行虚拟端口设备(例如CPE3)的功能来解析业务消息，得到LLDP PDU，并将LLDPPDU发送给第一工业设备。
在图8所示的通信系统中，也可以采用如图6所示的通信流程的思想：由虚拟交换机向虚拟端口设备下发用于构造LLDP PDU的设备标识和端口标识，由虚拟端口设备来构造LLDP PDU，以实现为第一工业设备(例如IO2设备)配置别名，及除MAC地址外的其他的相关参数信息。但是不同之处是，在图8所示的通信系统中，交换机SW执行虚拟端口设备(例如CPE3)功能，虚拟交换机向交换机SW下发用于构造LLDP PDU的设备标识和端口标识，虚拟交换机来构造LLDP PDU，将LLDP PDU发送给第一工业设备。
另外，需要对LLDP PDU中端口标识进行改动，相应的，第二工业设备(例如IO2设备)的别名、第一工业设备(例如新IO设备)的别名也会进行改动。例如均在原来的基础上加上了交换机的端口标识，交换机的端口标识是指交换机上与要被替换的工业设备(也是新的工业设备)连接的端口的标识。例如，第一LLDP PDU中的第一端口标识为第一虚拟端口设备的标识和交换机的端口标识。第一工业设备(例如新IO设备)、第二工业设备(例如IO2设备)的别名为：第一虚拟端口设备的标识-交换机的端口标识.虚拟交换机的标识。
例如，新IO设备连接到交换机SW的port2上，交换机SW连接到CPE3上，CPE3连接到UPF1上，则新IO设备的别名可以为：CPE3-2.UPF1，其中“2”表示交换机的端口标识。或者新IO设备的别名为：CPE3-port2.UPF1，或者port2-CPE3.UPF1，或者UPF1.port2-CPE3，新IO设备的别名可以是任何可以唯一表示新IO设备的变形方式。
接下来提供一种适用于如图7所述的通信系统的通信流程，在该示例中，交换机SW与新IO设备采用现有的方式进行信息交互，例如：
交换机向新IO设备发送LLDP报文，新IO设备接收来自交换机的LLDP报文，LLDP报文中的LLDP PDU中的设备标识为该交换机SW的标识，端口标识为该交换机的端口标识。
新IO设备基于LLDP PDU，来确定新IO设备的别名。例如，LLDP PDU中的设备标识为交换机SW的标识，端口标识为交换机的Port02，则新IO设备可以将自己的别名设置为Port02.Switch。
当控制设备向新IO设备发送发现消息，以获取新IO设备的相关参数信息时，新IO设备可以将自身的别名上报给控制设备。
IFES可以组播或单播的方式发送发现消息。
发现消息例如为DCP Identify请求，发现消息中可以包括IO2设备(即新IO设备)的别名。或者发现消息例如为DCP Identify all请求。
可以理解的是，控制设备与新IO设备之间的交互需要通过虚拟交换机、虚拟端口设备及交换机的准发。
如图9所示，介绍了一种适用于如图7所述的通信系统的通信流程，包括以下步骤：
步骤900：工业现场使能服务IFES功能实体可以获取正常运转下的网络拓扑关系。
该示例以IO2设备和IO3设备通过交换机SW连接到CPE3，CPE3连接到UPF1上，新IO设备替换故障的IO2设备为例进行介绍，IFES可以获取到IO2设备的设备名为：IO2，IO2设备的别名为：Port02.Switch，还可以获取到IO3设备的设备名为：IO3，IO3设备的别名为：Port03.Switch。
步骤901：交换机与新IO设备相互发送LLDP PDU，确定新IO设备的别名为Port02.Switch。
步骤902(与步骤405c相同)：IFES向全网设备(主要指工业设备)发送发现消息，但是超时未收到来自IO2设备的响应，这时可以确定IO2故障。
步骤903(与步骤406相同)：IFES可以根据预先保存的全网拓扑关系，确定IO2设备的别名，根据IO2设备的别名(例如Port02.Switch)向IO2设备发送发现消息。这时，新IO设备接收到该发现消息。
发现消息例如为DCP Identify请求。IFES可以组播或单播的方式发送发现消息。
上述的步骤902和步骤903也可以替换为IFES向全网设备(主要指工业设备)发送发现消息，新IO设备接收到该发现消息。
步骤904(与步骤407相同)：新IO设备向IFES发送应答消息，该应答消息中包括所述新IO设备的相关参数信息。
应答消息例如为DCP Identify应答。新IO设备的相关参数信息包括新IO设备的别名，MAC地址。
步骤905(与步骤408相同)：IFES查询存储的IO2设备的原有组态参数。
步骤906(与步骤409相同)：IFES向新IO设备配置该原有组态参数中除MAC之外的旧参数。例如IO2设备的设备名。
为尽量保证通信不中断，通过SET流程保证参数(除MAC外)的一致性，例如，IFES向新IO设备发送DCP Set请求，包括原有组态参数中除MAC之外的旧参数。参数来源是工业拓扑发现的历史存储。
步骤907(与步骤410相同)：新IO设备向IFES发送响应(例如DCP Set应答)，表示收到DCP Set请求。
新IO设备已根据旧参数对自身的参数进行更新。
可以理解的是，IFES与新IO设备之间的交互，需要通过UPF1、CPE3、SW之间的 参与。
如图10所示，介绍了一种适用于如图7所述的通信系统的通信流程，图10的示例与图9的示例的区别包括：IFES上保存的IO设备的别名中包括CPE和UPF的信息，而IO设备与交换机SW基于现有的方式确定的IO设备的别名中只有交换机的标识和交换机的端口标识，没有CPE和UPF的信息。控制设备向IO设备发送消息时，CPE需要具备映射别名功能，CPE会基于别名映射规则对该消息中的别名进行转换，以便IO设备能够识别出来。
步骤1000：工业现场使能服务IFES功能实体可以获取正常运转下的网络拓扑关系。
该示例以IO2设备和IO3设备通过交换机SW连接到CPE3，CPE3连接到UPF1上，新IO设备替换故障的IO2设备为例进行介绍，IFES可以获取到IO2设备的设备名为：IO2，IO2设备的别名为：CPE3-2.UPF(其中的“2”表示交换机的Port02)，还可以获取到IO3设备的设备名为：IO3，IO3设备的别名为：CPE3-3.UPF(其中的“3”表示交换机的Port03)。
步骤1001：交换机与新IO设备相互发送LLDP PDU，确定新IO设备的别名为Port02.Switch。
步骤1002：IFES向CPE3发送发现消息。
可选的，发现消息中可以包括IO2设备的别名CPE3-2.UPF。
发现消息例如为DCP Identify请求。IFES可以组播或单播的方式发送发现消息。
步骤1003：CPE3发送发现消息，新IO设备接收到该发现消息。
可选的，CPE3基于别名映射规则，将IO2设备的别名进行转换，例如将CPE3-2.UPF转换为Port02.Switch。CPE3向基于转换后的别名(例如Port02.Switch)发送发现消息。
步骤1004(与步骤407类似)：新IO设备向CPE3发送应答消息，该应答消息中包括所述新IO设备的相关参数信息。
应答消息例如为DCP Identify应答。可选的，应答消息中可以包括成功指示信息，例如在头部(header)中携带0x00，表示success的。
新IO设备的相关参数信息包括新IO设备的别名(此处的新IO设备的别名为与交换机确定的别名，例如Port02.Switch)，MAC地址，站点名称(NameOfStation)、设备角色(Device Role)、设备供应商(Device Vendor)、设备ID(Device ID)、设备选项(Device Options)、IP参数(IP Parameter)、DHCP参数(DHCParameter)、制造商特定参数(Manufacturer Specific Parameter)、别名(AliasName)。
步骤1005：CPE3基于别名映射规则，将IO2设备的别名进行转换，例如将Port02.Switch转换为CPE3-2.UPF。CPE3向IFES发送应答消息，该应答消息中包括所述新IO设备的相关参数信息。应答消息例如为DCP Identify应答。新IO设备的相关参数信息包括新IO设备的别名(此处的新IO设备的别名为转换后的别名，例如CPE3-2.UPF)，MAC地址，还可以包括上述步骤1004介绍的信息。
步骤1006(与步骤408相同)：IFES查询存储的IO2设备的原有组态参数。
步骤1007(与步骤409类似)：IFES向CPE3配置该原有组态参数中除MAC之外的旧参数。例如IO2设备的设备名，还可以包括上述步骤1004介绍的信息，步骤1007中可以无别名。
例如，IFES向新IO设备发送DCP Set请求，包括原有组态参数中除MAC之外的旧参数。
在配置时，发送给CPE3的消息中携带的IFES中保存的IO2设备的别名，例如CPE3-2.UPF。
步骤1008：CPE3基于别名映射规则，将IO2设备的别名进行转换，例如将CPE3-2.UPF转换为Port02.Switch。CPE3向IO设备配置该原有组态参数中除MAC之外的旧参数。例如IO2设备的设备名，还可以包括上述步骤1007介绍的信息。
步骤1009(与步骤410类似)：新IO设备通过CPE3向IFES发送响应(例如DCP Set应答)，表示收到DCP Set请求。
新IO设备已根据旧参数对自身的参数进行更新。
如表6所示，介绍了CPE3下的别名列表。表6介绍的内容可以参考表3、表4、表5的介绍，不再详细赘述。
表6：
Figure PCTCN2022137353-appb-000006
如下表7所示，介绍了网络侧下的别名列表。表7介绍的内容可以参考表3、表4、表5的介绍，不再详细赘述。
表7：
Figure PCTCN2022137353-appb-000007
实施例3：
如图11所示，介绍了一种通信系统示意图，虚拟交换机通过RAN连接一个或多个工 业设备，工业设备具有无线接入功能，可以省略虚拟端口设备，也可以理解为工业设备与虚拟端口设备合二为一。第二工业设备故障或其它原因，第一工业设备用于替换第二工业设备。替换后，第一工业设备保持与第二工业设备相同的连接关系，但是别名会发生变化。本实施例中涉及的连接关系可以是5G连接，WiFi连接等无线连接，也可以是铜线、光线、双绞线等有线连接。
如图12所示，介绍了一种通信方法流程图，该方法可以适用于图11所示的通信系统，图12的示例与图3b的示例的区别包括：
在图3b的示例中，由虚拟交换机生成包括LLDP PDU的业务消息，将业务消息发送给虚拟端口设备，虚拟端口设备解析出LLDP PDU后，构造LLDP报文，将LLDP报文发送给第一工业设备。在图12的示例中，由于第一工业设备中集成了虚拟端口设备的功能，所以，虚拟交换机生成的包括LLDP PDU的业务消息可以直接发送给第一工业设备，第一工业设备可以解析出LLDP PDU，从而根据LLDP PDU确定第一工业设备的别名。
图12包括以下步骤：
步骤1200：虚拟交换机向第一工业设备发送业务消息，相应的，第一工业设备接收来自虚拟交换机的业务消息。
所述业务消息的消息体包括第一链路层发现协议分组数据单元LLDP PDU，也就是虚拟交换机在生成的第一LLDP PDU外再加一层消息头，将整个消息发给第一工业设备。第一工业设备可以解析业务消息，得到第一LLDP PDU。
所述第一LLDP PDU用于确定工业设备的别名。
在本实施例中，所述第一LLDP PDU包括的第一设备标识为虚拟交换机的标识，所述第一LLDP PDU包括的第一端口标识为第一工业设备的永久设备身份码(permanent equipment identifier，PEI)或国际移动设备身份码(international mobile equipment identity，IMEI)。
工业设备在注册时，已经将自身的PEI和/或IMEI上报给网络侧，所以，虚拟端口设备是知道新的工业设备的PEI和/或IMEI。
在工业设备与虚拟端口设备合二为一的场景中，在发生工业设备替换时，新的工业设备的PEI和IMEI相对于原来的工业设备会发生变化，所以新的工业设备的别名相对于原来的工业设备的别名也会发生变化。例如，被替换的第二工业设备对应的设备名为IO2，别名为：CPE3.UPF1，第一工业设备的PEI/IMEI为CPE4，则第一工业设备的别名为：CPE4.UPF1。
可以理解的是，虚拟交换机通过RAN向第一工业设备发送业务信息。
步骤1201：第一工业设备基于所述第一设备标识和所述第一端口标识，确定所述第一工业设备的别名。
例如，第一工业设备确定自身的别名为：第一端口标识.所述第一设备的标识，即IMEI.所述虚拟交换机的标识。
该别名只是一种示意，也可以是其它的表现形式，只要网络内各个设备相互约定好即可。例如可以是设备标识在前，端口标识在后，例如，所述虚拟交换机的标识.IMEI。再例如，端口标识与设备标识之间可以采用其他的字符来代替，例如采用“-”，“_”等。
在该实施例中，第一工业设备也可以向控制设备上报自身的相关参数信息，控制设备可以向第一工业设备下发第二工业设备(第二工业设备损坏，由第一工业设备来替换)的 相关参数信息(不包括第二工业设备的媒体存取控制地址MAC)，以便实现业务的无损替换。这个过程与实施例1中介绍的过程相同，例如：
控制设备向所述第一工业设备发送发现消息，相应的，所述第一工业设备接收发现消息；所述发现消息用于指示获取所述第一工业设备的相关参数信息。发现消息中包括第一工业设备的别名。发现消息例如可以是发现和配置协议识别DCP Identify请求。
所述第一工业设备发送针对该发现消息的应答消息，相应的，所述控制设备接收来自所述第一工业设备的应答消息，所述应答消息包括所述第一工业设备的相关参数信息；例如，该应答消息例如可以是发现和配置协议识别DCP Identify应答。
控制设备在接收到应答消息后，可以向第一工业设备发送第一参数信息，相应的，所述第一工业设备接收第一参数信息，所述第一参数信息为所述第一工业设备所替换的第二工业设备的相关参数信息，所述相关参数信息中不包括所述第二工业设备的媒体存取控制地址MAC。
具体过程可以参考图4中的步骤405a至步骤411b的过程，例如可以参考图5中的步骤505a至步骤511b的过程，不再重复赘述。
虚拟交换机来生成包含LLDP PDU的业务消息，并将业务消息发送给新的工业设备，以便新的工业设备基于业务消息中的LLDP PDU确定自身的别名。新的工业设备可以基于现有的LLDP协议的规范及现有的命名规则来确定唯一的别名，将永久设备身份码PEI或国际移动设备身份码IMEI作为端口标识，从而实现新IO设备加入无线组网架构。
前文介绍了本申请实施例的方法，下文中将介绍本申请实施例中的装置。方法、装置是基于同一技术构思的，由于方法、装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
本申请实施例可以根据上述方法示例，对装置进行功能模块的划分，例如，可以对应各个功能划分为各个功能模块，也可以将两个或两个以上的功能集成在一个模块中。这些模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，具体实现时可以有另外的划分方式。
基于与上述方法的同一技术构思，参见图13，提供了一种通信装置1300结构示意图，该装置1300可以包括：处理模块1310，可选的，还包括接收模块1320a、发送模块1320b、存储模块1330。处理模块1310可以分别与存储模块1330和接收模块1320a和发送模块1320b相连，所述存储模块1330也可以与接收模块1320a和发送模块1320b相连。
在一种示例中，上述的接收模块1320a和发送模块1320b也可以集成在一起，定义为收发模块。
在一种示例中，该装置1300可以为第一虚拟端口设备，也可以为应用于第一虚拟端口设备中的芯片或功能单元。该装置1300具有上述方法中第一虚拟端口设备的任意功能，例如，该装置1300能够执行上述图3b、图4、图5、图6、图7、图9、图10、图12的方法中由第一虚拟端口设备执行的各个步骤。
所述接收模块1320a，可以执行上述方法实施例中第一虚拟端口设备执行的接收动作。
所述发送模块1320b，可以执行上述方法实施例中第一虚拟端口设备执行的发送动作。
所述处理模块1310，可以执行上述方法实施例中第一虚拟端口设备执行的动作中，除发送动作和接收动作外的其它动作。
在一种示例中，所述接收模块1320a，用于接收来自虚拟交换机的第一信息，所述第一信息用于指示第一设备标识和第一端口标识，所述第一设备标识为所述虚拟交换机的标识，所述第一端口标识包括至少一个虚拟端口设备的标识。
所述发送模块1320b，用于向第一工业设备发送链路层发现协议LLDP报文，所述LLDP报文中包括第一链路层发现协议分组数据单元LLDP PDU，所述第一LLDP PDU中的第一设备标识为所述虚拟交换机的标识，所述第一LLDP PDU中的第一端口标识包括至少一个虚拟端口设备的标识，所述第一LLDP PDU用于确定所述第一工业设备的别名。
在一种可能的实现中，所述第一信息可以为业务消息；所述业务消息的消息体包括所述第一LLDP PDU。
在一种可能的实现中，所述第一信息还可以包括第一指示信息，所述第一指示信息用于指示透传所述第一LLDP PDU。
在一种可能的实现中，所述处理模块1310，可以用于基于所述第一信息指示的第一设备标识和第一端口标识，生成所述第一LLDP PDU。
在一种可能的实现中，所述接收模块1320a，还用于接收来自虚拟交换机的第二指示信息，所述第二指示信息用于指示由所述第一虚拟端口设备生成LLDP PDU。
在一种可能的实现中，所述接收模块1320a，还用于接收来自控制设备的发现消息，触发生成所述第一LLDP PDU，所述发现消息用于指示获取所述第一工业设备信息。
在一种可能的实现中，所述发送模块1320b，还用于向所述第一工业设备发送所述发现消息，所述发现消息用于指示获取所述第一工业设备的相关参数信息。所述接收模块1320a，还用于接收来自所述第一工业设备的应答消息，所述应答消息包括所述第一工业设备的相关参数信息。所述发送模块1320b，还用于向所述控制设备发送所述应答消息，所述应答消息中包括所述第一工业设备的相关参数信息。
在一种示例中，所述存储模块1330，可以存储第一虚拟端口设备执行的方法的计算机执行指令，以使处理模块1310和接收模块1320a和发送模块1320b执行上述示例中第一虚拟端口设备执行的方法。
在一种示例中，该装置1300可以为虚拟交换机，也可以为应用于虚拟交换机中的芯片或功能单元。该装置1300具有上述方法中虚拟交换机的任意功能，例如，该装置1300能够执行上述图3b、图4、图5、图6、图7、图9、图10、图12的方法中由虚拟交换机执行的各个步骤。
所述接收模块1320a，可以执行上述方法实施例中虚拟交换机执行的接收动作。
所述发送模块1320b，可以执行上述方法实施例中虚拟交换机执行的发送动作。
所述处理模块1310，可以执行上述方法实施例中虚拟交换机执行的动作中，除发送动作和接收动作外的其它动作。
在一种示例中，所述处理模块1310，用于生成第一信息，所述第一信息用于指示第一设备标识和第一端口标识，所述第一设备标识和所述第一端口标识用于生成第一链路层发现协议分组数据单元LLDP PDU，其中，所述第一设备标识为所述虚拟交换机的标识，所述第一端口标识包括至少一个虚拟端口设备的标识；所述第一LLDP PDU用于确定第一工业设备的别名。所述发送模块1320b，用于向第一虚拟端口设备发送所述第一信息，所述至少一个虚拟端口设备包括所述第一虚拟端口设备。
在一种可能的实现中，所述第一信息可以为业务消息；所述业务消息的消息体包括所述第一LLDP PDU。
在一种可能的实现中，所述第一信息还可以包括第一指示信息，所述第一指示信息用于指示透传所述第一LLDP PDU。
在一种可能的实现中，所述发送模块1320b，还用于向第一虚拟端口设备发送第二指示信息，所述第二指示信息用于指示由所述第一虚拟端口设备生成LLDP PDU。
在一种示例中，所述存储模块1330，可以存储虚拟交换机执行的方法的计算机执行指令，以使处理模块1310和接收模块1320a和发送模块1320b执行上述示例中虚拟交换机执行的方法。
在一种示例中，该装置1300可以为第一工业设备，也可以为应用于第一工业设备中的芯片或功能单元。该装置1300具有上述方法中第一工业设备的任意功能，例如，该装置1300能够执行上述图3b、图4、图5、图6、图7、图9、图10、图12的方法中由第一工业设备执行的各个步骤。
所述接收模块1320a，可以执行上述方法实施例中第一工业设备执行的接收动作。
所述发送模块1320b，可以执行上述方法实施例中第一工业设备执行的发送动作。
所述处理模块1310，可以执行上述方法实施例中第一工业设备执行的动作中，除发送动作和接收动作外的其它动作。
在一种示例中，所述接收模块1320a，用于接收来自第一虚拟端口设备的LLDP报文，所述LLDP报文中包括第一链路层发现协议分组数据单元LLDP PDU；所述第一LLDP PDU包括的第一设备标识为虚拟交换机的标识，所述第一LLDP PDU包括的第一端口标识包括至少一个虚拟端口设备的标识；所述第一LLDP PDU用于确定所述第一工业设备的别名。所述处理模块1310，用于基于所述第一设备标识和所述第一端口标识，确定所述第一工业设备的别名。例如，别名为所述虚拟交换机的标识.所述至少一个虚拟端口设备的标识。
在一种可能的实现中，所述接收模块1320a，还用于可以接收发现消息，所述发现消息中包括所述第一工业设备的别名，所述发现消息用于指示获取所述第一工业设备的相关参数信息。所述发送模块1320b，还用于发送应答消息，所述应答消息中包括所述第一工业设备的相关参数信息。所述接收模块1320a，还用于接收第一参数信息，所述第一参数信息为所述第一工业设备所替换的旧工业设备的相关参数信息，所述相关参数信息中不包括所述旧工业设备的媒体存取控制地址MAC。
在一种示例中，所述存储模块1330，可以存储第一工业设备执行的方法的计算机执行指令，以使处理模块1310和接收模块1320a和发送模块1320b执行上述示例中第一工业设备执行的方法。
示例的，存储模块可以包括一个或者多个存储器，存储器可以是一个或者多个设备、电路中用于存储程序或者数据的器件。存储模块可以是寄存器、缓存或者RAM等，存储模块可以和处理模块集成在一起。存储模块可以是ROM或者可存储静态信息和指令的其他类型的静态存储设备，存储模块可以与处理模块相独立。
所述收发模块可以是输入或者输出接口、管脚或者电路等。
作为一种可能的产品形态，装置可以由一般性的总线体系结构来实现。
如图14所示，提供了一种通信装置1400的示意性框图。
该装置1400可以包括：处理器1410，可选的，还包括收发器1420、存储器1430。该收发器1420，可以用于接收程序或指令并传输至所述处理器1410，或者，该收发器1420可以用于该装置1400与其他通信设备进行通信交互，比如交互控制信令和/或业务数据等。该收发器1420可以为代码和/或数据读写收发器，或者，该收发器1420可以为处理器与收发机之间的信号传输收发器。所述处理器1410和所述存储器1430之间电耦合。
一种示例中，该装置1400可以为第一虚拟端口设备，也可以为应用于第一虚拟端口设备中的芯片。应理解，该装置具有上述方法中第一虚拟端口设备的任意功能，例如，所述装置1400能够执行上述图3b、图4、图5、图6、图7、图9、图10、图12的方法中由第一虚拟端口设备执行的各个步骤。示例的，所述存储器1430，用于存储计算机程序；所述处理器1410，可以用于调用所述存储器1430中存储的计算机程序或指令，执行上述示例中第一虚拟端口设备执行的方法，或者通过所述收发器1420执行上述示例中第一虚拟端口设备执行的方法。
一种示例中，该装置1400可以为虚拟交换机，也可以为应用于虚拟交换机中的芯片。应理解，该装置具有上述方法中虚拟交换机的任意功能，例如，所述装置1400能够执行上述图3b、图4、图5、图6、图7、图9、图10、图12的方法中由虚拟交换机执行的各个步骤。示例的，所述存储器1430，用于存储计算机程序；所述处理器1410，可以用于调用所述存储器1430中存储的计算机程序或指令，执行上述示例中虚拟交换机执行的方法，或者通过所述收发器1420执行上述示例中虚拟交换机执行的方法。
一种示例中，该装置1400可以为第一工业设备，也可以为应用于第一工业设备中的芯片。应理解，该装置具有上述方法中第一工业设备的任意功能，例如，所述装置1400能够执行上述图3b、图4、图5、图6、图7、图9、图10、图12的方法中由第一工业设备执行的各个步骤。示例的，所述存储器1430，用于存储计算机程序；所述处理器1410，可以用于调用所述存储器1430中存储的计算机程序或指令，执行上述示例中第一工业设备执行的方法，或者通过所述收发器1420执行上述示例中第一工业设备执行的方法。
图13中的处理模块1310可以通过所述处理器1410来实现。
图13中的接收模块1320a和发送模块1320b可以通过所述收发器1420来实现。或者，收发器1420分为接收器和发送器，接收器执行接收模块的功能，发送器执行发送模块的功能。
图13中的存储模块1330可以通过所述存储器1430来实现。
作为一种可能的产品形态，装置可以由通用处理器(通用处理器也可以称为芯片或芯片系统)来实现。
一种可能的实现方式中，实现应用于第一虚拟端口设备的装置或虚拟交换机的装置或第一工业设备的通用处理器包括：处理电路(处理电路也可以称为处理器)；可选的，还包括：与所述处理电路内部连接通信的输入输出接口、存储介质(存储介质也可以称为存储器)，所述存储介质用于存储处理电路执行的指令，以执行上述示例中第一虚拟端口设备或虚拟交换机或第一工业设备执行的方法。
图13中的处理模块1310可以通过处理电路来实现。
图13中的接收模块1320a和发送模块1320b可以通过输入输出接口来实现。或者，输 入输出接口分为输入接口和输出接口，输入接口执行接收模块的功能，输出接口执行发送模块的功能。
图13中的存储模块1330可以通过存储介质来实现。
作为一种可能的产品形态，本申请实施例的装置，还可以使用下述来实现：一个或多个FPGA(现场可编程门阵列)、PLD(可编程逻辑器件)、控制器、状态机、门逻辑、分立硬件部件、任何其它适合的电路、或者能够执行本申请通篇所描述的各种功能的电路的任意组合。
本申请实施例还提供了一种计算机可读存储介质，存储有计算机程序，该计算机程序被计算机执行时，可以使得所述计算机用于执行上述通信的方法。或者说：所述计算机程序包括用于实现上述通信的方法的指令。
本申请实施例还提供了一种计算机程序产品，包括：计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机可以执行上述提供的通信的方法。
本申请实施例还提供了一种通信的系统，所述通信系统包括：执行上述通信的方法的虚拟交换机、第一虚拟端口设备、第一工业设备。
另外，本申请实施例中提及的处理器可以是中央处理器(central processing unit，CPU)，基带处理器，基带处理器和CPU可以集成在一起，或者分开，还可以是网络处理器(network processor，NP)或者CPU和NP的组合。处理器还可以进一步包括硬件芯片或其他通用处理器。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)及其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等或其任意组合。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
本申请实施例中提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本申请描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例中提及的收发器中可以包括单独的发送器，和/或，单独的接收器，也可以是发送器和接收器集成一体。收发器可以在相应的处理器的指示下工作。可选的，发送器可以对应物理设备中发射机，接收器可以对应物理设备中的接收机。
本领域普通技术人员可以意识到，结合本文中所公开的实施例中描述的各方法步骤和 单元，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各实施例的步骤及组成。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。本领域普通技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分，或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
本申请中的“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。本申请中所涉及的多个，是指两个或两个以上。另外，需要理解的是，在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本申请实施例进行各种改动和变型而不脱离本申请实施例的精神和范围。这样，倘若本申请实施例的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包括这些改动和变型在内。

Claims (35)

  1. 一种通信方法，其特征在于，包括：
    第一虚拟端口设备接收来自虚拟交换机的第一信息，所述第一信息用于指示第一设备标识和第一端口标识，所述第一设备标识为所述虚拟交换机的标识，所述第一端口标识包括至少一个虚拟端口设备的标识；
    第一虚拟端口设备向第一工业设备发送LLDP报文，所述LLDP报文中包括第一LLDP PDU，所述第一LLDP PDU中的第一设备标识为所述虚拟交换机的标识，所述第一LLDP PDU中的第一端口标识包括至少一个虚拟端口设备的标识，所述第一LLDP PDU用于确定所述第一工业设备的别名。
  2. 如权利要求1所述的方法，其特征在于，所述第一信息为业务消息；所述业务消息的消息体包括所述第一LLDP PDU。
  3. 如权利要求2所述的方法，其特征在于，所述第一信息还包括第一指示信息，所述第一指示信息用于指示透传所述第一LLDP PDU。
  4. 如权利要求1所述的方法，其特征在于，还包括：
    所述第一虚拟端口设备基于所述第一信息，生成所述第一LLDP PDU。
  5. 如权利要求4所述的方法，其特征在于，还包括：
    所述第一虚拟端口设备接收来自虚拟交换机的第二指示信息，所述第二指示信息用于指示由所述第一虚拟端口设备生成LLDP PDU。
  6. 如权利要求4或5所述的方法，其特征在于，还包括：
    第一虚拟端口设备接收来自控制设备的发现消息，触发生成所述第一LLDP PDU，所述发现消息用于指示获取所述第一工业设备信息。
  7. 如权利要求1-6任一项所述的方法，其特征在于，在所述第一虚拟端口设备向第一工业设备发送所述LLDP报文之后，还包括：
    所述第一虚拟端口设备向所述第一工业设备发送所述发现消息，所述发现消息用于指示获取所述第一工业设备的相关参数信息；
    所述第一虚拟端口设备接收来自所述第一工业设备的应答消息，所述应答消息包括所述第一工业设备的相关参数信息；
    所述第一虚拟端口设备向所述控制设备发送所述应答消息，所述应答消息中包括所述第一工业设备的相关参数信息。
  8. 如权利要求1-7任一项所述的方法，其特征在于，还包括：
    所述虚拟交换机生成所述第一信息；
    所述虚拟交换机向所述第一虚拟端口设备发送所述第一信息，所述至少一个虚拟端口设备包括所述第一虚拟端口设备。
  9. 如权利要求1-7任一项所述的方法，其特征在于，还包括：
    所述第一工业设备接收来自所述第一虚拟端口设备的所述LLDP报文；
    所述第一工业设备基于所述第一设备标识和所述第一端口标识，确定所述第一工业设备的别名。
  10. 如权利要求9所述的方法，其特征在于，还包括：
    所述第一工业设备接收发现消息，所述发现消息中包括所述第一工业设备的别名，所 述发现消息用于指示获取所述第一工业设备的相关参数信息；
    所述第一工业设备发送应答消息，所述应答消息中包括所述第一工业设备的相关参数信息；
    所述第一工业设备接收第一参数信息，所述第一参数信息为所述第一工业设备所替换的旧工业设备的相关参数信息，所述相关参数信息中不包括所述旧工业设备的媒体存取控制地址MAC。
  11. 一种通信系统，其特征在于，包括：
    虚拟交换机，用于生成第一信息，所述第一信息用于指示第一设备标识和第一端口标识，所述第一设备标识为所述虚拟交换机的标识，所述第一端口标识包括至少一个虚拟端口设备的标识；
    第一虚拟端口设备，用于接收来自虚拟交换机的第一信息，并向第一工业设备发送LLDP报文，所述LLDP报文中包括第一LLDP PDU，所述第一LLDP PDU中的第一设备标识为所述虚拟交换机的标识，所述第一LLDP PDU中的第一端口标识包括至少一个虚拟端口设备的标识，所述第一LLDP PDU用于确定所述第一工业设备的别名；
    第一工业设备，用于接收来自第一虚拟端口设备的LLDP报文，并基于所述第一设备标识和所述第一端口标识，确定所述第一工业设备的别名。
  12. 如权利要求11所述的系统，其特征在于，所述第一信息为业务消息；所述业务消息的消息体包括所述第一LLDP PDU。
  13. 如权利要求12所述的系统，其特征在于，所述第一信息还包括第一指示信息，所述第一指示信息用于指示透传所述第一LLDP PDU。
  14. 如权利要求11所述的系统，其特征在于，所述第一虚拟端口设备，还用于基于所述第一信息指示的第一设备标识和第一端口标识，生成所述第一LLDP PDU。
  15. 如权利要求14所述的系统，其特征在于，所述虚拟交换机，还用于向所述第一虚拟端口设备发送第二指示信息，所述第二指示信息用于指示由所述第一虚拟端口设备生成LLDP PDU；
    所述第一虚拟端口设备，还用于接收来自所述虚拟交换机的第二指示信息。
  16. 如权利要求14或15所述的系统，其特征在于，第一虚拟端口设备，用于接收来自控制设备的发现消息，触发生成所述第一LLDP PDU，所述发现消息用于指示获取所述第一工业设备信息。
  17. 如权利要求11-16任一项所述的系统，其特征在于，所述第一虚拟端口设备，还用于：
    在向第一工业设备发送所述LLDP报文之后，向所述第一工业设备发送所述发现消息，所述发现消息用于指示获取所述第一工业设备的相关参数信息；
    接收来自所述第一工业设备的应答消息，所述应答消息包括所述第一工业设备的相关参数信息；以及
    向所述控制设备发送所述应答消息，所述应答消息中包括所述第一工业设备的相关参数信息。
  18. 如权利要求11-16任一项所述的系统，其特征在于，所述第一工业设备，还用于：
    接收发现消息，所述发现消息中包括所述第一工业设备的别名，所述发现消息用于指示获取所述第一工业设备的相关参数信息；
    发送应答消息，所述应答消息中包括所述第一工业设备的相关参数信息；以及
    接收第一参数信息，所述第一参数信息为所述第一工业设备所替换的旧工业设备的相关参数信息，所述相关参数信息中不包括所述旧工业设备的媒体存取控制地址MAC。
  19. 一种通信装置，其特征在于，包括：实现如权利要求1-10任一项所述的方法的功能模块。
  20. 一种通信装置，其特征在于，包括处理器，所述处理器与存储器耦合；
    所述存储器，用于存储计算机程序或指令；
    所述处理器，用于执行所述存储器中的部分或者全部计算机程序或指令，当所述部分或者全部计算机程序或指令被执行时，用于实现如权利要求1-10任一项所述的方法。
  21. 一种通信装置，其特征在于，包括处理器和存储器；
    所述存储器，用于存储计算机程序或指令；
    所述处理器，用于执行所述存储器中的部分或者全部计算机程序或指令，当所述部分或者全部计算机程序或指令被执行时，用于实现如权利要求1-10任一项所述的方法。
  22. 一种芯片系统，其特征在于，所述芯片系统包括：处理电路；所述处理电路与存储介质耦合；
    所述处理电路，用于执行所述存储介质中的部分或者全部计算机程序或指令，当所述部分或者全部计算机程序或指令被执行时，用于实现如权利要求1-10任一项所述的方法。
  23. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序包括用于实现权利要求1-10任一项所述的方法的指令。
  24. 一种计算机程序产品，其特征在于，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行如权利要求1-10任一项所述的方法。
  25. 一种通信方法，其特征在于，包括：
    虚拟交换机向第一虚拟端口设备发送第一信息，所述第一信息用于指示第一设备标识和第一端口标识，所述第一设备标识为所述虚拟交换机的标识，所述第一端口标识包括至少一个虚拟端口设备的标识；
    第一虚拟端口设备接收所述第一信息，并向第一工业设备发送LLDP报文，所述LLDP报文中包括第一LLDP PDU，所述第一LLDP PDU中的第一设备标识为所述虚拟交换机的标识，所述第一LLDP PDU中的第一端口标识包括至少一个虚拟端口设备的标识，所述第一LLDP PDU用于确定所述第一工业设备的别名。
  26. 如权利要求25所述的方法，其特征在于，还包括：
    所述第一工业设备接收所述LLDP报文，并基于所述第一设备标识和所述第一端口标识，确定所述第一工业设备的别名。
  27. 一种通信方法，其特征在于，包括：
    第一虚拟端口设备接收来自虚拟交换机的第一信息，所述第一信息用于指示第一设备标识和第一端口标识，所述第一设备标识为所述虚拟交换机的标识，所述第一端口标识包括至少一个虚拟端口设备的标识；
    所述第一虚拟端口设备向第一工业设备发送LLDP报文，所述LLDP报文中包括第一LLDP PDU，所述第一LLDP PDU中的第一设备标识为所述虚拟交换机的标识，所述第一LLDP PDU中的第一端口标识包括至少一个虚拟端口设备的标识，所述第一LLDP PDU用 于确定所述第一工业设备的别名；
    所述第一工业设备接收所述LLDP报文，并基于所述第一设备标识和所述第一端口标识，确定所述第一工业设备的别名。
  28. 如权利要求27所述的方法，其特征在于，还包括：
    所述虚拟交换机生成并向所述第一虚拟端口设备发送所述第一信息。
  29. 如权利要求25-28任一项所述的方法，其特征在于，所述第一信息为业务消息；所述业务消息的消息体包括所述第一LLDP PDU。
  30. 如权利要求29所述的方法，其特征在于，所述第一信息还包括第一指示信息，所述第一指示信息用于指示透传所述第一LLDP PDU。
  31. 如权利要求25-30任一项所述的方法，其特征在于，还包括：
    基于所述第一信息指示的第一设备标识和第一端口标识，所述第一虚拟端口设备生成所述第一LLDP PDU。
  32. 如权利要求31所述的方法，其特征在于，还包括：
    所述虚拟交换机向所述第一虚拟端口设备发送第二指示信息，所述第二指示信息用于指示由所述第一虚拟端口设备生成LLDP PDU；
    所述第一虚拟端口设备接收来自所述虚拟交换机的第二指示信息。
  33. 如权利要求31或32所述的方法，其特征在于，还包括：
    所述第一虚拟端口设备接收来自控制设备的发现消息，触发生成所述第一LLDP PDU，所述发现消息用于指示获取所述第一工业设备信息。
  34. 如权利要求25-33任一项所述的方法，其特征在于，还包括：
    所述第一虚拟端口设备向第一工业设备发送所述LLDP报文之后，向所述第一工业设备发送所述发现消息，所述发现消息用于指示获取所述第一工业设备的相关参数信息；
    所述第一虚拟端口设备接收来自所述第一工业设备的应答消息，所述应答消息包括所述第一工业设备的相关参数信息；以及
    所述第一虚拟端口设备向所述控制设备发送所述应答消息，所述应答消息中包括所述第一工业设备的相关参数信息。
  35. 如权利要求25-34任一项所述的方法，其特征在于，还包括：
    所述第一工业设备接收发现消息，所述发现消息中包括所述第一工业设备的别名，所述发现消息用于指示获取所述第一工业设备的相关参数信息；
    所述第一工业设备发送应答消息，所述应答消息中包括所述第一工业设备的相关参数信息；以及
    所述第一工业设备接收第一参数信息，所述第一参数信息为所述第一工业设备所替换的旧工业设备的相关参数信息，所述相关参数信息中不包括所述旧工业设备的媒体存取控制地址MAC。
PCT/CN2022/137353 2022-01-17 2022-12-07 一种通信方法及装置 WO2023134338A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210050568.9A CN114640973A (zh) 2022-01-17 2022-01-17 一种通信方法及装置
CN202210050568.9 2022-01-17

Publications (1)

Publication Number Publication Date
WO2023134338A1 true WO2023134338A1 (zh) 2023-07-20

Family

ID=81946609

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/137353 WO2023134338A1 (zh) 2022-01-17 2022-12-07 一种通信方法及装置

Country Status (2)

Country Link
CN (1) CN114640973A (zh)
WO (1) WO2023134338A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114640973A (zh) * 2022-01-17 2022-06-17 华为技术有限公司 一种通信方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020073903A1 (zh) * 2018-10-08 2020-04-16 华为技术有限公司 时延敏感网络通信方法及其装置
CN111327509A (zh) * 2020-01-21 2020-06-23 新华三信息安全技术有限公司 一种信息更新方法及装置
CN114640973A (zh) * 2022-01-17 2022-06-17 华为技术有限公司 一种通信方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020073903A1 (zh) * 2018-10-08 2020-04-16 华为技术有限公司 时延敏感网络通信方法及其装置
CN113473500A (zh) * 2018-10-08 2021-10-01 华为技术有限公司 时延敏感网络通信方法及其装置
CN111327509A (zh) * 2020-01-21 2020-06-23 新华三信息安全技术有限公司 一种信息更新方法及装置
CN114640973A (zh) * 2022-01-17 2022-06-17 华为技术有限公司 一种通信方法及装置

Also Published As

Publication number Publication date
CN114640973A (zh) 2022-06-17

Similar Documents

Publication Publication Date Title
CN105577736B (zh) 一种电力线载波通讯终端控制装置、系统及方法
US20220256393A1 (en) TSN AND 5GS QoS MAPPING - A USER PLANE BASED METHOD
CN111512691A (zh) 为冗余用户平面路径提供双连接性的方法和相关网络节点
US9648541B2 (en) Apparatus and method for forwarding data based on software defined network in communication network
US11134009B2 (en) Packet processing method and apparatus
CN110324225B (zh) 一种处理报文的方法及装置
JP6121548B2 (ja) パケットを送信するための方法、ルーティング・ブリッジ、およびシステム
US11855894B2 (en) Control system, server, terminal device, control device, communication control method, and recording medium
EP4075866A1 (en) Communication method and apparatus
WO2023134338A1 (zh) 一种通信方法及装置
CN113472595A (zh) 核心网子网切片创建方法、功能实体和切片管理系统
CN113632439A (zh) 支持虚拟以太网网桥管理的蜂窝通信系统
CN111277507A (zh) 实现无线终端间信息交换的方法
CN112995038B (zh) Profinet协议在工业sdn中的接入方法
EP3939215B1 (en) Filtering ethernet device source addresses for loop avoidance
CN108260147B (zh) 一种mesh网络节点的网络配置参数的配置方法
US11949555B2 (en) Setting country code in a network access device during an onboarding process
US9894474B2 (en) ZigBee system management employing a TR-069 enabled CPE proxy
WO2022267950A1 (zh) 一种通信方法和装置
WO2022143395A1 (zh) 一种冗余路径创建方法、装置及系统
JP2021510269A (ja) データ伝送方法及び装置、コンピュータ記憶媒体
WO2023019874A1 (zh) 分布式业务转发方法、装置、系统、存储介质及电子设备
WO2023284367A1 (zh) Dbng-up的备份方法及装置
US20240163753A1 (en) Handling layer 3 measurements of a user equipment
WO2023184542A1 (zh) 配置信息的方法、装置和通信系统

Legal Events

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

Ref document number: 22919971

Country of ref document: EP

Kind code of ref document: A1