Communication method and apparatus

Abstract

The present application relates to the technical field of wireless communications. Provided are a communication method and apparatus. The method comprises: a session management network element acquiring a data network access identifier of a first service, and determining that the first service is a service of a first type, wherein the service of the first type is a service meeting a quality-of-service and / or position deployment requirement; the session management network element instructing a first network element to create or update a processing rule for the first service of a terminal, wherein the processing rule for the first service instructs that the session management network element be notified when the terminal initiates the first service; and the session management network element receiving first notification information from the first network element, wherein the first notification information indicates that the terminal initiates the first service. In the present application, when the distance between the position of an application server corresponding to a first service and the position where a terminal is located is relatively large, a first network element may also determine that a service initiated by the terminal hits a processing rule, and then send a first notification message to a session management network element, so as to notify the session management network element to process the service initiated by the terminal.

Description

A communication method and apparatus

[0001] Cross-reference to Related Applications

[0002] This application claims priority to the Chinese Patent Application No. 202410612368.7, filed on May 16, 2024, and entitled "A communication method and apparatus", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] The present application relates to the technical field of wireless communication, and in particular to a communication method and apparatus. BACKGROUND

[0004] In an edge computing (EC) deployment scenario, some services can be provided by multiple edge application servers (EASs) deployed at the edge of a network. The multiple EASs deployed at the edge of the network can provide the same services and content, but different EASs can have different address information, for example, different IP addresses of different EASs.

[0005] When a terminal needs to access a certain service, a session management function (SMF) network element can detect an EAS close to the terminal corresponding to a current service executed by the terminal, and can assist the terminal to access the EAS. However, when the terminal accesses an EAS corresponding to a service far away from the terminal, the SMF cannot perceive, so that the terminal cannot access the EAS far away that can execute the current service. SUMMARY

[0006] The present application provides a communication method and apparatus to ensure that the SMF network element can guarantee the terminal to access the EAS when the terminal accesses the EAS corresponding to a service far away from the terminal.

[0007] In a first aspect, an embodiment of the present application provides a communication method, which can be applied to a session management network element or a chip in a session management network element. Taking the method applied to a session management network element as an example, the method comprises: a session management network element acquires a data network access identifier of a first service, and determines that the first service is a first type of service, the first type of service being a service meeting a quality of service and / or a deployment location requirement; the session management network element instructs a first network element to create or update a processing rule of the first service for a terminal, the processing rule of the first service instructing the terminal to notify the session management network element when initiating the first service; and the session management network element receives first notification information from the first network element, the first notification information indicating that the terminal initiates the first service.

[0008] The first service corresponds to a data network access identifier that does not include the data network access identifier corresponding to the terminal, or the data network access identifier corresponding to the first service is different from the data network access identifier corresponding to the terminal, or the first network element retains the processing rule of the first service when the terminal moves; or the first network element does not update or delete the processing rule of the first service when the terminal moves.

[0009] Optionally, the terminal initiating the first service can include: the terminal sending a DNS request message, the DNS request message including the FQDN corresponding to the first service; or the DNS server sending a DNS reply message to the terminal, the DNS reply message including the EAS address information corresponding to the first service; or the terminal sending data (or a data packet or a data stream), the data (or the data packet or the data stream) including the address information of the application server corresponding to the first service.

[0010] Through the above method, when the session management network element instructs the first network element to create or update the processing rule of the first service for the terminal, the location of the application server corresponding to the first service and the location where the terminal is located can be far away from each other. In this way, when the terminal initiates a service of a server deployed in a far location, the first network element can also determine that the service initiated by the terminal hits the processing rule, and thus sends a first notification message to the SMF network element, to notify the SMF network element to process the service initiated by the terminal.

[0011] In a possible design, the session management network element determines that the terminal supports the first type of service, or determines that the terminal is authorized to access the first type of service.

[0012] Through the above design, since the first type of service is a service that meets the quality of service and / or deployment location requirement, in a case where the session management network element determines that the terminal supports or is authorized to access the type of service, the session management network element can perceive the first type of service initiated by the terminal.

[0013] Optionally, the processing rule of the first service includes full address domain name (FQDN) information corresponding to the first service; or the processing rule of the first service includes address information of an application server corresponding to the first service.

[0014] In a possible design, the session management network element receives first indication information from the second network element, where the first indication information is used to indicate that the first service is a first type of service; or the session management network element determines, according to a data network access identifier of the first service, that the first service is a first type of service; or the session management network element determines, according to server deployment information of the first service sent by the second network element, that the first service is a first type of service.

[0015] Through the above design, the session management network element can flexibly determine the first service as the first type of service in multiple different ways.

[0016] In a possible design, the session management network element receives second notification information from the first network element, where the second notification information is used to indicate address information of an application server corresponding to the first service; the session management network element determines at least one first candidate user plane network element corresponding to the address information of the application server, and selects a first user plane network element from the at least one first candidate user plane network element according to a time delay between each first candidate user plane network element and the application server corresponding to the first service; and the session management network element configures a user plane path corresponding to the first service according to the first user plane network element.

[0017] Through the above design, the session management network element can reasonably configure the user plane path corresponding to the first service according to the time delay between each first candidate user plane network element and the application server; for example, the session management network element can select the first candidate user plane network element with the lowest time delay as the first user plane network element, and the user plane path configured based on the first user plane network element can ensure that data sent by the terminal to the application server has a shorter routing time in the Internet network, thereby improving the reliability of the terminal service.

[0018] In a possible design, the session management network element determines at least one data network access node corresponding to the address information of the application server according to server deployment information of the first service sent by the second network element; the session management network element determines a target data network access node from the at least one data network access node; and the session management network element determines a user plane network element corresponding to the target data network access node as the at least one first candidate user plane network element.

[0019] Through the above design, the session management network element can accurately determine the first candidate user plane network element according to the server deployment information of the first service, thereby accurately configuring the user plane path corresponding to the first service.

[0020] In a possible design, the session management network element determines a target data network access node from the at least one data network access node according to a time delay between each data network access node and the application server corresponding to the first service.

[0021] Through the above design, the session management network element can reasonably select the target data network access node according to the time delay between the data network access node and the application server.

[0022] In a possible design, the first type of service includes any of the following:

[0023] a service requiring low N6 latency; wherein requiring low N6 latency can also be referred to as having requirement on N6 delay, or requiring guaranteeing N6 latency, or considering N6 latency, or requiring considering N6 latency, or indicating considering N6 latency, or N6 latency based EAS discovery, or indicating communication (or routing) requirement of local data network and central data network;

[0024] a service deployed in a cloud server or a remote server;

[0025] a service requiring low N6 latency and deployed in a cloud server or a remote server;

[0026] a service requiring guaranteeing QoS; wherein requiring guaranteeing QoS can also be referred to as having requirement on QoS, or considering QoS, or requiring considering QoS, or indicating considering QoS, or QoS based EAS discovery;

[0027] a service requiring guaranteeing QoS and deployed in a cloud server or a remote server.

[0028] In a second aspect, an embodiment of the present application provides a communication method, which can be applied to a session management network element or a chip in the session management network element. Taking the method applied to the session management network element as an example, the method comprises the following steps: a session management network element acquires a data network access identifier of a first service, and determines that the first service is a first type of service, wherein the first type of service is a service meeting a quality of service requirement and / or a deployment location requirement; the session management network element sends second indication information to a second user plane network element, wherein the second indication information is used to indicate a split rule of the first service of a terminal.

[0029] Optionally, the data network access identifier corresponding to the first service does not include a data network access identifier corresponding to the terminal, or the data network access identifier corresponding to the first service is different from the data network access identifier corresponding to the terminal, or the first network element retains the split rule of the first service when the terminal moves; or the first network element does not update or delete the split rule of the first service when the terminal moves.

[0030] Through the above method, the SMF network element can create or update the split rule for the terminal in advance, the split rule includes the split rule of the first service, and the location of the application server corresponding to the first service and the location of the terminal can be far away from each other. In this way, when the terminal initiates a service of a server deployed in a faraway location, the SMF network element can also determine that the service initiated by the terminal hits the processing rule, and process the service initiated by the terminal.

[0031] In a possible design, the session management network element determines that the terminal supports the first type of service, or determines that the terminal is authorized to access the first type of service.

[0032] In a possible design, the session management network element receives first indication information from a second network element, where the first indication information is used to indicate that the first service is a first type of service; or the session management network element determines that the first service is a first type of service according to a data network access identifier of the first service; or the session management network element determines that the first service is a first type of service according to server deployment information of the first service sent by the second network element.

[0033] Through the foregoing design, the session management network element can flexibly determine that the first service is a first type of service in a plurality of different manners.

[0034] In a possible design, the first type of service includes any one of the following:

[0035] a service requiring low N6 latency; where requiring low N6 latency can also be referred to as having a requirement on N6 latency, or requiring guaranteeing N6 latency, or considering N6 latency, or requiring considering N6 latency, or indicating considering N6 latency, or EAS discovery based on N6 latency, or indicating communication (or routing) requirement between a local data network and a central data network;

[0036] a service deployed in a cloud server or a remote server;

[0037] a service requiring low N6 latency and deployed in a cloud server or a remote server;

[0038] a service requiring guaranteeing QoS; where requiring guaranteeing QoS can also be referred to as having a requirement on QoS, or considering QoS, or requiring considering QoS, or indicating considering QoS, or EAS discovery based on QoS;

[0039] a service requiring guaranteeing QoS and deployed in a cloud server or a remote server.

[0040] In a third aspect, an embodiment of the present application provides a communication method, which can be applied to a session management network element or a chip in the session management network element. Taking the case where the method is applied to a session management network element as an example, the method includes: the session management network element determines that a first service is a first type of service; the first type of service is a service meeting a quality of service requirement and / or a deployment location requirement; and the session management network element configures a user plane path corresponding to the first service according to a data network access identifier corresponding to the first service.

[0041] Optionally, the session management network element configuring the user plane path corresponding to the first service can be to instruct the user plane network element to configure a user plane path (e.g., a tunnel of a session of the terminal), the terminal accesses the first service through the user plane network element, or a data packet of the terminal accessing the first service passes through the user plane network element, or a user plane path of the terminal accessing the first service includes the user plane network element.

[0042] Through the above method, for the first service (the first type of service) of the terminal, the session management network element can perceive that the terminal initiates the first service, and configure a user plane path for the first service; in this way, when the terminal initiates the first service, data of the first service can be transmitted through the user plane path corresponding to the first service, thereby ensuring the reliability of the first service of the terminal.

[0043] In a possible design, the first type of service includes any of the following:

[0044] a service requiring low N6 latency; wherein requiring low N6 latency can also be referred to as having a requirement on N6 latency, or requiring to guarantee N6 latency, or considering N6 latency, or requiring to consider N6 latency, or indicating to consider N6 latency, or EAS discovery based on N6 latency, or indicating communication (or routing) requirements of a local data network and a central data network;

[0045] a service deployed in a cloud server or a remote server;

[0046] a service requiring low N6 latency and deployed in a cloud server or a remote server;

[0047] a service requiring to guarantee QoS; wherein requiring to guarantee QoS can also be referred to as having a requirement on QoS, or considering QoS, or requiring to consider QoS, or indicating to consider QoS, or EAS discovery based on QoS;

[0048] a service requiring to guarantee QoS and deployed in a cloud server or a remote server.

[0049] Optionally, the data network access identifier corresponding to the first service does not include the data network access identifier corresponding to the terminal, or the data network access identifier corresponding to the first service is different from the data network access identifier corresponding to the terminal, or the first network element retains the offloading rule of the first service when the terminal moves; or the first network element does not update or delete the offloading rule of the first service when the terminal moves.

[0050] In a possible design, the session management network element receives third indication information from a second network element, where the third indication information is used to indicate that the first service is a first type of service; or the session management network element determines, according to server deployment information of the first service, that the first service is a first type of service.

[0051] Through the above design, the session management network element can flexibly determine the first service as the first type of service in multiple different ways.

[0052] Optionally, the second indication information is carried in a user plane configuration indication sent by the second network element, and the user plane configuration indication is used to indicate configuration of a user plane path for the first service; the user plane configuration indication further includes FQDN information corresponding to the first service and / or address information of an application server corresponding to the first service.

[0053] Optionally, the user plane configuration indication further includes a data network access identifier corresponding to the first service.

[0054] In a possible design, the session management network element determines the data network access identifier corresponding to the first service according to the FQDN information corresponding to the first service and / or the address information of the application server, and server deployment information of the first service.

[0055] Through the above design, the session management network element can accurately determine the data network access identifier corresponding to the first service according to the FQDN information corresponding to the first service and / or the address information of the application server, and the server deployment information of the first service.

[0056] In a possible design, the session management network element receives a fourth notification message from the first network element, and the fourth notification message indicates that the terminal initiates the first service.

[0057] Through the above design, the session management network element can determine that the terminal initiates the first service after receiving the fourth notification message from the first network element, and then perform user plane configuration.

[0058] Optionally, the second indication information is carried in a PDU session establishment request sent by the terminal, and the PDU session establishment request is used to request establishment of a PDU session that carries service data of the first service; the PDU session establishment request further includes the FQDN information corresponding to the first service.

[0059] Optionally, the PDU session establishment request further includes a data network access identifier corresponding to the first service.

[0060] In a possible design, the session management network element determines the data network access identifier corresponding to the first service according to the FQDN information corresponding to the first service and server deployment information of the first service.

[0061] According to the above design, the session management network element can determine the data network access identifier corresponding to the first service according to the FQDN information corresponding to the first service and the server deployment information of the first service.

[0062] In a possible design, the session management network element determines a third user plane network element for establishing a user plane path corresponding to the first service according to the data network access identifier corresponding to the first service, and instructs the third user plane network element to establish the user plane path through which the data flow corresponding to the first service is transmitted.

[0063] In a possible design, the session management network element determines the third user plane network element according to the time delay between at least one second candidate user plane network element and an application server corresponding to the first service, wherein the at least one second candidate user plane network element corresponds to the data network access identifier corresponding to the first service, and the application server corresponding to the first service corresponds to the data network access identifier corresponding to the first service.

[0064] Optionally, the third user plane network element is a user plane network element with the lowest time delay between the at least one second candidate user plane network element and the application server corresponding to the first service, wherein the at least one second candidate user plane network element corresponds to the data network access identifier corresponding to the first service, and the application server corresponding to the first service corresponds to the data network access identifier corresponding to the first service.

[0065] According to the above design, the session management network element can select the third user plane network element according to the time delay between each second candidate user plane network element and the application server, and configure the user plane path according to the third user plane network element. For example, the session management network element can select the second candidate user plane network element with the lowest time delay as the third user plane network element, and the user plane path configured based on the third user plane network element can ensure that the data sent by the terminal to the application server has a shorter routing time in the Internet network, thereby improving the reliability of the terminal service.

[0066] In a fourth aspect, a communication apparatus is provided. The communication apparatus can implement the functions described in any of the first aspect to the third aspect. The communication apparatus can include a module or unit or means for performing the operations of any of the first aspect to the third aspect. The module or unit or means can be implemented in software or hardware, or a combination thereof. For example, the communication apparatus includes a communication unit and a processing unit. The communication unit is configured to perform the functions of any of the first aspect to the third aspect, or any possible implementation of the first aspect to the third aspect. The communication unit can be referred to as a transceiver. Optionally, the communication unit includes a receiver and a transmitter. The processing unit is configured to perform the processing functions.

[0067] In one design, the communication apparatus is a communication chip. The processing unit can be one or more processors or processor cores. The communication unit can be input / output circuits, input / output interfaces, or antenna ports of the communication chip.

[0068] In another design, the communication unit can be a transmitter and a receiver. Or the communication unit can be a transmitter and a receiver.

[0069] Optionally, the communication apparatus further includes various modules that can be used to perform any of the first aspect to the third aspect, or any possible implementation of the first aspect to the third aspect.

[0070] In a fifth aspect, a communication apparatus is provided. The communication apparatus can be the terminal device or the network device. The communication apparatus can include a processor and a memory to perform any of the first aspect to the third aspect, or any possible implementation of the first aspect to the third aspect. Optionally, the communication apparatus further includes a transceiver. The memory is configured to store a computer program or instructions. The processor is configured to invoke and run the computer program or instructions in the memory. When the processor executes the computer program or instructions in the memory, the communication apparatus performs any of the first aspect to the third aspect, or any possible implementation of the first aspect to the third aspect.

[0071] Optionally, the processor can be one or more processors. The memory can be one or more memories.

[0072] Optionally, the memory can be integrated with the processor. Or the memory can be separate from the processor.

[0073] Optionally, the transceiver can include a transmitter and a receiver.

[0074] In a sixth aspect, a communication apparatus is provided. The communication apparatus can be a terminal device or a network device. The communication apparatus can include a processor configured to implement any of the methods in the first aspect to the third aspect, or any possible implementation of the first aspect to the third aspect. The processor is coupled to a memory. Optionally, the communication apparatus further includes the memory. Optionally, the communication apparatus further includes a communication interface, and the processor is coupled to the communication interface.

[0075] In an implementation form, when the communication apparatus is a terminal device or a network device, the communication interface can be a transceiver, or an input / output interface. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0076] In yet another implementation form, when the communication apparatus is a chip or a chip system, the communication interface can be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or related circuitry, etc. on the chip or chip system. The processor can also be implemented as a processing circuit or a logic circuit.

[0077] In a seventh aspect, a communication apparatus is provided. The communication apparatus includes a processor, and can further include a storage medium storing a computer program or instructions. The computer program or instructions, when executed by the processor, can be used to implement the method in any possible design of the first aspect to the third aspect. The communication apparatus can be a chip system. The chip system can be composed of a chip, or can include a chip and other discrete devices.

[0078] In an eighth aspect, a chip is provided. The chip includes a processor coupled to a memory, and is configured to read and execute a computer program or instructions stored in the memory, so as to enable the chip to implement the method in any possible design of the first aspect to the third aspect.

[0079] In a ninth aspect, a computer readable storage medium is provided. The computer readable storage medium stores a computer program or instructions. When the computer program or instructions are read and executed by a computer, the computer is enabled to perform the method in any possible design of the first aspect to the third aspect.

[0080] In a tenth aspect, a computer program product is provided. When the computer program product is read and executed by a computer, the computer is enabled to perform the method in any possible design of the first aspect to the sixth aspect.

[0081] The technical effects of each of the second aspect to the tenth aspect and each possible design can refer to the technical effect description of the first aspect or each possible design, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0082] Figure 1 is a network architecture diagram of a communication system provided by an embodiment of the present application;

[0083] Figure 2 is a multi-anchor session architecture diagram provided by an embodiment of the present application;

[0084] Figure 3 is a flow diagram of a communication method provided by an embodiment of the present application;

[0085] Figure 4 is a flow diagram of a communication method provided by an embodiment of the present application;

[0086] Figure 5 is a flow diagram of a communication method provided by an embodiment of the present application;

[0087] Figure 6 is a flow diagram of a communication method provided by an embodiment of the present application;

[0088] Figure 7 is a flow diagram of a communication method provided by an embodiment of the present application;

[0089] Figure 8 is a flow diagram of a communication method provided by an embodiment of the present application;

[0090] Figure 9 is a flow diagram of a communication method provided by an embodiment of the present application;

[0091] Figure 10 is a flow diagram of a communication method provided by an embodiment of the present application;

[0092] Figure 11 is a flow diagram of a communication method provided by an embodiment of the present application;

[0093] Figure 12 is a structural diagram of a communication apparatus provided by an embodiment of the present application;

[0094] Figure 13 is a structural diagram of a communication apparatus provided by an embodiment of the present application. DETAILED DESCRIPTION

[0095] 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 drawings.

[0096] At least one (item) to which the embodiments of the present application relate indicates one (item) or multiple (items). Multiple (items) means two (items) or more than two (items). “And / or” describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can mean that there are three cases of A alone, A and B together, and B alone. The character “ / ” generally represents that the front and rear associated objects have an “or” relationship. In addition, it should be understood that although the terms first, second, etc. may be used to describe various objects in the embodiments of the present application, these objects should not be limited to these terms. These terms are only used to distinguish the objects from each other.

[0097] The ordinal numbers “first”, “second”, etc. mentioned in the embodiments of the present application are used to distinguish a plurality of objects, and are not used to limit the order, time sequence, priority or importance of the plurality of objects. For example, the first indication information and the second indication information are only used to distinguish different information, and do not represent that the contents, priorities or importance of the two kinds of information are different.

[0098] The terms “comprise”, “have” and any variations thereof mentioned in the embodiments of the present application are intended to cover the non-exclusive inclusion. For example, a process, method, system, product or device including a series of steps or units is not limited to the listed steps or units, but can optionally further include other steps or units not listed, or can optionally further include other steps or units inherent to the process, method, product or device. It should be noted that in the embodiments of the present application, the words “exemplary” or “for example” are used to mean serving as an example, instance or illustration. Any method or design scheme described as “exemplary” or “for example” in the embodiments of the present application should not be interpreted as being more preferred or having more advantages than other methods or design schemes. Rather, the words “exemplary” or “for example” are used in the specific manner to present the relevant concept.

[0099] The technology provided by the embodiments of the present application can be applied to various communication systems, such as a universal mobile communication system (UMTS), a wireless local area network (WLAN), a wireless fidelity (Wi-Fi) system, a 4th generation (4G) mobile communication system such as a long term evolution (LTE) system, a 5th generation (5G) mobile communication system such as a new radio (NR) system, and a future communication system.

[0100] The present application will present various aspects, embodiments or features around a system that can include a plurality of devices, components, modules, etc. It should be understood and appreciated that each system can include additional devices, components, modules, etc., and / or can not include all of the devices, components, modules, etc. discussed in connection with the figures. Furthermore, combinations of these aspects can also be used.

[0101] In addition, in the embodiments of the present application, the words "exemplary", "for example", "for instance", etc. are used only to mean example, illustration or description. Any embodiment or design solution described in the present application as "exemplary" should not be interpreted as being more preferred or advantageous than other embodiments or design solutions. In fact, the word "exemplary" is used only to present concepts in a concrete manner. In the embodiments of the present application, "of", "corresponding" and "corresponding" are sometimes mixed. It should be pointed out that when the difference is not emphasized, the meanings expressed are consistent.

[0102] A network element in a communication system can send a signal to another network element or receive a signal from another network element. Wherein the signal can include information or data, etc.; the network element can also be referred to as an entity, a network entity, a device, a communication device, a communication module, a node, a communication node, etc. In the embodiments of the present application, the network element is taken as an example for description.

[0103] Referring to FIG. 1, a network architecture diagram of a communication system to which the embodiments of the present application are applicable is shown. The system contains network functions and entities mainly including: a terminal (user equipment, UE), a (radio) access network ((R)AN) network element, a user plane function (UPF) network element, a data network (data network, DN), an access and mobility management function (access and mobility management function, AMF) network element, a session management function (session management function, SMF) network element, a policy control function (policy control function, PCF) network element, an application function (application function, AF) network element, a unified data management (unified data management, UDM) network element, a network exposure function (network exposure function, NEF) network element, a network repository function (network repository function, NRF) network element, an edge application server discovery network element (edge application server discovery function, EASDF) network element, etc.

[0104] The terminal can be a device or module with corresponding communication functions for accessing the communication system and having corresponding communication functions. The terminal can also be referred to as a user equipment (UE), terminal device, user apparatus, access terminal, subscriber unit, subscriber station, mobile station, mobile station (MS), remote station, remote terminal, mobile device, user terminal, terminal unit, terminal station, terminal apparatus, wireless communication device, user agent, or user device. The terminal is usually provided with a communication module, circuit or chip for performing corresponding communication functions, and is also configured with program instructions for performing corresponding communication functions. For example, the terminal in the embodiments of the present application can be a mobile phone, a personal digital assistant (PDA) computer, a laptop computer, a tablet computer (Pad), a drone, a computer with wireless transceiver function, a machine type communication (MTC) terminal, a virtual reality (VR) terminal, an augmented reality (AR) terminal, an internet of things (IoT) terminal, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical treatment, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home (such as game consoles, smart televisions, smart speakers, smart refrigerators and fitness equipment, etc.), a transport vehicle with wireless communication function, a communication module, a roadside unit (RSU) with terminal function. The embodiments of the present application do not limit the specific technology and specific device form of the terminal device.

[0105] The (R)AN network element can be an evolved universal terrestrial radio access (E-UTRA) system, an NR system and a future wireless access system defined in the 3rd generation partnership project (3GPP). The RAN 100 can also include two or more different wireless access systems. The (R)AN network element can also be an open RAN (O-RAN).

[0106] The (R)AN network element involved in the embodiments of the present application can be a RAN node. The RAN node, also referred to as a radio access network device, a RAN entity or an access node, is used to help the terminal access the communication system through wireless means. In one application scenario, the RAN node can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next generation NodeB (gNB) in a 5th generation (5G) mobile communication system, or a base station in a future mobile communication system. The RAN node can be a macro base station, a micro base station or an indoor station, and can also be a relay node or a donor node.

[0107] In another application scenario, the terminal can access the wireless network through the cooperation of multiple RAN nodes, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node can be a central unit (CU), a distributed unit (DU) or a radio unit (RU). The CU here implements the functions of the radio resource control protocol and the packet data convergence protocol (PDCP) of the base station, and can also implement the function of the service data adaptation protocol (SDAP); the DU implements the functions of the radio link control layer and the medium access control (MAC) layer of the base station, and can also implement part of the physical layer or all the physical layer functions. For specific descriptions of the above-mentioned protocol layers, reference can be made to the relevant technical specifications of 3GPP. The RU can be used to implement the functions of receiving and transmitting radio frequency signals. The CU and the DU can be two independent RAN nodes, or can be integrated in the same RAN node, such as in a baseband unit (BBU). The RU can be included in a radio frequency device, such as a remote radio unit (RRU) or an active antenna unit (AAU). The CU can be further divided into two types of RAN nodes: CU-control plane and CU-user plane.

[0108] In different systems, the RAN node can have different names, for example, in an O-RAN system, the CU can be referred to as an open CU (O-CU), the DU can be referred to as an open DU (O-DU), and the RU can be referred to as an open RU (O-RU). The CU-control panel (CU-CP) can also be referred to as an open CU-CP (O-CU-CP), and the CU-user panel (CU-UP) can also be referred to as an open CU-UP (O-CU-UP). The RAN node in the embodiments of the present application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module, for example, the RAN node can be a server loaded with a corresponding software module. The embodiments of the present application do not limit the specific technology and specific equipment form adopted by the RAN node. For ease of description, a base station is described as an example of the RAN node in the following.

[0109] Data Network (DN): a data network providing service for a user, generally a client is located at a terminal and a server is located at a data network. The data network can be a private network such as a local area network, can be an external network not controlled by an operator, for example, the Internet, or can be a dedicated network jointly deployed by operators, for example, a network providing IP Multimedia Core Network Subsystem (IMS) services.

[0110] The functions of the network elements in the core network are briefly introduced as follows:

[0111] SMF network element: mainly used for session management, IP address allocation and management of a terminal, selection of a manageable user equipment plane function, policy control, or termination of a charging function interface, and downlink data notification, etc.

[0112] AMF network element: mainly used for mobility management and access management, for example, it can be a mobility management entity (MME) function in a 4G communication network or an AMF network element in a 5G network.

[0113] PCF network element: a unified policy framework for guiding network behavior, providing policy rule information for control plane function network elements (such as AMF, SMF, etc.).

[0114] UDM network element: used for processing user identification, subscription, access authentication, registration, or mobility management, etc.

[0115] AF network element: used for data routing for application influence, access network exposure function, or policy control interaction with the policy framework, etc.

[0116] UPF network element: used for packet routing and forwarding, or quality of service (QoS) processing of user plane data, etc.

[0117] NEF network element: used for securely exposing services and capabilities provided by 3GPP network functions to the outside, etc.

[0118] NRF network element: used for saving the description information of network function entities and the services they provide, and supporting service discovery, network element entity discovery, etc.

[0119] EASDF network element: a network element used for assisting in discovering edge application servers (EAS), which mainly functions to process domain name system (DNS) messages according to the instructions of the SMF.

[0120] It can be understood that other network elements can also be included in the network architecture described above in actual applications, which are not limited in the present application.

[0121] It should be noted that in the present application, the names of the various network elements are only examples, and the present application does not exclude the case where the various network elements are given other names in the future, and the functions of the various network elements are combined. With the evolution of technology, any device or network element that can realize the functions of the above-mentioned network elements is within the protection scope of the present application. The interface names between the various network elements in FIG. 1 are only examples, and the names of the interfaces in the specific implementation can be other names, which are not limited in the present application. In addition, the names of the messages (or signaling) transmitted between the above-mentioned various network elements are also only examples, and do not constitute any limitation on the functions of the messages themselves.

[0122] It should be understood that the embodiments introduced hereinafter in the present application can be implemented by all the network elements in FIG. 1, or can be implemented by part of the network elements in FIG. 1, which are not limited in the present application.

[0123] For ease of description, hereinafter, the various network elements can be represented by their corresponding English abbreviations, for example, the application function network element is represented by "AF", the session management function network element is represented by "SMF", etc.

[0124] The terms related to the present application are introduced as follows.

[0125] 1. Multi-anchor point session:

[0126] In order to support selective traffic routing to data network or support session continuity mode, the SMF network element can insert multiple UPF network elements controlled by the SMF network element in the user plane of the protocol data unit (PDU) session to control the user plane path of the PDU session, so that one PDU session can access the DN network element through multiple N6 interfaces at the same time. Each UPF network element accessing the DN network element needs to support the PDU session anchor point function, that is, one PDU session needs to access the same DN network element through multiple anchor points.

[0127] As shown in the multi-anchor point session architecture of FIG. 2, there is a split point UPF network element (such as the uplink classifier (ULCL) / branching point (BP) UPF network element in FIG. 2) in the PDU session, which has the function of splitting the user plane message according to the source / destination IP address of the user plane message. The splitting rule can be configured by the SMF network element. For example, the ULCL UPF network element splits according to the destination IP address of the uplink message, and according to the destination IP address, forwards the user plane message to the C-PSA or L-PSA through different tunnels (such as the tunnel between the ULCL and the central-PSA (C-PSA) in FIG. 2, or the tunnel between the ULCL and the local-PSA (L-PSA)). Wherein, the C-PSA can also be referred to as PAS. For example, the branching point (BP) UPF network element splits according to the source IP address of the uplink message, and according to the source IP address, forwards the user plane message to the C-PSA or L-PSA through different tunnels. When using BP splitting, the SMF network element generates routing rules and sends them to the UE. The UE selects different source IPs when accessing services according to the routing rules, and further, the BP UPF network element splits according to the source IP.

[0128] The splitting rule of the split point is configured by the SMF network element, and the SMF network element can control the insertion, modification, removal, and splitting rule configuration / modification of the UPF network element through the N4 interface between the UPF network element.

[0129] In the scenario of public network, the local DN and the DN are the internet network (internet) in FIG. 2, and the two DNs can interwork. That is, the data packet of the UE can reach any one of the servers in the L-DN / DN, no matter whether the data packet enters the L-DN / DN from the L-PSA or the C-PSA. For example, the deployment locations of the L-PSA and the L-DN are A, the deployment location of the C-PSA is B, and the deployment location of the server corresponding to a service is C. The data packet routing mode of the UE includes: mode 1, the data packet can enter the internet through the C-PSA with the deployment location B, and be routed to the server with the deployment location C in the internet; and mode 2, the data packet can directly enter the internet from the L-PSA with the deployment location A, and be routed to the server with the deployment location C in the internet. Both modes can reach the server with the deployment location C; the difference is that if the location B is closer to the location C, the data packet in mode 1 has a longer routing distance in the core network, and the data packet in mode 2 has a longer routing distance in the internet.

[0130] 2. EAS deployment information (EDI):

[0131] The EAS deployment information reflects the deployment of the network at the edge. The EAS deployment information can include address information of the EAS deployed by a service provider, DNS server information, FQDN (full qualified domain name) information, and the like. The EAS deployment information can also include an identifier of an edge service for a 5G core network (5GC), such as a DNAI (data network access identifier), a DNN (data network name) corresponding to the EAS, and S-NSSAI (Single Network Slice Selection Assistance Information).

[0132] For details of the EAS deployment information, refer to 3GPP TS 23.548.

[0133] The DNAI can be used to represent a network access point, that is, an access point for accessing a DN from a core network (such as a UPF network element). The DNAI can include or correspond to one or more UPFs and EASs. The DNAI can be related to a geographic location, for example, the DNAI has a corresponding relationship with a TA (tracking area).

[0134] The EAS deployment information can be provided by an AF network element; the AF network element is a network element controlled by a service provider; for example, the AF network element provides the EAS deployment information to the operator.

[0135] The EAS deployment information can be stored in a unified data repository (UDR) network element; the SMF network element can obtain the EAS deployment information from the UDR network element through the NEF network element. For example, the SMF network element provides a DNN and / or S-NSSAI to the NEF network element, the NEF network element obtains and notifies the SMF network element from the UDR network element, and the SMF network element thereby obtains the EAS deployment information related to the DNN and / or S-NSSAI.

[0136] In the following description, the target service is taken as an example when the terminal initiates a certain service, the SMF network element is used to discover the EAS corresponding to the target service according to the target service initiated by the terminal. In the process of discovering the EAS corresponding to the target service by the SMF network element, the EASDF network element can be used to assist the discovery of the EAS. In the PDU session establishment process, the SMF network element selects the EASDF network element, and after selecting the EASDF network element, the SMF network element can configure the EASDF network element with a processing rule for the first service of the terminal. Since in the edge computing deployment scenario, the SMF network element assists the terminal to access the EAS corresponding to the target service close to the terminal; therefore, when the SMF network element configures the EASDF network element with the processing rule for the first service of the terminal, the processing rule includes the service provided by the application server close to the terminal. When the terminal initiates the target service, the EASDF network element receives the DNS request message sent by the terminal, and the EASDF network element determines that the target service currently initiated by the terminal is the service included in the processing rule according to the DNS request message, and only then notifies the SMF network element to perform corresponding processing, that is, to discover the EAS for the target service currently initiated by the terminal. However, for the service provided by the application server far away from the terminal, the processing rule of the service (provided by the application server far away from the terminal) is not included in the processing rule configured by the SMF network element to the EASDF network element, and then the EASDF network element will not notify the SMF network element to perform corresponding processing after receiving the DNS request message sent by the terminal for the service, therefore, for the service provided by the application server far away from the terminal, the SMF network element cannot be aware, thereby causing the terminal to be unable to access the EAS corresponding to the service far away.

[0137] Based on this, the embodiment of the present application provides a communication method, when the terminal initiates the service provided by the application server far away, the SMF network element can also be aware of the service and control the terminal to access the application server corresponding to the service.

[0138] FIG. 3 is a flow diagram of a communication method provided by an embodiment of the present application. The communication method mainly includes the following steps 300-302. It can be understood that the steps and the execution order shown in FIG. 3 are only examples. In actual implementation, part of the steps or the remaining steps can be executed, and the execution order of the steps can be adjusted. The embodiments of the present application do not limit this.

[0139] Step 300: The session management network element obtains a data network access identifier of the first service, and determines that the first service is a first type of service.

[0140] Optionally, the session management network element can obtain the data network access identifier (DNAI) of the first service from the second network element.

[0141] In the following description, the session management network element is taken as an SMF network element, and the second network element is taken as an AF network element. The session management network element in the embodiments of the present application can also be other names, or the second network element can also be other network elements or other names. The present application does not limit this.

[0142] The AF network element sends server deployment information of at least one service to the SMF network element, and the at least one service can include the first service in step 300. Correspondingly, the SMF network element receives the server deployment information of the at least one service from the AF network element.

[0143] The server deployment information includes but is not limited to at least one of the following:

[0144] The address information of the server, the DNS server information, the FQDN information, the data network access identifier, the DNN, the S-NSSAI, and the service type indication information. The service type indication information is used to indicate that the corresponding service is a first type of service. For example, the service type indication information corresponds to one or more of the address information of the server, the FQDN, and the data network access identifier, indicating that the address information of the corresponding server or the FQDN is a first type of service. The data network access identifier can be a data network access identifier corresponding to the service, and the DNN and the S-NSSAI can be a DNN and an S-NSSAI corresponding to the service.

[0145] For example, the server deployment information of the service can be EAS deployment information. The content included in the EAS deployment information can be referred to the description in the foregoing.

[0146] Optionally, the process of the SMF network element obtaining the server deployment information can be that the AF network element provides the server deployment information to the NEF, the NEF stores the server deployment information in the UDR, the SMF network element subscribes to the server deployment information from the NEF, and the NEF sends the server deployment information stored locally or obtained from the UDR to the SMF network element.

[0147] The first type of service in this application is a service that meets a service quality requirement and / or a deployment location requirement. For example, meeting a service quality requirement can include meeting a QoS requirement, or meeting an N6 latency requirement, etc.

[0148] Optionally, the first type of service can include at least one of the following services:

[0149] 1. a service that requires low N6 latency;

[0150] a service that requires low N6 latency, which can also be referred to as having a requirement on N6 delay, or requiring to guarantee N6 latency, or considering N6 latency, or requiring to consider N6 latency, or indicating to consider N6 latency, or EAS discovery based on N6 latency, or indicating the communication (or routing) requirement of a local data network and a central data network.

[0151] Wherein, N6 is the interface between a UPF network element and a DN. The N6 latency can be the latency between the UPF network element and the application server corresponding to the service; it can be understood as the latency of the data packet or signaling from leaving the UPF network element (leaving the operator network can also be understood as leaving the operator network) to reaching the application server corresponding to the service through routing in the DN (such as the Internet).

[0152] For example, the N6 latency can be the latency of the N6 segment between a UPF and an EAS.

[0153] In the case where there are multiple UPFs and at least one EAS within a data network access identifier, the N6 latency corresponding to the data network access identifier can also be determined according to the N6 latency between any UPF and EAS combination within the data network access identifier, or according to the average value of the N6 latency between all UPF and EAS combinations within the data network access identifier.

[0154] For example, a service that requires low N6 latency can be a service that requires the N6 latency corresponding to the service to be no greater than a first threshold value, wherein the first threshold value can be a set value or an empirical value. The first threshold value can be provided by the AF, or provided by any core network element, or locally configured by the SMF network element.

[0155] 2. a service deployed on a cloud server or a remote server;

[0156] Exemplarily, the cloud server or the remote server can be a server deployed in a central DN, or the cloud server or the remote server can be a server far away from a location where the terminal is located; for example, a distance between the cloud server or the remote server and the terminal is not less than a second threshold value, where the second threshold value can be a set value or an empirical value.

[0157] 3. A service requiring low N6 latency and deployed in a cloud server or a remote server.

[0158] 4. A service requiring guaranteed QoS.

[0159] The requirement for guaranteed QoS can also be referred to as a requirement for QoS, or consideration of QoS, or a requirement for consideration of QoS, or an instruction for consideration of QoS, or QoS-based EAS discovery. The requirement for QoS can be specifically seen in QoS parameters in 3GPP TS 23.503, such as a 5G QoS identifier (5G QoS Identifier, 5QI) and a packet delay budget (packet delay budget, PDB).

[0160] 5. A service requiring guaranteed QoS and deployed in a cloud server or a remote server.

[0161] In step 300, the SMF network element can determine that the first service is a service of the first type according to different manners, which will be introduced below.

[0162] The service type determination manner 1: the SMF network element receives first indication information from the AF network element, and the first indication information is used to indicate that the first service is a service of the first type. Correspondingly, the AF network element sends the first indication information to the SMF network element.

[0163] Optionally, the first indication information can be directly sent by the AF network element to the SMF network element, or can be forwarded by the AF network element to the SMF network element through other network elements, for example, through forwarding of NEF, UDR, PCF and the like. In the forwarding process, the first indication information can be carried by different messages, such as Nnef_EASDeployment_Notify message, Nnef_EASDeployment_Create / Update message, and PCC rule message. Optionally, in the forwarding process, the first indication information itself can also change, but its role does not change, for example, the name of the first indication information changes in the forwarding process, but its role is to indicate that the first service is a service of the first type.

[0164] The AF network element sends server deployment information of at least one service to the SMF network element, the at least one service including the first service, and the first service being a service of the first type.

[0165] Optionally, the first indication information and the server deployment information of the at least one service can be two pieces of information sent independently, or the first indication information can also be carried in the server deployment information of the service (it can be understood that when the service is a service of the first type, the first indication information is added in the server deployment information of the service, which is used to indicate that the service is a service of the first type. For example, the first indication information corresponds to one or more of the address information of the server, the FQDN, and the data network access identifier, indicating that the address information or the FQDN of the corresponding server is of the first type of service).

[0166] Optionally, the first indication information and the server deployment information of the at least one service can be carried in the same message or different messages.

[0167] Service type determination mode 2: The SMF network element determines that the first service is a service of the first type according to the data network access identifier of the first service.

[0168] Optionally, the data network access identifier of the service of the first type is different from the data network access identifier of the service of other types.

[0169] For example, the data network access identifier of the service of the first type can be a special data network access identifier. After the SMF network element obtains the data network access identifier of the first service from the AF network element, if the data network access identifier of the first service is a special data network access identifier, it can be determined that the first service is a service of the first type.

[0170] Service type determination mode 3: The SMF network element determines that the first service is a service of the first type according to the server deployment information of the first service sent by the AF network element.

[0171] Optionally, the SMF network element can determine that the first service is a service of the first type according to the server deployment information of the first service sent by the AF network element and the local configuration.

[0172] For example, the local configuration includes the data network access identifier of the service of the first type, or the FQDN of the service of the first type, or the address information of the application server of the service of the first type.

[0173] After the SMF network element obtains the server deployment information of the first service from the AF network element, whether the first service is a first type of service is determined according to the data network access identifier or the FQDN information or the application server address information in the server deployment information of the first service and the local configuration. For example, if the local configuration includes a data network access identifier belonging to the first type of service, when the data network access identifier of the first service is the same as the data network access identifier included in the local configuration, it is determined that the first service is the first type of service.

[0174] Step 301: The SMF network element instructs the first network element to create or update the processing rule of the first service for the terminal.

[0175] Optionally, the SMF network element sends configuration indication information to the first network element, for instructing the first network element to create or update the processing rule of the first service for the terminal. Correspondingly, the first network element receives the configuration indication information from the SMF network element.

[0176] The processing rule can include the processing rule of one or more services supported by the terminal; wherein the processing rule includes the processing rule of the first service, the corresponding data network access identifier of the first service is different from the corresponding data network access identifier of the terminal; or the corresponding at least one data network access identifier of the first service does not include the corresponding data network access identifier of the terminal; or the first network element retains the processing rule of the first service when the terminal moves; or the first network element does not update or delete the processing rule of the first service when the terminal moves.

[0177] The processing rule of the first service instructs the terminal to notify the session management network element when the terminal initiates the first service.

[0178] When the SMF network element instructs the first network element to create or update the processing rule, the first network element can be instructed not to consider the location of the terminal, i.e. services with a server deployment location far away from the location of the terminal can be included in the processing rule.

[0179] Since the data network access identifier can be used to represent the geographical location, for example, the data network access identifier and the TA have a corresponding relationship, one service can correspond to one or more data network access identifiers, and the one or more data network identifiers corresponding to the service are related to the deployment location of the service server; in the case that the data network access identifier corresponding to the first service does not include the data network access identifier corresponding to the terminal, or the data network access identifier corresponding to the first service is different from the data network access identifier corresponding to the terminal, it can be indicated that the terminal is far away from the application server of the first service.

[0180] Step 302: The SMF network element receives the first notification information from the first network element, and the first notification information indicates that the terminal initiates the first service.

[0181] Correspondingly, the first network element sends a first notification message to the SMF network element.

[0182] When the first network element determines that the service initiated by the terminal meets (or satisfies, or conforms to) the processing rule, the first network element sends a first notification message to the SMF network element, for notifying the SMF network element to process the service initiated by the terminal. Correspondingly, the SMF network element can process the first service sent by the terminal after receiving the first notification message.

[0183] Optionally, the processing rule can include FQDN information corresponding to one or more services; or the processing rule includes address information of an application server corresponding to one or more services. The one or more services include the first service.

[0184] For example, when the first network element is an EASDF network element, the processing rule can include FQDN information of one or more services. The first network element determines that the FQDN information carried in the DNS request message sent by the terminal for the first service is included in the processing rule, and determines that the first service initiated by the terminal meets the processing rule. The first network element sends a first notification message to the SMF network element.

[0185] For another example, when the first network element is a first UPF network element, the first UPF network element is a UPF network element configured when a PDU session of the terminal is established. The processing rule includes address information of an application server corresponding to one or more services. The first network element determines that the address information of the application server corresponding to the data (or data packet or data stream) sent by the terminal is included in the processing rule, and determines that the first service initiated by the terminal meets the processing rule. The first network element sends a first notification message to the SMF network element.

[0186] Based on the above communication method provided by the embodiments of the present application, when the SMF network element instructs the first network element to create or update the processing rule for the terminal, the processing rule includes the processing rule of the first service, and the location of the application server corresponding to the first service and the location of the terminal can be far away. In this way, when the terminal initiates a service of a server deployed in a far location, the first network element can also determine that the service initiated by the terminal meets the processing rule, so as to send a first notification message to the SMF network element, and notify the SMF network element to process the service initiated by the terminal.

[0187] In addition, as a possible implementation manner, in the above communication method, the SMF network element can also determine that the terminal supports the first type of service, or determine that the terminal is authorized to access the first type of service.

[0188] Optionally, the SMF network element can determine that the terminal supports the first type of service or that the terminal is authorized to access the first type of service according to the session subscription information and / or the session policy of the terminal. Alternatively, all terminals can support the first type of service or be authorized to access the first type of service.

[0189] In a case where the SMF network element determines that the terminal supports the first type of service or that the terminal is authorized to access the first type of service according to the session subscription information and / or the session policy of the terminal, the SMF network element can obtain the session subscription information and / or the session policy of the terminal in the PDU session establishment process, and then determine that the terminal supports the first type of service or that the terminal is authorized to access the first type of service according to the session subscription information and / or the session policy of the terminal.

[0190] For example, the terminal device can subscribe to a service of low N6 latency and / or guaranteed QoS from the operator, i.e., the terminal indicates that the operator needs to guarantee a certain QoS for the first type of service and / or guarantee low N6 latency.

[0191] For example, the terminal device can subscribe to a service of low N6 latency and / or guaranteed QoS from the operator, i.e., the terminal indicates that the operator needs to guarantee a certain QoS for the first type of service and / or guarantee low N6 latency.

[0192] Step 303: The SMF network element receives second notification information from the first network element, where the second notification information is used to indicate address information of the application server corresponding to the first service.

[0193] Correspondingly, the first network element sends the second notification message to the SMF network element.

[0194] In the embodiment of the application, the SMF network element maydetermine the address information of the application server corresponding to the first service in different ways when the first network element type is different, which will be introduced below for different types of first network elements. It should be noted that the first network element introduced below is only an example, and the first network element of the embodiment of the application can also be other types of network elements.

[0195] The first network element is an EASDF network element:

[0196] In a case where the first network element is an EASDF network element, the terminal sends a DNS request message to the EASDF network element when initiating the first service; and in a case where the EASDF network element determines that the processing rule is hit according to the FQDN information carried in the DNS request message, the EASDF network element sends a first notification message to the SMF network element.

[0197] After receiving the first notification message, the SMF network element determines that the first service initiated by the terminal currently hits the processing rule, and then the SMF network element sends a third notification message to the EASDF network element, for notifying the EASDF network element to process the DNS request message sent by the terminal.

[0198] Optionally, the third notification message sent by the SMF network element to the EASDF network element can carry an address information used for generating an ECS option, which can be referred to as ECS option information. The ECS option can be an extension item in the DNS request message, and is used to represent the location information of the terminal. For example, the SMF network element can determine the ECS option information according to the FQDN information carried in the DNS request message, the server deployment information obtained from the AF network element, and the location information of the terminal currently located in. For example, the ECS option information is an IP address.

[0199] After receiving the third notification message, the EASDF network element can update the DNS request message sent by the terminal. For example, the ECS option information is added as the ECS option in the DNS request message. And the updated DNS request message is sent to the DNS server (or DNS resolver).

[0200] The DNS server returns a DNS response message to the EASDF network element according to the updated DNS request message, wherein the DNS response message can carry the address information of the application server corresponding to the first service initiated by the terminal. Correspondingly, the EASDF network element receives the DNS response message sent by the DNS server, and the DNS response message includes the address information of the application server corresponding to the first service.

[0201] The EASDF network element sends second notification information to the SMF network element, wherein the second notification information is used to indicate the address information of the application server corresponding to the first service.

[0202] The first network element is a first UPF network element:

[0203] In the case that the first network element is a first UPF network element, wherein the first UPF network element can be a UPF network element configured when establishing a PDU session of the terminal. In the PDU session establishment process initiated by the terminal, the SMF network element determines that the current PDU session is used to access the first service, and configures the first UPF network element for the PDU session.

[0204] After the PDU session establishment is completed, the terminal can send data (or referred to as data packets or data streams) accessing the application server corresponding to the first service. After detecting the data corresponding to the first service, the first UPF network element determines that the address information of the application server corresponding to the first service hits the processing rule, and the first UPF network element sends a first notification message to the SMF network element, and the first notification message is used to indicate that the terminal initiates the first service. Optionally, the first notification message can include the address information of the application server corresponding to the first service; the SMF network element can obtain the address information of the application server corresponding to the first service from the first notification message.

[0205] Alternatively, the first UPF network element can also send a second notification message to the SMF network element in the case that the address information of the application server corresponding to the first service hits the processing rule, wherein the second notification message is used to indicate the address information of the application server corresponding to the first service.

[0206] Step S304: The SMF network element determines at least one first candidate user plane network element corresponding to the address information of the application server, and selects a first user plane network element from the at least one first candidate user plane network element according to the time delay between each first candidate user plane network element and the application server corresponding to the first service.

[0207] For example, the first candidate user plane network element can be a UPF network element. The SMF network element can select the first user plane network element from the at least one UPF network element.

[0208] Optionally, the SMF directly determines the first user plane network element according to the address information of the application server. Wherein, the SMF can determine the first user plane network element according to at least one of the address information of the application server, the server deployment information, and the N6 time delay.

[0209] Optionally, the at least one first candidate user plane network element corresponding to the address information of the application server and the address information of the application server belong to or correspond to the same data network access identifier.

[0210] Optionally, the SMF can determine the first user plane network element according to the N6 time delay.

[0211] Optionally, when the SMF network element determines at least one first candidate user plane corresponding to the address information of the application server, the at least one first candidate user plane network element can be determined according to the following steps:

[0212] Step a: The SMF network element determines at least one data network access node corresponding to the address information of the application server according to the server deployment information of the first service sent by the AF network element.

[0213] The AF network element sends server deployment information of one or more services to the SMF network element, and the server deployment information can include a data network access identifier and address information of an application server. After receiving the address information of the application server corresponding to the first service indicated by the second network element through the second notification message, the SMF can determine the data network access identifier corresponding to the first service from the server deployment information of one or more services according to the address information of the application server corresponding to the first service.

[0214] The SMF network element can determine at least one data network access node corresponding to the address information of the application server according to the data network access identifier corresponding to the first service.

[0215] The DANI corresponds to a data network access node, and the data network access identifier can be an identifier of the data network access node. For example, the data network access node can include one or more UPF network elements.

[0216] Step b: The SMF network element determines a target data network access node from the at least one data network access node.

[0217] In the case of determining one data network access node in step a, the data network access node can be determined as the target data network access node.

[0218] In the case of determining multiple data network access nodes in step a, the SMF network element can determine a target data network access node from the at least one data network access node according to the N6 delay corresponding to each data network access node.

[0219] For example, the N6 delay corresponding to the data network access node can be the delay between the data network access node and the application server corresponding to the first service.

[0220] In implementation, the SMF network element can determine the N6 delay corresponding to each data network access node respectively, and the SMF network element can select the data network access node with the minimum N6 delay from the multiple data network access nodes as the target data network access node.

[0221] Step c: The SMF network element determines the UPF network element corresponding to the target data network access node as at least one first candidate user plane network element.

[0222] The target data network access node can correspond to one or more UPF network elements, and the SMF network element takes the one or more UPF network elements corresponding to the target data network access node as the first candidate user plane network element.

[0223] After determining the at least one first candidate user plane network element, the SMF network element can further select a first user plane network element from the at least one first candidate user plane.

[0224] Optionally, in a case where one first candidate user plane network element is determined, the SMF network element can determine the first candidate user plane network element as the first user plane network element. In a case where multiple first candidate user plane network elements are determined, the SMF network element can determine an N6 latency corresponding to each of the first candidate user plane network elements respectively, and the SMF network element can select a first candidate user plane network element with the minimum N6 latency from the multiple first candidate user plane network elements as the first user plane network element.

[0225] For example, the N6 latency corresponding to the first candidate user plane network element can be a latency between the first candidate user plane network element and an application server corresponding to the first service.

[0226] In step S305, the SMF network element configures a user plane path corresponding to the first service according to the first user plane network element.

[0227] In an implementation, the SMF network element takes the first user plane network element as a splitting point and / or a local anchor point, and thus configures the user plane path corresponding to the first service.

[0228] In a case where the first network element is the EASDF network element, after the SMF network element configures the user plane path corresponding to the first service, the SMF network element can subsequently send data of the first service to a service server corresponding to the first service based on the user plane path.

[0229] In a case where the first network element is the first UPF network element, the SMF network element can forward or send data of the first service sent by the terminal to a service server corresponding to the first service based on the configured user plane path corresponding to the first service.

[0230] In addition, in a case where the first network element is the EASDF network element, the SMF network element can further instruct the EASDF network element to send a buffered DNS response message to the terminal.

[0231] When the terminal moves, the SMF network element does not perform a rediscovery / relocation process for the first type of service.

[0232] The rediscovery procedure is that when the terminal moves, the SMF network element sends the identifiers of services to the terminal according to server deployment information or services accessed by the terminal, and instructs the terminal to clear the DNS cache corresponding to the services (after clearing, the UE accesses the services again to reinitiate a DNS request, and the SMF network element can also reconfigure the user plane). However, for the first type of service, the SMF network element instructs the terminal to retain the DNS cache corresponding to the first type of service; or the first type of service is not included in the services instructed by the SMF network element to the terminal to clear the DNS cache when the movement occurs.

[0233] The relocation procedure is that the SMF network element needs to notify the AF network element of information such as FQDN information of the service, address information of the application server, data network access identifier, and instruct the AF network element to trigger relocation. For the first type of service, the SMF network element instructs the AF not to perform the relocation procedure, or the first type of service is not included in the services triggered by the SMF network element to the AF network element to perform relocation, or for the first type of service, the SMF network element does not instruct the AF network element to perform the relocation procedure.

[0234] The communication method of the embodiment of the application shown in FIGS. 3 and 4 will be introduced below in conjunction with examples.

[0235] Example 1:

[0236] Taking the session management network element as the SMF network element, the first network element as the EASDF network element, and the second network element as the AF network element as an example for description.

[0237] The communication method procedure shown in FIG. 5 can include the following steps; it can be understood that the steps and the execution order shown in FIG. 5 are only as an example, and in actual implementation, part of the steps or the remaining steps can be executed, and similarly, the execution order of the steps can also be adjusted, and the embodiment of the application does not limit this.

[0238] Step 500: The AF network element sends server deployment information of at least one service to the SMF network element.

[0239] The at least one service includes a first service, and the first service is a first type of service; for details, refer to the introduction of the first type of service in the foregoing.

[0240] Optionally, the server deployment information of the first service can include first indication information, the first indication information being used to indicate that the first service is a service of the first type; or the server deployment information of the first service includes a data network access identifier of the first service, wherein the data network access identifier of the first service is a special data network access identifier, so that the SMF network element can determine that the first service is a service of the first type based on the data network access identifier of the first service; or the SMF network element can also determine that the first service is a service of the first type according to local configuration and the FQDN or the data network access identifier or the application server address information in the server deployment information of the first service.

[0241] Step 501: The SMF network element determines that the terminal supports the first type of service, or determines that the terminal is authorized to access the first type of service.

[0242] Optionally, the SMF network element can determine that the terminal supports the first type of service, or determines that the terminal is authorized to access the first type of service, according to the session subscription information and / or the session policy of the terminal.

[0243] In implementation, the SMF network element can determine that the PDU session supports the first type of service in the PDU session establishment process of the terminal, which can be understood as that the terminal can access the first type of service through the PDU session.

[0244] Optionally, step 501 is an optional step.

[0245] Step 502: The SMF network element instructs the EASDF network element to create or update the processing rule of the first service for the terminal.

[0246] Optionally, the data network access identifier corresponding to the first service does not include the DNAI corresponding to the terminal, or the data network access identifier corresponding to the first service is different from the data network access identifier corresponding to the terminal, or the first network element retains the processing rule of the first service when the terminal moves; or the first network element does not update or delete the processing rule of the first service when the terminal moves.

[0247] Optionally, the processing rule of the first service of the terminal includes FQDN information of one or more services; for example, the processing rule of the first service of the terminal includes FQDN information of the first service.

[0248] Based on step 502, when the EASDF network element creates or updates the processing rule of the first service for the terminal, whether the application server of the service supported by the terminal (or the service that can be accessed) is close to the terminal or not, it can be configured in the processing rule of the terminal.

[0249] Step 503: The terminal initiates a first service, and sends a DNS request message for the first service to an EASDF network element.

[0250] Step 504: After determining that the first service hits the processing rule of the terminal, the EASDF network element sends a first notification message to an SMF network element.

[0251] The first notification message indicates that the terminal initiates the first service. In this way, the SMF network element can perceive the first service initiated by the terminal.

[0252] In implementation, the EASDF network element can compare the FQDN information in the DNS request message with the FQDN information included in the processing rule, and if the FQDN information in the DNS request message is included in the processing rule, it is determined that the first service hits the processing rule of the terminal.

[0253] Step 505: The SMF network element generates ECS option information according to a data network access identifier corresponding to the first service and / or location information of the terminal.

[0254] The ECS option information can be used to generate ECS option, and the ECS option can be used as an extension item in the DNS request message to represent the location information of the terminal.

[0255] Step 506: The SMF network element sends a third notification message to the EASDF network element, for notifying the EASDF network element to process the DNS request message sent by the terminal.

[0256] The third notification message can carry the ECS option information.

[0257] Step 507: After receiving the third notification message, the EASDF network element sends an updated DNS request message to a DNS server.

[0258] After receiving the third notification message, the EASDF network element can update the DNS request message sent by the terminal to obtain an updated DNS request message. For example, the ECS option information is added as ECS option in the DNS request message to obtain the updated DNS request message.

[0259] Step 508: The DNS server returns a DNS response message to the EASDF network element.

[0260] The DNS response message includes address information of an application server corresponding to the first service.

[0261] Step 509: The EASDF network element sends second notification information to the SMF network element, where the second notification information is used to indicate address information of the application server corresponding to the first service.

[0262] Step 510: The SMF network element determines the first user plane network element.

[0263] Optionally, the SMF network element determines at least one first candidate user plane network element corresponding to the address information of the application server, and selects the first user plane network element from the at least one first candidate user plane network element according to the time delay between each first candidate user plane network element and the application server corresponding to the first service.

[0264] The specific manner in which the SMF network element determines the first user plane network element can be referred to the description of step 304.

[0265] Step 511: The SMF network element configures a user plane path corresponding to the first service according to the first user plane network element.

[0266] For example, the SMF network element inserts a split point (ULCL / BP) and a local anchor point (L-PSA) according to the first user plane network element, and configures a split rule on the split point. The inserted split point and local anchor point are used to send user plane data of the first service of the terminal to the application server corresponding to the first service.

[0267] Step 512: The SMF network element instructs the EASDF network element to send the cached DNS response message to the terminal.

[0268] Step 513: The EASDF network element sends the cached DNS response message to the terminal.

[0269] Example 2:

[0270] Taking the session management network element as the SMF network element, the first network element as the first UPF network element, and the second network element as the AF network element as an example.

[0271] As shown in the communication method flow of FIG. 6, the following steps can be included; it can be understood that the steps and execution order shown in FIG. 6 are only as an example, and part of the steps or the remaining steps can be executed in actual implementation, similarly, the execution order of the steps can also be adjusted, and the embodiments of the present application do not limit this.

[0272] Step 600: The AF network element sends server deployment information of at least one service to the SMF network element.

[0273] Among the at least one service, the first service is included, and the first service is a first type of service; for details, see the description of the first type of service above.

[0274] Optionally, the server deployment information of the first service can include first indication information, the first indication information being used to indicate that the first service is a first type of service; or the server deployment information of the first service includes a data network access identifier of the first service, wherein the data network access identifier of the first service is a special data network access identifier, so that the SMF network element can determine that the first service is a first type of service based on the data network access identifier of the first service; or the SMF network element can also determine that the first service is a first type of service according to local configuration and the FQDN or the data network access identifier or the application server address information in the server deployment information of the first service.

[0275] Step 601: The SMF network element determines that the terminal supports the first type of service, or determines that the terminal is authorized to access the first type of service.

[0276] Optionally, the SMF network element can determine that the terminal supports the first type of service, or determines that the terminal is authorized to access the first type of service, according to the session subscription information and / or session policy of the terminal.

[0277] In implementation, the SMF network element can determine that the PDU session supports the first type of service in the PDU session establishment process of the terminal, which can be understood as that the terminal can access the first type of service through the PDU session.

[0278] Optionally, step 601 is an optional step.

[0279] Step 602: The SMF network element instructs the first UPF network element to create or update the processing rule for the first service of the terminal.

[0280] The first UPF network element can be a UPF network element configured when the PDU session of the terminal is established.

[0281] The data network access identifier corresponding to the first service does not include the DNAI corresponding to the terminal, or the data network access identifier corresponding to the first service is different from the data network access identifier corresponding to the terminal, or the first network element retains the processing rule of the first service when the terminal moves; or the first network element does not update or delete the processing rule of the first service when the terminal moves.

[0282] Optionally, the processing rule of the terminal includes address information of one or more application servers corresponding to the service; for example, the processing rule of the terminal includes address information of the application server corresponding to the first service.

[0283] Based on step 602, when the first UPF network element creates or updates the processing rule for the terminal, whether the application server of the service supported by the terminal (or called the service that can be accessed) is close to the terminal or not, it can be configured in the processing rule of the terminal.

[0284] Step 603: The terminal sends data accessing the application server corresponding to the first service.

[0285] Step 604: After the first UPF network element detects the data of the first service and determines that the processing rule of the first service hits the terminal, the first UPF network element sends a first notification message to the SMF network element.

[0286] The first notification message indicates that the terminal initiates the first service. In this way, the SMF network element can perceive the first service initiated by the terminal.

[0287] In implementation, the first UPF network element can compare the address information of the application server accessed by the terminal with the address information of the application server included in the processing rule, and if the address information of the application server accessed by the terminal is included in the processing rule, it is determined that the processing rule of the first service hits the terminal.

[0288] Optionally, the first notification message includes the address information of the application server corresponding to the first service.

[0289] Step 605: The SMF network element determines the first user plane network element.

[0290] Optionally, the SMF network element determines at least one first candidate user plane network element corresponding to the address information of the application server, and selects the first user plane network element from the at least one first candidate user plane network element according to the delay between each first candidate user plane network element and the application server corresponding to the first service.

[0291] The specific manner in which the SMF network element determines the first user plane network element can be referred to the description of step 304 above.

[0292] Step 606: The SMF network element configures a user plane path corresponding to the first service according to the first user plane network element.

[0293] For example, the SMF network element inserts a splitting point (such as ULCL / BP shown in FIG. 6) and a local anchor point (such as Remote PSA shown in FIG. 6) according to the first user plane network element, and configures a splitting rule on the splitting point. The inserted splitting point and local anchor point are used to send the user plane data of the first service of the terminal to the application server corresponding to the first service.

[0294] Step 607: The terminal sends data accessing the application server corresponding to the first service.

[0295] The data of the terminal can be sent to the application server corresponding to the first service through the user plane path corresponding to the first service, such as the data of the terminal being sent to the application server corresponding to the first service through ULCL / BP and Remote PSA in FIG. 6.

[0296] The embodiment of the application further provides a communication method, when a terminal initiates a service provided by a remote application server, the SMF network element can also perceive the service and process the service message of the terminal.

[0297] Fig. 7 is a flow diagram of a communication method provided by the embodiment of the application, which mainly includes steps 700-702. It can be understood that the steps and execution order shown in Fig. 7 are only as an example, and in actual implementation, part of the steps or the remaining steps can be executed, and similarly, the execution order of the steps can also be adjusted, which is not limited by the embodiment of the application.

[0298] Step 700: The session management network element acquires a data network access identifier of a first service, and determines that the first service is a first type of service.

[0299] The first type of service in the application is a service meeting the quality of service and / or deployment location requirement. For example, meeting the quality of service requirement can include meeting the QoS requirement, or meeting the N6 delay requirement, etc.

[0300] Optionally, the first type of service can include at least one of the following services:

[0301] 1. A service requiring low N6 delay;

[0302] For the service requiring low N6 delay, refer to the description in step 300 above, which is not repeated here.

[0303] 2. A service deployed in a cloud server or a remote server;

[0304] For the service deployed in a cloud server or a remote server, refer to the description in step 300 above, which is not repeated here.

[0305] 3. A service requiring low N6 delay and deployed in a cloud server or a remote server.

[0306] 4. A service requiring guaranteed QoS.

[0307] The requirement of guaranteed QoS can also be referred to as QoS requirement, QoS consideration, requirement of QoS consideration, indication of QoS consideration, or QoS-based EAS discovery.

[0308] 5. A service requiring guaranteed QoS and deployed in a cloud server or a remote server.

[0309] The specific manner in which the session management network element in step 700 acquires the data network access identifier of the first service and determines that the first service is a first type of service can be referred to the description of step 300 above, and will not be repeated here.

[0310] Step 701: The session management network element sends second indication information to the second user plane network element; wherein the second indication information is used to indicate the service splitting rule of the terminal.

[0311] Correspondingly, the second user plane network element can receive the second indication information from the session management network element.

[0312] In the following description, the session management network element is taken as an SMF network element for example.

[0313] Optionally, the SMF network element can create or update the splitting rule for the terminal.

[0314] For example, the SMF network element can create or update the splitting rule for the terminal when establishing a PDU session for the terminal.

[0315] The splitting rule can include the splitting rule of one or more services supported by the terminal; wherein the splitting rule includes the splitting rule of the first service, and the data network access identifier corresponding to the first service does not include the data network access identifier corresponding to the terminal, or the data network access identifier corresponding to the first service is different from the data network access identifier corresponding to the terminal.

[0316] When creating or updating the splitting rule, the SMF network element can not consider the location of the terminal, i.e. services whose application server deployment location is far away from the terminal location can be included in the splitting rule.

[0317] Since the data network access identifier can be used to represent the geographical location, one service can correspond to one or more data network access identifiers, and the one or more data network identifiers corresponding to the service are related to the deployment location of the service server; in the case that the data network access identifier corresponding to the first service does not include the data network access identifier corresponding to the terminal, or the data network access identifier corresponding to the first service is different from the data network access identifier corresponding to the terminal, it can be indicated that the terminal is far away from the application server of the first service.

[0318] In this application, the offloading rule refers to a rule for forwarding a service message of a terminal to another user plane network element or an application server; the offloading rule can also be referred to as a traffic routing rule. The service message of the terminal includes, but is not limited to, a DNS request message sent by the terminal, a data flow (or data or data packet) of the terminal; the other user plane network element can be a UPF network element, which can serve as a session anchor.

[0319] For example, when the terminal initiates a first service, the terminal can send a DNS request message, and the offloading rule is used to offload the access request of the first service initiated by the terminal to an application server corresponding to the first service.

[0320] For another example, for a data packet of the terminal, the offloading rule is used to indicate that the data of the application server accessing each data network access identifier is offloaded to a local anchor point PSA corresponding to the data network access identifier.

[0321] After the SMF network element creates or updates the offloading rule of the terminal, the SMF network element can send second indication information to the second user plane network element, and configure the offloading rule of the terminal to the second user plane network element through the first indication information.

[0322] Optionally, the second user plane network element can be a splitting point UPF network element; for example, the second user plane network element can be a ULCL UPF network element, or the second user plane network element can be a BP UPF network element.

[0323] The second user plane network element receives a service message of the first service from the terminal, and processes the service message according to the offloading rule.

[0324] For example, for a DNS request message initiated by the terminal, the second user plane network element offloads the DNS request message to a corresponding DNS server according to the offloading rule configured by the SMF and a user plane path, and resolves a local anchor point PSA corresponding to a data network access identifier. For a data packet sent by the terminal, the data packet is offloaded to a corresponding application server according to the offloading rule configured by the SMF and the user plane path.

[0325] Based on the above communication method provided by the embodiments of the application, the SMF network element can create or update the offloading rule for the terminal in advance, the offloading rule includes the offloading rule of the first service, and the location of the application server corresponding to the first service and the location of the terminal can be far away from each other. In this way, when the terminal initiates a service of a server deployed in a far location, the SMF network element can also determine that the service initiated by the terminal hits the processing rule, and process the service initiated by the terminal.

[0326] The communication method of the embodiments of the application shown in FIG. 7 will be introduced below in conjunction with examples.

[0327] Example 3:

[0328] Taking the session management network element as an SMF network element and the second network element as an AF network element as an example, the following is described.

[0329] The communication method flow shown in FIG. 8 can include the following steps. It can be understood that the steps shown in FIG. 8 and the execution order are only as an example. In actual implementation, part of the steps or the remaining steps can be executed. Similarly, the execution order of the steps can also be adjusted. The embodiments of the present application do not limit this.

[0330] Step 800: The AF network element sends server deployment information of at least one service to the SMF network element.

[0331] The at least one service includes a first service, and the first service is a first type of service. For details, refer to the description of the first type of service above.

[0332] Optionally, the server deployment information of the first service can include first indication information, which is used to indicate that the first service is a first type of service. Alternatively, the server deployment information of the first service includes a data network access identifier of the first service, and the data network access identifier of the first service is a special data network access identifier. In this way, the SMF network element can determine that the first service is a first type of service based on the data network access identifier of the first service. Alternatively, the SMF network element can also determine that the first service is a first type of service according to local configuration and FQDN or data network access identifier or application server address information in the server deployment information of the first service.

[0333] Step 801: The SMF network element determines that the terminal supports the first type of service, or determines that the terminal is authorized to access the first type of service.

[0334] Optionally, the SMF network element can determine that the terminal supports the first type of service, or determines that the terminal is authorized to access the first type of service, according to the session subscription information and / or session policy of the terminal.

[0335] In implementation, the SMF network element can determine that a PDU session of the terminal supports the first type of service in a PDU session establishment process of the terminal. It can be understood that the terminal can access the first type of service through the PDU session.

[0336] The step 801 is an optional step.

[0337] Step 802: The SMF network element creates or updates a first service splitting rule for the terminal.

[0338] The split rule can also be referred to as a traffic routing rule.

[0339] The data network access identifier corresponding to the first service does not include the DNAI corresponding to the terminal, or the data network access identifier corresponding to the first service is different from the data network access identifier corresponding to the terminal, or the first network element retains the processing rule of the first service when the terminal moves; or the first network element does not update or delete the processing rule of the first service when the terminal moves.

[0340] Optionally, the SMF can create or update the split rule for the first service of the terminal in the process of establishing the PDU session for the terminal.

[0341] Based on step 802, the SMF network element creates or updates the split rule for the terminal, whether the application server of the service (or service that can be accessed) supported by the terminal is close to the terminal or not, can be configured in the split rule of the terminal.

[0342] Step 803: The SMF network element sends second indication information to the second user plane network element, and the second indication information is used to indicate the split rule of the terminal.

[0343] The second user plane network element can be a split point UPF network element; for example, the second user plane network element can be a ULCL UPF network element, or the second user plane network element can be a BP UPF network element.

[0344] Step 804a: The second user plane network element receives the DNS request message of the first service sent by the terminal, and the second user plane network element can split the DNS request message to the corresponding DNS server according to the split rule.

[0345] Step 804b: The second user plane network element receives the data of the first service sent by the terminal, and the second user plane network element can split the data of the first service to the application server corresponding to the first service through the local anchor (such as Remote PSA shown in FIG. 8) according to the split rule.

[0346] The embodiment of the application also provides a communication method for the SMF network element to perceive the first service, wherein the first service is a first type of service meeting the quality of service and / or deployment location requirement, and a user plane path is configured for the first service.

[0347] FIG. 9 is a flowchart of a communication method provided by an embodiment of the application, which mainly includes the following steps 900-901. It can be understood that the steps and the execution order shown in FIG. 9 are only as an example, and in actual implementation, part of the steps or the remaining steps can be executed, and similarly, the execution order of the steps can also be adjusted, which is not limited in the embodiment of the application.

[0348] Step 900: The session management network element determines that the first service is a first type of service.

[0349] In the following description, the session management network element is taken as an example of an SMF network element.

[0350] In the present application, the first type of service is a service that meets the requirements of quality of service and / or deployment location. For example, meeting the requirements of quality of service can include meeting the requirements of QoS, or meeting the requirements of N6 latency, etc.

[0351] Optionally, the first type of service can include at least one of the following services:

[0352] 1. A service requiring low N6 latency;

[0353] For the service requiring low N6 latency, refer to the description in step 300 above, which will not be repeated here.

[0354] 2. A service deployed in a cloud server or a remote server;

[0355] For the service deployed in a cloud server or a remote server, refer to the description in step 300 above, which will not be repeated here.

[0356] 3. A service requiring low N6 latency and deployed in a cloud server or a remote server.

[0357] 4. A service requiring guaranteed QoS.

[0358] The requirement of guaranteed QoS can also be referred to as having requirements for QoS, or considering QoS, or requiring consideration of QoS, or indicating consideration of QoS, or EAS discovery based on QoS.

[0359] 5. A service requiring guaranteed QoS and deployed in a cloud server or a remote server.

[0360] Optionally, in the embodiments of the present application, the data network access identifier corresponding to the first service does not include the data network access identifier corresponding to the terminal, or the data network access identifier corresponding to the first service is different from the data network access identifier corresponding to the terminal.

[0361] Since the data network access identifier can be used to represent the geographical location, one service can correspond to one or more data network access identifiers, and the one or more data network access identifiers corresponding to the service are related to the deployment location of the application server of the service; in the case that the data network access identifier corresponding to the first service does not include the data network access identifier corresponding to the terminal, or the data network access identifier corresponding to the first service is different from the data network access identifier corresponding to the terminal, it can be indicated that the terminal is far away from the application server of the first service.

[0362] In the present application, the SMF network element can determine that the first service is a first type of service under different circumstances. The following will be introduced in different circumstances.

[0363] Case 1: After the SMF network element receives the user plane configuration indication sent by the second network element, it determines that the first service is a first type of service.

[0364] In case 1, the second network element can be an AF network element.

[0365] The AF network element sends a user plane configuration indication to the SMF network element, which is used to instruct the SMF network element to configure a user plane for the first service. Correspondingly, the SMF network element receives the user plane configuration indication from the AF network element.

[0366] Optionally, the user plane configuration indication can be sent directly by the AF network element to the SMF network element, or can be forwarded by the AF network element to the SMF network element through other network elements, such as NEF, UDR, PCF, etc. In the forwarding process, the user plane configuration indication can be carried by different messages. Optionally, in the forwarding process, the user plane configuration indication itself can also change, but its function does not change, for example, the name of the user plane configuration indication changes in the forwarding process, but its function is to instruct the SMF network element to configure a user plane for the first service.

[0367] The SMF network element can determine that the first service is a first type of service according to different ways, which will be introduced as follows.

[0368] Service type determination method 1: the SMF network element receives third indication information from the AF network element, and the third indication information is used to indicate that the first service is a first type of service. Correspondingly, the AF network element sends the third indication information to the SMF network element.

[0369] Optionally, the third indication information can be directly sent by the AF network element to the SMF network element, or can be forwarded by the AF network element to the SMF network element through other network elements, for example, through the forwarding of NEF, UDR, PCF and other network elements. In the forwarding process, the third indication information can be carried by different messages, such as Nnef_EASDeployment_Notify message, Nnef_EASDeployment_Create / Update message, and PCC rule message. Optionally, in the forwarding process, the third indication information itself can also change, but its role remains unchanged, for example, the name of the third indication information changes in the forwarding process, but its role is to indicate that the first service is a first type of service.

[0370] Optionally, the third indication information and the user plane configuration indication can be two independent information sent, or the third indication information can also be carried in the user plane configuration indication (it can be understood that the third indication information is added in the user plane configuration indication when the service is a first type of service, which is used to indicate that the service is a first type of service. For example, the third indication information corresponds to one or more of the address information of the server, FQDN, and data network access identifier, indicating that the address information or FQDN of the corresponding server is a first type of service).

[0371] Optionally, the third indication information and the user plane configuration indication can be carried in the same message or different messages.

[0372] Service type determination mode 2: the SMF network element determines that the first service is a first type of service according to the server deployment information of the first service.

[0373] Optionally, the SMF network element can receive the server deployment information of the first service sent by the AF network element, or the SMF network element can obtain the locally stored server deployment information of the first service.

[0374] The server deployment information can include but is not limited to at least one of the following:

[0375] The address information of the server, the DNS server information, the FQDN information, the data network access identifier, the DNN, the S-NSSAI, and the service type indication information, which is used to indicate that the corresponding service is a first type of service. For example, the service type indication information corresponds to one or more of the address information of the server, FQDN, and data network access identifier, indicating that the address information or FQDN of the corresponding server is a first type of service. The data network access identifier can be the data network access identifier corresponding to the service, and the DNN and S-NSSAI can be the DNN and S-NSSAI corresponding to the service.

[0376] In a manner that the SMF network element determines the first service as the first type of service according to the server deployment information of the first service:

[0377] For example, the server deployment information can include the first service indication information. When the first service indication information is included in the server deployment information of the first service, it can be determined that the first service is the first type of service.

[0378] For another example, the SMF network element can determine the first service as the first type of service according to the server deployment information of the first service sent by the AF network element and the local configuration. The local configuration can be the service identification information of the service belonging to the first type of service configured locally by the SMF network element. For example, the local configuration includes the data network access identifier of the service belonging to the first type of service, or the FQDN of the service belonging to the first type of service, or the application server address information of the service belonging to the first type of service. After the SMF network element obtains the server deployment information of the first service from the AF network element, the data network access identifier or the FQDN information or the application server address information in the server deployment information of the first service is used to determine whether the first service is the first type of service according to the local configuration. For example, if the local configuration includes the data network access identifier of the service belonging to the first type of service, and the data network access identifier of the first service is the same as the data network access identifier included in the local configuration, it is determined that the first service is the first type of service.

[0379] For another example, the data network access identifier of the first type of service can be a special data network access identifier. After the SMF network element obtains the data network access identifier of the first service from the AF network element, if the data network access identifier of the first service is a special data network access identifier, it can be determined that the first service is the first type of service.

[0380] Optionally, the user plane configuration indication sent by the AF network element to the SMF network element can further include at least one of the FQDN information corresponding to the first service, the address information of the application server corresponding to the first service, and the data network access identifier corresponding to the first service.

[0381] For the above case 1, after the terminal establishes the PDU session, the terminal can access the first service based on the PDU session. After the terminal initiates the first service, the AF network element can send the user plane configuration indication to the SMF network element. Alternatively, for the above case 1, the AF network element can send the user plane configuration indication to the SMF network element before the terminal initiates the first service.

[0382] As a possible implementation manner, after receiving the user plane configuration indication sent by the AF network element, the SMF network element can perform user plane configuration.

[0383] As another possible implementation, the SMF network element can perform user plane configuration after receiving the fourth notification message from the first network element; wherein the fourth notification message indicates that the terminal initiates the first service. Optionally, the first network element can be an EASDF network element.

[0384] For example, the EASDF network element can send a fourth notification message to the SMF network element after determining that the first service currently initiated by the terminal hits the processing rule; it should be noted that the specific manner in which the EASDF network element determines that the first service currently initiated by the terminal hits the processing rule can be found in the description of step 302 above, and will not be repeated here.

[0385] Case 2: The SMF network element determines that the first service is a first type of service after receiving the PDU session establishment request sent by the terminal.

[0386] In case 2, when the terminal initiates the first service, the terminal requests to establish a PDU session for accessing the first service. The terminal sends a PDU session establishment request to the SMF; correspondingly, the SMF network element receives the PDU session establishment request sent by the terminal, and determines that the first service is a first type of service after receiving the PDU session request.

[0387] Optionally, the PDU session establishment request can include third indication information, and the third indication information is used to indicate that the first service initiated by the terminal is a first type of service.

[0388] For case 2, the AF network element can configure server deployment information of at least one service to the SMF network element, and indicate that the first service in the configured at least one service is a first type of service.

[0389] Optionally, the process in which the SMF network element obtains the server deployment information can be that the AF network element provides the server deployment information to the NEF, the NEF stores the server deployment information in the UDR, the SMF network element subscribes to the server deployment information from the NEF, and the NEF sends the server deployment information stored locally or obtained from the UDR to the SMF network element.

[0390] The manner in which the SMF network element determines the first service in the at least one service can refer to the various service type determination manners described in step 300 above.

[0391] In addition, the AF network element instructs the PCF network element to distinguish the first service from other services in a UE route selection policy (URSP) of a terminal policy. Optionally, the AF network element sends a policy configuration instruction to the PCF network element; the policy configuration instruction can include fourth indication information, and the fourth indication information is used to indicate that the first service is a first type of service. In addition, optionally, the policy configuration instruction can also include an FQDN corresponding to the first service and / or a data network access identifier.

[0392] Correspondingly, the PCF network element receives the policy configuration instruction sent by the AF network element, and configures the first service as a first type of service in a URSP policy of a terminal when configuring the URSP policy of the terminal; optionally, the FQDN corresponding to the first service and / or the data network access identifier can also be configured in the URSP policy of the terminal.

[0393] When the terminal initiates the first service, the terminal requests to establish a PDU session for accessing the first service. The PDU session establishment request sent by the terminal to the SMF includes third indication information, and the third indication information is used to indicate that the first service initiated by the terminal is a first type of service.

[0394] Optionally, the PDU session establishment request can also include the FQDN corresponding to the first service and / or the data network access identifier.

[0395] After receiving the PDU session establishment request sent by the terminal, the SMF network element determines, according to the third indication information included in the PDU session establishment request, that the first service is a first type of service.

[0396] Step 901: The session management network element configures a user plane path corresponding to the first service according to a data network access identifier corresponding to the first service.

[0397] In step 901, the SMF network element configures a user plane path corresponding to the first service according to a data network access identifier corresponding to the first service.

[0398] First, the way in which the SMF network element determines the data network access identifier corresponding to the first service is introduced.

[0399] The way in which the SMF network element determines the data network access identifier corresponding to the first service is introduced below in combination with the content of step 600.

[0400] For case 1 in step 900:

[0401] If the AF network element sends the data network access identifier corresponding to the first service to the SMF network element in the user plane configuration indication, the SMF network element can determine the data network access identifier corresponding to the first service according to the user plane configuration indication.

[0402] If the AF network element does not send the data network access identifier corresponding to the first service to the SMF network element in the user plane configuration indication, the SMF network element can determine the data network access identifier corresponding to the first service according to the FQDN information and / or the address information of the application server corresponding to the first service, and the server deployment information of the first service.

[0403] Optionally, the data network access identifier corresponding to the first service is different from the data network access identifier corresponding to the terminal.

[0404] For the case 2 in step 900:

[0405] If the terminal sends the data network access identifier corresponding to the first service to the SMF network element in the PDU session establishment request, the SMF network element can determine the data network access identifier corresponding to the first service according to the PDU session establishment request.

[0406] If the terminal does not send the data network access identifier corresponding to the first service to the SMF network element in the PDU session establishment request, or the SMF network element determines that the data network access identifier corresponding to the first service included in the PDU session establishment request is inappropriate, the SMF network element can determine the data network access identifier corresponding to the first service according to the FQDN information corresponding to the first service, and the server deployment information of the first service.

[0407] The SMF network element configures the user plane path corresponding to the first service according to the following manner:

[0408] The SMF network element determines the third user plane network element used to establish the user plane path corresponding to the first service according to the data network access identifier corresponding to the first service, and instructs the third user plane network element to establish the user plane path through which the data flow corresponding to the first service is transmitted.

[0409] The user plane path can be the user plane path of the session of the terminal, through which the terminal accesses the first service, or the data packet of the terminal accessing the first service is carried by the session.

[0410] The third user plane network element can be one or more, for example, the third user plane network element includes the ULCL / BP and L-PSA of the session, and the data packet of the terminal accessing the first service passes through the ULCL / BP and L-PSA.

[0411] The manner of establishing the user plane path can be that the SMF network element instructs a third user plane network element to establish an N4 context, allocates tunnel information for a session corresponding to the first service, and sends tunnel information of other user plane network elements or access network devices serving the session corresponding to the first service to the third user plane network element, instructing the third user plane network element to forward data packets according to the tunnel information. The session corresponding to the first service refers to that data packets of the terminal accessing the first service are transmitted through the session, and the session is referred to as the session corresponding to the first service.

[0412] Optionally, the SMF network element instructing the third user plane network element to establish the user plane path comprises that the SMF network element sends an N4 session establish / modification request message to the third user plane network element, wherein the N4 session establish / modification request message comprises a PDR and a FAR.

[0413] Illustratively, the third user plane network element is an ULCL / BP and / or an L-PSA.

[0414] In implementation, the data network access identifier corresponding to the first service can correspond to one or more second candidate user plane network elements.

[0415] When the data network access identifier corresponding to the first service corresponds to one second candidate user plane network element, the SMF network element can take the second candidate user plane network element as the third user plane network element.

[0416] When the data network access identifier corresponding to the first service corresponds to multiple second candidate user plane network elements, the SMF network element can determine the third user plane network element according to a time delay between at least one second candidate user plane network element and an application server corresponding to the first service, wherein the at least one second candidate user plane network element corresponds to the data network access identifier corresponding to the first service, and the application server corresponding to the first service corresponds to the data network access identifier corresponding to the first service.

[0417] Illustratively, the time delay between the second candidate user plane network element and the application server corresponding to the first service can be an N6 time delay. The SMF network element can determine an N6 time delay corresponding to each second candidate user plane network element (i.e., a time delay between each second candidate user plane network element and an application server corresponding to a service), and determine the third user plane network element according to the N6 time delay corresponding to each second candidate user plane network element.

[0418] Optionally, the third user plane network element can be a user plane network element having the lowest time delay between the at least one second candidate user plane network element and the application server corresponding to the first service. Illustratively, the SMF network element can select a second candidate user plane network element having the lowest corresponding N6 time delay from the multiple second candidate user plane network elements as the third user plane network element.

[0419] The communication method of the embodiment of the application shown in FIG. 10 is described below in conjunction with examples.

[0420] Example 4:

[0421] Take the SMF network element as the session management network element and the AF network element as the second network element as an example for description.

[0422] The communication method flow shown in FIG. 10 can include the following steps. It can be understood that the steps and the execution order shown in FIG. 10 are only as an example, and in actual implementation, part of the steps or the remaining steps can be executed, and similarly, the execution order of the steps can also be adjusted, which is not limited in the embodiment of the application.

[0423] Step 1000: The terminal requests to establish a PDU session.

[0424] Step 1001: The terminal accesses the application server of the first service through the established PDU session.

[0425] In implementation, the terminal can send data of the first service based on the PDU session; wherein the first UPF network element can be a UPF network element configured when the PDU session of the terminal is established.

[0426] It should be noted that the above step 1000 and step 1001 are optional steps.

[0427] Step 1002: The AF network element can send a user plane configuration indication to the SMF network element.

[0428] The user plane configuration indication can include third indication information, and the third indication information is used to indicate that the first service is a first type of service. Optionally, the user plane configuration indication can also include at least one of the FQDN information corresponding to the first service, the address information of the application server corresponding to the first service, and the DNAI corresponding to the first service.

[0429] Step 1003: The SMF network element configures a user plane path corresponding to the first service according to the DNAI corresponding to the first service.

[0430] Optionally, the SMF network element determines the third user plane network element, such as the ULCL / BP network element and the Remote PSA, according to the DNAI corresponding to the first service.

[0431] Step 1004: The data of the first service sent by the terminal is sent to the application server of the first service through the ULCL / BP network element and the Remote PSA.

[0432] Example 5:

[0433] Taking the session management network element as the SMF network element and the second network element as the AF network element as an example, the following is described.

[0434] The communication method flow shown in FIG. 11 can include the following steps. It can be understood that the steps and the execution order shown in FIG. 11 are only as an example. In actual implementation, part of the steps or the remaining steps can be executed. Similarly, the execution order of the steps can also be adjusted. The embodiments of the present application do not limit this.

[0435] Step 1100: The AF network element sends server deployment information of at least one service to the SMF network element.

[0436] The at least one service includes a first service, and the first service is a first type of service. For details, refer to the description of the first type of service above.

[0437] Step 1101: The AF network element sends a policy configuration indication to the PCF network element.

[0438] The AF network element indicates the PCF network element to distinguish the first service from other services in a UE route selection policy (URSP) of a terminal policy through the policy configuration indication.

[0439] The policy configuration indication can include fourth indication information, and the fourth indication information is used to indicate that the first service is a first type of service. In addition, the policy configuration indication can also include a FQDN and / or a DNAI corresponding to the first service.

[0440] Step 1102: The PCF network element configures a terminal policy for the terminal.

[0441] The URSP policy of the terminal is configured to indicate that the first service is a first type of service. Optionally, the URSP policy of the terminal can also be configured to include a FQDN and / or a DNAI corresponding to the first service.

[0442] Step 1103: The terminal sends a PDU session establishment request to the SMF network element.

[0443] The PDU session establishment request can include third indication information, and the third indication information is used to indicate that the first service initiated by the terminal is a first type of service. Optionally, the PDU session establishment request can also include a FQDN and / or a DNAI corresponding to the first service.

[0444] Step 1104: The SMF network element configures a user plane path corresponding to the first service according to a DNAI corresponding to the first service.

[0445] Optionally, the SMF network element determines a third user plane network element according to the DNAI corresponding to the first service, such as a PSA shown in FIG. 11.

[0446] Step 1105: The SMF network element sends a PDU session establishment completion message to the terminal.

[0447] Step 1106: The terminal sends data of the first service to an application server of the first service through the PSA.

[0448] Based on the same technical concept, the embodiments of the present application provide a communication apparatus, which comprises a module / unit / means for executing the method performed by any network function and entity in the above method embodiments. The module / unit / means can be implemented by software or hardware, or by executing corresponding software by hardware.

[0449] For example, referring to FIG. 12, the communication apparatus 1200 can comprise a communication unit 1201, and further comprise a processing unit 1202.

[0450] For example, when the communication apparatus 1200 is or is located at a session management function network element:

[0451] The processing unit 1202 is configured to acquire a data network access identifier of a first service, and determine that the first service is a first type of service, the first type of service being a service meeting a quality of service requirement and / or a deployment location requirement;

[0452] The communication unit 1201 is configured to instruct a first network element to create or update a processing rule of the first service for a terminal, the processing rule of the first service instructing the terminal to notify the session management network element when initiating the first service; and a data network access identifier corresponding to the first service is different from a data network access identifier corresponding to the terminal.

[0453] The communication unit 1201 is further configured to receive first notification information from the first network element, the first notification information instructing the terminal to initiate the first service.

[0454] For another example, when the communication apparatus 1200 is or is located at a session management function network element:

[0455] The processing unit 1202 is configured to acquire a data network access identifier of a first service, and determine that the first service is a first type of service, the first type of service being a service meeting a quality of service requirement and / or a deployment location requirement;

[0456] The communication unit 1201 is configured to send second indication information to a second user plane network element, the second indication information being used to indicate a splitting rule of a first service of a terminal, a corresponding data network access identifier of the first service being different from a corresponding data network access identifier of the terminal.

[0457] For another example, when the communication apparatus 1200 is or is located at a session management function network element:

[0458] The processing unit 1202 is configured to determine that the first service is a first type of service, the first type of service being a service meeting a quality of service requirement and / or a deployment location requirement, and configure a user plane path corresponding to the first service according to a data network access identifier corresponding to the first service.

[0459] The communication unit 1201 is configured to communicate with other network elements or terminals or other devices.

[0460] For more details about the communication unit 1201 and the processing unit 1202, refer to the related description in the above method embodiments.

[0461] Based on the same technical concept, the embodiments of the present application also provide a communication apparatus, as shown in FIG. 13, the communication apparatus 1300 includes a processor 1301 and a memory 1302; the memory 1302 is configured to store computer execution instructions; the processor 1301 is configured to execute the computer execution instructions stored in the memory 1302, so that the communication apparatus implements the functions of any network function and entity in the above method embodiments, such as the functions of the session management network element in the above method embodiments.

[0462] The number of the memory 1302 can be one or more. The memory 1302 can include a read only memory (ROM), a random access memory (RAM) and a disk memory, etc. The memory 1302 can be used to store program codes required by the processor 1301 to perform tasks, and can also be used to store data, etc. The memory 1302 is an optional functional module rather than a mandatory functional module.

[0463] The processor 1301 and the memory 1302 can be connected through a bus, or can also be connected with the processor through a dedicated connection line, which is not limited here.

[0464] The codes corresponding to the methods shown in the foregoing embodiments are fixed into the chip by programming the processor 1301, so that the chip can execute the methods shown in the foregoing embodiments at runtime. How to program the processor 1301 is a technology known to those skilled in the art, and will not be described here.

[0465] It should be understood that the processor mentioned in the embodiments of the present application can be implemented by hardware or software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented by software, the processor can be a general-purpose processor, which is implemented by reading software codes stored in a memory.

[0466] For example, the processor can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0467] It should be appreciated that the memory mentioned in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable Programmable ROM (EPROM), an Electrically EPROM (EEPROM), or a flash memory. The volatile memory can be a Random Access Memory (RAM) used as an external cache. By way of example and not limitation, many forms of RAM can be used, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0468] It should be noted that when the processor is a general processor, a DSP, an ASIC, a FPGA or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, the memory (storage module) can be integrated in the processor.

[0469] It should be noted that the memory described in the present application is intended to include but not limited to these and any other suitable types of memory.

[0470] Based on the same technical concept, the embodiments of the present application also provide a computer readable storage medium for storing instructions, when the instructions are executed, the method performed by the functions of any of the network functions and entities in the above method embodiments is realized.

[0471] Based on the same technical concept, the embodiments of the present application also provide a chip coupled with a memory, for reading and executing program instructions stored in the memory, to realize the method performed by the functions of any of the network functions and entities in the above method embodiments.

[0472] Based on the same technical concept, the embodiments of the present application also provide a computer program product containing instructions, and the computer program product stores the instructions, which, when running on a computer, enable the computer to perform the method executed by the functions of any of the network functions and entities in the above method embodiments.

[0473] Those skilled in the art will appreciate that embodiments of the present application can be in the form of hardware embodiments, software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of the present application can be in the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk memory, CD-ROMs, optical storage media, etc.) embodying computer-readable program code.

[0474] The present application is described with reference to the flowcharts and / or block diagrams of the methods, apparatus (systems), and computer program products according to this application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, as well as combinations of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing apparatus to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus generate means for implementing the functions specified in one or more flows in the flowcharts and / or one or more blocks in the block diagrams.

[0475] These computer program instructions can also be stored in a computer-readable memory that can direct the computer or other programmable data processing apparatus to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including instruction means, which implements the functions specified in one or more flows in the flowcharts and / or one or more blocks in the block diagrams.

[0476] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus, so that a series of operation steps are performed on the computer or other programmable data processing apparatus to produce a computer-implemented process, so that the instructions executed on the computer or other programmable data processing apparatus provide steps for implementing the functions specified in one or more flows in the flowcharts and / or one or more blocks in the block diagrams.

[0477] Obviously, those skilled in the art can make various modifications and variations to the present application without departing from the scope and spirit of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A communication method characterized by comprising: The method applied to a session management network element comprises: obtaining a data network access identifier of a first service, and determining that the first service is a first type of service, the first type of service being a service meeting a quality of service and / or a deployment location requirement; instructing a first network element to create or update a processing rule of the first service for a terminal, the processing rule of the first service instructing the terminal to notify the session management network element when the terminal initiates the first service, a corresponding data network access identifier of the first service being different from a corresponding data network access identifier of the terminal; receiving first notification information from the first network element, the first notification information instructing the terminal to initiate the first service.

2. The method of claim 1, wherein, The method further comprises: determining that the terminal supports the first type of service, or determining that the terminal is authorized to access the first type of service.

3. The method of claim 1 or 2, wherein, The processing rule comprises full address domain name (FQDN) information corresponding to the first service; or The processing rule comprises address information of an application server corresponding to the first service.

4. The method of any of claims 1-3, wherein, The determination that the first service is the first type of service comprises: receiving first instruction information from a second network element, the first instruction information being used to instruct that the first service is the first type of service; or determining that the first service is the first type of service according to a data network access identifier of the first service; or determining that the first service is the first type of service according to server deployment information of the first service sent by a second network element.

5. The method of any of claims 1-4, wherein, The method further comprises: receiving second notification information from the first network element, the second notification information being used to instruct address information of an application server corresponding to the first service; determining at least one first candidate user plane network element corresponding to the address information of the application server, and selecting a first user plane network element from the at least one first candidate user plane network element according to a time delay between each first candidate user plane network element and the application server corresponding to the first service; configuring a user plane path corresponding to the first service according to the first user plane network element.

6. The method of claim 5, wherein, The determination of the at least one first candidate user plane network element corresponding to the address information of the application server comprises: determining at least one data network access node corresponding to the address information of the application server according to server deployment information of the first service sent by a second network element; determining a target data network access node from the at least one data network access node; determining a user plane network element corresponding to the target data network access node as the at least one first candidate user plane network element.

7. The method of claim 6, wherein, The determination of the target data network access node from the at least one data network access node comprises: determining a target data network access node from the at least one data network access node according to a time delay between each data network access node and the application server corresponding to the first service.

8. The method of any of claims 1-7, wherein, The first type of service comprises any one of: a service requiring low N6 latency; a service deployed on a cloud server or a remote server; a service requiring low N6 latency and deployed on a cloud server or a remote server; a service requiring guaranteed quality of service (QoS); a service requiring guaranteed QoS and deployed in a cloud server or a remote server.

9. A communication method characterized by comprising: The method is applied to a session management network element, and the method comprises: obtaining a data network access identifier of a first service, and determining that the first service is a first type of service, the first type of service being a service meeting a quality of service requirement and / or a deployment location requirement; sending second indication information to a second user plane network element, the second indication information being used for indicating a split rule of a first service of a terminal, a corresponding data network access identifier of the first service being different from a corresponding data network access identifier of the terminal.

10. The method of claim 9, wherein, The method further comprises: determining that the terminal supports the first type of service, or determining that the terminal is authorized to access the first type of service.

11. The method of claim 9 or 10, wherein, The determination that the first service is the first type of service comprises: receiving first indication information from a second network element, the first indication information being used for indicating that the first service is the first type of service; or determining that the first service is the first type of service according to a data network access identifier of the first service; or determining that the first service is the first type of service according to server deployment information of the first service sent by a second network element.

12. The method of any of claims 9-11, wherein, The first type of service comprises any one of: a service requiring low N6 latency; a service deployed in a cloud server or a remote server; a service requiring low N6 latency and deployed in a cloud server or a remote server; a service requiring guaranteed quality of service (QoS); a service requiring guaranteed QoS and deployed in a cloud server or a remote server.

13. A method of communication, comprising: The method is applied to a session management network element, and the method comprises: determining that a first service is a first type of service, the first type of service being a service meeting a quality of service requirement and / or a deployment location requirement; configuring a user plane path corresponding to the first service according to a data network access identifier corresponding to the first service.

14. The method of claim 13, wherein, The first type of service comprises any one of: a service requiring low N6 latency; a service deployed in a cloud server or a remote server; a service requiring low N6 latency and deployed in a cloud server or a remote server; a service requiring guaranteed quality of service (QoS); a service requiring guaranteed QoS and deployed in a cloud server or a remote server.

15. The method of claim 13 or 14, wherein, A corresponding data network access identifier of the first service is different from a corresponding data network access identifier of the terminal.

16. The method of any of claims 13-15, wherein, The determination that the first service is the first type of service comprises: receiving third indication information from a second network element, the third indication information being used for indicating that the first service is the first type of service; or determining that the first service is the first type of service according to server deployment information of the first service.

17. The method of claim 16, wherein, The second indication information is carried in user plane configuration indication sent by the second network element, the user plane configuration indication being used for indicating that a user plane path is configured for the first service; The user plane configuration indication further comprises full domain name (FQDN) information corresponding to the first service and / or address information of an application server corresponding to the first service.

18. The method of claim 17, wherein, The user plane configuration indication further includes a data network access identifier corresponding to the first service.

19. The method of claim 17, wherein, The method further includes: determining the data network access identifier corresponding to the first service according to the FQDN information and / or the address information of the application server corresponding to the first service, and the server deployment information of the first service.

20. The method of any of claims 13-19, wherein, The method further includes: receiving a fourth notification message from the first network element, the fourth notification message indicating that the terminal initiates the first service.

21. The method of claim 16, wherein, The second indication information is carried in a protocol data unit (PDU) session establishment request sent by the terminal, the PDU session establishment request being used to request establishment of a PDU session carrying service data of the first service. The PDU session establishment request further includes FQDN information corresponding to the first service.

22. The method of claim 21, wherein, The PDU session establishment request further includes a data network access identifier corresponding to the first service.

23. The method of claim 21, wherein, The method further includes: determining the data network access identifier corresponding to the first service according to the FQDN information corresponding to the first service and the server deployment information of the first service.

24. The method of any of claims 13-23, wherein, The configuring the user plane path corresponding to the first service according to the data network access identifier corresponding to the first service includes: determining a third user plane network element for establishing the user plane path corresponding to the first service according to the data network access identifier corresponding to the first service; indicating the third user plane network element to establish the user plane path through which data flow of the first service is transmitted.

25. The method of claim 24, wherein, The determining the third user plane network element for establishing the user plane path corresponding to the first service according to the data network access identifier corresponding to the first service includes: determining the third user plane network element according to a time delay between at least one second candidate user plane network element and the application server corresponding to the first service; The at least one second candidate user plane network element corresponds to the data network access identifier corresponding to the first service. The application server corresponding to the first service corresponds to the data network access identifier corresponding to the first service.

26. The method of claim 24, wherein, The third user plane network element is a user plane network element having the lowest time delay between the at least one second candidate user plane network element and the application server corresponding to the first service; the at least one second candidate user plane network element corresponds to the data network access identifier corresponding to the first service; and the application server corresponding to the first service corresponds to the data network access identifier corresponding to the first service.

27. A communications device, characterized by The method includes a module or unit for performing the method of any one of claims 1-8, or a module or unit for performing the method of any one of claims 9-12, or a module or unit for performing the method of any one of claims 13-26.

28. A communications device, characterized by comprises one or more processors; the one or more processors are configured to execute a computer program in a memory, so that the communication device executes the method according to any one of claims 1-8, or so that the communication device executes the method according to any one of claims 9-12, or so that the communication device executes the method according to any one of claims 13-26.

29. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, and when the computer program or instructions are executed by a computer, the method according to any one of claims 1-8, or the method according to any one of claims 9-12, or the method according to any one of claims 13-26 is implemented.

30. A computer program product, characterised in that, When the computer program product is read and executed by the computer, the computer executes the method according to any one of claims 1-8, or the method according to any one of claims 9-12, or the method according to any one of claims 13-26.

Images