CN113950072B

CN113950072B - Gateway shunting method, device, equipment and storage medium

Info

Publication number: CN113950072B
Application number: CN202010684996.8A
Authority: CN
Inventors: 陈妍玉; 唐小勇; 陆宏霞; 朱磊
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Chengdu ICT Co Ltd
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Chengdu ICT Co Ltd
Priority date: 2020-07-16
Filing date: 2020-07-16
Publication date: 2023-08-15
Anticipated expiration: 2040-07-16
Also published as: CN113950072A

Abstract

The embodiment of the invention discloses a gateway shunting method, device, equipment and storage medium. Starting a timer to start timing when receiving an Internet Protocol (IP) address of the multi-access edge computing MEC device or an MEC device offline message; and when the timing duration of the timer exceeds the first preset duration, the IP or MEC equipment offline message is invalidated. The embodiment of the invention solves the ping-pong effect problem in the automatic configuration process of the shunt strategy, realizes the automatic configuration process of the shunt strategy without ping-pong effect, and ensures the service continuity of the high-reliability application scene and the requirement of an operator for binding an edge computing platform.

Description

Gateway shunting method, device, equipment and storage medium

Technical Field

The present invention relates to the field of software development, and in particular, to a gateway shunting method, device, equipment and storage medium.

Background

In the application scenario of the fifth generation mobile communication network (5th generation mobile networks,5G) with high reliability in the vertical industry, such as medical mobile ward round, remote diagnosis, electronic medical record, image diagnosis and other data transmission, in order to ensure the safety of the MEC device, an interconnection protocol (Internet Protocol, IP) between dynamic networks is required.

However, in the process of monitoring the dynamic IP in real time to ensure service continuity, when the network management equipment receives the IP reported by the MEC equipment but does not configure the policy later, if the MEC equipment reports the new service IP again, the network management equipment cannot know which IP configures the shunting policy for the gateway, so that a strong ping-pong effect exists.

In addition, in the process of detecting whether the MEC device is replaced to configure the start or stop of the shunt command to the gateway, if the gateway cannot detect the heartbeat message of the MEC device but does not report the heartbeat message to the network management device at a later time, or if the network management device receives the MEC device offline message reported by the gateway but does not configure the shunt command to the gateway at a later time, a strong ping-pong effect is generated.

Therefore, there is a strong ping-pong effect problem in the process of automatic configuration of the shunt strategy.

Disclosure of Invention

The embodiment of the invention provides a gateway shunting method, device, equipment and storage medium, solves the ping-pong effect problem in the shunting strategy automatic configuration process, realizes the shunting strategy automatic configuration process without ping-pong effect, and ensures the service continuity of a high-reliability application scene and the requirement of an operator for binding an edge computing platform.

In order to solve the technical problems, the invention comprises:

in a first aspect, a gateway offloading method is provided, applied to a network management device, where the method includes:

starting a timer to start timing when receiving an Internet Protocol (IP) address of the multi-access edge computing MEC device or an MEC device offline message;

and when the timing duration of the timer exceeds the first preset duration, the IP or MEC equipment offline message is invalidated.

In some implementations of the first aspect, the method further includes:

generating a first shunting strategy according to the IP;

if the first shunting strategy is sent to the gateway within the first preset duration, stopping timing by the timer; or alternatively, the process may be performed,

generating a termination shunt message according to the MEC equipment offline message;

and within the first preset duration, if the shunt termination message is sent to the gateway, stopping timing by the timer.

In some implementations of the first aspect, the first offload policy includes a domain name system protocol (Domain Name System, DNS) resolution policy, a second offload policy, and an offload bandwidth policy;

the DNS resolution strategy comprises a domain name and MEC equipment IP corresponding to the domain name;

the second flow splitting strategy comprises a destination MEC device IP and a port number;

the split bandwidth policy includes destination MEC device IP and split bandwidth.

In some implementations of the first aspect, the method further includes:

and when the gateway is successfully configured according to the first distribution strategy, sending a distribution opening instruction to the gateway, wherein the distribution opening instruction comprises the destination MEC equipment IP and the port number of the destination MEC equipment IP, and the distribution opening instruction is used for distributing data to the destination MEC equipment by the gateway.

In a second aspect, a method for splitting a gateway is provided, and the method is applied to the gateway, and includes:

when the information sent by the MEC equipment is not received within the second preset time length, generating an MEC equipment offline message, and starting a timer to start timing;

and when the timing duration of the timer exceeds a third preset duration, invalidating the MEC equipment offline message.

In some implementations of the second aspect, the method includes:

and within a third preset duration, if the MEC equipment offline message is sent to the network management equipment, stopping timing by the timer, wherein the MEC equipment offline message is used for the network management equipment to send the termination and distribution message to the gateway.

In a third aspect, a network management device is provided, which is characterized in that the network management device includes:

the starting module is used for starting a timer to start timing when receiving an Internet Protocol (IP) address of the multi-access edge computing MEC device or an MEC device offline message;

And the processing module is used for invalidating the IP or MEC equipment offline message when the timing duration of the timer exceeds the first preset duration.

In some implementations of the third aspect,

the processing module is also used for generating a first shunting strategy according to the IP;

the processing module is also used for generating a termination shunt message according to the MEC equipment offline message;

In some implementations of the third aspect, the first offload policy includes a DNS resolution policy, a second offload policy, and an offload bandwidth policy;

In some implementations of the third aspect,

the sending module is used for sending a shunt opening instruction to the gateway when the gateway is configured successfully according to the first shunt strategy, wherein the shunt opening instruction comprises a destination MEC device IP and a port number of the destination MEC device IP, and the shunt opening instruction is used for the gateway to shunt data to the destination MEC device.

In a fourth aspect, there is provided a gateway comprising:

the starting module is used for generating MEC equipment offline information when the information sent by the MEC equipment is not received within a second preset time length, and starting a timer to start timing;

and the processing module is used for invalidating the MEC equipment offline message when the timing duration of the timer exceeds a third preset duration.

In some implementations of the fourth aspect, the processing module is further configured to stop counting if the MEC device offline message is sent to the network management device within the third preset duration, where the MEC device offline message is used by the network management device to send a termination split message to the gateway.

In a fifth aspect, there is provided an electronic device, the device comprising: a processor and a memory storing computer program instructions;

the processor, when executing the computer program instructions, implements the first aspect and the method of gateway splitting in some implementations of the first aspect, or implements the second aspect and the method of gateway splitting in some implementations of the second aspect.

In a sixth aspect, there is provided a computer storage medium having stored thereon computer program instructions which, when executed by a processor, implement the first aspect and methods of gateway splitting in some implementations of the first aspect, or implement the second aspect and methods of gateway splitting in some implementations of the second aspect.

The embodiment of the invention provides a gateway shunting method, a gateway shunting device and a gateway shunting storage medium, which start a timer to start timing according to an acquired Internet Protocol (IP) address of MEC equipment or an MEC equipment offline message, and invalidate the IP or MEC equipment offline message when the timing duration of the timer exceeds a first preset duration, thereby solving the ping-pong effect problem in the shunting strategy automatic configuration process, realizing the shunting strategy automatic configuration process without ping-pong effect, and guaranteeing the service continuity of a high-reliability application scene and the requirement of an operator for binding an edge computing platform.

Drawings

In order to more clearly illustrate the technical solution of the embodiments of the present invention, the drawings that are needed to be used in the embodiments of the present invention will be briefly described, and other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is an interactive schematic diagram of a data distribution method according to an embodiment of the present invention;

fig. 2 is an interactive schematic diagram of a gateway splitting method according to an embodiment of the present invention;

fig. 3 is an interactive schematic diagram of another gateway offloading method according to an embodiment of the present invention;

Fig. 4 is an interactive schematic diagram of a method for configuring a gateway and an MEC device according to an embodiment of the present invention;

fig. 5 is a network management device according to an embodiment of the present invention;

fig. 6 is a gateway provided in an embodiment of the present invention;

fig. 7 is a block diagram of a hardware architecture of a computing device according to an embodiment of the present invention.

Detailed Description

Features and exemplary embodiments of various aspects of the present invention will be described in detail below, and in order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are merely configured to illustrate the invention and are not configured to limit the invention. It will be apparent to one skilled in the art that the present invention may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the invention by showing examples of the invention.

It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

With the rapid development of the mobile internet and the gradual penetration of industry informatization, global mobile data traffic presents an explosive growth situation, new services such as augmented Reality (Augmented Reality, AR)/Virtual Reality (VR), high-definition video, industrial internet of things and the like are continuously inoculated, requirements of Ultra-high reliability and low-delay communication (Ultra-reliable and Low Latency Communications, URLLC), enhanced mobile broadband (Enhanced Mobile Broadband, emmbb), large-scale machine type communication (Massive MachineType Communication, mMTC), real-time computing and the like are put forward for an operator network, the requirements of the existing centralized data processing mode with cloud computing as a core are difficult to meet, all traffic needs enter a core network, then are processed by a far-end cloud computing center, and then are returned to a user end by the operator network. In this mode, huge amounts of data can cause significant delays and congestion, as well as slow down the network operation. Therefore, the 5G mobile edge computing technology has been developed, MEC equipment is distributed at the user side, and the flow is locally split to the MEC equipment without flowing into the core network, so that the requirements of reducing time delay and optimizing the flow are met.

Fig. 1 is an interaction schematic diagram of a data distribution method according to an embodiment of the present invention.

As shown in fig. 1, the current data offloading method of a User Equipment may include that the User Equipment (UE) initiates a DNS query request of an MEC to a base station, the base station forwards the DNS query request to a gateway, the gateway hives the DNS query request and generates an MEC IP according to a DNS resolution policy configured by the gateway, and the gateway forwards the generated MEC IP to the User Equipment through the base station. And then, the user sends an MEC access request comprising the MEC IP to the gateway through the base station, the gateway sends the MEC access request comprising the MEC IP to the MEC server according to the configured distribution strategy, the MEC server responds according to the MEC access request comprising the MEC IP and generates MEC response data, and the MEC response data is sent to the user equipment through the gateway and the base station. If the DNS resolution policy configured in the gateway does not correspond to the MEC IP to the DNS query request of the MEC, the data of the user equipment is directly sent to the core network.

In the existing local distribution scheme under the independent networking (The National Shellfisheries Association, NSA)/independent networking (The Shellfisheries Association, SA) networking, when the system is applied to a high-reliability service application scene in the 5G vertical industry, for example, when medical mobile ward round, remote diagnosis, electronic medical record transmission, image diagnosis and other data transmission are carried out, dynamic IP is needed to ensure the safety of MEC.

By using dynamic IP, the IP address of the MEC is continuously changed, so that an attacker cannot easily locate the MEC position and the attacked service and application, the problem that related data in a high-reliability service application scene is revealed or stolen in the transmission process can be effectively avoided, and the privacy safety of enterprises is protected.

When using dynamic IP, real-time monitoring and feedback are required to ensure the continuity of the service. The MEC uses dynamic IP, namely the IP of the shunting destination is not fixed, real-time monitoring is needed to be carried out on the dynamic IP of the MEC, and the MEC actively reports the IP which is continuously changed to network management equipment so as to realize automatic configuration of a local shunting strategy and ensure the continuity of the service.

In the process, when the network management equipment receives the IP reported by the MEC but does not configure the strategy later, the MEC reports the new service IP again, and the network management equipment can not know which IP configures the distribution strategy for the gateway according to the new service IP, so that a strong ping-pong effect exists.

The existence of the ping-pong effect can cause the confusion and blockage of the automatic configuration flow of the shunt strategy, so that the local shunt service is interrupted, and the requirement of a high-reliability application scene on service continuity is not met. There is a need to address the ping-pong effect that exists in dynamic IP offloading.

Furthermore, MEC equipment is deployed in an industrial consumer premises, with the possibility of being replaced. To increase operator control and revenue to the edge computing platform, MEC equipment needs to be bound. The network management equipment needs to sense the state of the MEC equipment, and judges whether the MEC equipment is replaced or not through heartbeat detection, so that a command for starting or stopping the diversion is configured to the gateway.

However, when the gateway cannot detect the MEC device heartbeat message but does not report the network management device later, no matter the gateway cannot detect the MEC heartbeat message again or can receive the MEC heartbeat message, the gateway cannot know which message is used for deciding whether to report the network management device, so that the network management device cannot judge that the MEC device is replaced.

If the network management equipment receives the MEC equipment offline message reported by the gateway, but does not configure the termination and shunt command for the gateway at a later time, and then receives the MEC equipment offline message again, the network management equipment can not know whether to configure the termination and shunt command according to which message, so that ping-pong effect occurs, and the network management equipment interrupts configuring the termination and shunt command.

The existence of the ping-pong effect can cause the network management equipment to confuse and block the MEC equipment state sensing process, so that the MEC equipment binding is interrupted, the requirement of an operator for binding an edge computing platform is not met, and the local shunt of the gateway is confused and blocked.

Therefore, there is a strong ping-pong effect problem in the automatic configuration process of the shunt strategy of the local shunt of the gateway.

In order to solve the ping-pong effect problem in the method, the device, the equipment and the storage medium provided by the embodiment of the invention are used for shunting the gateway, starting a timer to start timing according to the acquired Internet Protocol (IP) address of MEC equipment or MEC equipment offline information, and invalidating the IP or MEC equipment offline information when the timing duration of the timer exceeds a first preset duration, thereby solving the ping-pong effect problem in the automatic configuration process of the shunting strategy, realizing the automatic configuration process of the shunting strategy without ping-pong effect, and guaranteeing the service continuity of a high-reliability application scene and the requirements of an operator for binding an edge computing platform.

The technical scheme provided by the embodiment of the invention is described below with reference to the accompanying drawings.

Fig. 2 is an interactive schematic diagram of a gateway splitting method according to an embodiment of the present invention. As shown in fig. 2, the method may be based on three execution bodies, including a network management device, a gateway, and an MEC device.

As shown in fig. 2, the gateway offloading method may include:

s101: when the network management equipment receives the internet protocol address IP of the multi-access edge computing MEC equipment, a shunting strategy configuration timer is started to start timing.

Note that the IP in S101 is a service IP related to the MEC device, and thus, the IP may also be referred to as a service IP.

In order to realize that the network management device can normally identify the MEC device and the information reported by the MEC device, the network management device needs to perform registration and authentication on the MEC device before executing S101.

The specific process of the network management device performing registration authentication on the MEC device may include the network management device executing S102: information of the MEC apparatus is received. The information of the MEC device is shown in table 1, and includes the management IP of the MEC device, the user name of the MEC device, and the authentication password corresponding to the user name.

TABLE 1

Field identification	Field name	Description of values
			ManagerIP	MEC management IP	MEC management IP
userName	User name	User name
			Password	Authentication password	Authentication password

After the network management device receives the information of the MEC device, S103 is executed again: and registering and authenticating the information of the MEC equipment. The MEC equipment after the registration and authentication of the network management equipment can enable the network management equipment to perform normal identification.

After the network management device completes the registration and authentication process of the MEC device, in order to enable the MEC device to report information to the network management device according to a preset rule, optionally, the network management device may further execute S104: and sending information comprising a service IP reporting mode to MEC equipment. The information included in the service IP reporting manner may include at least one of a reporting type, a reporting period, and a reporting trigger event, as shown in table 2.

After receiving the information of the service IP reporting manner, in order to configure the information included in S104, the MEC device may execute S105: and the MEC equipment analyzes and configures the information of the service IP reporting mode. To further achieve the effect of automatically configuring the shunt strategy.

As further shown in table 2, the service IP reporting manner configured by the MEC device may include at least one of periodic reporting and aperiodic reporting.

Specifically, when the configuration of the MEC device is periodically reported, the MEC device will report the service IP to the network management device according to the period.

When the MEC equipment is configured for aperiodic reporting, the MEC equipment queries the service IP according to the period T, and if the service IP queried at the current time T0 is different from the service IP queried at the time T1 (t1=t0-T), the reporting is triggered, and the service IP is reported to the MEC equipment.

TABLE 2

After the network management device completes registration authentication on the MEC device and the MEC device configures a service IP reporting mode, the network management device can already identify information reported by the MEC device, and the MEC device performs S106 according to the service IP reporting mode configured by the network management device to the MEC device in step S104: and sending the service IP of the MEC equipment to the network management equipment.

After S106, the MEC device may send the service IP of the MEC device to the network management device. Thereafter, S101 may be entered: when the network management equipment receives the service IP sent by the MEC equipment, a distribution strategy configuration timer is started to start timing.

Specifically, when receiving the service IP of the MEC device, the network management device may trigger the shunting policy configuration timer to start timing, and generate the first shunting policy according to the IP. The fields used in S101 may include a start timing field, a validity period T, as shown in Table 3 ₀ The timing field is ended. Wherein the effective period T ₀ And may also be referred to as a first preset time period.

TABLE 3 Table 3

At T ₀ In, if the network management device executes S107: and sending the first shunting strategy to the gateway, and stopping timing by a shunting strategy configuration timer.

In addition, it should be noted that if the time duration exceeds the valid period T0, the stop of the time counting is triggered, the time is reset to zero, the network management device invalidates the service IP message of the MEC device, and considers that the service IP message reported by the MEC device is invalid, and the configuration of the splitting policy is not performed. Therefore, when the network management equipment receives the service IP reported by the MEC equipment but does not configure the policy later, the network management equipment can invalidate the service IP reported by the MEC equipment, so that the network management equipment can not store the service IP of the useless MEC equipment, the MEC equipment reports the new service IP again at the moment, and the management platform only configures the diversion policy for the gateway according to the new service IP reported again, thereby solving the problem of ping-pong effect in the automatic configuration process of the diversion policy.

It should be further noted that the first splitting policy includes a DNS resolution policy, a second splitting policy, and a splitting bandwidth policy, where a field of the DNS resolution policy is shown in table 4, a field of the second splitting policy is shown in table 5, and a field of the splitting bandwidth policy is shown in table 6.

TABLE 4 Table 4

TABLE 5

TABLE 6

Different MEC devices may be allocated different bandwidths by using a split bandwidth policy that includes field information shown in table 6. The bandwidth allocation strategy can allocate bandwidth according to different MEC differential bandwidth requirements, so that the bandwidth allocation is more flexible, the bandwidth is fully utilized, and the possibility of allocation blocking is further reduced.

At S107: after the network management device sends the first offloading policy to the gateway, the gateway performs S108: the first split strategy is configured. After the gateway configuration is successful, the gateway performs S109: and sending a configuration success message to the network management equipment. The network management device executes S110 according to the configuration success message in S109: and sending a configuration success message to the MEC equipment. After receiving the configuration success message in S110, the MEC device stops reporting the service IP message to the network management device.

In addition, if the MEC device does not receive the configuration success message sent by the network management device, the MEC device may report the service IP to the network management device again after a period of time T1, so as to perform configuration of the splitting policy.

After the network management device executes S110 and sends a configuration success message to the MEC device, the network management device will execute S111: and sending a shunt opening command to the gateway. The fields of the split start command may be as shown in table 7.

TABLE 7 shunt start command

The gateway responds to the configuration of the destination equipment according to the destination MEC equipment IP and the port number of the destination MEC equipment IP in the split-flow opening command included in S111, and after the response is successful, the MEC equipment executes S112: and sending a response success message to the network management equipment. The process of automatic configuration of the shunt strategy is completed, and the data of the user can flow into the target MEC equipment through the gateway, so that the data of the user does not need to flow into the core network completely, and the requirements of reducing time delay and optimizing flow are met.

According to the gateway shunting method provided by the embodiment of the invention, when the IP of MEC equipment is received, the timer is started to start timing, and when the timing duration of the timer exceeds the first preset duration, the IP is invalidated, so that the problem of ping-pong effect in the shunting strategy automatic configuration process is solved, the shunting strategy automatic configuration process without ping-pong effect is realized, and the service continuity of a high-reliability application scene and the requirements of an operator bound edge computing platform are ensured.

Fig. 3 is an interactive schematic diagram of another gateway offloading method according to an embodiment of the present invention. As shown in fig. 3, the method may also be based on three execution bodies, including a network management device, a gateway, and an MEC device.

As shown in fig. 3, the gateway offloading method may include:

s201: and when the gateway does not receive the information sent by the MEC equipment within the second preset time, generating an MEC equipment offline message, and starting a timer to start timing.

Because the MEC device and the gateway need to be configured before receiving the MEC device offline message, the MEC device can report heartbeat information to the gateway and the gateway can report the MEC device offline message to the network management device. Fig. 4 is an interactive schematic diagram of a method for configuring a gateway and an MEC device according to an embodiment of the present invention.

Because it is possible for the MEC device to be altered to manage IP invariance, a verification method that is owned by only the device is needed. Thus, as shown in fig. 4, the network management device may perform S302: the sub-certificate is sent to the MEC device. So that the configuration sub-certificate in the MEC device will always follow the MEC device unchanged.

Once the MEC device configured with the sub-certificate is online, the MEC device performs S303: and sending the MEC equipment online message to the network management equipment. After that, the network management device performs S304: and authenticating the sub-certificate carried by the MEC equipment online message and the field in the table 1. Therefore, after the equipment reconnection, the network management equipment can judge whether the original MEC equipment is or not through the sub-certificate carried in the MEC equipment online message. Only after passing the authentication, the network management device can configure the gateway with an open split command, and the field of the open split command is shown in table 7.

After the MEC device passes the authentication, in order to enable the MEC device to report the heartbeat message to the gateway in a preset manner, the gateway may execute S305: and sending information comprising a heartbeat message reporting mode to MEC equipment. And the MEC equipment configures the heartbeat message reporting mode according to the information of the heartbeat message reporting mode included in the S305 so that the MEC equipment can report the heartbeat message to the gateway according to a preset rule. The configuration information is shown in table 8.

TABLE 8

Field identification	Field name	Description of values
			Period	Cycle time	Reporting period

After the MEC device is successfully configured according to the heartbeat message reporting mode message included in S305, the MEC device may execute S306: and sending a configuration success message to the gateway.

In order to enable the gateway to report the MEC device heartbeat message to the network management device according to the preset rule, the network management device may execute S307 again: and sending a message including a mode of reporting the heartbeat message of the MEC equipment to the gateway. The fields included in the message of the MEC device heartbeat message format are shown in table 9. According to the information in table 9, if the gateway cannot detect the MEC heartbeat message for a period of time T2, the Event field will take the value down and trigger reporting. Wherein T2 may also be referred to as a second preset time period.

It should be noted that, the gateway is configured according to the information in table 9, so that the gateway can report to the network management device only when the MEC device is offline, and thus, the network management device does not need to receive the heartbeat message of each MEC device, and can sense the state of the MEC device more clearly and efficiently.

TABLE 9

After the gateway is successfully configured according to the message included in S307 and reporting the heartbeat message manner of the MEC device, the gateway executes S308: and sending a configuration success message to the network management equipment.

Because the MEC device configures the heartbeat message reporting manner shown in table 8 according to the heartbeat message reporting manner included in S305, the MEC device performs S309 in a periodic manner: and reporting the heartbeat to the gateway. The fields included in the reported heartbeat may be as shown in table 10.

Table 10

After the gateway receives the heartbeat message of the MEC device, the gateway performs S310: and sending a message that the heartbeat message is successfully received to the MEC equipment so that the MEC equipment receives the feedback.

The interactive schematic diagram of the method for configuring the gateway and the MEC device shown in fig. 4 implements that the MEC device reports the heartbeat message to the gateway according to a preset period by configuring the heartbeat reporting period for the MEC device and configuring the heartbeat message reporting mode for the gateway, and reports the device offline message to the network management device when the MEC heartbeat message cannot be detected in the time of the gateway T2.

After the gateway and MEC devices are configured using the method shown in fig. 4, the subsequent interaction is as shown in fig. 3.

As shown in S201 in fig. 3, when the gateway does not receive the information sent by the MEC device within the second preset time period, the MEC device off-line message is generated, and the message reporting timer is started to start timing.

Because the reporting of the heartbeat to the gateway will cease once the MEC device is replaced or taken off line, the gateway will not be able to detect the heartbeat message of the MEC device. If the gateway is at T ₂ If the heartbeat message of the MEC equipment cannot be detected, generating an offline message of the MEC equipment and triggering a message report timer of the gateway to start timing. The fields associated with the message report timer are shown in table 12.

TABLE 11

As shown in table 11, the timer effective period T3 may be specified, and T3 may also be referred to as a third preset time period. After that, the gateway performs S202: if the MEC equipment offline message is sent to the network management equipment in the T3, the message reporting timer stops timing.

If the timing duration of the message reporting timer exceeds T3, the gateway can invalidate the generated MEC equipment offline message. And the MEC equipment offline message is not reported to the network management equipment.

Therefore, the message report timer is used for invalidating the MEC equipment offline message exceeding the time length of T3, so that the gateway can receive the MEC equipment offline message again, and report the MEC equipment offline message to the network management equipment according to the latest MEC equipment offline message, thereby solving the ping-pong problem existing in the process of judging whether the MEC equipment is replaced or not.

As shown in S203 of fig. 3, when the network management device receives the MEC device offline message, the network management device starts a timer to start counting.

Wherein the timer may comprise an expiration of the split configuration timer.

Specifically, when receiving the MEC device offline message, the network management device triggers the termination shunt configuration timer to start timing. The fields associated with terminating the split configuration timer are shown in table 12.

Table 12 management platform terminates the split time window field

As further shown in S204 in fig. 3, if the management platform sends a termination shunt command to the gateway during the valid period T4 counted by the termination shunt configuration timer, the termination shunt configuration timer counts zero. The fields included in the termination and splitting command are shown in table 13, and the gateway can accurately perform termination and splitting operation on the destination MEC device through the destination MEC device IP and the port number of the destination MEC device IP included in table 13.

And if the timing duration of the termination shunt configuration timer exceeds T4, invalidating the received MEC equipment offline message. In the method shown in fig. 3, T4 may also be referred to as a first preset time period.

TABLE 13

After successful execution of the termination forking message included in S204, the gateway generates a message that the configuration termination forking command was successful. The gateway then performs S205: and sending a message of successful configuration termination and distribution command to the network management equipment. And completing the process that the network management equipment configures the termination shunt command to the gateway according to the received MEC equipment offline message.

Therefore, by using the termination shunt configuration timer to count time and invalidating the MEC equipment offline message exceeding the time length T4, the network management equipment can receive the MEC equipment offline message again, and the termination shunt command can be configured according to the latest MEC equipment offline message, so that the ping-pong effect existing in the process of configuring the termination shunt command of the network management equipment is solved, and the shunt strategy automatic configuration process without the ping-pong effect is realized.

According to the gateway shunting method provided by the embodiment of the invention, the timer is started to start timing according to the acquired Internet Protocol (IP) address of MEC equipment or the MEC equipment offline message, and the IP or MEC equipment offline message is invalidated when the timing duration of the timer exceeds the first preset duration, so that the problem of ping-pong effect in the shunting strategy automatic configuration process is solved, the shunting strategy automatic configuration process without ping-pong effect is realized, and the service continuity of a high-reliability application scene and the requirement of an operator for binding an edge computing platform are ensured.

Fig. 5 is a network management device according to an embodiment of the present invention. As shown in fig. 5, the network management device may include: a starting module 401, a processing module 402 and a transmitting module 403.

The starting module 401 may be configured to start a timer to start counting when receiving an internet protocol address IP of the multi-access edge computing MEC device or an MEC device offline message.

The processing module 402 may be configured to invalidate the IP or the MEC device offline message when a time duration of the timer exceeds a first preset time duration.

The processing module 402 may be further configured to generate a first offloading policy according to the IP, or generate a termination offloading message according to the MEC device offline message.

And in the first preset duration, if the first shunting strategy is sent to the gateway, stopping timing by the timer, or in the first preset duration, if the shunting termination message is sent to the gateway, stopping timing by the timer.

The first offload policy includes a DNS resolution policy, a second offload policy, and an offload bandwidth policy.

The DNS resolution strategy comprises a domain name and MEC equipment IP corresponding to the domain name.

The second bypass policy includes a destination MEC device IP and port number.

The sending module 403 may be configured to send a split opening instruction to the gateway when the gateway is configured successfully according to the first splitting policy, where the split opening instruction includes a destination MEC device IP and a port number of the destination MEC device IP, and the split opening instruction is used for the gateway to split data to the destination MEC device.

It can be understood that each module in the network management device shown in fig. 5 has a function of implementing each step on the network management device side in fig. 2 and 3, and can achieve the corresponding technical effects, which are not described herein for brevity.

According to the network management equipment provided by the embodiment of the invention, the timer is started to start timing according to the acquired Internet Protocol (IP) address of the MEC equipment or the MEC equipment offline message, and the IP or MEC equipment offline message is invalidated when the timing duration of the timer exceeds the first preset duration, so that the ping-pong effect problem existing in the automatic configuration process of the shunting strategy is solved, the automatic configuration process of the shunting strategy without ping-pong effect is realized, and the service continuity of a high-reliability application scene and the requirement of an operator for binding an edge computing platform are ensured.

Fig. 6 is a gateway according to an embodiment of the present invention. As shown in fig. 6, the gateway may include: a module 501 is started and a module 502 is processed.

The starting module 501 is configured to generate an MEC device offline message when the information sent by the MEC device is not received within the second preset duration, and start a timer to start timing.

And the processing module 502 is configured to invalidate the MEC device offline message when the timing duration of the timer exceeds a third preset duration.

The processing module 502 may be further configured to stop counting if the MEC device offline message is sent to the network management device within a third preset duration, where the MEC device offline message is used for the network management device to send a termination and diversion message to the gateway.

It can be understood that each module in the gateway shown in fig. 6 has a function of implementing each step on the gateway side in fig. 3, and can achieve the corresponding technical effects, which are not described herein for brevity.

According to the gateway provided by the embodiment of the invention, the MEC equipment offline message is generated when the information sent by the MEC equipment is not received within the second preset time period, the timer is started to start timing, and the MEC equipment offline message is invalidated when the timing time period of the timer exceeds the third preset time period, so that the problem of ping-pong effect in the automatic configuration process of the shunting strategy is solved, the automatic configuration process of the shunting strategy without ping-pong effect is realized, and the service continuity of a high-reliability application scene and the requirements of an operator bound edge computing platform are ensured.

Fig. 7 is a block diagram of a hardware architecture of a computing device according to an embodiment of the present invention. As shown in fig. 7, computing device 600 includes an input device 601, an input interface 602, a central processor 603, a memory 604, an output interface 605, and an output device 606. The input interface 602, the central processor 603, the memory 604, and the output interface 605 are connected to each other through a bus 610, and the input device 601 and the output device 606 are connected to the bus 610 through the input interface 602 and the output interface 605, respectively, and further connected to other components of the computing device 600.

Specifically, the input device 601 receives input information from the outside and transmits the input information to the central processor 603 through the input interface 602; the central processor 603 processes the input information based on computer executable instructions stored in the memory 604 to generate output information, temporarily or permanently stores the output information in the memory 604, and then transmits the output information to the output device 606 through the output interface 605; output device 606 outputs the output information to the outside of computing device 600 for use by a user.

That is, the computing device shown in fig. 7 may also be implemented as a gateway-forking device, which may include: a memory storing computer-executable instructions; and a processor, which when executing the computer executable instructions, can implement the gateway offloading method provided by the embodiment of the present invention.

Embodiments of the present invention also provide a computer readable storage medium having computer program instructions stored thereon; the computer program instructions, when executed by the processor, implement the gateway offloading method provided by the embodiments of the present invention.

It should be understood that the invention is not limited to the particular arrangements and instrumentality described above and shown in the drawings. For the sake of brevity, a detailed description of known methods is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present invention are not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between steps, after appreciating the spirit of the present invention.

The functional blocks shown in the above-described structural block diagrams may be implemented in hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic circuit, an Application Specific Integrated Circuit (ASIC), suitable firmware, a plug-in, a function card, or the like. When implemented in software, the elements of the invention are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine readable medium or transmitted over transmission media or communication links by a data signal carried in a carrier wave. A "machine-readable medium" may include any medium that can store or transfer information. Examples of machine-readable media include electronic circuitry, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio Frequency (RF) links, and the like. The code segments may be downloaded via computer networks such as the internet, intranets, etc.

It should also be noted that the exemplary embodiments mentioned in this disclosure describe some methods or systems based on a series of steps or devices. However, the present invention is not limited to the order of the above-described steps, that is, the steps may be performed in the order mentioned in the embodiments, or may be performed in a different order from the order in the embodiments, or several steps may be performed simultaneously.

Aspects of the present disclosure are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of 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, 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, enable the implementation of the functions/acts specified in the flowchart and/or block diagram block or blocks. Such a processor may be, but is not limited to being, a general purpose processor, a special purpose processor, an application specific processor, or a field programmable logic circuit. It will also be understood that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware which performs the specified functions or acts, or combinations of special purpose hardware and computer instructions.

In the foregoing, only the specific embodiments of the present invention are described, and it will be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the systems, modules and units described above may refer to the corresponding processes in the foregoing method embodiments, which are not repeated herein. It should be understood that the scope of the present invention is not limited thereto, and any equivalent modifications or substitutions can be easily made by those skilled in the art within the technical scope of the present invention, and they should be included in the scope of the present invention.

Claims

1. A method for gateway offloading, the method being applied to a network management device, the method comprising:

starting a timer to start timing when receiving an Internet Protocol (IP) address of the multi-access edge computing MEC device or an MEC device offline message; when the timing duration of the timer exceeds a first preset duration, the IP or MEC equipment offline message is invalidated;

generating a first shunting strategy according to the IP;

if the first shunting strategy is sent to the gateway within a first preset duration, stopping timing by the timer; or alternatively, the process may be performed,

if the termination shunt message is sent to the gateway within a first preset duration, stopping timing by the timer; and when the gateway is successfully configured according to the first distribution strategy, sending a distribution opening instruction to the gateway, wherein the distribution opening instruction comprises a destination MEC device IP and a port number of the destination MEC device IP, and the distribution opening instruction is used for the gateway to distribute data to the destination MEC device.

2. The method of claim 1, wherein the first offload policy comprises a DNS resolution policy, a second offload policy, and an offload bandwidth policy;

3. A method of gateway offloading, applied to a gateway, the method comprising: receiving a first shunting strategy sent by network management equipment;

configuring a first shunting strategy, and after successful configuration, sending a configuration success message to network management equipment;

in response to receiving a split starting command sent by the network management equipment, sending information comprising a heartbeat message reporting mode to the MEC equipment, so that the MEC equipment configures the heartbeat message reporting mode according to the information of the heartbeat message reporting mode and can report the heartbeat message according to a preset rule;

receiving a configuration success message sent by MEC equipment;

responding to the received message which is sent by the network management equipment and comprises a mode of reporting the heartbeat message of the MEC equipment, and sending a configuration success message to the network management equipment;

after receiving the heartbeat message of the MEC equipment, sending a message of success in receiving the heartbeat message to the MEC equipment so as to enable the MEC equipment to receive feedback;

when the information sent by the MEC equipment is not received within the second preset time length, generating an MEC equipment offline message, and starting a timer to start timing; and when the timing duration of the timer exceeds a third preset duration, invalidating the MEC equipment offline message.

4. A method according to claim 3, characterized in that the method comprises:

and in a third preset duration, if the MEC equipment offline message is sent to the network management equipment, stopping timing by the timer, wherein the MEC equipment offline message is used for the network management equipment to send a termination and shunt message to the gateway.

5. A network management device, characterized in that the network management device comprises:

the processing module is used for invalidating the IP or MEC equipment offline message when the timing duration of the timer exceeds a first preset duration;

the processing module is further used for generating a first shunting strategy according to the IP;

the processing module is further used for generating a termination shunt message according to the MEC equipment offline message;

if the termination shunt message is sent to the gateway within a first preset duration, stopping timing by the timer;

And the sending module is used for sending a shunt opening instruction to the gateway when the gateway is configured successfully according to the first shunt strategy, wherein the shunt opening instruction comprises a destination MEC device IP and a port number of the destination MEC device IP, and the shunt opening instruction is used for the gateway to shunt data to the destination MEC device.

6. The network management device of claim 5, wherein the first offload policy comprises a DNS resolution policy, a second offload policy, and an offload bandwidth policy;

7. A gateway, the gateway comprising:

the receiving module is used for receiving a first shunting strategy sent by the network management equipment;

the sending module is used for responding to the split starting command sent by the network management equipment and sending information comprising a heartbeat message reporting mode to the MEC equipment, so that the MEC equipment configures the heartbeat message reporting mode according to the information of the heartbeat message reporting mode and can report the heartbeat message according to a preset rule;

The receiving module is also used for receiving a configuration success message sent by the MEC equipment;

the sending module is also used for sending a configuration success message to the network management equipment in response to receiving the message which is sent by the network management equipment and comprises a mode of reporting the heartbeat message of the MEC equipment;

the sending module is further used for sending a message of successful heartbeat message receiving to the MEC equipment after receiving the heartbeat message of the MEC equipment so that the MEC equipment receives feedback;

8. The gateway of claim 7, wherein the gateway is configured to,

and the processing module is further configured to stop timing if the MEC device offline message is sent to the network management device within a third preset duration, where the MEC device offline message is used for the network management device to send a termination and diversion message to the gateway.

9. An electronic device, the device comprising: a processor and a memory storing computer program instructions;

The processor, when executing the computer program instructions, implements the gateway offloading method according to any one of claims 1-2, or implements the gateway offloading method according to any one of claims 3-4.

10. A computer storage medium having stored thereon computer program instructions which, when executed by a processor, implement the gateway offloading method of any one of claims 1-2 or the gateway offloading method of any one of claims 3-4.