CN100395977C - Implementation method for automatically identifying packaging type of subscriber data - Google Patents
Implementation method for automatically identifying packaging type of subscriber data Download PDFInfo
- Publication number
- CN100395977C CN100395977C CNB2005100753401A CN200510075340A CN100395977C CN 100395977 C CN100395977 C CN 100395977C CN B2005100753401 A CNB2005100753401 A CN B2005100753401A CN 200510075340 A CN200510075340 A CN 200510075340A CN 100395977 C CN100395977 C CN 100395977C
- Authority
- CN
- China
- Prior art keywords
- data
- user
- treatment facility
- message
- data message
- 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.)
- Expired - Fee Related
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2212/00—Encapsulation of packets
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The present invention discloses a realizing method for automatically identifying a subscriber data package type. Upstream data processing equipment receives a data message from a subscriber terminal, and the method judges whether the subscriber terminal establishes subscriber connection with the upstream data processing equipment, if true, then the upstream data processing equipment is carried out with package release by a data package format contained in a data package type corresponding the stored subscriber connection, else the upstream data processing equipment determines a data package type corresponding the received data message according to corresponding relation set in advance between the data message and the data package type, and the data message is carried out with the package release by the data package format contained in the data package type; the upstream data processing equipment also establishes and stores the corresponding relation between subscriber connection corresponding to the data message, and the data package type. The present invention greatly reduces the workload of manual operation, and obviously reduces the running cost.
Description
Technical field
The present invention relates to the user data encapsulation technology in the communication network, be specifically related to a kind of implementation method that can determine packaging type of subscriber data automatically.
Background technology
At present, user terminal enters the Internet (Internet) by digital subscriber loop modem (xDSL Modem), Digital Subscriber Loop couple in multiplexer (DSLAM) usually and carries out data interaction with Internet, and concrete data interaction principle as shown in Figure 1.
Among Fig. 1, user terminal 110 links to each other with DSLAM 130 by xDSL Modem 120, and 130 of DSLAM link to each other with Internet 150 by switch 140 usually, can also be connected with switch between xDSL Modem 120 and the DSLAM 130.Be respectively arranged with the data encapsulation type on xDSL Modem 120 and the DSLAM 130, different data encapsulation types has different data encapsulation forms.
Wherein, xDSL Modem 120 can support more than one user to connect, it is provided with and is used for user data is encapsulated and the single data encapsulation type of decapsulation, that is: no matter xDSLModem 120 supports several users to connect, and the data encapsulation form that 120 pairs of user data of flowing through of xDSL Modem encapsulate or applied data encapsulation type is had during decapsulation all is identical.DSLAM 130 can link to each other with more than one described xDSL Modem, is provided with more than one data encapsulation type on it by way of manual operation.At each the xDSL Modem that links to each other, the data encapsulation form that DSLAM 130 applied data encapsulation types are had might be different.
At present, use the ATM agreement to communicate between xDSL Modem 120 and the DSLAM 130 usually, this agreement is supported LLC, LLC/SNAP and these three kinds of data encapsulation types of VC.For normally carrying out of guaranteeing to communicate by letter, the data encapsulation form that the data encapsulation type that xDSL Modem 120 uses is had, the data encapsulation form that is had with data encapsulation type that DSLAM 130 uses at xDSL Modem 120 must be identical, and also can think: the data encapsulation type that xDSL Modem 120 uses is necessary identical at the data encapsulation type that xDSL Modem 120 uses with DSLAM 130.
Such as: the data encapsulation type that the user is provided with on xDSL Modem 120 is the LLC encapsulated type, operating personnel are corresponding relation between the data encapsulation type of LLC and preservation in the sign of setting up xDSL Modem 120 on the DSLAM 130 and value, that is: DSLAM 130 is set to the LLC encapsulated type at the applied data encapsulation type of xDSL Modem120.
Like this, when user terminal 110 when xDSL Modem 120 sends datagram, xDSLModem 120 encapsulates the data message of receiving with the data encapsulation form that the LLC encapsulated type that sets in advance is had, the data message that will finish encapsulation afterwards sends to DSLAM 130.After DSLAM130 receives data message from xDSL Modem 120, search the pairing data encapsulation types value of sign of the xDSL Modem120 of self storage.Afterwards, use the data encapsulation form that the LLC encapsulated type find had the data message of receiving is carried out decapsulation, and the data message that will finish decapsulation sends to Internet 150 by switch 140.
Equally, when DSLAM 130 receives data message from Internet 150, read the sign of the xDSL Modem 120 that comprises in this message, and search self storage this identify pairing data encapsulation types value.Afterwards, use the data encapsulation form that the LLC encapsulated type find had the data message of receiving is encapsulated, and the data message that will finish encapsulation sends to xDSL Modem120.XDSL Modem 120 carries out decapsulation with the data message of receiving with the data encapsulation form that the LLC encapsulated type that sets in advance is had, and the data message that will finish decapsulation afterwards sends to user terminal 110.
By the above as can be known, the common at present mode by artificial setting makes DSLAM 130 at xDSL Modem 120 applied data encapsulation types, and is identical with xDSL Modem 120 applied data encapsulation types.But because the number of the xDSL Modem that links to each other with DSLAM 130 is usually in thousand, ten thousand, so operating personnel need carry out a large amount of human configuration operations on DSLAM 130, to guarantee DSLAM 130, identical with the applied data encapsulation type of corresponding xDSL Modem at the applied data encapsulation type of each xDSL Modem.As seen, the workload of this human configuration operation is excessive, has expended great amount of manpower, financial resources, has obviously increased operation cost.
In addition, if, make the data encapsulation type of xDSL Modem that variation take place, can't know this variation with the DSLAM 130 that this xDSL Modem links to each other because of the user has changed xDSL Modem or the configuration of xDSL Modem is revised.Therefore, DSLAM 130 still uses the data encapsulation form that the original data encapsulation type that is provided with had and carries out encapsulation, the decapsulation operation of data message at this xDSL Modem, this will make DSLAM 130 at the applied data encapsulation type of this xDSL Modem, with the applied data encapsulation Type-Inconsistencies of this xDSL Modem, cause DSLAM 130 and this xDSL Modem can't normally carry out data interaction, the user terminal communication that final influence links to each other with this xDSLModem, and reduced user satisfaction.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of implementation method that can determine packaging type of subscriber data automatically, to reduce manually-operated workload, cuts operating costs.
For achieving the above object, technical scheme of the present invention is achieved in that
The invention discloses a kind of implementation method that can determine packaging type of subscriber data automatically, this method comprises:
A. the upstream data treatment facility receives the data message from user terminal, judges according to this data message whether this user terminal establishes the user with this upstream data treatment facility and be connected, if then enter step b; Otherwise, enter step c;
B. the described user of upstream data treatment facility application memory connects the data encapsulation form that pairing data encapsulation type has, to described data message decapsulation, and process ends;
C. the upstream data treatment facility is according to data message that sets in advance and the corresponding relation between the data encapsulation type, the described data message that determine to receive should corresponding data encapsulation type, and uses data encapsulation form that this data encapsulation type had to described data message decapsulation; This upstream data treatment facility is also set up corresponding relation and is preserved between pairing user's connection of this data message and described data encapsulation type.
The method of described judgement is:
The upstream data treatment facility is in all user's connection identifier of preserving, search with the data message of receiving in the identical user's connection identifier of user's connection identifier that comprises, if find this user's connection identifier, the upstream data treatment facility determines that then establishing the user with described user terminal is connected; Otherwise the upstream data treatment facility determines that then not setting up the user with described user terminal is connected;
Step b comprises: the upstream data treatment facility is searched the pairing data encapsulation types value of described user's connection identifier of storage, and the data encapsulation form that is had with the corresponding data encapsulation type of this value carries out decapsulation to described data message.
Among the step a, the method for described judgement is:
The upstream data treatment facility is in all user's connection identifier of preserving, search with the data message of receiving in the identical user's connection identifier of user's connection identifier that comprises, and with the data encapsulation types value of the corresponding preservation of this user's connection identifier, if find this user's connection identifier and corresponding data encapsulation types value thereof, the upstream data treatment facility determines that then establishing the user with described user terminal is connected; Otherwise the upstream data treatment facility determines that then not setting up the user with described user terminal is connected;
Step b comprises: the data encapsulation form that the data encapsulation type of the data encapsulation types value correspondence that the application of upstream data treatment facility finds is had carries out decapsulation to described data message.
Among step b and the step c, after the upstream data treatment facility was finished described decapsulation, the data message that further will finish decapsulation sent to internet Internet, or the data message of finishing decapsulation was carried out this locality handle.
Among the step c, determine that the method for described data encapsulation type is:
The upstream data treatment facility reads the header of the described data message of receiving, header that sets in advance according to communication protocol and the corresponding relation between the data encapsulation type, the pairing data encapsulation type of header of the described data message received is defined as this data message should corresponding data encapsulation type.
Among the step c, the method for setting up described corresponding relation and preservation is:
Set up corresponding relation between the value of user's connection identifier that the upstream data treatment facility comprises and the described data encapsulation type determined and preserve in described data message.
This method further comprises:
The upstream data treatment facility reads the user's connection identifier that comprises in the data message that will send to user terminal, search the data encapsulation types value corresponding of storage, and the data encapsulation form that is had with the corresponding data encapsulation type of this value encapsulates to described data message with this user's connection identifier.
After the upstream data treatment facility was finished described encapsulation, the data message that further will finish encapsulation sent to described user terminal.
This method further comprises:
User terminal upstream data processing equipment sends user's connection release message, after the upstream data treatment facility is received this message, read the user's connection identifier that comprises in this message, and the value of the data encapsulation type of this user's connection identifier of deletion storage and correspondence thereof.
Described upstream data treatment facility is the Digital Subscriber Loop couple in multiplexer DSLAM that links to each other with described user terminal, or is connected in the switch between DSLAM and the Internet, or is connected in the switch between DSLAM and the described user terminal.
Described user's connection identifier is the user terminal network address, or the user conversation sign.
Compared with prior art, provided by the present inventionly can determine automatically in the implementation method of packaging type of subscriber data, the upstream data treatment facility can be according to the corresponding relation between data message that sets in advance and the data encapsulation type, the data message that determine to receive should corresponding data encapsulation type, and uses data encapsulation form that this data encapsulation type had to described data message decapsulation; This upstream data treatment facility also the pairing user of this data message connect with described data encapsulation type between set up corresponding relation and preserve, connect the data encapsulation form that the described data encapsulation type that can use correspondence had at this user and carry out data encapsulation, decapsulation to guarantee that the upstream data treatment facility is follow-up; This makes the data encapsulation type of upstream data treatment facility to dispose by way of manual operation again, makes manually-operated workload significantly reduce, and has obviously reduced operation cost.
Description of drawings
Fig. 1 is the data interaction schematic diagram of user terminal and Internet;
Fig. 2 is the DSLAM processes user data flow chart of a preferred embodiment of the present invention;
Fig. 3 is the DSLAM processes user data flow chart of another preferred embodiment of the present invention.
Embodiment
Below in conjunction with drawings and the specific embodiments to the detailed description of the invention.
The implementation method that can determine packaging type of subscriber data automatically of the present invention, by the data message of upstream data treatment facility reception from user terminal, judge according to this data message whether this user terminal establishes the user with this upstream data treatment facility and be connected, if, the upstream data treatment facility then described user of application memory connects the data encapsulation form that pairing data encapsulation type has, to described data message decapsulation; Otherwise, the upstream data treatment facility is then according to data message that sets in advance and the corresponding relation between the data encapsulation type, the described data message that determine to receive should corresponding data encapsulation type, and uses data encapsulation form that this data encapsulation type had to described data message decapsulation; This upstream data treatment facility is also set up corresponding relation and is preserved between pairing user's connection of this data message and described data encapsulation type.
Referring to Fig. 2, Fig. 2 is the DSLAM processes user data flow chart of a preferred embodiment of the present invention, and this flow process may further comprise the steps:
Step 201:DSLAM receives the data message from xDSL Modem constantly.
Step 202: receive after the data message from xDSL Modem, DSLAM reads the user's connection identifier in this data message, and judge the current pairing user's connection of this user's connection identifier that whether establishes, and connect if do not set up described user, then enter step 203; Connect if establish described user, then enter step 206.
Concrete determination methods is: DSLAM is in all user's connection identifier of self preserving, search with the data message of receiving in the identical user's connection identifier of user's connection identifier that comprises, if find this user's connection identifier, DSLAM then determines the current pairing user's connection of this user's connection identifier that establishes; Otherwise DSLAM then determines the current pairing user's connection of this user's connection identifier of not setting up.
In actual applications, described determination methods can also be: DSLAM is in all user's connection identifier of self preserving, search with the data message of receiving in the identical user's connection identifier of user's connection identifier that comprises, and with this sign corresponding preservation the data encapsulation types value, if find this user's connection identifier and corresponding data encapsulation types value, DSLAM then determines the current pairing user's connection of this user's connection identifier that establishes; Otherwise DSLAM then determines the current pairing user's connection of this user's connection identifier of not setting up.
Step 203:DSLAM reads the header of the described data message of receiving, and header that sets in advance according to the ATM agreement and the corresponding relation between the data encapsulation type, determines that the described data message of receiving should corresponding data encapsulation type.Such as present ATM agreement regulation, when the byte that comprises when the header of data message is followed successively by 0xFE, 0xFE and 0x03, this data message is used the LLC encapsulated type; When the byte that comprises when the header of data message is followed successively by 0xAA, 0xAA and 0x03, this data message is used the LLC/SNAP encapsulated type; The byte that comprises when the header of data message is followed successively by 0x00,0x00, or is followed successively by 0x00,0x00,0x00, or when being followed successively by 0x00,0x00,0xXX, this data message is used the VC encapsulated type.
Like this, if DSLAM by reading the header of the described data message of receiving, knows when byte that this header comprises is followed successively by 0xFE, 0xFE and 0x03 that DSLAM just can determine this data message is used the LLC encapsulated type.
Step 204:DSLAM carries out decapsulation according to the data encapsulation form that the described data encapsulation type of having determined has to the described data message of receiving, also the user's connection identifier that comprises in this data message and the value of the described data encapsulation type of having determined are set up corresponding relation, and the user's connection identifier that will set up corresponding relation is preserved with the data encapsulation types value.DSLAM is kept at described user's connection identifier in the data storage device of self with the data encapsulation types value usually, DSLAM also can be kept in the third party device, as long as can obtain this user's connection identifier and corresponding data encapsulation types value.
Step 205:DSLAM carries out subsequent treatment to the data message of finishing decapsulation, and process ends.The mode that DSLAM carries out subsequent treatment to described data message has multiple, as: data message is transmitted to Internet by switch, or the data message carried out that this locality is handled etc.
Step 206: at the described user's connection identifier that finds, DSLAM further searches the pairing data encapsulation types value of this user's connection identifier of storage, and the data encapsulation form that is had with the corresponding data encapsulation type of this value carries out decapsulation to the described data message of receiving.Certainly, if DSLAM has found the pairing data encapsulation types value of this user's connection identifier in step 202, the data encapsulation form that DSLAM is then directly had with the corresponding data encapsulation type of this value carries out decapsulation to described data message.
Step 207:DSLAM transmits the data message of finishing decapsulation or subsequent treatment such as local processing.
Why to carry out described decision operation in the step 202, be because the data message that DSLAM receives, might be that user terminal connects the data message that sends to DSLAM first based on newly-built user, also might be that user terminal connects the follow-up data message that sends to DSLAM based on this user.Therefore, if DSLAM receive to be user terminal connect the data message that sends first based on newly-built user, the operation during DSLAM then will carry out step 203 is to determine corresponding which kind of the data encapsulation type of this data message according to the data message header of receiving; If what DSLAM received is user terminal connects follow-up transmission based on described user data message, because at this moment DSLAM has preserved the corresponding relation between this user's connection and the data encapsulation type, therefore can carry out step 206, the data encapsulation form that is had with the corresponding data encapsulated type of preserving carries out decapsulation to described data message.
By the above as can be known, DSLAM can determine the data encapsulation type that will use from the data message of user terminal automatically, and use the data encapsulation form that this data encapsulation type had this data message is carried out decapsulation, make manually-operated workload significantly reduce, and obviously reduced operation cost.
The definite data encapsulation type that will use from the data message of user terminal of the DSLAM of being described above, and corresponding data encapsulation operation.Operating principle is identical therewith, when DSLAM receives the data message that will send to user terminal from Internet, or DSLAM self generates in the time of will sending to the data message of this user terminal, DSLAM then will use the data encapsulation type that the definite data message that will send to this user terminal of flow process shown in Figure 3 will be used, and corresponding data encapsulation operation.
Referring to Fig. 3, Fig. 3 is the DSLAM processes user data flow chart of another preferred embodiment of the present invention, and this flow process may further comprise the steps:
Step 301:DSLAM receives the data message from Internet constantly.
Step 302: when DSLAM receives data message from Internet, can determine that user under this data message connects and set up, and DSLAM the sign that this user is connected of the correlation method described in the application drawing 2 and the value of data encapsulation type have been set up corresponding relation.
Thereby DSLAM can read the user's connection identifier that comprises in this data message when receiving described data message, and search storage this identify pairing data encapsulation types value.Afterwards, DSLAM determines that the pairing data encapsulation type of the data encapsulation types value that finds is the data encapsulation type that described data message will be used.
Step 303:DSLAM encapsulates described data message according to the data encapsulation form that the data encapsulation type that finds is had.
The data message that step 304:DSLAM will finish encapsulation sends to xDSL Modem, the data encapsulation form that the data encapsulation type that is set in advance according to self by xDSLModem is had carries out decapsulation to the data message of receiving, and the data message that will finish decapsulation sends to described user terminal.
Certainly, in step 301, DSLAM also can generate the data message that will send to described user terminal by self according to user's request.In step 302, DSLAM just reads the user's connection identifier that comprises in this data message so, and search storage this identify pairing data encapsulation types value.Afterwards, DSLAM determines that the pairing data encapsulation type of the data encapsulation types value that finds is the data encapsulation type that described data message will be used.
In Fig. 2 and flow process shown in Figure 3, when described user terminal disconnected network and connects, this user terminal sent user's connection release message to DSLAM.After DSLAM receives user's connection release message, read the user's connection identifier that comprises in this message, and this user's connection identifier of deletion storage and corresponding data encapsulation types value.
By the above as can be known, DSLAM can determine the data encapsulation type that will use from the data message of Internet automatically, and use the data encapsulation form that this data encapsulation type had this data message is carried out decapsulation, make manually-operated workload significantly reduce, and obviously reduced operation cost.
By the above as can be known, in communication process, the operation of the data encapsulation type that automatic specified data message will be used is all finished by DSLAM usually.But in actual applications, also can finish described operation, or finish described operation by the upstream data treatment facilities such as switch that are connected between xDSL Modem and the DSLAM by the upstream data treatment facilities such as switch that are connected between Internet and the DSLAM.In this case, the unique variation in Fig. 2, the flow process shown in Figure 3 is that variation has taken place operating main body, that is: the corresponding operating that carries out of former cause DSLAM changes into by described switch and being undertaken.Above-mentioned upstream data treatment facility is at communication equipments such as described user terminal, the described DSLAM that is in this user terminal upstream position or described switches.
Have, described user's connection identifier can be that user terminal network address, user conversation sign etc. are any again.
The above-described implementation method that can determine packaging type of subscriber data had automatically both gone for the ATM agreement, also went for the communication protocol of other type.
By the above as can be seen, the implementation method that can determine packaging type of subscriber data automatically provided by the present invention, need not dispose the data encapsulation type on the upstream data treatment facilities such as DSLAM or described switch more by way of manual operation, make manually-operated workload significantly reduce, and obviously reduced operation cost.
Claims (11)
1. the implementation method that can determine packaging type of subscriber data automatically is characterized in that this method comprises:
A. the upstream data treatment facility receives the data message from user terminal, judges according to this data message whether this user terminal establishes the user with this upstream data treatment facility and be connected, if then enter step b; Otherwise, enter step c;
B. the described user of upstream data treatment facility application memory connects the data encapsulation form that pairing data encapsulation type has, to described data message decapsulation, and process ends;
C. the upstream data treatment facility is according to data message that sets in advance and the corresponding relation between the data encapsulation type, the described data message that determine to receive should corresponding data encapsulation type, and uses data encapsulation form that this data encapsulation type had to described data message decapsulation; This upstream data treatment facility is also set up corresponding relation and is preserved between pairing user's connection of this data message and described data encapsulation type.
2. the method for claim 1 is characterized in that, among the step a, the method for described judgement is:
The upstream data treatment facility is in all user's connection identifier of preserving, search with the data message of receiving in the identical user's connection identifier of user's connection identifier that comprises, if find this user's connection identifier, the upstream data treatment facility determines that then establishing the user with described user terminal is connected; Otherwise the upstream data treatment facility determines that then not setting up the user with described user terminal is connected;
Step b comprises: the upstream data treatment facility is searched the pairing data encapsulation types value of described user's connection identifier of storage, and the data encapsulation form that is had with the corresponding data encapsulation type of this value carries out decapsulation to described data message.
3. the method for claim 1 is characterized in that, among the step a, the method for described judgement is:
The upstream data treatment facility is in all user's connection identifier of preserving, search with the data message of receiving in the identical user's connection identifier of user's connection identifier that comprises, and with the data encapsulation types value of the corresponding preservation of this user's connection identifier, if find this user's connection identifier and corresponding data encapsulation types value thereof, the upstream data treatment facility determines that then establishing the user with described user terminal is connected; Otherwise the upstream data treatment facility determines that then not setting up the user with described user terminal is connected;
Step b comprises: the data encapsulation form that the data encapsulation type of the data encapsulation types value correspondence that the application of upstream data treatment facility finds is had carries out decapsulation to described data message.
4. the method for claim 1, it is characterized in that, among step b and the step c, after the upstream data treatment facility is finished described decapsulation, the data message that further will finish decapsulation sends to internet Internet, or the data message of finishing decapsulation is carried out this locality handle.
5. the method for claim 1 is characterized in that, among the step c, determines that the method for described data encapsulation type is:
The upstream data treatment facility reads the header of the described data message of receiving, header that sets in advance according to communication protocol and the corresponding relation between the data encapsulation type, the pairing data encapsulation type of header of the described data message received is defined as this data message should corresponding data encapsulation type.
6. the method for claim 1 is characterized in that, among the step c, the method for setting up described corresponding relation and preservation is:
Set up corresponding relation between user's connection identifier that the upstream data treatment facility comprises and the described data encapsulation types value determined and preserve in described data message.
7. the method for claim 1 is characterized in that, this method further comprises:
The upstream data treatment facility reads the user's connection identifier that comprises in the data message that will send to user terminal, search the data encapsulation types value corresponding of storage, and the data encapsulation form that is had with the corresponding data encapsulation type of this value encapsulates to described data message with this user's connection identifier.
8. method as claimed in claim 7 is characterized in that, after the upstream data treatment facility was finished described encapsulation, the data message that further will finish encapsulation sent to described user terminal.
9. the method for claim 1 is characterized in that, this method further comprises:
User terminal upstream data processing equipment sends user's connection release message, after the upstream data treatment facility is received this message, reads the user's connection identifier that comprises in this message, and this user's connection identifier of deletion storage and corresponding data encapsulation types value thereof.
10. the method for claim 1, it is characterized in that, described upstream data treatment facility is the Digital Subscriber Loop couple in multiplexer DSLAM that links to each other with described user terminal, or be connected in switch between DSLAM and the Internet, or be connected in the switch between DSLAM and the described user terminal.
11., it is characterized in that described user's connection identifier is the user terminal network address as claim 2,3,6,7 or 9 described methods, or user conversation sign.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100753401A CN100395977C (en) | 2005-06-10 | 2005-06-10 | Implementation method for automatically identifying packaging type of subscriber data |
| PCT/CN2006/001217 WO2006131063A1 (en) | 2005-06-10 | 2006-06-05 | A method for determining the subscriber data encapsulation type automatically and an upstream data processing device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100753401A CN100395977C (en) | 2005-06-10 | 2005-06-10 | Implementation method for automatically identifying packaging type of subscriber data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1878064A CN1878064A (en) | 2006-12-13 |
| CN100395977C true CN100395977C (en) | 2008-06-18 |
Family
ID=37498126
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005100753401A Expired - Fee Related CN100395977C (en) | 2005-06-10 | 2005-06-10 | Implementation method for automatically identifying packaging type of subscriber data |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN100395977C (en) |
| WO (1) | WO2006131063A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105162673A (en) * | 2015-08-24 | 2015-12-16 | 北京大众益康科技有限公司 | Data transmission interface and method |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6445715B1 (en) * | 1998-08-27 | 2002-09-03 | Cisco Technology, Inc. | Dynamic trunk protocol |
| US20030210697A1 (en) * | 2000-09-29 | 2003-11-13 | Mathieu Mercier | Auto encapsulation detection |
| CN1479489A (en) * | 2002-08-29 | 2004-03-03 | ����ͨѶ�ɷ�����˾ | Method of transmitting broadband multimedia data on comprehensive business digital network |
| CN1509023A (en) * | 2002-12-17 | 2004-06-30 | 深圳市中兴通讯股份有限公司上海第二 | Asynchronous transmission mode data dispatching device and method |
| CN1553646A (en) * | 2003-05-27 | 2004-12-08 | 华为技术有限公司 | Method for transmitting Ethernet message by Internet |
| CN1571395A (en) * | 2003-07-17 | 2005-01-26 | 华为技术有限公司 | A method for bearing IP message protocol on ATM network supported by broadband access equipment |
-
2005
- 2005-06-10 CN CNB2005100753401A patent/CN100395977C/en not_active Expired - Fee Related
-
2006
- 2006-06-05 WO PCT/CN2006/001217 patent/WO2006131063A1/en active Application Filing
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6445715B1 (en) * | 1998-08-27 | 2002-09-03 | Cisco Technology, Inc. | Dynamic trunk protocol |
| US20030210697A1 (en) * | 2000-09-29 | 2003-11-13 | Mathieu Mercier | Auto encapsulation detection |
| CN1479489A (en) * | 2002-08-29 | 2004-03-03 | ����ͨѶ�ɷ�����˾ | Method of transmitting broadband multimedia data on comprehensive business digital network |
| CN1509023A (en) * | 2002-12-17 | 2004-06-30 | 深圳市中兴通讯股份有限公司上海第二 | Asynchronous transmission mode data dispatching device and method |
| CN1553646A (en) * | 2003-05-27 | 2004-12-08 | 华为技术有限公司 | Method for transmitting Ethernet message by Internet |
| CN1571395A (en) * | 2003-07-17 | 2005-01-26 | 华为技术有限公司 | A method for bearing IP message protocol on ATM network supported by broadband access equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1878064A (en) | 2006-12-13 |
| WO2006131063A1 (en) | 2006-12-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN116208524B (en) | Method, equipment and system for detecting data message | |
| US9332577B2 (en) | Method and system for implementing smart card remote operation | |
| US8031700B2 (en) | PPP terminating equipment, network equipment and method of responding to LCP echo requirement | |
| EP1335564A3 (en) | Communication system and communication method | |
| CN102907049A (en) | Specifying priority on a virtual station interface discovery and configuration protocol response | |
| GB9913678D0 (en) | A cellular communication terminal a method and a system for fetching content from a server | |
| JP2002510935A (en) | Wireless packet data communication device and method | |
| EP0961516A3 (en) | Plural communication connection setting method | |
| EP1091528A3 (en) | Systems and methods for mapping quality of service across communications systems | |
| CN101136870A (en) | Symbol based message transferring method and system | |
| MY130201A (en) | Communication method in a home network, network and device for implementing such a method | |
| CN107547932A (en) | Sharing method and device, the terminal of data message | |
| RU99106677A (en) | METHOD FOR PROCESSING SERVICES AND MOBILE NETWORK SYSTEM PROTOCOL | |
| CA2299686A1 (en) | System and method for establishing a communication connection | |
| CN100395977C (en) | Implementation method for automatically identifying packaging type of subscriber data | |
| CN101753448A (en) | Method and device for establishing ATM communication connection | |
| EP1111870A3 (en) | Communication method and communication system | |
| CN106685600A (en) | Method for messaging among work stations within local area network | |
| AU2001231612A1 (en) | Telecommunication system and method for transferring information between an intelligent network control unit and a terminal | |
| CN107113230B (en) | Method, equipment and system for determining Generic Routing Encapsulation (GRE) tunnel identifier | |
| CN107465996A (en) | Wireless monitor system | |
| GB2408650B (en) | Network telephone system main apparatus for the same system and connection information update method using the same system | |
| CN114095895B (en) | Communication self-adaptive data acquisition method and device for intelligent perception terminal | |
| JP2008136053A (en) | Remote monitoring control system, monitoring object control device and communication terminal | |
| CN109246244B (en) | Message synchronization detection method, device and system |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20080618 Termination date: 20160610 |