Multi-layer heterogeneous MEC, auxiliary terminal automatic moving method, device and medium

CN117939404BActive Publication Date: 2026-10-30CHINA UNITED NETWORK COMM GRP CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202410114731.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-01-26
Publication Date
2026-10-30
Estimated Expiration
2044-01-26

AI Technical Summary

Technical Problem

[0004]本公开所要解决的技术问题是针对上述不足,提供一种多层异构MEC、辅助终端自动移动方法、辅助终端自动移动装置及计算机可读存储介质,以解决如何将边缘算力下沉端侧的问题

Benefits of technology

[0018]本公开提供一种多层异构MEC、辅助终端自动移动方法、辅助终端自动移动装置及计算机可读存储介质,通过设置包括R-MEP的MEC架构,且将R-MEP部署于通信网络的基站和UPF之间,由R-MEP承担UE的至少一部分计算服务,实现将边缘算力下沉端侧,使得边缘算力资源贴近业务侧,减弱对终端设备的算力要求。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117939404B_ABST
    Figure CN117939404B_ABST
Patent Text Reader

Abstract

The present disclosure provides a multi-layer heterogeneous MEC, an auxiliary terminal automatic moving method, device and medium, relates to the technical field of edge computing, and is used for solving the problem of how to sink edge computing power to the terminal side. The multi-layer heterogeneous MEC comprises a remote multi-access edge computing platform R-MEP, the R-MEP is deployed between a base station and a user plane function UPF of a communication network in a light weight manner, so that the R-MEP is sunk to the terminal side; an MEP is connected with the R-MEP, is used for acquiring the computing requirement of a UE, and provides computing services for the UE in cooperation with the R-MEP according to the computing requirement; and a MEO is connected with the MEP, and is used for overall arrangement and scheduling of the multi-layer heterogeneous MEC. The present disclosure adds the R-MEP, and deploys the R-MEP between the base station and the UPF of the communication network. At least part of the computing services of the UE are borne by the R-MEP, edge computing power is sunk to the terminal side, edge computing power resources are close to the business side, and the requirement for the computing power of the terminal device is weakened.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates at least to the field of edge computing technology, and in particular to a multi-layer heterogeneous MEC, an automatic movement method for assisted terminals, an automatic movement device for assisted terminals, and a computer-readable storage medium. Background Technology

[0002] The main characteristic of MEC (Multi-Access Edge Computing) is that it pushes mobile computing, network control, and storage to the network edge, enabling mobile devices to support compute-intensive and latency-sensitive applications. Common MEC architectures include... Figure 1 As shown, the architecture is a three-tier structure: MEO (MEC Orchestrator), MEPM (MEC Platform Manager), and MEP (MEC Platform). MEO connects to MEPM via the Mm3 interface, MEPM connects to MEP via the Mm5 interface, and there are multiple MEPs located at different edges. Each MEP includes several MEC APPs (applications) to provide connectivity and management services for different scenarios. MEC APPs connect to several MEC Services via the Mp1 interface to provide computing services to terminals. Different MEPs can connect via the Mp3 interface, and MEPs connect to the DP (data plane) via the N6 and Mp2 interfaces.

[0003] Because the current MEC system (MEO / MEPM / MEP architecture) is deployed at a relatively high location, most shared MEPs are deployed in prefecture-level cities, a few in districts and counties, and dedicated MEPs are deployed in industrial parks. In reality, the so-called MEP deployment at the edge of the current MEC system is the edge of the operator and the edge of the network, which is far away from the actual production end business. This results in the current MEP infrastructure being limited, the scheduling of computing network capabilities being inflexible, and the computing power for the edge being insufficient, especially in scenarios such as autonomous driving, where the computing power requirements for terminal devices are high. Summary of the Invention

[0004] The technical problem to be solved by this disclosure is to address the above-mentioned shortcomings by providing a multi-layer heterogeneous MEC, an automatic mobile method for auxiliary terminals, an automatic mobile device for auxiliary terminals, and a computer-readable storage medium, so as to solve the problem of how to bring edge computing power down to the terminal side.

[0005] In a first aspect, this disclosure provides a multi-layer heterogeneous multi-access edge computing (MEC) including:

[0006] The Remote Multi-Access Edge Computing Platform (R-MEP) is deployed in a lightweight manner between the base station and the User Plane Function (UPF) of the communication network, so that R-MEP can be brought to the edge.

[0007] The Multi-Access Edge Computing Platform (MEP) connects to the R-MEP to obtain the computing requirements of the User Equipment (UE) and collaborates with the R-MEP to provide computing services to the UE based on these requirements.

[0008] The Multi-Access Edge Computing Orchestrator (MEO), connected to the MEP, is used for the overall orchestration and scheduling of multi-layer heterogeneous MECs.

[0009] Secondly, this disclosure provides an auxiliary terminal automatic movement method, the method being applied to the multi-layer heterogeneous MEC as described above, and comprising:

[0010] R-MEP receives base station location information acquisition requests from multiple UEs from MEP;

[0011] R-MEP obtains the base station location information of the multiple UEs from the base station according to the base station location information acquisition request;

[0012] R-MEP sends the base station location information of the multiple UEs to MEP, so that MEP can obtain the final location information of the multiple UEs based on the base station location information, and assist the multiple UEs to move automatically based on the final location information.

[0013] Thirdly, this disclosure provides an auxiliary terminal automatic movement device, which is disposed in the multi-layer heterogeneous MEC as described above, and includes an R-MEP, wherein the R-MEP includes:

[0014] The first receiving unit is used to receive base station location information acquisition requests from multiple UEs of the MEP;

[0015] The first acquisition unit, connected to the first receiving unit, is used to acquire base station location information of the plurality of UEs from the base station according to the base station location information acquisition request;

[0016] The first sending unit, connected to the first acquiring unit, sends the base station positioning information of the plurality of UEs to the MEP, so that the MEP can obtain the final positioning information of the plurality of UEs based on the base station positioning information, and assist the plurality of UEs in automatic movement based on the final positioning information.

[0017] Fourthly, this disclosure provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the automatic movement method for an auxiliary terminal as described above.

[0018] This disclosure provides a multi-layer heterogeneous MEC, an automatic mobility assistance method for assisted terminals, an automatic mobility assistance device for assisted terminals, and a computer-readable storage medium. By setting up an MEC architecture including an R-MEP and deploying the R-MEP between the base station and the UPF in the communication network, the R-MEP undertakes at least a portion of the computing services of the UE, thereby sinking edge computing power to the terminal side, making edge computing resources closer to the service side, and reducing the computing power requirements of the terminal device. Attached Figure Description

[0019] Figure 1 This is an existing MEC architecture diagram;

[0020] Figure 2 This is an architecture diagram of a multi-layer heterogeneous MEC according to an embodiment of this disclosure;

[0021] Figure 3 This is a flowchart of an auxiliary terminal automatic movement method according to an embodiment of the present disclosure;

[0022] Figure 4 This is a schematic diagram of a collision probability analysis method according to an embodiment of this disclosure;

[0023] Figure 5 This is a schematic diagram of the structure of an auxiliary terminal automatic moving device according to an embodiment of the present disclosure. Detailed Implementation

[0024] To enable those skilled in the art to better understand the technical solutions of this disclosure, the embodiments of this disclosure will be further described in detail below with reference to the accompanying drawings.

[0025] It is understood that the specific embodiments and accompanying drawings described herein are for illustrative purposes only and are not intended to limit the scope of this disclosure.

[0026] It is understood that, without conflict, the various embodiments and features in the embodiments of this disclosure can be combined with each other.

[0027] It is understood that, for ease of description, only the parts relevant to this disclosure are shown in the accompanying drawings, while parts unrelated to this disclosure are not shown in the drawings.

[0028] It is understood that each unit or module involved in the embodiments of this disclosure may correspond to only one entity structure, or may be composed of multiple entity structures, or multiple units or modules may be integrated into one entity structure.

[0029] It is understood that, without conflict, the functions and steps marked in the flowcharts and block diagrams of this disclosure may occur in a different order than that marked in the accompanying drawings.

[0030] It is understood that the flowcharts and block diagrams of this disclosure illustrate the architecture, functions, and operations of possible implementations of systems, apparatuses, devices, and methods according to various embodiments of this disclosure. Each block in a flowchart or block diagram may represent a unit, module, program segment, or code, containing executable instructions for implementing the specified function. Furthermore, each block or combination of blocks in the block diagrams and flowcharts may be implemented using a hardware-based system to implement the specified function, or using a combination of hardware and computer instructions.

[0031] It is understood that the units and modules involved in the embodiments of this disclosure can be implemented by software or by hardware, for example, the units and modules can be located in a processor.

[0032] Example 1:

[0033] like Figure 2 As shown, this disclosure provides a multi-layer heterogeneous multi-access edge computing (MEC) including:

[0034] The Remote Multi-Access Edge Computing Platform (R-MEP) is deployed in a lightweight manner between the base station and the User Plane Function (UPF) of the communication network, so that R-MEP can be brought to the edge.

[0035] The Multi-Access Edge Computing Platform (MEP) connects to the R-MEP to obtain the computing requirements of the User Equipment (UE) and collaborates with the R-MEP to provide computing services to the UE based on these requirements.

[0036] The Multi-Access Edge Computing Orchestrator (MEO), connected to the MEP, is used for the overall orchestration and scheduling of multi-layer heterogeneous MECs.

[0037] In this embodiment, a novel architecture, MEO / MEP / R-MEP (Remote MEP, Remote Multi-Access Edge Computing Platform), is proposed. This architecture aims to bring edge computing resources closer to the service side (i.e., the end-user side), reducing the computing power requirements on terminal devices (UEs) and shifting end-user computing power demands to the edge computing platform. Specifically... Figure 2 As shown, the MEPM layer is removed and an R-MEP layer is added on the basis of the original architecture. R-MEP is only deployed as a lightweight MEP. R-MEP is not deployed directly on the same platform as UPF (User Plane Function). R-MEP is deployed between the base station and UPF, as close as possible to the end device. Through this improved edge computing architecture, the R-MEP module (ultra-edge module) is added. R-MEP undertakes at least part of the UE's computing services. R-MEP is close to the service side to enhance the service side's perception.

[0038] In one implementation, the lightweight deployment of R-MEP includes at least one of the following:

[0039] R-MEP uses an x86 or ARM central processing unit (CPU);

[0040] R-MEP's operating system uses the container cluster management system Kubernetes;

[0041] R-MEP deploys customized applications, which are connected to general applications deployed in MEP. The customized applications provide the UE with the first computing service, while the general applications provide the UE with the second computing service.

[0042] In this embodiment, the lightweight nature of R-MEP is reflected in the following aspects: In terms of hardware form, it adopts an X86 (Intel x86) / ARM (ARM chip) CPU (Central Processing Unit). R-MEP can support either X86 or ARM, mainly depending on the deployment scenario. Traditional MEPs generally support X86, therefore R-MEP is more flexible than MEP and more suitable for proximity to the business end; in terms of hardware size, it is smaller than MEP, such as being integrated into handheld terminals or inserted into base station equipment room card slots; the operating system can be a lightweight k8s (Kubernetes, a container cluster management system), with lower requirements than MEP; and it has fewer deployment functions than MEP, generally deploying customized applications strongly related to the deployment scenario. For example, in industry, it can deploy intelligent sorting applications for a specific fixed product, while MEP deployment functions are more generalized.

[0043] In one embodiment, the R-MEP recessed end side further includes at least one of the following:

[0044] R-MEP offloads traffic to the base station through the data plane DP module;

[0045] R-MEP and MEP edge UPF connection;

[0046] R-MEP is co-located with the base station.

[0047] In this embodiment, the R-MEP directly offloads traffic from the base station side through the DP (data plane) module and connects to the edge UPF of the MEP. The DP serves as the offloading module between the MEC and the 5G network element, utilizing the existing N3 interface between the gNB (gNodeB, 5G base station) and the UPF. The RAN (Radio Access Network)... The network path is RAN->DP->UPF, meaning that an R-MEP has been added between the gNB and UPF. The current N3 performs dual backups on the original transmission information: part goes directly to UPF (RAN->UPF is to ensure uninterrupted sessions), and part goes to UPF via R-MEP (for rapid traffic offloading). R-MEP can be co-located with the base station. For example, base station equipment rooms are typically expanded before 50% of the card slots are filled, leaving spare slots. These extra slots provide a geographical location for R-MEP deployment. R-MEP is close to the service production line, has a flexible form factor, and co-location with the base station is beneficial for obtaining information from the base station. For example, to solve the collision avoidance problem of intelligent vehicles in industrial scenarios, it is convenient to open up wireless side information and sense the terminal location.

[0048] More specifically, such as Figure 2 As shown, in this embodiment, the MEO of the multi-layer heterogeneous MEC is responsible for overall orchestration and scheduling, and may include an APP Store, OSS (Operation Support Systems), and customer self-service functions. The MEO and MEP are connected through China Unicom's CUII large customer bearer network. The MEP consists of multiple MEC nodes, each of which deploys the necessary MEC APP, runs the corresponding MEC Service, and is equipped with an edge UPF. The MEP can be a standard x86 cluster. The MEP and R-MEP are connected through 5G networks, wired backhaul, etc. The R-MEP consists of multiple R-MEC devices, each of which deploys a lightweight MEP and is equipped with a DP. The R-MEC devices can use low-power chips, such as ARM A7, Atom, etc.

[0049] Example 2:

[0050] like Figure 3 As shown, this disclosure provides an auxiliary terminal automatic movement method, which is applied to a multi-layer heterogeneous MEC as described in Embodiment 1, and includes:

[0051] S11, R-MEP receives base station location information acquisition requests from multiple UEs from MEP;

[0052] S12, R-MEP obtains the base station location information of the multiple UEs from the base station according to the base station location information acquisition request;

[0053] S13, R-MEP sends the base station positioning information of the multiple UEs to MEP, so that MEP can obtain the final positioning information of the multiple UEs based on the base station positioning information, and assist the multiple UEs to move automatically based on the final positioning information.

[0054] In this embodiment, based on the multi-layer heterogeneous MEC deployment scenario described in Embodiment 1, a collision avoidance method for autonomous driving terminals (such as industrial AGVs, driverless cars, and park logistics robots) is provided. This method mainly involves opening up wireless side information through R-MEP to sense the terminal position and sending the terminal position information (UE's base station positioning information) obtained from the base station to the MEP, so that the MEP can perform more accurate positioning to assist in autonomous driving calculations, enhance the perception of network resources of end-side devices, assist in autonomous driving, and realize intelligent driving.

[0055] In one embodiment, the method further includes:

[0056] MEP acquires self-location information and movement information of multiple UEs;

[0057] MEP sends a request to R-MEP to obtain the base station location information of the multiple UEs;

[0058] MEP obtains the final location information of the multiple UEs based on self-location information and base station location information;

[0059] MEP assists the multiple UEs in automatic movement based on the final location information and mobility information.

[0060] In this embodiment, the MEP performs dual positioning based on the UE's base station positioning information and self-positioning information to achieve dual error correction positioning for the UE. Then, based on this positioning, anti-collision analysis is performed, and the anti-collision analysis results assist in autonomous driving. The self-positioning information can be the UE's own GPS (Global Positioning System) positioning information, etc. By improving positioning accuracy through dual positioning, better assistance is provided for the UE's automatic movement.

[0061] In one implementation, the MEP acquires self-location information and mobility information of multiple UEs, specifically including:

[0062] The first MEP receives self-location information and movement information from multiple first UEs connected to it; and / or;

[0063] With the assistance of MEO, the first MEP acquires the self-location information and movement information of multiple second UEs connected to the second MEP.

[0064] In this embodiment, the UE uses the MEP to share its own location and orientation with other UEs in real time. These UEs include those connected to the same MEP and those connected to different MEPs. UEs connected to different MEPs can share information through MEO to assist in the execution of intelligent collision prevention for autonomous driving.

[0065] In one embodiment, the first MEP, with the assistance of the MEO, acquires the self-location information and mobility information of multiple second UEs connected to the second MEP, specifically including:

[0066] MEO receives self-location information and mobility information of the first UE and the second UE respectively sent by the first MEP and the second MEP.

[0067] In response to determining that a collision is possible between the first UE and the second UE based on the self-location information and movement information of the first UE and the second UE, the MEO sends the self-location information and movement information of the second UE to the first MEP and / or sends the self-location information and movement information of the first UE to the second MEP.

[0068] In this embodiment, UEs accessing the same MEP periodically send their self-location information and mobility information to the MEPs they are accessing. UEs accessing different MEPs achieve information sharing through MEO assistance. MEO can determine whether it is necessary to share UE information between MEPs based on information such as whether different MEPs are adjacent.

[0069] In one embodiment, the MEP obtains the final location information of the plurality of UEs based on self-location information and base station location information, specifically including:

[0070] If the difference between the self-location information and the base station location information of the same UE is greater than a preset threshold, the MEP re-acquires the self-location information and the base station location information of the same UE; otherwise, the MEP uses the base station location information as the final location information of the same UE.

[0071] In this embodiment, if the GPS positioning accuracy of the UE itself is <10 meters and the positioning accuracy of the base station is <3 meters, and a huge difference is found between the two positioning results, it is considered as erroneous data and a new positioning request is made; otherwise, the base station positioning information can be used as the positioning result of the UE.

[0072] In one embodiment, the MEP assists the multiple UEs in automatic movement based on final location information and movement information, specifically including:

[0073] MEP predicts the possible trajectory range of the multiple UEs within a preset time threshold based on the final location information and mobility information;

[0074] MEP predicts the probability of a collision between a UE and other UEs among the multiple UEs based on the possible trajectory range;

[0075] The MEP sends the collision probability to a specific UE so that the specific UE can avoid colliding with other UEs based on the collision probability.

[0076] In this embodiment, one of the important goals of assisted autonomous driving is to prevent the terminal from colliding. The collision avoidance analysis method can be as follows: Figure 4 As shown, assuming all UE terminals move forward at a constant speed, if it is predicted that a UE may collide with another UE on its possible trajectory (a circle with radius r = v * t in the figure) at a certain time threshold t under the current speed v and direction, there is a possibility of collision.

[0077] More specifically, the automatic movement method for the auxiliary terminal may include the following steps:

[0078] 1. User login, accessing edge applications:

[0079] The UE connects to the local MEC APP through the client APP. Specifically, it establishes a TCP connection to the MEC application through the MEC DNS, resolves known domain names, and the MEC APP forwards the client authentication request to the central cloud. The cloud backend responds to the client access request based on the credentials.

[0080] Second, location sharing and pre-collision between UEs, including:

[0081] In a single MEP access scenario, terminals share location information. The UE uses GPS for self-positioning. The client APP periodically shares location, measurement time, direction, and speed with the MEC APP. The base station is used to locate the UE. The MEC APP accumulates the client's location and simultaneously requests the current UE location from the radio side. The MEC APP requests the MEP to open the geographical location information of the currently accessing terminal through the MP1 interface. The MEP requests the location of the currently accessing UE from the R-MEC through the MR1 interface. The R-MEC is co-located with the base station. The R-MEC<->DP<->gNb obtains the location information of the base station and requests the base station to open RAN info (information) through the N3 interface.

[0082] In cross-MEP access, terminals share locations. With the assistance of MEP / MEO, MEC1 APP needs to discover other MEC2 APP instances and their physical locations, and periodically share the list of client information currently served by the MEC1 APP instance with MEC2 APP. MEC2 APP then passes this information to the Client APP it serves.

[0083] Collision avoidance analysis involves the MEC APP updating the locations of all other connected clients (including GPS and base station location information for the connected UE) to each already connected client. Both GPS and base station positioning are used simultaneously for each client. If a significant discrepancy is found between the two positioning results, it is considered erroneous data, and a new positioning request is made, repeating the process synchronously. Figure 4 The MEC APP analyzes the data to calculate the probability of a collision between its current location and the locations of nearby clients, and then returns the analysis results to the client APP.

[0084] Third, regularly update user information:

[0085] The MEC1 / 2APP regularly updates the latest information of all clients under its service list to the cloud. This upload frequency is lower than the update frequency between MEC1 / 2APPs and between MEC APP and Client APP. The purpose is to train models and modify MEC APP versions in the cloud based on the behavior data of the access terminals.

[0086] 4. End, log out:

[0087] If a client does not initiate access to the MEC APP for an extended period of time (i.e., the client is disconnected by default), the MEC APP will update the latest context of the client stored in the central cloud and send a log off message to delete the authentication token and the client context.

[0088] Example 3:

[0089] like Figure 5 As shown, this disclosure provides an auxiliary terminal automatic mobility device, which is disposed in a multi-layer heterogeneous MEC as described in Embodiment 1, and includes an R-MEP, wherein the R-MEP includes:

[0090] The first receiving unit is used to receive base station location information acquisition requests from multiple UEs of the MEP;

[0091] The first acquisition unit, connected to the first receiving unit, is used to acquire the base station location information of the plurality of UEs from the base station according to the base station location information acquisition request;

[0092] The first sending unit, connected to the first acquiring unit, sends the base station positioning information of the plurality of UEs to the MEP, so that the MEP can obtain the final positioning information of the plurality of UEs based on the base station positioning information, and assist the plurality of UEs in automatic movement based on the final positioning information.

[0093] In one embodiment, the assisted terminal automatic mobility device further includes a MEP, the MEP comprising:

[0094] The second acquisition unit is used to acquire the self-location information and movement information of multiple UEs;

[0095] The second sending unit, connected to the second obtaining unit, is used to send a request to the R-MEP to obtain the base station location information of the plurality of UEs;

[0096] The final positioning unit, connected to the second sending unit, is used to obtain the final positioning information of the multiple UEs based on self-positioning information and base station positioning information;

[0097] An auxiliary mobility unit, connected to the final positioning unit, is used to assist the multiple UEs in automatic movement based on the final positioning information and mobility information.

[0098] In one embodiment, the second acquisition unit specifically includes:

[0099] The self-connection information acquisition unit is used to receive self-location information and movement information of multiple first UEs connected to itself;

[0100] The heterogeneous connection information acquisition unit is used to acquire the self-location information and mobility information of multiple second UEs connected to the second MEP itself with the assistance of MEO.

[0101] In one embodiment, the heterogeneous connection information acquisition unit is specifically used for:

[0102] MEO receives self-location information and mobility information of the first UE and the second UE respectively sent by the first MEP and the second MEP.

[0103] In response to determining that a collision is possible between the first UE and the second UE based on the self-location information and movement information of the first UE and the second UE, the MEO sends the self-location information and movement information of the second UE to the first MEP and / or sends the self-location information and movement information of the first UE to the second MEP.

[0104] In one embodiment, the final positioning unit is specifically used for:

[0105] If the difference between the self-location information and the base station location information of the same UE is greater than a preset threshold, the self-location information and the base station location information of the same UE are reacquired; otherwise, the base station location information is used as the final location information of the same UE.

[0106] In one embodiment, the auxiliary moving unit specifically includes:

[0107] The trajectory prediction unit is used to predict the possible trajectory range of the multiple UEs within a preset time threshold based on the final location information and movement information.

[0108] The collision prediction unit, connected to the trajectory prediction unit, is used to predict the probability of a collision between a UE and other UEs among the multiple UEs based on the possible trajectory range.

[0109] The third transmitting unit, connected to the collision prediction unit, is used to transmit the collision probability to the UE so that the UE can avoid colliding with other UEs based on the collision probability.

[0110] Example 4:

[0111] Embodiment 4 of this disclosure provides a computer-readable storage medium storing a computer program. When the computer program is run by a processor, it implements the automatic movement method for an auxiliary terminal as described in Embodiment 2, or the automatic movement device for an auxiliary terminal as described in Embodiment 3.

[0112] The computer-readable storage medium includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules, or other data). Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other memory technologies, CD-ROM (Compact Disc Read-Only Memory), DVD or other optical disc storage, cartridges, magnetic tapes, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer.

[0113] In addition, this disclosure may also provide a computer device including a memory and a processor, wherein the memory stores a computer program, and when the processor runs the computer program stored in the memory, the processor executes the automatic movement method for an auxiliary terminal as described in Embodiment 2, and the computer device may be the automatic movement device for an auxiliary terminal as described in Embodiment 3.

[0114] The memory is connected to the processor. The memory can be flash memory, read-only memory or other types of memory. The processor can be a central processing unit or a microcontroller.

[0115] Embodiments 1-4 of this disclosure provide a multi-layer heterogeneous MEC, an automatic mobile assisted terminal method, an automatic mobile assisted terminal device, and a computer-readable storage medium. By setting up an MEC architecture including an R-MEP and deploying the R-MEP between the base station and the UPF of the communication network, the R-MEP undertakes at least a part of the computing services of the UE, thereby realizing the sinking of edge computing power to the terminal side, so that the edge computing power resources are closer to the service side, and the computing power requirements of the terminal device are reduced.

[0116] It is understood that the above embodiments are merely exemplary embodiments used to illustrate the principles of this disclosure, and this disclosure is not limited thereto. For those skilled in the art, various modifications and improvements can be made without departing from the spirit and substance of this disclosure, and these modifications and improvements are also considered to be within the scope of protection of this disclosure.

Claims

1. A method for automatic movement of an auxiliary terminal, characterized in that, The method is applied to multilayer heterogeneous MECs, which include: The Remote Multi-Access Edge Computing Platform (R-MEP) is lightweight and deployed between the base station and the User Plane Function (UPF) in the communication network, enabling R-MEP to be deployed at the edge. The Multi-Access Edge Computing Platform (MEP), connected to the R-MEP, is used to obtain the computing requirements of User Equipment (UE) and, based on these requirements, collaborates with the R-MEP to provide computing services to the UE. The Multi-Access Edge Computing Orchestrator (MEO), connected to the Multi-Access Edge Programming (MEP), is used for the overall orchestration and scheduling of multi-layer heterogeneous MECs. The method includes: MEP acquires self-location information and mobility information from multiple UEs, specifically including: The first MEP receives self-location information and movement information from multiple first UEs connected to it, and / or, With the assistance of MEO, the first MEP obtains the self-location information and movement information of multiple second UEs connected to the second MEP itself; MEP sends a request to R-MEP to obtain the base station location information of the multiple UEs; R-MEP receives base station location information acquisition requests from multiple UEs from MEP; R-MEP obtains the base station location information of the multiple UEs from the base station according to the base station location information acquisition request; R-MEP sends the base station location information of the multiple UEs to MEP; MEP obtains the final location information of the multiple UEs based on self-location information and base station location information; MEP assists the multiple UEs in automatic movement based on the final location information and mobility information.

2. The method according to claim 1, characterized in that, With the assistance of MEO, the first MEP acquires the self-location and movement information of multiple second UEs connected to the second MEP, specifically including: MEO receives self-location information and mobility information of the first UE and the second UE respectively sent by the first MEP and the second MEP. In response to determining that a collision is possible between the first UE and the second UE based on the self-location information and movement information of the first UE and the second UE, the MEO sends the self-location information and movement information of the second UE to the first MEP and / or sends the self-location information and movement information of the first UE to the second MEP.

3. The method according to claim 1, characterized in that, The MEP obtains the final location information of the multiple UEs based on self-location information and base station location information, specifically including: If the difference between the self-location information and the base station location information of the same UE is greater than a preset threshold, the MEP re-acquires the self-location information and the base station location information of the same UE; otherwise, the MEP uses the base station location information as the final location information of the same UE.

4. The method according to any one of claims 1-3, characterized in that, The MEP assists the multiple UEs in automatic movement based on the final location information and movement information, specifically including: MEP predicts the possible trajectory range of the multiple UEs within a preset time threshold based on the final location information and mobility information; MEP predicts the probability of a collision between a UE and other UEs among the multiple UEs based on the possible trajectory range; The MEP sends the collision probability to a specific UE so that the specific UE can avoid colliding with other UEs based on the collision probability.

5. An auxiliary terminal automatic moving device, characterized in that, The auxiliary terminal automatic movement device is disposed in a multi-layer heterogeneous MEC and includes: The Remote Multi-Access Edge Computing Platform (R-MEP) is lightweight and deployed between the base station and the User Plane Function (UPF) in the communication network, enabling R-MEP to be deployed at the edge. The Multi-Access Edge Computing Platform (MEP), connected to the R-MEP, is used to obtain the computing requirements of User Equipment (UE) and, based on these requirements, collaborates with the R-MEP to provide computing services to the UE. The Multi-Access Edge Computing Orchestrator (MEO), connected to the Multi-Access Edge Programming (MEP), is used for the overall orchestration and scheduling of multi-layer heterogeneous MECs. R-MEP includes: The first receiving unit is used to receive base station location information acquisition requests from multiple UEs in the MEP. The first acquisition unit, connected to the first receiving unit, is used to acquire base station location information of the plurality of UEs from the base station according to a base station location information acquisition request. The first sending unit, connected to the first acquiring unit, sends the base station positioning information of the plurality of UEs to the MEP, so that the MEP can obtain the final positioning information of the plurality of UEs based on the base station positioning information, and assist the plurality of UEs in automatic movement based on the final positioning information. MEP includes: The second acquisition unit is used to acquire the self-location information and movement information of multiple UEs. The second sending unit, connected to the second acquiring unit, is used to send a request to the R-MEP to acquire the base station location information of the plurality of UEs. The final positioning unit, connected to the second transmitting unit, is used to obtain the final positioning information of the multiple UEs based on self-positioning information and base station positioning information. An auxiliary mobility unit, connected to the final positioning unit, is used to assist the multiple UEs in automatic movement based on the final positioning information and mobility information. The second acquisition unit specifically includes: The self-connection information acquisition unit is used to receive self-location information and movement information of multiple first UEs connected to it, and / or, The heterogeneous connection information acquisition unit is used to acquire the self-location information and mobility information of multiple second UEs connected to the second MEP itself with the assistance of MEO.

6. The multilayer heterogeneous MEC according to claim 5, characterized in that, Lightweight deployment of R-MEP includes at least one of the following: R-MEP uses an x86 or ARM central processing unit (CPU); R-MEP's operating system uses the container cluster management system Kubernetes; R-MEP deploys customized applications, which are connected to general applications deployed in MEP. The customized applications provide the UE with the first computing service, while the general applications provide the UE with the second computing service.

7. The multilayer heterogeneous MEC according to claim 5 or 6, characterized in that, The R-MEP sinking end side also includes at least one of the following: R-MEP offloads traffic to the base station through the data plane DP module; R-MEP is co-located with the base station.

8. The auxiliary terminal automatic moving device according to claim 6, characterized in that, R-MEP includes multiple R-MEC devices, and MEP includes multiple MEC nodes. Each MEC node deploys a MEC APP. The MEC APP connects to the UE's client APP. The UE uses GPS for self-positioning. The client APP periodically shares the UE's self-positioning information with the MEC APP. The MEC APP requests the MEP through an interface, and the MEP requests the R-MEC through an interface, to obtain the base station positioning information of the currently accessing UE.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the automatic movement method for an auxiliary terminal as described in any one of claims 1-4.

Citation Information

Patent Citations

  • Load scheduling method based on MEC-SBS clustering in ultra-dense network

    CN112601256A

  • Cloud computing service deployment and distribution method, system and device and storage medium

    CN113301077A