Communication method, device and system

Abstract

The embodiment of the invention discloses a communication method, device and system, relates to the technical field of communication, and helps to reduce the pressure of a session management function network element for processing a request for an edge application service. The method comprises: a session management function network element obtaining application information signed by a terminal device, the application information comprising at least one of the following items: a full domain name, an application identifier, or a data network access identifier; the session management function network element selects a target first network element according to the application information; wherein the first network element is used for selecting a local user plane function network element and / or an edge application service.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to communication methods, devices, and systems. Background Art

[0002] For some services with low latency and large bandwidth requirements, such as virtual reality (VR), cloud gaming, or industrial automation, etc., deploying application services at the network edge can provide users with a better service experience. Such application services deployed at the network edge can be referred to as edge application services (EAS).

[0003] Currently, the session management function network element (SMF) can centrally process requests from terminal devices for edge application services. However, this centralized processing method consumes more network resources and is more suitable for scenarios with a small number of EAS. In scenarios with a large number of EAS, this method is no longer suitable. Therefore, how to reduce the overhead of selecting an EAS in scenarios with a large number of EAS is an unsolved problem at present. Summary of the Invention

[0004] Embodiments of this application provide communication methods, devices, and systems, which can select a first network element to share the pressure of the session management function network element in selecting edge application services and / or local user plane function network elements, and reduce resource overhead.

[0005] Embodiments of this application adopt the following technical solutions:

[0006] In a first aspect, a communication method is provided. This method can be executed by a session management function network element, or by a component of a session management function network element (such as a processor, a chip, or a chip system, etc.), or by a logical module or software that can implement all or part of the functions of a session management function network element. The following takes the session management function network element as the execution subject of this method for illustration. The method includes: The session management function network element obtains application information subscribed by the terminal device, and the application information includes at least one of the following: fully qualified domain name, application identifier, or data network access identifier. The session management function network element selects a target first network element according to the application information; wherein, the first network element is used to select a local user plane function network element and / or an edge application service.

[0007] Wherein, selecting an edge application service can also be referred to as determining an edge application service. In some scenarios, selecting an edge application service can also be understood as reselecting an edge application service.

[0008] Based on the communication method provided in the embodiments of the present application, the session management function network element can select a first network element according to the application information subscribed by the terminal device, and the selected first network element can select a local user plane function network element and / or an edge application service. The embodiments of the present application not only provide a more fine-grained network element selection method, but also this method of distributed selection of the local user plane function network element and / or the edge application service by the first network element can effectively relieve the pressure of centralized processing of the session management function network element, and can also reduce resource overhead in scenarios where there are many edge application services and / or local user plane function network elements.

[0009] In a possible implementation manner, the session management function network element selects a target first network element according to the application information, including: the session management function network element sends a first request message to the network storage function network element, and the first request message includes the application information, and the first request message is used to request the network storage function network element to select a target first network element. Then, the session management function network element receives a first response message for the first request message from the network storage function network element, and the first response message includes information about the target first network element.

[0010] This solution provides a specific method for selecting a target first network element.

[0011] In a possible implementation manner, the first request message further includes information about a first area, and the information about the first area is used for the network storage function network element to select a target first network element, and the first area is related to the location of the terminal device.

[0012] Based on this solution, the network storage function network element can also refer to the information of a specific area to select a target first network element, and can select a target first network element suitable for selecting an edge application service and / or a local user plane function network element for the terminal device.

[0013] In a possible implementation manner, the first request message further includes first indication information, and the first indication information is used to indicate that the network element requested to be selected is a first network element.

[0014] Based on this solution, the network storage function network element can be directly instructed to select a first network element through the first indication information.

[0015] In a possible implementation manner, the first request message includes second indication information, and the second indication information is used to indicate that the requested network service is to select a user plane function network element or to establish a session.

[0016] In a possible implementation manner, the session management function network element selects a target first network element according to the application information, including: the session management function network element selects a target first network element according to the mapping relationship between the locally configured application information and the first network element.

[0017] This solution provides a specific method for selecting a target first network element.

[0018] In a possible implementation, the session management function network element selects a target first network element according to application information, including: the session management function network element determines a target data network access identifier and / or the IP address of the target edge application service according to the application information and the deployment information of the edge application service; wherein, the deployment information of the edge application service includes the corresponding relationship between the application information and the data network access identifier and / or the IP address of the edge application service. The session management function network element selects the target first network element according to the target data network access identifier and / or the IP address of the target edge application service.

[0019] This solution provides a specific method for selecting a target first network element.

[0020] In a possible implementation, the method further includes: the session management function network element sends a second request message to the target first network element, and the second request message is used to request the target first network element to select a target edge application service and / or a target user plane function network element.

[0021] In a possible implementation, the second request message includes application information, and the application information is used for the target first network element to select a target edge application service and / or a target user plane function network element.

[0022] Based on this solution, the target first network element can select a target edge application service and / or a target user plane function network element with reference to the application information, and can select a suitable target edge application service and / or target user plane function network element.

[0023] In a possible implementation, the application information further includes one or more of the following information: the delay requirement for the transmission between the user plane function network element and the edge application service, or the load requirement for the user plane function network element.

[0024] Based on this solution, the target first network element can also select a target edge application service and / or a target user plane function network element with reference to the delay factor and / or the load factor, and can avoid selecting an edge application service and / or a user plane function network element with too large transmission delay or too large load, which affects the user experience.

[0025] In a possible implementation, the method further includes: the session management function network element receives a second response message from the target first network element for the second request message, and the second response message includes information about the target user plane function network element.

[0026] In a possible implementation, the method further includes: The session management function network element receives a third request message from the access and mobility management function network element, and the third request message is used to request the establishment of a session context. The session management function network element determines to select a target first network element according to the third request message.

[0027] Based on this solution, the session management function network element can select a target first network element in the scenario of session establishment.

[0028] In a second aspect, a communication method is provided. This method can be executed by the access and mobility management function network element, or by components of the access and mobility management function network element (such as a processor, a chip, or a chip system, etc.), or can also be implemented by a logic module or software that can implement all or part of the functions of the access and mobility management function network element. The following takes the access and mobility management function network element as the execution entity of this method as an example for description. The method includes: The access and mobility management function network element receives a session establishment request message from a terminal device. The access and mobility management function network element selects a target first network element according to a first parameter; the first network element is used to select an edge application service, and the first parameter includes one or more of the following information: data network name, information about a slice associated with the application, information about a first area, where the first area is related to the location of the terminal device.

[0029] Based on the communication method provided in the embodiments of this application, the access and mobility management function network element can select a first network element according to the first parameter, and the selected first network element can select a local user plane function network element and / or an edge application service. The embodiments of this application not only provide a more fine-grained network element selection method, but also this method of distributedly selecting a local user plane function network element and / or an edge application service by the first network element can effectively relieve the pressure of centralized processing of the session management function network element, and can also reduce resource overhead in scenarios where there are many edge application services and / or local user plane function network elements.

[0030] In a possible implementation, the method further includes: The access and mobility management function network element determines to select a session management network element according to the session establishment request message. The access and mobility management function network element selects a target first network element according to the first parameter, including: when the access and mobility management function network element selects a session management network element according to the first parameter, it selects a target first network element.

[0031] Based on this solution, the access and mobility management function network element can select a first network element in the scenario of session establishment.

[0032] In a third aspect, a communication method is provided. This method can be executed by a second network element, or by components of the second network element (such as a processor, a chip, or a chip system, etc.), or can be implemented by a logic module or software that can implement all or part of the functions of the second network element. Hereinafter, taking the second network element as the execution subject of this method as an example for description, the method includes: The second network element sends deployment information of an edge application service to a first network element serving a second area; wherein, the deployment information of the edge application service includes at least one of the following: a fully qualified domain name, an application identifier, an IP address of the edge application service, or a data network access identifier. Wherein, the first network element is used to select an edge application service and / or a local user plane function network element.

[0033] Based on the communication method provided in the embodiments of the present application, deployment information of an edge application service can be provided to a first network element serving a specific area. Compared with the method of centrally providing the deployment information of the edge application service to a session management function network element, this distributed providing method can effectively relieve the pressure of centralized processing of the session management function network element.

[0034] In a possible implementation manner, the second network element sends a fourth request message to a network storage function network element. The fourth request message is used to request to discover the first network element serving the second area, and the fourth request message includes information indicating the second area. The second network element receives information of the first network element serving the second area from the network storage function network element. The second network element sends deployment information of the edge application service to a second network element serving a first area, including: The second network element sends deployment information of the edge application service to the first network element serving the second area according to the information of the first network element serving the second area.

[0035] Based on this solution, the second network element can request the network storage function network element to discover the first network element serving the second area, so that it can send the deployment information of the edge application service based on the feedback of the network storage function network element.

[0036] In a possible implementation manner, the fourth request message includes at least one of the following information: a third indication information, or a fourth indication information; wherein, the third indication information is used to indicate that the network element requested to be discovered is the first network element, and the fourth indication information is used to indicate that the requested service is to provide deployment information of the edge application service.

[0037] In a possible implementation manner, the method further includes: The second network element receives a fifth request message from the first network element. The fifth request message requests to subscribe to the deployment information of the edge application service; The second network element sends deployment information of the edge application service to the first network element serving the second area, including: The second network element sends deployment information of the edge application service to the first network element according to the fifth request message.

[0038] Based on this solution, the first network element serving a specific area can actively subscribe to the deployment information of the edge application service.

[0039] In a possible implementation, the fifth request message includes a second parameter, and the second parameter includes at least one of the following: fully qualified domain name, application identifier, or IP address of the edge application service. The second network element sends the deployment information of the edge application service to the first network element serving the second area, including: the second network element sends the deployment information of the edge application service corresponding to the second parameter to the first network element according to the fifth request message.

[0040] Based on this solution, the first network element can, according to its own needs, request the deployment information of the edge application service corresponding to specific parameters from the second network element. Correspondingly, the second network element can provide the first network element with the targeted deployment information of the edge application service.

[0041] In a fourth aspect, a communication method is provided. This method can be executed by an application function network element, or by a component (such as a processor, chip, or chip system, etc.) of the first network element, or by a logic module or software that can implement all or part of the functions of the first network element. The following takes the first network element as the execution entity of this method as an example for description. This method includes: the first network element sends a fifth request message to the second network element, and the fifth request message requests to subscribe to the deployment information of the edge application service. The first network element receives the deployment information of the edge application service from the second network element; wherein, the deployment information of the edge application service includes at least one of the following: fully qualified domain name, application identifier, IP address of the edge application service, or data network access identifier.

[0042] Based on the communication method provided in the embodiments of the present application, the first network element can actively subscribe to the deployment information of the edge application service. Compared with the method of centrally providing the deployment information of the edge application service to the session management function network element, this distributed providing method can effectively relieve the pressure of centralized processing of the session management function network element.

[0043] In a possible implementation, the fifth request message includes a second parameter, and the second parameter includes at least one of the following: fully qualified domain name, application identifier, or IP address of the edge application service. The first network element receives the deployment information of the edge application service from the second network element, including: the first network element receives the deployment information of the edge application service corresponding to the second parameter from the second network element.

[0044] Based on this solution, the first network element can, according to its own needs, request the deployment information of the edge application service corresponding to specific parameters from the second network element. Correspondingly, the second network element can provide the first network element with the targeted deployment information of the edge application service.

[0045] In a fifth aspect, a communication device is provided for implementing the various methods described above. The communication device includes corresponding modules, units, or means for implementing the above methods. The modules, units, or means may be implemented by hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0046] In some possible designs, the communication device may include a transceiver module and a processing module. The transceiver module, which may also be referred to as a transceiver unit, is used to implement the sending and / or receiving functions in the first aspect, the second aspect, the third aspect, or the fourth aspect and any possible implementation manners thereof. The transceiver module may be constituted by a transceiver circuit, a transceiver, a transceiver, or a communication interface. The processing module may be used to implement the processing functions in the first aspect, the second aspect, the third aspect, or the fourth aspect and any possible implementation manners thereof.

[0047] In some possible designs, the transceiver module includes a sending module and a receiving module, which are respectively used to implement the sending and receiving functions in the first aspect, the second aspect, the third aspect, or the fourth aspect and any possible implementation manners thereof.

[0048] In a sixth aspect, a communication device is provided, including: a processor and a communication interface; the communication interface is used to communicate with modules outside the communication device; the processor is used to execute a computer program or instruction to enable the communication device to execute the method in any of the above aspects.

[0049] In a seventh aspect, a communication device is provided, including: at least one processor; the processor is used to execute a computer program or instruction stored in a memory to enable the communication device to execute the method in any of the above aspects. In a possible implementation, the memory may be coupled to the processor, or may be independent of the processor. In a possible implementation, the communication device further includes the memory. Optionally, the memory and the processor are integrated together.

[0050] In the fifth to seventh aspects, the communication device may be the session management function network element in the first aspect above, or any implementation manner in the first aspect, or a device including the session management function network element above, or a device included in the session management function network element above, such as a chip. Alternatively, the communication device may be the access and mobility management function network element in the second aspect above, or any implementation manner in the second aspect, or a device including the access and mobility management function network element above, or a device included in the access and mobility management function network element above, such as a chip. Alternatively, the communication device may be the second network element in the third aspect above, or any implementation manner in the third aspect, or a device including the second network element above, or a device included in the second network element above, such as a chip. Alternatively, the communication device may be the first network element in the fourth aspect above, or any implementation manner in the fourth aspect, or a device including the first network element above, or a device included in the first network element above, such as a chip or a chip system.

[0051] In an eighth aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored. When it runs on a communication device, the communication device can execute the method of any of the above aspects or any of its implementation manners.

[0052] In a ninth aspect, a computer program product including instructions is provided. When it runs on a communication device, the communication device can execute the method of any of the above aspects or any of its implementation manners.

[0053] In a tenth aspect, a communication device (for example, the communication device may be a chip or a chip system) is provided. The communication device includes a processor for implementing the functions involved in any of the above aspects or any of its implementation manners.

[0054] In some possible designs, the communication device includes a memory for storing necessary program instructions and data.

[0055] In some possible designs, when the device is a chip system, it may be composed of chips or may also include chips and other discrete devices.

[0056] It can be understood that when the communication device provided in any of the fifth to seventh aspects is a chip, the above-mentioned sending action / function can be understood as output, and the above-mentioned receiving action / function can be understood as input.

[0057] Among them, for the technical effects brought by any implementation manner in the fifth to tenth aspects, reference can be made to the technical effects brought by the corresponding implementation manners in the first to fourth aspects, which will not be elaborated here.

[0058] Among them, it should be noted that various possible implementation manners of any one of the above aspects can be combined on the premise that the solutions do not conflict with each other.

[0059] In the eleventh aspect, a communication system is provided, and the communication system includes a first network element and a second network element. Among them, the second network element is used to send deployment information of an edge application service to the first network element, where the deployment information of the edge application service includes at least one of the following: fully qualified domain name, application identifier, IP address of the edge application service, or data network access identifier. The first network element is used to receive the deployment information of the edge application service. The first network element is further used to select an edge application service and / or a local user plane function network element.

[0060] In some possible designs, the first network element is further used to execute the method of any implementation manner of the above fourth aspect.

[0061] In some possible designs, the second network element is a network exposure function network element or an application function network element.

[0062] In some possible designs, the second network element is further used to execute the method of any implementation manner of the above third aspect.

[0063] In some possible designs, the communication system further includes a session management function network element, and the session management function network element is used to execute the method of any implementation manner of the above first aspect.

[0064] In some possible designs, the communication system further includes an access and mobility management function network element, and the access and mobility management function network element is used to execute the method of any implementation manner of the above second aspect. Description of the Drawings

[0065] Figure 1 Schematic diagram of the architecture of the communication system applicable to the embodiments of the present application;

[0066] Figure 2 Schematic flow diagram of a communication method provided by the embodiments of the present application;

[0067] Figure 3 Interaction diagram of another communication method provided by the embodiments of the present application;

[0068] Figure 4 Interaction diagram of another communication method provided by the embodiments of the present application;

[0069] Figure 5 Schematic flow diagram of the process for the SMF network element to select the SRF network element in the session establishment process provided by the embodiments of the present application;

[0070] Figure 6Schematic diagram of the process by which the AMF network element provided by the embodiment of the present application selects an I-SMF network element in the session establishment process;

[0071] Figure 7 Schematic diagram of the process by which the SMF network element provided by the embodiment of the present application selects an I-SMF network element in the session establishment process;

[0072] Figure 8 Schematic diagram of the process of providing EAS deployment information to the first network element provided by the embodiment of the present application;

[0073] Figure 9 Schematic diagram of the structure of a communication device provided by the embodiment of the present application;

[0074] Figure 10 Schematic diagram of the structure of another communication device provided by the embodiment of the present application. Detailed implementation manners

[0075] The embodiments of the present application provide a communication method, device, and system. The following introduces the specific implementation of the communication method provided by the embodiments of the present application. In the description of the embodiments of the present application, unless otherwise specified, " / " means that the objects associated before and after are in an "or" relationship. For example, A / B may represent A or B; "and / or" in the embodiments of the present application is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. Here, A and B can be singular or plural. Also, in the description of the present application, unless otherwise specified, "a plurality of" means two or more than two. "At least one (item)" or similar expressions below refer to any combination of these items, including any combination of single item (item) or plural items (items). For example, at least one (item) of a, b, or c may represent: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, c can be single or multiple. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same items or similar items with basically the same functions and effects. Those skilled in the art can understand that the words such as "first" and "second" do not limit the quantity and execution order, and the words such as "first" and "second" do not necessarily limit being different. At the same time, in the embodiments of the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations, or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Exactly, using words such as "exemplary" or "for example" is intended to present relevant concepts in a specific way for easy understanding.

[0076] In the embodiments of the present application, "indication" may include direct indication and indirect indication, and may also include explicit indication and implicit indication. If the information indicated by a certain piece of information is called the information to be indicated, then in the specific implementation process, there are many ways to indicate the information to be indicated. For example, but not limited to, the information to be indicated can be directly indicated, such as the information to be indicated itself or the index of the information to be indicated, etc. It is also possible to indirectly indicate the information to be indicated by indicating other information, where there is an association relationship between the other information and the information to be indicated. It is also possible to only indicate a part of the information to be indicated, while the other parts of the information to be indicated are known or pre-agreed. For example, it is also possible to use the arrangement order of each piece of information pre-agreed (such as protocol regulations) to achieve the indication of specific information, thereby reducing the indication overhead to a certain extent. At the same time, it is also possible to identify the common parts of each piece of information and indicate them uniformly to reduce the indication overhead caused by separately indicating the same information.

[0077] It should be understood that the information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately, and the sending cycles and / or sending opportunities of these sub-information can be the same or different. The specific sending method is not limited in the embodiments of the present application. Among them, the sending cycles and / or sending opportunities of these sub-information can be predefined, such as predefined according to the protocol, or can be configured by the sending device by sending configuration information to the receiving device.

[0078] In the embodiments of the present application, "predefined", "predefined", "preconfigured", "preconfigured" or "locally configured" can be implemented by pre-saving corresponding codes, tables or other ways that can be used to indicate relevant information in the device. For example, it can be burned into the device when the device leaves the factory, or configured when first accessing the network. The embodiments of the present application do not limit its specific implementation method. Among them, "saving" can mean saving in one or more memories. The one or more memories can be separately provided, or integrated in an encoder or decoder, a processor, or a communication device. The one or more memories can also be partially separately provided and partially integrated in a decoder, a processor, or a communication device. The type of the memory can be any form of storage medium, which is not limited in the embodiments of the present application.

[0079] In the embodiments of the present application, descriptions such as "when...", "in the case of...", "if" and "if" all refer to that the device will perform corresponding processing under a certain objective situation, which does not limit the time, and does not require the device to have a judgment action when implementing, nor does it mean that there are other limitations.

[0080] In the embodiments of the present application, "sending information to... (taking the first network element as an example)" can be understood as the destination of the information being the first network element. It may include directly or indirectly sending information to the first network element. "Receiving information from... (taking the first network element as an example)" can be understood as the source of the information being the first network element, and it may include directly or indirectly receiving information from the first network element. Necessary processing may be performed on the information between the source and destination of the information transmission, such as format conversion, etc., but the destination can understand the valid information from the source. Similar expressions in the embodiments of the present application can be understood similarly, and will not be elaborated here.

[0081] The technical solutions provided by the present application can be applied to various communication systems, such as Long Term Evolution (LTE) systems, 4th generation (4G) mobile communication systems, 5th generation (5G) mobile communication systems and their evolved systems, Non-Terrestrial Network (NTN) systems, Vehicle to Everything (V2X) systems, systems with hybrid networking of LTE and New Radio (NR), or Device-to-Device (D2D) systems, Machine-to-Machine (M2M) communication systems, Internet of Things (IoT), and future next-generation communication systems, such as 6th generation (6G) mobile communication systems, etc. In addition, the term "system" can be interchanged with "network".

[0082] It should be noted that the network architecture and service scenarios described in the embodiments of the present application are for more clearly explaining the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those of ordinary skill in the art know that with the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0083] It should be noted that the names of the network elements mentioned in this article are only possible exemplary names. If the actual names of the network elements in subsequent communication networks (such as 6G networks) are different from the names mentioned in this article, it will not affect the application of the communication methods provided by the embodiments of the present application.

[0084] Taking the application of the embodiments of the present application to a 5G system as an example, Figure 11A, 1B, 1C, and 1D in this figure are schematic diagrams of the architectures of possible and non - restrictive communication systems applicable to the embodiments of the present application. The communication system applicable to the embodiments of the present application includes a terminal device, a core network (CN), and an access network (AN). Logically, the core network can be divided into two parts: the user plane and the control plane. The control plane is responsible for the management of the mobile network, and the user plane is responsible for the transmission of service data.

[0085] As Figure 1 shown in 1A, 1B, 1C, and 1D in this figure, in this communication system, the user plane function (UPF) network element of the core network, together with the access network element ( Figure 1 AN in this figure) and the terminal device, jointly form the user plane network element of the 5G system (5GS). The core network control plane mainly includes the following network elements: the access and mobility management function (AMF) network element, the session management function (SMF) network element, the network exposure function (NEF) network element, the network repository function (NRF), the policy control function (PCF) network element, the application function (AF) network element, the unified data management (UDM) network element, and the edge application service discovery function (EASDF) network element.

[0086] As Figure 1 shown in 1A, 1B, 1C, and 1D in this figure, the communication system may also include an EAS. The EAS can be deployed in a data network (DN), such as a local data network. Optionally, the EAS can be controlled by an operator or a third party. Exemplarily, the entity providing the EAS can be a server. For example, in the mobile edge computing (MEC) scenario, the EAS can be provided by an edge computing server, or in other words, the EAS can be deployed on the edge computing server.

[0087] In the embodiments of the present application, the server providing the EAS can also be simply referred to as the EAS server.

[0088] As Figure 1As shown in 1A, 1B, 1C, and 1D, the communication system may further include a first network element. The first network element may be used to determine / select / reselect an edge application service (EAS) and / or a user plane function network element.

[0089] Taking the session management function network element executing the communication method provided in the embodiments of the present application as an example, a possible implementation of the communication method provided in the embodiments of the present application may include: The session management function network element obtains the application information subscribed by the terminal device, and the application information includes at least one of the following: fully qualified domain name (FQDN), application identity (App ID), or data network access identifier (DNAI). The session management function network element selects a target first network element according to the application information. The specific implementation and technical effects of this solution will be described in detail in the subsequent method embodiments and will not be elaborated here.

[0090] In some possible scenarios, the user plane function network element determined / selected / reselected by the first network element may be referred to as a local user plane function network element (local UPF, LUPF). Among them, the local user plane function network element is a user plane function network element connected to the edge application service (deployed in the DN). When the application that the terminal device hopes to access has deployed an edge application service in the DN close to the local user plane function network element, or the network provides an edge application service for the terminal device, the local user plane function network element may provide a connection for the terminal device.

[0091] Exemplarily, as Figure 1 shown in 1A, 1B, 1C, and 1D, the UPF network element connected to the EAS may be referred to as the local UPF in the present application, that is, the LUPF network element.

[0092] It can be understood that the local user plane function network element is an exemplary name provided by the embodiments of the present application for the user plane function network element connected to the EAS. If the actual name of the user plane function network element connected to the EAS in the communication system is not the local user plane function network element, it does not affect the application of the communication method provided by the embodiments of the present application, and the first network element in the embodiments of the present application can still determine / select / reselect the user plane function network element connected to the EAS.

[0093] Optionally, the first network element may be a newly defined network element. For example, the first network element may be referred to as a service routing function (SRF) network element, or a local session management function network element (local SMF, L-SMF). Alternatively, the first network element may also be an existing network element. For example, the first network element may be an intermediate session management function network element (intermediate SMF, I-SMF). When the terminal device is located in an area not managed by the session management network element, the intermediate session management function network element may be inserted to find a session management network element that supports the session.

[0094] Exemplarily, as Figure 1 shown in 1C, the first network element may be an I-SMF network element connected to the AMF network element. As Figure 1 shown in 1D, the first network element may be an I-SMF network element connected to the SMF network element.

[0095] In some possible architectures, the first network element may also manage the local user plane function network element and / or the edge application service. For example, Figure 1 the first network element in 1A and 1B (for example, it may be an SRF, or an L-SMF network element), Figure 1 the I-SMF network element in 1C and 1D, may manage the LUPF network element and the EAS.

[0096] It should be noted that Figure 1 1A, 1B, 1C, and 1D in Figure 1 only exemplarily show some examples of network elements or entities in the communication system. The communication system may also include some

[0097] network elements or entities not shown, and the embodiments of the present application do not make specific limitations on this. Figure 1 As shown in 1A, the terminal device accesses the network through the AN device. The terminal device communicates with the AMF network element through the N1 interface (abbreviated as N1); the AN device communicates with the AMF network element through the N2 interface (abbreviated as N2); the AN device communicates with the UPF network element through the N3 interface (abbreviated as N3); different UPF network elements communicate with each other through the N9 interface (abbreviated as N9); the entity providing the EAS may communicate with the UPF network element through the N6 interface (abbreviated as N6); the SMF network element may communicate with the first network element through the Nx interface; the first network element may communicate with the UPF network element through the Ny interface.

[0098] In one possible implementation, Figure 1 in 1A, the first network element may determine / select / reselect the EAS, and / or determine / select / reselect the UPF network element connected to the EAS.

[0099] AsFigure 1 As shown in Figure 1B, the terminal device accesses the network through the AN device. The terminal device communicates with the AMF network element through N1; the AN device communicates with the AMF network element through N2; the AN device communicates with the ULCL / branchpoint (BP) UPF network element through N3; the PDU session anchor (PSA) UPF network element communicates with the DN through N6; different UPF network elements communicate with each other through N9; the entity providing the EAS can communicate with the UPF network element through N6. The SMF network element can communicate with the first network element through the Nx interface; the first network element can communicate with the UPF network element through the Ny interface.

[0100] In a possible implementation, Figure 1 in Figure 1B, the first network element can determine / select / reselect the EAS, and / or determine / select / reselect the UPF network element connected to the EAS.

[0101] As Figure 1 shown in Figure 1C, the terminal device accesses the network through the AN device. The terminal device communicates with the AMF network element through N1; the AN device communicates with the AMF network element through N2; the AN device communicates with the UL CL UPF network element or the BP UPF network element through N3; the AMF network element communicates with the I-SMF network element through the N11 interface (abbreviated as N11); the SMF network element communicates with the PSA1 UPF network element through the N4 interface (abbreviated as N4); the PSA1 UPF network element communicates with the DN through N6; the I-SMF network element can communicate with the SMF network element through the N16a interface (abbreviated as N16a); the I-SMF network element can communicate with the UL CL UPF network element and the PAS2 UPF network element through N4; different UPF network elements communicate with each other through N9; the entity providing the EAS can communicate with the UPF network element through N6.

[0102] In a possible implementation, Figure 1 in Figure 1C, during the session establishment or modification process, the AMF network element can select the I-SMF network element (i.e., Figure 1 the I-SMF network element in Figure 1C). Then, the I-SMF network element can determine / select / reselect the EAS, and / or determine / select / reselect the UPF network element connected to the EAS.

[0103] As Figure 1As shown in 1D, the terminal device accesses the network through the AN device. The terminal device communicates with the AMF network element through N1; the AN device communicates with the AMF network element through N2; the AN device communicates with the ULCL UPF network element or the BP UPF network element through N3; the AMF network element communicates with the SMF network element through N11; the SMF network element communicates with the PAS1 UPF network element and the UL CL UPF network element through N4; the PSA1 UPF network element communicates with the DN through N6; different UPF network elements communicate with each other through the N9 interface (abbreviated as N9); the I-SMF network element can communicate with the SMF network element through N16a or Nx; the I-SMF network element can communicate with the PSA2 UPF network element through N4 or Ny; the entity providing the EAS can communicate with the UPF network element through N6.

[0104] In a possible implementation, Figure 1 in 1D, the AMF network element in 1D selects the SMF network element during the session establishment or modification process, and the SMF network element further selects the I-SMF network element (i.e., Figure 1 the I-SMF network element in 1D). Then the I-SMF network element can determine / select / reselect the EAS, and / or determine / select / reselect the UPF network element connected to the EAS.

[0105] In addition, Figure 1 the core network control plane network elements shown in the figure interact using service-based interfaces. For example, the service-based interface provided by the AMF network element externally is Namf; the service-based interface provided by the SMF network element externally is Nsmf; the service-based interface provided by the NEF network element externally is Nnef; the service-based interface provided by the NRF network element externally is Nnrf; the service-based interface provided by the PCF network element externally is Npcf; the service-based interface provided by the UDM network element externally is Nudm; the service-based interface provided by the AF network element externally is Naf; the service-based interface provided by the EASDF network element externally is Nasdf. The relevant function descriptions and interface descriptions can refer to existing standards and will not be elaborated here.

[0106] All or part of the functions of the network elements or devices in the embodiments of this application can also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform (such as a cloud platform). The network elements in the embodiments of this application can also be logical nodes, logical modules, or software that can implement all or part of the network element functions.

[0107] An access network device, which can also be referred to as an AN entity or an access node, etc., forms part of a communication system and is used to assist terminal devices in accessing the network. In one possible scenario, the access network device can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation nodeB (gNB), a next generation base station in a 6G mobile communication system, a base station in a future mobile communication system, or an access node in a wireless fidelity (WiFi) system, etc. The access network device can be a macro base station, a micro base station or an indoor station, a relay node or a donor node, or a radio controller in a cloud radio access network (C-RAN) scenario. Optionally, the access network device can also be a server, a wearable device, a vehicle or a vehicle-mounted device, etc. For example, the access network device in V2X technology can be a road side unit (RSU).

[0108] In another possible scenario, multiple access network devices cooperate to assist terminal devices in achieving access, and different access network devices respectively implement some functions of the base station. For example, the access network device can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. The CU and DU can be set separately, or can also be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio device or a radio unit, such as included in a remote radio unit (RRU), an active antenna unit (AAU) or a remote radio head (RRH).

[0109] In different systems, the CU (or CU-CP and CU-UP), DU, or RU may also have different names, but those skilled in the art can understand their meanings. For example, in an open radio access network (O-RAN), the CU may also be referred to as O-CU (Open CU), the DU may also be referred to as O-DU, the CU-CP may also be referred to as O-CU-CP, the CU-UP may also be referred to as O-CU-UP, and the RU may also be referred to as O-RU. For the convenience of description, in the embodiments of the present application, the CU, CU-CP, CU-UP, DU, and RU are used as examples for description. Any one of the CU (or CU-CP, CU-UP), DU, and RU in the embodiments of the present application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0110] The terminal device may also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. The terminal device can be widely applied to various scenarios. For example, in D2D, V2X communication, machine-type communication (MTC), Internet of Things, virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical, smart grid, smart furniture, smart office, smart wearables, smart transportation, or smart city, etc. The terminal device can be a mobile phone, tablet computer, computer with wireless transceiver function, wearable device, vehicle, drone, helicopter, airplane, ship, robot, robotic arm, smart home device, etc. The embodiments of the present application do not limit the form of the terminal device.

[0111] The following combines Figure 1 the architecture of the communication system shown to describe the communication method provided by the embodiments of the present application.

[0112] It can be understood that in the following embodiments of the present application, the names of each network element, the names of the messages exchanged between each network element, the names of each parameter, or the names of each piece of information, etc. are only examples, and in other embodiments, they may also be other names. The method provided by the present application does not make specific limitations on this.

[0113] It can be understood that in the following embodiments of the present application, each parameter may include one or more specific values. Taking DNAI as an example, DNAI(s) may represent one or more DNAIs.

[0114] It can be understood that in the embodiments of the present application, each network element or entity may execute some or all of the steps in the embodiments of the present application. These steps or operations are only examples, and the embodiments of the present application may also execute other operations or variations of various operations. In addition, each step may be executed in a different order presented in the embodiments of the present application, and it is possible that not all of the operations in the embodiments of the present application need to be executed.

[0115] As Figure 2 shown, a communication method provided by an embodiment of the present application is presented. Figure 2 Taking the session management network element as an example of the execution subject of this process schematic to illustrate the method, but the present application does not limit the execution subject of this process schematic. For example, Figure 2 the session management function network element in it may also be a module applied to the session management function network element, such as a chip, a chip system, or a processor, and may also be a logical node, a logical module, or software that can implement all or part of the functions of the first network element.

[0116] Referring to Figure 2 , this communication method includes steps S201 - S202:

[0117] S201. The session management function network element obtains the application information subscribed by the terminal device, and the application information includes at least one of the following: fully qualified domain name (FQDN), application identifier (App ID), or data network access identifier (DNAI).

[0118] S202. The session management function network element determines a target first network element according to the application information; wherein, the first network element is used to determine the local user plane function network element or the edge application service.

[0119] In the embodiments of the present application, "target... (taking the target first network element as an example)" can be understood as the first network element actually applied determined from at least one first network element. Correspondingly, these at least one first network elements can be understood as candidates (or alternatives) for the target first network element. Similar expressions in the following embodiments, such as "target edge application service" or "target user plane function network element", etc., can also be understood in this way.

[0120] In the embodiments of the present application, in some scenarios, the first network element is used to determine the local user plane function network element or the edge application service, which can also be understood as selecting the local user plane function network element or the edge application service. For example, during the session establishment process, there are multiple candidate local user plane function network elements or edge application services, and the first network element needs to select one of them. In some scenarios, the first network element is used to determine the local user plane function network element or the edge application service, which can also be understood as reselecting the local user plane function network element or the edge application service. For example, after the session establishment is completed, the first network element triggers the reselection of the local user plane function network element or the edge application service to replace the original local user plane function network element or edge application service.

[0121] Similarly, in some scenarios, for example, during the session establishment process, the session management network element determines the target first network element, which can also be understood as selecting the target first network element. In some scenarios, for example, after the session establishment is completed, the session management network element determines the target first network element, which can also be understood as reselecting the target first network element. The following takes the session management function network element selecting the target first network element according to the application information as an example to introduce the following embodiments.

[0122] Based on the communication method provided by the embodiments of the present application, the session management function network element can select the first network element according to the application information subscribed by the terminal device, which not only provides a more fine-grained network element selection method, but also the determined first network element can be responsible for determining the local user plane function network element or the edge application service, effectively alleviating the pressure on the session management function network element to centrally process the requests of the terminal device for the edge application service. In scenarios where there are more edge application services and / or local user plane function network elements, it can also reduce resource overhead.

[0123] The following expands and introduces S201 and S202.

[0124] In S201, the embodiments of the present application do not limit the manner in which the session management function obtains the application information subscribed by the terminal device. In one possible implementation, the session management function network element can obtain the application information from the unified data management network element. For example, the session management function network element can request the subscription information of the terminal device from the unified data management network element. The unified data management network element sends the subscription information of the terminal device to the session management function network element according to the request of the session management function network element. The session management function network element receives the subscription information of the terminal device from the unified data management network element, where the subscription information includes the application information.

[0125] Optionally, the subscription information of the terminal device may further include at least one of the following: information such as data network name (DNN), single network slice selection assistance information (S-NSSAI), etc.

[0126] In S202, the embodiments of the present application do not limit the specific implementation of the session management function to determine the target first network element according to the application information. The following introduces several possible implementations provided by the embodiments of the present application.

[0127] In a possible implementation manner, the session management function network element sends a first request message to the network storage function network element. The first request message includes application information and is used to request the network storage function network element to select a target first network element. After receiving the first request message, the network storage function network element selects a target first network element according to the application information therein, and carries the information of the target first network element in the first response message for the first request message and sends it to the session management function network element. The session management function network element receives the first response message and selects the target first network element according to the information of the target first network element therein.

[0128] Among them, exemplarily, the information of the target first network element may include at least one of the following: address information of the target first network element, port number of the target first network element, or identifier of the target first network element, etc.

[0129] Optionally, in this implementation, the first request message may further include information about a first area. The network storage function network element may select the target first network element according to the information of the first area and the application information. Among them, the first area is related to the location of the terminal device. For example, the information of the first area may include at least one of the following: tracking area (TA) where the terminal device is currently located, TA list (TA list) to which the TA where the terminal device is currently located belongs, adjacent TA of the TA where the terminal device is currently located, TA list to which the adjacent TA of the TA where the terminal device is currently located belongs, etc. Another example is that the information of the first area may include information indicating the longitude and latitude of the terminal device, etc., information characterizing the geographical range.

[0130] For how the network storage function network element selects the target first network element according to the information of the first area and the application information in this implementation, optionally, if the information of the first area has a priority, for example, the information of the first area includes the TA list to which the TA where the terminal device is currently located belongs, and each TA in the TA list has a corresponding priority, the network storage function network element may match the first network element in order from high to low according to the application information and the priority of the information of the first area.

[0131] Optionally, in this implementation, the first request message may further include first indication information for indicating that the network element to be selected upon request is the first network element. It can also be understood that the first indication information is used to indicate the type of the network element to be selected upon request. Exemplarily, if the first network element is an SRF network element, the first indication information may indicate that the type of the destination NF is SRF.

[0132] Optionally, in this implementation, the first request message may further include second indication information for indicating that the requested network service is for selecting a user plane function service or for establishing a session service. The network storage function network element may determine the target first network element to be selected based on the second indication information. Exemplarily, the second indication information may be represented in the form of a string. For example, the second indication information may be represented as: the destination NFS name is Nsrf_lupfselect / Nsmf_pdusession, etc.

[0133] Optionally, in this implementation, the first request message may further include at least one of the following: DNN or S-NSSAI. The network storage function network element may select the target first network element based on the application information and DNN or SNSSAI.

[0134] In another possible implementation, the session management function network element may determine the first network element corresponding to the application information obtained in S201 as the target first network element according to the mapping relationship between the application information and the first network element. Optionally, the mapping relationship between the application information and the first network element may include the correspondence between the identifiers, names, or specific values of the various parameters included in the application information and the information of the first network element, such as the identifier, name, or address information of the first network element. Similar expressions in the following text can also be understood in this way.

[0135] Optionally, the mapping relationship between the application information and the first network element may be locally configured by the session management network element, or may also be obtained by the session management network element from other network elements.

[0136] It should be noted that the embodiment of the present application does not limit the representation form of the mapping relationship between the application information and the first network element. For example, the mapping relationship between the application information and the first network element may be represented in the form of a list.

[0137] Exemplarily, assume that the first network element is an SRF network element. The SMF network element can locally configure the following mapping relationships: SRF1: DNAI01, DNAI02 (i.e., SRF1 corresponds to DNAI01 and DNAI02), SRF2: DNAI11, DNAI12 (i.e., SRF2 corresponds to DNAI11 and DNAI12). If the application information obtained by the SMF network element includes DNAI01, the SMF network element can determine that SRF1 corresponding to DNAI01 is the target first network element according to the above mapping relationship. It should be understood that when the first network element is other network elements, such as L-SMF or I-SMF network elements, or the application information includes other parameters, such as FQDN or App ID, the mapping relationship in the above example is also applicable.

[0138] In another possible implementation, the session management function network element can determine the information of the first area corresponding to the application information obtained in S201 according to the mapping relationship between the application information (such as the identification, name, or specific value of each parameter included in the application information, etc.), the information of the first area (such as the identification of the first area, the longitude and latitude of the first area, etc.) and the first network element (such as the identification, name, or address information of the first network element, etc.), and then further determine the target first network element according to the corresponding information of the first area.

[0139] Optionally, the mapping relationship between the application information, the information of the first area, and the first network element can be locally configured by the session management network element, or can also be obtained by the session management network element from other network elements.

[0140] In this application embodiment, the representation form of the mapping relationship between the application information and the first network element is not limited. For example, the mapping relationship between the application information and the first network element can be represented in the form of a list.

[0141] Exemplarily, assume that the first network element is an SRF network element. The SMF network element can configure the following corresponding relationships: SRF1: TA01, TA02 (DNAI1) (i.e., SRF1 corresponds to TA01 and TA02, and TA01 and TA02 correspond to DNAI1), SRF2: TA11, TA12 (DNAI2) (i.e., SRF2 corresponds to TA11 and TA12, and TA11 and TA12 correspond to DNAI2). If the application information obtained by the SMF network element is DNAI2, the SMF network element can determine that DNAI2 corresponds to TA11 and TA12 according to the above mapping relationship, and further determine that SRF2 corresponding to TA11 and TA12 is the target first network element. It should be understood that when the first network element is other network elements, such as L-SMF or I-SMF network elements, or the application information includes other parameters, such as FQDN or App ID, the mapping relationship in the above example is also applicable.

[0142] In another possible implementation, the session management function network element may obtain the deployment information of the edge application service (hereinafter referred to as EAS deployment information). The EAS deployment information may include at least one of FQDN or APP ID, and at least one of information such as DNAI, EAS IP (optionally, the EAS IP may correspond to the DNAI), or domain name server (DNS) (optionally, the DNS may correspond to the DNAI). Among them, there may be a corresponding relationship between the information included in the EAS deployment information. For example, FQDN / APP ID may correspond to the DNAI. After the session management network element obtains the application information in S201, it may search for the information corresponding to the obtained application information in the EAS deployment information, and determine the target first network element according to the found information (or rather, match the application information with the EAS deployment information and determine the target first network element according to the matched information). In this implementation, the information found by the session management function network element in the EAS deployment information may also be referred to as target information. For example, if the EAS deployment information includes DNAI or EAS IP, the DNAI found by the session management function network element in the EAS deployment information may be referred to as the target DNAI, and the found EAS IP may be referred to as the target EAS IP.

[0143] Among them, the EAS deployment information may be obtained by the session management function network element from other network elements. For example, it may be obtained from the application function network element, or it may be locally configured by the session management network element. The embodiments of the present application do not limit the specific implementation of the session management function for obtaining the EAS deployment information.

[0144] Exemplarily, if the application information obtained by the SMF network element includes FQDN / APP ID, the SMF network element may search for the information corresponding to the FQDN / APP ID in the EAS deployment information. If the EAS deployment information includes DNAI, the SMF network element may determine the target first network element according to the obtained target DNAI (for example, the target first network element may be determined according to the mapping relationship between the DNAI configured locally and the first network element, etc., and the embodiments of the present application do not make specific limitations on this). If the EAS deployment information includes EAS IP, the SMF network element may determine the target first network element according to the obtained target EAS IP (for example, the target first network element may be determined according to the mapping relationship between the EAS IP configured locally and the first network element, or for another example, the first network element that manages the EAS corresponding to the EAS IP may be determined as the target first network element, or for another example, the first network element closest to the EAS corresponding to the EAS IP may be determined as the target first network element, etc., and the embodiments of the present application do not make specific limitations on this). If the EAS deployment information includes DNS, the SMF network element may determine the target first network element according to the obtained target DNS (for example, the target first network element may be determined according to the mapping relationship between the DNS configured locally and the first network element, or for another example, the first network element that manages the EAS corresponding to the EAS IP may be determined as the target first network element, or for another example, the first network element closest to the EAS corresponding to the EAS IP may be determined as the target first network element, etc., and the embodiments of the present application do not make specific limitations on this).

[0145] Optionally, the EAS deployment information may further include other information, such as data network name (DNN), information of the slice associated with the application, and other information.

[0146] Optionally, after the session management network element selects the target first network element, the target first network element may select the target edge application service and / or the target user plane function network element (the target user plane function network element may be a local user plane function network element).

[0147] In a possible implementation, the session management function network element sends a second request message to the target first network element, and the second request message is used to request the target first network element to select the target edge application service and / or the target user plane function network element. After receiving the second request message, the target first network element selects the target edge application service and / or the target user plane function network element.

[0148] Optionally, the second request message may include application information, and the target first network element may determine (or select or reselect, hereinafter introduced by taking selection as an example) the target edge application service and / or the target user plane function network element according to the application information.

[0149] The embodiments of the present application do not limit the specific implementation of the target first network element to select the target edge application service and / or the target user plane function network element according to the application information. Exemplarily, the first network element may match the FQDN(s), App ID with the EAS deployment information to determine the IP address of the target EAS or the DNAI corresponding to the target EAS. Also for example, the first network element may, according to the information of the determined target EAS, select the user plane function network element connected to the target EAS as the target user plane function network element.

[0150] Optionally, the first network element may obtain the EAS deployment information from other network elements. For example, it may obtain the information from the application function network element, or the first network element may locally configure the EAS deployment information. The embodiments of the present application do not limit the specific implementation of the first network element to obtain the EAS deployment information.

[0151] Optionally, the application information may further include one or more of the following information: the latency requirement for the transmission between the user plane function network element and the edge application service, or the load requirement for the user plane function network element. Among them, the latency requirement for the transmission between the user plane function network element and the edge application service may include a threshold value. In this case, the latency for the transmission between the selected target user plane function network element and the target edge application service shall not exceed the threshold value. Or, the latency requirement for the transmission between the user plane function network element and the edge application service may indicate to select the one with the minimum latency for the transmission between the user plane function network element and the edge application service as the target user plane function network element and the target edge application service. Similarly, the load requirement for the user plane function network element may include a threshold value, and the load of the selected target user plane function network element shall not exceed the threshold value, or it may indicate to select the user plane function network element with the minimum load.

[0152] The above one or more pieces of information may also be referred to as preferred parameters. The target first network element may, according to the preferred parameters, select the target edge application service and / or the target user plane function network element that meet the preferred parameters.

[0153] Exemplarily, assuming that the application information includes the latency requirement for the transmission between the user plane function network element and the edge application service, the target first network element may select the user plane function network element and the edge application service that meet the latency requirement as the target edge application service and the target user plane function network element. If the application information includes the load requirement for the user plane function network element, the target first network element may select the user plane function network element that meets the load requirement as the target user plane function network element. Further, the target first network element may also select the edge application service with the shortest distance or the minimum transmission latency between the target user plane function network element as the target edge application service.

[0154] Optionally, after the target first network element selects the target edge application service and / or the target user plane function network element, it may send a second response message for the second request message to the session management function network element. Correspondingly, the session management function network element receives the second response message, where the second response message includes information about the target edge application service and / or the target user plane function network element, such as the IP address of the target edge application service, the core network tunnel information (CNtunnel info) of the target user plane function network element, the UE IP assigned by the intermediate user plane function network element (local UPF, I-UPF), etc.

[0155] Optionally, S201-S202 can be applied to a session establishment scenario, such as in a PDU session establishment scenario. In this scenario, the session management function network element selects the target first network element, which may be triggered by the access mobility management function network element. For example, before S201, the following steps may be included:

[0156] The access mobility management function network element sends a third request message to the session management function network element, and the session management function network element receives the third request message from the access mobility management function network element. The third request message is used to request the establishment of a session context (such as a PDU session context). The third request message triggers the session management network element to select the target first network element, or rather, the session management function network element determines to select the target first network element according to the third request message.

[0157] Optionally, if S201-S202 is applied to a session establishment scenario, in S202, the second request message sent by the session management network element to the target first network element may be a session establishment request message (such as a PDU session establishment request message), or it may be a local user plane function network element selection request message for requesting the selection of a local user plane function network element.

[0158] In addition, an embodiment of the present application also provides another method for the access mobility management network element to select the target first network element. Figure 3 Taking the terminal device and the access mobility management function network element as the execution entities of this interaction schematic as an example to illustrate this method, but the present application does not limit the execution entities of this interaction schematic. For example, Figure 3 the access mobility management function network element in Figure 3 may also be a module applied to the access mobility management function network element, such as a chip, a chip system, or a processor, and may also be a logical node, a logical module, or software that can implement all or part of the functions of the access mobility management function network element;

[0159] such as Figure 3As shown in the figure, the communication method includes the following steps:

[0160] S301. The terminal device sends a session establishment request message to the access mobility management function network element. Correspondingly, the access mobility management function network element receives the session establishment request message from the terminal device.

[0161] S302. The access mobility management function network element determines (or selects or reselects, hereinafter introduced by taking selection as an example) a target first network element according to a first parameter. Wherein, the first network element is used to determine (or select or reselect, hereinafter introduced by taking selection as an example) an edge application service or a local user plane function network element, and the first parameter includes one or more of the following information: information of a first area, a data network name, or information of a slice associated with an application. Wherein, the first area is related to the location of the terminal device.

[0162] The following further introduces S301 and S302.

[0163] S301 and S302 can be applied to a session establishment scenario, such as a PDU session establishment scenario.

[0164] In S301, the information of the first area can specifically refer to the above introduction and will not be elaborated here.

[0165] In S301, the session establishment request message of the terminal device can trigger the access mobility management function network element to select a first network element.

[0166] In a possible scenario, when determining a session management network element according to the session establishment request message, the access mobility management function network element can select an intermediate session management network element, that is, the target first network element.

[0167] In S302, the access mobility management network element can locally configure the first parameter, or the access mobility management network element can obtain the first parameter from other network elements. The embodiments of the present application do not limit the specific implementation of the access mobility management network element obtaining the first parameter.

[0168] The embodiments of the present application do not limit the manner in which the access mobility management function network element selects a target first network element according to the first parameter. For example, the access mobility management function network element can determine the target first network element according to the mapping relationship between the first parameter and the first network element, and this manner can refer to the above introduction of how the session management network element determines the target first network element. Another example is that the access mobility management function network element can query the target first network element corresponding to the first parameter from the unified data management network element.

[0169] Optionally, the target first network element may obtain the application information subscribed by the terminal device. The application information includes at least one of the following: FQDN, or App ID, or DNAI. Specifically, reference may be made to the above introduction. The embodiments of the present application do not limit the specific implementation of the target first network element for obtaining the subscribed information. For example, the target first network element may obtain the application information from the unified data management network element. Alternatively, the target first network element may obtain the application information from the session management function network element. For example, the session management function network element first obtains the application information, and then in response to the PDU session procedure, sends the application information to the target first network element. Among them, the response PDU session procedure includes: the target first network element sends a PDU session establishment request message to the session management function network element. After receiving the PDU session establishment request message, the session management function network element sends a response message to the target first network element for the PDU session establishment request message, and the response message includes the application information.

[0170] Further, the target first network element may select (or select or reselect) the target edge application service and / or the target user plane function network element according to the application information. Optionally, the target first network element may also send the target edge application service and / or the target user plane function network element to the session management function network element. Specifically, reference may be made to the above introduction and will not be elaborated here.

[0171] In addition, the embodiments of the present application also provide a method for providing deployment information of edge application services (hereinafter referred to as EAS deployment information) to the first network element serving a specific area. Figure 4 Taking the second network element and the first network element (optionally, the network storage function network element) as the execution subjects of this interaction schematic as an example to illustrate this method, but the present application does not limit the execution subjects of this interaction schematic. For example, Figure 4 the first network element in may also be a module applied to the first network element, such as a chip, a chip system, or a processor, and may also be a logical node, a logical module, or software that can implement all or part of the functions of the first network element; Figure 4 the second network element in may also be a module applied to the second network element, such as a chip, a chip system, or a processor, and may also be a logical node, a logical module, or software that can implement all or part of the functions of the second network element; Figure 4 the network storage function network element in may also be a module applied to the network storage function network element, such as a chip, a chip system, or a processor, and may also be a logical node, a logical module, or software that can implement all or part of the functions of the network storage function network element.

[0172] Optionally, as Figure 4 shown, the method may be applied when the application is launched. In this scenario, the second network element may provide the EAS deployment information to the first network element through the service interface for creating / updating / deleting the EAS deployment information. As Figure 4As shown, the method includes the following steps:

[0173] S401. The second network element sends EAS deployment information to the first network element serving the second area; wherein, the EAS deployment information includes at least one of the following: fully qualified domain name (FQDN), application identifier (APP ID), IP address of the edge application service (EAS IP), or data network access identifier (DNAI).

[0174] Wherein, the second network element is another network element different from the first network element. Exemplarily, the second network element may be an application function network element, a network open function network element, or a local network open function (localNEF, L-NEF) network element.

[0175] Wherein, the first network element is used to select an edge application service and / or a local user plane function network element, which can be specifically referred to the above introduction and will not be elaborated here.

[0176] Wherein, the number of the first network elements serving the first area may be one or more.

[0177] Optionally, the EAS deployment information may further include other information, such as data network name (DNN), information of the slice associated with the application, DNS server and other information.

[0178] In the embodiments of the present application, there are various implementation manners for the second network element to send the deployment information of the edge application service to the first network element serving the second area. The following is an expanded introduction.

[0179] In a possible implementation, as Figure 4 shown in 4a, before S401, the following steps may be included:

[0180] S400. The first network element serving the second area sends a fifth request message to the second network element, and the fifth request message requests to subscribe to the deployment information of the edge application service.

[0181] Correspondingly, after receiving the fifth request message, the second network element may, in response to the fifth request message, send the deployment information of the edge application service to the first network element.

[0182] Wherein, if the second network element is a network open function network element or a local network open function network element, the second network element may obtain the EAS deployment information from the application function network element. If the second network element is an application function network element, the second network element may obtain the EAS deployment information from a third party or an operator.

[0183] Optionally, in addition to the network exposure function network element or the local network exposure function network element, the application function network element may also save the EAS deployment information in the unified data repository (UDR) network element.

[0184] Optionally, the fifth request message may include a specific second parameter (for example, it may be a second parameter supported by the first network element serving the second area), and the second parameter includes at least one of the following: FQDN, APP ID, or EAS IP. In this case, after receiving the fifth request message, the second network element may determine the EAS deployment information corresponding to the specific second parameter according to the specific second parameter carried therein, and send it to the first network element.

[0185] Exemplarily, assuming that in the fifth request message, the second parameter includes FQDN1, the EAS deployment information corresponding to FQDN1 sent by the second network element to the first network element may include one or more of the following: FQDN1, the APP ID corresponding to FQDN1, EAS IP, DNAI, DNN, or slice, etc. information.

[0186] In another possible implementation, as shown in Figure 4 4b, before S401, the following steps may be included:

[0187] S402. After obtaining the EAS deployment information, the second network element may send a fourth request message to the network storage function network element, where the fourth request message is used to request to discover the first network element serving the second area, and the fourth request message includes information indicating the second area.

[0188] Wherein, if the second network element is a network exposure function network element or a local network exposure function network element, the second network element may obtain the EAS deployment information from the application function network element. If the second network element is an application function network element, the second network element may obtain the EAS deployment information from a third party or an operator.

[0189] The embodiments of the present application do not limit how the second network element determines the second area. For example, the area where the second network element expects to send the EAS deployment information may be the second area.

[0190] The embodiments of the present application do not specifically limit the second area. Exemplarily, the information indicating the second area may indicate TA, TAlist, longitude and latitude, etc.

[0191] Exemplarily, the information indicating the second area may be represented in the form of a string. For example, the information indicating the second area may be a service area identifier (ServiceArea ID), where the second area is ServiceArea.

[0192] Correspondingly, after receiving the fourth request message, the network storage function network element can discover the first network element serving the second area according to the fourth request message. Further, the network storage function network element sends the information of the first network element serving the second area, such as IP address or port number, to the second network element. Thus, the second network element can send the deployment information of the edge application service to the first network element serving the second area according to the information of the first network element serving the second area.

[0193] Optionally, in this implementation, the fourth request message may further include at least one of the following pieces of information: the third indication information or the fourth indication information. The third indication information is used to indicate that the network element to be discovered by the request is the first network element, or in other words, to indicate the type of the network element to be discovered by the request. Exemplarily, if the first network element is an SRF, the third indication information may indicate that the target NF is an SRF. The fourth indication information is used to indicate that the requested service is to provide EAS deployment information. Exemplarily, the fourth indication information may be represented in the form of a string. For example, the fourth indication information may be represented as: the destination NFS name is Nnef_easdeployment.

[0194] Optionally, the above embodiments as Figure 2 shown or the embodiments as Figure 3 shown can be applied independently, or can also be combined. In the scenario where the embodiments as Figure 4 shown or the embodiments as Figure 2 shown are combined with the embodiments as Figure 3 shown, the target first network element determined by the session management function network element or the access and mobility management function network element can obtain the EAS deployment information through the method provided by the embodiments as Figure 4 shown. Further, the target first network element can determine the target edge application service and / or the target user plane function network element according to the obtained EAS deployment information and the application information. Figure 4

[0195] The following assumes that the terminal device is a UE, the first network element is an SRF network element (it should be understood that when the first network element is other network elements, such as an L-SMF or an I-SMF, the following process is also applicable), the session management function network element is an SMF network element, the access and mobility management function network element is an AMF network element, the network exposure function network element is a NEF network element, the application function network element is an AF network element, the unified data management network element is a UDM network element, the network storage function network element is an NRF network element, the target user plane function network element is a target L-UPF, and the target edge application service is a target EAS. The possible process of the session management function network element determining the target first network element in the above embodiments will be introduced.

[0196] Assume that the target first network element is determined in a session establishment scenario, such as​Figure 5 As shown, a possible process may include the following steps:

[0197] S501. The UE sends a session establishment request message to the AMF network element to initiate session establishment, for example, initiate the establishment of a PDU session.

[0198] S502. The AMF network element selects an SMF network element based on at least one of the following information: DNN / slice, public land mobile network (PLMN), TA list information, etc.

[0199] S503. The AMF network element requests the selected SMF network element to create a session management (SM) context.

[0200] S504. The SMF network element requests the subscription information of the UE from the UDM network element, and the UDM network element feeds back the subscription information of the UE. Among them, the subscription information includes information such as DNN, SNSSAI, etc. and the application information subscribed by the UE. The application information includes at least one of the following: FQDN(s), or APP ID, etc.

[0201] Optionally, the application information may further include preference parameters, and the preference parameters include at least one of the following: the latency requirement for the transmission between the LUPF and the EAS, or the load requirement for the LUPF.

[0202] S505. The SMF network element sends a response message to the AMF network element for the request to create an SM context.

[0203] S506. The SMF network element selects an SRF network element according to the application information.

[0204] Among them, the SMF network element may select the SRF network element in the way of S506a:

[0205] S506a. The SMF network element selects the SRF network element corresponding to the application information obtained in S504 in the mapping relationship based on the locally configured mapping relationship between the SRF network element and the application information.

[0206] S506a may specifically refer to the introduction in the above text about S202, where the session management function network element determines the target first network element as the first network element corresponding to the obtained application information according to the mapping relationship between the application information and the first network element, and will not be elaborated here.

[0207] Alternatively, the SMF network element may select the SRF network element in the way of S506b, where the S506b method includes the following steps:

[0208] The SMF network element requests the NRF network element to discover the SRF network element. Among them, the request message includes that the destination NF type is SRF, and the destination NFS name is Nsrf_lupfselect / Nsmf_pdusession. The request message also includes application information, that is, at least one of information such as FQDN(s), Appid, or preferred parameters. Optionally, the request message may further include at least one of the following: DNN, SNSSAI, or information about the first area.

[0209] After receiving the request message, the NRF network element selects the SRF network element according to the request message and feeds back the information of the selected SRF network element to the SMF network element. After receiving the information fed back by the NRF network element, the SMF network element selects the SRF network element fed back by the NRF network element.

[0210] S506b can specifically refer to the introduction of the following solution in S202 above: The session management function network element sends a first request message to the network storage function network element. After receiving the first request message, the network storage function network element selects the target first network element according to the application information therein, and carries the information of the target first network element in the first response message for the first request message and sends it to the session management function network element. The session management function network element selects the target first network element according to the first response message.

[0211] S507. The SMF network element sends a session establishment request or a LUPF selection request to the selected SRF network element, which carries application information as a reference for the SRF network element to select the target LUPF and / or target EAS. The following takes the case where the SRF network element selects the target LUPF and target EAS as an example for introduction.

[0212] S508. The SRF network element determines the target EAS and the target LUPF network element according to the application information.

[0213] Exemplarily, the SRF network element may match the FQDN and App ID in the application information with the obtained EAS deployment information to determine the IP address of the target EAS. Or, the SRF network element may determine the IP address of the target EAS according to the correspondence between the FQDN(s) and AppID configured locally and the EAS IP, and the FQDN and App ID in the application information.

[0214] Exemplarily, the SRF network element may determine, according to the FQDN(s) / App ID in the application information and the obtained EAS deployment information, the DNAI corresponding to the FQDN(s) / App ID in the EAS deployment information, and further determine the LUPF network element corresponding to the DNAI as the target LUPF network element. Optionally, if the DNAI corresponds to multiple LUPF network elements, the SRF network element may select the target LUPF network element according to the load requirement for the LUPF or the latency requirement between the LUPF and the EAS in the preference parameters, etc.

[0215] For S508, reference may be specifically made to the above introduction of how the target first network element selects the target edge application service and / or the target user plane function network element in S202.

[0216] S509. The SRF network element sends a response message to the SMF network element for the PDU session establishment request or the LUPF selection request, carrying the selected target LUPF information, such as CN tunnel info and the UE IP assigned by the iupf.

[0217] S510. The SMF network element establishes a user plane channel between the target LUPF network element and the UE.

[0218] S511. A channel is established between the target EAS and the target LUPF network element.

[0219] The following assumes that the terminal device is a UE, the first network element is an I-SMF network element (it should be understood that when the first network element is other network elements, such as an L-SMF or an SRF, the following process is also applicable), the session management function network element is an SMF network element, the access and mobility management function network element is an AMF network element, the network exposure function network element is an NEF network element, the application function network element is an AF network element, the unified data management network element is a UDM network element, the network repository function network element is an NRF network element, the target user plane function network element is a target L-UPF, and the target edge application service is a target EAS. A possible process for the access and mobility management function network element to determine the target first network element according to the first parameter in the above embodiments is introduced.

[0220] Assume that the target first network element is determined in a session establishment scenario, such as Figure 6 As shown, a possible process may include the following steps:

[0221] S601. The UE sends a session establishment request message to the AMF network element to initiate session establishment, such as initiating the establishment of a PDU session.

[0222] When the AMF network element selects an SMF network element based on the first parameter, it selects an I-SMF network element. The first parameter includes at least one of the following information: DNN, slice, or information of the second area, etc., and then selects the SMF network element.

[0223] For the specific operation of S602, reference can be made to the description in the above S302 about the access and mobility management function network element selecting the target first network element according to the first parameter.

[0224] S603. The AMF network element requests the selected I-SMF network element to create an SM context. The I-SMF network element sends a response message for the create SM context request to the ALF network element.

[0225] S604. The I-SMF network element obtains the subscription information of the UE.

[0226] The subscription information includes information such as DNN, SNSSAI, etc., and the application information subscribed by the UE. The application information includes at least one of the following: FQDN(s), or APP ID, etc. Optionally, the application information may further include preferred parameters, and the preferred parameters include at least one of the following: the latency requirement for the transmission between the LUPF and the EAS, or the load requirement for the LUPF.

[0227] Optionally, the I-SMF network element may obtain the subscription information of the UE in the manner shown in S604a. S604a includes the following steps:

[0228] The I-SMF network element requests the UDM network element for the subscription information of the UE, and the UDM feeds back the subscription information of the UE.

[0229] Alternatively, the I-SMF network element may also obtain the subscription information of the UE in the manner shown in S604b. S604b includes the following steps:

[0230] The I-SMF network element requests the SMF network element to establish a PDU session. After receiving the request, the SMF network element obtains the subscription information of the UE (for example, obtains it from the UDM network element), and then sends the subscription information to the I-SMF network element in the response PDU session process.

[0231] S605. The I-SMF network element determines the target EAS and the target LUPF network element according to the application information.

[0232] For the specific operation of S605, reference can be made to the description in the above S202 about the target first network element selecting the target edge application service and / or the target user plane function network element according to the application information.

[0233] S606. The I-SMF network element sends the information of the selected target L-UPF network element to the SMF network element, such as the CN tunnel info and the UE IP allocated by the I-UPF.

[0234] S607. The SMF network element establishes a user plane channel between the target L-UPF network element and the UE.

[0235] S608. A channel is established between the target EAS and the target L-UPF network element.

[0236] The following assumes that the terminal device is the UE, the first network element is the I-SMF network element (it should be understood that when the first network element is other network elements, such as the L-SMF or SRF, the following process is also applicable), the session management function network element is the SMF network element, the access and mobility management function network element is the AMF network element, the network exposure function network element is the NEF network element, the application function network element is the AF network element, the unified data management network element is the UDM network element, the network repository function network element is the NRF network element, the target user plane function network element is the target L-UPF, and the target edge application service is the target EAS. Another possible process for the session management function network element to determine the target first network element according to the application information in the above embodiments is introduced.

[0237] Assume that the target first network element is determined in the session establishment scenario, such as Figure 7 As shown, another possible process may include the following steps:

[0238] S701. The UE sends a session establishment request message to the AMF network element to initiate session establishment, such as initiating the establishment of a PDU session.

[0239] S702. The AMF network element selects the SMF network element according to at least one of the following information: DNN, slice, PLMN, TA list information, etc.

[0240] S703. The AMF network element requests the selected SMF network element to create an SM context.

[0241] S704. The SMF network element requests the UE's subscription information from the UDM network element, and the UDM feeds back the UE's subscription information. The subscription information includes information such as DNN, SNSSAI, etc. and the application information subscribed by the UE. For details, reference can be made to the introduction of S504 above.

[0242] S705. The SMF network element sends a response message to the AMF for the request to create an SM context.

[0243] S706. The SMF network element determines the I-SMF network element according to the application information.

[0244] Among them, the SMF network element can determine the I-SMF network element in the manner of S506a or S506b as described above (just replace the SRF network element with the I-SMF network element, Figure 7 which is not shown in the figure). Or, as Figure 7 shown, the SMF network element can match the application information with the obtained EAS deployment information to determine the IP address or DNAI of the corresponding target EAS.

[0245] S707. The SMF network element sends a session establishment request or a LUPF selection request to the selected I-SMF network element, carrying the application information, as a reference for the I-SMF network element to select the target LUPF and / or the target EAS. The following takes the case where the I-SMF network element selects the target LUPF and the target EAS as an example for introduction.

[0246] S708. The I-SMF network element determines the target EAS and the target LUPF network element according to the application information.

[0247] Specifically, S708 can refer to the introduction above for S202, where the target first network element selects the target edge application service and / or the target user plane function network element according to the application information.

[0248] S709. The I-SMF network element sends a response message to the SMF network element for the PDU session establishment request or the LUPF selection request, carrying the information of the selected target LUPF network element, such as CN tunnel info, UEIP assigned by iupf.

[0249] S710. The SMF network element establishes a user plane channel between the target LUPF network element and the UE.

[0250] S711. A channel is established between the target EAS and the target LUPF network element.

[0251] In some possible scenarios, before the processes as Figure 5 shown, the processes as Figure 6 shown, or the processes as Figure 7 shown, it may include the process in which the first network element (SRF network element, L-SMF network element or I-SMF network element) obtains the EAS deployment information as Figure 8 shown.

[0252] As Figure 8 shown in 8a, a possible process for the first network element to obtain the EAS deployment information includes the following steps S801a - S803a:

[0253] S801a. The AF network element sends the EAS deployment information to the NEF network element. Among them, the EAS deployment information includes at least one of the following: FQDN(s), Appid, EAS IP, DNAI, or slice information, etc.

[0254] Optionally, the AF can also save the EAS deployment information in the UDR network element.

[0255] S802a. The first network element subscribes to the EAS deployment information corresponding to a specific second parameter from the NEF network element. The second parameter includes at least one of the following: FQDN(s), Appid, or EAS IP.

[0256] S803a. The NEF network element sends the EAS deployment information corresponding to the specific second parameter to the SRF network element.

[0257] For the specific details of S801a - S803a, reference can be made to the introduction of S400 - S401 above.

[0258] As Figure 8 shown in 8b, another possible process for the first network element to obtain the EAS deployment information includes the following steps S801b - S804b:

[0259] S801b. The AF network element provides the EAS deployment information to the NEF / L - NEF network element.

[0260] S802b. The NEF / L - NEF network element requests the NRF to discover the first network element. Among them, the request message (for example, it can be the Nnrf_Nfdicovery_req string) includes: the target NF is SRF, the target NFS is Nnef_easdeployment, and the ServiceAreaID. Among them, the ServiceAreaID indicates the service area of the first network element for which discovery is requested.

[0261] S803b. The NRF network element sends the information of the discovered first network element to the NEF / L - NEF network element.

[0262] S804b. The NEF / L - NEF network element provides the EAS deployment information to the discovered first network element.

[0263] As Figure 8 shown in 8c, another possible process for the first network element to obtain the EAS deployment information includes the following steps S801c - S803c:

[0264] S801c. The AF network element requests the NRF to discover the first network element. The request message (e.g., it can be the Nnrf_Nfdicovery_req string) includes: the target NF is the SRF, the target NFS is the Nnef_easdeployment, and the ServiceAreaID. The ServiceAreaID indicates the service area of the first network element for which discovery is requested.

[0265] S802c. The NRF network element sends the information of the discovered first network element to the AF network element.

[0266] S803c. The AF network element provides the EAS deployment information to the discovered first network element.

[0267] S801b - S804b, or S801c - S803c can specifically refer to the introduction of S402 - S401 above.

[0268] It can be understood that the above Figures 2 - 8 shown process is only a logically schematic process provided for the convenience of understanding the embodiments of the present application, and does not represent the actual timing of the embodiments of the present application. The embodiments of the present application do not limit Figures 2 - 8 the timing between different steps in the shown process.

[0269] The above mainly introduces the solutions provided by the embodiments of the present application from the perspective of the interaction between each network element. Correspondingly, the embodiments of the present application also provide a communication device, which is used to implement the above various methods. The communication device can be each network element in the above method embodiments, or a device including each of the above network elements, or a component applicable to each of the above network elements. It can be understood that in order to implement the above functions, the communication device includes the corresponding hardware structure and / or software module for executing each function. Those skilled in the art should easily realize that, combining the units and algorithm steps of each example described in the embodiments disclosed in this article, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0270] Embodiments of the present application can divide functional modules of a communication device according to the method embodiments above. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. It should be understood that the division of modules in the embodiments of the present application is illustrative, only a logical function division, and there can be other division methods in actual implementation.

[0271] Figure 9 FIG. shows a schematic structural diagram of a communication device 900. The communication device 900 includes a processing module 901 and a transceiver module 902. Optionally, the communication device 900 may further include a storage module 903. The transceiver module 902, which can also be referred to as a transceiver unit, is used to implement the transceiver function. For example, it can be a transceiver circuit, a transceiver, a transceiver, or a communication interface.

[0272] Taking the communication device 900 as the session management network element in the above embodiment as an example, in a possible implementation:

[0273] The transceiver module 902 is used to obtain the application information subscribed by the terminal device, and the application information includes at least one of the following: fully qualified domain name, application identifier, or data network access identifier. The processing module 901 is used to select a target first network element according to the application information; wherein, the first network element is used to select a local user plane function network element and / or an edge application service.

[0274] Optionally, the processing module 901 is specifically used to: send a first request message including the application information to the network storage function network element through the transceiver module 902, and the first request message is used to request the network storage function network element to select a target first network element; receive, through the transceiver module 902, a first response message for the first request message from the network storage function network element, and the first response message includes information about the target first network element.

[0275] Optionally, the processing module 901 is specifically used to: select a target first network element according to the mapping relationship between the locally configured application information and the first network element.

[0276] Optionally, the processing module 901 is specifically used to: determine a target data network access identifier and / or an IP address of a target edge application service according to the application information and the deployment information of the edge application service; wherein, the deployment information of the edge application service includes the correspondence between the application information and the data network access identifier and / or the IP address of the edge application service; select a target first network element according to the target data network access identifier and / or the IP address of the target edge application service.

[0277] Optionally, the transceiver module 902 is further configured to: send a second request message to a target first network element, where the second request message is used to request the target first network element to select a target edge application service and / or a target user plane function network element.

[0278] Optionally, the transceiver module 902 is further configured to: receive a second response message from the target first network element for the second request message, where the second response message includes information about the target user plane function network element.

[0279] Optionally, the transceiver module 902 is further configured to: receive a third request message from an access mobility management function network element, where the third request message is used to request to establish a session context. The processing module 901 is further configured to determine to select a target first network element according to the third request message.

[0280] Taking the communication device 900 as the access mobility management function network element in the foregoing embodiment as an example, in a possible implementation:

[0281] The transceiver module 902 is configured to receive a session establishment request message from a terminal device. The processing module 901 is configured to select a target first network element according to a first parameter; the first network element is used to select an edge application service, and the first parameter includes one or more of the following information: a data network name, information about a slice associated with the application, information about a first area, where the first area is related to the location of the terminal device.

[0282] The processing module 901 is further configured to determine to select a session management network element according to the session establishment request message. Specifically, when the processing module 901 selects a session management network element according to the first parameter, it selects a target first network element.

[0283] Taking the communication device 900 as the second network element in the foregoing embodiment as an example, in a possible implementation:

[0284] The transceiver module 902 is configured to send deployment information of an edge application service to a first network element serving a second area; where the deployment information of the edge application service includes at least one of the following: a fully qualified domain name, an application identifier, an IP address of the edge application service, or a data network access identifier. The first network element is used to select an edge application service and / or a local user plane function network element.

[0285] Optionally, the transceiver module 902 is further configured to send a fourth request message to the network storage function network element. The fourth request message is used to request to discover the first network element in the second service area. The fourth request message includes information indicating the second area. The transceiver module 902 is further configured to receive information about the first network element in the second service area from the network storage function network element. Specifically, the transceiver module 902 is configured to send deployment information of the edge application service to the first network element in the second service area according to the information about the first network element in the second service area.

[0286] Optionally, the transceiver module 902 is further configured to receive a fifth request message from the first network element. The fifth request message requests to subscribe to the deployment information of the edge application service. Specifically, the transceiver module 902 is configured to send the deployment information of the edge application service to the first network element according to the fifth request message.

[0287] In a possible implementation, the fifth request message includes a second parameter. The second parameter includes at least one of the following: fully qualified domain name, application identifier, or IP address of the edge application service. Specifically, the transceiver module 902 is configured to send the deployment information of the edge application service corresponding to the second parameter to the first network element according to the fifth request message.

[0288] Taking the communication device 900 as the first network element in the above embodiment as an example, in a possible implementation:

[0289] The transceiver module 902 is configured to send a fifth request message. The fifth request message requests to subscribe to the deployment information of the edge application service. The transceiver module 902 is further configured to receive the deployment information of the edge application service from the second network element; wherein, the deployment information of the edge application service includes at least one of the following: fully qualified domain name, application identifier, IP address of the edge application service, or data network access identifier.

[0290] In a possible implementation, the fifth request message includes a second parameter. The second parameter includes at least one of the following: fully qualified domain name, application identifier, or IP address of the edge application service. Specifically, the transceiver module 902 is configured to receive the deployment information of the edge application service corresponding to the second parameter from the second network element.

[0291] All relevant content of each step involved in the above method embodiment can be cited in the function description of the corresponding functional module, and will not be elaborated here.

[0292] Optionally, Figure 9 the modules in can also be called units. For example, the processing module can be called a processing unit, and the transceiver module can be called a transceiver unit. Additionally, in Figure 9 the embodiments shown, the names of each unit may not be the names shown in the figure. For example, the transceiver module can also be called a communication module or a communication unit.

[0293] Figure 9 When each unit in the above is implemented in the form of a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of the present application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application. The storage media storing the computer software product include: various media such as USB flash drives, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical discs that can store program codes.

[0294] In the embodiments of the present application, the communication device 900 is presented in the form of dividing each functional module in an integrated manner. Here, a "module" may refer to an application-specific integrated circuit (ASIC), a circuit, a processor and a memory that execute one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions.

[0295] In a simple embodiment, those skilled in the art can conceive that the communication device 900 can adopt Figure 10 the form of the communication device shown.

[0296] As Figure 10 shown, the communication device 1000 includes one or more processors 1001, a communication line 1002, and at least one communication interface ( Figure 10 only for example, it is exemplary to include a communication interface 1004 and one processor 1001 in the following), and optionally, a memory 1003 may also be included.

[0297] The processor 1001 may be a general-purpose central processing unit (CPU), a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of the programs of the present application solution.

[0298] The communication line 1002 may include a path for connecting different components.

[0299] The communication interface 1004 can be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, terminals, wireless local area networks (WLANs), etc. For example, the transceiver module can be a device such as a transceiver or a transceiver unit. Optionally, the communication interface 1004 can also be a transceiver circuit or an input / output interface located within the processor 1001 for realizing signal input and signal output of the processor.

[0300] The memory 1003 can be a device with storage functions. For example, it can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or it can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), a magnetic storage medium such as a disk storage or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but not limited thereto. The memory can exist independently and be connected to the processor through the communication line 1002. The memory can also be integrated with the processor.

[0301] Among them, the memory 1003 is used to store computer-executable instructions for implementing the solution of this application, and is controlled and executed by the processor 1001. The processor 1001 is used to execute the computer-executable instructions stored in the memory 1003, thereby implementing the communication method provided in the embodiments of this application.

[0302] Alternatively, optionally, in the embodiments of this application, it can also be that the processor 1001 executes the functions related to processing in the communication method provided in the following embodiments of this application, and the communication interface 1004 is responsible for communicating with other devices or communication networks. The embodiments of this application do not make specific limitations in this regard.

[0303] Optionally, the computer-executable instructions in the embodiments of this application can also be referred to as application code. The embodiments of this application do not make specific limitations in this regard.

[0304] In a specific implementation, as an embodiment, the processor 1001 can include one or more CPUs, such as Figure 10 CPU0 and CPU1 in

[0305] In a specific implementation, as an example, the communication device 1000 may include multiple processors, such as Figure 10 the processor 1001 and the processor 1007 in []. Each of these processors can be a single-core processor or a multi-core processor. The processors here may include, but are not limited to, at least one of the following: CPU, microprocessor, digital signal processing (DSP) processor, microcontroller unit (MCU), or artificial intelligence processor and other various computing devices that run software, and each computing device may include one or more cores for executing software instructions to perform operations or processing.

[0306] In a specific implementation, as an example, the communication device 1000 may further include an output device 1005 and an input device 1006. The output device 1005 communicates with the processor 1001 and can display information in various ways. For example, the output device 1005 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 1006 communicates with the processor 1001 and can receive user input in various ways. For example, the input device 1206 can be a mouse, a keyboard, a touch screen device, or a sensing device, etc.

[0307] The above-mentioned communication device 1000 can sometimes also be referred to as a communication equipment, and it can be a general device or a special device. For example, the communication device 1000 can be various network elements, access network devices in the above text, or devices with a Figure 10 similar structure in []. The embodiments of the present application do not limit the type of the communication device 1000.

[0308] In addition, Figure 10 the shown composition structure in [] does not constitute a limitation on the communication device. Except for Figure 10 the shown components, the communication device 1000 may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0309] Optionally, Figure 9 the functions / implementation processes of the transceiver module 902 and the processing module 901 in [] can be achieved through Figure 10The processor 1001 in the communication device 1000 shown implements it by invoking the computer-executable instructions stored in the memory 1003. Alternatively, Figure 9 the function / implementation process of the processing module 901 in Figure 10 can be implemented by the processor 1001 in the communication device 1000 shown invoking the computer-executable instructions stored in the memory 1003, Figure 9 the function / implementation process of the transceiver module 902 in Figure 10 can be implemented by the communication interface 1004 in the communication device 1000 shown.

[0310] It should be understood that one or more of the above modules or units can be implemented in software, hardware, or a combination of both. When any of the above modules or units is implemented in software, the software exists in the form of computer program instructions and is stored in the memory. The processor can be used to execute the program instructions and implement the above method flow. The processor can be built into the SoC or ASIC, or it can be an independent semiconductor chip. In addition to the core for executing software instructions for arithmetic or processing in the processor, it can further include necessary hardware accelerators, such as FPGA, programmable logic device (PLD), or logic circuits for implementing dedicated logic operations.

[0311] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of CPU, microprocessor, DSP chip, MCU, artificial intelligence processor, ASIC, SoC, FPGA, PLD, dedicated digital circuit, hardware accelerator, or non-integrated discrete device, which can run the necessary software or execute the above method flow without relying on software.

[0312] Optionally, the embodiment of the present application further provides a communication device (for example, the communication device can be a chip or a chip system), which includes a processor for implementing the method in any of the above method embodiments. In a possible design, the communication device further includes a memory. The memory is used to store necessary program instructions and data. The processor can call the program code stored in the memory to instruct the communication device to execute the method in any of the above method embodiments. Of course, the memory may not be in the communication device. When the communication device is a chip system, it can be composed of chips or can include chips and other discrete devices. The embodiment of the present application does not make specific limitations on this.

[0313] Optionally, the embodiment of the present application further provides a computer-readable storage medium, in which computer programs or instructions are stored. When it runs on a communication device, it enables the communication device to execute the method described in any of the above method embodiments or any of its implementation manners.

[0314] Optionally, an embodiment of the present application further provides a communication system, which includes a plurality of network elements described in the above method embodiment, for example, including a first network element and a second network element.

[0315] In the above embodiment, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired manner (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that includes one or more media integrated therein. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state drive (SSD)), etc.

[0316] Although the present application has been described in conjunction with various embodiments herein, however, in the process of implementing the claimed present application, those skilled in the art can understand and implement other variations of the disclosed embodiments by viewing the drawings, the disclosure content, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "one" does not exclude a plurality of cases. A single processor or other unit can implement several functions recited in the claims. Certain measures are recited in mutually different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0317] Although the present application has been described in connection with specific features and their embodiments, it will be apparent that various modifications and combinations can be made thereto without departing from the scope of the present application. Accordingly, the present specification and drawings are merely exemplary illustrations of the present application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the scope 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 equivalent technologies, the present application is also intended to include these changes and modifications.

Claims

1. A communication method, characterized in that, The method includes: The session management function network element obtains the application information subscribed by the terminal device, where the application information includes at least one of the following: fully qualified domain name, application identifier, or data network access identifier; The session management function network element selects a target first network element according to the application information; wherein, the first network element is used to select a local user plane function network element and / or an edge application service.

2. The method according to claim 1, wherein The session management function network element selects a target first network element according to the application information, including: The session management function network element sends a first request message to the network storage function network element, where the first request message includes the application information, and the first request message is used to request the network storage function network element to select a target first network element; The session management function network element receives a first response message for the first request message from the network storage function network element, where the first response message includes information about the target first network element.

3. The method according to claim 2, wherein The first request message further includes information about a first area, and the information about the first area is used for the network storage function network element to select a target first network element, and the first area is related to the location of the terminal device.

4. The method according to claim 2 or 3, characterized in that, The first request message further includes first indication information, and the first indication information is used to indicate that the network element requested to be selected is a first network element.

5. The method according to any one of claims 2 to 4, characterized in that The first request message includes second indication information, and the second indication information is used to indicate that the requested network service is to select a user plane function network element, or to establish a session.

6. The method according to claim 1, characterized in that, The session management function network element selects a target first network element according to the application information, including: The session management function network element selects the target first network element according to the mapping relationship between the application information configured locally and the first network element.

7. The method according to claim 1, wherein The session management function network element selects a target first network element according to the application information, including: The session management function network element determines a target data network access identifier and / or an IP address of a target edge application service according to the application information and the deployment information of the edge application service; wherein, the deployment information of the edge application service includes the corresponding relationship between the application information and the data network access identifier and / or the IP address of the edge application service; The session management function network element selects the target first network element according to the target data network access identifier and / or the IP address of the target edge application service.

8. The method according to any one of claims 1-7, characterized in that, The method further includes: The session management function network element sends a second request message to the target first network element, and the second request message is used to request the target first network element to select a target edge application service and / or a target user plane function network element.

9. The method according to claim 8, wherein The second request message includes the application information, and the application information is used for the target first network element to select a target edge application service and / or a target user plane function network element.

10. The method according to claim 9, characterized in that, The application information further includes one or more of the following information: a delay requirement for transmission between the user plane function network element and the edge application service, or a load requirement for the user plane function network element.

11. The method according to any one of claims 8-10, characterized in that, The method further includes: The session management function network element receives a second response message for the second request message from the target first network element, and the second response message includes information of the target user plane function network element.

12. The method according to any one of claims 1-11, characterized in that, The method further includes: The session management function network element receives a third request message from the access and mobility management function network element, and the third request message is used to request the establishment of a session context; The session management function network element determines to select a target first network element according to the third request message.

13. A communication method, characterized in that, The method includes: The access and mobility management function network element receives a session establishment request message from a terminal device; The access and mobility management function network element selects a target first network element according to a first parameter; the first network element is used to select an edge application service, and the first parameter includes one or more of the following information: data network name, information of a slice associated with the application, information of a first area, and the first area is related to the location of the terminal device.

14. The method according to claim 13, wherein The method further includes: The access and mobility management function network element determines to select a session management network element according to the session establishment request message; The access and mobility management function network element selects a target first network element according to the first parameter, including: When the access and mobility management function network element selects a session management network element according to the first parameter, it selects the target first network element.

15. A communication method, characterized in that, The method includes: A second network element sends deployment information of an edge application service to a first network element serving a second area; wherein, the deployment information of the edge application service includes at least one of the following: fully qualified domain name, application identifier, IP address of the edge application service, or data network access identifier; Wherein, the first network element is used to select an edge application service and / or a local user plane function network element.

16. The method according to claim 15, characterized in that, The method further includes: The second network element sends a fourth request message to a network storage function network element, and the fourth request message is used to request to discover a first network element serving a second area, and the fourth request message includes information indicating the second area; The second network element receives information of the first network element serving the second area from the network storage function network element; The second network element sends deployment information of an edge application service to a second network element serving a first area, including: The second network element sends the deployment information of the edge application service to the first network element serving the second area according to the information of the first network element serving the second area.

17. The method according to claim 16, wherein The fourth request message includes at least one of the following information: a third indication information, or a fourth indication information; wherein, the third indication information is used to indicate that the network element requested to be discovered is a first network element, and the fourth indication information is used to indicate that the requested service is to provide deployment information of an edge application service.

18. The method according to claim 15, wherein The method further includes: The second network element receives a fifth request message from the first network element, and the fifth request message requests to subscribe to deployment information of an edge application service; The second network element sends deployment information of an edge application service to a first network element serving a second area, including: The second network element sends the deployment information of the edge application service to the first network element according to the fifth request message.

19. The method according to claim 18, characterized in that, The fifth request message includes a second parameter, and the second parameter includes at least one of the following: fully qualified domain name, application identifier, or IP address of the edge application service; The second network element sends deployment information of the edge application service to the first network element serving the second area, including: The second network element sends, according to the fifth request message, deployment information of the edge application service corresponding to the second parameter to the first network element.

20. A communication method, characterized in that, The method includes: A first network element sends a fifth request message to a second network element, and the fifth request message requests to subscribe to deployment information of an edge application service; The first network element receives deployment information of the edge application service from the second network element; wherein, the deployment information of the edge application service includes at least one of the following: fully qualified domain name, application identifier, IP address of the edge application service, or data network access identifier.

21. The method according to claim 20, wherein The fifth request message includes a second parameter, and the second parameter includes at least one of the following: fully qualified domain name, application identifier, or IP address of the edge application service; The first network element receives deployment information of the edge application service from the second network element, including: The first network element receives deployment information of the edge application service corresponding to the second parameter from the second network element.

22. A communication system, characterized in that, The communication system includes a first network element and a second network element; The second network element is configured to send deployment information of the edge application service to the first network element, wherein the deployment information of the edge application service includes at least one of the following: fully qualified domain name, application identifier, IP address of the edge application service, or data network access identifier; The first network element is configured to receive the deployment information of the edge application service; The first network element is further configured to select an edge application service and / or a local user plane function network element.

23. The communication system according to claim 22, wherein The first network element is further configured to send a fifth request message to the second network element, and the fifth request message requests to subscribe to deployment information of the edge application service.

24. The communication system according to claim 22, wherein The second network element is further configured to send a fourth request message to a network storage function network element, and the fourth request message is used to request to discover the first network element serving the second area, and the fourth request message includes information indicating the second area; The second network element is further configured to receive information of the first network element serving the second area from the network storage function network element; The second network element sends deployment information of the edge application service to the second network element, including: sending the deployment information of the edge application service to the first network element serving the second area according to the information of the first network element serving the second area.

25. The communication system according to any one of claims 22-24, characterized in that, The communication system further includes a session management function network element; The session management function network element is configured to obtain application information subscribed by a terminal device, and the application information includes at least one of the following: fully qualified domain name, application identifier, or data network access identifier; The session management function network element is further configured to select a target first network element according to the application information.

26. The communication system according to any one of claims 22-24, characterized in that, The communication system further includes an access and mobility management function network element; The access and mobility management function network element is configured to receive a session establishment request message from a terminal device; The access mobility management functional network element is further configured to select a target first network element according to a first parameter, where the first parameter includes one or more pieces of the following information: data network name, information of a slice associated with an application, and information of a first area, and the first area is related to the location of the terminal device.

27. A network element, characterized in that, The network element includes a module or unit configured to execute the method according to any one of claims 1-12; or, the network element includes a module or unit configured to execute the method according to claim 13 or 14; or, the network element includes a module or unit configured to execute the method according to any one of claims 15-19; or, the network element includes a module or unit configured to execute the method according to claim 20 or 21.

28. A communication device, characterized in that, The communication device includes: a processor; the processor is configured to execute a computer program or instruction stored in a memory, so that the communication device executes the method according to any one of claims 1-12 or 13-14 or 15-19 or 20-21.

29. A chip system, characterized in that, Comprising: A processor and an interface circuit; The interface circuit is configured to receive a computer execution instruction and transmit it to the processor; The processor is configured to execute the computer execution instruction, so that the communication device executes the method according to any one of claims 1-12 or 13-14 or 15-19 or 20-21.

30. A computer-readable storage medium, characterized in that, A computer program or instruction is stored thereon, and when the computer program or instruction is executed by a computer, the computer is caused to execute the method according to any one of claims 1-12 or 13-14 or 15-19 or 20-21.

Images