CN102201994B - Context identification negotiation method, server and client used for OAA - Google Patents
Context identification negotiation method, server and client used for OAA Download PDFInfo
- Publication number
- CN102201994B CN102201994B CN201110146866.XA CN201110146866A CN102201994B CN 102201994 B CN102201994 B CN 102201994B CN 201110146866 A CN201110146866 A CN 201110146866A CN 102201994 B CN102201994 B CN 102201994B
- Authority
- CN
- China
- Prior art keywords
- interface
- server
- client
- attributes
- interface attributes
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 17
- 230000008859 change Effects 0.000 claims abstract description 56
- 230000004044 response Effects 0.000 claims description 18
- 230000002776 aggregation Effects 0.000 claims description 10
- 238000004220 aggregation Methods 0.000 claims description 10
- 230000005540 biological transmission Effects 0.000 claims description 2
- 238000012545 processing Methods 0.000 abstract description 6
- 230000002159 abnormal effect Effects 0.000 abstract 1
- 230000008569 process Effects 0.000 description 7
- 230000005856 abnormality Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- RTZKZFJDLAIYFH-UHFFFAOYSA-N Diethyl ether Chemical compound CCOCC RTZKZFJDLAIYFH-UHFFFAOYSA-N 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 101100194362 Schizosaccharomyces pombe (strain 972 / ATCC 24843) res1 gene Proteins 0.000 description 1
- 101100194363 Schizosaccharomyces pombe (strain 972 / ATCC 24843) res2 gene Proteins 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000002457 bidirectional effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000000052 comparative effect Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000012279 drainage procedure Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000000630 rising effect Effects 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
- 238000011282 treatment Methods 0.000 description 1
Landscapes
- Communication Control (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a context identification negotiation method used for OAA (Open Application Architecture). The method comprises: when the client knows the interface attribute change of a server interface, the client actively initiates a context identification negotiation request to the server; after the context identification negotiation request is received by the server, the server responds to the client about the negotiation result of carrying new context identification. Based on the same invention conception, the invention also discloses a server and a client which are able to help avoid abnormal processing of data flows.
Description
Technical field
The present invention relates to communication technical field, particularly one is used for the Context identifier machinery of consultation of open application architecture (OAA), server and client.
Background technology
Current network world is no longer only the data forwarding capability that traditional router and switch provide to the requirement of the network equipment, more requires that the network equipment supports various application.And any one independently technology manufacturer all services of simultaneously providing required by client are all provided.And a kind of structure-OAA of opening, can allow equipment that numerous different vendor produces together with Integrated Simulation, work as an equipment, be the solution that client provides integration, becomes the rising star of network Development.
Be OAA basic architecture figure see Fig. 1, Fig. 1.As shown in Figure 1, OAA system can be divided into three parts: route switching parts 101, separate traffic parts 102, interface connection component 103.Wherein, route switching parts 101 are main parts of router and switch, and this part has complete router or the function of switch, are also the cores that user management controls; Separate traffic parts 102 to open the main body to third party's cooperative development, is mainly used to the business service function providing various uniqueness; Interface connection component 103 is interface connector of route switching relay part 101 and separate traffic parts 102, by these parts by the equipment connection of Liang Ge different vendor together, to form a unified product.
By application controls retransmission protocol (ACFP) agreement and ACFP server and ACFP client interactive information (ACSEI) agreement, separate traffic parts are as client, initiatively can trigger the request of data to the switching and routing parts as server, inform that switching and routing parts carry out drainage procedure according to certain stream feature; Further, separate traffic parts and switching and routing parts can be consulted and interaction, identify the Different treatments of user according to stream feature.But, the Context identifier (Context ID) of data flow be client when user is configured and server negotiate, as long as two ends connect normal, would not again consult Context ID.If affect the server interface attribute change of Context ID, the change of Context ID can be caused, but now two ends connect normal, and again can not consult Context ID, in data flow process, there will be exception in this case.
Summary of the invention
In view of this, the invention provides a kind of Context identifier machinery of consultation for OAA, server and client, the abnormality processing of data flow can be avoided.
For solving the problems of the technologies described above, technical scheme of the present invention is achieved in that
For a Context identifier machinery of consultation of OAA, the method comprises:
When client knows the interface attributes change of server interface, initiatively initiate Context identifier to server and consult request;
Server carries the negotiation result of new Context identifier after receiving described Context identifier negotiation request to client end response.
For a server of OAA, this server is connected with the client in OAA, and this server comprises: property change notification's unit and negotiate response unit;
Described property change notification's unit, during for detecting that the interface attributes of this equipment interface changes, send the interface attributes change notification message of the interface attributes after the interface index and change comprising server interface to described client, know that to make client the interface attributes of server interface changes and initiates to consult Context identifier request;
Described negotiate response unit, receives the Context identifier negotiation request that described client is initiated, and carries the negotiation result of new Context identifier to described client end response.
For a client of OAA, this client is connected with the server in open application architecture, and this client comprises: memory cell, receiving element and negotiation request unit;
Described memory cell, for the interface index of storage server interface and the interface attributes of correspondence;
Described receiving element, receive interface attributes change notification message or the interface attributes notice message of the transmission of described server, wherein, interface attributes change notification message comprises the interface index of server interface and the interface attributes after changing; Interface attributes notice message comprises interface index and the interface attributes of server interface;
Described negotiation request unit, be connected with described memory cell with described receiving element, if described receiving element receives interface attributes change notification message, the request initiated Context identifier and consult then is sent to described server, or, the interface attributes notice message that described receiving element receives, described negotiation request unit determines that the interface attributes stored in the interface attributes that receives and described memory cell is inconsistent, then upgrade interface attributes corresponding to the interface index that stores in described memory cell and initiate to described server the request that this Context identifier consults.
In sum, when in the present invention, client knows the interface attributes change affecting server interface, initiatively initiate the request of the Context ID consulting corresponding server interface to server, after server receives request, carry the negotiation result of new Context identifier to client end response.The abnormality processing of data flow can be avoided.
Accompanying drawing explanation
Fig. 1 is OAA basic architecture figure;
Fig. 2 is the flow chart of the context of the invention identification negotiations;
Fig. 3 is standard A CSEI protocol massages form;
Fig. 4 is the flow chart that in embodiment one, Context identifier is consulted;
Fig. 5 is the flow chart that in embodiment two, Context identifier is consulted;
Fig. 6 is the server architecture figure for OAA;
Fig. 7 is the client terminal structure figure for OAA.
Embodiment
For making object of the present invention, technical scheme and advantage clearly understand, to develop simultaneously embodiment referring to accompanying drawing, scheme of the present invention is described in further detail.
See the flow chart that Fig. 2, Fig. 2 are the context of the invention identification negotiations.Concrete steps are:
Step 201, when client knows the interface attributes change of server interface, initiatively initiates Context identifier to server and consults request.
Step 202, server carries the negotiation result of new Context identifier after receiving described Context identifier negotiation request to client end response.
In the present invention, client knows that server interface attribute change mainly contains two kinds of modes, and a kind of interface attributes change message being client and receiving that server sends, directly knows; Be the server interface attribute carried in Simple Network Management Protocol (SNMP) message sent by timing acquisition server, compare with the local server interface attribute stored, know whether interface attributes changes.Both of these case is described in detail respectively below by embodiment one and embodiment two.
Embodiment one
Server is by sending protocol massages to client, and the interface attributes of notice client-server interface there occurs change, makes client active request consult Context ID.
Introduce a kind of implementation realizing server interface property change notification message below.
See Fig. 3, the interface attributes change notification message that this server sends can realize by standard A CSEI protocol massages as shown in Figure 3.Wherein, the field that this message protocol head comprises is:
VER accounts for 4, represents this protocol version, is 1 at present, represents version 1.
RES1 accounts for 3, retains, does not temporarily use.
C/S accounts for 1, and 0 expression is the message from ACFP Client, and 1 expression is the message from ACFP Server.
TYPE accounts for 1 byte, represents type of message.
RES2 accounts for a byte, retains, does not temporarily use.
Client ID accounts for a byte, is used for distinguishing ACFP Client, in registration request message and registration reject message, is necessary for 0; Must be the Client ID of ACFP Client in other messages.
LENGTH accounts for 2 byte representation message lengths, comprises this protocol header of VER, RES, C/S, TYPE, LENGTH itself and protocol data.
The present embodiment is newly-increased protocol type in TYPE, for when affecting the server interface attribute change of Context ID, sends message to client.For the ease of expansion, the content of newly-increased protocol type adopts type lengths values (TLV, Type Length Value) structure to be stored in the protocol data of ACSEI protocol massages as shown in Figure 3.
Wherein, Type accounts for 1 byte, and value is 0 ~ 255, the maximum type of interaction can supporting 256 kinds of Server and client.
Length accounts for 1 byte, refers to TLV data length, comprises the whole length of Type, Length and Value.According to ACSEI agreement regulation, span is 3 ~ 66, and namely the length range of Value is 1 ~ 64
The variable-length of Value, according to ACSEI agreement regulation, the longest is 64 bytes.Value is for storing the particular content of newly-increased protocol type.
Citing below describes the present invention in detail and how to carry out Context ID negotiation when the server interface attribute affecting Context ID changes.
In existing handling process, system starts, and Client initiates registration to Server, and after succeeding in registration, server can be that each Client distributes Client ID, connects, enters the session stage of Server and Client; Client, by ACFP agreement, obtains the user interface information of server; User, in the WEB interface of client port, according to the interface message obtained, according to the service needed of self, is divided into interface in different security domains, and performs different drainage strategies and processing policy; When drainage, server needs to transmit current affiliated security domain in a stream, this just needs both sides' joint consultation to go out a Context ID, for identifying the security domain belonging to flow, client is shunted according to ContextID after receiving data flow, and the strategy according to corresponding security domain carries out flow detection and process; Server and client side coordinates, the related service that completing user needs.
See the flow chart that Fig. 4, Fig. 4 are Context identifier negotiation in embodiment one; Concrete steps are:
Step 401, when server interface attribute change, server sends ACSEI protocol massages to client.
In this step, server interface attribute is one of the following or its combination in any: interface adds aggregation group, interface exits aggregation group, interface attributes switching, interface type change etc.The change of these server interface attributes all can affect Context ID and change.Wherein, the attribute that interface attributes switches as server interface switches to three layer interfaces by two layer interfaces, or switches to two layer interfaces by three layer interfaces; Interface type switches as POS switches to ether GE etc.
The form of the message sent as described above, the interface institute that the content of message is: notice client-server interface should with change after interface attributes.
Step 402, when client receives the ACSEI protocol massages that server sends, the corresponding interface to server initiates the request that Context ID consults.
When client receives the message that server sends, resolve this message, obtain the content of this message, know the interface attributes after the server interface that interface attributes changes and change according to the interface index in message content.Client initiates the request of Context ID negotiation to corresponding interface.
Step 403, after server receives the request that client sends, determines new Context ID based on the interface attributes after change, and new Context ID is sent to client by response message.
Step 404, client receives the new Context ID that server is sent, and carries out the process of data flow according to this Context ID.
Step 403 and step 404 are prior art, repeat no more.
Embodiment two
Introduce the interface attributes notice message that the present embodiment sends according to server below, the implementation to the new Context ID of server active negotiation:
See the flow chart that Fig. 5, Fig. 5 are Context identifier negotiation in embodiment two.Concrete steps are:
Step 501, client receives the SNMP message that server is sent, the interface attributes of the server interface that this message carries and the interface index of correspondence.
In this step, client can arrange timing acquisition, and user can arrange according to actual conditions the time obtaining interface attributes.SNMP is used for carrying out network management, and the SNMP message that server issues client can carry interface index and the interface attributes of server interface.
According to the interface index of server interface, step 502, judges that whether the interface attributes obtained is consistent with the interface attributes that corresponding this locality stores, if so, perform step 503; Otherwise, perform step 504.
If when the interface attributes obtained in this step is inconsistent with the local interface attributes stored, upgrade original interface attributes stored, the interface attributes affecting the server of Context ID that namely local storage is up-to-date.
Step 503, process ends.
Continue to perform by existing procedure, do not carry out any operation bidirectional.
Step 504, the corresponding interface of user end to server initiates the request of Context ID negotiation.
User end to server initiate Context ID consult request process and subsequent client all consistent with prior art with the reciprocal process of server, also simply describe in embodiment one, repeat no more here.。
Based on the same inventive concept of same said method, the invention allows for a kind of server for OAA.See the server architecture figure that Fig. 6, Fig. 6 are for OAA.This server is connected with the client in OAA, and this server comprises: property change notification's unit 601 and negotiate response unit 602.
Property change notification's unit 601, be connected with negotiate response unit 602, during for detecting that the interface attributes of this equipment interface changes, send the interface attributes change notification message of the interface attributes after the interface index and change comprising server interface to client, know that to make client the interface attributes of server interface changes and initiates to consult Context identifier request; Wherein, interface attributes change notification message can be the ACSEI protocol massages realized in embodiment one.
Negotiate response unit 602, receives the Context identifier negotiation request that client is initiated, and carries the negotiation result of new Context identifier to client end response.
Property notification unit 603, be connected with negotiate response unit 602, for sending the interface attributes notice message of interface index and the interface attributes comprising server interface to client, search the interface attributes of the server interface that client stores to determine whether the request consulted according to the interface attributes that the interface attributes renewal client received stores and initiation Context identifier to make described client according to the interface index received.Wherein interface attributes notice message can be the SNMP message realized in embodiment two.
In server provided by the invention, those skilled in the art can to set a property the enable of change notification unit 601 and property notification unit 603 according to practical application, as only configured a cell enable in these two unit; Or it is simultaneously enable to configure these two unit.
The invention allows for a kind of client for OAA.See the client terminal structure figure that Fig. 7, Fig. 7 are for OAA.This client is connected with the server in OAA, and this client comprises: memory cell 701, receiving element 702 and negotiation request unit 703;
Memory cell 701, for the interface index of storage server interface and the interface attributes of correspondence.
Receiving element 702, the interface attributes change notification message that reception server sends or interface attributes notice message, wherein, interface attributes change notification message comprises the interface index of server interface and the interface attributes after changing; Interface attributes notice message comprises interface index and the interface attributes of server interface;
Consult request unit 703, be connected with memory cell 702 with receiving element 701.Receiving element 701 receives interface attributes change notification message, the request initiated Context identifier and consult then is sent to described server, or, the interface attributes notice message that receiving element 701 receives, then consult the interface attributes that request unit 703 needs to store in the interface attributes determining further to receive and described memory cell inconsistent, then upgrade the interface attributes corresponding to interface index that stores in described memory cell and and initiate the request of this Context identifier negotiation to described server.
The server interface attribute change affecting Context identifier in the present invention is that interface adds aggregation group, interface exits aggregation group, interface attributes switches or interface type change; Or the combination of these interface attributes change.
In sum, the present invention is changed by the interface attributes of server interface, sends out protocol massages notice client, and client initiatively initiates the request consulting Context identifier after receiving this message; Or the interface attributes of the snmp protocol Receive message server interface that client-server is sent, and compare with the interface attributes that this locality stores, when comparative result is inconsistent, initiatively initiate the request consulting Context identifier.The request of server response customer side, and send new Context identifier to client, client carries out Data Stream Processing according to new Context identifier, avoids the abnormality processing of data flow.
The above, be only preferred embodiment of the present invention, be not intended to limit protection scope of the present invention.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (6)
1. for a Context identifier machinery of consultation of open application architecture OAA, client and server negotiate Context identifier, it is characterized in that, the method comprises:
When client knows the interface attributes change of server interface, initiatively initiate Context identifier to server and consult request;
Server carries the negotiation result of new Context identifier after receiving described Context identifier negotiation request to client end response;
Wherein, described client knows that the method for server interface attribute change is:
The interface attributes change notification message that client reception server sends; This interface attributes change notification message comprises the interface index of server interface and the interface attributes after changing;
Client knows the interface attributes change of server interface according to the described interface attributes change notification message received;
Or described client knows that the method for the interface attributes change of server interface is:
The interface attributes notice message that client reception server sends; This interface attributes notice message comprises interface index and the interface attributes of server interface;
Client searches the interface attributes corresponding with the interface index received on this equipment; If the interface attributes found is inconsistent with the interface attributes received, then knows the interface attributes change of server interface, and upgrade the interface attributes of the server interface that this equipment stores according to the interface attributes received.
2. the method for claim 1, is characterized in that, the interface attributes of server interface is one of the following or combination in any: interface adds aggregation group, interface exits aggregation group, interface attributes switches, interface type change.
3. for a server of open application architecture OAA, it is characterized in that, described server is connected with the client in OAA, and described server comprises: property change notification's unit and negotiate response unit;
Described property change notification's unit, during for detecting that the interface attributes of this equipment interface changes, send the interface attributes change notification message of the interface attributes after the interface index and change comprising server interface to described client, know that to make client the interface attributes of server interface changes and initiates to consult Context identifier request;
Described negotiate response unit, receives the Context identifier negotiation request that described client is initiated, and carries the negotiation result of new Context identifier to described client end response;
Wherein, described server also comprises: property notification unit;
Described property notification unit, be connected with described negotiate response unit, for sending the interface attributes notice message comprising the interface index of server interface and interface attributes to client, the interface attributes of to search the server interface that client stores according to the interface index received to make described client is to determine whether upgrade according to the interface attributes received interface attributes that client stores and initiate the request of Context identifier negotiation.
4. server as claimed in claim 3, it is characterized in that, the interface attributes of described server interface is one of the following or combination in any: interface adds aggregation group, interface exits aggregation group, interface attributes switches, interface type change.
5. for a client of open application architecture OAA, client and server negotiate Context identifier, it is characterized in that, this client connects with the server of OAA, this client comprises: memory cell, receiving element and negotiation request unit;
Described memory cell, for the interface index of storage server interface and the interface attributes of correspondence;
Described receiving element, receive interface attributes change notification message or the interface attributes notice message of the transmission of described server, wherein, interface attributes change notification message comprises the interface index of server interface and the interface attributes after changing; Interface attributes notice message comprises interface index and the interface attributes of server interface;
Described negotiation request unit, be connected with described memory cell with described receiving element, if described receiving element receives interface attributes change notification message, the request initiated Context identifier and consult then is sent to described server, or, if the interface attributes notice message that described receiving element receives, described negotiation request unit determines that the interface attributes stored in the interface attributes that receives and described memory cell is inconsistent, then upgrade interface attributes corresponding to the interface index that stores in described memory cell and initiate to described server the request that this Context identifier consults.
6. client as claimed in claim 5, it is characterized in that, the interface attributes of described server interface is one of the following or combination in any: interface adds aggregation group, interface exits aggregation group, interface attributes switches, interface type change.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110146866.XA CN102201994B (en) | 2011-05-31 | 2011-05-31 | Context identification negotiation method, server and client used for OAA |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110146866.XA CN102201994B (en) | 2011-05-31 | 2011-05-31 | Context identification negotiation method, server and client used for OAA |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102201994A CN102201994A (en) | 2011-09-28 |
| CN102201994B true CN102201994B (en) | 2015-04-01 |
Family
ID=44662395
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110146866.XA Active CN102201994B (en) | 2011-05-31 | 2011-05-31 | Context identification negotiation method, server and client used for OAA |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102201994B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1790982A (en) * | 2005-12-26 | 2006-06-21 | 北京航空航天大学 | Method and system for realizing trust identification based on negotiation communication |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2005114921A2 (en) * | 2004-05-21 | 2005-12-01 | Ronald Scott Visscher | Architectural frameworks, functions and interfaces for relationship management (affirm) |
| CN100527686C (en) * | 2006-12-04 | 2009-08-12 | 华为技术有限公司 | Method and device for restraining virtual local area network interface state change |
-
2011
- 2011-05-31 CN CN201110146866.XA patent/CN102201994B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1790982A (en) * | 2005-12-26 | 2006-06-21 | 北京航空航天大学 | Method and system for realizing trust identification based on negotiation communication |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102201994A (en) | 2011-09-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103339901B (en) | Terminal and intermediate node and communication method of terminal and intermediate node in content-oriented network environment | |
| US9386047B2 (en) | Method, switch, server and system for sending connection establishment request | |
| WO2011087085A1 (en) | Calculator, network connection switching method, and program | |
| US9088499B2 (en) | Routing generation for implementation of fiber channel over ethernet | |
| CN102204209B (en) | Method, system and network device for quality of service (qos) negotiation in cross-medium networks | |
| CN103580894B (en) | Method, equipment and the system of Operations, Administration and Maintenance OAM configurations | |
| US10411911B2 (en) | Network as service service cross-domain orchestration method, orchestration device, and control device | |
| JP2014534782A (en) | Extending the border gateway protocol for hosts to join / leave a virtual private network | |
| US11134009B2 (en) | Packet processing method and apparatus | |
| CN101984605B (en) | Diameter node in routing discovering method and indirectly connected diameter system | |
| EP3203685B1 (en) | Method and apparatus for implementing operations, administration and maintenance function | |
| CN102624745B (en) | Method and device for establishing PCEP session | |
| CN112751763A (en) | Message forwarding method, device, storage medium and system | |
| CN111431787B (en) | Tunnel establishment method and device and computer readable storage medium | |
| WO2018000859A1 (en) | Topology determination method, message response method, controller and switch | |
| EP2928129A1 (en) | Method, network device, and virtual cluster for determining administrative domain | |
| CN105960780B (en) | A kind of cross-layer path establishment method and device | |
| US11929851B2 (en) | Gateway selection method, device, and system | |
| CN104702478A (en) | Virtual route forwarding instance handling method and virtual routing forward instance handling device | |
| CN102201994B (en) | Context identification negotiation method, server and client used for OAA | |
| WO2006007789A1 (en) | A method for realizing terminals management in the network device | |
| CN103905338B (en) | The method and device that a kind of IP backbone merges | |
| JPWO2013141193A1 (en) | COMMUNICATION SYSTEM, CONTROL DEVICE, COMMUNICATION DEVICE, INFORMATION RELAY METHOD, AND PROGRAM | |
| CN102546201A (en) | System and method for achieving management of serial server | |
| WO2018028499A1 (en) | Method and device for configuring ospf area number |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Patentee after: Xinhua three Technology Co., Ltd. Address before: 310053 Hangzhou hi tech Industrial Development Zone, Zhejiang province science and Technology Industrial Park, No. 310 and No. six road, HUAWEI, Hangzhou production base Patentee before: Huasan Communication Technology Co., Ltd. |