CN117956043A

CN117956043A - Message compression method and device

Info

Publication number: CN117956043A
Application number: CN202211340053.9A
Authority: CN
Inventors: 谭策
Original assignee: Beijing Huawei Digital Technologies Co Ltd
Current assignee: Beijing Huawei Digital Technologies Co Ltd
Priority date: 2022-10-29
Filing date: 2022-10-29
Publication date: 2024-04-30

Abstract

The application discloses a message compression method and device, which are applied to gateway equipment. In the method, a service data packet sent by a user is received, and a target compression strategy is determined according to a target IP address of the service data packet; and then, compressing the service data packet according to the target compression strategy. The application determines the corresponding target compression strategy according to the destination IP address of the service data packet, compresses the service data packet, and further can realize the compression of the appointed service data of the user.

Description

Message compression method and device

Technical Field

The present application relates to the field of data processing technologies, and in particular, to a method and apparatus for packet compression.

Background

The gateway equipment is compatible with various external broadband network access modes and becomes a connecting bridge and portal of the home internal network and the external network. Among them, broadband network gateway (broadband network gateway, BNG) devices are important as conventional broadband access gateway devices in subscriber broadband access services and scenarios. The main requirements on BNG devices on subscriber access are subscriber authentication, access control, traffic scheduling, etc.

With the layering of various internet services, the session number requirements of users supported by BNG devices are continuously improved, the access bandwidth of the users is continuously improved, and the access bandwidth of the users becomes an important factor affecting the broadband experience of the users due to the limitation of the hardware optical fiber links of the devices. Therefore, the service data generated after the user is accessed needs to be compressed and transmitted.

In the prior art, an IP payload compression protocol (IP payload compression protocol, IPComp or IPPCP) is generally used to compress service data, however, IPComp only supports matching between a five-tuple and an access control list (access control list, ACL) and performs data compression, so that separate charging and statistics cannot be performed on the data traffic of the compressed portion of the access user, customized compression service cannot be realized for the access user, and bandwidth experience of the access user cannot be improved.

Disclosure of Invention

The embodiment of the application provides a message compression method and a message compression device, which can compress a business data packet of a user part so as to realize customized compression service for an access user.

In a first aspect, the present application provides a method for compressing a message, applied to a gateway device, where the method includes:

The gateway equipment receives the service data packet sent by the user and determines a target compression strategy according to the target IP address of the service data packet. And the gateway equipment compresses the service data packet according to the determined target compression strategy.

In the method, gateway equipment determines a target compression strategy corresponding to a service data packet based on a target IP address carried by the service data packet after receiving the service data packet sent by a user; and then, the gateway equipment compresses the service data packet based on the determined target compression strategy to realize the compression of the service data packet appointed by the user, thereby providing customized compression service for the user.

In one possible design, the gateway device determines a service group corresponding to the destination IP address according to the correspondence between the IP address and the service group in the set user control list; the gateway device then determines a target compression policy corresponding to the service group from the plurality of compression policies.

In the design, the gateway device determines whether a service group corresponding to a target IP address exists in a preset user control list, and if so, determines a target compression strategy corresponding to the service group from a plurality of compression strategies so as to obtain the target compression strategy corresponding to the service data packet sent by the user.

In one possible design, the gateway device activates a plurality of compression policies bound to the user after determining that the user access was successful; or the gateway device may also activate a plurality of compression policies issued by the server after determining that the user access is successful.

In the design, the gateway device can directly activate a plurality of compression strategies bound with the user after determining that the user is successfully accessed, and can also activate a plurality of compression strategies issued by the received server after determining that the user is successfully accessed, so as to determine whether the service data packet needs to be compressed to provide a data basis when transmitting the service data packet for the subsequent user.

In one possible design, the gateway device determines a data bandwidth corresponding to the service data packet; when the data bandwidth is determined to be smaller than or equal to the service bandwidth in the target compression strategy, compressing the service data packet according to the message compression rule in the target compression strategy; or when the data bandwidth is determined to be larger than the service bandwidth, the gateway equipment limits the speed of the service data packet according to the service bandwidth, and compresses the service data packet after the speed limit.

In the design, the gateway device determines whether the service data packet needs to be speed-limited according to the data bandwidth corresponding to the service data packet and the service bandwidth in the target compression strategy, and the data bandwidth corresponding to the compressed service data packet can be ensured to meet the service bandwidth requirement in the target compression strategy by speed-limiting the service data packet.

In one possible design, the gateway device transmits the compressed service data packet to the destination IP address.

In one possible design, the gateway device generates the compression policy by establishing a correspondence between the service bandwidth, a message compression rule, and the service group; and the gateway equipment also generates a user control list by establishing the corresponding relation between the IP address and the service group.

In the design, the gateway device can generate the compression policy by establishing the corresponding relation between the service bandwidth, the message compression rule and the service group, and generate the user control list by establishing the corresponding relation between the IP address and the service group, so that the gateway device can determine whether the corresponding compression policy exists in the service data packet based on the user control list.

In one possible design, the gateway device binds the compression policy under the domain of the user.

In the design, the gateway device binds the generated compression strategy to the domain of the user, and can directly activate the compression strategy bound with the user after the user is successfully accessed, so that whether the corresponding compression strategy exists in the service data packet transmitted by the user or not can be rapidly and accurately judged, and the service data packet can be compressed.

In a second aspect, the present application provides a packet compression device, applied to a gateway apparatus, where the device includes:

the receiving module is used for receiving the service data packet sent by the user;

The determining module is used for determining a target compression strategy according to the destination IP address of the service data packet;

and the compression module is used for compressing the service data packet according to the target compression strategy.

In one possible design, the determining module is specifically configured to:

Determining a service group corresponding to the target IP address according to the corresponding relation between the IP address and the service group in the set user control list;

among the plurality of compression policies, a target compression policy corresponding to the service group is determined.

In one possible design, before receiving the service data packet sent by the user, the receiving module is further configured to:

activating the compression strategies bound with the user after the user is successfully accessed; or alternatively, the first and second heat exchangers may be,

And after the user is successfully accessed, activating the compression strategies issued by the server.

In one possible design, the compression module is specifically configured to:

determining the data bandwidth corresponding to the service data packet;

if the data bandwidth is smaller than or equal to the service bandwidth in the target compression strategy, compressing the service data packet according to a message compression rule in the target compression strategy; or alternatively, the first and second heat exchangers may be,

And if the data bandwidth is larger than the service bandwidth, limiting the speed of the service data packet according to the service bandwidth, and compressing the service data packet after limiting the speed.

In one possible design, after the compressing the service data packet, the compressing module is further configured to:

And transmitting the compressed service data packet to the destination IP address.

In one possible design, the apparatus further comprises a generation module; the generating module is specifically configured to:

generating the compression strategy by establishing the corresponding relation among the service bandwidth, the message compression rule and the service group;

And generating the user control list by establishing a corresponding relation between the IP address and the service group.

In one possible design, after generating the compression policy, the generating module is further configured to:

Binding the compression policy under the domain of the user.

In a third aspect, the present application provides a gateway device comprising a processor and a memory, the memory storing one or more computer programs, the one or more computer programs comprising instructions which, when invoked by the processor, cause the processor to perform the method of message compression of the first aspect described above.

In a fourth aspect, the present application provides a computer readable storage medium having stored thereon a computer program or instructions which, when executed, cause a computer to perform the method of the first aspect or any of the possible implementations of the first aspect.

In a fifth aspect, the application provides a computer program product which, when executed by a computer, causes the computer to perform the method of the first aspect or any of the possible implementations of the first aspect.

The beneficial effects of the second aspect are described with reference to the beneficial effects of the first aspect, and the detailed description is not repeated here.

Drawings

Fig. 1 is a schematic diagram of an application scenario of a possible message compression according to an embodiment of the present application;

fig. 2 is a schematic diagram of another possible application scenario of message compression according to the scheme provided by the embodiment of the present application;

fig. 3 is a schematic diagram of one possible message compression method according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a possible relationship between a user and a compression policy and an IP address according to an embodiment of the present application;

fig. 5 is a schematic flow chart of a possible message compression method according to an embodiment of the present application;

Fig. 6 is a schematic structural diagram of a possible message compression apparatus according to an embodiment of the present application;

Fig. 7 is a schematic structural diagram of a possible gateway device according to an embodiment of the present application.

Detailed Description

The embodiment of the application provides a message compression method and device. The method and the device are based on the same conception, and because the principles of solving the problems by the method and the device are similar, the implementation of the device and the method can be referred to each other, and the repetition is not repeated.

In order to make the objects, technical solutions and advantages of the embodiments of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings. Wherein in the description of embodiments of the application, the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature.

For ease of understanding, a description of concepts related to the application is given by way of example for reference.

1) The value added service, which is an additional communication service developed by means of the resources of the public telecommunication network and other communication equipment, has a value that increases the economic benefit or the functional value of the original network, and is called a telecommunication value added service. More precisely, the value added service is a charging service additionally provided to the user, which is a value added to the communication industry, and which is a value added to the user.

2) Dial-up access, i.e., modem dial-up access, refers to a way of connecting an existing telephone line to an internet service provider ("ISP") via a Modem ("Modem", commonly known as a "cat") installed on a computer to thereby enjoy internet services.

3) The domains refer to units independently operated in the Windows network, and trust relationship (i.e. trust relationship) needs to be established when the domains access each other. A trust relationship is a bridge that connects from domain to domain. After a trust relationship is established between one domain and other domains, 2 domains can be managed according to the needs, and equipment resources such as files, printers and the like can be distributed across networks, so that sharing and management of network resources among different domains are realized. The domain is both a logical organization unit of the Windows network operating system, in which the domain is a security boundary, and a logical organization unit of the Internet. A domain administrator can only manage the inside of a domain, and can access or manage other domains unless other domains explicitly give other management rights; each domain has its own security policies and its secure trust relationships with other domains.

In the description of the embodiment of the present application, "and/or" describing the association relationship of the association object indicates that three relationships may exist, for example, a and/or B may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship. At least one in reference to the present application means one or more; plural means two or more. In addition, it should be understood that in the description of the present application, the words "first," "second," and the like are used merely for distinguishing between the descriptions and not for indicating or implying any relative importance or order. Embodiments of the present application will be described in detail below with reference to the accompanying drawings.

In order to realize customized compression service for users, the embodiment of the application provides a message compression method which is applied to gateway equipment. In the method, gateway equipment receives a service data packet sent by a user and determines a target compression strategy according to a target IP address of the service data packet; and then, the gateway equipment compresses the service data packet according to the target compression strategy. After determining the target compression policy corresponding to the service data packet, the gateway device can compress the service data packet, so as to realize the designated service data compression of the user, realize the customized compression service of the user, and independently charge and count the compressed service data packet.

Embodiments of the present application will be described in detail below with reference to the accompanying drawings.

Fig. 1 is a schematic diagram of an application scenario of a possible message compression, where the scheme provided by the embodiment of the present application is applicable. As shown in fig. 1, the application scenario includes a user (i.e., a terminal device), a gateway device, and a network. The gateway device may be a broadband access gateway device, and in particular may be a broadband network gateway (broadband network gateway, BNG) device.

The gateway device can bind the preconfigured compression strategy under the domain of the user, and when the user dials in, the gateway device can activate the compression strategy bound under the domain of the user.

In an alternative embodiment, the user sends a service data packet to the gateway device when accessing the network successfully; after receiving the service data packet, the gateway device determines a target compression policy from the activated compression policies according to the target IP address carried by the service data packet.

After determining the target compression strategy, the gateway device compresses the service data packet and transmits the compressed data packet to the target IP address. After receiving the compressed service data packet, the network decompresses the compressed service data packet and returns a return service data packet to the gateway device according to the decompressed service data packet. After receiving the backhaul service data packet, the gateway device decompresses the backhaul service data packet and sends the backhaul service data packet to the user.

Fig. 2 is a schematic diagram of another possible application scenario of message compression, to which the scheme provided by the embodiment of the present application is applicable. As shown in fig. 2, the application scenario includes a user, a gateway device, a server, and a network. The gateway device may be a broadband access gateway device, and in particular may be a broadband network gateway (broadband network gateway, BNG) device. The server may be a server with a remote user dial-in authentication service (remote authentication dial In user service, radius). The server stores the compression strategy configured by the gateway equipment.

In an alternative embodiment, the gateway device may send the user information to the server after the user accesses the gateway device. After receiving the user information, the server determines a compression strategy bound with the user and issues the determined compression strategy to the gateway equipment. The gateway device activates the compression policy after it is received.

When a user accesses the network, a service data packet is sent to a destination IP address through gateway equipment. In implementation, after receiving a service data packet, the gateway device determines a target compression policy corresponding to the service data packet, compresses the service data packet, and transmits the compressed service data packet to the network. The process of the specific embodiment of the user access to the network is the same as the process of the user access to the network in fig. 1, and will not be described herein.

The following describes the solution provided by the present application in connection with specific embodiments.

Fig. 3 is a schematic diagram of a message compression method according to an embodiment of the present application, which is applied to a gateway device. As shown in fig. 3, the method includes:

s301: and the gateway equipment receives the service data packet sent by the user.

In some alternative embodiments, the user sends a service data packet of the value added service to the gateway device when using the value added service. And the gateway equipment receives the service data packet sent by the user.

The gateway device also needs to activate the compression policy bound to the user before receiving the service data packet sent by the user. Optionally, the compression policy includes a service bandwidth, a packet compression rule, and a service cluster.

In implementation, the gateway device determines and activates a compression policy bound to the user after determining that the user access is successful.

In some alternative embodiments, the gateway device activates a plurality of compression policies bound to the user under the user's domain after determining that the user access was successful.

In other alternative embodiments, the gateway device activates a plurality of compression policies issued by the server after determining that the user access was successful.

In the implementation, after determining that the user access is successful, the gateway device sends the user information to the server. And the server determines a compression strategy bound with the user according to the user information and sends the determined compression strategy to the gateway equipment. The gateway device then receives and activates the plurality of compression policies issued by the server.

For example, after the user accesses the gateway device, the gateway device sends user information to the Radius server; the Radius server determines the compression strategy of the value-added service bound with the user according to the user information, and sends the determined compression strategy to the gateway equipment through modification authority (change of authorization, COA) operation so as to enable the gateway equipment to take effect of the compression strategy.

In some alternative embodiments, the gateway device also needs to configure compression policies and user control lists (user control list, UCL) for traffic requiring compression services before user access.

Optionally, the gateway device may generate the compression policy by establishing a correspondence between the service bandwidth, the packet compression rule, and the service group. The service bandwidth is the bandwidth corresponding to the service. The message compression rule comprises information such as quintuple information which needs to be reserved when the IP message of the service data packet is compressed.

In other optional embodiments, the compression policy configured by the gateway device may further include a charging manner. For example, the traffic for the traffic transmission is charged separately.

For example, when the IP traffic corresponding to the value-added service needs to be compressed in the transmission process, the gateway device may bind the service bandwidth size, the message compression rule and the service cluster corresponding to the value-added service to the newly added compression policy, so as to obtain the compression policy corresponding to the value-added service.

For example, as shown in table 1, the embodiment of the present application provides configuration information of a compression policy of a value added service, as shown in table 1 below:

table 1: configuration information of compression strategy of value added service

Value added service compression strategy	Service bandwidth	Message compression rules	Source service group (Source service-group)
				Service policy 1	100M	1	Service group (service-group) 1
Service policy 2	300M	2	Service cluster 2
				Service policy 3	500M	3	Service cluster 3
Service policy 4	1G	4	Service cluster 4
				Service policy 5	1G	5	Service cluster 5

The service bandwidth refers to the maximum bandwidth capable of compressing the service data packet corresponding to the service. For example, in the service policy 1, when the bandwidth of the service data packet is less than or equal to 100M, the gateway device directly compresses the service data packet according to the message compression policy; in the service policy 1, when the bandwidth of the service data packet is greater than 100M, the gateway device cannot compress the service data packet corresponding to the service policy, and when the data bandwidth of the service data packet needs to be limited to 100M, the gateway device can compress the limited service data packet.

The message compression rule refers to a compression rule adopted by the gateway device for the service data packet corresponding to the service, wherein the compression rule comprises five-tuple information and other information which need to be reserved when the IP message of the service data packet is compressed.

After the gateway device generates the compression policy of the value added service, the generated compression policy is bound under the domain of the corresponding user. After the user accesses the gateway equipment, the gateway equipment activates the compression strategy of the value added service bound with the user; after receiving the service data packet sent by the user, the gateway device determines the target IP address of the service data packet. The gateway equipment matches the target IP address with the IP address in the UCL, and if the matching is successful, the service cluster corresponding to the target IP address is determined in the UCL. Then, the gateway equipment matches the service cluster corresponding to the target IP address with the service cluster in the compression strategy, and if the matching fails, the gateway equipment directly sends a service data packet to the target IP address; and if the matching is successful, determining a target compression strategy corresponding to the service cluster. The gateway device limits the data bandwidth of the service data packet according to the service bandwidth in the target compression strategy, compresses the limited service data packet according to the message compression rule in the target compression strategy, and transmits the compressed service data packet to the target IP address.

In some optional embodiments, after generating the compression policy, the gateway device also needs to generate the UCL corresponding to the compression policy.

In implementation, the gateway device may generate the UCL by establishing a correspondence between the IP address and the service group. Wherein, the IP address is the IP address of the network element with decompression capability.

For example, as shown in table 2, an embodiment of the present application provides configuration information of UCL, as shown in table 2 below:

Table 2: configuration information of UCL

UCL	Source service group	Destination IP address
			UCLv4 1	Service cluster 1	IP Address 1
UCLv4 2	Service cluster 2	IP Address 2
			UCLv4 3	Service cluster 3	IP Address 3
UCLv6 1	Service cluster 1	IPv6 address 1
			UCLv6 2	Service cluster 4	IPv6 address 2

In some alternative embodiments, when a user uses a service corresponding to a compression policy, the gateway device binds the corresponding compression policy under the user's domain.

Alternatively, the gateway device may bind the multiple compression policies directly under the user's domain. Or the gateway device may also bind multiple compression policies to servers under the user's domain.

In some alternative embodiments, the user may bind multiple compression policies and the user's traffic also includes multiple compressible traffic destination IP addresses.

For example, as shown in fig. 4, an embodiment of the present application provides a schematic diagram of a relationship between a user and a compression policy and an IP address. In fig. 4, compression policies bound to user 1 are compression policy 1, compression policy 2, and compression policy 3; and the compressible traffic destination address corresponding to the user 1 comprises an IP address 1, an IP address 2 and an IP address 3. And, the compression policy of the user binding with the user 2 in fig. 4 includes a compression policy 2, a compression policy 3 and a compression policy 4, and the compressible traffic destination address corresponding to the user 2 includes an IP address 2, an IP address 3 and an IPv6 address 2.

S302: and the gateway equipment determines a target compression strategy according to the destination IP address of the service data packet.

In some alternative embodiments, the gateway device determines the destination IP address of the service data packet after receiving the service data packet. And the gateway equipment determines a service group corresponding to the target IP address according to the corresponding relation between the IP address in the set UCL and the service group. The gateway device determines a target compression policy corresponding to the service group among the plurality of compression policies.

For example, as shown in fig. 4, after receiving the service data packet sent by the user 1, the gateway device determines the destination IP address of the service data packet as the IP address 1. The IP address 1 is a compressible traffic destination address corresponding to the user 1, that is, the service data packet supports packet compression. The gateway device determines a service group 1 corresponding to the IP address 1 according to the corresponding relation between the IP address in the set UCL and the service group. The gateway device then determines a target compression policy matching the service group 1 among compression policies 1,2 and 3 bound to the user 1. The gateway device determines the target compression policy corresponding to service group 1 as compression policy 2.

As another example, as shown in fig. 4, after receiving the service data packet sent by the user 2, the gateway device determines the destination IP address of the service data packet to be IP address 1, where the compressible traffic destination address corresponding to the user 2 does not include IP address 1, which indicates that the destination IP address of the service data packet of the user 2 does not support compression. The gateway device cannot match the same IP address as the IP address 1 in the set UCL, and the gateway device directly transmits the service data packet to the IP address 1.

S303: and the gateway equipment compresses the service data packet according to the target compression strategy.

In some optional embodiments, the gateway device determines a data bandwidth corresponding to the service data packet, and determines whether the data bandwidth is less than or equal to the service bandwidth in the target compression policy.

The gateway device may determine the data bandwidth according to the traffic of the service data packet.

In some optional embodiments, when determining that the data bandwidth is less than or equal to the traffic bandwidth in the target compression policy, the gateway device compresses the traffic data packet according to a packet compression rule in the target compression policy.

In other optional embodiments, when determining that the data bandwidth is greater than the service bandwidth, the gateway device limits the speed of the service data packet according to the service bandwidth; and the gateway equipment compresses the service data packet after speed limiting when determining that the data bandwidth corresponding to the service data packet is limited to the service bandwidth.

In implementation, when the gateway device determines that the data bandwidth is greater than the service bandwidth, the gateway device limits the flow of the service data packet until the data bandwidth of the service data packet after the speed limit is less than or equal to the service bandwidth.

When the gateway device compresses the service data packet, the gateway device can limit the bandwidth of the traffic of the service data packet according to the target compression policy. The bandwidth limitation can be set to be unified bandwidth limitation with other service data packets transmitted by the user, or can be independently performed for the service data packets, and meanwhile, the service corresponding to the service data packets can be independently charged.

In some alternative embodiments, the gateway device compresses the service data packet and transmits the compressed service data packet to the destination IP address.

For example, after compressing the service data packet of the value added service, the gateway device transmits the compressed service data packet to the network element indicated by the target IP address.

After receiving a message returned by the network for the sent service data packet, the gateway device decompresses the message and sends the message to the user, so as to ensure that the message format of the message received by the user is consistent with that of the sent service data packet.

In the application, gateway equipment determines a target compression strategy corresponding to a service data packet according to a destination IP address of the service data packet after receiving the service data packet sent by a user; the gateway device compresses the service data packet according to the determined target compression strategy, so that the gateway device can compress the appointed service data packet of the user, thereby providing customized compression service for the user, and further realizing independent statistics and charging of the appointed service.

Fig. 5 is a schematic flow chart of a message compression method according to an embodiment of the present application, and a specific flow chart of the method is described with reference to fig. 6.

S501: the gateway equipment generates a compression strategy by establishing the corresponding relation among the service bandwidth, the message compression rule and the service group.

S502: the gateway device generates UCL by establishing the corresponding relation between the IP address and the service group.

S503: the gateway device binds the compression policy under the domain of the user.

In implementation, when a user opens a service with a compression service, the gateway device binds a compression policy corresponding to the service under the domain of the user.

Alternatively, the gateway device may bind the compression policy directly under the domain of the user, or may bind the compression policy to a server under the domain of the user.

S504: after the gateway device determines that the user access is successful, a plurality of compression strategies bound with the user are activated.

S505: and the gateway equipment receives the service data packet sent by the user.

S506: the gateway equipment determines whether the destination IP address of the service data packet is successfully matched with the UCL; if not, executing step S507; if yes, go to step S508.

Wherein, UCL includes the corresponding relation between IP address and service group.

S507: the gateway device transmits the service data packet to the destination IP address.

S508: the gateway device determines a service cluster corresponding to the destination IP address from the UCL.

S509: the gateway device determines a target compression policy corresponding to the service group among the plurality of compression policies.

S510: the gateway device determines the data bandwidth corresponding to the service data packet.

S511: the gateway equipment determines whether the data bandwidth is larger than the service bandwidth in the target compression strategy; if yes, go to step S512; if not, step S513 is performed.

S512: and the gateway equipment limits the speed of the service data packet according to the service bandwidth.

In the implementation, the gateway device limits the flow of the service data packet until the data bandwidth corresponding to the service data packet after the speed limit is smaller than or equal to the service bandwidth.

S513: and the gateway equipment compresses the service data packet according to the message compression rule in the target compression strategy.

S514: the gateway device transmits the compressed service data packet to the destination IP address.

In the embodiment shown in fig. 5, the gateway device establishes a compression policy for the value added service to be compressed in advance, and configures the UCL according to the destination IP address of the compressible traffic of the user using the value added service, so that when the subsequent user accesses the network, the gateway device can perform specified compression for the service data packet transmitted by the user. And the gateway equipment can also count the flow of the value-added service transmitted by the user independently and charge the user independently, and can provide customized compression service for the user.

Based on the above embodiments and the same concept, the embodiments of the present application further provide a message compression device, where the message compression device is applied to a gateway device. As shown in fig. 6, the message compression apparatus 600 includes:

a receiving module 601, configured to receive a service data packet sent by a user;

a determining module 602, configured to determine a target compression policy according to a destination IP address of the service data packet;

And the compression module 603 is configured to compress the service data packet according to the target compression policy.

In one possible design, the determining module 602 is specifically configured to:

In one possible design, before receiving the service data packet sent by the user, the receiving module 601 is further configured to:

In one possible design, the compression module 603 is specifically configured to:

determining the data bandwidth corresponding to the service data packet;

In one possible design, after the compressing the service data packet, the compressing module 603 is further configured to:

In one possible design, the apparatus further comprises a generation module; the generating module 604 is specifically configured to:

In one possible design, after generating the compression policy, the generating module 604 is further configured to:

Binding the compression policy under the domain of the user.

Based on the above and the same concept, the present application provides a gateway apparatus as shown in fig. 7. Fig. 7 shows a schematic structural diagram of a gateway device 700.

Gateway device 700 includes at least one processor 710 for implementing or for supporting gateway device 700 to implement the functionality of the message compression apparatus in the method provided by the embodiments of the present application. For example, the processor 710 may create a compression policy and a user control list, or compress and transmit a service data packet, which are specifically described in the method example and are not described herein.

Gateway device 700 may also include at least one memory 720 for storing program instructions and/or data. Memory 720 is coupled to processor 710. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which may be in electrical, mechanical, or other forms for information interaction between the devices, units, or modules. Processor 710 may operate in conjunction with memory 720. Processor 710 may execute program instructions stored in memory 720. At least one of the at least one memory may be included in the processor.

Gateway device 700 may also include an interface 730 for communicating with processor 710 or for communicating with a user, network, or other device over a transmission medium. The other device may be a client, for example. Processor 710 may transmit and receive data using interface 730.

The specific connection medium between the interface 730, the processor 710, and the memory 720 is not limited in the embodiment of the present application. In the embodiment of the present application, the memory 720, the processor 710 and the interface 730 are connected through the bus 740 in fig. 7, and the bus is shown by a thick line in fig. 7, and the connection manner between other components is only schematically illustrated, but not limited thereto. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 7, but not only one bus or one type of bus.

In an embodiment of the present application, processor 710 may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution.

In an embodiment of the present application, the memory 720 may be a nonvolatile memory, such as a hard disk (HARD DISK DRIVE, HDD) or a Solid State Disk (SSD), or may be a volatile memory (RAM). The memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory in embodiments of the present application may also be circuitry or any other device capable of performing memory functions for storing program instructions and/or data.

Embodiments of the present application also provide a computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the method of message compression in the embodiment shown in fig. 3.

Embodiments of the present application also provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of message compression in the embodiment shown in fig. 3.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims

1. The message compression method is characterized by being applied to gateway equipment and comprising the following steps:

Receiving a service data packet sent by a user;

Determining a target compression strategy according to the destination IP address of the service data packet;

and compressing the service data packet according to the target compression strategy.

2. The method of claim 1, wherein determining the target compression policy based on the destination IP address of the service data packet comprises:

3. The method of claim 2, wherein prior to receiving the service data packet sent by the user, the method further comprises:

4. A method according to any one of claims 1-3, wherein said compressing said traffic data packets according to said target compression policy comprises:

determining the data bandwidth corresponding to the service data packet;

5. The method according to any one of claims 1-4, wherein after compressing the service data packet, the method further comprises:

6. The method according to any one of claims 1-5, further comprising:

7. The method of claim 6, wherein after generating the compression policy, the method further comprises:

Binding the compression policy under the domain of the user.

8. A message compression apparatus, applied to a gateway device, comprising:

9. The apparatus of claim 8, wherein the determining module is specifically configured to:

10. The apparatus of claim 9, wherein the receiving module is further configured to, prior to receiving a service data packet sent by a user:

11. The apparatus according to any one of claims 8-10, wherein the compression module is specifically configured to:

determining the data bandwidth corresponding to the service data packet;

12. The apparatus according to any one of claims 8-11, wherein after the compressing the service data packet, the compressing module is further configured to:

13. The apparatus according to any one of claims 8-12, further comprising a generation module; the generating module is specifically configured to:

14. The apparatus of claim 13, wherein after generating the compression policy, the generating module is further configured to:

Binding the compression policy under the domain of the user.

15. A gateway device comprising a memory and a processor, the memory having stored thereon a computer program executable on the processor, which when executed by the processor, implements the method of any of claims 1-7.

16. A computer program product comprising instructions which, when executed by a processor, cause the computer to perform the method of any of claims 1-7.

17. A computer readable storage medium comprising computer program instructions which, when executed by a computer, perform the method of any of claims 1-7.