Communication method and apparatus

Abstract

Embodiments of the present application provide a communication method and apparatus. The method comprises: a first user plane function network element receiving a first data packet from a terminal device, the first data packet corresponding to a first application; on the basis of at least one DNAI and resources required for the first application, determining a second user plane function network element, the at least one DNAI being a DNAI corresponding to the first application, and the second user plane function network element corresponding to a first DNAI among the at least one DNAI; and sending the first data packet to the second user plane function network element. In the embodiments of the present application, when the first user plane function network element forwards the first data packet to the second user plane function network element corresponding to the first DNAI, since the first DNAI is selected on the basis of the resources required for the first application, the resources for the first application corresponding to the first DNAI can support the access of the terminal device, thereby reducing the delay of the terminal device in accessing the first application.

Description

Communication method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on September 26, 2023, with application number 202311259622.1 and invention name "A Communication Method and Device", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art

[0004] Currently, the user plane function (UPF) network element in the 5th generation (5G) network can forward data packets from terminal devices to the multi-access edge computing (MEC) platform. The UPF network element and the MEC platform share the same data network access identifier (DNAI). If the data packet corresponds to an application, the application server (AP) deployed on the MEC platform that supports the application can process the data packet.

[0005] However, the application server supporting the application deployed on the MEC platform may not be able to process the data message in time due to insufficient computing resources, resulting in a long delay for the terminal device to access the application.

[0006] Summary of the Invention

[0007] Embodiments of the present application provide a communication method and apparatus for reducing access latency.

[0008] In a first aspect, an embodiment of the present application provides a communication method, which can be executed by a first user plane function network element, or by a chip system, which can implement the function of the first user plane function network element. The method includes: receiving a first data packet from a terminal device, the first data packet corresponding to a first application; determining a second user plane function network element based on at least one DNAI and resources required by the first application, the at least one DNAI being the DNAI corresponding to the first application, and the second user plane function network element corresponding to the first DNAI in the at least one DNAI; and sending the first data packet to the second user plane function network element.

[0009] In an embodiment of the present application, after receiving the first data packet, the first user plane functional network element can determine the second user plane functional network element based on the resources required by the first application. For example, the MEC platform corresponding to the DNAI corresponding to the second user plane functional network element is an MEC platform with resources that can support processing the first data packet. As a result, after the first user plane functional network element sends the first data packet to the second user plane functional network element, the first data packet can be processed by the MEC platform corresponding to the second user plane functional network element, thereby improving the processing efficiency of the data packet and reducing the latency of the terminal device accessing the first application.

[0010] In an optional embodiment, determining the second user plane function network element includes: sending the first DNAI to the first network element, and receiving the address of the second user plane function network element from the first network element. In this embodiment, the first user plane function network element can obtain the address of the second user plane function network element corresponding to the first DNAI by interacting with the first network element, without pre-storing the address of the user plane function network element corresponding to the DNAI, thereby saving storage space of the first user plane function network element.

[0011] In an optional implementation, the first network element includes a session management function network element or a network storage function network element.

[0012] In an optional embodiment, determining the second user plane function network element includes: determining the address of the second user plane function network element based on the address of the user plane function network element corresponding to the at least one DNAI, where the at least one user plane function network element corresponding to the DNAI includes the second user plane function network element. In this embodiment, the first user plane function network element may also determine the address of the second user plane function network element using the pre-stored address of the user plane function network element corresponding to the DNAI, thereby reducing the interaction process of the network elements.

[0013] In an optional embodiment, the method further includes: sending the address of the second user plane function network element to the session management function network element. In this embodiment, the session management function network element can determine that the next-hop user plane function network element selected by the first user plane function network element for routing forwarding is the second user plane function network element, and the next-hop user plane function network element can be the next hop of the first user plane function network element, or the next hop of the base station, and then can perform corresponding processing, such as requesting the first user plane function network element or the base station to establish a tunnel (such as an N9 tunnel or an N3 tunnel) between the second user plane function network element to forward data packets, or determining whether the data packets can be forwarded to the second user plane function network element, etc. For example, before selecting the second user plane function network element as the next-hop user plane function network element, the first user plane function network element may have selected a user plane function network element different from the second user plane function network element (for example, user plane function network element A) as the next-hop user plane function network element, that is, the first user plane function network element may have forwarded the received data packet to the MEC platform corresponding to the DNAI corresponding to the user plane function network element A (for example, MEC platform A) for processing. Therefore, the session management function network element can request the application function network element to allow the historical information of MEC platform A processing the data packet to be migrated to the MEC platform corresponding to the DNAI corresponding to the second user plane function network element (for example, MEC platform B), so that MEC platform B can process the data packet in combination with the historical information of MEC platform A processing the data packet. If the application function network element allows migration, the session management function network element can determine that the first user plane function network element can forward the data packet to the second user plane function network element.

[0014] In an optional embodiment, the method further includes: receiving first indication information from the session management function network element, the first indication information being used to instruct the first user plane function network element to send a data packet to the second user plane function network element. In this embodiment, the session management function network element instructs the first user plane function network element to forward the data packet, enabling the packet forwarding process to be performed under the control of the core network.

[0015] In an optional embodiment, the method further includes: receiving a session modification request from the session management function network element, the session modification request being used to request the first user plane function network element to assign a tunnel identifier to a first tunnel, the first tunnel being a tunnel between the first user plane function network element and the second user plane function network element for transmitting data packets, the session modification request including a first identifier, the first identifier being the tunnel identifier assigned by the second user plane function network element to the first tunnel; sending a second identifier to the session management function network element, the second identifier being the tunnel identifier assigned by the first user plane function network element to the first tunnel; and establishing the first tunnel based on the first identifier and the second identifier. In this embodiment, the tunnel identifier can be transmitted between the first user plane function network element and the second user plane function network element via the session management function network element to establish the first tunnel (e.g., the N9 tunnel), and establishing the N9 tunnel via the session management function network element complies with the provisions of existing protocols and has better compatibility.

[0016] In an optional embodiment, the method further includes: sending a tunnel establishment request to the second user plane function network element, the tunnel establishment request including a second identifier, the second identifier being the tunnel identifier assigned by the first user plane function network element to the first tunnel, the first tunnel being a tunnel between the first user plane function network element and the second user plane function network element for transmitting data packets; receiving a first identifier from the second user plane function network element, the first identifier being the tunnel identifier assigned by the second user plane function network element to the first tunnel; and establishing the first tunnel based on the first identifier and the second identifier. In this embodiment, the tunnel identifier can be directly transmitted (for example, via the general packet radio service tunneling protocol (GTP)) between the first user plane function network element and the second user plane function network element to establish the first tunnel (for example, the N9 tunnel), reducing the interaction process of the network elements.

[0017] In an optional embodiment, the method further includes: receiving a first request from a session management function network element, the first request being used to request the first user plane function network element to report first information after receiving a data packet from the terminal device, the first information including a DNAI and / or an address, and the first information being used to determine a second user plane function network element. In this embodiment, the session management function network element can determine a next-hop user plane function network element selected by the first user plane function network element for routing forwarding, where the next-hop user plane function network element can be the next-hop of the first user plane function network element or the next-hop of the base station, and can then perform corresponding processing, such as requesting the first user plane function network element to establish a tunnel (e.g., an N9 tunnel) between the first user plane function network element and the next-hop user plane function network element to forward the data packet, or requesting the base station to establish a tunnel (e.g., an N3 tunnel) between the next-hop user plane function network element, or determining whether the data packet can be forwarded to the next-hop user plane function network element.

[0018] In an optional embodiment, the method also includes: sending a registration request to a network storage function network element, the registration request including one or more of the following information: the data network name (DNN) corresponding to the first user plane function network element; the single network slice selection assistance information (S-NSSAI, S-NSSAI) corresponding to the first user plane function network element; or, second indication information, used to indicate that the first user plane function network element has computing power routing capability, and the computing power routing capability is used by the first user plane function network element to forward the data message of the application according to the resources required by the application. In this embodiment, since the network storage function network element can pre-select and store the DNN and / or S-NSSAI corresponding to the user plane function network element with computing power routing capability, the first user plane function network element can indirectly report to the network storage function network element that the first user plane function network element has computing power routing capability through the DNN and / or S-NSSAI corresponding to the first user plane function network element, or can directly report to the network storage function network element that the first user plane function network element has computing power routing capability through the second indication information. The indication method is more flexible and also enables the network side to clearly understand the capabilities of the first user plane function network element.

[0019] In a second aspect, an embodiment of the present application further provides a communication method, which can be executed by a session management function network element, or by a chip system, which can implement the function of a session management function network element. The method includes: sending a first request to a first user plane function network element, the first request being used to request the first user plane function network element to report first information after receiving a data message from a terminal device, the first information including a DNAI and / or an address, the first information being used to determine a second user plane function network element, the data message corresponding to a first application; receiving a first DNAI and / or an address of the second user plane function network element from the first user plane function network element, the first DNAI being one of at least one DNAI, the at least one DNAI being a DNAI corresponding to the first application, the second user plane function network element corresponding to the first DNAI; and establishing a tunnel for transmitting data messages according to the first DNAI and / or the address of the second user plane function network element.

[0020] In an optional embodiment, the method further includes: sending the first DNAI to the network storage function network element, receiving the address of the second user plane function network element from the network storage function network element; and sending the address of the second user plane function network element to the first user plane function network element.

[0021] In an optional embodiment, the method also includes: sending a second request to the application function network element, the second request is used to request that the context information of the first application corresponding to the second DNAI be migrated to the first DNAI, the second DNAI is a DNAI other than the first DNAI in the at least one DNAI, the context information includes historical information of the first application, and the second request includes the first DNAI; receiving a first response from the application function network element, the first response is used to indicate that the context information of the first application corresponding to the second DNAI is allowed to be migrated to the first DNAI.

[0022] In an optional embodiment, the second request further includes third indication information, used to indicate that the first DNAI is determined from the at least one DNAI based on the resources required by the first application.

[0023] In an optional implementation, first indication information is sent to the first user plane function network element, where the first indication information is used to instruct the first user plane function network element to send a data packet to the second user plane function network element.

[0024] In an optional embodiment, a tunnel for transmitting data packets is established according to the address of the first DNAI and / or the second user plane functional network element, including: establishing a first tunnel according to the address of the first DNAI and / or the second user plane functional network element, the first tunnel being a tunnel for transmitting data packets between the first user plane functional network element and the second user plane functional network element; or, establishing a second tunnel according to the address of the first DNAI and / or the second user plane functional network element, the second tunnel being a tunnel for transmitting data packets between the access network device and the second user plane functional network element.

[0025] In an optional embodiment, a first tunnel is established according to the address of the first DNAI and / or the second user plane function network element, including: sending a third request to the second user plane function network element, the third request being used to request the second user plane function network element to assign a tunnel identifier to the first tunnel; receiving a first identifier from the second user plane function network element, the first identifier being the tunnel identifier assigned by the second user plane function network element to the first tunnel; sending a session modification request to the first user plane function network element, the session modification request being used to request the first user plane function network element to assign a tunnel identifier to the first tunnel, the session modification request including the first identifier; receiving a second identifier from the first user plane function network element, the second identifier being the tunnel identifier assigned by the first user plane function network element to the first tunnel; and sending the second identifier to the second user plane function network element.

[0026] In an optional embodiment, a second tunnel is established according to the address of the first DNAI and / or the second user plane functional network element, including: sending a fourth request to the second user plane functional network element, the fourth request being used to request the second user plane functional network element to assign a tunnel identifier to the second tunnel; receiving a third identifier from the second user plane functional network element, the third identifier being the tunnel identifier assigned by the second user plane functional network element to the second tunnel; sending the third identifier to the access and mobility management functional network element; receiving a fourth identifier from the access and mobility management functional network element, the fourth identifier being the tunnel identifier assigned by the access network device to the second tunnel; and sending the fourth identifier to the second user plane functional network element.

[0027] In an optional embodiment, the method further includes: receiving a session establishment request from the terminal device, the session establishment request being used to request the session management function network element to establish a first session, the first session being used for the terminal device to access the first application; sending a discovery request to the network storage function network element, the discovery request being used to request the network storage function network element to discover a user plane function network element with computing power routing capability, the computing power routing capability being used for the user plane function network element to forward the data packets of the application according to the resources required by the application; receiving a discovery response from the network storage function network element, the discovery response being used to indicate that the first user plane function network element has the computing power routing capability.

[0028] In an optional embodiment, the session establishment request includes one or more of the following information: the DNN corresponding to the first session; the S-NSSAI corresponding to the first session; or, fourth indication information, used to indicate that the data packet transmitted on the first session has computing power routing requirements.

[0029] In an optional embodiment, the discovery request includes one or more of the following information: the DNN corresponding to the first session; the S-NSSAI corresponding to the first session; the location information of the terminal device; or, fifth indication information, used to instruct the network storage function network element to discover the user plane function network element with the computing power routing capability.

[0030] Regarding the technical effects brought about by the second aspect or some optional implementation methods, reference may be made to the introduction to the technical effects of the first aspect or corresponding implementation methods.

[0031] In a third aspect, embodiments of the present application provide a communication device comprising a processor and a memory; the memory is configured to store computer instructions, and when the device is running, the processor executes the computer instructions stored in the memory to cause the device to perform any of the implementation methods described in aspects 1 to 2 above. The memory can be volatile or non-volatile memory, such as a cache memory in a semiconductor chip.

[0032] In a fourth aspect, embodiments of the present application provide a communications device, which may be a user plane function network element or a session management function network, or a chip for a user plane function network element or a session management function network. The device has the function of implementing any of the implementation methods of the first to second aspects described above. The function may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.

[0033] In a fifth aspect, an embodiment of the present application provides a communication device, comprising a unit or means for executing each step of any implementation method in the above-mentioned first to second aspects.

[0034] In a sixth aspect, an embodiment of the present application provides a communication device, comprising a processor and an interface circuit, wherein the processor is configured to communicate with other devices via the interface circuit and execute any of the implementation methods described in the first to second aspects above. The processor may be one or more processors.

[0035] In a seventh aspect, an embodiment of the present application provides a communication device, comprising a processor coupled to a memory, the processor configured to call a program stored in the memory to execute any of the implementation methods described in aspects 1 to 2 above. The memory may be located within or outside the device. The processor may also be one or more processors.

[0036] In an eighth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein instructions are stored in the computer-readable storage medium, which, when executed on a communication device, enables any implementation method in the above-mentioned first to second aspects to be executed.

[0037] In the ninth aspect, an embodiment of the present application further provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are run by a communication device, any implementation method in the above-mentioned first to second aspects is executed.

[0038] In the tenth aspect, an embodiment of the present application further provides a chip system, comprising: a processor for executing any implementation method in the above-mentioned first to second aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] FIG1A and FIG1B are schematic diagrams of two network architectures provided in embodiments of the present application;

[0040] FIG2A is a schematic diagram of a network architecture provided in an embodiment of the present application;

[0041] FIG2B is a schematic diagram of another network architecture provided in an embodiment of the present application;

[0042] FIG2C and FIG2D are schematic diagrams of two communication scenarios provided in an embodiment of the present application;

[0043] FIG3 is a flow chart of a communication method provided in an embodiment of the present application;

[0044] Figures 4, 5, 6, 7, and 8 are flowcharts of five communication methods provided in embodiments of the present application;

[0045] FIG9 is a schematic diagram of a device provided in an embodiment of the present application;

[0046] FIG10 is a schematic diagram of another device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0047] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0048] In the embodiments of the present application, the number of nouns, unless otherwise specified, means "singular noun or plural noun", that is, "one or more". "At least one" means one or more, and "plural" means two or more. "And / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A or B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. For example, A / B means: A or B. "At least one of the following items" or "one or more of them" and other similar expressions refer to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c, or one or more of a, b, or c, means: a, b, c, a and b, a and c, b and c, or a and b and c. Each of a, b, and c can be single or multiple.

[0049] The ordinal numbers "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the size, content, order, timing, priority, or importance of multiple objects. In addition, the numbering of the steps in the various embodiments introduced in the embodiments of this application is only to distinguish different steps and is not used to define the order between the steps. For example, S301 can occur before S302, or it can occur after S302, or it can also occur at the same time as S302.

[0050] Below, some terms or concepts in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

[0051] (1) In the embodiments of the present application, a terminal device is a device with wireless transceiver functions, which can be a fixed device, a mobile device, a handheld device (such as a mobile phone), a wearable device, a vehicle-mounted device, or a wireless device built into the above-mentioned device (such as a communication module, a modem, or a chip system, etc.). The terminal device is used to connect people, objects, machines, etc., and can be widely used in various scenarios, such as but not limited to the following scenarios: cellular communication, device-to-device communication (D2D), V2X, machine-to-machine / machine-type communication (M2M / MTC), Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, drones, robots and other scenarios. The terminal device may sometimes be referred to as user equipment (UE), terminal, access station, UE station, remote station, wireless communication device, or user equipment, etc.

[0052] In the embodiments of the present application, the communication device for implementing the terminal device function may be a terminal device, or may be a device capable of supporting the terminal device to implement the function, such as a chip system, which may be installed in the terminal device. In the technical solutions provided in the embodiments of the present application, the technical solutions provided in the embodiments of the present application are described by taking the terminal device as an example in which the device for implementing the terminal device function is a terminal device. In addition, for ease of description, the terminal device in the embodiments of the present application is described by taking a UE as an example.

[0053] (2) The network devices in the embodiments of the present application include, for example, access network devices and / or core network devices. The access network device is a device with wireless transceiver functions, which is used to communicate with the terminal device. The access network device includes but is not limited to base stations (base transceiver station (BTS), Node B, eNodeB / eNB, or gNodeB / gNB), transmission reception points (TRP), base stations subsequently evolved from the third generation partnership project (3GPP), access nodes in wireless fidelity (Wi-Fi) systems, wireless relay nodes, wireless backhaul nodes, etc. The base station can be: a macro base station, a micro base station, a pico base station, a small station, a relay station, etc. Multiple base stations can support networks with the same access technology, or they can support networks with different access technologies. The base station can include one or more co-station or non-co-station transmission and reception points. The access network device may also be a wireless controller, a centralized unit (CU), and / or a distributed unit (DU) in a cloud radio access network (CRAN) scenario. The access network device may also be a server, etc. For example, the network device in the vehicle to everything (V2X) technology may be a road side unit (RSU). The following describes the access network device using a base station as an example. The base station can communicate with the terminal device, or it can communicate with the terminal device through a relay station. The terminal device can communicate with multiple base stations in different access technologies. The core network device is used to implement functions such as mobility management, data processing, session management, policy and billing. The names of the devices that implement core network functions in systems with different access technologies may be different, and the embodiments of the present application are not limited to this. Taking the fifth generation (5G) mobile communication system as an example, the core network equipment includes: access and mobility management function (AMF), session management function (SMF), policy control function (PCF) or user plane function (UPF), etc.

[0054] In the embodiments of the present application, the communication device for implementing the network device function may be a network device, or may be a device capable of supporting the network device to implement the function, such as a chip system, which may be installed in the network device. In the technical solutions provided in the embodiments of the present application, the technical solutions provided in the embodiments of the present application are described by taking the network device as an example of the device for implementing the network device function being a network device.

[0055] Please refer to Figure 1A, which is a schematic diagram of a 5G network architecture based on a service-oriented architecture, which is also a network architecture used in the embodiments of this application. The 5G network architecture shown in Figure 1A can include three parts: the UE part, the data network (DN), and the operator network part.

[0056] Among them, the operator network may include one or more of the following network elements: authentication server function (AUSF) network element, network exposure function (NEF) network element, PCF network element, unified data management (UDM) network element, unified data repository (UDR), network storage function (NRF) network element, application function (AF) network element, AMF network element, SMF network element, (radio) access network (R)AN) or UPF network element, etc.

[0057] The operator network includes a radio access network and a core network. The UE accesses the core network through the (R)AN. The core network includes user plane network elements and control plane network elements. The user plane network elements of the core network include the UPF; the control plane network elements of the core network include at least one of the following network elements: AUSF, AMF, SMF, NSSF, NEF, NRF, UDM, PCF, or AF.

[0058] User plane network elements (such as UPF) are mainly responsible for packet forwarding, quality of service (QoS) control, billing information statistics, etc. Control plane network elements are mainly responsible for business process interaction, issuing packet forwarding policies and QoS control policies to the user plane.

[0059] The core network control plane can adopt a service-based architecture. That is, the interaction between control plane network elements uses service calls, replacing the point-to-point communication method in the traditional architecture. In a service-based architecture, one control plane network element will open services to other control plane network elements for them to call. In point-to-point communication, the communication interface between control plane network elements will have a specific set of messages that can only be used by the control plane network elements at both ends of the interface during communication.

[0060] The functions of network elements in the core network are described as follows:

[0061] UPF supports all or part of the following functions: interconnecting protocol data unit (PDU) sessions with data networks, packet routing and forwarding (for example, supporting uplink classifier for forwarding traffic to the data network, supporting branching points to support multi-homed PDU sessions), or packet inspection.

[0062] The AMF manages UE access and mobility. It is responsible for maintaining UE status, managing UE reachability, forwarding non-mobility management (MM) and non-access-stratum (NAS) messages, and forwarding session management (SM) N2 messages.

[0063] The SMF, or UE Session Management, allocates and releases resources for UE sessions. These resources include session quality of service (QoS), session paths, and forwarding rules. The SMF is responsible for selecting or reselecting UPFs, allocating Internet Protocol (IP) addresses, and establishing, modifying, and releasing bearers.

[0064] NEF opens network functions to third parties in the form of northbound application programming interfaces (APIs).

[0065] NRF provides storage and selection functions for network function entity information for other network elements.

[0066] UDM, User Context Management, is responsible for managing the UE's subscription data and notifying the corresponding network elements when the subscription data is modified.

[0067] The UDR, a unified data repository, is responsible for storing and retrieving contract data, policy data, and public architecture data, enabling network elements such as the UDM, PCF, or NEF to access relevant data. The UDR can implement different data access authentication mechanisms for different types of data (such as contract data and policy data) to ensure data access security. The UDR should be able to return a failure response with an appropriate cause value for illegal service-based operations or data access requests.

[0068] PCF, User Policy Management, is used to generate and manage user, session, and QoS flow processing policies.

[0069] AF (Application Management) provides application layer services to the UE. When providing services to the UE, AF has requirements for QoS (policy) and charging policies, and needs to notify the network. In addition, AF also needs to feedback application-related information from the core network.

[0070] The relevant interfaces between network element functions involved in the embodiments of this application include:

[0071] N1: Interface between UE and core network control plane.

[0072] N2: Communication interface between (R)AN and core network control plane.

[0073] N3: Communication interface between (R)AN and UPF, used to transmit user plane data.

[0074] N4: Communication interface between SMF and UPF, used by SMF to configure policies for UPF, etc.

[0075] N6: Communication port between UPF and DN.

[0076] Please refer to Figure 1B again, which is a schematic diagram of a 5G network architecture based on a point-to-point interface. This network architecture is another network architecture used in the embodiments of the present application. For the network elements in Figure 1B, please refer to the introduction to the relevant network elements in Figure 1A. The main difference between Figure 1B and Figure 1A is that the interfaces between the network elements in Figure 1B are point-to-point interfaces, rather than service-based interfaces.

[0077] (3) Computing-first network (CFN) is a new type of information infrastructure that allocates and flexibly schedules computing resources, storage resources, and network resources on demand between cloud computing, edge computing, and terminal devices. The purpose of CFN is to enable data flows to select the optimal path and optimal computing node in the outbound process and the optimal path in the return process.

[0078] CFN dynamic anycast (Dyncast) is a key technology in CFN's control layer or routing layer. It distributes computing power information of computing nodes through network protocols and combines network information to provide users with optimal computing power allocation and network connectivity.

[0079] (4) Multi-access edge computing (MEC) refers to cloud computing located at the edge of the network. It deploys computing power closer to users, reduces network latency, and provides users with computing power and applications nearby, thereby significantly improving the service experience.

[0080] The UPF network element in the 5G network is a key element in the integration of MEC and 5G networks. MEC is primarily responsible for computing data packets forwarded by the UPF network element. For example, the UPF network element can connect to the MEC data center (i.e., the MEC platform) via the N6 interface. The UPF network element can forward data packets accessing a specific application to the MEC platform, allowing the application server deployed on the MEC platform to support the application to process the data packets.

[0081] Please refer to Figure 2A, which is a schematic diagram of a network architecture provided in an embodiment of the present application, taking a 5G network as an example. The network architecture shown in Figure 2A may include a UE, a base station, three UPF network elements (respectively, UPF1 network element, UPF2 network element, and UPF3 network element), and three MEC platforms (respectively, MEC platform 1, MEC platform 2, and MEC platform 3). Among them, the base station can connect to the UPF1 network element via the N3 interface, and the UPF1 network element can connect to the UPF2 network element and the UPF3 network element via the N9 interface. The UPF1 network element, UPF2 network element, and UPF3 network element can connect to MEC platform 1, MEC platform 2, and MEC platform 3, respectively, via the N6 interface.

[0082] Please refer to Figure 2B again, which is another network architecture diagram provided for an embodiment of the present application, taking a 5G network as an example. The network architecture shown in Figure 2B may include a UE, a base station, three UPF network elements (respectively, a UPF1 network element, a UPF2 network element, and a UPF3 network element) and three MEC platforms (respectively, MEC platform 1, MEC platform 2, and MEC platform 3). Among them, the base station can be connected to any UPF network element among the UPF1 network element, the UPF2 network element, and the UPF3 network element through the N3 interface, which can be understood as the base station connecting to a UPF network element through the N3 interface. The UPF1 network element, the UPF2 network element, and the UPF3 network element can be connected to the MEC platform 1, MEC platform 2, and MEC platform 3, respectively, through the N6 interface.

[0083] It should be understood that Figure 2A or 2B only shows an exemplary network architecture for ease of understanding, but this should not constitute any limitation to the present application. The network architecture can also include a larger number of UPF network elements and a larger number of MEC platforms; the MEC platforms that interact with different UPF network elements can be the same MEC platform or different MEC platforms; the number of MEC platforms that interact with different UPF network elements can be the same or different, and the embodiments of the present application do not limit this.

[0084] The following describes the method provided by the embodiments of the present application in conjunction with the accompanying drawings. The various embodiments of this document can be applied to the network architecture shown in Figure 1A or Figure 1B. For example, the UPF network element described in the various embodiments of this document can be the UPF network element in Figure 1A or Figure 1B; the SMF network element described in the various embodiments of this document can be the SMF network element in Figure 1A or Figure 1B; the NRF network element described in the various embodiments of this document can be the NRF network element in Figure 1A or Figure 1B; the AF network element described in the various embodiments of this document can be the AF network element in Figure 1A or Figure 1B; the AMF network element described in the various embodiments of this document can be the AMF network element in Figure 1A or Figure 1B.

[0085] The various embodiments herein may also be applied to the network architecture shown in Figure 2A or Figure 2B. For example, the base station described in the various embodiments herein may be the base station in Figure 2A or Figure 2B; the UPF network element described in the various embodiments herein may be the UPF network element in Figure 2A or Figure 2B; and the MEC platform described in the various embodiments herein may be the MEC platform in Figure 2A or Figure 2B.

[0086] Please refer to Figure 2C, which is a schematic diagram of a communication scenario provided in an embodiment of the present application. It should be understood that the scenario shown in Figure 2C can be applied to the network architecture of Figure 2A. In this scenario, the UPF1 network element and the UPF2 network element can periodically synchronize the resources of the MEC platform corresponding to their respective data network access identifiers (DNAI) through the border gateway protocol (BGP) protocol. For example, the UPF1 network element can obtain the resources of the MEC platform 2 corresponding to the DNAI#2 corresponding to the UPF2 network element, and the resources of the MEC platform 2 can be the resources (such as computing power resources) of the application server 3 (supporting application 1) and the application server 4 (supporting application 2) deployed on the MEC platform 2. After the UPF1 network element receives the data packet 1 from UE1 accessing application 1, it can perform computing power routing to determine that the application server supporting application 1 with the optimal (or appropriate) computing power resources is application server 3. The UPF1 network element can report the address of DNAI#2 and / or the UPF2 network element corresponding to DNAI#2 (for example, the Internet Protocol (IP) address) to the SMF network element. The SMF network element can determine the optimal (or appropriate) path for transmitting data message 1 (such as UE1, base station, UPF1 network element, UPF2 network element, and application server 3 deployed on the MEC platform 2) based on the address of DNAI#2 and / or the UPF2 network element corresponding to DNAI#2. The SMF network element or the UPF1 network element can establish an N9 tunnel for transmitting data message 1 between the UPF1 network element and the UPF2 network element, so that the UPF1 network element can forward the data message 1 to the UPF2 network element. Among them, the optimal (or appropriate) path is compared with the original path for transmitting data message 1 when the UPF1 network element does not perform computing power routing (such as UE1, base station, UPF1 network element, and application server 1 deployed on MEC platform 1). It takes into account whether the computing power resources of the application server deployed on the MEC platform can process the data message in time, thereby reducing the delay of UE accessing the application.

[0087] Please refer to Figure 2D, which is a schematic diagram of another communication scenario provided in an embodiment of the present application. It should be understood that the scenario shown in Figure 2D can be applied to the network architecture of Figure 2B. In this scenario, the UPF1 network element and the UPF2 network element can periodically synchronize the resources of the MEC platform corresponding to their respective DNAIs through the BGP protocol. For example, the UPF1 network element can obtain the resources of the MEC platform 2 corresponding to the DNAI#2 corresponding to the UPF2 network element. The resources of the MEC platform 2 can be the resources (such as computing power resources) of the application server 3 (supporting application 1) and the application server 4 (supporting application 2) deployed on the MEC platform 2. After the UPF1 network element receives the data packet 1 from UE1 accessing application 1, it can perform computing power routing and determine that the application server supporting application 1 with the best (or appropriate) computing power resources is application server 3. The UPF1 network element can report the address of DNAI#2 and / or the UPF2 network element corresponding to DNAI#2 to the SMF network element. The SMF network element can determine the optimal (or appropriate) path for transmitting data message 1 (such as UE1, base station, UPF2 network element, and application server 3 deployed on MEC platform 2) based on DNAI#2 and / or the address of the UPF2 network element corresponding to DNAI#2. The SMF network element can establish an N3 tunnel for transmitting data message 1 between the base station and the UPF2 network element, and switch the N3 tunnel for transmitting data message 1 between the base station and the UPF1 network element to the N3 tunnel for transmitting data message 1 between the base station and the UPF2 network element, so that the base station can forward the data message 1 to the UPF2 network element. Among them, the optimal (or appropriate) path is compared with the original path for transmitting data message 1 when the UPF1 network element does not perform computing power routing (such as UE1, base station, UPF1 network element, and application server 1 deployed on MEC platform 1). It takes into account whether the computing power resources of the application server deployed on the MEC platform can process the data message in a timely manner, thereby reducing the latency of UE accessing the application.

[0088] In the drawings corresponding to the various embodiments of the present application, all steps indicated by dotted lines are optional steps.

[0089] An embodiment of the present application provides a communication method. See Figure 3 for a flowchart of the method. This method can be applied to the network architecture of Figure 2A or Figure 2B without limitation. This method can be applied to the communication scenarios of Figure 2C or Figure 2D without limitation. In the embodiment shown in Figure 3, the first UPF network element is UPF1 network element, and the second UPF network element is UPF2 network element or UPF3 network element.

[0090] S301: A UE sends a first data packet to a first UPF network element. Correspondingly, the first UPF network element receives the first data packet from the UE. The first data packet corresponds to a first application.

[0091] Among them, an N3 tunnel is established between the base station and the first UPF network element, and the UE can send the first data message to the first UPF network element through the base station.

[0092] In a possible implementation, before the UE sends the first data message to the first UPF network element, the UE, the SMF network element, and the NRF network element may perform the following steps:

[0093] Step A1: The UE sends a session establishment request to the SMF network element. Correspondingly, the SMF network element receives the session establishment request from the UE.

[0094] Among them, the session establishment request can be used to request the SMF network element to establish a first session, and the first session can be used for the UE to access the first application. The session establishment request may include but is not limited to one or more of the following information: the DNN corresponding to the first session; the S-NSSAI corresponding to the first session; or, indication information 1. Indication information 1 can also be referred to as the fourth indication information. Indication information 1 can be used to indicate that the data packet transmitted on the first session has a computing power routing requirement. The computing power routing requirement may refer to the need for a network device (such as a UPF network element) to forward the data packet of the application according to the resources required by the application (such as computing power resources). The resources required for the application may refer to the computing power resources of the application server deployed on the MEC platform that supports the application, such as the number of connected users and / or the central processing unit (CPU) load of the application server.

[0095] Step A2: The SMF network element sends a discovery request to the NRF network element, and accordingly, the NRF network element receives the discovery request from the SMF network element.

[0096] Among them, the discovery request can be an Nnrf_NFDiscovery_Request message. The discovery request can be used to request the NRF network element to discover the UPF network element with computing power routing capability. The discovery request may include but is not limited to one or more of the following information: the DNN corresponding to the first session; the S-NSSAI corresponding to the first session; the location information of the UE; or, indication information 2. Indication information 2 can also be referred to as the fifth indication information. Indication information 2 can be used to instruct the NRF network element to discover the UPF network element with computing power routing capability. The computing power routing capability can be used to forward the data message of the application according to the resources required by the application (such as computing power resources). Optionally, the computing power routing capability can be a CFN routing capability (such as CFN Dyncast).

[0097] Step A3: The NRF network element sends a discovery response to the SMF network element, and accordingly, the SMF network element receives a discovery response from the NRF network element.

[0098] The discovery response may be an Nnrf_NFDiscovery_Response message. The discovery response may include the address of the first UPF network element. Optionally, the discovery response may also include indication information that can be used to indicate that the first UPF network element has computing power routing capability, so that the SMF network element can select the first UPF network element to forward the data packet transmitted on the first session.

[0099] In one possible implementation, before the NRF network element sends a discovery response to the SMF network element, the first UPF network element and the NRF network element may perform the following steps: the first UPF network element sends a registration request to the NRF network element, and accordingly, the NRF network element receives the registration request from the first UPF network element.

[0100] The registration request may be an Nnrf_NFManagement_NFRegister Request message. The registration request may include, but is not limited to, one or more of the following information: the DNN corresponding to the first UPF network element; the S-NSSAI corresponding to the first UPF network element; or indication information 3. Indication information 3 may also be referred to as second indication information. Indication information 3 may be used to indicate that the first UPF network element has computing power routing capabilities.

[0101] Step A4: The SMF network element sends a session establishment response to the UE. Correspondingly, the UE receives the session establishment response from the SMF network element. The session establishment response may be used to indicate that the first session is successfully established.

[0102] S302: The first UPF network element determines a second UPF network element based on at least one DNAI and resources required by the first application. The at least one DNAI is a DNAI corresponding to the first application, and the second UPF network element corresponds to a first DNAI in the at least one DNAI.

[0103] In the above 301, the first UPF network element may receive a first data message corresponding to a first application from a UE. If the first UPF network element directly forwards the first data message to the MEC platform corresponding to the first UPF network element, so that the application server supporting the first application deployed on the MEC platform processes the first data message, since the first UPF network element does not consider the computing power resources of the application server supporting the first application deployed on the MEC platform, the computing power resources of the application server supporting the first application deployed on the MEC platform may be insufficient and unable to process the first data message in a timely manner, thereby resulting in a long delay in the UE accessing the first application. Therefore, in order to reduce the delay in the UE accessing the first application, the first UPF network element may consider whether the computing power resources of each application server supporting the first application can process the first data message in a timely manner when forwarding the first data message to the application server supporting the first application, thereby reducing the delay in the UE accessing the first application.

[0104] Specifically, S302 includes S302a and S302b.

[0105] S302a. The first UPF network element determines a first DNAI based on at least one DNAI and resources required by the first application.

[0106] Among them, at least one DNAI is the DNAI corresponding to the first application, and the DNAI corresponding to the first application may refer to the DNAI corresponding to the deployment location of the first application. For example, the MEC platform corresponding to DNAI#1 deploys application server #1 supporting the first application, then DNAI#1 is a DNAI corresponding to the first application. The resources required for the first application may refer to the computing power resources of the application server supporting the first application deployed on the MEC platform corresponding to the DNAI corresponding to the first application. For example, the MEC platform corresponding to DNAI#1 deploys application server #1 supporting the first application, then the resources required for the first application corresponding to DNAI#1 are the computing power resources of application server #1. The first DNAI may be the DNAI corresponding to the application server that supports the first application and has the best (or appropriate) computing power resources.

[0107] In one possible implementation, multiple UPF network elements can periodically synchronize the resources of the MEC platform corresponding to their respective DNAIs through the BGP protocol. That is, the first UPF network element can obtain the resources of the MEC platform corresponding to the DNAIs of other UPF network elements from other UPF network elements through the BGP protocol. Among them, one DNAI can correspond to at least one UPF network element, so a UPF network element can obtain the resources of the MEC platform corresponding to a DNAI from each UPF network element corresponding to the DNAI, or can obtain the resources of the MEC platform corresponding to the DNAI from a UPF network element corresponding to the DNAI.

[0108] Exemplarily, the first UPF network element can obtain the resources of the MEC platforms corresponding to DNAI#1, DNAI#2 and DNAI#3 as shown in Table 1 through the BGP protocol. Among them, the MEC platform corresponding to DNAI#1 deploys application server #1 (supporting application #1) and application server #2 (supporting application #2), the MEC platform corresponding to DNAI#2 deploys application server #3 (supporting application #1), application server #4 (supporting application #2) and application server #5 (supporting application #3), and the MEC platform corresponding to DNAI#3 deploys application server #6 (supporting application #1). Therefore, the resources of the MEC platform corresponding to DNAI#1, DNAI#2 and DNAI#3 corresponding to the deployment location of application #1 can be the number of users connected to application server #1 and / or CPU load, the number of users connected to application server #3 and / or CPU load, and the number of users connected to application server #6 and / or CPU load, respectively. The resources of the MEC platform corresponding to DNAI#1 and DNAI#2 corresponding to the deployment location of application #2 can be the number of users connected to application server #2 and / or CPU load, and the number of users connected to application server #4 and / or CPU load, respectively. The resources of the MEC platform corresponding to DNAI#2 corresponding to the deployment location of application #3 can be the number of users connected to application server #5 and / or CPU load.

[0109] After the first UPF network element receives data packet 1 for accessing application #1 from the UE, the first UPF network element can determine an application server with optimal (or appropriate) computing power resources from application server #1, application server #3 and application server #6 supporting application #1 based on the resources of the MEC platform corresponding to DNAI #1, DNAI #2 and DNAI #3 corresponding to the deployment location of application #1, and determine the DNAI corresponding to the application server with optimal (or appropriate) computing power resources as the first DNAI.

[0110] Table 1

[0111] S302b. The first UPF network element obtains the address of the second UPF network element.

[0112] The second UPF network element may correspond to the first DNAI. The address of the second UPF network element may be an Internet Protocol (IP) address of the second UPF network element.

[0113] In a first example, a first UPF network element may send a first DNAI to a first network element, and receive an address of a second UPF network element from the first network element, wherein the first network element includes an SMF network element or an NRF network element.

[0114] For example, the first UPF network element and the SMF network element can perform the following steps to obtain the address of the second UPF network element:

[0115] Step B1: The first UPF network element sends the first DNAI to the SMF network element. Correspondingly, the SMF network element receives the first DNAI from the first UPF network element.

[0116] Step B2: The SMF network element sends the address of the second UPF network element to the first UPF network element. Correspondingly, the first UPF network element receives the address of the second UPF network element from the SMF network element.

[0117] Optionally, the SMF network element and the NRF network element may perform the following steps to obtain the address of the second UPF network element:

[0118] Step C1: The SMF network element sends a first DNAI to the NRF network element, and correspondingly, the NRF network element receives the first DNAI from the SMF network element. The first DNAI may be carried in the Nnrf_NFDiscovery_Request message.

[0119] Step C2: The NRF network element sends the address of the second UPF network element to the SMF network element. Correspondingly, the SMF network element receives the address of the second UPF network element from the NRF network element. The address of the second UPF network element may be carried in the Nnrf_NFDiscovery_Response message.

[0120] Alternatively, the first UPF network element and the NRF network element may perform the following steps to obtain the address of the second UPF network element:

[0121] Step D1: The first UPF network element sends a first DNAI to the NRF network element. Correspondingly, the NRF network element receives the first DNAI from the first UPF network element. The first DNAI may be carried in an Nnrf_NFDiscovery_Request message.

[0122] Step D2: The NRF network element sends the address of the second UPF network element to the first UPF network element. Correspondingly, the first UPF network element receives the address of the second UPF network element from the NRF network element. The address of the second UPF network element may be carried in the Nnrf_NFDiscovery_Response message.

[0123] In the second example, the first UPF network element determines the address of the second UPF network element based on the address of the UPF network element corresponding to at least one DNAI. For example, when the above-mentioned multiple UPF network elements periodically synchronize the resources of the MEC platform corresponding to their respective DNAIs through the BGP protocol, their respective addresses are also synchronized.

[0124] In one possible implementation, after the first UPF network element obtains the address of the second UPF network element by sending the first DNAI to the NRF network element in the first example above, or obtains the address of the second UPF network element through the second example above, the first UPF network element and the SMF network element may perform the following steps: the first UPF network element sends the address of the second UPF network element to the SMF network element, and accordingly, the SMF network element receives the address of the second UPF network element from the first UPF network element.

[0125] In one possible implementation, after the SMF network element receives the discovery response from the NRF network element, the SMF network element can determine that the first UPF network element has computing power routing capability, that is, the SMF network element can determine that the first UPF network element can perform computing power routing forwarding on the data message from the UE to meet the computing power routing requirements of the data message transmitted by the UE on the first session. Therefore, the SMF network element and the first UPF network element can perform the following steps: the SMF network element sends request 1 to the first UPF network element, and accordingly, the first UPF network element receives request 1 from the SMF network element. Request 1 can also be referred to as a first request. Request 1 can be an N4 session establishment request. Request 1 can be used to request the first UPF network element to report first information after receiving the data message from the UE. The first information includes DNAI and / or address, and the first information is used to determine the second user plane function network element. It can be understood that request 1 can be used to request the first UPF network element to report the information of the next-hop UPF network element after receiving the data message from the UE. The next-hop UPF network element can be the next hop of the first UPF network element, for example, the first UPF network element forwards the data message to the next-hop UPF network element, or it can also be the next hop of the base station, for example, the base station forwards the data message to the next-hop UPF network element. The information of the next-hop UPF network element includes the DNAI corresponding to the next-hop UPF network element and / or the address of the next-hop UPF. This enables the SMF network element to obtain the DNAI (for example, the first DNAI) corresponding to the next-hop UPF network element and / or the address of the next-hop UPF network element (for example, the second UPF network element) determined when the first UPF network element performs computing power routing forwarding on the first data message corresponding to the first application from the UE, so as to establish a tunnel (i.e., N9 tunnel) for transmitting data messages between the first UPF network element and the second UPF network element, or to establish a tunnel (i.e., N3 tunnel) for transmitting data messages between the base station and the second UPF network element.

[0126] Specifically, after the SMF network element receives the first DNAI and / or the address of the second UPF network element from the first UPF network element, the SMF network element can establish a tunnel for transmitting data messages according to the first DNAI and / or the address of the second UPF network element. The tunnel can be a first tunnel or a second tunnel. The first tunnel can be a tunnel for transmitting data messages between the first UPF network element and the second UPF network element (i.e., an N9 tunnel), and the second tunnel can be a tunnel for transmitting data messages between the base station and the second UPF network element (i.e., an N3 tunnel).

[0127] In one example, the SMF network element, the first UPF network element, and the second UPF network element may perform the following steps to establish a first tunnel:

[0128] Step E1: The SMF network element sends Request 2 to the second UPF network element. In response, the second UPF network element receives Request 2 from the SMF network element. Request 2 may also be referred to as a third request. Request 2 may be an N4 session establishment request. Request 2 may be used to request the second UPF network element to allocate a tunnel identifier for the first tunnel.

[0129] Step E2: The second UPF network element sends a first identifier to the SMF network element. Accordingly, the SMF network element receives the first identifier from the second UPF network element. The first identifier is the tunnel identifier assigned by the second UPF network element to the first tunnel. The first identifier may be carried in the N4 session establishment response.

[0130] Step E3: The SMF network element sends a session modification request to the first UPF network element. In response, the first UPF network element receives the session modification request from the SMF network element. The session modification request may be an N4 session modification request. The session modification request may be used to request the first UPF network element to assign a tunnel identifier to the first tunnel. The session modification request may include the first identifier.

[0131] Step E4: The first UPF network element sends a second identifier to the SMF network element. In response, the SMF network element receives the second identifier from the first UPF network element. The second identifier is the tunnel identifier assigned by the first UPF network element to the first tunnel. The second identifier can be carried in the N4 session modification response.

[0132] Step E5: The SMF network element sends a second identifier to the second UPF network element. Correspondingly, the second UPF network element receives the second identifier from the SMF network element. The second identifier can be carried in the N4 session modification request.

[0133] Step E6: The first UPF network element establishes the first tunnel according to the first identifier and the second identifier, and the second UPF network element establishes the first tunnel according to the first identifier and the second identifier.

[0134] In another example, the SMF network element, the second UPF network element, the AMF network element, and the base station may perform the following steps to establish a second tunnel:

[0135] Step F1: The SMF network element sends Request 3 to the second UPF network element. Accordingly, the second UPF network element receives Request 3 from the SMF network element. Request 3 may also be referred to as a fourth request. Request 3 may be an N4 session establishment request. Request 3 may be used to request the second UPF network element to allocate a tunnel identifier for the second tunnel.

[0136] Step F2: The second UPF network element sends a third identifier to the SMF network element. Correspondingly, the SMF network element receives the third identifier from the second UPF network element. The third identifier is the tunnel identifier allocated by the second UPF network element to the second tunnel, and the third identifier can be carried in the N4 session establishment response.

[0137] Step F3: The SMF network element sends a third identifier to the AMF network element, and accordingly, the AMF network element receives the third identifier from the SMF network element. The third identifier may be carried in the N2 session management (SM) information of the Namf_Communication_N1N2MessageTransfer message.

[0138] Step F4: The AMF network element sends a third identifier to the base station. Accordingly, the base station receives the third identifier from the AMF network element. The third identifier may be carried in the N2 SM information of the N2 message.

[0139] Step F5: The base station sends a fourth identifier to the AMF network element. Accordingly, the AMF network element receives the fourth identifier from the base station. The fourth identifier may be carried in the N2 SM information of the N2 message.

[0140] Step F6: The AMF network element sends a fourth identifier to the SMF network element. Correspondingly, the SMF network element receives the fourth identifier from the AMF network element. The fourth identifier is the tunnel identifier allocated by the base station for the second tunnel, and the fourth identifier can be carried in the N2 SM information of the Nsmf_PDUSession_UpdateSMContext message.

[0141] Step F7: The SMF network element sends a fourth identifier to the second UPF network element, and correspondingly, the second UPF network element receives the fourth identifier from the SMF network element. The fourth identifier may be carried in the N4 session modification request.

[0142] Step F8: The second UPF network element establishes a second tunnel according to the third identifier and the fourth identifier, and the base station establishes a second tunnel according to the third identifier and the fourth identifier.

[0143] S303. The first UPF network element sends a first data message to the second UPF network element. Correspondingly, the second UPF network element receives the first data message from the first UPF network element.

[0144] The tunnel for transmitting data packets between the first UPF network element and the second UPF network element is the first tunnel. The first tunnel can be established by transmitting the tunnel identifier allocated by the first UPF network element and the second UPF network element through the SMF network element, that is, the SMF network element, the first UPF network element, and the second UPF network element execute the above steps E1-E6 to establish the first tunnel. Alternatively, the first tunnel can be established by transmitting the tunnel identifier allocated by the first UPF network element and the second UPF network element through GTP-C in the general packet radio service tunneling protocol (GTP), that is, the first UPF network element and the second UPF network element execute the following steps to establish the first tunnel:

[0145] Step G1: The first UPF network element sends a tunnel establishment request to the second UPF network element, and correspondingly, the second UPF network element receives the tunnel establishment request from the first UPF network element, wherein the tunnel establishment request includes a second identifier.

[0146] Step G2: The second UPF network element sends the first identifier to the first UPF network element. Correspondingly, the first UPF network element receives the first identifier from the second UPF network element.

[0147] Step G3: The first UPF network element establishes the first tunnel according to the first identifier and the second identifier, and the second UPF network element establishes the first tunnel according to the first identifier and the second identifier.

[0148] In one possible implementation, the first UPF network element may be a UPF1 network element, and the second UPF network element may be a UPF2 network element or a UPF3 network element. This can be understood as the UPF1 network element being able to send a first data packet to the UPF2 network element or the UPF3 network element. When the UPF1 network element sends the first data packet to the UPF2 network element, the application server currently having the best (or appropriate) computing resources is the application server supporting the first application deployed on the MEC platform (or DNAI) corresponding to the UPF2 network element. In this case, the DNAI corresponding to the UPF2 network element may be referred to as the first DNAI. When the UPF1 network element sends the first data message to the UPF3 network element, the application server that currently has the best (or suitable) computing power resources is the application server that supports the first application deployed on the MEC platform (or DNAI) corresponding to the UPF3 network element. It can be understood that as time goes by, the application server that currently has the best (or suitable) computing power resources may be updated from the application server that supports the first application deployed on the MEC platform (or DNAI) corresponding to the UPF2 network element to the application server that supports the first application deployed on the MEC platform (or DNAI) corresponding to the UPF3 network element. At this time, the DNAI corresponding to the UPF3 network element can be called the first DNAI, and the DNAI corresponding to the UPF2 network element can be called the second DNAI, that is, the second DNAI is a DNAI other than the first DNAI in at least one DNAI corresponding to the first application.

[0149] For example, the MEC platform corresponding to DNAI#1 deploys application server #1 (supporting application #1), the MEC platform corresponding to DNAI#2 deploys application server #3 (supporting application #1), and the MEC platform corresponding to DNAI#3 deploys application server #6 (supporting application #1). The UPF3 network element corresponds to DNAI#1, and the UPF2 network element corresponds to DNAI#2. When the application server with the best (or appropriate) computing power resources is application server #3 corresponding to DNAI#2, after the UPF1 network element receives data packet 1 for accessing application #1 from the UE, it needs to send data packet 1 for accessing application #1 to the UPF2 network element. As time goes by, the application server with the best (or appropriate) computing power resources may be updated from application server #3 corresponding to DNAI#2 to application server #1 corresponding to DNAI#1. At this time, after the UPF1 network element receives data packet 1 for accessing application #1 from the UE, it needs to send data packet 1 for accessing application #1 to the UPF3 network element.

[0150] Therefore, after the SMF network element receives the first DNAI from the first UPF network element, if the second UPF network element is a UPF3 network element, the SMF network element and the AF network element may perform the following steps to determine whether to migrate the context information of the first application corresponding to the second DNAI to the first DNAI:

[0151] Step H1: The SMF network element sends request 4 to the AF network element, and accordingly, the AF network element receives request 4 from the SMF network element.

[0152] Request 4 may also be referred to as a second request. Request 4 may be an Nsmf_EventExposure_Notify message. Request 4 may be used to request that the context information of the first application corresponding to the second DNAI be migrated to the first DNAI. The context information of the first application includes historical information of the first application, and request 4 may include the first DNAI. Optionally, request 4 may also include indication information 4. Indication information 4 may also be referred to as third indication information. Indication information 4 may be used to indicate that the first DNAI is determined from at least one DNAI corresponding to the first application based on the resources required by the first application.

[0153] Step H2: The AF network element migrates the context information of the first application corresponding to the second DNAI to the first DNAI. For example, the application server supporting the first application deployed on the MEC platform corresponding to the second DNAI is application server #1, and the application server supporting the first application deployed on the MEC platform corresponding to the first DNAI is application server #2. The AF network element can determine whether to migrate the context information of application server #1 to application server #2 based on the migration energy consumption between application server #1 and application server #2.

[0154] Step H3: The AF network element sends Response 1 to the SMF network element. Accordingly, the SMF network element receives Response 1 from the AF network element. Response 1 may also be referred to as a first response. Response 1 may be an Nsmf_EventExposure_AppRelocationInfo message. Response 1 may be used to indicate permission to migrate the context information of the first application corresponding to the second DNAI to the first DNAI.

[0155] Optionally, if the AF network element does not allow the context information of the first application corresponding to the second DNAI to be migrated to the first DNAI, the AF network element may send a response 2 to the SMF network element, and accordingly, the SMF network element receives the response 2 from the AF network element. Response 2 may be an Nsmf_EventExposure_AppRelocationInfo message. Response 2 may be used to allow the context information of the first application corresponding to the second DNAI to be migrated to a third DNAI. Response 2 may include a third DNAI. The third UPF network element corresponds to the third DNAI.

[0156] In one possible implementation, after the SMF network element receives the response 1 from the AF network element, the SMF network element and the first UPF network element may perform the following steps: the SMF network element sends an indication message 5 to the first UPF network element, and accordingly, the first UPF network element receives the indication message 5 from the SMF network element. The indication message 5 may also be referred to as the first indication message. The indication message 5 may be used to instruct the first UPF network element to send a first data packet to the UPF network element corresponding to the first DNAI. Optionally, the indication message 5 may be used to instruct the first UPF network element to send the first data packet to a second UPF network element.

[0157] Optionally, after the SMF network element receives the response 2 from the AF network element, the SMF network element and the first UPF network element may perform the following steps: the SMF network element sends an indication message 6 to the first UPF network element, and accordingly, the first UPF network element receives the indication message 6 from the SMF network element. The indication message 6 may be used to instruct the first UPF network element to send a first data packet to the third UPF network element.

[0158] Please refer to Figure 4, which is another flowchart illustrating a communication method provided in an embodiment of the present application. It should be understood that Figure 4 is an exemplary interaction diagram of the method shown in Figure 3, and the present embodiment is not limited thereto. The method shown in Figure 4 can be applied to the network architecture shown in Figure 2A. In the embodiment shown in Figure 4, the first UPF network element is UPF1 and the second UPF network element is UPF2.

[0159] S401: UPF1 network element and UPF2 network element periodically synchronize the resources of the MEC platform corresponding to their respective DNAI through the BGP protocol. Optionally, UPF1 network element and UPF2 network element synchronize their respective addresses through the BGP protocol.

[0160] The specific implementation process of the above S401 can refer to the content of the above S302 and will not be repeated here.

[0161] S402: The UPF1 network element sends a registration request to the NRF network element. In response, the NRF network element receives the registration request from the UPF1 network element. This registration request may be an Nnrf_NFManagement_NFRegister Request message. This registration request may include, but is not limited to, one or more of the following information: the DNN corresponding to the UPF1 network element; the S-NSSAI corresponding to the UPF1 network element; or indication information 3. Indication information 3 may be used to indicate that the UPF1 network element has computing power routing capabilities.

[0162] S403: The UE sends a session establishment request to the SMF network element. In response, the SMF network element receives the session establishment request from the UE. The session establishment request may be used to request the SMF network element to establish a first session, which can be used by the UE to access a first application. The session establishment request may include, but is not limited to, one or more of the following information: the DNN corresponding to the first session; the S-NSSAI corresponding to the first session; or, indication information 1. Indication information 1 may be used to indicate that data packets transmitted on the first session have computing power routing requirements.

[0163] S404: The SMF network element sends a discovery request to the NRF network element. In response, the NRF network element receives the discovery request from the SMF network element. The discovery request may be an Nnrf_NFDiscovery_Request message. This discovery request may be used to request the NRF network element to discover UPF network elements with computing power routing capabilities. The discovery request may include, but is not limited to, one or more of the following information: the DNN corresponding to the first session; the S-NSSAI corresponding to the first session; the UE's location information; or indication information 2. Indication information 2 may be used to instruct the NRF network element to discover UPF network elements with computing power routing capabilities.

[0164] S405: The NRF network element sends a discovery response to the SMF network element. In response, the SMF network element receives the discovery response from the NRF network element. The discovery response may be an Nnrf_NFDiscovery_Response message. The discovery response includes the address of the UPF1 network element and, optionally, indication information indicating that the UPF1 network element has computing power routing capabilities.

[0165] The specific implementation process of the above S402-S405 can refer to the content of the above S301 and will not be repeated here.

[0166] S406: The SMF network element sends Request 1 to the UPF1 network element. Correspondingly, the UPF1 network element receives Request 1 from the SMF network element. Request 1 may be used to request the UPF1 network element to report information about the next-hop UPF network element after receiving the data message from the UE. The next-hop UPF network element is the next hop of the UPF1 network element. For example, the UPF1 network element forwards the data message to the next-hop UPF network element. The information about the next-hop UPF network element includes the DNAI corresponding to the next-hop UPF network element and / or the address of the next-hop UPF network element.

[0167] After receiving the discovery response from the NRF network element, the SMF network element can determine that the UPF1 network element has the computing power routing capability, that is, the SMF network element can determine that the UPF1 network element can perform computing power routing forwarding on the data message from the UE to meet the computing power routing requirements of the data message transmitted by the UE on the first session. Therefore, the SMF network element can send request 1 to the UPF1 network element to obtain the next-hop forwarding path information determined by the UPF1 network element when performing computing power routing forwarding on the first data message corresponding to the first application from the UE. The information of the next-hop forwarding path includes the DNAI corresponding to the next-hop UPF network element (that is, the first DNAI) and / or the address of the next-hop UPF network element (that is, the UPF2 network element). The next-hop UPF network element refers to the next hop of the UPF1 network element. For example, the UPF1 network element forwards the data message to the UPF2 network element.

[0168] S407: The SMF network element sends a session establishment response to the UE. Correspondingly, the UE receives the session establishment response from the SMF network element. The session establishment response may be used to indicate that the first session is successfully established.

[0169] S408: The UE sends a first data message corresponding to the first application to the UPF1 network element. Correspondingly, the UPF1 network element receives the first data message corresponding to the first application from the UE.

[0170] The specific implementation process of the above S408 can refer to the content of the above S301 and will not be repeated here.

[0171] S409: The UPF1 network element determines a first DNAI based on at least one DNAI and the resources required by the first application. The at least one DNAI may be a DNAI corresponding to the first application, and the DNAI corresponding to the first application may refer to a DNAI corresponding to the deployment location of the first application. For example, an application server supporting the first application is deployed on the MEC platform corresponding to DNAI#1, and DNAI#1 is a DNAI corresponding to the first application. The resources required for the first application may refer to the computing power resources of the application server supporting the first application deployed on the MEC platform corresponding to the DNAI corresponding to the first application. The first DNAI may be a DNAI corresponding to the UPF2 network element. The UPF2 network element may be the UPF network element required for the next-hop forwarding path determined when the UPF1 network element performs computing power routing forwarding on the first data message corresponding to the first application from the UE, that is, the next-hop UPF network element. The next-hop UPF network element refers to the next hop of the UPF1 network element. For example, the UPF1 network element forwards the data message to the UPF2 network element.

[0172] The specific implementation process of the above S409 can refer to the content of the above S302 and will not be repeated here.

[0173] S410: The UPF1 network element sends the first DNAI and / or the address of the UPF2 network element to the SMF network element. Correspondingly, the SMF network element receives the first DNAI and / or the address of the UPF2 network element from the UPF1 network element.

[0174] Optionally, in the case where the UPF1 network element sends the address of the UPF2 network element to the SMF network element, the above S410 further includes the following steps before the UPF1 network element sends the address of the UPF2 network element to the SMF network element:

[0175] S410a: The UPF1 network element sends a first DNAI to the NRF network element. Correspondingly, the NRF network element receives the first DNAI from the UPF1 network element. The first DNAI may be carried in the Nnrf_NFDiscovery_Request message.

[0176] S410b: The NRF network element sends the address of the UPF2 network element to the UPF1 network element. Correspondingly, the UPF1 network element receives the address of the UPF2 network element from the NRF network element. The address of the UPF2 network element may be carried in the Nnrf_NFDiscovery_Response message.

[0177] Optionally, in the case where the UPF1 network element sends the first DNAI to the SMF network element, the above S409 further includes the following steps after the UPF1 network element sends the first DNAI to the SMF network element:

[0178] S410c: The SMF network element sends a first DNAI to the NRF network element. Correspondingly, the NRF network element receives the first DNAI from the SMF network element. The first DNAI may be carried in the Nnrf_NFDiscovery_Request message.

[0179] S410d: The NRF network element sends the address of the UPF2 network element to the SMF network element. Correspondingly, the SMF network element receives the address of the UPF2 network element from the NRF network element. The address of the UPF2 network element can be carried in the Nnrf_NFDiscovery_Response message.

[0180] S410e: The SMF network element sends the address of the UPF2 network element to the UPF1 network element. Correspondingly, the UPF1 network element receives the address of the UPF2 network element from the SMF network element.

[0181] The above steps S410a-S410e are optional steps, which are indicated by dotted lines in FIG4 .

[0182] S411: The SMF network element sends Request 2 to the UPF2 network element. In response, the UPF2 network element receives Request 2 from the SMF network element. Request 2 may be an N4 session establishment request. Request 2 may be used to request the UPF2 network element to assign a tunnel identifier to a first tunnel. The first tunnel is the tunnel for transmitting data packets between the UPF1 and UPF2 network elements (i.e., the N9 tunnel).

[0183] S412: The UPF2 network element sends a first identifier to the SMF network element. Correspondingly, the SMF network element receives the first identifier from the UPF2 network element. The first identifier can be carried in the N4 session establishment response. The first identifier is the tunnel identifier allocated by the UPF2 network element for the first tunnel.

[0184] S413: The SMF network element sends a session modification request to the UPF1 network element. In response, the UPF1 network element receives the session modification request from the SMF network element. The session modification request may be an N4 session modification request. The session modification request may be used to request the UPF1 network element to assign a tunnel identifier to the first tunnel. The session modification request may include the first identifier.

[0185] S414: The UPF1 network element sends a second identifier to the SMF network element. Correspondingly, the SMF network element receives the second identifier from the UPF1 network element. The second identifier can be carried in the N4 session modification response. The second identifier is the tunnel identifier allocated by the UPF1 network element to the first tunnel.

[0186] S415: The SMF network element sends a second identifier to the UPF2 network element. Correspondingly, the UPF2 network element receives the second identifier from the SMF network element. The second identifier can be carried in the N4 session modification response.

[0187] S416: The UPF1 network element establishes a first tunnel according to the first identifier and the second identifier, and the UPF2 network element establishes a first tunnel according to the first identifier and the second identifier.

[0188] The specific implementation process of the above S410, S410a-S410e, and S411-S416 can refer to the content of the above S302 and will not be repeated here.

[0189] S417: The UPF1 network element sends a first data message to the UPF2 network element. Correspondingly, the UPF2 network element receives the first data message from the UPF1 network element.

[0190] The specific implementation process of the above S417 can refer to the content of the above S303 and will not be repeated here.

[0191] Please refer to Figure 5, which is another flowchart illustrating a communication method provided in an embodiment of the present application. It should be understood that Figure 5 is an exemplary interaction diagram of the method shown in Figure 3, and the present embodiment is not limited thereto. The method shown in Figure 5 can be applied to the network architecture shown in Figure 2A. In the embodiment shown in Figure 5, the first UPF network element is UPF1 and the second UPF network element is UPF3.

[0192] S501: The UE sends a first data message corresponding to a first application to the UPF1 network element. Correspondingly, the UPF1 network element receives the first data message corresponding to the first application from the UE.

[0193] S502: The UPF1 network element sends a first data message to the UPF2 network element. Correspondingly, the UPF2 network element receives the first data message from the UPF1 network element.

[0194] The specific implementation process of the above S501-S502 can refer to the content of Figure 4 above, and will not be repeated here.

[0195] S503: The UPF1 network element determines a first DNAI based on at least one DNAI and the resources required by the first application. The at least one DNAI may be a DNAI corresponding to the first application, and the DNAI corresponding to the first application may refer to a DNAI corresponding to the deployment location of the first application. For example, an application server supporting the first application is deployed on the MEC platform corresponding to DNAI#1, and DNAI#1 is a DNAI corresponding to the first application. The resources required for the first application may refer to the computing power resources of the application server supporting the first application deployed on the MEC platform corresponding to the DNAI corresponding to the first application. The first DNAI may be a DNAI corresponding to the UPF3 network element. The UPF3 network element may be the UPF network element required for the next-hop forwarding path determined when the UPF1 network element performs computing power routing forwarding on the first data message corresponding to the first application from the UE, that is, the next-hop UPF network element. The next-hop UPF network element refers to the next hop of the UPF1 network element. For example, the UPF1 network element forwards the data message to the UPF3 network element.

[0196] The specific implementation process of the above S503 can refer to the content of the above S302 and will not be repeated here.

[0197] S504: The UPF1 network element sends a first DNAI to the SMF network element. Correspondingly, the SMF network element receives the first DNAI from the UPF1 network element.

[0198] The specific implementation process of the above S504 can refer to the content of the above S302 and will not be repeated here.

[0199] S505: The SMF network element sends request 4 to the AF network element, and accordingly, the AF network element receives request 4 from the SMF network element. The request 4 may be an Nsmf_EventExposure_Notify message. The request 4 may be used to request that the context information of the first application corresponding to the second DNAI be migrated to the first DNAI. The second DNAI may be the DNAI corresponding to the UPF2 network element in the above S502. The request 4 may include the first DNAI. Optionally, the request 4 may also include indication information 4. The indication information 4 may be used to indicate that the first DNAI is determined from at least one DNAI corresponding to the first application based on the resources required by the first application.

[0200] S506: The AF network element migrates the context information of the first application corresponding to the second DNAI to the first DNAI.

[0201] S507: The AF network element sends a response 1 to the SMF network element. Correspondingly, the SMF network element receives the response 1 from the AF network element. The response 1 may be an Nsmf_EventExposure_AppRelocationInfo message. The response 1 may be used to indicate that the context information of the first application corresponding to the second DNAI is allowed to be migrated to the first DNAI.

[0202] The specific implementation process of the above S505-S507 can refer to the content of the above S303 and will not be repeated here.

[0203] S508: The SMF network element sends a first DNAI to the NRF network element. Correspondingly, the NRF network element receives the first DNAI from the SMF network element. The first DNAI may be carried in the Nnrf_NFDiscovery_Request message.

[0204] S509: The NRF network element sends the address of the UPF3 network element to the SMF network element. Correspondingly, the SMF network element receives the address of the UPF3 network element from the NRF network element. The address of the UPF3 network element can be carried in the Nnrf_NFDiscovery_Response message.

[0205] S510: The SMF network element sends Request 2 to the UPF3 network element. In response, the UPF2 network element receives Request 2 from the SMF network element. Request 2 may be an N4 session establishment request. Request 2 may be used to request the UPF3 network element to assign a tunnel identifier to a first tunnel. The first tunnel is the tunnel for transmitting data packets between the UPF1 network element and the UPF3 network element (i.e., the N9 tunnel).

[0206] S511: The UPF3 network element sends a first identifier to the SMF network element. Correspondingly, the SMF network element receives the first identifier from the UPF3 network element. The first identifier can be carried in the N4 session establishment response. The first identifier is the tunnel identifier allocated by the UPF3 network element for the first tunnel.

[0207] S512: The SMF network element sends a session modification request to the UPF1 network element. In response, the UPF1 network element receives the session modification request from the SMF network element. The session modification request may be an N4 session modification request. The session modification request may be used to request the UPF1 network element to assign a tunnel identifier to the first tunnel. The session modification request may include the first identifier.

[0208] S513: The UPF1 network element sends a second identifier to the SMF network element. Correspondingly, the SMF network element receives the second identifier from the UPF1 network element. The second identifier can be carried in the N4 session modification response. The second identifier is the tunnel identifier allocated by the UPF1 network element to the first tunnel.

[0209] S514: The SMF network element sends a second identifier to the UPF3 network element. Correspondingly, the UPF3 network element receives the second identifier from the SMF network element. The second identifier may be carried in the N4 session modification response.

[0210] S515: The UPF1 network element establishes a first tunnel according to the first identifier and the second identifier, and the UPF3 network element establishes a first tunnel according to the first identifier and the second identifier.

[0211] The specific implementation process of the above S508-S515 can refer to the content of the above S302 and will not be repeated here.

[0212] S516: The UPF1 network element sends a first data message to the UPF3 network element. Correspondingly, the UPF3 network element receives the first data message from the UPF1 network element.

[0213] The specific implementation process of the above S516 can refer to the content of the above S303 and will not be repeated here.

[0214] Please refer to Figure 6, which is another flowchart illustrating a communication method provided in an embodiment of the present application. It should be understood that Figure 6 is an exemplary interaction diagram of the method shown in Figure 3, and the present embodiment is not limited thereto. The method shown in Figure 6 can be applied to the network architecture shown in Figure 2A. In the embodiment shown in Figure 6, the first UPF network element is UPF1 and the second UPF network element is UPF2.

[0215] S601: UPF1 network element and UPF2 network element periodically synchronize the resources of the MEC platform corresponding to their respective DNAI through the BGP protocol. Optionally, UPF1 network element and UPF2 network element synchronize their respective addresses through the BGP protocol.

[0216] S602: The UPF1 network element sends a registration request to the NRF network element. In response, the NRF network element receives the registration request from the UPF1 network element. The registration request may be an Nnrf_NFManagement_NFRegister Request message. The registration request may include, but is not limited to, one or more of the following information: the DNN corresponding to the UPF1 network element; the S-NSSAI corresponding to the UPF1 network element; or indication information 3. Indication information 3 may be used to indicate that the UPF1 network element has computing power routing capabilities.

[0217] S603: The UE sends a session establishment request to the SMF network element. In response, the SMF network element receives the session establishment request from the UE. The session establishment request may be used to request the SMF network element to establish a first session, which can be used by the UE to access a first application. The session establishment request may include, but is not limited to, one or more of the following information: the DNN corresponding to the first session; the S-NSSAI corresponding to the first session; or indication information 1. Indication information 1 may be used to indicate that the data packets transmitted on the first session have computing power routing requirements.

[0218] S604: The SMF network element sends a discovery request to the NRF network element. In response, the NRF network element receives the discovery request from the SMF network element. The discovery request may be an Nnrf_NFDiscovery_Request message. The discovery request may be used to request the NRF network element to discover UPF network elements with computing power routing capabilities. The discovery request may include, but is not limited to, one or more of the following information: the DNN corresponding to the first session; the S-NSSAI corresponding to the first session; the UE's location information; or indication information 2. Indication information 2 may be used to instruct the NRF network element to discover UPF network elements with computing power routing capabilities.

[0219] S605: The NRF network element sends a discovery response to the SMF network element. In response, the SMF network element receives the discovery response from the NRF network element. The discovery response may be an Nnrf_NFDiscovery_Response message. The discovery response includes the address of the UPF1 network element and, optionally, indication information indicating that the UPF1 network element has computing power routing capabilities.

[0220] The specific implementation process of the above S601-S605 can refer to the content of the above S401-S405 and will not be repeated here.

[0221] S606: The SMF network element sends a session establishment response to the UE. Correspondingly, the UE receives the session establishment response from the SMF network element. The session establishment response may be used to indicate that the first session is successfully established.

[0222] S607: The UE sends a first data message corresponding to the first application to the UPF1 network element. Correspondingly, the UPF1 network element receives the first data message corresponding to the first application from the UE.

[0223] The specific implementation process of the above S606-S607 can refer to the content of the above S407-S408 and will not be repeated here.

[0224] S608: The UPF1 network element determines a first DNAI based on at least one DNAI and the resources required by the first application. The at least one DNAI may be a DNAI corresponding to the first application, and the DNAI corresponding to the first application may refer to a DNAI corresponding to the deployment location of the first application. For example, an application server supporting the first application is deployed on the MEC platform corresponding to DNAI#1, and DNAI#1 is a DNAI corresponding to the first application. The resources required for the first application may refer to the computing power resources of the application server supporting the first application deployed on the MEC platform corresponding to the DNAI corresponding to the first application. The first DNAI may be a DNAI corresponding to the UPF2 network element. The UPF2 network element may be the UPF network element required for the next-hop forwarding path determined when the UPF1 network element performs computing power routing forwarding on the first data message corresponding to the first application from the UE, that is, the next-hop UPF network element. The next-hop UPF network element refers to the next hop of the UPF1 network element. For example, the UPF1 network element forwards the data message to the UPF2 network element.

[0225] Optionally, after the UPF1 network element determines the first DNAI according to the at least one DNAI and the resources required by the first application, the above S608 further includes the following steps:

[0226] S608a: The UPF1 network element sends the first DNAI to the SMF network element. Correspondingly, the SMF network element receives the first DNAI from the UPF1 network element.

[0227] S608b: The SMF network element sends a first DNAI to the NRF network element. Correspondingly, the NRF network element receives the first DNAI from the SMF network element. The first DNAI may be carried in the Nnrf_NFDiscovery_Request message.

[0228] S608c: The NRF network element sends the address of the UPF2 network element to the SMF network element. Correspondingly, the SMF network element receives the address of the UPF2 network element from the NRF network element. The address of the UPF2 network element can be carried in the Nnrf_NFDiscovery_Response message.

[0229] S608d: The SMF network element sends the address of the UPF2 network element to the UPF1 network element. Correspondingly, the UPF1 network element receives the address of the UPF2 network element from the SMF network element.

[0230] Optionally, after the UPF1 network element determines the first DNAI according to the at least one DNAI and the resources required by the first application, the above S608 further includes the following steps:

[0231] S608e: The UPF1 network element sends a first DNAI to the NRF network element. Correspondingly, the NRF network element receives the first DNAI from the UPF1 network element. The first DNAI may be carried in the Nnrf_NFDiscovery_Request message.

[0232] S608f: The NRF network element sends the address of the UPF2 network element to the UPF1 network element. Correspondingly, the UPF1 network element receives the address of the UPF2 network element from the NRF network element. The address of the UPF2 network element can be carried in the Nnrf_NFDiscovery_Response message.

[0233] The above steps S608a-S608f are optional steps, which are indicated by dotted lines in Figure 6. The specific implementation process of the above steps S608 and S608a-S608f can refer to the content of the above step S302 and will not be described in detail.

[0234] S609: UPF1 sends a tunnel establishment request to UPF2. Accordingly, UPF2 receives the tunnel establishment request from UPF1. The tunnel establishment request includes a second identifier, which is a tunnel identifier assigned by UPF1 to a first tunnel. The first tunnel is a tunnel for transmitting data packets between UPF1 and UPF2 (i.e., N9 tunnel).

[0235] S610: The UPF2 network element sends a first identifier to the UPF1 network element. Correspondingly, the UPF1 network element receives the first identifier from the UPF2 network element. The first identifier is a tunnel identifier allocated by the UPF2 network element to the first tunnel.

[0236] S611: The UPF1 network element establishes a first tunnel according to the first identifier and the second identifier, and the UPF2 network element establishes a first tunnel according to the first identifier and the second identifier.

[0237] S612: The UPF1 network element sends a first data message to the UPF2 network element. Correspondingly, the UPF2 network element receives the first data message from the UPF1 network element.

[0238] The specific implementation process of the above S609-S612 can refer to the content of the above S303 and will not be repeated here.

[0239] Please refer to Figure 7, which is another flowchart illustrating a communication method provided in an embodiment of the present application. It should be understood that Figure 7 is an exemplary interaction diagram for the method shown in Figure 3, and the present embodiment is not limited thereto. The method shown in Figure 7 can be applied to the network architecture shown in Figure 2A. In the embodiment shown in Figure 7, the first UPF network element is UPF1 and the second UPF network element is UPF3.

[0240] S701: The UE sends a first data message corresponding to a first application to the UPF1 network element. Correspondingly, the UPF1 network element receives the first data message corresponding to the first application from the UE.

[0241] S702: The UPF1 network element sends a first data message to the UPF2 network element. Correspondingly, the UPF2 network element receives the first data message from the UPF1 network element.

[0242] S703: The UPF1 network element determines a first DNAI based on at least one DNAI and the resources required by the first application. The at least one DNAI may be a DNAI corresponding to the first application, and the DNAI corresponding to the first application may refer to a DNAI corresponding to the deployment location of the first application. For example, an application server supporting the first application is deployed on the MEC platform corresponding to DNAI#1, and DNAI#1 is a DNAI corresponding to the first application. The resources required for the first application may refer to the computing power resources of the application server supporting the first application deployed on the MEC platform corresponding to the DNAI corresponding to the first application. The first DNAI may be a DNAI corresponding to the UPF3 network element. The UPF3 network element may be the UPF network element required for the next-hop forwarding path determined when the UPF1 network element performs computing power routing forwarding on the first data message corresponding to the first application from the UE, that is, the next-hop UPF network element. The next-hop UPF network element refers to the next hop of the UPF1 network element. For example, the UPF1 network element forwards the data message to the UPF3 network element.

[0243] S704: The UPF1 network element sends a first DNAI to the SMF network element. Correspondingly, the SMF network element receives the first DNAI from the UPF1 network element.

[0244] S705: The SMF network element sends request 4 to the AF network element, and accordingly, the AF network element receives request 4 from the SMF network element. The request 4 may be an Nsmf_EventExposure_Notify message. The request 4 may be used to request that the context information of the first application corresponding to the second DNAI be migrated to the first DNAI. The second DNAI may be the DNAI corresponding to the UPF2 network element in the above S702. The request 4 may include the first DNAI. Optionally, the request 4 may also include indication information 4. The indication information 4 may be used to indicate that the first DNAI is determined from at least one DNAI corresponding to the first application based on the resources required by the first application.

[0245] S706: The AF network element migrates the context information of the first application corresponding to the second DNAI to the first DNAI.

[0246] S707: The AF network element sends a response 1 to the SMF network element. Correspondingly, the SMF network element receives the response 1 from the AF network element. The response 1 may be an Nsmf_EventExposure_AppRelocationInfo message. The response 1 may be used to indicate that the context information of the first application corresponding to the second DNAI is allowed to be migrated to the first DNAI.

[0247] Optionally, after the SMF network element receives the response 1 from the AF network element, the above S707 further includes the following steps:

[0248] S707a: The SMF network element sends a first DNAI to the NRF network element. Correspondingly, the NRF network element receives the first DNAI from the SMF network element. The first DNAI may be carried in the Nnrf_NFDiscovery_Request message.

[0249] S707b: The NRF network element sends the address of the UPF3 network element to the SMF network element. Correspondingly, the SMF network element receives the address of the UPF3 network element from the NRF network element. The address of the UPF3 network element can be carried in the Nnrf_NFDiscovery_Response message.

[0250] The above steps S707a-S707b are optional steps, which are indicated by dotted lines in Figure 7. The specific implementation process of the above steps S701-S707 and S707a-S707b can refer to the content of the above steps S501-S509, which will not be described in detail.

[0251] S708: The SMF network element sends instruction information 5 to the UPF1 network element. Accordingly, the UPF1 network element may receive the instruction information 5 from the SMF network element. The instruction information 5 may be used to instruct the UPF1 network element to send a first data packet to the UPF network element corresponding to the first DNAI. Optionally, the instruction information 5 may be used to instruct the UPF1 network element to send the first data packet to the UPF3 network element. The instruction information 5 includes the address of the UPF3 network element.

[0252] The specific implementation process of the above S708 can refer to the content of the above S303 and will not be repeated here.

[0253] S709: UPF1 sends a tunnel establishment request to UPF3. In response, UPF3 receives the tunnel establishment request from UPF1. The tunnel establishment request includes a second identifier, which is the tunnel identifier assigned by UPF1 to the first tunnel. The first tunnel is the tunnel for transmitting data packets between UPF1 and UPF3 (i.e., N9 tunnel).

[0254] Optionally, before the UPF1 network element sends the tunnel establishment request to the UPF3 network element, the above S709 further includes the following steps:

[0255] S709a: The UPF1 network element sends a first DNAI to the NRF network element. Correspondingly, the NRF network element receives the first DNAI from the UPF1 network element. The first DNAI may be carried in the Nnrf_NFDiscovery_Request message.

[0256] S709b: The NRF network element sends the address of the UPF3 network element to the UPF1 network element. Correspondingly, the UPF1 network element receives the address of the UPF3 network element from the NRF network element. The address of the UPF3 network element can be carried in the Nnrf_NFDiscovery_Response message.

[0257] The above steps S709a-S709b are optional steps, which are indicated by dotted lines in Figure 7. The specific implementation process of the above steps S709a-S709b can refer to the content of the above step S302 and will not be described in detail.

[0258] S710: The UPF3 network element sends a first identifier to the UPF1 network element. Correspondingly, the UPF1 network element receives the first identifier from the UPF3 network element. The first identifier is a tunnel identifier allocated by the UPF3 network element to the first tunnel.

[0259] S711: The UPF1 network element establishes a first tunnel according to the first identifier and the second identifier, and the UPF3 network element establishes a first tunnel according to the first identifier and the second identifier.

[0260] S712: The UPF1 network element sends a first data message to the UPF3 network element. Correspondingly, the UPF3 network element receives the first data message from the UPF1 network element.

[0261] The specific implementation process of the above S709-S712 can refer to the content of the above S609-S612 and will not be repeated here.

[0262] Please refer to Figure 8, which is another flowchart illustrating a communication method provided in an embodiment of the present application. It should be understood that Figure 8 is an exemplary interaction diagram for the method shown in Figure 3, and the present embodiment is not limited thereto. The method shown in Figure 8 can be applied to the network architecture shown in Figure 2B. In the embodiment shown in Figure 8, the first UPF network element is UPF1 and the second UPF network element is UPF2.

[0263] S801: UPF1 network element and UPF2 network element periodically synchronize the resources of the MEC platform corresponding to their respective DNAI through the BGP protocol. Optionally, UPF1 network element and UPF2 network element periodically synchronize their respective addresses through the BGP protocol.

[0264] S802: The UPF1 network element sends a registration request to the NRF network element. In response, the NRF network element receives the registration request from the UPF1 network element. The registration request may be an Nnrf_NFManagement_NFRegister Request message. The registration request may include, but is not limited to, one or more of the following information: the DNN corresponding to the UPF1 network element; the S-NSSAI corresponding to the UPF1 network element; or indication information 3. Indication information 3 may be used to indicate that the UPF1 network element has computing power routing capabilities.

[0265] S803: The UE sends a session establishment request to the SMF network element. In response, the SMF network element receives the session establishment request from the UE. The session establishment request may be used to request the SMF network element to establish a first session, which can be used by the UE to access a first application. The session establishment request may include, but is not limited to, one or more of the following information: the DNN corresponding to the first session; the S-NSSAI corresponding to the first session; or indication information 1. Indication information 1 may be used to indicate that the data packets transmitted on the first session have computing power routing requirements.

[0266] S804: The SMF network element sends a discovery request to the NRF network element. In response, the NRF network element receives the discovery request from the SMF network element. The discovery request may be an Nnrf_NFDiscovery_Request message. This discovery request may be used to request the NRF network element to discover UPF network elements with computing power routing capabilities. The discovery request may include, but is not limited to, one or more of the following information: the DNN corresponding to the first session; the S-NSSAI corresponding to the first session; the UE's location information; or indication information 2. Indication information 2 may be used to instruct the NRF network element to discover UPF network elements with computing power routing capabilities.

[0267] S805: The NRF network element sends a discovery response to the SMF network element. In response, the SMF network element receives the discovery response from the NRF network element. The discovery response may be an Nnrf_NFDiscovery_Response message. The discovery response includes the address of the UPF1 network element and, optionally, indication information indicating that the UPF1 network element has computing power routing capabilities.

[0268] S806: The SMF network element sends Request 1 to the UPF1 network element. Correspondingly, the UPF1 network element receives Request 1 from the SMF network element. Request 1 may be used to request the UPF1 network element to report information about the next-hop UPF network element after receiving a data message from the UE. The next-hop UPF network element is the next hop of the base station. For example, the base station forwards the data message to the next-hop UPF network element. The information about the next-hop UPF network element includes the DNAI corresponding to the next-hop UPF network element and / or the address of the next-hop UPF network element.

[0269] After receiving the discovery response from the NRF network element, the SMF network element can determine that the UPF1 network element has the computing power routing capability, that is, the SMF network element can determine that the UPF1 network element can perform computing power routing forwarding on the data message from the UE to meet the computing power routing requirements of the data message transmitted by the UE on the first session. Therefore, the SMF network element can send a request 1 to the UPF1 network element to obtain the next-hop forwarding path information determined by the UPF1 network element when performing computing power routing forwarding on the first data message corresponding to the first application from the UE. The information of the next-hop forwarding path includes the DNAI corresponding to the next-hop UPF network element (that is, the first DNAI) and / or the address of the next-hop UPF network element (that is, the UPF2 network element). The next-hop UPF network element refers to the next hop of the base station. For example, the base station no longer forwards the data message to the UPF1 network element, but forwards it to the UPF2 network element.

[0270] S807: The SMF network element sends a session establishment response to the UE. Correspondingly, the UE receives the session establishment response from the SMF network element. The session establishment response may be used to indicate that the first session is successfully established.

[0271] S808: The UE sends a first data message corresponding to the first application to the UPF1 network element. Correspondingly, the UPF1 network element receives the first data message for accessing the first application from the UE.

[0272] S809: The UPF1 network element determines a first DNAI based on at least one DNAI and the resources required by the first application. The at least one DNAI may be a DNAI corresponding to the first application, and the DNAI corresponding to the first application may refer to a DNAI corresponding to the deployment location of the first application. For example, an application server supporting the first application is deployed on the MEC platform corresponding to DNAI#1, and DNAI#1 is a DNAI corresponding to the first application. The resources required for the first application may refer to the computing power resources of the application server supporting the first application deployed on the MEC platform corresponding to the DNAI corresponding to the first application. The first DNAI may be a DNAI corresponding to the UPF2 network element. The UPF2 network element may be the UPF network element required for the next-hop forwarding path determined when the UPF1 network element performs computing power routing forwarding on the first data message corresponding to the first application from the UE, that is, the next-hop UPF network element. The next-hop UPF network element refers to the next hop of the base station. For example, the base station no longer forwards the data message to the UPF1 network element, but forwards it to the UPF2 network element.

[0273] S810: The UPF1 network element sends the first DNAI and / or the address of the UPF2 network element to the SMF network element. Correspondingly, the SMF network element receives the first DNAI and / or the address of the UPF2 network element from the UPF1 network element.

[0274] Optionally, in the case where the UPF1 network element sends the address of the UPF2 network element to the SMF network element, the above S810 further includes the following steps before the UPF1 network element sends the address of the UPF2 network element to the SMF network element:

[0275] S810a: The UPF1 network element sends a first DNAI to the NRF network element. Correspondingly, the NRF network element receives the first DNAI from the UPF1 network element.

[0276] S810b: The NRF network element sends the address of the UPF2 network element to the UPF1 network element. Correspondingly, the UPF1 network element receives the address of the UPF2 network element from the NRF network element.

[0277] Optionally, in the case where the UPF1 network element sends the first DNAI to the SMF network element, the above S810 further includes the following steps after the UPF1 network element sends the first DNAI to the SMF network element:

[0278] S810c: The SMF network element sends a first DNAI to the NRF network element. Correspondingly, the NRF network element receives the first DNAI from the SMF network element.

[0279] S810d: The NRF network element sends the address of the UPF2 network element to the SMF network element. Correspondingly, the SMF network element receives the address of the UPF2 network element from the NRF network element.

[0280] S810e: The SMF network element sends the address of the UPF2 network element to the UPF1 network element. Correspondingly, the UPF1 network element receives the address of the UPF2 network element from the SMF network element.

[0281] The above steps S810a-S810e are optional steps, which are indicated by dotted lines in Figure 8. The specific implementation process of the above steps S801-S810 and S810a-S810e can refer to the contents of the above steps S401-S410 and S410a-S410e, and will not be repeated here.

[0282] S811: The SMF network element sends Request 3 to the UPF2 network element. In response, the UPF2 network element receives Request 3 from the SMF network element. Request 3 may be an N4 session establishment request. Request 3 may be used to request the UPF2 network element to allocate a tunnel identifier for a second tunnel, which is a tunnel for transmitting data packets between the base station and the UPF2 network element (i.e., an N3 tunnel).

[0283] S812: The UPF2 network element sends a third identifier to the SMF network element. In response, the SMF network element receives the third identifier from the UPF2 network element. The third identifier can be carried in the N4 session establishment response. The third identifier is the tunnel identifier allocated by the UPF2 network element for the second tunnel.

[0284] S813: The SMF network element sends a third identifier to the AMF network element. Correspondingly, the AMF network element receives the third identifier from the SMF network element. The third identifier can be carried in the N2 SM information of the Namf_Communication_N1N2MessageTransfer message.

[0285] S814: The AMF network element sends a third identifier to the base station. Accordingly, the base station receives the third identifier from the AMF network element. The third identifier may be carried in the N2 SM information of the N2 message.

[0286] S815: The base station sends a fourth identifier to the AMF network element. In response, the AMF network element receives the fourth identifier from the base station. The fourth identifier is the tunnel identifier assigned by the base station for the second tunnel. The fourth identifier may be carried in the N2 SM information of the N2 message.

[0287] S816: The AMF network element sends a fourth identifier to the SMF network element. Correspondingly, the SMF network element receives the fourth identifier from the AMF network element. The fourth identifier may be carried in the N2 SM information of the Nsmf_PDUSession_UpdateSMContext message.

[0288] S817: The SMF network element sends a fourth identifier to the UPF2 network element. Correspondingly, the UPF2 network element receives the fourth identifier from the SMF network element. The fourth identifier can be carried in the N4 session modification request.

[0289] S818: The UPF2 network element establishes a second tunnel according to the third identifier and the fourth identifier, and the base station establishes a second tunnel based on the third identifier and the fourth identifier.

[0290] The specific implementation process of the above S811-S818 can refer to the content of the above S302 and will not be repeated here.

[0291] S819: The UE sends a first data message to the base station. Correspondingly, the base station receives the first data message from the UE.

[0292] S820: The base station sends a first data message to the UPF2 network element. Correspondingly, the UPF2 network element receives the first data message from the base station.

[0293] The specific implementation process of the above S819-S880 can refer to the content of the above S302 and will not be repeated here.

[0294] Figure 9 shows a structural diagram of a communication device provided in an embodiment of the present application. The communication device 900 can be the first UPF network element or the circuit system of the first UPF network element described in the embodiment shown in any one of the figures in Figures 3 to 8, which is used to implement the method corresponding to the first UPF network element in the above method embodiment. Alternatively, the communication device 900 can be the SMF network element or the circuit system of the SMF network element described in the embodiment shown in any one of the figures in Figures 4 to 8, which is used to implement the method corresponding to the SMF network element in the above method embodiment. Alternatively, the communication device 900 can be the second UPF network element or the circuit system of the second UPF network element described in the embodiment shown in any one of the figures in Figures 3 to 8, which is used to implement the method corresponding to the second UPF network element in the above method embodiment. Alternatively, the communication device 900 can be the NRF network element or the circuit system of the NRF network element described in the embodiment shown in any one of the figures in Figures 4 to 8, which is used to implement the method corresponding to the NRF network element in the above method embodiment. Alternatively, the communication device 900 may be the AF network element or the circuit system of the AF network element described in the embodiment shown in any one of Figures 5 or 7, for implementing the method corresponding to the AF network element in the above method embodiment. Alternatively, the communication device 900 may be the AMF network element or the circuit system of the AMF network element described in the embodiment shown in Figure 8, for implementing the method corresponding to the AMF network element in the above method embodiment. Alternatively, the communication device 900 may be the base station or the circuit system of the base station described in the embodiment shown in any one of Figures 8-8, for implementing the method corresponding to the base station in the above method embodiment. For example, one circuit system is a chip system.

[0295] The communication device 900 includes at least one processor 901. Processor 901 can be used for internal processing of the device to implement certain control processing functions. Optionally, processor 901 includes instructions. Optionally, processor 901 can store data. Optionally, different processors can be independent devices, located in different physical locations, or on different integrated circuits. Optionally, different processors can be integrated into one or more processors, for example, on one or more integrated circuits.

[0296] Optionally, the communication device 900 includes one or more memories 903 for storing instructions. Optionally, data may also be stored in the memories 903. The processor and memory may be provided separately or integrated together.

[0297] Optionally, the communication device 900 includes a communication line 902 and at least one communication interface 904. Since the memory 903, the communication line 902 and the communication interface 904 are all optional, they are indicated by dotted lines in FIG9 .

[0298] Optionally, the communication device 900 may further include a transceiver and / or an antenna. The transceiver may be used to send information to or receive information from other devices. The transceiver may be referred to as a transceiver, a transceiver circuit, an input / output interface, etc., and is used to implement the transceiver function of the communication device 900 through the antenna. Optionally, the transceiver includes a transmitter and a receiver. For example, the transmitter may be used to generate a radio frequency signal from a baseband signal, and the receiver may be used to convert the radio frequency signal into a baseband signal.

[0299] The processor 901 may include a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0300] Communication link 902 may include a pathway for transmitting information between the aforementioned components.

[0301] The communication interface 904 uses any transceiver or other device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), wired access network, etc.

[0302] The memory 903 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 903 may exist independently and be connected to the processor 901 via the communication line 902. Alternatively, the memory 903 may be integrated with the processor 901.

[0303] The memory 903 is used to store computer-executable instructions for executing the solution of the present application, and the execution is controlled by the processor 901. The processor 901 is used to execute the computer-executable instructions stored in the memory 903, thereby implementing the steps performed by the first UPF network element, SMF network element, second UPF network element, NRF network element, AF network element, AMF network element, or base station described in the embodiment shown in any one of Figures 3 to 8.

[0304] Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.

[0305] In a specific implementation, as an embodiment, the processor 901 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 9 .

[0306] In a specific implementation, as an embodiment, the communication device 900 may include multiple processors, such as the processor 901 and the processor 905 in FIG9 . Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0307] When the device shown in Figure 9 is a chip, for example, a chip of a first UPF network element, a chip of an SMF network element, a chip of a second UPF network element, a chip of an NRF network element, a chip of an AF network element, a chip of an AMF network element, or a chip of a base station, the chip includes a processor 901 (and may also include a processor 905), a communication line 902 and a communication interface 904, and optionally, may include a memory 903. Specifically, the communication interface 904 may be an input interface, a pin or a circuit, etc. The memory 903 may be a register, a cache, etc. The processor 901 and the processor 905 may be a general-purpose CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of the program of the communication method of any of the above embodiments.

[0308] The embodiment of the present application can divide the functional modules of the device according to the above-mentioned method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation. For example, in the case of dividing each functional module according to each function, Figure 10 shows a schematic diagram of a device. The device 1000 can be the first UPF network element, SMF network element, second UPF network element, NRF network element, AF network element, AMF network element, or base station involved in the above-mentioned various method embodiments, or the device 1000 can be the chip of the first UPF network element, the chip of the SMF network element, the chip of the second UPF network element, the chip of the NRF network element, the chip of the AF network element, the chip of the AMF network element, or the chip of the base station involved in the above-mentioned various method embodiments. The apparatus 1000 includes a sending unit 1001 , a processing unit 1002 and a receiving unit 1003 .

[0309] It should be understood that the device 1000 can be used to implement the steps performed by the first UPF network element, SMF network element, second UPF network element, NRF network element, AF network element, AMF network element, or base station in the communication method of the embodiment of the present application. The relevant features can refer to the embodiments shown in any of the figures in Figures 3 to 8 above, and will not be repeated here.

[0310] Optionally, the functions / implementation processes of the sending unit 1001, the receiving unit 1003, and the processing unit 1002 in FIG10 may be implemented by the processor 901 in FIG9 calling computer-executable instructions stored in the memory 903. Alternatively, the functions / implementation processes of the processing unit 1002 in FIG10 may be implemented by the processor 901 in FIG9 calling computer-executable instructions stored in the memory 903, and the functions / implementation processes of the sending unit 1001 and the receiving unit 1003 in FIG10 may be implemented by the communication interface 904 in FIG9.

[0311] Optionally, when the device 1000 is a chip or a circuit, the functions / implementation processes of the sending unit 1001 and the receiving unit 1003 can also be implemented through pins or circuits.

[0312] The present application also provides a computer-readable storage medium, which stores a computer program or instruction. When the computer program or instruction is executed, the method performed by the first UPF network element, SMF network element, second UPF network element, NRF network element, AF network element, AMF network element, or base station in the aforementioned method embodiment is implemented. In this way, the functions described in the above embodiments can be implemented in the form of software functional units and sold or used as independent products. Based on this understanding, the technical solution of the present application can essentially or in other words, the part that contributes or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. Storage media include: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

[0313] The present application also provides a computer program product, which includes: computer program code, which, when running on a computer, enables the computer to execute the method performed by the first UPF network element, SMF network element, second UPF network element, NRF network element, AF network element, AMF network element, or base station in any of the aforementioned method embodiments.

[0314] An embodiment of the present application also provides a processing device, including a processor and an interface; the processor is used to execute the method executed by the first UPF network element, SMF network element, second UPF network element, NRF network element, AF network element, AMF network element, or base station involved in any of the above method embodiments.

[0315] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. 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 computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0316] The various illustrative logic units and circuits described in the embodiments of the present application can be implemented or operated by a general-purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general-purpose processor can be a microprocessor, and optionally, the general-purpose processor can also be any conventional processor, controller, microcontroller or state machine. The processor can also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration.

[0317] The steps of the methods or algorithms described in the embodiments of the present application can be directly embedded in hardware, software units executed by a processor, or a combination of the two. The software unit can be stored in RAM, flash memory, ROM, erasable programmable read-only memory (EPROM), EEPROM, registers, hard disks, removable disks, CD-ROMs, or other storage media in any form known in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from the storage medium and write information to the storage medium. Alternatively, the storage medium can also be integrated into the processor. The processor and storage medium can be provided in an ASIC, which can be provided in a terminal device. Alternatively, the processor and storage medium can also be provided in different components in the terminal device.

[0318] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0319] The contents of the various embodiments of this application can refer to each other. If there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0320] It can be understood that in the embodiment of the present application, the first UPF network element, the SMF network element, the second UPF network element, the NRF network element, the AF network element, the AMF network element, or the base station can perform some or all of the steps in the embodiment of the present application. These steps or operations are only examples. In the embodiment of the present application, other operations or variations of various operations can also be performed. In addition, the various steps can be performed in a different order than those presented in the embodiment of the present application, and it is possible that not all operations in the embodiment of the present application need to be performed.

Claims

1. A communication method, characterized in that: Applied to a first user plane function network element, the method includes: Receiving a first data message from a terminal device, where the first data message corresponds to a first application; Determine a second user plane function network element according to at least one data network access identifier DNAI and resources required by the first application, wherein the at least one DNAI is a DNAI corresponding to the first application, and the second user plane function network element corresponds to a first DNAI in the at least one DNAI; Send the first data packet to the second user plane function network element.

2. The method according to claim 1, characterized in that Determine the second user plane function network element, including: The first DNAI is sent to the first network element, and the address of the second user plane function network element is received from the first network element.

3. The method according to claim 2, characterized in that The first network element includes a session management function network element or a network storage function network element.

4. The method according to claim 1, characterized in that Determine the second user plane function network element, including: The address of the second user plane function network element is determined according to the address of the user plane function network element corresponding to the at least one DNAI, and the user plane function network element corresponding to the at least one DNAI includes the second user plane function network element.

5. The method according to claim 4, characterized in that The method further comprises: Send the address of the second user plane function network element to the session management function network element.

6. The method according to claim 3 or 5, characterized in that The method further comprises: Receive first indication information from the session management function network element, where the first indication information is used to instruct the first user plane function network element to send a data message to the second user plane function network element.

7. The method according to claim 3 or 5, characterized in that The method further comprises: receiving a session modification request from the session management function network element, the session modification request being used to request the first user plane function network element to allocate a tunnel identifier for a first tunnel, the first tunnel being a tunnel for transmitting data messages between the first user plane function network element and the second user plane function network element, the session modification request including a first identifier, the first identifier being a tunnel identifier allocated by the second user plane function network element to the first tunnel; Sending a second identifier to the session management function network element, where the second identifier is a tunnel identifier allocated by the first user plane function network element to the first tunnel; The first tunnel is established according to the first identifier and the second identifier.

8. The method according to any one of claims 2 to 6, characterized in that: The method further comprises: Sending a tunnel establishment request to the second user plane function network element, the tunnel establishment request including a second identifier, where the second identifier is a tunnel identifier allocated by the first user plane function network element to a first tunnel, where the first tunnel is a tunnel between the first user plane function network element and the second user plane function network element for transmitting data packets; receiving a first identifier from the second user plane function network element, where the first identifier is a tunnel identifier allocated by the second user plane function network element to the first tunnel; The first tunnel is established according to the first identifier and the second identifier.

9. The method according to any one of claims 1 to 8, characterized in that: The method further comprises: Receive a first request from a session management function network element, where the first request is used to request the first user plane function network element to report first information after receiving a data packet from the terminal device, where the first information includes a DNAI and / or an address, and the first information is used to determine a second user plane function network element.

10. The method according to any one of claims 1 to 9, characterized in that: The method further comprises: Send a registration request to the network storage function network element, where the registration request includes one or more of the following information: The data network name DNN corresponding to the first user plane functional network element; The single network slice selection auxiliary information S-NSSAI corresponding to the first user plane function network element; or, The second indication information is used to indicate that the first user plane function network element has computing power routing capability, and the computing power routing capability is used by the first user plane function network element to forward the data message of the application according to the resources required by the application.

11. A communication method, characterized in that: Applied to a session management function network element, the method comprises: Sending a first request to a first user plane function network element, the first request being used to request the first user plane function network element to report first information after receiving a data message from a terminal device, the first information including a DNAI and / or an address, the first information being used to confirm Determine a second user plane function network element, wherein the data message corresponds to the first application; Receive a first DNAI from the first user plane function network element and / or an address of the second user plane function network element, where the first DNAI is a DNAI in at least one DNAI, the at least one DNAI is a DNAI corresponding to the first application, and the second user plane function network element corresponds to the first DNAI; A tunnel for transmitting data packets is established according to the address of the first DNAI and / or the second user plane functional network element.

12. The method according to claim 11, characterized in that The method further comprises: Sending the first DNAI to the network storage function network element, Receiving an address of the second user plane function network element from the network storage function network element; Send the address of the second user plane function network element to the first user plane function network element.

13. The method according to claim 11 or 12, characterized in that: The method further comprises: Sending a second request to an application function network element, where the second request is used to request that context information of the first application corresponding to a second DNAI be migrated to the first DNAI, where the second DNAI is a DNAI other than the first DNAI in the at least one DNAI, the context information includes historical information of the first application, and the second request includes the first DNAI; Receive a first response from the application function network element, where the first response is used to indicate that the context information of the first application corresponding to the second DNAI is allowed to be migrated to the first DNAI.

14. The method according to claim 13, characterized in that The second request also includes third indication information, used to indicate that the first DNAI is determined from the at least one DNAI based on the resources required by the first application.

15. The method according to claim 13 or 14, characterized in that The method further comprises: Sending first indication information to the first user plane function network element, where the first indication information is used to instruct the first user plane function network element to send a data message to the second user plane function network element.

16. The method according to any one of claims 11 to 15, characterized in that: Establishing a tunnel for transmitting a data message according to the address of the first DNAI and / or the second user plane function network element, including: establishing a first tunnel according to the address of the first DNAI and / or the second user plane function network element, where the first tunnel is a tunnel for transmitting data packets between the first user plane function network element and the second user plane function network element; or, A second tunnel is established according to the address of the first DNAI and / or the second user plane function network element, and the second tunnel is a tunnel for transmitting data packets between the access network device and the second user plane function network element.

17. The method according to claim 16, characterized in that Establishing a first tunnel according to the first DNAI and / or the address of the second user plane function network element includes: Sending a third request to the second user plane function network element, where the third request is used to request the second user plane function network element to allocate a tunnel identifier for the first tunnel; receiving a first identifier from the second user plane function network element, where the first identifier is a tunnel identifier allocated by the second user plane function network element to the first tunnel; Sending a session modification request to the first user plane function network element, where the session modification request is used to request the first user plane function network element to allocate a tunnel identifier for the first tunnel, and the session modification request includes the first identifier; receiving a second identifier from the first user plane function network element, where the second identifier is a tunnel identifier allocated by the first user plane function network element to the first tunnel; Send the second identifier to the second user plane function network element.

18. The method according to claim 16, characterized in that Establishing a second tunnel according to the first DNAI and / or the address of the second user plane function network element includes: Sending a fourth request to the second user plane function network element, where the fourth request is used to request the second user plane function network element to allocate a tunnel identifier for the second tunnel; receiving a third identifier from the second user plane function network element, where the third identifier is a tunnel identifier allocated by the second user plane function network element to the second tunnel; Sending the third identifier to an access and mobility management function network element; receiving a fourth identifier from the access and mobility management function network element, where the fourth identifier is a tunnel identifier allocated by the access network device to the second tunnel; Send the fourth identifier to the second user plane function network element.

19. The method according to any one of claims 11 to 18, characterized in that: The method further comprises: receiving a session establishment request from the terminal device, the session establishment request being used to request the session management function network element to establish a first session, the first session being used for the terminal device to access the first application; Sending a discovery request to a network storage function network element, wherein the discovery request is used to request the network storage function network element to discover a user plane function network element with computing power routing capability, wherein the computing power routing capability is used by the user plane function network element to forward data packets of the application according to resources required by the application; Receive a discovery response from the network storage function network element, where the discovery response is used to indicate that the first user plane function network element has the computing power routing capability.

20. The method of claim 19, wherein: The session establishment request includes one or more of the following information: The DNN corresponding to the first session; The S-NSSAI corresponding to the first session; or The fourth indication information is used to indicate that the data message transmitted on the first session has a computing power routing requirement.

21. The method of claim 20, wherein: The discovery request includes one or more of the following information: The DNN corresponding to the first session; The S-NSSAI corresponding to the first session; The location information of the terminal device; or, The fifth indication information is used to instruct the network storage function network element to discover the user plane function network element with the computing power routing capability.

22. A communication device, characterized in that: The method comprises a module for executing the method as claimed in any one of claims 1 to 10, or a module for executing the method as claimed in any one of claims 11 to 21.

23. A communication device, characterized in that: It includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor implements the method as described in any one of claims 1 to 10 or the method as described in any one of claims 11 to 21 through a logic circuit or by executing code instructions.

24. A communication device, characterized in that: include: Memory for storing computer programs; A processor, configured to call and run the computer program from the memory to implement the method according to any one of claims 1 to 10, or to implement the method according to any one of claims 11 to 21.

25. A chip system, characterized in that: include: Memory for storing computer programs; A processor, configured to call and run the computer program from the memory, so that a device equipped with the chip system executes the method as claimed in any one of claims 1 to 10, or executes the method as claimed in any one of claims 11 to 21.

26. A computer program product, characterized in that The invention comprises a computer program, which, when executed by a communication device, implements the method according to any one of claims 1 to 21.

27. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or an instruction, and when the computer program or the instruction is executed by the communication device, the method according to any one of claims 1 to 21 is implemented.

28. A communication system, characterized in that: include: A first user plane function network element, configured to execute the method according to any one of claims 1 to 10; A session management function network element, configured to execute the method as claimed in any one of claims 11 to 21.

Images