WO2017096791A1 - 一种诊断测试消息处理方法及装置 - Google Patents

一种诊断测试消息处理方法及装置 Download PDF

Info

Publication number
WO2017096791A1
WO2017096791A1 PCT/CN2016/088222 CN2016088222W WO2017096791A1 WO 2017096791 A1 WO2017096791 A1 WO 2017096791A1 CN 2016088222 W CN2016088222 W CN 2016088222W WO 2017096791 A1 WO2017096791 A1 WO 2017096791A1
Authority
WO
WIPO (PCT)
Prior art keywords
request message
network management
diagnostic
message
client
Prior art date
Application number
PCT/CN2016/088222
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 WO2017096791A1 publication Critical patent/WO2017096791A1/zh

Links

Images

Classifications

    • 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/04—Network management architectures or arrangements
    • H04L41/042—Network management architectures or arrangements comprising distributed management centres cooperatively managing the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning

Definitions

  • This application relates to, but is not limited to, the field of electronic technology.
  • the board diagnostic request is sent to the board to be diagnosed, and then the diagnostic test result returned by the board to be diagnosed is received.
  • multiple diagnostic boards may be diagnosed at the same time. Therefore, multiple diagnostic tasks may exist in the system at the same time. Some diagnostic tasks may take a long time, or there may be multiple diagnostic tasks. Dependencies.
  • the implementation of the diagnostic board in the related art is: in the network management system, after receiving a certain diagnosis request of a board, the state machine for the diagnosis request for the board is started, and then the state machine exclusively processes the The test result of the diagnostic request of the board. Diagnosing a board in the above manner. If you need to diagnose a large number of boards and perform multiple types of diagnostics on each board, you may use too many system resources because you create too many state machines.
  • the present invention provides a method and a device for processing a diagnostic test message to solve the problem that the board diagnosis mode in the related art is too much, resulting in excessive system resources.
  • a diagnostic test message processing method comprising:
  • the network management server receives the diagnostic request message sent by the at least two network management clients for performing diagnostic tests on the plurality of to-be-diagnosed boards.
  • the network management server generates, according to the attribute information of each diagnosis request message, a unique identifier that is in one-to-one correspondence with each of the diagnosis request messages;
  • the network management server adds each of the unique identifiers to the corresponding diagnostic request message, and sends a diagnosis request message that is added to the plurality of to-be-tested boards.
  • the network management server receives the test result information sent by the multiple test boards, where each test result information carries a unique identifier in the corresponding diagnosis request message;
  • the network management server sends each test result information to the corresponding network management client according to the unique identifier in each of the test result information.
  • the diagnostic test message processing method further includes:
  • the network management server After receiving the first diagnosis request message sent by the first network management client of the at least two network management clients to perform diagnostic test on one of the to-be diagnosed boards, the network management server detects that the second network management client has sent And a second diagnostic request message that is the same as the first diagnostic request message, and processes the first diagnostic request message according to the mutually exclusive attributes of the second diagnostic request message and the first diagnostic request message.
  • the network management server processes the first diagnostic request message according to the mutually exclusive attributes of the second diagnostic request message and the first diagnostic request message, including:
  • the network management server rejects the first diagnosis request message of the first network management client when determining that the mutually exclusive attribute of the second diagnosis request message is a mutually exclusive type; wherein the mutual exclusion type indicates Before the end condition of the target diagnosis request message is satisfied, the target diagnosis request message is waited for or processed, and the same diagnosis request message sent by the other client as the target diagnosis request message is rejected.
  • the network management server processes the first diagnostic request message according to the mutually exclusive attributes of the second diagnostic request message and the first diagnostic request message, including:
  • the network management server determines that the mutually exclusive attribute of the second diagnosis request message is a coexistence type, the first unique identifier corresponding to the first diagnosis request message and the second corresponding to the second diagnosis request message are recorded. Uniquely identifies;
  • the network management server When receiving the test result corresponding to the second diagnosis request message, the network management server sends the test result to the first network management client according to the first unique identifier and the second unique identifier.
  • the second network management client When receiving the test result corresponding to the second diagnosis request message, the network management server sends the test result to the first network management client according to the first unique identifier and the second unique identifier. The second network management client.
  • the network management server according to the second diagnosis request message and the first diagnosis request
  • the mutually exclusive attribute of the message is processed to process the first diagnosis request message, including:
  • the network management server determines that the mutually exclusive attribute registered by the second diagnosis request message is a steal type, records the second unique identifier corresponding to the second diagnosis request message;
  • the network management server deletes the first diagnosis request message, and when receiving the test result corresponding to the second diagnosis request message, sends the test result to the second network management according to the second unique identifier. Client.
  • the network management server detects that the second network management client has sent the second diagnosis request message that is the same as the first diagnosis request message, and includes:
  • a diagnostic test message processing device comprising:
  • the receiving module is configured to: receive a diagnosis request message that is sent by the at least two network management clients to perform diagnostic tests on multiple to-be-diagnosed boards;
  • the identifier generating module is configured to: generate, according to the attribute information of each diagnostic request message received by the receiving module, a unique identifier corresponding to each of the diagnostic request messages;
  • the interaction module is configured to: add each of the unique identifiers generated by the identifier generation module to a corresponding diagnosis request message, and send a diagnosis request message that is added to the multiple identifiers to the plurality of to-be-tested board;
  • the interaction module is further configured to: receive the test result information sent by the multiple boards to be tested; wherein each of the test result information carries a unique identifier in the corresponding diagnosis request message;
  • the feedback module is configured to: send each test result information to the corresponding network management client according to the unique identifier in each of the test result information received by the interaction module.
  • the diagnostic test message processing apparatus further includes:
  • the conflict processing module is configured to: after receiving the first diagnosis request message sent by the first network management client of the at least two network management clients to perform diagnostic test on one of the to-be diagnosed boards, detecting the second network management client The terminal has sent the second diagnostic request message that is the same as the first diagnostic request message, according to the mutually exclusive attribute of the second diagnostic request message and the first diagnostic request message. Processing the first diagnostic request message.
  • the conflict processing module is configured to: reject the first diagnosis request message of the first network management client when determining that the mutually exclusive attribute registered by the second diagnosis request message is a mutually exclusive type
  • the mutex type indicates that the target diagnostic request message is awaited or processed before the end condition of the target diagnostic request message is satisfied, and the same diagnostic request message sent by the other client as the target diagnostic request message is rejected.
  • the conflict processing module is configured to: when determining that the mutually exclusive attribute registered by the second diagnosis request message is a coexistence type, record the first unique identifier and the corresponding corresponding to the first diagnosis request message a second unique identifier corresponding to the second diagnostic request message; when receiving the test result corresponding to the second diagnostic request message, sending the test result according to the first unique identifier and the second unique identifier And the first network management client and the second network management client.
  • the conflict processing module is configured to: when determining that the mutually exclusive attribute registered by the second diagnosis request message is a steal type, recording a second unique identifier corresponding to the second diagnosis request message; deleting And the first diagnosis request message, and when receiving the test result corresponding to the second diagnosis request message, sending the test result to the second network management client according to the second unique identifier.
  • the diagnostic test message processing method and device processes a plurality of diagnostic test request messages by using a public state machine, and generates a one-to-one corresponding unique identifier according to the attribute of each diagnostic request message, thereby
  • the public state machine can separately process multiple diagnostic test requests according to the unique identifier, and feed back the processed result to the client that sends the request message, thereby achieving the effect of processing multiple diagnostic test requests in one state machine.
  • the embodiment of the invention solves the phenomenon that the resources occupied by the diagnostic test are high when a large number of boards in the related art need to be simultaneously diagnosed and tested.
  • FIG. 1 is a schematic flowchart of a method for processing a diagnostic test message according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of an application scenario of a method for processing a diagnostic test message according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of another method for processing a diagnostic test message according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of an interaction process for processing the same request message in a diagnostic test message processing method according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of another interaction process for processing the same request message in the diagnostic test message processing method according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram of another interaction process for processing the same request message in the method for processing a diagnostic test message according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of another interaction process for processing the same request message in the method for processing a diagnostic test message according to an embodiment of the present disclosure
  • FIG. 8 is a schematic diagram of an interaction process for processing the same request message in the method for processing a diagnostic test message according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a device for processing a diagnostic test message according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of another diagnostic test message processing apparatus according to an embodiment of the present invention.
  • FIG. 1 is a schematic flowchart diagram of a method for processing a diagnostic test message according to an embodiment of the present invention. The method provided in this embodiment is as follows:
  • the implementation of the provided method may include the following steps, that is, steps 101 to 105:
  • Step 101 The network management server receives, by using at least two network management clients, a diagnostic request message for performing diagnostic tests on multiple to-be-diagnosed boards.
  • Step 102 The network management server generates, according to the attribute information of each diagnosis request message, a unique identifier corresponding to each diagnosis request message.
  • Step 103 The network management server adds each unique identifier to the corresponding diagnosis request message, and sends a diagnosis request message that is added to the plurality of to-be-tested boards.
  • Step 104 The network management server receives test result information sent by multiple boards to be tested, where each test result information carries a unique identifier in the corresponding diagnosis request message.
  • Step 105 The network management server sends each test result information to the corresponding network management client according to the unique identifier in each test result information.
  • FIG. 2 is a schematic diagram of an application scenario of a method for processing a diagnostic test message according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of another method for processing a diagnostic test message according to an embodiment of the present invention.
  • the implementation manner of the method for processing the diagnostic test message provided by the embodiment of the present invention may include the following steps, that is, steps 201 to 210:
  • Step 201 The network management client sends a diagnosis request message (Req_1 message) to the message processing framework in the diagnostic test module in the network management server.
  • Req_1 message a diagnosis request message
  • Step 202 The message processing framework in the network management server uses the Req_1 message as a parameter to generate the content of the Req_2 message sent to the agent (Agent) in the network element.
  • the network management server invokes the application (Application, referred to as APP).
  • the interface obtains the message type attribute, the mutually exclusive attribute, the managed object attribute, and the like corresponding to the Req_1, and generates a message content to the Req_2 sent to the agent in the network element.
  • Step 203 The message processing framework in the network management server uses the Req_1 message as a parameter, and invokes its own task manager to generate a globally unique task ID.
  • the task ID and Req_1 are in a one-to-one correspondence.
  • Step 204 The diagnostic test module in the network management server sends a Req_2 message to the proxy in the network element, where the Req_2 message carries the task ID.
  • Step 205 After receiving the Req_2 message, the agent in the network element stores the task ID in its own task manager, and sends a diagnosis request message (Req_3 message) that does not carry the task ID to the managed object (NE Object). ).
  • Step 206 The managed object performs a diagnostic test on the board, and sends a diagnosis result to form an Ack_1 message to the agent in the network element.
  • Step 207 After receiving the Ack_1 message, the agent in the network element adds the task ID to form an Ack_2 message, and sends the Ack_2 message to the message processing framework in the diagnostic test module in the network management server.
  • Step 208 After receiving the message, the diagnostic test module in the network management server finds the processing object corresponding to the APP according to the task ID, and calls the processing object to process the Ack_2 message to form the Ack_3 message content recognizable by the network management client.
  • Step 209 The diagnostic test module in the network management server sends an Ack_3 message to the corresponding network management request client.
  • step 210 the managed object sends the message carrying the task ID directly to the agent in the network element when the subsequent message continues to be reported.
  • the network management server and the managed object can directly interact with each other. Therefore, in order to save the detected message flow, the network management system can also interact with the proxy process on the entity where the managed object is located. That is, the diagnostic request message is not processed by the proxy object in the network element of FIG. 2, and the request message and the response message that are not processed by the proxy object need to carry the task ID, so that the diagnostic test module in the network management network management server can diagnose the test result according to the task ID. Take action.
  • Standard message A request message corresponds to a response message, the network management server sends a request message, and the managed object returns a response message.
  • One request message corresponds to multiple response messages
  • the network management server sends a request message
  • the managed object returns multiple response messages.
  • Monitoring message The network management server issues a monitoring start request message, and the managed object returns a monitoring start request success message, and then the managed object starts reporting the related information of the monitored object until the network management server issues a monitoring stop request message, and the managed object returns the monitoring request. Stop successful response.
  • MSG TYPE the type of the above message (Message Type, which can be expressed as: MSG TYPE) can be defined as: MSG_TYPE_NORMAL, MSG_TYPE_REPROT and MSG_TYPE_TASK.
  • the processing manner of the message when the same request is sent by the different clients may be implemented, and the processing is performed by the principle that the same request message is mutually exclusive, including the following processing manners:
  • Mutually exclusive messages Wait until the end condition is met, waiting for or processing the response message of the managed object, rejecting the same request from other clients.
  • Snatch message Before the request processing end condition of the first client is satisfied, if the second client initiates the same request, the request of the first client can be intercepted, the diagnostic task is turned into the second client service, and the processed information is reported. Give the second client;
  • Coexisting message Before the end condition is met, if the second client initiates the same request, the second client and the first client have the same status, and the data of the managed object is simultaneously reported to the two network management clients.
  • multi-client processing can be defined as: MSG_MUTEX, MSG_OVERRIDE, and MSG_COEXIST.
  • message attribute definitions can be obtained in the following ways:
  • the diagnostic request task definition can be:
  • mapMsg2Task mapsMsg2Task to mapMsg2Task.
  • the implementation manner of the diagnostic test message processing method provided by the embodiment of the present invention may include: by using a message type (one for one answer, one for multiple answer, monitoring) and a mutually exclusive type (mutually exclusive)
  • the main principle of message processing is: the network management server receives the first network management client of at least two network management clients.
  • the second network management client After the first diagnosis request message sent by the terminal to perform diagnostic test on any of the to-be-diagnosed boards, it is detected that the second network management client has sent the second diagnosis request message that is the same as the first diagnosis request message, so that according to the second The mutually exclusive attributes of the diagnostic request message and the first diagnostic request message process the first diagnostic request message.
  • the method for detecting whether the second diagnosis request message sent by the second network management client is the same as the first diagnosis request message may include: detecting whether the message identifier of the first diagnosis request message and the second diagnosis request message are the same as the receiving object. If all are the same, it is determined that the first diagnosis request message and the second diagnosis request message are the same.
  • the method provided in this embodiment further includes:
  • the pipe server rejects the first diagnosis request message of the first network management client when determining that the mutual exclusion attribute registered by the second diagnosis request message is a mutually exclusive type; wherein the mutual exclusion type is that the end condition of the target diagnosis request message is satisfied before Waiting for or processing the target diagnostic request message, rejecting the same diagnostic request message sent by other clients as the target diagnostic request message.
  • FIG. 4 is a schematic diagram of an interaction process of an application processing in a method for processing a diagnostic test message according to an embodiment of the present invention.
  • the method provided in this embodiment may include the following steps, that is, step 301 ⁇ Step 313:
  • Step 301 The client 1 sends a diagnostic test request message (Msg_req_1 message) to the network management server for the diagnostic test process.
  • Msg_req_1 message a diagnostic test request message
  • Step 302 After receiving the Msg_req_1 message, the network test server's diagnostic test process checks whether other clients have initiated the same request message. At this time, if no identical request message is detected, the corresponding request processing interface (beforeDeal) is invoked. , organize the message content;
  • Step 303 The network management server sends a diagnostic test request message (Msg_req_1 message) to the managed object (NE Object), where the Msg_req_1 message carries the generated task ID; the managed object in this embodiment is the to-be-diagnosed board;
  • Step 304 After the Msg_req_1 message is successfully sent, the network management server adds the task ID to the task list, and stores related information about the board to be processed, the client, and the elapsed time.
  • Step 305 The client 2 sends a diagnostic test request message (Msg_req_1 message) to the diagnostic test process of the network management server.
  • Msg_req_1 message a diagnostic test request message
  • Step 306 After receiving the diagnostic test request message (Msg_Req_1 message) sent by the client 2, the diagnostic test process of the network management server checks whether another client has initiated the same request message. At this time, the client 2 and the client are detected. End 1 sends the same request message;
  • Step 307 The network management server determines that the mutually exclusive attribute of the Msg_req_1 message sent by the client 1 is a mutually exclusive type.
  • Step 308 the network management server rejects the request of the client 2, and therefore returns a rejection message (Msg_req_1_Reject message) to the client 2;
  • Step 309 the managed object sends the Msg_req_1 message to the client 1 for processing;
  • Step 310 The managed object sends a response feedback message (Msg_Req_1_Ack message) to the diagnostic test process of the network management server, where the Msg_Req_1_Ack message carries the task ID;
  • Step 311 after receiving the Msg_Req_1_Ack message, the diagnostic test process of the network management server retrieves the corresponding processing object in the task list according to the task ID, and calls the processing object (backDeal) to process the response message, and obtains the message content returned to the client 1;
  • Step 312 the network management server sends a Msg_Req_1_Ack message to the client 1;
  • step 313 the network management server deletes the task ID in the task list.
  • the request message is similar to the mutual exclusion type is: the mutual exclusion attribute registered by the second diagnosis request message is a steal type, and according to the definition of the stealing message, it can be known that the request initiated later is a steal type, and the device needs to first
  • the service request corresponding to the stealing type request is processed, and the implementation manner in this embodiment may further include:
  • the network management server records the second unique identifier of the second diagnosis request message when determining that the mutually exclusive attribute registered by the second diagnosis request message is a steal type;
  • the network management server deletes the first diagnosis request message, and when receiving the test result corresponding to the second diagnosis request message, sends the test result to the second network management client according to the second unique identifier.
  • Steps 307-313 may be replaced with Steps 320-327:
  • Step 320 The network management server determines that the mutually exclusive attribute of the Msg_req_1 message sent by the client 1 is a steal type.
  • Step 321 The network management server records the first unique identifier corresponding to the Msg_req_1 message sent by the client 1;
  • Step 322 the network management server deletes the Msg_req_1 message sent by the client 2, and therefore returns a rejection message (Msg_req_1_Reject message) to the client 2;
  • Step 323 The managed object sends the Msg_req_1 message to the client 1 for processing;
  • Step 324 the managed object sends a response feedback message (Msg_Req_1_Ack message) to the diagnostic test process of the network management server, where the Msg_Req_1_Ack message carries the task ID;
  • Step 325 After receiving the Msg_Req_1_Ack message, the diagnostic test process in the network management server retrieves the corresponding processing object in the task list according to the task ID, and calls the processing object (backDeal) to process the response message, and obtains the message content returned to the client 1;
  • step 326 the network management server sends an Msg_Req_1_Ack message to the client 1.
  • step 327 the network management server deletes the task ID in the task list.
  • the method provided in this embodiment further includes:
  • the network management server determines that the mutually exclusive attribute of the second diagnosis request message is a coexistence type, the first unique identifier corresponding to the first diagnosis request message and the second unique identifier corresponding to the second diagnosis request message are recorded; the network management server receives the second unique identifier.
  • the test result corresponding to the second diagnosis request message is sent, the test result is sent to the first network management client and the second network management client according to the first unique identifier and the second unique identifier.
  • FIG. 5 is a schematic diagram of an interaction process for processing the same request message in the method for processing a diagnostic test message according to an embodiment of the present invention.
  • the method provided in this embodiment may include the following steps, that is, steps. 401 to step 413:
  • Step 401 The client 1 sends a diagnostic test request message (Msg_req_1 message) to the diagnostic test process of the network management server.
  • Msg_req_1 message a diagnostic test request message
  • Step 402 After receiving the Msg_req_1 message, the network test server's diagnostic test process checks whether other clients have initiated the same request message. At this time, if no identical request message is detected, the corresponding request processing interface (beforeDeal) is invoked. , organize the message content;
  • Step 403 The network management server sends a diagnostic test request message (Msg_req_1 message) to the managed object (NE Object), where the Msg_req_1 message carries the generated task ID; the managed object in this embodiment is the to-be-diagnosed board;
  • Step 404 After the Msg_req_1 message is successfully sent, the network management server adds the task ID to the task list.
  • Step 405 the client 2 sends a diagnostic test request message (Msg_req_1 message) to the network management server. Diagnostic test process;
  • Step 406 After the diagnosis test process of the network management server receives the diagnostic test request message (Msg_Req_1 message), the client 2 checks whether another client has initiated the same request message. At this time, the client 2 and the client are detected. The message ID sent by 1 is the same as the board to be diagnosed;
  • Step 407 The network management server determines that the mutually exclusive attribute of the Msg_req_1 message sent by the client 1 is a coexistence type.
  • Step 408 The network management server adds the information of the client 2 to the client information list saved by the task ID of the client 1.
  • Step 409 the managed object processes the Msg_req_1 message
  • Step 410 The managed object sends a response feedback message (Msg_Req_1_Ack message) to the diagnostic test process of the network management server, where the Msg_Req_1_Ack message carries the task ID.
  • Msg_Req_1_Ack message a response feedback message
  • Step 411 after receiving the Msg_Req_1_Ack message, the diagnostic test process of the network management server retrieves the corresponding processing object in the task list according to the task ID, calls the processing object (backDeal) to process the response message, and obtains the message content returned to the client;
  • the network management server sends the Msg_Req_1_Ack message to all clients (client 1 and client 2) associated with the task ID.
  • step 413 the network management server deletes the task ID in the task list.
  • FIG. 6 is a schematic diagram of an interaction process for processing the same request message in the method for processing a diagnostic test message according to an embodiment of the present invention.
  • the method provided in this embodiment may include the following steps, that is, steps 501 to 516. :
  • Step 501 The client 1 sends a diagnostic test request message (Msg_req_1 message) to the network management server for the diagnostic test process.
  • Msg_req_1 message a diagnostic test request message
  • Step 502 After receiving the Msg_req_1 message, the network management server's diagnostic test process checks whether other clients have initiated the same request message. At this time, if no identical request message is detected, the corresponding request processing interface (beforeDeal) is invoked. , organize the message content;
  • the network management server sends a diagnostic test request message (Msg_req_1 message) to the managed object (NE Object), where the Msg_req_1 message carries the generated task ID;
  • the managed object in this embodiment is the to-be-diagnosed board;
  • Step 504 After the Msg_req_1 message is successfully sent, the network management server adds the task ID to the task list.
  • Step 505 The managed object processes the Msg_req_1 message.
  • Step 506 the managed object sends a response feedback message (Msg_Req_1_Ack message) to the diagnostic test process of the network management server, where the Msg_Req_1_Ack message carries the task ID;
  • Step 507 after receiving the Msg_Req_1_Ack message, the diagnostic test process of the network management server retrieves the corresponding processing object in the task list according to the task ID, and calls the processing object (backDeal) to process the response message, and obtains the message content returned to the client 1;
  • Step 508 the network management server sends a Msg_Req_1_Ack message to the client 1;
  • Step 509 The managed object subsequently sends a Msg_Req_1_Rpt message to the network management server for the diagnostic test process.
  • Step 510 the network management server sends a Msg_Req_1_Rpt message to the client 1;
  • Step 511 The client 2 sends a diagnostic test request message (Msg_Req_1 message) to the diagnostic test process of the network management server.
  • Msg_Req_1 message a diagnostic test request message
  • Step 512 After receiving the diagnostic test request message (Msg_Req_1 message) sent by the client 2, the diagnostic test process of the network management server checks whether another client has initiated the same request message. At this time, the client 2 and the client are detected. End 1 sends the same request message;
  • Step 513 The network management server determines that the mutually exclusive attribute of the Msg_req_1 message sent by the client 1 is a mutually exclusive type.
  • step 514 the network management server rejects the request message of the client 2, and therefore returns a reject message (Msg_req_1_Reject message) to the client 2.
  • Step 515 The managed object subsequently sends a Msg_Req_1_Rpt message to the network management server for the diagnostic test process.
  • step 516 the network management server sends only the Msg_Req_1_Rpt message to the client 1.
  • a request message corresponds to multiple response messages
  • the mutually exclusive attribute of the request message registration is an application scenario of a coexistence type, for example, N in this example.
  • the client sends a request message.
  • the implementation of this embodiment may be as shown in FIG. 7 , which is a schematic diagram of an interaction process for processing the same request message in the diagnostic test message processing method provided by the embodiment of the present invention.
  • the method may include the following steps, that is, steps 601 to 620:
  • Step 601 The client 1 sends a diagnostic test request message (Msg_req_1 message) to the network management server for the diagnostic test process.
  • Msg_req_1 message a diagnostic test request message
  • Step 602 After receiving the Msg_req_1 message, the network test server's diagnostic test process checks whether other clients have initiated the same request message. At this time, if the same request message is not detected, the corresponding request processing interface (beforeDeal) is invoked. , organize the message content;
  • the network management server sends a diagnostic test request message (Msg_req_1 message) to the managed object (NE Object), where the Msg_req_1 message carries the generated task ID;
  • the managed object in this embodiment is the to-be-diagnosed board;
  • Step 604 After the Msg_req_1 message is successfully sent, the network management server adds the task ID to the task list.
  • Step 605 The managed object processes the Msg_req_1 message.
  • Step 606 the managed object sends a response feedback message (Msg_Req_1_Ack message) to the diagnostic test process of the network management server, where the Msg_Req_1_Ack message carries the task ID;
  • Step 607 After receiving the Msg_Req_1_Ack message, the diagnostic test process of the network management server retrieves the corresponding processing object in the task list according to the task ID, and invokes the corresponding processing interface to process the response message, and obtains the message content returned to the client 1;
  • Step 608 the network management server sends a Msg_Req_1_Ack message to the client 1;
  • Step 609 The managed object subsequently sends a Msg_Req_1_Rpt message to the network test server for the diagnostic test process.
  • Step 610 the network management server sends a Msg_Req_1_Rpt message to the client 1;
  • Step 611 the client 2 sends a diagnostic test request message (Msg_Req_1 message) to the network management service. Diagnostic test process;
  • Step 612 After receiving the diagnostic test request message (Msg_Req_1 message) sent by the client 2, the diagnostic test process of the network management server checks whether another client has initiated the same request message. At this time, the client 2 and the client are detected. End 1 sends the same request message;
  • Step 613 The network management server determines that the mutually exclusive attribute of the Msg_req_1 message sent by the client 1 is a coexistence type.
  • Step 614 The network management server sends an Msg_req_1_Ack message to the client 2, indicating that the request is successful.
  • Step 615 the network management server adds the information of the client 2 to the client information list saved by the task ID of the client 1;
  • Step 616 The managed object subsequently sends a Msg_Req_1_Rpt message to the network management server for the diagnostic test process.
  • Step 617 the network management server sends the Msg_Req_1_Rpt message to the client 1 and the client 2 respectively;
  • Step 618 the client N sends a diagnostic test request message (Msg_Req_1 message) to the network management server for the diagnostic test process;
  • Step 619 The network management server determines that the Msg_Req_1 message has exceeded the maximum number of clients allowed to be concurrent.
  • step 620 the network management server rejects the request message of the client N, and therefore sends an Msg_Req_1_Reject message to the client N. And the Msg_Req_1_Rpt message sent by the managed object is not sent to the client N.
  • FIG. 8 is a schematic diagram of an interaction process for processing the same request message in the diagnostic test message processing method provided by the embodiment of the present invention.
  • the method provided in this embodiment may include the following steps. , that is, steps 701 to 726:
  • Step 701 the client 1 sends a start monitoring request message (Msg_Beg_Req_1 message) to the network. Diagnostic test process of the server;
  • Step 702 After receiving the Msg_Beg_Req_1 message, the network test server's diagnostic test process checks whether other clients have initiated the same request message. At this time, if no identical request message is detected, the corresponding request processing interface (beforeDeal) is invoked. , organize the message content;
  • Step 703 The network management server sends an Msg_Beg_Req_1 message to the managed object (NE Object), where the message carries the generated task ID.
  • Step 704 After the Msg_Beg_Req_1 message is successfully sent, the network management server adds the task ID to the task list.
  • Step 705 The managed object processes the Msg_Beg_Req_1 message.
  • Step 706 the managed object sends a Msg_Beg_Req_1_Ack message to the network management server for the diagnostic test process, and the Msg_Beg_Req_1_Ack message carries the task ID, indicating that the monitoring is successful;
  • Step 707 The diagnostic test process of the network management server invokes the interface to process the message, and obtains the message content returned to the client 1;
  • Step 708 the network management server sends Msg_Beg_Req_1_Ack to the client 1;
  • Step 709 The managed object subsequently sends a Msg_Req_1_Rpt message to the network management server for the diagnostic test process.
  • Step 710 the network management server sends a Msg_Req_1_Rpt message to the client 1;
  • Step 711 The client 2 sends a Msg_Beg_Req_1 message to the network management server for the diagnostic test process.
  • Step 712 After receiving the Msg_Beg_Req_1 message sent by the client 2, the diagnostic test process of the network management server checks whether another client has initiated the same request message. At this time, it is detected that the client 2 and the client 1 send the same message. Request message
  • Step 713 The network management server determines that the mutually exclusive attribute of the Msg_Beg_Req_1 message sent by the client 1 is a coexistence type.
  • Step 714 the network management server adds the information of the client 2 to the client list saved by the task ID of the client 1;
  • Step 715 the network management server sends a monitoring success message (Msg_Beg_Req_1_Ack message) to Client 2;
  • Step 716 The managed object subsequently sends a Msg_Req_1_Rpt message to the network test server for the diagnostic test process.
  • Step 717 the network management server sends the Msg_Req_1_Rpt message to the client 1 and the client 2 respectively;
  • Step 718 the client N sends a start monitoring request message (Msg_Beg_Req_1 message) to the network management server diagnostic test process;
  • Step 719 the network management server determines that the number of clients supported by the server has reached a maximum
  • step 720 the network management server does not support the Msg_Beg_Req_1 message of the client N, and sends an Msg_Beg_Req_1_Reject message to the client N.
  • Step 721 the client 2 sends an end monitoring message (Msg_End_Req_1 message) to the network controller server diagnostic test process;
  • Step 722 the network server returns a Msg_End_Req_1_Ack message to the client 2;
  • step 723 the network server deletes the information of the client 2 from the client list of the task ID.
  • Step 724 the client 1 sends an end monitoring message (Msg_End_Req_1 message) to the network controller server diagnostic test process;
  • Step 725 the network server returns a Msg_End_Req_1_Ack message to the client 1;
  • step 726 the network server deletes the information of the client 1 from the client list of the task ID. At this point, all client information in the task ID is deleted, so the task ID node is also deleted.
  • a plurality of diagnostic test request messages are processed by a common state machine, and a one-to-one corresponding unique identifier is generated according to an attribute of each diagnostic request message, thereby making the public state According to the unique identifier, the machine can process multiple diagnostic test requests separately, and feed back the processed result to the client that sends the request message, thereby achieving the effect of processing multiple diagnostic test requests in one state machine.
  • the example solves the phenomenon that the resources occupied by the diagnostic test are high when a large number of boards in the related art need to be simultaneously diagnosed and tested.
  • FIG. 9 is a schematic structural diagram of a diagnostic test message processing apparatus according to an embodiment of the present invention.
  • the apparatus provided in this embodiment may include:
  • the receiving module 901 is configured to: receive, by using at least two network management clients, a diagnostic request message for performing a diagnostic test on multiple to-be-diagnosed boards;
  • the identifier generation module 902 is configured to generate a unique identifier corresponding to each diagnosis request message according to the attribute information of each diagnosis request message received by the receiving module 901;
  • the interaction module 903 is configured to: add the unique identifier generated by the identifier generation module 902 to the corresponding diagnosis request message, and send the diagnosis request message after the unique identifier is sent to the plurality of boards to be tested;
  • the interaction module 903 is further configured to: receive test result information sent by multiple boards to be tested; wherein each test result information carries a unique identifier in the corresponding diagnosis request message;
  • the feedback module 904 is configured to: send each test result information to the corresponding network management client according to the unique identifier in each of the test result information received by the interaction module 903.
  • FIG. 10 is a schematic structural diagram of another diagnostic test message processing apparatus according to an embodiment of the present invention.
  • the diagnostic test message processing apparatus provided in this embodiment may further include:
  • the conflict processing module 905 is configured to: after receiving the first diagnosis request message sent by the first network management client of the at least two network management clients to perform diagnostic test on one of the to-be-diagnosed boards, detecting the second network management client The second diagnostic request message that is the same as the first diagnostic request message has been sent, and the first diagnostic request message is processed according to the mutually exclusive attributes of the second diagnostic request message and the first diagnostic request message.
  • the conflict processing module 905 is configured to: message identification and reception for detecting the first diagnosis request message and the second diagnosis request message. Whether the objects are the same, if they are all the same, it is determined that the first diagnosis request message and the second diagnosis request message are the same.
  • the conflict processing module 905 is configured to: reject the first network administrator when determining that the mutually exclusive attribute of the second diagnostic request message registration is a mutually exclusive type a first diagnostic request message of the client; wherein the mutual exclusion type indicates that the target diagnostic request message is waited for or processed before the end condition of the target diagnostic request message is satisfied, and rejecting the same as the target diagnostic request message sent by other clients Diagnostic request message
  • the conflict processing module 905 is configured to: when determining that the mutually exclusive attribute registered by the second diagnosis request message is a coexistence type, record the first diagnosis request message corresponding to The first unique identifier and the second unique identifier corresponding to the second diagnostic request message; when the test result corresponding to the second diagnostic request message is received, the test result is sent according to the first unique identifier and the second unique identifier A network management client and a second network management client.
  • the conflict processing module 905 is configured to: when determining that the mutually exclusive attribute registered by the second diagnosis request message is a steal type, recording the second diagnosis request message correspondingly The second unique identifier is deleted; the first diagnostic request message is deleted, and the test result corresponding to the second diagnostic request message is received, and the test result is sent to the second network management client according to the second unique identifier.
  • a plurality of diagnostic test request messages are processed by a common state machine, and a one-to-one corresponding unique identifier is generated according to an attribute of each diagnostic request message, thereby
  • the public state machine can separately process multiple diagnostic test requests according to the unique identifier, and feed back the processed result to the client that sends the request message, thereby achieving the effect of processing multiple diagnostic test requests in one state machine.
  • the embodiment of the invention solves the phenomenon that the resources occupied by the diagnostic test are high when a large number of boards in the related art need to be simultaneously diagnosed and tested.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • the device/function module/functional unit in the above embodiment When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the embodiment of the present invention processes a plurality of diagnostic test request messages by using a public state machine, and generates a one-to-one corresponding unique identifier according to the attributes of each diagnostic request message, so that the public state machine can be respectively configured according to the unique identifier.
  • the multiple diagnostic test requests are processed, and the processed result is fed back to the client that sends the request message, thereby achieving the effect of processing multiple diagnostic test requests in one state machine.
  • the embodiment of the present invention solves a large number of singles in the related art. When the board needs to be diagnosed at the same time, the resource occupied by the diagnostic test is high.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)
  • Debugging And Monitoring (AREA)

Abstract

一种诊断测试消息处理方法及装置，该方法包括：网管服务器接收至少两个网管客户端发送的对多个待诊断单板进行诊断测试的诊断请求消息；根据每个诊断请求消息的属性信息，生成与每个诊断请求消息一一对应的唯一标识；将每个唯一标识添加到对应的诊断请求消息中，并将添加唯一标识后的诊断请求消息发送给多个待测单板；接收多个待测单板发送的测试结果信息；根据唯一标识，将每个测试结果信息反馈给对应的网管客户端。

Description

一种诊断测试消息处理方法及装置 技术领域
本申请涉及但不限于电子技术领域。
背景技术
在相关技术中的移动通信网络管理系统中，诊断测试单板时，需要发送单板诊断请求给待诊断单板，然后接收待诊断单板返回的诊断测试结果。
在实际应用中，进行诊断测试时，可能会同时诊断多块单板，因此，在系统中可能同时存在多个诊断任务，某些诊断任务可能耗时很长，或者多个诊断任务之间有依赖关系。
相关技术中诊断单板的实现方式为：在网络管理系统中，收到某个单板的某种诊断请求后，启动针对该单板的该诊断请求的状态机，然后该状态机专门处理该单板的该诊断请求的测试结果。通过上述方式诊断单板，如果需要诊断大量单板，以及对每个单板进行多种诊断时，会因为创建的状态机过多，而造成占用过多的系统资源。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本文提供一种诊断测试消息处理方法及装置，以解决相关技术中的单板诊断方式因为创建的状态机过多，造成占用过多的系统资源的问题。
一种诊断测试消息处理方法，该方法包括：
网管服务器接收至少两个网管客户端发送的对多个待诊断单板进行诊断测试的诊断请求消息；
所述网管服务器根据每个诊断请求消息的属性信息，生成与所述每个诊断请求消息一一对应的唯一标识；
所述网管服务器将每个所述唯一标识添加到对应的诊断请求消息中，并将添加所述唯一标识后的诊断请求消息发送给所述多个待测单板；
所述网管服务器接收所述多个待测单板发送的测试结果信息；其中，每个所述测试结果信息中携带对应的诊断请求消息中的唯一标识；
所述网管服务器根据每个所述测试结果信息中的唯一标识，将每个所述测试结果信息发送给对应的网管客户端。
可选地，所述诊断测试消息处理方法还包括：
所述网管服务器接收到所述至少两个网管客户端中的第一网管客户端发送的对其中一个待诊断单板进行诊断测试的第一诊断请求消息后，检测到第二网管客户端已经发送了与所述第一诊断请求消息相同的第二诊断请求消息，根据所述第二诊断请求消息和所述第一诊断请求消息的互斥属性对所述第一诊断请求消息进行处理。
可选地，所述网管服务器根据所述第二诊断请求消息和所述第一诊断请求消息的互斥属性对所述第一诊断请求消息进行处理，包括：
所述网管服务器在确定出所述第二诊断请求消息注册的互斥属性是互斥类型时，拒绝所述第一网管客户端的所述第一诊断请求消息；其中，所述互斥类型表示在目标诊断请求消息的结束条件满足之前，等待或处理所述目标诊断请求消息，拒绝其他客户端发送的与所述目标诊断请求消息相同的诊断请求消息。
可选地，所述网管服务器根据所述第二诊断请求消息和所述第一诊断请求消息的互斥属性对所述第一诊断请求消息进行处理，包括：
所述网管服务器在确定出所述第二诊断请求消息注册的互斥属性是共存类型时，记录所述第一诊断请求消息对应的第一唯一标识和所述第二诊断请求消息对应的第二唯一标识；
所述网管服务器在接收到与所述第二诊断请求消息对应的测试结果时，根据所述第一唯一标识和所述第二唯一标识将所述测试结果发送给所述第一网管客户端和所述第二网管客户端。
可选地，所述网管服务器根据所述第二诊断请求消息和所述第一诊断请 求消息的互斥属性对所述第一诊断请求消息进行处理，包括：
所述网管服务器在确定出所述第二诊断请求消息注册的互斥属性是抢断类型时，记录所述第二诊断请求消息对应的第二唯一标识；
所述网管服务器删除所述第一诊断请求消息，并在接收到与所述第二诊断请求消息对应的测试结果时，根据所述第二唯一标识将所述测试结果发送给所述第二网管客户端。
可选地，所述网管服务器检测到第二网管客户端已经发送了与所述第一诊断请求消息相同的第二诊断请求消息，包括：
所述网管服务器检测所述第一诊断请求消息和所述第二诊断请求消息的消息标识和接收对象是否相同；如果都相同，则确定所述第一诊断请求消息和所述第二诊断请求消息相同。
一种诊断测试消息处理装置，该装置包括：
接收模块，设置为：接收至少两个网管客户端发送的对多个待诊断单板进行诊断测试的诊断请求消息；
标识生成模块，设置为：根据所述接收模块接收的每个诊断请求消息的属性信息，生成与所述每个诊断请求消息一一对应的唯一标识；
交互模块，设置为：将所述标识生成模块生成的每个所述唯一标识添加到对应的诊断请求消息中，并将添加所述唯一标识后的诊断请求消息发送给所述多个待测单板；
所述交互模块，还设置为：接收所述多个待测单板发送的测试结果信息；其中，每个所述测试结果信息中携带对应的诊断请求消息中的唯一标识；
反馈模块，设置为：根据所述交互模块接收到的每个所述测试结果信息中的唯一标识，将每个所述测试结果信息发送给对应的网管客户端。
可选地，所述诊断测试消息处理装置还包括：
冲突处理模块，设置为：接收到所述至少两个网管客户端中的第一网管客户端发送的对其中一个待诊断单板进行诊断测试的第一诊断请求消息后，检测到第二网管客户端已经发送了与所述第一诊断请求消息相同的第二诊断请求消息，根据所述第二诊断请求消息和所述第一诊断请求消息的互斥属性 对所述第一诊断请求消息进行处理。
可选地，所述冲突处理模块，是设置为：在确定出所述第二诊断请求消息注册的互斥属性是互斥类型时，拒绝所述第一网管客户端的所述第一诊断请求消息；其中，所述互斥类型表示在目标诊断请求消息的结束条件满足之前，等待或处理所述目标诊断请求消息，拒绝其他客户端发送的与所述目标诊断请求消息相同的诊断请求消息。
可选地，所述冲突处理模块，是设置为：在确定出所述第二诊断请求消息注册的互斥属性是共存类型时，记录所述第一诊断请求消息对应的第一唯一标识和所述第二诊断请求消息对应的第二唯一标识；在接收到与所述第二诊断请求消息对应的测试结果时，根据所述第一唯一标识和所述第二唯一标识将所述测试结果发送给所述第一网管客户端和所述第二网管客户端。
可选地，所述冲突处理模块，是设置为：在确定出所述第二诊断请求消息注册的互斥属性是抢断类型时，记录所述第二诊断请求消息对应的第二唯一标识；删除所述第一诊断请求消息，并在接收到与所述第二诊断请求消息对应的测试结果时，根据所述第二唯一标识将所述测试结果发送给所述第二网管客户端。
本发明实施例所提供的诊断测试消息处理方法及装置，通过一个公共状态机对多个诊断测试请求消息进行处理，并且根据每个诊断请求消息的属性生成一一对应的唯一标识，从而使得该公共状态机能够根据该唯一标识将分别对多个诊断测试请求进行处理，并将处理的结果反馈到发送请求消息的客户端，从而达到了一个状态机内处理多个诊断测试请求的效果，本发明实施例解决了相关技术中的大量单板需要同时诊断测试时，诊断测试所占用资源冲高的现象。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1为本发明实施例提供的一种诊断测试消息处理方法的流程示意图；
图2为本发明实施例提供的诊断测试消息处理方法的一种应用场景示意 图；
图3为本发明实施例提供的另一种诊断测试消息处理方法的流程示意图；
图4为本发明实施例提供的诊断测试消息处理方法中一种处理相同请求消息的交互流程示意图；
图5为本发明实施例提供的诊断测试消息处理方法中另一种处理相同请求消息的交互流程示意图；
图6为本发明实施例提供的诊断测试消息处理方法中又一种处理相同请求消息的交互流程示意图；
图7为本发明实施例提供的诊断测试消息处理方法中再一种处理相同请求消息的交互流程示意图；
图8为本发明实施例提供的诊断测试消息处理方法中还一种处理相同请求消息的交互流程示意图；
图9为本发明实施例提供一种诊断测试消息处理装置的结构示意图；
图10为本发明实施例提供的另一种诊断测试消息处理装置的结构示意图。
本发明的实施方式
下文中将结合附图对本发明的实施方式进行详细说明。需要说明的是，在不冲突的情况下，本文中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸根据一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
如图1所示，为本发明实施例提供的一种诊断测试消息处理方法的流程示意图。本实施例提供的方法如下所述：
因为诊断测试的请求和应答上报在移动通信网络管理系统中，表现为数据的处理和显示，这部分处理并不占用资源，而状态机本身则很占用资源，在本实施例中则将所有请求都汇集到一个公共的状态机进行处理。本实施例 提供的方法的实现方式可以包括如下步骤，即步骤101～步骤105：
步骤101，网管服务器接收至少两个网管客户端发送的对多个待诊断单板进行诊断测试的诊断请求消息；
步骤102，网管服务器根据每个诊断请求消息的属性信息，生成与每个诊断请求消息一一对应的唯一标识；
步骤103，网管服务器将每个唯一标识添加到对应的诊断请求消息中，并将添加该唯一标识后的诊断请求消息发送给所述多个待测单板；
步骤104，网管服务器接收多个待测单板发送的测试结果信息；其中，每个测试结果信息中携带对应的诊断请求消息中的唯一标识；
步骤105，网管服务器根据每个测试结果信息中的唯一标识，将每个测试结果信息发送给对应的网管客户端。
可选地，图2为本发明实施例提供的诊断测试消息处理方法的一种应用场景示意图，图3为本发明实施例提供的另一种诊断测试消息处理方法的流程示意图。结合图2中的网络环境装置结构，本发明实施例所提供的诊断测试消息处理方法的实现方式可以包括如下步骤，即步骤201～步骤210：
步骤201，网管客户端发送诊断请求消息(Req_1消息)给网管服务器中的诊断测试模块中的消息处理框架。
步骤202，网管服务器中消息处理框架以Req_1消息为参数，生成到发送给网元中代理(Agent)的Req_2消息的内容；在实际应用中，网管服务器调用应用程序(Application，简称为：APP)接口，获取该Req_1对应的消息类型属性、互斥属性、被管理对象属性等，并生成到发送给网元中代理(Agent)的Req_2的消息内容。
步骤203，网管服务器中的消息处理框架以Req_1消息为参数，调用自身的任务管理器，产生全局唯一的任务ID；其中，该任务ID与Req_1是一一对应关系。
步骤204，网管服务器中的诊断测试模块发送Req_2消息给网元中的代理，该Req_2消息中携带任务ID。
步骤205，网元中的代理收到Req_2消息后，将该任务ID存储在自身的任务管理器中，并将不携带该任务ID的诊断请求消息(Req_3消息)发给被管理对象(NE Object)。
步骤206，被管理对象对单板进行诊断测试工作，并将诊断结果形成Ack_1消息发送给网元中的代理。
步骤207，网元中的代理接收到Ack_1消息后，添加任务ID，形成Ack_2消息，将该Ack_2消息发送给网管服务器中的诊断测试模块中的消息处理框架。
步骤208，网管服务器中的诊断测试模块收到消息后，根据任务ID找到对应APP的处理对象，并调用该处理对象来处理Ack_2消息，形成网管客户端可识别的Ack_3消息内容。
步骤209，网管服务器中的诊断测试模块将Ack_3消息发给对应的网管请求客户端。
步骤210，被管理对象在后续有消息继续上报时，将携带任务ID的消息直接发送给网元中的代理。
在实际的应用环境中，网管服务器和被管理对象可以直接信息交互，所以为了节省检测的消息流程，还可以网管不通过被管理对象所在实体上的代理进程来交互。即诊断请求消息不通过图2网元中的代理对象进行处理，不经过代理对象处理的请求消息和应答消息都需要携带任务ID，便于网管网管服务器中的诊断测试模块根据任务ID对诊断测试结果进行操作。
分析诊断测试中使用的消息交互方式，从不同侧面，有下面几种概念：
消息类型概念(根据消息请求-应答数目区分)：
标准消息：一个请求消息对应一个应答消息，网管服务器发送一条请求消息，被管理对象返回一条应答消息。
多答消息：一个请求消息对应多个应答消息，网管服务器发送一条请求消息，被管理对象返回多条应答消息。多个应答消息中，消息结构可能存在不一致的情况，这个使用者可以通过对消息结构进行相应定义来解决，因此这里不再对消息类型做进一步划分。
监视消息：网管服务器发出监视开始请求消息，被管理对象返回监视开始请求成功消息，然后被管理对象开始上报被监视对象的相关信息，直至网管服务器发出监视停止请求消息，并且被管理对象返回监视请求停止成功应答为止。
在系统中，上述消息的类型(Message Type，可以表示为：MSG TYPE)可以是定义为：MSG_TYPE_NORMAL，MSG_TYPE_REPROT和MSG_TYPE_TASK。
可选地，本发明实施例提供的方法中，还可以实现不同客户端发出相同请求时消息的处理方式，通过相同请求消息是否互斥的原则进行处理，包括以下处理方式：
当前有一个诊断任务在执行时，
互斥消息：在结束条件满足之前，一直等待或处理被管理对象的应答消息，拒绝其他客户端的相同请求。
抢断消息：在第一客户端的请求处理结束条件满足之前，如果第二个客户端发起相同请求，可抢断第一个客户端的请求，诊断任务转而为第二个客户端服务，处理的信息上报给第二个客户端；
共存消息：在结束条件满足之前，如果第二个客户端发起相同请求，则第二个客户端和第一个客户端的地位相同，被管理对象的数据同时上报给这两个网管客户端。
在系统中，多客户端处理方式(MsgMutex)可以定义为：MSG_MUTEX、MSG_OVERRIDE和MSG_COEXIST。
在系统中，消息属性定义可以通过以下方式：
map<DWORD,MsgInfo>mapMsgInfo；//键值为msgNo
Figure PCTCN2016088222-appb-000001
Figure PCTCN2016088222-appb-000002
在系统中，诊断请求任务定义可以为：
map<DWORD,CTaskInfo>mapTaskInfo；//键值为taskNo
Figure PCTCN2016088222-appb-000003
其中，关联消息标识和诊断请求任务：mapMsg2Task：
map<DWORD,map<DWORD,CTaskInfo>>mapMsg2Task
可选地，在系统运行状态，本发明实施例提供的诊断测试消息处理方法的实现方式可以包括：通过对消息类型(一求一答，一求多答，监视)和互斥类型(互斥、抢断、共存)的排列组合方式对请求消息进行处理，有3*3＝9种交互方式，消息处理时的主要的原则为：网管服务器接收到至少两个网管客户端中的第一网管客户端发送的对任一待诊断单板进行诊断测试的第一诊断请求消息后，检测到第二网管客户端已经发送了与该第一诊断请求消息相同的第二诊断请求消息，从而根据第二诊断请求消息和第一诊断请求消息的互斥属性对第一诊断请求消息进行处理。
其中，检测第二网管客户端发送的第二诊断请求消息与所述第一诊断请求消息是否相同的方式可以包括：检测第一诊断请求消息和第二诊断请求消息的消息标识和接收对象是否相同，如果都相同，则确定第一诊断请求消息和第二诊断请求消息相同。
下面结合附图对“根据第二诊断请求消息和第一诊断请求消息的互斥属性对第一诊断请求消息进行处理”的实现方式进行详细描述：
可选地，在本发明实施例的一种应用场景中，本实施例提供的方法还包括：
管服务器在确定出第二诊断请求消息注册的互斥属性是互斥类型时，拒绝第一网管客户端的第一诊断请求消息；其中，该互斥类型是表示目标诊断请求消息的结束条件满足之前，一直等待或处理目标诊断请求消息，拒绝其他客户端发送的与该目标诊断请求消息相同的诊断请求消息。本实施例的实现方式可以如图4所示，为本发明实施例提供的诊断测试消息处理方法中一种应用处理的交互流程示意图，本实施例提供的方法可以包括如下步骤，即步骤301～步骤313：
步骤301，客户端1发送诊断测试请求消息(Msg_req_1消息)给网管服务器的诊断测试进程；
步骤302，网管服务器的诊断测试进程收到Msg_req_1消息后，检查是否有其他客户端已经发起了相同的请求消息，此时，检测到没有相同的请求消息，则调用对应的请求处理接口(beforeDeal)，整理消息内容；
步骤303，网管服务器发送诊断测试请求消息(Msg_req_1消息)给被管理对象(NE Object)，该Msg_req_1消息中携带生成的任务ID；本实施例中的被管理对象即为待诊断单板；
步骤304，网管服务器在Msg_req_1消息发送成功后，将任务ID加入任务列表，同时存储相应的待处理单板、客户端、耗用时间等相关信息；
步骤305，客户端2发送诊断测试请求消息(Msg_req_1消息)给网管服务器的诊断测试进程；
步骤306，网管服务器的诊断测试进程收到客户端2发送的诊断测试请求消息(Msg_Req_1消息)后，检查是否有其他客户端已经发起了相同的请求消息，此时，检测出客户端2与客户端1发出了相同的请求消息；
步骤307，网管服务器确定出客户端1发送的Msg_req_1消息注册的互斥属性是互斥类型；
步骤308，网管服务器拒绝客户端2的请求，因此，返回拒绝消息(Msg_req_1_Reject消息)给客户端2；
步骤309，被管理对象对客户端1发送Msg_req_1消息进行处理；
步骤310，被管理对象发送应答反馈消息(Msg_Req_1_Ack消息)给网管服务器的诊断测试进程，该Msg_Req_1_Ack消息中携带任务ID；
步骤311，网管服务器的诊断测试进程接收到Msg_Req_1_Ack消息后，根据任务ID在任务列表检索到对应的处理对象，调用该处理对象(backDeal)处理应答消息，获取返回给客户端1的消息内容；
步骤312，网管服务器将Msg_Req_1_Ack消息发送给客户端1；
步骤313，网管服务器在任务列表中删除该任务ID。
另外，和上述请求消息为互斥类型相似的的情况是：第二诊断请求消息注册的互斥属性是抢断类型，根据抢断消息的定义可知道当后发起的请求是抢断类型，则设备需要先处理抢断类型请求对应的业务申请，在该实施例中的实施方式还可以包括：
网管服务器在确定出第二诊断请求消息注册的互斥属性是抢断类型时，记录该第二诊断请求消息的第二唯一标识；
网管服务器在删除第一诊断请求消息，并在接收到与第二诊断请求消息对应的测试结果时，根据第二唯一标识将该测试结果发送给第二网管客户端。
可选地，基于图4所示实施例所给出的实现方式的步骤，当请求消息为抢断类型时的实现可以是，步骤307～步骤313可以替换为，步骤320～步骤327：
步骤320，网管服务器确定出客户端1发送的Msg_req_1消息注册的互斥属性是抢断类型；
步骤321，网管服务器记录客户端1发送的Msg_req_1消息对应的第一唯一标识；
步骤322，网管服务器的删除客户端2发送的Msg_req_1消息，因此，返回拒绝消息(Msg_req_1_Reject消息)给客户端2；
步骤323，被管理对象对客户端1发送Msg_req_1消息进行处理；
步骤324，被管理对象发送应答反馈消息(Msg_Req_1_Ack消息)给网管服务器的诊断测试进程，该Msg_Req_1_Ack消息中携带任务ID；
步骤325，网管服务器中的诊断测试进程接收到Msg_Req_1_Ack消息后，根据任务ID在任务列表检索到对应的处理对象，调用该处理对象(backDeal)处理应答消息，获取返回给客户端1的消息内容；
步骤326，网管服务器将Msg_Req_1_Ack消息发送给客户端1。
步骤327，网管服务器在任务列表中将该任务ID删除。
可选地，在本发明实施例的另一种应用场景中，本实施例提供的方法还包括：
网管服务器在确定出第二诊断请求消息注册的互斥属性是共存类型时，记录第一诊断请求消息对应的第一唯一标识和第二诊断请求消息对应的第二唯一标识；网管服务器在接收到与第二诊断请求消息对应的测试结果时，根据第一唯一标识和第二唯一标识将该测试结果发送给第一网管客户端和第二网管客户端。本实施例的实现方式可以如图5所示，为本发明实施例提供的诊断测试消息处理方法中一种处理相同请求消息的交互流程示意图，本实施例提供的方法可以包括如下步骤，即步骤401～步骤413：
步骤401，客户端1发送诊断测试请求消息(Msg_req_1消息)给网管服务器的诊断测试进程；
步骤402，网管服务器的诊断测试进程收到Msg_req_1消息后，检查是否有其他客户端已经发起了相同的请求消息，此时，检测到没有相同的请求消息，则调用对应的请求处理接口(beforeDeal)，整理消息内容；
步骤403，网管服务器发送诊断测试请求消息(Msg_req_1消息)给被管理对象(NE Object)，该Msg_req_1消息中携带生成的任务ID；本实施例中的被管理对象即为待诊断单板；
步骤404，网管服务器在Msg_req_1消息发送成功后，将任务ID加入任务列表；
步骤405，客户端2发诊断测试请求消息(Msg_req_1消息)给网管服务器 的诊断测试进程；
步骤406，网管服务器的诊断测试进程收到客户端2发送诊断测试请求消息(Msg_Req_1消息)后，检查是否有其他客户端已经发起了相同的请求消息，此时，检测出客户端2与客户端1发出的消息标识和待诊断单板都相同；
步骤407，网管服务器确定出客户端1发送的Msg_req_1消息注册的互斥属性是共存类型；
步骤408，网管服务器将客户端2的信息加入客户端1的任务ID所保存的客户端信息列表中。
步骤409，被管理对象对Msg_req_1消息进行处理；
步骤410，被管理对象发送应答反馈消息(Msg_Req_1_Ack消息)给网管服务器的诊断测试进程，该Msg_Req_1_Ack消息中携带任务ID；
步骤411，网管服务器的诊断测试进程接收到Msg_Req_1_Ack消息后，根据任务ID在任务列表检索到对应的处理对象，调用该处理对象(backDeal)处理应答消息，获取返回给客户端的消息内容；
步骤412，网管服务器将Msg_Req_1_Ack消息发送给任务ID所关联的所有客户端(客户端1和客户端2)。
步骤413，网管服务器在任务列表中将删除该任务ID。
可选地，在本发明实施例的又一种应用场景中，例如为一个请求消息对应多个应答消息，并且请求消息注册的互斥属性是互斥类型的应用场景中，本实施例的实现方式可以如图6所示，为本发明实施例提供的诊断测试消息处理方法中又一种处理相同请求消息的交互流程示意图，本实施例提供的方法可以包括如下步骤，即步骤501～步骤516：
步骤501，客户端1发送诊断测试请求消息(Msg_req_1消息)给网管服务器的诊断测试进程；
步骤502，网管服务器的诊断测试进程收到Msg_req_1消息后，检查是否有其他客户端已经发起了相同的请求消息，此时，检测到没有相同的请求消息，则调用对应的请求处理接口(beforeDeal)，整理消息内容；
步骤503，网管服务器发送诊断测试请求消息(Msg_req_1消息)给被管理对象(NE Object)，该Msg_req_1消息中携带生成的任务ID；本实施例中的被管理对象即为待诊断单板；
步骤504，网管服务器在Msg_req_1消息发送成功后，将任务ID加入任务列表；
步骤505，被管理对象对Msg_req_1消息进行处理；
步骤506，被管理对象发送应答反馈消息(Msg_Req_1_Ack消息)给网管服务器的诊断测试进程，该Msg_Req_1_Ack消息中携带任务ID；
步骤507，网管服务器的诊断测试进程接收到Msg_Req_1_Ack消息后，根据任务ID在任务列表检索到对应的处理对象，调用该处理对象(backDeal)处理该应答消息，获取返回给客户端1的消息内容；
步骤508，网管服务器将Msg_Req_1_Ack消息发送给客户端1；
步骤509，被管理对象后续发送Msg_Req_1_Rpt消息给网管服务器的诊断测试进程；
步骤510，网管服务器将Msg_Req_1_Rpt消息发送给客户端1；
步骤511，客户端2发送诊断测试请求消息(Msg_Req_1消息)给网管服务器的诊断测试进程；
步骤512，网管服务器的诊断测试进程收到客户端2发送的诊断测试请求消息(Msg_Req_1消息)后，检查是否有其他客户端已经发起了相同的请求消息，此时，检测出客户端2与客户端1发出了相同的请求消息；
步骤513，网管服务器确定出客户端1发送的Msg_req_1消息注册的互斥属性是互斥类型；
步骤514，网管服务器拒绝客户端2的请求消息，因此，返回拒绝消息(Msg_req_1_Reject消息)给客户端2。
步骤515，被管理对象后续发送Msg_Req_1_Rpt消息给网管服务器的诊断测试进程；
步骤516，网管服务器仅将Msg_Req_1_Rpt消息发送给客户端1。
可选地，在本发明实施例的再一种应用场景中，例如为一个请求消息对应多个应答消息，并且请求消息注册的互斥属性是共存类型的应用场景中，本实例中例如有N个客户端发送了请求消息，本实施例的实现方式可以如图7所示，为本发明实施例提供的诊断测试消息处理方法中再一种处理相同请求消息的交互流程示意图，本实施例提供的方法可以包括如下步骤，即步骤601～步骤620：
步骤601，客户端1发送诊断测试请求消息(Msg_req_1消息)给网管服务器的诊断测试进程；
步骤602，网管服务器的诊断测试进程收到Msg_req_1消息后，检查是否有其他客户端已经发起了相同的请求消息，此时，检测到没有相同的请求消息，则调用对应的请求处理接口(beforeDeal)，整理消息内容；
步骤603，网管服务器发送诊断测试请求消息(Msg_req_1消息)给被管理对象(NE Object)，该Msg_req_1消息中携带生成的任务ID；本实施例中的被管理对象即为待诊断单板；
步骤604，网管服务器在Msg_req_1消息发送成功后，将任务ID加入任务列表；
步骤605，被管理对象对Msg_req_1消息进行处理；
步骤606，被管理对象发送应答反馈消息(Msg_Req_1_Ack消息)给网管服务器的诊断测试进程，该Msg_Req_1_Ack消息中携带任务ID；
步骤607，网管服务器的诊断测试进程接收到Msg_Req_1_Ack消息后，根据任务ID在任务列表检索到对应的处理对象，调用相应处理接口处理该应答消息，获取返回给客户端1的消息内容；
步骤608，网管服务器将Msg_Req_1_Ack消息发送给客户端1；
步骤609，被管理对象后续发送Msg_Req_1_Rpt消息给网管服务器的诊断测试进程；
步骤610，网管服务器将Msg_Req_1_Rpt消息发送给客户端1；
步骤611，客户端2发送诊断测试请求消息(Msg_Req_1消息)给网管服 务器的诊断测试进程；
步骤612，网管服务器的诊断测试进程收到客户端2发送的诊断测试请求消息(Msg_Req_1消息)后，检查是否有其他客户端已经发起了相同的请求消息，此时，检测出客户端2与客户端1发出了相同的请求消息；
步骤613，网管服务器确定出客户端1发送的Msg_req_1消息注册的互斥属性是共存类型；
步骤614，网管服务器向客户端2发送Msg_req_1_Ack消息，表明请求成功；
步骤615，网管服务器将客户端2的信息加入客户端1的任务ID所保存的客户端信息列表中；
步骤616，被管理对象后续发送Msg_Req_1_Rpt消息给网管服务器的诊断测试进程；
步骤617，网管服务器将Msg_Req_1_Rpt消息分别发送给客户端1和客户端2；
步骤618，客户端N发送诊断测试请求消息(Msg_Req_1消息)给网管服务器的诊断测试进程；
步骤619，网管服务器确定出此时Msg_Req_1消息已超过允许并发的最大客户端数目；
步骤620，网管服务器拒绝客户端N的请求消息，因此，发送Msg_Req_1_Reject消息给客户端N。并且被管理对象后续发送的Msg_Req_1_Rpt消息也不发给客户端N。
可选地，在本发明实施例的还一种应用场景中，例如为监视时序，并且请求消息注册的互斥属性是共存类型的应用场景中，本实例中例如有N个客户端发送了请求消息，本实施例的实现方式可以如图8所示，为本发明实施例提供的诊断测试消息处理方法中还一种处理相同请求消息的交互流程示意图，本实施例提供的方法可以包括如下步骤，即步骤701～步骤726：
步骤701，客户端1发送开始监视请求消息(Msg_Beg_Req_1消息)给网 管服务器的诊断测试进程；
步骤702，网管服务器的诊断测试进程收到Msg_Beg_Req_1消息后，检查是否有其他客户端已经发起了相同的请求消息，此时，检测到没有相同的请求消息，则调用对应的请求处理接口(beforeDeal)，整理消息内容；
步骤703，网管服务器发送Msg_Beg_Req_1消息给被管理对象(NE Object)，消息中携带生成的任务ID；
步骤704，网管服务器在Msg_Beg_Req_1消息发送成功后，将任务ID加入任务列表；
步骤705，被管理对象对Msg_Beg_Req_1消息进行处理；
步骤706，被管理对象发送Msg_Beg_Req_1_Ack消息给网管服务器的诊断测试进程，该Msg_Beg_Req_1_Ack消息中携带任务ID，表明开始监视成功；
步骤707，网管服务器的诊断测试进程调用接口处理该消息，获取返回给客户端1的消息内容；
步骤708，网管服务器将Msg_Beg_Req_1_Ack发送给客户端1；
步骤709，被管理对象后续发送Msg_Req_1_Rpt消息给网管服务器的诊断测试进程；
步骤710，网管服务器将Msg_Req_1_Rpt消息发送给客户端1；
步骤711，客户端2发送Msg_Beg_Req_1消息给网管服务器的诊断测试进程；
步骤712，网管服务器的诊断测试进程接收到客户端2发送的Msg_Beg_Req_1消息后，检查是否有其他客户端已经发起了相同的请求消息，此时，检测出客户端2与客户端1发出了相同的请求消息；
步骤713，网管服务器确定出客户端1发送的Msg_Beg_Req_1消息注册的互斥属性是共存类型；
步骤714，网管服务器将客户端2的信息加入客户端1的任务ID所保存的客户端列表中；
步骤715，网管服务器发送监视成功消息(Msg_Beg_Req_1_Ack消息)给 客户端2；
步骤716，被管理对象后续发送Msg_Req_1_Rpt消息给网管服务器的诊断测试进程；
步骤717，网管服务器将Msg_Req_1_Rpt消息分别发送给客户端1和客户端2；
步骤718，客户端N发送开始监视请求消息(Msg_Beg_Req_1消息)给网管服务器的诊断测试进程；
步骤719，网管服务器确定出此时服务器支持的客户端数目已经达到最大限度；
步骤720，网管服务器不支持客户端N的Msg_Beg_Req_1消息，发送Msg_Beg_Req_1_Reject消息给客户端N。
步骤721，客户端2发送结束监视消息(Msg_End_Req_1消息)给网管服务器的诊断测试进程；
步骤722，网络服务器返回Msg_End_Req_1_Ack消息给客户端2；
步骤723，网络服务器从任务ID的客户端列表中删除客户端2的信息。
步骤724，客户端1发送结束监视消息(Msg_End_Req_1消息)给网管服务器的诊断测试进程；
步骤725，网络服务器返回Msg_End_Req_1_Ack消息给客户端1；
步骤726，网络服务器从任务ID的客户端列表中删除客户端1的信息。此时任务ID中的所有客户端信息都被删除，因此任务ID节点也连带被删除。
本发明实施例所提供的诊断测试消息方法中，通过一个公共状态机对多个诊断测试请求消息进行处理，并且根据每个诊断请求消息的属性生成一一对应的唯一标识，从而使得该公共状态机能够根据该唯一标识将分别对多个诊断测试请求进行处理，并将处理的结果反馈到发送请求消息的客户端，从而达到了一个状态机内处理多个诊断测试请求的效果，本发明实施例解决了相关技术中的大量单板需要同时诊断测试时，诊断测试所占用资源冲高的现象。
如图9所示，为本发明实施例提供的一种诊断测试消息处理装置的结构示意图。本实施例提供的该装置可以包括：
接收模块901，设置为：接收至少两个网管客户端发送的对多个待诊断单板进行诊断测试的诊断请求消息；
标识生成模块902，设置为：根据接收模块901接收的每个诊断请求消息的属性信息，生成与每个诊断请求消息一一对应的唯一标识；
交互模块903，设置为：将标识生成模块902生成的唯一标识添加到对应的诊断请求消息中，并将添加该唯一标识后的诊断请求消息发送给多个待测单板；
该交互模块903，还设置为：接收多个待测单板发送的测试结果信息；其中，每个测试结果信息中携带对应的诊断请求消息中的唯一标识；
反馈模块904，设置为：根据交互模块903接收到的每个所述测试结果信息中的唯一标识，将每个测试结果信息发送给对应的网管客户端。
可选地，图10为本发明实施例提供的另一种诊断测试消息处理装置的结构示意图。在图9所示装置的结构基础上，本实施例提供的诊断测试消息处理装置还可以包括：
冲突处理模块905，设置为：接收到至少两个网管客户端中的第一网管客户端发送的对其中一个待诊断单板进行诊断测试的第一诊断请求消息后，检测到第二网管客户端已经发送了与该第一诊断请求消息相同的第二诊断请求消息，根据第二诊断请求消息和第一诊断请求消息的互斥属性对第一诊断请求消息进行处理。
在实际应用中，为了确定第一诊断请求消息是否与第二诊断请求消息相同，该冲突处理模块905，是设置为：用于检测第一诊断请求消息和第二诊断请求消息的消息标识和接收对象是否相同，如果都相同，则确定第一诊断请求消息和第二诊断请求消息相同。
可选地，在本实施例的一种应用场景中，该冲突处理模块905是设置为：在确定出第二诊断请求消息注册的互斥属性是互斥类型时，拒绝第一网管客 户端的第一诊断请求消息；其中，该互斥类型表示在目标诊断请求消息的结束条件满足之前，等待或处理所述目标诊断请求消息，拒绝其他客户端发送的与所述目标诊断请求消息相同的诊断请求消息
可选地，在本实施例的另一种应用场景中，该冲突处理模块905是设置为：在确定出第二诊断请求消息注册的互斥属性是共存类型时，记录第一诊断请求消息对应的第一唯一标识和第二诊断请求消息对应的第二唯一标识；在接收到与第二诊断请求消息对应的测试结果时，根据第一唯一标识和第二唯一标识将该测试结果发送个第一网管客户端和第二网管客户端。
可选地，在本实施例的又一种应用场景中，该冲突处理模块905是设置为：在确定出第二诊断请求消息注册的互斥属性是抢断类型时，记录第二诊断请求消息对应的第二唯一标识；删除第一诊断请求消息，并在接收到与该第二诊断请求消息对应的测试结果，根据第二唯一标识将该测试结果发送给第二网管客户端。
本发明实施例中的上述一个或多个技术方案，实现了如下的技术效果：
本发明实施例所提供的诊断测试消息方法和装置中，通过一个公共状态机对多个诊断测试请求消息进行处理，并且根据每个诊断请求消息的属性生成一一对应的唯一标识，从而使得该公共状态机能够根据该唯一标识将分别对多个诊断测试请求进行处理，并将处理的结果反馈到发送请求消息的客户端，从而达到了一个状态机内处理多个诊断测试请求的效果，本发明实施例解决了相关技术中的大量单板需要同时诊断测试时，诊断测试所占用资源冲高的现象。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中，所述计算机程序在相应的硬件平台上(根据系统、设备、装置、器件等)执行，在执行时，包括方法实施例的步骤之一或其组合。
可选地，上述实施例的全部或部分步骤也可以使用集成电路来实现，这些步骤可以被分别制作成一个个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。
上述实施例中的装置/功能模块/功能单元可以采用通用的计算装置来实现，它们可以集中在单个的计算装置上，也可以分布在多个计算装置所组成的网络上。
上述实施例中的装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器，磁盘或光盘等。
工业实用性
本发明实施例通过一个公共状态机对多个诊断测试请求消息进行处理，并且根据每个诊断请求消息的属性生成一一对应的唯一标识，从而使得该公共状态机能够根据该唯一标识将分别对多个诊断测试请求进行处理，并将处理的结果反馈到发送请求消息的客户端，从而达到了一个状态机内处理多个诊断测试请求的效果，本发明实施例解决了相关技术中的大量单板需要同时诊断测试时，诊断测试所占用资源冲高的现象。

Claims (10)

  1. 一种诊断测试消息处理方法，包括：
    网管服务器接收至少两个网管客户端发送的对多个待诊断单板进行诊断测试的诊断请求消息；
    所述网管服务器根据每个诊断请求消息的属性信息，生成与所述每个诊断请求消息一一对应的唯一标识；
    所述网管服务器将每个所述唯一标识添加到对应的诊断请求消息中，并将添加所述唯一标识后的诊断请求消息发送给所述多个待测单板；
    所述网管服务器接收所述多个待测单板发送的测试结果信息；其中，每个所述测试结果信息中携带对应的诊断请求消息中的唯一标识；
    所述网管服务器根据每个所述测试结果信息中的唯一标识，将每个所述测试结果信息发送给对应的网管客户端。
  2. 根据权利要求1所述的方法，还包括：
    所述网管服务器接收到所述至少两个网管客户端中的第一网管客户端发送的对其中一个待诊断单板进行诊断测试的第一诊断请求消息后，检测到第二网管客户端已经发送了与所述第一诊断请求消息相同的第二诊断请求消息，根据所述第二诊断请求消息和所述第一诊断请求消息的互斥属性对所述第一诊断请求消息进行处理。
  3. 根据权利要求2所述的方法，其中，所述网管服务器根据所述第二诊断请求消息和所述第一诊断请求消息的互斥属性对所述第一诊断请求消息进行处理，包括：
    所述网管服务器在确定出所述第二诊断请求消息注册的互斥属性是互斥类型时，拒绝所述第一网管客户端的所述第一诊断请求消息；其中，所述互斥类型表示在目标诊断请求消息的结束条件满足之前，等待或处理所述目标诊断请求消息，拒绝其他客户端发送的与所述目标诊断请求消息相同的诊断请求消息。
  4. 根据权利要求2所述的方法，其中，所述网管服务器根据所述第二诊断请求消息和所述第一诊断请求消息的互斥属性对所述第一诊断请求消息进 行处理，包括：
    所述网管服务器在确定出所述第二诊断请求消息注册的互斥属性是共存类型时，记录所述第一诊断请求消息对应的第一唯一标识和所述第二诊断请求消息对应的第二唯一标识；
    所述网管服务器在接收到与所述第二诊断请求消息对应的测试结果时，根据所述第一唯一标识和所述第二唯一标识将所述测试结果发送给所述第一网管客户端和所述第二网管客户端。
  5. 根据权利要求2所述的方法，其中，所述网管服务器根据所述第二诊断请求消息和所述第一诊断请求消息的互斥属性对所述第一诊断请求消息进行处理，包括：
    所述网管服务器在确定出所述第二诊断请求消息注册的互斥属性是抢断类型时，记录所述第二诊断请求消息对应的第二唯一标识；
    所述网管服务器删除所述第一诊断请求消息，并在接收到与所述第二诊断请求消息对应的测试结果时，根据所述第二唯一标识将所述测试结果发送给所述第二网管客户端。
  6. 一种诊断测试消息处理装置，包括：
    接收模块，设置为：接收至少两个网管客户端发送的对多个待诊断单板进行诊断测试的诊断请求消息；
    标识生成模块，设置为：根据所述接收模块接收的每个诊断请求消息的属性信息，生成与所述每个诊断请求消息一一对应的唯一标识；
    交互模块，设置为：将所述标识生成模块生成的每个所述唯一标识添加到对应的诊断请求消息中，并将添加所述唯一标识后的诊断请求消息发送给所述多个待测单板；
    所述交互模块，还设置为：接收所述多个待测单板发送的测试结果信息；其中，每个所述测试结果信息中携带对应的诊断请求消息中的唯一标识；
    反馈模块，设置为：根据所述交互模块接收到的每个所述测试结果信息中的唯一标识，将每个所述测试结果信息发送给对应的网管客户端。
  7. 根据权利要求1所述的装置，还包括：
    冲突处理模块，设置为：接收到所述至少两个网管客户端中的第一网管客户端发送的对其中一个待诊断单板进行诊断测试的第一诊断请求消息后，检测到第二网管客户端已经发送了与所述第一诊断请求消息相同的第二诊断请求消息，根据所述第二诊断请求消息和所述第一诊断请求消息的互斥属性对所述第一诊断请求消息进行处理。
  8. 根据权利要求7所述的装置，其中，所述冲突处理模块，是设置为：在确定出所述第二诊断请求消息注册的互斥属性是互斥类型时，拒绝所述第一网管客户端的所述第一诊断请求消息；其中，所述互斥类型表示在目标诊断请求消息的结束条件满足之前，等待或处理所述目标诊断请求消息，拒绝其他客户端发送的与所述目标诊断请求消息相同的诊断请求消息。
  9. 根据权利要求7所述的装置，其中，所述冲突处理模块，是设置为：在确定出所述第二诊断请求消息注册的互斥属性是共存类型时，记录所述第一诊断请求消息对应的第一唯一标识和所述第二诊断请求消息对应的第二唯一标识；在接收到与所述第二诊断请求消息对应的测试结果时，根据所述第一唯一标识和所述第二唯一标识将所述测试结果发送给所述第一网管客户端和所述第二网管客户端。
  10. 根据权利要求7所述的装置，其中，所述冲突处理模块，是设置为：在确定出所述第二诊断请求消息注册的互斥属性是抢断类型时，记录所述第二诊断请求消息对应的第二唯一标识；删除所述第一诊断请求消息，并在接收到与所述第二诊断请求消息对应的测试结果时，根据所述第二唯一标识将所述测试结果发送给所述第二网管客户端。
PCT/CN2016/088222 2015-12-07 2016-07-01 一种诊断测试消息处理方法及装置 WO2017096791A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510890762.8 2015-12-07
CN201510890762.8A CN106850245B (zh) 2015-12-07 2015-12-07 一种诊断测试消息处理方法及装置

Publications (1)

Publication Number Publication Date
WO2017096791A1 true WO2017096791A1 (zh) 2017-06-15

Family

ID=59012634

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/088222 WO2017096791A1 (zh) 2015-12-07 2016-07-01 一种诊断测试消息处理方法及装置

Country Status (2)

Country Link
CN (1) CN106850245B (zh)
WO (1) WO2017096791A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022046246A1 (en) * 2020-08-22 2022-03-03 Arris Enterprises Llc Traffic management architecture

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050060396A1 (en) * 2003-09-16 2005-03-17 Yokogawa Electric Corporation Device diagnosis system
CN102014002A (zh) * 2010-12-13 2011-04-13 中兴通讯股份有限公司 一种多个网元设备的管理方法和系统
CN102104890A (zh) * 2009-12-21 2011-06-22 中兴通讯股份有限公司 一种实现基站诊断的方法及装置
CN103200021A (zh) * 2012-01-04 2013-07-10 中兴通讯股份有限公司 网管系统、客户端、服务端及实现批量配置数据的方法
US20150195182A1 (en) * 2014-01-09 2015-07-09 Citrix Systems, Inc Systems and methods for cloud-based probing and diagnostics

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6868434B1 (en) * 2000-08-07 2005-03-15 Sun Microsystems, Inc. System and method for testing server latencies using multiple concurrent users in a computer system
CN101060437B (zh) * 2007-06-07 2010-12-29 中兴通讯股份有限公司 一种对多个同类网元的并行管理方法及装置
CN103686782A (zh) * 2012-09-19 2014-03-26 中兴通讯股份有限公司 基站诊断系统及基站诊断方法
CN104618919B (zh) * 2015-01-05 2018-02-06 重庆邮电大学 传感器网络传感节点标识符解析一致性测试方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050060396A1 (en) * 2003-09-16 2005-03-17 Yokogawa Electric Corporation Device diagnosis system
CN102104890A (zh) * 2009-12-21 2011-06-22 中兴通讯股份有限公司 一种实现基站诊断的方法及装置
CN102014002A (zh) * 2010-12-13 2011-04-13 中兴通讯股份有限公司 一种多个网元设备的管理方法和系统
CN103200021A (zh) * 2012-01-04 2013-07-10 中兴通讯股份有限公司 网管系统、客户端、服务端及实现批量配置数据的方法
US20150195182A1 (en) * 2014-01-09 2015-07-09 Citrix Systems, Inc Systems and methods for cloud-based probing and diagnostics

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022046246A1 (en) * 2020-08-22 2022-03-03 Arris Enterprises Llc Traffic management architecture
US11705978B2 (en) 2020-08-22 2023-07-18 Arris Enterprises Llc Traffic management architecture
US11996930B2 (en) 2020-08-22 2024-05-28 Arris Enterprises Llc Traffic management architecture

Also Published As

Publication number Publication date
CN106850245B (zh) 2020-12-29
CN106850245A (zh) 2017-06-13

Similar Documents

Publication Publication Date Title
CN111752799A (zh) 一种业务链路跟踪方法、装置、设备及储存介质
CN107800565B (zh) 巡检方法、装置、系统、计算机设备和存储介质
CN108038039B (zh) 记录日志的方法及微服务系统
CN112800129B (zh) 区块状态更新方法、装置、系统和电子设备
CN106776093A (zh) 一种应用程序异常日志处理方法及系统
US9727394B2 (en) Establishing causality order of computer trace records
CN111258627A (zh) 一种接口文档生成方法和装置
CN112052227A (zh) 数据变更日志的处理方法、装置和电子设备
CN113791792B (zh) 应用调用信息的获取方法、设备以及存储介质
WO2017096791A1 (zh) 一种诊断测试消息处理方法及装置
CN111930542A (zh) 数据采集方法、装置、电子设备及计算机可读存储介质
CN108390770B (zh) 一种信息生成方法、装置及服务器
CN111092956A (zh) 资源同步方法、装置、存储介质及设备
CN111274032A (zh) 任务处理系统及方法、存储介质
CN108347462B (zh) 一种传输操作数据的方法及设备
CN115580522A (zh) 一种容器云平台运行状态的监控方法及装置
CN112860770B (zh) 报表生成的方法、装置、电子设备和存储介质
WO2021174730A1 (zh) 网络地址处理方法、计算机设备及存储介质
CN112714161A (zh) 视频接入方法、装置及视频接入系统
WO2016119398A1 (zh) 一种被测设备挂起跑飞故障的检测方法、装置及系统
CN110768855A (zh) 链路化性能测试的方法和装置
EP4354298A1 (en) Correlating session failures with application faults from application upgrades
CN115438287A (zh) 无浏览器模式的图表生成方法、电子设备及可读存储介质
CN112261051B (zh) 一种用户注册方法、装置及系统
CN110912720B (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: 16871995

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

Country of ref document: EP

Kind code of ref document: A1