Communication method and apparatus

By selecting edge user plane network elements and application servers within the same edge computing node, the problem of low terminal computing power offloading efficiency is solved, thereby reducing data transmission latency and improving user experience.

WO2026046022A1PCT designated stage Publication Date: 2026-03-05HUAWEI TECH CO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/115963
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-08-27
Filing Date
2025-08-20
Publication Date
2026-03-05

AI Technical Summary

Technical Problem

When the terminal selects an inappropriate edge UPF network element and EAS, it leads to increased application data transmission latency and decreased terminal computing power offloading efficiency.

Method used

By selecting edge user plane network elements and edge application servers within the same edge computing node and configuring data transmission paths, data can be transmitted within the same node, reducing cross-node transmission.

Benefits of technology

It reduces the latency of application data transmission, improves the efficiency of terminal computing power offloading, and enhances the user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025115963_05032026_PF_FP_ABST
    Figure CN2025115963_05032026_PF_FP_ABST
Patent Text Reader

Abstract

A communication method and apparatus. The communication method comprises: a first network element determining a first edge user plane network element and a first edge application server, wherein the first edge user plane network element and the first edge application server belong to the same edge computing power node; the first network element configuring the first edge user plane network element for transmission of data of a first application from a terminal apparatus to the first edge application server; and the first network element sending address information of the first edge application server, wherein the first edge application server is used for processing the data of the first application that is from the terminal apparatus. It can be seen that in the method, a first network element selects, for a terminal apparatus, an edge user plane network element and an edge application server that belong to the same edge computing power node, such that the edge user plane network element can transmit data of a first application to the edge application server within the same edge computing power node, thereby reducing the transmission delay of application data and improving the efficiency of terminal computing power offloading.
Need to check novelty before this filing date? Find Prior Art

Description

Communication methods and devices

[0001] This application claims priority to Chinese Patent Application No. 202411189723.0, filed on August 27, 2024, entitled "Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0003] With the development of intelligent computing applications such as artificial intelligence generated content (AIGC) and extended reality (XR), the volume of application data has surged, leading to a significant increase in the computing power required to process it. To conserve computing power at the terminal, computing power can be offloaded to the network edge. For example, edge application servers (EAS) and edge user plane functions (UPF) network elements can be deployed on edge computing nodes at the network edge. The terminal can send application data to the EAS through the edge UPF network element, and the EAS will process the application data for the terminal. If the edge UPF network element and EAS selected for the terminal are unsuitable, it may lead to increased transmission latency of application data and decreased efficiency in offloading computing power from the terminal. Summary of the Invention

[0004] This application provides a communication method and apparatus that can improve the efficiency of terminal computing power offloading.

[0005] Firstly, this application provides a communication method. This method can be applied to a first network element, or to components within the first network element (such as a processor, chip, chip system, circuit, or functional module), or to logical nodes, logical modules, or software capable of implementing all or part of the functions of the first network element; there is no limitation in this regard. The following description uses a first network element as an example. The method includes: the first network element determining a first edge user plane network element and a first edge application server, wherein the first edge user plane network element and the first edge application server belong to the same edge computing node. The first network element configures the first edge user plane network element for the transmission of data from a terminal device to the first edge application server for a first application. The first network element sends the address information of the first edge application server, which processes the data from the terminal device for the first application.

[0006] As can be seen, in this method, the first network element selects an edge user plane network element and an edge application server for the terminal device. The selected edge user plane network element used to transmit the data of the first application belongs to the same edge computing power node as the edge application server used to process the data of the first application. The first network element is also configured to use the selected edge user plane network element for the transmission of the data of the first application from the terminal device to the selected edge application server. This enables the edge user plane network element to transmit the data of the first application to the edge application server within the same edge computing power node, without having to transmit the data of the first application across edge computing power nodes. This reduces the transmission latency of application data and improves the efficiency of terminal computing power offloading.

[0007] In one optional implementation, the first network element configures the first edge user plane network element for the transmission of data of the first application from the terminal device to the first edge application server, including: the first network element configures the first edge user plane network element to send data of the first application from the terminal device to the first edge application server.

[0008] Alternatively, it may include: configuring a first edge user plane network element to enable the first edge user plane network element to send data from a first application of a terminal device to a first edge application server;

[0009] Alternatively, it may include: the first network element sending configuration information to the first edge user plane network element, the configuration information being used by the first edge user plane network element to send data from the first application of the terminal device to the first edge application server.

[0010] In one optional implementation, the address information of the first edge application server is used by the terminal device to send data of the first application to the first edge application server.

[0011] In one optional implementation, the first network element determines the first edge user plane network element and the first edge application server, including: the first network element determines the edge user plane network element whose service range includes the location of the terminal device as the first edge user plane network element; the first network element determines the edge application server that supports processing the data of the first application among the edge application servers belonging to the same edge computing node as the first edge user plane network element as the first edge application server.

[0012] As can be seen, the service range of the first edge user plane network element selected by the first network element for the terminal device includes the location of the terminal device, so that the selected edge user plane network element can be used to transmit the data of the first application sent by the terminal device to the first edge application server. The first edge application server selected by the first network element for the terminal device supports the processing of the data of the first application, so that the first edge application server can be used to process the data of the first application. This implementation is beneficial to the normal operation of the first application and improves the user experience.

[0013] In one optional implementation, the first edge user plane network element and the first edge application server further satisfy at least one of the following conditions:

[0014] The load of the first edge user plane network element is less than or equal to the first threshold;

[0015] The load on the first edge application server is less than or equal to the second threshold;

[0016] The load of the first edge user plane network element is the smallest among the loads of multiple edge user plane network elements, and the service range of multiple edge user plane network elements includes the location of the terminal device.

[0017] The load on the first edge application server is the lowest among the loads on multiple edge application servers, which support the processing of data from the first application.

[0018] The latency of the first edge user plane network element is the lowest among the latency of multiple edge user plane network elements, and the service range of multiple edge user plane network elements includes the location of the terminal device.

[0019] In this embodiment, if the load of the first edge user plane network element is less than or equal to a first threshold, it indicates that the first edge user plane network element has available resources to transmit data for the first application, which is beneficial to improving the reliability of data transmission. In this embodiment, the resources of the edge user plane network element may include: storage space, power, etc.

[0020] If the load of the first edge application server is less than or equal to the second threshold, it indicates that the first edge application server has available resources to process the data of the first application, which is beneficial to the normal operation of the first application and improves the user experience. In this embodiment, the resources of the edge application server may include: storage space, computing power, power consumption, etc.

[0021] The load of the first edge user plane network element is the smallest among the loads of multiple edge user plane network elements whose service range includes the location of the terminal device. This indicates that the first edge user plane network element has the least used resources among the multiple edge user plane network elements whose service range includes the location of the terminal device. It is evident that the first edge user plane network element has relatively more available resources to be used for transmitting the data of the first application, which is beneficial to improving the reliability of data transmission.

[0022] The load on the first edge application server is the lowest among the multiple edge application servers that support the processing of data from the first application. This indicates that the first edge application server has the least amount of used resources among the multiple edge application servers that support the processing of data from the first application. Therefore, the first edge application server has relatively more available resources to process the data from the first application on the terminal device, which is beneficial to the normal operation of the first application and improves the user experience.

[0023] The latency of the first edge user plane network element is the lowest among multiple edge user plane network elements whose service range includes the location of the terminal device. This helps to reduce the data transmission latency of the first application and improve the user experience.

[0024] In an optional implementation, before the first network element determines the first edge user plane network element and the first edge application server, the method further includes: the first network element receiving a first request message from a terminal device, the first request message being used to request the establishment of a session, the session being used for the transmission of data of the first application from the terminal device to the first edge application server. The first network element sending the address information of the first edge application server includes: the first network element sending a first response message to the terminal device, the first response message including the address information of the first edge application server.

[0025] In one alternative implementation, the first request message includes an identifier of the first application; and / or, the first response message further includes at least one of the following: the application domain name of the first edge application server, or the identifier of the first application.

[0026] The inclusion of the identifier of the first application in the first request message allows the first network element to obtain the identifier of the first application from the first request message. This enables the first network element to determine the first edge application server that supports processing the data of the first application based on the identifier of the first application, which is beneficial to the normal operation of the first application and improves the user experience.

[0027] In an optional implementation, before the first network element determines the first edge user plane network element and the first edge application server, the method further includes: the first network element receiving a second request message from an application network element, the second request message being used to request an edge application server allocated for processing data for a first application on a terminal device. The first network element sending the address information of the first edge application server includes: the first network element sending a second response message to the application network element, the second response message including the address information of the first edge application server.

[0028] In one alternative implementation, the second request message includes an identifier of the first application; and / or, the second response message further includes at least one of the following: an identifier of the first application, or an identifier of the terminal device.

[0029] The inclusion of the identifier of the first application in the second request message allows the first network element to obtain the identifier of the first application from the second request message. This enables the first network element to determine the first edge application server that supports processing the data of the first application based on the identifier of the first application, which is beneficial to the normal operation of the first application and improves the user experience.

[0030] In one optional implementation, the first network element configures the first edge user plane network element for the transmission of data of the first application from the terminal device to the first edge application server, including: the first network element sending a forwarding rule to the first edge user plane network element, the forwarding rule being used to instruct the first edge user plane network element to forward the data of the first application from the terminal device to the first edge application server.

[0031] Secondly, this application provides a communication method applicable to a terminal device. The terminal device can be a terminal equipment, or a component within the terminal equipment (e.g., a processor, chip, chip system, circuit, or functional module), or a logical node, logical module, or software capable of implementing all or part of the terminal equipment; no limitation is imposed in this regard. The following description uses a terminal device as an example. The method includes: the terminal device obtaining the address information of a first edge application server. The first edge application server is used to process data from a first application originating from the terminal device. The first edge application server and a first edge user plane network element belong to the same edge computing node. The first edge user plane network element is used for transmitting data of the first application from the terminal device to the first edge application server. Based on the address information of the first edge application server, the terminal device sends the data of the first application to the first edge application server.

[0032] It is evident that the edge user plane network element used to transmit the data of the first application and the edge application server used to process the data of the first application belong to the same edge computing power node. This enables the edge user plane network element to transmit the data of the first application to the edge application server within the same edge computing power node, without having to transmit the data of the first application across edge computing power nodes. This reduces the transmission latency of application data and improves the efficiency of terminal computing power offloading.

[0033] In an optional implementation, the method further includes: the terminal device sending a first request message to a first network element, the first request message being used to request the establishment of a session, the session being used for the transmission of data of the first application from the terminal device to a first edge application server. The terminal device obtaining the address information of the first edge application server includes: the terminal device receiving a first response message from the first network element, the first response message including the address information of the first edge application server.

[0034] In one optional implementation, the first request message includes an identifier of the first application. Thus, the terminal device carries the identifier of the first application in the first request message used to request the establishment of a session, enabling the first network element to obtain the identifier of the first application from the first request message. Based on the identifier of the first application, the first network element can determine the first edge application server that supports processing data of the first application, which is beneficial to the normal operation of the first application and improves the user experience.

[0035] In an optional implementation, the method further includes: the terminal device sending a third request message to an application network element, the third request message being used to request access to an edge application server that processes data for the first application for the terminal device; and the terminal device receiving a third response message from the application network element, the third response message including address information of the first edge application server.

[0036] In one alternative implementation, the third request message includes the identifier of the first application.

[0037] It is evident that the terminal device carries the identifier of the first application in the third request message used to request access to the edge application server, so that the application network element can send the identifier of the first application to the first network element, enabling the first network element to obtain the identifier of the first application. Thus, the first network element can determine the first edge application server that supports processing the data of the first application based on the identifier of the first application, which is beneficial to the normal operation of the first application and improves the user experience.

[0038] In one optional implementation, the terminal device obtains the address information of the first edge application server, including: the terminal device obtaining the address information of the first edge application server and the application domain name of the first edge application server. The method further includes: the terminal device configuring the mapping relationship between the application domain name of the first edge application server and the address information of the first edge application server in its local domain name system.

[0039] The terminal device sends data of the first application to the first edge application server based on the address information of the first edge application server, including: the terminal device receiving data of the first application from the application client and the application domain name of the first edge application server; the terminal device determining the address information of the first edge application server corresponding to the application domain name of the first edge application server from the local domain name system; and the terminal device sending a data packet to the first edge application server, the data packet including the data of the first application, the destination address of the data packet being the address information of the first edge application server.

[0040] As can be seen, the terminal device configures the correspondence between the application domain name of the first edge application server and the address information of the first edge application server in the local domain name system, so that the terminal device can determine the address information of the first edge application server corresponding to the application domain name of the first edge application server from the local domain name system, without having to query the domain name system in the network for the address information of the first edge application server corresponding to the application domain name of the first edge application server, thereby reducing query latency and thus reducing the data transmission latency of the first application.

[0041] In one optional implementation, the terminal device sends data of a first application to the first edge application server based on the address information of the first edge application server, including: the terminal device providing the address information of the first edge application server to the application client; the terminal device receiving the data of the first application and the destination address of the data of the first application from the application client, wherein the destination address of the data of the first application is the address information of the first edge application server; and the terminal device sending a data packet to the first edge application server, wherein the data packet includes the data of the first application and the destination address of the data packet is the destination address of the data of the first application.

[0042] Thirdly, this application provides a communication method that can be applied to application network elements, components within application network elements (such as processors, chips, chip systems, circuits, or functional modules), and logical nodes, logical modules, or software capable of implementing all or part of the application network element's functions; no limitation is imposed in this regard. The following description uses an application network element as an example. The method includes: the application network element receiving a third request message from a terminal device, the third request message requesting access to an edge application server that processes data for a first application on the terminal device. The application network element sending a second request message to a first network element, the second request message requesting an edge application server allocated to process data for the first application on the terminal device. The application network element receiving a second response message from the first network element, the second response message including the address information of a first edge application server, the first edge application server and a first edge user plane network element belonging to the same edge computing node, the first edge user plane network element used for transmitting data for the first application from the terminal device to the first edge application server. The application network element sending a third response message to the terminal device, the third response message including the address information of the first edge application server, the first edge application server used for processing the data for the first application from the terminal device.

[0043] It is evident that the edge user plane network element used to transmit the data of the first application and the edge application server used to process the data of the first application belong to the same edge computing power node. This enables the edge user plane network element to transmit the data of the first application to the edge application server within the same edge computing power node, without having to transmit the data of the first application across edge computing power nodes. This reduces the transmission latency of application data and improves the efficiency of terminal computing power offloading.

[0044] In one optional implementation, the third request message includes an identifier of the first application; and / or, the second request message includes an identifier of the first application. This implementation facilitates the first network element in obtaining the identifier of the first application, thereby enabling the first network element to determine the first edge application server that supports processing data of the first application based on the identifier of the first application, which is beneficial to the normal operation of the first application and improves the user experience.

[0045] In one alternative implementation, the second request message may also include an identifier of the terminal device.

[0046] In one alternative implementation, the second response message further includes at least one of the following: the identifier of the first application, or the identifier of the terminal device.

[0047] In one optional implementation, before the application network element sends a third response message to the terminal device, the method further includes: the application network element determining the terminal device based on the identifier of the first application or the identifier of the terminal device.

[0048] Fourthly, this application also provides a communication device. This communication device includes modules, units, or means that implement the methods described above. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above.

[0049] In one possible design, the communication device may include a processing unit and a communication unit. The processing unit is configured to support the communication device in performing the corresponding functions described in the above-described method. The communication unit supports communication between the communication device and other communication devices. The communication device may also include a storage unit coupled to the processing unit and the communication unit, which stores necessary program instructions and data for the communication device. Additionally, the processing unit may be used to control the communication unit to transmit and receive data / signaling.

[0050] In one embodiment, the processing unit is used to determine a first edge user plane network element and a first edge application server, wherein the first edge user plane network element and the first edge application server belong to the same edge computing node.

[0051] The processing unit is also configured to configure the first edge user plane network element for the transmission of data from the terminal device to the first edge application server for the first application.

[0052] The communication unit is used to send the address information of the first edge application server, which is used to process data from the first application of the terminal device.

[0053] In addition, other optional implementations of the communication device in this method can be found in the relevant content of the first aspect above, and will not be described in detail here.

[0054] In another embodiment, the communication unit is used to obtain the address information of the first edge application server. The first edge application server is used to process the data of the first application from the communication device. The first edge application server and the first edge user plane network element belong to the same edge computing node. The first edge user plane network element is used for the transmission of the data of the first application from the communication device to the first edge application server.

[0055] The communication unit is also used to send data of the first application to the first edge application server based on the address information of the first edge application server.

[0056] In addition, other optional implementations of the communication device in this method can be found in the relevant content of the second aspect above, and will not be described in detail here.

[0057] In another embodiment, the communication unit is configured to receive a third request message from the terminal device, the third request message being used to request access to an edge application server that processes data for the first application on the terminal device.

[0058] The communication unit is also used to send a second request message to the first network element, the second request message being used to request an edge application server to allocate data for the terminal device to process the first application.

[0059] The communication unit is also used to receive a second response message from the first network element. The second response message includes the address information of the first edge application server. The first edge application server and the first edge user plane network element belong to the same edge computing node. The first edge user plane network element is used for the transmission of data of the first application from the terminal device to the first edge application server.

[0060] The communication unit is also used to send a third response message to the terminal device. The third response message includes the address information of the first edge application server, which is used to process data from the first application of the terminal device.

[0061] In addition, other optional implementations of the communication device in this method can be found in the relevant content of the third aspect above, and will not be described in detail here.

[0062] As an example, the communication unit can be a transceiver or a communication interface, the storage unit can be a memory, and the processing unit can be a processor. The processor is coupled to the memory, which stores programs or instructions for the processor. The processor can be used to cause the communication device to perform the method described in the first aspect above when the program or instructions are executed by the processor. The transceiver or communication interface can be used to send and receive signals and / or data.

[0063] In one embodiment, the processor is used to determine a first edge user plane network element and a first edge application server, wherein the first edge user plane network element and the first edge application server belong to the same edge computing node.

[0064] The processor is also used to configure the first edge user plane network element for the transmission of data from the terminal device to the first edge application server for the first application.

[0065] A transceiver is used to send the address information of a first edge application server, which is used to process data from a first application on a terminal device.

[0066] In addition, other optional implementations of the communication device in this method can be found in the relevant content of the first aspect above, and will not be described in detail here.

[0067] In another embodiment, the transceiver is used to obtain the address information of the first edge application server. The first edge application server is used to process the data of the first application from the communication device. The first edge application server and the first edge user plane network element belong to the same edge computing node. The first edge user plane network element is used for the transmission of the data of the first application from the communication device to the first edge application server.

[0068] The transceiver is also used to send data of the first application to the first edge application server based on the address information of the first edge application server.

[0069] In addition, other optional implementations of the communication device in this method can be found in the relevant content of the second aspect above, and will not be described in detail here.

[0070] In another embodiment, the transceiver is configured to receive a third request message from the terminal device, the third request message being used to request access to an edge application server that processes data for the first application on the terminal device.

[0071] The transceiver is also used to send a second request message to the first network element, the second request message being used to request an edge application server to allocate data for processing the first application for the terminal device.

[0072] The transceiver is also used to receive a second response message from the first network element. The second response message includes the address information of the first edge application server. The first edge application server and the first edge user plane network element belong to the same edge computing node. The first edge user plane network element is used for the transmission of data of the first application from the terminal device to the first edge application server.

[0073] The transceiver is also used to send a third response message to the terminal device. The third response message includes the address information of the first edge application server, which is used to process data from the first application of the terminal device.

[0074] In addition, other optional implementations of the communication device in this method can be found in the relevant content of the third aspect above, and will not be described in detail here.

[0075] In another embodiment, the communication device is a chip or chip system. The processing unit may also be a processing circuit or logic circuit; the transceiver unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system.

[0076] In implementation, the processor can be used for, but is not limited to, baseband-related processing, and the transceiver or communication interface can be used for, but is not limited to, radio frequency transceiver. These devices can be disposed on separate chips, or at least partially or entirely on the same chip. For example, the processor can be further divided into analog baseband processors and digital baseband processors. The analog baseband processor can be integrated with the transceiver (or communication interface) on the same chip, while the digital baseband processor can be disposed on a separate chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip. For example, a digital baseband processor can be integrated with multiple application processors (e.g., but not limited to graphics processors, multimedia processors, etc.) on the same chip. Such a chip can be called a system-on-a-chip (SoC). Whether the various devices are disposed independently on different chips or integrated on one or more chips often depends on the needs of the product design. This application does not limit the implementation form of the above-mentioned devices.

[0077] Fifthly, this application also provides a communication device, comprising: a processor for executing the various methods described above. In executing these methods, the processes of sending and receiving the signals described above can be understood as the process of the processor outputting the signals and the process of the processor inputting the signals. When outputting the signals, the processor outputs the signals to a transceiver for transmission by the transceiver (or communication interface). After being output by the processor, the signals may require further processing before reaching the transceiver (or communication interface). Similarly, when the processor receives the input signals, the transceiver (or communication interface) receives the signals and inputs them to the processor. Furthermore, after the transceiver (or communication interface) receives the signals, the signals may require further processing before being input to the processor.

[0078] Unless otherwise specified, or unless it contradicts its actual function or internal logic in the relevant description, the transmission and reception operations involved by the processor can be more generally understood as processor output and reception, input and other operations, rather than transmission and reception operations directly performed by radio frequency circuits and antennas.

[0079] In conjunction with the fifth aspect above, in one possible implementation, the communication device further includes a memory for storing necessary program instructions and data.

[0080] In implementation, the processor can be a dedicated processor for executing these methods, or it can be a processor that executes computer instructions stored in memory to execute these methods, such as a general-purpose processor. The memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or disposed on different chips. This application does not limit the type of memory or the arrangement of the memory and processor.

[0081] Sixthly, this application also provides a communication system, which includes a first network element and a first edge user plane network element. The first network element is used to perform the method described in the first aspect and any of its optional embodiments. The first edge user plane network element is used to: receive configuration information from the first network element, and send data from a first application of a terminal device to a first edge application server according to the configuration information.

[0082] Optionally, the system further includes a first edge application server. The first edge application server is configured to: receive data from a first application from a first edge user plane network element, and process the data of the first application. Optionally, the first edge application server is also configured to: send the result of processing the data of the first application to the terminal device through the first edge user plane network element.

[0083] Optionally, the system further includes an application network element. The application network element is used to: send a second request message to the first network element, the second request message being used to request an edge application server to allocate data for processing a first application for the terminal device. The application network element can also be used to perform the methods described in the third aspect above and any of its optional embodiments.

[0084] Optionally, the system further includes a terminal device for performing the method described in the second aspect and any of its optional embodiments.

[0085] In a seventh aspect, this application provides a computer-readable storage medium storing a computer program that, when run, causes the methods described in the first, second, or third aspect above to be performed.

[0086] Eighthly, this application also provides a computer program product including instructions, the computer program product comprising: computer program code, which, when executed, causes the methods described in the first, second, or third aspects above to be performed.

[0087] Ninthly, this application provides a chip system including a processor and an interface. The interface is used to acquire programs or instructions, and the processor is used to invoke the programs or instructions to implement the functions involved in the first, second, or third aspects. In one possible design, the chip system further includes a memory for storing program instructions and data necessary for the terminal. This chip system may be composed of chips or may include chips and other discrete devices.

[0088] The technical effects of any of the possible implementations in aspects four through nine can be found in the technical effects of the different possible implementations in aspects one through three above, and will not be repeated here.

[0089] Understandably, provided that the solutions do not contradict each other, the solutions in the above aspects can be combined. Attached Figure Description

[0090] Figure 1 is a schematic diagram of a network architecture provided in an embodiment of this application;

[0091] Figure 2 is a schematic diagram of a terminal computing power offloading to the network edge provided in an embodiment of this application;

[0092] Figure 3 is a schematic diagram of a process for selecting edge UPF network elements and EAS according to an embodiment of this application;

[0093] Figure 4 is a schematic diagram of another terminal computing power offloading to the network edge provided in an embodiment of this application;

[0094] Figure 5 is a schematic diagram of another process for selecting edge UPF network elements and EAS provided in an embodiment of this application;

[0095] Figure 6 is a schematic diagram of another process for selecting edge UPF network elements and EAS provided in an embodiment of this application;

[0096] Figure 7 is a schematic diagram of data transmission provided in an embodiment of this application;

[0097] Figure 8 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0098] Figure 9 is a schematic diagram of a DNAI provided in an embodiment of this application;

[0099] Figure 10 is a schematic diagram of an ENLI provided in an embodiment of this application;

[0100] Figure 11 is a schematic diagram of determining a first edge user plane network element and a first edge application server according to an embodiment of this application;

[0101] Figure 12 is a schematic diagram of another communication method provided in an embodiment of this application;

[0102] Figure 13 is a schematic diagram of another communication method provided in an embodiment of this application;

[0103] Figure 14 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0104] Figure 15 is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0105] The embodiments of this application are described below with reference to the accompanying drawings.

[0106] First, in order to better understand the communication method disclosed in the embodiments of this application, the communication system applicable to the embodiments of this application will be described.

[0107] The technical solutions of the embodiments of this application can be applied to various communication systems. For example, the Global System for Mobile Communications (GSMA), Long Term Evolution (LTE) system, Universal Mobile Communications System (UMS), 4th Generation (4G) mobile communication system, 5th Generation (5G) mobile communication system, and with the continuous development of communication technology, the technical solutions of the embodiments of this application can also be used in future communication systems.

[0108] Please refer to Figure 1, which is a schematic diagram of a network architecture provided in an embodiment of this application. The network architecture shown in Figure 1 includes terminal equipment, access network (AN), user plane function (UPF) network elements, edge application server (EAS), access and mobility management function (AMF) network elements, session management function (SMF) network elements, and application function (AF) network elements. The network architecture shown in Figure 1 may also include: network slice selection function (NSSF) network elements, network slice-specific authentication and authorization function (NSSAAF) network elements, network exposure function (NEF) network elements, authentication server function (AUSF) network elements, network repository function (NRF) network elements, policy control function (PCF) network elements, unified data management (UDM) network elements, and network slice admission control function (NSACF) network elements.

[0109] Specifically, the terminal equipment communicates with the AMF network element via the N1 interface. The AN communicates with the AMF network element via the N2 interface. The AN communicates with the UPF network element via the N3 interface. The UPF network element communicates with the SMF network element via the N4 interface. The UPF network element communicates with the EAS via the N6 interface. Different UPF network elements communicate with each other via the N9 interface.

[0110] In this application embodiment, the terminal device may also be referred to as user equipment (UE), terminal, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, user agent, or user device, and can be applied to 5G systems, future communication systems, etc. The terminal device in this application embodiment can be a joint device for transmitting and receiving digital signals over a regular telephone line, or it can be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), mobile phone, tablet computer, computer with wireless transceiver function, head-mounted display (HMD), virtual reality (VR) terminal device (such as VR glasses), augmented reality (AR) terminal device (such as AR glasses), mixed reality (MR) terminal device, wireless terminal in industrial control, processing device connected to a wireless modem, tactile terminal device, vehicle terminal device, wireless terminal in self-driving, wireless terminal in remote medical care, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, or wireless terminal in smart home. Wireless terminals in the home, roadside units (RSUs) of the aforementioned wireless terminal types, wearable terminal devices, etc.

[0111] An AN can be a radio access network (RAN), which implements radio-related functions. AN equipment can be access network equipment. AN equipment includes, but is not limited to: base station (BS), radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), home network equipment (e.g., home evolved Node B, or home Node B, HNB), baseband unit (BBU), radio relay node, radio backhaul node, and transmission and reception point (TRP; or transmission point, TP). A base station is a device deployed in a radio access network that provides wireless communication functions. It can also be called base station equipment, such as an evolved Node B (eNB or e-NodeB) in an LTE system, a Node B, a base station (gNodeB or gNB) in a 5G system, and a base station in a future communication system. A base station may include a BBU and a remote radio unit (RRU). BBU and RRU can be placed in different locations. For example, the RRU can be deployed remotely to a high-traffic area, while the BBU is placed in the central equipment room. Alternatively, the BBU and RRU can be placed in the same equipment room. They can also be different components within the same rack. Base stations can take the following forms: macro base stations, micro base stations (also known as small stations), pico base stations, relay stations, access points, balloon stations, etc.

[0112] Optionally, in some deployments of access network equipment, the access network equipment may include centralized units (CUs) and distributed units (DUs). For example, some protocol layer functions of the access network equipment are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU, which is centrally controlled by the CU. In other deployments of access network equipment, the CU can also be divided into CU-control plane (CP) and CU-user plane (UP). In still other deployments of access network equipment, the network equipment can also be an open radio access network (ORAN / O-RAN) architecture. When the access network equipment is an ORAN architecture, the access network equipment can be a functional entity or module in the ORAN, such as a CU, DU, or radio unit (RU) or a combination of one or more of these. In an ORAN system, the CU can also be called an open (O)-CU, the DU can also be called an O-DU, the CU-CP can also be called an O-CU-CP, and the CU-UP can also be called an O-CU-UP, etc. The deployment methods of access network devices listed herein are merely examples. As standard technologies evolve, access network devices may have other deployment forms, and this application does not limit them.

[0113] The AMF (Active Mobility Management) element is responsible for the mobility management of terminal devices, including: mobility state management, allocation of temporary identity identifiers for terminal devices, authentication and authorization of terminal devices. The AMF element can be used to complete the access process for establishing or updating Protocol Data Unit (PDU) sessions initiated by terminal devices, including: requesting the UDM (Universal Device Management) element to authenticate the terminal device, selecting the SMF (Active Mobility Management) element for establishing or updating the PDU session, instructing the AN (Active Access Controller) to complete the air interface resource allocation for the slice corresponding to the PDU session, and establishing or updating the N3 tunnel between the AN and the UPF element.

[0114] SMF network elements can be used to complete the N4 session establishment or update process, including: requesting UDM network elements to perform session slice authentication, requesting PCF network elements to perform session policy control, selecting UPF network elements to establish or update N4 sessions, issuing session policy and charging control (PCC) rules, and interacting with AMF network elements to establish or update N3 tunnels between AN and UPF network elements.

[0115] UPF network elements can be used to complete user data access and forwarding functions, including: N4 session establishment, GPRS tunneling protocol for the user plane (GTPU) tunneling processing on the N3 interface, quality of service (QoS) processing, billing, data statistics, and N6 interface routing and forwarding processing. GPRS stands for General Packet Radio Service.

[0116] UPF network elements can be categorized into two types: edge UPF network elements and large-scale UPF network elements. Edge UPF network elements are deployed on edge computing nodes and are used to process and forward application data transmitted between terminal devices and edge application servers. Large-scale UPF network elements are used to process and forward application data transmitted between terminal devices and the Internet / central cloud application servers, as well as to offload application data transmitted between terminal devices and edge application servers.

[0117] EAS can be used to receive and process application data from terminal devices forwarded by edge UPF network elements, and return the processing results to the terminal devices through edge UPF network elements.

[0118] UDM network elements are responsible for managing contract data, and when contract data is modified, they are responsible for notifying the corresponding network elements.

[0119] Application layer (AF) elements are used to provide application layer services to terminal devices. When providing services to terminal devices, AF elements have requirements for QoS and charging policies and need to notify the network. AF elements also need application-related information from the core network.

[0120] It is understood that, for ease of explanation, the embodiments of this application are illustrated using a 5G network as an example. When the solutions of the embodiments of this application are applied to future communication networks, the corresponding network element names, network element deployment methods, and interfaces may change, and this application does not limit them.

[0121] Offloading computing power to the network edge can be achieved by the edge UPF network element sending application data from the terminal device to the EAS. The EAS then processes the application data, saving computing power for the terminal device. For example, the terminal device sends application data to the edge UPF network element, which then forwards it to the EAS. The EAS processes the application data and sends the results back to the edge UPF network element, which then sends the results back to the terminal device. Optionally, the EAS processes the application data, including analyzing and calculating it. For example, if the application data is video data, the EAS can analyze and calculate it to determine the scene, objects, and quantity of objects within the video data. Optionally, after receiving the application data, the edge UPF network element can also perform user plane processing, such as statistics, billing, and QoS processing.

[0122] For example, referring to Figure 2, which illustrates the situation using a 5G network as an example, assuming the terminal device detects that the AIGC app installed on the AIGC client is running, the terminal device can send AIGC data to edge UPF network element 1 via the 5G network (including 5G base stations). Edge UPF network element 1 then sends the AIGC data to EAS1, which processes the AIGC data. Alternatively, EAS1 can also send the processing results of the AIGC data to edge UPF network element 1, which then sends the processing results back to the terminal device via the 5G network (including 5G base stations).

[0123] As can be seen, in the scenario where the computing power of terminal devices is offloaded to the network edge, the nodes in the user plane path include edge UPF network elements and EAS. The following describes several methods for selecting edge UPF network elements and EAS, as described in methods 1 to 3.

[0124] Method 1: When the terminal device detects that an APP is running, it triggers the establishment of a dedicated PDU session for the APP based on the User Equipment Routing Selection Policy (URSP) mechanism. During the establishment of the dedicated PDU session, the SMF network element selects an Edge UPF network element for the terminal device to transmit the APP's data. In addition, the APP client deployed in the terminal device also sends signaling to the DNS server or APP scheduler, so that the DNS server or APP scheduler selects an EAS for the terminal device to process the APP's data. In this embodiment, the dedicated PDU session refers to a PDU session (packet data unit session) established separately for the APP. This PDU session is used to carry the data exchanged between the APP client on the terminal side and the APP server on the network side, which can better guarantee the QoS (such as bandwidth, latency, packet loss rate, etc.) and security of the data transmitted by the 5G network.

[0125] Referring to Figure 3, Method 1 includes the following steps:

[0126] S101. When the terminal device detects that the APP is running, it initiates the establishment of a PDU session based on the matching URSP rules. This PDU session is a dedicated PDU session for the APP.

[0127] For example, when a terminal device detects that an app is running, it determines the URSP rule that matches the app. The URSP rule that matches the app includes the app's identifier (ID) and slice ID, where a slice can also be called a network slice. Then, the terminal device sends a PDU session establishment request to the SMF network element through the AMF network element. This PDU session establishment request carries the slice ID included in the URSP rule that matches the app.

[0128] S102. Based on the slice ID carried in the PDU session establishment request, the SMF network element selects the edge UPF network element that supports the slice.

[0129] In addition, the APP client deployed in the terminal device also sends signaling to the APP scheduler so that the APP scheduler selects an EAS for the APP, as described in step S104a below, where step S103a is a preceding operation to S104a. Alternatively, the APP client deployed in the terminal device also sends signaling to the DNS server so that the DNS server selects an EAS for the APP, as described in step S104b below, where step S103b is a preceding operation to S104b.

[0130] S103a. Each EAS reports its own information to the APP scheduler. The information reported by the EAS includes: the location of the EAS, the Internet Protocol (IP) address of the EAS, and the port number of the EAS. Optionally, the information reported by the EAS may also include: the load of the EAS.

[0131] S104a. The APP client sends higher-level signaling to the APP scheduler. This higher-level signaling is used to request access to the EAS for processing application data. This higher-level signaling includes the IP address of the terminal device.

[0132] Understandably, after receiving the higher-level signaling in step S104a, the APP scheduler can determine the city-level location of the terminal device based on its IP address. Since the APP scheduler has already obtained the information of each EAS based on step S103a, it can identify the EAS located in the city where the terminal device is located, select one EAS from the EAS deployed in that city, and send the IP address and port number of the selected EAS to the APP client.

[0133] S103b. Manually configure the APP domain name address record for the DNS server. The APP domain name address record includes the IP address and port number of each EAS.

[0134] S104b: The APP client sends a request message to the DNS server. This request message is used to query the IP address of the EAS that processes application data. This request message includes the IP address of the terminal device.

[0135] Understandably, after receiving the request message in step S104b, the DNS server can determine the city-level location of the terminal device based on its IP address. Since the DNS server has pre-configured the APP domain name address record manually, and it supports location-based traffic management, the DNS server can identify the EAS located within the city where the terminal device is located, select one EAS from those deployed within that city, and send the selected EAS's IP address and port number to the APP client.

[0136] After obtaining the IP address and port number of the EAS selected by the APP scheduler or DNS server, the APP client can send application data and a target address to the operating system (OS) in the terminal device. The target address is the IP address and port number of the EAS obtained by the APP client. The OS in the terminal device sends the application data and target address to the edge UPF network element selected by the SMF network element through the access network device. After processing the application data, the edge UPF network element sends the application data to the EAS corresponding to the target address based on the target address.

[0137] In Method 1, the URSP rules can be sent from the PCF network element to the AMF network element, and then from the AMF network element to the terminal device. For example, referring to Figure 4, the PCF network element sends the URSP rules to the AMF network element, which then sends the URSP rules to the terminal device. After establishing a connection with the APP client, the terminal device determines the URSP rules matching the APP and initiates a dedicated PDU session for the APP based on the matching URSP rules. Establishing a connection between the terminal device and the APP client can include: the APP client registering an APP ID with the OS in the terminal device when installing the APP; the terminal device determining the APP ID when detecting the APP running; and then the terminal device determining the URSP rules matching the APP based on the APP ID.

[0138] For example, Figure 4 illustrates the AIGC client and cloud gaming client. After establishing a connection with the AIGC client, the terminal device initiates PDU session 1 based on the URSP rules matching the AIGC APP. PDU session 1 corresponds to slice 1, data network name (DNN) 1, and service and session continuity (SSC) mode 1. Application data is then transmitted between the AIGC client and the EAS providing the AIGC service through PDU session 1. Similarly, after establishing a connection with the cloud gaming client, the terminal device initiates PDU session 2 based on the URSP rules matching the cloud gaming APP. PDU session 2 corresponds to slice 2, DNN 2, and SSC mode 3. Application data is then transmitted between the cloud gaming client and the EAS providing the cloud gaming service through PDU session 2.

[0139] Method 2: The terminal device initiates the process of establishing a large-scale PDU session. During the establishment of the large-scale PDU session, the SMF network element selects an edge UPF network element for the terminal device. When the APP is running, the APP client deployed on the terminal device sends signaling to the DNS server or APP scheduler, so that the DNS server or APP scheduler selects an EAS for the terminal device to process the APP's data. In this embodiment, the large-scale PDU session refers to a default PDU session established for the terminal device. The large-scale PDU session is used to carry application data exchanged between the application client deployed on the terminal device and the application server of the Internet / central cloud.

[0140] Referring to Figure 5, Method 2 includes the following steps:

[0141] S201. Manually configure the EAS information of the APP subscribed by the terminal device for the PCF network element, or have the AF network element send the EAS information of the APP subscribed by the terminal device to the PCF network element by calling the application programming interface (API). The EAS information of the APP subscribed by the terminal device includes: the APP ID, the EAS IP address range, and the port number.

[0142] S202. The terminal device sends a large network PDU session establishment request to the SMF network element through the AMF network element. Understandably, the terminal device initiates the establishment of a large network PDU session.

[0143] S203. The PCF network element sends a policy control response to the SMF network element in response to the policy control request. The policy control response includes uplink classifier (UL CL) traffic splitting rules. The UL CL traffic splitting rules include: rule ID, EAS IP address range, and port number.

[0144] Understandably, after receiving the large network PDU session establishment request, the SMF network element sends a policy control request to the PCF network element so that the PCF network element can send the UL CL traffic splitting rules to the SMF network element in the policy control response.

[0145] S204. The SMF network element sends an instruction message to the large network UPF network element to instruct the large network UPF network element to establish a large network PDU session. The SMF network element also sends UL CL traffic splitting rules to the large network UPF network element.

[0146] S205 and SMF network elements select edge UPF network elements for terminal devices based on the location of the terminal devices, and instruct the main network UPF network elements to establish an N9 tunnel between the selected edge UPF network elements.

[0147] The process involves the SMF network element instructing a large-scale UPF network element to establish an N9 tunnel with a selected edge UPF network element. This includes: the SMF network element sending instruction information to the large-scale UPF network element to instruct it to establish an N9 tunnel with the edge UPF network element; the large-scale UPF network element determining its endpoint information as an N9 tunnel endpoint and sending this endpoint information to the SMF network element; the SMF network element sending the large-scale UPF network element's endpoint information and the instruction information to the selected edge UPF network element, whereby the instruction information instructs the edge UPF network element to establish an N9 tunnel with the large-scale UPF network element; the edge UPF network element determining its endpoint information as an N9 tunnel endpoint and sending this endpoint information to the SMF network element; and the SMF network element sending the edge UPF network element's endpoint information to the large-scale UPF network element. At this point, the large network UPF element has obtained the endpoint information of the edge UPF element, and the edge UPF element has also obtained the endpoint information of the large network UPF element, which helps to establish an N9 tunnel between the large network UPF element and the edge UPF element.

[0148] Additionally, during APP runtime, the APP client deployed on the terminal device sends signaling to the APP scheduler, causing the APP scheduler to select an EAS for the APP, as described in step S207a below, where step S206a is a prerequisite operation for S207a. Alternatively, during APP runtime, the APP client deployed on the terminal device also sends signaling to the DNS server, causing the DNS server to select an EAS for the APP, as described in step S207b below, where step S206b is a prerequisite operation for S207b.

[0149] S206a. Each EAS reports its own information to the APP scheduler. The information reported by the EAS includes: the location of the EAS, the IP address of the EAS, and the port number of the EAS. Optionally, the information reported by the EAS also includes the load of the EAS.

[0150] S207a. The APP client sends higher-level signaling to the APP scheduler. This higher-level signaling is used to request access to the EAS for processing application data. This higher-level signaling includes the IP address of the terminal device.

[0151] For a detailed explanation of steps S206a and S207a, please refer to the detailed explanation of S103a and S104a in the aforementioned method 1, and will not be repeated here.

[0152] S206b. Manually configure the APP domain name address record for the DNS server. The APP domain name address record includes the IP address and port number of each EAS.

[0153] S207b: The APP client sends a request message to the DNS server. This request message is used to query the IP address of the EAS that processes application data. This request message includes the IP address of the terminal device.

[0154] For a detailed explanation of steps S206b and S207b, please refer to the detailed explanation of S103b and S104b in the aforementioned method 1, and will not be repeated here.

[0155] In addition, after the APP client obtains the IP address and port number of EAS, step S208 can be executed.

[0156] S208: The APP client sends application data and the target address to the OS in the terminal device. The target address is the IP address and port number of the EAS obtained by the APP client. The OS in the terminal device then sends the application data and the target address to the UPF network element of the main network through the access network device.

[0157] S209. The large-scale UPF network element matches the target address of the application data with the UL CL traffic splitting rules; if the match is successful, the large-scale UPF network element sends the application data to the edge UPF network element selected by the SMF network element through the N9 tunnel.

[0158] After receiving the application data, the edge UPF network element sends the application data to the EAS corresponding to the target address based on the target address.

[0159] Method 3: The difference between Method 3 and Method 2 is that after the terminal device initiates the process of establishing a large-scale PDU session, the SMF network element does not temporarily select an edge UPF network element. After the terminal device sends application data and the target address to the large-scale UPF network element, the SMF network element then selects the edge UPF network element based on the target address of the application data and establishes an N9 tunnel between the edge UPF network element and the large-scale UPF network element. The target address is the IP address and port number of the EAS obtained by the terminal device from the DNS server or the APP scheduler.

[0160] Referring to Figure 6, method 3 includes the following operations:

[0161] S301. Manually configure the EAS information of the APP subscribed by the terminal device for the PCF network element, or have the AF network element call the API to send the EAS information of the APP subscribed by the terminal device to the PCF network element. The EAS information of the APP subscribed by the terminal device includes: the APP ID, EAS IP address range, and port number.

[0162] S302. Manually configure and enable multi-DNN functionality for SMF network elements, large-scale UPF network elements, and edge UPF network elements. Manually configure the ID of the edge UPF network element for the SMF network element, which is located in the same edge computing node as the IP address in the EAS IP address range.

[0163] For example, the Data Network Name (DNN) in a 5G network has the same function as the Access Point Name (APN) in a 4G network, used to identify an external data network. Multiple DNN functionality refers to enabling a separate DNN for a specific app or a group of apps.

[0164] S303. The terminal device sends a large network PDU session establishment request to the SMF network element through the AMF network element. Understandably, the terminal device initiates the establishment of a large network PDU session.

[0165] S304. The SMF network element sends an instruction message to the large network UPF network element to instruct the large network UPF network element to establish a large network PDU session. In addition, the SMF network element also sends multiple DNN rules to the large network UPF network element.

[0166] Understandably, when a large-scale UPF network element receives multiple DNN rules from an SMF network element, it will subsequently report to the SMF network element that the large-scale UPF network element has detected the application data when it receives application data.

[0167] Additionally, during APP runtime, the APP client deployed on the terminal device sends signaling to the APP scheduler, causing the APP scheduler to select an EAS for the APP, as described in step S306a below. Step S305a is a prerequisite operation for S306a. Alternatively, during APP runtime, the APP client deployed on the terminal device also sends signaling to the DNS server, causing the DNS server to select an EAS for the APP, as described in step S306b below. Step S305b is a prerequisite operation for S306b.

[0168] S305a. Each EAS reports its own information to the APP scheduler. The information reported by the EAS includes: the location of the EAS, the IP address of the EAS, and the port number of the EAS. Optionally, the information reported by the EAS also includes the load of the EAS.

[0169] S306a. The APP client sends higher-level signaling to the APP scheduler. This higher-level signaling is used to request access to the EAS for processing application data. This higher-level signaling includes the IP address of the terminal device.

[0170] For a detailed explanation of steps S305a and S306a, please refer to the detailed explanation of S103a and S104a in the aforementioned method 1, and will not be repeated here.

[0171] S305b: Manually configure the APP domain name address record for the DNS server. The APP domain name address record includes the IP address and port number of each EAS.

[0172] S306b: The APP client sends a request message to the DNS server. This request message is used to query the IP address of the EAS that processes application data. This request message includes the IP address of the terminal device.

[0173] For a detailed explanation of steps S305b and S306b, please refer to the detailed explanation of S103b and S104b in the aforementioned method 1, and will not be repeated here.

[0174] In addition, after the APP client obtains the IP address and port number of EAS, it can execute step S307.

[0175] S307: The APP client sends application data and the target address to the OS in the terminal device. The target address is the IP address and port number of the EAS obtained by the APP client. The OS in the terminal device then sends the application data and the target address to the UPF network element of the main network through the access network device.

[0176] After receiving application data and the target address, the S308 and the large-scale UPF network element will report the detection of application data and the target address to the SMF network element. Furthermore, the large-scale UPF network element caches the application data.

[0177] Based on the target address, i.e., the IP address and port number of the EAS, the S309 and SMF network elements select the edge UPF network element that is in the same edge computing node as the EAS and establish a dedicated EAS session.

[0178] For example, when an SMF network element establishes a dedicated EAS session, it includes: the SMF network element instructing the main network UPF network element to establish an N9 tunnel between the selected edge UPF network element and the main network UPF network element. For a detailed explanation of "the SMF network element instructing the main network UPF network element to establish an N9 tunnel between the selected edge UPF network element and the main network UPF network element," please refer to the relevant explanation in Method 2, which will not be repeated here.

[0179] S310. After the N9 tunnel between the main network UPF element and the edge UPF element is established, the main network UPF element sends the cached application data to the edge UPF element through the N9 tunnel.

[0180] After receiving the application data, the edge UPF network element sends the application data to the EAS corresponding to the target address based on the target address.

[0181] As can be seen, in methods 1 and 2 above, the APP scheduler or DNS server selects the EAS for the terminal device, and the SMF network element selects the edge UPF network element for the terminal device. In cases where the APP scheduler or DNS server is unaware of the edge UPF network element, and the SMF network element is unaware of the EAS, the selection of the EAS and the edge UPF network element are executed independently. The selected EAS and edge UPF network element may be deployed on different edge computing nodes. The edge UPF network element needs to cross edge computing nodes to transmit the terminal's application data to the EAS, resulting in increased application data transmission latency and decreased efficiency of terminal computing offloading. In this embodiment, the edge computing node can also be understood as a data center (DC).

[0182] For example, as shown in Figure 7, edge UPF network element 1 and EAS1 are located in edge computing node 1, and edge UPF network element 2 and EAS2 are located in edge computing node 2. Assuming that the SMF network element selected for terminal device 1 is edge UPF network element 1, and the APP scheduler or DNS server selected EAS2 for terminal device 1, then, as shown by the gray arrow in Figure 7, after receiving application data from terminal device 1 forwarded by the access network device, edge UPF network element 1 in edge computing node 1 needs to bypass the metropolitan area network to send the application data to EAS2 in edge computing node 2, increasing the transmission latency of the application data. In this embodiment, the metropolitan area network can be, for example, the China Mobile Network Metropolis Backbone (CMNET MB) network, as illustrated in Figure 7 using CMNET MB as an example.

[0183] In Method 3, the EAS is selected by the DNS server or the APP scheduler. After the terminal device determines the EAS selected by the DNS server or the APP scheduler as the destination address for application data, the SMF network element then selects an edge UPF network element based on the destination address of the application data from the terminal device. However, the DNS server or the APP scheduler is unaware of the edge UPF network element when selecting the EAS, which cannot guarantee that the edge UPF network element subsequently selected by the SMF network element can transmit application data to the EAS, thus reducing the efficiency of terminal computing power offloading.

[0184] This application provides a communication method in which a first network element uniformly selects a first edge user plane network element and a first edge application server located in the same edge computing node. The first network element configures the first edge user plane network element for transmitting data of a first application from a terminal device to the first edge application server. This allows the first edge user plane network element to transmit data of the first application to the first edge application server within the same edge computing node, without needing to transmit the data of the first application across edge computing nodes. This reduces the transmission latency of application data and improves the efficiency of terminal computing power offloading. The first network element may, for example, be a session management network element.

[0185] The embodiments of this application are described in detail below with reference to the accompanying drawings. This application uses the first network element as the session management network element, and the execution entities as the session management network element and the terminal device, to illustrate the corresponding method. For example, the session management network element in the method can be an SMF network element in a 5G network, or a network element or device with session management network element functionality in a future communication network. The session management network element can also be replaced by a module, unit, or chip within the session management network element. For example, the terminal device in the method can be a terminal device, or it can be a module, unit, or chip within a terminal device. Furthermore, other network elements / devices involved in the method can also be chips, chip systems, or processors that support the implementation of the corresponding method by the network element / device, or logic modules or software capable of implementing all or part of the functions of the network element / device.

[0186] Please refer to Figure 8, which is a flowchart illustrating a communication method provided in an embodiment of this application. The communication method includes the following steps.

[0187] S401. The session management network element determines the first edge user plane network element and the first edge application server. The first edge user plane network element and the first edge application server belong to the same edge computing node.

[0188] In one optional implementation, the first edge application server and the first edge user plane network element belong to the same edge computing node, including: the identifier of the edge computing node to which the first edge application server belongs matches the identifier of the edge computing node to which the first edge user plane network element belongs. Here, matching the identifier of the edge computing node to which the first edge application server belongs and the identifier of the edge computing node to which the first edge user plane network element belongs means that the identifier of the edge computing node to which the first edge application server belongs and the identifier of the edge computing node to which the first edge user plane network element belongs are used to identify the same edge computing node. For example, the identifier of the edge computing node to which the first edge application server belongs and the identifier of the edge computing node to which the first edge user plane network element belongs are the same. Another example is that the identifier of the edge computing node to which the first edge application server belongs and the identifier of the edge computing node to which the first edge user plane network element belongs are of different types and / or values, but as long as they identify the same edge computing node, it is considered that the identifier of the edge computing node to which the first edge application server belongs and the identifier of the edge computing node to which the first edge user plane network element belongs match.

[0189] In this embodiment, the identifier of the edge computing node can be, for example, an edge node location identification (ENLI), which uniquely identifies the location of the edge computing node. ENLI can be a string, such as enli.XXX.YYY, where "XXX" can be the operator name and "YYY" can be the geographical location of the edge computing node, such as the city where the edge computing node is located. However, this embodiment does not limit the name of "ENLI," and for ease of explanation, "ENLI" will be used as an example below.

[0190] Furthermore, compared to using data network access identification (DNAI) to identify the access location of edge computing nodes, the identification of edge computing nodes mentioned in the embodiments of this application is beneficial for session management network elements to determine whether edge user plane network elements and edge application servers belong to the same edge computing node, and thus determine the first edge application server and the first edge user plane network element belonging to the same edge computing node. This will be explained below with reference to Figures 9 and 10.

[0191] For example, a brief explanation of DNAI is provided: DNAIs are manually assigned to multiple edge computing nodes within the same metropolitan area network (MAN). These edge computing nodes may share the same DNAI or use different DNAIs. Each edge user plane network element needs to configure the DNAI of all edge computing nodes located within the same MAN. The DNAI identifies the access location of the edge computing node. The edge user plane network element can determine, based on the DNAI, where to send application data to the edge application server within the edge computing node identified by that DNAI.

[0192] For example, referring to Figure 9, edge user plane network element 1 and edge application server 1 belong to edge computing node 1, and edge user plane network element 2 and edge application server 2 belong to edge computing node 2. DNAI1 is used to identify edge computing node 1. DNAI2 is used to identify edge computing node 2. Both edge user plane network element 1 and edge user plane network element 2 are configured with DNAI1 and DNAI2. Terminal device 1 sends the destination address of application data 1 to the access network device, and then the access network device sends the destination address of application data 1 to edge user plane network element 1. If the destination address of application data 1 received by edge user plane network element 1 is the address information of edge application server 2, then edge user plane network element 1 determines the DNAI2 corresponding to edge application server 2, and then sends application data 1 to edge application server 2 based on DNAI2. Terminal device 2 sends the destination address of application data 2 to the access network device, and then the access network device sends the destination address of application data 2 to edge user plane network element 1. If the destination address of the application data 2 received by edge user plane network element 1 is the address information of edge application server 1, then edge user plane network element 1 determines the DNAI1 corresponding to edge application server 1, and then sends application data 2 to edge application server 1 via the metropolitan area network based on DNAI1. Edge user plane network element 2 works similarly and will not be described in detail.

[0193] The usage of the edge computing node identifier mentioned in the embodiments of this application includes: the session management network element determines whether the edge user plane network element and the edge application server belong to the same edge computing node based on the identifier of the edge computing node to which the edge user plane network element belongs and the identifier of the edge computing node to which the edge application server belongs, so that the session management network element can determine the first edge application server and the first edge user plane network element that belong to the same edge computing node.

[0194] For example, referring to Figure 10, edge user plane network element 1 and edge application server 1 belong to edge computing node 1, and edge user plane network element 2 and edge application server 2 belong to edge computing node 2. The identifier of edge computing node 1 is ENLI1, which is enli.XXX.YYY.1. The identifier of edge computing node 2 is ENLI2, which is enli.XXX.YYY.2. Based on the fact that the ENLI of the edge computing node to which edge user plane network element 1 belongs is the same as the ENLI of the edge computing node to which edge application server 1 belongs, the session management network element can determine that edge user plane network element 1 and edge application server 1 belong to the same edge computing node. Similarly, based on the fact that the ENLI of the edge computing node to which edge user plane network element 2 belongs is the same as the ENLI of the edge computing node to which edge application server 2 belongs, the session management network element can determine that edge user plane network element 2 and edge application server 2 belong to the same edge computing node. Therefore, the session management network element can determine that the first edge user plane network element and the first edge application server are edge user plane network element 1 and edge application server 1, or edge user plane network element 2 and edge application server 2, respectively.

[0195] Alternatively, the identifier of the edge computing node to which the edge user plane network element belongs is configured by the manager for the edge user plane network element, and the identifier of the edge computing node to which the edge application server belongs is configured by the manager for the edge application server.

[0196] For example, when deploying edge user plane network elements, the manager adds the identifier of the edge computing node to which the edge user plane network element belongs to the virtualized network function descriptor (VNFD) in the template file issued to the edge user plane network element. This allows the edge user plane network element to read the identifier of its own edge computing node from the template file. Similarly, when deploying edge application servers, the manager adds the identifier of the edge computing node to which the edge application server belongs to the template file issued to the edge application server. This allows the edge application server to read the identifier of its own edge computing node from the template file.

[0197] For example, the manager can configure the identifier of the edge computing node to which the edge user plane network element belongs to the edge user plane network element through the operation and maintenance (OM) module, and configure the identifier of the edge computing node to which the edge application server belongs to the edge application server through the OM module.

[0198] However, this application embodiment does not limit the specific method by which edge user plane network elements and edge application servers determine the identifier of the edge computing power node to which they belong.

[0199] In one optional implementation, the session management network element determines the first edge user plane network element and the first edge application server, including: the session management network element determining the edge user plane network element whose service range includes the location of the terminal device as the first edge user plane network element; and determining the edge application server that supports processing the data of the first application among the edge application servers belonging to the same edge computing node as the first edge user plane network element as the first edge application server.

[0200] Optionally, the session management network element determines the edge user plane network element whose service range includes the location of the terminal device as the first edge user plane network element, including: the session management network element determines the edge user plane network element that meets the first condition as the first edge user plane network element, wherein the first condition is: 1) the service range includes the location of the terminal device; 2) the edge application server that belongs to the same edge computing node as the edge user plane network element includes the edge application server that supports processing the first application.

[0201] For example, the service range of both edge user plane network element 1 and edge user plane network element 2 includes the location of the terminal device. Edge application server 1, which belongs to the same edge computing node as edge user plane network element 1, does not support processing data for the first application, while edge application server 2, which belongs to the same edge computing node as edge user plane network element 2, does support processing data for the first application. Therefore, the session management network element can determine that edge user plane network element 2 is the first edge user plane network element and edge application server 2 is the first edge application server.

[0202] Optionally, the location of the terminal device can be represented using a tracking area (TA). For example, the session management network element can pre-configure a mapping relationship between the TA and edge user plane network elements. The service range of the edge user plane network element mapped to the TA includes that TA. The mapping relationship between the TA and the edge user plane network element can be, for example, a mapping relationship between the TA and the identifier of the edge user plane network element. The identifier of the edge user plane network element can be, for example, the ID of the edge user plane network element, such as the UPF ID in a 5G network.

[0203] Understandably, the session management function network element, based on the TA of the terminal device, can determine at least one edge user plane network element that has a mapping relationship with the TA of the terminal device, that is, determine at least one edge user plane network element whose service range includes the location of the terminal device. The session management function network element then determines the first edge user plane network element from the at least one edge user plane network element that has a mapping relationship with the TA of the terminal device.

[0204] For example, edge user plane network elements mapped to TA1 include edge user plane network element 1 and edge user plane network element 2, while edge user plane network elements mapped to TA2 include edge user plane network element 3 and edge user plane network element 4. If the terminal device is located at TA1, the session management network element determines the first edge user plane network element from edge user plane network element 1 and edge user plane network element 2. If the terminal device is located at TA2, the session management network element determines the first edge user plane network element from edge user plane network element 3 and edge user plane network element 4.

[0205] In addition, besides using TA to represent the location of the terminal device, other methods can also be used to represent the location of the terminal device in this embodiment of the application, and there are no restrictions on this.

[0206] Optionally, the first edge application server supports processing data of the first application, including: the identifier of the application supported by the first edge application server includes the identifier of the first application. In this embodiment, "edge application server supports application" means that the edge application server supports processing data of the application. Optionally, the application identifier can be, for example, an APP ID. For example, the APP ID of M Video is com.M.video. The APP ID of M Cloud Gaming is com.M.cloudgaming. The APP ID of M AIGC is com.M.aigc. Here, "M" can be the name of the APP, or it can be the name of the APP's developer. This embodiment does not limit the form of the application identifier.

[0207] Using the location of the terminal device as TA, and the identifier of the edge user plane network element as UPF ID, the identifier of the application as APP ID, and the identifier of the edge computing node as ENLI, as shown in Figure 11, the identifier of edge user plane network element 1 is UPF ID1, and the ENLI of the edge computing node to which edge user plane network element 1 belongs is ENLI1. The identifier of edge user plane network element 2 is UPF ID2, and the ENLI of the edge computing node to which edge user plane network element 2 belongs is ENLI2. The identifier of edge user plane network element 3 is UPF ID3, and the ENLI of the edge computing node to which edge user plane network element 3 belongs is ENLI3. The identifiers of the applications supported by edge application server 1 include APP ID1 and APP ID2, and the ENLI of the edge computing node to which edge application server 1 belongs is ENLI1. The identifiers of the applications supported by edge application server 2 include APP ID2 and APP ID3, and the ENLI of the edge computing node to which edge application server 2 belongs is ENLI2. The application identifiers supported by edge application server 3 include APP ID1 and APP ID3, and the ENLI of the edge computing node to which edge application server 3 belongs is ENLI3. It can be seen that edge user plane network element 1 and edge application server 1 belong to the same edge computing node, edge user plane network element 2 and edge application server 2 belong to the same edge computing node, and edge user plane network element 3 and edge application server 3 belong to the same edge computing node. Assuming the location of the terminal device is TA1, the identifier of the first application is APP ID1. The UPF IDs that have a mapping relationship with TA1 include UPF ID1 and UPF ID2.

[0208] In one optional approach, the session management network element, based on UPF ID1, can determine the ENLI1 corresponding to edge user plane network element 1, and thus determine the edge application server 1 corresponding to ENLI1. Similarly, the session management network element, based on UPF ID2, can determine the ENLI2 corresponding to edge user plane network element 2, and thus determine the edge application server 2 corresponding to ENLI2. Since the identifiers of applications supported by edge application server 1 include APP ID1, while the identifiers of applications supported by edge application server 2 do not include APP ID1, the session management network element can determine that the first edge application server is edge application server 1, and the first edge user plane network element is edge user plane network element 1.

[0209] In another optional approach, the session management network element determines the ENLI1 corresponding to edge user plane network element 1 based on UPF ID1, and then determines the edge application server 1 corresponding to ENLI1. The session management network element determines that the identifier of the application supported by edge application server 1 includes APP ID1. Therefore, the session management network element determines that the first edge application server is edge application server 1, and the first edge user plane network element is edge user plane network element 1. In this approach, the session management network element does not need to determine the edge application server 2 with the same ENLI1 as edge user plane network element 2 based on UPF ID2, thus saving power consumption.

[0210] In one optional implementation, the first edge user plane network element and the first edge application server further satisfy at least one of the following conditions:

[0211] Condition 1: The load of the first edge user plane network element is less than or equal to the first threshold.

[0212] Condition 2: The load of the first edge application server is less than or equal to the second threshold.

[0213] Condition 3: The load of the first edge user plane network element is the smallest among the loads of multiple edge user plane network elements, and the service range of these multiple edge user plane network elements includes the location of the terminal device.

[0214] Condition 4: The load of the first edge application server is the lowest among the loads of multiple edge application servers, which support the processing of data from the first application.

[0215] Condition 5: The latency of the first edge user plane network element is the lowest among the latencies of multiple edge user plane network elements, and the service range of these multiple edge user plane network elements includes the location of the terminal device.

[0216] The first and second thresholds can be pre-configured, for example, without any restrictions.

[0217] Understandably, when the first edge application server satisfies condition 1, it indicates that the first edge user plane network element has available resources for transmitting data from the terminal device to the first edge application server, which is beneficial to improving the reliability of data transmission. In this embodiment, the resources of the edge user plane network element may include at least one of the following: storage space or power of the edge user plane network element, etc.

[0218] When the first edge application server meets condition 2, it indicates that the first edge application server has available resources to process data from the first application on the terminal device, which is beneficial to the normal operation of the first application and improves the user experience. In this embodiment, the resources of the edge application server may include at least one of the following: storage space, computing power, or power consumption of the edge application server, etc.

[0219] When the first edge user plane network element satisfies condition 3, it means that among the multiple edge user plane network elements whose service range includes the location of the terminal device, the first edge user plane network element has the least used resources. It can be seen that the first edge user plane network element has relatively more available resources that can be used for the transmission of data of the first application from the terminal device to the first edge application server, which is beneficial to improving the reliability of data transmission.

[0220] When the first edge application server meets condition 4, it means that among the multiple edge application servers that support the processing of data for the first application, the first edge application server has the least amount of used resources. This indicates that the first edge application server has relatively more available resources to process data from the first application on the terminal device, which is beneficial to the normal operation of the first application and improves the user experience.

[0221] When the first edge user plane network element meets condition 5, it helps to reduce the data transmission latency of the first application and improve the user experience.

[0222] Optionally, in the scenario where the first edge user plane network element satisfies condition 1, if the load of each edge user plane network element is less than or equal to the first threshold, the first edge user plane network element may further satisfy the following condition: the load of the first edge user plane network element is the smallest among the multiple edge user plane network elements whose load is less than or equal to the first threshold.

[0223] Optionally, in the scenario where the first edge application server satisfies condition 2, if the load of each edge application server among the multiple edge application servers is less than or equal to the second threshold, the first edge application server may further satisfy the following condition: the load of the first edge application server is the smallest among the multiple edge application servers whose load is less than or equal to the second threshold.

[0224] For example, the following assumes that the service range of each of the M1 edge user plane network elements includes the location of the terminal device, and M1 is an integer greater than 1. An exemplary implementation method is provided for the operation of determining the first edge user plane network element and the first edge application server for the session management network element:

[0225] The session management network element determines the M1 edge application servers corresponding to the M1 edge user plane network elements. In this embodiment, the correspondence between the edge user plane network element and the edge application server means that the edge user plane network element and the edge application server belong to the same edge computing node.

[0226] The session management network element determines M2 edge application servers from M1 edge application servers that support processing data for the first application. If M2 equals 1, the session management network element determines the edge application server from the M1 edge application servers that supports processing data for the first application as the first edge application server, and determines the edge user plane network element that belongs to the same edge computing node as the first edge application server as the first edge user plane network element.

[0227] If M2 is greater than 1, the session management network element determines M3 edge application servers from the M2 edge application servers whose load is less than or equal to the second threshold, and M4 edge user plane network elements from the M2 edge user plane network elements corresponding to the M2 edge application servers whose load is less than the first threshold. The session management network element then determines M5 combinations belonging to the same edge computing node from the M3 and M4 edge user plane network elements. Each of the M5 combinations consists of an edge application server and an edge user plane network element belonging to the same edge computing node. If M5 equals 1, the session management network element determines that the edge user plane network element and the edge application server in this combination are respectively the first edge user plane network element and the first edge application server.

[0228] If M5 is greater than 1, the session management network element determines the M6 ​​edge user plane network elements with the lowest latency from the total M5 edge user plane network elements included in the M5 combinations. If M6 equals 1, the session management network element determines the edge user plane network element with the lowest latency among the M5 edge user plane network elements as the first edge user plane network element, and determines the edge application server belonging to the same edge computing node as the first edge application server.

[0229] If M6 is greater than 1, the session management network element determines the M7 edge application servers with the lowest load from the total M5 edge application servers included in the M5 combinations. If M7 equals 1, the session management network element determines the edge application server with the lowest load among the M5 edge application servers as the first edge application server, and determines the edge user plane network element belonging to the same edge computing node as the first edge user plane network element.

[0230] If M7 is greater than 1, the session management network element determines the M8 edge user plane network elements with the lowest load from the M7 edge user plane network elements corresponding to the M7 edge application servers. If M8 equals 1, the session management network element determines the edge user plane network element with the lowest latency among the M7 edge user plane network elements as the first edge user plane network element, and determines the edge application server belonging to the same edge computing node as the first edge application server.

[0231] If M8 is greater than 1, the session management network element randomly selects one of the M7 combinations consisting of M7 edge application servers and M7 edge user plane network elements, and determines the edge user plane network element and edge application server in the randomly selected combination as the first edge user plane network element and the first edge application server, respectively. Each of the M7 combinations consists of edge application servers and edge user plane network elements belonging to the same edge computing node.

[0232] As can be seen, in the exemplary method provided above, when the session management network element determines the first edge user plane network element and the first edge application server, the priority order of considering the three factors—"minimum latency of the first edge user plane network element," "minimum load of the first edge application server," and "minimum load of the first edge user plane network element"—is as follows: "minimum latency of the first edge user plane network element" takes precedence over "minimum load of the first edge application server," and "minimum load of the first edge application server" takes precedence over "minimum load of the first edge user plane network element." However, this application embodiment does not limit the priority order of these three factors. For example, the priority order of these three factors can also be: "minimum latency of the first edge user plane network element" takes precedence over "minimum load of the first edge user plane network element," "minimum load of the first edge user plane network element" takes precedence over "minimum load of the first edge application server," or other orders, etc.

[0233] In another optional approach, to ensure the transmission of data for the first application, if the session management network element cannot determine which edge user plane network elements and edge application servers belong to the same edge computing node among the edge user plane network elements and edge application servers that meet the following conditions: the service range of the edge user plane network element includes the location of the terminal device, the load of the edge user plane network element is less than a first threshold, the edge application server supports processing data for the first application, and the load of the edge application server is less than a second threshold, then the session management network element determines the edge user plane network element with the lowest latency as the second edge user plane network element from at least one edge user plane network element whose service range includes the location of the terminal device and whose load is less than the first threshold, and determines the edge application server with the lowest load as the second edge application server from at least one edge application server that supports processing data for the first application and whose load is less than the second threshold. Understandably, the second edge user plane network element and the second edge application server do not belong to the same edge computing node.

[0234] In the subsequent process, the session management network element configures the second edge user plane network element for the transmission of data from the terminal device to the second edge application server for the first application. The session management network element sends the address information of the second edge application server, which processes the data from the terminal device for the first application. Correspondingly, the terminal device sends the data of the first application to the second edge application server based on the address information of the second edge application server. Similar to steps S402 to S404 for the first edge user plane network element and the first edge application server described later, a detailed explanation of steps S402 to S404 can be found in the following descriptions and will not be repeated here.

[0235] For example, edge user plane network element 1 and edge application server 1 belong to the same edge computing node, and edge user plane network element 2 and edge application server 2 belong to the same edge computing node. The service range of both edge user plane network element 1 and edge user plane network element 2 includes the location of the terminal device. The load of edge user plane network element 1 is less than a first threshold, while the load of edge user plane network element 2 is greater than the first threshold. Both edge application server 1 and edge application server 2 support processing data for the first application. The load of edge application server 1 is greater than a second threshold, while the load of edge application server 2 is less than the second threshold. Therefore, to ensure the transmission of data for the first application, the session management network element designates edge user plane network element 1 as the second edge user plane network element and edge application server 2 as the second edge application server. Edge application server 2 is used to process data from the first application originating from the terminal device, while edge user plane network element 1 is used for transmitting data from the terminal device to edge application server 2.

[0236] In an optional implementation, before step S401, the method further includes: a first edge user plane network element sending its information to a session management network element, and a first edge application server sending its information to the session management network element. Correspondingly, the session management network element receives the information from the first edge user plane network element and the information from the first application server. The information from the first edge user plane network element includes the identifier of the edge computing node to which the first edge user plane network element belongs, and the information from the first edge application server includes the identifier of the edge computing node to which the first edge application server belongs.

[0237] In one optional approach, each of the one or more edge user plane network elements sends its own information, and each of the one or more edge application servers sends its own information. Correspondingly, the session management network element receives information from the one or more edge user plane network elements and information from the one or more edge application servers. The information of the edge user plane network elements includes the identifier of the edge computing node to which the edge user plane network element belongs, and the information of the edge application servers includes the identifier of the edge computing node to which the edge application server belongs. The one or more edge user plane network elements include a first edge user plane network element, and the one or more edge application servers include a first edge application server.

[0238] Accordingly, step S401 includes: the session management network element determines a first edge user plane network element from one or more edge user plane network elements and a first edge application server from one or more edge application servers based on the information of one or more edge user plane network elements and the information of one or more edge application servers, wherein the first edge user plane network element and the first edge application server belong to the same edge computing node.

[0239] Understandably, since the information received by the session management network element from the edge user plane network element includes the identifier of the edge computing node to which the edge user plane network element belongs, and the information received from the edge application server includes the identifier of the edge computing node to which the edge application server belongs, the session management network element can determine whether the edge user plane network element and the edge application server belong to the same edge computing node based on whether the identifier of the edge computing node to which the edge user plane network element belongs matches the identifier of the edge computing node to which the edge application server belongs. Furthermore, it can determine the first edge user plane network element and the first edge application server that belong to the same edge computing node. Specifically, the identifier of the edge computing node to which the first edge user plane network element belongs, included in the information of the first edge user plane network element, matches the identifier of the edge computing node to which the first edge application server belongs, included in the information of the first edge application server.

[0240] Optionally, the information of the edge user plane network element may also include one or more of the following: the identifier of the edge user plane network element, the load of the edge user plane network element, or the latency of the edge user plane network element. The latency of the edge user plane network element may, for example, include one or more of the following: the latency between the edge user plane network element and the access network equipment, or the latency between the edge user plane network element and the main network user plane network element. For example, in a 5G network, the latency between the edge user plane network element and the access network equipment may also be referred to as the N3 latency, and the latency between the edge user plane network element and the main network user plane network element may also be referred to as the N9 latency. Optionally, the method may further include: measuring the latency between the edge user plane network element and the access network equipment, and / or measuring the latency between the edge user plane network element and the main network user plane network element.

[0241] Understandably, including the load of the edge user plane network element in the information helps the session management network element determine the first edge user plane network element whose load is less than a first threshold. Including the latency of the edge user plane network element in the information helps the session management network element determine the first edge user plane network element with the lowest latency among multiple edge user plane network elements whose service range includes the location of the terminal device.

[0242] Optionally, the information of the edge application server may also include one or more of the following: the identifier of the application supported by the edge application server, the load of the edge application server, the application domain name of the edge application server, or the address information of the edge application server. The application domain name may be, for example, a fully qualified domain name (FQDN). The address information of the edge application server may include, for example, the IP address and port number of the edge application server.

[0243] Understandably, including the identifier of the application supported by the edge application server helps the session management network element determine the first edge application server that supports processing data for the first application. Including the load of the edge application server helps the session management network element determine the first edge application server whose load is less than the second threshold. Including the address information of the edge application server helps the session management network element determine the address information of the first edge application server, so that the session management network element can send the address information of the first edge application server in step S403.

[0244] Alternatively, edge user plane network elements can send their information directly to the session management network element, or they can send it indirectly. For example, edge user plane network elements can send their information indirectly to the session management network element through a manager. For instance, each of one or more edge user plane network elements sends its own information to the manager, and the manager then sends the information of each of the one or more edge user plane network elements to the session management network element. For example, edge user plane network elements can send their information to the manager through registration. For instance, an edge user plane network element sends a registration request message to the manager, requesting to register its information, which includes the edge user plane network element's information. After receiving the registration request message, the manager stores the edge user plane network element's information so that the manager can publish the edge user plane network element's information to the session management network element.

[0245] Similarly, edge application servers can send their information directly to the session management network element, or they can send it indirectly. For example, an edge application server can send its information indirectly to the session management network element through a manager. For instance, each of one or more edge application servers sends its own information to the manager, and the manager then sends the information of each of the one or more edge application servers to the session management network element. For example, an edge application server can send its own information to the manager through registration. This is similar to the process described above where edge user plane network elements send their own information to the manager through registration, and will not be elaborated further.

[0246] Furthermore, this application embodiment does not restrict the mode of information transmission by edge user plane network elements. For example, the edge user plane network element only needs to send its identifier and the identifier of the edge computing node to which it belongs once, directly or indirectly; while it can send its load and latency information to the session management network element multiple times, in real time, periodically, or non-periodically. Similarly, this application embodiment does not restrict the mode of information transmission by edge application servers. For example, the edge application server only needs to send its identifier, the identifier of the edge computing node to which it belongs, its application domain name, and its address information once, directly or indirectly; while it can send its load information to the session management network element multiple times, in real time, periodically, or non-periodically.

[0247] In one alternative implementation, prior to step S401, the method further includes either implementation 1.1 or implementation 1.2.

[0248] In implementation method 1.1, the terminal device sends a first request message to the session management network element. The first request message is used to request the establishment of a session, which is used for the transmission of data of the first application from the terminal device to the first edge application server. In this embodiment, the session is, for example, a PDU session, which will not be described further below.

[0249] Optionally, the first request message includes an identifier of the first application. For example, the identifier of the first application included in the first request message can be used by the session management network element to determine a first edge application server that supports processing data for the first application. The identifier of the first application included in the first request message can also be used by the session management network element to determine that the session requested by the terminal device is an application-specific session, so that the first response message subsequently sent by the session management network element to the terminal device includes the address information of the first edge application server. Optionally, the first response message also includes the identifier of the first application and / or the application domain name of the first edge application server. The identifier of the first application included in the first request message can also be used by the session management network element to determine that the application targeted by the enhanced content billing function during application operation is the first application. For example, the session management network element determines that the application identifier corresponding to the billing call detail record is the identifier of the first application, which is beneficial for the operator to which the session management network element belongs to achieve refined traffic operation.

[0250] For example, the first request message is a PDU session establishment request message. Optionally, the terminal device indirectly sends the first request message to the session management network element through an access and mobility management network element. For example, the first request message sent by the terminal device to the access and mobility management network element is carried in a non-access stratum message, and the first request message sent by the access and mobility management network element to the session management network element is carried in a session establishment context request message, which may be a PDU session establishment SM context request message, where SM stands for session management. The access and mobility management network element is, for example, an AMF network element.

[0251] Optionally, the terminal device sends a first request message based on the URSP mechanism. For example, the terminal device is a terminal OS, and the application client sends the identifier of the first application to the terminal OS when installing the first application. The terminal OS determines the identifier of the first application when it detects that the first application is running. Then, the terminal OS determines the URSP rule that matches the identifier of the first application, which includes the identifier of the first application and the identifier of the first slice. Then, the terminal OS sends the first request message. In this scenario, the first request message includes not only the identifier of the first application but also the identifier of the first slice, so that the session management network element can determine the first edge user plane network element that supports the first slice.

[0252] Optionally, the URSP rules are sent to the terminal device by the policy control network element through the access and mobility management network element. For example, when the application network element registers the application's identifier when signing a slicing agreement with the operator, it maps the application's identifier and the slice's identifier to the URSP rules. The application network element sends the URSP rules to the policy control network element, which in turn sends them to the access and mobility management network element, which then sends them to the terminal device. In this embodiment, the policy control network element may be, for example, a PCF network element. The application network element may be, for example, an AF network element or an APP scheduler.

[0253] Alternatively, in implementation 1.1, after the session management network element receives the first request message from the terminal device, it can uniformly select the first edge user plane network element and the first edge application server through step S401.

[0254] In implementation method 1.2, the terminal device sends a third request message to the application network element, which requests access to an edge application server that processes data for the first application on the terminal device; correspondingly, the application network element receives the third request message. The application network element sends a second request message to the session management network element, which requests allocation of an edge application server for processing data for the first application on the terminal device; correspondingly, the session management network element receives the second request message. The third request message may, for example, be a higher-layer signaling message sent by an application client deployed in the terminal device to the application network element. Optionally, the second request message can also be understood as: requesting allocation / scheduling of an edge application server for processing data for the first application on the terminal device.

[0255] Optionally, the application network element sends a second request message to the session management network element, including: the application network element calling a network-exposed API to send a second request message to a network-exposed network element in the network, and then the network-exposed network element forwarding the second request message to the session management network element in the network. The network-exposed network element can be, for example, a NEF network element.

[0256] Optionally, the third request message includes the identifier of the first application, and / or the second request message includes the identifier of the first application. This approach helps the session management network element determine the first edge application server that supports processing data of the first application based on the identifier of the first application.

[0257] Optionally, the second request message may also include the identifier of the terminal device, so that the session management network element can determine the session requested by the terminal device based on the identifier of the terminal device, and then determine the location of the terminal device based on the session, thereby determining the first edge user plane network element whose service range includes the location of the terminal device.

[0258] Optionally, the method further includes: the terminal device sending a fourth request message to the session management network element, the fourth request message being used to request the establishment of a session. The session requested by the fourth request message differs from the session requested by the first request message in the aforementioned implementation 1.1. The fourth request message is sent by the terminal device without configured URSP rules to request the establishment of a session; the session requested by the fourth request message is a general network session, not an application-specific session requested by the first request message. Based on the identifier of the terminal device, the session management network element can determine the general network session requested by the terminal device, and then determine the location of the terminal device based on the general network session, thereby determining the first edge user plane network element whose service area includes the location of the terminal device.

[0259] Understandably, in implementation method 1.2, after receiving the third request message from the terminal device, the application network element does not select an edge application server. The application network element sends a second request message to the session management network element. After receiving the second request message, the session management network element selects the first edge application server and the first edge user plane network element based on step S401.

[0260] In another alternative approach, after receiving a third request message from the terminal device, the application network element determines a third edge application server. This third edge application server supports processing data from the first application, and its load is less than a second threshold. The application network element sends the identifier of the first application and the address information of the third edge application server to the session management network element. Optionally, each of the one or more edge application servers can pre-report its own information to the application network element, allowing the application network element to determine the third edge application server from among these servers. Information regarding edge application servers can be found in the foregoing descriptions and will not be repeated here.

[0261] Upon receiving the address information of the third edge application server, the session management network element does not select an edge application server but instead determines a third edge user plane network element. For example, when determining the third edge user plane network element, the session management network element prioritizes edge user plane network elements belonging to the same edge computing node as the third edge application server. If the load of an edge user plane network element belonging to the same edge computing node as the third edge application server exceeds a first threshold, the session management network element determines an edge user plane network element with a load less than or equal to the first threshold as the third edge user plane network element. In this scenario, the third edge user plane network element and the third edge application server do not belong to the same edge computing node.

[0262] Alternatively, if the session management network element receives the address information of the third edge application server, and the load of the edge user plane network element belonging to the same edge computing node as the third edge application server is less than or equal to the first threshold, the session management network element will not select the edge application server and will instead determine the third edge user plane network element. For a detailed explanation of how the session management network element determines the third edge user plane network element, please refer to the aforementioned related explanations, which will not be repeated here. If the load of the edge user plane network element belonging to the same edge computing node as the third edge application server is greater than the first threshold, step S401 will be executed to uniformly select the first edge application server and the first edge user plane network element.

[0263] Specifically, when the application network element determines the third edge application server and the session management network element determines the third edge user plane network element, the third edge user plane network element is used for the transmission of data from the terminal device to the third edge application server for the first application, and the third edge application server is used for processing the data from the terminal device for the first application. Similar to steps S402 to S404 performed on the first edge user plane network element and the first edge application server later in the text, a detailed explanation of steps S402 to S404 can be found in the following descriptions and will not be repeated here.

[0264] When the session management network element uniformly selects the first edge application server and the first edge user plane network element by executing step S401, the first edge user plane network element is used for the transmission of data of the first application from the terminal device to the first edge application server, and the first edge application server is used for processing the data of the first application from the terminal device, as described in steps S402 to S404 below.

[0265] S402. The session management network element configures the first edge user plane network element for the transmission of data from the terminal device to the first edge application server for the first application.

[0266] In one optional implementation, the session management network element configures the first edge user plane network element for the transmission of data of the first application from the terminal device to the first edge application server, including: the session management network element configures the first edge user plane network element to send data from the first application of the terminal device to the first edge application server.

[0267] Alternatively, it may include: configuring the session management network element to configure the first edge user plane network element so that the first edge user plane network element sends data from the first application of the terminal device to the first edge application server;

[0268] Alternatively, it may include: the session management network element sending configuration information to the first edge user plane network element, the configuration information being used by the first edge user plane network element to send data from the first application of the terminal to the first edge application server.

[0269] The possible implementations of step S402 are illustrated below by example, as described in optional implementation methods 2.1 and 2.2. Implementation method 2.1 can be applied to the situation described in implementation method 1.1, and implementation method 2.2 can be applied to the situation described in implementation method 1.2.

[0270] In implementation 2.1, step S402 includes: the session management network element sending a forwarding rule to the first edge user plane network element, the forwarding rule being used to instruct the first edge user plane network element to forward data from the first application of the terminal device to the first edge application server. Optionally, step S402 further includes: the session management network element sending one or more of the following to the first edge user plane network element: the identifier of the first application, the address information of the first edge application server, and the application domain name of the first edge application server.

[0271] Understandably, the first edge user plane network element can determine, based on the identifier of the first application received from the session management network element, that the session requested by the terminal device is an application-specific session, and subsequently forward the data of the first application according to the forwarding rules when it receives data from the first application. Optionally, the first edge user plane network element also performs application-level value-added functions for the first application, such as content billing and report statistics. In addition, the first edge user plane network element receives the address information of the first edge application server from the session management network element so that the first edge user plane network element can forward the data of the first application to the first edge application server in the future.

[0272] Optionally, one or more of the following information sent by the session management network element to the first edge user plane network element—the forwarding rules, the identifier of the first application, the address information of the first edge application server, and the application domain name of the first application server—are carried in the fifth request message. The fifth request message is used to request the first edge user plane network element to establish a session. For example, the fifth request message can be an N4 session establishment request message. Optionally, the fifth request message is determined by the session management network element based on the first request message from the terminal device. That is, the session requested by the fifth request message to be established by the first edge user plane network element is the same session as the session requested by the terminal device through the first request message. For a detailed explanation of the first request message, please refer to the foregoing related explanations; further details will not be repeated here.

[0273] In addition to the above-mentioned method of sending forwarding rules from the session management network element to the first edge user plane network element, the first edge user plane network element can also determine forwarding rules based on other methods. For example, the forwarding rules can also be pre-configured in the first edge user plane network element, and there are no restrictions on this.

[0274] In implementation 2.2, step S402 includes: the session management network element sending a traffic splitting rule to the first edge user plane network element. The traffic splitting rule instructs the first edge user plane network element to forward data of the first application matching the traffic splitting rule to the first edge application server, and to forward large network data that does not match the traffic splitting rule to the large network user plane network element through a first tunnel between the large network user plane network element and the large network user plane network element. The traffic splitting rule can be, for example, an UL CL traffic splitting rule. The large network data is, for example, data transmitted between the terminal device and the Internet / central cloud application server.

[0275] Optionally, the method further includes: the session management network element switching the data offloading anchor point from the main network user plane network element to the first edge user plane network element. The data offloading anchor point is used to offload application data and main network data sent by the terminal device.

[0276] Understandably, when the terminal device requests to establish a large network session, the data offloading anchor point in the large network session is originally the large network user plane element. This means the large network user plane element forwards the large network data sent by the terminal device to the Internet / central cloud application server, and forwards the data of the first application sent by the terminal device to the first edge user plane element. This method requires the data transmitted between the terminal device and the first edge user plane element to be forwarded through the large network user plane element. However, when the session management element switches the data offloading anchor point from the large network user plane element to the first edge user plane element, the first edge user plane element forwards the large network data sent by the terminal device to the large network user plane element, so that the large network user plane element can forward the large network data to the Internet / central cloud application server. The first edge user plane element then forwards the data of the first application sent by the terminal device to the first edge application server. Therefore, the data of the first application can be transmitted from the terminal device to the first edge user plane element without passing through the large network user plane element, reducing the transmission latency of the first application data.

[0277] For example, the session management network element switches the data offloading anchor point from the main network user plane network element to the first edge user plane network element, including: the session management network element instructing the first edge user plane network element to establish a first tunnel between the main network user plane network element and the first network user plane network element, and instructing the access network device to update the peer of the second tunnel from the main network user plane network element to the first edge user plane network element. The second tunnel is a tunnel between the access network device and the user plane network element.

[0278] Optionally, the session management network element instructs the first edge user plane network element and the main network user plane network element to establish a first tunnel, including: the session management network element sending first instruction information to the first edge user plane network element, the first instruction information being used to instruct the first edge user plane network element to establish a first tunnel with the main network user plane network element; and the session management network element sending second instruction information to the main network user plane network element, the second instruction information being used to instruct the main network user plane network element to establish a first tunnel with the first edge user plane network element.

[0279] Optionally, the method further includes: the session management network element sending endpoint information of the first edge user plane network element to the main network user plane network element, and sending endpoint information of the main network user plane network element to the first edge user plane network element. The main network user plane network element establishes a first tunnel with the first edge user plane network element based on the endpoint information of the first edge user plane network element. The first edge user plane network element establishes a first tunnel with the main network user plane network element based on the endpoint information of the first edge user plane network element.

[0280] For example, after receiving the first indication information, the first edge user plane network element sends its endpoint information to the session management network element, so that the session management network element can obtain the endpoint information of the first edge user plane network element and then send the endpoint information of the first edge user plane network element to the main network user plane network element. And / or, after receiving the second indication information, the main network user plane network element sends its endpoint information to the session management network element, so that the session management network element can obtain the endpoint information of the main network user plane network element and then send the endpoint information of the main network user plane network element to the first edge user plane network element.

[0281] For example, if the session management network element sends the first indication information to the first edge user plane network element earlier than it sends the second indication information to the main network user plane network element, the session management network element may, after receiving the endpoint information of the first edge user plane network element, send the endpoint information of the first edge user plane network element and the second indication information in the same message to the main network user plane network element, or send the endpoint information of the first edge user plane network element in the second indication information to the main network user plane network element, without any restriction.

[0282] For example, if the session management network element sends the second indication information to the large user plane network element earlier than it sends the first indication information to the first edge user plane network element, the session management network element may, after receiving the endpoint information of the large user plane network element, send the endpoint information of the large user plane network element and the first indication information in the same message to the first edge user plane network element, or send the endpoint information of the large user plane network element in the first indication information to the first edge user plane network element, without any restriction.

[0283] Optionally, the session management network element instructs the access network device to update the peer of the second tunnel from the main network user plane element to the first edge user plane element. This includes: the session management network element sending third indication information to the first edge user plane element, the third indication information being used to instruct the first edge user plane element to establish a second tunnel with the access network device; and the session management network element sending fourth indication information to the access network device, the fourth indication information being used to instruct the access network device to update the peer of the second tunnel from the main network user plane element to the first edge user plane element.

[0284] Optionally, the method further includes: the session management network element sending endpoint information of the access network device to the first edge user plane network element, and sending endpoint information of the first edge user plane network element to the access network device. The first edge user plane network element establishes a second tunnel with the access network device based on the endpoint information of the access network device. The access network device updates the peer of the second tunnel from the main network user plane network element to the first edge user plane network element based on the endpoint information of the first edge user plane network element.

[0285] For example, the session management network element can send the endpoint information and third indication information of the access network device in the same message to the first edge user plane network element, or it can send the endpoint information of the access network device in the third indication information to the first edge user plane network element; there is no restriction on this. As another example, the session management network element can send the endpoint information and fourth indication information of the first edge user plane network element in the same message to the access network device, or it can send the endpoint information of the first edge user plane network element in the third indication information to the access network device; there is no restriction on this.

[0286] Understandably, compared to the method where the session management network element selects edge user plane network elements and instructs the selected edge user plane network elements to establish tunnels between them and the main network user plane network elements during the process of establishing a large network session with the access network equipment and the main network user plane network elements before the first application runs, in this embodiment, the terminal device sends a third request message to the application network element when it detects that the first application is running. The third request message is used to request access to the edge application server that processes the data of the first application for the terminal device. The application network element sends a second request message to the session management network element. The second request message is used to request the edge application server assigned to process the data of the first application for the terminal device. After receiving the second request message, the session management network element determines the first edge user plane network element and the first edge application server, and then instructs the first edge user plane network element to establish a first tunnel between it and the main network user plane network elements. This avoids the session management network element selecting edge user plane network elements and establishing tunnels between edge user plane network elements and main network user plane network elements in advance before the first application runs, reducing resource waste.

[0287] Understandably, compared to the approach where the session management element only selects an edge user plane network element and instructs the selected edge user plane network element to establish a tunnel with the main user plane network element when application data is detected by the main user plane network element, thus requiring the main user plane network element to cache application data, this embodiment of the application, after receiving the second request message, determines the first edge user plane network element and the first edge application server, then instructs the first edge user plane network element to establish a first tunnel with the main user plane network element, and sends the address information of the first edge application server to the terminal device. This ensures that the data transmission of the first application occurs after the first tunnel between the first edge user plane network element and the main user plane network element is established, avoiding packet loss caused by the main user plane network element caching application data for a long time, and improving the user experience.

[0288] S403. The session management network element sends the address information of the first edge application server, which is used to process data from the first application of the terminal device. Correspondingly, the terminal device obtains the address information of the first edge application server.

[0289] The possible implementations of step S403 are illustrated below by example, as described in optional embodiments 3.1 and 3.2. Embodiment 3.1 can be applied to the situation described in embodiment 1.1 or embodiment 2.1. Embodiment 3.2 can be applied to the situation described in embodiment 1.2 or embodiment 2.2.

[0290] In implementation 3.1, step S403 includes: the session management network element sending a first response message to the terminal device, the first response message including the address information of the first edge application server.

[0291] Optionally, the session management network element indirectly sends the first response message to the terminal device through the access and mobility management network element. For example, the session management network element sends a session first response message to the access and mobility management network element, which then sends the first response message to the terminal device.

[0292] Optionally, the first response message may further include at least one of the following: the application domain name of the first edge application server, or the identifier of the first application. The inclusion of the first application identifier in the first response message can be applied to scenarios where the session requested by the terminal device can be used to transmit data from multiple applications. In this scenario, the first response message including the address information of the first edge application server and the identifier of the first application helps the terminal device determine that the address information of the first edge application server corresponds to the first application, so that the terminal device can send the data of the first application to the first edge application server based on the address information of the first edge application server.

[0293] In implementation method 3.2, step S403 includes: the session management network element sending a second response message to the application network element, the second response message including the address information of the first edge application server; and the application network element sending a third response message to the terminal device, the third response message including the address information of the first edge application server.

[0294] Optionally, the second response message further includes at least one of the following: the identifier of the first application, or the identifier of the terminal device. Optionally, before sending the third response message to the terminal device, the method further includes: the application network element determining the terminal device based on the identifier of the first application or the identifier of the terminal device. Then, the application network element can send the third response message to the determined terminal device.

[0295] Optionally, the third response message may also include at least one of the following: the identifier of the first application, or the application domain name of the first edge application server. The application network element determines the application domain name of the first edge application server, for example, by receiving the application domain name of the first edge application server from the session management network element. For another example, if the edge application server has pre-reported information about its address and application domain name to the application network element, the application network element may determine the application domain name of the first edge application server based on the address information received from the session management network element.

[0296] S404. The terminal device sends the data of the first application to the first edge application server based on the address information of the first edge application server.

[0297] Understandably, the process of the terminal device sending data of the first application to the first edge application server includes: the terminal device sending the data of the first application to the first edge user plane network element, and the first edge user plane network element sending the data of the first application to the first edge application server. Specifically, the terminal device sending the data of the first application to the first edge user plane network element can, for example, be achieved by the access network device forwarding the data of the first application from the terminal device to the first edge user plane network element.

[0298] The possible implementations of step S404 are illustrated below by example, as described in optional implementation methods 4.1 and 4.2.

[0299] In implementation 4.1, the terminal device is a terminal OS. Step S404 includes: the terminal OS providing the application client with the address information of the first edge application server; the application client sending the data of the first application and the destination address of the data of the first application to the terminal OS, wherein the destination address of the data of the first application is the address information of the first edge application server; and the terminal OS sending a data packet to the first edge application server, wherein the data packet includes the data of the first application and the destination address of the data packet is the destination address of the data of the first application.

[0300] For example, after receiving the address information of the first edge application server, the terminal OS can provide an interface for the application client so that the application client can call the interface to obtain the address information of the first edge application server and use the address information of the first edge application server as the target address of the data of the first application, thereby sending the data of the first application and the target address to the terminal OS.

[0301] In implementation method 4.2, the terminal device is a terminal OS. Besides obtaining the address information of the first edge application server, the terminal OS also obtains the application domain name of the first edge application server. The method further includes: the terminal OS configuring the correspondence between the application domain name of the first edge application server and the address information of the first edge application server in the local domain name system. Step S404 includes: the application client sending data of the first application and the application domain name of the first edge application server to the terminal OS; the terminal OS determining the address information of the first edge application server corresponding to the application domain name of the first edge application server from the local domain name system; and the terminal OS sending a data packet to the first edge application server, the data packet including the data of the first application, and the destination address of the data packet being the address information of the first edge application server.

[0302] For example, after obtaining the address information and application domain name of the first edge application server, the terminal OS configures a host domain name address record in the local domain name system. This host domain name address record includes the application domain name and address information of the first edge application server. When the application client calls the underlying transport protocol stack to send data for the first application, it fills in the application domain name of the first edge application server. The terminal OS calls the local domain name system to query the address information corresponding to the application domain name of the first edge application server. For example, the terminal OS first queries the host domain name address record configured in the local domain name system and can find the address information of the first edge application server corresponding to the application domain name. Therefore, the terminal OS determines the address information of the first edge application server as the target address of the first application's data through the underlying transport protocol stack. The underlying transport protocol stack is, for example, the Hypertext Transfer Protocol (HTTP).

[0303] As can be seen, since the terminal OS configures the correspondence between the application domain name of the first edge application server and the address information of the first edge application server in the local DNS, the terminal OS can preferentially query the address information of the first edge application server corresponding to the application domain name of the first edge application server from the local domain name system, without having to initiate a query to the network domain name system, thereby reducing query latency and thus reducing the data transmission latency of the first application.

[0304] In one optional implementation, when the first edge user plane network element receives a forwarding rule from the session management network element, after receiving a data packet from the terminal device, the first edge user plane network element forwards the data of the first application in the data packet to the first edge application server based on the forwarding rule. Regarding the situation where "the first edge user plane network element receives a forwarding rule from the session management network element," please refer to the relevant description in the aforementioned implementation 2.1, which will not be repeated here.

[0305] This application does not limit the implementation method of the forwarding rule. An exemplary forwarding rule is provided below: After receiving data from the first application, the first edge user plane network element matches the source address of the first application data with the IP address of the terminal device, and matches the destination address of the first application data with the address information of the first edge application server. If the source address of the first application data matches the IP address of the terminal device, and the destination address of the first application data matches the address information of the first edge application server, the first edge user plane network element sends the first application data to the first edge application server based on the destination address of the first application data. If the source address of the first application data matches the IP address of the terminal device, but the destination address of the first application data does not match the address information of the first edge application server, the first edge user plane network element sends the first application data to the first edge application server according to the address information of the first edge application server sent by the session management network element. If the source address of the first application data does not match the IP address of the terminal device, and the destination address of the first application data does not match the address information of the first edge application server, the first edge user plane network element discards the first application data.

[0306] In another optional implementation, when the first edge user plane network element receives a traffic splitting rule from the session management network element, after receiving a data packet from the terminal device, the first edge user plane network element forwards the data of the first application in the data packet that matches the traffic splitting rule to the first edge application server. Optionally, if the first edge user plane network element also includes large network data in the data packet that does not match the traffic splitting rule, it forwards the large network data in the data packet that does not match the traffic splitting rule to the large network user plane network element through a first tunnel with the large network user plane network element. Regarding the situation where "the first edge user plane network element receives a traffic splitting rule from the session management network element," please refer to the relevant description in the aforementioned implementation 2.2, which will not be repeated here.

[0307] In an optional implementation, the method further includes: a first edge application server processing data from a first application and sending the processing result to a first edge user plane network element. The first edge user plane network element then sends the processing result to a terminal device. For example, the EAS processes the application data, including: the EAS analyzing and calculating the application data. For instance, if the application data is video data, the EAS can analyze and calculate the video data to determine scenes, objects, and the number of objects in the video data, and send the determined scenes, objects, and the number of objects as processing results to the terminal device.

[0308] Optionally, the first edge user plane network element sends the processing result to the terminal device, including: the first edge user plane network element sends the processing result to the access network device, and the access network device forwards the processing result to the terminal device.

[0309] In summary, in the communication method provided in this application embodiment, the session management network element determines a first edge user plane network element and a first edge application server, which belong to the same edge computing node. The session management network element configures the first edge user plane network element for the transmission of data from the terminal device to the first edge application server for the first application. The session management network element sends the address information of the first edge application server, which is used to process the data from the first application on the terminal device.

[0310] As can be seen, in this method, the session management network element selects an edge user plane network element and an edge application server for the terminal device. The selected edge user plane network element used to transmit the data of the first application belongs to the same edge computing power node as the edge application server used to process the data of the first application. This enables the edge user plane network element to transmit the data of the first application to the edge application server within the same edge computing power node, without having to transmit the data of the first application across edge computing power nodes. This reduces the transmission latency of application data, reduces bandwidth costs, and improves the efficiency of terminal computing power offloading.

[0311] Furthermore, in this method, since the session management network element can obtain more precise location information for the terminal device than that at the prefecture-level city level, it can select edge user plane network elements and edge application servers based on the more precise location of the terminal device. If the terminal device moves across prefecture-level cities during application operation, the session management network element can reselect suitable edge user plane network elements and edge application servers for the terminal device based on its precise location, avoiding the increased transmission latency caused by the application data needing to detour back to the original prefecture-level city for transmission.

[0312] Furthermore, in this method, the session management network element selects the edge user plane network element and the edge application server for the terminal device. Compared to the aforementioned methods 1, 2, and 3, the method provided in this application embodiment does not require a DNS server to select the edge application server. Therefore, it eliminates the need for manual configuration of APP domain name address records for the DNS server, reducing operational complexity. Moreover, compared to the aforementioned method 3, the method provided in this application embodiment eliminates the need for manual configuration of multiple DNN functions for SMF network elements, large-scale UPF network elements, and edge UPF network elements. It also eliminates the need for manual configuration of the ID of the edge UPF network element located in the same edge computing node as the EAS IP address range for the SMF network element to select the edge UPF network element, further reducing operational complexity.

[0313] Based on the communication method shown in Figure 8, the following exemplary communication methods are provided in Examples 1 and 2.

[0314] Example 1: Referring to Figure 12, the communication method described in Example 1 is illustrated. The method includes the following steps:

[0315] S501. The application network element sends URSP rules to the policy control network element. The URSP rules include the application identifier and the slice identifier. Correspondingly, the policy control network element receives the URSP rules.

[0316] S502, the policy control network element sends URSP rules to the terminal device through the access and mobility management network element. Correspondingly, the terminal device receives the URSP rules.

[0317] Optionally, the policy control network element also sends the session's policy and charging control (PCC) rules to the session management network element.

[0318] S503. Each edge user plane network element in one or more edge user plane network elements sends its own information, and each edge application server in one or more edge application servers sends its own information. Correspondingly, the session management network element receives information from one or more edge user plane network elements and information from one or more edge application servers.

[0319] The information of the edge user plane network element includes at least one of the following: the identifier of the edge user plane network element, the identifier of the edge computing node to which the edge user plane network element belongs, the load of the edge user plane network element, and the latency of the edge user plane network element.

[0320] The information of the edge application server includes at least one of the following: the identifier of the application supported by the edge application server, the identifier of the edge computing node to which the edge application server belongs, the load of the edge application server, the application domain name of the edge application server, and the address information of the edge application server.

[0321] S504. When the terminal device detects that the first application is running, it determines the URSP rule that matches the first application based on the identifier of the first application. The URSP rule that matches the first application includes the identifier of the first application and the identifier of the first slice.

[0322] S505, the terminal device sends a first request message to the access and mobility management network element. The first request message is used to request the establishment of a session. The session is used for the transmission of data of a first application from the terminal device to a first edge application server. The first request message includes an identifier of the first application. Correspondingly, the access and mobility management network element receives the first request message from the terminal device.

[0323] For example, the first request message sent by the terminal device to the access and mobility management network element is carried in the PDU session establishment request message.

[0324] S506, the access and mobility management network element sends a first request message to the session management network element. Correspondingly, the session management network element receives the first request message from the access and mobility management network element.

[0325] For example, the first request message sent by the access and mobility management network element to the session management network element is carried in the PDU session establishment SM context request (Nsmf_PDUsession_createSMcontext request) message.

[0326] S507, the session management network element, the unified data management network element, and the policy control network element perform the session slice authentication and policy control process.

[0327] S508, the session management network element determines the first edge user plane network element and the first edge application server based on the location of the terminal device, the identifier of the first application, the information of one or more edge user plane network elements, and the information of one or more edge application servers. The first edge user plane network element and the first edge application server belong to the same edge computing node.

[0328] S509. The session management network element sends a fourth request message to the first edge user plane network element. The fourth request message requests the first edge user plane network element to establish a session. The fourth request message includes at least one of the following: the identifier of the first application, the application domain name of the first edge application server, the address information of the first edge application server, or a forwarding rule. The forwarding rule instructs the first edge user plane network element to forward the data of the first application to the first edge application server. Correspondingly, the first edge user plane network element receives the fourth request message from the session management network element.

[0329] For example, the fourth request message is the N4 session establishment request message.

[0330] S510, the first edge user plane network element sends a fourth response message to the session management network element. Correspondingly, the session management network element receives the fourth response message from the first edge user plane network element. This allows the session management network element to determine, based on the fourth response message, that the first edge user plane network element has received the fourth request message.

[0331] For example, the fourth response message is the N4 session establishment response message.

[0332] S511, the session management network element sends a first response message to the access and mobility management network element, the first response message including the address information of the first edge application server. Correspondingly, the access and mobility management network element receives the first response message from the session management network element. Optionally, the first response message also includes the identifier of the first application and / or the application domain name of the first edge application server.

[0333] For example, the first response message sent by the session management network element to the access and mobility management network element can be a communication_N1N2 message transfer request message. The PDU session establishment accept field in the communication_N1N2 message transfer request message carries the identifier of the first application, the application domain name of the first edge application server, and the address information of the first edge application server.

[0334] S512, the access and mobility management network element sends a first response message to the access network device. Correspondingly, the access network device receives the first response message from the access and mobility management network element.

[0335] For example, the first response message sent by the access and mobility management network element to the access network device can be an N2 PDU session request message. The PDU session assignment accept field in the N2 PDU session request message carries the identifier of the first application, the application domain name of the first edge application server, and the address information of the first edge application server.

[0336] S513. The access network device sends a first response message to the terminal device. Correspondingly, the terminal device receives the first response message from the access network device.

[0337] For example, the first response message sent by the access network device to the terminal device may be an access network-specific resource setup (AN) message, in which the PDU session assignment accept field carries the identifier of the first application, the application domain name of the first edge application server, and the address information of the first edge application server.

[0338] S514. The access network device sends a session response message to the access and mobility management network element. The session response message includes the address information of the first edge application server. Correspondingly, the access and mobility management network element receives the session response message from the access network device. Optionally, the session response message also includes the identifier of the first application and / or the application domain name of the first edge application server.

[0339] For example, the session response message sent by the access network device to the access and mobility management network element can be an N2 PDU session response message. The PDU session establishment accept field in the N2 PDU session response message carries the identifier of the first application, the application domain name of the first edge application server, and the address information of the first edge application server.

[0340] After receiving the session response message, the S515 access and mobility management network element, together with the session management network element, unified data management network element, and policy control network element, performs the session establishment and session update process.

[0341] S516. The terminal device sends a data packet to the access network device. The data packet includes data from the first application, the source address of the data packet is the IP address of the terminal device, and the destination address of the data packet is the address information of the first edge application server. Correspondingly, the access network device receives the data packet.

[0342] S517. The access network device sends data packets to the first edge user plane network element. Correspondingly, the first edge user plane network element receives the data packets.

[0343] S518. The first edge user plane network element matches the source address and destination address of the data packet with the forwarding rules. If the match is successful, proceed to step S519.

[0344] S519, the first edge user plane network element sends a data packet to the first edge application server. Correspondingly, the first edge application server receives the data packet.

[0345] In addition, after the first edge user plane network element processes the data of the first application, it can also send the processing result to the first edge user plane network element, which then sends the processing result to the access network device, and the access network device sends the processing result to the terminal device.

[0346] For a detailed explanation of each step in Example 1, please refer to the relevant explanation in the communication method described in Figure 8 above, which will not be repeated here.

[0347] Example 2: Referring to Figure 13, the communication method described in Example 1 is illustrated. The method includes the following steps:

[0348] S601. Each edge user plane network element in one or more edge user plane network elements sends its own information, and each edge application server in one or more edge application servers sends its own information. Correspondingly, the session management network element receives information from one or more edge user plane network elements and information from one or more edge application servers.

[0349] The information of the edge user plane network element includes at least one of the following: the identifier of the edge user plane network element, the identifier of the edge computing node to which the edge user plane network element belongs, the load of the edge user plane network element, and the latency of the edge user plane network element.

[0350] The information of the edge application server includes at least one of the following: the identifier of the application supported by the edge application server, the identifier of the edge computing node to which the edge application server belongs, the load of the edge application server, the application domain name of the edge application server, and the address information of the edge application server.

[0351] S602. The terminal device sends a fourth request message to the session management network element through the access and mobility management network element. The fourth request message is used to request the establishment of a large network session. Correspondingly, the session management network element receives the fourth request message.

[0352] S603, session management network element, large network user plane network element, and access network equipment cooperate to establish a large network session.

[0353] S604. When the terminal device detects that the first application has started, it sends a third request message to the application network element. The third request message is used to request access to the edge application server that processes the data of the first application for the terminal device. The third request message includes the identifier of the first application. Correspondingly, the application network element receives the third request message from the terminal device.

[0354] S605. The application network element sends a second request message to the session management network element through the network open network element. The second request message is used to request an edge application server to process data for the first application for the terminal device. The second request message includes the identifier of the first application. Correspondingly, the session management network element receives the second request message.

[0355] S606. The session management network element determines the first edge user plane network element and the first edge application server based on the location of the terminal device, the identifier of the first application, the information of one or more edge user plane network elements, and the information of one or more edge application servers. The first edge user plane network element and the first edge application server belong to the same edge computing node.

[0356] S607. The session management network element instructs the first edge user plane network element and the main network user plane network element to establish a first tunnel, and instructs the access network device to update the peer of the second tunnel from the main network user plane network element to the first edge user plane network element. The session management network element also sends traffic splitting rules to the first edge user plane network element.

[0357] The traffic splitting rule is used to instruct the first edge user plane network element to forward the data of the first application that matches the traffic splitting rule to the first edge application server, and to forward the large network data that does not match the traffic splitting rule to the large network user plane network element through the first tunnel between the large network user plane network element and the large network user plane network element.

[0358] S608, the session management network element sends a second response message to the application network element through the network open network element. The second response message includes the address information of the first edge application server. Correspondingly, the application network element receives the second response message.

[0359] Optionally, the second response message may also include at least one of the following: the identifier of the first application, or the identifier of the terminal device.

[0360] S609, the application network element sends a third response message to the terminal device, the third response message including the address information of the first edge application server. Correspondingly, the terminal OS receives the third response message.

[0361] S610, the terminal device sends a data packet to the access network device. The data packet includes data from the first application, the source address of the data packet is the IP address of the terminal device, and the destination address of the data packet is the address information of the first edge application server. Correspondingly, the access network device receives the data packet.

[0362] S611. The access network device sends data packets to the first edge user plane network element. Correspondingly, the first edge user plane network element receives the data packets.

[0363] S612, the first edge user plane network element sends the large network data in the data packet that does not match the traffic splitting rules to the large network user plane network element. Correspondingly, the large network user plane network element receives the large network data.

[0364] S613, the first edge user plane network element sends the data of the first application that matches the traffic splitting rule in the data packet to the first edge application server. Correspondingly, the first edge application server receives the data of the first application.

[0365] In addition, after the first edge user plane network element processes the data of the first application, it can also send the processing result to the first edge user plane network element, which then sends the processing result to the access network device, and the access network device sends the processing result to the terminal device.

[0366] For a detailed explanation of each step in Example 2, please refer to the relevant explanation in the communication method described in Figure 8 above, which will not be repeated here.

[0367] To achieve the functions of the methods provided in the embodiments of this application, the network element / device may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0368] As shown in Figure 14, this application embodiment provides a communication device 1400. The communication device 1400 can be a first network element, or a component of the first network element (e.g., an integrated circuit, a chip, a processor, a chip system, etc.). Alternatively, the communication device 1400 can be a terminal device, or a component of a terminal device (e.g., an integrated circuit, a chip, a processor, a chip system, etc.). Alternatively, the communication device 1400 can be an application network element, or a component of an application network element (e.g., an integrated circuit, a chip, etc.). The communication device 1400 can also be other communication units used to implement the methods in the method embodiments of this application. The communication device 1400 may include a processing unit 1401. Optionally, the communication device 1400 may further include a communication unit 1402, where the processing unit 1401 controls the communication unit 1402 to perform data / signaling transmission and reception. The communication unit 1402 may also be called a transceiver unit. Optionally, the communication unit 1402 may include a sending unit and a receiving unit, where the sending unit can be used to send data / signaling, and the receiving unit can be used to receive data / signaling. Optionally, the communication device 1400 may also include a storage unit 1403, which can be used to store information and / or data and / or instructions, etc. The storage unit 1403 can interact with the processing unit 1401 or the communication unit 1402.

[0369] In one possible design, regarding the case where the communication device 1400 is used to implement the function of the first network element in the above method embodiment:

[0370] The processing unit 1401 is used to determine the first edge user plane network element and the first edge application server, wherein the first edge user plane network element and the first edge application server belong to the same edge computing node.

[0371] The processing unit 1401 is also configured to configure the first edge user plane network element for the transmission of data from the terminal device to the first edge application server for the first application.

[0372] The communication unit 1402 is used to send the address information of the first edge application server, which is used to process data from the first application of the terminal device.

[0373] In one optional implementation, the processing unit 1401 determines the first edge user plane network element and the first edge application server, specifically configured to: determine the edge user plane network element whose service range includes the location of the terminal device as the first edge user plane network element; and determine the edge application server that supports processing the data of the first application among the edge application servers belonging to the same edge computing node as the first edge user plane network element as the first edge application server.

[0374] In one optional implementation, the first edge user plane network element and the first edge application server further satisfy at least one of the following conditions:

[0375] The load of the first edge user plane network element is less than or equal to the first threshold;

[0376] The load on the first edge application server is less than or equal to the second threshold;

[0377] The load of the first edge user plane network element is the smallest among the loads of multiple edge user plane network elements, and the service range of multiple edge user plane network elements includes the location of the terminal device.

[0378] The load on the first edge application server is the lowest among the loads on multiple edge application servers, which support the processing of data from the first application.

[0379] The latency of the first edge user plane network element is the lowest among the latency of multiple edge user plane network elements, and the service range of multiple edge user plane network elements includes the location of the terminal device.

[0380] In one optional embodiment, the communication unit 1402 is further configured to receive a first request message from a terminal device, the first request message being used to request the establishment of a session, the session being used for the transmission of data of the first application from the terminal device to the first edge application server.

[0381] The communication unit 1402 sends the address information of the first edge application server, specifically for sending a first response message to the terminal device, the first response message including the address information of the first edge application server.

[0382] In one optional implementation, the first request message includes an identifier of the first application; and / or, the first response message further includes at least one of the following: the application domain name of the first edge application server, or the identifier of the first application.

[0383] In one optional embodiment, the communication unit 1402 is further configured to receive a second request message from an application network element, the second request message being used to request an edge application server to allocate data for processing the first application for the terminal device.

[0384] The communication unit 1402 sends the address information of the first edge application server, specifically for sending a second response message to the application network element, the second response message including the address information of the first edge application server.

[0385] In one optional implementation, the second request message includes an identifier of the first application; and / or, the second response message further includes at least one of the following: an identifier of the first application, or an identifier of the terminal device.

[0386] In one optional implementation, the processing unit 1401 configures the first edge user plane network element for the transmission of data of the first application from the terminal device to the first edge application server. Specifically, it is configured to send forwarding rules to the first edge user plane network element through the communication unit 1402. The forwarding rules are used to instruct the first edge user plane network element to forward the data of the first application from the terminal device to the first edge application server.

[0387] In another possible design, regarding the case where the communication device 1400 is used to implement the functions of the terminal device in the above method embodiments:

[0388] The communication unit 1402 is used to obtain the address information of the first edge application server. The first edge application server is used to process the data of the first application from the communication device 1400. The first edge application server and the first edge user plane network element belong to the same edge computing node. The first edge user plane network element is used for the transmission of the data of the first application from the communication device 1400 to the first edge application server.

[0389] The communication unit 1402 is also used to send the data 14 of the first application to the first edge application server based on the address information of the first edge application server.

[0390] In one optional implementation, the communication unit 1402 is further configured to send a first request message to the first network element. The first request message is used to request the establishment of a session, and the session is used for the transmission of data of the first application from the communication device 1400 to the first edge application server.

[0391] The communication unit 1402 obtains the address information of the first edge application server, specifically for: receiving a first response message from the first network element, the first response message including the address information of the first edge application server.

[0392] In one alternative implementation, the first request message includes an identifier of the first application.

[0393] In an optional embodiment, the communication unit 1402 is further configured to send a third request message to the application network element, the third request message being used to request access to an edge application server that processes data for the first application for the communication device 1400. The communication unit 1402 is also configured to receive a third response message from the application network element, the third response message including the address information of the first edge application server.

[0394] In one alternative implementation, the third request message includes an identifier of the first application.

[0395] In one optional implementation, the communication unit 1402 obtains the address information of the first edge application server, specifically for: obtaining the address information of the first edge application server and the application domain name of the first edge application server.

[0396] The processing unit 1401 is used to configure the correspondence between the application domain name of the first edge application server and the address information of the first edge application server in the local domain name system of the communication device 1400.

[0397] The communication unit 1402 sends data of the first application to the first edge application server based on the address information of the first edge application server. Specifically, it is used to: receive data of the first application from the application client and the application domain name of the first edge application server; determine the address information of the first edge application server corresponding to the application domain name of the first edge application server from the local domain name system; and send a data packet to the first edge application server, the data packet including the data of the first application, and the destination address of the data packet being the address information of the first edge application server.

[0398] In one optional implementation, the communication unit 1402 sends data of the first application to the first edge application server based on the address information of the first edge application server. Specifically, it is used to: provide the address information of the first edge application server to the application client; receive the data of the first application from the application client and the destination address of the data of the first application, wherein the destination address of the data of the first application is the address information of the first edge application server; and send a data packet to the first edge application server, wherein the data packet includes the data of the first application and the destination address of the data packet is the destination address of the data of the first application.

[0399] In another possible design, regarding the case where the communication device 1400 is used to implement the functions of the network element in the above method embodiments:

[0400] The communication unit 1402 is used to receive a third request message from the terminal device, the third request message being used to request access to the edge application server that processes data for the first application for the terminal device.

[0401] The communication unit 1402 is also used to send a second request message to the first network element. The second request message is used to request an edge application server to allocate data for the terminal device to process the first application.

[0402] The communication unit 1402 is also used to receive a second response message from the first network element. The second response message includes the address information of the first edge application server. The first edge application server and the first edge user plane network element belong to the same edge computing node. The first edge user plane network element is used for the transmission of data of the first application from the terminal device to the first edge application server.

[0403] The communication unit 1402 is also used to send a third response message to the terminal device. The third response message includes the address information of the first edge application server, which is used to process data from the first application of the terminal device.

[0404] In one optional implementation, the third request message includes an identifier of the first application; and / or, the second request message includes an identifier of the first application.

[0405] In one alternative implementation, the second request message may also include an identifier of the terminal device.

[0406] In one optional implementation, the second response message further includes at least one of the following: the identifier of the first application, or the identifier of the terminal device.

[0407] In one optional implementation, the processing unit 1401 is configured to determine the terminal device based on the identifier of the first application or the identifier of the terminal device.

[0408] The embodiments of this application and the method embodiments shown above are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the embodiments shown above, which will not be repeated here.

[0409] This application also provides a communication device 1500, as shown in FIG15. The communication device 1500 can be a first network element, or a chip, chip system, or processor that supports the first network element in implementing the above-described methods. Alternatively, the communication device 1500 can be a terminal device, or a chip, chip system, or processor that supports the terminal device in implementing the above-described methods. Alternatively, the communication device 1500 can be an AF device, or a chip, chip system, or processor that supports the AF device in implementing the above-described methods. This device can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0410] The communication device 1500 may include one or more processors 1501. The processor 1501 can be used to implement some or all of the functions of the terminal-side device or network-side device through logic circuits or by running computer programs. The processor 1501 may be a general-purpose processor or a special-purpose processor, etc. For example, it may be a baseband processor, digital signal processor, application-specific integrated circuit, field-programmable gate array or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, and the CPU can be used to control the communication device, execute software programs, and process data from the software programs. The communication device may be, for example, a base station, a baseband chip, a terminal, a terminal chip, a distributed unit (DU), or a central unit (CU), etc.

[0411] Optionally, the communication device 1500 may include one or more memories 1502, which may store instructions 1504 that can be executed on the processor 1501, causing the communication device 1500 to perform the methods described in the above method embodiments. Optionally, the memory 1502 may also store data. The processor 1501 and the memory 1502 may be provided separately or integrated together.

[0412] The memory 1502 may include, but is not limited to, non-volatile memory such as hard disk drive (HDD) or solid-state drive (SSD), random access memory (RAM), erasable programmable read-only memory (EPROM), ROM or compact disc read-only memory (CD-ROM), etc.

[0413] Optionally, the communication device 1500 may further include a transceiver 1505 and an antenna 1506. The transceiver 1505 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 1505 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0414] In one possible design, regarding the case where the communication device 1500 is used to implement the function of the first network element in the above method embodiment:

[0415] Processor 1501 is used to determine the first edge user plane network element and the first edge application server, which belong to the same edge computing node.

[0416] The processor 1501 is also configured to configure the first edge user plane network element for the transmission of data from the terminal device to the first edge application server for the first application.

[0417] Transceiver 1505 is used to send the address information of the first edge application server, which is used to process data from the first application of the terminal device.

[0418] In another possible design, regarding the case where the communication device 1500 is used to implement the functions of the terminal device in the above method embodiments:

[0419] Transceiver 1505 is used to obtain the address information of the first edge application server. The first edge application server is used to process the data of the first application from the communication device 1500. The first edge application server and the first edge user plane network element belong to the same edge computing node. The first edge user plane network element is used for the transmission of data of the first application from the communication device 1500 to the first edge application server.

[0420] The transceiver 1505 is also used to send data 15 of the first application to the first edge application server based on the address information of the first edge application server.

[0421] In another possible design, regarding the communication device 1500 used to implement the functions of the network elements in the above method embodiments:

[0422] Transceiver 1505 is used to receive a third request message from a terminal device, the third request message being used to request access to an edge application server that processes data for a first application on the terminal device.

[0423] The transceiver 1505 is also used to send a second request message to the first network element, the second request message being used to request an edge application server to be allocated to process data for the first application of the terminal device.

[0424] The transceiver 1505 is also used to receive a second response message from the first network element. The second response message includes the address information of the first edge application server. The first edge application server and the first edge user plane network element belong to the same edge computing node. The first edge user plane network element is used for the transmission of data of the first application from the terminal device to the first edge application server.

[0425] The transceiver 1505 is also used to send a third response message to the terminal device. The third response message includes the address information of the first edge application server, which is used to process data from the first application of the terminal device.

[0426] In another possible design, the processor 1501 may include a transceiver for implementing receive and transmit functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receive and transmit functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0427] In another possible design, the processor 1501 may optionally store instructions 1503, which, when executed on the processor 1501, cause the communication device 1500 to perform the methods described in the above method embodiments. Instructions 1503 may be embedded in the processor 1501; in this case, the processor 1501 may be implemented in hardware.

[0428] In another possible design, the communication device 1500 may include circuitry that can perform the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this application embodiment can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), p-type metal oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0429] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented through hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can use various methods to implement the described functionality for a specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this application.

[0430] The embodiments of this application and the above-described method embodiments are based on the same concept and have the same technical effects. For the specific principles, please refer to the description in the above-described method embodiments, which will not be repeated here.

[0431] This application also provides a computer-readable storage medium for storing computer software instructions that, when executed by a communication device, implement the functions of any of the above method embodiments.

[0432] This application also provides a computer program product for storing computer software instructions, which, when executed by a communication device, implement the functions of any of the above method embodiments.

[0433] This application also provides a communication system, which includes a first network element and a first edge user plane network element. The first network element is used to perform the operations of the first network element in the above method embodiments. The first edge user plane network element is used to: receive configuration information from the first network element, and send data from a first application of a terminal device to a first edge application server according to the configuration information. The first edge user plane network element can also be used to perform the operations of the first edge user plane network element in the above method embodiments.

[0434] Optionally, the system further includes a first edge application server. The first edge application server is configured to: receive data from a first application from a first edge user plane network element, and process the data of the first application. Optionally, the first edge application server is further configured to: send the result of processing the data of the first application to the terminal device through the first edge user plane network element. The first edge application server can also be used to perform the operations of the first edge application server in the above method embodiments.

[0435] Optionally, the system further includes an application network element. The application network element is used to: send a second request message to the first network element, the second request message being used to request an edge application server allocated for processing data for the first application on the terminal device. The application network element can also be used to perform the operations of the application network element in the above method embodiments.

[0436] Optionally, the system also includes a terminal device, which can be used to perform the operations of the terminal device in the above method embodiments.

[0437] This application also provides a computer program that, when run on a computer, implements the functions of any of the above method embodiments.

[0438] This application also provides a chip including a processor. The processor is used to execute code or instructions to implement the functions of any of the method embodiments described above. Optionally, the chip further includes an interface, and the processor is coupled to the interface, which is used to receive or output signals.

[0439] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., SSDs), etc.

[0440] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0441] Furthermore, unless otherwise specified or logically conflicting, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0442] It is understood that some optional features in the various embodiments of this application may not depend on other features in certain scenarios, or may be combined with other features in certain scenarios, without limitation.

[0443] It is understood that the solutions in the embodiments of this application can be used in combination, and the explanations or descriptions of various terms, similar operations or steps appearing in the embodiments can be referenced or explained to each other in the various embodiments, and this application does not limit them.

[0444] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b, and c. Here, a, b, and c can each be single or multiple.

[0445] In this application, the terms "first," "second," and various numerical designations are used for ease of description and are not intended to limit the scope of the embodiments of this application. For example, they may be used to distinguish different messages, rather than to describe a specific order or sequence. It should be understood that such descriptions can be interchanged where appropriate to describe solutions other than those described in this application.

[0446] In this application, the terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion, such that a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such process, method, product, or apparatus.

[0447] In this application, "for indicating" can include both direct and indirect indication. When describing an indication message as indicating A, it can include whether the indication message directly indicates A or indirectly indicates A, but does not necessarily mean that the indication message carries A.

[0448] In this application, "sending information to XX (device / network element)" can be understood as the destination of the information being that device / network element. This can include sending information directly or indirectly to that device / network element. "Receiving information from XX (device / network element), or receiving information from XX (device / network element)" can be understood as the source of the information being that device / network element. This can include receiving information directly or indirectly from that device / network element. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source.

[0449] In this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

Claims

1. A communication method, characterized in that, Applied to the first network element, the method includes: Identify the first edge user plane network element and the first edge application server, wherein the first edge user plane network element and the first edge application server belong to the same edge computing node; Configure the first edge user plane network element for the transmission of data from the terminal device to the first edge application server for the first application; The address information of the first edge application server is sent, and the first edge application server is used to process the data from the first application of the terminal device.

2. The method according to claim 1, characterized in that, The determination of the first edge user plane network element and the first edge application server includes: The edge user plane network element whose service range includes the location of the terminal device is defined as the first edge user plane network element. Among the edge application servers that belong to the same edge computing node as the first edge user plane network element, the edge application server that supports processing the data of the first application is identified as the first edge application server.

3. The method according to claim 1 or 2, characterized in that, The first edge user plane network element and the first edge application server also satisfy at least one of the following conditions: The load of the first edge user plane network element is less than or equal to the first threshold; The load on the first edge application server is less than or equal to the second threshold; The load of the first edge user plane network element is the smallest among the loads of the multiple edge user plane network elements, and the service range of the multiple edge user plane network elements includes the location of the terminal device; The first edge application server has the lowest load among the multiple edge application servers, which support the processing of data from the first application. The latency of the first edge user plane network element is the lowest among the latency of multiple edge user plane network elements, and the service range of the multiple edge user plane network elements includes the location of the terminal device.

4. The method according to any one of claims 1-3, characterized in that, Before determining the first edge user plane network element and the first edge application server, the method further includes: Receive a first request message from the terminal device, the first request message being used to request the establishment of a session, the session being used for the transmission of data of the first application from the terminal device to the first edge application server; The step of sending the address information of the first edge application server includes: A first response message is sent to the terminal device, the first response message including the address information of the first edge application server.

5. The method according to claim 4, characterized in that, The first request message includes the identifier of the first application; and / or, The first response message also includes at least one of the following: the application domain name of the first edge application server, or the identifier of the first application.

6. The method according to any one of claims 1-3, characterized in that, Before determining the first edge user plane network element and the first edge application server, the method further includes: Receive a second request message from the application network element, the second request message being used to request an edge application server to be allocated for processing the data of the first application for the terminal device; The step of sending the address information of the first edge application server includes: A second response message is sent to the application network element, the second response message including the address information of the first edge application server.

7. The method according to claim 6, characterized in that, The second request message includes the identifier of the first application; and / or, The second response message also includes at least one of the following: the identifier of the first application, or the identifier of the terminal device.

8. The method according to any one of claims 1-7, characterized in that, The transmission of data from the terminal device to the first edge application server configured for the first application in the first edge user plane network element includes: A forwarding rule is sent to the first edge user plane network element, the forwarding rule being used to instruct the first edge user plane network element to forward the data from the first application of the terminal device to the first edge application server.

9. A communication method, characterized in that, Applied to a terminal device, the method includes: Obtain the address information of the first edge application server. The first edge application server is used to process data from the first application of the terminal device. The first edge application server and the first edge user plane network element belong to the same edge computing node. The first edge user plane network element is used for the transmission of data of the first application from the terminal device to the first edge application server. Based on the address information of the first edge application server, the data of the first application is sent to the first edge application server.

10. The method according to claim 9, characterized in that, The method further includes: Send a first request message to the first network element. The first request message is used to request the establishment of a session. The session is used for the transmission of data of the first application from the terminal device to the first edge application server. The step of obtaining the address information of the first edge application server includes: receiving a first response message from the first network element, wherein the first response message includes the address information of the first edge application server.

11. The method according to claim 10, characterized in that, The first request message includes the identifier of the first application.

12. The method according to claim 9, characterized in that, The method further includes: Send a third request message to the application network element, the third request message being used to request access to the edge application server that processes the data of the first application for the terminal device; Receive a third response message from the application network element, the third response message including the address information of the first edge application server.

13. The method according to claim 12, characterized in that, The third request message includes the identifier of the first application.

14. The method according to any one of claims 9-13, characterized in that, The step of obtaining the address information of the first edge application server includes: obtaining the address information of the first edge application server and the application domain name of the first edge application server; The method further includes: configuring the correspondence between the application domain name of the first edge application server and the address information of the first edge application server in the local domain name system of the terminal device; The step of sending the data of the first application to the first edge application server based on the address information of the first edge application server includes: Receive data from the first application from the application client and the application domain name from the first edge application server; Determine the address information of the first edge application server corresponding to the application domain name of the first edge application server from the local domain name system; A data packet is sent to the first edge application server. The data packet includes data from the first application, and the destination address of the data packet is the address information of the first edge application server.

15. The method according to any one of claims 9-13, characterized in that, The step of sending the data of the first application to the first edge application server based on the address information of the first edge application server includes: Provide the application client with the address information of the first edge application server; Receive data from the application client of the first application and the target address of the data of the first application, wherein the target address of the data of the first application is the address information of the first edge application server; A data packet is sent to the first edge application server. The data packet includes data from the first application, and the destination address of the data packet is the destination address of the data from the first application.

16. A communication method, characterized in that, Applied to application network elements, the method includes: Receive a third request message from a terminal device, the third request message being used to request access to an edge application server that processes data for the first application on the terminal device; Send a second request message to the first network element, the second request message being used to request an edge application server to be allocated for processing the data of the first application for the terminal device; Receive a second response message from the first network element. The second response message includes the address information of the first edge application server. The first edge application server and the first edge user plane network element belong to the same edge computing node. The first edge user plane network element is used for the transmission of data of the first application from the terminal device to the first edge application server. A third response message is sent to the terminal device. The third response message includes the address information of the first edge application server, which is used to process data from the first application on the terminal device.

17. The method according to claim 16, characterized in that, The third request message includes the identifier of the first application; and / or, The second request message includes the identifier of the first application.

18. The method according to claim 16 or 17, characterized in that, The second request message also includes the identifier of the terminal device.

19. The method according to any one of claims 16 to 18, characterized in that, The second response message also includes at least one of the following: the identifier of the first application, or the identifier of the terminal device.

20. The method according to claim 19, characterized in that, Before sending the third response message to the terminal device, the method further includes: The terminal device is determined based on the identifier of the first application or the identifier of the terminal device.

21. A communication system, the system comprising a first network element and a first edge user plane network element; The first network element is used to perform the method described in any one of claims 1 to 8; The first edge user plane network element is used to: receive configuration information from the first network element, and send data from the first application of the terminal device to the first edge application server according to the configuration information.

22. The system according to claim 21, characterized in that, The system also includes the first edge application server; The first edge application server is configured to: receive data from the first application from the first edge user plane network element, and process the data of the first application.

23. The system according to claim 22, characterized in that, The first edge application server is also used to: send the result of processing the data of the first application to the terminal device through the first edge user plane network element.

24. The system according to any one of claims 21 to 23, characterized in that, The system also includes application network elements; The application network element is used to perform the method described in any one of claims 16 to 20.

25. The system according to any one of claims 21 to 24, characterized in that, The system also includes the terminal device; The terminal device is used to instruct the execution of the method according to any one of claims 9 to 15.

26. A communication device, characterized in that, The apparatus includes modules or units for implementing the method of any one of claims 1 to 8, or modules or units for implementing the method of any one of claims 9 to 15, or modules or units for implementing the method of any one of claims 16 to 20.

27. A communication device, characterized in that, Including memory and processor; The memory is used to store instructions or computer programs; The processor is configured to execute a computer program or instructions stored in the memory to cause the communication device to perform the method according to any one of claims 1 to 8, or to cause the communication device to perform the method according to any one of claims 9 to 15, or to cause the communication device to perform the method according to any one of claims 16 to 20.

28. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed, implements the method as described in any one of claims 1 to 8, or implements the method as described in any one of claims 9 to 15, or implements the method as described in any one of claims 16 to 20.

29. A computer program product, the computer program product comprising: Computer program code, when the computer program code is run, implements the method as described in any one of claims 1 to 8, or implements the method as described in any one of claims 9 to 15, or implements the method as described in any one of claims 16 to 20.

Citation Information

Patent Citations

  • Data processing method, network element equipment and readable storage medium

    CN113596191A

  • Method, device and system for acquiring IP address of EAS

    CN113973099A

  • Apparatus and method for providing information of application server in mobile communication system

    CN114902634A

  • Session management method and device for cross-domain computing power aware network

    CN115918247A

  • Novel lactic acid bacteria having immune-enhancing activity and uses thereof

    KR102519143B1