CN116420393A

CN116420393A - Identification transmitting method and communication device

Info

Publication number: CN116420393A
Application number: CN202080106822.1A
Authority: CN
Inventors: 葛翠丽; 杨艳梅; 胡雅婕
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-11-10
Filing date: 2020-11-10
Publication date: 2023-07-11
Also published as: WO2022099484A1

Abstract

The application discloses an identification sending method and a communication device, which relate to the field of communication and are used for avoiding unnecessary DNAI (digital media access control) change or UPF (uplink packet transfer) device change of a network so as to save signaling interaction resources. The identification sending method comprises the following steps: the session management function device acquires first information and flow information of an application, wherein the first information is used for indicating that a data network access identifier DNAI is changed and notifying the application function device when the application is deployed on an edge data network corresponding to a changed target DNAI; when the DNAI is changed, the session management function device sends the target DNAI to the application function device according to the first information.

Description

Identification transmitting method and communication device

Technical Field

The present disclosure relates to the field of communications, and in particular, to a method and a communications device for sending an identifier.

Background

In a multiple access edge computing (multi-access edge computing, MEC) system, applications running on terminal equipment are served by an edge data network (edge data network, EDN) through user plane functions (user plane function, UPF) means. When the terminal device moves outside the current service area, a session management function (session management function, SMF) means is triggered to change UPF means, and an application function (application function, AF) means changes the data network access identity (data network access identifier, DNAI) (for identifying EDN).

However, if the AF device does not have the capability to instantiate an application on the EDN and the application is not deployed on the target EDN, both the UPF device change and the DNAI change are unnecessary, wasting signaling interaction resources.

Disclosure of Invention

The embodiment of the application provides an identification sending method and a communication device, which are used for avoiding unnecessary DNAI (digital media access control) change or UPF (unified power flow) device change of a network so as to save signaling interaction resources.

In order to achieve the above purpose, the embodiments of the present application adopt the following technical solutions:

in a first aspect, there is provided an identifier sending method, including: the session management function device acquires first information and flow information of an application, wherein the first information is used for indicating that a data network access identifier DNAI is changed and notifying the application function device when the application is deployed on an edge data network corresponding to a changed target DNAI; when the DNAI is changed, the session management function device sends the target DNAI to the application function device according to the first information.

According to the identification sending method provided by the embodiment of the invention, the SMF device acquires the first information and the application flow information, wherein the first information is used for indicating that the AF device is informed when the DNAI is changed and the application is deployed on the EDN corresponding to the changed target DNAI, namely that the AF device does not have the application instantiating capability, and the SMF device is informed of the changed target DNAI when the DNAI is changed and the application is deployed on the EDN corresponding to the changed target DNAI, so that the AF device is not informed when the application is not deployed on the EDN corresponding to the target DNAI, and thus unnecessary DNAI change or UPF device change (such as adding, modifying or deleting) by the network under the condition that the AF device selects not to perform application context migration or application context migration failure can be avoided, and signaling interaction resources can be saved.

In one possible implementation, the session management function device obtains first information, including: the session management function device receives first information from the application function device. I.e. the AF device instructs the SMF network element that the AF device does not have the capability to instantiate an application.

In one possible implementation, the session management function device obtains first information, including: when the session management function device does not receive the application location information from the application function device, the session management function device receives DNAI change subscription information from the application function device, and determines that the DNAI change subscription information is the first information. I.e. the SMF network element determines by itself that the AF device does not have the capability to instantiate an application.

In one possible embodiment, the method further comprises: the session management function device sends third information to the application function device, wherein the third information is used for indicating that the edge data network corresponding to the target DNAI is deployed with the application. In one possible implementation, whether the application is deployed on the EDN corresponding to the target DNAI may be indicated by different values of the same cell. In another possible implementation manner, the application is deployed on the EDN corresponding to the target DNAI and the EDN corresponding to the target DNAI is not deployed on the EDN corresponding to the target DNAI, which is included in the user plane path management notification (UP path management notification) message; or, the AF request message includes the third information to indicate that the application is not deployed on the EDN corresponding to the target DNAI, and the AF request message does not include the third information to indicate that the application is deployed on the EDN corresponding to the target DNAI.

In one possible embodiment, the method further comprises: if the edge data network corresponding to the target DNAI is deployed with an application, the session management function device activates the user plane path of the target DNAI. I.e. the SMF network element may perform a late notification (Late Notification).

In one possible embodiment, the method further comprises: if the edge data network corresponding to the target DNAI is not deployed with the application, the session management function device configures a user plane path of the target DNAI. I.e. the SMF network element may perform an early notification (Early Notification).

In a second aspect, there is provided an identifier sending method, including: the application function device sends first information and flow information of the application to the session management function device, wherein the first information is used for indicating that the access identifier DNAI of the data network is changed and notifying the application function device when the application is deployed on the edge data network corresponding to the changed target DNAI; the application function device receives the target DNAI from the session management function device.

In one possible embodiment, the method further comprises: the application function device receives third information from the session management function device, where the third information is used to indicate that an application is deployed on the edge data network corresponding to the target DNAI. In one possible implementation, whether the application is deployed on the EDN corresponding to the target DNAI may be indicated by different values of the same cell. In another possible implementation manner, the application is deployed on the EDN corresponding to the target DNAI and the EDN corresponding to the target DNAI is not deployed on the EDN corresponding to the target DNAI, which is included in the user plane path management notification (UP path management notification) message; or, the AF request message includes the third information to indicate that the application is not deployed on the EDN corresponding to the target DNAI, and the AF request message does not include the third information to indicate that the application is deployed on the EDN corresponding to the target DNAI.

In a third aspect, there is provided an identifier sending method, including: the session management function device obtains second information, wherein the second information is used for indicating that the application function device is notified as long as the data network access identifier DNAI is changed; when the DNAI is changed, the session management function device transmits the changed target DNAI to the application function device according to the second information.

According to the identifier sending method provided by the embodiment of the application, the SMF device acquires the second information, the second information is used for indicating that the AF device is informed only if the DNAI is changed, the AF device is indicated to have the instantiation application capability, the SMF device can inform the AF device of the changed target DNAI whenever the DNAI is changed, and the AF device can smoothly carry out application context migration no matter whether the application is deployed on the EDN corresponding to the target DNAI, so that the AF device can be prevented from selecting not to carry out application context migration or failing to carry out application context migration, and unnecessary DNAI change or UPF device change (such as adding, modifying or deleting) by a network is avoided, and signaling interaction resources can be saved.

In one possible implementation, the session management function device obtains the second information, including: the session management function device receives the second information from the application function device. The second information and the first information may be different values of the same cell; alternatively, the AF request message includes a certain cell indicating the first information and does not include a certain cell indicating the second information; alternatively, a certain cell is included in the AF request message to indicate the second information, and a certain cell is not included to indicate the first information.

In one possible implementation, the session management function device obtains first information, including: when the session management function device receives the application location information from the application function device, the session management function device receives DNAI change subscription information from the application function device, and determines that the DNAI change subscription information is the second information. I.e. the SMF network element determines itself that the AF device has the capability to instantiate an application.

In one possible embodiment, the method further comprises: the session management function device receives traffic information of an application from the application function device; the session management function device sends third information to the application function device, where the third information is used to indicate whether an application is deployed on the edge data network corresponding to the target DNAI. In one possible implementation, whether the application is deployed on the EDN corresponding to the target DNAI may be indicated by different values of the same cell. In another possible implementation manner, the application is deployed on the EDN corresponding to the target DNAI and the EDN corresponding to the target DNAI is not deployed on the EDN corresponding to the target DNAI, which is included in the user plane path management notification (UP path management notification) message; or, the AF request message includes the third information to indicate that the application is not deployed on the EDN corresponding to the target DNAI, and the AF request message does not include the third information to indicate that the application is deployed on the EDN corresponding to the target DNAI.

In a fourth aspect, there is provided an identifier sending method, including: the application function device sends second information to the session management function device, wherein the second information is used for indicating that the application function device is notified as long as the data network access identifier DNAI is changed; the application function device receives the changed target DNAI from the session management function device.

In one possible embodiment, the method further comprises: the application function device sends the flow information of the application to the session management function device; the application function device receives third information from the session management function device, where the third information is used to indicate whether an application is deployed on the edge data network corresponding to the target DNAI. In one possible implementation, whether the application is deployed on the EDN corresponding to the target DNAI may be indicated by different values of the same cell. In another possible implementation manner, the application is deployed on the EDN corresponding to the target DNAI and the EDN corresponding to the target DNAI is not deployed on the EDN corresponding to the target DNAI, which is included in the user plane path management notification (UP path management notification) message; or, the AF request message includes the third information to indicate that the application is not deployed on the EDN corresponding to the target DNAI, and the AF request message does not include the third information to indicate that the application is deployed on the EDN corresponding to the target DNAI.

In a fifth aspect, there is provided an identification transmitting method, including: the application function device sends an application function request message to the session management function device, wherein the application function request message is used for subscribing a data network access identifier DNAI change event, and the application function request message comprises flow information of an application; the application function device receives the changed target DNAI and third information from the session management function device, where the third information is used to indicate whether an application is deployed on an edge data network corresponding to the target DNAI.

According to the identification sending method provided by the embodiment of the application, the SMF device acquires one of the first information or the second information and the traffic information of the application. The first information is used for indicating that the AF device is informed when the DNAI is changed and the application is deployed on the EDN corresponding to the changed target DNAI, namely indicating that the AF device does not have the application instantiating capability, and when the DNAI is changed and the application is deployed on the EDN corresponding to the changed target DNAI, the SMF device is informed of the changed target DNAI by the AF device, so that the AF device is not informed when the application is not deployed on the EDN corresponding to the target DNAI, and thus unnecessary DNAI change or UPF device change (such as adding, modifying or deleting) by the network under the condition that the AF device selects not to perform application context migration or application context migration fails can be avoided, and signaling interaction resources can be saved. The second information is used for indicating that the AF device is informed if the DNAI is changed, and indicating that the AF device has the instantiation application capability, and the SMF device can inform the AF device of the changed target DNAI if the DNAI is changed, so that the AF device can smoothly perform application context migration no matter whether the application is deployed on the EDN corresponding to the target DNAI, and therefore, the AF device can be prevented from selecting not to perform application context migration or failing to perform application context migration, unnecessary DNAI change or UPF device change (such as adding, modifying or deleting) by the network is avoided, and signaling interaction resources can be saved.

In a sixth aspect, there is provided an identification transmitting method, including: the session management function device acquires first information and flow information of an application, wherein the first information is used for indicating that a data network access identifier DNAI is changed and notifying the application function device when the application is deployed on an edge data network corresponding to a changed target DNAI; when the DNAI is changed, the session management function device sends a target DNAI to the application function device according to the first information; the application function device receives the target DNAI from the session management function device.

In one possible implementation, the session management function device obtains first information, including: the application function device sends first information to the session management function device; the session management function device receives first information from the application function device.

In one possible implementation, the session management function device obtains first information, including: the application function device sends DNAI change subscription information to the session management function device; when the session management function device does not receive the application location information from the application function device, the session management function device receives the DNAI change subscription information and determines that the DNAI change subscription information is the first information.

In one possible embodiment, the method further comprises: the session management function device sends third information to the application function device, wherein the third information is used for indicating that an edge data network corresponding to the target DNAI is deployed with an application; the application function device receives the third information from the session management function device.

In one possible embodiment, the method further comprises: if the edge data network corresponding to the target DNAI is deployed with an application, the session management function device activates the user plane path of the target DNAI.

In one possible embodiment, the method further comprises: if the edge data network corresponding to the target DNAI is not deployed with the application, the session management function device configures a user plane path of the target DNAI.

In a seventh aspect, there is provided an identification transmitting method, including: the session management function device obtains second information, wherein the second information is used for indicating that the application function device is notified as long as the data network access identifier DNAI is changed; when the DNAI is changed, the session management function device sends the changed target DNAI to the application function device according to the second information; the application function device receives the target DNAI from the session management function device.

In one possible implementation, the session management function device obtains the second information, including: the application function device sends second information to the session management function device; the session management function device receives the second information from the application function device.

In one possible implementation, the session management function device obtains the second information, including: the application function device sends application position information and DNAI change subscription information to the session management function device; when the session management function device receives the application location information, the session management function device receives the DNAI change subscription information, and determines that the DNAI change subscription information is the second information.

In one possible embodiment, the method further comprises: the application function device sends the flow information of the application to the session management function device; the session management function device receives traffic information from the application function device; the session management function device sends third information to the application function device, wherein the third information is used for indicating whether an edge data network corresponding to the target DNAI is deployed with an application or not; the application function device receives the third information from the session management function device.

An eighth aspect provides an identifier sending method, including: the application function device sends an application function request message to the session management function device, wherein the application function request message is used for subscribing a data network access identifier DNAI change event, and the application function request message comprises flow information of an application; the session management function device receives the application function request message; the session management function device obtains one of the first information or the second information and traffic information of the application; the first information is used for indicating that the data network access identifier DNAI is changed and notifying an application function device when an application is deployed on the edge data network corresponding to the changed target DNAI; the second information is used for indicating that the application function device is informed as long as the data network access identifier DNAI is changed; when the DNAI is changed, the session management function device sends the changed target DNAI and third information to the application function device according to the first information or the second information, wherein the third information is used for indicating whether an application is deployed on an edge data network corresponding to the target DNAI; the application function device receives the target DNAI and the third information from the session management function device.

In one possible embodiment, the session management function device acquires one of the first information or the second information, including: when the session management function device does not receive the application position information from the application function device, the session management function device receives DNAI change subscription information from the application function device, and determines the DNAI change subscription information to be first information; when the session management function device receives the application location information from the application function device, the session management function device receives the DNAI change subscription information and determines that the DNAI change subscription information is the second information.

A ninth aspect provides a communication device, including a processing module and a transceiver module, where the processing module is configured to obtain first information and traffic information of an application, where the first information is used to indicate that a data network access identifier DNAI is changed and an application is deployed on an edge data network corresponding to the changed target DNAI, and notify an application function device; and the receiving and transmitting module is used for transmitting the target DNAI to the application function device by the session management function device according to the first information when the DNAI is changed.

In one possible embodiment, the transceiver module is configured to receive the first information from the application function device.

In one possible implementation, when the transceiver module does not receive the application location information from the application function device, receives DNAI change subscription information from the application function device, the processing module is configured to determine that the DNAI change subscription information is the first information.

In one possible implementation manner, the transceiver module is configured to send third information to the application function device, where the third information is used to indicate that the edge data network corresponding to the target DNAI is deployed with an application.

In one possible implementation, the processing module is configured to activate a user plane path of the target DNAI if an edge data network to which the target DNAI corresponds is deployed with an application.

In one possible implementation, the processing module is configured to configure a user plane path of the target DNAI if the edge data network to which the target DNAI corresponds is not deployed with an application.

In a tenth aspect, a communication device is provided, including a transceiver module, where the transceiver module is configured to send first information to a session management function device, where the first information is configured to indicate that a data network access identifier DNAI is changed and an application is deployed on an edge data network corresponding to the changed target DNAI, and notify the application function device; the target DNAI is received from the session management function device.

In one possible implementation, the transceiver module is configured to receive third information from the session management function device, where the third information is used to indicate that an application is deployed on the edge data network corresponding to the target DNAI.

In an eleventh aspect, a communication device is provided, including a processing module and a transceiver module, where the processing module is configured to obtain second information, where the second information is configured to instruct an application function device to be notified whenever a data network access identifier DNAI is changed; when the DNAI is changed, the transceiver module is configured to send the changed target DNAI to the application function device according to the second information.

In one possible embodiment, the transceiver module is configured to receive the second information from the application function device.

In one possible implementation, when the transceiver module receives the application location information from the application function device, receives DNAI change subscription information from the application function device, the processing module is configured to determine that the DNAI change subscription information is the second information.

In one possible implementation, the transceiver module is configured to receive traffic information of an application from an application function device; and sending third information to the application function device, wherein the third information is used for indicating whether the edge data network corresponding to the target DNAI is deployed with the application.

In one possible implementation, if the edge data network to which the target DNAI corresponds is deployed with an application, the processing module is configured to activate a user plane path of the target DNAI.

In one possible implementation, if the edge data network to which the target DNAI corresponds is not deployed with an application, the processing module is configured to configure a user plane path of the target DNAI.

In a twelfth aspect, a communication device is provided, including a transceiver module, where the transceiver module is configured to send second information to a session management function device, where the second information is configured to instruct an application function device to be notified whenever a data network access identifier DNAI is changed; the modified target DNAI is received from the session management function device.

In one possible implementation, the transceiver module is configured to send traffic information of an application to the session management function device; and receiving third information from the session management function device, wherein the third information is used for indicating whether an application is deployed on the edge data network corresponding to the target DNAI.

In a thirteenth aspect, a communication device is provided, including a transceiver module, where the transceiver module is configured to send an application function request message to a session management function device, where the application function request message is used to subscribe to a data network access identifier DNAI change event, and the application function request message includes flow information of an application; and receiving the changed target DNAI and third information from the session management function device, wherein the third information is used for indicating whether an application is deployed on the edge data network corresponding to the target DNAI.

In a fourteenth aspect, there is provided a communication device comprising a processor, the processor being connected to a memory, the memory being for storing a computer program, the processor being for executing the computer program stored in the memory to cause the communication device to perform a method as in the first aspect and any of its embodiments, or to perform a method as in the third aspect and any of its embodiments, or to perform a method as in the sixth to eighth aspects corresponding to the session management function device.

In a fifteenth aspect, there is provided a communication device comprising a processor, the processor being connected to a memory, the memory being for storing a computer program, the processor being for executing the computer program stored in the memory to cause the communication device to perform a method as described in the second aspect and any of its embodiments, or to perform a method as described in the fourth aspect and any of its embodiments, or to perform a method as described in the fifth aspect and any of its embodiments, or to perform a method as described in the sixth to eighth aspects as corresponding to the application function device.

In a sixteenth aspect, there is provided a computer readable storage medium having stored therein a computer program which, when run on a computer, causes the computer to perform the method according to the first aspect and any of its embodiments, or to perform the method according to the third aspect and any of its embodiments, or to perform the method according to the session management function device according to the sixth to eighth aspects.

A seventeenth aspect provides a computer readable storage medium having a computer program stored therein, which when run on a computer causes the computer to perform the method according to the second aspect and any of its embodiments, or to perform the method according to the fourth aspect and any of its embodiments, or to perform the method according to the fifth aspect and any of its embodiments, or to perform the method according to the application function device according to the sixth to eighth aspects.

In an eighteenth aspect, there is provided a computer program product comprising instructions which, when run on a computer or processor, cause the computer or processor to perform the method according to the first aspect and any of the embodiments, or to perform the method according to the third aspect and any of the embodiments, or to perform the method according to the session management function device according to the sixth to eighth aspects.

In a nineteenth aspect, there is provided a computer program product comprising instructions which, when run on a computer or processor, cause the computer or processor to perform the method according to the second aspect and any of its embodiments, or to perform the method according to the fourth aspect and any of its embodiments, or to perform the method according to the fifth aspect and any of its embodiments, or to perform the method according to the application functionality device according to the sixth to eighth aspects.

In a twentieth aspect, there is provided a communication system comprising a communication device as in the ninth aspect and any one thereof, and a communication device as in the tenth aspect and any one thereof; or comprises a communication device according to the eleventh aspect and a communication device according to the twelfth aspect and any one of them; or, a communication device as described in the thirteenth aspect; or comprises a communication device according to the fourteenth aspect and a communication device according to the fifteenth aspect and any one of them.

Technical effects of the sixth to twentieth aspects refer to the contents of the first to fifth aspects and are not repeated here.

Drawings

Fig. 1 is a schematic architecture diagram of a 5G communication system according to an embodiment of the present application;

fig. 2 is a schematic architecture diagram of an MEC communication system according to an embodiment of the present application;

FIG. 3 is a flow chart of an application context migration process according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a DNAI modification according to an embodiment of the present application;

FIG. 5 is a schematic diagram of the basic principles of the present application provided in an embodiment of the present application;

fig. 6A is a schematic flow chart of a method for sending an identifier according to an embodiment of the present application;

Fig. 6B is a second flowchart of an identifier sending method provided in the embodiment of the present application;

fig. 6C is a flowchart of a method for sending an identifier according to an embodiment of the present application;

fig. 7 is a flowchart of a method for sending an identifier according to an embodiment of the present application;

fig. 8 is a flowchart fifth of a method for sending an identifier according to an embodiment of the present application;

fig. 9A is a flowchart sixth of a method for sending an identifier according to an embodiment of the present application;

fig. 9B is a flowchart seventh of a method for sending an identifier according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a second communication device according to an embodiment of the present application;

fig. 12 is a schematic structural diagram III of a communication device according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of a communication device according to an embodiment of the present application.

Detailed Description

As used in this application, the terms "component," "module," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, the components may be, but are not limited to: a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of example, both an application running on a computing device and the computing device can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. Furthermore, these components can execute from various computer readable media having various data structures thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the internet with other systems by way of the signal).

First, a description will be given of a communication system architecture to which an embodiment of the present application relates.

The 3gpp SA2 standard defines a 5G communication system architecture for application function (application function, AF) traffic (traffic influence) management, as shown in fig. 1, comprising: terminal equipment 101, radio access network (R) AN device 102, user plane function (user plane function, UPF) device 103, data Network (DN) 104, access and mobility management function (access and mobility management function, AMF) device 105, session management function (session management function, SMF) device 106, policy control device (policy control function, PCF) device 107, unified data management device (unified data management, UDM) device 108, application function (application function, AF) device 109, authentication server function (authentication server function, AUSF) device 110, and network slice selection function (network slice selection function, NSSF) device 111 and network slice specific authentication and authorization function (network slice specific authentication and authorization function, NSSAAF) device 112, network opening function (network exposure function, NEF) device 113, and service capability opening platform (service capability exposure function, SCEF) device 114. The core network device mainly includes a UPF device 103, an AMF device 105, an SMF device 106, a PCF device 107, a UDM device 108, an AUSF device 110, an NSSF device, an NSSAAF device 112, a NEF device 113, and an SCEF device 114. The NEF device 113 and the SCEF device 114 may be co-located.

It should be noted that the interface names between the devices in fig. 1 are only an example, and the interface names may be other names in the specific implementation, and are not limited. For example, the interface between terminal equipment 101 and AMF device 105 may be an N1 interface, the interface between RAN device 102 and AMF device 105 may be an N2 interface, the interface between RAN device 102 and UPF device 103 may be an N3 interface, the interface between UPF device 103 and SMF device 106 may be an N4 interface, the interface between PCF device 107 and AF device 109 may be an N5 interface, the interface between UPF device 103 and DN 104 may be an N6 interface, the interface between SMF device 106 and PCF device 107 may be an N7 interface, the interface between AMF device 105 and UDM device 108 may be an N8 interface, the interface between UPF device 103 and UPF device 103 may be an N9 interface, the interface between AMF device 105 and SMF device 106 may be an N11 interface, the interface between PCF device 107 and UDM device 108 may be an N25 interface, the interface between amsf device 105 and AUSF device 110 may be an N12 interface between asf device 110 and an asf device 108, the interface between asf device 112 and an asf device 112 may be an ef device 112 or an ef device 112 (e.f) may be an N12 interface between asf device 112 and an asf device 112, an asf device 112 or an asf device 112 between asf device 112 and an asf device 112 may be an N112 (e.e.e.e.e.112 interface between asf device 112 and an N12 and an interface between asf device).

The functions of the respective devices (means) are described below:

terminal device 101 may include various handheld devices, vehicle mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities; and may also include a subscriber unit (subscriber unit), a cellular phone (cell phone), a smart phone (smart phone), a wireless data card, a personal digital assistant (personal digital assistant, PDA) computer, a tablet computer, a wireless modem (modem), a hand-held device (handheld), a laptop computer (laptop), a cordless phone (cord) or a wireless local loop (wireless local loop, WLL) station, a machine type communication (machine type communication, MTC) terminal, a User Equipment (UE), a Mobile Station (MS), a terminal device (terminal device), a relay user equipment, or the like. Wherein the relay user equipment may be a 5G home gateway (residential gateway, RG). For convenience of description, the above-mentioned devices may be collectively referred to as terminal devices.

RAN apparatus 102 provides equipment for wireless access to terminal equipment 101 including, but not limited to, a gndeb, a wireless fidelity (wireless fidelity, wi-Fi) access point, a worldwide interoperability for microwave access (world interoperability for microwave access, wiMAX) base station, and the like. The RAN device may be a RAN device, which is a RAN device accessing a 5G core network, may be an NR gndeb, or may be an evolved universal terrestrial radio access (evolved universal terrestrial radio access, E-UTRA) device in LTE.

The UPF devices 103 are mainly responsible for handling user messages, such as forwarding, charging, etc. The IP address/prefix (if supported) of the terminal device may be allocated in response to a request by the SMF device, an external protocol data unit (protocol data unit, PDU) session point connected to the data network, packet routing and forwarding (e.g. supporting routing traffic to an upstream classifier of the data network instance, supporting Branching point (supporting multi-host PDU session), packet inspection, etc. user plane functions. The UPF device may be a unicast UPF device, a multicast UPF device, or a multicast broadcast user plane function (MB-UPF) device. The unicast UPF device and the multicast UPF device may be the same UPF device. The unicast UPF device is functionally identical to the multicast UPF device, except that the unicast UPF device transmits a unicast data stream of the current terminal device (the UPF device may also transmit a multicast data stream, such as a multicast data stream of a multicast service of another terminal device), and the multicast UPF device transmits a multicast data stream of the current terminal device (the UPF device may also transmit a unicast data stream). Both unicast UPF devices and multicast UPF devices send data streams in the form of tunnels to RAN devices. The MB-UPF device is a UPF device dedicated to transmitting multicast data streams, i.e. to transmit multicast data streams, and to transmit multicast data streams in multicast form to the RAN device.

DN 104 refers to a network providing a data transmission service for a user, for example, a service network of an operator or a third party, an IP Multimedia Service (IMS), an Internet service (Internet), etc. may be provided. Terminal device 101 accesses DN 104 by establishing a protocol data unit (protocol data unit, PDU) session between the terminal device, RAN apparatus 102, UPF apparatus 103, and DN 104.

The AMF device 105 is mainly responsible for mobility management in mobile networks, such as user location update, user registration network, user handover, etc.

The SMF device 106 is mainly responsible for session management of terminal devices in the mobile network, e.g. session establishment, modification, release. For example, specific functions include: assigning and managing IP addresses for users, selecting and controlling UPF devices that provide message forwarding functionality, configuring forking on UPF devices, routing traffic to appropriate destinations, determining service and session continuity (service and session sontinuity, SSC) modes, etc.

PCF device 107 is responsible for providing policies, such as QoS policies, slice selection policies, etc.

The UDM device 108 is used for storing user data such as subscription information, authentication/authorization information.

The AF device 109, which may also be referred to as a server, is responsible for providing services to the 3GPP network, such as affecting traffic routing, interacting with PCF devices for policy control, etc. The AF device interacts with other control plane devices of the 5G network on behalf of the application, including providing quality of service (quality of service, qoS) policy requirements, routing policy requirements, etc. The SMF device routing decisions affecting PDU sessions affect UPF device (re) selection, route user traffic to the local access data network, responsible for application relocation within the local data network.

The AUSF device 110 is used to authenticate and authorize a user.

NSSF device 111 is used to centrally manage the slicing functions.

The NSSAAF device 112 is used to support network slice specific authentication and authorization procedures and may communicate with an AAA (authentication, authorization and accounting) server or an AAA proxy.

The NEF device 113 (or SCEF device 114) is responsible for internal and external network isolation for network capability opening, including open Monitoring (Monitoring) capabilities, policy/charging capabilities, and analytics reporting capabilities, among others.

The MEC communication system architecture as shown in fig. 2 is defined in the 3gpp SA6 standard for application-enabled multi-access edge computing (multi-access edge computing, MEC), comprising: terminal equipment 21, core network device 22, edge data network (edge data network, EDN) 23, and edge configuration server (edge configuration server, ECS) 24. The terminal device 211 comprises an application client (application client) 211 and an edge-enabled client (edge enabler client, EEC) 212. The EDN 23 includes an edge application server (edge application server, EAS) 231 and an edge enabling server (edge enabler server, EES) 232. The core network device 22 may include the NEF device 113 (or SCEF device 114) of fig. 1. The functions of the terminal device 21 and the core network means 22 are described in fig. 1 and are not repeated here.

It should be noted that the names of interfaces between the parts in fig. 2 are only an example, and the names of interfaces may be other names in the specific implementation, and are not limited. For example, the data stream may be transferred between the application client 211 and the EAS 231 through the core network device 22 (e.g., the NEF device 113 (or the SCEF device 114)), the interface between the EEC 212 and the EES 232 may be an EDGE-1 interface, the interface between the core network device 22 (e.g., the NEF device 113 (or the SCEF device 114)) and the EES 232 may be an EDGE-2 interface, the interface between the EAS 231 and the EES 232 may be an EDGE-3 interface, the interface between the EEC 212 and the ECS 24 may be an EDGE-4 interface, the interface between the application client 211 and the EEC 212 may be an EDGE-5 interface, the interface between the EES 232 and the ECS 24 may be an EDGE-6 interface, the interface between the core network device 22 (e.g., the NEF device 113 (or the SCEF device 114)) and the EAS 231 may be an EDGE-7 interface, the interface between the core network device 22 (e.g., the NEF device 113 (or the SCEF device 114)) and the ECS 24 may be an EDGE-8 interface, and the different EESs 232 may be an EDGE-9 interface.

Various concepts involved in the communication system architecture are described below:

the MEC can provide needed services and cloud computing functions for telecommunication users nearby by utilizing the wireless access network, so that a carrier class service environment with high performance, low delay and high bandwidth is created, downloading of various contents, services and applications in the network is accelerated, and consumers enjoy uninterrupted high-quality network experience.

EDN 23: in one understanding, an EDN is considered as a network logic concept, and typically corresponds to only one data network, namely a local data network (local DN), which has an edge-enabled function, and can be identified by a data network access identifier (data network access identifier, DNAI) or a data network name (data network name, DNN). In another understanding, taking an EDN as a concept that is peer-to-peer with a central cloud, typically corresponding to a local data center (geographical location concept), the EDN may include a plurality of local data networks (local DNs) that may be identified by DNAI.

Where a local data network (local DN) refers to an access point (access point) of a data network that is very close to a user's attachment point (attachment point).

Applications deployed in EDNs are referred to as application instances (or edge applications). In particular, a server application (e.g., social media software, augmented Reality (AR), virtual Reality (VR)) deploys instances (instances) running on the EDN.

EAS 231: may also be referred to as MEC application servers, EAS functions, etc., provide hardware resources for the running of application instances (edge application instances). One application may be deployed in one or more EAS in one EDN, or in multiple EDNs, which may be considered as different EAS of one application, which may share a domain name, may use one anycast IP address, or may use different anycast IP addresses.

Application client 211: the application instance is a peer entity at the terminal equipment side, and the application instance is a client program of the application service at the terminal equipment side. The application client may connect to an application server on the cloud to obtain application traffic, or to deploy EAS running in one or more EDNs to obtain application traffic.

EES 232: the method can provide the enabling capability for the application instance deployed in the EDN, and can better support the deployment of the application in the MEC. Registration of the edge application, authentication and authentication of the terminal equipment can be supported, and an IP address of an application instance is provided for the terminal equipment. It may further be supported to obtain the identity and IP address of the application instance and send the identity and IP address of the application instance to the ECS. Typically, EAS is registered with, or information about EAS is configured on, an EES, referred to as the EAS associated EES, by a management system, which is responsible for controlling, managing EAS registered and configured on the EES.

EEC 212: is a peer entity of EES 232 at the end device side. The EEC is configured to register the information of the EEC with the EES and the information of the application client, perform security authentication and authorization, acquire the IP address of the EAS from the EES, provide the application client with edge computing enabling capabilities (e.g., EAS discovery services), and return the IP address of the EAS to the application client.

ECS 24: is responsible for the configuration of the EDN, for example providing information of EES to the terminal device. The method can also directly provide the information such as the identification and the IP address of the application instance to the terminal equipment, acquire the information such as the identification and the IP address of the application instance by interacting with the DNS of the application, and acquire and store the information such as the identification and the IP address of the application instance from other functional entities. The functionality of the ECS in the current standard may be incorporated into the EEC entity, i.e. the EEC has the functionality of the EEC and ECS described above.

During the running of an application instance (or edge application), when the end device moves outside of the current service area (e.g., the end device moves between EDNs, the end device moves between local data networks (local area data network, LADN)), the currently serviced EAS may not continue to service the currently running application, or the currently serviced EAS is not already the optimal application server to service, and other EAS may be more suitable to service application clients on the end device, thus requiring replacement of the currently serviced EAS (i.e., source EAS) with a new EAS (i.e., target EAS).

After the SMF device detects the user mobility event, it selects a target DNAI (i.e. DNAI corresponding to the EDN where the new EAS is located) for the terminal device, sends the target DNAI to the AF device, and modifies the user plane path, and the AF device selects the new EAS in the EDN corresponding to the target DNAI to continue to provide services for the terminal device.

In this process, a short suspension or interruption of the application service is caused, for which purpose it is necessary to migrate the application context from the EAS currently served (i.e. the source EAS) to the new EAS (i.e. the target EAS), so that the influence of the suspension or interruption of the application service is minimized. This process is known as an application context migration process (alternatively referred to as an application relocation process).

The application context migration process based on the communication system architecture of fig. 2 is shown in fig. 3. Mainly comprises four stages S1-S4:

s1, detecting application context migration: i.e. it is determined that an application context migration is possible, at which time some event is detected by the detecting entity, e.g. a change in the location of the terminal device, or an update of the user plane path of the terminal device, etc.

S2, decision of application context migration: the decision entity determines that application context migration is required.

S3, executing application context migration: the application context is primarily transferred from the source EAS to the target EAS. The relevant information of the target EAS that needs to be notified to the terminal device, the relevant information about the completion of the application context migration on the network side and the relevant information of the target EAS (e.g., the address of the target EAS, the N6 routing information corresponding to the target EAS, etc.) may also be transmitted to the target EAS.

S4, cleaning work after application context migration: involving multiple entities such as an application client initiating a new socket connection to the target EAS, etc.

The 3GPP SA2 standard also defines the use of user plane path notification events of the network to trigger application context migration and user plane path update for subscription and notification flows of user plane path management events managed by application function (application function, AF) traffic (traffic influence).

As shown in fig. 4, in the process that the terminal device moves between service areas, the UPF device and the EDN (identified by DNAI) that provide services to the applications running on the terminal device may change, so that the user plane paths among the terminal device, the RAN device, the UPF device and the EDN change, the EDN that provides services changes from the EDN corresponding to the source DNAI to the EDN corresponding to the target DNAI, and the SMF device notifies the target DNAI to the AF device through the subscription and notification procedure described above, so that the AF device migrates the application context from EAS in the EDN corresponding to the source DNAI to EAS in the EDN corresponding to the target DNAI, thereby minimizing the influence of suspension or interruption of the application service.

The subscription and notification flow described above includes both early notification (Early Notification) and late notification (Late Notification).

Specifically, the early notification (Early Notification) flow is as follows:

the AF device sends an AF Request (AF Request) message to the SMF device to subscribe to the user plane path management event, the AF Request message including traffic information of the application (see "traffic description" cell in table 1) and a subscription notification type (see "AF subscription corresponding SMF event information" cell in table 1). Wherein the subscription notification type is optional for indicating whether it is an early notification (Early Notification) or a late notification (Late Notification), here indicating an early notification (Early Notification); the traffic information of the application is used to identify the application traffic to be routed.

When the SMF device detects a change in DNAI (e.g., a change in the user plane path as shown in fig. 4), the SMF device sends the target DNAI to the AF device. If the indication information waiting for the AF device to answer is not included in the subscription notification type of the AF request message (AF acknowledgment to be expected), the SMF device immediately performs DNAI change or UPF device change (e.g., addition, modification, or deletion).

The AF device immediately transmits an acknowledgement message to the SMF device, or the AF device transmits an acknowledgement message to the SMF device after completing the application context migration in the target DNAI, and if the AF device cannot successfully complete the application context migration, the AF device may transmit a negative acknowledgement message to the SMF device.

If the subscription notification type of the AF request message includes indication information (AF acknowledgment to be expected) waiting for the AF device to answer, the SMF device waits for a positive acknowledgement message from the AF device to be received, and then performs DNAI change or UPF device change (e.g., addition, modification, or deletion).

The late notification (Late Notification) flow is as follows:

the AF device sends an AF request message to the SMF device, wherein the AF request message comprises the traffic information of the application and the subscription notification type. Wherein the subscription notification type here indicates a late notification (Late Notification)).

When the SMF device detects a DNAI change (e.g., a user plane path change as shown in fig. 4), the SMF device performs the DNAI change or the UPF device change (e.g., an addition, a modification, or a deletion). If the subscription notification type of the AF request message does not include the instruction information waiting for the AF device to answer (AF acknowledgment to be expected), the SMF device transmits the target DNAI to the AF device after completing the DNAI change or the UPF device change (e.g., addition, modification, or deletion).

If the subscription notification type of the AF request message includes indication information (AF acknowledgment to be expected) for waiting for the AF device to answer, the SMF device waits for receiving an acknowledgement message from the AF device after transmitting the target DNAI to the AF device, and activates the user plane path of the target DNAI.

The AF device determines whether the target DNAI can be served, determines an appropriate target DNAI if the AF instance needs to be changed, and performs application migration.

In actual deployment, two kinds of AF devices are included, an AF device having an instantiation application capability and an AF device not having an instantiation application capability, respectively.

For an AF device with instantiation application capabilities, the AF device may be an EAS management entity, with management plane functionality and EAS deployment information, responsible for instantiation of the EAS and which edge nodes the EAS is deployed at. Such AF devices can indicate potential deployment locations of applications, and can determine whether the application is deployed or not on the target DNAI or whether the application can be deployed or not by themselves when DNAI changes.

But for AF devices that do not have the capability to instantiate an application, the AF device may be an AF device that implements application service logic functions, such as EAS or EES, that are distributed, do not have management plane functions and EAS deployment information, so the information is not known whether an application is instantiated or deployed. After receiving the DNAI change notification, it can only be determined whether to make the DNAI change and trigger the EAS instantiation. When the application is not deployed on the target DNAI, such AF devices perform an unnecessary application relocation and the SMF device performs an unnecessary UPF device change.

For this reason, in the embodiment of the present application, as shown in fig. 5, for an AF device having an instantiation application capability, the AF device may notify the AF device when the SMF device indicates that the DNAI has changed. Whether the SMF device belongs to "does not know the potential deployment location of the application", does not know which locations the application has been instantiated "," knows the potential deployment location of the application, does not know which locations the application has been instantiated ", or" knows the potential deployment location of the application, knows which locations the application has been instantiated ", the target DNAI can be sent to the AF device whenever a change in DNAI is detected, and the AF device can successfully complete application context migration. In addition, the SMF device may also indicate to the AF device whether the EDN corresponding to the target DNAI is deployed with the application, so that the AF device performs application context migration.

The potential deployment location of an application refers to: applications may be deployed on which DNAI-corresponding EDNs, that is, may be deployed on which DNAI-corresponding EDNs, applications may not yet be instantiated, but may be instantiated on which DNAI-corresponding EDNs if desired.

What the application has been instantiated at is: when the application is deployed or instantiated on the EDNs corresponding to the DNAI, the context can be directly migrated to the EAS of the EDNs corresponding to the DNAI when the context is migrated, and the application can be directly operated.

And for an AF device that does not have the capability of instantiating an application, the AF device may notify the AF device when the SMF device indicates that DNAI has changed and that the application is deployed on the EDN to which the target DNAI corresponds. For the SMF device which knows the potential deployment position of the application and knows which positions the application has been instantiated in, the AF device can be notified when DNAI changes and the application is deployed on the EDN corresponding to the target DNAI, so that the AF device can smoothly complete the application context migration without the AF device instantiating the application. Likewise, the SMF device may also indicate to the AF device whether the EDN corresponding to the target DNAI is deployed with the application, so that the AF device performs application context migration.

Specifically, as shown in fig. 6A, an embodiment of the present application provides a method for sending an identifier, including:

s601, the SMF device acquires the first information and the traffic information of the application.

The traffic information of the application, corresponding to the "traffic description" cell in table one, is used to identify the user plane traffic of the application to be routed, so that the UPF device can detect the user plane traffic of the application.

The first information is used to indicate that the AF device is notified when the DNAI is changed and the application (determined by the traffic information of the application) is deployed on the EDN corresponding to the changed target DNAI. For example, the first information indicates to the SMF device: when the DNAI is changed and the application is deployed on the EDN corresponding to the changed target DNAI, the AF device is notified of the target DNAI.

The occurrence of a DNAI change (also referred to as a DNAI change event) includes the following: the UP path of the PDU session is changed (e.g., established or released), the DNAI serving the application is changed, or the SMF device has received the AF request message and the ongoing PDU session satisfies the condition of notifying the AF device. Changes to DNAI trigger the application context migration described above, and in particular the description of the application context migration above.

The SMF device may obtain the first information by:

mode one: the AF device may transmit the first information to the SMF device, and accordingly, the SMF device may receive the first information from the AF device. The first information may be carried in an AF request message, such as the "first information" cell in table 1. I.e. the first information is explicitly indicated by the AF device.

Mode two: the AF device sends DNAI change subscription information (e.g., AF request message in table 1) to the SMF device, and when the SMF device does not receive application location information (e.g., a "potential location of application" cell in table 1, indicated by DNAI list) from the AF device, the SMF device receives DNAI change subscription information from the AF device, determines the DNAI change subscription information as the first information. I.e. the AF device does not explicitly indicate the first information, which is determined by the SMF device.

The SMF device may obtain traffic information of the application by:

in one possible implementation, the AF device may send traffic information of the application to the SMF device, and accordingly, the SMF device may receive traffic information of the application from the AF device. The traffic information of the application may be carried in the AF request message.

S602, when DNAI is changed, the SMF device sends the changed target DNAI to the AF device according to the first information.

That is, when the DNAI is changed and the application (determined by the traffic information of the application) is deployed on the EDN corresponding to the changed target DNAI, the SMF device transmits the target DNAI to the AF device. The SMF device may send the target DNAI to the AF device through the NEF device.

Accordingly, the AF device receives the target DNAI from the SMF device. The target DNAI may be carried in a user plane path management notification (UP path management notification) message.

Optionally, the SMF device may further send third information to the AF device, and accordingly, the AF device may further receive third information from the SMF device, where the third information is used to indicate whether the application is deployed on the EDN corresponding to the target DNAI. The third information may be carried in a user plane path management notification (UP path management notification) message.

Optionally, when the SMF device sends the target DNAI to the AF device, the SMF device may further carry traffic information of an application corresponding to the DNAI, for example, the traffic information of the application may be an identifier of the application.

In one possible implementation, whether the application is deployed on the EDN corresponding to the target DNAI may be indicated by different values of the same cell.

In another possible implementation manner, the application is deployed (i.e., explicitly indicated) on the EDN corresponding to the target DNAI and the user plane path management notification (UP path management notification) message includes the third information, and the EDN corresponding to the target DNAI is not deployed (i.e., implicitly indicated) without the third information; alternatively, the inclusion of the third information in the AF request message indicates that the application is not deployed on the EDN corresponding to the target DNAI (i.e., explicitly indicated), and the exclusion of the third information indicates that the application is deployed on the EDN corresponding to the target DNAI (i.e., implicitly indicated).

In addition, the SMF device may determine the subscription notification type based on whether the EDN corresponding to the target DNAI is deployed with the application. The subscription notification type is used to indicate an early notification (Early Notification) or a late notification (Late Notification).

For example, if the EDN to which the target DNAI corresponds is deployed with the application, the SMF device may perform a late notification, i.e., the SMF device activates the user plane path path of target DNAI of the target DNAI.

For another example, if the EDN to which the target DNAI corresponds is not deployed with the application, the SMF device may perform an early notification that the SMF device configures a user plane path (user plane) path of target DNAI of the target DNAI, wait for the AF device to send a positive acknowledgement message to the SMF device after the application context migration is completed in the target DNAI, and then the SMF device re-activates the user plane path of the target DNAI.

As shown in fig. 6B, another method for sending an identifier is provided in an embodiment of the present application, including:

s611, the SMF device acquires the second information.

The second information is used to instruct the AF device to be notified whenever DNAI changes. For example, the second information instructs the SMF device to notify the AF device of the changed target DNAI whenever the DNAI is changed.

The second information and the first information may be different values of the same cell; alternatively, the AF request message includes a certain cell indicating the first information and does not include a certain cell indicating the second information; alternatively, a certain cell is included in the AF request message to indicate the second information, and a certain cell is not included to indicate the first information.

Changes made with respect to DNAI are described above and are not repeated here.

The SMF device may obtain the second information by:

mode one: the AF device may transmit the second information to the SMF device, and accordingly, the SMF device may receive the second information from the AF device. The second information may be carried in an AF request message, such as the "second information" cell in table 1. I.e. the second information is explicitly indicated by the AF device.

Mode two: the AF device sends application location information (e.g., the "potential location of application" cell in table 1, represented by the DNAI list) and DNAI change subscription information (e.g., the AF request message in table 1) to the SMF device, and when the SMF device receives the application location information (e.g., the "potential location of application" cell in table 1, represented by the DNAI list) from the AF device, the SMF device receives the DNAI change subscription information from the AF device, determines the DNAI change subscription information as the second information. I.e. the AF device does not explicitly indicate the second information, which is determined by the SMF device.

S612, when the DNAI is changed, the SMF device sends the changed target DNAI to the AF device according to the second information.

That is, when the DNAI is changed, the SMF device transmits the changed target DNAI to the AF device.

Optionally, the AF device may further send traffic information of the application to the SMF device, and correspondingly, the SMF device may further receive traffic information of the application from the AF device; the SMF device may also transmit third information to the AF device, and accordingly, the AF device may also receive the third information from the SMF device. The flow information and the third information about the application are described above and are not repeated here.

As shown in fig. 6C, another method for sending an identifier is provided in an embodiment of the present application, including:

s621, the AF device transmits an AF request message to the SMF device.

Accordingly, the SMF device receives an AF request message from the AF device, where the AF request message is used to subscribe to a DNAI change event (i.e., DNAI changes), and the AF request message includes traffic information of the application. The flow information regarding the DNAI change event (or DNAI change), the application, is described above and is not repeated here.

S622, the SMF device acquires one of the first information or the second information and the traffic information of the application.

Wherein the traffic information of the application is from an AF request message. Reference is made to the foregoing description for the first information and the second information.

Reference is made to mode two in step S601 for the SMF device acquiring the first information.

Reference is made to mode two in step S611 for the SMF device to acquire the second information.

S623, when the SMF device detects that a change has occurred (i.e., DNAI change event), the SMF device transmits the changed target DNAI and third information to the AF device according to the first information or the second information.

Accordingly, the AF device receives the changed target DNAI and the third information from the SMF device.

When the SMF device detects that a change (i.e., DNAI change event) has occurred, the SMF device refers to step S602 with respect to transmitting the changed target DNAI and the third information to the AF device according to the first information, and the SMF device refers to step S612 with respect to transmitting the changed target DNAI and the third information to the AF device according to the second information.

The embodiment of the application provides another method for sending the identifier, the AF device has the capability of instantiating the application, the SMF device obtains a position list of a potential deployment application through the pre-configuration of a network management system or the AF device, the SMF device obtains the position list of the deployed/instantiated application, and the AF device sends second information to the SMF device, namely the AF device is notified as long as DNAI changes.

As shown in fig. 7, the method includes:

s701, the AF device transmits an AF request message to the SMF device.

Accordingly, the SMF device receives an AF request message for subscribing to DNAI change events (i.e., DNAI changes).

The cells of the AF request message are shown in table 1. The AF request message includes traffic information (see "traffic description" cells in table 1) and second information (see "second information" cells in table 1) of the application. Optionally, the AF request message may further include a subscription notification type (see "AF subscription corresponding SMF event information" information element in table 1), where the subscription notification type is used to instruct the SMF device to notify the AF device in the manner of early notification (Early Notification) or late notification (Late Notification).

TABLE 1

This step corresponds to step S611.

S702, when the SMF device detects that DNAI changes (i.e., DNAI changing event), the SMF device sends a user plane path management notification (UP path management notification) message to the AF device subscribed to the event according to the second information.

That is, whenever the SMF device detects that a DNAI change has occurred (i.e., a DNAI change event), a user plane path management notification message is sent to the AF device subscribed to the event. Accordingly, the AF device receives the user plane path management notification message from the SMF device.

The user plane path management notification message includes the changed target DNAI, and optionally, may further include third information.

Regarding the change in DNAI (i.e., DNAI change event) and the third information, see description above.

Alternatively, if the subscription notification type is included in the AF request message, the SMF device transmits the target DNAI to the AF device in the form of an early notification (Early Notification) or a late notification (Late Notification) indicated by the subscription notification type.

Optionally, if the AF request message does not include the subscription notification type, the SMF device determines the subscription notification type according to whether the EDN corresponding to the target DNAI is deployed with the application (the application is determined by the traffic information of the application).

For example, when the application is deployed on the EDN to which the target DNAI corresponds, the SMF device determines the subscription notification type as a late notification (Late Notification). That is, the SMF device may perform step S705 and step S702 to transmit the target DNAI to the AF device, and if the indication information waiting for the AF device to answer (AF acknowledgment to be expected) is not included in the subscription notification type of the AF request message, the SMF device activates the user plane path of the target DNAI. Optionally, when the SMF device sends the target DNAI to the AF device, the SMF device may further carry traffic information of an application corresponding to the DNAI, for example, the traffic information of the application may be an identifier of the application. The AF device immediately transmits an acknowledgement message to the SMF device, or the AF device transmits an acknowledgement message to the SMF device after completing the application context migration in the target DNAI. If the subscription notification type of the AF request message includes indication information (AF acknowledgment to be expected) waiting for the AF device to answer, the SMF device waits for the user plane path of the target DNAI to be activated after receiving an acknowledgement message from the AF device.

When the EDN to which the target DNAI corresponds is not deployed with the application, the SMF device determines the subscription notification type as an early notification (Early Notification). That is, the SMF device performs step S702 to transmit the target DNAI to the AF device, and the AF device immediately transmits an acknowledgement message to the SMF device, or the AF device transmits an acknowledgement message to the SMF device after the completion of the application context migration in the target DNAI. Optionally, when the SMF device sends the target DNAI to the AF device, the SMF device may further carry traffic information of an application corresponding to the DNAI, for example, the traffic information of the application may be an identifier of the application. If the subscription notification type of the AF device includes indication information (AF acknowledgment to be expected) waiting for the AF device to answer, the SMF device waits for an acknowledgement message from the AF device to be received, then performs step S705, and configures the user plane path of the target DNAI. This can avoid unnecessary DNAI changes or UPF device changes (e.g., additions, modifications, or deletions) by the network in the event that the AF device chooses not to make an application context migration or the application context migration fails.

The early notification (Early Notification) or the late notification (Late Notification) is described above and will not be repeated here.

This step corresponds to step S612.

S703, the AF device executes an application context migration process.

If the third information indicates that the application is deployed on the EDN corresponding to the target DNAI, the AF device may perform an application context migration procedure. Because the application is already deployed on the EDN corresponding to the target DNAI, the AF device can directly migrate the application context to the EAS in the EDN corresponding to the target DNAI, and the EDN corresponding to the target DNAI can provide services for the application.

If the third information indicates that the EDN corresponding to the target DNAI is not deployed with the application, the AF device may instantiate the application at the EDN corresponding to the target DNAI and migrate the application context to the EAS in the EDN corresponding to the target DNAI, where the EDN corresponding to the target DNAI may provide services for the application.

S704, if the AF device successfully completes the application context migration and the AF request message includes indication information waiting for the AF device to answer (AF acknowledgment to be expected), the AF device sends an application relocation information notification (ApplicationRelocationInfo notify) message to the SMF device.

The application relocation information notification (ApplicationRelocationInfo notify) message is used to notify the SMF device that the application context migration (application relocation) is successfully completed.

S705, the SMF device performs DNAI change or UPF device change (e.g., addition, modification, or deletion) to update the user plane path.

In this embodiment of the present application, the AF device sends the second information to the SMF device, where the first information indicates that the AF device is notified as soon as the DNAI changes, that is, indicates that the AF device has an instantiation application capability, and as soon as the DNAI changes, the SMF device notifies the AF device of the changed target DNAI, and the AF device can smoothly perform application context migration no matter whether the EDN corresponding to the target DNAI is deployed with the application or not, so that the AF device can avoid selecting to not perform application context migration or failing to perform application context migration, and also avoid the network from performing unnecessary DNAI change or UPF device change (e.g., adding, modifying or deleting), which can save signaling interaction resources.

The embodiment of the application provides another method for sending an identifier, an AF device does not have an instantiation application capability, an SMF device has obtained a location list of a potential (potential/allowed) deployment application through a network management system or pre-configuration of the AF device, and the SMF device obtains the location list of the deployed/instantiated application, and the AF device sends first information to the SMF device, namely, indicates that the AF device is notified when DNAI is changed and the application is deployed on an EDN corresponding to the changed target DNAI.

As shown in fig. 8, the method includes:

s801, the AF device transmits an AF request message to the SMF device.

The cells of the AF request message are shown in table 1. The AF request message includes traffic information (see "traffic description" cells in table 1) and first information (see "first information" cells in table 1) of the application. Optionally, the AF request message may further include a subscription notification type (see "AF subscription corresponding SMF event information" information element in table 1), where the subscription notification type is used to instruct the SMF device to notify the AF device in the manner of early notification (Early Notification) or late notification (Late Notification).

This step corresponds to step S601.

S802, when the SMF device detects that DNAI changes (i.e., DNAI change event), the SMF device sends a user plane path management notification (UP path management notification) message to the AF device subscribed to the event according to the first information.

That is, when the DNAI changes (i.e., DNAI change event) and the application is deployed on the EDN corresponding to the changed target DNAI (the application is determined by the traffic information of the application), the SMF device sends a user plane path management notification message to the AF device subscribed to the event. Accordingly, the AF device receives the user plane path management notification message from the SMF device.

The user plane path management notification message includes the changed target DNAI, and optionally, may further include third information. Optionally, when the SMF device sends the target DNAI to the AF device, the SMF device may further carry traffic information of an application corresponding to the DNAI, for example, the traffic information of the application may be an identifier of the application.

Alternatively, if the subscription notification type is included in the AF request message, the SMF device transmits the target DNAI to the AF device in the form of an early notification (Early Notification) or a late notification (Late Notification) indicated by the subscription notification type. Optionally, when the SMF device sends the target DNAI to the AF device, the SMF device may further carry traffic information of an application corresponding to the DNAI, for example, the traffic information of the application may be an identifier of the application.

Optionally, if the AF request message does not include the subscription notification type, the SMF device determines the subscription notification type according to whether the EDN corresponding to the target DNAI is deployed with the application.

For example, when the application is deployed on the EDN to which the target DNAI corresponds, the SMF device determines the subscription notification type as a late notification (Late Notification). I.e. the SMF device may perform step S802 after performing step S805. And if the subscription notification type of the AF request message includes indication information (AF acknowledgment to be expected) waiting for the AF device to answer, the SMF device waits for the user plane path of the target DNAI to be activated after receiving an acknowledgement message from the AF device after transmitting the target DNAI to the AF device. Optionally, when the SMF device sends the target DNAI to the AF device, the SMF device may further carry traffic information of an application corresponding to the DNAI, for example, the traffic information of the application may be an identifier of the application.

When the application is not deployed on the EDN corresponding to the target DNAI, the SMF device does not execute step S802 and the following step S805, and accordingly, the following steps S803 and S804 are not executed, so that unnecessary DNAI modification or UPF device modification (such as addition, modification or deletion) by the network can be avoided in the case that the AF device chooses not to perform the application context migration or the application context migration fails.

S803, the AF device performs an application context migration process.

If the third information indicates that the application is not deployed on the EDN corresponding to the target DNAI, the AF device does not perform application context migration.

S804, if the AF device successfully completes the application context migration and the indication information waiting for the AF device response is included in the AF request message (AF acknowledgment to be expected), the AF device transmits an application relocation information notification (ApplicationRelocationInfo notify) message to the SMF device.

S805, the SMF device performs DNAI change or UPF device change (e.g. addition, modification or deletion) to update the user plane path.

In this embodiment of the present application, the AF device sends first information to the SMF device, where the first information indicates that the AF device is notified when the DNAI is changed and the application is deployed on the EDN corresponding to the changed target DNAI, that is, the AF device does not have the application instantiation capability, and when the DNAI is changed and the application is deployed on the EDN corresponding to the changed target DNAI, the SMF device notifies the changed target DNAI of the AF device, so that when the application is not deployed on the EDN corresponding to the target DNAI, the AF device is not notified, and thus, unnecessary DNAI change or UPF device change (such as addition, modification or deletion) by the network can be avoided under the condition that the AF device chooses not to perform application context migration or application context migration fails, and signaling interaction resources can be saved.

The embodiment of the present application provides another method for sending an identifier, where the SMF device has obtained a location list of a potential (potential/allowed) deployment application through a network management system or a pre-configuration of the AF device, and the SMF device obtains a location list of the deployed/instantiated application, and the AF device does not indicate the first information, but determines the first information by the SMF device according to whether the application location information from the AF device is received.

As shown in fig. 9A, the method includes:

s901, the AF device transmits an AF request message to the SMF device.

The cells of the AF request message are shown in table 1. The AF request message includes traffic information of the application (see "traffic description" cells in table 1). Optionally, the AF request message may further include a subscription notification type (see "AF subscription corresponding SMF event information" information element in table 1), where the subscription notification type is used to instruct the SMF device to notify the AF device in the manner of early notification (Early Notification) or late notification (Late Notification).

This step corresponds to step S621.

S902, the SMF device determines the first information or the second information according to whether application location information from the AF device is received.

When the SMF device does not receive application location information (e.g., an "application's potential location" cell in table 1, represented by a DNAI list) from the AF device, the SMF device receives DNAI change subscription information (e.g., an AF request message in table 1) from the AF device, determines the DNAI change subscription information as the first information. Reference is specifically made to the related description in step S601.

When the SMF device receives the application location information from the AF device, the SMF device receives DNAI change subscription information from the AF device, and determines the DNAI change subscription information to be second information. Refer specifically to the related description in step S611.

S903, when the SMF device detects that a change occurs (i.e., DNAI change event), the SMF device sends a user plane path management notification (UP path management notification) message to the AF device subscribed to the event according to the first information or the second information.

When the SMF device detects that a change occurs (i.e., DNAI change event), the SMF device may send a user plane path management notification (UP path management notification) message to the AF device subscribed to the event according to the second information in the manner of step S702; alternatively, the SMF device may send a user plane path management notification (UP path management notification) message to the AF device subscribed to the event according to the first information in the manner of step S802. And will not be repeated here.

This step corresponds to step S622.

S904, the AF device performs an application context migration process.

This step is the same as step S803 and is not repeated here.

S905, if the AF device successfully completes the application context migration and the indication information waiting for the AF device to answer (AF acknowledgment to be expected) is included in the AF Request (AF Request) message, the AF device transmits an application relocation information notification (ApplicationRelocationInfo notify) message to the SMF device.

S906, the SMF device performs DNAI change or UPF device change (e.g. addition, modification or deletion) to update the user plane path.

In the embodiment of the present application, the AF device does not transmit the first information or the second information to the SMF device, but the SMF device determines the first information or the second information according to whether application location information from the AF device is received. The first information indicates that the AF device is notified when the DNAI is changed and the application is deployed on the EDN corresponding to the changed target DNAI, namely the AF device does not have the application instantiation capability, and the SMF device notifies the AF device of the changed target DNAI when the DNAI is changed and the application is deployed on the EDN corresponding to the changed target DNAI, so that the AF device is not notified when the application is not deployed on the EDN corresponding to the target DNAI, and unnecessary DNAI change or UPF device change (such as adding, modifying or deleting) by the network under the condition that the AF device selects not to perform application context migration or fails to perform application context migration can be avoided, and signaling interaction resources can be saved. The first information indicates that the AF device is informed if the DNAI is changed, namely the AF device has the instantiation application capability, and the SMF device informs the target DNAI after the change of the AF device if the DNAI is changed, and the AF device can smoothly perform application context migration no matter whether the application is deployed on the EDN corresponding to the target DNAI, so that the AF device can be prevented from selecting not to perform application context migration or failing to perform application context migration, unnecessary DNAI change or UPF device change (such as adding, modifying or deleting) by the network is avoided, and signaling interaction resources can be saved.

The embodiment of the application provides another method for sending the identifier, as shown in fig. 9B, the method includes:

s1, the EAS sends a user plane path management event subscription request message (user plane path management event subscribe request) to the EES.

The message is used to track user plane path changes. The message optionally carries DNAI change type information, which is used to indicate that EAS expects a user plane path (user plane path) change and only receives notification message when the target DNAI corresponding to the user plane path has EAS deployment. Where a target DNAI has an EAS deployment may be understood as having an EAS deployment at the target DNAI, "deployment" may be understood as available or instantiation (instantiation). Wherein the EAS deployed at the target DNAI is the same as the EAS that sent the request message as the EAS that provided the same application service. The request message may also carry an identifier of the terminal device, an IP address, or an identifier of the terminal device group. The request message may also carry a subscription notification type indicating whether the notification is early (Early Notification) or late (Late Notification), and an EAS acknowledgement indication (EAS acknowledgement) message indicating that the notification message requires EAS to provide acknowledgement information.

S2, the EES performs authorization check on the request of the EAS, judges that the EAS is allowed to execute the subscription operation, and records the subscription information of the EAS.

S3, the EES sends a user plane path management event subscription response message (user plane path management event subscribe response) to the EAS.

The message is used to confirm that the edge application server successfully subscribed to the user plane path management event.

S4, after the authorization check is successful in the step S2, the EES sends an AF request message to the SMF device.

The request message is used to subscribe to the SMF device for a user plane path change event.

If the EAS provides DNAI change type information in the message of S1, the EES carries the parameter information in the application function request message. If the EAS also carries in the message of S1 the identity of the terminal device, the IP address or identity of the group of terminal devices, the type of subscription notification, the indication of EAS acknowledgement, the EES also carries in the AF request message the above parameters. In one possible implementation, if the EAS does not provide DNAI change type information in the message of S1, the EES may still carry the DNAI change type information in the application function request message. Specifically, the EES may determine that the information needs to be added to the AF request message according to capability information of EAS, or local policy information, etc. Wherein DNAI change type information may be regarded as first information in the previous embodiments.

The present application does not limit the sequence relationship between step S4 and step S3.

S5, the SMF device stores the subscription information of the EES.

S6, the SMF device sends an AF request confirmation message to the EES.

This step is optional and is used to indicate that the EES successfully subscribed to the user plane path event.

Wherein step S3 may also be sent after the EES receives the acknowledgement message from the SMF device at step S6.

S7, the SMF device detects a change event of the user plane.

And S8, when detecting a change event of a user, if the EES provides DNAI change type information, the SMF device can send a user plane path management notification message to the EAS through the EES after determining the target DNAI and determining that the EDN corresponding to the target DNAI is deployed with the application (or the EDN is deployed with the EAS (the same application as the EAS sending S1)).

The user plane path management notification message includes the target DNAI, that is, when the DNAI is changed, the SMF device sends the changed target DNAI to the AF device according to the first information (the DNAI change type information may be equivalent to the first information), and the description of this step may refer to the previous step S602.

If the EES does not provide DNAI change type information, the SMF may send a user plane path management notification message to the EES when it is determined that there is a change in DNAI, the message carrying the target DNAI. Optionally, information of the application corresponding to the DNAI is also carried.

S9, if the EES does not provide DNAI change type information to the SMF device, the EES further needs to judge whether the application (or whether the EAS deployment exists) is deployed on the EDN corresponding to the target DNAI when receiving the target DNAI contained in the user plane path management notification message sent by the SMF.

This step is optional, where the EES can determine whether the target DNAI has an edge application deployment (EAS that is the same application as the EAS that sent S1) by interacting with the ECS, or with other EES, or in the EES local configuration information, or interacting with the EAS management system, etc. When the target DNAI has the edge application deployment, the EES sends a user plane path management event notification message to the EAS, which may contain the target DNAI. Further the user plane path management event notification message indicates that the target DNAI has the edge application deployment described above. If the EES provides DNAI change type information to the SMF, the EES determines that the target DNAI has the edge application deployment when the EES receive the target DNAI contained in the user plane path management notification message sent by the SMF. The EES sends a user plane path management event notification message to the EAS, which may contain the target DNAI described above. Further the user plane path management event notification message indicates that the target DNAI has the edge application deployment described above.

According to the identifier sending method provided by the embodiment of the application, the EAS indicates that the EAS is notified when the DNAI is changed and the application is deployed on the changed target DNAI by carrying DNAI change type information in the subscription of the user plane path management event, so that the EAS can be allowed to provide a filtering condition of an accurate user plane path change notification event, and the EES can further indicate DNAI change type information (namely, the first information) to the SMF (namely, the first information) so that the SMF can notify the EES of the changed target DNAI when the application is deployed on the changed target DNAI pair when the DNAI is changed. And further, it can be avoided that when the application is not deployed on the EDN corresponding to the target DNAI, the SMF will not notify the EES, and the EES will not notify the EAS. In this way, unnecessary DNAI changes or UPF device changes (e.g., additions, modifications, or deletions) by the network in the event that the EAS selects to not perform an application context migration or the application context migration fails can be avoided, and signaling interaction resources can be saved. In addition, the EES can further filter the user plane path management event notification message sent by the SMF, and further determine whether the target DNAI provided by the SMF has EAS application deployment, so that it can be further limited that the notification message is sent to the EAS only when the target DNAI has EAS deployment, and further avoid the situation that the signaling interaction is wasted when the target DNAI cannot be processed and the target DNAI has no EAS deployment, and increase the extra burden on the EAS. In this way, unnecessary DNAI changes or UPF device changes (such as addition, modification or deletion) by the network can be avoided under the condition that the AF device chooses not to perform application context migration or fails to perform application context migration, and signaling interaction resources can be saved.

The foregoing description of the solution provided in the embodiments of the present application has been mainly presented in terms of interaction between devices. Correspondingly, the embodiment of the application also provides a communication device which is used for realizing the various methods. The communication device may be an SMF device in the above method embodiment, or a chip or a functional module in the SMF device. Alternatively, the communication device may be an AF device in the above-described method embodiment, or a chip or a functional module in the AF device.

It will be appreciated that the communication device, in order to achieve the above-described functions, comprises corresponding hardware structures and/or software modules performing the respective functions. Those of skill in the art will readily appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The embodiment of the application may divide the functional modules of the communication device according to the embodiment of the method, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that, in the embodiment of the present application, the division of the modules is schematic, which is merely a logic function division, and other division manners may be implemented in actual implementation.

For example, the communication device is taken as an SMF device in the above method embodiment. Fig. 10 shows a schematic structural diagram of a communication device 100. The communication device 100 may be the SMF device of fig. 1. The communication device 100 comprises a processing module 1001 and a transceiver module 1002. The processing module 1001 may also be referred to as a processing unit, for implementing the processing functions of the SMF device in the above-described method embodiment, for example, performing the processing functions of the SMF device in fig. 6A-9B. The transceiver module 1002 may also be referred to as a transceiver unit, and is configured to implement the transceiver function of the SMF device in the foregoing method embodiment. For example, performing the transceiving functions of the SMF device of fig. 6A-9B. The transceiver module 1002 may be referred to as a transceiver circuit, transceiver, or communication interface.

In a possible implementation manner, the processing module 1001 is configured to obtain first information and traffic information of an application, where the first information is used to indicate that an application is deployed on an edge data network corresponding to a target DNAI after the change of the data network access identifier DNAI, and notify the AF device; when the DNAI changes, the transceiver module 1002 is configured to send the target DNAI to the AF device according to the first information. Optionally, when the SMF device sends the target DNAI to the AF device, the SMF device may further carry traffic information of an application corresponding to the DNAI, for example, the traffic information of the application may be an identifier of the application.

In one possible implementation, the transceiver module 1002 is configured to receive the first information from the AF device.

In one possible implementation, when the transceiver module 1002 does not receive the application location information from the AF device, receives DNAI change subscription information from the AF device, the processing module 1001 is configured to determine that the DNAI change subscription information is the first information.

In a possible implementation manner, the transceiver module 1002 is further configured to send third information to the AF device, where the third information is used to indicate that the edge data network corresponding to the target DNAI is deployed with an application.

In one possible implementation, if the edge data network to which the target DNAI corresponds is deployed with an application, the processing module 1001 is configured to activate the user plane path of the target DNAI.

In one possible implementation, if the edge data network to which the target DNAI corresponds is not deployed with an application, the processing module 1001 is configured to configure a user plane path of the target DNAI.

In a possible implementation manner, the processing module 1001 is configured to obtain second information, where the second information is used to instruct the AF device to be notified whenever the data network access identifier DNAI is changed; when the DNAI is changed, the transceiver module 1002 is configured to send the changed target DNAI to the AF device according to the second information. Optionally, when the SMF device sends the target DNAI to the AF device, the SMF device may further carry traffic information of an application corresponding to the DNAI, for example, the traffic information of the application may be an identifier of the application.

In one possible implementation, the transceiver module 1002 is configured to receive the second information from the AF device.

In one possible implementation, when the transceiver module 1002 receives the application location information from the AF device, receives DNAI change subscription information from the AF device, the processing module 1001 is configured to determine that the DNAI change subscription information is the second information.

In one possible implementation, the transceiver module 1002 is configured to receive traffic information of an application from an AF device; and sending third information to the AF device, wherein the third information is used for indicating that the edge data network corresponding to the target DNAI is deployed with the application.

In a possible implementation manner, the transceiver module 1002 is configured to receive an application function request message, where the application function request message is used to subscribe to a data network access identifier DNAI modification event, and the application function request message includes flow information of an application; the processing module 1001 is configured to obtain one of the first information or the second information and flow information of an application; the first information is used for indicating that the data network access identifier DNAI is changed and notifying an AF device when an application is deployed on the edge data network corresponding to the changed target DNAI; the second information is used for indicating that the AF device is informed as long as the data network access identification DNAI is changed; when the DNAI is changed, the transceiver module 1002 is configured to send, to the AF device, the changed target DNAI and third information according to the first information or the second information, where the third information is used to indicate whether an application is deployed on an edge data network corresponding to the target DNAI.

Taking the communication device as an example of the AF device in the above-described method embodiment. Fig. 11 shows a schematic structural diagram of a communication device 110. The communication device 110 may be an AF network element in fig. 1. The communication device 110 comprises a processing module 1101 and a transceiver module 1102. The processing module 1101 may also be referred to as a processing unit, for implementing the processing functions of the AF apparatus in the above-described method embodiment, for example, performing the processing functions of the AF apparatus in fig. 6A-9B. The transceiver module 1102, which may also be referred to as a transceiver unit, is configured to implement the transceiver function of the AF device in the above-described method embodiment, for example, perform the transceiver function of the AF device in fig. 6A-9B. The transceiver module 1102 may be referred to as a transceiver circuit, transceiver, or communication interface.

In a possible implementation manner, the transceiver module 1102 is configured to send, to the SMF device, first information and application traffic information, where the first information is used to indicate that the data network access identifier DNAI is changed and that an application is deployed on an edge data network corresponding to the changed target DNAI, and notify the AF device; the target DNAI is received from the SMF device.

In one possible implementation, the transceiver module 1102 is configured to receive third information from the SMF device, where the third information is used to indicate that an application is deployed on the edge data network corresponding to the target DNAI.

In a possible implementation manner, the transceiver module 1102 is configured to send second information to the SMF device, where the second information is used to instruct the AF device to be notified whenever the data network access identifier DNAI is changed; the altered target DNAI is received from the SMF device.

In one possible implementation, the transceiver module 1102 is configured to send traffic information of an application by the SMF device; third information is received from the SMF device, the third information being used to indicate that an application is deployed on the edge data network corresponding to the target DNAI.

In a possible implementation manner, the transceiver module 1102 is configured to send an application function request message to the SMF device, where the application function request message is used to subscribe to a data network access identifier DNAI change event, and the application function request message includes flow information of an application; and receiving the changed target DNAI and third information from the SMF device, wherein the third information is used for indicating whether an application is deployed on the edge data network corresponding to the target DNAI. Optionally, when the SMF device sends the target DNAI to the AF device, the SMF device may further carry traffic information of an application corresponding to the DNAI, for example, the traffic information of the application may be an identifier of the application.

In the present embodiment, the above-described communication apparatus is presented in a form in which the respective functional modules are divided in an integrated manner. A "module" herein may refer to a particular ASIC, an electronic circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other device that can provide the described functionality.

In particular, the functions/implementations of the processing modules may be implemented by a processor in the communications device invoking computer-executable instructions stored in a memory. The functions/implementations of the transceiver module may be implemented by a transceiver or a communication interface in a communication device.

Since the communication device provided in this embodiment can execute the above method, the technical effects obtained by the communication device can be referred to the above method embodiment, and will not be described herein.

As shown in fig. 12, the embodiment of the present application further provides a communication device 120 including a processor 1201, a memory 1202 and a communication interface 1203, where the processor 1201 is coupled to the memory 1202, and when the processor 1201 executes a computer program or instruction in the memory 1202, a corresponding method of the SMF device in fig. 6A-9B is performed.

As shown in fig. 13, the embodiment of the present application further provides a communication device, where the communication device 130 includes a processor 1301, a memory 1302, and a communication interface 1303, where the processor 1301 is coupled to the memory 1302, and when the processor 1301 executes a computer program or instruction in the memory 1302, a method corresponding to the AF device in fig. 6A-9B is executed.

Embodiments of the present application also provide a computer-readable storage medium having a computer program stored therein, which when run on a computer or processor, causes the computer or processor to perform a method corresponding to the SMF device of fig. 6A-9B.

Embodiments of the present application also provide a computer-readable storage medium having a computer program stored therein, which when run on a computer or processor, causes the computer or processor to perform a method corresponding to the AF apparatus in fig. 6A-9B.

Embodiments of the present application also provide a computer program product comprising instructions which, when executed on a computer or processor, cause the computer or processor to perform a method corresponding to the SMF device of fig. 6A-9B.

Embodiments of the present application also provide a computer program product comprising instructions which, when executed on a computer or processor, cause the computer or processor to perform a method corresponding to the AF device of fig. 6A-9B.

The embodiment of the application provides a chip system, which comprises a processor, wherein the processor is used for a communication device to execute a method corresponding to an SMF device in fig. 6A-9B or execute a method corresponding to an AF device in fig. 6A-9B.

In one possible design, the system on a chip also includes memory to hold the necessary program instructions and data. The chip system may include a chip, an integrated circuit, or may include a chip and other discrete devices, which are not specifically limited in this embodiment.

The communication device, chip, computer storage medium, computer program product or chip system provided in the present application are used to perform the above-mentioned method, so that the advantages achieved by the method can be referred to the advantages provided in the above-mentioned embodiments, and are not described herein again.

The processor referred to in the embodiments of the present application may be a chip. For example, it may be a field programmable gate array (field programmable gate array, FPGA), an application specific integrated chip (application specific integrated circuit, ASIC), a system on chip (SoC), a central processing unit (central processor unit, CPU), a network processor (network processor, NP), a digital signal processing circuit (digital signal processor, DSP), a microcontroller (micro controller unit, MCU), a programmable controller (programmable logic device, PLD) or other integrated chip.

The memory to which embodiments of the present application relate may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, indirect coupling or communication connection of devices or units, electrical, mechanical, or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using a software program, it may 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 described in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may 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 may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more servers, data centers, etc. that can be integrated with the medium. The usable medium may be a magnetic medium (e.g., a floppy Disk, a hard Disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

An identification transmitting method, comprising:

the session management function device obtains first information and flow information of an application, wherein the first information is used for indicating that when a data network access identifier DNAI is changed and the application is deployed on an edge data network corresponding to a changed target DNAI, the application function device is notified;

when the DNAI is changed, the session management function device sends the target DNAI to the application function device according to the first information.
The method of claim 1, wherein the session management function device obtains the first information, comprising:

the session management function device receives the first information from the application function device.
The method of claim 1, wherein the session management function device obtains the first information, comprising:

When the session management function device does not receive the application location information from the application function device, the session management function device receives DNAI change subscription information from the application function device, and determines that the DNAI change subscription information is the first information.
A method according to any one of claims 1-3, further comprising:

and the session management function device sends third information to the application function device, wherein the third information is used for indicating that the application is deployed on the edge data network corresponding to the target DNAI.
The method of any one of claims 1-4, further comprising:

and if the edge data network corresponding to the target DNAI is deployed with the application, the session management function device activates a user plane path of the target DNAI.
The method of any one of claims 1-4, further comprising:

and if the edge data network corresponding to the target DNAI is not deployed with the application, the session management function device configures a user plane path of the target DNAI.
An identification transmitting method, comprising:

The method comprises the steps that an application function device sends first information and flow information of an application to a session management function device, wherein the first information is used for indicating that a data network access identifier DNAI is changed and notifying the application function device when the application is deployed on an edge data network corresponding to a changed target DNAI;

the application function device receives the target DNAI from the session management function device.
The method as recited in claim 7, further comprising:

the application function device receives third information from the session management function device, where the third information is used to indicate that the application is deployed on an edge data network corresponding to the target DNAI.
An identification transmitting method, comprising:

the method comprises the steps that an application function device sends an application function request message to a session management function device, wherein the application function request message is used for subscribing a data network access identifier DNAI change event, and the application function request message comprises flow information of an application;

the application function device receives the changed target DNAI and third information from the session management function device, where the third information is used to indicate whether the application is deployed on an edge data network corresponding to the target DNAI.
An identification transmitting method, comprising:

the session management function device obtains first information and flow information of an application, wherein the first information is used for indicating that when a data network access identifier DNAI is changed and the application is deployed on an edge data network corresponding to a changed target DNAI, the application function device is notified;

when the DNAI is changed, the session management function device sends the target DNAI to the application function device according to the first information;

the application function device receives the target DNAI from the session management function device.
The method of claim 10, wherein the session management function device obtains the first information, comprising:

the application function device sends the first information to the session management function device;

the session management function device receives the first information from the application function device.
The method of claim 10, wherein the session management function device obtains the first information, comprising:

the application function device sends DNAI change subscription information to the session management function device;

when the session management function device does not receive the application location information from the application function device, the session management function device receives the DNAI change subscription information and determines that the DNAI change subscription information is the first information.
The method according to any one of claims 10-12, further comprising:

the session management function device sends third information to the application function device, wherein the third information is used for indicating that the application is deployed on the edge data network corresponding to the target DNAI;

the application function device receives the third information from the session management function device.
The method according to any one of claims 10-13, further comprising:

and if the edge data network corresponding to the target DNAI is deployed with the application, the session management function device activates a user plane path of the target DNAI.
The method according to any one of claims 10-13, further comprising:

and if the edge data network corresponding to the target DNAI is not deployed with the application, the session management function device configures a user plane path of the target DNAI.
An identification transmitting method, comprising:

the method comprises the steps that an application function device sends an application function request message to a session management function device, wherein the application function request message is used for subscribing a data network access identifier DNAI change event, and the application function request message comprises flow information of an application;

The session management function device receives the application function request message;

the session management function device obtains one of the first information or the second information and the traffic information of the application; the first information is used for indicating that the data network access identifier DNAI is changed and notifying the application function device when the application is deployed on the edge data network corresponding to the changed target DNAI; the second information is used for indicating that the application function device is notified as long as the data network access identifier DNAI is changed;

when DNAI is changed, the session management function device sends, to the application function device, changed target DNAI and third information according to the first information or the second information, where the third information is used to indicate whether the application is deployed on an edge data network corresponding to the target DNAI;

the application function device receives the target DNAI and the third information from the session management function device.
The method of claim 16, wherein the session management function device obtains one of the first information or the second information, comprising:

when the session management function device does not receive the application location information from the application function device, the session management function device receives DNAI change subscription information from the application function device, and determines that the DNAI change subscription information is the first information;

When the session management function device receives the application location information from the application function device, the session management function device receives the DNAI change subscription information and determines that the DNAI change subscription information is the second information.
The method according to any one of claims 16-17, further comprising:

and if the edge data network corresponding to the target DNAI is deployed with the application, the session management function device activates a user plane path of the target DNAI.
The method according to any one of claims 16-17, further comprising:

and if the edge data network corresponding to the target DNAI is not deployed with the application, the session management function device configures a user plane path of the target DNAI.
A communication device comprising a processor, the processor being connected to a memory, the memory being configured to store a computer program, the processor being configured to execute the computer program stored in the memory, to cause the communication device to perform the method according to any one of claims 1-6 or to perform the method corresponding to the session management function device according to any one of claims 10-19.
A communication device comprising a processor, the processor being connected to a memory, the memory being configured to store a computer program, the processor being configured to execute the computer program stored in the memory, to cause the communication device to perform the method according to any one of claims 7-9 or to perform the method corresponding to the application function device according to any one of claims 10-19.
A communication system comprising a communication device according to claim 20 and a communication device according to claim 21.