CN111866950A

CN111866950A - Method and communication device for data transmission in MEC

Info

Publication number: CN111866950A
Application number: CN202010547334.6A
Authority: CN
Inventors: 施小龙; 陈方贵; 陈照甫
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-06-16
Filing date: 2020-06-16
Publication date: 2020-10-30
Anticipated expiration: 2040-06-16
Also published as: CN111866950B

Abstract

The application provides a method and a communication device for data transmission in an MEC, wherein the method comprises the following steps: sending first information to a core network element, wherein the first information comprises a cell identifier of a terminal device and an identifier of a first initiated application; receiving first response information sent by a core network element, wherein the first response information comprises DNAI corresponding to the cell identifier; sending a service request for requesting service data corresponding to the first application to a core network element, wherein the service request comprises the DNAI; and receiving second response information from the core network element, wherein the second response information comprises the identifiers of the MEC platform and the CDN nodes on the MEC platform corresponding to the DNAI and the positions of the terminal equipment. According to the method, before the user formally initiates the service access, the MEC platform which the user needs to access and the CDN edge node on the MEC platform are determined, so that the user communication failure caused by the distribution of the shunting strategy is avoided, the interruption of a communication link is avoided, and the user experience is improved.

Description

Method and communication device for data transmission in MEC

Technical Field

The present application relates to the field of communications, and in particular, to a method and a communication apparatus for data transmission in an MEC.

Background

Mobile Edge Computing (MEC) is a technology for deeply fusing an access network and internet services based on an evolution architecture of a 5rd generation (5G) system. The method deploys an Application Server (AS) and a function of resource scheduling and service processing of a mobile broadband (MBB) core network part to a network edge close to an access network, provides a computing environment at a position closer to a user (or a terminal device) at the rear side of a 5G base station, and supports a third-party service (for example, a Content Delivery Network (CDN) edge node) to be deployed on an MEC platform, so that the CDN is closer to the user, and faster download speed and lower access delay are provided.

Currently, a third-party service (e.g., CDN) deployed on the MEC implements an uplink classifier (UL CL) split-flow synchronization interface, and a third-party service scheduling system is docked with a core network element to dynamically determine whether a location of a terminal device has a region change, and update the UL CL after the location of the terminal device has changed. After the UL CL offload policy is completed, the established link between the terminal device and the service node deployed on the non-MEC may be broken and reconnected, which may cause interruption of data accessed by the user and affect user experience.

Disclosure of Invention

The application provides a method and a communication device for data transmission in an MEC (media over coax), which can realize synchronization of a shunting strategy, avoid user communication failure caused by distribution of the shunting strategy, avoid interruption of a communication link and improve user experience.

In a first aspect, a method for data transmission in an MEC is provided, where an execution subject of the method may be either a terminal device or a chip applied to the terminal device. The method comprises the following steps: the terminal equipment sends first information to a core network element, wherein the first information comprises: the cell identification of the terminal equipment and the identification of the first application initiated by the terminal equipment; the terminal equipment receives first response information from a core network element in response to the first information, wherein the first response information comprises: a data network access identifier DNAI corresponding to the cell identifier; the terminal equipment sends a service request to core network equipment, wherein the service request is used for requesting service data corresponding to the first application, and the service request comprises the DNAI; the terminal device receives second response information from the core network element in response to the service request, where the second response information includes: and calculating the identifier of the MEC platform and the identifier of the CDN node of the content delivery network on the MEC platform by the mobile edge corresponding to the DNAI and the position of the terminal equipment. The terminal device may access the CDN node on the MEC platform according to the identifier of the MEC platform and the identifier or the IP address of the CDN node on the MEC platform, and obtain service data corresponding to the first application from the CDN node.

In an MEC scenario, before a user starts a specific application, the method for transmitting data in an MEC first determines an MEC platform that the user needs to access and a CDN edge node on the MEC platform according to a offloading policy, and performs service access according to IP addresses of the MEC platform that the user needs to access and the CDN edge node on the MEC platform when the user formally initiates service access. Therefore, the synchronization of the shunting strategy is realized, the communication failure of the user caused by the distribution of the shunting strategy is avoided, the interruption of a communication link is avoided, and the user experience is improved.

Optionally, in this embodiment of the present application, the core network element may be: an MEC policy synchronization service network element, other core network elements, PCF, SMF or GSLB network element.

In a possible implementation manner of the first aspect, the method further includes: and the terminal equipment acquires the service data from the CDN node according to the identifier of the MEC platform and the identifier of the CDN node.

After the first application is finished, the method further comprises: the terminal device sends a first request to a core network device, where the first request is used to request to delete a offloading policy corresponding to the first application, the offloading policy includes offloading policies corresponding to a plurality of applications, and the offloading policy corresponding to the first application includes: the identifier of the first application, the identifier of the MEC platform accessed by the first application, and the identifier of the CDN node, where the first request includes: an identification of the first application and the DNAI.

For example, the offloading policy corresponding to the first application includes five-tuple information, where the five-tuple information is: the method comprises a client IP, a client port number, a server IP, a server port number and a protocol type, wherein the client can be understood as a first application program on the terminal equipment, and the server can be understood as a CDN edge node on an MEC platform for acquiring data of the first application program.

In a possible implementation manner of the first aspect, after determining that all applications accessing the MEC platform end, the first request is used to request to delete the offloading policy. In the implementation manner, when all the applications (all APPs) on the terminal device do not need to access resources on the corresponding MEC any more, the offloading policy is deleted from the UPF on the MEC, so that it is ensured that the subsequent traffic of other applications is not forwarded to the MEC any more, and the fact that the MEC resources are occupied by invalid traffic is avoided.

In a possible implementation manner of the first aspect, the service request is a hypertext transfer protocol HTTP request.

In a second aspect, a method for data transmission in an MEC is provided, where an execution subject of the method may be a core network element or a chip applied to the core network element. For example, the core network element may be: an MEC strategy synchronization service network element, other core network elements, PCF, SMF or GSLB network element, the method comprises: the core network element receives first information from the terminal equipment, wherein the first information comprises: the cell identification of the terminal equipment and the identification of the first application initiated by the terminal equipment; the core network element sends first response information responding to the first information to the terminal equipment, wherein the first response information comprises: a data network access identifier DNAI corresponding to the cell identifier; the core network equipment receives a service request from the terminal equipment, wherein the service request is used for requesting service data corresponding to the first application, and the service request comprises the DNAI; the core network device sends second response information responding to the service request to the terminal device, wherein the second response information comprises: and calculating the identifier of the MEC platform and the identifier of the CDN node of the content delivery network on the MEC platform by the mobile edge corresponding to the DNAI and the position of the terminal equipment.

In the method for data transmission in the MEC provided in the second aspect, in an MEC scenario, before a user starts a specific application, a core network element first determines a offloading policy, determines an MEC platform to be accessed by the user and a CDN edge node on the MEC platform according to the offloading policy, and feeds back the MEC platform and the CDN edge node on the MEC platform to a terminal device. The terminal device can perform service access according to the MEC platform to be accessed and the IP address of the CDN edge node on the MEC platform. Therefore, the synchronization of the shunting strategy is realized, the communication failure of the user caused by the distribution of the shunting strategy is avoided, the interruption of a communication link is avoided, and the user experience is improved.

In a possible implementation manner of the second aspect, the core network element generates a offloading policy according to the first information, where the offloading policy includes offloading policies corresponding to a plurality of applications, and the offloading policy corresponding to the first application includes: the identity of the first application, the identity of the MEC platform accessed by the first application, and the identity of the CDN node. For example, the offloading policy corresponding to the first application includes five-tuple information, where the five-tuple information is: the method comprises a client IP, a client port number, a server IP, a server port number and a protocol type, wherein the client can be understood as a first application program on the terminal equipment, and the server can be understood as a CDN edge node on an MEC platform for acquiring data of the first application program.

In a possible implementation manner of the second aspect, the core network element sends the offloading policy to the first network element. For example, the first network element is a user plane function UPF network element on the MEC platform, so as to implement triggering and inserting edge UPF and thus implement ULCL forking,

in a possible implementation manner of the second aspect, after the first application is ended, the method further includes: the core network element receives a first request from the terminal device, where the first request is used to request to delete a offloading policy corresponding to the first application, and the first request includes: an identification of the first application and the DNAI.

In a possible implementation manner of the second aspect, after determining that all applications accessing the MEC platform end, the first request is used to request to delete the offloading policy. In the implementation manner, when all the applications (all APPs) on the terminal device do not need to access resources on the corresponding MEC any more, the offloading policy is deleted from the UPF on the MEC, so that it is ensured that the subsequent traffic of other applications is not forwarded to the MEC any more, and the fact that the MEC resources are occupied by invalid traffic is avoided.

In a possible implementation manner of the second aspect, the service request is a hypertext transfer protocol HTTP request.

In a possible implementation manner of the second aspect, the first network element is a user plane function UPF network element on the MEC platform.

In a third aspect, there is provided a communication device comprising means for performing the steps of the above first aspect or any possible implementation manner of the first aspect. Alternatively, the communication device may be a terminal device.

In a fourth aspect, there is provided a communication apparatus comprising at least one processor and a memory, the at least one processor being configured to perform the method of the first aspect above or any possible implementation manner of the first aspect. Alternatively, the communication device may be a terminal device.

In a fifth aspect, there is provided a communication device comprising at least one processor configured to perform the method of the first aspect above or any possible implementation manner of the first aspect, and an interface circuit. Alternatively, the communication device may be a terminal device.

In a sixth aspect, there is provided a communication device comprising means for performing the steps of any possible implementation of the above third aspect. Optionally, the communication device may be an MEC policy synchronization service network element, another core network element, a PCF, an SMF, or a GSLB network element.

In a seventh aspect, a communication device is provided, which includes at least one processor and a memory, the at least one processor being configured to perform the method of the second aspect above or any possible implementation manner of the second aspect. Optionally, the communication device may be an MEC policy synchronization service network element, another core network element, a PCF, an SMF, or a GSLB network element.

In an eighth aspect, there is provided a communication device comprising at least one processor configured to perform the method of the second aspect above or any possible implementation of the second aspect, and an interface circuit. Optionally, the communication device may be an MEC policy synchronization service network element, another core network element, a PCF, an SMF, or a GSLB network element.

In a ninth aspect, a computer program product is provided, the computer program product comprising a computer program for performing the method of the first aspect or any possible implementation form of the first aspect, or for performing the method of the second aspect or any possible implementation form of the second aspect, when the computer program is executed by a processor.

A tenth aspect provides a computer readable storage medium having stored thereon a computer program for performing the method of the first aspect or any possible implementation form of the first aspect, or for performing the method of the second aspect or any possible implementation form of the second aspect, when the computer program is executed.

In an eleventh aspect, there is provided a chip or an integrated circuit, comprising: a processor for calling and running the computer program from the memory so that the device on which the chip or integrated circuit is installed performs the method of the first aspect or any possible implementation manner of the first aspect, or performs the method of the second aspect or any possible implementation manner of the second aspect.

According to the method and the communication device for data transmission in the MEC, in an MEC scene, before a user starts a specific application, the MEC platform to be accessed by the user and the CDN edge node on the MEC platform are determined according to a shunting strategy, and when the user formally initiates service access, the service access is performed according to the IP addresses of the MEC platform to be accessed and the CDN edge node on the MEC platform. Therefore, the synchronization of the shunting strategy is realized, the communication failure of the user caused by the distribution of the shunting strategy is avoided, the interruption of a communication link is avoided, and the user experience is improved.

Drawings

Fig. 1 is a schematic structural diagram of a terminal device provided in an embodiment of the present application.

Fig. 2 is a schematic software structure block diagram of a terminal device provided in an embodiment of the present application.

Fig. 3 is a schematic block diagram of an example wireless communication system architecture suitable for use in the present application.

Fig. 4 is a network architecture diagram of an example of a communication system for deploying an edge CDN node on an MEC platform according to an embodiment of the present application.

Fig. 5 is a schematic interaction diagram of a service or application access flow performed by a user using a terminal device in the prior art.

Fig. 6 is a schematic block diagram of another example wireless communication system architecture suitable for use with the present application.

Fig. 7 is a schematic interaction diagram of a method of data transmission in an MEC according to an embodiment of the present application.

Fig. 8 is a schematic interaction diagram of a method of data transmission in an MEC according to another embodiment of the present application.

Fig. 9 is a schematic interaction diagram of a method of data transmission in an MEC according to yet another embodiment of the present application.

Fig. 10 is a schematic interaction diagram of a method of data transmission in an MEC according to another embodiment of the present application.

Fig. 11 is a schematic interaction diagram of a method of data transmission in an MEC according to yet another embodiment of the present application.

Fig. 12 is a schematic block diagram of an example of a communication apparatus structure according to an embodiment of the present application.

Fig. 13 is a schematic block diagram of another example of the structure of a communication device according to an embodiment of the present application.

Fig. 14 is a schematic block diagram of a structure of another example of a communication device according to an embodiment of the present application.

Fig. 15 is a schematic block diagram of another example of the structure of a communication device according to an embodiment of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

In the description of the embodiments of the present application, "/" means "or" unless otherwise specified, for example, a/B may mean a or B; "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present application, "a plurality" means two or more than two.

In the following, the terms "first", "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the present embodiment, "a plurality" means two or more unless otherwise specified.

The method for data transmission in the MEC provided by the embodiment of the application can be applied to electronic devices such as a mobile phone, a tablet personal computer, a wearable device, a vehicle-mounted device, an Augmented Reality (AR)/Virtual Reality (VR) device, a notebook computer, a super-mobile personal computer (UMPC), a netbook, a Personal Digital Assistant (PDA), a router, and a wireless Access Point (AP). The electronic device may also be other terminal devices having data processing functions. The embodiment of the present application does not set any limit to the specific type of the electronic device.

The data processing method provided by the embodiment of the application can be applied to electronic devices such as a mobile phone, a tablet personal computer, a wearable device, a vehicle-mounted device, an Augmented Reality (AR)/Virtual Reality (VR) device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a Personal Digital Assistant (PDA), a router, and an Access Point (AP). The electronic device may also be other terminal devices having data processing functions. The embodiment of the present application does not set any limit to the specific type of the electronic device.

By way of example, fig. 1 shows a schematic diagram of a possible structure of the electronic device 100. The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a Subscriber Identification Module (SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, and the like.

It is to be understood that the illustrated structure of the embodiment of the present application does not specifically limit the electronic device 100. In other embodiments of the present application, electronic device 100 may include more or fewer components than shown, or some components may be combined, some components may be split, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a memory, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), etc. The different processors may be separate devices or may be integrated into one or more processors.

In the data processing method provided by the present application, the processor 110 may complete the segmentation of the service to be processed, and perform processing and calculation of the service. For example, rendering of images (for example, rendering of game screens), processing of videos, processing of audios, and Artificial Intelligence (AI) calculation are performed. Further, the processor 110 may also obtain the storage space condition in the memory, the processing capability of the CPU, GPU, DSP, NPU, etc., and the calculation load condition.

The controller may be, among other things, a neural center and a command center of the electronic device 100. The controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution.

A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 110, thereby increasing the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, and/or a Universal Serial Bus (USB) interface, etc.

The I2C interface is a bi-directional synchronous serial bus that includes a serial data line (SDA) and a Serial Clock Line (SCL). In some embodiments, processor 110 may include multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces, respectively. For example: the processor 110 may be coupled to the touch sensor 180K via an I2C interface, such that the processor 110 and the touch sensor 180K communicate via an I2C bus interface to implement the touch functionality of the electronic device 100.

The I2S interface may be used for audio communication. In some embodiments, processor 110 may include multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 via an I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may communicate audio signals to the wireless communication module 160 via the I2S interface, enabling answering of calls via a bluetooth headset.

The PCM interface may also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled by a PCM bus interface. In some embodiments, the audio module 170 may also transmit audio signals to the wireless communication module 160 through the PCM interface, so as to implement a function of answering a call through a bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communications. The bus may be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is generally used to connect the processor 110 with the wireless communication module 160. For example: the processor 110 communicates with a bluetooth module in the wireless communication module 160 through a UART interface to implement a bluetooth function. In some embodiments, the audio module 170 may transmit the audio signal to the wireless communication module 160 through a UART interface, so as to realize the function of playing music through a bluetooth headset.

MIPI interfaces may be used to connect processor 110 with peripheral devices such as display screen 194, camera 193, and the like. The MIPI interface includes a Camera Serial Interface (CSI), a display screen serial interface (DSI), and the like. In some embodiments, processor 110 and camera 193 communicate through a CSI interface to implement the capture functionality of electronic device 100. The processor 110 and the display screen 194 communicate through the DSI interface to implement the display function of the electronic device 100.

The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal and may also be configured as a data signal. In some embodiments, a GPIO interface may be used to connect the processor 110 with the camera 193, the display 194, the wireless communication module 160, the audio module 170, the sensor module 180, and the like. The GPIO interface may also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, and the like.

The USB interface 130 is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface 130 may be used to connect a charger to charge the electronic device 100, and may also be used to transmit data between the electronic device 100 and a peripheral device. And the earphone can also be used for connecting an earphone and playing audio through the earphone. The interface may also be used to connect other electronic devices, such as AR devices and the like.

It should be understood that the interface connection relationship between the modules illustrated in the embodiments of the present application is only an illustration, and does not limit the structure of the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection manners or a combination of multiple interface connection manners in the above embodiments.

The charging management module 140 is configured to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive a wireless charging input through a wireless charging coil of the electronic device 100. The charging management module 140 may also supply power to the electronic device through the power management module 141 while charging the battery 142.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be used to monitor parameters such as battery capacity, battery cycle count, battery state of health (leakage, impedance), etc. In some other embodiments, the power management module 141 may also be disposed in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be disposed in the same device.

In the specific implementation process of the data processing method provided by the present application, the power management module 141 may determine the remaining power of the mobile phone in real time, and further determine the power consumption rate within a period of time.

The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The

antennas

1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution including 2G/3G/4G/5G wireless communication applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional modules, independent of the processor 110.

The wireless communication module 160 may provide a solution for wireless communication applied to the electronic device 100, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), bluetooth (bluetooth, BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

In the specific implementation process of the data processing method provided by the present application, the mobile phone 100 may discover other electronic devices through the wireless communication module 160, and establish communication connection with other electronic devices to form a local area network, so as to transmit data or information and the like. For example, communication connection is established with other electronics through communication technologies such as NFC, bluetooth, and Wi-Fi network, and service information that needs to be processed by each and processing capability, remaining power, storage space, power consumption, calculation result, and the like of each are interacted.

In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150 and antenna 2 is coupled to wireless communication module 160 so that electronic device 100 can communicate with networks and other devices through wireless communication techniques. The wireless communication technology may include global system for mobile communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), time-division code division multiple access (time-division code division multiple access, TD-SCDMA), Long Term Evolution (LTE), LTE, BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc. The GNSS may include a Global Positioning System (GPS), a global navigation satellite system (GLONASS), a beidou satellite navigation system (BDS), a quasi-zenith satellite system (QZSS), and/or a Satellite Based Augmentation System (SBAS).

The electronic device 100 implements display functions via the GPU, the display screen 194, and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, video, and the like. The display screen 194 includes a display panel. The display panel may be a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (FLED), a miniature, a Micro-oeld, a quantum dot light-emitting diode (QLED), or the like. In some embodiments, the electronic device 100 may include 1 or N display screens 194, with N being a positive integer greater than 1. In the data processing method provided by the present application, the display screen 194 may display other electrons that can be paired or connected with the mobile phone 100 to the user, so that the user can establish a local area network formed by a plurality of electrons. Also, the display screen 194 may display an image screen, a video screen, and the like to the user.

The electronic device 100 may implement a shooting function through the ISP, the camera 193, the video codec, the GPU, the display 194, the application processor, and the like.

The ISP is used to process the data fed back by the camera 193. For example, when a photo is taken, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converting into an image visible to naked eyes. The ISP can also carry out algorithm optimization on the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing element converts the optical signal into an electrical signal, which is then passed to the ISP where it is converted into a digital image signal. And the ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into image signal in standard RGB, YUV and other formats. In some embodiments, the electronic device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process digital image signals and other digital signals. Such as video digital signals, audio digital signals, etc.

Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 may play or record video in a variety of encoding formats, such as: moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, and the like.

The NPU is a neural-network (NN) computing processor that processes input information quickly by using a biological neural network structure, for example, by using a transfer mode between neurons of a human brain, and can also learn by itself continuously. Applications such as intelligent recognition of the electronic device 100 can be realized through the NPU, for example: image recognition, face recognition, speech recognition, text understanding, and the like.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the memory capability of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music, video, etc. are saved in an external memory card.

The internal memory 121 may be used to store computer executable program code, which includes instructions. The processor 110 executes various functional applications of the electronic device 100 and data processing by executing instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. The storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required by at least one function, and the like. The storage data area may store data (such as audio data, phone book, etc.) created during use of the electronic device 100, and the like. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (UFS), and the like.

The electronic device 100 may implement audio functions via the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or some functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also called a "horn", is used to convert the audio electrical signal into an acoustic signal. The electronic apparatus 100 can listen to music through the speaker 170A or listen to a handsfree call.

The receiver 170B, also called "earpiece", is used to convert the electrical audio signal into an acoustic signal. When the electronic apparatus 100 receives a call or voice information, it can receive voice by placing the receiver 170B close to the ear of the person.

The microphone 170C, also referred to as a "microphone," is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can input a voice signal to the microphone 170C by speaking the user's mouth near the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In other embodiments, the electronic device 100 may be provided with two microphones 170C to achieve a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device 100 may further include three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, perform directional recording, and so on.

The headphone interface 170D is used to connect a wired headphone. The headset interface 170D may be the USB interface 130, or may be a 3.5mm open mobile electronic device platform (OMTP) standard interface, a cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 180A is used for sensing a pressure signal, and converting the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The pressure sensor 180A can be of a wide variety, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a sensor comprising at least two parallel plates having an electrically conductive material. When a force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 194, the electronic apparatus 100 detects the intensity of the touch operation according to the pressure sensor 180A. The electronic apparatus 100 may also calculate the touched position from the detection signal of the pressure sensor 180A. In some embodiments, the touch operations that are applied to the same touch position but different touch operation intensities may correspond to different operation instructions. For example: and when the touch operation with the touch operation intensity smaller than the first pressure threshold value acts on the short message application icon, executing an instruction for viewing the short message. And when the touch operation with the touch operation intensity larger than or equal to the first pressure threshold value acts on the short message application icon, executing an instruction of newly building the short message.

The gyro sensor 180B may be used to determine the motion attitude of the electronic device 100. In some embodiments, the angular velocity of electronic device 100 about three axes (i.e., the x, y, and z axes) may be determined by gyroscope sensor 180B. The gyro sensor 180B may be used for photographing anti-shake. For example, when the shutter is pressed, the gyro sensor 180B detects a shake angle of the electronic device 100, calculates a distance to be compensated for by the lens module according to the shake angle, and allows the lens to counteract the shake of the electronic device 100 through a reverse movement, thereby achieving anti-shake. The gyroscope sensor 180B may also be used for navigation, somatosensory gaming scenes.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, electronic device 100 calculates altitude, aiding in positioning and navigation, from barometric pressure values measured by barometric pressure sensor 180C.

The magnetic sensor 180D includes a hall sensor. The electronic device 100 may detect the opening and closing of the flip holster using the magnetic sensor 180D. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 may detect the opening and closing of the flip according to the magnetic sensor 180D. And then according to the opening and closing state of the leather sheath or the opening and closing state of the flip cover, the automatic unlocking of the flip cover is set.

The acceleration sensor 180E may detect the magnitude of acceleration of the electronic device 100 in various directions (typically three axes). The magnitude and direction of gravity can be detected when the electronic device 100 is stationary. The method can also be used for recognizing the posture of the electronic equipment, and is applied to horizontal and vertical screen switching, pedometers and other applications.

A distance sensor 180F for measuring a distance. The electronic device 100 may measure the distance by infrared or laser. In some embodiments, taking a picture of a scene, electronic device 100 may utilize range sensor 180F to range for fast focus.

The proximity light sensor 180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light to the outside through the light emitting diode. The electronic device 100 detects infrared reflected light from nearby objects using a photodiode. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100. When insufficient reflected light is detected, the electronic device 100 may determine that there are no objects near the electronic device 100. The electronic device 100 can utilize the proximity light sensor 180G to detect that the user holds the electronic device 100 close to the ear for talking, so as to automatically turn off the screen to achieve the purpose of saving power. The proximity light sensor 180G may also be used in a holster mode, a pocket mode automatically unlocks and locks the screen.

The ambient light sensor 180L is used to sense the ambient light level. Electronic device 100 may adaptively adjust the brightness of display screen 194 based on the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust the white balance when taking a picture. The ambient light sensor 180L may also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in a pocket to prevent accidental touches.

The fingerprint sensor 180H is used to collect a fingerprint. The electronic device 100 can utilize the collected fingerprint characteristics to unlock the fingerprint, access the application lock, photograph the fingerprint, answer an incoming call with the fingerprint, and so on.

The temperature sensor 180J is used to detect temperature. In some embodiments, electronic device 100 implements a temperature processing strategy using the temperature detected by temperature sensor 180J. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device 100 performs a reduction in performance of a processor located near the temperature sensor 180J, so as to reduce power consumption and implement thermal protection. In other embodiments, the electronic device 100 heats the battery 142 when the temperature is below another threshold to avoid the low temperature causing the electronic device 100 to shut down abnormally. In other embodiments, when the temperature is lower than a further threshold, the electronic device 100 performs boosting on the output voltage of the battery 142 to avoid abnormal shutdown due to low temperature.

The touch sensor 180K is also referred to as a "touch panel". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is used to detect a touch operation applied thereto or nearby. The touch sensor can communicate the detected touch operation to the application processor to determine the touch event type. Visual output associated with the touch operation may be provided through the display screen 194. In other embodiments, the touch sensor 180K may be disposed on a surface of the electronic device 100, different from the position of the display screen 194.

The keys 190 include a power-on key, a volume key, and the like. The keys 190 may be mechanical keys. Or may be touch keys. The electronic apparatus 100 may receive a key input, and generate a key signal input related to user setting and function control of the electronic apparatus 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration cues, as well as for touch vibration feedback. For example, touch operations applied to different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also respond to different vibration feedback effects for touch operations applied to different areas of the display screen 194. Different application scenes (such as time reminding, receiving information, alarm clock, game and the like) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

Indicator 192 may be an indicator light that may be used to indicate a state of charge, a change in charge, or a message, missed call, notification, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card can be brought into and out of contact with the electronic apparatus 100 by being inserted into the SIM card interface 195 or being pulled out of the SIM card interface 195. The electronic device 100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support a Nano SIM card, a Micro SIM card, a SIM card, etc. The same SIM card interface 195 can be inserted with multiple cards at the same time. The multiple cards may be of the same or different types. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as communication and data communication. In some embodiments, the electronic device 100 employs esims, namely: an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

The software system of the electronic device 100 may employ a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes an Android system with a layered architecture as an example, and exemplarily illustrates a software structure of the electronic device 100.

Fig. 2 is a block diagram of a software structure of the electronic device 100 according to the embodiment of the present application.

The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, an application layer, an application framework layer, an Android runtime (Android runtime) and system library, and a kernel layer from top to bottom.

The application layer may include a series of application packages.

As shown in fig. 2, the application package may include applications such as camera, gallery, calendar, phone call, map, navigation, WLAN, bluetooth, music, video, short message, etc.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application programs of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 2, the application framework layers may include a window manager, content provider, view system, phone manager, resource manager, notification manager, and the like.

The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide communication functions of the electronic device 100. Such as management of call status (including on, off, etc.).

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and the like.

The notification manager enables the application to display notification information in the status bar, can be used to convey notification-type messages, can disappear automatically after a short dwell, and does not require user interaction. Such as a notification manager used to inform download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in the status bar, sounding a prompt tone, vibrating the electronic device, flashing an indicator light, etc.

The Android Runtime comprises a core library and a virtual machine. The Android runtime is responsible for scheduling and managing an Android system.

The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. And executing java files of the application program layer and the application program framework layer into a binary file by the virtual machine. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), Media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), and the like.

The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, and the like.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

The following describes exemplary workflow of the software and hardware of the electronic device 100 in connection with capturing a photo scene.

When the touch sensor 180K receives a touch operation, a corresponding hardware interrupt is issued to the kernel layer. The kernel layer processes the touch operation into an original input event (including touch coordinates, a time stamp of the touch operation, and other information). The raw input events are stored at the kernel layer. And the application program framework layer acquires the original input event from the kernel layer and identifies the control corresponding to the input event. Taking the touch operation as a touch click operation, and taking a control corresponding to the click operation as a control of a camera application icon as an example, the camera application calls an interface of an application framework layer, starts the camera application, further starts a camera drive by calling a kernel layer, and captures a still image or a video through the camera 193.

It should be noted that the electronic device shown in fig. 1 is only an example of an electronic device, and the application is not particularly limited, and the application may be applied to a terminal device such as a mobile phone and a tablet computer, and the application is not limited thereto.

With the rapid development of mobile broadband and intelligent terminal devices (such as the electronic device 100 shown in fig. 1), the terminal devices have stronger capabilities and more executable service classes. When terminal equipment faces business requirements, the current terminals basically fight against each other, namely, the terminal equipment can meet the business requirements by self capacity. When the self-ability can not meet the service requirement, the user experience can be only reduced, for example: presence of game or video jams, reduced game frame rates, extended latency, etc. On the other hand, when a plurality of terminal devices perform a certain service together, the same calculation requirements may be faced. For example: when multiple persons participate in the mobile phone network game together, if the persons are grouped, the persons may face (part of) the same or similar game pictures, and the rendering calculation requirements of the same or similar game pictures are the same. However, it can be said that the respective rendering screens of the multiple terminals are wasted in computing resources.

Fig. 3 is a schematic block diagram of a wireless communication system architecture suitable for use with the present application. As shown in fig. 3, the system architecture includes a terminal device, an access network device, a management device, a gateway device, and a Data Network (DN). The terminal device in fig. 1 may be configured to connect to an access network device deployed by an operator through a wireless air interface, and then connect to a data network through a gateway device; the access network equipment is mainly used for realizing the functions of a wireless physical layer, resource scheduling, wireless resource management, wireless access control, mobility management and the like; the gateway device is mainly used for establishing a channel with the terminal device and forwarding a data packet between the terminal device and an external data network on the channel; the data network may correspond to a plurality of different service domains, such as an IP Multimedia Subsystem (IMS), the Internet (Internet), an Internet Protocol Television (IPTV), other operator service domains, and the like, and is mainly used for providing a plurality of data service services for the terminal device, where the data service domains may include network devices such as a server (including a server providing a multicast service), a router, a gateway, and the like. For a terminal desiring to receive an IP multicast service data packet, a group management protocol (IPv 4) includes a network group management protocol (IGMP) protocol, and an IPv6 includes a multicast listener discovery protocol (MLD) protocol, to request to join/withdraw a multicast IP address corresponding to a certain multicast service, so as to start receiving/ending the multicast service. It should be noted that fig. 1 is only an exemplary architecture diagram, and besides the functional units shown in fig. 1, the network architecture may further include other functional units or functional network elements, which is not limited in this embodiment of the application.

When the communication network shown in fig. 3 is a 5G network, the terminal device (also referred to as a terminal device) may be a User Equipment (UE), such as: a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a smart phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a computer, a laptop computer, a handheld communication device, a handheld computing device, a satellite radio device, a wireless modem card, a Set Top Box (STB), a Customer Premises Equipment (CPE), and/or other devices for communicating over a wireless system. The access network device may be AN Access Network (AN)/Radio Access Network (RAN) device, and the network may be composed of a plurality of 5G-AN/5G-RAN nodes, where the 5G-AN/5G-RAN nodes may be: access node (AP), next generation base station (NR nodeB, gNB), Central Unit (CU), and Distributed Unit (DU) in separate forms, which are, gNB, TRP, TP, or some other access node. The management apparatus may include: a unified data management network element (UDM), an Access and Mobility Function (AMF), a Session Management Function (SMF), a Policy Control Function (PCF), an Application Function (AF), a network open function (NEF), etc. The gateway device may include functional units such as a User Plane Function (UPF), a Branching Point (BP), an Uplink Classifier (UL CL), and the like, which may work independently or may be combined together to implement some control functions, for example: the AMF, SMF and PCF may be combined together as a management device to perform access control and mobility management functions such as access authentication, security encryption, location registration, etc. of the terminal device, session management functions such as establishment, release and change of a user plane transmission path, and a function of analyzing data (e.g. congestion) related to some slices (slices) and data related to the terminal device. The UPF, as a gateway device, mainly completes functions such as routing forwarding of user plane data, for example: and the system is responsible for filtering data messages of the terminal equipment, transmitting/forwarding data, controlling the rate, generating charging information and the like. In addition, in the 5G system, in order to support selective routing of traffic to a data network, a session management network element may control a data path of a Protocol Data Unit (PDU) session, so that a plurality of interfaces may be simultaneously corresponded between the PDU session and the data network, that is, a plurality of session anchors may exist for the same PDU session. The User Plane Function (UPF) that terminates these interfaces is called a PDU Session Anchor (PSA) or anchor UPF. Each anchor point of a PDU session may also provide a different entry to the same DN. Meanwhile, data offloading from upstream data to different PSAs is implemented by inserting one or more UPF network elements between the access network device and different PSAs, where the inserted UPF network element may be a Branch Point (BP) or an upstream classifier (ULCL). It is also noted that BP or UL CL may also be referred to as a forking point UPF network element.

In the 5G network shown in fig. 3, the functional units may establish connections through a next generation Network (NG) interface to implement communication, such as: the terminal equipment establishes an air interface connection with RAN equipment through a New Radio (NR) interface and is used for transmitting user plane data and control plane signaling; the terminal equipment can establish control plane signaling connection with the AMF through an NG interface 1 (N1 for short); AN/RAN device, such as a next generation radio access base station (NR NodeB, gNB), may establish a user plane data connection with a forking point UPF through AN NG interface 3 (N3 for short); the AN/RAN equipment can establish a control plane signaling connection with the AMF through AN NG interface 2 (N2 for short); the shunting point UPF can establish user plane data connection with the anchor point UPF through an NG interface 9 (N9 for short); the shunting point UPF and the anchor point UPF can establish control plane signaling connection with the SMF through an NG interface 4 (N4 for short); the anchor point UPF may interact with the data network via the NG interface 6 (abbreviated N6); the AMF can establish a control plane signaling connection with the SMF through an NG interface 11 (N11 for short); the SMF may establish a control plane signaling connection with the PCF via NG interface 7 (abbreviated N7). It should be noted that the portion shown in fig. 1 is only an exemplary architecture diagram, and the network architecture may include other functional units or functional network elements besides the functional units shown in the portion shown in fig. 1, which is not limited in this embodiment of the present application.

When the communication network shown in fig. 3 is a 4G network, the terminal device may refer to the description related to the terminal device in fig. 3, and details are not described herein again; the access network device may be a base station (NB), an evolved nodeB (eNB), a TRP, TP, AP, or some other access unit; the core network device may include: management devices such as a Mobility Management Element (MME), a Policy and Charging Rules Function (PCRF), and gateway devices such as a Serving Gateway (SGW), a packet data network gateway (PGW), and a Local Gateway (LGW).

It should be understood that the names of the interfaces between the network elements in the present application are only exemplary, and the interfaces between the network elements may also be other names.

Terminal equipment in the embodiments of the present application may refer to user equipment, access terminals, subscriber units, subscriber stations, mobile stations, remote terminals, mobile devices, user terminals, wireless communication devices, user agents, or user devices. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G Network or a terminal device in a Public Land Mobile Network (PLMN) for future evolution, and the like, which are not limited in this embodiment.

The Radio Access Network device in this embodiment may be a device for communicating with a terminal device, where the Radio Access Network device may be a Base Transceiver Station (BTS) in a Global System for Mobile communications (GSM) System or a Code Division Multiple Access (CDMA) System, may also be a Base Station (NodeB, NB) in a Wideband Code Division Multiple Access (WCDMA) System, may also be an evolved Base Station (evolved NodeB, eNB, or eNodeB) in an LTE System, may also be a Radio controller in a Cloud Radio Access Network (CRAN) scenario, or may be a relay Station, an Access point, a vehicle-mounted device, a wearable device, a Network device in a 5G Network, or a Network device in a future evolution Network, and the like, and the present embodiment is not limited thereto.

For the PDU session in the 5G system, multiple session anchors may exist for the same PDU session by using UL CL, or multiple-anchor for the same PDU session by using Internet Protocol Version number 6 (Ipv 6).

In a PDU session scenario where multiple PSAs are implemented with a UL CL, the SMF may insert a UL CL in the middle of the data path of the PDU session. UL CL is a function provided by UPF that aims to locally route traffic (routing) for certain traffic using flow filters provided by SMF. Here, the terminal device does not perceive UL CL and does not participate in UL CL addition/deletion. The UL CL forwards upstream traffic to different PDU session anchors (e.g., UPF1 and UPF2 in fig. 1 are two different anchors for the PDU session) based on traffic detection and traffic forwarding rules provided by the SMF. And aggregating downstream data streams destined for the terminal devices, namely: traffic data flows from different PDU session anchors (e.g., UPF1 and UPF2 in fig. 1) are aggregated to the downlink to the terminal device.

Mobile Edge Computing (MEC) is a technology for deeply fusing an access network and internet services based on an evolution architecture of a 5G system. The method deploys the functions of service processing and resource scheduling of part of an Application Server (AS) and a mobile broadband (MBB) core network to the network edge close to an access network together, and provides reliable and extremely-low-delay service experience through service close to user processing. That is, on the rear side of the 5G base station, a computing environment is provided at a position closer to a user (or a terminal device), and deployment of a third-party service (for example, a Content Delivery Network (CDN) edge node) on the MEC platform is supported, so that the service is closer to the user, and a faster download speed and a lower access delay are provided.

For example, fig. 4 is a diagram illustrating an example of a network architecture of a communication system deploying edge CDN nodes on a MEC platform. As shown in fig. 4, the communication system includes a terminal device, a radio access network device, a core network device, an MEC platform, a Global Service Load Balancing (GSLB) node, and the like. And CDN edge nodes are deployed on the MEC platform. The terminal device may obtain data or services by accessing a CDN edge node on the MEC platform. For example, as shown in fig. 2, in the system architecture, an MEC platform 1(MEC-1) and an MEC platform 2(MEC-2) are respectively deployed, and edge CDN nodes are respectively deployed on the MEC-1 platform and the MEC-2 platform.

In the MEC scenario, a flow of a user accessing a service or an application by using a terminal device may be shown as a method 100 shown in fig. 5, where as shown in fig. 5, the method 100 includes:

s101, a terminal device sends a request for querying a CDN edge node to a core network device through a hypertext transfer protocol (HTTP). For example, the terminal device may send an HTTP request to the core network device for querying the CDN edge node.

S102, the core network device receives the request, and determines a Data Network Access Identity (DNAI) corresponding to the terminal device according to the IP address of the terminal device. The DNAI may be used to identify or indicate the MEC platform, i.e., the DNAI may serve as an identification of the MEC platform. For example, the identity of the MEC platform may be a DNAI supported by a UPF network element deployed on the MEC platform or a DNAI supported by a UPF network element connected to the MEC platform. Different DNAIs may represent different MEC platforms. The DNAI corresponding to the terminal device may be understood as DNAI corresponding to the location of the terminal device, for example, may be DNAI supported by a UPF network element on the MEC platform closest to the terminal device. After determining the DNAI, the core network device adds the DNAI to an HTTP request message header.

And S103, the core network device sends the HTTP request to a GSLB network element on the CDN.

And S104, the CDN GSLB network element determines (dispatches) the CDN edge node which the terminal equipment needs to access according to the DNAI carried by the HTTP request, the IP address of the terminal equipment and the like.

And S105, the CDN GSLB network element sends the determined IP address of the CDN edge node and the like to the terminal equipment.

S106a, if the CDN GSLB network element is scheduled to a CDN edge node on the non-MEC platform, the terminal device sends the service request to the CDN edge node on the non-MEC platform, and the terminal device obtains the application data through the CDN edge node on the non-MEC platform.

S106b, if the CDN GSLB network element is scheduled to a CDN edge node on the MEC platform, the terminal device needs to send the service request to the core network device first, and then the core network device forwards the service request to the CDN edge node on the MEC platform, and the terminal device obtains the application data through the CDN edge node on the MEC platform.

And S107, the CDN GSLB network element asynchronously sends the DNAI corresponding to the terminal equipment and the IP address of the terminal equipment to the core network equipment. In the embodiments of the present application, "asynchronous or asynchronous mechanism" may be understood as: the CDN GSLB may send the DNAI corresponding to the terminal device and the IP address of the terminal device to the core network device to request for determining the UL CL offload policy, without confirming that the terminal device receives the response information of the location of the CDN node that can be served and that is returned to the terminal device by the CDN GSLB. For example, the response information of the serviceable CDN node location returned by the CDN GSLB to the terminal device may be sent before the CDN GSLB sends the information to the core network device, that is, the effective time of the two pieces of information is not strictly controlled.

And S108, the core network equipment determines the UL CL shunting strategy (triggering insertion of UL CL) according to the DNAI and the IP address of the terminal equipment. For example, the SMF network element may implement the insertion of UL CL with the trigger insertion edge UPF. The UL CL offload policy is used to indicate that the terminal device needs to access a CDN edge node on the MEC platform, where the CDN edge node may be understood as an application server and stores data corresponding to an application accessed by the terminal device. The UL CL policy is to determine whether a service request of the terminal device is diverted to a CDN node of the MEC or a CDN node of a non-MEC according to a source IP, a target IP, a source port, a target port, and a communication protocol defined by UL and CL. For example, the UL CL offloading policy includes: the IP address of the MEC platform, the IP address of the CDN edge node on the MEC platform, and the like. The core network device may feed back the IP address of the CDN edge node on the MEC platform to the terminal device.

S109a, if the CDN edge node accessed by the terminal device is not on the MEC platform, and if the communication already exists in S106a, the communication connection in S106a step is disconnected, the service request of the terminal device is routed to the CDN edge node on the MEC platform first, and the CDN edge node on the MEC platform is routed to the CDN edge node on the non-MEC platform, and the connection is reestablished and data transmission is performed.

S109b, if the CDN edge node accessed by the terminal device is on the MEC platform, and if the communication already exists in S106b, the communication connection in step S1056 is disconnected, the service request of the terminal device is routed to the CDN edge node on the MEC platform, and the connection is reestablished and data transmission is performed.

Currently, a third-party service (e.g., a CDN) deployed on the MEC implements a UL CL offload synchronization interface, and a third-party service scheduling system (e.g., a GSLB of the CDN) is docked with a core network element, dynamically determines whether a location of a terminal device has a regional change, and updates the UL CL after the location of the terminal device changes. Because the distribution synchronization is an asynchronous mechanism, that is, response information of a position of a CDN node that can be served and is returned to the terminal device by the CDN GSLB does not confirm that the terminal device receives the response information, the CDN GSLB may send the DNAI corresponding to the terminal device and the IP address of the terminal device to the core network device to request for determining the UL CL distribution policy. In other words, the terminal device establishes a communication link with the service node deployed on the non-MEC or the MEC before obtaining the UL CL offloading policy, and after the UL CL offloading policy is completed, the link between the terminal device and the service node deployed on the non-MEC or the MEC is broken and reconnected, which may cause interruption of data accessed by the user and affect user experience. Moreover, after the terminal device initiates a session request, the core network device may schedule all request traffic on the terminal device to the CDN edge node on the MEC unconditionally within a session period, even if a certain request does not access a service resource on the MEC, which may cause the MEC resource to be additionally occupied.

In view of this, the present application provides a method for data transmission in an MEC, where in an MEC scenario, before a user starts a specific application, a offloading policy is first determined, an MEC platform that the user needs to access and a CDN edge node on the MEC platform are determined according to the offloading policy, and when the user formally initiates a service access, the service access is performed according to IP addresses of the MEC platform that the user needs to access and the CDN edge node on the MEC platform. Therefore, the synchronization of the shunting strategy is realized, the communication failure of the user caused by the distribution of the shunting strategy is avoided, the interruption of a communication link is avoided, and the user experience is improved.

For the understanding of the embodiments of the present application, a communication system applicable to the embodiments of the present application will be briefly described with reference to fig. 6.

Fig. 6 is a schematic diagram of a communication system suitable for implementation of the present application. As shown in fig. 6, the communication system includes a terminal device, a radio access network device, a core network device, an MEC platform, a CDN GSLB, and the like. And CDN edge nodes are deployed on the MEC platform. The terminal device may obtain data or services by accessing a CDN edge node on the MEC platform or a CDN edge node on a non-MEC platform (which may be referred to as a normal CDN edge node).

It should be noted that, for the sake of understanding, fig. 6 only schematically illustrates the architecture of the communication system, but this should not limit the present application in any way. For example, the communication system may further include more network nodes, for example, include more terminal devices, core network devices, MEC platforms, CDN edge nodes, and the like, and the radio access network devices, the terminal devices, and the like included in the communication system shown in fig. 6 may be access network devices or terminal devices in various forms described above. The embodiments of the present application are not shown in the figures one by one.

It should be understood that, in the embodiments of the present application, a terminal device and a core network device are taken as an example to serve as an execution subject of the execution method of each embodiment, and the method of each embodiment is described. By way of example and not limitation, the execution subject of the execution method may also be a chip applied to the terminal device and a chip applied to the core network element, or the execution subject may also be a device that implements the functions of the terminal device or the core network element.

The method for data transmission in the MEC provided in the present application is described in detail below with reference to fig. 7, and fig. 7 is a schematic flowchart of a method 200 for data transmission in the MEC according to an embodiment of the present application. The method 200 may be applied to the scenario shown in fig. 6, and of course, may also be applied to other communication scenarios, and the embodiment of the present application is not limited herein.

As shown in fig. 7, the method 200 shown in fig. 7 may include S210 to S260. The various steps in method 200 are described in detail below in conjunction with fig. 7. Wherein step S220 and step S250 are optional.

S210, the terminal device sends first information to a core network element, where the first information includes: the cell identifier of the terminal device and the identifier of the first application initiated by the terminal device.

And S220, the core network element (or the core network equipment) determines the DNAI corresponding to the position of the terminal equipment according to the first information.

S230, the core network element sends, to the terminal device, first response information in response to the first information, where the first response information includes: and accessing the data network corresponding to the cell identifier by using the DNAI.

S240, the terminal device sends a service request to a core network device, where the service request is used to request service data corresponding to the first application, and the service request includes the DNAI.

And S250, the core network element determines an MEC platform corresponding to the position of the terminal equipment and a CDN node on the MEC platform according to the IP address and the DNAI of the terminal equipment.

S260, the core network element sends, to the terminal device, second response information in response to the service request, where the second response information includes: and the identifiers of the MEC platform and the CDN nodes on the MEC platform correspond to the DNAI and the position of the terminal equipment.

In S210, when a user opens a certain Application (APP) by using the terminal device, for example, when opening Applications (APPs) such as "view video" and "view music", the APP obtains a cell id (cell id) where the terminal device is currently located and an application id (APP id) that is opened through an Application Program Interface (API) of the android system. Then, the terminal device may send first information to a core network element (in the following description, the core network element takes an MEC policy synchronization service network element as an example for explanation), where the first information may be, for example, an HTTP request, and the first information includes: the cell ID where the terminal device is located and an identifier (APP ID) of a first application (or a first application program) initiated by the terminal device, for example, the first application may be "hua be a video", "hua be a music", or "hua be a shopping mall", and the like. Optionally, the first information may be used to query a CDN edge node serving the terminal device.

In S220, the MEC policy synchronization service network element determines, according to the first information, a DNAI corresponding to the location of the terminal device. For example, the MEC policy synchronization service network element converts the cell ID into DNAI according to the cell ID of the terminal device, and completes the triggering of the UL CL of the terminal device.

Optionally, in S220, the MEC policy synchronization service network element may further generate a offloading policy for the terminal device. The offloading policy includes: the identity of the first application, the identity of the MEC platform accessed by the first application, and the identity of the CDN node. The offloading policy is to determine whether a service request of the terminal device is offloaded to a CDN node of the MEC or a CDN node of a non-MEC according to a source IP, a target IP, a source port, a target port, and a communication protocol defined by UL and CL. For example, the offloading policy (or may also be referred to as an uplink traffic offloading policy or an UL CL policy) includes five-tuple information, where the five-tuple information is: the method comprises a client IP, a client port number, a server IP, a server port number and a protocol type, wherein the client can be understood as a first application program on the terminal equipment, and the server can be understood as a CDN edge node on an MEC platform for acquiring data of the first application program. The offload policy is stored in the PDU session of the client. Meanwhile, the MEC strategy synchronization service network element maintains the shunting strategy according to the APPID, the DNAI, the PDU session ID and the like.

Optionally, in this embodiment of the present application, the offloading policy may include offloading policies respectively corresponding to multiple applications, where the multiple applications access CDN edge nodes on the same MEC platform, and the offloading policy corresponding to each application includes: the method comprises the steps of applying a corresponding client IP, a corresponding client port number, a corresponding server IP, a corresponding server port number and a protocol type. The MEC policy synchronization service network element may also initiate a synchronization of the breakout policy to other core network elements (e.g., NEF, PCF, or SMF, and the NEF, PCF, or SMF issues the policy to a UPF network element on the MEC, and finally the SMF triggers the insertion of the edge UPF to implement UL CL breakout.

In S230, the MEC policy synchronization service network element sends, to the terminal device, first response information in response to the first information, where the first response information includes: DNAI corresponding to the location of the terminal device.

In S240, the terminal device sends a service request to the MEC policy synchronization service network element, for example, the service request may be sent through an HTTP message. The service request is used for requesting service data corresponding to the first application, and the service request comprises the DNAI.

In S250, the MEC policy synchronization service network element determines the location of the terminal device according to the IP address and the DNAI of the terminal device, and determines an MEC platform corresponding to the location of the terminal device and a CDN node on the MEC platform. For example, the GSLB network element, which may be the CDN, determines, according to the IP address of the terminal device and the DNAI, an MEC platform corresponding to the location of the terminal device and a CDN node on the MEC platform. The CDN node on the MEC platform can provide data accessed by the application for the terminal equipment.

At S260, the MEC policy synchronization service network element or the GSLB network element sends, to the terminal device, second response information in response to the service request, where the second response information includes: an identifier of the MEC platform (e.g., an IP address of the MEC platform) and an identifier of the CDN node on the MEC platform (e.g., an IP address of the CDN node) corresponding to the DNAI and the location of the terminal device. Therefore, the terminal device can access the CDN node on the MEC platform according to the identifier of the MEC platform and the identifier or the IP address of the CDN node on the MEC platform, and obtain the service data corresponding to the first application from the CDN node.

According to the method for data transmission in the MEC, in an MEC scene, before a user starts a specific application, the MEC platform needing to be accessed by the user and the CDN edge node on the MEC platform are determined according to a shunting strategy, and when the user formally initiates service access, the service access is carried out according to the IP addresses of the MEC platform needing to be accessed and the CDN edge node on the MEC platform. Therefore, the synchronization of the shunting strategy is realized, the communication failure of the user caused by the distribution of the shunting strategy is avoided, the interruption of a communication link is avoided, and the user experience is improved.

In other possible implementations of the present application, after the access of the first application is ended, as shown in fig. 8, on the basis of the method steps shown in fig. 7, the method further includes S270 and S280.

S270, the terminal device sends a first request to a core network device, where the first request is used to request to delete a offloading policy corresponding to the first application, and the offloading policy includes: the identifier of the first application, the identifier of the MEC platform accessed by the first application, and the identifier of the CDN node, where the first request includes: an identification of the first application and the DNAI.

S280, the core network device deletes the shunting strategy corresponding to the first application according to the identifier (APP ID) of the first application and the DNAI.

The descriptions of S210 to S260 shown in fig. 8 may refer to the descriptions of these steps in fig. 7, and are not repeated here for brevity.

In S270, after the user finishes accessing the first application, that is, before the user finishes accessing the CDN edge node on the MEC, finishes exiting the application, the terminal device may send a first request to a core network device (for example, an MEC policy synchronization service network element), where the first request is used to request to delete the offloading policy corresponding to the first application. The offloading policy may include offloading policies corresponding to the multiple applications, respectively, where the MEC platforms accessed by the multiple applications are the same, and the separation policy corresponding to each application includes quintuple information, where the quintuple information is: the method comprises the steps of applying a corresponding client IP, a corresponding client port number, a corresponding server IP, a corresponding server port number and a protocol type.

In S280, after receiving the first request, the MEC policy synchronization service network element obtains a session ID from a Protocol Data Unit (PDU) session of the terminal device when determining that the user ends the access of the first application program, and deletes the offloading policy corresponding to the first application from the offloading policy according to the APP ID, DNAI, and PDU session ID of the first application, so as to avoid that the application request traffic that does not support the MEC access is offloaded to the MEC, thereby reducing the invalid occupation of the MEC resources.

Optionally, in this embodiment of the present application, the MEC policy synchronization service network element may further determine whether all applications (all APPs) on the terminal device need to access the MEC, and if all applications (all APPs) on the terminal device do not need to access resources on the MEC corresponding thereto any more, trigger deletion of the offload policy, and delete the offload policy from the UPF on the MEC, thereby ensuring that traffic of subsequent other applications is not forwarded to the MEC any more, and avoiding that invalid traffic occupies the MEC resources.

The following describes a method for data transmission in an MEC provided by the present application with reference to specific examples.

In the examples shown in fig. 9 and fig. 10, a user accesses a "hua is a video" application by using a terminal device, where a CDN node is deployed on an MEC platform in an administrative district B of a city a. Two CDN nodes exist in a city A, wherein a CDN node deployed on an MEC platform on an administrative district B is a CDN node 1 and is oriented to application access of 'Huaqi video' in the administrative district B, and another CDN node (CDN node 2) is oriented to application access of 'Huaqi video' of users in a non-administrative district B in the city A.

As shown in fig. 9, a method 300 for a user in an administrative area B of a city a, the method 300 comprising:

S301, when the user opens the APP "hua is video", the hua is video APP obtains the cell ID and APP ID (for example, com.huawei.video) of the current terminal device of the mobile phone through the open API of the android system, writes the cell ID and APP ID into the HTTP request, and sends the HTTP request to the MEC policy synchronization service network element.

S302, after receiving the HTTP request, the MEC policy synchronization service network element converts the cell ID into a DNAI identifier: and simultaneously generating an uplink flow distribution strategy (client IP, port, server IP, port and protocol type) aiming at the terminal equipment. The uplink traffic offload policy is stored in the PDU session of the client. Meanwhile, the MEC strategy synchronization service network element maintains the uplink flow shunting strategy according to the APPID, the DNAI and the PDU session ID.

And S303, the MEC strategy synchronization service network element sends the DNAI to the terminal equipment.

S304, the MEC policy synchronization service network element initiates synchronization of the UL CL policy to other core network elements (e.g., NEF, PCF, or SMF), and the NEF, PCF, or SMF network element issues the UL CL policy to the UPF network element of the MEC.

S305, the user selects a video through the 'Huaqi video' APP, clicks a play button, and sends an HTTP service request to the GSLB of the CDN manufacturer when initiating a video play request, wherein the HTTP service request carries DNAI and the IP address of the terminal device.

And S306, the CDN GSLB locates the CDN node 1 for providing service for the terminal equipment according to the DNAI and the IP address of the HTTP request.

S307, the CDN GSLB returns the IP address of the CDN node 1 to the terminal device.

S308, initiating a video playing request (CDN access request) according to the IP address of the CDN edge node 1 by the Hua is video APP on the terminal equipment.

The video playing request is shunted to the MEC by the wireless access network equipment according to an uplink traffic shunting strategy, the UPF on the MEC judges whether the request accesses the CDN node 1 on the MEC (for example, the request can be judged by a client IP, a port, a server IP, a port and a protocol type) according to the uplink traffic shunting strategy, and if so, the request of the user is dispatched to the CDN node 1 to provide service. If not, the request is forwarded to the UPF on the core, which determines the access policy.

As shown in fig. 10, a method 400 for a situation where a user is in a non-administrative area B of a city a, the method 400 comprising:

s401, when the user opens the APP "hua is video", the hua is video APP obtains the cell ID and APP ID (for example, com.huawei.video) of the current terminal device of the mobile phone through the open API of the android system, writes the cell ID and APP ID into the HTTP request, and sends the HTTP request to the MEC policy synchronization service network element.

S402, after receiving the HTTP request, the MEC policy synchronization service network element converts the cell ID into a DNAI identifier: and simultaneously generating an uplink flow distribution strategy (client IP, port, server IP, port and protocol type) aiming at the terminal equipment. The uplink traffic offload policy is stored in the PDU session of the client. Meanwhile, the MEC strategy synchronization service network element maintains the uplink flow shunting strategy according to the APPID, the DNAI and the PDU session ID.

And S403, the MEC strategy synchronization service network element sends the DNAI to the terminal equipment.

S404, the MEC policy synchronization service network element initiates a synchronization of the uplink traffic offload policy to other core network elements (e.g., NEF, PCF, or SMF), and since the area where the user is located is not deployed with MEC, the uplink traffic offload policy needs to be synchronized to the UPF network element in the core network of city a.

S405, the user selects a video through the 'Huaqi video' APP, clicks a play button, and sends an HTTP service request to the GSLB of the CDN manufacturer when initiating a play request, wherein the HTTP service request carries the DNAI and the IP address of the terminal device.

And S406, the CDN GSLB locates the CDN node 2 for providing service for the terminal equipment according to the DNAI and the IP address of the HTTP request.

S407, the CDN GSLB returns the IP address of the CDN node 2 to the terminal device.

S408, initiating a video playing request (CDN access request) according to the IP address of the CDN edge node 2 by the Hua is video APP on the terminal equipment. The video playing request is distributed to a UPF in a core network of the city A by a wireless access network device network according to an uplink flow distribution strategy, and the UPF schedules the request of the user to a CDN edge node 2 for providing service.

According to the method for data transmission in the MEC, when a user formally initiates service access, service access is carried out according to the access strategy (the MEC platform and the IP address of the CDN edge node on the MEC platform) required, so that synchronization of the shunting strategy is realized, the terminal equipment can obtain service from the CDN edge node deployed at the MEC near the corresponding 5G base station, and user communication failure caused by strategy distribution is avoided.

Fig. 11 shows another example of a method for data transmission in an MEC provided by the present application, where before an application on a terminal device finishes accessing a CDN edge node on the MEC, and finishes exiting the application, an uplink traffic offload policy is actively requested to be deleted, so that traffic of other subsequent applications does not enter the MEC again. As shown in fig. 11, the method 500 includes:

S501, after a user finishes video playing by using the 'Hua is video' APP or finishes the use of other application programs, the user closes the APP, before closing, the user uses the APP to send an HTTP request to an MEC strategy synchronization service network element, and the HTTP request is used for requesting to delete the uplink flow shunting strategy. The HTTP request includes: APP ID and DNAI.

S502, the MEC strategy synchronization service network element obtains the APP ID, obtains the session ID from the PDU session of the terminal equipment, and confirms whether all APPs on the terminal equipment do not need to access the corresponding MEC resources any more according to the APP ID, DNAI and PDU session ID.

S503, if all the related applications no longer access the MEC resources corresponding thereto, the MEC policy synchronization service network element initiates a request for deleting the upstream traffic offload policy to another core network element (e.g., NEF, PCF, or SMF). Optionally, if the terminal device further has another APP to access the MEC, the current APP (e.g., hua is a video) ID is deleted from the uplink traffic offload policy.

And S504, the terminal equipment deletes the uplink flow shunting strategy from the UPF on the MEC.

When other subsequent APPs (such as the ace art) of the terminal device re-issue network requests, the requests are directly shunted to other CDN nodes on the non-MEC.

According to the method for data transmission in the MEC, when the application on the terminal equipment does not access the MEC resource any more, the shunting strategy can be deleted from the MEC, the follow-up request flow is ensured not to forward to the MEC any more, the MEC resource is prevented from being occupied by the invalid flow, the utilization rate of the MEC resource is improved, and therefore the communication efficiency is improved.

It should be understood that the above description is only for the purpose of helping those skilled in the art better understand the embodiments of the present application, and is not intended to limit the scope of the embodiments of the present application. Various equivalent modifications or changes will be apparent to those skilled in the art in light of the above examples given, for example, some steps may not be necessary or some steps may be newly added in various embodiments of the above-described methods 200-500, etc. Or a combination of any two or more of the above embodiments. Such modifications, variations, or combinations are also within the scope of the embodiments of the present application.

It should also be understood that the foregoing descriptions of the embodiments of the present application focus on highlighting differences between the various embodiments, and that the same or similar elements that are not mentioned may be referred to one another and, for brevity, are not repeated herein.

It should also be understood that the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by the function and the inherent logic thereof, and should not constitute any limitation to the implementation process of the embodiments of the present application.

It should also be understood that in the embodiment of the present application, "preset" or "predefined" may be implemented by saving a corresponding code, table, or other manners that may be used to indicate related information in advance in a device (for example, including a terminal and a network device), and the present application is not limited to a specific implementation manner thereof.

It should also be understood that the manner, the case, the category, and the division of the embodiments are only for convenience of description and should not be construed as a particular limitation, and features in various manners, the category, the case, and the embodiments may be combined without contradiction.

It is also to be understood that the terminology and/or the description of the various embodiments herein is consistent and mutually inconsistent if no specific statement or logic conflicts exists, and that the technical features of the various embodiments may be combined to form new embodiments based on their inherent logical relationships.

The method for data transmission in the MEC according to the embodiment of the present application is described in detail above with reference to fig. 1 to 11. Hereinafter, a communication device according to an embodiment of the present application will be described in detail with reference to fig. 12 to 15.

Fig. 12 shows a schematic block diagram of a communication apparatus 600 according to an embodiment of the present application, where the communication apparatus 600 may correspond to the terminal device described in the foregoing methods 200 to 500, and may also be a chip or a component applied to the terminal device, and each module or unit of the communication apparatus 600 is respectively used to execute each action or process performed by the terminal device in the foregoing methods 200 to 500, and as shown in fig. 12, the communication apparatus 600 may include: a communication unit 610 and a processing unit 620. The communication unit (or may also be referred to as a transceiving unit) 610 is configured to perform specific signal transceiving under the driving of the processing unit 620.

A communication unit 610, configured to send first information to a core network element, where the first information includes: the cell identification of the terminal equipment and the identification of the first application initiated by the communication device;

the communication unit 610 is further configured to receive first response information from a network element of the core network in response to the first information, where the first response information includes: a data network access identifier DNAI corresponding to the cell identifier;

a communication unit 610, further configured to send a service request to a core network device, where the service request is used to request service data corresponding to the first application, and the service request includes the DNAI;

the communication unit 610 is further configured to receive second response information from the core network element in response to the service request, where the second response information includes: an identification of a mobile edge computing MEC platform corresponding to the DNAI and the location of the communication device and an identification of a content delivery network CDN node on the MEC platform.

According to the communication device provided by the application, in an MEC scene, before a user uses the communication device to start a specific application, the communication device can firstly determine the MEC platform which the user needs to access and the CDN edge node on the MEC platform according to a shunting strategy, and when the user formally initiates service access, the communication device performs service access according to the IP addresses of the MEC platform which the user needs to access and the CDN edge node on the MEC platform. Therefore, the synchronization of the shunting strategy is realized, the communication failure of the user caused by the distribution of the shunting strategy is avoided, the interruption of a communication link is avoided, and the user experience is improved.

Optionally, in some embodiments of the present application, the processing unit 620 is configured to obtain service data from the CDN node according to the identifier of the MEC platform and the identifier of the CDN node.

Optionally, in some embodiments of the present application, after the first application is ended, the communication unit 610 is further configured to send a first request to the core network device, where the first request is used to request to delete a offloading policy corresponding to the first application, where the offloading policy includes offloading policies respectively corresponding to multiple applications, and the offloading policy corresponding to the first application includes: the identifier of the first application, the identifier of the MEC platform accessed by the first application, and the identifier of the CDN node, where the first request includes: an identification of the first application and the DNAI.

Optionally, in some embodiments of the present application, after determining that all applications accessing the MEC platform are finished, the processing unit 620 uses the first request to delete the offloading policy.

Optionally, in some embodiments of the present application, the service request is a hypertext transfer protocol HTTP request.

Further, the communication device 600 may also be the storage unit, and the communication unit 610 may be a transceiver, an input/output interface, or an interface circuit. The storage unit is used for storing instructions executed by the communication unit 610 and the processing unit 620. The communication unit 610, the processing unit 620 and the storage unit are coupled to each other, the storage unit stores instructions, the processing unit 620 is used for executing the instructions stored by the storage unit, and the communication unit 610 is used for performing specific signal transceiving under the driving of the processing unit 620.

It should be understood that, for the sake of brevity, please refer to the description related to the terminal device in the foregoing embodiments in conjunction with the methods 200 to 500 and fig. 7 to 11, and please refer to the detailed description related to the above steps executed by each unit in the communication apparatus 600.

Optionally, the communication unit 610 may include a receiving unit (module) and a sending unit (module) for performing the steps of receiving and sending information by the terminal device in the embodiments illustrated in the foregoing 200 to 500 and fig. 7 to 11.

It should be understood that the communication unit 610 may be a transceiver, an input/output interface, or an interface circuit. The storage unit may be a memory. The processing unit 620 may be implemented by a processor. As shown in fig. 13, the communication device 700 may include a processor 710, a memory 720, a transceiver 730, and a bus system 740. The various components of the communication device 700 are coupled together by a bus system 440, wherein the bus system 740 may include a power bus, a control bus, a status signal bus, and the like, in addition to a data bus. For clarity of illustration, however, the various buses are labeled as bus system 740 in fig. 13. For ease of illustration, it is only schematically drawn in fig. 13.

The communication apparatus 600 shown in fig. 12 or the communication apparatus 700 shown in fig. 13 can implement the steps performed by the terminal device in the embodiments shown in fig. 7 to 11 and the aforementioned methods 200 to 500. Similar descriptions may refer to the description in the corresponding method previously described. To avoid repetition, further description is omitted here.

The communication apparatus 600 shown in fig. 12 or the communication apparatus 700 shown in fig. 13 may be a terminal device.

Fig. 14 shows a schematic block diagram of a communication apparatus 800 according to an embodiment of the present application, where the communication apparatus 800 may correspond to the core network element described in the foregoing methods 200 to 500, and may also be a chip or a component applied to the core network element, and modules or units of the communication apparatus 800 are respectively configured to execute actions or processes executed by the core network element in the foregoing methods 200 to 500, as shown in fig. 14, and the communication apparatus 800 may include: a communication unit 810 and a processing unit 820. The communication unit (or may also be referred to as a transceiving unit) 810 is configured to perform specific signal transceiving under the driving of the processing unit 820.

A communication unit 810, configured to receive first information from a terminal device, where the first information includes: the cell identification of the terminal equipment and the identification of the first application initiated by the terminal equipment;

A communication unit 810, further configured to send first response information in response to the first information to the terminal device, where the first response information includes: a data network access identifier DNAI corresponding to the cell identifier;

a communication unit 810, further configured to receive a service request from the terminal device, where the service request is used to request service data corresponding to the first application, and the service request includes the DNAI;

the communication unit 810 is further configured to send, to the terminal device, second response information in response to the service request, where the second response information includes: and calculating the identifier of the MEC platform and the identifier of the CDN node of the content delivery network on the MEC platform by the mobile edge corresponding to the DNAI and the position of the terminal equipment.

According to the communication device provided by the application, before a user starts a specific application, the communication device firstly determines a shunting strategy, determines an MEC platform which the user needs to access and CDN edge nodes on the MEC platform according to the shunting strategy, and feeds back the MEC platform and the CDN edge nodes on the MEC platform to a terminal device. The terminal device can perform service access according to the MEC platform to be accessed and the IP address of the CDN edge node on the MEC platform. Therefore, the synchronization of the shunting strategy is realized, the communication failure of the user caused by the distribution of the shunting strategy is avoided, the interruption of a communication link is avoided, and the user experience is improved.

Optionally, in some embodiments of the present application, the processing unit 820 is configured to generate a offloading policy according to the first information, where the offloading policy includes offloading policies respectively corresponding to a plurality of applications, and the offloading policy corresponding to the first application includes: the identity of the first application, the identity of the MEC platform accessed by the first application, and the identity of the CDN node.

Optionally, in some embodiments of the present application, the communication unit 810 is further configured to send the offloading policy to the first network element.

Optionally, in some embodiments of the present application, after the first application is ended, the communication unit 810 is further configured to receive a first request from the terminal device, where the first request is used to request to delete a offloading policy corresponding to the first application, and the first request includes: an identification of the first application and the DNAI.

Optionally, in some embodiments of the present application, after determining that all applications accessing the MEC platform end, the first request is used to request to delete the offloading policy.

Optionally, in some embodiments of the present application, the communication device may be an MEC policy synchronization service network element.

Optionally, in some embodiments of the present application, the first network element is a UPF network element on the MEC platform.

In a possible design, the communication apparatus 800 may be an MEC policy synchronization service network element, a GSLB network element, a PCF network element, or an SMF network element in the foregoing method embodiment. Or may be a chip used for implementing the functions of the MEC policy synchronization service network element, the GSLB network element, the PCF network element, or the SMF network element in the foregoing method embodiments. Also, the units and other operations and/or functions described above in the communication apparatus 800 are respectively for implementing the methods 200 to 500 and the corresponding flows in fig. 7 to 11. It should be understood that the specific processes of the units for executing the corresponding steps are already described in detail in the above method embodiments, and therefore, for brevity, detailed descriptions thereof are omitted.

Further, the communication device 800 may also be the storage unit, and the communication unit 810 may be a transceiver, an input/output interface, or an interface circuit. The storage unit is used for storing instructions executed by the communication unit 810 and the processing unit 820. The communication unit 810, the processing unit 820 and the storage unit are coupled to each other, the storage unit stores instructions, the processing unit 820 is used for executing the instructions stored by the storage unit, and the communication unit 810 is used for performing specific signal transceiving under the driving of the processing unit 620.

It should be understood that, for the specific process of each unit in the communication apparatus 800 to execute the corresponding step described above, please refer to the description related to the MEC policy synchronization service network element, the core network element, or the GSLB network element in the foregoing with reference to the methods 200 to 500 and the related embodiments in fig. 7 to 11, and for brevity, no further description is provided here.

Optionally, the communication unit 810 may include a receiving unit (module) and a sending unit (module) for performing the steps of receiving and sending information by the MEC policy synchronization service network element, the core network element, or the GSLB network element in the foregoing embodiments 200 to 500 and shown in fig. 7 to 11.

It should be understood that the communication unit 810 may be a transceiver, an input/output interface, or an interface circuit. The storage unit may be a memory. The processing unit 820 may be implemented by a processor. As shown in fig. 15, the communication device 900 may include a processor 910, a memory 920, and a transceiver 930.

The communication apparatus 800 shown in fig. 14 or the communication apparatus 900 shown in fig. 15 can implement the steps performed by the foregoing methods 200 to 500, and the MEC policy synchronization service network element, the core network element, or the GSLB network element in the embodiments shown in fig. 7 to 11. Similar descriptions may refer to the description in the corresponding method previously described. To avoid repetition, further description is omitted here.

The communication apparatus 800 shown in fig. 14 or the communication apparatus 900 shown in fig. 15 may be an MEC policy synchronization service network element, a core network element, or a GSLB network element.

It should also be understood that the division of the units in the above apparatus is only a division of logical functions, and the actual implementation may be wholly or partially integrated into one physical entity, or may be physically separated. And the units in the device can be realized in the form of software called by the processing element; or may be implemented entirely in hardware; part of the units can also be realized in the form of software called by a processing element, and part of the units can be realized in the form of hardware. For example, each unit may be a processing element separately set up, or may be implemented by being integrated into a chip of the apparatus, or may be stored in a memory in the form of a program, and a function of the unit may be called and executed by a processing element of the apparatus. The processing element, which may also be referred to herein as a processor, may be an integrated circuit having signal processing capabilities. In the implementation process, the steps of the method or the units above may be implemented by integrated logic circuits of hardware in a processor element or in a form called by software through the processor element.

In one example, the units in any of the above apparatuses may be one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more Digital Signal Processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), or a combination of at least two of these integrated circuit forms. As another example, when a unit in a device may be implemented in the form of a processing element scheduler, the processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of invoking programs. As another example, these units may be integrated together and implemented in the form of a system-on-a-chip (SOC).

Embodiments of the present application further provide a computer-readable storage medium for storing a computer program code, where the computer program includes instructions for executing the method 200 to 500 described above, and the method for data transmission in the MEC of the embodiments of the present application. The readable medium may be a read-only memory (ROM) or a Random Access Memory (RAM), which is not limited in this embodiment of the present application.

The present application further provides a computer program product comprising instructions that, when executed, cause the terminal device, the MEC policy synchronization service network element, the core network element, or the GSLB network element to perform operations of the terminal device, the MEC policy synchronization service network element, the core network element, or the GSLB network element corresponding to the above methods.

An embodiment of the present application further provides a chip located in a communication device, where the chip includes: a processing unit, which may be, for example, a processor, and a communication unit, which may be, for example, an input/output interface, a pin or a circuit, etc. The processing unit may execute computer instructions to enable the communication device to execute any one of the methods for data transmission in an MEC provided by the embodiments of the present application.

Optionally, the computer instructions are stored in a storage unit.

Alternatively, the storage unit is a storage unit in the chip, such as a register, a cache, and the like, and the storage unit may also be a storage unit located outside the chip in the terminal, such as a read-only memory (ROM) or another type of static storage device that can store static information and instructions, a Random Access Memory (RAM), and the like. The processor mentioned in any of the above may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits for executing programs for controlling the transmission method of the feedback information. The processing unit and the storage unit may be decoupled, and are respectively disposed on different physical devices, and are connected in a wired or wireless manner to implement respective functions of the processing unit and the storage unit, so as to support the system chip to implement various functions in the foregoing embodiments. Alternatively, the processing unit and the memory may be coupled to the same device.

It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a ROM, a Programmable Read Only Memory (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash memory. Volatile memory can be RAM, which acts as external cache memory. There are many different types of RAM, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), synclink DRAM (SLDRAM), and direct bus RAM (DRRAM).

The terms "upstream" and "downstream" appearing in the present application are used to describe the direction of data/information transmission in a specific scenario, for example, the "upstream" direction generally refers to the direction of data/information transmission from the terminal to the network side, or the direction of transmission from the distributed unit to the centralized unit, and the "downstream" direction generally refers to the direction of data/information transmission from the network side to the terminal, or the direction of transmission from the centralized unit to the distributed unit.

Various objects such as various messages/information/devices/network elements/systems/devices/actions/operations/procedures/concepts may be named in the present application, it is to be understood that these specific names do not constitute limitations on related objects, and the named names may vary according to circumstances, contexts, or usage habits, and the understanding of the technical meaning of the technical terms in the present application should be mainly determined by the functions and technical effects embodied/performed in the technical solutions.

In the embodiments of the present application, unless otherwise specified or conflicting with respect to logic, the terms and/or descriptions in different embodiments have consistency and may be mutually cited, and technical features in different embodiments may be combined to form a new embodiment according to their inherent logic relationship.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The methods in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer program or instructions may be stored in or transmitted over a computer-readable storage medium. The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server that integrates one or more available media.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a readable storage medium, which includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method described in the embodiments of the present application. And the aforementioned readable storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for data transmission in an MEC, comprising:

the method comprises the steps that terminal equipment sends first information to a core network element, wherein the first information comprises: the cell identification of the terminal equipment and the identification of the first application initiated by the terminal equipment;

the terminal device receives first response information from the core network element in response to the first information, where the first response information includes: a data network access identifier DNAI corresponding to the cell identifier;

the terminal equipment sends a service request to the core network element, wherein the service request is used for requesting service data corresponding to the first application, and the service request comprises the DNAI;

the terminal device receives second response information from the core network element in response to the service request, where the second response information includes: and calculating the identifier of the MEC platform and the identifier of the CDN node of the content delivery network on the MEC platform by the mobile edge corresponding to the DNAI and the position of the terminal equipment.

2. The method of claim 1, further comprising: and the terminal equipment acquires service data from the CDN node according to the identifier of the MEC platform and the identifier of the CDN node.

3. The method according to claim 1 or 2, wherein after the first application is ended, the method further comprises:

the terminal device sends a first request to the core network element, where the first request is used to request deletion of a offloading policy corresponding to the first application, the offloading policy includes offloading policies corresponding to a plurality of applications, and the offloading policy corresponding to the first application includes: the identifier of the first application, the identifier of the MEC platform accessed by the first application, and the identifier of the CDN node, and the first request includes: an identification of the first application and the DNAI.

4. The method of claim 3, wherein the first request is configured to request deletion of the offload policy after determining that all applications accessing the MEC platform are finished.

5. The method according to any of claims 1 to 4, wherein the service request is a Hypertext transfer protocol, HTTP, request.

6. A method for data transmission in an MEC, comprising:

a core network element receives first information from a terminal device, where the first information includes: the cell identification of the terminal equipment and the identification of the first application initiated by the terminal equipment;

The core network element sends first response information responding to the first information to the terminal equipment, wherein the first response information comprises: a data network access identifier DNAI corresponding to the cell identifier;

the core network element receives a service request from the terminal device, wherein the service request is used for requesting service data corresponding to the first application, and the service request comprises the DNAI;

the core network element sends second response information responding to the service request to the terminal equipment, wherein the second response information comprises: and calculating the identifier of the MEC platform and the identifier of the CDN node of the content delivery network on the MEC platform by the mobile edge corresponding to the DNAI and the position of the terminal equipment.

7. The method of claim 6, further comprising:

the core network element generates a offloading policy according to the first information, where the offloading policy includes offloading policies corresponding to a plurality of applications, respectively, and the offloading policy corresponding to the first application includes: the identifier of the first application, the identifier of the MEC platform accessed by the first application, and the identifier of the CDN node.

8. The method of claim 7, wherein the core network element sends the offloading policy to the first network element.

9. The method according to claim 7 or 8, wherein after the first application is ended, the method further comprises:

the core network element receives a first request from the terminal device, where the first request is used to request to delete a offloading policy corresponding to the first application, and the first request includes: an identification of the first application and the DNAI.

10. The method of claim 9, wherein the first request is configured to request deletion of the offload policy after determining that all applications accessing the MEC platform are finished.

11. Method according to any of claims 6 to 10, wherein said service request is a hypertext transfer protocol, HTTP, request.

12. The method according to any of claims 6 to 11, wherein the core network element is an MEC policy synchronization service network element.

13. The method of claim 8, wherein the first network element is a User Plane Function (UPF) network element on the MEC platform.

14. A communication apparatus, comprising means for performing the steps of the method according to any of claims 1 to 5.

15. A communication apparatus, characterized by comprising means for performing the steps of the method according to any of claims 6 to 13.

16. A communications device comprising at least one processor and interface circuitry for the at least one processor to retrieve a program or instructions in at least one memory, the at least one processor to execute the program or instructions to cause the communications device to perform the method of any of claims 1 to 5.

17. A communications device comprising at least one processor and interface circuitry for the at least one processor to retrieve a program or instructions in at least one memory, the at least one processor to execute the program or instructions to cause the communications device to perform the method of any of claims 6 to 13.

18. A chip system, comprising: a processor for calling and running a computer program from a memory so that a communication device in which the system-on-chip is installed performs the method of any one of claims 1 to 5, or the method of any one of claims 6 to 13.

19. A computer-readable storage medium, in which a program is stored which, when executed by at least one processor, causes the method of any one of claims 1 to 5 to be performed, or causes the method of any one of claims 6 to 13 to be performed.