WO2020024303A1 - Procédé et appareil de collecte de données - Google Patents

Procédé et appareil de collecte de données Download PDF

Info

Publication number
WO2020024303A1
WO2020024303A1 PCT/CN2018/098688 CN2018098688W WO2020024303A1 WO 2020024303 A1 WO2020024303 A1 WO 2020024303A1 CN 2018098688 W CN2018098688 W CN 2018098688W WO 2020024303 A1 WO2020024303 A1 WO 2020024303A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
protocol
ipdr
data
request
Prior art date
Application number
PCT/CN2018/098688
Other languages
English (en)
Chinese (zh)
Inventor
普云
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2018/098688 priority Critical patent/WO2020024303A1/fr
Publication of WO2020024303A1 publication Critical patent/WO2020024303A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method and device for data collection.
  • CMTS equipment can use CMTS equipment to collect data from user-side equipment (such as Cable Modem (CM)), such as the operating status of the CM, and the types of services of different user terminals connected to the CM.
  • user-side equipment such as Cable Modem (CM)
  • CM Cable Modem
  • FIG. 1 shows a traditional CMTS networking architecture.
  • the OLT is deployed in the central office room to manage multiple CMTS devices (only one CMTS is shown as an example in the figure).
  • the CMTS device is deployed in the residential room.
  • CMs are deployed in users 'homes.
  • Each CM can be connected to multiple customer premise equipment (CPE).
  • CPE customer premise equipment
  • CMs can be used to connect users' mobile phones, computers, and cable television.
  • the CMTS device collects the data of each CM, uploads the collected CM data to the OLT, and the OLT uploads the CM data to the operator server.
  • the industry has proposed a new networking architecture.
  • different functions of the CMTS can be separated and deployed in different locations.
  • the downstream CMTS and PHY layer processing can be separated from the CMTS and MAC layer processing and deployed at different locations, or the upstream and downstream CMTS and PHY layer processing can be separated from the CMTS and MAC layer processing and deployed at different locations.
  • the CMTS processing unit and the CMTS processing unit are connected by optical fibers. This connection method is generally called a remote physical layer (Remote Physical) (R-PHY) architecture.
  • R-PHY remote physical layer
  • the new network architecture has a larger change in network element composition, network element location, and network element functions than the traditional CMTS network architecture, the data collection technology in the traditional CMTS network architecture is no longer available. Applicable to the new networking architecture.
  • the embodiments of the present application provide a data collection method and device, which can execute a data collection process in a new networking architecture.
  • an embodiment of the present application provides a data collection method.
  • the method includes: a second network element receiving a first message encapsulated in a first interface protocol format sent by a third network element, and encapsulating according to a second interface protocol format.
  • First message get the second message.
  • the second network element determines at least one first network element associated with the third network element according to the second message, and sends a second message to the at least one first network element, respectively.
  • first network element is any one of at least one first network element
  • first interface protocol format A piece of data to obtain second data
  • determine a third network element associated with the first network element according to the second data and send the second data to the third network element.
  • the first interface protocol is the Internet Detailed Record (IPDR) protocol
  • the second interface protocol includes a characterization state transfer configuration (restconf) protocol, a network configuration (netconf) protocol, and a simple network management protocol (Simple Network Management Protocol). (SNMP), Remote Procedure Call (RPC) protocol; the second message is used to request data collected by at least one first network element.
  • IPDR Internet Detailed Record
  • restconf characterization state transfer configuration
  • network configuration network configuration
  • RPC Remote Procedure Call
  • the second network element after receiving the first message encapsulated in the first interface protocol format sent by the third network element, the second network element encapsulates the first message according to the second interface protocol format to obtain the second Message, and send a second message to the first network element to obtain first data sent by the first network element.
  • the second network element After obtaining the first data, the second network element encapsulates the first data according to the first interface protocol format to obtain the second data, so that the second data can be carried in the transmission channel between the second network element and the third network element, thereby The data collected by the first network element is successfully transmitted to the third network element via the second network element.
  • each segment of the transmission channel can transmit data or messages consistent with the format of the channel, which improves the probability of successfully transmitting data or messages in the channel, thereby improving the success rate of data collection .
  • the second network element before the second network element receives the first message sent by the third network element and encapsulated in the first interface protocol format, the following steps may be performed: the second network element receives the first message sent by the third network element. For the first version negotiation request, the second network element sends a first version negotiation response to the third network element.
  • the first version negotiation request is used to request to negotiate the first protocol version.
  • the first protocol version is an IPDR protocol version between the second network element and the third network element.
  • the first version negotiation response carries the first protocol version.
  • the above process uses the third network element to actively initiate a version negotiation request as an example to explain the process of negotiating the IPDR protocol version between the third network element and the second network element.
  • the second network may also be used by the second network.
  • the element actively initiates an IPDR protocol version negotiation request with the third network element.
  • the second network element sends a first version negotiation request to the third network element, and receives a first version negotiation response sent by the third network element.
  • the following steps may be performed:
  • the second network element sends a second version negotiation request to the first network element, and receives a second version negotiation response sent by the first network element.
  • the second version negotiation request is used to request to negotiate a second protocol version.
  • the second protocol version is an IPDR protocol version between the second network element and the first network element.
  • the second version negotiation response carries the second protocol version.
  • the second network element actively initiates an IPDR protocol version negotiation request with the first network element to negotiate the IPDR protocol version with the first network element.
  • the first network element may also actively initiate the IPDR protocol version negotiation request.
  • the second network element receives the second version negotiation request sent by the first network element, and sends a second version negotiation response to the first network element.
  • a first interface protocol is used when communicating between the second network element and the third network element, and the first interface protocol may be the IPDR protocol, and the second The network element and the first network element use a second interface protocol for communication, and the second interface protocol may be an IPDR protocol.
  • the second network element encapsulates the first message according to the second interface protocol format to obtain the second message, which can be specifically implemented as follows:
  • the second network element learns that the first protocol version is different from the second protocol version
  • the second network element changes the encapsulation format of the first message from the encapsulation format corresponding to the first protocol version to An encapsulation format corresponding to the second protocol version to obtain a second message.
  • the second network element encapsulates the first data according to the format of the first interface protocol to obtain the second data, which can be specifically implemented as:
  • the second network element changes the encapsulation format of the first data from the encapsulation format corresponding to the second protocol version to the encapsulation format corresponding to the first protocol version to obtain the second data.
  • the first interface protocol used in the communication between the second network element and the third network element is the IPDR protocol
  • the second interface used in the communication between the second network element and the first network element can be any of restconf, netconf, SNMP, and SNMP protocols.
  • the second network element encapsulates the first message according to the second interface protocol format to obtain the second message, which can be specifically implemented as follows:
  • the second network element encapsulates the first message's encapsulation format with the encapsulation format corresponding to the first protocol version.
  • the second message is obtained by modifying the encapsulation format corresponding to any protocol other than the IPDR protocol in the second interface protocol.
  • the second network element encapsulates the first data according to the first interface protocol format to obtain the second data, which can be specifically implemented as follows: the second network element divides the encapsulation format of the first data from the IPDR protocol by the second interface protocol The encapsulation format corresponding to any other protocol is modified to the encapsulation format corresponding to the first protocol version to obtain the second data.
  • control Protocol Transmission Control Protocol
  • the second network element receives a TCP connection request sent by the third network element, where the TCP connection request is used to request establishment of a TCP between the third network element and the second network element connection;
  • TCP Transmission Control Protocol
  • the second network element before the second network element receives the first message encapsulated in the first interface protocol format sent by the third network element, the second network element performs the following steps to establish a connection with the first network element.
  • TCP connection :
  • the second network element When the second network element works in the active mode, the second network element sends a TCP connection request to the first network element, and the TCP connection request is used to request establishment of a TCP connection between the second network element and the first network element.
  • the second network element before the second network element receives the first message encapsulated in the first interface protocol format sent by the third network element, the second network element performs the following steps to establish a connection with the first network element. TCP connection between the two network elements: when the second network element works in the passive mode, the second network element receives the TCP connection request sent by the first network element.
  • the second network element before the second network element receives the first message encapsulated in the first interface protocol format sent by the third network element, the second network element performs the following steps to establish a connection with the third network element.
  • IPDR connection
  • the second network element sends an IPDR connection request to the third network element, and receives the IPDR connection response sent by the third network element.
  • the IPDR connection request is used to request to establish an IPDR connection between the third network element and the second network element.
  • the second network element before the second network element receives the first message encapsulated in the first interface protocol format sent by the third network element, the second network element performs the following steps to establish a connection with the third network element.
  • IPDR connection between: In the case where the third network element works in the active mode, the second network element receives the IPDR connection request sent by the third network element and sends an IPDR connection response to the third network element.
  • the second network element before the second network element receives the first message encapsulated in the first interface protocol format sent by the third network element, the second network element performs the following steps to establish a connection with the first network element.
  • IPDR connection When the second network element works in the passive mode, the second network element receives the IPDR connection request sent by the first network element and sends an IPDR connection response to the third network element. The IPDR connection request is used to request to establish an IPDR connection between the first network element and the second network element.
  • the second network element before the second network element receives the first message encapsulated in the first interface protocol format sent by the third network element, the second network element performs the following steps to establish a connection with the first network element.
  • IPDR connection between the two network elements When the second network element works in the active mode, the second network element sends an IPDR connection request to the first network element, and receives the IPDR connection response sent by the first network element.
  • the second network element may further perform the following steps: the second network element receives the third The session query request sent by the network element, and sends a session query response to the third network element.
  • the session query request is used to request to query the session associated with the first network element; the session query response carries the session associated with the first network element.
  • the second network element may further perform the following steps:
  • the second network element sends a session query request to the first network element, and receives a session query response sent by the first network element.
  • the session query response carries a session associated with the first network element, and the session query request is used to request to query the first network element. Associated Session.
  • an embodiment of the present application provides a data acquisition device.
  • the device is provided with a transceiver and a processor.
  • the transceiver is configured to receive the first message encapsulated in the first interface protocol format sent by the third network element; and the processor is configured to encapsulate the first message received by the transceiver according to the second interface protocol format to obtain the second message.
  • the first interface protocol is the Internet detailed record IPDR protocol.
  • the second interface protocol includes a state transfer configuration restconf protocol, a network configuration netconf protocol, a simple network management protocol SNMP, and a remote procedure call RPC protocol.
  • the processor is also used to The message determines at least one first network element associated with the third network element; the transceiver is further configured to send a second message to the at least one first network element, respectively, and the second message is used to request the data collected by the at least one first network element Data; receiving the first data encapsulated in the second interface protocol format sent by the first network element; the processor is further configured to encapsulate the first data according to the first interface protocol format to obtain the second data, and the first network element is at least one Any one of the first network elements, the first network element; determining the third network element associated with the first network element according to the second data; the transceiver is further configured to send a signal to the third network element Transmitting the second data element.
  • the transceiver is further configured to receive a first version negotiation request sent by a third network element.
  • the first version negotiation request is used to request to negotiate a first protocol version, and the first protocol version is a second network element.
  • IPDR protocol version with the third network element; sending a first version negotiation response to the third network element, where the first version negotiation response carries the first protocol version.
  • the transceiver is further configured to send a first version negotiation request to a third network element; and receive a first version negotiation response sent by the third network element.
  • the transceiver is further configured to send a second version negotiation request to the first network element, the second version negotiation request is used to request to negotiate a second protocol version, and the second protocol version is the second network element and The version of the IPDR protocol between the first network elements; receiving the second version negotiation response sent by the first network element, and the second version negotiation response carrying the second protocol version.
  • the transceiver is further configured to receive a second version negotiation request sent by the first network element; and send a second version negotiation response to the first network element.
  • the processor is configured to encapsulate the first message according to the second interface protocol format to obtain the second message, including: if the first protocol version is different from For the second protocol version, the encapsulation format of the first message is modified from the encapsulation format corresponding to the first protocol version to the encapsulation format corresponding to the second protocol version to obtain the second message.
  • the processor is configured to encapsulate the first data according to the first interface protocol format to obtain the second data, including: if the first protocol version is different from the second protocol version, The encapsulation format is changed from the encapsulation format corresponding to the second protocol version to the encapsulation format corresponding to the first protocol version to obtain the second data.
  • the processor is configured to encapsulate the first message according to the second interface protocol format to obtain a second message, including: encapsulating the first message.
  • the format is changed from the encapsulation format corresponding to the first protocol version to the encapsulation format corresponding to any protocol other than the IPDR protocol in the second interface protocol to obtain a second message.
  • the processor is configured to encapsulate the first data according to the first interface protocol format to obtain the second data, including: dividing the encapsulation format of the first data from the IPDR protocol by the second interface protocol.
  • the encapsulation format corresponding to any external protocol is modified to the encapsulation format corresponding to the first protocol version to obtain the second data.
  • the transceiver is further configured to receive a Transmission Control Protocol TCP connection request sent by the third network element when the third network element works in an active mode, and the TCP connection request is used to request establishment of a third TCP connection between the network element and the second network element.
  • the transceiver is further configured to send a TCP connection request to the third network element when the third network element works in the passive mode.
  • the transceiver is further configured to send a TCP connection request to the first network element when the second network element works in an active mode, and the TCP connection request is used to request establishment of the second network element and the first network element. TCP connection between network elements.
  • the transceiver is further configured to receive a TCP connection request sent by the first network element when the second network element works in a passive mode.
  • the second network element actively initiates an IPDR connection request with the third network element
  • the transceiver is further configured to send the third network element to the third network element when the third network element works in the passive mode.
  • the second network element passively receives an IPDR connection request initiated by the third network element, and the transceiver is further configured to receive the third network element when the third network element works in an active mode.
  • the second network element passively receives the IPDR connection request initiated by the first network element, and the transceiver is further configured to receive the first network element to send the IPDR when the second network element works in the passive mode.
  • a connection request sending an IPDR connection response to the third network element; the IPDR connection request is used to request the establishment of an IPDR connection between the first network element and the second network element;
  • the second network element actively initiates an IPDR connection request with the first network element
  • the transceiver is further configured to send the first network element to the first network element when the second network element works in an active mode.
  • the network element sends an IPDR connection request; receives the IPDR connection response sent by the first network element.
  • the transceiver is further configured to receive a session query request sent by a third network element, and send a session query response to the third network element; the session query request is used to request a query about a session associated with the first network element; The session query response carries the session associated with the first network element.
  • the transceiver is further configured to send a session query request to the first network element and receive a session query response sent by the first network element; the session query request is used to request a query about a session associated with the first network element; The session query response carries the session associated with the first network element.
  • an embodiment of the present application provides a data acquisition device, which has a function of implementing the data acquisition method of any one of the first aspects.
  • This function can be realized by hardware, and can also be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • a data acquisition device including: a processor and a memory; the memory is configured to store computer execution instructions, and when the data acquisition device is running, the processor executes the computer execution instructions stored in the memory so that The data acquisition device executes the data acquisition method according to any one of the first aspects.
  • a data acquisition device including: a processor; the processor is coupled to the memory and reads instructions in the memory, and then executes the data acquisition method according to any one of the first aspects according to the instructions.
  • a computer-readable storage medium stores instructions that, when run on a computer, enable the computer to execute the data collection method of any one of the first aspects.
  • a computer program product containing instructions which, when run on a computer, enables the computer to execute the data collection method of any one of the above-mentioned first aspects.
  • a circuit system includes a processing circuit configured to execute the data acquisition method according to any one of the first aspects.
  • a chip includes a processor, and the processor is coupled to a memory.
  • the memory stores program instructions.
  • the program instructions stored in the memory are executed by the processor to implement the first chip.
  • the data collection method according to any one of the aspects.
  • the technical effects brought by any one of the design methods in the second aspect to the ninth aspect can refer to the technical effects brought by the different design methods in the first aspect, and are not repeated here.
  • FIG. 1 is a schematic diagram of the architecture of a traditional data acquisition system
  • FIG. 2 is a schematic structural diagram of a data acquisition system according to an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a data acquisition system according to an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a data acquisition device according to an embodiment of the present application.
  • FIG. 5 is a flowchart of a data collection preprocessing method according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a version negotiation message according to an embodiment of the present application.
  • FIG. 7 is a flowchart of another data collection and preprocessing method according to an embodiment of the present application.
  • FIG. 8 is a first method flowchart of a data collection method according to an embodiment of the present application.
  • FIG. 9 is a second method flowchart of a data collection method according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a data acquisition device according to an embodiment of the present application.
  • first and “second” in the specification of the present application and the drawings are used to distinguish different objects, or to distinguish different processes on the same object, rather than to describe a specific order of the objects.
  • the terms “including” and “having” as well as any variants thereof mentioned in the description of the present application are intended to cover non-exclusive inclusion.
  • a process, method, system, product, or device that contains a series of steps or units is not limited to the listed steps or units, but optionally also includes other steps or units not listed, or optionally also Include other steps or units inherent to these processes, methods, products, or equipment.
  • words such as “exemplary” or “for example” are used as examples, illustrations or illustrations.
  • the system includes an Internet detailed record server (Internet Protocol Record Server, IPDR Server), a media access control management network element (MAC Manager, also referred to herein as a MAC controller), and a remote media access control.
  • IPDR Server Internet Protocol Record Server
  • MAC Manager media access control management network element
  • CM Physical layer
  • R-MACPHY Remote Media Access Control and Physical
  • the IPDR server is located at the aggregation layer and is used to manage at least one MAC Manager (only one is shown as an example in the figure).
  • MAC Manager is used to manage at least one remote entity.
  • the form of the remote entity may be different under different networking architectures.
  • the MAC layer and PHY layer functions of the CMTS are separated and deployed in different locations.
  • the PHY layer function of the CMTS is sunk to the user side to form the R-PHY entity (to simplify the description, the R-PHY entity is referred to as R-PHY hereinafter), and the R-PHY entity is responsible for the PHY layer processing.
  • the function of the MAC layer is retained at the central office side, forming an R-MAC entity (for simplicity of description, the R-MAC entity is hereinafter referred to simply as R-MAC), and the R-MAC entity is responsible for MAC layer processing.
  • R-MAC the R-MAC entity
  • the MAC Manager directly manages at least one R-MAC (only one is exemplarily shown in FIG. 2), and the R-MAC manages at least one R-PHY.
  • the functions of the MAC layer and the PHY layer of the CMTS are sunk to the user side to form the R-MACPHY entity (to simplify the description, the R-MACPHY entity is referred to as R-MACPHY hereinafter), and the R-MACPHY MACPHY is responsible for MAC layer and PHY layer processing. Therefore, in this architecture, at least one R-MACPHY is directly managed by the MAC Manager (only one is exemplarily shown in FIG. 2).
  • the R-PHY or R-MACPHY is located in the access layer and is used to manage at least one CM (the case where each R-MACPHY or R-PHY manages one CM is exemplarily shown in FIG. 2).
  • the CM is located in the user's home and is used to manage at least one CPE.
  • the CPE located in the user's home, is used to connect user terminals and provide users with integrated access to services such as home cable broadband, Internet Protocol Television (IPTV), and Voice over Internet Protocol (VOIP).
  • the CPE involved in the embodiments of the present application may include various devices having an access function, such as a digital video conversion box (Set Top Box, STB), a home gateway, and the like.
  • the user terminal may be, for example, a cable TV, or a wearable device, a computing device, a personal digital assistant (PDA) computer, a tablet computer, a laptop computer, and a machine type communication, MTC) terminal, user equipment (UE), and so on.
  • PDA personal digital assistant
  • MTC machine type communication
  • UE user equipment
  • the following mainly uses the R-PHY architecture as an example to describe the data transmission method of the system of FIG. 2.
  • the downlink data is sent by the IPDR server to the MAC manager, and then sent by the MAC manager to the R-PHY through the R-MAC.
  • the R-PHY demodulates and decodes to obtain the original downlink data.
  • Re-encoding and modulation convert the original downlink data into a coaxial cable signal and send it to each connected CM, and the CM sends the coaxial cable signal to the CPE (such as a set-top box and / or a personal computer).
  • the CPE sends the uplink data to the CM, and the CM transmits the data to the R-PHY through a coaxial cable.
  • the R-PHY demodulates and decodes the data, and then encodes and modulates the data.
  • the shaft cable signal is converted into an optical fiber signal, which is then sent to the R-MAC by the R-PHY through the optical fiber.
  • the R-MAC uploads the downlink data to the IPDR server through the MAC Manager.
  • the names of the network elements in FIG. 2 are only examples, and the names of the network elements in the specific implementation may be other names, or the network elements may also be called entities, which is not specifically limited in the embodiment of the present application. All or part of the foregoing network elements may be physical physical network elements or virtualized network elements, which is not limited herein.
  • the network architecture and service scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. With the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • an embodiment of the present application provides a data acquisition system, which includes a third network element 303, a second network element 302, and a first network element 301.
  • the first network element 301 is configured to collect data from the CM, and the collected data includes CM operating status, CM-related charging information, spectrum information of uplink and downlink channels of the link where the CM is located, and debugging information of the CM.
  • the second network element 302 has an Internet Protocol (IP) layer function, and is configured to upload data collected by the first network element 301 to the third network element 303.
  • IP Internet Protocol
  • the second network element 302 and the first network element 301 have a second protocol interface
  • the second network element 302 and the third network element 303 have a first protocol interface.
  • the second network element 302 and the first network element 301 use the second interface protocol to encapsulate communication data when communicating
  • the second network element 302 and the third network element 303 use the first interface protocol to encapsulate communication data when communicating.
  • the third network element 303 is configured to receive the collected data sent by the second network element 302 and upload the collected data to an upper network.
  • the data collection system provided in the embodiment of the present application may be applied to the system shown in FIG. 2 or a system with a similar architecture or a subsequent evolved system.
  • the first network element 301 described above The corresponding network element or entity may be the R-MAC and / or R-MACPHY in FIG. 2
  • the network element or entity corresponding to the above-mentioned second network element 302 may be the MAC manager in FIG. 2
  • the network element or entity corresponding to the network element 303 may be the IPDR server in FIG. 2.
  • the first network element 301, the second network element 302, and the third network element 303 in FIG. 3 may be implemented by multiple devices, and may also be implemented by one device, for example, different functions in one device may be implemented.
  • Module which is not specifically limited in the embodiment of the present application. It can be understood that the foregoing function module may be a network element in a hardware device, a software function running on a hardware device, or a virtualization function instantiated on a platform (for example, a cloud platform).
  • FIG. 4 is a schematic diagram of a hardware structure of a communication device according to an embodiment of the present application.
  • the communication device 400 includes at least one processor 401, a communication line 402, a memory 403, and at least one communication interface 404.
  • the processor 401 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more processors for controlling the execution of the program of the solution of the present application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication line 402 may include a path for transmitting information between the aforementioned components.
  • the communication interface 404 uses any device such as a transceiver to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • RAN radio access network
  • WLAN wireless local area networks
  • the memory 403 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types that can store information and instructions
  • the dynamic storage device can also be electrically erasable programmable read-only memory (EEPROM-ready-only memory (EEPROM)), compact disc (read-only memory (CD-ROM)) or other optical disk storage, optical disk storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.
  • the memory may exist independently, and is connected to the processor through the communication line 402. The memory can also be integrated with the processor.
  • the memory 403 is configured to store computer execution instructions for executing the solutions in the embodiments of the present application, and the execution is controlled by the processor 401.
  • the processor 401 is configured to execute computer execution instructions stored in the memory 403, so as to implement the data collection method provided in the following embodiments of the present application.
  • the memory 403 is used to store two tables shown in FIG. 4, namely, the association relationship between the IPDR server and the R-MACPHY, and the IPDR protocol versions supported by the IPDR server and the R-MACPHY, respectively.
  • the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.
  • the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 4.
  • the communication device 400 may include multiple processors, such as the processor 401 and the processor 405. Each of these processors may be a single-CPU processor or a multi-CPU processor.
  • a processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).
  • FIG. 4 only shows an exemplary hardware structure diagram of a communication device.
  • the communication device 400 may further include other components. Limitation.
  • the above-mentioned communication device 400 may be a general-purpose device or a special-purpose device.
  • the communication device 400 may be a device having a similar structure as in FIG. 4.
  • the embodiment of the present application does not limit the type of the communication device 400.
  • the second network element and the third network element adopt a first interface protocol for communication, and the first interface protocol may be an IPDR protocol.
  • the second network element communicates with the first network element using a second interface protocol, and the second interface protocol may be an IPDR protocol or a non-IPDR protocol.
  • non-IPDR protocols include restconf protocol, netconf protocol, SNMP protocol, and RPC protocol.
  • the RPC protocol includes but is not limited to Google Remote Procedure Call (GRPC) GRPC protocol, Apache Thrift and so on.
  • the pre-processing flow of the embodiment of the present application is given.
  • the IPDR server sends a first version negotiation request (Version Request) to the MAC Manager.
  • the MAC Manager receives the first version negotiation request sent by the IPDR Server.
  • the first version negotiation request is used to request to negotiate a first protocol version, and the first protocol version is an IPDR protocol version between the MAC Manager and the IPDR Server.
  • the fields included in the first version negotiation request message sent by the IPDR Server include a request ID (IDentity, ID) field, which occupies 4 bytes, a request time field, and an IPDR version field of the IPDR Server.
  • request ID IDentity, ID
  • the MAC Manager sends a first version negotiation response to the IPDR Server.
  • the IPDR Server receives the first version negotiation response sent by the MAC Manager.
  • the first version negotiation response carries the first protocol version.
  • the first version negotiation response message sent by the MAC Manager includes the following fields: the transmission type field of the MAC Manager, the IPDR protocol version field of the MAC Manager, and the port number used by the MAC Manager Fields, reserved words, and fields to indicate additional information.
  • the transmission type is used to indicate the transport layer protocol defined by the TCP / IP protocol.
  • the above S501 and S502 are the IPDR protocol version negotiation process between the MAC Manager and the IPDR server, and may also be referred to herein as the first protocol version negotiation process.
  • the MAC Manager can also actively initiate the protocol negotiation process, that is, the MAC Manager sends a first version negotiation request to the IPDR Server and receives the first version negotiation response sent by the IPDR Server.
  • the embodiment of the present application does not limit specific devices that actively initiate a protocol negotiation process.
  • the MAC Manager sends a second version negotiation request to the R-MACPHY.
  • the R-MACPHY receives the second version negotiation request sent by the MAC Manager.
  • the second version negotiation request is used to request to negotiate a second protocol version, and the second protocol version is an IPDR protocol version between the MAC Manager and the R-MACPHY.
  • the R-MACPHY sends a second version negotiation response to the MAC Manager.
  • the MAC Manager receives the second version negotiation response sent by the R-MACPHY.
  • the second version negotiation response carries a second protocol version.
  • S503 and S504 are processes for negotiating the IPDR protocol version between the R-MACPHY and the MAC Manager, and may also be referred to herein as a second protocol version negotiation process.
  • the R-MACPHY can initiate the protocol version negotiation process with the MAC Manager.
  • the first protocol version negotiation process and the second protocol version negotiation process are performed independently. This means that when the MAC Manager actively initiates the negotiation process in the first protocol version negotiation process, the MAC Manager in the second protocol version negotiation process can actively initiate the negotiation process or passively receive the R-MACPHY version negotiation response.
  • the IPDR Server In the case where the IPDR Server works in the active mode, the IPDR Server sends a TCP connection request to the MAC Manager.
  • the MAC Manager receives the TCP connection request sent by the IPDR Server.
  • the TCP connection request is used to request to establish a TCP connection between the IPDR Server and the MAC Manager.
  • a TCP connection between the peers is usually established through a three-way handshake.
  • the schematic process of the three-way handshake is shown in FIG. 5.
  • the TCP connection between the MAC Manager and the IPDR Server was successfully established.
  • the MAC Manager actively initiates a TCP connection request to the IPDR Server to establish a TCP connection with the IPDR Server.
  • the MAC Manager When the MAC Manager works in the active mode, the MAC Manager sends a TCP connection request to the R-MACPHY.
  • the R-MACPHY receives the TCP connection request sent by the MAC Manager.
  • the TCP connection request is used to request establishment of a TCP connection between the MAC Manager and the R-MACPHY.
  • S506 can also be implemented as: R-MACPHY sends a TCP connection request to the MAC Manager to establish a TCP connection with the MAC Manager.
  • the IPDR Server sends an IPDR connection request to the MAC Manager.
  • the MAC Manager receives the IPDR connection request sent by the IPDR Server.
  • the IPDR connection request is used to request to establish an IPDR connection between the IPDR server and the MAC manager.
  • the MAC Manager sends an IPDR connection response to the IPDR Server.
  • S507 and S508 are procedures for establishing an IPDR connection between the MAC Manager and the IPDR Server.
  • the MACDR Manager can actively initiate an IPDR connection request.
  • S507 and S508 may be implemented as follows: The MAC Manager sends an IPDR connection request to the IPDR Server, and receives the IPDR connection response sent by the IPDR Server.
  • the R-MACPHY receives the IPDR connection request sent by the MAC Manager.
  • the IPDR connection request is used to request the establishment of an IPDR connection between the MAC Manager and the R-MACPHY.
  • the R-MACPHY sends an IPDR connection response to the MAC Manager.
  • the MAC Manager receives the IPDR connection response sent by the R-MACPHY.
  • S509 and S510 can be implemented as follows: R-MACPHY sends an IPDR connection request to the MAC Manager and receives an IPDR connection response sent by the MAC Manager.
  • the IPDR server sends a session query request to the MAC Manager.
  • the MAC Manager receives the session query request sent by the IPDR Server.
  • the session query request is used to request to query a session associated with the R-MACPHY.
  • the MAC Manager sends a session query response to the IPDR Server.
  • the IPDR Server receives the session query response sent by the MAC Manager.
  • the session query response carries a session associated with the R-MACPHY.
  • S512 may be directly executed to feed back the session query response to the IPDR Server.
  • the MAC Manager sends a session query request to the R-MACPHY (S513) and receives the session query sent by the R-MACPHY A response (S514), and sends the session query response to the IPDR server (S515).
  • the other pre-processing process includes the following steps:
  • the IPDR server sends a first version negotiation request (Version Request) to the MAC manager.
  • the MAC Manager receives the first version negotiation request sent by the IPDR Server.
  • the MAC manager sends a first version negotiation response (Version Response) to the IPDR server.
  • the IPDR Server receives the first version negotiation response sent by the MAC Manager.
  • the IPDR Server works in the active mode, the IPDR Server sends a TCP connection request to the MAC Manager.
  • the MAC Manager receives the TCP connection request sent by the IPDR Server.
  • the IPDR server sends an IPDR connection request to the MAC Manager.
  • the MAC Manager receives the IPDR connection request sent by the IPDR Server.
  • the MAC Manager sends an IPDR connection response to the IPDR Server.
  • the IPDR server receives the IPDR connection response sent by the MAC Manager.
  • the IPDR server sends a session query request to the MAC manager.
  • the MAC Manager receives the session query request sent by the IPDR Server.
  • the MAC Manager sends a session query response to the IPDR Server.
  • the IPDR Server receives the session query response sent by the MAC Manager.
  • the embodiment of the present application provides a data collection method.
  • the second interface protocol is the IPDR protocol, based on the preprocessing process shown in FIG. 5, and as shown in FIG. 8, the data collection method provided in the embodiment of the present application, It includes the following steps:
  • the IPDR server sends a first message encapsulated in a first interface protocol format to the MAC manager.
  • the MAC Manager receives the first message sent by the IPDR Server.
  • the first interface protocol is the IPDR protocol.
  • the first message may be an IPDR session control message, and the first message carries an IPDR server identifier and is used to address an R-MACPHY associated with the IPDR server.
  • the IPDR server identification includes but is not limited to the IP address of the IPDR server and the MAC address of the IPDR server identification.
  • the MAC manager encapsulates the first message according to the second interface protocol format to obtain the second message.
  • the MAC Manager learns that the first protocol version is different from the second protocol version after the protocol version negotiation.
  • S802 can be implemented as follows: The MAC Manager encapsulates the first message from the first The encapsulation format corresponding to the protocol version is changed to the encapsulation format corresponding to the second protocol version to obtain a second message.
  • the first message carries the IPDR server identifier, and accordingly, the re-encapsulated second message also carries the IPDR server identifier.
  • the MAC Manager finds that the IPDR protocol version between the MAC Manager and the IPDR Server is IPDR 2.0, and the IPDR protocol version between the MAC Manager and the R-MACPHY is IPDR 1.0. Subsequently, the MAC Manager receives the first message of the IPDR 2.0 version, parses the first message, and repackages the first message according to the format of the IPDR 1.0 to obtain the second message.
  • the MAC manager determines at least one R-MACPHY associated with the IPDR server according to the second message.
  • the MAC Manager stores the association relationship between the IPDR server and the R-MACPHY.
  • the memory 403 of the MAC Manager stores an association table of the IPDR server ID and the R-MACPHY ID.
  • the MAC Manager may query the stored association table according to the IPDR server identifier carried in the second message to determine one or more R-MACPHYs to which the IPDR server is associated.
  • the MAC manager sends a second message to at least one R-MACPHY, respectively.
  • the R-MACPHY receives the second message from the MAC Manager.
  • the second message is used to request data collected by at least one R-MACPHY.
  • the R-MACPHY sends the first data encapsulated in the second interface protocol format to the MAC Manager.
  • the MAC Manager receives the first data sent by the R-MACPHY.
  • the first data includes, but is not limited to, the CM operating state, CM-related charging information, spectrum information of uplink and downlink channels of the link where the CM is located, and debugging information of the CM.
  • the first data carries an R-MACPHY identifier and is used to address an IPDR server associated with the R-MACPHY.
  • the MAC Manager encapsulates the first data according to the first interface protocol format to obtain the second data.
  • the first protocol version between the MAC Manager and the IPDR server is different from the second protocol version between the MAC Manager and the R-MACPHY.
  • S806 can be implemented as follows: The MAC Manager converts the first data encapsulation format from the second protocol version. The corresponding encapsulation format is modified to the encapsulation format corresponding to the first protocol version to obtain second data, where the second data carries the R-MACPHY identifier.
  • the MAC manager determines the IPDR server associated with the R-MACPHY according to the second data.
  • the MAC Manager queries the association table shown in FIG. 4 according to the R-MACPHY identifier carried in the second data to determine the IPDR Server associated with the R-MACPHY.
  • the MAC Manager sends the second data to the IPDR Server.
  • the second network element after receiving the first message encapsulated in the first interface protocol format sent by the third network element, the second network element repackages the first message according to the second interface protocol format to obtain the first message. Two messages and sending the second message to the first network element to trigger the first network element to send the collected first data to the second network element. After obtaining the first data, the second network element repackages the first data according to the first interface protocol format to obtain the second data, so that the second data can be carried in the transmission channel between the second network element and the third network element, Thus, the data collected by the first network element is successfully transmitted to the third network element via the second network element.
  • each segment of the transmission channel can transmit data or messages consistent with the format of the channel, which improves the probability of successfully transmitting data or messages in the channel, thereby improving the success rate of data collection.
  • An embodiment of the present application further provides a data collection method.
  • the data collection method includes the following steps: :
  • the IPDR server sends a first message encapsulated in a first interface protocol format to the MAC Manager.
  • the MAC Manager receives the first message sent by the IPDR Server.
  • the MAC Manager encapsulates the first message according to the second interface protocol format to obtain a second message.
  • S902 can be implemented as follows: The MAC Manager changes the encapsulation format of the first message from the encapsulation format corresponding to the first protocol version to the corresponding one of the second interface protocols except the IPDR protocol (that is, non-IPDR protocol). Encapsulated format to get the second message.
  • IPDR protocol that is, non-IPDR protocol
  • the second interface protocol is the GRPC protocol.
  • the IPDR protocol version between the MAC Manager and the IPDR Server is IPDR 2.0.
  • the MAC Manager receives the first message of the IPDR 2.0 version, parses the first message, and repackages the first message according to the GRPC format to obtain the second message.
  • the MAC manager determines at least one R-MACPHY associated with the IPDR server according to the second message.
  • the MAC Manager establishes a connection with the R-MACPHY.
  • the MAC Manager establishes a GRPC connection with the R-MACPHY.
  • the MAC Manager can establish a GRPC connection with the R-MACPHY in any of the following two ways:
  • Method 1 The MAC Manager actively sends a GRPC connection request to the R-MACPHY to establish a GRPC connection.
  • R-MACPHY can collect data periodically and upload the collected data to a designated device. If the specified device is not configured, R-MACPHY uploads the collected data to MAC Manager by default. And, in the method 1, if the GRPC connection between the MAC Manager and the R-MACPHY is disconnected, the R-MACPHY no longer pushes the collected data upwards.
  • Method 2 The MAC Manager receives a GRPC connection request initiated by the R-MACPHY to establish a GRPC connection with the R-MACPHY.
  • R-MACPHY will retry to establish a GRPC connection and upload the collected data to the MAC Manager.
  • the MAC Manager can also trigger the action of establishing a connection with the R-MACPHY after receiving the first message (ie, S901) from the IPDR Server, or it can be executed after S902 or simultaneously with S902.
  • S901 the first message
  • S902 the first message
  • S904 the execution timing of S904 is restricted.
  • the R-MACPHY receives the second message from the IPDR server.
  • the R-MACPHY sends the first data encapsulated in the second interface protocol format to the MAC Manager.
  • the MAC Manager receives the first data sent by the R-MACPHY.
  • the MAC Manager encapsulates the first data according to the first interface protocol format to obtain the second data.
  • S907 can be implemented as follows:
  • the MAC Manager changes the encapsulation format of the first data from the encapsulation format corresponding to any protocol in the second interface protocol except the IPDR protocol to the encapsulation format corresponding to the first protocol version to obtain the second data.
  • the second interface protocol is the GRPC protocol and the first protocol version is IPDR 2.0
  • the MAC Manager decapsulates the first data after receiving the first data in the GRPC format, and decapsulates the first data. Re-encapsulate according to the IPDR 2.0 format to obtain the second data.
  • the MAC manager determines the IPDR server associated with the R-MACPHY according to the second data.
  • the MAC Manager sends the second data to the IPDR Server.
  • data or messages encapsulated in the IPDR protocol format are transmitted between the second network element and the third network element, and data or messages encapsulated in the non-IPDR protocol format are transmitted between the second network element and the third network element, so that The data or message format is adapted to the transmission channel carrying the data or message, and the success rate of data collection is improved.
  • the first interface protocol in the embodiment of the present application is not limited to the IPDR protocol, and may also be an evolved protocol of the IPDR protocol, or another protocol having the same function as the IPDR protocol.
  • the second interface protocol is not limited to the above-listed protocols, but may also be an evolved version of the listed protocols, or other protocols having the same functions as the listed protocols.
  • the network element in the embodiment of the present application includes a hardware structure and / or a software module corresponding to each function.
  • the embodiments of this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application of the technical solution and design constraints. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the technical solutions of the embodiments of the present application.
  • each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit.
  • the above integrated unit may be implemented in the form of hardware or in the form of software functional unit. It should be noted that the division of the units in the embodiments of the present application is schematic, and is only a logical function division. There may be another division manner in actual implementation.
  • FIG. 10 shows a schematic block diagram of a data acquisition device provided in an embodiment of the present application, and the data acquisition device may be the foregoing second network element.
  • the data acquisition device 1000 may exist in the form of software, or may be a chip that can be used in a device.
  • the data acquisition device 1000 includes a processing unit 1002 and a communication unit 1003.
  • the processing unit 1002 may be used to support the second network element to perform S802, S803, S806, S807 in FIG. 8, S902, S903, S907, S908, etc. in FIG. 9, and / or other processes for the scheme described herein .
  • the communication unit 1003 is configured to support communication between the second network element and other network elements (for example, the first network element and the third network element described above).
  • the second network element supports S501 to S512 in FIG. 5 and FIG. 7. S701 to S707, S801, S804, S805, and S808 in FIG. 8, S901, S904, S905, S906, and S909 in FIG. 9.
  • the data acquisition device 1000 may further include a storage unit 1001 for storing program codes and data of the data acquisition device 1000.
  • the data may include, but is not limited to, original data or intermediate data.
  • the processing unit 1002 may be a controller or the processor 401 or the processor 405 shown in FIG. 4, for example, it may be a central processing unit (CPU), a general-purpose processor, and digital signal processing ( Digital Signal Processing (DSP), Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any of them combination. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the present disclosure.
  • the processor may also be a combination that implements computing functions, such as a combination including one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication unit 1003 may be a transceiver, a transceiver circuit, or the communication interface 404 shown in FIG. 4 and the like.
  • the storage unit 1001 may be a memory 403 shown in FIG. 4.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be from a website site, computer, server, or data center Transmission to another website site, computer, server or data center via wired (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, and the like including one or more available medium integration.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a Digital Video Disc (DVD)), or a semiconductor medium (for example, a solid state disk (Solid State Disk, SSD)) )Wait.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a Digital Video Disc (DVD)
  • DVD Digital Video Disc
  • semiconductor medium for example, a solid state disk (Solid State Disk, SSD)
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be electrical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, which may be located in one place, or may be distributed to multiple network devices (for example, Terminal device). Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each functional unit may exist independently, or two or more units may be integrated into one unit.
  • the above integrated unit may be implemented in the form of hardware, or in the form of hardware plus software functional units.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Communication Control (AREA)

Abstract

Procédé et appareil de collecte de données, se rapportant au domaine technique des communications et utilisés pour exécuter une procédure de collecte de données dans une nouvelle architecture de réseautage. Le procédé comprend : un second élément de réseau recevant un premier message envoyé par un troisième élément de réseau et encapsulé dans le format d'un premier protocole d'interface (S801), et encapsulant le premier message dans le format d'un deuxième protocole d'interface pour obtenir un deuxième message (S802), le premier protocole d'interface étant un protocole IPDR, et le deuxième protocole d'interface comprenant un protocole restconf, un protocole netconf, un protocole SNMP et un protocole RPC ; le deuxième élément de réseau déterminant, selon le deuxième message, au moins un premier élément de réseau associé au troisième élément de réseau, et envoyant respectivement le deuxième message au ou aux premiers éléments de réseau (S804) ; le deuxième élément de réseau recevant des premières données envoyées par le premier élément de réseau et encapsulées dans le format du deuxième protocole d'interface (S805), et encapsulant les premières données dans le format du premier protocole d'interface pour obtenir des deuxième données (S806) ; et le deuxième élément de réseau déterminant, en fonction des deuxièmes données, le troisième élément de réseau associé au premier élément de réseau (S807), et envoyant les deuxièmes données au troisième élément de réseau (S808).
PCT/CN2018/098688 2018-08-03 2018-08-03 Procédé et appareil de collecte de données WO2020024303A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/098688 WO2020024303A1 (fr) 2018-08-03 2018-08-03 Procédé et appareil de collecte de données

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/098688 WO2020024303A1 (fr) 2018-08-03 2018-08-03 Procédé et appareil de collecte de données

Publications (1)

Publication Number Publication Date
WO2020024303A1 true WO2020024303A1 (fr) 2020-02-06

Family

ID=69231347

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/098688 WO2020024303A1 (fr) 2018-08-03 2018-08-03 Procédé et appareil de collecte de données

Country Status (1)

Country Link
WO (1) WO2020024303A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1449157A (zh) * 2002-03-30 2003-10-15 深圳市中兴通讯股份有限公司 一种网络管理系统和方法
CN103297273A (zh) * 2013-06-04 2013-09-11 华为技术有限公司 一种管理设备的方法、装置及系统
CN106357590A (zh) * 2015-07-15 2017-01-25 艾默生网络能源系统北美公司 一种网络协议转换系统、网络协议转换器及其转换方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1449157A (zh) * 2002-03-30 2003-10-15 深圳市中兴通讯股份有限公司 一种网络管理系统和方法
CN103297273A (zh) * 2013-06-04 2013-09-11 华为技术有限公司 一种管理设备的方法、装置及系统
CN106357590A (zh) * 2015-07-15 2017-01-25 艾默生网络能源系统北美公司 一种网络协议转换系统、网络协议转换器及其转换方法

Similar Documents

Publication Publication Date Title
US20210084443A1 (en) Methods of joint registration and de-registration for proximity services and internet of things services
KR101740449B1 (ko) M2m(machine-to-machine)시스템에서 게이트웨이 변경 방법 및 이를 위한 장치
EP3025483B1 (fr) Sessions point-à-point de couche de services
EP3005822B1 (fr) Transport à couche mac pour plateforme de services d'application de services directs à wi-fi sans protocole internet
US20210274418A1 (en) Information Transmission Method and Apparatus
CN111434083B (zh) 用于netconf的网络管理设备和集中式授权服务器
WO2017147772A1 (fr) Procédé de transmission d'informations et appareil d'accès à un réseau central
WO2019157968A1 (fr) Procédé, appareil, et système de communication
WO2016180020A1 (fr) Procédé, dispositif et système de traitement de message
WO2019242525A1 (fr) Procédé de transmission de données, dispositif et système associés
US20220239761A1 (en) Data Subscription Method, Apparatus, and System
CN104320347B (zh) 一种主动更新lldp的方法及设备
US20200344725A1 (en) Data transmission method and apparatus, and computer storage medium
WO2023035925A1 (fr) Procédé, appareil et système de traitement de service
WO2018196463A1 (fr) Procédé et appareil d'accès au réseau, support d'informations et processeur
WO2022151420A1 (fr) Procédé, appareil et système permettant de transmettre un paquet de données
CN111385131A (zh) 网络设备的配置方法、装置、设备及系统
EP4233272A1 (fr) Appel interactif pour l'internet des objets
EP3220584A1 (fr) Procédé et système de partage de wifi, passerelle domestique et passerelle de réseau local sans fil
WO2022237857A1 (fr) Procédé de détermination de mode d'activation de protection de sécurité, procédé de communication et appareil de communication
WO2020024303A1 (fr) Procédé et appareil de collecte de données
US20240292198A1 (en) Proximity service for ai/ml capable devices
CN110620999B (zh) 用户面数据处理方法及装置
WO2019140648A1 (fr) Procédé et dispositif de notification d'informations par un terminal et support d'informations d'ordinateur
EP3912329B1 (fr) Gestion automatisée de flux de messages de couche de service dans un réseau de communication

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: 18928183

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18928183

Country of ref document: EP

Kind code of ref document: A1