WO2006131063A1

WO2006131063A1 - A method for determining the subscriber data encapsulation type automatically and an upstream data processing device

Info

Publication number: WO2006131063A1
Application number: PCT/CN2006/001217
Authority: WO
Inventors: Jianjun Li; Gang Xu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2005-06-10
Filing date: 2006-06-05
Publication date: 2006-12-14
Also published as: CN100395977C; CN1878064A

Abstract

A method for determining the subscriber data encapsulation type automatically includes: the upstream data processing device receives the data message from the subscriber terminal, and it determines whether the subscriber terminal has established the subscriber connection with the upstream data processing device based on the data message; if so, the upstream data processing device decapsulates the data message with the stored data encapsulation format provided by the data encapsulation type corresponding to the subscriber connection; otherwise, the upstream data processing device determined the data encapsulation type corresponding to the received data message based on the predetermined correspondence relations between the data message and the data encapsulation type, and decapsulates the data message with the data encapsulation format provided by the data encapsulation type. The invention greatly reduced the workload due to the manual operations, and the running cost is reduced clearly.

Description

Method for automatically determining user data encapsulation type and upstream data processing device

The present invention relates to user data encapsulation technology in a communication network, and in particular to a method for automatically determining a user data encapsulation type and an upstream data processing device. Background of the invention

At present, the user terminal usually accesses the Internet (Internet) through the digital subscriber loop modem (xDSL Modem) and the Digital Subscriber Loop Access Multiplexer (DSLAM) and interacts with the Internet. The specific data interaction principle is shown in Figure 1. Show.

Referring to FIG. 1, the user terminal 110 is connected to the DSLAM 130 through the xDSL Modem 120, and the DSLAM 130 is usually connected to the Internet 150 through the switch 140. A switch can also be connected between the DSL Modem 120 and the DSLAM 130. The xDSL Modem 120 and the DSLAM 130 are respectively provided with data encapsulation types, and different data encapsulation types have different data encapsulation formats.

The xDSL Modem 120 can support more than one user connection, and is provided with a single data encapsulation type for encapsulating and decapsulating user data, namely: xDSL Modem 120 supports several user connections, xDSL Modem 120 pairs flow through The data encapsulation type applied when the user data is encapsulated or decapsulated has the same data encapsulation format. The DSLAM 130 can be coupled to more than one of the xDSL Modem 120, on which more than one type of data encapsulation is manually configured. The data encapsulation type applied by the DSLAM 130 may have a different data encapsulation format for each xDSL Modem 120 connected.

Currently, xDSL Modem 120 and DSLAM 130 typically communicate using the Asynchronous Transfer Mode (ATM) protocol, which supports Logical Link Control (LLC), LLC/Subnet. Three data encapsulation types, the additional point (SNAP) and the virtual circuit (VC). In order to ensure the normal operation of the communication, the data encapsulation type of the xDSL Modem 120 application has the same data encapsulation format as that of the data encapsulation type of the DSDSL Modem 120 application, and may also be considered as: xDSL Modem 120 The data encapsulation type of the application must be the same as the data encapsulation type of the DSLAM 130 application for the xDSL Modem 120 application.

For example, the data encapsulation type set by the user on the xDSL Modem 120 is an LLC encapsulation type, and the operator establishes a correspondence between the identifier of the xDSL Modem 120 and the data encapsulation type of the LLC on the DSLAM 130, that is, The data encapsulation type applied by the DSLAM 130 for the xDSL Modem 120 is set to the LLC encapsulation type.

In this way, when the user terminal 110 sends a data packet to the xDSL modem 120, the xDSL modem 120 encapsulates the received data packet in a data encapsulation format of a preset LLC encapsulation type, and then completes the encapsulated data packet. Sent to the DSLAM 130.

After receiving the data packet from the xDSL modem 120, the DSLAM 130 searches for the data encapsulation type value corresponding to the identifier of the DSL Modem 120 stored by itself. Then, the data encapsulation format of the LLC encapsulation type is used to decapsulate the received data packet, and the decapsulated data packet is sent to the Internet 150 through the switch 140.

Similarly, when the DSLAM 130 receives the data packet from the Internet 150, it reads the identifier of the xDSL Modem 120 included in the packet, and searches for the data encapsulation type value corresponding to the user connection identifier stored by itself. Then, the data encapsulation format of the LLC encapsulation type found by the application encapsulates the received data packet, and sends the encapsulated data packet to the DSL Modem 120. The xDSL modem 120 decapsulates the received data packet in the data encapsulation format of the LLC encapsulation type, and then sends the decapsulated data packet to the user terminal 110.

As can be seen from the above, the DSLAM 130 pin is usually set by manual setting. The data encapsulation type applied to the xDSL Modem 120 is the same as the data encapsulation type applied to the xDSL Modem 120. However, since the number of xDSL modems connected to the DSLAM 130 is usually in the thousands, tens of thousands, the operator needs to perform a large number of manual configuration operations on the DSLAM 130 to ensure the data encapsulation type and corresponding xDSL applied by the DSLAM 130 for each xDSL Modem. Modem applies the same data encapsulation type. It can be seen that the manual configuration operation is too large, which requires a lot of manpower and financial resources, and obviously increases the operating cost.

In addition, if the user replaces the xDSL Modem or changes the configuration of the xDSL Modem, the data encapsulation type of the xDSL Modem changes, and the DSLAM 130 connected to the xDSL Modem cannot know the change. Therefore, the DSLAM 130 still applies the data encapsulation format of the originally set data encapsulation type to encapsulate and decapsulate the data packet for the xDSL Modem, which will enable the DSLAM 130 to apply the data encapsulation type to the xDSL Modem. The data encapsulation type applied by the xDSL Modem is inconsistent, which causes the DSLAM 130 and the xDSL Modem to fail to perform data interaction normally, which ultimately affects the communication of the user terminal connected to the xDSL Modem and reduces user satisfaction. Summary of the invention

In view of this, the main object of the present invention is to provide a method for automatically determining the type of user data encapsulation, thereby reducing the workload of manual operations and reducing operating costs. Another object of the present invention is to provide an upstream data processing device.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

The present invention discloses a method for automatically determining a user data encapsulation type, the method comprising: a. The upstream data processing device receives a data message from the user terminal, and determines, according to the data message, whether the user terminal is processed with the upstream data. The device is established with a user connection, if Yes, proceed to step b; otherwise, proceed to step c;

b. The data encapsulation format of the data encapsulation type corresponding to the user connection stored by the upstream data processing device application, decapsulating the data packet, and ending the process;

The upstream data processing device determines the data encapsulation type corresponding to the received data packet according to the correspondence between the preset data packet and the data encapsulation type, and applies the data encapsulation format of the data encapsulation type. The data packet is decapsulated.

The method for determining in the step a is: the upstream data processing device searches for the same user connection identifier as the user connection identifier included in the received data packet in the saved user connection identifier, and if the user connection identifier is found, It is determined that a user connection is established with the user terminal; otherwise, it is determined that a user connection is not established with the user terminal. The step b includes: the upstream data processing device searches for the stored data encapsulation type value corresponding to the user connection identifier, and decapsulates the data packet by using a data encapsulation format of the data encapsulation type corresponding to the value.

In the step a, the determining method is: the upstream data processing device searches for the same user connection identifier and the user connection identifier corresponding to the user connection identifier included in the received data packet in the saved user connection identifier. a data encapsulation type value, if the user connection identifier and its corresponding data encapsulation type value are found, determining that a user connection is established with the user terminal; otherwise, determining that a user connection is not established with the user terminal;

The step b includes: decapsulating the data packet by the data encapsulation format of the data encapsulation type corresponding to the data encapsulation type value found by the upstream data processing device.

In step b and step c, after the upstream data processing device completes the decapsulation, the method further includes: sending the decapsulated data packet to the Internet, or locally processing the decapsulated data.

In the step c, the method for determining the data encapsulation type is: the upstream data processing device reads the header information of the received data packet, and the header information and data preset according to the communication protocol. The mapping relationship between the encapsulation types and the data encapsulation type corresponding to the header information of the received data packet is determined as the data encapsulation type corresponding to the data packet.

In the step C, the method for establishing the corresponding relationship and saving is: the upstream data processing device establishes a correspondence between the user connection identifier included in the data packet and the determined value of the data encapsulation type and saves.

The correspondence is saved in the upstream data processing device itself or in a third party device. The method further includes: the upstream data processing device reads the user connection identifier included in the data packet to be sent to the user terminal, searches for the stored data encapsulation type value corresponding to the user connection identifier, and uses the data encapsulation type corresponding to the value The data encapsulation format has the data encapsulation.

After the upstream data processing device completes the encapsulation, the method further includes: transmitting the encapsulated data packet to the user terminal.

The method further includes: the user terminal sending a user connection release message to the upstream data processing device, after receiving the message, the upstream data processing device reads the user connection identifier included in the message, and deletes the stored user connection identifier and the corresponding The value of the data encapsulation type.

The upstream data processing device is a DSLAM connected to the user terminal, or a switch connected between the DSLAM and the Internet, or a switch connected between the DSLAM and the user terminal.

The user connection identifier is a user terminal network address or a user session identifier. The present invention also discloses an upstream data processing device, including a storage unit, a connection determination unit, a package type determination unit, and a decapsulation unit. The storage unit is configured to store a data encapsulation format of a data encapsulation type corresponding to the user connection. Corresponding relationship between the data packet and the data encapsulation type; the connection judging unit is configured to determine, according to the data packet from the user terminal, whether the user terminal establishes a user connection with the upstream data processing device, and provides the judgment result a unit for determining a package type; a package type determining unit for determining The result is that when the user connection is established, determining that the data encapsulation type corresponding to the user connection in the storage unit has a data encapsulation format is a user data encapsulation format, and when the judgment result is that no user connection is established, according to the datagram in the storage unit. Corresponding relationship between the text and the data encapsulation type, determining that the data encapsulation type corresponding to the received data packet is a user data encapsulation type; and decapsulating unit, configured to encapsulate the encapsulation format according to the determined user data encapsulation type The data packet is decapsulated.

The upstream data processing device further includes: a post-processing unit, configured to send the decapsulated data to the Internet or perform local processing.

The storage unit is located in the upstream data processing device itself or in a third party device.

The upstream data processing device further includes: an encapsulating unit, configured to encapsulate the data packet of the user terminal according to the encapsulation type. The encapsulation type determining unit is further configured to read the user connection identifier included in the data packet to be sent to the user terminal, search for a data encapsulation type corresponding to the user connection identifier in the storage unit, and determine that it is user data. Package type.

The upstream data processing device further includes: a post-processing unit, configured to send the encapsulated data message to the user terminal.

The upstream data processing device further includes: a dry release unit configured to read the user connection identifier included in the user connection release message from the user terminal, and delete the user connection identifier in the storage unit and its corresponding data encapsulation type.

Compared with the prior art, in the method for automatically determining the user data encapsulation type provided by the present invention, the upstream data processing device may be based on a preset data packet and data encapsulation type. Corresponding relationship, determining a data encapsulation type corresponding to the received data packet, and decapsulating the data packet by using a data encapsulation format of the data encapsulation type; the upstream data processing device is still in the data Corresponding relationship between the user connection corresponding to the packet and the data encapsulation type is saved, and the data processing encapsulation format of the data encapsulation type is applied to the upstream data processing device for data encapsulation. Decapsulation; This makes the data encapsulation type of the upstream data processing device no longer need to be manually operated, which greatly reduces the workload of manual operations and significantly reduces operating costs. BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a schematic diagram of data interaction between a user terminal and the Internet;

2 is a flow chart of DSLAM processing user data according to a preferred embodiment of the present invention; FIG. 3 is a flow chart of DSLAM processing user data according to another preferred embodiment of the present invention; FIG. 4 is a flowchart of an upstream data processing device according to an embodiment of the present invention; schematic diagram. Mode for carrying out the invention

The present invention will be described in detail below with reference to the accompanying drawings and specific embodiments.

In the method for automatically determining the user data encapsulation type of the present invention, the data packet from the user terminal is received by an upstream data processing device such as a DSLAM, and the user is determined whether the user terminal establishes a user with the upstream data processing device according to the data packet. Connecting, if yes, the upstream data processing device applies a data encapsulation format that the data encapsulation type corresponding to the stored user connection has, and decapsulates the data packet; otherwise, the upstream data processing device is configured according to the preset data. Corresponding relationship between the packet and the data encapsulation type, determining a data encapsulation type corresponding to the received data packet, and decapsulating the data packet by using a data encapsulation format of the data encapsulation type; The data processing device is still in the number Corresponding relationship between the user connection corresponding to the message and the data encapsulation type is saved and saved.

Referring to FIG. 2, FIG. 2 is a flow chart of processing data of an upstream data processing device according to a preferred embodiment of the present invention, wherein the upstream data processing device is a DSLAM. The process includes the following steps:

Step 201: The DSLAM receives the data packet from the xDSL Modem at a time.

Step 202: After receiving the data packet from the xDSL Modem, the DSLAM reads the user connection identifier in the data packet, and determines whether a user connection corresponding to the user connection identifier is currently established, if the user connection is not established. Go to step 203; if the user connection is established, go to step 206.

The specific judgment method is as follows: The DSLAM searches for the same user connection identifier as the user connection identifier included in the received data packet in all the user connection identifiers saved by the DSLAM. If the user connection identifier is found, the DSLAM determines that the current connection is established. The user connection corresponding to the user connection identifier; otherwise, the DSLAM determines that the user connection corresponding to the user connection identifier is not currently established.

In an actual application, the determining method may be: the DSLAM searches for the same user connection identifier as the user connection identifier included in the received data packet, and the connection identifier with the user in all the user connection identifiers saved by the DSLAM. Corresponding to the saved data encapsulation type value, if the user connection identifier and the corresponding data encapsulation type value are found, the DSLAM determines that the user connection corresponding to the user connection identifier is currently established; otherwise, the DSLAM determines that the user connection identifier is not currently established. Corresponding user connection.

Step 203: The DSLAM reads the header information of the received data packet, and determines the data encapsulation type corresponding to the received data packet according to the correspondence between the header information and the data encapsulation type preset by the ATM protocol. . For example, the current ATM protocol stipulates that when the header information of the data packet contains 0xFE, OxFE, and 0x03, the number is According to the application, the LLC encapsulation type is applied; when the header information of the data packet includes OxAA, OxAA, and 0x03, the LLC/SNAP encapsulation type is applied to the data packet; when the header information of the data packet contains the word When the section is 0x00, 0x00, or 0x00, 0x00, 0x00, or 0x00, 0x00, OxXX, the VC encapsulation type is applied to the data packet.

In this way, if the DSLAM reads the header information of the received data packet and knows that the header contains the bytes OxFE, OxFE, and 0x03, the DSLAM can determine the LLC encapsulation type for the data packet.

Step 204: The DSLAM decapsulates the received data packet according to the determined data encapsulation format of the data encapsulation type, and further includes the user connection identifier included in the data packet and the determined data. The value of the encapsulation type establishes a correspondence, and the user connection identifier that establishes the corresponding relationship is saved together with the data encapsulation type value. The DSLAM usually saves the user connection identifier together with the data encapsulation type value in its own data storage device, and can also be saved in the third-party device, as long as the DSLAM can obtain the user connection identifier and the corresponding data encapsulation type value. .

Step 205: The DSLAM performs subsequent processing on the decapsulated data packet, and ends the process. There are various ways for the DSLAM to perform subsequent processing on the data packet, such as: forwarding the data packet to the Internet through the switch, or performing local processing on the data packet.

Step 206: The DSLAM further searches for the stored data encapsulation type value corresponding to the stored user connection identifier, and uses the data encapsulation format of the data encapsulation type corresponding to the value to receive the received The data packet is decapsulated. Of course, if the DSLAM has found the data encapsulation type value corresponding to the user connection identifier in step 202, the DSLAM decapsulates the data packet directly by using the data encapsulation format of the data encapsulation type corresponding to the value.

Step 207: The DSLAM forwards or locally processes the decapsulated data packet. Follow-up processing.

The reason why the determining operation is performed in step 202 is because the data message received by the DSLAM may be the data message sent by the user terminal to the DSLAM based on the newly established user connection for the first time, or the user terminal may be connected based on the user. Subsequent data packets sent to the DSLAM. Therefore, if the DSLAM receives the data packet sent by the user terminal for the first time based on the newly established user connection, the DSLAM performs the operation in step 203 to determine which data packet corresponds to the received data packet header information. The data encapsulation type; if the DSLAM receives the data packet sent by the user terminal based on the user connection, since the DSLAM has already stored the correspondence between the user connection and the data encapsulation type, step 206 can be performed. Decapsulating the data packet with a data encapsulation format of the saved corresponding data encapsulation type.

As can be seen from the above, the DSLAM can automatically determine the data encapsulation type to be applied to the data packet from the user terminal, and decapsulate the data packet by using the data encapsulation format of the data encapsulation type, so that the manual operation is performed. The amount is greatly reduced and the operating costs are significantly reduced.

What has been described above is that the DSLAM determines the type of data encapsulation to be applied by the data message from the user terminal, and the corresponding data encapsulation operation. As with this operation principle, when the DSLAM receives a data message from the Internet to be sent to the user terminal, or the DSLAM itself generates a data message to be sent to the user terminal, the DSLAM applies the process shown in FIG. The data encapsulation type to be applied to the data message to be sent to the user terminal, and the corresponding data encapsulation operation.

Referring to FIG. 3, FIG. 3 is a flowchart of processing user data by a DSLAM according to another preferred embodiment of the present invention, where the process includes the following steps:

Step 301: The DSLAM receives data packets from the Internet at a time.

Step 302: When the DSLAM receives the data packet from the Internet, it may determine the The user connection to which the data message belongs has been established, and the DSLAM has applied the corresponding method described in FIG. 2 to establish a correspondence between the user connection identifier and the value of the data encapsulation type.

Therefore, when receiving the data packet, the DSLAM can read the user connection identifier included in the data packet, and look up the stored data encapsulation type value corresponding to the user connection identifier. Thereafter, the DSLAM determines that the data encapsulation type corresponding to the found data encapsulation type value is the data encapsulation type to which the data packet is to be applied.

Step 303: The DSLAM encapsulates the data packet according to the data encapsulation format of the found data encapsulation type.

Step 304: The DSLAM sends the encapsulated data packet to the xDSL Modem, and the xDSL Modem decapsulates the received data packet according to the data encapsulation format of the pre-set data encapsulation type, and the decapsulation is completed. The data message is sent to the user terminal.

Of course, in step 301, the DSLAM may also generate a data message to be sent to the user terminal by itself according to the user request. Then, in step 302, the DSLAM reads the user connection identifier included in the data packet, and searches for the stored data encapsulation type value corresponding to the user connection identifier. Thereafter, the DSLAM determines that the data encapsulation type corresponding to the found data encapsulation type value is the data encapsulation type to which the data message is to be applied.

In the flow shown in Figures 2 and 3, when the user terminal disconnects from the network, the user terminal sends a user connection release message to the DSLAM. After receiving the user connection release message, the DSLAM reads the user connection identifier contained in the message, and deletes the stored user connection identifier and the corresponding data encapsulation type value.

It can be seen from the above that the DSLAM can automatically determine the data encapsulation type to be applied to the data packet from the Internet, and encapsulate the data packet by using the data encapsulation format of the data encapsulation type, so that the workload of the manual operation is greatly increased. Reduced and significantly reduced operating costs. In the communication process, the operation of automatically determining the data encapsulation type to be applied to the data message is usually completed by the DSLAM. However, in an actual application, the operation may be completed by an upstream data processing device such as a switch connected between the Internet and the DSLAM, or may be completed by an upstream data processing device such as a switch connected between the xDSL Modem and the DSLAM. . In this case, the only change in the flow shown in Figures 2 and 3 is that the operating subject has changed, i.e., the corresponding operation originally performed by the DSLAM is changed to be performed by the switch. The upstream data processing device is a communication device such as the DSLAM or the switch that is located at an upstream location of the user terminal for the user terminal.

Further, the user connection identifier may be any one of a user terminal network address, a user session identifier, and the like.

The method for automatically determining the user data encapsulation type described above can be applied to both the ATM protocol and other types of communication protocols.

The above method of automatically determining the user data encapsulation type can be implemented by an upstream data processing device as shown in FIG. Referring to FIG. 4, the data processing device of this embodiment includes a storage unit, a connection determining unit, a package type determining unit, and a decapsulation unit, and may further include a packaging unit, a post-processing unit, and a releasing unit.

The storage unit stores a data encapsulation format of the data encapsulation type corresponding to the user connection, and also stores a correspondence between the data packet and the data encapsulation type. In addition, the storage unit may be located in the upstream data processing device itself or in a third party device.

When the upstream data processing device receives the data packet from the user terminal, the connection determining unit determines whether the user terminal establishes a user connection with the upstream data processing device according to the data message by using the determining method described in step 202, and The judgment result is provided to the package type determining unit, and the judgment result is that the user connection is established or the user connection is not established. When the result of the determination is that the user connection is established, the encapsulation type determining unit determines the number of the data encapsulation type corresponding to the user connection in the storage unit by using the method described in step 206. According to the encapsulation format, the user data encapsulation format is provided, and the determined user data encapsulation format is provided to the decapsulation unit; the encapsulation type determining unit determines the correspondence relationship between the user and the received datagram when the judgment result is that the user connection is not established. The data encapsulation type corresponding to the text is a user data encapsulation type, and the determined user data encapsulation format is provided to the decapsulation unit. Then, the decapsulation unit decapsulates the data packet according to the encapsulation format of the user data encapsulation type determined by the encapsulation type determining unit, and sends the decapsulated data packet to the post-processing unit. The post-processing unit sends the decapsulated data message to the Internet or performs local processing.

When the upstream data processing device receives a data message from the Internet to be sent to the user terminal, or generates a data message to be sent to the user terminal, the encapsulation type determining unit may further read the data packet to be sent to the user terminal. The user connection identifier included in the text finds the data encapsulation type corresponding to the user connection identifier in the storage unit, and determines that it is a user data encapsulation type, and then provides a encapsulation unit. The encapsulating unit encapsulates the data packet according to the data encapsulation format of the user data encapsulation type determined by the encapsulation type determining unit. Then, the post-processing unit sends the encapsulated data>3⁄4 text to the user terminal.

When the upstream data processing device receives the user connection release message from the user terminal, the front-end unit reads the user connection identifier included in the user connection release message, and deletes the user connection identifier and its corresponding data encapsulation type in the storage unit.

The upstream data processing device in this embodiment may be a DSLAM connected to the user terminal, or a switch connected between the DSLAM and the Internet, or a switch connected between the DSLAM and the user terminal.

It can be seen from the above that the method for automatically determining the user data encapsulation type provided by the present invention does not need to manually configure the data encapsulation type on the upstream data processing device such as the DSLAM or the switch by manual operation, so that the manual operation is performed. The workload is greatly reduced, and Significantly reduced operating costs.

Claims

Claim

A method for automatically determining a user data encapsulation type, the method comprising:

Receiving, by the upstream data processing device, a data packet from the user terminal, determining, according to the data packet, whether the user terminal establishes a user connection with the upstream data processing device, and if yes, proceeding to step b; otherwise, proceeding to step c ;

b. The data encapsulation format of the data encapsulation type corresponding to the user connection stored by the upstream data processing device application, decapsulating the data packet, and ending the process; c the upstream data processing device according to the preset datagram Corresponding relationship between the text and the data encapsulation type, determining a data encapsulation type corresponding to the received data packet, and decapsulating the data packet by using a data encapsulation format of the data encapsulation type.

The method according to claim 1, wherein after determining the data encapsulation type in step c, the method further comprises: establishing a correspondence between the user connection corresponding to the data packet and the data encapsulation type; save.

3. The method according to claim 1, wherein in the step a, the determining method is:

The upstream data processing device searches for the same user connection identifier as the user connection identifier included in the received data packet in the saved user connection identifier, and if the user connection identifier is found, determines that the user is established with the user terminal. Connecting; otherwise, determining that a user connection is not established with the user terminal;

Step b includes: the upstream data processing device searches for the data encapsulation type value corresponding to the stored user connection identifier, and decapsulates the data packet by using a data encapsulation format of the data encapsulation type corresponding to the value.

4. The method according to claim 1, wherein in step a, the determining the way is:

The upstream data processing device searches for the same user connection identifier as the user connection identifier included in the received data packet and the data encapsulation type value corresponding to the user connection identifier in the saved user connection identifier, if the user connection is found. Identifying, and the corresponding data encapsulation type value, determining that a user connection is established with the user terminal; otherwise, determining that a user connection is not established with the user terminal;

The method of claim 2, wherein, in step b and step c, after the upstream data processing device completes the decapsulation, the method further comprises: sending the decapsulated data packet to the Internet, or The data packet that completes the decapsulation is processed locally.

The method according to claim 2, wherein in step c, the method for determining the data encapsulation type is:

The upstream data processing device reads the header information of the received data packet, and encapsulates the data corresponding to the header information of the received data packet according to the correspondence between the header information and the data encapsulation type set in advance by the communication protocol. The type is determined to be the data encapsulation type corresponding to the data message.

7. The method according to claim 2, wherein in step c, the method of establishing the corresponding relationship and saving is:

The upstream data processing device establishes a correspondence between the user connection identifier included in the data packet and the determined value of the data encapsulation type and saves.

The method according to claim 2, wherein the correspondence is stored in the upstream data processing device itself or in a third party device.

9. The method of claim 1, wherein the method further comprises: the upstream data processing device reading the user included in the data message to be sent to the user terminal The connection identifier is used to search for the stored data encapsulation type value corresponding to the user connection identifier, and encapsulate the data packet by using a data encapsulation format of the data encapsulation type corresponding to the value.

The method of claim 9, wherein after the upstream data processing device completes the encapsulation, the method further comprises: transmitting the encapsulated data message to the user terminal.

11. The method of claim 1 or 2, wherein the method further comprises:

The user terminal sends a user connection release message to the upstream data processing device. After receiving the message, the upstream data processing device reads the user connection identifier included in the message, and deletes the stored user connection identifier and the corresponding data encapsulation type value. .

12. The method according to claim 1, wherein the upstream data processing device is a digital subscriber loop access multiplexer DSLAM connected to the user terminal, or is connected between the DSLAM and the Internet. A switch, or a switch connected between the DSLAM and the user terminal.

The method according to claim 3, 4, 9 or 11, wherein the user connection identifier is a user terminal network address or a user session identifier.

An upstream data processing device, comprising: a storage unit, a connection determination unit, a package type determination unit, and a decapsulation unit, wherein

a storage unit, configured to store a data encapsulation format of the data encapsulation type corresponding to the user connection, and a correspondence between the data packet and the data encapsulation type;

a connection determining unit, configured to determine, according to the data packet from the user terminal, whether the user terminal establishes a user connection with the upstream data processing device, and provides the determination result to the package type determining unit;

a package type determining unit, configured to determine, when the judgment result is that a user connection is established The data encapsulation type corresponding to the user connection in the storage unit has a data encapsulation format of a user data encapsulation format, and when the judgment result is that no user connection is established, according to the correspondence between the data packet and the data encapsulation type in the storage unit Relationship, determining that the data encapsulation type corresponding to the received data packet is a user data encapsulation type;

And a decapsulation unit, configured to decapsulate the data packet according to the determined encapsulation format of the user data encapsulation type.

The upstream data processing device of claim 14, wherein the upstream data processing device further comprises: a post-processing unit, configured to send the decapsulated data message to the Internet or perform local processing.

The upstream data processing device according to claim 14, wherein the storage unit is located in the upstream data processing device itself or in a third party device.

The upstream data processing device of claim 14, wherein the upstream data processing device further comprises: a packaging unit, configured to: according to the data encapsulation format pair of the user data encapsulation type determined by the encapsulation type determining unit The data packet to be sent to the user terminal is encapsulated;

The encapsulation type determining unit is further configured to read the user connection identifier included in the data packet to be sent to the user terminal, search for a data encapsulation type corresponding to the user connection identifier in the storage unit, and determine that it is user data. Package type.

The upstream data processing device of claim 17, wherein the upstream data processing device further comprises: a post-processing unit, configured to send the encapsulated data message to the user terminal.

The upstream data processing device according to claim 14, wherein the upstream data processing device further comprises: a releasing unit, configured to read a user connection identifier included in a user connection release message from the user terminal, and delete The user connection identifier in the storage unit and its corresponding data encapsulation type.

The upstream data processing device according to claim 14, wherein the upstream data processing device is a DSLAM connected to the user terminal, or a switch connected between the DSLAM and the Internet, or connected to the DSLAM and A switch between the user terminals.