WO2019001562A1 - 模型加载方法、装置、存储介质和计算机设备 - Google Patents

模型加载方法、装置、存储介质和计算机设备 Download PDF

Info

Publication number
WO2019001562A1
WO2019001562A1 PCT/CN2018/093586 CN2018093586W WO2019001562A1 WO 2019001562 A1 WO2019001562 A1 WO 2019001562A1 CN 2018093586 W CN2018093586 W CN 2018093586W WO 2019001562 A1 WO2019001562 A1 WO 2019001562A1
Authority
WO
WIPO (PCT)
Prior art keywords
model
network element
reported
version number
loading
Prior art date
Application number
PCT/CN2018/093586
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 WO2019001562A1 publication Critical patent/WO2019001562A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0859—Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/133—Protocols for remote procedure calls [RPC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a method, an apparatus, a storage medium, and a computer device for loading a model.
  • the Internet Engineering Task Force proposes a Network Configuration (NETCONF) protocol that provides a mechanism for managing network devices.
  • the NETCONF protocol uses the xml format as a data carrier and performs data interaction by means of a remote call interface.
  • the NETCONF protocol is modeled using YANG.
  • the YANG model is a data modeling language used to model configuration data and state data for NETCONF protocols, NETCONF Remote Procedure Call (RPC), and NETCONF notification operations.
  • the network element when the network element is connected to the network management system, the network element reports the service model described by YANG to the network management system.
  • the NMS accesses a large number of NEs, it generates a large number of message exchanges and consumes more bandwidth, which seriously affects the access of NEs.
  • the present disclosure is directed to a method, apparatus, storage medium, and computer device for loading a model, which optimizes loading of a model by loading the model of the same version of the network element only once.
  • An embodiment of the present disclosure provides a method for loading a model, including: establishing a session with a network element; querying and acquiring a model version number reported by the network element; and determining, according to a model query algorithm, a version corresponding to the reported model version number. Whether the model has been loaded; if not, acquiring a model file corresponding to the reported model version number, and loading the model file to the local; if loaded, directly using the model version number corresponding to the reported model The loaded model file accesses the network element for operation.
  • the embodiment of the present disclosure further provides an apparatus for loading a model, including: a session establishing module, configured to establish a session with a network element; and a query module configured to query and acquire a model version number reported by the network element; Is configured to determine, according to the model query algorithm, whether the model corresponding to the reported model version number has been loaded; loading the module, when the determining module determines that the model corresponding to the reported model version number is not loaded, the loading module Obtaining a model file corresponding to the reported model version number, and loading the model file to the local; and an operation module, when the determining module determines that the model corresponding to the reported model version number is loaded, The operation module directly accesses the network element by using the loaded model file corresponding to the reported model version number.
  • a session establishing module configured to establish a session with a network element
  • a query module configured to query and acquire a model version number reported by the network element
  • Is configured to determine, according to the model query algorithm, whether the model corresponding to the reported
  • Embodiments of the present disclosure also provide a computer readable storage medium having stored thereon computer executable instructions that, when executed by a processor, cause the processor to perform a loading model according to the present disclosure method.
  • Embodiments of the present disclosure also provide a computer device including a memory and a processor having stored therein computer readable instructions that, when executed by the processor, cause the processor to execute A method of loading a model according to the present disclosure.
  • FIG. 1 is an environmental diagram of a method of loading a model according to an embodiment of the present disclosure
  • FIG. 2 is a flow chart of a method of loading a model in accordance with an embodiment of the present disclosure
  • FIG. 3 is a flowchart of a method of detecting a loading state of a model according to an embodiment of the present disclosure
  • FIG. 4 is a flowchart of a method of detecting a loading state of a model according to another embodiment of the present disclosure
  • FIG. 5 is a flowchart of a method of loading a model according to another embodiment of the present disclosure.
  • FIG. 6 is a flowchart of a method of loading a model according to another embodiment of the present disclosure.
  • FIG. 7 is a structural block diagram of an apparatus for loading a model according to an embodiment of the present disclosure.
  • FIG. 8 is a structural block diagram of a determination module in an apparatus for loading a model according to an embodiment of the present disclosure
  • FIG. 9 is a structural block diagram of an apparatus for loading a model according to another embodiment of the present disclosure.
  • FIG. 1 is an environmental diagram of a method of loading a model according to an embodiment of the present disclosure.
  • the application environment includes a network management system 110 and a network element 120, and the network management system 110 and the network element 120 can communicate through a network.
  • the network element 120 reports its model version information and status information of each model in the network element 120 to the network management system 110.
  • the network management system 110 obtains the model version number reported by the network element 120, and determines whether the model corresponding to the model version number has been loaded according to the model version number. If not loaded, the model file corresponding to the model version number reported by the network element 120 is obtained from the network element 120 or the server and loaded into the network management system 110; if it is loaded, the network management system 110 directly uses the loaded model file to access the network element. 120 operates.
  • Network management 110 may be a mobile terminal and may include, but is not limited to, a smartphone, tablet, laptop, wearable device, and the like.
  • the network element 120 can be a server and can be implemented as a standalone server or a cluster of servers consisting of multiple servers.
  • FIG. 2 is a flow chart of a method of loading a model in accordance with an embodiment of the present disclosure.
  • the method of loading a model includes steps S210 to S250, which can be applied to the network management system 110 shown in FIG. 1.
  • a session is established with the network element.
  • the network element can be composed of one or more chassis or chassis, and can perform transmission functions independently.
  • a network element is a type of network device and is the smallest unit that can be monitored and managed in network management.
  • the network management system 110 may initiate a connection request to the network element 120, for example, a Secure Shell (SSH) protocol connection, and after establishing a connection, the two parties send messages to each other for capability exchange and establishment of a session.
  • SSH protocol is a security protocol based on the application layer developed by the IETF's Network Working Group.
  • the SSH protocol is a protocol designed to provide security for remote login sessions and other network services.
  • the SSH protocol can effectively prevent information leakage during remote management. Capability exchange is a standard process defined in the NETCONF protocol.
  • step S220 the model version number reported by the network element is queried and obtained.
  • the model version number is used to identify the version information of the network element model.
  • the model in the network element 120 can be reported as a capability of the network element 120.
  • the network management system 110 acquires the model information reported by the network element 120, and reads the model version number corresponding to the model information.
  • the corresponding packet information can be carried in the first packet (for example, a hello packet) reported by the network element 120.
  • network element 120 may also report model information by using a separate message.
  • step S230 it is determined according to the model query algorithm whether the model corresponding to the reported model version number has been loaded. If not, step S240 is performed; if it is loaded, step S250 is performed.
  • the model version algorithm compares the model version number reported by the network element 120 with the model version number that has been loaded on the network management unit 110 to determine whether the network element model corresponding to the model version number reported by the network element 120 has been recorded. .
  • the model version number of the network element model that has been loaded may be stored in the corresponding network element, or may be stored in the network management system, or may also be stored in the third-party server.
  • the network management system 110 when the network management system 110 loads a model file to the local area, the network element model corresponding to the loaded model file and its model version number may be recorded to generate a historical loading record of the model file.
  • the network management system 110 obtains the model version number reported by the network element 120, it can directly traverse the history loading record of the model file to determine whether the network element model corresponding to the model version number reported by the network element 120 has been loaded.
  • the network element 120 can mark the uploaded model by, for example, setting the state information of the uploaded model to the loading state.
  • the network management system 110 When the network management system 110 establishes a session with the network element 120 again, the network element 120 reports the model version information, and the network management unit 110 retrieves the state information of each model marked by the network element 120 to determine the model included in the reported version information. Whether the model corresponding to the version number has been loaded.
  • the loading state of the model may be marked by a third-party server, and the model corresponding to the model version number reported by the network element 120 is determined to be loaded by retrieving the model loading state list recorded in the third-party server.
  • step S240 the model file corresponding to the reported model version number is acquired, and the model file is loaded locally.
  • the network management system 110 when the network management system 110 detects that the model corresponding to the model version number reported by the network element 120 is not loaded, the network management system 110 can obtain the corresponding model file according to the model version number reported by the network element 120, and the model file is obtained. Loaded locally. After loading the model file to the local, the network administrator 110 can mark the model corresponding to the model file (eg, generate a historical load record of the model file). On the other hand, after the network element 120 uploads the model file to the network management system 110, the uploaded model file may also be marked (for example, the state information of the model corresponding to the model file is set to the loading state).
  • the step S240 may include: acquiring a model file interface corresponding to the reported model version number; and transmitting the file transfer protocol information to the network element through the model file interface, so that the network element obtaining corresponds to the reported model version number.
  • the model file and upload the model file to the server specified by the file transfer protocol information; and obtain the model file uploaded by the network element from the server specified by the file transfer protocol information.
  • the File Transfer Protocol can include an FTP server and an FTP client.
  • the FTP server is used to store files, and users can use FTP clients to access resources located on the FTP server through the FTP protocol.
  • the network management system 110 detects that the model corresponding to the model version number reported by the network element 120 is not loaded, the network file is sent to the network element 120 through the model file interface corresponding to the model version number, and the FTP protocol is used.
  • the information carries the model version information and the model file acquisition request.
  • the network element 120 After receiving the FTP protocol information, the network element 120 obtains the corresponding model file according to the model version information, and can compress the model file according to the FTP protocol, and upload the compressed model file to the FTP server.
  • the loaded model file corresponding to the reported model version number is directly used to access the network element for operation.
  • the network management system 110 detects that the model corresponding to the model version number reported by the network element 120 has been loaded, the model file accessing the network element 120 directly corresponding to the model is used, and the network element 120 is related. operating.
  • the model version number is used to distinguish different network element models, and it is determined whether the model corresponding thereto is loaded by using the model version number. When it is detected that the model has been loaded, there is no need to load the model again, thus ensuring that the same model is parsed and loaded once, which improves the efficiency of model loading and saves bandwidth.
  • FIG. 3 is a flow chart of a method of detecting a loading state of a model in accordance with an embodiment of the present disclosure.
  • the method of detecting the loading state of the model may include steps S230A and S230B.
  • a model version label set of the network element is obtained.
  • the model version label set may record the model version number of each model in the network element 120 and the status information of each model.
  • an RPC message may be separately defined in the network element 120, and a model version tag may be defined in the RPC message.
  • the model version tag may include version number information of the model (eg, "version” tag) and status information of the model (eg, "status” tag).
  • version number information of the model eg, "version” tag
  • status information of the model eg, "status” tag
  • the load/unload state of the "status” tag can be used to mark whether a model corresponding to a model version number (ie, "version” tag) is loaded.
  • the network management 110 may send an instruction to the network element 120 to acquire a model file corresponding to the model version number.
  • the network element 120 uploads the corresponding model file to the network management system 110, and changes the state information of the model corresponding to the uploaded model file, for example, changes the state of the "status" tag to load.
  • the network element 120 generates a model version label set in this way.
  • the model version tag set is traversed to detect whether the state information of the model corresponding to the reported model version number is the loaded state.
  • the state information of the model corresponding to the model file that has been uploaded by the network element tag is “load”, and the network management device can acquire and traverse the information of the network element tag to detect the loading state of the model.
  • the method for loading the model may further include: after the session is established, acquiring the first message information reported by the network element, where the first message information includes a model added in advance by using an extended standard protocol. Version Information.
  • the step S220 may include: querying the model version information in the first packet information to obtain the model version number reported by the network element.
  • the first message information may be a “hello” message transmitted between the network management system 110 and the network element 120.
  • a model version information node can be added to the standard protocol to record the model version number that the network element 120 needs to report.
  • the network version 110 directly obtains the model version number reported by the network element 120 by adding the model version information of the model reported by the network element 120 to the transmitted "hello" message.
  • the model version number reported by the network element 120 can also be obtained by defining a separate RPC message.
  • the RPC packet of the following format can be used to query the model version number that the network element 120 needs to report:
  • an RPC response message of the following form may be defined, and the model version number reported above:
  • the reported model version number is "version 1", and the state of the network element 120 is recorded as "load”. If the loading of the model file is recorded on the network management system 110 side (that is, the history loading record of the model file is generated), the status information reported by the network element 120 may be ignored; if the network management layer 110 has no loading history for recording, the network may be The status information reported by the element 120 determines whether the model corresponding to the model version number has been loaded.
  • FIG. 4 is a flowchart of a method of detecting a loading state of a model according to another embodiment of the present disclosure.
  • FIG. 4 shows an example of a method of detecting the loading state of the model in the case where the loading of the model file is recorded on the network management side, that is, in the case of generating a history loading record of the model file.
  • the method for detecting the loading state of the model may include step S230C, and according to the history loading record, detecting whether there is a model version number corresponding to the report. Model.
  • the network management system 110 can record the history loading record of the model file, and can record the history of the model file. It is stored in the storage device of the network management system 110 for long-term storage.
  • step S230C the network management system 110 acquires the stored history loading record, and detects whether there is a model corresponding to the model version number reported by the network element 120 in the history loading record. If there is a model corresponding to the model version number reported by the network element 120, the model does not need to be loaded again. If the history loading record does not exist, the model corresponding to the model version number reported by the network element 120 needs to be added.
  • the loaded model file is recorded on the network management side and the history loading record is saved, so that the loading state of the model corresponding to the model version number is not required to be obtained from the network element, and the detection efficiency of the model loading state is improved, and The problem of loading the same model for different network elements is avoided.
  • FIG. 5 is a flowchart of a method of loading a model according to another embodiment of the present disclosure.
  • the method for loading a model provided by this embodiment includes steps S501 to S507.
  • step S501 a session is established with the network element.
  • step S502 the model version number reported by the network element is obtained by using the RPC packet.
  • a model version label set of the network element is obtained.
  • the model version label set can record the model version number of each model in the network element and the status information of each model.
  • step S504 the model version label set is traversed to detect whether the state information of the model corresponding to the reported model version number is the loaded state. If it is not loaded, step S505 is performed; if it is loaded, step S507 is performed.
  • step S505 the model file interface corresponding to the model version number is obtained, and the file transfer protocol information is sent to the network element through the model file interface, so that the network element obtains the model file corresponding to the model version number, and uploads the model file to the file.
  • step S506 the model file uploaded by the network element is obtained from the server specified by the file transfer protocol.
  • step S507 the loaded model file accessing the network element corresponding to the model version number reported by the network element is directly used for operation.
  • FIG. 6 is a flowchart of a method of loading a model according to another embodiment of the present disclosure.
  • the method for loading a model provided by this embodiment includes steps S601 to S607.
  • step S601 a session is established with the network element.
  • step S602 the first message information reported by the network element is obtained.
  • the first message information includes model version information added in advance by an extended standard protocol.
  • step S603 the model version information in the first packet information is queried to obtain the model version number reported by the network element.
  • step S604 a history loading record is acquired, and it is detected whether there is a model corresponding to the reported model version number in the history loading record. If not, step S605 is performed; if yes, step S607 is performed.
  • step S605 the model file interface corresponding to the model version number is obtained, and the file transfer protocol information is sent to the network element through the model file interface, so that the network element obtains the model file corresponding to the model version number, and uploads the model file to the file.
  • step S606 the model file uploaded by the network element is obtained from the server specified by the file transfer protocol.
  • step S607 the loaded model file accessing the network element corresponding to the model version number reported by the network element is directly used for operation.
  • FIG. 7 is a structural block diagram of an apparatus for loading a model according to an embodiment of the present disclosure.
  • the apparatus for loading a model includes a session establishing module 710, a querying module 720, a determining module 730, a loading module 740, and an operating module 750.
  • the session establishment module 710 is arranged to establish a session with the network element.
  • the query module 720 is configured to query and obtain the model version number reported by the network element.
  • the determining module 730 is configured to determine, according to the model query algorithm, whether the model corresponding to the reported model version number has been loaded. When the judging module 730 judges that the model corresponding to the reported model version number is not loaded, the loading module 740 acquires the model file corresponding to the reported model version number, and loads the model file to the local. When the judging module 730 determines that the model corresponding to the reported model version number has been loaded, the operation module 750 directly accesses the network element using the loaded model file corresponding to the reported model version number.
  • the query module 720 may be further configured to: after the session is established, acquire the first packet information reported by the network element, where the first packet information includes model version information added in advance through an extended standard protocol; and the query The model version information in the first packet information is used to obtain the model version number reported by the network element.
  • the query module 720 may be further configured to: send a remote procedure call message to the network element; and receive a remote procedure call response message sent by the network element.
  • the remote procedure call response packet includes the model version number reported by the network element.
  • the loading module 740 is further configured to: acquire a model file interface corresponding to the reported model version number; and send the file transfer protocol information to the network element through the model file interface, so that the network element acquires and reports the model The model file corresponding to the version number, and the model file is uploaded to the server specified by the file transfer protocol.
  • FIG. 8 is a structural block diagram of a determination module in an apparatus for loading a model according to an embodiment of the present disclosure.
  • the break module 730 can include a first acquisition module 730A, a detection module 730B, and a status determination module 730C.
  • the first obtaining module 730A is configured to acquire a model version label set of the network element.
  • the model version label collection records the model version number of each model in the network element and the status information of each model.
  • the detection module 730B is configured to traverse the model version label set to detect status information of the model corresponding to the reported model version number.
  • the state determination module 730C is configured to determine whether the model corresponding to the reported model version number has been loaded according to the detection result of the detection module 730B.
  • FIG. 9 is a structural block diagram of an apparatus for loading a model according to another embodiment of the present disclosure.
  • the device for loading the model shown in FIG. 9 further includes a recording module 760 as compared with the embodiment shown in FIG. After loading the model file to the local, the logging module 760 records the historical loading record of the model file.
  • the determining module 730 may be configured to detect whether there is a model corresponding to the reported model version number according to the history loading record.
  • a computer readable storage medium having stored thereon computer executable instructions that, when executed by a processor, cause a processor to perform a method of loading a model according to various embodiments of the present disclosure .
  • a computer device comprising a memory and a processor.
  • Computer readable instructions are stored in the memory, and when the computer readable instructions are executed by the processor, cause the processor to perform a method of loading a model in accordance with various embodiments of the present disclosure.
  • the program can be stored in a computer readable storage medium, as in an embodiment of the present disclosure, the program can be stored in a storage medium of the computer system and executed by at least one processor in the computer system to implement The flow of an embodiment of each method.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer And Data Communications (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本公开涉及一种加载模型的方法，包括：与网元建立会话；查询并获取网元上报的模型版本号；根据模型查询算法判断与上报的模型版本号对应的模型是否已经加载；若未加载，则获取与上报的模型版本号对应的模型文件，并且将模型文件加载到本地；若已加载，则直接使用与上报的模型版本号对应的已加载的模型文件接入网元进行操作。本公开还包括一种模型加载装置、存储介质和计算机设备。

Description

模型加载方法、装置、存储介质和计算机设备 技术领域
本公开涉及通信技术领域，特别是涉及一种加载模型的方法、装置、存储介质和计算机设备。
背景技术
国际互联网工程任务组(Internet Engineering Task Force，IETF)提出了一种网络配置(NETCONF)协议，其提供了一套对于网络设备进行管理的机制。NETCONF协议采用xml格式作为数据载体，并且通过远程调用接口的方式进行数据交互。NETCONF协议采用YANG进行建模。YANG模型是一种数据建模语言，用来对由NETCONF协议、NETCONF远程过程调用(Remote Procedure Call，RPC)和NETCONF通知操作的配置数据和状态数据进行建模。
相关技术中，在网元与网管建立连接时，网元会将通过YANG描述的业务模型上报至网管。当网管接入大量的网元时，会产生大量的消息交互，消耗较多的带宽，从而严重影响网元的接入。
发明内容
本公开旨在提供一种加载模型的方法、装置、存储介质和计算机设备，通过对网元相同版本的模型只加载一次，来优化模型的加载。
本公开的实施例提供了一种加载模型的方法，包括：与网元建立会话；查询并获取所述网元上报的模型版本号；根据模型查询算法判断与所述上报的模型版本号对应的模型是否已经加载；若未加载，则获取与所述上报的模型版本号对应的模型文件，并且将所述模型文件加载到本地；若已加载，则直接使用与所述上报的模型版本号对应的已加载的模型文件接入所述网元进行操作。
本公开的实施例还提供了一种加载模型的装置，包括：会话建立模块，设置为与网元建立会话；查询模块，设置为查询并获取所述网元上报的模型版本号；判断模块，设置为根据模型查询算法判断与 所述上报的模型版本号对应的模型是否已经加载；加载模块，当所述判断模块判断与所述上报的模型版本号对应的模型未加载时，所述加载模块获取与所述上报的模型版本号对应的模型文件，并且将所述模型文件加载到本地；以及操作模块，当所述判断模块判断与所述上报的模型版本号对应的模型已加载时，所述操作模块直接使用与所述上报的模型版本号对应的已加载的模型文件接入所述网元进行操作。
本公开的实施例还提供了一种计算机可读存储介质，其上存储有计算机可执行指令，所述计算机可执行指令被处理器执行时，使得所述处理器执行根据本公开的加载模型的方法。
本公开的实施例还提供了一种计算机设备，包括存储器和处理器，所述存储器中储存有计算机可读指令，所述计算机可读指令被所述处理器执行时，使得所述处理器执行根据本公开的加载模型的方法。
附图说明
此处所说明的附图用来提供对本公开的进一步理解，构成本申请的一部分，本公开的示意性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1为应用根据本公开实施例的加载模型的方法的环境图；
图2为根据本公开实施例的加载模型的方法的流程图；
图3为根据本公开实施例的检测模型的加载状态的方法的流程图；
图4为根据本公开另一实施例的检测模型的加载状态的方法的流程图；
图5为根据本公开另一实施例的加载模型的方法的流程图；
图6为根据本公开另一实施例的加载模型的方法的流程图；
图7为根据本公开实施例的加载模型的装置的结构框图；
图8为根据本公开实施例的加载模型的装置中的判断模块的结构框图；以及
图9为根据本公开另一实施例的加载模型的装置的结构框图。
具体实施方式
为了使本公开的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本公开进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本公开，并不用于限定本公开。
图1为应用根据本公开实施例的加载模型的方法的环境图。
如图1所示，该应用环境包括网管110和网元120，并且网管110和网元120可通过网络进行通信。网管110和网元120建立会话后，网元120上报其模型版本信息和网元120中的各个模型的状态信息至网管110。网管110获取网元120上报的模型版本号，并根据模型版本号判断与该模型版本号对应的模型是否已经加载。若未加载，则从网元120或者服务器获取与网元120上报的模型版本号对应的模型文件并加载到网管110本地；若已加载，则网管110直接使用已加载的模型文件接入网元120进行操作。网管110可以是移动终端，并且可以包括(但不仅限于)智能手机、平板电脑、笔记本电脑、穿戴设备等。网元120可以是服务器，并且可以实现为独立的服务器或者由多个服务器组成的服务器集群。
图2为根据本公开实施例的加载模型的方法的流程图。
如图2所示，根据本公开实施例的加载模型的方法包括步骤S210至S250，该方法可应用于图1所示的网管110。
在步骤S210处，与网元建立会话。
网元可以由一个或多个机盘或机框组成，并且能够独立完成传输功能。网元是一种网络设备，并且是网络管理中可以监视和管理的最小单位。
参见图1和图2，网管110可以向网元120发起，例如，安全外壳(Secure Shell，SSH)协议连接请求，并且在建立连接后，双方相互发送报文，以进行能力交换并建立会话。SSH协议是由IETF的网络小组(Network Working Group)制定的、建立在应用层基础上的安全协议。SSH协议是专为远程登录会话和其他网络服务提供安全性的协议。利用SSH协议可以有效防止远程管理过程中的信息泄露问题。能力交换是NETCONF协议中定义的一种标准流程。
在步骤S220处，查询并获取网元上报的模型版本号。
模型版本号用来标识网元模型的版本信息。参见图1和图2，在网管110与网元120建立会话后，网元120中的模型可以作为网元120的一种能力进行上报。网管110获取网元120上报的模型信息，并读取与模型信息对应的模型版本号。在网管110与网元120建立连接后，可以在网元120上报的第一个报文(例如，hello报文)中携带对应的模型信息。可替换地，网元120也可以通过使用单独的报文上报模型信息。
在步骤S230处，根据模型查询算法判断与上报的模型版本号对应的模型是否已经加载。若未加载，则执行步骤S240；若已加载，则执行步骤S250。
在本文中，通过模型查询算法来对网元120上报的模型版本号与已经在网管110加载的模型版本号进行比较，来判断与网元120上报的模型版本号对应的网元模型是否已经记载。
根据本公开各实施例，已经加载网元模型的模型版本号可以存储在对应的网元中，也可以存储在网管中，或者还可以存储在第三方服务器中。
参见图1和图2，网管110每加载一个模型文件到本地时，可以记录与加载的模型文件对应的网元模型及其模型版本号，以生成模型文件的历史加载记录。当网管110获取到网元120上报的模型版本号时，可以直接遍历模型文件的历史加载记录，来判断与网元120上报的模型版本号对应的网元模型是否已经加载。另一方面，当网元120与网管110建立会话并上传对应的模型文件后，网元120可以通过，例如，将已上传的模型的状态信息设置为加载状态的方式来标记已上传的模型。当网管110再次与该网元120建立会话时，网元120上报模型版本信息，并且网管110调取网元120标记的各个模型的状态信息，来判断与包括在上报的模型版本信息中的模型版本号对应的模型是否已经加载。此外，还可以通过第三方服务器来标记模型的加载状态，并且通过调取第三方服务器中记录的模型加载状态列表来判断与网元120上报的模型版本号对应的模型是否已经加载。
在步骤S240处，获取与上报的模型版本号对应的模型文件，并且将模型文件加载到本地。
参见图1和图2，当网管110检测到与网元120上报的模型版本号对应的模型未加载时，网管110可以根据网元120上报的模型版本号获取对应的模型文件，并且将模型文件加载到本地。在将模型文件加载到本地之后，网管110可以对与模型文件对应的模型进行标记(例如，生成模型文件的历史加载记录)。另一方面，网元120在将模型文件上传至网管110后，也可以对上传的模型文件进行标记(例如，将与模型文件对应的模型的状态信息设置为加载状态)。
根据本公开实施例，步骤S240可以包括：获取与上报的模型版本号对应的模型文件接口；通过模型文件接口下发文件传输协议信息到网元，以使网元获取与上报的模型版本号对应的模型文件，并且将模型文件上传至文件传输协议信息指定的服务器；以及从文件传输协议信息指定的服务器获取网元上传的模型文件。
文件传输协议(File Transfer Protocol，FTP)可以包括FTP服务器和FTP客户端。FTP服务器用来存储文件，并且用户可以使用FTP客户端通过FTP协议访问位于FTP服务器上的资源。
参见图1和图2，当网管110检测到与网元120上报的模型版本号对应的模型未加载时，通过与模型版本号对应的模型文件接口向网元120发送FTP信息，并且在FTP协议信息中携带模型版本信息与模型文件获取请求。网元120接收到FTP协议信息后，根据模型版本信息获取对应的模型文件，并且可以根据FTP协议对模型文件进行压缩，并且将压缩后的模型文件上传至FTP服务器。
在步骤S250处，直接使用与上报的模型版本号对应的已加载的模型文件接入网元进行操作。
参见图1和图2，如果网管110检测到与网元120上报的模型版本号对应的模型已经加载，则直接使用与该模型对应的模型文件接入网元120，并对网元120进行相关操作。
根据本实施例，使用模型版本号区分不同的网元模型，并使通过利用模型版本号来判断与其对应的模型是否加载。当检测到模型已 经加载时，则无需对模型再次进行加载，从而保证相同的模型只要解析加载一次，提高了模型加载的效率，并节省了带宽。
图3为根据本公开实施例的检测模型的加载状态的方法的流程图。
如图3所示，根据本公开实施例的检测模型的加载状态的方法(即，图2示出的步骤S230)可以包括步骤S230A和S230B。
在步骤S230A处，获取网元的模型版本标签集合。
参见图1和图3，模型版本标签集合可以记录网元120中的各个模型的模型版本号和各个模型的状态信息。根据本公开实施例，可以在网元120中单独定义RPC报文，并且在RPC报文中定义模型版本标签。模型版本标签中可以包括模型的版本号信息(例如，“version”标签)和模型的状态信息(例如，“status”标签)。例如，可以通过“status”标签的load/unload状态来标记与某一模型版本号(即，“version”标签)对应的模型是否被加载。
在检测到与网元120上报的模型版本号对应的模型未加载时，网管110可以向网元120发送获取与模型版本号对应的模型文件的指令。网元120在接收到获取模型文件的指令后向网管110上传对应的模型文件，并更改与上传的模型文件对应的模型的状态信息，例如，将“status”标签的状态改为load。网元120通过这种方式来生成模型版本标签集合。
在步骤S230B处，遍历模型版本标签集合，以检测与上报的模型版本号对应的模型的状态信息是否为已加载状态。
根据本实施例，通过网元标记与已经上传的模型文件对应的模型的状态信息为“load”，网管可以获取并遍历网元标记的信息，以检测模型的加载状态。
根据本公开实施例，在步骤S220之前，加载模型的方法还可以包括：在会话建立后，获取网元上报的第一报文信息，第一报文信息中包括预先通过扩展标准协议添加的模型版本信息。在此情况下，步骤S220可以包括：查询第一报文信息中的模型版本信息，以获取网元上报的模型版本号。
参见图1和图2，第一报文信息可以是在网管110和网元120之间传递的“hello”报文。在NETCONF协议的基础上，通过扩展标准协议，可以在标准协议中添加模型版本信息节点，以记载网元120需要上报的模型版本号。在网管110和网元120建立连接后，通过在发送的“hello”报文中添加网元120上报的模型的模型版本信息，可以使网管110直接获取到网元120上报的模型版本号。
根据本公开实施例，还可以通过定义单独的RPC报文来获取网元120上报的模型版本号。例如，在网管110侧，可以定义，例如，如下形式的RPC报文对网元120需要上报的模型版本号进行查询：
Figure PCTCN2018093586-appb-000001
在此情况下，在网元120侧，可以定义，例如，如下形式的RPC应答报文，以上报的模型版本号：
Figure PCTCN2018093586-appb-000002
在上述PRC应答报文中，上报的模型版本号为“version 1”，并且在网元120侧记录了其状态为“load”。如果在网管110侧对模型文件的加载进行记录(即，生成模型文件的历史加载记录)，则可以忽略网元120上报的状态信息；如果网管110侧没有即加载历史进行记录，则可以根据网元120上报的状态信息来确定与模型版本号对 应的模型是否已经加载。
图4为根据本公开另一实施例的检测模型的加载状态的方法的流程图。图4示出了在网管侧对模型文件的加载进行记录，即，生成模型文件的历史加载记录的情况下，检测模型的加载状态的方法的示例。
如图4所示，根据本公开实施例的检测模型的加载状态的方法(即，图2示出的步骤S230)可以包括步骤S230C，根据历史加载记录，检测是否存在与上报的模型版本号对应的模型。
参见图1、图2和图4，在将模型文件加载到本地(即，图2示出的步骤S240)后，网管110可以记录模型文件的历史加载记录，并且可以将模型文件的历史加载记录保存在网管110的存储装置中，以长久保存。
在步骤S230C中，网管110获取存储的历史加载记录，并且检测历史加载记录中是否存在与网元120上报的模型版本号对应的模型。若历史加载记录存在与网元120上报的模型版本号对应的模型，则无需对模型再次进行加载；若历史加载记录不存在，则需要加装与网元120上报的模型版本号对应的模型。
根据本实施例，在网管侧对加载的模型文件进行记载并保存历史加载记录，从而不需要从网元获取与模型版本号对应的模型的加载状态，提高了对模型加载状态的检测效率，并且避免了针对不同网元加载相同模型的问题。
图5为根据本公开另一实施例的加载模型的方法的流程图。
如图5所示，本实施例提供的加载模型的方法包括步骤S501至S507。
在步骤S501，与网元建立会话。
在步骤S502，通过RPC报文获取网元上报的模型版本号。
在步骤S503，获取网元的模型版本标签集合。模型版本标签集合可以记录网元中的各个模型的模型版本号和各个模型的状态信息。
在步骤S504，遍历模型版本标签集合，以检测与上报的模型版本号对应的模型的状态信息是否为已加载状态。若未加载，则执行步 骤S505；若已加载，则执行步骤S507。
在步骤S505，获取与模型版本号对应的模型文件接口，通过模型文件接口下发文件传输协议信息到网元，以使网元获取与模型版本号对应的模型文件，并将模型文件上传至文件传输协议指定的服务器。
在步骤S506，从文件传输协议指定的服务器获取网元上传的模型文件。
在步骤S507，直接使用与网元上报的模型版本号对应的已加载的模型文件接入网元进行操作。
图6为根据本公开另一实施例的加载模型的方法的流程图。
如图6所示，本实施例提供的加载模型的方法包括步骤S601至S607。
在步骤S601，与网元建立会话。
在步骤S602，获取网元上报的第一报文信息。第一报文信息中包括预先通过扩展标准协议添加的模型版本信息。
在步骤S603，查询第一报文信息中的模型版本信息，以获取网元上报的模型版本号。
在步骤S604，获取历史加载记录，并且检测历史加载记录中是否存在与上报的模型版本号对应的模型。若不存在，则执行步骤S605；若存在，则执行步骤S607。
在步骤S605，获取与模型版本号对应的模型文件接口，通过模型文件接口下发文件传输协议信息到网元，以使网元获取与模型版本号对应的模型文件，并将模型文件上传至文件传输协议指定的服务器。
在步骤S606，从文件传输协议指定的服务器获取网元上传的模型文件。
在步骤S607，直接使用与网元上报的模型版本号对应的已加载的模型文件接入网元进行操作。
图7为根据本公开实施例的加载模型的装置的结构框图。
如图7所示，根据本公开实施例的加载模型的装置包括会话建立模块710、查询模块720、判断模块730、加载模块740和操作模块750。
会话建立模块710设置为与网元建立会话。查询模块720设置为查询并获取网元上报的模型版本号。判断模块730设置为根据模型查询算法判断与上报的模型版本号对应的模型是否已经加载。当判断模块730判断与上报的模型版本号对应的模型未加载时，加载模块740获取与上报的模型版本号对应的模型文件，并且将模型文件加载到本地。当判断模块730判断与上报的模型版本号对应的模型已加载时，操作模块750直接使用与上报的模型版本号对应的已加载的模型文件接入网元进行操作。
根据本公开实施例，查询模块720还可以设置为：在会话建立后，获取网元上报的第一报文信息，第一报文信息中包括预先通过扩展标准协议添加的模型版本信息；以及查询第一报文信息中的模型版本信息，以获取网元上报的模型版本号。
根据本公开实施例，查询模块720还可以设置为：向网元发送远程过程调用报文；以及接收网元发送的远程过程调用应答报文。远程过程调用应答报文包括网元上报的模型版本号。
根据本公开实施例中，加载模块740还设置为：获取与上报的模型版本号对应的模型文件接口；通过模型文件接口下发文件传输协议信息到网元，以使网元获取与上报的模型版本号对应的模型文件，并且将模型文件上传至文件传送协议指定的服务器。
图8为根据本公开实施例的加载模型的装置中的判断模块的结构框图。
如图8所示，断模块730可以包括第一获取模块730A、检测模块730B和状态确定模块730C。
第一获取模块730A设置为获取网元的模型版本标签集合。模型版本标签集合记录了网元中的各个模型的模型版本号和各个模型的状态信息。检测模块730B设置为遍历模型版本标签集合，以检测与上报的模型版本号对应的模型的状态信息。状态确定模块730C设置为根据检测模块730B的检测结果来确定与上报的模型版本号对应的模型是否已加载。
图9为根据本公开另一实施例的加载模型的装置的结构框图。
如图9所示，与图7所示的实施例相比，图9所示的加载模型的装置还包括记录模块760。在将模型文件加载到本地后，记录模块760记录模型文件的历史加载记录。在此情况下，判断模块730可以设置为：根据历史加载记录，检测是否存在与上报的模型版本号对应的模型。
根据本公开实施例，提供了一种计算机可读存储介质，其上存储有计算机可执行指令，计算机可执行指令被处理器执行时，使得处理器执行根据本公开各实施例的加载模型的方法。
在一个实施例中，提供一种计算机设备，包括存储器和处理器。存储器中储存有计算机可读指令，计算机可读指令被处理器执行时，使得处理器执行根据本公开各实施例的加载模型的方法。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，可以通过计算机程序指令相关的硬件来完成。所述程序可存储于计算机可读取存储介质中，如本公开实施例中，该程序可存储于计算机***的存储介质中，并被计算机***中的至少一个处理器执行，以实现包括如上述各方法的实施例的流程。存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory，ROM)或随机存储记忆体(Random Access Memory，RAM)等。
以上所述实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本公开的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本公开构思的前提下，还可以做出若干变形和改进，这些都属于本公开的保护范围。因此，本公开的保护范围应以所附权利要求为准。

Claims (13)

  1. 一种加载模型的方法，包括：
    与网元建立会话；
    查询并获取所述网元上报的模型版本号；
    根据模型查询算法判断与所述上报的模型版本号对应的模型是否已经加载；
    若未加载，则获取与所述上报的模型版本号对应的模型文件，并且将所述模型文件加载到本地；
    若已加载，则直接使用与所述上报的模型版本号对应的已加载的模型文件接入所述网元进行操作。
  2. 根据权利要求1所述的加载模型的方法，其中，所述根据模型查询算法判断与所述上报的模型版本号对应的模型是否已经加载的步骤包括：
    获取所述网元的模型版本标签集合，所述模型版本标签集合记录了所述网元中的各个模型的模型版本号和各个模型的状态信息；以及
    遍历所述模型版本标签集合，以检测与所述上报的模型版本号对应的模型的状态信息是否为已加载状态。
  3. 根据权利要求1所述的加载模型的方法，其中，在所述查询并获取所述网元上报的模型版本号的步骤之前，还包括：
    在会话建立后，获取所述网元上报的第一报文信息，所述第一报文信息中包括预先通过扩展标准协议添加的模型版本信息，并且
    所述查询并获取所述网元上报的模型版本号的步骤包括：
    查询所述第一报文信息中的所述模型版本信息，以获取所述网元上报的模型版本号。
  4. 根据权利要求1所述的加载模型的方法，还包括：
    在将所述模型文件加载到本地后，记录模型文件的历史加载记录，并且
    所述根据模型查询算法判断与所述上报的模型版本号对应的模型是否已经加载的步骤包括：
    根据所述历史加载记录，检测是否存在与所述上报的模型版本号对应的模型。
  5. 根据权利要求1所述的加载模型的方法，其中，所述获取与所述上报的模型版本号对应的模型文件的步骤包括：
    获取与所述上报的模型版本号对应的模型文件接口；
    通过所述模型文件接口下发文件传输协议信息到所述网元，以使所述网元获取与所述上报的模型版本号对应的模型文件，并且将所述模型文件上传至所述文件传输协议指定的服务器；以及
    从所述文件传输协议指定的服务器获取所述网元上传的模型文件。
  6. 根据权利要求1所述的加载模型的方法，其中，所述查询并获取所述网元上报的模型版本号的步骤包括：
    向所述网元发送远程过程调用报文；以及
    接收所述网元发送的远程过程调用应答报文，
    其中，所述远程过程调用应答报文包括所述网元上报的模型版本号。
  7. 一种加载模型的装置，包括：
    会话建立模块，设置为与网元建立会话；
    查询模块，设置为查询并获取所述网元上报的模型版本号；
    判断模块，设置为根据模型查询算法判断与所述上报的模型版本号对应的模型是否已经加载；
    加载模块，当所述判断模块判断与所述上报的模型版本号对应的模型未加载时，所述加载模块获取与所述上报的模型版本号对应的 模型文件，并且将所述模型文件加载到本地；以及
    操作模块，当所述判断模块判断与所述上报的模型版本号对应的模型已加载时，所述操作模块直接使用与所述上报的模型版本号对应的已加载的模型文件接入所述网元进行操作。
  8. 根据权利要求7所述的加载模型的装置，其中，所述判断模块包括：
    第一获取模块，设置为获取所述网元的模型版本标签集合，所述模型版本标签集合记录了所述网元中的各个模型的模型版本号和各个模型的状态信息；
    检测模块，设置为遍历所述模型版本标签集合，以检测与所述上报的模型版本号对应的模型的状态信息；以及
    状态确定模块，设置为根据所述检测模块的检测结果来确定与所述上报的模型版本号对应的模型是否已加载。
  9. 根据权利要求7所述的加载模型的装置，其中，所述查询模块还设置为：
    在会话建立后，获取所述网元上报的第一报文信息，所述第一报文信息中包括预先通过扩展标准协议添加的模型版本信息；以及
    查询所述第一报文信息中的所述模型版本信息，以获取所述网元上报的模型版本号。
  10. 根据权利要求7所述的加载模型的装置，还包括：
    记录模块，在将所述模型文件加载到本地后，所述记录模块记录所述模型文件的历史加载记录，并且
    所述判断模块设置为：
    根据所述历史加载记录，检测是否存在与所述上报的模型版本号对应的模型。
  11. 根据权利要求7所述的加载模型的装置，其中，所述加载 模块还设置为：
    获取与所述上报的模型版本号对应的模型文件接口；
    通过所述模型文件接口下发文件传输协议信息到所述网元，以使所述网元获取与所述上报的模型版本号对应的模型文件，并且将所述模型文件上传至所述文件传输协议指定的服务器；以及
    从所述文件传输协议指定的服务器获取所述网元上传的模型文件。
  12. 根据权利要求7所述的加载模型的装置，其中，所述查询模块还设置为：
    向所述网元发送远程过程调用报文；以及
    接收所述网元发送的远程过程调用应答报文，
    其中，所述远程过程调用应答报文包括所述网元上报的模型版本号。
  13. 一种计算机可读存储介质，其上存储有计算机可执行指令，所述计算机可执行指令被处理器执行时，使得所述处理器执行根据权利要求1至6中任一项所述的加载模型的方法。
PCT/CN2018/093586 2017-06-30 2018-06-29 模型加载方法、装置、存储介质和计算机设备 WO2019001562A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710525690.6 2017-06-30
CN201710525690.6A CN109218354A (zh) 2017-06-30 2017-06-30 模型加载方法、装置、存储介质和计算机设备

Publications (1)

Publication Number Publication Date
WO2019001562A1 true WO2019001562A1 (zh) 2019-01-03

Family

ID=64741141

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/093586 WO2019001562A1 (zh) 2017-06-30 2018-06-29 模型加载方法、装置、存储介质和计算机设备

Country Status (2)

Country Link
CN (1) CN109218354A (zh)
WO (1) WO2019001562A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112528283A (zh) * 2020-12-15 2021-03-19 微医云(杭州)控股有限公司 Sdk收集用户信息的检测方法及装置、电子设备、存储介质
WO2023279848A1 (zh) * 2021-07-06 2023-01-12 华为技术有限公司 一种查询方法、装置及设备

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112395437B (zh) * 2019-08-16 2024-04-30 北京百度网讯科技有限公司 一种3d模型的加载方法、装置、电子设备及存储介质
CN115701042A (zh) * 2021-07-29 2023-02-07 华为技术有限公司 配置更新的方法、装置、***及计算机可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101212342A (zh) * 2006-12-27 2008-07-02 大唐移动通信设备有限公司 多版本网元的网络管理方法
CN101447891A (zh) * 2008-04-17 2009-06-03 中兴通讯股份有限公司 业务模型自适应***及方法
US8341594B1 (en) * 2004-07-08 2012-12-25 The Mathworks, Inc. Version control in modeling environments
CN106487567A (zh) * 2015-09-02 2017-03-08 中兴通讯股份有限公司 一种网元模型管理方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102238033A (zh) * 2011-07-04 2011-11-09 中兴通讯股份有限公司 低级网管***的管理方法及装置、***
US9900209B2 (en) * 2015-09-14 2018-02-20 Cisco Technology, Inc. Techniques for YANG model version control validation
CN105808748B (zh) * 2016-03-14 2017-11-07 广州市诚毅科技软件开发有限公司 一种mib版本对比方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8341594B1 (en) * 2004-07-08 2012-12-25 The Mathworks, Inc. Version control in modeling environments
CN101212342A (zh) * 2006-12-27 2008-07-02 大唐移动通信设备有限公司 多版本网元的网络管理方法
CN101447891A (zh) * 2008-04-17 2009-06-03 中兴通讯股份有限公司 业务模型自适应***及方法
CN106487567A (zh) * 2015-09-02 2017-03-08 中兴通讯股份有限公司 一种网元模型管理方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112528283A (zh) * 2020-12-15 2021-03-19 微医云(杭州)控股有限公司 Sdk收集用户信息的检测方法及装置、电子设备、存储介质
WO2023279848A1 (zh) * 2021-07-06 2023-01-12 华为技术有限公司 一种查询方法、装置及设备

Also Published As

Publication number Publication date
CN109218354A (zh) 2019-01-15

Similar Documents

Publication Publication Date Title
US10392823B2 (en) Synthetic client
WO2019001562A1 (zh) 模型加载方法、装置、存储介质和计算机设备
WO2019029525A1 (zh) 网络功能信息的管理方法及相关设备
US10476758B2 (en) Systems and methods for providing notifications of changes in a cloud-based file system
BR112021013594A2 (pt) Método e sistema de armazenamento compartilhável para análise de dados de rede
JP6686033B2 (ja) メッセージをプッシュするための方法および装置
US11363679B2 (en) Facilitating integrated management of connected assets in 5G and other advanced networks
US11888653B2 (en) Managing network packet flows based on device information
CN116057924A (zh) 用于提供网络功能发现服务增强的方法、***和计算机可读介质
US9015344B2 (en) Method, apparatus and system for managing private network remotely using session initiation protocol
US10616066B2 (en) Device discovery in a network environment
WO2015127603A1 (zh) 一种接口管理服务实体、功能服务实体及网元管理方法
WO2016086755A1 (zh) 一种报文处理的方法和透明代理服务器
CN108768849A (zh) 报文处理方法及装置
CN116097691A (zh) 服务请求处置
US9277014B2 (en) Handling of auxiliary NAS
WO2017005118A1 (zh) 维持通信连接的方法、装置、终端及服务器
US8005967B2 (en) Policy negotiation system and method
EP3002910B1 (en) Connecting computer management systems via cellular digital telecommunication networks
US9465541B2 (en) Apparatus and method for constructing storage virtualization network
TW201719455A (zh) 詮釋資料伺服器、網路裝置及自動資源管理方法
WO2010020153A1 (zh) 一种根据用户状态选择用户的方法、装置和***
US20170093610A1 (en) Proactive M2M Framework Using Device-Level vCard for Inventory, Identity, and Network Management
US11258540B2 (en) Ultra-reliability for cellular vehicle-to-everything (C-V2X) PC5 communications
WO2016106557A1 (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: 18823275

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

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 28/05/2020)