CN110557785B - Data distribution method and device based on MEC - Google Patents

Data distribution method and device based on MEC Download PDF

Info

Publication number
CN110557785B
CN110557785B CN201810540800.0A CN201810540800A CN110557785B CN 110557785 B CN110557785 B CN 110557785B CN 201810540800 A CN201810540800 A CN 201810540800A CN 110557785 B CN110557785 B CN 110557785B
Authority
CN
China
Prior art keywords
message
nas
address
iot
iot terminal
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201810540800.0A
Other languages
Chinese (zh)
Other versions
CN110557785A (en
Inventor
段江海
丁国栋
张海波
郭俊利
习建德
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Datang Mobile Communications Equipment Co Ltd
Original Assignee
Datang Mobile Communications Equipment Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Datang Mobile Communications Equipment Co Ltd filed Critical Datang Mobile Communications Equipment Co Ltd
Priority to CN201810540800.0A priority Critical patent/CN110557785B/en
Publication of CN110557785A publication Critical patent/CN110557785A/en
Application granted granted Critical
Publication of CN110557785B publication Critical patent/CN110557785B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/12Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/10Flow control between communication endpoints

Abstract

The application discloses a data distribution method and device based on MEC. In the method, an MEC device monitors an S1AP message interacted between a base station and a core network device, wherein the S1AP message carries NAS PDU interacted between an NB-IoT terminal and the core network device; the MEC equipment judges whether the NAS PDU contains an NAS message container or not; if so, obtaining the data message contained in the NAS message container, and sending the data message to a local IoT service server, otherwise, sending the S1AP message to core network equipment. By adopting the method and the device, the MEC-based data distribution can be realized for the NB-IoT system.

Description

Data distribution method and device based on MEC
Technical Field
The present invention relates to the field of wireless communication technologies, and in particular, to a data distribution method and device based on Mobile Edge Computing (MEC).
Background
An Internet of things (IoT) system based on a mobile communication network is mainly composed of an IoT terminal, a mobile communication network, and an IoT service platform (also called an IoT service system or an IoT service server), wherein the mobile communication network mainly includes a base station and a core network. The IoT service platform is deployed on the upper layer of the core network and is used for managing and controlling the IoT terminal and providing the application service of the Internet of things. The system architecture is shown in fig. 1.
With the introduction of mobile edge computing technology, computing (such as IoT service processing), network, and storage capabilities in the cloud extend and expand to the edge, and data processing and application analysis are distributed to network edge devices. Edge computing internet of things (EC-IoT) systems have emerged.
In an EC-IoT system, an IoT service platform is deployed locally near the mobile edge side, as shown in fig. 2. Compared with fig. 1, a Mobile Edge Computing (MEC) device is added between a base station and a core network device, the MEC device is deployed at the same network level (near the mobile edge) as the base station and an IoT service platform, and the core network is deployed at a higher network level (such as a core room). The MEC device supports a local Traffic Offload Function (TOF). IoT service data sent by the IoT terminal is transmitted to the MEC equipment through the base station, and then is shunted to the IoT service platform by the MEC equipment.
Currently, based on the EC-IoT system shown in fig. 2, the local traffic offloading process includes: the MEC device monitors Control Plane (CP) signaling and service plane (UP) data messages between a base station and a core network, acquires a corresponding relation between a terminal IP address and GPRS tunneling protocol (GTP-U) tunnel information of a terminal through monitoring the control plane signaling, and sends received uplink user plane data messages to a local IoT service platform on one hand and puts received downlink data messages into a GTP-U tunnel distributed for the terminal according to the terminal IP address to be forwarded to a service base station of the terminal on the other hand through monitoring the service plane data messages.
To meet the cellular data connection requirements of low power devices in wide area networks, a narrowband internet of things (NB-IoT) system has been developed. The NB-IoT system is optimized for small data transmission, and instead of establishing a GTP-U tunnel to transmit a data packet in a user plane, encapsulates the data packet into a non-access stratum (NAS) Protocol Data Unit (PDU), and carries the NAS PDU through an S1application protocol (S1application protocol, S1-AP) message of a control plane. Therefore, according to the prior art, the MEC device cannot realize the local service distribution function for the NB-IoT system, and further cannot construct an edge computing internet of things system.
Disclosure of Invention
The embodiment of the application provides a data distribution method and device based on MEC, which are used for realizing the data distribution based on MEC aiming at an NB-IoT system.
In a first aspect, a method for data offloading based on MEC is provided, where the method includes: the MEC equipment monitors an S1AP message interacted between a base station and core network equipment, wherein the S1AP message carries NAS PDU interacted between an NB-IoT terminal and the core network equipment; the MEC equipment judges whether the NAS PDU contains an NAS message container or not; if so, obtaining the data message contained in the NAS message container, and sending the data message to a local IoT service server, otherwise, sending the S1AP message to core network equipment.
According to the scheme, aiming at the characteristic that IoT service data in an NB-IoT system is borne in NAS PDU and is sent through an S1AP message, MEC equipment monitors S1AP messages interacted between a base station and core network equipment, judges whether NAS PDU borne by the monitored S1AP messages contains an NAS message container or not, if yes, the fact that the messages contain data messages needing to be processed by a local IoT service server is indicated, and therefore the data messages are sent to the local IoT service server, and if not, the S1AP messages are sent to the core network equipment, so that data distribution based on MEC is achieved for the NB-IoT system.
Optionally, if the MEC device determines that the NAS PDU includes a NAS message container, the method further includes: the MEC device establishes a corresponding relationship between the identity of the NB-IoT terminal and address information in the NAS message container.
According to the above scheme, if the MEC device determines that the NAS PDU includes the NAS message container, it indicates that the message includes the data packet that needs to be processed by the local IoT service server, so that the corresponding relationship between the NB-IoT terminal identifier and the address information in the NAS message container is established for routing the IoT service data packet.
Optionally, the address information in the NAS message container includes: the source IP address is the IP address of the NB-IoT terminal, and the destination IP address is a local IoT service IP address.
Optionally, the method further comprises: the MEC equipment receives a data message sent to the NB-IoT terminal by the local IoT service server, wherein the data message comprises an IP address of the NB-IoT terminal; the MEC equipment queries corresponding relation information between NB-IoT terminal identification and address information according to the IP address of the NB-IoT terminal contained in the data message to obtain the identification of the NB-IoT terminal; and the MEC equipment encapsulates the data message into an NAS message container according to the IP address of the NB-IoT terminal and the IP address of the local IoT service server, encapsulates the NAS message container into an NAS PDU (protocol data Unit), encapsulates the NAS PDU into an S1AP message according to the identifier of the NB-IoT terminal, and sends the S1AP message to a service base station of the NB-IoT terminal.
According to the above scheme, after receiving the data packet sent to the NB-IoT terminal by the local IoT service server, the MEC device may encapsulate and route the data packet according to the previously established correspondence information between the NB-IoT terminal identifier and the address information, so as to send the data packet to the NB-IoT terminal, thereby realizing distribution of downlink service data.
In a second aspect, there is provided a mobile edge computing MEC apparatus comprising: a monitoring module, configured to monitor an S1AP message exchanged between a base station and a core network device, where the S1AP message carries an NAS PDU exchanged between an NB-IoT terminal and the core network device; the judging module is used for judging whether the NAS PDU contains an NAS message container or not; and the shunting module is used for acquiring the data message contained in the NAS message container and sending the data message to a local IoT service server when the judgment module judges that the NAS message container is positive, and otherwise, sending the S1AP message to core network equipment.
Optionally, the method further comprises: a corresponding relationship establishing module, configured to establish a corresponding relationship between the NB-IoT terminal identifier and the address information in the NAS message container when the determining module determines that the NAS PDU includes the NAS message container.
Optionally, the address information in the NAS message container includes: the source IP address is the IP address of the NB-IoT terminal, and the destination IP address is a local IoT service IP address.
Optionally, the system further comprises a forwarding module, configured to: receiving a data message sent by the local IoT service server to the NB-IoT terminal, wherein the data message comprises an IP address of the NB-IoT terminal; inquiring corresponding relation information between NB-IoT terminal identification and address information according to the IP address of the NB-IoT terminal contained in the data message to obtain the identification of the NB-IoT terminal; and according to the IP address of the NB-IoT terminal and the IP address of the local IoT service server, encapsulating the data message into an NAS message container, encapsulating the NAS message container into an NAS PDU, according to the identifier of the NB-IoT terminal, encapsulating the NAS PDU into an S1AP message, and sending the S1AP message to a service base station of the NB-IoT terminal.
In a third aspect, a communication apparatus is provided, including: the system comprises a processor and a memory, wherein the processor and the memory are connected through a bus; the processor is configured to read a program in the memory and execute the method of any of the first aspect.
In a fourth aspect, there is provided a computer-readable storage medium having stored thereon computer-executable instructions for causing the computer to perform the method of any of the first aspects above.
Drawings
Fig. 1 is a schematic diagram of a system architecture of an internet of things based on a mobile communication network in the prior art;
FIG. 2 is a schematic diagram of a prior art architecture of an edge computing IOT system based on a mobile communication network;
fig. 3 is one of schematic flow diagrams of a data offloading method based on MEC according to an embodiment of the present disclosure;
fig. 4 is a schematic diagram of an NB-IoT system data transmission structure in the embodiment of the present application;
fig. 5 is a second schematic flowchart of a MEC-based data offloading method according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of an MEC apparatus provided in an embodiment of the present application;
fig. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application.
Detailed Description
The embodiment of the application provides a data distribution method and device based on MEC. The embodiments of the present application will be described in detail below with reference to the accompanying drawings.
The data distribution method provided by the embodiment of the application can be applied to an edge computing internet of things system architecture as shown in fig. 2. The core network device in the architecture may be a cellular IoT serving gateway node (C-SGN) or a Mobility Management Entity (MME) device, and the like, which is not limited in this embodiment of the present invention.
Referring to fig. 3, a schematic flow chart of the MEC-based data offloading method provided in the embodiment of the present application is shown, where as shown in the drawing, the flow chart may include:
s301: the MEC equipment monitors an S1application protocol (S1application protocol, S1AP) message between the base station and the core network equipment, and the S1AP message carries NAS PDU interacted between the NB-IoT terminal and the core network equipment.
After the NB-Iot terminal is accessed to the mobile communication network, the NB-Iot terminal can communicate with the core network side. The communication between the base station and the core network equipment follows the S1AP protocol, that is, the interactive message between the base station and the core network equipment is the S1AP message. The S1AP message carries NAS PDUs exchanged between the NB-IoT terminal and the core network device.
In this embodiment, the MEC device has a message monitoring function, and may monitor an S1AP message exchanged between the base station and the core network device. In this flow, an example that the MEC device monitors an S1AP message sent by the base station to the core network device is described, where the S1AP message carries NAS PDUs sent by the NB-IoT terminal.
Fig. 4 exemplarily illustrates an NB-IoT system data transmission structure. As shown in fig. 4, the S1AP message includes NAS PDUs, and the NAS PDUs include NAS PDU headers and NAS message containers. The NAS message container includes an IP header portion (source IP address, destination IP address) and a payload portion.
The S1AP message also carries an IoT terminal identity. The IoT terminal identity may be included in section S1AP in fig. 4. The IoT terminal identifier may be S1AP ID, and the like, which is not limited in this embodiment.
Wherein the NAS message container is an optional component. Whether the NAS PDU includes the NAS message container may be determined by the NAS PDU type.
For example, the NAS PDU may comprise the type shown in table 1 according to the control plane service request message content of the bearer.
Table 1: CONTROL plane service REQUEST message content (CONTROL PLANE SERVICE REQUEST message content)
Figure BDA0001678763820000061
"NAS Message container" is used as an optional information element, and when the Message Type is "Control plane service request Message identity" in table 1, the information element may appear optionally. When the IEI (Information Element Identity) value is 67, "NAS message container" appears.
For another example, the NAS PDU may include the type shown in table 2 according to the content of the uplink NAS transport message carried.
Table 2: upstream NAS TRANSPORT message content (UPLINK NAS TRANSPORT message content)
Figure BDA0001678763820000071
"NAS Message container" is used as an optional information element, and when the Message Type is "Uplink NAS transport Message identity" in table 2, the information element is a mandatory one.
In specific implementation, as an example, if an NB-IoT terminal has service data to send to an IoT service platform, the terminal uses the IoT service data packet as a payload, encapsulates the source IP address and the destination IP address, encodes the encapsulated source IP address and destination IP address to form an NAS message container, loads the NAS message container in an NASPDU and sends the NASPDU to the serving base station, and then loads the NASPDU in an S1AP message by the base station and sends the message to the core network device.
S302: the MEC equipment judges whether the NAS PDU contains an NAS message container or not; if yes, the process proceeds to S303, otherwise, the process proceeds to S304.
In this embodiment of the present application, the MEC device is deployed with an S1AP protocol stack and an NAS protocol stack, and may parse the monitored S1AP message and parse the NAS PDU carried in the S1AP message.
In this step, the MEC device parses the monitored S1AP message, obtains the IoT terminal identifier carried in the S1AP message and the NAS PDU carried in the S1AP message, and further parses the NAS PDU. Analyzing the NAS PDU, if the NAS PDU is judged to contain an NAS message container, indicating that the NAS PDU contains a data message which needs to be processed by a local IoT service platform, and then switching to S303, and sending the data message to the local IoT service platform for processing through S303; if the NAS PDU does not contain the NAS message container, it indicates that the NAS PDU does not contain the data packet that needs to be processed by the local IoT service platform, and the S1AP message needs to be processed by the core network device, so that through S304, the S1AP message is sent to the core network device for further processing.
S303: the MEC device sends the data message carried in the NAS message container to the local IoT service platform.
In this step, the MEC device may extract a data packet sent by the IoT terminal from the NAS PDU (the data packet exists in the NAS PDU as a payload of a NAS container message), and send the data packet to the local IoT service platform.
Further, the MEC device may also establish a correspondence between the identity of the NB-IoT terminal and the address information in the NAS message container. Alternatively, if the same correspondence has been established, this step may be omitted. The correspondence may appear as the context of the IoT terminal.
Specifically, the MEC device may resolve IP address information in the NAS message container to obtain a source IP address (an IP address of an IoT terminal) and a destination IP address (an IoT service IP address), and may further resolve information, such as an IoT terminal identifier, included in the S1AP message, and according to the information, the MEC device may establish a context of the IoT terminal. The IoT terminal context may be used to route IoT traffic data packets.
Optionally, the address information in the NAS message container includes a source IP address and a destination IP address, where the source IP address is an IP address of the IoT terminal, and the destination IP address is a local IoT service IP address (that is, a local service platform IP address). Accordingly, the MEC device may parse the NAS message container to obtain the IP address of the IoT terminal and the local IoT service IP address, and establish the context of the IoT terminal according to the IP address of the IoT terminal and the local IoT service IP address, and the parsed identifier of the IoT terminal.
In S303, the MEC device may send the data message in the NAS message container as the payload to the local IoT service platform according to the destination IP address (i.e., the local IoT service IP address) in the NAS message container. As an example, the MEC device may send the data packet as the payload in the NAS message container to the local IoT service platform according to the IoT terminal context after establishing the IoT terminal context.
S304: the MEC device sends the S1AP message to the core network device.
After the MEC device shunts the IoT service data packet sent by the IoT terminal to the local IoT service platform in the manner described above, the local IoT service platform may process the IoT service data packet according to the packet and may further return the data packet to the IoT terminal, and the data packet may be sent to the IoT terminal through the MEC device. The process may be as shown in fig. 5, and may specifically include:
s501: and the MEC equipment receives the data message sent to the IoT terminal by the local IoT service platform. Wherein the data message carries the IP address of the IoT terminal.
S502: and the MEC equipment queries the NB-IoT terminal identification and the corresponding relation information between the address information according to the IP address of the IoT terminal carried in the data message to obtain the NB-IoT terminal identification.
In this step, as described in S303, the MEC device may create a context for the IoT terminal, where the context includes an identity of the IoT terminal, an IP address of the IoT terminal, and a local IoT service IP address. Therefore, the MEC device may query the terminal context according to the IP address of the IoT terminal carried in the data packet to obtain the identity of the IoT terminal corresponding to the IP address of the IoT terminal.
S503: and the MEC equipment encapsulates the data message into an NAS message container according to the IP address of the NB-IoT terminal and the local IoT service IP address, encapsulates the NAS message container into an NAS PDU, encapsulates the NAS PDU into an S1AP message according to the identification of the terminal, and sends the message to the service base station of the IoT terminal.
In this step, the MEC device may generate the NAS message container by using the data packet as a payload of the NAS message container and using the local IoT service IP address and the IP address of the NB-IoT terminal as address information. The source address is a local IoT service IP address, and the destination address is an IP address of the IoT terminal. The MEC device encapsulates the NAS message container and NAS PDU header into a NAS PDU. The structure of the NAS PDU may be as shown in fig. 3. Further, the MEC device encapsulates the NAS PDU into an S1AP message according to the identity of the IoT terminal, and sends the message to the serving base station of the IoT terminal.
In some embodiments, for security reasons, NAS protocols between IoT terminals and the core network may initiate ciphering and/or integrity protection algorithms.
In this embodiment of the application, since the MEC device needs to analyze the NAS protocol and to add a data packet or extract a data packet in the NAS PDU, the NAS interaction process between the IoT terminal and the core network uses null computation, that is, the Encryption Algorithm uses EEA0(EPS Encryption Algorithm 0), and the Integrity protection Algorithm uses EIA0(EPS Integrity Algorithm 0, EPS Integrity protection Algorithm 0).
Wherein security is implemented at an Access Stratum (AS).
If the NAS protocol between the IoT terminal and the core network starts the encryption algorithm EEA0, in S302, the MEC device does not perform decryption processing after listening to the S1AP message. In S503, the MEC device does not encrypt the S1AP message.
If the NAS protocol between the IoT terminal and the core network starts the integrity protection algorithm EIA0, in S302, the MEC device does not perform integrity protection verification after listening to the S1AP message. In S503, the MEC device does not integrity protect the S1AP message.
As can be seen from the above description, in the embodiment of the present application, for the problem that MEC local offloading cannot be implemented in an EC-IoT system at present, the MEC device monitors an S1AP message exchanged between a base station and a core network device, and determines whether a data packet to be processed by a local IoT service platform is carried in the S1AP message according to whether an NAS PDU in the S1AP message includes an NAS message container, so as to implement local offloading.
The local distribution of the IoT service is realized in the EC-IoT system, so that better real-time computing capability can be realized, and the high-delay service application requirements such as industrial Internet of things and Internet of vehicles can be met. Compared with the traditional IoT system, the method and the device for processing the IoT system have the advantages that the safety can be improved, the system congestion can be reduced, the cost can be reduced, and the like.
Based on the same technical concept, the embodiment of the present application further provides an MEC device, which can implement the data offloading process described in the foregoing embodiment.
Referring to fig. 6, a schematic structural diagram of an MEC apparatus provided in an embodiment of the present application is shown. The MEC apparatus may include: a monitoring module 601, a judging module 602, and a shunting module 603.
The monitoring module 601 is configured to monitor an S1AP message interacted between a base station and a core network device, where the S1AP message carries an NAS PDU interacted between an NB-IoT terminal and the core network device. The determining module 602 is configured to determine whether the NAS PDU includes a NAS message container. The offloading module 603 is configured to, when the determining module 602 determines that the NAS message container is the NAS message container, obtain a data packet included in the NAS message container, and send the data packet to a local IoT service server; otherwise, the S1AP message is sent to the core network device.
Optionally, the MEC device may further include a correspondence relationship establishing module 604. The correspondence establishing module 604 is configured to establish a correspondence between the identity of the NB-IoT terminal and the address information in the NAS message container when the determining module 602 determines that the NAS PDU includes the NAS message container.
Optionally, the address information in the NAS message container includes: the source IP address is the IP address of the NB-IoT terminal, and the destination IP address is a local IoT service IP address.
Optionally, the MEC apparatus may further include a forwarding module 605. The forwarding module 605 is configured to: receiving a data message sent by the local IoT service server to the NB-IoT terminal, wherein the data message comprises an IP address of the NB-IoT terminal; inquiring corresponding relation information between NB-IoT terminal identification and address information according to the IP address of the NB-IoT terminal contained in the data message to obtain the identification of the NB-IoT terminal; and according to the IP address of the NB-IoT terminal and the IP address of the local IoT service server, encapsulating the data message into a NAS message container, encapsulating the NAS message container into a NAS PDU, according to the identification of the IoT terminal, encapsulating the NAS PDU into an S1AP message, and sending the S1AP message to a service base station of the NB-IoT terminal.
Based on the same technical concept, the embodiment of the present application further provides a communication device, which can implement the data offloading function described in the foregoing embodiment.
Referring to fig. 7, a schematic structural diagram of a communication device provided in the embodiment of the present application is shown, where the communication device may include: a processor 701, a memory 702, a transceiver 703, and a bus interface.
The processor 701 is responsible for managing the bus architecture and general processing, and the memory 702 may store data used by the processor 701 in performing operations. The transceiver 703 is used for receiving and transmitting data under the control of the processor 701.
The bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 701, and various circuits, represented by memory 702, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The processor 701 is responsible for managing the bus architecture and general processing, and the memory 702 may store data used by the processor 701 in performing operations.
The process disclosed in the embodiments of the present invention may be applied to the processor 701, or implemented by the processor 701. In implementation, the steps of the signal processing flow may be implemented by integrated logic circuits of hardware or instructions in the form of software in the processor 701. The processor 701 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, discrete gate or transistor logic, discrete hardware components, or the like that may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present invention. A 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 invention may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 702, and the processor 701 reads the information in the memory 702 and completes the steps of the signal processing flow in combination with the hardware thereof.
Specifically, the processor 701 is configured to read a program in the memory 702 and execute: monitoring an S1AP message interacted between a base station and core network equipment, wherein the S1AP message carries NAS PDU interacted between an NB-IoT terminal and the core network equipment; the MEC equipment judges whether the NAS PDU contains an NAS message container or not; if so, acquiring a data message contained in the NAS message container, and sending the data message to a local IoT service server; otherwise, the S1AP message is sent to the core network device. The specific implementation process can be referred to the foregoing embodiments, and is not repeated here.
Based on the same technical concept, the embodiment of the application also provides a computer readable storage medium. The computer-readable storage medium stores computer-executable instructions for causing the computer to perform the processes performed by the foregoing embodiments.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims (10)

1. A data distribution method based on Mobile Edge Computing (MEC) is characterized by comprising the following steps:
the MEC equipment monitors an S1application protocol S1AP message interacted between the base station and the core network equipment, wherein the S1AP message carries a non-access stratum protocol data unit (NAS PDU) sent to the core network equipment by a narrowband Internet of things (NB-IoT) terminal;
the MEC equipment judges whether the NAS PDU contains an NAS message container or not;
if so, acquiring a data message contained in the NAS message container, and sending the data message to a local IoT service server; otherwise, the S1AP message is sent to the core network device.
2. The method of claim 1, wherein if the MEC device determines that the NAS PDU includes a NAS message container, the method further comprises:
the MEC device establishes a corresponding relationship between the identity of the NB-IoT terminal and address information in the NAS message container.
3. The method of claim 2, wherein the address information in the NAS message container comprises: the source IP address is the IP address of the NB-IoT terminal, and the destination IP address is a local IoT service IP address.
4. The method of any of claims 1 to 3, further comprising:
the MEC equipment receives a data message sent to the NB-IoT terminal by the local IoT service server, wherein the data message comprises an IP address of the NB-IoT terminal;
the MEC equipment queries corresponding relation information between NB-IoT terminal identification and address information according to the IP address of the NB-IoT terminal contained in the data message to obtain the identification of the NB-IoT terminal;
and the MEC equipment encapsulates the data message into an NAS message container according to the IP address of the NB-IoT terminal and the IP address of the local IoT service server, encapsulates the NAS message container into an NAS PDU (protocol data Unit), encapsulates the NAS PDU into an S1AP message according to the identifier of the NB-IoT terminal, and sends the S1AP message to a service base station of the NB-IoT terminal.
5. A mobile edge computing, MEC, apparatus comprising:
a monitoring module, configured to monitor an S1application protocol S1AP message interacted between a base station and a core network device, where the S1AP message carries a non-access stratum protocol data unit NAS PDU sent to the core network device by a narrowband internet of things NB-IoT terminal;
the judging module is used for judging whether the NAS PDU contains an NAS message container or not;
the flow distribution module is used for acquiring the data message contained in the NAS message container and sending the data message to a local IoT service server when the judgment module judges that the data message is contained in the NAS message container; otherwise, the S1AP message is sent to the core network device.
6. The apparatus of claim 5, further comprising:
a corresponding relationship establishing module, configured to establish a corresponding relationship between the NB-IoT terminal identifier and the address information in the NAS message container when the determining module determines that the NAS PDU includes the NAS message container.
7. The apparatus of claim 6, wherein the address information in the NAS message container comprises: the source IP address is the IP address of the NB-IoT terminal, and the destination IP address is a local IoT service IP address.
8. The apparatus of any of claims 5 to 7, further comprising a forwarding module to:
receiving a data message sent by the local IoT service server to the NB-IoT terminal, wherein the data message comprises an IP address of the NB-IoT terminal;
inquiring corresponding relation information between NB-IoT terminal identification and address information according to the IP address of the NB-IoT terminal contained in the data message to obtain the identification of the NB-IoT terminal;
and according to the IP address of the NB-IoT terminal and the IP address of the local IoT service server, encapsulating the data message into an NAS message container, encapsulating the NAS message container into an NAS PDU, according to the identifier of the NB-IoT terminal, encapsulating the NAS PDU into an S1AP message, and sending the S1AP message to a service base station of the NB-IoT terminal.
9. A data distribution device for calculating MEC based on moving edge, comprising: the system comprises a processor and a memory, wherein the processor and the memory are connected through a bus;
the processor is used for reading the program in the memory and executing:
monitoring an S1application protocol S1AP message interacted between a base station and core network equipment, wherein the S1AP message carries a non-access stratum protocol data unit (NAS PDU) sent to the core network equipment by a narrowband Internet of things (NB-IoT) terminal;
judging whether the NAS PDU contains an NAS message container or not;
if so, acquiring a data message contained in the NAS message container, and sending the data message to a local IoT service server; otherwise, the S1AP message is sent to the core network device.
10. The apparatus of claim 9, wherein the processor is further configured to:
and if the NAS PDU is judged to contain an NAS message container, establishing a corresponding relation between the identifier of the NB-IoT terminal and address information in the NAS message container.
CN201810540800.0A 2018-05-30 2018-05-30 Data distribution method and device based on MEC Active CN110557785B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810540800.0A CN110557785B (en) 2018-05-30 2018-05-30 Data distribution method and device based on MEC

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810540800.0A CN110557785B (en) 2018-05-30 2018-05-30 Data distribution method and device based on MEC

Publications (2)

Publication Number Publication Date
CN110557785A CN110557785A (en) 2019-12-10
CN110557785B true CN110557785B (en) 2021-02-02

Family

ID=68733844

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810540800.0A Active CN110557785B (en) 2018-05-30 2018-05-30 Data distribution method and device based on MEC

Country Status (1)

Country Link
CN (1) CN110557785B (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113873582B (en) * 2020-06-30 2023-03-28 华为技术有限公司 Mobile edge calculation processing method and related equipment
CN112019427B (en) * 2020-08-28 2021-09-03 浙江九州云信息科技有限公司 Wireless side edge gateway of mobile cellular network
CN114727291B (en) * 2022-03-31 2023-09-29 中国电信股份有限公司 Local shunting system, method, device, network equipment and storage medium
CN114980100B (en) * 2022-05-16 2023-11-14 中国电信股份有限公司 Service data distribution method and device, electronic equipment and storage medium
WO2024000412A1 (en) * 2022-06-30 2024-01-04 Oppo广东移动通信有限公司 Communication method and communication apparatus

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106488508A (en) * 2015-08-31 2017-03-08 大唐移动通信设备有限公司 A kind of data transmission method, apparatus and system
CN107172664A (en) * 2016-03-07 2017-09-15 大唐移动通信设备有限公司 Data transmission method, apparatus and system
EP3291605A1 (en) * 2015-04-28 2018-03-07 Nec Corporation Communication method, communication system, base station for mobile communication, and communication apparatus for wireless lan
CN107852637A (en) * 2015-08-07 2018-03-27 三星电子株式会社 Terminal and its communication means

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3291605A1 (en) * 2015-04-28 2018-03-07 Nec Corporation Communication method, communication system, base station for mobile communication, and communication apparatus for wireless lan
CN107852637A (en) * 2015-08-07 2018-03-27 三星电子株式会社 Terminal and its communication means
CN106488508A (en) * 2015-08-31 2017-03-08 大唐移动通信设备有限公司 A kind of data transmission method, apparatus and system
CN107172664A (en) * 2016-03-07 2017-09-15 大唐移动通信设备有限公司 Data transmission method, apparatus and system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
Draft Report of SA WG2 meetings #118;Secretary of SA WG2;《3GPP TSG_SA WG2 Meeting#118bis Docs S2-170002》;20170120;全文 *

Also Published As

Publication number Publication date
CN110557785A (en) 2019-12-10

Similar Documents

Publication Publication Date Title
CN110557785B (en) Data distribution method and device based on MEC
US8144593B2 (en) Method and apparatus for efficient routing in communication networks
US20200267007A1 (en) Efficient and dynamic support of mobile low latency services
CN109952781B (en) UE, network node and method for processing data packets
CN102972007B (en) Reduce the protocol overhead in monolithic grouping access procedure
CN106488508B (en) A kind of data transmission method, apparatus and system
CA3043470A1 (en) User plane model for non-3gpp access to fifth generation core network
CN105981470A (en) Methods and apparatuses for handling communication in a communication system comprising an access point and a wire line network node connected via wire line to the access point
WO2017147772A1 (en) Method of transmitting information and core network access apparatus
US9854051B2 (en) Using proxy devices as dynamic data relays
US10314090B2 (en) Access point management
CN105684381A (en) Apparatus and method for lawful interception
CN107333295B (en) Data distribution method and gateway
US20240089779A1 (en) Processing terminal device sensing data using a network function element
CN108616877B (en) Communication method, system and equipment of small base station
CN113473538A (en) Wireless convergence network-based shunt control method and system
CN112751871A (en) Data transmission method, device, network equipment and storage medium
CN111556530A (en) Data processing method and UPF unit
CN112910791B (en) Diversion system and method thereof
CN110719612A (en) Method and device for forwarding data
CN102821435A (en) Local routing method for establishing data route in segmented mode in WiMAX (wireless metropolitan area network) system
KR101472964B1 (en) Security system and security method for enterprise communication service using mobile communication network
CN114503625B (en) Communication method, device and system
CN116137718A (en) Communication method and device
CN108243082B (en) Data transmission method and equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant